April 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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

[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#c5 --- Comment #5 from Arvin Schnell <aschnell(a)suse.com> --- The logs show that btrfs_util_create_snapshot_fd2() fails with errno = 2 (No such file or directory). That is very strange since the function gets two file descriptors and one path. The path is constant ("snapshot") and is created - so should never exist beforehand. If one of the file descriptors is wrong I would expect a different errno. Maybe the errno of 2 is a leftover of a previous ioctl. Can someone who can reproduce the problem compile snapper and place an 'errno = 0;' before the btrfs_util_create_snapshot_fd2 in BtrfsUtils.cc? Also, are there any error messages in dmesg or journalctl? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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#c4 --- Comment #4 from pallas wept <pallaswept(a)proton.me> --- Sorry to hear it, Ingo. FWIW, I don't get the snapshot check errors. This is from one of my failing hourly snapshots: > 2024-04-12 22:00:00 MIL libsnapper(28132) snapperd.cc(main):283 - Requesting DBus name > 2024-04-12 22:00:00 MIL libsnapper(28132) snapperd.cc(main):298 - Loading snapper configs > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(getConfigs):355 - Snapper get-configs > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(getConfigs):356 - libsnapper version 0.10.7 > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(reload):922 - loading file /etc/sysconfig/snapper > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SNAPPER_CONFIGS value:root home > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(reload):922 - loading file /etc/snapper/configs/root > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SUBVOLUME value:/ > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(reload):922 - loading file /etc/snapper/configs/home > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SUBVOLUME value:/home > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:ALLOW_USERS value: > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:ALLOW_GROUPS value: > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:ALLOW_USERS value: > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:ALLOW_GROUPS value: > 2024-04-12 22:00:00 MIL libsnapper(28132) snapperd.cc(main):311 - Listening for method calls and signals > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):97 - Snapper constructor > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):98 - snapper version 0.10.7 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):99 - libsnapper version 7.4.0 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):100 - config_name:home root_prefix:/ disable_filters:false > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(reload):922 - loading file /etc/snapper/configs/home > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SUBVOLUME value:/home > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:FSTYPE value:btrfs > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:QGROUP value: > 2024-04-12 22:00:00 MIL libsnapper(28132) Selinux.cc(_is_selinux_enabled):141 - SELinux support disabled > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SYNC_ACL value:no > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):130 - subvolume:/home filesystem:btrfs > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(loadIgnorePatterns):204 - number of ignore patterns:8 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapshot.cc(read):344 - found 25 snapshots > 2024-04-12 22:00:00 WAR libsnapper(28132) FileUtils.cc(SDir):88 - THROW: open failed path:/home/.snapshots/8185 errno:2 (No such file or directory) > 2024-04-12 22:00:00 WAR libsnapper(28132) Btrfs.cc(checkSnapshot):490 - CAUGHT: open failed path:/home/.snapshots/8185 errno:2 (No such file or directory) > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):97 - Snapper constructor > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):98 - snapper version 0.10.7 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):99 - libsnapper version 7.4.0 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):100 - config_name:root root_prefix:/ disable_filters:false > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(reload):922 - loading file /etc/snapper/configs/root > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SUBVOLUME value:/ > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:FSTYPE value:btrfs > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:QGROUP value:1/0 > 2024-04-12 22:00:00 MIL libsnapper(28132) AsciiFile.cc(get_value):1078 - key:SYNC_ACL value:no > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(Snapper):130 - subvolume:/ filesystem:btrfs > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapper.cc(loadIgnorePatterns):204 - number of ignore patterns:8 > 2024-04-12 22:00:00 MIL libsnapper(28132) Snapshot.cc(read):344 - found 90 snapshots > 2024-04-12 22:00:00 WAR libsnapper(28132) FileUtils.cc(SDir):88 - THROW: open failed path://.snapshots/9891 errno:2 (No such file or directory) > 2024-04-12 22:00:00 WAR libsnapper(28132) Btrfs.cc(checkSnapshot):490 - CAUGHT: open failed path://.snapshots/9891 errno:2 (No such file or directory) > 2024-04-12 22:00:00 ERR libsnapper(28132) Btrfs.cc(createSnapshot):328 - create snapshot failed, btrfs_util_create_snapshot_fd2() failed, errno:2 (No such file or directory) > 2024-04-12 22:00:00 WAR libsnapper(28132) Btrfs.cc(createSnapshot):329 - THROW: create snapshot failed > 2024-04-12 22:00:00 WAR libsnapper(28132) Snapshot.cc(createHelper):780 - CAUGHT: create snapshot failed > 2024-04-12 22:00:00 WAR libsnapper(28132) Snapshot.cc(createHelper):785 - RETHROW: create snapshot failed > 2024-04-12 22:00:00 WAR libsnapper(28132) Client.cc(dispatch):1983 - CAUGHT: create snapshot failed > 2024-04-12 22:00:00 WAR libsnapper(28130) DBusConnection.cc(send_with_reply_and_block):104 - THROW: dbus error exception > 2024-04-12 22:00:30 MIL libsnapper(28132) Snapper.cc(~Snapper):142 - Snapper destructor > 2024-04-12 22:00:30 MIL libsnapper(28132) Snapper.cc(~Snapper):142 - Snapper destructor > 2024-04-12 22:01:00 MIL libsnapper(28132) snapperd.cc(main):315 - Exiting -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 11 Apr '24

11 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c22 Andrea Manzini <andrea.manzini(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #22 from Andrea Manzini <andrea.manzini(a)suse.com> --- closing this as fixed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218184] New: Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug ID: 1218184 Summary: Eliminate the need for 'OBS source links': convert to _multibuild Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: Dolomite Version: Milestone 5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fcrozat(a)suse.com CC: dimstar(a)opensuse.org, dleuenberger(a)suse.com, fcrozat(a)suse.com, jslaby(a)suse.com, kernel-bugs(a)opensuse.org, mls(a)suse.com, msuchanek(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com Depends on: 1211226 Target Milestone: --- Group: SUSE Enterprise Partner Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1211226 +++ In order to prepare for 'git based source management', we need to fix up a few technical issues. One such issue is 'source links' not being supported in git (i.e in OBS we have openSUSE:Factory/kernel-source as the main package plus a bunch of 'linked packages', each with the name of the additional spec files) The solution is, technically seem, rather simple: using _multibuild multibuild support on OBS is known in two variants, one using a single spec file and conditionals inside the spec file based on @BUILD_FLAVOR@ (probably the more known way) but OBS also supports 'just' listing the additional spec files as 'flavors' the _multibuild to be added to the kernel-source (main package) can be generated like this:  #!/bin/sh echo "<multibuild>" > _multibuild for pkg in *.spec; do test "{$pkg}" == "kernel-source.spec" && continue echo " <package>${pkg/.spec/}</package>" >> _multibuild; done echo "</multibuild>" >> _multibuild  the spec files do not need to be changed in anyway with this method -- You are receiving this mail because: You are on the CC list for the bug.

1 59

[Bug 1211226] Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1211226 Bug 1211226 depends on bug 1218998, which changed state. Bug 1218998 Summary: cannot abort build/restart build/wipe binaries for multibuild packages https://bugzilla.suse.com/show_bug.cgi?id=1218998 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221504] bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 https://bugzilla.suse.com/show_bug.cgi?id=1221504#c19 --- Comment #19 from Andreas <opendreas(a)gmail.com> --- (In reply to Takashi Iwai from comment #15) > OK, then it should be reported to the upstream devs. > Care to do that from your side? At best, write to linux-bluetooth ML. Feel > free to put me (tiwai(a)suse.de) to Cc. > Alternatively, you can report to bugzilla.kernel.org, but it gets little > attention in general. (In reply to Takashi Iwai from comment #15) > OK, then it should be reported to the upstream devs. > Care to do that from your side? At best, write to linux-bluetooth ML. Feel > free to put me (tiwai(a)suse.de) to Cc. > Alternatively, you can report to bugzilla.kernel.org, but it gets little > attention in general. I created a new issue, but I don't see an option to add you to the CC list on github. https://github.com/bluez/bluez/issues/809 -- 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 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c46 --- Comment #46 from Andreas <opendreas(a)gmail.com> --- (In reply to Paolo De Pasquale from comment #45) > (In reply to Andreas from comment #44) > > > No. One user attributes these errors to freezes in Wine and WeChat. > > I can confirm wine freezes on my Thinkpad ThinkPad P15 Gen 1 running TW > 20240402 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 -- 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 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c45 --- Comment #45 from Paolo De Pasquale <paolo.depasquale(a)suse.com> --- (In reply to Andreas from comment #44) > No. One user attributes these errors to freezes in Wine and WeChat. I can confirm wine freezes on my Thinkpad ThinkPad P15 Gen 1 running TW 20240402 -- 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 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c44 --- Comment #44 from Andreas <opendreas(a)gmail.com> --- Created attachment 874166 --> https://bugzilla.suse.com/attachment.cgi?id=874166&action=edit journald-6.4.0-150600.1-patched (In reply to Takashi Iwai from comment #43) > (In reply to Andreas from comment #40) > > The following message contains patches from the Intel developer. > > https://patchwork.freedesktop.org/series/125157/ > > The patches aren't included in the upstream (yet?). No. One user attributes these errors to freezes in Wine and WeChat. I don't use these programs so I can't confirm this. The Intel developer says they can't do anything because... no access to proprietary nvidia module. In theory, these errors occur when nothing is connected to the HDMI port. > I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 > repo. > The package will appear later at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ > > Please give it a try later. The patch works, the errors have disappeared. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Then some spurious interrupt must be waking up the machine. Please check the following: - Enable/disable LID ACPI: To check the status: % cat /proc/acpi/wakeup To toggle the status: % echo LID > /proc/acpi/wakeup If this doesn't influence, it's something else than ACPI wakeup. Then, you can try the direct suspend by echo mem > /sys/power/state Does it behave differently? -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c7 Tristan Miller <psychonaut(a)nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #7 from Tristan Miller <psychonaut(a)nothingisreal.com> --- Yes, I've rebooted (still using 6.8.4-rc1) and the problem occurs again. I suspect that the kernel version may have nothing to do with this bug. Rather, each time the computer is rebooted, it somehow decides whether or not closing the lid will wake from suspend, and it maintains this behaviour at least until the next reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219522] New: Kernel panic with 6.7.x version
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 Bug ID: 1219522 Summary: Kernel panic with 6.7.x version 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 872422 --> https://bugzilla.suse.com/attachment.cgi?id=872422&action=edit dmesg 6.6.11-1 kernel I get a kernel panic since the 6.7.x kernels. The capslock key is flickering and if i use the "recovery mode" i usually see: [T8] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf01fa3/0x940300/0x12e800/0x400000, board id: 3276, fw id: 2700068 [T8] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [T8] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2 I have no idea how to debug this. No error message. In the past i applied a kernel bisect (for debian i think) but i could not find a guide for Tumbleweed. Hardware: Lenovo T580 Grub menu contains: * 6.7.2-1 * 6.7.1-2 * 6.6.11-1 Included a "dmesg" output of a normal boot with the "6.6.11-1" kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 22

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

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c48 --- Comment #48 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 874102 --> https://bugzilla.suse.com/attachment.cgi?id=874102&action=edit ok_6.8.2-2.gb88b81e-default -- 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 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c47 --- Comment #47 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Thanks for all the help! Can this bug also explain the random freezes while in desktop mode or is this code called only once (at boot)? How to continue? The current change at least prevent a panic but i assume a driver still contains a bug/race-condition. Can i see in which (suse) mainline kernel this workaround is upstreamed? Latest commit seems a while ago: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/dri… Should i file a bug somewhere? I will include "ok_6.8.2-2.gb88b81e-default.txt". The same kernel version log, but that startup did not trigger the error. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Yes, it looks so; it's likely a problem triggered by BIOS setup or such, which had been changed accidentally. Feel free to reopen if the issue is reproduced. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222388] Unable to build kernel
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222388 https://bugzilla.suse.com/show_bug.cgi?id=1222388#c2 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org Status|NEW |RESOLVED Component|Development |Kernel CC| |Andreas.Stieger(a)gmx.de --- Comment #2 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- . *** This bug has been marked as a duplicate of bug 1216042 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c5 --- Comment #5 from Tristan Miller <psychonaut(a)nothingisreal.com> --- I found a kernel bug report for the same issue with another model of ThinkPad: https://bugzilla.kernel.org/show_bug.cgi?id=214855 That bug report indicates that the issue was fixed with 5.16. So I installed 5.16 from <http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.16/backpor…> was no longer able to reproduce the problem. I rebooted again, this time to 6.8.4-rc1, and I still can't reproduce the problem. Perhaps the bug is there in all the kernel versions I've tested, but is not always reproducible. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c4 --- Comment #4 from Tristan Miller <psychonaut(a)nothingisreal.com> --- The problem is also reproducible with 6.7.9 from your repository and 6.4.0 from the 15.6 repository. But strangely, when I downgrade kernel-default back to 5.14.21, or even boot into a read-only snapshot with that kernel, the problem is still reproducible! I'm not sure what to make of this. In any event, it would be nice if I could use any kernel version that keeps the laptop suspended when I close the lid. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- You can find in my OBS repo, e.g. http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.7/backport/ Also, try Leap 15.6 kernel. http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ This should work stably without surprises. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c2 --- Comment #2 from Tristan Miller <psychonaut(a)nothingisreal.com> --- I don't know; I didn't try 6.7.x. I tried only 5.14.21, which is the current stable kernel for Leap 15.5, and 6.8.4-rc1, which is the current kernel available in backports. (I wanted to upgrade from 5.14.21 because that version has a different suspend problem where, about 10% of the time, the computer locks up or reboots when waking from suspend.) I can try 6.7.x if you tell me where to find a Leap 15.5 package, or where to find the project on the build service so that I can build one myself. I found 6.8.4-rc1 in the repository <https://build.opensuse.org/package/show/Kernel:stable:Backport/kernel-source> but it has only one revision in the history. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222319] New: kernel-firmware-* packages have duplicate WHENCE license files
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222319 Bug ID: 1222319 Summary: kernel-firmware-* packages have duplicate WHENCE license files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Target Milestone: --- Found By: --- Blocker: --- The "WHENCE" file is >300K and included as %license in all kernel-firmware-* packages: /usr/share/licenses/kernel-firmware-usb-network/WHENCE /usr/share/licenses/kernel-firmware-ueagle/WHENCE /usr/share/licenses/kernel-firmware-ti/WHENCE /usr/share/licenses/kernel-firmware-sound/WHENCE /usr/share/licenses/kernel-firmware-serial/WHENCE /usr/share/licenses/kernel-firmware-realtek/WHENCE /usr/share/licenses/kernel-firmware-radeon/WHENCE /usr/share/licenses/kernel-firmware-qcom/WHENCE /usr/share/licenses/kernel-firmware-platform/WHENCE /usr/share/licenses/kernel-firmware-nfp/WHENCE /usr/share/licenses/kernel-firmware-network/WHENCE /usr/share/licenses/kernel-firmware-mwifiex/WHENCE /usr/share/licenses/kernel-firmware-mediatek/WHENCE /usr/share/licenses/kernel-firmware-media/WHENCE /usr/share/licenses/kernel-firmware-marvell/WHENCE /usr/share/licenses/kernel-firmware-intel/WHENCE /usr/share/licenses/kernel-firmware-i915/WHENCE /usr/share/licenses/kernel-firmware-dpaa2/WHENCE /usr/share/licenses/kernel-firmware-bnx2/WHENCE /usr/share/licenses/kernel-firmware-bluetooth/WHENCE /usr/share/licenses/kernel-firmware-atheros/WHENCE /usr/share/licenses/kernel-firmware-ath12k/WHENCE /usr/share/licenses/kernel-firmware-ath11k/WHENCE /usr/share/licenses/kernel-firmware-ath10k/WHENCE /usr/share/licenses/kernel-firmware-amdgpu/WHENCE This could be optimized by moving common files into a separate package or maybe not shipping this at all. I'm not sure whether the info inside is actually necessary, it mostly just links to the actual license files? -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 https://bugzilla.suse.com/show_bug.cgi?id=1222345#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- This didn't happen with 6.7.x, right? I guess it's a regression in the recent upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222345 Bug ID: 1222345 Summary: Laptop wakes from suspend once the user closes the lid Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a ThinkPad T14 Gen 4, which has an AMD Ryzen 7 PRO 7840U. With kernel-default 6.8.4-rc1, the computer can be suspended when the lid is open, but it wakes up as soon as the user closes the lid. The problem does not occur with kernel-default 5.14.21. -- 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 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c43 --- Comment #43 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 874079 --> https://bugzilla.suse.com/attachment.cgi?id=874079&action=edit fail02_6.8.2-2.gb88b81e-default -- 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 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c42 --- Comment #42 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 874078 --> https://bugzilla.suse.com/attachment.cgi?id=874078&action=edit fail01_6.8.2-2.gb88b81e-default -- 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 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c41 --- Comment #41 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- i think i misunderstood. I expected 6.8.2-2.gb88b81e-default still to panic. Failed to find 6.8.3 so i installed kernel-default-6.8.4-1.1.g1089550.x86_64.rpm . That one will also panic sometimes. Will include the dmesg output of 6.8.2-2.gb88b81e-default. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c40 --- Comment #40 from Michal Suchanek <msuchanek(a)suse.com> --- The KVM on Power10 is probably best bet long term because it shares a lot of infrastructure with PowerVM which is the supported and tested virtualization. At this point it's quite new and there is no experience with it so far so there may be some issues as well. The KVM on POWER8 and POWER9 is used a lot but often requires some workaround because of a bug that was introduced upstream and not yet tracked down - this is not something that SLE supports, and any fixes are best-effort. The KVM on this particular hardware seems to be especially broken, this issue is AFAIK not observed on other machines, even POWER8. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c39 --- Comment #39 from Oliver Kurz <okurz(a)suse.com> --- True, so to refine my statement: I understand we can continue running KVM@PowerNV on older Leap versions and older quirky hardware until any new version of SLE/Leap supports KVM again as well or alternatively switch our workload to Tumbleweed as hypervisor base OS running and use Power10+ hardware, correct? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c38 --- Comment #38 from Michal Suchanek <msuchanek(a)suse.com> --- If you had new hardware. Seems your problem is specific to these machines which are different from the other POWER8 hardware in use where the problem is not reproducible. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c37 --- Comment #37 from Oliver Kurz <okurz(a)suse.com> --- ok, so I understand we can continue running KVM@PowerNV on older Leap versions until any new version of SLE/Leap supports that as well or alternatively switch our workload to Tumbleweed as hypervisor base OS, correct? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202138] PowerPC machine crashes frequently after upgrading to Leap 15.4
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1202138 https://bugzilla.suse.com/show_bug.cgi?id=1202138#c36 --- Comment #36 from Michal Suchanek <msuchanek(a)suse.com> --- On Power10 PowerVM hypervisor based KVM is planned, should work with Tumbleweed already. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Great, thanks! Your post appeared at https://lore.kernel.org/all/424B3F10-D91C-4F47-B33C-BB66FE4DB91A@suse.de/ Let's track there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c9 --- Comment #9 from William Brown <william.brown(a)suse.com> --- I'm not really thrilled to do this but I have sent the email. Lets pray it goes okay. -- 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 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c39 --- Comment #39 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- not sure how to modify the osc command to retrieve the file :( Next command downloads newer files: osc getbinaries Kernel:stable/kernel-source:kernel-default/standard/x86_64 Assume it does match the site: https://build.opensuse.org/package/show/Kernel:stable/kernel-source But this is also unknown to me. -- 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 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c37 --- Comment #37 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- Created attachment 874028 --> https://bugzilla.suse.com/attachment.cgi?id=874028&action=edit dmesg of the 6.8.2-2.1.gb88b81e kernel (no panics seen yet) -- 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 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219522 https://bugzilla.suse.com/show_bug.cgi?id=1219522#c36 --- Comment #36 from Edwin KM <e.kleinmentink(a)zonnet.nl> --- I understand. But i can not reproduce the crash with your latest test kernel. So, i think there a multiple scenarios: * It is very recently fixed (> 6.8.1-1). Seems unlikely * It is really timing related. This 6.8.1-1 kernel is maybe faster/slower and the crash does not happen. So, i hope that a older kernel with your patch will crash again to generate more information. About the touchpad. Sorry, i remembered incorrectly. The pad, the mouse buttons and the red mouse-tracker are indeed disabled. But not in the BIOS, i disabled them in XFCE it seems. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c21 --- Comment #21 from Daniel Wagner <daniel.wagner(a)suse.com> --- Are we good to close this one? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185542] 32 bit Tumbleweed failing to boot with the 5.12.0-1-pae kernel must revert to 5.11.16-1-pae kernel.
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1185542 Paul Graff <pj.opensuse(a)gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|64bit |i586 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- FWIW, get_maintainers gives: Peter Huewe <peterhuewe(a)gmx.de> (maintainer:TPM DEVICE DRIVER) Jarkko Sakkinen <jarkko(a)kernel.org> (maintainer:TPM DEVICE DRIVER) Jason Gunthorpe <jgg(a)ziepe.ca> (reviewer:TPM DEVICE DRIVER) linux-integrity(a)vger.kernel.org (open list:TPM DEVICE DRIVER) linux-kernel(a)vger.kernel.org (open list) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- It's no longer a wild west as in 20 years ago, and there is no much reason to hesitate. It's really better you reporting it since you have the specific system and program to test with, and have better understanding around the TPM handling from user-space side. (Though, in the end it might be unchanged, as the issue could be a firmware issue; I thought the value TPM2_PT_CONTEXT_GAP_MAX is read from the system, not what the kernel defines?) When you reporting, feel free to put me (tiwai(a)suse.de) to Cc in case you need assistance from the distro kernel side. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c6 --- Comment #6 from William Brown <william.brown(a)suse.com> --- Well this issue affects tumbleweed, and may block kanidms unix client working properly as well as himmelblau, both of which use the tpm via tpmrm0. So it seems like an issue that affects tumbleweed to me. (Kanidm is being used as an IDM within opensuse infrastructure now). I'm also not a kernel developer. The kernel community has a community of toxicity and hostility. And I've been on the receiving end of that in the past. I'm not signed up to the bug trackers. I'm not on the mailing lists. I have no idea where I would even start to report a bug, and given past experience I'm sure if I don't report it in precisely the correct way then I'll surely be sent a list of derogatory comments. This is why I'm asking you *here* to report it and manage the bug on my behalf. I don't know the process. I'm not reporting it upstream. Put another way. If you reported a bug to me about LDAP or IDM I would not ask you to report it upstream. I would report it upstream on your behalf because I know the in's an outs of the process, and I would take it from there. I hope you will do the same for me now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- It's an upstream issue as you're reporting for Tumbleweed, so the best place to address is there :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c4 --- Comment #4 from William Brown <william.brown(a)suse.com> --- (In reply to Takashi Iwai from comment #3) > Then the best would be to report to the kernel upstream devs. > Care to do that? I don't feel comfortable reporting an issue to upstream kernel directly. That's why I'm reporting it here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222098] tpm resource manager - tpm2_save-context failed with error 0x0901
by bugzilla_noreply＠suse.com 03 Apr '24

03 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222098 https://bugzilla.suse.com/show_bug.cgi?id=1222098#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Then the best would be to report to the kernel upstream devs. Care to do that? -- You are receiving this mail because: You are the assignee for the bug.

1 0