July 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1201450] New: Cannot compile kernel, No rule to make target '.kernel_signing_key.pem', needed by 'certs/signing_key.x509'
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201450 Bug ID: 1201450 Summary: Cannot compile kernel, No rule to make target '.kernel_signing_key.pem', needed by 'certs/signing_key.x509' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaronw(a)doofus.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time I follow the instructions for README.SUSE I get the following error: make -j24 vmlinux modules GEN Makefile DESCEND objtool DESCEND bpf/resolve_btfids CALL /usr/src/linux-5.14.21-150400.22/scripts/atomic/check-atomics.sh CALL /usr/src/linux-5.14.21-150400.22/scripts/checksyscalls.sh CHK include/generated/compile.h make[2]: *** No rule to make target '.kernel_signing_key.pem', needed by 'certs/signing_key.x509'. Stop. make[2]: *** Waiting for unfinished jobs.... make[1]: *** [/usr/src/linux-5.14.21-150400.22/Makefile:1882: certs] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [/usr/src/linux-5.14.21-150400.22/Makefile:220: __sub-make] Error 2 The instructions in README.SUSE do not describe how to remove the signing key requirement or how to generate a self-signed key for this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200442] kernel-install-tools should be recommended by all kernel-source flavors
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200442 https://bugzilla.suse.com/show_bug.cgi?id=1200442#c22 --- Comment #22 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:2376-1: An update that solves 9 vulnerabilities and has 40 fixes is now available. Category: security (important) Bug References: 1065729,1179195,1180814,1185762,1192761,1193629,1194013,1195504,1195775,1196901,1197362,1197754,1198020,1199487,1199489,1199657,1200217,1200263,1200442,1200571,1200599,1200600,1200608,1200619,1200622,1200692,1200806,1200807,1200809,1200810,1200813,1200816,1200820,1200821,1200822,1200825,1200828,1200829,1200925,1201050,1201080,1201143,1201147,1201149,1201160,1201171,1201177,1201193,1201222 CVE References: CVE-2021-26341,CVE-2021-4157,CVE-2022-1679,CVE-2022-20132,CVE-2022-20154,CVE-2022-29900,CVE-2022-29901,CVE-2022-33981,CVE-2022-34918 JIRA References: Sources used: openSUSE Leap 15.3 (src): kernel-azure-5.3.18-150300.38.69.1, kernel-source-azure-5.3.18-150300.38.69.1, kernel-syms-azure-5.3.18-150300.38.69.1 SUSE Linux Enterprise Module for Public Cloud 15-SP3 (src): kernel-azure-5.3.18-150300.38.69.1, kernel-source-azure-5.3.18-150300.38.69.1, kernel-syms-azure-5.3.18-150300.38.69.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201396] New: 5.18.9-2-default does not boot
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201396 Bug ID: 1201396 Summary: 5.18.9-2-default does not boot 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: aotto1968(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: after background update my linux does not boot anymore kernel: 5.18.9-1-default is OK, but 5.18.9-2-default not Reproducible: Always Steps to Reproduce: 1. choose the kernel 2. boot 3. hang Expected Results: boot kernel: 5.18.9-1-default is ok -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c8 Stanislav Brabec <sbrabec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec(a)suse.com Assignee|sbrabec(a)suse.com |kernel-bugs(a)opensuse.org Flags|needinfo?(genes1122(a)gmail.c | |om) | --- Comment #8 from Stanislav Brabec <sbrabec(a)suse.com> --- Thanks. Reassigning. Just guessing that the problem is somewhere in the kernel, in the way, how it holds information about rslave. It seems to stay connected to the device, even if it is successfully remounted. It could easily happen, because technically, setting of propagation flag (--make-rslave) uses a special form of mount() syscall: mount("none", "/mnt/chroot/sys", NULL, MS_REC|MS_SLAVE, NULL) = 0 I do not see any reverse command that could be called before the unplug. -- 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 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c7 --- Comment #7 from Gene Snider <genes1122(a)gmail.com> --- (In reply to Stanislav Brabec from comment #3) > This is very strange: > > Jul 07 13:52:20 Mobile-PC kernel: BTRFS warning: duplicate device /dev/sdc2 > devid 1 generation 6733 scanned by mount (4717) > > It looks that even if everything was correctly unmounted, something in the > kernel still holds a record for /dev/sdb2, which prevents it from releasing. > > > Just a dumb idea: > > What happens if you do rmdir /mnt/chroot after unplug, but before replug. It > seems, that something becomes bound to this directory, but it is not a > mounted volume. > > Does the bug happens then? Does the device get name sdb2 or sdc2 then? > > In any case, it looks like a kernel problem that has nothing to do with > mount/libmount. Should I open a bug against the kernel, then? Or will you move this bug? Thanks, Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201262] New: kernel 5.18.9 hangs at luks encryption password prompt
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201262 Bug ID: 1201262 Summary: kernel 5.18.9 hangs at luks encryption password prompt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugs(a)clearingstelle-eeg-kwkg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We need to use Opensuse Leap 15.3 with the kernel installed from the Kernel-Backports repository: https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar… because it is a Ryzen 4000 CPU computer. Everything worked fine. With the kernel update 5.18.9-lp153.3.1.ge00841d the computer hangs at boot at the password prompt for the luks encryption. No keyboard input from the laptop or from an external USB-Keyboard is accepted and the boot process stops. The Laptop is an Acer Travelmate P215-41, Model No: N19Q8, Model Name TMP215-41-R0WF. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1200947] Error message on resume
by bugzilla_noreply＠suse.com 09 Jul '22

