Public bug reported:

[Impact]
Saw the unstable sleep time while running the sleep test.
[  245.081957] Timekeeping suspended for 98.914 seconds
[  351.082704] Timekeeping suspended for 3.017 seconds
[  457.084662] Timekeeping suspended for 98.893 seconds
[  564.087162] Timekeeping suspended for 4.024 seconds

[Fix]
The root cause is from intel-ish-hid driver that fails to respond and blocks 
the suspend process for around 90 seconds totally.
Intel provides a patch to fix this issue.

[Test]
Use fwts to run to sleep test and then check the Timekeeping suspended should 
be around 60.
sudo fwts s3 --s3-multiple=30

[Where problems could occur]
The fix increase the resume timeout from 50ms to 300ms, it should not introduce 
any issue.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: linux-oem-6.11 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux-oem-6.14 (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: linux-oem-6.11 (Ubuntu Noble)
     Importance: Undecided
     Assignee: AceLan Kao (acelankao)
         Status: In Progress

** Affects: linux-oem-6.14 (Ubuntu Noble)
     Importance: Undecided
     Assignee: AceLan Kao (acelankao)
         Status: In Progress


** Tags: jira-stella-1334 oem-priority stella

** Patch added: 
"0001-HID-intel-ish-hid-Increase-ISHTP-resume-ack-timeout-.patch"
   
https://bugs.launchpad.net/bugs/2115390/+attachment/5886207/+files/0001-HID-intel-ish-hid-Increase-ISHTP-resume-ack-timeout-.patch

** Also affects: linux-oem-6.11 (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-6.14 (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

  [Impact]
  Saw the unstable sleep time while running the sleep test.
  [  245.081957] Timekeeping suspended for 98.914 seconds
  [  351.082704] Timekeeping suspended for 3.017 seconds
  [  457.084662] Timekeeping suspended for 98.893 seconds
  [  564.087162] Timekeeping suspended for 4.024 seconds
  
  [Fix]
  The root cause is from intel-ish-hid driver that fails to respond and blocks 
the suspend process for around 90 seconds totally.
  Intel provides a patch to fix this issue.
  
  [Test]
  Use fwts to run to sleep test and then check the Timekeeping suspended should 
be around 60.
  sudo fwts s3 --s3-multiple=30
  
  [Where problems could occur]
+ The fix increase the resume timeout from 50ms to 300ms, it should not 
introduce any issue.

** Changed in: linux-oem-6.11 (Ubuntu Noble)
       Status: New => In Progress

** Changed in: linux-oem-6.14 (Ubuntu Noble)
       Status: New => In Progress

** Changed in: linux-oem-6.14 (Ubuntu Noble)
     Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-6.11 (Ubuntu Noble)
     Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-6.11 (Ubuntu)
       Status: New => Invalid

** Changed in: linux-oem-6.14 (Ubuntu)
       Status: New => Invalid

** Tags added: jira-stella-1334 oem-priority stella

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2115390

Title:
  intel-ish-hid keeps timeout while accessing it during suspend

Status in HWE Next:
  New
Status in linux-oem-6.11 package in Ubuntu:
  Invalid
Status in linux-oem-6.14 package in Ubuntu:
  Invalid
Status in linux-oem-6.11 source package in Noble:
  In Progress
Status in linux-oem-6.14 source package in Noble:
  In Progress

Bug description:
  [Impact]
  Saw the unstable sleep time while running the sleep test.
  [  245.081957] Timekeeping suspended for 98.914 seconds
  [  351.082704] Timekeeping suspended for 3.017 seconds
  [  457.084662] Timekeeping suspended for 98.893 seconds
  [  564.087162] Timekeeping suspended for 4.024 seconds

  [Fix]
  The root cause is from intel-ish-hid driver that fails to respond and blocks 
the suspend process for around 90 seconds totally.
  Intel provides a patch to fix this issue.

  [Test]
  Use fwts to run to sleep test and then check the Timekeeping suspended should 
be around 60.
  sudo fwts s3 --s3-multiple=30

  [Where problems could occur]
  The fix increase the resume timeout from 50ms to 300ms, it should not 
introduce any issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2115390/+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

Reply via email to