From: "Yigal Sadgat" <YSadgat1@gcte.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
lsorense@csclub.uwaterloo.ca, sancelot@free.fr, liml@rtr.ca,
w@1wt.eu
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jwboyer@linux.vnet.ibm.com, joern@logfs.org,
linux-os@analogic.com, bart.vanassche@gmail.com, mangoo@wpkg.org,
helge.hafting@aitel.hist.no
Subject: Re: Compact Flash Question
Date: Tue, 13 May 2008 10:13:35 -0700 [thread overview]
Message-ID: <008e01c8b51c$ae840ae0$6401a8c0@techwriter> (raw)
In-Reply-To: 20080506230954.6e034cba@core
First, thank you to all that responded.
My original thought was that perhaps we're experiencing "soft errors". We
shipped several thousands of systems and a very small number of them (3 to 4
units) are showing this problem. I'm still waiting for these systems to come
back to us...
Meanwhile I found out that although we (Engineering) specified "SanDisk
ONLY" (only because they do wear leveling), our purchasing bought from other
manufacturers as well (Toshiba, Crucial, Kingstone). Crucial is absolutely
the LEAST reliable CF (system down!) and furthermore, their "lifetime
warranty" is a joke.
Regards,
Yigal Sadgat
next prev parent reply other threads:[~2008-05-13 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:59 Compact Flash Question Yigal Sadgat
2008-05-06 22:09 ` Alan Cox
2008-05-13 17:13 ` Yigal Sadgat [this message]
2008-05-06 22:22 ` linux-os (Dick Johnson)
2008-05-07 6:15 ` Bart Van Assche
2008-05-07 7:39 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 7:27 Tomasz Chmielewski
[not found] <48215673.3060201@wpkg.org>
[not found] ` <e2e108260805070044v42f596bbj39c5b52b6f0a096@mail.gmail.com>
2008-05-07 7:54 ` Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche
2008-05-07 12:31 ` Helge Hafting
2008-05-07 15:01 ` Stéphane ANCELOT
2008-05-07 16:46 ` Bart Van Assche
2008-05-08 13:26 ` Mark Lord
2008-05-08 14:27 ` Lennart Sorensen
2008-05-08 14:59 ` Willy Tarreau
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='008e01c8b51c$ae840ae0$6401a8c0@techwriter' \
--to=ysadgat1@gcte.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bart.vanassche@gmail.com \
--cc=helge.hafting@aitel.hist.no \
--cc=joern@logfs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mangoo@wpkg.org \
--cc=sancelot@free.fr \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).