Ok, I have more info now.
1. Adding `-vv` to the Exec line in fwupd.service and posting the new
log will probably not help. The problem is that fwupd takes 20 minutes
to start.
2. There is something rotten in what fwupd is doing. During the 20
minute startup pause the syslog is replete with the DPCD accesses
failures reported from nouveau. As soon as the 20 minutes are over, so
are the DPCD accesses failures
3. Right now I am trying to run fwupd -vv from console and capture the
output to a file. This is much harder than expected. Simple shell
redirection (sudo /usr/libexec/fwupd/fwupd -vv >somelogfile.log) does
not work while it should ("sudo ls -l >otherfile.log" works). I hate it
when programs invent their own ways how to do console output and/or
logging, complicating catching bugs like this. This might be another
reason why I think adding `-vv` to the Exec line in fwupd.service would
not work. I don't trust fwupd to play nice and send this logging info to
syslog.
4. Rebooting the computer can take up to 20 minutes because the kernel waits
for the wonky and unkillable fwupd process to finish. I have no idea how a
process that takes nonzero CPU time all the time can't die.
Right now I think that while the fwupd process is doing this mystery stuff, the
kernel is even unable to finish shutting down.
--
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:
fwupd daemon hangs for a while during TPM access
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
