From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205585] [Regression] [amdgpu] AMD Vega 64 GPU invalid access and EEH under load
Date: Fri, 29 Nov 2019 21:24:08 +0000 [thread overview]
Message-ID: <bug-205585-2300-ndwsX41i5E@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205585-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205585
--- Comment #6 from Timothy Pearson (tpearson@raptorengineering.com) ---
Yes, my fault, sorry about that -- different box, unbeknownst to me had a
different GPU (note to self, check lspci next time before decoding trace).
To top it off, this particular fault seems to be related to a faulty GPU --
letting it cool overnight fixes the problems temporarily. I still need to
verify the Vega is failing on 5.4.0, as one of the patches leading up to 5.4.0
resolved the similar software lockup I had been seeing on this Polaris card.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-29 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 1:18 [Bug 205585] New: [Regression] [amdgpu] AMD Vega 64 GPU invalid access and EEH under load bugzilla-daemon
2019-11-20 15:21 ` [Bug 205585] " bugzilla-daemon
2019-11-20 20:26 ` bugzilla-daemon
2019-11-29 7:45 ` bugzilla-daemon
2019-11-29 8:25 ` bugzilla-daemon
2019-11-29 20:16 ` bugzilla-daemon
2019-11-29 21:24 ` bugzilla-daemon [this message]
2019-11-30 0:36 ` 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-205585-2300-ndwsX41i5E@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.