Actions
Bug #4751
closedkernel panic after disabling captive portal when idle timeout is in use
Start date:
06/08/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.x
Affected Architecture:
Description
If you have a CP config with an idle timeout, have a user logged in, and disable CP, when the idle timeout is reached it will kernel panic the system with something like the following:
db:0:kdb.enter.default> bt Tracing pid 37926 tid 100336 td 0xfffff801da64e490 __rw_wlock_hard() at __rw_wlock_hard+0x1b0/frame 0xfffffe00649b77b0 _rw_wlock_cookie() at _rw_wlock_cookie+0x5a/frame 0xfffffe00649b77d0 ipfw_add_table_entry() at ipfw_add_table_entry+0xef/frame 0xfffffe00649b7850 ipfw_ctl() at ipfw_ctl+0x2a2/frame 0xfffffe00649b79b0 rip_ctloutput() at rip_ctloutput+0x2a0/frame 0xfffffe00649b79e0 sosetopt() at sosetopt+0xcc/frame 0xfffffe00649b7a50 kern_setsockopt() at kern_setsockopt+0xdc/frame 0xfffffe00649b7ac0 sys_setsockopt() at sys_setsockopt+0x24/frame 0xfffffe00649b7ae0 amd64_syscall() at amd64_syscall+0x351/frame 0xfffffe00649b7bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00649b7bf0 fff9fc888, rbp = 0x7fffff9fc950 ---
Actions