Bug 11726 - [Testimage]Multiple errors present in dmesg_ouput.log
Summary: [Testimage]Multiple errors present in dmesg_ouput.log
Status: RESOLVED OBSOLETE
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-intel-corei7-64 (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 4.99
Assignee: yeoh ee peng
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-06-27 21:30 UTC by Juan Ramos
Modified: 2018-07-20 06:26 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
testimage_intel-corei7-64_Joule (41.94 KB, application/octet-stream)
2017-06-27 21:30 UTC, Juan Ramos
no flags Details
LOg file (526.27 KB, text/plain)
2018-07-03 09:47 UTC, nagarajagopal
no flags Details
Log file (526.27 KB, text/plain)
2018-07-03 09:50 UTC, nagarajagopal
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juan Ramos 2017-06-27 21:30:09 UTC
Created attachment 3847 [details]
testimage_intel-corei7-64_Joule

BUILD: 2.4 M1: rc1-54d18a7efe307b9fb45d64156d53b886abc3792b
ENVIRONMENT: corei7-64_Joule
Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "intel-corei7-64"
DISTRO            = "poky"
DISTRO_VERSION    = "2.3"
TUNE_FEATURES     = "m64 corei7"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "HEAD:6964efddd31c479386d1643c1025bc102710392f"
meta-intel        = "HEAD:54d18a7efe307b9fb45d64156d53b886abc3792b"

STEPS TO REPRODUCE: 
  
1.-Download the intel-corei7-64 image.hddimg from:
http://yocto-ab-master.jf.intel.com/pub/releases/yocto-2.4_M1.rc1/machines/intel-corei7-64/  
2.-Setup the environment to run automated BSP image as explained in this link:
https://wiki.yoctoproject.org/wiki/Quality_Assurance_yocto_project#Steps_for_BSP_Automated_Testing

3.-bitbake core-image-sato-sdk -c testimage   


EXPECTED OUTCOME: 
  
 No errors or fails should be present in logs

ACTUAL OUTCOME:
-Central error: [    14.628] (EE) libinput: Dell KB216 Wired Keyboard: Failed to find parent device
-Central error: [    15.049] (II) failed to create input device '/dev/input/event1'.
-Central error: [    15.049] (EE) xf86OpenSerial: Cannot open device /dev/input/event1
-Central error: [    15.049] (II) opening input device '/dev/input/event1' failed (No such device).

Log attached.
Comment 1 Saul Wold 2017-06-28 15:31:22 UTC
Did the keyboard work after the X system finished initializing?

Can you try a different keyboard?
Comment 2 Juan Ramos 2017-06-28 16:23:54 UTC
(In reply to comment #1)
> Did the keyboard work after the X system finished initializing?
> 
> Can you try a different keyboard?

Keyboard and Mouse are responsive, it doesn't seem to affect the functioning.
Comment 3 Anuj Mittal 2018-05-31 03:45:46 UTC
Raj, Ee Peng, can you please try and see if this is still reproducible? I don't see this on NUC.

If this is Joule specific, we can probably close this bug now.
Comment 4 nagarajagopal 2018-07-03 09:47:16 UTC
Created attachment 4339 [details]
LOg file
Comment 5 nagarajagopal 2018-07-03 09:50:27 UTC
Created attachment 4340 [details]
Log file


 Able to reproduce issue on NUC, 
 ENVIRONMENT - Corei7 NUC
 Getting blow error,
  Central error: [    7.144969] thermal thermal_zone2: failed to read out thermal zone (-5)
  Central error: [    6.371300] udevd[429]: inotify_add_watch(6, /dev/loop0, 10) failed: No such file or directory

 Log file attached.
Comment 6 Stephen K Jolley 2018-07-06 16:15:24 UTC
It appears your question has been answered.  If not, please restate the question and place in NEEDINFO again.
Comment 7 Anuj Mittal 2018-07-09 05:42:34 UTC
These are different errors from the original bug report.

I don't get: 

Central error: [    6.371300] udevd[429]: inotify_add_watch(6, /dev/loop0, 10) failed: No such file or directory

And the thermal_zone error is probably for the wifi card/iwlwifi driver and can be ignored if wifi is working. Do you get that error in parselogs?

I am using wic image with intel-corei7-64 on NUC.

If you're able to reproduce either with parselogs/actual hardware, please give instructions that can help me reproduce this.
Comment 8 yeoh ee peng 2018-07-20 06:26:24 UTC
Closed this as we no longer have Joule.