September 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

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

04 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174800 https://bugzilla.suse.com/show_bug.cgi?id=1174800#c6 --- Comment #6 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/832013 15.2 / kernel-source -- 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 04 Sep '20

04 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c54 --- Comment #54 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Gary Ching-Pang Lin from comment #53) > John, > > Have you seen the MokManager screen with Secure Boot enabled before? I > wonder if it's a drawing problem. (I mean the MokManager from the older shim.) -- 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 04 Sep '20

04 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1175626 http://bugzilla.opensuse.org/show_bug.cgi?id=1175626#c53 --- Comment #53 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Martin Wilck from comment #48) > (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. > MokManager deletes the MokNew after loading it. This is a bug should be fixed. It seems to me that MokManager was loaded but got stuck or just failed to draw the screen. John, Have you seen the MokManager screen with Secure Boot enabled before? I wonder if it's a drawing problem. [snip] > > > > 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. Although mokutil can create a reset request, it seems MokManager cannot be launched reliably, and that's why I recommend a firmware reset. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

04 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176121 https://bugzilla.suse.com/show_bug.cgi?id=1176121#c10 --- Comment #10 from Daniel Wagner <daniel.wagner(a)suse.com> --- FTR, the drm message was today not present when booting mainline 5.8.6. I suspect the graphic card doesn't always reset properly. Thus, I don't think it is related with the crash I saw. -- 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 https://bugzilla.suse.com/show_bug.cgi?id=1175296#c29 --- Comment #29 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2486-1: An update that solves four vulnerabilities and has 116 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1153274,1154353,1154488,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174205,1174247,1174362,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-14331,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Workstation Extension 15-SP2 (src): kernel-default-5.3.18-24.12.1 SUSE Linux Enterprise Module for Live Patching 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-livepatch-SLE15-SP2_Update_2-1-5.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP2 (src): kernel-default-5.3.18-24.12.1 SUSE Linux Enterprise Module for Development Tools 15-SP2 (src): kernel-docs-5.3.18-24.12.1, kernel-obs-build-5.3.18-24.12.1, kernel-preempt-5.3.18-24.12.1, kernel-source-5.3.18-24.12.1, kernel-syms-5.3.18-24.12.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-default-base-5.3.18-24.12.1.9.4.1, kernel-preempt-5.3.18-24.12.1, kernel-source-5.3.18-24.12.1 SUSE Linux Enterprise High Availability 15-SP2 (src): kernel-default-5.3.18-24.12.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#c38 --- Comment #38 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2486-1: An update that solves four vulnerabilities and has 116 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1153274,1154353,1154488,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174205,1174247,1174362,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-14331,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Workstation Extension 15-SP2 (src): kernel-default-5.3.18-24.12.1 SUSE Linux Enterprise Module for Live Patching 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-livepatch-SLE15-SP2_Update_2-1-5.3.1 SUSE Linux Enterprise Module for Legacy Software 15-SP2 (src): kernel-default-5.3.18-24.12.1 SUSE Linux Enterprise Module for Development Tools 15-SP2 (src): kernel-docs-5.3.18-24.12.1, kernel-obs-build-5.3.18-24.12.1, kernel-preempt-5.3.18-24.12.1, kernel-source-5.3.18-24.12.1, kernel-syms-5.3.18-24.12.1 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-default-base-5.3.18-24.12.1.9.4.1, kernel-preempt-5.3.18-24.12.1, kernel-source-5.3.18-24.12.1 SUSE Linux Enterprise High Availability 15-SP2 (src): kernel-default-5.3.18-24.12.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 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#c28 --- Comment #28 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2486-1: An update that solves four vulnerabilities and has 116 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1153274,1154353,1154488,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174205,1174247,1174362,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-14331,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Module for Live Patching 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-livepatch-SLE15-SP2_Update_2-1-5.3.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#c37 --- Comment #37 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2020:2486-1: An update that solves four vulnerabilities and has 116 fixes is now available. Category: security (important) Bug References: 1065600,1065729,1071995,1085030,1120163,1133021,1149032,1152472,1152489,1153274,1154353,1154488,1154492,1155518,1156395,1159058,1160634,1167773,1169790,1171634,1171688,1172108,1172197,1172247,1172418,1172871,1172963,1173468,1173485,1173798,1173813,1173954,1174002,1174003,1174026,1174205,1174247,1174362,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-14331,CVE-2020-14356,CVE-2020-16166 JIRA References: Sources used: SUSE Linux Enterprise Module for Live Patching 15-SP2 (src): kernel-default-5.3.18-24.12.1, kernel-livepatch-SLE15-SP2_Update_2-1-5.3.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 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#c52 --- Comment #52 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- Replying to Martin Wilck comment #48 >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. That cannot actually work. I might have more than one openSUSE system installed on my computer, and those systems all share the same list of enrolled keys. The rpm scripts can only check what is needed for the particular system where it is running. -- 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#c51 --- Comment #51 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Martin Wilck from comment #48) > 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. Probably not, see bug 1176146. -- You are receiving this mail because: You are on the CC list for the bug.

1 0