From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Martin Kjær Jørgensen" <me@lagy.org>,
"Jakub Kicinski" <kuba@kernel.org>
Cc: netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: r8169 link up but no traffic, and watchdog error
Date: Mon, 25 Sep 2023 12:37:58 +0200 [thread overview]
Message-ID: <4ed0991b-5473-409d-b00a-bf71f0877df5@gmail.com> (raw)
In-Reply-To: <87a5taabs9.fsf@mkjws.danelec-net.lan>
On 25.09.2023 10:36, Martin Kjær Jørgensen wrote:
>
> On Wed, Aug 09 2023, Jakub Kicinski <kuba@kernel.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.
next prev parent reply other threads:[~2023-09-25 10:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 11:50 r8169 link up but no traffic, and watchdog error Martin Kjær Jørgensen
2023-08-09 19:58 ` Jakub Kicinski
2023-08-18 11:49 ` Martin Kjær Jørgensen
2023-08-24 7:52 ` Heiner Kallweit
2023-08-24 8:01 ` Martin Kjær Jørgensen
2023-08-24 8:21 ` Heiner Kallweit
2023-08-24 9:22 ` Martin Kjær Jørgensen
2023-08-25 16:55 ` Heiner Kallweit
2023-09-25 8:36 ` Martin Kjær Jørgensen
2023-09-25 10:37 ` Heiner Kallweit [this message]
2023-09-25 11:30 ` Martin Kjær Jørgensen
2023-09-25 15:38 ` Heiner Kallweit
2023-09-25 15:41 ` Martin Kjær Jørgensen
2023-09-25 15:59 ` Heiner Kallweit
2024-03-22 11:28 ` Martin Kjær Jørgensen
2024-03-22 12:26 ` Heiner Kallweit
2024-03-23 11:18 ` Heiner Kallweit
2023-09-25 20:38 ` Heiner Kallweit
2023-10-02 8:28 ` Martin Kjær Jørgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ed0991b-5473-409d-b00a-bf71f0877df5@gmail.com \
--to=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=me@lagy.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).