linux-mips
[Top] [All Lists]

Re: IRQ problem on cobalt / 2.6.6

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: IRQ problem on cobalt / 2.6.6
From: Peter Horton <phorton@bitbox.co.uk>
Date: Wed, 19 May 2004 13:57:22 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.55.0405191318500.22609@jurand.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20040513183059.GA25743@getyour.pawsoff.org> <20040518073439.GA6818@skeleton-jack> <20040518205914.GA29574@getyour.pawsoff.org> <Pine.LNX.4.55.0405191318500.22609@jurand.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.6 (Windows/20040502)
Maciej W. Rozycki wrote:

On Tue, 18 May 2004, Kieran Fulke wrote:

alas, no joy.
[...]
VP_IDE: VIA vt82c586a (rev 27) IDE UDMA33 controller on pci0000:00:09.1
   ide0: BM-DMA at 0x1420-0x1427, BIOS settings: hda:pio, hdb:pio
   ide1: BM-DMA at 0x1428-0x142f, BIOS settings: hdc:pio, hdd:pio
spurious 8259A interrupt: IRQ9.

Hmm, interesting.  As the 8259A can only signal IRQ7 and possibly IRQ15
as spurious interrupts, this smells like a bug in 8259A handlers,
regardless of system-specific problems you have.

We were getting interrupt 23 and calling do_IRQ() with a value of 9 (a bug, obviously). Interrupt 9 is masked so we get a "spurious 8259A interrupt" message.

P.



<Prev in Thread] Current Thread [Next in Thread>