[Bug 1828657] [NEW] Slow resume after lid close/open

[Brian LePage]

Public bug reported:

Summary
1.) Release Info:
    Description: Ubuntu 19.04
    Release:	19.04
2.) Package version: linux-image-5.0.0-13-generic
3.) Expected behavior: Computer resumes shortly after opening lid.
4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid.

I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM.
I found that when it resumes from sleep after opening the lid, it takes
a long time to resume (~2 minutes).

While experimenting with the upstream kernel releases, I found that the
problem was introduced with version 5.0.5 version of the Linux kernel;
the problem does not occur when I run version 5.0.4.

I've narrowed the culprit down to the following commit in the upstream
kernel:

a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for
each codec

This change was applied to the ubuntu kernel with commit
9c51afaceb61459d2becac8fb32c860bb084e643.

The following messages appear in the system log upon resume with the
released ubuntu kernel:

May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel 0000:00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100
May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel 0000:00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100
May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11

These messages do not appear in the system log upon resume when running
with upstream kernel version 5.0.4.

I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww),
but the problem persists.

For now, I will run with the 5.0.4 version of the upstream kernel, as I
am not experiencing any issues with it.

Thank you.

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1828657

Title:
  Slow resume after lid close/open

Status in apport package in Ubuntu:
  New

Bug description:
  Summary
  1.) Release Info:
      Description: Ubuntu 19.04
      Release:	19.04
  2.) Package version: linux-image-5.0.0-13-generic
  3.) Expected behavior: Computer resumes shortly after opening lid.
  4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid.

  I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM.
  I found that when it resumes from sleep after opening the lid, it
  takes a long time to resume (~2 minutes).

  While experimenting with the upstream kernel releases, I found that
  the problem was introduced with version 5.0.5 version of the Linux
  kernel; the problem does not occur when I run version 5.0.4.

  I've narrowed the culprit down to the following commit in the upstream
  kernel:

  a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for
  each codec

  This change was applied to the ubuntu kernel with commit
  9c51afaceb61459d2becac8fb32c860bb084e643.

  The following messages appear in the system log upon resume with the
  released ubuntu kernel:

  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel 0000:00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel 0000:00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100
  May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11

  These messages do not appear in the system log upon resume when
  running with upstream kernel version 5.0.4.

  I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww),
  but the problem persists.

  For now, I will run with the 5.0.4 version of the upstream kernel, as
  I am not experiencing any issues with it.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1828657/+subscriptions