On Friday 18 February 2005 20:04, Nicolai Haehnle wrote: > There's still at least one hardware lockup bug that can be triggered with > glxgears; unfortunately, this one doesn't seem to be so easily > reproducible.
This bug can be triggered on my machine by a single instance of glxgears. It seems to be unrelated to 2D activity. The lockup is a lot more likely to occur for me at high framerates. This is unfortunate, because it means that I need to turn down debug message volume, otherwise the lockup is actually very unlikely to appear at all. However, the lockup seems to be unrelated to the use of "sync": It has happened both with RADEON_DEBUG= empty and with RADEON_DEBUG=sync. When I don't issue any of the magic "begin3d" sequences from the userspace driver, the lockup always happens just after one DMA block has been discarded, but I can't find a pattern as to when it happens exactly. Emitting some of those magic sequences changes the time when the lockup happens a bit, but I have no idea what's really going on. cu, Nicolai
pgpMA0G4AdB6f.pgp
Description: PGP signature