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: Fri, 22 Mar 2019 01:40:46 +0000 [thread overview]
Message-ID: <bug-110142-502-XF8qgYmJ44@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110142-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110142
Peter Easton <JollyRoger@Mailfence.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #11 from Peter Easton <JollyRoger@Mailfence.com> ---
Yay, glad to hear!
I'm going to change it to fixed then, if that's okay with you guys?
Thank you so much for the help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2443 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
prev parent reply other threads:[~2019-03-22 1:40 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
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 message]
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-XF8qgYmJ44@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.