From: Mike Galbraith <efault@gmx.de>
To: "Christian König" <christian.koenig@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: nouveau <nouveau@lists.freedesktop.org>,
Ben Skeggs <bskeggs@redhat.com>, Dave Airlie <airlied@redhat.com>
Subject: Re: [Nouveau] [bisected] Re: nouveau: lockdep cli->mutex vs reservation_ww_class_mutex deadlock report
Date: Mon, 15 Mar 2021 11:36:30 +0100 [thread overview]
Message-ID: <d434abd7029f0b7978dfbc0c1f5db3979812fc35.camel@gmx.de> (raw)
In-Reply-To: <d1d64307bf834d263bd57be84ca701eb2bc34ca2.camel@gmx.de>
On Mon, 2021-03-15 at 09:53 +0100, Mike Galbraith wrote:
> On Mon, 2021-03-15 at 09:05 +0100, Christian König wrote:
> > Hi Mike,
> >
> > I'm pretty sure your bisection is a bit off.
>
> (huh?) Ah crap, yup, the spew from hell you plugged obliterated the
> lockdep gripe I was grepping for as go/nogo, and off into lala land we
> go.. twice.. whee :) Oh well, the ordering gripe is clear enough
> without a whodoneit.
However, after having rummaged around, two minutes with gitk was enough
for 551620f2 to flash neon red, and one build later confirm it.
-Mike
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2021-03-15 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:58 [Nouveau] nouveau: lockdep cli->mutex vs reservation_ww_class_mutex deadlock report Mike Galbraith
2021-03-14 4:48 ` [Nouveau] [bisected] " Mike Galbraith
2021-03-15 8:05 ` Christian König
2021-03-15 8:53 ` Mike Galbraith
2021-03-15 10:36 ` Mike Galbraith [this message]
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=d434abd7029f0b7978dfbc0c1f5db3979812fc35.camel@gmx.de \
--to=efault@gmx.de \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@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 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).