May 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

21 Jun '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 22

[Bug 1224434] New: Page cache invalidation failure during direct I/O write
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224434 Bug ID: 1224434 Summary: Page cache invalidation failure during direct I/O write Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 URL: https://openqa.opensuse.org/tests/4202483/modules/AD03 3/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avinesh.kumar(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-ltp_aiodio_part1@ppc64le fails in [AD033](https://openqa.opensuse.org/tests/4202483/modules/AD033/steps/8) ## Test suite description LTP_ENV=TMPDIR=/var/tmp is to test on btrfs instead of tmpfs ## Reproducible Fails since (at least) Build [20240131](https://openqa.opensuse.org/tests/3907534) Last good: Unknown ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -------- LTP Test - https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/io/l… we run this test with various combinations of write block size and I/O numbers (https://github.com/linux-test-project/ltp/blob/master/runtest/ltp-aiodio.pa…) failing scenarios on ppc64le: AD033 aiocp -b 4k -n 4 -f DIRECT AD035 aiocp -b 4k -n 8 -f DIRECT AD037 aiocp -b 4k -n 16 -f DIRECT (few times doesn't fail) AD039 aiocp -b 4k -n 32 -f DIRECT (few times doesn't fail) AD047 aiocp -b 8k -n 4 -f DIRECT AD049 aiocp -b 8k -n 8 -f DIRECT AD051 aiocp -b 8k -n 16 -f DIRECT (few times doesn't fail) AD061 aiocp -b 16k -n 4 -f DIRECT AD063 aiocp -b 16k -n 8 -f DIRECT AD075 aiocp -b 32k -n 4 -f DIRECT dmesg log during each of these failures: OpenQA::run_ltp.pm: Starting AD032 OpenQA::run_ltp.pm: Starting AD033 [ 48.470444][ T62] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O! [ 48.471404][ T62] File: /var/tmp/LTP_aioTBsaEH/dstfile.bin PID: 62 Comm: kworker/1:1 OpenQA::run_ltp.pm: Starting AD034 OpenQA::run_ltp.pm: Starting AD035 This issue is not present on aarch64 and x86_64 tumbleweed builds. And on SLE15-SP6, we are not seeing this on ppc64le also. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1223131] New: Disable WAN drivers
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223131 Bug ID: 1223131 Summary: Disable WAN drivers 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: --- We do not provide WAN in SLE at all (it lives in the -optional subpackage, so is Leap only). Provided: * no our customer apparently uses this, * is poorly maintained upstream (hdlc in particular), * it's unlikely TW/Leap users run this (but not impossible), * we diverge from SLE configs, we should consider disabling whole WAN in TW and Leap too. The proposed config change is: @@ -4217,20 +4217,7 @@ CONFIG_QTNFMAC=m CONFIG_QTNFMAC_PCIE=m CONFIG_MAC80211_HWSIM=m CONFIG_VIRT_WIFI=m -CONFIG_WAN=y -CONFIG_HDLC=m -CONFIG_HDLC_RAW=m -CONFIG_HDLC_RAW_ETH=m -CONFIG_HDLC_CISCO=m -CONFIG_HDLC_FR=m -CONFIG_HDLC_PPP=m -CONFIG_HDLC_X25=m -CONFIG_FRAMER=m -CONFIG_PCI200SYN=m -CONFIG_WANXL=m -CONFIG_PC300TOO=m -CONFIG_FARSYNC=m -CONFIG_LAPBETHER=m +# CONFIG_WAN is not set CONFIG_IEEE802154_DRIVERS=m CONFIG_IEEE802154_FAKELB=m # CONFIG_IEEE802154_AT86RF230 is not set @@ -4658,7 +4645,7 @@ CONFIG_SERIAL_MCTRL_GPIO=y CONFIG_SERIAL_NONSTANDARD=y # CONFIG_MOXA_INTELLIO is not set CONFIG_MOXA_SMARTIO=m -CONFIG_N_HDLC=m +# CONFIG_N_HDLC is not set CONFIG_IPWIRELESS=m CONFIG_N_GSM=m CONFIG_NOZOMI=m -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1224820] New: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset
by bugzilla_noreply＠suse.com 14 Jun '24

14 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224820 Bug ID: 1224820 Summary: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Critical 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: --- I recently assembled a computer based on the ASUS WRX90E Sage motherboard and a 32-core AMD Threadripper PRO CPU. In the BIOS, I enabled 64-bit PCIe remapping support to allow the OS to remap devices to 64-bit address space. For some odd reason, however, the system went into standby and could not recover. Pressing Control+Alt+F10 reported problems remapping the PCIe devices, and then there was a failure with BTRFS reading bad data, and the system hung. The NVME drive is an old Intel PCIe card I had lying around that only had light usage. I strongly suspect there are compatibility issues with the new motherboard chipset since it is pretty new. The WRX90 chipset is only used in two motherboards I am aware of, the ASUS board and an ASRock board. I could not capture the messages directly since the FS went read-only and it started spewing a ton of BTRFS errors before I could capture the screen. As for why it went into suspend mode to begin with, I have no idea. The reason I know it did is I sshed into the box remotely and got a broadcast message: Broadcast message from aaronw@localhost (Tue 2024-05-21 14:09:53 PDT): The system will suspend now! I will try disabling S4/S5 support in the BIOS and see if that helps and I can also try disabling the 64-bit PCIe remapping as well. System specs: ASUS Pro WRX90E Sage SE EEB motherboard with latest BIOS firmware AMD Threadripper Pro 7975WX CPU Gigabyte Ge-Force RTX4090 Windforce V2 24G graphics card Intel NVME drive Kingston Fury Renegade Pro 128GB ECC Registered DDR5 (PC5 48000) memory. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1224805] New: Failed to start kdump on update
by bugzilla_noreply＠suse.com 10 Jun '24

10 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224805 Bug ID: 1224805 Summary: Failed to start kdump on update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Looks like this was caused due to being short on memory, but as the machine has SWAP available, could you please confirm that this is not a product bug? # free -m total used free shared buff/cache available Mem: 892 510 44 16 389 382 Swap: 2050 583 1467 2024-05-17T03:32:24.281360+02:00 unreal6 sh[18901]: (537/566) Installing: kdump-2.0.3+git10.gfdb71b2-150600.1.2.x86_64 [... 2024-05-17T03:32:24.281604+02:00 unreal6 sh[18901]: Updating /etc/sysconfig/kdump ... 2024-05-17T03:32:24.334296+02:00 unreal6 systemd[1]: Reloading requested from client PID 18611 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:24.334360+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:24.924343+02:00 unreal6 systemd[1]: Reloading finished in 589 ms. 2024-05-17T03:32:24.961835+02:00 unreal6 systemd[1]: Reloading requested from client PID 18656 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:24.961918+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:25.630446+02:00 unreal6 systemd[1]: Reloading finished in 667 ms. 2024-05-17T03:32:25.666952+02:00 unreal6 systemd[1]: Reloading requested from client PID 18704 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:25.667019+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:26.369634+02:00 unreal6 systemd[1]: Reloading finished in 702 ms. 2024-05-17T03:32:26.439702+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump.service". 2024-05-17T03:32:26.439788+02:00 unreal6 systemd[1]: Reloading requested from client PID 18754 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:26.439877+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:27.110180+02:00 unreal6 systemd[1]: Reloading finished in 669 ms. 2024-05-17T03:32:27.144729+02:00 unreal6 [RPM][18604]: install kdump-2.0.3+git10.gfdb71b2-150600.1.2.x86_64: success 2024-05-17T03:32:27.149403+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump-early.service". 2024-05-17T03:32:27.149452+02:00 unreal6 sh[18901]: Removed "/etc/systemd/system/multi-user.target.wants/kdump-notify.service". 2024-05-17T03:32:27.149507+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump.service -> /usr/lib/systemd/system/kdump.service. 2024-05-17T03:32:27.149542+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump-early.service -> /usr/lib/systemd/system/kdump-early.service. 2024-05-17T03:32:27.149574+02:00 unreal6 sh[18901]: Created symlink /etc/systemd/system/multi-user.target.wants/kdump-notify.service -> /usr/lib/systemd/system/kdump-notify.service. 2024-05-17T03:32:27.149596+02:00 unreal6 sh[18901]: Stopping kdump ... 2024-05-17T03:32:27.169840+02:00 unreal6 systemd[1]: Reloading requested from client PID 18804 ('systemctl') (unit auto-upgrade.service)... 2024-05-17T03:32:27.169906+02:00 unreal6 systemd[1]: Reloading... 2024-05-17T03:32:27.792978+02:00 unreal6 systemd[1]: Reloading finished in 622 ms. 2024-05-17T03:32:27.854093+02:00 unreal6 systemd[1]: Stopping Load kdump kernel and initrd... 2024-05-17T03:32:27.872108+02:00 unreal6 unload.sh[18863]: config option KDUMP_COPY_KERNEL is deprecated, ignoring 2024-05-17T03:32:27.896361+02:00 unreal6 systemd[1]: kdump.service: Deactivated successfully. 2024-05-17T03:32:27.930224+02:00 unreal6 systemd[1]: Stopped Load kdump kernel and initrd. 2024-05-17T03:32:27.978698+02:00 unreal6 systemd[1]: Starting Load kdump kernel and initrd... 2024-05-17T03:32:27.994187+02:00 unreal6 load.sh[18867]: config option KDUMP_COPY_KERNEL is deprecated, ignoring 2024-05-17T03:32:30.191833+02:00 unreal6 auditd[826]: Audit daemon rotating log files 2024-05-17T03:32:49.966979+02:00 unreal6 load.sh[22533]: console=com3 in Xen commandline not handled 2024-05-17T03:32:49.980421+02:00 unreal6 load.sh[18867]: Starting kdump kernel load; kexec cmdline: /sbin/kexec -p /var/lib/kdump/kernel --append=" console=ttyS2,115200n8 sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/var/lib/kdump/initrd -a 2024-05-17T03:32:50.552928+02:00 unreal6 kernel: [300981.080213][T22543] kexec: page allocation failure: order:4, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 2024-05-17T03:32:50.552957+02:00 unreal6 kernel: [300981.093661][T22543] CPU: 5 PID: 22543 Comm: kexec Tainted: G n 6.4.0-150600.17-default #1 SLE15-SP6 8d7122a8d4d10b24a1d15f496e70a80423123bfb 2024-05-17T03:32:50.686496+02:00 unreal6 kernel: [300981.107928][T22543] Hardware name: Supermicro X10SLD-F/HF/X10SLD, BIOS 3.2 05/10/2018 2024-05-17T03:32:50.686507+02:00 unreal6 kernel: [300981.107930][T22543] Call Trace: 2024-05-17T03:32:50.686508+02:00 unreal6 kernel: [300981.107932][T22543] <TASK> 2024-05-17T03:32:50.686509+02:00 unreal6 kernel: [300981.107936][T22543] dump_stack_lvl+0x44/0x60 2024-05-17T03:32:50.686509+02:00 unreal6 kernel: [300981.107942][T22543] warn_alloc+0x116/0x190 2024-05-17T03:32:50.686521+02:00 unreal6 kernel: [300981.107946][T22543] __alloc_pages_slowpath.constprop.76+0xd21/0xda0 2024-05-17T03:32:50.686522+02:00 unreal6 kernel: [300981.107949][T22543] ? mas_alloc_nodes+0x58/0x200 2024-05-17T03:32:50.686523+02:00 unreal6 kernel: [300981.142000][T22543] __alloc_pages+0x306/0x350 2024-05-17T03:32:50.686523+02:00 unreal6 kernel: [300981.142018][T22543] ? privcmd_buf_mmap+0x40/0x140 [xen_privcmd 934db45836cbae60a50a9c21606f8d0a484d9c16] 2024-05-17T03:32:50.686524+02:00 unreal6 kernel: [300981.142021][T22543] __kmalloc_large_node+0x7a/0x140 2024-05-17T03:32:50.686525+02:00 unreal6 kernel: [300981.142023][T22543] __kmalloc+0xbe/0x130 2024-05-17T03:32:50.686532+02:00 unreal6 kernel: [300981.142025][T22543] privcmd_buf_mmap+0x40/0x140 [xen_privcmd 934db45836cbae60a50a9c21606f8d0a484d9c16] 2024-05-17T03:32:50.686535+02:00 unreal6 kernel: [300981.142027][T22543] mmap_region+0x26c/0xa70 2024-05-17T03:32:50.686535+02:00 unreal6 kernel: [300981.179256][T22543] do_mmap+0x3c4/0x550 2024-05-17T03:32:50.686536+02:00 unreal6 kernel: [300981.179262][T22543] vm_mmap_pgoff+0xe1/0x1a0 2024-05-17T03:32:50.686537+02:00 unreal6 kernel: [300981.179266][T22543] ksys_mmap_pgoff+0x1a1/0x1e0 2024-05-17T03:32:50.686537+02:00 unreal6 kernel: [300981.179268][T22543] do_syscall_64+0x5b/0x80 2024-05-17T03:32:50.686538+02:00 unreal6 kernel: [300981.179271][T22543] ? syscall_exit_to_user_mode+0x1e/0x40 2024-05-17T03:32:50.686547+02:00 unreal6 kernel: [300981.179273][T22543] ? do_syscall_64+0x67/0x80 2024-05-17T03:32:50.686549+02:00 unreal6 kernel: [300981.179274][T22543] ? irq_exit_rcu+0x40/0xc0 2024-05-17T03:32:50.686550+02:00 unreal6 kernel: [300981.211457][T22543] ? xen_pv_evtchn_do_upcall+0x8f/0xa0 2024-05-17T03:32:50.686550+02:00 unreal6 kernel: [300981.211471][T22543] entry_SYSCALL_64_after_hwframe+0x77/0xe1 2024-05-17T03:32:50.686551+02:00 unreal6 kernel: [300981.211474][T22543] RIP: 0033:0x7ff96012a5f2 2024-05-17T03:32:50.686552+02:00 unreal6 kernel: [300981.227143][T22543] Code: 90 90 90 90 90 90 90 90 41 f7 c1 ff 0f 00 00 75 27 55 89 cd 53 48 89 fb 48 85 ff 74 3b 41 89 ea 48 89 df b8 09 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 76 5b 5d c3 0f 1f 00 48 8b 05 f9 47 0d 00 64 2024-05-17T03:32:50.686558+02:00 unreal6 kernel: [300981.227145][T22543] RSP: 002b:00007fffe14c8538 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 2024-05-17T03:32:50.686559+02:00 unreal6 kernel: [300981.227157][T22543] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff96012a5f2 2024-05-17T03:32:50.686559+02:00 unreal6 kernel: [300981.227158][T22543] RDX: 0000000000000003 RSI: 00000000012ea000 RDI: 0000000000000000 2024-05-17T03:32:50.686560+02:00 unreal6 kernel: [300981.227159][T22543] RBP: 0000000000000001 R08: 0000000000000004 R09: 0000000000000000 2024-05-17T03:32:50.686561+02:00 unreal6 kernel: [300981.227159][T22543] R10: 0000000000000001 R11: 0000000000000246 R12: 00000000000012ea 2024-05-17T03:32:50.686561+02:00 unreal6 kernel: [300981.227160][T22543] R13: 000055d5af63eb20 R14: 000055d5af63f480 R15: 000055d5af63fa80 2024-05-17T03:32:50.686566+02:00 unreal6 kernel: [300981.227163][T22543] </TASK> 2024-05-17T03:32:50.686576+02:00 unreal6 kernel: [300981.227246][T22543] Mem-Info: 2024-05-17T03:32:50.806334+02:00 unreal6 kernel: [300981.301023][T22543] active_anon:27322 inactive_anon:41870 isolated_anon:0 2024-05-17T03:32:50.806343+02:00 unreal6 kernel: [300981.301023][T22543] active_file:26410 inactive_file:35814 isolated_file:0 2024-05-17T03:32:50.806344+02:00 unreal6 kernel: [300981.301023][T22543] unevictable:16761 dirty:196 writeback:0 2024-05-17T03:32:50.806345+02:00 unreal6 kernel: [300981.301023][T22543] slab_reclaimable:22564 slab_unreclaimable:25083 2024-05-17T03:32:50.806365+02:00 unreal6 kernel: [300981.301023][T22543] mapped:15869 shmem:1831 pagetables:5681 2024-05-17T03:32:50.806368+02:00 unreal6 kernel: [300981.301023][T22543] sec_pagetables:0 bounce:0 2024-05-17T03:32:50.806368+02:00 unreal6 kernel: [300981.301023][T22543] kernel_misc_reclaimable:0 2024-05-17T03:32:50.806369+02:00 unreal6 kernel: [300981.301023][T22543] free:11073 free_pcp:149 free_cma:0 2024-05-17T03:32:50.806370+02:00 unreal6 kernel: [300981.301027][T22543] Node 0 active_anon:109288kB inactive_anon:167480kB active_file:105640kB inactive_file:143256kB unevictable:67044kB isolated(anon):0kB isolated(file):0kB mapped:63476kB dirty:784kB writeback:0kB shmem:7324kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:10260kB pagetables:22724kB sec_pagetables:0kB all_unreclaimable? no 2024-05-17T03:32:50.806370+02:00 unreal6 kernel: [300981.301030][T22543] Node 0 DMA free:3464kB boost:0kB min:64kB low:80kB high:96kB reserved_highatomic:0KB active_anon:1056kB inactive_anon:1960kB active_file:1272kB inactive_file:1300kB unevictable:12kB writepending:0kB present:15968kB managed:15908kB mlocked:12kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 2024-05-17T03:32:50.806377+02:00 unreal6 kernel: [300981.301034][T22543] lowmem_reserve[]: 0 849 849 849 849 2024-05-17T03:32:50.806378+02:00 unreal6 kernel: [300981.301036][T22543] Node 0 DMA32 free:40828kB boost:0kB min:3696kB low:4620kB high:5544kB reserved_highatomic:2048KB active_anon:108348kB inactive_anon:165472kB active_file:104448kB inactive_file:141932kB unevictable:67032kB writepending:720kB present:1032604kB managed:898080kB mlocked:63960kB bounce:0kB free_pcp:600kB local_pcp:0kB free_cma:0kB 2024-05-17T03:32:50.806379+02:00 unreal6 kernel: [300981.301040][T22543] lowmem_reserve[]: 0 0 0 0 0 2024-05-17T03:32:50.908415+02:00 unreal6 load.sh[22543]: xencall: error: alloc_pages: mmap (,4842*4096,...) [bufdev] failed: Cannot allocate memory 2024-05-17T03:32:50.908545+02:00 unreal6 load.sh[22543]: kexec_load failed: Cannot allocate memory 2024-05-17T03:32:50.908589+02:00 unreal6 load.sh[22543]: entry = 0x41a49f740 flags = 0x3e0001 2024-05-17T03:32:50.908627+02:00 unreal6 load.sh[22543]: nr_segments = 7 2024-05-17T03:32:50.908663+02:00 unreal6 load.sh[22543]: segment[0].buf = 0x55d5af5902a0 2024-05-17T03:32:50.908695+02:00 unreal6 load.sh[22543]: segment[0].bufsz = 0x30 2024-05-17T03:32:50.908729+02:00 unreal6 load.sh[22543]: segment[0].mem = 0x40d346000 2024-05-17T03:32:50.908762+02:00 unreal6 load.sh[22543]: segment[0].memsz = 0x1000 2024-05-17T03:32:50.908796+02:00 unreal6 load.sh[22543]: segment[1].buf = 0x7ff95df8d010 2024-05-17T03:32:50.908831+02:00 unreal6 load.sh[22543]: segment[1].bufsz = 0x12e94dc 2024-05-17T03:32:50.908863+02:00 unreal6 load.sh[22543]: segment[1].mem = 0x415716000 2024-05-17T03:32:50.908908+02:00 unreal6 load.sh[22543]: segment[1].memsz = 0x12ea000 2024-05-17T03:32:50.908944+02:00 unreal6 load.sh[22543]: segment[2].buf = 0x7ff95f27b010 2024-05-17T03:32:50.908978+02:00 unreal6 load.sh[22543]: segment[2].bufsz = 0xd841e0 2024-05-17T03:32:50.909013+02:00 unreal6 load.sh[22543]: segment[2].mem = 0x416a00000 2024-05-17T03:32:50.909048+02:00 unreal6 load.sh[22543]: segment[2].memsz = 0x39d8000 2024-05-17T03:32:50.909086+02:00 unreal6 load.sh[22543]: segment[3].buf = 0x55d5af63a7c0 2024-05-17T03:32:50.909119+02:00 unreal6 load.sh[22543]: segment[3].bufsz = 0x4121 2024-05-17T03:32:50.909148+02:00 unreal6 load.sh[22543]: segment[3].mem = 0x41a49a000 2024-05-17T03:32:50.909179+02:00 unreal6 load.sh[22543]: segment[3].memsz = 0x5000 2024-05-17T03:32:50.909210+02:00 unreal6 load.sh[22543]: segment[4].buf = 0x55d5af6334b0 2024-05-17T03:32:50.909241+02:00 unreal6 load.sh[22543]: segment[4].bufsz = 0x70e0 2024-05-17T03:32:50.909272+02:00 unreal6 load.sh[22543]: segment[4].mem = 0x41a49f000 2024-05-17T03:32:50.909346+02:00 unreal6 kernel: [300981.301042][T22543] Node 0 DMA: 40*4kB (UME) 29*8kB (UME) 36*16kB (UE) 14*32kB (UME) 4*64kB (UME) 4*128kB (UE) 3*256kB (U) 1*512kB (U) 0*1024kB 0*2048kB 0*4096kB = 3464kB 2024-05-17T03:32:50.909351+02:00 unreal6 kernel: [300981.448605][T22543] Node 0 DMA32: 7108*4kB (UMEH) 1421*8kB (UMEH) 50*16kB (UMH) 3*32kB (H) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 40696kB 2024-05-17T03:32:50.909364+02:00 unreal6 kernel: [300981.448612][T22543] 72778 total pagecache pages 2024-05-17T03:32:50.909367+02:00 unreal6 kernel: [300981.448613][T22543] 4164 pages in swap cache 2024-05-17T03:32:50.909368+02:00 unreal6 kernel: [300981.448614][T22543] Free swap = 1067936kB 2024-05-17T03:32:50.909369+02:00 unreal6 kernel: [300981.448614][T22543] Total swap = 2099648kB 2024-05-17T03:32:50.909375+02:00 unreal6 kernel: [300981.448615][T22543] 262143 pages RAM 2024-05-17T03:32:50.909376+02:00 unreal6 kernel: [300981.448616][T22543] 0 pages HighMem/MovableOnly 2024-05-17T03:32:50.909382+02:00 unreal6 kernel: [300981.448616][T22543] 33646 pages reserved 2024-05-17T03:32:50.909383+02:00 unreal6 kernel: [300981.448617][T22543] 0 pages cma reserved 2024-05-17T03:32:50.909384+02:00 unreal6 kernel: [300981.448617][T22543] 0 pages hwpoisoned 2024-05-17T03:32:50.909328+02:00 unreal6 load.sh[22543]: segment[4].memsz = 0x9000 2024-05-17T03:32:50.909407+02:00 unreal6 load.sh[22543]: segment[5].buf = 0x55d5af6315e0 2024-05-17T03:32:50.909444+02:00 unreal6 load.sh[22543]: segment[5].bufsz = 0x800 2024-05-17T03:32:50.909475+02:00 unreal6 load.sh[22543]: segment[5].mem = 0x41a4a8000 2024-05-17T03:32:50.909505+02:00 unreal6 load.sh[22543]: segment[5].memsz = 0x4000 2024-05-17T03:32:50.909537+02:00 unreal6 load.sh[22543]: segment[6].buf = 0x55d5af5979d0 2024-05-17T03:32:50.909568+02:00 unreal6 load.sh[22543]: segment[6].bufsz = 0x99c00 2024-05-17T03:32:50.909596+02:00 unreal6 load.sh[22543]: segment[6].mem = 0x41a4ac000 2024-05-17T03:32:50.909625+02:00 unreal6 load.sh[22543]: segment[6].memsz = 0x9a000 2024-05-17T03:32:50.912398+02:00 unreal6 load.sh[18867]: kexec failed. 2024-05-17T03:32:50.916526+02:00 unreal6 systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION 2024-05-17T03:32:50.916594+02:00 unreal6 systemd[1]: kdump.service: Failed with result 'exit-code'. 2024-05-17T03:32:50.941787+02:00 unreal6 systemd[1]: Failed to start Load kdump kernel and initrd. 2024-05-17T03:32:50.942145+02:00 unreal6 systemd[1]: kdump.service: Consumed 20.770s CPU time. 2024-05-17T03:32:50.978629+02:00 unreal6 sh[18901]: .. 2024-05-17T03:32:50.978699+02:00 unreal6 sh[18901]: Job for kdump.service failed because the control process exited with error code. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1225703] New: can't add wlan0 to bridge br0: Operation not supported
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225703 Bug ID: 1225703 Summary: can't add wlan0 to bridge br0: Operation not supported Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- brctl addif br0 wlan0 can't add wlan0 to bridge br0: Operation not supported Since when is bridging WiFi broken? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 30 May '24

30 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Axel Braun from comment #7) > > Also, it might be worth to check whether it's a kernel regression. You can > > try older kernels in my OBS repos, e.g. home:tiwai:kernel:6.6 for 6.6.x > > kernel > > Currently running your 6.6.11 kernel and did not see the behaviour so far. Interesting. Try 6.7.x and 6.8.x to narrow down the regression range, if it's indeed a regression. It'll help for identifying the cause. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 30 May '24

30 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c7 --- Comment #7 from Axel Braun <axel.braun(a)gmx.de> --- Hello Takashi (In reply to Takashi Iwai from comment #6) > So it seems that BAT0 reports a wrong value from the beginning even before > the suspend. And it's a generic ACPI battery stuff, the most suspected is a > BIOS firmware bug. Well, the BIOS did not change..... > But you can try to report to the upstream, e.g. bugzilla.kernel.org. Done: https://bugzilla.kernel.org/show_bug.cgi?id=218915 > Also, it might be worth to check whether it's a kernel regression. You can > try older kernels in my OBS repos, e.g. home:tiwai:kernel:6.6 for 6.6.x > kernel Currently running your 6.6.11 kernel and did not see the behaviour so far. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223544] kernel config: enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223544 https://bugzilla.suse.com/show_bug.cgi?id=1223544#c3 Coly Li <colyli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |colyli(a)suse.com Flags|needinfo?(hare(a)suse.com) | --- Comment #3 from Coly Li <colyli(a)suse.com> --- Let me handle this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c13 --- Comment #13 from P Gillespie <millstonepoet(a)gmail.com> --- This bug is still very much alive and makes any 6.x kernel unusable on various models of the MS Surface, including mine (on which I'm writing this). It's no longer possible to install TW on my model of the Surface. I haven't checked recently, but Kernel maintainers have been aware of the bug for years and have done nothing to solve it (there are many other reports). They've decided to ignore it. As you say, it's an upstream problem. Since I've locked my kernel version at 5.13.x, I haven't had any problems. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1137748 https://bugzilla.suse.com/show_bug.cgi?id=1137748#c145 --- Comment #145 from Biswarup Ray <biswarupr(a)gmail.com> --- (In reply to Jiri Slaby from comment #143) > (In reply to Biswarup Ray from comment #142) > > I am still facing the same problem only when I am using Opensuse. Suspend is > > working perfectly in all other distros including Gecko. How can I file bug > > with upstream? > > OK, what distribution (show /etc/os-release output) and kernel version > (uname -r output) do you use which does not work. And what distro (fedora? > ubuntu? -- /etc/os-release) with what kernel works (uname -r)? ok, I am posting this comment using Ubuntu 24.04LTS live-usb.Suspend to ram is not only working, it is working extremely fast. ubuntu@ubuntu:~$ uname -r 6.8.0-31-generic -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1137748 https://bugzilla.suse.com/show_bug.cgi?id=1137748#c144 --- Comment #144 from Biswarup Ray <biswarupr(a)gmail.com> --- (In reply to Jiri Slaby from comment #143) > (In reply to Biswarup Ray from comment #142) > > I am still facing the same problem only when I am using Opensuse. Suspend is > > working perfectly in all other distros including Gecko. How can I file bug > > with upstream? > > OK, what distribution (show /etc/os-release output) and kernel version > (uname -r output) do you use which does not work. And what distro (fedora? > ubuntu? -- /etc/os-release) with what kernel works (uname -r)? I am using the latest tumbleweed snapshot(I just updated). uname -r 6.9.1-1-default I have run many distros on this desktop and I have never faced this problem. I will download and run the latest ubuntu live-usb and report back to you later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1137748 https://bugzilla.suse.com/show_bug.cgi?id=1137748#c143 --- Comment #143 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Biswarup Ray from comment #142) > I am still facing the same problem only when I am using Opensuse. Suspend is > working perfectly in all other distros including Gecko. How can I file bug > with upstream? OK, what distribution (show /etc/os-release output) and kernel version (uname -r output) do you use which does not work. And what distro (fedora? ubuntu? -- /etc/os-release) with what kernel works (uname -r)? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1137748 https://bugzilla.suse.com/show_bug.cgi?id=1137748#c142 Biswarup Ray <biswarupr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #142 from Biswarup Ray <biswarupr(a)gmail.com> --- I am still facing the same problem only when I am using Opensuse. Suspend is working perfectly in all other distros including Gecko. How can I file bug with upstream? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1173891] BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1173891 https://bugzilla.suse.com/show_bug.cgi?id=1173891#c8 --- Comment #8 from Richard Weinberger <richard(a)nod.at> --- The device in question died. No need to investigate further. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206864] Direct Rendering Manager trouble upon resume from suspend to RAM
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1206864 https://bugzilla.suse.com/show_bug.cgi?id=1206864#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM Flags|needinfo?(karl.mistelberger | |(a)nefkom.net) | --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- They write in the linked issue: https://gitlab.freedesktop.org/drm/amd/-/issues/3017 === This seems to be fixed for me with kernel 6.7 (specifically Fedora kernel 6.7.4-200.fc39.x86_64). === So hopefully fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191583] iwlwifi queue stuck for 10000ms
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1191583 https://bugzilla.suse.com/show_bug.cgi?id=1191583#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|NEW |RESOLVED --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207355] Battery drain despite shutdown...
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1207355 https://bugzilla.suse.com/show_bug.cgi?id=1207355#c12 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME CC| |jslaby(a)suse.com Flags|needinfo?(millstonepoet@gma | |il.com) | Status|NEW |RESOLVED --- Comment #12 from Jiri Slaby <jslaby(a)suse.com> --- You forgot to remove the needinfo flag. This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207259] BananaPi no HDMI output with kernel 6.0.3+, 6.1.1+ fails to boot
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1207259 https://bugzilla.suse.com/show_bug.cgi?id=1207259#c11 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(peter_haak_otd@we | |b.de) | Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #11 from Jiri Slaby <jslaby(a)suse.com> --- You did not remove the needinfo flag. This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190461] loading initial ramdisk 5.14
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1190461 https://bugzilla.suse.com/show_bug.cgi?id=1190461#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190027] ima: Can not allocate sha384 (reason: -2)
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1190027 https://bugzilla.suse.com/show_bug.cgi?id=1190027#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|NEW |RESOLVED --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185649] [Build 20210504] openQA test fails in kdump_and_crash
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1185649 https://bugzilla.suse.com/show_bug.cgi?id=1185649#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- So closing in a hope this got fixed. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207347] Webcam not working in Lenovo T14 gen 1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1207347 https://bugzilla.suse.com/show_bug.cgi?id=1207347#c13 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |WONTFIX Flags|needinfo?(paolabonacini@vir | |gilio.it) | --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- OK then closing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c19 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC| |jslaby(a)suse.com --- Comment #19 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206926] process exit status not set by leader thread, when all threads exit using SYS_exit
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1206926 https://bugzilla.suse.com/show_bug.cgi?id=1206926#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM CC| |jslaby(a)suse.com Status|NEW |RESOLVED --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- This was fixed in gdb tests. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1173891] BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1173891 https://bugzilla.suse.com/show_bug.cgi?id=1173891#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|NEW |RESOLVED --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1166406] Consider moving /boot/vmlinux-*.xz to a different package
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1166406 https://bugzilla.suse.com/show_bug.cgi?id=1166406#c43 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #43 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Michal Suchanek from comment #42) > - moving vmlinux into separate package is possible (on non-ppc) provided > tools that assume vmlinux is present are fixed up (there are some additional > binaries used exclusively for debugging - eg. the s390 boot stub, vdso?) > - some of these tools are something like debug tools or performance > measurement tools that can be fixed up as problems are found > - some of these tools may be part of basesystem and it is critical that > they work from the start on all platforms > - complex dependencies can be used to fix up debug package installation > on SLE15, on SLE12 this cannot be reasonably expected to work. Anyone is invited to do the work. Until then, closing as WONTFIX as this is hanging here for years, sorry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1177800] [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1177800 https://bugzilla.suse.com/show_bug.cgi?id=1177800#c7 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1137748 https://bugzilla.suse.com/show_bug.cgi?id=1137748#c141 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED CC| |jslaby(a)suse.com --- Comment #141 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202825] Haswell Laptop Completely Freezes After Waking up from Suspend
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1202825 https://bugzilla.suse.com/show_bug.cgi?id=1202825#c14 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME CC| |jslaby(a)suse.com --- Comment #14 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200461] Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1200461 https://bugzilla.suse.com/show_bug.cgi?id=1200461#c72 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(kernel-bugs@suse. | |de), | |needinfo?(mfdemicco(a)gmail.c | |om) | --- Comment #72 from Jiri Slaby <jslaby(a)suse.com> --- NEEDINFO never cleared. Closing as this is rather old. If this still happens, feel free to reopen. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189946] [trackerbug] Ancient patch cleanup
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1189946 Bug 1189946 depends on bug 1189970, which changed state. Bug 1189970 Summary: cleanup: remove or document patches.suse/scsi-retry-alua-transition-in-progress https://bugzilla.suse.com/show_bug.cgi?id=1189970 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225561] New: Add extra modules to kernel-kvmsmall
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225561 Bug ID: 1225561 Summary: Add extra modules to kernel-kvmsmall 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: daan.j.demeyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, we'd like to use kernel-kvmsmall to run systemd's integration test suite instead of kernel-default. However, there's a few missing modules. Could these be added to kernel-kvmsmall? - CONFIG_DUMMY - CONFIG_NVME_TARGET_TCP -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1223544] New: kernel config: enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG
by bugzilla_noreply＠suse.com 29 May '24

29 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223544 Bug ID: 1223544 Summary: kernel config: enable CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Systemd wants to have CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG to enable signed Verity images: https://github.com/systemd/systemd/blob/main/README#L131 Any chance we can enable that (and potentially other settings we missed) in TW kernels to leverage systemd's full potential? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1225352] [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 28 May '24

28 May '24

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 28 May '24

28 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c8 --- Comment #8 from Nikolay Borisov <nik.borisov(a)suse.com> --- This seems to be an upstream kernel issue. Would it be possible to bisect the issue using v6.4/v6.5 as good/bad respectively ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c7 --- Comment #7 from Charaf Rais <charafweb(a)gmail.com> --- on kernel 6.9 the boot hangs as always. on kernel 6.1 the system boots normally. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Just a blind shot: is there any change if you pass mitigations=off option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c5 --- Comment #5 from Charaf Rais <charafweb(a)gmail.com> --- All the thanks are for you and the community of devs active here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |nik.borisov(a)suse.com Flags|needinfo?(charafweb(a)gmail.c | |om) | --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. So it seems that the issue was introduced between 6.4.x and 6.5.x. Adding Nik and Jiri to CC, in case they know of something about the regression with intel ucode. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1214013] Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 https://bugzilla.suse.com/show_bug.cgi?id=1214013#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear, let's close for now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

27 May '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 9

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c14 --- Comment #14 from llyyr <llyyr.public(a)gmail.com> --- Gave 6.10-rc1 a shot, got a freeze within minutes. The patch still workarounds the issue though. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(llyyr.public@gmai | |l.com) | --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to llyyr from comment #12) > (In reply to Takashi Iwai from comment #11) > > OK, then please update the upstream bugtracker info accordingly. It's > > useful to know that the very latest code still suffers from the same problem. > > > 6.10-rc1 should be tagged later today, I'll give that a spin then update > upstream. Might also be worth trying out the > https://gitlab.freedesktop.org/agd5f/linux/-/tree/amd-staging-drm-next > branch? Sure, worth to try out. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c12 --- Comment #12 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #11) > OK, then please update the upstream bugtracker info accordingly. It's > useful to know that the very latest code still suffers from the same problem. > 6.10-rc1 should be tagged later today, I'll give that a spin then update upstream. Might also be worth trying out the https://gitlab.freedesktop.org/agd5f/linux/-/tree/amd-staging-drm-next branch? > Let's take the workaround temporarily for now until the upstream gets the > proper resolution. It's not ideal, but better than sorry. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- OK, then please update the upstream bugtracker info accordingly. It's useful to know that the very latest code still suffers from the same problem. Let's take the workaround temporarily for now until the upstream gets the proper resolution. It's not ideal, but better than sorry. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c10 --- Comment #10 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #9) > Just to be sure, could you try kernel-vanilla package in my OBS > home:tiwai:kernel:drm-tip repo? > > http://download.opensuse.org/repositories/home:/tiwai:/kernel:/drm-tip/ > standard/ Freezes. Only thing that helps is the patch which deletes this line https://github.com/torvalds/linux/blob/c13320499ba0efd93174ef6462ae8a7a2933… But it's definitely not ideal -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to llyyr from comment #8) > (In reply to Takashi Iwai from comment #7) > > It's a good news. At least we're heading to the right direction. > > > > I can backport the workaround patch to TW, but since the upstream got a > > significant rewrite of the relevant code, let's check whether it covers your > > problem at first. > > > > I'm building another test kernel with two upstream backports: > > 2d5bb791e24f43b6b4231b7973009987bbcc9b06 > > drm/amd/display: Implement update_planes_and_stream_v3 sequence > > d62d5551dd615f9e488b13595d69b308cd019e16 > > drm/amd/display: Backup and restore only on full updates > > > > It's being built in OBS home:tiwai:bsc1225147 repo. The package will appear > > at > > http://download.opensuse.org/repositories/home:/tiwai:/bsc1225147/standard/ > > Please give it a try later. > > > That does not resolve the issue, I can still reproduce the hard lockup. Thanks, good to know. Just to be sure, could you try kernel-vanilla package in my OBS home:tiwai:kernel:drm-tip repo? http://download.opensuse.org/repositories/home:/tiwai:/kernel:/drm-tip/stan… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c8 --- Comment #8 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #7) > It's a good news. At least we're heading to the right direction. > > I can backport the workaround patch to TW, but since the upstream got a > significant rewrite of the relevant code, let's check whether it covers your > problem at first. > > I'm building another test kernel with two upstream backports: > 2d5bb791e24f43b6b4231b7973009987bbcc9b06 > drm/amd/display: Implement update_planes_and_stream_v3 sequence > d62d5551dd615f9e488b13595d69b308cd019e16 > drm/amd/display: Backup and restore only on full updates > > It's being built in OBS home:tiwai:bsc1225147 repo. The package will appear > at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1225147/standard/ > Please give it a try later. > That does not resolve the issue, I can still reproduce the hard lockup. > Meanwhile, you can join to the upstream gitlab.freedesktop.org issues > mentioned in comment 2, echoing that the revert helped, too. I did https://gitlab.freedesktop.org/drm/amd/-/issues/3142#note_2427275 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- It's a good news. At least we're heading to the right direction. I can backport the workaround patch to TW, but since the upstream got a significant rewrite of the relevant code, let's check whether it covers your problem at first. I'm building another test kernel with two upstream backports: 2d5bb791e24f43b6b4231b7973009987bbcc9b06 drm/amd/display: Implement update_planes_and_stream_v3 sequence d62d5551dd615f9e488b13595d69b308cd019e16 drm/amd/display: Backup and restore only on full updates It's being built in OBS home:tiwai:bsc1225147 repo. The package will appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1225147/standard/ Please give it a try later. Meanwhile, you can join to the upstream gitlab.freedesktop.org issues mentioned in comment 2, echoing that the revert helped, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c6 --- Comment #6 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #5) > So the patch didn't seem helping in your case? > FWIW, it was a one-line revert mentioned in > https://gitlab.freedesktop.org/drm/amd/-/issues/3142 > > The best you can do for the moment would be to try to catch any kernel crash > or such messages and report / track the bug in the upstream > gitlab.freedesktop.org Issues. Actually that patch does work, thanks! I must've booted into the latest kernel instead of picking the one from your branch by accident when trying it out. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- So it seems that BAT0 reports a wrong value from the beginning even before the suspend. And it's a generic ACPI battery stuff, the most suspected is a BIOS firmware bug. But you can try to report to the upstream, e.g. bugzilla.kernel.org. Also, it might be worth to check whether it's a kernel regression. You can try older kernels in my OBS repos, e.g. home:tiwai:kernel:6.6 for 6.6.x kernel http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.6/standard/ Graphics or something else might be not working, but if it boots up, you can try the upower stuff to check the values without GUI, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- So the patch didn't seem helping in your case? FWIW, it was a one-line revert mentioned in https://gitlab.freedesktop.org/drm/amd/-/issues/3142 The best you can do for the moment would be to try to catch any kernel crash or such messages and report / track the bug in the upstream gitlab.freedesktop.org Issues. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c5 --- Comment #5 from Axel Braun <axel.braun(a)gmx.de> --- Created attachment 875099 --> https://bugzilla.suse.com/attachment.cgi?id=875099&action=edit upower after suspend Note that Laptop was attached to power all the time -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c4 --- Comment #4 from Axel Braun <axel.braun(a)gmx.de> --- Created attachment 875098 --> https://bugzilla.suse.com/attachment.cgi?id=875098&action=edit output of upower upower before suspend -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c4 --- Comment #4 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > Thanks. > > As a blind shot (as it's a 6.7 regression), could you try later a test > patched kernel in OBS home:tiwai:bsc1219983 repo? Once after the build > finishes, the package will appear at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1219983/standard/ Has the same issue, I get hard lockup. I'd imagine it's related to power management or gpu clocks because these crashes are very similar to what happens when you're running a very unstable overclock and you stress your system a little. Except I'm not overclocking. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 Bug ID: 1211428 Summary: Steam deck speaker is quiet. 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: --- Hi everyone, Steam deck speakers finally works in both speakers. Speaker-test works. However, I also notice the sound is quiet compared to SteamOS. Can you fix it? speaker-test -Dplughw:1,1 -c2 Linux steamdeck.lan 6.4.0-rc2-1.g679133f-default #1 SMP PREEMPT_DYNAMIC Sun May 14 21:09:47 UTC 2023 (679133f) x86_64 x86_64 x86_64 GNU/Linux LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230514 Codename: n/a -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1214013] Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 https://bugzilla.suse.com/show_bug.cgi?id=1214013#c10 --- Comment #10 from Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> --- Some update has fixed the problem, so it does not happen any more. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c3 --- Comment #3 from Charaf Rais <charafweb(a)gmail.com> --- Thank you for you reply. To give you unbiased information, I made a fresh install, update the system, installed latest ucode via "Yast Software Management" without installing gpu related drivers. I booted using "dis_ucode_ldr", and I downloaded bellow kernels from your repos, then tested them one by one: please check hwinfo in attached file. -------------------------------------------------------- kernel-default-6.1.12-1.1.g373f017.x86_64.rpm kernel-default-devel-6.1.12-1.1.g373f017.x86_64.rpm --> Boots normally! rais@192:~> sudo dmesg | grep -i microcode [sudo] password for root: [ 0.000000] [ T0] microcode: microcode updated early to revision 0xf0, date = 2021-11-12 [ 0.076111] [ T0] SRBDS: Mitigation: Microcode [ 0.505522] [ T0] microcode: sig=0x506e3, pf=0x20, revision=0xf0 [ 0.505739] [ T1] microcode: Microcode Update Driver: v2.2. -------------------------------------------------------- kernel-default-6.2.12-1.1.geb3255d.x86_64.rpm kernel-default-devel-6.2.12-1.1.geb3255d.x86_64.rpm --> Boots normally! rais@192:~> sudo dmesg | grep -i microcode [sudo] password for root: [ 0.000000] [ T0] microcode: microcode updated early to revision 0xf0, date = 2021-11-12 [ 0.078794] [ T0] SRBDS: Mitigation: Microcode [ 0.512834] [ T1] microcode: Microcode Update Driver: v2.2. -------------------------------------------------------- kernel-default-6.3.9-1.1.g0df701d.x86_64.rpm kernel-default-devel-6.3.9-1.1.g0df701d.x86_64.rpm HANGS on first boot Hangs on second boot 3d boot, I pushed "e" then F10 (without any editing) and the boot successed! 4 boot, passed without "e" + F10 5 boot Hangs 6 boot hangs 7 boot hangs even with "e" F10 trick 8 boot passed using dis_ucode_ldr 9,10 ... tested using dis_ucode_ldr , boot succeddfully evry time rais@192:~> sudo dmesg | grep -i microcode [sudo] password for root: [ 0.000000] [ T0] microcode: updated early: 0xc6 -> 0xf0, date = 2021-11-12 [ 0.078876] [ T0] SRBDS: Mitigation: Microcode [ 0.976939] [ T1] microcode: Microcode Update Driver: v2.2. -------------------------------------------------------- kernel-default-6.4.12-1.1.gf5aa89b.x86_64.rpm kernel-default-devel-6.4.12-1.1.gf5aa89b.x86_64.rpm --> Working ! rais@192:~> sudo dmesg | grep -i microcode [sudo] password for root: [ 0.000000] [ T0] microcode: updated early: 0xc6 -> 0xf0, date = 2021-11-12 [ 0.071282] [ T0] SRBDS: Mitigation: Microcode [ 0.514596] [ T1] microcode: Microcode Update Driver: v2.2. --------------------------------------------------------- kernel-default-6.5.9-1.1.g1823166.x86_64.rpm kernel-default-devel-6.5.9-1.1.g1823166.x86_64.rpm --> NOT BOOTING. -------------------------------------------------------- kernel-default-6.6.11-1.1.g05ae4ad.x86_64.rpm kernel-default-devel-6.6.11-1.1.g05ae4ad.x86_64.rpm --> Not booting -------------------------------------------------------- kernel-default-6.7.9-1.1.gc6dad0c.x86_64.rpm kernel-default-devel-6.7.9-1.1.gc6dad0c.x86_64.rpm --> Not booting --------------------------------------------------------- Kernel v 6.8 & 6.9 has been tested and they are not booting without dis_ucode_ldr. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c2 --- Comment #2 from Charaf Rais <charafweb(a)gmail.com> --- Created attachment 875081 --> https://bugzilla.suse.com/attachment.cgi?id=875081&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(llyyr.public@gmai | |l.com) CC| |llyyr.public(a)gmail.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. As a blind shot (as it's a 6.7 regression), could you try later a test patched kernel in OBS home:tiwai:bsc1219983 repo? Once after the build finishes, the package will appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1219983/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c2 --- Comment #2 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #1) > It's quite difficult to debug without any logs, unfortunately. > You can try to set up kdump and get the kernel crash dump (at least the > dmesg output), too. If it were a kernel panic, the crash dump will be > triggered automatically. Other than that, you can trigger manually via > magic sysrq-c. I bisected it down to amdgpu changes in 6.7-rc1 and reported it upstream here https://gitlab.freedesktop.org/drm/amd/-/issues/3403 Unfortunately I can't bisect it down to a specific commit because amdgpu is broken at random commits in that tree -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. And what shows "upower -d" output before and after suspend/resume? Does it indicate the same problem, right? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 https://bugzilla.suse.com/show_bug.cgi?id=1225217#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(charafweb(a)gmail.c | |om) CC| |charafweb(a)gmail.com, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- You can try the old kernels from my OBS repo, e.g. home:tiwai:kernel:6.1 http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.1/standard/ Could you confirm whether it starts breaking since 6.2.x and 6.1.x works with the very same intel ucode? Also, please give the hwinfo output. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225217] New: OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225217 Bug ID: 1225217 Summary: OpenSUSE TW won’t boot without the “dis_ucode_ldr” parameter 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: charafweb(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My specs: CPU i7 6700HQ, Nvidia Geforce 960M, 4k Screen, 16GB RAM, 512GB SSD, and 2TB HDD (ASUS Laptop N552V). OpenSUSE TW won’t boot without the “dis_ucode_ldr” kernel boot parameter. I removed the “quiet” boot kernel parameter to get error output, but unfortunately, nothing shows up; the boot process stops very early. Even on a fresh install with default open-source drivers, I’m facing the same issue. So, it doesn’t seem to be related to the Nvidia drivers. In fact, openSUSE boots without any issues the first time because the Intel microcode isn’t installed. But once it’s installed, the boot process hangs. I’ve tried several rolling distros that use version 6 kernels, they all present the same problem. Only kernel 6.1.x seems to work with Intel-ucode (tested in Manjaro). OpenSUSE Leap (kernel v. 5.x) works fine even when installing ucode. So, I thought the issue might be with the ucode for TW. I tried copying the microcode file (06-5e-03) from Leap and replacing the one in TW, following successfully all the necessary steps to install it manually, but the boot process continues to hang with no output. Microcode code for i7 6700HQ is not updated anymore, the latest version is microcode-20220510. It’s possible that something broke with kernel versions above 6.1. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- It's quite difficult to debug without any logs, unfortunately. You can try to set up kdump and get the kernel crash dump (at least the dmesg output), too. If it were a kernel panic, the crash dump will be triggered automatically. Other than that, you can trigger manually via magic sysrq-c. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225159] New: OpenSUSE installation support for RZ/G3S and RZ/V2H
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225159 Bug ID: 1225159 Summary: OpenSUSE installation support for RZ/G3S and RZ/V2H 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: john.vincent.xa(a)bp.renesas.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, Please enable Renesas RZ/V2H & RZ/G3S SOM device support in openSUSE by updating the following configurations in "config/arm64/default" file CONFIG_ARCH_R9A09G057=y #RZ/V2H CONFIG_ARCH_R9A08G045=y #RZ/G3S Best Regards John -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1219132] New: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 Bug ID: 1219132 Summary: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889391/modules/Sysc tl/steps/136 OS: Other Status: NEW Severity: Normal 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 # Test messages # Sysctl_kernel_sched_energy_aware # failure: ValueError: invalid literal for int() with base 10: '' Possibly this is a kernel issue - possibly the kernel just no longer exposes this and the test should not care. Please advise openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sys-param-check@64bit fails in [Sysctl](https://openqa.opensuse.org/tests/3889391/modules/Sysctl/steps/136) ## Test suite description RAM size is set to 2048, some kernel parameters change with total RAM https://github.com/openSUSE/sys-param-check ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888589) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886345) (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 1

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c2 Axel Braun <axel.braun(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(axel.braun(a)gmx.de | |) | --- Comment #2 from Axel Braun <axel.braun(a)gmx.de> --- Created attachment 875060 --> https://bugzilla.suse.com/attachment.cgi?id=875060&action=edit hwinfo -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223025] CPU soft lockup when suspending
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223025 https://bugzilla.suse.com/show_bug.cgi?id=1223025#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(badshah400@gmail. | |com) CC| |badshah400(a)gmail.com, | |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- TW is moving to 6.9.x already. Could you check the latest kernel in OBS Kernel:stable repo and see whether the problem persists? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 https://bugzilla.suse.com/show_bug.cgi?id=1223194#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(axel.braun(a)gmx.de | |) CC| |axel.braun(a)gmx.de, | |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you give hwinfo output? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225147] New: Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 Bug ID: 1225147 Summary: Kernel hard lockup under mild GPU load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: llyyr.public(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: Randomly get hard lockups with no errors or dmesg logs, can't ssh into the system either. Reproducible: Always Steps to Reproduce: 1. Record the screen with vaapi encoding on amdgpu Actual Results: Kernel hard lockup some time after 5-30 minutes Expected Results: System should be stable With i5-13600k and RX 6600 XT. I'm running sway and the screen recording tool doesn't matter as long as it's using vaapi encoding. The Mesa version also doesn't matter. This happens on Kernel versions 6.7 or newer, I just tried 6.9.1 and can reproduce it there as well. It does not happen on 6.6.x. I'm currently running 6.6.31-lts. I'd go ahead and bisect the kernel but I'm not sure how to build and install the kernel in a way that it appears in the grub menu. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224769] Update failure
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224769 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(gfbraff@wolfenet. | |com) CC| |gfbraff(a)wolfenet.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1225142] New: Kernel oops in nfs
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225142 Bug ID: 1225142 Summary: Kernel oops in nfs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875055 --> https://bugzilla.suse.com/attachment.cgi?id=875055&action=edit Kernel oops log As I already mentioned in bug 1223640 I'm getting oops in NFS (see the attached log) It happens in both kernel-default-5.14.21-150500.55.59.1.x86_64 kernel-default-5.14.21-150500.55.62.2.x86_64 Until and including the previous one it's been fine: kernel-default-5.14.21-150500.55.52.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1221512] scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 https://bugzilla.suse.com/show_bug.cgi?id=1221512#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |screening-team-bugs(a)suse.de --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- At best ping on OBS or ask via mail. Unfortunately the package maintainer of sane-airscan doesn't seem registered on Bugzilla, so we can't assign it to him. I noticed, though, that sane-airscan package seems pretty new. Didn't the system work after you uninstall that package? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221512] scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 https://bugzilla.suse.com/show_bug.cgi?id=1221512#c3 David Walker <David(a)WalkerStreet.info> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #3 from David Walker <David(a)WalkerStreet.info> --- Good question. I don't do a lot of scanning, so I don't remember the last time I could scan successfully, but I tried kernels 6.8.7-1-default and 6.8.4-rc1-1-default, and both had the same problem. So, I did a little searching and found that there is a sane-airscan-unstable in home:pzz. I installed it, and scanning works again. Can this report be reassigned to get the version of sane-airscan in Tumbleweed updated? Also, there's no aarch64 build, and I normally do my scanning from a Raspberry Pi 4 system, so aarch64 would be greatly appreciated. (I can report either or both of these separately, if that's better.) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224808] dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224808 https://bugzilla.suse.com/show_bug.cgi?id=1224808#c8 --- Comment #8 from Frederic Crozat <fcrozat(a)suse.com> --- It was also broken with kernel 6.8.9 on MicroOS -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224808] dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224808 https://bugzilla.suse.com/show_bug.cgi?id=1224808#c7 --- Comment #7 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Observed: > [ 1.415049] localhost kernel: BTRFS: device label ROOT devid 1 transid 65 /dev/vda3 (254:3) scanned by mount (450) > [ 1.415283] localhost kernel: BTRFS info (device vda3): first mount of filesystem 0ccd61f9-7e1a-4329-9b48-04673b6ba623 > [ 1.415292] localhost kernel: BTRFS info (device vda3): using crc32c (crc32c-intel) checksum algorithm > [ 1.415295] localhost kernel: BTRFS info (device vda3): using free-space-tree > [ 1.757878] localhost systemd[1]: Switching root. > [ 2.935997] localhost kernel: BTRFS info (device vda3 state M): use zstd compression, level 1 > ... > [ 3.179772] localhost systemd[1]: Mounting /.snapshots... > [ 3.180726] localhost kernel: BTRFS info (device vda3 state M): use compression, level 0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224808] dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224808 https://bugzilla.suse.com/show_bug.cgi?id=1224808#c6 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dracut-maintainers(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #6 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Antonio Feijoo from comment #5) > But, I'm testing this with SL Micro, I'll download the latest MicroOS > snapshot later and check if I can reproduce it. Ok, my bad, I should've tested this with MicroOS since the beginning, I can reproduce it with snapshot 20240520. > localhost:~ # grep -m1 compress= /proc/self/mountinfo > 64 1 0:36 /(a)/.snapshots/2/snapshot / ro,relatime shared:1 - btrfs /dev/vda3 rw,seclabel,compress=,discard=async,space_cache=v2,subvolid=268,subvol=/(a)/.snapshots/2/snapshot There was not any change in dracut that could affect this between the version shipped with SL Micro and the latest Factory version, and the arguments in dracut look ok: > May 22 13:05:43 localhost dracut-cmdline[233]: dracut-059+suse.588.g528264be-1.1 > May 22 13:05:43 localhost dracut-cmdline[233]: Using kernel command line parameters: ... rootfstype=btrfs rootflags=ro,compress=zstd:1 ... Also, `findmnt` reports the right options on the running system: > localhost:~ # findmnt --fstab -e -v -n -o 'OPTIONS' --target / ro,compress=zstd:1 But, /proc/self/mountinfo trims the value of compress=... So, I guess this should be an issue with kernel 6.9.1-1-default (it works with 6.4.0-17-default). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224368] New: RCU not on for: amd_e400_idle+0x4/0x30
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224368 Bug ID: 1224368 Summary: RCU not on for: amd_e400_idle+0x4/0x30 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: wegao(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- run opensuse-Tumbleweed-x86_64-20240514-DVD(a)64bit-with-ltp.qcow2 with following qemu parameter. qemu-system-x86_64 -smp cores=4 -m 1024 -s -nodefaults -device virtio-rng-pci -nographic -serial mon:stdio -display none \ -drive file=$1,if=virtio \ -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp::5555-:22 susetest:/sys/kernel/debug/tracing # echo function_graph > current_tracer [ 271.226973][ T0] ------------[ cut here ]------------ [ 271.229804][ T0] RCU not on for: amd_e400_idle+0x4/0x30 [ 271.229804][ T0] WARNING: CPU: 0 PID: 0 at include/linux/trace_recursion.h:162 prepare_ftrace_return+0x15e/0x170 [ 271.229804][ T0] Modules linked in: joydev st sr_mod cdrom nls_iso8859_1 nls_cp437 exfat vfat fat bcachefs lz4_compress lz4hc_compress xfs ext4 mbcacg [ 271.229804][ T0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.9-1-default #1 openSUSE Tumbleweed bdefa5c8548782cd7f40c96ed6ab2e9359be7133 [ 271.229804][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-6-gb1b30830-rebuilt.opensuse.org 04/01/2014 [ 271.229804][ T0] RIP: 0010:prepare_ftrace_return+0x15e/0x170 [ 271.229804][ T0] Code: 8b 04 25 40 a1 03 00 48 81 a0 08 23 00 00 ff ff fe ff eb a2 4c 89 e6 48 c7 c7 57 30 7b 8e c6 05 eb a6 00 02 01 e8 02 36 03 00 0 [ 271.229804][ T0] RSP: 0018:ffffffff8f003d90 EFLAGS: 00000082 [ 271.229804][ T0] RAX: 0000000000000000 RBX: ffffffff8f003e78 RCX: 0000000000000027 [ 271.229804][ T0] RDX: 00000000000a414d RSI: 0000000000000001 RDI: ffff9b67bea27800 [ 271.229804][ T0] RBP: ffffffff8f003db8 R08: 0000000000000000 R09: ffffffff8f003c38 [ 271.229804][ T0] R10: ffffffff8f003c30 R11: 0000000000000003 R12: ffffffff8d2552b4 [ 271.229804][ T0] R13: 0000000000000000 R14: ffffffff8f010980 R15: 0000000000000000 [ 271.229804][ T0] FS: 0000000000000000(0000) GS:ffff9b67bea00000(0000) knlGS:0000000000000000 [ 271.229804][ T0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 271.229804][ T0] CR2: 000055f646b2ba80 CR3: 0000000004acc000 CR4: 00000000000006f0 [ 271.229804][ T0] Call Trace: [ 271.229804][ T0] <TASK> [ 271.229804][ T0] ? prepare_ftrace_return+0x15e/0x170 [ 271.229804][ T0] ? ftrace_stub_direct_tramp+0x20/0x20 [ 271.229804][ T0] ? __warn+0x81/0x130 [ 271.229804][ T0] ? prepare_ftrace_return+0x15e/0x170 [ 271.229804][ T0] ? report_bug+0x171/0x1a0 [ 271.229804][ T0] ? handle_bug+0x3c/0x80 [ 271.229804][ T0] ? exc_invalid_op+0x17/0x70 [ 271.229804][ T0] ? asm_exc_invalid_op+0x1a/0x20 [ 271.229804][ T0] ? amd_e400_idle+0x4/0x30 [ 271.229804][ T0] ? prepare_ftrace_return+0x15e/0x170 [ 271.229804][ T0] joydev_init+0x8b/0xff0 [joydev 0a00000089e2ffff000000002000000000000000] [ 271.229804][ T0] ? amd_e400_idle+0x9/0x30 [ 271.229804][ T0] amd_e400_idle+0x9/0x30 [ 271.229804][ T0] default_idle_call+0x2c/0xe0 [ 271.229804][ T0] do_idle+0x226/0x270 [ 271.229804][ T0] cpu_startup_entry+0x2a/0x30 [ 271.229804][ T0] rest_init+0xd0/0xd0 [ 271.229804][ T0] arch_call_rest_init+0xe/0x30 [ 271.229804][ T0] start_kernel+0x70b/0xa60 [ 271.229804][ T0] x86_64_start_reservations+0x18/0x30 [ 271.229804][ T0] x86_64_start_kernel+0x96/0xa0 [ 271.229804][ T0] secondary_startup_64_no_verify+0x184/0x18b [ 271.229804][ T0] </TASK> [ 271.229804][ T0] ---[ end trace 0000000000000000 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1224457] New: Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 Bug ID: 1224457 Summary: Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrwlms(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installation of Leap 15.5 or Tumbleweed on a machine with an AMD APU on an ASUS Prime B550-Plus (uses Realtek ALC 887 for sound) results in no sound from the motherboard. This is discussed in a thread on openSuSE forums: English language, Hardware forum, "5700G+ALC887" thread title. This has been explored with aplay -l, inxi -Axx, dmesg | grep snd_hda, lsmod and modprobe. It is apparently a matter of detection of the motherboard sound "card" in the presence of the CPU's integrated sound "card". This is apparently a bug in the kernel, not openSuSE, since installation of Linux Mint on the same hardware causes exactly the same problem, including identical output from aplay -l, inxi -Axx and dmesg | grep snd_hda. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1222578] MicroOS enters emergency.target when rebooted by transactional-update
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222578 https://bugzilla.suse.com/show_bug.cgi?id=1222578#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- That sounds weird. Can you reproduce the problem by transaction-update of a single kernel package 6.8.2? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222578] MicroOS enters emergency.target when rebooted by transactional-update
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222578 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224769] Update failure
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224769 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Maintenance |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224776] make install in kernel directory adds "1.13" to distro name in grub
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224776 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Bootloader Assignee|kernel-bugs(a)opensuse.org |screening-team-bugs(a)suse.de CC| |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1223194] Empty battery reported after suspend
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223194 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224776] make install in kernel directory adds "1.13" to distro name in grub
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224776 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221512] scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 https://bugzilla.suse.com/show_bug.cgi?id=1221512#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo? --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Is it really a kernel regression? If so, booting the previous kernel (before the problem appeared) should work. If the problem persists with the old kernels, it's an issue rather in user-space. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222914] Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 https://bugzilla.suse.com/show_bug.cgi?id=1222914#c10 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- First off, try the very latest kernel in OBS Kernel:SLE15-SP5 repo: http://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/ But this is an unofficial build, hence you have to disable Secure Boot in BIOS beforehand. If it were about graphics, you can try to boot with nomodeset boot option to disable the native graphics, and you can see whether it still crashes or not. Please check it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1222914] Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1221512] scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 20 May '24

