Date: Sat, 19 Apr 2008 22:12:45 +0900 From: "George V. Neville-Neil" <gnn@neville-neil.com> To: "Jack Vogel" <jfvogel@gmail.com> Cc: jfv@freebsd.org, stable@freebsd.org, Jeremy Chadwick <koitsu@freebsd.org> Subject: Re: Problems with em0 failing to initialize on stable? Message-ID: <m2prsm3s4y.wl%gnn@neville-neil.com> In-Reply-To: <2a41acea0804171032y239913efq3163edb67fc468a0@mail.gmail.com> References: <m2ej94rfm7.wl%gnn@neville-neil.com> <20080417112035.GA81275@eos.sc1.parodius.com> <0528764C-4B25-4063-B018-EFD2750ACBDB@altesco.nl> <20080417141139.GA84832@eos.sc1.parodius.com> <4DE42652-2CE8-4567-AD49-2F425917A232@altesco.nl> <2a41acea0804171032y239913efq3163edb67fc468a0@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 17 Apr 2008 10:32:33 -0700, Jack Vogel wrote: > > On Thu, Apr 17, 2008 at 8:28 AM, Ben Stuyts <ben@altesco.nl> wrote: > > > > > > On 17 apr 2008, at 16:11, Jeremy Chadwick wrote: > > > > > > > On Thu, Apr 17, 2008 at 02:02:51PM +0200, Ben Stuyts wrote: > > > > > > > On 17 apr 2008, at 13:20, Jeremy Chadwick wrote: > > > > > > > > > On Thu, Apr 17, 2008 at 06:32:32PM +0900, gnn@freebsd.org wrote: > > > > > > > > > > > I am running 7-STABLE with machines that are net booted. On > > occasion, > > > > > > that is not with any level of predictability, this happens: > > > > > > > > > > > > em0: Hardware Initialization Failed > > > > > > em0: Unable to initialize the hardware > > > > > > > > > > > > which of course stops the machine in its tracks. A normal dmesg is > > > > > > also included. > > > > > > > > > > > > Any steps I should take to help debug this? > > > > > > > > > > > > > > > > George, can you provide the following? > > > > > > > > > > * Motherboard type and model (a URL to the board would be good) > > > > > * kenv | grep smbios > > > > > * pciconf -lv > > > > > > > > > > > > > I have seen this too. A couple of times on a new server here. Maybe one > > in > > > > two or three reboots. So far, it only happens after a reboot, but not > > after > > > > a hard reset or power cycle. This board has 3 em network if's. Two on > > the > > > > board itself, and one on a daughter card on the ipmi add-on card. It is > > > > always em0 that is giving trouble. The board is a Supermicro X7DBP-i: > > > > > > <http://www.supermicro.com/products/motherboard/xeon1333/5000P/X7DBP-i.cfm>; > > > > > > > > > > I'm wondering if the IPMI add-on is what's doing it. However, the IPMI > > > cards compatible with the X7DBP all have a dedicated NIC (versus > > > piggybacking on top of the existing mainboards' NICs, which almost > > > always causes problems of the mysterious sort). I'm not sure, but I > > > don't think em0 will be that NIC. > > > > > > > Correct, em0 and em1 are on the mainboard. em2 is on the > > daughter-daughtercard and also single use for the OS. And then there's a 4th > > nic which is the ipmi interface. It is completely separate. (I have the > > SIM1U-3B & SIM1U-3D daughter cards: > > <http://www.supermicro.com/products/accessories/addon/SIM.cfm>; > > > > > > > > > Both you and George have boards that use the 82563EB. jv@ will have to > > > help with this one. I wonder if it's a BIOS bug of some kind, where > > > something on the NIC isn't getting reset by the BIOS on a soft boot... > > > > > > > Let me know if there's anything I can do to help. I can test patches during > > evening hours when this server is mostly idle. > > > > Ben > > > > > > There is a fix in the shared code that is checked into CURRENT that > addresses this, however, yesterday evening a problem cropped up that > might still be unfixed with that code, I'm looking into that > today... Once that's fixed can it be MFC'd? Best, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2prsm3s4y.wl%gnn>