September 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1172541] New: Mysterious crashes with kernel 5.6.14
by bugzilla_noreply＠suse.com 22 Oct '20

22 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172541 Bug ID: 1172541 Summary: Mysterious crashes with kernel 5.6.14 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jimc(a)jfcarter.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Version: kernel-default-5.6.14-1.1.x86_64 and aarch64 for Tumbleweed I did a dist-upgrade on 2020-06-02. After I waited for download.opensuse.org to recover from its illness, the upgrade went smoothly. But after I rebooted all the machines, 5 to 10 minutes later two of them went catatonic, and a third (my laptop) froze up a few minutes after being booted up two days later. After I power cycled the gateway machine, it again froze about five minutes after booting. On those hosts I reverted (by the grub menu) to kernel-default-5.6.12-1.3.x86_64 and aarch64. There were no further catatonic incidents. The other hosts continued (on 5.6.14) for up to 36 hours and did not go catatonic (but I eventually reverted them also). Here are the symptoms: On two machines I was working on the console (XFCE) when it happened. It seemed perfectly normal, but suddenly keystrokes had no effect and continuously updating apps (load meter etc.) ceased updating. On the gateway, network thru traffic was no longer forwarded. After I rebooted it I checked syslog (debug level). After the last normal message (e.g. DHCP lease renewed) there was a burst of \0's, and the dmesg dump appeared immediately after, starting with "microcode updated early to revision..." and "Jun 4 08:47:03 jacinth kernel: [ 0.000000] Linux version 5.6.12-1-default (geeko@buildhost) (gcc version 9.3.1 20200406 [revision 6db837a5288ee3ca5ec504fbd5a765817e556ac2] (SUSE Linux)) #1 SMP Tue May 12 17:44:12 UTC 2020 (9bff61b)", i.e. the very first expected messages from dmesg. (I carefully booted it into 5.6.12 not 5.6.14.) I have not been able to find any useful symptoms that might shed light on what is killing the machines. Machines running 5.6.12 did not crash, both before the dist-upgrade and after I reverted. For what it's worth, here is some data about the various machines. These went catatonic: jacinth Gateway, directory server, never sleeps. Intel NUC6CAYH, Celeron(R) CPU J3455 @ 1.50GHz, Intel HD Graphics 500 (i915). It runs hostapd as a wireless access point, driver 8812au from rtl8812au-kmp-default-5.6.4.2+git20200318.49e98ff_k5.6.12_1-1.7.x86_64 xena Laptop, wireless, powered off when the human is sleeping. Acer Aspire A515-54-51D1, Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz, Intel UHD Graphics 620 (Whiskey Lake) (i915) diamond Normal desktop. When it crashed nobody was using it. At night it hibernates. Intel NUC7i5BNH, Core(TM) i5-7260U CPU @ 2.20GHz, Intel Iris Plus Graphics 640 (i915) These survived up to 36 hours on 5.6.14 (called "non-catatonic" below): claude Webserver (1.5 hits/min). VM (KVM) on Jacinth, x86_64, video=cirrus holly Desktop replacement. Raspberry Pi-3B, Broadcom BCM2837 @1.2GHz and VideoCore IV (vc4). aarch64. RPi's can't sleep. iris Audio-video player (17kbyte/sec), hibernates when unused. Intel NUC6CAYH, Celeron(R) CPU J3455 @ 1.50GHz (like Jacinth), Intel HD Graphics 500 (i915) oso Development VM (KVM) on Diamond, x86_64, video=cirrus petra Development VM (KVM) on Xena, x86_64, video=cirrus surya Cloud server, VM (KVM) at Linode, never sleeps :-), Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, no GPU at all. Thinking that X-Windows activity might be correlated with catatonia, for about 6 hours I set the non-catatonic machines (except Surya, has no console) to show screensaver eye candy continuously. I was wrong; none of them crashed. Iris hardware is identical to Jacinth, yet it did not go catatonic while Jacinth failed more times than any other host. I don't really know what effective action could be taken, beyond trying to guess which kernel patch may have been the culprit. Anyway, thank you for whatever you can do with this info. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1174278] New: kernel-firmware-amdgpu 20200702 breaks video on Raven Ridge
by bugzilla_noreply＠suse.com 15 Oct '20

15 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174278 Bug ID: 1174278 Summary: kernel-firmware-amdgpu 20200702 breaks video on Raven Ridge 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: adam.reichold(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 839828 --> http://bugzilla.opensuse.org/attachment.cgi?id=839828&action=edit GZippped output of YaST's hardware information module Update kernel-firmware-amdgpu from 20200610-1.1 to 20200702-1.1 breaks video on a HP ProBook 455R G6 containing an AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, i.e. AMD Raven Ridge. The problem manifests itself as a blank screen when the boot splash would be displayed and continuously spinning system fan. The machine is unresponsive when reaching this state, i.e. escape and sysrq keys are not working. Downgrading just the kernel-firwmare-amdgpu packages works around the issue. There is one kernel log message only visible with the new firmware: kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110). -- You are receiving this mail because: You are the assignee for the bug.

1 17

[kernel-bugs] [Bug 1177060] New: drm_calc_timestamping_constants error
by bugzilla_noreply＠suse.com 14 Oct '20

14 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177060 Bug ID: 1177060 Summary: drm_calc_timestamping_constants error 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: therapon(a)netzero.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Dell Precision M4800 laptop nVidia GK107GLM [Quadro K1100M] Nouveau 20.1.8-264.1 driver Once it starts happening, the following line is printed to the journald log: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 50: Can't calculate constants, dotclock = 0! It's a continuous stream as long as the mouse is moving. After just a few hours there are thousands of these lines in the log. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1175599] New: I installed Leap 15.2 and after upgrading I had no keyboard
by bugzilla_noreply＠suse.com 05 Oct '20

05 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175599 Bug ID: 1175599 Summary: I installed Leap 15.2 and after upgrading I had no keyboard Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: luizcantarino(a)yahoo.com.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.135 Safari/537.36 Build Identifier: Hello everyone! I just installed Leap 15.2, with everything working ... And after the first update I had no keyboard. The usb keyboard works. I had to determine by yast, the boot from the previous kernel, but I would like to try to fix this, and use the most current kernel. My machine is an Acer E5-511 laptop - 4gib ram - Intel Celeron N2940 - Bay Trail. Reproducible: Always I don't know if what I did is right, but it worked ... I went to /etc/x11/xorg.conf.d I deleted all files except touchpad ... I rebooted with the current kernel, and it worked ... -- You are receiving this mail because: You are the assignee for the bug.

1 113

[kernel-bugs] [Bug 1177060] drm_calc_timestamping_constants error
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1177060 https://bugzilla.suse.com/show_bug.cgi?id=1177060#c4 --- Comment #4 from Therapon Sundoulos <therapon(a)netzero.com> --- Working on trying to figure out which kernel was last without the problem. So far it is present in all from 5.8.4-1.1 and later. Takes time to determine if the problem is still present - have to reboot, use it for a little while, then let it suspend. The issue doesn't appear until wake after first suspend. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1176646] Latest Kernel has i915 GPU Hang
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176646 https://bugzilla.suse.com/show_bug.cgi?id=1176646#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- I believe only upstream can solve it fully. Care to report to the upstream bug tracker, e.g. gitlab.fredesktop.org issues? It's an old chip (Haswell) and Intel people might not be interested in fixing that so much, though. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175599] I installed Leap 15.2 and after upgrading kernel I had no internal laptop keyboard via libinput driver (evdev driver works)
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175599 https://bugzilla.suse.com/show_bug.cgi?id=1175599#c105 --- Comment #105 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 842121 --> https://bugzilla.suse.com/attachment.cgi?id=842121&action=edit Fix patch for intel-vbtn -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175599] I installed Leap 15.2 and after upgrading kernel I had no internal laptop keyboard via libinput driver (evdev driver works)
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175599 https://bugzilla.suse.com/show_bug.cgi?id=1175599#c104 --- Comment #104 from Takashi Iwai <tiwai(a)suse.com> --- Now we have a fix patch from the upstream, to be included in either 5.9-final or 5.10-rc1. I'm building test kernel with the patch for Leap 15.2 and stable in OBS home:tiwai:bsc1175599-leap15.2 and home:tiwai:bsc1175599-stable repos, respectively. Those will appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1175599-leap15.2/… and http://download.opensuse.org/repositories/home:/tiwai:/bsc1175599-stable/st… Please give it a try later. Install the kernel, remove the blacklist, reboot with that kernel, and test whether the built-in keyboard still works. If it works, please confirm that intel_vbn module is loaded (shown in lsmod output). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1169273] WiFi broken -Broadcom-wl can't install on latest tumbleweed snapshot, running on kernel 5.6 so WIFI not working
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1169273 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1159882] Excessive swapping when buffers / cache expand beyond free physical RAM
by bugzilla_noreply＠suse.com 30 Sep '20

30 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1159882 https://bugzilla.suse.com/show_bug.cgi?id=1159882#c55 --- Comment #55 from Michal Hocko <mhocko(a)suse.com> --- (In reply to Robert Delahunt from comment #54) > Sorry, today is crunch time for my graduate college courses. I should be > able to get to it tomorrow, 9/30/20. I'll do my best to get to it ASAP. No rush. -- You are receiving this mail because: You are the assignee for the bug.

1 0