All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Krishna Manikandan <mkrishn@codeaurora.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Jonathan Marek <jonathan@marek.ca>,
	"open list:DRM DRIVER FOR MSM ADRENO GPU"
	<freedreno@lists.freedesktop.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Sean Paul <sean@poorly.run>
Subject: Re: Reboot crash at msm_atomic_commit_tail
Date: Tue, 19 Jan 2021 08:43:14 -0800	[thread overview]
Message-ID: <CAF6AEGvxdLCLDfhnY9M4-R6U3CvH6eqJBUs=xB6ycDQf2F=JOw@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGuEeaSMyjVQXV-2WAJ6FamrqYc=TF8_EFQo27r+X8_gdg@mail.gmail.com>

forgot to CC Krishna

On Tue, Jan 19, 2021 at 8:34 AM Rob Clark <robdclark@gmail.com> wrote:
>
> On Mon, Jan 18, 2021 at 11:00 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Mon, Jan 18, 2021 at 11:00 PM Fabio Estevam <festevam@gmail.com> wrote:
> > >
> > > On Mon, Jan 18, 2021 at 6:44 PM Fabio Estevam <festevam@gmail.com> wrote:
> > > >
> > > > Adding some more folks in case anyone has any suggestions to fix this
> > > > reboot hang.
> > >
> > > Not sure if this is a valid fix, but the change below makes reboot
> > > works correctly.
> > >
> > > kmscube still works.
> > >
> > > --- a/drivers/gpu/drm/msm/msm_atomic.c
> > > +++ b/drivers/gpu/drm/msm/msm_atomic.c
> > > @@ -207,8 +207,12 @@ void msm_atomic_commit_tail(struct drm_atomic_state *state)
> > >         struct msm_kms *kms = priv->kms;
> > >         struct drm_crtc *async_crtc = NULL;
> > >         unsigned crtc_mask = get_crtc_mask(state);
> > > -       bool async = kms->funcs->vsync_time &&
> > > -                       can_do_async(state, &async_crtc);
> > > +       bool async;
> > > +
> > > +       if (!kms)
> > > +               return;
> >
> > That looks a bit like a hack papering over the real issue.
> >
> > From your report it sounds like earlier kernels worked, did you
> > attempt bisecting? Also for regressions put regressions into the
> > subject, it's the magic work that gets much more attention.
>
> the root issue is how are we doing KMS stuff on imx (where drm/msm is
> only used for gpu).. which I think is this commit:
>
> ----------
> commit 9d5cbf5fe46e350715389d89d0c350d83289a102
> Author:     Krishna Manikandan <mkrishn@codeaurora.org>
> AuthorDate: Mon Jun 1 16:33:22 2020 +0530
> Commit:     Rob Clark <robdclark@chromium.org>
> CommitDate: Tue Aug 18 08:09:01 2020 -0700
>
>     drm/msm: add shutdown support for display platform_driver
>
>     Define shutdown callback for display drm driver,
>     so as to disable all the CRTCS when shutdown
>     notification is received by the driver.
>
>     This change will turn off the timing engine so
>     that no display transactions are requested
>     while mmu translations are getting disabled
>     during reboot sequence.
>
>     Signed-off-by: Krishna Manikandan <mkrishn@codeaurora.org>
>
>     Changes in v2:
>             - Remove NULL check from msm_pdev_shutdown (Stephen Boyd)
>             - Change commit text to reflect when this issue
>               was uncovered (Sai Prakash Ranjan)
>
>     Signed-off-by: Rob Clark <robdclark@chromium.org>
> ----------
>
> I suppose we should do the drm_atomic_helper_shutdown() conditionally?
>  Or the helper should bail if there is no kms?
>
> BR,
> -R
>
> > -Daniel
> >
> > > +
> > > +       async = kms->funcs->vsync_time && can_do_async(state, &async_crtc);
> > >
> > >         trace_msm_atomic_commit_tail_start(async, crtc_mask);
> > >
> > > Any comments?
> > >
> > > Thanks
> > > _______________________________________________
> > > dri-devel mailing list
> > > dri-devel@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> >
> >
> >
> > --
> > Daniel Vetter
> > Software Engineer, Intel Corporation
> > http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-01-19 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 20:07 Reboot crash at msm_atomic_commit_tail Fabio Estevam
2021-01-18 21:44 ` Fabio Estevam
2021-01-18 22:00   ` Fabio Estevam
2021-01-19  7:00     ` Daniel Vetter
2021-01-19 16:34       ` Rob Clark
2021-01-19 16:43         ` Rob Clark [this message]
2021-01-19 17:35           ` Fabio Estevam
2021-01-19 17:49             ` Daniel Vetter

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='CAF6AEGvxdLCLDfhnY9M4-R6U3CvH6eqJBUs=xB6ycDQf2F=JOw@mail.gmail.com' \
    --to=robdclark@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=jonathan@marek.ca \
    --cc=kernel@pengutronix.de \
    --cc=mkrishn@codeaurora.org \
    --cc=sean@poorly.run \
    /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.