From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211277] sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail
Date: Tue, 07 Sep 2021 11:02:13 +0000 [thread overview]
Message-ID: <bug-211277-2300-uDsnbEJIkJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211277-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211277
--- Comment #57 from James Zhu (jamesz@amd.com) ---
(In reply to Anthony Rabbito from comment #53)
> Thanks for chiming in James! Few things I've observed since adding
> 'pci=noats' the graphic artifacts seem to happen way less. I did observe one
> lockup which required me to hard shut down the computer. This was a wake
> from suspend scenario.
>
> I used to deal with somwhat similar issues here --
> https://bugs.freedesktop.org/show_bug.cgi?id=110674 not sure if that's of
> any use. Let me know if a fresh bug is warranted.
Hi Anthony,
The s3 hung issue here always with error: AMD-Vi: Event logged
[IO_PAGE_FAULT...] Bug:110674 don't have gfx ECC error. You case do have lots
of them.
Can you share the whole dmesg after you added pci=noats?
Regards!
James
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-09-07 11:02 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:25 [Bug 211277] New: sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail bugzilla-daemon
2021-01-19 10:25 ` [Bug 211277] " bugzilla-daemon
2021-01-19 10:27 ` bugzilla-daemon
2021-01-22 4:42 ` bugzilla-daemon
2021-01-24 19:23 ` bugzilla-daemon
2021-01-27 2:11 ` bugzilla-daemon
2021-01-30 10:25 ` bugzilla-daemon
2021-01-30 10:41 ` bugzilla-daemon
2021-02-21 0:17 ` bugzilla-daemon
2021-02-21 14:40 ` bugzilla-daemon
2021-02-25 22:28 ` bugzilla-daemon
2021-03-05 15:02 ` bugzilla-daemon
2021-03-05 15:13 ` bugzilla-daemon
2021-03-07 15:43 ` bugzilla-daemon
2021-03-11 13:55 ` bugzilla-daemon
2021-05-12 23:43 ` bugzilla-daemon
2021-05-13 2:20 ` bugzilla-daemon
2021-05-13 6:26 ` bugzilla-daemon
2021-05-18 15:17 ` bugzilla-daemon
2021-05-18 16:13 ` bugzilla-daemon
2021-05-18 16:41 ` bugzilla-daemon
2021-05-18 17:18 ` bugzilla-daemon
2021-05-18 18:04 ` bugzilla-daemon
2021-05-18 18:21 ` bugzilla-daemon
2021-05-18 18:21 ` bugzilla-daemon
2021-05-18 18:48 ` bugzilla-daemon
2021-05-18 19:33 ` bugzilla-daemon
2021-05-19 19:44 ` bugzilla-daemon
2021-05-19 20:02 ` bugzilla-daemon
2021-05-20 9:31 ` bugzilla-daemon
2021-05-20 9:40 ` bugzilla-daemon
2021-05-20 18:34 ` bugzilla-daemon
2021-05-20 18:42 ` bugzilla-daemon
2021-06-28 9:01 ` bugzilla-daemon
2021-08-04 12:43 ` bugzilla-daemon
2021-08-04 13:24 ` bugzilla-daemon
2021-08-25 12:00 ` bugzilla-daemon
2021-08-25 16:53 ` bugzilla-daemon
2021-08-25 17:09 ` bugzilla-daemon
2021-09-01 13:34 ` bugzilla-daemon
2021-09-02 12:59 ` bugzilla-daemon
2021-09-02 14:20 ` bugzilla-daemon
2021-09-02 21:24 ` bugzilla-daemon
2021-09-03 6:52 ` bugzilla-daemon
2021-09-03 11:54 ` bugzilla-daemon
2021-09-03 12:12 ` bugzilla-daemon
2021-09-03 12:13 ` bugzilla-daemon
2021-09-03 12:23 ` bugzilla-daemon
2021-09-04 17:41 ` bugzilla-daemon
2021-09-07 2:00 ` bugzilla-daemon
2021-09-07 2:32 ` bugzilla-daemon
2021-09-07 6:27 ` bugzilla-daemon
2021-09-07 6:27 ` bugzilla-daemon
2021-09-07 7:47 ` bugzilla-daemon
2021-09-07 11:02 ` bugzilla-daemon [this message]
2021-09-20 10:47 ` bugzilla-daemon
2021-09-20 11:34 ` bugzilla-daemon
2021-09-20 14:43 ` bugzilla-daemon
2021-09-20 14:57 ` bugzilla-daemon
2021-09-20 15:00 ` bugzilla-daemon
2021-09-20 21:07 ` bugzilla-daemon
2021-09-21 3:56 ` bugzilla-daemon
2021-09-21 4:04 ` bugzilla-daemon
2021-09-21 4:53 ` bugzilla-daemon
2021-09-21 14:32 ` bugzilla-daemon
2021-09-21 17:43 ` bugzilla-daemon
2021-09-21 17:43 ` bugzilla-daemon
2021-09-21 18:02 ` bugzilla-daemon
2021-09-21 18:29 ` bugzilla-daemon
2021-09-22 13:59 ` bugzilla-daemon
2021-11-15 1:39 ` bugzilla-daemon
2021-11-23 9:31 ` bugzilla-daemon
2021-11-23 13:28 ` bugzilla-daemon
2021-11-23 20:44 ` bugzilla-daemon
2021-11-24 3:22 ` bugzilla-daemon
2021-11-25 18:34 ` bugzilla-daemon
2021-11-25 18:58 ` bugzilla-daemon
2021-11-25 20:48 ` bugzilla-daemon
2021-11-26 4:04 ` bugzilla-daemon
2021-11-26 16:37 ` bugzilla-daemon
2021-11-27 12:14 ` bugzilla-daemon
2021-11-27 13:03 ` bugzilla-daemon
2021-11-29 19:21 ` bugzilla-daemon
2021-11-29 19:53 ` bugzilla-daemon
2021-12-04 22:29 ` bugzilla-daemon
2022-01-23 13:54 ` 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-211277-2300-uDsnbEJIkJ@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 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.