From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 13:37:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5CE3D38; Fri, 22 Feb 2013 13:37:33 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 2AF51FC2; Fri, 22 Feb 2013 13:37:32 +0000 (UTC) Received: from dagger.cc.vt.edu (dagger.cc.vt.edu [198.82.163.114]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id r1MDb1ba022562; Fri, 22 Feb 2013 08:37:01 -0500 Received: from auth3.smtp.vt.edu (EHLO auth3.smtp.vt.edu) ([198.82.161.152]) by dagger.cc.vt.edu (MOS 4.3.3-GA FastPath queued) with ESMTP id YUZ00677; Fri, 22 Feb 2013 08:37:01 -0500 (EST) Received: from pmather.tower.lib.vt.edu (pmather.tower.lib.vt.edu [128.173.51.28]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id r1MDb091030185 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 22 Feb 2013 08:37:00 -0500 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: IPMI serial console From: Paul Mather In-Reply-To: <20130222042907.GA75261@icarus.home.lan> Date: Fri, 22 Feb 2013 08:37:00 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51269ABD.2040308@gmail.com> <2AF6F8E4-A45E-4D4C-9232-FF09AD4A3641@gsoft.com.au> <5126A3A1.1030208@gmail.com> <64293C7A-038A-4EA1-B394-9E80CFCBC14F@gsoft.com.au> <20130221230001.GF2598@kib.kiev.ua> <20130221232929.GA91708@icarus.home.lan> <3FE71C9F-29B2-48F5-9A51-D312B1803E14@gsoft.com.au> <20130222013258.GA93350@icarus.home.lan> <9F6E4B36-0C89-4409-91FB-08CC90848D23@gsoft.com.au> <20130222042907.GA75261@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1499) X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu paul@gromit.dlib.vt.edu 5 none X-Junkmail-Status: score=10/50, host=dagger.cc.vt.edu X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A020201.5127747D.019E,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=single engine X-Junkmail-IWF: false Cc: Konstantin Belousov , freebsd-stable@freebsd.org, John Baldwin , Navdeep Parhar X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 13:37:33 -0000 On Feb 21, 2013, at 11:29 PM, Jeremy Chadwick wrote: > On Fri, Feb 22, 2013 at 02:22:52PM +1030, Daniel O'Connor wrote: >> On 22/02/2013, at 12:02, Jeremy Chadwick wrote: >>>> Hmm I tried putting '-S 115200' in /boot.config and it broke - the = boot process didn't run the loader (or kernel). >>>=20 >>> I'll talk a bit about this -- again, sorry for the verbosity. I'll >>> explain what I've historically used/done, then speculate a bit about >>> your IPMI stuff: >>>=20 >>> For me, on systems without IPMI, all I had to do was this (and = nothing >>> else): >>>=20 >>> * Put the following in /boot.config: >>>=20 >>> -S115200 -Dh >>=20 >> This breaks the boot for me, boot.config has to contain more than = just >> flags it seems. In any case I believe setting boot_multicons and >> boot_serial is the same as -Dh. Not sure about the baud rate though. >=20 > Then someone broke something (parser or something else). This has > always, *always* worked (just flags). The last time I verified it was > with the release of 9.0-RELEASE. I do have a system I could test this > on, but I'd need to find a null modem cable first. >=20 > I have seen some MFCs that touch those bits in the bootloader, but = from > my memory it didn't touch anything other than supporting /boot/config = as > an alternate location to the classic /boot.config file. I would be = very > surprised if this broke it. >=20 > I can assure you that those were the only flags that were needed, and = in > exactly that syntax. Even the Handbook has this in it, as well as > boot(8). >=20 > I believe your explanation of boot_multicons and boot_serial are = correct > and do correlate with -D and -h. I could look at the bootstrap code = to > verify. The options are described in loader(8) but not = loader.conf(5). I think something did break back at the start of the year that caused = /boot.config contents to render the system completely unbootable. At = least that is what happened to me on RELENG_8: = http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071579.html= Bruce A. Mah reports later in the same thread that his happened to him = on 8.3-RELEASE. I don't know if this was fixed. Cheers, Paul.=