* eMMC write error in IMX6 Sabre AI board
@ 2014-11-07 11:35 vadivelan mani
2014-11-07 12:12 ` Fabio Estevam
0 siblings, 1 reply; 6+ messages in thread
From: vadivelan mani @ 2014-11-07 11:35 UTC (permalink / raw)
To: linux-mmc
Dear all,
I'm facing this unique problem during emmc write operation. I'm using a
Toshiba emmc device on Sabre AI board and linux kernel version 3.0.35.
The write operation is successful when i disable multi-block read/write.
But when multi block read/write is enabled, the writes fail for data of size
above 12KBytes. Please find the logs below for your reference. Any data
write upto 12KB, there is no problem. The error message is a data crc error
which i'm unable to figure why it is occuring.
===========================================================================
Data size <= 12KB - SUCCESS
-------------------
===========================================================================
root@freescale ~$ dd if=/file of=/dev/mmcblk0 bs=1024 count=12
mmc0: starting CMD18 arg 00000000 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f80000
mmc0: starting CMD18 arg 00000008 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f80000
mmc0: starting CMD18 arg 00000010 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f80000
mmc0: starting CMD25 arg 00000000 flags 000000b5
mmc0: blksz 512 blocks 24 flags 00000100 tsac 800 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 24
Block size 29184
Block size 7
=========> transfer_ mode 0x23
=============> flags 0x3a, cmd 25
intmask 0x8
Address after failure 0x74f80000
intmask 0x2
Address after failure 0x74f80000
mmc0: starting CMD13 arg 00010000 flags 00000195
===========host flags 0x5
--------------- ACMD23
=============> flags 0x1a, cmd 13
12+0 records in
12+0 records out
12288 bytes (12.0KB) copied, 0.178464 seconds, 67.2KB/s
============================================================================
Data size > 12KB - FAIL
-----------------
============================================================================
root@freescale ~$ dd if=/file of=/dev/mmcblk0 bs=1024 count=15
mmc0: starting CMD18 arg 00000000 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f00000
mmc0: starting CMD18 arg 00000008 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f00000
mmc0: starting CMD18 arg 00000010 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f00000
mmc0: starting CMD18 arg 00000018 flags 000000b5
mmc0: blksz 512 blocks 8 flags 00000200 tsac 50 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 8
Block size 29184
Block size 7
=========> transfer_ mode 0x33
=============> flags 0x3a, cmd 18
intmask 0xa
Address after failure 0x74f00000
mmc0: starting CMD25 arg 00000000 flags 000000b5
mmc0: blksz 512 blocks 32 flags 00000100 tsac 800 ms nsac 0
mmc0: CMD12 arg 00000000 flags 0000049d
===========host flags 0x5
=============> flags 0x1a, cmd 23
--------------- Not ACMD23
data Block size 0 512
Block count 32
Block size 29184
Block size 7
=========> transfer_ mode 0x23
=============> flags 0x3a, cmd 25
intmask 0x200002
============> need to send cmd12
=============> flags 0x1b, cmd 12
Address after failure 0x0
mmc0: starting CMD13 arg 00010000 flags 00000195
===========host flags 0x5
--------------- ACMD23
=============> flags 0x1a, cmd 13
mmcblk0: error -84 transferring data, sector 0, nr 32, cmd response 0x900,
card status 0xc00
end_request: I/O error, dev mmcblk0, sector 0
Buffer I/O error on device mmcblk0, logical block 0
lost page write due to I/O error on mmcblk0
end_request: I/O error, dev mmcblk0, sector 8
Buffer I/O error on device mmcblk0, logical block 1
lost page write due to I/O error on mmcblk0
end_request: I/O error, dev mmcblk0, sector 16
Buffer I/O error on device mmcblk0, logical block 2
lost page write due to I/O error on mmcblk0
end_request: I/O error, dev mmcblk0, sector 24
Buffer I/O error on device mmcblk0, logical block 3
lost page write due to I/O error on mmcblk0
15+0 records in
15+0 records out
15360 bytes (15.0KB) copied, 0.277967 seconds, 54.0KB/s
Please provide your valuable inputs for the same.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: eMMC write error in IMX6 Sabre AI board
2014-11-07 11:35 eMMC write error in IMX6 Sabre AI board vadivelan mani
@ 2014-11-07 12:12 ` Fabio Estevam
2014-11-10 8:44 ` Vadivelan M
0 siblings, 1 reply; 6+ messages in thread
From: Fabio Estevam @ 2014-11-07 12:12 UTC (permalink / raw)
To: vadivelan mani; +Cc: linux-mmc@vger.kernel.org
On Fri, Nov 7, 2014 at 9:35 AM, vadivelan mani
<vadivelan.mani@toshiba-tsip.com> wrote:
> Dear all,
> I'm facing this unique problem during emmc write operation. I'm using a
> Toshiba emmc device on Sabre AI board and linux kernel version 3.0.35.
Please try 3.18-rc3.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: eMMC write error in IMX6 Sabre AI board
2014-11-07 12:12 ` Fabio Estevam
@ 2014-11-10 8:44 ` Vadivelan M
2014-11-25 21:04 ` Robert Schwebel
0 siblings, 1 reply; 6+ messages in thread
From: Vadivelan M @ 2014-11-10 8:44 UTC (permalink / raw)
To: 'Fabio Estevam'; +Cc: linux-mmc@vger.kernel.org
Hi,
Thanks for your suggestion. But my kernel is fixed to version 3.0.35 and hence unable to use a different kernel. Please tell what is the problem in this kernel version if you already know. That would be very helpful.
NOTE: There may be some copyright messages below my mail which gets added automatically. Kindly ignore those messages.
Thanks and regards,
Vadivelan.
-----Original Message-----
From: Fabio Estevam [mailto:festevam@gmail.com]
Sent: 07 November 2014 17:42
To: Vadivelan M
Cc: linux-mmc@vger.kernel.org
Subject: Re: eMMC write error in IMX6 Sabre AI board
On Fri, Nov 7, 2014 at 9:35 AM, vadivelan mani <vadivelan.mani@toshiba-tsip.com> wrote:
> Dear all,
> I'm facing this unique problem during emmc write operation. I'm
> using a Toshiba emmc device on Sabre AI board and linux kernel version 3.0.35.
Please try 3.18-rc3.
The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: eMMC write error in IMX6 Sabre AI board
2014-11-10 8:44 ` Vadivelan M
@ 2014-11-25 21:04 ` Robert Schwebel
2014-11-26 3:21 ` Vadivelan M
0 siblings, 1 reply; 6+ messages in thread
From: Robert Schwebel @ 2014-11-25 21:04 UTC (permalink / raw)
To: Vadivelan M; +Cc: 'Fabio Estevam', linux-mmc@vger.kernel.org
On Mon, Nov 10, 2014 at 08:44:29AM +0000, Vadivelan M wrote:
> Thanks for your suggestion. But my kernel is fixed to version 3.0.35
> and hence unable to use a different kernel. Please tell what is the
> problem in this kernel version if you already know. That would be very
> helpful.
If you use such an old kernel, you are basically on your own;
community development & support takes place on top-of-tree.
Note that 3.0.35 is 227048 patches behind 3.18-rc6, and this does not
even take into account that you are probably using 3.0.35 plus thousands
of vendor patches. You can't seriously expect anyone in the community to
help you with issues which have long been solved.
Regards,
Robert
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: eMMC write error in IMX6 Sabre AI board
2014-11-25 21:04 ` Robert Schwebel
@ 2014-11-26 3:21 ` Vadivelan M
2014-11-26 6:23 ` Robert Schwebel
0 siblings, 1 reply; 6+ messages in thread
From: Vadivelan M @ 2014-11-26 3:21 UTC (permalink / raw)
To: 'Robert Schwebel'
Cc: 'Fabio Estevam', linux-mmc@vger.kernel.org
I understand. Ok then let me try to solve the issue by myself.
Thanks,
Vadivelan.
-----Original Message-----
From: Robert Schwebel [mailto:r.schwebel@pengutronix.de]
Sent: 26 November 2014 02:34
To: Vadivelan M
Cc: 'Fabio Estevam'; linux-mmc@vger.kernel.org
Subject: Re: eMMC write error in IMX6 Sabre AI board
On Mon, Nov 10, 2014 at 08:44:29AM +0000, Vadivelan M wrote:
> Thanks for your suggestion. But my kernel is fixed to version 3.0.35
> and hence unable to use a different kernel. Please tell what is the
> problem in this kernel version if you already know. That would be very
> helpful.
If you use such an old kernel, you are basically on your own; community development & support takes place on top-of-tree.
Note that 3.0.35 is 227048 patches behind 3.18-rc6, and this does not even take into account that you are probably using 3.0.35 plus thousands of vendor patches. You can't seriously expect anyone in the community to help you with issues which have long been solved.
Regards,
Robert
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: eMMC write error in IMX6 Sabre AI board
2014-11-26 3:21 ` Vadivelan M
@ 2014-11-26 6:23 ` Robert Schwebel
0 siblings, 0 replies; 6+ messages in thread
From: Robert Schwebel @ 2014-11-26 6:23 UTC (permalink / raw)
To: Vadivelan M; +Cc: 'Fabio Estevam', linux-mmc@vger.kernel.org
On Wed, Nov 26, 2014 at 03:21:47AM +0000, Vadivelan M wrote:
> I understand. Ok then let me try to solve the issue by myself.
Out of interest, why can't you go with mainline?
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-11-26 6:23 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-07 11:35 eMMC write error in IMX6 Sabre AI board vadivelan mani
2014-11-07 12:12 ` Fabio Estevam
2014-11-10 8:44 ` Vadivelan M
2014-11-25 21:04 ` Robert Schwebel
2014-11-26 3:21 ` Vadivelan M
2014-11-26 6:23 ` Robert Schwebel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox