August 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c38 --- Comment #38 from Gary Ching-Pang Lin <glin(a)suse.com> --- So there is no pending MOK request and shim/grub2 are up-to-date, the it's a different issue. Could you set SHIM_VERBOSE with this command and enable Secure Boot again? # mokutil --set-verbosity true It'd make shim to print more information. I hope we can get more clues from that... ("mokutil --set-verbosity false" removes SHIM_VERBOSE.) As for grubx64.efi, it's unsigned grub2 with dynamic module loading enabled. To make sure that grub2 won't load any malicious code, grub.efi is generated as a monolithic image and built in the necessary modules. That's the image we sign. On the other hand, grubx64.efi is a fallback for the system without Secure Boot or with disabled Secure Boot, so it's unsigned. As for the verification of shim, it's supposed to be verified by "Microsoft Corporation UEFI CA 2011", and it can be downloaded from the following link: https://go.microsoft.com/fwlink/p/?linkid=321194 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1174800] Touchsreen and touchpad randomly don't work
by bugzilla_noreply＠suse.com 30 Aug '20

30 Aug '20

https://bugzilla.suse.com/show_bug.cgi?id=1174800 https://bugzilla.suse.com/show_bug.cgi?id=1174800#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1174800) was mentioned in https://build.opensuse.org/request/show/830611 15.2 / kernel-source -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 30 Aug '20

30 Aug '20

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! Raise default file descriptor limits to meet Valve Proton requirements -> http://bugzilla.suse.com/show_bug.cgi?id=1107525 suspend to RAM no longer working after upgrade to Leap 15.1 -> http://bugzilla.suse.com/show_bug.cgi?id=1137748 Untested laptop multimedia keys, please report success or failure to eric.piel(a)tremplin-utc.net -> http://bugzilla.suse.com/show_bug.cgi?id=1142370 Bad USB cable causes eternal kernel messages, even after unplug: "tag#0 sense submit err -19 uas-tag 1 inflight: s-st a-in s-in a-cmd s-cmd" -> http://bugzilla.suse.com/show_bug.cgi?id=1155840 System crash caused by i915 driver -> http://bugzilla.suse.com/show_bug.cgi?id=1155938 Bluetooth device sometimes vanishes after booting Tumbleweed - needs BIOS on/off cycle to come back -> http://bugzilla.suse.com/show_bug.cgi?id=1159767 Excessive swapping when buffers / cache expand beyond free physical RAM -> http://bugzilla.suse.com/show_bug.cgi?id=1159882 Screen flickering on latest Dell XPS 7390 with kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun -> http://bugzilla.suse.com/show_bug.cgi?id=1161843 kernel 5.3.18-lp152.1 : Interrupts enabled after mce_syscore_resume -> http://bugzilla.suse.com/show_bug.cgi?id=1161867 kernel packaging problem: RPM group = %group -> http://bugzilla.suse.com/show_bug.cgi?id=1163592 Kernel oops in s390x tumbleweed -> http://bugzilla.suse.com/show_bug.cgi?id=1163684 Kernel crash (likely because of Intel graphics card) -> http://bugzilla.suse.com/show_bug.cgi?id=1164698 CD tray closed immediately after ejecting media -> http://bugzilla.suse.com/show_bug.cgi?id=1165047 System hung - nouveau 0000:01:00.0: plasmashell[2512]: channel 7 killed! -> http://bugzilla.suse.com/show_bug.cgi?id=1165790 Harmonize kernel modules in JeOS leap 15.1 with TW and leap 15.2 -> http://bugzilla.suse.com/show_bug.cgi?id=1166342 shorewall traffic shaping locks/crashes kernel hard -> http://bugzilla.suse.com/show_bug.cgi?id=1166688 ACPI BIOS Error (bug) -> http://bugzilla.suse.com/show_bug.cgi?id=1167305 Mounting of SMB share through fstab fails on boot -> http://bugzilla.suse.com/show_bug.cgi?id=1168873 ACPI error on boot -> http://bugzilla.suse.com/show_bug.cgi?id=1169837 HW exception while booting on Rockchip Excavation board (aarch64) -> http://bugzilla.suse.com/show_bug.cgi?id=1170088 test bug for assignee change -> http://bugzilla.suse.com/show_bug.cgi?id=1172181 Support for 64-bot processors on motherboards with 32-bit UEFI -> http://bugzilla.suse.com/show_bug.cgi?id=1172292 usb message shown on console even with "quiet splash=silent" -> http://bugzilla.suse.com/show_bug.cgi?id=1172322 Random screen flashing after suspend on KDE -> http://bugzilla.suse.com/show_bug.cgi?id=1172475 Mysterious crashes with kernel 5.6.14, suspect KVM -> http://bugzilla.suse.com/show_bug.cgi?id=1172541 Videoconferencing apps on openSUSE --> much higher CPU and heat than Clear Linux -> http://bugzilla.suse.com/show_bug.cgi?id=1172900 Kernel 5.7.1 does not boot -> http://bugzilla.suse.com/show_bug.cgi?id=1173071 iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 -> http://bugzilla.suse.com/show_bug.cgi?id=1173294 Kernel delays boot by 12s if ip= option given -> http://bugzilla.suse.com/show_bug.cgi?id=1173402 Webcam(earlier working) doesn't work now. Sony Vaio -> http://bugzilla.suse.com/show_bug.cgi?id=1173448 WiFi Device not working for BCM-43142,even after the installation of boradcom-wl from packman. -> http://bugzilla.suse.com/show_bug.cgi?id=1173449 Build of VMware access to kernel gives issues at interface build time. -> http://bugzilla.suse.com/show_bug.cgi?id=1173591 journal is flooded with "upowerd: treating change event as add on" when Dell WD15 Dock is connected -> http://bugzilla.suse.com/show_bug.cgi?id=1173728 System hangups in dual monitor use, likely Plasma/Xorg related -> http://bugzilla.suse.com/show_bug.cgi?id=1173748 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS -> http://bugzilla.suse.com/show_bug.cgi?id=1173819 Internal error: synchronous parity or ECC error - while building on obs-arm-2/3 (ThunderX) -> http://bugzilla.suse.com/show_bug.cgi?id=1173870 BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook -> http://bugzilla.suse.com/show_bug.cgi?id=1173891 Laptop: one of two usb3 hubs gone with 5.7 - works with 5.3.6 (linux live system) -> http://bugzilla.suse.com/show_bug.cgi?id=1174017 kernel-firmware-amdgpu 20200702 breaks video on Picasso -> http://bugzilla.suse.com/show_bug.cgi?id=1174278 rsync and mv command fails: "File exists" on cifs mount on kernel >= 5.7.8 with SMB protocol version 1.0 -> http://bugzilla.suse.com/show_bug.cgi?id=1174505 System not reconnecting to WLAN after suspend/resume -> http://bugzilla.suse.com/show_bug.cgi?id=1174622 Kernel v5.7.9 panic when resuming from hibernation with usb dock plugged-in -> http://bugzilla.suse.com/show_bug.cgi?id=1174886 Black screen with cursor upon login to plasma -> http://bugzilla.suse.com/show_bug.cgi?id=1175033 mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table -> http://bugzilla.suse.com/show_bug.cgi?id=1175105 WiFi breaks for Intel duel band AC 8265 -> http://bugzilla.suse.com/show_bug.cgi?id=1175125 AMDGPU Driver Brightness Issue -> http://bugzilla.suse.com/show_bug.cgi?id=1175300 NFSv4.1: timeout and endless unsuccessful retries -> http://bugzilla.suse.com/show_bug.cgi?id=1175305 latest kernel update gives backtrace on boot on Huawei TaiShan 2280 -> http://bugzilla.suse.com/show_bug.cgi?id=1175589 -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

1 0

[kernel-bugs] [Bug 1175296] New: network regression with a Realtek RTL8111E network chip
by bugzilla_noreply＠suse.com 30 Aug '20

