I'm forwarding this bug from a Ubuntu reporter.
If "Virtual X Y" is specified in xorg.conf, where X > 2048 (such as to permit dual-head layouts), and the user rotates the screen using 'xrandr', X crashes and hangs the machine.
PCI ID: Intel Mobile 945GM/GMS/GME, 943/940GML (chip 8086,27a2 card 17aa,201a)
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001getbl_err: 0x0
ipeir: 0 iphdr: 2000011
LP ring tail: 38 head: dc9c len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: 81 instpm: 0
memmode: 306 instps: 800f04c4
hwstam: ffff ier: 0 imr: ffff iir: 0
Ring at virtual 0xa78c5000 head 0xdc9c tail 0x38 count 18663
Presumably this is occurring because a screen that had been configured for DRI can no longer use it when the width goes over 2048? Rather than crashing, it would be preferable for it to either refuse to rotate, or to rotate but disable DRI and issue an error message about it, but not crash.
On Mon, Apr 14, 2008 at 18:28:42 -0700, firstname.lastname@example.org wrote:
> If "Virtual X Y" is specified in xorg.conf, where X > 2048 (such as to permit
> dual-head layouts), and the user rotates the screen using 'xrandr', X crashes
> and hangs the machine.
What version of the driver? 7bba2c13310ed5ac22a355a3cc0ec8b7afaa79cf
Created attachment 15979 [details] [review]
proposal fix for exa pitch checking
I have produced on 915G here, and it looks we got pitch that larger than hw can support (8k for i915). This is a kludge patch to always check pitch size in driver, as current exa pitch checks of pixmap not created by CreatePixmap is broken to ignore devKind.
A seperate xserver/exa patch is available to fix this issue, but there will be compat issue...
Please try with this patch first.
Created attachment 15981 [details] [review]
more clean one
Fixed in git.
Zhenyu, I can't find the attached patch in the git. Could you double check and provide the commit id?
*** Bug 16064 has been marked as a duplicate of this bug. ***
8187a5a16f8bd8f0ba5e7f5357f355928b3b8f07 in 2.3-branch.