dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76761] New: radeon driver breaks suspend to disk and resume from RAM in 3.14
Date: Thu, 22 May 2014 19:35:12 +0000	[thread overview]
Message-ID: <bug-76761-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 76761
           Summary: radeon driver breaks suspend to disk and resume from
                    RAM in 3.14
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.14.4 (debian 3.14.4-1 amd64)
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: vitalif@yourcmc.ru
        Regression: Yes

Hi!

The suspend/resume has broken again on my laptop with the 3.14 kernel. But it
works without any problem when I boot without radeon module, so I assume it's
the case.

The problem detail is:
- machine suspends to RAM without problem, but does not resume (hangs with
black screen during resume)
- machine does not suspend to disk (just hangs with black screen after
"snapshotting system", magic sysrq doesn't work so I assume that's an "oops"),
neither via s2disk or echo disk > /sys/power/state

Without the radeon module, everything works OK; the card is RV730.

Are there any other details I should provide?

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

             reply	other threads:[~2014-05-22 19:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 19:35 bugzilla-daemon [this message]
2014-05-22 19:51 ` [Bug 76761] radeon driver breaks suspend to disk and resume from RAM in 3.14 bugzilla-daemon
2014-05-22 19:56 ` bugzilla-daemon
2014-05-22 19:57 ` [Bug 76761] radeon DPM " bugzilla-daemon
2014-05-23 23:24 ` bugzilla-daemon
2014-05-24 16:43 ` bugzilla-daemon
2014-05-27 21:23 ` bugzilla-daemon
2014-05-28  0:11 ` bugzilla-daemon
2014-05-30 14:31 ` bugzilla-daemon
2014-05-30 14:49 ` bugzilla-daemon
2014-05-30 22:34 ` bugzilla-daemon
2014-05-30 22:42 ` bugzilla-daemon
2014-06-02 21:33 ` bugzilla-daemon
2014-06-09  7:19 ` bugzilla-daemon
2014-06-09 13:46 ` bugzilla-daemon
2014-06-10  3:25 ` bugzilla-daemon
2014-06-10  3:36 ` bugzilla-daemon
2014-06-10  7:22 ` bugzilla-daemon
2014-06-10  8:29 ` bugzilla-daemon
2014-06-10 14:00 ` bugzilla-daemon
2014-08-29 18:28 ` 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-76761-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