From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1531] net/txgbe initialisation failed: EEPROM checksum is not valid.
Date: Wed, 04 Sep 2024 06:57:27 +0000 [thread overview]
Message-ID: <bug-1531-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1531
Bug ID: 1531
Summary: net/txgbe initialisation failed: EEPROM checksum is
not valid.
Product: DPDK
Version: 21.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: 626938192@qq.com
Target Milestone: ---
when build with gcc 10.3.1, start with error:
=================
EAL: Using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_txgbe (8088:1001) device: 0000:71:00.1 (socket 7)
eth_txgbe_dev_init(): The EEPROM checksum is not valid: -258
ethdev initialisation failed
EAL: Releasing PCI mapped resource for 0000:71:00.1
EAL: Calling pci_unmap_resource for 0000:71:00.1 at 0x7f58e57e0000
EAL: Calling pci_unmap_resource for 0000:71:00.1 at 0x7f74efc4e000
EAL: Requested device 0000:71:00.1 cannot be used
EAL: Bus (pci) probe failed.
TELEMETRY: No legacy callbacks, legacy socket not created
EAL: Error - exiting with code: 1
=================
but, when gcc version change to 4.8.5, it's ok.
DPDK: "21.11"
NIC: "Ethernet Controller RP1000 for 10GbE SFP+ 1001"
driver: "txgbe"
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3269 bytes --]
next reply other threads:[~2024-09-04 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:57 bugzilla [this message]
2025-03-26 14:10 ` [DPDK/ethdev Bug 1531] net/txgbe initialisation failed: EEPROM checksum is not valid bugzilla
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=bug-1531-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).