[Bug 189219] [dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic

2015-12-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189219 Kubilay Kocak changed: What|Removed |Added Status|In Progress |Open --- Comment #7 from Kubilay K

[Bug 189219] [dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic

2015-12-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189219 Kubilay Kocak changed: What|Removed |Added Keywords||crash, needs-qa, patch -- You are

[Bug 189219] [dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic

2015-12-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189219 --- Comment #6 from Marius Strobl --- (In reply to Michael Moll from comment #2) That patch is overly complicated for solving the unaligned access triggered by config_link(); it's way simpler to just fix do_config() to properly align dn_li

RE: Intel X710 NVM - Update not available

2015-12-02 Thread Pieper, Jeffrey E
Steve, Subdevice: 6 indicates that this is a Dell SKU, and as such I don't believe their NVMs are included in Intel's public NVMUpdate tool. You'll need to use Dell's version, which you can find here: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=KWCDH Thanks, Jeff

Intel X710 NVM - Update not available

2015-12-02 Thread Steven Hartland
When starting on both FreeBSD and Linux the latest driver complains that the NVM should be updated. As there's no FreeBSD NVM update utility available I got the machine temporarily booted into Linux however the updater reports: "Update not available" I've attached the log from an inventory ru

[Bug 189219] [dummynet] [patch] using dummynet on sparc64 and configuring a pipe is an insta-panic

2015-12-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189219 l...@pix.net changed: What|Removed |Added CC||l...@pix.net --- Comment #5 from l..

Re: Outgoing packets being sent via wrong interface

2015-12-02 Thread Daniel Bilik
On Tue, 1 Dec 2015 12:16:45 +0100 Daniel Bilik wrote: > But next time it happens, I'll try to reload pf rules, and also to > disable pf completely... Done. First I've tried to flush nat... # pfctl -f /etc/pf.conf -F nat -O -N nat cleared ... then rules... # pfctl -f /etc/pf.conf -F rules -O -