From: Eric Altendorf <EricAltendorf@orst.edu>
To: Vincent Hanquez <tab@crans.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.25: spurious 8259A interrupt: IRQ7
Date: Tue, 30 Jul 2002 10:42:31 -0700 [thread overview]
Message-ID: <200207301042.31667.EricAltendorf@orst.edu> (raw)
In-Reply-To: <20020730175932.GA29379@darwin.crans.org>
On Tuesday 30 July 2002 10:59, Vincent Hanquez wrote:
> There were a discussion about this warning some time ago.
> As far as I remember, it's just a interrupt which is not registered
> by any peripheral.
> this is not a kernel bug, just a buggy hardware.
OK -- I'll take that explanation. I mentioned it because it happened
in the first half hour of using this kernel specifically, and I'd
never seen it before.
Thanks,
Eric
--
"First they ignore you. Then they laugh at you.
Then they fight you. And then you win." -Gandhi
next prev parent reply other threads:[~2002-07-30 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 16:52 2.5.25: spurious 8259A interrupt: IRQ7 Eric Altendorf
2002-07-30 17:59 ` Vincent Hanquez
2002-07-30 17:42 ` Eric Altendorf [this message]
2002-07-30 21:04 ` Wade
2002-07-30 20:54 ` Eric Altendorf
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=200207301042.31667.EricAltendorf@orst.edu \
--to=ericaltendorf@orst.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tab@crans.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