Bug 9406

Summary: dmesg test_parseLogs failed corei7-64 on NUC error BAR 14 and 15
Product: [Build System, Metadata & Runtime] BSPs Reporter: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Component: bsps-meta-intelAssignee: David Rodriguez <david.israelx.rodriguez.castellanos>
Status: RESOLVED NOTABUG QA Contact: David Rodriguez <david.israelx.rodriguez.castellanos>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, california.l.sullivan, jose.perez.carranza, juan.fernandox.ramos.frayle
Version: 2.1   
Target Milestone: 2.2   
Hardware: NUC   
OS: Multiple   
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 Flags
logs
none
logs minnow none

Description Francisco Pedraza 2016-04-06 20:27:00 UTC 
Created attachment 3103 [details]
logs

STATUS: FAILED
Commit f4f1d206f4ebafcde18c96c88a1bfc4ab7b0c119
ENVIRONMENT: COREI7-64 on NUC meta-intel
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 OUTCOME: 
  
No errors or fails should be present in logs

ACTUAL OUTCOME:
The following error messages are displayed:
Central error: [    0.358942] pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]

Central error: [    0.700281] [drm] failed to retrieve link info, disabling eDP

Central error: [    0.358919] pci 0000:00:1c.3: BAR 14: failed to assign [mem size 0x00200000]

Central error: [    0.359030] pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]

Central error: [    0.359007] pci 0000:00:1c.0: BAR 14: failed to assign [mem size 0x00200000]

Central error: [    1.806895] sdhci-acpi 80860F16:00: failed to setup card detect gpio

Central error: [    0.358942] pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]

Central error: [    0.700281] [drm] failed to retrieve link info, disabling eDP

Central error: [    0.358919] pci 0000:00:1c.3: BAR 14: failed to assign [mem size 0x00200000]

Central error: [    0.359030] pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]

Central error: [    0.359007] pci 0000:00:1c.0: BAR 14: failed to assign [mem size 0x00200000]

Central error: [    1.806895] sdhci-acpi 80860F16:00: failed to setup card detect gpio

Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    0.358919] pci 0000:00:1c.3: BAR 14: failed to assign [mem size 0x00200000]

Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    1.806895] sdhci-acpi 80860F16:00: failed to setup card detect gpio

Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    0.359007] pci 0000:00:1c.0: BAR 14: failed to assign [mem size 0x00200000]

Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    0.358942] pci 0000:00:1c.3: BAR 15: failed to assign [mem size 0x00200000 64bit pref]


Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    0.359030] pci 0000:00:1c.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]

Central error: Feb 26 11:56:38 intel-corei7-64 kernel: [    0.700281] [drm] failed to retrieve link info, disabling eDP

Similar to this one: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7897
Comment 1 Saul Wold 2016-04-07 15:29:27 UTC 
This could be an older firmware issue, can you confirm you have the latest firmware installed on the NUC.
Comment 2 Francisco Pedraza 2016-04-11 19:34:10 UTC 
(In reply to comment #1)
> This could be an older firmware issue, can you confirm you have the latest
> firmware installed on the NUC.

Hi Saul,
This was tested on LAVA server I cannot confirm which firmware is installed on it.
Comment 3 Francisco Pedraza 2016-04-11 19:35:53 UTC 
This issue is also reproducible on corei7-64 on MinnowMax64bit - core-image-sato-sdk.
commit: f4f1d206f4ebafcde18c96c88a1bfc4ab7b0c119. Attached you can find logs as well.
Comment 4 Francisco Pedraza 2016-04-11 19:36:21 UTC 
Created attachment 3114 [details]
logs minnow
Comment 5 Alexandru Georgescu 2016-04-12 13:47:12 UTC 
On a quick look, this seems to be a duplicate of bug 7897. Please investigate and if so, mark this as duplicate and reopen bug 7897.

Thanks!
Comment 6 California Sullivan 2016-04-13 17:57:45 UTC 
Interesting!

This is expected the the MinnowBoard MAX/Turbot and was thought to be a firmware issue, but this is the first time I have heard of it being seen on a NUC! Seeing it on another platform would give us another data point and finally figure out what is wrong.

For now I will see if I can reproduce the bug on my NUC here.
Comment 7 California Sullivan 2016-04-15 18:16:34 UTC 
I cannot reproduce the BAR error messages on the NUC6 at my desk.

Which NUC board and what firmware version was this tested on?
Comment 8 Francisco Pedraza 2016-04-18 21:30:34 UTC 
(In reply to comment #7)
> I cannot reproduce the BAR error messages on the NUC6 at my desk.
> 
> Which NUC board and what firmware version was this tested on?

Hi,
This is the NUC MODEL: "D5425WYK"
Comment 9 Francisco Pedraza 2016-04-25 20:27:22 UTC 
As the asked details were provided.
Comment 10 California Sullivan 2016-04-27 17:26:06 UTC 
Moving to 2.1.1 as we are past the windoq for 2.1.
Comment 11 California Sullivan 2016-07-20 18:10:41 UTC 
I have still been unable to reproduce this error on the NUC, only MinnowBoard Max/Turbot.
Comment 12 California Sullivan 2016-08-19 19:55:46 UTC 
David, can you confirm whether this still occurs on the NUC?

I have been unable to reproduce this on a NUC locally and on the MinnowBoard Max/Turbot it is an expected (and whitelisted) error message.

Thanks.
Comment 13 David Rodriguez 2016-08-25 17:24:31 UTC 
In NUC6i5SYH with meta-intel-2.2_M2: a3cad8f0e0db9b2ad62ce0f2f1b0234cb9192f56
I was also unable to reproduce. Confirmed and Closing for NUC.