Red Hat Bugzilla – Bug 494411
X dies on VT switch
Last modified: 2013-01-10 00:09:01 EST
Description of problem:
I have a Thinkpad X200 with a 965:
00:02.1 0380: 8086:2a43 (rev 07)
X is somehow dying when I switch VTs (so that includes on suspend/resume). The logs are clean, so I'm not sure what information to provide here.
Version-Release number of selected component (if applicable):
Please attach your X server config file (/etc/X11/xorg.conf), X server log file (/var/log/Xorg.*.log) and the output of "dmesg" to the bug report as individual uncompressed text/plain file attachments.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
If your card is using KMS, please try the nomodeset kernel parameter at boot to see if it improves things, and include dmesg and /var/log/Xorg.0.log from this attempt as well.
We will review this issue again once you've had a chance to attach this information.
Thank you in advance.
Fedora Bugzappers volunteer triage team
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I'm been struggling with the same problems.
After spending a lot of time on the issue, I found out that:
a. Either you enable EXA in /etc/X11/xorg.conf (and disable UXA)
b. You have to upgrade to xorg-x11-drv-intel-188.8.131.521, which is not packaged yet. Plan b also requires a couple of kernel patches if you want to use AIGLX/compiz.
By the way, when dying, X logs the following message:
Xorg: i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion `pI830->batch_ptr != ((void *)0)' failed.
You can find that in /var/log/gdm/:0.log.
*** Bug 511887 has been marked as a duplicate of this bug. ***
*** Bug 509304 has been marked as a duplicate of this bug. ***
*** Bug 496648 has been marked as a duplicate of this bug. ***
Could anybody provide information required in the comment 1, please?
All the three bugs that are marked duplicate have xorg.0.log files.
This was my Xorg.0.log (without any xorg.conf)
No interesting output in the kernel log for me. Details in
(In reply to comment #9)
> All the three bugs that are marked duplicate have xorg.0.log files.
Sorry, true, of course:
Bug 496648 attachment 340349 [details]
Bug 509304 attachment 350245 [details] (/var/log/messages attachment 354197 [details])
Bug 511887 attachment 353830 [details]
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command
yum upgrade --enablerepo='*-updates-testing'
Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Issue persist after F11 update on my laptop.
Should I also test on F12 ?
(In reply to comment #13)
> Should I also test on F12 ?
It would be nice if you do, but you don't have to.
I can not reproduce the issue on F12 :)
Just for note, list of packages versions:
Thank you for letting us know.