Date: Mon, 21 Jan 2008 13:58:27 +0300 From: Vladimir Ivanov <wawa@yandex-team.ru> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org, Andrew Snow <andrew@modulus.org> Subject: Re: 7.0-RC1 onboard em1 intel pro1000 vanishing occasionally Message-ID: <47947AD3.2040708@yandex-team.ru> In-Reply-To: <2a41acea0801201226t3f7eb2d0qfd12102d1d480529@mail.gmail.com> References: <4793072F.9030909@modulus.org> <2a41acea0801201226t3f7eb2d0qfd12102d1d480529@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, All Jack Vogel wrote: > Hi Andrew, > > Someone else has already reported this to me and in fact he is testing > a shared code > fix to see if it resolves it. I will be updating the driver if it does. > > Jack > We've same issue w/Supermicro boards if IPMI daughterboard installed. A problem looks as PHY reg reads/writes fails. I suppose they use buggy (incompatible) technique to make "virtual lan" channel for remote KVM support. On some systems we can start interfaces via warm boot, sometimes not, sometimes we can recover it w/powercord unplug, sometimes - not. 100% workaround: remove IPMI daughterboard. Also, I've a several systems w/IPMI which works Ok. > On Jan 20, 2008 12:32 AM, Andrew Snow <andrew@modulus.org> wrote: > >> Hi, >> >> I have a recent Supermicro board (Super X7DWT >> Intel 5400 chipset) with two onboard NICs - Intel (ESB2/Gilgal) 82563EB >> Dual-Port Gigabit Ethernet Controller >> >> >> >> Usually boot up looks like this: >> >> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port >> 0x3000-0x301f mem 0xda020000-0xda03ffff,0xda000000-0xda01ffff irq 44 at >> 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 >> 0x3020-0x303f mem 0xda060000-0xda07ffff,0xda040000-0xda05ffff irq 40 at >> device 0.1 on pci5 >> em1: Using MSI interrupt >> em1: Ethernet address: 00:30:48:7e:20:e1 >> em1: [FILTER] >> >> Sometimes when I reboot this happens: >> >> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port >> 0x3000-0x301f mem 0xda020000-0xda03ffff,0xda000000-0xda01ffff irq 44 at >> 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 >> 0x3020-0x303f mem 0xda060000-0xda07ffff,0xda040000-0xda05ffff irq 40 at >> device 0.1 on pci5 >> em1: Using MSI interrupt >> em1: Setup of Shared code failed >> device_attach: em1 attach returned 6 >> >> And em1 does not exist after that. Power cycling the machine seems to >> fix it for the next boot. >> >> >> Any suggestions? >> >> [skip] Trully, -- Vladimir Ivanov Network Operations Center OOO "Yandex" t: +7 495 739-7000 f: +7 495 739-7070 @: noc@yandex.net (corporate) wawa@yandex-team.ru (personal) www: www.yandex.ru --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47947AD3.2040708>