June 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211459] [Leap 15.4][btrfs][snapper-cleanup], 'systemctl start snapper-cleanup' causes infinite message 'BTRFS warning (device vda2): qgroup rescan is already in progress' in syslog and causes 'yast2 lan' command hang
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211459 https://bugzilla.suse.com/show_bug.cgi?id=1211459#c20 --- Comment #20 from Lubos Kocman <lubos.kocman(a)suse.com> --- Do we have any update on the issue team? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 01 Jun '23

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c43 --- Comment #43 from Joey Lee <jlee(a)suse.com> --- I have updated the openSUSE wiki page for UEFI to add a "Signing kernel module" section: https://en.opensuse.org/openSUSE:UEFI#Signing_kernel_module_for_verification openSUSE users can reference it to signing their self-built kernel module. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211069] Bugged RMRR prevents PCIe Passthrough of KVM VMs on certain platforms
by bugzilla_noreply＠suse.com 01 Jun '23

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211069 https://bugzilla.suse.com/show_bug.cgi?id=1211069#c5 --- Comment #5 from Joerg Roedel <jroedel(a)suse.com> --- When devices have RMRRs are are not USB host controlers, there is no way to passthrough them. That is because there is no way to preserve the RMRR regions when attaching the device to a guest. This needs to be fixed in the machine firmware. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211898] New: stress-ng fsize failure on NFSv3
by bugzilla_noreply＠suse.com 01 Jun '23

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211898 Bug ID: 1211898 Summary: stress-ng fsize failure on NFSv3 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: richard.palethorpe(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While setting up some OpenQA NFS testing I came across the following error with stress-ng. $ stress-ng --sequential -1 --timeout 3 --class filesystem ... stress-ng: fail: [3866] fsize: fallocate unexpectedly succeeded at offset 262144 (0x40000), expecting EFBIG error stress-ng: fail: [3866] fsize: expected a SIGXFSZ signal at offset 262144 (0x40000), nothing happened stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 106797 (0x1a12d), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 1 (0x1), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 3 (0x3), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 7 (0x7), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 15 (0xf), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 31 (0x1f), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 63 (0x3f), expecting EFBIG error ... This does not happen with NFSv4. It happens with both NFSv3 sync and async. I don't see any other errors. The tests have not been merged or scheduled on the main OpenQA instance yet. When they are I can post a link. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17181 -- You are receiving this mail because: You are the assignee for the bug.

1 0