From owner-freebsd-acpi@FreeBSD.ORG Mon Aug 13 17:47:16 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 38586106564A; Mon, 13 Aug 2012 17:47:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0C38E8FC15; Mon, 13 Aug 2012 17:47:16 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 817C8B9BC; Mon, 13 Aug 2012 13:47:15 -0400 (EDT) From: John Baldwin To: Sean Bruno Date: Mon, 13 Aug 2012 11:27:18 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <1342730963.2656.5.camel@powernoodle.corp.yahoo.com> <201208080725.24199.jhb@freebsd.org> <1344445163.2813.2.camel@powernoodle.corp.yahoo.com> In-Reply-To: <1344445163.2813.2.camel@powernoodle.corp.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201208131127.18457.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 13 Aug 2012 13:47:15 -0400 (EDT) Cc: "freebsd-acpi@freebsd.org" Subject: Re: Time to increase MAX_TASKS? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2012 17:47:16 -0000 On Wednesday, August 08, 2012 12:59:23 pm Sean Bruno wrote: > On Wed, 2012-08-08 at 04:25 -0700, John Baldwin wrote: > > I meant that with the limit jacked up to something that silences the > > warning > > (such as 128), what is the max number of tasks queued? > > > > > > I set debug.acpi.max_tasks=128 and added a temp log message to > acpi_task_enqueue(). I see the system request *98* tasks according to > my test on this new Dell box. Is it possible that the queue really > isn't running yet or something? Yes, it isn't running during the first pass of probe and attach. It would be good to know what the source of tasks besides acpi_cpuX devices was. -- John Baldwin