I wrote
> > So we have "uadmin 3 21" to check if suspend to ram might work, and
> > "uadmin 3 20" to actually suspend the system to ram. uadmin 3 20 doesn't
> > seem to be a test point but the real function.
>
> Oops, maybe not. The box does seem to resume after "uadmin 2 20" on it's
> own, after a short pause.
OK, "uadmin 2 20" is supposed to suspend the box into S3-suspend to ram.
Problem is apparently that this old ASUS P2B box does not support ACPI
S3 state. It supports S0, S1, S4 and S5. But not S3. From iasl -g:
...
DefinitionBlock ("{From Memory Of Running System}.aml", "DSDT", 1, "ASUS", "P2B-
LS ", 0x00001000)
{
Scope (\_PR)
{
Processor (\_PR.CPU0, 0x01, 0x0000E410, 0x06) {}
}
Name (\_S0, Package (0x04)
{
0x05,
0x05,
0x00,
0x00
})
Name (\_S1, Package (0x04)
{
0x07,
0x07,
0x00,
0x00
})
Name (\_S4, Package (0x04)
{
0x06,
0x06,
0x00,
0x00
})
Name (\_S5, Package (0x04)
{
0x06,
0x06,
0x00,
0x00
})
...
So, the box suspends all drivers, tries to enter S3, and in function
AcpiEnterSleepStatePrep() notices that \_S3 is missing in the ACPI
tables, returns an error, and the system resumes...
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
