From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Andrew Barr <barr.156-ZbGKxL/pcrQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: i855-based ThinkPad STR: Graphics device stays in D3 after resume
Date: Wed, 13 Apr 2005 01:50:40 +0100 [thread overview]
Message-ID: <1113353440.10110.96.camel@tyrosine> (raw)
In-Reply-To: <200504122032.36053.barr.156-ZbGKxL/pcrQ@public.gmane.org>
On Tue, 2005-04-12 at 20:32 -0400, Andrew Barr wrote:
> Basically, these people did a BIOS upgrade that seems to have borked
> suspend-to-RAM on their ThinkPads. My ThinkPad is very new, so it shipped
> with a BIOS with this problem. I am going to try downgrading to BIOS and
> Embedded Controller versions mentioned in the above-referenced threads, but I
> did discover something interesting. The graphics device stays in D3 after
> resuming from S3 (I can ssh into my laptop). Here is the output of 'lspci
> -vvvxxx -s 00:02.0' before S3:
Hmm. Interesting. There's no code that will actually have bound to the
PCI device (well, other than the drm driver, but that's different in
magical ways), so the kernel won't attempt to reenable it on resume.
We really should be doing something about devices that the kernel has no
drivers for - at the moment, unless there's a driver loaded, we don't
power down the device at all. However, I'm not entirely clear on /what/
we should be doing.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-13 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 0:32 i855-based ThinkPad STR: Graphics device stays in D3 after resume Andrew Barr
[not found] ` <200504122032.36053.barr.156-ZbGKxL/pcrQ@public.gmane.org>
2005-04-13 0:50 ` Matthew Garrett [this message]
2005-04-13 12:08 ` Andrew Barr
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=1113353440.10110.96.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=barr.156-ZbGKxL/pcrQ@public.gmane.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