From: Vincent Hanquez <tab@crans.org>
To: Eric Altendorf <EricAltendorf@orst.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.25: spurious 8259A interrupt: IRQ7
Date: Tue, 30 Jul 2002 19:59:33 +0200 [thread overview]
Message-ID: <20020730175932.GA29379@darwin.crans.org> (raw)
In-Reply-To: <200207300952.28460.EricAltendorf@orst.edu>
On Tue, Jul 30, 2002 at 09:52:28AM -0700, Eric Altendorf wrote:
>
> This is my first time trying to report a kernel problem, so I have no
> idea if I'm doing it the right way or not. I also don't understand
> the problem; maybe it's my own fault. Here it goes, though:
This is my first time trying to answer to a kernel report problem :)
> [1.] One line summary of the problem:
>
> spurious 8259A interrupt: IRQ7. (during heavy disk reads)
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.
--
Tab
next prev parent reply other threads:[~2002-07-30 17:56 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 [this message]
2002-07-30 17:42 ` Eric Altendorf
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=20020730175932.GA29379@darwin.crans.org \
--to=tab@crans.org \
--cc=EricAltendorf@orst.edu \
--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