All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jens Axboe <axboe@kernel.dk>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: next-20250327 - lockdep whine and USB issues at boot
Date: Mon, 31 Mar 2025 17:21:01 +0800	[thread overview]
Message-ID: <Z-peffTZ7lVo3m5n@fedora> (raw)
In-Reply-To: <7755.1743228130@turing-police>

On Sat, Mar 29, 2025 at 02:02:10AM -0400, Valdis Klētnieks wrote:
> On Sat, 29 Mar 2025 10:06:39 +0800, Ming Lei said:
> > On Fri, Mar 28, 2025 at 02:10:53PM -0400, Valdis Kl??tnieks wrote:
> > > Saw this during boot on a Dell Inspiron 5559 laptop.  
> > > 
> > > In addition, the external USB ports all gave up, rendering a USB mouse and a
> > > USB external drive totally dead in the water.  May or may not be related, I didn't
> > > dig too far into it.
> >
> > It shouldn't be related to the warning.
> 
> > For this lockdep warning, feel free to try patch in the following link:
> >
> > https://lore.kernel.org/linux-block/Z-dUCLvf06SfTOHy@fedora/
> 
> After applying that patch, USB *didn't* die during boot.  So apparently
> *something* changed.  

That is surprising, and maybe the USB die isn't 100% thing.

> 
> Also, the patch merely caused a *different* lockdep warning.
> Rather than  &q->q_usage_counter(io) and &q->elevator_lock, the
> new one is &q->elevator_lock versus pcpu_alloc_mutex...
> 
> Looks like it's a bit more convoluted than first looked?

That is another story wrt. freeze lock, fs_reclaim & percpu allocator
lock, looks one real risk, I will try to work one patch and see if
all can be addressed.



Thanks,
Ming


      reply	other threads:[~2025-03-31  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 18:10 next-20250327 - lockdep whine and USB issues at boot Valdis Klētnieks
2025-03-28 20:32 ` Luck, Tony
2025-03-29  2:06 ` Ming Lei
2025-03-29  6:02   ` Valdis Klētnieks
2025-03-31  9:21     ` Ming Lei [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=Z-peffTZ7lVo3m5n@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=valdis.kletnieks@vt.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 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.