From owner-freebsd-acpi@freebsd.org Tue Sep 29 13:50:28 2015 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47C69A0BD52 for ; Tue, 29 Sep 2015 13:50:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 24F8914EC for ; Tue, 29 Sep 2015 13:50:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1035CB95D; Tue, 29 Sep 2015 09:50:27 -0400 (EDT) From: John Baldwin To: freebsd-acpi@freebsd.org Cc: Arthur van der Peijl , Kevin Oberman Subject: Re: ACPI problems op ASrock Date: Mon, 28 Sep 2015 13:59:41 -0700 Message-ID: <8632725.d9CDSAQRzF@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-PRERELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <49E6B533-4457-4583-82A2-9940C291AB51@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 29 Sep 2015 09:50:27 -0400 (EDT) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2015 13:50:28 -0000 On Saturday, September 26, 2015 10:17:20 AM Arthur van der Peijl wrote: > Thank you for assistance: powerd must clearly not be my focus: the CPU stays high and thus cannot go into idle mode. Yes, I don't think tcc or throttling is related here. Your issue is that something is queueing tasks to the ACPI task queue threads (or a task is getting stuck in a busy loop). AFAIK there isn't really a great way currently to see which tasks are being queued to a taskqueue and how long they are running. It might be a nice thing to add some KTR traces for, to log how long tasks run on a given taskqueue thread (I added something a while back for callouts so they show up in schedgraph with the function pointer and you can then use a debugger to map that pointer to a symbol name). As an initial guess you might try identifying tasks that can be queued and adding some stat counters exported via sysctl for different functions. -- John Baldwin