Re: [Bug 219428] em network driver broken in current

On Sat, Jul 13, 2019 at 12:54 PM wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 > > --- Comment #23 from IPTRACE --- > Is there any workaround instead of restart a system? > I was trying below without progress as well. > > # ifconfig igb0 down > # ifconfig igb0 up > > I think

[Bug 219428] em network driver broken in current

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219428 --- Comment #23 from IPTRACE --- Is there any workaround instead of restart a system? I was trying below without progress as well. # ifconfig igb0 down # ifconfig igb0 up I think the problem is when the network card loses ethernet link an

[Bug 237441] Virtio net consistently truncates last byte of a fetch xfer with > 8956 bytes of payload

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237441 --- Comment #7 from Christoph Kliemann --- (In reply to Christoph Kliemann from comment #6) Please disregard. Managed to reproduce after a reboot. Sorry for the noise. -- You are receiving this mail because: You are on the CC list for th

[Bug 237441] Virtio net consistently truncates last byte of a fetch xfer with > 8956 bytes of payload

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237441 --- Comment #6 from Christoph Kliemann --- I think this is not a FreeBSD issue. Can't reproduce immediately after a host reboot. The issue occurs after the first sleep/wake cycle of the host and persists until reboot. This seems to be a ma

[Bug 238642] netmap: fix kernel pointer printing in netmap_generic.c

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238642 --- Comment #6 from Vincenzo Maffione --- Yes, indeed. For some reason when I did not catch this when running the tests. I'll fix it now. -- You are receiving this mail because: You are on the CC list for the bug.