Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752664AbdI3CFT (ORCPT ); Fri, 29 Sep 2017 22:05:19 -0400 Received: from tartarus.angband.pl ([89.206.35.136]:47557 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752639AbdI3CFS (ORCPT ); Fri, 29 Sep 2017 22:05:18 -0400 Date: Sat, 30 Sep 2017 04:05:16 +0200 From: Adam Borowski To: linux-kernel@vger.kernel.org Subject: random insta-reboots on AMD Phenom II Message-ID: <20170930020516.sybqsf5yn2gzuph3@angband.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 825 Lines: 20 Hi! I'm afraid I see random instant reboots on current -rc, approximately once per day, only under CPU load. There's nothing on serial/etc -- just an immediate reboot. 4.13 works perfectly; last kernel I've tried is v4.14-rc2-165-g770b782f555d. gcc 7.2.0-7 (Debian). CPU is AMD Phenom II X6 1055T (family 10h). Sometimes it dies within a few minutes of load, sometimes all is fine for a couple of days. This randomness makes bisecting not really an option. Any hints how to debug this? Meow! -- ⢀⣴⠾⠻⢶⣦⠀ We domesticated dogs 36000 years ago; together we chased ⣾⠁⢰⠒⠀⣿⡁ animals, hung out and licked or scratched our private parts. ⢿⡄⠘⠷⠚⠋⠀ Cats domesticated us 9500 years ago, and immediately we got ⠈⠳⣄⠀⠀⠀⠀ agriculture, towns then cities. -- whitroth on /.