dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76531] New: linux-3.14-rc7 radeon/nouveau runtime-suspend never coming back
Date: Sun, 23 Mar 2014 23:03:29 +0000	[thread overview]
Message-ID: <bug-76531-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76531
          Assignee: dri-devel@lists.freedesktop.org
           Summary: linux-3.14-rc7 radeon/nouveau runtime-suspend never
                    coming back
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: bonbons67@internet.lu
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/other
           Product: DRI

Most recent testing: 3.14-rc7 mainline.

As suggested on IRC by imirkin, returning -EBUSY instead of -EINVAL from
nouveau_pmops_runtime_suspend() avoids driver to fall too far to the ground.

When returning -EINVAL connectors get being seen as "disconnected" and there is
no way to get them connected anymore.

When returning -EBUSY the connectors stay functional but DE (enlightenment)
complains about missing crtc and all that is visible is black background and a
cursor that response to mouse/trackpad.

Way to reproduce:
Have xorg running, then for each avtive output call:
xrandr --output $OUTPUT --off

When last output got marked off runtime-suspend kicks in.


Same/similar behavior has been observed on radeon (I don't remember the exact
kernel releases, but older ones got console to display when switching VTs while
newer failed to do so).

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

[-- Attachment #1.2: Type: text/html, Size: 2765 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:[~2014-03-23 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23 23:03 bugzilla-daemon [this message]
2014-03-23 23:11 ` [Bug 76531] linux-3.14-rc7 radeon/nouveau runtime-suspend never coming back bugzilla-daemon
2014-03-23 23:15 ` bugzilla-daemon
2014-06-08 14:55 ` bugzilla-daemon
2014-06-08 15:07 ` 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-76531-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox