[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable test] 18851: regressions - FAIL [and 1 more messages]
>>> On 06.09.13 at 12:38, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote: > Jan Beulich writes ("Re: [xen-unstable test] 18851: regressions - FAIL"): >> This looks like a red herring. Having poked about in woodlouse it looks >> like something is screwy with interrupts. The tg3 cards aren't using >> MSI and the USB controller is using edge not level handlers. Another >> machine with the same chipset is happily using MSIs. > > I did the following tests overnight: > > * 3.4.60 kernel: > > Pass! [adhoc flight 19081] > > * 3.10.10 + patch from Zoltan Kiss to limit SKB_FRAG_PAGE_ORDER > Subject: net/core: Order-3 frag allocator causes SWIOTLB bouncing under > Xen > Date: Wed Sep 04 21:54:01 BST 2013 > Message-ID: <1378327638-23956-1-git-send-email-zoltan.kiss@xxxxxxxxxx> > > Fail as before (in this case, timeout in debootstrap trying to > install a geust). [adhoc flight 19082] > > * 3.10.10, kernel command line "pci=noacpi and pci=nocrs" > > Total boot failure. SATA controller complaining bitterly about > lost interrupts. [adhoc flight 19085] > > I also took woodlouse out of the main test pool, which is how we got a > push of 4.2. I'm going to put it back now, and make a change to > switch to Linux 3.4.y for general tests. For -unstable this also resulted in just a single left test failure (test-amd64-i386-pair 17 guest-migrate/src_host/dst_host), which appears to be the result of the migration, after the first few thousand pages, seeing a rapid decrease of speed (which then likely causes that timeout). I couldn't spot anything in the logs that would explain this though. But I did notice that in two of the three runs there was not xend.log captured on the source host in the first place - is there an explanation for this? In any event I'm going to take these almost-pushes as a "good enough" sign to pull over the two or three commits into the stable branches, in the expectation that we should be able to get a push there over the weekend, and then release early next week. Looking through the logs of *-mite it also seems like you gave 3.11 a try, hitting a BUG() in balloon.c. Jan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |