May 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211117] New: 50-check-kernel-build-id fails to extract vmlinux
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211117 Bug ID: 1211117 Summary: 50-check-kernel-build-id fails to extract vmlinux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 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: --- When looking at build log from random stable kernel build I get this: [17308s] ... running 50-check-kernel-build-id [17309s] ... Verifying kernel build-ids for kernel-default 6.3.1-1.gdd8cfff s390x [17309s] ... Processing kernel rpms in '//home/abuild/rpmbuild/RPMS/s390x' [17909s] ... Unable to extract ./usr/lib/modules/6.3.1-1.gdd8cfff-default/vmlinux.xz from //home/abuild/rpmbuild/RPMS/s390x/kernel-default-debuginfo-6.3.1-1.1.gdd8cfff.s390x.rpm [17910s] Giving up vmlinux.xz is in kernel-default, not kernel-default-debuginfo. Either the message is misleading or the script is looking in the wrong place. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 18 Nov '23

18 Nov '23

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 8

[Bug 1211796] New: kernel modules not usrmerged
by bugzilla_noreply＠suse.com 25 Jul '23

25 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211796 Bug ID: 1211796 Summary: kernel modules not usrmerged 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently kernel modules are installed through compatibility symlink, and te assumed location is in /lib. Patch kmod and kernel-binary.spec.in to not rely on this symlink. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1211224] New: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK?
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211224 Bug ID: 1211224 Summary: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK? 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: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This issue is derived from boo#1211166. The openSUSE tumbleweed kernel can work with MOK for Nvidia KMP now. But in the dracut uefi_secureboot_cert case, it doesn't use shim, which means that MOK is not available. How does Nvidia RPM works with dracut solution for modsign? Even when lockdown be enabled in kernel? Does dracut uefi_secureboot_cert solution support dynamic local generated one time key? Nvidia KMP needs the solution. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1210791] New: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o
by bugzilla_noreply＠suse.com 18 Jul '23

18 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210791 Bug ID: 1210791 Summary: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Out-of-tree kernel modules can no longer be built for openSUSE:Factory:zSystems. See See https://build.opensuse.org/build/Kernel:kdump/openSUSE_Factory_zSystems/s39… [ 783s] + make -C /usr/src/linux-obj/s390x/default modules M=/home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default [ 783s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.o [ 784s] MODPOST /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/Module.symvers [ 784s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.mod.o [ 784s] LD [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko [ 784s] ld: cannot find arch/s390/lib/expoline/expoline.o: No such file or directory [ 784s] make[1]: *** [/usr/src/linux-6.2.12-1/scripts/Makefile.modfinal:61: /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko] Error 1 [ 784s] make: *** [../../../linux-6.2.12-1/Makefile:1953: modules] Error 2 [ 784s] error: Bad exit status from /var/tmp/rpm-tmp.6wzRBp (%build) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1211353] New: [Build 20230511] LTP: failure in test statx09
by bugzilla_noreply＠suse.com 13 Jul '23

13 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211353 Bug ID: 1211353 Summary: [Build 20230511] LTP: failure in test statx09 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3285771/modules/stat x09/steps/8 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 tst_kconfig.c:87: TINFO: Parsing kernel config '/proc/config.gz' tst_cmd.c:285: TINFO: Parsing mkfs.ext4 version tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1093: TINFO: Formatting /dev/loop0 with ext4 opts='-O verity' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s statx09.c:108: TBROK: ioctl(3, FS_IOC_ENABLE_VERITY) failed: EINVAL (22) tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 1... tst_device.c:412: TINFO: Likely gvfsd-trash is probing newly mounted fs, kill it to speed up tests. tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 2... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 3... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 4... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 5... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 6... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 7... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 8... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 9... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 10... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 11... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 12... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 13... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 14... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 15... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 16... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 17... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 18... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 19... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 20... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 21... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 22... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 23... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 24... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 25... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 26... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 27... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 28... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 29... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 30... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 31... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 32... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 33... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 34... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 35... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 36... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 37... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 38... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 39... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 40... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 41... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 42... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 43... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 44... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 45... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 46... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 47... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 48... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 49... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 50... tst_device.c:419: TWARN: Failed to umount('mnt_point') after 50 retries Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 tst_device.c:263: TWARN: ioctl(/dev/loop0, LOOP_CLR_FD, 0) no ENXIO for too long tst_tmpdir.c:342: TWARN: tst_rmdir: rmobj(/tmp/LTP_staCoVZgK) failed: remove(/tmp/LTP_staCoVZgK/mnt_point) failed; errno=16: EBUSY ### TEST statx09 COMPLETE >>> 6. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [statx09](https://openqa.opensuse.org/tests/3285771/modules/statx09/steps/8) ## Test suite description ## Reproducible Fails since (at least) Build [20230503](https://openqa.opensuse.org/tests/3261645) ## Expected result Last good: [20230502](https://openqa.opensuse.org/tests/3259709) (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 1211385] New: i915 disconnecting USB display causes GPU hangs and phantom display
by bugzilla_noreply＠suse.com 19 Jun '23

