From: Daniel Mundy <djmunds@gmx.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Kernel panic, "Aiee, killing interrupt handler!"
Date: Wed, 3 Apr 2002 18:41:02 +0930 [thread overview]
Message-ID: <20020403091102.GA1492@gmx.net> (raw)
Lately I have had my box freeze up just after connecting, although it
doesn't happen every time.. I am not sure exactly what the factors are
that make it crash.
When I was having the freezes yesterday I watched syslog from a terminal
and wrote down some of the output on paper (I did a search in my syslog
file just now and it I don't have any of this... maybe because the data
was still in cache and didn't get written to disk?):
--
PPP BSD Compresseion module registered
PPP Deflate Compression module registered
Unable to handle kernel paging requestat virtual address 010000a
printing eip:
010000a
*pde = 00000000
Oops: 0000
CPU: 0
EIP
--
...this is where I stopped writing, was further debugging messages. They
would have been no use to me but at the time I wasn't considering
writing to this list, now I am thinking maybe they would have been
useful... I got a bit more of the messages though:
--
Code: Bad EIP value.
<0>Kernel panicL Aiee, killing interrupt handler!
In interrupt handler - not syncing
--
I also noticed a weird startup message, although I have no idea whether
this is related:
--
/etc/init.d/rc: line 6: 180 Segmentation fault $debug "$@"
--
One other message I see in syslog a few times, and also am not sure
whether it is related:
--
pppd[357]: Cannot determine ethernet address for proxy ARP
--
Has anyone had similar problems? I asked around a bit on IRC and I was
recommended to try asking on this list.
Regards,
Daniel Mundy
next reply other threads:[~2002-04-03 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 9:11 Daniel Mundy [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-18 21:22 Kernel panic: Aiee, killing interrupt handler! C.Backstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020403091102.GA1492@gmx.net \
--to=djmunds@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox