mt76 MT7612EN Constant hardware restart requested on b22977c

MT7612EN Constant hardware restart requested on b22977c

Open JosiahWhite opened this issue 3 years ago • 103 comments

When this happens, all wifi traffic stops for multiple seconds while the hardware restarts Chip: MT7612EN Device: Xiaomi MiWiFi 4A gigabit edition

Using three of these devices as AP-repeaters with the backhaul on the same radio in WDS mode. All three are experiencing the same issue to differing degrees, some only have the message printed once per hour, others multiple times per minute. Frequency seems to depend on how many clients are connected and active. The device the log below was from a quiet AP with only 2 clients connected. If it matters, the other side of the backhaul is an Archer C7 v2 with a QCA9880-BR4A radio.

All of the devices are running the latest OpenWrt snapshot which is using this master branch at commit ID b22977c

Dmesg output follows:

[ 1105.247542] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 1105.253078] mt76x2e 0000:01:00.0: Build: 1
[ 1105.257250] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[ 1105.278354] mt76x2e 0000:01:00.0: Firmware running!
[ 1105.286566] ieee80211 phy1: Hardware restart was requested
[ 2382.541609] mt76x2e 0000:01:00.0: MCU message 31 (seq 6) timed out
[ 2382.586767] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 2382.592296] mt76x2e 0000:01:00.0: Build: 1
[ 2382.596478] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[ 2382.617593] mt76x2e 0000:01:00.0: Firmware running!
[ 2382.625861] ieee80211 phy1: Hardware restart was requested
[ 2570.690347] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 2570.695877] mt76x2e 0000:01:00.0: Build: 1
[ 2570.700035] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[ 2570.721149] mt76x2e 0000:01:00.0: Firmware running!
[ 2570.729397] ieee80211 phy1: Hardware restart was requested
[ 3302.287051] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 3302.292558] mt76x2e 0000:01:00.0: Build: 1
[ 3302.296706] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[ 3302.317843] mt76x2e 0000:01:00.0: Firmware running!
[ 3302.330030] ieee80211 phy1: Hardware restart was requested
[ 3326.257359] mt76x2e 0000:01:00.0: MCU message 31 (seq 3) timed out
[ 3326.302482] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
[ 3326.307988] mt76x2e 0000:01:00.0: Build: 1
[ 3326.312155] mt76x2e 0000:01:00.0: Build Time: 201507311614____
[ 3326.333352] mt76x2e 0000:01:00.0: Firmware running!
[ 3326.341610] ieee80211 phy1: Hardware restart was requested

Sep 29 '20 22:09 JosiahWhite

Similar behaviour with a MT7621AT based Newifi-D2 running OpenWrt 19.07.4.

