netdev - Re: AMD XGBE "phy irq request failed" kernel v5.17-rc2 on V1500B based board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c3e8cbdc-d3f9-d258-fcb6-761a5c6c89ed@amd.com>
Date:   Sat, 5 Feb 2022 09:51:00 -0600
From:   Tom Lendacky <thomas.lendacky@....com>
To:     Thomas Kupper <thomas@...per.org>,
        Shyam Sundar S K <Shyam-sundar.S-k@....com>
Cc:     netdev@...r.kernel.org
Subject: Re: AMD XGBE "phy irq request failed" kernel v5.17-rc2 on V1500B
 based board

On 2/5/22 04:06, Thomas Kupper wrote:
> Hi,
> 
> I got an OPNsense DEC740 firewall which is based on the AMD V1500B CPU.
> 
> OPNsense runs fine on it but on Linux I'm not able to get the 10GbE 
> interfaces to work.
> 
> My test setup is based on Ubuntu 21.10 Impish Indri with a v5.17-rc2 
> kernel compiled from Mr Torvalds sources, tag v5.17-rc2. The second 10GbE 
> interface (enp6s0f2) is set to receive the IP by DHCPv4.
> 
> The relevant dmesg entries after boot are:
> 
> [    4.763712] libphy: amd-xgbe-mii: probed
> [    4.782850] amd-xgbe 0000:06:00.1 eth0: net device enabled
> [    4.800625] libphy: amd-xgbe-mii: probed
> [    4.803192] amd-xgbe 0000:06:00.2 eth1: net device enabled
> [    4.841151] amd-xgbe 0000:06:00.1 enp6s0f1: renamed from eth0
> [    5.116617] amd-xgbe 0000:06:00.2 enp6s0f2: renamed from eth1
> 
> After that I see a link up on the switch for enp6s0f2 and the switch 
> reports 10G link speed.
> 
> ethtool reports:
> 
> $ sudo ethtool enp6s0f2
> Settings for enp6s0f2:
>          Supported ports: [ FIBRE ]
>          Supported link modes:   Not reported
>          Supported pause frame use: No
>          Supports auto-negotiation: No
>          Supported FEC modes: Not reported
>          Advertised link modes:  Not reported
>          Advertised pause frame use: No
>          Advertised auto-negotiation: No
>          Advertised FEC modes: Not reported
>          Speed: Unknown!
>          Duplex: Unknown! (255)
>          Auto-negotiation: off
>          Port: None
>          PHYAD: 0
>          Transceiver: internal
>          Current message level: 0x00000034 (52)
>                                 link ifdown ifup
>          Link detected: no
> 
> 
> Manually assigning an IP and pull the interface up and I end up with:
> 
> $ sudo ifconfig enp6s0f2 up
> 
> SIOCSIFFLAGS: Device or resource busy
> 
> ... and dmesg reports:
> 
> [  648.038655] genirq: Flags mismatch irq 59. 00000000 (enp6s0f2-pcs) vs. 
> 00000000 (enp6s0f2-pcs)
> [  648.048303] amd-xgbe 0000:06:00.2 enp6s0f2: phy irq request failed
> 
> After that the lights are out on the switch for that port and it reports 
> 'no link'
> 
> Would that be an known issue or is that configuration simply not yet 
> supported?
> 

Reloading the module and specify the dyndbg option to get some additional 
debug output.

I'm adding Shyam to the thread, too, as I'm not familiar with the 
configuration for this chip.

Thanks,
Tom

> 
> Kind Regards
> 
> Thomas Kupper
>