From: Larry Finger <Larry.Finger@lwfinger.net>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Ping-Ke Shih <pkshih@realtek.com>
Subject: Re: [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup
Date: Wed, 22 Mar 2023 11:57:21 -0500 [thread overview]
Message-ID: <55057734-9913-8288-ad88-85c189cbe045@lwfinger.net> (raw)
In-Reply-To: <ZBskz06HJdLzhFl5@hyeyoo>
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
next prev parent reply other threads:[~2023-03-22 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:54 [BUG v6.2.7] Hitting BUG_ON() on rtw89 wireless driver startup Hyeonggon Yoo
2023-03-22 16:57 ` Larry Finger [this message]
2023-03-22 20:52 ` Jonas Gorski
2023-03-23 0:59 ` Ping-Ke Shih
2023-03-23 1:36 ` Larry Finger
2023-03-23 1:41 ` Larry Finger
2023-03-23 8:36 ` Ping-Ke Shih
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=55057734-9913-8288-ad88-85c189cbe045@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=42.hyeyoo@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.com \
/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