From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32308 invoked by alias); 7 Oct 2003 13:43:05 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 32301 invoked from network); 7 Oct 2003 13:43:04 -0000 Received: from unknown (HELO londo.lunn.ch) (80.238.139.98) by sources.redhat.com with SMTP; 7 Oct 2003 13:43:04 -0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1A6s7B-0004Af-00; Tue, 07 Oct 2003 15:43:01 +0200 Date: Tue, 07 Oct 2003 13:43:00 -0000 To: oyvind.harboe@zylin.com Cc: ecos-discuss@sources.redhat.com Message-ID: <20031007134301.GC15932@lunn.ch> Mail-Followup-To: oyvind.harboe@zylin.com, ecos-discuss@sources.redhat.com References: <1065524219.5485.43.camel@famine> <20031007130402.GB15932@lunn.ch> <1065532608.5999.8.camel@famine> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1065532608.5999.8.camel@famine> User-Agent: Mutt/1.5.4i From: Andrew Lunn Subject: Re: [ECOS] Stress testing JFFS2 X-SW-Source: 2003-10/txt/msg00099.txt.bz2 On Tue, Oct 07, 2003 at 03:16:48PM +0200, ?yvind Harboe wrote: > > Please could you give us a complete test case. Something we can run > > ourselves. Create a new bugzilla bug on bugs.ecos.sourceware.org and > > include the source code and the ecos configuration you are using. > > > > That will make it much easier for us to see whats happening. > > OK. > > But I need a few pointers. Clearly this standalone test case > should not be EB40a specific. > > Ideally anyone should be able to run the testcase, but setting up a > JFFS2 mount consists of a fair bit of hardware specific ecos.ecc > manipulations, etc. Yep. Ideally would be to write a test case which runs on the synth target. We can all work with that. This does work, i've run the standard test case on synth before. > This might not be eCos specific, but I would expect the eCos community > having greater interest in this kind of bug being fixed than > non-embedded applications. Actually, it could be ecos specific. There is an wrapper round jffs2 which implements the interface between eCos fileio and jffs2. The problem could be in there. Also, its easier to debug jffs2 in eCos than inside a linux kernel. Andrew -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss