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: Sun, 10 Apr 2022 22:45:37 +0000 [thread overview]
Message-ID: <bug-215803-206035-M99EIgtj4A@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215803-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215803
Daniel Kolesa (linux@octaforge.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux@octaforge.org
--- Comment #2 from Daniel Kolesa (linux@octaforge.org) ---
This now hits 5.15.33. I noticed this when virtio-gpu failed to come up.
Commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/video/fbdev/core?h=linux-5.15.y&id=c894ac44786cfed383a6c6b20c1bfb12eb96018a
More detailed backtrace:
https://gist.github.com/q66/6ffc1bd18cf241e6ad894dc4409a2f72
This is also on a ppc64le system. However, I think this bug may not be ppc64
specific...
--
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-10 22:46 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 ` [Bug 215803] " bugzilla-daemon
2022-04-10 22:45 ` bugzilla-daemon [this message]
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-M99EIgtj4A@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 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.