Test new xradio firmware


Go to solution Solved by Werner,

Recommended Posts

If somebody has a chance to test new firmware blob for XR819 feedback would be appreciated :love:

Simply grab the fw_xr819.bin from the PR below, replace your current one and reboot. Check if Wi-Fi still works as expected or ideally even better.

The file is located here: /usr/lib/firmware/xr819/

 

https://github.com/armbian/firmware/commit/aff348fa9eef0fcc97d4f2bb7304f0862baffc20

 

If in doubt create a backup of your current firmware bin.

Link to post
Share on other sites
Donate and support the project!

As far as I can tell nothing much changed - nothing negative and nothing positive (still 200ms ping).

 

Did I actually install the new version or am I just an idiot?

 

[   10.021886] xradio: XR819 device discovered
[   10.181980] cfg80211: failed to load regulatory.db
[   10.257067] xradio: hardware vers. 7.9
[   10.257082] xradio: firmware vers. 8 (WSM), build 5258, api 1060, cap 0x0003
[   10.257086] xradio: Config USE_EXTENSIONS

Link to post
Share on other sites

The power management still acts up on my board.

Ping is arround 200ms even though Power Management:off

If I let the orange Pi ping the router or something else every 50ms ( ping -i 0,05 ) the orange pi responds < 5ms. I assume the ping command forces it out of the power safe mode.

Can you confirm this?

Link to post
Share on other sites

After 24h running the new firmware on Armbian 21.02.0-trunk Buster with Linux 5.9.11-sunxi I got the following:

 

[7789.126960] xradio WRN: BH: missed 9 consecutive interrupts!
[ 7798.343147] xradio WRN: BH: missed 10 consecutive interrupts!
[ 8168.424968] xradio WRN: BH: missed 11 consecutive interrupts!
[ 8317.727378] xradio WRN: BH: missed 12 consecutive interrupts!
[ 8458.633587] xradio WRN: BH: missed 13 consecutive interrupts!
[ 8875.000177] xradio WRN: BH: missed 14 consecutive interrupts!
[ 9703.025621] xradio WRN: BH: missed 15 consecutive interrupts!
[11029.338694] xradio WRN: BH: missed 16 consecutive interrupts!
[11698.845312] xradio WRN: BH: missed 17 consecutive interrupts!
[11830.943440] xradio WRN: BH: missed 18 consecutive interrupts!

[...]

 

and:

[14108.446345] wlan0: XXX tries to chanswitch to same channel, ignore
[14108.446708] wlan0: cannot understand ECSA IE operating class, 11, ignoring

 

Edit: and:

[ 5248.939102] xradio STA-WRN: [CQM] BSS lost, Beacon miss=20, event=24.
[ 5249.043167] xradio STA-WRN: [CQM] Beacon loss.
[ 5251.051198] xradio STA-ERR: [CQM] if0 Reporting connection loss.

 

Link to post
Share on other sites
2 minutes ago, Hammy said:

After 24h running the new firmware on Armbian 21.02.0-trunk Buster with Linux 5.9.11-sunxi I got the following:

 

[7789.126960] xradio WRN: BH: missed 9 consecutive interrupts!
[ 7798.343147] xradio WRN: BH: missed 10 consecutive interrupts!
[ 8168.424968] xradio WRN: BH: missed 11 consecutive interrupts!
[ 8317.727378] xradio WRN: BH: missed 12 consecutive interrupts!
[ 8458.633587] xradio WRN: BH: missed 13 consecutive interrupts!
[ 8875.000177] xradio WRN: BH: missed 14 consecutive interrupts!
[ 9703.025621] xradio WRN: BH: missed 15 consecutive interrupts!
[11029.338694] xradio WRN: BH: missed 16 consecutive interrupts!
[11698.845312] xradio WRN: BH: missed 17 consecutive interrupts!
[11830.943440] xradio WRN: BH: missed 18 consecutive interrupts!

[...]

 

and:

[14108.446345] wlan0: XXX tries to chanswitch to same channel, ignore
[14108.446708] wlan0: cannot understand ECSA IE operating class, 11, ignoring

 

This did not happen with the old version?

Link to post
Share on other sites
On 11/30/2020 at 10:36 AM, Werner said:

This did not happen with the old version?

I've checked on my second OPi0 where I didn't upgrade firmware, so still previous version, and the issue is also present :

[   14.824376] xradio: XR819 device discovered
[   15.056442] xradio: hardware vers. 7.9
[   15.056457] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003
[   15.056460] xradio: Config USE_EXTENSIONS
[   40.809788] xradio TXRX-WRN: received frame has no key status
[   40.809802] xradio TXRX-WRN: dropped received frame
[ 3653.654011] xradio WRN: BH: missed 4 consecutive interrupts!
[ 5423.670767] xradio WRN: BH: missed 5 consecutive interrupts!
[ 7584.760350] xradio WRN: BH: missed 6 consecutive interrupts!
[ 9724.478792] xradio WRN: BH: missed 7 consecutive interrupts!
[10080.291066] xradio WRN: BH: missed 8 consecutive interrupts!
[10777.751448] xradio WRN: BH: missed 9 consecutive interrupts!
[13480.647858] xradio WRN: BH: missed 10 consecutive interrupts!
[18367.827745] xradio WRN: BH: missed 11 consecutive interrupts!
[19237.530227] xradio WRN: BH: missed 12 consecutive interrupts!
[20461.024844] xradio WRN: BH: missed 13 consecutive interrupts!

 

Link to post
Share on other sites

I have observed kernel panics using xradio driver before. Check Opizero wifi kernel hang

I decided to test it with this driver.
Summary: No improvements

image.thumb.png.b9971ffd44a15520caae9cb8b2a2766b.png

 

Ap mode

No kernel panics were observed during 1 day when running only on AP mode.

 

However, when Orange Pi is rebooted in AP mode, kernel panic was observed.

After running 5 Orange Pi devices, after 60 average reboots, Kernel panic occurred for all devices.

[   25.238909] xradio WSM-ERR: CMD timeout!>>> 0x0006 (16), buf_use=1, bh_state=0
[   25.247990] xradio WSM-ERR: bh error!>>> 0x0006 (12)
[   25.254591] xradio WSM-ERR: bh error!>>> 0x0006 (12)
[   25.261367] xradio WSM-ERR: bh error!>>> 0x0012 (16)
[   25.266375] xradio STA-ERR: wsm_set_tx_queue_params failed!
[   25.271979] xradio WSM-ERR: bh error!>>> 0x0012 (16)
[   25.276963] xradio STA-ERR: wsm_set_tx_queue_params failed!
[   25.282555] xradio WSM-ERR: bh error!>>> 0x0012 (16)
[   25.287536] xradio STA-ERR: wsm_set_tx_queue_params failed!
[   25.293128] xradio WSM-ERR: bh error!>>> 0x0012 (16)
[   25.298109] xradio STA-ERR: wsm_set_tx_queue_params failed!
[   42.299138] rcu: INFO: rcu_sched self-detected stall on CPU
[   42.304730] rcu:     1-....: (1 GPs behind) idle=21e/1/0x40000002 softirq=3544/3545 fqs=2623
[   74.743671] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 1-... } 5569 jiffies s: 129 root: 0x2/.
[   74.754140] rcu: blocking rcu_node structures:

Same error was observed in old firmware.

 

Client mode

No kernel panics were observed during 1 day when connected to an AP with a non-changing channel.

 

Running in Client mode and changing AP’s channel result in similar kernel panic.

But this occurred rarely. Running 5 Orange pi zero devices and changing channel continuously 72 times, lead to a Kernel panic only on 1 device.

 

Running in Client mode, and rebooting also result in Kernel panic.

It took an average of 200 reboots for the Kernel panic for 5 Orange Pi Zero Devices.

Same error occurred on all situations.

 

Hope this helps.

This is how I tested.

image.thumb.png.f7c839258323262f225eb3fc5164fe54.png

Link to post
Share on other sites

Tested with the standard Armbian 20.11 Buster with Linux 5.8.16-sunxi

 

[7789.126960] xradio WRN: BH: missed 9 consecutive interrupts!
[ 7798.343147] xradio WRN: BH: missed 10 consecutive interrupts!
[ 8168.424968] xradio WRN: BH: missed 11 consecutive interrupts!

As already mentioned happens also on the old version

 

[14108.446345] wlan0: XXX tries to chanswitch to same channel, ignore
[14108.446708] wlan0: cannot understand ECSA IE operating class, 11, ignoring

Happened only once with the new version in 6 days, never with the old version. I have however something similar on the OPiZ+ with roughly the same time stamp and hence doubt that the firmware is to blame.

 

[ 5248.939102] xradio STA-WRN: [CQM] BSS lost, Beacon miss=20, event=24.
[ 5249.043167] xradio STA-WRN: [CQM] Beacon loss.
[ 5251.051198] xradio STA-ERR: [CQM] if0 Reporting connection loss.

Only happened once with the new firmware, never with the old. Don’t know what to think of it.

 

-> The firmware seems to be just as crappy as before. Is there a changelog available?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...