linux-kernel - Re: 2.6.20-rc4: usb somehow broken

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: <200701141008.49986.prakash@punnoor.de>
Date:	Sun, 14 Jan 2007 10:08:37 +0100
From:	Prakash Punnoor <prakash@...noor.de>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: 2.6.20-rc4: usb somehow broken

Am Donnerstag 11 Januar 2007 18:28 schrieb Oliver Neukum:
> Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
> > Hi,
> >
> > I can't scan anymore. :-( I don't know which rc kernel introduced it, but
> > this are the messages I get (w/o touching the device/usb cable except
> > pluggin it in for the first time):
> >
> > usb 1-1.2: new full speed USB device using ehci_hcd and address 4
> > ehci_hcd 0000:00:0b.1: qh ffff81007bc6c280 (#00) state 4
> > usb 1-1.2: configuration #1 chosen from 1 choice
> > usb 1-1.2: USB disconnect, address 4
> > usb 1-1.2: new full speed USB device using ehci_hcd and address 5
> > usb 1-1.2: configuration #1 chosen from 1 choice
> > usb 1-1.2: USB disconnect, address 5
> > usb 1-1.2: new full speed USB device using ehci_hcd and address 6
> > usb 1-1.2: configuration #1 chosen from 1 choice
> > usb 1-1.2: USB disconnect, address 6
> > usb 1-1.2: new full speed USB device using ehci_hcd and address 7
> > usb 1-1.2: configuration #1 chosen from 1 choice
> > usb 1-1.2: USB disconnect, address 7
> > usb 1-1.2: new full speed USB device using ehci_hcd and address 8
> > usb 1-1.2: configuration #1 chosen from 1 choice
> >
> >
> > Shouldn't the ohci module handle the scanner? The scanner is connected
> > through a hub.
>
> Therefore it goes to EHCI. Can you try a direct connection?
>
> > I don't remember how 2.6.19 handled it, or whether I used some new exotic
> > setting which causes the breakage.
>
> Could you try 2.6.19?
>
> > Well, I'll test this week-end and upload more infos then. If you already
> > have some ideas in the meantime, let me know.
>
> Please test with CONFIG_USB_DEBUG


Hi, I did more tests and I was wrong about "broken". It seems more a time-out 
problem, ie if I try to use sane again in short intervalls, I will get my 
device working. The cause seems CONFIG_USB_SUSPEND=y. With 2.6.20-rc5 the 
situation seems better, ie now I don't get "no device" very less often.

So do you still want me to try above stuff?

-- 
(°=                 =°)
//\ Prakash Punnoor /\\
V_/                 \_V

Content of type "application/pgp-signature" skipped