dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194731] drm general protection fault in drm_atomic_init
Date: Tue, 28 Feb 2017 09:26:17 +0000	[thread overview]
Message-ID: <bug-194731-2300-ouYr42uXbp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194731-2300@https.bugzilla.kernel.org/>

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

--- Comment #1 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Janpieter Sollie from comment #0)
> I modified the drm_atomic.c a bit to be more verbose.  the drm_init calls a
> general protection fault when allocating my second GPU(does it work this
> way?) of the amdgpu module.

[...]

> [   77.950445] Modules linked in: amdkfd amdgpu(O+) amdttm(O) amdkcl(O)

amdttm and amdkcl indicate that you're using an out-of-tree version of the
amdgpu kernel module, possibly from an amdgpu-pro release? Does the problem
also occur with the in-tree amdgpu driver?

-- 
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:[~2017-02-28  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  8:20 [Bug 194731] New: drm general protection fault in drm_atomic_init bugzilla-daemon
2017-02-28  9:26 ` bugzilla-daemon [this message]
2017-02-28  9:33 ` [Bug 194731] " bugzilla-daemon
2017-02-28  9:41 ` bugzilla-daemon
2017-02-28  9:42 ` bugzilla-daemon
2017-02-28 10:10 ` bugzilla-daemon
2017-03-01  1:07 ` bugzilla-daemon
2017-03-01  5:00 ` bugzilla-daemon
2017-03-07  8:10 ` bugzilla-daemon
2020-01-09 11:13 ` 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-194731-2300-ouYr42uXbp@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;
as well as URLs for NNTP newsgroup(s).