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;
MIME-Version: 1.0
References: <09464e67-f3de-ac09-28a3-e27b7914ee7d@skogtun.org>
In-Reply-To: <09464e67-f3de-ac09-28a3-e27b7914ee7d@skogtun.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 26 Apr 2021 11:59:31 -0700
Message-ID: <CAHk-=wgA1Ma6e5qZO1EP9oMveLPJFbj=SC1R0ZewCmC-u0_r=A@mail.gmail.com>
Subject: Re: [BISECTED] 5.12 hangs at reboot
To:     Harald Arnesen <harald@skogtun.org>
Cc:     johannes.berg@intel.com,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Apr 26, 2021 at 11:47 AM Harald Arnesen <harald@skogtun.org> wrote:
>
> Bisected to commit 776a39b8196dbca4afb69669db0d9926ffac29ab, and
> reverting this makes the machine reboot as usual.

Hmm. That was already in rc1, so this isn't some late untested
last-minute commit that broke things for you.

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).

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

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

 (b) make sure to reboot in text mode so that any lockdep messages
would actually be visible.

Maybe Johannes will go "Doh!" and see what's wrong.

                  Linus