Date: Thu, 2 Jun 2016 22:46:54 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Kevin Oberman <rkoberman@gmail.com> Cc: Hans Petter Selasky <hps@selasky.org>, RayCherng Yu <raycherng@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Suddenly poweroff in 11-Current r300097 Message-ID: <20160602224654.18927083.ohartman@zedat.fu-berlin.de> In-Reply-To: <CAN6yY1uxTdv0Gbh=A3vPRgSkboOb5dgjNRc0V9VrJvCqsSprZg@mail.gmail.com> References: <CAG2Wu4OtrDxRWMtYhOt2RNCEjryYuZzhYE=-WKH3t-153M9jJA@mail.gmail.com> <0448c751-8608-51ce-f47e-76280ebf14f2@selasky.org> <CAN6yY1uxTdv0Gbh=A3vPRgSkboOb5dgjNRc0V9VrJvCqsSprZg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Z5RU72DxlV4dX1TVk1zpYpZ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 2 Jun 2016 10:26:22 -0700 Kevin Oberman <rkoberman@gmail.com> schrieb: > On Thu, Jun 2, 2016 at 7:41 AM, Hans Petter Selasky <hps@selasky.org> wro= te: >=20 > > On 06/02/16 03:07, RayCherng Yu wrote: > > =20 > >> I got a suddenly poweroff in r300097 (and previous revision in April a= nd > >> May) when I built textproc/docproj. > >> My machine is Macbook Pro 13 2011 early. I have checked the Apple webs= ite. > >> 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 f= an > >> 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 > >> > >> =20 > > Hi, > > > > Do you have a temperature sysctl? Usually FreeBSD will shutdown the sys= tem > > 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 =20 >=20 >=20 > 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 u= p, > but before shutdown would be nice, too. >=20 > 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 ho= t. >=20 > 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 abo= ut > just what thermal control techniques are enabled. >=20 > Just to explain a bit on how this should work: when the temperature excee= ds > 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. >=20 > 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 "dr= ied 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 solv= ed the problem for my. In both cases, the former high-viscous thermal grease has become li= ke dry mud. Same with pads.=20 --Sig_/Z5RU72DxlV4dX1TVk1zpYpZ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXUJs+AAoJEOgBcD7A/5N8+pEH/0wkm1TNTzUuKOlZbFDDk1wS x0RaooNUiLXwvV1xtV5WG340UReIhOPyyQTekmAa3MpaJjKTtuw6gLuEsbavgC4i tnSxTLou/zk0f0YKXmABU/Smd6dZOeWaPtKvkuOfx/qlQn/AEDYizDS6+Bp4GBmH rfmAmzKQptRDL+ick4Cy2FiGWUleItn1hIdkhTM90TfOZbk/vavPE9FA3PPzNetf sTGsGnehflPI9uzWj3tBwmnTiyx3LLERlnTgSDjdrpHGDDSfx70KVC5EnZG+QQWg jyLc2NTIKtsphmWNTAB9SGoA75giPTmYR+2F99m1oHgz4hYPfMfo+GRsa/iNL6M= =lbfw -----END PGP SIGNATURE----- --Sig_/Z5RU72DxlV4dX1TVk1zpYpZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160602224654.18927083.ohartman>