April 2025 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 12 May '25

12 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1241260] New: Unified kernel not available for kernel-vanilla
by bugzilla_noreply＠suse.com 06 May '25

06 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241260 Bug ID: 1241260 Summary: Unified kernel not available for kernel-vanilla Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)sufrin.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In order to have secure boot signature verification of the entire boot chain (in kernel-default booting, initrd is not signed, so it is not verified for having been maliciously modified), I have moved to using the unified kernel (where the entire boot process is in a signed efi file which is verified), as described in the latter half of https://en.opensuse.org/SDB:Static_Initrd_and_Unified_Kernel_Image However, despite the section being titled “Install the Unified Kernel Image (uki-<kernel_flavor>)”, the only kernel flavor supported is kernel-default. My problem is that I use kernel-vanilla and there is no uki-vanilla package, only uki-default. In order to support the vanilla kernel, the process that currently generates uki-default should be modified to also generate uki-vanilla, based off of kernel-vanilla. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1241986] New: r8169 breaks after upgrading to 6.14.3-1
by bugzilla_noreply＠suse.com 05 May '25

05 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1241986 Bug ID: 1241986 Summary: r8169 breaks after upgrading to 6.14.3-1 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: enzooocf(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently im on 6.14.3-1-default where it works fine. after upgrading to kernel-default-6.14.4-1.1 it no longer works. I cant get it up and running again even after several reboots and reloading the module. hw ino: ``` sata@t14:~$ lspci -nnk | grep -iA3 ether pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0e) Subsystem: Lenovo Device [17aa:50ee] Kernel driver in use: r8169 Kernel modules: r8169 ``` -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1242075] New: libgallium segmentation fault / nouveau nvkm_dp_train_sense kernel trace
by bugzilla_noreply＠suse.com 02 May '25

