- openSUSE Kernel Bugs

[Bug 1220541] New: kexec does a full reboot with kernel 6.7.6-1.1
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220541 Bug ID: 1220541 Summary: kexec does a full reboot with kernel 6.7.6-1.1 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: me(a)pavinjoseph.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tested on identical systems with kexec-tools 2.0.27-3.2 (on both) and kernel 6.7.5-1.1 (on working system) and 6.7.6-1.1 (on faulty system). Faulty system (fully updated as of Feb 28 2024) is on Tumbleweed release 20240226. Working system is on release 20240222. Issue reproduced on working system by doing zypper ref and zypper in kernel-default to upgrade just the kernel to the latest version. Issue happens after the next cold boot and persists. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1222345] Laptop wakes from suspend once the user closes the lid
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c9 --- Comment #9 from Tristan Miller <psychonaut(a)nothingisreal.com> --- I tried toggling the lid wakeup as you suggested. No matter whether it shows as enabled or disabled in /proc/acpi/wakeup, and no matter whether I put the laptop to sleep using the KDE Plasma GUI or with "echo mem > /sys/power/state", the laptop wakes up once I close the lid. I don't see any settings in the BIOS menu that seem relevant. Is there anything else I can try? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222816] New: BTRFS_IOC_SNAP_CREATE_V2 return error but did some of the work
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222816 Bug ID: 1222816 Summary: BTRFS_IOC_SNAP_CREATE_V2 return error but did some of the work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While working on bug #1222674 I noticed that the BTRFS_IOC_SNAP_CREATE_V2 ioctl when passed a non existing qgroup does create the snapshot but also reports an error (ENOENT). Is that desired behavior? Can I really on that it (ioctl does everything except adding to the qgroup)? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1222818] New: Kernel Configuration Breakage (regulators) in config/arm64/default for MediaTek boards when merge from master to stable
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222818 Bug ID: 1222818 Summary: Kernel Configuration Breakage (regulators) in config/arm64/default for MediaTek boards when merge from master to stable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: macpaul.lin(a)mediatek.com QA Contact: qa-bugs(a)suse.de CC: 95kreaninw95(a)gmail.com, chester.lin(a)suse.com, dmueller(a)suse.com, forgotten_0079121656(a)user.net, ivan.ivanov(a)suse.com, m4ng4n(a)gmx.de, macpaul.lin(a)mediatek.com, mgorman(a)suse.com, mhocko(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com, vbabka(a)suse.com Depends on: 1215335 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1215335 +++ Reference: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035591 ## Description A regression has been identified in the kernel configuration file `config/arm64/default` that appears to have been introduced during a merge from the master branch to the stable branch. The issue affected genio-mt8395 boards and removed settings of enabling regulators by this commit. [b197b3604a7b1542574ed75ee9e5f708eaa9772c] Update config files: enable arm64 regulator modules for mediatek boards (bsc#1215335) ## Affected Commits - **Bad Commit**: [a26e308341f11d0300a8bef13e97c9d213c6722a] Merge branch 'master' into stable - **Last Known Good Commit**: [18231664d40aa6b0efdc96714d3d1de0519bb460] Merge remote-tracking branch 'origin/users/vkarasulli/stable/for-next' into stable ## Removed configurations which leads board boot up fail. git checkout a26e308341f11d0300a8bef13e97c9d213c6722a git diff HEAD~1 | grep MT63 -CONFIG_PINCTRL_MT6397=y -# CONFIG_POWER_RESET_MT6323 is not set CONFIG_MFD_MT6360=m # CONFIG_MFD_MT6370 is not set -CONFIG_MFD_MT6397=m +# CONFIG_MFD_MT6397 is not set # CONFIG_REGULATOR_MT6311 is not set CONFIG_REGULATOR_MT6315=m -# CONFIG_REGULATOR_MT6323 is not set -# CONFIG_REGULATOR_MT6331 is not set -# CONFIG_REGULATOR_MT6332 is not set -CONFIG_REGULATOR_MT6357=m -CONFIG_REGULATOR_MT6358=m -CONFIG_REGULATOR_MT6359=m CONFIG_REGULATOR_MT6360=m CONFIG_REGULATOR_MT6380=m -CONFIG_REGULATOR_MT6397=m CONFIG_SND_SOC_MT6797_MT6351=m CONFIG_SND_SOC_MT8183_MT6358_TS3A227E_MAX98357A=m -# CONFIG_LEDS_MT6323 is not set -CONFIG_RTC_DRV_MT6397=m ## Expected Behavior and suggested fix Please help to add these settings in both master and stable branch in config/arm64/default CONFIG_PINCTRL_MT6397=y CONFIG_MFD_MT6397=m CONFIG_REGULATOR_MT6357=m CONFIG_REGULATOR_MT6358=m CONFIG_REGULATOR_MT6359=m CONFIG_REGULATOR_MT6397=m CONFIG_RTC_DRV_MT6397=m ## Additional Information Boot fail log using openSuse openSUSE-Tumbleweed-NET-aarch64-20240410.iso (This issue has been reported more earlier.) Error log: /var/log/boot.msg:509:<6>[ 25.667557][ T10] platform 11290000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:510:<6>[ 25.669208][ T10] platform 112a0000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:511:<6>[ 25.670850][ T10] platform 11230000.mmc: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vufs /var/log/boot.msg:512:<6>[ 25.672507][ T10] platform 112b0000.usb: deferred probe pending: platform: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vusb /var/log/boot.msg:513:<6>[ 25.674149][ T10] spi spi0.0: deferred probe pending: spi: wait for supplier /soc/pwrap@10024000/pmic/regulators/ldo_vcn33_2_bt Thanks! Macpaul Lin -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222674] BTRFS Snapshots failing since kernel 6.8.4rc1, still working on 6.8.2
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222674 https://bugzilla.suse.com/show_bug.cgi?id=1222674#c11 pallas wept <pallaswept(a)proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FEATURE Status|NEW |RESOLVED --- Comment #11 from pallas wept <pallaswept(a)proton.me> --- (In reply to Ingo Göppert from comment #9) > The workaround works for me ;-) Great news! I feel like I should resolve+close this now, because the change to the kernel which triggered this, is intentional, so any change would be made against snapper, and I already have that issue on snapper's github, so their team could track this from there. If you would like me to re-open this just let me know :) (although I imagine you have the power to re-open it yourself?) Thanks everyone! I got so accustomed to the added layer of security that snapper provides, that I felt rather uncomfortable without it... It's nice to have my snapshots back :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222674] New: BTRFS Snapshots failing since kernel 6.8.4rc1, still working on 6.8.2
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222674 Bug ID: 1222674 Summary: BTRFS Snapshots failing since kernel 6.8.4rc1, still working on 6.8.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just noticed I don't have a single snapshot from the last 3 days (they normally are taken hourly). Looking at "what changed?" I notice that's when I updated my kernel, and it's the only change I can see that would be relevant. I rebooted, and selected the old kernel from GRUB, and snapshots work fine. Reboot into 6.8.4 again, can't snapshot. More detail: Manual snapshots will work, but not if given a cleanup schedule, ie: sudo snapper create #works sudo snapper create -c timeline #fails Accordingly, it's unsurprising that scheduled snapshots with snapper fail with the same error as the manual snapshot, since it creates snapshots with the cleanup set. The logs show the following errors: >2024-04-11 19:28:52 MIL libsnapper(12199) Snapshot.cc(read):344 - found 95 snapshots >2024-04-11 19:28:52 WAR libsnapper(12199) FileUtils.cc(SDir):88 - THROW: open failed path://.snapshots/9878 errno:2 (No such file or directory) >2024-04-11 19:28:52 WAR libsnapper(12199) Btrfs.cc(checkSnapshot):490 - CAUGHT: open failed path://.snapshots/9878 errno:2 (No such file or directory) >2024-04-11 19:28:52 ERR libsnapper(12199) Btrfs.cc(createSnapshot):328 - create snapshot failed, btrfs_util_create_snapshot_fd2() failed, errno:2 (No such file or directory) >2024-04-11 19:28:52 WAR libsnapper(12199) Btrfs.cc(createSnapshot):329 - THROW: create snapshot failed >2024-04-11 19:28:52 WAR libsnapper(12199) Snapshot.cc(createHelper):780 - CAUGHT: create snapshot failed >2024-04-11 19:28:52 WAR libsnapper(12199) Snapshot.cc(createHelper):785 - RETHROW: create snapshot failed >2024-04-11 19:28:52 WAR libsnapper(12199) Client.cc(dispatch):1983 - CAUGHT: create snapshot failed In this example, the last snapshot already existing was 9877, and it would have been creating 9878, but the directory does not exist before or after the command. If I create a manual snapshot with no cleanup set, or reboot into kernel 6.8.2, the snapshot will work, and become 9878. The failure of the snapshot causes the snapper-timeline.service to exit, also. It does not provide any information in its logs. Please let me know if there's anything I can do to help. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 14 Apr '24

14 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c48 --- Comment #48 from Andreas <opendreas(a)gmail.com> --- (In reply to Paolo De Pasquale from comment #47) > (In reply to Andreas from comment #46) > > > > It would probably be nice to write about this on GitLab and attach the log. > > https://gitlab.freedesktop.org/drm/intel/-/issues/4458#note_2336439 > > Unfortunately I don't think it would help, given that Intel is not offering > support on systems having the nvidia module loaded. > > Nonetheless it's worth to say that, having updated TW to 6.8.5-1-default > kernel, the wine freezes seems to be gone for me ( while I can still see > some LSPCON errors in the dmesg). There is already a patch to fix the bugs, but it was not included in the upstream because the reviews about freezing are confusing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 14 Apr '24

14 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c47 --- Comment #47 from Paolo De Pasquale <paolo.depasquale(a)suse.com> --- (In reply to Andreas from comment #46) > > It would probably be nice to write about this on GitLab and attach the log. > https://gitlab.freedesktop.org/drm/intel/-/issues/4458#note_2336439 Unfortunately I don't think it would help, given that Intel is not offering support on systems having the nvidia module loaded. Nonetheless it's worth to say that, having updated TW to 6.8.5-1-default kernel, the wine freezes seems to be gone for me ( while I can still see some LSPCON errors in the dmesg). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222748] New: RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] and RIP: 0033:0x7fac1690f3df - virtualbox host
by bugzilla_noreply＠suse.com 13 Apr '24

13 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222748 Bug ID: 1222748 Summary: RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] and RIP: 0033:0x7fac1690f3df - virtualbox host 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: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi OpenSUSE Kernel Team, I notice this today when using default kernel and virtualbox. ``` [ 1534.673651] ------------[ cut here ]------------ [ 1534.673660] WARNING: CPU: 10 PID: 2942 at /home/abuild/rpmbuild/BUILD/VirtualBox-7.0.14/modules_build_dir/default/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:564 rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] [ 1534.673716] Modules linked in: vtsspp(OE) sep5(OE) socperf3(OE) pax(OE) ccm snd_seq_dummy rfcomm snd_hrtimer snd_seq xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter bridge stp llc overlay cmac algif_hash algif_skcipher af_alg nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct af_packet nft_chain_nat nf_tables ebtable_nat ebtable_broute vboxnetadp(O) vboxnetflt(O) ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter vboxdrv(O) qrtr bnep binfmt_misc ext4 mbcache jbd2 btusb btrtl btintel btbcm btmtk bluetooth snd_usb_audio snd_usbmidi_lib snd_ump snd_rawmidi snd_seq_device ecdh_generic mc nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(POE) snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp [ 1534.673798] snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic snd_soc_core mt7921e intel_rapl_msr nls_iso8859_1 intel_rapl_common snd_hda_codec_hdmi snd_compress mt7921_common nls_cp437 snd_pcm_dmaengine edac_mce_amd snd_pci_ps mt792x_lib snd_rpl_pci_acp6x mt76_connac_lib snd_hda_intel snd_acp_pci vfat snd_acp_legacy_common snd_intel_dspcfg mt76 kvm_amd snd_pci_acp6x snd_intel_sdw_acpi fat snd_pci_acp5x snd_hda_codec mac80211 snd_hda_core kvm snd_hwdep snd_rn_pci_acp3x snd_pcm snd_acp_config libarc4 nvidia(POE) snd_timer irqbypass asus_nb_wmi wmi_bmof snd_soc_acpi pcspkr snd cfg80211 snd_pci_acp3x k10temp i2c_piix4 soundcore thermal ac joydev amd_pmc asus_wireless tiny_power_button nvme_fabrics fuse loop dm_mod efi_pstore configfs nfnetlink efivarfs dmi_sysfs ip_tables x_tables hid_asus asus_wmi ledtrig_audio sparse_keymap platform_profile rfkill usbhid amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul drm_exec crc32_pclmul gpu_sched polyval_clmulni [ 1534.673887] polyval_generic drm_suballoc_helper xhci_pci gf128mul xhci_pci_renesas drm_buddy nvme ghash_clmulni_intel drm_display_helper xhci_hcd hid_multitouch sha512_ssse3 nvme_core ucsi_acpi sha256_ssse3 hid_generic cec typec_ucsi video nvme_auth sha1_ssse3 aesni_intel usbcore crypto_simd roles cryptd ccp rc_core sp5100_tco typec t10_pi battery button wmi i2c_hid_acpi i2c_hid btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq msr [ 1534.673932] CPU: 10 PID: 2942 Comm: EMT-0 Tainted: P OE 6.8.4-rc1-1-default #1 openSUSE Tumbleweed 7c8542a930b9a705533f9dd2c381f1ab0c0f923c [ 1534.673937] Hardware name: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401QM_GA401QM/GA401QM, BIOS GA401QM.415 08/11/2023 [ 1534.673939] RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv] [ 1534.673970] Code: 83 ff 40 74 25 48 89 c7 48 21 f7 48 85 d2 75 1c 48 89 f8 0f 1f 00 48 89 c6 48 89 cf e8 9e ea 75 f1 90 31 c0 5d e9 40 8c 5c f2 <0f> 0b f6 c2 01 75 15 48 f7 d0 48 89 c7 48 21 f7 48 81 e7 00 f0 ff [ 1534.673972] RSP: 0018:ffffbbed50ba7c98 EFLAGS: 00010246 [ 1534.673975] RAX: 00000003f6bdf000 RBX: ffff9e4ec15635f8 RCX: ffff9e4ec15635f0 [ 1534.673977] RDX: 0000000000000161 RSI: 000fffffffffffff RDI: 0000000000000040 [ 1534.673979] RBP: ffffbbed50ba7c98 R08: ffffbbed50e75000 R09: ffff9e51697cebb8 [ 1534.673981] R10: ffffbbed50e75000 R11: 0000000000000000 R12: 0000000000000001 [ 1534.673982] R13: ffffffffc4d3b460 R14: ffffbbed50cbe000 R15: ffffbbed50ba7d60 [ 1534.673984] FS: 00007fabf0b7e6c0(0000) GS:ffff9e554e700000(0000) knlGS:0000000000000000 [ 1534.673985] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1534.673987] CR2: 00007fabd88c4000 CR3: 00000003e97ce000 CR4: 0000000000750ef0 [ 1534.673988] PKRU: 55555554 [ 1534.673990] Call Trace: [ 1534.673995] <TASK> [ 1534.673997] ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674022] ? __warn+0x81/0x130 [ 1534.674032] ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674057] ? report_bug+0x171/0x1a0 [ 1534.674064] ? handle_bug+0x3c/0x80 [ 1534.674068] ? exc_invalid_op+0x17/0x70 [ 1534.674071] ? asm_exc_invalid_op+0x1a/0x20 [ 1534.674076] ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674101] ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674124] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674127] __apply_to_page_range+0x3ba/0x8b0 [ 1534.674136] rtR0MemObjNativeProtect+0x78/0xb0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674160] VBoxHost_RTR0MemObjProtect+0x8b/0xc0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674189] supdrvIOCtl+0x2cad/0x31b0 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674216] VBoxDrvLinuxIOCtl_7_0_14+0x151/0x240 [vboxdrv 6b4b2edfb2f8cde0b70adb3961927d98ca3ce978] [ 1534.674241] __x64_sys_ioctl+0x97/0xd0 [ 1534.674246] do_syscall_64+0x89/0x170 [ 1534.674250] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674252] ? ksys_write+0xd0/0xe0 [ 1534.674255] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674257] ? syscall_exit_to_user_mode+0x80/0x230 [ 1534.674259] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674261] ? do_syscall_64+0x96/0x170 [ 1534.674263] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674265] ? srso_alias_return_thunk+0x5/0xfbef5 [ 1534.674267] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 1534.674271] RIP: 0033:0x7fac1690f3df [ 1534.674320] 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 [ 1534.674322] RSP: 002b:00007fabf0b7cd20 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 1534.674324] RAX: ffffffffffffffda RBX: 0000000000000030 RCX: 00007fac1690f3df [ 1534.674325] RDX: 00007fabd8600010 RSI: 0000000000005684 RDI: 0000000000000007 [ 1534.674327] RBP: 00007fabf0b7cd80 R08: 0000000000000000 R09: 00007fabf0b7cc00 [ 1534.674328] R10: 00007fabd8600010 R11: 0000000000000246 R12: 00007fabe7137a63 [ 1534.674329] R13: 0000000000000000 R14: 00007fab94000ca0 R15: 0000000000000000 [ 1534.674333] </TASK> [ 1534.674334] ---[ end trace 0000000000000000 ]--- ``` OS: OpenSUSE Tw 20240411 Virtualbox: virtualbox-7.0.14-7.1 Kernel: 6.8.4-rc1-1-default, 6.8.4-rc1-1-default #1 SMP PREEMPT_DYNAMIC Thu Apr 4 07:22:28 UTC 2024 (1089550) x86_64 x86_64 x86_64 GNU/Linux CPU: AMD Ryzen 9 5900HS with Radeon Graphics, 16 threads Packages: virtualbox-host-source-7.0.14-7.1.noarch virtualbox-kmp-default-7.0.14_k6.8.4_rc1_1-7.3.x86_64 virtualbox-qt-7.0.14-7.1.x86_64 virtualbox-7.0.14-7.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1222674] BTRFS Snapshots failing since kernel 6.8.4rc1, still working on 6.8.2
by bugzilla_noreply＠suse.com 12 Apr '24

