linux-kernel - Re: [PATCH] [OLPC] sdhci: add quirk for the Marvell CaFe's interrupt timeout

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]

Date:	Fri, 27 Jun 2008 13:42:14 -0400
From:	Andres Salomon <dilinger@...ued.net>
To:	Pierre Ossman <drzeus@...eus.cx>
Cc:	akpm@...ux-foundation.org, sdhci-devel@...t.drzeus.cx,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [OLPC] sdhci: add quirk for the Marvell CaFe's
 interrupt timeout

On Fri, 27 Jun 2008 19:30:01 +0200
Pierre Ossman <drzeus@...eus.cx> wrote:

> On Mon, 23 Jun 2008 10:13:52 -0400
> Andres Salomon <dilinger@...ued.net> wrote:
> 
> > 
> > The CaFe chip has a hardware bug that ends up with us getting a
> > timeout value that's too small, causing the following sorts of
> > problems:
> > 
> > [   60.525138] mmcblk0: error -110 transferring data
> > [   60.531477] end_request: I/O error, dev mmcblk0, sector 1484353
> > [   60.533371] Buffer I/O error on device mmcblk0p2, logical block
> > 181632 [   60.533371] lost page write due to I/O error on mmcblk0p2
> > 
> > Presumably this is an off-by-one error in the hardware.
> > Incrementing the timeout count value that we stuff into the
> > TIMEOUT_CONTROL register gets us a value that works.  This bug was
> > originally discovered by Pierre Ossman, I believe.
> > 
> > [thanks to Robert Millan for proving that this was still a problem]
> > 
> > Signed-off-by: Andres Salomon <dilinger@...ian.org>
> 
> Hmm... I'm not entirely sure about the specifics of the workaround
> here. It's likely that we'll have an off-by-minus-one in another
> controller, and off-by-two in a third.
> 
> Perhaps we should just have "broken timeout" and set the timeout to
> 0xE. It doesn't cause any side-effects except that the user will have
> to wait slightly longer for requests to fail if the card has decided
> to crap out.
> 

That would be fine.  OFW actually just hardcodes the timeout to 0xc,
with Mitch citing the same logic.  Just setting it to the upper bound
would certainly make it more applicable hardware other than the cafe.

--
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/