Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757798AbcC2RKg (ORCPT ); Tue, 29 Mar 2016 13:10:36 -0400 Received: from smtp1.mail.ru ([94.100.179.111]:46370 "EHLO smtp1.mail.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753409AbcC2RKe (ORCPT ); Tue, 29 Mar 2016 13:10:34 -0400 Subject: Re: kvm: repeatable kernel crash with Athlon II cpu To: Paolo Bonzini , kvm@vger.kernel.org References: <56FA9DB1.4060704@list.ru> <56FAA135.1080600@redhat.com> <56FAA88C.3050800@list.ru> <56FAACDC.1010802@redhat.com> Cc: Stas Sergeev , Linux kernel , X86 ML From: Stas Sergeev Message-ID: <56FAB6FC.2000204@list.ru> Date: Tue, 29 Mar 2016 20:10:20 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <56FAACDC.1010802@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Mras: Ok Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1110 Lines: 30 29.03.2016 19:27, Paolo Bonzini пишет: > On 29/03/2016 18:08, Stas Sergeev wrote: >>>> I've been running dosemu and found out that it hangs >>>> or reboots one of my PCs. This happens with any fedora-23 >>>> kernels and hand-compiled kernels. The latest I tried, were: >>>> 4.4.6-300.fc23.x86_64 >>>> 4.5.0-rc6 >>> >>> Can you check if 4.3 works? >> >> Same crash on kernel-4.2.3-300.fc23.x86_64 - the oldest >> available for f23. >> >>>>>> Hope someone can find such an old CPU an reproduce the problem. >>>>>> Please let me know what info should I provide or what debugging >>>>>> to do to help getting that fixed. >>>> >>>> Do you have experience bisecting the kernel? If so perhaps you can try >>>> doing that. >> But it looks like a genuine bug, not a regression. > > Yeah, I was hoping it was introduced recently. > >> Of course I can check some 3.x versions... > > That would help a lot, thanks. Same on 3.18, and that's the oldest kernel that can be built on f23 (gcc5). So that's a genuine bug after all, not a regression. So does anyone have the AMD AthlonII X2 245 to try reproducing this?