Re: Problem with Ethernet port BCM57416 NetXtreme-E Dual-Media 10G

2024-02-06 Thread Patrick M. Hausen
Hello Marcos,

> Am 06.02.2024 um 07:26 schrieb Marcos Lage :
> 
> Hello, I have a problem with the installation of OPNSense 24.1.

OPNsense 24.1 is based on FreeBSD 13.2-RELEASE-p9.

> I am unable to activate the Ethernet port BCM57416 NetXtreme-E Dual-Media 10G 
> RDMA Ethernet Controller.

Could you please post the pciconf output as text instead of a picture?

Also please verify with

kldstat

that the if_bnxt.ko module is loaded and add the output of

ifconfig -a

Thanks,
Patrick


Re: Problem with Ethernet port BCM57416 NetXtreme-E Dual-Media 10G

2024-02-06 Thread Marcos Lage
PciConf :

cibS@pcio: 0:28:0:
vendor
=
•Intel
class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a38
class
Corporation'
subvendor=0×1043
=
bridge
subdevice=0x8882
subclass
= PCI-PCI
cib6@pci0: 0:28:2:
vendor
=
'Intel Corporation'
class
class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a3a subvendor=0x1043
subdevice=0x8882
= bridge
subclass
= PCI-PCI
cib7Opci0:0:29:0:
vendor
' Intel
class
Corporation'
class=0x060400 rev=0x11 hdr=0x01 vendor=0x8086 device=0x7a36 subvendor=Dx1043
subdevice=0x8882
= bridge
subclass
= PCI-PCI
sabQ@pci0:0:31:0:
vendor
class=0x060100 rev=0x11 hdr=0×00 vendor=0x8086 device=0x7a06 subvendor=0x1043
Corporation'
class
= bridge
subclass
=
jac0@pciO: 0:31:3:
vendor
=
'Intel Corporation'
class=0x040300 rev=0x11 hdr=0x00 vendor=0x8086 device=0x7a50 subvendor=0x1043 
subdevice=0x87fb
class
multimedia
subclass
HDA
эпе4@рсі0:0:31:4:
vendor
' Intel
class
= serial
subclass
class=0x0c0500
rev=0x11
Corporation'
hdr=0x00 vendor=0x8086 device=0x7a23 subvendor=0x1043
bus
subdevice=0x8882
= SMBus
neS@pciO:0:31:5:
vendor
class=0x0c8000
rev=0x11 hdr=0x00 vendor=0x8086
=
• Intel
Corporation'
device=0x7a24 subvendor=0x1043 subdevice=0×8882
class
= serial
one6@pci0:1:0:0:
bus
class=0×02
rev=0x01
hdr=0x00 vendor=0x14e4 device=0x16d8 subvendor=0x14e4 subdevice=0x1593
vendor
=
' Broadcom
Inc.
and subsidiaries'
device
= ' BCM57416 Netxtreme-E
Dual-Media 10G RDMA Ethernet Controller'
class
=
network
subclass
=
ethernet
one7@pciD:1:0:1:
c1ass=D×D2
rev=0x01
hdr=0x00 vendor=0x14e4 device=0x16d8 subvendor=0x14e4 subdevice=0x1593
vendor
• Broadcom
Inc.
and subsidiaries'
device
= ' BCM57416 NetXtreme-E
Dual-Media 10G
RDMA Ethernet Controller'
class
= network
subclass
=
ethernet
mmeD@pci0:2:0:0:
class=0x010802 rev=0x01 hdr=0x00 vendor=0x2646 device=0x501c subvendor=0x2646 
subdevice=0x501c
vendor
'Kingston Technology Company, Inc.'
class
subclass
mass storage
NVM
one8@pciD:5:0:0:
vendor device class
subclass
=
n+ลกDleoneo.~
class=0x02 rev=0x05 hdr=0x00 vendor=0x10ec device=0x8125 subvendor=0x1043 
subdevice=0x87d7
'Realtek
Semi conductor Co. :
' RTL8125 2. 5GbE Controller
netuork
ethernet

Thanks
Le 6 févr. 2024 à 10:00 +0100, Patrick M. Hausen , a écrit :
> Hello Marcos,
>
> > Am 06.02.2024 um 07:26 schrieb Marcos Lage :
> >
> > Hello, I have a problem with the installation of OPNSense 24.1.
>
> OPNsense 24.1 is based on FreeBSD 13.2-RELEASE-p9.
>
> > I am unable to activate the Ethernet port BCM57416 NetXtreme-E Dual-Media 
> > 10G RDMA Ethernet Controller.
>
> Could you please post the pciconf output as text instead of a picture?
>
> Also please verify with
>
> kldstat
>
> that the if_bnxt.ko module is loaded and add the output of
>
> ifconfig -a
>
> Thanks,
> Patrick


