Issues with DPDK ICE PMD

[David Marchand]

Hello,

On Tue, 12 May 2026 at 09:58, Mahan, Patrick <patrick.mahan at hpe.com> wrote:
>
> Morning all,
>
> If this is not the appropriate group then please let me know the proper mailing list.

Adding Intel maintainers in the loop, probably the best to answer your
questions.

>
> I am trying to debug an issue with the ICE PMD in DPDK v24.11.0 in a linux environment (YOCTO scarthgap, 6.6.35 kernel).
>
> We are bringing up a new platform based on the Intel Atom C5315 which has the ICE driver (E822-L) and I am seeing the following error during the call to rte_eal_init() -
>
> ICE_INIT: ice_dev_init(): Failed to read device serial number

Afaik, reading the device serial number only affects which ddp binary is loaded.
If reading this SN fails, there is a fallback, and the device
initialisation should still succeed.

>
> Now, we have been using the ICE PMD successfully on another platform (E810-XXV) with the AMD EPYC 9354P.

Do you mean that the ICE port init fails on the Atom server?
My understanding is that the port would be functional, regardless of
the SN, and even if there is some error log.
Maybe this log message should be lower to warning level?


> After some initial research via google-fu, it seems that the ICE device on the Atom processor is missing its serial number.
>
> On the AMD processor, if I issue lspci -vs <pci-addr> | grep “Serial”, I see -
>
> admin at BRXXXX:~# lspci -vs 0000:46:00.0 | grep "Serial"
>       Capabilities: [150] Device Serial Number 30-3e-a7-ff-ff-02-71-04
>
> While on the Intel ATOM platform, I don’t -
>
> admin at BRYYYY-2:~# lspci -vs f4:00.0 | grep -i Serial
> admin at BRYYYY-2:~#
>
> But I cannot find any info on having the ICE PMD ignore the serial number.  One of my HW contacts suggested that it was embedded on the ATOM, though I am a bit skeptical of that suggestion.
>
> The ICE PMD documentation yields nothing and before I decide to dive into the ICE PMD internals, I thought I would ask the DPDK community first, to see if someone has already seen this issue.  I don’t see any currently open bugs on this with DPDK.


-- 
David Marchand