From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215803] ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0
Date: Tue, 05 Apr 2022 04:37:40 +0000 [thread overview]
Message-ID: <bug-215803-206035-JphAY5Y1xZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215803-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215803
--- Comment #1 from Zorro Lang (zlang@redhat.com) ---
Created attachment 300697
--> https://bugzilla.kernel.org/attachment.cgi?id=300697&action=edit
kernel .config file
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-04-05 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 4:37 [Bug 215803] New: ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0 bugzilla-daemon
2022-04-05 4:37 ` bugzilla-daemon [this message]
2022-04-10 22:45 ` [Bug 215803] " bugzilla-daemon
2022-04-10 22:46 ` bugzilla-daemon
2022-04-10 22:47 ` bugzilla-daemon
2022-04-12 7:07 ` bugzilla-daemon
2022-05-23 23:53 ` bugzilla-daemon
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-215803-206035-JphAY5Y1xZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 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).