Bug 10640 - Parselog: dmi: Firmware registration failed.
Summary: Parselog: dmi: Firmware registration failed.
Status: RESOLVED WORKSFORME
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.3 M1
Assignee: California Sullivan
QA Contact: Juan Ramos
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-11-10 15:37 UTC by Juan Ramos
Modified: 2016-12-09 19:14 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
intel-quark dmesg log (12.05 KB, application/octet-stream)
2016-11-10 15:41 UTC, Juan Ramos 		no flags Details
dmesg_output.log (33.55 KB, application/octet-stream)
2016-12-09 18:41 UTC, Juan Ramos 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramos 2016-11-10 15:37:53 UTC 
STATUS: IDLE
BUILD: meta-intel-6.0 : 6c9f6b5f70ab3ee194b2c2c6f3bd462c994848fa
ENVIRONMENT: intel-quark on Galileo v.2
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 results:
Comment 1 Juan Ramos 2016-11-10 15:41:38 UTC 
Created attachment 3535 [details]
intel-quark dmesg log
Comment 2 Juan Ramos 2016-11-10 15:42:37 UTC 
(In reply to comment #0)
> STATUS: IDLE
> BUILD: meta-intel-6.0 : 6c9f6b5f70ab3ee194b2c2c6f3bd462c994848fa
> ENVIRONMENT: intel-quark on Galileo v.2
> 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 results:

Central error: [    0.336316] amd_nb: Cannot enumerate AMD northbridges

Central error: [    0.333726] ioremap error for 0x78b8d000-0x78b8e000, requested 0x2, got 0x0

Central error: [    0.333745] dmi: Firmware registration failed.
Comment 3 California Sullivan 2016-11-15 19:31:11 UTC 
Hmm, these are whitelisted for core2, but we don't seem to have a whitelist for quark.
Comment 4 California Sullivan 2016-12-08 01:38:58 UTC 
I get an entirely different set of errors, see below:

root@intel-quark:~# dmesg | grep -iE "Error|fail|warn|unable|cannot|can\'t"
Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
stmmaceth 0000:00:14.6: stmmac_dvr_probe: warning: cannot get CSR clock
mce: Unable to init device /dev/mcelog (rc: -5)

With all but the last one being whitelisted in common-errors.

Could you provide the full dmesg log and firmware version of the Galileo?

Thanks.
Comment 5 Juan Ramos 2016-12-09 18:41:29 UTC 
Created attachment 3556 [details]
dmesg_output.log
Comment 6 Juan Ramos 2016-12-09 18:54:51 UTC 
(In reply to comment #5)
> Created attachment 3556 [details]
> dmesg_output.log

(In reply to comment #5)
> Created attachment 3556 [details]
> dmesg_output.log

Hi, the Galileo version and firmware:
 
Galileo V2 
Firmware version 1.1.0
Comment 7 California Sullivan 2016-12-09 19:14:24 UTC 
I am not seeing these errors in that dmesg log either. Marking as resolved/worksforme.