I am using a Fujitsu T4215 Tablet PC
I use the intel free driver xorg-x11-drv-intel v 2.11.0
Description of problem:
xrandr -output LVDS1 -rotate right
xrandr -output LVDS1 -rotate normal
gives me a black screen.
if I then hit, ctrl-alt-f2, then ctrl-alt-f1, I get a non-black screen, which is frozen and takes a few minutes, but then unlocks.
Version-Release number of selected component (if applicable):
Has been happening consistently, and of course when I went to file this bug, it seems to be working.
Steps to Reproduce:
1. xrandr -output LVDS1 -rotate right
2. xrandr -output LVDS1 -rotate normal
Xorg log: http://fpaste.org/32Pt/
My hardware is a Fujitsu T4215 Tablet PC.
Ok this is still a problem, it is now always failing to rotate back to normal properly
xrandr --output LVDS1 --rotate right
xrandr --output LVDS1 --rotate normal
produces a black screen
pressing ctrl-alt-f2 then ctrl-alt-f1 gives me a non black screen.
Created attachment 436877 [details]
This is the entire xorg log, I tried rotating my tablet back and forth multiple times between tablet/laptop postion, this issue xrandr --rotate commands
Created attachment 436878 [details]
Xorg.0.log after issues xrandr --rotate left --output LVDS1 and xrandr --rotate right --output normal multiple times
I can only replicate the black screen when issuing a rotate from inside of the X display itself, as a test I issues
xrandr --rotate left --output LVDS1 -display :0 from a remote machine over SSH
xrandr --rotate normal --output LVDS1 -display :0
and everything works fine.
However doing things in the X session causes black screens
hitting ctrl alt f2 to switch to terminal mode, than ctrl alt f1 to switch back to the X session, returns me to the proper screen.
Created attachment 436879 [details]
Could you boot with drm.debug=15 and reproduce the issue?
Then attach the /var/log/dmesg from that attempt, as text/plain please.
Thanks in advance
Fedora Bugzappers volunteer triage team
Created attachment 436942 [details]
/var/log/dmesg after drm.debug=15
Is there any more information we can get out of this bug report?
I'm curious if the engineers have a place to go hunting for this bug.
I have an Intel chip I can try reproducing with and patching if I figure out where the issue may be at, is it in the i915.ko kernel driver, Xorg intel_drv.so driver or xrandr?
Jasper, _probably_ xorg-x11-server-Xorg or xorg-x11-drv-intel. The drm.debug trace doesn't contain much meaningful information AFAICT, so I'm hesitating to mark as triaged. I'll ask on IRC.
Fedora Bugzappers volunteer triage team
The problem has been upstreamed, still yet not solution, but it seems that the intel graphics developers are looking into it:
This seems to be similar as bug 655331, and bug 694006.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.