[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #34 from Andriy Gapon --- (In reply to Kristof Provost from comment #27) Do memory allocations need to be done with M_NOWAIT if they are performed in a context of a call (ioctl) from userland? I think that it's not impossible th

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #33 from Andriy Gapon --- (In reply to tech-lists from comment #32) Comment out all calls to uma_zone_set_max() under sys/netpfil/pf. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #32 from tech-li...@zyxst.net --- (In reply to Andriy Gapon from comment #31) How could that be done? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260629] cc(4): Chelsio T6225-CR takes 252 seconds to change state to UP

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260629 Navdeep Parhar changed: What|Removed |Added Status|Open|In Progress Assignee|b.

[Bug 260629] cc(4): Chelsio T6225-CR takes 252 seconds to change state to UP

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260629 Kubilay Kocak changed: What|Removed |Added Keywords||needs-qa CC|

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #31 from Andriy Gapon --- I wonder whether it would help if --purely as a hack / experiment -- the limits on uma zones that pf uses were removed. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #30 from Diego Linke --- (In reply to Kristof Provost from comment #29) Yes, I did. Please see below: # vmstat -z | grep -E 'pf|ITEM' ITEM SIZE LIMIT USED FREE REQ FAILSLEEP XDOMAIN pf mtags

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #29 from Kristof Provost --- (In reply to Diego Linke from comment #28) Have you checked the vmstat -z output as well? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #28 from Diego Linke --- I don't think it's an exclusive issue of arm64 platform. I am facing exactly this issue on a 13.0-RELEASE-p3 running at AWS EC2 instance in an amd64 i386 platform. -- You are receiving this mail becau

[Bug 260406] pfctl: Cannot allocate memory (after a time)

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406 --- Comment #27 from Kristof Provost --- Summarising some private debugging: The "pfctl: Cannot allocate memory." originates in a failed uma_zalloc() in pfr_create_kentry() on the V_pf_kentry_z ("pf table entries") zone. Confirmed by dtrac

[Bug 260474] ping -e does not forward packets to specified next-hop

2021-12-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260474 --- Comment #1 from Dmitry Afanasiev --- FreeBSD stable/13-n248589-defb7da9772 also affected by this issue. Check on VM from: https://download.freebsd.org/ftp/snapshots/VM-IMAGES/13.0-STABLE/amd64/20211216/FreeBSD-13.0-STABLE-amd64-2021121