Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Nuno Gonçalves" <nunojpg@gmail.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	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: Tue, 12 Nov 2024 09:11:31 +0100	[thread overview]
Message-ID: <832483d5-db64-4195-a86c-028eff033fbe@suse.de> (raw)
In-Reply-To: <CAEXMXLRDDC+PB7S9VtqyMr1MUPPb7NYngwu4gcn9-K2kyHm3rQ@mail.gmail.com>

Hi


Am 11.11.24 um 20:06 schrieb Nuno Gonçalves:
>
>
> On Mon, Nov 11, 2024, 14:37 Thomas Zimmermann <tzimmermann@suse.de> wrote:
>
>     Hi
>
>
>     Am 11.11.24 um 14:42 schrieb Nuno Gonçalves:
>     > On Mon, Nov 11, 2024 at 1:22 PM Thomas Zimmermann
>     <tzimmermann@suse.de> wrote:
>     >> 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.
>     > Issue was present since 5ab91447aa13b8b98bc11f5326f33500b0ee2c48 and
>     > tested until 6.12-rc3.
>     > Is there any suggestion on how to dig down?
>
>     Do you have a stack trace of this problem?
>
>
> No. I need to build kernel with debug?

Isn't there an error message in the output of dmesg?

Or maybe can you save the whole output of dmesg after a crash and attach 
the file to an email?

In the original bug report, you mentioned that you often get an error. 
But not 'always'?

Do you have a reproducer for the problem? Such as a very simple program 
that triggers the bug.

>
>
>
>     Which hardware platform is affected?
>
>
> ARM64 with ili9225 and display size 220, 176. It also
> happens in another board with a different tinydrm driver and size 320,
> 240.

I meant, which board or CPU. ARM64/Aarch64 is really just a very broad 
term describing the system.

Best regards
Thomas


-- 
--
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)


  parent reply	other threads:[~2024-11-12  8:11 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
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 [this message]
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=832483d5-db64-4195-a86c-028eff033fbe@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