Long delay when resuming from hibernation

[xinhua]

I've been happy with my T60 purchase from about a year ago. It's been working reliably, and is cool and quiet.

However, there is one annoying thing: there is usually a long delay (a few minutes) when it resumes from hibernation. I keep it docked most of the time. Not sure if this matters. I also feel that the delay is shorter when resuming from hibernation while keeping the Thinkpad docked, but a bit unsure if this is a consistent behavior.

I searched the threads here, but didn't find the exact same problem brought up by someone else. I plan to carry my laptop more in the future, and this will surely become an annoying issue. Has anyone seen this problem before? Is there a solution to this problem?

My T60:
Model 2623D6U
Windows XP Pro SP2
BIOS date 6/12/2006
And, I do use wireless network all the time

Thanks in advance!

Joshua

[GomJabbar]

Here are a couple of possibilities.

This first one is of the Common Windows XP update modules included with the factory install. If you did a fresh install of Windows, it may be missing.
A hardware DEP-enabled computer may stop responding when you resume from standby or from hibernation in Windows XP Service Pack 2

Laptop Computer Reaches 100 Percent CPU Usage After You Remove It from the Docking Station

Another possibility is that it is trying to make a network connection on resume. Look in Event Viewer for clues. Start > Control Panel > Administrative Tools > Event Viewer.

[xinhua]

Hey DKB,

Thank you so much for your reply to my inquiry! I was overseas for more than a month. Sorry for the slow response.

The first two possibilities that you cited do not seem to apply in my case. I was using the factory installed copy of Windows XP on my Thinkpad, and I have the delay in resuming problem even when the laptop is docked all the time.

Your third scenario, i.e. attempting to make network connection when resuming, is an interesting one. I read about a potential problem that can be caused by Skype somewhere else. I tried to disable Skype before hibernation, and that seems to make a difference. I haven't accumulated enough evidence to declare it as the root cause yet. But this is something worth trying for others who are experiencing a similar problem.

I'll surely report back once I can conclude one way or the other after experimenting a little more, especially by checking the event log as you suggested. Thanks again for your tips.

JZ