12 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222674 https://bugzilla.suse.com/show_bug.cgi?id=1222674#c6 --- Comment #6 from pallas wept <pallaswept(a)proton.me> --- (In reply to Arvin Schnell from comment #5) > Also, are there any error messages in dmesg or journalctl? dmesg is silent on this, journalctl is largely uninteresting, it just lets me know the timeline service failed: >Apr 13 02:00:00 Pallas CRON[21411]: (root) CMD (run-parts /etc/cron.hourly) >Apr 13 02:00:00 Pallas CRON[21410]: (root) CMDEND (run-parts /etc/cron.hourly) >Apr 13 02:00:00 Pallas systemd[1]: Started Timeline of Snapper Snapshots. >Apr 13 02:00:00 Pallas dbus-daemon[8554]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.229' (uid=0 pid=21412 comm="/usr/lib/snapper/systemd-helper --timeline") >Apr 13 02:00:00 Pallas systemd[1]: Starting DBus interface for snapper... >Apr 13 02:00:00 Pallas dbus-daemon[8554]: [system] Successfully activated service 'org.opensuse.Snapper' >Apr 13 02:00:00 Pallas systemd[1]: Started DBus interface for snapper. >Apr 13 02:00:00 Pallas systemd-helper[21412]: running timeline for 'home'. >Apr 13 02:00:00 Pallas systemd-helper[21412]: running timeline for 'root'. >Apr 13 02:00:00 Pallas systemd-helper[21412]: Creating snapshot failed. >Apr 13 02:00:00 Pallas systemd-helper[21412]: timeline for 'root' failed. >Apr 13 02:00:00 Pallas systemd[1]: snapper-timeline.service: Main process exited, code=exited, status=1/FAILURE >Apr 13 02:00:00 Pallas systemd[1]: snapper-timeline.service: Failed with result 'exit-code'. >Apr 13 02:01:00 Pallas systemd[1]: snapperd.service: Deactivated successfully. I'll branch snapper in the morning and let you know what it says. Thanks for the insight :) -- You are receiving this mail because: You are the assignee for the bug.

1 0