FS#31311 - [xf86-video-intel] 2.20.5-1 crashes with SNA acceleration
Attached to Project:
Arch Linux
Opened by Thomas Bächler (brain0) - Tuesday, 28 August 2012, 08:31 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 05 September 2012, 08:03 GMT
Opened by Thomas Bächler (brain0) - Tuesday, 28 August 2012, 08:31 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 05 September 2012, 08:03 GMT
|
Details
On my first generation intel HD graphics (Arrandale CPU,
Ironlake GPU), 2.20.5-1 crashes after a few minutes of usage
when SNA acceleration is enabled. I just switched back to
UXA to see if the crash still occurs there, which didn't
happen yet.
|
This task depends upon
Closed by Thomas Bächler (brain0)
Wednesday, 05 September 2012, 08:03 GMT
Reason for closing: Fixed
Additional comments about closing: 2.20.6
Wednesday, 05 September 2012, 08:03 GMT
Reason for closing: Fixed
Additional comments about closing: 2.20.6
---------------------------
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x36) [0x560366]
1: /usr/bin/X (0x400000+0x1640c9) [0x5640c9]
2: /lib/libpthread.so.0 (0x7f8794f2e000+0xf170) [0x7f8794f3d170]
3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f8791f0d000+0x5ec6e) [0x7f8791f6bc6e]
4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f8791f0d000+0xb8e2a) [0x7f8791fc5e2a]
5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f8791f0d000+0x615fe) [0x7f8791f6e5fe]
6: /usr/bin/X (0x400000+0xf2119) [0x4f2119]
7: /usr/bin/X (0x400000+0xeb084) [0x4eb084]
8: /usr/bin/X (0x400000+0x34531) [0x434531]
9: /usr/bin/X (0x400000+0x23615) [0x423615]
10: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7f8793ddd725]
11: /usr/bin/X (0x400000+0x238ed) [0x4238ed]
Segmentation fault at address 0x7a
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
---------------------------
Turning of SNA acceleration (switching to UXA) eliminates the problem.
P.S.
Just updated to 3.5.3-1 ..... might solve the problem. I'll report if there're some changes.
BR
Log output:
---------------------------
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x36) [0x560366]
1: /usr/bin/X (0x400000+0x1640c9) [0x5640c9]
2: /lib/libpthread.so.0 (0x7f0a48637000+0xf170) [0x7f0a48646170]
3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0a45616000+0x5ec6e) [0x7f0a45674c6e]
4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0a45616000+0xb8e2a) [0x7f0a456cee2a]
5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f0a45616000+0x615fe) [0x7f0a456775fe]
6: /usr/bin/X (0x400000+0xf2119) [0x4f2119]
7: /usr/bin/X (0x400000+0xeb084) [0x4eb084]
8: /usr/bin/X (0x400000+0x34531) [0x434531]
9: /usr/bin/X (0x400000+0x23615) [0x423615]
10: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7f0a474e6725]
11: /usr/bin/X (0x400000+0x238ed) [0x4238ed]
Segmentation fault at address 0x7a
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Server terminated with error (1). Closing log file.
---------------------------
System info:
-- DE
KDE4.9 x86_64
Desktop Effects:
Compositing type = OpenGL
Qt graphics system = Native
-- Hardware
Lenovo ThinkPad Edge E320
Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz
Core-i7 2630QM, SNA, with enabled RC6 'i915.i915_enable_rc6=1', backtrace same like in 1-st post.
I've observed, that with intel-2.20.5 firefox crashes 100% times on this page: http://www.archlinux.org/visualize/
so it could be used for testing.
@erdk: Do you have RC6 mode manually turned on? I'm not sure, but the RC6 mode is turned on by default.
I'm turning off SNA as temporary solution.
1. open chromium
2. click on a download link (save-as-dialog appears)
3. click on save
*CHRASH*
i915.i915_enable_rc6=1 was set via kernel command line and rc6 is enabled in UEFI.
I didn't test without these settings.
Reverted to 2.20.4 -> no problems.
Downgrading to 2.20.4 workes.
Today I teststed the current git version of xf86-video-intel and it seems like this bug has been fixed.
I couldn't reproduce the crash anymore.
Please open a NEW bug report for a NEW issue, instead of confusing old and new bugs.