Bug 64657 - [HSW] I-G-T/testdisplay, ALSA hda_eld.c:334 HDMI: ELD buf size is 0, force 128
Summary: [HSW] I-G-T/testdisplay, ALSA hda_eld.c:334 HDMI: ELD buf size is 0, force 128
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-16 01:28 UTC by shui yangwei
Modified: 2017-10-06 14:46 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg: DRM_INFO after running testdisplay (74.18 KB, text/plain)
2013-05-16 01:28 UTC, shui yangwei 		no flags Details
View All

Description shui yangwei 2013-05-16 01:28:01 UTC 
Created attachment 79371 [details]
dmesg: DRM_INFO after running testdisplay

Environment:
------------------------------
Kernel: (drm-intel-next-queued)f2799ab0a317ecde76161df5d3102aa6e0e2c9e4
Some additional commit info:
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Tue May 7 15:10:29 2013 +0300

    drm/i915: fix hotplug event bit tracking

Description:
------------------------------
I retest with the latest -next-queued kernel, it's much more better, there's only a little DRM_INFO messages after running testdisplay like below:

<6>[  182.607082] ALSA sound/pci/hda/hda_eld.c:334 HDMI: ELD buf size is 0, force 128
<6>[  182.607127] ALSA sound/pci/hda/hda_eld.c:351 HDMI: invalid ELD data byte 0
<6>[  182.607188] ALSA sound/pci/hda/hda_eld.c:334 HDMI: ELD buf size is 0, force 128
<6>[  182.607228] ALSA sound/pci/hda/hda_eld.c:351 HDMI: invalid ELD data byte 0

Reproduce step:
------------------------------
1. booting up machine
2. dmesg -c
3. ./testdisplay -a
4. dmesg -r | less
Comment 1 Paulo Zanoni 2013-05-16 13:55:44 UTC 
Shouldn't this bug report go to the Audio teams?
Comment 2 Daniel Vetter 2013-05-20 19:28:28 UTC 
Otoh the eld shouldn't be 0, so this could be something we botch up in our hdmi code.
Comment 3 Chris Wilson 2013-06-30 08:49:03 UTC 
Curious as to whether this magically disappeared by itself...
Comment 4 shui yangwei 2013-07-01 05:52:22 UTC 
(In reply to comment #3)
> Curious as to whether this magically disappeared by itself...

I tested with latest -next-queued kernel, and it just like what you said, the issue magically disappeared. And there's not other issue in dmesg. I think it's fixed.
Comment 5 Chris Wilson 2013-07-01 07:35:30 UTC 
Hopefully fixed, definitely notourbug at least!
Comment 6 Elizabeth 2017-10-06 14:46:23 UTC 
Closing old verified.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.