All the mail mirrored from 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: Sat, 08 May 2021 03:10:20 +0000	[thread overview]
Message-ID: <bug-212955-208809-snyhZcsZ8r@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 #10 from Lucas Endres (jaffa225man@gmail.com) ---
Thanks for your thoughts!  I helped to test a change on snd-ua101 to fix its
MIDI port not being created, but think it just blacklists the UA-101 from the
snd-usb-audio driver, since it was conflicting.  Here's a link to that
discussion: https://bugzilla.kernel.org/show_bug.cgi?id=212477

Also, there have been substantial quality Roland/EDIROL/BOSS detection quirk
tweaks to snd-usb-audio (also with my championing and testing), but if I
understand correctly, they shouldn't be affecting the UA-101, due to its use of
only snd-ua101: https://bugzilla.kernel.org/show_bug.cgi?id=212519

Sorry I hadn't mentioned these before, but until now I thought they could have
nothing to do with this issue.

In the next few days I hope to have time to attempt bisection to get to the
bottom of it all.

-- 
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-08  3:10 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 [this message]
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-snyhZcsZ8r@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.