Hammy
-
Posts
13 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Hammy
-
-
I guess this is related to:
-
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, ignoringHappened 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?
-
vor 19 Minuten schrieb Werner:
This did not happen with the old version?
Thats my problem, I never checked on the old one, just wrote it off as buggy.
I’ll monitor a few more days, roll back to standard Armbian on Friday and report back the differences
-
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, ignoringEdit: 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. -
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?
-
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 -
Awesome guys, when will the change be in the current build?
Out of curiosity: What is “ZSMALLOC_PGTABLE_MAPPING“ actually doing?
-
I’d like the red led to indicate wifi activity. The led triggers phy0rx and phy0tz are missing on OPiZ+ (H5) however.
On OPiZ (H2) this worked fine – any ideas?
Hammy
-
Thanks for the info, is there any work around?
Switching to zstd caused the same error and crashed the board while benchmarking. After a reboot: http://ix.io/2F3t - Interestingly it says:
### Activated 1 lzo-rle zram swap devices with 491 MB each
While
root@orangepizero:~# zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram1 zstd 491,6M 4K 58B 4K 4 [SWAP]
/dev/zram0 zstd 50M 1,4M 184,1K 572K 4 /var/log
Daniel
-
Small update:
going back to Armbian 20.08.17 Buster with Linux 5.4.62-sunxi64 "solves" the problem.
Can anyone confirm this behavior?
Daniel
-
Armbianmonitor:
Good evening,
I ran into some problems with sbc-bench on a couple of Allwinner boards Orange Pi Zero, Orange Pi Zero+, Orange Pi One and Nanopi Neo 2 spcifically. The 7 Zip benchmark causes the following error:
./sbc-bench.sh: Zeile 611: 4206 Bus-Zugriffsfehler "${SevenZip}" b >> ${TempLog}
Most likely due to a problem with the ZRam:
zram: Decompression failed! err=-22
This happens on all boards under Debian and focal with different SD cards and power supplies. The benchmark ran previously on this setups without any issues – unfortunately I don’t know when it stopped working and hence cannot narrow down the change that caused the problem.
The benchmark results and armbianmonitor output from the Orange Pi one as an example:
Is this a known issue? Is there a solution?
Daniel
-
I'm seeing the exact same behavior on a Nanopi Neo 2. It won’t throttle below 1.1 Ghz on the 5.4 and 5.6 Kernels.
Orange pi zero kernel oops with zram enabled
in Beginners
Posted
Zram works for me with 5.9 build from trunk. I'm not sure though if building from trunk is a good idea when stability is a concern.