From owner-freebsd-acpi@freebsd.org Thu Apr 21 14:46:11 2016 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 B182AB171F9 for ; Thu, 21 Apr 2016 14:46:11 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B80D115C for ; Thu, 21 Apr 2016 14:46:11 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: by mail-oi0-x236.google.com with SMTP id x201so86718977oif.3 for ; Thu, 21 Apr 2016 07:46:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=9k6dP6Kp/fZ7FDF8zCJaysV2ZIVseGsitVjL52Q5wgU=; b=DiCF/k4OVYgmMNgDmhlGzWoN/m+fex9UghTWxvM+eEg7sXSxf1SZxVMLxRQsWqwoAz GIAWO7jaMh6sOP8nZCifkTq4WMyaDHbV9zVTQJusyn8QZEv1GUYNWIHnPhuzFkGR+HCw JAomgAdOGktXEIHOHH/zHOlZcf8dOWNovpAKusWBIeYpHELQX0MC/t2uAhPZYw+QgR/c x6Az4VvWJMmsuhmeVMD5gc1YFSVlxI3iXFNIGcgjhNokNdGRMr0mFzg00ga7MhE4Ooe/ YtKVtqLqXHwr4zNFcVQEf+fVnwqmEhKkQq3Pg+z23IO1HgGz9BvxWD6xul7LvZBn84nz DMHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=9k6dP6Kp/fZ7FDF8zCJaysV2ZIVseGsitVjL52Q5wgU=; b=XamcZzdvGArsyFLuoM4XvIPbWPcFf4BgTakTt2TyjAKbjNxM0vi25jfVxG9jUNSow5 CziU6pKFTVlvbTRImI+VRnoEsYEuRaBlaQWMgcDlg9EnW3Hu3Rq6lfM3UGCG+Djj8M+f 5HxKbyhm8hkdiFFsIW3a8qw5jXYQQ2KW90vVaClER4D/3b9Ikzmka91BkBfcFqpSYwaX sjZ7q6DaaIM0Kz3Xz/IVwjud+Zksgr3P1kteMTxs4brs9E+e+uCGo7ux8qjWbz+BP+Ws xQGKH3mZbFL1M175bNoTRj0j08rPAwix4XbTYGwdPwS7ClVz69de5RvEu7MHr7dZwOYA UEvw== X-Gm-Message-State: AOPr4FWqKR20LmiM+AmgyA48LuJk9xjmw1/LOvVJGeFV0wzSNOhx/l7inCd7UdbH57LNLBAgY8DrlUygBLOayA== MIME-Version: 1.0 X-Received: by 10.60.123.41 with SMTP id lx9mr6622384oeb.55.1461249970766; Thu, 21 Apr 2016 07:46:10 -0700 (PDT) Received: by 10.202.199.135 with HTTP; Thu, 21 Apr 2016 07:46:10 -0700 (PDT) Date: Thu, 21 Apr 2016 10:46:10 -0400 Message-ID: Subject: high acpi_task load From: Johannes Dieterich To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 14:46:11 -0000 Dear all, I have for a long time observed a very high system load (seemingly erratic) on my Elitebook 745 G3. I am finally able to reproduce the behavior and would love input on how to solve it. If the laptop is attached to the docking station, acpi_task processes are eating up an entire core worth of CPU time, thereby disallowing the system to ever get to idle states with temperature and load issues associated. This is in so far reprodroducable as that locking it in at runtime causes these processes to appear on top -SH, disconnecting at runtime causes them to disappear. Inspecting a core dump generated during high load seems to point to ACPI's thermalzone: #5 0xffffffff803b0a97 in acpi_tz_cooling_thread (arg=) at /usr/src/sys/dev/acpica/acpi_thermal.c:1162 #6 0xffffffff809ec8e4 in fork_exit ( callout=0xffffffff803b0620 , arg=0xfffff800055f9a00, frame=0xfffffe043f590a40) This is a timer: tsleep(&sc->tz_cooling_proc, PZERO, "cooling", hz * sc->tz_zone.tsp / 10); As I reported earlier, the thermal zones are very broken on this notebook. However, it surprises me that this would a) have such an impact and b) only when connected to a docking station. Any input/ideas are appreciated! Happy to test things. Johannes