From owner-freebsd-current@freebsd.org Fri Jun 3 00:08:49 2016 Return-Path: Delivered-To: freebsd-current@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 0C926B68A8F for ; Fri, 3 Jun 2016 00:08:49 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 C80B31702 for ; Fri, 3 Jun 2016 00:08:48 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-it0-x233.google.com with SMTP id e62so141396981ita.1 for ; Thu, 02 Jun 2016 17:08:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=VggJGVvRJGvz30z5X8AVzkBj7j5eXYlSbtW6REOiuNs=; b=KyJk4XecN0EdGp7BLJsKvecvlrOyqf0ZrAM84XjsfxZLtbqNrZhZVOx9J1eQmuAPgT TYyE+4tDKP0L6x16uduvM1xrWXtLdUA7ZqONHByEl7h3yBMfvWo6RaETtLG2dueN8ov8 1ThISsbB6vJhgT1iIOhdsNPBEMy2WNF0GTh7DevKL8ao7z6JRq952PwjxBWM7DDn8g+I Exc2K9W8wgxOuxMB4uIgrC6mN9bUhp0ScO02dWz5GrvROl+PsMKLSLbtUHAxvhXM61Y8 kkkfNYvLzgFf87RVEkwNpuhkdnPrc912ECdY+OMbJb4/iuLkRnQDAdExxt/+3rxZxVwW yvcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=VggJGVvRJGvz30z5X8AVzkBj7j5eXYlSbtW6REOiuNs=; b=X8sZHxvMTMMJUhlmxeVCz7pLYd+aPPEOZA4t0WNL1cmWPqKEP3BmAji8l6xHxBYTi7 Iq9SIqrFieI65KzrsbUAhLCLzbWcsbRb/OOgkKPpXsbXBKWLlTZX+M/9hqHxSiGAK/f5 4kuCoZlJG9OtXpY3NYYbTr48uNcqNPbD4jpNGpGA1b04gfAp/PaW3e9QxPMKy52A37MQ SNKx5syVh6MDd/pzNuSVUbiZkKkFVgJoROQvpvL1K214163sGlOebvEWIPWEu62Fv7hZ CZ09PIL1Hihr5OMO5jwGDs7vTARAugJzVgAml2944pFbAi8lswcFy7GbB0gU6ezch1c7 I8ZA== X-Gm-Message-State: ALyK8tJBs4sM1bPc2eI+pGMnjXvRUahrfkrIAcXIeM3b1gGVRs+Vj1bKfu/il2SCf/uNDec71/QLCwsALd4gQQ== MIME-Version: 1.0 X-Received: by 10.36.64.14 with SMTP id n14mr6059774ita.53.1464912528136; Thu, 02 Jun 2016 17:08:48 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.79.20.70 with HTTP; Thu, 2 Jun 2016 17:08:48 -0700 (PDT) In-Reply-To: <20160602224654.18927083.ohartman@zedat.fu-berlin.de> References: <0448c751-8608-51ce-f47e-76280ebf14f2@selasky.org> <20160602224654.18927083.ohartman@zedat.fu-berlin.de> Date: Thu, 2 Jun 2016 17:08:48 -0700 X-Google-Sender-Auth: aaoHOv511vqOr-kpSNMGzQ-Q7s0 Message-ID: Subject: Re: Suddenly poweroff in 11-Current r300097 From: Kevin Oberman To: "O. Hartmann" Cc: Hans Petter Selasky , RayCherng Yu , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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, 03 Jun 2016 00:08:49 -0000 On Thu, Jun 2, 2016 at 1:46 PM, O. Hartmann wrote: > Am Thu, 2 Jun 2016 10:26:22 -0700 > Kevin Oberman schrieb: > > > On Thu, Jun 2, 2016 at 7:41 AM, Hans Petter Selasky > wrote: > > > > > On 06/02/16 03:07, RayCherng Yu wrote: > > > > > >> I got a suddenly poweroff in r300097 (and previous revision in April > and > > >> May) when I built textproc/docproj. > > >> My machine is Macbook Pro 13 2011 early. I have checked the Apple > website. > > >> My bios is the latest version. > > >> Actually it also happened in 10.3-STABLE. > > >> It happened when the machine load was heavy. Before it shutdown, the > fan > > >> started to run very loudly. After several seconds (20 or 30 seconds), > my > > >> laptop shutdown (poweroff directly) suddenly. It seems not happen > with the > > >> AC power supply connected. > > >> > > >> I installed both Mac OSX and FreeBSD (dual boot). It never happened > in Mac > > >> OSX. > > >> > > >> My dmesg: > > >> http://pastebin.com/QjZmbGCB > > >> > > >> My sysctl hw.acpi: > > >> > > >> hw.acpi.acline: 0 > > >> hw.acpi.battery.info_expire: 5 > > >> hw.acpi.battery.units: 1 > > >> hw.acpi.battery.state: 1 > > >> hw.acpi.battery.time: 87 > > >> hw.acpi.battery.life: 59 > > >> hw.acpi.cpu.cx_lowest: C8 > > >> hw.acpi.reset_video: 0 > > >> hw.acpi.handle_reboot: 1 > > >> hw.acpi.disable_on_reboot: 0 > > >> hw.acpi.verbose: 0 > > >> hw.acpi.s4bios: 0 > > >> hw.acpi.sleep_delay: 1 > > >> hw.acpi.suspend_state: S3 > > >> hw.acpi.standby_state: NONE > > >> hw.acpi.lid_switch_state: NONE > > >> hw.acpi.sleep_button_state: S3 > > >> hw.acpi.power_button_state: S5 > > >> hw.acpi.supported_sleep_state: S3 S4 S5 > > >> > > >> > > > Hi, > > > > > > Do you have a temperature sysctl? Usually FreeBSD will shutdown the > system > > > if the ACPI temperature exceeds some value. Maybe it would be better to > > > reduce the CPU load when the temperature goes up instead of facing a > > > shutdown? > > > > > > --HPS > > > > > > The relevant information is probably found in dev.cpu. That is where all > > temperature information is located as it is per-CPU, not per-system. Of > > particular interest is dev.cpu.0.cx_lowest, dev.cpu.0.cx_supported, and > > dev.cpu.0.freq_levels. A snapshot of dev.cpu.0 when the fan has cranked > up, > > but before shutdown would be nice, too. > > > > I see no hw.acpi.thermal information. This is very odd. These values > > indicate what the system will do and is doing if it starts getting too > hot. > > > > Is coretemp loaded? It is required to see the core temperatures and those > > are almost certainly significant. It may account for the lack of thermal > > information. Finally, a dmesg might be useful as it will tell us more > about > > just what thermal control techniques are enabled. > > > > Just to explain a bit on how this should work: when the temperature > exceeds > > some BIOS defined point, the system should "throttle" by pausing one of > > every 8 clock cycles. If that does not fix the problem, the it rests for > > two of every 8 and so on until the temperature is reduced. If it > continues > > to rise and reaches another BIOS set point, it will initiate an emergency > > shutdown. If it reaches a CPU defined temperature, the power will shut > off > > immediately. Note that this is entirely a hardware function with no BIOS > or > > OS involvement. It should NEVER happen in normal operation as it is > > triggered by a significant overtemp that threatens to destroy the CPU. > I've > > only seen it once when the CPU heat sink came loose on an old P4 system > > several years ago. > > > > I should mention that I have zero experience with Apple hardware and it > is > > possible that they do some things differently than I have seen on other > > hardware. > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkoberman@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > I have had such problems many times with older hardware. In most cases > "dried out" > thermal conductive pad or grease was the reason overheating the CPU du to > a ineffective > thermal conductivity from the CPU's surface to the heat spreader/cooler. I > had recently > two laptops with such a phenomenon - using high-quality thermal grease > solved the problem > for my. In both cases, the former high-viscous thermal grease has become > like dry mud. > Same with pads. > Valid suggestion. If you have not worked with it, keep the layer of grease as thin as possible. Use quality grease, not pads or tape. They just don't work as well. Good silicone thermal grease should remain effective for at a minimum of 10 years. Also, clean your heat sinks! I clean the ones on my laptop about once a year (I have to remove the keyboard to blow them out) and I see the quiescent temperature drop by 10-15C and the temp under load can drop by 20C. As active cooling works on my laptop, it does not overheat, but it does slow down on "buildworld -j6" and building ports like chromium and libreoffice. Very significant. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683