February 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219690] New: Recurring Kernel panic
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219690 Bug ID: 1219690 Summary: Recurring Kernel panic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sakphul(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:122.0) Gecko/20100101 Firefox/122.0 Build Identifier: System randomly stalls/hangs after updating the Motherboard BIOS/CPU. Kernel is reporting an issue in RCU context switching. Here is one error message: Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2d940 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2cf80 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2c900 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb105984ae0 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb1059d67e0 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2d940 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2cf80 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb107f2c900 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb105984ae0 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox.desktop[7322]: [Parent 7322, Main Thread] WARNING: Couldn't map window 0x7fb1059d67e0 as subsurface because its parent is not mapped.: 'glib warning', file /home/abuild/rpmbuild/BUILD/firefox-122.0/too> Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2d940 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2cf80 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2c900 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb105984ae0 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb1059d67e0 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2d940 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2cf80 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb107f2c900 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb105984ae0 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop firefox[7322]: Couldn't map window 0x7fb1059d67e0 as subsurface because its parent is not mapped. Feb 07 21:31:39 desktop rtkit-daemon[24839]: Successfully made thread 2647 of process 2613 owned by 'albert' high priority at nice level 0. Feb 07 21:31:39 desktop kernel: usb 1-7.1: new full-speed USB device number 15 using xhci_hcd Feb 07 21:31:39 desktop rtkit-daemon[24839]: Successfully made thread 2647 of process 2613 owned by 'albert' RT at priority 20. Feb 07 21:31:39 desktop rtkit-daemon[24839]: Successfully made thread 27399 of process 3531 owned by 'albert' RT at priority 5. Feb 07 21:31:39 desktop kernel: usb 1-7.1: New USB device found, idVendor=0c76, idProduct=161e, bcdDevice= 1.00 Feb 07 21:31:39 desktop kernel: usb 1-7.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 Feb 07 21:31:39 desktop kernel: usb 1-7.1: Product: USB PnP Audio Device Feb 07 21:31:39 desktop kernel: usb 1-7.1: Warning! Unlikely big volume range (=496), cval->res is probably wrong. Feb 07 21:31:39 desktop kernel: usb 1-7.1: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 Feb 07 21:31:39 desktop kernel: input: USB PnP Audio Device as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7/1-7.1/1-7.1:1.2/0003:0C76:161E.000E/input/input28 Feb 07 21:31:39 desktop kernel: hid-generic 0003:0C76:161E.000E: input,hidraw0: USB HID v1.00 Device [USB PnP Audio Device] on usb-0000:02:00.0-7.1/input2 Feb 07 21:31:39 desktop mtp-probe[27401]: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7/1-7.1" Feb 07 21:31:39 desktop mtp-probe[27401]: bus: 1, device: 15 was not an MTP device Feb 07 21:31:39 desktop mtp-probe[27411]: checking bus 1, device 15: "/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7/1-7.1" Feb 07 21:31:39 desktop mtp-probe[27411]: bus: 1, device: 15 was not an MTP device Feb 07 21:31:39 desktop rtkit-daemon[24839]: Successfully made thread 27414 of process 3531 owned by 'albert' RT at priority 5. Feb 07 21:31:49 desktop kernel: traps: gnome-shell[2613] general protection fault ip:7f1f49840350 sp:7fffe0b64650 error:0 in libmozjs-115.so.0.0.0 (deleted)[7f1f492f2000+ad7000] Feb 07 21:31:49 desktop systemd[1]: Started Process Core Dump (PID 27418/UID 0). Feb 07 21:31:49 desktop kernel: general protection fault, probably for non-canonical address 0x8000000000000: 0000 [#1] PREEMPT SMP NOPTI Feb 07 21:31:49 desktop kernel: CPU: 2 PID: 2613 Comm: gnome-shell Not tainted 6.7.2-1-default #1 openSUSE Tumbleweed 2ebfa03c136f8452443a794052b1fbb2172d83ef Feb 07 21:31:49 desktop kernel: Hardware name: To Be Filled By O.E.M. AB350 Gaming-ITX/ac/AB350 Gaming-ITX/ac, BIOS P7.40 10/27/2022 Feb 07 21:31:49 desktop kernel: RIP: 0010:next_uptodate_folio+0xb7/0x240 Feb 07 21:31:49 desktop kernel: Code: c7 48 85 ff 0f 84 2a 01 00 00 48 81 ff 06 04 00 00 0f 84 9e 00 00 00 48 81 ff 02 04 00 00 74 cb 40 f6 c7 01 0f 85 8b 00 00 00 <48> 8b 07 a8 01 0f 85 80 00 00 00 8b 47 34 85 c0 74 79 8d 50 01 4c Feb 07 21:31:49 desktop kernel: RSP: 0018:ffffb32e44503710 EFLAGS: 00010246 Feb 07 21:31:49 desktop kernel: RAX: 0008000000000000 RBX: ffffb32e44503798 RCX: 0000000000000000 Feb 07 21:31:49 desktop kernel: RDX: 000000000000001d RSI: ffff8ce3defbb478 RDI: 0008000000000000 Feb 07 21:31:49 desktop kernel: RBP: 0000000000001d9f R08: ffffffffffffffc0 R09: 0000000000000000 Feb 07 21:31:49 desktop kernel: R10: ffff8ce3c5c1f900 R11: 0000000000000000 R12: ffff8ce43e6edbc8 Feb 07 21:31:49 desktop kernel: R13: ffff8ce46cdfec00 R14: ffff8ce466c19a40 R15: ffff8ce43e6edbc8 Feb 07 21:31:49 desktop kernel: FS: 00007f1f478ba600(0000) GS:ffff8ce6ee300000(0000) knlGS:0000000000000000 Feb 07 21:31:49 desktop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 07 21:31:49 desktop kernel: CR2: 00007f1f47810000 CR3: 000000015293a000 CR4: 0000000000750ef0 Feb 07 21:31:49 desktop kernel: PKRU: 55555554 Feb 07 21:31:49 desktop kernel: Call Trace: Feb 07 21:31:49 desktop kernel: <TASK> Feb 07 21:31:49 desktop kernel: ? die_addr+0x36/0x90 Feb 07 21:31:49 desktop kernel: ? exc_general_protection+0x1bd/0x410 Feb 07 21:31:49 desktop kernel: ? asm_exc_general_protection+0x26/0x30 Feb 07 21:31:49 desktop kernel: ? next_uptodate_folio+0xb7/0x240 Feb 07 21:31:49 desktop kernel: filemap_map_pages+0xa6/0x550 Feb 07 21:31:49 desktop kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Feb 07 21:31:49 desktop kernel: ? __mod_lruvec_page_state+0x99/0x130 Feb 07 21:31:49 desktop kernel: ? folio_add_file_rmap_range+0x74/0x130 Feb 07 21:31:49 desktop kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Feb 07 21:31:49 desktop kernel: do_fault+0x229/0x460 Feb 07 21:31:49 desktop kernel: __handle_mm_fault+0x77f/0xdb0 Feb 07 21:31:49 desktop kernel: handle_mm_fault+0x17f/0x360 Feb 07 21:31:49 desktop kernel: __get_user_pages+0x152/0x6d0 Feb 07 21:31:49 desktop kernel: get_dump_page+0x7a/0x110 Feb 07 21:31:49 desktop kernel: dump_user_range+0x124/0x210 Feb 07 21:31:49 desktop kernel: elf_core_dump+0xf76/0xfc0 Feb 07 21:31:49 desktop kernel: ? 0xffffffffff600000 Feb 07 21:31:49 desktop kernel: do_coredump+0x1276/0x1720 Feb 07 21:31:49 desktop kernel: get_signal+0x928/0xa30 Feb 07 21:31:49 desktop kernel: arch_do_signal_or_restart+0x2e/0x260 Feb 07 21:31:49 desktop kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Feb 07 21:31:49 desktop kernel: ? exc_general_protection+0x306/0x410 Feb 07 21:31:49 desktop kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Feb 07 21:31:49 desktop kernel: exit_to_user_mode_prepare+0x19a/0x1f0 Feb 07 21:31:49 desktop kernel: irqentry_exit_to_user_mode+0x9/0x30 Feb 07 21:31:49 desktop kernel: asm_exc_general_protection+0x26/0x30 Feb 07 21:31:49 desktop kernel: RIP: 0033:0x7f1f49840350 Feb 07 21:31:49 desktop kernel: Code: eb cc 48 89 ee 48 89 df 5b 5d 41 5c e9 a9 ac ff ff 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 8b 2e 48 89 e8 48 25 00 00 f0 ff <48> 83 38 00 74 0a 5b 5d 41 5c c3 0f 1f 44 00 00 48 89 e8 48 89 fb Feb 07 21:31:49 desktop kernel: RSP: 002b:00007fffe0b64650 EFLAGS: 00010206 Feb 07 21:31:49 desktop kernel: RAX: 01000debd6500000 RBX: 000055968cdd24e0 RCX: 00007f1f49840340 Feb 07 21:31:49 desktop kernel: RDX: 00007f1f49dc9611 RSI: 000055968d61df10 RDI: 000055968cdd24e0 Feb 07 21:31:49 desktop kernel: RBP: 01000debd65ca290 R08: 000055968cdd24e0 R09: 00000debd6500028 Feb 07 21:31:49 desktop kernel: R10: 2000000000000000 R11: 0000000000000004 R12: 000055968d71bb60 Feb 07 21:31:49 desktop kernel: R13: 000055968d61df70 R14: 00007f1f4937e230 R15: 00007f1f49dc95e0 Feb 07 21:31:49 desktop kernel: </TASK> Feb 07 21:31:49 desktop kernel: Modules linked in: nct6775 nct6775_core hwmon_vid nls_utf8 cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver fscache netfs af_packet rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user x> Feb 07 21:31:49 desktop kernel: kvm_amd snd_rawmidi btbcm snd_seq_device snd_hda_core btmtk iwlwifi mc snd_hwdep kvm irqbypass joydev wmi_bmof bluetooth snd_pcm igb cfg80211 snd_timer pcspkr dca efi_pstore ecdh_generic acpi_cpufreq > Feb 07 21:31:49 desktop kernel: [last unloaded: nct6775_core] Feb 07 21:31:49 desktop kernel: ---[ end trace 0000000000000000 ]--- Feb 07 21:31:49 desktop kernel: RIP: 0010:next_uptodate_folio+0xb7/0x240 Feb 07 21:31:49 desktop kernel: Code: c7 48 85 ff 0f 84 2a 01 00 00 48 81 ff 06 04 00 00 0f 84 9e 00 00 00 48 81 ff 02 04 00 00 74 cb 40 f6 c7 01 0f 85 8b 00 00 00 <48> 8b 07 a8 01 0f 85 80 00 00 00 8b 47 34 85 c0 74 79 8d 50 01 4c Feb 07 21:31:49 desktop kernel: RSP: 0018:ffffb32e44503710 EFLAGS: 00010246 Feb 07 21:31:49 desktop kernel: RAX: 0008000000000000 RBX: ffffb32e44503798 RCX: 0000000000000000 Feb 07 21:31:49 desktop kernel: RDX: 000000000000001d RSI: ffff8ce3defbb478 RDI: 0008000000000000 Feb 07 21:31:49 desktop kernel: RBP: 0000000000001d9f R08: ffffffffffffffc0 R09: 0000000000000000 Feb 07 21:31:49 desktop kernel: R10: ffff8ce3c5c1f900 R11: 0000000000000000 R12: ffff8ce43e6edbc8 Feb 07 21:31:49 desktop kernel: R13: ffff8ce46cdfec00 R14: ffff8ce466c19a40 R15: ffff8ce43e6edbc8 Feb 07 21:31:49 desktop kernel: FS: 00007f1f478ba600(0000) GS:ffff8ce6ee300000(0000) knlGS:0000000000000000 Feb 07 21:31:49 desktop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 07 21:31:49 desktop kernel: CR2: 00007f1f47810000 CR3: 000000015293a000 CR4: 0000000000750ef0 Feb 07 21:31:49 desktop kernel: PKRU: 55555554 Feb 07 21:31:49 desktop kernel: ------------[ cut here ]------------ Feb 07 21:31:49 desktop kernel: Voluntary context switch within RCU read-side critical section! Feb 07 21:31:49 desktop kernel: WARNING: CPU: 2 PID: 2613 at kernel/rcu/tree_plugin.h:320 rcu_note_context_switch+0x5e6/0x640 Feb 07 21:31:49 desktop kernel: Modules linked in: nct6775 nct6775_core hwmon_vid nls_utf8 cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver fscache netfs af_packet rfcomm xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user x> Feb 07 21:31:49 desktop kernel: kvm_amd snd_rawmidi btbcm snd_seq_device snd_hda_core btmtk iwlwifi mc snd_hwdep kvm irqbypass joydev wmi_bmof bluetooth snd_pcm igb cfg80211 snd_timer pcspkr dca efi_pstore ecdh_generic acpi_cpufreq > Feb 07 21:31:49 desktop kernel: [last unloaded: nct6775_core] Feb 07 21:31:49 desktop kernel: CPU: 2 PID: 2613 Comm: gnome-shell Tainted: G D 6.7.2-1-default #1 openSUSE Tumbleweed 2ebfa03c136f8452443a794052b1fbb2172d83ef Feb 07 21:31:49 desktop kernel: Hardware name: To Be Filled By O.E.M. AB350 Gaming-ITX/ac/AB350 Gaming-ITX/ac, BIOS P7.40 10/27/2022 Feb 07 21:31:49 desktop kernel: RIP: 0010:rcu_note_context_switch+0x5e6/0x640 Feb 07 21:31:49 desktop kernel: Code: 00 00 00 00 0f 85 31 fd ff ff 49 89 84 24 a0 00 00 00 e9 24 fd ff ff 48 c7 c7 98 3e 22 af c6 05 35 dd f1 01 01 e8 da 1d f4 ff <0f> 0b e9 6d fa ff ff c6 43 11 00 48 8b 73 20 ba 01 00 00 00 48 8b Feb 07 21:31:49 desktop kernel: RSP: 0018:ffffb32e44503de0 EFLAGS: 00010086 Feb 07 21:31:49 desktop kernel: RAX: 0000000000000000 RBX: ffff8ce6ee33b180 RCX: 0000000000000027 Feb 07 21:31:49 desktop kernel: RDX: ffff8ce6ee327508 RSI: 0000000000000001 RDI: ffff8ce6ee327500 Feb 07 21:31:49 desktop kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffb32e44503c80 Feb 07 21:31:49 desktop kernel: R10: 0000000000000003 R11: ffff8ce6edffffe8 R12: ffff8ce6ee33a380 Feb 07 21:31:49 desktop kernel: R13: ffff8ce41da00000 R14: 0000000000000000 R15: 0000000000000000 Feb 07 21:31:49 desktop kernel: FS: 00007f1f478ba600(0000) GS:ffff8ce6ee300000(0000) knlGS:0000000000000000 Feb 07 21:31:49 desktop kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 07 21:31:49 desktop kernel: CR2: 00007f1f47810000 CR3: 000000015293a000 CR4: 0000000000750ef0 Feb 07 21:31:49 desktop kernel: PKRU: 55555554 Feb 07 21:31:49 desktop kernel: Call Trace: Feb 07 21:31:49 desktop kernel: <TASK> Feb 07 21:31:49 desktop kernel: ? rcu_note_context_switch+0x5e6/0x640 Feb 07 21:31:49 desktop kernel: ? __warn+0x81/0x130 Feb 07 21:31:49 desktop kernel: ? rcu_note_context_switch+0x5e6/0x640 Feb 07 21:31:49 desktop kernel: ? report_bug+0x171/0x1a0 Feb 07 21:31:49 desktop kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Feb 07 21:31:49 desktop kernel: ? handle_bug+0x3c/0x80 Feb 07 21:31:49 desktop kernel: ? exc_invalid_op+0x17/0x70 Feb 07 21:31:49 desktop kernel: ? asm_exc_invalid_op+0x1a/0x20 Feb 07 21:31:49 desktop kernel: ? rcu_note_context_switch+0x5e6/0x640 Feb 07 21:31:49 desktop kernel: __schedule+0xb0/0x14b0 Feb 07 21:31:49 desktop kernel: ? get_signal+0x928/0xa30 Feb 07 21:31:49 desktop kernel: schedule+0x32/0xd0 Feb 07 21:31:49 desktop kernel: do_exit+0x107/0xa80 Feb 07 21:31:49 desktop kernel: make_task_dead+0x83/0x170 Feb 07 21:31:49 desktop kernel: rewind_stack_and_make_dead+0x17/0x20 Feb 07 21:31:49 desktop kernel: RIP: 0033:0x7f1f49840350 Feb 07 21:31:49 desktop kernel: Code: eb cc 48 89 ee 48 89 df 5b 5d 41 5c e9 a9 ac ff ff 66 0f 1f 84 00 00 00 00 00 41 54 55 53 48 8b 2e 48 89 e8 48 25 00 00 f0 ff <48> 83 38 00 74 0a 5b 5d 41 5c c3 0f 1f 44 00 00 48 89 e8 48 89 fb Feb 07 21:31:49 desktop kernel: RSP: 002b:00007fffe0b64650 EFLAGS: 00010206 Feb 07 21:31:49 desktop kernel: RAX: 01000debd6500000 RBX: 000055968cdd24e0 RCX: 00007f1f49840340 Feb 07 21:31:49 desktop kernel: RDX: 00007f1f49dc9611 RSI: 000055968d61df10 RDI: 000055968cdd24e0 Feb 07 21:31:49 desktop kernel: RBP: 01000debd65ca290 R08: 000055968cdd24e0 R09: 00000debd6500028 Feb 07 21:31:49 desktop kernel: R10: 2000000000000000 R11: 0000000000000004 R12: 000055968d71bb60 Feb 07 21:31:49 desktop kernel: R13: 000055968d61df70 R14: 00007f1f4937e230 R15: 00007f1f49dc95e0 Feb 07 21:31:49 desktop kernel: </TASK> Feb 07 21:31:49 desktop kernel: ---[ end trace 0000000000000000 ]--- Reproducible: Couldn't Reproduce Steps to Reproduce: I wasn't able to reproduce this. Sometimes it happens when system is idling, or under heavy load, watching a video or doing any day-to-day work. I cannot find a reason for the system to stall/freeze. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c18 --- Comment #18 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 872556 --> https://bugzilla.suse.com/attachment.cgi?id=872556&action=edit kernel panic with "working" kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c17 --- Comment #17 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- (In reply to Takashi Iwai from comment #15) > So, test only with the normal boot, but with extra options or removal of > options. Do I understand correctly that the very same symptom appears with > nomodeset option and the removal of "silence" and "splash=*" options on the > normal boot? That is, even though the caps lock flushing, you see no kernel > messages but the screen got frozen? Did you wait long enough (e.g. for a > minute) after that? see the movie. The boot after this test with the "working" kernel throwed something like a output on screen. Will upload it after this post. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c16 --- Comment #16 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 872554 --> https://bugzilla.suse.com/attachment.cgi?id=872554&action=edit failed boot -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] New: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 Bug ID: 1218948 Summary: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chris(a)computersalat.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello kernel support, looks like a kernel module has some problems. I am continiously getting these watchdog messages on the console: Message from syslogd@tfrs-01 at Jan 18 12:24:04 ... kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:24:34 ... kernel:[ 3410.230328][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 140s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:25:04 ... kernel:[ 3440.311352][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 168s! [kworker/0:2:156] --- snip End --- This is what I see in /var/log/messages: 2024-01-18T12:18:44.564626+00:00 tfrs-01 kernel: [ 3060.657363][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 142s! [kworker/0:2:156] 2024-01-18T12:18:44.564635+00:00 tfrs-01 kernel: [ 3060.657366][ C0] Modules linked in: usbhid af_packet iscsi_ibft iscsi_boot_sysfs dmi_sysfs msr snd_hda_codec_realtek intel_rapl_msr intel_rapl_common intel _uncore_frequency intel_uncore_frequency_common intel_pmc_core x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_generic nvme ucsi_acpi coretemp ledtrig_audio kvm_intel hp_wmi sparse_keymap iTCO_wdt nls_iso88 59_1 nls_cp437 mei_pxp mei_hdcp(N) mei_wdt typec_ucsi snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_d sp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_hda_ext_core snd_soc_core intel_pmc_bxt vfat mei_me nvme_core typec iTCO_vendor_support snd_compress platform_pr ofile kvm fat snd_pcm_dmaengine e1000e mfd_core nvme_common wmi_bmof roles irqbypass rfkill mei pcspkr snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657381][ C0] snd_timer snd soundcore i2c_i801 i2c_smbus button thermal acpi_tad(N) acpi_pad fuse configfs efi_pstore(N) ip_tables x_tables ext4 crc16 mbcache jbd2 raid1 md_mod sd_mod t10_pi sr_mod crc64_rocksoft_generic cdrom crc64_rocksoft crc64 i915 i2c_algo_bit drm_buddy drm_display_helper crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel xhci_pci syscopyarea sysfillrect xhci_pci_renesas sysimgblt fb_sys_fops cec xhci_hcd rc_core ttm ahci aesni_intel drm libahci usbcore libata crypto_simd cryptd serio_raw wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657394][ C0] Supported: No, Unsupported modules are loaded 2024-01-18T12:18:44.564637+00:00 tfrs-01 kernel: [ 3060.657395][ C0] CPU: 0 PID: 156 Comm: kworker/0:2 Tainted: G W L N 5.14.21-150500.55.39-default #1 SLE15-SP5 534d850193522c220e62d98d0494b02a0dde2443 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Hardware name: HP HP Elite Tower 600 G9 Desktop PC/8950, BIOS U01 Ver. 02.12.02 11/28/2023 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Workqueue: events output_poll_execute [drm_kms_helper] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657401][ C0] RIP: 0010:intel_dmc_load_program.part.10+0x75/0x320 [i915] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657440][ C0] Code: 48 8d bd 48 0e 00 00 49 89 ec 8b 51 04 31 c0 85 d2 74 1f 48 8b 51 08 89 c6 8b 34 b2 8b 11 8d 14 82 48 03 95 e8 07 00 00 89 32 <83> c0 01 3b 41 04 72 e1 48 81 c1 c0 00 00 00 48 39 f9 75 cc 65 ff 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657441][ C0] RSP: 0018:ffffa498c065fb08 EFLAGS: 00000286 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657442][ C0] RAX: 0000000000000927 RBX: 0000000000000001 RCX: ffff952ed20a0a88 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RDX: ffffa498c168249c RSI: 0000000000000010 RDI: ffff952ed20a0e48 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RBP: ffff952ed20a0000 R08: 0000000000000000 R09: 0000000000000001 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R10: ffffa498c065f9d0 R11: ffffa498c065f8f8 R12: ffff952ed20a0000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R13: 0000000000000006 R14: 0000000000000002 R15: ffffffffc0d967a0 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] FS: 0000000000000000(0000) GS:ffff953dff400000(0000) knlGS:0000000000000000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] CR2: 00007ffd1a37bee6 CR3: 0000000456210000 CR4: 0000000000750ef0 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] PKRU: 55555554 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] Call Trace: 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657447][ C0] <TASK> 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657447][ C0] icl_display_core_init+0x2e3/0x6d0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657485][ C0] intel_display_power_resume+0x6b/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657522][ C0] intel_runtime_resume+0x7f/0x1e0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657543][ C0] pci_pm_runtime_resume+0x76/0xb0 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657545][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657546][ C0] __rpm_callback+0x43/0x120 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657547][ C0] rpm_callback+0x5d/0x70 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657548][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657549][ C0] rpm_resume+0x4c0/0x770 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657550][ C0] ? pci_bus_read_config_dword+0x41/0x70 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657551][ C0] __pm_runtime_resume+0x47/0x80 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657552][ C0] __intel_runtime_pm_get+0x1e/0x90 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657577][ C0] intel_display_power_get+0x24/0x60 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657614][ C0] intel_digital_port_connected+0x3a/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657645][ C0] intel_dp_detect+0x2c8/0x660 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657675][ C0] ? newidle_balance+0x2f0/0x440 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657676][ C0] drm_helper_probe_detect_ctx+0x6a/0xf0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657682][ C0] output_poll_execute+0x116/0x1f0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657686][ C0] process_one_work+0x264/0x440 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657688][ C0] worker_thread+0x2d/0x3c0 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657689][ C0] ? process_one_work+0x440/0x440 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657690][ C0] kthread+0x154/0x180 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657691][ C0] ? set_kthread_struct+0x50/0x50 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657692][ C0] ret_from_fork+0x1f/0x30 2024-01-18T12:18:44.564652+00:00 tfrs-01 kernel: [ 3060.657694][ C0] </TASK> --- snip END --- Is there any chance to get this fixed somehow ? Thank you Kind Regards Christian -- You are receiving this mail because: You are the assignee for the bug.

1 30

[Bug 1210639] Kernel 6.2+ fails to boot on Intel Atom x5-Z8300
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1210639 https://bugzilla.suse.com/show_bug.cgi?id=1210639#c18 --- Comment #18 from Vojtech Zeisek <Vojtech.Zeisek(a)opensuse.org> --- > Didn't you see those messages about the firmware load errors? Nothing. As soon as I submit the modprobe command, notebook freezes completely and I can do nothing and see nothing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c14 --- Comment #14 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Is there something i can do to find the cullprit? Note: a good kernel will sometimes also fail. A retry will usually fix this. I also have some freezes (but not that often). Usually the sound will replay the last second at that point. So, until now, i blamed this on bad kernels. But not sure. This kernel panic is consistent however. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c47 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kernel-bugs@opens | |use.org) | --- Comment #47 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Then could you try the 6.7.x kernel in OBS Kernel:stable:Backport repo, and see whether it works as is without options? http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ Or try the SLE15-SP6 kernel, too http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1218682] EFI aarch64 boot failure on honeycomb lx2
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218682 https://bugzilla.suse.com/show_bug.cgi?id=1218682#c5 --- Comment #5 from Stanimir Varbanov <stanimir.varbanov(a)suse.com> --- Guillaume, is it visible from the boot log which driver is provoking those iommu faults? Could you attach boot log, please. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210639] Kernel 6.2+ fails to boot on Intel Atom x5-Z8300
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1210639 https://bugzilla.suse.com/show_bug.cgi?id=1210639#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Vojtech Zeisek from comment #16) > Created attachment 872534 [details] > log with failed modprobe > > I used "sudo journalctl -b-1" to obtain the log. Failed modprobe I tried ca. > 11:12 and hard rebooted ca. 10 min. later. HTH Hm, it doesn't show anything about atomisp unlike the previous report. Didn't you see those messages about the firmware load errors? -- You are receiving this mail because: You are the assignee for the bug.

1 0