All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207047] New: Crash after failed to pin userptr on amdgpu
Date: Tue, 31 Mar 2020 23:39:09 +0000	[thread overview]
Message-ID: <bug-207047-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 207047
           Summary: Crash after failed to pin userptr on amdgpu
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.5.13
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: me@artem.ist
        Regression: No

Created attachment 288139
  --> https://bugzilla.kernel.org/attachment.cgi?id=288139&action=edit
dmesg output since usermode crash that caused bug

When a user-mode program crashes while using amdgpu resources amdgpu fails to
pin userptr then segfaults in the GPU scheduler. This occured while attempting
to port a program to use Wayland and Vulkan on AMD Ryzen 3700X and AMD RX580
using unmodified amdgpu drivers.

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

             reply	other threads:[~2020-03-31 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 23:39 bugzilla-daemon [this message]
2020-04-01  6:27 ` [Bug 207047] Crash after failed to pin userptr on amdgpu bugzilla-daemon
2020-04-01 13:09 ` 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@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.