From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:17:54 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9AE1F28; Sun, 11 Nov 2012 16:17:54 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 7E7768FC5A; Sun, 11 Nov 2012 16:17:54 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGHs5i025769; Sun, 11 Nov 2012 16:17:54 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id qABGHs5N025768; Sun, 11 Nov 2012 16:17:54 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:17:54 GMT Message-Id: <201211111617.qABGHs5N025768@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:17:54 -0000 TB --- 2012-11-11 16:09:45 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-11 16:09:45 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-11 16:09:45 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2012-11-11 16:09:45 - cleaning the object tree TB --- 2012-11-11 16:09:45 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-11 16:09:45 - cd /tinderbox/RELENG_9/i386/i386 TB --- 2012-11-11 16:09:45 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:10:23 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:10:54 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:10:54 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:11:24 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:11:51 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:11:51 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:12:51 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:13:27 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:13:27 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:14:57 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:15:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:15:25 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:17:25 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:17:54 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:17:54 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:17:54 - 3.71 user 4.84 system 488.63 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:03 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BB04F6A2; Sun, 11 Nov 2012 16:33:03 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id A62DE8FC60; Sun, 11 Nov 2012 16:33:00 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX07c022643; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX0Fn022639; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX0Fn022639@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on i386/pc98 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:03 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/i386/pc98 TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.61 user 4.27 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:03 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BFD7E6A3; Sun, 11 Nov 2012 16:33:03 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id A633F8FC61; Sun, 11 Nov 2012 16:33:00 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX0Ua022645; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX0A2022637; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX0A2022637@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:03 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/i386/i386 TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.62 user 4.23 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:03 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C49A96A4; Sun, 11 Nov 2012 16:33:03 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id A88528FC62; Sun, 11 Nov 2012 16:33:00 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX0gD022642; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX072022635; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX072022635@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:04 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/ia64/ia64 TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.88 user 3.98 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:04 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C958E6A5; Sun, 11 Nov 2012 16:33:03 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id AFC4E8FC64; Sun, 11 Nov 2012 16:33:00 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX0He022641; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX0WW022636; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX0WW022636@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on sparc64/sparc64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:04 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/sparc64/sparc64 TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.73 user 4.14 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:04 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EBDB6A8; Sun, 11 Nov 2012 16:33:04 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id A5E4F8FC46; Sun, 11 Nov 2012 16:33:00 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX0IA022640; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX0g7022634; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX0g7022634@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:04 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/powerpc/powerpc TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.77 user 4.10 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:33:54 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1FBD7930; Sun, 11 Nov 2012 16:33:54 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id A986C8FC88; Sun, 11 Nov 2012 16:26:02 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGQ2cs057939; Sun, 11 Nov 2012 16:26:02 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id qABGQ2mj057924; Sun, 11 Nov 2012 16:26:02 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:26:02 GMT Message-Id: <201211111626.qABGQ2mj057924@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on i386/pc98 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:33:54 -0000 TB --- 2012-11-11 16:17:54 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-11 16:17:54 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-11 16:17:54 - starting RELENG_9 tinderbox run for i386/pc98 TB --- 2012-11-11 16:17:54 - cleaning the object tree TB --- 2012-11-11 16:17:54 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-11 16:17:54 - cd /tinderbox/RELENG_9/i386/pc98 TB --- 2012-11-11 16:17:54 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:18:23 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:19:00 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:19:00 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:19:30 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:19:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:19:59 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:20:59 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:21:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:21:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:22:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:23:30 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:23:30 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:25:30 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:02 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:02 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:26:02 - 3.72 user 4.76 system 487.92 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:26 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93E731C4; Sun, 11 Nov 2012 16:41:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 517088FC99; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMUY022782; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMqe022775; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMqe022775@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:26 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for arm/arm TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/arm/arm TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.96 user 4.53 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-arm-arm.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:26 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8E411C5; Sun, 11 Nov 2012 16:41:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 4C2988FC96; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMsP022780; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMRi022774; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMRi022774@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on i386/pc98 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:26 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for i386/pc98 TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/i386/pc98 TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.62 user 4.91 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-pc98.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:26 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AECBD1C6; Sun, 11 Nov 2012 16:41:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 58B5F8FC9A; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMAO022779; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMFw022773; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMFw022773@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:26 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for ia64/ia64 TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/ia64/ia64 TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.62 user 4.88 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:26 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B37D61C7; Sun, 11 Nov 2012 16:41:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4E58FC9B; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMmD022783; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMxZ022777; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMxZ022777@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:26 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for mips/mips TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/mips/mips TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.57 user 4.97 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-mips-mips.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:26 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B83501C8; Sun, 11 Nov 2012 16:41:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 5FD9F8FC9C; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMTZ022781; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMcC022776; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMcC022776@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:27 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/i386/i386 TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.80 user 4.67 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:41:29 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CB0C1C9; Sun, 11 Nov 2012 16:41:29 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 4E6FA8FC97; Sun, 11 Nov 2012 16:41:23 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGfMm6022784; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGfMmm022778; Sun, 11 Nov 2012 16:41:22 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:41:22 GMT Message-Id: <201211111641.qABGfMmm022778@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_8 tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:41:29 -0000 TB --- 2012-11-11 16:33:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:33:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:33:00 - starting RELENG_8 tinderbox run for amd64/amd64 TB --- 2012-11-11 16:33:00 - cleaning the object tree TB --- 2012-11-11 16:33:00 - checking out /src from svn://svn.freebsd.org/base/stable/8 TB --- 2012-11-11 16:33:00 - cd /tinderbox/RELENG_8/amd64/amd64 TB --- 2012-11-11 16:33:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:33:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:33:43 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:33:43 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:34:13 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:03 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:03 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:36:03 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:38 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:38 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:38:08 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:38:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:38:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:40:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:41:22 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:41:22 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:41:22 - 1.73 user 4.80 system 502.58 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 16:42:32 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 113048B5; Sun, 11 Nov 2012 16:42:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id AA8078FC96; Sun, 11 Nov 2012 16:42:28 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGgSJB011161; Sun, 11 Nov 2012 16:42:28 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id qABGgSkY011158; Sun, 11 Nov 2012 16:42:28 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:42:28 GMT Message-Id: <201211111642.qABGgSkY011158@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 16:42:32 -0000 TB --- 2012-11-11 16:34:21 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-11 16:34:21 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-11 16:34:21 - starting RELENG_9 tinderbox run for mips/mips TB --- 2012-11-11 16:34:21 - cleaning the object tree TB --- 2012-11-11 16:34:21 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-11 16:34:21 - cd /tinderbox/RELENG_9/mips/mips TB --- 2012-11-11 16:34:21 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:34:53 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:35:28 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:35:28 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:35:58 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:36:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:36:25 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:37:25 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:37:53 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:37:53 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:39:23 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:39:51 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:39:51 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:41:51 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:42:28 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:42:28 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:42:28 - 3.66 user 4.81 system 486.33 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-mips-mips.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 17:04:24 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0633F1CE; Sun, 11 Nov 2012 17:04:24 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy2.sentex.ca (freebsd-legacy2.sentex.ca [IPv6:2607:f3e0:0:3::6502:9c]) by mx1.freebsd.org (Postfix) with ESMTP id 9CB028FD0A; Sun, 11 Nov 2012 17:04:20 +0000 (UTC) Received: from freebsd-legacy2.sentex.ca (localhost [127.0.0.1]) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGX0Zi022644; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-legacy2.sentex.ca (8.14.5/8.14.5/Submit) id qABGX0Fb022638; Sun, 11 Nov 2012 16:33:00 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:33:00 GMT Message-Id: <201211111633.qABGX0Fb022638@freebsd-legacy2.sentex.ca> X-Authentication-Warning: freebsd-legacy2.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_7 tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 17:04:24 -0000 TB --- 2012-11-11 16:25:00 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-11-11 16:25:00 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-11 16:25:00 - starting RELENG_7 tinderbox run for amd64/amd64 TB --- 2012-11-11 16:25:00 - cleaning the object tree TB --- 2012-11-11 16:25:00 - checking out /src from svn://svn.freebsd.org/base/stable/7 TB --- 2012-11-11 16:25:00 - cd /tinderbox/RELENG_7/amd64/amd64 TB --- 2012-11-11 16:25:00 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:25:09 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:25:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:25:45 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:26:15 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:50 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:50 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:27:50 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:25 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:25 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:29:55 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:30:31 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:30:31 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:32:31 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:32:59 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:32:59 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:32:59 - 1.67 user 4.12 system 479.45 real http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 17:08:56 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0284D3A5; Sun, 11 Nov 2012 17:08:56 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 0237A8FC08; Sun, 11 Nov 2012 16:09:45 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id qABG9jRH081970; Sun, 11 Nov 2012 16:09:45 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id qABG9jam081969; Sun, 11 Nov 2012 16:09:45 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:09:45 GMT Message-Id: <201211111609.qABG9jam081969@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 17:08:56 -0000 TB --- 2012-11-11 16:01:46 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-11 16:01:46 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-11 16:01:46 - starting RELENG_9 tinderbox run for arm/arm TB --- 2012-11-11 16:01:46 - cleaning the object tree TB --- 2012-11-11 16:01:46 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-11 16:01:46 - cd /tinderbox/RELENG_9/arm/arm TB --- 2012-11-11 16:01:46 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:02:20 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:02:51 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:02:51 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:03:21 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:03:49 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:03:49 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:04:49 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:05:18 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:05:18 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:06:48 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:07:16 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:07:16 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:09:16 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:09:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:09:45 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:09:45 - 3.73 user 4.72 system 478.44 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-arm-arm.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 17:23:51 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A56F21CE; Sun, 11 Nov 2012 17:23:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [IPv6:2607:f3e0:0:3::6502:9b]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0BB8FC2B; Sun, 11 Nov 2012 16:34:22 +0000 (UTC) Received: from freebsd-stable.sentex.ca (localhost [127.0.0.1]) by freebsd-stable.sentex.ca (8.14.5/8.14.5) with ESMTP id qABGYLxD087155; Sun, 11 Nov 2012 16:34:21 GMT (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-stable.sentex.ca (8.14.5/8.14.5/Submit) id qABGYLT0087153; Sun, 11 Nov 2012 16:34:21 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 11 Nov 2012 16:34:21 GMT Message-Id: <201211111634.qABGYLT0087153@freebsd-stable.sentex.ca> X-Authentication-Warning: freebsd-stable.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [releng_9 tinderbox] failure on ia64/ia64 Precedence: bulk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 17:23:51 -0000 TB --- 2012-11-11 16:26:02 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-11-11 16:26:02 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-11-11 16:26:02 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2012-11-11 16:26:02 - cleaning the object tree TB --- 2012-11-11 16:26:02 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2012-11-11 16:26:02 - cd /tinderbox/RELENG_9/ia64/ia64 TB --- 2012-11-11 16:26:02 - /usr/local/bin/svn cleanup /src TB --- 2012-11-11 16:26:30 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:26:58 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:26:58 - WARNING: sleeping 30 s and retrying... TB --- 2012-11-11 16:27:28 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:28:16 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:28:16 - WARNING: sleeping 60 s and retrying... TB --- 2012-11-11 16:29:16 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:29:44 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:29:44 - WARNING: sleeping 90 s and retrying... TB --- 2012-11-11 16:31:14 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:31:45 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:31:45 - WARNING: sleeping 120 s and retrying... TB --- 2012-11-11 16:33:45 - /usr/local/bin/svn update /src TB --- 2012-11-11 16:34:21 - WARNING: /usr/local/bin/svn returned exit code 1 TB --- 2012-11-11 16:34:21 - ERROR: unable to check out the source tree TB --- 2012-11-11 16:34:21 - 3.59 user 4.99 system 499.32 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-ia64-ia64.full From owner-freebsd-stable@FreeBSD.ORG Sun Nov 11 21:35:31 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E869B7D; Sun, 11 Nov 2012 21:35:31 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id EB03E8FC0C; Sun, 11 Nov 2012 21:35:30 +0000 (UTC) Received: from server.rulingia.com (c220-239-241-202.belrs5.nsw.optusnet.com.au [220.239.241.202]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id qABLZMBK064345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Nov 2012 08:35:22 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id qABLZGuo063915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 08:35:16 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id qABLZFoK063914; Mon, 12 Nov 2012 08:35:15 +1100 (EST) (envelope-from peter) Date: Mon, 12 Nov 2012 08:35:15 +1100 From: Peter Jeremy To: Steven Hartland Subject: Re: ZFS corruption due to lack of space? Message-ID: <20121111213515.GC5594@server.rulingia.com> References: <27087376D1C14132A3CC1B4016912F6D@multiplay.co.uk> <20121031212346.GL3309@server.rulingia.com> <9DB937FEA7634C4BAC49EF5823F93CA3@multiplay.co.uk> <20121101224355.GS3309@server.rulingia.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2012 21:35:31 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Nov-02 09:30:04 -0000, Steven Hartland wr= ote: >From: "Peter Jeremy" >> Many years ago, I wrote a simple utility that fills a raw disk with >> a pseudo-random sequence and then verifies it. This sort of tool > >Sounds useful, got a link? Sorry, no. I never released it. But writing something like it is quite easy. --=20 Peter Jeremy --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCgGhMACgkQ/opHv/APuIcEWQCgv/fIBA95G/Xy6D0NRfqJTgqx vhAAoKYra7UebNp7fz2YZxxVnNFcA+pv =0pjN -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 05:12:32 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9DD8E0F for ; Mon, 12 Nov 2012 05:12:32 +0000 (UTC) (envelope-from zkolic@sbb.rs) Received: from smtp3.sbb.rs (smtp3.sbb.rs [89.216.2.35]) by mx1.freebsd.org (Postfix) with ESMTP id 23CA58FC13 for ; Mon, 12 Nov 2012 05:12:31 +0000 (UTC) Received: from mycenae (cable-178-148-96-72.dynamic.sbb.rs [178.148.96.72]) by smtp3.sbb.rs (8.14.0/8.14.0) with ESMTP id qAC5CIFf004546 for ; Mon, 12 Nov 2012 06:12:23 +0100 Received: by mycenae (Postfix, from userid 1001) id DFA075C23; Mon, 12 Nov 2012 06:12:29 +0100 (CET) Date: Mon, 12 Nov 2012 06:12:29 +0100 From: Zoran Kolic To: freebsd-stable@freebsd.org Subject: nomenclature for conf files Message-ID: <20121112051229.GA1235@mycenae.sbb.rs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-SMTP-Vilter-Version: 1.3.2 X-SBB-Virus-Status: clean X-SBB-Spam-Score: -1.8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 05:12:32 -0000 It might sound stupid, but I'd like to know if there's any difference. Are those 3 line the same? WITH_KMS=YES WITH_KMS="YES" WITH_KMS=yes Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 05:20:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3517F71 for ; Mon, 12 Nov 2012 05:20:14 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 761438FC0C for ; Mon, 12 Nov 2012 05:20:13 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so86635eek.13 for ; Sun, 11 Nov 2012 21:20:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+2fnhkgzmvDWZNdZXcCtrWfZVRYZBlOtmo3J635eI3M=; b=JK4jjSwW52/h1onvlql9pxNwtMKztA1an4atlCmf2PIUibtAne/k4Iw2GoAzR1ZMCM a8DN3CzRwWWZLWIsFtyS1ZDyoA7z5KvLgHFxk0xZ9tw3Z6vahGcBaWwbu9fAfdhQjngy liy9+gzFGKHBDn7UALKRgmBauZEtQGnbeDge4PKqEzHcTzSJSz2zAm0ADymLzXRSchA0 Lly8x0ffqGifi2fl+QrAsLJm0qT02i+Fqm452fn0uLhE5vSwSHRslJjc/Itsi9wh1pmy eSm8h4Ylw4Ym37n7w7HdN5cV927wO6C00T9NIQ3WP++UUq1cFmhAoC4EPEXB/c8rO33n VLgg== MIME-Version: 1.0 Received: by 10.14.213.65 with SMTP id z41mr58943501eeo.29.1352697613250; Sun, 11 Nov 2012 21:20:13 -0800 (PST) Received: by 10.14.211.137 with HTTP; Sun, 11 Nov 2012 21:20:13 -0800 (PST) In-Reply-To: <20121112051229.GA1235@mycenae.sbb.rs> References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Sun, 11 Nov 2012 21:20:13 -0800 Message-ID: Subject: Re: nomenclature for conf files From: Kurt Buff To: Zoran Kolic Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 05:20:15 -0000 On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > It might sound stupid, but I'd like to know if there's > any difference. Are those 3 line the same? > > WITH_KMS=YES > WITH_KMS="YES" > WITH_KMS=yes With regard to their use in /etc/rc.conf, no, absolutely not. In general, from my experience, only the second one will work. This might, or might not, be true for other uses, but rc.conf is pretty picky about this. Kurt From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 05:29:41 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 65CF4139 for ; Mon, 12 Nov 2012 05:29:41 +0000 (UTC) (envelope-from zkolic@sbb.rs) Received: from smtp3.sbb.rs (smtp3.sbb.rs [89.216.2.35]) by mx1.freebsd.org (Postfix) with ESMTP id C25C68FC13 for ; Mon, 12 Nov 2012 05:29:40 +0000 (UTC) Received: from mycenae (cable-178-148-96-72.dynamic.sbb.rs [178.148.96.72]) by smtp3.sbb.rs (8.14.0/8.14.0) with ESMTP id qAC5TX04012601; Mon, 12 Nov 2012 06:29:38 +0100 Received: by mycenae (Postfix, from userid 1001) id D59DB5C23; Mon, 12 Nov 2012 06:29:39 +0100 (CET) Date: Mon, 12 Nov 2012 06:29:39 +0100 From: Zoran Kolic To: Kurt Buff Subject: Re: nomenclature for conf files Message-ID: <20121112052939.GA1309@mycenae.sbb.rs> References: <20121112051229.GA1235@mycenae.sbb.rs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SMTP-Vilter-Version: 1.3.2 X-SBB-Virus-Status: clean X-SBB-Spam-Score: -1.8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 05:29:41 -0000 > > WITH_KMS=YES > > WITH_KMS="YES" > > WITH_KMS=yes > > With regard to their use in /etc/rc.conf, no, absolutely not. > In general, from my experience, only the second one will work. Yep, in rc.conf only the second one. I was thinking of make.conf. It is the place kms should be set. Loader conf might take only "" versions also. Thank you and best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 07:13:04 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13B119F7 for ; Mon, 12 Nov 2012 07:13:04 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8EDFC8FC16 for ; Mon, 12 Nov 2012 07:13:03 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so129439eek.13 for ; Sun, 11 Nov 2012 23:13:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kVYsvF+HLLEuklZCwouKrAprQIcaGBBvIKc+hAxvkMA=; b=UmM6f6PQkA09hVzZbDBGsHCtd9+u+Vl10Lui2oBa2p+k7uHKNtl0LD0hy+8eQ07jYH +lIsrtMF/UYI/eHkAtcFJT+sZwWC32J9DWZiW5D7iXS6HxGe/HrF1fbErZleeWCCADIo 6IfuaMpJqrHG/Nr197EO/tgpCZp7qjfSU+neNGnsJMWJ8W2IXJhO5bhOw4AD+QU00GKd vtJUwofYTBB79pO/WE9K7LW60TU3JMAaKyrfy9sKibPrTwvVJ1M48sEQswhn5aWblgQH l5kWvu0ZoFSQmhO5BrFxyTHPQ+d2r/5qwXmIjy4c0v9Eh0ERO1Wor6xRMU4DSbwDelV2 Lnjg== MIME-Version: 1.0 Received: by 10.14.194.71 with SMTP id l47mr59803611een.6.1352704382464; Sun, 11 Nov 2012 23:13:02 -0800 (PST) Received: by 10.223.66.194 with HTTP; Sun, 11 Nov 2012 23:13:02 -0800 (PST) In-Reply-To: <20121112052939.GA1309@mycenae.sbb.rs> References: <20121112051229.GA1235@mycenae.sbb.rs> <20121112052939.GA1309@mycenae.sbb.rs> Date: Sun, 11 Nov 2012 23:13:02 -0800 Message-ID: Subject: Re: nomenclature for conf files From: Kevin Oberman To: Zoran Kolic Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kurt Buff , "freebsd-stable@freebsd.org Stable" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 07:13:04 -0000 On Sun, Nov 11, 2012 at 9:29 PM, Zoran Kolic wrote: > > > WITH_KMS=YES > > > WITH_KMS="YES" > > > WITH_KMS=yes > > > > With regard to their use in /etc/rc.conf, no, absolutely not. > > In general, from my experience, only the second one will work. > > Yep, in rc.conf only the second one. I was thinking of make.conf. > It is the place kms should be set. Loader conf might take only > "" versions also. > Thank you and best regards > A minor detail, but the line does not belong in rc.conf (a shell script), but in /etc/make.conf (a Makefile). Normally you don't use quotation marks in that case, but it really does not matter in this case as the presence of "WITH_KMS=" is the significant part. I believe that "WITH_KMS=no" and "WITH_KMS=yes" are equivalent. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 08:29:28 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7865B0A for ; Mon, 12 Nov 2012 08:29:28 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 305D98FC14 for ; Mon, 12 Nov 2012 08:29:28 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so1269396bkc.13 for ; Mon, 12 Nov 2012 00:29:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=j3adXqB9sHtrKKlk+s3Uvhm5E1ZV8NZh02uCs+TEt2k=; b=z0EMfvoBfM3rbDRCYrEDwXczlnwSDD/LfMmKDtZ0aZMlCkB4Qz9z5RD6BVBsmqcE7X yNqPWjMhiSaeYucm4QVEJbu1w/6vmQ78H2m+o5FXsAYJ81OIEtvTsj2K8NQU2SQ5aQzi oIFLjEUzOoNpML1DQmKAzANKuDvf8FwB2Wy/lhROCZj6xtJppezc9Xt9GcJCtfypi3ia XITRMKG2jkm2mWiH6QNAAN4VgV2sEOmPqoiYGn/CZRPAry75q1gqNNe5v2aXkoThP2EM nu8gk6CK5MqaYm3b/nXUdRYn9Egb8PsQZiBhSgJrB292jHuRLh61/ookJfeDozf6/URK er3Q== MIME-Version: 1.0 Received: by 10.204.150.213 with SMTP id z21mr6957999bkv.45.1352708967122; Mon, 12 Nov 2012 00:29:27 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 00:29:27 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 00:29:27 -0800 (PST) In-Reply-To: References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Mon, 12 Nov 2012 08:29:27 +0000 Message-ID: Subject: Re: nomenclature for conf files From: Chris Rees To: Kurt Buff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD , Zoran Kolic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 08:29:28 -0000 On 12 Nov 2012 05:20, "Kurt Buff" wrote: > > On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > > It might sound stupid, but I'd like to know if there's > > any difference. Are those 3 line the same? > > > > WITH_KMS=YES > > WITH_KMS="YES" > > WITH_KMS=yes > > With regard to their use in /etc/rc.conf, no, absolutely not. > > In general, from my experience, only the second one will work. > > This might, or might not, be true for other uses, but rc.conf is > pretty picky about this. All three are fine in make.conf and rc.conf The issue with rc.conf is when people put spaces around the = sign. Chris From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 08:55:31 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 961FE1AC for ; Mon, 12 Nov 2012 08:55:31 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id 410048FC08 for ; Mon, 12 Nov 2012 08:55:30 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id qAC8tOI5052568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 09:55:29 +0100 (CET) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id qAC8tOtX052567; Mon, 12 Nov 2012 09:55:24 +0100 (CET) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Mon, 12 Nov 2012 09:55:24 +0100 From: Paul Schenkeveld To: freebsd-stable@freebsd.org Subject: Re: nomenclature for conf files Message-ID: <20121112085524.GA52287@psconsult.nl> References: <20121112051229.GA1235@mycenae.sbb.rs> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Zoran Kolic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 08:55:31 -0000 On Mon, Nov 12, 2012 at 08:29:27AM +0000, Chris Rees wrote: > On 12 Nov 2012 05:20, "Kurt Buff" wrote: > > > > On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > > > It might sound stupid, but I'd like to know if there's > > > any difference. Are those 3 line the same? > > > > > > WITH_KMS=YES > > > WITH_KMS="YES" > > > WITH_KMS=yes > > > > With regard to their use in /etc/rc.conf, no, absolutely not. > > > > In general, from my experience, only the second one will work. > > > > This might, or might not, be true for other uses, but rc.conf is > > pretty picky about this. > > All three are fine in make.conf and rc.conf > > The issue with rc.conf is when people put spaces around the = sign. > > Chris Indeed /etc/rc (executed by /bin/sh) accepts all three forms because quotes are optional in /bin/sh and /etc/rc.subr (sourced by /etc/rc) matches the value against "[Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1". Also, the FreeBSD makefiles and sources test all WITH_* variables with .ifdef or #ifdef so the value doesn't matter and can even be empty. White space around the = is permitted too (but not in rc.conf!). However, things are different when people start using tools to maintain rc.conf/make.conf. If not written with the above in mind, these tools may have problems parsing these files. It's good practice to be consistent and use a canonical form that matches the documentation or example files as this is probably the syntax that is guarenteed to not confuse such tools. In other words: "Be conservative in what you send [write], liberal in what you accept". HTH Paul Schenkeveld From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 10:24:59 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5936D11E for ; Mon, 12 Nov 2012 10:24:59 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id C719E8FC13 for ; Mon, 12 Nov 2012 10:24:58 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so1332450bkc.13 for ; Mon, 12 Nov 2012 02:24:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ShwTFwo88RTgruVWoxA2wJWwr3IAici2m7ZwjEDOLrg=; b=u6LedxjhR/pb8SlKhhOpt4KDQp+AzTHJl8ODQvYSDMwfdRPzSot3FyQfCwo9DjvkTV 16xJfLWx+FEUBGpz6R68smsNTJsCns/t3tWu0tmhuOz5WTcIm+6QAjRgEilsFQ08yPVa UrmBAtt1RX609VTuYqFnaj4pmOZosvz7C8yrv51ZsQ8C3ls4lrMz/fwtwXHAW6GLOO1m JazCN6ASEpC2TiIQsIF+wzjjMYqxXzeoNCNXzr6vtTo9DLWWRUgwswEtN+uwPwgppz2I wYFzEs5CZDtyovyMQWAXIJTIJ8V+lDz6SbupPsSpMe+PJCGVleW89DfGqNW5C+caZgK/ KpUw== MIME-Version: 1.0 Received: by 10.204.150.213 with SMTP id z21mr7083011bkv.45.1352715897653; Mon, 12 Nov 2012 02:24:57 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 02:24:57 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 02:24:57 -0800 (PST) In-Reply-To: <20121112085524.GA52287@psconsult.nl> References: <20121112051229.GA1235@mycenae.sbb.rs> <20121112085524.GA52287@psconsult.nl> Date: Mon, 12 Nov 2012 10:24:57 +0000 Message-ID: Subject: Re: nomenclature for conf files From: Chris Rees To: Paul Schenkeveld Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD , Zoran Kolic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 10:24:59 -0000 On 12 Nov 2012 08:55, "Paul Schenkeveld" wrote: > > On Mon, Nov 12, 2012 at 08:29:27AM +0000, Chris Rees wrote: > > On 12 Nov 2012 05:20, "Kurt Buff" wrote: > > > > > > On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > > > > It might sound stupid, but I'd like to know if there's > > > > any difference. Are those 3 line the same? > > > > > > > > WITH_KMS=YES > > > > WITH_KMS="YES" > > > > WITH_KMS=yes > > > > > > With regard to their use in /etc/rc.conf, no, absolutely not. > > > > > > In general, from my experience, only the second one will work. > > > > > > This might, or might not, be true for other uses, but rc.conf is > > > pretty picky about this. > > > > All three are fine in make.conf and rc.conf > > > > The issue with rc.conf is when people put spaces around the = sign. > > > > Chris > > Indeed /etc/rc (executed by /bin/sh) accepts all three forms because > quotes are optional in /bin/sh and /etc/rc.subr (sourced by /etc/rc) > matches the value against "[Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1". > > Also, the FreeBSD makefiles and sources test all WITH_* variables with > .ifdef or #ifdef so the value doesn't matter and can even be empty. > White space around the = is permitted too (but not in rc.conf!). > > However, things are different when people start using tools to maintain > rc.conf/make.conf. If not written with the above in mind, these tools > may have problems parsing these files. > > It's good practice to be consistent and use a canonical form that > matches the documentation or example files as this is probably the > syntax that is guarenteed to not confuse such tools. In other words: > "Be conservative in what you send [write], liberal in what you accept". Doesn't sound like a very good tool if it can't handle quoting and capital letters, but I accept the principle. Quotes in Makefiles are often harmful, so good practice IMO is to only use them when necessary. Chris From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 10:34:16 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 808842D4 for ; Mon, 12 Nov 2012 10:34:16 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (unknown [IPv6:2001:7b8:30f:e0::5059:ee8a]) by mx1.freebsd.org (Postfix) with ESMTP id EF11C8FC12 for ; Mon, 12 Nov 2012 10:34:15 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.hvnu.psconsult.nl [46.44.189.154]) by mx1.psconsult.nl (8.14.5/8.14.4) with ESMTP id qACAY97x014357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Nov 2012 11:34:14 +0100 (CET) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.5/8.14.4/Submit) id qACAY9MJ014356; Mon, 12 Nov 2012 11:34:09 +0100 (CET) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Mon, 12 Nov 2012 11:34:09 +0100 From: Paul Schenkeveld To: freebsd-stable@freebsd.org Subject: Re: nomenclature for conf files Message-ID: <20121112103409.GA81838@psconsult.nl> References: <20121112051229.GA1235@mycenae.sbb.rs> <20121112085524.GA52287@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Chris Rees X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 10:34:16 -0000 On Mon, Nov 12, 2012 at 10:24:57AM +0000, Chris Rees wrote: > On 12 Nov 2012 08:55, "Paul Schenkeveld" wrote: > > > > On Mon, Nov 12, 2012 at 08:29:27AM +0000, Chris Rees wrote: > > > On 12 Nov 2012 05:20, "Kurt Buff" wrote: > > > > > > > > On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > > > > > It might sound stupid, but I'd like to know if there's > > > > > any difference. Are those 3 line the same? > > > > > > > > > > WITH_KMS=YES > > > > > WITH_KMS="YES" > > > > > WITH_KMS=yes > > > > > > > > With regard to their use in /etc/rc.conf, no, absolutely not. > > > > > > > > In general, from my experience, only the second one will work. > > > > > > > > This might, or might not, be true for other uses, but rc.conf is > > > > pretty picky about this. > > > > > > All three are fine in make.conf and rc.conf > > > > > > The issue with rc.conf is when people put spaces around the = sign. > > > > > > Chris > > > > Indeed /etc/rc (executed by /bin/sh) accepts all three forms because > > quotes are optional in /bin/sh and /etc/rc.subr (sourced by /etc/rc) > > matches the value against "[Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1". > > > > Also, the FreeBSD makefiles and sources test all WITH_* variables with > > .ifdef or #ifdef so the value doesn't matter and can even be empty. > > White space around the = is permitted too (but not in rc.conf!). > > > > However, things are different when people start using tools to maintain > > rc.conf/make.conf. If not written with the above in mind, these tools > > may have problems parsing these files. > > > > It's good practice to be consistent and use a canonical form that > > matches the documentation or example files as this is probably the > > syntax that is guarenteed to not confuse such tools. In other words: > > "Be conservative in what you send [write], liberal in what you accept". > > Doesn't sound like a very good tool if it can't handle quoting and capital > letters, but I accept the principle. > > Chris I wouldn't want to verify all home-grown scripts written by sysadmins around the Internet though. > Quotes in Makefiles are often harmful, so good practice IMO is to only use > them when necessary. For Makefiles yes, quotes are not part of the assignment syntax but appear in the expansion of the macros so be careful. For sh compatible config files better use them for clarity and parsability although I realize that then differences between " and ' come into play too. HTH Paul Schenkeveld From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 11:57:09 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E3788EF; Mon, 12 Nov 2012 11:57:09 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id EEC568FC12; Mon, 12 Nov 2012 11:57:08 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBD58D.dip.t-dialin.net [93.203.213.141]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id qACBuv2u094533; Mon, 12 Nov 2012 11:56:59 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id qACBujR5026400; Mon, 12 Nov 2012 12:56:45 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id qACBuCNO053019; Mon, 12 Nov 2012 12:56:19 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201211121156.qACBuCNO053019@fire.js.berklix.net> To: Peter Jeremy Subject: Re: ZFS corruption due to lack of space? From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 12 Nov 2012 08:35:15 +1100." <20121111213515.GC5594@server.rulingia.com> Date: Mon, 12 Nov 2012 12:56:11 +0100 Sender: jhs@berklix.com Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Steven Hartland X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 11:57:09 -0000 Peter Jeremy wrote: > On 2012-Nov-02 09:30:04 -0000, Steven Hartland wr= > ote: > >From: "Peter Jeremy" > >> Many years ago, I wrote a simple utility that fills a raw disk with > >> a pseudo-random sequence and then verifies it. This sort of tool > > > >Sounds useful, got a link? > > Sorry, no. I never released it. But writing something like it is > quite easy. I wrote http://berklix.com/~jhs/src/bsd/jhs/bin/public/testblock/ There's no pseudo random, but sufficient for my media test needs, There's a bunch of similar tools in ports/ (but I wrote mine before FreeBSD existed so I've never looked). Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 14:31:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B59549E for ; Mon, 12 Nov 2012 14:31:08 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from ecbiz102.inmotionhosting.com (ecbiz102.inmotionhosting.com [70.39.235.94]) by mx1.freebsd.org (Postfix) with ESMTP id 1A7648FC12 for ; Mon, 12 Nov 2012 14:31:07 +0000 (UTC) Received: from c-174-62-183-95.hsd1.nh.comcast.net ([174.62.183.95]:62983 helo=jack.bspruce.com) by ecbiz102.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TXuZl-0004mI-Mh; Mon, 12 Nov 2012 09:01:23 -0500 Message-ID: <50A10133.7090609@greatbaysoftware.com> Date: Mon, 12 Nov 2012 09:01:23 -0500 From: Charles Owens Organization: Great Bay Software User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Eugene Grosbein Subject: Re: Panic during kernel boot, igb-init related? (8.3-RELEASE) References: <509158BC.7090901@greatbaysoftware.com> <509215E6.5040306@rdtc.ru> In-Reply-To: <509215E6.5040306@rdtc.ru> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ecbiz102.inmotionhosting.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - greatbaysoftware.com Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable@freebsd.org, Jack Vogel , Steve McCoy , jdc@parodius.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 14:31:08 -0000 On 11/1/12 2:25 AM, Eugene Grosbein wrote: > 31.10.2012 23:58, Charles Owens ÐÉÛÅÔ: >> Hello, >> >> We're seeing boot-time panics in about 4% of cases when upgrading from >> FreeBSD 8.1 to 8.3-RELEASE (i386). This problem is subtle enough that >> it escaped detection during our regular testing cycle... now with over >> 100 systems upgraded we're convinced there's a real issue. Our kernel >> config is essentially PAE (ie. static modules ... with a few drivers >> added/removed). The hardware is Intel Server System SR1625UR. >> >> This appears to match a finding discussed in these threads, having to do >> with timing of initialization of the igb(4)-based NICs (if I'm >> understanding it properly): >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062596.html >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-June/062949.html >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063867.html >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063958.html >> >> >> These threads include some potential patches and possibility of >> commit/MFC... but it isn't clear that there was ever final resolution >> (and MFC to 8-stable). I've cc'd a few folks from back then. >> >> A real challenge here is the frequency of occurrence. As mentioned, it >> only hit's a fraction of our systems. When it _does_ hit, the system >> may enter a reboot loop for days and then mysteriously break out of >> it... and thereafter seem to work fine. >> >> I'd be very grateful for any help. Some questions: >> >> * Was there ever a final "blessed" patch? >> o if so, will it apply to RELENG_8_3? >> * Is there anything that could be said that might help us with >> reproducing-the-problem / testing / validating-a-fix? >> >> >> Panic message is -- >> >> panic: m_getzone: m_getjcl: invalid cluster type >> cpuid = 0 >> KDB: stack backtrace: >> #0 0xc059c717 at kdb_backtrace+0x47 >> #1 0xc056caf7 at panic+0x117 >> #2 0xc03c979e at igb_refresh_mbufs+0x25e >> #3 0xc03c9f98 at igb_rxeof+0x638 >> #4 0xc03ca135 at igb_msix_que+0x105 >> #5 0xc0541e2b at intr_event_execute_handlers+0x13b >> #6 0xc05434eb at ithread_loop+0x6b >> #7 0xc053efb7 at fork_exit+0x97 >> #8 0xc0806744 at fork_trampoline+0x8 >> >> Thanks very much, >> >> Charles > Take a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/172113 that contains > simple workaround in followup message not involving any patching, and the fix. > > Eugene Grosbein > Eugene, thanks very much for the pointer. This is definitely what we were looking for! -- Charles Charles Owens Great Bay Software, Inc. From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 15:35:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87AA7A4D for ; Mon, 12 Nov 2012 15:35:14 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD4E8FC13 for ; Mon, 12 Nov 2012 15:35:13 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so3102378eaa.13 for ; Mon, 12 Nov 2012 07:35:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LBUZNq+VgriUYV/BBG+PHmmfMSfxC+c9g77tEKSAJ3k=; b=hAgGZuwyteAKOqiOhDEb6UlDU7NOBVb3frsLwOV10GvFpNAEzx3R50iRcoMizhRNV2 9kUfjeug9DtAoPFPYsUPI1I8uqMgPrWWHSZqBTEMvzbPjms34m/8dcIchtcUaDhQT44T jh2X2QTu+pqPSkd2JVwun8SAdcZLDyAVcAo2SgmsUImIieOZyXOCkgilAOYKv372KOVn T0BvwtDiz9/Du9E+qreIf/Dc0zDpRYF2mi9KE5gzVFn7I7NVRJ0CBCngMOm3RE0PV/NF 3pkMQmEbnJkpCQVu0uRihecpVBumaPKQSvuxg5n1mLUrLbvgq1FFsKGvuBeVKutFkXDs 3R8A== MIME-Version: 1.0 Received: by 10.14.215.69 with SMTP id d45mr64041854eep.16.1352734512124; Mon, 12 Nov 2012 07:35:12 -0800 (PST) Received: by 10.14.211.137 with HTTP; Mon, 12 Nov 2012 07:35:12 -0800 (PST) In-Reply-To: References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Mon, 12 Nov 2012 07:35:12 -0800 Message-ID: Subject: Re: nomenclature for conf files From: Kurt Buff To: Chris Rees Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD , Zoran Kolic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 15:35:14 -0000 On Mon, Nov 12, 2012 at 12:29 AM, Chris Rees wrote: > > On 12 Nov 2012 05:20, "Kurt Buff" wrote: >> >> On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: >> > It might sound stupid, but I'd like to know if there's >> > any difference. Are those 3 line the same? >> > >> > WITH_KMS=YES >> > WITH_KMS="YES" >> > WITH_KMS=yes >> >> With regard to their use in /etc/rc.conf, no, absolutely not. >> >> In general, from my experience, only the second one will work. >> >> This might, or might not, be true for other uses, but rc.conf is >> pretty picky about this. > > All three are fine in make.conf and rc.conf > > The issue with rc.conf is when people put spaces around the = sign. > > Chris This has not been my experience - but I will experiment soon and see if I can verify. Kurt From owner-freebsd-stable@FreeBSD.ORG Mon Nov 12 15:51:57 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BF46D26 for ; Mon, 12 Nov 2012 15:51:57 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 096158FC0C for ; Mon, 12 Nov 2012 15:51:56 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so1532786bkc.13 for ; Mon, 12 Nov 2012 07:51:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e9XmUCr+WFsxAM6Ogrgy6eE/1/OUto3QiVH7JOfglkU=; b=0aBNfMw08e2lWD/LKyNXb2q+vSEjMs154hCXBNi2kcgJcTxniuWkG36a2Nhj31GQdl 4CA2KZUxS2Ll47fELL2SJZJKBW6drHk3iHwU70+TdRhhRjVYJ+ZJRgxHqJnYzqeCMW5I sfxrmrqqVFFAmL2oZHEwpG24L6sB3k7aecPnQ7ktozvVB8wLKl1Bjiv/J+r6T5kX3gm0 M6XTCVjsPHgsom1IVvOaZb1Gzm4IAZ3ktak+k9b+FWJa+wi4qq0vgiKfnlf1TqPOFe5x DDTJnTi6z+f5huD2Fs0FlJn9PVDW44SKbLB0lBUWHdzktf/NTU6cMpuT9tlsKZVawnQg UExw== MIME-Version: 1.0 Received: by 10.204.7.213 with SMTP id e21mr7127310bke.32.1352735515945; Mon, 12 Nov 2012 07:51:55 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 07:51:55 -0800 (PST) Received: by 10.204.50.197 with HTTP; Mon, 12 Nov 2012 07:51:55 -0800 (PST) In-Reply-To: References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Mon, 12 Nov 2012 15:51:55 +0000 Message-ID: Subject: Re: nomenclature for conf files From: Chris Rees To: Kurt Buff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD , Zoran Kolic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2012 15:51:57 -0000 On 12 Nov 2012 15:35, "Kurt Buff" wrote: > > On Mon, Nov 12, 2012 at 12:29 AM, Chris Rees wrote: > > > > On 12 Nov 2012 05:20, "Kurt Buff" wrote: > >> > >> On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > >> > It might sound stupid, but I'd like to know if there's > >> > any difference. Are those 3 line the same? > >> > > >> > WITH_KMS=YES > >> > WITH_KMS="YES" > >> > WITH_KMS=yes > >> > >> With regard to their use in /etc/rc.conf, no, absolutely not. > >> > >> In general, from my experience, only the second one will work. > >> > >> This might, or might not, be true for other uses, but rc.conf is > >> pretty picky about this. > > > > All three are fine in make.conf and rc.conf > > > > The issue with rc.conf is when people put spaces around the = sign. > > > > Chris > > This has not been my experience - but I will experiment soon and see > if I can verify. Anything that complains about any of those syntaxes is a bug. Please file a PR if you find any examples. Chris From owner-freebsd-stable@FreeBSD.ORG Tue Nov 13 11:28:09 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACD07C28 for ; Tue, 13 Nov 2012 11:28:09 +0000 (UTC) (envelope-from sneakywumpus@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 366108FC12 for ; Tue, 13 Nov 2012 11:28:08 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id jm19so1926423bkc.13 for ; Tue, 13 Nov 2012 03:28:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer; bh=afCwmaM8h7XL6qx6M1+hqTIpe6+X4rUITEoIt6/asqk=; b=mKJ2xZlZPxIqr50Ht80ZV+BqpJ6lIdUga2iiEhYGfnJQgaOK0QasXxXFNgfuFua53X NSAjWmYA1xsU8SxvgdfNxxsR4/5OrJcBhWOqJBuYNZKzybEvO68X1AEzuLLlRtnQzAUc pXsZ1qL51ScVg2nyqo8Yj+gMIz24e572cE1ybiIr3ouZJ1Jd9+wPzfI+XEULF0JYPa0p BfoX6is/fN9Wlj9WSAlCF/G3wqwCNwnlGg8WBZKuuB/CdUTo0jTKc9JQWEHeX7tRXxpd H3jfBfuusUryC1QnI9dryVWdubYFXxbCevPCUN2bmHR1Y/PgwgcDS/2V9MD6nZpnWh5U 5dFA== Received: by 10.204.147.132 with SMTP id l4mr2187418bkv.20.1352806087801; Tue, 13 Nov 2012 03:28:07 -0800 (PST) Received: from ed209.fritz.box (77-23-67-63-dynip.superkabel.de. [77.23.67.63]) by mx.google.com with ESMTPS id 9sm5202422bkq.13.2012.11.13.03.28.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Nov 2012 03:28:06 -0800 (PST) From: Thomas Eberhardt Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: can't build sysutils/apcupsd on 9.1-RC3 Message-Id: Date: Tue, 13 Nov 2012 12:28:06 +0100 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2012 11:28:09 -0000 Just tested out FreeBSD 9.1-RC3 and i can't build sysutils/apcupsd = because of http://www.freebsd.org/cgi/query-pr.cgi?pr=3D169901. Error messages are: =85... LD src/apcupsd = /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.= o): In function `astring::assign(char const*, int)': astring.cpp:(.text+0x6c): undefined reference to `operator = new[](unsigned long)' = /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.= o): In function `astring::realloc(unsigned int)': astring.cpp:(.text+0x1de): undefined reference to `operator = new[](unsigned long)' = /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/lib/libapc.a(astring.= o): In function `astring::vformat(char const*, __va_list_tag*)': astring.cpp:(.text+0x48e): undefined reference to `operator = new[](unsigned long)' gmake[2]: *** [apcupsd] Error 1 gmake[1]: *** [all] Error 2 gmake: *** [src_DIR] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/sysutils/apcupsd. *** [build] Error code 1 Stop in /usr/ports/sysutils/apcupsd. There is also an older report by me http://www.freebsd.org/cgi/query-pr.cgi?pr=3D168631 that can be closed if this gets fixed. Best regards, Thomas Eberhardt From owner-freebsd-stable@FreeBSD.ORG Tue Nov 13 16:49:49 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88FB096E for ; Tue, 13 Nov 2012 16:49:49 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4E6EA8FC14 for ; Tue, 13 Nov 2012 16:49:49 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id x2so1014410iad.13 for ; Tue, 13 Nov 2012 08:49:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rfe9gkIw+pa8e/jS0wGDPzm2Rc5JWWsB4sH9+buZm4U=; b=OdOOHAHZUl5g7BLOC6P/9G4eWUsiu5RHtPweLCrgBvmhYnnqxG8ag7+ppd821FsEdd X8RXRSFiA388kNMUO2FGUdxifSCn57tx3I2MM3E9S9wL6BVIDq8Um9logL67IaEJtb7h bEgjbWXAZjBpw2sAKdcaoiHZRwUVz8v3b2hrXHdFOCPgENhTMUc3TuQ2Wkjvu6M+MMZx VVoeRHgb7MIfAI6Za925P+ANcPtSEpyFVor0n8Zj/M2Qc2MZ8tTYHYVqovEClRuvt2FX KSLtgLQ1iJhKdHwT+Zo0WiccU4KWpqcgTsiT2EtZBc7S3EnBBUvFTc9r9nP+5WOnN/G4 VLqA== MIME-Version: 1.0 Received: by 10.50.185.195 with SMTP id fe3mr11572322igc.25.1352825388501; Tue, 13 Nov 2012 08:49:48 -0800 (PST) Received: by 10.64.30.11 with HTTP; Tue, 13 Nov 2012 08:49:47 -0800 (PST) In-Reply-To: <20121112051229.GA1235@mycenae.sbb.rs> References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Tue, 13 Nov 2012 11:49:47 -0500 Message-ID: Subject: Re: nomenclature for conf files From: "illoai@gmail.com" To: Zoran Kolic Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2012 16:49:49 -0000 On 12 November 2012 00:12, Zoran Kolic wrote: > It might sound stupid, but I'd like to know if there's > any difference. Are those 3 line the same? > > WITH_KMS=YES > WITH_KMS="YES" > WITH_KMS=yes > > Best regards In /etc/make.conf it shouldn't matter: they should all be treated as synonyms for: WITH_KMS= -- -- From owner-freebsd-stable@FreeBSD.ORG Tue Nov 13 17:42:44 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4001CCE for ; Tue, 13 Nov 2012 17:42:44 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 90A118FC08 for ; Tue, 13 Nov 2012 17:42:43 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TYKVW-0002U9-Vm for freebsd-stable@freebsd.org; Tue, 13 Nov 2012 09:42:42 -0800 Date: Tue, 13 Nov 2012 09:42:42 -0800 (PST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1352828562964-5760661.post@n5.nabble.com> In-Reply-To: References: <20121112051229.GA1235@mycenae.sbb.rs> Subject: Re: nomenclature for conf files MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2012 17:42:44 -0000 > Also, the FreeBSD makefiles and sources test all WITH_* variables with > .ifdef or #ifdef so the value doesn't matter and can even be empty. This is exactly the point. But I still use 'yes' just for mnemotechnical reason. -- View this message in context: http://freebsd.1045724.n5.nabble.com/nomenclature-for-conf-files-tp5760163p5760661.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Tue Nov 13 18:02:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 03B86101 for ; Tue, 13 Nov 2012 18:02:14 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFCB8FC19 for ; Tue, 13 Nov 2012 18:02:13 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so3702073eaa.13 for ; Tue, 13 Nov 2012 10:02:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pAIJUXbDTFbnEm3IS7auHZkTTs2ax1sukjb4XwXQlcY=; b=Mfyz4qyV1Q5owdEf9EGirhJ0GugcPulB4KdlcoK3E/7rjHLI902ydujXa8KalUi5sc BTR4xMJyI0na0U0toaTwSEI+GhaNAKk21f5Bn13Ewg4HyxTXYw/lorKxphKzGYdQk8xw 21Y6YwcU9kfElVk8Rno2upQ6pEb7TcFvzahyYfz2kcjOn/nFt05L+7VMsrzSDaOhtgQa 7jN9MxXkWpYxWo69ft3GiqmdkJgSRQaPpPMPs3IR0Dcu0Eiai4b026IkTLZxDVaOdci1 w5CqnMceXBXxiTxNAgTtj4Na4wxM5XZXd5Pfj3oW6s7j1bbqVWkqjmwq0vWf8DbAuvup 5U1Q== MIME-Version: 1.0 Received: by 10.14.215.197 with SMTP id e45mr15130523eep.0.1352829732375; Tue, 13 Nov 2012 10:02:12 -0800 (PST) Received: by 10.14.211.137 with HTTP; Tue, 13 Nov 2012 10:02:12 -0800 (PST) In-Reply-To: References: <20121112051229.GA1235@mycenae.sbb.rs> Date: Tue, 13 Nov 2012 10:02:12 -0800 Message-ID: Subject: Re: nomenclature for conf files From: Kurt Buff To: Chris Rees Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2012 18:02:14 -0000 OK - I figured it out. I have always followed the examples in the handbook. I have also been bitten more than once when I've typoed, and left out one of the quote marks. That tends to leave a lasting impression, as it can be painful to fix, sometimes requiring to drop into single user mode to clean up. Kurt On Mon, Nov 12, 2012 at 7:51 AM, Chris Rees wrote: > > On 12 Nov 2012 15:35, "Kurt Buff" wrote: > > > > On Mon, Nov 12, 2012 at 12:29 AM, Chris Rees wrote: > > > > > > On 12 Nov 2012 05:20, "Kurt Buff" wrote: > > >> > > >> On Sun, Nov 11, 2012 at 9:12 PM, Zoran Kolic wrote: > > >> > It might sound stupid, but I'd like to know if there's > > >> > any difference. Are those 3 line the same? > > >> > > > >> > WITH_KMS=YES > > >> > WITH_KMS="YES" > > >> > WITH_KMS=yes > > >> > > >> With regard to their use in /etc/rc.conf, no, absolutely not. > > >> > > >> In general, from my experience, only the second one will work. > > >> > > >> This might, or might not, be true for other uses, but rc.conf is > > >> pretty picky about this. > > > > > > All three are fine in make.conf and rc.conf > > > > > > The issue with rc.conf is when people put spaces around the = sign. > > > > > > Chris > > > > This has not been my experience - but I will experiment soon and see > > if I can verify. > > Anything that complains about any of those syntaxes is a bug. Please file > a PR if you find any examples. > > Chris > From owner-freebsd-stable@FreeBSD.ORG Tue Nov 13 18:31:17 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00E2687A for ; Tue, 13 Nov 2012 18:31:16 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) by mx1.freebsd.org (Postfix) with ESMTP id A1C598FC0C for ; Tue, 13 Nov 2012 18:31:14 +0000 (UTC) Received: from [2001:1620:2013:1:e8ec:d52:8672:17b] (port=65228) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TYLG5-000Jwk-8d for freebsd-stable@freebsd.org; Tue, 13 Nov 2012 19:30:49 +0100 From: Markus Gebert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC Message-Id: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> Date: Tue, 13 Nov 2012 19:30:34 +0100 To: freebsd-stable Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2012 18:31:17 -0000 Hi there We have a pair of servers running FreeBSD 9.1-RC3 that act as = transparent layer 7 loadbalancer (relayd) and pop/imap proxy (dovecot). = Only one of them is active at a given time, it's a failover setup. =46rom = time to time the active one gets in a state in which the 'thread taskq' = thread uses up 100% of one cpu on its own, like here: ---- PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU = COMMAND 0 root 8 0 0K 3968K CPU12 12 9:49 100.00% = kernel{thread taskq} ---- Most of the userland processes get stalled and if the sitation is not = resolved, their network services stop responding alltogether after some = time. This affects relayd and dovecot for sure, but not sshd. When processes are slow, they often block in states like '*unp_l' or = 'pipewr' according to top, and overall cpu time spent in kernel grows by = factors (and system load too). See [0], [1], [2] for top screenshots = when things work badly. Under normal circumstances load is below 5 and = systime below 5%. Load during daytime makes this situation more likely = to occur. At the same time it does _not_ seem to be triggered by any = sudden load peaks (e.g. more network connections etc.), so I guess it's = some kind of race condition. Today I had the chance to get a few ddb traces of the 'thread taskq' = while the problem was occuring. Every few seconds I ran a ddb script and = continued. I got five samples, after that ddb became unresponsive. All = of them show the thread executing in unp_gc() like here: ---- unp_gc() at unp_gc+0x81 taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe ---- See all samples under [3]. This is consistent with some textdumps and ddb sessions I've done. Also, = the sysctl 'net.local.taskcount' seems to increase at much higher rates = when the problem occurs. To me it looks like the unix socket GC is triggered way too often and/or = running too long, which uses cpu and worse, causes a lot of contention = around the unp_list_lock which in turn causes delays for all processes = relaying on unix sockets for IPC. I don't know why the unp_gc() is called so often and what's triggering = this. Sometimes this condition only lasts for a few seconds and then resolves = itself before the thread taskq reaches 100% cpu usage. Sometimes it will = last, render dovecot/relayd unresponsive and can only be resolved by = taking load off the system (forcefully restart services). Booting a kernel with INVARIANTS and WITNESS did not bring much more = clues. The system ends up panicing with 'soabort: so_count' after a few = minutes of load, but the trace[4] does not seem related to unix sockets, = so that might be another problem. System info, boot dmesg and some configs can be found under [5]. I hope somebody can help me debug this further. Markus [0] last pid: 10227; load averages: 18.81, 13.02, 8.09 = up 0+18:14:55 13:07:53 136 processes: 4 running, 53 sleeping, 1 waiting, 78 lock CPU 0: 5.9% user, 0.0% nice, 54.5% system, 3.5% interrupt, 36.1% = idle CPU 1: 5.9% user, 0.0% nice, 56.5% system, 3.1% interrupt, 34.5% = idle CPU 2: 4.3% user, 0.0% nice, 58.8% system, 3.9% interrupt, 32.9% = idle CPU 3: 6.3% user, 0.0% nice, 60.4% system, 2.0% interrupt, 31.4% = idle CPU 4: 3.5% user, 0.0% nice, 59.2% system, 2.7% interrupt, 34.5% = idle CPU 5: 3.9% user, 0.0% nice, 60.0% system, 1.6% interrupt, 34.5% = idle CPU 6: 4.3% user, 0.0% nice, 62.0% system, 1.2% interrupt, 32.5% = idle CPU 7: 8.6% user, 0.0% nice, 56.9% system, 0.8% interrupt, 33.7% = idle CPU 8: 5.1% user, 0.0% nice, 59.1% system, 0.0% interrupt, 35.8% = idle CPU 9: 7.1% user, 0.0% nice, 56.3% system, 0.0% interrupt, 36.6% = idle CPU 10: 4.7% user, 0.0% nice, 61.0% system, 0.0% interrupt, 34.3% = idle CPU 11: 5.5% user, 0.0% nice, 60.8% system, 0.0% interrupt, 33.7% = idle CPU 12: 6.3% user, 0.0% nice, 61.8% system, 0.4% interrupt, 31.5% = idle CPU 13: 8.3% user, 0.0% nice, 57.1% system, 0.0% interrupt, 34.6% = idle CPU 14: 9.1% user, 0.0% nice, 58.3% system, 0.0% interrupt, 32.7% = idle CPU 15: 7.9% user, 0.0% nice, 55.9% system, 0.0% interrupt, 36.2% = idle CPU 16: 13.4% user, 0.0% nice, 52.8% system, 0.0% interrupt, 33.9% = idle CPU 17: 9.8% user, 0.0% nice, 55.3% system, 0.0% interrupt, 34.9% = idle CPU 18: 5.9% user, 0.0% nice, 62.0% system, 0.0% interrupt, 32.2% = idle CPU 19: 5.1% user, 0.0% nice, 62.6% system, 0.0% interrupt, 32.3% = idle CPU 20: 5.5% user, 0.0% nice, 60.8% system, 0.0% interrupt, 33.7% = idle CPU 21: 10.6% user, 0.0% nice, 57.1% system, 0.0% interrupt, 32.3% = idle CPU 22: 5.9% user, 0.0% nice, 58.8% system, 0.0% interrupt, 35.3% = idle CPU 23: 6.3% user, 0.0% nice, 59.6% system, 0.0% interrupt, 34.1% = idle Mem: 3551M Active, 1351M Inact, 2905M Wired, 8K Cache, 7488K Buf, 85G = Free ARC: 1073M Total, 107M MRU, 828M MFU, 784K Anon, 7647K Header, 130M = Other Swap: 8192M Total, 8192M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU = COMMAND 11 root 24 155 ki31 0K 384K CPU23 23 431.4H 847.95% = idle 0 root 248 -8 0 0K 3968K - 1 10:24 89.45% = kernel 2880 _relayd 1 79 0 69608K 54764K *unp_l 22 18:47 25.68% = relayd 2879 _relayd 1 80 0 49128K 34232K *unp_l 6 9:22 25.29% = relayd 2881 _relayd 1 79 0 73704K 57092K *unp_l 9 2:54 24.76% = relayd 2877 _relayd 1 79 0 2948M 2936M *unp_l 1 24:25 24.27% = relayd 2873 root 1 79 0 22584K 4180K *unp_l 23 1:38 23.68% = relayd 3017 root 1 79 0 19860K 2316K *unp_l 2 2:58 22.66% = log 2878 _relayd 1 79 0 57320K 42428K *unp_l 3 17:27 22.27% = relayd 3010 dovenull 1 31 0 67240K 39408K CPU6 6 4:06 22.27% = imap-login 7607 dovecot 1 78 0 58036K 9580K *unp_l 23 1:02 22.27% = auth 3009 dovenull 1 78 0 67240K 39756K *unp_l 17 3:06 21.88% = imap-login 3004 dovenull 1 78 0 63144K 36512K *unp_l 8 1:42 21.29% = imap-login 2998 dovenull 1 78 0 67240K 39556K *unp_l 13 2:47 21.09% = imap-login 7619 dovenull 1 43 0 50856K 25264K *unp_l 12 0:53 21.09% = imap-login 3006 dovenull 1 78 0 63144K 38464K *unp_l 15 3:14 20.65% = imap-login 83740 dovenull 1 78 0 59048K 30956K *unp_l 12 1:57 20.65% = imap-login 2993 dovenull 1 47 0 63144K 37984K *unp_l 17 1:39 20.65% = imap-login 3007 dovenull 1 78 0 63144K 38736K *unp_l 21 3:19 20.56% = imap-login 2994 dovenull 1 78 0 67240K 40144K *unp_l 11 3:52 20.46% = imap-login 7679 dovenull 1 78 0 50856K 24804K *unp_l 4 0:54 20.46% = imap-login 7690 dovenull 1 78 0 50856K 25444K *unp_l 17 0:50 20.46% = imap-login 3008 dovenull 1 78 0 67240K 39248K *unp_l 15 3:16 20.36% = imap-login 3001 dovenull 1 78 0 59048K 34072K *unp_l 21 1:45 20.26% = imap-login 84187 dovenull 1 78 0 63144K 38116K *unp_l 4 3:19 20.07% = imap-login 3000 dovenull 1 78 0 63144K 38832K *unp_l 6 3:40 19.97% = imap-login 83594 dovenull 1 78 0 54952K 28620K *unp_l 9 1:39 19.97% = imap-login 2992 dovenull 1 78 0 67240K 39876K *unp_l 0 3:27 19.87% = imap-login 3012 dovenull 1 78 0 63144K 39064K *unp_l 22 3:03 19.78% = imap-login 87238 dovenull 1 77 0 63144K 39028K *unp_l 1 2:45 19.78% = imap-login 87057 dovenull 1 77 0 67240K 39388K *unp_l 3 2:58 19.68% = imap-login 86973 dovenull 1 77 0 63144K 38464K *unp_l 2 2:52 19.68% = imap-login 85175 dovenull 1 77 0 63144K 38832K *unp_l 12 2:57 19.58% = imap-login 7618 dovenull 1 78 0 54952K 26424K *unp_l 2 0:53 19.58% = imap-login 2995 dovenull 1 77 0 67240K 40504K *unp_l 16 3:02 19.48% = imap-login 86151 dovenull 1 77 0 63144K 38484K *unp_l 11 2:53 19.48% = imap-login 83822 dovenull 1 78 0 63144K 36436K *unp_l 9 2:21 19.48% = imap-login 86132 dovenull 1 78 0 63144K 37948K *unp_l 7 2:59 19.38% = imap-login 7689 dovenull 1 78 0 50856K 25064K *unp_l 19 0:55 19.38% = imap-login 84186 dovenull 1 77 0 63144K 38252K *unp_l 18 2:54 19.09% = imap-login 2999 dovenull 1 77 0 63144K 37760K *unp_l 13 2:00 19.09% = imap-login 3011 dovenull 1 36 0 63144K 36624K *unp_l 3 1:48 19.09% = imap-login 2996 dovenull 1 45 0 63144K 38972K *unp_l 7 3:24 18.99% = imap-login 83731 dovenull 1 45 0 54952K 28824K *unp_l 8 1:48 18.80% = imap-login 3002 dovenull 1 36 0 50856K 22748K *unp_l 19 0:55 18.65% = imap-login 25589 dovenull 1 40 0 63144K 37164K *unp_l 4 1:42 18.46% = imap-login 3021 dovecot 1 77 0 23952K 8924K *unp_l 10 2:04 18.36% = director 2997 dovenull 1 77 0 63144K 38872K *unp_l 16 3:13 18.26% = imap-login [1] last pid: 15656; load averages: 29.20, 16.70, 10.67 = up 0+18:43:35 13:36:33 525 processes: 44 running, 426 sleeping, 55 waiting CPU 0: 1.9% user, 0.0% nice, 67.4% system, 1.5% interrupt, 29.1% = idle CPU 1: 1.9% user, 0.0% nice, 72.8% system, 0.8% interrupt, 24.5% = idle CPU 2: 0.8% user, 0.0% nice, 70.1% system, 0.8% interrupt, 28.4% = idle CPU 3: 1.5% user, 0.0% nice, 70.1% system, 1.9% interrupt, 26.4% = idle CPU 4: 0.0% user, 0.0% nice, 73.6% system, 0.8% interrupt, 25.7% = idle CPU 5: 1.9% user, 0.0% nice, 69.0% system, 0.8% interrupt, 28.4% = idle CPU 6: 0.8% user, 0.0% nice, 69.7% system, 1.5% interrupt, 28.0% = idle CPU 7: 0.0% user, 0.0% nice, 73.2% system, 3.1% interrupt, 23.8% = idle CPU 8: 2.3% user, 0.0% nice, 77.8% system, 0.0% interrupt, 19.9% = idle CPU 9: 2.3% user, 0.0% nice, 74.3% system, 0.0% interrupt, 23.4% = idle CPU 10: 1.1% user, 0.0% nice, 75.1% system, 0.0% interrupt, 23.8% = idle CPU 11: 1.2% user, 0.0% nice, 65.0% system, 0.0% interrupt, 33.8% = idle CPU 12: 0.0% user, 0.0% nice, 77.0% system, 0.0% interrupt, 23.0% = idle CPU 13: 0.8% user, 0.0% nice, 76.2% system, 0.0% interrupt, 23.0% = idle CPU 14: 1.1% user, 0.0% nice, 75.1% system, 0.0% interrupt, 23.8% = idle CPU 15: 0.8% user, 0.0% nice, 75.9% system, 0.0% interrupt, 23.4% = idle CPU 16: 0.8% user, 0.0% nice, 73.6% system, 0.0% interrupt, 25.7% = idle CPU 17: 2.3% user, 0.0% nice, 74.3% system, 0.0% interrupt, 23.4% = idle CPU 18: 1.1% user, 0.0% nice, 70.5% system, 0.0% interrupt, 28.4% = idle CPU 19: 0.8% user, 0.0% nice, 73.6% system, 0.0% interrupt, 25.7% = idle CPU 20: 3.4% user, 0.0% nice, 75.9% system, 0.0% interrupt, 20.7% = idle CPU 21: 1.9% user, 0.0% nice, 76.6% system, 0.0% interrupt, 21.5% = idle CPU 22: 1.9% user, 0.0% nice, 75.5% system, 0.0% interrupt, 22.6% = idle CPU 23: 1.1% user, 0.0% nice, 75.5% system, 0.0% interrupt, 23.4% = idle Mem: 688M Active, 1431M Inact, 3064M Wired, 8K Cache, 7488K Buf, 88G = Free ARC: 1212M Total, 107M MRU, 965M MFU, 1040K Anon, 8010K Header, 131M = Other Swap: 8192M Total, 8192M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU = COMMAND 0 root 8 0 0K 3968K CPU12 12 9:49 100.00% = kernel{thread taskq} 2873 root 84 0 22584K 4180K CPU1 1 2:53 44.58% = relayd 2879 _relayd 84 0 49128K 34268K CPU9 1 12:17 43.26% = relayd 2877 _relayd 52 0 69608K 54400K kqread 22 30:07 39.45% = relayd 2880 _relayd 84 0 65512K 50692K CPU21 21 23:22 39.36% = relayd 2878 _relayd 52 0 57320K 42432K kqread 14 21:54 39.16% = relayd 2881 _relayd 83 0 49128K 31572K CPU4 4 4:34 38.67% = relayd 7607 dovecot 82 0 58036K 10528K CPU16 16 2:31 37.50% auth 3017 root 83 0 19860K 2316K CPU6 6 4:25 36.47% log 3021 dovecot 82 0 23952K 8924K CPU5 5 3:19 34.47% = director 11 root 155 ki31 0K 384K CPU11 11 18.4H 32.96% = idle{idle: cpu11} 11 root 155 ki31 0K 384K RUN 4 18.4H 32.86% = idle{idle: cpu4} 11 root 155 ki31 0K 384K RUN 3 18.4H 32.76% = idle{idle: cpu3} 11 root 155 ki31 0K 384K RUN 2 18.4H 32.67% = idle{idle: cpu2} 11 root 155 ki31 0K 384K RUN 9 18.4H 32.57% = idle{idle: cpu9} 11 root 155 ki31 0K 384K RUN 5 18.4H 32.57% = idle{idle: cpu5} 11 root 155 ki31 0K 384K RUN 0 18.4H 32.37% = idle{idle: cpu0} 11 root 155 ki31 0K 384K CPU22 22 18.3H 32.37% = idle{idle: cpu22} 11 root 155 ki31 0K 384K RUN 7 18.4H 32.28% = idle{idle: cpu7} 11 root 155 ki31 0K 384K CPU14 14 18.3H 32.08% = idle{idle: cpu14} 11 root 155 ki31 0K 384K RUN 6 18.4H 31.88% = idle{idle: cpu6} 11 root 155 ki31 0K 384K RUN 1 18.4H 31.79% = idle{idle: cpu1} 11 root 155 ki31 0K 384K RUN 19 18.3H 31.59% = idle{idle: cpu19} 11 root 155 ki31 0K 384K RUN 8 18.4H 30.96% = idle{idle: cpu8} 7619 dovenull 81 0 59048K 32864K CPU20 20 2:01 30.96% = imap-login 11 root 155 ki31 0K 384K CPU18 18 18.3H 30.76% = idle{idle: cpu18} 11 root 155 ki31 0K 384K RUN 13 18.3H 30.57% = idle{idle: cpu13} 11 root 155 ki31 0K 384K RUN 12 18.3H 30.47% = idle{idle: cpu12} 11 root 155 ki31 0K 384K RUN 20 18.3H 30.08% = idle{idle: cpu20} 11 root 155 ki31 0K 384K RUN 10 18.4H 29.88% = idle{idle: cpu10} 11 root 155 ki31 0K 384K RUN 23 18.3H 29.79% = idle{idle: cpu23} 11 root 155 ki31 0K 384K RUN 15 18.3H 29.59% = idle{idle: cpu15} 11 root 155 ki31 0K 384K RUN 16 18.3H 29.59% = idle{idle: cpu16} 2968 dovenull 52 0 38568K 12240K pipewr 4 5:24 29.39% = pop3-login 11 root 155 ki31 0K 384K RUN 17 18.3H 29.30% = idle{idle: cpu17} 2970 dovenull 52 0 42664K 15968K pipewr 10 7:18 28.66% = pop3-login 2983 dovenull 52 0 38568K 11984K pipewr 5 5:03 28.66% = pop3-login 2976 dovenull 52 0 42664K 17896K pipewr 23 7:46 28.56% = pop3-login 2974 dovenull 52 0 46760K 19156K pipewr 16 7:40 28.47% = pop3-login 2969 dovenull 52 0 38568K 13764K pipewr 12 5:13 28.27% = pop3-login 2990 dovenull 52 0 42664K 16096K pipewr 0 7:22 28.17% = pop3-login 2984 dovenull 52 0 38568K 12796K pipewr 14 5:43 28.08% = pop3-login 2988 dovenull 52 0 42664K 16068K pipewr 2 6:42 27.98% = pop3-login 11 root 155 ki31 0K 384K RUN 21 18.3H 27.88% = idle{idle: cpu21} 2971 dovenull 52 0 38568K 10724K pipewr 0 2:06 27.88% = pop3-login 2989 dovenull 52 0 38568K 12428K pipewr 10 5:21 27.78% = pop3-login 2972 dovenull 52 0 42664K 17876K pipewr 5 7:42 27.69% = pop3-login 2987 dovenull 52 0 42664K 14992K pipewr 16 5:23 27.69% = pop3-login 2981 dovenull 52 0 42664K 16060K pipewr 19 7:32 27.59% = pop3-login [2] last pid: 38598; load averages: 42.11, 22.97, 11.77 = up 0+20:46:40 15:39:38 520 processes: 96 running, 369 sleeping, 55 waiting CPU: 2.8% user, 0.0% nice, 82.3% system, 0.4% interrupt, 14.5% idle Mem: 939M Active, 837M Inact, 3787M Wired, 8K Cache, 7488K Buf, 88G Free ARC: 1884M Total, 108M MRU, 1633M MFU, 914K Anon, 9764K Header, 132M = Other Swap: 8192M Total, 8192M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU = COMMAND 0 root 8 0 0K 3968K CPU20 14 16:09 100.00% = kernel{thread taskq} 2880 _relayd 100 0 65512K 50128K RUN 11 44:06 89.79% = relayd 2881 _relayd 100 0 61416K 44116K RUN 10 8:13 89.45% = relayd 15779 dovenull 98 0 38568K 13236K RUN 17 3:28 86.28% = pop3-login 15771 dovenull 99 0 38568K 12672K RUN 2 5:17 86.08% = pop3-login 15761 dovenull 98 0 38568K 13212K RUN 23 5:15 84.77% = pop3-login 15768 dovenull 99 0 38568K 13268K RUN 12 5:43 84.18% = pop3-login 15775 dovenull 98 0 42664K 14536K RUN 7 4:05 84.08% = pop3-login 17610 dovenull 98 0 50856K 26204K RUN 18 2:09 83.50% = imap-login 16944 dovenull 98 0 54952K 28332K RUN 20 1:42 83.40% = imap-login 15803 dovenull 98 0 67240K 39640K RUN 15 2:48 83.06% = imap-login 15800 dovenull 98 0 63144K 38892K RUN 9 3:15 82.86% = imap-login 20530 dovenull 98 0 63144K 38136K RUN 4 2:57 82.76% = imap-login 12 root -92 - 0K 880K WAIT 0 6:16 82.47% = intr{irq274: ix1:que } 12 root -92 - 0K 880K WAIT 1 6:16 82.37% = intr{irq275: ix1:que } 12 root -92 - 0K 880K WAIT 7 6:05 82.28% = intr{irq281: ix1:que } 12 root -92 - 0K 880K WAIT 2 6:00 82.28% = intr{irq276: ix1:que } 12 root -92 - 0K 880K WAIT 6 5:50 82.28% = intr{irq280: ix1:que } 12 root -60 - 0K 880K WAIT 0 3:20 82.18% = intr{swi4: clock} 12 root -92 - 0K 880K WAIT 4 6:10 82.08% = intr{irq278: ix1:que } 12 root -92 - 0K 880K WAIT 5 5:59 81.98% = intr{irq279: ix1:que } 0 root -92 0 0K 3968K - 23 0:47 81.88% = kernel{ix1 que} 0 root -92 0 0K 3968K - 5 0:43 80.18% = kernel{ix0 que} 17945 root 95 0 16592K 4056K CPU7 0 0:08 75.10% top 15765 dovenull 77 0 46760K 20468K RUN 2 5:41 19.48% = pop3-login 15762 dovenull 78 0 46760K 20708K RUN 20 5:45 19.38% = pop3-login 15773 dovenull 78 0 42664K 14928K RUN 4 3:41 19.38% = pop3-login 15781 dovenull 77 0 42664K 13136K RUN 9 3:01 18.90% = pop3-login 15777 dovenull 77 0 42664K 15840K RUN 1 3:15 18.55% = pop3-login 15772 dovenull 77 0 42664K 14484K RUN 0 5:15 18.46% = pop3-login 15782 dovenull 77 0 38568K 13368K RUN 6 3:20 17.87% = pop3-login 15764 dovenull 77 0 42664K 14816K RUN 20 5:54 17.77% = pop3-login 15759 dovenull 77 0 42664K 16616K RUN 4 1:06 17.77% = pop3-login 15780 dovenull 76 0 42664K 13684K RUN 22 3:19 12.89% = pop3-login [3] db:0:kdb.enter.sysctl> run lockinfo db:1:lockinfo> show locks No such command db:1:locks> show alllocks No such command db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.sysctl> trace 100058 Tracing pid 0 tid 100058 td 0xfffffe00262fc000 cpustop_handler() at cpustop_handler+0x28 ipi_nmi_handler() at ipi_nmi_handler+0x3d trap() at trap+0x2ea nmi_calltrap() at nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff809a2a3e, rsp =3D 0xffffff800039efe0, = rbp =3D 0xffffff975cf4aa10 --- unp_gc() at unp_gc+0x20e taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff975cf4abb0, rbp =3D 0 --- db:0:kdb.enter.sysctl> capture off db:0:kdb.enter.sysctl> run lockinfo db:1:lockinfo> show locks No such command db:1:locks> show alllocks No such command db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.sysctl> trace 100058 Tracing pid 0 tid 100058 td 0xfffffe00262fc000 cpustop_handler() at cpustop_handler+0x28 ipi_nmi_handler() at ipi_nmi_handler+0x3d trap() at trap+0x2ea nmi_calltrap() at nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff809a29a6, rsp =3D 0xffffff800039efe0, = rbp =3D 0xffffff975cf4aa10 --- unp_gc() at unp_gc+0x176 taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff975cf4abb0, rbp =3D 0 --- db:0:kdb.enter.sysctl> capture off db:0:kdb.enter.sysctl> run lockinfo db:1:lockinfo> show locks No such command db:1:locks> show alllocks No such command db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.sysctl> trace 100058 Tracing pid 0 tid 100058 td 0xfffffe00262fc000 cpustop_handler() at cpustop_handler+0x28 ipi_nmi_handler() at ipi_nmi_handler+0x3d trap() at trap+0x2ea nmi_calltrap() at nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff809a2997, rsp =3D 0xffffff80003a5fe0, = rbp =3D 0xffffff975cf4aa10 --- unp_gc() at unp_gc+0x167 taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff975cf4abb0, rbp =3D 0 --- db:0:kdb.enter.sysctl> capture off db:0:kdb.enter.sysctl> run lockinfo db:1:lockinfo> show locks No such command db:1:locks> show alllocks No such command db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.sysctl> trace 100058 Tracing pid 0 tid 100058 td 0xfffffe00262fc000 cpustop_handler() at cpustop_handler+0x28 ipi_nmi_handler() at ipi_nmi_handler+0x3d trap() at trap+0x2ea nmi_calltrap() at nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff809a28b1, rsp =3D 0xffffff8000374fe0, = rbp =3D 0xffffff975cf4aa10 --- unp_gc() at unp_gc+0x81 taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff975cf4abb0, rbp =3D 0 --- db:0:kdb.enter.sysctl> capture off db:0:kdb.enter.sysctl> run lockinfo db:1:lockinfo> show locks No such command db:1:locks> show alllocks No such command db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.sysctl> trace 100058 Tracing pid 0 tid 100058 td 0xfffffe00262fc000 cpustop_handler() at cpustop_handler+0x28 ipi_nmi_handler() at ipi_nmi_handler+0x3d trap() at trap+0x2ea nmi_calltrap() at nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff809a28b1, rsp =3D 0xffffff80003b3fe0, = rbp =3D 0xffffff975cf4aa10 --- unp_gc() at unp_gc+0x81 taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff975cf4abb0, rbp =3D 0 --- db:0:kdb.enter.sysctl> capture off [4] db:0:lockedvnods> show pcpu cpuid =3D 0 dynamic pcpu =3D 0x800380 curthread =3D 0xfffffe00264b8000: pid 12 "irq265: ix0:que 0" curpcb =3D 0xffffff9a3ea71bc0 fpcurthread =3D none idlethread =3D 0xfffffe00262bc470: tid 100003 "idle: cpu0" curpmap =3D 0xffffffff812d5af0 tssp =3D 0xffffffff814e0960 commontssp =3D 0xffffffff814e0960 rsp0 =3D 0xffffff9a3ea71bc0 gs32p =3D 0xffffffff814deab8 ldt =3D 0xffffffff814deaf8 tss =3D 0xffffffff814deae8 spin locks held: db:0:pcpu> bt Tracing pid 12 tid 100069 td 0xfffffe00264b8000 kdb_enter() at kdb_enter+0x3b panic() at panic+0x1d1 soabort() at soabort+0x99 syncache_expand() at syncache_expand+0x306 tcp_input() at tcp_input+0x1033 ip_input() at ip_input+0xbd netisr_dispatch_src() at netisr_dispatch_src+0x152 ether_demux() at ether_demux+0x17d ether_nh_input() at ether_nh_input+0x20e netisr_dispatch_src() at netisr_dispatch_src+0x152 ether_demux() at ether_demux+0x86 ether_nh_input() at ether_nh_input+0x20e netisr_dispatch_src() at netisr_dispatch_src+0x152 ixgbe_rxeof() at ixgbe_rxeof+0x1b9 ixgbe_msix_que() at ixgbe_msix_que+0x8d intr_event_execute_handlers() at intr_event_execute_handlers+0x6a ithread_loop() at ithread_loop+0xb4 fork_exit() at fork_exit+0x135 fork_trampoline() at fork_trampoline+0xe [5] FreeBSD XY.hostpoint.net 9.1-RC3 FreeBSD 9.1-RC3 #4 r242695: Wed Nov 7 = 11:33:17 UTC 2012 = root@XY.hostpoint.ch:/usr/obj/usr/src/sys/HOSTPOINT amd64 kernconf: ---- include GENERIC ident HOSTPOINT # ipfw options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=3D5 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_FORWARD options IPDIVERT # ddb for debugging and textdumps options KDB # Enable kernel debugger support. options DDB # Support DDB. # dtrace options KDTRACE_HOOKS # all architectures - enable general = DTrace hooks options DDB_CTF # all architectures - kernel ELF = linker loads CTF data options KDTRACE_FRAME # amd64-only makeoptions DEBUG=3D"-g" makeoptions WITH_CTF=3D1 ---- dmesg boot: ---- Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RC3 #4 r242695: Wed Nov 7 11:33:17 UTC 2012 root@XY.hostpoint.ch:/usr/obj/usr/src/sys/HOSTPOINT amd64 CPU: Intel(R) Xeon(R) CPU E5-2440 0 @ 2.40GHz (2400.05-MHz K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x206d7 Family =3D 6 Model =3D 2d = Stepping =3D 7 = Features=3D0xbfebfbff = Features2=3D0x1fbee3ff AMD Features=3D0x2c100800 AMD Features2=3D0x1 TSC: P-state invariant, performance statistics real memory =3D 103079215104 (98304 MB) avail memory =3D 99335512064 (94733 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs FreeBSD/SMP: 2 package(s) x 6 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 32 cpu13 (AP): APIC ID: 33 cpu14 (AP): APIC ID: 34 cpu15 (AP): APIC ID: 35 cpu16 (AP): APIC ID: 36 cpu17 (AP): APIC ID: 37 cpu18 (AP): APIC ID: 38 cpu19 (AP): APIC ID: 39 cpu20 (AP): APIC ID: 40 cpu21 (AP): APIC ID: 41 cpu22 (AP): APIC ID: 42 cpu23 (AP): APIC ID: 43 Security policy loaded: TrustedBSD MAC/seeotheruids (mac_seeotheruids) ioapic1: Changing APIC ID to 1 ioapic2: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 cpu8: on acpi0 cpu9: on acpi0 cpu10: on acpi0 cpu11: on acpi0 cpu12: on acpi0 cpu13: on acpi0 cpu14: on acpi0 cpu15: on acpi0 cpu16: on acpi0 cpu17: on acpi0 cpu18: on acpi0 cpu19: on acpi0 cpu20: on acpi0 cpu21: on acpi0 cpu22: on acpi0 cpu23: on acpi0 atrtc0: port 0x70-0x7f irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x5f irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Event timer "HPET5" frequency 14318180 Hz quality 440 Event timer "HPET6" frequency 14318180 Hz quality 440 Event timer "HPET7" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 53 at device 1.0 on pci0 pci1: on pcib1 mfi0: port 0xfc00-0xfcff mem = 0xdcffc000-0xdcffffff,0xdcf80000-0xdcfbffff irq 34 at device 0.0 on pci1 mfi0: Using MSI mfi0: Megaraid SAS driver Ver 4.23=20 mfi0: MaxCmd =3D 3f0 MaxSgl =3D 46 state =3D b73c03f0=20 pcib2: irq 53 at device 3.0 on pci0 pci8: on pcib2 ix0: = mem 0xd9000000-0xd91fffff,0xd95f8000-0xd95fbfff irq 52 at device 0.0 on = pci8 ix0: Using MSIX interrupts with 9 vectors ix0: Ethernet address: a0:36:9f:08:cd:4c ix0: PCI Express Bus: Speed 5.0Gb/s Width x8 ix1: = mem 0xd9200000-0xd93fffff,0xd95fc000-0xd95fffff irq 48 at device 0.1 on = pci8 ix1: Using MSIX interrupts with 9 vectors ix1: Ethernet address: a0:36:9f:08:cd:4e ix1: PCI Express Bus: Speed 5.0Gb/s Width x8 pci0: at device 5.0 (no driver attached) pci0: at device 5.2 (no driver attached) pcib3: irq 16 at device 17.0 on pci0 pci9: on pcib3 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) ehci0: mem 0xdf8fd000-0xdf8fd3ff irq = 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib4: at device 28.0 on pci0 pci10: on pcib4 pcib5: irq 16 at device 28.4 on pci0 pci2: on pcib5 bge0: mem = 0xd96a0000-0xd96affff,0xd96b0000-0xd96bffff,0xd96c0000-0xd96cffff irq 16 = at device 0.0 on pci2 bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E bge0: Try again miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: d4:ae:52:a4:3c:de bge1: mem = 0xd96d0000-0xd96dffff,0xd96e0000-0xd96effff,0xd96f0000-0xd96fffff irq 17 = at device 0.1 on pci2 bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E miibus1: on bge1 brgphy1: PHY 2 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge1: Ethernet address: d4:ae:52:a4:3c:df pcib6: irq 19 at device 28.7 on pci0 pci3: on pcib6 pcib7: at device 0.0 on pci3 pci4: on pcib7 pcib8: at device 0.0 on pci4 pci5: on pcib8 pcib9: at device 0.0 on pci5 pci6: on pcib9 vgapci0: mem = 0xd8000000-0xd8ffffff,0xdeffc000-0xdeffffff,0xde000000-0xde7fffff irq 19 = at device 0.0 on pci6 pcib10: at device 1.0 on pci4 pci7: on pcib10 ehci1: mem 0xdf8fe000-0xdf8fe3ff irq = 22 at device 29.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci1 pcib11: at device 30.0 on pci0 pci11: on pcib11 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port = 0xece8-0xecef,0xecf8-0xecfb,0xecf0-0xecf7,0xecfc-0xecff,0xecc0-0xecdf = mem 0xdf8ff000-0xdf8ff7ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 pcib12: on acpi0 pci64: on pcib12 pcib13: irq 85 at device 3.0 on pci64 pci65: on pcib13 pci64: at device 5.0 (no driver attached) pci64: at device 5.2 (no driver attached) pcib14: on acpi0 pci63: on pcib14 pci63: at device 8.0 (no driver attached) pci63: at device 9.0 (no driver attached) pci63: at device 10.0 (no driver attached) pci63: at device 10.1 (no driver attached) pci63: at device 10.2 (no driver attached) pci63: at device 10.3 (no driver attached) pci63: at device 11.0 (no driver attached) pci63: at device 11.3 (no driver attached) pci63: at device 12.0 (no driver attached) pci63: at device 12.1 (no driver attached) pci63: at device 12.2 (no driver attached) pci63: at device 12.6 (no driver attached) pci63: at device 12.7 (no driver attached) pci63: at device 13.0 (no driver attached) pci63: at device 13.1 (no driver attached) pci63: at device 13.2 (no driver attached) pci63: at device 13.6 (no driver attached) pci63: at device 14.0 (no driver attached) pci63: at device 14.1 (no driver attached) pci63: at device 15.0 (no driver attached) pci63: at device 15.1 (no driver attached) pci63: at device 15.2 (no driver attached) pci63: at device 15.3 (no driver attached) pci63: at device 15.4 (no driver attached) pci63: at device 15.5 (no driver attached) pci63: at device 15.6 (no driver attached) pci63: at device 16.0 (no driver attached) pci63: at device 16.1 (no driver attached) pci63: at device 16.2 (no driver attached) pci63: at device 16.3 (no driver attached) pci63: at device 16.5 (no driver attached) pci63: at device 16.6 (no driver attached) pci63: at device 16.7 (no driver attached) pci63: at device 17.0 (no driver attached) pci63: at device 19.0 (no driver attached) pci63: at device 19.1 (no driver attached) pci63: at device 19.4 (no driver attached) pci63: at device 19.5 (no driver attached) pci63: at device 19.6 (no driver attached) pcib15: on acpi0 pci127: on pcib15 pci127: at device 8.0 (no driver attached) pci127: at device 9.0 (no driver attached) pci127: at device 10.0 (no driver attached) pci127: at device 10.1 (no driver attached) pci127: at device 10.2 (no driver attached) pci127: at device 10.3 (no driver attached) pci127: at device 11.0 (no driver attached) pci127: at device 11.3 (no driver attached) pci127: at device 12.0 (no driver attached) pci127: at device 12.1 (no driver attached) pci127: at device 12.2 (no driver attached) pci127: at device 12.6 (no driver attached) pci127: at device 12.7 (no driver attached) pci127: at device 13.0 (no driver attached) pci127: at device 13.1 (no driver attached) pci127: at device 13.2 (no driver attached) pci127: at device 13.6 (no driver attached) pci127: at device 14.0 (no driver attached) pci127: at device 14.1 (no driver attached) pci127: at device 15.0 (no driver attached) pci127: at device 15.1 (no driver attached) pci127: at device 15.2 (no driver attached) pci127: at device 15.3 (no driver attached) pci127: at device 15.4 (no driver attached) pci127: at device 15.5 (no driver attached) pci127: at device 15.6 (no driver attached) pci127: at device 16.0 (no driver attached) pci127: at device 16.1 (no driver attached) pci127: at device 16.2 (no driver attached) pci127: at device 16.3 (no driver attached) pci127: at device 16.5 (no driver attached) pci127: at device 16.6 (no driver attached) pci127: at device 16.7 (no driver attached) pci127: at device 17.0 (no driver attached) pci127: at device 19.0 (no driver attached) pci127: at device 19.1 (no driver attached) pci127: at device 19.4 (no driver attached) pci127: at device 19.5 (no driver attached) pci127: at device 19.6 (no driver attached) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (9600,n,8,1) orm0: at iomem = 0xc0000-0xc7fff,0xcc000-0xccfff,0xec000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 ppc0: cannot reserve I/O port range ctl: CAM Target Layer loaded est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est0 attach returned 6 p4tcc0: on cpu0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est1 attach returned 6 p4tcc1: on cpu1 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est2 attach returned 6 p4tcc2: on cpu2 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est3 attach returned 6 p4tcc3: on cpu3 est4: on cpu4 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est4 attach returned 6 p4tcc4: on cpu4 est5: on cpu5 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est5 attach returned 6 p4tcc5: on cpu5 est6: on cpu6 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est6 attach returned 6 p4tcc6: on cpu6 est7: on cpu7 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est7 attach returned 6 p4tcc7: on cpu7 est8: on cpu8 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est8 attach returned 6 p4tcc8: on cpu8 est9: on cpu9 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est9 attach returned 6 p4tcc9: on cpu9 est10: on cpu10 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est10 attach returned 6 p4tcc10: on cpu10 est11: on cpu11 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est11 attach returned 6 p4tcc11: on cpu11 est12: on cpu12 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est12 attach returned 6 p4tcc12: on cpu12 est13: on cpu13 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est13 attach returned 6 p4tcc13: on cpu13 est14: on cpu14 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est14 attach returned 6 p4tcc14: on cpu14 est15: on cpu15 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est15 attach returned 6 p4tcc15: on cpu15 est16: on cpu16 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est16 attach returned 6 p4tcc16: on cpu16 est17: on cpu17 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est17 attach returned 6 p4tcc17: on cpu17 est18: on cpu18 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est18 attach returned 6 p4tcc18: on cpu18 est19: on cpu19 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est19 attach returned 6 p4tcc19: on cpu19 est20: on cpu20 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est20 attach returned 6 p4tcc20: on cpu20 est21: on cpu21 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est21 attach returned 6 p4tcc21: on cpu21 est22: on cpu22 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est22 attach returned 6 p4tcc22: on cpu22 est23: on cpu23 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 23b500001b00 device_attach: est23 attach returned 6 p4tcc23: on cpu23 ZFS filesystem version 5 ZFS storage pool version 28 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert enabled, nat loadable, rule-based = forwarding enabled, default to accept, logging disabled mfi0: 1828 (406136473s/0x0020/info) - Shutdown command received from = host mfi0: 1829 (boot + 4s/0x0020/info) - Firmware initialization started = (PCI ID 005b/1000/1f38/1028) mfi0: 1830 (boot + 4s/0x0020/info) - Firmware version 3.130.05-1587 mfi0: 1831 (boot + 5s/0x0008/info) - Battery Present mfi0: 1832 (boot + 5s/0x0020/info) - Package version 21.0.2-0001 mfi0: 1833 (boot + 5s/0x0020/info) - Board Revision A00 mfi0: 1834 (boot + 19s/0x0004/info) - Enclosure PD 20(c None/p1) = communication restored mfi0: 1835 (boot + 19s/0x0002/info) - Inserted: Encl PD 20 usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 mfid0 on mfi0 mfid0: 285568MB (584843264 sectors) RAID volume (no label) is optimal mfid1 on mfi0 mfid1: 285568MB (584843264 sectors) RAID volume (no label) is optimal mfi0: 1836 (boot + 19s/0x0002/info) - Inserted: PD 20(c None/p1) Info: = enclPd=3D20, scsiType=3Dd, portMap=3D00, = sasAddr=3D5e4ae020b6ff2c00,0000000000000000 mfi0: 1837 (boot + 19s/0x0002/info) - Inserted: PD 00(e0x20/s0) mfi0: 1838 (boot + 19s/0x0002/info) - Inserted: PD 00(e0x20/s0) Info: = enclPd=3D20, scsiType=3D0, portMap=3D00, = sasAddr=3D5000c50054b863ad,0000000000000000 mfi0: 1839 (boot + 19s/0x0002/info) - Inserted: PD 01(e0x20/s1) mfi0: 1840 (boot + 19s/0x0002/info) - Inserted: PD 01(e0x20/s1) Info: = enclPd=3D20, scsiType=3D0, portMap=3D01, = sasAddr=3D5000c50054b62409,0000000000000000 mfi0: 1841 (406136547s/0x0020/info) - Time established as 11/13/12 = 15:42:27; (53 seconds since power on) mfi0: 1842 (406136564s/0x0008/info) - Battery temperature is normal uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered mfi0: 1843 (406136564s/0x0008/info) - Current capacity of the battery is = above threshold mfi0: 1844 (406136789s/0x0020/info) - Host driver is loaded and = operational ugen0.2: at usbus0 uhub2: = on usbus0 ugen1.2: at usbus1 uhub3: = on usbus1 SMP: AP CPU #1 Launched! SMP: AP CPU #20 Launched! SMP: AP CPU #9 Launched! SMP: AP CPU #15 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #10 Launched! SMP: AP CPU #14 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #23 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #8 Launched! SMP: AP CPU #22 Launched! SMP: AP CPU #17 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #21 Launched! SMP: AP CPU #16 Launched! SMP: AP CPU #12 Launched! SMP: AP CPU #13 Launched! SMP: AP CPU #19 Launched! SMP: AP CPU #11 Launched! SMP: AP CPU #18 Launched! Timecounter "TSC-low" frequency 9375184 Hz quality 1000 Root mount waiting for: usbus1 usbus0 uhub2: 6 ports with 6 removable, self powered uhub3: 8 ports with 8 removable, self powered ugen0.3: at usbus0 uhub4: on usbus0 Root mount waiting for: usbus0 uhub4: 6 ports with 6 removable, self powered ugen0.4: at usbus0 ukbd0: on usbus0 kbd0 at ukbd0 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=3D0 ums1: on usbus0 Root mount waiting for: usbus0 ums1: 3 buttons and [XYZ] coordinates ID=3D0 Root mount waiting for: usbus0 ugen0.5: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 umass0:6:0:-1: Attached to scbus6 cd0 at umass-sim0 bus 0 scbus6 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device=20 cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at umass-sim0 bus 0 scbus6 target 0 lun 1 da0: Removable Direct Access SCSI-0 device=20= da0: 40.000MB/s transfers da0: 524MB (1073741 512 byte sectors: 64H 32S/T 524C) Trying to mount root from zfs:zroot []... ix0: 2 link states coalesced ix1: 2 link states coalesced ix0: 2 link states coalesced ---- network related loader.conf settings: ---- dev.bge.0.msi=3D"0" dev.bge.1.msi=3D"0" net.inet.tcp.syncache.hashsize=3D32768 net.inet.tcp.syncache.bucketlimit=3D32 net.inet.tcp.syncache.cachelimit=3D1048576 net.inet.tcp.tcbhashsize=3D1048576 net.inet.tcp.hostcache.hashsize=3D65536 net.inet.tcp.hostcache.cachelimit=3D1966080 ---- network related part of sysctl.conf: ---- net.inet.ip.fw.verbose=3D0 net.inet.ip.redirect=3D0 net.inet.icmp.drop_redirect=3D1 net.inet.tcp.drop_synfin=3D1 #net.inet.tcp.icmp_may_rst=3D0 #net.inet.udp.blackhole=3D1 #net.inet.tcp.blackhole=3D2 net.inet6.ip6.accept_rtadv=3D0 net.inet6.icmp6.rediraccept=3D0 kern.ipc.maxsockets=3D1000000 net.inet.tcp.maxtcptw=3D200000 kern.ipc.nmbclusters=3D262144 net.inet.tcp.recvspace=3D65536 net.inet.tcp.sendspace=3D65536 kern.ipc.somaxconn=3D10240 net.inet.ip.portrange.first=3D2048 net.inet.ip.portrange.last=3D65535 net.inet.tcp.msl=3D5000 net.inet.tcp.fast_finwait2_recycle=3D1 net.inet.ip.intr_queue_maxlen=3D4096 #net.inet.tcp.ecn.enable=3D1 net.inet.icmp.icmplim=3D5000 ---- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 00:13:52 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F2D7E16 for ; Wed, 14 Nov 2012 00:13:52 +0000 (UTC) (envelope-from takeda@chinatsu.takeda.tk) Received: from chinatsu.takeda.tk (mail.takeda.tk [74.0.89.210]) by mx1.freebsd.org (Postfix) with ESMTP id 236758FC13 for ; Wed, 14 Nov 2012 00:13:51 +0000 (UTC) Received: from chinatsu.takeda.tk (localhost.takeda.tk [127.0.0.1]) by chinatsu.takeda.tk (8.14.5/8.14.5) with ESMTP id qADNme1W061715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 13 Nov 2012 15:48:41 -0800 (PST) (envelope-from takeda@chinatsu.takeda.tk) Received: (from takeda@localhost) by chinatsu.takeda.tk (8.14.5/8.14.5/Submit) id qADNmc1w061714 for freebsd-stable@freebsd.org; Tue, 13 Nov 2012 15:48:38 -0800 (PST) (envelope-from takeda) Date: Tue, 13 Nov 2012 15:48:38 -0800 From: Derek Kulinski To: freebsd-stable@freebsd.org Subject: Problems with ZFS's user quota. Message-ID: <20121113234838.GA60930@chinatsu.takeda.tk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at chinatsu.takeda.tk X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 00:13:52 -0000 Hi everyone, I'm having problem using user quotas in ZFS, I think something is broken, but it very possible that I'm just doing something wrong. I have two problems actually: 1. When trying to define quota for a filesystem that has sub filesystem the zfs userspace behaves weird: [chinatsu]:/tank/system# zfs userspace tank/system TYPE NAME USED QUOTA POSIX User root 9,16K none [chinatsu]:/tank/system# zfs set userquota@takeda=7G tank/system [chinatsu]:/tank/system# zfs userspace tank/system TYPE NAME USED QUOTA POSIX User root 9,16K none POSIX User takeda 7G [chinatsu]:/tank/system# zfs set userquota@takeda=1PB tank/system [chinatsu]:/tank/system# zfs userspace tank/system TYPE NAME USED QUOTA POSIX User root 9,16K none POSIX User takeda 1P [chinatsu]:/tank/system# zfs set userquota@takeda=none tank/system Is it possible to set quota that would also be inherited by subfilesystem? For example if I have 2 filesystems under tank/system I want them to share the quota, so when I set 7GB the total data use would be 7GB max (and not 7GB per filesystem) 2. Setting quota works fine on filesystem that has files by given users, but does not seem to be enforced (I enabled quota in the kenrel even though I don't belive it is ecessary). [chinatsu]:/tank/system# zfs userspace tank/system/home TYPE NAME USED QUOTA [...] POSIX User takeda 6,06G none [...] POSIX User www 1,34G none [chinatsu]:/tank/system# zfs set userquota@takeda=7G tank/system/home [chinatsu]:/tank/system# zfs userspace tank/system/home TYPE NAME USED QUOTA [...] POSIX User takeda 6,06G 7G [...] POSIX User www 1,34G none [chinatsu]:/tank/system# sudo su - takeda chinatsu :: ~ » dd if=/dev/zero of=bigfile bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 7.882992 secs (136209934 bytes/sec) chinatsu :: ~ » [chinatsu]:/tank/system# zfs userspace tank/system/home TYPE NAME USED QUOTA [...] POSIX User takeda 7,06G 7G [...] POSIX User www 1,34G none [chinatsu]:/tank/system# It looks like ZFS does not allow me set quota in fractions (for example 6.5GB, but I guess that's not that big of a deal). Thank you, Derek From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 00:41:06 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FB8096B for ; Wed, 14 Nov 2012 00:41:06 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) by mx1.freebsd.org (Postfix) with ESMTP id 231AB8FC12 for ; Wed, 14 Nov 2012 00:41:05 +0000 (UTC) Received: from 46-127-111-189.dynamic.hispeed.ch ([46.127.111.189]:55400 helo=[172.16.1.20]) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TYR20-0005Rb-Is for freebsd-stable@freebsd.org; Wed, 14 Nov 2012 01:40:40 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Markus Gebert In-Reply-To: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> Date: Wed, 14 Nov 2012 01:41:04 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> To: freebsd-stable X-Mailer: Apple Mail (2.1499) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 00:41:06 -0000 On 13.11.2012, at 19:30, Markus Gebert = wrote: > To me it looks like the unix socket GC is triggered way too often = and/or running too long, which uses cpu and worse, causes a lot of = contention around the unp_list_lock which in turn causes delays for all = processes relaying on unix sockets for IPC. >=20 > I don't know why the unp_gc() is called so often and what's triggering = this. I have a guess now. Dovecot and relayd both use unix sockets heavily. = According to dtrace uipc_detach() gets called quite often by dovecot = closing unix sockets. Each time uipc_detach() is called unp_gc_task is = taskqueue_enqueue()d if fds are inflight. in uipc_detach(): 682 if (local_unp_rights)=09 683 taskqueue_enqueue(taskqueue_thread, = &unp_gc_task); We use relayd in a way that keeps the source address of the client when = connecting to the backend server (transparent load balancing). This = requires IP_BINDANY on the socket which cannot be set by unprivileged = processes, so relayd sends the socket fd to the parent process just to = set the socket option and send it back. This means an fd gets = transferred twice for every new backend connection. So we have dovecot calling uipc_detach() often and relayd making it = likely that fds are inflight (unp_rights > 0). With a certain amount of = load this could cause unp_gc_task to be added to the thread taskq too = often, slowing everything unix socket related down by holding global = locks in unp_gc(). I don't know if the slowdown can even cause a negative feedback loop at = some point by inreasing the chance of fds being inflight. This would = explain why sometimes the condition goes away by itself and sometimes = requires intervention (taking load away for a moment). I'll look into a way to (dis)prove all this tomorrow. Ideas still = welcome :-). Markus From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 01:12:45 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AAB45455 for ; Wed, 14 Nov 2012 01:12:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7708D8FC08 for ; Wed, 14 Nov 2012 01:12:45 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so797886pbc.13 for ; Tue, 13 Nov 2012 17:12:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mEIQrGlSu/cqPlVWZGIXkdfXp58h3Al2JonbvilAmU0=; b=q6bIC1Uhy67Lt/zfv6OBW55+Pc9runc316oCQ5u6OLAZ4pyxcHF2jWm1bnpA4VT/3w UzycKVoxwargAG/pkn0+slkPOm8Jx9gV/Z0fEqPpt+mlr++neZuXAvFeX2aYWJbIIsEi A+/TeXBxkSU6b5SiC+kOChADxIKXiDTOtpprQ4/QLLxhtxZhjVfpbI+9hIBRB+K7RPZg F8rMTMKS4ZSolNXiw6cuIMKpeEEMp31psuKb6fbeU/XLcq+htpNs7BVs+8gyMOpgiJF5 Vnr4PpqjuxiV7c8QKybA/OZCpVKykkz6sntI3x6rrnFVy3pTvbMUw8dabDvP+upU0P4P W6Vg== MIME-Version: 1.0 Received: by 10.68.209.166 with SMTP id mn6mr45085829pbc.95.1352855564876; Tue, 13 Nov 2012 17:12:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Tue, 13 Nov 2012 17:12:44 -0800 (PST) In-Reply-To: <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> Date: Tue, 13 Nov 2012 17:12:44 -0800 X-Google-Sender-Auth: ErqwiNyiZ8lGq8lr74WU3HKc2V4 Message-ID: Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Adrian Chadd To: Markus Gebert Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 01:12:45 -0000 Oh lordie, just hack the kernel to make IP_BINDANY usable by any uid, not just root. I was hoping that capabilitiies would actually be useful these days, but apparently not. :( Then you can stop this FD exchange nonsense and this problem should go away= . :) Adrian On 13 November 2012 16:41, Markus Gebert wrote= : > > On 13.11.2012, at 19:30, Markus Gebert wrote= : > >> To me it looks like the unix socket GC is triggered way too often and/or= running too long, which uses cpu and worse, causes a lot of contention aro= und the unp_list_lock which in turn causes delays for all processes relayin= g on unix sockets for IPC. >> >> I don't know why the unp_gc() is called so often and what's triggering t= his. > > I have a guess now. Dovecot and relayd both use unix sockets heavily. Acc= ording to dtrace uipc_detach() gets called quite often by dovecot closing u= nix sockets. Each time uipc_detach() is called unp_gc_task is taskqueue_enq= ueue()d if fds are inflight. > > in uipc_detach(): > 682 if (local_unp_rights) > 683 taskqueue_enqueue(taskqueue_thread, &unp_gc_task)= ; > > We use relayd in a way that keeps the source address of the client when c= onnecting to the backend server (transparent load balancing). This requires= IP_BINDANY on the socket which cannot be set by unprivileged processes, so= relayd sends the socket fd to the parent process just to set the socket op= tion and send it back. This means an fd gets transferred twice for every ne= w backend connection. > > So we have dovecot calling uipc_detach() often and relayd making it likel= y that fds are inflight (unp_rights > 0). With a certain amount of load thi= s could cause unp_gc_task to be added to the thread taskq too often, slowin= g everything unix socket related down by holding global locks in unp_gc(). > > I don't know if the slowdown can even cause a negative feedback loop at s= ome point by inreasing the chance of fds being inflight. This would explain= why sometimes the condition goes away by itself and sometimes requires int= ervention (taking load away for a moment). > > I'll look into a way to (dis)prove all this tomorrow. Ideas still welcome= :-). > > > Markus > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 03:05:56 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B09A2D4A for ; Wed, 14 Nov 2012 03:05:56 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 589538FC08 for ; Wed, 14 Nov 2012 03:05:55 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so10669416vba.13 for ; Tue, 13 Nov 2012 19:05:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=R/R3fJDqt0H/fiwtjjESntFuVfn4Nj0xZhUNnztzSto=; b=pvONBgDcroTgjphKLg1LnbY2BRcoEwUNqk/DuRECRHO8OuJ8vYcQ+XXX/ET4tX/BVz KX0BD36iRNUEQmfHdPjTNaW3beoEf8ivQCXUVs83HNMQhkTaHgaf9mtMFgHUePDCqsaA ovcnfYSWQf1twjCol1OKPs6ASKBu184pKGDWvjG+4tUIkaXKv8bbBeF8u6ZtoWTg0AnT VHqF9YhNvU+kj+lQUCqM9WmstdqH2f69d5sZwZWIqN6ZuJig9Yc15nKrHYSty0Qrtng8 6ragWNfi5N7V6gjxhlAnEKzawYfiGPH+pag3s2A1SFGdUsKvXy32zDa5cS6s7/DPKcvq +sqA== MIME-Version: 1.0 Received: by 10.52.100.65 with SMTP id ew1mr4531946vdb.125.1352862355187; Tue, 13 Nov 2012 19:05:55 -0800 (PST) Received: by 10.58.178.234 with HTTP; Tue, 13 Nov 2012 19:05:55 -0800 (PST) Date: Wed, 14 Nov 2012 11:05:55 +0800 Message-ID: Subject: Compilation error while compiling FreeBSD9-STABLE with Clang From: Alie Tan To: freebsd-stable@freebsd.org X-Gm-Message-State: ALoCoQmE0+zs10g5MrBdd89WNREBU/KeSDUNNuC0ru1eiYw1IoAXmcO3iJ0Ua6DcW9KkWXVrAoLc Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 03:05:56 -0000 Hi. I got compilation error while compiling FreeBSD9-STABLE with Clang: -m32 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 -5 bytes available *** [boot2] Error code 1 And here is my src.conf CFLAGS+= -O3 -fno-strict-aliasing -pipe -funroll-loops CXXFLAGS+= -O3 -fno-strict-aliasing -pipe -funroll-loops COPTFLAGS+= -O3 -pipe -ffast-math -funroll-loops CC=clang CXX=clang++ CPP=clang-cpp WITH_CLANG="YES" WITH_CLANG_EXTRAS="YES" WITH_CLANG_IS_CC="YES" From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 03:29:50 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41EAF143 for ; Wed, 14 Nov 2012 03:29:50 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 22FFD8FC1B for ; Wed, 14 Nov 2012 03:29:49 +0000 (UTC) Received: from kruse-124.4.ixsystems.com (drawbridge.ixsystems.com [206.40.55.65]) by elvis.mu.org (Postfix) with ESMTPSA id 892A41A3C1D; Tue, 13 Nov 2012 19:29:49 -0800 (PST) Message-ID: <50A3104E.5000107@mu.org> Date: Tue, 13 Nov 2012 19:30:22 -0800 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Markus Gebert Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> In-Reply-To: <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 03:29:50 -0000 On 11/13/12 4:41 PM, Markus Gebert wrote: > On 13.11.2012, at 19:30, Markus Gebert wrote: > >> To me it looks like the unix socket GC is triggered way too often and/or running too long, which uses cpu and worse, causes a lot of contention around the unp_list_lock which in turn causes delays for all processes relaying on unix sockets for IPC. >> >> I don't know why the unp_gc() is called so often and what's triggering this. > I have a guess now. Dovecot and relayd both use unix sockets heavily. According to dtrace uipc_detach() gets called quite often by dovecot closing unix sockets. Each time uipc_detach() is called unp_gc_task is taskqueue_enqueue()d if fds are inflight. > > in uipc_detach(): > 682 if (local_unp_rights) > 683 taskqueue_enqueue(taskqueue_thread, &unp_gc_task); > > We use relayd in a way that keeps the source address of the client when connecting to the backend server (transparent load balancing). This requires IP_BINDANY on the socket which cannot be set by unprivileged processes, so relayd sends the socket fd to the parent process just to set the socket option and send it back. This means an fd gets transferred twice for every new backend connection. > > So we have dovecot calling uipc_detach() often and relayd making it likely that fds are inflight (unp_rights > 0). With a certain amount of load this could cause unp_gc_task to be added to the thread taskq too often, slowing everything unix socket related down by holding global locks in unp_gc(). > > I don't know if the slowdown can even cause a negative feedback loop at some point by inreasing the chance of fds being inflight. This would explain why sometimes the condition goes away by itself and sometimes requires intervention (taking load away for a moment). > > I'll look into a way to (dis)prove all this tomorrow. Ideas still welcome :-). A couple of ideas: 1) convert the taskqueue to a callout, but only allow one to be queued at a time. set the granularity. 2) I think you only need to actually run garbage collection on the off-chance that you pass unix file descriptors, otherwise you can get away with refcounting. It's hard for me to express the exact logic needed for this though. I think you would need some way to simply do refcounting until there was a unix socket descriptor in flight, then switch to gc. Either that or make a sysctl that allows you administratively deny passing of unix descriptors and just use refcounting. Or just use Adrian's hack. :) -Alfred From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 07:21:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 32D703D4 for ; Wed, 14 Nov 2012 07:21:20 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7E7A68FC15 for ; Wed, 14 Nov 2012 07:21:19 +0000 (UTC) Received: from tom.home (localhost [127.0.0.1]) by kib.kiev.ua (8.14.5/8.14.5) with ESMTP id qAE7LCNS069255; Wed, 14 Nov 2012 09:21:12 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.1 kib.kiev.ua qAE7LCNS069255 Received: (from kostik@localhost) by tom.home (8.14.5/8.14.5/Submit) id qAE7LC4S069254; Wed, 14 Nov 2012 09:21:12 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 14 Nov 2012 09:21:12 +0200 From: Konstantin Belousov To: Markus Gebert Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC Message-ID: <20121114072112.GX73505@kib.kiev.ua> References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LLz+487bO+3TjNAZ" Content-Disposition: inline In-Reply-To: <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=0.2 required=5.0 tests=ALL_TRUSTED, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 07:21:20 -0000 --LLz+487bO+3TjNAZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 14, 2012 at 01:41:04AM +0100, Markus Gebert wrote: >=20 > On 13.11.2012, at 19:30, Markus Gebert wrote: >=20 > > To me it looks like the unix socket GC is triggered way too often and/o= r running too long, which uses cpu and worse, causes a lot of contention ar= ound the unp_list_lock which in turn causes delays for all processes relayi= ng on unix sockets for IPC. > >=20 > > I don't know why the unp_gc() is called so often and what's triggering = this. >=20 > I have a guess now. Dovecot and relayd both use unix sockets heavily. Acc= ording to dtrace uipc_detach() gets called quite often by dovecot closing u= nix sockets. Each time uipc_detach() is called unp_gc_task is taskqueue_enq= ueue()d if fds are inflight. >=20 > in uipc_detach(): > 682 if (local_unp_rights)=09 > 683 taskqueue_enqueue(taskqueue_thread, &unp_gc_task); >=20 > We use relayd in a way that keeps the source address of the client when c= onnecting to the backend server (transparent load balancing). This requires= IP_BINDANY on the socket which cannot be set by unprivileged processes, so= relayd sends the socket fd to the parent process just to set the socket op= tion and send it back. This means an fd gets transferred twice for every ne= w backend connection. >=20 > So we have dovecot calling uipc_detach() often and relayd making it likel= y that fds are inflight (unp_rights > 0). With a certain amount of load thi= s could cause unp_gc_task to be added to the thread taskq too often, slowin= g everything unix socket related down by holding global locks in unp_gc(). >=20 > I don't know if the slowdown can even cause a negative feedback loop at s= ome point by inreasing the chance of fds being inflight. This would explain= why sometimes the condition goes away by itself and sometimes requires int= ervention (taking load away for a moment). >=20 > I'll look into a way to (dis)prove all this tomorrow. Ideas still welcome= :-). >=20 If the only issue is indeed too aggressive scheduling of the taskqueue, than the postpone up to the next tick could do it. The patch below tries to schedule the taskqueue for gc to the next tick if it is not yet scheduled. Could you try it ? diff --git a/sys/kern/subr_taskqueue.c b/sys/kern/subr_taskqueue.c index 90c6ffc..3bf62f9 100644 --- a/sys/kern/subr_taskqueue.c +++ b/sys/kern/subr_taskqueue.c @@ -252,9 +252,13 @@ taskqueue_enqueue_timeout(struct taskqueue *queue, } else { queue->tq_callouts++; timeout_task->f |=3D DT_CALLOUT_ARMED; + if (ticks < 0) + ticks =3D -ticks; /* Ignore overflow. */ + } + if (ticks > 0) { + callout_reset(&timeout_task->c, ticks, + taskqueue_timeout_func, timeout_task); } - callout_reset(&timeout_task->c, ticks, taskqueue_timeout_func, - timeout_task); } TQ_UNLOCK(queue); return (res); diff --git a/sys/kern/uipc_usrreq.c b/sys/kern/uipc_usrreq.c index cc5360f..ed92e90 100644 --- a/sys/kern/uipc_usrreq.c +++ b/sys/kern/uipc_usrreq.c @@ -131,7 +131,7 @@ static const struct sockaddr sun_noname =3D { sizeof(su= n_noname), AF_LOCAL }; * reentrance in the UNIX domain socket, file descriptor, and socket layer * code. See unp_gc() for a full description. */ -static struct task unp_gc_task; +static struct timeout_task unp_gc_task; =20 /* * The close of unix domain sockets attached as SCM_RIGHTS is @@ -672,7 +672,7 @@ uipc_detach(struct socket *so) if (vp) vrele(vp); if (local_unp_rights) - taskqueue_enqueue(taskqueue_thread, &unp_gc_task); + taskqueue_enqueue_timeout(taskqueue_thread, &unp_gc_task, -1); } =20 static int @@ -1783,7 +1783,7 @@ unp_init(void) LIST_INIT(&unp_shead); LIST_INIT(&unp_sphead); SLIST_INIT(&unp_defers); - TASK_INIT(&unp_gc_task, 0, unp_gc, NULL); + TIMEOUT_TASK_INIT(taskqueue_thread, &unp_gc_task, 0, unp_gc, NULL); TASK_INIT(&unp_defer_task, 0, unp_process_defers, NULL); UNP_LINK_LOCK_INIT(); UNP_LIST_LOCK_INIT(); --LLz+487bO+3TjNAZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCjRmgACgkQC3+MBN1Mb4jZYACeLpu6b0BiuRrYrvQGlFq+BRbc LMYAoJN1cEvxgy3CJHhrfxdjAtiVfM1m =ADPc -----END PGP SIGNATURE----- --LLz+487bO+3TjNAZ-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 10:31:16 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA2473C2 for ; Wed, 14 Nov 2012 10:31:16 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 193A28FC08 for ; Wed, 14 Nov 2012 10:31:15 +0000 (UTC) Received: (qmail 30477 invoked from network); 14 Nov 2012 12:05:17 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 14 Nov 2012 12:05:17 -0000 Message-ID: <50A372EC.5080002@freebsd.org> Date: Wed, 14 Nov 2012 11:31:08 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Looking for bge(4) , bce(4) and igb(4) cards Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: andre@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 10:31:16 -0000 Hello I currently working on a number of drivers for popular network cards and extend them with automatic hybrid interrupt/polling ithread processing with life-lock prevention (so that the driver can't consume all CPU when under heavy load or attack). To properly test this I need the proper hardware as PCIe network cards: bge(4) Broadcom BCM57xx/BCM590x bce(4) Broadcom NetXtreme II (BCM5706/5708/5709/5716) igb(4) Intel PRO/1000 i82575, i82576, i82580, i210, i350 If you have one of these and can spare it I'd be very glad if you could send it to me. I'm located in Switzerland/Europe. I can reply to you privately to give you my shipping address. Of course if you have any other PCIe Gigabit Ethernet cards with a driver in FreeBSD I'm interested in receiving one as well. Of particular interest are: em(4) Intel i82571 to i82573 lem(4) Intel i82540 to i82546 age(4) Atheros L1 GigE ??? anything else 1GigE with PCIe The same goes for 10 Gigabit Ethernet but the setup is a bit more involved and I haven't done that yet, but will do soon (the issue being expensive SPF+ optics): bxe(4) Broadcom BCM5771x 10GigE cxbge(4) Chelsio T4 10GigE ixgbe(4) Intel i82598 and i82599 10GigE mxge(4) Myricom Myri10G qlxgb(4) QLogic 3200 and 8200 10GigE sfxge(4) Solarflare Many thanks for your support! -- Andre From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 10:39:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D575A78; Wed, 14 Nov 2012 10:39:38 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB3B8FC18; Wed, 14 Nov 2012 10:39:37 +0000 (UTC) Received: from [2001:1620:2013:1:e8ec:d52:8672:17b] (port=51430) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TYaND-000NWs-Hb; Wed, 14 Nov 2012 11:39:11 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Markus Gebert In-Reply-To: Date: Wed, 14 Nov 2012 11:39:00 +0100 Message-Id: References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> To: Adrian Chadd X-Mailer: Apple Mail (2.1499) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 10:39:38 -0000 On 14.11.2012, at 02:12, Adrian Chadd wrote: > Oh lordie, just hack the kernel to make IP_BINDANY usable by any uid, > not just root. >=20 > I was hoping that capabilitiies would actually be useful these days, > but apparently not. :( >=20 > Then you can stop this FD exchange nonsense and this problem should go = away. :) Thanks for the suggestion, I'll probably do that regardless of a fix to = the unp_gc problem, because it's indeed unnecessary overhead in our = scenario. Still that's a workaround you most probably don't want if you = have untrusted users on the system or you end up hacking in something = comparable to security.mac.seeotheruids.specificgid. Markus From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 10:43:26 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 55751BD3 for ; Wed, 14 Nov 2012 10:43:26 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) by mx1.freebsd.org (Postfix) with ESMTP id D8CEF8FC13 for ; Wed, 14 Nov 2012 10:43:25 +0000 (UTC) Received: from [2001:1620:2013:1:e8ec:d52:8672:17b] (port=51439) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TYaQs-000OV6-OT; Wed, 14 Nov 2012 11:42:58 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Markus Gebert In-Reply-To: <50A3104E.5000107@mu.org> Date: Wed, 14 Nov 2012 11:42:48 +0100 Message-Id: <4DDA6862-6BE5-4EF4-B6B5-141DD9123C36@hostpoint.ch> References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> <50A3104E.5000107@mu.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.1499) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 10:43:26 -0000 On 14.11.2012, at 04:30, Alfred Perlstein wrote: > A couple of ideas: Thanks. > 1) convert the taskqueue to a callout, but only allow one to be queued = at a time. set the granularity. I think Konstantin's patch is going in this direction. > 2) I think you only need to actually run garbage collection on the = off-chance that you pass unix file descriptors, otherwise you can get = away with refcounting. Hm, isn't that whats done currently? gc is only scheduled if fds are = inflight while uipc_detach() is called. > It's hard for me to express the exact logic needed for this though. = I think you would need some way to simply do refcounting until there was = a unix socket descriptor in flight, then switch to gc. Either that or = make a sysctl that allows you administratively deny passing of unix = descriptors and just use refcounting. Markus From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 10:51:16 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4BE01F19 for ; Wed, 14 Nov 2012 10:51:16 +0000 (UTC) (envelope-from markus.gebert@hostpoint.ch) Received: from mail.adm.hostpoint.ch (mail.adm.hostpoint.ch [IPv6:2a00:d70:0:a::e0]) by mx1.freebsd.org (Postfix) with ESMTP id BAB458FC0C for ; Wed, 14 Nov 2012 10:51:15 +0000 (UTC) Received: from [2001:1620:2013:1:e8ec:d52:8672:17b] (port=51457) by mail.adm.hostpoint.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TYaYU-000PaD-2o; Wed, 14 Nov 2012 11:50:50 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Markus Gebert In-Reply-To: <20121114072112.GX73505@kib.kiev.ua> Date: Wed, 14 Nov 2012 11:50:39 +0100 Message-Id: <6F156867-5334-489E-AC92-BD385B0DBC2F@hostpoint.ch> References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> <20121114072112.GX73505@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1499) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 10:51:16 -0000 On 14.11.2012, at 08:21, Konstantin Belousov = wrote: > On Wed, Nov 14, 2012 at 01:41:04AM +0100, Markus Gebert wrote: >>=20 >> On 13.11.2012, at 19:30, Markus Gebert = wrote: >>=20 >>> To me it looks like the unix socket GC is triggered way too often = and/or running too long, which uses cpu and worse, causes a lot of = contention around the unp_list_lock which in turn causes delays for all = processes relaying on unix sockets for IPC. >>>=20 >>> I don't know why the unp_gc() is called so often and what's = triggering this. >>=20 >> I have a guess now. Dovecot and relayd both use unix sockets heavily. = According to dtrace uipc_detach() gets called quite often by dovecot = closing unix sockets. Each time uipc_detach() is called unp_gc_task is = taskqueue_enqueue()d if fds are inflight. >>=20 >> in uipc_detach(): >> 682 if (local_unp_rights)=09 >> 683 taskqueue_enqueue(taskqueue_thread, = &unp_gc_task); >>=20 >> We use relayd in a way that keeps the source address of the client = when connecting to the backend server (transparent load balancing). This = requires IP_BINDANY on the socket which cannot be set by unprivileged = processes, so relayd sends the socket fd to the parent process just to = set the socket option and send it back. This means an fd gets = transferred twice for every new backend connection. >>=20 >> So we have dovecot calling uipc_detach() often and relayd making it = likely that fds are inflight (unp_rights > 0). With a certain amount of = load this could cause unp_gc_task to be added to the thread taskq too = often, slowing everything unix socket related down by holding global = locks in unp_gc(). >>=20 >> I don't know if the slowdown can even cause a negative feedback loop = at some point by inreasing the chance of fds being inflight. This would = explain why sometimes the condition goes away by itself and sometimes = requires intervention (taking load away for a moment). >>=20 >> I'll look into a way to (dis)prove all this tomorrow. Ideas still = welcome :-). >>=20 >=20 > If the only issue is indeed too aggressive scheduling of the = taskqueue, > than the postpone up to the next tick could do it. The patch below > tries to schedule the taskqueue for gc to the next tick if it is not = yet > scheduled. Could you try it ? Sounds like a good idea, thanks! I'm testing the patch right now. It = could take a few days to know it works for sure. I'll get back to you = soon. Markus From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 11:41:55 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DAD0A431 for ; Wed, 14 Nov 2012 11:41:55 +0000 (UTC) (envelope-from paulo@nlink.com.br) Received: from nlink.com.br (smtp.nlink.com.br [187.87.132.3]) by mx1.freebsd.org (Postfix) with SMTP id EFB628FC08 for ; Wed, 14 Nov 2012 11:41:54 +0000 (UTC) Received: (qmail 87147 invoked from network); 14 Nov 2012 08:35:11 -0300 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=nlink.com.br; b=MN4OmNQ2Z0HzvnwlT0hvyW8m18GX4Yfd1qORfFh7iqBUHxMxjlV88y3Y0GicxQI258DOtpL6X33uvdTwF85KVvV3B/UYJs51Yv08kOFrdijCQpkkHc6+SQIF8M7M0I5R ; Received: from unknown (HELO ?192.168.2.100?) (paulo@nlink.com.br@201.12.60.146) by smtp.nlink.com.br with SMTP; 14 Nov 2012 08:35:11 -0300 Message-ID: <50A381FC.9090809@nlink.com.br> Date: Wed, 14 Nov 2012 08:35:24 -0300 From: Paulo Fragoso User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121027 Icedove/3.0.11 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 9.1-PRERELEASE jail_sysvipc_allow Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 11:41:55 -0000 I've instaled FreeBSD 9 for hosts some jails and setting jail_sysvipc_allow="YES" in host rc.conf, why is security.jail.sysvipc_allowed false in jail? -- BSDCG: BSDA - Digium: dCAP Electrical/Eletronic Engineer http://www.nlink.com.br +55 81 2121-6666 Cel:81 9727-6666 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 11:50:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B76B5DF for ; Wed, 14 Nov 2012 11:50:54 +0000 (UTC) (envelope-from twigcass@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id 721188FC0C for ; Wed, 14 Nov 2012 11:50:53 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from 173.179.175.194 ([173.179.175.194]) by VL-VM-MR006.ip.videotron.ca (Oracle Communications Messaging Exchange Server 7u4-22.01 64bit (built Apr 21 2011)) with ESMTP id <0MDH006WN4SLKN01@VL-VM-MR006.ip.videotron.ca> for freebsd-stable@freebsd.org; Wed, 14 Nov 2012 05:50:47 -0500 (EST) Date: Wed, 14 Nov 2012 05:52:01 -0500 From: hugues Levesque To: freebsd-stable@freebsd.org Subject: to unsubscribe Message-id: <20121114055201.261e10d7@173.179.175.194> Organization: bhug X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; i386-portbld-freebsd9.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 11:50:54 -0000 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 12:35:23 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 74040481 for ; Wed, 14 Nov 2012 12:35:23 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 495F48FC13 for ; Wed, 14 Nov 2012 12:35:22 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id qAECZMfF023578; Wed, 14 Nov 2012 04:35:22 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id qAECZMtq023577; Wed, 14 Nov 2012 04:35:22 -0800 (PST) (envelope-from david) Date: Wed, 14 Nov 2012 04:35:22 -0800 From: David Wolfskill To: hugues Levesque Subject: Re: to unsubscribe Message-ID: <20121114123522.GG17755@albert.catwhisker.org> References: <20121114055201.261e10d7@173.179.175.194> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zrag5V6pnZGjLKiw" Content-Disposition: inline In-Reply-To: <20121114055201.261e10d7@173.179.175.194> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 12:35:23 -0000 --Zrag5V6pnZGjLKiw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 14, 2012 at 05:52:01AM -0500, hugues Levesque wrote: >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Another way is to direct a Web browser to to subscribe, change your subscription options, or unsubscribe. Peace, david (current hat: part of postmaster@freebsd.org) --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Zrag5V6pnZGjLKiw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCjkAkACgkQmprOCmdXAD0l4gCfXVk2/uGcZI7gMR0Mynn/5oHY 474AniO21ov4ZWxTJcE0L5z9n7KzMHM1 =YuIo -----END PGP SIGNATURE----- --Zrag5V6pnZGjLKiw-- From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 12:38:22 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 813255D1 for ; Wed, 14 Nov 2012 12:38:22 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3895D8FC0C for ; Wed, 14 Nov 2012 12:38:22 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6] (unknown [IPv6:2001:7b8:3a7:0:89d9:d735:1f7a:92e6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 03D585C59; Wed, 14 Nov 2012 13:38:20 +0100 (CET) Message-ID: <50A390BE.1090702@FreeBSD.org> Date: Wed, 14 Nov 2012 13:38:22 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Alie Tan Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 12:38:22 -0000 On 2012-11-14 04:05, Alie Tan wrote: > I got compilation error while compiling FreeBSD9-STABLE with Clang: > -m32 -c /usr/src/sys/boot/i386/boot2/sio.S > clang: warning: the clang compiler does not support '-fno-unit-at-a-time' > ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o > boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o > sio.o > objcopy -S -O binary boot2.out boot2.bin > btxld -v -E 0x2000 -f bin -b > /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > boot2.ld -P 1 boot2.bin > kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 > client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 > output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 > -5 bytes available > *** [boot2] Error code 1 Please update your source tree to at least r242907. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 14:02:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B628110 for ; Wed, 14 Nov 2012 14:02:14 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 12FA18FC0C for ; Wed, 14 Nov 2012 14:02:13 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so568071vba.13 for ; Wed, 14 Nov 2012 06:02:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=aclwJ/6vnpt7+hs+pWKKXCn9i+LmaNbS3IOBylqHnmM=; b=nPeb/e4AFeHPkbkyH9uXNng8oxeO5FmHctlbwxoxA83P8m6WQ4xQcjQ3BDZz7UB90L HBHdLewpE6d1ApmgsmCSeW6WJk9qrnN7Sd3f3TztEuaRyidvdix8Lqy799jc4eq1UJL0 dM2oTONP9LV+YLDSwVuRGfLfP2QxO2wzCG/+coSavpkpxcZ4WAvVGG1Slgf5aLS+mYRx W/A+6//FFSwweEf9zETkwzcX6U9w15wFCePAtOVuj64T4K4q9D2zj6JcZbjDe4k+pGpG pTuhgSBxuiI2SFAY1f47AFKRzTEKVpZ92qXVL5vAqquVqw1sf/hHEYSxfjOTXOQ502+r cIPw== MIME-Version: 1.0 Received: by 10.220.16.4 with SMTP id m4mr11013781vca.43.1352901733333; Wed, 14 Nov 2012 06:02:13 -0800 (PST) Received: by 10.58.178.234 with HTTP; Wed, 14 Nov 2012 06:02:12 -0800 (PST) In-Reply-To: <50A390BE.1090702@FreeBSD.org> References: <50A390BE.1090702@FreeBSD.org> Date: Wed, 14 Nov 2012 22:02:12 +0800 Message-ID: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang From: Alie Tan To: Dimitry Andric X-Gm-Message-State: ALoCoQm/5E1mRVNzlCwLFf2KkB+CWFdJwGaNwDpFE6MCHFkDkNGu4nlXLOLwutis7nFCdZXp0GHB Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 14:02:14 -0000 Hi Mine is already the latest. I slready synched my src today. Seems r242907 only for i386? Cmiiw. Regards, Alie T On Wednesday, November 14, 2012, Dimitry Andric wrote: > On 2012-11-14 04:05, Alie Tan wrote: >> >> I got compilation error while compiling FreeBSD9-STABLE with Clang: >> -m32 -c /usr/src/sys/boot/i386/boot2/sio.S >> clang: warning: the clang compiler does not support '-fno-unit-at-a-time' >> ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o >> boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o >> sio.o >> objcopy -S -O binary boot2.out boot2.bin >> btxld -v -E 0x2000 -f bin -b >> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >> boot2.ld -P 1 boot2.bin >> kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 >> client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 >> output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 >> -5 bytes available >> *** [boot2] Error code 1 > > Please update your source tree to at least r242907. > From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 14:30:21 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FC265F7 for ; Wed, 14 Nov 2012 14:30:21 +0000 (UTC) (envelope-from axelbsd@ymail.com) Received: from nm18.bullet.mail.ukl.yahoo.com (nm18.bullet.mail.ukl.yahoo.com [217.146.183.192]) by mx1.freebsd.org (Postfix) with ESMTP id E9C4C8FC12 for ; Wed, 14 Nov 2012 14:30:20 +0000 (UTC) Received: from [217.12.10.89] by nm18.bullet.mail.ukl.yahoo.com with NNFMP; 14 Nov 2012 14:30:18 -0000 Received: from [77.238.184.73] by tm19.bullet.mail.ukl.yahoo.com with NNFMP; 14 Nov 2012 14:30:18 -0000 Received: from [127.0.0.1] by smtp142.mail.ukl.yahoo.com with NNFMP; 14 Nov 2012 14:30:18 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1352903418; bh=/U0txds6KdwTPc6yXBcMbyE1c9ocIowOmRfFGNWdbbQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:Received:MIME-Version:Received:In-Reply-To:References:From:Date:Message-ID:Subject:To:Cc:Content-Type; b=faV3EPEsb6kSJwCt9hOJVKFcLSMeXQzebYuusVokUhlKaxXhiex6x+Ica3kq9w/2FKZPN266tllQiKmRY2DMq7ZI/xGviUt7Uvy3O7ICiUjS2AbEw6uGHIz+Mtp7ilzZ0LhY0HuOhfRkXJnfi7ebD7GsE3dO9cUlIyx/QodMA/Y= X-Yahoo-Newman-Id: 379586.51604.bm@smtp142.mail.ukl.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: cNd4UsUVM1mhUTkel0XaXl3iZRHImfV5CVsNVvEH8N.t9pR 5lZSogM_D2wETkXzFohsG2_PUKV.R5D6UOGzVQXKDC4Cvz2PUw81uVTPxPWp JR9djRyow5n0gdxpvQXZqGavo8Tm2zAoZjiNJnfOATl.87Ff.gHeY1_o9Mvm djhguWwUCjXbSXi6tA03v.5zku7fXor7Ady5p5dMbk0KoWfQJsGQqPcCognw prXjskRL3HvZns_pjL1uuczRkJSZ7ZKSNskTSK82WcBAdWdwkbwddjXNRn44 _OdoG5bi2cwNRAc8JFYl7dSYkkUNZuTFzjy0ldPS1rEkfznB3wCYDk6OCwPi bcIEWo8BhTGNsLqeNh31xchqTv92SoEygnpxvjUOTKa1TN_ztt4P7f4nvMFV urO.sxIVX1oZiQdP2JPJrTKlZXjH5Et33qJiL1J1dmL8SnyuUYVxRr5rUWpY tWU9DCRKjy7UGXRpw X-Yahoo-SMTP: S65s63SswBDjU54Gjqw2GSWlZmfgiEU_X3tN1_9u Received: from mail-ie0-f182.google.com (axelbsd@209.85.223.182 with plain) by smtp142.mail.ukl.yahoo.com with SMTP; 14 Nov 2012 14:30:18 +0000 GMT Received: by mail-ie0-f182.google.com with SMTP id k10so881214iea.13 for ; Wed, 14 Nov 2012 06:30:17 -0800 (PST) Received: by 10.50.237.103 with SMTP id vb7mr1963662igc.29.1352903417036; Wed, 14 Nov 2012 06:30:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.17.198 with HTTP; Wed, 14 Nov 2012 06:29:55 -0800 (PST) In-Reply-To: References: <50A390BE.1090702@FreeBSD.org> From: Alexandre Date: Wed, 14 Nov 2012 15:29:55 +0100 Message-ID: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang To: Alie Tan Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-stable@freebsd.org" , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 14:30:21 -0000 On Wed, Nov 14, 2012 at 3:02 PM, Alie Tan wrote: > Hi > > Mine is already the latest. I slready synched my src today. Seems r242907 > only for i386? Cmiiw. > > Regards, > Alie T > > On Wednesday, November 14, 2012, Dimitry Andric wrote: >> On 2012-11-14 04:05, Alie Tan wrote: >>> >>> I got compilation error while compiling FreeBSD9-STABLE with Clang: >>> -m32 -c /usr/src/sys/boot/i386/boot2/sio.S >>> clang: warning: the clang compiler does not support '-fno-unit-at-a-time' >>> ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o >>> boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o >>> sio.o >>> objcopy -S -O binary boot2.out boot2.bin >>> btxld -v -E 0x2000 -f bin -b >>> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >>> boot2.ld -P 1 boot2.bin >>> kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 >>> client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 >>> output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 >>> -5 bytes available >>> *** [boot2] Error code 1 >> >> Please update your source tree to at least r242907. >> Hi, I encountered the problem, but has been resolved yesterday. # uname -a 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r242957: Tue Nov 13 15:24:22 CET 2012 root@DL380G4:/usr/obj/usr/src/sys/GENERIC amd64 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 14:41:28 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 869147D1 for ; Wed, 14 Nov 2012 14:41:28 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2FA928FC12 for ; Wed, 14 Nov 2012 14:41:27 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so640260vcb.13 for ; Wed, 14 Nov 2012 06:41:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=xWbbkUpSNmVG/R2zgs2fJRYaxgjSRoW0N1p3niAbUZc=; b=YzsUYMapFWsCEuxGgSqh8Cha2ZDrckm4DL4wy1mwZlQoe40igmBzNqp3qV9FzVkWbp +cTo7T1FKXP8AdFxZ5jfWBxAyAH/eiEMJzMqBP+XETz/Ey00qTqN5lUy02VUXKVugxoZ B+2a1Cor8Aa5THaR4X1MdlKq8keGegEkEMBUROwmMksRAzCRKJBNRCGGUGKPQxGdtqGA bAIgz3TEPnUOsXqDEwVOTn4vWmBV6N9adeXPilO8+WreSiBEbtItQg8QD+d01cPjWP2z ClwAkJvpY5MQFXtfOtZlamdAIvqqU6Y6gViguVgXXIfukYMSCdwL2GjJO0KhRj3L1DMq xgMg== MIME-Version: 1.0 Received: by 10.52.29.138 with SMTP id k10mr2282173vdh.53.1352904087244; Wed, 14 Nov 2012 06:41:27 -0800 (PST) Received: by 10.58.178.234 with HTTP; Wed, 14 Nov 2012 06:41:26 -0800 (PST) In-Reply-To: References: <50A390BE.1090702@FreeBSD.org> Date: Wed, 14 Nov 2012 22:41:26 +0800 Message-ID: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang From: Alie Tan To: Alexandre X-Gm-Message-State: ALoCoQkk1nF5dtt5hZep3ZrA+6sB2JTM9FhVn+POgZ+xUur2pAv1wjzLsYT9kSHNm1PDWHaCP8xa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org" , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 14:41:28 -0000 Ok thanks. I will try again and delete the src folder before making any compilation. Regards, Alie Tan On Wednesday, November 14, 2012, Alexandre wrote: > On Wed, Nov 14, 2012 at 3:02 PM, Alie Tan wrote: >> Hi >> >> Mine is already the latest. I slready synched my src today. Seems r242907 >> only for i386? Cmiiw. >> >> Regards, >> Alie T >> >> On Wednesday, November 14, 2012, Dimitry Andric wrote: >>> On 2012-11-14 04:05, Alie Tan wrote: >>>> >>>> I got compilation error while compiling FreeBSD9-STABLE with Clang: >>>> -m32 -c /usr/src/sys/boot/i386/boot2/sio.S >>>> clang: warning: the clang compiler does not support '-fno-unit-at-a-time' >>>> ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o >>>> boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o >>>> sio.o >>>> objcopy -S -O binary boot2.out boot2.bin >>>> btxld -v -E 0x2000 -f bin -b >>>> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o >>>> boot2.ld -P 1 boot2.bin >>>> kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 >>>> client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 >>>> output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 >>>> -5 bytes available >>>> *** [boot2] Error code 1 >>> >>> Please update your source tree to at least r242907. >>> > Hi, > I encountered the problem, but has been resolved yesterday. > > # uname -a > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r242957: Tue Nov 13 15:24:22 > CET 2012 root@DL380G4:/usr/obj/usr/src/sys/GENERIC amd64 > From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 15:34:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CFBD44C for ; Wed, 14 Nov 2012 15:34:54 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id EE0D08FC12 for ; Wed, 14 Nov 2012 15:34:53 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TYezH-00007p-K6 for freebsd-stable@freebsd.org; Wed, 14 Nov 2012 07:34:47 -0800 Date: Wed, 14 Nov 2012 07:34:47 -0800 (PST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1352907286766-5760980.post@n5.nabble.com> In-Reply-To: References: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 15:34:54 -0000 Are you Gentoo refugee? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Compilation-error-while-compiling-FreeBSD9-STABLE-with-Clang-tp5760822p5760980.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 16:06:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2890BEE5 for ; Wed, 14 Nov 2012 16:06:38 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 05C9A8FC08 for ; Wed, 14 Nov 2012 16:06:38 +0000 (UTC) Received: from [10.250.10.104] (3.sub-174-254-232.myvzw.com [174.254.232.3]) by elvis.mu.org (Postfix) with ESMTPSA id 780401A3CC2; Wed, 14 Nov 2012 08:06:37 -0800 (PST) References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> <50A3104E.5000107@mu.org> <4DDA6862-6BE5-4EF4-B6B5-141DD9123C36@hostpoint.ch> In-Reply-To: <4DDA6862-6BE5-4EF4-B6B5-141DD9123C36@hostpoint.ch> Mime-Version: 1.0 (1.0) Message-Id: <6177E5C2-7FF6-42D7-B1E0-C09803BF6383@mu.org> X-Mailer: iPhone Mail (9B206) From: Alfred Perlstein Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC Date: Wed, 14 Nov 2012 08:06:33 -0800 To: Markus Gebert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 16:06:38 -0000 On Nov 14, 2012, at 2:42 AM, Markus Gebert wrot= e: >=20 > On 14.11.2012, at 04:30, Alfred Perlstein wrote: >=20 >> A couple of ideas: >=20 > Thanks. >=20 >> 1) convert the taskqueue to a callout, but only allow one to be queued at= a time. set the granularity. >=20 > I think Konstantin's patch is going in this direction. Yes. Looks good.=20 >=20 >=20 >> 2) I think you only need to actually run garbage collection on the off-ch= ance that you pass unix file descriptors, otherwise you can get away with re= fcounting. >=20 > Hm, isn't that whats done currently? gc is only scheduled if fds are infli= ght while uipc_detach() is called. >=20 It looks to me as if it runs the gc when ANY type are in flight.=20 If you added refcounting then you could trust the refcounting so long as no u= nix sockets were in flight as its only the unix sockets that can cause cycle= s in a refcount based graph.=20 >=20 >> It's hard for me to express the exact logic needed for this though. I t= hink you would need some way to simply do refcounting until there was a unix= socket descriptor in flight, then switch to gc. Either that or make a sys= ctl that allows you administratively deny passing of unix descriptors and ju= st use refcounting. >=20 >=20 >=20 > Markus >=20 From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 17:59:37 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4CFA4C56; Wed, 14 Nov 2012 17:59:37 +0000 (UTC) (envelope-from prvs=166515a72b=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id A266A8FC13; Wed, 14 Nov 2012 17:59:36 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001058451.msg; Wed, 14 Nov 2012 17:59:34 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 14 Nov 2012 17:59:34 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=166515a72b=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <6A9D5119A4774E8C8C8E0427035FC05B@multiplay.co.uk> From: "Steven Hartland" To: "Doug Ambrisko" References: <2DC1C56CFFF24FE0B17C34AD21A7DFAA@multiplay.co.uk> <39D16C43C8274CE9B8F23C18459E2FD4@multiplay.co.uk> <20121105212911.GA17904@ambrisko.com> <27169C7FE704495087A093752D15E7B6@multiplay.co.uk> <20121106180152.GA40422@ambrisko.com> <6B5B65F4FC854EB8BBC701500096602E@multiplay.co.uk> <0B4E8AFF9DA04C6EBD2496A8B58F1D67@multiplay.co.uk> <20121109172508.GA13333@ambrisko.com> Subject: Re: mfi panic on recused on non-recusive mutex MFI I/O lock Date: Wed, 14 Nov 2012 17:59:36 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 17:59:37 -0000 ----- Original Message ----- From: "Doug Ambrisko" To: "Steven Hartland" Cc: ; Sent: Friday, November 09, 2012 5:25 PM Subject: Re: mfi panic on recused on non-recusive mutex MFI I/O lock > On Fri, Nov 09, 2012 at 05:06:03PM -0000, Steven Hartland wrote: > | > | ----- Original Message ----- > | From: "Steven Hartland" > | ... > | >I've just had another panic, trace below, but it doesn't seem to be related > | >to my changes so I'd appreciate your feedback on them as they are for now. > | > > | >While the lock patch fixes the problems I've seen, its not clear to me > | >why mfi_tbolt_reset is acquiring the lock and hence requiring > | >mfi_process_fw_state_chg_isr to jump through hoops to ensure locking > | >around queue manipulation is done correctly. Given what its doing > | >(resetting the entire adapter) I wouldn't be surprised if it should > | >really be acquiring the config lock. > | > > | >Other things I've noticed / questions > | >* Should mfi_abort sleep even if its call to mfi_mapcmd fails? > | >* Should mfi_get_controller_info really ignore the error from mfi_mapcmd? > | >* Do these controllers not support none 512 byte requests? Currently > | >all syspd requests are done assuming 512 byte sectors which the disk may > | >not be. This will both reduce performance or potentially break totally > | >if the firmware isn't translating it under the surface correctly. > | > > | >Anyway the new panic manually transcribed is:- > | >panic: Bad linx elm 0xffffff0069b0fc0 next->prev != elm > | >... > | >mfi_tbolt_get_cmd() > | >mfi_build_mpt_pass_thru() > | >mfi_tbolt_build_mpt_cmd() > | >mfi_tbolt_send_frame() > | >bus_dmamap_load() > | >mfi_mapcmd() > | >mfi_startio() > | >mfi_syspd_strategy() > | >g_disk_start() > | >g_io_schedule_down() > | >g_down_proc_body() > | >fork_exit() > | >fork_trampoline() > | > > | >Looks like mfi_cmd_tbolt_tqh has become corrupt some how, but as far as I > | >can tell all manip is done using the TAILQ macros and under mfi_io_lock > | >so its not obvious to me at this time why this is, any ideas? > | > | I've gone through looking for the possible cause of this and while there's > | nothing directly connected to the manip of this queue I've found and fixed > | quite a large number of additional problems which may have been indirectly > | causing this problem. > | > | The biggest change is to use mfi_max_cmds to limit the value stored in > | sc->mfi_max_fw_cmds as this is used extensively throughout the driver > | for allocation and range checks so having this inconsitently set opened up > | a large number of possible overrun errors. > | > | The new patch attached documents all the changes in detail. > | > | I've managed to do one test run so far which failed to reproduce any panics, > | so definitely moving in the right direction :) > | > | The machine has now been collected for repair by the supplier but I'm going > | to try and get them to put it online for more testing over the weekend. > | > | Given the failure rate so far if I can do another 4 runs with no panics I'd > | be happy that the majority of error conditions are working as expected. > > Sounds like you have made some good progress. I looked at your prior locking > change and they good. Haven't had time to go through the queue changes > yet. Just to update people on this, as its taken quite some time to track down the random issues causing panics, but I believe I made a breakthrough last night. It seems that the cleanup interation between mfi_cmd's and tbolt_cmd's is flawed meaning its possible that tbolt commands are processed after the caller has already recieved a response, cleaned and returned the mfi_cmd to the free queue. This means that its anyones guess what the result of the tbolt cleanup is as it could well be operating on a mfi_cmd thats either now in the free queue or even worse has already been reused. It also possible this was the underling issue you may well have seening which caused you to add the mfi_tbolt_complete_cmd calls to mfi_tbolt_send_frame in r242681. If this is correct then I believe the correct fix is to ensure that mfi_tbolt_return_cmd is only ever called from mfi_release_command thus ensuring completion ordering is always correct. I'm testing fixes for this theory now but initial debug has had good results. The patch of fixes is really growing, so definitely going to need someone to review in detail when I'm done. What do you think of the above, does it make sence? Would you be willing to review the patch when I'm done, before I commit it Doug? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Nov 14 21:58:26 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A57DAF52; Wed, 14 Nov 2012 21:58:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6B79A8FC13; Wed, 14 Nov 2012 21:58:26 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kp6so655762pab.13 for ; Wed, 14 Nov 2012 13:58:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=BPpPYtMykPPFq3nViXgRH1pBySMFJsiyhABJFXskSEk=; b=Yv6A9F8RLfuft6pYbAoefAUbVx5U4ulqgjDvUK+F+uW/PZXLUg3radNBKjSIXrZNEI APqckfu1ekXFzcYJ3SWacCiXAjzvhINqURzYXc3MiqPU44RR5iud6gI7fWj59QXJ3uT8 lPRVnWzJQOxYh3AJzdavaNjGp/oyWQLHJUq0zvCxoill86kgG8cHu/eLD5igMA9xqj1h 4J+lUuR1X7qzJUYYFpYq0ZISlKX4wTDkX1vhhoNa09345BGJKAjVltD9eLfibw5ukrki FvpHyPpDeFlmIVLk9JFq0BXwHqm1nSwUFUgObdbGCf9OJu4ygBSAMY6E/JOIoDGqNHIR Eetw== MIME-Version: 1.0 Received: by 10.66.89.9 with SMTP id bk9mr1641513pab.67.1352930306066; Wed, 14 Nov 2012 13:58:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Wed, 14 Nov 2012 13:58:25 -0800 (PST) In-Reply-To: References: <6908B498-6978-4995-B081-8D504ECB5C0A@hostpoint.ch> <007F7A73-75F6-48A6-9C01-E7C179CDA48A@hostpoint.ch> Date: Wed, 14 Nov 2012 13:58:25 -0800 X-Google-Sender-Auth: Pt2fLnJUrk6XoLLRGBWu_dyjAYY Message-ID: Subject: Re: thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC From: Adrian Chadd To: Markus Gebert , rwatson@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2012 21:58:26 -0000 On 14 November 2012 02:39, Markus Gebert wrote: > > On 14.11.2012, at 02:12, Adrian Chadd wrote: > > Oh lordie, just hack the kernel to make IP_BINDANY usable by any uid, > not just root. > > I was hoping that capabilitiies would actually be useful these days, > but apparently not. :( > > Then you can stop this FD exchange nonsense and this problem should go away. > :) > > > Thanks for the suggestion, I'll probably do that regardless of a fix to the > unp_gc problem, because it's indeed unnecessary overhead in our scenario. > Still that's a workaround you most probably don't want if you have untrusted > users on the system or you end up hacking in something comparable to > security.mac.seeotheruids.specificgid. Yeah. I was hoping that capabilities would be settable from userland these days. I remember talking with Robert (CC'ed) about this when Julian/I threw this into FreeBSD. He wanted me to put it behind a capability (which I did) but there was no way for userland to grant a process this capability. Robert - is there any way these days to grant capabilities to userland processes? Adrian From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 01:41:00 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E3375A00 for ; Thu, 15 Nov 2012 01:40:59 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0D48FC0C for ; Thu, 15 Nov 2012 01:40:59 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so1472161vba.13 for ; Wed, 14 Nov 2012 17:40:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=Azx6bbNa3CA4AdJm15SyQR1b8/UuaITFJ3eaqFLD4Zk=; b=VkfKWR2fZ6/+U1dK5Xl2SSCpIkKmpKiAi5eC1ZSYtySycYHJLQ8ntEGKfiUZf41S3G rY8bLAhmo6Q2PMnXW7lMrDW/XBT2AD6Uad550xWkCgwKkEjzr2/UChr3SzJ76u+L4GeY cyycq96XGzxO88Ef4mJEpp028eLlev+P4/shqKbuPGoaAuVS8IpTZ78vKxPnfkKHagpb ullfYPu2Txkjz6F55QuWGiYTOzdgWCKz4vIwxYjqoGbM+qGr3ONM9b55noiBlzTDdxd0 rOpNb7/QadnT62n5Wcw8qqzxGoqhMH7r9G/HeyAABMVjh5I9BwH2IwPVy7wgo+klG3no 54MQ== MIME-Version: 1.0 Received: by 10.220.229.133 with SMTP id ji5mr13596012vcb.51.1352943652862; Wed, 14 Nov 2012 17:40:52 -0800 (PST) Received: by 10.58.178.234 with HTTP; Wed, 14 Nov 2012 17:40:52 -0800 (PST) In-Reply-To: References: <50A390BE.1090702@FreeBSD.org> Date: Thu, 15 Nov 2012 09:40:52 +0800 Message-ID: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang From: Alie Tan To: Alexandre X-Gm-Message-State: ALoCoQmybC2fATGj9nrakvQnrZbUiaKp+79/J0oaBetX6/0fBrXLDTpXIpxvOffrxxemD+I5q1Q4 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org" , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 01:41:00 -0000 Hi, Strange, this issue happens when I use cvsup only. Did I miss something here? Is FreeBSD CVS still syncing with SVN or otherwise? Regards, Alie T On Wed, Nov 14, 2012 at 10:41 PM, Alie Tan wrote: > Ok thanks. > > I will try again and delete the src folder before making any compilation. > > Regards, > Alie Tan > > On Wednesday, November 14, 2012, Alexandre wrote: > > On Wed, Nov 14, 2012 at 3:02 PM, Alie Tan wrote: > >> Hi > >> > >> Mine is already the latest. I slready synched my src today. Seems > r242907 > >> only for i386? Cmiiw. > >> > >> Regards, > >> Alie T > >> > >> On Wednesday, November 14, 2012, Dimitry Andric > wrote: > >>> On 2012-11-14 04:05, Alie Tan wrote: > >>>> > >>>> I got compilation error while compiling FreeBSD9-STABLE with Clang: > >>>> -m32 -c /usr/src/sys/boot/i386/boot2/sio.S > >>>> clang: warning: the clang compiler does not support > '-fno-unit-at-a-time' > >>>> ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 > -o > >>>> boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o > boot2.o > >>>> sio.o > >>>> objcopy -S -O binary boot2.out boot2.bin > >>>> btxld -v -E 0x2000 -f bin -b > >>>> /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o > >>>> boot2.ld -P 1 boot2.bin > >>>> kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 > >>>> client: fmt=bin size=1575 text=0 data=0 bss=0 entry=0 > >>>> output: fmt=bin size=1e05 text=200 data=1c05 org=0 entry=0 > >>>> -5 bytes available > >>>> *** [boot2] Error code 1 > >>> > >>> Please update your source tree to at least r242907. > >>> > > Hi, > > I encountered the problem, but has been resolved yesterday. > > > > # uname -a > > 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r242957: Tue Nov 13 15:24:22 > > CET 2012 root@DL380G4:/usr/obj/usr/src/sys/GENERIC amd64 > > From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 02:38:50 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B22B91BC for ; Thu, 15 Nov 2012 02:38:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1CA288FC0C for ; Thu, 15 Nov 2012 02:38:49 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id gg13so1205964lbb.13 for ; Wed, 14 Nov 2012 18:38:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1aQGnK173lCxOJLxT3poHT1BkT0MJaKB4FmyiHsUWpM=; b=c7F8NrG5Nau/6DX/tPaaNc6OSWi2KxEAZ0lomW71k8NZQRszGnESMm1qAHDE/0aO8d 4cahOT5eAY3gZQQYBBQYUBAEH6k8It8lXzYgB3PaZaFrQz0YlA0hsEw5Ykju647KA79R OoOZ2OVz2S4kCgQiieCmIgp0Io+NFwKkaIWTY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=1aQGnK173lCxOJLxT3poHT1BkT0MJaKB4FmyiHsUWpM=; b=A72gKwwqJJv9IGUtub1QiPmJEAv4AgpPs2NLrb85E570MEYigOyvRq4w94C6xlzrin 9Ua9EK3MTtTMHV55HI7P8mealB0n53yin1mYDqHZ/PiYo9vbED9n595CfciNsxcK9c5g 6byh/yjPX1yipFr+o3U1vKH12ruEiIPHInHgXKCfwogi9i0WYIs060lHtQMKEgdp5GKp nab3vhEVURicZjnH852zTqaSlfgG9oxbZ5l0lQRZ8ub+NyvSNNyFagErIK3ohk20+Wu6 rV/SxPTXFvcmUFSUlUJeESGYhz+5aI6Ekhivejl6IwbGkj6F3TFi1kTkZXMjre4SlsYa b7Mw== Received: by 10.152.104.115 with SMTP id gd19mr27204393lab.13.1352947128378; Wed, 14 Nov 2012 18:38:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Wed, 14 Nov 2012 18:38:17 -0800 (PST) In-Reply-To: References: <50A390BE.1090702@FreeBSD.org> From: Eitan Adler Date: Wed, 14 Nov 2012 21:38:17 -0500 Message-ID: Subject: Re: Compilation error while compiling FreeBSD9-STABLE with Clang To: Alie Tan Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmV42XO/ktt823TY/R8UX/hF7EmqNfG1mfyl5iDB1kn6+5D+grsyDN1wqGlf4C4t0fAb6MR Cc: Dimitry Andric , "freebsd-stable@freebsd.org" , Alexandre X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 02:38:50 -0000 On 14 November 2012 20:40, Alie Tan wrote: > Hi, > > Strange, this issue happens when I use cvsup only. Did I miss something > here? Is FreeBSD CVS still syncing with SVN or otherwise? known issue atm. people are working on fixing it. -- Eitan Adler From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 05:16:40 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 181AC3F0 for ; Thu, 15 Nov 2012 05:16:40 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id DABD98FC08 for ; Thu, 15 Nov 2012 05:16:39 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kp6so880600pab.13 for ; Wed, 14 Nov 2012 21:16:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=PQkt958wfrF1ZjRbXuYLSGrjZxYFSq48fD624WZEM9o=; b=Ijo+d2AIx/xwrr5hhKIso0+7hXiYZtrqlGJ568V+hK0toLmqHM0L3X/yZS1+iwm7V/ wWCASpr/a8DKWTcko80E08u+iQNp6CFFBxBMcjVc7DBqOCBBVrSviId9CAkDlOI5dirz SxJsASptgFFbSuYLhKUVsvZXCdPj+4+LnHAGjL7zwQzlssF7GfliIBtbk6kNNo7yV00g vdRwZMwjgXDHom2xR79LDLFX/lIHaxmNoK6vQu+AkW2mZKXkUErROkmwrSV0IPyivjEX 560OE1oR7W/H0mCuaJwKdi2uUvQm9BNgZ/6bAi4QcsHojsvLEkrxr4sq4MQdUFrceCOl IabQ== MIME-Version: 1.0 Received: by 10.68.189.38 with SMTP id gf6mr1026475pbc.145.1352956593059; Wed, 14 Nov 2012 21:16:33 -0800 (PST) Received: by 10.66.190.161 with HTTP; Wed, 14 Nov 2012 21:16:32 -0800 (PST) Date: Thu, 15 Nov 2012 13:16:32 +0800 Message-ID: Subject: Compilation error while compiling FreeBSD9-STABLE with Clang From: Alie Tan To: freebsd-stable@freebsd.org X-Gm-Message-State: ALoCoQkYJF21hbkCTWGgTvMOON1OHpoNBk5LQgKD3u1yNjZnHfejl5186P6b97eiH4ZVgMSH9vIk Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 05:16:40 -0000 > On 14 November 2012 20:40, Alie Tan wrote: > > Hi, > > > > Strange, this issue happens when I use cvsup only. Did I miss something > > here? Is FreeBSD CVS still syncing with SVN or otherwise? > > known issue atm. people are working on fixing it. > > > -- > Eitan Adler No offense. But why there is no announcement for this issue, at least on forums.freebsd.org? So people don't waste their time trying to fix the issue or looking for solution? Regards, Alie T From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 06:03:57 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EBF956A for ; Thu, 15 Nov 2012 06:03:57 +0000 (UTC) (envelope-from lhao62@kimo.com) Received: from smtpa.meduniwien.ac.at (manon.srv.meduniwien.ac.at [149.148.224.15]) by mx1.freebsd.org (Postfix) with ESMTP id C1C1B8FC08 for ; Thu, 15 Nov 2012 06:03:56 +0000 (UTC) Received: from smtpa.meduniwien.ac.at (localhost [127.0.0.1]) by smtpa.meduniwien.ac.at (Postfix) with SMTP id 026F714412A for ; Thu, 15 Nov 2012 07:03:55 +0100 (CET) Received: from kcs2-server (60-242-179-86.static.tpgi.com.au [60.242.179.86]) by smtpa.meduniwien.ac.at (Postfix) with ESMTPSA id 3A633144126 for ; Thu, 15 Nov 2012 07:03:54 +0100 (CET) Message-ID: <010bcaf0-41228-87807109606366@kcs2-server> From: "Li Hao" To: freebsd-stable@freebsd.org Subject: Proposition Date: Thu, 15 Nov 2012 17:02:54 +1100 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Priority: 3 X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.11.15.55415 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Li Hao List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 06:03:57 -0000 Greetings, I am Mr. Li Hao, CFO of China Merchants Bank, P.R.C. I have a discreet proposition for you to the tune of 105 Million EUR. Please reply for details. Warmest, LH From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 10:43:08 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B55FB1A for ; Thu, 15 Nov 2012 10:43:08 +0000 (UTC) (envelope-from freebsd-stable@dino.sk) Received: from mailhost.netlab.sk (mailhost.netlab.sk [84.245.65.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0A74A8FC08 for ; Thu, 15 Nov 2012 10:43:07 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan, TLS: TLSv1/SSLv3,128bits,AES128-SHA) by mailhost.netlab.sk with ESMTPSA; Thu, 15 Nov 2012 11:39:03 +0100 id 00513AB7.50A4C647.00010069 Date: Thu, 15 Nov 2012 11:38:55 +0100 From: Milan Obuch To: freebsd-stable@freebsd.org Subject: Does svn-to-cvs still work? & How to use freebsd-update? Message-ID: <20121115113855.38923fdc@zeta.dino.sk> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEX+/v7++v6YOTrq8PCcuIX989UvOSj++v0BNCbpAAAAB3RJTUUHsQwfFzs7RBhzUQAAAhJJREFUOI1dU8GOqzAMNKIoV1bvwD1i0ysqrHplIdBrVSX7ATSbd03VVvn9tQNtQy0hjAdn7LED4AAcPtWm9RV+MPSfxhBLx9ajd6X/ngB6/mTwnRSZua7i7Ca+0ctZKo4Qmz+JY13X6I3nFZBxIYW1PbgfQ5RP8g0XlltEWGf3cV03joYpRnFbvYDKbXjZlXyyhEZA4lI+cN3NaVXE4VKjSwTExO10eTEkkJVqIAD5z0nUBQJluQDRSQjcrBiHAJxZlAH5CUMBMC7OcJ4LMQNnxhZ1HYPscMc6J4UlWRMNwzOpCcAHKSICd1EDn83abdREIbXsHkD1OinP1aCUCOEVRaa1lMcvywUWdYgk13JQUpYNKmvXQ8Kw5ML9YI5h8SakctBc7E/IYuLhYd/zZIk+1gM1vNweQBvHE0j+oYah3sMqAytQYlZk6+ANaaawJdu3OFzYGMZ3iGpa3qMlq9ZH0VZTgrCtw/ngdYkEIIpSbP1bWQAdFdX9vocBdkH2qVjVmuMu3gI5rjs814EUdrCZgWlPaxZZ3RiLFUtr+ud0PXwp2dnQSNXgePt6AZpBj6UMJ7VQkzN4utVeaSW1Dhn/kblGrKeMvNGnzwX4zuEDarYz1KdPtR60Gul0Gued+515SJXhCsl+Tx/3kY/UDvicPll9mfu50t3tvQ/thZpJYgeuwdSKNJ6tCD98MCgoxLDaPxbwqqwPWaWiAAAAAElFTkSuQmCC X-Face: ak5rwz4-aUa>hPFZlcg,bXxn.(TN}e9DGFrKU\.i_'B[&5=pAd9o"j)5VSUYW:BRQG#^42Ev$Il|; Ztn=,C X-Operating-System: FreeBSD/amd64 8.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 10:43:08 -0000 Hello, it looks like updating source/ports via csup does not work for some time. I was using for a long time simple command sequence csup -h cvsup.freebsd.org /usr/share/examples/cvsup/stable-supfile csup -h cvsup.freebsd.org /usr/share/examples/cvsup/ports-supfile to update both source files and ports collection. For some (maybe five) days there is nothing updated. Is svn-to-cvs stil working? In some mail there was announced February 2013 as last time it will work (writing from my memory, not looking up this mail in some archive, so I could be wrong). As I will need to change my work flow anyhow in some not too distant future, I decided to test freebsd-update, which should be able to update system sources along with binaries in compiled form. I need only the former, but that's just me (and knowing how to use it for userland binaries/kernel update is not bad anyway). When I tried it, however, all I saw was this: # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. So no joy here - no files fetched. I was using /etc/freebsd-update.conf untouched, as installed on system, or copied from /usr/src/etc directory if it did not exist on my system. Is there anything I could try to find the root cause it does not work for me? I am sure it is used by others and I did not see any message about it not working (at least not today or in not too distant past). Regards, Milan From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 12:35:13 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D205914 for ; Thu, 15 Nov 2012 12:35:13 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 31AEC8FC13 for ; Thu, 15 Nov 2012 12:35:12 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TYyev-0003yY-5l for freebsd-stable@freebsd.org; Thu, 15 Nov 2012 13:35:05 +0100 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TYyeu-0008B4-58 for freebsd-stable@freebsd.org; Thu, 15 Nov 2012 13:35:04 +0100 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Date: Thu, 15 Nov 2012 13:35:04 +0100 Subject: portsnap not updating MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.10 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: 258bd43c1b7c380ff6f1b27dffaa1ebc X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 12:35:13 -0000 Hello, Probably the wrong mailinglist. But portsnap is not updating since a few days while there are commits on the ports tree. [1] After some searching I found I am not the only one. Apparently there is maintenance being done on the servers. http://www.mail-archive.com/freebsd-ports@freebsd.org/msg45395.html I read a lot of blogs/RSS/etc. Nowhere any signs of maintenance on the servers. What is wrong with announcing these things on for example www.freebsd.org? NB: I know it is voluntary work, thanks for doing it. Regards, Ronald. [1] [root@sjakie ~]# time update_portstree.sh Looking up eu.portsnap.FreeBSD.org mirrors... 6 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Latest snapshot on server matches what we already have. No updates needed. Ports tree is already up to date. ===>>> There are no new versions available ===>>> 968 total installed ports Thu Nov 15 13:23:57 CET 2012 [root@sjakie ~]# ls -l /usr/ports/INDEX-* -rw-r--r-- 1 root wheel 26830552 Nov 12 20:38 /usr/ports/INDEX-7 -rw-r--r-- 1 root wheel 26714819 Nov 12 20:38 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 26696014 Nov 12 20:38 /usr/ports/INDEX-9 From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 14:34:33 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9C0D8D2 for ; Thu, 15 Nov 2012 14:34:33 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id B625B8FC0C for ; Thu, 15 Nov 2012 14:34:33 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TZ0WW-0002Ct-GB for freebsd-stable@freebsd.org; Thu, 15 Nov 2012 06:34:32 -0800 Date: Thu, 15 Nov 2012 06:34:32 -0800 (PST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1352990072450-5761220.post@n5.nabble.com> In-Reply-To: <20121115113855.38923fdc@zeta.dino.sk> References: <20121115113855.38923fdc@zeta.dino.sk> Subject: Re: Does svn-to-cvs still work? & How to use freebsd-update? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 14:34:33 -0000 > I am sure it is used by others and I did not see any message > about it not working I think there are plenty messages, just scattered. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Does-svn-to-cvs-still-work-How-to-use-freebsd-update-tp5761168p5761220.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 14:37:20 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B022AEE for ; Thu, 15 Nov 2012 14:37:20 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id EC0798FC1A for ; Thu, 15 Nov 2012 14:37:18 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TZ0ZC-0002SE-0z for freebsd-stable@freebsd.org; Thu, 15 Nov 2012 06:37:18 -0800 Date: Thu, 15 Nov 2012 06:37:18 -0800 (PST) From: Jakub Lach To: freebsd-stable@freebsd.org Message-ID: <1352990238016-5761222.post@n5.nabble.com> In-Reply-To: <1352990072450-5761220.post@n5.nabble.com> References: <20121115113855.38923fdc@zeta.dino.sk> <1352990072450-5761220.post@n5.nabble.com> Subject: Re: Does svn-to-cvs still work? & How to use freebsd-update? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 14:37:20 -0000 Just to be clear, cvs is currently not syncing to svn. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Does-svn-to-cvs-still-work-How-to-use-freebsd-update-tp5761168p5761222.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Thu Nov 15 15:06:42 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C6CEC4D for ; Thu, 15 Nov 2012 15:06:41 +0000 (UTC) (envelope-from paulo@nlink.com.br) Received: from nlink.com.br (smtp.nlink.com.br [187.87.132.3]) by mx1.freebsd.org (Postfix) with SMTP id 914CC8FC12 for ; Thu, 15 Nov 2012 15:06:39 +0000 (UTC) Received: (qmail 18224 invoked from network); 15 Nov 2012 12:06:31 -0300 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=nlink.com.br; b=Jt0VaVxEoNVarWDPRfsazJJq4orhS6tP2vWjK8iyNO1wM8uaT4zJYiEwYAHyv1//Kpej8xnYm3FtGybjY88tJN8Ul6sg6VZ1GsgILo0NMsovPxLeb8adm7ZrRUqEDcu+ ; Received: from unknown (HELO j1.nlink.com.br) (paulo@intra.nlink.com.br@201.12.59.126) by smtp.nlink.com.br with SMTP; 15 Nov 2012 12:06:31 -0300 Message-ID: <50A504F6.5010208@nlink.com.br> Date: Thu, 15 Nov 2012 12:06:30 -0300 From: Paulo Fragoso User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120719 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 9.1-PRERELEASE jail_sysvipc_allow References: <50A381FC.9090809@nlink.com.br> In-Reply-To: <50A381FC.9090809@nlink.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 15:06:42 -0000 Reading /etc/rc.d/jail script I found the answer: jail_*_parameters="allow.sysvipc=1" in /etc/rc.conf Paulo. On 14/11/2012 08:35, Paulo Fragoso wrote: > I've instaled FreeBSD 9 for hosts some jails and setting > jail_sysvipc_allow="YES" in host rc.conf, why is > security.jail.sysvipc_allowed false in jail? > From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 15:31:16 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E26FF2B6 for ; Fri, 16 Nov 2012 15:31:16 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from local.wintek.com (local.wintek.com [72.12.201.234]) by mx1.freebsd.org (Postfix) with ESMTP id A7AD28FC0C for ; Fri, 16 Nov 2012 15:31:16 +0000 (UTC) Received: from rjk.wintek.local (172.28.1.248) by local.wintek.com (172.28.1.234) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 16 Nov 2012 10:30:04 -0500 Message-ID: <50A65BFC.7030406@wintek.com> Date: Fri, 16 Nov 2012 10:30:04 -0500 From: Richard Kuhns Organization: Wintek Corporation User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: bge on the new Mac Mini X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rjk@wintek.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 15:31:16 -0000 Hi all, Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac Minis via the memstick image; they seem to be pretty good little boxes for things like offsite secondary nameservers, for example, and they're easily replaced in case of problems. However, the newest minis have slightly different hardware, and FreeBSD can't find the built-in NIC. pciconf -lv on the new mini shows it as none3@pci0:1:0:0: class=0x020000 card=0x168614e4 chip=0x168614e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' class = network subclass = ethernet The previous edition mini (that works) reports bge0@pci0:2:0:0: class=0x020000 card=0x16b414e4 chip=0x16b414e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme BCM57765 Gigabit Ethernet PCIe' class = network subclass = ethernet Is there a chance that adding the new card/chip info to the current driver would allow it to work? I'll be happy to test and report back. I'm afraid I'm not familiar enough with hardware at that level to figure out the patch myself. Thanks! -- Richard Kuhns My Desk: 765-269-8541 Wintek Corporation Internet Support: 765-269-8503 427 N 6th Street STE C Consulting: 765-269-8504 Lafayette, IN 47901-2211 Accounting: 765-269-8502 From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 15:41:42 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 218995B7 for ; Fri, 16 Nov 2012 15:41:42 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 061328FC08 for ; Fri, 16 Nov 2012 15:41:41 +0000 (UTC) Received: from Alfreds-MacBook-Pro-5.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id 644691A3DDD; Fri, 16 Nov 2012 07:41:41 -0800 (PST) Message-ID: <50A65EB5.7040004@mu.org> Date: Fri, 16 Nov 2012 07:41:41 -0800 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: rjk@wintek.com Subject: Re: bge on the new Mac Mini References: <50A65BFC.7030406@wintek.com> In-Reply-To: <50A65BFC.7030406@wintek.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 15:41:42 -0000 Often that is all that is needed. It's worth a shot and reporting back. Do you know how to update the table in the driver, rebuild/install kernel and check? -Alfred On 11/16/12 7:30 AM, Richard Kuhns wrote: > Hi all, > > Over the last month or so I've installed FreeBSD 9 (-stable) on several Mac > Minis via the memstick image; they seem to be pretty good little boxes for > things like offsite secondary nameservers, for example, and they're easily > replaced in case of problems. > > However, the newest minis have slightly different hardware, and FreeBSD can't > find the built-in NIC. pciconf -lv on the new mini shows it as > > none3@pci0:1:0:0: class=0x020000 card=0x168614e4 chip=0x168614e4 rev=0x01 > hdr=0x00 > vendor = 'Broadcom Corporation' > class = network > subclass = ethernet > > The previous edition mini (that works) reports > > bge0@pci0:2:0:0: class=0x020000 card=0x16b414e4 chip=0x16b414e4 rev=0x10 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'NetXtreme BCM57765 Gigabit Ethernet PCIe' > class = network > subclass = ethernet > > Is there a chance that adding the new card/chip info to the current driver would > allow it to work? I'll be happy to test and report back. I'm afraid I'm not > familiar enough with hardware at that level to figure out the patch myself. > > Thanks! From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 15:54:02 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E064CA9 for ; Fri, 16 Nov 2012 15:54:02 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from local.wintek.com (local.wintek.com [72.12.201.234]) by mx1.freebsd.org (Postfix) with ESMTP id DABB28FC14 for ; Fri, 16 Nov 2012 15:54:01 +0000 (UTC) Received: from rjk.wintek.local (172.28.1.248) by local.wintek.com (172.28.1.234) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 16 Nov 2012 10:54:00 -0500 Message-ID: <50A66198.6060108@wintek.com> Date: Fri, 16 Nov 2012 10:54:00 -0500 From: Richard Kuhns Organization: Wintek Corporation User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: bge on the new Mac Mini References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> In-Reply-To: <50A65EB5.7040004@mu.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rjk@wintek.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 15:54:02 -0000 On 11/16/12 10:41, Alfred Perlstein wrote: > Often that is all that is needed. It's worth a shot and reporting back. > > Do you know how to update the table in the driver, rebuild/install > kernel and check? > > -Alfred > I'm afraid not. I grepped for the hex value reported on the one that works (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I don't know what to add :-( I don't have any problem with rebuilding and installing a new kernel, though. -- Richard Kuhns My Desk: 765-269-8541 Wintek Corporation Internet Support: 765-269-8503 427 N 6th Street STE C Consulting: 765-269-8504 Lafayette, IN 47901-2211 Accounting: 765-269-8502 From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 16:20:50 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0D999AA for ; Fri, 16 Nov 2012 16:20:50 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id BC8CE8FC16 for ; Fri, 16 Nov 2012 16:20:50 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TZOer-0007fL-8C; Fri, 16 Nov 2012 11:20:45 -0500 Date: Fri, 16 Nov 2012 11:20:45 -0500 From: Gary Palmer To: Richard Kuhns Subject: Re: bge on the new Mac Mini Message-ID: <20121116162045.GC24320@in-addr.com> References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> <50A66198.6060108@wintek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50A66198.6060108@wintek.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: Alfred Perlstein , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 16:20:51 -0000 On Fri, Nov 16, 2012 at 10:54:00AM -0500, Richard Kuhns wrote: > On 11/16/12 10:41, Alfred Perlstein wrote: > > Often that is all that is needed. It's worth a shot and reporting back. > > > > Do you know how to update the table in the driver, rebuild/install > > kernel and check? > > > > -Alfred > > > > I'm afraid not. I grepped for the hex value reported on the one that works > (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I > don't know what to add :-( > > I don't have any problem with rebuilding and installing a new kernel, though. 14e4 is the ID for Broadcom 16b4 is the ID for BCM57765, a NetXtreme Desktop/Mobile chip http://www.broadcom.com/support/ethernet_nic/determine_driver.php has a list of the BCM PCI ID values There is a (frequently incomplete) database of user reported PCI values at http://www.pcidatabase.com. It has the BCM ID (14e4), but not your chip Linux uses the tg3 driver for that chipset apparently, but I think thats a general dumping ground for a lot of Broadcom products. Not sure what the appropriate FreeBSD driver to add the ID code to would be. Regards, Gary From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 16:25:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41AFCC26 for ; Fri, 16 Nov 2012 16:25:38 +0000 (UTC) (envelope-from edwinlculp@gmail.com) Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by mx1.freebsd.org (Postfix) with ESMTP id 021838FC14 for ; Fri, 16 Nov 2012 16:25:37 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so3727164oag.13 for ; Fri, 16 Nov 2012 08:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=5//bBcgcix7CblpRBAnOVtmBIhDD8PqDs0vMO68UqRI=; b=cdKJchJS6U7KSwPkdYaGIPEsgN3ckEqelaIDiFDxhvK9sNgk6eYZz36Ib6DN4hcZe7 W9qw5rtrjRTCuD3FiR8g5BFrivxlR/VxO4NuH+BjxPSAyOMWyZSclSKMCBIw0Y+MmaiU D4RZrzgxYGpgx+I6lanNFWA5zZVrYOIZi/VAF+bkSGzzeqe/Giop3edbSdmhTXeatD0G z5Algn7exsUk+8P8c32+GLUb5fZc8y5YQ9LC+mOLtklbBqjEzO7NGZFKio21hA6AfGD/ wy9A6hOYOGvDd91PMXN/fn92gud3MmqzRbCpj9Z8Tp4NJ+J9ypYVSrfdRSiuRplydto9 r+wQ== MIME-Version: 1.0 Received: by 10.60.26.72 with SMTP id j8mr4307825oeg.68.1353083137566; Fri, 16 Nov 2012 08:25:37 -0800 (PST) Received: by 10.182.69.5 with HTTP; Fri, 16 Nov 2012 08:25:37 -0800 (PST) Date: Fri, 16 Nov 2012 10:25:37 -0600 Message-ID: Subject: confirm that csup is still usable fos the new 9.1 From: "Edwin L. Culp W." To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 16:25:38 -0000 I haven't received updates to sources, ports or release for a few days. The process seems to work, no errors, but no updating. I seem to remember talk of no longer using csup but I could be confused. Thanks. results of named: 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #320 r229960M: Sun Nov 11 05:04:45 CST 2012 Thanks , ed From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 16:27:18 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6870FDBF; Fri, 16 Nov 2012 16:27:18 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from local.wintek.com (local.wintek.com [72.12.201.234]) by mx1.freebsd.org (Postfix) with ESMTP id 2AE178FC17; Fri, 16 Nov 2012 16:27:17 +0000 (UTC) Received: from rjk.wintek.local (172.28.1.248) by local.wintek.com (172.28.1.234) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 16 Nov 2012 11:27:17 -0500 Message-ID: <50A66965.20109@wintek.com> Date: Fri, 16 Nov 2012 11:27:17 -0500 From: Richard Kuhns Organization: Wintek Corporation User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: Gary Palmer Subject: Re: bge on the new Mac Mini References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> <50A66198.6060108@wintek.com> <20121116162045.GC24320@in-addr.com> In-Reply-To: <20121116162045.GC24320@in-addr.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Alfred Perlstein , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rjk@wintek.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 16:27:18 -0000 On 11/16/12 11:20, Gary Palmer wrote: > On Fri, Nov 16, 2012 at 10:54:00AM -0500, Richard Kuhns wrote: >> On 11/16/12 10:41, Alfred Perlstein wrote: >>> Often that is all that is needed. It's worth a shot and reporting back. >>> >>> Do you know how to update the table in the driver, rebuild/install >>> kernel and check? >>> >>> -Alfred >>> >> >> I'm afraid not. I grepped for the hex value reported on the one that works >> (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I >> don't know what to add :-( >> >> I don't have any problem with rebuilding and installing a new kernel, though. > > 14e4 is the ID for Broadcom > 16b4 is the ID for BCM57765, a NetXtreme Desktop/Mobile chip > > http://www.broadcom.com/support/ethernet_nic/determine_driver.php has a list > of the BCM PCI ID values > > There is a (frequently incomplete) database of user reported PCI values at > http://www.pcidatabase.com. It has the BCM ID (14e4), but not your chip > > Linux uses the tg3 driver for that chipset apparently, but I think thats > a general dumping ground for a lot of Broadcom products. Not sure what the > appropriate FreeBSD driver to add the ID code to would be. > > Regards, > > Gary > Sorry, I should have been more clear. I grepped for those values in /usr/src/sys/dev/bge/*, since that's the driver that's used on the older minis. I assume that's where the table is that Alfred mentioned; I just don't know what to add to it. -- Richard Kuhns My Desk: 765-269-8541 Wintek Corporation Internet Support: 765-269-8503 427 N 6th Street Consulting: 765-269-8504 Lafayette, IN 47901-2211 Accounting: 765-269-8502 From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 16:44:51 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C7596A9 for ; Fri, 16 Nov 2012 16:44:51 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0BC5A8FC0C for ; Fri, 16 Nov 2012 16:44:50 +0000 (UTC) Received: from Alfreds-MacBook-Pro-5.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id 0E0091A3DDA for ; Fri, 16 Nov 2012 08:44:49 -0800 (PST) Message-ID: <50A66D82.9050401@mu.org> Date: Fri, 16 Nov 2012 08:44:50 -0800 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: bge on the new Mac Mini References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> <50A66198.6060108@wintek.com> <20121116162045.GC24320@in-addr.com> <50A66965.20109@wintek.com> In-Reply-To: <50A66965.20109@wintek.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 16:44:51 -0000 On 11/16/12 8:27 AM, Richard Kuhns wrote: > On 11/16/12 11:20, Gary Palmer wrote: >> On Fri, Nov 16, 2012 at 10:54:00AM -0500, Richard Kuhns wrote: >>> On 11/16/12 10:41, Alfred Perlstein wrote: >>>> Often that is all that is needed. It's worth a shot and reporting back. >>>> >>>> Do you know how to update the table in the driver, rebuild/install >>>> kernel and check? >>>> >>>> -Alfred >>>> >>> I'm afraid not. I grepped for the hex value reported on the one that works >>> (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I >>> don't know what to add :-( >>> >>> I don't have any problem with rebuilding and installing a new kernel, though. >> 14e4 is the ID for Broadcom >> 16b4 is the ID for BCM57765, a NetXtreme Desktop/Mobile chip >> >> http://www.broadcom.com/support/ethernet_nic/determine_driver.php has a list >> of the BCM PCI ID values >> >> There is a (frequently incomplete) database of user reported PCI values at >> http://www.pcidatabase.com. It has the BCM ID (14e4), but not your chip >> >> Linux uses the tg3 driver for that chipset apparently, but I think thats >> a general dumping ground for a lot of Broadcom products. Not sure what the >> appropriate FreeBSD driver to add the ID code to would be. >> >> Regards, >> >> Gary >> > Sorry, I should have been more clear. I grepped for those values in > /usr/src/sys/dev/bge/*, since that's the driver that's used on the older minis. > I assume that's where the table is that Alfred mentioned; I just don't know what > to add to it. > Here's a cool trick you can do. 1) make a backup of your /boot/kernel directory: mv /boot/kernel /boot/kernel.good (now you can boot to a known good kernel if you blow things up) 2) hack a few drivers to add the PCI id. 3) now build a kernel WITHOUT most of the nic drivers. 4) reboot with this kernel 5) try loading/unloading the various drivers you suspect will be compatible until it either works or you get tired. :) Eventually you'll find the change that works. Go look at commit logs to see how others have added PCI ids to the drivers. It's usually in a table or under a simple "if" statement. It honestly won't take you that long, probably a few hours of head scratching. -Alfred From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 17:09:30 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EABC692 for ; Fri, 16 Nov 2012 17:09:30 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 654B18FC12 for ; Fri, 16 Nov 2012 17:09:30 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so239147lbb.13 for ; Fri, 16 Nov 2012 09:09:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=K1p2Fw+mWugFjiox96TUk64SHhJW9tDyWXky3q3jOmU=; b=geisiNkIlnGO1os528RbyYZJikt3BV9JUdrgHVasROKYJARvKnfeWMiLrNyoAqZZGh rCYhwwYoHMY8uL/V8AeApqoJ1cZ6AO1VlLONQwn4axT3fcWOVlwhumCzwF6ITQV89ZDB aB9NzMdSzOqHQye0zvT3gF347WbtFlzOceDCI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=K1p2Fw+mWugFjiox96TUk64SHhJW9tDyWXky3q3jOmU=; b=aehdNkbMvvfyG4P87WTeIYPMF32MWfhAvNULLmGGnu5CWsU5E5hXr4nDbnQD/liTPt /E6aSHeZP4/emnD6xlfm5cFe36kMNINYcoRLfq2z6BrSVUMYPsQt+V991NJlTPHapvWZ 5RdUjL5eeYYccv0AGau5nAd7E2mo0LE4iMogtbQAbvTbWkfeG2EPt5mdy8hmtvjxSinG lIvAso0c8NF4Z3LT6EoJPFJEJXUQkk4GNcJraCG1YTNeDq7ZXcdEBsxA0OIw7WAuqBL1 fd9/HqSIefO+TV7QuNS0uv1MqvGCInckdCuXnFPQoSZ6SxOqXbzFEzsr+hmyb1I/CYxm zNXA== Received: by 10.112.54.40 with SMTP id g8mr2256329lbp.49.1353085769193; Fri, 16 Nov 2012 09:09:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Fri, 16 Nov 2012 09:08:58 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Fri, 16 Nov 2012 12:08:58 -0500 Message-ID: Subject: Re: confirm that csup is still usable fos the new 9.1 To: "Edwin L. Culp W." Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQk0kUtBTO553IZ70tDTzIApm+FSiGPRUT53MKz4qGAJBRzWWJoYilQdGyrS1NTjBXaPcoBz Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 17:09:31 -0000 On 16 November 2012 11:25, Edwin L. Culp W. wrote: > I haven't received updates to sources, ports or release for a few days. > The process seems to work, no errors, but no updating. There are known problems with the cluster at this time. The machines were recently moved, upgraded, and generally manipulated. We are working to fix this as fast as possible. -- Eitan Adler From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 17:09:38 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34532BE for ; Fri, 16 Nov 2012 17:09:38 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id DCA338FC15 for ; Fri, 16 Nov 2012 17:09:37 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TZPQ4-0007kZ-A0; Fri, 16 Nov 2012 12:09:32 -0500 Date: Fri, 16 Nov 2012 12:09:32 -0500 From: Gary Palmer To: Richard Kuhns Subject: Re: bge on the new Mac Mini Message-ID: <20121116170932.GD24320@in-addr.com> References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> <50A66198.6060108@wintek.com> <20121116162045.GC24320@in-addr.com> <50A66965.20109@wintek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50A66965.20109@wintek.com> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: Alfred Perlstein , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 17:09:38 -0000 On Fri, Nov 16, 2012 at 11:27:17AM -0500, Richard Kuhns wrote: > On 11/16/12 11:20, Gary Palmer wrote: > > On Fri, Nov 16, 2012 at 10:54:00AM -0500, Richard Kuhns wrote: > >> On 11/16/12 10:41, Alfred Perlstein wrote: > >>> Often that is all that is needed. It's worth a shot and reporting back. > >>> > >>> Do you know how to update the table in the driver, rebuild/install > >>> kernel and check? > >>> > >>> -Alfred > >>> > >> > >> I'm afraid not. I grepped for the hex value reported on the one that works > >> (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I > >> don't know what to add :-( > >> > >> I don't have any problem with rebuilding and installing a new kernel, though. > > > > 14e4 is the ID for Broadcom > > 16b4 is the ID for BCM57765, a NetXtreme Desktop/Mobile chip > > > > http://www.broadcom.com/support/ethernet_nic/determine_driver.php has a list > > of the BCM PCI ID values > > > > There is a (frequently incomplete) database of user reported PCI values at > > http://www.pcidatabase.com. It has the BCM ID (14e4), but not your chip > > > > Linux uses the tg3 driver for that chipset apparently, but I think thats > > a general dumping ground for a lot of Broadcom products. Not sure what the > > appropriate FreeBSD driver to add the ID code to would be. > > > > Regards, > > > > Gary > > > > Sorry, I should have been more clear. I grepped for those values in > /usr/src/sys/dev/bge/*, since that's the driver that's used on the older minis. > I assume that's where the table is that Alfred mentioned; I just don't know what > to add to it. > The probe table appears to be bge_devs in if_bge.c. The values there are #define'd in if_bgereg.h, but for a quick hack you just need to add the value to the table Gary From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 17:14:48 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF65B348 for ; Fri, 16 Nov 2012 17:14:48 +0000 (UTC) (envelope-from b.smeelen@ose.nl) Received: from mail.ose.nl (mail.ose.nl [212.178.134.164]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFA38FC08 for ; Fri, 16 Nov 2012 17:14:47 +0000 (UTC) X-Footer: b3NlLm5s Received: from localhost ([127.0.0.1]) by mail.ose.nl (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)) for freebsd-stable@freebsd.org; Fri, 16 Nov 2012 18:14:45 +0100 Message-ID: <50A67485.7090701@ose.nl> Date: Fri, 16 Nov 2012 18:14:45 +0100 From: Bas Smeelen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: confirm that csup is still usable fos the new 9.1 References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 17:14:49 -0000 On 11/16/2012 05=3A25 PM=2C Edwin L=2E Culp W=2E wrote=3A =3E I haven=27t received updates to sources=2C ports or release for a few d= ays=2E =3E The process seems to work=2C no errors=2C but no updating=2E =3E =3E I seem to remember talk of no longer using csup but I could be confused= =2E =3E =3E Thanks=2E =3E =3E results of named=3A =3E =3E 9=2E1-PRERELEASE FreeBSD 9=2E1-PRERELEASE =23320 r229960M=3A Sun Nov= 11 05=3A04=3A45 =3E CST 2012 Hi Ed=2C Uhm=2C no confirmation for the future I guess=3F I still had a couple of servers upgraded with csup to 9=2E1-RC3 using cvs= =20 tag RELENG=5F9=5F1=2E It seems that you have RELENG=5F9 which correspondents to 9-STABLE=2E This is still at 9=2E1-PRERELEASE and maybe there are no updates due to=20= the focus on 9=2E1-RELEASE=2E I remember having read that cvs will not be available in the future for=20= the new releases being RELENG=5F8=5F3 =288=2E3-RELEASE=29 and RELENG=5F9=5F= 1=20 =289=2E1-RELEASE=29 at the moment=2C but it will continue to be available f= or=20 the STABLE and CURRENT=2E From the revision number in uname I guess you are using svn =3F Or is=20= this also available when using csup=3F This e-mail message=2C including any attachment=28s=29=2C is intended solel= y for the addressee or addressees=2E Any views or opinions presented herein= are solely those of the author and do not necessarily represent those of O= SE=2E If you are not the intended recipient of this communication please return t= his e-mail message and the attachment=28s=29 to the sender and delete and d= estroy all copies=2E From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 17:25:53 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5229BA35; Fri, 16 Nov 2012 17:25:53 +0000 (UTC) (envelope-from rjk@wintek.com) Received: from local.wintek.com (local.wintek.com [72.12.201.234]) by mx1.freebsd.org (Postfix) with ESMTP id 03D318FC0C; Fri, 16 Nov 2012 17:25:52 +0000 (UTC) Received: from rjk.wintek.local (172.28.1.248) by local.wintek.com (172.28.1.234) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 16 Nov 2012 12:25:52 -0500 Message-ID: <50A67720.70603@wintek.com> Date: Fri, 16 Nov 2012 12:25:52 -0500 From: Richard Kuhns Organization: Wintek Corporation User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: Gary Palmer Subject: Re: bge on the new Mac Mini References: <50A65BFC.7030406@wintek.com> <50A65EB5.7040004@mu.org> <50A66198.6060108@wintek.com> <20121116162045.GC24320@in-addr.com> <50A66965.20109@wintek.com> <20121116170932.GD24320@in-addr.com> In-Reply-To: <20121116170932.GD24320@in-addr.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Alfred Perlstein , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rjk@wintek.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 17:25:53 -0000 On 11/16/12 12:09, Gary Palmer wrote: > On Fri, Nov 16, 2012 at 11:27:17AM -0500, Richard Kuhns wrote: >> On 11/16/12 11:20, Gary Palmer wrote: >>> On Fri, Nov 16, 2012 at 10:54:00AM -0500, Richard Kuhns wrote: >>>> On 11/16/12 10:41, Alfred Perlstein wrote: >>>>> Often that is all that is needed. It's worth a shot and reporting back. >>>>> >>>>> Do you know how to update the table in the driver, rebuild/install >>>>> kernel and check? >>>>> >>>>> -Alfred >>>>> >>>> >>>> I'm afraid not. I grepped for the hex value reported on the one that works >>>> (chip=0x16b414e4), but I couldn't find it in its entirety, 16b4, or 14e4. So I >>>> don't know what to add :-( >>>> >>>> I don't have any problem with rebuilding and installing a new kernel, though. >>> >>> 14e4 is the ID for Broadcom >>> 16b4 is the ID for BCM57765, a NetXtreme Desktop/Mobile chip >>> >>> http://www.broadcom.com/support/ethernet_nic/determine_driver.php has a list >>> of the BCM PCI ID values >>> >>> There is a (frequently incomplete) database of user reported PCI values at >>> http://www.pcidatabase.com. It has the BCM ID (14e4), but not your chip >>> >>> Linux uses the tg3 driver for that chipset apparently, but I think thats >>> a general dumping ground for a lot of Broadcom products. Not sure what the >>> appropriate FreeBSD driver to add the ID code to would be. >>> >>> Regards, >>> >>> Gary >>> >> >> Sorry, I should have been more clear. I grepped for those values in >> /usr/src/sys/dev/bge/*, since that's the driver that's used on the older minis. >> I assume that's where the table is that Alfred mentioned; I just don't know what >> to add to it. >> > > The probe table appears to be bge_devs in if_bge.c. The values there are > #define'd in if_bgereg.h, but for a quick hack you just need to add the value > to the table > > Gary > Thanks, I found it. I also found that the reason I couldn't find it before was that I didn't tell grep to ignore case :-( -- Richard Kuhns My Desk: 765-269-8541 Wintek Corporation Internet Support: 765-269-8503 427 N 6th Street Consulting: 765-269-8504 Lafayette, IN 47901-2211 Accounting: 765-269-8502 From owner-freebsd-stable@FreeBSD.ORG Fri Nov 16 23:39:26 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BC99A63; Fri, 16 Nov 2012 23:39:26 +0000 (UTC) (envelope-from prvs=1667f8fa28=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B98BA8FC08; Fri, 16 Nov 2012 23:39:25 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001083906.msg; Fri, 16 Nov 2012 23:39:17 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Fri, 16 Nov 2012 23:39:17 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1667f8fa28=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <5AD5215CCD2D4693B211A4F6D076987D@multiplay.co.uk> From: "Steven Hartland" To: "Doug Ambrisko" References: <2DC1C56CFFF24FE0B17C34AD21A7DFAA@multiplay.co.uk> <39D16C43C8274CE9B8F23C18459E2FD4@multiplay.co.uk> <20121105212911.GA17904@ambrisko.com> <27169C7FE704495087A093752D15E7B6@multiplay.co.uk> <20121106180152.GA40422@ambrisko.com> <6B5B65F4FC854EB8BBC701500096602E@multiplay.co.uk> <0B4E8AFF9DA04C6EBD2496A8B58F1D67@multiplay.co.uk> <20121109172508.GA13333@ambrisko.com> <6A9D5119A4774E8C8C8E0427035FC05B@multiplay.co.uk> Subject: Re: mfi panic on recused on non-recusive mutex MFI I/O lock Date: Fri, 16 Nov 2012 23:39:18 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2012 23:39:26 -0000 ----- Original Message ----- From: "Steven Hartland" >> Sounds like you have made some good progress. I looked at your prior locking >> change and they good. Haven't had time to go through the queue changes >> yet. > > Just to update people on this, as its taken quite some time to track down the > random issues causing panics, but I believe I made a breakthrough last night. > > It seems that the cleanup interation between mfi_cmd's and tbolt_cmd's is flawed > meaning its possible that tbolt commands are processed after the caller has > already recieved a response, cleaned and returned the mfi_cmd to the free queue. > > This means that its anyones guess what the result of the tbolt cleanup is as it > could well be operating on a mfi_cmd thats either now in the free queue or even > worse has already been reused. > > It also possible this was the underling issue you may well have seening which > caused you to add the mfi_tbolt_complete_cmd calls to mfi_tbolt_send_frame > in r242681. > > If this is correct then I believe the correct fix is to ensure that > mfi_tbolt_return_cmd is only ever called from mfi_release_command thus ensuring > completion ordering is always correct. I'm testing fixes for this theory now > but initial debug has had good results. > > The patch of fixes is really growing, so definitely going to need someone to > review in detail when I'm done. > > What do you think of the above, does it make sence? Would you be willing to > review the patch when I'm done, before I commit it Doug? Ok I think I'm done. The good news is I've managed to fix all panics and cases of commands being processed incorrectly that we've seen here. The bad news is the patch is now really quite large as there was a lot if issues found during debugging of the core problems. The main fixes are:- 1. Ensure that IO lock is not dropped during tbolt ISR processing, as this can cause some very nasty issues when two threads end up processing the same tbolt cmd. 2. Ensure that interaction between mfi_cmd's and tbolt_cmd's, specifically in their cleanup, total number and range checks as if this isn't done then again some very nasty issues can occur. 3. Ensure that tbolt init doesn't break MFI indexing by assuming it always gets the first mfi command structure. The reset of the fixes are for things like potential NULL pointer exceptions, locks not being dropped during error cases etc. Full details of all the fixes are in the patch which can be found here:- http://blog.multiplay.co.uk/dropzone/freebsd/zz-mfi-queue.patch It should be noted that while the changes now make the driver functionally correct, the promotion of the IO lock to the upper layers isn't ideal and could do with optimising. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Sat Nov 17 06:41:34 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79022845; Sat, 17 Nov 2012 06:41:34 +0000 (UTC) (envelope-from wkoszek@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [212.87.224.105]) by mx1.freebsd.org (Postfix) with ESMTP id ECE108FC08; Sat, 17 Nov 2012 06:41:33 +0000 (UTC) Received: from freebsd.czest.pl (freebsd.czest.pl [212.87.224.105]) by freebsd.czest.pl (8.14.5/8.14.5) with ESMTP id qAH6Uku7043511; Sat, 17 Nov 2012 06:30:46 GMT (envelope-from wkoszek@freebsd.czest.pl) Received: (from wkoszek@localhost) by freebsd.czest.pl (8.14.5/8.14.5/Submit) id qAH6Ukrs043510; Sat, 17 Nov 2012 06:30:46 GMT (envelope-from wkoszek) Date: Sat, 17 Nov 2012 06:30:46 +0000 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: [Not this year] Re: FreeBSD in Google Code-In 2012? You can help too! Message-ID: <20121117063046.GN59689@FreeBSD.org> References: <20121016101957.GB53800@FreeBSD.org> <20121102201318.GI59689@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20121102201318.GI59689@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (freebsd.czest.pl [212.87.224.105]); Sat, 17 Nov 2012 06:30:46 +0000 (UTC) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Nov 2012 06:41:34 -0000 On Fri, Nov 02, 2012 at 08:13:18PM +0000, Wojciech A. Koszek wrote: > On Tue, Oct 16, 2012 at 10:19:57AM +0000, Wojciech A. Koszek wrote: > > (cross-posted message; please keep discussion on freebsd-hackers@) > > > > Hello, > > > > Last year FreeBSD qualified for Google Code-In 2011 event--contest for > > youngest open-source hackers in 13-17yr age range: > > > > http://www.google-melange.com/gci/homepage/google/gci2012 > > > > It was successful. We gained one more FreeBSD developer thanks to that > > (Isabell Long) We're pondering participating in the contest this year as > > well. > > > > For now we only have 25 ideas. We need at least 100. > > > > I felt all members of the FreeBSD community should help, so please submit > > your own Google Code-In 2012 ideas here: > > > > http://www.emailmeform.com/builder/form/4aU93Obxo4NYdVAgb1 > > > > Examples of previously completed tasks: > > > > http://wiki.freebsd.org/GoogleCodeIn/2011Tasks > > > > Those of you who have Wiki access, please spent 2 more minutes and submit > > straight to Wiki: > > > > http://wiki.freebsd.org/GoogleCodeIn/2012Tasks > > > > I plan to send out next e-mail if there's any progress on this project. > > > > Help will be appreciated. > > Hello, > > This is last call for action. > > As for now, we won't qualify. I suggest doc@ and ports@ and www@ and src@ > teams to try to come up with some ideas and add them to Wiki. Most of the > ideas which we have so far are more GSOC-alike. > > Unless we have at least 80 tasks of the "easy"/"medium" type, we'll have to > postpone participating in Code-In for next year. > > Thanks, Hello, We didn't make it this year. I want to thank all the people who submitted (and keep submitting) ideas for our Google Code-In wiki page: http://wiki.freebsd.org/GoogleCodeIn/2012Tasks In total I got 61 ideas over e-mail from the web form (lessons learnt: for GSOC, we should also have a web form) All of them should be on the Wiki now. I suggest we keep collecting good ideas and try to make sure this years GSOC will be successful. On the other note--NetBSD guys are in Google Code-In.. Thanks, -- Wojciech A. Koszek wkoszek@FreeBSD.czest.pl http://FreeBSD.czest.pl/~wkoszek/ From owner-freebsd-stable@FreeBSD.ORG Sat Nov 17 19:26:49 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 755CBCC3 for ; Sat, 17 Nov 2012 19:26:49 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp.eutelia.it (mp1-smtp-5.eutelia.it [62.94.10.165]) by mx1.freebsd.org (Postfix) with ESMTP id 113AF8FC0C for ; Sat, 17 Nov 2012 19:26:47 +0000 (UTC) Received: from ns2.biolchim.it (ip-188-188.sn2.eutelia.it [83.211.188.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.eutelia.it (Eutelia) with ESMTP id 3287C14A503 for ; Sat, 17 Nov 2012 20:01:20 +0100 (CET) Received: from soth.ventu (adsl-ull-38-163.41-151.net24.it [151.41.163.38]) (authenticated bits=0) by ns2.biolchim.it (8.14.5/8.14.5) with ESMTP id qAHJ19th065007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Sat, 17 Nov 2012 20:01:11 +0100 (CET) (envelope-from ml@netfence.it) Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.5/8.14.5) with ESMTP id qAHJ0tuq016457 for ; Sat, 17 Nov 2012 20:00:55 +0100 (CET) (envelope-from ml@netfence.it) Message-ID: <50A7DEE7.8090802@netfence.it> Date: Sat, 17 Nov 2012 20:00:55 +0100 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: confirm that csup is still usable fos the new 9.1 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 X-Scanned-By: MIMEDefang 2.73 on 10.1.2.13 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns2.biolchim.it [192.168.2.203]); Sat, 17 Nov 2012 20:01:11 +0100 (CET) X-Spam-Score: 5.627 (*****) BAYES_20, RCVD_IN_PBL, RCVD_IN_RP_RNBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Nov 2012 19:26:49 -0000 On 11/16/12 18:08, Eitan Adler wrote: > There are known problems with the cluster at this time. The machines > were recently moved, upgraded, and generally manipulated. We are > working to fix this as fast as possible. Looks like everything is back up again. Thanks for the good work. bye av. From owner-freebsd-stable@FreeBSD.ORG Sat Nov 17 20:04:57 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA690DD6 for ; Sat, 17 Nov 2012 20:04:57 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 679DE8FC0C for ; Sat, 17 Nov 2012 20:04:56 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so1878601eaa.13 for ; Sat, 17 Nov 2012 12:04:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u9S/d/vgk5qFo4isUcPPZ60xyH2+REA6/TtHeTDx8Vg=; b=Nw2QL/foTcR+YCUN//JItD1yxrST7fUdTwTFOiU6og0yPbL/GRdjJEBI900e/NjgEg vKLGSbn4ecVQOryZbhpTzLlQkuQr/djPJ4a4m66621ZaIlu40b9Dz5Q3/tgARF4YR3q4 +Ua9ZqXv7JDdSZhl/Wa8wl5Ns/fPmz6Dpn78CI3UCKOt8SHEoIPbHmDp0Cq85vY5b1wr m9niI6mLQ0u3QDf5/jFlxIfbCFeqLa9qwxweO5/ogcUgdIIQfWCqZbT9n8p2zpZuOVtu znoTZHcv4QRMxikS/KFXc7TwwD9y01dCOby9MPWxQlJh/vIYsEoKaiJwf61elCxkRbm/ bovA== MIME-Version: 1.0 Received: by 10.14.175.198 with SMTP id z46mr8874742eel.26.1353182696163; Sat, 17 Nov 2012 12:04:56 -0800 (PST) Received: by 10.223.71.199 with HTTP; Sat, 17 Nov 2012 12:04:56 -0800 (PST) In-Reply-To: <50A7DEE7.8090802@netfence.it> References: <50A7DEE7.8090802@netfence.it> Date: Sat, 17 Nov 2012 12:04:56 -0800 Message-ID: Subject: Re: confirm that csup is still usable fos the new 9.1 From: Kevin Oberman To: Andrea Venturoli Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Nov 2012 20:04:58 -0000 On Sat, Nov 17, 2012 at 11:00 AM, Andrea Venturoli wrote: > On 11/16/12 18:08, Eitan Adler wrote: > >> There are known problems with the cluster at this time. The machines >> were recently moved, upgraded, and generally manipulated. We are >> working to fix this as fast as possible. > > > Looks like everything is back up again. > Thanks for the good work. Yes, but don't bet that csup and cvs will be around long. The outage was the result of an intrusion into core FreeBSD systems. Please read the posting at http://www.freebsd.org/news/2012-compromise.html. It's really time to get away from CVS and I suspect it will be going away sooner than had been planned. I notice that no response has confirmed whether it will be available for 9.1, probably because the security team is still evaluating the situation. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com