Bug 51652 - [6550D SUMO] problems with secondar monitor on VGA, causing GPU lockups
Summary: [6550D SUMO] problems with secondar monitor on VGA, causing GPU lockups
Status: RESOLVED DUPLICATE of bug 42490
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL: http://212.158.157.7/bugreport.html
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-02 06:00 UTC by David Heidelberg (okias)
Modified: 2012-09-30 15:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg_VGAonBootConnected.txt (35.45 KB, application/octet-stream)
2012-07-02 06:00 UTC, David Heidelberg (okias)
no flags Details
picture.jpg (1.15 MB, image/jpeg)
2012-09-11 13:45 UTC, David Heidelberg (okias)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Heidelberg (okias) 2012-07-02 06:00:11 UTC
Created attachment 63701 [details]
dmesg_VGAonBootConnected.txt

1) when is computer booted with VGA connected, ends with repeatly restarting GPU

2) when is monitor connected on-fly in running Xorg, it seems fine (except small artifacts, i guess EXA, on screen mostly on top of DVI and bottom VGA trigerred by switching KDE virtual desktops). No errors in dmesg

3) when is DPMS activated and monitors suspends, back to online is returned only DVI

4) randomly I found:
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

5) out-topic, exist even only on DVI: when is enabled OGL KWIN and OpenGL video render, color of rendered context goes to white (every frame is whitier, until it's #ffffff)

No HDMI or DP conneted to system.

DVI-D: LG IPS235 1920x1080
VGA: ASUS VW224 1680x1050
Gentoo ~amd64
Kernel,libdrm,mesa,ddx: git, KMS

I'm able to test patches against anything.
Comment 1 David Heidelberg (okias) 2012-07-14 09:36:38 UTC
1a) I tested switched (so Asus on DVI and LG on VGA - switched) and it booted

1b) secondary I tested only Asus on DVI and it had same problem...
only in this line numbers (13 => 12 etc.) is little bit changing:
radeon 0000:00:01.0: GPU lockup (waiting for 0x0000000000000016 last fence id 0x0000000000000013)

1c) tested only LG on VGA and it failed. (same errors)

2) of fly was tested: VGA only, DVI only, both vga+dvi, both dvi+vga, seems ok
sometimes it start rebooting, but it takes a some time.
Comment 2 David Heidelberg (okias) 2012-09-06 10:00:32 UTC
Still valid with kernel 3.6.0-rc4
Comment 3 David Heidelberg (okias) 2012-09-11 13:45:48 UTC
Created attachment 66971 [details]
picture.jpg

after upgrade from 3.6.0_rc2 to rc4 second monitor works with clone (absolute 0 0 both), but extending desktop cause this (absolute 1920 0 and 0 0)
Comment 4 David Heidelberg (okias) 2012-09-14 13:26:32 UTC
to picture - I tested rc2 and I accidantally discovered, that it's because OpenGL Kwin, after deactivating affects it's ok. So some git mesa update...
Comment 5 David Heidelberg (okias) 2012-09-30 13:03:34 UTC
more can be founded here:

http://212.158.157.7/bugreport.html
Comment 6 diego.abelenda 2012-09-30 15:43:33 UTC
Although I didn't have display garbled that much (but I am not using an opengl-based DE).
Comment 7 diego.abelenda 2012-09-30 15:45:13 UTC
Sorry I wanted to make it duplicate of #42490
Comment 8 diego.abelenda 2012-09-30 15:46:46 UTC

*** This bug has been marked as a duplicate of bug 42490 ***


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.