https://bugs.freedesktop.org/show_bug.cgi?id=110142
Bug ID: 110142
Summary: "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.
Product: DRI
Version: unspecified
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: jollyro...@mailfence.com
Created attachment 143700
--> https://bugs.freedesktop.org/attachment.cgi?id=143700&action=edit
dmesg output, kernel configuration file, lspci, and Xorg.0.log respectively.
Ahoy!
It looks like amdgpu is having an "Oops" when initializing with Kernels 5.0.0
and later on Linux PPC64 (Little Endian) platforms, right as it tries to load
amdgpu.
In the attached dmesg it looks like it starts around here:
[ 34.247578] Oops: Kernel access of bad area, sig: 7 [#1]
I came to notice this bug when I upgraded the kernel from 4.20.11 on Gentoo and
4.20.1 on Debian and rebooted, then trying to bring up xfce4 would hang. This
even causes Gentoo to hang on shutdown when / cannot be unmounted and requires
a hard poweroff, even if I attempt to kill the process starting xfce4.
I tried it with both 5.0.0 and 5.0.2 on Gentoo, after upgrading from 4.20.11,
and got similar results: when I enter "startxfce4" at the prompt, xorg hangs.
I'm attaching my dmesg, kernel configuration file, the output of lspci, and the
xorg.0.log in that order. The xorg.0.log file is only 48 lines long, and hasn't
been truncated, that's all that's in it. Currently the only way to work around
this is for me to use an older kernel. I can post the dmesg from 4.20.11 (the
last kernel I had that worked) if it's required.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
