dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105684] Loading amdgpu hits general protection fault: 0000 [#1] SMP NOPTI
Date: Wed, 25 Jul 2018 16:38:18 +0000	[thread overview]
Message-ID: <bug-105684-502-r5K3E0SfJB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105684-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105684

--- Comment #39 from Paul Menzel <pmenzel+bugs.freedesktop@molgen.mpg.de> ---
(In reply to jian-hong from comment #36)
> Created attachment 140806 [details]
> dmesg of 4.18.0-rc6
> 
> Tested with Linux 4.18.0-rc6 kernel.
> It seems the amdgpu module could be loaded correctly. I tried over 20 times.

I am still hitting this issue, though less often with 4.18-rc6. Could you
please attach your configuration, your build instructions? It seems independent
from the compiler (gcc version 6.3.0 20170516 (Debian
6.3.0-18+deb9u1endless2bem1)) as I use GCC 8.1.0 from Debian Sid/unstable.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1892 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-07-25 16:38 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  8:19 [Bug 105684] Loading amdgpu hits general protection fault: 0000 [#1] SMP NOPTI bugzilla-daemon
2018-03-22  8:22 ` bugzilla-daemon
2018-03-22  8:31 ` bugzilla-daemon
2018-03-22  9:08 ` bugzilla-daemon
2018-03-22 13:56 ` bugzilla-daemon
2018-03-23  2:58 ` bugzilla-daemon
2018-03-23  2:59 ` bugzilla-daemon
2018-03-23  3:00 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:01 ` bugzilla-daemon
2018-03-23  3:02 ` bugzilla-daemon
2018-03-23  3:02 ` bugzilla-daemon
2018-03-23  3:12 ` bugzilla-daemon
2018-03-27  6:39 ` bugzilla-daemon
2018-04-09  7:30 ` bugzilla-daemon
2018-04-17  7:56 ` bugzilla-daemon
2018-04-26  3:54 ` bugzilla-daemon
2018-05-09 18:49 ` bugzilla-daemon
2018-05-09 19:06 ` bugzilla-daemon
2018-05-10  7:10 ` bugzilla-daemon
2018-05-10  9:27 ` bugzilla-daemon
2018-05-10  9:50 ` bugzilla-daemon
2018-05-10 13:20 ` bugzilla-daemon
2018-05-11  3:20 ` bugzilla-daemon
2018-05-11 15:23 ` bugzilla-daemon
2018-05-11 15:51 ` bugzilla-daemon
2018-05-11 17:51 ` bugzilla-daemon
2018-05-12 20:30 ` bugzilla-daemon
2018-05-12 20:37 ` bugzilla-daemon
2018-05-14  3:00 ` bugzilla-daemon
2018-05-14  3:04 ` bugzilla-daemon
2018-07-18 13:47 ` bugzilla-daemon
2018-07-19 17:27 ` bugzilla-daemon
2018-07-20 14:57 ` bugzilla-daemon
2018-07-23 11:33 ` bugzilla-daemon
2018-07-24  9:27 ` bugzilla-daemon
2018-07-25 10:10 ` bugzilla-daemon
2018-07-25 14:13 ` bugzilla-daemon
2018-07-25 16:38 ` bugzilla-daemon [this message]
2018-07-26  8:21 ` bugzilla-daemon
2018-08-09  7:24 ` bugzilla-daemon
2018-08-09  9:56 ` bugzilla-daemon
2018-08-09 12:21 ` bugzilla-daemon
2019-04-29 15:24 ` bugzilla-daemon
2019-04-29 15:53 ` bugzilla-daemon
2019-05-29 13:36 ` bugzilla-daemon
2019-06-05 12:39 ` bugzilla-daemon
2019-11-19  8:33 ` 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-105684-502-r5K3E0SfJB@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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