Date: Thu, 08 Jul 2021 10:53:19 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 256934] Panic in ena driver on a t3.large ec2 instance after upgrading to 13.0 Message-ID: <bug-256934-27103-DhdF1DYIj2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256934-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-256934-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256934 Artur Rojek <ar@semihalf.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ar@semihalf.com --- Comment #2 from Artur Rojek <ar@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 a= nd 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 eventua= lly the instance forcibly comes down to baseline CPU utilization. Perhaps you f= aced 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. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256934-27103-DhdF1DYIj2>