Hello, first time poster here. Computer is a late 2011 MacBook Pro, 2.4GHz, 4GB RAM, 500GB ATA (approximately 50% full), previously operating normally. Here's a timeline of events: 6/23: On an airplane when ~2-4oz of hot tea spilled near upper left section of keyboard (while operating). Computer shut itself down within 5-10sec. Dried all apparent liquid on the outside and rebooted about 5min later. Everything seemed to work, but also was very slow. Later that day, removed bottom cover and inspected. No apparent liquid there. Ran AHT to reveal logic board fault. Enroute on a cross-country road trip, shut down and closed it up. 6/25: Visited local mac repair shop for advice. Removed bottom cover, cleaned, inspected. No visible damage. Advised going to Apple store for consult. 6/27: At Apple store, activity monitor showed 300%+ CPU usage for kernel task. Advised logic board fault (voltage sensor) and $700+ repair. Apple rep suggested leaving computer open/off for two weeks and restart, as rarely this will fix the problem. 6/27-7/11: As advised, left computer open/off. Placed near box fan for additional airflow. Applied hair dryer on low setting 5min/day. 7/11: Turn computer on, and everything worked perfectly. Kernel task usage appeared normal (<2%). No problems. Rejoice! 7/11-7/15: Worked normally through ~15h of use and 10+ shutdown/boot cycles. No problems. 7/15: Following unremarkable shutdown/reboot, same problem returned. Very slow, 300%+ CPU usage for kernel task. Reboot to same. Discovered that under another user account, computer still ran very slow, but kernel task overload did not show on activity monitor. 7/16: After 24h off with air blowing on it, computer rebooted and ran normally. 7/18: After 36h off with air blowing, computer rebooted to run normally. Restart and AHT revealed same logic board fault. Restart to run slowly with original problem. Computer's been shut down since. So... from what I've read here, the slow operation seems consistent with spilled liquid, logic board failure, and buying a new computer. However, the fact that the problem seemingly resolved with drying treatment, then returned, and especially that the kernel task indicator is inconsistent across users makes me think there's hope. Perhaps a software bug introduced by the original hardware insult? Maybe I should dry it out even longer? Appreciate any advice or perspectives!