July 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1220814] New: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?)
by bugzilla_noreply＠suse.com 28 Aug '24

28 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220814 Bug ID: 1220814 Summary: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: michael.burge77(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873182 --> https://bugzilla.suse.com/attachment.cgi?id=873182&action=edit full journalctl of the third crash I have an old portable with a wonky dc power jack which tends to generate a few quick AC0<->BAT0 events in succession. Starting with kernel 6.7.6-1-default the system locks up. Log is full of ``` Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost plasmashell[2682]: plasma-pk-updates: acPluggedChanged onBattery: false -> true Mar 01 17:34:17 ost kernel: BUG: unable to handle page fault for address: 0000000000007b8a Mar 01 17:34:17 ost kernel: #PF: supervisor read access in kernel mode Mar 01 17:34:17 ost kernel: #PF: error_code(0x0000) - not-present page ``` until it locks up with ``` Mar 01 18:11:29 ost kernel: note: kworker/11:5[23457] exited with irqs disabled Mar 01 18:11:50 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:54 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:55 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:58 ost plasmashell[5912]: [5912:0301/181158.744595:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. Mar 01 18:12:05 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:12:06 ost kernel: BUG: workqueue lockup - pool cpus=11 node=0 flags=0x0 nice=0 stuck for 37s! ``` at which point only holding down the power button works. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1224046] New: [Kernel][Upgrade] After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE
by bugzilla_noreply＠suse.com 26 Aug '24

26 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224046 Bug ID: 1224046 Summary: [Kernel][Upgrade] After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: viktors.trubovics(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874762 --> https://bugzilla.suse.com/attachment.cgi?id=874762&action=edit Boot video with loglevel=7 After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE It fails to load KDE on all 5.14.21-150500.x kernels but boots successfully on 5.14.21-150400.24.100 and 5.14.21-150400.24.97 kernels. See attached boot video. Used procedure for upgrade: https://en.opensuse.org/SDB:System_upgrade_to_Leap_15.5 Machine is alive so I can collect any additional information. -- You are receiving this mail because: You are the assignee for the bug.

1 14

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

21 Aug '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 60

[Bug 1221504] New: bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 20 Aug '24

20 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 Bug ID: 1221504 Summary: bluetooth errors on every kernel starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell Precision 7530 with Intel Wireless-AC 9260 Bluetooth Adapter and kernel 6.4.0-150600.9.2. Errors constantly appear when booting the system, but bluetooth works with my headphones, although there are some audio artifacts at the beginning when playing sound. Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth daemon 5.71 Mär 16 17:49:38 precision bluetoothd[1073]: Starting SDP server Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support csip plugin Mär 16 17:49:38 precision bluetoothd[1073]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support micp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support vcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support mcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bass plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bap plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support admin plugin Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth management interface 1.22 initialized Mär 16 17:49:38 precision dbus-daemon[1074]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=1073 comm="/usr/lib/bluetooth/bluetoothd ") Mär 16 17:49:38 precision bluetoothd[1073]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Battery Provider Manager created Mär 16 17:49:38 precision bluetoothd[1073]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution Mär 16 17:49:38 precision bluetoothd[1073]: Failed to clear UUIDs: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Too small Add Device complete event Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision (smartd)[1105]: smartd.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts Looks like this is the error https://bugzilla.kernel.org/show_bug.cgi?id=217651 Here's a fix https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… -- You are receiving this mail because: You are the assignee for the bug.

1 24

[Bug 1228605] New: Freezed screen
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228605 Bug ID: 1228605 Summary: Freezed screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: OES - Linux Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monesi.manuel06(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The system with KDE freezes casually, it needs a reboot to work againg. It happens with a Dell Vostro 3520 -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1228523] New: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=180184, emitted seq=180186
by bugzilla_noreply＠suse.com 12 Aug '24

12 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228523 Bug ID: 1228523 Summary: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=180184, emitted seq=180186 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fhassel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, my openSUSE 15.6 system freezes about twice a day. This started to happen directly after the upgrade from 15.5 to 15.6. It happens with kernel-default-6.4.0-150600.23.14.2.x86_64 from the distribution, but also with kernel-default-6.10.2-lp155.2.1.gd3b5079.x86_64 which I have installed from the Kernel:stable:Backport repository. I have triggered a crash manually, and these are the lines from dmesg during the time the system freezed: ---------------------------->---------------------------- [15563.421924] ath11k_pci 0000:01:00.0: msdu_done bit in attention is not set [18330.887533] ath11k_pci 0000:01:00.0: msdu_done bit in attention is not set [19186.445841] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=180184, emitted seq=180186 [19186.446566] amdgpu 0000:33:00.0: amdgpu: GPU reset begin! [19186.589535] amdgpu 0000:33:00.0: amdgpu: MODE2 reset [19186.599147] amdgpu 0000:33:00.0: amdgpu: GPU reset succeeded, trying to resume [19186.599358] [drm] PCIE GART of 1024M enabled (table at 0x000000F43FC00000). [19186.611561] [drm] VRAM is lost due to GPU reset! [19186.611569] amdgpu 0000:33:00.0: amdgpu: PSP is resuming... [19186.634249] amdgpu 0000:33:00.0: amdgpu: reserve 0xa00000 from 0xf43e000000 for PSP TMR [19186.969747] amdgpu 0000:33:00.0: amdgpu: RAS: optional ras ta ucode is not available [19186.982314] amdgpu 0000:33:00.0: amdgpu: RAP: optional rap ta ucode is not available [19186.982329] amdgpu 0000:33:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [19186.982341] amdgpu 0000:33:00.0: amdgpu: SMU is resuming... [19186.982888] amdgpu 0000:33:00.0: amdgpu: SMU is resumed successfully! [19186.984915] [drm] DMUB hardware initialized: version=0x04000044 [19187.314676] [drm] kiq ring mec 2 pipe 1 q 0 [19187.319934] [drm] JPEG decode initialized successfully. [19187.319952] amdgpu 0000:33:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [19187.319962] amdgpu 0000:33:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0 [19187.319969] amdgpu 0000:33:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0 [19187.319976] amdgpu 0000:33:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0 [19187.319982] amdgpu 0000:33:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [19187.319989] amdgpu 0000:33:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [19187.319995] amdgpu 0000:33:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [19187.320002] amdgpu 0000:33:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [19187.320008] amdgpu 0000:33:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [19187.320015] amdgpu 0000:33:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [19187.320022] amdgpu 0000:33:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0 [19187.320028] amdgpu 0000:33:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0 [19187.320035] amdgpu 0000:33:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8 [19187.320042] amdgpu 0000:33:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 [19187.320048] amdgpu 0000:33:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 [19187.320055] amdgpu 0000:33:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8 [19187.329018] amdgpu 0000:33:00.0: amdgpu: recover vram bo from shadow start [19187.329033] amdgpu 0000:33:00.0: amdgpu: recover vram bo from shadow done [19187.329075] amdgpu 0000:33:00.0: amdgpu: GPU reset(1) succeeded! [19210.748201] sysrq: Emergency Sync [19210.759574] Emergency Sync complete [19218.301327] sysrq: Trigger a crash ----------------------------<---------------------------- -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1228388] [Build 20240728] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 31 Jul '24

