From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753297AbdLMPzE (ORCPT ); Wed, 13 Dec 2017 10:55:04 -0500 Received: from mga03.intel.com ([134.134.136.65]:46319 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751026AbdLMPzD (ORCPT ); Wed, 13 Dec 2017 10:55:03 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,397,1508828400"; d="scan'208";a="12245163" Date: Wed, 13 Dec 2017 23:57:46 +0800 From: Yu Chen To: Dave Young Cc: Thomas Gleixner , Juergen Gross , Tony Luck , Boris Ostrovsky , Borislav Petkov , Rui Zhang , Arjan van de Ven , Dan Williams , mingo@kernel.org, Yu Chen , kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: Regression: kexec/kdump boot hangs with x86/vector commits Message-ID: <20171213155746.GA29572@yu-chen.sh.intel.com> References: <20171213025256.GA1913@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171213025256.GA1913@dhcp-128-65.nay.redhat.com> User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 13, 2017 at 10:52:56AM +0800, Dave Young wrote: > Hi, > > Kexec reboot and kdump has broken on my laptop for long time with > 4.15.0-rc1+ kernels. With the patch below an early panic been fixed: > https://patchwork.kernel.org/patch/10084289/ > > But still can not get a successful reboot, it looked like graphic > issue, but after bisecting the kernel, I got below: > > [dyoung@dhcp-*-* linux]$ git bisect good > There are only 'skip'ped commits left to test. > The first bad commit could be any of: > 2db1f959d9dc16035f2eb44ed5fdb2789b754d6a > 4900be83602b6be07366d3e69f756c1959f4169a > We cannot bisect more! > > These two commits can no be reverted because of code conflicts, thus > I reverted the whole series from Thomas (below commits), with those > x86/vector changes reverted, kexec reboot works fine. > > Could you help to take a look, any thoughts? I can do the test > if you have some debug patch to try. Is it possible that the "second" kernel runs on non-zero CPU? If yes, what if some irqs are only delivered to cpu0? (use cpumask_of(0) directly) Thanks, Yu From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga05.intel.com ([192.55.52.43]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1eP9NT-0001UC-DY for kexec@lists.infradead.org; Wed, 13 Dec 2017 15:55:25 +0000 Date: Wed, 13 Dec 2017 23:57:46 +0800 From: Yu Chen Subject: Re: Regression: kexec/kdump boot hangs with x86/vector commits Message-ID: <20171213155746.GA29572@yu-chen.sh.intel.com> References: <20171213025256.GA1913@dhcp-128-65.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20171213025256.GA1913@dhcp-128-65.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Dave Young Cc: Juergen Gross , Tony Luck , Yu Chen , kexec@lists.infradead.org, mingo@kernel.org, Dan Williams , linux-kernel@vger.kernel.org, Rui Zhang , Borislav Petkov , Thomas Gleixner , Arjan van de Ven , Boris Ostrovsky On Wed, Dec 13, 2017 at 10:52:56AM +0800, Dave Young wrote: > Hi, > > Kexec reboot and kdump has broken on my laptop for long time with > 4.15.0-rc1+ kernels. With the patch below an early panic been fixed: > https://patchwork.kernel.org/patch/10084289/ > > But still can not get a successful reboot, it looked like graphic > issue, but after bisecting the kernel, I got below: > > [dyoung@dhcp-*-* linux]$ git bisect good > There are only 'skip'ped commits left to test. > The first bad commit could be any of: > 2db1f959d9dc16035f2eb44ed5fdb2789b754d6a > 4900be83602b6be07366d3e69f756c1959f4169a > We cannot bisect more! > > These two commits can no be reverted because of code conflicts, thus > I reverted the whole series from Thomas (below commits), with those > x86/vector changes reverted, kexec reboot works fine. > > Could you help to take a look, any thoughts? I can do the test > if you have some debug patch to try. Is it possible that the "second" kernel runs on non-zero CPU? If yes, what if some irqs are only delivered to cpu0? (use cpumask_of(0) directly) Thanks, Yu _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec