| Summary: | segfault in r300_dri.so | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Heinrich Fu Jin Wang <b824929> |
| Component: | Drivers/DRI/r300 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Xorg.0.log.old
dmesg output |
||
Created attachment 32438 [details]
Xorg.0.log.old
Created attachment 32439 [details]
dmesg output
Any chance you could get a real backtrace with gdb? I tried to receive a backtrace from gdb but obviously my computer skills are not sufficient. After reading a couple of howtos on debugging with gdb in the internet I installed xserver-xorg-core-dbg, recompiled drm, ddx and mesa with CFLAGS="-march=native -O2 -ggdb" (and aditionally configured mesa with --enable-debug running ./autogen.sh). However on calling glxinfo within gdb I still get: "Reading symbols from /usr/bin/glxinfo...(no debugging symbols found)...done." Sorry, it seems as though I cannot contribute anything useful at the moment. Best regards, Heinrich (In reply to comment #4) > However on calling glxinfo within gdb I still get: > > "Reading symbols from /usr/bin/glxinfo...(no debugging symbols found)...done." That should be okay, so long as it can get debugging symbols for r300_dri.so. No bug but a user mistake. I had not configured the respective mesa code with --with-dri-drivers=radeon,r200,r300,r600 as proposed in radeonBuildHowTo but had assumed that configure option --with-dri-drivers=radeon was ok for my r500. So an older version of r300_dri.so was in my /usr/lib/dri/ which probably caused the segfault. |
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.
xserver crashes immediately after kde4 login. login to fluxbox is working but a glxinfo gives me: name of display: :0.0 Speicherzugriffsfehler And dmesg: glxinfo[7533]: segfault at 10 ip b714add7 sp bfa71350 error 4 in r300_dri.so[b7104000+273000] Xorg.Olog.old states: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x3b) [0x81314cb] 1: /usr/bin/X(xf86SigHandler+0x51) [0x80c1df1] 2: [0xb772e400] Fatal server error: Caught signal 11. Server aborting Asus Laptop x2300 video kernel 2.6.32.2 from kernel.org (radeon kms enabled) loading radeon module via /etc/modules /etc/modprobe.d/radeon.conf : options radeon modeset=1 agpmode=-1 xserver: Debain Sid (1.6.5) no xorg.conf from git (latest pull 01-03-2010): macros dri2proto drm (--enable-radeon-experimental-api) xf86-video-ati mesa (--with-dri-drivers=radeon --disable-gallium) Thank you for considering this bug report. I'd be glad to provide any further information if needed. Heinrich Fu Jin Wang