<0>Kernel panic: Aiee, killing interupt handler!

<0>Kernel panic: Aiee, killing interupt handler!

Post by davidwr » Mon, 04 Nov 2002 01:38:45



Last night all was well, this morning -> no boot.

<exerpt>
ds: 0018   es: 0018    ss: 0018
Process insmod (pid:  220,  stackpage=c05b1000)
Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
       3 more lines of address',...

Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>] [<c0101a08a>]
            7 more lines of [<address>]

            7 more lines of [<address>]

Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
 <0>Kernel paniv: Aiee, killing interupt handler!
In interrupt handler - not syncing

I have been able to reboot, enter runlevel 0 fsck / and work that way but i
can not boot cold, i will not get by problem.

I have not experienced this before, any ideas?

TIA
--
-david

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by Grahame Kell » Mon, 04 Nov 2002 05:50:59



> Last night all was well, this morning -> no boot.

> <exerpt>
> ds: 0018   es: 0018    ss: 0018
> Process insmod (pid:  220,  stackpage=c05b1000)
> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
>        3 more lines of address',...

> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
> [<c0101a08a>]
>             7 more lines of [<address>]

>             7 more lines of [<address>]

> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
>  <0>Kernel paniv: Aiee, killing interupt handler!
> In interrupt handler - not syncing

> I have been able to reboot, enter runlevel 0 fsck / and work that way but
> i can not boot cold, i will not get by problem.

> I have not experienced this before, any ideas?

> TIA

Hi.

I suggest that you modify your BIOS (if possible) to use XT-PIC
interrupts rather than APIC (Advance PIC). If you can't mod your
BIOS to do this, then boot Linux with the following boot directive
"acpi=off".

To check if your got XT-PIC or APIC interrupts you can see by looking
at /proc/interrupts and dmesg.

--
Cheers.
Grahame (at) Wildpossum (dot) com

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by Bill Unr » Mon, 04 Nov 2002 09:04:08


]> Last night all was well, this morning -> no boot.
]>
]> <exerpt>
]> ds: 0018   es: 0018    ss: 0018
]> Process insmod (pid:  220,  stackpage=c05b1000)
]> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
]>        3 more lines of address',...
]>
]> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
]> [<c0101a08a>]
]>             7 more lines of [<address>]
]>
]>             7 more lines of [<address>]
]>
]> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
]>  <0>Kernel paniv: Aiee, killing interupt handler!
]> In interrupt handler - not syncing
]>
]> I have been able to reboot, enter runlevel 0 fsck / and work that way but
]> i can not boot cold, i will not get by problem.
]>
]> I have not experienced this before, any ideas?
]>
]> TIA

]Hi.

]I suggest that you modify your BIOS (if possible) to use XT-PIC
]interrupts rather than APIC (Advance PIC). If you can't mod your
]BIOS to do this, then boot Linux with the following boot directive
]"acpi=off".

]To check if your got XT-PIC or APIC interrupts you can see by looking
]at /proc/interrupts and dmesg.

OK, this is weird. I have been having a steadily worsening problem with
this same sort of thing. It started off by a freeze in X (I left X up
permanantly) every week or so, which got more frequent. Then in console
mode I would get a similar panic to the above. Then in cosole mode I
would get a problem running other programs. In each end every case that
I could see the error output, I got a
Unable to handle kernel Null Pointer dereference at virtual address
00000018.
Also teh ds,es,ss registers all had 0018 in them just as does the above
user's problem. the processes varied. egrep, less, run-parts would give
it ( but would not crash the machine), but then swapper would get it,
and would definitely crash the machine with the same Kernel Panic error
message as abouve.

I assumed it is hardware. I replaced the cpu (550MHz PIII-> 400MHz PII)
and got the same problem. I replaced the memory, an got the same
problem.

t goto, it is either some motherboard fault (why are we all getting those
virtual address 18 problems?--),
(Just got another one while typing this in crond this time.) Again
000018 EIP: 0010 EFLAGS:00010013
)
Or it is some problem in Linux
(kernel 2.4.8-32mdk Mandrake 8.1,)
or it is some hacker who has gotten in and is playing real games with
the kernel.

HELP.

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by davidwr » Mon, 04 Nov 2002 09:44:15




>> Last night all was well, this morning -> no boot.

>> <exerpt>
>> ds: 0018   es: 0018    ss: 0018
>> Process insmod (pid:  220,  stackpage=c05b1000)
>> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
>>        3 more lines of address',...

>> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
>> [<c0101a08a>]
>>             7 more lines of [<address>]

>>             7 more lines of [<address>]

>> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
>>  <0>Kernel paniv: Aiee, killing interupt handler!
>> In interrupt handler - not syncing

>> I have been able to reboot, enter runlevel 0 fsck / and work that way but
>> i can not boot cold, i will not get by problem.

>> I have not experienced this before, any ideas?

>> TIA

> Hi.

> I suggest that you modify your BIOS (if possible) to use XT-PIC
> interrupts rather than APIC (Advance PIC). If you can't mod your
> BIOS to do this, then boot Linux with the following boot directive
> "acpi=off".

> To check if your got XT-PIC or APIC interrupts you can see by looking
> at /proc/interrupts and dmesg.

Grahame,
thanks for the reply. Of course my bios doesn't support the option.
I have never booted with a directive before, i assume you append it to the
boot prompt?
boot>linux acpi=off   (?)
could i put that in lilo? i tried adding it (to lilo), it doesn't recognize
acpi.

In the meantime the problem appears to be either a module, or nfs or other
issue. I told inittab to boot to runlevel 1. and turned off networking,
portmap, mountnfs, and ifupdown, in rcS. it booted fine, then i initiated
runlevel 2, networking and all runlevel 2 sciprts started up fine.

I would really like to know what the real problem is and why i haven't had
any warnings, or signs (well, that i know off,...)

Thanks again

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by davidwr » Mon, 04 Nov 2002 10:30:20





> ]> Last night all was well, this morning -> no boot.
> ]>
> ]> <exerpt>
> ]> ds: 0018   es: 0018    ss: 0018
> ]> Process insmod (pid:  220,  stackpage=c05b1000)
> ]> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
> ]>        3 more lines of address',...
> ]>
> ]> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
> ]> [<c0101a08a>]
> ]>             7 more lines of [<address>]
> ]>
> ]>             7 more lines of [<address>]
> ]>
> ]> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
> ]>  <0>Kernel paniv: Aiee, killing interupt handler!
> ]> In interrupt handler - not syncing
> ]>
> ]> I have been able to reboot, enter runlevel 0 fsck / and work that way
> but ]> i can not boot cold, i will not get by problem.
> ]>
> ]> I have not experienced this before, any ideas?
> ]>
> ]> TIA

> ]Hi.

> ]I suggest that you modify your BIOS (if possible) to use XT-PIC
> ]interrupts rather than APIC (Advance PIC). If you can't mod your
> ]BIOS to do this, then boot Linux with the following boot directive
> ]"acpi=off".

> ]To check if your got XT-PIC or APIC interrupts you can see by looking
> ]at /proc/interrupts and dmesg.

> OK, this is weird. I have been having a steadily worsening problem with
> this same sort of thing. It started off by a freeze in X (I left X up
> permanantly) every week or so, which got more frequent. Then in console
> mode I would get a similar panic to the above. Then in cosole mode I
> would get a problem running other programs. In each end every case that
> I could see the error output, I got a
> Unable to handle kernel Null Pointer dereference at virtual address
> 00000018.
> Also teh ds,es,ss registers all had 0018 in them just as does the above
> user's problem. the processes varied. egrep, less, run-parts would give
> it ( but would not crash the machine), but then swapper would get it,
> and would definitely crash the machine with the same Kernel Panic error
> message as abouve.

> I assumed it is hardware. I replaced the cpu (550MHz PIII-> 400MHz PII)
> and got the same problem. I replaced the memory, an got the same
> problem.

> t goto, it is either some motherboard fault (why are we all getting those
> virtual address 18 problems?--),
> (Just got another one while typing this in crond this time.) Again
> 000018 EIP: 0010 EFLAGS:00010013
> )
> Or it is some problem in Linux
> (kernel 2.4.8-32mdk Mandrake 8.1,)
> or it is some hacker who has gotten in and is playing real games with
> the kernel.

> HELP.

Bill,

Interesting, i don't know if we're experiencing the same thing but it does
have similiarities, if so it's definately not your processor or memory but
may be a motherboard issue (the machine in question is a toshiba laptop
with a pent mmx 266 MHz processor with 32 mb ram). I don't run X, so i
can't share any of your "kernel Null Pointer dereference's" but i do get:
ide1: unexpected interrupt, status=0x51, count=1
alot, it will just pop up at random times, at prompt's within `vi', within
`less' or `man', it doesn't seem to have a negative effect on anything, it
just displays to the screen (stderr).  

It would be great to get some answer's on this.

--david

to reply axe _SPAM_BLOWS_

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by baskitcais » Mon, 04 Nov 2002 11:52:11






>> ]> Last night all was well, this morning -> no boot.
>> ]>
>> ]> <exerpt>
>> ]> ds: 0018   es: 0018    ss: 0018
>> ]> Process insmod (pid:  220,  stackpage=c05b1000)
>> ]> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
>> ]>        3 more lines of address',...
>> ]>
>> ]> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
>> ]> [<c0101a08a>]
>> ]>             7 more lines of [<address>]
>> ]>
>> ]>             7 more lines of [<address>]
>> ]>
>> ]> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
>> ]>  <0>Kernel paniv: Aiee, killing interupt handler!
>> ]> In interrupt handler - not syncing
>> ]>
>> ]> I have been able to reboot, enter runlevel 0 fsck / and work that way
>> but ]> i can not boot cold, i will not get by problem.
>> ]>
>> ]> I have not experienced this before, any ideas?
>> ]>
>> ]> TIA

>> ]Hi.

>> ]I suggest that you modify your BIOS (if possible) to use XT-PIC
>> ]interrupts rather than APIC (Advance PIC). If you can't mod your
>> ]BIOS to do this, then boot Linux with the following boot directive
>> ]"acpi=off".

>> ]To check if your got XT-PIC or APIC interrupts you can see by looking
>> ]at /proc/interrupts and dmesg.

>> OK, this is weird. I have been having a steadily worsening problem with
>> this same sort of thing. It started off by a freeze in X (I left X up
>> permanantly) every week or so, which got more frequent. Then in console
>> mode I would get a similar panic to the above. Then in cosole mode I
>> would get a problem running other programs. In each end every case that
>> I could see the error output, I got a
>> Unable to handle kernel Null Pointer dereference at virtual address
>> 00000018.
>> Also teh ds,es,ss registers all had 0018 in them just as does the above
>> user's problem. the processes varied. egrep, less, run-parts would give
>> it ( but would not crash the machine), but then swapper would get it,
>> and would definitely crash the machine with the same Kernel Panic error
>> message as abouve.

>> I assumed it is hardware. I replaced the cpu (550MHz PIII-> 400MHz PII)
>> and got the same problem. I replaced the memory, an got the same
>> problem.

>> t goto, it is either some motherboard fault (why are we all getting those
>> virtual address 18 problems?--),
>> (Just got another one while typing this in crond this time.) Again
>> 000018 EIP: 0010 EFLAGS:00010013
>> )
>> Or it is some problem in Linux
>> (kernel 2.4.8-32mdk Mandrake 8.1,)
>> or it is some hacker who has gotten in and is playing real games with
>> the kernel.

>> HELP.

> Bill,

> Interesting, i don't know if we're experiencing the same thing but it does
> have similiarities, if so it's definately not your processor or memory but
> may be a motherboard issue (the machine in question is a toshiba laptop
> with a pent mmx 266 MHz processor with 32 mb ram). I don't run X, so i
> can't share any of your "kernel Null Pointer dereference's" but i do get:
> ide1: unexpected interrupt, status=0x51, count=1
> alot, it will just pop up at random times, at prompt's within `vi', within
> `less' or `man', it doesn't seem to have a negative effect on anything, it
> just displays to the screen (stderr).

> It would be great to get some answer's on this.

> --david

> to reply axe _SPAM_BLOWS_

Bill,

How old is the power supply? if it on its way out or maybe the regulators on
the board are getting a bit old it can have this affect.


that started showing the same sort of probs, I monitored it with lm-sensors
and the 5v rail was down to 4.55v, replaced board and all is well again

--
Cheers
Mark
Nil iligitum carborundum

 
 
 

<0>Kernel panic: Aiee, killing interupt handler!

Post by Grahame Kell » Mon, 04 Nov 2002 14:27:32







>>> ]> Last night all was well, this morning -> no boot.
>>> ]>
>>> ]> <exerpt>
>>> ]> ds: 0018   es: 0018    ss: 0018
>>> ]> Process insmod (pid:  220,  stackpage=c05b1000)
>>> ]> Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
>>> ]>        3 more lines of address',...
>>> ]>
>>> ]> Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>]
>>> ]> [<c0101a08a>]
>>> ]>             7 more lines of [<address>]
>>> ]>
>>> ]>             7 more lines of [<address>]
>>> ]>
>>> ]> Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
>>> ]>  <0>Kernel paniv: Aiee, killing interupt handler!
>>> ]> In interrupt handler - not syncing
>>> ]>
>>> ]> I have been able to reboot, enter runlevel 0 fsck / and work that way
>>> but ]> i can not boot cold, i will not get by problem.
>>> ]>
>>> ]> I have not experienced this before, any ideas?
>>> ]>
>>> ]> TIA

>>> ]Hi.

>>> ]I suggest that you modify your BIOS (if possible) to use XT-PIC
>>> ]interrupts rather than APIC (Advance PIC). If you can't mod your
>>> ]BIOS to do this, then boot Linux with the following boot directive
>>> ]"acpi=off".

>>> ]To check if your got XT-PIC or APIC interrupts you can see by looking
>>> ]at /proc/interrupts and dmesg.

>>> OK, this is weird. I have been having a steadily worsening problem with
>>> this same sort of thing. It started off by a freeze in X (I left X up
>>> permanantly) every week or so, which got more frequent. Then in console
>>> mode I would get a similar panic to the above. Then in cosole mode I
>>> would get a problem running other programs. In each end every case that
>>> I could see the error output, I got a
>>> Unable to handle kernel Null Pointer dereference at virtual address
>>> 00000018.
>>> Also teh ds,es,ss registers all had 0018 in them just as does the above
>>> user's problem. the processes varied. egrep, less, run-parts would give
>>> it ( but would not crash the machine), but then swapper would get it,
>>> and would definitely crash the machine with the same Kernel Panic error
>>> message as abouve.

>>> I assumed it is hardware. I replaced the cpu (550MHz PIII-> 400MHz PII)
>>> and got the same problem. I replaced the memory, an got the same
>>> problem.

>>> t goto, it is either some motherboard fault (why are we all getting
>>> those virtual address 18 problems?--),
>>> (Just got another one while typing this in crond this time.) Again
>>> 000018 EIP: 0010 EFLAGS:00010013
>>> )
>>> Or it is some problem in Linux
>>> (kernel 2.4.8-32mdk Mandrake 8.1,)
>>> or it is some hacker who has gotten in and is playing real games with
>>> the kernel.

>>> HELP.

>> Bill,

>> Interesting, i don't know if we're experiencing the same thing but it
>> does have similiarities, if so it's definately not your processor or
>> memory but may be a motherboard issue (the machine in question is a
>> toshiba laptop with a pent mmx 266 MHz processor with 32 mb ram). I don't
>> run X, so i can't share any of your "kernel Null Pointer dereference's"
>> but i do get: ide1: unexpected interrupt, status=0x51, count=1
>> alot, it will just pop up at random times, at prompt's within `vi',
>> within `less' or `man', it doesn't seem to have a negative effect on
>> anything, it just displays to the screen (stderr).

