** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1861284
Title:
Build and ship a signed wireguard.ko
Status in linux package in Ubuntu:
Fix Rel
All set now!
zx2c4@thinkpad ~ $ curl -s
http://archive.ubuntu.com/ubuntu/dists/focal-updates/main/binary-amd64/Packages.xz
| unxz | grep -B11 Provides:.*wireguard | grep ^Package:
Package: linux-image-aws
Package: linux-image-azure
Package: linux-image-gcp
Package: linux-image-generic
Package: l
Looks like it's still in -proposed, not -updates:
zx2c4@thinkpad ~ $ curl -s
http://archive.ubuntu.com/ubuntu/dists/focal-proposed/main/binary-amd64/Packages.xz
| unxz | grep -B11 Provides:.*wireguard | grep ^Package:
Package: linux-image-aws
Package: linux-image-azure
Package: linux-image-gcp
P
Reopening this until we have some conclusion on (2) and (3) of #9.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873288
Title:
wireguard-tools should NOT recommend wireguard-dkms
Ah, looks like I can't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873288
Title:
wireguard-tools should NOT recommend wireguard-dkms
Status in linux-meta package in Ubuntu:
Simon - to keep you updated on the bug you reported, this fixes issue
(1), as described in comment #9: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux-
meta/+git/focal/commit/?id=204fb3b2ae6b0c8c41c339f47949b45d571c4953
We'll keep this open until there's a decision/fix on (2) and (3
The Ubuntu kernel team seems to be behind in deploying a fix for this.
In the interim you can solve this by using the WireGuard project's PPA,
which now has backports for 19.10. Run this command to fix your issue:
sudo add-apt-repository ppa:wireguard/wireguard && sudo apt-get update
&& sudo apt-g
Seems dkms related.
** Package changed: wireguard (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851295
Title:
dkms error with wireguard on upgrafe to 19.10
[ 15.589541] module: x86/modules: Skipping invalid relocation target,
existing value is nonzero for type 1, loc f4677a21, val
c1171b82
Looks like a dkms issue? Thankfully we won't need that for 20.04 and
also earlier kernels once things are backported. I'll reassign this to
the c
Doesn't look like a WireGuard bug.
** Package changed: wireguard (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854225
Title:
Kernel oops and system lock up
The kernel team can backport things need be.
** Package changed: wireguard (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858807
Title:
Wireguard install fai
** Summary changed:
- wireguard crashes system shortly after wg-quick down wg0
+ eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is set
on suppress rule"
** Package changed: wireguard (Ubuntu) => linux-meta (Ubuntu)
--
You received this bug notification because you are a
It's possible this same issue is responsible for this crash in
WireGuard:
https://lists.zx2c4.com/pipermail/wireguard/2019-September/004495.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
I'm having this issue on kernel 4.11.1.
[48112.422418] [ cut here ]
[48112.422441] WARNING: CPU: 0 PID: 14420 at drivers/usb/host/xhci-ring.c:1390
handle_cmd_completion+0xb17/0xc00 [xhci_hcd]
[48112.422446] Modules linked in: xt_hashlimit ip6_udp_tunnel udp_tunnel rfcomm
Hey Jay,
I found this same issue here --
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685416 -- when
debugging WireGuard issues on GCE. I'm curious how you found it and what
your debugging was like. Do you work for Google and could debug their
virtio implementation? I spent a really long
Hi Stefan -- thanks for taking ownership of this bug. Could you give a
rough timeline on when you expect to roll out the next kernel update
that contains these commits?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
No such log is necessary. You simply forgot to backport two critical
patches.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Description changed:
The HWE kernel, and possibly others too, backport some virtio
improvements related to setting VIRTIO_NET_HDR_F_DATA_VALID on received
packets so that the CPU doesn't have to checksum packets that have
already been verified by hardware. In the initial implementation
Public bug reported:
The HWE kernel, and possibly others too, backport some virtio
improvements related to setting VIRTIO_NET_HDR_F_DATA_VALID on received
packets so that the CPU doesn't have to checksum packets that have
already been verified by hardware. In the initial implementation of
this, th
20 matches
Mail list logo
