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, 07 Mar 2017 08:10:41 +0000	[thread overview]
Message-ID: <bug-194731-2300-05NkXIxW3G@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 #7 from Janpieter Sollie (janpieter.sollie@dommel.be) ---
hello, I have some other news about this bug (if anyone is still interested):
I rewrote the amdgpu-pro driver, as the amdgpu driver seems more complex, and I
took one step forward! this is my solution:
- unload the Cape Verde card with echo 1 > /proc/sys/pci/0000:41:00.0/remove
- load the driver, the driver loading finishes successfully
- rescan the pci bus: echo 1 > /sys/bus/pci/rescan
then the behaviour of amdgpu and amdgpu-pro are the same: the system reboots
after initialisation, even if I order it not to restart on panic.
can somebody tell me where I should look for Cape Verde initialization code in
the in-tree driver? I may be able to fix the initialization bug.

Thank you

-- 
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-03-07  8:10 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
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 [this message]
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-05NkXIxW3G@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.