Re: ns83820 - Strange behavior w/Dlink DGE-500T

Re: ns83820 - Strange behavior w/Dlink DGE-500T

[Xose Vazquez Perez]

Brian McGroarty wrote:

> With a Dlink DGE-550T and the 2.4.22 ns83820 driver, I'm seeing

DGE-550T works with dl2k driver.

-- 
Software is like sex, it's better when it's bug free.

Re: ns83820 - Strange behavior w/Dlink DGE-500T

[Brian McGroarty]

On Fri, Oct 17, 2003 at 02:45:39AM +0200, Xose Vazquez Perez wrote:
> Brian McGroarty wrote:
> 
> > With a Dlink DGE-550T and the 2.4.22 ns83820 driver, I'm seeing
> 
> DGE-550T works with dl2k driver.

A typo -- this problem is with the DGE-500T as mentioned in the
subject line, not DGE-550T as I said in the body.

ns83820 - Strange behavior w/Dlink DGE-500T

[Brian McGroarty]

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.