Re: Sandisk MMC I/O errors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I will try to as clear as possible.

When I reset, this is a complete reset of the board.
I tried Freescale's kernel version, and it works, even after reset and
several minutes.
The same sample, the same board, but with a 3.17-rc2 kernel, I get
those errors  would say about 95% of times. The first but can be ok,
but this is not invariable...

On another board, with another sample, it has the same problem, but I
would say about 80% of times.
I tried to use dynamic debug on boot in order to get all dev_dbg
messages, but for the moment I don't have them...

Thanks,
JM


2014-08-28 16:20 GMT+02:00 Hsin-Hsiang Tseng <hsinhsiangtseng@xxxxxxxxx>:
> No matter which sample you changed to test has this issue?
>
> Is your reboot means only re-init eMMC or entire platform?
> If you re-init eMMC by your customized flow, you need to guarantee the
> frequency and bus-width between host and device.
>
>
> 2014-08-28 15:28 GMT+08:00 Jean-Michel Hautbois
> <jean-michel.hautbois@xxxxxxxxxxx>:
>> Hi,
>>
>> 2014-08-09 11:05 GMT+02:00 Hsin-Hsiang Tseng <hsinhsiangtseng@xxxxxxxxx>:
>>> Could you change another sample to test?
>>> As a result, we can check this is a driver issue or sample issue.
>>
>> I can change whatever you want :). I noticed that on first boot it
>> seems to be working fine, but after some minutes, if I reboot (POR or
>> poweroff/poweron) I have those messages.
>>
>>>> [    4.518732] mmc0: req done (CMD18): 0: 00000900 00000000 00000000 00000000
>>>> [    4.518746] mmc0:     4096 bytes transferred: 0
>>>> [    4.518756] mmc0:     (CMD12): 0: 00000b00 00000000 00000000 00000000
>>> the eMMC has change state to data state(0xb00) and the data transferred 0...
>>> It means the cmd and clk pin work well. I will check the DMA and data
>>> lines(pin).
>>>> [    4.518545] mmc1: req done (CMD17): 0: 00000900 00000000 00000000 00000000
>>>> [    4.518563] mmc1:     0 bytes transferred: -84
>>> No data transferred from your platform to eMMC....even use single block read.
>>
>> What is the next step ? BTW, I am now on the latest 3.17-rc2 tag.
>>
>> Thanks,
>> JM
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux