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: Sat, 9 Feb 2008 14:59:24 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802091255190.3145@apollo.tec.linutronix.de> (raw)
In-Reply-To: <1202553464.6386.7.camel@popeye>

On Sat, 9 Feb 2008, Chris Holvenstot wrote:

> Thomas - 
> 
> Attached is the output I believe you requested (standard boot - ommiting
> the NOHPET directive)
> 
> Unless you want to try something else i will run in this configuration
> today to try and verify that the problem is still with us.
> 
> Thanks for th good wishes - it is going to be a while - I had an open
> heart procedure about two weeks ago and they are not subtle  when they
> split your chest open.
> 
> This is why I said that I would be more than happy to do the bisect
> thing if it comes to that - since I can't go out and chase the ladies I
> might as well do something useful.

That'd be cool.
 
> However, as previously stated I would need a little instruction on how
> to accoomplish this.

Linus gave instructions here:

http://marc.info/?l=linux-kernel&m=118408208816556&w=2

If you have further questions, I'm happy to help.
 
> [    0.000000] Kernel command line: root=UUID=4dc2e6b0-c980-418b-8ad0-98358e7ec47d ro quiet splash
....
> [    0.004000] HPET not available

Ok. That confirms, that we never even try to touch hpet at all. So the
mystery why "nohpet" on the kernel command line makes your problem go
away is yet more mysterious.

Thanks,
	tglx

  reply	other threads:[~2008-02-09 13:59 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
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 [this message]
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.0802091255190.3145@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).