From: Oliver Neukum <oliver@neukum.org>
To: Prakash Punnoor <prakash@punnoor.de>,
       Alan Stern <stern@rowland.harvard.edu>
Subject: Re: 2.6.20-rc4: usb somehow broken
Date: Sun, 14 Jan 2007 10:28:35 +0100
User-Agent: KMail/1.8
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
References: <200701111820.46121.prakash@punnoor.de> <200701111828.02119.oliver@neukum.org> <200701141008.49986.prakash@punnoor.de>
In-Reply-To: <200701141008.49986.prakash@punnoor.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200701141028.35533.oliver@neukum.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1850
Lines: 39

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/