Created attachment 13895 [details] Xorg.0.log System Environment: -------------------------- Platform: gm965 Arch: 64bit Xf86_video_intel: xf86-video-intel-2.2-branch Xserver: xserver 1.4 Drm: libdrm 2.3.0 Mesa: mesa_7_0_3_rc1 branch Kernel: 2.6.23.1 Bug detailed description: -------------------------- startx ,run torcs, it run abort and print : "Visual Properties Report ------------------------ Compatibility mode, properties unknown. Failed to initialize TTM buffer manager. Falling back to classic. /usr/local/bin/torcs: line 52: 6097 Segmentation fault $LIBDIR/torcs-bin -l $LOCAL_CONF -L $LIBDIR -D $DATADIR $* " and it can run normally on 915gm (32bit) and the some mesa version . Reproduce steps: ---------------- startx , run torcs
> Mesa: mesa_7_0_3_rc1 branch [...] > Failed to initialize TTM buffer manager. Falling back to classic. The i965 driver on mesa_7_0_branch doesn't have any TTM support. Please clarify.
(In reply to comment #1) > > Mesa: mesa_7_0_3_rc1 branch > > [...] > > > Failed to initialize TTM buffer manager. Falling back to classic. > > The i965 driver on mesa_7_0_branch doesn't have any TTM support. Please > clarify. > yes, I think there's something wrong in his environment. Lerui, please recover your mesa7.0.3 rc1 environment and try again. Thanks
Created attachment 13925 [details] Xorg.0.log I retest it on mesa 7.0.3 ,and it is the new log .
I'm confused -- the current information is a Xorg log that appears to be from an X instance that's running just fine. The original report had a segfault in the client, though the wrong mesa version was being used. Assuming that X is not actually crashing, could we get updated log of the client being run and a bactrace of it?
Created attachment 14628 [details] Xorg.0.log I retest this case .and this is the new log & backtrace .
Created attachment 14629 [details] backtrace
this bug can't be produced on 7_0_branch
so marking it as fixed.
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.