Date: Sun, 12 Aug 2012 14:07:03 +0430 From: Hooman Fazaeli <hoomanfazaeli@gmail.com> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.0-R em0 issues? Message-ID: <5027793F.5010504@gmail.com> In-Reply-To: <ED9338E3A3D82D0B39DCF79B@Octca64MkIV.tdx.co.uk> References: <26ABB168B4C8E32E7D127EF9@Octca64MkIV.tdx.co.uk> <50261271.50101@gmail.com> <ED9338E3A3D82D0B39DCF79B@Octca64MkIV.tdx.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/11/2012 2:17 PM, Karl Pielorz wrote: > > > --On 11 August 2012 12:36 +0430 Hooman Fazaeli <hoomanfazaeli@gmail.com> wrote: > >>> " >>> Name Mtu Network Address Ipkts Ierrs Idrop >>> Opkts Oerrs Coll em0 1500 <Link#5> 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 >> <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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5027793F.5010504>