02 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1242075 Bug ID: 1242075 Summary: libgallium segmentation fault / nouveau nvkm_dp_train_sense kernel trace Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 882257 --> https://bugzilla.suse.com/attachment.cgi?id=882257&action=edit journalctl -S '1h ago' --no-pager Hello, under Wayland / Sway on a Lenovo ThinkPad P70, sometimes the system freezes forever, some other times it freezes briefly and then "recovers" by crashing Sway. The laptop is equipped with this GPU: ``` $ lspci|grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M600M] (rev a2) ``` The kernel log reveals this together with the freezes: ``` [Wed Apr 30 16:57:00 2025] [ T8099] nouveau 0000:01:00.0: sway[8099]: nv50cal_space: -16 [Wed Apr 30 16:57:01 2025] [ T8099] nouveau 0000:01:00.0: sway[8099]: nv50cal_space: -16 [Wed Apr 30 16:57:01 2025] [ C5] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] [Wed Apr 30 16:57:01 2025] [ C5] nouveau 0000:01:00.0: fifo:000000:0003:[sway[8099]] rc scheduled [Wed Apr 30 16:57:01 2025] [ C5] nouveau 0000:01:00.0: fifo:000000: rc scheduled [Wed Apr 30 16:57:01 2025] [T2780111] nouveau 0000:01:00.0: fifo:000000:0003:0003:[sway[8099]] errored - disabling channel [Wed Apr 30 16:57:01 2025] [T2780111] nouveau 0000:01:00.0: sway[8099]: channel 3 killed! [Wed Apr 30 16:57:01 2025] [ T8099] sway[8099]: segfault at 560800000000 ip 00007f1254ae8f6c sp 00007fff5e650c00 error 4 in libgallium-25.0.3.so[ae8f6c,7f12540c7000+16c5000] likely on CPU 4 (core 0, socket 0) [Wed Apr 30 16:57:01 2025] [ T8099] Code: 10 40 01 00 0f 8e c4 00 00 00 41 8b 45 00 48 8b 3c 24 be 02 00 00 00 4c 8d 05 52 99 cd 00 49 8b 55 08 45 8b 4d 00 48 8d 04 80 <4c> 8b 3c c7 49 8b 45 10 48 8b 3d 7d 8a cf 01 49 8b 4f 28 48 89 c5 [Wed Apr 30 16:57:01 2025] [ T2615] ------------[ cut here ]------------ [Wed Apr 30 16:57:01 2025] [ T2615] WARNING: CPU: 1 PID: 2615 at drivers/gpu/drm/nouveau/include/nvkm/subdev/i2c.h:164 nvkm_dp_train_sense+0xd0/0x220 [nouveau] [Wed Apr 30 16:57:01 2025] [ T2615] Modules linked in: xfs rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc netfs wireguard libchacha20poly1305 chacha_x86_64 poly1305_x86_64 curve25519_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel tun cfg80211 rfcomm af_packet iscsi_ibft iscsi_boot_sysfs uhid cmac algif_hash algif_skcipher af_alg bnep iptable_filter binfmt_misc uvcvideo videobuf2_vmalloc uvc videobuf2_memops snd_usb_audio videobuf2_v4l2 videobuf2_common snd_usbmidi_lib snd_ump videodev snd_rawmidi snd_seq_device mc btusb btrtl btintel btbcm btmtk bluetooth nls_iso8859_1 intel_rapl_msr nls_cp437 snd_soc_avs intel_rapl_common vfat snd_soc_hda_codec intel_pmc_core_pltdrv fat snd_hda_ext_core intel_pmc_core snd_hda_codec_realtek snd_soc_core pmt_telemetry snd_hda_codec_generic pmt_class snd_compress snd_hda_scodec_component snd_hda_codec_hdmi intel_vsec snd_pcm_dmaengine intel_tcc_cooling snd_hda_intel x86_pkg_temp_thermal intel_powerclamp snd_ctl_led snd_intel_dspcfg coretemp snd_intel_sdw_acpi [Wed Apr 30 16:57:01 2025] [ T2615] snd_hda_codec snd_hda_core kvm_intel iTCO_wdt thinkpad_acpi snd_hwdep intel_pmc_bxt mei_pxp mei_hdcp mei_wdt iTCO_vendor_support ee1004 platform_profile snd_pcm think_lmi sparse_keymap kvm i2c_i801 mei_me pcspkr snd_timer rfkill i2c_smbus firmware_attributes_class efi_pstore intel_wmi_thunderbolt wmi_bmof e1000e i2c_mux mei snd intel_pch_thermal thermal soundcore ac joydev tiny_power_button configfs fuse loop dm_crypt essiv authenc trusted asn1_encoder tee hid_generic usbhid uas usb_storage nouveau ahci drm_ttm_helper libahci ttm polyval_clmulni polyval_generic gpu_sched libata ghash_clmulni_intel i2c_algo_bit sd_mod sha512_ssse3 drm_gpuvm scsi_dh_emc xhci_pci sha256_ssse3 rtsx_pci_sdmmc drm_exec scsi_dh_rdac sha1_ssse3 mxm_wmi mmc_core xhci_hcd scsi_dh_alua sg drm_display_helper aesni_intel cec scsi_mod crypto_simd rtsx_pci usbcore scsi_common cryptd rc_core video battery wmi button serio_raw btrfs blake2b_generic xor raid6_pq dm_mod br_netfilter bridge stp llc nf_tables nbd msr i2c_dev ip6_tables [Wed Apr 30 16:57:01 2025] [ T2615] nfnetlink efivarfs dmi_sysfs ip_tables x_tables [Wed Apr 30 16:57:01 2025] [ T2615] CPU: 1 UID: 0 PID: 2615 Comm: systemd-logind Not tainted 6.14.2-1-default #1 openSUSE Tumbleweed 968795ef2b1407352128b466fe887416c33af6fa [Wed Apr 30 16:57:01 2025] [ T2615] Hardware name: LENOVO 20ESS2JG00/20ESS2JG00, BIOS N1DET95W (2.21 ) 12/13/2017 [Wed Apr 30 16:57:01 2025] [ T2615] RIP: 0010:nvkm_dp_train_sense+0xd0/0x220 [nouveau] [Wed Apr 30 16:57:01 2025] [ T2615] Code: 49 89 c0 be 01 00 00 00 4c 89 f7 48 89 04 24 e8 26 14 fd ff 41 89 c7 85 c0 0f 85 9d 00 00 00 80 7c 24 0f 03 0f 84 db 00 00 00 <0f> 0b 4c 89 f7 e8 46 11 fd ff 8b 43 0c bd 06 02 00 00 85 c0 74 0c [Wed Apr 30 16:57:01 2025] [ T2615] RSP: 0018:ffffb9d3c061f298 EFLAGS: 00010293 [Wed Apr 30 16:57:01 2025] [ T2615] RAX: 0000000000000000 RBX: ffffb9d3c061f2f0 RCX: ffffb9d3c061f2a7 [Wed Apr 30 16:57:01 2025] [ T2615] RDX: 0000000000000000 RSI: ffffb9d3c300e534 RDI: 0000000001009002 [Wed Apr 30 16:57:01 2025] [ T2615] RBP: 0000000000000202 R08: 0000000000000000 R09: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] R10: 00000000000042e5 R11: 0000000000000000 R12: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] R13: ffff9e14444d3c00 R14: ffff9e144c138800 R15: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] FS: 00007f8a258279c0(0000) GS:ffff9e1bb3a80000(0000) knlGS:0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Wed Apr 30 16:57:01 2025] [ T2615] CR2: 0000559f10a29c28 CR3: 0000000106100005 CR4: 00000000003726f0 [Wed Apr 30 16:57:01 2025] [ T2615] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [Wed Apr 30 16:57:01 2025] [ T2615] Call Trace: [Wed Apr 30 16:57:01 2025] [ T2615] <TASK> [Wed Apr 30 16:57:01 2025] [ T2615] nvkm_dp_train_link+0x1ec/0x5e0 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nvkm_dp_train+0x101/0x250 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] ? nvkm_dp_aux_xfer+0x5f/0x80 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nvkm_uoutp_mthd+0x11c/0xba0 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nvkm_ioctl+0xa3/0x140 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nvif_object_mthd+0xc1/0x1a0 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] ? nvif_outp_dp_aux_xfer+0xb8/0x110 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nvif_outp_dp_train+0x70/0x120 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nouveau_dp_train_link+0xc2/0x2f0 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] ? drm_dp_dpcd_write+0x69/0xe0 [drm_display_helper a7d8965970cab1f0bbda1303238aa4fcb5954639] [Wed Apr 30 16:57:01 2025] [ T2615] nouveau_dp_train+0xec/0x190 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] nv50_sor_atomic_enable+0x29b/0x890 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] ? __wait_for_common+0x177/0x1c0 [Wed Apr 30 16:57:01 2025] [ T2615] ? __pfx_schedule_timeout+0x10/0x10 [Wed Apr 30 16:57:01 2025] [ T2615] ? drm_calc_timestamping_constants+0x106/0x170 [Wed Apr 30 16:57:01 2025] [ T2615] nv50_disp_atomic_commit_tail+0x242/0x790 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] ? drm_crtc_get_last_vbltimestamp+0x53/0x90 [Wed Apr 30 16:57:01 2025] [ T2615] nv50_disp_atomic_commit+0x188/0x1b0 [nouveau 96c5202a3e54756824f08028c4d841aab269c56b] [Wed Apr 30 16:57:01 2025] [ T2615] drm_atomic_commit+0xaf/0xe0 [Wed Apr 30 16:57:01 2025] [ T2615] ? __pfx___drm_printfn_info+0x10/0x10 [Wed Apr 30 16:57:01 2025] [ T2615] drm_client_modeset_commit_atomic+0x1e2/0x220 [Wed Apr 30 16:57:01 2025] [ T2615] drm_client_modeset_commit_locked+0x5a/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0 [Wed Apr 30 16:57:01 2025] [ T2615] drm_fb_helper_set_par+0x30/0x40 [Wed Apr 30 16:57:01 2025] [ T2615] fb_set_var+0x22f/0x410 [Wed Apr 30 16:57:01 2025] [ T2615] ? pollwake+0x78/0xa0 [Wed Apr 30 16:57:01 2025] [ T2615] ? __pfx_default_wake_function+0x10/0x10 [Wed Apr 30 16:57:01 2025] [ T2615] ? __wake_up_common+0x75/0xa0 [Wed Apr 30 16:57:01 2025] [ T2615] fbcon_blank+0x271/0x330 [Wed Apr 30 16:57:01 2025] [ T2615] do_unblank_screen+0xad/0x150 [Wed Apr 30 16:57:01 2025] [ T2615] vt_ioctl+0x568/0x1200 [Wed Apr 30 16:57:01 2025] [ T2615] tty_ioctl+0xe2/0x880 [Wed Apr 30 16:57:01 2025] [ T2615] ? __seccomp_filter+0x2f5/0x510 [Wed Apr 30 16:57:01 2025] [ T2615] __x64_sys_ioctl+0x94/0xc0 [Wed Apr 30 16:57:01 2025] [ T2615] do_syscall_64+0x82/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] ? syscall_exit_to_user_mode+0x37/0x1d0 [Wed Apr 30 16:57:01 2025] [ T2615] ? do_syscall_64+0x8e/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] ? switch_fpu_return+0x4e/0xd0 [Wed Apr 30 16:57:01 2025] [ T2615] ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90 [Wed Apr 30 16:57:01 2025] [ T2615] ? syscall_exit_to_user_mode+0x37/0x1d0 [Wed Apr 30 16:57:01 2025] [ T2615] ? do_syscall_64+0x8e/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] ? syscall_exit_to_user_mode+0x37/0x1d0 [Wed Apr 30 16:57:01 2025] [ T2615] ? do_syscall_64+0x8e/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] ? __sys_sendmsg+0x68/0xc0 [Wed Apr 30 16:57:01 2025] [ T2615] ? syscall_exit_to_user_mode+0x37/0x1d0 [Wed Apr 30 16:57:01 2025] [ T2615] ? do_syscall_64+0x8e/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] ? do_syscall_64+0x8e/0x160 [Wed Apr 30 16:57:01 2025] [ T2615] entry_SYSCALL_64_after_hwframe+0x76/0x7e [Wed Apr 30 16:57:01 2025] [ T2615] RIP: 0033:0x7f8a2571916f [Wed Apr 30 16:57:01 2025] [ T2615] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [Wed Apr 30 16:57:01 2025] [ T2615] RSP: 002b:00007fffc909cf80 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [Wed Apr 30 16:57:01 2025] [ T2615] RAX: ffffffffffffffda RBX: 0000000000000018 RCX: 00007f8a2571916f [Wed Apr 30 16:57:01 2025] [ T2615] RDX: 0000000000000000 RSI: 0000000000004b3a RDI: 0000000000000018 [Wed Apr 30 16:57:01 2025] [ T2615] RBP: 000055d835d1f070 R08: 00007fffc909cf70 R09: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffc909d0b0 [Wed Apr 30 16:57:01 2025] [ T2615] R13: 0000000000000000 R14: 000055d835d1f070 R15: 0000000000000000 [Wed Apr 30 16:57:01 2025] [ T2615] </TASK> [Wed Apr 30 16:57:01 2025] [ T2615] ---[ end trace 0000000000000000 ]--- ``` The Sway core dump: ``` ~> coredumpctl info 8099 PID: 8099 (sway) UID: 1000 (georg) GID: 1000 (georg) Signal: 11 (SEGV) Timestamp: Wed 2025-04-30 16:57:02 CEST (24min ago) Command Line: sway Executable: /usr/bin/sway Control Group: /user.slice/user-1000.slice/session-12.scope Unit: session-12.scope Slice: user-1000.slice Session: 12 Owner UID: 1000 (georg) Boot ID: 657ccba2a42145efab88cb15ad1cd281 Machine ID: ccdf4e1ff6d54acaa27c1037f2bd991c Hostname: bittersuse.lysergic.dev Storage: /var/lib/systemd/coredump/core.sway.1000.657ccba2a42145efab88cb15ad1cd281.8099.1746025022000000.zst (present) Size on Disk: 3.4M Message: Process 8099 (sway) of user 1000 dumped core. Module /usr/lib64/libgallium-25.0.3.so (deleted) without build-id. Module /usr/lib64/libgallium-25.0.3.so (deleted) Stack trace of thread 8099: #0 0x00007f1254ae8f6c n/a (/usr/lib64/libgallium-25.0.3.so (deleted) + 0xae8f6c) ELF object binary architecture: AMD x86-64 ``` I attached the journal output (which contains the kernel log) starting from a bit before the last event happened. Unsure if this is related to https://bugzilla.opensuse.org/show_bug.cgi?id=1241478 (same hardware and also related to libgallium/nouveau, but with X instead of Wayland and no kernel trace there). Any hints? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1242077] New: "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default
by bugzilla_noreply＠suse.com 01 May '25

