wolf2 test triggers it, and it completely locks either the card or the
driver... killing wolf2/X via ssh, then trying to start the X-server (via ssh)
hangs the kernel on the radeon probe. Commenting out the printk (as was suggested
in other lists) only cuts down on kernel CPU usage, it doesn't help the problem.
I looked into replacing the kernel DRI module with the ones from other branches,
no go. (Not that there's a significant difference between CVS and the stock
I'm willing to help debug this, especially if we can find a quicker test-case
then loading wolf2test and starting a game. First guess would be that we're
very ungraceful when we run out of texture or framebuffer memory on-card,
and wolf2 is the first game complex enough to hit that limit instantly.
(quake3 hits it eventually while playing and locks)
I note previous bug reports here indicate they only had a few messages ( less
then 200)... I'm scrolling thousands:
Nov 19 19:43:13 vulpine kernel: [drm:radeon_freelist_get] *ERROR* returning NULL!
Nov 19 19:43:44 vulpine last message repeated 1115 times
Nov 19 19:44:45 vulpine last message repeated 2264 times
Nov 19 19:45:46 vulpine last message repeated 2157 times
Nov 19 19:46:10 vulpine last message repeated 823 times
Nov 19 19:47:48 vulpine init: Switching to runlevel: 6
... as long as I don't try to touch the radeon after lockup, I can ssh in and