From owner-freebsd-net@FreeBSD.ORG Sun Aug 12 09:37:17 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4781E1065674 for ; Sun, 12 Aug 2012 09:37:17 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id C12FE8FC14 for ; Sun, 12 Aug 2012 09:37:15 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so2437180wgb.31 for ; Sun, 12 Aug 2012 02:37:14 -0700 (PDT) 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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ihm+8og9T5R4QPItpb/Fm0e7mf6HhiVIP05S63Ib6GE=; b=puAz8tr1w10mEM94umMeLthiEv7m8aWnyg6OVwfxXh7jvFOX/GMrWr+y9hvKHsiy22 Y5jmiLVek/2LOXtZFroJha6ds3gFGTk4e/5UZx4GlCBjEO63GNiWoHF8leb2Ub9Ewfcx 4sQOFPE2VAW/w6PpxSvZNAqIZEmsvWI8wwKFUI2kvQyR8nwrFJ+x0Xet35Wd+nU8lIyp gIcYlZebkU/VxC56aPB+0dc5gcH1sh8suKwjlpZca8NBtuluH+U4SJ+PdG9q+yrASM98 yliC8Sco9CHYQS3wvB/IwrdtNZWCJ7ENdmO3WoS1pHqYBw2R3iKMAW5Tyi1ZafTh8bdc LiLA== Received: by 10.180.85.167 with SMTP id i7mr9546103wiz.8.1344764234613; Sun, 12 Aug 2012 02:37:14 -0700 (PDT) Received: from [127.0.0.1] ([84.241.57.181]) by mx.google.com with ESMTPS id o2sm13412672wiz.11.2012.08.12.02.37.11 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 12 Aug 2012 02:37:13 -0700 (PDT) Message-ID: <5027793F.5010504@gmail.com> Date: Sun, 12 Aug 2012 14:07:03 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.28) Gecko/20120306 Thunderbird/3.1.20 MIME-Version: 1.0 To: Karl Pielorz References: <26ABB168B4C8E32E7D127EF9@Octca64MkIV.tdx.co.uk> <50261271.50101@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.0-R em0 issues? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2012 09:37:17 -0000 On 8/11/2012 2:17 PM, Karl Pielorz wrote: > > > --On 11 August 2012 12:36 +0430 Hooman Fazaeli wrote: > >>> " >>> Name Mtu Network Address Ipkts Ierrs Idrop >>> Opkts Oerrs Coll em0 1500 00:25:90:31:82:46 355482 >>> 10612864185945 0 291109 3032246910270 1516123455135 " >> 82574L with ASPM enabled is known to cause a problem like yours. >> (See:http://www.google.com/#hl=en&sclient=psy-ab&q=82574L+%2B+ASPM >> ) >> However, some time ago, jack committed a fix which disabled ASPM to fix >> the problem. >> I recommend getting and compiling latest e1000 source from CVS (which is >> version 7.3.2) >> and see what happens. > > Hi, > > In the midst of trying to get this onto the machine (without the NIC working - which was fun), during a reboot the NIC suddenly disappeared completely. > > Rebooting the machine again gives a 50/50 on the NIC probing when FreeBSD runs up - half the time I'm left with em1 only, and no em0. > > It looks like this has gone from a 'possible software' issue to a 'probable hardware' issue now? - I've moved the connection over to em1, I'll see how I get on with that. > I have also seen this problem on a different hardware but I can not recall if I fixed it with hardware replacement or driver update. Anyway, it is worth to give the driver update a try.