If the workaround appears to not work, try this quite elaborate process to try and find out why.
First enter these two commands: "sudo snap stop firmware-updater.firmware-notifier" "sudo service fwupd-refresh stop" These stop everything that tries to access the broken fwupd service. Now wait until the stream of kernel oopses stops (watch in /var/log/syslog) and a bit more. What you want is to verify the oopses are really gone and also to have a few non-error messages to "delimit" the attempt you are going to make from the endless stream of oopses you got. Once the oopses are gone, note the time. Then update fwupd.service to give the service "TimeoutSec=1800" and also give it "-vv" in ExecStart. Then enter this: "sudo systemctl daemon-reload" "sudo service fwupd start" The second command will take a LONG time to complete due to this bug. In my case it is 20 minutes. Your case may vary. But it should stop after 30 mimutes, possibly with a timeout error. Once the command completed, go to /var/log/syslog and verify that the oopses stopped. If they did not, wait for them to stop. Once they do, note the time. The difference between the "sudo service fwupd start" time and the time when the oopses stopped is the time you need to put into TimeoutSec of fwupd.service. Add 5-10 minutes for good measure. At this point you may remove the "-vv" from ExecStart but I suggest to keep it in and watch the logs for trouble caused by this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098668 Title: nouveau crashes when fwupd requests DPCD reads on drm_dp_auxN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2098668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
