From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Kilian Singer <kilian.singer@quantumtechnology.info>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-pci <linux-pci@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: PCI: Revert "PCI: Add runtime PM support for PCIe ports"
Date: Mon, 2 Jan 2017 14:10:19 +0200 [thread overview]
Message-ID: <20170102121019.GA3353@lahna.fi.intel.com> (raw)
In-Reply-To: <20170102114040.GA20127@wunner.de>
On Mon, Jan 02, 2017 at 12:40:40PM +0100, Lukas Wunner wrote:
> On Fri, Dec 30, 2016 at 01:16:17AM +0100, Kilian Singer wrote:
> > I did the debug message on the 4.10-rc1 for now. I could go back to 4.9
> > if that helps but needs some time again to compile.
> > The debug messages from the first rpm_... to the crash are:
> [...]
> > [ 24.831417] nouveau 0000:01:00.0: rpm_suspend
> > [ 24.831427] nouveau 0000:01:00.0: DRM: suspending console...
> > [ 24.831432] nouveau 0000:01:00.0: DRM: suspending display...
> > [ 24.831477] nouveau 0000:01:00.0: DRM: evicting buffers...
> > [ 24.865243] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
> > [ 24.865269] nouveau 0000:01:00.0: DRM: suspending client object trees...
> > [ 24.870724] nouveau 0000:01:00.0: DRM: suspending kernel object tree...
> > [ 26.080300] thinkpad_acpi: EC reports that Thermal Table has changed
> > [ 26.207691] pcieport 0000:00:01.0: rpm_idle
> > [ 26.207693] pcieport 0000:00:01.0: rpm_suspend
> > [ 28.927640] snd_hda_codec_hdmi hdaudioC0D0: rpm_suspend
> > SYSTEM IS NOW NOT RESPONSIVE
>
> So two seconds before the system became unresponsive, the root port above
> the discrete GPU suspended, suggesting that's the culprit. Could you test
> either of the attached patches to confirm this theory? They disable
> runtime PM on this specific root port but allow it on all the others.
>
> You've got an Optimus laptop, i.e. power to the discrete GPU can be cut.
> Traditionally this is achieved by invoking an ACPI _DSM (Device Specific
> Method). That's what we did up until v4.7.
>
> However on newer laptops Windows no longer cuts power to the discrete GPU
> by invoking the _DSM, but rather by suspending the root port above the
> GPU. (More specifically by turning off Power Resources required for D3
> of the root port, those are specified in a _PR3 object.) We started
> supporting this with v4.8.
>
> If the above theory is correct, we need to involve Optimus experts
> because this is not an issue then with powering down root ports in
> general, but rather specific to this Optimus use case.
[Back from vacation now]
I've checked the acpidump of this machine and it does not seem to be a
traditional Optimus machine. At least this one is missing the magic _DSM
which is used to gather capabilities of the graphics device.
However, it does have _PR3 and it is attached to the device
(_SB.PCI0.PEG) itself, not the root port.
One thing you could try in addition to Lucas' patches is just to prevent
D3cold from the device by doing this:
# echo 0 > /sys/bus/pci/devices/0000:01:00.0/d3cold_allowed
next prev parent reply other threads:[~2017-01-02 12:10 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 23:57 PCI: Revert "PCI: Add runtime PM support for PCIe ports" Bjorn Helgaas
2016-12-28 9:17 ` Mika Westerberg
2016-12-28 11:29 ` Lukas Wunner
2016-12-28 16:18 ` Bjorn Helgaas
2016-12-29 9:58 ` Kilian Singer
2016-12-29 16:02 ` Kilian Singer
2016-12-29 16:20 ` Kilian Singer
2016-12-29 17:50 ` Lukas Wunner
2016-12-29 22:52 ` Kilian Singer
2016-12-29 23:02 ` Kilian Singer
2016-12-29 23:05 ` Kilian Singer
2016-12-29 23:48 ` Lukas Wunner
2016-12-29 23:20 ` Kilian Singer
2016-12-30 0:07 ` Lukas Wunner
2016-12-30 0:16 ` Kilian Singer
2016-12-30 0:24 ` Kilian Singer
2016-12-30 0:22 ` Rafael J. Wysocki
2016-12-30 0:39 ` Kilian Singer
2016-12-30 0:41 ` Rafael J. Wysocki
2016-12-30 0:45 ` Kilian Singer
2016-12-30 1:40 ` Rafael J. Wysocki
2016-12-30 1:50 ` Rafael J. Wysocki
2016-12-30 1:52 ` Rafael J. Wysocki
2016-12-30 13:37 ` Kilian Singer
2016-12-30 13:59 ` Kilian Singer
2016-12-30 14:44 ` Rafael J. Wysocki
2016-12-30 14:47 ` Rafael J. Wysocki
2017-01-02 12:22 ` Mika Westerberg
2017-01-03 17:12 ` Kilian Singer
2017-01-02 11:40 ` Lukas Wunner
2017-01-02 12:10 ` Mika Westerberg [this message]
2017-01-02 13:53 ` Mika Westerberg
2017-01-02 14:48 ` Mika Westerberg
2017-01-02 21:31 ` Rafael J. Wysocki
2017-01-03 9:51 ` Mika Westerberg
2017-01-03 15:15 ` Peter Wu
2017-01-03 16:11 ` Lukas Wunner
2017-01-03 16:31 ` Peter Wu
2017-01-03 16:44 ` Deucher, Alexander
2017-01-03 18:09 ` Lukas Wunner
2017-01-03 18:12 ` Bjorn Helgaas
2017-01-03 21:38 ` Rafael J. Wysocki
2017-01-03 21:52 ` Kilian Singer
2017-01-03 22:07 ` Rafael J. Wysocki
2017-01-03 22:25 ` Kilian Singer
2017-01-03 22:25 ` Bjorn Helgaas
2017-01-03 23:13 ` Rafael J. Wysocki
2017-01-04 0:05 ` Bjorn Helgaas
2017-01-04 1:09 ` Rafael J. Wysocki
2017-01-04 8:16 ` Lukas Wunner
2017-01-04 10:33 ` Kilian Singer
2017-01-04 12:29 ` Mika Westerberg
2017-01-04 15:50 ` Deucher, Alexander
2017-01-04 21:09 ` Peter Wu
2017-01-04 21:58 ` Rafael J. Wysocki
2017-01-04 23:21 ` David Airlie
2017-01-05 15:06 ` Lukas Wunner
2017-01-05 18:13 ` Peter Jones
2017-01-05 19:36 ` David Airlie
2017-01-09 15:11 ` Lyude Paul
2017-01-09 15:21 ` Hans de Goede
2017-01-09 18:48 ` Kilian Singer
2017-01-10 0:33 ` David Airlie
2017-01-10 9:17 ` Kilian Singer
2017-01-12 18:10 ` Lyude Paul
2017-01-24 4:59 ` Lukas Wunner
2017-01-24 19:09 ` Lyude Paul
2017-01-11 20:40 ` Lyude Paul
2017-01-12 1:13 ` Lyude Paul
2017-01-12 2:04 ` Lyude Paul
2017-01-12 2:12 ` Lukas Wunner
2017-01-17 15:55 ` Mika Westerberg
2017-01-17 18:06 ` Lyude Paul
2017-01-17 19:10 ` Bjorn Helgaas
2017-01-17 19:49 ` Lyude Paul
2017-01-07 11:45 ` Hans de Goede
2017-01-07 12:16 ` Lukas Wunner
2017-01-09 23:00 ` Peter Jones
2017-01-10 0:17 ` David Airlie
2017-01-10 1:24 ` Lukas Wunner
2017-01-10 2:15 ` David Airlie
2017-01-11 11:04 ` Hans de Goede
2017-01-11 13:24 ` Kilian Singer
2017-01-11 13:26 ` Hans de Goede
2017-01-11 16:24 ` Peter Jones
2017-01-11 19:20 ` Kilian Singer
2017-01-05 10:49 ` Mika Westerberg
2017-01-05 14:19 ` Rafael J. Wysocki
2017-01-05 14:20 ` Mika Westerberg
2017-01-05 14:23 ` Rafael J. Wysocki
2017-01-05 14:42 ` Lukas Wunner
2017-01-06 1:21 ` Rafael J. Wysocki
2017-01-07 6:50 ` Mika Westerberg
2017-01-07 11:35 ` Peter Wu
2017-01-07 12:19 ` Lukas Wunner
2017-01-07 12:36 ` Peter Wu
2017-01-08 14:05 ` Lukas Wunner
2017-01-04 21:55 ` Rafael J. Wysocki
2017-01-03 21:26 ` Rafael J. Wysocki
2017-01-03 17:37 ` Kilian Singer
2017-01-03 17:10 ` Kilian Singer
2017-01-03 16:59 ` Kilian Singer
2017-01-03 17:08 ` Kilian Singer
2016-12-30 0:19 ` Rafael J. Wysocki
2016-12-30 14:48 ` Rafael J. Wysocki
2017-01-17 14:56 ` Bjorn Helgaas
2017-01-17 15:49 ` Kilian Singer
2017-01-23 20:33 ` Bjorn Helgaas
2017-01-23 21:12 ` Mika Westerberg
2017-01-24 4:53 ` Lukas Wunner
2017-01-24 20:01 ` Bjorn Helgaas
2017-01-25 9:48 ` Mika Westerberg
2017-01-25 16:05 ` Kilian Singer
2017-01-25 16:31 ` Mika Westerberg
2017-01-25 17:58 ` Bjorn Helgaas
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=20170102121019.GA3353@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=kilian.singer@quantumtechnology.info \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=rafael.j.wysocki@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).