Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <54debab9a79df628cff86a637dde13c281001578.camel@sipsolutions.net>
Subject: Re: [BISECTED] 5.12 hangs at reboot
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Harald Arnesen <harald@skogtun.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Date:   Mon, 26 Apr 2021 21:38:28 +0200
In-Reply-To: <34d778fa-343f-912f-2fd7-a8ba49bd1b95@skogtun.org>
References: <09464e67-f3de-ac09-28a3-e27b7914ee7d@skogtun.org>
         <CAHk-=wgA1Ma6e5qZO1EP9oMveLPJFbj=SC1R0ZewCmC-u0_r=A@mail.gmail.com>
         <34d778fa-343f-912f-2fd7-a8ba49bd1b95@skogtun.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 2021-04-26 at 19:29 +0000, Harald Arnesen wrote:
> > Which implies that it's likely something fairly specific to  your
> > setup (either the config or the hardware - or possibly Void Linux
> > doing something other distros don't).
> 
> Init system is runit, not systemd? Could that affect something?

Unlikely.

> > Mind also attaching a dmesg of an affected kernel (or with the revert
> > in place, I guess - it shouldn't matter until the reboot ;)
> 
> dmesg from 5.12 without the revert is attached.

That's it? There it just hangs? Not even printing something about tasks
getting stuck? Did you let it sit for a couple of (2-3) minutes to see
the task stuck warnings?

What's weird though is that this is evidently with mac80211 - so
certainly all the patches I just sent out will do nothing for you, and
something else is strange, because mac80211 I've definitely not just
reviewed but also tested these code paths many times.

Hmm. But yeah, either way, a lockdep report or stack dump will surely
help. Perhaps something in the ath* driver you're using that I missed.

> > There's a lockdep assertion there, but you don't seem to have lockdep
> > enabled. So it be interesting to see what happens if you
> > 
> >  (a) enable lockdep
> 
> Will report when I have tried it.

Thanks.

johannes