From owner-freebsd-arm@FreeBSD.ORG Sat Sep 21 01:16:18 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A8C1DFC7 for ; Sat, 21 Sep 2013 01:16:18 +0000 (UTC) (envelope-from lists.br@gmail.com) Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1B2BC2DFE for ; Sat, 21 Sep 2013 01:16:17 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id w7so1089002lbi.8 for ; Fri, 20 Sep 2013 18:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yr1gOwZ9/6CyhlyZZsIkJx0rFxw+8zFXHLlXbqTmcMM=; b=q+pkbA/t5P4+5IQ1aAxijbY5y8Sc06GzQeiDchNlr1GFNBbQPaPeZXWym60phXJvC8 YkJfppETAq4y3OfyhavA8R60FSZUHfzhWkcefSr3zYENlbZl0l0IMLmDXXWCuni5TyV0 Yu3k0stcvIBxW5BnLqTVPPWOO+7bKv7+/ptcRNCSiHteQKKzX7qnTkH1rT4tD6SpHTRS 1fpy1mj0sP/8zdCo00yo9TjXpSIa5du3qSkgScTmnauCyU47JhxT0/LXgQ4GJkxtnXmu +CDbUQBgpfEARPq4PVkgT2GWTKUSP3eaMdJBpi9HebkMcCUQaAbFxuz8oqKu80KBtnqA mHEw== MIME-Version: 1.0 X-Received: by 10.112.146.33 with SMTP id sz1mr8527404lbb.14.1379726175451; Fri, 20 Sep 2013 18:16:15 -0700 (PDT) Received: by 10.112.147.197 with HTTP; Fri, 20 Sep 2013 18:16:15 -0700 (PDT) In-Reply-To: <523CED09.2010509@m5p.com> References: <523CED09.2010509@m5p.com> Date: Fri, 20 Sep 2013 22:16:15 -0300 Message-ID: Subject: Re: Progress on Raspberry Pi From: Luiz Otavio O Souza To: George Mitchell Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" 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: Sat, 21 Sep 2013 01:16:18 -0000 On 20 September 2013 21:49, George Mitchell wrote: > My AdaFruit serial cable arrived, so now I can gather useful information > when my RPi crashes (which is still happening fairly often as I try to > build print/cups, having started five days ago and still not having > gotten through ghostscript). > > I built my image with crochet on an amd64 running r255361, and the image > itself is based on that version. (However, in sys/arm/arm I updated > pmap-v6.c to 255612 and stdatomic.c to 255613. I see they have been > updated again within the last day; perhaps I should try again.) > > /etc/src.conf: > MALLOC_PRODUCTION=yes > MALLOC_PRODUCTION=yes is just a workaround for the RPi problem, in a ideal world (where everything works) we wouldn't need to set it. > > /etc/make.conf: > WITH_PKGNG=yes > MALLOC_PRODUCTION=yes > # added by use.perl 2013-08-20 10:11:49 > PERL_VERSION=5.14.4 > > I commented out the five syscons-related lines in sys/arm/conf/RPI-B so > I could use the serial port. My SDHC card is apparently on the hairy > edge of working, so I definitely needed /boot/loader.conf to contain: > hw.bcm2835.sdhci.hs=0. Before I added that, I ended up with the dreaded > error 19 and a manual mountroot prompt, at which point mountroot would > accept a character from the serial input about 1/4 of the time. Other > serial input works without a problem. > Can you check if the patch on arm/179688 ( http://www.freebsd.org/cgi/query-pr.cgi?pr=arm/179688) fix the mountroot input problem for you ? > > Before I remembered to comment out the /dev/ttyvN lines in /etc/tty, I > naturally saw getty errors on the nonexistent devices, but I would also > randomly get an "Interrupted system call" on /dev/ttyu0, followed by a > long pause, followed (finally) by a login prompt. After I commented out > the ttyvN lines, the "Interrupted system call" error on /dev/ttyu0 went > away. > This is added by crochet, isn't ? (boards/RaspberryPi/overlay/etc/ttys) > > Questions: > > 1. Do we have any sort of a memory test for the RPi? It seems unlikely > that I have a hardware problem, but I would like to rule it out. > 2. Now that I can do something when I get the prefetch abort or panic, > what should I do at the "db>" prompt to help debug it? It's happening > about five or six times a day. > > We have a known bug that triggers under heavy load (during builds): http://www.freebsd.org/cgi/query-pr.cgi?pr=arm/182060 We need to check (now that gcc builds should be working again for arm) if there is any difference between the builds with clang and gcc, oabi and eabi. Thanks, Luiz