From mboxrd@z Thu Jan 1 00:00:00 1970 From: Douglas Gilbert Subject: Re: [Bug 39822] SDHC cards no longer recognized on AT91 based board Date: Mon, 24 Oct 2011 21:54:44 -0400 Message-ID: <4EA616E4.2060405@interlog.com> References: <201107282323.p6SNN9Jk026454@demeter1.kernel.org> Reply-To: dgilbert@interlog.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtp.infotech.no ([82.134.31.41]:44097 "EHLO smtp.infotech.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756171Ab1JYByv (ORCPT ); Mon, 24 Oct 2011 21:54:51 -0400 In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Chris Ball Cc: linux-mmc@vger.kernel.org, Nicolas Ferre , Jean-Christophe PLAGNIOL-VILLARD , ludovic.desroches@atmel.com, akpm@linux-foundation.org On 11-07-28 07:48 PM, Chris Ball wrote: > Hi, thanks for the bug report. Adding linux-mmc@ and some atmel driver > folks to CC. > > On Thu, Jul 28 2011, bugzilla-daemon@bugzilla.kernel.org wrote: >> Prior to 3.0.0 the FoxG20 board (Atmel AT91SAM9G20) could boot and use >> both micro SD and SDHC card to contain its root file system. With the >> advent of the 3.0.0 kernel the micro SDHC card is unable to mount the >> root file system. >> >> Comparing the relevant part of dmesg for 2.6.38.6 (and it worked on >> 2.6.39): >> ... >> Waiting for root device /dev/mmcblk0p2... >> mmc0: host does not support reading read-only switch. assuming write-enable. >> at91_mci at91_mci: Timeout waiting end of packet >> mmc0: new SDHC card at address 1234 >> mmcblk0: mmc0:1234 SA04G 3.67 GiB >> mmcblk0: p1 p2 p3 >> ... >> >> to the same dmesg section for 3.0.0 : >> ... >> Waiting for root device /dev/mmcblk0p2... >> mmc0: error -110 whilst initialising SD card >> at91_mci at91_mci: Timeout waiting end of packet >> mmc0: error -110 whilst initialising SD card >> [no further progress] >> >> Non "HC" SD cards work as expected in 3.0.0 > > If no-one on the CC list has any ideas, would you be interested in > trying to bisect this change? > > Another possibility would be adding printks before all of the -ETIMEDOUT > lines in core/* and host/at*, in order to see which one you're hitting > (and therefore which operation is causing the initialization to fail). > But a full bisection would be more conclusive. Still broken in lk 3.1.0, same errors in dmesg. Doug Gilbert