From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201727] Hardware Error reported on Ryzen 5 2500U
Date: Mon, 19 Nov 2018 11:40:42 +0000 [thread overview]
Message-ID: <bug-201727-2300-ZxqE6zCGBq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201727-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201727
--- Comment #6 from Christian König (christian.koenig@amd.com) ---
Currently GTT is only used for PD/PT as last resort when there is so few stolen
memory assigned to the APU that it won't work at all otherwise.
The faulting address looks suspicious like we miss to handle an error code
correctly somewhere and instead use the value as DMA address.
What is your BIOS setting for the stolen VRAM?
--
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:[~2018-11-19 11:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 9:25 [Bug 201727] New: Hardware Error reported on Ryzen 5 2500U bugzilla-daemon
2018-11-19 9:26 ` [Bug 201727] " bugzilla-daemon
2018-11-19 9:26 ` bugzilla-daemon
2018-11-19 9:27 ` bugzilla-daemon
2018-11-19 10:58 ` bugzilla-daemon
2018-11-19 11:03 ` bugzilla-daemon
2018-11-19 11:40 ` bugzilla-daemon [this message]
2018-11-19 11:47 ` bugzilla-daemon
2018-11-19 11:48 ` bugzilla-daemon
2018-11-19 12:50 ` bugzilla-daemon
2018-11-19 16:31 ` bugzilla-daemon
2018-12-09 21:01 ` bugzilla-daemon
2018-12-17 5:43 ` bugzilla-daemon
2018-12-29 21:06 ` bugzilla-daemon
2019-01-05 1:20 ` bugzilla-daemon
2019-01-07 4:30 ` bugzilla-daemon
2019-01-18 20:43 ` bugzilla-daemon
2019-01-24 12:53 ` 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-201727-2300-ZxqE6zCGBq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox