From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110142] "Oops: Kernel access of bad area sig 7" on Kernel 5.0.0 PPC64LE when loading amdgpu, xorg hangs after being unable to load after OS boots.
Date: Mon, 18 Mar 2019 10:03:26 +0000 [thread overview]
Message-ID: <bug-110142-502-yM3z60EhhQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110142-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110142
--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c713a461459202504050305242cd854bad57837c
seems the most likely candidate, it's the only significant change to
gmc_v9_0_late_init between 4.20 and 5.0.
I guess the problem is actually in gmc_v9_0_allocate_vm_inv_eng though. Peter,
what does
scripts/faddr2line drivers/gpu/drm/amd/amdgpu/amdgpu.ko
gmc_v9_0_late_init+0x114/0x500
say in the kernel build tree (in the state after building the binaries which
generated the attached dmesg output)?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1845 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 prev parent reply other threads:[~2019-03-18 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 2:52 [Bug 110142] "Oops: Kernel access of bad area sig 7" on Kernel 5.0.0 PPC64LE when loading amdgpu, xorg hangs after being unable to load after OS boots bugzilla-daemon
2019-03-18 2:33 ` bugzilla-daemon
2019-03-18 2:59 ` bugzilla-daemon
2019-03-18 10:03 ` bugzilla-daemon [this message]
2019-03-18 10:05 ` bugzilla-daemon
2019-03-19 3:21 ` bugzilla-daemon
2019-03-19 3:24 ` bugzilla-daemon
2019-03-19 8:50 ` bugzilla-daemon
2019-03-20 0:42 ` bugzilla-daemon
2019-03-20 2:01 ` bugzilla-daemon
2019-03-20 9:47 ` bugzilla-daemon
2019-03-22 1:40 ` 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-110142-502-yM3z60EhhQ@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;
as well as URLs for NNTP newsgroup(s).