Subject: Re: [OOPS] [XEN] OOPS early after boot on master
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Bryan Donlan <bdonlan@gmail.com>
CC: Jeremy Fitzhardinge <jeremy@goop.org>, LKML <linux-kernel@vger.kernel.org>,
       <xen-devel@lists.xensource.com>
In-Reply-To: <3e8340490906111555r313ff6e9nce956fc76eff7382@mail.gmail.com>
References: <3e8340490906071010l33ceaf5eh304e163178384592@mail.gmail.com>
	 <3e8340490906081305u1ad00ba7s78b367e4fa8973c4@mail.gmail.com>
	 <4A317433.5000700@goop.org>
	 <3e8340490906111555r313ff6e9nce956fc76eff7382@mail.gmail.com>
Content-Type: text/plain
Organization: Citrix Systems, Inc.
Date: Mon, 15 Jun 2009 08:13:59 +0100
Message-ID: <1245050039.5782.867.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 861
Lines: 20

On Thu, 2009-06-11 at 18:55 -0400, Bryan Donlan wrote:
> On further analysis, it seems that that's a red herring - disabling PV
> spinlocks just makes it occur less often, I think... I'm currently
> still bisecting it; it's complicated by other OOPS-causing bugs having
> existed in the interim, but it definitely existed before the
> introduction of CONFIG_PARAVIRT_SPINLOCKS.

It's worth bearing in mind that prior to CONFIG_PARAVIRT_SPINLOCKS the
pv spinlock functionality was already present but not optional so it's
not unlikely that an issue with pv spinlocks could predate the addition
of the option.

Ian.


--
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/