• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Intel Burn Test + Prime95 = Error?

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
See the odd thing here is that isn't what happens in practice. Try it. IBT snuffs p95 out.

I'm assuming IBT runs at Normal priority. I've never run IBT, so it may be running at a different priority.

Two instances of Prime95 using the CPU full bore will behave as I've described.
 
See the odd thing here is that isn't what happens in practice. Try it. IBT snuffs p95 out.
Yay because the process can set a priority for his own threads, so if IBT set's it to very high or Realtime clearly it will get more CPU time.. that's the very principle of this stuff.

But again this has ABSOLUTELY nothing to do with a deadlock. As I said Coffman defined this stuff more than 30 years ago. And one of the four (five? look it up in Wikipedia or somewhere else if you need to know it that correctly) necessary conditions for a deadlock is, that there's no preemption for ressources. Which clearly isn't true, because every modern OS uses preemptive scheduling.
QED
 
Back
Top