From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Alex Dubov <oakad@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird MMC errors: 1 of 2 - bad ocr value
Date: Sun, 08 Apr 2007 21:41:04 +0200 [thread overview]
Message-ID: <46194550.30203@drzeus.cx> (raw)
In-Reply-To: <20070314144437.3695.qmail@web36706.mail.mud.yahoo.com>
Alex Dubov wrote:
> Recently, I've obtained a bug report concerning an MMC card. Two problems are described, both
> sporadic.
> Problem 1: illegal ocr value is returned. You may notice, in the non-working case, obviously
> incorrect ocr value (0xffffffff) is returned. The card won't work after this, unless reinserted.
> What, to your opinion, shall we do about it?
>
I got something similar when there was problem with the power supply. The card
was booting through power it drain from the other pins, but it didn't work
correctly.
Try adding some more delay after you power up in case the controller needs some
time to stabilize.
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-04-08 19:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 22:20 [2.6.20] tifm_7xx1/mmc not working Andreas Steinmetz
2007-02-08 5:59 ` Pierre Ossman
2007-02-08 23:35 ` Alex Dubov
2007-02-09 12:27 ` Andreas Steinmetz
2007-02-09 15:14 ` Recent and not-so problems with tifm_sd driver Alex Dubov
2007-02-09 19:10 ` Pierre Ossman
2007-02-10 9:12 ` Recent and not-so problems with tifm_sd driver - one more Alex Dubov
2007-02-10 13:01 ` Pierre Ossman
2007-02-11 6:03 ` Brad Campbell
2007-02-11 14:52 ` Fabio Comolli
2007-02-11 15:40 ` Pierre Ossman
2007-02-11 15:56 ` Brad Campbell
2007-02-11 18:04 ` Pierre Ossman
2007-02-11 19:32 ` Brad Campbell
2007-02-12 9:14 ` Pierre Ossman
2007-02-12 10:50 ` Brad Campbell
2007-02-12 13:21 ` Andreas Steinmetz
2007-02-17 15:16 ` [mmc] incorrect behavior on resume Alex Dubov
2007-02-17 23:35 ` Pierre Ossman
2007-02-18 0:29 ` Pavel Machek
2007-02-18 1:46 ` Alex Dubov
2007-02-18 6:53 ` Russell King
2007-02-18 12:18 ` Alex Dubov
2007-02-11 4:47 ` Recent and not-so problems with tifm_sd driver Alex Dubov
2007-02-11 18:15 ` Pierre Ossman
2007-02-12 11:53 ` Alex Dubov
2007-02-12 13:49 ` Pierre Ossman
2007-02-13 0:44 ` Alex Dubov
2007-02-13 14:40 ` Alex Dubov
2007-02-17 23:14 ` Pierre Ossman
2007-02-17 23:51 ` Pierre Ossman
2007-02-18 4:59 ` Alex Dubov
2007-02-18 8:13 ` Pierre Ossman
2007-02-18 14:19 ` Alex Dubov
2007-02-18 15:10 ` Pierre Ossman
2007-02-18 23:48 ` Alex Dubov
2007-02-19 7:06 ` Pierre Ossman
2007-02-19 12:09 ` Alex Dubov
2007-02-19 12:34 ` Pierre Ossman
2007-02-20 1:30 ` Alex Dubov
2007-02-20 7:03 ` Pierre Ossman
2007-03-14 14:44 ` Weird MMC errors: 1 of 2 - bad ocr value Alex Dubov
2007-04-08 19:41 ` Pierre Ossman [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=46194550.30203@drzeus.cx \
--to=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.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.