On Fri, Sep 04, 2009 at 02:22:23PM -0700, Pyun YongHyeon wrote:
>
> Would you back out previous changes and apply the patch at the
> following URL?
> http://people.freebsd.org/~yongari/msk/msk.DGE560.diff2
>
> Note, I have no more access to msk(4) hardwares so it wasn't tested
> at all except com
Stef Walter wrote:
Stef Walter wrote:
On a new VPN server, running OSPF, I'm experiencing regular panics at:
imo_match_source: !AF_INET
BTW, src->sa_family is 0
Moved back to FreeBSD 7.1 i386 and the problem goes away.
Full OS version, dmesg, panic and backtrace please, when rep
[Brief reply as I'm meant to be doing a zillion other things...]
Bruce Simpson wrote:
Full OS version, dmesg, panic and backtrace please, when reporting
this kind of issue... otherwise folk can't help. Are you using SSM
multicast features?
P.S. You might want to try demoting the KASSERT to
Shteryana Shopova wrote:
Hi,
I actually managed to get the same kernel dump using the following
sample code - http://people.freebsd.org/~syrinx/mcast/mcast_crash.c
and the crash is 100% reproducable. A temporary fix is here -
http://people.freebsd.org/~syrinx/mcast/in_mcast.c-20090908-01.diff
Hi,
I actually managed to get the same kernel dump using the following
sample code - http://people.freebsd.org/~syrinx/mcast/mcast_crash.c
and the crash is 100% reproducable. A temporary fix is here -
http://people.freebsd.org/~syrinx/mcast/in_mcast.c-20090908-01.diff
but I actually prefer that
Bruce Simpson wrote:
> Full OS version, dmesg, panic and backtrace please, when reporting this
> kind of issue... otherwise folk can't help.
Thanks for taking a look. It was linked in the parent post:
> This is the stack trace:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/137164&cat=
> Are
Shteryana Shopova wrote:
> I actually managed to get the same kernel dump using the following
> sample code - http://people.freebsd.org/~syrinx/mcast/mcast_crash.c
> and the crash is 100% reproducable. A temporary fix is here -
> http://people.freebsd.org/~syrinx/mcast/in_mcast.c-2009
Bruce Simpson wrote:
> [Brief reply as I'm meant to be doing a zillion other things...]
>
> Bruce Simpson wrote:
>>
>> Full OS version, dmesg, panic and backtrace please, when reporting
>> this kind of issue... otherwise folk can't help. Are you using SSM
>> multicast features?
>
> P.S. You might
On Sep 7, 2009, at 15:10 , Chris Cowart wrote:
George Neville-Neil wrote:
On Sep 4, 2009, at 18:31 , Chris Cowart wrote:
Starting about a week ago, our primary webserver (then running
FreeBSD
7.0) began crashing several times a day, typically during our
higher-load times of day. We have sin
Old Synopsis: lagg port bpf-writes blocked
New Synopsis: [lagg] [patch] lagg port bpf-writes blocked
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Sep 8 18:02:22 UTC 2009
Responsible-Changed-Why:
Over to maintainer(s).
http:/
Old Synopsis: race at vap destroy
New Synopsis: [ndis] [patch] race at vap destroy
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Sep 8 18:08:44 UTC 2009
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/c
grarpamp wrote:
Wouldn't it be better to support the obvious formal emergent standards
track protocol instead of the legacy informational one? Or to perform
both via sysctl or other arguments/defines, with the standard IPFIX
being the default mode? Have you reviewed the nProbe code for other
vari
Synopsis: [zyd] [usb8] "zyd0: device timeout" with ZyXEL G-202
Responsible-Changed-From-To: freebsd-net->weongyo
Responsible-Changed-By: weongyo
Responsible-Changed-When: Tue Sep 8 20:39:37 UTC 2009
Responsible-Changed-Why:
grap.
http://www.freebsd.org/cgi/query-pr.cgi?pr=138292
On Tue, Sep 08, 2009 at 10:50:30AM +0300, Eugene Perevyazko wrote:
> On Fri, Sep 04, 2009 at 02:22:23PM -0700, Pyun YongHyeon wrote:
> >
> > Would you back out previous changes and apply the patch at the
> > following URL?
> > http://people.freebsd.org/~yongari/msk/msk.DGE560.diff2
> >
> > Note,
--- On Fri, 9/4/09, Manish Vachharajani wrote:
> From: Manish Vachharajani
> Subject: Re: em driver input errors
> To: alexpalias-bsd...@yahoo.com
> Cc: freebsd-net@freebsd.org, "Artis Caune"
> Date: Friday, September 4, 2009, 1:41 PM
> Just decided to follow this thread as
> it seems to be r
At 05:42 PM 9/8/2009, Barney Cordoba wrote:
Manish What specific kinds of input errors are you getting? How many
PPS are you doing, what is the size of the ring, and the interrupt
modulation rate? Are the NICs PCIe or PCIx? Barney
In my case, our backup server (mix of dump via nfs and some dum
> Thanks for pointing out those RFCs.
Sure. There are more I probably missed.
Search rfc-editor or ietf for netflow or ipfix.
> can v5 count ipv6 ? No, what's next netflow version can ? v9? Ok, let's
> implement v9.
Yep, ipv6 is becoming really important, definitely on backbones. nProbe
has ha
t it has been the historical
behavior. One can see people coding against this in routing software [2].
Besides fixing the problem of dropping membership on the first
interface, the effect of this patch is to restore the previous freebsd
behavior.
Cheers,
Stef
PS: BTW, I've been using the patch
18 matches
Mail list logo
