From: James Bottomley <James.Bottomley@SteelEye.com>
To: Stan Sieler <sieler@allegro.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C3000 HPMC with high NFS traffic. 99% it's ASTRO's
Date: 13 Aug 2004 13:06:58 -0400 [thread overview]
Message-ID: <1092416823.2186.70.camel@mulgrave> (raw)
In-Reply-To: <200408131656.i7DGuWF19777@opus.allegro.com>
On Fri, 2004-08-13 at 12:56, Stan Sieler wrote:
> If it helps, the instruction trapping appears to be:
> LDWAX 0(0,19),19
> and r19 has fed30000 ... an I/O space address.
Actually that's the back end of a LBA I/O cycle generation (this is the
actual read that guarantees completion semantics---see lba_pci.c). The
HPMC occurred because port 0x1008 timed out on an outl, I think.
That's tulip register CSR1 (i.e. the tulip driver was trying to force an
immediate transmit). I assume this must be either because the tulip
failed to respond to the outl in time or because the Astro couldn't get
on the bus in time.
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
parent reply other threads:[~2004-08-13 17:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200408131656.i7DGuWF19777@opus.allegro.com>]
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=1092416823.2186.70.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=sieler@allegro.com \
/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.