![]() | |||||||||||||
Messages in this thread |
On Mon, 2007-04-30 at 23:33 -0400, Mark Lord wrote: > Daniel Walker wrote:> > > > I'm interested in which clocksource is getting used, which is in the > > boot log.> > Well then, send me a patch that dumps that information out just before it locks up. > We know (first post in this thread) that the lockup occurs just after > these two messages:> > "switched to high resolution mode on cpu 1" > "switched to high resolution mode on cpu 0" > > So just dump out anything else you need to see at the same time, > and it'll still be on my screen when the darned thing locks up. > > Simple, eh. We both get to run around a treadmill this way. ;) I guess I could make due with the successful boot (less running for us both).. It's using the hpet clocksource .. You could try adding clocksource=acpi_pm to the boot args , in the off chance it's an hpet clock issue. Daniel - 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/ | ||||||||||||
| Last update: 2007-05-01 06:37 [from the cache] ©2003-2008 | |||||||||||||