https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
John-Mark Gurney changed:
What|Removed |Added
CC||j...@freebsd.org
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Kristof Provost changed:
What|Removed |Added
Assignee|freebsd...@freebsd.org |freebsd-bugs@FreeBSD.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #10 from noah.bergba...@tum.de ---
# sysctl kern.hz
kern.hz: 1000
I can't really experiment on the machine but from what I can see, r320848
shouldn't change anything anyways because VNET isn't in use right now.
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #9 from Kristof Provost ---
That's quite odd. It's almost as if rw_sleep() isn't doing what it's supposed
to do.
That seems unlikely, but not impossible.
Is the output of 'sysctl kern.hz' sane?
If you can experiment on the box
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #8 from noah.bergba...@tum.de ---
The workaround I'm using now is:
echo "set timeout interval 2" | pfctl -mf - && echo "set timeout interval 1" |
pfctl -mf -
Every hour in crontab.
It causes the purge thread to wake up
(https:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #7 from Kristof Provost ---
Hmm, that looks entirely normal. Your purge thread is sleeping in the
rw_sleep() call. It should be waking up every 10 seconds or so. It's either not
waking up, or it's not actually doing anything whe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #6 from noah.bergba...@tum.de ---
# procstat -kk 16
16 100102 pf purge- mi_switch+0xe5
sleepq_timedwait+0x42 _sleep+0x235 pf_purge_thread+0x8e fork_exit+0x85
fork_trampoline+0xe
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #5 from Kristof Provost ---
Okay, that's an interesting clue.
Let's see if we can work out where it's getting stuck. Can you do 'sudo
procstat -kk '?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #4 from noah.bergba...@tum.de ---
I just realized that because pf is compiled into the kernel, the dtrace probes
need to be fbt:kernel:* instead of fbt:pf:* . With that, it starts up:
dtrace: script './pf.dtrace' matched 8 probe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #3 from Kristof Provost ---
(In reply to noah.bergbauer from comment #2)
The function may have wound up being inlined in your kernel config, so we can't
instrument it.
Just remove whatever functions dtrace can't find, we'll get
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #2 from noah.bergba...@tum.de ---
The purge thread is there:
root160,0 0,0 0 16 - DL 10:57 0:00,04 - [pf
purge]
The dtrace script fails:
dtrace: failed to compile script ./pf.dtrace: line 3: pr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Bug ID: 222126
Summary: pf is not clearing expired states
Product: Base System
Version: 11.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: A
16 matches
Mail list logo
