Re: kern/187414: ZFS Write Deadlock
The following reply was made to PR kern/187414; it has been noted by GNATS. From: Gordon Yeu To: bug-follo...@freebsd.org, k...@kmd.twbbs.org Cc: Subject: Re: kern/187414: ZFS Write Deadlock Date: Tue, 18 Mar 2014 17:11:51 +0800 --001a1135ed9639bcbf04f4ddeddd Content-Type: text/plain; charset=ISO-8859-1 Clean install FreeBSD 10.0-STABLE r263205, everything works fine. Time to say goodbye to 8.4-STABLE. uname -a FreeBSD kmd.twbbs.org 10.0-STABLE FreeBSD 10.0-STABLE #0 r263205: Sat Mar 15 23:38:52 CST 2014 r...@kmd.twbbs.org:/usr/obj/usr/src/sys/MERCURY amd64 --001a1135ed9639bcbf04f4ddeddd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Clean install FreeBSD 10.0-STABLE r263205, everything= works fine. Time to say goodbye to 8.4-STABLE.un= ame -aFreeBSD http://kmd.twbbs.org";>kmd.twbbs.org= 10.0-STABLE FreeBSD 10.0-STABLE #0 r263205: Sat Mar 15 23:38:52 CST 2014 = =A0 =A0 r...@kmd.twbbs.org:/usr/obj/usr/src/sys/MERCURY =A0amd64 --001a1135ed9639bcbf04f4ddeddd-- ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187654: Panic on system resume (swi4: clock)
The following reply was made to PR kern/187654; it has been noted by GNATS. From: Robert David To: bug-follo...@freebsd.org Cc: Subject: Re: kern/187654: Panic on system resume (swi4: clock) Date: Tue, 18 Mar 2014 11:36:02 +0100 The git revisions are wrong: I got the same also on: a887dd1976ef3a88756e362b7933a80b0dccc608 So the realy correct revision where it works is: 9f9257101a73a807f44a8b46452822dbab7305b0 This is revision when it worked for me (I got zfs snapshot for that revision and used that before). So maybe the borders are: 9f9257101a73a807f44a8b46452822dbab7305b0 a887dd1976ef3a88756e362b7933a80b0dccc608 unfortunately the difference between them are aprox one month. Robert. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
conf/187696: After upgrade 9.1->9.2 boot deadlock if ipv4_addrs_IF contains invalid values
>Number: 187696 >Category: conf >Synopsis: After upgrade 9.1->9.2 boot deadlock if ipv4_addrs_IF contains >invalid values >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 18 12:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Ildar Hizbulin >Release:9.2-RELEASE-p3 >Organization: Ariadna-Link, JSC >Environment: FreeBSD vpn2.vyborg.ru 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #3 r262241: Thu Feb 20 22:41:39 MSK 2014 r...@vpn2.vyborg.ru:/usr/obj/usr/src/sys/VPN2 amd64 >Description: After upgrade FreeBSD from 9.1->9.2 deadlocking boot if ipv4_addrs_IF contains invalid values like "-txcsum" ifalias_af_common_handler function goes into an infinite loop on "-txcsum" value >How-To-Repeat: Add to rc.conf ipv4_addrs_em0="192.168.0.1/24 192.168.1.1/24 -txcsum" replace em0 existing interface name >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: conf/187696: After upgrade 9.1->9.2 boot deadlock if ipv4_addrs_IF contains invalid values
Synopsis: After upgrade 9.1->9.2 boot deadlock if ipv4_addrs_IF contains invalid values Responsible-Changed-From-To: freebsd-bugs->freebsd-rc Responsible-Changed-By: gjb Responsible-Changed-When: Tue Mar 18 12:08:08 UTC 2014 Responsible-Changed-Why: Assign http://www.freebsd.org/cgi/query-pr.cgi?pr=187696 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
bin/187699: Nondefault FIBs don't get loopback addresses
>Number: 187699 >Category: bin >Synopsis: Nondefault FIBs don't get loopback addresses >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 18 15:50:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Alan Somers >Release:11.0 CURRENT >Organization: Spectra Logic >Environment: FreeBSD alans-fbsd-head 11.0-CURRENT FreeBSD 11.0-CURRENT #40 r263266: Mon Mar 17 13:07:35 MDT 2014 al...@ns1.eng.sldomain.com:/vmpool/obj/usr/home/alans/freebsd/head/sys/GENERIC amd64 >Description: "ping 127.0.0.1" and "ping6 ::1" should always work, regardless of which FIB is in use. However, they don't. ipv4_up() in network.subr ensures adds the 127.0.0.1 address to lo0 in the default fib, which causes the kernel to add it to the default fib's routing table. But nothing adds that address to alternate fibs. Nor does anything add ::1 to the inet6 routing tables for alternate FIBs. IMHO, the best way to solve this bug would be to add 127.0.0.1 and ::1 static routes in /etc/rc.d/routing in the functions static_inet() and static_inet6(). >How-To-Repeat: In /boot/loader.conf.local: net.fibs="4" net.add_addr_allfibs="0" setfib 1 ping localhost# This will fail, but it should succeed setfib 1 ping6 ::1 # This will fail, but it should succeed. >Fix: Working on a patch now ... >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: bin/187699: Nondefault FIBs don't get loopback addresses
Synopsis: Nondefault FIBs don't get loopback addresses Responsible-Changed-From-To: freebsd-bugs->asomers Responsible-Changed-By: asomers Responsible-Changed-When: Tue Mar 18 16:08:15 UTC 2014 Responsible-Changed-Why: I'll take it http://www.freebsd.org/cgi/query-pr.cgi?pr=187699 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/187700: FreeBSD Guest in Virtual Box NAT environment - PCnet-FAST III(Am79C973) and Intel PRO/1000 MT Server (82545EM) cards - not receiving IP address
>Number: 187700 >Category: misc >Synopsis: FreeBSD Guest in Virtual Box NAT environment - PCnet-FAST >III(Am79C973) and Intel PRO/1000 MT Server (82545EM) cards - not receiving IP >address >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 18 16:30:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Sastry Tumuluri >Release:10.0-RELEASE (amd64), 9.2-RELEASE (amd64) >Organization: Government of Haryana >Environment: FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I'm trying to use FreeBSD 10.0-RELEASE (amd64) on VirtualBox (3.2.x and 3.3.8) with the network setting (on VirtualBox) in NAT mode. When I choose either of these adapters in VirtualBox Settings->network->NAT->Advanced: -- PCnet-FAST III(Am79C973) -- Intel PRO/1000 MT Server (82545EM) Upon boot, there is no IP address and the VM can't reach out to the internet. I tried assigning the IP address manually, but still can't reach out (ping can't reach the VirtualBox-internal default gateway: 10.0.2.2) Boot time messages show 6x DHCPDISCOVER but no DHCPOFFER response. Manually invoking dhclient shows the same symptom (6x DHCPDISCOVER, no DHCPOFFER). The following adapters seem to work (obtain the IP address 10.0.2.15 from VirtualBox and get out to the Internet) just fine: -- Intel PRO/1000 MT Desktop (82540EM) -- default -- Intel PRO/1000 T Server (82543GC) -- PCnet-PCI II(Am79C970A) All the five adapters work fine on other guest OSes (e.g., xubuntu Linux). Other info: 1. All this, on Acer Travelmate 8372 running Xubuntu 13.10 (all updates and patches are current) as Host OS. I haven't tried this on any other system (will do if someone feels it may be relevant). 2. The problem exists in 9.2-RELEASE (amd64) as well. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187575: r263140 breaks installworld: if_ef.4/ef.4 is missing
Synopsis: r263140 breaks installworld: if_ef.4/ef.4 is missing State-Changed-From-To: open->closed State-Changed-By: glebius State-Changed-When: Tue Mar 18 16:58:58 UTC 2014 State-Changed-Why: Already fixed. Responsible-Changed-From-To: freebsd-bugs->glebius Responsible-Changed-By: glebius Responsible-Changed-When: Tue Mar 18 16:58:58 UTC 2014 Responsible-Changed-Why: Already fixed. http://www.freebsd.org/cgi/query-pr.cgi?pr=187575 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall
Synopsis: incomming ng_l2tp/ipsec packet bypass PF firewall State-Changed-From-To: open->feedback State-Changed-By: glebius State-Changed-When: Tue Mar 18 17:03:27 UTC 2014 State-Changed-Why: Submitter was asked for feedback. http://www.freebsd.org/cgi/query-pr.cgi?pr=187566 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall
The following reply was made to PR kern/187566; it has been noted by GNATS. From: Gleb Smirnoff To: HASHI Hiroaki Cc: freebsd-gnats-sub...@freebsd.org Subject: Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall Date: Tue, 18 Mar 2014 21:03:18 +0400 Hiroaki-san, On Fri, Mar 14, 2014 at 04:05:37PM +0900, HASHI Hiroaki wrote: H> >Environment: H> System: FreeBSD tomba.meridiani.jp 10.0-STABLE FreeBSD 10.0-STABLE #3 r262965: Thu Mar 13 18:44:26 JST 2014 has...@stenmark.meridiani.jp:/usr/obj/usr/src/sys/TOMBA amd64 H> H> ng_l2tp: net/mpd5 H> ipsec: security/ipsec-tools H> H> >Description: H> incoming packet on ng_l2tp interface bypass PF firewall rules. H> not nat, no filter. Can you please check whether the issue is fixed or not by r263307 commit to stable/10? -- Totus tuus, Glebius. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/173516: [cxgbe] Doesn't detect link-up after driver is first loaded
Synopsis: [cxgbe] Doesn't detect link-up after driver is first loaded State-Changed-From-To: open->closed State-Changed-By: np State-Changed-When: Tue Mar 18 18:39:37 UTC 2014 State-Changed-Why: This is as designed. The driver powers up the PHY only when the link is administratively up. So you do need an ifconfig up in order for link state to be reported accurately. http://www.freebsd.org/cgi/query-pr.cgi?pr=173516 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
misc/187709: version update
>Number: 187709
>Category: misc
>Synopsis: version update
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Mar 18 20:30:02 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Vasiliy P. Melnik
>Release:10.0-RELEASE
>Organization:
>Environment:
FreeBSD fr10 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59
UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
This release allows to set fields on tab Personal to read-only. NIS mail
aliases can managed on user tab and there is a new option if referrals should
be followed. The Pro version supports Oracle databases and organizational
roles. The self service now includes a language selection and password reset
supports alternate email addresses.
>How-To-Repeat:
>Fix:
diff -ruN /usr/ports/sysutils/ldap-account-manager/Makefile
/root/ldap-account-manager/Makefile
--- /usr/ports/sysutils/ldap-account-manager/Makefile 2014-02-21
15:39:38.0 +0200
+++ /root/ldap-account-manager/Makefile 2014-03-18 22:13:46.116069310 +0200
@@ -1,7 +1,7 @@
# $FreeBSD: head/sysutils/ldap-account-manager/Makefile 345435 2014-02-21
13:39:38Z ehaupt $
PORTNAME= ldap-account-manager
-PORTVERSION= 4.4
+PORTVERSION= 4.5
PORTREVISION= 1
CATEGORIES=sysutils www
MASTER_SITES= SF/${SHORTNAME}/LAM/${PORTVERSION}
diff -ruN /usr/ports/sysutils/ldap-account-manager/distinfo
/root/ldap-account-manager/distinfo
--- /usr/ports/sysutils/ldap-account-manager/distinfo 2014-01-11
18:55:30.0 +0200
+++ /root/ldap-account-manager/distinfo 2014-03-18 22:14:02.114062838 +0200
@@ -1,2 +1,2 @@
-SHA256 (ldap-account-manager-4.4.tar.bz2) =
990b963a98a7a6ee1e15072010b7da3a11535e205c4c5c6724676dc2deb44789
-SIZE (ldap-account-manager-4.4.tar.bz2) = 13557991
+SHA256 (ldap-account-manager-4.5.tar.bz2) =
7652475905fdfb27b40feaa6c0dc39dc78caa6465e1654539799f5c40ae8f714
+SIZE (ldap-account-manager-4.5.tar.bz2) = 11729338
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187654: Panic on system resume (swi4: clock)
The following reply was made to PR kern/187654; it has been noted by GNATS. From: Ivan Klymenko To: bug-follo...@freebsd.org, robert.david.pub...@gmail.com Cc: Subject: Re: kern/187654: Panic on system resume (swi4: clock) Date: Tue, 18 Mar 2014 22:26:34 +0200 In mailing list with the subject "Clock issues and crash on resume on 10-Stable r263062M" there method to avoid panic: "This is actually a crash in newcons. Try setting kern.vt.suspendswitch to 0 as a workaround." ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/187712: config(8) does not respect KERNCONFDIR
>Number: 187712
>Category: kern
>Synopsis: config(8) does not respect KERNCONFDIR
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Mar 18 22:20:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Alan Somers
>Release:11.0 CURRENT
>Organization:
Spectra Logic
>Environment:
FreeBSD alans-fbsd-head 11.0-CURRENT FreeBSD 11.0-CURRENT #40 r263266: Mon Mar
17 13:07:35 MDT 2014
al...@ns1.eng.sldomain.com:/vmpool/obj/usr/home/alans/freebsd/head/sys/GENERIC
amd64
>Description:
When doing a buildkernel, you can set the make variable KERNCONFDIR if the
kernel config file is in a location other than sys/${ARCH}/conf. However, if
your kernel config file uses the "include" statement to include another config
file, config(8) will not search in KERNCONFDIR to find the included file. My
patch makes config(8) aware of KERNCONFDIR when processing the "include"
statement, and causes make to set KERNCONFDIR when invoking config(8).
This bug is the more general case of ports/164242.
>How-To-Repeat:
# cd /usr/src
# cp sys/amd64/conf/GENERIC /tmp/GENERIC_dup
# echo "include GENERIC_dup" > /tmp/GENERIC2
# make KERNCONFDIR="/tmp" KERNCONF=GENERIC2 buildkernel
--
>Fix:
Apply attached patch
Patch attached with submission follows:
Index: Makefile.inc1
===
--- Makefile.inc1 (revision 263266)
+++ Makefile.inc1 (working copy)
@@ -1013,7 +1013,7 @@
@echo ">>> stage 1: configuring the kernel"
@echo "--"
cd ${KRNLCONFDIR}; \
- PATH=${TMPPATH} \
+ PATH=${TMPPATH} KERNCONFDIR=${KERNCONFDIR} \
config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} \
${KERNCONFDIR}/${_kernel}
.endif
Index: usr.sbin/config/lang.l
===
--- usr.sbin/config/lang.l (revision 263266)
+++ usr.sbin/config/lang.l (working copy)
@@ -34,6 +34,7 @@
#include
#include
#include
+#include
#include
#include "y.tab.h"
#include "config.h"
@@ -258,6 +259,7 @@
FILE *fp;
struct incl *in;
char *fnamebuf;
+ char *kernconfdir;
fnamebuf = NULL;
fp = fopen(fname, "r");
@@ -269,6 +271,16 @@
}
}
if (fp == NULL) {
+ kernconfdir = getenv("KERNCONFDIR");
+ if (kernconfdir != NULL) {
+ asprintf(&fnamebuf, "%s/%s", kernconfdir, fname);
+ if (fnamebuf != NULL) {
+ fp = fopen(fnamebuf, "r");
+ free(fnamebuf);
+ }
+ }
+ }
+ if (fp == NULL) {
yyerror("cannot open included file");
return (-1);
}
>Release-Note:
>Audit-Trail:
>Unformatted:
>>> Kernel build for GENERIC2 started on Tue Mar 18 12:13:27 MDT 2014
--
===> GENERIC2
mkdir -p /vmpool/obj/usr/home/alans/freebsd/head/sys
--
>>> stage 1: configuring the kernel
--
cd /usr/home/alans/freebsd/head/sys/amd64/conf;
PATH=/vmpool/obj/usr/home/alans/freebsd/head/tmp/legacy/usr/sbin:/vmpool/obj/usr/home/alans/freebsd/head/tmp/legacy/usr/bin:/vmpool/obj/usr/home/alans/freebsd/head/tmp/legacy/usr/games:/vmpool/obj/usr/home
/alans/freebsd/head/tmp/legacy/bin:/vmpool/obj/usr/home/alans/freebsd/head/tmp/usr/sbin:/vmpool/obj/usr/home/alans/freebsd/head/tmp/usr/bin:/vmpool/obj/usr/home/alans/freebsd/head/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
config -d /vmpool/obj/usr/ho me/alans/freebsd/head/sys/GENERIC2
/tmp/GENERIC2
config: /tmp/GENERIC2:2: cannot open included file
*** Error code 1
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187712: config(8) does not respect KERNCONFDIR
Synopsis: config(8) does not respect KERNCONFDIR Responsible-Changed-From-To: freebsd-bugs->asomers Responsible-Changed-By: asomers Responsible-Changed-When: Tue Mar 18 22:44:38 UTC 2014 Responsible-Changed-Why: I'll take it http://www.freebsd.org/cgi/query-pr.cgi?pr=187712 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall
The following reply was made to PR kern/187566; it has been noted by GNATS. From: HASHI Hiroaki To: gleb...@freebsd.org Cc: freebsd-gnats-sub...@freebsd.org Subject: Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall Date: Wed, 19 Mar 2014 09:20:59 +0900 (JST) Gleb-san fixed. But the problem of kern/169620 that was hidden due to this issue will appear again. http://www.freebsd.org/cgi/query-pr.cgi?pr=169620 In "Re: kern/187566: incomming ng_l2tp/ipsec packet bypass PF firewall" at Tue, 18 Mar 2014 21:03:18 +0400 Gleb Smirnoff wrote: > Hiroaki-san, > > On Fri, Mar 14, 2014 at 04:05:37PM +0900, HASHI Hiroaki wrote: > H> >Environment: > H> System: FreeBSD tomba.meridiani.jp 10.0-STABLE FreeBSD 10.0-STABLE #3 > r262965: Thu Mar 13 18:44:26 JST 2014 > has...@stenmark.meridiani.jp:/usr/obj/usr/src/sys/TOMBA amd64 > H> > H> ng_l2tp: net/mpd5 > H> ipsec: security/ipsec-tools > H> > H> >Description: > H> incoming packet on ng_l2tp interface bypass PF firewall rules. > H> not nat, no filter. > > Can you please check whether the issue is fixed or not by r263307 > commit to stable/10? > > -- > Totus tuus, Glebius. > ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
kern/187718: UDP bad performance and out-of-order packet with iperf3 and igb(4) drivers
>Number: 187718
>Category: kern
>Synopsis: UDP bad performance and out-of-order packet with iperf3 and
>igb(4) drivers
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Mar 19 00:50:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Olivier Cochard-Labbe
>Release:-current
>Organization:
BSD Router project
>Environment:
FreeBSD R1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r263118M: Fri Mar 14 00:02:53
CET 2014
r...@orange.bsdrp.net:/usr/obj/BSDRPcur.amd64/usr/local/BSDRP/BSDRPcur/FreeBSD/src/sys/amd64
amd64
>Description:
Testing UDP throughput with iperf and iperf3 give totally different value:
With iperf:
[root@R1]~# iperf -u -c 99.99.99.100 -w65536 -l1460 -t30 -i4 -b1000m -P1
Client connecting to 99.99.99.100, UDP port 5001
Sending 1460 byte datagrams
UDP buffer size: 64.0 KByte
[ 3] local 99.99.99.99 port 64273 connected with 99.99.99.100 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 4.0 sec 373 MBytes 783 Mbits/sec
[ 3] 4.0- 8.0 sec 374 MBytes 784 Mbits/sec
[ 3] 8.0-12.0 sec 372 MBytes 780 Mbits/sec
[ 3] 12.0-16.0 sec 373 MBytes 783 Mbits/sec
[ 3] 16.0-20.0 sec 373 MBytes 783 Mbits/sec
[ 3] 20.0-24.0 sec 373 MBytes 782 Mbits/sec
[ 3] 24.0-28.0 sec 373 MBytes 783 Mbits/sec
[ 3] 0.0-30.0 sec 2.73 GBytes 783 Mbits/sec
[ 3] Sent 2010212 datagrams
[ 3] Server Report:
[ 3] 0.0-30.0 sec 2.73 GBytes 781 Mbits/sec 0.010 ms 4953/2010211 (0.25%)
[ 3] 0.0-30.0 sec 954425 datagrams received out-of-order
with iperf3.
[root@R1]~# iperf3 -u -c 99.99.99.100 -w65536 -l1460 -t30 -i4 -b1000m -P1
Connecting to host 99.99.99.100, port 5201
[ 4] local 99.99.99.99 port 43694 connected to 99.99.99.100 port 5201
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-4.00 sec 48.7 MBytes 102 Mbits/sec 1295380
[ 4] 4.00-8.00 sec 28.2 MBytes 59.2 Mbits/sec 1334970
[ 4] 8.00-12.00 sec 31.6 MBytes 66.4 Mbits/sec 1334995
[ 4] 12.00-16.00 sec 32.0 MBytes 67.1 Mbits/sec 1330605
[ 4] 16.00-20.00 sec 47.3 MBytes 99.2 Mbits/sec 1335097
[ 4] 20.00-24.00 sec 30.6 MBytes 64.1 Mbits/sec 1335121
[ 4] 24.00-28.00 sec 35.3 MBytes 74.0 Mbits/sec 1331542
[ 4] 28.00-30.00 sec 19.3 MBytes 81.0 Mbits/sec 663836
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth JitterLost/Total
Datagrams
[ 4] 0.00-30.00 sec 273 MBytes 76.4 Mbits/sec 7.755 ms 9381619/9954141
(94%)
[ 4] Sent 9954141 datagrams
>How-To-Repeat:
Load on the generator during the iperf3 test is:
[root@R1]~# top -nCHSIzs1
last pid: 14453; load averages: 0.37, 0.19, 0.09 up 4+17:17:3301:26:07
160 processes: 6 running, 104 sleeping, 50 waiting
Mem: 4192K Active, 26M Inact, 751M Wired, 27M Buf, 15G Free
Swap:
PID USERNAME PRI NICE SIZERES STATE C TIME CPU COMMAND
14452 root 1000 14300K 1880K CPU11 0:26 96.39% iperf3
11 root -92- 0K 800K WAIT1 0:07 0.88% intr{irq279:
igb2:que}
11 root -92- 0K 800K WAIT2 0:13 0.78% intr{irq280:
igb2:que}
11 root -92- 0K 800K WAIT3 0:05 0.68% intr{irq281:
igb2:que}
11 root -92- 0K 800K WAIT0 0:11 0.49% intr{irq278:
igb2:que}
and an extract of the iperf receiver during this test:
iperf3: OUT OF ORDER - incoming packet = 9972872 and received packet = 9983051
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9950852 and received packet = 9983052
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9947731 and received packet = 9983052
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9972873 and received packet = 9983052
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9950853 and received packet = 9983053
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9947732 and received packet = 9983053
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9972874 and received packet = 9983053
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9950854 and received packet = 9983054
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9947733 and received packet = 9983054
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9972875 and received packet = 9983054
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9950855 and received packet = 9983055
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9947734 and received packet = 9983055
AND SP = 5
iperf3: OUT OF ORDER - incoming packet = 9972876 and received packet = 9983055
Re: kern/187654: Panic on system resume (swi4: clock)
The following reply was made to PR kern/187654; it has been noted by GNATS. From: Ivan Klymenko To: bug-follo...@freebsd.org, robert.david.pub...@gmail.com Cc: Subject: Re: kern/187654: Panic on system resume (swi4: clock) Date: Wed, 19 Mar 2014 07:51:30 +0200 fixed in : http://svnweb.freebsd.org/changeset/base/263321 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
