Bug in sbsndptr()
Hi Andre, A colleague and I spent a very frustrating day tracing an accounting bug in the multipath TCP patch we're working on at CAIA to a bug in sbsndptr(). I haven't tested it with regular TCP yet, but I believe the following patch fixes the bug (proposed commit log message is at the top of the patch): http://people.freebsd.org/~lstewart/patches/misctcp/sbsndptr_mnext_10.x.r247314.diff The patch should have no tangible effect to operation other than to ensure the function delivers on the promise to return the closest mbuf in the chain for the given offset. I would appreciate a review and any thoughts. Cheers, Lawrence ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Clarifications required in rn_delete
Am 26.02.2013 17:56, schrieb Dheeraj Kandula: Here x will always be an internal node and hence if (m->rm_bit >= b_leaf) will always fail as b_leaf is a signed short and rm_bit is a signed short too and b_leaf is negative as b_leaf is -1 -t->rn_bit. *Isn't it? Is this a bug in the code.* at least there is a bug with radix_mpath; I had problems with no more existing leafs. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/173477 -- Mit freundlichen Grüßen, With best regards, Ingo Flaschberger Geschäftsleitung --- Beschreibung: Beschreibung: Beschreibung: logo_email2 *Besondere Ansprüche. Individuelle Lösungen. Particular demands. **Individual solutions.*** crossip communications gmbh A-1020 Wien, Wohlmutstrasse 27 Sitz der Gesellschaft: 1020 Wien, Österreich Firmenbuchgericht: Handelsgericht Wien, FN 269698 s, Umsatzsteueridentifikationsnummer (UID): ATU62080367 Haftungsausschluss / Disclaimer: _http://www.crossip.net/de/legal/haftungsausschluss-disclaimer_ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout
Hi. On 25.02.2013 14:20, YongHyeon PYUN wrote: On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote: Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a): We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed 9.1-RELEASE, and it looks like all of the hardware is detected properly, and being configured … After reboot, I start getting the 'watchdog timeout - resetting' message on bge0 … I've searched the web, and found the references to setting: Have a look at the following patch: http://svnweb.freebsd.org/base?view=revision&revision=243546 When I encountered the same error on Dell machines, using bge driver from HEAD helped me, although it seems that the aforementioned patch should be enough. That change is just one of changes required to make BCM5718/5718/5719/5720 work. You need entire bge(4)/brgphy(4) changes to get working bge(4) driver on your machines. Just to clear some things: this (or earlier changes) doesn't affect and doesn't enable IPMI sol and stuff on a BCM5722 ? Thanks. Eugene. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST
Old Synopsis: Concurrency in ixgbe driving out-of-order packet process and spurious RST New Synopsis: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:09:22 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176446 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/176419: [kernel] [patch] socketpair support for LOCAL_PEERCRED
Old Synopsis: [patch] socketpair support for LOCAL_PEERCRED New Synopsis: [kernel] [patch] socketpair support for LOCAL_PEERCRED Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:19:05 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176419 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/176420: [kernel] [patch] incorrect errno for LOCAL_PEERCRED
Old Synopsis: [patch] incorrect errno for LOCAL_PEERCRED New Synopsis: [kernel] [patch] incorrect errno for LOCAL_PEERCRED Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:19:39 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176420 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout
On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote: > Hi. > > On 25.02.2013 14:20, YongHyeon PYUN wrote: > >On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote: > >>Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisał(a): > >>>We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just > >>>installed > >>>9.1-RELEASE, and it looks like all of the hardware is detected properly, > >>>and being configured … > >>> > >>>After reboot, I start getting the 'watchdog timeout - resetting' message > >>>on > >>>bge0 … I've searched the web, and found the references to setting: > >>Have a look at the following patch: > >> > >>http://svnweb.freebsd.org/base?view=revision&revision=243546 > >> > >>When I encountered the same error on Dell machines, using bge driver from > >>HEAD > >>helped me, although it seems that the aforementioned patch should be > >>enough. > >That change is just one of changes required to make > >BCM5718/5718/5719/5720 work. You need entire bge(4)/brgphy(4) > >changes to get working bge(4) driver on your machines. > > > Just to clear some things: this (or earlier changes) doesn't affect and > doesn't enable IPMI sol and stuff on a BCM5722 ? bge(4)'s IPMI support for old controllers had many issues and didn't work well. Only some of users had luck to enjoy it. However IPMI support for 5717/5718/5719/5720 has no known issues and it should work. I also got a report that mentions IPMI does not work any more on 5715 after adding support for 5717/5718/5719/5720. The sanitized public data sheet does not mention IPMI interface so Linux tg3 would be the only source of information. Given that I don't have access to IPMI-capable controllers I have no idea when it could be fixed. Somebody with the IPMI-capable controllers have to sit down and verify all possible combinations. > > Thanks. > Eugene. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Odd issue with VirtualBox+9-STABLE+bce ...
I'm experiencing some odd issues with Virtualbox running on 9-STABLE. where my network periodically disappears … sometimes, it comes back again after a few minutes, other times I have to reboot the server … This last time, the error on the screen states: bce1: bce_pulse(): Warning: boot code thinks driver is absent! (bc_state = 0x4006) I had 20 regular 'jail' VPSs running on it before I tried VirtualBox on it,and never had this problem, so figure it has to be something with VirtualBox / kmod … ? Anyone experiencing any odd issues with VirtualBox and 9-STABLE? Pointers / ideas? Thx … ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
