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]

Date:	Sun, 14 Jan 2007 10:28:35 +0100
From:	Oliver Neukum <oliver@...kum.org>
To:	Prakash Punnoor <prakash@...noor.de>,
	Alan Stern <stern@...land.harvard.edu>
Cc:	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: 2.6.20-rc4: usb somehow broken

Am Sonntag, 14. Januar 2007 10:08 schrieb Prakash Punnoor:
> 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

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

Have you confirmed that by using a kernel without  CONFIG_USB_SUSPEND ?

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