AnsweredAssumed Answered

iMX6 framebuffer error with yocto

Question asked by Krisztian Bakos on Jul 1, 2015
Latest reply on Jul 14, 2015 by Krisztian Bakos

Hello,

 

I have a strange error with my custom iMX6 board, running Yocto -> fido | meta-qt5 -> fido.

The framebuffer device comes up and I see picture on my LCD screen, but after some minutes I get the following error:

 

root@imx6qsabresd:~# imx-ipuv3 2400000.ipu: ch = 9, pm_runtime_put failed:-38!

CPU: 0 PID: 25 Comm: kworker/0:1 Not tainted 3.14.28-1.0.0_ga+g91cf351 #7

Workqueue: events console_callback

[<80014644>] (unwind_backtrace) from [<8001164c>] (show_stack+0x10/0x14)

[<8001164c>] (show_stack) from [<8065485c>] (dump_stack+0x7c/0xbc)

[<8065485c>] (dump_stack) from [<80459cdc>] (ipu_uninit_channel+0x524/0xa7c)

[<80459cdc>] (ipu_uninit_channel) from [<802ca220>] (mxcfb_blank+0x80/0xb8)

[<802ca220>] (mxcfb_blank) from [<802b0550>] (fb_blank+0x54/0xa8)

[<802b0550>] (fb_blank) from [<802ba92c>] (fbcon_blank+0xf4/0x2a8)

[<802ba92c>] (fbcon_blank) from [<802f6604>] (do_blank_screen+0x1d4/0x284)

[<802f6604>] (do_blank_screen) from [<802f94dc>] (console_callback+0x88/0x15c)

[<802f94dc>] (console_callback) from [<8003ed2c>] (process_one_work+0xf4/0x35c)

[<8003ed2c>] (process_one_work) from [<8003f97c>] (worker_thread+0x130/0x3bc)

[<8003f97c>] (worker_thread) from [<80044c3c>] (kthread+0xcc/0xe4)

[<80044c3c>] (kthread) from [<8000e478>] (ret_from_fork+0x14/0x3c)

 

And my screen goes off (pixel clock stops)

 

Does anyone have any idea what could be the problem?

 

Thank you in advance!

 

Best regards,

Krisztián Bakos

Outcomes