30 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175296 Bug ID: 1175296 Summary: network regression with a Realtek RTL8111E network chip Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.koelmel(a)kit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 840655 --> http://bugzilla.opensuse.org/attachment.cgi?id=840655&action=edit lscpi of the realtek ethernet controller a watchdog stops the network function (a bridge with one ethernet interface is configured) on a Gigabyte Z68XP-UD3 motherboard with a Realtek RTL8111E network chip (driver r8169). This is reproducible after a little network usage after boot (e.g. working on a ssh session or doing some ansible commands over ssh) and until the watchdog is stopping the network, the ssh session is reacting very slow on the input. Then the bridge, the interface and the routes are still present and up, but the network is not working. There are no significant signs in the system log and on the higher network level before the problem is occuring. I have 2 such identical systems, which are showing the problem and were running stable on Leap 15.1. I have only tried the kernel 5.3.18-lp152.33-default. The Leap 15.2 was installed from a image, which is running stable on other systems (with other network cards and motherboards). -- You are receiving this mail because: You are the assignee for the bug.

1 21

[kernel-bugs] [Bug 1175908] encrypted rootfs does not boot anymore
by bugzilla_noreply＠suse.com 30 Aug '20

30 Aug '20

https://bugzilla.suse.com/show_bug.cgi?id=1175908 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- 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 1175581] Laptop BuildIn keyboard is not working with kernel-default-5.8.0-1.1
by bugzilla_noreply＠suse.com 29 Aug '20

29 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175581 http://bugzilla.opensuse.org/show_bug.cgi?id=1175581#c9 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch(a)suse.com --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- Could you test with IceWM instead of KDE? If it's broken there, too, it's not specific to DE. Also, you can test with evtest program to see whether you get the key events on both working and non-working cases. Adding Stefan to Cc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175581] Laptop BuildIn keyboard is not working with kernel-default-5.8.0-1.1
by bugzilla_noreply＠suse.com 29 Aug '20

29 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175581 http://bugzilla.opensuse.org/show_bug.cgi?id=1175581#c8 --- Comment #8 from Erwin Laskodi <elaskodi(a)gmail.com> --- Hi Takashi, yes, with kernel 5.8 and the "al t+ctrl+F1" combination on my usb keyboard, I'm able to login by using the the built-in keyboard. It looks like it's not a kernel but a KDE problem.... any suggestions? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 28 Aug '20

