All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Michal Suchánek" <msuchanek@suse.de>, dtsen@linux.ibm.com
Cc: netdev@vger.kernel.org, "Jason A. Donenfeld" <Jason@zx2c4.com>,
	linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com
Subject: Re: Cannot load wireguard module
Date: Mon, 18 Mar 2024 22:50:49 +1100	[thread overview]
Message-ID: <87r0g7zrl2.fsf@mail.lhotse> (raw)
In-Reply-To: <87jzm32h7q.fsf@mail.lhotse>

Michael Ellerman <mpe@ellerman.id.au> writes:
> Michal Suchánek <msuchanek@suse.de> writes:
>> Hello,
>>
>> I cannot load the wireguard module.
>>
>> Loading the module provides no diagnostic other than 'No such device'.
>>
>> Please provide maningful diagnostics for loading software-only driver,
>> clearly there is no particular device needed.
>
> Presumably it's just bubbling up an -ENODEV from somewhere.
>
> Can you get a trace of it?
>
> Something like:
>
>   # trace-cmd record -p function_graph -F modprobe wireguard
>
> That should probably show where it's bailing out.
>
>> jostaberry-1:~ # uname -a
>> Linux jostaberry-1 6.8.0-lp155.8.g7e0e887-default #1 SMP Wed Mar 13 09:02:21 UTC 2024 (7e0e887) ppc64le ppc64le ppc64le GNU/Linux
>> jostaberry-1:~ # modprobe wireguard
>> modprobe: ERROR: could not insert 'wireguard': No such device
>> jostaberry-1:~ # modprobe -v wireguard
>> insmod /lib/modules/6.8.0-lp155.8.g7e0e887-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst 
>> modprobe: ERROR: could not insert 'wireguard': No such device
>  
> What machine is this? A Power10?

I am able to load the module successfully on a P10 running v6.8.0.

I tried running the demo (client-quick.sh) to check it actually works,
but that hangs sending the public key, I suspect because my development
machine is behind multiple firewalls.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Michal Suchánek" <msuchanek@suse.de>, dtsen@linux.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, wireguard@lists.zx2c4.com,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	netdev@vger.kernel.org
Subject: Re: Cannot load wireguard module
Date: Mon, 18 Mar 2024 22:50:49 +1100	[thread overview]
Message-ID: <87r0g7zrl2.fsf@mail.lhotse> (raw)
In-Reply-To: <87jzm32h7q.fsf@mail.lhotse>

Michael Ellerman <mpe@ellerman.id.au> writes:
> Michal Suchánek <msuchanek@suse.de> writes:
>> Hello,
>>
>> I cannot load the wireguard module.
>>
>> Loading the module provides no diagnostic other than 'No such device'.
>>
>> Please provide maningful diagnostics for loading software-only driver,
>> clearly there is no particular device needed.
>
> Presumably it's just bubbling up an -ENODEV from somewhere.
>
> Can you get a trace of it?
>
> Something like:
>
>   # trace-cmd record -p function_graph -F modprobe wireguard
>
> That should probably show where it's bailing out.
>
>> jostaberry-1:~ # uname -a
>> Linux jostaberry-1 6.8.0-lp155.8.g7e0e887-default #1 SMP Wed Mar 13 09:02:21 UTC 2024 (7e0e887) ppc64le ppc64le ppc64le GNU/Linux
>> jostaberry-1:~ # modprobe wireguard
>> modprobe: ERROR: could not insert 'wireguard': No such device
>> jostaberry-1:~ # modprobe -v wireguard
>> insmod /lib/modules/6.8.0-lp155.8.g7e0e887-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst 
>> modprobe: ERROR: could not insert 'wireguard': No such device
>  
> What machine is this? A Power10?

I am able to load the module successfully on a P10 running v6.8.0.

I tried running the demo (client-quick.sh) to check it actually works,
but that hangs sending the public key, I suspect because my development
machine is behind multiple firewalls.

cheers

  reply	other threads:[~2024-03-18 11:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 12:20 Cannot load wireguard module Michal Suchánek
2024-03-15 12:37 ` Christophe Leroy
2024-03-15 13:05   ` Michal Suchánek
2024-03-15 13:05     ` Michal Suchánek
2024-03-15 23:44 ` Michael Ellerman
2024-03-15 23:44   ` Michael Ellerman
2024-03-18 11:50   ` Michael Ellerman [this message]
2024-03-18 11:50     ` Michael Ellerman
2024-03-18 17:08     ` Michal Suchánek
2024-03-18 17:08       ` Michal Suchánek
2024-03-19 12:47       ` Michal Suchánek
2024-03-19 12:47         ` Michal Suchánek
2024-03-20 12:41         ` Michael Ellerman
2024-03-20 12:41           ` Michael Ellerman
2024-03-20 16:04           ` Michal Suchánek
2024-03-20 16:04             ` Michal Suchánek
2024-03-21 12:47             ` Michael Ellerman
2024-03-21 12:47               ` Michael Ellerman
2024-03-22 11:33           ` Herbert Xu
2024-03-22 11:33             ` Herbert Xu
2024-03-23  0:18             ` Michael Ellerman
2024-03-23  0:18               ` Michael Ellerman

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=87r0g7zrl2.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=Jason@zx2c4.com \
    --cc=dtsen@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    --cc=netdev@vger.kernel.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 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.