On Sun, 27 Jan 2008 13:37:02 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > * Kevin Winchester <[EMAIL PROTECTED]> wrote: > > > Sure, the result of the script is at > > > > http://personal.nbnet.nb.ca/kwin/cfs-debug-info-2008.01.27-08.13.28 > > it seems you've got hpet active by default: > > /sys/devices/system/clocksource/clocksource0/current_clocksource: > hpet > /sys/devices/system/clocksource/clocksource0/available_clocksource: > hpet acpi_pm pit jiffies tsc > > do you get a similar lockup if you use acpi_pm? You can do that either > by disabling the HPET options in your .config, or by doing this prior > starting up X: > > echo acpi_pm > > /sys/devices/system/clocksource/clocksource0/current_clocksource > Since X was being autostarted when the computer booted, I just removed "hpet=force" from my command line instead. The result was that the lockup happened earlier, so that it was before X was being started. So I guess X is not the culprit. -- Kevin Winchester <[EMAIL PROTECTED]> -- 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/
