Date: Thu, 7 Feb 2008 10:18:46 +0100 (CET)
From: Jiri Kosina <jkosina@suse.cz>
To: Chris Holvenstot <cholvenstot@comcast.net>
cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?
In-Reply-To: <1202318666.6406.13.camel@popeye>
Message-ID: <Pine.LNX.4.64.0802071016220.30873@twin.jikos.cz>
References: <1202302978.9058.13.camel@popeye>  <Pine.LNX.4.64.0802061427410.30873@twin.jikos.cz>
  <1202305740.9058.22.camel@popeye>  <Pine.LNX.4.64.0802061452210.30873@twin.jikos.cz>
 <1202318666.6406.13.camel@popeye>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1254
Lines: 32

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.

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/