Mon Oct  5 17:35:57 2020 kern.info kernel: [489806.464298] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Oct  5 17:35:57 2020 kern.info kernel: [489806.469869] mt76x2e 0000:01:00.0: Build: 1
Mon Oct  5 17:35:57 2020 kern.info kernel: [489806.474137] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Oct  5 17:35:57 2020 kern.info kernel: [489806.502477] mt76x2e 0000:01:00.0: Firmware running!
Mon Oct  5 17:35:57 2020 kern.info kernel: [489806.512600] ieee80211 phy1: Hardware restart was requested
Mon Oct  5 17:36:06 2020 kern.info kernel: [489815.924024] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Oct  5 17:36:06 2020 kern.info kernel: [489815.929595] mt76x2e 0000:01:00.0: Build: 1
Mon Oct  5 17:36:06 2020 kern.info kernel: [489815.933833] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Oct  5 17:36:06 2020 kern.info kernel: [489815.962189] mt76x2e 0000:01:00.0: Firmware running!
Mon Oct  5 17:36:06 2020 kern.info kernel: [489815.972375] ieee80211 phy1: Hardware restart was requested
Mon Oct  5 17:37:18 2020 kern.info kernel: [489887.941970] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Oct  5 17:37:18 2020 kern.info kernel: [489887.947540] mt76x2e 0000:01:00.0: Build: 1
Mon Oct  5 17:37:18 2020 kern.info kernel: [489887.951821] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Oct  5 17:37:18 2020 kern.info kernel: [489887.980063] mt76x2e 0000:01:00.0: Firmware running!
Mon Oct  5 17:37:18 2020 kern.info kernel: [489887.990240] ieee80211 phy1: Hardware restart was requested
Mon Oct  5 17:37:21 2020 kern.info kernel: [489890.711825] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Oct  5 17:37:21 2020 kern.info kernel: [489890.717395] mt76x2e 0000:01:00.0: Build: 1
Mon Oct  5 17:37:21 2020 kern.info kernel: [489890.721669] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Oct  5 17:37:21 2020 kern.info kernel: [489890.750033] mt76x2e 0000:01:00.0: Firmware running!
Mon Oct  5 17:37:21 2020 kern.info kernel: [489890.760117] ieee80211 phy1: Hardware restart was requested
Mon Oct  5 17:37:25 2020 kern.info kernel: [489894.391767] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Oct  5 17:37:25 2020 kern.info kernel: [489894.397338] mt76x2e 0000:01:00.0: Build: 1
Mon Oct  5 17:37:25 2020 kern.info kernel: [489894.401657] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Oct  5 17:37:25 2020 kern.info kernel: [489894.429880] mt76x2e 0000:01:00.0: Firmware running!
Mon Oct  5 17:37:25 2020 kern.info kernel: [489894.440081] ieee80211 phy1: Hardware restart was requested

Oct 05 '20 22:10 Kevinjil

Its worth reducing the transmit power setting to 20 dBm - depending on country limits etc. I've noticed setting above that level, this issue occurs. Possible that gpio pins need to be set high to work at high levels?

Dec 22 '20 16:12 db260179

For what it's worth, I've seen a similar issue on my DIR-860L B1 (PHY1 is the N radio here though). With kernel 5.4, the radio then often completely disappeared. I brought this up in the pending 5.10 PR for ramips and one of the people who worked on the mt7621-pcie suggested the GPIO pins related to the PCI-E ports needed to be reset explicitly. This needs to be done through the DTS. These pins are board specific, so you need to find those out first, but it might be worth a try.

Dec 27 '20 15:12 Borromini

I notice this issue in many devices of mt7621

Dec 31 '20 14:12 ptpt52

@Borromini How to find the needed GPIO pin? I have the same problem on mir3g.

Jan 02 '21 10:01 Vladdrako

@Vladdrako See https://github.com/openwrt/openwrt/pull/3693#issuecomment-750782970 seems it could be 19, 8 and 7. Try modifying the PCI-E section in your DTS and recompile:

 &pcie {
        pinctrl-names = "default";
        pinctrl-0 = <&pcie_pins>;

       reset-gpios = <&gpio 19 GPIO_ACTIVE_LOW>,
                       <&gpio 8 GPIO_ACTIVE_LOW>,
                       <&gpio 7 GPIO_ACTIVE_LOW>;

        status = "okay";
 };

I checked the Mi Router 3G DTS, it just says status = "okay" like mine (DIR-860L rev B1) did. You might see some extra errors in dmesg, check the comment section of the PR for more insights on it.

Jan 02 '21 14:01 Borromini

@Borromini gpio8 used for Front LED on my board. Sadly, resetting gpio 19 and 7 didn't fix MCU error. Anyway, thanks for the help.

Jan 06 '21 14:01 Vladdrako

Is there anything that we can do to help debug this issue further? Also, what versions are affected by this bug? I've had this issue for a while on the 19.07 branch, including the latest 19.07.5. It didn't happen on the earlier versions of 19.07 if I remember correctly. And from what I am reading, it's also happening on devices on recent master branch images?

Jan 06 '21 22:01 Mushoz

@Mushoz Don't you have a DIR-860L B1 as well? (You can PM me on the OpenWrt forum if you'd like).

Jan 06 '21 23:01 Borromini

