On 10/04/2007 04:13 PM, Gordon Messmer wrote: > Gordon Messmer wrote: >> Chuck Ebbert wrote: >>> >>> What is displayed on consoles 3 and 4? >> >> No errors. Console 3 lists a number of modules loaded, and several >> inserted, ending with /tmp/loop.ko. Console 4 has normal looking >> kernel messages ending with: >> >> <4>loader used greatest stack depth: 2296 bytes left >> <6>loop: module loaded >> > > So... I left the laptop alone for a few minutes, and it eventually moved > on. The anaconda log is confusing. It indicates that several modules > were inserted seconds after loop, but those weren't printed on the > console at that time. The 'dmesg' output indicates: > > Clocksource tsc unstable (delta = -139639622012 ns) > > ...immediately after "loop: module loaded". I have no idea what this > all means, but I'm inclined to think that the times represented in > anaconda.log are incorrect. > Kernel option "clocksource=acpi_pm" will probably fix this. See https://fedoraproject.org/wiki/KernelBugTriage#common_problems -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
