September 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1175296] network regression with a Realtek RTL8111E network chip
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175296 https://bugzilla.suse.com/show_bug.cgi?id=1175296#c27 --- Comment #27 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2485-1: An update that solves three vulnerabilities and has 112 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1154353,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174387,1174484,1174625,1174645,1174689,1174699,1174737,1174757,1174762,1174770,1174771,1174777,1174805,1174824,1174825,1174852,1174865,1174880,1174897,1174906,1174969,1175009,1175010,1175011,1175012,1175013,1175014,1175015,1175016,1175017,1175018,1175019,1175020,1175021,1175052,1175112,1175116,1175128,1175149,1175175,1175176,1175180,1175181,1175182,1175183,1175184,1175185,1175186,1175187,1175188,1175189,1175190,1175191,1175192,1175195,1175199,1175213,1175232,1175263,1175284,1175296,1175344,1175345,1175346,1175347,1175367,1175377,1175440,1175493,1175546,1175550,1175654,1175691,1175768,1175769,1175770,1175771,1175772,1175774,1175775,1175834,1175873 CVE References: CVE-2020-14314,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.15.1, kernel-source-azure-5.3.18-18.15.1, kernel-syms-azure-5.3.18-18.15.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1174737] kernel-default-5.3.18-lp152.33.1.x86_64 hard lockup
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174737 https://bugzilla.suse.com/show_bug.cgi?id=1174737#c36 --- Comment #36 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2485-1: An update that solves three vulnerabilities and has 112 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1154353,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174387,1174484,1174625,1174645,1174689,1174699,1174737,1174757,1174762,1174770,1174771,1174777,1174805,1174824,1174825,1174852,1174865,1174880,1174897,1174906,1174969,1175009,1175010,1175011,1175012,1175013,1175014,1175015,1175016,1175017,1175018,1175019,1175020,1175021,1175052,1175112,1175116,1175128,1175149,1175175,1175176,1175180,1175181,1175182,1175183,1175184,1175185,1175186,1175187,1175188,1175189,1175190,1175191,1175192,1175195,1175199,1175213,1175232,1175263,1175284,1175296,1175344,1175345,1175346,1175347,1175367,1175377,1175440,1175493,1175546,1175550,1175654,1175691,1175768,1175769,1175770,1175771,1175772,1175774,1175775,1175834,1175873 CVE References: CVE-2020-14314,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.15.1, kernel-source-azure-5.3.18-18.15.1, kernel-syms-azure-5.3.18-18.15.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1176121] kernel 5.8.4-1-default: crash during boot
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176121 https://bugzilla.suse.com/show_bug.cgi?id=1176121#c9 Daniel Wagner <daniel.wagner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #9 from Daniel Wagner <daniel.wagner(a)suse.com> --- Not sure if I got the right commit. So I used eba08ea7422a ("- Linux 5.8.4 (bsc#1012628).") and it boots just fine. And no drm worshiping timeout. Well, it's hard to say what upset my setup. I think we can close this bug, there is not much do to right now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175296] network regression with a Realtek RTL8111E network chip
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175296 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=209081 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1175541] workqueue lockup and freeze
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175541 https://bugzilla.suse.com/show_bug.cgi?id=1175541#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(P.Suetterlin@roya | |c.iac.es) --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Does it still happen with the recent Nvidia package? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[kernel-bugs] [Bug 1176104] DVB tuning fails after hibernation
by bugzilla_noreply＠suse.com 03 Sep '20

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176104 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=201467 -- 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 03 Sep '20

03 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c50 --- Comment #50 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Marcus Meissner from comment #49) > serial FABED8BF409A5E63 is the new one post-boothole > serial FABED8BF409A5E60 is the one before boothole That makes sense. Thanks, I could have figured that I guess. I still reckon we lack a web page somewhere where users can look up the fingerprints and check (bug 1174490). For a situation like boothole, that would be extremely worthwhile. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

03 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175626 https://bugzilla.suse.com/show_bug.cgi?id=1175626#c49 --- Comment #49 from Marcus Meissner <meissner(a)suse.com> --- serial FABED8BF409A5E63 is the new one post-boothole serial FABED8BF409A5E60 is the one before boothole -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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#c48 --- Comment #48 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Gary Ching-Pang Lin from comment #45) > 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. How would MokNew go away? The scriptlets in the kernel rpm are written so that the keys won't be deleted as long as the system still has one kernel installed that needs them. Why do we have different signkeys for Leap 15.2, anyway? > ~ # rpm -qlp /var/cache/zypp/packages/repo-oss/x86_64/kernel-default-5.3.18-lp152.19.2.x86_64.rpm | grep crt > /etc/uefi/certs/F1C08E27.crt > ~ # rpm -qlp /var/cache/zypp/packages/repo-update/x86_64/kernel-default-5.3.18-lp152.33.1.x86_64.rpm | grep crt > /etc/uefi/certs/F1C08E27.crt > ~ # rpm -qlp /var/cache/zypp/packages/repo-update/x86_64/kernel-default-5.3.18-lp152.33.1.x86_64.rpm /var/cache/zypp/packages/repo-update/x86_64/kernel-default-5.3.18-lp152.36.1.x86_64.rpm | grep crt > /etc/uefi/certs/F1C08E27.crt > /etc/uefi/certs/33CEA71B.crt We've got two signkeys here with the same subject and slightly different serial number and validity. I guess it depends on the OBS project the kernel's built in, but it's intransparent and confusing for users. == /etc/uefi/certs/33CEA71B.crt == issuer=CN = openSUSE Secure Boot CA, C = DE, L = Nuremberg, O = openSUSE Project, emailAddress = build(a)opensuse.org serial=FABED8BF409A5E63 subject=CN = openSUSE Secure Boot Signkey, C = DE, L = Nuremberg, O = openSUSE Project, emailAddress = build(a)opensuse.org notBefore=Aug 3 12:35:39 2020 GMT notAfter=Jun 12 12:35:39 2030 GMT SHA1 Fingerprint=33:CE:A7:1B:A1:6A:67:BA:D8:6B:93:CB:DA:2E:19:A7:E9:DF:95:66 X509v3 Subject Key Identifier: C8:BD:C7:AC:1A:1D:85:96:62:17:FD:93:EB:FC:14:F4:A2:00:B8:14 == /etc/uefi/certs/F1C08E27.crt == issuer=CN = openSUSE Secure Boot CA, C = DE, L = Nuremberg, O = openSUSE Project, emailAddress = build(a)opensuse.org serial=FABED8BF409A5E60 subject=CN = openSUSE Secure Boot Signkey, C = DE, L = Nuremberg, O = openSUSE Project, emailAddress = build(a)opensuse.org notBefore=Jan 8 16:25:54 2020 GMT notAfter=Nov 16 16:25:54 2029 GMT SHA1 Fingerprint=F1:C0:8E:27:F3:5F:3F:39:C5:5C:CB:F8:58:18:C6:27:DF:49:4E:34 X509v3 Subject Key Identifier: 03:32:FA:9C:BF:0D:88:BF:21:92:4B:0D:E8:2A:09:A5:4D:5D:EF:C8 > > I forced Yast to > > reinstall them, rebooted, and its now working (not SecureBoot). The forced reinstall may have caused harm. When you reinstall (and the version number of the nvidia-gfxG05-kmp-default package is the same as before), the installation procedure will generate a new key with the same file name, overwriting the previous one. Because of rpm scriptlet ordering (%postun is executed after %post), this might lead to the old key remaining present and the new one not being enrolled. I'm not 100% certain about this, but I guess it could happen. It's safer to delete the package and install it again. I'm not saying this is the user's fault. It's rather a corner case that we may have overlooked. It does not apply to the kernel packages. > 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. Isn't this is an overkill recommendation? It should be only a last resort measure. Perhaps MokManager should have an option to reset the MokList only. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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#c47 --- Comment #47 from John Shaw <johngshaw(a)twc.com> --- (In reply to Gary Ching-Pang Lin from comment #46) > BTW, I still would like to know whether "mokutil --set-verbosity true" makes > shim print more messages before the blank screen. I hope it could provide > some hints to the blank screen. The answer to this is no. Its possible something flashes between POST and the black screen of death, but it is on for only ~1 frame so its impossible to read. If its the BIOS, and no efi code is run, then there is nothing that could be done, but maybe any efi code should attempt to write some sort of simple diagnostics along the way (no matter what, it can be cleared if you get to a useful screen). Someone made a comment that my "BIOS may be broken". I wonder if that is true. If SecureBoot could not load anything one would think I would see a red message stating so. I have seen such a thing once or twice soon after I installed 15.2 (due to missing the MOK Manager page), but not that never happens. -- You are receiving this mail because: You are on the CC list for the bug.

1 0