All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Luca Coelho <luciano.coelho@intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi Lockdep warning with 5.12-rc4 on 8086:02f0 (Comet Lake PCH-LP CNVi WiFi)
Date: Thu, 15 Apr 2021 10:31:12 -0600	[thread overview]
Message-ID: <CAJCQCtQosH3Pc2O4yc7n8eTdAcF=7AiJYxh+y1tuEE2kxMGfrg@mail.gmail.com> (raw)
In-Reply-To: <10faeb84-1232-f179-a687-35a148fb7a0d@redhat.com>

On Thu, Apr 15, 2021 at 6:04 AM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Hi Chris,
>
> On 4/13/21 11:38 PM, Chris Murphy wrote:

> > Looks like this:
> > https://lore.kernel.org/linux-wireless/nycvar.YFH.7.76.2103021125430.12405@cbobk.fhfr.pm/
> >
> > I tested that patch on rc6 and it worked so far.
>
> That patch has been added to rc7, so I tested rc7 and rc7 still has the lockdep splat in dmesg.

I'm running 5.12.0-0.rc7.189.fc35.x86_64+debug and don't have the lockdep splat.

[   12.502108] iwlwifi 0000:6c:00.0: Detected Intel(R) Dual Band
Wireless AC 8260, REV=0x204

> But good news, the issue is my wifi card uses iwl_pcie_gen2_enqueue_hcmd where as the
> patch you linked to fixes iwl_pcie_enqueue_hcmd . Applying the same changes to the
> iwl_pcie_gen2_enqueue_hcmd function also fixes lockdep complaining for me.

OK super.


-- 
Chris Murphy

      reply	other threads:[~2021-04-15 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 20:55 iwlwifi Lockdep warning with 5.12-rc4 on 8086:02f0 (Comet Lake PCH-LP CNVi WiFi) Hans de Goede
2021-04-13 21:38 ` Chris Murphy
2021-04-13 21:42   ` Chris Murphy
2021-04-15 12:04   ` Hans de Goede
2021-04-15 16:31     ` Chris Murphy [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='CAJCQCtQosH3Pc2O4yc7n8eTdAcF=7AiJYxh+y1tuEE2kxMGfrg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.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 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.