28 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c37 --- Comment #37 from John Shaw <johngshaw(a)twc.com> --- (In reply to Martin Wilck from comment #36) > (In reply to John Shaw from comment #35) > > With regard to my reply in comment 34, I do not get to the GRUB menu. If > > SecureBoot is enabled, failure is an immediate blank screen(s) as the BIOS > > exits POST. Nothing reboots the machine (eg, cntl-alt-del) other than > > physically pressing the reboot button. > > The question is if the BIOS fails to verify the shim, or shim fails to > verify any of the follow-up binaries. Can you check this e.g. with the UEFI > shell? I don't know how to check this in the UEFI shell. Can you explain? However, I managed to get a version of sbverify to work under suse 15.2. How correct this version is is unclear. I got the binary from a ubuntu repo, and I had to jury-rig the libcrypto.1.0.0 library dependency with a symlink to /usr/lib64/libcrypto.so.43. Anyway, it apparently works for the --list option. efi/boot% sudo sbverify --list bootx64.efi warning: data remaining[1172696 vs 1336112]: gaps between PE/COFF sections? signature 1 image signature issuers: - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 image signature certificates: - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Windows UEFI Driver Publisher issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation UEFI CA 2011 issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft Corporation Third Party Marketplace Root signature 2 image signature issuers: - /CN=openSUSE Secure Boot CA/C=DE/L=Nuremberg/O=openSUSE Project/emailAddress=build(a)opensuse.org image signature certificates: - subject: /CN=openSUSE Secure Boot Signkey/C=DE/L=Nuremberg/O=openSUSE Project/emailAddress=build(a)opensuse.org issuer: /CN=openSUSE Secure Boot CA/C=DE/L=Nuremberg/O=openSUSE Project/emailAddress=build(a)opensuse.org I tested every efi file and the vmlinux images in both /efi/boot and /efi/opensuse, and all BUT /efi/opensuse/grubx64.efi appear to have valid signature certificates. For this I get: % sudo sbverify --list grubx64.efi No signature table present Should grubx86.efi be signed or not? As to using sbverify to actually verify the signatures, I either don't understand what to use for the x509 certificate (for the --cert option), or the utility is broken (as it was not meant for Suse). Its looking for a file here. I tried to save the for keysets in the bios (db, dbx, KEK, PK) and these do seem to be somesort of certificate files, but they don't work in this context. One must be able to get the appropriate (original) certificate from the BIOS, but I don't know how to get it in the correct x509 format. > > > Other info: In my Asus BIOS, I can effectively disable SecureBoot by > > selecting "Other OS" vs "Windows UEFI" under the SecureBoot section. This > > still displays a line stating that SecureBoot is enabled, but the full linux > > boot sequence works, and mokutil will confirm that it's disabled. > > Sounds like broken BIOS. its the only one I got (well, the most recent one anyway;). Asus does not define this very well. I interpreted "Other OS" as anything that does not use UEFI but clearly my system is not booting from an MBR. > > > I have > > read that clearing the BIOS keys also disables SecureBoot, and that the BIOS > > will state so. I have not tried that method. > > I wouldn't recommend that, unless you're certain you can undo it. Yes, I don't really know what I am doing here. I have the keys backed up, but I can see really screwing this up. I can restore the keys to the orginal factory condition easily as well. I am wondering if its possible that the keys that are in the BIOS are somehow invalid. Still I would expect the BIOS to put put a big red screen and indicate it will not boot. That is difference behavior to hanging the 1st stage boot loader. > > Btw the pesign -S output is a pain. No fingerprint or otherwise useful data, > just the common name, which could mean anything. And why does it *always* > print "Content is detached; signature cannot be verified."? see my comment above regarding the use of sbverify. Can I use it to try and verify the signitures of the efi files? I just don't know how to supply the correct certificates with it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1169866] boot sequence fails with "failed to probe lspcon"
by bugzilla_noreply＠suse.com 28 Aug '20

28 Aug '20

https://bugzilla.suse.com/show_bug.cgi?id=1169866 https://bugzilla.suse.com/show_bug.cgi?id=1169866#c5 Thomas Rother <t.rother(a)netzwissen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(t.rother@netzwiss | |en.de) | --- Comment #5 from Thomas Rother <t.rother(a)netzwissen.de> --- no more an issue on NAME="openSUSE Tumbleweed" # VERSION="20200824" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200824" PRETTY_NAME="openSUSE Tumbleweed" to be closed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175626] Recent update run on August 21, 2020 kills bootloader
by bugzilla_noreply＠suse.com 28 Aug '20

28 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c36 --- Comment #36 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to John Shaw from comment #35) > With regard to my reply in comment 34, I do not get to the GRUB menu. If > SecureBoot is enabled, failure is an immediate blank screen(s) as the BIOS > exits POST. Nothing reboots the machine (eg, cntl-alt-del) other than > physically pressing the reboot button. The question is if the BIOS fails to verify the shim, or shim fails to verify any of the follow-up binaries. Can you check this e.g. with the UEFI shell? > Other info: In my Asus BIOS, I can effectively disable SecureBoot by > selecting "Other OS" vs "Windows UEFI" under the SecureBoot section. This > still displays a line stating that SecureBoot is enabled, but the full linux > boot sequence works, and mokutil will confirm that it's disabled. Sounds like broken BIOS. > I have > read that clearing the BIOS keys also disables SecureBoot, and that the BIOS > will state so. I have not tried that method. I wouldn't recommend that, unless you're certain you can undo it. Btw the pesign -S output is a pain. No fingerprint or otherwise useful data, just the common name, which could mean anything. And why does it *always* print "Content is detached; signature cannot be verified."? -- You are receiving this mail because: You are on the CC list for the bug.

1 0