I'm trying to make new directories, create files, save
changes to files, etc. and when I reboot my changes
are not being saved. I'm sorry if this is vague, but
I haven't run into this problem before in previous
kernels. I'm using 2.6.25 and my configuration is
very similar to mpc8313erdb_defconfi
Ron Madrid wrote:
I'm trying to make new directories, create files, save
changes to files, etc. and when I reboot my changes
are not being saved. I'm sorry if this is vague, but
I haven't run into this problem before in previous
kernels. I'm using 2.6.25 and my configuration is
very similar to
On Thu, 22 May 2008 13:36:32 -0700 (PDT)
"Ron Madrid" <[EMAIL PROTECTED]> wrote:
> I'm trying to make new directories, create files, save
> changes to files, etc. and when I reboot my changes
> are not being saved. I'm sorry if this is vague, but
> I haven't run into this problem before in previo
I have tried the latest code and now, I'm able to
write a limited amount. After which when I reboot,
more than 100 contiguous blocks have been marked bad,
through the end of the device (according to the dts).
Is this something that has been seen before? My NAND
device is a large page.
Ron
--- S
Ron Madrid wrote:
I have tried the latest code and now, I'm able to
write a limited amount. After which when I reboot,
more than 100 contiguous blocks have been marked bad,
through the end of the device (according to the dts).
Is this something that has been seen before?
Yes, but not with the
In which function should I start searching for this
problem? What would cause a block to be marked bad?
Ron
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> Ron Madrid wrote:
> > I have tried the latest code and now, I'm able to
> > write a limited amount. After which when I
> reboot,
> > more than
Ron Madrid wrote:
In which function should I start searching for this
problem? What would cause a block to be marked bad?
No particular function; just something that causes things to not work. :-P
You may want to try increasing the OR[SCY] field or other timing
parameters associated with the
--- Scott Wood <[EMAIL PROTECTED]> wrote:
> You may want to try increasing the OR[SCY] field or
> other timing
> parameters associated with the NAND flash.
So are you saying that when this happened in the past
it was a timing issue? This change would need to
happen in u-boot correct?
Ron
__
Ron Madrid wrote:
--- Scott Wood <[EMAIL PROTECTED]> wrote:
You may want to try increasing the OR[SCY] field or
other timing
parameters associated with the NAND flash.
So are you saying that when this happened in the past
it was a timing issue? This change would need to
happen in u-boot corr
So I found something that looks suspicious to me.
This may not be a fsl_elbc_nand.c problem, but a more
general problem.
Shortly after mounting the root filesystem, which is a
jffs2 on a large page NAND device (my board is based
on the MPC8313) the kernel appears to read the device
starting just
10 matches
Mail list logo
