From: Wang Jian <larkwang@gmail.com>
To: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: soft lockup - may be related to wireguard (backported)
Date: Tue, 5 May 2020 00:51:02 +0800 [thread overview]
Message-ID: <CAF75rJA+Cs8Zspete8r4sZoZYP=N8+OVZnRK2JL5468VyiRZUQ@mail.gmail.com> (raw)
In-Reply-To: <1588599653.habtnvnvne.none@localhost>
Alex Xu (Hello71) <alex_y_xu@yahoo.ca> 于2020年5月4日周一 下午9:49写道：
>
> Excerpts from Jason A. Donenfeld's message of May 4, 2020 1:26 am:
> > Are you routing wireguard over wireguard, or something interesting like that?
> >
> > Is ipsec being used?
> >
>
> This "DN2800MT" looks like an Atom board from 2012; are you trying to
> run a very large bandwidth through it? I think it's plausible that
> buffering could cause a large enough chunk of work for a slow CPU that
> the kernel could erroneously think that the code is stuck. I don't know
> why that would happen on the tx thread though, or why it would result in
> an RCU stall, seeing as only a single access is made under an RCU lock
> in this function...
It's an old Atom CPU but still capable of handling at least 100Mbps
(even with encryption).
I have a prometheus running on this box, so I have monitoring data at
an interval of 15s.
Looking at the monitoring data
1. the event started from 1:02:00am, ended at 1:04:45am
2. peak time was 1:03:15am, for load, cpu usage and memory usage
3. available memory dropped from 3.359GB to 2.714GB at 1:03:15am, and
bounced up gradually
from this point
Seems it's related to wireguard's memory use, a cause or a result.
next prev parent reply other threads:[~2020-05-04 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 3:55 Wang Jian
2020-05-04 5:26 ` Jason A. Donenfeld
2020-05-04 12:49 ` Wang Jian
2020-05-04 13:49 ` Alex Xu (Hello71)
2020-05-04 16:51 ` Wang Jian [this message]
2020-05-04 10:47 ` Serge Belyshev
2020-05-04 22:55 ` Jason A. Donenfeld
2020-05-04 22:28 ` Jason A. Donenfeld
2020-05-05 6:54 ` Wang Jian
2020-05-05 0:05 ` Jason A. Donenfeld
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='CAF75rJA+Cs8Zspete8r4sZoZYP=N8+OVZnRK2JL5468VyiRZUQ@mail.gmail.com' \
--to=larkwang@gmail.com \
--cc=Jason@zx2c4.com \
--cc=alex_y_xu@yahoo.ca \
--cc=wireguard@lists.zx2c4.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).