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: Fri, 23 Mar 2018 03:12:27 +0000 [thread overview]
Message-ID: <bug-105684-502-IcXoMetPtA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105684-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 650 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105684
--- Comment #13 from jian-hong@endlessm.com ---
Because system hangs up after loading amdgpu module, I cannot get dmesg
directly at that time.
Therefore, I load efi-pstore module to store the dmesg in efi before panic
happens.
The attachments:
"dmesg before loading amdgpu module": dmesg before loading amdgpu module
"Oops1~7 after loading amdgpu module": I gather the dmesg stored in efi-pstore,
which is during the panic happening. I concatenate them with the Oops number
and order by the part number.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1472 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
next prev parent reply other threads:[~2018-03-23 3:12 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 [this message]
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
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-IcXoMetPtA@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 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.