July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228416] New: Aeon RC3 (20240726) automatically unlocks partition even if kernel cmdline is modified
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228416 Bug ID: 1228416 Summary: Aeon RC3 (20240726) automatically unlocks partition even if kernel cmdline is modified Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: philipp(a)nhus.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 Build Identifier: I've installed Aeon RC3 (Aeon-Installer.x86_64-0.1.0-Snapshot20240726.raw) on a ThinkPad T14s AMD Gen1. The installation finished without any errors and Aeon was installed in "Default" mode. After booting the system, I wanted to see if it actually prevents booting if the kernel cmdline is modified. So, I hit "e" in the systemd-boot menu, changed the cmdline, and the system booted without asking for the recovery key, which I did not expect. I then checked the LUKS header with "cryptsetup luksDump <device>" which reported the following: tpm2-hash-pcrs: 7 tpm2-pcrlock: false But pcrlock has to be enabled to prevent tampering of boot config on Aeon, correct? I then manually re-enrolled with systemd-cryptenroll <device> --wipe-slot 2 systemd-cryptenroll <device> --tpm2-device auto Afterwards, luksDump reports this: tpm2-hash-pcrs: <empty> tpm2-pcrlock: true which is what I would expect. If I now try to modify the cmdline on boot, it correctly asks for the recovery key. I've reinstalled 3 times, always with the same behavior. I don't have a tik.log on the stick after installation, is it not saved if the installation finished successfully? Reproducible: Always Steps to Reproduce: 1. Install Aeon-Installer.x86_64-0.1.0-Snapshot20240726 from USB stick 2. Boot the system, set up initial user account & reboot 3. In systemd-boot, press "e" to edit the kernel cmdline, remove "quiet" from the cmdline and boot Actual Results: System automatically unlocks partition without asking for recovery code. Expected Results: System refuses automatic unlocking of partition, because kernel cmdline has changed. It asks for the recovery code to unlock. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1228659] New: Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228659 Bug ID: 1228659 Summary: Snapshot 20240730 - unbootable after transactional-update dup Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Transactional Update Assignee: aplanas(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All Aeon installations (and I suspect all MicroOS systemd-boot installations) are failing to boot after a transactional-update dup to the latest snapshot I suspect the cause is the misbehaviour of the sdbootutil plugin reported during the transactional-update Example logs below: (25/41) Installing: kernel-default-6.10.2-1.1.x86_64 [... Error: No ESP detected. Legacy system? ................................................................................................... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.10.2-1-default 6.10.2-1-default dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: No KEYMAP configured. dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut-install: ERROR: installing 'grub2-editenv' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.kGpiZ2/initramfs -a date btrfs awk grub2-editenv dracut[I]: *** Including module: pcr-signature *** dracut[I]: *** Including module: transactional-update *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[E]: Failed to detect udev version! dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Generating early-microcode cpio image *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=btrfs dracut[I]: rd.driver.pre=overlay dracut[I]: root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=403,subvol=/@/.snapshots/98/snapshot,subvol=@/.snapshots/98/snapshot dracut[I]: *** Stripping files *** dracut[I]: *** Stripping files done *** dracut[I]: *** Creating image file '/boot/initrd-6.10.2-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.10.2-1-default' done *** /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory CA enrolled. Skip /etc/uefi/certs/1F673297.crt Error: No ESP detected. Legacy system? ... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory done] -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1228602] New: systemd-cryptenroll fails on standard secureboot settings on ASUS motherboard - system still bootable but without a recovery key
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228602 Bug ID: 1228602 Summary: systemd-cryptenroll fails on standard secureboot settings on ASUS motherboard - system still bootable but without a recovery key Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: mats.bursjo(a)ownmail.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876379 --> https://bugzilla.suse.com/attachment.cgi?id=876379&action=edit log from an unsuccessful install The installation of Aeon Desktop RC3 fails when the secureboot settings on my ASUS prime x670-p motherboard is set to "Other OS" and "Standard". It requires the more lax "Other OS" - "Custom" setting" to work. I tried installing 3 times. Once the error was hidden in the UI due to an inability to copy the user data (this log is however lost). I was instead booted into a working OS that updated some TPM package - but since the recovery key was not enrolled I could not boot again. I then got the error two more times. I then changed the bios setting mentioned above, and installation worked. Attached is the log file from the last failed install. I understand this is probably a very specific bug, and I submit it mostly to help any other person in the same situation. The system being in a bootable state when the cryptenroll fails to enroll a recovery key seems like a good way to have a system update nuke some poor soul's data. Best regards Mats -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227621] New: IncompleteRead Error with Packaging Distrobox
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227621 Bug ID: 1227621 Summary: IncompleteRead Error with Packaging Distrobox Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: pirateclip(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This on the surface looks similar to boo#834990 except that this requires one to use osc inside of a distrobox such as the image made for packagers: https://en.opensuse.org/Distrobox#Distrobox_For_Packagers and it affects doing a local build of any package on build.opensuse.org too. I have not gotten and IncompleteRead errors when using osc outside of distrobox (such as installing it on the MicroOS base system or on TW) Steps to reproduce: 1 Create a distrobox as detailed on the wiki: $ distrobox create --root --name tumbleweed-pkg --image registry.opensuse.org/opensuse/distrobox-packaging:latest 2 Do zypper dup (the image is not always up to date and recommends need to be installed or else osc misses a lot of features such as the loading bar when you run osc co and it is taking some time to download something) 3 Enter into it and osc co any package 4 Do a local build with osc build If osc then tries to download dependencies then *sometimes* it will fail midway through with a message like this: [40/171] (openSUSE:Tumbleweed) libuuid1-2.40.1-4.1.x86_64.rpm: 100%|############################################################################| Time: 0:00:00 [41/171] (openSUSE:Tumbleweed) libsmartcols1-2.40.1-4.1.x86_64.rpm: 100%|#######################################################################| Time: 0:00:00 [42/171] (openSUSE:Tumbleweed) libcrypt1-4.4.36-1.6.x86_64.rpm: 100%|###########################################################################| Time: 0:00:00 Connection broken: IncompleteRead(196304 bytes read, 31608179 more expected) | ETA: --:--:-- I can work around this by then just rerunning osc build and then it will download some more deps before maybe throwing another IncompleteRead error while trying to download a different dependency. Eventually it succeeds and I can get on with my local build -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227749] New: Orange PI 5 Plus limited functionality
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227749 Bug ID: 1227749 Summary: Orange PI 5 Plus limited functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876046 --> https://bugzilla.suse.com/attachment.cgi?id=876046&action=edit idbloader for Orange PI 5 Plus I managed to get U-Boot running on the Orange PI 5 Plus with a couple of key SUSE patches to the point where it is booting into OpenSUSE AARCH64 Rockchip version. Currently only the following are working: - PCIe - NVME - eMMC/SD - Serial port The following are not working: - USB - Realtek RTL8125 2.5G Ethernet drivers (seen on PCIe bus) - Realtek RTL8852BE (seen on PCIe bus, not driver seems to be available) Note that in U-Boot that USB also does not work and the network cards are not supported (as of 7/15). I am attaching my U-Boot and idbloader for this board which should allow it to boot, use the usual offset 64 for the idbloader and offset 16384 for U-Boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset 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: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

30 Dec '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 on the CC list for the bug.

1 25

[Bug 1217428] New: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217428 Bug ID: 1217428 Summary: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/385844/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: luca.boccassi(a)gmail.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: thomas.leroy(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Side-channel proofing PKCS#1 1.5 paths (Marvin) Ref: https://github.com/latchset/pkcs11-provider/pull/308 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6258 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1220119] New: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220119 Bug ID: 1220119 Summary: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:" 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jwiesner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Some tests running on o3 (openQA instance on https://openqa.opensuse.org/) triggers in dmesg. All tests run in VM via qemu. This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered for 2 tests: arp and host (both tests did not fail): OpenQA::run_ltp.pm: Starting ipneigh01_arp [ 410.818828][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820365][ C0] clocksource: 'kvm-clock' wd_nsec: 506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821824][ C0] clocksource: 'tsc' cs_nsec: 49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.823293][ C0] clocksource: Clocksource 'tsc' skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of 506724586 ns (506 ms) [ 410.824843][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.825707][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.109710][T28135] Initializing XFRM netlink socket OpenQA::run_ltp.pm: Starting ipneigh01_ip OpenQA::run_ltp.pm: Starting arping01 OpenQA::run_ltp.pm: Starting clockdiff01 OpenQA::run_ltp.pm: Starting ftp OpenQA::run_ltp.pm: Starting host [ 410.818845][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820687][ C0] clocksource: 'kvm-clock' wd_nsec: 506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821794][ C0] clocksource: 'tsc' cs_nsec: 804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.822919][ C0] clocksource: Clocksource 'tsc' skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns (506 ms) [ 410.824088][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.824768][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.126759][T28138] Initializing XFRM netlink socket Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3 (kernel tests in https://openqa.opensuse.org/group_overview/32) where host test keeps failing (but arp test is working), I don't see it on ltp_net_tcp_cmds on x86_64 on o3. I was not able to trigger this on VM on my laptop (x86_64). Others found that systemd-networkd test on Tumbleweed on x86_64 (https://openqa.opensuse.org/group_overview/1) [ 570.754611][ C0] Showing busy workqueues and worker pools: [ 570.755654][ C0] workqueue events: flags=0x0 [ 570.756580][ C0] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 [ 570.756586][ C0] pending: drm_fb_helper_damage_work [ 570.759551][ C0] sysrq: Show Blocked State zDBFr-0- [ 311.682306][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 311.684482][ C0] clocksource: 'kvm-clock' wd_nsec: 621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff [ 311.686513][ C0] clocksource: 'tsc' cs_nsec: 952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff [ 311.688559][ C0] clocksource: Clocksource 'tsc' skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns (621 ms) [ 311.690452][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 311.691559][ C0] tsc: Marking TSC unstable due to clocksource watchdog Test runs also on aarch64, but error is not there. Is it a problem of openQA setup? There are other bugs. -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 1226017] New: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi'
by bugzilla_noreply＠suse.com 26 Dec '24

26 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226017 Bug ID: 1226017 Summary: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi' Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: anselm.gora(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Build Identifier: fwupd expects to find EFI/opensuse/shim.efi while on openSUSE Aeon the path is EFI/systemd/shim.efi https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… fwupd seems to use os release ID but it's also a build option: https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… Tumbleweed seems to patch it: https://build.opensuse.org/projects/openSUSE:Factory/packages/fwupd/files/f… Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 10