Description of problem: The following was produced in log files: BUG: unable to handle kernel paging request at ffffc200002b1e08 IP: [<ffffffff8838291d>] :radeon:radeon_driver_lastclose+0x21/0x3b .... Fixing recursive fault but reboot is needed A full oops trace is attached. After such oops a zombie X process is left in a D state and cannot be killed. A display and a keyboard stop responding although a login from a remote is still possible. The message "reboot is neeeded" above is not kidding. It looks like that this is always repeatable with a help of 'pkill -f gdm' command. Rebooting with 2.6.25-0.204.rc8.git4.fc9.x86_64 kernel makes that command to perform without oopsing. 'pkill -f X' does not seem to be a problem. Version-Release number of selected component (if applicable): kernel-2.6.25-0.218.rc8.git7.fc9. Also /usr/sbin/gdm-restart seems to be harmless but that just sends SIGHUP to an existing gdm process and does not terminate an exisiting one. How reproducible: apparently always as described
Created attachment 302246 [details] oops trace from 2.6.25-0.218.rc8
I am afraid that I am getting the same oops by just logging out from a desktop session.
With an update to kernel-2.6.25-0.234.rc9.git1.fc9.x86_64 so far, so good. :-) Thanks.