From owner-freebsd-hackers@FreeBSD.ORG  Sat Jun  7 16:39:28 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8B1C0524
 for <freebsd-hackers@FreeBSD.org>; Sat,  7 Jun 2014 16:39:28 +0000 (UTC)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5DA572CB1
 for <freebsd-hackers@FreeBSD.org>; Sat,  7 Jun 2014 16:39:28 +0000 (UTC)
Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52]
 helo=damnhippie.dyndns.org)
 by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.72) (envelope-from <ian@FreeBSD.org>)
 id 1WtJeK-0004wy-NU; Sat, 07 Jun 2014 16:39:20 +0000
Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240])
 by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s57GdH2i002650;
 Sat, 7 Jun 2014 10:39:17 -0600 (MDT) (envelope-from ian@FreeBSD.org)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 24.8.230.52
X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse
 reporting information)
X-MHO-User: U2FsdGVkX1+RYYntt4Hj8JAli7KzKwqQ
Subject: Re: Re[2]: Fwd: Interrupt Overload
From: Ian Lepore <ian@FreeBSD.org>
To: Vladislav Prodan <universite@ukr.net>
In-Reply-To: <1402157083.156846225.m95e69ke@frv35.fwdcdn.com>
References: <538A3432.5010303@gmx.us> <53930E19.8090603@gmx.us>
 <53931963.4040604@selasky.org> <53932314.6010108@gmx.us>
 <1402153691.709851721.u6k6kkkk@frv35.fwdcdn.com> <53933110.8060300@gmx.us>
 <1402157083.156846225.m95e69ke@frv35.fwdcdn.com>
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 07 Jun 2014 10:39:17 -0600
Message-ID: <1402159157.20883.157.camel@revolution.hippie.lan>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: freebsd-hackers@FreeBSD.org, Dutch Ingraham <stoa@gmx.us>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jun 2014 16:39:28 -0000

On Sat, 2014-06-07 at 19:04 +0300, 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
>  

It's unclear to me why you are hung up on the idea of changing timers
when the misbehaving interrupt is unshared and used only by a USB
controller and there's no evidence of any kind that a timer is involved.

-- Ian