From: Francois Romieu <romieu@cogenit.fr>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to debug PCI issues?
Date: Fri, 28 Sep 2001 10:30:12 +0200 [thread overview]
Message-ID: <20010928103012.A17549@se1.cogenit.fr> (raw)
In-Reply-To: <3BB3CFFA.F9021469@candelatech.com>
In-Reply-To: <3BB3CFFA.F9021469@candelatech.com>; from greearb@candelatech.com on Thu, Sep 27, 2001 at 06:18:50PM -0700
Ben Greear <greearb@candelatech.com> :
[...]
> So, I'm thinking that the DLINK NIC must be screwing up the PCI
> bus somehow when more than one of it's interfaces is passing any
> significant traffic. I have been able to run 10Mbps on all 8 ports
> of two DLINKs on an Intel EEA2 (i815) board, so I suspect the MB.
>
> Does anyone have any ideas how to go about trouble-shooting this
> farther?
Check the pci latency timer settings for the devices are the same
on the two mobos and force them with setpci if they aren't.
--
Ueimor
next prev parent reply other threads:[~2001-09-28 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 1:18 How to debug PCI issues? Ben Greear
2001-09-28 8:30 ` Francois Romieu [this message]
2001-09-28 10:40 ` Martin Josefsson
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=20010928103012.A17549@se1.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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