From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219824] [6.13 regression] USB controller just died
Date: Sat, 08 Mar 2025 06:56:59 +0000 [thread overview]
Message-ID: <bug-219824-208809-b2SPRg4yY6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219824-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219824
--- Comment #20 from Michał Pecio (michal.pecio@gmail.com) ---
Sorry about Reported-by, but if I added that then they would also want a Closes
and I wasn't sure if it really is this bug. It's something I produced on my
machine under my workload, using knowledge of how one commit is broken.
I guess I could have taken a gamble and tagged it anyway because it seemed
likely, but I had no confirmation and no idea if I would get any by the end of
the week. Indeed, to this day the best I've seen is reports that downgrading to
6.12 helps, I haven't heard from anyone previously affected reverting the
suspect patch.
Like Mathias, I was expecting some nightmare scenario and not that. I hope that
this is all there was to it, but we will really know next week.
My patch made it to Greg's usb-linus branch, which normally means it will land
in the next -rc tomorrow and then propagate to stable. No other -rc has it
because they were released before it existed.
--
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:[~2025-03-08 6:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 22:23 [Bug 219824] New: [6.13 regression] USB controller just died bugzilla-daemon
2025-02-26 22:28 ` [Bug 219824] " bugzilla-daemon
2025-02-26 22:31 ` bugzilla-daemon
2025-02-26 22:47 ` bugzilla-daemon
2025-02-27 12:58 ` bugzilla-daemon
2025-02-27 15:12 ` bugzilla-daemon
2025-02-27 16:05 ` bugzilla-daemon
2025-02-27 17:14 ` bugzilla-daemon
2025-02-27 21:07 ` bugzilla-daemon
2025-02-28 19:49 ` bugzilla-daemon
2025-02-28 20:10 ` bugzilla-daemon
2025-03-03 13:54 ` bugzilla-daemon
2025-03-03 15:42 ` bugzilla-daemon
2025-03-03 19:23 ` bugzilla-daemon
2025-03-03 22:38 ` bugzilla-daemon
2025-03-06 11:15 ` bugzilla-daemon
2025-03-06 11:54 ` bugzilla-daemon
2025-03-06 11:57 ` bugzilla-daemon
2025-03-06 12:03 ` bugzilla-daemon
2025-03-07 23:28 ` bugzilla-daemon
2025-03-08 6:56 ` bugzilla-daemon [this message]
2025-03-14 8:42 ` bugzilla-daemon
2025-03-14 9:06 ` bugzilla-daemon
2025-03-14 10:49 ` 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-219824-208809-b2SPRg4yY6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.