Bug 1350133

Summary: Very slow graphics on Intel 945GM (TV output wrongly enabled)
Product: [Fedora] Fedora Reporter: robho <robert>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: ajax, mnowak, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 15:03:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description robho 2016-06-25 22:27:37 UTC 
Description of problem:
Very slow graphics on Dell D620 laptop with Intel 945 graphics. GUI is not usable.

Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.99.917-23.20160512.fc24.x86_64

How reproducible:
100 % - on every boot

Steps to Reproduce:
1. Boot a standard installation of Fedora 24 Workstation on a Dell D620 laptop (no external displays attached to computer)
2. When gnome has started the graphics are very slow

Actual results:
Screen resolution is set to 2128x800 and graphics are very slow

Expected results:
Screen resolution should be 1200x800 and UI should be usable

Additional info:

xrandr reports the TV1 output "connected" and this seems to cause the resolution to go to 2128x800:

Screen 0: minimum 8 x 8, current 1280 x 800, maximum 32767 x 32767
LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 300mm x 190mm
   1280x800      59.91*+
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
   640x400       60.00  
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 unknown connection (normal left inverted right x axis y axis)
   848x480       59.94 +
   640x480       59.94 +
   1024x768      59.94  
   800x600       59.94  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Note that there's no TV output present on this laptop. There is TV output available on the docking station, but this problem happens even if the laptop isn't docked.

I can "fix" the problem by executing "xrandr --output TV1 --off". Starting the "gnome settings" also seems to fix this problem, but I don't know why.

This seems to have broken sometime between Fedora 23 and Fedora 24 releases. The initial Fedora 23 release worked, but in Fedora 23 the problem appeared a few months back(?). Fedora 24 had the problem in the initial release.
Comment 1 robho 2016-06-26 08:48:06 UTC 
By just running xrandr (without arguments) I can toggle this bug on/off.

Executing xrandr right after boot "fixes" the problem (resolution is 1280x800). Then, executing xrandr again causes it to trigger again (resolution goes to 2128x800). I need to wait ~30 seconds between each xrandr command for it to have any effect.

The screen resolutions I mention have been taken from the output from xdpyinfo.

When graphics is "fast" xrandr says:

Screen 0: minimum 8 x 8, current 2128 x 800, maximum 32767 x 32767
LVDS1 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 300mm x 190mm
   1280x800      59.91*+
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
   640x400       60.00  
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected 848x480+1280+0 (normal left inverted right x axis y axis) 0mm x 0mm
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  848x480 (0x96) 29.027MHz
        h: width   848 start  849 end  912 total  944 skew    0 clock  30.75KHz
        v: height  480 start  481 end  512 total  513           clock  59.94Hz


I'm running kernel-core-4.5.7-300.fc24.x86_64.
Comment 2 Michal Nowak 2016-07-02 15:13:35 UTC 
Facing the same issue. Filled bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=96783.
Comment 3 robho 2016-07-14 13:42:38 UTC 
With kernel 4.6.3-300.fc24.x86_64 I no longer have this problem.

Michal, does a more recent kernel fix the problem for you too?
Comment 4 robho 2016-07-14 14:07:52 UTC 
I spoke too soon. The problem is still there if the laptop is docked and an external monitor is used. I can still "fix" the problem by running "xrandr".
Comment 5 Fedora End Of Life 2017-07-25 21:18:31 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2017-08-08 15:03:15 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.