From: Tim Joneson <tim_joneson@pm.me>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: eth: igb: RTNL assertion failed on igb_resume
Date: Fri, 02 Dec 2022 18:58:59 +0000 [thread overview]
Message-ID: <7dHNwI6WnTACGVS6Gl7-ip2gk15x8DePuQBiGIdYJxrTjtS-tEq0zYMcC-3STel7LU-tDewibuZKzOMCo_Yuftwe29JMnqnszgDJ6KVoI58=@pm.me> (raw)
Hello,
My igb driver fails on an RTNL assertion when resuming, see below dmesg and lspci excerpts. I searched the lists and the trace seems very similar to an issue in alx that was solved earlier:
https://lore.kernel.org/netdev/20220928181236.1053043-1-kuba@kernel.org/T/
Is this list the correct place to report this or should I file a report in BugZilla?
Best regards,
Tim
RTNL: assertion failed at net/core/dev.c (2891)
WARNING: CPU: 1 PID: 277 at net/core/dev.c:2891 netif_set_real_num_tx_queues+0x1a3/0x1c0
Modules linked in: qrtr bluetooth jitterentropy_rng sha512_ssse3 sha512_generic drbg ansi_cprng ecdh_generic rfkill ecc binfmt_misc nft_nat intel_rapl_msr intel_rapl_common nft_masq intel_pmc_core_pltdrv intel_pmc_core nft_chain_nat nf_nat nls_ascii nls_cp437 vfat nft_limit fat nfnetlink_log x86_pkg_temp_thermal i915 nft_log mei_hdcp mei_wdt intel_powerclamp kvm_intel drm_buddy drm_display_helper kvm cec irqbypass rc_core rapl intel_cstate intel_uncore ttm pcspkr iTCO_wdt mei_me ee1004 intel_pmc_bxt iTCO_vendor_support cdc_acm mei drm_kms_helper nft_ct intel_pch_thermal nf_conntrack ie31200_edac nf_defrag_ipv6 nf_defrag_ipv4 button acpi_pad evdev sg nf_tables ftsteutates watchdog nfnetlink coretemp msr drm fuse efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic zstd_compress efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod
dm_mod hid_generic sd_mod t10_pi usbhid crc64_rocksoft_generic hid crc64_rocksoft crc_t10dif crct10dif_generic crc64 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel ahci libahci e1000e igb xhci_pci xhci_hcd i2c_algo_bit dca aesni_intel crypto_simd libata cryptd i2c_i801 i2c_smbus ptp usbcore scsi_mod pps_core scsi_common wmi usb_common video
CPU: 1 PID: 277 Comm: kworker/1:2 Not tainted 6.0.0-4-amd64 #1 Debian 6.0.8-1
Hardware name: FUJITSU /D3644-B1, BIOS V5.0.0.13 R1.26.0 for D3644-B1x 03/08/2021
Workqueue: pm pm_runtime_work
RIP: 0010:netif_set_real_num_tx_queues+0x1a3/0x1c0
Code: 00 b4 25 01 00 0f 85 d9 fe ff ff ba 4b 0b 00 00 48 c7 c6 fc 94 7e a6 48 c7 c7 a0 b3 75 a6 c6 05 e0 b3 25 01 01 e8 17 03 1f 00 <0f> 0b e9 b3 fe ff ff b8 ea ff ff ff e9 8f fe ff ff 66 66 2e 0f 1f
RSP: 0018:ffffbadc40997cf0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffff9fc78894c000 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffffa677ed52 RDI: 00000000ffffffff
RBP: 0000000000000004 R08: 0000000000000000 R09: ffffbadc40997b78
R10: 0000000000000003 R11: ffffffffa6ed22a8 R12: 0000000000000001
R13: 0000000000000004 R14: ffff9fc70a32d1f0 R15: ffff9fc78894c000
FS: 0000000000000000(0000) GS:ffff9fca5e480000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdad97641dc CR3: 0000000016810006 CR4: 00000000003706e0
Call Trace:
<TASK>
__igb_open+0x3f4/0x660 [igb]
__igb_resume+0x136/0x240 [igb]
? __pci_enable_wake+0x7e/0xb0
? pci_pm_restore_noirq+0xc0/0xc0
__rpm_callback+0x41/0x170
rpm_callback+0x35/0x70
? pci_pm_restore_noirq+0xc0/0xc0
rpm_resume+0x5e5/0x810
? _raw_spin_unlock_irq+0x1b/0x35
? pcie_pme_work_fn+0x1c4/0x2b0
pm_runtime_work+0x6c/0xa0
process_one_work+0x1c4/0x380
worker_thread+0x4d/0x380
? _raw_spin_lock_irqsave+0x23/0x50
? rescuer_thread+0x3a0/0x3a0
kthread+0xe6/0x110
? kthread_complete_and_exit+0x20/0x20
ret_from_fork+0x1f/0x30
</TASK>
---[ end trace 0000000000000000 ]---
Device:
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 9
Memory at 8f900000 (32-bit, non-prefetchable) [size=1M]
Memory at 8fa00000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at 8f800000 [disabled] [size=1M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 6c-b3-11-ff-ff-52-95-01
Capabilities: [1a0] Transaction Processing Hints
Kernel driver in use: igb
Kernel modules: igb
reply other threads:[~2022-12-02 18:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='7dHNwI6WnTACGVS6Gl7-ip2gk15x8DePuQBiGIdYJxrTjtS-tEq0zYMcC-3STel7LU-tDewibuZKzOMCo_Yuftwe29JMnqnszgDJ6KVoI58=@pm.me' \
--to=tim_joneson@pm.me \
--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 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.