All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208811] AMDGPU on-load null pointer dereference
Date: Tue, 04 Aug 2020 22:04:41 +0000	[thread overview]
Message-ID: <bug-208811-2300-8HLHaqtdgl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208811-2300@https.bugzilla.kernel.org/>

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

--- Comment #6 from R0b0t1 (sid@aeam.us) ---
To clarify, there is one machine with an APU (3700U) and one machine with a GPU
(RX 5700XT). I have a machine with an older Picasso APU that works on 5.4.48. I
am unsure if it is a regression, but I have messed with some settings to ensure
it is not a configuration issue. As I understand these devices work for most
users.

BIOS has no settings I can recognize as DMA protection. Both devices are ASUS
platforms, the desktop is a TUF X570-PLUS (WiFi) and the laptop is a ZenBook
UM433D.

-- 
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

  parent reply	other threads:[~2020-08-04 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 20:51 [Bug 208811] New: AMDGPU on-load null pointer dereference bugzilla-daemon
2020-08-04 21:17 ` [Bug 208811] " bugzilla-daemon
2020-08-04 21:36 ` bugzilla-daemon
2020-08-04 21:56 ` bugzilla-daemon
2020-08-04 21:57 ` bugzilla-daemon
2020-08-04 22:00 ` bugzilla-daemon
2020-08-04 22:04 ` bugzilla-daemon [this message]
2020-08-05 16:25 ` bugzilla-daemon
2020-08-05 17:22 ` bugzilla-daemon
2020-08-05 17:23 ` bugzilla-daemon
2020-08-05 19:44 ` 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-208811-2300-8HLHaqtdgl@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.