Re: Problem with Ethernet port BCM57416 NetXtreme-E Dual-Media 10G

2024-02-06 Thread Patrick M. Hausen
Hi all!

> Am 06.02.2024 um 11:14 schrieb Marcos Lage :
> 
> PciConf :
> [...]

What about the other two pieces of information I asked for?

>> Also please verify with
>> 
>> kldstat
>> 
>> that the if_bnxt.ko module is loaded and add the output of
>> 
>> ifconfig -a

Kind regards,
Patrick




[Bug 276674] [panic] [htcp] sysctl net.inet.tcp.cc.algorithm=htcp produces kernel panic

2024-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276674

--- Comment #5 from Vladyslav V. Prodan  ---
Fresh panic.

Fatal trap 18: integer divide fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer = 0x20:0x830172f1
stack pointer   = 0x28:0xfe0044c4d838
frame pointer   = 0x28:0xfe0044c4d840
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 12 (irq25: virtio_pci0)
trap number = 18
panic: integer divide fault
cpuid = 0
time = 1707207718
KDB: stack backtrace:
db_trace_self_wrapper() at 0x804e375b =
db_trace_self_wrapper+0x2b/frame 0xfe0044c4d650
vpanic() at 0x80ce6a92 = vpanic+0x152/frame 0xfe0044c4d6a0
panic() at 0x80ce6933 = panic+0x43/frame 0xfe0044c4d700
trap_fatal() at 0x812faacd = trap_fatal+0x38d/frame 0xfe0044c4d760
calltrap() at 0x812d0bb8 = calltrap+0x8/frame 0xfe0044c4d760
--- trap 0x12, rip = 0x830172f1, rsp = 0xfe0044c4d838, rbp =
0xfe0044c4d840 ---
htcp_ack_received() at 0x830172f1 = htcp_ack_received+0x231/frame
0xfe0044c4d840
cc_ack_received() at 0x80f5cadc = cc_ack_received+0x28c/frame
0xfe0044c4d8a0
tcp_do_segment() at 0x80f61590 = tcp_do_segment+0x2be0/frame
0xfe0044c4d970
tcp_input_with_port() at 0x80f5dc2d = tcp_input_with_port+0xabd/frame
0xfe0044c4dab0
tcp6_input_with_port() at 0x80f5d10a = tcp6_input_with_port+0x6a/frame
0xfe0044c4dae0
tcp6_input() at 0x80f5e47b = tcp6_input+0xb/frame 0xfe0044c4daf0
ip6_input() at 0x80fb11a4 = ip6_input+0x9b4/frame 0xfe0044c4dbd0
netisr_dispatch_src() at 0x80e6d6af = netisr_dispatch_src+0xaf/frame
0xfe0044c4dc20
ether_demux() at 0x80e37bc9 = ether_demux+0x149/frame
0xfe0044c4dc50
ether_nh_input() at 0x80e38ee9 = ether_nh_input+0x379/frame
0xfe0044c4dcb0
netisr_dispatch_src() at 0x80e6d6af = netisr_dispatch_src+0xaf/frame
0xfe0044c4dd00
ether_input() at 0x80e37f39 = ether_input+0x69/frame 0xfe0044c4dd60
vtnet_rxq_eof() at 0x80a93f2f = vtnet_rxq_eof+0x72f/frame
0xfe0044c4de20
vtnet_rx_vq_process() at 0x80a936f8 = vtnet_rx_vq_process+0xb8/frame
0xfe0044c4de60
ithread_loop() at 0x80ca3957 = ithread_loop+0x257/frame
0xfe0044c4def0
fork_exit() at 0x80ca039d = fork_exit+0x7d/frame 0xfe0044c4df30
fork_trampoline() at 0x812d1c2e = fork_trampoline+0xe/frame
0xfe0044c4df30
--- trap 0xa57f2f0d, rip = 0xb1378a3faf069d41, rsp = 0x7a5d5f3c4604970a, rbp =
0x2b154069806bd89e ---
KDB: enter: panic

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 276674] [panic] [htcp] sysctl net.inet.tcp.cc.algorithm=htcp produces kernel panic

2024-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276674

--- Comment #6 from Vladyslav V. Prodan  ---
Created attachment 248219
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=248219&action=edit
Core.9

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 276674] [panic] [htcp] sysctl net.inet.tcp.cc.algorithm=htcp produces kernel panic

2024-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276674

--- Comment #7 from Vladyslav V. Prodan  ---
(In reply to Vladyslav V. Prodan from comment #6)

vmcore.9.xz - 52MB
https://mega.nz/file/Y0YSVTDJ#oDOM_UTqcud8JjnJaQ4Y6fcvpLETibLq_6EVKab0FlE

-- 
You are receiving this mail because:
You are the assignee for the bug.


Re: Guidance regarding GSoC projects

2024-02-06 Thread Joseph Mingrone
On Sun, 2024-02-04 at 22:43, "divyansh.nankani"  wrote:

> Hi , 

> I am intending to participate in GSoC for FreeBSD this year. I need a bit of 
> help navigating where to start contributing to FreeBSD for issues/features 
> specifically related to the GSoC projects I am targeting : 


> - Improve netgraph concurrency 

> - Implement MPLS support for FreeBSD



> I am also interested in UFS4fuse: support FreeBSD's UFS2 with fusefs (with 
> rust) but there is no mentor assigned for this project on the project ideas 
> page.

> I will be really grateful if you can help me out with this.



> Thanks,

> Divyansh

Hi Divyansh,

It's nice to hear you are interested in working with FreeBSD this summer, and 
it's good you are starting early.  We find out around February 21 whether 
FreeBSD has been accepted to participate in GSoC 2024.

The MPLS project was attempted in 2008 [0] and 2018 [1].  Hopefully we can 
track down some code from that past work and then determine whether this is 
still an appropriate project.

I see 29 bugs related to netgraph [3].  I suggest investigating the newer ones 
to see if they pique your interest.  Although not directly related to 
concurrency, bug #267413 looks interesting.  It's unclear how challenging it 
will be to solve.  Maybe Alexander, who is copied here, could offer better 
guidance.

There is now one tentative mentor for the UFS4fuse project, Alan Somers.  I say 
tentative because we probably still require a co-mentor for this project to be 
viable.  We have one in mind but have yet to hear back whether he's available.

I hope this helps you get started.  If you have any other questions, please let 
me know, and I'll do my best to steer you in the right direction.

Regards,

Joe

[0] https://wiki.freebsd.org/SummerOfCode2008#Implementation_of_MPLS_on_FreeBSD
[1] https://wiki.freebsd.org/SummerOfCode2018Projects/FinishingMPLS
[3] https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=netgraph



dot1 issue, can't ping 2 interfaces each others

2024-02-06 Thread Benoit Chesneau
I have 2 machines connected on 2 ports of the same switch on which I try to 
pass a vlan 10 encapsulated in vlan 330 using dot1 q protocol. The 
configuration is very generic, but I cant ping each others machines

Ex:
```
# ping 1.1.1.198
PING 1.1.1.1.198 (1.1.1.1.198): 56 data bytes
ping: sendto: Host is down
```

Configuration:

M1:
```
vlan330: flags=1008843 metric 
0 mtu 1500
options=680703
ether 50:65:f3:8b:98:71
groups: vlan
vlan: 330 vlanproto: 802.1ad vlanpcp: 0 parent interface: mlxen0
media: Ethernet autoselect (40Gbase-CR4 )
status: active
nd6 options=29
vlan330.10: flags=1008843 
metric 0 mtu 1480
options=8
ether 50:65:f3:8b:98:71
inet 1.1.1.199 netmask 0xfffe broadcast 255.255.255.255
groups: vlan
vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: vlan330
media: Ethernet autoselect (40Gbase-CR4 )
status: active nd6 options=29
```

M2:

```
vlan330: flags=1008843 metric 
0 mtu 1500
description: service
options=1c680703
ether 02:01:02:02:01:00
groups: vlan
vlan: 330 vlanproto: 802.1ad vlanpcp: 0 parent interface: mce0
media: Ethernet 25GBase-SR 
status: active
nd6 options=29
vlan330.10: flags=1008843 
metric 0 mtu 1480
options=1c08
ether 02:01:02:02:01:00
inet 1.1.1.198 netmask 0xfffe broadcast 255.255.255.255
inet6 fe80::1:2ff:fe02:100%vlan330.10 prefixlen 64 scopeid 0xe
groups: vlan
vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: vlan330
media: Ethernet 25GBase-SR 
status: active nd6 options=21

```

On the switch:

```
interface eth-0-29
switchport mode trunk
switchport trunk allowed vlan all!
interface eth-0-30
switchport mode trunk
switchport trunk allowed vlan all!

```

Any idea is welcome :)

Benoît Chesneau, Enki Multimedia
—
t. +33608655490

