From: Romano Giannetti <romanol@upcomillas.es>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.34-rc1 eat my photo SD card :-(
Date: Sun, 04 Nov 2007 10:29:43 +0100 [thread overview]
Message-ID: <1194168583.10245.15.camel@rukbat> (raw)
In-Reply-To: <20071102182833.2c055446@poseidon.drzeus.cx>
On Fri, 2007-11-02 at 18:28 +0100, Pierre Ossman wrote:
> On Thu, 01 Nov 2007 12:56:42 +0100
> Romano Giannetti <romanol@upcomillas.es> wrote:
>
> Data loss is never fun. I hope you didn't have anything important on the card.
>
Well. A cousin-in-law marriage, would have been best not to lose it, but
I'll survive.
> > I have a flight waiting now, so I have put all the dmesgs and syslogs
> > over there:
> >
> > http://www.dea.icai.upcomillas.es/romano/linux/info/2624-rc1-mmc/
> >
Hmmm... the Uni server is down today. Darn.
> I'm afraid the logs are of little help. They are just filled with
> noise from the file system. You also seem to prove the FAT code to
> give an invalid pointer (the oops in the first dmesg).
>
Ok, I suspected it.
> Can you reproduce this? To help you I need to see the errors given by
> the MMC layer. You should also try reproducing it without a tainted
> kernel (i.e. don't load ndiswrapper).
I have a spare 128M card I can use to try. The one that failed was a 2G
one. I will try to reproduce without tainting the kernel (unfortunately,
the Atheros chip I have is not supported by ath5k yet, and the choice is
between ndiswrapper or Vista.). Should I enable some debugging option
for the MMC layer?
> Rgds
--
Sorry for the disclaimer --- ¡I cannot stop it!
--
La presente comunicación tiene carácter confidencial y es para el exclusivo uso del destinatario indicado en la misma. Si Ud. no es el destinatario indicado, le informamos que cualquier forma de distribución, reproducción o uso de esta comunicación y/o de la información contenida en la misma están estrictamente prohibidos por la ley. Si Ud. ha recibido esta comunicación por error, por favor, notifíquelo inmediatamente al remitente contestando a este mensaje y proceda a continuación a destruirlo. Gracias por su colaboración.
This communication contains confidential information. It is for the exclusive use of the intended addressee. If you are not the intended addressee, please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited by law. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this message. Thank you for your cooperation.
next prev parent reply other threads:[~2007-11-04 9:29 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 [this message]
2007-11-04 16:11 ` Roland Dreier
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=1194168583.10245.15.camel@rukbat \
--to=romanol@upcomillas.es \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.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