I have a testing machine which I leave it on & haven't touch for months.
Today I received this error. After reboot still the same. Any idea?

<0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

CL wrote:

> I have a testing machine which I leave it on & haven't touch for months.
> Today I received this error. After reboot still the same. Any idea?
>
> <0>Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing

Well, the system paniced while it was processing an interrupt, and
therefore is not syncing disks before dieing ...

I would check disks, memory, stuff like that (perhaps the panic message
provides additional information that might be useful to determine which
interrupt handler is failing?) before anything else. If you had the
system running for a long period of time before the errors started
happening, I imagine that it's most likely a hardware failure, and disks
seem the most likely culprit.

I hope that helps ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Thx. I will try.

"Sylvain Robitaille" <syl@alcor.concordia.ca> wrote in message
news:slrnd29bqq.dv6n.syl@alcor.concordia.ca...
> CL wrote:
>
> > I have a testing machine which I leave it on & haven't touch for months.
> > Today I received this error. After reboot still the same. Any idea?
> >
> > <0>Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
>
> Well, the system paniced while it was processing an interrupt, and
> therefore is not syncing disks before dieing ...
>
> I would check disks, memory, stuff like that (perhaps the panic message
> provides additional information that might be useful to determine which
> interrupt handler is failing?) before anything else. If you had the
> system running for a long period of time before the errors started
> happening, I imagine that it's most likely a hardware failure, and disks
> seem the most likely culprit.
>
> I hope that helps ...
>
> --
> ----------------------------------------------------------------------
> Sylvain Robitaille syl@alcor.concordia.ca
>
> Systems analyst Concordia University
> Instructional & Information Technology Montreal, Quebec, Canada
> ----------------------------------------------------------------------