Re: panic in 6.3-RELEASE when multi-cast client exits

2008-02-22 Thread Rob Watt
tephan Uphoff. > > I tested it today. > > Best, > George > > -- Rob Watt Hudson River Trading 212.479.3954 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"

panic in 6.3-RELEASE when multi-cast client exits

2008-02-18 Thread Rob Watt
acc in ?? () Thanks -- Rob Watt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: em driver packet loss in 6.2 amd64 (RELEASE and STABLE)

2007-04-02 Thread Rob Watt
was the same exact behavior that we saw with the earlier version of the em driver I figured it was the same bug resurfacing again. - Rob Watt On Mon, 2 Apr 2007, Rob Watt wrote: Hi, In 6.1-RELEASE there were a number of em driver stability and performance issues. We would regularly see

em driver packet loss in 6.2 amd64 (RELEASE and STABLE)

2007-04-02 Thread Rob Watt
LEASE SMP kernel. - Rob Watt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Intel em receive hang and possible pr #72970

2006-09-01 Thread Rob Watt
On Fri, 1 Sep 2006, Jack Vogel wrote: On 9/1/06, Rob Watt <[EMAIL PROTECTED]> wrote: This was my earlier point Rob, that delta of the driver WILL NOT build against 6.1 RELEASE, it has taskqueue changes in it that are not in the release, as well as a few other small gotchas. To get that f

Re: Intel em receive hang and possible pr #72970

2006-09-01 Thread Rob Watt
on been tested? Will that version play nicely with 6.1? Thanks! - Rob Watt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Intel em receive hang and possible pr #72970

2006-08-31 Thread Rob Watt
g in the past on these machines with tons of network/disk/cpu/memory activity all happening at the same time, and we've never encountered this bug. The fact that it is not easily repeatable makes it hard to test for. Any testing suggestions would also be appreciated.