>> It would be great to get some answer's on this.

>> --david

>> to reply axe _SPAM_BLOWS_

> Bill,

> How old is the power supply? if it on its way out or maybe the regulators
> on the board are getting a bit old it can have this affect.


> ) that started showing the same sort of probs, I monitored it with
> lm-sensors and the 5v rail was down to 4.55v, replaced board and all is
> well again

Hi guys.

Boot using "safe mode" (if your running SuSE - which I do) or
use the lilo directive at boot time to disable APIC and IDE DMA.
which is of course is distribution specific on how you may do this.

I suspect that IDE/DMA is a no no with your systems (it is with my
laptop too), and my motherboards on five system (PIII mostly all
have issues with APIC and MUST run in XTPIC mode, some with IDE/DMA
and APIC modes).

Before booting, deselect all but the very basic requirements in
/etc/rc.d/rc[35].d run modes to limit the problem area.
Initially only boot into Single user mode, and disable
individual services and see what happens, otherwise
boot into level 3 (SuSE) non X mode and check everything is AOK
before proceeding to level 5 (X mode). Look at all the logs
/var/log/* especially /var/log/messages and your X logs.

As I only have SuSE, you'll have to RTFM for your distribution /
release.

Hope this is of some help.
--
Cheers.
Grahame (at) Wildpossum (dot) com

 
 
 

1. RH7.1 Install -->Kernel panic: Aiee, killing interrupt handler!

I'm trying to install RH7.1 on a machine that was previously running
RH6.0 just fine.  However I don't get very far in the install before
running into a Kernel panic.  Does anyone have any information as to
what this might mean?

Any and all help gratefully appreciated. Thanks in advance.  Here is the
script of what happens...

<<boot from floppy>>
boot: text
Loading initrd.img...........
Loading vmlinuz.......
Uncompress <<boot messages scroll by>>
Running /sbin/loader
Loading tmscsim driver
Running anaconda - please wait...
<<prompt>>Language Selection: English
<<prompt>>Keyboard Selection: us
<<prompt>>Installationg Type: Workstation
<<within 1 second this appears>>
               Oops: 0002
CPU:    0
EIP:    0010:[<c482fe37>]
EFLAGS: 00010006
eax: 00000000   ebx: c3f020f4   ecx: 00000081   edx: 000bff0c
esi: c1117a10   edi: 00000080   ebp: c3f02078   esp: c0241f14F12> next
screen
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 0, stackpage=c0241000)
Stack: c0241f47 c3f020f4 c3f02078 000000c9 c482f4d6 c3f02078 c3f020f4
00000080
        c3f02078 c3f020f4 c0241f47 00000282 9128cb40 c017db29 c3f10060
00000002
        c480b1a0 c1116980 04000001 0000000b c0241fac c010a019 0000000b
c3f02078
Call Trace: [<c482f4d6>] [<c017db29>] [<c480b1a0>] [<c010a019>]
[<c010a168>] [<c0107210>] [<c0108f58>]
        [<c0107210>] [<c0107233>] [<c010729a>] [<c0100191>]
Code: 80 60 27 fe 85 f6 0f 84 9f 00 00 00 80 4e 27 02 e9 96 00 00
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

-Randy Galbraith

2. Xnest as a security wrapper?

3. Aiee, killing interupt handler (when installing redhat 6.0,slackware,anything)

4. Vidéo card ATI RAGE FURY 32Mo

5. Aiee, killing interupt handler

6. S built?

7. aiee, killed interrupt handler - kernel panic

8. ide/udma hard disks

9. Kernel panic: Aiee, killing interrupt handler!

10. Kernel panic:Aiee killing interrupt handler

11. 2.4.5 Kernel panic: Aiee, killing interrupt handler!

12. Kernel panic, "Aiee, killing interrupt handler!"

13. SMP aic7xxx 2.4.3 boot panic: Aiee, killing interrupt handler