linux-kernel - Re: tifm_7xx1: SD card is ignored

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c878e2290805230232n441351bl3a1038dfacffb4d8@mail.gmail.com>
Date:	Fri, 23 May 2008 11:32:32 +0200
From:	"Kim Hansen" <kimhanse@...il.com>
To:	"Pierre Ossman" <drzeus@...eus.cx>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: tifm_7xx1: SD card is ignored

On Wed, May 21, 2008 at 2:21 PM, Pierre Ossman <drzeus@...eus.cx> wrote:
> On Wed, 7 May 2008 18:50:54 +0200
> "Kim Hansen" <kimhanse@...il.com> wrote:
>
>> Now it just looks like it sometimes work and other times don't, on
>> some kernels it works on 80% inserts and on other it only works on 5%.
>> This means that the problem most likely has not been fixed between
>> 2.6.24 and 2.6.25, it was just a coincidence that it worked on on and
>> not the other the first few times I tested it.
>
> I missed the start of this, but I assume it is just the one card that
> exhibits this craziness?

I can reproduce it on 3 different cards: SD 512MB, SD 4GB, MMC 64kB.

>> I have captured some logs now, there is logs of a successful insert
>> and remove, and of an unsuccessful.
>>
>> Successful  insert: 16:18:50   remove:  16:20:26
>> Unsuccessful insert:  16:21:38  remove:  16:21:47
>>
>> The log can be found at: http://i9.dk/~kim/mmc-log.txt.bz2
>>
>> This is the part from the unsuccessful insert:
>
> *snip*
>
>> sdhci [sdhci_irq()]: *** sdhci:slot0 got interrupt: 0x00000001
>> mmc0: req done (CMD5): 0: ffffffff 00000000 00000000 00000000
>
> What can I say, the card thinks it's an SDIO card. :)
>
> The question is why. Might be some shoddy wiring between the card and
> the controller that causes some unlucky misinterpretations. Might also
> be that the card needs some increased delay to function correctly. Try
> adding:
>
>        msleep(500);
>
> to mmc_rescan() in drivers/mmc/core/core.c. Put it right after
> mmc_power_up().

I will try that.

-- 
Kim Hansen
Vadgårdsvej 3, 2.tv
2860 Søborg
Fastnet: 3956 2437 -- Mobil: 3091 2437
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/