[Intel-gfx] Sandy Bridge X crash - OpenGL/DPMS-related?

[Ivan Bulatovic]

On Saturday, March 26, 2011 02:34:15 PM Ian Pilcher wrote:
> 
> When I entered my password, X crashed.  The backtrace in the log is:
> 
> Backtrace:
> [ 49562.907] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x4a117f]
> [ 49562.907] 1: /usr/bin/X (0x400000+0x621c6) [0x4621c6]
> [ 49562.907] 2: /lib64/libpthread.so.0 (0x37ae800000+0xf4e0) [0x37ae80f4e0]
> [ 49562.907] 3: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x84251)
> [0x7fd70c43d251]
> [ 49562.907] 4: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x6e116)
> [0x7fd70c427116]
> [ 49562.907] 5: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x5d5cd)
> [0x7fd70c4165cd]
> [ 49562.907] 6: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x148b93)
> [0x7fd70c501b93]
> [ 49562.907] 7: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x14690c)
> [0x7fd70c4ff90c]
> [ 49562.907] 8: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x146b0a)
> [0x7fd70c4ffb0a]
> [ 49562.907] 9: /usr/lib64/dri/i965_dri.so (0x7fd70c3b9000+0x1090cb)
> [0x7fd70c4c20cb]
> [ 49562.907] 10: /usr/lib64/xorg/modules/extensions/libglx.so
> (0x7fd70d839000+0x310b9) [0x7fd70d86a0b9]
> [ 49562.907] 11: /usr/lib64/xorg/modules/extensions/libglx.so
> (0x7fd70d839000+0x33831) [0x7fd70d86c831]
> [ 49562.907] 12: /usr/bin/X (0x400000+0x2ebd1) [0x42ebd1]
> [ 49562.907] 13: /usr/bin/X (0x400000+0x22e5a) [0x422e5a]
> [ 49562.907] 14: /lib64/libc.so.6 (__libc_start_main+0xed) [0x37adc2131d]
> [ 49562.907] 15: /usr/bin/X (0x400000+0x23141) [0x423141]
> [ 49562.907] Segmentation fault at address (nil)
> [ 49562.907]
> Fatal server error:
> [ 49562.907] Caught signal 11 (Segmentation fault). Server aborting
> 
> Any ideas?
> 
> Thanks!

I had the same problem, as I recall backtrace was similar to this one 
(i965_dri.so) with mesa 7.10 on ArchLinux. Although the trigger to this bug 
was somewhat different, exiting UrbanTerror was killing X server. Haven't had 
that problem after upgrading to mesa 7.10.1

I've installed Fedora 15 on a different machine yesterday and I saw that mesa 
7.10.1 was in update list. If you can confirm that mesa 7.10.1 fixes the bug 
or not would be great.