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: Tue, 19 Jun 2012 18:53:15 +0200 [thread overview]
Message-ID: <4FE0AE7B.4040502@gmail.com> (raw)
In-Reply-To: <CANrkHUaxJGcv2bdUWTCB_oKct-iFCKCdb7OQPTUjS4MuKeCS2w@mail.gmail.com>
On 06/13/2012 05:28 PM, T Krishnamoorthy, Balaji wrote:
> 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.
> Hi,
>
> Couldn't reproduce the issue with BeagleXM rev C, Might be a combination
> of rev and SD card. How often do you see mis-match in file content?
i just want to say that i'm affected by this too, and i can reproduce it
100%.
do you want me to run that patch or you already have enough data?
--
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: Tue, 19 Jun 2012 18:53:15 +0200 [thread overview]
Message-ID: <4FE0AE7B.4040502@gmail.com> (raw)
In-Reply-To: <CANrkHUaxJGcv2bdUWTCB_oKct-iFCKCdb7OQPTUjS4MuKeCS2w@mail.gmail.com>
On 06/13/2012 05:28 PM, T Krishnamoorthy, Balaji wrote:
> 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.
> Hi,
>
> Couldn't reproduce the issue with BeagleXM rev C, Might be a combination
> of rev and SD card. How often do you see mis-match in file content?
i just want to say that i'm affected by this too, and i can reproduce it
100%.
do you want me to run that patch or you already have enough data?
--
bye,
p.
next prev parent reply other threads:[~2012-06-19 16:53 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 [this message]
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
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=4FE0AE7B.4040502@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.