December 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1193422] Kernel crash in the logs when exiting / shutting down the system
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193422 https://bugzilla.suse.com/show_bug.cgi?id=1193422#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |stakanov(a)disroot.org, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com Flags| |needinfo?(stakanov@disroot. | |org) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Is it a regression since the recent kernel update? Or did you get it in the earlier kernels? And, please upload the full dmesg output. In anyway, it's a DRM problem, Ccing relevant people. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192874] During OS booting, the loading installation system progress is very slow with Intel Alder Lake nonVpro system.
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192874 http://bugzilla.opensuse.org/show_bug.cgi?id=1192874#c22 --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Lin Ellen from comment #21) > Thank you, may I confirm if this is merged in OpenSUSU 15.4? It's provided as SLE15-SP4, and the latest kernel built from SLE15-SP4 git branch is found at OBS Kernel:SLE15-SP4 repo, http://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 http://bugzilla.opensuse.org/show_bug.cgi?id=1188970#c68 --- Comment #68 from Thomas Zimmermann <tzimmermann(a)suse.com> --- Hi (In reply to Ricardo Lopez Caballero from comment #67) > (In reply to Thomas Zimmermann from comment #66) > > Hi > > > > (In reply to guek wu neo from comment #65) > > > (In reply to Thomas Zimmermann from comment #63) > > > > Hi > > > > > > > > (In reply to Takashi Iwai from comment #62) > > > > > (In reply to Thomas Zimmermann from comment #57) > > > > > > I cannot reproduce the issue. > > > > > > > > > > > > STR: > > > > > > > > > > > > * Installed the latest SLE15-SP3 LEAP installer without updates. > > > > > > > > > > Just to make sure, could you try rather with SLE15-SP3 installer? The > > > > > quarter-update-1 should be new enough and still have the problem accordingly. > > > > > > > > Yes, I also tried SLE15-SP3. I still cannot reproduce the problem. :/ > > > > > > Just to double confirm.. you need to have the displaylink monitor attached > > > when you do the installation inorder to see the problem > > > > I did this a while ago. I'll try again, but I don't have much hope. It seems > > like it's dependent on the display. > > Hi Thomas, > what USB Display are you using ? I have several USB2 adapters with DisplayLink chips. They all have a separate connector for the monitor. I don't have a dedicated display. > The graphics card in your system is onboard or external (PCI or PCIe) ? A discrete Radeon on PCIe. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193374] [kernel 5.15.3][zpci] PCI not initialized/supported: => lspci -v / lspci -k lists no PCI devices
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193374 https://bugzilla.suse.com/show_bug.cgi?id=1193374#c12 --- Comment #12 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From Niklas.Schnelle(a)ibm.com 2021-12-06 04:06 EDT------- This looks very much like a hardware/VM configuration issue to me. As the dmesg output states facilities 69 and 71 don't seem to be available on the VM and these are required for the use of PCI. Linux has no control over what facilities are available, that is all under control of the hypervisor, so in this case the underlying z/VM host. I'm not sure why that would not provide these facilities as I'd think they are the default on at least z13+. One reason could be if the z/VM host is part of a sysplex as far as I know since PCI doesn't work with live guest migration on z/VM right now that might disable it. I'd still like to address a few misconceptions in prior comments. 1. zpci is not a special PCI device, it is the name of the "glue layer" that helps adapt the IBM Z native PCI support such that the devices can be used by standard Linux drivers for these devices such as the nvme and mlx5_core drivers. It kind of takes the role of PCI controller drivers on other platforms though we don't really have the concept of a PCI controller on Z as PCI is part of the Architecture. 2. No pci=1 parameter is needed anymore, PCI support should be enabled on all supported kernels and distributions. 3. In a z/VM guest PCI devices are by default not visible to the guests they can be listed with "vmcp query pcif" and attached with "vmcp attach pcif <fid> to \*" where <fid> is the Function ID displayed in the above query command. However since the facilities aren't enabled even if there are PCI devices they will not be usable so the lack of the facilities needs to be fixed first. All that said I was planning to do some PCI tests with an OpenSUSE Tumbleweed system in the future anyway since I also use Tumbleweed in a KVM guest of my x86_64 system. So I'll confirm if that works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193286] Kernel panic after waking up laptop from sleep
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193286 https://bugzilla.suse.com/show_bug.cgi?id=1193286#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- The kernel crash is definitely a kernel problem, but how to trigger is a different question. The condition might be some power-management adjustment by the desktop environment, for example. Could you upload the full dmesg output? Please use attachment. And, assume that it's some issue due to some devices: we may try to reduce the used devices and check whether it works or not. e.g. avoid BT device or USB DVD device (those appeared right before the crash line). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193263] New journalctl errors after installing kernel-default 5.15.5-1.1
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193263 https://bugzilla.suse.com/show_bug.cgi?id=1193263#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Gene Snider from comment #13) > Here are the error messages for kernel-default-5.15.6-3.1.g0f8ae34: > > > jctl-n -b -2 -p err > -- Journal begins at Wed 2021-09-29 10:25:23 PDT, ends at Sun 2021-12-05 > 15:35:19 PST. -- > Dec 05 15:31:11 Mobile-PC systemd[1]: Failed to start X Display Manager. > Dec 05 15:31:11 Mobile-PC systemd-backlight[1519]: Failed to get backlight > or LED device 'backlight:acpi_video0': No such device > Dec 05 15:31:11 Mobile-PC systemd[1]: Failed to start Load/Save Screen > Backlight Brightness of backlight:acpi_video0. > Dec 05 15:31:44 Mobile-PC login[1193]: gkr-pam: unable to locate daemon > control file > > It appears that all the kernel messages are fixed, but systemd isn't happy. Hm, it must be the saved information in that directory. Are you sure that all files there got removed? Once when you boot an older kernel, this file gets created again, and the problem is re-triggered. Basically systemd should remove the stale entry automatically or downgrade the message level, i.e. the remaining issue is a systemd issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193374] [kernel 5.15.3][zpci] PCI not initialized/supported: => lspci -v / lspci -k lists no PCI devices
by bugzilla_noreply＠suse.com 06 Dec '21

06 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193374 LTC BugProxy <bugproxy(a)us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=195588 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c25 --- Comment #25 from Kourosh P. <kourosh(a)pourdanandeh.com> --- (In reply to Takashi Iwai from comment #16) > BTW, when you boot with another desktop environment (such as icewm), does > the problem persist? I mean not to log out and switch from KDE, but login > directly to icewm session (which should be available as fallback) at boot. I enabled icewm to load instead of Plasma at boot, but still NO Signal when turning on monitor after boot I am afraid. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c24 --- Comment #24 from Kourosh P. <kourosh(a)pourdanandeh.com> --- Created attachment 854332 --> http://bugzilla.opensuse.org/attachment.cgi?id=854332&action=edit ps ucx for root after switching to TTY1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 05 Dec '21

05 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193397 http://bugzilla.opensuse.org/show_bug.cgi?id=1193397#c23 --- Comment #23 from Kourosh P. <kourosh(a)pourdanandeh.com> --- Created attachment 854331 --> http://bugzilla.opensuse.org/attachment.cgi?id=854331&action=edit ps ucx for user after switching to TTY1 -- You are receiving this mail because: You are the assignee for the bug.

1 0