Oops: Unable to handle kernel paging request When setup!

Oops: Unable to handle kernel paging request When setup!

Post by Erik Kileda » Tue, 15 Dec 1998 04:00:00




> Hi! All.

>     I just move to another Machine and try to setup my SLACKWARE3.5(kernel
> 2.0.34) which I used  for several months.

>     The setup runs fine until I restart the machine. It reports during init
> (part of the dmesg's result):

> PPP line discipline registered.
> Unable to handle kernel paging request at virtual address f3344544
> current->tss.cr3 = 01f5a000, %cr3 = 01f5a000

I am getting the same messages (different addresses) when trying to
install SuSE Linux on an AMD K6-2 300 with a Microstar MI-5169 (rev 2)
motherboard. I also tried installing Red Hat 5.1 with this setup and
the installation program crashed with segmentation faults about
at the point where it's supposed to say 'entering stage 2 of install'
(or something similar).

I then tried swapping the AMD chip with a GenuineIntel Pentium 166
and the installation runs smoothly.

Btw, win98 installed and runs without any apparent problems with both
chips.

I am beginning to think the motherboard is bad (I replaced the AMD for
another AMD with same results, replaced the RAM (with certified
PC100 RAM (appears on an Intel list) etc. without any luck), or that
the combination of parts is just not stable for Linux.

Right now I am planning to get an Asus
super socket 7 motherboard and try the AMD again...

Any input appreciated, I would really like to hear from people with
similar problems - what is your configuration? (CPU, MB etc.).

-Erik

 
 
 

Oops: Unable to handle kernel paging request When setup!

Post by Erik Kileda » Sat, 19 Dec 1998 04:00:00



> I am beginning to think the motherboard is bad (I replaced the AMD for
> another AMD with same results, replaced the RAM (with certified
> PC100 RAM (appears on an Intel list) etc. without any luck), or that
> the combination of parts is just not stable for Linux.

> Right now I am planning to get an Asus
> super socket 7 motherboard and try the AMD again...

While I ended up with a Diamond Micronics C200 motherboard instead,
(for reasons of convenience) it seems that my guess was correct.
With the new motherboard I was able to perform the installation without
any problems and the system has been running fine for 2 days now.

The motherboard that caused trouble was a Microstar MS5169 ver 2.1 AL9.