Bug #4777
closedtcpdump causes kernel panic when deleting underlying interface
0%
Description
Cloned ath0 interface.
Ran tcpdump on console against ath0_wlan1.
Deleted ath0_wlan1 from GUI (Interfaces->Wireless tab).
Everything was fine for a short while, then kernel messages started flying past too quickly to read, and when I pressed the ACPI power button, the system instantly rebooted.
Yes, I know, stupid thing to do in the first place (I forgot about the running tcpdump!), but... I would have hoped tcpdump would have exited with an error, been killed, etc., not have the kernel suddenly wedge/die.
Updated by Adam Thompson almost 9 years ago
pfSense just prompted me, then automatically uploaded a crashreport (approx 2015-Jun-19 21:40 CDT [GMT-5]). Of course, there's no visible tracking number or anything, and I'm not sure where it went to... perhaps that could be made a little clearer?
Updated by Chris Buechler almost 9 years ago
- Status changed from New to Closed
that triggers a kernel panic in FreeBSD 10.1. Same wifi card in an 11-CURRENT (as of a couple days ago) box, tcpdump spits out a message that the interface disappeared and exits, and it doesn't crash.
Since it's already fixed in 11, and is highly unlikely to be encountered in production, I'll close this. Thanks for the report though.