On Monday 22 May 2006 20:59, Andrew Morton wrote:
> It appears that the 2.6.13 kernel did not bring up the machine's io-APICs,
> but 2.6.16 did. However you are receiving eth0 interrupts on 2.6.16 so
> perhaps that's not relevant.
It looks like he's _not_ receiving eth0 interrupts if I'm not mistaken?
The lower one with apic presumably is 2.6.16
> 10: 130 XT-PIC eth0
> 16: 0 IO-APIC-level eth0
and this:
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=-1 pin1=-1 apic2=-1 pin2=-1
> ...trying to set up timer (IRQ0) through the 8259A ... failed.
> ...trying to set up timer as Virtual Wire IRQ... works.
looks suspiciously like a broken apic/code/workaround/whatever
I'd go with Andrew's suggestion and disable apic in your bootparameters
(noapic and/or nolapic) and possibly in your config if it corrects it
--
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
