Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memo

看板FB_current作者時間12年前 (2013/06/24 02:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串14/18 (看更多)
--s/DY0TM5dkgdNyMY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 23, 2013 at 12:32:20PM +0400, Ruslan Bukin wrote: > On Sun, Jun 23, 2013 at 09:57:06AM +0300, Konstantin Belousov wrote: > > > I don't really see a lot of wasted memory in the zones. There is=20 > > > certainly some. Can you give me sysctl vm from both a working and=20 > > > non-working kernel after the build is done or fails? > >=20 > > Try this: > > http://people.freebsd.org/~kib/misc/arm_bcache.1.patch > >=20 > > Please _do_ notify me whether it compiled and helped with your problem. >=20 > Btw, there is a problem while allocating 2GB RAM on armv7 boards > while unmapped_buf_allowed =3D=3D 1 (default): >=20 > ----- > ## Starting application at 0x40F00000 ... > KDB: debugger backends: ddb =20 > KDB: current backend: ddb > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-CURRENT #5 r252090M: Sun Jun 23 12:18:31 MSK 2013 > root@intel.bsdpad.com:/usr/obj/arm.armv6/usr/home/br/dev/head/sys/ARN= DALE arm > FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > WARNING: DIAGNOSTIC option enabled, expect reduced performance. > CPU: Cortex A15 rev 4 (Cortex-A core) > Supported features: ARM_ISA THUMB2 THUMBEE ARMv4 Security_Ext > WB disabled EABT branch prediction enabled > LoUU:2 LoC:2 LoUIS:2=20 > Cache level 1:=20 > 32KB/64B 2-way data cache WB Read-Alloc Write-Alloc > 32KB/64B 2-way instruction cache Read-Alloc > Cache level 2:=20 > 1024KB/64B 16-way unified cache WB Read-Alloc Write-Alloc > real memory =3D 2147483648 (2048 MB) > panic: kmem_suballoc: bad status return of 3 > ----- >=20 > arm_bcache.1.patch resolves the issue above, but forced another one: I have no idea why do you think that the patch 'forced' this issue. >=20 > ----- > Trying to mount root from ufs:/dev/da0 []... > WARNING: / was not properly dismounted > warning: no time-of-day clock registered, system time will not be set acc= urately > panic: __rw_wlock_hard: recursing but non-recursive rw pmap pv global @ /= usr/home/br/dev/head/sys/arm/arm/pmap-v6.c:1289 > ----- This is useless without a backtrace. >=20 > and there are no problems at all if unmapped_buf_allowed =3D=3D 0 >=20 > -Ruslan --s/DY0TM5dkgdNyMY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRxwcPAAoJEJDCuSvBvK1BOdsP/34HcvrUJjGAge4x76J0sf3r SU7pgGJKsH3kYDU9CwOSYZy5foRg7exd3xi23wX4Tj7tH3mt+IfYfbUNROzkzBOb YRmPYSBeWC6f12p1jed5NQ86iVIaEQbfp2jeBFKOnnKKvxsH6I96UgBUwbjQ2VXb S2xim74YyOgjHUnannxxb2CULEHH/ExMMWCZuu43EL/fU4egLGHdyoVO+pjnh5UV hULIECrsz3+JbKsLeTt6S4pEamGvFEYQe12cFLcnE9GGSzyvhqAV/ZMEAWUiG3xO h8Z6/qPGWMddpAR6kkmFXTIX3cRWo02y/hnb4JU6Fx1x/O1rGoLkWV4s6efyb/5j q5EPpuNKoa8MMXPA6OCQyFUH+/RWV/GwM9sJs8F9Hc6nS4Xg55hCfF16iSiKVCxo 3GOGnpiF3HrpHHYE8sSvU37PeEI3yp+0Pqi4L2fNMAZqXm+F/9NcYRgWwZQpaXw1 /I6nGEhwX3Ea3gfFLWLUKKUI15bKD/6Ezu2c7lvCNnhNFlblkFuduc+kib6OxmZG 2xubatKDMLnRrkjFsrt+dm4mpndfqhbuF2RxmSm+muua8gIV9k6GCVoLMEGRlHMH l5TfSj9WMhXMZwSFYvaGfi/N2t9p9wwfugHLUnt29dFVqur/P5wZk9KPcvL9xH5S KEV3hfQmZSurWL+TijtL =aVeu -----END PGP SIGNATURE----- --s/DY0TM5dkgdNyMY--
文章代碼(AID): #1HnpVW0D (FB_current)
討論串 (同標題文章)
完整討論串 (本文為第 14 之 18 篇):
文章代碼(AID): #1HnpVW0D (FB_current)