Bug 13098 - [2.6 RC2][Meta-Intel 10.0][BSP][Testcase 1059]: dmesg error: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Summary: [2.6 RC2][Meta-Intel 10.0][BSP][Testcase 1059]: dmesg error: platform regulat...
Status: CLOSED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-intel-corei7-64 (show other bugs)
Version: 2.6
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.6.2
Assignee: Naveen Saini
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-12-21 02:01 UTC by Sudhir Sharma
Modified: 2019-05-30 10:29 UTC (History)
3 users (show)

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


Attachments
Test image logs (1000.23 KB, text/plain)
2018-12-21 02:01 UTC, Sudhir Sharma
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sudhir Sharma 2018-12-21 02:01:28 UTC
Created attachment 4414 [details]
Test image logs

This error occurs for NUC6,NUC7,Minnowmax MTurbot 

failed test case URL.

https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1059

image information 
download the link following location
pravinsx@andromeda02.png.intel.com:/data/eyeoh7/yp_images/qa_meta-intel_10.0_thud_2.6_rc2/K4.19_image-sato-sdk-intel-corei7-64/core-image-sato-sdk-intel-corei7-64-20181214090006.hddimg

test procedure - 
https://wiki.yoctoproject.org/wiki/BSP_Test_Plan

STATUS: FAILED
BUILD: 2.6. RC1:
poky commit id - 84eecb017ef92ef36b4df730908828e54aeff85c 
IMAGE: core-image-sato-sdk_generic-x86_64
ENVIRONMENT: generic-x86_64 on nuc7

STEPS TO REPRODUCE: 
Parse dmesg log and all log files in /var/log for k
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:

error log coming
Comment 2 pavan 2019-05-30 09:58:18 UTC
We didn't observe this issue in the current release meta-intel-11.0-warrior-2.7
Comment 3 Sudhir Sharma 2019-05-30 10:29:30 UTC
We have verified issue. Hence, closing it.