On Monday, 24 September 2007 18:46, Thomas Gleixner wrote: > On Mon, 2007-09-24 at 17:18 +0200, Rafael J. Wysocki wrote: > > > > Well, "noacpi" seems to be a synonym for "pci=noacpi". > > > > > > > > Anyway, it causes acpi_disable_pci() to be executed, which according to > > > > Documentation/kernel-parameters.txt means "Do not use ACPI for IRQ > > > > routing or > > > > for PCI scanning" (it works like this on x86_64 too, although the doc > > > > says it's > > > > x86_32-specific). > > > > > > Hrm. The local apic timer calibration does not use anything which is > > > related to interrupts, but if we use the local APIC timer we switch off > > > PIT. > > > > > > Can you boot Linus latest (w/o hrt patches) and add "apicmaintimer" to > > > the kernel command line please ? > > > > Works, dmesg attached. > > /me scratches head
Retested. > We know, that > - disabling local apic timers work This works reproducibly accross the board. > - local apic timers (which turn off PIT) work. when noacpiFSCKEDPARSING This stopped working, although it evidently worked yesterday (wtf?). There seems to be a history effect in the box, to make things more "interesting". > is given on the kernel command line. > > I have no clue, what might be the difference of noacpiFSCKEDPARSING. The > boot log is not giving any hint at all. > > acpi_disable_pci() sets acpi_pci_disabled and acpi_noirq to 1. > > What happens, if you set "acpi=noirq" instead ? That obviously doesn't help. I think the only solid data point so far is that "noapictimer" makes the box boot. Greetings, Rafael - 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/
