June 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1212176] New: System hangs after upgrade to OpenSuse 15.5 during load of i915 driver when using Xen
by bugzilla_noreply＠suse.com 09 Jun '23

09 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212176 Bug ID: 1212176 Summary: System hangs after upgrade to OpenSuse 15.5 during load of i915 driver when using Xen 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: Manfred.Haertel(a)rz-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the upgrade to OpenSuse 15.5 my laptop did not boot completely when using Xen. It just hangs after during the load of the i915 driver from the initrd and just displays a black screen. The laptop boots normally if NOT using Xen (just booting directly to the Linux kernel) and it boots normally IF using Xen when using the Linux kernel command line parameter "nomodeset" (but of course, with bad graphics performance). After a long debugging session using my own printk() statements and netconsole for logging I found out that the actual problem is that the kernel routine pat_enabled() incorrectly returns false in a Xen Dom0 and the i915 driver fails if it receives this value, which finally leads to a kernel oops during the cleanup (!) of the i915 driver. With that knowledge I found out that the problem is a known one which was already discussed in the Linux kernel mailing list, see https://lore.kernel.org/lkml/bc13c66d-a885-e405-7b53-8cd7afdbecff@suse.com/… , but it seems that the included patch from that discussion is not contained in OpenSuse 15.5. Changing the wrong value of pat_enabled() solves my problem and the system boots normally. So the patch from the LKML or a similiar one should be applied to the OpenSuse 15.5 kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211761] vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 09 Jun '23

