HP-LX195 WHS High hardware interrupts after wake up from sleep RRS feed

  • Question

  • I have a HP-LX195 windows home server which is set to sleep every day between 2AM and 7 AM. On wake up from sleep the CPU usage is triggered to 35-40%. No tasks are executing during this period and if any they add up the original usage. Using process explorer notices these CPU utilization is due to hardware interrupts. Using kernrate noticed the high usage is on intelppm.sys.

    I have determined this is due to sleep. If the server is kept running without sleep, the hardware interrupt is minimal on normal operations. But if i manually set the server to sleep and wake up, the usage triggers back to 35 or 40.

    Any advice... Thanks Raja

    Tuesday, March 30, 2010 3:52 AM

All replies

  • Honestly? Don't put your server into sleep mode if you're concerned about the interrupts.
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, March 30, 2010 4:10 AM
  • It could be a workaround, but I am not sure how that would be an answer?
    Tuesday, March 30, 2010 5:28 AM
  • I'm pretty sure if you check you'll find that they're a normal result of waking from sleep mode. So if you don't want that activity, don't create the initial condition that causes it.

    Or, as the old joke goes:

    Patient: "Doctor, it hurts when I do this (demonstrates painful activity)."

    Doctor: "Then don't do that."

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, March 30, 2010 5:37 AM
  • Thanks for your help, Please do not thread ____ if you don't have an appropriate answer. I am sure your doctor analogy would work on other stuff, not on software's. Usual activities on processor drives are driven due to some activity state not being registered or taken proper actions.


    Tuesday, March 30, 2010 5:49 AM
  • AbdSea,

    Ken is right.  If you suspend your machine, when it resumes it will have all sorts of housekeeping to do when it powers back on.  If you don't want that to happen then there are two solutions, leave it turned off or don't turn it off.  I think the latter is probably the answer.  35% cpu usage when powering back on is nothing to worry about.


    Tuesday, March 30, 2010 9:26 AM
  • Al,

    It is not a one time issue or momentary spike on CPU. CPU is in a spin lock state ever after the wake up until the box is rebooted. If it were a momentary spike, I would take the approach of ignoring. This is certainly a driver issue. Thanks :-)


    Tuesday, March 30, 2010 2:55 PM
  • I'm seeing the same problem on w7x64 - a year later! I've disabled as many services as possible, have no apps running. Once returning from sleep, CPU will spike every couple of seconds all day long until rebooted. Certainly seems as though some driver isn't waking up properly.


    Friday, May 13, 2011 2:21 PM