From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: war@lucidpixels.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A Interrupt IRQ 7
Date: 23 Jun 2003 08:11:29 +0200 [thread overview]
Message-ID: <1056348689.587.1.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <20030622222014.7827.qmail@lucidpixels.com>
On Mon, 2003-06-23 at 00:20, war@lucidpixels.com wrote:
> Jun 22 09:29:51 p500 kernel: spurious 8259A interrupt: IRQ7.
I'm also seeing this on my NEC Chrom@ laptop, just at the very end of
the boot stage, just before X starts up.
> # cat /proc/interrupts
> CPU0
> 0: 6486628 XT-PIC timer
> 1: 6 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 4: 647546 XT-PIC serial
> 5: 0 XT-PIC Crystal audio controller
> 8: 1 XT-PIC rtc
> 9: 3548883 XT-PIC eth2, eth3
> 11: 2601852 XT-PIC ide2, ide3, eth0, eth1
> 12: 38 XT-PIC PS/2 Mouse
> 14: 121950 XT-PIC ide0
> 15: 25 XT-PIC ide1
> NMI: 0
> LOC: 6486487
> ERR: 11
> MIS: 0
>
> Is there anyway to narrow down what could be causing this error, as nothing uses IRQ7?
>
> The system is a Dell Optiplex GX1 \bp.
>
> http://docs.us.dell.com/docs/systems/d_gx1p/irq.htm
>
> It says IRQ7 is the parallel port.
>
> I have the parallel port disabled on \b\b\bin the bios.
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0301.2/0960.html
>
> An earlier thread on LKML, a lot of different opn\binions as to if this is a serious problem or not and what to do about it.
>
> Should I take each board out and run the system until I see the message again?
>
> I've only seen this message once.
>
> Today that is.
>
> Using all PCI nics.
>
> kern.warn:Jun 10 23:30:43 p500 kernel: spurious 8259A interrupt: IRQ7.
> kern.warn:Jun 11 22:29:44 p500 kernel: spurious 8259A interrupt: IRQ7.
> kern.warn:Jun 14 20:24:34 p500 kernel: spurious 8259A interrupt: IRQ7.
> kern.warn:Jun 20 00:10:24 p500 kernel: spurious 8259A interrupt: IRQ7.
>
> Could this have anything to do with using the onboard ISA Sound card?
>
> (It uses IRQ5).
>
> I am using Kernel 2.4.21.
>
> linux-2.4.21.tar.bz2 . . . . . . Jun 13 14:52 27865k
>
> And those logs go back to the 10th, before I was running 2.4.20, so it is nothing to do with the kernel.
>
> What did *I* change?
>
> The only I\bthing I've recently change w\b\bd was: I went from 3 ISA boae\brds to PCI
>
> and took out an ol d\b\bd ATA/100 board and put in a ATA/133 board (Promise) (both)
>
> the 3isas were 5\b3com 90\b\b509s, 2 TP only, 1 aui,bnc,tp
>
> it is the same configuration now but with PCI and 3com 905bs (2), and 1 3com 900 combo (pci)
>
> here is lspci output
>
> 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
> 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
> 00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
> 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
> 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
> 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
> 00:0e.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02)
> 00:0f.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev 03)
> 00:11.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
> 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c)
> 02:09.0 Ethernet controller: 3Com Corporation 3c900 Combo [Boomerang]
> 02:0a.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
> 02:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30)
>
> what would be the best way to determine what is causing his \b\b\b\bthis problem?
prev parent reply other threads:[~2003-06-23 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 22:20 war
2003-06-22 22:47 ` Alan Cox
2003-06-22 23:01 ` war
2003-06-22 23:27 ` war
2003-06-23 6:11 ` Felipe Alfaro Solana [this message]
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=1056348689.587.1.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=war@lucidpixels.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
all inboxes | Powered by JetHome®