From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH] xen/kexec: Prevent deadlock because of one_cpu_only() Date: Mon, 8 Apr 2013 10:47:30 +0100 Message-ID: <51629232.1020207@citrix.com> References: <5160394F.3020908@citrix.com> <5162926402000078000CB3AA@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5162926402000078000CB3AA@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 08/04/13 08:48, Jan Beulich wrote: >>>> On 06.04.13 at 17:03, Andrew Cooper wrote: >> I can probably fix the acpi_dmar_reinstate() and kexec_crash_save_cpu() >> issues without too much problem and will look into those in due course, >> but my next task is to see whether there was a programatic reason as to >> why the wait descriptor was not executed successfully. > Was that perhaps still without the Intel chipset interrupt remapping > errata workaround? These errata can - afaict - have exactly that > panic as a symptom. > > Jan > This is not from an affected system; It is Sandy-Bridge EP (And we have the workaround in place anyway), although we too saw these symptoms for the errata-affected systems. I am double checking the errata docs, given the similarity. ~Andrew