Bug 23783 - Xorg crashes randomly with compositing enabled
Summary: Xorg crashes randomly with compositing enabled
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/r300 (show other bugs)
Version: 7.5
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-07 13:08 UTC by Daniel Klaffenbach
Modified: 2014-07-07 16:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg configuration file, also tried turning backingstore off (446 bytes, text/plain)
2009-09-07 13:08 UTC, Daniel Klaffenbach
Details
Xorg log file (43.73 KB, text/plain)
2009-09-07 13:09 UTC, Daniel Klaffenbach
Details
Compressed kdm.log with RADEON_DEBUG=all (23.23 KB, application/x-bzip)
2009-09-07 14:45 UTC, Daniel Klaffenbach
Details

Description Daniel Klaffenbach 2009-09-07 13:08:25 UTC
Created attachment 29320 [details]
Xorg configuration file, also tried turning backingstore off

With compositing enabled the XServer crashes frequently and randomly on my machine. Especially desktop effects (from KDE 4.3 or compiz-fusion) cause the crash.

My setup:
- HP nx6125, 1.2 GB Ram
- Radeon XPress 200M
- Linux 2.6.30.1 (in-kernel radeon DRM module)
- XServer 1.5.3, libdrm 2.4.12, mesa 7.5, xf86-video-ati 6.12.2

Backtrace:
(gdb) cont
Continuing.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7b4c8d0 (LWP 1849)]
0xb8050424 in __kernel_vsyscall ()
(gdb) bt
#0  0xb8050424 in __kernel_vsyscall ()
#1  0xb7b78660 in raise () from /lib/libc.so.6
#2  0xb7b79ea8 in abort () from /lib/libc.so.6
#3  0xb7b7164e in __assert_fail () from /lib/libc.so.6
#4  0xb15f381b in _mesa_reference_texobj () from /usr/lib/dri/r300_dri.so
(gdb)

Please tell me if there is any information I can contribute to help you solve this problem.
Comment 1 Daniel Klaffenbach 2009-09-07 13:09:18 UTC
Created attachment 29321 [details]
Xorg log file
Comment 2 Pauli 2009-09-07 13:38:27 UTC
Debug symbols would help in backtrace.

I don't know why this backtrace is cut but it would help if you could get backtrace to show what is calling the _mesa_reference_texobj.

If there is no easy way to get ful lbacktrace then running X with RADEON_DEBUG=all environment variable set might give useful info what is going wrong. But this will produce large log file which you might have to compress because of limit in attachment sizes. This output goes to [gk]dm log file or to console (if using startx).
Comment 3 Daniel Klaffenbach 2009-09-07 14:45:32 UTC
I don't know, but for some reasons the only information I can get out of the backtrace is this "_mesa_reference_texobj () from /usr/lib/dri/r300_dri.so" thing.

I did also upgrade to XServer 1.6.3.901 and 7.5.1, but the problem still persists. I have attached my compressed kdm.log with RADEON_DEBUG=all.
Comment 4 Daniel Klaffenbach 2009-09-07 14:45:59 UTC
Created attachment 29323 [details]
Compressed kdm.log with RADEON_DEBUG=all
Comment 5 Andreas Boll 2014-07-07 16:43:34 UTC
The classic r300 driver has been abandoned long ago.
It was replaced by the Gallium driver r300g.

If you have issues with r300g please file a new bug report with component Drivers/Gallium/r300

Thanks.


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.