Bug 9271 - dmi firmware registration failed, ioremap error on 32 bit MinnowBoard
Summary: dmi firmware registration failed, ioremap error on 32 bit MinnowBoard
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: 2.1
Hardware: MinnowBoard Max x86
: Medium minor
Target Milestone: 2.2
Assignee: California Sullivan
QA Contact: Juan Ramos
URL: http://autobuilder.yoctoproject.org/p...
Whiteboard:
: 10021 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-03-16 00:33 UTC by Francisco Pedraza
Modified: 2017-06-12 18:59 UTC (History)
3 users (show)

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


Attachments
do_testimage.24405 (20.29 KB, application/octet-stream)
2016-03-16 00:36 UTC, Francisco Pedraza
no flags Details
Test_parselogs-genericx86 - on MMAX32bit (20.42 KB, application/octet-stream)
2016-07-07 21:44 UTC, David Rodriguez
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Francisco Pedraza 2016-03-16 00:33:40 UTC
STATUS: FAILED
BUILD: 2.1_M3.RC1: 8debfea81e69d038bd2d56314b272cb74f5582ed
ENVIRONMENT: genericx86 - on MMAX32bit
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:

Central error: [00.335659] ioremap error for 0x78da4000-0x78da5000, requested 0x2, got 0x0
Central error: [ 0.335677] dmi: Firmware registration failed.
Comment 1 Francisco Pedraza 2016-03-16 00:36:37 UTC
Created attachment 3032 [details]
do_testimage.24405
Comment 2 California Sullivan 2016-03-28 16:35:55 UTC
I'm looking into this. From the error message it appears to be a MinnowBoard firmware issue, but I'm not certain.
Comment 3 California Sullivan 2016-05-05 21:31:20 UTC
Moving to 2.2. As it does not appear to impact functionality I am lowering its priority as well.
Comment 4 David Rodriguez 2016-07-07 21:42:30 UTC
Same result found on:

BUILD: 2.1.1.RC1: 98c57bb512ea6790db8604fcf0b88c81651d2ab4 
ENVIRONMENT: genericx86 - on MMAX32bit

log file attached.
Comment 5 David Rodriguez 2016-07-07 21:44:33 UTC
Created attachment 3275 [details]
Test_parselogs-genericx86 - on MMAX32bit
Comment 6 California Sullivan 2016-07-25 21:09:44 UTC
*** Bug 10021 has been marked as a duplicate of this bug. ***
Comment 7 California Sullivan 2016-08-19 19:52:37 UTC
This error has been occurring since the 4.4 kernel was introduced with no apparent functionality loss and no fix in sight. Therefore I whitelisted the error.

See here: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a9b2c9d83aa7b1c6eb7a8c5cb929518c26ad75ce
Comment 8 Juan Ramos 2016-12-23 17:33:03 UTC
This bug is present in commit 573c646d4cc62dcd0c230381df4940bdf314d495 with minnowmax32 in core-image-sato-sdk-genericx86.wic
Comment 9 David Lopez Barriba 2017-06-12 18:59:12 UTC
I found this in fe7fb002216f7886d49942333ea6d8592339bb05 with minnowmax32 in core-image-sato-sdk-genericx86