All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 218900] amdgpu: Fatal error during GPU init
Date: Tue, 25 Jun 2024 17:10:06 +0000	[thread overview]
Message-ID: <bug-218900-2300-JWLmtRUWX2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218900-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218900

Jean-Denis Girard (jd.girard@sysnux.pf) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jd.girard@sysnux.pf

--- Comment #17 from Jean-Denis Girard (jd.girard@sysnux.pf) ---
I seem to have a similar problem on 6.10-rc5 after suspend. I get a black
screen on resume.

[  269.157149] amdgpu 0000:02:00.0: amdgpu: reserve 0x400000 from 0xf41f800000
for PSP TMR
[  269.159956] iommu ivhd0: AMD-Vi: Event logged [ILLEGAL_DEV_TABLE_ENTRY
device=0000:02:00.0 pasid=0x00000 address=0x131400000 flags=0x0180]
[  269.159960] AMD-Vi: DTE[0]: 6190000000000003
[  269.159962] AMD-Vi: DTE[1]: 00001001049e000b
[  269.159963] AMD-Vi: DTE[2]: 200000013c610013
[  269.159963] AMD-Vi: DTE[3]: 0000000000000000
[  269.160104] amdgpu 0000:02:00.0: amdgpu: failed to load ucode SDMA0(0x1) 
[  269.160108] amdgpu 0000:02:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6)
failed and response status is (0xF)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-06-25 17:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 14:52 [Bug 218900] New: amdgpu: Fatal error during GPU init bugzilla-daemon
2024-05-27 15:08 ` [Bug 218900] " bugzilla-daemon
2024-05-27 15:10 ` bugzilla-daemon
2024-05-27 15:22 ` bugzilla-daemon
2024-05-27 15:46 ` bugzilla-daemon
2024-05-28 15:45 ` bugzilla-daemon
2024-05-28 18:01 ` bugzilla-daemon
2024-05-29  6:15 ` bugzilla-daemon
2024-05-29  6:16 ` bugzilla-daemon
2024-05-29  7:11 ` bugzilla-daemon
2024-05-29  7:42 ` bugzilla-daemon
2024-05-29 10:41 ` bugzilla-daemon
2024-05-29 11:39 ` bugzilla-daemon
2024-05-29 12:41 ` bugzilla-daemon
2024-05-29 12:43 ` bugzilla-daemon
2024-05-29 16:14 ` bugzilla-daemon
2024-05-29 16:17 ` bugzilla-daemon
2024-05-29 21:26 ` bugzilla-daemon
2024-05-30  6:20 ` bugzilla-daemon
2024-06-06 12:26 ` bugzilla-daemon
2024-06-07 15:18 ` bugzilla-daemon
2024-06-10 15:02 ` bugzilla-daemon
2024-06-25 17:10 ` bugzilla-daemon [this message]
2024-06-25 17:11 ` bugzilla-daemon
2024-06-25 17:14 ` bugzilla-daemon
2024-06-25 17:55 ` bugzilla-daemon
2024-06-27 16:00 ` bugzilla-daemon
2024-06-28  9:13 ` 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-218900-2300-JWLmtRUWX2@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.