Date: Fri, 6 Jul 2018 16:25:15 -0700 From: Pete Wright <pete@nomadlogic.org> To: freebsd-current@freebsd.org Subject: Re: AWS M5 ena issues [IGNORE] Message-ID: <3cf5f980-fb7b-efc7-e3ea-33a2646dc140@nomadlogic.org> In-Reply-To: <ced35751-2e2b-defd-592b-46fb8993028b@nomadlogic.org> References: <ced35751-2e2b-defd-592b-46fb8993028b@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
sorry - this was sent to incorrect list - please ignore. sorry for the noise! -pete On 07/06/2018 16:22, Pete Wright wrote: > hi there - this is in relation to this ticket: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 > > "ena driver causing kernel panics on AWS EC2" > > reading through the thread, and Colin's blog post on the new M5 > instance types, it looks like the issues people are running into are > related to NVMe devices fronting EBS block stores. My question is is > this a discreet issue from other anomalies people have seen with ena > network devices. For example, on some currently lightly loaded > m5.large instances I have been seeing this in the logs pretty regularly: > > ena0: device is going DOWN > ena0: device is going UP > ena0: queue 0 - cpu 0 > ena0: queue 1 - cpu 1 > > These systems were previously running 11.1-RELEASE, which I upgraded > to 11.2-RELEASE via "freebsd-update". These messages only started > showing up after I had completed the upgrade.2 > > > from reading the bug report above though it's not clear as to the > state of the ena drivers themselves. Are they considered unstable on > 11.2-RELEASE? > > Cheers, > -pete > -- Pete Wright pete@nomadlogic.org @nomadlogicLA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3cf5f980-fb7b-efc7-e3ea-33a2646dc140>