On 3/7/2024 7:53 AM, Hranislav Milenkovic wrote:
> Hi Arend, couple years later same question... can these crashes be
> fixed... who maintains chipset firmware for 43602... I get it for
> brcmfmac but who maintains firmwares from here
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/ <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/>
Hi Hranislav,
The firmware repo is maintained by kernel.org. Regarding the firmwares
for the brcm chips these have been submitted by Broadcom. The 43602 is
EOL so there will be no regular releases. Can you provide hardware
configuration details for your platform.
The firmware repo has two firmware files for 43602:
-rw-r--r-- brcmfmac43602-pcie.ap.bin 595472
-rw-r--r-- brcmfmac43602-pcie.bin 635449
Which one are you using?
> I have some crashes if you are interested (also have you seen this
> bugreport
> https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432
> <https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432>)
You made me look. So are you using OpenWrt? What release/branch are you
using?
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.722477] ieee80211 phy0:
> brcmf_fw_crashed: Firmware has halted or crashed
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.729587] 0001:01:00.0:
> CONSOLE: 005280.898
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.734051] 0001:01:00.0:
> CONSOLE: FWID 01-f458629d
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.739004] 0001:01:00.0:
> CONSOLE: flags 110005
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.743562] 0001:01:00.0:
> CONSOLE: 005280.898
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.748079] 0001:01:00.0:
> CONSOLE: TRAP 7(26fea8): pc 1871d6, lr 1867e9, sp 26ff00, cpsr 800001df,
> spsr 800001bf
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.758362] 0001:01:00.0:
> CONSOLE: 005280.898 r0 1000000, r1 40000000, r2 40, r3 1, r4 1fc8d8,
> r5 26af20, r6 25f2d4
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.769074] 0001:01:00.0:
> CONSOLE: 005280.898 r7 25eab4, r8 25f2dc, r9 0, r10 bf3c0282, r11
> db1d6d6c, r12 6038120
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.779551] 0001:01:00.0:
> CONSOLE: 005280.898
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.784043] 0001:01:00.0:
> CONSOLE: sp+0 00000000 0026af20 00000000 0018861d
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.791385] 0001:01:00.0:
> CONSOLE: 005280.898 sp+10 00000000 0025f3c0 00000000 0018078c
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.799596] 0001:01:00.0:
> CONSOLE:
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.803114] 0001:01:00.0:
> CONSOLE: 005280.898 sp+c 0018861d
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.808743] 0001:01:00.0:
> CONSOLE: 005280.898 sp+2c 00006fc7
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.814441] 0001:01:00.0:
> CONSOLE: 005280.898 sp+30 00006f9d
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.820146] 0001:01:00.0:
> CONSOLE: 005280.899 sp+3c 00007005
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.825842] 0001:01:00.0:
> CONSOLE: 005280.899 sp+4c 00007243
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.831544] 0001:01:00.0:
> CONSOLE: 005280.899 sp+5c 00183825
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.837236] 0001:01:00.0:
> CONSOLE: 005280.899 sp+70 001837f9
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.842937] 0001:01:00.0:
> CONSOLE: 005280.899 sp+8c 001823d7
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.848640] 0001:01:00.0:
> CONSOLE: 005280.899 sp+98 000001df
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.854329] 0001:01:00.0:
> CONSOLE: 005280.899 sp+d8 000071df
> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.860032] 0001:01:00.0:
> CONSOLE: 005280.899 sp+e8 00188e59
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.797981] ieee80211 phy0:
> brcmf_fil_cmd_data: bus is down. we have nothing to do.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.805670] brcmfmac:
> brcmf_cfg80211_stop_ap: bss_enable config failed -5
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.812497] ieee80211 phy0:
> brcmf_fil_cmd_data: bus is down. we have nothing to do.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.820190] ieee80211 phy0:
> brcmf_cfg80211_stop_ap: SET SSID error (-5)
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.826827] ieee80211 phy0:
> brcmf_fil_cmd_data: bus is down. we have nothing to do.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.834521] ieee80211 phy0:
> brcmf_fil_cmd_data: bus is down. we have nothing to do.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.842213] brcmfmac:
> brcmf_cfg80211_stop_ap: wl apsta failed (-5)
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.848420] ieee80211 phy0:
> brcmf_fil_cmd_data: bus is down. we have nothing to do.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.856098] ieee80211 phy0:
> brcmf_cfg80211_stop_ap: BRCMF_C_DOWN error -5
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.864446] br0: port
> 4(wlan0) entered disabled state
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.870425] device wlan0 left
> promiscuous mode
> Mar 05 19:13:22 178.220.177.32 kernel [ 5285.874923] br0: port
> 4(wlan0) entered disabled state
> Mar 05 19:13:22 178.220.177.32 kernel [ 5286.417713] brcmfmac:
> brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1
> Mar 05 19:13:22 178.220.177.32 kernel [ 5286.428364] brcmfmac
> 0001:01:00.0: Direct firmware load for �H0�
> �\` �`�dp�`0 �y��H0�\` �`�dp�`0 �r� failed with error -2
Not sure why this is all garbled. Can image there is not file with that
name though ;-) Above seems the driver attempts to recover from the
firmware crash. I can take a look at the firmware crash and the recovery
mechanism in the driver.
> Mar 05 19:13:22 178.220.177.32 kernel [ 5286.441255] brcmfmac
> 0001:01:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt
> failed with error -2
> Mar 05 19:13:25 178.220.177.32 kernel [ 5289.150530] BUG: Bad page
> state in process modprobe pfn:07150
> Mar 05 19:13:25 178.220.177.32 kernel [ 5289.156407] page:86cb6f40
> count:-1 mapcount:0 mapping: (null) index:0x0
> Mar 05 19:13:25 178.220.177.32 kernel [ 5289.163118] flags: 0x0()
> Mar 05 19:13:25 178.220.177.32 kernel [ 5289.165660] page dumped
> because: nonzero _count
> Mar 06 05:20:56 178.220.177.32 kernel [41739.171893] 0002:03:00.0:
> CONSOLE: 041746.172 ucode revision 986.128
> Mar 06 05:20:56 178.220.177.32 kernel [41739.178467] 0002:03:00.0:
> CONSOLE: 041746.172 wl0: PSM microcode watchdog fired at 41733 (seconds)
> Mar 06 05:20:56 178.220.177.32 kernel [41739.187768] 0002:03:00.0:
> CONSOLE: 041746.172 wl0: psmdebug 0x00ec8111, phydebug 0x00000048,
> psm_brc 0x0501 psm_brc_1 0x0000maccontrol 0x84160403 ifsstat 0x00af
> m_cts_duration 0x0000 m_ucode_dbgst 0x0002
> Mar 06 05:20:56 178.220.177.32 kernel [41739.206038] 0002:03:00.0:
> CONSOLE: 041746.172 wepctl 0x0050 wepstat 0x0000 wep_hdrloc 0x001e
> wep_psdulen 281
> Mar 06 05:20:56 178.220.177.32 kernel [41739.216025] 0002:03:00.0:
> CONSOLE: 041746.172 RXE_RXCNT: 0x011f DAGG: ctl: 0x0000, bleft:
> 0x0096
> Mar 06 05:20:56 178.220.177.32 kernel [41739.225523] 0002:03:00.0:
> CONSOLE: offs: 0x000c, stat: 0x1056, len: 0x0000
> Mar 06 05:20:56 178.220.177.32 kernel [41739.232995] 0002:03:00.0:
> CONSOLE: 041746.172 M_RXFRM_BLK scr(0:63) btc_params(0:63) phydebug PC
> ampdu clk off
> Mar 06 05:20:56 178.220.177.32 kernel [41739.243076] 0002:03:00.0:
> CONSOLE: 041746.172 wlc_dump_aggfifo:
> Mar 06 05:20:56 178.220.177.32 kernel [41739.249089] 0002:03:00.0:
> CONSOLE: 041746.172 framerdy 0x0 bmccmd 7 framecnt 1024
> Mar 06 05:20:56 178.220.177.32 kernel [41739.256822] 0002:03:00.0:
> CONSOLE: 041746.172 AQM agg params 0xfc0 maxlen hi/lo 0x0 0xffff minlen
> 0x0 adjlen 0x0
> Mar 06 05:20:56 178.220.177.32 kernel [41739.267153] 0002:03:00.0:
> CONSOLE: 041746.172 AQM agg results 0x8001 len hi/lo: 0x0 0x22
> BAbitmap(0-3) 0 0 0 0
> Mar 06 05:20:56 178.220.177.32 kernel [41739.277244] ieee80211 phy1:
> brcmf_psm_watchdog_notify: PSM's watchdog has fired!
The PSM watchdog means the microcode got stuck in a bad state. Getting
microcode development involved in fixing this will prove difficult.
Regards,
Arend
On 3/20/2024 11:41 AM, Arend van Spriel wrote:
> On 3/7/2024 7:53 AM, Hranislav Milenkovic wrote:
>> Hi Arend, couple years later same question... can these crashes be
>> fixed... who maintains chipset firmware for 43602... I get it for
>> brcmfmac but who maintains firmwares from here
>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/ <https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/>
>
> Hi Hranislav,
>
> The firmware repo is maintained by kernel.org. Regarding the firmwares
> for the brcm chips these have been submitted by Broadcom. The 43602 is
> EOL so there will be no regular releases. Can you provide hardware
> configuration details for your platform.
>
> The firmware repo has two firmware files for 43602:
>
> -rw-r--r-- brcmfmac43602-pcie.ap.bin 595472
> -rw-r--r-- brcmfmac43602-pcie.bin 635449
>
> Which one are you using?
>
>> I have some crashes if you are interested (also have you seen this
>> bugreport
>> https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432 <https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432>)
>
> You made me look. So are you using OpenWrt? What release/branch are you
> using?
>
>> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.722477] ieee80211 phy0:
>> brcmf_fw_crashed: Firmware has halted or crashed
>> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.729587] 0001:01:00.0:
>> CONSOLE: 005280.898
>> Mar 05 19:13:21 178.220.177.32 kernel [ 5284.734051] 0001:01:00.0:
>> CONSOLE: FWID 01-f458629d
This FWID is not matching the firmware files in linux-firmware repo:
$ for f in brcmfmac43602-pcie.*; do strings $f | tail -1; done
43602a1-roml/pcie-ag-splitrx-fdap-mbss-mfp-wl11k-wl11u-txbf-pktctx-amsdutx-ampduretry-chkd2hdma-proptxstatus-11nprop
Version: 7.35.177.56 CRC: 548eccd4 Date: Fri 2015-09-18 03:31:06 PDT
Ucode Ver: 986.122 FWID: 01-6cb8e269
43602a1-roml/pcie-ag-pktctx-splitrx-amsdutx-txbf-p2p-mchan-idauth-idsup-tdls-mfp-sr-proptxstatus-pktfilter-wowlpf-ampduhostreorder-keepalive-srom12-chkd2hdma
Version: 7.35.177.61 CRC: 55b10cfe Date: Tue 2015-11-10 06:39:55 PST
Ucode Ver: 986.122 FWID: 01-ea662a8c
Can you provide the above details for the firmware file you are using?
Regards,
Arend
Hi Arend, thank you for responding to my mail.
To answer you, I use both ddwrt and openwrt even. Both of them have problems with this chipset.
1) Openwrt stalls sometimes described here https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432 has problem with weak siignal on 5 ghz and doesn't show signal level because of BRCMF_FEAT_DUMP_OBSS is disabled described here https://github.com/openwrt/openwrt/issues/13903
2) ddwrt (brcmfamc version) has great signal strenght, shows signal levels but crashes all the time and basic functions like su-beamformee doesn't work with 43602
I attached as many info as I could get like hostapd.conf, dmesg, build versions/branch but commad you asked for f in brcmfmac43602-pcie.*; do strings $f | tail -1; output nothing both on openwrt and ddwrt...
Hranislav Milenkovic
+381 (0)65 2026199
Sent with Proton Mail secure email.
On Wednesday, March 20th, 2024 at 11:41 AM, Arend van Spriel <[email protected]> wrote:
> On 3/7/2024 7:53 AM, Hranislav Milenkovic wrote:
>
> > Hi Arend, couple years later same question... can these crashes be
> > fixed... who maintains chipset firmware for 43602... I get it for
> > brcmfmac but who maintains firmwares from here
> > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/ https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/brcm/
>
>
> Hi Hranislav,
>
> The firmware repo is maintained by kernel.org. Regarding the firmwares
> for the brcm chips these have been submitted by Broadcom. The 43602 is
> EOL so there will be no regular releases. Can you provide hardware
> configuration details for your platform.
>
> The firmware repo has two firmware files for 43602:
>
> -rw-r--r-- brcmfmac43602-pcie.ap.bin 595472
> -rw-r--r-- brcmfmac43602-pcie.bin 635449
>
> Which one are you using?
>
> > I have some crashes if you are interested (also have you seen this
> > bugreport
> > https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432
> > https://github.com/openwrt/openwrt/issues/14685#issuecomment-1980108432)
>
>
> You made me look. So are you using OpenWrt? What release/branch are you
> using?
>
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.722477] ieee80211 phy0:
> > brcmf_fw_crashed: Firmware has halted or crashed
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.729587] 0001:01:00.0:
> > CONSOLE: 005280.898
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.734051] 0001:01:00.0:
> > CONSOLE: FWID 01-f458629d
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.739004] 0001:01:00.0:
> > CONSOLE: flags 110005
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.743562] 0001:01:00.0:
> > CONSOLE: 005280.898
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.748079] 0001:01:00.0:
> > CONSOLE: TRAP 7(26fea8): pc 1871d6, lr 1867e9, sp 26ff00, cpsr 800001df,
> > spsr 800001bf
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.758362] 0001:01:00.0:
> > CONSOLE: 005280.898 r0 1000000, r1 40000000, r2 40, r3 1, r4 1fc8d8,
> > r5 26af20, r6 25f2d4
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.769074] 0001:01:00.0:
> > CONSOLE: 005280.898 r7 25eab4, r8 25f2dc, r9 0, r10 bf3c0282, r11
> > db1d6d6c, r12 6038120
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.779551] 0001:01:00.0:
> > CONSOLE: 005280.898
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.784043] 0001:01:00.0:
> > CONSOLE: sp+0 00000000 0026af20 00000000 0018861d
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.791385] 0001:01:00.0:
> > CONSOLE: 005280.898 sp+10 00000000 0025f3c0 00000000 0018078c
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.799596] 0001:01:00.0:
> > CONSOLE:
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.803114] 0001:01:00.0:
> > CONSOLE: 005280.898 sp+c 0018861d
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.808743] 0001:01:00.0:
> > CONSOLE: 005280.898 sp+2c 00006fc7
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.814441] 0001:01:00.0:
> > CONSOLE: 005280.898 sp+30 00006f9d
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.820146] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+3c 00007005
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.825842] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+4c 00007243
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.831544] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+5c 00183825
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.837236] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+70 001837f9
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.842937] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+8c 001823d7
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.848640] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+98 000001df
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.854329] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+d8 000071df
> > Mar 05 19:13:21 178.220.177.32 kernel [ 5284.860032] 0001:01:00.0:
> > CONSOLE: 005280.899 sp+e8 00188e59
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.797981] ieee80211 phy0:
> > brcmf_fil_cmd_data: bus is down. we have nothing to do.
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.805670] brcmfmac:
> > brcmf_cfg80211_stop_ap: bss_enable config failed -5
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.812497] ieee80211 phy0:
> > brcmf_fil_cmd_data: bus is down. we have nothing to do.
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.820190] ieee80211 phy0:
> > brcmf_cfg80211_stop_ap: SET SSID error (-5)
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.826827] ieee80211 phy0:
> > brcmf_fil_cmd_data: bus is down. we have nothing to do.
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.834521] ieee80211 phy0:
> > brcmf_fil_cmd_data: bus is down. we have nothing to do.
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.842213] brcmfmac:
> > brcmf_cfg80211_stop_ap: wl apsta failed (-5)
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.848420] ieee80211 phy0:
> > brcmf_fil_cmd_data: bus is down. we have nothing to do.
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.856098] ieee80211 phy0:
> > brcmf_cfg80211_stop_ap: BRCMF_C_DOWN error -5
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.864446] br0: port
> > 4(wlan0) entered disabled state
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.870425] device wlan0 left
> > promiscuous mode
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5285.874923] br0: port
> > 4(wlan0) entered disabled state
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5286.417713] brcmfmac:
> > brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5286.428364] brcmfmac
> > 0001:01:00.0: Direct firmware load for �H0�
> > �\ `�`�dp�`0 �y��H0�\\` �`�dp�`0 �r� failed with error -2
>
>
> Not sure why this is all garbled. Can image there is not file with that
> name though ;-) Above seems the driver attempts to recover from the
> firmware crash. I can take a look at the firmware crash and the recovery
> mechanism in the driver.
>
> > Mar 05 19:13:22 178.220.177.32 kernel [ 5286.441255] brcmfmac
> > 0001:01:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt
> > failed with error -2
> > Mar 05 19:13:25 178.220.177.32 kernel [ 5289.150530] BUG: Bad page
> > state in process modprobe pfn:07150
> > Mar 05 19:13:25 178.220.177.32 kernel [ 5289.156407] page:86cb6f40
> > count:-1 mapcount:0 mapping: (null) index:0x0
> > Mar 05 19:13:25 178.220.177.32 kernel [ 5289.163118] flags: 0x0()
> > Mar 05 19:13:25 178.220.177.32 kernel [ 5289.165660] page dumped
> > because: nonzero _count
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.171893] 0002:03:00.0:
> > CONSOLE: 041746.172 ucode revision 986.128
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.178467] 0002:03:00.0:
> > CONSOLE: 041746.172 wl0: PSM microcode watchdog fired at 41733 (seconds)
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.187768] 0002:03:00.0:
> > CONSOLE: 041746.172 wl0: psmdebug 0x00ec8111, phydebug 0x00000048,
> > psm_brc 0x0501 psm_brc_1 0x0000maccontrol 0x84160403 ifsstat 0x00af
> > m_cts_duration 0x0000 m_ucode_dbgst 0x0002
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.206038] 0002:03:00.0:
> > CONSOLE: 041746.172 wepctl 0x0050 wepstat 0x0000 wep_hdrloc 0x001e
> > wep_psdulen 281
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.216025] 0002:03:00.0:
> > CONSOLE: 041746.172 RXE_RXCNT: 0x011f DAGG: ctl: 0x0000, bleft:
> > 0x0096
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.225523] 0002:03:00.0:
> > CONSOLE: offs: 0x000c, stat: 0x1056, len: 0x0000
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.232995] 0002:03:00.0:
> > CONSOLE: 041746.172 M_RXFRM_BLK scr(0:63) btc_params(0:63) phydebug PC
> > ampdu clk off
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.243076] 0002:03:00.0:
> > CONSOLE: 041746.172 wlc_dump_aggfifo:
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.249089] 0002:03:00.0:
> > CONSOLE: 041746.172 framerdy 0x0 bmccmd 7 framecnt 1024
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.256822] 0002:03:00.0:
> > CONSOLE: 041746.172 AQM agg params 0xfc0 maxlen hi/lo 0x0 0xffff minlen
> > 0x0 adjlen 0x0
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.267153] 0002:03:00.0:
> > CONSOLE: 041746.172 AQM agg results 0x8001 len hi/lo: 0x0 0x22
> > BAbitmap(0-3) 0 0 0 0
> > Mar 06 05:20:56 178.220.177.32 kernel [41739.277244] ieee80211 phy1:
> > brcmf_psm_watchdog_notify: PSM's watchdog has fired!
>
>
> The PSM watchdog means the microcode got stuck in a bad state. Getting
> microcode development involved in fixing this will prove difficult.
>
> Regards,
> Arend
On 3/20/2024 10:20 PM, Hranislav Milenkovic wrote:
> I attached as many info as I could get like hostapd.conf, dmesg, build
> versions/branch but commad you asked for f in brcmfmac43602-pcie.*; do
> strings $f | tail -1; output nothing both on openwrt and ddwrt...
The command should be executed in the directory where the firmware file
reside, eg. /lib/firmware/brcm. Might be they are in a different
location though.
Regards,
Arend
Ah, ok... here is the output:
OPENWRT:
[hranislav@toshiba-laptop ~]$ sudo ssh 192.168.1.1
[sudo] password for hranislav:
[email protected]'s password:
BusyBox v1.36.1 (2024-03-22 10:37:01 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt SNAPSHOT, r25604-494c5691c6
-----------------------------------------------------
root@R8000:~# cd /lib/firmware/brcm
root@R8000:/lib/firmware/brcm# for f in brcmfmac43602-pcie.*; do strings $f | tail -1; done
43602a1-roml/pcie-ag-splitrx-fdap-mbss-mfp-wl11k-wl11u-txbf-pktctx-amsdutx-ampduretry-chkd2hdma-proptxstatus-11nprop Version: 7.35.177.56 CRC: 548eccd4 Date: Fri 2015-09-18 03:31:06 PDT Ucode Ver: 986.122 FWID: 01-6cb8e269
root@R8000:/lib/firmware/brcm#
DDWRT:
[hranislav@toshiba-laptop ~]$ mactelnet r8000
Searching for 'r8000'...found
Login: root
Password:
Connecting to 2c:30:33:59:aa:79...done
==========================================================
___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/
DD-WRT v3.0
https://www.dd-wrt.com
==========================================================
BusyBox v1.36.1 (2024-03-21 07:18:48 +06) built-in shell (ash)
~ # cd /lib/firmware/brcm
/lib/firmware/brcm # for f in brcmfmac43602-pcie.*; do strings $f | tail -1; done
43602a1-roml/pcie-ag-splitrx-fdap-mbss-mfp-wnm-osen-wl11k-wl11u-txbf-pktctx-amsdutx-ampduretry-chkd2hdma-proptxstatus-txpwr-authrmf-11nprop-obss-dbwsw-ringer-dmaindex16-bgdfs-stamon-hostpmac-hostmemucode-splitassoc-cca Version: 7.49.6.0 CRC: 17a26fb1 Date: Sun 2022-06-12 22:22:41 +07 FWID 01-f458629d
/lib/firmware/brcm #
Hranislav Milenkovic
+381 (0)65 2026199
Sent with Proton Mail secure email.
On Saturday, March 23rd, 2024 at 8:40 PM, Arend van Spriel <[email protected]> wrote:
> On 3/20/2024 10:20 PM, Hranislav Milenkovic wrote:
>
> > I attached as many info as I could get like hostapd.conf, dmesg, build
> > versions/branch but commad you asked for f in brcmfmac43602-pcie.*; do
> > strings $f | tail -1; output nothing both on openwrt and ddwrt...
>
>
> The command should be executed in the directory where the firmware file
> reside, eg. /lib/firmware/brcm. Might be they are in a different
> location though.
>
> Regards,
> Arend