Date: Tue, 8 Sep 1998 21:08:35 -0700 (PDT) From: Bill Paul <wpaul> To: gibbs@plutotech.com (Justin T. Gibbs) Cc: cvs-committers@freebsd.org Subject: Re: cvs commit: src/sys/pci if_xl.c Message-ID: <199809090408.VAA13781@hub.freebsd.org> In-Reply-To: <199809090153.TAA02512@pluto.plutotech.com> from "Justin T. Gibbs" at "Sep 8, 98 07:47:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> >wpaul 1998/09/08 16:42:10 PDT > > > > Modified files: > > sys/pci if_xl.c > > Log: > > ... > > > - Disable the 'background' autonegotiation performed during bootstrap. > > What happens currently is that the driver starts an autoneg session, > > the sets a timeout in the ifnet structure and returns. Later, when the > > timer expires, the watchdog routine calls the autoneg handler to check > > the results of the session. The problem with this is that the session > > may not complete until some point after we have started to mount NFS > > filesystems, which can cause the mounts to fail. This is especially > > troublesome if booting with an NFS rootfs: we need the interface up > > and running before reaching the mountroot() code. > > This is what the interrupt driven config hook mechanism is designed to > address. It fires your hook once interrupt and timeout services are > available and prevents the system boot from continuing until you remove > your hook. See kern/subr_autoconf.c for details. Ooooo.... awesome!!! This is just what I need! Thankyouthankyouthankyou! Hm. You know, I noticed with the Dell machines and the Adaptec 3895 controller that the probe messages for the disk controller appear during the PCI bus probe, but the probe messages for the disks themselves don't show up until the very end. In fact, they appear _after_ the message that says 'changing root device to da0s2a'. Is take it this is because the CAM code is also using this mechanism, yes? -Bill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809090408.VAA13781>