Re: e008:[<ffff82c480122353>] check_lock+0x1b/0x45

[Andrew Cooper <andrew.cooper3@citrix.com>]

On 19/06/13 18:01, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 19, 2013 at 05:37:01PM +0100, Andrew Cooper wrote:
>> On 19/06/13 17:06, Konrad Rzeszutek Wilk wrote:
>>> Hey,
>>>
>>> It looks like one of the patches that went in Xen 4.1 blows up.
>>>
>>> This used to work over the weekend, so I can only surmise
>>> it is one the three patches. This is with a debug=y build
>>> (which has been working nicely for the last month or more).
>>>
>>> It looks like one of the patches that went in Xen 4.1 blows up.
>>>
>>> This used to work a day ago - that is c/s 23551 worked nicely.
> And just to confirm, yes the same kernel but with cs 23551 boots
> (just built it). Let me narrow down which of the c/s is at fault.
>

There are only 3 changesets to choose from.  It can only really be

hg: 23552:d7ad3e2f1119
git: df751b6da15afff1f87a68f63013dd96e9563047

"x86: fix ordering of operations in destroy_irq()".

Is it possible for your to run tests with the same dom0 kernel but 4.2
or unstable around these changesets?  Unless it can be proved to only be
a problem with 4.1, I suspect we may want to back out the change,
especially given the proximity of 4.3

~Andrew