Laptop very slow (in excess of 5 minutes) to respond after Suspend

Hi there,

My laptop is very slow to respond, like about 5 minutes, after being hibernated for a long time.

If it is just put to 'Sleep' then it is almost instant likewise if it is suspended (hibernated) for less than a day or so then again it is instant once the Unlock screen appears.

I believe the drivers are up to date etc.

Thanks,

Ian.

So it resumes instantly if it's been with the lid closed for a short period of time but takes forever if overnight or something?

I think that that is relatively normal. Suspend requires power and if the battery gets too low it will have to truly hibernate which takes a lot longer to wake up from. And with the insanely slow laptop hard drives may take a LOT longer than a desktop would even.

I don;t know what's normal for a laptop myself as I always turn it off unless I'm just coming back in 5 minutes. I don;t trust suspend to actually survive if the battery gets low myself

Hi,

If I suspend it i.e. hibernate I realise the startup will be longer than standby.

When it is hibernated to disk for short periods such as a few hours or overnight it's normally fine. The problem is that after it has been hibernated for more than a day or so it takes a long time to respond.

E.g.

Hibernate the laptop and then resume it a few hours later - the resume loads the saved state from disk and shows the welcome screen. I can then unlock it and immediatley begin using it with no lag etc on the open applications

Hibernate the laptop and then resume it a couple of days later - the resume again loads the saved state from disk and shows the welcome screen. It is a little slower to accept my fingerprint to unlock it but then when the desktop appears nothing responds for anything up to 5 minutes. By nothing responds the mouse pointer will not appear when the mouse is moved the keyboard has no effect such as pressing the Windows key or any other normal combination.

Does that make sense?

Thanks,

Ian

Ok, so at the desktop it really should be running...

That is strange, it's like the large change in date is causing some driver or service to go out to lunch :/

Could be av or possibly something to do with networking, or maybe some sync software? Just wild guesses, something that has some sort of problem with the clock suddenly changing forward for days right in the middle of it running.

I guess if you really wanted to track it down, I'd start temp disabling things that you have running one at a time till the problem goes away (But with a 2+ day turnaround, that could take a while!)