From owner-freebsd-current@freebsd.org Fri Jul 6 23:25:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58137103B965 for ; Fri, 6 Jul 2018 23:25:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCEF874A93 for ; Fri, 6 Jul 2018 23:25:21 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 4b47c83f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Fri, 6 Jul 2018 16:25:19 -0700 (PDT) Subject: Re: AWS M5 ena issues [IGNORE] To: freebsd-current@freebsd.org References: From: Pete Wright Message-ID: <3cf5f980-fb7b-efc7-e3ea-33a2646dc140@nomadlogic.org> Date: Fri, 6 Jul 2018 16:25:15 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2018 23:25:22 -0000 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