From: "Subhash Jadavani" <subhashj@codeaurora.org>
To: 'Praveen Krishnan' <praveen.gk@gmail.com>, linux-mmc@vger.kernel.org
Subject: RE: DDR eMMC write failures
Date: Sun, 13 Nov 2011 22:18:54 +0530 [thread overview]
Message-ID: <000901cca224$22f49b40$68ddd1c0$@org> (raw)
In-Reply-To: <000601cca222$3a103430$ae309c90$@org>
You may also try by lowering the clock speed (from 50mhz to some lower value
say 40 or 30 Mhz). See if you are still seeing the data crc errors with
lower clock speed in DDR50 mode or not.
Regards,
Subhash
> -----Original Message-----
> From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
> owner@vger.kernel.org] On Behalf Of Subhash Jadavani
> Sent: Sunday, November 13, 2011 10:05 PM
> To: 'Praveen Krishnan'; linux-mmc@vger.kernel.org
> Subject: RE: DDR eMMC write failures
>
> I guess there is some issue with board level signal condition issue on
> MMC
> interface lines. You may try increasing the drive strength of interface
> lines from host controller side.
>
> Regards,
> Subhash
>
> > -----Original Message-----
> > From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
> > owner@vger.kernel.org] On Behalf Of Praveen Krishnan
> > Sent: Saturday, November 05, 2011 5:57 AM
> > To: linux-mmc@vger.kernel.org
> > Subject: Re: DDR eMMC write failures
> >
> > I am seeing some very strange things.
> >
> > When I do
> >
> > Dd if=/dev/zero of=/dev/mmcblk0 bs=512k count=200 (it fails when
> > writing about 100MB of data with a crc error)
> >
> > When I do
> > Dd if=/dev/zero of=/dev/mmcblk0 bs=64k count=3000 (it fails only
> after
> > 125 MB of data with a crc error)
> >
> > When I do
> >
> > Dd if=/dev/zero of=/dev/mmcblk0 bs=32k count=16000 (it fails when I
> > try to write 500MB of data, but good until 375MB of data)
> >
> > Any ideas what I am running into?
> >
> > Thanks,
> > Praveen
> >
> >
> > On Wed, Nov 2, 2011 at 4:51 PM, Praveen Krishnan
> <praveen.gk@gmail.com>
> > wrote:
> > > Hello all,
> > >
> > > I am working on getting the DDR50 mode up and running for the eMMC
> > > cards. I am running into some weird CRC error cases. Initially, I
> > > thought that everything works fine, but when I stress test it with
> > > large amounts of data (more than 100MB of writes), I notice that my
> > > console is spewed with venomous error messages. I get a CRC error
> > and
> > > every now and then, I also see this message "Got data interrupt
> even
> > > though no data operation was in progress" and "Buffer I/O error"
> and
> > > so on.
> > >
> > > Can anybody give any pointers as to what could be causing this?
> > >
> > > Thanks a lot,
> > > Praveen
> > >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-mmc"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-13 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 23:51 DDR eMMC write failures Praveen Krishnan
2011-11-05 0:26 ` Praveen Krishnan
2011-11-13 16:35 ` Subhash Jadavani
2011-11-13 16:48 ` Subhash Jadavani [this message]
2011-11-13 18:02 ` Praveen Krishnan
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='000901cca224$22f49b40$68ddd1c0$@org' \
--to=subhashj@codeaurora.org \
--cc=linux-mmc@vger.kernel.org \
--cc=praveen.gk@gmail.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.