public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: Mike Kelly <pioto@pioto.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Matt Fleming <matt@console-pimps.org>,
	linux-mmc@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted
Date: Mon, 20 Sep 2010 20:50:21 -0700 (PDT)	[thread overview]
Message-ID: <731551.27747.qm@web37608.mail.mud.yahoo.com> (raw)
In-Reply-To: <20100920232517.4299f662@aether.home.pioto.org>

> > Can you confirm that the socket and media are good, by
> trying them out
> > under windows or something?
> 
> The same SD card and reader work fine under Windows Vista
> on this same
> machine. Ditto other SD cards in this reader. The fact that
> I am
> occasionally able to get this reader to work under Linux,
> though does
> make it seem like some timing or race issue that I'm
> hitting, though.
> 

It does not look like a pure software issue from the debug trace.
Host issues initialisation commands to the media (8, 5, 55), each is retried 3 times. For all of them, command execution fails with
hardware error flag set (and those are cleaned in between).

I still tend to blame improper hardware initialisation, but I'll try
to look and see if there can be something else.



      

      reply	other threads:[~2010-09-21  3:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18602-10286@https.bugzilla.kernel.org/>
2010-09-15 19:38 ` [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted Andrew Morton
2010-09-17 13:54   ` Matt Fleming
2010-09-18  7:23     ` Alex Dubov
2010-09-18  9:01       ` Mike Kelly
2010-09-19  5:19         ` Alex Dubov
2010-09-19 14:56           ` Mike Kelly
2010-09-20  0:50             ` Alex Dubov
2010-09-21  3:25               ` Mike Kelly
2010-09-21  3:50                 ` Alex Dubov [this message]

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=731551.27747.qm@web37608.mail.mud.yahoo.com \
    --to=oakad@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=pioto@pioto.org \
    /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