From: Len Brown <lenb@kernel.org>
To: Zach <netrek@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: spurious kernel error
Date: Fri, 30 Mar 2007 15:25:06 -0400 [thread overview]
Message-ID: <200703301525.06460.lenb@kernel.org> (raw)
In-Reply-To: <ecfa260c0703300036u5d82389apaaa735ba7de5a3bb@mail.gmail.com>
On Friday 30 March 2007 03:36, Zach wrote:
> kern.log:Mar 29 23:44:36 netrek kernel: spurious 8259A interrupt: IRQ7.
A spurious interrupt isn't necessarily a "spurious kernel error",
it means that the kernel went to service an interrupt and didn't
find any sources. In PIC mode, these are registered on IRQ7.
Could be a race condition in a device driver
that is exposed from multiple drivers sharing the same IRQ.
-Len
prev parent reply other threads:[~2007-03-30 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 7:36 spurious kernel error Zach
2007-03-30 19:25 ` Len Brown [this message]
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=200703301525.06460.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netrek@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.