From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207047] Crash after failed to pin userptr on amdgpu
Date: Wed, 01 Apr 2020 06:27:23 +0000 [thread overview]
Message-ID: <bug-207047-2300-7rpldZH9RN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207047-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207047
bigbeeshane@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bigbeeshane@gmail.com
--- Comment #1 from bigbeeshane@gmail.com ---
Can you try on 5.6 kernel. Fixes for userptr where submitted and merged into
that release and I think are lined up for 5.5.14
--
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-04-01 6:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 23:39 [Bug 207047] New: Crash after failed to pin userptr on amdgpu bugzilla-daemon
2020-04-01 6:27 ` bugzilla-daemon [this message]
2020-04-01 13:09 ` [Bug 207047] " bugzilla-daemon
2020-04-02 15:30 ` 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-207047-2300-7rpldZH9RN@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