Problem waking from hibernation - XP Pro

[Neos]

...will not re-connect - most of the time - especially after an all nighter. It also sometimes will re-boot when I put it into hibernation - but not always.

I have trying to find a fix. Would a complete kernal dump or a complete memory dump help in this at all?

Help, please. I hate to re-boot.

 

[bsobel]

Most likely it's a driver issue, I'd start by seeing if there is a drive update for your network card...

 

[SunnyD]

Are you using USB for your modem's connection to the computer?

If so - DON'T hibernate the computer.

 

[bersl2]

ACPI states S3 (suspend to RAM) and S4 (suspend to HD) are very touch-and-go. It's usually best to turn off any special peripherals. Usually it's because such drivers may not bother to save the state of the device.

 

[Neos]

Originally posted by: SunnyD
Are you using USB for your modem's connection to the computer?

If so - DON'T hibernate the computer.

Actually - I have since stopped it anyway - since I found out how much memory hibernation used.

But - yes - I am using usb. Why would I not hibernate? Just curious.

 

[Neos]

Originally posted by: bersl2
ACPI states S3 (suspend to RAM) and S4 (suspend to HD) are very touch-and-go. It's usually best to turn off any special peripherals. Usually it's because such drivers may not bother to save the state of the device.

Is the only way then to upgrade to a driver that will save the state of the device?

 

[Nothinman]

Actually - I have since stopped it anyway - since I found out how much memory hibernation used.

Technically hibernation uses no memory, because the memory is saved to disk and the machine powered off.

Is the only way then to upgrade to a driver that will save the state of the device?

Or disable the device before you hibernate and then reenable it after you resume.

 

[VirtualLarry]

Originally posted by: Nothinman

Is the only way then to upgrade to a driver that will save the state of the device?

Or disable the device before you hibernate and then reenable it after you resume.

Isn't/shouldn't that be the job of the OS? IMHO, Hibernate is still largely "broken". Perhaps these sorts of device-state issues will be fixed when more systems ship with an Intel EFI BIOS instead of the current ACPI-driven mess that MS has created.

 

[Nothinman]

Isn't/shouldn't that be the job of the OS?

No, it would be the job of the driver. The OS tells the driver "we're going to suspend" and the driver needs to respond, but not all respond properly if at all. If he manually disables the device it shouldn't have any problems.

 

[SunnyD]

Originally posted by: Neos

Originally posted by: SunnyD
Are you using USB for your modem's connection to the computer?

If so - DON'T hibernate the computer.

Actually - I have since stopped it anyway - since I found out how much memory hibernation used.

But - yes - I am using usb. Why would I not hibernate? Just curious.

USB + Hibernation causes problems with power-on/wake up on many chipsets. Some devices get the USB connection shutdown from the system when it goes into hibernate, and once the connection is shutdown, many... MANY devices never wake up until the system is power cycled.

I can't remember exactly which chipsets this affects, but I know it's a bunch. Hibernate is pure crap.

 

[Nothinman]

I can't remember exactly which chipsets this affects, but I know it's a bunch. Hibernate is pure crap.

Hibernation rocks, I use it on my laptop every day. Of course I'm using the Linux implementation.

 

[madthumbs]

If you hdd is above 137GB and you haven't installed sp1 or later, you could be getting corruption on your hdd going into hibernation due to an old atapi.sys driver. In this case you can update the driver, or install a service pack.