Panic on Boot - Current AMD64

From: Juan Ramón Molina Menor <listjm_at_club.fr>
Date: Tue, 6 Feb 2018 22:36:46 +0100
> I get panic on boot from current kernel.
> Since last night - changes to vm system ?
> World is Current as of this morning
>
> FreeBSD is a registered trademark of The FreeBSD Foundation.
> FreeBSD 12.0-CURRENT #0 r328948: Tue Feb  6 11:30:57 PST 2018
>      root at pozo.com 
> <https://lists.freebsd.org/mailman/listinfo/freebsd-current>:/usr/src/sys/amd64/compile/pozo amd64
> FreeBSD clang version 6.0.0 (branches/release_60 324090) (based on LLVM 6.0.0)
> Table 'FACP' at 0xdfbc57e8
> Table 'APIC' at 0xdfbc585c
> Table 'ASF!' at 0xdfbc58e0
> Table 'MCFG' at 0xdfbc5943
> Table 'TCPA' at 0xdfbc597f
> Table 'SLIC' at 0xdfbc59b1
> Table 'HPET' at 0xdfbc5b27
> ACPI: No SRAT table found
> panic: UMA: Increase vm.boot_pages
> cpuid = 0
> time = 1
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff820bc820
> vpanic() at vpanic+0x18d/frame 0xffffffff820bc880
> panic() at panic+0x43/frame 0xffffffff820bc8e0
> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940
> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0
> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20
> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50
> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0
> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0
> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0
> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20
> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50
> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70
> btext() at btext+0x2c
> KDB: enter: panic
> [ thread pid 0 tid 0 ]
> Stopped at      kdb_enter+0x3b: movq    $0,kdb_why
> db> bt
> Tracing pid 0 tid 0 td 0xffffffff80ff1240
> kdb_enter() at kdb_enter+0x3b/frame 0xffffffff820bc820
> vpanic() at vpanic+0x1aa/frame 0xffffffff820bc880
> panic() at panic+0x43/frame 0xffffffff820bc8e0
> startup_alloc() at startup_alloc+0x19c/frame 0xffffffff820bc940
> keg_alloc_slab() at keg_alloc_slab+0xef/frame 0xffffffff820bc9c0
> keg_fetch_slab() at keg_fetch_slab+0x128/frame 0xffffffff820bca20
> zone_fetch_slab() at zone_fetch_slab+0x69/frame 0xffffffff820bca50
> zone_import() at zone_import+0x5a/frame 0xffffffff820bcaa0
> zone_alloc_item() at zone_alloc_item+0x3b/frame 0xffffffff820bcae0
> uma_startup() at uma_startup+0x3d3/frame 0xffffffff820bcbd0
> vm_page_startup() at vm_page_startup+0x338/frame 0xffffffff820bcc20
> vm_mem_init() at vm_mem_init+0x1d/frame 0xffffffff820bcc50
> mi_startup() at mi_startup+0x118/frame 0xffffffff820bcc70
> btext() at btext+0x2c
> db>


Same panic here with HEAD from this afternoon in a Lenovo ThinkPad S440 
with 4 GB.

Workaround: break into the loader prompt and:

set vm.boot_pages=120
boot

When booting kernel.old, vm.boot_pages is 64.

There is something wrong with r328916.

Hope it helps,
Juan
Received on Tue Feb 06 2018 - 20:42:12 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC