From: Robert Hancock <hancockr@shaw.ca>
To: Greg.Chandler@wellsfargo.com,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem
Date: Sun, 18 Mar 2007 13:41:01 -0600 [thread overview]
Message-ID: <45FD95CD.2030403@shaw.ca> (raw)
In-Reply-To: <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
Greg.Chandler@wellsfargo.com wrote:
> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot. The intel
> site shows this is a supported config for the card, but linux is pulling
> this info:
>
> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit Ethernet
> Controller (Fiber) (rev 02)
> Subsystem: Intel Corporation PRO/1000 XF Server Adapter
> Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
> Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
> Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
> I/O ports at 7000 [size=32]
> [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> Capabilities: [e4] PCI-X non-bridge device
> Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
>
> My thoughput tests show it is definitely not running at the 100Mhz bus
> rate is should be capable of.
How are you determining this?
> Any ideas on how to make it work at full speed?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-03-18 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
2007-03-18 19:41 ` Robert Hancock [this message]
2007-03-18 20:51 ` 1000xf bus problem Kok, Auke
2007-03-19 3:03 ` Greg.Chandler
2007-03-19 3:39 ` Kok, Auke
2007-03-19 3:48 ` Greg.Chandler
2007-03-19 2:53 ` Greg.Chandler
2007-03-19 5:20 ` Robert Hancock
2007-03-19 5:31 ` Willy Tarreau
2007-03-19 5:59 ` [E1000-devel] " Robin Humble
2007-03-19 6:56 ` Willy Tarreau
2007-03-18 18:51 Greg.Chandler
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=45FD95CD.2030403@shaw.ca \
--to=hancockr@shaw.ca \
--cc=Greg.Chandler@wellsfargo.com \
--cc=e1000-devel@lists.sourceforge.net \
--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