From: Thorsten Leemhuis <linux@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH v2] usb: core: reduce power-on-good delay time of root hub
Date: Tue, 9 Nov 2021 11:28:54 +0100 [thread overview]
Message-ID: <c156e850-2aa6-33e5-37c6-efcc2fd72b42@leemhuis.info> (raw)
In-Reply-To: <fd7df619-3eba-b142-cc20-97edf9f20c4d@leemhuis.info>
On 01.11.21 17:46, Thorsten Leemhuis wrote:
> On 01.11.21 04:33, Walt Jr. Brake wrote:
>> Three month ago, My USB 3.1 device cannot be detected after upgrade
>> kernel from version 5.10.41 to 5.10.42.
>>
>> And I found some other people ran into the same issue:
>>
>> https://forum.manjaro.org/t/kernel-5-10-59-doesnt-detect-a-connected-usb-external-disk/79320
>>
>> https://forum.manjaro.org/t/how-to-make-active-usb-hub-work-in-manjaro/84548
>>
>>
>> Two days ago, I try to fix the issue myself, and I found out that it was
>> cause by this patch. After revert this patch, my USB 3.1 device can be
>> detect again.
>>
>> I have already file a bug on here:
>> https://bugzilla.kernel.org/show_bug.cgi?id=214875.
>
> #regzbot ^introduced 90d28fb53d4a51299ff324dede015d5cb11b88a2
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=214875
#regzbot fixed-by e1959faf085b004e6c3afaaaa743381f00e7c015
#regzbot ignore-activity
BTW, to anyone is reading this and wondering why it's needed: regzbot
needed the above, as the fix for this regression(¹) lacked a Link: tag
with the URL to the report. It it had been there, regzbot would have
automatically noticed the fix when it showed up in next.
Thinking aloud: The fix was posted in the thread with the regression
report. Regzbot could be enhanced to detect such cases automatically.
Thinking aloud, too: regzbot could be enhanced to notice if a mail or a
commit mentioned a commit-id that is known to cause a tracked regression.
I guess the former might not be worth it, the latter OTOH might be a
good idea I will keep in mind.
Ciao, Thorsten
(¹)
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e1959faf085b004e6c3afaaaa743381f00e7c015
prev parent reply other threads:[~2021-11-09 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1618017645-12259-1-git-send-email-chunfeng.yun@mediatek.com>
[not found] ` <c639c965-5231-b745-7b59-476877202e0c@gmail.com>
2021-11-01 16:46 ` [PATCH v2] usb: core: reduce power-on-good delay time of root hub Thorsten Leemhuis
2021-11-02 6:41 ` Thorsten Leemhuis
2021-11-09 10:28 ` Thorsten Leemhuis [this message]
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=c156e850-2aa6-33e5-37c6-efcc2fd72b42@leemhuis.info \
--to=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).