From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217862] [BUG] Alauda driver causes oops when inserted with card in with transfer buffer is on stack, throws errors if card is inserted afterwards.
Date: Wed, 13 Sep 2023 19:08:57 +0000 [thread overview]
Message-ID: <bug-217862-208809-YAr47nZ9Oz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217862-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217862
--- Comment #19 from Alan Stern (stern@rowland.harvard.edu) ---
Are you referring to the attachment in comment #16? Whatever error messages it
contains are completely swamped by the usb-storage verbose debugging output; in
practice it's impossible to find them.
In any case, we've pretty much reached the limit of my knowledge about this
driver. Everything so far has involved fixing some pretty straightforward bugs
(i.e., bad interactions between the driver and the rest of the kernel), but
problems involving the data sent between the driver and the device are beyond
me, since I have no idea how Alauda devices are meant to work.
If you want to proceed farther, there are two things you might try. One is to
get in touch with the people who originally wrote the driver, to see if they
still remember how it's supposed to operate and can help fix the problems.
The other is to try running an older version of the Linux kernel, back from
when the driver did work right (assuming it ever did -- something I'm not sure
of). If you do manage to find a version of the driver that works, comparing it
with the current version may indicate what needs to be fixed.
One other thing: You remember that comparing the usbmon trace with the Windows
Wireshark recording showed that the Linux driver was using the wrong endpoint
for some of its commands. Well, in fact the recording shows that Windows uses
_both_ bulk_OUT endpoints at various times. Therefore the fact that the Linux
driver uses only one of them is rather suspicious. But I don't know what each
endpoint is supposed to do or when they are supposed to be used. (Also, this
is partly why I wonder whether the driver ever really worked, given that it has
never used more than one of the bulk-OUT endpoints. Just possibly, the devices
it was written for were somehow different from the device you are using now.)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-09-13 19:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 1:05 [Bug 217862] New: [BUG] Alauda driver causes oops when inserted with card in with transfer buffer is on stack, throws errors if card is inserted afterwards bugzilla-daemon
2023-09-02 1:05 ` [Bug 217862] " bugzilla-daemon
2023-09-02 2:49 ` bugzilla-daemon
2023-09-02 23:36 ` bugzilla-daemon
2023-09-03 16:09 ` bugzilla-daemon
2023-09-04 19:41 ` bugzilla-daemon
2023-09-05 0:46 ` bugzilla-daemon
2023-09-05 16:16 ` bugzilla-daemon
2023-09-05 16:17 ` bugzilla-daemon
2023-09-05 17:47 ` bugzilla-daemon
2023-09-05 17:48 ` bugzilla-daemon
2023-09-05 19:43 ` bugzilla-daemon
2023-09-06 1:25 ` bugzilla-daemon
2023-09-06 14:49 ` bugzilla-daemon
2023-09-07 1:35 ` bugzilla-daemon
2023-09-07 13:02 ` bugzilla-daemon
2023-09-09 20:58 ` bugzilla-daemon
2023-09-10 2:33 ` bugzilla-daemon
2023-09-13 18:08 ` bugzilla-daemon
2023-09-13 19:08 ` bugzilla-daemon [this message]
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=bug-217862-208809-YAr47nZ9Oz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.