[Bug 1211985] New: kernel: RTNL: assertion failed at net/core/dev.c (2879)
https://bugzilla.suse.com/show_bug.cgi?id=1211985 Bug ID: 1211985 Summary: kernel: RTNL: assertion failed at net/core/dev.c (2879) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867393 --> https://bugzilla.suse.com/attachment.cgi?id=867393&action=edit stack trace openSUSE Tumbleweed 20230601 Linux 6.3.4-1-default kernel stack trace: kernel: RTNL: assertion failed at net/core/dev.c (2879) see log There was nothing special going on, when this happened. The akonadiserver message 3 minutes before was the latest, before the crash occurred. Afterwards the igb net device was gone. After a reboot everything seems to work again. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c1 --- Comment #1 from Michael Hirmke <opensuse@mike.franken.de> --- Similar crash already happend once: Mai 29 10:16:22 client kernel: pcieport 0000:00:07.2: PME: Spurious native interrupt! Mai 29 10:16:22 client kernel: ------------[ cut here ]------------ Mai 29 10:16:22 client kernel: RTNL: assertion failed at net/core/dev.c (2877) Mai 29 10:16:22 client kernel: WARNING: CPU: 3 PID: 28355 at net/core/dev.c:2877 netif_set_real_num_tx_queues+0x1e7/0x200 In this case, the device war still available afterwards. This was with kernel 6.3.2-1-default. See log. At least four times since Mai 07 I got Mai 29 10:16:22 client kernel: pcieport 0000:00:07.2: PME: Spurious native interrupt! Mai 29 20:46:51 client kernel: pcieport 0000:00:07.2: PME: Spurious native interrupt! Mai 30 06:12:35 client kernel: pcieport 0000:00:07.2: PME: Spurious native interrupt! Mai 30 07:41:06 client kernel: pcieport 0000:00:07.2: PME: Spurious native interrupt! So the problems seem to have started with kernel 6.3.2-1-default. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c2 --- Comment #2 from Michael Hirmke <opensuse@mike.franken.de> --- Created attachment 867394 --> https://bugzilla.suse.com/attachment.cgi?id=867394&action=edit stack trace 2 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 Michael Hirmke <opensuse@mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c3 --- Comment #3 from Michael Hirmke <opensuse@mike.franken.de> --- The concrete reason was a dying switch. But I can reproduce the crash just by unplugging the lan cable from the new switch. The notebook is connected via thunderbolt to a thunderbolt box and this box is connected via lan cable with the switch. Unplugging the thunderbolt cable from either the notebook or the thunderbolt box doesn't lead to the crash, but unplugging the lan cable from the thunderbolt box or the switch leads to it. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c4 --- Comment #4 from Michael Hirmke <opensuse@mike.franken.de> --- No one? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c5 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby@suse.com Resolution|--- |WORKSFORME --- Comment #5 from Jiri Slaby <jslaby@suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1211985 https://bugzilla.suse.com/show_bug.cgi?id=1211985#c6 --- Comment #6 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Jiri Slaby from comment #5)
This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that.
You still can reopen if this still happens. But it would make more sense to report and handle this upstream.
Just tested it and as it seems, the problem is fixed indeed. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com