Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Nuno Gonçalves" <nunojpg@gmail.com>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
	dri-devel@lists.freedesktop.org,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Framebuffer <linux-fbdev@vger.kernel.org>
Subject: Re: drm/fbdev-dma: regression
Date: Mon, 11 Nov 2024 14:22:12 +0100	[thread overview]
Message-ID: <b4d28b98-a85c-4095-9c1b-8ebdfa13861c@suse.de> (raw)
In-Reply-To: <d2562174-eebe-4462-9a9a-03936b3bcf89@leemhuis.info>

Hi


Am 11.11.24 um 12:51 schrieb Thorsten Leemhuis:
> [CCing a few more lists]
>
> On 21.10.24 15:03, Nuno Gonçalves wrote:
>> Since 5ab91447aa13b8b98bc11f5326f33500b0ee2c48 and still happening in
>> master, I often get a kernel crash, either a "Unable to handle kernel
>> NULL pointer dereference at virtual address" or "Unable to handle
>> kernel paging request at virtual address".
>>
>> This happens in ARM64 with ili9225 and display size 220, 176. It also
>> happens in another board with a different tinydrm driver and size 320,
>> 240.
>>
>> I've reported in 2022 a bug (that you fixed, thanks!), where it was
>> related to screen size causing non alignment of scanlines and pages.
>> I've not investigated further this time as I was not doing any driver
>> development, but let me know if I can do any further testing.
> Thx for the report. I might be missing something, but from here it looks
> like nothing happened. So allow me to ask:
>
> What's the status? Did anyone look into this? Is this sill happening?

I briefly looked into this bug report some time ago.

The patch in question changes the whole memory management of the 
affected code. It's also noteworthy that most of it has been reworked 
for the upcoming v6.12. Maybe this already fixed the problem. Kernel 
v6.11-rc7 added commit 5a498d4d06d6 ("drm/fbdev-dma: Only install 
deferred I/O if necessary"), which possibly fixes the problem as well.

But there's no explicit fix for this problem and I have not seen any 
other related reports. Any further information is welcome.

Best regards
Thomas

>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> If I did something stupid, please tell me, as explained on that page.
>
> #regzbot poke

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)


  reply	other threads:[~2024-11-11 13:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220621104617.8817-1-tzimmermann@suse.de>
     [not found] ` <CAEXMXLR55DziAMbv_+2hmLeH-jP96pmit6nhs6siB22cpQFr9w@mail.gmail.com>
2024-11-11 11:51   ` drm/fbdev-dma: regression Thorsten Leemhuis
2024-11-11 13:22     ` Thomas Zimmermann [this message]
2024-11-11 13:42       ` Nuno Gonçalves
2024-11-11 14:37         ` Thomas Zimmermann
     [not found]           ` <CAEXMXLRDDC+PB7S9VtqyMr1MUPPb7NYngwu4gcn9-K2kyHm3rQ@mail.gmail.com>
2024-11-12  8:11             ` Thomas Zimmermann
2024-11-28 15:47         ` Thomas Zimmermann
2024-11-28 23:37           ` Nuno Gonçalves
2024-12-02 11:18             ` Thomas Zimmermann
2024-12-07 22:36               ` Nuno Gonçalves
2024-12-09 13:43                 ` Thomas Zimmermann
2024-12-09 13:56                   ` Nuno Gonçalves
2024-12-11  9:07                     ` Thomas Zimmermann
2025-02-26 22:57                       ` Nuno Gonçalves
2025-02-27  9:01                         ` Thomas Zimmermann

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=b4d28b98-a85c-4095-9c1b-8ebdfa13861c@suse.de \
    --to=tzimmermann@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nunojpg@gmail.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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