From nobody Wed Feb 02 16:50:02 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 2D3A219B276B for ; Wed, 2 Feb 2022 16:50:14 +0000 (UTC) (envelope-from kevans@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 4Jpnpt0V82z3FkZ; Wed, 2 Feb 2022 16:50:14 +0000 (UTC) (envelope-from kevans@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643820614; 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=9p7TuR82uOOU0Xa5QUozyvizuFYg2wVK+SqfbDRK82U=; b=Lky6ZtF9S63K3aV/rNj6I3EgirbO7L9KqiAJoLbXJwbA4vAPsLdwLBB/RV5R+kFIPmPYUH zgURI1EyFgGkZWe2txOMrNBL8lGH/otTp+6IJu3v3T/9kAe082/od70QDo5OJ35mCB4viO J+SA+BCXg5uh7REC9+/PFFpPAQeg9wmPnKj3ND0zEAlx8N33Qh4ag3c/AIgvIQ7TmLiiSw D+xs1xVrqHGnk9OUqkzvq59NyHNAf+YkdD6fc4PzeYvZnjJT1D7Nhc+fnuOGm8thP6Mr2T deFtevCtdU00Npb6iPSMPKYy7sX4wTRczGcO6KADnP0lqf8AJpqnWddpNLQI4w== Received: from mail-qv1-f46.google.com (mail-qv1-f46.google.com [209.85.219.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id CD158B4DF; Wed, 2 Feb 2022 16:50:13 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f46.google.com with SMTP id g13so139116qvw.4; Wed, 02 Feb 2022 08:50:13 -0800 (PST) X-Gm-Message-State: AOAM531mVEt7G9j3zLtScV8OB36x4RbXUaPt+i98pxsPXE8hqDM6ubtZ cel0v05kSU3UqjfmdYfl8ADr5eAD1Xlc/CvfLrw= X-Google-Smtp-Source: ABdhPJz2AaUw69PWO9ApOXZB5QOVrmFM0i+kT1dnWJ9446OoaiiVcdGcQkmjcoNoAlW6FVCfpn3VLoOnafQzbjRsdWk= X-Received: by 2002:ad4:5949:: with SMTP id eo9mr26863390qvb.95.1643820613255; Wed, 02 Feb 2022 08:50:13 -0800 (PST) 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 References: <3f375da9-c2a0-8c9e-33e5-d8273e84590c@FreeBSD.org> In-Reply-To: <3f375da9-c2a0-8c9e-33e5-d8273e84590c@FreeBSD.org> From: Kyle Evans Date: Wed, 2 Feb 2022 10:50:02 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: randomdev hangs during initial boot of -current on Raspberry Pi To: Jesper Schmitz Mouridsen Cc: Mark Millard , Mike Karels , freebsd-current , John Baldwin Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643820614; 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=9p7TuR82uOOU0Xa5QUozyvizuFYg2wVK+SqfbDRK82U=; b=vwQABK2uQvnZ9ie9fOjjAe3mBz+gyrFfql6F3rkBzf8VzLVBAXuFUodgNJ/ivqzUbodMJB YjxgZ8T2wKfKn3OO7YWAzou1zbL4562Xro1O9r4ShN0h1vTw45Bqmc2qpAx9VYC+jdggtW MymyvHx4YPojfYXVWtd3SPg1ND06weCMU4LOIARoTpnT/CLl609nmvh6CrpGD9huOyWxsw HtFf2xGBdjv2/58mDOSwj/l5chWchpCNOr624o78hSSFezKACSfPdNU2CoLXFOCQ6DGqUY nIiNJW/uWa9JdB1+YXCfaB08zjAPeULL0Owhny0xtDchRJjrLE0IfmOAwG+Isw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643820614; a=rsa-sha256; cv=none; b=ikjMUThilVtwzpZhfQ3geWPs47V332kJ+z1K7xG+4cD1dov9LIpLRXoKPgsuCPhqkgDx7z 5XioKEIThVy9tmrM2GkFnaiTCicLFTjVTk7yHKo4bqCa63zlIitjMu6qIwQ420AcPJajGq VeGHxoDwa6jnKaW37NRG2SZrrvvgtmCHG7bceUGCzB6jZxm4fUGgkcIdxhf72+8I2azSj7 qtuimBoHUD095GWqBLxYiTJfi4WslXnF+79yv8oCAc6kAdeOK4HQKU4Xn83QjDZLcSCyl3 q0cFBBMdQUHlofpoZnEV6M+rrwSci7zJWH0kZrtICLdumOOkWfRVqLs4y63IkA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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.