01 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1242077 Bug ID: 1242077 Summary: "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: e.kleinmentink(a)zonnet.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 882259 --> https://bugzilla.suse.com/attachment.cgi?id=882259&action=edit screenshot crash Summary: Recent kernel versions cause a kernel panic on boot. Description: After several recent kernel updates, my system fails to boot and results in a kernel panic with the message: "Kernel panic - not syncing: VFS: Unable to mount root fs" The only kernel that still works reliably is 6.13.8-1-default. I have to manually select this version each time to boot successfully. Please see the attached screenshot for the on-screen panic message, and the attached dmesg.txt for the dmesg output from a successful boot using 6.13.8-1-default. Note: I reported a kernel issue about a year ago, which turned out to be related to libinput (see: https://bugzilla.opensuse.org/show_bug.cgi?id=1219522) This appears to be unrelated. Hardware: Lenovo ThinkPad T580 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1242077] "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default
by bugzilla_noreply＠suse.com 30 Apr '25

30 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1242077 https://bugzilla.suse.com/show_bug.cgi?id=1242077#c12 --- Comment #12 from Michal Suchanek <msuchanek(a)suse.com> --- ZFS cannot be part of the kernel because of licensing conflict. Then it has to keep up with changes in the kernel independently, and it sometimes does not. That results in this problem, repeatedly. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1242077] "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default
by bugzilla_noreply＠suse.com 30 Apr '25

