<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - "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."
href="https://bugs.freedesktop.org/show_bug.cgi?id=110142#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - "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."
href="https://bugs.freedesktop.org/show_bug.cgi?id=110142">bug 110142</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre><a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c713a461459202504050305242cd854bad57837c">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c713a461459202504050305242cd854bad57837c</a>
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)?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>