ts-7000
[Top] [All Lists]

Re: [ts-7000] Re: TS-7260 yaffs2/NAND problem

To:
Subject: Re: [ts-7000] Re: TS-7260 yaffs2/NAND problem
From: Gary Wicker <>
Date: Fri, 24 Apr 2009 12:24:45 -0700
Hi Richard,

I made the change to JFFS2 quite some time ago here.  I think I had to
patch the kernel to get JFFS2 working but I can't remember exactly
what I had to do.  It has been a long time.  If I did, the changes
were easy otherwise I'm sure I would remember them.  Good luck.

Gary

On Fri, Apr 24, 2009 at 3:49 AM, Richard Williams
<> wrote:
> Hi Gary,
>
> Sounds interesting, I will try JFFS2. Looks like I will need to patch the 
> kernel with the latest MTD driver. Will this interfere with TS specific 
> patchs to the kernel?
>
> Richard
>
>>
>> Richard,
>>
>> I quit using YAFFS on my TS-7250s because it kept marking blocks as
>> bad, and I was never able to figure out how to unmark them.  I ended
>> up with several unusable boards as a result.  As a result I switched
>> to JFFS2 and haven't had any problems since.
>>
>> Gary
>>
>> On Thu, Apr 23, 2009 at 2:45 PM, Richard Williams
>> <> wrote:
>> >
>> >> >
>> >> >
>> >> > The log shows all blocks 814-1000 are unusable and some 39-104 unusable.
>> >>
>> >> That would seem to correspond to the 21% usage you noted assuming yaffs 
>> >> is reporting % of total size.
>> >>
>> >> The question is whether these retired blocks are really fautly or whether 
>> >> some bug or electrical defect has caused them to be marked as bad.
>> >>
>> >> How old is this board and what root fs is it running? Is it still on 
>> >> factory TS linux and kernel?
>> >>
>> >> How much use did it get before you set up everything is tmpfs?
>> >>
>> >
>> > It's running a cut down version of the oiginal rootfs that comes with the 
>> > board and ts7400_tskernel-jul162008.tar.gz to get proper support for 
>> > YAFFS2.
>> >
>> > I've been running tmpfs right from the beginning so it hasn't been 
>> > thrashed.
>> >
>> > I have another unit that has been running the same software for a week and 
>> > it's got this in the log which is a bit worrying. I get the same bad 
>> > blocks mentioned each time I boot the board. Does this mean that there are 
>> > only 3 bad blocks (312,878 and 110)? Why is block 110 be retired 50 times 
>> > at each boot?
>> >
>> > yaffs: dev is 7937 name is "1f:01"
>> > yaffs: Attempting MTD mount on 31.1, "1f:01"
>> > block 312 is bad
>> > block 878 is bad
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > Partially written block 110 being set for retirement
>> > VFS: Mounted root (yaffs2 filesystem).
>> >
>> > Richard
>> >
>> >
>> >
>> > ------------------------------------
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
    
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU