Godfrey van der Linden writes:
G'day Nikita,
Hello, Godfrey,
The KDP protocol is transported using the ethernet driver that is
polling. This causes the CPU to spin really, really fast, (I'm not
sure what the other CPU is doing during this). So you are using 100%
of the CPU to keep up with the network, this needs to be cooled.
Now when you start debugging you are deliberately setting the system up
to ONLY run your code in the driver being debugger. Unfortunately this
stops the fan controller driver from running. Thus the system
fails-safe by spinning up the fans until the driver start running
again. As you are using 100% CPU you probably do need to let the fans
go anyway.
Yes, this makes perfect sense.
You may be able to workaround the fans by breaking up your debugging
into sections. Instead of thinking at the GDB prompt, continue the
system then set another breakpoint after your have done your thinking.
Back to the good old batch days. :)
Finally as a general rule the system doesn't appreciate being unable to
run for too long, (I can't define 'too' long as it depends).
Godfrey
Thank you for your help, Nikita. _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.