From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Marc MERLIN <marc@merlins.org>,
linux-wireless@vger.kernel.org, ilw@linux.intel.com,
Tony Nguyen <anthony.l.nguyen@intel.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] Thinkpad P17 keep hanging in ipv6_addrconf addrconf_verify_work / netlink in 6.4 and 6.6
Date: Mon, 04 Dec 2023 22:17:50 +0100 [thread overview]
Message-ID: <95265243715c2f7cbb5ef94083d64e1a17d8ee04.camel@sipsolutions.net> (raw)
In-Reply-To: <20231204131615.26b57722@kernel.org>
On Mon, 2023-12-04 at 13:16 -0800, Jakub Kicinski wrote:
> > > > [ 363.945511] __mutex_lock.constprop.0+0x18b/0x291
> > > >
> > > > [ 363.945531] igc_resume+0x18b/0x1ca [igc 1a96e277f8878a2a3c9599226acd0eeb7de577b7]
> >
> > this is trying to acquire the RTNL, by looking at the code
> >
> > > > [ 363.945566] __rpm_callback+0x7a/0xe7
> > > > [ 363.945578] rpm_callback+0x35/0x64
> > > > [ 363.945587] ? __pfx_pci_pm_runtime_resume+0x40/0x40
> > > > [ 363.945592] rpm_resume+0x342/0x44a
> > > > [ 363.945600] ? __kmem_cache_alloc_node+0x123/0x154
> > > > [ 363.945614] __pm_runtime_resume+0x5a/0x7a
> > > > [ 363.945624] dev_ethtool+0x15a/0x24e7
> >
> > but this already holds it
> >
> > So looks like bug in the 'igc' driver wrt. runtime PM locking.
> >
So actually maybe it shouldn't be a bug there, I posted this:
https://patchwork.kernel.org/project/netdevbpf/patch/20231204200710.40c291e60cea.I2deb5804ef1739a2af307283d320ef7d82456494@changeid/
but I don't know this driver at all, and ethtool not that well ...
johannes
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-12-04 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231202171326.GB24486@merlins.org>
[not found] ` <20231204004003.GB29484@merlins.org>
[not found] ` <20231204073515.GA9208@merlins.org>
[not found] ` <69717129398d05b18df1c1300bfb41da268c52a0.camel@sipsolutions.net>
2023-12-04 21:16 ` [Intel-wired-lan] Thinkpad P17 keep hanging in ipv6_addrconf addrconf_verify_work / netlink in 6.4 and 6.6 Jakub Kicinski
2023-12-04 21:17 ` Johannes Berg [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=95265243715c2f7cbb5ef94083d64e1a17d8ee04.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anthony.l.nguyen@intel.com \
--cc=ilw@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marc@merlins.org \
--cc=netdev@vger.kernel.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