Howdy again folks, I have another oops for ya's to look over...
Yesterday when I was about to patch and build the new (test12) kernel I found
the ominous message:
Kernel panic: attempted to kill init!
Something like that anyway. No other info, just locked up solid.
No real clues on that one
Howdy again folks, I have another oops for ya's to look over...
Yesterday when I was about to patch and build the new (test12) kernel I found
the ominous message:
Kernel panic: attempted to kill init!
Something like that anyway. No other info, just locked up solid.
No real clues on that one
> 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?)...
Hmm, Andrew just informed me that the
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!
at the bottom. The
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!
at the bottom. The
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?)...
Hmm, Andrew just informed me that the rtl8139
The other day I got the patch for 2.2.17 and after just over a day of normal
operation, while my sister was playing kpat (KDE solitaire) yesterday
afternoon, X died and dropped her out to the console.
After she told me about it later on I found this at the bottom of my dmesg:
CPU 0: Machine
While preparing my first ever post to lkml just now about a problem in 2.2.17
(which I will post after this hopefully), I was fortunate enough to get my
first ever oops. I was in X at the time so I was unaware of the happy occasion.
All I noticed was su segfault once or thrice and then I couldn't
While preparing my first ever post to lkml just now about a problem in 2.2.17
(which I will post after this hopefully), I was fortunate enough to get my
first ever oops. I was in X at the time so I was unaware of the happy occasion.
All I noticed was su segfault once or thrice and then I couldn't
The other day I got the patch for 2.2.17 and after just over a day of normal
operation, while my sister was playing kpat (KDE solitaire) yesterday
afternoon, X died and dropped her out to the console.
After she told me about it later on I found this at the bottom of my dmesg:
CPU 0: Machine
10 matches
Mail list logo
