Bug 92144

Summary:	intel output broken in f0fd4d500de03c30c7ce19915f85acadd1ca4e5d
Product:	DRI	Reporter:	Tobias Jakobi <liquid.acid>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	critical
Priority:	medium	CC:	intel-gfx-bugs
Version:	XOrg git
Hardware:	x86-64 (AMD64)
OS:	All
Whiteboard:
i915 platform:	HSW	i915 features:	display/eDP

Description Tobias Jakobi 2015-09-27 17:29:08 UTC

xf86-video-intel commit f0fd4d500de03c30c7ce19915f85acadd1ca4e5d: internal eDP1 output broken, display switched off shortly after xorg-server start, need sysrq to kill server

good commit e179e7d3a436631c434b26fafb0304e777a6b24b (hints to issue with hotplug/coldplug rewrite)

uname -a:
Linux leena 4.2.1 #1 SMP Fri Sep 25 23:48:32 CEST 2015 x86_64 Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz GenuineIntel GNU/Linux

xorg-server git tip (dca5770af9e20bb1148374ebfd60931a81b148a2)
libdrm git tip (f3c6740f0c27d98d16340396f1a15e10384f9284)

no errors in xorg, syslog nor kernel log

- Tobias

Comment 1 Chris Wilson 2015-09-27 18:16:19 UTC

At least attach the Xorg.0.log from the last good commit - and bisecting would be very useful.

Comment 2 Chris Wilson 2015-10-02 14:02:22 UTC

Ping for the Xorg.0.log.

Comment 3 Ricardo 2017-02-21 15:45:27 UTC

Request for logs has been requested more than a year ago with no response. We will wait for response from liquid.acid@gmx.net for 30 days or the bug will be closed

Comment 4 Jani Nikula 2017-02-22 09:41:21 UTC

(In reply to Ricardo from comment #3)
> Request for logs has been requested more than a year ago with no response.
> We will wait for response from liquid.acid@gmx.net for 30 days or the bug
> will be closed

IME when there's been repeated requests and enough time has passed, just closing the bug will provoke a response better than new pings, if there's ever going to be a response at all. And then we don't need to worry about closing the bugs later.

Closing, please reopen and provide logs if the problem still persists with latest components.

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.