linux-kernel - Re: 2.6.31 ehci problem

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: <Pine.LNX.4.44L0.0909160939230.8236-100000@netrider.rowland.org>
Date:	Wed, 16 Sep 2009 09:44:03 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Volker Armin Hemmann <volkerarmin@...glemail.com>
cc:	Oliver Neukum <oliver@...kum.org>,
	LKML <linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>
Subject: Re: 2.6.31 ehci problem - mouse dead on scroll

On Wed, 16 Sep 2009, Volker Armin Hemmann wrote:

> emm, the mouse is attached through a powered 4port usb 2.0 hub. That is the 
> only way to get it working. If I attach it directly (without loading ohci) it 
> does not work (well, only tried with both Transaction Translator options off), 
> and if I load ohci before I connect it, it is very very jerky. So jerky in 
> fact, that I considered douzends of lockups a day a better alternative.

That is a separate issue and it is a serious bug.  If anything, the 
behavior with OHCI should be better than with EHCI.  This is worth 
pursuing farther.  A usbmon log combined with the dmesg log would help.  
There's no need to include all the boot-up messages in the dmesg log; 
you can clear the log buffer before plugging in the mouse.

In fact, we can probably forget about the EHCI issue.  If it works okay 
with the newer TT scheduler, that should be good enough.

Alan Stern

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