-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UDOO crash when connecting HDMI cable during operation (DVI) #10
Comments
Could you supply dmesg and config file? Could you test files from: http://kowalczyk.ws/imx/kernel/4.0/ ? Kernel command line: console=ttymxc1,115200 root=/dev/sda1 rw mem=1024M video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 panic=10 |
My kernel command line was wrong, when i play with different command lines, the lock up when reconnecting the HDMI cable disappeared, but i get an error during boot. Here is my kernel config:
My dmesg output with the wrong kernel command line:
The kernel boot logs containing your command line:
I will check your kernel config later on. |
which version of uboot do you have ? |
U-Boot 2015.04+fslc+gb16ec2d (Jun 11 2015 - 07:28:25) It is the u-boot provided by freescale https://github.com/Freescale/u-boot-fslc |
I use now uboot-udoo-quad 2015.01-1 from arch linux. |
Could you test my kernel or compile vivante driver into kernel ? |
I wiil test it with a changed kernel config... |
Thank you very much. Now the HDMI output works. I use the command line you added in 77d1626 and the kernel config below. But the issue still remains, that when i connect the hdmi cable while the udoo is running, the system locks up. The same behaviour is present, when the hdmi cable is plugged in when powering the board up, wait for the boot process to finish, disconnect the hdmi cable and reconnect it. Working kernel config
|
issues: 1) problem with HDMI sound: CPU: 2 PID: 740 Comm: alsa-sink-i.MX Not tainted 4.0.0 #21 [ 153.834550] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 153.839818] [<80015624>] (unwind_backtrace) from [<800117dc>] (show_stack+0x10/0x14) [ 153.846281] [<800117dc>] (show_stack) from [<806fea84>] (dump_stack+0x8c/0x9c) [ 153.852217] [<806fea84>] (dump_stack) from [<802843c8>] (Ldiv0+0x8/0x10) [ 153.857627] [<802843c8>] (Ldiv0) from [<802fb69c>] (sdma_prep_dma_cyclic+0x24/0x1a4) [ 153.864090] [<802fb69c>] (sdma_prep_dma_cyclic) from [<805575d4>] (hdmi_dma_trigger+0x168/0x1cc) [ 153.871590] [<805575d4>] (hdmi_dma_trigger) from [<8053ff9c>] (soc_pcm_trigger+0x9c/0x11c) [ 153.878571] [<8053ff9c>] (soc_pcm_trigger) from [<8052ba7c>] (snd_pcm_action_single+0x38/0x80) [ 153.885890] [<8052ba7c>] (snd_pcm_action_single) from [<8052c1a0>] (snd_pcm_action_lock_irq+0x3c/0x64) [ 153.893901] [<8052c1a0>] (snd_pcm_action_lock_irq) from [<8052d95c>] (snd_pcm_common_ioctl1+0x314/0xe58) [ 153.902087] [<8052d95c>] (snd_pcm_common_ioctl1) from [<8052e688>] (snd_pcm_playback_ioctl1+0x1e8/0x4bc) [ 153.910276] [<8052e688>] (snd_pcm_playback_ioctl1) from [<800f4e58>] (do_vfs_ioctl+0x414/0x608) [ 153.917685] [<800f4e58>] (do_vfs_ioctl) from [<800f5080>] (SyS_ioctl+0x34/0x5c) [ 153.923702] [<800f5080>] (SyS_ioctl) from [<8000e560>] (ret_fast_syscall+0x0/0x34)
This problem is related to hdmi sound too . [ 3531.580280] imx-hdmi-audio imx-hdmi-audio: failed to config slave dma |
After last commits HDMI video should works ok. |
HDMI video output works. But when in plug in the HDMI cable after booting the udo board, it still locks up. |
I couldn't reproduce this problem with my kernel. Could you supply kernel oops log? |
Do you use DVI adapter or some any other adapter? |
Sorry, but i do net get any oops message, i see nothing in my serial terminal. The board just locks up. It does not accept any keyboard inputs. |
Thats the point, DVI, could you supply your edid and monitor model and as many as possible informations. |
Model: Dell P2012Ht, see http://www1.la.dell.com/vc/en/corp/peripherals/dell-p2012h/pd.aspx?refid=dell-p2012h&s=corp EDID:
Misc output:
|
I have seen many patches related to DVI: |
Hi, did you try only_cea=1 for mxc_hdmi module? |
With mxc_hdmi.only_cea=0 there is no change in the behaviour (lock up) and no image on the monitor. With mxc_hdmi.only_cea=1 in the kernel command line i still get a lock up, but the login message is displayed on the monitor:
But the cursor on the monitor does not blink, it is a solid line. And the font is very large. According to the monitor the resolution is 640x480@60Hz (with mxc_hdmi.only_cea=1). Without mxc_hdmi.only_cea=1 and when i connect HDMI before booting the monitor reports its native resolution 1600x900@60Hz. Even when i supply the correct monitor resolution in the kernel command line together with mxc_hdmi.only_cea=1, the monitor reports 640x480. |
issues: 1) problem with HDMI sound: CPU: 2 PID: 740 Comm: alsa-sink-i.MX Not tainted 4.0.0 #21 [ 153.834550] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 153.839818] [<80015624>] (unwind_backtrace) from [<800117dc>] (show_stack+0x10/0x14) [ 153.846281] [<800117dc>] (show_stack) from [<806fea84>] (dump_stack+0x8c/0x9c) [ 153.852217] [<806fea84>] (dump_stack) from [<802843c8>] (Ldiv0+0x8/0x10) [ 153.857627] [<802843c8>] (Ldiv0) from [<802fb69c>] (sdma_prep_dma_cyclic+0x24/0x1a4) [ 153.864090] [<802fb69c>] (sdma_prep_dma_cyclic) from [<805575d4>] (hdmi_dma_trigger+0x168/0x1cc) [ 153.871590] [<805575d4>] (hdmi_dma_trigger) from [<8053ff9c>] (soc_pcm_trigger+0x9c/0x11c) [ 153.878571] [<8053ff9c>] (soc_pcm_trigger) from [<8052ba7c>] (snd_pcm_action_single+0x38/0x80) [ 153.885890] [<8052ba7c>] (snd_pcm_action_single) from [<8052c1a0>] (snd_pcm_action_lock_irq+0x3c/0x64) [ 153.893901] [<8052c1a0>] (snd_pcm_action_lock_irq) from [<8052d95c>] (snd_pcm_common_ioctl1+0x314/0xe58) [ 153.902087] [<8052d95c>] (snd_pcm_common_ioctl1) from [<8052e688>] (snd_pcm_playback_ioctl1+0x1e8/0x4bc) [ 153.910276] [<8052e688>] (snd_pcm_playback_ioctl1) from [<800f4e58>] (do_vfs_ioctl+0x414/0x608) [ 153.917685] [<800f4e58>] (do_vfs_ioctl) from [<800f5080>] (SyS_ioctl+0x34/0x5c) [ 153.923702] [<800f5080>] (SyS_ioctl) from [<8000e560>] (ret_fast_syscall+0x0/0x34)
Signed-off-by: Robert Winkler <robert.winkler@boundarydevices.com> (cherry picked from commit b3d513fd2e5344052f3ec33608dec01cdcb4004c)
Signed-off-by: Robert Winkler <robert.winkler@boundarydevices.com> (cherry picked from commit b3d513fd2e5344052f3ec33608dec01cdcb4004c)
issues: 1) problem with HDMI sound: CPU: 2 PID: 740 Comm: alsa-sink-i.MX Not tainted 4.0.0 #21 [ 153.834550] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) [ 153.839818] [<80015624>] (unwind_backtrace) from [<800117dc>] (show_stack+0x10/0x14) [ 153.846281] [<800117dc>] (show_stack) from [<806fea84>] (dump_stack+0x8c/0x9c) [ 153.852217] [<806fea84>] (dump_stack) from [<802843c8>] (Ldiv0+0x8/0x10) [ 153.857627] [<802843c8>] (Ldiv0) from [<802fb69c>] (sdma_prep_dma_cyclic+0x24/0x1a4) [ 153.864090] [<802fb69c>] (sdma_prep_dma_cyclic) from [<805575d4>] (hdmi_dma_trigger+0x168/0x1cc) [ 153.871590] [<805575d4>] (hdmi_dma_trigger) from [<8053ff9c>] (soc_pcm_trigger+0x9c/0x11c) [ 153.878571] [<8053ff9c>] (soc_pcm_trigger) from [<8052ba7c>] (snd_pcm_action_single+0x38/0x80) [ 153.885890] [<8052ba7c>] (snd_pcm_action_single) from [<8052c1a0>] (snd_pcm_action_lock_irq+0x3c/0x64) [ 153.893901] [<8052c1a0>] (snd_pcm_action_lock_irq) from [<8052d95c>] (snd_pcm_common_ioctl1+0x314/0xe58) [ 153.902087] [<8052d95c>] (snd_pcm_common_ioctl1) from [<8052e688>] (snd_pcm_playback_ioctl1+0x1e8/0x4bc) [ 153.910276] [<8052e688>] (snd_pcm_playback_ioctl1) from [<800f4e58>] (do_vfs_ioctl+0x414/0x608) [ 153.917685] [<800f4e58>] (do_vfs_ioctl) from [<800f5080>] (SyS_ioctl+0x34/0x5c) [ 153.923702] [<800f5080>] (SyS_ioctl) from [<8000e560>] (ret_fast_syscall+0x0/0x34)
Signed-off-by: Robert Winkler <robert.winkler@boundarydevices.com> (cherry picked from commit b3d513fd2e5344052f3ec33608dec01cdcb4004c)
The kernel with revision dd5bf16 boots now on the udoo quad board after disabling caam.
But i have two issues with HDMI:
The only message i get when i reconnect the cable is:
[ 257.839305] mxc_hdmi 20e0000.hdmi_video: same edid
Even when i boot without a connected HDMI cable a connect it after udoo boot, linux locks up, but without any messages.
The text was updated successfully, but these errors were encountered: