Messages in this thread | | | Date | Thu, 7 Feb 2008 17:13:44 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: 2.6.24-git15 Keyboard Issue? |
| |
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
| |