From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751282AbbEGNgF (ORCPT ); Thu, 7 May 2015 09:36:05 -0400 Received: from mx02.posteo.de ([89.146.194.165]:53669 "EHLO mx02.posteo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750726AbbEGNgC (ORCPT ); Thu, 7 May 2015 09:36:02 -0400 Message-ID: <554B6A1B.9050201@posteo.de> Date: Thu, 07 May 2015 15:35:23 +0200 From: Martin Kepplinger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Jani Nikula , daniel.vetter@intel.com, airlied@linux.ie CC: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, "linux-kernel@vger.kernel.org" Subject: Re: [BUG] i915: suspend by closing Laptop lid broken References: <55474FD2.7070600@posteo.de> <87a8xk8u20.fsf@intel.com> In-Reply-To: <87a8xk8u20.fsf@intel.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2015-05-04 um 13:24 schrieb Jani Nikula: > On Mon, 04 May 2015, Martin Kepplinger wrote: >> So. -rc1 broke suspending by closing my laptop lid and it's not fixed in >> -rc2. It works exactly *one* first time and every subsequent lid-closing >> is ignored. >> >> Biscted and tested first bad commit: >> 14aa02449064541217836b9f3d3295e241d5ae9c >> >> This pulls in i915 changes as well as ACPI changes. I don't know the >> driver but I'm sure you can find the mistake. I'm happy to test changes. >> >> There are no log differences. > > Any chance you could bisect into the merge? It would be helpful. > > BR, > Jani. > > My attempt to go into the merge was too much effort as the checkouts in between break random other stuff. We should be between 09d51602cf84a1264946711dd4ea0dddbac599a1 (good) and c0f404284192f2d4a0159a714372a8c8610c1f6d. Could you have a look and maybe you have guesses for me, what I should test? It's not sooo much anymore, maybe you even have a guess about the bug? thanks martin