From owner-freebsd-stable@FreeBSD.ORG Mon Nov 13 22:35:25 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FA9E16A4CE for ; Mon, 13 Nov 2006 22:35:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F32543E13 for ; Mon, 13 Nov 2006 22:30:52 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so789486pyh for ; Mon, 13 Nov 2006 14:30:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ek6PD136v/bAuJws6W39+Gy2MULWMDGTctfKsH9Zn7DVJtnHvWCbRt3bzonP1vc6peSAm9qkKkAOhgYyEysz5p6K6hW1BizllNL8HlkraNzsTe8sM9BFVW/93eUBY/GLHGm5ytimysSBUusrgl3PC4a4JkPeOf69pqbPR8ftO+8= Received: by 10.35.82.15 with SMTP id j15mr295160pyl.1163457001739; Mon, 13 Nov 2006 14:30:01 -0800 (PST) Received: by 10.35.118.6 with HTTP; Mon, 13 Nov 2006 14:30:01 -0800 (PST) Message-ID: <2a41acea0611131430x3c9206f4ua1ffe6cbf5e82202@mail.gmail.com> Date: Mon, 13 Nov 2006 14:30:01 -0800 From: "Jack Vogel" To: "Bill Moran" In-Reply-To: <20061113171529.a75fe20a.wmoran@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061113171529.a75fe20a.wmoran@collaborativefusion.com> Cc: stable@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 22:35:25 -0000 On 11/13/06, Bill Moran wrote: > > Just experienced an "interrupt storm" on an em device that disabled a > server until I could reboot it. > > My initial research turned up this thread: > http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058336.html > > Which seems related, even if it is a little old. I'm aware that there > have been problems with recent versions of the em driver but I haven't > been following them closely enough, and there's a LOT of mail traffic > on this topic. > > Note that this is a FreeBSD 5.3-RELEASE-p37 system. An upgrade is > possible, but this is a production system and the problem occurs > infrequently, so I'm reluctant to schedule downtime unless I have good > reason to believe that it will fix the problem. > > Anyone remember if the above problem was fixed in more recent versions, > or knows enough about the issue to comment on whether I'm barking up > the correct tree or not? I'm pretty early in the diagnosis on this, > but I'm looking for pointers to keep me from doing random upgrades or > other time-wasting activities. There were fixes to things that MIGHT be a cause of an interrupt storm in the em driver, but without knowing more about your specific hardware and the event when it happened its hard to pontificate :) As an aside, I would think getting off 5.3 would be desireable in and of itself :) Can you give a vmstat -i, a pciconf -l, and maybe messages when the storm occurred? Thanks Bill, Jack