From: svenkatr@ti.com (S, Venkatraman)
To: linux-arm-kernel@lists.infradead.org
Subject: MMC: commit dba3c29 ruins mmc card data on beagle-xm revB
Date: Wed, 13 Jun 2012 10:56:28 +0530 [thread overview]
Message-ID: <CANfBPZ-Sei434hV0edEEGeViwL6TXWsvRnprv7-Kf64dJ6_auQ@mail.gmail.com> (raw)
In-Reply-To: <CACVXFVP16UmHe-GGydrSMgGHwnkSvYhnY339=zr=BfCehvS8Kw@mail.gmail.com>
On Mon, Jun 11, 2012 at 12:50 PM, Ming Lei <ming.lei@canonical.com> wrote:
> On Mon, Jun 11, 2012 at 2:21 PM, T Krishnamoorthy, Balaji
> <balajitk@ti.com> wrote:
>> Hi Ming Lei,
>> Can you let me know if you noticed any write/timeout errors ?
>
> Nothing error logs found during writing.
>
> Below is one of my test case.
>
> root at beagleboard:~# upk
> updateing kernel...
> flush storage...
> root at beagleboard:~# cat bin/upk
> #!/bin/sh
>
> echo "updateing kernel..."
> cp -f /mnt/nfs/t/uImage /media/mmcblk0p1/
>
> echo "flush storage..."
> sync
> root at beagleboard:~# diff /mnt/nfs/t/uImage /media/mmcblk0p1/uImage
> Binary files /mnt/nfs/t/uImage and /media/mmcblk0p1/uImage differ
> root at beagleboard:~# umount /media/mmcblk0p1
> root at beagleboard:~# mount -t vfat /dev/mmcblk0p1 /media/mmcblk0p1
> root at beagleboard:~#
> root at beagleboard:~#
> root at beagleboard:~# diff /mnt/nfs/t/uImage /media/mmcblk0p1/uImage
> Binary files /mnt/nfs/t/uImage and /media/mmcblk0p1/uImage differ
>
Ming,
Just to keep you posted, Balaji and myself are trying to reproduce
the issue and haven't hit the problem yet.
This patch was in use internaly for sometime before we sent it upstream.
Meanwhile, is is possible for you to reproduce this problem with
MMC_DEBUG enabled ? That would be helpful.
~Venkat.
next prev parent reply other threads:[~2012-06-13 5:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 2:47 MMC: commit dba3c29 ruins mmc card data on beagle-xm revB Ming Lei
[not found] ` <CANrkHUYd8Ww6De4MiZ8_oPfcnhvtsZXOySLRiWSBU4QUQ6beHw@mail.gmail.com>
2012-06-11 7:20 ` Ming Lei
2012-06-13 5:26 ` S, Venkatraman [this message]
2012-06-13 15:28 ` T Krishnamoorthy, Balaji
2012-06-14 5:18 ` Ming Lei
2012-06-14 10:25 ` Ming Lei
2012-06-15 1:55 ` Ming Lei
2012-06-19 16:53 ` Paolo Pisati
2012-06-20 2:02 ` Ming Lei
2012-06-20 7:23 ` T Krishnamoorthy, Balaji
2012-06-22 11:51 ` Paolo Pisati
2012-06-22 15:33 ` T Krishnamoorthy, Balaji
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANfBPZ-Sei434hV0edEEGeViwL6TXWsvRnprv7-Kf64dJ6_auQ@mail.gmail.com \
--to=svenkatr@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).