On Wed, 28 Mar 2018, Manuel Bouyer wrote:
On Wed, Mar 28, 2018 at 06:23:56PM +0200, 6b...@6bone.informatik.uni-leipzig.de
wrote:
I changed from 1.88.2.10 to 1.88.2.13. The problem was not solved. I have
also tested the onboeard network card. After a few hours, the problem also
occurred here.
On Wed, Mar 28, 2018 at 06:33:57PM +0200, Manuel Bouyer wrote:
> I also use NFS on a netbsd-8 host, without problems.
Me too, but that does not mean a lot.
Martin
On 2018-03-28 18:23, 6b...@6bone.informatik.uni-leipzig.de wrote:
Any ideas how to narrow down the cause?
I would try it with fewer mount options if you can, you seemed to be
using
everything available in the original email.
On Wed, Mar 28, 2018 at 06:23:56PM +0200, 6b...@6bone.informatik.uni-leipzig.de
wrote:
> I changed from 1.88.2.10 to 1.88.2.13. The problem was not solved. I have
> also tested the onboeard network card. After a few hours, the problem also
> occurred here. I still think it's a nfs problem.
>
>
On Fri, 23 Mar 2018, SAITOH Masanobu wrote:
How old is your kernel?
If your kernel's ixgbe.c is older than 1.88.2.13 please update the latest
netbsd-8 and try. 1.88.2.13 (and 1.88.2.10) fixed serious interrupt problem.
I changed from 1.88.2.10 to 1.88.2.13. The problem was not solved. I
On Tue, 20 Mar 2018, Martin Husemann wrote:
Which network driver is used on the client?
ixg0 at pci8 dev 0 function 0: Intel(R) PRO/10GbE PCI-Express Network Driver,
Version - 3.2.12-k
ixg0: device 82599EB
ixg0: ETrackID 830d
ixg0: for TX/RX, interrupting at msix0 vec 0, bound queue 0
On Tue, Mar 20, 2018 at 10:20:08AM +0100, 6b...@6bone.informatik.uni-leipzig.de
wrote:
> Are there any ideas which mount option can be the problem? Is it possible to
> eliminate the problem with a configuration change or is it a bug?
Which network driver is used on the client?
Martin
Hello,
I have problems with the nfs-client under netbsd-8. In principle, the nfs
works. Some time after an nfs share is mounted, there are network breaks
on the client. The following ping from the outside on the client shows the
phenomenon.
...
64 bytes from 139.18.xx.yy: icmp_seq=6496
