From owner-freebsd-arm@FreeBSD.ORG Fri Sep 13 19:50:50 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 DD774B2A for ; Fri, 13 Sep 2013 19:50:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ye0-f176.google.com (mail-ye0-f176.google.com [209.85.213.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DCDD2DC5 for ; Fri, 13 Sep 2013 19:50:50 +0000 (UTC) Received: by mail-ye0-f176.google.com with SMTP id m4so661740yen.21 for ; Fri, 13 Sep 2013 12:50:44 -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=YWTCflorHnxrNwby+0YnWmOgm6hEVupgwV4RTi6q0Bw=; b=QwPKYkE0tEdcUJ3TuFkD/gpMiz62vKl6k6M61jHymcM8f3D7ylL2liUc/GRZg/j/ku 0OszGBA3JQ7SrHbnkUaSGniO9M0GT7TIPz2x6E43E6qmPKOQXkEqLEt45PbfgRZgFz6H U4fEY4M45+B2QX8AzgUaP341O7Ph7BNy55Jm9lGkJUdKVvZ6U3LkNIMP4khhy1UQuYcQ zJVWylNBMILJ3igR7O5Tf7hkSF9L8eJ3WCw+tRmbRqy79BXG7hqYDTCWAqAxKZS1n+Pk ujIBkHIGEcgugpyMQk+GEnUe3goXXgXGARQlcEol7B0UHedgccFWBnq9ESlCK+mDuOki tE+A== X-Gm-Message-State: ALoCoQkdhFO5EFtvw3TQabhMswplCv0wuybdAN0UAu2ATKP7grknXPK+zbLokARfpjyMX+Jpf4mu X-Received: by 10.236.38.162 with SMTP id a22mr14235810yhb.30.1379101844439; Fri, 13 Sep 2013 12:50:44 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id 48sm15052188yhq.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Sep 2013 12:50:43 -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: Date: Fri, 13 Sep 2013 13:50:41 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <0E7C0397-7D47-4725-B996-C5FB28BCF453@bsdimp.com> References: <1379080987.1111.637.camel@revolution.hippie.lan> <0D9A93F9-E4F1-4D78-BA8B-809169AE450D@bsdimp.com> To: Adrian Chadd X-Mailer: Apple Mail (2.1085) Cc: "freebsd-arm@freebsd.org" , Ian Lepore , 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:50:50 -0000 On Sep 13, 2013, at 1:44 PM, Adrian Chadd wrote: > .. don't we have a guard page on ARM/MIPS so we can trap out whenever = that occurs? We know on the MIPS when that happens. > That way we can at least try to identify where people have made some = "huh we're running on amd64, stack space is cheap huh" assumptions? Well, I'm not sure that's even real. I think that there are more = registers on mips, so certain traps eat a lot more space than on i386... = 32 * 8 bytes adds up fast...=20 Warner >=20 > -adrian >=20 >=20 >=20 > On 13 September 2013 12:21, Warner Losh wrote: >=20 > On Sep 13, 2013, at 8:03 AM, Ian Lepore wrote: >=20 > > On Fri, 2013-09-13 at 15:11 +0200, Ronald Klop wrote: > >> Hello, > >> > >> I have a repeatable panic while building perl on my Sheevaplug = ARMv5 > >> 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. > >> > >> ---- 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) > > > > 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. >=20 > 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... >=20 > Warner >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20