From owner-freebsd-current@FreeBSD.ORG Fri Apr 20 18:18:30 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A02FC106566B; Fri, 20 Apr 2012 18:18:30 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3823D8FC08; Fri, 20 Apr 2012 18:18:30 +0000 (UTC) Received: by vbmv11 with SMTP id v11so9257777vbm.13 for ; Fri, 20 Apr 2012 11:18:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=2fde7twC4oCNCwK5Gkp0baChbIj1MCbtGaniPUd3JCg=; b=SPVAZUrxPmh3cgUSkvD9BUNdvhJ8Z0GvF2erdajzEaD+jMWWKA9hSU+JlTuRTpk0mk xM2MJX+ZOPG1Etpr3CB9uG/Q6osv8MPqYqKH3AjecZ9VHBnlRs8CWjqsL/v0IOIcZDP3 XhqXdQ/4b008QBmBtUXgGnqLxMMayH9yNp7Tma+O5NrJW9o9kH2rLzwiLVg70oJfkAw1 PgloXFlAg34qpwvvYc++e6U45qsgFuJIC/kDMpXIW0RjcTEPIeaO3iM4GyjsOUIwUHIm rk6J4A910Amly3n2+do249Ssmwg0Hq/c3WTgOKMr4HKgi53o/1Rrc+gAz2xNWhIr81fe UWFA== MIME-Version: 1.0 Received: by 10.52.172.172 with SMTP id bd12mr4819915vdc.69.1334945909700; Fri, 20 Apr 2012 11:18:29 -0700 (PDT) Received: by 10.220.18.16 with HTTP; Fri, 20 Apr 2012 11:18:29 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Apr 2012 14:18:29 -0400 Message-ID: From: Arnaud Lacombe To: FreeBSD Hackers , FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Disabling an arbitrary device X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 18:18:30 -0000 Hi, On Fri, Apr 20, 2012 at 2:16 PM, Arnaud Lacombe wrote: > Hi, > > I will be bringing up an old thread there, but it would seem the > situation did not evolve in the past 9 years. I have a machine running > 7.1 whose UHCI controller is generating some interrupt storm: > > # vmstat -i > interrupt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0total =A0 = =A0 =A0 rate > irq4: sio0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01328 =A0 = =A0 =A0 =A0 =A02 > irq19: uhci1+ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 63514509 =A0 =A0 =A0963= 80 > [...] > > generating useless load on one CPU: > > # top -SH > last pid: =A05223; =A0load averages: =A00.00, =A00.00, =A00.00 =A0 =A0up = 0+00:17:21 =A013:10:35 > 117 processes: 14 running, 79 sleeping, 24 waiting > CPU: =A00.2% user, =A00.0% nice, =A00.2% system, =A06.6% interrupt, 93.0%= idle > Mem: 33M Active, 9348K Inact, 67M Wired, 400K Cache, 29M Buf, 2892M Free > [...] > =A0 57 root =A0 =A0 =A0 =A0 =A0-64 =A0 =A0- =A0 =A0 0K =A0 =A0 8K CPU0 = =A0 0 =A011:59 86.57% irq19: uhci1+ > > I thought I could use an hint to forbid uhci(4) attachment, ala: > > hint.uhci.0.disabled=3D"1" > hint.uhci.1.disabled=3D"1" > > in /boot/loader.conf. However, it would seem that what should be > usable with any arbitrary devices, ie. be an integral part of > device(9), has to be hardcoded in every driver, sad. > as for the usual "if you're not happy, please provide a patch": https://github.com/lacombar/freebsd/commit/30786d09b0cb441890cdc749ee524323= 8e81d2d8 regards, - Arnaud > =A0- Arnaud > > ps: the original thread I found is from September 2004: > http://lists.freebsd.org/pipermail/freebsd-questions/2004-September/05871= 7.html