Date: Wed, 30 Mar 2016 03:46:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 208389] Netmap Panic Message-ID: <bug-208389-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208389 Bug ID: 208389 Summary: Netmap Panic Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: shawn.webb@hardenedbsd.org When you run `tcpdump -ni netmap:em0` and em0 is not in Netmap mode and you exit tcpdump (by hitting ^C), FreeBSD will panic. Picture of panicking box here: https://goo.gl/photos/1fdTaMBFdit6ZkrP8 For some reason, doing a dump at the ddb prompt didn't produce a core.txt. Here's info.txt: Dump header from device: /dev/ada0s1b Architecture: amd64 Architecture Version: 2 Dump Length: 710184960 Blocksize: 512 Dumptime: Tue Mar 29 15:37:43 2016 Hostname: [sanitized] Magic: FreeBSD Kernel Dump Version String: FreeBSD 11.0-CURRENT-HBSD #73 [DEVEL:HardenedBSD-CURRENT-amd64:427] d31c1ca(HEAD): Sun Mar 20 09:25:50 EDT 2016 jenkins@nyi-01.build.hardenedbsd.org:/usr/obj/jenkins/workspace/Hardene= dBSD Panic String: Dump Parity: 3422855522 Bounds: 0 Dump Status: good --=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-8>