All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91620] Tonga warnings after mem sleep with drm-next-4.3-wip
Date: Wed, 12 Aug 2015 18:19:49 +0000	[thread overview]
Message-ID: <bug-91620-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 91620
           Summary: Tonga warnings after mem sleep with drm-next-4.3-wip
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 117654
  --> https://bugs.freedesktop.org/attachment.cgi?id=117654&action=edit
dmesg with warnings

No ill effects but I see some WARNINGS after mem sleep with drm-next-4.3-wip. I
don't see them with 4.2 fixes.

 WARNING: CPU: 0 PID: 558 at include/drm/drm_crtc.h:1577
drm_helper_choose_encoder_dpms+0x83/0x90 [drm_kms_helper]()

Workqueue: events_unbound async_run_entry_fn

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

[-- Attachment #1.2: Type: text/html, Size: 2288 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:[~2015-08-12 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 18:19 bugzilla-daemon [this message]
2015-10-19 11:33 ` [Bug 91620] Tonga warnings after mem sleep with drm-next-4.3-wip bugzilla-daemon
2015-10-19 11:33 ` 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-91620-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.