Currently Being ModeratedJul 25, 2012 10:20 PM (in response to IEBA1)
unless of course, you know....you managed to break your own computer
its only Apple's responsibility if its under warranty
but feel free to cry about Apple some more, surely this novel approach to diagnostic testing will magically reward you with the knowledge you are seeking
Currently Being ModeratedJul 26, 2012 12:39 AM (in response to kallisti)
>>or perhaps you've demonstrated you're not really worth the complete explanation
Go ahead, explain it to me in detail, I am a OS kernel developer (not XNU)
so I can understand a low level explanation of the problem.
>>but its cute how you think Apple reads these posts
I do not know if they do. They should listen to their customers.
Again, you seem to be out of arguments.
Currently Being ModeratedJul 26, 2012 12:58 AM (in response to e__soriano)
oh man if only i would rise to the challenge or risk the shame of esteemed forums poster "e__soriano" telling the world "I am out of arguments"
I imagine youre just squirming for a worthy opponent
if only....if only there was someone who could tolerate you long enough to wage the mighty battle of nerd rage.
Perhaps you enjoy more adversaries willing to throw down the gauntlet back at 4chan
I lay down my bat leth and bid you, run along tiny man, somewhere on this vast digital expanse there is a chan of fellow hormonally inclement males bated with rabid fingers who would lunge at the opportunity to rain an onslaught of "youre out of arguments" upon thee
Currently Being ModeratedJul 26, 2012 1:47 AM (in response to kallisti)
I only see cheap meme-based forum rhetoric in your posts.
No time for kiddies fights. It is clear that you do not have
technical arguments. If you find any, I am still waiting.
If not, shut up and stop making a fool of yourself.
Your solution is shooting in the dark. It is a botch.
Something you did made the bug stop bitting, but the
bug is still there. This is not an acceptable solution.
Apple, fix the bug.
Currently Being ModeratedJul 26, 2012 2:28 AM (in response to e__soriano)
Could you two children (kallisti and soriano) please stop this pointless bickering? Every time you post a message that has nothing more to do with the original problem, ALL the posters get an email. Please stop wasting bandwidth.
There have been quite a few informative posts in this thread as a whole, but none seems to have solved the problem for everybody.
Since the issue has not gone away for all, but I think I have found a way of solving it for myself (see my posts on the subject) I will now try to see if my solution is actually veryfiable. I have put back the Uniq leather cover on my MB Air and will see if the KT issue starts up again. That would point to (for me at least) the fact that the problem seems heat related. I will post back in a week or so to relay results.
On a tangential issue that was raised, it would seem obvious to me that Apple staff read these postings (or at very least read the most active ones). Why would they spend the money hosting this support forum otherwise?If they have not responded it seems also obvious that there is no clear solution for now, or there will be one in a future release. Let's see what happens with Mountain Lion...
Currently Being ModeratedJul 26, 2012 2:38 AM (in response to makalu57)
> Could you two children (kallisti and soriano) please stop
> this pointless bickering? Every time you post a message
> that has nothing more to do with the original problem,
> ALL the posters get an email. Please stop wasting bandwidth.
You are right. Sorry to take the bait.
> That would point to (for me at least) the fact that the problem
> seems heat related.
I bet it is related to heat/power-saving. Tell us the results of
Currently Being ModeratedJul 26, 2012 6:22 AM (in response to e__soriano)
I didn't have to wait a week! KT's running amok (from less than 50% to 147% of CPU varying instant by instant) less than 4 hours after I put the cover on the MB Air! I will now shut down, take the sleeve off and restart. Definitely heat related, for me at least. I am not running any other CPU intensive tasks, other than the processor hog that Flash is on Safari. Everything else is pretty much shut down, including Carbonite backups.
I haven't had ANY KT problems since I removed the sleeve. Now with the sleeve on the problem returns.
Currently Being ModeratedJul 26, 2012 8:35 AM (in response to snow_bunny)
> That would point to (for me at least) the fact
> that the problem seems heat related.
and, as suggested by someone else at: https://discussions.apple.com/message/19025715?ac_cid=tw123456#19025715
> I suspect some core hardware/software problem
> that gets stuck in some bad loop.
Definitely, on all counts. As I have posted on another thread on 12th March (https://discussions.apple.com/message/17841142), try vacuum-cleaning the fans after opening the case (full throttle, but carefully, thank you) – even if, as was my case, the dust looks very thin, indeed almost inconspicuous. It has worked marvels.
I've had to repeat the operation a few weeks ago, though. I attribute this to two factors: 1. A period of extensive removal. Removals are always the cause of lots of dust flying about, and while dustbunnies are readily visible, the "thin" kinds aren't, but that doesn't keep them from sneaking into the most undesirable places (computer fans, or lungs). Then, 2. The power strip that feeds my screen, which in turn feeds my MBP, wasn't properly grounded – I hadn't really paid attention, because I use an older external keyboard made of plastic, not metal. Possibly, the unwanted electric current in the case would also be attracting more dust.
But again, I got back the MBP's full power after vacuuming the fans, and that's what counts.
Currently Being ModeratedJul 26, 2012 8:47 AM (in response to kallisti)
If only we could flag replies as inappropriate...
Because insulting, demeaning, nonsensical, and completely unhelpful replies are a waste of everyone's time.
Makalu57 - sorry to hear KT has come back.
But at least you have a plan for combatting it, based on prior success.
As much as I would expect that heat would cause the computer to throttle down the CPU to have it do _less_ it seems that the opposite is happening, some bug in software is causing a process to get stuck in an bad loop, forcing the processor to work harder- without rest, increasing CPU temp, which creates more heat.
I'd love to hear if someone with a Mini with this problem could stick it in a "dorm fridge" without adjusting any settings, and then, after a half hour of chill, start it up and see if the much cooler computer banished the KT with ZERO other effort.