Hi. Just want you to know and try it. I had the same problem with Newifi 3 D2. And I fixed it :) The reason was the HDD connected to my router and lying next to my router. I have used a longer cable and moved HDD 0.5m+ (about 70cm, ok) far from the router and everything is ok now. Dmesg is clean now :) Try it. Or you can try to turn off HDD, if you do not have long cable. If you do not have HDD near your router then look for other electromagnetic sources.

Btw, when I put my HDD near router again - errors come back. So, I think it is a hardware problem.

Hope it will help. OpenWrt 19.07.6 r11278-8055e38794 / Newifi-D2 / MediaTek MT7621 ver:1 eco:3 / MT7662E

Jan 28 '21 21:01 infunx

See https://bugs.openwrt.org/index.php?do=details&task_id=3989. But still exists in OpenWrt 21.02.0 FINAL on the Xiaomi Mi Router 4A Gigabit Edition.

Sep 08 '21 09:09 gstammw

@gstammw Did you try fiddling with the GPIO resets in the DTS to see if that fixes it for you?

Sep 08 '21 17:09 Borromini

I'm experiencing the same issue on:

Xiaomi Mi Router 3G MediaTek MT7621 ver:1 eco:3 OpenWrt 21.02.0 r16279-5cc0535800 / LuCI openwrt-21.02 branch git-21.231.26241-422c175

Same on and on in the Kernel log:

[1213184.312296] ieee80211 phy1: Hardware restart was requested
[1213221.697213] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
[1213221.702897] mt76x2e 0000:02:00.0: Build: 1
[1213221.707216] mt76x2e 0000:02:00.0: Build Time: 201507311614____
[1213221.728069] mt76x2e 0000:02:00.0: Firmware running!
[1213221.736223] ieee80211 phy1: Hardware restart was requested

Oct 05 '21 21:10 iAbadia

My xiaomi miwifi mini also reboots automatically often on openwrt 21.02.0 I rollbacked the firmware to openwrt 19.07.7.

Oct 09 '21 15:10 aero

Same issue on Newifi-D2. Firmware restarts frequently, especially on heavy load with more than 10 clients connected to 5GHz.

[19561.719469] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [19561.724954] mt76x2e 0000:01:00.0: Build: 1 [19561.729168] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [19561.758190] mt76x2e 0000:01:00.0: Firmware running! [19561.768250] ieee80211 phy1: Hardware restart was requested [19606.318380] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [19606.323864] mt76x2e 0000:01:00.0: Build: 1 [19606.328067] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [19606.357122] mt76x2e 0000:01:00.0: Firmware running! [19606.367217] ieee80211 phy1: Hardware restart was requested [19643.547575] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [19643.553061] mt76x2e 0000:01:00.0: Build: 1 [19643.557242] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [19643.586232] mt76x2e 0000:01:00.0: Firmware running! [19643.596304] ieee80211 phy1: Hardware restart was requested [19675.826701] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [19675.832380] mt76x2e 0000:01:00.0: Build: 1 [19675.836595] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [19675.865448] mt76x2e 0000:01:00.0: Firmware running! [19675.875483] ieee80211 phy1: Hardware restart was requested [20040.597919] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [20040.603407] mt76x2e 0000:01:00.0: Build: 1 [20040.607659] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [20040.636281] mt76x2e 0000:01:00.0: Firmware running! [20040.646353] ieee80211 phy1: Hardware restart was requested [20050.877247] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [20050.882732] mt76x2e 0000:01:00.0: Build: 1 [20050.886947] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [20050.916022] mt76x2e 0000:01:00.0: Firmware running! [20050.926077] ieee80211 phy1: Hardware restart was requested [22142.691835] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 [22142.697329] mt76x2e 0000:01:00.0: Build: 1 [22142.701517] mt76x2e 0000:01:00.0: Build Time: 201507311614____ [22142.730636] mt76x2e 0000:01:00.0: Firmware running! [22142.740691] ieee80211 phy1: Hardware restart was requested

Nov 04 '21 12:11 HiGarfield

