Created attachment 15116 [details] xorg.0.log When trying the latest git version of xf86-video-intel (2.3) driver I get a Fatal server error: Couldn't bind memory for BO front buffer. I am using Debian/Sid and kernel 2.6.24-1-686 on a laptop with 82852/855GM Integrated Graphics Device.
I'm getting something similar, but a bit different with the same combination of latest git (commit 402fbd36221d2ed27913850f6bfcce768b970fe8) (II) intel(0): [DRI] installation complete (EE) intel(0): Failed to mprotect ring buffer: Permission denied (EE) intel(0): Failed to mprotect compressed frame buffer: Permission denied (EE) intel(0): Failed to mprotect compressed ll buffer: Permission denied (EE) intel(0): Failed to mprotect HW cursors: Permission denied (EE) intel(0): Failed to mprotect overlay registers: Permission denied (EE) intel(0): Failed to mprotect DRI memory manager: Permission denied (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0bbf4000 (pgoffset 48116) (EE) intel(0): Failed to mprotect exa offscreen: Permission denied (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0d9f4000 (pgoffset 55796) (EE) intel(0): Failed to mprotect classic textures: Permission denied (EE) intel(0): Failed to mprotect depth buffer: Permission denied (EE) intel(0): Failed to mprotect back buffer: Permission denied (EE) intel(0): Failed to mprotect front buffer: Permission denied (EE) intel(0): Failed to mprotect logical 3D context: Permission denied (II) intel(0): Fixed memory allocation layout:
Created attachment 15117 [details] xorg log
this bug seems to be fixed at least on one machine for me. I'll check the other (the one where I've seen the bug, it has a slightly different kernel - 2.6.22 ubuntu instead of debian) at Monday.
actually, it's not fixed.. I was using old version DRI modules, so it worked, but when I put the git mesa DRI modules it happens again, with added twist that it sometimes hard locks instead showing this: http://mjesec.ffzg.hr/~vrodic/img_1751_small.jpg
It seems that now it happens only if XAA accel method is selected in xorg.conf
(In reply to comment #5) > It seems that now it happens only if XAA accel method is selected in xorg.conf XAA will be removed soon, so I'm afraid we won't have any new development on XAA side.
Vedran, pls don't mixed up your other problem here. Jos's xorg log shows no mprotect error you met, but relate to larget Virtual set to trigger front buffer BO binding error. Both of these issues are already having bug reports, so both are dup.
zhenyu, please specify the bug number you think this bug is a dup of...
Jos, pls attach your xorg.conf. BO error should be same to bug #12585. Vedran's mprotect problem I lost my mind which bug picked it, but it is there. Current guess is libpciaccess relate issue.
Created attachment 15221 [details] xorg.conf I don't use the Virtual fb option as mentioned in bug #12585!
(In reply to comment #7) > Vedran, pls don't mixed up your other problem here. > > Jos's xorg log shows no mprotect error you met, but relate to larget Virtual > set to trigger front buffer BO binding error. > > Both of these issues are already having bug reports, so both are dup. > You're right, this is a different bug probably. I'll file a separate bug report for the bug I'm seeing with the current git (a hard lockup when using XAA).
> > You're right, this is a different bug probably. I'll file a separate bug report > for the bug I'm seeing with the current git (a hard lockup when using XAA). > The bug I'm experiencing is already reported as bug #12922
reassigning to Eric, since this bug might be related to bug#12585.
After updating to the latest git, no more errors!
then I'm closing this one.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.