From: "Ryan Walklin" <ryan@testtoast.com>
To: "Ping-Ke Shih" <pkshih@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-sunxi@lists.linux.dev" <linux-sunxi@lists.linux.dev>
Subject: Re: [BUG] RTL8821CS panic on entering power-save mode
Date: Sun, 17 Mar 2024 21:40:39 +1300 [thread overview]
Message-ID: <9ef4c29f-de98-4192-bf5d-1b2802496761@app.fastmail.com> (raw)
In-Reply-To: <902ff7d3d6221f28df21c2e5b3e743671355c874.camel@realtek.com>
On Sat, 16 Mar 2024, at 2:47 AM, Ping-Ke Shih wrote:
> This is because it is trying to enter PS mode but TX queue is still not empty.
> If power consumption is not big deal to you, try to turn off PS by
> iw wlan0 set power_save off
>
> I think messages can be disappear.
I would prefer to have power-saving on as it is a portable device but this does stop the remaining messages about the queue.
Finally I get extensive logging of
[ 1137.214502] Bluetooth: hci0: Out-of-order packet arrived (0 != 1)
[ 1142.185255] Bluetooth: hci0: Out-of-order packet arrived (1 != 2)
[ 1142.319504] Bluetooth: hci0: Out-of-order packet arrived (2 != 3)
[ 1142.446742] Bluetooth: hci0: Out-of-order packet arrived (3 != 4)
[ 1142.574117] Bluetooth: hci0: Out-of-order packet arrived (4 != 5)
[ 1143.160501] Bluetooth: hci0: Out-of-order packet arrived (5 != 6)
[ 1143.287232] Bluetooth: hci0: Out-of-order packet arrived (6 != 7)
When I am running a bluetooth scan and/or connecting to a device, this seems harmless but does spam dmesg quite a bit.
Thanks,
Ryan
prev parent reply other threads:[~2024-03-17 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 22:42 [BUG] RTL8821CS panic on entering power-save mode Ryan Walklin
2024-03-13 6:05 ` Ping-Ke Shih
2024-03-13 20:11 ` [BUG] rtw88: RTL8821CS warning " Ryan Walklin
2024-03-15 9:30 ` [BUG] RTL8821CS panic " Ryan Walklin
2024-03-15 13:47 ` Ping-Ke Shih
2024-03-17 8:40 ` Ryan Walklin [this message]
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=9ef4c29f-de98-4192-bf5d-1b2802496761@app.fastmail.com \
--to=ryan@testtoast.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-wireless@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