Red Hat Bugzilla – Bug 491500
assertion failure in intel Xorg driver, console locked
Last modified: 2009-04-20 16:57:11 EDT
Created attachment 336187 [details]
Photo of the error screen
Description of problem:
An attempt to use second X server (via the "Switch user" Gnome or KDE
menu or otherwise) locks console on my system. Usually I can revive
the keyboard by ssh-ing into the machine and issuing "chvt <N>". This
is what I did to demonstrate the problem in a simple setup:
Boot into runlevel 3.
Login (non-root) onto tty2 and tty3
[tty2] $ xinit /usr/bin/xterm -- /usr/bin/X :2
Works as expected. Switch to tty3.
[tty3] $ xiint /usr/bin/xterm -- /usr/bin/X :3
OK, got an xterm on :3
An attempt to switch to the server on :2 gives black screen.
Can't switch to any tty via keyboard now. Connected
to the system via ssh, did "chvt 1" as root. The console is
back to life. On tty3, there is the following error message:
X: intel_bufmgr_fake.c:1372: intel_bufmgr_fake_evict_all: Assertion
`((&bufmgr_fake->fenced)->next == (&bufmgr_fake->fenced))' failed.
xterm: fatal IO error 11 .... on X server ":3.0"
xinit: connection to X server lost.
I am attaching a photo of the error screen, log files of the two X
servers, and output of "lspci -vvv". The machine is a Lenovo x200s
laptop with Intel GMA 4500MHD. Fedora 10 with current updates,
Version-Release number of selected component (if applicable):
How reproducible: always
Steps to Reproduce: start 2 X servers
Actual results: server crash, console locked
Expected results: both X servers working
Created attachment 336188 [details]
Log file of the surviving X server (the one that was started first)
Created attachment 336189 [details]
Log file of the crashed X server
Created attachment 336190 [details]
This problem is fixed in
I could start up, and switch between, two X servers.
Closing this bug.