From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
"agross@kernel.org" <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Annoying message on the console for the db845c board
Date: Fri, 6 Jan 2023 21:08:22 +0100 [thread overview]
Message-ID: <17e2d99d-31e5-b29a-e729-4f4d70b2efbc@linaro.org> (raw)
In-Reply-To: <CAA8EJpr0A=VjWEv6NPaZ-t_3TgNaWpsVO8_inJhxqoThry_zZA@mail.gmail.com>
On 06/01/2023 19:14, Dmitry Baryshkov wrote:
> On Fri, 6 Jan 2023 at 18:37, Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>>
>> Hi all,
>>
>> Does anyone have an idea on how to fix these timeout messages ? They are
>> displayed again and again every 5 seconds and that saturates the
>> filesystem after awhile.
>
> Could you please check that you have CONFIG_QCOM_RMTFS_MEM enabled and
> the rmtfs daemon running?
> I think that's the usual cause of such messages.
Yes, I have the option and the daemon running:
zcat /proc/config.gz | grep CONFIG_QCOM_RMTFS_MEM
CONFIG_QCOM_RMTFS_MEM=y
ps -ef | grep rmtfs
root 9888 1 2 20:07 ? 00:00:00 /usr/bin/rmtfs -r -P -s
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2023-01-06 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:37 Annoying message on the console for the db845c board Daniel Lezcano
2023-01-06 18:14 ` Dmitry Baryshkov
2023-01-06 20:08 ` Daniel Lezcano [this message]
2023-01-07 14:11 ` Dmitry Baryshkov
2023-01-07 19:01 ` Daniel Lezcano
2023-01-07 22:07 ` Dmitry Baryshkov
2023-01-07 22:51 ` Daniel Lezcano
2023-01-08 4:30 ` Dmitry Baryshkov
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=17e2d99d-31e5-b29a-e729-4f4d70b2efbc@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=p.zabel@pengutronix.de \
/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).