[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Kernel panic
The message itself indicates that do_exit (kernel/exit.c) has
been called with interrupts disabled. Normally this happens
after a kernel oops (arch/cris/mm/fault.c).
The number of calls to do_exit in the kernel is rather
limited so maybe you could add a printk before each
and see which one that occurs. Obviosuly you don't
need to modify files under arch/i386 etc.
Does this happen every time? Does it happen at startup
or later? Can you connect it to some other event (e.g.
it happens when you load a module).
From: email@example.com">mailto:firstname.lastname@example.org] On
Behalf Of Uwe Reimann
Sent: Friday, October 24, 2003 7:55 AM
To: Mikael Starvik
Subject: RE: Kernel panic
no, I'm sorry. The syslog doesn't contain anything related to the panic.
Those two lines, that were printed on the console, are all I have.
Best regards, Uwe
Am Fre, den 24.10.2003 schrieb Mikael Starvik um 07:19:
> The interresting output is probably before the lines you sent. Can
> you cut out more information from the debug log?
> The messages you sent means that something unexpected happened
> with interrupts disabled but it doesn't tell me what the
> unexpected thing was.
> -----Original Message-----
> From: email@example.com">mailto:firstname.lastname@example.org] On
> Behalf Of Uwe Reimann
> Sent: Thursday, October 23, 2003 8:57 PM
> To: dev-etrax
> Subject: Kernel panic
> anybody ever encountered that kernel-panic and knows what could be
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
> I am using linux-2.4.19 plus linux-2.4.19.diff from axis.
> Best regards, Uwe