Bug 51975

Is this a regression?

(In reply to comment #1)
> Is this a regression?
It's the first time for us to test audio with HDMI,I try one kernel half a year before, with that kernel if still can't catch the HDMI audio device.

Is the HDMI audio on that monitor detected on any other platform? Would be useful to have its dmesg to compare.

Created attachment 64130 [details]
huronriver booting with HDMI dmesg info

(In reply to comment #3)
> Is the HDMI audio on that monitor detected on any other platform? Would be
> useful to have its dmesg to compare.
I try with Huronriver platform,while running command "aplay -l",it can detect the HDMI audio like this,and I attach the dmesg after booting with HDMI monitor.

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC272 Analog [ALC272 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Is this still an issue on latest -fixes/-queued?

(In reply to comment #5)
> Is this still an issue on latest -fixes/-queued?
Yes, the latest -fixes/-queued branch all have this issue.

This issue also exist with
Kernel: (drm-intel-testing)6760818aad5622d7f20d7f1c45d75a8165aeaf24
I tested.

A couple of months and a new kernel since the last test report.

(In reply to comment #8)
> A couple of months and a new kernel since the last test report.
I try with the latest -nightly:
Kernel: (drm-intel-nightly)539526b4137bc0e7a8806c38c8522f226814a0e6
the issue still occurs.

539526b4137bc0e7a8806c38c8522f226814a0e6 doesn't include the merge with 3.7, so there is still a slim chance that this was fixed upstream. Or do we believe something is missing in our IVB ELD?

(In reply to comment #10)
> 539526b4137bc0e7a8806c38c8522f226814a0e6 doesn't include the merge with 3.7,
> so there is still a slim chance that this was fixed upstream. Or do we
> believe something is missing in our IVB ELD?
   I try with the newest -fixes,the bug still occurs, Chris, does -fixes branch is the upstream branch you mentioned？

(In reply to comment #10)
> 539526b4137bc0e7a8806c38c8522f226814a0e6 doesn't include the merge with 3.7,
> so there is still a slim chance that this was fixed upstream. Or do we
> believe something is missing in our IVB ELD?

(In reply to comment #11)
> (In reply to comment #10)
> > 539526b4137bc0e7a8806c38c8522f226814a0e6 doesn't include the merge with 3.7,
> > so there is still a slim chance that this was fixed upstream. Or do we
> > believe something is missing in our IVB ELD?
>    I try with the newest -fixes,the bug still occurs, Chris, does -fixes
> branch is the upstream branch you mentioned？

I have test with newest -nightly, the issue still occurs,the kernel is: 
Kernel: (drm-intel-nightly)70880564238362d96181fb54d0edf1a5bf5b24cc

A few more months, a new kernel... Time for another round of testing - at some point I guess we are just going to have to declare this as notourbug.

(In reply to comment #13)
> A few more months, a new kernel... Time for another round of testing - at
> some point I guess we are just going to have to declare this as notourbug.

I have tried latest drm-intel-tesing kernel, and  it also can't find HDMI audio device. If you really think it need to be marked NOTOURBUG, please let me knows.
---------------------------------
kernel: d08a6eb2690b1ac6f0582feb41c2ccbea945285f
Merge: 35aad75 f40ebd6
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Thu Mar 7 22:54:25 2013 +0100

(In reply to comment #13)
> A few more months, a new kernel... Time for another round of testing - at
> some point I guess we are just going to have to declare this as notourbug.

I have tested another IVB platform, and it can detect HDMI audio device:
-----------------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

lspci:
00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Ivy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09)
00:14.0 USB Controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 2 (rev c4)
00:1c.2 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 3 (rev c4)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 04)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation Device 1058 (rev a1)

(In reply to comment #14)
> (In reply to comment #13)
> > A few more months, a new kernel... Time for another round of testing - at
> > some point I guess we are just going to have to declare this as notourbug.
> 
> I have tried latest drm-intel-tesing kernel, and  it also can't find HDMI
> audio device. If you really think it need to be marked NOTOURBUG, please let
> me knows.
> ---------------------------------
> kernel: d08a6eb2690b1ac6f0582feb41c2ccbea945285f
> Merge: 35aad75 f40ebd6
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Thu Mar 7 22:54:25 2013 +0100

00:00.0 Host bridge: Intel Corporation Ivy Bridge DRAM Controller (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Device 0162 (rev 04)
00:14.0 USB Controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 02)
00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 02)
00:16.3 Serial controller: Intel Corporation Panther Point KT Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c2)
00:1c.6 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 7 (rev c2)
00:1c.7 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 8 (rev c2)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a2)
00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 02)
03:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200A PCI Express-to-PCI Bridge (rev 03)
04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2200A IEEE-1394a-2000 Controller (PHY/Link) (rev 01)

Yangwei, can you still reproduce the issue with latest kernel?

(In reply to comment #17)
> Yangwei, can you still reproduce the issue with latest kernel?

I have retested on two different IVB platform with latest drm-intel-fixes kernel, and the result is the same. The IVB desktop also have this issue.

kernel info:
---------------------
Kernel: (drm-intel-fixes)c12aba5aa0e60b7947bc8b6ea25ef55c4acf81a4
Some additional commit info:
Author: Jiri Kosina <jkosina@suse.cz>
Date:   Tue Mar 19 09:56:57 2013 +0100

    drm/i915: stop using GMBUS IRQs on Gen4 chips


one IVB desktop (x-ivb4):
-----------------
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC889 Analog [ALC889 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC889 Digital [ALC889 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

one IVB laptop (x-ivb18):
-----------------
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Another 3 months, time for a new test. ;)

(In reply to comment #19)
> Another 3 months, time for a new test. ;)

I tried with latest -next-queued kernel, one IVB desktop machine also can't find 
HDMI audio device, then I covered another IVB laptop, we can see the HDMI info been listed clearly.



IVB desktop:(Maho Bay () : Host bridge id=0x0150 (rev 04), 4C/8T, CPU @2.2GHz, GT2 1800MHz, AMT support, no VT-d )
---------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC889 Analog [ALC889 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC889 Digital [ALC889 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0


IVB mobile:(i5-3550 product( i5-3317U (id=0x0166, rev 09), Host bridge id=0x0154 (rev 09), 4C/8T, CPU @1.70GHz, GT2, no VT-d, no AMT )
---------------------------
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Paulo, mind taking a look and make sure we have enough debug messages to be sure that everything is working as expected on our side?

(In reply to comment #21)
> Paulo, mind taking a look and make sure we have enough debug messages to be
> sure that everything is working as expected on our side?

Paulo, ping.

Guang, ping, does it work with current drm-intel-nightly?

(In reply to comment #21)
> Paulo, mind taking a look and make sure we have enough debug messages to be
> sure that everything is working as expected on our side?

We should get someone from the Audio team to debug this. I can't really say for sure.

(In reply to comment #22)
> (In reply to comment #21)
> > Paulo, mind taking a look and make sure we have enough debug messages to be
> > sure that everything is working as expected on our side?
> 
> Paulo, ping.
> 
> Guang, ping, does it work with current drm-intel-nightly?

I tried with latest -nightly kernel(commit b7214fceac0659d440adfa5f1acec238fb7217fc) on both IVB desktop and IVB laptop
the HDMI info can be listed clearly on the both machine.

IVB desktop(x-ivb6):
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

IVB laptop(x-ivb17):
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

It seems that it's working now, right? wasn't our bug I guess then. Closing.

Closing old verified.