From: Greg KH <gregkh@linuxfoundation.org>
To: "Seïfane Idouchach" <seifane53@gmail.com>
Cc: dirk.behme@de.bosch.com, rafael@kernel.org, dakr@kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
stable@vger.kernel.org
Subject: Re: [REGRESSION] Long boot times due to USB enumeration
Date: Fri, 7 Mar 2025 15:07:03 +0100 [thread overview]
Message-ID: <2025030718-dwindle-degrading-94d3@gregkh> (raw)
In-Reply-To: <CAMpRfLMakzeazr91DBVyZQnin7y6L9RB+sPFb59U1QZvY3+KBQ@mail.gmail.com>
On Fri, Mar 07, 2025 at 08:58:04PM +0800, Seïfane Idouchach wrote:
> Dear all,
>
> I continued bisecting and while applying Dan's fix (15fffc6a5624) along the way.
> While the patch solves the problem for some commits it seems I am
> hitting another commit that exhibits the error again
> (25f51b76f90f10f9bf2fbc05fc51cf685da7ccad).
That is a totally different change, I think you have something odd here
as these bisection points are very confusing.
> I tested on top of v6.14-rc5 (7eb172143d5508) which has the issue,
> applying the fix and reverting the bad commit (25f51b76f90f10) fixes
> it.
> Both the applying fix and the revert are needed to resolve the issue.
>
> Let me know your thoughts on this.
I think you have a mix of problems here. Let's fix up all of those
error messages in the log first. Dan's fix has nothing to do with that
at all, once the USB bus connection stuff is resolved, then it should be
ok.
As that xhci commit you point at is showing an issue, are you sure that
you are properly building the right xhci driver into the system? Do you
have a Renesas xhci controller? What is the output of 'lspci'?
thanks,
greg k-h
next prev parent reply other threads:[~2025-03-07 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 16:32 [REGRESSION] Long boot times due to USB enumeration Seïfane Idouchach
2025-03-05 18:09 ` Greg KH
2025-03-05 19:57 ` Seïfane Idouchach
2025-03-07 12:58 ` Seïfane Idouchach
2025-03-07 14:07 ` Greg KH [this message]
2025-03-07 15:45 ` Seïfane Idouchach
2025-03-08 9:06 ` Seïfane Idouchach
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=2025030718-dwindle-degrading-94d3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dakr@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=seifane53@gmail.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox