All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Xu (Hello71)" <alex_y_xu@yahoo.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Wang Jian <larkwang@gmail.com>,
	wireguard@lists.zx2c4.com
Subject: Re: soft lockup - may be related to wireguard (backported)
Date: Mon, 04 May 2020 09:49:43 -0400	[thread overview]
Message-ID: <1588599653.habtnvnvne.none@localhost> (raw)
In-Reply-To: <CAHmME9oNus499EVFHVfLNjbOhU+vOV4P7R7USCm1ycNH2e0apA@mail.gmail.com>

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...

  parent reply	other threads:[~2020-05-04 13:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  3:55 soft lockup - may be related to wireguard (backported) 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) [this message]
2020-05-04 16:51     ` Wang Jian
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=1588599653.habtnvnvne.none@localhost \
    --to=alex_y_xu@yahoo.ca \
    --cc=Jason@zx2c4.com \
    --cc=larkwang@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.