31 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228388 https://bugzilla.suse.com/show_bug.cgi?id=1228388#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |ptesarik(a)suse.com --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- With the current head of crash, the error is different: # crash vmcore /usr/lib/modules/6.10.2-2.g65a34e2-default/vmlinux.xz ... crash: page excluded: kernel virtual address: ffff9075c042cb90 type: "xa_node.slots[off]" So this is an upstream bug, likely. (Despite there are many support-for-6.10 fixes in the current head.) tl;dr this still fails: echo c >/proc/sysrq-trigger crash path_to_vmcore /usr/lib/modules/6.10.2-2.g65a34e2-default/vmlinux.xz -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228387] New: [Build 20240728] openQA test fails in welcome: qxl graphics garbage
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228387 Bug ID: 1228387 Summary: [Build 20240728] openQA test fails in welcome: qxl graphics garbage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4363532/modules/welc ome/steps/7 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation This is relared to kernel 6.10 All tests that run on qxl graphics are giving render issues e.g * https://openqa.opensuse.org/tests/4363537#step/logs_from_installation_syste… * https://openqa.opensuse.org/tests/4363532#step/welcome/7 openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnome_dual_windows10@uefi_win fails in [welcome](https://openqa.opensuse.org/tests/4363532/modules/welcome/steps/7) ## Test suite description Maintainer: grace.wang(a)suse.com ## Reproducible Fails since (at least) Build [20240728](https://openqa.opensuse.org/tests/4362928) ## Expected result Last good: [20240726](https://openqa.opensuse.org/tests/4361550) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1228387] [Build 20240728] openQA test fails in welcome: qxl graphics garbage
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228387 https://bugzilla.suse.com/show_bug.cgi?id=1228387#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- Fixed by: commit c537fb4e3d36e7cd1a0837dd577cd30d3d64f1bc Author: Thomas Zimmermann <tzimmermann(a)suse.de> Date: Mon Jul 8 16:21:37 2024 +0200 drm/qxl: Pin buffer objects for internal mappings hopefully. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1228318] kernel crash on two laptops during shutdown/reboot
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228318 https://bugzilla.suse.com/show_bug.cgi?id=1228318#c6 --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Eric Benton from comment #5) > I thought kdump required a debug kernel? No :). -- You are receiving this mail because: You are the assignee for the bug.

1 0