LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Thu, 7 Feb 2008 11:51:47 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802071149260.30955@jikos.suse.cz> (raw)
In-Reply-To: <1202381094.6179.0.camel@popeye>

On Thu, 7 Feb 2008, Chris Holvenstot wrote:

> I have been up and running now for about a half hour - since I did not 
> hear your preference I stayed with git15 instead of jumping up to git16 
> in an attempt to avoid introducing any unwanted changes.
> 
> The only non-standard thing I did was to use the nohpet directive at
> boot time - I did NOT enter the previously used taskset command to alter
> X's affinity. 
> 
> I have been banging away on my keyboard for about a half hour now with
> no problems. While this is not conclusive on a 'soft' problem, from what
> I experienced yesterday I would have expected to have seen the problem
> by now.
> 
> Please let me know if there are any other items you would like to do or
> options you would like me to try.

Thanks. So this clearly indicates that you are hitting either hardware 
bug, or some bug in our HPET handling code.

Adding Ingo and Thomas to CC. Short summary -- Chris (and apparently other 
people) are sometimes seeing repeated keypressess when HPET timer is used. 
This doesn't happen when alternative clocksource is used.

Full thread: http://lkml.org/lkml/2008/2/6/100

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2008-02-07 10:51 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 [this message]
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
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=Pine.LNX.4.64.0802071149260.30955@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=cholvenstot@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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).