This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-artful

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  speaker can't output sound anymore after system resumes from S3 on a
  lenovo machine with alc257

Status in HWE Next:
Status in linux package in Ubuntu:
Status in linux-oem package in Ubuntu:
Status in linux source package in Xenial:
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:

Bug description:
  After booting up, the speaker works well. If we suspend the machine then 
  it back, the speaker can't output sound, even rebooting can't make the speaker
  work, we need to power off the machine then power up the machine, the speaker
  can work again.

  We need to add the basic support for the codec alc257 first (0001-xxx.patch),
  then add hooking function for this codec and clear the bit of 15 for register
  0x57 (0002-xxx.patch). Both of these two patches come from mainline kernel.

  [Test Case]
  After booting up the system, suspend the machine, then resume the machine,
  test the speaker, the speaker can output sound. Repeat the testing steps many
  times, the speaker still can work.

  [Regression Potential]
  Very low, since the 1st patch just add the support for a new codec alc257, it
  will not affect other codecs. The 2nd patch just apply a fix for alc257, it
  doesn't affect other codecs too. And both of them come from mainline and

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to