NetBSD-Users archive

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

Re: wm(4) problems

Brian Buhrow wrote:
        Is it possible you have a bad ethernet cable?  That kind of error
sounds like either a bad cable or a bad port on the switch.  I'm not saying
it's not a driver bug, but if it's generating CRC errors on the other side,
that's sounding very hardwareish!

I might try swapping the card later tonight.

I don't think it's a switch port, since I've tried more than one switch, and more than one port on each switch. I don't think it's the cable, since I've tried three different cables.

Peace...  Sridhar


On Jan 12,  8:33pm, Sridhar Ayengar wrote:
} Subject: Re: wm(4) problems
} Brian Buhrow wrote:
} >  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.
} } I'll get you the dmesg as soon as the ethernet interface comes back up. } } Peace... Sridhar
-- End of excerpt from Sridhar Ayengar

Home | Main Index | Thread Index | Old Index