September 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 03 Sep '20

03 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c45 --- Comment #45 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to John Shaw from comment #43) > (In reply to Gary Ching-Pang Lin from comment #38) > > 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 > > This seemed to be working on my machine after the last round of grub2 > updates went through, then this morning a new nVidia driver update came > (along with about 20 other updates). On reboot with SecureBoot enabled, the > machine hung after post with a black screen. I rebooted with SecureBoot > disabled (ie, selected OtherOS in the ASUS bios), and it brought up the MOK > Manager. However, unlike before the options are now different. There is no > "enrole MOK", just: Continue, Reset MOK, Delete MOK, and enrole key and > enrole hash from disk. > I guess the update of kernel triggered the enrollment of new signkey and the deletion of the old signkey. But somehow MokNew was gone, so MokManager thought that there was a reset. > Its unclear what to enrole. I basically gave up and rebooted without > SecureBoot and still did not have working video drivers. I forced Yast to > reinstall them, rebooted, and its now working (not SecureBoot). I guess at > this point, I will just keep SecureBoot disabled. Its scary what would > happen if I did not have that option, or for some reason I wanted to dual > boot with windows. > > Its possible the keys are all screwed up somehow on my machine (there are a > number saved accordingto mokutil, but noththing that looks related to > nvidia). Is there a simple way to reset the whole MOK status without > reinstalling the OS (yet again)? Its not clear that that would reset the > keys stored in the BIOS. Reinstalling OS won't change MokList. The most reliable way is to reset the firmware to factory default. You'll need to restore the boot entries after that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172951 http://bugzilla.opensuse.org/show_bug.cgi?id=1172951#c44 --- Comment #44 from m j <1chip(a)protonmail.com> --- Created attachment 841319 --> http://bugzilla.opensuse.org/attachment.cgi?id=841319&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1172951 https://bugzilla.suse.com/show_bug.cgi?id=1172951#c43 --- Comment #43 from Takashi Iwai <tiwai(a)suse.com> --- OK, so far, so good. Now, please test suspend/resume, and confirm whether the touchpad works. If the problem persists, please upload the dmesg output taken after the resume again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172951 http://bugzilla.opensuse.org/show_bug.cgi?id=1172951#c42 --- Comment #42 from m j <1chip(a)protonmail.com> --- Created attachment 841318 --> http://bugzilla.opensuse.org/attachment.cgi?id=841318&action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172951 http://bugzilla.opensuse.org/show_bug.cgi?id=1172951#c41 --- Comment #41 from m j <1chip(a)protonmail.com> --- sorry, added the new file -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1172951 https://bugzilla.suse.com/show_bug.cgi?id=1172951#c40 --- Comment #40 from Takashi Iwai <tiwai(a)suse.com> --- Erm, your dmesg output shows that you're running 5.3.18-lp152.36-default, which is the official update kernel, and not the test kernel I've provided. It's likely because you didn't choose explicitly the kernel to boot at GRUB menu. The test kernel has a smaller version number, 5.3.18-lp152.1.1.g00a927a, so please choose this kernel at GRUB boot menu, and test with it. BTW, you can check the version of the running kernel by "uname -r" command. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172951 http://bugzilla.opensuse.org/show_bug.cgi?id=1172951#c39 --- Comment #39 from m j <1chip(a)protonmail.com> --- Created attachment 841313 --> http://bugzilla.opensuse.org/attachment.cgi?id=841313&action=edit sept2dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1172951 http://bugzilla.opensuse.org/show_bug.cgi?id=1172951#c38 --- Comment #38 from m j <1chip(a)protonmail.com> --- ok, I rebooted and everything works fine -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1172951] Trackpoint/Trackpad gone/unfunctional after resume (closing/opening LID cycle) [kernel issue]
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1172951 https://bugzilla.suse.com/show_bug.cgi?id=1172951#c37 --- Comment #37 from Takashi Iwai <tiwai(a)suse.com> --- Could you upload the dmesg output from the kernel you've tested? Just to confirm whether it hits the same problem or not. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1170232] Kernel spec self obsoletes
by bugzilla_noreply＠suse.com 02 Sep '20

02 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1170232 https://bugzilla.suse.com/show_bug.cgi?id=1170232#c14 --- Comment #14 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:1325-1: An update that solves 6 vulnerabilities and has 107 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1083548,1085030,1085308,1087082,1111666,1112178,1113956,1133021,1144333,1152148,1163524,1165629,1166965,1169790,1170232,1171688,1172073,1172108,1172418,1172428,1172783,1172871,1172872,1172873,1172963,1173485,1173798,1173954,1174003,1174026,1174205,1174387,1174484,1174547,1174550,1174625,1174689,1174699,1174734,1174771,1174852,1174873,1174904,1174926,1174968,1175062,1175063,1175064,1175065,1175066,1175067,1175112,1175127,1175128,1175149,1175199,1175213,1175228,1175232,1175284,1175393,1175394,1175396,1175397,1175398,1175399,1175400,1175401,1175402,1175403,1175404,1175405,1175406,1175407,1175408,1175409,1175410,1175411,1175412,1175413,1175414,1175415,1175416,1175417,1175418,1175419,1175420,1175421,1175422,1175423,1175440,1175493,1175515,1175518,1175526,1175550,1175654,1175666,1175667,1175668,1175669,1175670,1175767,1175768,1175769,1175770,1175771,1175772,1175786,1175873 CVE References: CVE-2018-3639,CVE-2020-14314,CVE-2020-14331,CVE-2020-14356,CVE-2020-1749,CVE-2020-24394 JIRA References: Sources used: openSUSE Leap 15.1 (src): kernel-debug-4.12.14-lp151.28.63.1, kernel-default-4.12.14-lp151.28.63.1, kernel-docs-4.12.14-lp151.28.63.1, kernel-kvmsmall-4.12.14-lp151.28.63.1, kernel-obs-build-4.12.14-lp151.28.63.1, kernel-obs-qa-4.12.14-lp151.28.63.1, kernel-source-4.12.14-lp151.28.63.1, kernel-syms-4.12.14-lp151.28.63.1, kernel-vanilla-4.12.14-lp151.28.63.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0