Created attachment 394235 [details] All errors and information as mentioned Description of problem: At random, the system will crash with a backtrace in radeon_blit.c with a ton of repeating dmesg output. Happens more frequently in firefox shipped with Fedora 12, but can happen independently of firefox. This crash takes one of 3 forms: 1. Freezes all graphics, allows switching to other ttys 2. Freezes all graphics, does not allow switching to other ttys 3. Screen flashes, turns black, cursor reappears. Total crash, kernel oops. (most common) Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12 How reproducible: May be difficult to reproduce. Steps to Reproduce: 1. Have a RV620 chipset 2. Be using the xorg-x11-drv-ati driver, and all standard packages. 3. Use the computer graphically until bug occurs (seems random, I can find no way of predicting it) Actual results: Crashes system Expected results: Would not crash system Additional info: My card is a RV620 chipset. Happens in multiple desktop environments. I have no Xorg.conf, and will post a /var/log/messages as soon as I get the crash with tty switching. Attached are my Xorg log, dmesg error (repeats hundreds of times), and my backtrace. I have not tried using the radeonhd driver.
whoops, sorry, in my previous post, I mentioned the backtrace was in radeon_blit.c. That's incorrect, it's in r600_blit_kms.c. Sorry for the inconvenience.
Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49ea48] 1: /usr/bin/Xorg (mieqEnqueue+0x1f4) [0x49e414] 2: /usr/bin/Xorg (xf86PostMotionEventP+0xce) [0x478fae] 3: /usr/bin/Xorg (xf86PostMotionEvent+0xa9) [0x479169] 4: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f5f9f423000+0x3739) [0x7f5f9f426739] 5: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f5f9f423000+0x5ae8) [0x7f5f9f428ae8] 6: /usr/bin/Xorg (0x400000+0x6bea7) [0x46bea7] 7: /usr/bin/Xorg (0x400000+0x116d53) [0x516d53] 8: /lib64/libpthread.so.0 (0x311f000000+0xf0f0) [0x311f00f0f0] 9: /lib64/libc.so.6 (ioctl+0x7) [0x311e8d6937] 10: /usr/lib64/libdrm.so.2 (drmIoctl+0x23) [0x3137003383] 11: /usr/lib64/libdrm.so.2 (drmCommandWriteRead+0x1c) [0x31370035cc] 12: /usr/lib64/libdrm_radeon.so.1 (0x7f5fa08f0000+0x1469) [0x7f5fa08f1469] 13: /usr/lib64/libdrm_radeon.so.1 (0x7f5fa08f0000+0x14b4) [0x7f5fa08f14b4] 14: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f5fa0b0a000+0xb9050) [0x7f5fa0bc3050] 15: /usr/lib64/xorg/modules/libexa.so (0x7f5f9feab000+0x82d8) [0x7f5f9feb32d8] 16: /usr/bin/Xorg (0x400000+0x152e44) [0x552e44] 17: /usr/bin/Xorg (0x400000+0x2dfd0) [0x42dfd0] 18: /usr/bin/Xorg (0x400000+0x2c71c) [0x42c71c] 19: /usr/bin/Xorg (0x400000+0x21d5a) [0x421d5a] 20: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x311e81eb1d] 21: /usr/bin/Xorg (0x400000+0x21909) [0x421909]
Hmmm... Seems to not crash with a nomodeset in the grub line, but obviously there's no KMS, therefore, no 3-D acceleration :( After some updates, there is only one kind of crash, everything sort of flashes, and everything goes black. Is there any more information I can provide you all with?
Hey! I just found this from some googling. This sounds exactly what I'm experiencing. They even tracked down the git revision where things went off. http://www.opensubscriber.com/message/dri-devel@lists.sourceforge.net/12916135.html I hope this helps!
I just turned KMS back on, and I'm not experiencing the bug any more. I used the latest from updates-testing. Woohoo!
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.