From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 23:55:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D4B0106564A for ; Sat, 3 Mar 2012 23:55:47 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 03F738FC12 for ; Sat, 3 Mar 2012 23:55:46 +0000 (UTC) Received: by dakl33 with SMTP id l33so9109319dak.17 for ; Sat, 03 Mar 2012 15:55:46 -0800 (PST) Received-SPF: pass (google.com: domain of sendtomatt@gmail.com designates 10.68.204.129 as permitted sender) client-ip=10.68.204.129; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sendtomatt@gmail.com designates 10.68.204.129 as permitted sender) smtp.mail=sendtomatt@gmail.com; dkim=pass header.i=sendtomatt@gmail.com Received: from mr.google.com ([10.68.204.129]) by 10.68.204.129 with SMTP id ky1mr32061994pbc.21.1330818946697 (num_hops = 1); Sat, 03 Mar 2012 15:55:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=JKfqPDxPfXe9udCtYLy0hoiEHUXmCcYdz9M4P/eSX3I=; b=D4TtZfPwG5lvgztGR1HzYS7EFQCIvvDicI+Y4EvaQXVkY36iTD7quoT+zvb4c5r6yx 3rmFv1WlJfw846Qsi6Z7uc5LJ4lQbhJvxupjZdeYSt3MWAPnvt0dZrcmbNplYRp1NV6m DZV9yN7aq67WlqzE8ZAxdP/qtV/bQlOvrcB/qj8CF2tIdK7lIoIRq33WzwgUQTZRFMtM bwrESjZ9LMp6xmySx0bmJDmB219A/UG72Mzqih4MmCHBQfVXAPNNDWAVlbNBq9cpjHtR Pyt0psc67VmFMZ4m+w9J876M5QdIAzEpNl7YvASkLejSFL4dbZmhF1+H/IR2U3N5zswc N6GA== Received: by 10.68.204.129 with SMTP id ky1mr27204060pbc.21.1330818946664; Sat, 03 Mar 2012 15:55:46 -0800 (PST) Received: from bakeneko.local (70-36-223-154.dsl.dynamic.sonic.net. [70.36.223.154]) by mx.google.com with ESMTPS id f3sm8938250pbr.61.2012.03.03.15.55.44 (version=SSLv3 cipher=OTHER); Sat, 03 Mar 2012 15:55:45 -0800 (PST) Message-ID: <4F52AF32.2020703@gmail.com> Date: Sat, 03 Mar 2012 15:54:26 -0800 From: matt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120301 Thunderbird/10.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4F50597B.5000108@gmail.com> <4F512894.4090105@gmail.com> In-Reply-To: <4F512894.4090105@gmail.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: if_igb crashes system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 03 Mar 2012 23:55:47 -0000 On 03/02/12 12:07, matt wrote: > On 03/01/12 21:24, matt wrote: >> bringing up igb0 is currently causing my 10-CURRENT box to become very= >> non-responsive (as though downclocked to some 100 KHZ...very, very, ve= ry >> slow). >> >> cmdwatch 'vmstat -i' shows the interrupts get assigned for igb0, and >> about 1 second later the machine is essentially non-responsive. >> >> anyone else seeing if_igb issues suddenly? >> the machine is running off a cvsup from about 75 minutes ago. >> >> I was only able to access the system after removing interface configs >> from rc.conf, which made me suspect polling initially, however even >> issuing "ifconfig igb0 up" with no media causes the issue to appear. >> >> Let me know what additional diagnostic data may help? >> >> Matt >> > Last time this machine was updated was last week. > I'm going to have to install something else to test the hardware, but i= t > had no problems until first reboot with new kernel. > I have blown away /usr/src and re fetched it...no change. > I've disabled pf and tried to bring it up...no change > I've tried to bring up the other interface in the pair...no change (igb= 1). > It doesn't look like the msix commit from jhb has anything to do with > it...didn't exactly revert but changed return(0); back to > return(msgs);...no change > > I'm down to either the hardware conveniently failed during upgrade, or > some earlier commit. > Luckily I have an em-based port as well. > I'm testing hardware next and then going further back into the week on > the commit log? > Anyone else with igb out there and working with latest HEAD? > > Matt > > igb is working now, I rebuilt world as of this afternoon and it appears to be stable. Sorry for the noise & thanks, Matt