Crash on boot (2.4.5)
Hi, everyone.. I'm borrowing my roommate's email, so please send replies to [email protected]. Thanks!
Here's my problem... when I boot anything 2.4, I get several oopsen in a row, all of which are either (most commonly) kernel paging request could not be handled, or (much less common) unable to handle kernel Null pointer dereference. I will send any info on request, but here's my hardware and kernel config:
iWill KKR-266R (Via 8363 Northbridge, 686B south)
AMD tbird 1GHz
256MB cas2 pc133 sdram
ATI Radeon DDR 64MB VIVO
Kingston KNE120TX (Realtek 8139 chip)
SBLive! 5.1
IBM GXP75 30GB (on the via ide controller)
Pioneer 16x dvd
ls120
This happens regardless if I turn on swap or not. When swap is on, it is a 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I believe I read somewhere that someone was working on that, and I didn't want to waste the extra 384MB on swap).
Is there anything I can do to fix this?
-- andyw
p.s., booting with devfs=nomount is better, but still causes oopsen (I get to a login prompt, but if I do much more than mount a disk a copy to it, the system freaks)
Daniel:
Have you tried swapping in a different stick of RAM and/or running a boot-time memory tester? Does it boot on 2.2 or any other OSs?
I had a problem like this once before - turned out one of the two 128MB CAS2 modules were bad. I replaced it and 2.4 booted wonderfully.
Good Luck,
- Dave
[email protected]
----- Original Message -----
From: "Daniel Fraley" <[email protected]>
To: <[email protected]>
Sent: Sunday, June 24, 2001 2:51 PM
Subject: Crash on boot (2.4.5)
Quoted 1 line
Hi, everyone.. I'm borrowing my roommate's email, so please send replies
to
Quoted 4 lines
[email protected]. Thanks!
Here's my problem... when I boot anything 2.4, I get several oopsen in a row, all of which are either (most commonly) kernel paging request could
not
Quoted 14 lines
be handled, or (much less common) unable to handle kernel Null pointer dereference. I will send any info on request, but here's my hardware and kernel config:
iWill KKR-266R (Via 8363 Northbridge, 686B south)
AMD tbird 1GHz
256MB cas2 pc133 sdram
ATI Radeon DDR 64MB VIVO
Kingston KNE120TX (Realtek 8139 chip)
SBLive! 5.1
IBM GXP75 30GB (on the via ide controller)
Pioneer 16x dvd
ls120
Quoted 1 line
This happens regardless if I turn on swap or not. When swap is on, it is
a
Quoted 2 lines
128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I believe I read somewhere that someone was working on that, and I didn't
want
Quoted 8 lines
to waste the extra 384MB on swap).
Is there anything I can do to fix this?
-- andyw
p.s., booting with devfs=nomount is better, but still causes oopsen (I get to a login prompt, but if I do much more than mount a disk a copy to it,
the
Quoted 4 lines
system freaks)
Quoted 26 lines · Daniel Fraley
Hi, everyone.. I'm borrowing my roommate's email, so please send replies to [email protected]. Thanks!
Here's my problem... when I boot anything 2.4, I get several oopsen in a row, all of which are either (most commonly) kernel paging request could not be handled, or (much less common) unable to handle kernel Null pointer dereference. I will send any info on request, but here's my hardware and kernel config:
iWill KKR-266R (Via 8363 Northbridge, 686B south)
AMD tbird 1GHz
256MB cas2 pc133 sdram
ATI Radeon DDR 64MB VIVO
Kingston KNE120TX (Realtek 8139 chip)
SBLive! 5.1
IBM GXP75 30GB (on the via ide controller)
Pioneer 16x dvd
ls120This happens regardless if I turn on swap or not. When swap is on, it is a 128MB partition (and yes, I'm aware of the recommendation of 2x RAM, but I believe I read somewhere that someone was working on that, and I didn't want to waste the extra 384MB on swap).
Is there anything I can do to fix this?
Quoted 7 lines
-- andyw
p.s., booting with devfs=nomount is better, but still causes oopsen (I get to a login prompt, but if I do much more than mount a disk a copy to it, the system freaks)
From the look of things, you're being bitten by the VIA southbridge
problem. As I've gathered, its some sort of interaction with that chip and the 3DNow! fast copy routines the kernel uses.
If you compile the kernel for a 686, does the problem go away? What about 586 or lower? If so, I believe there are some people working on finding common aspects of the hardware that experience this problem, though I don't remember who. You should get in contact with them, or they might get into contact with you.
Good luck on working this out.
Signature · 3 lines
-Steven In a time of universal deceit, telling the truth is a revolutionary act. -- George Orwell