All of lore.kernel.org
 help / color / mirror / Atom feed
From: Computer Enthusiastic <computer.enthusiastic@gmail.com>
To: Lyude Paul <lyude@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Ben Skeggs <bskeggs@redhat.com>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] nouveau lockdep deadlock report with 5.18-rc6
Date: Fri, 20 May 2022 13:46:44 +0200	[thread overview]
Message-ID: <CAHSpYy37aDAxGKR8ZbPC+C3bFxeyYqG8X1Px4h89MSxKLAak=A@mail.gmail.com> (raw)
In-Reply-To: <c703a49c57d77f4fcadba09a55fa926049dfe114.camel@redhat.com>

Hello,

Il giorno mer 18 mag 2022 alle ore 19:42 Lyude Paul <lyude@redhat.com>
ha scritto:
>
> Yeah I noticed this as well, I will try to bisect this the next change that I
> get
>
> On Tue, 2022-05-17 at 13:10 +0200, Hans de Goede wrote:
> > Hi All,
> > I just noticed the below lockdep possible deadlock report with a 5.18-rc6
> > kernel on a Dell Latitude E6430 laptop with the following nvidia GPU:
> > [..]
I hope not to be off topic in regard to kernel version, otherwise I
apologize in advance.

I would like to report that I'm constantly observing a similar, but
somehow different, lockdep warning (see [1]) in kernels 5.16 and 5.17
(compiled with lockdep debugging features) every time I activate the
Suspend To Ram (regardless if STR succeeds or not).

Thanks.

[1] https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/547#note_1361411

WARNING: multiple messages have this Message-ID (diff)
From: Computer Enthusiastic <computer.enthusiastic@gmail.com>
To: Lyude Paul <lyude@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Ben Skeggs <bskeggs@redhat.com>,
	Karol Herbst <kherbst@redhat.com>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: [Nouveau] nouveau lockdep deadlock report with 5.18-rc6
Date: Fri, 20 May 2022 13:46:44 +0200	[thread overview]
Message-ID: <CAHSpYy37aDAxGKR8ZbPC+C3bFxeyYqG8X1Px4h89MSxKLAak=A@mail.gmail.com> (raw)
In-Reply-To: <c703a49c57d77f4fcadba09a55fa926049dfe114.camel@redhat.com>

Hello,

Il giorno mer 18 mag 2022 alle ore 19:42 Lyude Paul <lyude@redhat.com>
ha scritto:
>
> Yeah I noticed this as well, I will try to bisect this the next change that I
> get
>
> On Tue, 2022-05-17 at 13:10 +0200, Hans de Goede wrote:
> > Hi All,
> > I just noticed the below lockdep possible deadlock report with a 5.18-rc6
> > kernel on a Dell Latitude E6430 laptop with the following nvidia GPU:
> > [..]
I hope not to be off topic in regard to kernel version, otherwise I
apologize in advance.

I would like to report that I'm constantly observing a similar, but
somehow different, lockdep warning (see [1]) in kernels 5.16 and 5.17
(compiled with lockdep debugging features) every time I activate the
Suspend To Ram (regardless if STR succeeds or not).

Thanks.

[1] https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/547#note_1361411

  reply	other threads:[~2022-05-20 11:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 11:10 [Nouveau] nouveau lockdep deadlock report with 5.18-rc6 Hans de Goede
2022-05-17 11:10 ` Hans de Goede
2022-05-17 22:24 ` [Nouveau] " Lyude Paul
2022-05-17 22:24   ` Lyude Paul
2022-05-18 17:42 ` [Nouveau] " Lyude Paul
2022-05-18 17:42   ` Lyude Paul
2022-05-20 11:46   ` Computer Enthusiastic [this message]
2022-05-20 11:46     ` [Nouveau] " Computer Enthusiastic
2022-05-23 19:59     ` Lyude Paul
2022-05-23 19:59       ` Lyude Paul

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='CAHSpYy37aDAxGKR8ZbPC+C3bFxeyYqG8X1Px4h89MSxKLAak=A@mail.gmail.com' \
    --to=computer.enthusiastic@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=lyude@redhat.com \
    --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 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.