Hi Josh, On 22.01.2014 17:50, Josh Triplett wrote:
Odd. Please report a bug in the fd.o bugzilla on the i915 driver.
This seems to be already reported [1], as i915.disable_power_well=0 stops the errors (but there is still mode change).
I tried: sudo journalctl -F BOOTCHART This gave no output.I don't know what isn't working there; you might try the systemd IRC channel or mailing list, to see if they know what's going on.
I just tried running it in a terminal and got: $ sudo /lib/systemd/systemd-bootchart open /proc/schedstat: No such file or directory Any idea why this is missing?
Because you'll never be consistent enough typing in your passphrase to allow accurate comparisons of boot time. You mentioned wanting to compare the whole boot time with and without plymouth; there's really no hope of doing that when the boot process depends on user interaction.
I first tried to compare the time used for userspace setup and already there was very much noise.
(Also, if you're using encryption, you're probably also using LVM, which causes major boot-time slowdowns on all distributions, and is outright broken on Debian systems. If udevadm settle is running at all in your boot path, that needs fixing.)Luckily I have no problems with LVM and systemd. (lvm2.service takes 548ms) At least the systemd-udev-settle.service is not called during boot.See the ongoing discussions about LVM and systemd in the bug on LVM (which has gotten wrapped up into the whole init system debacle). LVM currently isn't coping with dynamic hardware correctly. And 548ms is ridiculous.
You mean bug #728486? It seems this might get resolved shortly after the infamous #727708.
Best regards, Andreas 1: https://bugs.freedesktop.org/show_bug.cgi?id=67813