| Summary: | [SNB] drm-intel-nightly takes long time to start | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | maria guadalupe <maria.g.perez.ibarra> | ||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | intel-gfx-bugs, ricardo.vega | ||||||
| Version: | unspecified | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | SNB | i915 features: | display/Other | ||||||
| Attachments: |
|
||||||||
also with this kernels from nightly tag takes a long time commit d77e2944fe6d31080bc1a8b6d97449ebb2824459 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Oct 13 21:59:29 2016 +0100 drm-intel-nightly: 2016y-10m-13d-20h-59m-11s UTC integration manifest commit dbcf6fbb541e70fac7db669631958eab2e4e0d9c Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu Oct 13 17:31:36 2016 +0200 drm-intel-nightly: 2016y-10m-13d-15h-31m-19s UTC integration manifest Doesn't appear to be a gfx issue. Please attach Xorg.0.log as well for interest. Created attachment 127641 [details]
Xorg.0.log
The windowing system is up and running in under 3s. It's what happens afterwards that would appear to be of interest - at any rate it appears the GPU and outputs are ready much earlier. this issue has impacted the IGT execution because it really slows the process after a S3/s4 reboot (In reply to ricardo.vega from comment #5) > this issue has impacted the IGT execution because it really slows the > process after a S3/s4 reboot Logs or it never happened... (In reply to Chris Wilson from comment #6) > (In reply to ricardo.vega from comment #5) > > this issue has impacted the IGT execution because it really slows the > > process after a S3/s4 reboot > > Logs or it never happened... Hi Chris, could you please add information about which log is needed besides dmesg & Xorg.log in order to add it? A bootchart really. We've already established there is nothing unusual or suffering long delays in dmesg/Xorg.0.log. So the question is what is taking so long for the system to become usable for you. closing bug due to it is a hardware issue. |
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.
Created attachment 127311 [details] dmesg.log Bug description ============================================= in SNB with drm-intel-nightly takes a long time to boot into user interface, please see the following example kernel time to boot into X ================================================================== 4.8.0-drm-intel-nightly-ww42-commit-fc23e80+ 4min 4.4.0-38-generic 4 min 4.4.0-21-generic 6min Software information ============================================ Kernel version : 4.8.0-drm-intel-nightly-ww42-commit-fc23e80+ Linux distribution : Ubuntu 16.04.1 LTS Architecture : 64-bit xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.3 DRM version : 2.4.71 Cairo version : 1.15.2 Intel GPU Tools version : Tag [intel-gpu-tools-1.16-59-g48a9e1e] / Commit [48a9e1e] Kernel driver in use : i915 Bios revision : 4.6 KSC revision : Not found <-- maybe the DUT doesn't has this firmware Hardware information ============================================ Platform : SNB Motherboard model : OptiPlex 990 Motherboard type : 06D7TR Mini Tower Motherboard manufacturer : Dell Inc. CPU family : Core i7 CPU information : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GPU Card : Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Memory ram : 8 GB Maximum memory ram allowed : 32 GB CPU thread : 8 CPU core : 4 Signature : Type 0, Family 6, Model 42, Stepping 7 Hard drive capacity : 1863GiB (2TB) Kernel parameters ============================================ quiet drm.debug=14 resume=/dev/sda3 Notes : =================================== Maybe is expected that in this platform drm-intel-nightly takes long time to start X or maybe no, plese confirm it Attachments: ===================================== dmesg.log