netdev - Re: r8169 link up but no traffic, and watchdog error

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]

Date: Mon, 25 Sep 2023 12:37:58 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Martin Kjær Jørgensen <me@...y.org>,
 Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, nic_swsd@...ltek.com
Subject: Re: r8169 link up but no traffic, and watchdog error

On 25.09.2023 10:36, Martin Kjær Jørgensen wrote:
> 
> On Wed, Aug 09 2023, Jakub Kicinski <kuba@...nel.org> wrote:
> 
>> CC: Heiner
>>
>> On Wed, 09 Aug 2023 13:50:31 +0200 Martin Kjær Jørgensen wrote:
>>
>> There were some fix in r8169 for power management changes recently.
>> Could you try the latest stable kernel? 6.4.9 ?
>>
> 
> Well, neither 6.4.11 nor current debian 'testing' kernel 6.5.3 solved the problem.

You can test with latest 5.15 and 6.1 LTS kernels. If either doesn't show the error,
please bisect. And you could test with vendor driver r8168 or r8125, depending on NIC
version.
The tx timeout error is very generic, based on just this info there's not much we can
do. According to the following log snippet you have 4 NIC's in your system.

[    0.750649] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[    0.771525] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[    0.791797] r8169 0000:08:00.0: can't disable ASPM; OS doesn't have ASPM control
[    0.807683] r8169 0000:09:00.0: can't disable ASPM; OS doesn't have ASPM control

Are some on PCIe extension cards? And does the problem occur with all of your NICs?
The exact NIC type might provide a hint, best provide a full dmesg log.