> Whatever it is, results in ping times being 1000ms then 10ms then 1000ms > then 10ms...when it responds. > > i.e. it's a mistake to use FreeBSD 3.x with the 3c589d. FWIW, I'm using the 3c589d with 3.2-STABLE + PAO, and it's working just fine. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: 4.0 code freeze scheduled for Jan 15th Dave Cornejo
- Re: 4.0 code freeze scheduled for Jan 15th Jordan K. Hubbard
- Re: 4.0 code freeze scheduled for Jan 15th Frank Mayhar
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Darren Reed
- Re: 4.0 code freeze scheduled for Jan 15th Amancio Hasty
- Re: 4.0 code freeze scheduled for Jan 15th Josef Karthauser
- Re: 4.0 code freeze scheduled for Jan 15th Tom Bartol
- Re: 4.0 code freeze scheduled for Jan 15th Warner Losh
- Re: 4.0 code freeze scheduled for Jan 15th Darren Reed
- 3c589d problem sthaug
- 3c589d problem Mike Smith
- 3C589 problems (was: 4.0 code freeze scheduled for ... Greg Lehey
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Warner Losh
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Jonathan Chen
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Frank Mayhar
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Greg Lehey
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Frank Mayhar
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Matthew N. Dodd
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Will Andrews
- Re: 3C589 problems (was: 4.0 code freeze scheduled ... Warner Losh