Kristof Provost
- Login: kprovost
- Registered on: 02/01/2021
- Last connection: 06/25/2024
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 2 | 87 | 89 |
| Reported issues | 5 | 1 | 6 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| pfSense | Developer, Reporter | 02/01/2021 |
| Bootstrap | Reporter | 02/01/2021 |
| pfSense Docs | Developer, Reporter | 02/01/2021 |
| pfSense Plus | Developer, Reporter | 02/01/2021 |
Activity
06/25/2024
-
06:40 PM pfSense Plus Bug #15196: AWS ena interfaces can become unstable/stop responding
- Okay, so the issue is believed to be associated with an increase in thread count. That's new information. It would be...
06/18/2024
-
- Craig Coonrad wrote in #note-34:
> dtrace submitted based on: https://redmine.pfsense.org/issues/15196#note-21
> HS...
06/17/2024
-
- `can't allocate llinfo` is logged by arpresolve_full(), when lltable_alloc_entry() returns NULL. lltable_alloc_entry(...
06/14/2024
-
- Are the users affected by `kernel: arpresolve: can't allocate llinfo` running a routing daemon (openbgpd, frr, ...)?
... -
- Was there a `kernel: arpresolve: can't allocate llinfo ` in HS# 2828658261?
What sort of connection issues is it see...
06/10/2024
-
- I believe I see what's happening.
When rules are re-loaded we explicitly copy the counter state from the previous ...
06/03/2024
-
- So the log in comment 23 has "kernel: arpresolve: can't allocate llinfo for 172.21.253.1 on ena1". So I'm wondering i...
05/23/2024
-
- Okay, that would seem to indicate that we're not spending our CPU time in the ena driver. That's a bit unexpected, gi...
05/21/2024
-
- This was on a VM that was manifesting the problem (i.e. elevated CPU use and loss of connectivity) at the time the dt...
05/17/2024
-
- I took a very quick look. The faulting code in6_pcbbind+0x360 translates to /var/jenkins/workspace/pfSense-CE-snapsho...
Also available in: Atom