Platform ：CML laptop with codec ALC3204 Reproduce Steps: 1.Do system reboot 2.Plug in HDMI and check HDMI status via commad "amixer cget numid=37" 3.Plug out HDMI very slowly and check HDMI status via amixer cget numid=37 Frequency:100% Expected result: Sound setting update HDMI status (HDMI option disappeared) after step3 Actual result: HDMI option still in Sound setting, and amixer cget numid=37 still shows value=on Similar status as but patch at https://bugs.freedesktop.org/show_bug.cgi?id=107125 doesn't resolve the issue. Bug reproduced rate almost reach 100% if we plug out HDMI very slowly. With HDA legacy driver, same symptom still exist. Need to fix in graphics driver.
Created attachment 144435 [details] amixer log after step23
Created attachment 144436 [details] HDMI_dmesg
Created attachment 144437 [details] HDMI_logger
Clint, any comments on this bug?
(In reply to Yvonne from comment #0) > Platform ：CML laptop with codec ALC3204 > > Reproduce Steps: > > 1.Do system reboot > 2.Plug in HDMI and check HDMI status via commad "amixer cget numid=37" > 3.Plug out HDMI very slowly and check HDMI status via amixer cget numid=37 > > Frequency:100% > > Expected result: > Sound setting update HDMI status (HDMI option disappeared) after step3 > > Actual result: > HDMI option still in Sound setting, and amixer cget numid=37 still shows > value=on > > Similar status as but patch at > https://bugs.freedesktop.org/show_bug.cgi?id=107125 doesn't resolve the > issue. Bug reproduced rate almost reach 100% if we plug out HDMI very slowly. > > With HDA legacy driver, same symptom still exist. > > Need to fix in graphics driver. @James, any suggestions here?
There was a recent email thread about this, here's Jani Nikula's response: "We get a hotplug interrupt before the plug is completely out, while ddc communication still works with the display, and we conclude we are still connected. Moreover, the live status bits on the hotplug state have been notoriously unreliable in the past, we've tried using them like three times in the past, leading to regressions and reverts every time. You can come up with all sorts of pathological slow plug/unplug/wiggle cases. If you have a concrete requirement how slow needs to be okay, or better yet write a test case for igt and chamelium, we can work with that. We've proposed fixes in the past but they stalled because some undisclosed unquantified test case still failed."
(In reply to Yvonne from comment #2) > Created attachment 144436 [details] > HDMI_dmesg Can you please attach the dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M? Just in case, it might be helpful. Also, as a user what is the impact of this issue?
Catched the log you need. Please see the attachment HDMI_drc_dmesg.log with kernel parameters drm.debug=0x1e log_buf_len=4M. As a user the impacts are as belows: 1. For audio. When issue occurred, system will always show HDMI option in sound setting and cannot auto switch to other output source if highlight HDMI before. 2. For display. When issue occurred,screen which split before cannot back to normal.
Created attachment 144490 [details] HDMI_drm_dmesg.log
(In reply to Yvonne from comment #8) > Catched the log you need. Please see the attachment HDMI_drc_dmesg.log with > kernel parameters drm.debug=0x1e log_buf_len=4M. > > As a user the impacts are as belows: > 1. For audio. When issue occurred, system will always show HDMI option in > sound setting and cannot auto switch to other output source if highlight > HDMI before. > 2. For display. When issue occurred,screen which split before cannot back to > normal. Thanks for the explaining the impact. But, the dmesg is from the boot, can you attach from 0 seconds, currently its from 196 seconds.
Created attachment 144497 [details] Update the HDMI_drm_dmesg from 0s
*** This bug has been marked as a duplicate of bug 107125 ***
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.