All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 215361] New: SL-6000 zaurus USB error - 'bad CDC descriptors'
Date: Mon, 20 Dec 2021 09:37:14 +0100	[thread overview]
Message-ID: <YcBAuk0027ItjqYX@kroah.com> (raw)
In-Reply-To: <bug-215361-208809@https.bugzilla.kernel.org/>

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

  parent reply	other threads:[~2021-12-20  8:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-19  6:14 [Bug 215361] New: SL-6000 zaurus USB error - 'bad CDC descriptors' bugzilla-daemon
2021-12-19 20:46 ` [Bug 215361] " bugzilla-daemon
2021-12-19 22:27 ` bugzilla-daemon
2021-12-20  8:37 ` Greg KH [this message]
2021-12-20  8:37 ` bugzilla-daemon
2021-12-21  8:07 ` bugzilla-daemon
2021-12-21  8:20   ` Greg KH
2021-12-21  8:20 ` bugzilla-daemon
2022-01-16  4:23 ` bugzilla-daemon
2022-01-26 12:31   ` Greg KH
2022-01-26 12:32 ` bugzilla-daemon
2022-01-27  2:25 ` bugzilla-daemon
2022-01-27  6:00 ` bugzilla-daemon
2022-01-27  7:45 ` bugzilla-daemon
2022-01-27 15:50 ` bugzilla-daemon
2022-01-28 23:52 ` bugzilla-daemon
2022-04-22  4:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YcBAuk0027ItjqYX@kroah.com \
    --to=greg@kroah.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.