From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: suspended DRAM bridge
Date: Mon, 01 Apr 2013 23:09:09 +0200 [thread overview]
Message-ID: <5159F775.30805@fold.natur.cuni.cz> (raw)
In-Reply-To: <35938665.ZFvDxnCU3l@vostro.rjw.lan>
Hi Rafael,
Rafael J. Wysocki wrote:
> On Monday, April 01, 2013 06:50:17 PM Martin Mokrejs wrote:
>> Hi Rafael,
>> I have a simple question. Why seems my DRAM controller suspended?
>
> I suppose that runtime PM is disabled for that device and therefore
> runtime_status is meaningless.
But I really mean this pair of values:
/sys/bus/pci/devices/0000:00:00.0/power/runtime_status:suspended
/sys/bus/pci/devices/0000:00:00.0/power/control:auto
>
> And really, that attribute is for *debugging* things by developers who know
> what they are looking for and not for random poking.
Well, if me or you are to figure out why laptop-mode-tools make my life
even more miserable with hotplug issues the requests to provide
grep . /sys/bus/pci/devices/*/power/runtime_status
grep . /sys/bus/pci/devices/*/power/control
provide crap. How can I infer something if I cannot trust the values?
Don't you think that this is the reason why you have a headache and me as well?
Seriously, only pcieport driver reports PME# enabled/disabled messages
in my system although
find /sys/bus/pci/devices/*/power/ -name control | while read f; do echo on > $f; done
should trigger similar message from other drivers as well! Provided they are
somewhat equally verbose under same kernel debug level. But they are all silent.
And if I start to think what the values mean it looks silly my only DRAM controller
is suspended.
I really do think that devices which cannot be ever suspended under a particular
condition should not claim they are suspended if they did not.
I reported that I sometimes see only PME# enabled (or just disabled) in dmesg
from a same device in dmesg *NOT* the accompanied opposite action on the same device.
As I see that most of my pci devices do not ever report a change of their status
I was hoping /sys/bus/pci/devices/*/power/runtime_status is correct.
>
> Besides, this is a host bridge, not a DRAM controller.
Hmm.
>
>> Does it make any sense in a laptop computer? How could the laptop work at all?
>
> I suppose it wouldn't work if the PCI host bridge were suspended. At least
> it couldn't access memory and the PCI bus then.
Thank you, had the same, although naive, expectation.
Thanks,
Martin
next prev parent reply other threads:[~2013-04-01 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5159BAC9.80700@fold.natur.cuni.cz>
2013-04-01 20:56 ` suspended DRAM bridge Rafael J. Wysocki
2013-04-01 21:09 ` Martin Mokrejs [this message]
2013-04-01 21:41 ` Rafael J. Wysocki
2013-04-01 22:03 ` Martin Mokrejs
2013-04-02 14:30 ` Martin Mokrejs
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=5159F775.30805@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/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