09 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211761 https://bugzilla.suse.com/show_bug.cgi?id=1211761#c1 --- Comment #1 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Hi Felix As stated in the kernel.org bug report, your best bet is to have the issue bisected. I don't have any nvidia cards to use for testing so I cannot bisect this either. Let's wait and see if there is any progress on the nouveau upstream issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1204940] Package hardware:rtl88x2bu does not build anymore
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1204940 https://bugzilla.suse.com/show_bug.cgi?id=1204940#c5 Eyad Issa <eyadlorenzo(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Eyad Issa <eyadlorenzo(a)gmail.com> --- After submitting the new package version, the package now compiles and works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211459] [Leap 15.4][btrfs][snapper-cleanup], 'systemctl start snapper-cleanup' causes infinite message 'BTRFS warning (device vda2): qgroup rescan is already in progress' in syslog and causes 'yast2 lan' command hang
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211459 https://bugzilla.suse.com/show_bug.cgi?id=1211459#c22 --- Comment #22 from David Sterba <dsterba(a)suse.com> --- I don't see what could be fixed on the kernel side, removing the warning is a workaround when snapper calls the ioctl frequently. Suggested in commen 18, snapper can check if there's something running and wait witout calling the ioctl. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

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

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211763 https://bugzilla.suse.com/show_bug.cgi?id=1211763#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- The package is available at: http://download.opensuse.org/repositories/Kernel:/stable/standard/ Note that it's an unofficial build, hence it won't boot with Secure Boot easily. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211410] Weird "vmalloc error" kernel stack trace when lsof is executed
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211410 https://bugzilla.suse.com/show_bug.cgi?id=1211410#c5 Vlastimil Babka <vbabka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(vbabka(a)suse.com) | Resolution|--- |UPSTREAM --- Comment #5 from Vlastimil Babka <vbabka(a)suse.com> --- The fix is posted here and merged in maintainer tree: https://lore.kernel.org/all/20230605201107.83298-1-lstoakes@gmail.com/ It will probably go to stable 6.3 as well. Since the warning was only observed once here, I think we can just wait for the stable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c79 --- Comment #79 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0749-2: An update that solves 12 vulnerabilities and has 27 fixes can now be installed. Category: security (important) Bug References: 1177529, 1193629, 1197534, 1198438, 1200054, 1202633, 1203331, 1204363, 1204993, 1205544, 1205846, 1206103, 1206232, 1206935, 1207051, 1207270, 1207560, 1207845, 1207846, 1208212, 1208420, 1208449, 1208534, 1208541, 1208542, 1208570, 1208607, 1208628, 1208700, 1208741, 1208759, 1208776, 1208784, 1208787, 1208816, 1208837, 1208843, 1209188, 1209436 CVE References: CVE-2022-3523, CVE-2022-38096, CVE-2023-0461, CVE-2023-0597, CVE-2023-1118, CVE-2023-22995, CVE-2023-22998, CVE-2023-23000, CVE-2023-23004, CVE-2023-23559, CVE-2023-25012, CVE-2023-26545 Sources used: openSUSE Leap 15.4 (src): kernel-syms-rt-5.14.21-150400.15.14.1, kernel-source-rt-5.14.21-150400.15.14.2 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4-RT_Update_4-1-150400.1.3.1 SUSE Real Time Module 15-SP4 (src): kernel-syms-rt-5.14.21-150400.15.14.1, kernel-source-rt-5.14.21-150400.15.14.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c78 --- Comment #78 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0796-2: An update that solves eight vulnerabilities and has 86 fixes can now be installed. Category: security (important) Bug References: 1166486, 1177529, 1203331, 1203332, 1204993, 1205544, 1206224, 1206232, 1206459, 1206640, 1206876, 1206877, 1206878, 1206880, 1206881, 1206882, 1206883, 1206884, 1206885, 1206886, 1206889, 1206894, 1207051, 1207270, 1207328, 1207588, 1207589, 1207590, 1207591, 1207592, 1207593, 1207594, 1207603, 1207605, 1207606, 1207607, 1207608, 1207609, 1207610, 1207613, 1207615, 1207617, 1207618, 1207619, 1207620, 1207621, 1207623, 1207624, 1207625, 1207626, 1207628, 1207630, 1207631, 1207632, 1207634, 1207635, 1207636, 1207638, 1207639, 1207641, 1207642, 1207643, 1207644, 1207645, 1207646, 1207647, 1207648, 1207651, 1207653, 1207770, 1207773, 1207845, 1207875, 1208149, 1208153, 1208183, 1208212, 1208290, 1208420, 1208428, 1208429, 1208449, 1208534, 1208541, 1208570, 1208607, 1208628, 1208700, 1208741, 1208759, 1208784, 1208787, 1209188, 1209436 CVE References: CVE-2022-36280, CVE-2022-38096, CVE-2023-0045, CVE-2023-0461, CVE-2023-0597, CVE-2023-22995, CVE-2023-23559, CVE-2023-26545 Sources used: openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 openSUSE Leap 15.4 (src): kernel-syms-5.14.21-150400.24.49.4, kernel-obs-qa-5.14.21-150400.24.49.2, kernel-source-5.14.21-150400.24.49.4, kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3, kernel-obs-build-5.14.21-150400.24.49.3 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 Basesystem Module 15-SP4 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3, kernel-source-5.14.21-150400.24.49.4 Development Tools Module 15-SP4 (src): kernel-syms-5.14.21-150400.24.49.4, kernel-obs-build-5.14.21-150400.24.49.3, kernel-source-5.14.21-150400.24.49.4 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_9-1-150400.9.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c52 --- Comment #52 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0796-2: An update that solves eight vulnerabilities and has 86 fixes can now be installed. Category: security (important) Bug References: 1166486, 1177529, 1203331, 1203332, 1204993, 1205544, 1206224, 1206232, 1206459, 1206640, 1206876, 1206877, 1206878, 1206880, 1206881, 1206882, 1206883, 1206884, 1206885, 1206886, 1206889, 1206894, 1207051, 1207270, 1207328, 1207588, 1207589, 1207590, 1207591, 1207592, 1207593, 1207594, 1207603, 1207605, 1207606, 1207607, 1207608, 1207609, 1207610, 1207613, 1207615, 1207617, 1207618, 1207619, 1207620, 1207621, 1207623, 1207624, 1207625, 1207626, 1207628, 1207630, 1207631, 1207632, 1207634, 1207635, 1207636, 1207638, 1207639, 1207641, 1207642, 1207643, 1207644, 1207645, 1207646, 1207647, 1207648, 1207651, 1207653, 1207770, 1207773, 1207845, 1207875, 1208149, 1208153, 1208183, 1208212, 1208290, 1208420, 1208428, 1208429, 1208449, 1208534, 1208541, 1208570, 1208607, 1208628, 1208700, 1208741, 1208759, 1208784, 1208787, 1209188, 1209436 CVE References: CVE-2022-36280, CVE-2022-38096, CVE-2023-0045, CVE-2023-0461, CVE-2023-0597, CVE-2023-22995, CVE-2023-23559, CVE-2023-26545 Sources used: openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 openSUSE Leap 15.4 (src): kernel-syms-5.14.21-150400.24.49.4, kernel-obs-qa-5.14.21-150400.24.49.2, kernel-source-5.14.21-150400.24.49.4, kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3, kernel-obs-build-5.14.21-150400.24.49.3 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 Basesystem Module 15-SP4 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3, kernel-source-5.14.21-150400.24.49.4 Development Tools Module 15-SP4 (src): kernel-syms-5.14.21-150400.24.49.4, kernel-obs-build-5.14.21-150400.24.49.3, kernel-source-5.14.21-150400.24.49.4 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_9-1-150400.9.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211796] kernel modules not usrmerged
by bugzilla_noreply＠suse.com 06 Jun '23

