Date: Mon, 20 Apr 2020 21:09:10 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 235856] FreeBSD freezes on AWS EC2 t3 machines Message-ID: <bug-235856-27103-HVTL6ti8HS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235856-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-235856-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=3D235856 --- Comment #51 from Colin Percival <cperciva@FreeBSD.org> --- (In reply to mail from comment #50) Hi Ruben, Thanks! This is consistent with my current understanding, which is that the patch I provided fixes the data structure corruption issues (which showed u= p as some of the more "interesting" warnings and also sometimes as kernel panics= ). The timeouts and freezing appear to be due to the ENA driver having trouble allocating jumbo mbuf clusters during low-memory conditions. Can you check "sysctl -a | grep mjum_alloc_fail" (ideally, log it every minute and see if= it jumps around the times you see hanging)? I have a patch which I believe fixes this which I'd be happy to share if you want to try something experimental -- we're still discussing details about = the best way to address this, though. Colin --=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-235856-27103-HVTL6ti8HS>