linux-kernel - Re: Weird MMC errors: 2 of 2 - inconsistent state after data crc error

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: <46194692.3000601@drzeus.cx>
Date:	Sun, 08 Apr 2007 21:46:26 +0200
From:	Pierre Ossman <drzeus-mmc@...eus.cx>
To:	Alex Dubov <oakad@...oo.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Weird MMC errors: 2 of 2 - inconsistent state after data crc
 error

Alex Dubov wrote:
> Problem 2: After a data crc error all subsequent commands fail. May it be caused by stop command
> leaving card in some bad state (something clearable by SEND_STATUS)? On the other hand, is there a
> real need to issue a stop command in case main command failed?
> 

It might be, depending on what the problem is. E.g. timeout might still mean the
card processed the command and will start sending data.

Anyway, CRC errors should be extremely rare so I'd guess that either the card or
the controller has gotten confused. In many cases the card will shut down when
it gets annoyed, so that might be what you're seeing here.

Other than that, I'm not sure I can help that much. The stop commands should
never wedge the card, so that isn't the issue (unless the card is buggy).

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/