New: SL-6000 zaurus USB error - 'bad CDC descriptors'

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

            Bug ID: 215361
           Summary: SL-6000 zaurus USB error - 'bad CDC descriptors'
           Product: Drivers
           Version: 2.5
    Kernel Version: 3/4/5
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

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.

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

In 2.6.32 the following lines were included in dmesg:

usb0: register 'zaurus' at usb-0000:00:14.0-2, pseudo-MDLM (BLAN) device, fe:1b:05:23:49:7f
usbcore: registered new interface driver zaurus

You may reply to this email to add a comment.

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

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

--- Comment #1 from Ross Maynard ([email protected]) --- Correction:

In 2.6.32 the following lines were included in dmesg:

usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver zaurus
usb0: register 'zaurus' at usb-0000:00:14.0-2, pseudo-MDLM (BLAN) device, fe:1b:05:23:49:7f
usbcore: registered new interface driver zaurus

You may reply to this email to add a comment.

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

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

--- Comment #2 from Ross Maynard ([email protected]) --- Correction:

In 2.6.32 the following lines were included in dmesg:

usbcore: registered new interface driver cdc_ether
usb0: register 'zaurus' at usb-0000:00:14.0-2, pseudo-MDLM (BLAN) device, fe:1b:05:23:49:7f
usbcore: registered new interface driver zaurus

You may reply to this email to add a comment.

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

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

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

--- Comment #3 from Greg Kroah-Hartman ([email protected]) ---

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.

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

--- Comment #4 from Ross Maynard ([email protected]) --- 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.

You may reply to this email to add a comment.

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

There probably is. Can you please use 'git bisect' between those two versions to find the offending change?

thanks,

greg k-h

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

--- Comment #5 from Greg Kroah-Hartman ([email protected]) ---

There probably is. Can you please use 'git bisect' between those two versions to find the offending change?

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.

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

--- Comment #6 from Ross Maynard ([email protected]) --- Hi Greg,

I found the patch:

Bisecting: 0 revisions left to test after this (roughly 0 steps) [16adf5d07987d93675945f3cecf0e33706566005] usbnet: Remove over-broad module alias from zaurus.

You may reply to this email to add a comment.

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

Great, can you send this information to the linux-usb mailing list so we know what id to add to the driver?

thanks,

greg k-h

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

--- Comment #7 from Greg Kroah-Hartman ([email protected]) ---

Great, can you send this information to the linux-usb mailing list so we know what id to add to the driver?

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.

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

--- Comment #8 from Ross Maynard ([email protected]) --- Hi Greg,

I have sent an email to [email protected].

Thanks

You may reply to this email to add a comment.

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

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

Oliver Neukum ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #9 from Oliver Neukum ([email protected]) ---
The SL-6000 is explicitly listed with the device and vendor IDs given here. Looks like multiple versions of the same device. Please give the output of 'lsusb -v' for your device.

You may reply to this email to add a comment.

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

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

--- Comment #10 from Ross Maynard ([email protected]) --- Hi Oliver,

Please see attached: lsusb.txt

Thanks

You may reply to this email to add a comment.

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

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

--- Comment #11 from Oliver Neukum ([email protected]) --- Created attachment 300340
--> https://bugzilla.kernel.org/attachment.cgi?id=300340&action=edit
another special case

Please try this patch

You may reply to this email to add a comment.

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

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

--- Comment #12 from Ross Maynard ([email protected]) --- Hi Oliver,

I applied the patch, and was able to ping and ssh into my SL-6000.

Thanks!

You may reply to this email to add a comment.

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

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

Ross Maynard ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

You may reply to this email to add a comment.

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