This is definitely a kernel bug, but it's exaggerated by userspace.
So whether it should be worked around in userspace or fixed in the kernel space is debatable.
For now, I believe you can employ that workaround to keep your system stable, but I would ask the following.
1) Can you please follow the things that the bot said to add your logs to the bug.
2) Can you please try latest mainline (5.1rc7: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc7/) and confirm it doesn't help? I don't expect it to.
3) If the fwupd workaround does end up being backported to Disco, please test it for the purposes of the SRU, you would see notification in this bug.
This is definitely a kernel bug, but it's exaggerated by userspace.
So whether it should be worked around in userspace or fixed in the kernel space is debatable.
For now, I believe you can employ that workaround to keep your system stable, but I would ask the following.
1) Can you please follow the things that the bot said to add your logs to the bug. /kernel. ubuntu. com/~kernel- ppa/mainline/ v5.1-rc7/) and confirm it doesn't help? I don't expect it to.
2) Can you please try latest mainline (5.1rc7: https:/
3) If the fwupd workaround does end up being backported to Disco, please test it for the purposes of the SRU, you would see notification in this bug.