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 18:15:26 +0000 [thread overview]
Message-ID: <bug-212955-208809-eCpCjBUvSI@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 #14 from Lucas Endres (jaffa225man@gmail.com) ---
(In reply to Alan Stern from comment #13)
> 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.
I probably was doing it wrong, then, but thought I was being quite thorough.
Here's the procedure I'd been following (probably from
https://git-scm.com/docs/git-bisect):
0. cd /usr/src/linux-next
0.1 On the first run, I ran these: "git bisect start", "git bisect bad", "git
bisect good $OriginalKnownGoodVersion" (I think the original known good was
v5.12.0 or the first commit to 5.12.0)
1. Copy my .config file to the source directory, in case it changes with bisect
2. make -j4 menuconfig, and then just exit and save, just to save .config with
any automatic changes needed for this source
3. Remove space hogs and any prior configuration: rm -r
/usr/src/linux-next/debian/ /boot/vmlinuz-5.12* /boot/initrd-5.12*
/usr/src/linux-image-5.12*
4. make -j4 deb-pkg
5. Install the kernel just built, and update grub accordingly: dpkg -i
../linux-image-5.12*_*.deb
6. Power off the computer
7. Power on and boot the new kernel
8. Test the bug (if its designation changes to "hw:USB1" I expect it'll be
working, but still test it): arecord -D hw:UA101 -f S24_3LE -r 48000 -c 2
./ua101.wav
9. If it records without the error: cd /usr/src/linux-next ; git bisect good,
Or with the error: cd /usr/sr/src/linux-next; git bisect bad
10. Repeat 1-10 until I got the output I gave you above.
I was under the assumption that running "git bisect {good,bad}" was enough to
checkout the next version that needed to be tested, and it seems that it must
have been. This is because I had quite a few that didn't work, then one that
did and another that didn't, eventually ending with the remaining few all
working.
If I, indeed, needed to be running checkout (as, say step 0.5),
/usr/src/linux-next/.git/refs/bisect contains a logged list of the first bad
and some good commits. Reverting each commit previously tested (logged) and
retesting sounds even more time consuming, but if you don't mind waiting and
think it's necessary, I will continue this endeavor, and eventually get back to
you.
--
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 18: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
2021-06-02 18:15 ` bugzilla-daemon [this message]
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-eCpCjBUvSI@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.