Date: Sat, 14 May 2022 08:05:39 +0100 From: Graham Perrin <grahamperrin@gmail.com> To: FreeBSD-CURRENT <freebsd-current@freebsd.org> Subject: EFI framebuffer information, then nothing: GENERIC-NODEBUG Message-ID: <32a85424-fb0d-c1e5-867b-e73f27388b9a@gmail.com> In-Reply-To: <d4dc0041-ae62-70e2-f3d7-a487df2fc297@gmail.com> References: <d4dc0041-ae62-70e2-f3d7-a487df2fc297@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/04/2022 23:37, Graham Perrin wrote: > Sometimes, boot gets no further than EFI framebuffer information. > Whenever this occurs, the computer will stop immediately in response > to a simple, short press on the power button. … When I first wrote <https://lists.freebsd.org/archives/freebsd-current/2022-April/001829.html>, I omitted a key point: I normally install GENERIC-NODEBUG. I wondered whether GENERIC would be less prone to the problem. For around two weeks I ran GENERIC e140d551b78 without a problem. For the next upgrade, I chose GENERIC-NODEBUG 01235012e5b. Problems recurred immediately; a series of six or seven boot failures. IIRC the first successful boot was with a combination of single user + verbose mode. Since then: a mixture of failures and successes, with an ongoing sense that single user + verbose mode is likely to work around the problem. This morning I changed loader.conf from boot_verbose="NO" to boot_verbose="YES" – I'll reboot frequently over the next few days, to get an idea of whether verbosity reduces the likelihood of the problem. Gut feeling: it will make little or no difference (I'm almost certain that I tried verbose boot alone, at the boot loader menu, a few times in the past, without success). <https://cgit.freebsd.org/src/commit/?id=e140d551b78>; (2022-04-27) <https://cgit.freebsd.org/src/commit/?id=01235012e5b>; (2022-05-12) % bectl list -c creation BE Active Mountpoint Space Created n250511-5f73b3338ee-d - - 64.6G 2021-11-13 15:43 n252381-75d20a5e386-b - - 23.5G 2022-01-12 23:23 n252450-5efa7281a79-a - - 6.87G 2022-01-14 19:27 n252483-c8f8299a230-b - - 7.85G 2022-01-17 14:24 n252505-cc68614da82-a - - 5.24G 2022-01-18 14:26 n252531-0ce7909cd0b-h - - 10.1G 2022-02-06 12:24 n252997-b6724f7004c-c - - 8.10G 2022-02-11 23:07 n253116-39a36707bd3-e - - 7.58G 2022-02-20 07:03 n253343-9835900cb95-c - - 9.32G 2022-02-27 14:58 n253776-d5ad1713cc3-b - - 14.1G 2022-03-18 09:31 n253861-92e6b4712b5-e - - 14.5G 2022-04-02 16:02 n254268-50e244964e9-d - - 11.0G 2022-04-09 18:50 n254693-d7696096209-f - - 14.2G 2022-04-27 17:41 n255078-e140d551b78-h - - 7.06M 2022-05-11 21:18 n255588-01235012e5b-a - - 19.4M 2022-05-12 22:23 n255588-01235012e5b-b NR / 13.4G 2022-05-12 23:36 % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #11 main-n255588-01235012e5b-dirty: Thu May 12 21:45:43 BST 2022 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC -NODEBUG amd64 1400058 1400058 % grep -v \# /etc/src.conf | sort KERNCONF=GENERIC-NODEBUG WITH_CCACHE_BUILD=yes WITH_MALLOC_PRODUCTION=yes %
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32a85424-fb0d-c1e5-867b-e73f27388b9a>