dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60381] New: AMD Radeon 7770 Ghz edition Crash with DPM active
Date: Thu,  4 Jul 2013 00:37:30 +0000 (UTC)	[thread overview]
Message-ID: <bug-60381-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=60381

           Summary: AMD Radeon 7770 Ghz edition Crash with DPM active
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.10.0-next-20130703
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Video(DRI - non Intel)
        AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
        ReportedBy: jrch2k10@gmail.com
        Regression: No


Created an attachment (id=106731)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=106731)
dmidecode

with 1 monitor it works fine until X session but UVD freeze the system and the
card never reclocks

multimonitor freeze the system the instant KMS try to load DVI  + HDMI

with static PM it crashes if you try to change the profile 

if you need any help to debug this issue plz provide instruction since the
hangs disable everything including ssh

system info as attach

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2013-07-04  0:37 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  0:37 bugzilla-daemon [this message]
2013-07-04  0:38 ` [Bug 60381] AMD Radeon 7770 Ghz edition Crash with DPM active bugzilla-daemon
2013-07-04  0:38 ` bugzilla-daemon
2013-07-04  1:01 ` bugzilla-daemon
2013-07-04  1:11 ` bugzilla-daemon
2013-07-04  1:12 ` bugzilla-daemon
2013-07-04  8:20 ` bugzilla-daemon
2013-07-07  1:37 ` bugzilla-daemon
2013-07-09  2:07 ` bugzilla-daemon
2013-07-12 16:14 ` bugzilla-daemon
2013-07-13  1:40 ` bugzilla-daemon
2013-07-16 10:22 ` bugzilla-daemon
2013-07-16 14:25 ` bugzilla-daemon
2013-07-16 16:16 ` bugzilla-daemon
2013-07-16 20:42 ` bugzilla-daemon
2013-07-16 23:44 ` bugzilla-daemon
2013-07-16 23:45 ` bugzilla-daemon
2013-07-17  1:42 ` bugzilla-daemon
2013-07-17  2:59 ` bugzilla-daemon
2013-07-17  4:06 ` bugzilla-daemon
2013-07-17  4:06 ` bugzilla-daemon
2013-07-17 11:58 ` bugzilla-daemon
2013-07-18  1:44 ` bugzilla-daemon
2013-07-18  1:46 ` bugzilla-daemon
2013-07-18 13:18 ` bugzilla-daemon
2013-07-18 15:02 ` bugzilla-daemon
2013-07-18 22:03 ` bugzilla-daemon
2013-07-18 22:13 ` bugzilla-daemon
2013-07-23  1:31 ` bugzilla-daemon
2013-07-23  1:32 ` bugzilla-daemon
2013-07-24  1:51 ` bugzilla-daemon
2013-07-24  1:52 ` bugzilla-daemon
2013-07-24  2:17 ` bugzilla-daemon
2013-07-24  2:50 ` bugzilla-daemon
2013-07-30  1:20 ` bugzilla-daemon
2013-07-30  7:53 ` bugzilla-daemon
2013-09-05 20:36 ` bugzilla-daemon
2013-09-05 21:04 ` bugzilla-daemon
2013-09-05 21:11 ` bugzilla-daemon
2013-09-06  1:17 ` bugzilla-daemon
2013-09-06  1:17 ` bugzilla-daemon
2013-09-06  1:18 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-60381-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).