Fedora Account System
Red Hat Associate
Red Hat Customer
1. Please describe the problem: Intel X710/X557-AT built in NIC is not recognized by system since upstream kernel commit eec37961a56aa4f3fe1c33ffd48eec7d1bb0c009. This leads to system not having any NIC avaialble. 2. What is the Version-Release number of the kernel: 6.13 and up 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : 6.12 works any kernel 6.13 after upstream commit eec37961a56aa4f3fe1c33ffd48eec7d1bb0c009 doesn't. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install any kernel 6.13+ after upstream commit eec37961a56aa4f3fe1c33ffd48eec7d1bb0c009 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes 6. Are you running any modules that not shipped with directly Fedora's kernel?: No 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. kernel: module_64: libie: doesn't contain __patchable_function_entries. kernel: ------------[ cut here ]------------ kernel: WARNING: CPU: 89 PID: 1341 at mm/vmalloc.c:3778 __vmalloc_node_range_noprof+0x354/0x3c0 kernel: module_64: libie: doesn't contain __patchable_function_entries. kernel: Modules linked in: enclosure aes_gcm_p10_crypto at24(+) kernel: execmem: unable to allocate memory kernel: scsi_transport_sas mtd crypto_simd cryptd i2c_opal rtc_opal vmx_crypto opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler loop zram lz4hc_compress lz> kernel: CPU: 89 UID: 0 PID: 1341 Comm: (udev-worker) Not tainted 6.14.0-0.rc6.0fed89a961ea.50.test.fc43.ppc64le #1 kernel: Hardware name: CSE-829U POWER9 0x4e1202 opal:skiboot-v6.0.7 PowerNV kernel: NIP: c0000000006ba5e4 LR: c0000000007acd14 CTR: 0000000000000000 kernel: REGS: c00000003e92b2e0 TRAP: 0700 Not tainted (6.14.0-0.rc6.0fed89a961ea.50.test.fc43.ppc64le) kernel: MSR: 9000000002029033 <SF,HV,VEC,EE,ME,IR,DR,RI,LE> CR: 24228224 XER: 20040000 kernel: CFAR: c0000000006ba2b8 IRQMASK: 0 GPR00: c00000000038ef50 c00000003e92b580 c00000000255aa00 0000000000000000 GPR04: 0000000000000001 c008000000000000 c00a000000000000 0000000000002cc0 GPR08: 800000000000018e 0000000000000100 ffffffffffffffff 0000000000008000 GPR12: c000000001ec0a70 c0002007ff693300 0000000000000000 0000000000000000 GPR16: 0000000000000000 0000000000000000 0000000000000000 c00000000038ef50 GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 GPR24: 00007fffb91d0958 c00800000b6f0680 c00000003e92b990 0000000000000000 GPR28: 0000000000000000 c00000003e92b990 c00800000b6f0500 0000000000000000 kernel: NIP [c0000000006ba5e4] __vmalloc_node_range_noprof+0x354/0x3c0 kernel: LR [c0000000007acd14] execmem_alloc+0x84/0x170 kernel: Call Trace: kernel: [c00000003e92b580] [c000000003ca7400] __UNIQUE_ID_ddebug514.52+0x0/0x38 (unreliable) kernel: [c00000003e92b670] [c00800000b6f0000] 0xc00800000b6f0000 kernel: [c00000003e92b710] [c00000000038ef50] move_module+0x390/0x610 kernel: [c00000003e92b7d0] [c0000000003958ac] layout_and_allocate.isra.0+0x15c/0x270 kernel: [c00000003e92b840] [c000000000395cfc] load_module+0xfc/0xab0 kernel: module_64: libie: doesn't contain __patchable_function_entries. kernel: module_64: libie: doesn't contain __patchable_function_entries. kernel: [c00000003e92b930] [c0000000003968e0] __do_sys_init_module+0x230/0x280 kernel: [c00000003e92ba60] [c000000000032980] system_call_exception+0x160/0x310 kernel: execmem: unable to allocate memory kernel: execmem: unable to allocate memory kernel: kernel: [c00000003e92be50] [c00000000000d05c] system_call_vectored_common+0x15c/0x2ec kernel: at24 7-0052: supply vcc not found, using dummy regulator kernel: --- interrupt: 3000 at 0x7fffb8f672f0 kernel: tpm_i2c_nuvoton 3-0057: VID: 1050 DID: FE RID: 04 kernel: NIP: 00007fffb8f672f0 LR: 00007fffb8f672f0 CTR: 0000000000000000 kernel: REGS: c00000003e92be80 TRAP: 3000 Not tainted (6.14.0-0.rc6.0fed89a961ea.50.test.fc43.ppc64le) kernel: MSR: 900000000000f033 <SF,HV,EE,PR,FP,ME,IR,DR,RI,LE> CR: 4422844e XER: 00000000 kernel: IRQMASK: 0 GPR00: 0000000000000080 00007ffff65cd890 00007fffb9066d00 000000012c9404a0 GPR04: 0000000000001c0e 00007fffb91d0958 000000000000000a 000000012c92e300 GPR08: 000000012c830010 0000000000000000 0000000000000000 0000000000000000 GPR12: 0000000000000000 00007fffb9893a20 0000000020000000 0000000000020000 GPR16: 0000000000000000 0000000000000000 0000000100718608 00007ffff65cde38 GPR20: 0000000000000000 000000012c90d800 0000000000000007 000000012c8b0d00 GPR24: 0000000000000000 000000012c937550 0000000020000000 000000012c93b010 GPR28: 00007fffb91d0958 0000000000020000 000000012c937550 0000000000100000 kernel: at24 7-0052: 256 byte spd EEPROM, read-only kernel: NIP [00007fffb8f672f0] 0x7fffb8f672f0 kernel: LR [00007fffb8f672f0] 0x7fffb8f672f0 kernel: --- interrupt: 3000 kernel: Code: kernel: at24 7-0054: supply vcc not found, using dummy regulator kernel: 81610008 ea61ff98 eb61ffd8 7d708120 4e800020 60000000 60420000 2834ffff 7e9aa378 4181fd68 3f400001 4bfffd60 <0fe00000> 4bfffe28 3ca2ff81 7f66db78 kernel: at24 7-0054: 256 byte spd EEPROM, read-only kernel: ---[ end trace 0000000000000000 ]--- kernel: execmem: unable to allocate memory Reproducible: Always
Created attachment 2081858 [details] dmesg
URL for the offending commit is https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eec37961a56aa4f3fe1c33ffd48eec7d1bb0c009 The NIC is normally served by the i40e driver. I am thinking about taking this to the linuxppc-devel list as the commit is very ppc specific.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2025-February/thread.html#281048 and https://lists.ozlabs.org/pipermail/linuxppc-dev/2025-March/thread.html#282537 so we should be good soon
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update.