From owner-freebsd-net@FreeBSD.ORG Mon Mar 3 18:59:11 2008 Return-Path: <owner-freebsd-net@FreeBSD.ORG> Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 780EC1065692 for <freebsd-net@freebsd.org>; Mon, 3 Mar 2008 18:59:11 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 4F5678FC14 for <freebsd-net@freebsd.org>; Mon, 3 Mar 2008 18:59:11 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <bounces@nabble.com>) id 1JWFsU-00032b-I5 for freebsd-net@freebsd.org; Mon, 03 Mar 2008 10:59:10 -0800 Message-ID: <15811094.post@talk.nabble.com> Date: Mon, 3 Mar 2008 10:59:10 -0800 (PST) From: Oznon <the_oznon@yahoo.com> To: freebsd-net@freebsd.org In-Reply-To: <4793072F.9030909@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: the_oznon@yahoo.com References: <4793072F.9030909@modulus.org> Subject: Re: 7.0-RC1 onboard em1 intel pro1000 vanishing occasionally X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net> List-Post: <mailto:freebsd-net@freebsd.org> List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 03 Mar 2008 18:59:11 -0000 Hi all, I am currently experiencing the same issue as well except this time around with a Supermicro X7DBU motherboard (Intel=C2=AE 5000P (Blackford) Chipset)= . The identical occurence is happening to me as well so we were wondering if anyone had a resolution? Possibly an updated driver for the Intel NIC card?= =20 Anywho, here is a snippet of the a particular error we receive before the interface disappears: em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x2000-0x201f mem 0xd8920000-0xd893ffff,0xd8900000-0xd891ffff irq 18 at device 0.0 on pci5 em0: Using MSI interrupt em0: Ethernet address: 00:30:48:7f:be:38 em0: [FILTER] em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 0x2020-0x203f mem 0xd8960000-0xd897ffff,0xd8940000-0xd895ffff irq 19 at device 0.1 on pci5 em1: Using MSI interrupt em1: Setup of Shared code failed Thanks all, Guy Andrew Snow-2 wrote: >=20 >=20 > Hi, >=20 > I have a recent Supermicro board (Super X7DWT > Intel 5400 chipset) with two onboard NICs - Intel (ESB2/Gilgal) 82563EB= =20 > Dual-Port Gigabit Ethernet Controller >=20 >=20 >=20 > Usually boot up looks like this: >=20 > em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port=20 > 0x3000-0x301f mem 0xda020000-0xda03ffff,0xda000000-0xda01ffff irq 44 at= =20 > device 0.0 on pci5 > em0: Using MSI interrupt > em0: Ethernet address: 00:30:48:7e:20:e0 > em0: [FILTER] > em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port=20 > 0x3020-0x303f mem 0xda060000-0xda07ffff,0xda040000-0xda05ffff irq 40 at= =20 > device 0.1 on pci5 > em1: Using MSI interrupt > em1: Ethernet address: 00:30:48:7e:20:e1 > em1: [FILTER] >=20 > Sometimes when I reboot this happens: >=20 > em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port=20 > 0x3000-0x301f mem 0xda020000-0xda03ffff,0xda000000-0xda01ffff irq 44 at= =20 > device 0.0 on pci5 > em0: Using MSI interrupt > em0: Ethernet address: 00:30:48:7e:20:e0 > em0: [FILTER] > em1: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port=20 > 0x3020-0x303f mem 0xda060000-0xda07ffff,0xda040000-0xda05ffff irq 40 at= =20 > device 0.1 on pci5 > em1: Using MSI interrupt > em1: Setup of Shared code failed > device_attach: em1 attach returned 6 >=20 > And em1 does not exist after that. Power cycling the machine seems to=20 > fix it for the next boot. >=20 >=20 > Any suggestions? >=20 >=20 > Regards, >=20 > - Andrew > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >=20 --=20 View this message in context: http://www.nabble.com/7.0-RC1-onboard-em1-int= el-pro1000-vanishing-occasionally-tp14979560p15811094.html Sent from the freebsd-net mailing list archive at Nabble.com.