OK, this (or at least some part of it) finally reproduced on an upstream
kernel (5.4.19-050419-generic)! I've attached the journal from "[ cut
here ]" onwards, with some minor redaction of VPN endpoints.
** Attachment added: "5.4.19-050419-generic.journal.txt"
https://bugs.launchpad.net/ubunt
I've been using the mainline kernel (5.4.5, specifically) for a few
weeks with no instability; I switched back to the -proposed kernel ~a
week ago and I've since seen this issue recur. The version I saw this
recur on was 5.4.0-13-generic (and I'm now on -14 as a result of the
forced reboot).
Is t
Yes that's right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854789
Title:
Hard lockup using 5.3.0.24.28 from proposed PPA on focal
To manage notifications about this bug go to:
https://bugs.la
Thanks for looking at the bug! Which mainline kernel should I look to
use? Is https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.1/ the
right one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18547
RCU bug? I guess the best approach is to reproduce it on mainline kernel
and raise the issue to RCU mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854789
Title:
Hard lockup using 5.3.0
** Package changed: linux-meta (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/1854789
Title:
Hard lockup using 5.3.0.24.28 from proposed PPA on focal
To manage notificatio