@Borromini Do you still run the patched DTS on a DIR 860L B1? If so, do you experience the issue with the released 21.01 version? With the unpatched release builds, I do still experience this issue, so I was wondering if it is worth it to give it a shot.

Nov 07 '21 22:11 noctux

@noctux It should be part of 21.02 since it was merged well before. I just set up my DIR-860L B1 somewhere else recently after it being unused for a long time and it seems to work fine.

Nov 08 '21 06:11 Borromini

@Borromini Thank you for your answer! Interesting. I assume that you are correct: https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ramips/dts/mt7621_dlink_dir-860l-b1.dts;hb=HEAD indicates that 19 and 8 are reset on current 860l builds (probably the two pins out of the 3 options that might be in use on the DIR 860L B1). However, I still see firmware reset-warnings and experience instable wifi (even though 21.01.1 has improved the situation slightly, but not definitely):

Mon Nov  8 11:58:38 2021 kern.info kernel: [575851.537080] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Mon Nov  8 11:58:38 2021 kern.info kernel: [575851.548446] mt76x2e 0000:01:00.0: Build: 1
Mon Nov  8 11:58:38 2021 kern.info kernel: [575851.556984] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Mon Nov  8 11:58:38 2021 kern.info kernel: [575851.583791] mt76x2e 0000:01:00.0: Firmware running!
Mon Nov  8 11:58:38 2021 kern.info kernel: [575851.595971] ieee80211 phy0: Hardware restart was requested

So unfortunately, it might not be the missing DTS-pins alone :/ But I'm glad (and a bit surpised) that your B1 works alight :D Maybe I have strange clients on my network...

Nov 08 '21 20:11 noctux

@noctux You might want to try pin 7, it seems 19, 8 and 7 are the common ones used on MT7621. But I lack the technical background, so I'm going out on a limb.

Nov 09 '21 10:11 Borromini

The mt76 uses the version below and no more firmware reset issues. PKG_SOURCE_DATE:=2018-11-09 PKG_SOURCE_VERSION:=ffccb48c5082b2c6f43a0235b77b62ca388810f0 PKG_MIRROR_HASH:=bff0063db1a1b1353f59aad16abad4dd93ceeb4c672811ad864cebe0e39c7d8d

Jan 10 '22 04:01 jxph1123

Please try the latest mt76 master version included in my staging tree at https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=summary

Jan 31 '22 14:01 nbd168

Cross-posted a link to your message in the following issue: https://github.com/openwrt/mt76/issues/444

This ticket seems to have been opened ~16 days after the other one, so this one is a duplicate. We might want to keep the conversation in one ticket to keep things clear :)

Jan 31 '22 14:01 Mushoz

Please try the latest mt76 master version included in my staging tree at https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=summary Thu Feb 3 06:38:21 2022 kern.info kernel: [ 0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3

15.213230] mt7621-pci 1e140000.pcie: bus=1 slot=0 irq=23 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.224075] pci 0000:00:00.0: enabling device (0004 -> 0007) Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.235373] mt76x2e 0000:01:00.0: enabling device (0000 -> 0002) Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.247575] mt76x2e 0000:01:00.0: ASIC revision: 76120044 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.912934] mt76x2e 0000:01:00.0: ROM patch build: 20141115060606a Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.965907] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.976891] mt76x2e 0000:01:00.0: Build: 1 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 15.985085] mt76x2e 0000:01:00.0: Build Time: 201706151016____ Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.011057] mt76x2e 0000:01:00.0: Firmware running! Thu Feb 3 06:38:21 2022 kern.debug kernel: [ 16.022621] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.028208] mt7621-pci 1e140000.pcie: bus=2 slot=1 irq=24 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.039129] pci 0000:00:01.0: enabling device (0004 -> 0007) Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.050455] mt76x2e 0000:02:00.0: enabling device (0000 -> 0002) Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.062696] mt76x2e 0000:02:00.0: ASIC revision: 76020044 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.731178] mt76x2e 0000:02:00.0: ROM patch already applied Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.743415] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.754400] mt76x2e 0000:02:00.0: Build: 1 Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.762598] mt76x2e 0000:02:00.0: Build Time: 201706151016____ Thu Feb 3 06:38:21 2022 kern.info kernel: [ 16.791235] mt76x2e 0000:02:00.0: Firmware running! Thu Feb 3 06:38:21 2022 kern.debug kernel: [ 16.803169] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' firmware version

