From: "Bjørn Mork" <bjorn@mork.no>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: gen4: work around hang during hibernation
Date: Mon, 02 Mar 2015 14:00:58 +0100 [thread overview]
Message-ID: <87sidn8sfp.fsf@nemi.mork.no> (raw)
In-Reply-To: <87385n60re.fsf@intel.com> (Jani Nikula's message of "Mon, 02 Mar 2015 14:29:25 +0200")
Jani Nikula <jani.nikula@intel.com> writes:
> On Mon, 02 Mar 2015, Imre Deak <imre.deak@intel.com> wrote:
>> Bjørn reported that his machine hang during hibernation and eventually
>> bisected the problem to the following commit:
>>
>> commit da2bc1b9db3351addd293e5b82757efe1f77ed1d
>> Author: Imre Deak <imre.deak@intel.com>
>> Date: Thu Oct 23 19:23:26 2014 +0300
>>
>> drm/i915: add poweroff_late handler
>>
>> The problem seems to be that after the kernel puts the device into D3
>> the BIOS still tries to access it, or otherwise assumes that it's in D0.
>> This is clearly bogus, since ACPI mandates that devices are put into D3
>> by the OSPM if they are not wake-up sources. In the future we want to
>> unify more of the driver's runtime and system suspend paths, for example
>> by skipping all the system suspend/hibernation hooks if the device is
>> runtime suspended already. Accordingly for all other platforms the goal
>> is still to properly power down the device during hibernation.
>>
>> v2:
>> - Another GEN4 Lenovo laptop had the same issue, while platforms from
>> other vendors (including mobile and desktop, GEN4 and non-GEN4) seem
>> to work fine. Based on this apply the workaround on all GEN4 Lenovo
>> platforms.
>> - add code comment about failing platforms (Ville)
>>
>> Reference: http://lists.freedesktop.org/archives/intel-gfx/2015-February/060633.html
>> Reported-and-bisected-by: Bjørn Mork <bjorn@mork.no>
>> Signed-off-by: Imre Deak <imre.deak@intel.com>
>
> Bjørn, I would really appreciate your Tested-by on this patch before I
> queue it for v4.0 and cc: stable for v3.19.
No problem. This version still works fine for me. Feel free to add
Tested-by: Bjørn Mork <bjorn@mork.no>
Bjørn
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-02 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 11:04 [PATCH v2] drm/i915: gen4: work around hang during hibernation Imre Deak
2015-03-02 12:29 ` Jani Nikula
2015-03-02 13:00 ` Bjørn Mork [this message]
2015-03-04 8:15 ` Jani Nikula
2015-03-03 15:27 ` shuang.he
2015-03-18 9:37 ` Paul Bolle
2015-03-18 10:22 ` Ville Syrjälä
2015-03-18 16:22 ` Paul Bolle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sidn8sfp.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox