Project

General

Profile

Actions

Regression #14569

closed

``bnxt(4)`` driver errors

Added by David Ludvigsson 9 months ago. Updated 5 months ago.

Status:
Closed
Priority:
High
Category:
Hardware / Drivers
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:
amd64

Description

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 happening on both pfsense CE 2.7 and plus 23.5.1.

sample output below:

---
bnxt0: Link is UP full duplex, FC - receive & transmit - 25000 Mbps
bnxt0: link state changed to UP
vlan0: changing name to 'bnxt0.16'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
bnxt0: HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error.
bnxt0: set_multi: rx_mask set failed
bnxt0: HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error.
bnxt0: set_multi: rx_mask set failed
bnxt0: HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error.
bnxt0: set_multi: rx_mask set failed
bnxt0: HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error.
bnxt0: set_multi: rx_mask set failed
vlan1: changing name to 'bnxt0.20'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan2: changing name to 'bnxt0.11'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan3: changing name to 'bnxt0.18'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan4: changing name to 'bnxt0.12'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
[fib_algo] inet.0 (bsearch4#28) rebuild_fd_flm: switching algo to radix4_lockless
vlan5: changing name to 'bnxt0.14'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan6: changing name to 'bnxt0.23'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan7: changing name to 'bnxt0.64'
bnxt0: HWRM_CFA_L2_FILTER_ALLOC command returned INVALID_PARAMS error.
vlan8: changing name to 'bnxt0.66'
---

Actions #1

Updated by David Ludvigsson 9 months ago

Actions #2

Updated by Danilo Zrenjanin 9 months ago

  • Tracker changed from Bug to Regression
Actions #3

Updated by Kris Phillips 9 months ago

Hello,

Are you able to test this in the 23.09 snapshots to see if this issue is resolved?

Actions #4

Updated by David Ludvigsson 9 months ago

I replaced the NICs to get online again, but ill try in a testbuild.

Actions #5

Updated by David Ludvigsson 9 months ago

Where do i get the 23.09 snapshot releases?

Actions #6

Updated by Kristof Provost 8 months ago

  • Status changed from New to Feedback

I've cherry-picked the upstream fixes (see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269133) into our branches. This should be fixed in the next snapshot build.

Actions #7

Updated by Steve Wheeler 7 months ago

  • Project changed from pfSense Plus to pfSense
  • Category changed from Interfaces to Interfaces
  • Target version set to 2.8.0
  • Affected Plus Version deleted (22.05.1)
  • Plus Target Version set to 23.09
  • Affected Version set to 2.7.0
Actions #8

Updated by Jim Pingle 7 months ago

  • Subject changed from bnxt driver bug in 2.7.0 and 23.5.1 to ``bnxt(4)`` driver errors
  • Assignee set to Kristof Provost
  • % Done changed from 0 to 100

Updating subject for release notes.

Actions #9

Updated by Jim Pingle 7 months ago

  • Category changed from Interfaces to Hardware / Drivers
Actions #10

Updated by Jim Pingle 6 months ago

  • Status changed from Feedback to Closed

Closing for lack of feedback. If it's still an issue in this release we can reopen and re-target the issue at the next release.

Actions #11

Updated by Jim Pingle 5 months ago

  • Target version changed from 2.8.0 to 2.7.1
Actions

Also available in: Atom PDF