[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #15 from Eugene Grosbein --- (In reply to Martin Birgmeier from comment #13) > What can you get from the ntp drift? Now we see this machine has good enough hardware timer to rule out problems linked with bad hardware timer. >

[Bug 234846] [lagg] race condition when adding port

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234846 --- Comment #14 from Stephen Hurd --- (In reply to Alexandre martins from comment #13) Ok, I'm a bit confused here, I must be missing something. Here's my (mis)understanding... please correct me where I'm wrong. - This bug was initially

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #14 from Martin Birgmeier --- Created attachment 201244 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201244&action=edit sysctl.conf This might be more interesting (kern.timecounter.hardware setting). -- You are r

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #13 from Martin Birgmeier --- Yes; I just thought it was going to help and wanted to make it permanent right away. Bad idea. In the meantime: [0]# cat /var/db/ntpd.drift -6.596 [0]# What can you get from the ntp drift? Is t

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #12 from Martin Birgmeier --- Created attachment 201243 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201243&action=edit loader.conf -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #11 from Eugene Grosbein --- Do you have any non-default settings in your /boot/loader.conf or /etc/sysctl.conf ? -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #10 from Eugene Grosbein --- (In reply to Martin Birgmeier from comment #9) >I added hw.pci.enable_msi=0 to /boot/loader.conf, which was a bad idea, >because with this, after loading the kernel, the system does not find ada0

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #9 from Martin Birgmeier --- I added hw.pci.enable_msi=0 to /boot/loader.conf, which was a bad idea, because with this, after loading the kernel, the system does not find ada0 anymore. (I recovered using a pxe netboot.) R

FreeBSD 12.0-Release - bge driver - network card glitches

2019-01-18 Thread Nikolas Chrysandreas
Hi, We've installed FreeBSD 12.0-Release on an HP DL380 Gen10. Seems like the network card freezes from time to time. Constant ping on machine stops working, ssh session is dropped and server is inaccessible. # pciconf -lv | grep -A4 bge bge0@pci0:2:0:0:class=0x02 card=0x22be1

[Bug 233535] Fix refcount leak in IPv6 MLD code leading to loss of IPv6 connectivity

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233535 --- Comment #48 from Hans Petter Selasky --- See: https://reviews.freebsd.org/D18887 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org maili

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #8 from Martin Birgmeier --- [0]# egrep 'FreeBSD|em0' var/run/dmesg.boot Copyright (c) 1992-2018 The FreeBSD Project. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-RELEASE-p5 #4 r341248M: Thu Nov 29 1

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #7 from Eugene Grosbein --- Routing of interrupts not changed between 11.2 and 12.0. Post output of grep em0 /z/backup/rsync/mizar/ROOT/.zfs/snapshot/backup.2018-12-24.21:03:49/var/run/dmesg.boot Please restart ntpd with drift

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 --- Comment #6 from Martin Birgmeier --- Hi Eugene, Thank you for looking into this. I have always been using ntp on all (physical, not VMs) machines. But I am not using a drift file because in my experience, the machines do not run long

[Bug 234207] VRRP packets generate "ipfw: pullup failed"

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234207 Andrey V. Elsukov changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 234207] VRRP packets generate "ipfw: pullup failed"

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234207 --- Comment #6 from commit-h...@freebsd.org --- A commit references this bug: Author: ae Date: Fri Jan 18 09:57:04 UTC 2019 New revision: 343142 URL: https://svnweb.freebsd.org/changeset/base/343142 Log: MFC 342925: Relax requirement

[Bug 234207] VRRP packets generate "ipfw: pullup failed"

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234207 --- Comment #5 from commit-h...@freebsd.org --- A commit references this bug: Author: ae Date: Fri Jan 18 09:54:29 UTC 2019 New revision: 343141 URL: https://svnweb.freebsd.org/changeset/base/343141 Log: MFC r342925: Relax requiremen

[Bug 233535] Fix refcount leak in IPv6 MLD code leading to loss of IPv6 connectivity

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233535 --- Comment #47 from Bjoern A. Zeeb --- (In reply to Hans Petter Selasky from comment #46) why don't you just open a review with the final patch, a good commit message, etc. and go the normal way; probably easier than anything else. --

[Bug 233535] Fix refcount leak in IPv6 MLD code leading to loss of IPv6 connectivity

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233535 --- Comment #46 from Hans Petter Selasky --- ae@ - What is the way forward? Differential revision or will someone approve the patch here? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 233535] Fix refcount leak in IPv6 MLD code leading to loss of IPv6 connectivity

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233535 --- Comment #45 from Andrey V. Elsukov --- (In reply to Hans Petter Selasky from comment #42) > Created attachment 201221 [details] > Fix MLD refcounting in IPv6 code (including additional debugging). > > Separate SLIST entries for deferre

[Bug 233535] Fix refcount leak in IPv6 MLD code leading to loss of IPv6 connectivity

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233535 --- Comment #44 from Hans Petter Selasky --- Created attachment 201228 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201228&action=edit Fix MLD refcounting in IPv6 code (no debug version). Here is also a no-debug version of the

[Bug 235031] [em] em0: poor NFS performance, strange behavior

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235031 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org --- Comment #5

[Bug 234846] [lagg] race condition when adding port

2019-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234846 --- Comment #13 from Alexandre martins --- I'm at the r321477 : https://svnweb.freebsd.org/base?view=revision&revision=321477 -- You are receiving this mail because: You are on the CC list for the bug. ___