Hello,
Please have a look at
https://doc.dpdk.org/guides/contributing/patches.html before sending a
new revision.
On Wed, 3 Sept 2025 at 16:24, Thanushree Sreerama
<thanushree.sreer...@nokia.com> wrote:
>
> From: "Thanushree.Sreerama" <thanushree.sreer...@nokia.com>
>
> Add proper EAGAIN handling for the device setup by retrying the device reset
>
> Issue:
> asc-0a Disp_0[18237]: EAL: Unable to reset device! Error: 11 (Resource
> temporarily unavailable)
> asc-0a Disp_0[18237]: EAL: 0000:f4:02.3 setup device failed
> asc-0a Disp_0[18237]: EAL: Requested device 0000:f4:02.3 cannot be used
We are missing the conditions where such an error is hit (iow, why do
we get a EBUSY here).
Please describe the functionnal impact.
Please explain how those timeout/retry values were chosen and how they
are enough for the issue you faced.
>
> Caused due to:
> 92d847a35e1 ("Revert "driver core: Fix uevent_show() vs driver detach race"")
This sha1 does not belong to DPDK public repo.
I also see the patch could not be applied in the CI, so you'll have to
make sure this patch is rebased on main.
> Cc: sta...@dpdk.org
If you want this fix to be backported, point at the commit where the
issue was introduced with a Fixes:.
> Change-Id: Ic3ae8701fccdbf1e8e2a575d48e707b4c58e939a
Please remove this marker, this does not make sense for upstream contributions.
> Signed-off-by: Thanushree Sreerama <thanushree.sreer...@nokia.com>
And please register to the mailing list, otherwise your patch waits in
the moderation queue until some dpdk admin looks at it.
Thanks.
--
David Marchand
