Hi,
Sorry, I misread the previous email. This time I checked the
CONFIG_FTRACE option and redone the tests, so anyway that's good
because I'm sure that in my previous test it was unset.
About how I am suspending to ram, I'm currently using Gentoo
'hibernate-ram' script, which in turn is using s2ram. The options
passed to the s2ram are "-f -s -a 3" if I remember correctly (can't
check the logs right now). The hibernate-ram script does some stuff
before suspending, like unloading some modules, etc...
Also, as I'm doing some very basic testing only, before attempting to
suspend I issue a 'init 1' command so I go into single-user mode, no
X. In some cases I even unload nvidia.ko module by using rmmod, but
I'm pretty sure this don't make any difference.
Best regards,
Eduard
2008/9/2 Rafael J. Wysocki <rjw@xxxxxxx>:
> On Tuesday, 2 of September 2008, Eduard Huguet wrote:
>> Hi,
>> I retried after checking CONFIG_FTRACE through menuconfig (I double
>> checked it was set in .config). Same results. Can I do any other test
>> now that this setting is on (I guess is something related to kernel
>> function tracing)?
>
> I'm not sure if I understand you correctly.
>
> If you had CONFIG_FTRACE unset before, please unset it.
>
> Also, please tell me what _exactly_ you do to suspend to RAM.
>
> Thanks,
> Rafael
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
