* i855-based ThinkPad STR: Graphics device stays in D3 after resume
@ 2005-04-13 0:32 Andrew Barr
[not found] ` <200504122032.36053.barr.156-ZbGKxL/pcrQ@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Barr @ 2005-04-13 0:32 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
I have been trying to get my ThinkPad R51 to resume from S3 for some weeks
now:
http://thread.gmane.org/gmane.linux.acpi.devel/12971
http://thread.gmane.org/gmane.linux.hardware.thinkpad/17253
http://bugme.osdl.org/show_bug.cgi?id=4455
There's been some discussion on the linux-thinkpad mailinglist that seems to
be the same problem I have:
http://thread.gmane.org/gmane.linux.hardware.thinkpad/17623
http://thread.gmane.org/gmane.linux.hardware.thinkpad/17489
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:
0000:00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
Integrated Graphics Device (rev 02) (prog-if 00 [VGA])
Subsystem: IBM: Unknown device 0557
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0000000 (32-bit, prefetchable)
Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at 1800 [size=8]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 82 35 03 00 90 00 02 00 00 03 00 00 80 00
10: 08 00 00 e0 00 00 00 d0 01 18 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 57 05
30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00
40: 09 00 05 81 00 40 00 00 00 00 00 00 00 00 00 00
50: 00 01 34 00 10 00 00 00 00 00 02 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: ff a2 5a 35 00 00 03 12 92 24 00 00 00 00 00 00
b0: 00 00 00 00 34 a0 36 00 1c 23 00 00 82 e6 48 07
c0: 07 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 00 21 02 00 00 00 00 08 c3 00 ff 25 00 00 00
e0: 2a 00 22 00 98 00 a2 00 00 00 00 00 00 04 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
and after:
0000:00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
Integrated Graphics Device (rev 02) (prog-if 00 [VGA])
Subsystem: IBM: Unknown device 0557
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0000000 (32-bit, prefetchable)
Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at 1800 [size=8]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D3 PME-Enable- DSel=0 DScale=0 PME-
00: 86 80 82 35 03 00 90 00 02 00 00 03 00 00 80 00
10: 08 00 00 e0 00 00 00 d0 01 18 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 14 10 57 05
30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00
40: 09 00 05 81 00 40 00 00 00 00 00 00 00 00 00 00
50: 00 01 34 00 10 00 00 00 00 00 02 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: ff a2 5a 35 00 00 00 00 cc 17 00 00 00 00 00 00
b0: 00 00 00 00 36 0f 11 00 e4 16 00 00 f2 89 3d 02
c0: 07 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 01 00 21 02 03 00 00 00 08 c2 00 ff 25 00 00 00
e0: 2a 00 22 00 98 00 22 00 00 00 00 00 00 04 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I'm afraid I don't know enough about PCI or ACPI to know if this means
anything. It is the only device in D3 after S3, though. All the others are
resumed, they are in D0. I have no acpi_sleep parameter on my kernel
commandline--s3_mode elicits similar behavior from the machine although I've
not compared the PCI config space before and after suspend-to-RAM with that
on the command line.
--
Andrew Barr
Student, Ohio State University
[firstname][lastname] at columbus rr com | [lastname].156 at osu edu
http://home.columbus.rr.com/andrewbarr
"Everyone is entitled to their own opinions, but not their own facts."
- Daniel Patrick Moynihan
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: i855-based ThinkPad STR: Graphics device stays in D3 after resume
[not found] ` <200504122032.36053.barr.156-ZbGKxL/pcrQ@public.gmane.org>
@ 2005-04-13 0:50 ` Matthew Garrett
2005-04-13 12:08 ` Andrew Barr
0 siblings, 1 reply; 3+ messages in thread
From: Matthew Garrett @ 2005-04-13 0:50 UTC (permalink / raw)
To: Andrew Barr; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: i855-based ThinkPad STR: Graphics device stays in D3 after resume
2005-04-13 0:50 ` Matthew Garrett
@ 2005-04-13 12:08 ` Andrew Barr
0 siblings, 0 replies; 3+ messages in thread
From: Andrew Barr @ 2005-04-13 12:08 UTC (permalink / raw)
To: Matthew Garrett; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
On Tuesday 12 April 2005 08:50 pm, Matthew Garrett wrote:
> 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.
I've made some promising progress in getting suspend-to-RAM working. The
following commands return me to the bash prompt after suspend-to-RAM. I
haven't had time to try this within X.org:
cat /sys/bus/pci/devices/0000:00:02.0/config > /var/tmp/pci.config
echo -n mem > /sys/power/state
(resume; ssh into the machine)
cat /var/tmp/pci.config > /proc/bus/pci/00/02.0
video_post
This is without any acpi_sleep parameters. Writing the saved config space back
to sysfs didn't work--the device stayed in D3. Using /proc/bus/pci returned
it to D0. I don't know why. I'll be testing this in X.org later on today.
--
Andrew Barr
Student, Ohio State University
[firstname][lastname] at columbus rr com | [lastname].156 at osu edu
http://home.columbus.rr.com/andrewbarr
"Everyone is entitled to their own opinions, but not their own facts."
- Daniel Patrick Moynihan
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-04-13 12:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2005-04-13 12:08 ` Andrew Barr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox