From nobody Tue Dec 14 00:17:52 2021 X-Original-To: hackers@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 00B2018EB2B3 for ; Tue, 14 Dec 2021 00:18:04 +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 4JCf975QlJz4hls for ; Tue, 14 Dec 2021 00:18:03 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f182.google.com (mail-qk1-f182.google.com [209.85.222.182]) (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 953542C060 for ; Tue, 14 Dec 2021 00:18:03 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f182.google.com with SMTP id 193so15452935qkh.10 for ; Mon, 13 Dec 2021 16:18:03 -0800 (PST) X-Gm-Message-State: AOAM533SBUto6VHYUl9qJ+Rm0Jx5rSvL90kfKREPaRCHIlTVA08cNFFf Lw+rgg3rRJ596VdytK+J7uYwxdSkNmP0getQTec= X-Google-Smtp-Source: ABdhPJxolq85SpJJ1MdsFxYybDnRw650vWVn0fRJ6bjKhfd+dKOOzekdDlnKy61ypqlsT2Zf0sjPVZpj4dTbTaPdAdc= X-Received: by 2002:a05:620a:1a92:: with SMTP id bl18mr1435645qkb.488.1639441083160; Mon, 13 Dec 2021 16:18:03 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <202112140007.1BE079G8030464@fire.js.berklix.net> In-Reply-To: <202112140007.1BE079G8030464@fire.js.berklix.net> From: Kyle Evans Date: Mon, 13 Dec 2021 18:17:52 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: /boot/loader.conf debuging traces come out jumbled To: "Julian H. Stacey" Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1639441083; 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=5O2BMoeEiZNtzKN6c/nwMd+tq720847qKfiPcTl03FI=; b=c8XqDub5s1sjufbBj7zi70efoSZoBYY87EeXQne3wvz30YObHSyKdNAjg/F6E5mulaKiAB ETR4AM4StbP4xbTYr5L3IY7Z5ogUP0CjoG/Sua65x0ZsjKrHmZXS9wU/mKXfgYW1HDd1aG W6byBYFVPVLVuhy4D5IO/qUNrul29ksYtIulEyhblBAsrK8TJwVTIIywgoxSBrCARI7ovE dAIMsZfLq5jsN0jdyDCs6M2vHrcQVsq5SP9JCFhNqaAuYcFMdW5+5CbcbjbRa4re+zh3/M b4DsnJ8VDKYN5HX4WLEOxQBLqwi36k56d3r4Mv8JVk9B4fpHX7YEC2H7AFm9rg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1639441083; a=rsa-sha256; cv=none; b=niCw4eMtET68jFWXxgXM1RARK8sE9IH65CRE6yy8GkZY/GIJyGji+rS0siTwwiztRvCNcN UHJu6Z8NL4C1wi6p+tcTDdKs+tgn/VlOVsUkMsVOIvT2oGxTpDM4J+1+9OnXCtCKd7bM77 4QnSbfs4KBzWbK8vNh5qs3ylQ2VfIH3+zzVPdITJWR6WTSQJFqSvnLK+Q7j1zpAQ5vg4V1 r6y+O7hy1Roin3DEBtN3QTej6XE9I+sTo3y9VTxzyAs68yOzGK7tQUNnZEGh1NvDZ0Tyf7 VVOzgC9MuCa8wP4ny+fhZ6H4kpGDvyOLhbon57g/OAu6+qp8fMMvC60ucNMUMA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Mon, Dec 13, 2021 at 6:07 PM Julian H. Stacey wrote: > > Debugging my /boot/loader.conf on 12.2-STABLE (with a 12.2-RELEASE kernel, > > (as 12.2-STABLE & 12.3-RELEASE & 13.0-RELEASE GENERIC kernels crash during > boot on one machine here (To be subject of later analysis & > posting)... I got distracted onto debugging boot options, after > output from booting screen rolled off the top), So I concentrated > first on identifying & hashing out noisey boot options , before > next searching how to capture boot text (maybe to a serial port ?) ) > > I tried adding markers to loader.conf create deliberate visible error texts to > mark around lines I wanted to study the effect of, eg > fuse_load="YES" etc ... > > I added this in the middle of /boot/loader.conf : > ZZZZZZZZZ00000000_load="YES" > ZZZZZZZZZ00001111_load="YES" > ZZZZZZZZZ00002222_load="YES" > ZZZZZZZZZ44440000_load="YES" > ZZZZZZZZZ44441111_load="YES" > ZZZZZZZZZ44442222_load="YES" > > & next boot showed a weirdly disordered: > > Loading configured modules... > can't find 'ZZZZZZZZZ00000000_load' > can't find 'ZZZZZZZZZ00002222_load' > can't find 'ZZZZZZZZZ44442222_load' > can't find 'ZZZZZZZZZ44440000_load' > can't find 'ZZZZZZZZZ44441111_load' > can't find 'ZZZZZZZZZ00001111_load' > /etc/hostid size=0x25 > > its not even just a reverse order that one might have expected from > a forth unstacker or some such. Makes it harder to trace what output > lines come from which loader.conf lines. > To my knowledge, we've never guaranteed module load order beyond kernel-first then everything else. You'll have a much better time with _before/_after though; something like this should work: hostid_before="echo before hostid" hostid_after="echo after hostid"