Date: Tue, 12 Aug 2014 17:39:23 -0700 From: Barney Cordoba <barney_cordoba@yahoo.com> To: John Nielsen <lists@jnielsen.net> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: Booting a SuperMicro Superserver Message-ID: <1407890363.54477.YahooMailNeo@web121603.mail.ne1.yahoo.com> In-Reply-To: <0F76C4E8-A71F-4192-9AE0-9E54F02DFBE1@jnielsen.net> References: <1407861156.35826.YahooMailNeo@web121606.mail.ne1.yahoo.com> <0D393AB7-4632-4BF8-95A3-D8AF25D53E60@jnielsen.net> <1407866979.73449.YahooMailNeo@web121604.mail.ne1.yahoo.com> <0F76C4E8-A71F-4192-9AE0-9E54F02DFBE1@jnielsen.net>
next in thread | previous in thread | raw e-mail | index | archive | help
So there is. But I still don't see how this can happen. The default is P0 f= irst and P1 second and it certainly wasn't changed, but it still seems to b= oot from the second drive when both are present. It's almost like there's s= ome logic that says "drive P1 has the same kernel booted the last time, so = lets use that instead of the new one in P0". =A0 It's happened more than on= ce in remote locations that is a PIA to pop the 2nd drive.=A0I'll have to t= ry a few things. Easy enough to build a new kernel and see which it boots= =0A=0A=0AOn Tuesday, August 12, 2014 2:24 PM, John Nielsen <lists@jnielsen.= net> wrote:=0A =0A=0A=0AOn Aug 12, 2014, at 12:09 PM, Barney Cordoba <barne= y_cordoba@yahoo.com> wrote:=0A=0A> On Tuesday, August 12, 2014 1:16 PM, Joh= n Nielsen <lists@jnielsen.net> wrote:=0A> =0A>> On Aug 12, 2014, at 10:32 A= M, Barney Cordoba <barney_cordoba@yahoo.com> wrote:=0A>> =0A>>> A continuin= g issue (with 9.1 previously and now 10) is that FreeBSD occasionally (or a= lways) seems to boot from the 2nd installed drive rather than the first. I'= d be happy to debug this, but I have no idea if it's bootcode or a BIOS iss= ue. Supermicro pleads innocent, but their bios guys are hard to work with a= nd fairly arrogant if you don't specifically isolate something.=0A>>> =0A>>= > The scenario occurs when ada0 is upgraded and has an incompatible kernel = with other code on drive ada1.=A0 (note that ada1 is a backup of the pre-up= grade ada0, so it's fstab points to ada0 for mount points). The system will= boot and then modules will fail to load. It loads the kernel from ada1 and= then mounts partitions from ada0; old kernel and newer modules.=0A>>> =0A>= >> The problem is resolved by popping the 2nd drive. So there is nothing wr= ong with ada0 to cause it to bounce to ada1.=0A>>> =0A>>> My question: What= would cause the system to boot from ada1 instead of ada0? Bios or Bootcode= ?=0A>> =0A>> BIOS, most likely. If the disk controller in question is onboa= rd you should be able to specify which disk(s) and what order they will be = booted from. If not, you'll need to just say <disk controller> in the BIOS = boot order then go to the controllers BIOS to say which disk(s) to boot fro= m and in what order. I have recent experience with a SuperMicro box and an = LSI controller; the latter allows you to specify a (b)oot drive and an (a)l= ternate. Yes, b comes before a. :)=0A> =0A> The bios only gives you one cho= ice for "HDD". You can't select one of the 4 drives to boot from. You can s= pecify USB or CD or HDD, but Not HDD2 or HDD3.=0A=0AThere may be a separate= option controlling "hard drive boot order", and/or there may be a complete= ly separate BIOS program for your drive controller with its own hotkey.=0A= =0A=0AJN From owner-freebsd-current@FreeBSD.ORG Wed Aug 13 06:17:39 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1EF1D65 for <freebsd-current@freebsd.org>; Wed, 13 Aug 2014 06:17:39 +0000 (UTC) Received: from graal.it-profi.org.ua (graal.shurik.kiev.ua [193.239.74.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AC05B23EE for <freebsd-current@freebsd.org>; Wed, 13 Aug 2014 06:17:38 +0000 (UTC) Received: from [217.76.201.82] (helo=thinkpad.it-profi.org.ua) by graal.it-profi.org.ua with esmtpa (Exim 4.83 (FreeBSD)) (envelope-from <shuriku@shurik.kiev.ua>) id 1XHRsH-000Dhx-NG; Wed, 13 Aug 2014 09:17:29 +0300 Message-ID: <53EB02F4.1020704@shurik.kiev.ua> Date: Wed, 13 Aug 2014 09:17:24 +0300 From: Alexandr Krivulya <shuriku@shurik.kiev.ua> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: chmeeedalf@gmail.com Subject: Re: Child suspend/resume References: <20140810223030.479badbc@zhabar.att.net> <53E9CDD5.6020507@shurik.kiev.ua> <20140812070616.62c66567@zhabar.att.net> In-Reply-To: <20140812070616.62c66567@zhabar.att.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 217.76.201.82 X-SA-Exim-Mail-From: shuriku@shurik.kiev.ua X-SA-Exim-Scanned: No (on graal.it-profi.org.ua); SAEximRunCond expanded to false Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 13 Aug 2014 06:17:40 -0000 Now laptop resumes, screen turned on and I see in dmesg "acpi: resumed at ...", but neither keyboard nor mouse don't work and host is not accessible from network. 12.08.2014 17:06, Justin Hibbits пишет: > Hi Alexandr, > > Thanks. I got another confirmation that it didn't work, and may have > found the cause. I have another patch that you can find at > https://phabric.freebsd.org/D590 which fixes a typo that I had made. > Could you try that? > > (Added current@ so everyone else sees this as well). > > Thanks! > > - Justin > > On Tue, 12 Aug 2014 11:18:29 +0300 > Alexandr Krivulya <shuriku@shurik.kiev.ua> wrote: > >> Hi, Justin >> After applying your patch my thinkpad e530 (FreeBSD 11.0-CURRENT, >> amd64) doesn't resume any more - screen remains black. >> >> 11.08.2014 08:30, Justin Hibbits (by way of Justin Hibbits >> <chmeeedalf@gmail.com>) пишет: >>> Hi all, >>> >>> The attached patch is completely untested, due to lack of existing >>> suspendable hardware (no x86 machines). It does compile cleanly >>> against head, though. I don't think it should change any behavior, >>> I tried to keep the essence of the code path the same. >>> >>> It was suggested that I break up my multipass suspend/resume code >>> into incremental parts, so this is part one. It adds a >>> BUS_SUSPEND_CHILD/BUS_RESUME_CHILD, as well as helper functions, >>> bus_generic_suspend_child()/bus_generic_resume_child(), and modifies >>> the PCI driver to use this new facility. >>> >>> I'd like some feedback, and testing of this, to make sure I didn't >>> break anything. >>> >>> Thanks, >>> Justin >>> >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1407890363.54477.YahooMailNeo>