20 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 https://bugzilla.suse.com/show_bug.cgi?id=1224457#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- The behavior difference can come from a subtle thing like BIOS, so no wonder. If it were a regression, you can try the old kernels. e.g. there are tons of old kernels in my OBS projects (in "backport" repo), e.g. for 5.14, http://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.14/backpor… and you can install kernel-default.rpm from there with zypper install (or rpm -i) with --oldpackage option. Once after testing, uninstall that kernel with "zypper rm kernel-default-x.y" with the exact package version to uninstall, too. In that way, you can test old kernels until certain time. If all those don't work, you can try with the recent kernel (e.g. Leap 5.16) probing forcibly the target codec. Pass "snd_hda_intel.probe_mask=,0x101" boot option and see whether it changes the situation. (The comma before 0x101 is no typo, it's intentional.) If this doesn't work, try with 0x102, 0x104, 0x108, 0x110, until 0x180. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 20 May '24

20 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 https://bugzilla.suse.com/show_bug.cgi?id=1224457#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. It shows the error [ 6.448531] snd_hda_intel 0000:07:00.6: no codecs found! and that's the crucial error. It means that, by some reason, HD-audio controller didn't get the codec information. Possibly related with some power management stuff. Did the sound work on Leap 15.4 in the past? If it's a regression, it'd be helpful to narrow down the regression range. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 20 May '24

20 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 https://bugzilla.suse.com/show_bug.cgi?id=1224457#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(andrwlms(a)gmail.co | |m) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, then could you get alsa-info.sh output and the dmesg output on the installed Leap 15.6 system? Run alsa-info.sh with --no-upload option as root, and upload the output to Bugzilla as an attachment. Ditto for the output of dmesg, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224342] radeon: Kernel >= 6.8.9 breaks multi-user systems (multiple Xservers) running KDE
by bugzilla_noreply＠suse.com 19 May '24

19 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224342 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Kernel:Drivers Assignee|kernel-bugs(a)opensuse.org |kernel-bugs(a)suse.de -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224342] radeon: Kernel >= 6.8.9 breaks multi-user systems (multiple Xservers) running KDE
by bugzilla_noreply＠suse.com 19 May '24

19 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224342 https://bugzilla.suse.com/show_bug.cgi?id=1224342#c33 --- Comment #33 from Stefan Dirsch <sndirsch(a)suse.com> --- At no time it was obvious to me, that we have a kernel issue here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224342] radeon: Kernel >= 6.8.9 breaks multi-user systems (multiple Xservers) running KDE
by bugzilla_noreply＠suse.com 19 May '24

19 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224342 https://bugzilla.suse.com/show_bug.cgi?id=1224342#c32 --- Comment #32 from Togan Muftuoglu <toganm(a)dinamizm.com> --- (In reply to Stakanov Schufter from comment #31) > (In reply to Togan Muftuoglu from comment #30) > > (In reply to Stakanov Schufter from comment #29) > > > (In reply to Stakanov Schufter from comment #28) > > > > entropy@silversurfer:~> uname -a > > > > Linux silversurfer.fritz.box 6.8.8-1-default #1 SMP PREEMPT_DYNAMIC Mon Apr > > > > 29 05:24:46 UTC 2024 (5cd3298) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > > > > Ich habe jetzt gesehen das ich beim Booten auch 6.8.8-1-default auswählen > > > > kann. Uns siehe da, alles funktioniert, habe zwei user offen, alle Browser > > > > der Welt, benutzte Opera, FF, auf beiden, keine Crash-Orgie und keine > > > > Probleme. > > > > > > Sorry, that should have been in English. I have notice that I can select > > > during boot also 6.8.8-1-default and surprise surprise, all works O.K., two > > > users open contemporarily using firefox, opera, no crash-orgy, no problems. > > > > So looks like a kernel regression rather than Mesa issue to me. Of course > > Stefan's perspective would be more usefull than mine. > > Thank you for the time invested in this. Very appreciated. Sorry for not > having caught the reason earlier. Well, having been hit by Mesa made me cautius. At least we all know the reason now. Let's hope kernel team would find a fix soon. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224342] radeon: Kernel >= 6.8.9 breaks multi-user systems (multiple Xservers) running KDE
by bugzilla_noreply＠suse.com 19 May '24

