All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 214991] VC4 DRM waiting for flip down makes UI freeze a while with kernel 5.15
Date: Wed, 17 Nov 2021 06:58:15 +0000	[thread overview]
Message-ID: <bug-214991-2300-ddJZGwwHyA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214991-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214991

--- Comment #1 from Jian-Hong Pan (jhp@endlessos.org) ---
Created attachment 299603
  --> https://bugzilla.kernel.org/attachment.cgi?id=299603&action=edit
Full dmesg log with the patch series "drm/vc4: kms: Misc fixes for HVS commits"

Thanks to Maxime's reply from
https://lore.kernel.org/lkml/20211115113348.aylgkwrmaaomqrp4@gilmour/T/

So, I applied the patch series "drm/vc4: kms: Misc fixes for HVS commits" [1]
based on latest mainline kernel at commit 8ab774587903 ("Merge tag
'trace-v5.16-5' of
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace"), which
almost equals "tags/v5.16-rc1".

However, the system hangs and becomes dead at the kernel message:

[drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0

If I revert the patch series to the original mainline kernel, system can boot
up.

[1]:
https://lore.kernel.org/dri-devel/20211115113105.103275-1-maxime@cerno.tech/

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2021-11-17  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  3:47 [Bug 214991] New: VC4 DRM waiting for flip down makes UI freeze a while with kernel 5.15 bugzilla-daemon
2021-11-17  6:58 ` bugzilla-daemon [this message]
2021-11-18  6:51 ` [Bug 214991] " bugzilla-daemon
2022-04-22  5:45 ` bugzilla-daemon

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=bug-214991-2300-ddJZGwwHyA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /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.