Celestia program starts, draws the universe for a few seconds, then crashes with the error message: "radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi->space_accounted' failed".
Using kernel 220.127.116.11 (2.6.37 already out, but hangs the X server at start), Mesa 7.10 r600c, radeon 6.13.99-af2e6d7d2f1b3d8f8f6b0acfb2b7b0cfaff7bcdb.
This does not happen when the Option "NoAccel" is set to "true" and Mesa is then using software rendering.
Does r600g work any better?
Yes, r600g (from Mesa 7.10) does not have this particular bug. But it has loads of other visual problems in celestia (which are not in r600c).
IIRC there was a similar problem on other radeon drivers that was fixed with the following commits:
If you could provide a patch for R600c (mesa 7.10) I can compile and test it.
Please try r600g, classic driver is no longer actively supported
Please do not spam my celestia bugs with useless comments without reading the history. R600g was already proposed and I already said in this same bug, that r600g is not an option, it is much worse than r600c. R600c works almost fine, just with small problems filed as bugs (e.g. bug 30502). R600g fails to render whole planets, stars, labels. Anyway, where can I read this 'no longer maintained' press release? I haven't seen anything like that.
The original report was with celestia 1.6.0. Now with version 1.6.1 and a Qt4 build, it starts up fine. It may be because the default value for "Texture resolution" is Medium. When toggling this to High (it means celestia loads other higher resolution texture files (jpg/png images)) it crashes again. However, the crash happens only at certain planets, i.e. toggling to High while viewing Mercury works fine. When moving to Earth, it crashes before displaying it. The highres texture for Mercury is 4096x2048px. The texture for Earth is 8192x4096px.
This radeon hardware should support 8192px textures, it is also shown in Help->OpenGL info. It also worked fine before Mesa 7.10 (and some devel version of 7.9).
This bug currently does not happen on kernel 18.104.22.168 and Mesa 7.10.2.
Let's close this, it does not currently happen. And also see bug 43893 comment 15.