From: Philip Walden <pwaldenlinux@pacbell.net>
To: linux-acpi@vger.kernel.org
Subject: Older PC stands-by only momentarily
Date: Fri, 21 Jul 2006 20:27:40 -0700 [thread overview]
Message-ID: <44C19B2C.1030603@pacbell.net> (raw)
I have an older PC with limited acpi capabilities and 2.6.17-1.2141_FC4
Code:
CPU type : AMD Athlon(tm)
Processor CPU speed : 856.102 MHz
Cache size : 512 KB Bogomips : 1714.25
Processor ID : 0
Bus mastering control : no
Power management : no
Throttling control : no
Limit interface : no
Active C-state : C1
C-states (incl. C0) : 2
But it does have:
ACPI: (supports S0 S1 S5) and /sys/power/state == "standby disk".
If I do a echo -n "standby" >state, then it appears to suspend for 1-3
seconds, power light blinking, etc. Then comes back to life. I cannot
figure out what is waking it up. acpitool say all wakeup devices are
disabled.
# acpitool -w
Device Sleep state Status
---------------------------------------
1. PCI0 1 disabled
2. KBC 1 disabled
3. USB0 1 disabled
4. USB1 1 disabled
Here is the system log. The acpi log has nothing in it.
Code:
Jul 20 16:37:26 walden4 kernel: Stopping tasks:
==================================================
================================================== ===|
Jul 20 16:37:26 walden4 kernel: pnp: Device 00:0b disabled.
Jul 20 16:37:26 walden4 kernel: pnp: Device 00:0a disabled.
Jul 20 16:37:26 walden4 kernel: ACPI: PCI interrupt for
device0000:00:0f.0 disabled
Jul 20 16:37:26 walden4 kernel: ACPI: PCI interrupt for device
0000:00:04.2 disabled
Jul 20 16:37:26 walden4 kernel: ACPI: PCI Interrupt 0000:00:04.2[D] ->
Link [LNKD] -> GSI 9 (level, low) -> IRQ 9
Jul 20 16:37:26 walden4 kernel: bttv0: reset, reinitialize
Jul 20 16:37:26 walden4 kernel: bttv0: PLL: 28636363 => 35468950 .. ok
Jul 20 16:37:26 walden4 kernel: ACPI: PCI Interrupt 0000:00:0d.1[A] ->
Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
Jul 20 16:37:26 walden4 kernel: ACPI: PCI Interrupt 0000:00:0f.0[A] ->
Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
Jul 20 16:37:27 walden4 kernel: eth0: link up, 100Mbps, full-duplex, lpa
0x45E1
Jul 20 16:37:27 walden4 kernel: pnp: Device 00:06 does not support
activation.
Jul 20 16:37:27 walden4 kernel: pnp: Device 00:07 does not support
activation.
Jul 20 16:37:27 walden4 kernel: pnp: Device 00:0a activated.
Jul 20 16:37:27 walden4 kernel: pnp: Device 00:0b activated.
Jul 20 16:37:27 walden4 kernel: Restarting tasks... done
next reply other threads:[~2006-07-22 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 3:27 Philip Walden [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-22 3:53 Older PC stands-by only momentarily Brown, Len
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=44C19B2C.1030603@pacbell.net \
--to=pwaldenlinux@pacbell.net \
--cc=linux-acpi@vger.kernel.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