From nobody Thu Dec 09 07:56:04 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2D2CE18D2FFB; Thu, 9 Dec 2021 07:56:12 +0000 (UTC) (envelope-from peterj@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4J8mZ36W6Nz3Bv6; Thu, 9 Dec 2021 07:56:11 +0000 (UTC) (envelope-from peterj@freebsd.org) Received: from server.rulingia.com (ppp239-208.static.internode.on.net [59.167.239.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: peterj) by smtp.freebsd.org (Postfix) with ESMTPSA id 38EB54CEF; Thu, 9 Dec 2021 07:56:10 +0000 (UTC) (envelope-from peterj@freebsd.org) Date: Thu, 9 Dec 2021 18:56:04 +1100 From: Peter Jeremy To: Emmanuel Vadot Cc: marklmi@yahoo.com, Mark Millard via freebsd-current , Free BSD , "wma@freebsd.org" Subject: Re: Rock64 configuration fails to boot for main 22c4ab6cb015 but worked for main 06bd74e1e39c (Nov 21): e.MMC mishandled? Message-ID: References: <243CBFC7-DFB5-4F8B-A8A3-CFF78455148D.ref@yahoo.com> <243CBFC7-DFB5-4F8B-A8A3-CFF78455148D@yahoo.com> <20211209081930.7970b6995a8f7c5f7466227d@bidouilliste.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="J6+/LmI2UsdAzFcT" Content-Disposition: inline In-Reply-To: <20211209081930.7970b6995a8f7c5f7466227d@bidouilliste.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639036571; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4pbVLCEhWLw5S1+g0maESBGGdmeJJlcWjzblgNS6L3g=; b=mWzyOtaaNEfwfjY6r/lJfjK8L8NP6YaabcKBbvQnkEuozhEebBMdVld1hARyMXA2EkHyc1 S+Gw3QEZiyMccR6QMEEzl5j5sxwHV7rFHIlqLc9cgNc13WQ60kRhEc+Bfv7B4sUPc2CCgo 3EuEun1iGiJg7ptt+WAc1xzhhlX0h21Wd21gfQZHZrGiDly+SBeawRgnzOFQQF7pJLZ6/Q T9XPWIVK/wtfCiGBF3R9d0NunzxCLe/lKt8K7TSm6eshJ6ik2/Ts7vDFfz7wiZ4zBiZI3V RLCmUKX97/5NdCI6ihgMaggtWnoYthFS7otniMva29Swn4gbKNd2dOZ0FpMNaA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639036571; a=rsa-sha256; cv=none; b=V7jHe5MD6XsfMNsiNYsVX1vr8vkZIG2k9NdqpPG/Qbi6F6dX3BEMrlAak6hrvqWhtm5Fou I76pFQonjkHGOuMf5zV1J01AXZaenbGFocWbvs4DyzOFI60dImflVTkJN4Xwh+IXcs+RvB MAwVA2S4uxYX1SrRfnyFK+edKa6MEhFAw2o6fX8hpyq6IvA/DVFN4dJU83gWHMELwbbU4O unzkBiL1ml6+LiwJ5A1eyOBXa1ZbAjbj7vKwyeZ3Yb+qjjeQOveuXdkJKityZQf4i/l+Z5 CeuRx04rm0kSCM1x2f9YOHtmNxeC3HNfwlbWaDN8/Y8CIpNkE8I88AK6cOmK5g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --J6+/LmI2UsdAzFcT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2021-Dec-09 08:19:30 +0100, Emmanuel Vadot wrote: > > Hi Mark, > >On Wed, 8 Dec 2021 20:36:20 -0800 >Mark Millard via freebsd-current wrote: > >> [ Note: wma@FreeBSD.org is only a guess, based on: >> https://lists.freebsd.org/archives/dev-commits-src-main/2021-December/00= 1931.html ] >>=20 >> Attempting to update to: >>=20 >> main-n251456-22c4ab6cb015-dirty: Tue Dec 7 19:38:53 PST 2021 >>=20 >> resulted in boot failure (showing some boot -v output): [hang just before root is mounted] > Could you try reverting=20 >8661e085fb953855dbc7059f21a64a05ae61b22c "mmc: Fix HS200/HS400 >capability check" and let me know ? I had exactly the same boot failure but was still working backwards through the root mount code trying to isolate the issue. Reverting 8661e085fb953855dbc7059f21a64a05ae61b22c solves the problem for me. I'd noticed the mmc1 difference and mmcsd1 error: mmc1: bus: 8bit, 200MHz (HS200 timing) mmc1: memory: 30310400 blocks, erase sector 1024 blocks mmc1: setting transfer rate to 150.000MHz (HS200 timing) bud I didn't think it was the cause. I had tracked down that the hang was somewhere between https://cgit.freebsd.org/src/tree/sys/kern/vfs_mountroot.c#n779 and https://cgit.freebsd.org/src/tree/sys/kern/vfs_mountroot.c#n1008 which led me to suspect that the problem might be in the geom layer (eg g_waitidle()) but was still considering where to add my next tranche of printf's when I saw Mark's mail. --=20 Peter Jeremy --J6+/LmI2UsdAzFcT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAmGxtotfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzRyaw/+O2tvQyhKuY1h8uEf9bI1ovNWl8g6tLm4cIMotRcsvcsfmi4HgCAxZqTJ 0FYhYvU/kIe+8zWnjHEaHhPnbUYKiy52NB+VAGI2hyGSrA/TGNaxQytrrw/2jIQ8 /IfyCeYjBZHEPlncl59PzjZe3EPyy4ALd8ucQbChCTbpB1CSXIXMKtshWKsdvSen a+vNsUP/W74LTQ7tA3mbP6KnpVJS1aTUSULC2CrpvBugCL+UBziY4bUqFEi1gSAX yZ2DfeUI2aYHJ2ax/HqHIeFjAMEP5RC29v6oKqfpA013TnKFQgSxwZxPet/cpmpu Xq+qwMnfOsq4J8wVmP79uIfgEWOCZWiORZcYhac/0zHwbJoZo39BWMqqNr8YB9ma 4b84QV+wPMyCsTFIjWG5St5d0TYD31/eaHxNv614FNSbZKY+Cycg+xTkIPZI0caB XIfDjDKggeApufKQ2kpzNMH0RmqXWnXaoVfIt7fByR33E4J2za0MDDWBqXS5OGHl CXXtvKGG5cHCDnITC8ljb4Ao8x/Rut3utktQVqtARNu9AwGRpej8VoUi+AbaL6FR xtYGfrAY5VPZ9fCfprc9U/9WeFQ7tA5EHqmj5EBFWzjECHzE8EPHGGutwexIsNPo fT1TQi426eFX+TNjylh8w3/oKuWw6NSrjw2UGfEXBdOX5qlBCfc= =8yfU -----END PGP SIGNATURE----- --J6+/LmI2UsdAzFcT--