Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751335Ab3J0EpJ (ORCPT ); Sun, 27 Oct 2013 00:45:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33057 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750914Ab3J0EpH (ORCPT ); Sun, 27 Oct 2013 00:45:07 -0400 Date: Sun, 27 Oct 2013 12:44:33 +0800 From: Dave Young To: linux-kernel@vger.kernel.org Cc: kexec@lists.infradead.org, x86@kernel.org Subject: Re: query for idea about a kexec regression Message-ID: <20131027044433.GB18689@dhcp-16-126.nay.redhat.com> References: <20131027043023.GA18689@dhcp-16-126.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131027043023.GA18689@dhcp-16-126.nay.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 889 Lines: 27 typo: mail address of x86@kernel.org On 10/27/13 at 12:30pm, Dave Young wrote: > Hi > > While I testing efi runtime patches for kexec kernel, there's > 2 machines kexec fails on them. It can be reproduced with > non-efi kernel, so it's not related to the patchset. > > Problem is kexec kernel will immediatly reboot after below > kernel message: > smpboot: Booting Node 0, Processors # 1 > > The latter CPUs were not printed. > > nr_cpus=1 works, so there might be some bug on smp code. > > Any idea or suspection acout some patches? This is not 100% > reproducible, to me it's about 30% thus it's hard to bisect. > > Thanks > Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/