From: Pavel Machek <pavel@ucw.cz>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Ilya Tumaykin" <itumaykin@gmail.com>,
"Dirk Griesbach" <spamthis@freenet.de>,
"Mikko Rapeli" <mikko.rapeli@iki.fi>,
"Paul Bolle" <pebolle@tiscali.nl>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: apply the PCI_D0/D3 hibernation workaround everywhere on pre GEN6
Date: Tue, 30 Jun 2015 19:27:06 +0200 [thread overview]
Message-ID: <20150630172706.GA28262@amd> (raw)
In-Reply-To: <1435673207-23030-1-git-send-email-imre.deak@intel.com>
Hi!
> commit da2bc1b9db3351addd293e5b82757efe1f77ed1d
> Author: Imre Deak <imre.deak@intel.com>
> Date: Thu Oct 23 19:23:26 2014 +0300
>
> drm/i915: add poweroff_late handler
>
> introduced a regression on old platforms during hibernation. A workaround was
> added in
>
> commit ab3be73fa7b43f4c3648ce29b5fd649ea54d3adb
> Author: Imre Deak <imre.deak@intel.com>
> Date: Mon Mar 2 13:04:41 2015 +0200
>
> drm/i915: gen4: work around hang during hibernation
>
> using an explicit blacklist for the GENs/BIOS vendors where the issue was
> reported. Later there we had reports of the same failure on platforms not on
> this list.
>
> To my best knowledge the correct thing to do is still to put the device to PCI
> D3 state during hibernation, see [1] and [2] for the reasons. This
> also aligns
Hmm, so the reasons according to you are:
> - ACPI mandates that the OSPM (the kernel in our case) puts all
> devices
> into D3 that are not wake-up sources (i915 is not) (Kudos to Ville
> for
> pointing this out)
Clearly, BIOS vendors did not read this, and pretty clearly Windows
do not follow the specs, either. That means that it is bad idea for us
to follow the specs, and trigger BIOS bugs.
> - Embedded panels have a well defined shutdown sequence. We don't
> have
> any good reason to not follow this, in fact for some panels the
> subsequent reinitialization could be problematic in case of a hard
> power-off. (Thanks to Jani for this info)
Please cite concrete example. I have yet to see machine that would not
power up on forced power down. In fact, I argue that such machine
would be very broken, and that such machine does not exist. While we
have these real machines broken:
> + * Lenovo Thinkpad X301, X61s, X60, T60, X41
> + * Fujitsu FSC S7110
> + * Acer Aspire 1830T
What makes you think that BIOS writers will do something different for
Gen6+ hardware? X301 is not that old.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-06-30 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 14:06 [PATCH] drm/i915: apply the PCI_D0/D3 hibernation workaround everywhere on pre GEN6 Imre Deak
2015-06-30 17:27 ` Pavel Machek [this message]
2015-07-01 8:35 ` Jani Nikula
2015-07-01 8:45 ` Pavel Machek
2015-07-01 9:02 ` Ville Syrjälä
2015-07-01 9:51 ` Pavel Machek
2015-07-01 10:53 ` Ville Syrjälä
2015-07-01 12:35 ` Pavel Machek
2015-07-01 12:42 ` Jani Nikula
2015-07-01 12:57 ` [Intel-gfx] " David Weinehall
2015-07-15 6:22 ` Mikko Rapeli
2015-08-29 18:02 ` Mikko Rapeli
2015-08-31 15:45 ` Jani Nikula
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=20150630172706.GA28262@amd \
--to=pavel@ucw.cz \
--cc=daniel.vetter@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=itumaykin@gmail.com \
--cc=jani.nikula@intel.com \
--cc=mikko.rapeli@iki.fi \
--cc=pebolle@tiscali.nl \
--cc=rjw@rjwysocki.net \
--cc=spamthis@freenet.de \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).