From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Chao Yu <yuchao0@huawei.com>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] F2fs failed on fresh installation 1st boot
Date: Thu, 17 Sep 2020 13:56:58 +0800 [thread overview]
Message-ID: <a70cb278-ef22-977b-87b0-f650ab9c8339@gtsys.com.hk> (raw)
In-Reply-To: <bc04f65d-dc90-dd3b-ed5c-dba60ebbbdc3@huawei.com>
On 14/9/2020 3:55 pm, Chao Yu wrote:
> Hi Chris,
>
> On 2020/9/14 15:38, Chris Ruehl wrote:
>> I must say sorry for the noise, I checked the Ram and CPU, we have a bad
>> RAM which can't follow the 992Mhz and causes the problem, once limit the
>> CPU speed to 800Mhz the problem is gone. Both 4.9 & 5.4
>
> Okay, out of curiosity, the frequency 992Mhz has exceed the frequency limitation
> of RAM?
Its a problem with the PCB, not the RAM and the frequency.
We take out the CPU for investigation and found some aging on the
balls and pads. Likely to much humidity.
>
>>
>> Please consider this bug as false-positive.
>
> Alright, let us know if you have any issue on f2fs use.
>
> Thanks,
we have new rollout on rk3399 with ddr4 and 8G eMMC 5.4 - 8 bit bus
tests run with 4.9 4.19 and 5.4 plus rt patch, no problems here.
>
>>
>>
>> Regards
>> Chris
>> .
>>
--
GTSYS Limited RFID Technology
9/F, Unit E, R07, Kwai Shing Industrial Building Phase 2,
42-46 Tai Lin Pai Road, Kwai Chung, N.T., Hong Kong
Tel (852) 9079 9521
Disclaimer: https://www.gtsys.com.hk/email/classified.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-09-17 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 4:20 [f2fs-dev] F2fs failed on fresh installation 1st boot Chris Ruehl
2020-09-12 6:19 ` Chris Ruehl
2020-09-14 7:30 ` Chao Yu
2020-09-14 7:38 ` Chris Ruehl
2020-09-14 7:55 ` Chao Yu
2020-09-17 5:56 ` Chris Ruehl [this message]
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=a70cb278-ef22-977b-87b0-f650ab9c8339@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
/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).