Re: [Xen-devel] [xen-unstable test] 24250: tolerable FAIL

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-01-08 at 10:59 +0000, Jan Beulich wrote:
> >>> On 08.01.14 at 11:49, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> > On Tue, 2014-01-07 at 12:29 +0000, Jan Beulich wrote:
> >> >>> On 06.01.14 at 10:36, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> >> > flight 24250 xen-unstable real [real]
> >> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24250/ 
> >> > 
> >> > Failures :-/ but no regressions.
> >> > 
> >> > Regressions which are regarded as allowable (not blocking):
> >> >  test-armhf-armhf-xl           7 debian-install               fail   
> >> > like 
> > 24146
> >> >  test-amd64-i386-xl-winxpsp3-vcpus1  7 windows-install          fail 
> >> > like 
> > 23938
> >> >  test-amd64-i386-xl-win7-amd64  7 windows-install              fail  
> >> > like 
> > 24146
> >> 
> >> These windows-install failures have been pretty persistent for
> >> the last month or two. I've been looking at the logs from the
> >> hypervisor side a number of times without spotting anything. It'd
> >> be nice to know whether anyone also did so from the tools and
> >> qemu sides... In any event we will need to do something about
> >> this before 4.4 goes out.
> > 
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24250/test-amd64-i386-xl-wi
> >  
> > n7-amd64/win.guest.osstest--vnc.jpeg
> > 
> > says that Windows experienced an unexpected error.
> > 
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/24250/test-amd64-i386-xl-wi
> >  
> > nxpsp3-vcpus1/win.guest.osstest--vnc.jpeg
> > 
> > is a blue screen "BAD_POOL_CALLER".

FWIW It's code 0x7 which
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560185%28v=vs.85%29.aspx
says is "The current thread attempted to free the pool, which was
already freed.".

The Internet(tm) seems to think this is often a driver issue. Not that
this helps us much!

> > I think this is unlikely to be a toolstack thing, but as to whether it
> > is a Xen or a Windows issue I wouldn't like to say. I had a look through
> > the toolstack logs anyway and didn't see anything untoward.
> 
> Right, neither did I. I was particularly thinking of qemu though,
> since I think these pretty persistent failures started around the
> time the qemu tree upgrade was done. Of course this could just
> be coincidence with a hypervisor side change having bad effects.

If there is a correlation then it would be interesting to investigate --
Anthony/Stefano could you guys have a look please.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel