From nobody Thu Sep 21 08:53:22 2023 X-Original-To: questions@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 4Rrq1x4jQNz4tnyJ for ; Thu, 21 Sep 2023 08:53:41 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from h1.out4.mxs.au (h1.out4.mxs.au [110.232.143.238]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rrq1x1pQmz4QH9 for ; Thu, 21 Sep 2023 08:53:39 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Authentication-Results: mx1.freebsd.org; none Received: from s121.syd3.hostingplatform.net.au (s121.syd3.hostingplatform.net.au [103.27.34.4]) by out4.mxs.au (Halon) with ESMTPS (TLSv1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 id 54768076-585c-11ee-9c85-00163c87da3f for ; Thu, 21 Sep 2023 18:53:27 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nimnet.asn.au; s=default; h=Message-ID:From:CC:To:Subject: Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To: Date:Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7n98YSfw4zzTneop0tlSCkXrZIYEDVxr0/XWochm8Po=; b=UJIRm4w46R7jeurj1nhm7zxkei nv98d28eTmQ7sqYizmposo55eG7h9W0H/UsjfVB0B4H/xySltVovTvaxEIGKVzXEPgj+MO0fEzM8d w4XkBXRw8XS5htZQ6m0Msm/vDZmA3Ww7c/nkpevox9JZJGWiF67WXYKgLjZP0KVUP2VRwMOC+FhdS lM++J2IUQsiKSSek72zhRA7tpCL4OTw0kR1nBPSSOv3Zs2QYtQqY5cvI8FUYgPc3VdLT5XXS/VHos w5ZwmpajNRyWsk2mYoW+3GlbQE8gEeAutZOEhDTkIxFLfQldbokKu79mbgvvJJSIkGQY4PNCx1wSq BfKzVdLA==; Received: from [1.145.82.184] (port=1311 helo=[10.236.68.5]) by s121.syd3.hostingplatform.net.au with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1qjFR9-003MwL-08; Thu, 21 Sep 2023 18:53:27 +1000 Date: Thu, 21 Sep 2023 18:53:22 +1000 User-Agent: K-9 Mail for Android In-Reply-To: <0b80148a-3feb-43b8-8358-cc048be8f32e@nebelschwaden.de> References: <26de1d95-abff-465d-b25c-1b2465e80342@nebelschwaden.de> <0b80148a-3feb-43b8-8358-cc048be8f32e@nebelschwaden.de> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Capturing Boot Messages? To: Ede Wolf ,Yuri CC: questions@freebsd.org From: Ian Smith Message-ID: <2FF738A7-8F20-469B-92BE-65525C95D770@nimnet.asn.au> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - s121.syd3.hostingplatform.net.au X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - nimnet.asn.au X-Get-Message-Sender-Via: s121.syd3.hostingplatform.net.au: authenticated_id: smithi@nimnet.asn.au X-Authenticated-Sender: s121.syd3.hostingplatform.net.au: smithi@nimnet.asn.au X-Source: X-Source-Args: X-Source-Dir: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:45638, ipnet:110.232.143.0/24, country:AU] X-Rspamd-Queue-Id: 4Rrq1x1pQmz4QH9 On 21 September 2023 5:53:55 am AEST, Ede Wolf = wrote: > Am 20=2E09=2E23 um 20:44 schrieb Yuri: > > Ede Wolf wrote: > >> Hello, > >> > >> I am seeing boot messages on screen, errors from rc=2Econf, that I h= ave > >> yet to find in any log=2E Neither dmesg, nor /var/run/dmesg=2Eboot n= or > >> in /var/log/messages=2E > >> > >> Any chance to reread the full boot process somewhere or to set up > >> full boot logging? > > Tried `dmesg -a`? > No, shame on me, did not remotely think about dmesg may having any=20 > options - therefore never been diving into the manpage=2E That's the=20 > solution, I've found my messages! >=20 > Thanks very much Further =2E=2E=2E log hoarders can add to /boot/loader=2Econf: boot_verbose=3D"YES" # always boot -v from loader verbose_loading=3D"YES" # detailed module loading kern=2Emsgbufsize=3D98304 # X200 @ 9=2E3S /var/run/dmesg=2Eboot can be >4 times its non-verbose size, so you might n= eed to enlarge the buffer to keep it all =2E=2E=2E check size of (verbose) = dmesg=2Eboot after boot and allow maybe +20%=2E Perhaps ~150kB by now? Apart from dmesg, it all (and more) goes into /var/log/messages, so newsys= log=2Econf needs tweaking if you always boot verbosely, where a boot might = use ~200kiB in messages=2E cheers, Ian