From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: spurious 8259A interrupt: IRQ7
Date: Thu, 14 Apr 2005 13:11:32 -0400 [thread overview]
Message-ID: <1113498693.18871.11.camel@mindpipe> (raw)
I get this message occasionally on both my machines. I googled and saw
some references to this message on 2.4 but nothing for 2.6. Some of the
references were to APIC, which I don't have enabled.
Both machines are using VIA chipsets and display the "VIA IRQ fixup"
message on boot. I think this behavior started about the same time that
message started to appear.
On both machines the parallel port is disabled in the BIOS and there's
nothing on IRQ7.
Lee
next reply other threads:[~2005-04-14 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 17:11 Lee Revell [this message]
2005-04-14 20:43 ` spurious 8259A interrupt: IRQ7 Bjorn Helgaas
2005-04-14 20:56 ` Lee Revell
2005-04-14 21:03 ` Bjorn Helgaas
2005-05-22 22:41 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2006-01-15 17:11 Jiri Slaby
2006-01-15 17:21 ` Jiri Slaby
2006-01-15 21:12 ` Jan Engelhardt
2006-01-15 22:21 ` Jiri Slaby
2006-01-20 17:55 ` Jiri Slaby
2002-07-08 12:30 Petr Vandrovec
2002-07-08 9:13 Patrick Clohessy
2002-07-08 9:27 ` jbradford
2002-07-08 10:05 ` Tomas Szepe
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=1113498693.18871.11.camel@mindpipe \
--to=rlrevell@joe-job.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