Bug 442227

Summary: kernel 2.6.25-0.218.rc8.git7.fc9.x86_64 oopses in radeon module
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-16 19:12:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 439966    
Attachments:
Description Flags
oops trace from 2.6.25-0.218.rc8 none

Description Michal Jaegermann 2008-04-13 00:21:26 UTC 
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
Comment 1 Michal Jaegermann 2008-04-13 00:21:26 UTC 
Created attachment 302246 [details]
oops trace from 2.6.25-0.218.rc8
Comment 2 Michal Jaegermann 2008-04-14 20:30:00 UTC 
I am afraid that I am getting the same oops by just logging out
from a desktop session.
Comment 3 Michal Jaegermann 2008-04-16 19:12:34 UTC 
With an update to kernel-2.6.25-0.234.rc9.git1.fc9.x86_64 so far,
so good. :-)  Thanks.