Bug 268261 - System crashs with radeon module
Summary: System crashs with radeon module
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 254004
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-30 18:20 UTC by Thomas Steudten
Modified: 2008-01-13 18:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-13 18:19:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.log (45.91 KB, text/plain)
2007-08-30 18:21 UTC, Thomas Steudten
no flags Details
xorg.conf (3.94 KB, text/plain)
2007-08-30 18:34 UTC, Thomas Steudten
no flags Details

Description Thomas Steudten 2007-08-30 18:20:38 UTC
running the system with Xserver, GL Application (antinspect) and OSD, crashs it:

Reproduce (run this script) runit.sh:
----------8<------------8<----------
#!/bin/sh
/usr/bin/Xorg :0 &
export DISPLAY=:0.0
sleep 5
/usr/libexec/xscreensaver/antinspect -root -delay 1000 -fps -shadows  &
sleep 10
sync
ls /bin | /usr/bin/osd_cat  -a -d 5 -o 70 -p bottom -l 10
### crash...
----------8<------------8<----------

Message comes up: Error: R300 timed out... exiting
(**) RADEON(0): RADEONCloseScreen
(**) RADEON(0): RADEONDRIStop

--- System freeze - no ping at all --

---
Fedora 7 latest updates
kernel  2.6.22.1-41
xosd-2.2.14-9.fc7

[drm] Initialized drm 1.1.0 20060810
[drm] Initialized radeon 1.27.0 20060524 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading R300 Microcode
[drm] writeback test succeeded in 1 usecs

md5sums:
c9cfe04eb7ad8799ce13ee5d42ff5a21  /usr/bin/Xorg
6987eb17c1da954a8e078e6e76e5ecf4  /usr/libexec/xscreensaver/antinspect
7280e04957aebf8165ecaa4223a85ede  /usr/bin/osd_cat

# modinfo radeon
filename:       /lib/modules/2.6.22.1-41.self.fc7/kernel/drivers/char/drm/radeon.ko
license:        GPL and additional rights
description:    ATI Radeon
author:         Gareth Hughes, Keith Whitwell, others.
srcversion:     599338B4A8E964DAA8797A8
depends:        drm
vermagic:       2.6.22.1-41.self.fc7 mod_unload PENTIUMM 4KSTACKS
parm:           no_wb:Disable AGP writeback for scratch registers

# modinfo drm
filename:       /lib/modules/2.6.22.1-41.self.fc7/kernel/drivers/char/drm/drm.ko
license:        GPL and additional rights
description:    DRM shared core routines
author:         Gareth Hughes, Leif Delgass, José Fonseca, Jon Smirl
srcversion:     2D5F3E3DCB9513E188C7268
depends:
vermagic:       2.6.22.1-41.self.fc7 mod_unload PENTIUMM 4KSTACKS
parm:           cards_limit:Maximum number of graphics cards (int)
parm:           debug:Enable debug output (int)

01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility
X600] (prog-if 00 [VGA])
        Subsystem: Samsung Electronics Co Ltd Unknown device c018
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at d0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at 3000 [size=256]
        Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at c0120000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Express Endpoint IRQ 0
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
        Capabilities: [100] Advanced Error Reporting

See Bug #254004

Comment 1 Thomas Steudten 2007-08-30 18:21:29 UTC
Created attachment 181461 [details]
Xorg.log

Comment 2 Thomas Steudten 2007-08-30 18:34:08 UTC
Created attachment 181541 [details]
xorg.conf

Comment 3 Christopher Brown 2007-09-30 16:22:04 UTC
Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem no longer exists then please close this bug as CURRENTRELEASE
indicating what resolved it for you or I'll do so in a few days if there is no
additional information lodged.

Comment 4 Christopher Brown 2008-01-13 18:19:04 UTC
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.


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