All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 07 May 2021 02:21:07 +0000	[thread overview]
Message-ID: <bug-212955-208809-2YmDFlHpAd@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 #8 from Lucas Endres (jaffa225man@gmail.com) ---
Created attachment 296683
  --> https://bugzilla.kernel.org/attachment.cgi?id=296683&action=edit
dmesg USB 2 port working on 5.9.0

Here is the dmesg output from the same USB2 port, but working on the older
5.9.0 kernel.

Thanks for the tip about "--shallow-exclude=".  I used it so far to limit it to
5.11 (since I think it had been working on it), like so:
git clone --shallow-exclude=v5.11
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

It was much smaller, being only 332.27 MiB in total.  Now I just have to read
up about how to use bisect.  Hopefully I'll be able to easily "make uninstall"
when all through testing, as I prefer using debian's package management, and
don't want leftover pieces taking up space.

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2021-05-07  2:21 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 [this message]
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
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-2YmDFlHpAd@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.