System stop after resume from suspend ...

Hi,

The system thread stop running when resume from suspend state...


..............OSD_DebugCommsResume.........................
Xllp_SuspendResume: State Restored: ResumePhase2Data=xa00ff420->xa00ff420
Xllp_SuspendResume: Wake Reason: PEDR=x00000002, PKSR=x00000000,
ISCR=x00000000, IER=x00000000
Xllp_SuspendResume: Exit: (entry_CPSR=xa0000093)
Xllp_SuspendResume: Exit: RCNR=x00000001, RTAR=x00000000, RTSR=x00000000,
PICR=x00000000
Xllp_SuspendResume: Exit: RYAR1=x000fa622, RDAR1=x005a0000
Xllp_SuspendResume: Exit: OSCR0=x8251edb3, OSMR0=x8250a9fd, OIER=x00000001
Xllp_SuspendResume: Exit: OMCR4=x00000000, OMCR5=x00000000, OMCR6=x00000000,
OMCR7=x00000000
OEMPowerOff: Xllp_SuspendAndResume(x804397a0) returned x00000000
OEMPowerOff: g_oalWakeSource => SYSWAKE_POWER_BUTTON(x00000403)
0x87d1ec64: Back from OEMPowerOff
0x87d1ec64: Calling device manager power proc.
0x87d1ec64: +FYS_PowerUp
0x87d1ec64: send low battery patch
0x87d1ec64: -FYS_PowerUp
0x87d1ec64: Calling GWES power proc.
0x87d1ec64: Returning to normally scheduled programming.

I had check that the OS timer 0 interrup is running and by right the
scheduler should continue to run...

Do any one had faced this problem?

--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200804/1

Bruce
Wed Apr 16 20:06:53 PDT 2008

What are you calling "the system thread"? What do you think that the debug
output is demonstrating?

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"JamesCool via PocketPCJunkies.com" <u42351@uwe> wrote in message
news:82cb0fe8cc8f4@uwe...
> Hi,
>
> The system thread stop running when resume from suspend state...
>
>
> ..............OSD_DebugCommsResume.........................
> Xllp_SuspendResume: State Restored: ResumePhase2Data=xa00ff420->xa00ff420
> Xllp_SuspendResume: Wake Reason: PEDR=x00000002, PKSR=x00000000,
> ISCR=x00000000, IER=x00000000
> Xllp_SuspendResume: Exit: (entry_CPSR=xa0000093)
> Xllp_SuspendResume: Exit: RCNR=x00000001, RTAR=x00000000, RTSR=x00000000,
> PICR=x00000000
> Xllp_SuspendResume: Exit: RYAR1=x000fa622, RDAR1=x005a0000
> Xllp_SuspendResume: Exit: OSCR0=x8251edb3, OSMR0=x8250a9fd, OIER=x00000001
> Xllp_SuspendResume: Exit: OMCR4=x00000000, OMCR5=x00000000,
> OMCR6=x00000000,
> OMCR7=x00000000
> OEMPowerOff: Xllp_SuspendAndResume(x804397a0) returned x00000000
> OEMPowerOff: g_oalWakeSource => SYSWAKE_POWER_BUTTON(x00000403)
> 0x87d1ec64: Back from OEMPowerOff
> 0x87d1ec64: Calling device manager power proc.
> 0x87d1ec64: +FYS_PowerUp
> 0x87d1ec64: send low battery patch
> 0x87d1ec64: -FYS_PowerUp
> 0x87d1ec64: Calling GWES power proc.
> 0x87d1ec64: Returning to normally scheduled programming.
>
> I had check that the OS timer 0 interrup is running and by right the
> scheduler should continue to run...
>
> Do any one had faced this problem?
>
> --
> Message posted via PocketPCJunkies.com
> http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200804/1
>

JamesCool
Wed Apr 16 20:47:31 PDT 2008

Hi,

I guess the OS should continue run the scheduled thread but from the debug
message it wouldn't....
It just stop there forever...

Best regards,


Bruce Eitman [eMVP] wrote:
>What are you calling "the system thread"? What do you think that the debug
>output is demonstrating?
>
>> Hi,
>>
>[quoted text clipped - 26 lines]
>>
>> Do any one had faced this problem?

--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200804/1