| Summary: | BeagleBone Black errors in logs | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Lucian Musat <georgex.l.musat> |
| Component: | bsps-runtime | Assignee: | Kevin Hao <kexin.hao> |
| Status: | VERIFIED WONTFIX | QA Contact: | Lucian Musat <georgex.l.musat> |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandru.c.georgescu, bluelightning, dvhart, yi.zhao, yp.kernel.watcher, yp.watcher |
| Version: | 1.7 | ||
| Target Milestone: | 1.9 | ||
| Hardware: | BeagleBone | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) |
| Verified: | Documentation change: | Don't know | |
|
Description
Lucian Musat
2014-10-16 08:04:35 UTC
Please provide build info / image / bsp / ab image URL / etc. Just dumping the error into a BZ is not sufficient to describe the problem. BeagleBone Black BSP, build ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 AB link: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4 These errors are caught by the log parser during automated runtime testing. Exact link please. Also, please update the Platform field accordingly when you submit the bug. Thanks. http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/beaglebone/ Image type is core-image-sato-sdk Also, rather than just dumping the log we should describe the issue. Not everyone has a board (I don't) and we can't see the screen to know what is happening. Does the display actually work ? Was this same issue present in any older builds ? We haven't changed anything in the kernel for the BBB, so this either an existing problem, or something that changed outside the kernel. Assigning to Lucian to answer Bruce's questions. Hello Bruce, Some time ago we added a new automated testcase that parses the logs on target machines. For now, in addition to dmesg and xorg.log it searches for all the .log files in /var/log location and parses them line by line searching for keywords like "error", "fail", "can't" etc. When such lines are found they are compared to a whitelist of know errors that are to be ignored. I am currently working on improving that list because since we implemented this test it fails a lot, mostly because the whitelists are incomplete. These errors are collected from our weekly automated tests that we do on our machines in a hardware rack. Our test automatically downloads the image from AB, installs it on the machine and runs the unit tests on it. It builds some packages locally and downloads the artifacts from the AB, like the kernel, rootfs and manifest file which it copies on the test machine. None of the test machines have screens connected to them, so of course that may lead to errors in dmesg. These errors may or may not have been present in older builds, wee see them now because of the parser that we implemented. Most likely that they were. For this particular error the environment is as follows: Build: ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 Image type: core-image-sato-sdk Machine: BeagleBone Black Link: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/beaglebone/core-image-sato-sdk-beaglebone.hddimg Errors from: dmesg log I will add Yi to the thread, since he is testing BBB regularly. Yi, can you check if you encounter the same errors as Lucian on your BBB? Until he responds, you can check his results from the 1.7_M4.rc5 buid; there are no errors attached from his test runs except bug 6665: https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3053 https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3054 (In reply to comment #8) > I will add Yi to the thread, since he is testing BBB regularly. > Yi, can you check if you encounter the same errors as Lucian on your BBB? > > > Until he responds, you can check his results from the 1.7_M4.rc5 buid; there > are no errors attached from his test runs except bug 6665: > > https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3053 > https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3054 Hi Yi, Can you help us with this issue? Thanks, Alex. (In reply to comment #9) > (In reply to comment #8) > > I will add Yi to the thread, since he is testing BBB regularly. > > Yi, can you check if you encounter the same errors as Lucian on your BBB? > > > > > > Until he responds, you can check his results from the 1.7_M4.rc5 buid; there > > are no errors attached from his test runs except bug 6665: > > > > https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3053 > > https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=3054 > > Hi Yi, > Can you help us with this issue? > > Thanks, > Alex. The error logs also exist in my board. But I'm not sure they are *real* errors. Re-assign to Kevin Hao. Kevin: Would you help us to confirm this? Thanks. Sorry for the delay. They're not actually errors. Ignore them. For "omap_hwmod: debugss: _wait_target_disable failed": This is a known issue. http://comments.gmane.org/gmane.linux.ports.arm.omap/112522 For "VGA arbiter: cannot open kernel arbiter, no multi-card support": The vga arbiter is only for some legacy vga devices. It is definitely not needed for this board. For "Cannot find any crtc or sizes - going 1024x768": It is only because that no monitor is connected to the board. Error added to whitelist: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7a4d72dc18ff4ce5b02684026ba1d564a2ab5c41 |