Bug#1060706: Info received (Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)
Some news, but unfortunately not helping me to understand what we see :-)
Network link was lost during the day.
dmesg shows this:
[Tue Jan 23 06:54:24 2024] igc 0000:0a:00.0 eno1: NIC Link is Up 1000
Mbps Full Duplex, Flow Control: RX
[Tue Jan 23 16:24:13 2024] [drm:retrieve_link_cap [amdgpu]] *ERROR*
retrieve_link_cap: Read receiver caps dpcd data failed.
[Tue Jan 23 23:09:16 2024] igc 0000:0a:00.0 eno1: NIC Link is Down
[Tue Jan 23 23:09:19 2024] igc 0000:0a:00.0 eno1: NIC Link is Up 1000
Mbps Full Duplex, Flow Control: RX
[Wed Jan 24 12:00:23 2024] systemd-journald[750]:<irrelevant>
[Wed Jan 24 14:46:17 2024] nfs: server <redacted> not responding, timed out
[Wed Jan 24 14:46:17 2024] nfs: server <redacted> not responding, timed out
[Wed Jan 24 17:00:09 2024] nfs: server <redacted> not responding, timed out
Here, I rmmod'ed the igc module and modprobe'd it immediately.
[Wed Jan 24 17:00:36 2024] igc 0000:0a:00.0 eno1: PHC removed
[Wed Jan 24 17:00:42 2024] Intel(R) 2.5G Ethernet Linux Driver
[Wed Jan 24 17:00:42 2024] Copyright(c) 2018 Intel Corporation.
[Wed Jan 24 17:00:42 2024] igc 0000:0a:00.0: PCIe PTM not supported by
PCIe bus/controller
[Wed Jan 24 17:00:42 2024] pps pps0: new PPS source ptp0
[Wed Jan 24 17:00:42 2024] igc 0000:0a:00.0 (unnamed net_device)
(uninitialized): PHC added
[Wed Jan 24 17:00:42 2024] igc 0000:0a:00.0: 4.000 Gb/s available PCIe
bandwidth (5.0 GT/s PCIe x1 link)
[Wed Jan 24 17:00:42 2024] igc 0000:0a:00.0 eth0: MAC: c8:7f:54:67:6d:cc
[Wed Jan 24 17:00:42 2024] igc 0000:0a:00.0 eno1: renamed from eth0
[Wed Jan 24 17:00:45 2024] igc 0000:0a:00.0 eno1: NIC Link is Up 1000
Mbps Full Duplex, Flow Control: RX
[Wed Jan 24 17:00:45 2024] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link
becomes ready
So, we have a case of the NIC becoming unresponsive for some reason, but
I can not see or even guess the reason. I'll leave the system as it is
for a few more days, I think, and then try a much newer kernel.
Or -- any better suggestions?
Cheers,
Arno
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
Reply to: