Date: Wed, 10 Dec 2014 12:05:21 +0000 From: Melissa Jenkins <melissa-freebsd@littlebluecar.co.uk> To: freebsd-net@freebsd.org Subject: Re: IPMI stops respond if boot in single user mode Message-ID: <483358CB-C0C2-4BE7-BE88-5333867801FD@littlebluecar.co.uk> In-Reply-To: <mailman.73.1418212801.43873.freebsd-net@freebsd.org> References: <mailman.73.1418212801.43873.freebsd-net@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 10 Dec 2014, at 12:00, freebsd-net-request@freebsd.org wrote: > > Message: 3 > Date: Wed, 10 Dec 2014 11:09:51 +0300 > From: "Alexey V. Panfilov" <lehis2000@mail.ru> > To: Julian Elischer <julian@freebsd.org>, freebsd-net@freebsd.org > Subject: Re: IPMI stops respond if boot in single user mode > Message-ID: <5487FFCF.10802@mail.ru> > Content-Type: text/plain; charset=koi8-r > >> IMI "shares" the NIC, by which I mean, it uses a backdoor in the chip to >> access it. >> After the driver is loaded, the chip gets reset, but not re-enabled >> until networking is enabled, >> so the backdoor is shut but not re-opened. >> In single user mode the first has happenned, but the second has not. >> >> My suggestion is: >> compile the kernel without the driver. >> load the driver from /etc/rc using the following variable in rc.conf. >> >> kld_list (str) A list of kernel modules to load right after the local >> disks are mounted. Loading modules at this point in >> the boot >> process is much faster than doing it via /boot/loader.conf >> for those modules not necessary for mounting local disk. >> >> let me know how it works out! > > Julian, thanks for your reply. I'll remember this trick. > > But I can't check it now - server goes in production. We had a similar problem with BCE before the drivers were updated. One other solution is to boot to BIOS and disable the onboard network adapter before booting single user. Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483358CB-C0C2-4BE7-BE88-5333867801FD>