On Sat, 2007-07-21 at 13:59 +0200, Ingo Molnar wrote: > * Mark Tiefenbruck <[EMAIL PROTECTED]> wrote: > > > IO window: disabled. > > MEM window: c0200000-c02fffff > > PREFETCH window: disabled. > > PCI: Bridge: 0000:00:14.4 > > IO window: disabled. > > MEM window: c0300000-c03fffff > > PREFETCH window: disabled. > > PCI: Setting latency timer of device 0000:00:05.0 to 64 > > PCI: Setting latency timer of device 0000:00:06.0 to 64 > > NET: Registered protocol family 2 > > > > The next few lines are usually as follows, but recent kernels never > > get to them: > > thanks for the detailed report and bisection test! The above hang > strongly implicates some sort of high-res timers, dynticks or > clocksource problem. Most likely timer interrupts do not come as > expected, and the above place is one of the first spots where the kernel > waits for a (short) timeout - so you see it hang indefinitely. > > Besides the options Thomas suggested, you could also try > clocksource=pm_timer?
Do you mean "clocksource=acpi_pm" ? Daniel - 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/
