From nobody Wed Feb 2 09:40:09 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 5758019A2EBB for ; Wed, 2 Feb 2022 09:40:12 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 4JpcGh25QCz3lMn; Wed, 2 Feb 2022 09:40:12 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643794812; 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=aqn8Hov2HT29V0pvLT0VFQe72ITZR61Q2Pqw4pe+1G4=; b=XioSfqQccb5lBs/W7A43auOdT0adOXwPh3pYtZ1AX0VVCXf9uPUet4cEsUbbOksLS3tEQT VADoQG3xfpwY/eeoEjLUoBPjLMBuSDk5rbOcbWedO2NAn1J6pKXgaMa8HWQB2jVQesXCGT nC46oQmjOjo6ijVr/1j+Me0ojl5VlXGdd9AEozf5sYEvga/mw8iq1Lzz4ounVSYAUbS7aG rcneS8/DVY8/fWqd+UHyjSiSWXFTdDDCZj8ooMa3IE4FzpLEp2tdmJUmtyy/Db0fjRM6Yu O38estnwLtg1fmDhj6plgZA3v6a3zPnKBpt7MAx/lkp2109mlWvVspyhuWIfLA== Received: from [192.168.1.5] (mail.northatlanticmusicsupplies.com [212.237.182.202]) (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 AFB1C7BE5; Wed, 2 Feb 2022 09:40:11 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <3f375da9-c2a0-8c9e-33e5-d8273e84590c@FreeBSD.org> Date: Wed, 2 Feb 2022 10:40:09 +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: Mark Millard , Mike Karels Cc: freebsd-current References: From: Jesper Schmitz Mouridsen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643794812; 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=aqn8Hov2HT29V0pvLT0VFQe72ITZR61Q2Pqw4pe+1G4=; b=RvtnBXKjCFUDmaPJSZiRkDpqmV9sb43V9l45mwz6QJ3Og5hj5QlGPNIN3ByXW6U79qCBIa KuJU6BmBT3G2454BWZIl3laL5TAo2FwLLkcaDffYUZxeWOfKDm+Djize7ypbkCp8sX0NkT x1BjFE5NNdouSPmZ3MueavCdU75amzdnDKrTiGUpyvxTH0OzLOTDwAPLpYPgc75NaFjI8P +iAVggzQSCCqEatMItW3bCU4NTp0fHDvervp6AjoqV1PHdE9PZcft9OPNO/8Ces2vPD3Lx /HpYBYWQtJu6YM28o3YyX5Eb/DMIIp8fQKftYt3jL/L6t9I/4KYINNDWONd3SA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643794812; a=rsa-sha256; cv=none; b=n020xNGQAM6xrcOayqCislBPO0KUgwyAgHSrqFoAZsXMIMo4yTIEivwTI3Ry9+7XNobc5C 3iiatJyQGIpvt6uZI0gffMGENsnlyaSL+51xplB3NunyY52HFXBr+7L0JAKPNJIFwAsF6H rl+UAGiUmvHnWJWSwOIoO+45Iv1rgy94M5t5t7pn0GfO6oTyKwcYm+PhPNsIPw331BnBK+ 28QPNQlV3KMnJ3TDcKItrzYZwxaM/z9x0r1TDrwbl+D+msu8S3x7o2fznTyyRnz7DVMavy YYImDtAp0xP5fBe64j6cDzPMLDDFUMVevbcaE90PkPS5lYKcK+PRnK1HsN1pww== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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