It seems that the lock state is not right ,that would cause this
error,now in driver level,when wake up,I hold a lock for 5 seconds,It
seems the second wakeup is right,it's better than former,but I don't
think it is the best way to fix this,perhaps do something in app level
is better,can anybody give me some idea?

On 7月23日, 下午6时40分, robert_mu <[email protected]> wrote:
> Hi,thanks for your reply :)
> today I meet this error a few times,It seems that when I use the
> peripheral device such as T flash card,a copper line dragged  from my
> board to connect the Oscilloscopes(for test something),the error
> occurs with a not low probability,is my judgement right?what condition
> will cause your error there?
>
>  thanks
> On 7月22日, 下午3时23分, Elvis Dowson <[email protected]> wrote:
>
>
>
> > Hi,     I'm facing the same issue with android-2.6.29 and android-1.5 SDK
> > build, on overo TI OMAP 3503 platform. Here are my observations, if someone
> > has a fix for this it would be great.
>
> > Observation 01
> > ----------------------
>
> > I get the following kernel error message on bootup, could you recommend a
> > fix for this?
>
> > mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
>
> > regulator: Unable to get requested regulator: vmmc_aux
> > regulator: Unable to get requested regulator: vmmc
>
> > SR1: VDD autocomp is not active
>
> > Observation 02
> > ----------------------
>
> > After the system goes to suspend mode, if I press the a key that sends an
> > event via the serial UART3 debug console, it wakes up briefly and then
> > immediately goes back to sleep, and I see the following messages on the
> > console.
>
> > The same thing happens if I press the touchscreen briefly. I am using an
> > ads7846 touchscreen controller connected to a 4.3" LG-Philips LCD display,
> > with the gumstix overo earth (TI OMAP 3503) and palo43 board.
>
> > Powerdomain (core_pwrdm) didn't enter target state 1
> > Powerdomain (usbhost_pwrdm) didn't enter target state 1
> > Could not enter target state in pm_suspend
> >wakeupwake lock: mmc_delayed_work
> > mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
> > Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
> > done.
> > suspend: exit suspend, ret = 0 (2000-01-01 00:04:08.555633537 UTC)
> > PM: Syncing filesystems ... done.
> > Freezing user space processes ... (elapsed 0.00 seconds) done.
> > Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> > Suspending console(s) (use no_console_suspend to debug)
>
> > Observation 03
> > ----------------------
>
> > If I press the touchscreen for a long time (> 2 secs), it comes out of
> > suspend mode with the following error messages
>
> > Powerdomain (core_pwrdm) didn't enter target state 1
> > Powerdomain (usbhost_pwrdm) didn't enter target state 1
> > Could not enter target state in pm_suspend
> >wakeupwake lock: mmc_delayed_work
> > mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
> > Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
> > request_suspend_state:wakeup(3->0) at 109015166614 (2000-01-01
> > 00:04:37.537445064 UTC)
> > done.
> > suspend: exit suspend, ret = 0 (2000-01-01 00:04:37.575256342 UTC)
> > D/SurfaceFlinger(  888):Screenabout to return, flinger = 0x16f328
>
> > Best regards,
>
> > Elvis- 隐藏被引用文字 -
>
> - 显示引用的文字 -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to