Hi,
I have just tested for fun the upcoming release candidate and have
found the following difference with a 'spurious 8259A interrupt:
IRQ7' message, possibly triggered by the
--- linux-2.6.19-rc5.txt2006-11-28 19:23:54.145722821 +0100
+++ linux-2.6.19-rc6-git10.txt 2006-1
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
On Thu, 2005-04-14 at 14:43 -0600, Bjorn Helgaas wrote:
> On Thu, 2005-04-14 at 13:11 -0400, Lee Revell wrote:
> > 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
On Thu, 2005-04-14 at 13:11 -0400, Lee Revell wrote:
> 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
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
On Wed, 6 Dec 2000, Giacomo Catenazzi wrote:
> On my box, with heavy load I saw:
> spurious 8259A interrupt: IRQ7.
> Newer seen this message before.
>
> Linux (2.4.0.11.4) or my old slow box ?
>
>
> giacomo
>
This is really "normal" occasional
On my box, with heavy load I saw:
spurious 8259A interrupt: IRQ7.
Newer seen this message before.
Linux (2.4.0.11.4) or my old slow box ?
giacomo
My dmesg
BIOS-provided physical RAM map:
BIOS-e820: 0009fc00 @ (usable)
BIOS-e820: 0400
7 matches
Mail list logo
