[Satellite P50-B, Intel Haswell HDMI, Digital Out, HDMI] No sound at all

Bug #1404589 reported by Antonio Rodriguez on 2014-12-21
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

New Toshiba P50-B, but no sound. "ubuntu-bug -s audio" said that PulseAudio was not configured to use the card I want output from (Built-In Audio - HDA Intel HDMI, but pavucontrol hasn't helped anyway (in pavucontrol, under Configuration tab, all options under Built-In Audio claim that they are unplugged [ 3 options say "Digital Stereo (HDMI) Output (unplugged)", 3 more options say "Digital Surround 5.1 (HDMI) output (unplugged)" and an "Off" option]).

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0c: taser 2786 F...m pulseaudio
 /dev/snd/controlC1: taser 2786 F.... pulseaudio
 /dev/snd/pcmC0D3p: taser 2786 F...m pulseaudio
 /dev/snd/controlC0: taser 2786 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Sat Dec 20 20:51:49 2014
InstallationDate: Installed on 2014-12-18 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Built-in Audio - HDA Intel HDMI
Symptom_DevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0c: taser 2786 F...m pulseaudio
 /dev/snd/controlC1: taser 2786 F.... pulseaudio
 /dev/snd/pcmC0D3p: taser 2786 F...m pulseaudio
 /dev/snd/controlC0: taser 2786 F.... pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Satellite P50-B, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.30
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG20SQ
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd08/14/2014:svnTOSHIBA:pnSatelliteP50-B:pvrPSPNUU-01P02Q:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Satellite P50-B
dmi.product.version: PSPNUU-01P02Q
dmi.sys.vendor: TOSHIBA
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D3p: taser 2935 F...m pulseaudio
 /dev/snd/controlC0: taser 2935 F.... pulseaudio
 /dev/snd/controlC1: taser 2935 F.... pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=UUID=1699f9db-fe96-4e53-893a-49a8bd957d5c
InstallationDate: Installed on 2014-12-18 (3 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: TOSHIBA Satellite P50-B
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=36624408-b7e6-4c9b-8f4a-09fabe5f2d56 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-29-generic N/A
 linux-backports-modules-3.16.0-29-generic N/A
 linux-firmware 1.138.1
Tags: utopic
Uname: Linux 3.16.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 08/14/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.30
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG20SQ
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd08/14/2014:svnTOSHIBA:pnSatelliteP50-B:pvrPSPNUU-01P02Q:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Satellite P50-B
dmi.product.version: PSPNUU-01P02Q
dmi.sys.vendor: TOSHIBA

Antonio Rodriguez (taserian) wrote :
affects: alsa-driver (Ubuntu) → linux-meta (Ubuntu)
Brad Figg (brad-figg) on 2014-12-21
affects: linux-meta (Ubuntu) → linux (Ubuntu)

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

apport-collect 1404589

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.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

description: updated

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium
description: updated

Antonio Rodriguez, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.19-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-fixed-upstream-3.19-rc1
Antonio Rodriguez (taserian) wrote :

Thank you for the indications on how to test this. I installed two kernels from mainline, v3.19.0-rc1 and v3.18.1, and both have my sound working correctly. I'm going to remove v3.19.0-rc1 from this machine, as I'd prefer to use a kernel that's not a release candidate.

I have a question, however. Should I revert to my previous kernel (3.16.0-29), or can I keep v3.18.1 without any adverse effects?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Antonio Rodriguez, the upstream kernel is not supported in Ubuntu as outlined in https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If you want to use this going forward, please feel free to mark this Status Invalid.

However, if you would like to have this fix backported to a Ubuntu supported kernel, the next step is to fully reverse commit bisect from kernel 3.16 to 3.18.1 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Antonio Rodriguez (taserian) wrote :

I've been going through the kernels and trying to determine what's going on, and a curious thing is happening.

If I use a kernel that fixes my sound (v3.18.1-vivid, for example), and then use my old kernel again (v3.16.7-ck2), sound still works. However, if I boot into Windows 8, then return to Ubuntu (v3.16.7-ck2), sound no longer works. I've tested v3.17.1-utopic and I still have no sound, so I'm considering it as a bug-exists kernel.

I'm currently downloading 3.18-rc2 to see if the bug is still present after purposefully losing my sound by booting into Windows 8. The download is going very slowly (close to 4 hours for a ~60MB file). Are there any additional mirrors for kernel images?

tags: added: needs-reverse-bisect
Antonio Rodriguez (taserian) wrote :

I've located the bisect. Kernel v3.18-rc6 has the bug, but V3.18-rc7 seems to fix it. I've removed the previous tag
kernel-fixed-upstream-3.19-rc1
, and added the tag
kernel-fixed-upstream-3.18-rc7
as the earliest fixed kernel.

Is there a tag I should use to show that the bug exists up to 3.18-rc6? And another to show that the reverse bisect is complete?

tags: added: kernel-fixed-upstream-3.18-rc7
removed: kernel-fixed-upstream-3.19-rc1
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Antonio Rodriguez, while you have made progress, finding adjacent kernel versions is not fully bisecting as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404589/comments/35 . Hence, there is not tag to adjust at this time.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers