Bug 31573

Summary: Crash in EXA code (HD5770)
Product: xorg Reporter: Eduard Bloch <blade>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log file
none
Preliminary backtrace result
none
Kernel config
none
xorg.conf none

Description Eduard Bloch 2010-11-11 23:57:41 UTC
Created attachment 40226 [details]
Xorg log file

Using the a git snapshot from Wednesday (xf86-video-radeon,master) I seem to get crashes when some certain operation happens. I was able to play videos with reduced CPU load and everything was fine untilEclipse reported a "trap divide error" (this may be related or not, don't know). Some minutes later the X-server crashed while I was working in Eclipses debugger. Meanwhile I was able to reproduce this or similar crash 4-5 times, it's almost reliably reproducible with DDD and graphical variable display; double-clicking a
pointer brings the X server down instead of showing buble with the pointed
contents.

I am using a git snapshot from yesterday built with Xorg 1.9 from Debian
Experimental, on a Sid/amd64 system, kernel 2.6.34 with TuxOnIce rc2.

A quick backtrace result is attached. IMHO radeon_vbo_space returns a NULL pointer (vb) which is never checked.
Comment 1 Eduard Bloch 2010-11-11 23:58:37 UTC
Created attachment 40227 [details]
Preliminary backtrace result
Comment 2 Eduard Bloch 2010-11-11 23:59:10 UTC
Created attachment 40228 [details]
Kernel config
Comment 3 Eduard Bloch 2010-11-12 00:01:15 UTC
Created attachment 40229 [details]
xorg.conf
Comment 4 Michel Dänzer 2010-11-12 04:21:31 UTC
Looks similar to bug 31414, could be the same underlying cause.
Comment 5 Alex Deucher 2010-12-07 09:58:43 UTC

*** This bug has been marked as a duplicate of bug 31414 ***

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.