Date: Thu, 15 Apr 2021 22:19:42 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: Dmitry Chagin <dchagin@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: FreeBSD-14.0-CURRENT-amd64-20210408-15dc713ceb5-245885-memstick.img fails to boot on Haswell-based laptop. Message-ID: <37dab5a0-3253-ee2f-c33f-6095016be134@FreeBSD.org> In-Reply-To: <YHiIwDYKG/c2txAV@heemeyer.club> References: <88fac685-ee3d-f9d6-d81d-1d8b5f3c7762@FreeBSD.org> <YHiIwDYKG/c2txAV@heemeyer.club>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15.04.2021 21:41, Dmitry Chagin wrote: >> calltrap() >> --- trap 0x9 >> run_interrupt_driven_config_hooks() >> boot_run_interrupt_driven_config_hooks() >> mi_startup() >> >> It is 100% reproducible, and I cannot issue commands to kernel debugger, keyboard is dead. >> >> Enabling verbose boot helps, with verbose boot it boots to installer. >> >> Looks like some race condition. >> >> Is it known problem? > > try to boot verbose It is funny, but boot-verbose helps on battery and doesn't help with AC. I think, it is because with AC plugged in CPU is set to "performance" mode and delay from printing verbose information is not enough! -- // Lev Serebryakov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37dab5a0-3253-ee2f-c33f-6095016be134>