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 18:46:03 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802071838110.9204@apollo.tec.linutronix.de> (raw)
In-Reply-To: <1202402704.6087.12.camel@popeye>

Chris,

On Thu, 7 Feb 2008, Chris Holvenstot wrote:
> Thomas - 
> 
> I hope that, from at least my perspective, your question is rhetorical.

Yeah. The non rhetorical one was directed to Jiri. :)

> 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. 

No problem. At the moment I'm equally clueless :)
 
> 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.

Can you please apply the following patch, boot w/o nohpet and provide
the dmesg output ?

Thanks,
	tglx

diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 429d084..4e98241 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -375,8 +375,10 @@ int __init hpet_enable(void)
 {
 	unsigned long id;
 
-	if (!is_hpet_capable())
+	if (!is_hpet_capable()) {
+		printk(KERN_INFO "HPET not available\n");
 		return 0;
+	}
 
 	hpet_set_mapping();
 
@@ -392,6 +394,7 @@ int __init hpet_enable(void)
 	 * information and the number of channels
 	 */
 	id = hpet_readl(HPET_ID);
+	printk(KERN_INFO "HPET available. ID = %lx\n", id);
 
 #ifdef CONFIG_HPET_EMULATE_RTC
 	/*
@@ -412,6 +415,7 @@ int __init hpet_enable(void)
 	return 0;
 
 out_nohpet:
+	printk(KERN_INFO "HPET disabled\n");
 	hpet_clear_mapping();
 	boot_hpet_disable = 1;
 	return 0;

  reply	other threads:[~2008-02-07 17:46 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
2008-02-07 16:45                     ` Chris Holvenstot
2008-02-07 17:46                       ` Thomas Gleixner [this message]
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.0802071838110.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).