[Tohsiba Portege Z20T-C] Internal speakers don't work after standby

[Michael]

On initial boot, sound on internal speakers is working. After standby it doesn work anymore, but a analog headset does. Switching around in pavucontrol doesn't work... Internal microphone works.

I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

Toshiba/Dynabook Portege Z20T-C:
https://support.dynabook.com/support/modelHome?freeText=1200015981&osId=3333785

WORKAROUND: Use suspend to disk.

---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michi 6510 F.... pulseaudio
CurrentDesktop: GNOME-Flashback:Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=/dev/mapper/1tb-swap
MachineType: TOSHIBA PORTEGE Z20t-C
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic N/A
 linux-firmware 1.157.3
Tags: xenial
Uname: Linux 4.4.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/27/2016
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 5.60
dmi.board.asset.tag: 0000000000
dmi.board.name: PORTEGE Z20t-C
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE Z20t-C
dmi.product.version: PT16BE-00W006GR
dmi.sys.vendor: TOSHIBA

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1612916

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Michael (3-ueuntu-4)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc2/

[Michael (3-ueuntu-4)]

The line "UpgradeStatus: No upgrade log present (probably fresh install)" is correct - it was a clean 16.04 install, and I had the problem from the beginning.

I'll try the mainline Kernel at the next opportunity for a restart :-)

[Michael (3-ueuntu-4)]

Problem exists with 4.8.0-040800rc2-generic as well.

[penalvch (penalvch)]

Michael, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc4) as it is released.

Could you please advise?

[Michael (3-ueuntu-4)]

Same problem with 4.8-rc4.

[penalvch (penalvch)]

Michael, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Michael (3-ueuntu-4)]

I suspended using the gui, resumed using the power button.

root@michis-toshiba:~# cat /sys/kernel/debug/suspend_stats
success: 1
fail: 0
failed_freeze: 0
failed_prepare: 0
failed_suspend: 0
failed_suspend_late: 0
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_early: 0
failed_resume_noirq: 0
failures:
  last_failed_dev:

  last_failed_errno: 0
   0
  last_failed_step:

root@michis-toshiba:~# cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PEG0 S4 *disabled
PEGP S4 *disabled
PEG1 S4 *disabled
PEGP S4 *disabled
PEG2 S4 *disabled
PEGP S4 *disabled
UAR1 S3 *disabled
ECIR S4 *disabled
GLAN S4 *enabled pci:0000:00:1f.6
XHC S3 *enabled pci:0000:00:14.0
XDCI S4 *disabled
HDAS S4 *disabled pci:0000:00:1f.3
RP09 S4 *disabled
PWRB S4 *enabled platform:PNP0C0C:00

The trace thing doesn't work for me:
michi@michis-toshiba:~$ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
[sudo] Passwort für michi:
sh: 1: cannot create /sys/power/pm_trace: Permission denied

michi@michis-toshiba:/sys/power$ ls
disk image_size pm_async pm_freeze_timeout pm_print_times pm_test pm_wakeup_irq reserved_size resume state wakeup_count

michi@michis-toshiba:/sys/power$ uname -a
Linux michis-toshiba 4.8.0-040800rc4-generic #201608312129 SMP Thu Sep 1 01:31:59 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Michael, I'll mark this Triaged for now given you have tested the latest upstream kernel, and hopefully the Ubuntu Audio Team would speak further to this issue.

[Michael (3-ueuntu-4)]

Any news? restarting pulseaudio or reloading snd_soc_skl doesn't help.

pavucontrol shows sound output at the soundcard if playing music.

[Luke Yelavich (themuso)]

You could try getting the latest ALSA driver code, which is not all necessarily in the latest mainline released kernel... https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS.

[Michael (3-ueuntu-4)]

Sadly didn't helped :-(

[penalvch (penalvch)]

Michael, to keep this relevant to upstream, one would want check for, and test the latest mainline kernel (now 4.9-rc4) as it is released.

Could you please advise?

[Michael (3-ueuntu-4)]

No change with 4.9-rc4.

[Michael (3-ueuntu-4)]

This problems happens with current Debian stretch as well.

[Michael (3-ueuntu-4)]

I've made a bug report in Debian's bug tracker system as well (already some time ago, but forgot to mention it) : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851404

[S. Joseph (josephatwork)]

Looks like the issue has not been resoled yet. I can confirm I have the same issue on a Toshiba z20t-B with Ubuntu 19.10 ( 5.3.0-18-generic kernel).

[penalvch (penalvch)]

Michael, it wouldn't hurt to update your BIOS to the latest (now. 6.30), given it includes multiple, high severity security vulnerability fixes.

Once done, could you please advise if this changes anything, and post the results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

If still reproducible, to keep this relevant, please attempt a suspend via live environment of http://cdimage.ubuntu.com/daily-live/current/ and advise on the outcome.

[apsaras (xbuntuone)]

I have the same problem with a Z20T-C (Z20T-C-11H m7-6y75).

I am using Ubuntu 18.04.3 (kernel 5.0.0-32-generic).

I updated to BIOS 6.30, but unfortunately this didn't make any difference.

[pheidrias (5-launchpad-net-pheidrias-info)]

Can confirm the problem still exists with Ubuntu 19.10, all up-to-date.

Where can I dig to debug?

Thanks!

[apsaras (xbuntuone)]

penalvch: in view of the fact that we have independently confirmed the bug with the latest BIOS and the latest Ubuntu, would it now make sense to change the status back to Confirmed (and remove the bios-outdated tag)?

Also, can I ask why you changed the importance down to Low? Having sound not working is a major usability problem, in my opinion.

Thanks.

[penalvch (penalvch)]

apsaras, it's helpful for developers if folks report their own bug so logs may be obtained from the hardware, regardless of similarities, via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

To do otherwise risks issues being ignored as unconfirmable noise.

[apsaras (xbuntuone)]

Thank you for the reply.

Are you saying that you need confirmation from the original bug reporter (Michael) that his problem still exists with the latest BIOS and latest Ubuntu, and that confirmation from other people won't do because we might have a different problem?

I can understand the reasoning behind that policy, but I think in this case it's reasonably clear that we all have the same problem here. If we were all to create separate bug reports describing exactly the same symptoms then that would create confusing distractions and dilute the good efforts of people like you, would it not?

Of course, if it's the only way to proceed then we can create a new report. (Can we be sure that it won't immediately get closed as a duplicate?)

[Michael (3-ueuntu-4)]

I, the original reporter, can confirm that this problem persists with current BIOS and Ubuntu.

[Michael (3-ueuntu-4)]

Arch is affected as well: https://mailman.alsa-project.org/pipermail/alsa-devel/2016-June/109296.html

[apsaras (xbuntuone)]

It's a pity - it's a great laptop apart from this problem, but not being able to shut the lid without losing sound is a significant drawback. It wouldn't be so bad if there were a workaround of some sort, but I've not seen one and I don't know how to go about looking for one.

I tried it with Ubuntu 20.04 (live USB version) and get the same problem.

[Michael (3-ueuntu-4)]

Only workaround is to not use suspend to ram, but suspend to disk.

[Juanma Navarro (juanma1980)]

This bug is very annoying. This problem still exists with every kernel and pulse/pipe combination I'm capable of (tested also with a 6.0 kernel).
No workwaround works but suspend to disk.

[Kai-Heng Feng (kaihengfeng)]

Can you please attach dmesg?

[raki72 (raki72)]

I am using Kubuntu 20.10 on a Toshiba Z20T-C-140 and this bug still exists.

Any way I can help to solve this issue by providing logfiles?

It would be a shame not being able to use this laptop because of this old bug.

[Riversol (riversol)]

I'd been trying Linux on and off over the last 5 years ago with a spare Z20t I have and thought I'd put in some recent findings that might help with this issue.

Z20t-B and z20t-C models seem affected the same, with Ubuntu and Arch based installs - also tried various kernels from 5 through to 6.7.

An interesting finding with one of my spare Z20's, is that when I wiped and decided to try Windows again, (tested with Win8, 10, and 11), this same situation is reproducable:
- Power on, Speakers produce sound
- Put to sleep
- Wake from sleep, Speakers don't produce sound

I found that there's an issue with the latest drivers from Toshiba/Dynabook, even for Windows:

1. Conexant Audio Driver
> Posted Date: 2018-05-21 | Version: 8.66.47.56

2. Conexant Audio Driver
> Posted Date: 2017-12-19 | Version: 8.66.47.50 | Size: 83.52M

The driver from 2018 has the 'sleep-wake speaker not working' issue. But installing the 2017 version works totally fine.

Hopefully this may provide some insight on this issue.