From owner-freebsd-arm@FreeBSD.ORG Mon Dec 14 11:06:51 2009 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77ABB1065701 for ; Mon, 14 Dec 2009 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 662FD8FC27 for ; Mon, 14 Dec 2009 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBEB6p2i075878 for ; Mon, 14 Dec 2009 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBEB6oiT075875 for freebsd-arm@FreeBSD.org; Mon, 14 Dec 2009 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Dec 2009 11:06:50 GMT Message-Id: <200912141106.nBEB6oiT075875@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arm@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o arm/134368 arm [patch] nslu2_led driver for the LEDs on the NSLU2 o arm/134338 arm [patch] Lock GPIO accesses on ixp425 o arm/134092 arm [patch] NSLU.hints contains wrong hints for on board n 3 problems total. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 00:21:23 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D3811065670 for ; Wed, 16 Dec 2009 00:21:23 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 1F2328FC0A for ; Wed, 16 Dec 2009 00:21:22 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKhdq-0002r7-GK for freebsd-arm@freebsd.org; Tue, 15 Dec 2009 16:21:22 -0800 Message-ID: <26803523.post@talk.nabble.com> Date: Tue, 15 Dec 2009 16:21:22 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org MIME-Version: 1.0 X-Nabble-From: ruidc@yahoo.com X-Mailman-Approved-At: Wed, 16 Dec 2009 00:50:53 +0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: problem setting up ports X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 00:21:23 -0000 After much battling, and courtesy of some recently uploaded patch files, i've got FreeBSD8 working on the plug. However, upon trying to set up ports using portsnap - which fails consistently but at varying places in the untar, i've now also got errors unzipping ports.tar.gz: splug# fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz splug# gunzip ports.tar.gz gunzip: invalid compressed data--crc error gunzip: ports.tar.gz: uncompress failed the same file extracts fine on an i386 machine. Has anybody got any ideas how to debug this? Regards, RuiDC -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26803523.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 00:57:05 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEAA01065672 for ; Wed, 16 Dec 2009 00:57:05 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id A17358FC0C for ; Wed, 16 Dec 2009 00:57:05 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKiCP-00057N-6Y for freebsd-arm@freebsd.org; Tue, 15 Dec 2009 16:57:05 -0800 Message-ID: <26803725.post@talk.nabble.com> Date: Tue, 15 Dec 2009 16:57:05 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <26803523.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> Subject: Re: problem setting up ports X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 00:57:05 -0000 Just thought i'd add: i've tried with other larger .gz files and they extract fine, and i tried two different mirrors for the ports.tar.gz -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26803725.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 12:06:09 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DCCC1065670 for ; Wed, 16 Dec 2009 12:06:09 +0000 (UTC) (envelope-from bebahu@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 6F9618FC16 for ; Wed, 16 Dec 2009 12:06:08 +0000 (UTC) Received: by fxm27 with SMTP id 27so826149fxm.3 for ; Wed, 16 Dec 2009 04:06:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=kCYSMAF3J1GqsiN0FJGHaTotk0gmH/CujjwvmWqlP+M=; b=vTuD/YwHeoH18QqYMsJgxcp0ZXOYlKRXYwNpbsZ9TbrgfIioT8hRVHlzR2FV0Lurbr XT8JXbIV0rppT4LQTIoEC1OoB8YnFawHAKFTrEubaElawPE69WF4S7m0AUiy9F2nwR53 +mZ/fdvh68eEEWSwKS7dHE6lNEPlZrn858f7g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=me6VEzvW0YrhtWKRSJ+P24Tv7fmnWpbEcSJGsBz8q6B1Y4rChfFmxvonqGzpS2jQvR D4Rr6/0Od+fnPZbYgY7NGIUJePv9nnM7XqmCPwTWwQAlC66Ra1yJbC6MawbqXbeUy87m l4MzdAtjEaAQ+K9zlynoTBwrgEgcxWoP3FXyI= Received: by 10.223.95.76 with SMTP id c12mr1109183fan.41.1260963365412; Wed, 16 Dec 2009 03:36:05 -0800 (PST) Received: from ?192.168.0.197? (dsl5402D7EB.pool.t-online.hu [84.2.215.235]) by mx.google.com with ESMTPS id 16sm282845fxm.8.2009.12.16.03.36.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Dec 2009 03:36:02 -0800 (PST) Message-ID: <4B28C608.1070802@gmail.com> Date: Wed, 16 Dec 2009 12:35:36 +0100 From: bebahu@gmail.com User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-arm@freebsd.org References: <26803523.post@talk.nabble.com> In-Reply-To: <26803523.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: RuiDC Subject: fetch data corruption on local fs (was: Re: problem setting up ports) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 12:06:09 -0000 Hi, I have seen the same problem. Fetch is corrupting downloads to local filesystems. You can try it on an NFS mount or mount your local fs with "-o sync". As i have seen there are n x 32bytes of corrupt chunks in the downloaded file. I hope it correlate with something, but have no time to dig deeper. Also note cp, scp does not corrupts data so fetch does something alternatively. Balazs. RuiDC wrote: > After much battling, and courtesy of some recently uploaded patch files, i've > got FreeBSD8 working on the plug. > However, upon trying to set up ports using portsnap - which fails > consistently but at varying places in the untar, i've now also got errors > unzipping ports.tar.gz: > > > splug# fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz > splug# gunzip ports.tar.gz > gunzip: invalid compressed data--crc error > gunzip: ports.tar.gz: uncompress failed > > > the same file extracts fine on an i386 machine. > Has anybody got any ideas how to debug this? > > Regards, > RuiDC From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 12:36:22 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9582B1065670 for ; Wed, 16 Dec 2009 12:36:22 +0000 (UTC) (envelope-from gjb@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 45A288FC15 for ; Wed, 16 Dec 2009 12:36:22 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id E4DC0C41E7; Wed, 16 Dec 2009 13:17:20 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id BaKjY7LVJ8gq; Wed, 16 Dec 2009 13:17:20 +0100 (CET) Received: from [10.0.0.75] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPA id 1FAB9C3BA4; Wed, 16 Dec 2009 13:17:20 +0100 (CET) Message-ID: <4B28CFCD.3000401@semihalf.com> Date: Wed, 16 Dec 2009 13:17:17 +0100 From: Grzegorz Bernacki User-Agent: Thunderbird 2.0.0.16 (X11/20090618) MIME-Version: 1.0 To: bebahu@gmail.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> In-Reply-To: <4B28C608.1070802@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org, RuiDC Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 12:36:22 -0000 bebahu@gmail.com wrote: > I have seen the same problem. Fetch is corrupting downloads to local > filesystems. You can try it on an NFS mount or mount your local fs with > "-o sync". > > As i have seen there are n x 32bytes of corrupt chunks in the downloaded > file. I hope it correlate with something, but have no time to dig > deeper. Also note cp, scp does not corrupts data so fetch does something > alternatively. > Hi, 32 bytes is a size of cache line, so probably this is a cache coherency issue. Please read mail below for details and workaround. http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html Grzesiek From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 14:22:04 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E04B106568B for ; Wed, 16 Dec 2009 14:22:04 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 510A18FC16 for ; Wed, 16 Dec 2009 14:22:04 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKulP-00053S-Ps for freebsd-arm@freebsd.org; Wed, 16 Dec 2009 06:22:03 -0800 Message-ID: <26811801.post@talk.nabble.com> Date: Wed, 16 Dec 2009 06:22:03 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <4B28CFCD.3000401@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 14:22:04 -0000 Thanks! That's definitely the problem, I used an md filesystem instead of nfs as it was easier, and reproduced the problem, this time on a smaller .gz file (11MB): ftp://ftp.gnu.org/gnu/gettext/gettext-0.17.tar.gz which was also failing consistently. If I mount it without -o sync I reproduce the problem, if I mount it with -o sync it works. so the only questions open are that: 1. this happens for relatively small files as above rather than the 300MB referred to in your quoted thread, 2. what is the safest to use: just -o sync or also -o noclusterr -o noclusterw ? 3. I then need to seek how to compile these mount options into the kernel, as this is for my root filesystem compiled using: option ROOTDEVNAME=\"ufs:/dev/da0s2\" Regards, RuiDC Grzegorz Bernacki wrote: > > bebahu@gmail.com wrote: > >> I have seen the same problem. Fetch is corrupting downloads to local >> filesystems. You can try it on an NFS mount or mount your local fs with >> "-o sync". >> >> As i have seen there are n x 32bytes of corrupt chunks in the downloaded >> file. I hope it correlate with something, but have no time to dig >> deeper. Also note cp, scp does not corrupts data so fetch does something >> alternatively. >> > > Hi, > > 32 bytes is a size of cache line, so probably this is a cache coherency > issue. Please read mail below for details and workaround. > > http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html > > Grzesiek > > > _______________________________________________ > 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" > > -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26811801.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 15:35:58 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58B81106566B for ; Wed, 16 Dec 2009 15:35:58 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 2E5408FC1B for ; Wed, 16 Dec 2009 15:35:57 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKvuv-0002t5-Hl for freebsd-arm@freebsd.org; Wed, 16 Dec 2009 07:35:57 -0800 Message-ID: <26813077.post@talk.nabble.com> Date: Wed, 16 Dec 2009 07:35:57 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <26811801.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:35:58 -0000 I'm having a hard time searching for how to pass these mount options for root. I believe I have to set them in the setting vfs.root.mountfrom.options But I don't know where I have to make this change so that it is baked into the kernel.bin output file that the sheevaplu/FreeBSD build process produces, or even if there's an easier way I can specify these eg. /etc/fstab but still have them picked up at boot time. Can anybody point me in the right direction? RuiDC wrote: > > Thanks! That's definitely the problem, I used an md filesystem instead of > nfs as it was easier, and reproduced the problem, this time on a smaller > .gz file (11MB): ftp://ftp.gnu.org/gnu/gettext/gettext-0.17.tar.gz > which was also failing consistently. If I mount it without -o sync I > reproduce the problem, if I mount it with -o sync it works. > > so the only questions open are that: > 1. this happens for relatively small files as above rather than the 300MB > referred to in your quoted thread, > 2. what is the safest to use: just -o sync or also -o noclusterr -o > noclusterw ? > > 3. I then need to seek how to compile these mount options into the kernel, > as this is for my root filesystem compiled using: option > ROOTDEVNAME=\"ufs:/dev/da0s2\" > > Regards, > RuiDC > > > Grzegorz Bernacki wrote: >> >> bebahu@gmail.com wrote: >> >>> I have seen the same problem. Fetch is corrupting downloads to local >>> filesystems. You can try it on an NFS mount or mount your local fs with >>> "-o sync". >>> >>> As i have seen there are n x 32bytes of corrupt chunks in the downloaded >>> file. I hope it correlate with something, but have no time to dig >>> deeper. Also note cp, scp does not corrupts data so fetch does something >>> alternatively. >>> >> >> Hi, >> >> 32 bytes is a size of cache line, so probably this is a cache coherency >> issue. Please read mail below for details and workaround. >> >> http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html >> >> Grzesiek >> >> >> _______________________________________________ >> 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" >> >> > > -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26813077.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 15:41:52 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59974106566B for ; Wed, 16 Dec 2009 15:41:52 +0000 (UTC) (envelope-from gjb@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id 05A608FC16 for ; Wed, 16 Dec 2009 15:41:51 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 7CEC6C41E7; Wed, 16 Dec 2009 16:41:52 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id SP-Gu44bAbvH; Wed, 16 Dec 2009 16:40:33 +0100 (CET) Received: from [10.0.0.75] (cardhu.semihalf.com [213.17.239.108]) by smtp.semihalf.com (Postfix) with ESMTPA id 8C096C3BA4; Wed, 16 Dec 2009 16:40:33 +0100 (CET) Message-ID: <4B28FF6F.4090601@semihalf.com> Date: Wed, 16 Dec 2009 16:40:31 +0100 From: Grzegorz Bernacki User-Agent: Thunderbird 2.0.0.16 (X11/20090618) MIME-Version: 1.0 To: RuiDC References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> In-Reply-To: <26811801.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:41:52 -0000 RuiDC wrote: > Thanks! That's definitely the problem, I used an md filesystem instead of nfs > as it was easier, and reproduced the problem, this time on a smaller .gz > file (11MB): ftp://ftp.gnu.org/gnu/gettext/gettext-0.17.tar.gz > which was also failing consistently. If I mount it without -o sync I > reproduce the problem, if I mount it with -o sync it works. > > so the only questions open are that: > 1. this happens for relatively small files as above rather than the 300MB > referred to in your quoted thread, It all depends on how memory is use and which cache lines are evicted. In my case it happened always for files bigger then 300MB and sometimes for smaller files. > 2. what is the safest to use: just -o sync or also -o noclusterr -o > noclusterw ? As I understand setting just "-o noclusterr -o noclusterw" didn't help you, right? If so use just "-o sync". > > 3. I then need to seek how to compile these mount options into the kernel, > as this is for my root filesystem compiled using: option > ROOTDEVNAME=\"ufs:/dev/da0s2\" I don't know how to compile it into kernel, but you can try to add line: vfs.root.mountfrom.options="sync" to your loader.conf Grzesiek From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 16:26:52 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4ED11065692 for ; Wed, 16 Dec 2009 16:26:52 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 8FD8D8FC08 for ; Wed, 16 Dec 2009 16:26:52 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NKwiC-00075b-1f for freebsd-arm@freebsd.org; Wed, 16 Dec 2009 08:26:52 -0800 Message-ID: <26813898.post@talk.nabble.com> Date: Wed, 16 Dec 2009 08:26:52 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <4B28FF6F.4090601@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 16:26:53 -0000 Thanks for your replies... Grzegorz Bernacki wrote: > > As I understand setting just "-o noclusterr -o noclusterw" didn't help > you, right? If so use just "-o sync". > I tried with three configurations: 1. just -o sync 2. just noclustered read/writes 3. both sync and noclustered All three worked, but am I correct in thinking that configuration 3 is the most conservative? Grzegorz Bernacki wrote: > > I don't know how to compile it into kernel, but you can try to add line: > vfs.root.mountfrom.options="sync" > to your loader.conf > > The sheevaplug build doesn't produce loader.conf or loader.4th, an ls of my /boot directory is below, although according to man pages for loader.conf: If no /boot/loader.rc exists at installworld time, one with the above lines will be installed. So I do not know if this is normal for a Sheevaplug build. Can anyone confirm? Is it OK to copy these over from an i386 machine??? splug# ls -l /boot total 352 drwxr-xr-x 2 root wheel 512 Dec 15 17:04 defaults drwxr-xr-x 2 root wheel 512 Dec 15 17:04 firmware drwxr-xr-x 2 root wheel 512 Dec 16 13:53 kernel -r--r--r-- 1 root wheel 13320 Dec 16 13:52 loader.help drwxr-xr-x 2 root wheel 512 Dec 15 17:04 modules -r-xr-xr-x 1 root wheel 166236 Dec 16 13:52 ubldr -r-xr-xr-x 1 root wheel 166236 Dec 16 11:52 ubldr.old drwxr-xr-x 2 root wheel 512 Dec 15 17:04 zfs -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26813898.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 19:44:00 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FC09106566B for ; Wed, 16 Dec 2009 19:44:00 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from smtp.semihalf.com (smtp.semihalf.com [213.17.239.109]) by mx1.freebsd.org (Postfix) with ESMTP id A94F28FC15 for ; Wed, 16 Dec 2009 19:43:59 +0000 (UTC) Received: from localhost (unknown [213.17.239.109]) by smtp.semihalf.com (Postfix) with ESMTP id 671E8C427A; Wed, 16 Dec 2009 20:44:00 +0100 (CET) X-Virus-Scanned: by amavisd-new at semihalf.com Received: from smtp.semihalf.com ([213.17.239.109]) by localhost (smtp.semihalf.com [213.17.239.109]) (amavisd-new, port 10024) with ESMTP id Z-dL9HbejmK3; Wed, 16 Dec 2009 20:43:59 +0100 (CET) Received: from [192.168.133.14] (nat2-102.ghnet.pl [91.150.223.102]) by smtp.semihalf.com (Postfix) with ESMTPSA id 62F19C41E7; Wed, 16 Dec 2009 20:43:59 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Rafal Jaworowski In-Reply-To: <26813898.post@talk.nabble.com> Date: Wed, 16 Dec 2009 20:43:56 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com> To: RuiDC X-Mailer: Apple Mail (2.1077) Cc: freebsd-arm@freebsd.org Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 19:44:00 -0000 On 2009-12-16, at 17:26, RuiDC wrote: > Grzegorz Bernacki wrote: >>=20 >> As I understand setting just "-o noclusterr -o noclusterw" didn't = help=20 >> you, right? If so use just "-o sync". >>=20 >=20 > I tried with three configurations: > 1. just -o sync > 2. just noclustered read/writes > 3. both sync and noclustered > All three worked, but am I correct in thinking that configuration 3 is = the > most conservative? =46rom our investigations back then disabling clustering should suffice, = forcing sync operation is a bigger hammer (against performance). > The sheevaplug build doesn't produce loader.conf or loader.4th, an ls = of my > /boot directory is below, although according to man pages for = loader.conf: > If no /boot/loader.rc exists at installworld time, one with the above = lines > will be installed.=20 >=20 > So I do not know if this is normal for a Sheevaplug build. Can anyone > confirm? > Is it OK to copy these over from an i386 machine??? > > splug# ls -l /boot > total 352 > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 defaults > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 firmware > drwxr-xr-x 2 root wheel 512 Dec 16 13:53 kernel > -r--r--r-- 1 root wheel 13320 Dec 16 13:52 loader.help > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 modules > -r-xr-xr-x 1 root wheel 166236 Dec 16 13:52 ubldr > -r-xr-xr-x 1 root wheel 166236 Dec 16 11:52 ubldr.old > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 zfs > It seems loader.conf and .4th are not hooked up to the ARM install = scripting/makefile; they are not required to get the loader initially = working, but you can copy them from i386 world if needed. Note that running ubldr on ARM requires the underlying U-Boot to be = compiled with CONFIG_API option enabled, which is only available in main = line U-Boot since ver. 1.3.2; what is your version? Rafal From owner-freebsd-arm@FreeBSD.ORG Wed Dec 16 21:43:39 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD3F1106566C for ; Wed, 16 Dec 2009 21:43:39 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.freebsd.org (Postfix) with ESMTP id 944038FC18 for ; Wed, 16 Dec 2009 21:43:39 +0000 (UTC) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.14.3/8.14.3) with ESMTP id nBGLhbrL038163; Wed, 16 Dec 2009 15:43:37 -0600 (CST) (envelope-from tinguely@casselton.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=casselton.net; s=ccnMail; t=1260999818; bh=MtXRq0vgXQJHznMX9ypjV1kylGZcsW+LiwcJSiAx6R8=; h=Date:From:Message-Id:To:Subject:In-Reply-To; b=Ltr98UNCMgtR3gCuOrKlzLk/MGYN9lZzwfKiubzu7VP3Fj5FkCaXWm5ADcX6hkc2O Jr+8e6VRr32fs0NrTzquKKSBOSf1PCHq+1U6yZaxA9brVN5WqqLzOkGabZXRHCeXZD vxu5v68MUpzx5GWa+Y8PFGrfmmu2T/ZWzqHpXdqU= Received: (from tinguely@localhost) by casselton.net (8.14.3/8.14.2/Submit) id nBGLhbva038162; Wed, 16 Dec 2009 15:43:37 -0600 (CST) (envelope-from tinguely) Date: Wed, 16 Dec 2009 15:43:37 -0600 (CST) From: Mark Tinguely Message-Id: <200912162143.nBGLhbva038162@casselton.net> To: freebsd-arm@freebsd.org, ruidc@yahoo.com In-Reply-To: <26811801.post@talk.nabble.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.2 (casselton.net [127.0.0.1]); Wed, 16 Dec 2009 15:43:38 -0600 (CST) Cc: Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 21:43:39 -0000 Sounds like you are using preload. Looks like sys/dev/md/md.c could use a cpu_flush_dcache() for the BIO_WRITE cases in mdstart_[malloc|preload] cases. Though from just mdstart_preload, I don't see an obvious reason the "-o sync" is helping. The pmap_kremove() patch for sf_buf_free() should help for the BIO_WRITE in the mdstart_swap case. --Mark. From owner-freebsd-arm@FreeBSD.ORG Fri Dec 18 13:23:10 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83D731065670 for ; Fri, 18 Dec 2009 13:23:10 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 63A218FC18 for ; Fri, 18 Dec 2009 13:23:10 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NLcnV-00031X-QQ for freebsd-arm@freebsd.org; Fri, 18 Dec 2009 05:23:09 -0800 Message-ID: <26843206.post@talk.nabble.com> Date: Fri, 18 Dec 2009 05:23:09 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com> <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2009 13:23:10 -0000 Rafal Jaworowski wrote: > > From our investigations back then disabling clustering should suffice, > forcing sync operation is a bigger hammer (against performance). > ok, i'll try with that initially Rafal Jaworowski wrote: > > It seems loader.conf and .4th are not hooked up to the ARM install > scripting/makefile; they are not required to get the loader initially > working, but you can copy them from i386 world if needed. > I notice some i386 specific "if" statements in .4th, but do not have anywhere near enough knowledge to understand what this is for, but will try this shortly and post back. Rafal Jaworowski wrote: > > Note that running ubldr on ARM requires the underlying U-Boot to be > compiled with CONFIG_API option enabled, which is only available in main > line U-Boot since ver. 1.3.2; what is your version? > I'm running freebsd kernel.bin from usb & FAT32 using: fatload usb 0:1 900000 kernel.bin go 900000 I've read your notes from http://www.bsdcan.org/2008/schedule/attachments/49_2008_uboot_freebsd.pdf but don't understand the implications of the alternative boot methods, but from reading that, I presume the note on ubldr is not relevant to me? Or will switching methods enable me to work around this problem? I'm running the Sheevaplug installer version, which is Marvell's version 3.4.19 which is based on 1.1.4. I'm reluctant to switch to Marvell's Open-Uboot stack due to reported problems here: http://plugcomputer.org/plugforum/index.php?topic=975.0 -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26843206.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Fri Dec 18 13:31:24 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D714B106566B for ; Fri, 18 Dec 2009 13:31:24 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id B87DD8FC08 for ; Fri, 18 Dec 2009 13:31:24 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NLcvU-0003eO-AN for freebsd-arm@freebsd.org; Fri, 18 Dec 2009 05:31:24 -0800 Message-ID: <26843272.post@talk.nabble.com> Date: Fri, 18 Dec 2009 05:31:24 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <200912162143.nBGLhbva038162@casselton.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <200912162143.nBGLhbva038162@casselton.net> Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2009 13:31:24 -0000 Mark Tinguely wrote: > > Sounds like you are using preload. > > Looks like sys/dev/md/md.c could use a cpu_flush_dcache() for the > BIO_WRITE cases in mdstart_[malloc|preload] cases. Though from just > mdstart_preload, I don't see an obvious reason the "-o sync" is > helping. > > The pmap_kremove() patch for sf_buf_free() should help for the BIO_WRITE > in the mdstart_swap case. > Thanks for your reply, I'm not quite sure what you mean in your reply, but presume that your suggestions may workaround this problem when performing fetch operations against an md filesystem? if so, then this may be the case, but my real target is UFS filesystem, I was just using md as an alternative to the NFS-mounted filesystem suggested to test problem and workaround. If I have misunderstood, then please forgive me. -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26843272.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Fri Dec 18 13:50:06 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D12BD1065768 for ; Fri, 18 Dec 2009 13:50:06 +0000 (UTC) (envelope-from tinguely@casselton.net) Received: from casselton.net (casselton.net [63.165.140.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0678FC0C for ; Fri, 18 Dec 2009 13:50:06 +0000 (UTC) Received: from casselton.net (localhost [127.0.0.1]) by casselton.net (8.14.3/8.14.3) with ESMTP id nBIDo5XB028739; Fri, 18 Dec 2009 07:50:05 -0600 (CST) (envelope-from tinguely@casselton.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=casselton.net; s=ccnMail; t=1261144205; bh=bKnbEwnFgBb6aTeEQYCYafhVZzTlHnEIywSxg4fZSG8=; h=Date:From:Message-Id:To:Subject:In-Reply-To; b=N9v6ZULzVllKhD6r1qt0JKeeiWr8xGu49P3ckYn8DGXvVtxzwURH/vcfuneR/hv3h 4Uau3NaWD231d7evBeqDwx82XBXI5Md+zikkEubcelsId+nyqR4i+rVKhk9AFAXNIn hWfok7USz7q/gQezPtNTeZkAqy7WnNTsnSbSFOlo= Received: (from tinguely@localhost) by casselton.net (8.14.3/8.14.2/Submit) id nBIDo5X2028738; Fri, 18 Dec 2009 07:50:05 -0600 (CST) (envelope-from tinguely) Date: Fri, 18 Dec 2009 07:50:05 -0600 (CST) From: Mark Tinguely Message-Id: <200912181350.nBIDo5X2028738@casselton.net> To: freebsd-arm@freebsd.org, ruidc@yahoo.com In-Reply-To: <26843272.post@talk.nabble.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.2 (casselton.net [127.0.0.1]); Fri, 18 Dec 2009 07:50:05 -0600 (CST) Cc: Subject: Re: fetch data corruption on local fs X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2009 13:50:06 -0000 > > Mark Tinguely wrote: > > > > Sounds like you are using preload. > > > > > Thanks for your reply, I'm not quite sure what you mean in your reply, but > presume that your suggestions may workaround this problem when performing > fetch operations against an md filesystem? if so, then this may be the case, > but my real target is UFS filesystem, I was just using md as an alternative > to the NFS-mounted filesystem suggested to test problem and workaround. > > If I have misunderstood, then please forgive me. You are correct, I misunderstood your problem; I thought your problem was in the md filesystem. --Mark. From owner-freebsd-arm@FreeBSD.ORG Fri Dec 18 17:00:01 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A5791065679 for ; Fri, 18 Dec 2009 17:00:01 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 3825F8FC17 for ; Fri, 18 Dec 2009 17:00:00 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NLgBM-0003xk-Ej for freebsd-arm@freebsd.org; Fri, 18 Dec 2009 09:00:00 -0800 Message-ID: <26846376.post@talk.nabble.com> Date: Fri, 18 Dec 2009 09:00:00 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <26843206.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com> <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> <26843206.post@talk.nabble.com> Subject: Re: fetch data corruption on local fs [SOLVED] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Dec 2009 17:00:01 -0000 the below patch from Balazs together with the disabling of clustering in fstab did the trick for me: --- sys/arm/mv/mv_machdep.c.orig 2009-12-09 21:42:53.000000000 +0000 +++ sys/arm/mv/mv_machdep.c 2009-12-09 21:42:40.000000000 +0000 @@ -408,7 +408,7 @@ availmem_regions_sz = i; } else { /* Fall back to hardcoded boothowto flags and metadata. */ - boothowto = RB_VERBOSE | RB_SINGLE; + boothowto = RB_VERBOSE; lastaddr = fake_preload_metadata(); /* RuiDC wrote: > > I notice some i386 specific "if" statements in .4th, but do not have > anywhere near enough knowledge to understand what this is for, but will > try this shortly and post back. > I didn't need to go near these in the end as they are not used by my boot mechanism. Rafal Jaworowski wrote: > > Note that running ubldr on ARM requires the underlying U-Boot to be > compiled with CONFIG_API option enabled, which is only available in main > line U-Boot since ver. 1.3.2; what is your version? > I'm running freebsd kernel.bin from usb & FAT32 using: fatload usb 0:1 900000 kernel.bin go 900000 I've read your notes from http://www.bsdcan.org/2008/schedule/attachments/49_2008_uboot_freebsd.pdf but don't understand the implications of the alternative boot methods, but from reading that, I presume the note on ubldr is not relevant to me? Or will switching methods enable me to work around this problem? I'm running the Sheevaplug installer version, which is Marvell's version 3.4.19 which is based on 1.1.4. I'm reluctant to switch to Marvell's Open-Uboot stack due to reported problems here: http://plugcomputer.org/plugforum/index.php?topic=975.0 I'm still curious to learn more about the implications of alternative boot methods if anyone can point me in the right direction. Thanks again! RuiDC -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26846376.html Sent from the freebsd-arm mailing list archive at Nabble.com. From owner-freebsd-arm@FreeBSD.ORG Sat Dec 19 07:30:58 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66BFF10656A7 for ; Sat, 19 Dec 2009 07:30:58 +0000 (UTC) (envelope-from toshi@ruby.ocn.ne.jp) Received: from smtp.ruby.ocn.ne.jp (ruby.ocn.ne.jp [61.207.12.164]) by mx1.freebsd.org (Postfix) with ESMTP id CE7F08FC0A for ; Sat, 19 Dec 2009 07:30:57 +0000 (UTC) Received: from localhost (p6194-ipadfx01sizuokaden.shizuoka.ocn.ne.jp [219.160.179.194]) by smtp.ruby.ocn.ne.jp (Postfix) with ESMTP id BBCC62C52; Sat, 19 Dec 2009 16:30:55 +0900 (JST) Date: Sat, 19 Dec 2009 16:30:55 +0900 (JST) Message-Id: <20091219.163055.193684234.toshi@ruby.ocn.ne.jp> To: freebsd-arm@freebsd.org From: SAITOU Toshihide In-Reply-To: <26846376.post@talk.nabble.com> References: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> <26843206.post@talk.nabble.com> <26846376.post@talk.nabble.com> X-GPG-fingerprint: 34B3 0B6A 8520 F5B0 EBC7 69F6 C055 9F8A 0D49 F8FC X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: fetch data corruption on local fs [SOLVED] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Dec 2009 07:30:58 -0000 From: RuiDC Subject: Re: fetch data corruption on local fs [SOLVED] Date: Fri, 18 Dec 2009 09:00:00 -0800 (PST) > I've read your notes from > http://www.bsdcan.org/2008/schedule/attachments/49_2008_uboot_freebsd.pdf > but don't understand the implications of the alternative boot methods, but > from reading that, I presume the note on ubldr is not relevant to me? Or > will switching methods enable me to work around this problem? > > I'm running the Sheevaplug installer version, which is Marvell's version > 3.4.19 which is based on 1.1.4. > > I'm reluctant to switch to Marvell's Open-Uboot stack due to reported > problems here: http://plugcomputer.org/plugforum/index.php?topic=975.0 It seems the patches are already mainlined. http://www.plugcomputer.org/plugwiki/index.php/Das_U-boot_plug_support So, Has anyone success to build the Open U-Boot with CONFIG_API and booting ubldr? > I'm still curious to learn more about the implications of alternative boot > methods if anyone can point me in the right direction. > > Thanks again! > RuiDC SAITOU Toshihide From owner-freebsd-arm@FreeBSD.ORG Sat Dec 19 14:28:23 2009 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91DE6106566B for ; Sat, 19 Dec 2009 14:28:23 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 700808FC16 for ; Sat, 19 Dec 2009 14:28:23 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NM0IA-0001US-ND for freebsd-arm@freebsd.org; Sat, 19 Dec 2009 06:28:22 -0800 Message-ID: <26855439.post@talk.nabble.com> Date: Sat, 19 Dec 2009 06:28:22 -0800 (PST) From: RuiDC To: freebsd-arm@freebsd.org In-Reply-To: <20091219.163055.193684234.toshi@ruby.ocn.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ruidc@yahoo.com References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com> <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> <26843206.post@talk.nabble.com> <26846376.post@talk.nabble.com> <20091219.163055.193684234.toshi@ruby.ocn.ne.jp> Subject: Re: fetch data corruption on local fs [SOLVED] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Dec 2009 14:28:23 -0000 SAITOU Toshihide wrote: > >> I'm reluctant to switch to Marvell's Open-Uboot stack due to reported >> problems here: http://plugcomputer.org/plugforum/index.php?topic=975.0 > It seems the patches are already mainlined. > It's still unclear which, and to several of us at least, what the differences are between Marvell's version and mainline, as per this thread: http://plugcomputer.org/plugforum/index.php?topic=913.msg6782 -- View this message in context: http://old.nabble.com/problem-setting-up-ports-tp26803523p26855439.html Sent from the freebsd-arm mailing list archive at Nabble.com.