Bug detailed descriptions(behavior, impact, etc) =========================================================== Setup the BLTK battery tool. And follow the User's guide Reproduce Steps(steps,current result, reproduce possibility) =========================================================== (1) Run the ./bltk -I (2) Wait for out of battery (3) Re-plug in the AC line (4) Check the folder "idle.results" (5) It produce err.log and work_out.log (6) It shows idle: signal 15 (Terminated) received stat.log : signal 15 (Terminated) received Test failed (7) Can't use ./bltk_report to create the test report Expected result: =========================================================== Produce the report by ./bltk_report normally.
Bltk does not have anything to do with dalston.
Hello robsta, It seems the Dalston process can't be killed. (by kill -9) Thus , when the system close to out of battery level. The machine will turn off by system instead of hardware turn off. Are there any method to test the battery life by BLTK ? Or any method to kill the dalston-power-applet ? BTW, Moblin2.0 can use BLTK to test battery life and can kill the dalston-power-applet. Thus when the system close to out of battery level , it intend to hardware turn off instead of system turn off. Ben
change the QA contact to Jingke
Hi bchou, I do not think dalston-power needs to do anything for this issue. If you kill -9 dalston, it will be restarted soon. (this is a feature in v2.1). But I suggest you to remove the dalston package to go on your test for battery. Welcome comments.
You can check if idle workload is ok by running: make check-idle
Hi Reporter, As I know, current v2.2 image does not contain dalston package at all. Could you please retest this issue? Re-assign to you for more information. Thanks!