Thu Feb 3 07:25:38 2022 kern.err kernel: [ 749.178989] mt76x2e 0000:01:00.0: MAC error detected at a distance errors are not often, Under load

Thu Feb 3 15:31:23 2022 kern.err kernel: [29893.867412] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:31:26 2022 kern.err kernel: [29896.977375] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:32:15 2022 kern.err kernel: [29945.856770] mt76x2e 0000:01:00.0: MAC error detected at a distance errors are not often,Under load

Thu Feb 3 15:46:59 2022 kern.err kernel: [30829.764956] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:00 2022 kern.err kernel: [30831.005029] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:14 2022 kern.err kernel: [30845.555142] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:16 2022 kern.err kernel: [30846.795164] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:18 2022 kern.err kernel: [30848.695189] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:31 2022 kern.err kernel: [30862.135387] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:46 2022 kern.err kernel: [30877.145494] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:47 2022 kern.err kernel: [30878.385533] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:47:49 2022 kern.err kernel: [30880.285532] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:48:07 2022 kern.err kernel: [30898.135841] mt76x2e 0000:01:00.0: MAC error detected

Very small distance to hdd, many errors, Under load Thu Feb 3 15:49:27 2022 kern.info kernel: [30978.376070] mt7530 mdio-bus:1f lan1: Link is Up - 100Mbps/Full - flow control off PC from wifi to ethernet

Thu Feb 3 15:50:48 2022 kern.err kernel: [31059.063773] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:03 2022 kern.err kernel: [31074.383483] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:04 2022 kern.err kernel: [31075.623469] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:07 2022 kern.err kernel: [31077.743439] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:31 2022 kern.err kernel: [31102.522946] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:33 2022 kern.err kernel: [31103.762937] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:34 2022 kern.err kernel: [31104.892900] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:35 2022 kern.err kernel: [31106.132899] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:48 2022 kern.err kernel: [31119.082633] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:52 2022 kern.err kernel: [31122.962557] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:53 2022 kern.err kernel: [31124.092541] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:51:55 2022 kern.err kernel: [31126.322511] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 15:52:08 2022 kern.err kernel: [31138.892264] mt76x2e 0000:01:00.0: MAC error detected Very small distance to hdd, many errors

daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 84:xx:xx:xx:xx:bc Thu Feb 3 16:12:22 2022 daemon.info hostapd: wlan0: STA 84:xx:xx:xx:xx:bc IEEE 802.11: disassociated Thu Feb 3 16:12:24 2022 daemon.info hostapd: wlan0: STA 84:xx:xx:xx:xx:bc IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE) Thu Feb 3 16:12:27 2022 daemon.info hostapd: wlan0: STA 84:xx:xx:xx:xx:bc IEEE 802.11: authenticated Thu Feb 3 16:12:27 2022 daemon.notice hostapd: wlan0: STA-OPMODE-N_SS-CHANGED 84:xx:xx:xx:xx:bc 2 Thu Feb 3 16:12:27 2022 daemon.info hostapd: wlan0: STA 84:c7:xx:xx:xx:bc IEEE 802.11: associated (aid 1) Thu Feb 3 16:12:27 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 84:xx:xx:xx:xx:bc Thu Feb 3 16:12:27 2022 daemon.info hostapd: wlan0: STA 84:xx:xx:xx:xx:bc RADIUS: starting accounting session CA6BD842CC6ADFA2 Thu Feb 3 16:12:27 2022 daemon.info hostapd: wlan0: STA 84:xx:xx:xx:xx:bc WPA: pairwise key handshake completed (RSN) Thu Feb 3 16:12:27 2022 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 84:xx:xx:xx:xx:bc Thu Feb 3 16:12:27 2022 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 84:xx:xx:xx:xx:bc Thu Feb 3 16:12:27 2022 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.1.245 84:xx:xx:xx:xx:bc was when iperf was running iperf worked on PC

