February 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219180] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219180 Bug ID: 1219180 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tzimmermann(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are the assignee for the bug.

1 1

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

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220541 Bug ID: 1220541 Summary: kexec does a full reboot with kernel 6.7.6-1.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: me(a)pavinjoseph.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tested on identical systems with kexec-tools 2.0.27-3.2 (on both) and kernel 6.7.5-1.1 (on working system) and 6.7.6-1.1 (on faulty system). Faulty system (fully updated as of Feb 28 2024) is on Tumbleweed release 20240226. Working system is on release 20240222. Issue reproduced on working system by doing zypper ref and zypper in kernel-default to upgrade just the kernel to the latest version. Issue happens after the next cold boot and persists. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 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 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 1219188] New: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219188 Bug ID: 1219188 Summary: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded 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: jack(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Starting from build 20240123, which brought kernel 6.7 splice fail: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded Jan, could you please have look whether it's a test bug or mainline kernel bug? I can reproduce the problem also on mainline 6.8.0-rc1 (testing with rapido). -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1211975] New: freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 26 Mar '24

26 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1211975 Bug ID: 1211975 Summary: freeze with flip_done time out when external monitor attached 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: mattm3a(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Only when external monitor is attached, display freezes for a Lenovo T14. External monitor is connected via HDMI. Mean time between freeze ~1 hour. Output from terminal (CTRL+ALT+F1) looks something like this (from image, not copied in text form): [374.123930][ T1729] i915 0000:00:02.0: [drm] *ERROR* flip_done timed out [374.123938][ T1729] i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) lsb-release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230531 Codename: n/a uname -srvp Linux 6.3.4-1-default #1 SMP PREEMPT_DYNAMIC Mon May 29 06:22:29 UTC 2023 (2c66b1f) x86_64 I think this issue first appeared for me in mid-May, but I'm unsure of exactly what Tumbleweed update that was. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1219653] New: Enable CONFIG_GDB_SCRIPTS
by bugzilla_noreply＠suse.com 22 Mar '24

22 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219653 Bug ID: 1219653 Summary: Enable CONFIG_GDB_SCRIPTS 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_GDB_SCRIPTS installs useful gdb macros. See: https://www.kernel.org/doc/html/latest/dev-tools/gdb-kernel-debugging.html -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1220303] New: KMP installation fails to make device node
by bugzilla_noreply＠suse.com 18 Mar '24

18 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1220303 Bug ID: 1220303 Summary: KMP installation fails to make device node Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing a KMP such as vhba-kmp-default.rpm, no device node /dev/vhba_ctl shows up until the system is rebooted. As such, the device cannot be opened without loading the module manually (and thus triggering an udev event to produce the device node belatedly). == Observed behavior == # zypper in vhba-kmp-default Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: vhba-kmp-default 1 new package to install. Overall download size: 27.1 KiB. Already cached: 0 B. After the operation, additional 57.7 KiB will be used. Continue? [y/n/v/...? shows all options] (y): Retrieving: vhba-kmp-default-20240202_k6.7.5_1-1.2.x86_64 (base) (1/1), 27.1 KiB Retrieving: vhba-kmp-default-20240202_k6.7.5_1-1.2.x86_64.rpm ............[done] Verifying ................................................................[done] Preparing ................................................................[done] (0/1) Executing prein script for: vhba-kmp-default-20240202_k6.7.5_1-1.2.x[done] (1/1) Installing: vhba-kmp-default-20240202_k6.7.5_1-1.2.x86_64 ..........[done] (1/1) Executing postin script for: vhba-kmp-default-20240202_k6.7.5_1-1.2.[done] (1/1) Executing posttrans script for: vhba-kmp-default-20240202_k6.7.5_1-1[done] # ls -l /dev/vhb* ls: cannot access '/dev/vhb*': No such file or directory == Expected behavior == Create the device node right away. # ls -l /dev/vhb* crw------- 1 root root 10, 170 Feb 25 14:31 /dev/vhba_ctl == Possible implementation == Adjust the KMP %post scriptlet so that it executes: systemctl restart kmod-static-nodes.service systemd-tmpfiles-setup-dev.service -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1218552] New: [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 - Steam Deck
by bugzilla_noreply＠suse.com 13 Mar '24

13 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218552 Bug ID: 1218552 Summary: [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 - Steam Deck 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: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871668 --> https://bugzilla.suse.com/attachment.cgi?id=871668&action=edit dmesg-pci-eror Hi everyone, Every once in awhile, this Steam Deck print out this error and the system drops me to tty. I do not know why. I did change the SSD to a WD Black as listed below. I do not know how to reproduce the error. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20231228 Codename: n/a Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Valve Version: F7A0120 Release Date: 12/01/2023 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 16 MB Information for package kernel-default: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : kernel-default Version : 6.6.7-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 238.1 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.6.7-1.1.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2023-12-14 17:36:48 +0000 GIT Revision: 6869d093e8485475463bc171d23d7c4142fb6fa4 GIT Branch: stable === START OF INFORMATION SECTION === Model Number: WD_BLACK SN770M 1TB Serial Number: 233101400993 Firmware Version: 731100WD PCI Vendor/Subsystem ID: 0x15b7 IEEE OUI Identifier: 0x001b44 Total NVM Capacity: 1,000,204,886,016 [1.00 TB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 001b44 4a48dc08dc Local Time is: Thu Jan 4 17:36:48 2024 PST Firmware Updates (0x14): 2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x00df): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify Log Page Attributes (0x7e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Log0_FISE_MI Telmtry_Ar_4 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 36 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 0% Data Units Read: 3,267,997 [1.67 TB] Data Units Written: 3,844,737 [1.96 TB] Host Read Commands: 22,073,106 Host Write Commands: 62,512,660 Controller Busy Time: 79 Power Cycles: 576 Power On Hours: 46 Unsafe Shutdowns: 123 [ 402.012325] pcieport 0000:00:01.2: AER: Corrected error received: 0000:01:00.0 [ 402.012342] nvme 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 402.012346] nvme 0000:01:00.0: device [15b7:5042] error status/mask=00000001/0000e000 [ 402.012351] nvme 0000:01:00.0: [ 0] RxErr [ 421.302005] usb 3-1.1: new full-speed USB device -- You are receiving this mail because: You are the assignee for the bug.

1 6

[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 12 Mar '24

12 Mar '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 the assignee for the bug.

1 36