lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20070703204853.57ecea17@poseidon.drzeus.cx>
Date:	Tue, 3 Jul 2007 20:48:53 +0200
From:	Pierre Ossman <drzeus-mmc@...eus.cx>
To:	"Midhun Agnihotram" <agnimidhun@...il.com>
Cc:	"Hans-Jürgen Koch" <hjk@...utronix.de>,
	jdi@....org, linux-kernel@...r.kernel.org
Subject: Re: Fwd: Mounting MMC card

On Tue, 3 Jul 2007 14:39:40 +0530
"Midhun Agnihotram" <agnimidhun@...il.com> wrote:

> Hi All,
> 
>    This is referring to my problem - not able to mount MMC card. I
> have some output from dmesg when I remove and put the card back (I
> have changes the kernel config to include i.MX SPI and disabled the
> generic SPI). DOes this give any clue as to why the MMC card is not
> appaering in /proc/partions and /sysfs/block ??  Any help will of
> great use. The output of dmesg is as follows. I have removed and
> inserted the card twice.
> 
> 
> <7>MMC: starting cmd 00 arg 00000000 flags 00000040
> <7>MMC: req done (00): 1: 00000000 00000000 00000000 00000000

These two and the ones like them were the ones I expected to see in
your dumps. So since you've discovered a way to get them functioning,
we can proceed with the debugging.

> <7>MMC: starting cmd 01 arg 00000000 flags 00000061
> <7>imx-mmc imx-mmc.0: CMD01 (0x01) mask set to 0x003b
> <7>imx-mmc imx-mmc.0: RESP 0x00000000, 0x00000000, 0x00000000,
> 0x00000000, error 0
> <7>MMC: req done (01): 0: 00000000 00000000 00000000 00000000

Here's your problem. CMD01 is a command that queries the cards for
their voltages. And the response is "no voltages". So either your host
driver is buggy, or your card is.

Have you tested with some other cards?

Also, the i.MX host driver is known to be a bit buggy. I would suggest
sending some questions out on the arm linux kernel mailing list as that
is where it's usually discussed.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  PulseAudio, core developer          http://pulseaudio.org
  rdesktop, core developer          http://www.rdesktop.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