linux-kernel - OLPC XO-1 sdhci regression

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-next>] [day] [month] [year] [list]

Message-ID: <20090220124343.707b83b4@ephemeral>
Date:	Fri, 20 Feb 2009 12:43:43 -0500
From:	Andres Salomon <dilinger@...ued.net>
To:	drzeus-sdhci@...eus.cx
Cc:	sdhci-devel@...t.drzeus.cx, linux-kernel@...r.kernel.org,
	cjb@...top.org
Subject: OLPC XO-1 sdhci regression

Hi Pierre,

With the current Linus git tree, the sdhci driver fails to find the partition
table on cards during bootup on OLPC XO-1 machines.  This makes booting off of
SD impossible.  The errors go something like this:

 mmcblk0:
mmc0: Timeout waiting for hardware interrupt.
mmcblk0: error -110 sending stop command
end_request: I/O error, dev mmcblk0, sector 0
Buffer I/O error on device mmcblk0, logical block 0
[repeat a bunch of times]
  unable to read partition table

No oopses or anything, the SD controller just fails to read the partition
table off the card.

I bisected a bit, and that led me to this commit:

 commit e809517f6fa5803a5a1cd56026f0e2190fc13d5c
 Author: Pierre Ossman <drzeus@...eus.cx>
 Date:   Fri Jul 25 01:09:08 2008 +0200

     sdhci: let the controller wait for busy state to end

     The sdhci controllers can interrupt us when the busy state from the
     card has ended, saving CPU cycles and power.

     Signed-off-by: Pierre Ossman <drzeus@...eus.cx>

Reverting that commit allows the driver to read the partition table.
--
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/