[Bug 221445] The absence of the accept_rtadv option causes an error "ping6: sendmsg: No buffer space available"

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221445 --- Comment #8 from b...@schafweide.org --- Same issue here with a box at ultravps.eu. The gateway is outside of the /64, set a host route to it and the defaultroute onto the gateway, but it does not work. -- You are receiving this mail be

mlx5 interrupts

2020-07-19 Thread Slawa Olhovchenkov
Can anybody explain what purpose of unnamed interrupts of Mellanox ConnectX-5 cards? I am see 19 interrupts per card. I am mean last 16 is RX queue. What about first 3? Also I am see very high rate for irq287/irq306 -- is this good? # vmstat -i | grep -e ^int -e mlx interrupt

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #79 from László Károlyi --- So, I have tested today, and the results are great. I hit my server hard with transferring a 72GB file to an SMB mount on the local network, and then I copied that file over from the SMB mount to bac

No connection between jails

2020-07-19 Thread Grzegorz Junka
I have two jails in the same subnet on two different hosts: HOST1 -- jail1 | | HOST2 - jail2 HOST1: 10.70.7.13/16 HOST2: 10.70.70.2/16 jail1: 10.70.5.2/32 jail2: 10.70.7.50/32 Default gateway in the network is 10.70.70.1 but I don't think it matters in this issue. There is network conn

Re: No connection between jails

2020-07-19 Thread Rodney W. Grimes
> I have two jails in the same subnet on two different hosts: > > > HOST1 -- jail1 > > | > > | > > HOST2 - jail2 > > > HOST1: 10.70.7.13/16 > HOST2: 10.70.70.2/16 > jail1: 10.70.5.2/32 > jail2: 10.70.7.50/32 > > Default gateway in the network is 10.70.70.1 but I don't think it > matters in

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #80 from Eugene Grosbein --- (In reply to László Károlyi from comment #78) > There were no "module_register" errors in the dmesg This is a messages from loader. Loader messages do not get to kernel dmesg buffer. -- You are r

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #81 from Eugene Grosbein --- (In reply to László Károlyi from comment #79) You should monitor this driver's work in the long run. AFAIK this drivers uses 9KB mbufs unconditionally no matter if MTU is 1500 or more, so in the lon

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #82 from László Károlyi --- (In reply to Eugene Grosbein from comment #81) I have 64GB ram in the server with 54G being wired right now, so I don't think such a condition will occur at my machine. -- You are receiving this mai

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #83 from Konstantin Belousov --- (In reply to László Károlyi from comment #82) These numbers does not matter. On my 16G machine I got the issue in approximately 1 week of uptime. The port (not the stock vendor driver) has the

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #84 from Eugene Grosbein --- (In reply to Konstantin Belousov from comment #83) How about using 4096 by default with a notice in pkg-message for users requiring larger MTU? -- You are receiving this mail because: You are on th

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #85 from László Károlyi --- (In reply to Eugene Grosbein from comment #84) I'd like to have this in the GENERIC kernel, at least as some kind of a configurable option in loader.conf, so that I won't have to recompile the ports m

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #86 from Eugene Grosbein --- (In reply to László Károlyi from comment #85) Yes. But, if you use GENERIC of RELEASE0pX then you don't need to keep source trees at each server. Just compile the module once for major FreeBSD branc

Problem reports for n...@freebsd.org that need special attention

2020-07-19 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 166724] if_re(4): watchdog timeout

2020-07-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #87 from Eugene Grosbein --- (In reply to Konstantin Belousov from comment #83) > On my 16G machine I got the issue in approximately 1 week of uptime. Should it help increasing kern.ipc.nmbjumbo9 and/or kern.ipc.nmbjumbo16? -