Date: Mon, 10 Jan 2011 23:41:03 +0000 From: FRLinux <frlinux@gmail.com> To: Chris Brennan <xaero@xaerolimit.net> Cc: freebsd-questions@freebsd.org Subject: Re: problem booting a new server on FreeBSD Message-ID: <AANLkTinQ6Rhe4qda1M1hx%2B1w%2BbbXpObEx-eexxc_pFoM@mail.gmail.com> In-Reply-To: <AANLkTikBXDimeYG1UhUTT4MArfHq0UzG-xY5dDbz8V=q@mail.gmail.com> References: <AANLkTikZQnhK%2Bg9uexuLdc8RtS2cTrp0Z4LZm4E%2BZa%2Bo@mail.gmail.com> <AANLkTikfPBy6J_z6bwK-JBe=s=-BuVhJ4Xm%2BppLmL7Z=@mail.gmail.com> <AANLkTikBXDimeYG1UhUTT4MArfHq0UzG-xY5dDbz8V=q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 10, 2011 at 11:29 PM, Chris Brennan <xaero@xaerolimit.net> wrote: > Where during the boot process does this happeb? As soon as you select any of the options of the boot (normal boot, boot without ACPI, boot single mode, etc...). It sits there for about 1mn to 1mn30 and then boots fine. We put the second server in production today, same CPU type and motherboard, same behavior. Cheers, Steph
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinQ6Rhe4qda1M1hx%2B1w%2BbbXpObEx-eexxc_pFoM>