Bug 13701

Summary: intermittent race in runtime parse logs failure in X on qemux86-64
Product: [Runtime] System Startup Reporter: Richard Purdie <richard.purdie>
Component: system-startupAssignee: Anuj Mittal <anuj.mittal>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Medium+ CC: akuster, kevin.tian, randy.macleod, tim.orling
Version: unspecified   
Target Milestone: 3.3 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Richard Purdie 2019-12-11 15:45:17 UTC 
https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/244

Started HTTPService on 192.168.7.1:40861
Test run when enable usrmege
Stopped HTTPService on 192.168.7.1:40861
Not appropiate for systemd image
Test requires opkg to be installed
Traceback (most recent call last):
  File "/home/pokybuild/yocto-worker/qemux86-alt/build/meta/lib/oeqa/core/decorator/__init__.py", line 36, in wrapped_f
    return func(*args, **kwargs)
  File "/home/pokybuild/yocto-worker/qemux86-alt/build/meta/lib/oeqa/runtime/cases/parselogs.py", line 378, in test_parselogs
    self.assertEqual(errcount, 0, msg=self.msg)
AssertionError: 1 != 0 : Log: /home/pokybuild/yocto-worker/qemux86-alt/build/build/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/target_logs/Xorg.0.log
-----------------------
Central error: [     9.357] failed to find screen to remove
***********************
[     9.131] (**) ImExPS/2 Generic Explorer Mouse: (accel) selected scheme none/0
[     9.131] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[     9.131] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[     9.131] (II) event3  - ImExPS/2 Generic Explorer Mouse: is tagged by udev as: Mouse
[     9.132] (II) event3  - ImExPS/2 Generic Explorer Mouse: device is a pointer
[     9.132] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
[     9.132] (II) No input driver specified, ignoring this device.
[     9.132] (II) This device may have been added with another device file.
[     9.356] (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:02.0/drm/card0 /dev/dri/card0
[     9.357] xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[     9.357] failed to find screen to remove
[     9.360] (II) config/udev: Adding input device QEMU QEMU USB Tablet (/dev/input/mouse0)
[     9.360] (II) No input driver specified, ignoring this device.
[     9.360] (II) This device may have been added with another device file.
[     9.362] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
[     9.362] (II) No input driver specified, ignoring this device.
[     9.362] (II) This device may have been added with another device file.
[     9.362] (II) config/udev: removing device AT Translated Set 2 keyboard
[     9.362] (II) event1  - AT Translated Set 2 keyboard: device removed
[     9.364] (II) UnloadModule: "libinput"
[     9.364] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event1)

***********************
1 errors found in logs.

Stdout:
Machine information: 
*******************************
Machine name: qemux86
CPU:  Intel(R) Core(TM)2 Duo CPU     T7700  @ 2.40GHz
Arch: i686
Physical cores: 1
Logical cores: 1
*******************************
Comment 2 Anuj Mittal 2020-02-24 05:23:25 UTC 
It looks like this is specific to altcfg images. Perhaps happening because of some interaction between the systemd services we start/stop while testing. Will try to reproduce locally.
Comment 3 Anuj Mittal 2020-04-15 17:34:09 UTC 
I have not been able to reproduce this. Pushing to 3.2.
Comment 4 Randy MacLeod 2020-04-15 18:45:35 UTC 
Anuj, M+ defects should have a specific milestone target. Since this is difficult to reproduce, I picked M2. Fee free to adjust. -- Randy
Comment 5 Anuj Mittal 2020-10-05 18:24:13 UTC 
I have not been able to reproduce this.
Comment 6 Anuj Mittal 2021-02-23 04:55:12 UTC 
Looks like we have not seen this for over an year now on any of the supported branches. Should we close this?
Comment 7 Randy MacLeod 2021-02-23 18:52:57 UTC 
Not able to reproduce.