From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111685] [Polaris 30] [Bisected] Kernel BUG during boot when amdgpu.dpm=0
Date: Sat, 14 Sep 2019 09:18:25 +0000 [thread overview]
Message-ID: <bug-111685-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1201 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111685
Bug ID: 111685
Summary: [Polaris 30] [Bisected] Kernel BUG during boot when
amdgpu.dpm=0
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: omar.squircleart@gmail.com
Created attachment 145359
--> https://bugs.freedesktop.org/attachment.cgi?id=145359&action=edit
Bisect log
To reproduce, pass the parameter amdgpu.dpm=0 to a kernel v5.2 or higher. The
kernel will hang at boot. v5.1 boots correctly.
I have bisected the kernel between v5.1 and v5.2, the bisect log is attached
below.
The last three lines from the log are as follow, the full log is attached
below:
kernel: BUG: unable to handle page fault for address: ffff91fe41bdf5f8
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x0000) - not-present page
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2604 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-09-14 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-14 9:18 bugzilla-daemon [this message]
2019-09-14 9:19 ` [Bug 111685] [Polaris 30] [Bisected] Kernel BUG during boot when amdgpu.dpm=0 bugzilla-daemon
2019-11-19 9:51 ` 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-111685-502@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.