public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	stern@rowland.harvard.edu, oneukum@suse.com,
	konrad.dybcio@oss.qualcomm.com, stable@kernel.org
Subject: Re: [PATCH 1/1] usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm
Date: Fri, 27 Jun 2025 16:51:34 +0300	[thread overview]
Message-ID: <50cbe7a8-c103-4922-b06b-d183a37ee08d@linux.intel.com> (raw)
In-Reply-To: <aF5rNp1l0LWITnEB@finisterre.sirena.org.uk>

On 27.6.2025 12.58, Mark Brown wrote:
> On Thu, Jun 26, 2025 at 04:01:02PM +0300, Mathias Nyman wrote:
>> Delayed work to prevent USB3 hubs from runtime-suspending immediately
>> after resume was added in commit 8f5b7e2bec1c ("usb: hub: fix detection
>> of high tier USB3 devices behind suspended hubs").
>>
>> This delayed work needs be flushed if system suspends, or hub needs to
>> be quiesced for other reasons right after resume. Not flushing it
>> triggered issues on QC SC8280XP CRD board during suspend/resume testing.
>>
>> Fix it by flushing the delayed resume work in hub_quiesce()
> 
> I'm seeing NFS boot failures on the Raspberry Pi 3B+ in pending-fixes
> which bisect to this commit.  The networking fails to come up so the
> rootfs can't be mounted, the ethernet on these boards is USB based.
> 
> Full log:
> 
>     https://lava.sirena.org.uk/scheduler/job/1516948#L1142
> 

Thanks for the report

The Raspberry Pi 3B+ doesn't have USB3 ports, so it should not be due
to pending post resume work.

The same hub->init_work is however used for other purposes as well, it
could be that we end up flushing some other work.

If I write a v2 patch that puts this post resume work into its own
dedicated work item, and only flushes that, could you try it out
on the Raspberry Pi 3B+

Same with the QC SC8280XP CRD board, would be grateful if Konrad could
try out a version 2.

Thanks
Mathias

  reply	other threads:[~2025-06-27 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 13:01 [PATCH 0/1] Fix "detection of high tier USB3 devices" patch in usb-linus Mathias Nyman
2025-06-26 13:01 ` [PATCH 1/1] usb: hub: Fix flushing and scheduling of delayed work that tunes runtime pm Mathias Nyman
2025-06-27  9:58   ` Mark Brown
2025-06-27 13:51     ` Mathias Nyman [this message]
2025-06-27 13:52       ` Konrad Dybcio
2025-06-27 13:56       ` Mark Brown
2025-06-27 16:01     ` Mark Brown
2025-06-26 14:58 ` [PATCH 0/1] Fix "detection of high tier USB3 devices" patch in usb-linus Greg KH

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=50cbe7a8-c103-4922-b06b-d183a37ee08d@linux.intel.com \
    --to=mathias.nyman@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stable@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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