Sent with [Proton Mail](https://proton.me/) secure email.

Re: Request for Testing: TCP RACK

2024-02-06 Thread tuexen
> On Jan 5, 2024, at 08:48, tue...@freebsd.org wrote:
> 
>> On Jan 4, 2024, at 21:39, Herbert J. Skuhra  wrote:
>> 
>> On Thu, 04 Jan 2024 21:22:22 +0100, tue...@freebsd.org wrote:
>>> 
 On Jan 4, 2024, at 18:52, Herbert J. Skuhra  wrote:
 
 On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote:
> 
> On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote:
>> 
>> Hi,
>> 
>> On Fri, 17 Nov 2023 00:15:13 +0100, tue...@freebsd.org wrote:
>>> 
 On Nov 16, 2023, at 20:06, Herbert J. Skuhra  wrote:
 
 On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labbé wrote:
> 
> On Thu, Nov 16, 2023 at 5:10 PM Herbert J. Skuhra  
> wrote:
> 
>> 
>> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS".
>> 
>> After setting "sysctl net.inet.tcp.functions_default=rack" git no
>> longer works:
>> 
>> 
> Are you using a fresh 15 head or a specific network setup ?
> 
> Because I'm not able to reproduce your problem on my system:
> 
> $ uname -a
> FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0
> main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023
> root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS
> amd64
> $ cat /usr/src/sys/amd64/conf/TCPHPTS
> include GENERIC-NODEBUG
> ident   TCPHPTS
> options TCPHPTS
> $ sysctl net.inet.tcp.functions_default
> net.inet.tcp.functions_default: rack
> $ git clone -q g...@github.com:freebsd/freebsd-src.git && echo working
> working
> $
 
 OK, (g)it works if I disable pf. Do you use pf?
>>> Can you share your pf config such that I can reproduce the problem 
>>> locally?
>> 
>> 1. It even fails with a simple pf.conf:
>> pass in all
>> pass out all
>> 
>> 2. Fetching port distfiles also failed.
>> 
>> 3. If I disable rxcsum on the ethernet adapter (igb0) it works.
> 
> Disabling lro also resolves the issue.
 
 If I run "sysctl net.inet.tcp.rack.features.cmpack=0" I don't have to
 disable rxcsum/tcxsum or lro on igb0.
>>> Does the problem also goes away if you disable pf completely, but keep
>>> compressed acks enabled?
>> 
>> Yes, it works with pf disabled and compressed acks enabled.
> Thanks for the information!
A patch is available at:
https://reviews.freebsd.org/D43769

Best regards
Michael
> 
> Best regards
> Michael
>> 
>> --
>> Herbert
> 
> 




Re: Request for Testing: TCP RACK

2024-02-06 Thread Herbert J. Skuhra
On Tue, 06 Feb 2024 23:05:27 +0100, tue...@freebsd.org wrote:
> 
> > On Jan 5, 2024, at 08:48, tue...@freebsd.org wrote:
> > 
> >> On Jan 4, 2024, at 21:39, Herbert J. Skuhra  wrote:
> >> 
> >> On Thu, 04 Jan 2024 21:22:22 +0100, tue...@freebsd.org wrote:
> >>> 
>  On Jan 4, 2024, at 18:52, Herbert J. Skuhra  wrote:
>  
>  On Thu, 04 Jan 2024 11:40:35 +0100, "Herbert J. Skuhra" wrote:
> > 
> > On Fri, 17 Nov 2023 14:31:02 +0100, "Herbert J. Skuhra" wrote:
> >> 
> >> Hi,
> >> 
> >> On Fri, 17 Nov 2023 00:15:13 +0100, tue...@freebsd.org wrote:
> >>> 
>  On Nov 16, 2023, at 20:06, Herbert J. Skuhra  
>  wrote:
>  
>  On Thu, 16 Nov 2023 19:07:29 +0100, Olivier Cochard-Labbé wrote:
> > 
> > On Thu, Nov 16, 2023 at 5:10 PM Herbert J. Skuhra 
> >  wrote:
> > 
> >> 
> >> OK, I am now running GENERIC-NODEBUG + "options TCPHPTS".
> >> 
> >> After setting "sysctl net.inet.tcp.functions_default=rack" git no
> >> longer works:
> >> 
> >> 
> > Are you using a fresh 15 head or a specific network setup ?
> > 
> > Because I'm not able to reproduce your problem on my system:
> > 
> > $ uname -a
> > FreeBSD bigone 15.0-CURRENT FreeBSD 15.0-CURRENT #0
> > main-n266452-070d9e3540e6: Thu Nov 16 17:53:15 CET 2023
> > root@bigone:/usr/obj/usr/src/amd64.amd64/sys/TCPHPTS
> > amd64
> > $ cat /usr/src/sys/amd64/conf/TCPHPTS
> > include GENERIC-NODEBUG
> > ident   TCPHPTS
> > options TCPHPTS
> > $ sysctl net.inet.tcp.functions_default
> > net.inet.tcp.functions_default: rack
> > $ git clone -q g...@github.com:freebsd/freebsd-src.git && echo 
> > working
> > working
> > $
>  
>  OK, (g)it works if I disable pf. Do you use pf?
> >>> Can you share your pf config such that I can reproduce the problem 
> >>> locally?
> >> 
> >> 1. It even fails with a simple pf.conf:
> >> pass in all
> >> pass out all
> >> 
> >> 2. Fetching port distfiles also failed.
> >> 
> >> 3. If I disable rxcsum on the ethernet adapter (igb0) it works.
> > 
> > Disabling lro also resolves the issue.
>  
>  If I run "sysctl net.inet.tcp.rack.features.cmpack=0" I don't have to
>  disable rxcsum/tcxsum or lro on igb0.
> >>> Does the problem also goes away if you disable pf completely, but keep
> >>> compressed acks enabled?
> >> 
> >> Yes, it works with pf disabled and compressed acks enabled.
> > Thanks for the information!
> A patch is available at:
> https://reviews.freebsd.org/D43769

Hi Michael,

the patch resolves the issue.

Thanks a lot.

Best regards,
Herbert



Re: dot1 issue, can't ping 2 interfaces each others

2024-02-06 Thread sthaug
> I have 2 machines connected on 2 ports of the same switch on which I try to 
> pass a vlan 10 encapsulated in vlan 330 using dot1 q protocol. The 
> configuration is very generic, but I cant ping each others machines

Did you want to have 802.1q (Ethertype 0x8100) for both inner and
outer tags? From the ifconfig output it looks like you're using
802.1ad (Ethertype 0x88a8) for the outer tag:

> vlan: 330 vlanproto: 802.1ad vlanpcp: 0 parent interface: mlxen0

This will *not* work with a switch configured for 802.1q, which this
certainly looks like:

> switchport mode trunk

FreeBSD is absolutely capable of using the 802.1q Ethertype for both
tags.

Steinar Haug, Nethelp consulting, sth...@nethelp.no

> 
> Ex:
> ```
> # ping 1.1.1.198
> PING 1.1.1.1.198 (1.1.1.1.198): 56 data bytes
> ping: sendto: Host is down
> ```
> 
> Configuration:
> 
> M1:
> ```
> vlan330: flags=1008843 
> metric 0 mtu 1500
> options=680703
> ether 50:65:f3:8b:98:71
> groups: vlan
> vlan: 330 vlanproto: 802.1ad vlanpcp: 0 parent interface: mlxen0
> media: Ethernet autoselect (40Gbase-CR4 )
> status: active
> nd6 options=29
> vlan330.10: flags=1008843 
> metric 0 mtu 1480
> options=8
> ether 50:65:f3:8b:98:71
> inet 1.1.1.199 netmask 0xfffe broadcast 255.255.255.255
> groups: vlan
> vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: vlan330
> media: Ethernet autoselect (40Gbase-CR4 )
> status: active nd6 options=29
> ```
> 
> M2:
> 
> ```
> vlan330: flags=1008843 
> metric 0 mtu 1500
> description: service
> options=1c680703
> ether 02:01:02:02:01:00
> groups: vlan
> vlan: 330 vlanproto: 802.1ad vlanpcp: 0 parent interface: mce0
> media: Ethernet 25GBase-SR 
> status: active
> nd6 options=29
> vlan330.10: flags=1008843 
> metric 0 mtu 1480
> options=1c08
> ether 02:01:02:02:01:00
> inet 1.1.1.198 netmask 0xfffe broadcast 255.255.255.255
> inet6 fe80::1:2ff:fe02:100%vlan330.10 prefixlen 64 scopeid 0xe
> groups: vlan
> vlan: 10 vlanproto: 802.1q vlanpcp: 0 parent interface: vlan330
> media: Ethernet 25GBase-SR 
> status: active nd6 options=21
> 
> ```
> 
> On the switch:
> 
> ```
> interface eth-0-29
> switchport mode trunk
> switchport trunk allowed vlan all!
> interface eth-0-30
> switchport mode trunk
> switchport trunk allowed vlan all!
> 
> ```
> 
> Any idea is welcome :)
> 
> Benoît Chesneau, Enki Multimedia
> —
> t. +33608655490
> 
> Sent with [Proton Mail](https://proton.me/) secure email.