Michel Dänzer <mic...@daenzer.net> writes: > Probably not (AGP is flaky in general, but in particular with older > UniNorth bridges), but it might be interesting to see some kernel output > from booting without agpmode=-1. If you can't get it via ssh, maybe you > can via netconsole or so.
While logging into KDE: radeon 0000:00:10.0: GPU lockup CP stall for more than 10064msec GPU lockup (waiting for 0x000003EE last fence id 0x000003ED) radeon: wait for empty RBBM fifo failed ! Bad things might happen. Failed to wait GUI idle while programming pipes. Bad things might happen. radeon 0000:00:10.0: (r300_asic_reset:414) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: (r300_asic_reset:433) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: (r300_asic_reset:445) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: GPU reset succeed radeon 0000:00:10.0: GPU reset succeed radeon 0000:00:10.0: (r300_asic_reset:414) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: (r300_asic_reset:433) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: (r300_asic_reset:445) RBBM_STATUS=0x8802C137 radeon 0000:00:10.0: GPU reset succeed radeon: wait for empty RBBM fifo failed ! Bad things might happen. Failed to wait GUI idle while programming pipes. Bad things might happen. After that is is dead. GPU lockup appears to be a common problem with the radeon driver. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
