Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-10-30 Thread Toralf Förster
On 10/29/2015 10:49 PM, Pavel Machek wrote: > On Sun 2015-10-04 18:30:14, Toralf Förster wrote: >> On 08/04/2015 02:29 PM, Toralf Förster wrote: >>> On 08/02/2015 09:43 AM, Pavel Machek wrote: Any chance to bisect it? >>> Did it. >>> >>> FWIW: the mentioned commit was introduced between 3.18

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-10-29 Thread Pavel Machek
On Sun 2015-10-04 18:30:14, Toralf Förster wrote: > On 08/04/2015 02:29 PM, Toralf Förster wrote: > > On 08/02/2015 09:43 AM, Pavel Machek wrote: > >> Any chance to bisect it? > > Did it. > > > > FWIW: the mentioned commit was introduced between 3.18 and 3.19. > > But my system (hardened 64 bit

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-10-04 Thread Toralf Förster
On 08/04/2015 02:29 PM, Toralf Förster wrote: > On 08/02/2015 09:43 AM, Pavel Machek wrote: >> Any chance to bisect it? > Did it. > > FWIW: the mentioned commit was introduced between 3.18 and 3.19. > But my system (hardened 64 bit Gentoo) did not suffer from it till version > 4.0.8. > The

Re: [Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-15 Thread Toralf Förster
On 08/04/2015 02:29 PM, Toralf Förster wrote: On 08/02/2015 09:43 AM, Pavel Machek wrote: Any chance to bisect it? Did it. FWIW: the mentioned commit was introduced between 3.18 and 3.19. But my system (hardened 64 bit Gentoo) did not suffer from it till version 4.0.8. The hardened

Re: [Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-04 Thread Toralf Förster
On 08/02/2015 09:43 AM, Pavel Machek wrote: Any chance to bisect it? Did it. FWIW: the mentioned commit was introduced between 3.18 and 3.19. But my system (hardened 64 bit Gentoo) did not suffer from it till version 4.0.8. The hardened kernel 4.1.x was the first where the bug was visible at my

Re: [Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-03 Thread Toralf Förster
On 08/02/2015 09:43 AM, Pavel Machek wrote: On Wed 2015-07-29 15:54:00, Toralf Förster wrote: Undocking helps, and then I can dock again. This happens at a hardened 64 bit Gentoo with i915, but I think, it is not hardened related, or ? Any chance to bisect it? Aren't there are already

Re: [Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-03 Thread Toralf Förster
On 08/03/2015 11:53 AM, Toralf Förster wrote: A quick look at the latest 4.1.3+hardened just shows that the power button at the docking station does not produce an ACPI event. This is fixed between 4.1.3 and 4.1.4 - would be helpful to know the commit id for the following bisecting of the

Re: [Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-02 Thread Pavel Machek
On Wed 2015-07-29 15:54:00, Toralf Förster wrote: Undocking helps, and then I can dock again. This happens at a hardened 64 bit Gentoo with i915, but I think, it is not hardened related, or ? Any chance to bisect it? -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures)

[Intel-gfx] 4.0.8-4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-07-29 Thread Toralf Förster
Undocking helps, and then I can dock again. This happens at a hardened 64 bit Gentoo with i915, but I think, it is not hardened related, or ? -- Toralf, pgp key: 872AE508 0076E94E ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org