From owner-freebsd-current@FreeBSD.ORG Fri Mar 2 20:09:09 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7AE8106566C for ; Fri, 2 Mar 2012 20:09:09 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 908758FC14 for ; Fri, 2 Mar 2012 20:09:09 +0000 (UTC) Received: by daec6 with SMTP id c6so2544472dae.13 for ; Fri, 02 Mar 2012 12:09:09 -0800 (PST) Received-SPF: pass (google.com: domain of sendtomatt@gmail.com designates 10.68.197.35 as permitted sender) client-ip=10.68.197.35; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sendtomatt@gmail.com designates 10.68.197.35 as permitted sender) smtp.mail=sendtomatt@gmail.com; dkim=pass header.i=sendtomatt@gmail.com Received: from mr.google.com ([10.68.197.35]) by 10.68.197.35 with SMTP id ir3mr20581180pbc.84.1330718949267 (num_hops = 1); Fri, 02 Mar 2012 12:09:09 -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=AKdHMyL/27k1fp36O5AzcruXnvPQiohABoVnfzlvkHM=; b=NfwdYsBzOtChLniYJDfRNJOSbdy28Ae0lj/kSpk0YfHix6hA9rVloWgo4xq5oOOdnH 14ilP0oonME0NgeRjHaCEuVpm6Hjp5VTJkSuzm9ZDfaHvPfLg7i8/cMEF/c7jNuy0Rov 0tI4eU3uJKN7WMoYQsSqNr2ctgXKX9O56Svc4vpnWiYDmIoCo7qcXUXKaFDRZEAnY8OX 7xY11jEty1mhHqyb5IXEm6ieFUbLqnogfVn2dy+EpfQMp2PuE3PBh3zDDxc9aq+aaoE+ A+I4Q6sKI3ioJe68K6KCKDg0D7Up7/7/bS5cRMdmw9nVQuiav1L8Dpg2MX2yye4uFeb0 pDMg== Received: by 10.68.197.35 with SMTP id ir3mr17188991pbc.84.1330718949185; Fri, 02 Mar 2012 12:09:09 -0800 (PST) Received: from bakeneko.local ([74.195.19.178]) by mx.google.com with ESMTPS id k3sm5777135pbn.71.2012.03.02.12.09.07 (version=SSLv3 cipher=OTHER); Fri, 02 Mar 2012 12:09:08 -0800 (PST) Message-ID: <4F512894.4090105@gmail.com> Date: Fri, 02 Mar 2012 12:07:48 -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> In-Reply-To: <4F50597B.5000108@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: Fri, 02 Mar 2012 20:09:09 -0000 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, ver= y > 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 it 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 (igb1)= =2E 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