Date: Fri, 09 Jul 2021 16:26:21 +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-VJNKpSzyrD@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=256934 --- Comment #3 from Alex Dupre <ale@FreeBSD.org> --- (In reply to Artur Rojek from comment #2) The machine had plenty of CPU credits when it happened, that possibility can be discarded. Until now, this was the only occurrence, but it happened after 15 days of uptime and now only other 7 days passed. I have other machines that were upgraded at the same time and didn't suffer the issue. But before upgrading to 13.0 they never suffered any kernel panic, FWIW. What does the `debug.lock.delay_max` param do and what value should I try? Currently I see it at 1024. -- 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-VJNKpSzyrD>