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: Wed, 02 Jun 2021 04:07:40 +0000	[thread overview]
Message-ID: <bug-212955-208809-QrSqF3an1C@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 #11 from Lucas Endres (jaffa225man@gmail.com) ---
(In reply to Lucas Endres from comment #10)
> In the next few days I hope to have time to attempt bisection to get to the
> bottom of it all.

Sorry it took me so long (please let me know if it's been noticed and fixed
already), but I finally have gotten through all the bisects to reveal this
commit (I don't think it's what anyone was expecting):

51e6f07cb12e50bfc71181bd08bad5f0a9b5e9e2 is the first bad commit
commit 51e6f07cb12e50bfc71181bd08bad5f0a9b5e9e2
Merge: 5e321ded30 6b3788e5fb
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue May 4 10:48:05 2021 -0700

    Merge tag 'm68knommu-for-v5.13' of
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu

    Pull m68knommu updates from Greg Ungerer:

     - a fix for interrupt number range checking for the ColdFire SIMR
       interrupt controller.

     - changes for the binfmt_flat binary loader to allow RISC-V nommu
       support it needs to be able to accept flat binaries that have no gap
       between the text and data sections.

    * tag 'm68knommu-for-v5.13' of
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu:
      m68k: coldfire: fix irq ranges
      riscv: Disable data start offset in flat binaries
      binfmt_flat: allow not offsetting data start

 arch/m68k/coldfire/intc-simr.c | 12 ++++++------
 arch/riscv/Kconfig             |  1 +
 fs/Kconfig.binfmt              |  3 +++
 fs/binfmt_flat.c               | 18 +++++++++++++-----
 4 files changed, 23 insertions(+), 11 deletions(-)


Thanks for any suggestions I may be needing to test,

  Lucas

-- 
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-06-02  4:07 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 [this message]
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-QrSqF3an1C@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.