Created attachment 116746 [details] byt-t_tag19june_i915-init-time-high_dmesg Hardware Platform: Bay Trail T / T100TA CPU: Atom Z3740 CPU core i5 (family 6, model 55, stepping 3) Software Linux distribution: Ubuntu 14.04 64 bits BIOS: T100TA.313 Kernel 4.1-rc8 from git://anongit.freedesktop.org/drm-intel tag drm-intel-testing-2015-06-19 Mesa: mesa-10.5.8 from http://cgit.freedesktop.org/mesa/mesa/ Xf86_video_intel: 2.99.917 from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/ Libdrm: libdrm-2.4.61 from http://cgit.freedesktop.org/mesa/drm/ Cairo: 1.14.2 from http://cgit.freedesktop.org/cairo libva: libva-1.6.0.pre1 from http://cgit.freedesktop.org/libva/ intel-driver: 1.6.0.pre1 from http://cgit.freedesktop.org/vaapi/intel-driver xorg: 1.17.99 installed with script git_xorg.sh Xserver: xorg-server-1.17.2 from http://cgit.freedesktop.org/xorg/xserver Pre-conditions: --------------- Use kernel boot command line: initcall_debug Steps: ------ 1. Power on DUT 2. Execute command: dmesg |grep i915_init Actual result: -------------- 2. Init time is between 1,5 and 1,6 seconds Expected result: ---------------- 2. Value is not so high (we use criteria 50 ms)
Please always ensure your dmesg starts from the very beginning. If necessary, add log_buf_len=4M or similar (although in this case the size doesn't seem to be the limit).
(In reply to cprigent from comment #0) > Actual result: > -------------- > 2. Init time is between 1,5 and 1,6 seconds That's bad. > Expected result: > ---------------- > 2. Value is not so high (we use criteria 50 ms) That's impossible. Not much has happened in this front in ages. I'm closing this one. We should look at this again when we have some sensible targets, but dragging on with this bug is not going to change that one way or another, unfortunately.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.