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.
h
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 Ub
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.
h
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.
h
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 yo
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: [Firmwar
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
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:/
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=768
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.launch
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 8100
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, whi
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 firmwar
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
0xc900
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
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
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
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-am
[ 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 suppor
** 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
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/bu
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/c
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.launch
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 a
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
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:/
** 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
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
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 La
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 Lat
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
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) w
** 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.laun
** 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-o
** 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
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 subscribe
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] micr
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-
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, whi
** 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
** 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 functiona
** 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
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
** 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 ker
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
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 ha
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
** 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 ke
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
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 c
** 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 wi
** 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 versio
@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
** 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 abo
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/8f1bd6
@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
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 subscri
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-
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:/
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 blo
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.la
from comment#5 set it Fix Released
** Changed in: acpi (Ubuntu)
Status: Confirmed => 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/1191691
Title:
[Dell Latitude E6330] Many ACPI
** Changed in: linux-lts-raring (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/1253871
Title:
[Dell Inspiron 5437] HIGH failure: FADTPM1AInvalidWidth, repor
for the _Q33 -> no CMOS handler.
The issue is the same as the bug#1143312,
Upstream has a patch to fix this issue. This shall be included in kernel 3.11,
The patch will be backported to 3.9+ kernel and will be included in ubuntu
13.10,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/l
For the no handler issue,
The issue is the same as the bug#1143312,
Upstream has a patch to fix this issue. This shall be included in kernel 3.11,
The patch will be backported to 3.9+ kernel and will be included in ubuntu
13.10,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug
The _WAK error,
s4: HIGH Kernel message: [322397.358723] ACPI Error: Field [PMS1] access width
(1 bytes) too large for region [SWCR] (length 0) (20121018/exfldio-195)
s4: HIGH Kernel message: [322397.358724] ACPI Error: Field [PMS1]
Base+Offset+Width 2+0+1 is beyond end of region [SWCR] (length
s4: HIGH Kernel message: [322397.481202] ACPI Error: Field [DRQL] at 144
exceeds Buffer [NULL] size 128 (bits) (20121018/dsopcode-236)
s4: HIGH Kernel message: [322397.481205] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.SIO1.DSRS] (Node 880427c4e7a8), AE_AML_BUFFER_LIMIT
(201
*** This bug is a duplicate of bug 1232975 ***
https://bugs.launchpad.net/bugs/1232975
the same bug as #1232975
** This bug has been marked a duplicate of bug 1232975
[Dell Optiplex 9020] High kernel failures in suspend / hibernate log.
--
You received this bug notification because you a
more information for comment#5
The _PLD failures come from the buggy firmware, from acpi spec,
This _PLD optional object is a method that conveys to OSPM a general
description of the physical location
of a device’s external connection point.
I don't think _PLD failures will cause affect any devic
Carefully comparing them found BYTE 7 is changed from 0x08, 0x40 to
0x00, it is Status Register(These read-only bits reflect the temporary
status of the device/function when fwst read the register). These bits
are "Signaled Target Abort", "Signaled System Error". This can indicate
that before sleep
The S1, S2 should work in fwts V14.02.00
** Changed in: linux-lts-saucy (Ubuntu)
Status: Confirmed => 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/1280103
Title:
[Dell Optiplex 3
Compare with the PCI configure registers that change between sleep/wake
are the offset 0x2c~0x2f, which are the subsystem vendor ID and
subsystem ID, these IDs can mainly be used for further identification of
a device. If the chip in itself is a generic interface chip to a local
(onboard) bus, it i
** Changed in: linux-lts-saucy (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/1312559
Title:
[Lenovo T540p] DevConfigDiffAfterS3 and DevConfigDiffAfterS4
To
@ 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.
https://bugs.launchpad
@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
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:
Propose
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
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.launc
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 s
@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 T
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_tpm
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 Ub
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
Here is the efibootmgr -v for your request.
BootNext: 0007
BootCurrent: 0006
Timeout: 0 seconds
BootOrder: 0006,0001,,0002,0003,0004
Boot* UEFI Internal Shell
FvVol(cdbb7b35-6833-4ed6-9ab2-57d2acddf6f0)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0001* Enter Setup
FvVol(cdbb7b35
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
** 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/1
Patch has sent for review,
https://lists.ubuntu.com/archives/fwts-devel/2016-July/008282.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606480
Title:
Incomplete dependencies for Linux headers
Sent out a patch fixing the set second stage function for loadoption.
And have been accepted on https://github.com/rhinstaller/shim
** Patch added: "0001-shim-dealing-with-only-one-string-on-loadoption.patch"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1581299/+attachment/4661695/+f
Public bug reported:
Using the applications such as fwupdate and efibootmgr to set the device path
for the second stage path is not working on some platforms.
The second stage set is not working after commit
3322257e611e2000f79726d295bb4845bbe449e7 on https://github.com/rhinstaller/shim
for those
Set.efi need to be signed with Canonical key.
** Affects: shim-signed (Ubuntu)
Importance: Undecided
Assignee: Ivan Hu (ivan.hu)
Status: Confirmed
** Attachment added: "shim_dis_valid.tar.gz"
https://bugs.launchpad.net/bugs/1609209/+attachment/4712747/+files/shim_dis_
** 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
@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 this
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".
the error,
s3: HIGH Kernel message: [ 457.594493] ACPI Error: Field [DRQL] at 144
exceeds Buffer [NULL] size 128 (bits) (20131115/dsopcode-236)
s3: HIGH Kernel message: [ 457.594498] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.SIO1.DSRS] (Node 880079715c58), AE_AML_BUFFER_L
into it.
** Changed in: linux (Ubuntu)
Assignee: Ivan Hu (ivan.hu) => Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335026
Title:
[Dell OptiPlex 3011] Someti
** Changed in: linux-lts-trusty (Ubuntu)
Status: Incomplete => 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/1273924
Title:
[Dell Precision T1700] CRITICAL / HIGH failures found in
the failures are form buggy firmware, set the method _PSR as NotSerialized, but
create the objects.
As from the ACPI spec mention,
Functions are equivalent to a Method that specifies NotSerialized. As such, a
function should not
create any named objects, since a second thread that might re-enter
The failure,
klog: HIGH Kernel message: [ 0.00] ACPI Error: Gpe0Block - 32-bit FADT
register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits
max, truncating (20130517/tbfadt-202)
is due to the setting length of GPE0 Block is 32 bytes, over the kernel
expectation(255 bit
For the S1,S2 failures,
The failures come from firmware not provide _S1 and _S2 objects, so that the
kernel complains about cannot find _S1,_S2 namespace objects that contains the
register values for the sleep state when kernel would like to setup all the
sleep state information. This means kern
this should due to the headers were not installed.
please refer to bug#1414946
https://bugs.launchpad.net/ubuntu/+source/fwts/+bug/1414946
** Changed in: fwts (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
the failures,
klog: CRITICAL Kernel message: [ 65.525879] CPU0: Core temperature above
threshold, cpu clock throttled (total events = 1)
klog: CRITICAL Kernel message: [ 65.525891] CPU1: Core temperature above
threshold, cpu clock throttled (total events = 1)
klog: CRITICAL Kernel message:
1 - 100 of 256 matches
Mail list logo
