January 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c22 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #22 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to filippos Filippos from comment #21) > Tried: > sudo vi /etc/modprobe.d/snd_hda.conf > options snd_hda_codec_hdmi.enable_silent_stream=N > > but it doesn't fix Obviously. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180799] New: No keyboard input available in installer or during boot on RPi4
by bugzilla_noreply＠suse.com 12 Jan '21

12 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180799 Bug ID: 1180799 Summary: No keyboard input available in installer or during boot on RPi4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dillon.ang.h(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, After I updated my system from Tumbleweed AArch64 snapshot 20201218 to snapshot 20210108, I noticed that there appears to be a problem with kernel-default-5.10.4-1.1. It may be related to the kernel module for the VL805 chip that handles USB on the Raspberry Pi 4. This issue does not affect the Raspberry Pi 3 which still appear to run normally. This problem can be seen in a few different ways. When booting the system from the installation DVD, I have keyboard input in GRUB, but as soon as the system starts booting into the installer, my keyboard and mouse goes dead. It will boot all the way to the screen where it asks you to accept the license agreement (including downloading what it needs to update the installer), but you cannot use either the mouse or keyboard. You also are unable to interact with the system during the boot process using the keyboard (to switch from the splash to a verbose mode). Because of this, you cannot actually install Tumbleweed 20210108 on the Raspberry Pi 4 from the USB. I tested this on a Raspberry Pi 4 4GB that boots entirely from a USB drive (no SD card), I installed 20201218, then I did a zypper dup to 20210108. While you can interact with the system using the keyboard during GRUB, during the boot process, it stalls completely, and the system times out and goes into a recovery prompt (since it can no longer see the USB drive it is booting from). You cannot type anything here since all USB devices appear to be dead. I also tested this on the same Raspberry Pi 4 4GB with an SD card. I installed 20201218 using the USB drive, then I did a zypper dup to 20210108. This time, it will boot up until the prompt to enter a password to unlock encrypted drives (I use LUKS on my home partition to encrypt it), but you are unable to enter a password to unlock the drive since the system does not respond to the keyboard. You are also unable to interact with the system using the keyboard during the boot process (you can switch between the splash and verbose mode with the keyboard). The workaround was to boot the system up using kernel-default-5.9.14-1, since it was previously installed when I installed 20201218. When I did this, the system worked as expected both when booted from USB and when booted from an SD card. I've seen this behavior previously when I ran the Debian AArch64 and Ubuntu AArch64 installer. You can interact with the system during GRUB, but as soon as the installer starts, you lose any ability to use USB devices. It appears also related to the VL805 chip the Raspberry Pi 4 uses since I was able to boot and run through the installation for both of these on the Raspberry Pi 3. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1180380] Blank external monitor after resume from suspend
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180380 http://bugzilla.opensuse.org/show_bug.cgi?id=1180380#c11 --- Comment #11 from Russell Sandish <hpcoder(a)hpcoders.com.au> --- What is worse is that when the screensaver turns off the monitor after a period of inactivity, it is impossible to resume the monitor. There appears to be nothing to do but reboot the computer at this point. After doing a clean install, the problem still remains. I haven't checked the suspend/resume is similarly affected as yet, but presumably so. I'll report back later if different. The workaround is to disable the Energy saver mode under power settings, and to not use suspend. But this is a major showstopper bug, and I will not upgrade my laptop until this is sorted. On the plus side, it does look like last year's wicked bug (https://bugzilla.opensuse.org/show_bug.cgi?id=1157394) has now been fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c21 filippos Filippos <filippos(a)filippides.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |filippos(a)filippides.eu Component|Kernel |Kernel Version|Leap 15.2 |Current Resolution|FIXED |--- Product|openSUSE Distribution |openSUSE Tumbleweed --- Comment #21 from filippos Filippos <filippos(a)filippides.eu> --- Same error here: screen frozen, net frozen, usb, mice & keyboards frozen. Tried: sudo vi /etc/modprobe.d/snd_hda.conf options snd_hda_codec_hdmi.enable_silent_stream=N but it doesn't fix (Kernel 5.10.4) Intel i5-7600T -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180711] External monitor DEAD after logging in - works in console / SDDM since updating to 20210106
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180711 https://bugzilla.suse.com/show_bug.cgi?id=1180711#c7 --- Comment #7 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- Maybe. I don't remember having changed anything with xrandr in ages, before the issue had occurred. This hit me "out of the blue". Good riddance! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1178790] [Build 20201112][s390x] openQA test fails in bootloader_s390 - dasd_configure: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0150/online: Resource temporarily unavailable (NO VALID SENSE AVAILABLE)
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178790 https://bugzilla.suse.com/show_bug.cgi?id=1178790#c19 Sergio Lindo Mansilla <slindomansilla(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #19 from Sergio Lindo Mansilla <slindomansilla(a)suse.com> --- https://openqa.opensuse.org/tests/1578902#next_previous -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1178790] [Build 20201112][s390x] openQA test fails in bootloader_s390 - dasd_configure: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0150/online: Resource temporarily unavailable (NO VALID SENSE AVAILABLE)
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178790 https://bugzilla.suse.com/show_bug.cgi?id=1178790#c18 Sergio Lindo Mansilla <slindomansilla(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(ihno(a)suse.com) | --- Comment #18 from Sergio Lindo Mansilla <slindomansilla(a)suse.com> --- Right, not reproducible anymore: https://openqa.opensuse.org/tests/1578902#next_previous -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180381] [Build 20201225] [s390x] Kernel Panic - No TPM chip found, activating TPM-bypass
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180381 https://bugzilla.suse.com/show_bug.cgi?id=1180381#c14 Sergio Lindo Mansilla <slindomansilla(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ihno(a)suse.com) --- Comment #14 from Sergio Lindo Mansilla <slindomansilla(a)suse.com> --- Ihno, I suppose that you only changed qaboot on the z/VM guests for openqa.opensuse.org. I can still find 200000 in `qaboot exec a` on auto-mounted disk A -> MNT191 on z/VM guests for openqa.suse.de. Could you update it too? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180780] New: ioctl(VIDIOC_G_FMT): Invalid argument from ffmpeg after upgrade to kernel v5.10.4
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180780 Bug ID: 1180780 Summary: ioctl(VIDIOC_G_FMT): Invalid argument from ffmpeg after upgrade to kernel v5.10.4 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: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- FFMpeg reports EINVAL on VIDIOC_G_FMT ioctl. Strace does not provide more information. This does not happen with v5.10 built from Git. lpechacek@fmn:~> ffmpeg -v error -i /dev/video0 /dev/video4 [video4linux2,v4l2 @ 0x55be60edc3c0] ioctl(VIDIOC_G_FMT): Invalid argument /dev/video0: Invalid argument -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1180749] AMD Ryzen 4800H Renoir APU brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 11 Jan '21

11 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180749 https://bugzilla.suse.com/show_bug.cgi?id=1180749#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> --- Care to report to the upstream, e.g. gitlab.freedsktop.org Issues? That's the official place for reporting. I'll keep this bug opened in case we can do some backports based on the upstream devs. -- You are receiving this mail because: You are the assignee for the bug.

1 0