Re: Fwd: Interrupt Overload

On 06/07/2014 12:04 PM, Vladislav Prodan wrote:
> 
> 
>  
>  --- Original message ---
>  From: "Dutch Ingraham" <stoa@gmx.us>
>  Date: 7 June 2014, 18:33:12
>   
> 
>>
>> Thanks for the response.
>>
>> The output you requested:
>>
>> kern.eventtimer.choice: HPET1 (440) HPET2 (440) HPET3 (440) HPET4 (440)
>> HPET5 (440) HPET6 (440) LAPIC (400) i8254 (100) RTC (0)
>>
>> kern.eventtimer.choice: HPET (did not specify 1, 2, etc.)
>>
>> I also changed the type of timer to LAPIC and rebooted; there was no
>> appreciable change in the interrupt activity.
> 
> After reboot what became timer? :)
> 
> You can change the timer "on the fly", without rebooting the system.
> 
> If LAPIC does not help, then try other timers.
> 
> 
> --
>  Vladislav V. Prodan
>  System & Network Administrator
>  support.od.ua
>  
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
> 

You're right, it is not persistent.  I changed to each different event
timer and the only one that made a difference was the i8254; that
dropped the cpu load from 30% to 10-12%.  Much better, but still of
course not acceptable for a Core II-Duo running at 3.0GHz.  The load
averages shown in <top> do also drop proportionally.  Interestingly,
though, <systat -vmstat> shows the same interrupt rate - 325K/sec.

What do you make of the fact that when I suspend with <<acpiconf -s 3>
and then wake-up, everything is absolutely normal, regardless of event
timer type?
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"