On 2010.02.25 23:03, Doug Barton wrote:
> On 02/25/10 19:56, Steve Bertrand wrote:
>> Do you want more v6 traffic thrown at the interface for testing?
>
> Thanks for the offer, but the load I have on it now is the same as what
> I had when I got the crashes, so I think it will either work, or it w
On 02/25/10 19:56, Steve Bertrand wrote:
> Do you want more v6 traffic thrown at the interface for testing?
Thanks for the offer, but the load I have on it now is the same as what
I had when I got the crashes, so I think it will either work, or it will
not work. :)
19+ hours and counting
D
On 2010.02.25 16:45, Doug Barton wrote:
> On 02/24/10 14:17, Li, Qing wrote:
>> Please try this patch
>>
>> http://people.freebsd.org/~qingli/nd6.c.diff
>>
>> and let me know if it works out for you.
>>
>> Thanks,
>>
>> -- Qing
>
> Thank YOU. :) Uptime is 12 hours so far, with fairly continuo
On 02/24/10 14:17, Li, Qing wrote:
> Please try this patch
>
> http://people.freebsd.org/~qingli/nd6.c.diff
>
> and let me know if it works out for you.
>
> Thanks,
>
> -- Qing
Thank YOU. :) Uptime is 12 hours so far, with fairly continuous (albeit
light) IPv6 traffic and so far so good.
On Wednesday 24 February 2010 7:23:44 pm Ivan Voras wrote:
> Ivan Voras wrote:
> > I have a fairly recent 8-stable machine running under VMWare ESXi 3.5
> > (amd64 guest), which apparently crashes every few days from the same
> > causes:
> >
> > em0: discard frame w/o packet header
> > em0: disc
Kirk Davis wrote on 2010-02-23 23:26:
I noticed that fastforwarding ( net.inet.ip.fastforwarding=1 ) was
turned on. I turned it off to see if that was causing the problem.
Sure enough, 5 hours later and no watchdog timeouts. This is still
running on FreeBSD 7.1 (I'm still planning to move
On 25 February 2010 02:31, Jack Vogel wrote:
> Hmmm, not sure what changes are in this, what if you use the 8.0 REL
> driver, does it still happen?
Yes, this is why it is now running 8-STABLE.
I have more FreeBSD guests on the same VMWare hosts which work fine,
but this is the only 64-bit one.
The following reply was made to PR kern/144000; it has been noted by GNATS.
From: Andrey Zonov
To: bug-follo...@freebsd.org, j...@freebsd.org
Cc:
Subject: Re: kern/144000: [tcp] ignore set TCP_MAXSEG by setsockopt()
Date: Thu, 25 Feb 2010 11:49:00 +0300
--00151758b020ad57aa048068da47
Content