From: Paolo Pisati <p.pisati@gmail.com>
To: "T Krishnamoorthy, Balaji" <balajitk@ti.com>
Cc: Ming Lei <ming.lei@canonical.com>,
linux-mmc@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Ball <cjb@laptop.org>, Venkatraman S <svenkatr@ti.com>
Subject: Re: MMC: commit dba3c29 ruins mmc card data on beagle-xm revB
Date: Fri, 22 Jun 2012 13:51:42 +0200 [thread overview]
Message-ID: <4FE45C4E.8060808@gmail.com> (raw)
In-Reply-To: <CANrkHUawrQfb+o+W7FrYACv6NocZn_MAym5A209peP8tW1nZRQ@mail.gmail.com>
On 06/20/2012 09:23 AM, T Krishnamoorthy, Balaji wrote:
>>
>> i just want to say that i'm affected by this too, and i can reproduce it
>> 100%.
>>
>
> Is it with SD or MMC card
> Can you provide Beagle board rev info?
kingston 4g class 4 sdhc c04g taiwan
tested on a beagle xm rev a and rev c, both boards exhibit the same
problem with this card, while with a brand new sandisk 16gb sdhc class 4
card, everything is ok.
i tried reverting dba3c29 "Enable Auto CMD12", and both cards are
behaving fine.
>> do you want me to run that patch or you already have enough data?
>
> Can you enable MMC debug and apply the debug patch I provided.
> The debug patch did not print any AUTOCMD errors with Ming Lei setup.
http://people.canonical.com/~ppisati/mmc-testing/
test-mmc.sh: script used for testing
test-mmc.log: md5sum of file copied around (as you can see after the
umount the md5 changes)
test-mmc.syslog: mmc-debug output (plus your patch)
after the test, my sd card was so badly wounded that it wouldn't even boot.
--
bye,
p.
WARNING: multiple messages have this Message-ID (diff)
From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: MMC: commit dba3c29 ruins mmc card data on beagle-xm revB
Date: Fri, 22 Jun 2012 13:51:42 +0200 [thread overview]
Message-ID: <4FE45C4E.8060808@gmail.com> (raw)
In-Reply-To: <CANrkHUawrQfb+o+W7FrYACv6NocZn_MAym5A209peP8tW1nZRQ@mail.gmail.com>
On 06/20/2012 09:23 AM, T Krishnamoorthy, Balaji wrote:
>>
>> i just want to say that i'm affected by this too, and i can reproduce it
>> 100%.
>>
>
> Is it with SD or MMC card
> Can you provide Beagle board rev info?
kingston 4g class 4 sdhc c04g taiwan
tested on a beagle xm rev a and rev c, both boards exhibit the same
problem with this card, while with a brand new sandisk 16gb sdhc class 4
card, everything is ok.
i tried reverting dba3c29 "Enable Auto CMD12", and both cards are
behaving fine.
>> do you want me to run that patch or you already have enough data?
>
> Can you enable MMC debug and apply the debug patch I provided.
> The debug patch did not print any AUTOCMD errors with Ming Lei setup.
http://people.canonical.com/~ppisati/mmc-testing/
test-mmc.sh: script used for testing
test-mmc.log: md5sum of file copied around (as you can see after the
umount the md5 changes)
test-mmc.syslog: mmc-debug output (plus your patch)
after the test, my sd card was so badly wounded that it wouldn't even boot.
--
bye,
p.
next prev parent reply other threads:[~2012-06-22 11:51 UTC|newest]
Thread overview: 24+ 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
2012-06-11 2:47 ` Ming Lei
[not found] ` <CANrkHUYd8Ww6De4MiZ8_oPfcnhvtsZXOySLRiWSBU4QUQ6beHw@mail.gmail.com>
2012-06-11 7:20 ` Ming Lei
2012-06-11 7:20 ` Ming Lei
2012-06-13 5:26 ` S, Venkatraman
2012-06-13 5:26 ` S, Venkatraman
2012-06-13 15:28 ` T Krishnamoorthy, Balaji
2012-06-13 15:28 ` T Krishnamoorthy, Balaji
2012-06-14 5:18 ` Ming Lei
2012-06-14 5:18 ` Ming Lei
2012-06-14 10:25 ` Ming Lei
2012-06-14 10:25 ` Ming Lei
2012-06-15 1:55 ` Ming Lei
2012-06-15 1:55 ` Ming Lei
2012-06-19 16:53 ` Paolo Pisati
2012-06-19 16:53 ` Paolo Pisati
2012-06-20 2:02 ` Ming Lei
2012-06-20 2:02 ` Ming Lei
2012-06-20 7:23 ` T Krishnamoorthy, Balaji
2012-06-20 7:23 ` T Krishnamoorthy, Balaji
2012-06-22 11:51 ` Paolo Pisati [this message]
2012-06-22 11:51 ` Paolo Pisati
2012-06-22 15:33 ` T Krishnamoorthy, Balaji
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=4FE45C4E.8060808@gmail.com \
--to=p.pisati@gmail.com \
--cc=balajitk@ti.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=svenkatr@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.