From: Auke Kok <auke-jan.h.kok@intel.com>
To: castet.matthieu@free.fr
Cc: e1000-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [E1000-devel] e1000 : link down issues
Date: Thu, 11 Jan 2007 09:17:02 -0800 [thread overview]
Message-ID: <45A6710E.1020506@intel.com> (raw)
In-Reply-To: <1168534773.45a66cf58d25e@imp4-g19.free.fr>
castet.matthieu@free.fr wrote:
> Hi,
>
> I got a 82566DM e1000 network controller [1] on my motherboard, and most of the
> time the link go down when doing dhcp. [2]
>
> ifconfig eth0 up -> link become up
> dhclient eth0 -> some packet are transmited and received and the link become
> down.
I'm unsure whether we saw this problem before or not but it does sound familiar. First I
would like to ask you to check your motherboards vendor website for a possible BIOS
update for your motherboard. The 82566DM chipsets are rather new and we have pushed out
NVM changes to vendors for some known issues.
> I sometimes got e1000_reset: Hardware Error.
>
> This happen with vanilla 2.6.19 and e1000-7.3.20 drivers.
>
> This is very anoying because I should do rmmod e1000; modprobe e1000; ifup e1000
> in loop until the link stay up. I try forcing speed, duplex and flow control, but
> nothing solve my issue.
>
> The device is working fine on windows.
unfortunately that doesn't say that much. I do know that we are queueing some ich8/82566
changes for the kernel and if you're willing to try them I can provide patch to the
kernel netdev tree to you (it was posted here 3 days ago) to try.
Cheers,
Auke
PS feel free to trim lkml from the CC to move this discussion further to e1000-devel
list only.
next prev parent reply other threads:[~2007-01-11 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:59 e1000 : link down issues castet.matthieu
2007-01-11 17:17 ` Auke Kok [this message]
2007-03-04 1:09 ` Kok, Auke
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=45A6710E.1020506@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=castet.matthieu@free.fr \
--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 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.