Summary: | [SNB] two monitors each show half of screen with extend mode | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | cancan,feng <cancan.feng> | ||||||||||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||||
Status: | CLOSED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||||
Severity: | major | ||||||||||||||||||
Priority: | medium | ||||||||||||||||||
Version: | unspecified | ||||||||||||||||||
Hardware: | Other | ||||||||||||||||||
OS: | All | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||
Attachments: |
|
Description
cancan,feng
2013-07-30 03:03:53 UTC
Created attachment 83251 [details]
scrot picture
Created attachment 83252 [details]
DVI monitor picture
Created attachment 83253 [details]
DP monitor picture
Interesting, can you also please attach Xorg.0.log and xrandr output. Please tell me this a kernel regression... :) (In reply to comment #4) > Interesting, can you also please attach Xorg.0.log and xrandr output. Please > tell me this a kernel regression... :) I'm afraid it's not a regression, I can't find a good commit.. :( xrandr: Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 32767 x 32767 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 641mm x 401mm 1920x1200 60.0* 1600x1200 60.0 1280x1024 75.0 60.0 1280x800 59.9 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP2 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 580mm x 360mm 1920x1200 60.0*+ 1600x1200 60.0 1680x1050 60.0 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP3 disconnected (normal left inverted right x axis y axis) Created attachment 83344 [details]
Xorg.0.log
The last change in the Xorg.0.log is: [ 525.169] (II) intel(0): resizing framebuffer to 3840x1200 [ 525.169] (II) intel(0): switch to mode 1920x1200 on pipe 0 using HDMI3 [ 525.196] (II) intel(0): switch to mode 1920x1200 on pipe 1 using DP2 [ 525.212] (II) intel(0): switch to mode 1920x1200 on pipe 0 using HDMI3 but xrandr still believes that the current fb is 1920 x 1200 with the two outputs in clone mode. Prior to that modeset, the two outputs were indeed mirrored (with a 1920x1200 fb). Can you please confirm that the xrandr is from after 525s? dmesg also believes that the two pipes should be in an extended configuration. (In reply to comment #7) > The last change in the Xorg.0.log is: > > [ 525.169] (II) intel(0): resizing framebuffer to 3840x1200 > [ 525.169] (II) intel(0): switch to mode 1920x1200 on pipe 0 using HDMI3 > [ 525.196] (II) intel(0): switch to mode 1920x1200 on pipe 1 using DP2 > [ 525.212] (II) intel(0): switch to mode 1920x1200 on pipe 0 using HDMI3 > > but xrandr still believes that the current fb is 1920 x 1200 with the two > outputs in clone mode. Prior to that modeset, the two outputs were indeed > mirrored (with a 1920x1200 fb). Can you please confirm that the xrandr is > from after 525s? dmesg also believes that the two pipes should be in an > extended configuration. Hmm, here I attach a new dmesg and Xorg.0.log which after system boots I just start X and gnome, then do rotation. Maybe these info is a little more clear :) Created attachment 83346 [details]
system dmesg fae5cb
Created attachment 83347 [details]
just rotation
I don't think this is a kernel/Xorg bug. The modesetting sequences and hardware programming look valid, and that is confirmed by the scrot pricture. I think gnome-shell is misrendering. 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.