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
