From: Vignesh Raman <vignesh.raman@collabora.com>
To: Helen Mae Koike Fornazier <helen.koike@collabora.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
daniels <daniels@collabora.com>, airlied <airlied@gmail.com>,
daniel <daniel@ffwll.ch>, robdclark <robdclark@gmail.com>,
"guilherme.gallo" <guilherme.gallo@collabora.com>,
"sergi.blanch.torne" <sergi.blanch.torne@collabora.com>,
"deborah.brouwer" <deborah.brouwer@collabora.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] drm/ci: enable lockdep detection
Date: Tue, 13 Aug 2024 10:56:48 +0530 [thread overview]
Message-ID: <0a3db7dc-4533-4111-bec9-35cc68e35d83@collabora.com> (raw)
In-Reply-To: <191483d05a3.129198f97500814.8001634600010504645@collabora.com>
Hi Helen,
On 13/08/24 01:47, Helen Mae Koike Fornazier wrote:
>
> Hi Vignesh,
>
> Thanks for your patch.
>
>
> ---- On Mon, 12 Aug 2024 08:20:28 -0300 Vignesh Raman wrote ---
>
> > We have enabled PROVE_LOCKING (which enables LOCKDEP) in drm-ci.
> > This will output warnings when kernel locking errors are encountered
> > and will continue executing tests. To detect if lockdep has been
> > triggered, check the debug_locks value in /proc/lockdep_stats after
> > the tests have run. When debug_locks is 0, it indicates that lockdep
> > has detected issues and turned itself off. So check this value and
> > exit with an error if lockdep is detected.
>
> Should we exit with an error? Or with a warning? (GitLab-CI supports that).
> Well, I guess it is serious enough.
I think we can exit with an error since we check the status at the end
of the tests.
>
> Should we also track on the xfail folder? So we can annotate those errors as well?
Do you mean reporting this error in expectation files?
> Did you have an entire pipeline with this? To see if everything is still green?
Yes. https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/62177711
This is a test branch in which I reverted a fix for the lockdep issue.
We see 'WARNING: bad unlock balance detected!' in logs and pipeline is
still green.
Regards,
Vignesh
>
> Helen
>
> >
> > Signed-off-by: Vignesh Raman vignesh.raman@collabora.com>
> > ---
> >
> > v1:
> > - Pipeline link to show lockdep_stats before and after tests,
> > https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1246721
> >
> > ---
> > drivers/gpu/drm/ci/igt_runner.sh | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/ci/igt_runner.sh b/drivers/gpu/drm/ci/igt_runner.sh
> > index f38836ec837c..d2c043cd8c6a 100755
> > --- a/drivers/gpu/drm/ci/igt_runner.sh
> > +++ b/drivers/gpu/drm/ci/igt_runner.sh
> > @@ -85,6 +85,17 @@ deqp-runner junit \
> > --limit 50 \
> > --template "See https://$CI_PROJECT_ROOT_NAMESPACE.pages.freedesktop.org/-/$CI_PROJECT_NAME/-/jobs/$CI_JOB_ID/artifacts/results/{{testcase}}.xml"
> >
> > +# Check if /proc/lockdep_stats exists
> > +if [ -f /proc/lockdep_stats ]; then
> > + # If debug_locks is 0, it indicates lockdep is detected and it turns itself off.
> > + debug_locks=$(grep 'debug_locks:' /proc/lockdep_stats | awk '{print $2}')
> > + if [ "$debug_locks" -eq 0 ]; then
> > + echo "LOCKDEP issue detected. Please check dmesg logs for more information."
> > + cat /proc/lockdep_stats
> > + ret=1
> > + fi
> > +fi
> > +
> > # Store the results also in the simpler format used by the runner in ChromeOS CI
> > #sed -r 's/(dmesg-warn|pass)/success/g' /results/results.txt > /results/results_simple.txt
> >
> > --
> > 2.43.0
> >
> >
next prev parent reply other threads:[~2024-08-13 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 11:20 Vignesh Raman
2024-08-12 20:17 ` Helen Mae Koike Fornazier
2024-08-13 5:26 ` Vignesh Raman [this message]
2024-08-13 20:14 ` Helen Mae Koike Fornazier
2024-08-14 9:42 ` Vignesh Raman
2024-08-14 17:41 ` Rob Clark
2024-09-13 12:19 ` Vignesh Raman
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=0a3db7dc-4533-4111-bec9-35cc68e35d83@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.koike@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®