Re: [rowboat] no_console_suspend

[Ashwin Bihari]

On Fri, May 4, 2012 at 3:43 AM, venkat k raju <kvraj...@gmail.com> wrote:
>
> Dear all,
>
> what is use of no_console_suspend in android bootarg
>
> thanks&Regards
> k.v.raju
>
> --

That instructs the Kernel not to disable the console when it suspends
so you can debug any issues that come up then. If your suspend is
working properly, you can remove that bootarg..

-- Ashwin

[venkat k raju]

[venkat k raju]

Dear Ashwin Bihari,

i have included this option in my bootarg even though my console is suspending .

setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off no_console_suspend omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16'

can you suggest me how to solve this issues? is any anything i am wrong doing in kernel configuration related to this?

--
You received this message because you are subscribed to the Google Groups "rowboat" group.
To post to this group, send email to row...@googlegroups.com.
To unsubscribe from this group, send email to rowboat+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rowboat?hl=en.

--
thanks&Regards
k.v.raju

[seba]

Hi,

Try no_console_suspend=1

BR,
Seba.

On 4 Maj, 15:50, venkat k raju <kvraju....@gmail.com> wrote:
> Dear Ashwin Bihari,
>
> i have included this option in my bootarg even though my console is
> suspending .
>
> setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off
> no_console_suspend omap_vout.vid1_static_vrfb_alloc=y vram=8M
> omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16'
>
> can you suggest me how to solve this issues? is any anything i am wrong
> doing in kernel configuration related to this?
>
>
>
>
>

> On Fri, May 4, 2012 at 6:06 PM, Ashwin Bihari <abih...@gmail.com> wrote:
> > On Fri, May 4, 2012 at 3:43 AM, venkat k raju <kvraju....@gmail.com>

[venkat k raju]

Hi sebastian.draus,

i have tried 

 setenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M

 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off

 no_console_suspend=1 omap_vout.vid1_static_vrfb_alloc=y vram=8M

omapfb.vram=0:8M omapdss.def_disp=dvi omapfb.mode=dvi:1024x768-16'

even though same console is suspending .

--
unsubscribe: android-porti...@googlegroups.com
website: http://groups.google.com/group/android-porting

--
thanks&Regards
k.v.raju

[hedwin]

Venkat,

Can you tell what the problem is you try to solve or face

the no_console_suspend option only makes sense for the printk used in the kernel drivers resume/suspend calls.

[venkat k raju]

Dear hedwin,

thank a lot.

i have been facing this issues.

initial i thought only console was suspending. but now i am thinking entire my board was hanging and releasing.

Behavior :

after zygote process run if i hit immediately then my console is working (ls ,ps,logcat,dmesg) fine.

after 3 or 5 minit my board is hanging,then if hit enter afer some time my console is releasing.

note :

1)  My lcd display not woring i don't know why? i have done everything related to display like kernel configuration,initialize the lcd structure in board-config.c file. 

2) But my touch and back light is working fine. without hanging mode i am  able to print the touch interrupt indication and event on console window,if the console is hang then touch driver printk also not printing on console window. because this indication i am thing entire board is hanging.

3) same android rootfs,u-boot.bin is working fine with 2.6.32 kernel.

please can you suggest me what is wrong i am doing?