| Summary: | The booting is too long with drm_atomic_helper_wait_for_dependencies errors (xenial+hwe,bionic)) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Dima <mihailov-d-v> | ||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | intel-gfx-bugs, kai.heng.feng, mihailov-d-v, ville.syrjala | ||||||||
| Version: | unspecified | ||||||||||
| Hardware: | x86 (IA32) | ||||||||||
| OS: | Linux (All) | ||||||||||
| URL: | https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326 | ||||||||||
| Whiteboard: | Triaged | ||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Dima
2018-11-14 22:41:06 UTC
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785326 Dmesg attached here from Linux version 4.15.0-20-generic, can you try to verify this issue with latest drm-tip? https://cgit.freedesktop.org/drm-tip If the problem persists (with drm-tip) attach the full dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M? Created attachment 142524 [details]
dmesg 4.20 RC2
Ville, any comments here? May I use this link for drm-tip? http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ I tried linux-image-4.20.0-994-lowlatency_4.20.0-994.201811182101_i386 from the link above, but I can't boot it by the normal way. And I don't know how to save dmesg while the system does not respond. But I tried to boot in recovery mode and have got two dmesgs without X and with nomodeset on (and/or something else by recovery mode menu -> resume). I guess it's not useful, but it's all I've got. If it's distro version related I can install any of them on my old hdd. And I don't know how to use https://cgit.freedesktop.org/drm-tip/. Should I merge it with the latest kernel sources and then compile? How to merge it? Created attachment 142525 [details]
dmesg Ubuntu drm-tip 4.20.0-994.201811182101 (recovery mode -> resume (nomodeset(?))
Dima, Can you please set kernel parameters drm.debug=0x1e log_buf_len=4M and reproduce this issue and attach the log? Current logs are without debug parameters. The dmesg didn't have the debugs enabled so can't see much. The one important detail I see is [ 15.130664] ? wait_woken+0x70/0x70 [ 15.130746] intel_get_load_detect_pipe+0x335/0x380 [i915] [ 15.130801] intel_tv_detect+0x10b/0x480 [i915] so this is a duplicate. *** This bug has been marked as a duplicate of bug 93782 *** Created attachment 142581 [details]
dmesg 4.15 ubuntu 16.04.5 hwe drm.debug=0x1e
I wasn't able to boot 4.20rc2, 4.20rc3 and drm-tip current. I don't know why. I was able to boot 4.20rc2 a day before and now I can't. It looks like it is the same case as was on linux-image-4.20.0-994-lowlatency_4.20.0-994.201811182101_i386.
So I've made the dmesg with drm.debug=0x1e log_buf_len=4M for default Ubuntu Xenial hwe kernel (4.15). I hope it can be helpful.
(In reply to Ville Syrjala from comment #8) I've attached dmesg with drm.debug recently. Could you please check it to be sure it's a duplicate? (In reply to Dima from comment #10) > (In reply to Ville Syrjala from comment #8) > > I've attached dmesg with drm.debug recently. Could you please check it to be > sure it's a duplicate? i965gm+tv -> it's a duplicate Booting with video=SVIDEO-1:d helps. So indeed it's a duplicate. Finally I can update to 18.04. A profound bow to you all. Thank you. |
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.