From: Brian McGroarty <brian@mcgroarty.net>
To: linux-kernel@vger.kernel.org
Subject: ns83820 - Strange behavior w/Dlink DGE-500T
Date: Thu, 16 Oct 2003 19:09:54 -0500 [thread overview]
Message-ID: <20031017000954.GA10635@mcgroarty.net> (raw)
With a Dlink DGE-550T and the 2.4.22 ns83820 driver, I'm seeing some
peculiar behavior. After installing the kernel module and bringing up
the interface, I see a lot of:
Oct 16 18:44:39 slate kernel: eth0: link now 1000 mbps, full duplex and up.
Oct 16 18:44:42 slate kernel: eth0: link now down.
Oct 16 18:44:45 slate kernel: eth0: link now 1000 mbps, full duplex and up.
Oct 16 18:44:47 slate kernel: eth0: link now down.
Oct 16 18:44:50 slate kernel: eth0: link now 1000 mbps, full duplex and up.
Oct 16 18:44:53 slate kernel: eth0: link now down.
Oct 16 18:44:55 slate kernel: eth0: link now 1000 mbps, full duplex and up.
Oct 16 18:44:58 slate kernel: eth0: link now down.
Oct 16 18:45:01 slate kernel: eth0: link now 1000 mbps, full duplex and up.
Adding several seconds of sleep after the insmod and again after bringing
the interface up makes just one or two of these happen.
Attempting net traffic without the sleep commands leaves the above
bouncing happening continuously until traffic attempts stop.
Once the network is up, the bouncing never happens anymore.
I've tried two different DGE-550Ts, a different switch, and a
different cable, but the problem seems consistent.
next reply other threads:[~2003-10-17 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 0:09 Brian McGroarty [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 0:45 ns83820 - Strange behavior w/Dlink DGE-500T Xose Vazquez Perez
2003-10-17 0:51 ` Brian McGroarty
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=20031017000954.GA10635@mcgroarty.net \
--to=brian@mcgroarty.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.