sdhc errors

Not sure what is happening here, but my kingston sdhc 4gb cards do not
seem to like 2.6.28, although one of them used to work with .27 (the
other one was aquired after mvoing to .28 and was never used on .27)

With the newest card I get:

....
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 SD4GB 3.76 GiB
mmcblk0: p1 p2
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing init memory: 196K
/bin/sh: can't access tty; job control turned off
/ # mmcblk0: error -110 transferring data
mmcblk0: error -110 transferring data
mmcblk0: error -110 transferring data
mmcblk0: error -110 transferring data
mmcblk0: error -110 transferring data

The other card says:

...
Remounting root file
system...
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
0
Buffer I/O error on device mtdblock0, logical block
0
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
8
Buffer I/O error on device mtdblock0, logical block
1
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
16
Buffer I/O error on device mtdblock0, logical block
2
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
24
Buffer I/O error on device mtdblock0, logical block
3
mmcblk0: error -110 transferring
data
end_request: I/O error, dev mmcblk0, sector
176723
Buffer I/O error on device mmcblk0p2, logical block
1
lost page write due to I/O error on
mmcblk0p2
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector
0
Buffer I/O error on device mtdblock0, logical block
0
mmcblk0: error -110 transferring
data
end_request: I/O error, dev mmcblk0, sector
964941
Buffer I/O error on device mmcblk0p2, logical block
98528
lost page write due to I/O error on
mmcblk0p2
end_request: I/O error, dev mmcblk0, sector
964947
Buffer I/O error on device mmcblk0p2, logical block
98529
lost page write due to I/O error on
mmcblk0p2
end_request: I/O error, dev mmcblk0, sector
964955
Buffer I/O error on device mmcblk0p2, logical block
98530
lost page write due to I/O error on
mmcblk0p2
mmcblk0: error -110 transferring
data
mmcblk0: error -110 transferring
data
end_request: I/O error, dev mmcblk0, sector
3326867
end_request: I/O error, dev mmcblk0, sector
3326875
end_request: I/O error, dev mmcblk0, sector
3326883
end_request: I/O error, dev mmcblk0, sector
3326891
end_request: I/O error, dev mmcblk0, sector
3326899
end_request: I/O error, dev mmcblk0, sector
3326907
end_request: I/O error, dev mmcblk0, sector
3326915
end_request: I/O error, dev mmcblk0, sector
3326923
end_request: I/O error, dev mmcblk0, sector
3326931
end_request: I/O error, dev mmcblk0, sector
3326939
end_request: I/O error, dev mmcblk0, sector
3326947
end_request: I/O error, dev mmcblk0, sector
3326955
end_request: I/O error, dev mmcblk0, sector
3326963
end_request: I/O error, dev mmcblk0, sector
3326971
end_request: I/O error, dev mmcblk0, sector
3326979
Aborting journal on device
mmcblk0p2.
ext3_abort
called.
EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected
aborted journal
Remounting filesystem read-
only
journal commit I/O
error
ext3_abort
called.
EXT3-fs error (device mmcblk0p2): ext3_remount: Abort forced by
user

Note that I fsck-ed this card on my unix box before putting it into
the beagle. This is the card that worked on .27!

Anyone an idea?

Frans

I have a 2GB card and it seems to be doing the same thing to me on .28

But what is strange is that after a few reboots it finally worked and
I could write to the SD card.

beagleboard login: mmcblk0: error -110 transferring data
end_request: I/O error, dev mmcblk0, sector 2397795
end_request: I/O error, dev mmcblk0, sector 2397803
end_request: I/O error, dev mmcblk0, sector 2397811
end_request: I/O error, dev mmcblk0, sector 2397819
end_request: I/O error, dev mmcblk0, sector 2397827
end_request: I/O error, dev mmcblk0, sector 2397835
end_request: I/O error, dev mmcblk0, sector 2397843
end_request: I/O error, dev mmcblk0, sector 2397851
end_request: I/O error, dev mmcblk0, sector 2397859
end_request: I/O error, dev mmcblk0, sector 2397867
end_request: I/O error, dev mmcblk0, sector 2397875
end_request: I/O error, dev mmcblk0, sector 2397883
end_request: I/O error, dev mmcblk0, sector 2397891
end_request: I/O error, dev mmcblk0, sector 2397899
end_request: I/O error, dev mmcblk0, sector 2397907
Aborting journal on device mmcblk0p2.
ext3_abort called.
EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected
aborted journal
Remounting filesystem read-only

~Brandon

