From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Martin Kjær Jørgensen" <me@lagy.org>
Cc: nic_swsd@realtek.com, Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: r8169 link up but no traffic, and watchdog error
Date: Thu, 24 Aug 2023 10:21:15 +0200 [thread overview]
Message-ID: <22ef754e-1d6c-652e-c626-edc571530a3b@gmail.com> (raw)
In-Reply-To: <87bkew98ai.fsf@lagy.org>
On 24.08.2023 10:01, Martin Kjær Jørgensen wrote:
>
> On Thu, Aug 24 2023, Heiner Kallweit <hkallweit1@gmail.com> wrote:
>
>> On 18.08.2023 13:49, Martin Kjær Jørgensen wrote:
>>>
>>> On Wed, Aug 09 2023, Jakub Kicinski <kuba@kernel.org> wrote:
>>>
>>>>
>>>> There were some fix in r8169 for power management changes recently.
>>>> Could you try the latest stable kernel? 6.4.9 ?
>>>>
>>>
>>> I have just upgraded to latest Debian testing kernel (6.4.0-3-amd64 #1 SMP
>>> PREEMPT_DYNAMIC Debian 6.4.11-1) but it doesn't seem to make much
>>> difference. I can trigger the same issue again, and get similar kernel error
>>> as before:
>>>
>
>
>> From the line above it's not clear which kernel version is used. Best test with a
>> self-compiled mainline kernel.
>>
>
> It should be based on 6.4.11 , but I can try with a self-compiled version too.
>
>>
>> Please test also with the different ASPM L1 states disabled, you can use the sysfs
>> attributes under /sys/class/net/enp3s0/device/link/ for this.
>>
>
> I will try that.
>
>
>> Best bisect between last known good kernel and latest 6.4 version.
>>
>
> I do not know of any working version. My machine/system have had this behavior
> ever since I've got it. At least for 9 months ...
You could compile and test the LTS versions 6.1 and 5.15.
next prev parent reply other threads:[~2023-08-24 8:21 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 [this message]
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
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=22ef754e-1d6c-652e-c626-edc571530a3b@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).