Re: bnxt_en: BCM57414: 0000:c4:00.0 (unnamed net_device) (uninitialized): Device requests max timeout of 100 seconds, may trigger hung task watchdog

[Michael Chan]

On Thu, Feb 12, 2026 at 10:30 AM Paul Menzel <pmenzel@xxxxxxxxxxxxx> wrote:

> There seem to be two problems:
>
> 1.  It’s logged before the name is known.

Yes, this information is received from the first FW response when
probing the device.  So the netdev name is not known yet and the PCI
device number is used instead.

> 2.  The timeout of 100 s seems higher than the one you expect, which is
> 60 s [1].

I believe the latest FW should use 60 seconds, but there are older FW
in the field that use 100 seconds.

>
>      > But 60 seconds is the timeout on most production FW and cannot be
>      > reduced further.
>
> It looks like you addressed some of this in commit 0fcad44a86bd
> (bnxt_en: Change FW message timeout warning) and commit 8ff617513996
> (bnxt_en: hide CONFIG_DETECT_HUNG_TASK specific code), merged in Linux
> v6.16-rc1. Both were not backported to the 6.12 LTS series. Also, it
> looks like they do not address the first issue.
>
> As we do have `CONFIG_DETECT_HUNG_TASK` unset, we would not see the
> warning with the patches.
>
>      $ grep HUNG_TASK /boot/config-6.12.49.mx64.487
>      # CONFIG_DETECT_HUNG_TASK is not set
>
> I’d recommend to have both commits backported. Will you do this, or
> should I contact the stable folks?

If AUTOSEL has not selected these patches for stable, I can request to
have these backported.  I agree that the warning is annoying.  I will
do it later today.

Thanks.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature