All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601 dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Feb 2018 06:17:37 +0000	[thread overview]
Message-ID: <bug-104064-502-TEyiaLeUpg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104064-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Bjorn <bjorn.aili@gmail.com> ---
Created attachment 137103
  --> https://bugs.freedesktop.org/attachment.cgi?id=137103&action=edit
dmesg output without amdgpu.dc=1

I'm seemingly hitting this too, on 4.15. Note that I get it with or without
amdgpu.dc=1.

Might also be relevant that on 4.14 and earlier, I would get kernel oopsies on
resume from suspend, with a very similar dmesg output (oopsie would happen in
the same dm_suspend function and same stack trace, as far as I can recall).
While I don't have any saved dmesg's from that, I could boot an old kernel to
obtain one if it seems useful.

I have slightly different hardware (eg, Radeon RX 570), but it's also a hybrid
laptop.

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

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

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

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

  parent reply	other threads:[~2018-02-01  6:17 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 11:02 [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601 dm_suspend+0x4e/0x60 [amdgpu] bugzilla-daemon
2017-12-04 11:03 ` bugzilla-daemon
2018-02-01  6:17 ` bugzilla-daemon [this message]
2018-02-01  6:32 ` bugzilla-daemon
2018-02-27  0:39 ` bugzilla-daemon
2018-02-27  3:36 ` bugzilla-daemon
2018-02-27 11:24 ` bugzilla-daemon
2018-02-27 13:57 ` bugzilla-daemon
2018-02-27 14:25 ` bugzilla-daemon
2018-02-27 15:26 ` bugzilla-daemon
2018-02-27 15:30 ` bugzilla-daemon
2018-02-27 15:54 ` bugzilla-daemon
2018-02-27 16:02 ` bugzilla-daemon
2018-02-27 16:07 ` bugzilla-daemon
2018-02-27 16:41 ` bugzilla-daemon
2018-02-27 20:40 ` bugzilla-daemon
2018-02-27 21:30 ` bugzilla-daemon
2018-02-27 21:44 ` bugzilla-daemon
2018-03-01 13:13 ` bugzilla-daemon
2018-03-01 14:44 ` bugzilla-daemon
2018-03-01 16:11 ` bugzilla-daemon
2018-03-01 16:39 ` bugzilla-daemon
2018-03-01 16:48 ` bugzilla-daemon
2018-03-01 19:59 ` bugzilla-daemon
2018-03-01 20:01 ` bugzilla-daemon
2018-03-06  9:29 ` bugzilla-daemon
2018-03-06  9:38 ` bugzilla-daemon
2018-03-06 13:32 ` bugzilla-daemon
2018-03-07 10:56 ` bugzilla-daemon
2018-03-10 22:08 ` bugzilla-daemon
2018-03-12 13:45 ` bugzilla-daemon
2018-03-12 14:21 ` bugzilla-daemon
2018-03-12 15:07 ` bugzilla-daemon
2018-03-12 15:54 ` bugzilla-daemon
2018-03-12 15:56 ` bugzilla-daemon
2018-03-12 17:56 ` bugzilla-daemon
2018-03-12 17:59 ` bugzilla-daemon
2018-03-12 18:00 ` bugzilla-daemon
2018-03-12 18:07 ` bugzilla-daemon
2018-03-12 18:09 ` bugzilla-daemon
2018-03-21 21:23 ` bugzilla-daemon
2018-03-21 22:15 ` bugzilla-daemon
2018-03-22  0:29 ` bugzilla-daemon
2018-03-22  2:11 ` bugzilla-daemon
2018-03-22 11:44 ` bugzilla-daemon
2018-03-22 11:46 ` bugzilla-daemon
2018-03-22 14:05 ` bugzilla-daemon
2018-03-23  8:55 ` bugzilla-daemon
2018-03-24 19:05 ` bugzilla-daemon
2018-03-24 20:57 ` bugzilla-daemon
2018-03-28  3:34 ` bugzilla-daemon
2018-03-28  9:23 ` bugzilla-daemon
2018-03-28 14:10 ` bugzilla-daemon
2018-06-26 14:22 ` 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-104064-502-TEyiaLeUpg@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.