Bug 508921 - Switching resolution causes Xorg hang
Switching resolution causes Xorg hang
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-30 10:41 EDT by Peter van Hooft
Modified: 2010-06-28 09:23 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 09:23:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
warn_slowpath with (1.55 KB, text/plain)
2009-06-30 10:41 EDT, Peter van Hooft
no flags Details
lspci -vnn output (10.09 KB, text/plain)
2009-06-30 14:01 EDT, Peter van Hooft
no flags Details

  None (edit)
Description Peter van Hooft 2009-06-30 10:41:20 EDT
Created attachment 349958 [details]
warn_slowpath with

Description of problem:
Docked Dell Latitude D630 running x86_64.
When using kernel- and switching to a higher resolution (1680x1050) than the (wrongly detected) one, I get a warn_slowpath because of i915_gem_set_tiling. The system seems to work ok after that. 
When using kernel- and doing the same, I get the same warn_slowpath (see attachment), Xorg hangs for a few seconds, but continues after that. When I try to display a movie, however, Xorg hangs completely. After setting the `nomodeset' kernel commandline option everything works ok.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Boot
2. Switch to a higher resolution
3. Play a movie
Actual results:
X hangs.

Expected results:

Additional info:
No xorg.conf was used.
Comment 1 Chuck Ebbert 2009-06-30 13:39:28 EDT
Can you post the output of the command 'lspci -vnn'?
Comment 2 Peter van Hooft 2009-06-30 14:01:33 EDT
Created attachment 349985 [details]
lspci -vnn output
Comment 3 Bug Zapper 2010-04-27 11:22:28 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 4 Bug Zapper 2010-06-28 09:23:56 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

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

Note You need to log in before you can comment on or make changes to this bug.