Bug 3936

Summary: [beagleboard xM] Some error message with usbhs_omap in dmesg
Product: [Build System, Metadata & Runtime] BSPs Reporter: Yi Zhao <yi.zhao>
Component: bsps-meta-yoctoAssignee: Kevin Hao <kexin.hao>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, bruce.ashfield, dvhart, kexin.hao, liang.li2, ning.zhang, ross.burton, simarpreet.singh, yi.zhao
Version: 1.4   
Target Milestone: Future   
Hardware: Beagleboard   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
1.6 M3 final dmesg Beagleboard xM rev C output without and with fixes. none

Description Yi Zhao 2013-02-26 04:44:02 UTC
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:~# 
############
Comment 1 Bruce Ashfield 2013-02-26 20:45:37 UTC
Note: I have no hardware or cycles to look into the beagleboard issues. So they
are a stretch for 1.4.
Comment 2 Bruce Ashfield 2013-02-28 14:05:39 UTC
I'm putting my name down as a placeholder for this, but a resource to debug it needs
to be identified.
Comment 3 Ning Zhang 2013-07-16 10:07:09 UTC
When i tested on 1.5 latest image, the dmesg error disappeared. 
Poky: master:a63229917a5708de2d161aba0d67168ce0da6365
Comment 4 Simarpreet Singh 2013-08-15 02:01:53 UTC
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
Comment 5 Simarpreet Singh 2013-08-16 15:16:55 UTC
*** Bug 4979 has been marked as a duplicate of this bug. ***
Comment 6 Bruce Ashfield 2013-10-09 00:32:41 UTC
is this happening with the 3.10 kernel ?
Comment 7 Yi Zhao 2013-10-15 10:00:48 UTC
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
################
Comment 8 Yi Zhao 2013-11-22 06:23:04 UTC
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
Comment 9 Yi Zhao 2013-12-19 09:02:44 UTC
This issue still exists in 1.5.1 rc2:

################
root@beagleboard:~# dmesg | grep error
[    1.428588] omapfb: probe of omapfb failed with error -22
################
Comment 10 Bruce Ashfield 2014-01-15 01:50:19 UTC
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.
Comment 11 Kevin Cribbs 2014-03-20 00:31:53 UTC
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.
Comment 12 Bruce Ashfield 2014-05-21 14:57:18 UTC
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.
Comment 13 Kevin Hao 2014-06-11 07:23:03 UTC
There is no such errors in the 3.14 kernel on beaglebone black board.