From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109526] [CARRIZO] amdgpu fails to resume from S3, atombios stuck executing C554 (len 629, WS 0, PS 0)
Date: Thu, 31 Jan 2019 22:17:15 +0000 [thread overview]
Message-ID: <bug-109526-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1058 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109526
Bug ID: 109526
Summary: [CARRIZO] amdgpu fails to resume from S3, atombios
stuck executing C554 (len 629, WS 0, PS 0)
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: johannes.hirte@datenkhaos.de
there is already a similar report at kernel bugzilla, but nobody took notice:
https://bugzilla.kernel.org/show_bug.cgi?id=190971
It's a kernel bug, first seen with linux-4.20 on my Carrizo. I don't have a
testcase for reproducing, so it's hard to bisect. Sometimes it happens multiple
times a day, with every suspend-resume cycle. Sometimes the machine works for
several days with at least two suspend-resume-cycles per day.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2443 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
next reply other threads:[~2019-01-31 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 22:17 bugzilla-daemon [this message]
2019-02-13 15:21 ` [Bug 109526] [CARRIZO] amdgpu fails to resume from S3, atombios stuck executing C554 (len 629, WS 0, PS 0) bugzilla-daemon
2019-02-14 14:34 ` bugzilla-daemon
2019-02-14 21:35 ` bugzilla-daemon
2019-03-20 16:28 ` bugzilla-daemon
2019-04-24 16:28 ` bugzilla-daemon
2019-05-08 17:26 ` bugzilla-daemon
2019-11-19 9:12 ` 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-109526-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.