[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220308162416.xnrlys6utylzb3uz@houat>
Date: Tue, 8 Mar 2022 17:24:16 +0100
From: Maxime Ripard <maxime@...no.tech>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jiri Slaby <jirislaby@...nel.org>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Deadlock at reboot?
Hi,
On Fri, Mar 04, 2022 at 03:15:36PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Mar 04, 2022 at 11:49:42AM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > I'm not entirely sure who I'm supposed to send this to, so apologies if
> > I forgot somebody.
> >
> > I've had an issue when rebooting on and off for a couple of monthes, but
> > I got a stacktrace from lockdep today:
> >
> > [71721.872904] reboot: Restarting system
> > [71721.876743] ------------[ cut here ]------------
> > [71721.877081]
> > [71721.877084] ======================================================
> > [71721.877086] WARNING: possible circular locking dependency detected
> > [71721.877088] 5.17.0-rc6-next-20220303-v8+ #10 Not tainted
>
> This is linux-next, does this also happen on Linus's tree?
>
> If not, can you bisect to find the offending commit?
So it turns out the reboot stuck issue was a bootloader issue that
wouldn't detect the ethernet phy after a patch was introduced in 5.16.
So nothing to do with the lockdep stacktrace, really. If there's indeed
a locking issue, it doesn't seem to affect my system.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists