From: castet.matthieu@free.fr
To: e1000-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: e1000 : link down issues
Date: Thu, 11 Jan 2007 17:59:33 +0100 [thread overview]
Message-ID: <1168534773.45a66cf58d25e@imp4-g19.free.fr> (raw)
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 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.
What should I do ?
Thanks.
Matthieu CASTET
[1]
00:19.0 0200: 8086:104a (rev 02)
Subsystem: 103c:2800
[2]
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
None
e1000: eth0: e1000_watchdog: NIC Link is Down
e1000: 0000:00:19.0: e1000_validate_option: Flow Control Disabled
e1000: 0000:00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
00:0f:fe:77:08:a1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
None
e1000: eth0: e1000_watchdog: NIC Link is Down
e1000: 0000:00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
00:0f:fe:77:08:a1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
RX
e1000: eth0: e1000_watchdog: NIC Link is Down
e1000: 0000:00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
00:0f:fe:77:08:a1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
RX
e1000: eth0: e1000_watchdog: NIC Link is Down
e1000: 0000:00:19.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1)
00:0f:fe:77:08:a1
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
None
e1000: eth0: e1000_watchdog: NIC Link is Down
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
None
next reply other threads:[~2007-01-11 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 16:59 castet.matthieu [this message]
2007-01-11 17:17 ` [E1000-devel] " Auke Kok
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=1168534773.45a66cf58d25e@imp4-g19.free.fr \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®