[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
bisecting kernel from the 6.5.0-42 to latest master-next, the patch "x86/boot: Omit compression buffer from PE/COFF image memory footprint" also causes fail to boot up. 03651c884514d311fa3e628ac073afbad04e5c57 is the first bad commit commit 03651c884514d311fa3e628ac073afbad04e5c57 Author: Ard Biesheuvel Date: Tue Sep 12 09:00:56 2023 + x86/boot: Omit compression buffer from PE/COFF image memory footprint BugLink: https://bugs.launchpad.net/bugs/2061814 commit 8eace5b3555606e684739bef5bcdfcfe68235257 upstream. Now that the EFI stub decompresses the kernel and hands over to the decompressed image directly, there is no longer a need to provide a decompression buffer as part of the .BSS allocation of the PE/COFF image. It also means the PE/COFF image can be loaded anywhere in memory, and setting the preferred image base is unnecessary. So drop the handling of this from the header and from the build tool. Signed-off-by: Ard Biesheuvel Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20230912090051.4014114-22-a...@google.com Signed-off-by: Greg Kroah-Hartman Signed-off-by: Portia Stephens Signed-off-by: Roxana Nicolescu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
Tested with the test kernel 6.5.0-42, https://launchpad.net/~roxanan/+archive/ubuntu/thermal/+packages unfortunately, got fail to boot up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
Test with latest proposed kernel Ubuntu-6.5.0-40.40, can boot up without problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
@Roxana, Checkout tag Ubuntu-6.5.0-34.34 and revert two patches below, it can boot up without problem. thermal: core: Store trip pointer in struct thermal_instance thermal: trip: Drop lockdep assertion from thermal_zone_trip_id() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
Test latest master-next of mantic with below two patches, thermal: trip: Drop redundant trips check from for_each_thermal_trip() thermal: core: Rework and rename __for_each_thermal_trip() still failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
seems 6.6.x has this in addition for apply the "thermal: trip: Drop redundant trips check from for_each_thermal_trip()" thermal: core: Rework and rename __for_each_thermal_trip() Rework the currently unused __for_each_thermal_trip() to pass original pointers to struct thermal_trip objects to the callback, so it can be used for updating trip data (e.g. temperatures), rename it to for_each_thermal_trip() and make it available to modular drivers. Suggested-by: Daniel Lezcano Signed-off-by: Rafael J. Wysocki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
bisect kernel result, the patch 2c7b4bfadef08cc0995c24a7b9eb120fe897165f causes this regression thermal: core: Store trip pointer in struct thermal_instance Replace the integer trip number stored in struct thermal_instance with a pointer to the relevant trip and adjust the code using the structure in question accordingly. The main reason for making this change is to allow the trip point to cooling device binding code more straightforward, as illustrated by subsequent modifications of the ACPI thermal driver, but it also helps to clarify the overall design and allows the governor code overhead to be reduced (through subsequent modifications). The only case in which it adds complexity is trip_point_show() that needs to walk the trips[] table to find the index of the given trip point, but this is not a critical path and the interface that trip_point_show() belongs to is problematic anyway (for instance, it doesn't cover the case when the same cooling devices is associated with multiple trip points). This is a preliminary change and the affected code will be refined by a series of subsequent modifications of thermal governors, the core and the ACPI thermal driver. The general functionality is not expected to be affected by this change. Signed-off-by: Rafael J. Wysocki Reviewed-by: Daniel Lezcano -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
testing with Ubuntu-6.5.0-28-generic without this issue, bisecting kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
testing with Ubuntu-6.5.0-32-generic, it can't boot up as well. ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049733] Re: Dynamically determine acpi_handle_list size
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049733 Title: Dynamically determine acpi_handle_list size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060981] Re: ACPI BIOS errors
From the acpidump log on comment#2, this is buggy bios uses below objects but are not actually implemented. all on the ssdt2(DptfTabl) table, \CTDP, \_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT, \_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT, \_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT, \_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT, \_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT, \_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT, \_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT, \_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT, \_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT, \_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT, \_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT, \_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT, \_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT, \_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT, \_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT, All these objects are related DPTF, you should reach your machine vendor for update bios. There is nothing can do on Ubuntu side. ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060981] Re: ACPI BIOS errors
ACPI AE_NOT_FOUND errors usually come from buggy firmware which uses the objects but not actually implemented. Can spot which parts of firmware errors if you can support acpidump log. $sudo acpidump > acpidump.log ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060981] Re: ACPI BIOS errors
** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972802] Re: enable config for fixing 5.17 kernel won't load mok
** Description changed: [Impact] Mok keys is not trusted after kernel 5.17 [Fix] Enable the CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT and CONFIG_IMA_ARCH_POLICY for fixing the patch "[patch] integrity: Do not load MOK and MOKx when secure boot be disabled" was added to check if secureboot enabled for trusting the MOK key [Test] Enroll Mok key and use it to sign kernel modules, make sure secure boot is on and load the kernel module by either modprobe or insmod. - [Regression Risk] + [Where problems could occur] Low. only affect the checking secureboot enable function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972802 Title: enable config for fixing 5.17 kernel won't load mok To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1972802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956914] Re: Can't resume from suspend on some specific systems using fwts 21.12
@Kevin, Yes, the commit 713284e505287611c7e1e6ae61254de3035433b5 add the "-- s3-sleep-type" sleep type selection and make S3(deep) as default if not specified. for those failed platforms, don't they support S3? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956914 Title: Can't resume from suspend on some specific systems using fwts 21.12 To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1956914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956914] Re: Can't resume from suspend on some specific systems using fwts 21.12
Is there any reason that "deep" cannot work? Shuuld it be an issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956914 Title: Can't resume from suspend on some specific systems using fwts 21.12 To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1956914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
Follow up the tests for comment#12, the same test kernel v5.14.0-rc7 signed with the original created key in /var/lib/shim-signed/test_kernel will not boot up with getting the invalid signature error. compare the keys between /var/lib/shim-signed/test_kernel and comment#12(/var/lib/test_ker/), the fail one(in /var/lib/shim- signed/test_kernel) has the (1.3.6.1.4.1.2312.16.1.2) KeyUsage OID. It seems it is because using the "Module-signing only" (1.3.6.1.4.1.2312.16.1.2) KeyUsage OID to sign the test kernel that cause signature verify failed. @YC I know the OEM projects base on the my EFI applicaiton and script to generate/enroll MOK keys for test kernels, https://github.com/Ivanhu5866/MokEnrollKey/blob/master/mok_testkernel_key.sh Could you provide the exact script how the MOK has been generated/enrolled and maybe openssl.cnf for checking? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
Got the Latitude 7520 machine, from the shim's log, it seems something wrong in the self signed certificate and the binary is not authorized. And do some tests, basically base on the comment#6, install another test kernel and signed/enrolled with another MOK key manually. 1. install test kernel(unsigned), v5.14.0-rc7 2. shim and grub have already been updated. 3. create a MOK key * mkdir -p /var/lib/test_ker/ * openssl genrsa -out /var/lib/test_ker/TestKer.priv 2048 * openssl req -new -x509 -sha256 -subj '/CN=TestKer-key' -key /var/lib/test_ker/TestKer.priv -out /var/lib/test_ker/TestKer.pem * openssl x509 -in /var/lib/test_ker/TestKer.pem -inform PEM -out /var/lib/test_ker/TestKer.der -outform DER 4. signed kernel * sbsign --key /var/lib/test_ker/TestKer.priv --cert /var/lib/test_ker/TestKer.pem --output vmlinuz-5.14.0-051400rc7-generic.signed vmlinuz-5.14.0-051400rc7-generic 6. enroll mok key * mokutil --import Testker.der 7. reboot The test kernel 5.14 and MOK key work normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
Test again with my UEFI develop kit(RainbowPass) platform by following procedures and still cannot reproduce this issue. 1. install focal 2. update shim-signed to 1.40.6+15.4.0ubuntu7 and grub2 to 2.04-1ubuntu26.12 3. install mainline kernel(unsigned), https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/ 4. signed kernel module and enrolled key to MOK( install a DKMS and followed the official procedures) 5. run the script and EFI application to signed key and enroll key to MOK(need to disable secureboot first), https://github.com/Ivanhu5866/MokEnrollKey/blob/master/mok_testkernel_key.sh this basically is the same procedure as OEM image installation. 6. reboot @YC per talk, please enable the shim log for me to check first by $sudo mokutil --set-verbosity true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
After singing kernel modules and enroll key to MOK, still cannot reproduce this with my UEFI develop kit(RainbowPass) platform. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
Manually test with my UEFI develop kit(RainbowPass) platform by following procedures and cannot reproduce this issue. 1. install focal 2. update shim-signed to 1.40.6+15.4.0ubuntu7 and grub2 to 2.04-1ubuntu26.12 3. install mainline kernel(unsigned), https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/ 4. check or create test kernel key * mkdir -p /var/lib/test_ker/ * openssl genrsa -out /var/lib/test_ker/TestKer.priv 2048 * openssl req -new -x509 -sha256 -subj '/CN=TestKer-key' -key /var/lib/test_ker/TestKer.priv -out /var/lib/test_ker/TestKer.pem * openssl x509 -in /var/lib/test_ker/TestKer.pem -inform PEM -out /var/lib/test_ker/TestKer.der -outform DER 5. signed kernel * sbsign --key /var/lib/test_ker/TestKer.priv --cert /var/lib/test_ker/TestKer.pem --output vmlinuz-5.8.18-05.0818-generic.signed vmlinuz-5.8.18-05.0818-generic 6. enroll mok key * mokutil --import Testker.der 7. reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H
The setting, Go to Advanced menu> TPM configuration > TCG2 Configuration > enable PCR Bank PCR Bank: SM3_256 [x ] is for PCR Bank supported Hash Algorithm. Here, what Ethan mentioned is for remove the SM3_256 supported for the platform, not only the PCR bank SM3_256 supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938678 Title: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939565] Re: kernel signed by mok failed to boot if secure boot is on
@ycheng-twn Have you also updated the Grub2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939565 Title: kernel signed by mok failed to boot if secure boot is on To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1939565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H
Snapd is not using the tpm2-tss, so it is not the same as mentioned in https://bugs.launchpad.net/intel/+bug/1936899/comments/10. Instead, snapd is using go-tpm2 from comment#15. Per talk to Ethan, he is building newer version which has some defined values of SM3_256 for testing, let's wait for the testing result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938678 Title: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail
For the tpm2_loadexternal, and tpm2_import tests, the failure seems from RSA private key 1024 bit no support for this platform. So TPM returned ErrorCode (0x02c4), "value is out of range or is not correct for the context" + openssl genrsa -aes128 -passout pass:mypassword -out private.pem 1024 Generating RSA private key, 1024 bit long modulus (2 primes) .+ ...+ e is 65537 (0x010001) + '[' pass:mypassword '!=' stdin ']' + cmd='tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin pass:mypassword' + eval tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin pass:mypassword ++ tpm2_loadexternal -Q -G rsa -r private.pem -c key.ctx --passin pass:mypassword WARNING:esys:src/tss2-esys/api/Esys_LoadExternal.c:304:Esys_LoadExternal_Finish() Received TPM Error ERROR:esys:src/tss2-esys/api/Esys_LoadExternal.c:108:Esys_LoadExternal() Esys Finish ErrorCode (0x02c4) ERROR: Esys_LoadExternal(0x2C4) - tpm:parameter(2):value is out of range or is not correct for the context ERROR: Unable to run tpm2_loadexternal From the PTP spec"TCG PC Client Platform TPM Profile Specification for TPM 2.0", Table2. PC Client TPM Algorithms It described, TPM_ALG_RSA M Support for 2048-bit keys is required; the TPM SHOULD NOT support 1024-bit keys. So I think this could be safely ignored, if 1024 key is not supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936899 Title: [IoTG] [TGL-H] TPM tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail
For the tpm2_createprimary tests,
The failures are both from tpm2_createprimary whit hash-algorithm
sm3_256
+ tpm2_createprimary -Q -g sm3_256 -G rsa -c context.out
ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:103:iesys_cryptossl_hash_start()
ErrorCode (0x00070002) Unsupported hash algorithm (18)
ERROR:esys:src/tss2-esys/esys_iutil.c:1493:iesys_get_name() crypto hash start
ErrorCode (0x00070002)
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:426:Esys_CreatePrimary_Finish()
ErrorCode (0x00070011) in Public name not equal name in response
ERROR:esys:src/tss2-esys/api/Esys_CreatePrimary.c:135:Esys_CreatePrimary() Esys
Finish ErrorCode (0x00070011)
ERROR: Esys_CreatePrimary(0x70011) - esapi:Response is malformed
ERROR:esys:src/tss2-esys/esys_iutil.c:1134:iesys_check_sequence_async() Esys
called in bad sequence.
ERROR:esys:src/tss2-esys/api/Esys_FlushContext.c:66:Esys_FlushContext() Error
in async function ErrorCode (0x00070007)
ERROR: Esys_FlushContext(0x70007) - esapi:Function called in the wrong order
ERROR: Unable to run tpm2_createprimary
the latest tpm2_tests will first check the platform supported hash algorithms,
then do the tests with the hash algorithms.
But test with it, got
ERROR:esys_crypto:src/tss2-esys/esys_crypto_ossl.c:103:iesys_cryptossl_hash_start()
ErrorCode (0x00070002) Unsupported hash algorithm (18)
Checking the tpm2-tss code, the sm3_256, so got the Unsupported hash algorithm
return from tpm2-tss.
Below is the tss support hash,
get_ossl_hash_md(TPM2_ALG_ID hashAlg)
{
switch (hashAlg) {
case TPM2_ALG_SHA1:
return EVP_sha1();
break;
case TPM2_ALG_SHA256:
return EVP_sha256();
break;
case TPM2_ALG_SHA384:
return EVP_sha384();
break;
case TPM2_ALG_SHA512:
return EVP_sha512();
break;
default:
return NULL;
}
}
From the latest Spec "TCG PC Client Platform TPM Profile Specification for TPM
2.0, Version 1.05
Revision 14 September 4, 2020"
I found that "sm3_256" is optional.
So, I think this failure could be safely ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936899
Title:
[IoTG] [TGL-H] TPM tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail
For the tpm2_clockrateadjust test fail, + tpm2_clockrateadjust s WARNING:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:287:Esys_ClockRateAdjust_Finish() Received TPM Error ERROR:esys:src/tss2-esys/api/Esys_ClockRateAdjust.c:100:Esys_ClockRateAdjust() Esys Finish ErrorCode (0x01c4) ERROR: Esys_ClockRateAdjust(0x1C4) - tpm:parameter(1):value is out of range or is not correct for the context ERROR: Unable to run tpm2_clockrateadjust it occurred on the tpm2_clockrateadjust to slow down the clock period one fine increment and got the "value is out of range or is not correct for the context" from TPM. It is due to the platform unsupported the clock rate adjust, it is known that some firmware TPM do not support this function, please check if this platform is firmware TPM, and check with your TPM vendors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936899 Title: [IoTG] [TGL-H] TPM tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933547] Re: tpm driver causes non-fatal kernel crash on boot
The kernel seems try to set up the interrupt and send data, but failed. After got error returned, the kernel will disable interrupt and using polling instead. I beleve it will have the following messages in dmesg log kernel: tpm tpm0: tpm_try_transmit: send(): error -62 kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead The call trace seems from the patch which add the checking for the invalid status, https://patchwork.kernel.org/project/linux-integrity/patch/9bad3da0c31ae2620aaae0d75748c3387afa3d47.ca...@hansenpartnership.com/#23649371 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933547 Title: tpm driver causes non-fatal kernel crash on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909734] Re: TPM PCR checking will fail if the all characters are 0
There are bugs in the fwupd for reconstruct the PCR value on some platforms. https://github.com/fwupd/fwupd/pull/2394 >From the comment#1, tested pass with the new fwupd version. ** Changed in: fwts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909734 Title: TPM PCR checking will fail if the all characters are 0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1909734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
Test done with the proposed version, 4.1.1-1ubuntu0.20.04.1 on focal and 4.3.0-1ubuntu0.20.10 on groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
test done with focal and groovy, $sudo tpm2_nvdefine nv-index: 0x102 ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff for hirsute ** Attachment added: "debdiff_hirsute" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5438713/+files/debdiff_hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff for hirsute ** Attachment added: "debdiff_hirsute" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5438712/+files/debdiff_hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff for groovy?field.comment=attached the debdiff for groovy ** Attachment added: "debdiff_groovy" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5438690/+files/debdiff_groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff for focal ** Attachment added: "debdiff_focal_v2" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5438644/+files/debdiff_focal_v2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
** Description changed: nvdefind tool takes the size MAX_NV_INDEX_SIZE(2048) as default, but got errors(0x2D5) returned on those platforms which don't have the size as default. https://github.com/tpm2-software/tpm2-tools/issues/2171 [Impact] - Some machines which don't have enough MAX_NV_INDEX_SIZE as default will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area + Some machines which don't have enough MAX_NV_INDEX_SIZE as default will get "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area [Test cases] run nvdefine without specifying the size of data area [Solution] A fix patch has been committed and accepted by maintainer https://github.com/tpm2-software/tpm2-tools/commit/48594efa6f1faca50c73ce0d88f6e99eb0f5005c [Regression Potential] Minimal, it fixed the issue by checking the platform capabilities instead of using default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff for focal ** Attachment added: "debdiff_focal" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5428321/+files/debdiff_focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] [NEW] tpm2_nvdefine without specifying the size issue
Public bug reported: nvdefind tool takes the size MAX_NV_INDEX_SIZE(2048) as default, but got errors(0x2D5) returned on those platforms which don't have the size as default. https://github.com/tpm2-software/tpm2-tools/issues/2171 [Impact] Some machines which don't have enough MAX_NV_INDEX_SIZE as defaule will got "the structure is the wrong size(0x2D5)" error when using tpm2_nvdefine without specifying the size of data area [Test cases] run nvdefine without specifying the size of data area [Solution] A fix patch has been committed and accepted by maintainer https://github.com/tpm2-software/tpm2-tools/commit/48594efa6f1faca50c73ce0d88f6e99eb0f5005c [Regression Potential] Minimal, it fixed the issue by checking the platform capabilities instead of using default. ** Affects: tpm2-tools (Ubuntu) Importance: Undecided Status: New ** Affects: tpm2-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tpm2-tools (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899460] Re: tpm2_nvdefine without specifying the size issue
attached the debdiff ** Attachment added: "tpm2-debdiff" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+attachment/5421237/+files/tpm2-debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899460 Title: tpm2_nvdefine without specifying the size issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1899460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884485] [NEW] 15+1533136590.3beb971-0ubuntu1 fail to build with gcc9(focal)
Public bug reported: The latest shim upload does not seem able to build with gcc9(under Focal). Got error message, MokManager.c: In function ‘write_back_mok_list’: MokManager.c:1080:19: error: taking address of packed member of ‘struct ’ may result in an unaligned pointer value [-Werror=address-of-packed-member] 1080 | if (CompareGuid(&(list[i].Type), _GUID) == 0) | ^~~ ... But it can be built with the version shim 15+1552672080.a4a1fbe-0ubuntu1. It seems because the Gcc9 fixing patches, MokManager: Use CompareMem on MokListNode.Type instead of CompareGuid(aaa09b35e73c4a35fc119d225e5241199d7cf5aa) MokManager: avoid -Werror=address-of-packed-member(58532e12e9aa207e3c14096f4f5d6f7900130c52) are removed from 15+1552672080.a4a1fbe-0ubuntu1. ** Affects: shim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884485 Title: 15+1533136590.3beb971-0ubuntu1 fail to build with gcc9(focal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1884485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
After restore OS to factory state and directly update intel-microcode by "apt install intel-microcode", then will meet this issue. this should be the intel-microcode issue. the info of intel-microcode, before update, [1.131499] microcode: sig=0x806eb, pf=0x80, revision=0xc6 [1.132064] microcode: Microcode Update Driver: v2.2. after update [0.00] microcode: microcode updated early to revision 0xd6, date = 2020-04-27 [1.156375] microcode: sig=0x806eb, pf=0x80, revision=0xd6 [1.156916] microcode: Microcode Update Driver: v2.2. lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz Stepping:11 CPU MHz: 989.418 CPU max MHz: 3900. CPU min MHz: 400. BogoMIPS:3600.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache:256K L3 cache:6144K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp flush_l1d arch_capabilities -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
After restore OS to factory state and directly update to latest kernel with "apt install linux-oem", it will not hang. It seems not the kernel issue. May upgrade certain package that cause the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881710] Re: tpm: fix TIS locality timeout problems
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
Status: New => In Progress
** Description changed:
[Impact]
It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
- Link: https://patchwork.kernel.org/patch/11576453/
+ PatchLink: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid
locking in NONBLOCKING mode").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881710] Re: tpm: fix TIS locality timeout problems
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux-oem-osp1 (Ubuntu Focal) ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux-oem-5.6 (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881710 Title: tpm: fix TIS locality timeout problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881710] Re: tpm: fix TIS locality timeout problems
** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881710 Title: tpm: fix TIS locality timeout problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881710] [NEW] tpm: fix TIS locality timeout problems
Public bug reported:
[Impact]
It has been reported that some TIS based TPMs are giving unexpected errors when
using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
Link: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid locking
in NONBLOCKING mode").
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-osp1 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Link: https://patchwork.kernel.org/patch/11576453/
[Impact]
-It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
+ It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
Link: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid
locking in NONBLOCKING mode").
** Description changed:
-
[Impact]
- It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
+ It has been reported that some TIS based TPMs are giving unexpected errors
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs
don't like it when you get and then relinquish a locality (as the
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This
currently happens all the time in the O_NONBLOCK write path. This affects
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix
invalid locking in NONBLOCKING mode").
Link: https://patchwork.kernel.org/patch/11576453/
[Fix]
Fix this by moving the tpm_try_get_ops()
further down the code to after the O_NONBLOCK determination is made.
This is safe because the priv->buffer_mutex still protects the priv
state being modified.
[Regression Risk]
Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid
locking in NONBLOCKING mode").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
Update kernel to 4.15.1081-oem with "apt upgrade" and it got fail to reboot. >From above testings, I think we should bisect kernel to see which kernel patch cause the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
Update grub2 to latest one (2.02-2ubuntu8.15), keep kernel version(4.15.0-1037-oem) and test more that 10 times, it worked fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880663] Re: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up
After restore OS to factory state(kernel 4.15.0-1037-oem, gub2 2.02-2ubuntu8.12), tested with more that 30 times, it worked fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor
The patch has been accepted upstream, and already in the Ubuntu release. ** Changed in: shim (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822043 Title: as enrolling mok, the font is too small in hi-dpi monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1822043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830359] Re: cpuset_base_ops from controller test suite in LTP failed
the failure,
cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0"
are from testing the
$/bin/echo "0-" > "$CPUSET/1/cpuset.cpus" and expecting "0" but got invalid
parameter
on cpuset_base_ops_testset.sh
else
base_op_test "$CPUSET/1/cpuset.cpus" "0-" "0"
fi
and the behavior is changed after the kernel patch "cpuset: Add new v2
cpuset.sched.partition flag"
commit#ee8dde0cd2ce78b62d16aec1c29960b64380e634
+ if (cs->partition_root_state) {
+ /* Cpumask of a partition root cannot be empty */
+ if (cpumask_empty(trialcs->cpus_allowed))
+ return -EINVAL;
+ if (update_parent_subparts_cpumask(cs, partcmd_update,
+ trialcs->cpus_allowed, ) < 0)
+ return -EINVAL;
+ }
which chcek the "0-" and returned -EINVAL;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830359
Title:
cpuset_base_ops from controller test suite in LTP failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830359/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
fix patch sent for review, https://github.com/linux-test-project/ltp/pull/578 ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Ivan Hu (ivan.hu) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
[ 504.084541] ltp_acpi_test: get register: 11 val: [ 504.084944] ltp_acpi_test: get register: 12 val: [ 504.085318] ACPI Exception: AE_BAD_ADDRESS, acpi_read_bit_register the fail is on read ID 0x13, which is on PM2 control bit 0(ARB_DIS). this failure is caused by the PM2 aren't supported by firmeare. >From FADT table. [038h 0056 4] PM1A Event Block Address : B000 [03Ch 0060 4] PM1B Event Block Address : [040h 0064 4] PM1A Control Block Address : B004 [044h 0068 4] PM1B Control Block Address : [048h 0072 4]PM2 Control Block Address : [04Ch 0076 4] PM Timer Block Address : B008 [050h 0080 4] GPE0 Block Address : AFE0 [054h 0084 4] GPE1 Block Address : [058h 0088 1] PM1 Event Block Length : 04 [059h 0089 1] PM1 Control Block Length : 02 [05Ah 0090 1] PM2 Control Block Length : 00 [05Bh 0091 1]PM Timer Block Length : 04 So got AE_BAD_ADDRESS when the test reads from the register is expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825128] Re: grub-efi-amd64-signed should depends on mokutil
shim-signed package has already depended on mokutil. When secureboot enabled, shim is needed and mokutil should be installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825128 Title: grub-efi-amd64-signed should depends on mokutil To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1825128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality
The fix patch has been included in the latest disco kernel. I've tested it with version 5.0.0-23-generic, it worked. ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833297 Title: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor
The patch has been upstreamed, https://github.com/rhboot/shim/pull/182 ** Changed in: shim (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822043 Title: as enrolling mok, the font is too small in hi-dpi monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1822043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor
attached the test mmx64.efi ** Attachment added: "mmx64.tar.gz" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1822043/+attachment/5278810/+files/mmx64.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822043 Title: as enrolling mok, the font is too small in hi-dpi monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1822043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality
** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833297 Title: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833297] Re: Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed TPM2 functionality
** Description changed: Hi, With all updates installed to Ubuntu disco it is impossible to use TPM2 device on the machine. Most of the TPM2 commands seem to fail due to Linux kernel having async access problem that is fixed in linux kernel 5.0.10 release. With previous Ubuntu releases I was able to utilize TPM2 but now this has regressed for disco release. tpm2-tools package's github ticket describes the problem: https://github.com/tpm2-software/tpm2-tools/issues/1356 Official kernel's includes the fix: https://github.com/torvalds/linux/commit/7110629263469b4664d00b38ef80a656eddf3637#diff-694c702fe379e115a3c42d926cedf6de Could you please include the fix from 5.0.10 in forthcoming Ubuntu kernel update to fix the TPM 2.0 regression? How to reproduce You may want to execute those commands as a root or alternative add yourself to tss group. (ubuntu's tpm2tss setup does not work so easily yet). Those commands from tpm2-tools issue can be used to test it out: $ tpm2_nvlist ERROR: GetCapability:Get NV Index list Error. TPM Error:0xa0008 ERROR: Unable to run tpm2_nvlist $ tpm2_pcrlist ERROR: GetCapability: Get PCR allocation status Error. TPM Error:0xa000a.. ERROR: Unable to run tpm2_pcrlist Both of those commands should work nicely and produce list of NV objects (nvlist) or PCR register contents (pcrlist). Latter one is probably easier to see that it works. Note: randomly some commands may progress so try them multiple times if it happens to success. More complex commands seems to have better rate to fail. This randomness is due to async nature of the problem that was fixed. What you are required to have in hardware: - TPM 2.0 chip so that: $ ls -1 /dev/tpm* /dev/tpm0 /dev/tpmrm0 Easiest is to have either laptop with integrated tpm 2.0 which is not in active use or then desktop with tpm 2.0 addon card (or integrated solution) where it is not in active use. Commands listed above can also be safely executed on TPM 2.0 enabled system without causing problems. With other commands I would be more cautious especially with TPM 2.0 enabled system if you are not familiar with TPM2 commands. What packages you need to install (may require some more): - tpm2-tools - libtss2-udev - libtss2-tcti-tabrmd0 Thanks, Vesa Jääskeläinen ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-17-generic 5.0.0-17.18 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: chaac 2503 F pulseaudio - /dev/snd/controlC0: chaac 2503 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: chaac 2503 F pulseaudio + /dev/snd/controlC0: chaac 2503 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jun 18 22:52:14 2019 HibernationDevice: RESUME=UUID=1c9f002c-f771-48de-8e73-c73ee21a6410 InstallationDate: Installed on 2018-09-02 (289 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-17-generic root=UUID=383abbcb-8fac-4f16-a3bd-2747d4f334cf ro quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-5.0.0-17-generic N/A - linux-backports-modules-5.0.0-17-generic N/A - linux-firmware1.178.1 + linux-restricted-modules-5.0.0-17-generic N/A + linux-backports-modules-5.0.0-17-generic N/A + linux-firmware1.178.1 RfKill: - + SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-19 (60 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0606 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z370-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0606:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ370-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer + + [Impact] + Most of the TPM2 commands fail to execute due to tpm2 kernel driver having async access problem. + + [Fix] + Fix an invalid poll condition. + + [Test Case] + After applied the fix patch on 19.04, the TPM2 commands
[Bug 1825128] Re: grub-efi-amd64-signed should depends on mokutil
What does grub-check-signatures use mokutil for? It makes more sense mokutil depends on shim not grub. Can mokutil depend on shim package solve your issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825128 Title: grub-efi-amd64-signed should depends on mokutil To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1825128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
Here are testing procedures,
1. Install Ubuntu 18.04 and connect to internet
2. Perform Firmware Update, base on 10-3 (expeted fail due to capsule header
issue)
$sudo fwupdate -a {guid} 1AUOK.bin
$sudo efibootmgr (check boot entry, next boot is create or not)
$sudo reboot
It failed to do firmware update.
3. Setting software for proposed version
Software & updates -> select Download from "Main server"
Software & updates -> check "Source code"
Software & updates -> Developer option -> Pre-released updates
4. update fwupdate to version 12-3
$sudo apt update
$sudo apt install fwupdate (make sure fwupdate update to 12)
5. Get firmware update GUID
$sudo fwupdate -l --find the guid for firmware update
6. Perform Firmware Update
$sudo fwupdate -a {guid} 1AUOK.bin
$sudo efibootmgr (check boot entry, next boot is create or not)
$sudo reboot
Confirmed firmware is successful updated by fwupdate 12-3 packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785165
Title:
firmware update on fwupdate version 10-3 not work on some AMI's
firmwares
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1785165/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
Got confirmed from AMI Taipei team. This version fixes the Capsule issue on AMI's firmware. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
It seems the proposed release packages still be pending, amd64 - Pending publication arm64 - Pending publication armhf - Pending publication i386 - Pending publication https://launchpad.net/ubuntu/+source/fwupdate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
Test with Intel software development platform on Trusty with the grub2 trusty-proposed, after updating the grub-efi-amd64(signed), got the correct 64-bit efi linear frame buffer address [1.295327] efifb: probing for efifb [1.295344] efifb: framebuffer at 0x40, mapped to 0xc9000100, using 14400k, total 14400k [1.295346] efifb: mode is 2560x1440x32, linelength=10240, pages=1 [1.295347] efifb: scrolling: redraw [1.295349] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
Test with Dell's machine on Xenial with the grub2 xenail-proposed, and update grub-efi-amd64 and grub-efi-amd64-signed packages got the correct 64-bit efi linear frame buffer address [0.923498] efifb: probing for efifb [0.923506] efifb: framebuffer at 0x40, using 8100k, total 8100k [0.923507] efifb: mode is 1920x1080x32, linelength=7680, pages=1 [0.923507] efifb: scrolling: redraw [0.923508] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
add debdiff, ** Attachment added: "fwupdat_b-debdiff" https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+attachment/5210283/+files/fwupdat_b-debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
Test with Dell's machine on Bionic with the grub2 bionic-proposed, got the correct 64-bit efi linear frame buffer address. [0.965079] efifb: probing for efifb [0.965086] efifb: framebuffer at 0x40, using 8100k, total 8100k [0.965087] efifb: mode is 1920x1080x32, linelength=7680, pages=1 [0.965088] efifb: scrolling: redraw [0.965089] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
Attached the debdiff on xenial ** Attachment added: "grub2_x-debdiff" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+attachment/5184820/+files/grub2_x-debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Description changed: [Rationale] - More firmwares support above 4G mmio configuration and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. + More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] - Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address, since Grub pass the incorrect (only 32-bit) EFI linear frame buffer. + Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. [Solution] A patch has been committed and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f + + [Regression Potential] + Minimal, it's unlikely completing the whole framebuffer address will affect those which hasn't used above 32-bits framebuffer address. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmwares
@Mario, Actually I have built a test package 10-3.3 on my test PPA, https://launchpad.net/~ivan.hu/+archive/ubuntu/test.ppa, base on 10-3 and with the only fixed patch, and got confirmed that can fix the fwupdate issue from OEM. What other patches do you think we also need to SRU? I also tested with Dell XPS machine which has no such issue originally, and it could do the firmware update successfully, not affected by this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on some AMI's firmware
** Summary changed: - firmware update on fwupdate version 10-3 not work on AMI's firmware + firmware update on fwupdate version 10-3 not work on some AMI's firmware ** Summary changed: - firmware update on fwupdate version 10-3 not work on some AMI's firmware + firmware update on fwupdate version 10-3 not work on some AMI's firmwares -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on some AMI's firmwares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
** Description changed: [Rationale] - The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. + The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" causes those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, #sudo fwudpate -s 4. get the update GUID #sudo fwupdate -l 5. do firmeare update #sudo -a GUID firmware.bin 6. reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] [NEW] firmware update on fwupdate version 10-3 not work on AMI's firmware
Public bug reported: [Rationale] The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, #sudo fwudpate -s 4. get the update GUID #sudo fwupdate -l 5. do firmeare update #sudo -a GUID firmware.bin 6. reboot ** Affects: fwupdate (Ubuntu) Importance: Undecided Status: New ** Description changed: [Rationale] - The commited patch, Handle ux capsule updates, https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. + The commited patch, Handle ux capsule updates, https://github.com/rhboot/fwupdate/commit/2561423dd68622dcf8a7542709f332edb517d34e, change to calculate CapsuleBlockDesc Length = CapsuleHeader.CapsuleImageSize + HeaderSize, but on AMI BIOS image which is without capsule header. Fwudpate package on 18.04(version 10-3) included the "Handle ux capsule updates" and cause those machine with AMI firmware cannot do firmware update. The fixed patch have been committed, https://github.com/rhboot/fwupdate/commit/863db45c246acd2cbeff0b4e32d3a8312475ff6a and fix the incorrect cbd_length. [Impact] Machines with AMI's firmware cannot do firmware update. [Test cases] 1. install ubuntu 18.04 on AMI's bios machine. 2. get the update firmware 3. See if this machine support firmware update, -#sudo fwudpate -s + #sudo fwudpate -s 4. get the update GUID -#sudo fwupdate -l + #sudo fwupdate -l 5. do firmeare update -#sudo -a GUID firmware.bin + #sudo -a GUID firmware.bin 6. reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785165] Re: firmware update on fwupdate version 10-3 not work on AMI's firmware
Attached the fixed patch ** Patch added: "0001-Let-s-see-if-this-works-with-that-number-smaller.patch" https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+attachment/5170974/+files/0001-Let-s-see-if-this-works-with-that-number-smaller.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785165 Title: firmware update on fwupdate version 10-3 not work on AMI's firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Description changed: [Rationale] More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] - Need Bios/Firmware support, + Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. - [Solution] - A patch has been commited and accepted by maintainer + A patch has been committed and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB need to support 64-bit efi linear frame buffer address
The patch on comment#1 have been tested can fix the block booting issue on some Dell machines. ** Summary changed: - GRUB need to support 64-bit efi linear frame buffer address + GRUB needs to support 64-bit efi linear frame buffer address -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] Re: GRUB need to support 64-bit efi linear frame buffer address
Attach the fix patch which has been accepted and committed. ** Patch added: "0001-i386-linux-Add-support-for-ext_lfb_base.patch" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+attachment/5170756/+files/0001-i386-linux-Add-support-for-ext_lfb_base.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785033] [NEW] GRUB needs to support 64-bit efi linear frame buffer address
Public bug reported: [Rationale] More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. [Solution] A patch has been commited and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698277] Re: fwts's supports to UEFI 2.7
prepare to add some tests for EFI_VARIABLE_AUTHENTICATION_3 in UEFI 2.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698277 Title: fwts's supports to UEFI 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1698277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698277] Re: fwts's supports to UEFI 2.7
** Changed in: fwts (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698277 Title: fwts's supports to UEFI 2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1698277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746114] Re: Move xenial to fwupd 0.8.x branch
testing with Dell XPS 13 9360 Got UEFI firmware update failed: Unknown error -1 Also check the PPA on comment#1 the same result UEFI firmware update failed: Unknown error -1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746114 Title: Move xenial to fwupd 0.8.x branch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1746114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
The patch which fixed this issue has included in the upstream git repository, http://git.savannah.gnu.org/cgit/grub.git/commit/?id=446794de8da4329ea532cbee4ca877bcafd0e534 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] [NEW] Grub2 cannot boot up when 8254 time function disable
Public bug reported: Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer function is disabled. "8254 clock gating" is provided to disable 8254 timer to get rid of legacy and save power. The platforms with the firmware which disable the 8254 timer will fail to boot up and block on grub2 which uses the 8254 timer to calibrate the TSC. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update
I've tested it with xenail, it worked. And also asked Lenovo to help to test with their platforms with multiple capsules support. Confirmed work fine. ** Tags removed: verification-needed ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684034 Title: Some Dell and Lenovo systems do not work after BIOS Capsule Update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update
Have modified 4 required patches base on the fwupdate 0.5 for Xenial, - 0001-fwupdate-fix-memory-leaks-and-storing-update_table-t.patch: fwupdate: fix memory leaks and storing update_table to NULL pointer. commit 765bb7221af37ac56b11ef2253bf1bb3230ef589 - 0001-fwupdate.efi-use-the-reset-type-from-some-querycapsu.patch: fwupdate. efi: use the reset type from some querycapsuleinfo call. commit f1cc489783d2054e90fa6bebc3732e7ea8bb3722 - 0001-Add-a-flag-to-Allow-flashing-GUID-s-that-don-t-match.patch: Add a flag to Allow flashing GUID's that don't match the ESRT table. commit 64b4cd53baa57352fa9b2459e804c4ea50d40299 - 0001-Make-sure-our-BootNext-entry-is-always-in-BootOrder.patch: Make sure our BootNext entry is always in BootOrder. commit ba48ac4ed7329ae5beb44063dcbd3c424e11fc46 Package available in https://launchpad.net/~ivan.hu/+archive/ubuntu/sru/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684034 Title: Some Dell and Lenovo systems do not work after BIOS Capsule Update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1684034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603026] Re: fwts mtrr should test IA32_MTTR_DEF_TYPE before running the test
Fix patches have been included to V17.06.00. ** Changed in: fwts (Ubuntu) Assignee: (unassigned) => Ivan Hu (ivan.hu) ** Changed in: fwts (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603026 Title: fwts mtrr should test IA32_MTTR_DEF_TYPE before running the test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1603026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581299] Re: shim: set second stage not work
Verify the shim-signed 1.27 with yakkety-proposed and xenial-proposed, it works fine on the second stage of shim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581299 Title: shim: set second stage not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1581299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673744] Re: Fwupdmgr does not work on Ubuntu 16.04.2
@Richard, Do you mean that *.cab only needs to include firmware.bin and firmware.metainfo.xml? For old and new version can both support by removing firmware.inf from *.cab? ** Changed in: fwupd (Ubuntu Xenial) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673744 Title: Fwupdmgr does not work on Ubuntu 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1673744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644806] Re: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
the patch has been accepted by upstream, commit# 07bda58596608f05bfa035a1cc5710f5ac8ea3d9 on https://github.com/rhinstaller/shim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1644806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642118] Re: Several TPM2.0 tests fail
get the machine from gerald, Ford-DVT2-C1, after build and re-install tpm2-tools v1.1.0 and TPM2-TSS 1.0.0 most tests pass test_tpm2_takeownership_all.sh pass test_tpm2_nv.sh pass test_tpm2_listpcrs.sh pass test_tpm2_getrandom.sh pass test_tpm2_load.sh pass test_tpm2_loadexternal.sh pass test_tpm2_evictcontrol.sh pass test_tpm2_hash.sh pass test_tpm2_hmac.sh pass test_tpm2_akparse.sh pass test_tpm2_certify.sh pass test_tpm2_evictcontrol.sh pass test_tpm2_getpubek.sh pass test_tpm2_getpubak.sh pass test_tpm2_makecredential.sh pass test_tpm2_activecredential.sh pass test_tpm2_readpublic.sh pass test_tpm2_rsaencrypt.sh pass test_tpm2_rsadecrypt.sh pass test_tpm2_sign.sh pass test_tpm2_verifysignature.sh pass only test_tpm2_quote.sh fail test_tpm2_unseal.sh fail test_tpm2_encryptdecrypt.sh fail So the comment from #4 should be false alarm. ** Attachment added: "test_all.tar.gz" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1642118/+attachment/4802290/+files/test_all.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642118 Title: Several TPM2.0 tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1642118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642118] Re: Several TPM2.0 tests fail
@gerald, Which machine you are using? Could you attach more detail fail log? Looks like you don't run resourcemgr accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642118 Title: Several TPM2.0 tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1642118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642118] Re: Several TPM2.0 tests fail
Those failures are mostly due to the tests use "tpm2_takeownership -c" to clear the Hierarchy auth fail Start to clear the Hierarchy auth ClearControl Failed ! ErrorCode: 0x9a2 Error Code 0x9a2 means "TPM ERROR: SESSION #1, TPM_RC_BAD_AUTH: authroization failure without DA implications". So if you met any 0x9a2 error, usually it is due to that the platform auth is not NULL or owner auth is not NULL. They have modifications for the test to avoid this issue on the following patches on https://github.com/01org/tpm2.0-tools commit 4d5c543ae056538f0ab1a1eaa6ed0cf3362f4b58 commit f18d77cdd6029af086ce0ac1a63a8afd86d7aceb commit adba1405e1358c9ee987121ae5e7aff4fa44afd3 and some failures are for the mismatch for the tool wrapped application between test scripts. the tpm2 packages we have was packed on 2016.02.26 but the test script for tpm2-tools developed from 2016.4.28. It means we used newer test scripts to test old wrapped applications. so you can find some error messages such as, tpm2_listpcrs: invalid option -- 'L' tpm2_quote: invalid option -- 'q' ** Attachment added: "test_all.log" https://bugs.launchpad.net/ubuntu/+source/tpm2-tools/+bug/1642118/+attachment/4788467/+files/test_all.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642118 Title: Several TPM2.0 tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1642118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644806] Re: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
@Steve The machines have been in production and sold more than one year. Unfortunately the error message is print out by console error, console_error(L"Failed to set MokSBStateRT", efi_status); It will block the boot with ugly full blue screen and wait for user's "enter" to continue to boot. I believe it is better that the new SRU should wait for the new patch included, because there might be a lot of Dell machine users affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644806] Re: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter"
This issue is caused by the Dell machines have already embedded the MokSBStatesRT variable with EFI_VARIABLE_NON_VOLATILE attribute, and the new shim-signed 1.21.4 include the patch which will mirror the MokSBStatesRT when MokSBState exists, see the https://github.com/rhinstaller/shim/commit/8f1bd605d05077a76502de5510cc937c4f4c62dd, and it causes the setvariable MokSBStatesRT failed because it has already existed with different attribute. Attached the patch which can be used to solve this issue by checking the MokSBStateRT existence and deleting it before mirroring it. This patch had been sent to upstream and wait for feedback. ** Patch added: "0001-shim-fix-the-mirroring-MokSBState-fail.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+attachment/4784570/+files/0001-shim-fix-the-mirroring-MokSBState-fail.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635502] Re: segment fault when running fwts method test
** Changed in: fwts Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635502 Title: segment fault when running fwts method test To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1635502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581299] Re: shim: set second stage not work
Verify the shim-signed 1.21.4 with xenial-proposed and trusty-proposed, they could fix the second stage issue of shim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581299 Title: shim: set second stage not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1581299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581299] Re: shim: set second stage not work
Verify the shim-signed 1.21.4 with yakkety-proposed, it could fix the second stage issue of shim. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581299 Title: shim: set second stage not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1581299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635502] Re: segment fault when running fwts method test
verify with fwts V16.09.00 with Yakkety-proposed, Xenial-proposed, Trusty-proposed, All pass with fwts method tests. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635502 Title: segment fault when running fwts method test To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1635502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