19 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211385 Bug ID: 1211385 Summary: i915 disconnecting USB display causes GPU hangs and phantom display 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: --- Created attachment 867010 --> https://bugzilla.suse.com/attachment.cgi?id=867010&action=edit kernel messages With external display disconnected: xrandr Screen 0: minimum 320 x 200, current 2560 x 1504, maximum 16384 x 16384 eDP-1 connected primary 2256x1504+0+0 (normal left inverted right x axis y axis) 285mm x 190mm 2256x1504 60.00*+ 48.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 59.99 59.98 59.90 59.91 1920x1200 59.88 59.95 1920x1080 60.01 59.97 59.96 59.93 1600x1200 60.00 1680x1050 59.95 59.88 1400x1050 59.98 1600x900 59.99 59.94 59.95 59.82 1280x1024 60.02 1400x900 59.96 59.88 1280x960 60.00 1440x810 60.00 59.97 1368x768 59.88 59.85 1280x800 59.99 59.97 59.81 59.91 1280x720 60.00 59.99 59.86 59.74 1024x768 60.04 60.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.95 59.96 59.90 59.82 960x600 59.93 60.00 960x540 59.96 59.99 59.63 59.82 800x600 60.00 60.32 56.25 840x525 60.01 59.88 864x486 59.92 59.57 700x525 59.98 800x450 59.95 59.82 640x512 60.02 700x450 59.96 59.88 640x480 60.00 59.94 720x405 59.51 58.99 684x384 59.88 59.85 640x400 59.88 59.98 640x360 59.86 59.83 59.84 59.32 512x384 60.00 512x288 60.00 59.92 480x270 59.63 59.82 400x300 60.32 56.34 432x243 59.92 59.57 320x240 60.05 360x202 59.51 59.13 320x180 59.84 59.32 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected 2560x1440+0+0 (normal left inverted right x axis y axis) 0mm x 0mm DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) 2560x1440 (0x7e3) 241.500MHz +HSync -VSync h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 88.79KHz v: height 1440 start 1443 end 1448 total 1481 clock 59.95Hz -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1211763] New: kernel 6.3.2-1-default AX201 Bluetooth regression: Opcode errors in dmesg
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211763 Bug ID: 1211763 Summary: kernel 6.3.2-1-default AX201 Bluetooth regression: Opcode errors in dmesg 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: draeath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My bluetooth hardware stopped working with kernel 6.3.2-1. Booting to the previously installed kernel, 6.3.1-2 (yes, not a transposition) allows it to work. The firmware file has not changed (I can't find the DDC file to check, I think it may be embedded in the SFI file) Shortly after loading firmware, the following kernel messages are printed and the bluetooth device fails to function: May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Device revision is 2 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Secure boot is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: OTP lock is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: API lock is enabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Debug lock is disabled May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Boot Address: 0x100800 May 26 19:52:29 muspelheimr kernel: Bluetooth: hci0: Firmware Version: 98-13.23 May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Waiting for firmware download to complete May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Firmware loaded in 1485331 usecs May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Waiting for device to boot May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Device booted in 15774 usecs May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Applying Intel DDC parameters completed May 26 19:52:31 muspelheimr kernel: Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562 May 26 19:52:34 muspelheimr kernel: Bluetooth: hci0: Opcode 0x204b failed: -56 May 26 19:53:10 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:53:11 muspelheimr kernel: Bluetooth: hci0: urb 00000000194e86ae failed to resubmit (113) May 26 19:53:12 muspelheimr kernel: Bluetooth: hci0: Failed to read MSFT supported features (-110) May 26 19:53:51 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:53:51 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:54:04 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:54:04 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:55:26 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:55:26 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered May 26 19:55:40 muspelheimr kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110 May 26 19:55:40 muspelheimr kernel: Bluetooth: hci0: MSFT extension not registered (repeated sequence of the "Opcode 0x c03 failed" and the MSFT extension report is due to my attempting to turn the device off/on etc). Normal logs (when it works correctly) look like this: May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Device revision is 2 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Secure boot is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: OTP lock is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: API lock is enabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Debug lock is disabled May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0040-4150.sfi May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Boot Address: 0x100800 May 13 22:02:07 muspelheimr kernel: Bluetooth: hci0: Firmware Version: 98-13.23 May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Waiting for firmware download to complete May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Firmware loaded in 1487927 usecs May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Waiting for device to boot May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Device booted in 15698 usecs May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02 May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Applying Intel DDC parameters completed May 13 22:02:08 muspelheimr kernel: Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562 USB device IDs: idVendor 0x8087 Intel Corp. idProduct 0x0026 AX201 Bluetooth Note that the MSFT error is normal and (seems to be) harmless. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211069] New: Bugged RMRR prevents PCIe Passthrough of KVM VMs on certain platforms
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211069 Bug ID: 1211069 Summary: Bugged RMRR prevents PCIe Passthrough of KVM VMs on certain platforms Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugtracker(a)fischbytes.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Build Identifier: Certain vendors that are under the assumption that standards are for jerks and Intel's specifications are a loose optional guideline have implemented RMRR in such a way that every PCI device is marked as reserved and therefore cannot be passed through to a virtual machine. This issue has been very well documented by some people that have a lot more experience than I do at the below linked resource. I was hoping that SUSE could implement the Relaxed RMRR option as an optional kernel parameter to use on these bugged platforms as that would re-enable or rather enable a lot of broken servers for the first time ever to use PCIe Passthrough. I can verify the issue exists on a HPE DL360e Gen8 with trying to passthrough a GPU to a KVM/QEMU machine. https://github.com/Aterfax/relax-intel-rmrr Reproducible: Always Steps to Reproduce: 1. Be on a bugged platform (e.g. HPE ProLiant DL360e Gen8 with latest BIOS and iLO) 2. Install the latest release of openSUSE Leap 15.4 3. Install the KVM/QEMU/Libvirt stack and passthrough a GPU to a virtual machine 4. See how the process fails with an error of "Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor." I followed the installation instructions: https://doc.opensuse.org/documentation/leap/virtualization/html/book-virtua… The issue is at a kernel-level however which means it also will not work on other platforms. Tested are Vanilla Proxmox and TrueNAS Scale. The patched Proxmox with relaxed-RMRR works(!) Actual Results: Dmesg: Device is ineligible for IOMMU domain attach due to platform RMRR requirement. Contact your platform vendor. QEMU: vfio: failed to set iommu for container: Operation not permitted Expected Results: Boot the VM with GPU Passthrough enabled. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1211856] New: Audio crackling in headphones, when two or more apps are playing audio
by bugzilla_noreply＠suse.com 31 May '23

31 May '23

https://bugzilla.suse.com/show_bug.cgi?id=1211856 Bug ID: 1211856 Summary: Audio crackling in headphones, when two or more apps are playing audio 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: erni2021(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Edg/113.0.1774.57 Build Identifier: On ROG Strix G513QR_G513QR 1.0 while using Logitech pro x wireless with USB adapter. Tumbleweed with newest updates, using pipewire. When only one app plays audio, everything seems fine, but when I open second one: for example firefix with youtube and discord, or discord and any game, the audio start to crack a lot, to the point, when I cannot hear any word properly. I was advised, that it may be issue related to a new hardware and kernel configuration and I should report it Reproducible: Always Steps to Reproduce: 1. Open any app that streams audio 2. Open second app that stream audio Actual Results: Audio in the headphones start to crack, making everything incomprehensive ASUS ROG Strix G513QR_G513QR 1.0 CPU: AMD Ryzen™ 9 5900HX GPU: NVIDIA® GeForce RTX™3070 Integrated sound card Using pipewire, issue happens with and without easyeffects, nothing changed in the config. -- You are receiving this mail because: You are the assignee for the bug.

1 1