Created attachment 124717 [details] Output of dmesg with drm.debug=3 taken AFTER the faulty commit As soon as kernel 4.7-rcX is started, the display is blanked, and it is never turned on again. This problem was bisected to commit f21a21983ef13a031250c4c3f6018e29a549d0f1 ("drm/i915: Splitting intel_dp_detect"). The adapter in question is the integrated graphics controller on a Toshiba Tecra A50 laptop. The output of "lspci -nnv" for that controller is as follows: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0002] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at e0000000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 Disabling i915 with a "nomodeset" on the kernel command line allows the system to boot normally.
Created attachment 124718 [details] Output of dmesg with drm.debug=3 taken before the faulty commit
This bug, which has been present since the 4.7 merge, is still present!!!! As kernel 4.7 will soon be released. what is happening to fix it? Sureley, I cannot be the only i915 user with the problem.
Unfortunately your logs don't have enough useful content. Please try again with drm.debug=0xe
Created attachment 125079 [details] Output of dmesg with drm.debug=0xe taken AFTER the faulty commit
The dmesg output for faulty case is posted. Do you need with drm.debug=0xe for the good case as well?
Created attachment 125081 [details] Output of dmesg with drm.debug=0xe taken before the faulty commit
Created attachment 125085 [details] [review] [PATCH] drm/i915: Treat eDP as always connected, again I think I found the problem. Please test.
Unfortunately, that patch does not help. I am willing to test any other patches. Larry
(In reply to Larry Finger from comment #8) > Unfortunately, that patch does not help. > > I am willing to test any other patches. > > Larry Hmm. That's weird. Can you attach a new log with the patch applied?
Actually, the patch did fix the problem with commit f21a21983ef13a, and you are on the right track; however, there seems to be another bug introduced later. I am in the process of bisecting to find where the second problem happens. At least, I should be able to restrict the amount of material that needs reverting.
I am losing my mind. When I retested mainline, the one-liner posted here does fix my system. Once that is pushed, 4.7 will be OK. I am closing this bug. Sorry for the grief. Thanks for your help. Larry
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.