From: CaT <cat@zip.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Ball <cjb@laptop.org>, 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: Thu, 3 Nov 2011 23:53:54 +1100 [thread overview]
Message-ID: <20111103125354.GZ3428@zip.com.au> (raw)
In-Reply-To: <4E710660.1060101@goop.org>
On Wed, Sep 14, 2011 at 12:54:08PM -0700, Jeremy Fitzhardinge wrote:
Ok. Thread is a bit dated but the bug is the same by the looks of it.
Apologies to anyone hit by the funk of a thousand years. :)
> On 09/14/2011 11:38 AM, Chris Ball wrote:
> > 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).
I have an X220 with the same issue. Using a MicroSDHC card with an adapter.
Windows likes it, Linux does not. Very similar looking errors as what Jeremy
has.
Linux: 3.1
BIOS: 1.21 (08/02/2011)
OS: Debian Wheezy
SanDisk adapter with Kingston 4GB MicroSDHC card.
I could help with any testing.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480
next prev parent reply other threads:[~2011-11-03 12:53 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
2011-11-03 12:53 ` CaT [this message]
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=20111103125354.GZ3428@zip.com.au \
--to=cat@zip.com.au \
--cc=cjb@laptop.org \
--cc=jeremy@goop.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.