Bug 10844

Summary: parselogs: qemux86 and x86-64 failing with message "qemux86-64 getty[728]"
Product: [Build System, Metadata & Runtime] BSPs Reporter: Jose Perez C <jose.perez.carranza>
Component: bsps-runtimeAssignee: Choong Yin Thong <yin.thong.choong>
Status: VERIFIED FIXED QA Contact: oscar lopez arandas <oscarx.lopez.arandas>
Severity: normal    
Priority: Medium CC: mikko.ylinen, oscarx.lopez.arandas, rebecca.swee.fun.chang, sgw, yp.kernel.watcher, yp.watcher
Version: 2.3   
Target Milestone: 2.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
qemux86-64
none
qemux86_log none

Description Jose Perez C 2016-12-22 14:31:52 UTC 
Created attachment 3572 [details]
qemux86-64

STATUS: FAILED
BUILD: 2.3_M1_rc1: 573c646d4cc62dcd0c230381df4940bdf314d495
ENVIRONMENT: qemux86_64-lsb
Image: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M1.rc1/machines/qemu/qemux86-64-lsb/core-image-lsb-sdk-qemux86-64.ext4

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: Dec 21 14:43:11 qemux86-64 getty[728]: tcgetattr: Input/output error^M
***********************
Dec 21 14:43:10 qemux86-64 sshd[719]: Accepted none for root from 192.168.7.1 port 50312 ssh2
Dec 21 14:43:10 qemux86-64 sshd[719]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 21 14:43:10 qemux86-64 sshd[719]: Received disconnect from 192.168.7.1 port 50312:11: disconnected by user
Dec 21 14:43:10 qemux86-64 sshd[719]: Disconnected from 192.168.7.1 port 50312
Dec 21 14:43:10 qemux86-64 sshd[719]: pam_unix(sshd:session): session closed for user root
Dec 21 14:43:10 qemux86-64 sshd[722]: Accepted none for root from 192.168.7.1 port 50314 ssh2
Dec 21 14:43:10 qemux86-64 sshd[722]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 21 14:43:11 qemux86-64 sshd[722]: Received disconnect from 192.168.7.1 port 50314:11: disconnected by user
Dec 21 14:43:11 qemux86-64 sshd[722]: Disconnected from 192.168.7.1 port 50314
Dec 21 14:43:11 qemux86-64 sshd[722]: pam_unix(sshd:session): session closed for user root
Dec 21 14:43:11 qemux86-64 getty[728]: tcgetattr: Input/output error^M
Dec 21 14:43:11 qemux86-64 sshd[726]: Accepted none for root from 192.168.7.1 port 50316 ssh2
Dec 21 14:43:11 qemux86-64 sshd[726]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 21 14:43:11 qemux86-64 sshd[726]: Received disconnect from 192.168.7.1 port 50316:11: disconnected by user
Dec 21 14:43:11 qemux86-64 sshd[726]: Disconnected from 192.168.7.1 port 50316
Dec 21 14:43:11 qemux86-64 sshd[726]: pam_unix(sshd:session): session closed for user root
Dec 21 14:43:11 qemux86-64 sshd[732]: Accepted none for root from 192.168.7.1 port 50318 ssh2
Dec 21 14:43:11 qemux86-64 sshd[732]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 21 14:43:12 qemux86-64 sshd[732]: Received disconnect from 192.168.7.1 port 50318:11: disconnected by user
Dec 21 14:43:12 qemux86-64 sshd[732]: Disconnected from 192.168.7.1 port 50318
Dec 21 14:43:12 qemux86-64 sshd[732]: pam_unix(sshd:session): session closed for user root
Comment 1 Saul Wold 2017-01-04 00:53:35 UTC 
Can you confirm that this was run with standard testimage and parselogs?  Is this reproducible?  I can see this when I run manually without, but that is due to the fact that we do not setup a second serial device via tcpserial=30001.
Comment 2 Jose Perez C 2017-01-04 13:42:40 UTC 
(In reply to comment #1)
> Can you confirm that this was run with standard testimage and parselogs?  Is
> this reproducible?  I can see this when I run manually without, but that is
> due to the fact that we do not setup a second serial device via
> tcpserial=30001.

Yes it was executed with standard testimage and parselogs 

$bitbake core-image-sato-sdk -c testimage
Comment 3 Saul Wold 2017-03-16 19:14:25 UTC 
This is more of an annoyance, but we need to improve the start_getty script in sysvinit-inittab to try and determine if a getty is really there, maybe by looking into /proc or /sys to see if the device exists.
Comment 4 Choong Yin Thong 2017-04-07 03:04:49 UTC 
Can you try execute this test case again with latest OE-core? I cannot reproduce with latest OE-Core code. If not make change on test case that's mean the root cause already been fixed a long from 2.3_M1 to current 2.3_M3.
Base on file meta/lib/oeqa/runtime/parselogs.py the nearest commit is on Dec 9, 2016 and meta/lib/oeqa/runtime/kernelmodule.py nearest commit is Jun 14, 2016

core-image-sato-sdk-1.0-r0 do_testimage: RESULTS - kernelmodule.KernelModuleTest.test_kernel_module - Testcase 1541: PASSED

core-image-sato-sdk-1.0-r0 do_testimage: RESULTS - parselogs.ParseLogsTest.test_parselogs - Testcase 1059: PASSED
Comment 5 Jose Perez C 2017-04-07 12:39:49 UTC 
This is not happening on latest test on 2.3 M3 rc2.

commit : 415b72ffcbd26e5f3664370d8b2a9b8105fb6342
Comment 6 Saul Wold 2017-04-10 17:35:47 UTC 
This may not fail with qemux86 any further, but we still have a similar failure in intel-corei7-64.  I am not completely sure what changed to make it succeed, ultimately that would be good to know.

I can reproduce this on qemux86 by adding a 3 tty to the SERIAL_CONSOLES (adding ttyS2).
Comment 7 oscar lopez arandas 2017-06-22 15:56:22 UTC 
STATUS: pass
BUILD: 2.4 M1 rc1: 6964efddd31c479386d1643c1025bc102710392f"
ENVIRONMENT: qemux86 and qemux86-64
 
 Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.3"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "master:6964efddd31c479386d1643c1025bc102710392f"

EXPECTED OUTCOME: 
   No errors or fails should be present in logs
ACTUAL OUTCOME
    No errors or fails should be present in logs
 
Full log attached.
Comment 8 oscar lopez arandas 2017-06-22 16:01:01 UTC 
Created attachment 3841 [details]
qemux86_log