Ok, so now I changed the systemd config to give it 30 minutes to start and while I was at it I added "-vv" to the Exec line (it is in the same file) just out of curiosity whether it would work despite my scepticism. It does so here is the log. And now it makes me think that tpm isn't going to be the culprit. Namely the story it tells is a bit different: it finds PCI_SLOT_NAME=0000:36:00.0:drm_dp_aux2, probes it, assigns something like GUID to it and then BAM, the DPCD kernel crashes start to flow. I included only three of them here. Need to wait about 10 more minutes to see what happens when it gets unstuck. Meanwhile you can have a look at the beginning of this mess.
** Attachment added: "ffupd making mess in my system" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2098668/+attachment/5858314/+files/fwupd-mess.log -- 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
