public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: retry efuse physical map dump on transient failure
Date: Mon, 2 Mar 2026 05:47:30 +0000	[thread overview]
Message-ID: <c751f9505a664f6895bacecb62bc534a@realtek.com> (raw)
In-Reply-To: <20260301042422.195491-1-christianshewitt@gmail.com>

Christian Hewitt <christianshewitt@gmail.com> wrote:
> On Radxa Rock 5B with a RTL8852BE combo WiFi/BT card, the efuse
> physical map dump intermittently fails with -EBUSY during probe.
> The failure occurs in rtw89_dump_physical_efuse_map_ddv() where
> read_poll_timeout_atomic() times out waiting for the B_AX_EF_RDY
> bit after 1 second.

I'm checking internally how we handle this case.

[...]

> 
> For context, firmware also fails (and recovers) sometimes:

Did you mean this doesn't always happen? sometimes?

We has seen similar log because of 36-bit DMA. Try below to force 32- or 36-
bit DMA to see if it can resolve problem in your platform.

diff --git a/drivers/net/wireless/realtek/rtw89/pci.c b/drivers/net/wireless/realtek/rtw89/pci.c
index 43c61b3dc969..9d003ab93c85 100644
--- a/drivers/net/wireless/realtek/rtw89/pci.c
+++ b/drivers/net/wireless/realtek/rtw89/pci.c
@@ -3305,6 +3305,8 @@ static bool rtw89_pci_is_dac_compatible_bridge(struct rtw89_dev *rtwdev)
        if (!bridge)
                return false;

+       return true; // or force to return false;
+
        switch (bridge->vendor) {
        case PCI_VENDOR_ID_INTEL:
                return true;

> 
> ROCK5B:~ # dmesg | grep rtw89
> [    6.436873] rtw89_8852be 0002:21:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
> [    6.437165] rtw89_8852be 0002:21:00.0: enabling device (0000 -> 0003)
> [    6.450228] rtw89_8852be 0002:21:00.0: Firmware version 0.29.29.15 (6fb3ec41), cmd version 0, type 5
> [    6.450239] rtw89_8852be 0002:21:00.0: Firmware version 0.29.29.15 (6fb3ec41), cmd version 0, type 3
> [    7.864148] rtw89_8852be 0002:21:00.0: fw security fail
> [    7.864154] rtw89_8852be 0002:21:00.0: download firmware fail
> [    7.864160] rtw89_8852be 0002:21:00.0: [ERR]fwdl 0x1E0 = 0x62
> [    7.864165] rtw89_8852be 0002:21:00.0: [ERR]fwdl 0x83F0 = 0x80011
> [    7.864173] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864188] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864203] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864219] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864234] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864250] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864265] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864281] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864296] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864311] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864327] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864342] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931150
> [    7.864358] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864373] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    7.864387] rtw89_8852be 0002:21:00.0: [ERR]fw PC = 0xb8931154
> [    8.181342] rtw89_8852be 0002:21:00.0: chip info CID: 0, CV: 1, AID: 0, ACV: 1, RFE: 1
> [    8.184322] rtw89_8852be 0002:21:00.0: rfkill hardware state changed to enable
> 



  reply	other threads:[~2026-03-02  5:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01  4:24 [PATCH] wifi: rtw89: retry efuse physical map dump on transient failure Christian Hewitt
2026-03-02  5:47 ` Ping-Ke Shih [this message]
2026-03-02  5:55   ` Christian Hewitt
2026-03-02  6:04     ` Ping-Ke Shih
2026-03-02  6:17       ` Christian Hewitt
2026-03-09  2:35         ` Ping-Ke Shih
2026-03-10 17:16           ` Christian Hewitt
2026-03-11  3:05             ` Ping-Ke Shih
2026-03-11  4:20               ` Christian Hewitt
2026-03-12  2:22                 ` Ping-Ke Shih
2026-03-12  5:58                   ` Christian Hewitt
2026-03-12  7:39                     ` Ping-Ke Shih
2026-03-12  8:11                       ` Christian Hewitt
2026-03-12  8:28                         ` Ping-Ke Shih
2026-03-16  5:32 ` Ping-Ke Shih
2026-03-16 11:03   ` Christian Hewitt
2026-03-17  1:37     ` Ping-Ke Shih
2026-03-17  6:15       ` Christian Hewitt

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=c751f9505a664f6895bacecb62bc534a@realtek.com \
    --to=pkshih@realtek.com \
    --cc=christianshewitt@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rtl8821cerfe2@gmail.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