From: Andrew H. <and...@gm...> - 2010-04-24 19:50:05
|
Hi Just formatted a mini CF card as per the instructions and downloaded todays overo image (201004232142). I'm using the console filesystem image. During boot, I see a lot of i/o errors, but everything appears to work normally. Is this normal? Here is some (clipped) dmesg output: EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing init memory: 936K hub 2-0:1.0: hub_suspend usb usb2: bus auto-suspend ehci-omap ehci-omap.0: suspend root hub udev: starting version 151 usb usb2: uevent usb 2-0:1.0: uevent usb usb1: uevent usb 1-0:1.0: uevent usb usb2: uevent usb usb1: uevent uncorrectable error : end_request: I/O error, dev mtdblock0, sector 0 Buffer I/O error on device mtdblock0, logical block 0 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 8 Buffer I/O error on device mtdblock0, logical block 1 end_request: I/O error, dev mtdblock0, sector 16 Buffer I/O error on device mtdblock0, logical block 2 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 24 Buffer I/O error on device mtdblock0, logical block 3 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 32 Buffer I/O error on device mtdblock0, logical block 4 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 40 Buffer I/O error on device mtdblock0, logical block 5 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 48 Buffer I/O error on device mtdblock0, logical block 6 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 56 Buffer I/O error on device mtdblock0, logical block 7 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 64 Buffer I/O error on device mtdblock0, logical block 8 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 72 Buffer I/O error on device mtdblock0, logical block 9 end_request: I/O error, dev mtdblock0, sector 80 end_request: I/O error, dev mtdblock0, sector 88 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 96 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 104 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 112 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 120 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 128 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 136 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 144 end_request: I/O error, dev mtdblock0, sector 152 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 160 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 168 end_request: I/O error, dev mtdblock0, sector 176 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 184 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 192 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 200 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 208 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 216 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 224 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 232 uncorrectable error : uncorrectable error : end_request: I/O error, dev mtdblock0, sector 240 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 248 uncorrectable error : end_request: I/O error, dev mtdblock0, sector 0 uncorrectable error : and on and on and on, then eventually (actually pretty quickly timewise, but a long ways down in the dmesg) it finishes booting and everything seems normal. What's going on? Andrew |
From: <cod...@gm...> - 2010-04-27 01:40:51
|
I'm getting the same error messages quite often on my SD cards. It doesn't seem to happen on every single boot of a given SD card though. I am assuming that mtdblock is NAND flash, but I could be wrong. It appears that mmcblock is the mmc (microSD) card itself, so mtdblock = NAND makes sense to me. Perhaps a NAND corruption of some kind, or corruption of the drivers on the SD card for NAND's filesystem? On Sat, Apr 24, 2010 at 3:49 PM, Andrew Hakman <and...@gm...>wrote: > Hi > > Just formatted a mini CF card as per the instructions and downloaded > todays overo image (201004232142). I'm using the console filesystem > image. > > During boot, I see a lot of i/o errors, but everything appears to work > normally. Is this normal? > > Here is some (clipped) dmesg output: > > EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode > VFS: Mounted root (ext3 filesystem) on device 179:2. > devtmpfs: mounted > Freeing init memory: 936K > hub 2-0:1.0: hub_suspend > usb usb2: bus auto-suspend > ehci-omap ehci-omap.0: suspend root hub > udev: starting version 151 > usb usb2: uevent > usb 2-0:1.0: uevent > usb usb1: uevent > usb 1-0:1.0: uevent > usb usb2: uevent > usb usb1: uevent > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 0 > Buffer I/O error on device mtdblock0, logical block 0 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 8 > Buffer I/O error on device mtdblock0, logical block 1 > end_request: I/O error, dev mtdblock0, sector 16 > Buffer I/O error on device mtdblock0, logical block 2 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 24 > Buffer I/O error on device mtdblock0, logical block 3 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 32 > Buffer I/O error on device mtdblock0, logical block 4 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 40 > Buffer I/O error on device mtdblock0, logical block 5 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 48 > Buffer I/O error on device mtdblock0, logical block 6 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 56 > Buffer I/O error on device mtdblock0, logical block 7 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 64 > Buffer I/O error on device mtdblock0, logical block 8 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 72 > Buffer I/O error on device mtdblock0, logical block 9 > end_request: I/O error, dev mtdblock0, sector 80 > end_request: I/O error, dev mtdblock0, sector 88 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 96 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 104 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 112 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 120 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 128 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 136 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 144 > end_request: I/O error, dev mtdblock0, sector 152 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 160 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 168 > end_request: I/O error, dev mtdblock0, sector 176 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 184 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 192 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 200 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 208 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 216 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 224 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 232 > uncorrectable error : > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 240 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 248 > uncorrectable error : > end_request: I/O error, dev mtdblock0, sector 0 > uncorrectable error : > > and on and on and on, then eventually (actually pretty quickly > timewise, but a long ways down in the dmesg) it finishes booting and > everything seems normal. > > What's going on? > > Andrew > > > ------------------------------------------------------------------------------ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Andrew H. <and...@gm...> - 2010-04-27 02:14:23
|
I think mtdblock0 is actually the region of NAND that contains x-load. I eventually figured that out after poking around a bit. Not sure why it gives I/O errors though - must be formatted in some non standard way, and then trying to be mounted during boot I guess. I'll just ignore it for now, and eventually figure out how to get it to not try to be auto mounted. And yes, it seems I get few I/O errors on the first boot after power up, and many many more on soft restarts after that. I have no clue why that's happening. Andrew On Mon, Apr 26, 2010 at 7:34 PM, <cod...@gm...> wrote: > I'm getting the same error messages quite often on my SD cards. It doesn't > seem to happen on every single boot of a given SD card though. I am > assuming that mtdblock is NAND flash, but I could be wrong. It appears that > mmcblock is the mmc (microSD) card itself, so mtdblock = NAND makes sense to > me. > > Perhaps a NAND corruption of some kind, or corruption of the drivers on the > SD card for NAND's filesystem? > > On Sat, Apr 24, 2010 at 3:49 PM, Andrew Hakman <and...@gm...> > wrote: >> >> Hi >> >> Just formatted a mini CF card as per the instructions and downloaded >> todays overo image (201004232142). I'm using the console filesystem >> image. >> >> During boot, I see a lot of i/o errors, but everything appears to work >> normally. Is this normal? >> >> Here is some (clipped) dmesg output: >> >> EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode >> VFS: Mounted root (ext3 filesystem) on device 179:2. >> devtmpfs: mounted >> Freeing init memory: 936K >> hub 2-0:1.0: hub_suspend >> usb usb2: bus auto-suspend >> ehci-omap ehci-omap.0: suspend root hub >> udev: starting version 151 >> usb usb2: uevent >> usb 2-0:1.0: uevent >> usb usb1: uevent >> usb 1-0:1.0: uevent >> usb usb2: uevent >> usb usb1: uevent >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 0 >> Buffer I/O error on device mtdblock0, logical block 0 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 8 >> Buffer I/O error on device mtdblock0, logical block 1 >> end_request: I/O error, dev mtdblock0, sector 16 >> Buffer I/O error on device mtdblock0, logical block 2 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 24 >> Buffer I/O error on device mtdblock0, logical block 3 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 32 >> Buffer I/O error on device mtdblock0, logical block 4 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 40 >> Buffer I/O error on device mtdblock0, logical block 5 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 48 >> Buffer I/O error on device mtdblock0, logical block 6 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 56 >> Buffer I/O error on device mtdblock0, logical block 7 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 64 >> Buffer I/O error on device mtdblock0, logical block 8 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 72 >> Buffer I/O error on device mtdblock0, logical block 9 >> end_request: I/O error, dev mtdblock0, sector 80 >> end_request: I/O error, dev mtdblock0, sector 88 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 96 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 104 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 112 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 120 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 128 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 136 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 144 >> end_request: I/O error, dev mtdblock0, sector 152 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 160 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 168 >> end_request: I/O error, dev mtdblock0, sector 176 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 184 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 192 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 200 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 208 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 216 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 224 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 232 >> uncorrectable error : >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 240 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 248 >> uncorrectable error : >> end_request: I/O error, dev mtdblock0, sector 0 >> uncorrectable error : >> >> and on and on and on, then eventually (actually pretty quickly >> timewise, but a long ways down in the dmesg) it finishes booting and >> everything seems normal. >> >> What's going on? >> >> Andrew >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Steve S. <sa...@gm...> - 2010-04-27 03:03:53
|
On Mon, Apr 26, 2010 at 7:14 PM, Andrew Hakman <and...@gm...> wrote: > I think mtdblock0 is actually the region of NAND that contains x-load. > I eventually figured that out after poking around a bit. Not sure why > it gives I/O errors though - must be formatted in some non standard > way, and then trying to be mounted during boot I guess. I'll just > ignore it for now, and eventually figure out how to get it to not try > to be auto mounted. Yes, mtdblock0 is the nand area that contains x-load. The OMAP3 boot ROM requires that that area be written with HW ECC. Linux uses SW ECC, so when it probes that partition at boot time it believes that the data is corrupt. These messages can be safely ignored, since Linux never needs to use the x-load partition. Starting with today's pre-built images you won't see these messages any more, so you can promptly forget all of the above :-) Steve |
From: Andrew H. <and...@gm...> - 2010-04-27 02:17:46
|
Actually another question on this to people that know more than I do about the bootloading process. I'm assuming x-load has to be in flash, and if I unprotect that region and erase it, then the thing won't boot at all correct? If that's gone, it won't boot from a SD card either right? Andrew On Mon, Apr 26, 2010 at 8:14 PM, Andrew Hakman <and...@gm...> wrote: > I think mtdblock0 is actually the region of NAND that contains x-load. > I eventually figured that out after poking around a bit. Not sure why > it gives I/O errors though - must be formatted in some non standard > way, and then trying to be mounted during boot I guess. I'll just > ignore it for now, and eventually figure out how to get it to not try > to be auto mounted. > > And yes, it seems I get few I/O errors on the first boot after power > up, and many many more on soft restarts after that. I have no clue why > that's happening. > > Andrew > > On Mon, Apr 26, 2010 at 7:34 PM, <cod...@gm...> wrote: >> I'm getting the same error messages quite often on my SD cards. It doesn't >> seem to happen on every single boot of a given SD card though. I am >> assuming that mtdblock is NAND flash, but I could be wrong. It appears that >> mmcblock is the mmc (microSD) card itself, so mtdblock = NAND makes sense to >> me. >> >> Perhaps a NAND corruption of some kind, or corruption of the drivers on the >> SD card for NAND's filesystem? >> >> On Sat, Apr 24, 2010 at 3:49 PM, Andrew Hakman <and...@gm...> >> wrote: >>> >>> Hi >>> >>> Just formatted a mini CF card as per the instructions and downloaded >>> todays overo image (201004232142). I'm using the console filesystem >>> image. >>> >>> During boot, I see a lot of i/o errors, but everything appears to work >>> normally. Is this normal? >>> >>> Here is some (clipped) dmesg output: >>> >>> EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode >>> VFS: Mounted root (ext3 filesystem) on device 179:2. >>> devtmpfs: mounted >>> Freeing init memory: 936K >>> hub 2-0:1.0: hub_suspend >>> usb usb2: bus auto-suspend >>> ehci-omap ehci-omap.0: suspend root hub >>> udev: starting version 151 >>> usb usb2: uevent >>> usb 2-0:1.0: uevent >>> usb usb1: uevent >>> usb 1-0:1.0: uevent >>> usb usb2: uevent >>> usb usb1: uevent >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 0 >>> Buffer I/O error on device mtdblock0, logical block 0 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 8 >>> Buffer I/O error on device mtdblock0, logical block 1 >>> end_request: I/O error, dev mtdblock0, sector 16 >>> Buffer I/O error on device mtdblock0, logical block 2 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 24 >>> Buffer I/O error on device mtdblock0, logical block 3 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 32 >>> Buffer I/O error on device mtdblock0, logical block 4 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 40 >>> Buffer I/O error on device mtdblock0, logical block 5 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 48 >>> Buffer I/O error on device mtdblock0, logical block 6 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 56 >>> Buffer I/O error on device mtdblock0, logical block 7 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 64 >>> Buffer I/O error on device mtdblock0, logical block 8 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 72 >>> Buffer I/O error on device mtdblock0, logical block 9 >>> end_request: I/O error, dev mtdblock0, sector 80 >>> end_request: I/O error, dev mtdblock0, sector 88 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 96 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 104 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 112 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 120 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 128 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 136 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 144 >>> end_request: I/O error, dev mtdblock0, sector 152 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 160 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 168 >>> end_request: I/O error, dev mtdblock0, sector 176 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 184 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 192 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 200 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 208 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 216 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 224 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 232 >>> uncorrectable error : >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 240 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 248 >>> uncorrectable error : >>> end_request: I/O error, dev mtdblock0, sector 0 >>> uncorrectable error : >>> >>> and on and on and on, then eventually (actually pretty quickly >>> timewise, but a long ways down in the dmesg) it finishes booting and >>> everything seems normal. >>> >>> What's going on? >>> >>> Andrew >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > |
From: Steve S. <sa...@gm...> - 2010-04-27 03:07:41
|
On Mon, Apr 26, 2010 at 7:17 PM, Andrew Hakman <and...@gm...> wrote: > Actually another question on this to people that know more than I do > about the bootloading process. > > I'm assuming x-load has to be in flash, and if I unprotect that region > and erase it, then the thing won't boot at all correct? If that's > gone, it won't boot from a SD card either right? No, it will still boot from a microSD card, even with an empty x-load partition in NAND. It will use the MLO file from the microSD card, which is actually just x-load with a different name. Why the different name? No idea! I've asked folks at TI and no one seemed to know (nor did anyone seem to know what MLO stood for!) Steve |
From: Ash C. <ash...@gm...> - 2010-04-27 03:34:45
|
Hi, My understanding was that MLO was supposed to be the signed version of x-load (looking back, my source was probably here: http://groups.google.com/group/beagleboard/msg/18b3c91e659ea206?pli=1). I guess this is some measure to ensure the authenticity of the bootstrap loader but I've never heard of anything not working with the 'unsigned' version. -Ash On Mon, Apr 26, 2010 at 8:07 PM, Steve Sakoman <sa...@gm...> wrote: > On Mon, Apr 26, 2010 at 7:17 PM, Andrew Hakman <and...@gm...> wrote: >> Actually another question on this to people that know more than I do >> about the bootloading process. >> >> I'm assuming x-load has to be in flash, and if I unprotect that region >> and erase it, then the thing won't boot at all correct? If that's >> gone, it won't boot from a SD card either right? > > No, it will still boot from a microSD card, even with an empty x-load > partition in NAND. > > It will use the MLO file from the microSD card, which is actually just > x-load with a different name. > > Why the different name? No idea! I've asked folks at TI and no one > seemed to know (nor did anyone seem to know what MLO stood for!) > > Steve > > ------------------------------------------------------------------------------ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2010-04-27 03:50:29
|
On Mon, Apr 26, 2010 at 8:34 PM, Ash Charles <ash...@gm...> wrote: > My understanding was that MLO was supposed to be the signed version of > x-load Yes, MLO on microSD is "signed"; but the signed version is also used in NAND. The unsigned version is only used when doing a USB or serial boot. Steve |