Still SD error with 2.6.34
Federico Pietro Briata
I had test with file shared on google code:
uImage-2.6.34-debian-20100530
modules-2.6.34-debian-20100530
debian-armel-lenny-rootfs-20091017
the boot was ok, then from the shell I made apt-get update and....
simone:~# uname -A
mmcblk0: retrying using single block read
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 6549520
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 6549521
mmcblk0: retrying using single block read
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 6549520
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 6549521
Segmentation fault
simone:~# mmcblk0: retrying using single block read
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064426
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064427
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=643
....
.....
....
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
INIT: mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
Id "T0" respawning too fmmcblk0: error -110 sending status comandast: disabled o
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
r 5 minutesend_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
quiet_error: 10 callbacks suppressed
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064426
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064427
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=643
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064416
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064417
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2065450
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2068642
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 4528134
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=648
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2065438
Buffer I/O error on device mmcblk0, logical block 1032719
lost page write due to I/O error on mmcblk0
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2065444
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064396
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064397
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=648
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064420
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064421
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=640
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064394
Buffer I/O error on device mmcblk0, logical block 1032197
lost page write due to I/O error on mmcblk0
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 4521990
Buffer I/O error on device mmcblk0, logical block 2260995
lost page write due to I/O error on mmcblk0
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064386
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064387
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: read_block_bitmap: Cannot read block bitmap - block_g3
mmcblk0: retrying using single block read
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064426
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2064427
EXT2-fs: mmcblk0 previous I/O error to superblock detected
mmcblk0: error -110 sending status comand
mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
end_request: I/O error, dev mmcblk0, sector 2
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
EXT2-fs (mmcblk0): error: ext2_get_inode: unable to read inode block - inode=643
Federico Pietro Briata
Martin Guy
> I had test with file shared on google code:
>
> uImage-2.6.34-debian-20100530
> modules-2.6.34-debian-20100530
> debian-armel-lenny-rootfs-20091017
>
> the boot was ok, then from the shell I made apt-get update and....
>
> simone:~# uname -A
> mmcblk0: retrying using single block read
> mmcblk0: error -38 sending read/write command, response 0x4, card status 0x0
> end_request: I/O error, dev mmcblk0, sector 6549520
Hi
Thanks for the problem report.
Are you using the hacked U-Boot bootloader on the downloads page
that accesses the RAM in 16-bit mode? That is necessary to work
around a bug in the EP9307 rev E1 silicon's USB hardware, although it
leaves you with 32MB RAM instead of 64MB.
If not, can you try using that? Instructions are in the wiki->BootLoader page
M
Martin Guy
>
> uImage-2.6.34-debian-20100530
> modules-2.6.34-debian-20100530
> debian-armel-lenny-rootfs-20091017
Note that you should also unpack modules-2.6.34-20100530.tgz into the
root filesystem (after deleting its /lib/modules/* if you like).
You may then also need to run "depmod -a" to rebuild the module index.
However, the MMC card stuff is built into our Debian kernel, so this
should not be the cause of your problem.
M
Federico Pietro Briata
> Hi
> Thanks for the problem report.
Hi Martin,
thank you for the support.
> Are you using the hacked U-Boot bootloader on the downloads page
> that accesses the RAM in 16-bit mode? That is necessary to work
> around a bug in the EP9307 rev E1 silicon's USB hardware, although it
> leaves you with 32MB RAM instead of 64MB.
> If not, can you try using that? Instructions are in the wiki->BootLoader page
I'm still using RAM in 32-bit mode.
I thought that EP9307 bug was inherent only with USB stuff [when not
used in low-speed USB
1.1 devices mode (like keyboard, mice)] and not inherent for MMC card
stuff. Am I wrong?
> You may then also need to run "depmod -a" to rebuild the module index.
thanks for the tip i forgot to do that.
> However, the MMC card stuff is built into our Debian kernel, so this
> should not be the cause of your problem.
right, but consider that my root device is in MMC card (not USB drive)
and also that issue happens always after something like: "apt-get
update".
federico
Martin Guy
> 2010/9/15 Martin Guy <marti...@gmail.com>:
> > Are you using the hacked U-Boot bootloader on the downloads page
> > that accesses the RAM in 16-bit mode? That is necessary to work
> > around a bug in the EP9307 rev E1 silicon's USB hardware, although it
> > leaves you with 32MB RAM instead of 64MB.
> > If not, can you try using that? Instructions are in the wiki->BootLoader page
>
> I'm still using RAM in 32-bit mode.
> I thought that EP9307 bug was inherent only with USB stuff [when not
> used in low-speed USB
> 1.1 devices mode (like keyboard, mice)] and not inherent for MMC card
> stuff. Am I wrong?
You are right. I am confused.
> > However, the MMC card stuff is built into our Debian kernel, so this
> > should not be the cause of your problem.
>
> right, but consider that my root device is in MMC card (not USB drive)
> and also that issue happens always after something like: "apt-get
> update".
Bad news! That was the exact symptom when using the old Cirrus
2.6.24.7 kernel's MMC-SPI driver, and I have never seen it using the
new one in 2.6.34. You are sure you are running 2.6.34-20100530?
(Yes, I am clutching at straws here!)
M
Federico Pietro Briata
>
> I am confused.
Me too and the mystery deepens... :/
>
> Bad news! That was the exact symptom when using the old Cirrus
> 2.6.24.7 kernel's MMC-SPI driver, and I have never seen it using the
> new one in 2.6.34. You are sure you are running 2.6.34-20100530?
> (Yes, I am clutching at straws here!)
Yes because I saw 2.6.34 in uboot log, but if we consider the Murphy's
law then lets say I don't know...
Did you test MMC stuff and 2.6.34 also in 32 bit ram mode? if no, can
the new MMC driver need 16 bit ram mode is some way?!
fede
Martin Guy
> the new MMC driver need 16 bit ram mode is some way?!
Nom, but it should make no difference to MMC - and - I doubt it.
Let me check I got the 20100530 kernel right, and let me run some tests here.
M
Martin Guy
> Let me check I got the 20100530 kernel right, and let me run some tests here.
Hi
I'm getting the same kind of errors. -84 (TIMEOUT) and -71 (Protocol error).
In SD card world there is a hardware modification you can make: the
chip-select line from the processor to the SD card is SFRMOUT. This is
only asserted while there is an active communication in progress. This
means that, when there is a multi-message transcation in progress, the
CS line gets de-asserted between the two transactions, which is
illegal as far as SD protocol is concerned, but it is tolerated by
most SD cards. The fix is to break the track from pin 1 of the SD
card (the CS line), run a wire from SDcard Pin 1 to pin 28 of JP9,
then modify the linux kernel to use *that* as the chip select by
changing in arch/arm/mach-ep93xx/simone.c uncomment the line
#define MMC_CHIP_SELECT_GPIO EP93XX_GPIO_LINE_EGPIO1
This makes EGPIO1 act as an additional chip select for the SD card,
but without de-asserting it between multi-message transactions. For SD
cards that are sensitive to this difference, it can make a difference.
I've made a modification to my prototype to be able to test SD card
with SFRMOUT chipselect or using a GPIO for the same function. My
results are that it is unreliable on both configurations.
A second factor you should consider is EMI. I've seen the sim.one
being unable to boot in an EMI-rich envoronment (a trade fair with
many naked boards in the area). Maybe you could try electrically
isolating it with earth screens.
Let us know what results you obtain
M
Federico Pietro Briata
2010/9/23 Martin Guy <marti...@gmail.com>:
> On 9/15/10, Martin Guy <marti...@gmail.com> wrote:
> The fix is to break the track from pin 1 of the SD
> card (the CS line),
unfortunately I overheated the pin 1 on Breakout Board and now I need
to change it... ;/
To fix it, should I buy this one?
http://www.sparkfun.com/commerce/product_info.php?products_id=204
> then modify the linux kernel to use *that* as the chip select by
> changing in arch/arm/mach-ep93xx/simone.c uncomment the line
>
> #define MMC_CHIP_SELECT_GPIO EP93XX_GPIO_LINE_EGPIO1
Can I do it on old Cirrus 2.6.24.7 kernel or SD will work on
2.6.34-20100530 only?
federico
Martin Guy
> > changing in arch/arm/mach-ep93xx/simone.c uncomment the line
> >
> > #define MMC_CHIP_SELECT_GPIO EP93XX_GPIO_LINE_EGPIO1
>
> Can I do it on old Cirrus 2.6.24.7 kernel or SD will work on
> 2.6.34-20100530 only?
I;ve only done this with the 2.6.34 kernel, and only that version has
the extra code fragments to be able to drive a GPIO as the chipselect.
I suppose you could backport that to the CIrrus kernel, but their SD
card driver transfers data at half the speed of ours, uses 100% CPU
instead of 50%, suffers from data errors and can't handle SDHC cards.
M
martinwguy
On Sep 23, 1:57 pm, Martin Guy <martinw...@gmail.com> wrote:
>
> > Let me check I got the 20100530 kernel right, and let me run some tests here.
>
> Hi
> I'm getting the same kind of errors. -84 (TIMEOUT) and -71 (Protocol error).
> In SD card world there is a hardware modification you can make: the
> chip-select line from the processor to the SD card is SFRMOUT. This is
> only asserted while there is an active communication in progress. This
> means that, when there is a multi-message transcation in progress, the
> CS line gets de-asserted between the two transactions, which is
> illegal as far as SD protocol is concerned, but it is tolerated by
> most SD cards. The fix is to break the track from pin 1 of the SD
> card (the CS line), run a wire from SDcard Pin 1 to pin 28 of JP9,
> then modify the linux kernel to use *that* as the chip select by
> changing in arch/arm/mach-ep93xx/simone.c uncomment the line
>
> #define MMC_CHIP_SELECT_GPIO EP93XX_GPIO_LINE_EGPIO1
>
> This makes EGPIO1 act as an additional chip select for the SD card,
> but without de-asserting it between multi-message transactions. For SD
> cards that are sensitive to this difference, it can make a difference.
> I've made a modification to my prototype to be able to test SD card
> with SFRMOUT chipselect or using a GPIO for the same function. My
> results are that it is unreliable on both configurations.
GPIO-as-chip-select hardware modification.
WIth a 2GB MLC SD card, I'm getting
mmcblk0: error -38 sending read/write command, response 0x4, card
status 0x0
The sector number varies and error -38 is ENOSYS ("Function not
implemented")
With a 1GB "SD card" (neither MLC nor SDHC) I am unable to provoke any
read/write errors by using it as a root filesystem and repeatedly
going:
# rm /var/lib/apt/lists/*_Packages /var/cache/apt/*.bin
# apt-get update
but during apt-get upgrade I managed to get
mmcblk0: error -84 transferring data, sector 64, nr 4, card status 0x0
end_request: I/O error, dev mmcblk0, sector 68
Buffer I/O error on device mmcblk0p1, logical block 2
lost page write due to I/O error on mmcblk0p1
... followed by a kernel stack backtrace and system hang
Ho hum
M