This bug is a follow-up of a freedesktop bug https://bugs.freedesktop.org/show_bug.cgi?id=28896 Software: Fedora 13 i686 with all updates installed Intel driver 2.12 vanilla Kernel 2.6.34 vanilla Hardware: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) Steps to reproduce: Run vesa X.org server next to already running intel X.org server. Result: PC is unusable, both X servers die, all VTs die, dozens of errors in dmesg and in the first X.org server log.
You have two drivers conflicting over control of the same hardware. Don't do that.
X.org server trying to run using Vesa shouldn't crash my computer and it happens now. I could be happy if kernel just said "Resource or device is busy" without wrecking havoc. (As a side not I wonder why it's possible (and it perfectly works) to run proprietary NVIDIA X.org server and Vesa X.org server at the same time).
The kernel has no way of doing this right now. A suitably privileged X server can open /dev/mem or any of the sysfs resource files and start poking regsiters. The reason NV and VESA work together is that the NV driver isn't a kernel mode driver, when you switch between servers in that config the whole hardware state is saved and restored, whereas in the i915 case, the i915 driver expects to be in sole control of the hw once it loads.
Created attachment 27388 [details] Bug appearance
Created attachment 27389 [details] Bug appearance II