Kernel panic: Aiee, killing handler!

shazhangwa · 09-20-2016, 02:20 AM

Computer can't start with below error:
code: 0f 0b 89 7c 24 04 c7 04 24 01 00 00 00 8b 44 24 04 25 f0 01
Kernel panic: Aiee, killing handler! Ininterrupt handler - not syncing

TKS

ardvark71 · 09-20-2016, 03:44 AM

Hello and welcome to the forum

Please note this forum is for introductions only. I have asked a moderator to move your thread to an appropriate forum.

Regards...

rtmistler · 09-20-2016, 07:37 AM

Welcome to LQ!

Quote:

Originally Posted by shazhangwa

Computer can't start with below error:
code: 0f 0b 89 7c 24 04 c7 04 24 01 00 00 00 8b 44 24 04 25 f0 01
Kernel panic: Aiee, killing handler! Ininterrupt handler - not syncing

I submit that THIS is one of the reasons why people throw their hands up in frustration at stuff!

Cryptic code.
Joking in the statement "Aiee"
Misspelling

@shazhangwa: Please add the distribution you are trying, the version of that distribution, whether or not you're using the standard kernel or a custom built one. Please also explain the specifications for the hardware which you are trying to run this on.

ardvark71 · 09-20-2016, 10:05 AM

Quote:

Originally Posted by shazhangwa

Computer can't start with below error:
code: 0f 0b 89 7c 24 04 c7 04 24 01 00 00 00 8b 44 24 04 25 f0 01
Kernel panic: Aiee, killing handler! Ininterrupt handler - not syncing

Hi...

In addition to what rtmistler has requested, you might want to run memtest86 to see if any of your memory modules have gone bad.

While the reasons mentioned may not be the ones responsible in your case, I did find a couple threads on the subject here and here.

Regards...

sundialsvcs · 09-20-2016, 03:48 PM

Actually, every operating system has some number of "kernel panic / BSOD / suddendeath" messages: situations that cannot possibly happen but that just did, such that the operating system cannot continue to function at all.

They also have counterparts to the "Oops" messages, which log non-fatal operating system errors.

rtmistler · 09-21-2016, 07:18 AM

Quote:

Originally Posted by sundialsvcs

Actually, every operating system has some number of "kernel panic / BSOD / suddendeath" messages: situations that cannot possibly happen but that just did, such that the operating system cannot continue to function at all.

They also have counterparts to the "Oops" messages, which log non-fatal operating system errors.

Yes however I feel it is inadequate to provide "funny" details when a critical fault has occurred. Either offer diagnostic information which possibly can be useful, or not. One obviously had the time to code a joke and include a misspelling, as well as a hex string. Probably better to post that hex string and cite that it should be reported to blah-blah.org/com or at least attempt something.

jostber · 09-21-2016, 03:39 PM

Some input here:

Troubleshoot Linux Kernel Panics – Linux Shtuff

http://g33kinfo.com/info/archives/492

keefaz · 09-21-2016, 04:20 PM

Quote:

Originally Posted by rtmistler

Yes however I feel it is inadequate to provide "funny" details when a critical fault has occurred. Either offer diagnostic information which possibly can be useful, or not. One obviously had the time to code a joke and include a misspelling, as well as a hex string. Probably better to post that hex string and cite that it should be reported to blah-blah.org/com or at least attempt something.

Maybe it's supposed to be easy to catch (grep) the error line in source code.

Code:

$ cd /lib/modules/`uname -r`/source
$ grep -rln 'Aiee, killing handler'
$ 
$ grep -rln 'Aiee, killing'
./arch/x86/boot/compressed/vmlinux.bin
./kernel/exit.c
./kernel/exit.o
./kernel/built-in.o
./.tmp_vmlinux1
./.tmp_vmlinux2
./vmlinux.o
./vmlinux
$ cat kernel/exit.c
..
        if (unlikely(in_interrupt()))
                panic("Aiee, killing interrupt handler!");
...

sundialsvcs · 09-21-2016, 05:49 PM

And ... well ... "Meh ... lighten up, willya?"

If you look through the source code of any application, you will find, tucked-away somewhere, both "unprintable

things" and "little bits of trivia and esoterica."

The person who wrote that message sincerely hoped that you would never see it on your computer screen, because the circumstances that would cause it to occur "are never supposed to happen ... but they just did."

They're not cracking jokes, and they're not making light of the situation. They're writing source code. Millions and millions of lines of it. By hand.