Show pausing worker threads in preparation for power spike

[GoogleCodeExporter]

What steps will reproduce the problem?
1.stressapptest -s 28800

What do you see instead?
The screen will show bellow message:
Show pausing worker threads in preparation for power spike (28200 seconds 
remaining)
Resuming worker threads to cause a power spike(28185 seconds remaining)

Why it will show these messages?
It cannot finish and keep running.

What version of the product are you using? On what operating system?
1.0.6 64bit binary

Original issue reported on code.google.com by ipmit...@gmail.com on 28 Jul 2014 at 3:32

[GoogleCodeExporter]

I'm running at CentOS6.5 x64.

Original comment by ipmit...@gmail.com on 28 Jul 2014 at 3:33

[GoogleCodeExporter]

Can you specify exactly the failure mode? Does the program hang, or exit 
unexpectedly, or does the system hang, or something else? Also, can you include 
the full log? 

This pause is intended to find issues related to sudden change of load and 
power usage.

Original comment by nsanders@google.com on 28 Jul 2014 at 6:40

[GoogleCodeExporter]

The program not hang, not exit and my system not hang.
But, the program keep running over 28800 sec and no any result about pass or 
fail.

Original comment by ipmit...@gmail.com on 29 Jul 2014 at 12:00

[GoogleCodeExporter]

Did it keep printing stuff? It shoudl print a note every 10 seconds or so. 
What happens if you press ctrl-C?

Original comment by nsanders@google.com on 29 Jul 2014 at 12:37

[GoogleCodeExporter]

NO, after show "pausing worker threads in preparation for power spike", then it 
will not printing stuff.
If I press ctrl-C, it have no response. 
If I press ctrl-Z, it will exit. But I have checked my system CPU, Memory 
loading, it's still keep running...

Original comment by ipmit...@gmail.com on 29 Jul 2014 at 1:09

[GoogleCodeExporter]

Hi, sorry for bother you.
Do you have any comment?
Thank you

Original comment by ipmit...@gmail.com on 30 Jul 2014 at 1:59

[GoogleCodeExporter]

Can you build with debug and run under gdb? When stressapptest is stuck, then 
break and see where it is stuck?

I'm not able to reproduce this on Ubuntu 64bit.

Original comment by pud...@gmail.com on 30 Jul 2014 at 4:51

[GoogleCodeExporter]

Also, just to get it running, you may add 
--pause_delay 100000
which will not run any pause within the 28000s run.

Original comment by pud...@gmail.com on 30 Jul 2014 at 4:57

[GoogleCodeExporter]

Hi, how to build with debug and run under gdb? Thanks

Original comment by ipmit...@gmail.com on 30 Jul 2014 at 5:48

[GoogleCodeExporter]

Hi, do you have any updates? thank you

Original comment by ipmit...@gmail.com on 4 Aug 2014 at 12:19

[GoogleCodeExporter]

# This adds debug symbols to the build:
CXXFLAGS+=" -g" ./configure
make

# Run under gdb
gdb ./src/stressapptest
(gdb) r -M 200 -s 200 --pause_delay 10

# Break at the problem occurance
^C when stressapptest appears to be stuck

# Check thread state
(gdb) info threads
(gdb) thread apply all bt

Then paste the result here.

Original comment by nick.j.s...@gmail.com on 4 Aug 2014 at 8:41

[GoogleCodeExporter]

Hi, thanks for your help.
About Log, please refer to the attachment file.

Original comment by ipmit...@gmail.com on 5 Aug 2014 at 6:14

Attachments:

• googlestress_gdb.txt

[GoogleCodeExporter]

It looks like the "thread apply all bt" command didn't get run.. Can you wait 
until "info threads" is complete and then run the other command? 

It does appear that stressapptest is stuck.

Original comment by nsand...@chromium.org on 6 Aug 2014 at 3:24