All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Jücker" <martin.juecker@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, dri-devel@lists.freedesktop.org
Cc: "Joonyoung Shim" <jy0922.shim@samsung.com>,
	"David Airlie" <airlied@linux.ie>,
	"Seung-Woo Kim" <sw0312.kim@samsung.com>,
	"Kyungmin Park" <kyungmin.park@samsung.com>,
	"Martin Jücker" <martin.juecker@gmail.com>
Subject: Re: Exynos vblank timeout issue
Date: Sun, 22 May 2022 12:06:39 +0200	[thread overview]
Message-ID: <20220522100639.GA191106@adroid> (raw)
In-Reply-To: <6aa0b632-674d-d9ca-2ba9-cab497aa1f37@kernel.org>

On Sun, May 22, 2022 at 09:45:51AM +0200, Krzysztof Kozlowski wrote:
> On 22/05/2022 02:02, Martin Jücker wrote:
> > Hello,
> > 
> > I'm trying to get Android 12 up and running on my Galaxy Note 10.1 which
> > is based on Exynos 4412 with a Mali GPU. For Android 11, I had no issues
> > with graphics but after upgrading and building Android 12, I'm getting a
> > vblank wait timeout shortly after starting the device setup, which in
> > turn leads to my display turning black and SurfaceFlinger hanging. This
> > can be reliably reproduced after every reboot, so much so that it's
> > basically always on the exact same step of the setup.
> > 
> > I'm using the following setup:
> > 
> > * 5.10.101 Android Common Kernel with some patches to get
> > the Note 10.1 up and running
> 
> It's Android kernel, so not upstream. It is perfectly fine to use
> downstream kernels, but with the issues you also go to downstream folks.
> I have no clue what Android did to Exynos.

Hi Krzysztof,

indeed, that was my mistake. Should have done that on mainline first.

I rebased some patches on top of v5.17.9 and tried again, same result.
There are no Android patches in there, only p4note related things. You
can have a look here: 

https://github.com/Viciouss/linux/commits/v5.17.9-android

The behaviour is exactly the same, as soon as I try to advance in the
setup process, it suddenly turns the screen all black.

Here is the warning again, just in case there are any differences.

[   77.651495] ------------[ cut here ]------------
[   77.651527] WARNING: CPU: 2 PID: 8 at
../drivers/gpu/drm/drm_atomic_helper.c:1530
drm_atomic_helper_wait_for_vblanks.part.1+0x2b0/0x2b4
[   77.651593] [CRTC:49:crtc-0] vblank wait timed out
[   77.651608] Modules linked in: s5p_mfc s5p_jpeg v4l2_mem2mem
videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common
rfcomm kheaders hidp hci_uart cpufreq_userspace cpufreq_powersave
cpufreq_conservative btbcm brcmfmac brcmutil bnep bluetooth atmel_mxt_ts
[   77.651789] CPU: 2 PID: 8 Comm: kworker/u8:0 Not tainted 5.17.9+ #3
[   77.651813] Hardware name: Samsung Exynos (Flattened Device Tree)
[   77.651828] Workqueue: events_unbound commit_work
[   77.651858] Backtrace: 
[   77.651874] dump_backtrace from show_stack+0x20/0x24
[   77.651915] r7:c071097c r6:00000000 r5:c10ec66c r4:600f0013
[   77.651926] show_stack from dump_stack_lvl+0x48/0x54
[   77.651958] dump_stack_lvl from dump_stack+0x18/0x1c
[   77.651986] r5:c113dcf4 r4:c1d51e04
[   77.651996] dump_stack from __warn+0x18c/0x190
[   77.652030] __warn from warn_slowpath_fmt+0x80/0xbc
[   77.652070] r9:00000009 r8:c071097c r7:000005fa r6:c113dcf4
r5:c1d8cb40 r4:c113e338
[   77.652081] warn_slowpath_fmt from
drm_atomic_helper_wait_for_vblanks.part.1+0x2b0/0x2b4
[   77.652123] r9:00000001 r8:00000000 r7:00000000 r6:00000000
r5:00000000 r4:c398c800
[   77.652135] drm_atomic_helper_wait_for_vblanks.part.1 from
drm_atomic_helper_commit_tail_rpm+0x6c/0x7c
[   77.652175] r10:c14cce68 r9:c1c2a005 r8:00000000 r7:0e3f351d
r6:00000012 r5:c398c000
[   77.652188] r4:d42943c0
[   77.652197] drm_atomic_helper_commit_tail_rpm from
commit_tail+0xb8/0x1d8
[   77.652228] r5:00000000 r4:d42943c0
[   77.652238] commit_tail from commit_work+0x1c/0x20
[   77.652274] r10:c1518d20 r9:c1c2a005 r8:00000000 r7:c1c2a000
r6:c1c0a800 r5:c1c08a00
[   77.652287] r4:d42943ec
[   77.652297] commit_work from process_one_work+0x1b0/0x528
[   77.652324] process_one_work from worker_thread+0x54/0x4d8
[   77.652356] r10:c1c0a800 r9:00000088 r8:c1403d00 r7:c1c0a81c
r6:c1c08a18 r5:c1c0a800
[   77.652368] r4:c1c08a00
[   77.652378] worker_thread from kthread+0x104/0x134
[   77.652419] r10:00000000 r9:c1d43e5c r8:c1d05880 r7:c1d8cb40
r6:c1c08a00 r5:c015530c
[   77.652432] r4:c1d05700
[   77.652441] kthread from ret_from_fork+0x14/0x2c
[   77.652468] Exception stack(0xc1d51fb0 to 0xc1d51ff8)
[   77.652488] 1fa0:                                     00000000
00000000 00000000 00000000
[   77.652509] 1fc0: 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000
[   77.652528] 1fe0: 00000000 00000000 00000000 00000000 00000013
00000000
[   77.652550] r9:00000000 r8:00000000 r7:00000000 r6:00000000
r5:c015da78 r4:c1d05700
[   77.652561] ---[ end trace 0000000000000000 ]---

Kind Regards
Martin

> 
> Best regards,
> Krzysztof

  reply	other threads:[~2022-05-23  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  0:02 Exynos vblank timeout issue Martin Jücker
2022-05-22  7:45 ` Krzysztof Kozlowski
2022-05-22 10:06   ` Martin Jücker [this message]
2022-05-26 23:34     ` Martin Jücker
2022-06-04  4:05       ` Inki Dae
2022-06-04 11:05         ` Martin Jücker
2022-06-22  3:27           ` Inki Dae

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=20220522100639.GA191106@adroid \
    --to=martin.juecker@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jy0922.shim@samsung.com \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=sw0312.kim@samsung.com \
    /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.