On Wed, 2018-06-13 at 03:58 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
>
> The current patch I'm now considering is here:
> https://git.zx2c4.com/WireGuard/patch/?id=17fb4ff6064e10bb91bf2ccf653
> 4bfdf767a9b90
Ahh!
Last night I recompiled with your first patch and left the machine
running - thi
Hi Paul,
> But although the machine froze I dont see the BUG's in the kernel log.
Alright, so this means I've determined the root cause of the BUGs you
were seeing before, and both the patch you applied and hopefully the
one I committed should take care of that. However, this lockup...
> Last ni
Hi Paul,
I got an -rt kernel up and running, enabled a bunch of nice debugging
options, and found a handful of problems, all of which were fixed by:
https://git.zx2c4.com/WireGuard/commit/?id=0f05452d043d8d047cf5d7987fc2732b97d676e6
I realize the solution in that patch is a bit of a bummer, but a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
A new snapshot, `0.0.20180613`, has been tagged in the git repository.
Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release that would be
considered secure
On Wed, 2018-06-13 at 14:13 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
>
> > But although the machine froze I dont see the BUG's in the kernel
> > log.
>
> Alright, so this means I've determined the root cause of the BUGs you
> were seeing before, and both the patch you applied and hopefully the
On Wed, 2018-06-13 at 15:52 +0200, Jason A. Donenfeld wrote:
> Hi Paul,
>
> I got an -rt kernel up and running, enabled a bunch of nice debugging
> options, and found a handful of problems, all of which were fixed by:
> https://git.zx2c4.com/WireGuard/commit/?id=0f05452d043d8d047cf5d7987f
> c2732b
On Wed, Jun 13, 2018 at 03:54:24PM +0100, Paul Hedderly wrote:
> On Wed, 2018-06-13 at 15:52 +0200, Jason A. Donenfeld wrote:
> > Hi Paul,
> >
> > I got an -rt kernel up and running, enabled a bunch of nice debugging
> > options, and found a handful of problems, all of which were fixed by:
> > htt
On Wed, 2018-06-13 at 17:08 +0200, Greg KH wrote:
>
> Note, the -rt kernels _always_ run slower than a non-rt kernel. Real
> time is not "faster", it is only "deterministic". And it achieves
> this
> goal at the expense of performance, which is the only way it can be
> done.
Thanks for the remi
On Wed, Jun 13, 2018 at 4:54 PM Paul Hedderly wrote:
> Yea that performance hit is a nuisance
I find that doubtful, for the reasons Greg mentioned.
But in either case, I don't anticipate this will be the final
situation, but rather just a stop gap measure. I think we'll be ready
to revisit this
Hi Jason,
Ive been getting into helping out a little with the android app however when i
run the build on a mac im getting the following.Are you able to point me in the
right direction to fix this?
Thanks
Bens-MacBook-Air:wireguard-android ben$ ./gradlew assembleRelease
Starting a Gradle Daemon,
> ln: illegal option -- r
>
> usage: ln [-Ffhinsv] source_file [target_file]
>
>ln [-Ffhinsv] source_file ... target_dir
>
>link source_file target_file
The makefile uses options from coreutil's ln, which aren't available
on macOS. Use Linux to build the app. If Mac support in the
Thanks for that, ive switched the makefile to use gln and it all works now.
On Wednesday, 13 June 2018, 23:08:30 BST, Jason A. Donenfeld
wrote:
> ln: illegal option -- r
>
> usage: ln [-Ffhinsv] source_file [target_file]
>
> ln [-Ffhinsv] source_file ... target_dir
>
> li
12 matches
Mail list logo
