On Sat, 16 Sep 2000, Harley Anderson wrote:

> I was just sitting here reading a page in lynx that I grabbed yesterday and got
> spammed by 2 or 3 oopsies..
> The machine had been up for approximately 44 hours with fairly light load.
> Only caught the bottom of the 1st or second one but it had
> 
>   kernel BUG at page_alloc.c:194!

If I'm not mistaken, this is a BAD_RANGE check,
indicating that a page hasn't been filed away
in the right memory zone...

> at the bottom. The next one was from the startup script from my
> ROM mud segfaulting,

Sounds like memory corruption ...

> Right after this I flicked to another VC (already logged in as
> root), I think I tried to do a ps, but then got this monster:

[snip bad oops]


This sounds like either some bit errors in memory
(memtest86 will find those), or a device driver
scribbling over memory, or the memory not being
refreshed or operated at the right speed (memory
to slow for the speed you're running it at?)...

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/               http://www.surriel.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to