Re: What are the $%& boxes waiting for? :(

2014-03-24 Thread Matt Graham
On 2014-03-24 08:32, kitepi...@kitepilot.com wrote: I have several Linux boxes (different distros, no common denominator) that for no apparent reason have the processor(s) go into a 'waiting' state rather way too often. Darn it, how do I find out what in the #$%@ World are those processors wa

Re: What are the $%& boxes waiting for? :(

2014-03-24 Thread JD Austin
Also modern Processors throttle themselves to cool down when they get too hot. -- JD Austin Voice: 480.269.4335 (480 2MY Geek) j...@twingeckos.com On Mon, Mar 24, 2014 at 8:32 AM, wrote: > My guess based on nothing is that you have the ACPI stuff turned on in the >> bios and have the power m

Re: What are the $%& boxes waiting for? :(

2014-03-24 Thread kitepilot
My guess based on nothing is that you have the ACPI stuff turned on in the bios and have the power management features enabled. Intriguing guess, something to test, but... My 'knowledge' stands that ACPI ON is 'good', isn't it? Can you elaborate? There are no laptops involved, so I certainly don'

Re: What are the $%& boxes waiting for? :(

2014-03-24 Thread JD Austin
My guess based on nothing is that you have the ACPI stuff turned on in the bios and have the power management features enabled. -- JD Austin Voice: 480.269.4335 (480 2MY Geek) j...@twingeckos.com On Mon, Mar 24, 2014 at 8:11 AM, Stephen Partington wrote: > the second coming? > > > On Mon, Mar

Re: What are the $%& boxes waiting for? :(

2014-03-24 Thread Stephen Partington
the second coming? On Mon, Mar 24, 2014 at 8:10 AM, wrote: > Hello collective wisdom... > I have several Linux boxes (different distros, no common denominator) that > for no apparent reason have the processor(s) go into a 'waiting' state > rather way too often. > And then they wait... > and wai

What are the $%& boxes waiting for? :(

2014-03-24 Thread kitepilot
Hello collective wisdom... I have several Linux boxes (different distros, no common denominator) that for no apparent reason have the processor(s) go into a 'waiting' state rather way too often. And then they wait... and wait... and wait some more... Darn it, how do I find out what in the #$