LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?
Date: Thu, 07 Feb 2008 04:44:54 -0600	[thread overview]
Message-ID: <1202381094.6179.0.camel@popeye> (raw)
In-Reply-To: <Pine.LNX.4.64.0802071016220.30873@twin.jikos.cz>

Jiri - 


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.


Chris



On Thu, 2008-02-07 at 10:18 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> 
> > I have several hours of running aith nohpet and X's affinity set to 2
> > instead of 3 and so far everything is running flawlessly.
> 
> Great, so this definitely is some kind of timing issue, thanks for 
> verifying that.
> 
> > which has the same suggestion (taskset) as you made, for me this was 
> > something new starting with 2.6.24-git15 - maybe something made a timing 
> > issue fall a little closer to the edge.
> 
> Yes, could be some scheduler update that made the problem more visible. If 
> you'd had time to use git-bisect to find the exact commit that exposes 
> your problem, that might be interesting. But as you said that this is not 
> immediately reproducible, it might take ages.
> 
> > Would you like me to try and further isolate things for you here by 
> > either running with just nohpet OR just the taskset to change X's 
> > affinity?
> 
> Yes, that would help. Especially knowing whether running with 'nohpet' 
> fixes the problem would be nice.
> 


  parent reply	other threads:[~2008-02-07 10:41 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 [this message]
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
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=1202381094.6179.0.camel@popeye \
    --to=cholvenstot@comcast.net \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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).