All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Ball <cjb@laptop.org>
Cc: Philip Rakity <prakity@marvell.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Manoj Iyer <manoj.iyer@canonical.com>
Subject: Re: SDHCI regression since 2.6.39
Date: Wed, 14 Sep 2011 12:54:08 -0700	[thread overview]
Message-ID: <4E710660.1060101@goop.org> (raw)
In-Reply-To: <m2boun9dg1.fsf@bob.laptop.org>

On 09/14/2011 11:38 AM, Chris Ball wrote:
> Hi,
>
> On Wed, Sep 14 2011, Jeremy Fitzhardinge wrote:
>> I powered it off with battery unplugged for about an hour, and rebooted
>> into the known-working kernel, making sure that any fancy power mgmt
>> features were disabled (like aspm), but it still failed in the same way.
>>
>> I'm wondering if it's simply something like the socket has failed, and
>> one or more of the terminals isn't connecting to the card?  Though that
>> would only show problems on card insertion, but I gather the driver is
>> having problems from the moment it detects the controller?
> I don't think it's true that we're having any problems talking to the
> controller other than with a card inserted -- do you see any errors in
> dmesg before inserting a card?
>
> It could indeed be some kind of signal integrity issue.  The easy way to
> investigate that would be to boot Windows and see if it works there, and
> the hard way would be to find a friendly hardware hacker with a nice scope.

I have the original HDD with Windows on it around here somewhere; when I
get the chance I'll switch them around and see what Windows thinks of it
(I guess if its still failing then its a warranty fix).

    J

  reply	other threads:[~2011-09-14 19:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13  0:29 SDHCI regression since 2.6.39 Jeremy Fitzhardinge
2011-09-13  0:36 ` Jeremy Fitzhardinge
2011-09-13 13:22 ` Chris Ball
2011-09-13 17:00   ` Jeremy Fitzhardinge
2011-09-13 17:12     ` Chris Ball
2011-09-13 18:43       ` Jeremy Fitzhardinge
2011-09-13 18:49         ` Chris Ball
2011-09-13 19:29           ` Manoj Iyer
2011-09-13 20:27             ` Jeremy Fitzhardinge
2011-09-13 20:29               ` Philip Rakity
2011-09-13 20:38               ` Jeremy Fitzhardinge
     [not found]               ` <D45CBF70-F0B1-453A-9E31-A621F52C21B9@marvell.com>
     [not found]                 ` <4E6FC422.9080306@goop.org>
     [not found]                   ` <7C3ED924-555D-4C50-9000-36077650328C@marvell.com>
     [not found]                     ` <4E6FCE28.5040403@goop.org>
     [not found]                       ` <F54ECF19-5E4C-40A6-8E26-99BF223F9FE2@marvell.com>
2011-09-13 22:32                         ` Jeremy Fitzhardinge
2011-09-13 22:42                           ` Jeremy Fitzhardinge
2011-09-13 22:48                             ` Philip Rakity
2011-09-14  0:52                               ` Jeremy Fitzhardinge
2011-09-14 13:48                                 ` Chris Ball
2011-09-14 13:48                                   ` Chris Ball
2011-09-14 16:28                                   ` Jeremy Fitzhardinge
2011-09-14 18:38                                     ` Chris Ball
2011-09-14 18:38                                       ` Chris Ball
2011-09-14 19:54                                       ` Jeremy Fitzhardinge [this message]
2011-11-03 12:53                                         ` CaT
2011-09-13 20:20           ` Jeremy Fitzhardinge
2012-06-28 14:35             ` Srinivas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E710660.1060101@goop.org \
    --to=jeremy@goop.org \
    --cc=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=manoj.iyer@canonical.com \
    --cc=prakity@marvell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.