https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256934
Artur Rojek <a...@semihalf.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |a...@semihalf.com
--- Comment #2 from Artur Rojek <a...@semihalf.com> ---
(In reply to Alex Dupre from comment #0)
Hi Alex,
I researched this issue and there are no significant changes between 12.2 and
13.0 with regards to your backtrace. I don't see any connection to the ena
driver either, as `ena_keep_alive_wd+0x24` is a simple call of
`counter_u64_zero`. The EC2 T3 instance type you are using is a burstable
performance instance, meaning that (depending on your configuration) you can
spend CPU resources above the baseline for periods of time, however eventually
the instance forcibly comes down to baseline CPU utilization. Perhaps you faced
this bottleneck just when your machine required more CPU "oomph"?
Have you been able to reproduce this issue on 13.0 since, or is this a one time
occurrence?
One thing I can suggest at the moment is to try to adjust
`debug.lock.delay_max`, which is configurable since 13.0.
--
You are receiving this mail because:
You are the assignee for the bug.
