Dealing with / Escalating an Easy Serv Issue - Advice?

[kjarrett]

IBM now says my T30 hibernation power loss is "normal" ... riiiiiiiiiiiiiight.

I'm on the phone with a technician right now. I've explained everything, in detail, I've got the documentation to prove my point(s). Fortunately the guy is cool, not at all a jerk, but he's sticking to his guns, and it looks like I'm SOL.

I am now being told that it is "normal" for a T30 to lose 3-4% of its battery power when in hibernation mode. No Thinkpad I have ever owned has lost more than an inconsequential amount of power during hibernation.

This can't be right, when shut down (or with the AC adapter plugged in) the system loses less than .1 Wh in a 24 hour period. So, how can a 3-4% loss in hibernation be considered normal?

Update ... just got done speaking with the tech (Russell). He spoke to a L2 tech and they are only willing to offer me another battery to "resolve" the problem.

At this point it has been repaired once for the problem and it's still not fixed.

What are my options? Any thoughts?

TIA,

-kj-

p.s. I still love my T30!!!

[lvlolvlo]

perhaps they're getting confused between hibernate and sleep/suspend. Hibernate saves to hd so no power is needed to be pumped any more, you can experiment this by placing your notebook in hibernate then pulling out your battery. Sleep/suspend saves everything to your ram/hd, making it mandatory for power to pump at a minimal level to aviod data loss. i'm thinking you should try updating your power drivers, http://www.tpdrivers.com and see if that remidies the problem.

[kjarrett]

Thanks, I believe you're right about their confusion. Hibernate is supposed to be a power-off condition, while Sleep/Suspend is not, AFAIK.

Am resolving this now with IBM support (see my other thread). Just want to be sure I'm not the only one. I've got the latest PM drivers, v1.26, I just rebuilt XP on this machine from scratch last month (bare drive install).

Hopefully others will chime in here. Wouldn't be the first time a user forum brought an issue to IBM's attention.

Thanks, kj