camus
February 18, 2022, 10:55pm
1
Hello,
frollic
February 18, 2022, 11:17pm
4
It had already been reported though...
opened 02:27PM - 10 Feb 22 UTC
release/21.02
_Link to this issue in the old bugtracker: [FS#3832 - [Regression] xrx200 switch… affecting AVM Fritz!Box 7362SL](https://bugs.openwrt.org/index.php?do=details&task_id=3832)_
**Recap:**
- The AVM FRITZ!Box 7362SL router has four LAN ports:
- ports 1 and 2 support gigabit speed
- ports 3 and 4 support fast ethernet speed
- On OpenWrt 19.07 (e.g. 19.07.7 kernel 4.14.221) all LAN ports are working correctly
- On OpenWrt 21.02 (e.g. OpenWrt 21.02.0-rc1 kernel 5.4.111, 21.02.1 kernel 5.4.154), LAN ports 1 and 2 work while LAN ports 3 and 4 are not working correctly:
- physical link (layer 1) is working
- fast ethernet connection is working
- as soon as at least one gigabit speed capable device is connected to port 3 or 4, both ports stop working
- when connecting a gigabit speed capable device to port 3 or 4, LuCI (/cgi-bin/luci/admin/network/switch) shows "1000baseT full-duplex" for that port, while only 100baseT would be supported by the router
**Selected quotes from the old issue:**
_Matthias Walther - 27.05.2021_
> Notably might be the line ”failed to get the PCIe PHY“ which does not appear in 19.07.7.
>
> As I didn’t notice any changes regarding this particular device model, it might be a problem with the kernel driver for the switch module.
_Matthias Walther - 02.06.2021_
> I also looked into the git history. Maybe this commit has something to do with the regression:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f8ea7c53fd227a9c21f0ca45a2c3345312ea54b5
Various log-/debug-output can be found in the archived issue in the old bugtracker.
camus
February 20, 2022, 11:31pm
6
I wonder how and when bugs are fixed, also how to know they have been fixed.
Follow the existing Open issue on GitHub...
opened 11:55PM - 27 May 21 UTC
flyspray
*MPW:*
The 7362sl by AVM has two gigabit ports labeled 1+2 and two fast etherne… t ports labled 3+4.
They all used to work, but with OpenWrt 21.02.0 only the two gigabit ports work. Port 3+4 are dead. Linked (layer1) can be established, no layer2 or higher traffic possible.
OpenWrt 19.07.7 Kernel 4.14.221 supports ports 3 + 4
Openwrt 21.02.0-rc1 Kernel 5.4.111 ports 3 + 4 are dead
```
root@OpenWrt:~# dmesg|grep -A5 -B5 PHY
[ 0.163028] pinctrl core: initialized pinctrl subsystem
[ 0.170653] NET: Registered protocol family 16
[ 0.183980] dcdc-xrx200 1f106a00.dcdc: Core Voltage : 1016 mV
[ 0.198588] pinctrl-xway 1e100b10.pinmux: Init done
[ 0.205140] dma-xway 1e104100.dma: Init done - hw rev: 7, ports: 7, channels: 28
[ 0.216895] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.265910] usbcore: registered new interface driver usbfs
[ 0.271499] usbcore: registered new interface driver hub
[ 0.276869] usbcore: registered new device driver usb
[ 0.282522] workqueue: max_active 576 requested for napi_workq is out of range, clamping between 1 and 512
[ 0.294467] clocksource: Switched to clocksource MIPS
--
[ 0.708199] NET: Registered protocol family 10
[ 0.715876] Segment Routing with IPv6
[ 0.718218] NET: Registered protocol family 17
[ 0.722769] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 0.735555] 8021q: 802.1Q VLAN Support v1.8
[ 0.746142] pcie-xrx200 1d900000.pcie: failed to get the PCIe PHY
[ 0.859313] libphy: lantiq,xrx200-mdio: probed
[ 0.869051] net-xrx200: invalid MAC, using random
[ 0.872575] Atheros 8030 ethernet 0:00: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:00, irq=POLL)
[ 0.883256] Atheros 8030 ethernet 0:01: attached PHY driver [Atheros 8030 ethernet] (mii_bus:phy_addr=0:01, irq=POLL)
[ 0.894242] Intel XWAY PHY11G (xRX v1.2 integrated) 0:11: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:11, irq=POLL)
[ 0.907971] Intel XWAY PHY11G (xRX v1.2 integrated) 0:13: attached PHY driver [Intel XWAY PHY11G (xRX v1.2 integrated)] (mii_bus:phy_addr=0:13, irq=POLL)
[ 1.046546] PCI host bridge /fpi@10000000/pcie@d900000 ranges:
[ 1.051221] PCI host bridge to bus 0000:00
[ 1.055083] pci_bus 0000:00: root bus resource [mem 0x1c000000-0x1cffffff]
[ 1.061969] pci_bus 0000:00: root bus resource [io 0x1d800000-0x1d8fffff]
[ 1.068840] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
```
Notably might be the line ”failed to get the PCIe PHY“ which does not appear in 19.07.7.
As I didn't notice any changes regarding this particular device model, it might be a problem with the kernel driver for the switch module.
All of the other duplicate reports have been closed, and merged under this one.
camus
March 1, 2022, 2:18pm
8
can someone please educate me on how things are done concerning bugs with the firmware. to be precise; how are bugs handled, by who and is there a way to know the status of a bug, so to speak; whether developers know about it and are working on it. thanks a lot.
status can be seen in the actual bug report.
scroll (usually) all the way down to the bottom.
camus
March 1, 2022, 2:28pm
10
thanks a lot @frollic while i have your attention, I was just reading the 21.2.02 release notes, but can't determine whether the issue discovered (of lan ports 3 and 4 not working on some avm boxes) was addressed in that release; would you happen to know?
the main bug report is still open, as I can see, so I'd say no.
camus
March 1, 2022, 2:44pm
12
thanks a lot. I just saw the discussion, fresh, as in an hour ago.
system
March 11, 2022, 2:45pm
13
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.