Board index Linux

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

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

Post by Chris J. Rad » Thu, 05 Aug 1993 05:24:44



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).

 
 
 
Top

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

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

2. Bpdbjobs with NetBackup 4.5

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

4. Pop3 needed for Solaris

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

6. Please HELP me identify a FastEthernet Pci card

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

8. Alter variable in parent from child

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