From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208647] persistent amdgpu: [mmhub] page faults
Date: Tue, 21 Jul 2020 15:22:12 +0000 [thread overview]
Message-ID: <bug-208647-2300-2MtFs4Q7iK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208647-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208647
Nicolai Hähnle (nhaehnle@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nhaehnle@gmail.com
--- Comment #3 from Nicolai Hähnle (nhaehnle@gmail.com) ---
Hi Alex, I asked Jay to report this because (1) the fact that there's a fault
during boot is suspicious and points in the direction of this being the
kernel's fault and (2) the fact that it's an *mmhub* fault is even more
suspicious.
Certainly this seems to happen without Mesa video encode/decode activity, so it
can't really be Mesa's (or any graphics driver's) fault.
Someone suggested that audio support also goes through mmhub and that it may be
related. I have no idea if that's true.
--
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:[~2020-07-21 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 14:35 [Bug 208647] New: persistent amdgpu: [mmhub] page faults bugzilla-daemon
2020-07-21 15:13 ` [Bug 208647] " bugzilla-daemon
2020-07-21 15:15 ` bugzilla-daemon
2020-07-21 15:22 ` bugzilla-daemon [this message]
2020-07-21 15:26 ` bugzilla-daemon
2020-07-21 15:34 ` bugzilla-daemon
2020-09-28 15:17 ` bugzilla-daemon
2020-09-28 15:18 ` 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-208647-2300-2MtFs4Q7iK@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