Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Larry Finger <larry.finger@gmail.com>
Message-ID: <55057734-9913-8288-ad88-85c189cbe045@lwfinger.net>
Date:   Wed, 22 Mar 2023 11:57:21 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.9.0
Subject: Re: [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup
To:     Hyeonggon Yoo <42.hyeyoo@gmail.com>, netdev@vger.kernel.org,
        linux-wireless@vger.kernel.org, Ping-Ke Shih <pkshih@realtek.com>
References: <ZBskz06HJdLzhFl5@hyeyoo>
Content-Language: en-US
From:   Larry Finger <Larry.Finger@lwfinger.net>
In-Reply-To: <ZBskz06HJdLzhFl5@hyeyoo>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 3/22/23 10:54, Hyeonggon Yoo wrote:
> 
> Hello folks,
> I've just encountered weird bug when booting Linux v6.2.7
> 
> config: attached
> dmesg: attached
> 
> I'm not sure exactly how to trigger this issue yet because it's not
> stably reproducible. (just have encountered randomly when logging in)
> 
> At quick look it seems to be related to rtw89 wireless driver or network subsystem.

Your bug is weird indeed, and it does come from rtw89_8852be. My distro has not 
yet released kernel 6.2.7, but I have not seen this problem with mainline 
kernels throughout the 6.2 or 6.3 development series.

One thing that would have been helpful is to include any rtw89 entries in the 
dmesg log that appeared BEFORE the BUG. For instance, I have no idea what 
firmware level you are running, etc.

If you are willing, I would like you to 'git clone 
https://github.com/lwfinger/rtw89.git'. You would likely need to install the 
packages needed to build an out-of-kernel driver as shown in README.md in the 
repo. You would also need to blacklist rtw89_8852be, which would interfere with 
rtw_8852be coming from the new repo. The code in the repo matches what will be 
in kernel 6.3+, and it would be instructive if there is something in your system 
that triggers this problem. I have never seen anything like this.

Larry