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  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]
Date:   Mon, 7 Feb 2022 20:49:35 +0530
From:   Shyam Sundar S K <Shyam-sundar.S-k@....com>
To:     Tom Lendacky <thomas.lendacky@....com>,
        Thomas Kupper <thomas@...per.org>
Cc:     netdev@...r.kernel.org
Subject: Re: AMD XGBE "phy irq request failed" kernel v5.17-rc2 on V1500B
 based board



On 2/7/2022 8:02 PM, Tom Lendacky wrote:
> On 2/5/22 12:14, Thomas Kupper wrote:
>> Am 05.02.22 um 16:51 schrieb Tom Lendacky:
>>> On 2/5/22 04:06, Thomas Kupper wrote:
> 
>>>
>>> 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.
>>>
>>
>> Right after boot:
>>
>> [    5.352977] amd-xgbe 0000:06:00.1 eth0: net device enabled
>> [    5.354198] amd-xgbe 0000:06:00.2 eth1: net device enabled
>> ...
>> [    5.382185] amd-xgbe 0000:06:00.1 enp6s0f1: renamed from eth0
>> [    5.426931] amd-xgbe 0000:06:00.2 enp6s0f2: renamed from eth1
>> ...
>> [    9.701637] amd-xgbe 0000:06:00.2 enp6s0f2: phy powered off
>> [    9.701679] amd-xgbe 0000:06:00.2 enp6s0f2: CL73 AN disabled
>> [    9.701715] amd-xgbe 0000:06:00.2 enp6s0f2: CL37 AN disabled
>> [    9.738191] amd-xgbe 0000:06:00.2 enp6s0f2: starting PHY
>> [    9.738219] amd-xgbe 0000:06:00.2 enp6s0f2: starting I2C
>> ...
>> [   10.742622] amd-xgbe 0000:06:00.2 enp6s0f2: firmware mailbox
>> command did not complete
>> [   10.742710] amd-xgbe 0000:06:00.2 enp6s0f2: firmware mailbox reset
>> performed
>> [   10.750813] amd-xgbe 0000:06:00.2 enp6s0f2: 10GbE SFI mode set
>> [   10.768366] amd-xgbe 0000:06:00.2 enp6s0f2: 10GbE SFI mode set
>> [   10.768371] amd-xgbe 0000:06:00.2 enp6s0f2: fixed PHY configuration
>>
>> Then after 'ifconfig enp6s0f2 up':
>>
>> [  189.184928] amd-xgbe 0000:06:00.2 enp6s0f2: phy powered off
>> [  189.191828] amd-xgbe 0000:06:00.2 enp6s0f2: 10GbE SFI mode set
>> [  189.191863] amd-xgbe 0000:06:00.2 enp6s0f2: CL73 AN disabled
>> [  189.191894] amd-xgbe 0000:06:00.2 enp6s0f2: CL37 AN disabled
>> [  189.196338] amd-xgbe 0000:06:00.2 enp6s0f2: starting PHY
>> [  189.198792] amd-xgbe 0000:06:00.2 enp6s0f2: 10GbE SFI mode set
>> [  189.212036] genirq: Flags mismatch irq 69. 00000000 (enp6s0f2-pcs)
>> vs. 00000000 (enp6s0f2-pcs)
>> [  189.221700] amd-xgbe 0000:06:00.2 enp6s0f2: phy irq request failed
>> [  189.231051] amd-xgbe 0000:06:00.2 enp6s0f2: phy powered off
>> [  189.231054] amd-xgbe 0000:06:00.2 enp6s0f2: stopping I2C
>>
> 
> Please ensure that the ethtool msglvl is on for drv and probe. I was
> expecting to see some additional debug messages that I don't see here.
> 
> Also, if you can provide the lspci output for the device (using -nn and
> -vv) that might be helpful as well.
> 
> Shyam will be the best one to understand what is going on here.

On some other platforms, we have seen similar kind of problems getting
reported. There is a fix sent for validation.

The root cause is that removal of xgbe driver is causing interrupt storm
on the MP2 device (Sensor Fusion Hub).

Shall submit a fix soon to upstream once the validation is done, you may
give it a try with that and see if that helps.

Thanks,
Shyam

> 
> Thanks,
> Tom

Powered by blists - more mailing lists