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 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c6 Michael Hirmke <opensuse(a)mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse(a)mike.franken.de --- Comment #6 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Jiri Slaby from comment #5) > (In reply to Bit Juggler from comment #4) > > Hope this helps. > > It would actually have helped if you had tried what is suggested in comment > #3. Had the same problem today with my DELL XPS. Using snd_hda_codec_hdmi.enable_silent_stream=0 worked around the problem, and I got back my graphics environment. Thx! Bye. Michael. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180609] i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180609 http://bugzilla.opensuse.org/show_bug.cgi?id=1180609#c2 Frank Kr�ger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #2 from Frank Kr�ger <fkrueger(a)mailbox.org> --- Cf. https://bugzilla.suse.com/show_bug.cgi?id=1180543#c3 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180609] New: i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180609 Bug ID: 1180609 Summary: i915: No picture in Gnome/Wayland after booting 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: --- Created attachment 844879 --> https://bugzilla.suse.com/attachment.cgi?id=844879&action=edit Boot log from v5.10.4 (no picture) After kernel upgrade to v5.10.4 there is no picture in my graphical desktop (Gnome+Wayland). Screen backlight is lit but there is no picture on neither the laptop display nor the HDMI attached external display. Booting back to v5.10.3 fixes the issue. Hardware: Dell Inspiron 7373 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1180607] New: Black screen after return from standby with kernel 5.10.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180607 Bug ID: 1180607 Summary: Black screen after return from standby with kernel 5.10.4 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: p.stolz77(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, with Kernel 5.10.4 the system shows a black screen after return from standby. With kernel 5.10.3 all works fine. Operating System: openSUSE Tumbleweed 20210104 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.4-1-default OS Type: 64-bit Processors: 6 �� Intel�� Core�� i5-9400 CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 630 Peter Stolz -- 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 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Bit Juggler from comment #4) > Hope this helps. It would actually have helped if you had tried what is suggested in comment #3. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180369] Insane ping-times when connecting to 5GHz WLAN - 2.4 GHz works fine
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180369 https://bugzilla.suse.com/show_bug.cgi?id=1180369#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- iw dev and iw phy outputs please. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180476] Can't boot past initial ramdisk unless I first successfully start via a btrfs snapshot using kernel 5.8.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180476 https://bugzilla.suse.com/show_bug.cgi?id=1180476#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |noahadvs(a)gmail.com Flags| |needinfo?(noahadvs(a)gmail.co | |m) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Noah Davis from comment #0) > Whenever I restart, > there is a chance that my laptop (ASUS K501UW) will fail to boot past > initial ramdisk. Could you boot with "debug" kernel parameter (and with plymouth disabled)? You should see where it stops. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180369] Insane ping-times when connecting to 5GHz WLAN - 2.4 GHz works fine
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180369 https://bugzilla.suse.com/show_bug.cgi?id=1180369#c3 --- Comment #3 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- I'm not sure this has ever worked with this laptop. I usually get to update and run tests on this device only once or twice a year, when I visit a relative. I'm rather reluctant to mess with it, as I don't want to drive 600km to resurrect it if anything goes wrong. I may be able to have it boot from an ISO with somewhat newer live-linux system with a newer kernel (5.10.1_pmagic-x86_64). This would be less "risky". This may take quite a while... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1179367] New: Driver brcmfmac for Broadcom 43430 or firmware does not use channel 12 and 13 on WiFi 2.4GHz
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179367 Bug ID: 1179367 Summary: Driver brcmfmac for Broadcom 43430 or firmware does not use channel 12 and 13 on WiFi 2.4GHz Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: cfamullaconrad(a)suse.com, dleuenberger(a)suse.com, karol(a)babioch.de, mpluskal(a)suse.com Depends on: 1179308 Found By: --- Blocker: --- Meanwhile I've installed the missing package wireless-regdb and build and installed the package crda, also I'm abel to set the country code to DE and allow to use the channels 12 and 13 in the 2.4GHz area. This is reported by ``iwlist``: smartmeter:~ # iwlist wlan0 channel wlan0 13 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Nevertheless the brcmfmac driver does not see my router on channel 13, nor channel 12 of any of my neighbours, the highest channel reported by e.g. the command ``nmcli dev wifi list`` I open this bug because there are reports that in principle the hardware Broadcom 43430 does support channels above channel 11 as seen here https://github.com/raspberrypi/linux/issues/1355 +++ This bug was initially created as a clone of Bug #1179308 +++ this fact leads even after adding the line options cfg80211 ieee80211_regdom=DE in /etc/modprobe.d/99-local.conf and reloading both cfg80211 and brcmfmac kernel modules ... in the kernel logs I see: [ 9360.888829] usbcore: deregistering interface driver brcmfmac [ 9378.151397] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 9378.152331] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 9378.152533] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 9378.152545] cfg80211: failed to load regulatory.db [ 9382.598023] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 9382.598335] usbcore: registered new interface driver brcmfmac [ 9382.725940] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 9382.726020] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 9382.726514] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f in other words theregulatory.bin is missed, compare with https://forum-raspberrypi.de/forum/thread/34332-rpi3-trotz-kernel-4-4-50-ke… -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1180369] Insane ping-times when connecting to 5GHz WLAN - 2.4 GHz works fine
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180369 https://bugzilla.suse.com/show_bug.cgi?id=1180369#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rs.opensuse(a)spitzenpfeil.or | |g, tiwai(a)suse.com Flags| |needinfo?(rs.opensuse@spitz | |enpfeil.org) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- It's a bit too broad between the working and the latest TW kernels. Could you try to narrow down which kernel started showing the problem? You can try various kernel packages in my OBS repo, e.g. OBS home:tiwai:kernel:5.4, home:tiwai:kernel:5.5, ... -- You are receiving this mail because: You are the assignee for the bug.

1 0