From: Jesper Juhl <jesper.juhl@gmail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: spurious 8259A interrupt: IRQ7
Date: Mon, 23 May 2005 00:41:21 +0200 [thread overview]
Message-ID: <9a874849050522154157cf7457@mail.gmail.com> (raw)
In-Reply-To: <1113512638.22496.47.camel@eeyore>
On 4/14/05, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Thu, 2005-04-14 at 16:56 -0400, Lee Revell wrote:
> > Is the VIA IRQ fixup related to the "spurious interrupts" messages in
> > any way? Googling the 2.4 threads on the issue gave me the impression
> > that it's related to broken hardware. I think excessive disk activity
> > might trigger it.
>
> If you need the VIA IRQ fixup and don't have it, I would expect
> some interrupt to be routed to the wrong IRQ. That might give
> you a "spurious interrupt" on the wrong IRQ, but your device would
> probably just not work at all.
>
For what it's worth I'll chime in with my own info on this subject.
I also see the
spurious 8259A interrupt: IRQ7.
messages from time to time. Actually I got one just a little while ago :
$ dmesg | grep spurious
[18994.222451] spurious 8259A interrupt: IRQ7.
The system seems to be in good shape - it has never caused me any
actual trouble.
As for the via irq fixup I see this :
$ dmesg | grep -i fixup
[ 74.629393] PCI: Via PIC IRQ fixup for 0000:00:09.0, from 255 to 3
The hardware is a ASUS A7M266 mobo with a AMD Athlon (t-bird) 1.4GHz CPU.
The kernel is 2.6.12-rc4-mm2 :
$ uname -a
Linux dragon 2.6.12-rc4-mm2 #2 Mon May 16 18:14:13 CEST 2005 i686
unknown unknown GNU/Linux
I've seen some references to APIC for this issue, so here are the APIC
related settings in my .config :
juhl@dragon:~/download/kernel/linux-2.6.12-rc4-mm2$ grep -i APIC .config
CONFIG_X86_GOOD_APIC=y
# CONFIG_X86_UP_APIC is not set
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-05-22 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 17:11 spurious 8259A interrupt: IRQ7 Lee Revell
2005-04-14 20:43 ` Bjorn Helgaas
2005-04-14 20:56 ` Lee Revell
2005-04-14 21:03 ` Bjorn Helgaas
2005-05-22 22:41 ` Jesper Juhl [this message]
-- 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=9a874849050522154157cf7457@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox