LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: Jiri Kosina <jkosina@suse.cz>,
Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Thu, 7 Feb 2008 17:13:44 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802071629350.9204@apollo.tec.linutronix.de> (raw)
In-Reply-To: <1202396868.6087.8.camel@popeye>
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
next prev parent reply other threads:[~2008-02-07 16:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 13:02 Chris Holvenstot
2008-02-06 13:23 ` Mark Hounschell
2008-02-06 13:28 ` Jiri Kosina
2008-02-06 13:49 ` Chris Holvenstot
2008-02-06 13:54 ` Jiri Kosina
2008-02-06 16:36 ` Kristoffer Ericson
2008-02-06 17:24 ` Chris Holvenstot
2008-02-07 9:18 ` Jiri Kosina
2008-02-07 9:51 ` Chris Holvenstot
2008-02-07 10:44 ` Chris Holvenstot
2008-02-07 10:51 ` Jiri Kosina
2008-02-07 12:29 ` Thomas Gleixner
2008-02-07 15:07 ` Chris Holvenstot
2008-02-07 16:13 ` Thomas Gleixner [this message]
2008-02-07 16:45 ` Chris Holvenstot
2008-02-07 17:46 ` Thomas Gleixner
2008-02-08 5:36 ` Chris Holvenstot
2008-02-09 9:56 ` Thomas Gleixner
2008-02-09 10:37 ` Chris Holvenstot
2008-02-09 13:59 ` Thomas Gleixner
2008-03-28 10:15 ` Thomas Gleixner
2008-03-28 11:20 ` Chris Holvenstot
2008-03-28 11:24 ` Jiri Kosina
2008-03-28 11:34 ` Chris Holvenstot
2008-02-08 15:08 ` Jiri Kosina
2008-02-08 23:25 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.00.0802071629350.9204@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=cholvenstot@comcast.net \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--subject='Re: 2.6.24-git15 Keyboard Issue?' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).