From owner-freebsd-stable@freebsd.org Mon Mar 5 14:13:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8DA6F32654 for ; Mon, 5 Mar 2018 14:13:54 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic314-13.consmr.mail.bf2.yahoo.com (sonic314-13.consmr.mail.bf2.yahoo.com [74.6.132.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4E53F7B6E1 for ; Mon, 5 Mar 2018 14:13:54 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: goEsePwVM1kt4NG8d0oWWwQjyvJAMJg07ugZ7KqzSIvR1e8rCuNJ.jF1LzKvtis Mra16OEz3Ns_CFwSvOuiMavq1rL2jUyCe5W1yOQQAgacZqhosatrsgqcY3UdZvh5s.uEJ1fuHuxo Awaz9A8uVWL2Wb9AWtqP6BqHr62Zi.lbBVUT89.V2tgu6Q_B89iy023rLFPQ6N3PEDcs.7JZIRjN t9bVuIoZvxnCoRMS.204Ni81g_YExpxpEonK2tjJP.QoTAI9R_.VHKfy01XYkp35lUshjt_p5IaV OKbYGeyYfsYva95D9UXUNZV1p1ngngh4p4rPxfCzse.DrX39FWA_Lrob.twRXwJNtCvGdQmgNFqn EpoE1pEsFGD1qjOBk7YkJh0V2Mwlp3Uvtx9zNPBLeeIeOrd5s53pb6F.2nfCNhUKqnCirnzfpIRU G2zjJlVrW.dD41jUKGXdKPacO_89mdLdZ0_KsLGXn0do5gd8efgob7HH0H6PkzfY9qFJL Received: from sonic.gate.mail.ne1.yahoo.com by sonic314.consmr.mail.bf2.yahoo.com with HTTP; Mon, 5 Mar 2018 14:13:48 +0000 Received: from smtpgate102.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([72.30.28.113]) by smtp404.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 9efb58d670adf9f13136743092ea88a7 for ; Mon, 05 Mar 2018 14:13:44 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: zfs problems after rebuilding system [SOLVED] Message-Id: Date: Mon, 5 Mar 2018 06:13:42 -0800 To: FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 14:13:54 -0000 Eugene Grosbein eugen at grosbein.net wrote on Mon Mar 5 12:20:47 UTC 2018 : > 05.03.2018 19:10, Dimitry Andric wrote: > >>> When no boot drive is detected early enough, the kernel goes to the >>> mountroot prompt. That seems to hold a Giant lock which inhibits >>> further progress being made. Sometimes progress can be made by trying >>> to mount unmountable partitions on other drives, but this usually goes >>> too fast, especially if the USB drive often times out. >> >> What I would like to know, is why our USB stack has such timeout issues >> at all. When I boot Linux on the same type of hardware, I never see USB >> timeouts. They must be doing something right, or maybe they just don't >> bother checking some status bits that we are very strict about? > > This is heavily hardware-dependent. You may have no issues with some > software+hardware combination and long timeouts with same software > but different hardware. Dimitry's example is for changing the software for the same(?) hardware, if I understand right. (FreeBSD vs. some Linux distribution.) (?: He did say "type of".) Perhaps that type of hardware can be used to figure out the difference. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)