Try charging on the right and not on the left
apple.stackexchange.com
Try charging on the right and not on the left
1–10 of 80 posts
Re: Try charging on the right and not on the left
#2Did anyone ever figure out why exactly the temperature sensor was making kernel_task go crazy?
Re: Try charging on the right and not on the left
#3Should I understand that having any kind of load on the measly 2 ports I have on my 1600€ computer will lead to abysmal performance? Like, attaching a USB hub to add basic necessity like HDMI or USB A?
Re: Try charging on the right and not on the left
#4high CPU usage by kernel_task is caused by high Thunderbolt Left Proximity temperature, which is caused by charging and having normal peripherals plugged in at the same time. Did anyone ever figure out why exactly the temperature sensor was making kernel_task go crazy?
Re: Try charging on the right and not on the left
#5high CPU usage by kernel_task is caused by high Thunderbolt Left Proximity temperature, which is caused by charging and having normal peripherals plugged in at the same time. Did anyone ever figure out why exactly the temperature sensor was making kernel_task go crazy?
The comment by jksoegaard may explain it: "the purpose of the thread is to force idleness". I guess it uses up all the CPU without actually making the CPU do anything, so other processes can't use the CPU and produce more heat than it can handle.
Re: Try charging on the right and not on the left
#6high CPU usage by kernel_task is caused by high Thunderbolt Left Proximity temperature, which is caused by charging and having normal peripherals plugged in at the same time. Did anyone ever figure out why exactly the temperature sensor was making kernel_task go crazy?
The comment by jksoegaard may explain it: "the purpose of the thread is to force idleness". I guess it uses up all the CPU without actually making the CPU do anything, so other processes can't use the CPU and produce more heat than it can handle.
Re: Try charging on the right and not on the left
#7Earlier quoted context omitted.
The comment by jksoegaard may explain it: "the purpose of the thread is to force idleness". I guess it uses up all the CPU without actually making the CPU do anything, so other processes can't use the CPU and produce more heat than it can handle.
That's very interesting. I didn't know it was possible for a process to use the CPU without using the CPU, as it were. Rather I thought the CPU usage was more or less a direct measurement.
On processors that have a halt instruction that stops the CPU until an interrupt occurs, such as x86's HLT instruction, it may save significant amounts of power and heat if the idle task consists of a loop which repeatedly executes HLT instructions.
--
I don't know how it is implemented in darwin, HLT is a privileged instruction, then again it's kernel_task.
Re: Try charging on the right and not on the left
#8This doesn't make sense, and I'm a bit worried: I "cheaped" out and have a "left side only USB-C" MBPro from 2019. Should I understand that having any kind of load on the measly 2 ports I have on my 1600€ computer will lead to abysmal performance? Like, attaching a USB hub to add basic necessity like HDMI or USB A?
Re: Try charging on the right and not on the left
#9This doesn't make sense, and I'm a bit worried: I "cheaped" out and have a "left side only USB-C" MBPro from 2019. Should I understand that having any kind of load on the measly 2 ports I have on my 1600€ computer will lead to abysmal performance? Like, attaching a USB hub to add basic necessity like HDMI or USB A?
Benchmarks show the MB having decent performance, as they start cold and don’t have external devices attached either. Thermal throttling only shows up once you’ve already bought
Re: Try charging on the right and not on the left
#10I mean, it's happening cause charging it, that's something all users will do :S
Sounds a lot like the antennagate