[FS#3832] [Regression] xrx200 switch affecting AVM Fritz!Box 7362SL
openwrt-bugs at lists.openwrt.org
Thu May 27 16:55:51 PDT 2021
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Matthias Walther (MPW)
Attached to Project - OpenWrt/LEDE Project
Summary - [Regression] xrx200 switch affecting AVM Fritz!Box 7362SL
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - The 7362sl by AVM has two gigabit ports labeled 1+2 and two fast ethernet 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 at 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 at 10000000/pcie at 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.
More information can be found at the following URL:
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the openwrt-bugs