Red Hat Bugzilla – Bug 510485
general protection fault - radeon_read_ring_rptr
Last modified: 2010-03-31 10:39:53 EDT
Created attachment 351067 [details]
segment of log
Description of problem:
details from log
Version-Release number of selected component (if applicable):
Steps to Reproduce:
up to date Fedora 11 install
AMD 810 quad core 64 bit
8 GB DDR3 RAM
5 * 500GB in software RAID-6 configuration
ASUS M4A78T-E mother board
Created attachment 351328 [details]
segment of messages log
'jupiter': problem host
'neptune': my main workstation
I found that the screen had frozen on saturn, but the logged in terminal from jupiter was still active.
From jupiter, I had top displaying tasks from saturn. I attempted to kill xorg which was at about 100% processor usage using the default signal, no affect. Then I used signal 9, and got kernel messages on all my terminals logged into saturn (xorg cpu usage now about 0%). Found the relevant section of the log and attached it.Linux saturn
188.8.131.52-191.fc11.x86_64.debug #1 SMP Tue Jun 16 23:09:06 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
This may be related to:
Bug 510482 - unable to handle kernel paging request - radeon_read_ring_rptr
I note that the first 6 lines, at least, of the call trace appear to be identical.
I think this is a duplicate of Bug 488940
Can you test with fedora 12 livecd and report if it works with it.
Sorry I can't, as the live CD fails to load properly see Bug 531945.
Can you retest now in F13 Alpha?
Sorry, it is not practical for me to run the Fedora 13 alpha, as the machine is both my main development machine and the gateway to the Internet for my local network.
I have been running Fedora 12 on saturn for a few months now.
However, I looked through my messages logs for the last few weeks and found no evidence of the 'radeon_read_ring_rptr' problem.
My current kernel is:
Linux saturn 184.108.40.206-90.fc12.x86_64 #1 SMP Tue Mar 23 09:47:08 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
Thanks for letting us know.
*** Bug 510482 has been marked as a duplicate of this bug. ***
I suddenly realized that I still had the SidePort disabled, as per:
Would it be useful if I tried restoring SidePort?