December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 1211761] New: 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 17 May '24

17 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: 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 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: 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 FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are the assignee for the bug.

1 6

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

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug ID: 1218184 Summary: Eliminate the need for 'OBS source links': convert to _multibuild Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: Dolomite Version: Milestone 5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fcrozat(a)suse.com CC: dimstar(a)opensuse.org, dleuenberger(a)suse.com, fcrozat(a)suse.com, jslaby(a)suse.com, kernel-bugs(a)opensuse.org, mls(a)suse.com, msuchanek(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com Depends on: 1211226 Target Milestone: --- Group: SUSE Enterprise Partner Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1211226 +++ In order to prepare for 'git based source management', we need to fix up a few technical issues. One such issue is 'source links' not being supported in git (i.e in OBS we have openSUSE:Factory/kernel-source as the main package plus a bunch of 'linked packages', each with the name of the additional spec files) The solution is, technically seem, rather simple: using _multibuild multibuild support on OBS is known in two variants, one using a single spec file and conditionals inside the spec file based on @BUILD_FLAVOR@ (probably the more known way) but OBS also supports 'just' listing the additional spec files as 'flavors' the _multibuild to be added to the kernel-source (main package) can be generated like this:  #!/bin/sh echo "<multibuild>" > _multibuild for pkg in *.spec; do test "{$pkg}" == "kernel-source.spec" && continue echo " <package>${pkg/.spec/}</package>" >> _multibuild; done echo "</multibuild>" >> _multibuild  the spec files do not need to be changed in anyway with this method -- You are receiving this mail because: You are on the CC list for the bug.

1 59

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

26 Mar '24

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

1 6

Leap 15.6 Alpha uses kernel 6.4.x which is buggy with Adaptec RAID controllers.
by Maxim 08 Mar '24

08 Mar '24

https://bugzilla.kernel.org/show_bug.cgi?id=217599 [ 7427.739081] aacraid: Host bus reset request. SCSI hang ? [ 7427.739101] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7427.739105] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7427.739107] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7427.739109] aacraid 0000:08:00.0: outstanding cmd: firmware-48 [ 7427.739111] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7427.765640] aacraid 0000:08:00.0: Controller reset type is 3 [ 7427.765652] aacraid 0000:08:00.0: Issuing IOP reset [ 7469.875692] aacraid 0000:08:00.0: IOP reset succeeded [ 7469.936116] aacraid: Comm Interface type2 enabled [ 7483.472661] aacraid 0000:08:00.0: Scheduling bus rescan [ 7496.491585] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7496.491764] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7553.768632] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768644] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768650] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768655] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768660] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768664] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768669] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.818630] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835306] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835312] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835317] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835331] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835335] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835340] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835344] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835348] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835353] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835357] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355616] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355631] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355637] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355642] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355647] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355652] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355657] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355661] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355666] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.382419] aacraid: Host bus reset request. SCSI hang ? [ 7598.382439] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7598.382443] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7598.382445] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7598.382447] aacraid 0000:08:00.0: outstanding cmd: firmware-30 [ 7598.382449] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7598.402360] aacraid 0000:08:00.0: Controller reset type is 3 [ 7598.402371] aacraid 0000:08:00.0: Issuing IOP reset [ 7640.363459] aacraid 0000:08:00.0: IOP reset succeeded [ 7640.422724] aacraid: Comm Interface type2 enabled [ 7653.650105] aacraid 0000:08:00.0: Scheduling bus rescan [ 7666.688374] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7666.688467] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7814.462297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462308] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462313] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462318] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462330] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462334] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462338] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.478923] aacraid: Host bus reset request. SCSI hang ? [ 7814.478936] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7814.478938] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7814.478940] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7814.478942] aacraid 0000:08:00.0: outstanding cmd: firmware-9 [ 7814.478943] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7814.495578] aacraid 0000:08:00.0: Controller reset type is 3 [ 7814.495587] aacraid 0000:08:00.0: Issuing IOP reset [ 7856.730598] aacraid 0000:08:00.0: IOP reset succeeded [ 7856.779371] aacraid: Comm Interface type2 enabled [ 7869.946607] aacraid 0000:08:00.0: Scheduling bus rescan [ 7882.985564] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7882.985661] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). P.S. I was not able to login to SUSE bugzillla. Login to SUSE portal does not work.

2 1

[Bug 1217748] New: Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 04 Mar '24

04 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217748 Bug ID: 1217748 Summary: Display corruption with spesific applications in Gnome-wayland session 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: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871111 --> https://bugzilla.suse.com/attachment.cgi?id=871111&action=edit sudo hwinfo >hwinfo.txt (macbook 5.1 with nvidia 9400/ core2 duo. 2008 old and rare) current build: 20231129 yast-snapper gui says my oldest snapshot is 2023-11-23 After a KDE/SDDM issue I installed a base gnome with gnome-wayland session and GDM. While most of the warnings on kernel log disappeared, couple of applications are causing massive display corruption in their work windows. gnome-terminal current and kde system monitor. They even corrupt the areas of desktop when they are moved. This is a kernel/nouveau hardware issue for sure as when I use gnome screen recording/snapshot all looks fine. Gnome developers suggested me to compile a new gnome git version which includes gtk4-terminal as opposed to current one which is a gtk3 version. I found a binary ( https://build.opensuse.org/package/show/home:mantarimay:GNOME:apps/gnome-te… ) and it is fine. I launched kde system monitor. I don't think it has anything to do with gtk3 and yet behaves same way. I am used to nouveau warnings but never seen this one: nouveau 0000:02:00.0: imem: OOM: 00100000 00001000 -2 I decided to post this bug report here as gnome-terminal from Fedora current official live USB works all fine. I have dmesg etc from it if needed. I can live without these applications however as this is a particularly rare configuration I thought I better report. I am OK with testing things. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1214073] New: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214073 Bug ID: 1214073 Summary: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading 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: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868684 --> https://bugzilla.suse.com/attachment.cgi?id=868684&action=edit photo of screen when system frozen As the system frozen and I am in hurry, I could only take photo of screen. It says "ACPI: _SB_.PCIB. IXUE. IGPU: failed to evaluate _DSM" on the last line which was said to be a harmless effect of nvidia chipset. I am using nouveau drivers (built into kernel) and the system is macbook 5,1 I don't want to flood here with needless data, I can provide everything needed. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1211796] New: kernel modules not usrmerged
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

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 22

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

27 Feb '24

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 17