From owner-freebsd-arm@FreeBSD.ORG Fri Sep 13 19:21:43 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CBADB18C for ; Fri, 13 Sep 2013 19:21:43 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A4032C22 for ; Fri, 13 Sep 2013 19:21:43 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id tp5so3551470ieb.12 for ; Fri, 13 Sep 2013 12:21:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ZL2VN0dpSzI8rBy8WRDQ39egHVKYGbfNvlnSKYejqB8=; b=SmxFsYNzNpSyn4hFQp7XrB57Y/0FaJG4+70LGb5qS/Kt3H5o7Hg3+vjXfmsbwNrHfU rEkzzsHzgDMqwQgEdPyPIof2Xk0OJAObkPyr3yHnXJqdgF0oREF03Trr3dnMhJ/Ln6sb Mjt2Wg0QZuVy32AOsGHbOjSlWigK8YgC94BNfXZd9CRXSs518x7dKNuyl4Oe26UIqFth J2OmuH1XVyTvDS2BeHYXjfRzghXuag3ElhK/OkFKDKGuUVonrfJSjnm5Wk+FL3Uaf40z qUXxHGm597WHQ73F3QIn0j096wJYpN03VVqXFzA42oZbEUpDsa2ahfPdd9YY1+KZt5vw a56g== X-Gm-Message-State: ALoCoQk89rEIAi7Ri2iBnazSv+rtC0uOBd2ZQbO/TJFbsUm14ReU+LTVtvu7NxXmlaRcB7ljKEtq X-Received: by 10.50.22.105 with SMTP id c9mr1934776igf.36.1379100097691; Fri, 13 Sep 2013 12:21:37 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id lp9sm1222703igb.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Sep 2013 12:21:37 -0700 (PDT) Sender: Warner Losh Subject: Re: Panic while building perl on sheevaplug/armv5 freebsd 10. Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1379080987.1111.637.camel@revolution.hippie.lan> Date: Fri, 13 Sep 2013 13:21:36 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0D9A93F9-E4F1-4D78-BA8B-809169AE450D@bsdimp.com> References: <1379080987.1111.637.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1085) Cc: freebsd-arm@FreeBSD.org, Ronald Klop X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 19:21:44 -0000 On Sep 13, 2013, at 8:03 AM, Ian Lepore wrote: > On Fri, 2013-09-13 at 15:11 +0200, Ronald Klop wrote: >> Hello, >>=20 >> I have a repeatable panic while building perl on my Sheevaplug ARMv5 =20= >> running FreeBSD 10-CURRENT. >> Kernel is loaded from NAND. >> / is mounted from USB /dev/da0s2 (UFS2) >> /usr/ports is mounted over NFS from a 9-STABLE/amd64 box. >> Swap from 512MB file in /data/swap. >>=20 >> ---- console output >> login: panic: vm_fault: fault on nofault entry, addr: ddf9d000 >> KDB: enter: panic >> [ thread pid 659 tid 100057 ] >> Stopped at kdb_enter+0x4c: ldrb r15, [r15, r15, ror r15]! >> db> bt >> Tracing pid 659 tid 100057 td 0xc3f86000 > [...] >> exception_exit() at exception_exit >> pc =3D 0xc0bba3fc lr =3D 0xc0a60c88 (tc_setclock+0x458) >> sp =3D 0xddf9d008 fp =3D 0xddf9e038 >> r0 =3D 0xc0bba324 r1 =3D 0xc0d00000 >> r2 =3D 0xddf9d00c r3 =3D 0x20000093 >> r4 =3D 0x00000000 r5 =3D 0xc0ccd630 >> r6 =3D 0x00000000 r7 =3D 0x00000000 >> r8 =3D 0xc0caece0 r9 =3D 0x00000001 >> r10 =3D 0xc0caec88 r12 =3D 0x00000000 >> data_abort_entry() at data_abort_entry+0x30 >> pc =3D 0xc0bba324 lr =3D 0xc0a60c88 (tc_setclock+0x458) >> sp =3D 0xddf9d008 fp =3D 0xddf9e038 >> Unwind failure (no registers changed) >=20 > That's the second time in the past few months I've seen a backtrace = that > makes it look like we ran out of kernel stack, but the default is 8k > which should be plenty. Still, try adding "option KSTACK_PAGES=3D3" = to > your kernel config and see if the problem goes away. If it does, we = may > need to figure out why we're using so much stack. If it doesn't, = we've > probably got a bad recursion loop happening somewhere. FreeBSD/mips runs out of kernel stack on ports builds as well, but = there's a number of special conditions that seem to be needed before = that happens... Warner