Port-i386 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: wm(4) problems

        The dmesg output might be a good idea.  We're running a number of
wm(4) devices in our network, and we have virtually no trouble with them.
We have both copper and fiber-based wm(4) devices, and all work great.
This is with a mix of 3.0 and 3.1 kernels in production environments, so
they run for months and years at a time.

On Jan 12,  3:46am, Sridhar Ayengar wrote:
} Subject: Re: wm(4) problems
} Matthias Scheler wrote:
} > On 11 Jan 2008, at 22:48, Sridhar Ayengar wrote:
} >> The machine is currently running NetBSD/i386 3.0, but I've been 
} >> thinking about upgrading to amd64 4.0.  Will that help?
} > 
} > 
} > Yes, the wm(4) driver has been substantially improved since NetBSD 3.0 
} > was released.
} > Even NetBSD 3.1_STABLE ("netbsd-3" branch) contains a lot of improvements.
} Hi Matthias.
} I didn't feel like running a full upgrade right at the moment, so I just 
} got the 3.1.1 GENERIC kernel and booted it.  Unfortunately, I'm still 
} getting the same errors, as well as the interface flapping.  Any other 
} ideas?  BTW, I checked, and the card is a PRO/1000 Desktop Adapter.
} Do you think the card might be bad or something?  Do you need to see my 
} dmesg?
} Peace...  Sridhar
>-- End of excerpt from Sridhar Ayengar

Home | Main Index | Thread Index | Old Index