From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 10 12:59:16 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99B0B106566C for ; Fri, 10 Aug 2012 12:59:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id 31B368FC08 for ; Fri, 10 Aug 2012 12:59:15 +0000 (UTC) Received: from OctaHexa64-MkII (HPQuadro64.dmpriest.net.uk [62.13.130.30]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q7ACxC5q051863 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Aug 2012 13:59:14 +0100 (BST) Date: Fri, 10 Aug 2012 13:59:12 +0100 From: Karl Pielorz To: freebsd-hackers@FreeBSD.org Message-ID: <933A64025C87497D5FBDCA75@OctaHexa64-MkII> In-Reply-To: <8E11701C93FCCC39AA97E4F1@OctaHexa64-MkII> References: <8E11701C93FCCC39AA97E4F1@OctaHexa64-MkII> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: FreeBSD 9.0-R em0 issues? - update... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2012 12:59:16 -0000 The last time it hung, 'netstat -n -i' showed: " Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll em0 1500 00:25:90:31:82:46 355482 10612864185945 0 291109 3032246910270 1516123455135 " That's from about 30 seconds after the interface 'stopped' - that number of ierrs/oerrs etc. - is just impossible for the traffic the machine handles, it looks like it's corrupt? Having dug around some more - I've now set: hw.em.enable_msix=0 After rebooting - the hang hasn't happened since - I'll leave it running like that for a while. If anyone can suggest anything to run when / if this happens again to track things down further - or any reason why it's doing it, that'd be great.. -Karl ps. Should have said before but the machine is running an amd64 kernel.