From: Daniel Stone <daniel@fooishbar.org>
To: Helen Koike <helen.koike@collabora.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Maira Canal <mairacanal@riseup.net>,
Arthur Grillo <arthurgrillo@riseup.net>,
Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>,
Melissa Wen <melissa.srw@gmail.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
David Airlie <airlied@gmail.com>,
DRI <dri-devel@lists.freedesktop.org>,
syzkaller@googlegroups.com, LKML <linux-kernel@vger.kernel.org>,
Hillf Danton <hdanton@sina.com>,
Sanan Hasanov <Sanan.Hasanov@ucf.edu>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Stone <daniels@collabora.com>,
David Heidelberg <david.heidelberg@collabora.com>,
Vignesh Raman <vignesh.raman@collabora.com>
Subject: Re: drm/vkms: deadlock between dev->event_lock and timer
Date: Tue, 19 Sep 2023 07:38:52 +0100 [thread overview]
Message-ID: <CAPj87rNAv_ACFJF_PbWnJjjmSrSOvfVuvOHq9mmza5w=t+BF0w@mail.gmail.com> (raw)
In-Reply-To: <2784f5e8-ebf4-a000-509e-415e14390e23@collabora.com>
On Mon, 18 Sept 2023 at 23:02, Helen Koike <helen.koike@collabora.com> wrote:
> On 14/09/2023 05:12, Daniel Vetter wrote:
> > Also yes how that landed without anyone running lockdep is ... not good. I
> > guess we need a lockdep enabled drm ci target that runs vkms tests asap
> > :-)
>
> btw, I just executed a draft version of vkms targed on the ci, we do get
> the warning:
>
> https://gitlab.freedesktop.org/helen.fornazier/linux/-/jobs/49156305#L623
>
> I'm just not sure if tests would fail (since it is a warning) and it has
> a chance to be ignored if people don't look at the logs (unless if igt
> already handles that).
Hmm, dmesg-warn is already a separate igt test status. I guess it just
needs to be handled explicitly.
> I still need to do some adjustments (it seems the tests is hanging
> somewhere and we got a timeout) but we should have vkms in drm ci soon.
Might be due to the locking explosion? The kernels should probably
have soft-lockup detection enabled as well as lockdep.
Cheers,
Daniel
next prev parent reply other threads:[~2023-09-19 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230913110709.6684-1-hdanton@sina.com>
2023-09-13 14:21 ` drm/vkms: deadlock between dev->event_lock and timer Tetsuo Handa
2023-09-13 16:47 ` Linus Torvalds
2023-09-13 21:08 ` Thomas Gleixner
2023-09-14 6:33 ` Tetsuo Handa
2023-09-14 8:12 ` Daniel Vetter
2023-09-18 22:02 ` Helen Koike
2023-09-19 6:38 ` Daniel Stone [this message]
2023-09-13 14:30 ` BUG: soft lockup in smp_call_function Tetsuo Handa
[not found] ` <20230914122134.6783-1-hdanton@sina.com>
2023-09-14 13:13 ` Tetsuo Handa
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='CAPj87rNAv_ACFJF_PbWnJjjmSrSOvfVuvOHq9mmza5w=t+BF0w@mail.gmail.com' \
--to=daniel@fooishbar.org \
--cc=Sanan.Hasanov@ucf.edu \
--cc=airlied@gmail.com \
--cc=arthurgrillo@riseup.net \
--cc=daniels@collabora.com \
--cc=david.heidelberg@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=hdanton@sina.com \
--cc=helen.koike@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vignesh.raman@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;
as well as URLs for NNTP newsgroup(s).