From: "Vellemans, Noel" <Noel.Vellemans-jVIO7HaJqZIeKeHsXy56Pg@public.gmane.org>
To: "kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: SYNC - takes VERY long complete ( system freezes) !
Date: Tue, 18 Apr 2017 08:43:58 +0000 [thread overview]
Message-ID: <D24E577EA1E37B4788A3BFBC418F14A70750D5DD@wetsrvex01.loepfe.com> (raw)
Hi all,
I've been upgrading to a recent kernel ( for one of our boards). { Running on a 1- Ghz ARM single core CPU}
And I'm having an issue that keeps me busy for some days.
"sync" seems to take VERY long to complete. ( the whole system seems to freeze, so that finally the WATDOG triggers a reset)
There is no disk activity ( logs are stored on tmpfs ) ... .!
On a recent 4.4.61 kernel the time measured for the "sync" seems often to be more than 5 seconds ( up to 30 seconds).
# /usr/bin/time sync;
real 0m 8.01s
user 0m 0.00s
sys 0m 0.01s
{ fyi: system load with 'TOP' is less than 2%, I've been trying 4.4.43 and 4.4.61 .. both have the same 'behavoir'}
On an older 2.6.35.x kernel ( the kernel has been rebuild) I have this behavior.
# /usr/bin/time sync;
real 0m 0.01s
user 0m 0.00s
sys 0m 0.01s
I'm using same root-filesystem, for both builds (the only change is another (upgraded) kernel version) -> must be kernel related.
I'm using the same file systems , I've been trying ext2,ubifs, even FAT .
Old-2.6.35.x-Kernel : sync - time very good ( acceptable)
NEW-4.4.x-Kernel : sync - time .. BAD .. takes way to long. !!!
Any clue what could be the cause , or any hints that could explain ( and solve ?) this ..
Best Regards
Noel
next reply other threads:[~2017-04-18 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 8:43 Vellemans, Noel [this message]
[not found] ` <D24E577EA1E37B4788A3BFBC418F14A70750D5DD-bUMf7dFpk4BvAH7Z6HRyZmXnswh1EIUO@public.gmane.org>
2017-04-19 11:12 ` SYNC - takes VERY long complete ( system freezes) ! Hubert Chaumette
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=D24E577EA1E37B4788A3BFBC418F14A70750D5DD@wetsrvex01.loepfe.com \
--to=noel.vellemans-jvio7hajqziekehsxy56pg@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).