Date: Tue, 10 Aug 2021 14:40:29 +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-iw6R98Nokv@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 --- Comment #4 from Artur Rojek <ar@semihalf.com> --- (In reply to Alex Dupre from comment #3) > What does the `debug.lock.delay_max` param do and what value should I try? This tunable defines how long to spin before the "spin lock held too long" panic is thrown, 1024 being default for your instance type (`roundup2(ncpus= ) * 256`). I suggested this thinking you were starved out of CPU resources, how= ever your machine clearly had plenty of CPU credits, so adjusting this param wou= ld not have helped. It could be something like temporary fluctuations on the instance side, in which case it would be very difficult to replicate the issue. --=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-iw6R98Nokv>