TX2 WiFi : FIRMWARE HALTED (set BUS DOWN)

user111095 · December 29, 2021, 1:15pm

TX2 WiFi runs fine, but in one case of multiply devices (11 TX2s) with single AP, we got critical errors:

Dec 24 18:15:50 localhost kernel: [ 608.293851] INTERNAL ERROR: FIRMWARE HALTED : set BUS DOWN

Dec 24 18:15:50 localhost kernel: [ 608.295654] CONSOLE:

Dec 24 18:15:50 localhost kernel: [ 608.295658] CONSOLE: 000000.090 wl0: wlc_enable_probe_req: state down, deferring setting of host flags

Dec 24 18:15:50 localhost kernel: [ 608.295659] CONSOLE: 000588.221

Dec 24 18:15:50 localhost kernel: [ 608.295661] CONSOLE: FWID 01-e527e2ad

Dec 24 18:15:50 localhost kernel: [ 608.295662] CONSOLE: flags 1

Dec 24 18:15:50 localhost kernel: [ 608.295664] CONSOLE: 000588.221

Dec 24 18:15:50 localhost kernel: [ 608.295665] CONSOLE: TRAP 4(23fd88): pc 1a16de, lr 1842bd, sp 23fde0, cpsr 8000019f, spsr 800001bf

Dec 24 18:15:50 localhost kernel: [ 608.295667] CONSOLE: 000588.221 dfsr 8, dfar 2bbbc4

Dec 24 18:15:50 localhost kernel: [ 608.295669] CONSOLE: 000588.221 r0 0, r1 0, r2 2e613, r3 22b678, r4 20c830, r5 22b70c, r6 2bbbc4

Dec 24 18:15:50 localhost kernel: [ 608.295671] CONSOLE: 000588.221 r7 904e0, r8 22b6e4, r9 904e, r10 23b0fc, r11 23feb6, r12 23fd94

Dec 24 18:15:50 localhost kernel: [ 608.295672] CONSOLE: 000588.221

Dec 24 18:15:50 localhost kernel: [ 608.295673] CONSOLE: sp+0 0022b70c 0021aa34 0021a92c 0021a92c

Dec 24 18:15:50 localhost kernel: [ 608.295675] CONSOLE: 000588.221 sp+10 00000001 0023a51c 0023fef0 00000000

Dec 24 18:15:50 localhost kernel: [ 608.295676] CONSOLE:

Dec 24 18:15:50 localhost kernel: [ 608.295678] CONSOLE: 000588.221 sp+2c 0018e331

Dec 24 18:15:50 localhost kernel: [ 608.295679] CONSOLE: 000588.221 sp+44 0019e8ab

Dec 24 18:15:50 localhost kernel: [ 608.295681] CONSOLE: 000588.221 sp+cc 00055849

Dec 24 18:15:50 localhost kernel: [ 608.295682] CONSOLE: 000588.221 sp+fc 001a8d95

Dec 24 18:15:50 localhost kernel: [ 608.295683] CONSOLE: 000588.221 sp+13c 001b1ba1

Dec 24 18:15:50 localhost kernel: [ 608.295685] CONSOLE: 000588.221 sp+164 0018ae51

Dec 24 18:15:50 localhost kernel: [ 608.295686] CONSOLE: 000588.221 sp+17c 00016e77

Dec 24 18:15:50 localhost kernel: [ 608.295688] CONSOLE: 000588.221 sp+180 00016e4d

Dec 24 18:15:50 localhost kernel: [ 608.295689] CONSOLE: 000588.221 sp+18c 00016eb5

Dec 24 18:15:50 localhost kernel: [ 608.295690] CONSOLE: 000588.221 sp+19c 000170cf

Dec 24 18:15:50 localhost kernel: [ 608.295692] CONSOLE: 000588.221 sp+1a4 00183685

Dec 24 18:15:50 localhost kernel: [ 608.295693] CONSOLE: 000588.221 sp+1ac 001824f7

Dec 24 18:15:50 localhost kernel: [ 608.295694] CONSOLE: 000588.221 sp+1b8 000001df

Dec 24 18:15:50 localhost kernel: [ 608.295696] CONSOLE: 000588.221 sp+1f8 0001706b

Dec 24 18:15:50 localhost kernel: [ 608.295697] CONSOLE: 000588.221 sp+208 001855fb

Dec 24 18:15:50 localhost kernel: [ 608.295700] dhdsdio_checkdied: msgtrace address : 0x00000000

Dec 24 18:15:50 localhost kernel: [ 608.295700] console address : 0x0023DEBC

Dec 24 18:15:50 localhost kernel: [ 608.295700] Assrt not built in dongle

Dec 24 18:15:50 localhost kernel: [ 608.295700] Dongle trap type 0x4 @ epc 0x1a16de, cpsr 0x8000019f, spsr 0x800001bf, sp 0x23fde0,lp 0x1842bd, rpc 0x1a16de Trap offset 0x23fd88, r0 0x0, r1 0x0, r2 0x2e613, r3 0x22b678, r4 0x20c830, r5 0x22b70c, r6 0x2bbbc4, r7 0x904e0

Dec 24 18:15:50 localhost kernel: [ 608.295700]

Dec 24 18:15:50 localhost kernel: [ 608.295700]

Dec 24 18:15:50 localhost kernel: [ 608.295770] dhdsdio_dpc: failed backplane access over SDIO, halting operation

Dec 24 18:15:50 localhost kernel: [ 608.443318] dhd_start_xmit: xmit rejected pub.up=1 busstate=0

Dec 24 18:15:50 localhost kernel: [ 608.443349] dhd_start_xmit: Event HANG sent up

Dec 24 18:15:50 localhost kernel: [ 608.443427] [12-24 18:15:50.222] wl_cfg80211_disconnect: Reason 3

Dec 24 18:15:50 localhost kernel: [ 608.443437] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443443] dhd_check_hang: Event HANG send up due to re=0 te=0 e=-1 s=0

Dec 24 18:15:50 localhost kernel: [ 608.443447] dhd_check_hang: Event HANG send up due to re=0 te=0 e=-1 s=0

Dec 24 18:15:50 localhost kernel: [ 608.443453] wl_cfg80211_disconnect :

Dec 24 18:15:50 localhost kernel: [ 608.443455] error (-1)

Dec 24 18:15:50 localhost kernel: [ 608.443499] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443505] CFGP2P-ERROR) wl_cfgp2p_bss_isup :

Dec 24 18:15:50 localhost kernel: [ 608.443507] 'cfg bss -C 0' failed: -1

Dec 24 18:15:50 localhost kernel: [ 608.443509] CFGP2P-ERROR) wl_cfgp2p_bss_isup :

Dec 24 18:15:50 localhost kernel: [ 608.443510] NOTE: this ioctl error is normal when the BSS has not been created yet.

Dec 24 18:15:50 localhost kernel: [ 608.443514] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443518] wl_notifier_change_state :

Dec 24 18:15:50 localhost kernel: [ 608.443519] wlan0:error(-1)

Dec 24 18:15:50 localhost kernel: [ 608.443523] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443556] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443561] CFGP2P-ERROR) wl_cfgp2p_set_management_ie :

Dec 24 18:15:50 localhost kernel: [ 608.443562] vndr ie set error : -1

Dec 24 18:15:50 localhost kernel: [ 608.443574] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.443577] wl_dongle_down :

Dec 24 18:15:50 localhost kernel: [ 608.443579] WLC_DOWN error (-1)

Dec 24 18:15:50 localhost kernel: [ 608.467397] wl_android_wifi_off in

Dec 24 18:15:50 localhost kernel: [ 608.467410] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.467416] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.467423] dhd_prot_ioctl : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.468913] dhdsdio_isr : bus is down. we have nothing to do

Dec 24 18:15:50 localhost kernel: [ 608.468950] gpio tegra-gpio-aon wake69 for gpio=59(FF:3)

Dec 24 18:15:50 localhost kernel: [ 608.468952] Disabling wake69

Dec 24 18:15:50 localhost kernel: [ 608.469035] sdhci-tegra 3440000.sdhci: Tuning done, restoring the best tap value : 64

Dec 24 18:15:50 localhost kernel: [ 608.470077] wifi_platform_set_power = 0

Dec 24 18:15:50 localhost kernel: [ 608.675566] wl_cfg80211_hang :

Dec 24 18:15:50 localhost kernel: [ 608.675569] In : chip crash eventing

We are using Linux version 4.9.201.

Thanks ~

kayccc · January 12, 2022, 3:19am

Sorry for the late response, is this still an issue to support? Thanks

user111095 · January 13, 2022, 1:58am

Yes, we need help. Due to the terrible error, we CANNOT continue our development plan …
Newly informations:
[1]CANNOT reproduce in the lab with two TX2s
[2]This issue nearly happened per day in our factory (multiply TX2s using different wireless routers from different venders)

WayneWWW · January 13, 2022, 2:28am

Hi,

Please check if you can reproduce issue with jetpack4.6 + TX2 devkit.

user111095 · January 13, 2022, 7:21am

Thanks for your advice, but we CANNOT reproduce even using current package.

Our hundreds of devices with TX2 is running for real business, and it is impractical to update BSP. So if you
can offer one new wifi firmware, we can update part of devices and test.

Can you explain the kernel error, and possible causation ?

Thank you ~

WayneWWW · January 13, 2022, 7:23am

Hi,

Unfortunately this wifi firmware is not our product so we cannot explain or share a new firmware. If you need to check from firmware, please contact Broadcom for help.

user111095 · January 13, 2022, 9:14am

We are using original WPA_SUPPLIANT (v2.6) to connect to AP and periodically check signal rssi (SIGNAL_POLL). Common usage but the wifi firmware halted.

We guess the issue is a BUG of Broadcom and has nothing to do with NVIDIA, is it right?

WayneWWW · January 13, 2022, 9:16am

We cannot make any comment for now unless we can reproduce this issue locally and do the analysis.

Thus, if you want us to really check something, share us the steps to reproduce issue.

As for your question regarding “analyze the fw” or “provide the fw”, these are not what we can help.

system · February 2, 2022, 6:24am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.