From owner-freebsd-stable@freebsd.org Wed Jul 31 15:59:47 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EA8A1A25D7 for ; Wed, 31 Jul 2019 15:59:47 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 45zJ5j3hVXz40c8 for ; Wed, 31 Jul 2019 15:59:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id x6VFxPYU045781 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jul 2019 15:59:26 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: mike@sentex.net Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id x6VFxLbK028373 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Jul 2019 22:59:21 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: extremely slow boot of RELENG_10 To: mike tancsa , freebsd-stable@freebsd.org References: <9f30d6b9-81bb-769c-1a03-1e81277ae07d@sentex.net> From: Eugene Grosbein Message-ID: <776e2f46-7a9e-c299-1c41-f2ca1ee90c32@grosbein.net> Date: Wed, 31 Jul 2019 22:59:16 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <9f30d6b9-81bb-769c-1a03-1e81277ae07d@sentex.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.0 SPF_PASS SPF: sender matches SPF record * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 45zJ5j3hVXz40c8 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-1.24 / 15.00]; ARC_NA(0.00)[]; MX_INVALID(0.50)[greylisted]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grosbein.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_PERMFAIL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.89)[-0.893,0]; IP_SCORE(-0.75)[ipnet: 2a01:4f8::/29(-1.92), asn: 24940(-1.82), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 15:59:48 -0000 31.07.2019 22:30, mike tancsa wrote: > While moving a pair of ZFS disks from an *very* old motherboard to a new > one, I ran into an odd problem I had not seen before. The box was > running just fine RELENG_10 from FreeBSD 10.1-STABLE #18 r279918 on 10yr > old MB. Boots normally and expected speeds for old hardware/CPU. But on > the new one, as soon as the |\-/|\ starts spinning, it looks like its > 1/100th of the speed it should be. Unfortunately, we didnt have the > luxury to wait for it to boot up all the way. We put the disks back in > the old motherboard, did the RELENG_11 upgrade which included putting in > the new boot blocks after zpool upgrade and then the disks booted just > fine in the new box. We at first thought it was a hardware issue, but > same behaviour on another new MB, new SATA cables etc etc. > > Any idea what was going on behind the scenes that might have caused it > ? Is there something about the way the old boot blocks would interact > poorly with new motherboards (in this case, a SuperMicro X11SSH-F) ? Maybe it attempted dual-console boot involving output to serial port...