From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [xen-unstable bisection] complete test-amd64-amd64-xl-xsm Date: Mon, 15 Jun 2015 10:41:03 +0100 Message-ID: <557E9DAF.9050106@citrix.com> References: <557EB73C0200007800084B5D@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z4QtL-0007wK-TW for xen-devel@lists.xenproject.org; Mon, 15 Jun 2015 09:41:20 +0000 In-Reply-To: <557EB73C0200007800084B5D@mail.emea.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 , xen-devel Cc: ian.jackson@eu.citrix.com, keir@xen.org, stefano.stabellini@eu.citrix.com List-Id: xen-devel@lists.xenproject.org On 15/06/15 10:30, Jan Beulich wrote: >>>> On 14.06.15 at 22:54, wrote: >> branch xen-unstable >> xen branch xen-unstable >> job test-amd64-amd64-xl-xsm >> test xen-boot >> >> Tree: linux git://xenbits.xen.org/linux-pvops.git >> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git >> Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git >> Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git >> Tree: xen git://xenbits.xen.org/xen.git >> >> *** Found and reproduced problem changeset *** >> >> Bug is in tree: xen git://xenbits.xen.org/xen.git >> Bug introduced: 73cb5d43a8f48930e4594ef7b15b974487651ffe >> Bug not present: 284ffb4f9b0d5c3a33c4c5bd87645d0cc342ca96 >> >> >> commit 73cb5d43a8f48930e4594ef7b15b974487651ffe >> Author: Jan Beulich >> Date: Thu Jun 11 11:53:20 2015 +0200 >> >> x86/MSI-X: use qword MMIO access for address writes >> >> Now that we support it for our guests, let's do so ourselves too. >> >> Signed-off-by: Jan Beulich >> Reviewed-by: Andrew Cooper > The only thing I can see us doing here is revert. Three machine > pairs are affected, yet each exhibits the problem in different ways: > - elbling[01] see tg3 transmit timeouts > - merlot[01] see SERR NMIs > - godello[01] appear to suffer from silent reboots > Other than assuming that the NICs of these systems (all using the > tg3 driver) don't properly support what the standard mandates I > have no explanation so far. Maybe once I run the code on a few > more systems here I can find one also showing such bad behavior. I can't explain this either. Best to revert for now. ~Andrew