Date: Wed, 7 Oct 2020 17:57:39 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Oskar Holmlund <oskar.holmlund@yahoo.com> Cc: Oskar Holmlund via freebsd-arm <freebsd-arm@freebsd.org>, Ed Maste <emaste@freebsd.org>, markj@freebsd.org Subject: Re: BBB boot failure between r366365 and r366386 Message-ID: <20201007175739.d2899b22406eaf86893f1357@bidouilliste.com> In-Reply-To: <472221209.496244.1602086031265@mail.yahoo.com> References: <CAPyFy2CHdEuPL4jaGdCzwacK2p3CbhfybOcPHPHQETd=NqFjyQ@mail.gmail.com> <CAPyFy2A2KKH4sKS1yeQR6PvYtQJBUhDnWg_yE%2BmqkCjxHZ-A8w@mail.gmail.com> <CAPyFy2DmN4xUPWf3yN4Y=bq=LTfWu2QPOmKx8s4UHHEP5sHpNA@mail.gmail.com> <CAPyFy2CG8dQkTFX-Qy4M=HOrcrJN2HFPk-F0CD5J4vBEDiUg7Q@mail.gmail.com> <472221209.496244.1602086031265@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 7 Oct 2020 15:53:51 +0000 (UTC) Oskar Holmlund via freebsd-arm <freebsd-arm@freebsd.org> wrote: > Hello Ed, >=20 > > Den onsdag 7 oktober 2020 03:11:55 CEST, Ed Maste <emaste@freebsd.org> = skrev:=20 > > On Tue, 6 Oct 2020 at 14:59, Ed Maste <emaste@freebsd.org> wrote: > > > > > > On Mon, 5 Oct 2020 at 15:56, Ed Maste <emaste@freebsd.org> wrote: > > > > > > > >=A0 On Mon, 5 Oct 2020 at 09:53, Ed Maste <emaste@freebsd.org> wrote: > > > > > > > > > > Sometime after r366365 and up to r366365 BBB stopped booting in t= he HW > > > > > test environment. > > > > > > > > That should of course be after r366365 and up to (and including) > > > > r366386. > > > > > > Discussed on IRC; the second U-Boot banner comes out ~60s after the > > > first, which might suggest a watchdog timeout. > > > > > > We seem to get stuck after > > > > random: unblocking device. > > > > kevans points out that std.armv7 includes VERBOSE_SYSINIT=3D0, so > > verbose sysinits are available with a loader tunable. We get this far: > >=20 > > subsystem 2140000 > >=A0 init_hwpmc(0)... done. > >=A0 init_dtrace(0)... done. > >=A0 pmc_soft_ev_register(&pmc___lock_failed)... done. > >=A0 pmc_soft_ev_register(&pmc___clock_prof)... done. > >=A0 pmc_soft_ev_register(&pmc___clock_hard)... done. > >=A0 pmc_soft_ev_register(&pmc___clock_stat)... done. > > subsystem 2160000 > > =A0 random_fortuna_init_alg(0)... done. > > =A0 random_harvestq_init(0)... done. > > =A0 random_harvestq_prime(0)... done. > > =A0 __stack_chk_init(0)... random: unblocking device. > > done. > > subsystem 2180000 > > =A0 mac_init(0)... done. > > subsystem 21d0000 > > =A0 mac_late_init(0)... done. > > subsystem 21e0000 > > =A0 vnet0_init(0)... done. > > subsystem 2200000 > > =A0 proc0_init(0)... done. > > =A0 shutdown_conf(0)... done. > > subsystem 2300000 > > =A0 vm_stats_init(0)... done. > > =A0 uma_startup3(0)... done. > > =A0 vm_page_init_cache_zones(0)... done. > > subsystem 2380000 > > =A0 db_capture_sysinit(0)... done. > > subsystem 2400000 > > =A0 sched_setup(0)... done. > > subsystem 2480000 > > =A0 ktrace_init(0)... > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20 >=20 > I can not reproduce the problem - I have tested r366366 - r366386 and as = of today r366515 and all works fine. U-boot is same as yours 2020.07. But i= have not tested to netboot the BBB, i have only tested from SD card and fr= om eMMC. > I can try the kernel and base from the CI builds later. >=20 > //Oskar I manage to find the problem with a lot of help from markj@. This is due to r364819 (and maybe the -O2 recent switch). =20 This patch fixes it : diff --git a/sys/kern/subr_vmem.c b/sys/kern/subr_vmem.c index b99b895233a4..b48ff7f29b63 100644 --- a/sys/kern/subr_vmem.c +++ b/sys/kern/subr_vmem.c @@ -697,7 +697,7 @@ vmem_startup(void) * arena, which may involve importing a range from the kernel arena, * so we need to keep at least 2 * BT_MAXALLOC tags reserved. */ - uma_zone_reserve(vmem_bt_zone, 2 * BT_MAXALLOC * mp_ncpus); + uma_zone_reserve(vmem_bt_zone, 64); uma_zone_set_allocf(vmem_bt_zone, vmem_bt_alloc); #endif } Mark is now aware of the issue and I'm sure he will find a correct patch soon :) Cheers, --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201007175739.d2899b22406eaf86893f1357>