** Description changed:
- Rather than calling drm directly, gpu-manager should simply check the
- outputs connector status by using the sysfs filesystem (e.g.
- /sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that
- is already available.
+ SRU request:
+
+ [Impact]
+ The current drm code to probe the connected outputs is too resource
intensive, and slow down the boot process.
+
+ [Test Case]
+ 1) Boot Ubuntu and run the following command, looking for gpu-manager:
+ systemd-analize blame
+
+ This will show how long gpu-manager took. Write down the number
+
+ 2) Install the package from -proposed, and run systemd-analize blame.
+ See if the number has become smaller.
+
+ [Regression Potential]
+ Low, all the changes are already included in Yakkety.
+
+
+ _____________________
+ Rather than calling drm directly, gpu-manager should simply check the outputs
connector status by using the sysfs filesystem (e.g.
/sys/class/drm/card0-HDMI-A-1/status, etc.), thus relying on data that is
already available.
This should make gpu-manager a bit less resource intensive, especially
on boot.
The attached perf shows the problem in gpu-manager.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586933
Title:
gpu-manager's drm output detection affects boot time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1586933/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
