Bug 215803
Summary: | ppc64le(P9): BUG: Kernel NULL pointer dereference on read at 0x00000060 NIP: do_remove_conflicting_framebuffers+0x184/0x1d0 | ||
---|---|---|---|
Product: | Platform Specific/Hardware | Reporter: | Zorro Lang (zlang) |
Component: | PPC-64 | Assignee: | platform_ppc-64 |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | linux, michael |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.18-rc1 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | kernel .config file |
Description
Zorro Lang
2022-04-05 04:37:02 UTC
Created attachment 300697 [details]
kernel .config file
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... It does not panic in my case though; I merely get stuck with the offb framebuffer console instead of it switching modes to the right thing Also, just to be clear, reverting the commit I linked above does fix the problem for me. Here is a patch you can quickly test: https://gist.github.com/q66/da01b4baecfdc24cd8fa3253d4e7f05a This was reported to the patch author here: https://lore.kernel.org/all/YkHXO6LGHAN0p1pq@debian/ And there is a fix here: https://patchwork.freedesktop.org/patch/480648/ The fix was merged into v5.18-rc2 as: https://git.kernel.org/torvalds/c/0f525289ff0ddeb380813bd81e0f9bdaaa1c9078 |