| Summary: | [GLK] HDMI hotplug between 4K@60 and 4K@30 monitors *ERROR* Failed to read TMDS config: -6 & *ERROR* Set TMDS ratio failed | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Antony Chen <antonychen> | ||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Severity: | normal | ||||||||
| Priority: | high | CC: | intel-gfx-bugs, jingwu.lin, ville.syrjala | ||||||
| Version: | DRI git | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=105644 | ||||||||
| Whiteboard: | ReadyForDev | ||||||||
| i915 platform: | GLK | i915 features: | display/HDMI | ||||||
| Attachments: |
|
||||||||
|
Description
Antony Chen
2018-03-21 10:41:41 UTC
AMI BIOS version: 5.13_VEB_1AUAJ018 Hi, could you attach full dmesg with drm.debug=0xe parameter on grub, from boot and with the error messages captured? Thank you. Created attachment 138280 [details]
dmesg with drm.debug=0xe
Unplug HDMI cable (ViewSonic VP2780-4K (A)) on the 105 second. Plug HDMI cable (ASUS PB287Q (B)) on the 128 second. Looks same as in bugs.freedesktop.org/show_bug.cgi?id=105644 First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug. It still shows the same error messages after patching from comment 5. And there is still no signal to the 4K@30 monitor after the steps. The last drm I used is: drm-intel-next-2018-02-21, with Kernel 4.14.14 HI, fix was merged to drm-tip: https://cgit.freedesktop.org/drm-tip/commit/?id=277ab5abc68df2f6f8fac7a46e50105b6648f432 Please try that out. After this not seen on CI. See: https://bugs.freedesktop.org/show_bug.cgi?id=105644 *** This bug has been marked as a duplicate of bug 105644 *** Closing, please re-open if seeing issues still. I use the last drm-tip today, there is still no signal on monitor B: Monitor A support 4K@60 Monitor B support 4K@30 My steps: 1. Plug A and bootup 2. After OS finishes booting, unplug HDMI cable in console mode 3. Plug B => There is no signal on monitor B. Created attachment 138947 [details]
dmesg when unplug and plug HDMI cable
Unplug HDMI cable on the 74 second, and plug it on the 91 second.
And you added logs from those plug-ins / out's with full dmesg with drm.debug=0xe? Ville, any advice here? Fixed with commit 7c7163c4f94198c595e640669954c8a1a292c506 Author: Ville Syrjälä <ville.syrjala@linux.intel.com> Date: Tue Apr 24 16:02:50 2018 +0300 drm/edid: Reset more of the display info Reporter, please verify. Thanks, closing. its looks like is not fully fixed, when you trying inject EDID same error appear here full log on drm-tip from yesterday http://ix.io/19FZ (In reply to Piotr Kasp. from comment #18) > its looks like is not fully fixed, when you trying inject EDID same error > appear If you inject a HDMI 2.0 EDID on a 1.x display you will get this. Totally expected. that HDMI 2.0 and cable HDMI 2.0 and NUC gemmini lake with HDMI 2.0 TV Samsung QLED 4k HDR, Q7 (In reply to Piotr Kasp. from comment #20) > that HDMI 2.0 and cable HDMI 2.0 and NUC gemmini lake with HDMI 2.0 > > TV Samsung QLED 4k HDR, Q7 Hmm. Looks like a broken display and/or flaky connection then. on kaby lake works fine, and if I'm not trying inject EDID also I didn't getting this issue. so are we sure ? here log with same setup TV, cables, kernel version - just not incjecting EDID http://ix.io/19FW (there is other issue already raported but like you see issue *ERROR* Failed to read TMDS is not appear) (In reply to Piotr Kasp. from comment #23) > here log with same setup TV, cables, kernel version - just not incjecting > EDID > http://ix.io/19FW Attach the logs pls. > > (there is other issue already raported but like you see issue *ERROR* Failed > to read TMDS is not appear) KBL doesn't support HDMI 2.0 natively, so it won't be taking this codepath. |
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.