From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 212955] Possible kernel regression USB2 (not USB3) port EDIROL UA-101 (in USB 1.1 mode, not USB2) error -110
Date: Wed, 02 Jun 2021 16:15:53 +0000 [thread overview]
Message-ID: <bug-212955-208809-ND37ExSOL5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212955-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212955
--- Comment #13 from Alan Stern (stern@rowland.harvard.edu) ---
THat commit you found, 51e6f07cb12e, cannot be the real culprit. Merge commits
don't change any code (as a general rule). Something must have gone wrong with
the bisection procedure.
The way to test the result of a bisection is: First, check out the commit that
the bisection identified, build it and boot that kernel, and verify that the
problem occurs. Second, check out the commit's parent (or revert the commit),
build and boot the resulting kernel, and verify that the problem does not
occur.
One thing you could do is get a list of commits affecting the snd-ua101 driver
and try checking out and testing various ones, to find the first commit which
exhibits the problem.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-06-02 16:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:34 [Bug 212955] New: Possible kernel regression USB2 (not USB3) port EDIROL UA-101 (in USB 1.1 mode, not USB2) error -110 bugzilla-daemon
2021-05-05 20:20 ` [Bug 212955] " bugzilla-daemon
2021-05-06 5:12 ` bugzilla-daemon
2021-05-06 5:14 ` bugzilla-daemon
2021-05-06 5:17 ` bugzilla-daemon
2021-05-06 5:17 ` bugzilla-daemon
2021-05-06 15:45 ` bugzilla-daemon
2021-05-07 2:12 ` bugzilla-daemon
2021-05-07 2:21 ` bugzilla-daemon
2021-05-07 15:07 ` bugzilla-daemon
2021-05-08 3:10 ` bugzilla-daemon
2021-06-02 4:07 ` bugzilla-daemon
2021-06-02 4:25 ` bugzilla-daemon
2021-06-02 16:15 ` bugzilla-daemon [this message]
2021-06-02 18:15 ` bugzilla-daemon
2021-06-02 19:51 ` bugzilla-daemon
2021-06-02 19:54 ` bugzilla-daemon
2021-06-02 20:00 ` bugzilla-daemon
2021-06-03 4:42 ` bugzilla-daemon
2021-06-05 3:36 ` bugzilla-daemon
2021-06-07 3:47 ` bugzilla-daemon
2021-06-07 4:39 ` bugzilla-daemon
2021-06-07 15:16 ` bugzilla-daemon
2021-06-07 19:06 ` 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=bug-212955-208809-ND37ExSOL5@https.bugzilla.kernel.org/ \
--to=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.