Date: Thu, 28 Jun 2018 10:46:43 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Message-ID: <bug-225791-27103-VgYwYz2wUN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225791-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-225791-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=3D225791 --- Comment #5 from Richard Paul <richard@primarysite.net> --- Hi Colin, Thanks for responding to this issue. You're right to point out that this m= ay be down to the difference in hypervisors. M5 seem to be based on HVM too so for our purposes maybe moving over to an r4.2xlarge would be our nearest alternative in the r4 range of instances. We're waiting for the inevitable failure of our current instance as it seems to be falling over after 6-7 da= ys. What we need is some kind of reproducible test case for this to better be a= ble to diagnose the issue. As the other reporters in this ticket say, this can take hours to a day to reproduce and in our case, multiple days, which makes finding such a test case so time consuming and difficult. This is what I'm currently attempting to do with a cloned M5 instance type = of our DB server running the database dump and then trying to load the server heavily but it's not producing much in the way of results at the moment. --=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-225791-27103-VgYwYz2wUN>