Kernel_task high CPU - faulty thunderbolt port?

Question

Have been experiencing problems with my MacBookPro8,2 (Late 2011) running 10.8.2 and connected to a Thunderbolt display when the kernel_task hogs 70% of CPU capability. A Promise RAID is also connected to the display, but don't think is related.
This is what I've found so far:
* As soon as I disconnect the Thunderbolt display, CPU system usage goes down to < 3%
* Connected Promise RAID to the MBP, and no CPU usage changes
* Reconnected the display and umm... wouldn't detect it... had to restart couple of times before getting it to work again...
Since I bought them (MBP + display) I've been having problems, but I have not being able to nail them down:
* The Display's speakers often fail
* The Ethernet connection often fail to detect
* The USB ports often fail
* The bloody display wouldn't get detected some times
Don't think the problem is with the Display as I've connected my Mac Book Air to it, and have not had any problem.
I guess I'll have no choice but to take the MBP to the shop, but I was wondering if somebody has some ideas.
Roberto

Answer 1

So this has been happening to me too... it's been infuriating as it's neither consistent, nor easy to resolve once it starts happening. Restarts and SMC resets SOMETIMES do not resolve the problem.
Thank you, rodogu, for your insight to this. Here's some further information. This happens to me BOTH at work with a ThunderBolt connected LED Cinema display (the model before the Thunderbolt Display), AND at home on an older 23" Apple Cinema Display connected, by adaptor, to the Thunderbolt port.
My MacBook Pro is actually an 8,3 (2.3GHz i7) running 10.8.3.
After reading your post I unplugged the display from the Thunderbolt port (leaving the displays USB connection plugged in) and presto!... CPU usage on process 0 (kernel_task) went from 609% to basically nothing.
APPLE FIX THIS!!!!!!! Sheesh..........