Processing control commands:
> forwarded -1
> https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/
Bug #1060706 [src:linux] linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe
link, network becomes unusable
Set Bug forwarded-to-address to
Control: forwarded -1
https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/
On Monday, 12 February 2024 12:56:45 CET Arno Lehmann wrote:
> Reported upstream, see
>
> https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0d2a@its-lehm
> ann.de/T/#u
Reported upstream, see
https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/T/#u
keep your fingers crossed this will have someone interested ;-)
Cheers,
Arno
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
On Friday, 9 February 2024 13:39:23 CET Arno Lehmann wrote:
> [Fr Feb 9 13:25:08 2024] CPU: 20 PID: 84300 Comm: kworker/20:0 Not
> tainted 6.5.0-0.deb12.4-amd64 #1 Debian 6.5.10-1~bpo12+1
> [Fr Feb 9 13:25:08 2024] Hardware name: ASUS System Product Name/ROG
> STRIX X670E-A GAMING WIFI, BIOS
And another instance, and this time I thought about getting messages
from an attempted igc module reloading.
[Fr Feb 9 13:25:08 2024] igc :0b:00.0 eno1: PCIe link lost, device
now detached
[Fr Feb 9 13:25:08 2024] [ cut here ]
[Fr Feb 9 13:25:08 2024] igc:
Hi all,
so, latest news.
System lost access to the NVMe again and could recover from that only
after powercycling. Pings, until that powercycle, worked so I assume the
NIC and software above it were still functional.
Rebooted into the 6.5 backported kernel, downloaded the newest BIOS,
FWIW I'm having the same problems. Granted, this NIC is in a
Thunderbolt dock, so one can't exclude this as a factor, but the
errors are identical. This is even the case running the 6.7.1-1~exp1
kernel from experimental.
Another one:
[Do Feb 1 04:19:21 2024] igc :0a:00.0 eno1: PCIe link lost, device
now detached
[Do Feb 1 04:19:21 2024] [ cut here ]
[Do Feb 1 04:19:21 2024] igc: Failed to read reg 0xc030!
[Do Feb 1 04:19:21 2024] WARNING: CPU: 6 PID: 90291 at
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 :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]]
Hi all,
I have now installed an early 6.1 kernel:
$ uname -a
Linux Zwerg 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1
(2023-01-07) x86_64 GNU/Linux
and not updated anything else. Also, still running with PCIe power
management in non-default:
# cat /proc/cmdline
Hello,
Am 18.01.2024 um 22:12 schrieb Salvatore Bonaccorso:
Hi,
On Sat, Jan 13, 2024 at 04:39:51PM +0100, Arno Lehmann wrote:
Hi Salvatore,
Am 13.01.2024 um 13:47 schrieb Salvatore Bonaccorso:
Just to be clear, can you confirm this is or is not a regression from
a previous running 6.1.y
Hi,
On Sat, Jan 13, 2024 at 04:39:51PM +0100, Arno Lehmann wrote:
> Hi Salvatore,
>
> Am 13.01.2024 um 13:47 schrieb Salvatore Bonaccorso:
>
> > Just to be clear, can you confirm this is or is not a regression from
> > a previous running 6.1.y kernel?
>
> On this hardware, the network issues
On Saturday, 13 January 2024 20:22:39 CET Arno Lehmann wrote:
> Am 13.01.2024 um 17:13 schrieb Diederik de Haas:
> > Via https://snapshot.debian.org/package/linux-signed-amd64/ you have easy
> > access to previous (6.1) kernels uploaded to Debian with which you can
> > check if the problem was
Hi Diederik,
Am 13.01.2024 um 17:13 schrieb Diederik de Haas:
...
Via https://snapshot.debian.org/package/linux-signed-amd64/ you have easy
access to previous (6.1) kernels uploaded to Debian with which you can check
if the problem was present in early 6.1 kernels.
The oldest record of this
On Saturday, 13 January 2024 16:39:51 CET Arno Lehmann wrote:
> > Just to be clear, can you confirm this is or is not a regression from
> > a previous running 6.1.y kernel?
>
> On this hardware, the network issues appeared right from the start.
> ...
> Actually I don't even know which was the
Hi Salvatore,
Am 13.01.2024 um 13:47 schrieb Salvatore Bonaccorso:
Just to be clear, can you confirm this is or is not a regression from
a previous running 6.1.y kernel?
On this hardware, the network issues appeared right from the start.
First time I encountered it was with the Debian
Am 13.01.2024 um 12:48 schrieb Diederik de Haas:
On Saturday, 13 January 2024 11:45:29 CET Arno Lehmann wrote:
Hardware name: ASUS System Product Name/ROG STRIX X670E-A GAMING WIFI,
BIOS 1410 04/28/2023
Possibly not related, but there's BIOS 1807 available.
I'll definitely give that a try
Processing control commands:
> tags -1 + moreinfo
Bug #1060706 [src:linux] linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe
link, network becomes unusable
Added tag(s) moreinfo.
--
1060706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060706
Debian Bug Tracking System
Contact
Control: tags -1 + moreinfo
On Sat, Jan 13, 2024 at 11:45:29AM +0100, Arno Lehmann wrote:
> Package: src:linux
> Version: 6.1.69-1
> Severity: normal
> Tags: upstream
>
> Dear Maintainer,
>
>
> just having the computer run for a while, the network loses connection because
> the NIC detached
On Saturday, 13 January 2024 11:45:29 CET Arno Lehmann wrote:
> Hardware name: ASUS System Product Name/ROG STRIX X670E-A GAMING WIFI,
> BIOS 1410 04/28/2023
Possibly not related, but there's BIOS 1807 available.
signature.asc
Description: This is a digitally signed message part.
Package: src:linux
Version: 6.1.69-1
Severity: normal
Tags: upstream
Dear Maintainer,
just having the computer run for a while, the network loses connection because
the NIC detached from PCIe. I suspect this is related to power management but
am not really sure.
As this seemed to be a known
21 matches
Mail list logo