I ran into the same errors when installing Debian on my RevC board
this last week. After a few failed attempts with the base install, I
decided to try an ext2 filesystem instead of ext3. I still get some
non-fatal errors (dozen+ over 4+ hours of package installs), but not
enough to force the filesystem to remount as readonly.

Could there be a problem with ext2/ext3 or SDHC access on 2.6.28? The
Debian install I did was the same kernel version.

-Chris

While looking through the latest 2.6.29 kernel sources, I saw some
fixes to the omap_hsmmc.c that might help. I think the driver was
using the incorrect SD response type in some cases. There was a good
description in the patch. Might help the situation. I see those same
errors on 2.6.27, but so far haven't bothered to backport the changes.

-Howard

Hi,

How to add usb otg driver beagle board in u-boot?

Regards,
Sanjeev

You mean USB tty support in u-boot? its already supported in our
latest sources.

http://git.gitorious.org/beagleboard/mainline.git branch: omap3-dev-usb

You might need to have usbser.sys, you can download the same from here,

http://support.microsoft.com/kb/943198

Regards,
Khasim

Hi,

Are you use otg as a host mode ?

If you use host mode you can use my patch:

This is source code:
git clone git://gitorious.org/u-boot-omap3/mainline.git u-boot-omap3-usb
git checkout -b omap3-dev-usb origin/omap3-dev-usb

OTG host support patch:
http://groups.google.com/group/beagleboard/msg/8e8cbd3770922b26

Best Regards,

Connie

Hi Khasim,

Thanks for the instructions regarding USBtty enabled u-boot… I compiled u-boot as you mentioned from omap3-dev-usb branch, and it comes up fine and while booting it shows that MUSB is enabled. But I’m having problem with Windows (XP) when it comes to the above mentioned Hotfix. The beagleboard is recognized as a CDC composite device but even after installing the hotfix, my PC cannot find the driver. It cannot find usbser.sys. It would be really helpful if you can provide any ideas about this.

Regards
-Nitin

Hello

Can't tell about usbtty or windows support, but here's a very simple
suggestion if you don't have any serial port.

If you happen to have a FTDI USB/Serial cable hanging around, simply
run MPROG to invert TX/RX.

Even a 5V version will be fine for communicating with the beagleboard
- something like
http://www.ftdichip.com/Products/EvaluationKits/TTL-232R.htm is quite
easy to fit into the pins. No need for a IDC10 adapter, then an
IDC10/USB serial adapter.

Guylhem

Hi Guylhem,

Thanks for your response… But I want to get the USB tty working not because I don’t have a serial port. In fact, I have been using the Airlink USB to serial convertor till now and having no issues working with the BeagleBoard with that.

But I wanted to get the USB-tty working because it’ll be great to have the board working with just one USB cable that provides power as well as serial terminal capability :). No more connecting a seperate serial cable. It’ll a very cool thing to have.

Looks like Windows is not looking for usbser.sys, but somthing else, maybe an .inf file. With the non MUSB u-boot, the Beagleboard is atleast detected as a RNDIS/Linux ethernet Gadget and linux.inf works fine for that class. But with the MUSB u-boot, its detected as an CDC Composite Gadget and that requires a different driver (cannot find what its looking for). I installed the hotfix as Khasim suggested but still no luck :frowning: .

I have searched but unable to find any inf file / driver for the MUSB device… Any help much appreciated …

Regards
-Nitin

Is this true :frowning:
http://kerneltrap.org/index.php?q=mailarchive/linux-usb/2009/1/24/4803014/thread

The problem is that I use Sun VirtualBox on windows to host Ubuntu. Now untill Windows recognizes the CDC Gadget, I cannot add the device under VirtualBox to make it visible under Ubuntu. Any helps ?

Thanks for your time.
-Nitin

Is this true :frowning:

An Interview With Linus Torvalds: Linux and Git - Part 1 | Tag1 Consulting

Not completely true. Windows can do CDC devices – No problem J

You just need to provide your own .inf-file (which of cause is different from device to device), and apparently nobody have done the exercise to create it for the standard (embedded) Linux CDC of a Networking card together with a serial port - yet - At least I have as well not been able to find any working .inf…

Best regards

Søren

Thanks Soren,

So for the time being, its sort of difficult to get the USB tty working with a Windows PC. Probably, I should install Linux on a dedicated partition
to get this working. Can you please let me know if I need any special packages for linux (ubuntu 8.10) to recognize the CDC device or it works out of the box ?

Regards
-Nitin

Can you please let me know if I need any special packages for linux

(ubuntu 8.10)

to recognize the CDC device or it works out of the box ?

To my understanding it's working out of the box, but I haven't tried it
myself...

Best regards
   Søren