[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5ed77c9-89ad-4de6-b46b-5865378e029a@gmx.de>
Date: Mon, 2 Sep 2024 22:18:55 +0200
From: Helge Deller <deller@....de>
To: "V, Narasimhan" <Narasimhan.V@....com>,
Thomas Zimmermann <tzimmermann@...e.de>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Daniel Vetter <daniel@...ll.ch>,
"linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
open list <linux-kernel@...r.kernel.org>,
"linux@...ssschuh.net" <linux@...ssschuh.net>, Borislav Petkov <bp@...en8.de>
Subject: Re: WARNING: CPU: 0 PID: 8 at drivers/video/fbdev/core/fbmem.c:467
unregister_framebuffer+0x45/0x160
On 9/2/24 20:56, V, Narasimhan wrote:
> From: Thomas Zimmermann <tzimmermann@...e.de>
>>>> Seeing the following warning and bug on boot with linux-next-20240829
>>>>
>>>> WARNING: CPU: 0 PID: 8 at drivers/video/fbdev/core/fbmem.c:467 unregister_framebuffer+0x45/0x160
>>>> BUG: kernel NULL pointer dereference, address: 0000000000000000
>
>> Does it work if you revert one of these commits?
>
>> c2fe0480cd77 ("fbdev/efifb: Use devm_register_framebuffer()")
>
>
> Reverting this commit fixes the issue.
Good.
>> For the latter, there might be a fix at
>
>> https://patchwork.freedesktop.org/patch/611902/?series=138008&rev=1
Current fbdev git tree and for-next series have this newer patch already.
I expect that the issue is already resolved with there, but it would
be good if you could test.
Helge
Powered by blists - more mailing lists