Note that this bug is quite old now, and I upgraded this machine to
20.04 last night. I have no idea if the information collected by apport
has any relevance any more.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
apport information
** Tags added: apport-collected focal
** Description changed:
On 2 occasions over the past week I have had full system crashes after
running "wg-quick up wg0". On the terminal, the command does not
complete (i.e. it does not return to the prompt), the fans on my laptop
Doesn't look like a WireGuard bug.
** Package changed: wireguard (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854225
Title:
Kernel oops and system lock up when invoking
Thanks for the bug report. That kern.log is useful. The relevant part is
reproduced below in this comment. Looks like wg-quick(8) invokes
sysctl(8), which then uses /proc/sys/, and somehow invokes a null
pointer dereference while holding a spinlock, leading to that lock being
hit by other cores, ev
Hi Neil - I think that's a good idea since we haven't seen any progress
on this private bug report. I'm not sure of the cause here but I think
that we would have received a lot more reports if this was a widespread
issue when using wg-quick (as we have in the past).
** Information type changed fro
