Ok so, my macbook pro 9,2 has three major problems in the aftermath of the spill.

PICS OF DAMAGED AREA: https://www.dropbox.com/sh/a5dwfzqs1fnto...

1. 4 keys do not work, I suspect an electrical short damaged them beyond repair. A bluetooth keyboard restores function of these keys. I might replace the oem keyboard with new keyboard. This is the least of my worries and could easily be fixed but may provide context to problem.

2. The Battery and supply of power to the laptop are malfunctioning. The laptop does not turn on with a simple press of the power button. This causes the light on the side of the case facing the users lap to light up, the fan runs for a few seconds, then it all shuts down. I can successfully turn on the laptop by holding it until the chime.

When on and plugged in, the magsafe charger will always show a green light regardless of battery's charge level. While plugged in, the battery percentage displays correctly and it acknowledges that it is plugged in. However, it states that the battery is not charging. It also states that the laptop is on adapter power. However, the battery drains steadily during use.

Furthermore, When off, the magsafe charger will display a green light and not charge the battery. An SMC reset (or soft SMC reset? I'm not sure what to call it because I hold down shift, option, and control and just tap the power button once. I do not hold it down to turn the computer on because the battery won't charge while on) will cause the magsafe light to change from green to orange and charging will begin. However, charging is very slow. 12 hours charging results in 15% battery.

3. CPU is being hogged by kernel_task. About 250-350%. Always. I understand this is probably reactionary by the computer to one of the problems I have.

Notes: Before any work began on cleaning, i received the error 400000: IPBR 9.165. I found a thread saying that this alluded to corrosion on the connectors and surrounding board connections where the battery connects to the logic board. Cleaning these areas and surrounding areas (as well as dc-in board) with 91% isoproply alcohol has removed this error.

The cleaning process did not damage any internals of the computer or cause any of these problems. The problems arose before cleaning occurred and persisted in the same manner afterwards.

Tasks already completed

-I spilled coffee

-I turned it off, removed battery, let dry

-Ran diagnostics, receieved error IPBR 9.165

-Ran SMC and PRAM resets

-Thoroughly cleaned logic board and dc-in board

-Re-ran diagnostics, no more error code.

Soooooo, I'm planning on replacing the dc-in board. Then the battery. But I'm kind of convinced it's neither. The fact that it charges, but only after an smc reset, suggests the battery is functioning. As does a reading of "good" for the battery from the OS and from Coconut Battery. The fact that it charges, suggests that my Magsafe charger is fine, although I'm borrowing another to see if there is any effect on charging speed.

Why it doesn't charge the battery while is confusing. I've found another user with a similar problem who says that watching the battery % reading, it actually would go up from time to time while running. So maybe the charging speed, or power supply from the magsafe, is so low that the battery doesn't charge fast, doesn't register as being charged while laptop is on, and doesn't supply enough power to the laptop to rely on it for all it's power while operating (causing it to deplete power from the battery).

If a new adapter is a fix, it still won't solve my kernel_task issue. I've read others having relief from this issue after replacing the battery. But I'm really stuck there.

I'm kind of lost, am I missing something? Please don't say it's the logic board.

So I Charged the battery completely. As painful as it was, it seems to have fixed the Kernel_task overloading and the battery is draining a much more normal speed. However, the battery does not charge while the laptop is on. I still have yet to try soMeone else‘s Magsafe charger. I think that Mine is definitely failing. I will post again if the probleM re-arises.