On Tuesday 23 November 2004 16:28, Fabio Coatti wrote:
> Alle 00:39, mercoled� 24 novembre 2004, David Brownell ha scritto:
> 
> >
> > Except for the problems that device had when enumerating.
> > Those look like device faults that USB recovered from in
> > the right ways, despites some scarey messages.
> 
> Just to add an information, maybe lost in forwards: The device works 
> flawlessly with 2.6.8.1. (last time I've tried on a slightly different 
> machine with 2.6.8.1 but IIRC the device worked on the same machine that now 
> faults under 2.6.10-rc2-mm3, using 2.6.8.1; anyway I can retest this if 
> needed).

OK, so there may be two different problems then.  The one
producing the stack backtraces from SCSI/kobject stuff;
and a change in behavior related to USB.

What happens if you set the "old_scheme_first" usbcore
parameter?  One thing that changed since that kernel
was that enumeration works a bit more like one of the
schemes MS-Windows uses.

- Dave


> The device is detected fully only after few plug/unplug tries, as it fails 
> with this message:
> 
> Nov 23 00:09:43 kefk kernel: hub 5-0:1.0: state 5 ports 8 chg ff00 evt 0008
> Nov 23 00:09:43 kefk kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3 status 
> 001803 POWER sig=j  CSC CONNECT
> Nov 23 00:09:43 kefk kernel: hub 5-0:1.0: port 3, status 0501, change 0001, 
> 480 Mb/s
> Nov 23 00:09:43 kefk kernel: hub 5-0:1.0: debounce: port 3: total 100ms 
> stable 
> 100ms status 0x501
> Nov 23 00:09:43 kefk kernel: ehci_hcd 0000:00:1d.7: port 3 high speed
> Nov 23 00:09:43 kefk kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3 status 
> 001005 POWER sig=se0  PE CONNECT
> Nov 23 00:09:43 kefk kernel: usb 5-3: new high speed USB device using 
> ehci_hcd 
> and address 4
> Nov 23 00:09:43 kefk kernel: ehci_hcd 0000:00:1d.7: devpath 3 ep0in 3strikes
> Nov 23 00:09:44 kefk kernel: ehci_hcd 0000:00:1d.7: port 3 full speed --> 
> companion
> Nov 23 00:09:44 kefk kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3 status 
> 003801 POWER OWNER sig=j  CONNECT
> Nov 23 00:09:44 kefk kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
> Nov 23 00:09:44 kefk kernel: hub 2-0:1.0: state 5 ports 2 chg fffc evt 0002
> Nov 23 00:09:44 kefk kernel: uhci_hcd 0000:00:1d.1: port 1 portsc 0083,00
> Nov 23 00:09:44 kefk kernel: hub 2-0:1.0: port 1, status 0101, change 0001, 
> 12 
> Mb/s
> Nov 23 00:09:44 kefk kernel: hub 2-0:1.0: debounce: port 1: total 100ms 
> stable 
> 100ms status 0x101
> Nov 23 00:09:44 kefk kernel: usb 2-1: new full speed USB device using 
> uhci_hcd 
> and address 4
> Nov 23 00:09:44 kefk kernel: uhci_hcd 0000:00:1d.1: uhci_result_control: 
> failed with status 440000
> Nov 23 00:09:44 kefk kernel: [f7a73240] link (37a731b2) element (37ab2040)
> Nov 23 00:09:44 kefk kernel:   0: [f7ab2040] link (37ab2080) e0 Stalled 
> CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=36846be0)
> Nov 23 00:09:44 kefk kernel:   1: [f7ab2080] link (37ab20c0) e3 SPD Active 
> Length=0 MaxLen=3f DT1 EndPt=0 Dev=0, PID=69(IN) (buf=36252980)
> Nov 23 00:09:44 kefk kernel:   2: [f7ab20c0] link (00000001) e3 IOC Active 
> Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=e1(OUT) (buf=00000000)
> 
> After some tries with the same result, finally the device is detected and the 
> behaviour is reported on previous mail.
> 
> HTH.
> 
> Just let me know if more tests or information are needed.
>  
> -- 
> Fabio Coatti       http://members.ferrara.linux.it/cova     
> Ferrara Linux Users Group           http://ferrara.linux.it
> GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
> Old SysOps never die... they simply forget their password.
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to