From: linas@austin.ibm.com
To: linux-kernel@vger.kernel.org
Subject: panic and timer interrupts?
Date: Tue, 1 Jul 2003 10:38:27 -0500 [thread overview]
Message-ID: <20030701103827.A24070@forte.austin.ibm.com> (raw)
I've got a machine here that just did one of the stranger kernel
things I've ever seen. Due to some bug, it panic'ed. But then, during
the panic, it took a timer interrupt, and then handled some network
interrupts, handled some network data, and seems to maybe even have
scheduled some user-land processes before getting hoplessly tangled up.
So, my naive kernel questions as follows: I would have thought that
interrupts would be disabled during a panic, but I can't find any code
that does this. Why is this? Is this a bug? Is this intentional?
It got me to thinking about a hang mode I've seen not infrequently
on PC's: Machine is hung, unresponsive to keyboard, telnet, etc. but
does reply to pings. I've never bothered to debug those, but now I'm
wondering if that's a related manifestation.
--linas
reply other threads:[~2003-07-01 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030701103827.A24070@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--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
all inboxes | Powered by JetHome®