Re: PM Issues after Android bootup on 2430
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 2 mei 2008, om 05:46 heeft Syed Mohammed, Khasim het volgende geschreven: -Original Message- From: [EMAIL PROTECTED] [mailto:linux-omap- [EMAIL PROTECTED] On Behalf Of Kevin Hilman Sent: Friday, May 02, 2008 3:18 AM To: Nishanth Menon Cc: [EMAIL PROTECTED]; linux-omap@vger.kernel.org Subject: Re: PM Issues after Android bootup on 2430 "Nishanth Menon" <[EMAIL PROTECTED]> writes: On 4/29/08, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote: omapfb omapfb: irq error status 00e2 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 This does look suspiciously like the thread http://linux.omap.com/pipermail/linux-omap-open-source/2007- July/010566.html Interesting... ;)... I never got the chance to debug this issue.. Kevin, Khasim, did u guys get a chance to look at this later?? I dont recollect hearing any one saying the same for 3430 though.. No, I never debugged this any further. AFAIK, the omapfb is still broken in git. Me too :(. We have FB working for 3530 EVM / Beagle boards. Should be same for 2430/2530 as well. against git or 2.6.22? regards, KOen Regards, Khasim -- To unsubscribe from this list: send the line "unsubscribe linux- omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFIGroaMkyGM64RGpERAoJfAJ9CRdM/Bo7qmM4qoe3YO70ALcU8sgCfVoqi 1mC/iHb196xeHblIunXDBEQ= =HR7R -END PGP SIGNATURE- -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: PM Issues after Android bootup on 2430
> -Original Message- > From: [EMAIL PROTECTED] [mailto:linux-omap- > [EMAIL PROTECTED] On Behalf Of Kevin Hilman > Sent: Friday, May 02, 2008 3:18 AM > To: Nishanth Menon > Cc: [EMAIL PROTECTED]; linux-omap@vger.kernel.org > Subject: Re: PM Issues after Android bootup on 2430 > > "Nishanth Menon" <[EMAIL PROTECTED]> writes: > > > On 4/29/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > >> omapfb omapfb: irq error status 00e2 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > >> omapfb omapfb: irq error status 0040 > > This does look suspiciously like the thread > > http://linux.omap.com/pipermail/linux-omap-open-source/2007- > July/010566.html > > > > Interesting... ;)... I never got the chance to debug this issue.. > > > > Kevin, Khasim, did u guys get a chance to look at this later?? I dont > > recollect hearing any one saying the same for 3430 though.. > > No, I never debugged this any further. AFAIK, the omapfb is still > broken in git. > Me too :(. We have FB working for 3530 EVM / Beagle boards. Should be same for 2430/2530 as well. Regards, Khasim -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PM Issues after Android bootup on 2430
"Nishanth Menon" <[EMAIL PROTECTED]> writes: > On 4/29/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> omapfb omapfb: irq error status 00e2 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 >> omapfb omapfb: irq error status 0040 > This does look suspiciously like the thread > http://linux.omap.com/pipermail/linux-omap-open-source/2007-July/010566.html > > Interesting... ;)... I never got the chance to debug this issue.. > > Kevin, Khasim, did u guys get a chance to look at this later?? I dont > recollect hearing any one saying the same for 3430 though.. No, I never debugged this any further. AFAIK, the omapfb is still broken in git. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: PM Issues after Android bootup on 2430
On 4/29/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > omapfb omapfb: irq error status 00e2 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 > omapfb omapfb: irq error status 0040 This does look suspiciously like the thread http://linux.omap.com/pipermail/linux-omap-open-source/2007-July/010566.html Interesting... ;)... I never got the chance to debug this issue.. Kevin, Khasim, did u guys get a chance to look at this later?? I dont recollect hearing any one saying the same for 3430 though.. Regards, Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
PM Issues after Android bootup on 2430
Hi , I am seeing some issues after booting up customized android kernel on 2430. I have taken the 2.23 kernel extracted from the SDK (2.6.23, m5-rc14) and applied the changes to 2.6.14 OMAP linux kernel. I am able to see the GUI after a duration of ~ 10 to 15 minutes. I have followed the steps mentioned in the Wiki as well as emails chains for issues while porting it to 2430. After initial display ,successfully transits from sleep to active mode twice .But Third time fails. Transition from sleep to normal mode was done by pressing the key on the hardware keypad. LCD switches off and console hangs. Here is the trace from my console: # android_power_suspend: 1604321547460 android sleep state 0->2 at 1604321547460 active wake lock PowerManagerService android_power_suspend: enter suspend Stopping tasks ... done. Suspending console(s) Restarting tasks ... android_power_wakeup 2->0 at 1604535606537 done. android_power_suspend: exit suspend, ret = 0 android_power_suspend: done # android_power_suspend: 1659940954691 android sleep state 0->2 at 1659940954691 active wake lock PowerManagerService android_power_suspend: 1659960619076 android_power_suspend: enter suspend Stopping tasks ... done. Suspending console(s) omapfb omapfb: irq error status 00e2 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 omapfb omapfb: irq error status 0040 Restarting tasks ... android_power_wakeup 2->0 at 1660136538459 done. android_power_suspend: exit suspend, ret = 0 android_power_suspend: done # # # android_power_suspend: 1807690295383 android sleep state 0->2 at 1807690295383 active wake lock PowerManagerService android_power_suspend: enter suspend Stopping tasks ... done. Suspending console(s) - Pls Let me know if you have any inputs on this. Regards, Shivananda -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
