* net-next: bnxt_en failing to load
@ 2024-05-03 9:01 Breno Leitao
2024-05-03 17:10 ` Michael Chan
0 siblings, 1 reply; 2+ messages in thread
From: Breno Leitao @ 2024-05-03 9:01 UTC (permalink / raw)
To: michael.chan, ajit.khaparde, kalesh-anakkur.purayil, edwin.peer; +Cc: netdev
Hello,
I am testing net-next, and my 50Gb Ethernet is failing to work, looking
deep I found that bnxt_en module is failing to load. This is happening
for a while (~week) now. Is this a known problem?
This is the problem I see:
bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Able to reserve only 0 out of 9 requested RX rings
bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Unable to reserve tx rings
bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): 2nd rings reservation failed.
bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Not enough rings available.
bnxt_en 0000:02:00.0: probe with driver bnxt_en failed with error -12
This is the device I am testing with:
# lspci -v -s 02:00.0
02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57452 NetXtreme-E 10Gb/25Gb/40Gb/50Gb Ethernet (rev 01)
Subsystem: Broadcom Inc. and subsidiaries Device 4520
Flags: fast devsel, IRQ 16
Memory at 38003fe00000 (64-bit, prefetchable) [size=64K]
Memory at 38003fd00000 (64-bit, prefetchable) [size=1M]
Memory at 38003fe10000 (64-bit, prefetchable) [size=8K]
Expansion ROM at aad00000 [disabled] [size=512K]
Capabilities: [48] Power Management version 3
Capabilities: [50] Vital Product Data
Capabilities: [58] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [a0] MSI-X: Enable- Count=32 Masked-
Capabilities: [ac] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Device Serial Number b0-26-28-ff-fe-a5-36-50
Capabilities: [150] Power Budgeting <?>
Capabilities: [160] Virtual Channel
Capabilities: [180] Vendor Specific Information: ID=0000 Rev=0 Len=020 <?>
Capabilities: [1b0] Latency Tolerance Reporting
Capabilities: [1b8] Alternative Routing-ID Interpretation (ARI)
Capabilities: [240] L1 PM Substates
Capabilities: [300] Secondary PCI Express
If this is not a known problem, I can try to bissect if this is useful.
Thanks
Breno
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: net-next: bnxt_en failing to load
2024-05-03 9:01 net-next: bnxt_en failing to load Breno Leitao
@ 2024-05-03 17:10 ` Michael Chan
0 siblings, 0 replies; 2+ messages in thread
From: Michael Chan @ 2024-05-03 17:10 UTC (permalink / raw)
To: Breno Leitao; +Cc: ajit.khaparde, kalesh-anakkur.purayil, edwin.peer, netdev
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Fri, May 3, 2024 at 2:01 AM Breno Leitao <leitao@debian.org> wrote:
>
> Hello,
>
> I am testing net-next, and my 50Gb Ethernet is failing to work, looking
> deep I found that bnxt_en module is failing to load. This is happening
> for a while (~week) now. Is this a known problem?
This patch posted yesterday should fix it:
https://lore.kernel.org/netdev/20240502203757.3761827-1-dw@davidwei.uk/
Thanks.
>
> This is the problem I see:
>
> bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Able to reserve only 0 out of 9 requested RX rings
> bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Unable to reserve tx rings
> bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): 2nd rings reservation failed.
> bnxt_en 0000:02:00.0 (unnamed net_device) (uninitialized): Not enough rings available.
> bnxt_en 0000:02:00.0: probe with driver bnxt_en failed with error -12
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-05-03 17:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-05-03 9:01 net-next: bnxt_en failing to load Breno Leitao
2024-05-03 17:10 ` Michael Chan
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).