From owner-freebsd-net@freebsd.org Fri Mar 10 08:27:40 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08DEFD04453 for ; Fri, 10 Mar 2017 08:27:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E217612F3 for ; Fri, 10 Mar 2017 08:27:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2A8RdwV048940 for ; Fri, 10 Mar 2017 08:27:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Fri, 10 Mar 2017 08:27:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: aiko@torrentkino.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Mar 2017 08:27:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #2 from Aiko Barz --- Today the other Bridge-Server had this issue. But I forget to collect the memory situation before applying the workaround= . :( My current workaround: $ ifconfig ix0 down $ ifconfig ix0 up $ ifconfig ix1 down $ ifconfig ix1 up This is the memory situation after applying the workaround: $ sysctl hw | egrep 'hw.(phys|user|real)' hw.physmem: 17095405568 hw.usermem: 14351601664 hw.realmem: 17179869184 $ grep memory /var/run/dmesg.boot real memory =3D 17179869184 (16384 MB) avail memory =3D 16531873792 (15766 MB) $ freecolor -m -o total used free shared buffers cached Mem: 15866 2625 13240 0 0 0 Swap: 8192 0 8192 $ vmstat -s 1609035107 cpu context switches 3485091537 device interrupts 11107443 software interrupts 44940504 traps 55770968 system calls 25 kernel threads created 184620 fork() calls 35599 vfork() calls 4 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 64250 vnode pager pageins 64954 vnode pager pages paged in 1378 vnode pager pageouts 21763 vnode pager pages paged out 0 page daemon wakeups 297604 pages examined by the page daemon 0 pages reactivated 11889396 copy-on-write faults 6627 copy-on-write optimized faults 24742122 zero fill pages zeroed 0 zero fill pages prezeroed 663 intransit blocking page faults 41093137 total VM faults taken 63984 page faults requiring I/O 0 pages affected by kernel thread creation 7838450 pages affected by fork() 1220635 pages affected by vfork() 1524 pages affected by rfork() 0 pages cached 45799762 pages freed 0 pages freed by daemon 30066607 pages freed by exiting processes 2339 pages active 17759 pages inactive 0 pages in VM cache 669862 pages wired down 3371746 pages free 4096 bytes per page 38614188 total name lookups cache hits (89% pos + 7% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% Those machines only run PF. Nothing else. Kind regards, Aiko --=20 You are receiving this mail because: You are the assignee for the bug.=