dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* [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.
@ 2019-03-17  2:52 bugzilla-daemon
  2019-03-18  2:33 ` bugzilla-daemon
                   ` (10 more replies)
  0 siblings, 11 replies; 12+ messages in thread
From: bugzilla-daemon @ 2019-03-17  2:52 UTC (permalink / raw)
  To: dri-devel


[-- Attachment #1.1: Type: text/plain, Size: 2031 bytes --]

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: JollyRoger@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.

[-- Attachment #1.2: Type: text/html, Size: 3659 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

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2019-03-22  1:40 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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).