From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216119] 087451f372bf76d breaks hibernation on amdgpu Radeon R9 390
Date: Thu, 15 Dec 2022 20:39:34 +0000 [thread overview]
Message-ID: <bug-216119-2300-9Ga2j5S42z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216119-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #48 from Harald Judt (h.judt@gmx.at) ---
Ok. I am quite sure about this, but I have new observations which could mean
that the hibernation issue could be fixed but there is another issue.
First, I have tried 6.1.0. Hibernation/resume seems to work as long as I do not
VT switch, causing the ring gfx timeout but soft recovered messages and fences
timed out. I have not tested this thoroughly enough though.
Second, the
amdgpu: GPU fault detected: 146 0x0006c40c
amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x060C400C
amdgpu: VM fault (0x0c, vmid 3, pasid 0) at page 0, read from 'TC7'
(0x54433700) (196)
and similar messages also happen with 5.18.19 when VT-switching, though *much*
more rarely.
It seems these remaining problems are likely more related to VT-switching than
having to do with hibernate/resume now. Maybe the new fb code or other changes
in the driver just cause these problems to happen more often?
--
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:[~2022-12-15 20:40 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 21:42 [Bug 216119] New: 087451f372bf76d breaks hibernation on amdgpu Radeon R9 390 bugzilla-daemon
2022-06-12 21:46 ` [Bug 216119] " bugzilla-daemon
2022-06-13 10:27 ` bugzilla-daemon
2022-06-13 13:48 ` bugzilla-daemon
2022-06-16 18:40 ` bugzilla-daemon
2022-06-16 19:15 ` bugzilla-daemon
2022-06-16 19:16 ` bugzilla-daemon
2022-06-16 19:24 ` bugzilla-daemon
2022-06-16 19:35 ` bugzilla-daemon
2022-06-16 19:47 ` bugzilla-daemon
2022-06-16 19:55 ` bugzilla-daemon
2022-06-16 21:57 ` bugzilla-daemon
2022-06-16 22:36 ` bugzilla-daemon
2022-06-21 14:08 ` bugzilla-daemon
2022-06-21 14:08 ` bugzilla-daemon
2022-06-21 14:08 ` bugzilla-daemon
2022-06-21 14:09 ` bugzilla-daemon
2022-06-21 22:33 ` bugzilla-daemon
2022-06-22 13:22 ` bugzilla-daemon
2022-06-22 21:08 ` bugzilla-daemon
2022-06-24 19:51 ` bugzilla-daemon
2022-06-27 16:20 ` bugzilla-daemon
2022-06-27 19:26 ` bugzilla-daemon
2022-06-27 23:48 ` bugzilla-daemon
2022-06-28 15:43 ` bugzilla-daemon
2022-06-28 21:12 ` bugzilla-daemon
2022-06-28 21:33 ` bugzilla-daemon
2022-06-28 21:33 ` bugzilla-daemon
2022-06-29 6:16 ` bugzilla-daemon
2022-06-29 13:00 ` bugzilla-daemon
2022-06-29 13:30 ` bugzilla-daemon
2022-06-29 13:40 ` bugzilla-daemon
2022-07-16 22:39 ` bugzilla-daemon
2022-07-16 22:41 ` bugzilla-daemon
2022-08-09 5:04 ` bugzilla-daemon
2022-08-09 18:53 ` bugzilla-daemon
2022-08-09 18:55 ` bugzilla-daemon
2022-08-09 19:07 ` bugzilla-daemon
2022-08-09 19:38 ` bugzilla-daemon
2022-08-25 8:37 ` bugzilla-daemon
2022-10-13 19:30 ` bugzilla-daemon
2022-10-13 20:39 ` bugzilla-daemon
2022-10-15 9:02 ` bugzilla-daemon
2022-10-20 14:13 ` bugzilla-daemon
2022-10-20 19:22 ` bugzilla-daemon
2022-10-20 21:59 ` bugzilla-daemon
2022-10-21 20:11 ` bugzilla-daemon
2022-10-24 21:19 ` bugzilla-daemon
2022-12-15 20:39 ` bugzilla-daemon [this message]
2022-12-15 20:40 ` bugzilla-daemon
2022-12-16 8:12 ` bugzilla-daemon
2023-02-03 11:25 ` bugzilla-daemon
2023-05-16 16:21 ` bugzilla-daemon
2023-05-16 17:02 ` bugzilla-daemon
2023-05-23 18:21 ` bugzilla-daemon
2023-05-26 8:28 ` bugzilla-daemon
2023-07-06 8:04 ` bugzilla-daemon
2023-07-06 14:51 ` bugzilla-daemon
2023-07-06 15:03 ` 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-216119-2300-9Ga2j5S42z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.