All of lore.kernel.org
 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:41:09 +0000	[thread overview]
Message-ID: <bug-194731-2300-nGSgkiNbxu@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 #3 from Janpieter Sollie (janpieter.sollie@dommel.be) ---
(In reply to Michel Dänzer from comment #1)
> (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?

no, then the kernel simply reboots. I'm sorry for using the amd pro module, but
native amd doesn't tell me anything:

modprobe amdgpu & cat /proc/kmsg gives this as its last output:
<6>[  252.228071] amdgpu 0000:41:00.0: fence driver on ring 0 use gpu addr
0x0000000040000010, cpu addr 0xffff881831cc6010
<6>[  252.228253] amdgpu 0000:41:00.0: fence driver on ring 1 use gpu addr
0x0000000040000020, cpu addr 0xffff881831cc6020
<6>[  252.228601] amdgpu 0000:41:00.0: fence driver on ring 2 use gpu addr
0x0000000040000030, cpu addr 0xffff881831cc6030
<6>[  252.228768] amdgpu 0000:41:00.0: fence driver on ring 3 use gpu addr
0x0000000040000040, cpu addr 0xffff881831cc6040
<6>[  252.228939] amdgpu 0000:41:00.0: fence driver on ring 4 use gpu addr
0x0000000040000050, cpu addr 0xffff881831cc6050
<6>[  252.229092] [drm] probing gen 2 caps for device 1002:5a1f = 31cd02/0
<6>[  252.229096] [drm] PCIE gen 2 link speeds already enabled
<6>[  252.458236] [drm] ring test on 0 succeeded in 7 usecs
<6>[  252.460247] [drm] ring test on 1 succeeded in 1 usecs
<6>[  252.460256] [drm] ring test on 2 succeeded in 1 usecs
<6>[  252.460265] [drm] ring test on 3 succeeded in 3 usecs
<6>[  252.460272] [drm] ring test on 4 succeeded in 3 usecs
but this is probably related to another bug: 194559

-- 
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:[~2017-02-28  9:41 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 ` [Bug 194731] " bugzilla-daemon
2017-02-28  9:33 ` bugzilla-daemon
2017-02-28  9:41 ` bugzilla-daemon [this message]
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-nGSgkiNbxu@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.