From: Jan-Frode Myklebust <janfrode@ii.uib.no>
To: linux-kernel@vger.kernel.org
Subject: spurious APIC interrupt on CPU#0
Date: Mon, 9 Apr 2001 11:43:51 +0200 [thread overview]
Message-ID: <20010409114351.A18170@ii.uib.no> (raw)
I just had a (quite) hard hang with 2.4.3-XFS (cvs from oss.sgi.com).
The machine got totally unresponsive in X, and it barely managed to execute
any commands from the serial console. After issuing a reboot, and waiting
for quite some time, I flipped the powerswitch.
Frm the syslog it looks like it started with:
kernel: spurious APIC interrupt on CPU#0, should never happen.
then there's repeated messages like:
kernel: NETDEV WATCHDOG: eth0: transmit timed out
kernel: ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
kernel: hdc: lost interrupt
This was on a K6-2, kernel config and hardware information available upon
request.
-jf
reply other threads:[~2001-04-09 10:46 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=20010409114351.A18170@ii.uib.no \
--to=janfrode@ii.uib.no \
--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®