From nobody Thu Jul 13 19:12:54 2023 X-Original-To: freebsd-embedded@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R244n165Mz4mflb for ; Thu, 13 Jul 2023 19:12:57 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smarthost1.sentex.ca", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R244m6c0vz4PQQ for ; Thu, 13 Jul 2023 19:12:56 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.17.1/8.16.1) with ESMTPS id 36DJCsJ5065245 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Thu, 13 Jul 2023 15:12:54 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4::29] ([IPv6:2607:f3e0:0:4:0:0:0:29]) by pyroxene2a.sentex.ca (8.16.1/8.15.2) with ESMTPS id 36DJCs9a050620 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 13 Jul 2023 15:12:54 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <028a3f80-4d90-3368-6f51-ab8f77c56154@sentex.net> Date: Thu, 13 Jul 2023 15:12:54 -0400 List-Id: Dedicated and Embedded Systems List-Archive: https://lists.freebsd.org/archives/freebsd-embedded List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-embedded@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: SD card corruption Content-Language: en-US To: Bob Bishop Cc: freebsd-embedded References: <709521ba-5719-5f80-10bf-1de05d99d5c1@sentex.net> From: mike tancsa In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.84 X-Rspamd-Queue-Id: 4R244m6c0vz4PQQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 7/13/2023 3:02 PM, Bob Bishop wrote: > > What’s the environment like? SD cards really don’t like being run hot for instance. Are there radios or other electrical noise nearby? Its a messy retail environment, but not too hot. The design of the APUs have excellent passive cooling and I monitor the CPU temp at a few hundred sites and have a good baseline. There is very little variation and failures dont seem to correlate with the few hot outliers. CPU is usually around 50C. (https://www.pcengines.ch/apucool.htm). The recent fail site the weekly avg was 49.9C with almost no variation / spikes Could exposure to a burst of intense em scramble the SD card ?  I would think other devices would be impacted if that were the case. Whats odd is that I am testing one of the returned cards right now. I wiped it, filled it with 15GB of a few random files and am continuously checksuming the files and they are fine. I would think that if the SD card failed, it would continue to fail. Hence, I am just trying to better understand what causes this. The SD card hardware layer is all "black box" to me     ---Mike