** 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
@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
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
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
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
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
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
** 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
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,
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
** 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
** 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
@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,
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
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/),
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
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),
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
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),
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
@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
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
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
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
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:
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:
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
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
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
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.
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.
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
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.
** 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
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.
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
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.
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
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]
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
** 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
** 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:
** 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.
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)
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.
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
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
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
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
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.
** 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.ne
[ 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
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:
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
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:
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.
** 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
** 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
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.
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
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,
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,
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
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
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.
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,
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.
** 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
@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
** 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
** 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
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
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
** 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
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
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
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
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
** 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
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.
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.
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
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
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
-
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 subs
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
@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
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:
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
@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
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".
@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.
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
** 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
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
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.
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
@Colin,
I've tried acpidump log last week but cannot reproduce the issue.
Unfortunately, I cannot get the machine which can reproduce the issue, since
the QA has been testing with it last week and not allow me to touch it. I need
to wait for a week after QA finish testing.
--
You received
@ Colin,
I recalled it seems we got the irrelevant headers installed, so we specified
the header dependency.
Removed all header dependencies seems a good solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: shim-signed (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/1609209
Title:
Disable signature validation on shim without user interactions under
1 - 100 of 250 matches
Mail list logo
