Hello,
it seems that I had another problem when upgrading from 4.14 to 5.4.
In 4.14 network config I had no switch definition and it worked out of the box.
But with 5.4 I need a switch config in network config like that:
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
option metric '10'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0 1 2 3 6t'
Sorry for the noise.
I could now check one of the bricked devices and found no hint for the FC issue.
Kind regards,
André
Am 06.08.20 um 14:31 schrieb Andre Valentin:
> Hi Jaap,
>
>
> Am 06.08.20 um 13:43 schrieb Jaap Buurman:
>> Dear all,
>>
>> I have noticed the flow control work for mt7621 in the following
>> Openwrt patch:
>> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=c8f8e59816eca49d776562d2d302bf990a87faf0
>>
>> However, the problem that the patch is supposed to fix is still
>> occurring, even in combination with other experimental patches
>> submitted. These experiences can be read about here:
>> https://forum.openwrt.org/t/mtk-soc-eth-watchdog-timeout-after-r11573/50000/
>>
>> However, on this mailing list a user by the name of Kristian claims
>> that disabling flow control helps fix this problem, as can be read
>> here:
>> https://lists.openwrt.org/pipermail/openwrt-devel/2017-November/009882.html
>>
>> From what I understood, he was running many mt7621 devices
>> commercially, with many of them experiencing the issue, which were all
>> fixed with his own flow control patch. My question is why the decision
>> was made to only disable flow control on port 5 in the above mentioned
>> Openwrt patch? AFAIK, Kristian's own patch disables flow control on
>> all of the ports and he claims the issue is fixed for him. Perhaps the
>> current patch should be extended to disable flow control on all ports?
>> What are people's thoughts on this?
>
> I'm facing the same issue now after upgrading to 5.4 kernel more often than
> before.
> Every second reboot reboot with 5.4 fails with this timeout error.
>
>>
>> Yours sincerely,
>>
>> Jaap
>
> André
>
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
--
Mit freundlichen Grüßen
André Valentin
Systemadministration - Projektkoordination
--
MarcanT AG, Herforder Straße 163a, D - 33609 Bielefeld
Fon: +49 (521) 95945-0 | Fax: +49 (521) 95945-18
URL: http://www.marcant.net <http://www.marcant.net/> |
http://www.global-m2m.com <http://www.global-m2m.com/>
Internet * Netzwerk * Mobile Daten
Vorstand:
Thorsten Hojas (Vorsitzender)
Marc-Henrik Delker
Dr. Anja-Christina Padberg
Handelsregister: AG Bielefeld, HRB 42260 USt-ID Nr.: DE 190203238
___________________________________________________________
Ausserhalb unserer Geschäftszeiten (Montag bis Freitag von 8:30 Uhr bis
17:30 Uhr, ausgenommen gesetzliche Feiertage in NRW) stehen wir Ihnen
gemäß Ihrer jeweiligen Service-Level-Agreements unter der Ihnen
mitgeteilten Telefonnummer für Störungen und Notfälle zur Verfügung.
Sie können natürlich auch gerne jederzeit unter supp...@marcant.net ein
Ticket eröffnen, welches am nächsten Arbeitstag bearbeitet wird.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
