July 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 13 Jul '20

13 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c76 --- Comment #76 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Martin Wilck from comment #75) > I thought it worked as Ludwig described in comment 64. At installation time, > the %post script runs "mokutil --import" for the kernel's key. At the > following reboot, the UEFI MOK manager application should prompt you whether > you want to add the key. > > Is your system missing mokutil, maybe? Ah. You're right I was asked once suddently after reboot to enter MOK management. There I saw the options (currently reproducing this): Continue Enroll MOK Enroll Key from Disk Enroll Hash from Disk First time I wasn't sure what to chose, so went on with Continue. Now I'm trying with "Enroll MOK". But I get asked for a password, which I don't know of course ... then unfortunately the machine turned off suddenly. After turning it on I see Continue *Reset* MOK Enroll Key from Disk Enroll Hash from Disk Now I selected "Reset MOK". Seems this was wrong. machine reoboots and longer asks questions. ;-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 13 Jul '20

13 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c75 --- Comment #75 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Stefan Dirsch from comment #74) > Is this the > expected behaviour of TW, that we don't support secure boot at al with TW? I thought it worked as Ludwig described in comment 64. At installation time, the %post script runs "mokutil --import" for the kernel's key. At the following reboot, the UEFI MOK manager application should prompt you whether you want to add the key. Is your system missing mokutil, maybe? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 13 Jul '20

13 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c74 --- Comment #74 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Takashi Iwai from comment #8) > The problem isn't too serious on TW because the TW kernel (i.e. the upstream > kernel) still has no strict lockdown. SLE / Leap kernel has a stricter > lockdown, so it can be an actual problem. It might be a problem on TW as > well once when the upstream accepts the more lockdown. > > IOW, it's not only about CONFIG_MODULE_SIG. Rather the key point is whether > the kernel has a lockdown feature for the unsigned module or not. So I tried to use a TW kernel in order to verify, if it's the kernel lockdown setting of Leap 15.2 in contrast to the its setting on TW. Result is that the kernel cannot be loaded at all with secure boot on. Is this the expected behaviour of TW, that we don't support secure boot at al with TW? I was using the current kernel of Devel:Kernel:master project in our internal buildservice. I expect the same issue with the kernel built in a TW project. I doubt that we let sign all of our TW kernels once or twice a week with each TW release, right? The error message when trying to load the kernel on a secure boot system is: Loading Linux 5.8.0-rc4-2.g006adcb-default ... error: bad shim signature Loading initial ramdisk ... error: you need to load the kernel first. Press any key to continue... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173158] CONFIG_MODULE_SIG=y
by bugzilla_noreply＠suse.com 13 Jul '20

13 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173158 https://bugzilla.suse.com/show_bug.cgi?id=1173158#c73 --- Comment #73 from Gary Ching-Pang Lin <glin(a)suse.com> --- While branching a nolockdown kernel may work, I wonder how to configure the key signing. Currently all packages under the same project share the same signing key, and if we add a nolockdown flavor to Leap:15.2 or Leap:15.3, then build service has to sign it with a separate key. This is probably not working with the current key setup. A possible solution is to build the nolockdown kernel in a separate project. It could work but add the maintenance effort. -- 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 12 Jul '20

12 Jul '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 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 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 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 kdump: fails to create dump as dump-capture kernel boots into systemd emergency mode -> http://bugzilla.suse.com/show_bug.cgi?id=1172670 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 -- 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 1174033] DELL XPS13 - not resume from hibernate with latest snapshot
by bugzilla_noreply＠suse.com 12 Jul '20

12 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174033 http://bugzilla.opensuse.org/show_bug.cgi?id=1174033#c1 Michael Hirmke <opensuse(a)mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Michael Hirmke <opensuse(a)mike.franken.de> --- Seems to be a kernel problem. Works with 5.7.5 - does not work with 5.7.7. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1173944] New: Kernel 5.3.18-lp152.20.7 doesn't load VirtualBox kernel driver
by bugzilla_noreply＠suse.com 11 Jul '20

11 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173944 Bug ID: 1173944 Summary: Kernel 5.3.18-lp152.20.7 doesn't load VirtualBox kernel driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chris.taylor(a)cantab.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Latest Leap 15.2 Kernel 5.3.18-lp152.20.7-default results in following error when starting a VirtualBox guest. No problems on previous Kernel (e.g. 5.3.18-lp152.19-default). VirtualBox error: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing '/sbin/vboxconfig' as root. If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[kernel-bugs] [Bug 1173912] New: ThinkPad Dock USB Audio - Output distorted
by bugzilla_noreply＠suse.com 11 Jul '20

11 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173912 Bug ID: 1173912 Summary: ThinkPad Dock USB Audio - Output distorted Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: marc(a)hoehn.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since I installed the "openSUSE-SU-2020:0935-1: important: Security update for the Linux Kernel" yesterday it distorted the sound output of my ThinkPad Dock USB audio. Sounds like slow motion. After switching back to kernel verion 5.3.18-lp152.19.2-x86_64 everything workes again. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1174036] New: HDMI out doesn't works.
by bugzilla_noreply＠suse.com 11 Jul '20

11 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174036 Bug ID: 1174036 Summary: HDMI out doesn't works. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: PC OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: hanin(a)tutamail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have ASUS TUF FX505D with NVIDIA Graphic card GTX1050 the HDMI out works perfectly on windows10 and leap15.2 with nouveau driver and doesn't work on opensuse leap15.2 with NVIDIA driver -- You are receiving this mail because: You are the assignee for the bug.

1 10

[kernel-bugs] [Bug 1174017] New: Laptop: one of two usb3 hubs gone with 5.7 - works with 5.3.6 (linux live system)
by bugzilla_noreply＠suse.com 10 Jul '20

10 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1174017 Bug ID: 1174017 Summary: Laptop: one of two usb3 hubs gone with 5.7 - works with 5.3.6 (linux live system) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rs.opensuse(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I've discovered that with 5.7.7 and back to 5.7.2 one of my laptop's internal usb3 hub is just gone (one type c and one type a port). I've tried removing the battery, bios reset etc. It's just GONE. Booting a live system with 5.3.6 works every time - no issues. Same hardware as in bug report 1167146 I will do some testing with other kernel versions and report back. Please let me know what info is required to get my usb ports back. -- You are receiving this mail because: You are the assignee for the bug.

1 5