| Summary: | Running testimage test_parselogs failed getting the following error message failed to retrieve link info, disabling eDP on Minnowboard Max 32 and 64 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Francisco Pedraza <francisco.j.pedraza.gonzalez> | ||||||||||
| Component: | bsps-meta-yocto | Assignee: | California Sullivan <california.l.sullivan> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | David Rodriguez <david.israelx.rodriguez.castellanos> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | Undecided | CC: | benjamin.esquivel, california.l.sullivan, jose.perez.carranza | ||||||||||
| Version: | 2.1 | ||||||||||||
| Target Milestone: | 2.2 | ||||||||||||
| Hardware: | MinnowBoard Max | ||||||||||||
| OS: | x86 | ||||||||||||
| URL: | http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/machines/genericx86-lsb/core-image-lsb-sdk-genericx86.hddimg | ||||||||||||
| Whiteboard: | |||||||||||||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Found by QA test) | ||||||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Francisco Pedraza
2016-04-11 20:28:42 UTC
(In reply to comment #0) > Created attachment 3115 [details] > Logs-Genericx86-lsb-minnowboardmax32 > > Running test image test_parselogs failed getting the following error messages > Test Environment: > MACHINE: Genericx86-LSB. > HW: MinnowboardMax 32 bits. > This bug belongs to: > https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5682 test execution. > Test Case Number: > https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1059 > > Steps to Reproduce: > Parse dmesg log and all log files in /var/log for keywords like: "error" , > "failed" , "cannot", "can't" etc. > Filter out the known and invalid errors or errors that appear in certain > situations and need to be ignored. > > Expected Result: > No errors or fails should be present in logs > > Actual Result: > The following error messages are displayed: > Central error: [ 0.847542] [drm] failed to retrieve link info, disabling > eDP > > Central error: [ 0.847542] [drm] failed to retrieve link info, disabling > eDP > > Central error: Apr 7 01:57:18 genericx86 kernel: [drm] failed to retrieve > link info, disabling eDP > > > Additional Information > > meta-intel : 7d2b2f5b644a2729c75b8ecb38345c9668d2c8bb > meta-minnow : 9c965ef5252e383843d796cd8b50c61b3034b6ae > meta-qt4 : 4058b0773381f894d915ea3dfac5fe052d82a9a7 > meta-qt3 : 7d958b928a4a38a186746fabbc0d8169dd8bb3a6 > poky : 296dfbc9b3a3c0ed64b8e748c2868928b9c2aa8b > > > Attached you can find log. Adding some information: Executed on LAVA Server. Reproducible also on Genericx86-64 MinnowMax64 Image: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/machines/genericx86-lsb/core-image-lsb-sdk-genericx86.hddimg Regards What type of monitor is hooked up to, if any? This seems to indicate that either there is no monitor or it's not responding with valid eDP (Embedded DisplayPort) information. I was not able to reproduce this with the image you pointed at here. (In reply to comment #4) > What type of monitor is hooked up to, if any? This seems to indicate that > either there is no monitor or it's not responding with valid eDP (Embedded > DisplayPort) information. > > I was not able to reproduce this with the image you pointed at here. Hi Saul, If you want I can try to reproduce it again. What firmware version is present on your test platform? This isn't new, see https://bugzilla.yoctoproject.org/show_bug.cgi?id=7901 *** Bug 9465 has been marked as a duplicate of this bug. *** Created attachment 3129 [details]
logs_
(In reply to comment #6) > What firmware version is present on your test platform? > > This isn't new, see https://bugzilla.yoctoproject.org/show_bug.cgi?id=7901 MinnowBoard.MAX.I32.0084.R01 In attempting to reproduce this bug with different firmware I had the following results: MinnowBoard.MAX.I32.90.R01.bin - PASS MinnowBoard.MAX.I32.0084.R01.bin - PASS MinnowBoard.MAX.I32.080.R01.bin - PASS MinnowBoard.MAX.I32.079.R01.bin - FAIL All tests were done using the image linked in comment 3: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/machines/genericx86-lsb/core-image-lsb-sdk-genericx86.hddimg So, I am unable to reproduce the bug unless it has firmware before version 0.80. I also see that the "failed to retrieve link info, disabling eDP" error message is not present on the latest log (comment 8). Can you verify that all MinnowBoards in your test environment have version 0.80 firmware or newer? (In reply to comment #10) > In attempting to reproduce this bug with different firmware I had the > following results: > > MinnowBoard.MAX.I32.90.R01.bin - PASS > MinnowBoard.MAX.I32.0084.R01.bin - PASS > MinnowBoard.MAX.I32.080.R01.bin - PASS > MinnowBoard.MAX.I32.079.R01.bin - FAIL > > All tests were done using the image linked in comment 3: > http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1.rc1/machines/ > genericx86-lsb/core-image-lsb-sdk-genericx86.hddimg > > So, I am unable to reproduce the bug unless it has firmware before version > 0.80. > > I also see that the "failed to retrieve link info, disabling eDP" error > message is not present on the latest log (comment 8). Can you verify that > all MinnowBoards in your test environment have version 0.80 firmware or > newer? Hi Sullivan, If you want I can reproduce it again, with the same build that is described here, or if you want with the new one released today. Waiting for confirmation. Yes, if you could provide me the firmware version and a dmesg log from the same machine it would be much appreciated. Use the same image that you linked in comment 3. I do not have details of your testing platform but I suspect there are MinnowBoards with old firmware mixed in. Thank you. Created attachment 3157 [details]
dmesglogg
Created attachment 3158 [details]
log_debugging
I ran again this one, the weird situation is that the reason why I raised was not present, but another failure was found. Find attached log_debugging dmesglogg for more information. The new error looks like a USB keyboard having some issues. I've seen it quite a bit when using powered USB hubs and it likely isn't a Yocto or MinnowBoard problem. (In reply to comment #16) > The new error looks like a USB keyboard having some issues. I've seen it > quite a bit when using powered USB hubs and it likely isn't a Yocto or > MinnowBoard problem. Yes I am agree with you, I will reproduce again tomorrow with no hub connection in the same image, also with the latest image that we have. Looks like for lsb is not reproducible anymore, however for the other images it is, failed on the following execuitions for 2.1_M4.rc2: https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5812 - genericx86-64-WIC on Minnow Max 64 bit https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5761 - genericx86 on Minnow Max 32 bit https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5811 - genericx86-WIC on Minnow Max 32 bit https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5758 - genericx86-64 on Minnow Max 64 bit Just as a comment, all those executions failed on LAVA server, what can I perform from my end, is to test all of them manually using the latest image from AB and the latest poky commit. Let me know your comments. Sorry I forgot to add the firmware of the Minnow Board: For 32 bit I use: MinnowBoard.MAX.I32.0084.R01 For 64 bit I use: MinnowBoard.MAX.X64.0084.R01 Regards, As per the latest requested information was added. I have still been unable to reproduce this on a MinnowBoard with up to date firmware. I see it on NUC6, however. Tested on the original set Genericx86-lsb-minnowboardmax32 Current Master 70ccc66126552c0b9b606c7010ea6c3e737b2463 frimware version: MinnowBoard.MAX_.I32.93.R01 Bug not present thus far yet. Setting as NOTABUG. This is actually a valid bug because is reproducible on NUC 6, I did't see comment 21, setting to reopened. I think I am going to whitelist this error. This message occurs because the firmware is telling the kernel to initialize an embedded DisplayPort connection. But since the NUC doesn't use eDP and nothing is connected to it, it fails. If it was a MinnowBoard firmware issue we could get it fixed, but we have no visibility into NUC firmware. |