[Bug 215361] SL-6000 zaurus USB error - 'bad CDC descriptors'

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=215361

--- Comment #4 from Ross Maynard (bids.7405@bigpond.com) ---
Hi Greg,

1. I tried connecting the SL-6000 in kernel 5.14.10, but got the same error:

usb 1-1: New USB device found, idVendor=04dd, idProduct=9032, bcdDevice= 
0.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: SL-6000
usb 1-1: Manufacturer: Sharp
usb 1-1: bad CDC descriptors
usbcore: registered new interface driver cdc_ether

As a side note, I also tried it with my SL-5600 with the same result.

2. The latest kernel I could find that would connect my Zaurus was 
2.6.38. I did get the "bad CDC descriptors" message, but the zaurus 
module loaded anyway:

usb 1-1: bad CDC descriptors
usbcore: registered new interface driver cdc_ether
zaurus 1-1:1.0: usb0: register 'zaurus' at usb-0000:00:14.0-1, 
pseudo-MDLM (BLAN) device, ea:30:12:ff:59:20
usbcore: registered new interface driver zaurus

3. I then tested with kernel 3.0. That did not work, and the zaurus 
module did not load:

usb 1-1: new full speed USB device number 4 using xhci_hcd
usb 1-1: bad CDC descriptors
usbcore: registered new interface driver cdc_ether

I am wondering if there was a change in the cdc_ether or zaurus modules 
that caused it to stop working in 3.0.


On 20/12/21 7:37 pm, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215361
>
> --- Comment #3 from Greg Kroah-Hartman (greg@kroah.com) ---
> On Sun, Dec 19, 2021 at 06:14:00AM +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
>> A 'bad CDC descriptors' error occurs when plugging the Sharp SL-6000 zaurus
>> into USB. It was working in 2.6.32 but has been broken from kernel 3
>> onwards.
> 2.6.32 was released in 2009, and 3.0 was released in 2011.  Can you
> please try a more modern kernel like 5.15, or ask for support from the
> vendor that is forcing you to use older kernels?
>
> Or, can you use 'git bisect' between the working and failing kernel
> versions to track down the offending commit?
>
> thanks,
>
> greg k-h
>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.