Central error: [3462626.485] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) *********************** [3462626.475] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [3462626.476] (II) Loader magic: 0x8275880 [3462626.476] (II) Module ABI versions: [3462626.476] X.Org ANSI C Emulation: 0.4 [3462626.476] X.Org Video Driver: 15.0 [3462626.477] X.Org XInput driver : 20.0 [3462626.477] X.Org Server Extension : 8.0 [3462626.485] (--) PCI:*(0:0:2:0) 8086:4108:8086:4108 rev 5, Mem @ 0xa0100000/1048576, 0x90000000/268435456, 0xa02c0000/262144, I/O @ 0x00003008/8 [3462626.485] (--) PCI: (0:0:3:0) 8086:8182:8086:8186 rev 2, Mem @ 0xa0200000/524288, 0x80000000/268435456, 0xa0280000/262144, I/O @ 0x00003000/8 [3462626.485] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [3462626.496] Initializing built-in extension Generic Event Extension [3462626.496] Initializing built-in extension SHAPE [3462626.496] Initializing built-in extension MIT-SHM [3462626.497] Initializing built-in extension XInputExtension [3462626.497] Initializing built-in extension XTEST [3462626.497] Initializing built-in extension BIG-REQUESTS [3462626.497] Initializing built-in extension SYNC [3462626.497] Initializing built-in extension XKEYBOARD [3462626.497] Initializing built-in extension XC-MISC [3462626.497] Initializing built-in extension XFIXES ***********************
When submitting bugs, please provide: The release The BSP The image you are using The Build Info from the beginning of the build OR the link to the image from the AB. As it is, there is not enough information to start an investigation or even triage.
Minnowboard BSP, build ccf5a4d2342c4fd40e4e0b332ea7e34e0bf175d4 AB link: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4 These errors are caught by the log parser during automated runtime testing. We use core-image-sato-sdk for all our automated testing in the HW Rack.
Exact link please, don't make me try and find the URL from a starting point and a hash. Is this on MinnowBoard v1 (the TunnelCreek E6xx version?). Please update the "Platform" field accordingly.
Hello Darren, The machine is Minnowboard (E640 Atom) http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/minnow/
So this is the image you tested? http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/minnow/core-image-sato-minnow-20141011174100.hddimg This is what I mean by a direct link to the image.
Hello Darren, This is the image: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc4/machines/minnow/core-image-sato-sdk-minnow.hddimg
Found this error on Sugarbay also. commit 9aff3a4ec058a1a1149d026ebedcc6251089fffb date 2014-11-06 image type core-image-sato-sdk target sugarbay hardware lenovo x220 Tablet http://yocto-ab-master.jf.intel.com/pub/releases/yocto-meta-intel-2.0-rc4-dizzy-1.7/machines/sugarbay/core-image-sato-sdk-sugarbay.hddimg
Darren: I appreciate this is ambiguous from the report so far however what QA need to know is whether this error message is "normal" and should be ignored, or whether this error signifies a real bug. I suspect it appears on any given image built for this hardware, the automated QA tests highlight it however.
MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform.