From owner-freebsd-arm@FreeBSD.ORG Sat Nov 22 21:33:00 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 095546A0; Sat, 22 Nov 2014 21:33:00 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 910077F9; Sat, 22 Nov 2014 21:32:58 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id sAMLW4vU054607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 22 Nov 2014 22:32:28 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id sAMLVuPL025476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Nov 2014 22:31:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id sAMLVuEY024016; Sat, 22 Nov 2014 22:31:56 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id sAMLVtEd024015; Sat, 22 Nov 2014 22:31:55 +0100 (CET) (envelope-from ticso) Date: Sat, 22 Nov 2014 22:31:55 +0100 From: Bernd Walter To: Warner Losh Subject: Re: new support for Raspberry Pi B+ Message-ID: <20141122213155.GB22446@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <5470E81A.3070009@foxvalley.net> <20141122200952.GA22446@cicely7.cicely.de> <5470F87D.1040208@foxvalley.net> <1416690352.1147.333.camel@revolution.hippie.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: "freebsd-arm@freebsd.org" , ticso@cicely.de, Ian Lepore X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 21:33:00 -0000 On Sat, Nov 22, 2014 at 02:20:02PM -0700, Warner Losh wrote: > > On Nov 22, 2014, at 2:05 PM, Ian Lepore wrote: > > > On Sat, 2014-11-22 at 13:56 -0700, Dan Raymond wrote: > >> On 11/22/2014 1:09 PM, Bernd Walter wrote: > >>> On Sat, Nov 22, 2014 at 12:46:34PM -0700, Dan Raymond wrote: > >>>> Further testing with the 16GB Kingston reveals that it is unstable even > >>>> at low speed. I hit the following panic while executing "portsnap fetch > >>>> update" on a r274416 build: > >>>> > >>>> dev = mmcsd0s2a, ino = 155101, fs = /mnt/ufs > >>>> panic: ffs_freefile: freeing free inode > >>>> KDB: enter: panic > >>>> [ thread pid 8 tid 100056 ] > >>>> Stopped at $d: ldrb r15, [r15, r15, ror r15]! > >>>> db> > >>> Maybe you've received a counterfeit. > >>> Unfortunately there are a lot of them on the market. > >>> Some of them are technically smaller than they claim and overwrite > >>> other data if they run short. > >> > >> I considered that originally which is why I bought 4 different cards of > >> different brands for testing (Transcend, SanDisk, Samsung, Kingston): > >> > >> http://www.amazon.com/gp/product/B00CBD0XSI/ref=oh_aui_detailpage_o06_s00?ie=UTF8&psc=1 > >> http://www.amazon.com/gp/product/B00M55C0NS/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1 > >> http://www.amazon.com/gp/product/B00IVPU7DQ/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 > >> http://www.amazon.com/gp/product/B003WIRFD2/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 > >> > >> None of them will boot FreeBSD at high speed and I have seen SD related > >> panics with 3 of them (so far) at low speed. Well high speed seems to be a different issue. But if it happens on multiple different cards, then the corruption is unlikely card related. > > I would actually dispute that this one is an sd-related panic, unless > > you have messages about gvfs_iodone failures on the console before the > > panic. Otherwise this is more likely another memory corruption problem > > similar to the panics being reported on wandboard. > > The RPi is also sensitive to power. I?ve seen weird corruption like this when I tried to run > my RPi off a battery and the battery was getting weak... They completely redesigned the power design in the B+, including the use of decent switching regulators. Assuming the problem happens on a B+ as the subject claims. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.