From: Christian Hewitt <christianshewitt@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: "bus error" when generating public key
Date: Fri, 7 Dec 2018 15:46:53 +0400 [thread overview]
Message-ID: <2DE53C12-A1B1-4E06-9391-7F64BC7328A2@gmail.com> (raw)
I’m working to add WireGuard support to an embedded distro that runs on a mix of x86 and ARM hardware. I’m using 4.19.7 as the kernel base, cross compiling using a well proven toolchain and build-system. The kernel defconfig can be seen here:
https://github.com/chewitt/LibreELEC.tv/blob/amlogic/projects/Amlogic/linux/linux.aarch64.conf
I see no compile errors when building the kernel module or wireguard tools. The kernel module loads without errors and ‘wg’ can generate private and preshared keys, but when creating a public key from the private key ‘wg pubkey < /path/to/privatekey' fails with “Bus error” and no key is generated.
dmesg from the device after the failure: http://ix.io/1vrb
modinfo wireguard
filename: /lib/modules/4.19.7/kernel/net/wireguard/wireguard.ko
alias: net-pf-16-proto-16-family-wireguard
alias: rtnl-link-wireguard
version: 0.0.20181119
author: Jason A. Donenfeld <Jason@zx2c4.com>
description: WireGuard secure network tunnel
license: GPL v2
srcversion: 1CFE12F8E5CF00DB842FD50
depends: ipv6,udp_tunnel,ip6_udp_tunnel
intree: Y
name: wireguard
vermagic: 4.19.7 SMP preempt mod_unload aarch64
ldd /usr/bin/wg
libc.so.6 => /usr/lib/libc.so.6 (0xf7771000)
/lib/ld-linux-armhf.so.3 => /usr/lib/ld-linux-armhf.so.3 (0xf78ad000)
I’m not a coding developer, but I’m able to follow instructions to a reasonable level if there is some kind of debugging or additional output that would be useful.
Can you spot the problem? Any suggestions?
Christian
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-12-07 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 11:46 Christian Hewitt [this message]
2018-12-10 7:25 ` Ole-Morten Duesund
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=2DE53C12-A1B1-4E06-9391-7F64BC7328A2@gmail.com \
--to=christianshewitt@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 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).