[ARMedslack] Hello

[Thorsten Mühlfelder]

Am Thursday 17 March 2011 17:48:09 schrieb Stuart Winter:
> On Thu, 17 Mar 2011, Davide wrote:
> > I downloaded miniroot current and did the exact same and it booted !!!
> > I guess there is something wrong with 13.1's kirkwood kernel image.
>
> NOthing wrong with 13.1's kirkwood kernel - works fine on the SheevaPlug,
> Guru and OpenRD client.  I don't know what the support was like for the
> Dockstar for that kernel though (or if it was even in there at all!)

I can confirm that I had the 13.1 kernel running on my dockstar without 
problems.

> > The only thing I noticed wrong while system came up is:
> > [   25.669649] uncorrectable error :
> > [   25.672905] end_request: I/O error, dev mtdblock0, sector 1920
> > [   25.678944] Buffer I/O error on device mtdblock0, logical block 240
> > [   25.839517] uncorrectable error :
> > [   25.845664] end_request: I/O error, dev mtdblock0, sector 1920
> > [   25.851715] Buffer I/O error on device mtdblock0, logical block 240
> > [   25.860583] uncorrectable error :
> > [   25.863897] uncorrectable error :
> > [   25.867630] end_request: I/O error, dev mtdblock0, sector 0
> > [   25.873419] Buffer I/O error on device mtdblock0, logical block 0
> > [   25.879845] uncorrectable error :
> > [   25.883085] uncorrectable error :
> > [   25.886731] end_request: I/O error, dev mtdblock0, sector 8
> >
> > This may be because mtdparts may be incorrect since I'm using openwrt
> > second stage u-boot that may have passed wrong flash partitions to
> > kernel. Hope it did not make a mess of the content.
>
> http://www.spinics.net/lists/arm-kernel/msg62881.html
>
> AFAIK it's nothing to worry about, but read up on it by following the info
> in there.

I have the same errors and I've assumed that they are bad block related. The 
link confirmed that in some way (OOB holds bad block information and some 
other data as well). But I've wondered why the mtd partitions are touched at 
bootup, even they are not mounted.
Was this issue introduced with new kernels? On another device I'm using a 
2.6.24 and 2.6.29 kernel and I'm writing u-boot and u-boot-env from within 
Linux to the NAND, but u-boot does not complain about anything (as noted in 
your link).

-- 
Thorsten Mühlfelder
Salix OS: www.salixos.org