Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Роман Гаврилов" <kogeler@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: new bug on armhf
Date: Mon, 20 Nov 2017 22:34:09 +0300	[thread overview]
Message-ID: <CALpTdxnL6akts71rb4yg+wisxqqs0U2wXPE5c12J9yMHVL6wGw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2420 bytes --]

Hello!

I have new bug on armhf.

____________________________________________________________

build from:
https://git.zx2c4.com/WireGuard/commit/?id=82cacee3511e5c2f624203487124e5ba0151c84d

____________________________________________________________

software:
Ubuntu Xenial 16.04

hardware:
PC: Orange Pi Plus 2E
SOC: Allwinner H3

____________________________________________________________
cat /proc/cpuinfo
processor    : 0
model name    : ARMv7 Processor rev 5 (v7l)
BogoMIPS    : 11.42
Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
vfpd32 lpae evtstrm
CPU implementer    : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part    : 0xc07
CPU revision    : 5

processor    : 1
model name    : ARMv7 Processor rev 5 (v7l)
BogoMIPS    : 11.42
Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
vfpd32 lpae evtstrm
CPU implementer    : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part    : 0xc07
CPU revision    : 5

processor    : 2
model name    : ARMv7 Processor rev 5 (v7l)
BogoMIPS    : 11.42
Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
vfpd32 lpae evtstrm
CPU implementer    : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part    : 0xc07
CPU revision    : 5

processor    : 3
model name    : ARMv7 Processor rev 5 (v7l)
BogoMIPS    : 11.42
Features    : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
vfpd32 lpae evtstrm
CPU implementer    : 0x41
CPU architecture: 7
CPU variant    : 0x0
CPU part    : 0xc07
CPU revision    : 5

Hardware    : Allwinner sun8i Family
Revision    : 0000
Serial        : 02c0008149ab5a29

____________________________________________________________

uname -a
Linux LAB-HOME-SERVER 4.13.14-sunxi #240 SMP Mon Nov 20 00:09:06 CET 2017
armv7l armv7l armv7l GNU/Linux

____________________________________________________________

I use mainline kernel.

Kernel config:
https://drive.google.com/open?id=1H6Vk7P8bCNAktBhmfJpTtGse2rRauRiB

____________________________________________________________

sudo modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Exec format error

____________________________________________________________

dmesg | grep wiregu
[  532.927236] wireguard: loading out-of-tree module taints kernel.
[  532.930604] wireguard: unknown relocation: 51
[  533.005892] wireguard: unknown relocation: 51

-- 
Thanks,
Roman Gavrilov

[-- Attachment #2: Type: text/html, Size: 3617 bytes --]

             reply	other threads:[~2017-11-20 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 19:34 Роман Гаврилов [this message]
2017-11-21  9:34 ` Ivan Labáth
2017-11-21 10:05   ` Jason A. Donenfeld
2017-11-21 10:04 ` Jason A. Donenfeld
2017-11-21 15:10   ` Jason A. Donenfeld
2017-11-21 16:39     ` Роман Гаврилов
2017-11-21 17:32       ` 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=CALpTdxnL6akts71rb4yg+wisxqqs0U2wXPE5c12J9yMHVL6wGw@mail.gmail.com \
    --to=kogeler@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).