From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Samuel Holland <samuel@sholland.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Instability during large transfers
Date: Tue, 21 Mar 2017 18:33:56 +0100 [thread overview]
Message-ID: <CAHmME9pjcoNKOSjHEhyQ4T0mYcTj7eMmkKnuMb8GGp2sC1ayKA@mail.gmail.com> (raw)
In-Reply-To: <a346373b-b822-9275-210a-c2bf2842f793@sholland.org>
Hey Samuel,
Thanks for sticking with it... This is a super hard bug to track down!
I wish I could reproduce it.
Can you try two odd things, separately, and report back?
1. Compile with DEBUG_ATOMIC_SLEEP. Do you get any additional warnings?
2. Hack kernel/sched/Makefile to remove "-fno-omit-frame-pointer" and
see if the backtraces you get are a bit more coherent.
Feel free to find me on IRC.
Jason
prev parent reply other threads:[~2017-03-21 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:38 Samuel Holland
2017-02-17 4:48 ` Samuel Holland
2017-02-17 13:36 ` Jason A. Donenfeld
2017-02-17 17:37 ` Samuel Holland
2017-03-01 22:44 ` Samuel Holland
2017-03-21 15:06 ` Samuel Holland
2017-03-21 17:33 ` Jason A. Donenfeld [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=CAHmME9pjcoNKOSjHEhyQ4T0mYcTj7eMmkKnuMb8GGp2sC1ayKA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=samuel@sholland.org \
--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).