Date: Sat, 02 Apr 2016 02:19:30 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208389] Netmap Panic Message-ID: <bug-208389-2472-vDiZmhMqgQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208389-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-208389-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208389 --- Comment #14 from Shirkdog <mshirk@daemon-security.com> --- Test with FreeBSD 11 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294499: Thu Jan 21 15:46:19 UTC 2016= =20=20=20=20 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 It seems to take longer on Vanilla FreeBSD than HardenedBSD. If I start and stop tcpdump a few times it still panics in the same way for= me. ifconfig em1 up (Run the following several times (6 times it panics every time)): tcpdump -i netmap:em1 -nns 0 <Ctrl>+C Also, I know this has been bugged in Bug 193075, but if you use a host interface with the vale switch you also get a kernel panic tcpdump -i vale0:em0 tcpdump -i vale0:em1 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208389-2472-vDiZmhMqgQ>