Subject: Re: 2.6.24-git15 Keyboard Issue?
From: Chris Holvenstot <cholvenstot@comcast.net>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Kernel <linux-kernel@vger.kernel.org>
In-Reply-To: <Pine.LNX.4.64.0802061452210.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>
Content-Type: text/plain
Date: Wed, 06 Feb 2008 11:24:26 -0600
Message-Id: <1202318666.6406.13.camel@popeye>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1898
Lines: 54

Jiri - 

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.

Even though Mark Hounschell pointed me at this old Suse issue 

(https://bugzilla.novell.com/show_bug.cgi?id=223561)

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.  

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?

Once again thank you for your prompt (and effective) support on this
issue.

Chris


On Wed, 2008-02-06 at 14:54 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
> 
> > On this system I am using a PS2 Keyboard - and let me stress that it is 
> > only occasionaly that it happens - I have had 2.6.24-git15 up for about 
> > 2 hours now and have only seen it about a dozen times. I also note one 
> > other thing - although my system is lightly loaded - at this time of day 
> > I am pretty much just using email on an AMD 64 X2 4600+ with 2 gigs of 
> > of memory - I have noticed several times that I will be typing away and 
> > nothing is appearing on the screen - and a few seconds later - boom - 
> > there it all is.
> 
> It could be some timing problem. Does this happen also in console, or 
> only when running X?
> 
> Could you please try to
> 
> - boot with 'nohpet' kernel parameter
> - taskset -p 0x00000002 <pid_of_Xserver> if this is a multi-CPU/core 
>   machine and you are experiencing the problems only in X
> 
> Thanks,
> 

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