From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@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: Sun, 17 Mar 2019 02:52:22 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0390787414=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 17C656E3E9
for ; Sun, 17 Mar 2019 02:52:23 +0000 (UTC)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0390787414==
Content-Type: multipart/alternative; boundary="15527911430.4DdAA1fC.13469"
Content-Transfer-Encoding: 7bit
--15527911430.4DdAA1fC.13469
Date: Sun, 17 Mar 2019 02:52:23 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D110142
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: JollyRoger@Mailfence.com
Created attachment 143700
--> https://bugs.freedesktop.org/attachment.cgi?id=3D143700&action=3Dedit
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 lo=
ad
amdgpu.=20
In the attached dmesg it looks like it starts around here:=20
[ 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. Th=
is
even causes Gentoo to hang on shutdown when / cannot be unmounted and requi=
res
a hard poweroff, even if I attempt to kill the process starting xfce4.=20
I tried it with both 5.0.0 and 5.0.2 on Gentoo, after upgrading from 4.20.1=
1,
and got similar results: when I enter "startxfce4" at the prompt, xorg hang=
s.=20
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 ha=
sn't
been truncated, that's all that's in it. Currently the only way to work aro=
und
this is for me to use an older kernel. I can post the dmesg from 4.20.11 (t=
he
last kernel I had that worked) if it's required.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15527911430.4DdAA1fC.13469
Date: Sun, 17 Mar 2019 02:52:23 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
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 aft=
er 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 |
JollyRoger@Mailfence.com
|
Created attachment 143700 [details]
dmesg output, kernel configuration file, lspci, and Xorg.0.log respectively.
Ahoy!
It looks like amdgpu is having an "Oops" when initializing with K=
ernels 5.0.0
and later on Linux PPC64 (Little Endian) platforms, right as it tries to lo=
ad
amdgpu.=20
In the attached dmesg it looks like it starts around here:=20
[ 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. Th=
is
even causes Gentoo to hang on shutdown when / cannot be unmounted and requi=
res
a hard poweroff, even if I attempt to kill the process starting xfce4.=20
I tried it with both 5.0.0 and 5.0.2 on Gentoo, after upgrading from 4.20.1=
1,
and got similar results: when I enter "startxfce4" at the prompt,=
xorg hangs.=20
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 ha=
sn't
been truncated, that's all that's in it. Currently the only way to work aro=
und
this is for me to use an older kernel. I can post the dmesg from 4.20.11 (t=
he
last kernel I had that worked) if it's required.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15527911430.4DdAA1fC.13469--
--===============0390787414==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============0390787414==--