linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AC <achirvasub@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
	Jes Sorensen <Jes.Sorensen@gmail.com>,
	linux-wireless@vger.kernel.org
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: PROBLEM: 5.6.0-rc6 + Realtek RTL8188CUS wifi dongle: 8051 reset failed!
Date: Tue, 17 Mar 2020 02:44:21 -0400	[thread overview]
Message-ID: <C9F34A4B-E3F3-4D7A-B870-058C8D4871B9@gmail.com> (raw)

I am on Debian 10.3 stable i386, running a custom-compiled kernel (I compile weekly, when new rc releases drop).

I keep the following USB wifi dongle connected to this machine:

ID 050d:1102 Belkin Components F7D1102 N150/Surf Micro Wireless Adapter v1000 [Realtek RTL8188CUS]


---

The problem: 

As of 5.6.0-rc6, booting up with the dongle connected returns a number of dmesg complaints:

--- cut here ---

[    9.448337] rtl8192cu: MAC auto ON okay!          [    9.579025] rtl8192cu: Tx queue select: 0x05      [   10.475308] rtl8192c_common: Polling FW ready fail! REG_MCUFWDL:0x00030006.                            [   10.478213] rtl8192c_common: Firmware is not ready to run!                                             [   10.960093] rtl8192cu: 8051 reset failed!.........................                                     [   10.971027] rtl8192cu: MAC auto ON okay!          [   11.101691] rtl8192cu: Tx queue select: 0x05

--- end ---

Occasionally, this results in a timeout while trying to reach network.target (systemd). 

Afterwards, there's endless dmesg noise Re: rtl8192cu:

--- cut here ---

[11391.204555] rtl8192cu: Tx queue select: 0x05      [11707.050480] rtl8192cu: MAC auto ON okay!          [11707.181118] rtl8192cu: Tx queue select: 0x05      [12023.057056] rtl8192cu: MAC auto ON okay!          [12023.187727] rtl8192cu: Tx queue select: 0x05
[12339.060183] rtl8192cu: MAC auto ON okay!          [12339.199316] rtl8192cu: Tx queue select: 0x05      [12655.054140] rtl8192cu: MAC auto ON okay!          [12655.184789] rtl8192cu: Tx queue select: 0x05      [12971.053948] rtl8192cu: MAC auto ON okay!          [12971.184600] rtl8192cu: Tx queue select: 0x05      [13287.062712] rtl8192cu: MAC auto ON okay!          [13287.193363] rtl8192cu: Tx queue select: 0x05      [13603.065987] rtl8192cu: MAC auto ON okay!          [13603.196641] rtl8192cu: Tx queue select: 0x05      [13919.066617] rtl8192cu: MAC auto ON okay!          [13919.197270] rtl8192cu: Tx queue select: 0x05      [14235.060621] rtl8192cu: MAC auto ON okay!          [14235.191277] rtl8192cu: Tx queue select: 0x05      [14551.055104] rtl8192cu: MAC auto ON okay!          [14551.185741] rtl8192cu: Tx queue select: 0x05      [14867.051799] rtl8192cu: MAC auto ON okay!          [14867.182451] rtl8192cu: Tx queue select: 0x05      [14878.855070] perf: interrupt took too long (7897 > 7896), lowering kernel.perf_event_max_sample_rate to 25250

--- end ---

There are large swaths of this in dmesg.


             reply	other threads:[~2020-03-17  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17  6:44 AC [this message]
2020-03-17 14:52 ` PROBLEM: 5.6.0-rc6 + Realtek RTL8188CUS wifi dongle: 8051 reset failed! Larry Finger
2020-03-17 16:03   ` AC

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=C9F34A4B-E3F3-4D7A-B870-058C8D4871B9@gmail.com \
    --to=achirvasub@gmail.com \
    --cc=Jes.Sorensen@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).