public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: 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: Tue, 13 Sep 2011 14:49:25 -0400	[thread overview]
Message-ID: <m2aaa89t1m.fsf@bob.laptop.org> (raw)
In-Reply-To: <4E6FA44F.1050705@goop.org> (Jeremy Fitzhardinge's message of "Tue, 13 Sep 2011 11:43:27 -0700")

Hi,

On Tue, Sep 13 2011, Jeremy Fitzhardinge wrote:
>> If it is running, and not helping, can I persuade you to try a full
>> bisection?
>
> OK, will do.

Thank you!

>>   I don't think we have other reports of this bug, and the
>> only other person who has reported something like it wasn't a kernel
>> hacker.
>
> That's interesting; the X220 is a pretty common machine these days, I
> think.  I wonder if there's variations in the SD controller or something?

I just asked Matthew Garrett to check his X220, and his has the same e823
controller as you, is running a 3.1-rc kernel, and everything's working.

So it's not even variation in the controller model, it's something even
more subtle.  Perhaps try some different cards?  What capacity/speed is
the one you're trying?  If there is a per-card difference, I suppose
we'd expect it to be that slower cards work and faster cards fail
(given the nature of the patch I linked in my last mail).

Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-09-13 18:49 UTC|newest]

Thread overview: 21+ 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 [this message]
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 16:28                                   ` Jeremy Fitzhardinge
2011-09-14 18:38                                     ` Chris Ball
2011-09-14 19:54                                       ` Jeremy Fitzhardinge
2011-11-03 12:53                                         ` CaT
2011-09-13 20:20           ` Jeremy Fitzhardinge

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=m2aaa89t1m.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=manoj.iyer@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox