linux-kernel - Re: [RFC] sdhci: timeouts

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: <BANLkTikmG5Me5vfja=6geYg7SW=k2KZxiA@mail.gmail.com>
Date:	Sat, 28 May 2011 19:17:52 -0400
From:	Charles Hannum <root@...ck.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] sdhci: timeouts

On Sat, May 28, 2011 at 19:09, Charles Hannum <root@...ck.net> wrote:
> 4) Ultimately I found that some SDHC cards just seem to take a good
> long time to respond.  I ended up increasing the write timeout to 1s
> and I've encountered 0 problems since then.  Since this is only an
> error condition, and therefore hardly of any performance concerns, I
> suggest it may be a good idea to do this in general.  See attached
> patch sdhci-timeout-limit.diff

BTW, I should mention that, with a TMCLK of 33000 (very common,
because it's just the PCI bus clock), increasing the limit from 300000
to 1000000 us actually increases the “counter” value by exactly 1
(from 11 to 12).  This is probably why the older controller-specific
hack of simply incrementing the counter worked.
--
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/