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>
 <CAHk-=wgA1Ma6e5qZO1EP9oMveLPJFbj=SC1R0ZewCmC-u0_r=A@mail.gmail.com>
 <34d778fa-343f-912f-2fd7-a8ba49bd1b95@skogtun.org> <54debab9a79df628cff86a637dde13c281001578.camel@sipsolutions.net>
 <CAHk-=wjvVMucgoAQKfi-x=jvYgKW1_LRmvnAfk3JGMkOSg9CQQ@mail.gmail.com> <2cafd6d0c6378b36644d04fe263a53a866354574.camel@sipsolutions.net>
In-Reply-To: <2cafd6d0c6378b36644d04fe263a53a866354574.camel@sipsolutions.net>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 26 Apr 2021 12:51:27 -0700
Message-ID: <CAHk-=wiwByiEUuO-NN=xHb4sxwCmP=tjB_vUHEebj8+-JGu8zg@mail.gmail.com>
Subject: Re: [BISECTED] 5.12 hangs at reboot
To:     Johannes Berg <johannes@sipsolutions.net>
Cc:     Harald Arnesen <harald@skogtun.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Apr 26, 2021 at 12:46 PM Johannes Berg
<johannes@sipsolutions.net> wrote:
>
> Right. Maybe if it's modules, could try to remove them rather than
> reboot?

Yes, doing an 'rmmod ath9k'  (or whatever that module is called)
sounds like a good idea, it might trigger the same lockup.

In fact, that might be the reason Harald sees this - maybe Void Linux
tries to unload modules before rebooting, and other distros don't?

Unloading modules doesn't tend to get a lot of testing, it's a fairly
unusual operation (and not one that is guaranteed to be safe - yes we
do basic module refcounting, but it's very basic indeed, not full).

               Linus