| Summary: | [HD 4000] triple monitor configuration - resolutions above 1024x768 hangs/locks kernel and/or xserver | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | nadrimajstor <ipejic> | ||||||||||
| 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: | major | ||||||||||||
| Priority: | medium | ||||||||||||
| Version: | unspecified | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
Infinite loops in DP link training should be fixed with commit 3b4f819d5eac94ba8fe5e8c061f6dabfe8d7b22c Author: Takashi Iwai <tiwai@suse.de> Date: Mon Mar 11 18:40:16 2013 +0100 Revert "drm/i915: try to train DP even harder" Which is only yet available in the drm-intel-fixes branch of http://cgit.freedesktop.org/~danvet/drm-intel but it's on the way to upstream and tagged for stable backporting. Can you please retest with that patch/revert? Created attachment 76833 [details]
dmesg
Created attachment 76834 [details]
Xorg.0.log
(In reply to comment #1) > Infinite loops in DP link training should be fixed with > > commit 3b4f819d5eac94ba8fe5e8c061f6dabfe8d7b22c > Author: Takashi Iwai <tiwai@suse.de> > Date: Mon Mar 11 18:40:16 2013 +0100 > > Revert "drm/i915: try to train DP even harder" > > Which is only yet available in the drm-intel-fixes branch of > > http://cgit.freedesktop.org/~danvet/drm-intel > > but it's on the way to upstream and tagged for stable backporting. Can you > please retest with that patch/revert? Retested. I can confirm - this patch/revert solved this issue. (tried on ubuntu 12.04.2 with kernel 3.5.0-26-generic #42~precise1) Thanks for the feedback. Just to double-check: Everything works fine again, screens all work as expected? (In reply to comment #5) > Thanks for the feedback. Just to double-check: Everything works fine again, > screens all work as expected? Actually there are some additional quirks. I've got inconstant results on: - changing VTs - hot-plugging monitors - waking up from power-saving - changing resolution Ranging from: - "no-signal" on one of the outputs - lines on left side of screen (see picture) - some outputs sometime have correct signal sometime they not. I'm thinking this must be related to the fact that chipset have only 2 PLLs (which I don't mind - I intend use two 1920x1080 HDMI TVs + monitor) I'll have to do a bit of research, go trough existing bug reports and eventually file another bug if needed. However, any help is much appropriated. Created attachment 77072 [details]
lines on the left side
|
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.
Created attachment 76831 [details] xrandr --verbose System environment: -- chipset: QM77 -- system architecture: i686 -- xf86-video-intel: 2.20.0 -- xserver: 1.11.3 -- mesa: 9.0.1 -- libdrm version: 2.4.32-1ubuntu1 -- kernel version: 3.5.0-26-generic -- Linux distribution: Ubuntu 12.04.2 -- Motherboard: kino-qm770-r10 -- Display connector: DVI, HDMI, HDMI Setting native monitor resolutions above 1024x768 for all three monitors always produce this continuously repeating error: ... [drm:intel_dp_start_link_train], training pattern 1 signal levels 00000000 [drm:intel_dp_start_link_train], training pattern 1 signal levels 02000000 [drm:intel_dp_start_link_train], training pattern 1 signal levels 04000000 ... Kernel 3.2.x hangs during boot. Kernel 3.5.x - 3.9 will boot fine by automatically setting resolution to 1024x768 However, no matter which combination of connectors I use issuing commands such as: xrandr --output VGA1 --auto --output DP2 --auto --output DP3 --auto or xrandr --output HDMI1 --auto --output DP2 --auto --output DP3 --auto will always trigger this error. Same monitor configuration works fine in Win7 so I assume that hardware is ok. :|