| Summary: | [Mobility FireGL 9000] cs_gem_write_reloc: Assertion `bo->space_accounted` failed. | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Nikolay Vladimirov <nikolay> |
| Component: | Drivers/DRI/r200 | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
| Status: | NEW --- | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | CC: | alex.hunziker, nikolay |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
dmesg
xorg log Experimenatal patch to fix space validation assertion |
||
Created attachment 25096 [details]
xorg log
I have the media center software "Moovida" fail on startup with the same error message: python: ../../../libdrm/radeon/radeon_cs_gem.c:121: cs_gem_write_reloc: Assertion `bo->space_accounted' failed. Aborted (core dumped) This is on Ubuntu Karmic with the new radeon-rewrite stack and DRI2. Can you try to get backtrace? easy way to do it is to enable core dumps and then analysing dump with gdb: ulimit -c unlimited glxgears gdb --core=core glxgears bt full q Not sure how helpful this will be, as there are many missing symbol names. Anyway, there you go: Core was generated by `/usr/bin/python /usr/bin/moovida'. Program terminated with signal 6, Aborted. #0 0xb7f84422 in __kernel_vsyscall () (gdb) bt full #0 0xb7f84422 in __kernel_vsyscall () No symbol table info available. #1 0xb7dde4f1 in ?? () No symbol table info available. #2 0xb7f07ff4 in ?? () No symbol table info available. #3 0xb5d3be38 in ?? () No symbol table info available. #4 0xb5d3be40 in ?? () No symbol table info available. #5 0xb7de1952 in ?? () No symbol table info available. #6 0x00000006 in ?? () No symbol table info available. #7 0xb5d3bdb8 in ?? () No symbol table info available. #8 0x00000000 in ?? () No symbol table info available. Created attachment 28624 [details] [review] Experimenatal patch to fix space validation assertion You would need to install debug symbols (libgl1-mesa-dri-dbg package for me) Can you try attached patch if it fixes problem for you? I tried to get a better stack trace, but failed. I have all mesa and dri debug symbols installed that I could find but there are still no symbol names in the trace. I notice the patch is against files in the r200 directory. I'm using an R500 GPU (Radeon Mobile X1400) - is the patch still relevant? I will try to apply the patch, but I'll have to read myself into debian packaging again before I can do that. If someone feels like providing a Karmic package, I won't be mad :-) I just looked at original report that told card is r200 so fix is for r200 only. There is no similar patch for r300 yet so you have to wait for a moment. I guess backtrace problem is because of python. It might help if you installed python debug symbols. Also libdrm2-dbg will show symbols for few last calls. It would help if you could reproduce same bug with some others program too. Sorry for not mentioning what hardware I use earlier. I cannot reproduce the bug in anything else so far. glxgears, neverball, and all GL screensavers work fine. The patch applied cleanly to a recent git snapshot of MESA. I'll be happy to try it out when there's a patch for the r300 series. Mass version move, cvs -> git This could be fixed in mesa master and 7.9 branch: http://lists.freedesktop.org/archives/mesa-dev/2010-October/003492.html |
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.
Created attachment 25095 [details] dmesg Description of problem: Using clean fedora 11 latest rawhide network install. No manual modification. just opened up a terminal and ran glxgears. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.12.2-4.fc11.i586 How reproducible: always Steps to Reproduce: 1.run glxgears Actual results: glxgears exits with: glxgears: radeon_cs_gem.c:121: cs_gem_write_reloc: Assertion `bo->space_accounted` failed. Expected results: Normal glxgears run. Additional info: there are some radeon related messages from the kernel. Attaching dmesg and Xorg.0.log. No xorg.conf.