06 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211796 https://bugzilla.suse.com/show_bug.cgi?id=1211796#c2 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint(a)suse.com Flags| |needinfo?(snwint(a)suse.com) URL| |https://github.com/openSUSE | |/installation-images/pull/6 | |47 --- Comment #2 from Michal Suchanek <msuchanek(a)suse.com> --- installation-images does not handle usrmerged modules -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1211975] freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211975 https://bugzilla.suse.com/show_bug.cgi?id=1211975#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Just download kernel-default.rpm from the history repo. e.g. the oldest one found right now is: http://download.opensuse.org/history/20230514/tumbleweed/repo/oss/x86_64/ke… Then install it manually via zypper install --oldpackage option. % zypper in --oldpackage kernel-default-6.3.1-1.1.x86_64.rpm And boot with it (select the kernel at GRUB menu). After testing, you can uninstall the kernel again. % zypper rm kernel-default-6.3.1-1.1 But, before testing multiple kernels, I'd recommend you to modify /etc/zypp/zypp.conf at first. Change the line setting "multiversion.kernels" to add more entries, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running This will allow up to 4 kernels installed on the system simultaneously. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212019] Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 https://bugzilla.suse.com/show_bug.cgi?id=1212019#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pujos.michael@gma | |il.com) CC| |pujos.michael(a)gmail.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Also, I'm building a test kernel with the backport of the thunderbolt fix patch in the upstream subsystem tree. It's being built in OBS home:tiwai:bsc1212019 repo. Once after the build finishes (it takes an hour or so), could you check whether it works better? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212019] Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 https://bugzilla.suse.com/show_bug.cgi?id=1212019#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> --- So when you boot with 6.3.3 kernel on the same system now, the problem doesn't happen? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211975] freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211975 https://bugzilla.suse.com/show_bug.cgi?id=1211975#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mattm3a(a)yahoo.com, | |tiwai(a)suse.com Flags| |needinfo?(mattm3a(a)yahoo.com | |) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you try the older kernels found in TW history repo and verify which one works and which not? http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211763] 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 https://bugzilla.suse.com/show_bug.cgi?id=1211763#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> --- Hm, at least through a quick glance, there is no relevant change between 6.3.1 and 6.3.2 kernels about BT itself. The only change is the upstream commit d8d7ce037d9a8f1f0714ece268c4c2c50845bbc3 Revert "Bluetooth: btsdio: fix use after free bug in btsdio_remove due to un finished work" which is likely irrelevant. Please check with the latest kernel in OBS Kernel:stable repo to be sure. If the problem persists, we need to report to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211410] Weird "vmalloc error" kernel stack trace when lsof is executed
by bugzilla_noreply＠suse.com 05 Jun '23

