Messages in this thread | | | Date | Fri, 28 Jul 2006 17:10:30 -0500 | From | Paul Fulghum <> | Subject | Re: 2.6.18-rc2-mm1 timer int 0 doesn't work |
| |
Andrew Morton wrote: > I don't know what would have caused this. Was 2.6.18-rc1-mm2 OK?
I have not tried that combination.
> 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.
The machine in question is at the office so I won't be able to test that particular setup this weekend. I will test removing the listed patches as time permits starting on Monday.
It happens every time so there is no problem in reproducing it. I will also test 2.6.18-rc2-mm1 on my home machine which is AMDx2 as well (but a different chipset/MB).
-- Paul
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |