On Wed, 21 Dec 2005, Christopher Beppler wrote:
Debugging oopses needs skills most of us here don't possess. But, if
you have the choice, it never does any harm to disable config options
which you do not need. You might also check your logs, in case there is
a pattern to the oopses. When did you build LFS on this box, and when
did the oopses start ?
I build the LFS a week ago. But the box runs the whole day since sunday.
The oopses began monday...
That's not a very long uptime for a stable kernel :-(
Lastly, I hope you reboot each time you discover an oops - after the
first oops, all bets are off until the machine is rebooted.
No... not in every case, because I don't see them at once...
Sure, I've been there too. My point is that only the first oops after
a reboot is ever worth attempting to debug, any subsequent oopses before
you've rebooted might be caused by damage from the first oops. That's
why I said reboot after you *discover* an oops. Any processes that have
run since the first oops might be fine, or they may give bizarre
results.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
