| Summary: | Parselogs: Bluez errors in Corei7_64 LSB | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Lucian Musat <georgex.l.musat> |
| Component: | connectivity | Assignee: | Saul Wold <sgw> |
| Status: | VERIFIED WONTFIX | QA Contact: | Cristina Agurida <cristina-danielax.agurida> |
| Severity: | normal | ||
| Priority: | Medium | CC: | alexandru.c.georgescu, cristian.iorga, dvhart, meta.mr.watcher, meta.watcher, Qi.Chen |
| Version: | 1.8 | ||
| Target Milestone: | 1.8.1 | ||
| Hardware: | NUC | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Found by QA test) |
| Verified: | Documentation change: | Don't know | |
This looks to be a generic bluez / dbus issue, I could reproduce this with a genericx86-64 so I am reassigning this to Cristi. Investigation started. On the latest master, with a Baytrail based NUC (Bluetooth adapter is recognized and drivers/firmware are loaded for it), I am unable to reproduce the error. Bluetooth is functional and the BT stack is also functional, hcitool scan found my phone (Meek). In dmesg there are no dbus errors (of any kind). poky top commit: 8ef99a00dc75c6eed87aa1bc1528614a2a27eddf meta-intel top commit: 2fafedaa4ae900f82eed572860114b8baa9b36e6 Can QA retest? Also, I would like to see what is happening if this gets re-tested on a machine that does not have at all Bluetooth and on one where it is present, but not functional. See logs and info below: root@intel-corei7-64:/var/log# root@intel-corei7-64:/var/log# ls -lia 14719 drwxr-xr-x 3 root root 180 Jun 18 18:04 . 12897 drwxrwxrwt 4 root root 80 Jun 18 18:04 .. 16442 drwxr-xr-x 2 root root 60 Jun 18 18:04 ConsoleKit 14985 -rw-r--r-- 1 root root 14659 Jun 18 18:04 Xorg.0.log 14838 -rw-r----- 1 root root 3418 Jun 18 18:04 boot 16019 -rw-r--r-- 1 root root 0 Jun 18 18:04 boot~ 14837 -rw-r--r-- 1 root root 50850 Jun 18 18:04 dmesg 15130 -rw-r--r-- 1 root root 81929 Jun 18 18:06 messages 14761 -rw-rw-r-- 1 root root 3456 Jun 18 18:06 wtmp root@intel-corei7-64:/var/log# grep -ris blue * dmesg:[ 1.119959] Bluetooth: Core ver 2.20 dmesg:[ 1.128938] Bluetooth: HCI device and connection manager initialized dmesg:[ 1.136037] Bluetooth: HCI socket layer initialized dmesg:[ 1.141492] Bluetooth: L2CAP socket layer initialized dmesg:[ 1.147155] Bluetooth: SCO socket layer initialized dmesg:[ 8.417291] Bluetooth: hci0: read Intel version: 370710018002030d00 dmesg:[ 8.587168] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq dmesg:[ 8.885265] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 1.119959] Bluetooth: Core ver 2.20 messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 1.128938] Bluetooth: HCI device and connection manager initialized messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 1.136037] Bluetooth: HCI socket layer initialized messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 1.141492] Bluetooth: L2CAP socket layer initialized messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 1.147155] Bluetooth: SCO socket layer initialized messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 8.417291] Bluetooth: hci0: read Intel version: 370710018002030d00 messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 8.587168] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq messages:Jun 18 18:04:53 intel-corei7-64 user.info kernel: [ 8.885265] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated root@intel-corei7-64:/var/log# rfkill unblock bluetooth root@intel-corei7-64:/var/log# hciconfig hci0 up root@intel-corei7-64:/var/log# hcitool scan Scanning ... 38:0A:94:B1:22:06 Meek root@intel-corei7-64:/var/log# root@intel-corei7-64:/var/log# uname -a Linux intel-corei7-64 3.19.5-yocto-standard #1 SMP PREEMPT Thu Jun 18 20:52:39 EEST 2015 x86_64 GNU/Linux root@intel-corei7-64:/var/log# dmesg | grep dbus root@intel-corei7-64:/var/log# hcitool dev Devices: hci0 AC:7B:A1:93:C4:3D root@intel-corei7-64:/var/log# root@intel-corei7-64:/var/log# grep -ris dbus * boot:Thu Jun 18 18:04:52 2015: dbus. messages:Jun 18 18:04:54 intel-corei7-64 daemon.notice dbus[1087]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) messages:Jun 18 18:04:54 intel-corei7-64 daemon.notice dbus[1087]: [system] Successfully activated service 'org.freedesktop.ConsoleKit' It appears the NEEDINFO is directed to QA. Re-tested this with the newer NUC we have in the lab and the error does not appear. Will retest with an older version of NUC. Retested with latest version of intel-corei7-64-lsb on NUC (DC3217IYE model) and the issue cannot be reproduced. Setting this as WORKSFORME as per last two comments. If the error reappears we can re-open this. As per last comments set this issue as verified. This issue appears again on 1.8.1: b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0 release, on MinnowMax and NUC. It was tested with genericx86 and genericx86-64 for LSB core-image-lsb-sdk images. This error appears in /var/log//daemon.log: genericx86 dbus[809]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1 This won't be fixed in 1.8.1. This issue is fixed in the upcoming 2.0 release. Basically, what is happening, is that the BlueZ stack is active, but some basic support from Linux kernel is needed and missing in 1.8.1, and BlueZ won't start correctly. As per last comment set this issue as "VERIFIED WONTFIX" |
meta-intel : f9738ec19d3b2864c0bd71b9bb3418d16e922a12 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 poky : fido-13.0.0 Yocto 1.8.rc1 image type core-image-sato-sdk target intel-corei7-64-lsb machine NUC STATUS: FAILED BUILD: Initial default ENVIRONMENT: corei7 on NUC 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: This error was found by the log parser: May 14 22:58:23 intel-corei7-64 dbus[862]: [system] Activated service 'org.bluez' failed: Launch helper exited with unknown return code 1