From: "Martin Kjær Jørgensen" <me@lagy.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, nic_swsd@realtek.com
Subject: Re: r8169 link up but no traffic, and watchdog error
Date: Mon, 25 Sep 2023 17:41:47 +0200 [thread overview]
Message-ID: <87ttriqmru.fsf@ws.c.lan> (raw)
In-Reply-To: <e391ca3b-c3e8-478a-a771-2554b8b828c0@gmail.com>
On Mon, Sep 25 2023, Heiner Kallweit <hkallweit1@gmail.com> wrote:
> On 25.09.2023 13:30, Martin Kjær Jørgensen wrote:
>>
>> On Mon, Sep 25 2023, Heiner Kallweit <hkallweit1@gmail.com> wrote:
>>
>>
>> There are no PCI extension cards.
>>
>
> Your BIOS signature indicates that the system is a Thinkstation P350.
> According to the Lenovo website it comes with one Intel-based network port.
> However you have additional 4 Realtek-based network ports on the mainboard?
>
Yes. 2 PCIE cards with two Realtek ethernet controllers each.
>>> And does the problem occur with all of your NICs?
>>
>> No, only the Realtek ones.
>>
>>> The exact NIC type might provide a hint, best provide a full dmesg log.
>> [ 1512.295490] RSP: 0018:ffffbc0240193e88 EFLAGS: 00000246
>> [ 1512.295492] RAX: ffff998935680000 RBX: ffffdc023faa8e00 RCX: 000000000000001f
>> [ 1512.295493] RDX: 0000000000000002 RSI: ffffffffb544f718 RDI: ffffffffb543bc32
>> [ 1512.295494] RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000018
>> [ 1512.295495] R10: ffff9989356b1dc4 R11: 00000000000058a8 R12: ffffffffb5d981a0
>> [ 1512.295496] R13: 000001601bd198ef R14: 0000000000000003 R15: 0000000000000000
>> [ 1512.295497] ? cpuidle_enter_state+0xbd/0x440
>> [ 1512.295499] cpuidle_enter+0x2d/0x40
>> [ 1512.295501] do_idle+0x217/0x270
>> [ 1512.295503] cpu_startup_entry+0x1d/0x20
>> [ 1512.295505] start_secondary+0x11a/0x140
>> [ 1512.295508] secondary_startup_64_no_verify+0x17e/0x18b
>> [ 1512.295510] </TASK>
>> [ 1512.295511] ---[ end trace 0000000000000000 ]---
>> [ 1512.295526] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
>> [ 1531.322039] r8169 0000:03:00.0 enp3s0: Link is Down
>> [ 1534.138489] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
>> [ 1538.177385] r8169 0000:03:00.0 enp3s0: Link is Down
>> [ 1566.174660] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
>> [ 1567.839082] r8169 0000:03:00.0 enp3s0: Link is Down
>> [ 1570.621088] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
>> [ 1576.294267] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
>
> Regarding the following: Issue occurs after few seconds of link-loss.
> Was this an intentional link-down event?
Yes, I intentionally unplug the cable at the other end for the link to go down.
> And is issue always related to link-up after a link-loss period?
>
Yes, it happends after cable is plugged in again, so after a link-loss period.
>> [ 1488.643231] r8169 0000:03:00.0 enp3s0: Link is Down
>> [ 1506.576941] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
>> [ 1512.295215] ------------[ cut here ]------------
>> [ 1512.295219] NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0 timed out 5368 ms
next prev parent reply other threads:[~2023-09-25 15:46 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
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 [this message]
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=87ttriqmru.fsf@ws.c.lan \
--to=me@lagy.org \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.