Bug 669853 - KMS: GPU lockup ATI Radeon X700 PRO (RV410) (PCIE) while playing DVD
Summary: KMS: GPU lockup ATI Radeon X700 PRO (RV410) (PCIE) while playing DVD
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 14
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-15 03:07 UTC by Tom Horsley
Modified: 2012-08-16 18:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:26:38 UTC
Type: ---


Attachments (Terms of Use)
clip from /var/log/messages where radeon driver spewed errors (39.49 KB, text/plain)
2011-01-15 03:08 UTC, Tom Horsley
no flags Details
/var/log/Xorg.0.log.old (36.59 KB, text/plain)
2011-01-15 03:09 UTC, Tom Horsley
no flags Details

Description Tom Horsley 2011-01-15 03:07:54 UTC
Description of problem:

A thread in the fedora users list was talking about DVD playing problems, so
I decided to pop in a DVD (October Sky) and try to play it with my
mplayer script that plays fullscreen and sends audio to optical out on
a 2nd sound card I have just for mplay to use. Here's the script:

#!/bin/sh
#
amixer --card 1 sset IEC958 unmute
exec mplayer dvd://1 -alang en -ao alsa:device=hw=1.0 -ac hwdts,hwac3, -monitoraspect 16:9 -fs

It started playing just fine, but just a minute or so into the movie, it
started getting real jerky, then froze up completely.

I was able to Ctrl-Alt-F2 to get in a terminal and reboot, so the system
was still somewhat responsive.

lspci shows:

01:00.0 VGA compatible controller: ATI Technologies Inc RV410 [Radeon X700 Pro (PCIE)]
01:00.1 Display controller: ATI Technologies Inc RV410 [Radeon X700 Pro (PCIE)] (Secondary)

Not using secondary output, primary is connected via DVI.

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.13.1-0.3.20100705git37b348059.fc14.x86_64
mplayer-1.0-0.119.20100703svn.fc14.x86_64


How reproducible:
I was kinda reluctant to try it again

Steps to Reproduce:
1. see above
2.
3.
  
Actual results:
radeon driver crash

Expected results:
play movie

Additional info:

I'll attach the errors from the /var/log/messages file and the xorg log.
I don't have a xorg.conf file.

Comment 1 Tom Horsley 2011-01-15 03:08:53 UTC
Created attachment 473622 [details]
clip from /var/log/messages where radeon driver spewed errors

Comment 2 Tom Horsley 2011-01-15 03:09:46 UTC
Created attachment 473623 [details]
/var/log/Xorg.0.log.old

Comment 3 Fedora End Of Life 2012-08-16 18:26:40 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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