FAQs
English (US) 日本語 | Japanese 中文 | Chinese (Simplified)

timeout when waiting for flip irq issue

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

timeout when waiting for flip irq issue

‎10-20-2015 12:33 AM
3,393 Views
leonlin1
Contributor II

Hi all,

     We encounter a timeout issue, the BSP we using is Freescale android 4.4.3 BSP and the platform is i.MX6Q customized board. Our platform enabled the configuaration CONFIG_MX6_CLK_FOR_BOOTUI_TRANS to keep the Uboot's logo pass through kernel until android call mxcfb_set_par() function to change fb mode and pixel format to diplay its animation or logo. We found our device have chance (1~3 times in 1000 times test) to encounter timeout issue. This issue will cause the LCD screen can't show anything, just black screen. But this issue can be recovered by press power button to awake android into screen on after keep android idle to enter the screen off mode. The normal and error logs are as followings, Do you have any idea to solve this issue?

Normal case :

[   14.503497] mxcfb_set_par

[   14.745493] ipu_init_channel

[   14.745545] ipu_init_sync_panel

[   14.749183] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000  <---- android call mxcfb_set_par()to cause warning

[   14.775533] imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

[   14.783801] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000

[   15.519900] ioctl_s_power ov5640_standby(0)  ov5640_init_mode mode is 255 , orig_mode is 255 , frame_rate is 1

[   15.542874] dn_mode is 6

[   15.549215] orig_dn_mode is 6

[   16.081052] type=1400 audit(1445307685.650:5): avc:  denied  { module_request } for  pid=175 comm="netd" kmod="net-pf-16-proto-5" scontext=u:r:netd:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0

[   16.326769] enable ov5640 AF function

[   16.330442] init & enable ov5640 Auto Focus mode!!

[   17.841908] ov5640_AF_mode - mode : 1 ok!!

[   17.846238] ioctl_s_power ov5640_standby(1)

[   22.816357] warning: `zygote' uses 32-bit capabilities (legacy support in use)

[   35.847101] request_suspend_state: wakeup (3->0) at 35841642003 (2015-10-20 02:21:45.426709669 UTC)

[   36.123925] lowmemorykiller: lowmem_shrink: convert oom_adj to oom_score_adj:

[   36.131111] lowmemorykiller: oom_adj 0 => oom_score_adj 0

[   36.136530] lowmemorykiller: oom_adj 1 => oom_score_adj 58

[   36.142836] lowmemorykiller: oom_adj 2 => oom_score_adj 117

[   36.148537] lowmemorykiller: oom_adj 3 => oom_score_adj 176

[   36.154132] lowmemorykiller: oom_adj 9 => oom_score_adj 529

[   36.159796] lowmemorykiller: oom_adj 15 => oom_score_adj 1000

Error case :

[   13.353497] mxcfb_set_par

[   13.599793] ipu_init_channel

[   13.600254] ipu_init_sync_panel

[   13.606842] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000   <---- android call mxcfb_set_par()to cause warning

[   13.626786] imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

[   14.521967] type=1400 audit(1444732951.430:5): avc:  denied  { module_request } for  pid=174 comm="netd" kmod="net-pf-16-proto-5" scontext=u:r:netd:s0 tcontext=u:r:kernel:s0 tclass=system permissive=0

[   14.745588] ioctl_s_power ov5640_standby(0)  ov5640_init_mode mode is 255 , orig_mode is 255 , frame_rate is 1

[   14.771265] dn_mode is 0

[   14.773890] orig_dn_mode is 0

[   14.965344] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   15.545312] enable ov5640 AF function

[   15.551182] init & enable ov5640 Auto Focus mode!!

[   15.822850] bq27x00_update power_supply_changed=0x9

[   15.830812] Change!!!bq27x00_update old_status=0x2,di->cur_status = 0x2

[   15.837767] Change!!!bq27x00_update cache.capacity = 94,di->cache.capacity=95

[   15.844921] Change!!!bq27x00_update cache.temperature = 3055,di->cache.temperature=3055

[   15.853036] Change!!!bq27x00_update temperature = 324

[   15.859000] Change!!!bq27x00_update voltage = 3963

[   15.965361] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   16.965364] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   17.161009] ov5640_AF_mode - mode : 1 ok!!

[   17.165175] ioctl_s_power ov5640_standby(1)

[   17.965365] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   18.965364] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   19.175916] warning: `zygote' uses 32-bit capabilities (legacy support in use)

[   19.965321] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   20.465334] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   21.465334] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   21.965342] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   22.965337] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   23.465383] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   24.465345] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   24.965348] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   25.965405] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   26.456543] request_suspend_state: wakeup (3->0) at 26451256669 (2015-10-13 10:42:43.376575335 UTC)

[   26.475332] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   27.485462] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   28.485448] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   29.485475] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   30.485409] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   30.985415] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   31.985497] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   32.485460] mxc_sdc_fb fb.29: timeout when waiting for flip irq

[   33.485458] mxc_sdc_fb fb.29: MXCFB_WAIT_FOR_VSYNC: timeout 0

[   33.985635] mxc_sdc_fb fb.29: timeout when waiting for flip irq

Labels (1)
Labels
0 Kudos
Reply
2 Replies

‎10-23-2015 05:23 PM
1,291 Views
igorpadykov
NXP Employee
NXP Employee

Hi Leon

if lcd panel will be enabled in Uboot, then in kernel, some IPU re-initialization code

should be skipped, otherwise one will get the "flip irq" error.

Please look at link below showing various ways to avoid this

Re: imx6q mxc_sdc_fb timeout when waiting for flip irq

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply

‎10-25-2015 05:53 PM
1,291 Views
leonlin1
Contributor II

Hi igorpadykov,

                 We already skip some IPU re-initialization function, so the Uboot's logo can display well during kernel boot up time. This issue only happen to show Android's logo or animation during Android boot up time occasionally. We notice that when our system boot up well, it still show some warning message when android display it's logo or animation. Maybe there are some modification need to be done in IPU re-initialization function, but we don't have any idea how to modify to avoid this warnning message. Do you have any suggestion? thanks~

Warnning message :

[   14.749183] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000  <---- android call mxcfb_set_par()to cause warning

[   14.775533] imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

[   14.783801] imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000

0 Kudos
Reply