From nobody Thu Feb 03 16:44:07 2022 X-Original-To: freebsd-current@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 9BAB41989236 for ; Thu, 3 Feb 2022 16:44:09 +0000 (UTC) (envelope-from jsm@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 4JqPdP3z2Fz4pH7; Thu, 3 Feb 2022 16:44:09 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643906649; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Xj493l7DagZjddl1YThELGtjAaa9UVWLav9diLyJSyQ=; b=Ph75pPO32qzGJ2JG/54MLfpMgsuxiT95JyIPlvIQ3mOBHrMBCBdigrFdx1zuKIIIPclOk8 Nl+qdxlY3aqoVh5h4nnaW/jfSV1Q1AYmexz8/dyWGpK886mj8nGQmKmc97Mwvh+6mVCFu2 +XjqMkLDmPuZ2JU7g0ZUAFD4Vdf1AEbycfuC0WNooTl6oJoGwshD9JDmJgOOK4H++UwLqb 9jLolnFsPAa1ZYKbjAqBYQeoswbsV1ZJ4kgnwW9FXTwC6ZAgGinVHA6r1DjYkf6UtrY5ww PZEfUHwa8X3w1V8BlH0rFjBskJEwI14pGVxIWWtYa3SCrL0tQM+KEepFtifrvw== Received: from [IPV6:2a06:4000:c189:1:1::2] (unknown [IPv6:2a06:4000:c189:1:1::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: jsm) by smtp.freebsd.org (Postfix) with ESMTPSA id D260A26D74; Thu, 3 Feb 2022 16:44:08 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <12b6fcc0-9343-63cb-53a3-bfa40c87017c@FreeBSD.org> Date: Thu, 3 Feb 2022 17:44:07 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 Subject: Re: randomdev hangs during initial boot of -current on Raspberry Pi Content-Language: en-US To: Kyle Evans Cc: Mark Millard , Mike Karels , freebsd-current References: <3f375da9-c2a0-8c9e-33e5-d8273e84590c@FreeBSD.org> From: Jesper Schmitz Mouridsen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643906649; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Xj493l7DagZjddl1YThELGtjAaa9UVWLav9diLyJSyQ=; b=D+WiF5+nT5VBm/tD+MCpRDMdfdARTSQs1GS7HWr7uAOLSUbArExjYE3ReQ/nvQ2qPJZxjO BVU7plwCyILywGH3bW8s4UKja68PE+Vy00ONHGsmHbxvK082dUVaoROVcE//g9AJPcz0fU IzUJ5cINziuirCpBck9GRRMjmVoYWLTbzN7rGFLrF22wYh17JHpEC0HoP36GKN6veGqp/3 Xuz5jsMDERZxXZ2WlfVnRHjXaJ13+5RUMAezSW1x11uChUysF+7x5ZZwPvPR+4sPV0JB4d J8Qurw0xC53bFlscjXZKb2f6UNcmEYGqbn0joaVdrsTLH60Nrv9e8L79lgp9VQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643906649; a=rsa-sha256; cv=none; b=ePxqwfdn+b2pgv8tujN7kk6SoaBwEkaB40etKHN6H5fxpETJf0+F1br61tdq/B3eElmBKm IQEA/sg055NhhyQ084nfQiKtNyyt31ir/VgLcP/OfMKbHvy7Wz0DtC5cCe1ErOCKFAIM+c HSrNVxQEQ0H0OzFgyH/AqFpX3y3JJgkkV9V21+pUA60oaOPU83Pgddt3qWX3e2FuaLyoR/ jD8QCV3mHtnuQ+ZOZskLcGedPQdcneEoUzy4Hr5i9LlLYdVsfonfQuBylYDfIkeNskeFUK 5VjQ+D82FSr1vuCEoeWeePD0DaZxVvvEHn+VrgJiANl8Igh2xocFwBjxIxZWHQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 03.02.2022 02.06, Kyle Evans wrote: > On Wed, Feb 2, 2022 at 10:50 AM Kyle Evans wrote: >> On Wed, Feb 2, 2022 at 3:41 AM Jesper Schmitz Mouridsen wrote: >>> >>> >>> On 31.01.2022 22.20, Mark Millard wrote: >>>> Mike Karels wrote on >>>> Date: Mon, 31 Jan 2022 12:27:41 -0600 : >>>> >>>>> A bisect >>>>> would be rather laborious, building a modified SD card each time, >>>>> even if just testing kernel changes. Any other suggestions? >>>> Historically I've used: >>>> >>>> https://artifact.ci.freebsd.org/snapshot/main/?C=M&O=D >>>> >>>> and the likes of kernel.txz (or more) from, for example: >>>> >>>> https://artifact.ci.freebsd.org/snapshot/main/b4cc5d63b6112746598d21413c9800a43171da52/arm64/aarch64/?C=M&O=D >>>> >>>> to update just the kernel (or whatever) and rebooted. >>>> (It can help to have a somewhat older world that is >>>> left in place instead of running newer worlds on older >>>> kernels. Avoiding needing got update world as well has >>>> been helpful when testing for kernel issues.) >>>> >>>> This avoids building the kernels and allows a somewhat >>>> bisect like activity until some subrange has no >>>> arm64/aarch64 artifacts available. >>>> >>>> One can sometimes run into the dates for the sort for: >>>> >>>> https://artifact.ci.freebsd.org/snapshot/main/?C=M&O=D >>>> >>>> not matching up well with the dates on the files of >>>> interest in specific sub directoreis. (Some sort of >>>> directory update?) This can make the bisect far more >>>> difficult, given the choice to not have the directory >>>> names prefixed with text that would sort by a >>>> date/time estimate when sorted by name. (Only using >>>> the commit id/hash completely randomizes the naming.) >>>> >>>> >>>> === >>>> Mark Millard >>>> marklmi at yahoo.com >>>> >>>> >>> Hi >>> My bisect gives: >>> The latest working is: >>> dda9847275da79ccbb2f0b7079b250e28b3b3b2a >>> The excact following commit: >>> 74cf7cae4d2238ae6d1c949b2bbd077e1ab33634 is bad. >>> So 74cf7cae4d2238ae6d1c949b2bbd077e1ab33634 is where the problem starts >>> for me. >>> Hope that someone can explain why >>> 74cf7cae4d2238ae6d1c949b2bbd077e1ab33634 does block entropy/random >>> seeding on first boot around growfs invocation on arm64 >>> /Jsm >>> >> That seems odd, but CC'ing jhb@ -- maybe there's something hinky going >> on since this is before AP startup for arm. > I poked jhb out-of-band and we tracked it down to callouts having been > a major source of entropy for early boot via SWI; tentative fix > pending here: https://reviews.freebsd.org/D34150 > > Thanks, > > Kyle Evans I can confirm it works on  arm64 (Pinebook Pro) Thanks!