Bug 442227 - kernel 2.6.25-0.218.rc8.git7.fc9.x86_64 oopses in radeon module
Summary: kernel 2.6.25-0.218.rc8.git7.fc9.x86_64 oopses in radeon module
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F9KernelBlocker
TreeView+ depends on / blocked
Reported: 2008-04-13 00:21 UTC by Michal Jaegermann
Modified: 2008-04-16 19:12 UTC (History)
0 users

Clone Of:
Last Closed: 2008-04-16 19:12:34 UTC

Attachments (Terms of Use)
oops trace from 2.6.25-0.218.rc8 (3.22 KB, text/plain)
2008-04-13 00:21 UTC, Michal Jaegermann
no flags Details

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.

Note You need to log in before you can comment on or make changes to this bug.