Date: Wed, 7 Feb 2018 11:35:31 +0000 From: =?iso-8859-1?Q?M=26S_-_Krasznai_Andr=E1s?= <Krasznai.Andras@mands.hu> To: =?iso-8859-1?Q?Juan_Ram=F3n_Molina_Menor?= <listjm@club.fr>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Cc: "manfredantar@gmail.com" <manfredantar@gmail.com>, "glebius@freebsd.org" <glebius@freebsd.org> Subject: RE: Panic on Boot - Current AMD64 Message-ID: <d1d563373cb7463186b440ed362198a4@MSEXCH13.mands.hu> In-Reply-To: <ecc36195-7ff9-5645-3507-94c0c48c3c89@club.fr> References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <ecc36195-7ff9-5645-3507-94c0c48c3c89@club.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi yesterday I experienced the problem, but after completely synchronizing the= src tree (deleting the content of the /usr/src folder and svnlite checkout= etc.) and recompiling the kernel I can boot my FreeBSD-CURRENT (12.0, amd6= 4, r328967) with the default setting (64) for vm.boot_pages. rgds Andr=E1s Krasznai -----Eredeti =FCzenet----- Felad=F3: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@f= reebsd.org] Meghatalmaz=F3 Juan Ram=F3n Molina Menor K=FCldve: 2018. febru=E1r 7. 12:18 C=EDmzett: freebsd-current@freebsd.org M=E1solatot kap: manfredantar@gmail.com; glebius@freebsd.org T=E1rgy: Panic on Boot - Current AMD64 >> 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=20 >> (branches/release_60 324090) (based on LLVM 6.0.0) Table 'FACP' at=20 >> 0xdfbc57e8 Table 'APIC' at 0xdfbc585c Table 'ASF!' at 0xdfbc58e0=20 >> Table 'MCFG' at 0xdfbc5943 Table 'TCPA' at 0xdfbc597f Table 'SLIC' at=20 >> 0xdfbc59b1 Table 'HPET' at 0xdfbc5b27 >> ACPI: No SRAT table found >> panic: UMA: Increase vm.boot_pages >> cpuid =3D 0 >> time =3D 1 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame=20 >> 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> >=20 >=20 > Same panic here with HEAD from this afternoon in a Lenovo ThinkPad=20 > S440 with 4 GB. >=20 > Workaround: break into the loader prompt and: >=20 > set vm.boot_pages=3D120 > boot >=20 > When booting kernel.old, vm.boot_pages is 64. >=20 > There is something wrong with r328916. >=20 > Hope it helps, > Juan Hi! Recent commits 328955, 328953 and 328952 by glebius@ do not resolve the iss= ue here. Hope it helps, Juan _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/= listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d1d563373cb7463186b440ed362198a4>