http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c1 Peter S�tterlin changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #1 from Peter S�tterlin --- Still the same issue with Kernel 6.2.4 (TW20230313) -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c3 --- Comment #3 from Peter S�tterlin --- Created attachment 865550 --> http://bugzilla.opensuse.org/attachment.cgi?id=865550&action=edit dmesg output of working kernel 6.1.12 Is 'dmesg' different from the journalctl output? Here's dmesg from the (working) 6.1.12. Computer is at use ATM, so I can't reboot to the non-working kernel. Will do ASAP, if dmesg is needed... -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c5 --- Comment #5 from Peter S�tterlin --- Created attachment 865552 --> http://bugzilla.opensuse.org/attachment.cgi?id=865552&action=edit dmesg output of kernel 6.2.4 OK, here's the non-working one -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c7 --- Comment #7 from Peter S�tterlin --- Created attachment 865562 --> http://bugzilla.opensuse.org/attachment.cgi?id=865562&action=edit hwinfo of affected computer Attached. This is with the 6.1.12 kernel, in case it's important. Maybe some default settings have changed, and I have to add them to some config file now? -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c9 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |P.Suetterlin@royac.iac.es Flags| |needinfo?(P.Suetterlin@roya | |c.iac.es) --- Comment #9 from Takashi Iwai --- In anyway, please check the latest 6.3-rc kernel from OBS Kernel:HEAD. If the problem persists, we'll have to report it to the upstream. OTOH, if the issue is gone with 6.3-rc, some fix can be backported to 6.2.x. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 http://bugzilla.opensuse.org/show_bug.cgi?id=1209254#c13 Peter S�tterlin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(P.Suetterlin@roya | |c.iac.es) | Severity|Major |Normal --- Comment #13 from Peter S�tterlin --- I'm afraid it's the 'somewhere else' issue: Yesterday I DUPed to latest TW (including kernel 6.2.8). After rebooting to my 'safe' kernel 6.1.12, also that one started placing the network card in 10Mbit mode :-o I verified this morning, doing another reboot to 6.1.12, and the network wasn't there. I started suspecting the hardware, and moved the CAT cable from the dock (Lenovo HW dock, not USB-C) to the socket of the laptop itself. Strangely enough, it didn't recognize it (maybe because the laptop was still in the dock - but I'm sure I had it done before that way). When I plugged it back to the dock, network came up without problems, in 1000Mbit mode. I rebooted to 6.2.8, first only got the 10Mbit config, but re-plugging the CAT cable also that kernel brings the network up in 1000Mbit mode. (I know I should have done/tested that before. Didn't think of it :( ... ) So I'm afraid checking other kernels is futile in that situation, and it *might* be a hardware issue of just my setup. As a laptop only rarely gets rebooted remotely, re-plugging is a minor thing. So I've lowered the severity back to normal. Closing for now with 'WORKSFORME'. But let me know if I should do more tests. Thanks for looking at it, and sorry for wasting your time :-o -- You are receiving this mail because: You are the assignee for the bug.