From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-4.2-testing test] 19031: regressions - FAIL
Date: Wed, 4 Sep 2013 14:18:50 -0400 [thread overview]
Message-ID: <20130904181850.GD6629@phenom.dumpdata.com> (raw)
In-Reply-To: <21031.19859.177411.926536@mariner.uk.xensource.com>
On Wed, Sep 04, 2013 at 04:11:15PM +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [xen-4.2-testing test] 19031: regressions - FAIL"):
> > It is interesting that it fails at the same problem the linux-real had
> > been failing. That is when doing rsync.
> >
> >
> > 5120 bytes (5.1 kB) copied, 0.0194138 s, 264 kB/s
> > 2013-09-04 04:42:13 Z execution took 19 seconds [**>30/2**]: ssh -o StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=100 -o ServerAliveInterval=100 -o PasswordAuthentication=no -o ChallengeResponseAuthentication=no -o UserKnownHostsFile=tmp/t.known_hosts_19031.test-amd64-i386-xend-qemut-winxpsp3 root@10.80.248.105 dd if=/dev/zero of=/dev/woodlouse/win.guest.osstest-disk count=10
> > 2013-09-04 04:42:13 Z executing rsync ... -p /home/xc_osstest/images/winxpsp3.iso root@10.80.248.105:/root/19031.test-amd64-i386-xend-qemut-winxpsp3.winxpsp3.iso
>
> This is obviously badly broken. It's copying a tiny known_hosts file,
> and it took 19 seconds.
>
> > Ian, is it possible to a bit more verbose - perhaps that will shed some light
> > at this awful speed.
>
> I could add a -v but I'm not sure it will be much more illuminating.
>
> > There does not seem to be anything about the 'tg3' blowing up?
> > Ian, would it also be able to get the interrupt count _Before_ and
> > _after_ the timeout? Perhaps the interrupts aren't going to the
> > device?
>
> Surely that wouldn't produce these symptoms...
Does this happen _only_ with 32-bit dom0? The theory about /proc/interrupts
is that the tg3 is not using the DMA API properly and the device driver
has submitted commands. The hardware sits there and occassionaly polls
instead of going over the commands quickly. That would explain the
slowness. But that won't explain why it works with 64-bit dom0s unless
there is some truncation of physical addresses.
Perhaps you could build with CONFIG_DEBUG_DMA_API=? Perhaps that will shed
some light on it?
prev parent reply other threads:[~2013-09-04 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 5:17 [xen-4.2-testing test] 19031: regressions - FAIL xen.org
2013-09-04 8:12 ` Jan Beulich
2013-09-04 14:50 ` Konrad Rzeszutek Wilk
2013-09-04 15:11 ` Ian Jackson
2013-09-04 18:18 ` Konrad Rzeszutek Wilk [this message]
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=20130904181850.GD6629@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).