Thomas - I hope that, from at least my perspective, your question is rhetorical. I am fully willing to publicly admit that I don't have a clue. About much of anything. I will even admit that until prompted by Jiri yesterday I had never even heard of the nohpet directive for the boot line.
I am willing to do whatever I can to help isolate and or resolve this issue, but to do so I need one of you experts to firmly grab hold of some portion of my anatomy and guide me in the right direction. Chris On Thu, 2008-02-07 at 17:13 +0100, Thomas Gleixner wrote: > On Thu, 7 Feb 2008, Chris Holvenstot wrote: > > > OK - I think that this is wat you are looking for. If there is > > anything else I can proivde or if I have mucked up this simple cut and > > paste just let me know. > > > > /proc/timer_list after a "standard" boot up: > > Tick Device: mode: 1 > > Clock Event Device: pit > > > /proc/timer_list after a boot with nohpet > > Tick Device: mode: 1 > > Clock Event Device: pit > > Both use PIT, so no hpet involved > > > The dmesg output after a "standard" boot: > > > [ 0.000000] Kernel command line: > > root=UUID=4dc2e6b0-c980-418b-8ad0-98358e7ec47d ro quiet splash > > [ 0.368027] Time: acpi_pm clocksource has been installed. > > > > The dmesg output after a boot with "nohpet" > > > [ 0.000000] Kernel command line: > > root=UUID=4dc2e6b0-c980-418b-8ad0-98358e7ec47d ro quiet splash nohpet > > [ 0.368027] Time: acpi_pm clocksource has been installed. > > Both boots use acpi_pm clocksource and there is nowhere a sign of HPET > in the logs except the "nohpet" on the command line. > > /me is confused > > How does "nohpet" on the command line influence the behaviour, when > there is no hpet available at all. > > Thanks, > tglx > > -- 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/