From: Angelo Dureghello <angelo70@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: Re: davinci_mmc issues on kernel 3.17.0
Date: Thu, 20 Nov 2014 12:24:24 +0100 [thread overview]
Message-ID: <546DCF68.6040100@gmail.com> (raw)
In-Reply-To: <546CB7D2.50903@gmail.com>
Sorry for the confusion,
i realized the card i use in the old kernel board is 8G, the one in
kernel 3.17.0 is 4G,
so the size / inodes i see in mkfs or fdisk are correct.
I can confirm i have issues on the "write" part. With whatever FS,
if i format the card on PC, and then
fsck on the arm device board with kernel 3.17.0, fsck find no errors.
While if i mkfs on kernel 3.17.0 and then put the card on PC, it can't
even be mounted,
and fsck gives errors.
I finally run mmc_test, in both PIO 4-bit and DMA 4-bit modes:
in PIO, all tests pass except 17
[root@barix boot]# echo 17 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 17. Correct xfer_size at write (midway failure)...
mmc0: Result: ERROR (-84)
mmc0: Tests completed
in DMA, test 17 fails too, and test 25 locks up.
[root@barix boot]# echo 17 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 17. Correct xfer_size at write (midway failure)...
mmc0: Result: ERROR (-84)
mmc0: Tests completed.
[root@barix boot]# echo 25 > /sys/kernel/debug/mmc0/mmc0\:0002/test
mmc0: Starting tests of card mmc0:0002...
mmc0: Test case 25. Best-case read performance into scattered pages...
edma-dma-engine edma-dma-engine.1: edma_prep_slave_sg: Failed to
allocate slot
so seems i have some additional dma issue.
regards
next prev parent reply other threads:[~2014-11-20 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 14:32 davinci_mmc issues on kernel 3.17.0 Angelo Dureghello
2014-11-19 15:31 ` Angelo Dureghello
2014-11-20 11:24 ` Angelo Dureghello [this message]
2014-11-20 18:32 ` Angelo Dureghello
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=546DCF68.6040100@gmail.com \
--to=angelo70@gmail.com \
--cc=linux-mmc@vger.kernel.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