No HDMI Audio Source on Newer Kernels

[hshan]

I am also experiencing this problem.
Ubuntu 15.04

TV plugged in HDMI port

Problem happens with Kernel versions 3.19.0-17 and 3.19.0-18

HDMI audio worked before upgrading from 14.10 to 15.04
HDMI audio works if I select an older kernel (3.16.0-38)

No hdmi source seen on newer kernels, not on pavc either.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-18-generic 3.19.0-18.18
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: steve 2506 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu May 21 06:52:36 2015
HibernationDevice: RESUME=UUID=0cc21abb-9611-459b-a2f3-d72b38316190
InstallationDate: Installed on 2014-09-29 (233 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Acer Aspire S7-392
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=9c0dd135-4539-4895-be0d-25ecc94a9bea ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-18-generic N/A
 linux-backports-modules-3.19.0-18-generic N/A
 linux-firmware 1.143.1
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-27 (23 days ago)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.12
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Storm2
dmi.board.vendor: Acer
dmi.board.version: V2.12
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.12
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12:
dmi.product.name: Aspire S7-392
dmi.product.version: V2.12
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

hshan, 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 by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

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.

[hshan (hshan)]

Tested 4.1.0-040100rc4, and found HDMI input recognized.

[penalvch (penalvch)]

hshan, the next step is to fully reverse commit bisect from kernel 3.19 to 4.1-rc1 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

[hshan (hshan)]

Christopher,

I thought I was following instructions to help locate bug in my instance
or my machine. I wasn't trying to hop in ;-)

But, If it would help, I'd be willing to follow instructions and reverse
bisect the kernel learning as I go, as time permits.

Thanks

Steve

<< FROM
> hshan, the next step is to fully reverse commit bisect from kernel
> 3.19 to 4.1-rc1 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
>
> ** Tags removed: kernel-fixed-upstream-4.1.0-040100rc4 ** Tags added:
> amd64 apport-bug kernel-fixed-upstream kernel-fixed-upstream-4.1-rc4
> latest-bios-2.12 needs-reverse-bisect package-from-proposed vivid
>
> ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the
> bug report. https://bugs.launchpad.net/bugs/1457446
>
> Title: No HDMI Audio Source on Newer Kernels
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457446/+subscriptions

[Jérémie (jitsumi)]

I also have this bug.
I confirm that in3.19.0-16 I have the HDMI sound, and in 3.19.0-18, nothing.

[penalvch (penalvch)]

Jérémie, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Andrey Gadyukov (andrey-gadyukov)]

The same problem! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458196

[Jérémie (jitsumi)]

Here is my bug report with the information asked.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458478

[Trey Witteried (twitteried)]

Experiencing the same issue running 3.19.0-15-generic on my Zotac ZBOX-BI320-U-W2 that I use as a living room PC. Running 4.1.0-040100rc2-generic fixes it. Massive bug.