From: Maxime Ripard <maxime@cerno.tech>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Deadlock at reboot?
Date: Fri, 4 Mar 2022 16:32:28 +0100 [thread overview]
Message-ID: <20220304153228.eqclo7sezczzs2t4@houat> (raw)
In-Reply-To: <20220304152042.xvyxxen6yyxgx4bh@houat>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Fri, Mar 04, 2022 at 04:20:42PM +0100, Maxime Ripard wrote:
> Hi Greg,
>
> 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?
>
> Like I said, it appeared with multiple versions across the past few
> monthes (I only ever got the trace with that next-version though) so I'm
> not sure the issue has been introduced recently.
>
> I'll try a couple of recent Linus' tags, and bisect if I can find
> something of interest.
It happens with 5.17-rc6, I'll try with older releases
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-03-04 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 10:49 Deadlock at reboot? Maxime Ripard
2022-03-04 14:15 ` Greg Kroah-Hartman
2022-03-04 15:20 ` Maxime Ripard
2022-03-04 15:32 ` Maxime Ripard [this message]
2022-03-08 16:24 ` Maxime Ripard
[not found] <CANgUfue6rVEwfF38dDChFvQk5iKo33+-Jb1yxrXisahTWtPHKg@mail.gmail.com>
2022-03-04 15:19 ` Maxime Ripard
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=20220304153228.eqclo7sezczzs2t4@houat \
--to=maxime@cerno.tech \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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