[ 14.278] (II) config/udev: Adding drm device (/dev/dri/card0) [ 14.716] drm device access denied [ 15.140] drm device access denied [ 15.568] drm device access denied [ 15.992] drm device access denied [ 16.415] drm device access denied [ 16.844] drm device access denied [ 17.268] drm device access denied [ 17.691] drm device access denied [ 18.115] drm device access denied [ 18.538] drm device access denied [ 18.538] setversion 1.4 failed
Gratifying to see the patch's behavior "in the wild". :-) Anyway, you can see there that the patch introduced a 4-second delay. There's also another similar delay later in the Xorg.0.log: [ 19.031] (II) config/udev: Adding drm device (/dev/dri/card0) [ 19.455] drm device access denied [ 19.880] drm device access denied [ 20.305] drm device access denied [ 20.729] drm device access denied [ 21.157] drm device access denied [ 21.582] drm device access denied [ 22.008] drm device access denied [ 22.432] drm device access denied [ 22.857] drm device access denied [ 23.282] drm device access denied [ 23.282] setversion 1.4 failed So, between the two invocations of the patched behavior that accounts for ~8-9 sec of your 10 sec delay. The good news is we can dial that up or down however we want, the bad news is it looks like doing so wouldn't substantially affect the behavior... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
