Activity log for bug #1969432
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2022-04-19 07:40:27 | Yuan-Chen Cheng | bug | added bug | ||
| 2022-04-19 07:40:45 | Yuan-Chen Cheng | information type | Proprietary | Public | |
| 2022-04-19 07:41:28 | Yuan-Chen Cheng | tags | oem-priority | ||
| 2022-04-19 07:42:26 | Yuan-Chen Cheng | attachment added | 5.15.dmesg.log https://bugs.launchpad.net/oem-priority/+bug/1969432/+attachment/5581393/+files/5.15.dmesg.log | ||
| 2022-04-19 07:42:50 | Yuan-Chen Cheng | attachment added | 5.17.dmesg.log https://bugs.launchpad.net/oem-priority/+bug/1969432/+attachment/5581394/+files/5.17.dmesg.log | ||
| 2022-04-19 08:26:06 | Yuan-Chen Cheng | oem-priority: assignee | Yuan-Chen Cheng (ycheng-twn) | ||
| 2022-04-27 09:37:22 | Yuan-Chen Cheng | bug | added subscriber OEM Solutions Group: Engineers | ||
| 2022-04-27 09:37:26 | Yuan-Chen Cheng | tags | oem-priority | oem-priority originate-from-1969557 somerville | |
| 2022-05-04 07:50:36 | Timo Aaltonen | bug task added | linux-oem-5.17 (Ubuntu) | ||
| 2022-05-04 07:50:45 | Timo Aaltonen | bug task added | linux (Ubuntu) | ||
| 2022-05-04 08:00:08 | Ubuntu Kernel Bot | linux (Ubuntu): status | New | Incomplete | |
| 2022-05-10 07:49:55 | AceLan Kao | linux-oem-5.17 (Ubuntu): importance | Undecided | Critical | |
| 2022-05-10 07:50:03 | AceLan Kao | linux-oem-5.17 (Ubuntu): importance | Critical | Undecided | |
| 2022-05-12 07:25:02 | Yuan-Chen Cheng | oem-priority: assignee | Yuan-Chen Cheng (ycheng-twn) | ||
| 2022-05-16 13:11:08 | Yuan-Chen Cheng | description | Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [ 0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [ 0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' | lp:1972802 Steps to reproduce: 1. enroll mok, and use the mok to sign dkms 2. make sure secure boot is on, and boots with kernel 3. load the kernel by either modprobe or insmod. Expected: the kernel module can be loaded. Actually: the kernel module can't be loaded. Failed kernel: 5.17.0-1003-oem Passed kernel: 5.15.0-25-generic With 5.17 kernel, using command "dmesg | grep 509", I can't see the mok key. With 5.15 kernel above, I can see the mok key is loaded like: [ 0.896168] integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) [ 0.896283] integrity: Loaded X.509 cert 'ubuntu Secure Boot Module Signature key: 670bc7d76f65d9cfc786f5501de6af89bf3973e7' | |
| 2022-06-02 08:17:20 | Yuan-Chen Cheng | oem-priority: status | Confirmed | Fix Committed | |
| 2022-06-08 00:14:07 | Yuan-Chen Cheng | oem-priority: status | Fix Committed | Fix Released | |
| 2022-06-08 00:14:17 | Yuan-Chen Cheng | linux-oem-5.17 (Ubuntu): status | New | Fix Released |
