From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753085AbdJLUIQ (ORCPT ); Thu, 12 Oct 2017 16:08:16 -0400 Received: from demfloro.ru ([188.166.0.225]:50312 "EHLO demfloro.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751900AbdJLUIO (ORCPT ); Thu, 12 Oct 2017 16:08:14 -0400 X-Greylist: delayed 369 seconds by postgrey-1.27 at vger.kernel.org; Thu, 12 Oct 2017 16:08:14 EDT Date: Thu, 12 Oct 2017 23:01:24 +0300 From: Dmitrii Tcvetkov To: Andy Lutomirski Cc: , Subject: Kernel freeze on AMD FX-9590 CPU during I/O Message-ID: <20171012230124.32550187@demfloro.ru> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.9 (--) X-Spam-Report: Spam detection software, running on the system "demfloro.ru", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Hello, Since linux kernel 4.14-rc1 almost any I/O has a chance to freeze kernel (no log in /dev/tty0 nor /dev/ttyS0 not netconsole, no ARP answer over network) on one of my machines. Compiling linux kernel reproduces the issue reliably so far. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Since linux kernel 4.14-rc1 almost any I/O has a chance to freeze kernel (no log in /dev/tty0 nor /dev/ttyS0 not netconsole, no ARP answer over network) on one of my machines. Compiling linux kernel reproduces the issue reliably so far. Bisecting between v4.13 and v4.14-rc1 led me to commit 94b1b03b519b81c494900cb112aa00ed205cc2d9 Also I created a bug in bugzilla, bisect log is attached there: https://bugzilla.kernel.org/show_bug.cgi?id=197209 Unfortunately I can't test reverting of the commit on current mainline due to revert conflicts and I don't know how to resolve them correctly. My machine: CPU: AMD FX-9590 RAM: non-ECC DDR 12 Gb Storage layout: btrfs on top LVM on top LUKS on top HDD