linux-kernel - Re: 2.6.24-git15 Keyboard Issue?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1202381094.6179.0.camel@popeye>
Date:	Thu, 07 Feb 2008 04:44:54 -0600
From:	Chris Holvenstot <cholvenstot@...cast.net>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.24-git15 Keyboard Issue?

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

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