Please create new topic with operation system and version. For me it looks like an error-pointer is used as memory address.
0xf…f98 should be -104 which is “connection reset”
Please create new topic with operation system and version. For me it looks like an error-pointer is used as memory address.
0xf…f98 should be -104 which is “connection reset”
thanks @frank-w . I will do, but first I need to collect some logs Just leave a msg for others, if someone have similar issue- my guess is related to mt7925e and recent update for mt76 in OpenWRT (probably it starts since this: mt76: update to Git HEAD (2024-08-16) · openwrt/openwrt@20bf5f3 · GitHub )
EDIT: Issue created: mt7925: Kernel panic after authentication · Issue #909 · openwrt/mt76 · GitHub
hope experts here can help me with this issue, currently using FM350GL / lastest snapshot , getting good speedtest around 600mbps but when upload starts , R4 will reboot due to kernel panic.
[ 22.894881] mtk_t7xx 0003:01:00.0: Packet drop on channel 0x100a, port not found
[ 27.698024] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 28.856590] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 28.894956] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 28.894962] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.267697] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.407202] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.407208] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.493214] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.603202] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 29.688209] NOHZ tick-stop error: local softirq work is pending, handler #08!!!
[ 88.920730] wwan wwan0 wwan0: TX queue 0 is full
[ 88.925360] wwan wwan0 wwan0: TX queue 0 is full
[ 88.929969] wwan wwan0 wwan0: TX queue 0 is full
[ 88.934591] wwan wwan0 wwan0: TX queue 0 is full
[ 88.939199] wwan wwan0 wwan0: TX queue 0 is full
[ 88.943824] wwan wwan0 wwan0: TX queue 0 is full
[ 88.948432] wwan wwan0 wwan0: TX queue 0 is full
[ 88.953046] wwan wwan0 wwan0: TX queue 0 is full
[ 88.957654] wwan wwan0 wwan0: TX queue 0 is full
[ 89.990457] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 1070 ms
[ 91.030488] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 2110 ms
[ 91.990518] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 3070 ms
[ 93.030549] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 4110 ms
[ 93.990577] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 5070 ms
[ 95.030610] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 6110 ms
[ 95.990636] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 7070 ms
[ 97.030666] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 8110 ms
[ 97.990694] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 9070 ms
[ 99.030721] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 10110 ms
[ 99.990750] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 11070 ms
[ 101.030779] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 12110 ms
[ 101.990807] wwan wwan0 wwan0: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 13070 ms
[ 102.303752] mtk_t7xx 0003:01:00.0: Could not unmask the UL interrupt. DPMAIF_AO_UL_AP_L2TIMR0 is 0xfffe1
[ 102.313258] wwan wwan0 wwan0: TX queue 0 is full
[ 102.492744] skbuff: skb_under_panic: text:ffffffc08077c45c len:-65269 put:149 head:ffffff80c805b000 data:ffffff7fc806afff tail:0xd3 end:0xec0 dev:wwan0
So, wifi be14 module arrived, mounted it , and after i’ve connected power board is not booting, nothing on serial, straight after power red pwr led and next g led green lights up and thats all… Someone have an idea how to diagnose this dead men?
Did you set SW4 to the “on” position? (to supply 12V to the BE14)
Yes, i did, but now without module board is also dead…
… you “may” have touched/changed the sdcard/emmc/nand boot selector switch while installing the wifi module (happened to me a couple of times).
Yes, but all combination don’t work, no boot blue led, also serial console is silent… Maybe later i’ll have some time to compare to my other one ( have three devices).
What power supply you have? AFAIK for BPI-R4 with BE 14 it is recommended 19V 3.2A:
# from conversation with Wendy
(...)
If you only use BPI-R4 mainboard, 12/2A power is OK. When you add wifi module or other more devices, we advice to use 19V/3.2A or choose power according to actual demand
Dell usb-c 45W brick or 12v 3Amps power supply from other working one. Tommorrow.i’ll take a look on this.
i have my BPI-R4-NIC-BE14 recive. The Modul is cooled with the metal case. is it normal that the Metalcase goes hot with this card?
Unfortunately, this is normal, my hand gets so hot that it can’t stand the heat
imo this is a failure from sinovoip. i replaced the top of the case with such one (Alu Lochblech 1 mm, Rundloch ø 3 mm, Rv 3-5), works like a charm and everything is cool. a closed case like sinovoip sells is… bad.
Oh that’s a good idea, didn’t think of that before may try that myself
if you need working dimensions, i have 154 mm x 101 mm (length x width)
@frank-w @dangowrt hey, is it possible somehow to upgrade u-boot to new release without UART? My friend got BPI-R4 and currently he don’t have UART and it is problematic for him to upgrade from stock to clean OpenWRT. Solution suggested by @kvic here does not work for him and as I see, OpenwRT wiki is poiting to BPI-R3, but is it same upgrade procedure to be done on BPI-R4 as it is done in BPI-R3 here ? In other words, he don’t want to brick the device, so if you can just ensure that BPI-R3 upgrade u-boot commands are same for BPI-R4 would be appreciated.
Thanks for advice.
This thread seems like a good place for a quick question. Is the temperature data for BE14 exposed in software? I found these sensors in /sys/class/thermal. Are any of them relevant to BE14?
mcusys_thermal_1
eth2p5g_thermal_0
eth2p5g_thermal_1
tops_thermal_0
tops_thermal_1
ethsys_thermal_0
ethsys_thermal_1
no, please create dedicated thread for software specific questions…and telling your OS
this thread has 379 posts and such questions are no more found in this thread and so asked again…
Hi experts I was wondering if MT7988a’s PCie lanes support endpoint mode?