Date: Fri, 18 Aug 2006 13:23:15 +0200 From: "Martin Horcicka" <martin@horcicka.eu> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org, Dan Nelson <dnelson@allantgroup.com>, Alan Amesbury <amesbury@umn.edu> Subject: Re: FreeBSD boots too fast on Dell PE850 Message-ID: <437bc1590608180423n513b58c1yd978b2fcf8997ef6@mail.gmail.com> In-Reply-To: <20060818092255.GD55509@cdnetworks.co.kr> References: <44E51C93.5090000@umn.edu> <20060818021643.GA74158@dan.emsphone.com> <437bc1590608180151m1017a50cg31c7817d1aeb0dfe@mail.gmail.com> <20060818092255.GD55509@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
2006/8/18, Pyun YongHyeon <pyunyh@gmail.com>: > On Fri, Aug 18, 2006 at 10:51:07AM +0200, Martin Horcicka wrote: > > 2006/8/18, Dan Nelson <dnelson@allantgroup.com>: > > >In the last episode (Aug 17), Alan Amesbury said: > > >> OK, booting *too* quickly is a somewhat unusual problem..... I have > > >> FreeBSD 6.1-RELEASE-p3 running on a Dell PowerEdge 850. For some > > >> reason, in the PowerEdge 850 Dell chose to replace the perfectly > > >> adequate em(4) adapters found on the PE750 with bge(4) hardware. > > >> FreeBSD identifies these adapters as BCM5750A1, but Dell says they're > > >> actually Broadcom 5721J adapters instead. See > > >> > > >> http://www.dell.com/downloads/global/products/pedge/en/850_specs.pdf > > >> > > >> for details. The switch to which the host is connected is a Cisco > > >> Catalyst 3750. How this relates to FreeBSD, however..... > > > > > >Have you enabled portfast on the Cisco? > > > > > >http://www.cisco.com/warp/public/473/12.html#c2k > > > > We have similar problems on various hardware and we also believe it's > > caused by the Spanning Tree Protocol procedure done during the switch > > port initialization. I don't like the idea of using portfast as it > > makes the switch less robust so I tried to delay the boot using an rc > > script as well: ... > I think it's job of device driver. If the driver find its link > negotiation is in progress it should not send frames. > Unfortunately not all drivers handle this correctly. Unfortunately, I don't know how it works exactly. In our case when the autodetection is disabled and there is e.g. 100/full configured manually on both, switch and the FreeBSD box, ifconfig shows the interface status wery early as "active". I suspect the switch (Cisco) to activate the port (from the point of view of the FreeBSD box) but not to forward any "normal" frames until the Spanning Tree Protocol procedure is finished for that port. But it's just a guess. I don't know the negotiation protocol in Ethernet at all and I would really welcome a commentary from someone who does. Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?437bc1590608180423n513b58c1yd978b2fcf8997ef6>