Bug 3946 - [NUC] dmesg MUX INFO call failed error
Summary: [NUC] dmesg MUX INFO call failed error
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.4
Hardware: NUC Multiple
: Medium normal
Target Milestone: 1.6
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-02-27 13:51 UTC by Alexandru Palalau
Modified: 2014-07-31 15:07 UTC (History)
4 users (show)

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

Attachments
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 Alexandru Palalau 2013-02-27 13:51:43 UTC 
Build Configuration:
BB_VERSION        = "1.17.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Unknown"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "nuc"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3+snapshot-20130227"
TUNE_FEATURES     = "m64"
TARGET_FPU        = ""
meta              
meta-yocto        
meta-yocto-bsp    = "(nobranch):7d22ef28e64de06b6238d0ef9b664c0bee6efa46"
meta-intel        
meta-nuc          = "(nobranch):150be7c8fb97ac88737f6017fdf9dd47b273bb3e"

When running the core-image-sato-sdk on the NUC, the dmesg test fails as presented below:
______________________________________________________________
root@nuc:~# dmesg |grep -i error
[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
______________________________________________________________
Comment 1 Paul Eggleton 2014-07-31 15:07:46 UTC 
Googling this, it has been fixed upstream in kernels 3.5 and later:

https://bugzilla.redhat.com/show_bug.cgi?id=846382

Accordingly I'm marking it resolved.