https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255971
--- Comment #7 from Kristof Provost <k...@freebsd.org> --- (In reply to Rumen Palov from comment #6) Ah, I misunderstood your test setup. In that case the last few thousand lines might be more interesting. Depending on how the system stops working, of course. When you say it hangs, how are you diagnosing this? Loss of SSH access, or do you not get any response from the console any more? (It's more likely for pf issues to break networking than it is for it to totally freeze the system.) I'm going to assume that comment #1 means you can access the console when it's in the bad state. If the console is still responsive a forced core dump (sysctl debug.kdb.panic=1) is likely to be useful. A truss run over a single pfctl that produces "pfctl: DIOCGETRULE: Cannot allocate memory" should also be useful. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-pf@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "freebsd-pf-unsubscr...@freebsd.org"
