All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: ian.jackson@eu.citrix.com, keir@xen.org,
	stefano.stabellini@eu.citrix.com
Subject: Re: [xen-unstable bisection] complete test-amd64-amd64-xl-xsm
Date: Mon, 15 Jun 2015 10:41:03 +0100	[thread overview]
Message-ID: <557E9DAF.9050106@citrix.com> (raw)
In-Reply-To: <557EB73C0200007800084B5D@mail.emea.novell.com>

On 15/06/15 10:30, Jan Beulich wrote:
>>>> On 14.06.15 at 22:54, <osstest@xenbits.xen.org> 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 <jbeulich@suse.com>
>>   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 <jbeulich@suse.com>
>>       Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> 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

  reply	other threads:[~2015-06-15  9:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 20:54 [xen-unstable bisection] complete test-amd64-amd64-xl-xsm osstest service user
2015-06-15  9:01 ` Ian Campbell
2015-06-15  9:05   ` Jan Beulich
2015-06-15  9:30 ` Jan Beulich
2015-06-15  9:41   ` Andrew Cooper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-22  7:44 osstest service owner
2020-10-01 16:50 osstest service owner
2020-11-09 22:15 osstest service owner
2022-12-17  3:21 osstest service owner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=557E9DAF.9050106@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.