@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 Kernel
Packages, 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2061940
Title:
Some DUTs can't boot up after installing the
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 Kernel
Packages, which is
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049733
Title:
Dynamically determine
>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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2060981
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049733
Title:
Dynamically determine acpi_handle_list size
Status
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) =>
Public bug reported:
[Impact]
ACPI handle list will be dynamic allocated without default fixed size.
[Fix]
Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for
some platforms that called ACPI _PSL method to get passive cooling device
objects. then will get the error
Test B PC device withlinux/5.15.0-93.103 kernel on several displays, display
fine.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Description changed:
[Impact]
- Some displays connect to the B PC device got the garbled display
+ Some displays connect to the B PC device got the garbled display
[Fix]
- Add quirk to force disable the i915 fastboot on the device to fix the
abnormal display
+ The issue will disappear
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => H
** Tags added: mering oem-priority originate-from-2039623
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2047630
Title:
Add quirk to disable i915 fastboot on B PC
Status in HWE Next:
Public bug reported:
[Impact]
Some displays connect to the B PC device got the garbled display
[Fix]
Add quirk to force disable the i915 fastboot on the device to fix the abnormal
display
[Test Case]
1. Connect the display and power on the B PC device
2. Check the display for boot up
[Where
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1025663
Title:
DMIStringIndexOutOfRange on HP Proliant ML110 G5
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995453
Title:
Add some ACPI device IDs for
Verify passed by checking the linux/5.15.0-68.75 kernel in -proposed
dmesg,
The "[\_SB.PR00._CPC], AE_NOT_FOUND" is gone and the dinamic ssdt
table(such as ApHwp etc.) are loaded.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Ivan Hu (ivan.hu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2006077
Title:
Fix the ACPI _CPC not found error from kernel dmesg on
** Summary changed:
- Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT
tables firmware
+ Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT
table loaded firmwares
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
Public bug reported:
[Impact]
Some machines which have dynamically loaded SSDT tables, will not be loaded and
get the CPPC not worked.
[Fix]
Fix the regression by some load supports for CPPC from an SSDT dynamically when
_OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone.
Verify pass.
Kernel:5.19.0-30.31 kernel (kinetic-proposed)
SKU: Alxd-Low-DVT-C1 (202209-30619)
BIOS: 0.12.70
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verify pass.
Kernel:linux-oem-6.0 (6.0.0-1008.8)
SKU: Alxd-Low-DVT-C1 (202209-30619)
BIOS: 0.12.70
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Assignee: Ivan Hu (ivan.hu)
Status: Triaged
** Also affects: linux-oem-5.17 (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Also affe
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in
This is due to 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,
https://lore.kernel.org/lkml/9b93e099fc6ee2a56d70ed338cd79f2c1ddcffa5.ca...@linux.ibm.com/T/
Unfortunately, the checking
** 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
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:
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 Kernel
Packages, 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:
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)
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
[ 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
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 Kernel
Packages, which is
** Changed in: linux (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1833297
Title:
Ubuntu 19.04's Linux kernel 5.0.0-17 has regressed
** 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
@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
Those failures are from firmware, and no real functions impacted.
Set as won't fix.
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
These failures are from firmware, set it as won't fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1263863
Title:
The failures,
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT0.CHN0.DRV0._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT0.CHN0.DRV1._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
the failure,
klog: HIGH Kernel message: [0.352459] \_SB_:_OSC invalid UUID
From the Acpi table,
Method (WOSC, 4, NotSerialized)
{
CreateDWordField (Arg3, Zero, CDW1)
If (LEqual (Arg0, Buffer (0x10)
{
/* */ 0x0C, 0x5E, 0x85,
Got Asus machine to verify 3.13 kernel, official 14.04.1 Ubuntu image got panic
when install.
Verify the 14.04.2 kernel 3.16, -proposed solves the problem.
** Changed in: hwe-next
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Kernel
Verify with the kernel 3.13.0-53, -proposed solved the problem.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
** Changed in: hwe-next
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
klog: HIGH Kernel message: [7.944886] ACPI Warning:
\_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - Found [Buffer],
ACPI requires [Package] (20140424/nsarguments-95)
for _DSM failure, kernel compliant about the mismatch of _DSM method(Device
Specific Method)
From ACPI spec,
This
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
install with the install the system via a live usb with 12.04.05 on
UEFI.
it will install completely and check the Boot path
\efi\ubuntu\shimx64.efi, it is created by installation(efibootmgr)
correctly before reboot.
After reboot, Boot entry disappear.
Bios that does not recognize boot entry
install in legacy, no problem.
** Changed in: hwe-next
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1444834
Title:
[Dell Latitude
For the failure,
klog: HIGH Kernel message: [7.859557] ACPI Warning: SystemIO range
0x0b00-0x0b07 conflicts with OpRegion
0x0b00-0x0b0f (\_SB_.PCI0.SMB_.SMB0)
(20141107/utaddress-258)
is from the buggy bios, that acpi implemented the
for 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 (20131115/tbfadt-202)
is due to the setting length of GPE0 Block is 32 bytes, over the kernel
For the failures,
klog: HIGH Kernel message: [0.257172] \_SB_.PCI0:_OSC invalid UUID
klog: HIGH Kernel message: [7.099033] ACPI Exception: AE_NOT_FOUND,
Evaluating _DOD (20131115/video-1278)
klog: HIGH Kernel message: [ 10.653041] ACPI Warning:
\_SB_.PCI0.RP05.PEGP._DSM: Argument #4
It seems that firmware ACPI table issue.
Please attache acpidump file for further investigation. Thanks!
** Changed in: hwe-next
Status: New = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For the confquation different,
s3: Found 1 differences in device configuation during S3 cycle.
compare to the differences, all from offset 5 byte, the pci register status,
The status represent the hardware temporary status. It should no hard for the
differences between sleep/wake.
--
You
For the failures,
s3: HIGH Kernel message: [ 660.997508] ACPI Error: Field [DRQL] at 144
exceeds Buffer [NULL] size 128 (bits) (20131115/dsopcode-236)
s3: HIGH Kernel message: [ 660.997513] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.SIO1.DSRS] (Node 880078312fc8),
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 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),
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1335026
Title:
[Dell OptiPlex 3011
this is caused by varible
Name: .
Checking with the uefidump, it is the record log variable, that logs the system
oops that has ever occurred.
It should not affect system function.
** Attachment added: results.log
The same root cause with bug#1243493,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1243493/comments/2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1148649
Title:
HP Pavilion G7 - FWTS HIGH errors during
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,
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,
The severity for LVT issue was down to the medium after fwts version
V0.26.07. set the bug to invalid.
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = Invalid
** Changed in: fwts
Status: New = Fix Committed
** Changed in: linux (Ubuntu Precise)
Assignee: Ivan Hu
** Changed in: fwts
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1021496
Title:
[Dell Inspiron One 2305]: Fails to suspend without errors.
The severity for LVT issue was down to the medium after fwts version
V0.26.07. Set the bug to invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
)
Status: Fix Committed = Won't Fix
** Changed in: linux (Ubuntu Quantal)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
** Changed in: linux (Ubuntu Raring)
Assignee: Ivan Hu (ivan.hu) = (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which
For Q33 issue, it is still waiting for the patch to be accepted.
please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
80 matches
Mail list logo
