Board index Linux

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

Post by Gregor Kuhlman » Thu, 17 May 2001 21:51:56



Hi,


Apollo Pro chipset (motherboard type unknown since I have no physical access
to the machine). SCSI subsystem is an Adaptec AIC 7892 (U2W-LVD?), NIC is a
LiteON LNE100TX.

Since installing the machine about 3 weeks ago I experienced regular errors
and lockups, including - but not limited to - the following:

* file names changing single characters (e.g. "libcrypt.so" was suddenly
named "libtrypt.so")
* "unable to handle kernel paging request" errors, each time from different
processed and virtual addresses
* no network transfer but machine still up, i.e. local console login
possible and all necessary processes running, NIC properly configured
* programs (both system programs and "homebrewn" ones) cause unexpected
"segmentation faults" (but work fine when started a couple of minutes later
with the same parameters/input files)

I suspect a problem with the system RAM (perhaps also chipset related)
and/or SCSI termination.

Any help would be very much appreciated!

- Gregor

 
 
 
Top

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

Post by Tim » Fri, 18 May 2001 00:07:37


Your problem could be RAM based, try running a memory test program.
However I have had similar problems which were caused by a kernel bug.
Upgrading to a more recent kernel eliminated the errors.

Tim


> Hi,


> Apollo Pro chipset (motherboard type unknown since I have no physical access
> to the machine). SCSI subsystem is an Adaptec AIC 7892 (U2W-LVD?), NIC is a
> LiteON LNE100TX.

> Since installing the machine about 3 weeks ago I experienced regular errors
> and lockups, including - but not limited to - the following:

> * file names changing single characters (e.g. "libcrypt.so" was suddenly
> named "libtrypt.so")
> * "unable to handle kernel paging request" errors, each time from different
> processed and virtual addresses
> * no network transfer but machine still up, i.e. local console login
> possible and all necessary processes running, NIC properly configured
> * programs (both system programs and "homebrewn" ones) cause unexpected
> "segmentation faults" (but work fine when started a couple of minutes later
> with the same parameters/input files)

> I suspect a problem with the system RAM (perhaps also chipset related)
> and/or SCSI termination.

> Any help would be very much appreciated!

> - Gregor


 
 
 
Top

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

Post by Michael Heimin » Fri, 18 May 2001 07:05:53



> Hi,


> Apollo Pro chipset (motherboard type unknown since I have no physical access
> to the machine). SCSI subsystem is an Adaptec AIC 7892 (U2W-LVD?), NIC is a
> LiteON LNE100TX.

> Since installing the machine about 3 weeks ago I experienced regular errors
> and lockups, including - but not limited to - the following:

> * file names changing single characters (e.g. "libcrypt.so" was suddenly
> named "libtrypt.so")

Hmmm, lybcrypt.so is used by passwd, perhaps your machine was hacked?

Quote:> * "unable to handle kernel paging request" errors, each time from different
> processed and virtual addresses
> * no network transfer but machine still up, i.e. local console login
> possible and all necessary processes running, NIC properly configured
> * programs (both system programs and "homebrewn" ones) cause unexpected
> "segmentation faults" (but work fine when started a couple of minutes later
> with the same parameters/input files)

> I suspect a problem with the system RAM (perhaps also chipset related)
> and/or SCSI termination.

> Any help would be very much appreciated!

The rest sounds a bit like bad RAM, try compiling a kernel,
it shouldn't stop with the message: gcc caught fatal signal 11.

Did you check the various file in /var/log for some more hints?

Michael Heiming

 
 
 
Top

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

Post by Gregor Kuhlman » Fri, 18 May 2001 21:04:38


Hi,

thanks for your reply.

I am currently trying more conservative memory timing settings, perhaps a
BIOS update might also help.

I already installed the latest RedHat released kernel and modules
(2.2.19-7.0.1).

- Gregor



> Your problem could be RAM based, try running a memory test program.
> However I have had similar problems which were caused by a kernel bug.
> Upgrading to a more recent kernel eliminated the errors.

> Tim


> > Hi,


Via
> > Apollo Pro chipset (motherboard type unknown since I have no physical
access
> > to the machine). SCSI subsystem is an Adaptec AIC 7892 (U2W-LVD?), NIC
is a
> > LiteON LNE100TX.

> > Since installing the machine about 3 weeks ago I experienced regular
errors
> > and lockups, including - but not limited to - the following:

> > * file names changing single characters (e.g. "libcrypt.so" was suddenly
> > named "libtrypt.so")
> > * "unable to handle kernel paging request" errors, each time from
different
> > processed and virtual addresses
> > * no network transfer but machine still up, i.e. local console login
> > possible and all necessary processes running, NIC properly configured
> > * programs (both system programs and "homebrewn" ones) cause unexpected
> > "segmentation faults" (but work fine when started a couple of minutes
later
> > with the same parameters/input files)

> > I suspect a problem with the system RAM (perhaps also chipset related)
> > and/or SCSI termination.

> > Any help would be very much appreciated!

> > - Gregor

 
 
 
Top

RedHat7 "unable to handle kernel paging request" and other strange errors - RAM problem?

Post by Gregor Kuhlman » Fri, 18 May 2001 21:08:18


Hi,

Quote:> The rest sounds a bit like bad RAM, try compiling a kernel,
> it shouldn't stop with the message: gcc caught fatal signal 11.

Good idea, I will try this...

Quote:> Did you check the various file in /var/log for some more hints?

the only error messages I got were some "unable to handle kernel paging
request" and "failed to read past end of device" errors. In most cases, the
machine just rebooted by itstel or simply locked up.

- Gregor

 
 
 
Top

1. Yggdrasil ignoring us - "unable to handle kernel paging request" problem!

We have purchased the Yggdrasil CD-ROM version of Linux (0.99.7A)

and have been able to run it in CD-Dependent mode just fine.  

Now we have installed it on a different hard drive (ESDI, with

a caching controller) in the "Full binary install" (i.e. boot

and run entirely from HD).  It boots and begins to come up, but

partway through it stops with the following message:

        Unable to handle kernel paging request at address

        C00002e8

        Oops: 0002

        EIP: 008:0112690

        EEFLAGS: 00010206

        fs: 0017

        base: 00000000   limit: C0000000

        PID: 1   Process Nr: 1

        Trying to free kernel page-directory: Not good

Then it does a bit more HD activity and stops dead.  I have

spoken with someone else who is experiencing more or less

the same symptoms with the Yggdrasil version as well.  Any

help or suggestions would be appreciated.  (We *can* still

boot from the floppy/CD-ROM combination and manually mount

the hard drive, so I don't think there's a hardware problem).

2. Possibly broken kernel patch on SunOS 5.6

3. "Unable to handle kernel paging request" x 3

4. Star Office 6.0?

5. SLS 1.02: "unable to handle kernel paging request"

6. Solaris 9 Jumpstart

7. Need help on "Unable to handle kernel paging request"

8. How to generate filesystem image

9. OOPS: "Unable to handle kernel paging request ..."

10. "Unable to handle kernel paging request..."

11. "unable to handle kernel paging request at virtual address ....." (fwd)

12. kernel 0.99p11 with scsi-patches "unable to handle paging request"

13. "unable to handle kernel paging request"


All times are UTC
Board index