05 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211410 https://bugzilla.suse.com/show_bug.cgi?id=1211410#c4 --- Comment #4 from Vlastimil Babka <vbabka(a)suse.com> --- I've reported it upstream and a vmalloc guy should have a fix soon. The warning is spurious as there's a fallback to the failing order-9 allocation, so it's going to be suppressed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199848] kernel crash on e.g. usb stick attach to qemu-kvm or un-plugging usb stick generally / error_code(0x0000) - not-present page
by bugzilla_noreply＠suse.com 04 Jun '23

04 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1199848 https://bugzilla.suse.com/show_bug.cgi?id=1199848#c8 --- Comment #8 from Alexander Krupp <obs(a)akr.yagii.de> --- The issue did not occur anymore. I am running on 5.14.21-150400.24.63-default #1 SMP PREEMPT_DYNAMIC Tue May 2 15:49:04 UTC 2023 , currently. From my point of view, the issue has been resolved. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1211459] [Leap 15.4][btrfs][snapper-cleanup], 'systemctl start snapper-cleanup' causes infinite message 'BTRFS warning (device vda2): qgroup rescan is already in progress' in syslog and causes 'yast2 lan' command hang
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211459 https://bugzilla.suse.com/show_bug.cgi?id=1211459#c21 --- Comment #21 from Arvin Schnell <aschnell(a)suse.com> --- David wanted to look at the problem. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

[Bug 1211459] [Leap 15.4][btrfs][snapper-cleanup], 'systemctl start snapper-cleanup' causes infinite message 'BTRFS warning (device vda2): qgroup rescan is already in progress' in syslog and causes 'yast2 lan' command hang
by bugzilla_noreply＠suse.com 02 Jun '23

02 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211459 https://bugzilla.suse.com/show_bug.cgi?id=1211459#c20 --- Comment #20 from Lubos Kocman <lubos.kocman(a)suse.com> --- Do we have any update on the issue team? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 01 Jun '23

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c43 --- Comment #43 from Joey Lee <jlee(a)suse.com> --- I have updated the openSUSE wiki page for UEFI to add a "Signing kernel module" section: https://en.opensuse.org/openSUSE:UEFI#Signing_kernel_module_for_verification openSUSE users can reference it to signing their self-built kernel module. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211069 https://bugzilla.suse.com/show_bug.cgi?id=1211069#c5 --- Comment #5 from Joerg Roedel <jroedel(a)suse.com> --- When devices have RMRRs are are not USB host controlers, there is no way to passthrough them. That is because there is no way to preserve the RMRR regions when attaching the device to a guest. This needs to be fixed in the machine firmware. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1211898] New: stress-ng fsize failure on NFSv3
by bugzilla_noreply＠suse.com 01 Jun '23

01 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211898 Bug ID: 1211898 Summary: stress-ng fsize failure on NFSv3 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: richard.palethorpe(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- While setting up some OpenQA NFS testing I came across the following error with stress-ng. $ stress-ng --sequential -1 --timeout 3 --class filesystem ... stress-ng: fail: [3866] fsize: fallocate unexpectedly succeeded at offset 262144 (0x40000), expecting EFBIG error stress-ng: fail: [3866] fsize: expected a SIGXFSZ signal at offset 262144 (0x40000), nothing happened stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 106797 (0x1a12d), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 1 (0x1), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 3 (0x3), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 7 (0x7), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 15 (0xf), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 31 (0x1f), expecting EFBIG error stress-ng: info: [3866] fsize: fallocate unexpectedly succeeded at offset 63 (0x3f), expecting EFBIG error ... This does not happen with NFSv4. It happens with both NFSv3 sync and async. I don't see any other errors. The tests have not been merged or scheduled on the main OpenQA instance yet. When they are I can post a link. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/17181 -- You are receiving this mail because: You are the assignee for the bug.

1 0