All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66942] New: Cayman HD 6950 hangs at start when loading kernel 3.11.0-rc1 or drm-next
Date: Mon, 15 Jul 2013 20:19:56 +0000	[thread overview]
Message-ID: <bug-66942-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=66942

          Priority: medium
            Bug ID: 66942
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Cayman HD 6950 hangs at start when loading kernel
                    3.11.0-rc1 or drm-next
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: alexandre.f.demers@gmail.com
          Hardware: All
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

I just compiled and tested kernel 3.11.0-rc1. It hangs and do nothing when
initializing (last thing displayed is "Loading initial ramdisk").

Setting radeon.dpm=1 or 0 gives the same result. 

Since I know I'm also experiencing this hang with last week drm-next branch,
I'll try to bisect and see where it leads us.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2245 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-07-15 20:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 20:19 bugzilla-daemon [this message]
2013-07-15 20:21 ` [Bug 66942] Cayman HD 6950 hangs at start when loading kernel 3.11.0-rc1 or drm-next bugzilla-daemon
2013-07-15 20:26 ` bugzilla-daemon
2013-07-15 23:17 ` bugzilla-daemon
2013-07-16 23:22 ` bugzilla-daemon
2013-07-16 23:28 ` bugzilla-daemon
2013-07-17  1:22 ` bugzilla-daemon
2013-07-17  4:17 ` bugzilla-daemon
2013-07-17  8:52 ` bugzilla-daemon
2013-07-18  3:25 ` bugzilla-daemon
2013-07-19  4:12 ` bugzilla-daemon
2013-07-20 16:03 ` bugzilla-daemon
2013-07-20 16:32 ` bugzilla-daemon
2013-07-22 13:39 ` bugzilla-daemon
2013-07-27  8:27 ` bugzilla-daemon
2013-07-28 17:47 ` bugzilla-daemon
2013-07-28 19:14 ` bugzilla-daemon
2013-07-28 19:50 ` bugzilla-daemon
2013-07-30  2:35 ` bugzilla-daemon
2013-07-30  2:49 ` bugzilla-daemon
2013-07-30  2:52 ` bugzilla-daemon
2013-07-30 17:21 ` bugzilla-daemon
2013-07-30 17:24 ` bugzilla-daemon
2013-07-31  5:05 ` 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-66942-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.