On Thu, 27 Apr 2017 08:19:19 +0100 Neil Williams codehelp@debian.org wrote:
CC:'ing Andy to see if there is extra config required to get this to work.
Andy: can you look at https://staging.validation.linaro.org/scheduler/job/174524 and see why the code does not start reading from the probe?
dmesg -T and lsusb -v output is included in the log, from inside the LXC.
On Wed, 26 Apr 2017 14:53:41 -0700 Lisa Nguyen lisa.nguyen@linaro.org wrote:
On 20 April 2017 at 02:57, Neil Williams codehelp@debian.org wrote:
On Tue, 18 Apr 2017 12:13:01 -0700 Lisa Nguyen lisa.nguyen@linaro.org wrote:
On 12 April 2017 at 08:09, Dave Pigott dave.pigott@linaro.org
https://pmwg.validation.linaro.org/scheduler/job/1405#L385
This problem is now fixed. For reference, USB devices which show a serial number which includes forward slash / will have that slash replaced by an underscore when processed through pyudev. The device dictionary has been updated for pmwg panda-01. A documentation fix is in preparation.
(BTW 2017.4 includes NFS support for panda, so I used that in my test job, your ramdisk test job will work too.)
Thanks for looking into this, Neil.
I wrote a test definition to build, install, and run the arm-probe command-line tool in LAVA, but I'm running into the error where the probe path cannot be accessed without running into the 'exclusive' error: https://pmwg.validation.linaro.org/scheduler/job/1489#L3776
OK, I've identified what is wrong here. LAVA is only adding devices from the 'usb' subsystem to the LXC but the energy probe software needs the 'tty' element instead or as well.
I've tried to use mknod to create the device within the LXC but LXC itself seems to do extra work to allow programs like minicom to use the device. In local tests, I can't get minicom to be happy with ttyUSB0 created using mknod inside the LXC, even thought the device looks the same as it is outside the LXC. Using lxc-device add works with minicom. (I'm testing with a usb serial device connected to a BBB rather than an energy probe but I'm hoping the energy probe code is essentially doing the same operations as minicom.)
So this will need a code change (which I've already prepared) to find the tty device node and pass that to lxc-device add. We are looking to release 2017.5 relatively soon - once we have had time to do full testing on staging after the much needed reorganisation of staging.validation.linaro.org. (The re-org includes the provision of devices with energy probes attached, so we can include checks on this functionality in future releases.)
https://staging.validation.linaro.org/scheduler/job/174516#results_0_find-pr...
In a manual setting, I expect to see output similar to this:
# configuration: config-panda-lab # config_name: pandaboard # trigger: 0.400000V (hyst 0.200000V) 0.000000W (hyst 0.200000W) 400us Configuration: pandaboard # date: Wed, 26 Apr 2017 22:47:59 +0100 # host: pmwg-server-01.pmwglab #
- /dev/serial/by-id/usb-NXP_SEMICOND_ARM_Energy_Probe_S_NO44440001-if00
The /dev/serial/by-id/ symlink is not being created automatically but even creating that within the test, I cannot get the supplied configuration to work.
+ arm-probe -C ../config -l 10 -x Configuration: pandaboard done all capture exited # configuration: ../config # config_name: pandaboard # trigger: 0.400000V (hyst 0.200000V) 0.000000W (hyst 0.200000W) 400us # date: Wed, 17 May 2017 14:58:48 +0100 # host: lxc-aep-test-174524 # + set +x <LAVA_SIGNAL_ENDRUN 2_arm-probe 174524_1.7.4.9>
https://staging.validation.linaro.org/scheduler/job/174524#L5766
Starting... sending start to 0 # VDD_ALL VDD ROOT #ff0000 SoC # # time VDD(V) VDD(A) VDD(W) 0.000500 5.19 0.0994 0.51568 0.000600 5.19 0.0704 0.36538 0.000700 5.19 0.0994 0.51538 0.000800 5.19 0.0764 0.39608 0.000900 5.20 0.0654 0.33967 0.001000 5.19 0.0934 0.48444 0.001100 5.19 0.0754 0.39097 0.001200 5.19 0.0734 0.38052 ... ...
However, I was able to verify that the LXC detected the probe by writing an inline test definition to use the lsusb command: https://pmwg.validation.linaro.org/scheduler/job/1489#L2049
https://staging.validation.linaro.org/scheduler/job/174524#L2079
The only thing which can be done at this stage is to pull staging-panda-03 out of the lab and I'll have to interrogate it on my desk.