30 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1242077 https://bugzilla.suse.com/show_bug.cgi?id=1242077#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Then complain whereever you got that zfs module. Due to licensing conflict it cannot be included in the distribution so I am fairly sure it's not form openSUSE. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1242077] "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default
by bugzilla_noreply＠suse.com 30 Apr '25

30 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1242077 https://bugzilla.suse.com/show_bug.cgi?id=1242077#c5 --- Comment #5 from Michal Suchanek <msuchanek(a)suse.com> --- Yes, no ramdisk is created since then: initrd-6.12.22-1-longterm initrd-6.12.24-1-longterm initrd-6.12.25-1-longterm initrd-6.13.8-1-default what does dracut -f /boot/initrd-6.14.4-1-default 6.14.4-1-default say? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1242077] "Kernel panic - not syncing: VFS" after kernel 6.13.8-1-default
by bugzilla_noreply＠suse.com 30 Apr '25

30 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1242077 https://bugzilla.suse.com/show_bug.cgi?id=1242077#c2 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com --- Comment #2 from Michal Suchanek <msuchanek(a)suse.com> --- Fails to start init. Probably missing or broken ramdisk. ramdisks should still be in /boot on TW, ls /boot should list them. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1241986] r8169 breaks after upgrading to 6.14.3-1
by bugzilla_noreply＠suse.com 30 Apr '25

30 Apr '25

https://bugzilla.suse.com/show_bug.cgi?id=1241986 https://bugzilla.suse.com/show_bug.cgi?id=1241986#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(enzooocf(a)gmail.co | |m) CC| |enzooocf(a)gmail.com, | |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- When you boot 6.13.x kernel, it works stably? Also, does the problem persist with 6.15-rc kernel found in OBS Kernel:HEAD repo? -- You are receiving this mail because: You are the assignee for the bug.

1 0