Re: 2.6.18-rc2-mm1 timer int 0 doesn't work

Andrew Morton
2006-07-28T21:49:19Z

On Fri, 28 Jul 2006 13:44:36 -0500
Paul Fulghum <paulkf@microgate.com> wrote:

> 2.6.18-rc2-mm1 causes boot to fail early with:
> kernel panic: IO_APIC timer interrupt 0 doesn't work
>
> 2.6.18-rc2 works.
>
> 2.6.18-rc2-mm1 kernel config located at:
> http://www.microgate.com/ftp/linux/test/config
>
> syslog from working 2.6.18-rc2 located at:
> http://www.microgate.com/ftp/linux/test/syslog
>

I don't know what would have caused this. Was 2.6.18-rc1-mm2 OK?

Patches which touch arch/i386/kernel/io_apic.c are:

x86_64-mm-i386-up-generic-arch.patch
x86_64-mm-i386-io-apic-access.patch
genirq-convert-the-i386-architecture-to-irq-chips.patch
initial-generic-hypertransport-interrupt-support.patch
genirq-i386-irq-remove-the-msi-assumption-that-irq-==-vector.patch
genirq-i386-irq-move-msi-message-composition-into-io_apicc.patch
genirq-i386-irq-dynamic-irq-support.patch

The developers of those patches are cc'ed.

A bisection search would be useful, if you have the time. I'd zero in on
the x86_64 tree initially. Perhaps x86_64-mm-i386-io-apic-access.patch.

Or it could be something else altogether.