09 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200947 https://bugzilla.suse.com/show_bug.cgi?id=1200947#c2 Luigi Baldoni <aloisio(a)gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(aloisio(a)gmx.com) | --- Comment #2 from Luigi Baldoni <aloisio(a)gmx.com> --- Created attachment 860091 --> https://bugzilla.suse.com/attachment.cgi?id=860091&action=edit Hardware data for Lenovo 15ADA05 > Do you happen to have installed tlp package? If yes, try to uninstall it. I have. The problem disappears after removing it but I'm not sure suspend works properly anymore. Should I try tlp 1.5.0? > In anyway, please give the full dmesg output and the output of hwinfo. See attachment. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c6 --- Comment #6 from Gene Snider <genes1122(a)gmail.com> --- It's not btrfs specific, here's the log for the same operations on an ext4 partition. Jul 08 11:44:23 Mobile-PC sudo[3379]: gene : TTY=pts/0 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/umount -v -R /mnt/chroot Jul 08 11:44:23 Mobile-PC sudo[3379]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-security.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC sudo[3379]: pam_unix(sudo:session): session closed for user root Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-config.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-fs-fuse-connections.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-tracing.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-kernel-debug.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-fs-bpf.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-firmware-efi-efivars.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-fs-pstore.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys-fs-cgroup.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot-sys.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1]: mnt-chroot.mount: Deactivated successfully. Jul 08 11:44:23 Mobile-PC systemd[1448]: Created slice User Background Tasks Slice. Jul 08 11:44:23 Mobile-PC systemd[1448]: Starting Cleanup of User's Temporary Files and Directories... Jul 08 11:44:23 Mobile-PC systemd[1448]: Finished Cleanup of User's Temporary Files and Directories. > # unplug Jul 08 11:44:36 Mobile-PC kernel: usb 2-1: USB disconnect, device number 2 Jul 08 11:44:36 Mobile-PC kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Jul 08 11:44:36 Mobile-PC systemd[1]: Stopping Sabrent-Samsung temperature monitor daemon, started by udev rule... Jul 08 11:44:36 Mobile-PC systemd[1]: Sabrent-Samsung-tempd.service: Deactivated successfully. Jul 08 11:44:36 Mobile-PC systemd[1]: Stopped Sabrent-Samsung temperature monitor daemon, started by udev rule. Jul 08 11:44:36 Mobile-PC systemd[1]: Sabrent-Samsung-tempd.service: Consumed 1.867s CPU time. Jul 08 11:44:36 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Jul 08 11:44:36 Mobile-PC kernel: sd 2:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK > sudo rmdir /mnt/chroot Jul 08 11:44:47 Mobile-PC sudo[3426]: gene : TTY=pts/0 ; PWD=/home/gene ; USER=root ; COMMAND=/usr/bin/rmdir /mnt/chroot Jul 08 11:44:47 Mobile-PC sudo[3426]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Jul 08 11:44:47 Mobile-PC kernel: Buffer I/O error on dev sdb3, logical block 1081344, lost sync page write Jul 08 11:44:47 Mobile-PC kernel: JBD2: Error -5 detected when updating journal superblock for sdb3-8. Jul 08 11:44:47 Mobile-PC kernel: Aborting journal on device sdb3-8. Jul 08 11:44:47 Mobile-PC kernel: Buffer I/O error on dev sdb3, logical block 1081344, lost sync page write Jul 08 11:44:47 Mobile-PC kernel: JBD2: Error -5 detected when updating journal superblock for sdb3-8. Jul 08 11:44:47 Mobile-PC kernel: EXT4-fs error (device sdb3): ext4_put_super:1226: comm rmdir: Couldn't clean up the journal Jul 08 11:44:47 Mobile-PC kernel: EXT4-fs (sdb3): Remounting filesystem read-only Jul 08 11:44:47 Mobile-PC sudo[3426]: pam_unix(sudo:session): session closed for user root Lots of different error messages, but that's expected. Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201114] mount fails after umount -R, then unplug/re-plug external drive
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201114 http://bugzilla.opensuse.org/show_bug.cgi?id=1201114#c5 --- Comment #5 from Gene Snider <genes1122(a)gmail.com> --- I forgot to mention whether it remounted as sdb2 or sdbc2, so I reran the test. It remounts as /dev/sdb2. > sudo umount -v -R /mnt/chroot umount: /mnt/chroot/sys/kernel/security unmounted umount: /mnt/chroot/sys/fs/cgroup (cgroup2) unmounted umount: /mnt/chroot/sys/fs/pstore unmounted umount: /mnt/chroot/sys/firmware/efi/efivars unmounted umount: /mnt/chroot/sys/fs/bpf (bpf) unmounted umount: /mnt/chroot/sys/kernel/debug unmounted umount: /mnt/chroot/sys/kernel/tracing (tracefs) unmounted umount: /mnt/chroot/sys/fs/fuse/connections (fusectl) unmounted umount: /mnt/chroot/sys/kernel/config unmounted umount: /mnt/chroot/sys unmounted umount: /mnt/chroot unmounted > # unplug > sudo rmdir /mnt/chroot > # replug > sudo mkdir /mnt/chroot > sudo mount -v UUID=4c96a0c2-f72f-4827-b023-83ba000b2fd2 /mnt/chroot mount: /dev/sdb2 mounted on /mnt/chroot. Gene -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200919] System is freeze on X loading
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200919 http://bugzilla.opensuse.org/show_bug.cgi?id=1200919#c5 --- Comment #5 from Hillwood Yang <hillwoodroc(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > Could you try to boot with the old Leap 15.3 kernel and see whether it works? > If zypper or rpm complains dependency, ignore it and forcibly install. kernel 5.3.18 conflicts with util-linux-2.37.2. And the installation does not provide the workaround option to ignore the conflict. debianARM:/home/hillwood # zypper install --force --oldpackage ./kernel-default-5.3.18-lp154.59.78.1.aarch64.rpm ��... ��... �� 'kernel-default-5.3.18-lp154.59.78.1.aarch64'�� '�� RPM ��'�� ... �� util-linux-2.37.2-150400.6.26.aarch64 �� kernel-default-5.3.18-lp154.59.78.1.aarch64 �� "kernel < 5.8" �� 1�� kernel-default-5.3.18-lp154.59.78.1.aarch64 �� [1/c/d/?] (c): -- You are receiving this mail because: You are the assignee for the bug.

1 0