From: Shawn Starr <shawn.starr@rogers.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: Re: [2.6.10-rc1-bk5] e1000 broken badly on IBM T42
Date: Wed, 27 Oct 2004 05:21:56 -0400 [thread overview]
Message-ID: <200410270521.56816.shawn.starr@rogers.com> (raw)
In-Reply-To: <200410270054.30313.shawn.starr@rogers.com>
I should just answer it myself, restarting fixed the interface negotiation
'blip'. Perhaps the driver somehow did not reset and retry negotiation?
That did look interesting though :)
On October 27, 2004 00:54, Shawn Starr wrote:
> I should also note, there is no gigabit interface on a linksys router ;-)
> it doesn't negotiate as 100Mbit now?
>
> Shawn.
>
> On October 27, 2004 00:33, Shawn Starr wrote:
> > NETDEV WATCHDOG: eth0: transmit timed out
> > e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
> > NETDEV WATCHDOG: eth0: transmit timed out
> >
> > eth0 Link encap:Ethernet HWaddr 00:0D:60:CA:C1:97
> > inet addr:192.168.10.5 Bcast:192.168.10.255
> > Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:4294883167 errors:4294370903 dropped:4294796898
> > overruns:4294882097 frame:4294711699 TX packets:4294883949
> > errors:4294796898 dropped:0 overruns:0 carrier:4294711699
> > collisions:4294882097 txqueuelen:1000
> > RX bytes:470309 (459.2 KiB) TX bytes:108971 (106.4 KiB)
> > Base address:0x8000 Memory:c0220000-c0240000
> >
> >
> > I can't even use the interface, some counters are going up others going
> > backwards? ;-)
> >
> > Anyone notice this?
> >
> > Shawn.
next parent reply other threads:[~2004-10-27 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410270033.22804.shawn.starr@rogers.com>
[not found] ` <200410270054.30313.shawn.starr@rogers.com>
2004-10-27 9:21 ` Shawn Starr [this message]
2004-10-27 15:51 ` [2.6.10-rc1-bk5] e1000 broken badly on IBM T42 Lee Revell
2004-10-27 21:41 ` Shawn Starr
2004-11-14 20:25 ` James Turner
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=200410270521.56816.shawn.starr@rogers.com \
--to=shawn.starr@rogers.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).