Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130220-2 Git rev: master:7d22ef28e64de06b6238d0ef9b664c0bee6efa46 When system boot up, there are some error messages in dmesg: ########### root@beagleboard:~# dmesg|grep error usbhs_omap usbhs_omap: xclk60mhsp1_ck set parentfailed error:-22 usbhs_omap usbhs_omap: xclk60mhsp2_ck set parentfailed error:-22 root@beagleboard:~# ############
Note: I have no hardware or cycles to look into the beagleboard issues. So they are a stretch for 1.4.
I'm putting my name down as a placeholder for this, but a resource to debug it needs to be identified.
When i tested on 1.5 latest image, the dmesg error disappeared. Poky: master:a63229917a5708de2d161aba0d67168ce0da6365
This issue should be closed as was a known issue upstream for which a patch has already been submitted. Upstream: https://lkml.org/lkml/2013/1/16/297
*** Bug 4979 has been marked as a duplicate of this bug. ***
is this happening with the 3.10 kernel ?
For 1.5 M5 rc6, the usb doesn't work at all. Please see bug 5211. There is no usbhs_omap error in dmesg but have another error for omapfb: ################ # dmesg|grep error [ 1.392852] omapfb: probe of omapfb failed with error -22 ################
Fro 1.6 20131119 build, the usb can work. There is no usbhs_omap error in dmesg but a error for omapfb. ################ root@beagleboard:~# dmesg | grep error [ 1.428588] omapfb: probe of omapfb failed with error -22 ################ git rev: master/215dab864e7cf74394840621ad0754db593708f1
This issue still exists in 1.5.1 rc2: ################ root@beagleboard:~# dmesg | grep error [ 1.428588] omapfb: probe of omapfb failed with error -22 ################
Marking the bug as accepted, but since I don't have a display to test, I'll have to find someone to look at this in detail.
Created attachment 1839 [details] 1.6 M3 final dmesg Beagleboard xM rev C output without and with fixes. Summary: The originally reported usbhs_omap errors are fixed and a simple fix can eliminate the omapfb problem mentioned. These are the errors that I notice in an unmodified 1.6 M3 build tested on a Beagleboard xM rev C: ... omapfb omapfb: no driver for display: dvi omapfb omapfb: failed to find default display omapfb omapfb: failed to setup omapfb omapfb: probe of omapfb failed with error -22 ... unable to find transceiver HS USB OTG: no transceiver configured musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517 platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral ... Adding the "test fix" layer I created for https://bugzilla.yoctoproject.org/show_bug.cgi?id=5182 eliminates the omapfb errors above (by setting CONFIG_PANEL_TFP410=y). Adding the "test fix" layer I created for https://bugzilla.yoctoproject.org/show_bug.cgi?id=5211 eliminates the musb errors above. I don't see any errors in a 1.6 M3 Beagleboard build (run on a Beagleboard xM rev C) when the "test fix" layers identified above are included in the build.
Is this being seen with the 3.14 kernel as well ? For beagleboard support in general 3.14 has many fixes and is a better starting point to look into issues like this. Note: you need to use http://git.yoctoproject.org/cgit.cgi/meta-yocto-bsp-old/ to enable the beagleboard BSPs.
There is no such errors in the 3.14 kernel on beaglebone black board.