From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Andreas Steinmetz <ast@domdv.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, <martin@jtrix.com (Martin A. Brooks)>
Subject: Re: "spurious 8259A interrupt: IRQ7"
Date: Tue, 27 Nov 2001 16:30:29 -0200 [thread overview]
Message-ID: <01112716302905.00872@manta> (raw)
In-Reply-To: <XFMail.20011127152007.ast@domdv.de>
In-Reply-To: <XFMail.20011127152007.ast@domdv.de>
On Tuesday 27 November 2001 12:20, Andreas Steinmetz wrote:
> As far as I remember this was talked about earlier. Different mobos,
> chipsets, processor brands, but always IRQ 7. /me wonders. At least it
> doesn't do any harm (got this message on nearly all or all of my systems).
>
> On 27-Nov-2001 Alan Cox wrote:
> >> I get this with 2.4.16 vanilla, though. IRQ 7 appears to be unassigned
> >> according to /proc/pci.
> >>
> >> Machine is a 1ghz Athlon on a VIA VT82C686 mobo and a DEC 21140 NIC.
> >>
> >> Any pointers appreciated.
> >
> > IRQ7 is asserted when the PIC sees an interrupt but nobody appears to be
> > generating it when it looks.
I see it too on my home system (Duron 650 + VIA chipset)
--
vda
next prev parent reply other threads:[~2001-11-27 14:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 10:27 "spurious 8259A interrupt: IRQ7" Martin A. Brooks
2001-11-27 13:14 ` Marek Pętlicki
2001-11-27 14:03 ` Alan Cox
2001-11-27 14:20 ` Andreas Steinmetz
2001-11-27 14:38 ` 'spurious 8259A interrupt: IRQ7' Martin A. Brooks
2001-11-27 14:41 ` Andreas Steinmetz
2001-11-27 14:52 ` Pascal Schmidt
2001-11-27 14:56 ` Bernd Bartmann
2001-11-27 15:01 ` Jan Niehusmann
2001-11-27 15:03 ` Ian Molton
2001-11-27 15:06 ` Adam Schrotenboer
2001-11-27 16:00 ` Peter Wächtler
2001-11-27 16:32 ` Pascal Schmidt
2001-11-27 17:01 ` lk
2001-11-27 16:30 ` Joachim Franek
2001-11-27 17:40 ` Tom Diehl
2001-11-27 23:56 ` Vojtech Pavlik
2001-11-28 11:08 ` Piter Punk
2001-11-28 8:55 ` Jurjen Oskam
2001-11-27 18:30 ` vda [this message]
2001-11-27 18:40 ` "spurious 8259A interrupt: IRQ7" Sebastian Dröge
2001-11-29 4:51 ` Ishan Oshadi Jayawardena
2001-11-28 17:57 ` Alan Cox
2001-11-29 10:14 ` Luca Montecchiani
[not found] <20011127234758.C5809@ftoomsh.progsoc.uts.edu.au>
2001-11-27 13:09 ` 'spurious 8259A interrupt: IRQ7' Martin A. Brooks
[not found] <E168jVk-00050O-00@core-gateway-1.hyperlink.com>
2001-11-27 14:50 ` Martin A. Brooks
2001-11-27 14:56 ` Andreas Steinmetz
2001-11-27 15:01 ` Alan Cox
2001-11-27 14:59 ` Martin A. Brooks
2001-11-27 15:04 ` Ian Molton
2001-11-27 15:04 ` Andreas Steinmetz
2001-11-27 15:17 ` Adam Schrotenboer
-- strict thread matches above, loose matches on Subject: below --
2001-11-27 15:04 mike_phillips
[not found] <1793.10.119.8.1.1006872608.squirrel@extranet.jtrix.com.suse.lists.linux.kernel>
[not found] ` <E168jk1-0001J7-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-11-27 15:08 ` Andi Kleen
2001-11-27 17:03 "spurious 8259A interrupt: IRQ7" bart
2001-11-27 17:11 ` Luigi Genoni
2001-11-27 17:06 'spurious 8259A interrupt: IRQ7' Alex Davis
2001-11-28 0:01 ` Peter Bornemann
2001-11-28 8:58 ` szonyi calin
2001-11-28 9:31 ` Wouter van Bommel
2001-11-28 9:52 ` Martin Eriksson
2001-11-28 13:59 ` Chris Meadors
2001-11-28 14:06 ` Richard B. Johnson
2001-11-28 14:23 ` Piter Punk
2001-11-28 9:46 PVotruba
2001-11-30 7:28 "spurious 8259A interrupt: IRQ7" Zwane Mwaikambo
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=01112716302905.00872@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@jtrix.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