Re: 2.4.x kernel crashing

[Russell Hires <rhires@earthlink.net>]

Okay, accepting for the moment that when the kernel dies, I can't read the 
console to find out what went wrong, what else can I do to figure out what's 
wrong? Which kernel or other system logs would tell me? 

I do know that for some reason, heavy disk activity kills the kernel. I run 
anacron, and I know that after a few days of not being on, my computer runs a 
bunch of tasks in the background. I think that it's the "locate" database 
update that could be the culprit. But then, how would I know for sure? 

Thanks for all the help!

Russell
On Thursday 06 December 2001 04:52 pm, Michel Dänzer wrote:
> On Thu, 2001-12-06 at 01:00, Russell Hires wrote:
> > > If that was the only problem... when you're in xmon, bad things have
> > > happened and everything is interrupted. Only when you exit xmon (by
> > > entering 'x') does the system continue to run. So there is no
> > > filesystem access in xmon.
> >
> > Typing 'x' could be bad anyway, since the whole system is down. At least
> > it would allow for an orderly shutdown?
>
> If it's only an oops, yes. If it's a panic, you won't be able to do
> anything but force reboot after you exit xmon.
>
> > I've got another question related to this: could it be a hardware failure
> > on my computer's part somewhere? The kind of failure that a 2.4 kernel
> > would see, where a 2.2. kernel wouldn't?
>
> I rather doubt that. I could imagine one kernel showing hardware
> problems more than another, but not that one does and the other not at
> all.