From: Adrian Bunk <bunk@stusta.de>
To: John covici <covici@ccs.covici.com>
Cc: linux-kernel@vger.kernel.org, cramerj@intel.com,
john.ronciak@intel.com, ganesh.venkatesan@intel.com,
netdev@oss.sgi.com
Subject: Re: e1000 not working using 2.6.11
Date: Sat, 11 Jun 2005 21:37:29 +0200 [thread overview]
Message-ID: <20050611193729.GJ3770@stusta.de> (raw)
In-Reply-To: <17064.41290.461755.920152@ccs.covici.com>
On Thu, Jun 09, 2005 at 04:06:34PM -0400, John covici wrote:
> Hi. I am not getting good results on a box I have which uses an Intel
> Pro gigabit Ethernet driver for its network connection. What happens
> is that I get messages like watchdog xmit timeout and lots of errors
> out of ifconfig. Here is the listpci entry for that card. It works
> under the other OS, so I imagine the hardware is OK.
>
> 0000:01:0b.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
> Subsystem: Intel Corp.: Unknown device 3013
> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19
> Memory at e7000000 (64-bit, non-prefetchable) [size=128K]
> Memory at e7020000 (64-bit, non-prefetchable) [size=64K]
> I/O ports at b400 [size=64]
> Capabilities: [dc] Power Management version 2
> Capabilities: [e4] PCI-X non-bridge device.
> Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
>
>
> Any assistance would be appreciated.
Does 2.6.12-rc6 work?
If not, the maintainers of this driver (Cc'ed) might be able to help
you.
> John Covici
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
parent reply other threads:[~2005-06-11 19:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17064.41290.461755.920152@ccs.covici.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=20050611193729.GJ3770@stusta.de \
--to=bunk@stusta.de \
--cc=covici@ccs.covici.com \
--cc=cramerj@intel.com \
--cc=ganesh.venkatesan@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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).