[Kernel-packages] [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 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 TPM2 functionality Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Released Bug description: 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 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 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 t
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in grub2 source package in Bionic: Incomplete Bug description: With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub. There is no any log in journal when it fails to boot up, and earlyprintk shows nothing on the screen, either. System Information Manufacturer: Dell Inc. Product Name: Latitude 7300 Version: Not Specified Serial Number: J83ZST2 UUID: 4C4C4544-0038-3310-805A-CAC04F535432 Wake-up Type: Power Switch SKU Number: 08E0 Family: Latitude BIOS Information Vendor: Dell Inc. Version: 1.6.1 Release Date: 11/14/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 24 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1880663 Title: Dell Latitude 7300 sometimes stuck at purple screen after grub and fails to boot up Status in OEM Priority Project: New Status in intel-microcode package in Ubuntu: New Status in intel-microcode source package in Bionic: New Status in intel-microcode source package in Focal: New Bug description: With linux-4.15.0-1081 kernel, it usually stuck at purple screen after grub. There is no any log in journal when it fails to boot up, and earlyprintk shows nothing on the screen, either. System Information Manufacturer: Dell Inc. Product Name: Latitude 7300 Version: Not Specified Serial Number: J83ZST2 UUID: 4C4C4544-0038-3310-805A-CAC04F535432 Wake-up Type: Power Switch SKU Number: 08E0 Family: Latitude BIOS Information Vendor: Dell Inc. Version: 1.6.1 Release Date: 11/14/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 24 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1880663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-osp1 package in Ubuntu:
New
Bug description:
[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").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-osp1 package in Ubuntu:
New
Bug description:
[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.o
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[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").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881710
Title:
tpm: fix TIS locality timeout problems
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux-oem-osp1 package in Ubuntu:
Invalid
Status in linux-oem-osp1 source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[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").
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").
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881710/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 tpm2_nvli
[Kernel-packages] [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 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 TPM2 functionality Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: 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 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 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] A
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:15:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:15:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:15:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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, &tmp) < 0)
+ return -EINVAL;
+ }
which chcek the "0-" and returned -EINVAL;
--
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/1830359
Title:
cpuset_base_ops from controller test suite in LTP failed
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
New
Status in linux source package in Disco:
New
Bug description:
Issue found on Disco with node glameow:
startup='Fri May 24 10:23:44 2019'
cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string
cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string
cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected
string
cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string
cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0"
cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string
cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0"
cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string
cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string
cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string
cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string
cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string
cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string
cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string
cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string
cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string
cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string
cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string
cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string
cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string
cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string
cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string
cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string
cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string
cpuset_base_ops 101 TPASS: cpuset.memory_migra
[Kernel-packages] [Bug 1345897] Re: [Dell Inspiron 3541] High failures found in fwts klog test
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
function will cause a fatal
error if an attempt is made to create the same named object twice.
Method (_PSR, 0, NotSerialized) // _PSR: Power Source
{
...
CreateWordField (XX00, Zero, SSZE)
CreateByteField (XX00, 0x02, ACST)
Store (0x03, SSZE)
Sleep (0x64)
If (Local0)
...
The _PSR method returns whether this power source device is currently online.
This causes temporarily cannot get the Power Source status online or not.
** 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/1345897
Title:
[Dell Inspiron 3541] High failures found in fwts klog test
Status in “linux” package in Ubuntu:
Won't Fix
Bug description:
CID: 201403-14859 Dell Inspiron 3541
The following HIGH kernel messages were found in fwts klog test:
High failures: 2
klog: HIGH Kernel message: [2.141589] ACPI Error: [SSZE] Namespace
lookup failure, AE_ALREADY_EXISTS (20131115/dsfield-211)
klog: HIGH Kernel message: [2.141609] ACPI Error: Method parse/execution
failed [\_SB_.AC__._PSR] (Node 88006835d410), AE_ALREADY_EXISTS
(20131115/psparse-536)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified:
boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1717 F pulseaudio
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Sun Jul 20 22:44:13 2014
HibernationDevice: RESUME=UUID=43272c2a-1a8c-404b-8b62-9c6b53e1a765
InstallationDate: Installed on 2014-07-16 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 3541
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
root=UUID=4f3d06a7-1106-40c0-a15b-0657fd66a382 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-24-generic N/A
linux-backports-modules-3.13.0-24-generic N/A
linux-firmware 1.127
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/20/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: Inspiron 3541
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd03/20/2014:svnDellInc.:pnInspiron3541:pvrNotSpecified:rvnDellInc.:rnInspiron3541:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3541
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1345897/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1331281] Re: [HP 110 Desktop] HIGH failure found in fwts uefirtvariable test
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331281/+attachment/4143659/+files/results.log ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1331281 Title: [HP 110 Desktop] HIGH failure found in fwts uefirtvariable test Status in “linux” package in Ubuntu: Won't Fix Bug description: CID:201301-12636 HP 110 Desktop The following high failure could be found in the fwts uefirtvariable test report FAILED [HIGH] UEFIRuntimeGetNextVariableName: Test 2, Duplicate variable name found. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1457 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 17 22:05:19 2014 HibernationDevice: RESUME=UUID=59db6909-073e-4037-a30a-1a573bdff093 InstallationDate: Installed on 2014-06-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard TEST ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=2baadb9d-3d7f-4cc2-8448-6bf2a8d52379 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17G dmi.board.name: 2B01 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.02 dmi.chassis.asset.tag: RDW3010022 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17G:bd03/18/2013:svnHewlett-Packard:pnTEST:pvr:rvnHewlett-Packard:rn2B01:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.name: TEST dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335026] Re: [Dell OptiPlex 3011] Sometimes system won't be able to run suspend stress test
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_LIMIT
(20131115/psparse-536)
s3: HIGH Kernel message: [ 457.594502] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.LPCB.UAR1._SRS] (Node 880079715ed8), AE_AML_BUFFER_LIMIT
(20131115/psparse-536)
is from buggy firmware, it occured on other Dell's machines. Don't have
acpidump on this machine, so past on the analysis on that machine.
When s3 resume, will set the resource, first call the _CSR of the UAR1 device
to check the current resource, then set the resoure via _SRS,
the UART1 _CRS call SIO1.DCRS, then return CRS1 -> buffer size 128 (bits), but
_SRS call SIO1.DSRS -> but operate with the buffer size 144(bits)
CreateByteField (Arg0, 0x11, DRQL)
CreateByteField (Arg0, 0x14, DMAC)
so the error is from, the current resource tell kernel using 128bits, but the
set resource operate 144bits.
see the ACPI table,
the _CSR->DCSR always return CRS1,
Method (DCRS, 2, NotSerialized)
{
If (LEqual (Arg0, Zero))
{
ENFG (0x0C)
Store (CR6A, Local0)
Store (Local0, IOLO)
Store (CR6B, Local0)
Store (Local0, IOHI)
Store (IOLO, IORL)
Store (IOHI, IORH)
Store (0x08, LNA1)
Store (GIRQ (Arg0), IRQL)
EXFG ()
Return (CRS1)
}
Return (CRS1)
}
but the _SRS, parse/execution the resoure exceeds the CSR1 buffer,
Method (DSRS, 2, NotSerialized)
{
CreateByteField (Arg0, 0x02, IOLO)
CreateByteField (Arg0, 0x03, IOHI)
CreateWordField (Arg0, 0x09, IRQL)
CreateByteField (Arg0, 0x11, DRQL)
CreateByteField (Arg0, 0x14, DMAC)
If (LEqual (Arg1, Zero))
{
ENFG (0x0C)
STIO (0x6A, IOLO, IOHI, Zero)
SIRQ (Arg1, IRQL)
EXFG ()
DCNT (Arg1, One)
}
}
The errors above seem to cause from a buggy firmware, and need to be checked.
It might impact the UART devices, but driver might take care the UART functions.
These failures should not impact the S3 function.
--
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] Sometimes system won't be able to run suspend
stress test
Status in HWE Next Project:
New
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
CID: 201302-12682 Dell OptiPlex 3011
Sometimes this system cannot be suspended for multiple times with
sudo fwts -P s3 --s3-multiple=5 --s3-device-check --s3-device-check-delay 45
(The first suspend cycle probably would success)
Error could be found in the log file:
S3 cycle 1 of 5
pm-suspend returned 128 after 20 seconds.
FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 20 seconds,
less
than the expected 30 seconds.
FAILED [HIGH] PMActionPowerStateS3: Test 1, pm-action tried to put the machine
in the requested power state but failed.
When this happened, even suspend with the system menu would fail.
I do have it successfully suspend for 5 times once.
Steps:
1. Install 14.04, boot to desktop
2. Try to suspend this system for multiple times with the command above
3. Reboot and re-test it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified:
boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1339 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jun 24 02:25:16 2014
HibernationDevice: RESUME=UUID=1877e238-0ac4-41ae-8f13-91e1e3636b73
InstallationDate: Installed on 2014-06-19 (4 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. OptiPlex 3011 AIO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-ge
[Kernel-packages] [Bug 1335026] Re: [Dell OptiPlex 3011] Sometimes system won't be able to run suspend stress test
As for the fwts S3 test find device configuration differences. s3: Found 1 differences in device configuation during S3 cycle. This mean fwts checks the the device configuration between sleep and wake, and it found a device configuration is different. This is not the cause of S3 fail but it shows the device might have problem before and after sleep. compare device configuration, it shows Device: event5 Device Name: Laptop_Integrated_Webcam_HD Phy: usb-:00:14.0-4/button is gone after waking up. All clues point to USB might have problem, need the USB expert to look 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] Sometimes system won't be able to run suspend stress test Status in HWE Next Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: CID: 201302-12682 Dell OptiPlex 3011 Sometimes this system cannot be suspended for multiple times with sudo fwts -P s3 --s3-multiple=5 --s3-device-check --s3-device-check-delay 45 (The first suspend cycle probably would success) Error could be found in the log file: S3 cycle 1 of 5 pm-suspend returned 128 after 20 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 20 seconds, less than the expected 30 seconds. FAILED [HIGH] PMActionPowerStateS3: Test 1, pm-action tried to put the machine in the requested power state but failed. When this happened, even suspend with the system menu would fail. I do have it successfully suspend for 5 times once. Steps: 1. Install 14.04, boot to desktop 2. Try to suspend this system for multiple times with the command above 3. Reboot and re-test it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1339 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 24 02:25:16 2014 HibernationDevice: RESUME=UUID=1877e238-0ac4-41ae-8f13-91e1e3636b73 InstallationDate: Installed on 2014-06-19 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=d6534767-b55e-4ec0-b18e-cb1151963470 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd02/22/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1335026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332389] Re: [Dell OptiPlex 3011 AIO] High failures found in suspend report
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 received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1332389 Title: [Dell OptiPlex 3011 AIO] High failures found in suspend report Status in “linux” package in Ubuntu: Won't Fix Bug description: CID: 201302-12682 Dell OptiPlex 3011 The following HIGH failures could be found in the suspend report: s3: Found 1 differences in device configuation during S3 cycle. 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), AE_AML_BUFFER_LIMIT (20131115/psparse-536) s3: HIGH Kernel message: [ 660.997517] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.UAR1._SRS] (Node 880078313258), AE_AML_BUFFER_LIMIT (20131115/psparse-536) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1430 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 23:09:39 2014 HibernationDevice: RESUME=UUID=1877e238-0ac4-41ae-8f13-91e1e3636b73 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=d6534767-b55e-4ec0-b18e-cb1151963470 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd02/22/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1332389] Re: [Dell OptiPlex 3011 AIO] High failures found in suspend report
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), AE_AML_BUFFER_LIMIT (20131115/psparse-536) s3: HIGH Kernel message: [ 660.997517] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.UAR1._SRS] (Node 880078313258), AE_AML_BUFFER_LIMIT (20131115/psparse-536) it should be the same as 1232975, please refer to, https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1232975/comments/4 ** Changed in: linux (Ubuntu) Status: Triaged => 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/1332389 Title: [Dell OptiPlex 3011 AIO] High failures found in suspend report Status in “linux” package in Ubuntu: Won't Fix Bug description: CID: 201302-12682 Dell OptiPlex 3011 The following HIGH failures could be found in the suspend report: s3: Found 1 differences in device configuation during S3 cycle. 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), AE_AML_BUFFER_LIMIT (20131115/psparse-536) s3: HIGH Kernel message: [ 660.997517] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.UAR1._SRS] (Node 880078313258), AE_AML_BUFFER_LIMIT (20131115/psparse-536) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1430 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 23:09:39 2014 HibernationDevice: RESUME=UUID=1877e238-0ac4-41ae-8f13-91e1e3636b73 InstallationDate: Installed on 2014-06-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=d6534767-b55e-4ec0-b18e-cb1151963470 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd02/22/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1433992] Re: [Lenovo E450] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests.' always fail
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 conflict IO 0x0B00, betwteen
Scope (_SB.PCI0.SMB)
{
Mutex (SBX0, 0x00)
OperationRegion (SMB0, SystemIO, 0x0B00, 0x10)
Field (SMB0, ByteAcc, NoLock, Preserve)
{
HST0, 8,
SLV0, 8,
CNT0, 8,
CMD0, 8,
ADD0, 8,
DT00, 8,
DT10, 8,
BLK0, 8
}
...
and
Device (SYSR)
{
Name (_HID, EisaId ("PNP0C02")) // _HID: Hardware ID
Name (_CRS, ResourceTemplate () // _CRS: Current Resource
Settings
{
IO (Decode16,
0x0B00, // Range Minimum
0x0B00, // Range Maximum
0x01, // Alignment
0x20, // Length
)
IO (Decode16,
}
** Changed in: hwe-next
Status: New => Won't Fix
--
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/1433992
Title:
[Lenovo E450] 'Run Firmware Test Suite (fwts) desktop-specific
diagnosis tests.' always fail
Status in HWE Next Project:
Won't Fix
Status in linux package in Ubuntu:
Incomplete
Status in linux-lts-utopic package in Ubuntu:
New
Bug description:
CID : 201407-15368 Lenovo E450 (A+A) with 14.04.2 (utopic)
Steps:
1. Install 14.04.2 on E450
2. Install Plainbox and run test case 'Run FWTS desktop-specific diagnosis
tests.'
Expected result:
Test result should be pass.
Actual result:
High Failures: 1
WARNING: The following test cases were reported as high
level failures by fwts. Please review the log at
/home/u/.cache/plainbox/sessions/pbox-1aqqz37_.session/CHECKBOX_DATA/fwts_desktop_diagnosis_results.log
for more information.
- klog
Medium Failures: 2
WARNING: The following test cases were reported as medium
level failures by fwts. Please review the log at
/home/u/.cache/plainbox/sessions/pbox-1aqqz37_.session/CHECKBOX_DATA/fwts_desktop_diagnosis_results.log
for more information.
- acpitables
- mtrr
Low Failures: 1
WARNING: The following test cases were reported as low
level failures by fwts. Please review the log at
/home/u/.cache/plainbox/sessions/pbox-1aqqz37_.session/CHECKBOX_DATA/fwts_desktop_diagnosis_results.log
for more information.
- mcfg
Passed: 5
- mpcheck
- version
- apicedge
- apicinstance
- hpet_check
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified:
boot/vmlinuz-3.16.0-30-generic]
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 19 05:51:36 2015
InstallationDate: Installed on 2015-03-18 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1433992/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1444834] Re: [Dell Latitude E5550 - Houston 15 BDW] could not find boot partition after installing system via live USB (both of legacy and UEFI)
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 E5550 - Houston 15 BDW] could not find boot partition after installing system via live USB (both of legacy and UEFI) Status in HWE Next Project: In Progress Status in linux-lts-utopic package in Ubuntu: New Bug description: Hardware: (CID201409-15490) Dell Latitude E5550 - Houston 15 BDW Steps to reproduce this bug: 1. install the system via a live usb (both of legacy or UEFI could reproduce this bug) 2. select default setting is asked by the installation menu. 3. reboot after the GUI provided the "successful installation" message Expected result: reboot to the fresh installation system. get ready to be in Ubuntu world Actual result: could not find bootable device (both of legacy and UEFI shows this kind of message) More information: Because I could not access the installed system, I collected possible information for debugging under the live usb desktop. Please refer to the attachment bug-report-201409-15490.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1444834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1444834] Re: [Dell Latitude E5550 - Houston 15 BDW] could not find boot partition after installing system via live USB (both of legacy and UEFI)
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 that ubuntu created \efi\ubuntu\shimx64.efi. Even manually set up the boot path on the Bios setup menu doesn't work. This is bug from bios, set it as won't fix. May need to be fixed for update the Bios. ** Changed in: hwe-next Status: In Progress => Won't Fix -- 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 E5550 - Houston 15 BDW] could not find boot partition after installing system via live USB (both of legacy and UEFI) Status in HWE Next Project: Won't Fix Status in linux-lts-utopic package in Ubuntu: New Bug description: Hardware: (CID201409-15490) Dell Latitude E5550 - Houston 15 BDW Steps to reproduce this bug: 1. install the system via a live usb (both of legacy or UEFI could reproduce this bug) 2. select default setting is asked by the installation menu. 3. reboot after the GUI provided the "successful installation" message Expected result: reboot to the fresh installation system. get ready to be in Ubuntu world Actual result: could not find bootable device (both of legacy and UEFI shows this kind of message) More information: Because I could not access the installed system, I collected possible information for debugging under the live usb desktop. Please refer to the attachment bug-report-201409-15490.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1444834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1452979] Re: [Lenovo W550s] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests' test case is always fail.
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: [ 65.525893] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) klog: CRITICAL Kernel message: [ 65.525898] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) klog: CRITICAL Kernel message: [ 65.525899] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) klog: CRITICAL Kernel message: [ 65.525899] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) are from the kernel warning about the temperature too high and start the CPU clock throttled which caught by fwts. this should not be any software issues. Might the HW or cooling issue of the machine. -- 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/1452979 Title: [Lenovo W550s] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests' test case is always fail. Status in HWE Next Project: New Status in linux package in Ubuntu: Incomplete Bug description: CID : 201412-16338 Lenovo W550s (I+N) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on W550s 2. Install Plainbox and run test case 'Run FWTS desktop-specific diagnosis tests.' Expected result: Test result should be pass. Actual result: == ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525891] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525893] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525898] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525899] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525899] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. Found 7 unique errors in kernel log. == ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 8 00:22:38 2015 InstallationDate: Installed on 2015-05-04 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStat
[Kernel-packages] [Bug 1452979] Re: [Lenovo W550s] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests' test case is always fail.
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 optional object is a control method that enables devices to provide device specific control functions that are consumed by the device driver. Arguments: (4) Arg0 – A Buffer containing a UUID Arg1 – An Integer containing the Revision ID Arg2 – An Integer containing the Function Index Arg3 – A Package that contains function-specific arguments the #4 Arg (i.e Arg3 is defined as a Package) , but seems the graphic driver bright an Buffer to it. This has often been seen on the graphic driver, since the _DSM is device specific method. This shouldnot be a problem if the graphic function is fine. ** Changed in: hwe-next Status: New => 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/1452979 Title: [Lenovo W550s] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests' test case is always fail. Status in HWE Next Project: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: CID : 201412-16338 Lenovo W550s (I+N) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on W550s 2. Install Plainbox and run test case 'Run FWTS desktop-specific diagnosis tests.' Expected result: Test result should be pass. Actual result: == ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525891] CPU1: Core temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525893] CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525898] CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525899] CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. FAILED [CRITICAL] KlogThermalOverrun: Test 1, CRITICAL Kernel message: [ 65.525899] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) ADVICE: Test caused CPU temperature above critical threshold. The CPU has been throttled to run slower because of over-heating above the critical threshold. CPU throttling will be turned off once the CPU has cooled sufficiently. Frequent throttling may indicate poor thermal design on the machine. Found 7 unique errors in kernel log. == ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 8 00:22:38 2015 InstallationDate: Installed on 2015-05-04 (3 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probabl
[Kernel-packages] [Bug 1464490] Re: Elan new touchpad recognized as a mouse and doesn't work
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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464490 Title: Elan new touchpad recognized as a mouse and doesn't work Status in HWE Next Project: In Progress Status in linux package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: New Bug description: Elan new touchpad recognized as a mouse, here is the steps to reproduce the bug: Steps: 1. try scrolling with touchpad Expected results: Touchpad features such as scrolling should be supported Actual results: Touchpad features such as scrolling are not supported Actually we need add new icbody type to fix the bug, and mainline kernel has the fix, commit is: 692dd1916436164e228608803dfb6cb768d6355a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1464490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1464490] Re: Elan new touchpad recognized as a mouse and doesn't work
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 Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1464490 Title: Elan new touchpad recognized as a mouse and doesn't work Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: New Status in linux source package in Trusty: Fix Committed Status in linux-lts-trusty source package in Trusty: New Bug description: Elan new touchpad recognized as a mouse, here is the steps to reproduce the bug: Steps: 1. try scrolling with touchpad Expected results: Touchpad features such as scrolling should be supported Actual results: Touchpad features such as scrolling are not supported Actually we need add new icbody type to fix the bug, and mainline kernel has the fix, commit is: 692dd1916436164e228608803dfb6cb768d6355a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1464490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1401466] Re: [Dell Inspiron 2350] fwts high failure:method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'.
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. https://bugs.launchpad.net/bugs/1401466 Title: [Dell Inspiron 2350] fwts high failure:method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'. Status in HWE Next Project: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron 2350 (CID 201305-13669) with Ubuntu 14.04.1 Linux 201305-13669 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The following fwts high failure was found: method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._UPC'. method: Detected error 'No return value' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS15._UPC'. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1476 F pulseaudio /dev/snd/controlC1: ubuntu 1476 F pulseaudio CurrentDesktop: Unity CurrentDmesg: [ 15.148179] thinkpad_ec: no ThinkPad embedded controller! [ 17.013792] init: plymouth-upstart-bridge main process ended, respawning [ 17.021574] init: plymouth-upstart-bridge main process ended, respawning [ 17.969005] r8169 :03:00.0 eth0: link up [ 17.969013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=a6237ffe-4fa9-4ab7-9253-55430263f86f InstallationDate: Installed on 2014-12-08 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 2350 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=fe7cefb8-002c-4091-9a6e-6cab455727b5 ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/02/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 08NG84 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/02/2013:svnDellInc.:pnInspiron2350:pvr00:rvnDellInc.:rn08NG84:rvrX01:cvnDellInc.:ct13:cvr00: dmi.product.name: Inspiron 2350 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1401466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1404173] Re: [Dell Inspiron 7537] HIGH failures found in FWTS klog report
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 expectation(255 bits). GPE0 Block Length : 20 ==> 32bytes So kernel sent the warnings and truncate it to 255 bits. this is the bug from ACPICA, and a fix patch has sent to upstream. https://lkml.org/lkml/2014/4/29/700 Fortunately, it might not impact a lot, and fwts has been lower the issue to medium. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: hwe-next Status: New => 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/1404173 Title: [Dell Inspiron 7537] HIGH failures found in FWTS klog report Status in HWE Next Project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201306-13868 Dell Inspiron 7537 There are four high failure reported in the klog log: High failures: 4 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) I think this one was confirmed not a blocker in bug 1363775 klog: HIGH Kernel message: [0.257172] \_SB_.PCI0:_OSC invalid UUID I think this one was confirmed not a blocker in bug 1279169 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 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1750 F pulseaudio /dev/snd/controlC1: ubuntu 1750 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Dec 19 04:52:02 2014 HibernationDevice: RESUME=UUID=1037e06d-3f36-4dbc-a80a-31400fcf4165 InstallationDate: Installed on 2014-12-17 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=8ffaa535-6ef2-4aa6-b934-cb06b23881b9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: C35 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrC35:bd12/10/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1404173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1404173] Re: [Dell Inspiron 7537] HIGH failures found in FWTS klog report
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 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) the same as bug#1413849 https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1413849 -- 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/1404173 Title: [Dell Inspiron 7537] HIGH failures found in FWTS klog report Status in HWE Next Project: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201306-13868 Dell Inspiron 7537 There are four high failure reported in the klog log: High failures: 4 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) I think this one was confirmed not a blocker in bug 1363775 klog: HIGH Kernel message: [0.257172] \_SB_.PCI0:_OSC invalid UUID I think this one was confirmed not a blocker in bug 1279169 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 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1750 F pulseaudio /dev/snd/controlC1: ubuntu 1750 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Dec 19 04:52:02 2014 HibernationDevice: RESUME=UUID=1037e06d-3f36-4dbc-a80a-31400fcf4165 InstallationDate: Installed on 2014-12-17 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=8ffaa535-6ef2-4aa6-b934-cb06b23881b9 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: C35 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrC35:bd12/10/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1404173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: New Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644806 Title: Proposed shim package will cause system complain "Failed to set MokSBStateRT: (2) Invalid Parameter" Status in linux package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: New Bug description: CID: 201606-22528 The proposed shim package will cause this laptop complain about: "Failed to set MokSBStateRT: (2) Invalid Parameter" on boot. You will see a blue screen after the Dell logo (please find the attached screenshot). Hit ok will continue to boot. BIOS setting UEFI + SecureBoot Enabled Steps: 1. Install 14.04.1 + dist-upgrade 2. Reboot to see if everything is ok 3. Enable proposed + dist-upgrade 4. Reboot, and you will see this issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-49-generic 4.4.0-49.70 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1611 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 25 07:03:10 2016 HibernationDevice: RESUME=UUID=b1256199-2e00-45a5-999c-0b81ea3fcfa6 InstallationDate: Installed on 2016-11-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0cf3:e005 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 15-3568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic.efi.signed root=UUID=f6e40ce3-8944-47c0-ac5d-592570800352 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-49-generic N/A linux-backports-modules-4.4.0-49-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd07/22/2016:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1152458] Re: HP Pavilion g7 - Assorted FWTS HIGH failures during testing
For the Unknown event_id - 10 - 0x1 error,
from the comment#9,
There are no impacts but only an error message. And should not be a
cert-blocker.
Set it as Won't Fix.
** Changed in: linux (Ubuntu Quantal)
Status: Fix Committed => Won't Fix
** Changed in: linux (Ubuntu Raring)
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 is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1152458
Title:
HP Pavilion g7 - Assorted FWTS HIGH failures during testing
Status in HWE Next Project:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “linux” source package in Quantal:
Won't Fix
Status in “linux” source package in Raring:
Won't Fix
Status in “linux” source package in Saucy:
Fix Released
Bug description:
This is another Pavilion G7 model, with assorted HIGH failures encountered
during certification of 12.04.2 with various tests that use fwts. I have
attached the batch run log and the suspend_30_cycles log.
There were also errors in the Hibernate log, but they were identical to the
ones in the suspend log regaring hp_wmi
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1498 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x5261 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76d9,103c1845,00100107
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 11
Date: Fri Mar 8 01:08:04 2013
HibernationDevice: RESUME=UUID=e65da86c-4522-494e-bee7-2dc02c1a910c
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=92c1ee52-075d-4282-97b3-c43eef01f6cf ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1845
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr07981000501630100:rvnHewlett-Packard:rn1845:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 07981000501630100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1152458/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1148649] Re: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing
For the CMOS issue, still waiting the Patch in comment#7 to be accepted. ** Changed in: linux (Ubuntu) Status: Triaged => 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/1148649 Title: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing Status in “linux” package in Ubuntu: In Progress Bug description: Gonna just start putting them all into a single bug for each machine, otherwise I'll be filing 2 - 4 bugs per machine just about every time I do a certification test ;-) So this is 12.04.2 plus latest SRU kernel for certification. FWTS reported HIGH errors during Hibernate, Suspend and batch testing. I've attached the logs from each. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fwts 0.25.06precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Mar 6 00:21:36 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1151664] Re: HP Pavilion g7 - FWTS failures when doing cert testing
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, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert testing
Status in “linux” package in Ubuntu:
In Progress
Bug description:
During cert testing, several FWTS tests returned HIGH or critical
failures. Logs are attached.
This occurred during hibernate, suspend and batch testing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1599 F pulseaudio
/dev/snd/controlC0: ubuntu 1599 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0344000 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf034 irq 16'
Mixer name : 'IDT 92HD87B2/4'
Components : 'HDA:111d76d9,103c184b,00100107'
Controls : 18
Simple ctrls : 10
Date: Thu Mar 7 03:18:22 2013
HibernationDevice: RESUME=UUID=09dbe284-769a-4cba-95e3-b0c6e7c8d1f6
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=12f59f42-f1b9-49fc-af07-88195f43aeee ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 184B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr079F1000501020100:rvnHewlett-Packard:rn184B:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 079F1000501020100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1175475] Re: [HP Pavilion Slimline S5] fwts_test reports Critical /High falures for hibernation/suspend test
More detail information,
This is caused by the wmi driver(hp-wmi.c) brings the input data 160bits
struct bios_args {
u32 signature;
u32 command;
u32 commandtype;
u32 datasize;
u32 data; --- 4 bytes data
};
into the the acpi method HWMC as Arg1,
Method (HWMC, 2, NotSerialized)
{
CreateDWordField (Arg1, Zero, SGIN)
CreateDWordField (Arg1, 0x04, COMD)
CreateDWordField (Arg1, 0x08, CMDT)
CreateDWordField (Arg1, 0x0C, DSZI)
CreateByteField (Arg1, 0x10, D008)
CreateByteField (Arg1, 0x11, D009)
CreateByteField (Arg1, 0x12, D010)
CreateField (Arg1, 0x80, 0x0400, D128) --- 128 bytes
.
}
the error occurred because the mismatch between the 4bytes "data" provided, but
the firmware 128 bytes "D128" used.
checking with the HP wmi spec, several wmi command type used input date 128
bytes (such as type 36h, Set Peak Shift Times, type 37h Set Battery Charging
Times). But this is not used by the hp-wmi.c. It is not reasonable to
CreateField for 128bytes at the method beginning, in stead, it should be
createfielded while it is used.
So I suggest the firmware should move the
CreateField (Arg1, 0x80, 0x0400, D128)
into the place that D128 is used, such as the type 36h, 37h.
If (LEqual (CMDT, 0x36))
{
move to here CreateField (Arg1, 0x80, 0x0400, D128)
Store (\_SB.WMID.SPST (D128), Local2)
Store (Zero, RETC)
}
If (LEqual (CMDT, 0x37))
{
move to here --- CreateField (Arg1, 0x80, 0x0400, D128)
Store (\_SB.WMID.SBCT (D128), Local2)
Store (Zero, RETC)
}
but actually the D128 isn't really used by (type 36h, type 37h) and other type.
If (LEqual (CMDT, 0x36))
{
Store (\_SB.WMID.GPST (), Local2)
Store (Zero, RETC)
}
If (LEqual (CMDT, 0x37))
{
Store (\_SB.WMID.GBCT (), Local2)
Store (Zero, RETC)
}
So directly remove
CreateField (Arg1, 0x80, 0x0400, D128) in the firmware is suggested.
--
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/1175475
Title:
[HP Pavilion Slimline S5] fwts_test reports Critical /High falures for
hibernation/suspend test
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
CID: 201205-11052 (HP Pavilion Slimline S5)
Ubuntu 12.04.2 LTS
suspend_single.log, suspend_30_cycles.log, hibernate-single.log and
hibernate_30_cycles.log are attached.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1547 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 50'
Mixer name : 'IDT 92HD73E1X5'
Components : 'HDA:111d7676,103c2ada,00100103'
Controls : 39
Simple ctrls : 21
Date: Thu May 2 02:39:35 2013
HibernationDevice: RESUME=UUID=0059822b-2011-4dbc-aea6-3e1aff45462e
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=c6420b34-c860-4df2-99fd-9fa1a0b893b7 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2013
dmi.bios.vendor: AMI
dmi.bios.version: 00.05
dmi.board.name: 2ADA
dmi.board.ve
[Kernel-packages] [Bug 1021496] Re: [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 Precise)
Status: Confirmed => Invalid
** Changed in: fwts
Status: New => Fix Committed
** Changed in: linux (Ubuntu Precise)
Assignee: Ivan Hu (ivan.hu) => (unassigned)
--
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.
Status in Firmware Test Suite:
Fix Committed
Status in “linux” package in Ubuntu:
Triaged
Status in “linux” source package in Precise:
Invalid
Bug description:
Problem:
System fails to suspend without kernel errors.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
Command used:
sudo fwts s3 --s3-device-check --s3-device-check-delay=30 --s3-sleep-delay=30
--s3-multiple=250 -r suspend_250_cycles.log
Errors seen:
00016 s3 pm-suspend returned 0 after 39 seconds.
00017 s3 FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel
message: [12243.543703]
00018 s3 [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset
0) for vector 0x400, but
00019 s3 the register is already in use for vector 0xf9 on
another cpu
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,10280479,0011'
Controls : 23
Simple ctrls : 11
Date: Thu Jul 5 17:49:20 2012
HibernationDevice: RESUME=UUID=ca47cb84-ba0d-4417-90c2-f9aa5add4fd8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. Inspiron One 2305
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=075a13ce-7891-4635-9608-4ad5a7153240 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.79
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0DPRF9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA05:bd11/11/2010:svnDellInc.:pnInspironOne2305:pvrNotSpecified:rvnDellInc.:rn0DPRF9:rvrA00:cvnDellInc.:ct13:cvrNotSpecified:
dmi.product.name: Inspiron One 2305
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,10280479,0011'
Controls : 23
Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ca47cb84-ba0d-4417-90c2-f9aa5add4fd8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. Inspiron One 2305
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=075a13ce-7891-4635-9608-4ad5a7153240 ro quiet splash initcall_debug
vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generi
[Kernel-packages] [Bug 1021496] Re: [Dell Inspiron One 2305]: Fails to suspend without errors.
** 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.
Status in Firmware Test Suite:
Fix Released
Status in “linux” package in Ubuntu:
Triaged
Status in “linux” source package in Precise:
Invalid
Bug description:
Problem:
System fails to suspend without kernel errors.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
Command used:
sudo fwts s3 --s3-device-check --s3-device-check-delay=30 --s3-sleep-delay=30
--s3-multiple=250 -r suspend_250_cycles.log
Errors seen:
00016 s3 pm-suspend returned 0 after 39 seconds.
00017 s3 FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel
message: [12243.543703]
00018 s3 [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset
0) for vector 0x400, but
00019 s3 the register is already in use for vector 0xf9 on
another cpu
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image (not installed)
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,10280479,0011'
Controls : 23
Simple ctrls : 11
Date: Thu Jul 5 17:49:20 2012
HibernationDevice: RESUME=UUID=ca47cb84-ba0d-4417-90c2-f9aa5add4fd8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. Inspiron One 2305
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=075a13ce-7891-4635-9608-4ad5a7153240 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.79
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0DPRF9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA05:bd11/11/2010:svnDellInc.:pnInspironOne2305:pvrNotSpecified:rvnDellInc.:rn0DPRF9:rvrA00:cvnDellInc.:ct13:cvrNotSpecified:
dmi.product.name: Inspiron One 2305
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1717 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfeb0 irq 16'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,10280479,0011'
Controls : 23
Simple ctrls : 11
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ca47cb84-ba0d-4417-90c2-f9aa5add4fd8
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Dell Inc. Inspiron One 2305
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic
root=UUID=075a13ce-7891-4635-9608-4ad5a7153240 ro quiet splash initcall_debug
vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic N/A
linux-backports-modules-3.2.0-23-generic N/A
linux-firmware1.79
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: No upgrade lo
[Kernel-packages] [Bug 1116659] Re: HIGH failure detected during S3 test
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. https://bugs.launchpad.net/bugs/1116659 Title: HIGH failure detected during S3 test Status in “linux” package in Ubuntu: Invalid Bug description: This was found in the logs and I need some idea of whether this should block a certification: FAILED [HIGH] KlogFirmwareBug: Test 1, HIGH Kernel message: [ 3527.661337] [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400, but the register is already in use for vector 0xf9 on another cpu The full log is attached. The system ran through 30 cycles of S3 and each cycles got this error, however, it also went through 30 of S4 without this issue, and it then ran several hours of stress without a problem. You can view the system here: https://certification.canonical.com/hardware/201302-12676/submission/i0ryyDGuuBim19Y I do NOT have access to the hardware, and it is unlikely we'll get much help with a firmware fix if this is something that you think should gate the certification. Just FYI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1194751] Re: [Dell Inspiron One 2330] High ACPI failures in Suspend/Hibernate log
Please provide Acpidump for further investigation. Thanks! by sudo acpidump > acpidump.dat ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1194751 Title: [Dell Inspiron One 2330] High ACPI failures in Suspend/Hibernate log Status in “linux” package in Ubuntu: Incomplete Bug description: CID: 201202-10555 Dell Inspiron One 2330 (12.10 kernel 3.5.0-34) Many high failures in Suspend/Hibernate log, they all complaining about the same thing: High failures: 4 s3: HIGH Kernel message: [81181.951324] ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20120320/psargs-359) s3: HIGH Kernel message: [81181.951331] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node 880070f19758), AE_NOT_FOUND (20120320/psparse-536) s3: HIGH Kernel message: [81182.133594] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness s3: HIGH Kernel message: [81186.324011] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node 880070f196e0), AE_NOT_FOUND (20120320/psparse-536) Suspend/Hibernate log attached. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-34-generic 3.5.0-34.55 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic x86_64 ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1798 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) Date: Wed Jun 26 14:49:15 2013 HibernationDevice: RESUME=UUID=980ce671-2412-4159-995e-0fca7a090db3 InstallationDate: Installed on 2013-06-24 (1 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron One 2330 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-34-generic root=UUID=7e274c33-6405-4c6f-ad0c-e41ee0bd73c9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-34-generic N/A linux-backports-modules-3.5.0-34-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 00 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd11/02/2012:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr00: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1194751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1148649] Re: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing
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/linux/+bug/1143312/comments/29 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/30 -- 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 suspend/resume and batch testing Status in “linux” package in Ubuntu: In Progress Bug description: Gonna just start putting them all into a single bug for each machine, otherwise I'll be filing 2 - 4 bugs per machine just about every time I do a certification test ;-) So this is 12.04.2 plus latest SRU kernel for certification. FWTS reported HIGH errors during Hibernate, Suspend and batch testing. I've attached the logs from each. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fwts 0.25.06precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Mar 6 00:21:36 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1151664] Re: HP Pavilion g7 - FWTS failures when doing cert testing
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/1143312/comments/29
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1143312/comments/30
--
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 testing
Status in “linux” package in Ubuntu:
In Progress
Bug description:
During cert testing, several FWTS tests returned HIGH or critical
failures. Logs are attached.
This occurred during hibernate, suspend and batch testing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1599 F pulseaudio
/dev/snd/controlC0: ubuntu 1599 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0344000 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf034 irq 16'
Mixer name : 'IDT 92HD87B2/4'
Components : 'HDA:111d76d9,103c184b,00100107'
Controls : 18
Simple ctrls : 10
Date: Thu Mar 7 03:18:22 2013
HibernationDevice: RESUME=UUID=09dbe284-769a-4cba-95e3-b0c6e7c8d1f6
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=12f59f42-f1b9-49fc-af07-88195f43aeee ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 184B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr079F1000501020100:rvnHewlett-Packard:rn184B:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 079F1000501020100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234905] Re: [Lenovo E535] High Failures reported Initial brightness and AMD MMCONFIG
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.
https://bugs.launchpad.net/bugs/1234905
Title:
[Lenovo E535] High Failures reported Initial brightness and AMD
MMCONFIG
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
The following High Failures were produced during an fwts run on a
Lenovo E535 laptop:
High failures: 2
klog: HIGH Kernel message: [0.567391] [Firmware Bug]: ACPI: No _BQC
method, cannot determine initial brightness
klog: HIGH Kernel message: [0.668681] pnp 00:07: [Firmware Bug]: [mem
0x-0x disabled] covers only part of AMD MMCONFIG area
[mem 0xf800-0xfbff]; adding more reservations
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-29-generic.
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1831 F pulseaudio
/dev/snd/controlC0: ubuntu 1831 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xe8444000 irq 53'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xe844 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5106,0012'
Controls : 22
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=021fd550-dfce-44fa-86dc-30cde2d89701
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MachineType: LENOVO 3260S08
MarkForUpload: True
NonfreeKernelModules: fglrx wl
Package: linux (not installed)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic
root=UUID=89049656-49ed-4ffc-a4cb-8f3051d497aa ro quiet splash initcall_debug
vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
RelatedPackageVersions:
linux-restricted-modules-3.8.0-29-generic N/A
linux-backports-modules-3.8.0-29-generic N/A
linux-firmware1.79.6
Tags: precise running-unity
Uname: Linux 3.8.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/31/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HHET31WW (1.06 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3260S08
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHHET31WW(1.06):bd05/31/2012:svnLENOVO:pn3260S08:pvrThinkPadEdgeE535:rvnLENOVO:rn3260S08:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3260S08
dmi.product.version: ThinkPad Edge E535
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234905/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1151664] Re: HP Pavilion g7 - FWTS failures when doing cert testing
** 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 testing
Status in “linux” package in Ubuntu:
Fix Released
Bug description:
During cert testing, several FWTS tests returned HIGH or critical
failures. Logs are attached.
This occurred during hibernate, suspend and batch testing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1599 F pulseaudio
/dev/snd/controlC0: ubuntu 1599 F pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0344000 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100300'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic'/'HD-Audio Generic at 0xf034 irq 16'
Mixer name : 'IDT 92HD87B2/4'
Components : 'HDA:111d76d9,103c184b,00100107'
Controls : 18
Simple ctrls : 10
Date: Thu Mar 7 03:18:22 2013
HibernationDevice: RESUME=UUID=09dbe284-769a-4cba-95e3-b0c6e7c8d1f6
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=12f59f42-f1b9-49fc-af07-88195f43aeee ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 184B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.34
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr079F1000501020100:rvnHewlett-Packard:rn184B:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 079F1000501020100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1151664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1148649] Re: HP Pavilion G7 - FWTS HIGH errors during suspend/resume and batch testing
** 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 suspend/resume and batch testing Status in “linux” package in Ubuntu: Fix Released Bug description: Gonna just start putting them all into a single bug for each machine, otherwise I'll be filing 2 - 4 bugs per machine just about every time I do a certification test ;-) So this is 12.04.2 plus latest SRU kernel for certification. FWTS reported HIGH errors during Hibernate, Suspend and batch testing. I've attached the logs from each. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fwts 0.25.06precise1 ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4 Uname: Linux 3.5.0-25-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Wed Mar 6 00:21:36 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fwts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1148649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1468180] Re: [Lenovo ThinkStation S30-3] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests.' always fail
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
'\_SB_.PCI0.SAT0.CHN1.DRV0._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT0.CHN1.DRV1._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT1.CHN0.DRV0._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT1.CHN0.DRV1._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT1.CHN1.DRV0._GTF'.
method: Detected error 'Incorrect operand value' when evaluating
'\_SB_.PCI0.SAT1.CHN1.DRV1._GTF'.
are from the firmware implement ACPI method RATA,
Method (RATA, 1, NotSerialized)
{
CreateByteField (Arg0, Zero, CMDN)
Multiply (CMDN, 0x38, Local0)
CreateField (Arg0, 0x08, Local0, RETB)
Store (RETB, Debug)
Return (Concatenate (RETB, FZTF))
}
and the Local0 equal 0
CreateField (Arg0, 0x08, Local0, RETB)
and a fatal exception is generated
--
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/1468180
Title:
[Lenovo ThinkStation S30-3] 'Run Firmware Test Suite (fwts) desktop-
specific diagnosis tests.' always fail
Status in HWE Next:
New
Status in linux-lts-utopic package in Ubuntu:
New
Bug description:
CID : 201402-14670 Lenovo ThinkStation S30-2) with 14.04.2 (utopic)
Steps:
1. Install 14.04.2 on S30-3
2. Install Plainbox and run test case 'Run FWTS desktop-specific diagnosis
tests.'
Expected result:
Test result should be pass.
Actual result:
High Failures: 2
WARNING: The following test cases were reported as high
level failures by fwts. Please review the log at
/home/u/.cache/plainbox/sessions/pbox-st7krnmk.session/CHECKBOX_DATA/fwts_desktop_diagnosis_results.log
for more information.
- klog
- method
Passed: 8
- version
- mpcheck
- apicedge
- acpitables
- apicinstance
- hpet_check
- mcfg
- msr
Notes:
I have updated the latest BIOS version
u@201402-12670:~$ sudo dmidecode -t 0
[sudo] password for u:
# dmidecode 2.12
SMBIOS 2.7 present.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: A2KT50AUS
Release Date: 03/31/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.50
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified:
boot/vmlinuz-3.16.0-30-generic]
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 24 00:26:47 2015
InstallationDate: Installed on 2015-06-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: u 1693 F pulseaudio
/dev/snd/controlC2: u 1693 F pulseaudio
/dev/snd/controlC0: u 1693 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=b3a2d5c1-e942-4c9d-85a4-e7eb626897a3
InstallationDate: Installed on 2015-06-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
IwConfi
[Kernel-packages] [Bug 1468180] Re: [Lenovo ThinkStation S30-3] 'Run Firmware Test Suite (fwts) desktop-specific diagnosis tests.' always fail
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, 0xED, 0x90, 0x6C, 0xBF, 0x47,
/* 0008 */ 0xA6, 0x2A, 0x26, 0xDE, 0x0F, 0xC5, 0xAD, 0x5C
}))
{
CreateDWordField (Arg3, 0x04, CDW2)
CreateDWordField (Arg3, 0x08, CDW3)
If (WHEA)
{
If (And (CDW2, One))
{
Return (One)
}
}
}
Else
{
Or (CDW1, 0x04, CDW1)
}
Return (Zero)
}
Method (_SB._OSC, 4, NotSerialized) // _OSC: Operating System Capabilities
{
If (WOSC (Arg0, Arg1, Arg3, Arg3))
{
Return (Arg3)
}
Return (Arg3)
}
Seems that firmware only support to report the APEI status, by the Microsoft
WHEA defined UUID "ed855e0c-6c90-47bf-a62a-26de0fc5ad5c"
Kernel expects the _OSC method following the ACPI spec Platform-Wide OSPM
Capabilities UUID(0811B06E-4A27-44F9-8D60-3CBBC22E7B48)
So, when the kernel driver, function acpi_bus_osc_support() in
drivers/acpi/bus.c , checks the platform-Wide OSPM Capabilities with it's UUID,
got the invalid UUID, because firmware ACPI \_SB_:_OSC method checks the
Microsoft WHEA defined UUID.
Although, the Microsoft WHEA defined UUID also be handled by the kernel
driver, function apei_osc_setup() in acpi/apei/apei-base.c, so it should
not have any problems. I still suggest that the firmware implement the
Platform-Wide OSPM Capabilities UUID defined on the ACPI spec, because
it covers the APEI capabilities define.
** Changed in: hwe-next
Status: New => Won't Fix
--
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/1468180
Title:
[Lenovo ThinkStation S30-3] 'Run Firmware Test Suite (fwts) desktop-
specific diagnosis tests.' always fail
Status in HWE Next:
Won't Fix
Status in linux-lts-utopic package in Ubuntu:
New
Bug description:
CID : 201402-14670 Lenovo ThinkStation S30-2) with 14.04.2 (utopic)
Steps:
1. Install 14.04.2 on S30-3
2. Install Plainbox and run test case 'Run FWTS desktop-specific diagnosis
tests.'
Expected result:
Test result should be pass.
Actual result:
High Failures: 2
WARNING: The following test cases were reported as high
level failures by fwts. Please review the log at
/home/u/.cache/plainbox/sessions/pbox-st7krnmk.session/CHECKBOX_DATA/fwts_desktop_diagnosis_results.log
for more information.
- klog
- method
Passed: 8
- version
- mpcheck
- apicedge
- acpitables
- apicinstance
- hpet_check
- mcfg
- msr
Notes:
I have updated the latest BIOS version
u@201402-12670:~$ sudo dmidecode -t 0
[sudo] password for u:
# dmidecode 2.12
SMBIOS 2.7 present.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: A2KT50AUS
Release Date: 03/31/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.50
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified:
boot/vmlinuz-3.16.0-30-generic]
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 24 00:26:47 2015
InstallationDate: Installed on 2015-06-23 (0 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
SourcePackage: linux-lts-utopic
UpgradeStatus: No upgrade log present (probably fresh inst
[Kernel-packages] [Bug 1263863] Re: [HP Pavilion 14] Multiple HIGH/CRITICAL failures found in fwts report
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:
[HP Pavilion 14] Multiple HIGH/CRITICAL failures found in fwts report
Status in linux package in Ubuntu:
Won't Fix
Bug description:
CID: 201303-13115 HP Pavilion 14
Critical failures: 2
klog: CRITICAL Kernel message: [5.345517] ACPI Exception: AE_NOT_FOUND,
Evaluating _PRT [AE_NOT_FOUND] (20121018/pci_irq-269)
klog: CRITICAL Kernel message: [5.722860] [Firmware Bug]: Invalid
critical threshold (0)
High failures: 5
klog: HIGH Kernel message: [5.311964] \_SB_.PCI0:_OSC invalid UUID
klog: HIGH Kernel message: [5.345505] ACPI Error: [AR02] Namespace
lookup failure, AE_NOT_FOUND (20121018/psargs-359)
klog: HIGH Kernel message: [5.345510] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.PEG0._PRT] (Node 8801591fed70), AE_NOT_FOUND
(20121018/psparse-537)
klog: HIGH Kernel message: [ 13.551401] ACPI Error:
[\_SB_.PCI0.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND
(20121018/psargs-359)
klog: HIGH Kernel message: [ 13.551407] ACPI Error: Method parse/execution
failed [\_SB_.PCI0.PEG0.PEGP.DD02._BCL] (Node 880159209cd0), AE_NOT_FOUND
(20121018/psparse-537)
Error message:
klog: HIGH Kernel message: [5.311964] \_SB_.PCI0:_OSC invalid UUID
has been answered in bug 1219669
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1
ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-34-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1771 F pulseaudio
/dev/snd/controlC0: ubuntu 1771 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xc361 irq 49'
Mixer name : 'Intel Haswell HDMI'
Components : 'HDA:80862807,80860101,0010'
Controls : 7
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'PCH'/'HDA Intel PCH at 0xc3614000 irq 50'
Mixer name : 'Realtek ALC282'
Components : 'HDA:10ec0282,103c1974,0013'
Controls : 20
Simple ctrls : 9
Date: Tue Dec 24 01:47:47 2013
HibernationDevice: RESUME=UUID=2b1037ae-50de-4c0c-8924-b3d0ec4aa1d3
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic
root=UUID=9f17ab75-d20e-45c7-a266-3dd0cdd4e0d0 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-3.8.0-34-generic N/A
linux-backports-modules-3.8.0-34-generic N/A
linux-firmware1.79.9
RfKill:
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1974
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.19
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.06:bd05/28/2013:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr089D100630100:rvnHewlett-Packard:rn1974:rvr96.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 14 Notebook PC
dmi.product.version: 089D100630100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263863/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1253942] Re: [Dell Inspiron 3737] Multiple CRITICAL failures found in fwts method test
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. https://bugs.launchpad.net/bugs/1253942 Title: [Dell Inspiron 3737] Multiple CRITICAL failures found in fwts method test Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201305-13639 Dell Inspiron 3737 Steps: 1. Install 12.04.3 + update (3.8.0-33) 2. Boot to desktop, run fwts method test There are many CRITICAL failures reported by fwts when running the method test. Critical failures: 81 method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS01._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS02._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS03._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS04._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS05._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS06._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS07._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS08._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS09._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS15._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP1._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP2._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP3._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP4._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP5._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP6._PLD'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.PDRC._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKA._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKB._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKC._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKD._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKE._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKF._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKG._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKH._CRS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKA._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKB._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKC._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKD._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKE._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKF._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKG._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.LNKH._DIS'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.LPCB.LDR2._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS10._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS11._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS12._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS13._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS14._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.HS15._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP5._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.XHC_.RHUB.SSP6._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.RP01._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.RP04._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0.RP05._STA'. method: Detected error 'Not exist' when evaluating '\_SB_.PCI0
[Kernel-packages] [Bug 2049733] [NEW] Dynamically determine acpi_handle_list size
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 message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. ** Affects: linux (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. https://bugs.launchpad.net/bugs/2049733 Title: Dynamically determine acpi_handle_list size Status in linux package in Ubuntu: New Bug description: [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 message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size
** 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) => Ivan Hu (ivan.hu) -- 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 in linux package in Ubuntu: Invalid Status in linux source package in Mantic: New Bug description: [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 message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size
** 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 in linux package in Ubuntu: Invalid Status in linux source package in Mantic: In Progress Bug description: [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 message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
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 subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: In Progress Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem 0x59dc1000-0x59dc103b] [0.020188] ACPI: Reserving SSDT table memory at [mem 0x59dbe000-0x59dc055c] [0.020189] ACPI: Reserving FIDT table mem
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: Triaged Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173] ACPI: PTDT 0x59D2A000 000D44 (v00 _ASUS_ Notebook 0005 MSFT 010D) [0.020177] ACPI: WSMT 0x59D37000 28 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020181] ACPI: FPDT 0x59D29000 44 (v01 _ASUS_ A M I 01072009 AMI 0113) [0.020184] ACPI: Reserving FACP table memory at [mem 0x59dbd000-0x59dbd113] [0.020186] ACPI: Reserving DSDT table memory at [mem 0x59d6-0x59dbc523] [0.020187] ACPI: Reserving FACS table memory at [mem 0x59ebc000-0x59ebc03f] [0.020187] ACPI: Reserving MCFG table memory at [mem 0
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060981 Title: ACPI BIOS errors Status in linux package in Ubuntu: Won't Fix Bug description: dmesg show the below ACPI errors, is this normal? # dmesg | grep -i acpi [0.00] BIOS-e820: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] BIOS-e820: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] reserve setup_data: [mem 0x59cf8000-0x59dc3fff] ACPI data [0.00] reserve setup_data: [mem 0x59dc4000-0x59eb] ACPI NVS [0.00] efi: ACPI=0x59dc3000 ACPI 2.0=0x59dc3014 TPMFinalLog=0x59e4a000 SMBIOS=0x5a609000 SMBIOS 3.0=0x5a608000 MEMATTR=0x528f6018 ESRT=0x53983818 MOKvar=0x5a5e4000 INITRD=0x4fde3f98 RNG=0x59d28018 TPMEventLog=0x4fdc7018 [0.020042] ACPI: Early table checksum verification disabled [0.020046] ACPI: RSDP 0x59DC3014 24 (v02 _ASUS_) [0.020052] ACPI: XSDT 0x59DC2728 00011C (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020060] ACPI: FACP 0x59DBD000 000114 (v06 _ASUS_ Notebook 01072009 AMI 00010013) [0.020066] ACPI: DSDT 0x59D6 05C524 (v02 _ASUS_ Notebook 01072009 INTL 20191018) [0.020070] ACPI: FACS 0x59EBC000 40 [0.020074] ACPI: MCFG 0x59DC1000 3C (v01 _ASUS_ Notebook 01072009 MSFT 0097) [0.020077] ACPI: SSDT 0x59DBE000 00255D (v02 CpuRef CpuSsdt 3000 INTL 20191018) [0.020081] ACPI: FIDT 0x59D5F000 9C (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020084] ACPI: ECDT 0x59D5E000 C1 (v01 _ASUS_ Notebook 01072009 AMI. 0005) [0.020088] ACPI: MSDM 0x59D5D000 55 (v03 _ASUS_ Notebook 01072009 ASUS 0001) [0.020092] ACPI: SSDT 0x59D58000 004F42 (v02 DptfTa DptfTabl 1000 INTL 20191018) [0.020095] ACPI: SSDT 0x59D56000 0017B5 (v02 SaSsdt SaSsdt 3000 INTL 20191018) [0.020099] ACPI: SSDT 0x59D52000 003350 (v02 INTEL IgfxSsdt 3000 INTL 20191018) [0.020103] ACPI: SSDT 0x59D46000 00B1B2 (v02 INTEL TcssSsdt 1000 INTL 20191018) [0.020106] ACPI: HPET 0x59D45000 38 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020110] ACPI: APIC 0x59D44000 00012C (v04 _ASUS_ Notebook 01072009 AMI 0113) [0.020114] ACPI: SSDT 0x59D43000 0002A7 (v02 _ASUS_ TcssSsdt INTL 20191018) [0.020118] ACPI: SSDT 0x59D3B000 007504 (v02 _ASUS_ TglU_Rvp 1000 INTL 20191018) [0.020122] ACPI: NHLT 0x59D39000 001B54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020126] ACPI: LPIT 0x59D38000 CC (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020129] ACPI: SSDT 0x59D36000 00012A (v02 _ASUS_ TbtTypeC INTL 20191018) [0.020133] ACPI: DBGP 0x59D35000 34 (v01 _ASUS_ Notebook 01072009 AMI 0113) [0.020137] ACPI: DBG2 0x59D34000 54 (v00 _ASUS_ Notebook 01072009 AMI 0113) [0.020141] ACPI: SSDT 0x59D33000 000D8A (v02 _ASUS_ UsbCTabl 1000 INTL 20191018) [0.020145] ACPI: DMAR 0x59D32000 B8 (v02 INTEL EDK2 0002 0113) [0.020148] ACPI: SSDT 0x59D31000 0004B8 (v02 HgRef HgRpSsdt 1000 INTL 20191018) [0.020152] ACPI: SSDT 0x59D3 000144 (v02 Intel ADebTabl 1000 INTL 20191018) [0.020155] ACPI: BGRT 0x59D2F000 38 (v01 _ASUS_ Notebook 01072009 AMI 00010013) [0.020159] ACPI: UEFI 0x59E28000 00063A (v01 INTEL RstVmdE ?? ) [0.020163] ACPI: UEFI 0x59E27000 5C (v01 INTEL RstVmdV ?? ) [0.020166] ACPI: TPM2 0x59D2E000 4C (v04 _ASUS_ Notebook 0001 AMI ) [0.020170] ACPI: SSDT 0x59D2B000 002495 (v01 OptRf1 Opt1Tabl 1000 INTL 20191018) [0.020173
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049733 Title: Dynamically determine acpi_handle_list size Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [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 message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047630] [NEW] Add quirk to disable i915 fastboot on B&R PC
Public bug reported: [Impact] Some displays connect to the B&R 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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&R PC Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: [Impact] Some displays connect to the B&R 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B&R PC
** 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&R PC Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] Some displays connect to the B&R 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B&R PC
** 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 => 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/2047630 Title: Add quirk to disable i915 fastboot on B&R PC Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] Some displays connect to the B&R 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B&R PC
** Description changed: [Impact] - Some displays connect to the B&R PC device got the garbled display + Some displays connect to the B&R 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 after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, + but these patches cannot be backported from 5.19 to 5.15. So 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&R PC device 2. Check the display for boot up - [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. -- 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&R PC Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] Some displays connect to the B&R PC device got the garbled display [Fix] The issue will disappear after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, but these patches cannot be backported from 5.19 to 5.15. So 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047630] Re: Add quirk to disable i915 fastboot on B&R PC
Test B&R 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 Ubuntu. https://bugs.launchpad.net/bugs/2047630 Title: Add quirk to disable i915 fastboot on B&R PC Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Some displays connect to the B&R PC device got the garbled display [Fix] The issue will disappear after commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0, but these patches cannot be backported from 5.19 to 5.15. So 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&R PC device 2. Check the display for boot up [Where problems could occur] Quirk only on the B&R PCs. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 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 proposed kernel on Mantic Status in linux package in Ubuntu: Triaged Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1972802 Title: enable config for fixing 5.17 kernel won't load mok Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [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. [Where problems could occur] Low. only affect the checking secureboot enable function. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1972802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** 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 affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: Triaged => In Progress -- 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 Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
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 linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936899 Title: [IoTG] [TGL-H] TPM tests fail Status in intel: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]TPM tests from CDTS 20 automated fail [Steps to reproduce]Run cdts.odm_certification, select TPM [Expected result]All tests should pass. [Actual result] Failed Jobs (TPM 2.0): tpm2.0_4.1.1/tpm2_clockratedadjust tpm2.0_4.1.1/tpm2_createprimary tpm2.0_4.1.1/tpm2_import tpm2.0_4.1.1/tpm2_loadexternal Jobs with failed dependencies tpm2.0_4.1.1/tpm2_rc_decode [Failure rate]100% [Additional information] CID: 202106-29175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1936899
Title:
[IoTG] [TGL-H] TPM tests fail
Status in intel:
New
Status in linux-intel package in Ubuntu:
New
Bug description:
[Summary]TPM tests from CDTS 20 automated fail
[Steps to reproduce]Run cdts.odm_certification, select TPM
[Expected result]All tests should pass.
[Actual result]
Failed Jobs (TPM 2.0):
tpm2.0_4.1.1/tpm2_clockratedadjust
tpm2.0_4.1.1/tpm2_createprimary
tpm2.0_4.1.1/tpm2_import
tpm2.0_4.1.1/tpm2_loadexternal
Jobs with failed dependencies
tpm2.0_4.1.1/tpm2_rc_decode
[Failure rate]100%
[Additional information]
CID: 202106-29175
SKU:
system-manufacturer: Intel Corporation
system-product-name: Tiger Lake Client Platform
bios-version: TGLIFUI1.R00.3455.A03.2011281547
CPU: Genuine Intel(R) CPU @ 2.60GHz (16x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:9a60]
kernel-version: 5.11.0-1009-intel
[Stage]
Issue reported and logs collected right after it happened
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936899 Title: [IoTG] [TGL-H] TPM tests fail Status in intel: New Status in linux-intel package in Ubuntu: New Bug description: [Summary]TPM tests from CDTS 20 automated fail [Steps to reproduce]Run cdts.odm_certification, select TPM [Expected result]All tests should pass. [Actual result] Failed Jobs (TPM 2.0): tpm2.0_4.1.1/tpm2_clockratedadjust tpm2.0_4.1.1/tpm2_createprimary tpm2.0_4.1.1/tpm2_import tpm2.0_4.1.1/tpm2_loadexternal Jobs with failed dependencies tpm2.0_4.1.1/tpm2_rc_decode [Failure rate]100% [Additional information] CID: 202106-29175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933547 Title: tpm driver causes non-fatal kernel crash on boot Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kernel: [1.138781] bus_for_each_dev+0x7e/0xc0 Jun 24 07:22:45 munin kernel: [1.138785] driver_attach+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138789] bus_add_driver+0x135/0x1f0 Jun 24 07:22:45 munin kernel: [1.138793] driver_register+0x95/0xf0 Jun 24 07:22:45 munin kernel: [1.138798] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138805] __platform_driver_register+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
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 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 some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] [NEW] Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT tables firmware
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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. ** Affects: linux (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. https://bugs.launchpad.net/bugs/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT tables firmware Status in linux package in Ubuntu: New Bug description: [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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
** 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 -- 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 some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Bug description: [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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
** 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 some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Bug description: [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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
** 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. https://bugs.launchpad.net/bugs/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: In Progress Bug description: [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. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** 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 Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1025663] Re: DMIStringIndexOutOfRange on HP Proliant ML110 G5
** 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 Status in linux package in Ubuntu: Won't Fix Bug description: We encountered this error when running certification tests in a HP Proliant ML110 G5: FAILED [HIGH] DMIStringIndexOutOfRange: Test 1, Out of range string index 0x09 while accessing entry 'Base Board Information (Type 2)' @ 0x000dc082, field 'Asset Tag', offset 0x08 ADVICE: It may be worth checking against section 7.3 of the System Management BIOS (SMBIOS) Reference Specification (see http://www.dmtf.org/standards/smbios). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-4-generic 3.5.0-4.4 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Jul 17 08:52 seq crw-rw---T 1 root audio 116, 33 Jul 17 08:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.3-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Tue Jul 17 09:25:00 2012 HibernationDevice: RESUME=UUID=c1530c5c-1763-45eb-b575-4504e0de61f6 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Alpha amd64 (20120717) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant ML110 G5 PciMultimedia: ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US LANGUAGE=en_US: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-4-generic root=UUID=90f6a1e1-da49-4ec1-bef7-139784b5a88a ro rootdelay=60 quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-4-generic N/A linux-backports-modules-3.5.0-4-generic N/A linux-firmware 1.84 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2007 dmi.bios.vendor: HP dmi.bios.version: O15 dmi.board.name: A61TT2 dmi.board.vendor: Wistron Corporation dmi.board.version: NA dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 17 dmi.chassis.vendor: HP dmi.chassis.version: N/A dmi.modalias: dmi:bvnHP:bvrO15:bd10/08/2007:svnHP:pnProLiantML110G5:pvrNA:rvnWistronCorporation:rnA61TT2:rvrNA:cvnHP:ct17:cvrN/A: dmi.product.name: ProLiant ML110 G5 dmi.product.version: NA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in OEM Priority Project: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981449] Re: 5.19 kernel does not load MOK keys
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 function, arch_ima_get_secureboot(), needs the config, CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT=y and it's dependency CONFIG_IMA_ARCH_POLICY https://bugs.launchpad.net/oem-priority/+bug/1972802 -- 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/1981449 Title: 5.19 kernel does not load MOK keys Status in linux package in Ubuntu: Confirmed Bug description: The 5.19 kernel only reads the db and dbx keys: jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949' Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f' Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for ~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed' Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: UEFI:dbx Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: UEFI:dbx The 5.15 kernel also loads the mok keys jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for ~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed' Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: UEFI:dbx Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: UEFI:dbx Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for ~ci-train-ppa-service/ubuntu/4093 UEFI: bbfd16fec6b3ba059a0f011203a5cd493a4529b7' Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:MokListRT (MOKvar table) Jun 27 23:10:
[Kernel-packages] [Bug 2077858] Re: Fix ethernet performance on JSL and EHL
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-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/2077858 Title: Fix ethernet performance on JSL and EHL Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: New Status in linux source package in Noble: Fix Committed Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: Fix Released Status in linux-oem-6.11 source package in Oracular: New Bug description: [Impact] Sub-optimal ethernet performance on Intel JSL and EHL platform with Realtek PCIe NIC. Iperf shows the network throughput can only reach around 75% of [Fix] The CPU idle state transition C1 -> C1E -> C0 overhead can be too high, so disabling C1E to increase the IRQ latency and DMA speed. [Test] With the patch applied, iperf shows over 95% of network throughput consistently. [Where problems could occur] Disabling C1E can theoretically increase power consumption slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
