Hi Shreyas, On 2/4/09, Shreyas Mahajan <mahajan.shreyas@xxxxxxxxx> wrote: > Hi, > Thanks for constantly tolerating my ignorance. I git-cloned the > latest PM tree available and booted my 3430 LDP board with ldp > defconfig configuration. Now the problem regarding hanging of machine > after some small interval is solved but when I done 'echo mem > >/sys/power/state' it gives error to suspend, > This is log for it, > > '/ # echo mem > /sys/power/state > <6>PM: Syncing filesystems ... PM: Syncing filesystems ... done. > done. > Freezing user space processes ... Freezing user space processes ... > (elapsed 0.00 seconds) (elapsed 0.00 seconds) done. > done. > Freezing remaining freezable tasks ... Freezing remaining freezable > tasks ... (elapsed 0� )����r$�Powerdomain (core_pwrdm) d1 > Powerdomain (per_pwrdm) didn't enter target state 1 > �*43 > Could not enter target state in pm_suspendend to debug) > � 1�ռ���, 森�Ѡr�� > Restarting tasks ... Restarting tasks ... done.%�������� J$�4%�% Ѵ�*43 > done.F�)������������ J$�4%�% Ѵ�*43 > ' > I searched similar problems on mailing list, in which suspend log > contains exactly which process could not be stopped as reason to > suspend failure. But in above log, I could not interpret such a > reason. > Could anyone please help me with this? Please look into below mail thread on the PM off mode support in l-o list. http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg08968.html If you are trying it on SDP , use u-boot mentioned in the above link. use below settings before running echo mem > /sys/power/state for off mode. echo 1 > /sys/power/clocks_off_while_idle echo 1 > /sys/power/voltage_off_while_idle echo 1 > /sys/power/enable_off_mode I tried it on my SDP with omap_3430sdp_min_defconfig, I am seeing all the domains entering to OFF mode. thanks Ramesh Gupta G -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
