From: Roland Dreier <rdreier@cisco.com>
To: Romano Giannetti <romanol@upcomillas.es>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.34-rc1 eat my photo SD card :-(
Date: Sun, 04 Nov 2007 08:11:10 -0800 [thread overview]
Message-ID: <ada8x5ec7oh.fsf@cisco.com> (raw)
In-Reply-To: <1194168583.10245.15.camel@rukbat> (Romano Giannetti's message of "Sun, 04 Nov 2007 10:29:43 +0100")
I had something similar recently, trying to access an SD card in the
internal drive of my thinkpad X60. Fortunately, the data wasn't
actually corrupted, but when I tried to copy the picture files off the
card, I saw garbage filenames in the picture directory, and I saw this
in the kernel log:
[84797.855013] mmc0: new SD card at address b368
[84798.227299] mmcblk0: mmc0:b368 SD 501248KiB
[84798.227541] mmcblk0: p1
[84810.378736] FAT: Filesystem panic (dev mmcblk0p1)
[84810.378748] invalid access to FAT (entry 0x0000bfff)
[84810.378753] File system has been set read-only
[84810.378812] FAT: Filesystem panic (dev mmcblk0p1)
[84810.378816] invalid access to FAT (entry 0x0000ffbf)
(and on quite a bit longer)
When I put the same card back in the camera and used the camera's dock
to access the data via USB mass storage, everything worked fine. So
it does seem to be at least somewhat MMC-related.
Please let me know if there's further debug info that might be
helpful... this problem seems to be completely reproducible on my
system. I'm running a post 2.6.24-rc1 git tree
(v2.6.24-rc1-521-g54866f0 according to git describe).
- R.
next prev parent reply other threads:[~2007-11-04 16:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 11:56 2.6.34-rc1 eat my photo SD card :-( Romano Giannetti
2007-11-01 11:35 ` Nick Piggin
2007-11-01 17:17 ` Chuck Ebbert
2007-11-02 17:39 ` Pierre Ossman
2007-11-02 17:28 ` Pierre Ossman
2007-11-04 9:29 ` Romano Giannetti
2007-11-04 16:11 ` Roland Dreier [this message]
2007-11-05 7:31 ` Pierre Ossman
2007-11-05 10:51 ` Romano Giannetti
2007-11-05 12:22 ` Pierre Ossman
2007-11-05 13:46 ` Romano Giannetti
2007-11-05 15:26 ` Pierre Ossman
2007-11-05 17:18 ` Romano Giannetti
2007-11-06 9:58 ` Romano Giannetti
2007-11-06 10:28 ` Romano Giannetti
2007-11-06 19:51 ` Willy Tarreau
2007-11-06 21:02 ` Romano Giannetti
2007-11-06 21:48 ` Romano Giannetti
2007-11-06 22:17 ` Romano Giannetti
2007-11-07 6:09 ` Willy Tarreau
2007-11-07 21:52 ` Romano Giannetti
2007-11-07 23:37 ` Roland Dreier
2007-11-08 5:54 ` Pierre Ossman
2007-11-08 7:01 ` Jens Axboe
2007-11-10 10:32 ` Pierre Ossman
2007-11-08 8:46 ` *SPAM* " Romano Giannetti
2007-11-08 17:13 ` Roland Dreier
2007-11-08 17:43 ` Jens Axboe
2007-11-08 0:52 ` Rafael J. Wysocki
2007-11-05 13:51 ` Romano Giannetti
2007-11-05 15:25 ` Pierre Ossman
2007-11-05 7:30 ` Pierre Ossman
2007-11-07 22:09 ` Joshua Doll
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=ada8x5ec7oh.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=romanol@upcomillas.es \
/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