Under load iperf, errors are less or completely absent, depending on the position of the phone. "Hardware restart was requested" Didn't see it. Without load and near the hard drive, except for the detected MAC error, I did not see other errors. MTC WR1201 1200M Sony XZ Sorry google translate.

keep watching :)

Thu Feb 3 18:54:04 2022 kern.err kernel: [42055.079264] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 18:54:45 2022 kern.err kernel: [42095.948511] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 18:56:46 2022 kern.info kernel: [42216.917561] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00 Thu Feb 3 18:56:46 2022 kern.info kernel: [42216.928546] mt76x2e 0000:01:00.0: Build: 1 Thu Feb 3 18:56:46 2022 kern.info kernel: [42216.937442] mt76x2e 0000:01:00.0: Build Time: 201706151016____ Thu Feb 3 18:56:46 2022 kern.info kernel: [42216.966283] mt76x2e 0000:01:00.0: Firmware running! Thu Feb 3 18:56:46 2022 kern.info kernel: [42216.986400] ieee80211 phy0: Hardware restart was requested Thu Feb 3 18:56:47 2022 kern.err kernel: [42217.566265] mt76x2e 0000:01:00.0: MAC error detected Thu Feb 3 18:56:48 2022 kern.err kernel: [42218.696279] mt76x2e 0000:01:00.0: MAC error detected observation successful :(

Feb 03 '22 16:02 DruvsEgo

Feb 03 '22 17:02 DruvsEgo

If it only happens occasionally, and the device continues to work afterwards, it should be fine.

Feb 03 '22 17:02 nbd168

If it only happens occasionally, and the device continues to work afterwards, it should be fine.

In my situation "Hardware restart requested" sometimes only appeared next to the hard drive, MAC error detected constantly. When moving further away from the HDD, a clean log. Thanks for your work!

Feb 03 '22 18:02 DruvsEgo

Please try the latest mt76 master version included in my staging tree at https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=summary

The issue still exists.

root@hw24g:~# dmesg | grep mt76x2e [ 17.672474] mt76x2e 0000:02:00.0: ASIC revision: 76120044 [ 18.413702] mt76x2e 0000:02:00.0: ROM patch build: 20141115060606a [ 18.423583] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00 [ 18.429129] mt76x2e 0000:02:00.0: Build: 1 [ 18.433219] mt76x2e 0000:02:00.0: Build Time: 201607111443____ [ 18.457401] mt76x2e 0000:02:00.0: Firmware running! [24454.006365] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00 [24454.011849] mt76x2e 0000:02:00.0: Build: 1 [24454.016086] mt76x2e 0000:02:00.0: Build Time: 201607111443____ [24454.045149] mt76x2e 0000:02:00.0: Firmware running!

Feb 05 '22 18:02 HiGarfield

With that much time inbetween, it seems like a rare occurence. Does the device still work after that error? If so, you can safely ignore it.

Feb 05 '22 19:02 nbd168

With that much time inbetween, it seems like a rare occurence. Does the device still work after that error? If so, you can safely ignore it.

There was no perceptible network disconnection before and after the firmware reset.

Feb 06 '22 03:02 HiGarfield

If it only happens occasionally, and the device continues to work afterwards, it should be fine.

In my situation "Hardware restart requested" sometimes only appeared next to the hard drive, MAC error detected constantly. When moving further away from the HDD, a clean log. Thanks for your work!

A similar case for me. When the portable HDD attached to the router through a USB 3.0 port works in extremely heavy load, the mt76x2e firmware reset potentially occurs.

Feb 06 '22 04:02 HiGarfield

mt76 mt76 copied to clipboard

MT7612EN Constant hardware restart requested on b22977c

mt76
mt76 copied to clipboard