19 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224342 https://bugzilla.suse.com/show_bug.cgi?id=1224342#c31 --- Comment #31 from Stakanov Schufter <stakanov(a)disroot.org> --- (In reply to Togan Muftuoglu from comment #30) > (In reply to Stakanov Schufter from comment #29) > > (In reply to Stakanov Schufter from comment #28) > > > entropy@silversurfer:~> uname -a > > > Linux silversurfer.fritz.box 6.8.8-1-default #1 SMP PREEMPT_DYNAMIC Mon Apr > > > 29 05:24:46 UTC 2024 (5cd3298) x86_64 x86_64 x86_64 GNU/Linux > > > > > > > > > Ich habe jetzt gesehen das ich beim Booten auch 6.8.8-1-default auswählen > > > kann. Uns siehe da, alles funktioniert, habe zwei user offen, alle Browser > > > der Welt, benutzte Opera, FF, auf beiden, keine Crash-Orgie und keine > > > Probleme. > > > > Sorry, that should have been in English. I have notice that I can select > > during boot also 6.8.8-1-default and surprise surprise, all works O.K., two > > users open contemporarily using firefox, opera, no crash-orgy, no problems. > > So looks like a kernel regression rather than Mesa issue to me. Of course > Stefan's perspective would be more usefull than mine. Thank you for the time invested in this. Very appreciated. Sorry for not having caught the reason earlier. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1224342] radeon: Kernel >= 6.8.9 breaks multi-user systems (multiple Xservers) running KDE
by bugzilla_noreply＠suse.com 19 May '24

19 May '24

1 0