* Suspend issue on ancient asus A7V system
@ 2008-04-21 9:36 Michel Lespinasse
2008-04-22 7:33 ` Zhang Rui
0 siblings, 1 reply; 3+ messages in thread
From: Michel Lespinasse @ 2008-04-21 9:36 UTC (permalink / raw)
To: linux-acpi
Hi,
I'm having a minor issue getting suspend to ram to work on an old
asus A7V based system: the system does suspend (I can hear the fans
go off etc...) but it immediately resumes.
I do have a workaround though: After booting, this system shows in
/proc/acpi/wakeup:
Device S-state Status Sysfs node
PWRB S5 *enabled
PCI0 S4 disabled no-bus:pci0000:00
USB0 S4 disabled pci:0000:00:04.2
USB1 S4 disabled pci:0000:00:04.3
If I run echo PWRB > /proc/acpi/wakeup,
1- the kernel complains that "ACPI: 'PCI0' and 'PWRB' have the same GPE,
can't disable/enable one seperately"
2- /proc/acpi/wakeup now shows:
Device S-state Status Sysfs node
PWRB S5 *disabled
PCI0 S4 disabled no-bus:pci0000:00
USB0 S4 disabled pci:0000:00:04.2
USB1 S4 disabled pci:0000:00:04.3
3- The system can now be suspended, and it will
resume normally when I press the power button.
This is not a recent regression, that system has been like that since
I first got suspend working.
Hope this helps. I can collect additional information if you tell me how.
Cheers,
--
Michel Lespinasse
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Suspend issue on ancient asus A7V system
2008-04-21 9:36 Suspend issue on ancient asus A7V system Michel Lespinasse
@ 2008-04-22 7:33 ` Zhang Rui
2008-04-22 10:03 ` Michel Lespinasse
0 siblings, 1 reply; 3+ messages in thread
From: Zhang Rui @ 2008-04-22 7:33 UTC (permalink / raw)
To: Michel Lespinasse; +Cc: linux-acpi
On Mon, 2008-04-21 at 02:36 -0700, Michel Lespinasse wrote:
> Hi,
>
> I'm having a minor issue getting suspend to ram to work on an old
> asus A7V based system: the system does suspend (I can hear the fans
> go off etc...) but it immediately resumes.
>
> I do have a workaround though: After booting, this system shows in
> /proc/acpi/wakeup:
> Device S-state Status Sysfs node
> PWRB S5 *enabled
> PCI0 S4 disabled no-bus:pci0000:00
> USB0 S4 disabled pci:0000:00:04.2
> USB1 S4 disabled pci:0000:00:04.3
>
> If I run echo PWRB > /proc/acpi/wakeup,
>
> 1- the kernel complains that "ACPI: 'PCI0' and 'PWRB' have the same GPE,
> can't disable/enable one seperately"
>
> 2- /proc/acpi/wakeup now shows:
> Device S-state Status Sysfs node
> PWRB S5 *disabled
> PCI0 S4 disabled no-bus:pci0000:00
> USB0 S4 disabled pci:0000:00:04.2
> USB1 S4 disabled pci:0000:00:04.3
What can you see in /proc/acpi/wakeup if you run "echo PWRB
> /proc/acpi/wakeup" again?
Please open a bug at
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
and attach the acpidump output there.
thanks,
rui
>
> 3- The system can now be suspended, and it will
> resume normally when I press the power button.
>
> This is not a recent regression, that system has been like that since
> I first got suspend working.
>
> Hope this helps. I can collect additional information if you tell me how.
>
> Cheers,
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Suspend issue on ancient asus A7V system
2008-04-22 7:33 ` Zhang Rui
@ 2008-04-22 10:03 ` Michel Lespinasse
0 siblings, 0 replies; 3+ messages in thread
From: Michel Lespinasse @ 2008-04-22 10:03 UTC (permalink / raw)
To: Zhang Rui; +Cc: linux-acpi
On Tue, Apr 22, 2008 at 03:33:50PM +0800, Zhang Rui wrote:
> Please open a bug at
> http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
> and attach the acpidump output there.
Done, bug 10503. No idea if I used the correct component though.
Thanks,
--
Michel Lespinasse
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-04-22 10:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-21 9:36 Suspend issue on ancient asus A7V system Michel Lespinasse
2008-04-22 7:33 ` Zhang Rui
2008-04-22 10:03 ` Michel Lespinasse
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox