From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 00:26:55 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B05AD89; Sun, 18 Nov 2012 00:26:55 +0000 (UTC) (envelope-from bartosz.stec@it4pro.pl) Received: from mainframe.kkip.pl (kkip.pl [78.9.102.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9978FC0C; Sun, 18 Nov 2012 00:26:54 +0000 (UTC) Received: from 89-69-114-93.dynamic.chello.pl ([89.69.114.93] helo=[192.168.0.100]) by mainframe.kkip.pl with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TZsij-000I4n-0C; Sun, 18 Nov 2012 01:26:52 +0100 Message-ID: <50A82B3A.6020608@it4pro.pl> Date: Sun, 18 Nov 2012 01:26:34 +0100 From: Bartosz Stec Organization: IT4Pro User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: problem booting to multi-vdev root pool [Was: kern/150503: [zfs] ZFS disks are UNAVAIL and corrupted after reboot] References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66701.701@madpilot.net> In-Reply-To: <50A66701.701@madpilot.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: bartosz.stec@it4pro.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.1 X-Spam-Score-Int: -80 X-Exim-Version: 4.80.1 (build at 26-Oct-2012 17:04:45) X-Date: 2012-11-18 01:26:52 X-Connected-IP: 89.69.114.93:51865 X-Message-Linecount: 72 X-Body-Linecount: 56 X-Message-Size: 2349 X-Body-Size: 1578 X-Received-Count: 1 X-Recipient-Count: 4 X-Local-Recipient-Count: 4 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Guido Falsi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 00:26:55 -0000 W dniu 2012-11-16 17:17, Guido Falsi pisze: > On 11/16/12 16:45, Andriy Gapon wrote: >> on 13/11/2012 18:16 Guido Falsi said the following: >>> My idea, but is just a speculation, i could be very wrong, is that >>> the geom >>> tasting code has some problem with multiple vdev root pools. >> >> Guido, >> >> you are absolutely correct. The code for reconstructing/tasting a >> root pool >> configuration is a modified upstream code, so it inherited a >> limitation from it: >> the support for only a single top-level vdev in a root pool. >> I have an idea how to add the missing support, but it turned out not >> to be >> something that I can hack together in couple of hours. > > I can imagine, it does not look simple in any way! > >> >> So, instead I wrote the following patch that should fall back to >> using a root pool >> configuration from zpool.cache (if it's present there) for a >> multi-vdev root pool: >> http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_fallback.diff >> >> The patch also fixes a minor (single-time) memory leak. >> >> Guido, Bartosz, >> could you please test the patch? > > I have just compiler an r242910 kernel with this patch (and just this > one) applied. > > System booted so it seems to work fine! :) I've just compiled and installed fresh kernel with your patch, system booted without any problems, so apparently patch works as intended. Good job Andriy! > >> >> Apologies for the breakage. >> > > No worries, and thanks for this fix. > > Also thanks for all the work on ZFS! > Make it twice :) Regards, -- Bartosz Stec From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 01:24:18 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2509E2CE; Sun, 18 Nov 2012 01:24:18 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E2D7D8FC08; Sun, 18 Nov 2012 01:24:17 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAI1OH6T015871; Sat, 17 Nov 2012 20:24:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAI1OGIJ015851; Sun, 18 Nov 2012 01:24:16 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 01:24:16 GMT Message-Id: <201211180124.qAI1OGIJ015851@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 01:24:18 -0000 TB --- 2012-11-17 21:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-17 21:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-17 21:10:01 - starting HEAD tinderbox run for i386/i386 TB --- 2012-11-17 21:10:01 - cleaning the object tree TB --- 2012-11-17 21:10:01 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-17 21:10:01 - cd /tinderbox/HEAD/i386/i386 TB --- 2012-11-17 21:10:01 - /usr/local/bin/svn cleanup /src TB --- 2012-11-17 21:13:30 - /usr/local/bin/svn update /src TB --- 2012-11-17 21:13:55 - At svn revision 243187 TB --- 2012-11-17 21:13:56 - building world TB --- 2012-11-17 21:13:56 - CROSS_BUILD_TESTING=YES TB --- 2012-11-17 21:13:56 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-17 21:13:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-17 21:13:56 - SRCCONF=/dev/null TB --- 2012-11-17 21:13:56 - TARGET=i386 TB --- 2012-11-17 21:13:56 - TARGET_ARCH=i386 TB --- 2012-11-17 21:13:56 - TZ=UTC TB --- 2012-11-17 21:13:56 - __MAKE_CONF=/dev/null TB --- 2012-11-17 21:13:56 - cd /src TB --- 2012-11-17 21:13:56 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sat Nov 17 21:14:05 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 18 00:12:05 UTC 2012 TB --- 2012-11-18 00:12:05 - generating LINT kernel config TB --- 2012-11-18 00:12:05 - cd /src/sys/i386/conf TB --- 2012-11-18 00:12:05 - /usr/bin/make -B LINT TB --- 2012-11-18 00:12:05 - cd /src/sys/i386/conf TB --- 2012-11-18 00:12:05 - /usr/sbin/config -m LINT TB --- 2012-11-18 00:12:05 - building LINT kernel TB --- 2012-11-18 00:12:05 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 00:12:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 00:12:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 00:12:05 - SRCCONF=/dev/null TB --- 2012-11-18 00:12:05 - TARGET=i386 TB --- 2012-11-18 00:12:05 - TARGET_ARCH=i386 TB --- 2012-11-18 00:12:05 - TZ=UTC TB --- 2012-11-18 00:12:05 - __MAKE_CONF=/dev/null TB --- 2012-11-18 00:12:05 - cd /src TB --- 2012-11-18 00:12:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 18 00:12:05 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sun Nov 18 00:43:28 UTC 2012 TB --- 2012-11-18 00:43:28 - cd /src/sys/i386/conf TB --- 2012-11-18 00:43:28 - /usr/sbin/config -m LINT-NOINET TB --- 2012-11-18 00:43:28 - building LINT-NOINET kernel TB --- 2012-11-18 00:43:28 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 00:43:28 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 00:43:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 00:43:28 - SRCCONF=/dev/null TB --- 2012-11-18 00:43:28 - TARGET=i386 TB --- 2012-11-18 00:43:28 - TARGET_ARCH=i386 TB --- 2012-11-18 00:43:28 - TZ=UTC TB --- 2012-11-18 00:43:28 - __MAKE_CONF=/dev/null TB --- 2012-11-18 00:43:28 - cd /src TB --- 2012-11-18 00:43:28 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET >>> Kernel build for LINT-NOINET started on Sun Nov 18 00:43:28 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT-NOINET completed on Sun Nov 18 01:11:20 UTC 2012 TB --- 2012-11-18 01:11:20 - cd /src/sys/i386/conf TB --- 2012-11-18 01:11:20 - /usr/sbin/config -m LINT-NOINET6 TB --- 2012-11-18 01:11:20 - building LINT-NOINET6 kernel TB --- 2012-11-18 01:11:20 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 01:11:20 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 01:11:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 01:11:20 - SRCCONF=/dev/null TB --- 2012-11-18 01:11:20 - TARGET=i386 TB --- 2012-11-18 01:11:20 - TARGET_ARCH=i386 TB --- 2012-11-18 01:11:20 - TZ=UTC TB --- 2012-11-18 01:11:20 - __MAKE_CONF=/dev/null TB --- 2012-11-18 01:11:20 - cd /src TB --- 2012-11-18 01:11:20 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET6 >>> Kernel build for LINT-NOINET6 started on Sun Nov 18 01:11:20 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg /src/sys/net/raw_cb.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg /src/sys/net/raw_usrreq.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg /src/sys/net/route.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg /src/sys/net/rtsock.c /src/sys/net/rtsock.c:1577:6: error: unused variable 'i' [-Werror,-Wunused-variable] int i; ^ 1 error generated. *** [rtsock.o] Error code 1 Stop in /obj/i386.i386/src/sys/LINT-NOINET6. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 01:24:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 01:24:16 - ERROR: failed to build LINT-NOINET6 kernel TB --- 2012-11-18 01:24:16 - 11008.79 user 2042.29 system 15255.70 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 17 23:13:49 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89335C33; Sat, 17 Nov 2012 23:13:49 +0000 (UTC) (envelope-from vijju.singh@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 1C67F8FC08; Sat, 17 Nov 2012 23:13:48 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id x2so3255307iad.13 for ; Sat, 17 Nov 2012 15:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=0vAbS1fimPPUkbq4dodbUJI/vliWdMN5stgTfMhfY9M=; b=zWmCnGdiBineyN26MaNo2bHycdlYCs/VmU4HzYEe4Gjkx2TQAKkzvvU2eD5QlOaSZu fGkVjSEWX+TFSLwLLxXe54mpFf2xocZ6en83AW96QAVyq/5eC/Psbv24d6WieRTFoVie yMJnpDokFWOX/Nk60jpRq4vAKdxBHPyZFho79Lk2avtHpAKfDH4ehZq8AYmzcqRcRtG2 V/hmRnfQ/DudfDZtp9PVSfwLYlpRNEu8Yt7lHRVn4JIg5YvSElXMcH9bAm4efa8D+lvi x+odgWo9tZXENkxX1jsaF7mztEjSGC62oY6nbsKCtEFgoo+Gq1n+vmayxIudX6AFjvxh BoVA== Received: by 10.50.37.196 with SMTP id a4mr3047999igk.16.1353194028332; Sat, 17 Nov 2012 15:13:48 -0800 (PST) Received: from [192.168.1.64] (108-64-226-69.lightspeed.sntcca.sbcglobal.net. [108.64.226.69]) by mx.google.com with ESMTPS id u4sm3914586igw.6.2012.11.17.15.13.44 (version=SSLv3 cipher=OTHER); Sat, 17 Nov 2012 15:13:46 -0800 (PST) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <55449D50-389B-4080-9B6F-A7CC0C0A2D1E@gmail.com> X-Mailer: iPhone Mail (10A523) From: Vijay Singh Subject: Re: netisr panic? Date: Sat, 17 Nov 2012 15:13:41 -0800 To: Robert Watson X-Mailman-Approved-At: Sun, 18 Nov 2012 01:56:34 +0000 Cc: FreeBSD Net , Adrian Chadd , Ian FREISLICH , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Nov 2012 23:13:49 -0000 Or cluster allocation failed, and only the mbuf was used. Sent from my iPhone On Nov 17, 2012, at 1:31 PM, Robert Watson wrote: > Panics along these lines often occur if there is a concurrency bug in a de= vice driver such that it modifies an mbuf after dispatching to the network s= tack. E.g., by freeing it, reusing it, an errant dereference, etc. Not guar= anteed, but that is where I'd start. >=20 > Robert >=20 > On Sat, 17 Nov 2012, Adrian Chadd wrote: >=20 >> Check what mtod() is doing. >>=20 >> mbuf.h:#define mtod(m, t) ((t)((m)->m_data)) >>=20 >> .. so if m->m_data is NULL, bam. >>=20 >> The question is why is m_data NULL here. Someone mbuf cluey is going >> to have to answer that. I don't know whether the MH_dat stuff is being >> treated as valid but m_data isn't being updated, or something. >>=20 >>=20 >> Adrian >>=20 >> On 17 November 2012 10:13, Ian FREISLICH wrote: >>> Adrian Chadd wrote: >>>> It's a NULL ponter deref. This is my line 484 in if_ethersubr.c: >>>>=20 >>>> eh =3D mtod(m, struct ether_header *); >>>>=20 >>>>=20 >>>> .. if that's yours, see if eh is NULL? >>>=20 >>> (kgdb) frame 7 >>> #7 0xffffffff8050f534 in ether_nh_input (m=3D0xfffffe012521e700) >>> at /usr/src/sys/net/if_ethersubr.c:484 >>> 484 eh =3D mtod(m, struct ether_header *); >>> (kgdb) print eh >>> No symbol "eh" in current context. >>> (kgdb) print *m >>> $2 =3D {m_hdr =3D {mh_next =3D 0x100000000000000, mh_nextpkt =3D 0x10000= 000000, >>> mh_data =3D 0x0, mh_len =3D 60, mh_flags =3D 4259842, mh_type =3D 0, >>> pad =3D "\000\000\000\000\000"}, M_dat =3D {MH =3D {MH_pkthdr =3D { >>> rcvif =3D 0xfffffe000a1c2000, header =3D 0xffffffff, len =3D 60, f= lowid =3D 0, >>> csum_flags =3D 3840, csum_data =3D 65535, tso_segsz =3D 0, PH_vt =3D= { >>> vt_vtag =3D 4, vt_nrecs =3D 4}, tags =3D {slh_first =3D 0x3c000= 000}}, >>> MH_dat =3D {MH_ext =3D { >>> ext_buf =3D 0x69e5498600000000
, ext_free =3D 0x10602, ext_arg1 =3D 0xc000000070000, ext_arg2 =3D 0= x100, >>> ext_size =3D 2048, ref_cnt =3D 0xfffffe0125236d8c, ext_type =3D= 6}, >>> MH_databuf =3D "\000\000\000\000\206I=D0=B5i\002\006\001\000\000\= 000\000\000\000\000\a\000\000\000\f\000\000\001\000\000\000\000\000\000\000\= b\000\000\000\000\000\000\214m#%\001=D1=8E=D1=8F=D1=8F\006", '\0' }}, >>> M_databuf =3D "\000 \034\n\000=D1=8E=D1=8F=D1=8F=D1=8F=D1=8F=D1=8F=D1= =8F\000\000\000\000<\000\000\000\000\000\000\000\000\017\000\000=D1=8F=D1=8F= \000\000\000\000\004\000\000\000\000\000\000\000\000<\000\000\000\000\000\00= 0\000\000\206I=D0=B5i\002\006\001\000\000\000\000\000\000\000\a\000\000\000\= f\000\000\001\000\000\000\000\000\000\000\b\000\000\000\000\000\000\214m#%\0= 01=D1=8E=D1=8F=D1=8F\006", '\0' }} >>>=20 >>>=20 >>> Ian >>>=20 >>> -- >>> Ian Freislich >>>=20 >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 02:00:00 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30AE1CD2; Sun, 18 Nov 2012 02:00:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id DF17E8FC0C; Sun, 18 Nov 2012 01:59:59 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAI1xwQQ041100; Sat, 17 Nov 2012 20:59:58 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAI1xwLd041095; Sun, 18 Nov 2012 01:59:58 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 01:59:58 GMT Message-Id: <201211180159.qAI1xwLd041095@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 02:00:00 -0000 TB --- 2012-11-17 21:10:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-17 21:10:01 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-17 21:10:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2012-11-17 21:10:01 - cleaning the object tree TB --- 2012-11-17 21:10:01 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-17 21:10:01 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2012-11-17 21:10:01 - /usr/local/bin/svn cleanup /src TB --- 2012-11-17 21:13:55 - /usr/local/bin/svn update /src TB --- 2012-11-17 21:14:12 - At svn revision 243187 TB --- 2012-11-17 21:14:13 - building world TB --- 2012-11-17 21:14:13 - CROSS_BUILD_TESTING=YES TB --- 2012-11-17 21:14:13 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-17 21:14:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-17 21:14:13 - SRCCONF=/dev/null TB --- 2012-11-17 21:14:13 - TARGET=amd64 TB --- 2012-11-17 21:14:13 - TARGET_ARCH=amd64 TB --- 2012-11-17 21:14:13 - TZ=UTC TB --- 2012-11-17 21:14:13 - __MAKE_CONF=/dev/null TB --- 2012-11-17 21:14:13 - cd /src TB --- 2012-11-17 21:14:13 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sat Nov 17 21:14:20 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sun Nov 18 00:48:34 UTC 2012 TB --- 2012-11-18 00:48:34 - generating LINT kernel config TB --- 2012-11-18 00:48:34 - cd /src/sys/amd64/conf TB --- 2012-11-18 00:48:34 - /usr/bin/make -B LINT TB --- 2012-11-18 00:48:34 - cd /src/sys/amd64/conf TB --- 2012-11-18 00:48:34 - /usr/sbin/config -m LINT TB --- 2012-11-18 00:48:34 - building LINT kernel TB --- 2012-11-18 00:48:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 00:48:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 00:48:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 00:48:34 - SRCCONF=/dev/null TB --- 2012-11-18 00:48:34 - TARGET=amd64 TB --- 2012-11-18 00:48:34 - TARGET_ARCH=amd64 TB --- 2012-11-18 00:48:34 - TZ=UTC TB --- 2012-11-18 00:48:34 - __MAKE_CONF=/dev/null TB --- 2012-11-18 00:48:34 - cd /src TB --- 2012-11-18 00:48:34 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 18 00:48:35 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sun Nov 18 01:19:10 UTC 2012 TB --- 2012-11-18 01:19:10 - cd /src/sys/amd64/conf TB --- 2012-11-18 01:19:10 - /usr/sbin/config -m LINT-NOINET TB --- 2012-11-18 01:19:10 - building LINT-NOINET kernel TB --- 2012-11-18 01:19:10 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 01:19:10 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 01:19:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 01:19:10 - SRCCONF=/dev/null TB --- 2012-11-18 01:19:10 - TARGET=amd64 TB --- 2012-11-18 01:19:10 - TARGET_ARCH=amd64 TB --- 2012-11-18 01:19:10 - TZ=UTC TB --- 2012-11-18 01:19:10 - __MAKE_CONF=/dev/null TB --- 2012-11-18 01:19:10 - cd /src TB --- 2012-11-18 01:19:10 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET >>> Kernel build for LINT-NOINET started on Sun Nov 18 01:19:10 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT-NOINET completed on Sun Nov 18 01:47:27 UTC 2012 TB --- 2012-11-18 01:47:27 - cd /src/sys/amd64/conf TB --- 2012-11-18 01:47:27 - /usr/sbin/config -m LINT-NOINET6 TB --- 2012-11-18 01:47:27 - building LINT-NOINET6 kernel TB --- 2012-11-18 01:47:27 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 01:47:27 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 01:47:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 01:47:27 - SRCCONF=/dev/null TB --- 2012-11-18 01:47:27 - TARGET=amd64 TB --- 2012-11-18 01:47:27 - TARGET_ARCH=amd64 TB --- 2012-11-18 01:47:27 - TZ=UTC TB --- 2012-11-18 01:47:27 - __MAKE_CONF=/dev/null TB --- 2012-11-18 01:47:27 - cd /src TB --- 2012-11-18 01:47:27 - /usr/bin/make -B buildkernel KERNCONF=LINT-NOINET6 >>> Kernel build for LINT-NOINET6 started on Sun Nov 18 01:47:27 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/net/raw_cb.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/net/raw_usrreq.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/net/route.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/net/rtsock.c /src/sys/net/rtsock.c:1577:6: error: unused variable 'i' [-Werror,-Wunused-variable] int i; ^ 1 error generated. *** [rtsock.o] Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT-NOINET6. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 01:59:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 01:59:58 - ERROR: failed to build LINT-NOINET6 kernel TB --- 2012-11-18 01:59:58 - 12205.13 user 2392.52 system 17397.67 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 02:06:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77AE5E47; Sun, 18 Nov 2012 02:06:08 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 368638FC0C; Sun, 18 Nov 2012 02:06:07 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAI2676c068910; Sat, 17 Nov 2012 21:06:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAI267cR068907; Sun, 18 Nov 2012 02:06:07 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 02:06:07 GMT Message-Id: <201211180206.qAI267cR068907@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 02:06:08 -0000 TB --- 2012-11-18 00:56:08 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 00:56:08 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 00:56:08 - starting HEAD tinderbox run for mips/mips TB --- 2012-11-18 00:56:09 - cleaning the object tree TB --- 2012-11-18 00:56:09 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 00:56:09 - cd /tinderbox/HEAD/mips/mips TB --- 2012-11-18 00:56:09 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 00:57:11 - /usr/local/bin/svn update /src TB --- 2012-11-18 00:57:18 - At svn revision 243203 TB --- 2012-11-18 00:57:19 - building world TB --- 2012-11-18 00:57:19 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 00:57:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 00:57:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 00:57:19 - SRCCONF=/dev/null TB --- 2012-11-18 00:57:19 - TARGET=mips TB --- 2012-11-18 00:57:19 - TARGET_ARCH=mips TB --- 2012-11-18 00:57:19 - TZ=UTC TB --- 2012-11-18 00:57:19 - __MAKE_CONF=/dev/null TB --- 2012-11-18 00:57:19 - cd /src TB --- 2012-11-18 00:57:19 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 00:57:25 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 18 02:03:47 UTC 2012 TB --- 2012-11-18 02:03:47 - cd /src/sys/mips/conf TB --- 2012-11-18 02:03:47 - /usr/sbin/config -m ADM5120 TB --- 2012-11-18 02:03:47 - skipping ADM5120 kernel TB --- 2012-11-18 02:03:47 - cd /src/sys/mips/conf TB --- 2012-11-18 02:03:47 - /usr/sbin/config -m ALCHEMY TB --- 2012-11-18 02:03:47 - skipping ALCHEMY kernel TB --- 2012-11-18 02:03:47 - cd /src/sys/mips/conf TB --- 2012-11-18 02:03:47 - /usr/sbin/config -m AP91 TB --- 2012-11-18 02:03:47 - building AP91 kernel TB --- 2012-11-18 02:03:47 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:03:47 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:03:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:03:47 - SRCCONF=/dev/null TB --- 2012-11-18 02:03:47 - TARGET=mips TB --- 2012-11-18 02:03:47 - TARGET_ARCH=mips TB --- 2012-11-18 02:03:47 - TZ=UTC TB --- 2012-11-18 02:03:47 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:03:47 - cd /src TB --- 2012-11-18 02:03:47 - /usr/bin/make -B buildkernel KERNCONF=AP91 >>> Kernel build for AP91 started on Sun Nov 18 02:03:47 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=768 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x80050000 -march=mips32 -msoft-float -ffreestanding -Werror /src/sys/net/radix_mpath.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=768 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x80050000 -march=mips32 -msoft-float -ffreestanding -Werror /src/sys/net/raw_cb.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=768 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x80050000 -march=mips32 -msoft-float -ffreestanding -Werror /src/sys/net/raw_usrreq.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=768 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x80050000 -march=mips32 -msoft-float -ffreestanding -Werror /src/sys/net/route.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=768 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x80050000 -march=mips32 -msoft-float -ffreestanding -Werror /src/sys/net/rtsock.c cc1: warnings being treated as errors /src/sys/net/rtsock.c: In function 'sysctl_dumpentry': /src/sys/net/rtsock.c:1577: warning: unused variable 'i' [-Wunused-variable] *** [rtsock.o] Error code 1 Stop in /obj/mips.mips/src/sys/AP91. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 02:06:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 02:06:07 - ERROR: failed to build AP91 kernel TB --- 2012-11-18 02:06:07 - 2726.96 user 667.90 system 4198.44 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 02:35:18 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 587AA2B6; Sun, 18 Nov 2012 02:35:18 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 037A98FC08; Sun, 18 Nov 2012 02:35:14 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAI2ZD4x022587; Sat, 17 Nov 2012 21:35:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAI2ZDql022583; Sun, 18 Nov 2012 02:35:13 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 02:35:13 GMT Message-Id: <201211180235.qAI2ZDql022583@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips64/mips Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 02:35:18 -0000 TB --- 2012-11-18 01:02:49 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 01:02:49 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 01:02:49 - starting HEAD tinderbox run for mips64/mips TB --- 2012-11-18 01:02:49 - cleaning the object tree TB --- 2012-11-18 01:02:49 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 01:02:49 - cd /tinderbox/HEAD/mips64/mips TB --- 2012-11-18 01:02:49 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 01:04:14 - /usr/local/bin/svn update /src TB --- 2012-11-18 01:04:21 - At svn revision 243203 TB --- 2012-11-18 01:04:22 - building world TB --- 2012-11-18 01:04:22 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 01:04:22 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 01:04:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 01:04:22 - SRCCONF=/dev/null TB --- 2012-11-18 01:04:22 - TARGET=mips TB --- 2012-11-18 01:04:22 - TARGET_ARCH=mips64 TB --- 2012-11-18 01:04:22 - TZ=UTC TB --- 2012-11-18 01:04:22 - __MAKE_CONF=/dev/null TB --- 2012-11-18 01:04:22 - cd /src TB --- 2012-11-18 01:04:22 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 01:04:27 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 18 02:14:32 UTC 2012 TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m ADM5120 TB --- 2012-11-18 02:14:32 - skipping ADM5120 kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m ALCHEMY TB --- 2012-11-18 02:14:32 - skipping ALCHEMY kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AP91 TB --- 2012-11-18 02:14:32 - skipping AP91 kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AP93 TB --- 2012-11-18 02:14:32 - skipping AP93 kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AP94 TB --- 2012-11-18 02:14:32 - skipping AP94 kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AP96 TB --- 2012-11-18 02:14:32 - skipping AP96 kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AR71XX_BASE TB --- 2012-11-18 02:14:32 - skipping AR71XX_BASE kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AR724X_BASE TB --- 2012-11-18 02:14:32 - skipping AR724X_BASE kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m AR91XX_BASE TB --- 2012-11-18 02:14:32 - skipping AR91XX_BASE kernel TB --- 2012-11-18 02:14:32 - cd /src/sys/mips/conf TB --- 2012-11-18 02:14:32 - /usr/sbin/config -m BERI_DE4_MDROOT TB --- 2012-11-18 02:14:32 - building BERI_DE4_MDROOT kernel TB --- 2012-11-18 02:14:32 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:14:32 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:14:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:14:32 - SRCCONF=/dev/null TB --- 2012-11-18 02:14:32 - TARGET=mips TB --- 2012-11-18 02:14:32 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:14:32 - TZ=UTC TB --- 2012-11-18 02:14:32 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:14:32 - cd /src TB --- 2012-11-18 02:14:32 - /usr/bin/make -B buildkernel KERNCONF=BERI_DE4_MDROOT >>> Kernel build for BERI_DE4_MDROOT started on Sun Nov 18 02:14:32 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for BERI_DE4_MDROOT completed on Sun Nov 18 02:17:04 UTC 2012 TB --- 2012-11-18 02:17:04 - cd /src/sys/mips/conf TB --- 2012-11-18 02:17:04 - /usr/sbin/config -m BERI_DE4_SDROOT TB --- 2012-11-18 02:17:04 - building BERI_DE4_SDROOT kernel TB --- 2012-11-18 02:17:04 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:17:04 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:17:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:17:04 - SRCCONF=/dev/null TB --- 2012-11-18 02:17:04 - TARGET=mips TB --- 2012-11-18 02:17:04 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:17:04 - TZ=UTC TB --- 2012-11-18 02:17:04 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:17:04 - cd /src TB --- 2012-11-18 02:17:04 - /usr/bin/make -B buildkernel KERNCONF=BERI_DE4_SDROOT >>> Kernel build for BERI_DE4_SDROOT started on Sun Nov 18 02:17:04 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for BERI_DE4_SDROOT completed on Sun Nov 18 02:19:17 UTC 2012 TB --- 2012-11-18 02:19:17 - cd /src/sys/mips/conf TB --- 2012-11-18 02:19:17 - /usr/sbin/config -m BERI_SIM_MDROOT TB --- 2012-11-18 02:19:17 - building BERI_SIM_MDROOT kernel TB --- 2012-11-18 02:19:17 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:19:17 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:19:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:19:17 - SRCCONF=/dev/null TB --- 2012-11-18 02:19:17 - TARGET=mips TB --- 2012-11-18 02:19:17 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:19:17 - TZ=UTC TB --- 2012-11-18 02:19:17 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:19:17 - cd /src TB --- 2012-11-18 02:19:17 - /usr/bin/make -B buildkernel KERNCONF=BERI_SIM_MDROOT >>> Kernel build for BERI_SIM_MDROOT started on Sun Nov 18 02:19:17 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for BERI_SIM_MDROOT completed on Sun Nov 18 02:21:28 UTC 2012 TB --- 2012-11-18 02:21:28 - cd /src/sys/mips/conf TB --- 2012-11-18 02:21:28 - /usr/sbin/config -m BERI_TEMPLATE TB --- 2012-11-18 02:21:28 - building BERI_TEMPLATE kernel TB --- 2012-11-18 02:21:28 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:21:28 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:21:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:21:28 - SRCCONF=/dev/null TB --- 2012-11-18 02:21:28 - TARGET=mips TB --- 2012-11-18 02:21:28 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:21:28 - TZ=UTC TB --- 2012-11-18 02:21:28 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:21:28 - cd /src TB --- 2012-11-18 02:21:28 - /usr/bin/make -B buildkernel KERNCONF=BERI_TEMPLATE >>> Kernel build for BERI_TEMPLATE started on Sun Nov 18 02:21:28 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for BERI_TEMPLATE completed on Sun Nov 18 02:23:38 UTC 2012 TB --- 2012-11-18 02:23:38 - cd /src/sys/mips/conf TB --- 2012-11-18 02:23:38 - /usr/sbin/config -m DIR-825 TB --- 2012-11-18 02:23:38 - skipping DIR-825 kernel TB --- 2012-11-18 02:23:38 - cd /src/sys/mips/conf TB --- 2012-11-18 02:23:38 - /usr/sbin/config -m GXEMUL TB --- 2012-11-18 02:23:38 - building GXEMUL kernel TB --- 2012-11-18 02:23:38 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:23:38 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:23:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:23:38 - SRCCONF=/dev/null TB --- 2012-11-18 02:23:38 - TARGET=mips TB --- 2012-11-18 02:23:38 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:23:38 - TZ=UTC TB --- 2012-11-18 02:23:38 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:23:38 - cd /src TB --- 2012-11-18 02:23:38 - /usr/bin/make -B buildkernel KERNCONF=GXEMUL >>> Kernel build for GXEMUL started on Sun Nov 18 02:23:38 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GXEMUL completed on Sun Nov 18 02:25:33 UTC 2012 TB --- 2012-11-18 02:25:33 - cd /src/sys/mips/conf TB --- 2012-11-18 02:25:33 - /usr/sbin/config -m IDT TB --- 2012-11-18 02:25:33 - skipping IDT kernel TB --- 2012-11-18 02:25:33 - cd /src/sys/mips/conf TB --- 2012-11-18 02:25:33 - /usr/sbin/config -m MALTA TB --- 2012-11-18 02:25:33 - skipping MALTA kernel TB --- 2012-11-18 02:25:33 - cd /src/sys/mips/conf TB --- 2012-11-18 02:25:33 - /usr/sbin/config -m MALTA64 TB --- 2012-11-18 02:25:33 - skipping MALTA64 kernel TB --- 2012-11-18 02:25:33 - cd /src/sys/mips/conf TB --- 2012-11-18 02:25:33 - /usr/sbin/config -m OCTEON1 TB --- 2012-11-18 02:25:34 - building OCTEON1 kernel TB --- 2012-11-18 02:25:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:25:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:25:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:25:34 - SRCCONF=/dev/null TB --- 2012-11-18 02:25:34 - TARGET=mips TB --- 2012-11-18 02:25:34 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:25:34 - TZ=UTC TB --- 2012-11-18 02:25:34 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:25:34 - cd /src TB --- 2012-11-18 02:25:34 - /usr/bin/make -B buildkernel KERNCONF=OCTEON1 >>> Kernel build for OCTEON1 started on Sun Nov 18 02:25:34 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for OCTEON1 completed on Sun Nov 18 02:33:13 UTC 2012 TB --- 2012-11-18 02:33:13 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:13 - /usr/sbin/config -m PB47 TB --- 2012-11-18 02:33:13 - skipping PB47 kernel TB --- 2012-11-18 02:33:13 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:13 - /usr/sbin/config -m PB92 TB --- 2012-11-18 02:33:13 - skipping PB92 kernel TB --- 2012-11-18 02:33:13 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:13 - /usr/sbin/config -m QEMU TB --- 2012-11-18 02:33:13 - skipping QEMU kernel TB --- 2012-11-18 02:33:13 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:13 - /usr/sbin/config -m ROUTERSTATION TB --- 2012-11-18 02:33:13 - skipping ROUTERSTATION kernel TB --- 2012-11-18 02:33:13 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:13 - /usr/sbin/config -m ROUTERSTATION_MFS TB --- 2012-11-18 02:33:14 - skipping ROUTERSTATION_MFS kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m RSPRO TB --- 2012-11-18 02:33:14 - skipping RSPRO kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m RSPRO_MFS TB --- 2012-11-18 02:33:14 - skipping RSPRO_MFS kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m RSPRO_STANDALONE TB --- 2012-11-18 02:33:14 - skipping RSPRO_STANDALONE kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m RT305X TB --- 2012-11-18 02:33:14 - skipping RT305X kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m SENTRY5 TB --- 2012-11-18 02:33:14 - skipping SENTRY5 kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m SWARM TB --- 2012-11-18 02:33:14 - skipping SWARM kernel TB --- 2012-11-18 02:33:14 - cd /src/sys/mips/conf TB --- 2012-11-18 02:33:14 - /usr/sbin/config -m SWARM64 TB --- 2012-11-18 02:33:14 - building SWARM64 kernel TB --- 2012-11-18 02:33:14 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 02:33:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 02:33:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 02:33:14 - SRCCONF=/dev/null TB --- 2012-11-18 02:33:14 - TARGET=mips TB --- 2012-11-18 02:33:14 - TARGET_ARCH=mips64 TB --- 2012-11-18 02:33:14 - TZ=UTC TB --- 2012-11-18 02:33:14 - __MAKE_CONF=/dev/null TB --- 2012-11-18 02:33:14 - cd /src TB --- 2012-11-18 02:33:14 - /usr/bin/make -B buildkernel KERNCONF=SWARM64 >>> Kernel build for SWARM64 started on Sun Nov 18 02:33:14 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/radix_mpath.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/raw_cb.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/raw_usrreq.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/route.c cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/rtsock.c cc1: warnings being treated as errors /src/sys/net/rtsock.c: In function 'sysctl_dumpentry': /src/sys/net/rtsock.c:1577: warning: unused variable 'i' [-Wunused-variable] *** [rtsock.o] Error code 1 Stop in /obj/mips.mips64/src/sys/SWARM64. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 02:35:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 02:35:13 - ERROR: failed to build SWARM64 kernel TB --- 2012-11-18 02:35:13 - 3657.26 user 797.76 system 5544.57 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips64-mips.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 04:52:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94A04793; Sun, 18 Nov 2012 04:52:38 +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 551618FC13; Sun, 18 Nov 2012 04:52:38 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so2908015pbc.13 for ; Sat, 17 Nov 2012 20:52:32 -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:content-type :content-transfer-encoding; bh=JYBvCyZXTD+bjRmiuyUc4liSvg5C8bFB9v3vSI18vHg=; b=MZAkN1LQmBL5Ma6DZ2dtazdnuk9Roy8VkWUMra4nuHGZd9/xX7hVXx2Hdk7A5XkMXl u3ZcgVX4M9VDIMz5mrWKvJsHke1ErA7u89g157OJxsANr9GJaAL05pxIH8lBI+To4V3+ Ce8epHmV8iWA2RNzyvezH/A7xuLM11k4Xf5csBrqXjtbZQmAES6ic9+86U77Sxjqljxm kF99BBMOOnAiUbmkqy2ftpGlsP/UIihqM5kMhhIbXQEAi5UQ7VMsJmuZ9eoMfIRazTQI Up1EDINxvWbdNrZE8lZzCFMd3wg6opDhmgRUpCG6cHujxm9fXInj4toYebZSSYRL4Qww ycoA== MIME-Version: 1.0 Received: by 10.66.79.168 with SMTP id k8mr26249817pax.12.1353214352193; Sat, 17 Nov 2012 20:52:32 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sat, 17 Nov 2012 20:52:32 -0800 (PST) In-Reply-To: <201211180235.qAI2ZDql022583@freebsd-current.sentex.ca> References: <201211180235.qAI2ZDql022583@freebsd-current.sentex.ca> Date: Sat, 17 Nov 2012 20:52:32 -0800 X-Google-Sender-Auth: kwFBWrQJUzlVRn6jYuC6UmAa2zc Message-ID: Subject: Re: [head tinderbox] failure on mips64/mips From: Adrian Chadd To: freebsd-current , FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 04:52:38 -0000 On 17 November 2012 18:35, FreeBSD Tinderbox wrote: > cc -c -O -pipe -std=3Dc99 -g -Wall -Wredundant-decls -Wnested-externs -W= strict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qua= l -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -f= diagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq= -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include = opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-growth= =3D10000 --param large-function-growth=3D100000 --param max-inline-insns-si= ngle=3D10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=3D0xffffffff8000100= 0 -mabi=3D64 -march=3Dmips64 -msoft-float -ffreestanding -Werror /src/sys/= net/rtsock.c > cc1: warnings being treated as errors > /src/sys/net/rtsock.c: In function 'sysctl_dumpentry': > /src/sys/net/rtsock.c:1577: warning: unused variable 'i' [-Wunused-variab= le] > *** [rtsock.o] Error code 1 Fixed. Damn those pesky non-IPV6 belivers. Adrian From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 05:46:30 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7AB2017C; Sun, 18 Nov 2012 05:46:30 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id ADDC08FC13; Sun, 18 Nov 2012 05:46:28 +0000 (UTC) Received: from alph.allbsd.org (p1137-ipbf1505funabasi.chiba.ocn.ne.jp [118.7.212.137]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id qAI5kBGf037907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Nov 2012 14:46:21 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.allbsd.org (8.14.5/8.14.5) with ESMTP id qAI5k93r095634; Sun, 18 Nov 2012 14:46:11 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 18 Nov 2012 14:45:59 +0900 (JST) Message-Id: <20121118.144559.684835936214218282.hrs@allbsd.org> To: adrian@FreeBSD.org Subject: Re: [head tinderbox] failure on mips64/mips From: Hiroki Sato In-Reply-To: References: <201211180235.qAI2ZDql022583@freebsd-current.sentex.ca> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sun_Nov_18_14_45_59_2012_683)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Sun, 18 Nov 2012 14:46:21 +0900 (JST) X-Spam-Status: No, score=-97.9 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,QENCPTR1,SAMEHELOBY2HOP,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-net@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 05:46:30 -0000 ----Security_Multipart(Sun_Nov_18_14_45_59_2012_683)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Adrian Chadd wrote in : ad> On 17 November 2012 18:35, FreeBSD Tinderbox wrote: ad> ad> > cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=10000 --param large-function-growth=100000 --param max-inline-insns-single=10000 -fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0xffffffff80001000 -mabi=64 -march=mips64 -msoft-float -ffreestanding -Werror /src/sys/net/rtsock.c ad> > cc1: warnings being treated as errors ad> > /src/sys/net/rtsock.c: In function 'sysctl_dumpentry': ad> > /src/sys/net/rtsock.c:1577: warning: unused variable 'i' [-Wunused-variable] ad> > *** [rtsock.o] Error code 1 ad> ad> Fixed. Damn those pesky non-IPV6 belivers. Sorry, I was careless about this part. -- Hiroki ----Security_Multipart(Sun_Nov_18_14_45_59_2012_683)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAlCodhcACgkQTyzT2CeTzy2UdgCeMuJgRYyt0DfsYbZsFrZlSq25 thwAoKVcnz6ltjN9L5NaMCNkFxXsKMkX =bLAa -----END PGP SIGNATURE----- ----Security_Multipart(Sun_Nov_18_14_45_59_2012_683)---- From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 07:24:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C89F6CA for ; Sun, 18 Nov 2012 07:24:08 +0000 (UTC) (envelope-from mailer-daemon@vniz.net) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id D98F58FC0C for ; Sun, 18 Nov 2012 07:24:07 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so2870443eek.13 for ; Sat, 17 Nov 2012 23:24:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:openpgp:content-type :content-transfer-encoding:x-gm-message-state; bh=9b/yP4OXwExDsjeKmQtEEhLz+bElPWgczjN9/LdbOWg=; b=TG6fTqcjOCEr03g7Qt8MV1jw92URhaKQhAlOdKWC8cB8HTb29Ff0Yr6iI54/TDP2hJ JcEL6yH+yUDBR9ZyGNHXnQpEs1n9TVkyCy+llpsJsnx+43CHhhiigLS7EF3x4jWgyvMe a1nQQJzLO2EiPPsaIrGDwp1wG8xXAJ0UucqNavXCz0TQ0bfv7ISkmqUTltPWch2F7Fu8 smGXT30mmCy/ncYiFZH5X1Krr8NooXWpGYud/07PRzb8Mw834Wj+IuUQT8Y58TC7SQ/d oMENXvR1SipUj+A0dnK9Na/P/zX6Zwg2qL3s86YRhfvPPojmzxPqseaHbWXBj0tie+qF N5Tw== Received: by 10.14.209.6 with SMTP id r6mr13093800eeo.34.1353223441021; Sat, 17 Nov 2012 23:24:01 -0800 (PST) Received: from [192.168.1.2] ([89.169.163.3]) by mx.google.com with ESMTPS id e7sm15607446eep.1.2012.11.17.23.23.59 (version=SSLv3 cipher=OTHER); Sat, 17 Nov 2012 23:24:00 -0800 (PST) Message-ID: <50A88D0E.1070301@freebsd.org> Date: Sun, 18 Nov 2012 11:23:58 +0400 From: Andrey Chernov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: current@freebsd.org Subject: Tons of "sa6_recoverscope: assumption failure" on recent -current OpenPGP: id=964474DD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkXt0ZJuBR3HoFTc2kx83QVMQG+fHQTeT13uo9PoT3TPU6dnooNgx+1qClMry1L4TAQFzG6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 07:24:08 -0000 On every IPv6 address of my card and router and every broadcast and link-local scope addresses I see now: kernel: sa6_recoverscope: assumption failure (non 0 ID): What does it mean and why there are so many of them? I have plain local net with IPv6 router, nothing unusual. IPv6 continues to work despite of those failures. From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 08:10:56 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A167DB2D; Sun, 18 Nov 2012 08:10:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 631CD8FC14; Sun, 18 Nov 2012 08:10:56 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1841447dad.13 for ; Sun, 18 Nov 2012 00:10:55 -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=gHYDOGP6DGWVWYueRBjeYS7NFocVfrkDja0zmotyGSA=; b=i0KHumUcR6mPDfCTxMpNhZE9+DsBqftmZMSTQPlO9uhqPjOjkOMRdQNhZx2SfF/B3u lB5FYHMskdgWcQcYjrfHGvmGDUELf9ZHXl4BsSsexFLwZiT7xMfMOnKTp+86C9EcpPj9 jy/eOWUQcDuPgnvAI1MnhIIGEyfm2lOYmXevQJabYJBHKL8JdvMQGbiKtMNrY4l3V/Hr MCv4QdBmU+7Tytc0OXpZXzme5rBFBx9ndjB+zSvIZCZX4MsYHJhMmBdVTv68RXd5ZAtH 7Ak6//rase8oCbuNhvyHU/FHnSOuvsJpC7UaUPwVe1srvtGdanW4IQr6xx9emdh56Jkd 1/FA== MIME-Version: 1.0 Received: by 10.66.75.101 with SMTP id b5mr26879964paw.45.1353226255760; Sun, 18 Nov 2012 00:10:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Sun, 18 Nov 2012 00:10:55 -0800 (PST) In-Reply-To: <20121118.144559.684835936214218282.hrs@allbsd.org> References: <201211180235.qAI2ZDql022583@freebsd-current.sentex.ca> <20121118.144559.684835936214218282.hrs@allbsd.org> Date: Sun, 18 Nov 2012 00:10:55 -0800 X-Google-Sender-Auth: kYK4eb-IhqyrdDd4RVyFBpL4s2U Message-ID: Subject: Re: [head tinderbox] failure on mips64/mips From: Adrian Chadd To: Hiroki Sato Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 08:10:56 -0000 On 17 November 2012 21:45, Hiroki Sato wrote: > ad> Fixed. Damn those pesky non-IPV6 belivers. > > Sorry, I was careless about this part. It's fine. :-) God, I so can't grill anyone for breaking the build, given my track record! I hope you didn't mind me quickly fixing that up? Thanks, Adrian From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 11:49:06 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C7F3AE9; Sun, 18 Nov 2012 11:49:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 326428FC16; Sun, 18 Nov 2012 11:49:04 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA02000; Sun, 18 Nov 2012 13:48:45 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Ta3Mj-0008zE-K2; Sun, 18 Nov 2012 13:48:45 +0200 Message-ID: <50A8CB1C.9090907@FreeBSD.org> Date: Sun, 18 Nov 2012 13:48:44 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Bartosz Stec , Guido Falsi Subject: Re: problem booting to multi-vdev root pool References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66701.701@madpilot.net> <50A82B3A.6020608@it4pro.pl> In-Reply-To: <50A82B3A.6020608@it4pro.pl> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 11:49:06 -0000 on 18/11/2012 02:26 Bartosz Stec said the following: > W dniu 2012-11-16 17:17, Guido Falsi pisze: >> On 11/16/12 16:45, Andriy Gapon wrote: >>> Guido, Bartosz, >>> could you please test the patch? >> >> I have just compiler an r242910 kernel with this patch (and just this one) >> applied. >> >> System booted so it seems to work fine! :) > I've just compiled and installed fresh kernel with your patch, system booted > without any problems, so apparently patch works as intended. Thank you both very much for testing! Committed as r243213. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 16:21:44 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B0E5824; Sun, 18 Nov 2012 16:21:44 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 7ACC48FC13; Sun, 18 Nov 2012 16:21:43 +0000 (UTC) Received: from alph.allbsd.org (p1137-ipbf1505funabasi.chiba.ocn.ne.jp [118.7.212.137]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id qAIGLQCI055073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Nov 2012 01:21:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.allbsd.org (8.14.5/8.14.5) with ESMTP id qAIGLP71017463; Mon, 19 Nov 2012 01:21:25 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 19 Nov 2012 01:21:17 +0900 (JST) Message-Id: <20121119.012117.1135299527992880767.hrs@allbsd.org> To: adrian@FreeBSD.org Subject: Re: [head tinderbox] failure on mips64/mips From: Hiroki Sato In-Reply-To: References: <20121118.144559.684835936214218282.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Nov_19_01_21_17_2012_132)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Mon, 19 Nov 2012 01:21:36 +0900 (JST) X-Spam-Status: No, score=-98.1 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,SAMEHELOBY2HOP,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-net@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 16:21:44 -0000 ----Security_Multipart(Mon_Nov_19_01_21_17_2012_132)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Adrian Chadd wrote in : ad> On 17 November 2012 21:45, Hiroki Sato wrote: ad> ad> > ad> Fixed. Damn those pesky non-IPV6 belivers. ad> > ad> > Sorry, I was careless about this part. ad> ad> It's fine. :-) God, I so can't grill anyone for breaking the build, ad> given my track record! ad> ad> I hope you didn't mind me quickly fixing that up? I did not mind at all. Thank you for fixing it! -- Hiroki ----Security_Multipart(Mon_Nov_19_01_21_17_2012_132)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAlCpCv0ACgkQTyzT2CeTzy3d4wCgzSZRxProKpE7ZPeIFZ/sKgKs iVsAoNDepgwpoFzUBpxynnQ8iq8wAfQD =0vU9 -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Nov_19_01_21_17_2012_132)---- From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 20:53:17 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1375EF45; Sun, 18 Nov 2012 20:53:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id BAF668FC0C; Sun, 18 Nov 2012 20:53:16 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAIKrF0p021649; Sun, 18 Nov 2012 15:53:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAIKrFLg021634; Sun, 18 Nov 2012 20:53:15 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 20:53:15 GMT Message-Id: <201211182053.qAIKrFLg021634@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 20:53:17 -0000 TB --- 2012-11-18 19:53:50 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 19:53:50 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 19:53:50 - starting HEAD tinderbox run for mips/mips TB --- 2012-11-18 19:53:50 - cleaning the object tree TB --- 2012-11-18 19:53:50 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 19:53:50 - cd /tinderbox/HEAD/mips/mips TB --- 2012-11-18 19:53:50 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 19:54:42 - /usr/local/bin/svn update /src TB --- 2012-11-18 19:54:49 - At svn revision 243248 TB --- 2012-11-18 19:54:50 - building world TB --- 2012-11-18 19:54:50 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 19:54:50 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 19:54:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 19:54:50 - SRCCONF=/dev/null TB --- 2012-11-18 19:54:50 - TARGET=mips TB --- 2012-11-18 19:54:50 - TARGET_ARCH=mips TB --- 2012-11-18 19:54:50 - TZ=UTC TB --- 2012-11-18 19:54:50 - __MAKE_CONF=/dev/null TB --- 2012-11-18 19:54:50 - cd /src TB --- 2012-11-18 19:54:50 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 19:54:55 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /obj/mips.mips/src/tmp/usr/include/netinet/ip_compat.h:1543: warning: previous declaration of 'bcopywrap' was here In file included from ioctl.c:123: /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:338: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:496: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:627: error: expected ')' before 'lbn' /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:647: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'lbn_offset' /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:693: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips/src/tmp/usr/include/ufs/ffs/fs.h:729: error: expected specifier-qualifier-list before 'ufs2_daddr_t' *** [ioctl.o] Error code 1 Stop in /src/usr.bin/kdump. *** [all] Error code 1 Stop in /src/usr.bin. *** [usr.bin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 20:53:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 20:53:15 - ERROR: failed to build world TB --- 2012-11-18 20:53:15 - 2402.47 user 596.24 system 3565.15 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 21:52:52 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 102AFA7D; Sun, 18 Nov 2012 21:52:52 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id B56FC8FC0C; Sun, 18 Nov 2012 21:52:51 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAILqo6R082771; Sun, 18 Nov 2012 16:52:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAILqoOc082766; Sun, 18 Nov 2012 21:52:50 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 21:52:50 GMT Message-Id: <201211182152.qAILqoOc082766@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips64/mips Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 21:52:52 -0000 TB --- 2012-11-18 20:53:16 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 20:53:16 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 20:53:16 - starting HEAD tinderbox run for mips64/mips TB --- 2012-11-18 20:53:16 - cleaning the object tree TB --- 2012-11-18 20:53:16 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 20:53:16 - cd /tinderbox/HEAD/mips64/mips TB --- 2012-11-18 20:53:16 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 20:54:26 - /usr/local/bin/svn update /src TB --- 2012-11-18 20:54:33 - At svn revision 243249 TB --- 2012-11-18 20:54:34 - building world TB --- 2012-11-18 20:54:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 20:54:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 20:54:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 20:54:34 - SRCCONF=/dev/null TB --- 2012-11-18 20:54:34 - TARGET=mips TB --- 2012-11-18 20:54:34 - TARGET_ARCH=mips64 TB --- 2012-11-18 20:54:34 - TZ=UTC TB --- 2012-11-18 20:54:34 - __MAKE_CONF=/dev/null TB --- 2012-11-18 20:54:34 - cd /src TB --- 2012-11-18 20:54:34 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 20:54:40 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /obj/mips.mips64/src/tmp/usr/include/netinet/ip_compat.h:1543: warning: previous declaration of 'bcopywrap' was here In file included from ioctl.c:123: /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:338: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:496: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:627: error: expected ')' before 'lbn' /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:647: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'lbn_offset' /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:693: error: expected specifier-qualifier-list before 'ufs_time_t' /obj/mips.mips64/src/tmp/usr/include/ufs/ffs/fs.h:729: error: expected specifier-qualifier-list before 'ufs2_daddr_t' *** [ioctl.o] Error code 1 Stop in /src/usr.bin/kdump. *** [all] Error code 1 Stop in /src/usr.bin. *** [usr.bin.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 21:52:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 21:52:50 - ERROR: failed to build world TB --- 2012-11-18 21:52:50 - 2414.55 user 550.71 system 3574.49 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-mips64-mips.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 23:20:59 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD9D99AD; Sun, 18 Nov 2012 23:20:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 79CC28FC12; Sun, 18 Nov 2012 23:20:59 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAINKrwA028771; Sun, 18 Nov 2012 18:20:53 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAINKrmC028770; Sun, 18 Nov 2012 23:20:53 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 23:20:53 GMT Message-Id: <201211182320.qAINKrmC028770@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 23:21:00 -0000 TB --- 2012-11-18 21:02:39 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 21:02:39 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 21:02:39 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-11-18 21:02:39 - cleaning the object tree TB --- 2012-11-18 21:02:39 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 21:02:39 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2012-11-18 21:02:39 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 21:03:26 - /usr/local/bin/svn update /src TB --- 2012-11-18 21:03:33 - At svn revision 243249 TB --- 2012-11-18 21:03:34 - building world TB --- 2012-11-18 21:03:34 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 21:03:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 21:03:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 21:03:34 - SRCCONF=/dev/null TB --- 2012-11-18 21:03:34 - TARGET=powerpc TB --- 2012-11-18 21:03:34 - TARGET_ARCH=powerpc TB --- 2012-11-18 21:03:34 - TZ=UTC TB --- 2012-11-18 21:03:34 - __MAKE_CONF=/dev/null TB --- 2012-11-18 21:03:34 - cd /src TB --- 2012-11-18 21:03:34 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 21:03:39 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/sys/boot/powerpc/boot1.chrp/boot1.c:64: error: previous declaration of 'mount' was here /src/sys/boot/powerpc/boot1.chrp/boot1.c: In function 'main': /src/sys/boot/powerpc/boot1.chrp/boot1.c:434: warning: passing argument 2 of 'mount' makes pointer from integer without a cast /src/sys/boot/powerpc/boot1.chrp/boot1.c:434: error: too few arguments to function 'mount' /src/sys/boot/powerpc/boot1.chrp/boot1.c:444: error: too few arguments to function 'mount' /src/sys/boot/powerpc/boot1.chrp/boot1.c: At top level: /src/sys/boot/powerpc/boot1.chrp/boot1.c:473: error: conflicting types for 'mount' /src/sys/boot/powerpc/boot1.chrp/../../../sys/mount.h:824: error: previous declaration of 'mount' was here *** [boot1.o] Error code 1 Stop in /src/sys/boot/powerpc/boot1.chrp. *** [all] Error code 1 Stop in /src/sys/boot/powerpc. *** [all] Error code 1 Stop in /src/sys/boot. *** [all] Error code 1 Stop in /src/sys. *** [sys.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 23:20:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 23:20:52 - ERROR: failed to build world TB --- 2012-11-18 23:20:52 - 6496.07 user 885.78 system 8293.59 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 23:32:52 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 954DEB4E for ; Sun, 18 Nov 2012 23:32:52 +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 0ECC18FC0C for ; Sun, 18 Nov 2012 23:32:51 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so1476223lbb.13 for ; Sun, 18 Nov 2012 15:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to:content-type; bh=5Xc2lWjNHdOl8WYnoX3WRjE3NKI3j4ZOjYH61xaMMI4=; b=tU3UbqUpfK6Dj818U+3NVd8T4hfPGCnSZtlN+GPu9VUwWe3XEQ2SYuDnIgPAY76hnX NkOrrKU7Xd4oeob99QaX0Az2FzcVqSGJbAlFaJE8suE0VW7V195TStZnFRcRhr+p0IJq p0XlEH6smrAzVSYV8Sa5DprXGntW/h8+4kXPI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-gm-message-state; bh=5Xc2lWjNHdOl8WYnoX3WRjE3NKI3j4ZOjYH61xaMMI4=; b=Q59YK95y+OHMO9BYyv/gwAcPoLsYM+FQPh6XqHL6bWNUgjIoZgazsGqL5gKwHVp0KC xsguGIB9JLZbIDARvte+1RCdqSJSyLClYf8YiR1foMVHVvdlyeXrDX1MLeziTM2xBj33 xUZYFF2QgVe92BpAGdNY1gpjxphN9hvEol6+LxdFd1nF4hl1n9IsKSVNmpOTbd27UuuO LjqzExoqhhbqRZzCeSIDrlpfosNHyrW5C1054LulCibRuu75plFu1jWF7azRTUgGZxEL jC8QYh/VEVNcZo1d98irnJuUTSlQjTSEEq9bZyKxEGAX7It/Cy7ndgBn/5gFchShkZ+v ZEAQ== Received: by 10.112.103.136 with SMTP id fw8mr4530444lbb.18.1353281570449; Sun, 18 Nov 2012 15:32:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Sun, 18 Nov 2012 15:32:20 -0800 (PST) From: Eitan Adler Date: Sun, 18 Nov 2012 18:32:20 -0500 Message-ID: Subject: prompt w/ uid 0 for cshrc To: freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnUMv33D+9qlKkW9UcXAUaOESG8kdCTMItgi8EtTCRQTh+1yjd9d+KGTDrfdwpfJi+Rvn9Q X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 23:32:52 -0000 Hey, at the moment the current default csh prompt looks like user@hostname:directory% command This leads to an unexpected[*] result when using su (without "-"). In particular the user part is *not* changed to "root" (or "toor" or any other superuser indication) although the promptchar is changed to "#". This causes some confusion for new users and even some experienced ones. I worked around this issue by including the following if ($uid == 0) then set user = root endif which I'm not certain is a good idea. I would like to replace this with logic like if $uid = 0 AND $user != toor AND $user != root set user = "+$user" endif does anyone think this is a bad idea? can anyone propose a better idea? Is the status quo okay? I don't trust user education for this problem. I've seen way too many people get confused to leave the default without some extra indicator. [*] Okay, so this is expected if you understand the difference between "su" and "su -" but the defaults are not aimed at people that understand this difference. -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 23:44:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C618D12 for ; Sun, 18 Nov 2012 23:44:42 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id EAA888FC14 for ; Sun, 18 Nov 2012 23:44:41 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id hj6so2758685wib.13 for ; Sun, 18 Nov 2012 15:44:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=iuYMEIW81n8yYM7Bu6frdV9VSdUPqcPrMRNyX2faZB8=; b=iQdcQa0SDRkLzqW6gfHnXmBxHFj6Lq3+izWjgYujE90arrYB05ROQji0kKoND+KBIv 0FjPwnUNVIPx9UAOsMOcaNzW247Uvjnu9GZ/CzNTidWO/8ayApcQbg0fzA62PGSdCzbP beoRXBbU4UFGLCvnzj1mVH7nOvbjfADaTO7VQr1ritCN+kI3M76dudCNTaFrZxf3al+t SeQjG5DRg1Tu4PA2Syi9Jvr4nlFwL7aBE3kZxR35LnUijCZMjrgbXwAaRYnv3GkrLhC4 vSu2xcDvriMOg7ZjWQxgDGCuh+8hqIA1M7yhNyPCzkJRaQbSyHa3CdDwvK4ZozJVNlfJ gGrA== Received: by 10.216.202.21 with SMTP id c21mr4173196weo.159.1353282280775; Sun, 18 Nov 2012 15:44:40 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id i2sm11162254wiw.3.2012.11.18.15.44.36 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 18 Nov 2012 15:44:39 -0800 (PST) Date: Mon, 19 Nov 2012 00:44:27 +0100 From: Mateusz Guzik To: Eitan Adler Subject: Re: prompt w/ uid 0 for cshrc Message-ID: <20121118234426.GA16628@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Eitan Adler , freebsd-current Current References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 23:44:42 -0000 On Sun, Nov 18, 2012 at 06:32:20PM -0500, Eitan Adler wrote: > Hey, > > at the moment the current default csh prompt looks like > > user@hostname:directory% command > > This leads to an unexpected[*] result when using su (without "-"). > > In particular the user part is *not* changed to "root" (or "toor" or > any other superuser indication) although the promptchar is changed to > "#". > This causes some confusion for new users and even some experienced ones. > > I worked around this issue by including the following > > if ($uid == 0) then > set user = root > endif > > which I'm not certain is a good idea. > > I would like to replace this with logic like > > if $uid = 0 AND $user != toor AND $user != root > set user = "+$user" > endif > > does anyone think this is a bad idea? can anyone propose a better > idea? Is the status quo okay? > Just take user name from id -nu. -- Mateusz Guzik From owner-freebsd-current@FreeBSD.ORG Sun Nov 18 23:51:29 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E05C9B0; Sun, 18 Nov 2012 23:51:28 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 95C168FC0C; Sun, 18 Nov 2012 23:51:28 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAINpRuX021730; Sun, 18 Nov 2012 18:51:27 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAINpRGP021729; Sun, 18 Nov 2012 23:51:27 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 18 Nov 2012 23:51:27 GMT Message-Id: <201211182351.qAINpRGP021729@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on sparc64/sparc64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 23:51:29 -0000 TB --- 2012-11-18 22:56:31 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 22:56:31 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 22:56:31 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-11-18 22:56:31 - cleaning the object tree TB --- 2012-11-18 22:56:31 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 22:56:31 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2012-11-18 22:56:31 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 22:57:52 - /usr/local/bin/svn update /src TB --- 2012-11-18 22:58:00 - At svn revision 243251 TB --- 2012-11-18 22:58:01 - building world TB --- 2012-11-18 22:58:01 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 22:58:01 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 22:58:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 22:58:01 - SRCCONF=/dev/null TB --- 2012-11-18 22:58:01 - TARGET=sparc64 TB --- 2012-11-18 22:58:01 - TARGET_ARCH=sparc64 TB --- 2012-11-18 22:58:01 - TZ=UTC TB --- 2012-11-18 22:58:01 - __MAKE_CONF=/dev/null TB --- 2012-11-18 22:58:01 - cd /src TB --- 2012-11-18 22:58:01 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 22:58:07 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -mcmodel=medlow -Os -I/src/sys/boot/sparc64/boot1/../../common -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/boot1/boot1.c In file included from /obj/sparc64.sparc64/src/tmp/usr/include/ufs/ffs/fs.h:36, from /src/sys/boot/sparc64/boot1/../../common/ufsread.c:51, from /src/sys/boot/sparc64/boot1/boot1.c:451: /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: conflicting types for 'mount' /src/sys/boot/sparc64/boot1/boot1.c:63: error: previous declaration of 'mount' was here /src/sys/boot/sparc64/boot1/boot1.c:501: error: conflicting types for 'mount' /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: previous declaration of 'mount' was here *** [boot1.o] Error code 1 Stop in /src/sys/boot/sparc64/boot1. *** [all] Error code 1 Stop in /src/sys/boot/sparc64. *** [all] Error code 1 Stop in /src/sys/boot. *** [all] Error code 1 Stop in /src/sys. *** [sys.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-18 23:51:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-18 23:51:27 - ERROR: failed to build world TB --- 2012-11-18 23:51:27 - 2673.95 user 457.65 system 3296.89 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 00:02:51 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0912E4F5; Mon, 19 Nov 2012 00:02:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id A9E228FC12; Mon, 19 Nov 2012 00:02:50 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAJ02nvd040028; Sun, 18 Nov 2012 19:02:49 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAJ02nJS040027; Mon, 19 Nov 2012 00:02:49 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 19 Nov 2012 00:02:49 GMT Message-Id: <201211190002.qAJ02nJS040027@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc64/powerpc Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 00:02:51 -0000 TB --- 2012-11-18 21:52:51 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-18 21:52:51 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-18 21:52:51 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-11-18 21:52:51 - cleaning the object tree TB --- 2012-11-18 21:52:51 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-18 21:52:51 - cd /tinderbox/HEAD/powerpc64/powerpc TB --- 2012-11-18 21:52:51 - /usr/local/bin/svn cleanup /src TB --- 2012-11-18 21:53:56 - /usr/local/bin/svn update /src TB --- 2012-11-18 21:54:03 - At svn revision 243249 TB --- 2012-11-18 21:54:04 - building world TB --- 2012-11-18 21:54:04 - CROSS_BUILD_TESTING=YES TB --- 2012-11-18 21:54:04 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-18 21:54:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-18 21:54:04 - SRCCONF=/dev/null TB --- 2012-11-18 21:54:04 - TARGET=powerpc TB --- 2012-11-18 21:54:04 - TARGET_ARCH=powerpc64 TB --- 2012-11-18 21:54:04 - TZ=UTC TB --- 2012-11-18 21:54:04 - __MAKE_CONF=/dev/null TB --- 2012-11-18 21:54:04 - cd /src TB --- 2012-11-18 21:54:04 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Nov 18 21:54:09 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] /src/sys/boot/powerpc/boot1.chrp/boot1.c:64: error: previous declaration of 'mount' was here /src/sys/boot/powerpc/boot1.chrp/boot1.c: In function 'main': /src/sys/boot/powerpc/boot1.chrp/boot1.c:434: warning: passing argument 2 of 'mount' makes pointer from integer without a cast /src/sys/boot/powerpc/boot1.chrp/boot1.c:434: error: too few arguments to function 'mount' /src/sys/boot/powerpc/boot1.chrp/boot1.c:444: error: too few arguments to function 'mount' /src/sys/boot/powerpc/boot1.chrp/boot1.c: At top level: /src/sys/boot/powerpc/boot1.chrp/boot1.c:473: error: conflicting types for 'mount' /src/sys/boot/powerpc/boot1.chrp/../../../sys/mount.h:824: error: previous declaration of 'mount' was here *** [boot1.o] Error code 1 Stop in /src/sys/boot/powerpc/boot1.chrp. *** [all] Error code 1 Stop in /src/sys/boot/powerpc. *** [all] Error code 1 Stop in /src/sys/boot. *** [all] Error code 1 Stop in /src/sys. *** [sys.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-19 00:02:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-19 00:02:49 - ERROR: failed to build world TB --- 2012-11-19 00:02:49 - 6534.73 user 817.66 system 7798.73 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 05:32:19 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C58CF143; Mon, 19 Nov 2012 05:32:19 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from zcs04.jnb1.cloudseed.co.za (zcs04.jnb1.cloudseed.co.za [41.154.0.161]) by mx1.freebsd.org (Postfix) with ESMTP id 52A8E8FC08; Mon, 19 Nov 2012 05:32:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTP id 78C7C2A82BD0; Mon, 19 Nov 2012 07:32:10 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs04.jnb1.cloudseed.co.za Received: from zcs04.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs04.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpN9GzBdZ9Un; Mon, 19 Nov 2012 07:32:09 +0200 (SAST) Received: from clue.co.za (unknown [41.154.88.19]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id C060D2A82BC4; Mon, 19 Nov 2012 07:32:09 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaJxo-000JjQ-D9; Mon, 19 Nov 2012 07:32:08 +0200 To: Gleb Smirnoff From: Ian FREISLICH Subject: Re: netisr panic? In-Reply-To: <20121117213754.GI38060@FreeBSD.org> References: <20121117213754.GI38060@FreeBSD.org> X-Attribution: BOFH Date: Mon, 19 Nov 2012 07:32:08 +0200 Message-Id: Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 05:32:19 -0000 Gleb Smirnoff wrote: > On Sat, Nov 17, 2012 at 05:07:54PM +0200, Ian FREISLICH wrote: > I> I have this consistently with: > I> > I> FreeBSD firewall2.jnb1.gp-online.net 10.0-CURRENT FreeBSD 10.0-CURRENT #30 r243156: Fri Nov 16 20:12:33 SAST 2012 ianf@firewall2.jnb1.gp-online.net:/ usr/obj/usr/src/sys/FIREWALL amd64 > > Pretty sure this is a new version of wrong byte order panic, which > no longer can happen in HEAD. > > Can you please try this patch? It survived the night, which it hasn't managed before. I'll keep you posted. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 07:50:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17A1B6A5 for ; Mon, 19 Nov 2012 07:50:47 +0000 (UTC) (envelope-from r.c.ladan@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 8F8A38FC13 for ; Mon, 19 Nov 2012 07:50:46 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id je9so1014782bkc.13 for ; Sun, 18 Nov 2012 23:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=zzmV4l1lJCcITI0OuzxTHtFJznuQp0f2UlyBWrBYue0=; b=dLvAZdFkt1d4Sqlq7yvod+4lFqZEiX5hEI3PS0sqpcbBhETWnK5+GgSFaOpDEAeTlq oMBeJxiztmj0vgPgoOkkn1QjlTbTqBb7o8cWpS6rNO7YPwBN+hxElgjqgsfryWW8vN9N EFAKXsd/3Bzjyg4+zWGBxRJ9NaNA20J8N32kDP6ybK+7PKg9njDjb5aD0zwz+086aZ56 lXX9PukiagZhxhmJYJHoQ60WqPRP/FAJI8Meq9Or3lOCj6myq9PtHBYkHqp7QEAXFAd/ n7LKJCydV1QH5XNxIJPB23GDZqt8lC3cDozeSfJFB/XvFdFg3qNkyu2ajSMyZ2I20EVY wpHA== Received: by 10.204.6.20 with SMTP id 20mr199214bkx.33.1353311445275; Sun, 18 Nov 2012 23:50:45 -0800 (PST) Received: from [192.168.1.11] (ip18-43-209-87.adsl2.static.versatel.nl. [87.209.43.18]) by mx.google.com with ESMTPS id v14sm3524734bkv.10.2012.11.18.23.50.43 (version=SSLv3 cipher=OTHER); Sun, 18 Nov 2012 23:50:44 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <50A9E4D1.8000701@freebsd.org> Date: Mon, 19 Nov 2012 08:50:41 +0100 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121115 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Tons of "sa6_recoverscope: assumption failure" on recent -current References: <50A88D0E.1070301@freebsd.org> In-Reply-To: <50A88D0E.1070301@freebsd.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 07:50:47 -0000 On 18-11-2012 08:23, Andrey Chernov wrote: > On every IPv6 address of my card and router and every broadcast and > link-local scope addresses I see now: > kernel: sa6_recoverscope: assumption failure (non 0 ID): > > What does it mean and why there are so many of them? I have plain local > net with IPv6 router, nothing unusual. > I'm also seeing them when using a teredo-tunnel over an IPv4 router, r243234-amd64 René From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 08:00:30 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6DF1A9D3; Mon, 19 Nov 2012 08:00:30 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id CE86D8FC13; Mon, 19 Nov 2012 08:00:28 +0000 (UTC) Received: from alph.allbsd.org (p1137-ipbf1505funabasi.chiba.ocn.ne.jp [118.7.212.137]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id qAJ801LF071185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Nov 2012 17:00:16 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.allbsd.org (8.14.5/8.14.5) with ESMTP id qAJ7xxDd027969; Mon, 19 Nov 2012 17:00:01 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 19 Nov 2012 16:59:54 +0900 (JST) Message-Id: <20121119.165954.1302634823989942540.hrs@allbsd.org> To: ache@FreeBSD.org, rene@FreeBSD.org Subject: Re: Tons of "sa6_recoverscope: assumption failure" on recent -current From: Hiroki Sato In-Reply-To: <50A88D0E.1070301@freebsd.org> <50A9E4D1.8000701@freebsd.org> References: <50A88D0E.1070301@freebsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Nov_19_16_59_54_2012_643)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Mon, 19 Nov 2012 17:00:17 +0900 (JST) X-Spam-Status: No, score=-97.7 required=13.0 tests=CONTENT_TYPE_PRESENT, MIMEQENC,ONLY1HOPDIRECT,QENCPTR2,SAMEHELOBY2HOP,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 08:00:30 -0000 ----Security_Multipart(Mon_Nov_19_16_59_54_2012_643)-- Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Andrey Chernov wrote in <50A88D0E.1070301@freebsd.org>: ac> On every IPv6 address of my card and router and every broadcast and= ac> link-local scope addresses I see now: ac> kernel: sa6_recoverscope: assumption failure (non 0 ID): ac> = ac> What does it mean and why there are so many of them? I have plain l= ocal ac> net with IPv6 router, nothing unusual. ac> = ac> IPv6 continues to work despite of those failures. Ren=E9 Ladan wrote in <50A9E4D1.8000701@freebsd.org>: re> I'm also seeing them when using a teredo-tunnel over an IPv4 router= , re> r243234-amd64 This warning message itself is not harmful actually, but my commit triggered it. It should be fixed at r243235. Can you let me know if this problem persists even at this revision or later? Thank you. -- Hiroki ----Security_Multipart(Mon_Nov_19_16_59_54_2012_643)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAlCp5voACgkQTyzT2CeTzy3VjQCfb3uxB/MdSj8KHKsNx8GnXQGe /mYAn1kNpEQjperhdkE+WkIr32Lr7Vpn =IIV2 -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Nov_19_16_59_54_2012_643)---- From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 08:12:21 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3EF2312F; Mon, 19 Nov 2012 08:12:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E86A38FC08; Mon, 19 Nov 2012 08:12:20 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAJ8CJDY091009; Mon, 19 Nov 2012 03:12:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAJ8CJJB091008; Mon, 19 Nov 2012 08:12:19 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 19 Nov 2012 08:12:19 GMT Message-Id: <201211190812.qAJ8CJJB091008@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on sparc64/sparc64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 08:12:21 -0000 TB --- 2012-11-19 07:12:07 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-19 07:12:07 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-19 07:12:07 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-11-19 07:12:07 - cleaning the object tree TB --- 2012-11-19 07:13:51 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-19 07:13:51 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2012-11-19 07:13:51 - /usr/local/bin/svn cleanup /src TB --- 2012-11-19 07:15:43 - /usr/local/bin/svn update /src TB --- 2012-11-19 07:15:50 - At svn revision 243261 TB --- 2012-11-19 07:15:51 - building world TB --- 2012-11-19 07:15:51 - CROSS_BUILD_TESTING=YES TB --- 2012-11-19 07:15:51 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-19 07:15:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-19 07:15:51 - SRCCONF=/dev/null TB --- 2012-11-19 07:15:51 - TARGET=sparc64 TB --- 2012-11-19 07:15:51 - TARGET_ARCH=sparc64 TB --- 2012-11-19 07:15:51 - TZ=UTC TB --- 2012-11-19 07:15:51 - __MAKE_CONF=/dev/null TB --- 2012-11-19 07:15:51 - cd /src TB --- 2012-11-19 07:15:51 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Nov 19 07:15:59 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -mcmodel=medlow -Os -I/src/sys/boot/sparc64/boot1/../../common -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/boot1/boot1.c In file included from /obj/sparc64.sparc64/src/tmp/usr/include/ufs/ffs/fs.h:36, from /src/sys/boot/sparc64/boot1/../../common/ufsread.c:51, from /src/sys/boot/sparc64/boot1/boot1.c:451: /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: conflicting types for 'mount' /src/sys/boot/sparc64/boot1/boot1.c:63: error: previous declaration of 'mount' was here /src/sys/boot/sparc64/boot1/boot1.c:501: error: conflicting types for 'mount' /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: previous declaration of 'mount' was here *** [boot1.o] Error code 1 Stop in /src/sys/boot/sparc64/boot1. *** [all] Error code 1 Stop in /src/sys/boot/sparc64. *** [all] Error code 1 Stop in /src/sys/boot. *** [all] Error code 1 Stop in /src/sys. *** [sys.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-19 08:12:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-19 08:12:19 - ERROR: failed to build world TB --- 2012-11-19 08:12:19 - 2695.95 user 485.55 system 3612.18 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 08:46:44 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9045BD5 for ; Mon, 19 Nov 2012 08:46:44 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id A325F8FC12 for ; Mon, 19 Nov 2012 08:46:43 +0000 (UTC) Received: from [195.93.240.5] (port=11124 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaMeR-000FXj-S5 for current@freebsd.org; Mon, 19 Nov 2012 12:24:20 +0400 Message-ID: <50A9ECB3.8010209@lissyara.su> Date: Mon, 19 Nov 2012 12:24:19 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: current@freebsd.org Subject: No ATA disks on 9.1-RC3 Content-Type: multipart/mixed; boundary="------------060705060105040601060203" X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 08:46:45 -0000 This is a multi-part message in MIME format. --------------060705060105040601060203 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit I try update my laptop - Compaq 6715s from 9.0 to 9.1-rc3 it cannot boot, because no HDD found dmesg from 9.0/9.1 and pciconf in attached files --------------060705060105040601060203 Content-Type: text/plain; charset=UTF-8; name="dmesg.9.0.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.9.0.txt" 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.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: AMD Turion(tm) 64 X2 Mobile Technology TL-60 (1995.05-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60f82 Family = f Model = 68 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f real memory = 4294967296 (4096 MB) avail memory = 3953205248 (3770 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Error: 32/64X address mismatch in Pm2ControlBlock: 0x00008800/0x0000000000008100, using 32 (20110527/tbfadt-457) ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported acpi0: reservation of 0, 8000000 (3) failed acpi0: reservation of 100000, fff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pcib0: Length mismatch for 3 range: 11ff000 vs 11fefff pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1 pcib2: at device 4.0 on pci0 pci16: on pcib2 bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 bge0: CHIP ID 0x0000c002; ASIC REV 0x0c; CHIP REV 0xc0; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow bge0: Ethernet address: 00:1f:29:89:38:f3 pcib3: at device 5.0 on pci0 pci32: on pcib3 pcib4: at device 6.0 on pci0 pci48: on pcib4 siba_bwn0: mem 0xc8000000-0xc8003fff irq 18 at device 0.0 on pci48 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages ahci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ohci0: mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0 usbus0: on ohci0 ohci1: mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0 usbus1: on ohci1 ohci2: mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0 usbus2: on ohci2 ohci3: mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0 usbus3: on ohci3 ohci4: mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0 usbus4: on ohci4 ehci0: mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0 ehci0: AMD SB600/700 quirk applied usbus5: EHCI version 1.0 usbus5: on ehci0 pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 ata0: on atapci0 hdac0: irq 16 at device 20.2 on pci0 isab0: at device 20.3 on pci0 isa0: on isab0 pcib5: at device 20.4 on pci0 pci2: on pcib5 cbb0: mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 battery0: on acpi0 battery1: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71,0x72-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range acpi_throttle0: on cpu0 powernow0: on cpu0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 powernow1: on cpu1 Timecounters tick every 1.000 msec hdac0: HDA Codec #0: Analog Devices AD1981HD hdac0: HDA Codec #1: Lucent/Agere Systems (Unknown) pcm0: at cad 0 nid 1 on hdac0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 SMP: AP CPU #1 Launched! cd0 at ata0 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray open Root mount waiting for: usbus5 Root mount waiting for: usbus5 Root mount waiting for: usbus5 Root mount waiting for: usbus5 uhub5: 10 ports with 10 removable, self powered Root mount waiting for: usbus5 Trying to mount root from ufs:/dev/label/rootFS [rw,async]... ugen0.2: at usbus0 WARNING: TMPFS is considered to be a highly experimental feature in FreeBSD. bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) wlan0: Ethernet address: 00:21:00:0a:64:8f bwn0: status of RF switch is changed to OFF ubt0: on usbus0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.19 drm0: on vgapci0 info: [drm] MSI enabled 1 message(s) info: [drm] Initialized radeon 1.31.0 20080613 info: [drm] Setting GART location based on new memory map info: [drm] Loading RS690/RS740 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs --------------060705060105040601060203 Content-Type: text/plain; charset=UTF-8; name="dmesg.9.1.rc3.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.9.1.rc3.txt" After Disable 0 255 N 0 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 9 Validation 0 255 N 0 9 After Disable 0 255 N 0 9 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 10 11 Validation 0 255 N 0 10 11 After Disable 0 255 N 0 10 11 pcib0: port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xc0000000-0xfedfffff pcib0: Length mismatch for 3 range: 11ff000 vs 11fefff pcib0: decoding 3 range 0xfee01000-0xffffffff pcib0: decoding 3 range 0xd3000-0xdffff pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x1002, dev=0x7910, revid=0x00 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2220, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7912, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x7914, revid=0x00 domain=0, bus=0, slot=4, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x7915, revid=0x00 domain=0, bus=0, slot=5, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x7916, revid=0x00 domain=0, bus=0, slot=6, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) powerspec 3 supports D0 D3 current D0 MSI supports 1 message found-> vendor=0x1002, dev=0x4380, revid=0x00 domain=0, bus=0, slot=18, func=0 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x9000, size 3, enabled pcib0: allocated type 4 (0x9000-0x9007) for rid 10 of pci0:0:18:0 map[14]: type I/O Port, range 32, base 0x9008, size 2, enabled pcib0: allocated type 4 (0x9008-0x900b) for rid 14 of pci0:0:18:0 map[18]: type I/O Port, range 32, base 0x9010, size 3, enabled pcib0: allocated type 4 (0x9010-0x9017) for rid 18 of pci0:0:18:0 map[1c]: type I/O Port, range 32, base 0x5018, size 2, enabled pcib0: allocated type 4 (0x5018-0x501b) for rid 1c of pci0:0:18:0 map[20]: type I/O Port, range 32, base 0x5020, size 4, enabled pcib0: allocated type 4 (0x5020-0x502f) for rid 20 of pci0:0:18:0 map[24]: type Memory, range 32, base 0xd0409000, size 10, enabled pcib0: allocated type 3 (0xd0409000-0xd04093ff) for rid 24 of pci0:0:18:0 pcib0: matched entry for 0.18.INTA pcib0: slot 18 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4387, revid=0x00 domain=0, bus=0, slot=19, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Memory, range 32, base 0xd0401000, size 12, enabled pcib0: allocated type 3 (0xd0401000-0xd0401fff) for rid 10 of pci0:0:19:0 pcib0: matched entry for 0.19.INTA pcib0: slot 19 INTA hardwired to IRQ 23 found-> vendor=0x1002, dev=0x4388, revid=0x00 domain=0, bus=0, slot=19, func=1 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type Memory, range 32, base 0xd0402000, size 12, enabled pcib0: allocated type 3 (0xd0402000-0xd0402fff) for rid 10 of pci0:0:19:1 pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4389, revid=0x00 domain=0, bus=0, slot=19, func=2 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[10]: type Memory, range 32, base 0xd0403000, size 12, enabled pcib0: allocated type 3 (0xd0403000-0xd0403fff) for rid 10 of pci0:0:19:2 pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 17 found-> vendor=0x1002, dev=0x438a, revid=0x00 domain=0, bus=0, slot=19, func=3 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type Memory, range 32, base 0xd0404000, size 12, enabled pcib0: allocated type 3 (0xd0404000-0xd0404fff) for rid 10 of pci0:0:19:3 pcib0: matched entry for 0.19.INTB pcib0: slot 19 INTB hardwired to IRQ 17 found-> vendor=0x1002, dev=0x438b, revid=0x00 domain=0, bus=0, slot=19, func=4 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02a0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 map[10]: type Memory, range 32, base 0xd0405000, size 12, enabled pcib0: allocated type 3 (0xd0405000-0xd0405fff) for rid 10 of pci0:0:19:4 pcib0: matched entry for 0.19.INTC pcib0: slot 19 INTC hardwired to IRQ 17 found-> vendor=0x1002, dev=0x4386, revid=0x00 domain=0, bus=0, slot=19, func=5 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0406000, size 8, enabled pcib0: allocated type 3 (0xd0406000-0xd04060ff) for rid 10 of pci0:0:19:5 pcib0: matched entry for 0.19.INTD pcib0: slot 19 INTD hardwired to IRQ 23 found-> vendor=0x1002, dev=0x4385, revid=0x14 domain=0, bus=0, slot=20, func=0 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0003, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type I/O Port, range 32, base 0x8200, size 4, enabled pcib0: allocated type 4 (0x8200-0x820f) for rid 10 of pci0:0:20:0 found-> vendor=0x1002, dev=0x438c, revid=0x00 domain=0, bus=0, slot=20, func=1 class=01-01-82, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0220, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:20:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:20:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:20:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:20:1 map[20]: type I/O Port, range 32, base 0x5040, size 4, enabled pcib0: allocated type 4 (0x5040-0x504f) for rid 20 of pci0:0:20:1 pcib0: matched entry for 0.20.INTA pcib0: slot 20 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x4383, revid=0x00 domain=0, bus=0, slot=20, func=2 class=04-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0410, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 64, base 0xd0408000, size 14, enabled pcib0: matched entry for 0.20.INTA pcib0: slot 20 INTA hardwired to IRQ 16 found-> vendor=0x1002, dev=0x438d, revid=0x00 domain=0, bus=0, slot=20, func=3 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1002, dev=0x4384, revid=0x00 domain=0, bus=0, slot=20, func=4 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0027, statreg=0x02a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1100, revid=0x00 domain=0, bus=0, slot=24, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1101, revid=0x00 domain=0, bus=0, slot=24, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1102, revid=0x00 domain=0, bus=0, slot=24, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1022, dev=0x1103, revid=0x00 domain=0, bus=0, slot=24, func=3 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib1: at device 1.0 on pci0 pcib0: allocated type 4 (0x4000-0x4fff) for rid 1c of pcib1 pcib0: allocated type 3 (0xd0200000-0xd03fffff) for rid 20 of pcib1 pcib0: allocated type 3 (0xc0000000-0xc7ffffff) for rid 24 of pcib1 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x4000-0x4fff pcib1: memory decode 0xd0200000-0xd03fffff pcib1: prefetched decode 0xc0000000-0xc7ffffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x1002, dev=0x791f, revid=0x00 domain=0, bus=1, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Prefetchable Memory, range 64, base 0xc0000000, size 27, enabled pcib1: allocated prefetch range (0xc0000000-0xc7ffffff) for rid 10 of pci0:1:5:0 map[18]: type Memory, range 64, base 0xd0200000, size 16, enabled pcib1: allocated memory range (0xd0200000-0xd020ffff) for rid 18 of pci0:1:5:0 map[20]: type I/O Port, range 32, base 0x4000, size 8, enabled pcib1: allocated I/O port range (0x4000-0x40ff) for rid 20 of pci0:1:5:0 map[24]: type Memory, range 32, base 0xd0300000, size 20, enabled pcib1: allocated memory range (0xd0300000-0xd03fffff) for rid 24 of pci0:1:5:0 pcib1: matched entry for 1.5.INTB pcib1: slot 5 INTB hardwired to IRQ 19 vgapci0: port 0x4000-0x40ff mem 0xc0000000-0xc7ffffff,0xd0200000-0xd020ffff,0xd0300000-0xd03fffff irq 19 at device 5.0 on pci1 pcib2: at device 4.0 on pci0 pcib0: allocated type 3 (0xd0000000-0xd00fffff) for rid 20 of pcib2 pcib2: domain 0 pcib2: secondary bus 16 pcib2: subordinate bus 16 pcib2: memory decode 0xd0000000-0xd00fffff pcib2: no prefetched decode pcib2: could not get PCI interrupt routing table for \\_SB_.C08B.C250 - AE_NOT_FOUND pci16: on pcib2 pci16: domain=0, physical bus=16 found-> vendor=0x14e4, dev=0x1713, revid=0x02 domain=0, bus=16, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xd0000000, size 16, enabled pcib2: allocated memory range (0xd0000000-0xd000ffff) for rid 10 of pci0:16:0:0 pcib0: matched entry for 0.4.INTA pcib0: slot 4 INTA hardwired to IRQ 16 pcib2: slot 0 INTA is routed to irq 16 bge0: mem 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 bge0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 51 bge0: using IRQ 256 for MSI bge0: CHIP ID 0x0000c002; ASIC REV 0x0c; CHIP REV 0xc0; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x0050ef, model 0x0004, rev. 0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow bge0: bpf attached bge0: Ethernet address: 00:1f:29:89:38:f3 pcib3: at device 5.0 on pci0 pcib0: allocated type 4 (0x2000-0x3fff) for rid 1c of pcib3 pcib0: allocated type 3 (0xcc000000-0xcfffffff) for rid 20 of pcib3 pcib3: domain 0 pcib3: secondary bus 32 pcib3: subordinate bus 32 pcib3: I/O decode 0x2000-0x3fff pcib3: memory decode 0xcc000000-0xcfffffff pcib3: no prefetched decode pcib3: could not get PCI interrupt routing table for \\_SB_.C08B.C255 - AE_NOT_FOUND pci32: on pcib3 pci32: domain=0, physical bus=32 pcib4: at device 6.0 on pci0 pcib0: allocated type 3 (0xc8000000-0xc80fffff) for rid 20 of pcib4 pcib4: domain 0 pcib4: secondary bus 48 pcib4: subordinate bus 48 pcib4: memory decode 0xc8000000-0xc80fffff pcib4: no prefetched decode pcib4: could not get PCI interrupt routing table for \\_SB_.C08B.C25F - AE_NOT_FOUND pci48: on pcib4 pci48: domain=0, physical bus=48 found-> vendor=0x14e4, dev=0x4312, revid=0x02 domain=0, bus=48, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xc8000000, size 14, enabled pcib4: allocated memory range (0xc8000000-0xc8003fff) for rid 10 of pci0:48:0:0 pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 18 pcib4: slot 0 INTA is routed to irq 18 pci48: at device 0.0 (no driver attached) ahci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported with FBS ahci0: Caps: ?Gbps FBS 2cmd 1ports ahcich0: at channel 0 on ahci0 ahcich0: Caps: FBSCP ahcich1: at channel 1 on ahci0 ahcich1: Caps: FBSCP ahcich2: not probed (disabled) ahcich3: not probed (disabled) ahcich4: not probed (disabled) ahcich5: not probed (disabled) ahcich6: not probed (disabled) ahcich7: at channel 7 on ahci0 device_attach: ahcich7 attach returned 6 ahcich8: at channel 8 on ahci0 device_attach: ahcich8 attach returned 6 ahcich9: at channel 9 on ahci0 device_attach: ahcich9 attach returned 6 ahcich10: at channel 10 on ahci0 device_attach: ahcich10 attach returned 6 ahcich11: at channel 11 on ahci0 device_attach: ahcich11 attach returned 6 ahcich12: at channel 12 on ahci0 device_attach: ahcich12 attach returned 6 ahcich13: at channel 13 on ahci0 device_attach: ahcich13 attach returned 6 ahcich14: at channel 14 on ahci0 device_attach: ahcich14 attach returned 6 ahcich15: at channel 15 on ahci0 device_attach: ahcich15 attach returned 6 ahcich16: not probed (disabled) ahcich17: not probed (disabled) ahcich18: not probed (disabled) ahcich19: not probed (disabled) ahcich20: not probed (disabled) ahcich21: at channel 21 on ahci0 device_attach: ahcich21 attach returned 6 ahcich22: not probed (disabled) ahcich23: not probed (disabled) ahcich24: at channel 24 on ahci0 device_attach: ahcich24 attach returned 6 ahcich25: at channel 25 on ahci0 device_attach: ahcich25 attach returned 6 ahcich26: at channel 26 on ahci0 device_attach: ahcich26 attach returned 6 ahcich27: not probed (disabled) ahcich28: at channel 28 on ahci0 device_attach: ahcich28 attach returned 6 ahcich29: at channel 29 on ahci0 device_attach: ahcich29 attach returned 6 ahcich30: at channel 30 on ahci0 device_attach: ahcich30 attach returned 6 ahcich31: at channel 31 on ahci0 device_attach: ahcich31 attach returned 6 ahcich32: at channel 32 on ahci0 device_attach: ahcich32 attach returned 6 ahcich33: at channel 33 on ahci0 device_attach: ahcich33 attach returned 6 ahcich34: not probed (disabled) ahcich35: not probed (disabled) ahcich36: not probed (disabled) ahcich37: not probed (disabled) ahcich38: not probed (disabled) ahcich39: at channel 39 on ahci0 device_attach: ahcich39 attach returned 6 ahcich40: at channel 40 on ahci0 device_attach: ahcich40 attach returned 6 ahcich41: at channel 41 on ahci0 device_attach: ahcich41 attach returned 6 ahcich42: at channel 42 on ahci0 device_attach: ahcich42 attach returned 6 ahcich43: at channel 43 on ahci0 device_attach: ahcich43 attach returned 6 ahcich44: at channel 44 on ahci0 device_attach: ahcich44 attach returned 6 ahcich45: at channel 45 on ahci0 device_attach: ahcich45 attach returned 6 ahcich46: at channel 46 on ahci0 device_attach: ahcich46 attach returned 6 ahcich47: at channel 47 on ahci0 device_attach: ahcich47 attach returned 6 ahcich48: not probed (disabled) ahcich49: not probed (disabled) ahcich50: not probed (disabled) ahcich51: not probed (disabled) ahcich52: not probed (disabled) ahcich53: at channel 53 on ahci0 device_attach: ahcich53 attach returned 6 ahcich54: not probed (disabled) ahcich55: not probed (disabled) ahcich56: at channel 56 on ahci0 device_attach: ahcich56 attach returned 6 ahcich57: at channel 57 on ahci0 device_attach: ahcich57 attach returned 6 ahcich58: at channel 58 on ahci0 device_attach: ahcich58 attach returned 6 ahcich59: not probed (disabled) ahcich60: at channel 60 on ahci0 device_attach: ahcich60 attach returned 6 ahcich61: at channel 61 on ahci0 device_attach: ahcich61 attach returned 6 ahcich62: at channel 62 on ahci0 device_attach: ahcich62 attach returned 6 ahcich63: at channel 63 on ahci0 device_attach: ahcich63 attach returned 6 ohci0: mem 0xd0401000-0xd0401fff irq 23 at device 19.0 on pci0 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 53 usbus0 on ohci0 usbus0: bpf attached ohci0: usbpf: Attached ohci1: mem 0xd0402000-0xd0402fff irq 17 at device 19.1 on pci0 ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 0 vector 54 usbus1 on ohci1 usbus1: bpf attached ohci1: usbpf: Attached ohci2: mem 0xd0403000-0xd0403fff irq 17 at device 19.2 on pci0 usbus2 on ohci2 usbus2: bpf attached ohci2: usbpf: Attached ohci3: mem 0xd0404000-0xd0404fff irq 17 at device 19.3 on pci0 usbus3 on ohci3 usbus3: bpf attached ohci3: usbpf: Attached ohci4: mem 0xd0405000-0xd0405fff irq 17 at device 19.4 on pci0 usbus4 on ohci4 usbus4: bpf attached ohci4: usbpf: Attached ehci0: mem 0xd0406000-0xd04060ff irq 23 at device 19.5 on pci0 ehci0: AMD SB600/700 quirk applied ehci0: Dropped interrupts workaround enabled usbus5: EHCI version 1.0 usbus5 on ehci0 usbus5: bpf attached ehci0: usbpf: Attached pci0: at device 20.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x5040-0x504f irq 16 at device 20.1 on pci0 ata0: at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 55 hdac0: irq 16 at device 20.2 on pci0 hdac0: HDA Driver Revision: 20120126_0002 hdac0: Config options: on=0x00000000 off=0x00000000 pcib0: allocated type 3 (0xc8100000-0xc8103fff) for rid 10 of hdac0 hdac0: Lazy allocation of 0x4000 bytes rid 0x10 type 3 at 0xc8100000 hdac0: Caps: OSS 4, ISS 4, BSS 0, NSDO 1, 64bit, CORB 256, RIRB 256 isab0: at device 20.3 on pci0 isa0: on isab0 pcib5: at device 20.4 on pci0 pcib0: allocated type 3 (0xd0100000-0xd01fffff) for rid 20 of pcib5 pcib5: domain 0 pcib5: secondary bus 2 pcib5: subordinate bus 3 pcib5: memory decode 0xd0100000-0xd01fffff pcib5: no prefetched decode pcib5: Subtractively decoded bridge. pci2: on pcib5 pci2: domain=0, physical bus=2 found-> vendor=0x1180, dev=0x0476, revid=0xb6 domain=0, bus=2, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0007, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xd0100000, size 12, enabled pcib5: allocated memory range (0xd0100000-0xd0100fff) for rid 10 of pci0:2:4:0 pcib5: matched entry for 2.4.INTA pcib5: slot 4 INTA hardwired to IRQ 20 cbb0: mem 0xd0100000-0xd0100fff irq 20 at device 4.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 0 vector 56 cbb0: PCI Configuration space: 0x00: 0x04761180 0x02100007 0x060700b6 0x00824000 0x10: 0xd0100000 0x020000dc 0x20030302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000114 0x40: 0x30c2103c 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x30a00001 0x00000000 0x04630463 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000008 0x00000000 0x00000000 0x00000000 0xb0: 0x00000000 0xbe000000 0x00003000 0x00000000 0xc0: 0x30c2103c 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 battery0: on acpi0 battery1: on acpi0 acpi_acad0: on acpi0 acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 57 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0065 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 58 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00004000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 acpi0: wakeup code va 0xffffff810f9cc000 pa 0x90000 ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 2: ioport 0x2c00 alloc failed ahc_isa_probe 3: ioport 0x3c00 alloc failed ahc_isa_probe 4: ioport 0x4c00 alloc failed ahc_isa_probe 5: ioport 0x5c00 alloc failed ahc_isa_probe 6: ioport 0x6c00 alloc failed ahc_isa_probe 7: ioport 0x7c00 alloc failed ahc_isa_probe 8: ioport 0x8c00 alloc failed ahc_isa_probe 9: ioport 0x9c00 alloc failed ahc_isa_probe 10: ioport 0xac00 alloc failed ahc_isa_probe 11: ioport 0xbc00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 pcib0: allocated type 3 (0xd3000-0xd37ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd3800-0xd3fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd4000-0xd47ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd4800-0xd4fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd5000-0xd57ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd5800-0xd5fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd6000-0xd67ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd6800-0xd6fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd7000-0xd77ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd7800-0xd7fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd8000-0xd87ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd8800-0xd8fff) for rid 1 of orm0 pcib0: allocated type 3 (0xd9000-0xd97ff) for rid 1 of orm0 pcib0: allocated type 3 (0xd9800-0xd9fff) for rid 1 of orm0 pcib0: allocated type 3 (0xda000-0xda7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xda800-0xdafff) for rid 1 of orm0 pcib0: allocated type 3 (0xdb000-0xdb7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdb800-0xdbfff) for rid 1 of orm0 pcib0: allocated type 3 (0xdc000-0xdc7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdc800-0xdcfff) for rid 1 of orm0 pcib0: allocated type 3 (0xdd000-0xdd7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdd800-0xddfff) for rid 1 of orm0 pcib0: allocated type 3 (0xde000-0xde7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xde800-0xdefff) for rid 1 of orm0 pcib0: allocated type 3 (0xdf000-0xdf7ff) for rid 1 of orm0 pcib0: allocated type 3 (0xdf800-0xdffff) for rid 1 of orm0 isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xd0000-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0 pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x3f8-0x3ff) for rid 0 of uart0 uart0 failed to probe at port 0x3f8-0x3ff irq 4 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices ctl: CAM Target Layer loaded acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x8010 powernow0: on cpu0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 powernow1: on cpu1 Device configuration finished. procfs registered lapic: Divisor 2, Frequency 99750291 Hz Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached hptrr: no controller detected. hdacc0: at cad 0 on hdac0 hdacc0: Root Node at nid=0: 1 subnodes 1-1 hdaa0: at nid 1 on hdacc0 hdaa0: Audio Function Group at nid=1: 30 subnodes 2-31 hdaa0: NumGPIO=4 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdaa0: GPIO0: disabled hdaa0: GPIO1: disabled hdaa0: GPIO2: disabled hdaa0: GPIO3: disabled hdaa0: WARNING: nid=2 has cnid outside of the AFG range j=0 entnum=4 index=0 res=0x00000401 hdaa0: Original pins configuration: hdaa0: nid 0x as seq device conn jack loc color misc hdaa0: 5 92174110 1 0 Speaker Fixed Analog 0x12 Green 1 hdaa0: 6 0421201f 1 15 Headphones Jack 1/8 Right Grey 0 hdaa0: 7 410710f0 15 0 Line-out None Analog Rear Black 0 hdaa0: 8 04a12020 2 0 Mic Jack 1/8 Right Grey 0 hdaa0: 9 0181302e 2 14 Line-in Jack 1/8 Rear Blue 0 hdaa0: 10 4145f0f0 15 0 SPDIF-out None Optical Rear Other 0 hdaa0: 22 995711f0 15 0 Digital-out Fixed Analog Onboard Black 1 hdaa0: 23 5993e0f0 15 0 AUX None ATAPI Onboard White 0 hdaa0: 24 f0a79159 5 9 Mic Both Analog Other Pink 1 hdaa0: 25 593310f0 15 0 CD None ATAPI Onboard Black 0 hdaa0: Patched pins configuration: hdaa0: nid 0x as seq device conn jack loc color misc hdaa0: 5 92174110 1 0 Speaker Fixed Analog 0x12 Green 1 hdaa0: 6 0421201f 1 15 Headphones Jack 1/8 Right Grey 0 hdaa0: 7 410710f0 15 0 Line-out None Analog Rear Black 0 DISA hdaa0: 8 04a12020 2 0 Mic Jack 1/8 Right Grey 0 hdaa0: 9 0181302e 2 14 Line-in Jack 1/8 Rear Blue 0 hdaa0: 10 4145f0f0 15 0 SPDIF-out None Optical Rear Other 0 DISA hdaa0: 22 995711f0 15 0 Digital-out Fixed Analog Onboard Black 1 hdaa0: 23 5993e0f0 15 0 AUX None ATAPI Onboard White 0 DISA hdaa0: 24 f0a79159 5 9 Mic Both Analog Other Pink 1 hdaa0: 25 593310f0 15 0 CD None ATAPI Onboard Black 0 DISA hdaa0: 4 associations found: hdaa0: Association 0 (1) out: hdaa0: Pin nid=5 seq=0 hdaa0: Pin nid=6 seq=15 hdaa0: Association 1 (2) in: hdaa0: Pin nid=8 seq=0 hdaa0: Pin nid=9 seq=14 hdaa0: Association 2 (5) in: hdaa0: Pin nid=24 seq=9 hdaa0: Association 3 (15) out: hdaa0: Pin nid=22 seq=0 hdaa0: Tracing association 0 (1) hdaa0: Pin 5 traced to DAC 3 hdaa0: Pin 6 traced to DAC 3 and hpredir 0 hdaa0: Association 0 (1) trace succeeded hdaa0: Tracing association 1 (2) hdaa0: Pin 8 traced to ADC 4 hdaa0: Pin 9 traced to ADC 4 hdaa0: Association 1 (2) trace succeeded hdaa0: Tracing association 2 (5) hdaa0: Association 2 (5) trace failed hdaa0: Tracing association 3 (15) hdaa0: Unable to trace pin 22 seq 0 with min nid 0 hdaa0: Association 3 (15) trace failed hdaa0: Looking for additional DAC for association 0 (1) hdaa0: Looking for additional ADC for association 1 (2) hdaa0: Tracing input monitor hdaa0: Tracing nid 12 to out hdaa0: Tracing other input monitors hdaa0: Tracing nid 8 to out hdaa0: nid 8 is input monitor hdaa0: Tracing nid 9 to out hdaa0: nid 9 is input monitor hdaa0: Tracing beeper hdaa0: nid 16 traced to out hdaa0: Headphones redirection for association 0 nid=6 using unsolicited responses. hdaa0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ivref hdaa0: hdaa0: +-------------------+ hdaa0: | DUMPING HDA NODES | hdaa0: +-------------------+ hdaa0: hdaa0: Default Parameter hdaa0: ----------------- hdaa0: Stream cap: 0x00000001 hdaa0: PCM hdaa0: PCM cap: 0x000e007f hdaa0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz hdaa0: IN amp: 0x00270300 hdaa0: OUT amp: 0x80053f3d hdaa0: hdaa0: nid: 2 [DISABLED] hdaa0: Name: audio output hdaa0: Widget cap: 0x00030311 hdaa0: DIGITAL STEREO hdaa0: Stream cap: 0x00000005 hdaa0: AC3 PCM hdaa0: PCM cap: 0x00020060 hdaa0: 16 bits, 44 48 KHz hdaa0: connections: 2 hdaa0: | hdaa0: + [DISABLED] <- nid=1 [GHOST!] [UNKNOWN] (selected) hdaa0: + <- nid=4 [audio input] hdaa0: hdaa0: nid: 3 hdaa0: Name: audio output hdaa0: Widget cap: 0x00000441 hdaa0: PWR PROC STEREO hdaa0: Association: 0 (0x00008001) hdaa0: OSS: pcm (pcm) hdaa0: Stream cap: 0x00000001 hdaa0: PCM hdaa0: PCM cap: 0x000e007f hdaa0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz hdaa0: hdaa0: nid: 4 hdaa0: Name: audio input hdaa0: Widget cap: 0x00100511 hdaa0: PWR STEREO hdaa0: Association: 1 (0x00004001) hdaa0: Stream cap: 0x00000001 hdaa0: PCM hdaa0: PCM cap: 0x0006007f hdaa0: 16 20 bits, 8 11 16 22 32 44 48 KHz hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=21 [audio selector] hdaa0: hdaa0: nid: 5 hdaa0: Name: pin: Speaker (Fixed) hdaa0: Widget cap: 0x00400187 hdaa0: UNSOL STEREO hdaa0: Association: 0 (0x00000001) hdaa0: Pin cap: 0x0001173f hdaa0: ISC TRQD PDC HP OUT IN VREF[ 50 80 GROUND HIZ ] EAPD hdaa0: Pin config: 0x92174110 hdaa0: Pin control: 0x00000040 OUT hdaa0: EAPD: 0x00000002 hdaa0: Output amp: 0x80053f3d hdaa0: mute=1 step=63 size=5 offset=61 hdaa0: Input amp: 0x00270300 hdaa0: mute=0 step=3 size=39 offset=0 hdaa0: connections: 2 hdaa0: | hdaa0: + [DISABLED] <- nid=3 [audio output] hdaa0: + <- nid=14 [audio mixer] (selected) hdaa0: hdaa0: nid: 6 hdaa0: Name: pin: Headphones (Grey Jack) hdaa0: Widget cap: 0x00400185 hdaa0: UNSOL STEREO hdaa0: Association: 0 (0x00008000) hdaa0: Pin cap: 0x0000001f hdaa0: ISC TRQD PDC HP OUT hdaa0: Pin config: 0x0421201f hdaa0: Pin control: 0x000000c0 HP OUT hdaa0: Output amp: 0x80053f3d hdaa0: mute=1 step=63 size=5 offset=61 hdaa0: connections: 2 hdaa0: | hdaa0: + [DISABLED] <- nid=3 [audio output] hdaa0: + <- nid=14 [audio mixer] (selected) hdaa0: hdaa0: nid: 7 [DISABLED] hdaa0: Name: pin: Line-out (None) hdaa0: Widget cap: 0x00400104 hdaa0: Pin cap: 0x00000010 hdaa0: OUT hdaa0: Pin config: 0x410710f0 hdaa0: Pin control: 0x00000000 hdaa0: Output amp: 0x80053f3d hdaa0: mute=1 step=63 size=5 offset=61 hdaa0: connections: 1 hdaa0: | hdaa0: + [DISABLED] <- nid=15 [audio mixer] [DISABLED] hdaa0: hdaa0: nid: 8 hdaa0: Name: pin: Mic (Grey Jack) hdaa0: Widget cap: 0x00400083 hdaa0: UNSOL STEREO hdaa0: Association: 1 (0x00000001) hdaa0: OSS: mic (mic) hdaa0: Pin cap: 0x00001727 hdaa0: ISC TRQD PDC IN VREF[ 50 80 GROUND HIZ ] hdaa0: Pin config: 0x04a12020 hdaa0: Pin control: 0x00000024 IN VREFs hdaa0: Input amp: 0x00270300 hdaa0: mute=0 step=3 size=39 offset=0 hdaa0: hdaa0: nid: 9 hdaa0: Name: pin: Line-in (Blue Jack) hdaa0: Widget cap: 0x00400187 hdaa0: UNSOL STEREO hdaa0: Association: 1 (0x00004000) hdaa0: OSS: line (line) hdaa0: Pin cap: 0x00001737 hdaa0: ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ] hdaa0: Pin config: 0x0181302e hdaa0: Pin control: 0x00000024 IN VREFs hdaa0: Output amp: 0x80053f3d hdaa0: mute=1 step=63 size=5 offset=61 hdaa0: Input amp: 0x00270300 hdaa0: mute=0 step=3 size=39 offset=0 hdaa0: connections: 2 hdaa0: | hdaa0: + [DISABLED] <- nid=3 [audio output] (selected) hdaa0: + [DISABLED] <- nid=14 [audio mixer] hdaa0: hdaa0: nid: 10 [DISABLED] hdaa0: Name: pin: SPDIF-out (None) hdaa0: Widget cap: 0x00400301 hdaa0: DIGITAL STEREO hdaa0: Pin cap: 0x00000010 hdaa0: OUT hdaa0: Pin config: 0x4145f0f0 hdaa0: Pin control: 0x00000000 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=2 [audio output] [DISABLED] hdaa0: hdaa0: nid: 11 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x00300101 hdaa0: STEREO hdaa0: connections: 6 hdaa0: | hdaa0: + <- nid=3 [audio output] (selected) hdaa0: + <- nid=12 [audio mixer] hdaa0: + <- nid=9 [pin: Line-in (Blue Jack)] hdaa0: + <- nid=14 [audio mixer] hdaa0: + <- nid=5 [pin: Speaker (Fixed)] hdaa0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdaa0: hdaa0: nid: 12 hdaa0: Name: audio mixer hdaa0: Widget cap: 0x00200101 hdaa0: STEREO hdaa0: Association: 1 (0x00000001) hdaa0: OSS: mic hdaa0: connections: 2 hdaa0: | hdaa0: + <- nid=30 [audio selector] hdaa0: + [DISABLED] <- nid=31 [audio selector] [DISABLED] hdaa0: hdaa0: nid: 13 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010c hdaa0: Association: -2 (0x00000000) hdaa0: OSS: speaker hdaa0: Output amp: 0x800b0f0f hdaa0: mute=1 step=15 size=11 offset=15 hdaa0: connections: 2 hdaa0: | hdaa0: + <- nid=16 [beep widget] (selected) hdaa0: + [DISABLED] <- nid=22 [pin: Digital-out (Fixed)] [DISABLED] hdaa0: hdaa0: nid: 14 hdaa0: Name: audio mixer hdaa0: Widget cap: 0x00200101 hdaa0: STEREO hdaa0: Association: 0 (0x00008001) hdaa0: OSS: pcm, speaker, line, mic hdaa0: connections: 8 hdaa0: | hdaa0: + <- nid=13 [audio selector] hdaa0: + <- nid=17 [audio selector] hdaa0: + <- nid=18 [audio selector] hdaa0: + <- nid=19 [audio selector] hdaa0: + [DISABLED] <- nid=26 [audio selector] [DISABLED] hdaa0: + [DISABLED] <- nid=27 [audio selector] [DISABLED] hdaa0: + [DISABLED] <- nid=28 [audio selector] [DISABLED] hdaa0: + [DISABLED] <- nid=29 [audio selector] [DISABLED] hdaa0: hdaa0: nid: 15 [DISABLED] hdaa0: Name: audio mixer hdaa0: Widget cap: 0x00200100 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=11 [audio selector] [DISABLED] hdaa0: hdaa0: nid: 16 hdaa0: Name: beep widget hdaa0: Widget cap: 0x00700000 hdaa0: Association: -2 (0x00000000) hdaa0: OSS: speaker (speaker) hdaa0: hdaa0: nid: 17 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Association: 0 (0x00008001) hdaa0: OSS: pcm hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=3 [audio output] hdaa0: hdaa0: nid: 18 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Association: -2 (0x00000000) hdaa0: OSS: mic hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=8 [pin: Mic (Grey Jack)] hdaa0: hdaa0: nid: 19 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Association: -2 (0x00000000) hdaa0: OSS: line hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=9 [pin: Line-in (Blue Jack)] hdaa0: hdaa0: nid: 20 [DISABLED] hdaa0: Name: power widget hdaa0: Widget cap: 0x00500500 hdaa0: PWR hdaa0: connections: 13 hdaa0: | hdaa0: + <- nid=13 [audio selector] (selected) hdaa0: + <- nid=14 [audio mixer] hdaa0: + <- nid=15 [audio mixer] [DISABLED] hdaa0: + <- nid=16 [beep widget] hdaa0: + <- nid=19 [audio selector] hdaa0: + <- nid=20 [power widget] [DISABLED] hdaa0: + <- nid=21 [audio selector] hdaa0: + <- nid=22 [pin: Digital-out (Fixed)] [DISABLED] hdaa0: + <- nid=23 [pin: AUX (None)] [DISABLED] hdaa0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdaa0: + <- nid=25 [pin: CD (None)] [DISABLED] hdaa0: + <- nid=26 [audio selector] [DISABLED] hdaa0: + <- nid=29 [audio selector] [DISABLED] hdaa0: hdaa0: nid: 21 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Association: 1 (0x00004001) hdaa0: OSS: line, mic hdaa0: Output amp: 0x80050f00 hdaa0: mute=1 step=15 size=5 offset=0 hdaa0: connections: 8 hdaa0: | hdaa0: + <- nid=12 [audio mixer] hdaa0: + <- nid=9 [pin: Line-in (Blue Jack)] (selected) hdaa0: + [DISABLED] <- nid=14 [audio mixer] hdaa0: + [DISABLED] <- nid=15 [audio mixer] [DISABLED] hdaa0: + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED] hdaa0: + [DISABLED] <- nid=5 [pin: Speaker (Fixed)] hdaa0: + [DISABLED] <- nid=24 [pin: Mic (Both)] [DISABLED] hdaa0: + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED] hdaa0: hdaa0: nid: 22 [DISABLED] hdaa0: Name: pin: Digital-out (Fixed) hdaa0: Widget cap: 0x00400000 hdaa0: Pin cap: 0x00000020 hdaa0: IN hdaa0: Pin config: 0x995711f0 hdaa0: Pin control: 0x00000000 hdaa0: hdaa0: nid: 23 [DISABLED] hdaa0: Name: pin: AUX (None) hdaa0: Widget cap: 0x00400081 hdaa0: UNSOL STEREO hdaa0: Pin cap: 0x00000027 hdaa0: ISC TRQD PDC IN hdaa0: Pin config: 0x5993e0f0 hdaa0: Pin control: 0x00000000 hdaa0: hdaa0: nid: 24 [DISABLED] hdaa0: Name: pin: Mic (Both) hdaa0: Widget cap: 0x00400187 hdaa0: UNSOL STEREO hdaa0: Pin cap: 0x00001737 hdaa0: ISC TRQD PDC OUT IN VREF[ 50 80 GROUND HIZ ] hdaa0: Pin config: 0xf0a79159 hdaa0: Pin control: 0x00000000 hdaa0: Output amp: 0x80053f3d hdaa0: mute=1 step=63 size=5 offset=61 hdaa0: Input amp: 0x00270300 hdaa0: mute=0 step=3 size=39 offset=0 hdaa0: connections: 2 hdaa0: | hdaa0: + [DISABLED] <- nid=3 [audio output] (selected) hdaa0: + <- nid=14 [audio mixer] hdaa0: hdaa0: nid: 25 [DISABLED] hdaa0: Name: pin: CD (None) hdaa0: Widget cap: 0x00400001 hdaa0: STEREO hdaa0: Pin cap: 0x00000020 hdaa0: IN hdaa0: Pin config: 0x593310f0 hdaa0: Pin control: 0x00000000 hdaa0: hdaa0: nid: 26 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=5 [pin: Speaker (Fixed)] hdaa0: hdaa0: nid: 27 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + [DISABLED] <- nid=23 [pin: AUX (None)] [DISABLED] hdaa0: hdaa0: nid: 28 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdaa0: hdaa0: nid: 29 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Output amp: 0x80051f17 hdaa0: mute=1 step=31 size=5 offset=23 hdaa0: connections: 1 hdaa0: | hdaa0: + [DISABLED] <- nid=25 [pin: CD (None)] [DISABLED] hdaa0: hdaa0: nid: 30 hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Association: 1 (0x00000001) hdaa0: OSS: mic hdaa0: Output amp: 0x80000000 hdaa0: mute=1 step=0 size=0 offset=0 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=8 [pin: Mic (Grey Jack)] hdaa0: hdaa0: nid: 31 [DISABLED] hdaa0: Name: audio selector hdaa0: Widget cap: 0x0030010d hdaa0: STEREO hdaa0: Output amp: 0x80000000 hdaa0: mute=1 step=0 size=0 offset=0 hdaa0: connections: 1 hdaa0: | hdaa0: + <- nid=24 [pin: Mic (Both)] [DISABLED] hdaa0: pcm0: at nid 5,6 and 8,9 on hdaa0 pcm0: +--------------------------------------+ pcm0: | DUMPING PCM Playback/Record Channels | pcm0: +--------------------------------------+ pcm0: pcm0: Playback: pcm0: pcm0: Stream cap: 0x00000001 pcm0: PCM pcm0: PCM cap: 0x000e007f pcm0: 16 20 24 bits, 8 11 16 22 32 44 48 KHz pcm0: DAC: 3 pcm0: pcm0: Record: pcm0: pcm0: Stream cap: 0x00000001 pcm0: PCM pcm0: PCM cap: 0x0006007f pcm0: 16 20 bits, 8 11 16 22 32 44 48 KHz pcm0: DAC: 4 pcm0: pcm0: +-------------------------------+ pcm0: | DUMPING Playback/Record Paths | pcm0: +-------------------------------+ pcm0: pcm0: Playback: pcm0: pcm0: nid=5 [pin: Speaker (Fixed)] pcm0: | pcm0: + <- nid=14 [audio mixer] [src: pcm, speaker, line, mic] pcm0: | pcm0: + <- nid=13 [audio selector] [src: speaker] pcm0: | pcm0: + <- nid=16 [beep widget] [src: speaker] pcm0: + <- nid=17 [audio selector] [src: pcm] pcm0: | pcm0: + <- nid=3 [audio output] [src: pcm] pcm0: + <- nid=18 [audio selector] [src: mic] pcm0: | pcm0: + <- nid=8 [pin: Mic (Grey Jack)] [src: mic] pcm0: + <- nid=19 [audio selector] [src: line] pcm0: | pcm0: + <- nid=9 [pin: Line-in (Blue Jack)] [src: line] pcm0: pcm0: nid=6 [pin: Headphones (Grey Jack)] pcm0: | pcm0: + <- nid=14 [audio mixer] [src: pcm, speaker, line, mic] pcm0: | pcm0: + <- nid=13 [audio selector] [src: speaker] pcm0: | pcm0: + <- nid=16 [beep widget] [src: speaker] pcm0: + <- nid=17 [audio selector] [src: pcm] pcm0: | pcm0: + <- nid=3 [audio output] [src: pcm] pcm0: + <- nid=18 [audio selector] [src: mic] pcm0: | pcm0: + <- nid=8 [pin: Mic (Grey Jack)] [src: mic] pcm0: + <- nid=19 [audio selector] [src: line] pcm0: | pcm0: + <- nid=9 [pin: Line-in (Blue Jack)] [src: line] pcm0: pcm0: Record: pcm0: pcm0: nid=4 [audio input] pcm0: | pcm0: + <- nid=21 [audio selector] [src: line, mic] pcm0: | pcm0: + <- nid=12 [audio mixer] [src: mic] pcm0: | pcm0: + <- nid=30 [audio selector] [src: mic] pcm0: | pcm0: + <- nid=8 [pin: Mic (Grey Jack)] [src: mic] pcm0: + <- nid=9 [pin: Line-in (Blue Jack)] [src: line] pcm0: pcm0: +-------------------------+ pcm0: | DUMPING Volume Controls | pcm0: +-------------------------+ pcm0: pcm0: Master Volume (OSS: vol): -91/3dB pcm0: | pcm0: +- ctl 1 (nid 5 in ): -91/3dB (64 steps) + mute pcm0: +- ctl 3 (nid 6 in ): -91/3dB (64 steps) + mute pcm0: +- ctl 8 (nid 13 out): -45/0dB (16 steps) + mute pcm0: +- ctl 9 (nid 17 out): -34/12dB (32 steps) + mute pcm0: +- ctl 10 (nid 18 out): -34/12dB (32 steps) + mute pcm0: +- ctl 11 (nid 19 out): -34/12dB (32 steps) + mute pcm0: pcm0: PCM Volume (OSS: pcm): -34/12dB pcm0: | pcm0: +- ctl 9 (nid 17 out): -34/12dB (32 steps) + mute pcm0: pcm0: Microphone Volume (OSS: mic): 0/30dB pcm0: | pcm0: +- ctl 5 (nid 8 out): 0/30dB (4 steps) pcm0: +- ctl 10 (nid 18 out): -34/12dB (32 steps) + mute pcm0: +- ctl 12 (nid 21 out): 0/22dB (16 steps) + mute pcm0: +- ctl 19 (nid 30 out): mute pcm0: pcm0: Line-in Volume (OSS: line): 0/30dB pcm0: | pcm0: +- ctl 7 (nid 9 out): 0/30dB (4 steps) pcm0: +- ctl 11 (nid 19 out): -34/12dB (32 steps) + mute pcm0: +- ctl 12 (nid 21 out): 0/22dB (16 steps) + mute pcm0: pcm0: Speaker/Beep Volume (OSS: speaker): -45/0dB pcm0: | pcm0: +- ctl 8 (nid 13 out): -45/0dB (16 steps) + mute pcm0: pcm0: Recording Level (OSS: rec): 0/22dB pcm0: | pcm0: +- ctl 12 (nid 21 out): 0/22dB (16 steps) + mute pcm0: +- ctl 19 (nid 30 out): mute pcm0: pcm0: Input Monitoring Level (OSS: igain): -34/0dB pcm0: | pcm0: +- ctl 8 (nid 13 out): -45/0dB (16 steps) + mute pcm0: +- ctl 10 (nid 18 out): -34/12dB (32 steps) + mute pcm0: +- ctl 11 (nid 19 out): -34/12dB (32 steps) + mute pcm0: pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "ogain": pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap 13ff80000, 10000; 0xffffff810f9e4000 -> 13ff80000 pcm0: sndbuf_setmap 13ff00000, 10000; 0xffffff810fa24000 -> 13ff00000 hdacc1: at cad 1 on hdac0 hdacc1: Root Node at nid=0: 1 subnodes 1-1 unknown: at nid 1 on hdacc1 (no driver attached) usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 acpi_tz0: _AC1: temperature 66.0 >= setpoint 60.0 acpi_tz0: switched from NONE to _AC1: 66.0C ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ahcich0: AHCI reset... ahcich0: SATA connect time=100us status=00000123 ahcich0: AHCI reset: device found ahcich1: AHCI reset... ahcich1: SATA connect timeout time=10000us status=00000000 ahcich1: AHCI reset: device not found ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 battery0: battery initialization start battery1: battery initialization start acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 acpi_tz0: _AC3: temperature 66.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 66.0 >= setpoint 50.0 battery0: battery initialization done, tried 1 times uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered ahcich0: AHCI reset: device ready after 400ms ahcich0: Poll timeout on slot 0 port 0 ahcich0: is 00000000 cs 00000001 ss 00000000 rs 00000001 tfd 150 serr 00000000 cmd 00002007 (aprobe0:ahcich0:0:0:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich0:0:0:0): CAM status: Command timeout (aprobe0:ahcich0:0:0:0): Error 5, Retries exhausted acpi_tz0: _AC3: temperature 68.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 68.0 >= setpoint 50.0 pass0 at ata0 bus 0 scbus2 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0 at ata0 bus 0 scbus2 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [350977 x 2048 byte records] GEOM: new disk cd0 SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x80050010 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 1 vector 48 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 1 vector 49 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 1 vector 50 ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 1 vector 51 msi: Assigning MSI IRQ 256 to local APIC 1 vector 52 TSC timecounter discards lower 7 bit(s) Timecounter "TSC-low" frequency 15586345 Hz quality -100 Root mount waiting for: usbus5 uhub5: 10 ports with 10 removable, self powered Root mount waiting for: usbus5 ugen0.2: at usbus0 ugen5.2: at usbus5 umass0: on usbus5 umass0: SCSI over Bulk-Only; quirks = 0x4001 umass0:4:0:-1: Attached to scbus4 Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? pass1 at umass-sim0 bus 0 scbus4 target 0 lun 0 pass1: Removable Direct Access SCSI-0 device pass1: Serial Number 058F0O1111B1 pass1: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: Serial Number 058F0O1111B1 da0: 40.000MB/s transfers da0: 14MB (29120 512 byte sectors: 64H 32S/T 14C) start_init: trying /sbin/init acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC2: temperature 59.0 >= setpoint 50.0 acpi_tz0: switched from _AC1 to _AC2: 59.0C acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 59.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 53.0 >= setpoint 40.0 battery1: battery initialization failed, giving up ubt0: on usbus0 acpi_tz0: _AC3: temperature 54.0 >= setpoint 40.0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() acpi_tz0: _AC3: temperature 55.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 56.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 acpi_tz0: _AC3: temperature 57.0 >= setpoint 40.0 --------------060705060105040601060203 Content-Type: text/plain; charset=UTF-8; name="pciconf.9.0.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pciconf.9.0.txt" lissyara@HP:/home/lissyara % su root@HP:/home/lissyara # pciconf -lvcb hostb0@pci0:0:0:0: class=0x060000 card=0x30c2103c chip=0x79101002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RS690 Host Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc' device = 'RS690 PCI to PCI Bridge (Internal gfx)' class = bridge subclass = PCI-PCI cap 08[44] = HT MSI fixed address window enabled at 0xfee00000 cap 0d[b0] = PCI Bridge card=0x30c2103c pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc' class = bridge subclass = PCI-PCI cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[58] = PCI-Express 1 root port max data 128(128) link x1(x1) cap 05[80] = MSI supports 1 message cap 0d[b0] = PCI Bridge card=0x30c2103c cap 08[b8] = HT MSI fixed address window enabled at 0xfee00000 ecap 0002[100] = VC 1 max VC0 pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc' device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' class = bridge subclass = PCI-PCI cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[58] = PCI-Express 1 root port max data 128(128) link x16(x1) cap 05[80] = MSI supports 1 message cap 0d[b0] = PCI Bridge card=0x30c2103c cap 08[b8] = HT MSI fixed address window enabled at 0xfee00000 ecap 0002[100] = VC 1 max VC0 pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc' device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' class = bridge subclass = PCI-PCI cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 10[58] = PCI-Express 1 root port max data 128(128) link x1(x1) cap 05[80] = MSI supports 1 message cap 0d[b0] = PCI Bridge card=0x30c2103c cap 08[b8] = HT MSI fixed address window enabled at 0xfee00000 ecap 0002[100] = VC 1 max VC0 ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 Non-Raid-5 SATA' class = mass storage subclass = ATA bar [10] = type I/O Port, range 32, base 0x9000, size 8, enabled bar [14] = type I/O Port, range 32, base 0x9008, size 4, enabled bar [18] = type I/O Port, range 32, base 0x9010, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x5018, size 4, enabled bar [20] = type I/O Port, range 32, base 0x5020, size 16, enabled bar [24] = type Memory, range 32, base 0xd0409000, size 1024, enabled cap 01[60] = powerspec 2 supports D0 D3 current D0 ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB (OHCI0)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0401000, size 4096, enabled ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB (OHCI1)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0402000, size 4096, enabled ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB (OHCI2)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0403000, size 4096, enabled ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB (OHCI3)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0404000, size 4096, enabled ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB (OHCI4)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0405000, size 4096, enabled ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 USB Controller (EHCI)' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xd0406000, size 256, enabled cap 01[c0] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 0a[e4] = EHCI Debug Port at offset 0xe0 in map 0x14 none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 rev=0x14 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SBx00 SMBus Controller' class = serial bus subclass = SMBus bar [10] = type I/O Port, range 32, base 0x8200, size 16, enabled cap 08[b0] = HT MSI fixed address window disabled at 0xfee00000 atapci0@pci0:0:20:1: class=0x010182 card=0x30c2103c chip=0x438c1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 IDE' class = mass storage subclass = ATA bar [20] = type I/O Port, range 32, base 0x5040, size 16, enabled hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SBx00 Azalia (Intel HDA)' class = multimedia subclass = HDA bar [10] = type Memory, range 64, base 0xc8100000, size 16384, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SB600 PCI to LPC Bridge' class = bridge subclass = PCI-ISA pcib5@pci0:0:20:4: class=0x060401 card=0x00000000 chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'ATI Technologies Inc' device = 'SBx00 PCI to PCI Bridge' class = bridge subclass = PCI-PCI hostb1@pci0:0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI cap 08[80] = HT host hostb2@pci0:0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] Miscellaneous Control' class = bridge subclass = HOST-PCI cap 0f[f0] = unknown vgapci0@pci0:1:5:0: class=0x030000 card=0x30c2103c chip=0x791f1002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'RS690M [Radeon X1200 Series]' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 64, base 0xc0000000, size 134217728, enabled bar [18] = type Memory, range 64, base 0xd0200000, size 65536, enabled bar [20] = type I/O Port, range 32, base 0x4000, size 256, enabled bar [24] = type Memory, range 32, base 0xd0300000, size 1048576, enabled cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[80] = MSI supports 1 message, 64 bit enabled with 1 message bge0@pci0:16:0:0: class=0x020000 card=0x30c2103c chip=0x171314e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetLink BCM5906M Fast Ethernet PCI Express' class = network subclass = ethernet bar [10] = type Memory, range 64, base 0xd0000000, size 65536, enabled cap 01[48] = powerspec 3 supports D0 D3 current D0 cap 03[50] = VPD cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[13c] = VC 1 max VC0 ecap 0003[160] = Serial 1 001f29fffe8938f3 siba_bwn0@pci0:48:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4311 802.11a/b/g' class = network bar [10] = type Memory, range 64, base 0xc8000000, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0002[13c] = VC 1 max VC0 ecap 0003[160] = Serial 1 648f00ffff0a0021 ecap 0004[16c] = unknown 1 cbb0@pci0:2:4:0: class=0x060700 card=0x30c2103c chip=0x04761180 rev=0xb6 hdr=0x02 vendor = 'Ricoh Co Ltd' device = 'RL5c476 II' class = bridge subclass = PCI-CardBus bar [10] = type Memory, range 32, base 0xd0100000, size 4096, enabled cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 root@HP:/home/lissyara # --------------060705060105040601060203-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 08:59:11 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4ADE81B1 for ; Mon, 19 Nov 2012 08:59:11 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0ABA08FC0C for ; Mon, 19 Nov 2012 08:59:10 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so8155811iea.13 for ; Mon, 19 Nov 2012 00:59:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dIch/M9wq3+jYpYJ6xsYOgBX3SXV7ei+DN5XZnDPg4I=; b=JBWypsGAm/lU29oiEaHpE8PieWSvGo10OxhiMpYHjOEQt/HmkEno4AfRSutWq1wxhk L7dtFmN54v1vLi3EZB0GeF3oj8CZHil8Hcigj2+Elhgp3h2D7fSpN/udNfTiN1buRFbr ZVYCuA9F+DkaM/HuS/NXpShL2hhhsrPDs5Q0Mw5KGGAIC5WYo0P1sLfQRgYc8kGnp4D2 Zk+ROzphNw3Sg+xktjWQP/6PT0ECd/yChtjef8dtuD1qq315uJUOtcJO9LiKAqzY1Ken Rjo2Hxgmaz9t1WwOED4P9eBv7dULlsPoVFz0qEjk0zXdaj7ChUUBUo+1rgAyCZ8Ce1IM myHw== Received: by 10.43.125.133 with SMTP id gs5mr10468748icc.54.1353315550297; Mon, 19 Nov 2012 00:59:10 -0800 (PST) Received: from [192.168.1.132] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id u4sm7301009igw.6.2012.11.19.00.59.08 (version=SSLv3 cipher=OTHER); Mon, 19 Nov 2012 00:59:09 -0800 (PST) Message-ID: <50A9F4D7.3050204@gmail.com> Date: Mon, 19 Nov 2012 10:59:03 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121116 Thunderbird/16.0.2 MIME-Version: 1.0 To: Alex Keda Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> In-Reply-To: <50A9ECB3.8010209@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 08:59:11 -0000 19.11.2012 10:24, Alex Keda wrote: > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad4 Looking for this one? ATA_CAM was made default for now. -- Sphinx of black quartz, judge my vow. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 09:20:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13D77879 for ; Mon, 19 Nov 2012 09:20:01 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id C765C8FC08 for ; Mon, 19 Nov 2012 09:20:00 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so8182446iea.13 for ; Mon, 19 Nov 2012 01:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=xy/qJxrtjknqycMaFYJB13/eOqxrK/jV1ZEPe7AG2z0=; b=Il7yGGh0SvjJmsMf7sjJk6E6L08T/CZcj3iKtJd76HAo6k37QymNcOyJEEGRAsoiBk WDv/im5W7JFqqe47IoXIZFHWZAXiVyVYXtMWMnv4oBZWTw5xwXgjosgfEQblkOYAbUDn /3ItRNZEpfT9R6UH86BmEidmkIfLG8qwOg7/gpB6DoL/0UM5roKj/lOujlS4R/F6jRW2 4oql2MRrsQ6KGA0z3KXRfCNjVGYvoBxesrt7BhCk1YiGNNlwR6rB6zODL5GY/jhQg1Lu 7JSsBbRSl03uPbizPeX8+2Zw1uy88KtrIrWs9WQ1g4VZuUA9gH0+PMGwR5saOPP8aAby 0Q6Q== Received: by 10.42.180.10 with SMTP id bs10mr10253029icb.39.1353316800444; Mon, 19 Nov 2012 01:20:00 -0800 (PST) Received: from [192.168.1.132] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id gz10sm7324378igc.9.2012.11.19.01.19.58 (version=SSLv3 cipher=OTHER); Mon, 19 Nov 2012 01:19:59 -0800 (PST) Message-ID: <50A9F9BC.8000903@gmail.com> Date: Mon, 19 Nov 2012 11:19:56 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121116 Thunderbird/16.0.2 MIME-Version: 1.0 Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> In-Reply-To: <50A9F4D7.3050204@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Alex Keda , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 09:20:01 -0000 19.11.2012 10:59, Volodymyr Kostyrko wrote: > 19.11.2012 10:24, Alex Keda wrote: >> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 >> ada0: ATA-8 SATA 2.x device >> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >> ada0: Command Queueing enabled >> ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) >> ada0: Previously was known as ad4 > > Looking for this one? ATA_CAM was made default for now. Damn I'm sorry. Looks like I need my coffee back... The change actually is at: > ahci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported and > ahci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 > ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported with FBS > ahci0: Caps: ?Gbps FBS 2cmd 1ports The bad thing about that is that there was no major rewrite of ahci code in this timeframe. There are some point that can be checked though: 1. What is your BIOS settings for controller? Can you try switching it between Legacy/Compatible mode? There was a change that fixed behavior for detecting different BIOS settings. 2. You can try using modular driver for this one, this means adding this to kernel: nodevice ata device atacore device ataati device ataahci -- Sphinx of black quartz, judge my vow. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 09:56:31 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F8F4E90 for ; Mon, 19 Nov 2012 09:56:31 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id 4E98F8FC14 for ; Mon, 19 Nov 2012 09:56:30 +0000 (UTC) Received: from [195.93.240.5] (port=13072 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaO5c-00087L-RW for current@freebsd.org; Mon, 19 Nov 2012 13:56:28 +0400 Message-ID: <50AA024C.4010100@lissyara.su> Date: Mon, 19 Nov 2012 13:56:28 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: current@freebsd.org Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> <50A9F9BC.8000903@gmail.com> In-Reply-To: <50A9F9BC.8000903@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 09:56:31 -0000 19.11.2012 13:19, Volodymyr Kostyrko пишет: > 19.11.2012 10:59, Volodymyr Kostyrko wrote: >> 19.11.2012 10:24, Alex Keda wrote: >>> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 >>> ada0: ATA-8 SATA 2.x device >>> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >>> ada0: Command Queueing enabled >>> ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) >>> ada0: Previously was known as ad4 >> >> Looking for this one? ATA_CAM was made default for now. > > Damn I'm sorry. Looks like I need my coffee back... > > The change actually is at: > > > ahci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > > ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported > > and > > > ahci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 > > ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported > with FBS > > ahci0: Caps: ?Gbps FBS 2cmd 1ports > > The bad thing about that is that there was no major rewrite of ahci > code in this timeframe. There are some point that can be checked though: > > 1. What is your BIOS settings for controller? Can you try switching it > between Legacy/Compatible mode? There was a change that fixed behavior > for detecting different BIOS settings. BIOS does not have SATA controller settings From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 10:31:31 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10B377C4 for ; Mon, 19 Nov 2012 10:31:31 +0000 (UTC) (envelope-from mailer-daemon@vniz.net) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 76AF88FC16 for ; Mon, 19 Nov 2012 10:31:30 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so1798948lbb.13 for ; Mon, 19 Nov 2012 02:31:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:openpgp :content-type:x-gm-message-state; bh=TxDm+o/754fTVGUn0BlMU67h82PYfsiU24I5CQgUjNs=; b=I5uPSK/vIvRzEL+7j3GhF4WJYzEbRUHgiTMO2tQ0x4+eASEH2WRS2jeywG5w7oBBsK iacqT0ULSfO7VqDEjNvDAMluceADHaZ9suDrYFUey2dXnH4dAKhAcY0Mjbxo0whHKyCT TicKJYznOFM8ATbqbAuU5m/sv+7GBIUFsnrr+7FI2yv5+um+hPoOziF5pI+G9okeDbSo v5oioW1imA0JBNYYvJXfkPlczSSIVCRg9Uam9siSOxuhyIOxcHSqryI9jir00ECxxQEI Aay6NXK8vKHIp7Vo5vGNISqPSC4MDI80wQZmxZ7BNN7P9ZzX0Gh7ftuB8J7/KJeeNbFy 4UbA== Received: by 10.112.102.230 with SMTP id fr6mr4893967lbb.112.1353321086793; Mon, 19 Nov 2012 02:31:26 -0800 (PST) Received: from [192.168.1.2] ([89.169.163.3]) by mx.google.com with ESMTPS id z9sm3404746lby.8.2012.11.19.02.31.25 (version=SSLv3 cipher=OTHER); Mon, 19 Nov 2012 02:31:26 -0800 (PST) Message-ID: <50AA0A69.1080901@freebsd.org> Date: Mon, 19 Nov 2012 14:31:05 +0400 From: Andrey Chernov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Hiroki Sato Subject: Re: Tons of "sa6_recoverscope: assumption failure" on recent -current References: <50A88D0E.1070301@freebsd.org> <20121119.165954.1302634823989942540.hrs@allbsd.org> In-Reply-To: <20121119.165954.1302634823989942540.hrs@allbsd.org> OpenPGP: id=964474DD Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1555CDEE5C4EB8ED636C0551" X-Gm-Message-State: ALoCoQlnZA2hPakeTKP2hD3unxPW57km7SZREVS2zMVMcVFrMtCDQJ4I9s/+w+VR746b+0ox58oA Cc: rene@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 10:31:31 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1555CDEE5C4EB8ED636C0551 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 19.11.2012 11:59, Hiroki Sato wrote: > This warning message itself is not harmful actually, but my commit > triggered it. It should be fixed at r243235. Can you let me know if > this problem persists even at this revision or later? Thank you. I see no such messages after boot at r243235, thanx. --------------enig1555CDEE5C4EB8ED636C0551 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iEYEARECAAYFAlCqCn0ACgkQVg5YK5ZEdN3X/ACbBQcbHn62VkqOAm4l5GwddtqF /GcAoJIt1+gQyb3ZVUBf3O9XP8STGx3t =09tf -----END PGP SIGNATURE----- --------------enig1555CDEE5C4EB8ED636C0551-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 13:00:38 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 82F6E322; Mon, 19 Nov 2012 13:00:38 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 813B58FC08; Mon, 19 Nov 2012 13:00:37 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA13645; Mon, 19 Nov 2012 15:00:16 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TaQxU-000CY9-3b; Mon, 19 Nov 2012 15:00:16 +0200 Message-ID: <50AA2D5D.7080105@FreeBSD.org> Date: Mon, 19 Nov 2012 15:00:13 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Bartosz Stec , Guido Falsi Subject: Re: problem booting to multi-vdev root pool References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66701.701@madpilot.net> <50A82B3A.6020608@it4pro.pl> <50A8CB1C.9090907@FreeBSD.org> In-Reply-To: <50A8CB1C.9090907@FreeBSD.org> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 13:00:38 -0000 on 18/11/2012 13:48 Andriy Gapon said the following: > on 18/11/2012 02:26 Bartosz Stec said the following: >> W dniu 2012-11-16 17:17, Guido Falsi pisze: >>> On 11/16/12 16:45, Andriy Gapon wrote: >>>> Guido, Bartosz, >>>> could you please test the patch? >>> >>> I have just compiler an r242910 kernel with this patch (and just this one) >>> applied. >>> >>> System booted so it seems to work fine! :) >> I've just compiled and installed fresh kernel with your patch, system booted >> without any problems, so apparently patch works as intended. > > Thank you both very much for testing! > Committed as r243213. > BTW, if you have some spare time and a desire to do some more testing, you can try the following patch: http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_support.diff It adds support for multi-vdev root pool probing in kernel. The best way to test is to remove zpool.cache before rebooting (but make sure to keep a copy somewhere and be able to recover). I'd use a boot environment (a root filesystem clone) for this. Thank you. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 13:01:45 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D147C4AC for ; Mon, 19 Nov 2012 13:01:45 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id 5EA388FC12 for ; Mon, 19 Nov 2012 13:01:44 +0000 (UTC) Received: from [195.93.240.5] (port=4647 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaQyr-0002Q0-NA for current@freebsd.org; Mon, 19 Nov 2012 17:01:41 +0400 Message-ID: <50AA2DB5.6000502@lissyara.su> Date: Mon, 19 Nov 2012 17:01:41 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: current@freebsd.org Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> <50A9F9BC.8000903@gmail.com> In-Reply-To: <50A9F9BC.8000903@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 13:01:46 -0000 19.11.2012 13:19, Volodymyr Kostyrko пишет: > 19.11.2012 10:59, Volodymyr Kostyrko wrote: >> 19.11.2012 10:24, Alex Keda wrote: >>> ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 >>> ada0: ATA-8 SATA 2.x device >>> ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) >>> ada0: Command Queueing enabled >>> ada0: 152627MB (312581809 512 byte sectors: 16H 63S/T 16383C) >>> ada0: Previously was known as ad4 >> >> Looking for this one? ATA_CAM was made default for now. > > Damn I'm sorry. Looks like I need my coffee back... > > The change actually is at: > > > ahci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > > ahci0: AHCI v1.10 with 4 3Gbps ports, Port Multiplier not supported > > and > > > ahci0: port > 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f > mem 0xd0409000-0xd04093ff irq 16 at device 18.0 on pci0 > > ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 52 > > ahci0: AHCI v0.00 with 1 ?Gbps ports, Port Multiplier not supported > with FBS > > ahci0: Caps: ?Gbps FBS 2cmd 1ports > > The bad thing about that is that there was no major rewrite of ahci > code in this timeframe. There are some point that can be checked though: > > 1. What is your BIOS settings for controller? Can you try switching it > between Legacy/Compatible mode? There was a change that fixed behavior > for detecting different BIOS settings. > > 2. You can try using modular driver for this one, this means adding > this to kernel: > > nodevice ata > device atacore > device ataati > device ataahci > It's not build config: =========== root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP # include GENERIC ident HPKERNEL nodevice ata nodevice siis device atacore device ataati device ataahci ============= error: ============= MAKE=make sh /usr/src/sys/conf/newvers.sh HPKERNEL /usr/local/bin/svnversion cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector vers.c linking kernel.debug ata-ahci.o: In function `ata_ahci_ata_attach': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:128: undefined reference to `ata_pci_ch_attach' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:129: undefined reference to `ata_pci_ch_detach' ata-ahci.o: In function `ata_ahci_probe': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:97: undefined reference to `ata_pcivendor2str' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:100: undefined reference to `ata_pcivendor2str' ata-ahci.o: In function `ata_ahci_chipinit': /usr/src/sys/dev/ata/chipsets/ata-ahci.c:165: undefined reference to `ata_generic_intr' /usr/src/sys/dev/ata/chipsets/ata-ahci.c:165: undefined reference to `ata_setup_interrupt' ata-ahci.o:(.data+0x1c0): undefined reference to `ata_pci_devclass' ata-ahci.o:(.data+0x200): undefined reference to `ata_pci_devclass' ata-ahci.o:(.data+0x2c8): undefined reference to `ata_pci_detach' ata-ahci.o:(.data+0x2d8): undefined reference to `ata_pci_suspend' ata-ahci.o:(.data+0x2e8): undefined reference to `ata_pci_resume' ata-ahci.o:(.data+0x308): undefined reference to `ata_pci_read_ivar' ata-ahci.o:(.data+0x318): undefined reference to `ata_pci_write_ivar' ata-ahci.o:(.data+0x328): undefined reference to `ata_pci_alloc_resource' ata-ahci.o:(.data+0x338): undefined reference to `ata_pci_release_resource' ata-ahci.o:(.data+0x368): undefined reference to `ata_pci_setup_intr' ata-ahci.o:(.data+0x378): undefined reference to `ata_pci_teardown_intr' ata-ahci.o:(.data+0x3b8): undefined reference to `ata_pci_attach' ata-ahci.o:(.data+0x3c8): undefined reference to `ata_pci_detach' ata-ahci.o:(.data+0x3d8): undefined reference to `ata_pci_suspend' ata-ahci.o:(.data+0x3e8): undefined reference to `ata_pci_resume' ata-ahci.o:(.data+0x408): undefined reference to `ata_pci_read_ivar' ata-ahci.o:(.data+0x418): undefined reference to `ata_pci_write_ivar' ata-ahci.o:(.data+0x428): undefined reference to `ata_pci_alloc_resource' ata-ahci.o:(.data+0x438): undefined reference to `ata_pci_release_resource' ata-ahci.o:(.data+0x468): undefined reference to `ata_pci_setup_intr' ata-ahci.o:(.data+0x478): undefined reference to `ata_pci_teardown_intr' ata-ahci.o:(.data+0x488): undefined reference to `ata_pci_read_config' ata-ahci.o:(.data+0x498): undefined reference to `ata_pci_write_config' ata-ahci.o:(.data+0x4a8): undefined reference to `ata_pci_print_child' ata-ahci.o:(.data+0x4b8): undefined reference to `ata_pci_child_location_str' ata-ati.o: In function `ata_ati_chipinit': /usr/src/sys/dev/ata/chipsets/ata-ati.c:131: undefined reference to `ata_generic_intr' /usr/src/sys/dev/ata/chipsets/ata-ati.c:131: undefined reference to `ata_setup_interrupt' ata-ati.o: In function `ata_ati_ixp700_ch_attach': /usr/src/sys/dev/ata/chipsets/ata-ati.c:195: undefined reference to `ata_pci_ch_attach' ata-ati.o: In function `ata_ati_dumb_ch_attach': /usr/src/sys/dev/ata/chipsets/ata-ati.c:181: undefined reference to `ata_pci_ch_attach' ata-ati.o: In function `ata_ati_probe': /usr/src/sys/dev/ata/chipsets/ata-ati.c:99: undefined reference to `ata_match_chip' /usr/src/sys/dev/ata/chipsets/ata-ati.c:102: undefined reference to `ata_set_desc' ata-ati.o: In function `ata_ati_setmode': /usr/src/sys/dev/ata/chipsets/ata-ati.c:254: undefined reference to `ata_mode2idx' ata-ati.o:(.data+0x1c0): undefined reference to `ata_pci_devclass' ata-ati.o:(.data+0x238): undefined reference to `ata_pci_attach' ata-ati.o:(.data+0x248): undefined reference to `ata_pci_detach' ata-ati.o:(.data+0x258): undefined reference to `ata_pci_suspend' ata-ati.o:(.data+0x268): undefined reference to `ata_pci_resume' ata-ati.o:(.data+0x288): undefined reference to `ata_pci_read_ivar' ata-ati.o:(.data+0x298): undefined reference to `ata_pci_write_ivar' ata-ati.o:(.data+0x2a8): undefined reference to `ata_pci_alloc_resource' ata-ati.o:(.data+0x2b8): undefined reference to `ata_pci_release_resource' ata-ati.o:(.data+0x2e8): undefined reference to `ata_pci_setup_intr' ata-ati.o:(.data+0x2f8): undefined reference to `ata_pci_teardown_intr' ata-ati.o:(.data+0x308): undefined reference to `ata_pci_read_config' ata-ati.o:(.data+0x318): undefined reference to `ata_pci_write_config' ata-ati.o:(.data+0x328): undefined reference to `ata_pci_print_child' ata-ati.o:(.data+0x338): undefined reference to `ata_pci_child_location_str' ata-siliconimage.o: In function `ata_sii_probe': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:112: undefined reference to `ata_match_chip' /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:115: undefined reference to `ata_set_desc' ata-siliconimage.o: In function `ata_cmd_ch_attach': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:237: undefined reference to `ata_pci_ch_attach' ata-siliconimage.o: In function `ata_sii_ch_detach': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:358: undefined reference to `ata_pci_dmafini' ata-siliconimage.o: In function `ata_sii_ch_attach': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:344: undefined reference to `ata_pci_hw' /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:349: undefined reference to `ata_pci_dmainit' ata-siliconimage.o: In function `ata_sii_chipinit': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:125: undefined reference to `ata_generic_intr' /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:125: undefined reference to `ata_setup_interrupt' /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:223: undefined reference to `ata_pci_ch_detach' ata-siliconimage.o: In function `ata_sii_setmode': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:448: undefined reference to `ata_mode2idx' ata-siliconimage.o: In function `ata_cmd_setmode': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:295: undefined reference to `ata_mode2idx' ata-siliconimage.o: In function `ata_sii_status': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:376: undefined reference to `ata_pci_status' ata-siliconimage.o: In function `ata_cmd_status': /usr/src/sys/dev/ata/chipsets/ata-siliconimage.c:260: undefined reference to `ata_pci_status' ata-siliconimage.o:(.data+0x140): undefined reference to `ata_pci_devclass' ata-siliconimage.o:(.data+0x1b8): undefined reference to `ata_pci_attach' ata-siliconimage.o:(.data+0x1c8): undefined reference to `ata_pci_detach' ata-siliconimage.o:(.data+0x1d8): undefined reference to `ata_pci_suspend' ata-siliconimage.o:(.data+0x1e8): undefined reference to `ata_pci_resume' ata-siliconimage.o:(.data+0x208): undefined reference to `ata_pci_read_ivar' ata-siliconimage.o:(.data+0x218): undefined reference to `ata_pci_write_ivar' ata-siliconimage.o:(.data+0x228): undefined reference to `ata_pci_alloc_resource' ata-siliconimage.o:(.data+0x238): undefined reference to `ata_pci_release_resource' ata-siliconimage.o:(.data+0x268): undefined reference to `ata_pci_setup_intr' ata-siliconimage.o:(.data+0x278): undefined reference to `ata_pci_teardown_intr' ata-siliconimage.o:(.data+0x288): undefined reference to `ata_pci_read_config' ata-siliconimage.o:(.data+0x298): undefined reference to `ata_pci_write_config' ata-siliconimage.o:(.data+0x2a8): undefined reference to `ata_pci_print_child' ata-siliconimage.o:(.data+0x2b8): undefined reference to `ata_pci_child_location_str' *** [kernel.debug] Error code 1 Stop in /usr/obj/usr/src/sys/HP. *** [buildkernel] Error code 1 Stop in /usr/src. *** [buildkernel] Error code 1 Stop in /usr/src. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 13:18:29 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0FDA26A for ; Mon, 19 Nov 2012 13:18:29 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8127B8FC15 for ; Mon, 19 Nov 2012 13:18:29 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so174871iec.13 for ; Mon, 19 Nov 2012 05:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4B1e6DluZX65UVZdOFD9cG3L2Iqfr1IBkcjO63HVWws=; b=JNUgOEEXtHBHSXcMQ22pe6rCumUWRO/pPcGgKFtsdh0Brd28qXT/7Fb11zoiMV1heA aOujrRmyR8EfRYTg916ZY8aCv3D2ucA2KwkrkBXHQNwuoWN/1ZXlK5mxXVLQ17LBbn3c mu0DRYO8mjnw4b9bOITggwMngbOfagKDVTy3rRNDY62KeK/MQ9ojd6B8YU5SbV/FsgGj g/AoV02XJEB+BAMeTZ20Ii1uG9OavvexvNPLWBb2/H9PChndN4/TDwkAx3TGAt5z8sTi nEthAo3yLqeZqN+NArUM7pS50bqiFFpJGht5XKFUS0jddZad4gQ9TbkBO0rRQKrJOEej uu2Q== Received: by 10.50.94.166 with SMTP id dd6mr6546100igb.38.1353331108858; Mon, 19 Nov 2012 05:18:28 -0800 (PST) Received: from [192.168.1.132] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id px5sm7076030igc.0.2012.11.19.05.18.26 (version=SSLv3 cipher=OTHER); Mon, 19 Nov 2012 05:18:28 -0800 (PST) Message-ID: <50AA319F.2000509@gmail.com> Date: Mon, 19 Nov 2012 15:18:23 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121116 Thunderbird/16.0.2 MIME-Version: 1.0 To: Alex Keda Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> <50A9F9BC.8000903@gmail.com> <50AA2DB5.6000502@lissyara.su> In-Reply-To: <50AA2DB5.6000502@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 13:18:29 -0000 19.11.2012 15:01, Alex Keda wrote: > It's not build > config: > =========== > root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP > # > include GENERIC > ident HPKERNEL > > nodevice ata > nodevice siis > device atacore > device ataati > device ataahci Looks like I have missed `device atapci` here. > ============= > > error: > ============= > MAKE=make sh /usr/src/sys/conf/newvers.sh HPKERNEL > /usr/local/bin/svnversion > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g > -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs > -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -include opt_global.h -fno-common -finline-limit=8000 --param > inline-unit-growth=100 --param large-function-growth=1000 > -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse > -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > -fstack-protector vers.c > linking kernel.debug > ata-ahci.o: In function `ata_ahci_ata_attach': > /usr/src/sys/dev/ata/chipsets/ata-ahci.c:128: undefined reference to > `ata_pci_ch_attach' -- Sphinx of black quartz, judge my vow. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 13:59:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D220548 for ; Mon, 19 Nov 2012 13:59:02 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id CD33A8FC0C for ; Mon, 19 Nov 2012 13:59:01 +0000 (UTC) Received: from [195.93.240.5] (port=6288 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaRsK-0006ur-OQ for freebsd-current@freebsd.org; Mon, 19 Nov 2012 17:59:00 +0400 Message-ID: <50AA3B24.4070008@lissyara.su> Date: Mon, 19 Nov 2012 17:59:00 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> <50A9F9BC.8000903@gmail.com> <50AA2DB5.6000502@lissyara.su> <50AA319F.2000509@gmail.com> In-Reply-To: <50AA319F.2000509@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 13:59:02 -0000 19.11.2012 17:18, Volodymyr Kostyrko пишет: > 19.11.2012 15:01, Alex Keda wrote: >> It's not build >> config: >> =========== >> root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP >> # >> include GENERIC >> ident HPKERNEL >> >> nodevice ata >> nodevice siis >> device atacore >> device ataati >> device ataahci > > Looks like I have missed `device atapci` here. OK, I rebuild kernel - no happy - error remains From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 14:26:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D1292C1A for ; Mon, 19 Nov 2012 14:26:24 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8AAEA8FC12 for ; Mon, 19 Nov 2012 14:26:24 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so323898iec.13 for ; Mon, 19 Nov 2012 06:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=JBhmxJIW5vS6uEXrf8oCirnRLiCr3fXeQIs+EgMN4Ac=; b=sCpEZBDfhXC+x0yPyFfShqLjPZCf9jEQhkZmPcVRSWn+7Dfau7t1R96bDNRfnyq1QB on4/XQ2Cpl+0Vq1QUB1qtg8jq/QRMBhL/QA5QlMM2dZeRgJHlw7oSqkrJEMS/ObcEsv6 at/qkeSvxFS026s+eYMdmqZpxb/0As+7+bPwNZjOUMlXwHWWKzyhr0tWocCr/pxeLzZA +e3XIdQ2GAugzuPgKI4jdyu254V1umVW1TpvdLj+cW89I6zTl0R24ZczHCaqnrDbbSwM uFUqbZVTLF5PIaNFeZ6gBrkplNjtIPt66Fs/qvCU6FP2tKEdR/6ibhEc5EAjLTFRMrPT VCNw== Received: by 10.50.104.230 with SMTP id gh6mr6856112igb.13.1353335177925; Mon, 19 Nov 2012 06:26:17 -0800 (PST) Received: from [192.168.1.132] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPS id 10sm7087696ign.5.2012.11.19.06.26.14 (version=SSLv3 cipher=OTHER); Mon, 19 Nov 2012 06:26:17 -0800 (PST) Message-ID: <50AA417C.4030104@gmail.com> Date: Mon, 19 Nov 2012 16:26:04 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121116 Thunderbird/16.0.2 MIME-Version: 1.0 To: Alex Keda Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> <50A9F4D7.3050204@gmail.com> <50A9F9BC.8000903@gmail.com> <50AA2DB5.6000502@lissyara.su> <50AA319F.2000509@gmail.com> <50AA3B24.4070008@lissyara.su> In-Reply-To: <50AA3B24.4070008@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 14:26:25 -0000 19.11.2012 15:59, Alex Keda wrote: > 19.11.2012 17:18, Volodymyr Kostyrko пишет: >> 19.11.2012 15:01, Alex Keda wrote: >>> It's not build >>> config: >>> =========== >>> root@HP:/usr/src # vim /usr/src/sys/amd64/conf/HP >>> # >>> include GENERIC >>> ident HPKERNEL >>> >>> nodevice ata >>> nodevice siis >>> device atacore >>> device ataati >>> device ataahci >> >> Looks like I have missed `device atapci` here. > OK, I rebuild kernel - no happy - error remains So this is rather IXP600 support problem, try hitting freebsd-stable or... freebsd-hardware? -- Sphinx of black quartz, judge my vow. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 14:29:57 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33A55E5A; Mon, 19 Nov 2012 14:29:57 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from zcs04.jnb1.cloudseed.co.za (zcs04.jnb1.cloudseed.co.za [41.154.0.161]) by mx1.freebsd.org (Postfix) with ESMTP id 7DD528FC08; Mon, 19 Nov 2012 14:29:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTP id B83342A82C1D; Mon, 19 Nov 2012 16:29:48 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs04.jnb1.cloudseed.co.za Received: from zcs04.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs04.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3gdJ8UOHr7M; Mon, 19 Nov 2012 16:29:48 +0200 (SAST) Received: from clue.co.za (unknown [41.154.88.19]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id D7DC22A82C15; Mon, 19 Nov 2012 16:29:47 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaSM6-000I0A-DW; Mon, 19 Nov 2012 16:29:46 +0200 To: Gleb Smirnoff , freebsd-current@FreeBSD.org From: Ian FREISLICH Subject: Re: netisr panic? In-Reply-To: References: <20121117213754.GI38060@FreeBSD.org> X-Attribution: BOFH Date: Mon, 19 Nov 2012 16:29:46 +0200 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 14:29:57 -0000 Ian FREISLICH wrote: > Gleb Smirnoff wrote: > > On Sat, Nov 17, 2012 at 05:07:54PM +0200, Ian FREISLICH wrote: > > I> I have this consistently with: > > I> > > I> FreeBSD firewall2.jnb1.gp-online.net 10.0-CURRENT FreeBSD 10.0-CURRENT # 30 > r243156: Fri Nov 16 20:12:33 SAST 2012 ianf@firewall2.jnb1.gp-online.net :/ > usr/obj/usr/src/sys/FIREWALL amd64 > > > > Pretty sure this is a new version of wrong byte order panic, which > > no longer can happen in HEAD. > > > > Can you please try this patch? > > It survived the night, which it hasn't managed before. I'll keep you posted. Jubilation short lived: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8050f494 stack pointer = 0x28:0xffffff84637a19d0 frame pointer = 0x28:0xffffff84637a1a10 code segment = base 0x0, limit 0xfffff, type 0x1b Fatal trap 12: page fault while in kernel mode = DPL 0, pres 1, long 1, def32 0, gran 1 cpuid = 7; apic id = 07 processor eflags = fault virtual address = 0xc interrupt enabled, fault code = supervisor read data, page not present resume, IOPL = 0 instruction pointer = 0x20:0xffffffff8050f494 stack pointer = 0x28:0xffffff846386c9d0 current process = 11 (irq261: igb0:que 0) frame pointer = 0x28:0xffffff846386ca10 trap number = 12 code segment = base 0x0, limit 0xfffff, type 0x1b panic: page fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x1ce trap_fatal() at trap_fatal+0x290 trap_pfault() at trap_pfault+0x21f trap() at trap+0x2b4 calltrap() at calltrap+0x8 --- trap 0xc, rip = 0xffffffff8050f494, rsp = 0xffffff84637a19d0, rbp = 0xffffff84637a1a10 --- ether_nh_input() at ether_nh_input+0x94 netisr_dispatch_src() at netisr_dispatch_src+0x212 igb_rxeof() at igb_rxeof+0x384 igb_msix_que() at igb_msix_que+0xfa intr_event_execute_handlers() at intr_event_execute_handlers+0xfd ithread_loop() at ithread_loop+0x9e fork_exit() at fork_exit+0x11e fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff84637a1cb0, rbp = 0 --- Uptime: 19h5m45s Dumping 2654 out of 16368 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% #0 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:266 266 if (textdump && textdump_pending) { (kgdb) #0 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:266 #1 0xffffffff8044ae64 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0xffffffff8044b3e7 in panic (fmt=0x1
) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0xffffffff80605b30 in trap_fatal (frame=0xc, eva=) at /usr/src/sys/amd64/amd64/trap.c:872 #4 0xffffffff80605e9f in trap_pfault (frame=0xffffff84637a1920, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:789 #5 0xffffffff80606254 in trap (frame=0xffffff84637a1920) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0xffffffff805efecf in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0xffffffff8050f494 in ether_nh_input (m=0xfffffe004f3bde00) at /usr/src/sys/net/if_ethersubr.c:484 #8 0xffffffff8051a562 in netisr_dispatch_src (proto=9, source=, m=) at /usr/src/sys/net/netisr.c:1013 #9 0xffffffff80318844 in igb_rxeof (que=0xfffffe000a183a00, count=499, done=0x0) at /usr/src/sys/dev/e1000/if_igb.c:4688 #10 0xffffffff8032183a in igb_msix_que (arg=) at /usr/src/sys/dev/e1000/if_igb.c:1596 #11 0xffffffff8042082d in intr_event_execute_handlers ( p=, ie=0xfffffe000a109e00) at /usr/src/sys/kern/kern_intr.c:1272 #12 0xffffffff8042205e in ithread_loop (arg=0xfffffe000a1a16e0) at /usr/src/sys/kern/kern_intr.c:1285 #13 0xffffffff8041d48e in fork_exit ( callout=0xffffffff80421fc0 , arg=0xfffffe000a1a16e0, frame=0xffffff84637a1c00) at /usr/src/sys/kern/kern_fork.c:995 #14 0xffffffff805f038e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:602 #15 0x0000000000000000 in ?? () -- Meditating Guru Ian Freislich From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 14:50:30 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 179B930C for ; Mon, 19 Nov 2012 14:50:30 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id AB93E8FC12 for ; Mon, 19 Nov 2012 14:50:29 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id qAJEoMXt026108; Mon, 19 Nov 2012 07:50:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id qAJEoMW6026105; Mon, 19 Nov 2012 07:50:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 19 Nov 2012 07:50:22 -0700 (MST) From: Warren Block To: Alex Keda Subject: Re: No ATA disks on 9.1-RC3 In-Reply-To: <50A9ECB3.8010209@lissyara.su> Message-ID: References: <50A9ECB3.8010209@lissyara.su> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; format=flowed Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Mon, 19 Nov 2012 07:50:22 -0700 (MST) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 14:50:30 -0000 On Mon, 19 Nov 2012, Alex Keda wrote: > I try update my laptop - Compaq 6715s from 9.0 to 9.1-rc3 > it cannot boot, because no HDD found > dmesg from 9.0/9.1 and pciconf in attached files If there is an IDE/AHCI mode setting in the BIOS, switch it to the other setting. From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 15:08:09 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27EE781A; Mon, 19 Nov 2012 15:08:09 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id CDC698FC0C; Mon, 19 Nov 2012 15:08:08 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3Y4thc6nTJzFTDk; Mon, 19 Nov 2012 16:08:00 +0100 (CET) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfGhoGxL7M1i; Mon, 19 Nov 2012 16:07:55 +0100 (CET) Received: from vwg82.hq.ignesti.it (unknown [80.74.176.55]) by winston.madpilot.net (Postfix) with ESMTPSA; Mon, 19 Nov 2012 16:07:55 +0100 (CET) Message-ID: <50AA4B48.5090804@madpilot.net> Date: Mon, 19 Nov 2012 16:07:52 +0100 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121114 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: problem booting to multi-vdev root pool References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66701.701@madpilot.net> <50A82B3A.6020608@it4pro.pl> <50A8CB1C.9090907@FreeBSD.org> <50AA2D5D.7080105@FreeBSD.org> In-Reply-To: <50AA2D5D.7080105@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bartosz Stec , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:08:09 -0000 On 11/19/12 14:00, Andriy Gapon wrote: > on 18/11/2012 13:48 Andriy Gapon said the following: >> on 18/11/2012 02:26 Bartosz Stec said the following: >> >> Thank you both very much for testing! >> Committed as r243213. >> > > BTW, if you have some spare time and a desire to do some more testing, you can > try the following patch: > http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_support.diff > > It adds support for multi-vdev root pool probing in kernel. > The best way to test is to remove zpool.cache before rebooting (but make sure to > keep a copy somewhere and be able to recover). I'd use a boot environment (a > root filesystem clone) for this. > Hi! Thank you again for the fast work. I tested this one on that machine and it was able to boot without zpool.cache. No file zpool.cache was created after boot. Are there any further test I should perform? -- Guido Falsi From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 15:23:44 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 40A9AFB1; Mon, 19 Nov 2012 15:23:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3D7558FC15; Mon, 19 Nov 2012 15:23:43 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA14947; Mon, 19 Nov 2012 17:23:27 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AA4EEF.6090306@FreeBSD.org> Date: Mon, 19 Nov 2012 17:23:27 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Guido Falsi Subject: Re: problem booting to multi-vdev root pool References: <509D1DEC.6040505@FreeBSD.org> <50A27243.408@madpilot.net> <50A65F83.5000604@FreeBSD.org> <50A66701.701@madpilot.net> <50A82B3A.6020608@it4pro.pl> <50A8CB1C.9090907@FreeBSD.org> <50AA2D5D.7080105@FreeBSD.org> <50AA4B48.5090804@madpilot.net> In-Reply-To: <50AA4B48.5090804@madpilot.net> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Bartosz Stec , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:23:44 -0000 on 19/11/2012 17:07 Guido Falsi said the following: > On 11/19/12 14:00, Andriy Gapon wrote: >> on 18/11/2012 13:48 Andriy Gapon said the following: >>> on 18/11/2012 02:26 Bartosz Stec said the following: >>> >>> Thank you both very much for testing! >>> Committed as r243213. >>> >> >> BTW, if you have some spare time and a desire to do some more testing, you can >> try the following patch: >> http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_support.diff >> >> It adds support for multi-vdev root pool probing in kernel. >> The best way to test is to remove zpool.cache before rebooting (but make sure to >> keep a copy somewhere and be able to recover). I'd use a boot environment (a >> root filesystem clone) for this. > > Thank you again for the fast work. > > I tested this one on that machine and it was able to boot without zpool.cache. Great! Thank you for testing. > No file zpool.cache was created after boot. This is expected. > Are there any further test I should perform? This was sufficient. Thanks again. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 15:34:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 927A17F1 for ; Mon, 19 Nov 2012 15:34:16 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id 401978FC0C for ; Mon, 19 Nov 2012 15:34:15 +0000 (UTC) Received: from [77.41.108.0] (port=44274 helo=dc7700p.lissyara.su) by mx.lissyara.su with esmtpa (Exim 4.80 (FreeBSD)) (envelope-from ) id 1TaTMO-000A5n-5x for freebsd-current@freebsd.org; Mon, 19 Nov 2012 19:34:08 +0400 Message-ID: <50AA516F.6050208@lissyara.su> Date: Mon, 19 Nov 2012 19:34:07 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121019 Thunderbird/16.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: No ATA disks on 9.1-RC3 References: <50A9ECB3.8010209@lissyara.su> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:34:16 -0000 On 19.11.2012 18:50, Warren Block wrote: > On Mon, 19 Nov 2012, Alex Keda wrote: > >> I try update my laptop - Compaq 6715s from 9.0 to 9.1-rc3 >> it cannot boot, because no HDD found >> dmesg from 9.0/9.1 and pciconf in attached files > > If there is an IDE/AHCI mode setting in the BIOS, switch it to the other > setting. It's HP. No BIOS settings for hard drive/SATA controller From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 15:46:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0F54B19 for ; Mon, 19 Nov 2012 15:46:13 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 21DC98FC0C for ; Mon, 19 Nov 2012 15:46:12 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so4710708lah.13 for ; Mon, 19 Nov 2012 07:46:05 -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 :content-type; bh=tVe7m/flzGiEpNIoy7JUInSTJg/uMOko5HPN75IU52E=; b=SXzgcfBs2qmtNKQuoekevzqcVfgCrD3QnrfkrPDWSjoukJgSSCQbwVzI7UijFdte8M +USwXImIdYPKnYSYMcfLWQqM5IwvSYXLTuzWJeh/84Qw9crQjAilR5IXrbbP0IjBZcs2 0O73bl8E/k/GrCXo4GwCa9NW42ajLT8SpQmSg= 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 :content-type:x-gm-message-state; bh=tVe7m/flzGiEpNIoy7JUInSTJg/uMOko5HPN75IU52E=; b=obxvOZDYT0RHffHfc4C0pioVYoGqrkQEIefSAYVKtT4/3xn/rESwA0EwYyaYIA517R BnhQUyr99PGTqE30dzgVG5b8tjP62P/5EFjtz278uSuHsCI0Vc6FoaswLsTxhTXAL8dn JeiKGoqm21nhTHJ8GjRV8sFd9fQk1ZUmn/EjNnfK4kt3QJasXuIqknaPDypI4NpTMdE2 /VdAPAqFpJ5N5AQhMNgNSSqX4PTvkf5+bpMiU425nQBf3w4nL91AN4MvC7dgG5+k3nFu zHLjReZ76PqgkQEW5g2MMlXbq21EsFY1RLS4fS440IxdFAtzOG421oc2REFPxHmKD6r0 Ipfg== Received: by 10.152.104.115 with SMTP id gd19mr12070064lab.13.1353339965473; Mon, 19 Nov 2012 07:46:05 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Mon, 19 Nov 2012 07:45:35 -0800 (PST) In-Reply-To: <20121118234426.GA16628@dft-labs.eu> References: <20121118234426.GA16628@dft-labs.eu> From: Eitan Adler Date: Mon, 19 Nov 2012 10:45:35 -0500 Message-ID: Subject: Re: prompt w/ uid 0 for cshrc To: Mateusz Guzik , Eitan Adler , freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlRfyRagqb3P+iXzvl/Si8IL+WcHhSePVVgTuASs3j9P2VLQ9JpyF8lnDyjkNY0FsBjH1KZ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 15:46:13 -0000 On 18 November 2012 18:44, Mateusz Guzik wrote: > Just take user name from id -nu. While that does provide the $user value I want, id is in /usr/bin/ which may not be mounted. Is there a builtin which provides similar functionality? -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 16:47:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3422FE9 for ; Mon, 19 Nov 2012 16:47:25 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4EDA18FC08 for ; Mon, 19 Nov 2012 16:47:24 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TaUVK-0004NU-36 for freebsd-current@freebsd.org; Mon, 19 Nov 2012 17:47:26 +0100 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Nov 2012 17:47:26 +0100 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 19 Nov 2012 17:47:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: jb Subject: Re: prompt w/ uid 0 for cshrc Date: Mon, 19 Nov 2012 16:46:59 +0000 (UTC) Lines: 14 Message-ID: References: <20121118234426.GA16628@dft-labs.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20100101 Firefox/16.0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 16:47:25 -0000 Eitan Adler eitanadler.com> writes: > > On 18 November 2012 18:44, Mateusz Guzik gmail.com> wrote: > > Just take user name from id -nu. > > While that does provide the $user value I want, id is in /usr/bin/ > which may not be mounted. /rescue/id jb From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 18:28:21 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 050F12BC; Mon, 19 Nov 2012 18:28:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id A34288FC0C; Mon, 19 Nov 2012 18:28:20 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id qAJISIt0073134; Mon, 19 Nov 2012 13:28:18 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id qAJISIke073133; Mon, 19 Nov 2012 18:28:18 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 19 Nov 2012 18:28:18 GMT Message-Id: <201211191828.qAJISIke073133@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on sparc64/sparc64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 18:28:21 -0000 TB --- 2012-11-19 17:30:22 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-11-19 17:30:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-11-19 17:30:22 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-11-19 17:30:22 - cleaning the object tree TB --- 2012-11-19 17:33:02 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-11-19 17:33:02 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2012-11-19 17:33:02 - /usr/local/bin/svn cleanup /src TB --- 2012-11-19 17:34:03 - /usr/local/bin/svn update /src TB --- 2012-11-19 17:34:09 - At svn revision 243290 TB --- 2012-11-19 17:34:10 - building world TB --- 2012-11-19 17:34:10 - CROSS_BUILD_TESTING=YES TB --- 2012-11-19 17:34:10 - MAKEOBJDIRPREFIX=/obj TB --- 2012-11-19 17:34:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-11-19 17:34:10 - SRCCONF=/dev/null TB --- 2012-11-19 17:34:10 - TARGET=sparc64 TB --- 2012-11-19 17:34:10 - TARGET_ARCH=sparc64 TB --- 2012-11-19 17:34:10 - TZ=UTC TB --- 2012-11-19 17:34:10 - __MAKE_CONF=/dev/null TB --- 2012-11-19 17:34:10 - cd /src TB --- 2012-11-19 17:34:10 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Nov 19 17:34:15 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -mcmodel=medlow -Os -I/src/sys/boot/sparc64/boot1/../../common -ffreestanding -std=gnu99 -c /src/sys/boot/sparc64/boot1/boot1.c In file included from /obj/sparc64.sparc64/src/tmp/usr/include/ufs/ffs/fs.h:36, from /src/sys/boot/sparc64/boot1/../../common/ufsread.c:51, from /src/sys/boot/sparc64/boot1/boot1.c:451: /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: conflicting types for 'mount' /src/sys/boot/sparc64/boot1/boot1.c:63: error: previous declaration of 'mount' was here /src/sys/boot/sparc64/boot1/boot1.c:501: error: conflicting types for 'mount' /obj/sparc64.sparc64/src/tmp/usr/include/sys/mount.h:824: error: previous declaration of 'mount' was here *** [boot1.o] Error code 1 Stop in /src/sys/boot/sparc64/boot1. *** [all] Error code 1 Stop in /src/sys/boot/sparc64. *** [all] Error code 1 Stop in /src/sys/boot. *** [all] Error code 1 Stop in /src/sys. *** [sys.all__D] Error code 1 Stop in /src. *** [everything] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-11-19 18:28:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-11-19 18:28:18 - ERROR: failed to build world TB --- 2012-11-19 18:28:18 - 2688.14 user 484.05 system 3475.62 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 19:15:33 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BAE8A72 for ; Mon, 19 Nov 2012 19:15:33 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id AB9E88FC14 for ; Mon, 19 Nov 2012 19:15:32 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1132785wey.13 for ; Mon, 19 Nov 2012 11:15:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=J1F9YTuoytockzF75zYtJ/V+HkZf1MsWXSgMNiCn4Os=; b=nEGjLc7I00IqSsCoWM+oUAA8PX9eJhaVZRvj/wJcFrnVCJDtc1sOAF8XManiKTMaXY hh/moxyNVksru3mf0FMtcXnxlLM0p30i8YSjsVKtRAjSMuROt/aiIpK8ceh/0wPRiKMi VW/Gq+rB20GmFqwVmTliUMuSpoTt4jiUgjn/h+T2oi898MhCiURUvWmVN2sneLmCM2XV acMWARbTcUglcpiJSydtReQxUl7UTHQ/xSBLTRE8tPO0iNIoQbqc6b5/uCrs40nLfPqz SAwhV1uel+JCPY6Gf2eZeSPs0GjeQawyYO6m0AC5PMfiCK3o/g3ElGthbIa4sz9Ow2n1 lssQ== Received: by 10.216.228.28 with SMTP id e28mr3108532weq.48.1353352531307; Mon, 19 Nov 2012 11:15:31 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id dd4sm10594308wib.2.2012.11.19.11.15.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Nov 2012 11:15:30 -0800 (PST) Date: Mon, 19 Nov 2012 20:15:22 +0100 From: Mateusz Guzik To: Eitan Adler Subject: Re: prompt w/ uid 0 for cshrc Message-ID: <20121119191521.GA22292@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Eitan Adler , freebsd-current Current References: <20121118234426.GA16628@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 19:15:33 -0000 On Mon, Nov 19, 2012 at 10:45:35AM -0500, Eitan Adler wrote: > On 18 November 2012 18:44, Mateusz Guzik wrote: > > Just take user name from id -nu. > > While that does provide the $user value I want, id is in /usr/bin/ > which may not be mounted. > Is there a builtin which provides similar functionality? > Valid point, but should not happen a lot when unprivileged accounts are involved, so I suggest the following (pseudo-sh-code): if [ -x /usr/bin/id ]; then up=$(id -nu); else if [ $uid = 0 ]; then up="root"; else up="($uid)" fi -- Mateusz Guzik From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 19:40:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6BBFEDE for ; Mon, 19 Nov 2012 19:40:08 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 769F48FC12 for ; Mon, 19 Nov 2012 19:40:08 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 17F4173027; Mon, 19 Nov 2012 20:32:02 +0100 (CET) Date: Mon, 19 Nov 2012 20:32:02 +0100 From: Luigi Rizzo To: current@freebsd.org Subject: syscall cost freebsd vs linux ? Message-ID: <20121119193202.GA79496@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 19:40:08 -0000 today i was comparing the performance of some netmap-related code on FreeBSD and Linux (RELENG_9 vs 3.2) and i was surprised to see that our system calls are significantly slower. On comparable hardware (i7-2600k vs E5-1650) the syscall getppid() takes about 95ns on FreeBSD and 38ns on linux. (i make sure not to use gettimeofday(), which in linux is through vdso, and getpid(), which is cached by glibc). Any idea on why there is this difference and whether/how we can reduce it ? cheers luigi From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 22:28:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45B05C14; Mon, 19 Nov 2012 22:28:55 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 999B48FC08; Mon, 19 Nov 2012 22:28:54 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id hm9so349871wib.13 for ; Mon, 19 Nov 2012 14:28:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=dlmaEM37Ofjw5U1p2b2TnN2fRMsHFAC8HRRqolxEQK8=; b=xZTtTlNdrq1a2AqaPaIq2WxOJ1D1FKbBjngsiUwjO+g42wTT/YgYY5Jpn7h6BVN5JG iSszQcbHZP0ct9y3e8X+ymwJEnU39QEzbQ1O2y3DTe4+Mz8M8jro/0rpknwkESYP3jlh D/ps1eH3uqTSEbDQBpFnitF++FlZEgX8ZcBpyOKzz+jFEDH9hvqqiccCfceIf/8Ad7uI EnKxSzxOThvhK9W+SLD6sza37N4t72y6mO2BIdoRjZ7CyqcZFCBAKoUMOcn5h3VULwaY sLL7VcDaMfRLql+z5YgJUQTiSDX1zsXwjMtdJRB3W1z7tQGNpzOtTq3ZUvBVchWnC4ig fPSQ== Received: by 10.180.86.70 with SMTP id n6mr11277620wiz.4.1353364133464; Mon, 19 Nov 2012 14:28:53 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id i2sm15348380wiw.3.2012.11.19.14.28.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Nov 2012 14:28:52 -0800 (PST) Date: Mon, 19 Nov 2012 23:28:43 +0100 From: Mateusz Guzik To: Ryan Stone Subject: Re: pw keeps setting /etc/group to 0600 Message-ID: <20121119222843.GB22292@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Ryan Stone , FreeBSD Current , bapt@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: bapt@freebsd.org, FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 22:28:55 -0000 On Sat, Nov 17, 2012 at 11:20:21AM -0500, Ryan Stone wrote: > My original complaint that /etc/group gets permissions of 0600 is a result > of a bug in libutil, which bapt@ ported pw to use in r242349. The new > group manipulation API using mktemp to create a temporary file, writes the > new group database to the temp file and then renames the temp file to > /etc/group. The problem here is that mktemp creates a file with a mode of > 600, and libutil never chmods it. That should be pretty trivial to fix. My additional 0,03$: I took closer look to this and I think that problems are much broader than this. I don't know if similar problems were present before. First, pw should not fail if other instance is running, it should wait instead (think of parallel batch scripts adding some users/groups). Second, current code has a race: lockfd = open(group_file, O_RDONLY, 0); if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) == -1) err(1, "%s", group_file); if (flock(lockfd, LOCK_EX|LOCK_NB) == -1) { [..] gr_copy(pfd, tfd, gr, old_gr); /* copy from groupfile to tempfile */ [..] rename(tempfile,groupfile); Now let's consider threads A and B: A: open() A: lock(); A: gr_copy B: open() Now B has file descriptor to /etc/group that is about to be removed. A: rename() A: unlock() B: lock() Now B has a lock on unlinked file. B: gr_copy() B: rename() ... and stores new content losing modifications done by A Third, I don't like current api. gr_lock and gr_tmp have no arguments (that matter anyway) gr_copy operates on two descriptors given as arguments gr_mkdb takes nothing and is expected to do The Right Thing I think descriptos should be hidden. Also I think that passing around struct gr_something (sorry, never had talent for names) that would contain all necessary data would be nice. -- Mateusz Guzik From owner-freebsd-current@FreeBSD.ORG Mon Nov 19 22:37:48 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF01FE7A for ; Mon, 19 Nov 2012 22:37:48 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 44BC38FC16 for ; Mon, 19 Nov 2012 22:37:47 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm6so371083wib.13 for ; Mon, 19 Nov 2012 14:37:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=IBe7lU1bY397xYrVcddT3apnW97mDtVu32B3GsEkOMk=; b=Z9uRrOFATPdwXgbMV64iictW1gmyiE6ywqV90puR78NUdXnNhnrwdM68bi5tFT6n6e dAS8yowlMiPLxHQygxa5vx2TRc0q146LDwNGfZaO2aRWg+/I7WRJS+NrsqLG4/e+RmZb ZjYhZD3j1eIEOAPNILTWR8aKBJgpAlZFNb7+M/4LYW3M/nFTvE+rJPGFB+MDOYluIadU gBJYxBTqnvgsrSnoj54KHofyiVN4rJ4OdnibHTR4KHIvaZRo4TSdP0sJCp8d/3h2RuLI 5z3K4kcXxIw7L3CKIJiTkSGhcZfU54uvtLQzhWxppLQGM0MetThmgkIyS/EUoIzOokRj I2NQ== Received: by 10.180.99.36 with SMTP id en4mr11253514wib.20.1353364667332; Mon, 19 Nov 2012 14:37:47 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id ec3sm15367039wib.10.2012.11.19.14.37.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Nov 2012 14:37:46 -0800 (PST) Sender: Baptiste Daroussin Date: Mon, 19 Nov 2012 23:37:45 +0100 From: Baptiste Daroussin To: Mateusz Guzik , Ryan Stone , FreeBSD Current Subject: Re: pw keeps setting /etc/group to 0600 Message-ID: <20121119223745.GG71195@ithaqua.etoilebsd.net> References: <20121119222843.GB22292@dft-labs.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QwZB9vYiNIzNXIj" Content-Disposition: inline In-Reply-To: <20121119222843.GB22292@dft-labs.eu> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2012 22:37:48 -0000 --+QwZB9vYiNIzNXIj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 19, 2012 at 11:28:43PM +0100, Mateusz Guzik wrote: > On Sat, Nov 17, 2012 at 11:20:21AM -0500, Ryan Stone wrote: > > My original complaint that /etc/group gets permissions of 0600 is a res= ult > > of a bug in libutil, which bapt@ ported pw to use in r242349. The new > > group manipulation API using mktemp to create a temporary file, writes = the > > new group database to the temp file and then renames the temp file to > > /etc/group. The problem here is that mktemp creates a file with a mode= of > > 600, and libutil never chmods it. That should be pretty trivial to fix. >=20 > My additional 0,03$: >=20 > I took closer look to this and I think that problems are much broader > than this. I don't know if similar problems were present before. >=20 > First, pw should not fail if other instance is running, it should wait > instead (think of parallel batch scripts adding some users/groups). >=20 > Second, current code has a race: > lockfd =3D open(group_file, O_RDONLY, 0); > if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) =3D=3D -1) > err(1, "%s", group_file); > if (flock(lockfd, LOCK_EX|LOCK_NB) =3D=3D -1) { > [..] > gr_copy(pfd, tfd, gr, old_gr); /* copy from groupfile to tempfile */ > [..] > rename(tempfile,groupfile); >=20 > Now let's consider threads A and B: >=20 > A: open() > A: lock(); > A: gr_copy > B: open() >=20 > Now B has file descriptor to /etc/group that is about to be removed. >=20 > A: rename() > A: unlock() > B: lock() >=20 > Now B has a lock on unlinked file. >=20 > B: gr_copy() > B: rename() >=20 > ... and stores new content losing modifications done by A >=20 > Third, I don't like current api. > gr_lock and gr_tmp have no arguments (that matter anyway) > gr_copy operates on two descriptors given as arguments > gr_mkdb takes nothing and is expected to do The Right Thing gr_mkdb should chmod 0644 after renaming if rename worked. I should work on this soon. The API has been design to match the exact same api of pw_utils, I don't li= ke it either but at least this is consistent. regards, Bapt --+QwZB9vYiNIzNXIj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCqtLkACgkQ8kTtMUmk6Ey/xgCdFhwC2X2HH7+SOki6QmTc7eBW sBYAn3nXdRkPnwoHVcFw61iUHdPgnNCz =lm2g -----END PGP SIGNATURE----- --+QwZB9vYiNIzNXIj-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 00:55:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CF1C48C for ; Tue, 20 Nov 2012 00:55:50 +0000 (UTC) (envelope-from mbsd@isgroup.com.ua) Received: from mail.standard.com.ua (mail.isgroup.com.ua [46.229.54.104]) by mx1.freebsd.org (Postfix) with ESMTP id 9388D8FC08 for ; Tue, 20 Nov 2012 00:55:48 +0000 (UTC) Received: from [192.168.11.5] (unused-213.111.71.228.bilink.ua [213.111.71.228] (may be forged)) (authenticated bits=0) by mail.standard.com.ua (8.14.3/8.14.3) with ESMTP id qAK0aGWb094869 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 20 Nov 2012 02:36:16 +0200 (EET) (envelope-from mbsd@isgroup.com.ua) Subject: Programmer dvorak layout for syscons From: mbsd To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Date: Tue, 20 Nov 2012 02:42:50 +0200 Message-ID: <1353372170.2121.9.camel@eva02> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-101.1 required=9.0 tests=BAYES_00,HELO_MISC_IP, RDNS_NONE,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.isgroup.com.ua X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 00:55:50 -0000 I've been using this layout for a long time in X and I create kbdmap for syscons. Does it any chance to be put in source tree? So my question is, is it worth. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 01:22:49 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EF03D75 for ; Tue, 20 Nov 2012 01:22:49 +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 B08E88FC13 for ; Tue, 20 Nov 2012 01:22:47 +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 qAK1Misa010133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Nov 2012 12:22:45 +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 qAK1McAp074530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Nov 2012 12:22:39 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id qAK1MbCP074527; Tue, 20 Nov 2012 12:22:37 +1100 (EST) (envelope-from peter) Date: Tue, 20 Nov 2012 12:22:37 +1100 From: Peter Jeremy To: mbsd Subject: Re: Programmer dvorak layout for syscons Message-ID: <20121120012237.GH38823@server.rulingia.com> References: <1353372170.2121.9.camel@eva02> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kA1LkgxZ0NN7Mz3A" Content-Disposition: inline In-Reply-To: <1353372170.2121.9.camel@eva02> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 01:22:49 -0000 --kA1LkgxZ0NN7Mz3A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Nov-20 02:42:50 +0200, mbsd wrote: >I've been using this layout for a long time in X and I create kbdmap for >syscons. > >Does it any chance to be put in source tree? So my question is, is it >worth. I suggest you write a PR that includes the keymap and an appropriate patch for /usr/share/syscons/keymaps/INDEX.keymaps as well as explaining how it differs from the 9 existing Dvorak keymaps. --=20 Peter Jeremy --kA1LkgxZ0NN7Mz3A Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCq210ACgkQ/opHv/APuIf/pgCfSsHWjRf53dIalTP9oDpJrr7u aAkAoL7ohLB5dF4DrwW+8w6LSIrgfUzc =ODsu -----END PGP SIGNATURE----- --kA1LkgxZ0NN7Mz3A-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 01:36:45 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CAE359A for ; Tue, 20 Nov 2012 01:36:45 +0000 (UTC) (envelope-from lists@eitanadler.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 6F71F8FC17 for ; Tue, 20 Nov 2012 01:36:44 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so7548561vcb.13 for ; Mon, 19 Nov 2012 17:36:44 -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 :content-type; bh=AFNK5QWBCqfbwken8iY/vjmPJpslxfN1Nij/mk3tlCQ=; b=WIkJg8IkO5RcRK44jJDCR6LjHDX6UP4uvi8wl/Yko21Ao6pBVjhelmDfeqV8gy+v/O Fnl77tTgoLjOPPFinoklXEk2BozfYbhU9GHNOFHOh46JMD8FqUbADxJaLR76eOWpXTnv cYfvYYhLLWWBaJEAeOx6R+uPx9hFVkyE3neac= 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 :content-type:x-gm-message-state; bh=AFNK5QWBCqfbwken8iY/vjmPJpslxfN1Nij/mk3tlCQ=; b=PZtpQZp3rT1XBjrUMQ/Kt566+yQ0t7nTU9Etg+yG8RtymBA5td1oa/JFlkqzdvA6CA v46Vg4h8EkIxa8uop/jNz4ffj1g0DHi8R50WoKF6HFjduUnXZP+qZ4dwojM8yuVpI6Gj qJg8TxruucWDFFD+2rrCMoWOTMZ7YZhKKsp5XKC14N+GUc7nFFTBdvrEMU3lZ/Q+k1QV nYtoaMPknSMHHFRhPt7o1Yk384+tmVUK9HBqcHOARfP8LuSOugk9DMPNZJCeEEVZsaWD +iszgE7eGEKwggaw69ffqMwlk103PelbiOxGfDMNDwvuRhsQaTin4ZYRc9hb7+06IOW3 sDmQ== Received: by 10.58.145.161 with SMTP id sv1mr19823601veb.52.1353375404123; Mon, 19 Nov 2012 17:36:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.4.197 with HTTP; Mon, 19 Nov 2012 17:36:13 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Mon, 19 Nov 2012 20:36:13 -0500 Message-ID: Subject: Re: prompt w/ uid 0 for cshrc To: freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmk4HmOCUbQczRHPjAFuIvKhU1NurnYKOY2yEHyTZV/vWWTmaNQATwZRT0VdDATDawP6bDq X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 01:36:45 -0000 On 18 November 2012 18:32, Eitan Adler wrote: > Hey, > > at the moment the current default csh prompt looks like > > user@hostname:directory% command > > This leads to an unexpected[*] result when using su (without "-"). > > In particular the user part is *not* changed to "root" (or "toor" or > any other superuser indication) although the promptchar is changed to > "#". > This causes some confusion for new users and even some experienced ones. > > I worked around this issue by including the following > > if ($uid == 0) then > set user = root > endif > > which I'm not certain is a good idea. > > I would like to replace this with logic like > > if $uid = 0 AND $user != toor AND $user != root > set user = "+$user" > endif > > does anyone think this is a bad idea? can anyone propose a better > idea? Is the status quo okay? ... I was pointed in the right direction. I should use %N instead of %n. -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 02:30:56 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F62ED7E for ; Tue, 20 Nov 2012 02:30:56 +0000 (UTC) (envelope-from paul.g.webster@googlemail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id E814E8FC0C for ; Tue, 20 Nov 2012 02:30:55 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id 12so2186149wgr.31 for ; Mon, 19 Nov 2012 18:30:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:organization:subject:to:date:mime-version:from :message-id:user-agent; bh=Ptlm5kUw7GhqU4VZe59Se6l0RjccQ14foNCsgYcOoPs=; b=Tr7IJU4VskZcBBkY9eWzK010IWnxaDVpJxmPp0B/dGcRTeb9RDJ8CDgbL3upaHFTlE GKbb13H0cm24uTH/kRzHUTFfO9MKfTc5VDmg0NgEdnFBI058ig2i/wqQFa7225f66NUp FePmHvm3mOKmw5RaKKdj+fxOzG9p/e0l8jSd30OsCAJW2lksngN45PQiCEPtXerzedAe RYTrHdbe06qmkkrv6Fs0StpwoCTr0tagHeiz/TAam4g79FGEkPlh+BSxez17w3Ui1Q6J 8YwgCKMCyXd/W3Qt46buAjbf8v5gOl4YyLkm0R29tvtzg2s1hvhd1Rshz59RhMvx3TzR z8xw== Received: by 10.180.88.100 with SMTP id bf4mr11838279wib.16.1353378654747; Mon, 19 Nov 2012 18:30:54 -0800 (PST) Received: from box.dlink.com (host-78-149-58-39.as13285.net. [78.149.58.39]) by mx.google.com with ESMTPS id fh10sm3246084wib.3.2012.11.19.18.30.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Nov 2012 18:30:54 -0800 (PST) Content-Type: multipart/mixed; boundary=----------6lJAZgrOUxT2gRScunhKlF Organization: Interflective Group Subject: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) To: freebsd-current@freebsd.org Date: Tue, 20 Nov 2012 02:30:53 -0000 MIME-Version: 1.0 From: "Paul Webster" Message-ID: User-Agent: Opera Mail/12.11 (Win64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 02:30:56 -0000 ------------6lJAZgrOUxT2gRScunhKlF Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Forward notice: I sent this to freebsd-pf originally and did not CC -current, but as the issue would affect current and the more opinions the better... I have sent it here too. -- Cheers, daemon -- original message Good day all, I am aware this is a much discussed subject since the upgrade of PF, I believe the final decision was that to many users are used to the old style pf and an upgrade to the new syntax would cause to much confusion. There was a recent debate on ##freebsd about this issue and I was inclined to mail in and get your opinions; basically it boiled down to the majority of users wanting either: 1) To move to the newer pf and just add to releases notes what had happened, and 2) my own personal opinion: creating 'pf2-*' as a kernel option tree, basically using the newer pf syntax and allowing users to choose. I would be interested to know the feedback from you guys as to be honest there seems to be quite a few users who actually DO want the new style format and functionality that comes with. I Attached the log of the conversation just for reference. -- Thank you for your time -- Paul G Webster 'daemon' Using Opera's revolutionary email client: http://www.opera.com/mail/ ------------6lJAZgrOUxT2gRScunhKlF Content-Disposition: attachment; filename=irc-snippet.txt Content-Type: text/plain; name="irc-snippet.txt" Content-Transfer-Encoding: Quoted-Printable * daemonik (~Adium@mail.originate.com) has joined ##freebsd Is the implementation of PF on FreeBSD up to date yet? no * stormcrow (~phydeaux@c-24-126-183-121.hsd1.ga.comcast.net) has left ##= freebsd and it won't ever be, we (retardedly) forked it with some ra= ndom guy's patches rather than updating it it's rare that that question asked about *any* part of the ba= se OS will be answered with "yes" doh. booo @ random patches blakkheim that was truly a stupid move i agree any chance of getting them to 'take it back' they think freebsd users are too stupid to adapt to the newe= r pf syntax and "thousands will upgrade without knowing and be left with= an unreachable system" or some bs like that is there anything that pf can do that ipfw cannot do check the freebsd-pf mailing list illuminated (or feel free = to post and complain) blakkheim: That's pretty damn . . wow might be worth a few emails to all the lists asking for other u= sers to post into the pf list to support moving to the correct pf maybe we can implement the newer pf as 'pf2' FreeBSD presently doesn't have ALTQ support included in the g= eneric kernel, correct? Is there an alternative to ALTQ? daemon: i think so too daemon: Is it really that hard to shout in the appropriate pl= aces to properly inform users? What about release notes? Anybody who doe= sn't read release notes deserves what's coming to them. that's what i said! * chrisb has learned to read MOVED and UPDATING closely Huh . . that kind of behavior is why no one respects anyone/t= hing associated with GNOME anymore . . daemonik, I dont see it being that hard to use both the 'ramdon= guys patches' version of pf as the default for a few releases putting t= he newer version of pf as 'pf2' therefor satisfying both channels of thought there certainly should be A WAY of using the newer version posting these thoughts to freebsd-pf@ is much more likely to= invoke a change (or at least a poll or something) than on irc daemon: No . . the noobs are the ones who should have to use = a pf-something. I bother to read the release notes, I want to use the co= rrect version of the software. Why should I have to suffer? Why should I= change when they're the ones who suck? * nightwalk has quit (Ping timeout: 276 seconds) I'll make a post later tonight. I hope that others see these = messages and also articulate their thoughts on the mailing list. FreeBSD= should hold a high standard for something as important as PF. daemonik, if you did read release notes you would see 'ad the n= ew version of pf is pf2' there is no need to upset users without cause; = as the 'patched' pf is the default for the tag 'pf' at the moment making= the new version 'pf2' is literally much more sane and certainly a huge degree less antagonistic How do I find the size of a folder? And for that matter how do I search a man page? du -sh dirname and use /string to search Thanks blakkheim I would rather read the release notes seeing that the WRONG v= ersion of PF gets deprecated to pf-legacy as it ought to be =97 knowing = that those who don't read the release notes will have a bad day. Referring to the CORRECT and latest stable version of PF as "= PF2" would make FreeBSD . . well, look about as incompetent as certain L= inux distros sometimes do to say the least. daemonik, transistion time should always be taken into account = on any system; if we did was I was suggesting then 'pf' would be the new= version in -CURRENT but for later 9.x releases it would still have to b= e as I pointed out above i recall a number of features having 2 tagged to the name UFS2 for one or was it FFS2 and i think IPFW2 its quite a common practice; sudeenly changing a major feature/= system is just generally what makes people cry especially when it can be avoided with something as simple as a= dding a number to the end of the kernel tag kernel option* ------------6lJAZgrOUxT2gRScunhKlF-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 07:25:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9427E07 for ; Tue, 20 Nov 2012 07:25:04 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3D0578FC0C for ; Tue, 20 Nov 2012 07:25:03 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1385912wey.13 for ; Mon, 19 Nov 2012 23:25:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=rJGHirFRtkuuM0T6Bpz3rxFjavD8DVRxDjEd415ouwY=; b=owQKDfWKPyp7AHg28IjJZfbyxlY0xg2ASyYTb9TnstSXLXVb5hrcXrn+kIAT+Tbh3P CuKOsGIcaKd+jr4huMd1bidGLPZNhOoZtcIC3BkB/zGB2s3CYNBs5av3xbI0SXs0Uhil 9pUANhIAP9fcMbb3IymKJ9k385orfmd0KsQ5xwXOOyM0+h0fZwnALKVYC9wkDcraOYhX pEE14mvW1czE4RVl1VrvrXidpW31zBy0yoIuBBu4fz/FOKt/0ZrJIfXl2xD+FsH2EhsF PGvRkxsHqV+iCWtkoz4H6IQOt0d4tkobUQ7RNObdHf/E9ExZV7NJGDIAQdRaQAVs+LaS Ua4w== Received: by 10.180.109.132 with SMTP id hs4mr3654448wib.1.1353396302138; Mon, 19 Nov 2012 23:25:02 -0800 (PST) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPS id s12sm16549833wik.11.2012.11.19.23.25.01 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Nov 2012 23:25:01 -0800 (PST) Sender: Baptiste Daroussin Date: Tue, 20 Nov 2012 08:24:59 +0100 From: Baptiste Daroussin To: Mateusz Guzik , Ryan Stone , FreeBSD Current Subject: Re: pw keeps setting /etc/group to 0600 Message-ID: <20121120072459.GH71195@ithaqua.etoilebsd.net> References: <20121119222843.GB22292@dft-labs.eu> <20121119223745.GG71195@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="poJSiGMzRSvrLGLs" Content-Disposition: inline In-Reply-To: <20121119223745.GG71195@ithaqua.etoilebsd.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 07:25:04 -0000 --poJSiGMzRSvrLGLs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 19, 2012 at 11:37:45PM +0100, Baptiste Daroussin wrote: > On Mon, Nov 19, 2012 at 11:28:43PM +0100, Mateusz Guzik wrote: > > On Sat, Nov 17, 2012 at 11:20:21AM -0500, Ryan Stone wrote: > > > My original complaint that /etc/group gets permissions of 0600 is a r= esult > > > of a bug in libutil, which bapt@ ported pw to use in r242349. The new > > > group manipulation API using mktemp to create a temporary file, write= s the > > > new group database to the temp file and then renames the temp file to > > > /etc/group. The problem here is that mktemp creates a file with a mo= de of > > > 600, and libutil never chmods it. That should be pretty trivial to f= ix. > >=20 > > My additional 0,03$: > >=20 > > I took closer look to this and I think that problems are much broader > > than this. I don't know if similar problems were present before. > >=20 > > First, pw should not fail if other instance is running, it should wait > > instead (think of parallel batch scripts adding some users/groups). > >=20 > > Second, current code has a race: > > lockfd =3D open(group_file, O_RDONLY, 0); > > if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) =3D=3D -1) > > err(1, "%s", group_file); > > if (flock(lockfd, LOCK_EX|LOCK_NB) =3D=3D -1) { > > [..] > > gr_copy(pfd, tfd, gr, old_gr); /* copy from groupfile to tempfile */ > > [..] > > rename(tempfile,groupfile); > >=20 > > Now let's consider threads A and B: > >=20 > > A: open() > > A: lock(); > > A: gr_copy > > B: open() > >=20 > > Now B has file descriptor to /etc/group that is about to be removed. > >=20 > > A: rename() > > A: unlock() > > B: lock() > >=20 > > Now B has a lock on unlinked file. > >=20 > > B: gr_copy() > > B: rename() > >=20 > > ... and stores new content losing modifications done by A > >=20 > > Third, I don't like current api. > > gr_lock and gr_tmp have no arguments (that matter anyway) > > gr_copy operates on two descriptors given as arguments > > gr_mkdb takes nothing and is expected to do The Right Thing >=20 > gr_mkdb should chmod 0644 after renaming if rename worked. >=20 > I should work on this soon. >=20 > The API has been design to match the exact same api of pw_utils, I don't = like it > either but at least this is consistent. >=20 > regards, > Bapt Should be fixed now, regards, Bapt --poJSiGMzRSvrLGLs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCrMEsACgkQ8kTtMUmk6EwFPACePY6HimVwKaaDHqgRGavziX4V KbIAnjTHaU+XBpFLvC3yNk7/YexpRr1Z =vGGz -----END PGP SIGNATURE----- --poJSiGMzRSvrLGLs-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 08:57:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B23C642; Tue, 20 Nov 2012 08:57:04 +0000 (UTC) (envelope-from andy.lavr@gmail.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 901FB8FC0C; Tue, 20 Nov 2012 08:57:03 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so2814989lbb.13 for ; Tue, 20 Nov 2012 00:57:02 -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=IXt3W4ri+azUVKsrkgJW9Yk05tK+3cdxHj1GaOmLx1M=; b=qlUmacWzHZ5hd3zClSB/3Q6HJiC15/t/fh4URTdwa+7dn0FU7A65VEfyS/M5PJO7ew jlEVeRx1f4mNxXwQSTT5QK+amP6Gx8HVWwnKOESqeVTrbMIa5konTOocT64sp0bKdQTM llriA5Lsf0NGezlsKBwliN39APyXE1V95aQqI9Zvt+5VWbHamuG9Srqz5Cgy1IZYxPAY B348mAOgvlxBWAd4rHQhgH4EluXrIY9PK7W1U6g4+NLpL6mRBOd307xD4ucYkvJZmVtp x6c+XwS8ZKaQdex7L7X4EJB9E/D9PnvySlHZE7qUvxv+pWDoCBHXQ/ySP0OgqoZHjZjj CWJQ== MIME-Version: 1.0 Received: by 10.152.111.166 with SMTP id ij6mr14076334lab.38.1353401822162; Tue, 20 Nov 2012 00:57:02 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 00:57:02 -0800 (PST) Date: Tue, 20 Nov 2012 10:57:02 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: freebsd-current@freebsd.org, avg@FreeBSD.org, bartosz.stec@it4pro.pl, freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 08:57:04 -0000 Hi! My system: # uname -a FreeBSD open.technica-03.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Tue Oct 30 14:13:01 EET 2012 root@open.technica-03.local:/usr/obj/usr/src/sys/SMP64R amd64 # zpool status -v pool: zsolar state: ONLINE scan: resilvered 2,56M in 0h0m with 0 errors on Tue Nov 20 10:26:35 2012 config: NAME STATE READ WRITE CKSUM zsolar ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 errors: No known data errors Update source: # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 243278 Node Kind: directory Schedule: normal Last Changed Author: avg Last Changed Rev: 243272 Last Changed Date: 2012-11-19 13:35:56 +0200 I used http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_support.diff buildworld + kernel rm /boot/zfs/zpool.cache Reboot.... Mounting from zfs:zsolar failed with error 45 --- Best regards, Andrei Lavreniyuk. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 09:48:54 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE5306A2; Tue, 20 Nov 2012 09:48:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CBCC78FC0C; Tue, 20 Nov 2012 09:48:53 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA25073; Tue, 20 Nov 2012 11:48:51 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TakRm-000DT9-SR; Tue, 20 Nov 2012 11:48:50 +0200 Message-ID: <50AB5202.4070906@FreeBSD.org> Date: Tue, 20 Nov 2012 11:48:50 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 09:48:54 -0000 on 20/11/2012 10:57 Andrei Lavreniyuk said the following: > Hi! > > > My system: > > # uname -a > FreeBSD open.technica-03.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0: > Tue Oct 30 14:13:01 EET 2012 > root@open.technica-03.local:/usr/obj/usr/src/sys/SMP64R amd64 > > > # zpool status -v > pool: zsolar > state: ONLINE > scan: resilvered 2,56M in 0h0m with 0 errors on Tue Nov 20 10:26:35 2012 > config: > > NAME STATE READ WRITE CKSUM > zsolar ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > gpt/disk0 ONLINE 0 0 0 > gpt/disk2 ONLINE 0 0 0 > gpt/disk3 ONLINE 0 0 0 > > errors: No known data errors > > > Update source: > > # svn info > Path: . > Working Copy Root Path: /usr/src > URL: svn://svn.freebsd.org/base/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 243278 > Node Kind: directory > Schedule: normal > Last Changed Author: avg > Last Changed Rev: 243272 > Last Changed Date: 2012-11-19 13:35:56 +0200 > > > I used http://people.freebsd.org/~avg/zfs-spa-multi_vdev_root_support.diff > > > buildworld + kernel > > rm /boot/zfs/zpool.cache > > > Reboot.... > > > Mounting from zfs:zsolar failed with error 45 Are there any other unusual messages before this line? Could you please try adding vfs.zfs.debug=1 to loader.conf and check again? Could you also provide 'zdb -CC zsolar' output and 'zdb -l /dev/gpt/diskX' for each of the disks. These could be uploaded somewhere as they can be quite lengthy. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 10:18:40 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A7FBA7 for ; Tue, 20 Nov 2012 10:18:40 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id D76D58FC14 for ; Tue, 20 Nov 2012 10:18:39 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5486251lah.13 for ; Tue, 20 Nov 2012 02:18:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type; bh=zzO2dLFnpDv7cuMojzQZi20SLGd4v5xsIUwgj1temnI=; b=jOYHLccFpu9y7D27tQKNcVy5684QlTamKrGxrBBlwopcgBJ0HfBSelZJ6YkYS9d6y+ 5dy9HHJHuTBlBX/zdBVhAyLNTmwKF0NdIGKBNURTfdn8oqnrm4NR6EI0Axf09NwFB7cm HATKPpSDy/9iZzO2j+GNwgAqeLTj0WoSOZIXK4EtJU3WJDhsBHrqi89DYwmWT3EVZwlZ Xl3370seIXomz/Nh4OCDaXd+BzRGo/18KvPY6WhWfLs14dUoiGEmsiqBRcdmnjrSTwMq K8Hld+0EnyngOEOGM8WgDH8WU0m8v+Rv94eOrQizvK+oCeJSZQsjV04+OwZtTZGLTWVF 1Dfg== Received: by 10.152.124.111 with SMTP id mh15mr14177802lab.20.1353406718246; Tue, 20 Nov 2012 02:18:38 -0800 (PST) Received: from [192.168.1.11] (ip18-43-209-87.adsl2.static.versatel.nl. [87.209.43.18]) by mx.google.com with ESMTPS id sy1sm4565113lab.16.2012.11.20.02.18.36 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 02:18:37 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <50AB58FA.505@freebsd.org> Date: Tue, 20 Nov 2012 11:18:34 +0100 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121115 Thunderbird/16.0.2 MIME-Version: 1.0 To: current@freebsd.org Subject: sluggish X.org/Xfce behavior X-Enigmail-Version: 1.4.6 Content-Type: multipart/mixed; boundary="------------050703060503040706040607" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 10:18:40 -0000 This is a multi-part message in MIME format. --------------050703060503040706040607 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Hi, since last weekend (November 17th) I have been noticing a sluggish behavior of X.org/Xfce. Typical symptoms are: - Alt-Tab not reacting all of the time - pulldown/popup menus not allowing selections with mouse (typically in Terminal/pidgin), or moving the mouse (touchpad) results in an automatic click - typing something in a Terminal requires mouse (touchpad) movements for the text to show up - sometimes moving the mouse (touchpad) is required for the laptop to "wake up"; this is noticeable when Thunderbird downloads all messages from the period when the laptop was "frozen". I am running 10-amd64 r243234 (so with clang as cc) and ports 307851 without any local modifications. Since November 5 (when clang became cc) I noticed x11/nvidia-driver and x11-drivers/xf86-input-mouse were updated but rebuilding those with gcc did not make any difference. Maybe I missed a related port? All ports last updated before November 5th are still built with gcc. My /etc/make.conf and /etc/rc.conf are attached. Has anyone else been noticing this? Regards, René --------------050703060503040706040607 Content-Type: text/plain; charset=UTF-8; name="rc.conf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.conf" check_quotas="NO" font8x14="iso15-8x14" font8x16="iso15-8x16" font8x8="iso15-8x8" keymap="us.iso" moused_enable="YES" ipv6_activate_all_interfaces="YES" nfs_client_enable="YES" sshd_enable="YES" powerd_enable="YES" hostname="acer" wlans_iwn0="wlan0" ifconfig_wlan0="DHCP WPA" ifconfig_bge0="DHCP" ntpd_enable="YES" dumpdev="AUTO" linux_enable="YES" dbus_enable="YES" hald_enable="YES" ddb_enable="YES" webcamd_enable="YES" --------------050703060503040706040607 Content-Type: text/plain; charset=UTF-8; name="make.conf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="make.conf" CPUTYPE?=core2 DOC_LANG=en_US.ISO8859-1 nl_NL.ISO8859-1 PORTSDIR=/usr/ports/head WITHOUT_PKGTOOLS=yes # no pkg_* stuff WITH_VIM_OPTIONS=yes KERNCONF=GENERIC FORCE_MAKE_JOBS=yes # added by use.perl 2012-10-16 09:21:05 PERL_VERSION=5.14.2 --------------050703060503040706040607-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 10:43:07 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7263594 for ; Tue, 20 Nov 2012 10:43:07 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id CC2038FC12 for ; Tue, 20 Nov 2012 10:43:06 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5506594lah.13 for ; Tue, 20 Nov 2012 02:43:05 -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=WpWTZrR+vGn/scDnyBKmygLTodATgTLhjVRUBK7BHH4=; b=XBL4HRVG48AlBuBM7xPBqCTMqy0CwkVcP9Z7sqjul+8mVMZ27936Ll+28Y1h4KEHbL 5kdzRWfEr7ttCkE+mbMdR9z5sMrexfPU4KDUF1/r1RyIDXLxKHX1X46odFW2oay2HwZY BxyjF/6PzctJ7wRz3EJmHcLEJC/HrGdkVBitQTau03g3GpoID7Ze4Y2Cc+MPD6aL6xXs iESWZGvUZClkaJ7b2ysbnMinQQ1e9CshJw6UNWD9akcsFFThFQd2SRjkwViUCaAP6Vje mZeJC5uoAdQ2bz9jVfB4PJTzbABoPcz1QE0Ykd6Hh64p+4m9yN8UvmZ5FyNfMOIMaMhl yVDQ== MIME-Version: 1.0 Received: by 10.112.50.205 with SMTP id e13mr4132964lbo.57.1353408185122; Tue, 20 Nov 2012 02:43:05 -0800 (PST) Received: by 10.112.24.129 with HTTP; Tue, 20 Nov 2012 02:43:04 -0800 (PST) In-Reply-To: References: Date: Tue, 20 Nov 2012 11:43:04 +0100 Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) From: Olivier Smedts To: Paul Webster Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn/ddY/G3ZOckV+JNtS8MNMMidPWn6wnDzKFit2X0TVlcxJA2PO2Idhz819YgMZihM4CUEE Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 10:43:07 -0000 2012/11/20 Paul Webster : > I am aware this is a much discussed subject since the upgrade of PF, I > believe the final decision was that to many users are used to the old > style pf and an upgrade to the new syntax would cause to much confusion. But a change like this is expected in a new major branch, ie. 10-CURRENT. Not so in -STABLE branches of course. I don't see the problem here. Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 11:59:45 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07D97F16; Tue, 20 Nov 2012 11:59:45 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 207868FC13; Tue, 20 Nov 2012 11:59:43 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5572625lah.13 for ; Tue, 20 Nov 2012 03:59:42 -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=C/yhW0n2CeDzNVy/nbdoNtfsmSapNu2zcST18JywTeU=; b=KQt6/Oung8DmtMB3JPGyDsItzcJH4F11nYw+3l0Xto22iFklOqvCjz5NJFr9KTz8z8 qWXoMB640WDl7W/bPEj9bPn9ozGd991eg0TdDrFhaI5IsUN/KquDv9yT3BW/HRwtkHTV 1LmyYZQaUX3nDARcYOVpA98YKpFeAuyuTepWrsYcrSeSycX98/4lTu5fSKP7izSLDDfk 9WZz45/1U1strLTA+byyfD/PXVjhOqdwDlMiYBgUCjTQfV4mWPaJ0vlKrJkFXPGSCb5F fm/+DaqtB+7qSTXdCu/akFUcp4LprFmuihOBoovo+R8LreuMzagchKxQft3oiw98Ttpt V3MQ== MIME-Version: 1.0 Received: by 10.152.104.148 with SMTP id ge20mr14202676lab.51.1353412782284; Tue, 20 Nov 2012 03:59:42 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 03:59:42 -0800 (PST) In-Reply-To: <50AB5202.4070906@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> Date: Tue, 20 Nov 2012 13:59:42 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 11:59:45 -0000 Hi! > Are there any other unusual messages before this line? > Could you please try adding vfs.zfs.debug=1 to loader.conf and check again? > Could you also provide 'zdb -CC zsolar' output and 'zdb -l /dev/gpt/diskX' for > each of the disks. These could be uploaded somewhere as they can be quite lengthy. Please download and view files: http://tor.reactor-xg.kiev.ua/files/zfs/disk0.txt http://tor.reactor-xg.kiev.ua/files/zfs/disk2.txt http://tor.reactor-xg.kiev.ua/files/zfs/disk3.txt http://tor.reactor-xg.kiev.ua/files/zfs/zdb_CC_zsolar.txt http://tor.reactor-xg.kiev.ua/files/zfs/gpart_show.txt http://tor.reactor-xg.kiev.ua/files/zfs/gpart_show_label.txt http://tor.reactor-xg.kiev.ua/files/zfs/20121120_004.jpg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_005.jpg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_006.jpg --- Best regards, Andrei Lavreniyuk. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 12:03:57 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E65B650B; Tue, 20 Nov 2012 12:03:57 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id ECCD28FC12; Tue, 20 Nov 2012 12:03:56 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA26823; Tue, 20 Nov 2012 14:03:54 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TamYU-000DZM-5j; Tue, 20 Nov 2012 14:03:54 +0200 Message-ID: <50AB71A7.7050101@FreeBSD.org> Date: Tue, 20 Nov 2012 14:03:51 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 12:03:58 -0000 on 20/11/2012 12:45 Andrei Lavreniyuk said the following: > Hi! > > >> Are there any other unusual messages before this line? >> Could you please try adding vfs.zfs.debug=1 to loader.conf and check again? > >> Could you also provide 'zdb -CC zsolar' output and 'zdb -l /dev/gpt/diskX' for >> each of the disks. These could be uploaded somewhere as they can be quite lengthy. > > > Please view attached files. Thank you. "Can not parse the config for pool" message explains what happens but not why... Could you please apply the following patch, "un-ifdef" the DEBUG sections of it and try again? http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 12:13:40 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AAC0AA76 for ; Tue, 20 Nov 2012 12:13:40 +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 5C2FA8FC0C for ; Tue, 20 Nov 2012 12:13:40 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Tamhp-000188-Pd; Tue, 20 Nov 2012 07:13:33 -0500 Date: Tue, 20 Nov 2012 07:13:33 -0500 From: Gary Palmer To: Olivier Smedts Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) Message-ID: <20121120121333.GB88593@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: Paul Webster , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 12:13:40 -0000 On Tue, Nov 20, 2012 at 11:43:04AM +0100, Olivier Smedts wrote: > 2012/11/20 Paul Webster : > > I am aware this is a much discussed subject since the upgrade of PF, I > > believe the final decision was that to many users are used to the old > > style pf and an upgrade to the new syntax would cause to much confusion. > > But a change like this is expected in a new major branch, ie. > 10-CURRENT. Not so in -STABLE branches of course. I don't see the > problem here. So you don't expect people to upgrade boxes in place? I also guess you've never been 5,000 miles away from a box and typo'd something in the firewall and locked yourself out. The think how tons of FreeBSD users would feel if the default pf syntax was changed to be incompatible and they find themselves in a similar situation after an upgrade. Defaulting to open, while it could solve the problem (although I would suspect there could be edge cases where it doesn't), could be bad for other reasons. The other question that I haven't seen answered (or maybe even asked), but is relevant: what do we gain by going to a later version of pf? I.e. as an administrator, what benefit do I get by having to expend effort converting my filter rules? Gary From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 12:24:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 006056A3 for ; Tue, 20 Nov 2012 12:24:57 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 67D338FC14 for ; Tue, 20 Nov 2012 12:24:56 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5595457lah.13 for ; Tue, 20 Nov 2012 04:24:50 -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=dzNkq0jU/C+ChTRqYh+4p6C0YaoOplUThSI+uzGEvx4=; b=UlxXQB3Fnr+riKCMQcvjeeJBagF7Y4ylspbJAJ4c1d5GkpwRMlHlKCp0F1arEoO7sC KwSuxAC42q101Oud1vX5sW2UwGD7xy+Kt1RN502PiiU3PXE4nEzcFb6iJb8AtrcuO6mS mSEi87uCc184s/lyFS8YDpZi9d21WwXp9etO0zaiL/owcGp7ytavRyBB4Z3Z/VwFV7Hn ho8d3iOMLDkb44kPAMiO3jqRW0YBKJuaXTsGZY1+QZydk/PKtzngDQ8CeRuCeLGBSkGm oeK0FGWYfz/z/KFFGDXT1G3ydB3obKDtr3hadaFhv4KUK/8pnfn58Sph9Zz3v/J1aeAZ dZVA== MIME-Version: 1.0 Received: by 10.152.106.79 with SMTP id gs15mr14614684lab.31.1353414289870; Tue, 20 Nov 2012 04:24:49 -0800 (PST) Received: by 10.112.24.129 with HTTP; Tue, 20 Nov 2012 04:24:49 -0800 (PST) In-Reply-To: <20121120121333.GB88593@in-addr.com> References: <20121120121333.GB88593@in-addr.com> Date: Tue, 20 Nov 2012 13:24:49 +0100 Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) From: Olivier Smedts To: Gary Palmer Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlk7w9rP10Kp0MLYAMj9mJS2fWwlP+L6gAWSWlShG7Pz91EQjibHQnZgJxoyan1fv4eflKR Cc: Paul Webster , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 12:24:58 -0000 2012/11/20 Gary Palmer : > On Tue, Nov 20, 2012 at 11:43:04AM +0100, Olivier Smedts wrote: >> 2012/11/20 Paul Webster : >> > I am aware this is a much discussed subject since the upgrade of PF, I >> > believe the final decision was that to many users are used to the old >> > style pf and an upgrade to the new syntax would cause to much confusion. >> >> But a change like this is expected in a new major branch, ie. >> 10-CURRENT. Not so in -STABLE branches of course. I don't see the >> problem here. > > So you don't expect people to upgrade boxes in place? I expect that before upgrading to a *major* version you should read an updating or "what's changed" documentation. > I also guess you've never been 5,000 miles away from a box and typo'd something > in the firewall and locked yourself out. The think how tons of FreeBSD > users would feel if the default pf syntax was changed to be incompatible and > they find themselves in a similar situation after an upgrade. Defaulting to > open, while it could solve the problem (although I would suspect there could > be edge cases where it doesn't), could be bad for other reasons. This already happened to me but, no, not during a major upgrade because I won't do this kind of work without at least someone on-site. > The other question that I haven't seen answered (or maybe even asked), but > is relevant: what do we gain by going to a later version of pf? I.e. as an > administrator, what benefit do I get by having to expend effort converting > my filter rules? > > Gary At some time we'll surely *have* to upgrade our pf, because the legacy version won't be supported upstream. I say that a major release is the most appropriated place for such a change. Another question : how did OpenBSD managed this change ? Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 12:35:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9F1FAE1; Tue, 20 Nov 2012 12:35:02 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E9C358FC08; Tue, 20 Nov 2012 12:35:01 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5604778lah.13 for ; Tue, 20 Nov 2012 04:35:00 -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 :content-type; bh=vX9OJW9LVS/oprEriBSPFbzie3dZUb4xr26OFVZGDGQ=; b=QxligrTLfiGNwkZ25NrlUVnv0XludUDUq36oOcJic8yNf7LDFVq+88fUbaFagL4Cb1 7V0gaYZWoAQzg9Hl34VA3dTmlDLlb3Ynj7p7xiVBo7EedPDkk6TjMyVh+tr1bxGNLgXu 8ui1qpqZA4cjW7e81SH032GioXPG/hN8dQpaBXLmE1GXAdGVu8gyQjcD/3LMDMGjAGrP J5b3bFkj028weKRJCt1ShlwCXwFkSjMAKaicMErjn+v/8Es9J1Mel8qHeEq+Dyt72IVY TzUS4EFIEYhjxbDg5YGKHg/zouf1aVLP4/fXRO2mSl9wPbFSBVum12Cz5uUmD/OEM2PH Gi8Q== MIME-Version: 1.0 Received: by 10.112.46.37 with SMTP id s5mr6342652lbm.67.1353414900814; Tue, 20 Nov 2012 04:35:00 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 04:35:00 -0800 (PST) In-Reply-To: References: <50AB5202.4070906@FreeBSD.org> Date: Tue, 20 Nov 2012 14:35:00 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Tom Evans , freebsd-current@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 12:35:02 -0000 2012/11/20 Tom Evans : > All those files just redirect to the homepage for me... Fixed. Please download and view files: http://tor.reactor-xg.kiev.ua/files/zfs/disk0.txt http://tor.reactor-xg.kiev.ua/files/zfs/disk2.txt http://tor.reactor-xg.kiev.ua/files/zfs/disk3.txt http://tor.reactor-xg.kiev.ua/files/zfs/zdb_CC_zsolar.txt http://tor.reactor-xg.kiev.ua/files/zfs/gpart_show.txt http://tor.reactor-xg.kiev.ua/files/zfs/gpart_show_label.txt http://tor.reactor-xg.kiev.ua/files/zfs/20121120_004.jpeg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_005.jpeg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_006.jpeg From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 12:41:44 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7881ECFF; Tue, 20 Nov 2012 12:41:44 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 783E48FC17; Tue, 20 Nov 2012 12:41:42 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5611025lah.13 for ; Tue, 20 Nov 2012 04:41:42 -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=O0EqJBwAOE31skW/2JwKWn5yiVv5y1dFR6xwprwr+9I=; b=jNvR+tqVyxrbpgCRW30suQT0FxMO4rG78Q5U2y9RqUALfTAfpCfWL3/PpwQRaluIp9 KGmGwUIoqdxHc+qOYsJvikn8CFxV2Mo7qviREa1hGkSqxFOOPgsjwH+t6javsY3Q0c4s GJ2gAcd1WJF/Y2gg3lAtchOK8JU1nkBmE/sb0GEOhSkc/vWB7xsXyebjE06eipVww9Um /8s6Zplj58eF3N4wXVv34UYXIYNTs0OVdTQU+uybXy7rTiHvrpNPW8I8iR+B0/r3jwYz 0ZNKmK3RPPnkF2kjReIErCCJ6btpMSUEswClWznKzsLm75FgdlOadGL/BFutdbc3F7iS Gokg== MIME-Version: 1.0 Received: by 10.112.39.225 with SMTP id s1mr6358133lbk.117.1353415301877; Tue, 20 Nov 2012 04:41:41 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 04:41:41 -0800 (PST) In-Reply-To: <50AB71A7.7050101@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> Date: Tue, 20 Nov 2012 14:41:41 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 12:41:44 -0000 Hi! > "Can not parse the config for pool" message explains what happens but not why... > > Could you please apply the following patch, "un-ifdef" the DEBUG sections of it > and try again? > http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff I use spa_generate_rootconf.debug.diff. make kernel && reboot No new debug messages. Pool cannot mount. --- Best regards, Andrei Lavreniyuk. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:03:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB181416; Tue, 20 Nov 2012 13:03:16 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C8D488FC13; Tue, 20 Nov 2012 13:03:15 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5631134lah.13 for ; Tue, 20 Nov 2012 05:03:14 -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=2/e4JBZsFV5xNCwOLsMlMD576nmGdTGAbDJkhl+Bi5k=; b=qH1Q/aO5uIUjtYx0jQp/lV+761Tjp22uu6SpCdNwcatGAzV1yatLCuaLmRWxjJpP2p pV0htflVChV6ILvJ+V6sUyAhIb0ZAoM4lPUYOInfJMud7Qs5DWeT2vxCtmNnHYRvKz+G mOIBxMZB7xQa5cCohj6I4hGhsBSx6p3C6UQZEGuboe+sBOu+BwpmWw+P6WIZe4elybCi Stmno9FWP4i1WH+/g/k9K6JTp5b4tSYkKW/K1uI67AcFc4Ci5lDykZ2NkJNgQvQkxbWh YWFFSDdNjq17SJJb9+TFmGtu3VPX1FERvNCe4tyf81HTWHg69h9j7n2K6uu1p1EAUr6h WRbQ== MIME-Version: 1.0 Received: by 10.112.39.225 with SMTP id s1mr6379595lbk.117.1353416594374; Tue, 20 Nov 2012 05:03:14 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 05:03:14 -0800 (PST) In-Reply-To: References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> Date: Tue, 20 Nov 2012 15:03:14 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:03:17 -0000 2012/11/20 Andrei Lavreniyuk : > Hi! > > >> "Can not parse the config for pool" message explains what happens but not why... >> >> Could you please apply the following patch, "un-ifdef" the DEBUG sections of it >> and try again? >> http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff > > > I use spa_generate_rootconf.debug.diff. > > make kernel && reboot > > No new debug messages. Pool cannot mount. This problem is only on systems with raidz. System with ZFS Mirror work normally. --- Best regards, Andrei Lavreniyuk. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:08:33 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B27768BE; Tue, 20 Nov 2012 13:08:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BA5D88FC1B; Tue, 20 Nov 2012 13:08:31 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA27485; Tue, 20 Nov 2012 15:08:23 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AB80C6.1090507@FreeBSD.org> Date: Tue, 20 Nov 2012 15:08:22 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:08:33 -0000 on 20/11/2012 14:41 Andrei Lavreniyuk said the following: > Hi! > > >> "Can not parse the config for pool" message explains what happens but not why... >> >> Could you please apply the following patch, "un-ifdef" the DEBUG sections of it >> and try again? >> http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff > > > I use spa_generate_rootconf.debug.diff. What about the " "un-ifdef" the DEBUG sections of it" part? > make kernel && reboot > > No new debug messages. Pool cannot mount. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:12:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6E25AC1; Tue, 20 Nov 2012 13:12:51 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id D97728FC16; Tue, 20 Nov 2012 13:12:50 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5641217lah.13 for ; Tue, 20 Nov 2012 05:12:49 -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=BIJFv0RJNB1Zj1WAf4+Z3NSottdAPrmDKLZuDb4osO8=; b=01yl2RYhwAFQiZoSPdcl+WnIT890L+n2FTEFPYG6DYrbie0zUFDv8Z6nue0jWj6ZzV gLdMRL2KSRSElnt9+FExihVAqBcxwVxPdjJnt6FiSXjZfg5MlZg7DRrv5c4vp5ZzynPo CYmo278ttM4kjdMxtjq4DaaDSGOa4Kt8Vu4SFLGzjgPsGz/8FsAGH9iANcsDqy9YipQ8 behvu7XAOB7d5cXkIx9LxoKoM/g/ogZQWmJUbD5uYVpg+OLLbLI9nYSOwxU+7e+7C/15 ZY6WiyB3DGxTuFHuoOQ5Zuaxy0RlDL6R30HkRpsS6q+mnHnOdloKwNwS7lHvu+UQK2Eb hCKQ== MIME-Version: 1.0 Received: by 10.112.39.225 with SMTP id s1mr6390018lbk.117.1353417169455; Tue, 20 Nov 2012 05:12:49 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 05:12:49 -0800 (PST) In-Reply-To: <50AB80C6.1090507@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> Date: Tue, 20 Nov 2012 15:12:49 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:12:52 -0000 2012/11/20 Andriy Gapon : > on 20/11/2012 14:41 Andrei Lavreniyuk said the following: >> Hi! >> >> >>> "Can not parse the config for pool" message explains what happens but not why... >>> >>> Could you please apply the following patch, "un-ifdef" the DEBUG sections of it >>> and try again? >>> http://people.freebsd.org/~avg/spa_generate_rootconf.debug.diff >> >> >> I use spa_generate_rootconf.debug.diff. > > What about the " "un-ifdef" the DEBUG sections of it" part? Sorry. A few minutes ... > >> make kernel && reboot >> >> No new debug messages. Pool cannot mount. > > -- > Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:34:21 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCF657B; Tue, 20 Nov 2012 13:34:21 +0000 (UTC) (envelope-from andy.lavr@gmail.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 CBF498FC13; Tue, 20 Nov 2012 13:34:20 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so3057912lbb.13 for ; Tue, 20 Nov 2012 05:34:19 -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=P3+eFOD8Cwtu/7eDudUY16h6T2/5JozG3Gjb4j/Fez4=; b=OEaZo2aOF6YjvKekHxE5C9X5Vw/Pc8m8w6EhIlXHSp3h1dCM9wT9RW5sHJNDv7mKWS d+AVywqoO2p2wae79ycm34CbqlI0JNXLW1A5uettNUgTDGjt1CTrrMYZ+oVLVc+eHlLL hJjK++B3jYrfJcSI4L+SfHLcCaMJBJ7HGMSpAxLapYb2nyX4e0cIvXlbqmn7r1+INiB3 59x12yZlHLQAScqlqJ44ARI7fRbm/XLRsstB7wMQENqxZJ6lzxNyBGNkgTF3CHxJGDVQ SemVMpj+MXqC29e6GRi60jP+1UhtG8/EyvPDVhOGzH0bv5sxzn4DF5bA3eqcifF/XdvG rI8A== MIME-Version: 1.0 Received: by 10.112.54.40 with SMTP id g8mr6534959lbp.49.1353418459609; Tue, 20 Nov 2012 05:34:19 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 05:34:19 -0800 (PST) In-Reply-To: <50AB80C6.1090507@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> Date: Tue, 20 Nov 2012 15:34:19 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:34:21 -0000 > What about the " "un-ifdef" the DEBUG sections of it" part? http://tor.reactor-xg.kiev.ua/files/zfs/20121120_000.jpeg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_001.jpeg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_002.jpeg http://tor.reactor-xg.kiev.ua/files/zfs/20121120_003.jpeg From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:44:49 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6ACA34C5 for ; Tue, 20 Nov 2012 13:44:49 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id DF4528FC19 for ; Tue, 20 Nov 2012 13:44:48 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so1559584wey.13 for ; Tue, 20 Nov 2012 05:44:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CcrAJRUXOqk6atGGD0uORRHWOGq/tnD2ExdSVTR+OaA=; b=HjHbDnBh5wwQkz9M329hP3T5DJFEfQFBeTaMv2bqMWHHe1MtbUGDQ/DrEs6xFVoWz6 oAl/TMcX3p/Q5hAyL2rT5d7XXr5TuzuRwy4Ps7FN5VuGGgdBvXKG0VIz8fv92xBLyXai 1z3Gf84gyykYNKHikgTFHerD4lbOAJWG0XY9A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=CcrAJRUXOqk6atGGD0uORRHWOGq/tnD2ExdSVTR+OaA=; b=JGmut4LsWfxRAqbZHXC38P1gCN1pptT/07NWsybtsge4FG8gmqO6nnj5KxZZN99zWh +znMg+QLlDPK/a4M7+LFaNWfyo+CvsRtMhlPdmv3N9Wu5x1gCgB26pXlUlZPj+xhfsxN IXiJYSK3bMOj9LiXr9pio4Ro+/0mxZAlof+IwONOF3yw9Uv+WRx+t3sWnuX2lDbawgg3 0jPK6pLKWeoeeXrm2Gr4uaGKMi418yxEsCqnmdU74zljkMmmq+5URHra3Jsh6yr+TUwn CD6WbmrSqvbmO8KTz+9cjIwwPOmnGext1RBq18bftmk7PSKfdlMC+NreB0JmtK1Qa0Rk Qxlg== MIME-Version: 1.0 Received: by 10.216.210.3 with SMTP id t3mr5456382weo.130.1353419087649; Tue, 20 Nov 2012 05:44:47 -0800 (PST) Sender: decke@bluelife.at Received: by 10.194.43.40 with HTTP; Tue, 20 Nov 2012 05:44:47 -0800 (PST) X-Originating-IP: [80.123.233.199] In-Reply-To: <50AB58FA.505@freebsd.org> References: <50AB58FA.505@freebsd.org> Date: Tue, 20 Nov 2012 14:44:47 +0100 X-Google-Sender-Auth: _53wKh9fR7Uat1UgkrsAFVREK2Y Message-ID: Subject: Re: sluggish X.org/Xfce behavior From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: =?ISO-8859-1?Q?Ren=E9_Ladan?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlu9isDJSOTHIt1nVPUfY33m3+HWNAb1CUuBhIfYi9hiOXyOEGu3pAgYwXZ10Wh6kaSSA2/ Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:44:49 -0000 On Tue, Nov 20, 2012 at 11:18 AM, Ren=E9 Ladan wrote: > Hi, > > since last weekend (November 17th) I have been noticing a sluggish > behavior of X.org/Xfce. Typical symptoms are: > - Alt-Tab not reacting all of the time > - pulldown/popup menus not allowing selections with mouse (typically in > Terminal/pidgin), or moving the mouse (touchpad) results in an automatic > click > - typing something in a Terminal requires mouse (touchpad) movements for > the text to show up > - sometimes moving the mouse (touchpad) is required for the laptop to > "wake up"; this is noticeable when Thunderbird downloads all messages > from the period when the laptop was "frozen". > > I am running 10-amd64 r243234 (so with clang as cc) and ports 307851 > without any local modifications. Since November 5 (when clang became cc) > I noticed x11/nvidia-driver and x11-drivers/xf86-input-mouse were > updated but rebuilding those with gcc did not make any difference. Maybe > I missed a related port? All ports last updated before November 5th are > still built with gcc. > > My /etc/make.conf and /etc/rc.conf are attached. > > Has anyone else been noticing this? Very interesting symptoms. I had the same until xf86-input-mouse was fixed with the last update. The symptoms were reproducible when attaching an USB mouse which caused all kind of weird X11 (re)drawing issues. --=20 Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:50:12 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B3D4775; Tue, 20 Nov 2012 13:50:12 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 80B098FC19; Tue, 20 Nov 2012 13:50:10 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5678680lah.13 for ; Tue, 20 Nov 2012 05:50:10 -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=8A0rF/58fq72fiLdX+OLReMfLjI/0jzPWSrNG6DutXs=; b=PRBnYLBGb/Q+fwbNlM17dGrrzezmyclItWH+WV58M/t09btjOZCzHuV2xLznQTqgpQ szfpQARXwkD6q7R1Im0TyeS1qEy28wssQxpkeIygRxj0PqFjUEsgen6mirKRRy3LSjFJ piUWN90LCu4PoFpEqHrndQdQyVKGrRRXAa1iFVbaU+SRzAkLaedj30yXF7CbE+9XT1uT DN220Jwleitza5b2TalghROLG+t+eilDaC1YcwMk0LAB8Eh3pYf8ZhFvkYkqVNEfBYIt g2UCouusB2J1hnRv+J5r+AyZkrJLb4/TZHOHEGkwGPswkI+888jyvaP0OttEK/DA9us1 uDMg== MIME-Version: 1.0 Received: by 10.112.83.133 with SMTP id q5mr3931628lby.40.1353419409927; Tue, 20 Nov 2012 05:50:09 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.114.12.226 with HTTP; Tue, 20 Nov 2012 05:50:09 -0800 (PST) In-Reply-To: References: <50AB58FA.505@freebsd.org> Date: Tue, 20 Nov 2012 14:50:09 +0100 X-Google-Sender-Auth: 60wLh3am6lC4v-64kOeOnX5gqcU Message-ID: Subject: Re: sluggish X.org/Xfce behavior From: CeDeROM To: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: =?UTF-8?Q?Ren=C3=A9_Ladan?= , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:50:12 -0000 On Tue, Nov 20, 2012 at 2:44 PM, Bernhard Fr=C3=B6hlich = wrote: > Very interesting symptoms. I had the same until xf86-input-mouse was fixe= d > with the last update. The symptoms were reproducible when attaching an > USB mouse which caused all kind of weird X11 (re)drawing issues. Exactly, known issue with xorg-mouse and xorg configuration + hald + allowEmptyInput, see list archive for good explanation :-) Best regards :-) Tomek --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:52:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7699C8C8 for ; Tue, 20 Nov 2012 13:52:59 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E52D18FC08 for ; Tue, 20 Nov 2012 13:52:58 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5681614lah.13 for ; Tue, 20 Nov 2012 05:52:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=GtUWhSx13dMnvdKoSvViubqaoXcWriwXooXE6kMd5hU=; b=wtLh1/GcIZoSpMpoxcjhS0/Gz+/tkjGxqfmJ2KkZQ/tVDc53z3RSqhN0HnttjMhCLo 9kuITMhIKva/hxV6bJ0azFQFK5M/MO9KY7VFgoJ3yiZqG64t5IxHCiHCrrG8UoNWoccr XR77450sd+2Ijgwl8+CRqcasiHI4NWM3X2pgbAaBnuVn4rj8hY2mYC7ckn3cbe6T90+V /lWqwMIYYMxWvjSMHVTAoZ9yvva5+4OjprUTF1NHUjEqHnKfblQe+X2AGFO4FTSFm66e 9bgC8CuatLsFExsCSpZv7im/rX6QwKoubqCoARYMgd/KquzaLmRtvqUo62jXBmQHSY7o IO8A== MIME-Version: 1.0 Received: by 10.152.110.74 with SMTP id hy10mr14876159lab.54.1353419577383; Tue, 20 Nov 2012 05:52:57 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.114.12.226 with HTTP; Tue, 20 Nov 2012 05:52:57 -0800 (PST) Date: Tue, 20 Nov 2012 14:52:57 +0100 X-Google-Sender-Auth: hfaswIU_I28k3rZmQ7m8rNG-WfU Message-ID: Subject: wifi + wpa_supplicant in 9.1-RC3 From: CeDeROM To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:52:59 -0000 Hello :-) I have some problems with WiFi connectivity on my Dell Latitude E4310 laptop with Intel card. Very often connection is broken, although windows clients of the same network is working fine. I need to turn radio off and on, sometimes this does not help, I need to kill wpa_supplicant and start one by hand, so probably this is something related with wpa_supplicant. Anyone observed similar issues? Btw if WiFi N supported? Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 13:56:50 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DABB1D08; Tue, 20 Nov 2012 13:56:50 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E6FCD8FC0C; Tue, 20 Nov 2012 13:56:49 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA27988; Tue, 20 Nov 2012 15:56:47 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AB8C1F.2040108@FreeBSD.org> Date: Tue, 20 Nov 2012 15:56:47 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 13:56:51 -0000 on 20/11/2012 15:34 Andrei Lavreniyuk said the following: >> What about the " "un-ifdef" the DEBUG sections of it" part? > > > http://tor.reactor-xg.kiev.ua/files/zfs/20121120_000.jpeg > http://tor.reactor-xg.kiev.ua/files/zfs/20121120_001.jpeg > http://tor.reactor-xg.kiev.ua/files/zfs/20121120_002.jpeg > http://tor.reactor-xg.kiev.ua/files/zfs/20121120_003.jpeg > Sorry to make you jump through so many hoops. Now that I see that the probed config is entirely correct, the problem appears to be quite obvious: vdev_alloc is not able to properly use spa_version in this context because spa_ubsync is not initialized yet. Let me think about how to fix this. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:16:56 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01C6CADB; Tue, 20 Nov 2012 14:16:55 +0000 (UTC) (envelope-from fbsd8@a1poweruser.com) Received: from mail-03.name-services.com (mail-03.name-services.com [69.64.155.195]) by mx1.freebsd.org (Postfix) with ESMTP id CE1D88FC14; Tue, 20 Nov 2012 14:16:55 +0000 (UTC) Received: from [10.0.10.3] ([173.88.197.103]) by mail-03.name-services.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 20 Nov 2012 06:16:57 -0800 Message-ID: <50AB90DA.4010404@a1poweruser.com> Date: Tue, 20 Nov 2012 09:16:58 -0500 From: Fbsd8 User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Olivier Smedts Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: <20121120121333.GB88593@in-addr.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Nov 2012 14:16:57.0183 (UTC) FILETIME=[B2D9FEF0:01CDC729] X-Sender: fbsd8@a1poweruser.com X-Authenticated-Sender: fbsd8@a1poweruser.com X-EchoSenderHash: [fbsd8]-[a1poweruser*com] Cc: Gary Palmer , Paul Webster , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:16:56 -0000 Olivier Smedts wrote: > 2012/11/20 Gary Palmer : >> On Tue, Nov 20, 2012 at 11:43:04AM +0100, Olivier Smedts wrote: >>> 2012/11/20 Paul Webster : >>>> I am aware this is a much discussed subject since the upgrade of PF, I >>>> believe the final decision was that to many users are used to the old >>>> style pf and an upgrade to the new syntax would cause to much confusion. >>> But a change like this is expected in a new major branch, ie. >>> 10-CURRENT. Not so in -STABLE branches of course. I don't see the >>> problem here. >> So you don't expect people to upgrade boxes in place? > > I expect that before upgrading to a *major* version you should read an > updating or "what's changed" documentation. > >> I also guess you've never been 5,000 miles away from a box and typo'd something >> in the firewall and locked yourself out. The think how tons of FreeBSD >> users would feel if the default pf syntax was changed to be incompatible and >> they find themselves in a similar situation after an upgrade. Defaulting to >> open, while it could solve the problem (although I would suspect there could >> be edge cases where it doesn't), could be bad for other reasons. > > This already happened to me but, no, not during a major upgrade > because I won't do this kind of work without at least someone on-site. > >> The other question that I haven't seen answered (or maybe even asked), but >> is relevant: what do we gain by going to a later version of pf? I.e. as an >> administrator, what benefit do I get by having to expend effort converting >> my filter rules? >> >> Gary > > At some time we'll surely *have* to upgrade our pf, because the legacy > version won't be supported upstream. I say that a major release is the > most appropriated place for such a change. > > Another question : how did OpenBSD managed this change ? > > Cheers > Hay I have been down this road myself. It's no longer possible to just re-port the current OpenBSD version of PF to FreeBSD. The FreeBSD version has been rewritten. Read all the threads shown in this post for all the gory details. [HEADS UP] merging projects/pf into head http://lists.freebsd.org/pipermail/freebsd-pf/2012-September/006740.html From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:17:16 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF03ECB5; Tue, 20 Nov 2012 14:17:16 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 027638FC0C; Tue, 20 Nov 2012 14:17:15 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA28242; Tue, 20 Nov 2012 16:17:13 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AB90E9.5070102@FreeBSD.org> Date: Tue, 20 Nov 2012 16:17:13 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> In-Reply-To: <50AB8C1F.2040108@FreeBSD.org> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:17:17 -0000 on 20/11/2012 15:56 Andriy Gapon said the following: > on 20/11/2012 15:34 Andrei Lavreniyuk said the following: >>> What about the " "un-ifdef" the DEBUG sections of it" part? >> >> >> http://tor.reactor-xg.kiev.ua/files/zfs/20121120_000.jpeg >> http://tor.reactor-xg.kiev.ua/files/zfs/20121120_001.jpeg >> http://tor.reactor-xg.kiev.ua/files/zfs/20121120_002.jpeg >> http://tor.reactor-xg.kiev.ua/files/zfs/20121120_003.jpeg >> > > Sorry to make you jump through so many hoops. > Now that I see that the probed config is entirely correct, the problem appears to > be quite obvious: vdev_alloc is not able to properly use spa_version in this > context because spa_ubsync is not initialized yet. > > Let me think about how to fix this. I hope that the following simple patch should fix the problem: http://people.freebsd.org/~avg/spa_import_rootpool.version.diff -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:34:44 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B5C44CA; Tue, 20 Nov 2012 14:34:44 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id D424F8FC17; Tue, 20 Nov 2012 14:34:43 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id qAKEYguG036686; Tue, 20 Nov 2012 07:34:42 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id qAKEYgnN036683; Tue, 20 Nov 2012 07:34:42 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 20 Nov 2012 07:34:42 -0700 (MST) From: Warren Block To: =?ISO-8859-15?Q?Ren=E9_Ladan?= Subject: Re: sluggish X.org/Xfce behavior In-Reply-To: <50AB58FA.505@freebsd.org> Message-ID: References: <50AB58FA.505@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY=------------050703060503040706040607 Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 20 Nov 2012 07:34:42 -0700 (MST) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:34:44 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --------------050703060503040706040607 Content-Type: TEXT/PLAIN; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Tue, 20 Nov 2012, René Ladan wrote: > since last weekend (November 17th) I have been noticing a sluggish > behavior of X.org/Xfce. Typical symptoms are: > - Alt-Tab not reacting all of the time > - pulldown/popup menus not allowing selections with mouse (typically in > Terminal/pidgin), or moving the mouse (touchpad) results in an automatic > click > - typing something in a Terminal requires mouse (touchpad) movements for > the text to show up > - sometimes moving the mouse (touchpad) is required for the laptop to > "wake up"; this is noticeable when Thunderbird downloads all messages > from the period when the laptop was "frozen". This is one of the problems that having Option "AllowEmptyInput" "Off" in xorg.conf causes. If you have that, substitute Option "AutoAddDevices" "Off" in the same place. --------------050703060503040706040607-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:38:11 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41B8767D for ; Tue, 20 Nov 2012 14:38:11 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5788FC0C for ; Tue, 20 Nov 2012 14:38:09 +0000 (UTC) Received: (qmail 55076 invoked by uid 89); 20 Nov 2012 14:38:03 -0000 Received: by simscan 1.4.0 ppid: 55071, pid: 55073, t: 0.1494s scanners: attach: 1.4.0 clamav: 0.97.3/m:54/d:15603 Received: from unknown (HELO suse3) (rainer@ultra-secure.de@212.71.117.1) by mail.ultra-secure.de with ESMTPA; 20 Nov 2012 14:38:03 -0000 Date: Tue, 20 Nov 2012 15:38:02 +0100 From: Rainer Duffner To: Olivier Smedts Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) Message-ID: <20121120153802.288aec92@suse3> In-Reply-To: References: <20121120121333.GB88593@in-addr.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Gary Palmer , Paul Webster , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:38:11 -0000 Am Tue, 20 Nov 2012 13:24:49 +0100 schrieb Olivier Smedts : > Another question : how did OpenBSD managed this change ? AFAIK, their users are used to stuff just disappearing or changing. Remember that pf started as a replacement to ipf and the rulesets had to be rewritten anyway. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:43:27 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A91F8C9; Tue, 20 Nov 2012 14:43:27 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id C50D08FC13; Tue, 20 Nov 2012 14:43:26 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3Y5V5n0ntmzGMgj; Tue, 20 Nov 2012 15:43:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= message-id:content-transfer-encoding:content-type:content-type :mime-version:in-reply-to:references:user-agent:date:date :subject:subject:organization:from:from:received:received :received:vbr-info; s=jakla2; t=1353422598; x=1356014599; bh=eEw QmbnmfGv+I5LmtyjfzYG67Iv9e6xlh8zdX6dFndE=; b=eh7vXC4AeqzGc4fXrt0 zgmRiRHWp1eUv1PC9XdcsykWqL9xmfQ0nKpC68UVZDCWSbcybslps7ebpyprbTq1 PH4bT2fgJG/1TMFQ/upOp66VKYJfDUnrWI3gdXFxMm9X8S8EXk73VaIch3eKmD+t De87YhCJ5DxBjg8iwr01+ONA= VBR-Info: md=ijs.si; mc=all; mv=dwl.spamhaus.org; X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id 4fOdnWBJvtQa; Tue, 20 Nov 2012 15:43:18 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP; Tue, 20 Nov 2012 15:43:18 +0100 (CET) Received: from neli.ijs.si (unknown [IPv6:2001:1470:ff80:0:21c:c0ff:feb1:8c91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mildred.ijs.si (Postfix) with ESMTPSA id 45A7B11D; Tue, 20 Nov 2012 15:43:18 +0100 (CET) From: Mark Martinec Organization: J. Stefan Institute To: freebsd-pf@freebsd.org Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. Date: Tue, 20 Nov 2012 15:43:17 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:43:27 -0000 Paul Webster wrote: > I am aware this is a much discussed subject since the upgrade of PF, > I believe the final decision was that too many users are used to the old > style pf and an upgrade to the new syntax would cause too much confusion. I don't buy that. Think of a confusion in a year of two when OpenBSD PF rules and the PF documentation won't match the legacy syntax in FreeBSD's PF. Maxim Khitrov wrote: > > 1) To move to the newer pf and just add to releases notes what had > > happened, > My vote is for option 1, but I'll also be happy with option 2 if it > costs little to maintain both versions. I'm pretty much for anything > that brings pf in sync (or close to it) with OpenBSD. My sentiments exactly. Olivier Smedts wrote: > But a change like this is expected in a new major branch, ie. > 10-CURRENT. Not so in -STABLE branches of course. I don't see the > problem here. Indeed. Gary Palmer wrote: > So you don't expect people to upgrade boxes in place? > I also guess you've never been 5,000 miles away from a box and typo'd > something in the firewall and locked yourself out. The think how tons > of FreeBSD users would feel if the default pf syntax was changed to be > incompatible and they find themselves in a similar situation after an > upgrade. The risk of locking oneself out even on minor fiddling with fw rules on a remote machine, let alone upgrading its OS, is something that every administrator is already aware if. Working without a safety net is unwise for a hobbyist, and unacceptable for a professional. I don't think the above argument holds water. Olivier Smedts wrote: > Another question : how did OpenBSD managed this change ? This is from http://www.openbsd.org/faq/upgrade46.html | | If you reboot your system without a usable pf.conf file in place, your pf | rules will not be loaded, and you will end up using the default rule set, | which will block all traffic EXCEPT for ssh over the standard port 22. | This means that if you do not fix your pf.conf rules before rebooting, | you may be greeted by a box that does not even respond to pings. | Do not panic, as you can still ssh to the box, assuming you have sshd(8) | listening on the usual port. Gary Palmer wrote: > The other question that I haven't seen answered (or maybe even asked), but > is relevant: what do we gain by going to a later version of pf? I.e. as an > administrator, what benefit do I get by having to expend effort converting > my filter rules? For one thing, I'm desperately awaiting NAT64 support (the 'af-to' translation rule in newer pf (5.1?), committed on 2011-10). Other: packet normalization (scrub) has been reworked and simplified, and is now a rulset option. Considering that scrub is currently broken (9.1, see list of PF bugs in FreeBSD), along with several other bugs that need fixing, it seems the (scarce) manpower would better be spent in moving on, than keeping the already leaky (buggy) pf afloat. I think the compatibility issue should not be used as an excuse for not moving on. You can't make an omelette without breaking eggs. Mark From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 14:59:08 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53966F65; Tue, 20 Nov 2012 14:59:08 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8E08FC15; Tue, 20 Nov 2012 14:59:06 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so5754354lah.13 for ; Tue, 20 Nov 2012 06:59:06 -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=WJrmU+WwboRIoNICAisgqtgXckuovl+rtt9WarvthC0=; b=bgAOa7c75o9+OfJcwggOBVJXL+dPU01q6ZgPXPrJfts44Zjc7CCOmHq9Px8EXv2X0/ ECJy/0JcyjIL1JADvvAT4stF8dJopOIUKRKkTdroRZ4InknF7KGhedEm3N3S16sIb8U7 WOvjiuIwaH9bKKr8A3X9G38ZO7Qbh+Jx5QKsaIuI6fKRB1aFjPICYT039C8FhGvo0b/R J0li12qFkjIh45/X6euoAdJg59L916i8Gq3MICETW/LCtE694TBwPGofGhoLbktTiGAe 8a8ciugLCwjlXFJPYYKrxltko/SC9qM9PkCblfa1EZdxNOreUkAub9WoEC1hEEOJ5W4Q JA7w== MIME-Version: 1.0 Received: by 10.112.39.225 with SMTP id s1mr6502787lbk.117.1353423546145; Tue, 20 Nov 2012 06:59:06 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 06:59:06 -0800 (PST) In-Reply-To: <50AB90E9.5070102@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> <50AB90E9.5070102@FreeBSD.org> Date: Tue, 20 Nov 2012 16:59:06 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 14:59:08 -0000 >> Sorry to make you jump through so many hoops. >> Now that I see that the probed config is entirely correct, the problem appears to >> be quite obvious: vdev_alloc is not able to properly use spa_version in this >> context because spa_ubsync is not initialized yet. >> >> Let me think about how to fix this. > > I hope that the following simple patch should fix the problem: > http://people.freebsd.org/~avg/spa_import_rootpool.version.diff At mount system trap and reboot. --- Best regards, Andrei Lavreniyuk. From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 15:06:07 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3406F400; Tue, 20 Nov 2012 15:06:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 37A428FC1B; Tue, 20 Nov 2012 15:06:05 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA28762; Tue, 20 Nov 2012 17:06:04 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AB9C5B.6030006@FreeBSD.org> Date: Tue, 20 Nov 2012 17:06:03 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> <50AB90E9.5070102@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 15:06:07 -0000 on 20/11/2012 16:59 Andrei Lavreniyuk said the following: >>> Sorry to make you jump through so many hoops. >>> Now that I see that the probed config is entirely correct, the problem appears to >>> be quite obvious: vdev_alloc is not able to properly use spa_version in this >>> context because spa_ubsync is not initialized yet. >>> >>> Let me think about how to fix this. >> >> I hope that the following simple patch should fix the problem: >> http://people.freebsd.org/~avg/spa_import_rootpool.version.diff > > > At mount system trap and reboot. > Unexpected. Can you catch the backtrace of the panic? If you have it on the screen. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 16:00:33 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E33DA5F; Tue, 20 Nov 2012 16:00:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1166A8FC15; Tue, 20 Nov 2012 16:00:31 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA29224; Tue, 20 Nov 2012 18:00:29 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50ABA91D.9090905@FreeBSD.org> Date: Tue, 20 Nov 2012 18:00:29 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> <50AB90E9.5070102@FreeBSD.org> <50AB9C5B.6030006@FreeBSD.org> In-Reply-To: <50AB9C5B.6030006@FreeBSD.org> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 16:00:33 -0000 on 20/11/2012 17:06 Andriy Gapon said the following: > on 20/11/2012 16:59 Andrei Lavreniyuk said the following: >>>> Sorry to make you jump through so many hoops. >>>> Now that I see that the probed config is entirely correct, the problem appears to >>>> be quite obvious: vdev_alloc is not able to properly use spa_version in this >>>> context because spa_ubsync is not initialized yet. >>>> >>>> Let me think about how to fix this. >>> >>> I hope that the following simple patch should fix the problem: >>> http://people.freebsd.org/~avg/spa_import_rootpool.version.diff >> >> >> At mount system trap and reboot. >> > > Unexpected. Can you catch the backtrace of the panic? > If you have it on the screen. > > Ah, found another bogosity in the code: --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c @@ -3925,8 +4117,6 @@ spa_import_rootpool(const char *name) return (error); } - spa_history_log_version(spa, LOG_POOL_IMPORT); - spa_config_enter(spa, SCL_ALL, FTAG, RW_WRITER); vdev_free(rvd); spa_config_exit(spa, SCL_ALL, FTAG); This previously "worked" only because the pool version was zero and thus the action was a NOP anyway. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 16:28:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C456F4A7 for ; Tue, 20 Nov 2012 16:28:10 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB7E8FC0C for ; Tue, 20 Nov 2012 16:28:10 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1Taqg6-002bqx-TY>; Tue, 20 Nov 2012 17:28:02 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1Taqg6-002Sll-RI>; Tue, 20 Nov 2012 17:28:02 +0100 Message-ID: <50ABAF8E.3020101@zedat.fu-berlin.de> Date: Tue, 20 Nov 2012 17:27:58 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121115 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA6FCD05271D63D8A69A7B964" X-Originating-IP: 130.133.86.198 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 16:28:10 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA6FCD05271D63D8A69A7B964 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/20/12 11:43, Olivier Smedts wrote: > 2012/11/20 Paul Webster : >> I am aware this is a much discussed subject since the upgrade of PF, I= >> believe the final decision was that to many users are used to the old >> style pf and an upgrade to the new syntax would cause to much confusio= n. >=20 > But a change like this is expected in a new major branch, ie. > 10-CURRENT. Not so in -STABLE branches of course. I don't see the > problem here. >=20 > Cheers >=20 What would be the alternative? Being stuck with the old PF? As Olivier Smedts said, changes like that are expected in a complete new branch. If people need to stay compatible, they are about to use 9.X as long as they have migrated. The downside is more work. The bright side would be development/progression. oh --------------enigA6FCD05271D63D8A69A7B964 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJQq6+SAAoJEOgBcD7A/5N84IEIAIp3FPTktCz0gBXLgJFRFCOj tkb1HVacBh+VQ6XcDwGlWqPchlav2/nttnxfsHdlV8faFxMm5ZVyF5zxnPRpsflj fDzlwD/X8wawApq6ALV9rtEj0zo3Q/1n66QED6zpsAOSIwFYdKEpO4cvedlEeDGn 07u5dHXuVC4hvQZRx091dzNdW5EfBdI2KAm0+oCeFugu25itPU5SrfY9Cho+6J8F V53/if1wRJFA50cqFUPRaw1qRAm8Y9D/tb1tusPZziqOSt5xls7W0SOCoOJ8AqmB yXgNdwxwz0U2nhNM2lz780Rsis+n4CIP9moHc/Yas4oqaAmrkrBkSq6G69vXQ1s= =BVmQ -----END PGP SIGNATURE----- --------------enigA6FCD05271D63D8A69A7B964-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 16:34:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D54F914 for ; Tue, 20 Nov 2012 16:34:10 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-yh0-f54.google.com (mail-yh0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1F1E08FC0C for ; Tue, 20 Nov 2012 16:34:08 +0000 (UTC) Received: by mail-yh0-f54.google.com with SMTP id s35so1184730yhf.13 for ; Tue, 20 Nov 2012 08:34:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=n5P4YgAltsl8WkVNUaqP8+y0YiTF+vRrpQxvDk7QsyY=; b=aM1IrNfawygcUPWTPq6mvrQ1/LKcMxDelQ7UIxkKtddJWyypu3u5Plu/ikkuZ11JD1 Nfvl+Mf+iiUeFgOG9o6dl+dzn6FAe1dmGzcmzc5503fSRCxDcENf0XLtxxDBkV0P6jen H2IgU5LpJ3f8lt+hN1S5OOp4HdmvIEKVfP6xh8a3JS6+5ewmzaGphyZs321InUmDq8Pf eXZhjyHsBDz4mjmIsA9fwT8dy5zZuzUKNu1mSKb3ykX+XQgI0RO0d3sFbi9TyT0WVMyq Vp54MeZ8YDVDpkOJmAQB9hSxRWNMILUpZFRexsmKNbqwf3aTJkcFD/bcTcz6/J2mWnyU EfDg== Received: by 10.236.117.33 with SMTP id i21mr15829376yhh.81.1353429241965; Tue, 20 Nov 2012 08:34:01 -0800 (PST) Received: from [192.168.0.199] (99-202-128-123.pools.spcsdns.net. [99.202.128.123]) by mx.google.com with ESMTPS id q48sm3174016yhk.7.2012.11.20.08.34.00 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 08:34:01 -0800 (PST) Message-ID: <50ABB0C7.7070404@gmail.com> Date: Tue, 20 Nov 2012 10:33:11 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: <50ABAF8E.3020101@zedat.fu-berlin.de> In-Reply-To: <50ABAF8E.3020101@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 16:34:10 -0000 On 11/20/2012 10:27 AM, O. Hartmann wrote: > On 11/20/12 11:43, Olivier Smedts wrote: >> 2012/11/20 Paul Webster : >>> I am aware this is a much discussed subject since the upgrade of PF, I >>> believe the final decision was that to many users are used to the old >>> style pf and an upgrade to the new syntax would cause to much confusion. >> >> But a change like this is expected in a new major branch, ie. >> 10-CURRENT. Not so in -STABLE branches of course. I don't see the >> problem here. >> >> Cheers >> > > What would be the alternative? Being stuck with the old PF? As Olivier > Smedts said, changes like that are expected in a complete new branch. If > people need to stay compatible, they are about to use 9.X as long as > they have migrated. The downside is more work. The bright side would be > development/progression. > > oh > Why not release pf2 as a port? Then those who want the new pf can use it, and those that want the old one can use it. Or, another option is a knob USE_NEWPF during buildworld will build the new pf, otherwise it'd build the old, default one. This way you can still introduce the change, but default to the old one for those of us who are too crusty to change. :) -- Chuck Burns From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 16:52:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2ACEA143 for ; Tue, 20 Nov 2012 16:52:16 +0000 (UTC) (envelope-from graudeejs@yandex.ru) Received: from forward5h.mail.yandex.net (forward5h.mail.yandex.net [IPv6:2a02:6b8:0:f05::5]) by mx1.freebsd.org (Postfix) with ESMTP id 73F128FC16 for ; Tue, 20 Nov 2012 16:52:15 +0000 (UTC) Received: from web2h.yandex.ru (web2h.yandex.ru [84.201.186.31]) by forward5h.mail.yandex.net (Yandex) with ESMTP id C7881D00A53; Tue, 20 Nov 2012 20:52:01 +0400 (MSK) Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web2h.yandex.ru (Yandex) with ESMTP id 3EDAB4EF000D; Tue, 20 Nov 2012 20:52:01 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353430321; bh=WlKl1eWPUbZmyS7McSZNzAwQ8cD7OGVP95nn142aKpw=; h=From:To:In-Reply-To:References:Subject:Date; b=tVIPRyXekVirBLEOD+04IMwftIo3qlgqSLdffisDVQ34sKUWRywytwV/PnX7y2c2x 3+ktd/9CVoNGFNMu0Cm1FyQZKXun9GqzBJF2ouFsmpHgypaXTd5mFLx8AM2ZbFFB+I Kb7hSqYQIvPmXvgkKLffzBVGwTApcTeqDf5ksZck= Received: from mpe-11-155.mpe.lv (mpe-11-155.mpe.lv [83.241.11.155]) by web2h.yandex.ru with HTTP; Tue, 20 Nov 2012 20:52:01 +0400 From: Aldis Berjoza To: Chuck Burns , "freebsd-current@freebsd.org" In-Reply-To: <50ABB0C7.7070404@gmail.com> References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) MIME-Version: 1.0 Message-Id: <1023391353430321@web2h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 20 Nov 2012 18:52:01 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 16:52:16 -0000 20.11.2012, 18:34, "Chuck Burns" : > On 11/20/2012 10:27 AM, O. Hartmann wrote: > >> šOn 11/20/12 11:43, Olivier Smedts wrote: >>> š2012/11/20 Paul Webster : >>>> šI am aware this is a much discussed subject since the upgrade of PF, I >>>> šbelieve the final decision was that to many users are used to the old >>>> šstyle pf and an upgrade to the new syntax would cause to much confusion. >>> šBut a change like this is expected in a new major branch, ie. >>> š10-CURRENT. Not so in -STABLE branches of course. I don't see the >>> šproblem here. >>> >>> šCheers >> šWhat would be the alternative? Being stuck with the old PF? šAs Olivier >> šSmedts said, changes like that are expected in a complete new branch. If >> špeople need to stay compatible, they are about to use 9.X as long as >> šthey have migrated. The downside is more work. The bright side would be >> šdevelopment/progression. >> >> šoh > > Why not release pf2 as a port? šThen those who want the new pf can use > it, and those that want the old one can use it. > > Or, another option is a knob USE_NEWPF during buildworld will build the > new pf, otherwise it'd build the old, default one. > > This way you can still introduce the change, but default to the old one > for those of us who are too crusty to change. :) > FreeBSD already have 3x firewalls. Having 4th m I think, isn't desired. -- Aldis Berjoza FreeBSD addict From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 17:26:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3860DF87; Tue, 20 Nov 2012 17:26:47 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 9737D8FC14; Tue, 20 Nov 2012 17:26:46 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm6so958658wib.13 for ; Tue, 20 Nov 2012 09:26:45 -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=OjfImTmc9905w660p7X9QoVL22+g1MxHn2YWphDrLvU=; b=H6d6C3H6R98JXH1JvSPFu6GqeM7+b3cDf+rQQ9aSehHHl8NDRMCsVe3fsLmvG5Yxp6 dlckM86kKH5HMzQ1eo+ku0ku3omwguXaeS4oLN53mpq04U21F3uqD/piOH5BloFbBoPb KNY5Set+Yj34I6T9wbhgsUPFaabX7erCm7SxTGNkjLl7jfKh77NdK4uIk6dbcuwim0gh ot16JsY8ZP+G6b5Q3oioTwJmUgorsh3/8mni3cUq5DdyVr3C7JY2aMKU4UosdmrXkMhB i2U603h5sWBMuyKDsv3p49rspkL56EHBd1B5/x3kLS569zeeduBMNCinNoXt2Z+ltKzt DYpA== MIME-Version: 1.0 Received: by 10.180.99.1 with SMTP id em1mr12961422wib.17.1353432405763; Tue, 20 Nov 2012 09:26:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.21.211 with HTTP; Tue, 20 Nov 2012 09:26:45 -0800 (PST) In-Reply-To: References: Date: Tue, 20 Nov 2012 09:26:45 -0800 X-Google-Sender-Auth: 0b7WeUtwo4rVMZl2y5dM3uAPIiY Message-ID: Subject: Re: wifi + wpa_supplicant in 9.1-RC3 From: Adrian Chadd To: CeDeROM Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, freebsd-wireless@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 17:26:47 -0000 On 20 November 2012 05:52, CeDeROM wrote: > Hello :-) > > I have some problems with WiFi connectivity on my Dell Latitude E4310 > laptop with Intel card. Very often connection is broken, although > windows clients of the same network is working fine. I need to turn > radio off and on, sometimes this does not help, I need to kill > wpa_supplicant and start one by hand, so probably this is something > related with wpa_supplicant. Anyone observed similar issues? Please file a PR with the details. Which wireless card is it? Which driver/ > Btw if WiFi N supported? Yes, the iwn(4) NICs support 802.11n in 9.1. > Best regards :-) > Tomek > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 17:47:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2185CC2F for ; Tue, 20 Nov 2012 17:47:59 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id CFEA18FC16 for ; Tue, 20 Nov 2012 17:47:58 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so3097130iec.13 for ; Tue, 20 Nov 2012 09:47:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Yicyr2zaGBlzLXeO8n4ahHT2698+Xb7u4eXeURRyiH4=; b=l9wJomnT7WiepHH3oS3F7IjBeEn1oI8v7kx5wpimEBgl3YXWPyUnJQqfDAD5AJtSo3 ovrAX8FZs6My/UmxSC3OY0AueGBmqKudd92+35jvQZEZI1v4smLZCrnl9P5ooDj7f09V CILH+xl0sEWat3w3ZD2plDRBMdmArNQcjwVvsA1kmgC8oG0FzJ0VwSH/Ff03zujyslZg +70OOPPh6tk9upNhow+nel6A4HJzQb8K3m7Ys5ygyTPbsG98TCYHAUJG2vzSVmQW1d6e KoUmx1ocjUtiC26ZoU6tHPsE33L215aVFMVU8XuEk++1ySLH1sqd0nxXJoLSlxgV1Kzy Cakg== Received: by 10.50.190.162 with SMTP id gr2mr10960618igc.65.1353433677914; Tue, 20 Nov 2012 09:47:57 -0800 (PST) Received: from [192.168.0.199] ([173.157.127.48]) by mx.google.com with ESMTPS id px5sm10047002igc.0.2012.11.20.09.47.53 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 09:47:57 -0800 (PST) Message-ID: <50ABC214.9060800@gmail.com> Date: Tue, 20 Nov 2012 11:47:00 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Aldis Berjoza Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> <1023391353430321@web2h.yandex.ru> In-Reply-To: <1023391353430321@web2h.yandex.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 17:47:59 -0000 On 11/20/2012 10:52 AM, Aldis Berjoza wrote: > > > 20.11.2012, 18:34, "Chuck Burns" : >> On 11/20/2012 10:27 AM, O. Hartmann wrote: >> >>> On 11/20/12 11:43, Olivier Smedts wrote: >>>> 2012/11/20 Paul Webster : >>>>> I am aware this is a much discussed subject since the upgrade of PF, I >>>>> believe the final decision was that to many users are used to the old >>>>> style pf and an upgrade to the new syntax would cause to much confusion. >>>> But a change like this is expected in a new major branch, ie. >>>> 10-CURRENT. Not so in -STABLE branches of course. I don't see the >>>> problem here. >>>> >>>> Cheers >>> What would be the alternative? Being stuck with the old PF? As Olivier >>> Smedts said, changes like that are expected in a complete new branch. If >>> people need to stay compatible, they are about to use 9.X as long as >>> they have migrated. The downside is more work. The bright side would be >>> development/progression. >>> >>> oh >> >> Why not release pf2 as a port? Then those who want the new pf can use >> it, and those that want the old one can use it. >> >> Or, another option is a knob USE_NEWPF during buildworld will build the >> new pf, otherwise it'd build the old, default one. >> >> This way you can still introduce the change, but default to the old one >> for those of us who are too crusty to change. :) >> > > FreeBSD already have 3x firewalls. Having 4th m I think, isn't desired. > Nonsense. More options are always preferable to fewer options. -- Chuck Burns From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 17:51:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C37DD7F for ; Tue, 20 Nov 2012 17:51:35 +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 D140C8FC14 for ; Tue, 20 Nov 2012 17:51:34 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so3341576lbb.13 for ; Tue, 20 Nov 2012 09:51:33 -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=1XelQMSuOrzyhoh9NHfScziUubh1El8z5lDbJGuw3rM=; b=Qc48v6IEZHY5e9PJbZYtIp73DXnCO2IChJVjaaAVtuMlgdttrPkysOTR9we+xRdsRv s2Yms8WH6O9YOOVCOgHpsL85nQ+QPVB7OFXMbb2R2uzXIXhS8WXD0kihyn1Nxx9D4Fck 69bkj8PHVaLxJa6LBrBCIgCuvquYNWh2v4kt8= 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=1XelQMSuOrzyhoh9NHfScziUubh1El8z5lDbJGuw3rM=; b=N17qcKEJsM9Adkrd0qJA/CzFbcSA6U6GpS06AdGfGFRU1VjRsKEavITZbq7i9nvW9u l+UrtLK71tadxd8tMhNfeYRtmjD2kzdvwQI6rtQxsuQtvZVEitsCsDSMmCAi8j/qfaTw yyIIVTDViIG2C3tVLqwO4ek3+8infSRdMLyRA59T556yzmufIrnu3M+89n+AGnN56MK8 lm7hnAj064+Mg8uf3PFC9isIraHoh3C+I2apsYy+TYUwSbSCKEIx186fCyRj+6lZv73v ahCe8BqennI1nTxXD+MSXQIOw9zjHikaBryeASbDJevR72WgbZ3y655ZJGzf3kn5DDW7 DizQ== Received: by 10.152.102.234 with SMTP id fr10mr15477700lab.28.1353433893424; Tue, 20 Nov 2012 09:51:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Tue, 20 Nov 2012 09:51:03 -0800 (PST) In-Reply-To: <50ABC214.9060800@gmail.com> References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> <1023391353430321@web2h.yandex.ru> <50ABC214.9060800@gmail.com> From: Eitan Adler Date: Tue, 20 Nov 2012 12:51:03 -0500 Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) To: Chuck Burns Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnCvfbYxDxzybpZyUqQaX2bg54zexgYgOwgz2qbjCoeGJBT51jcSItY2XXVI5iUvPe2oykc Cc: "freebsd-current@freebsd.org" , Aldis Berjoza X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 17:51:35 -0000 On 20 November 2012 12:47, Chuck Burns wrote: > Nonsense. More options are always preferable to fewer options. Even when those options must be maintained? Documented? Bug fixed? -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 18:22:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F7B21000 for ; Tue, 20 Nov 2012 18:22:51 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ye0-f182.google.com (mail-ye0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id BCE628FC0C for ; Tue, 20 Nov 2012 18:22:50 +0000 (UTC) Received: by mail-ye0-f182.google.com with SMTP id q9so1229716yen.13 for ; Tue, 20 Nov 2012 10:22:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5kpOjQ0b6VoL7nCASE2s3Iot1ThnMH0EmwqLB4qu05M=; b=SrxwE1GQRCXXOeeAKTH1nprVN/L2WWx3zkn/dSzrXk88NfptK1SPD5dsuWjl+bbfUm YS6xSYVhX6GFVg3F9uVqIpaxFZf1Ee2hrtLZPoPo+87ZqmsTr4+tPKSyMh5hvmIjRkHN /AjyHQhaEgSEhiNpP0oarCJhtY6/dODUb0HaJ36KGuDCCXnrRNnOsQP7L+Hz3+PvTB6v YdOQBwZuKNldNt5lpbTyjQ6UQ0OZ5dpjPlFhTdgfjWCv1Q+egDv6ACmRJrdtaQln2ek+ sfYFfp3jMYaq1Vsq3L1qQDQQUJNjkRqfOT7H38rbvcVTqGS4QgVDPRgYzkoq15fo81uU UkRw== Received: by 10.101.59.2 with SMTP id m2mr4489833ank.33.1353435764520; Tue, 20 Nov 2012 10:22:44 -0800 (PST) Received: from [192.168.2.20] (173-17-218-61.client.mchsi.com. [173.17.218.61]) by mx.google.com with ESMTPS id z6sm13531373yhl.8.2012.11.20.10.22.41 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 10:22:43 -0800 (PST) Message-ID: <50ABCA6E.6030408@gmail.com> Date: Tue, 20 Nov 2012 12:22:38 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: Eitan Adler Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> <1023391353430321@web2h.yandex.ru> <50ABC214.9060800@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Aldis Berjoza X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 18:22:51 -0000 On 11/20/2012 11:51 AM, Eitan Adler wrote: > On 20 November 2012 12:47, Chuck Burns wrote: >> Nonsense. More options are always preferable to fewer options. > Even when those options must be maintained? Documented? Bug fixed? > > The ones who want the old pf can maintain it.. those who want the new one, can maintain *it*. I, for one, would prefer the new one eventually replace the old one, but there should definitely be a transition period, similar to how pkgng is going in. Chuck From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 18:48:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5AA5B78D for ; Tue, 20 Nov 2012 18:48:58 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0DBE18FC18 for ; Tue, 20 Nov 2012 18:48:57 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id 16so7994116obc.13 for ; Tue, 20 Nov 2012 10:48: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=mFqTSozzGPSaXxnU/oWkysy9rSYHkWNeFy+0vDRvJ28=; b=Mp7WAnyWLjcz3uT0N7OyQx8iciFkdwP++d/M0n2bQE3tOAgGSqlK9NBiwQvP7pfsM/ FaLi2rOUBwaJKjigegRBtCCCu/gs8sxvp2ILuHIC9aKj1fVmG7oyb4kXcStNFdIoFz6A 2W6GeK3YTUSunXiHGy3Yfci6svkoGlKU7xTc2zZHXXTfFcddVLb3VAAmSfVjacdVKX7r p/U4kvnj3oq7otU316ANFGgbXiD8QivM5lh/8rnrZVXnmgfnr5uvdsPr8XLvqQ2+4Sht Dip+T3qC9arHquJHUQsSiXweqkhzg3jDYH46zEaBfYkJsYyqK4wz4N9lUdZX+FNmMMm7 AQrA== MIME-Version: 1.0 Received: by 10.182.86.225 with SMTP id s1mr13972405obz.91.1353437336957; Tue, 20 Nov 2012 10:48:56 -0800 (PST) Received: by 10.76.80.104 with HTTP; Tue, 20 Nov 2012 10:48:56 -0800 (PST) In-Reply-To: <50ABCA6E.6030408@gmail.com> References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> <1023391353430321@web2h.yandex.ru> <50ABC214.9060800@gmail.com> <50ABCA6E.6030408@gmail.com> Date: Tue, 20 Nov 2012 12:48:56 -0600 Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) From: Adam Vande More To: Chuck Burns Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Eitan Adler , "freebsd-current@freebsd.org" , Aldis Berjoza X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 18:48:58 -0000 On Tue, Nov 20, 2012 at 12:22 PM, Chuck Burns wrote: > The ones who want the old pf can maintain it.. those who want the new one, > can maintain *it*. This is beach front property on Fantasy Island. There isn't even enough manpower to sufficiently support one currently. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 21:21:41 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6942FFE0 for ; Tue, 20 Nov 2012 21:21:41 +0000 (UTC) (envelope-from r.c.ladan@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 E88358FC08 for ; Tue, 20 Nov 2012 21:21:40 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c13so4620471eek.13 for ; Tue, 20 Nov 2012 13:21:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=B9KScJ3EzUxt4HRBhVgquSroixxyYYxVGHMMs3kbUnI=; b=xRd1kGaeHffQyUL/7YYdMVb3z3v5AQI5GSWqus1/EAWlf79+8x9wYq1CX5lTxU88x9 Ymsu07XYkxMynmmyEsGCWYX6Z3QO87NZXUWg797U/nuYlJaqLLcaR19xPr02Mvl0bmn6 Xj2Xwe54RMOFwu0uX40xE1EYC/i5oUDeBhCHQZGX8/DJOZ9tFN3HHuIoVV6m4o+6u8ib OxuvzxnUgE6hbEldYA6FMSsGtdFpMzE+5kirPCU19E/18CPk25LHLk83DbFcK61tCH+9 D56NMnVd4P5eQzTMS0KWbBXWXuGi08IXJ1KgoUXYhQwPBCzelmGuem3s7XWaXX8uCDuf +98A== Received: by 10.14.213.7 with SMTP id z7mr37153400eeo.39.1353446493705; Tue, 20 Nov 2012 13:21:33 -0800 (PST) Received: from [192.168.1.11] (ip18-43-209-87.adsl2.static.versatel.nl. [87.209.43.18]) by mx.google.com with ESMTPS id b44sm32864837eep.12.2012.11.20.13.21.31 (version=SSLv3 cipher=OTHER); Tue, 20 Nov 2012 13:21:32 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <50ABF45A.9000200@freebsd.org> Date: Tue, 20 Nov 2012 22:21:30 +0100 From: =?UTF-8?B?UmVuw6kgTGFkYW4=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121115 Thunderbird/16.0.2 MIME-Version: 1.0 To: Warren Block Subject: Re: sluggish X.org/Xfce behavior References: <50AB58FA.505@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 21:21:41 -0000 On 20-11-2012 15:34, Warren Block wrote: > On Tue, 20 Nov 2012, René Ladan wrote: > >> since last weekend (November 17th) I have been noticing a sluggish >> behavior of X.org/Xfce. Typical symptoms are: >> - Alt-Tab not reacting all of the time >> - pulldown/popup menus not allowing selections with mouse (typically in >> Terminal/pidgin), or moving the mouse (touchpad) results in an automatic >> click >> - typing something in a Terminal requires mouse (touchpad) movements for >> the text to show up >> - sometimes moving the mouse (touchpad) is required for the laptop to >> "wake up"; this is noticeable when Thunderbird downloads all messages >> from the period when the laptop was "frozen". > > This is one of the problems that having Option "AllowEmptyInput" "Off" > in xorg.conf causes. If you have that, substitute Option > "AutoAddDevices" "Off" in the same place. Commenting out "AllowEmptyInput" "Off" (and not having an AutoAddDevices entry) works for me. Must do better homework... René From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 22:00:13 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69450CDE; Tue, 20 Nov 2012 22:00:13 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1F15C8FC15; Tue, 20 Nov 2012 22:00:13 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id qAKM05Zj040017; Tue, 20 Nov 2012 15:00:05 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id qAKM05Tj040014; Tue, 20 Nov 2012 15:00:05 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 20 Nov 2012 15:00:05 -0700 (MST) From: Warren Block To: =?ISO-8859-15?Q?Ren=E9_Ladan?= Subject: Re: sluggish X.org/Xfce behavior In-Reply-To: <50ABF45A.9000200@freebsd.org> Message-ID: References: <50AB58FA.505@freebsd.org> <50ABF45A.9000200@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-1533897496-1353447847=:39585" Content-ID: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 20 Nov 2012 15:00:05 -0700 (MST) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 22:00:13 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-1533897496-1353447847=:39585 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; FORMAT=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Tue, 20 Nov 2012, René Ladan wrote: > On 20-11-2012 15:34, Warren Block wrote: >> On Tue, 20 Nov 2012, René Ladan wrote: >> >>> since last weekend (November 17th) I have been noticing a sluggish >>> behavior of X.org/Xfce. Typical symptoms are: >>> - Alt-Tab not reacting all of the time >>> - pulldown/popup menus not allowing selections with mouse (typically in >>> Terminal/pidgin), or moving the mouse (touchpad) results in an automatic >>> click >>> - typing something in a Terminal requires mouse (touchpad) movements for >>> the text to show up >>> - sometimes moving the mouse (touchpad) is required for the laptop to >>> "wake up"; this is noticeable when Thunderbird downloads all messages >>> from the period when the laptop was "frozen". >> >> This is one of the problems that having Option "AllowEmptyInput" "Off" >> in xorg.conf causes. If you have that, substitute Option >> "AutoAddDevices" "Off" in the same place. > Commenting out "AllowEmptyInput" "Off" (and not having an AutoAddDevices > entry) works for me. > > Must do better homework... http://www.wonkity.com/~wblock/docs/html/aei.html gives more detail. --3512871622-1533897496-1353447847=:39585-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 20 22:01:25 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98881E03; Tue, 20 Nov 2012 22:01:25 +0000 (UTC) (envelope-from kes-kes@yandex.ru) Received: from forward18.mail.yandex.net (forward18.mail.yandex.net [IPv6:2a02:6b8:0:1402::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0B60E8FC08; Tue, 20 Nov 2012 22:01:24 +0000 (UTC) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17]) by forward18.mail.yandex.net (Yandex) with ESMTP id 0C4381780621; Wed, 21 Nov 2012 02:01:23 +0400 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id C7FC919002D7; Wed, 21 Nov 2012 02:01:22 +0400 (MSK) Received: from unknown (unknown [77.93.52.20]) by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 1MkGSu0B-1Mkq2Grr; Wed, 21 Nov 2012 02:01:22 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1353448882; bh=bgI3ybQD+QAsDdFbFvnRWvLlmYtIVoxOF5trZjWdS4M=; h=Date:From:X-Mailer:Reply-To:Organization:X-Priority:Message-ID:To: CC:Subject:In-Reply-To:References:MIME-Version:Content-Type: Content-Transfer-Encoding; b=aYXPee95PeItIeBjmL1/IlrArzPAlANJRkUdEq1k/GlLBiCNH1dnf1xcwtW9sn9Su 5WgZTMEEOCr/D4i1zDIyTWRn/y/2FyLkWyD7PkA6kcPNDyyR1tSDXOj6JiGDYBwvqa BLkJE2lw1K5oMQ+YAxMUSJ2G6JItvSeJ8FX3hK90= Date: Wed, 21 Nov 2012 00:01:20 +0200 From: Eugen Konkov X-Mailer: The Bat! (v4.0.24) Professional Organization: ISP FreeLine X-Priority: 3 (Normal) Message-ID: <1692054066.20121121000120@yandex.ru> To: Ian FREISLICH Subject: Re[2]: netisr panic? In-Reply-To: References: <20121117213754.GI38060@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Cc: Gleb Smirnoff , freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Eugen Konkov List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2012 22:01:25 -0000 Çäðàâñòâóéòå, Ian. Âû ïèñàëè 19 íîÿáðÿ 2012 ã., 7:32:08: IF> Gleb Smirnoff wrote: >> On Sat, Nov 17, 2012 at 05:07:54PM +0200, Ian FREISLICH wrote: >> I> I have this consistently with: >> I> >> I> FreeBSD firewall2.jnb1.gp-online.net 10.0-CURRENT FreeBSD 10.0-CURRENT #30 IF> r243156: Fri Nov 16 20:12:33 SAST 2012 IF> ianf@firewall2.jnb1.gp-online.net:/ IF> usr/obj/usr/src/sys/FIREWALL amd64 >> >> Pretty sure this is a new version of wrong byte order panic, which >> no longer can happen in HEAD. >> >> Can you please try this patch? Do you mean 10 only. Are that available in FreeBSD 9? -- Ñ óâàæåíèåì, Eugen mailto:kes-kes@yandex.ru From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 01:57:54 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E912AF79; Wed, 21 Nov 2012 01:57:54 +0000 (UTC) (envelope-from kevin.wilcox@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 AF7158FC08; Wed, 21 Nov 2012 01:57:54 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so4920511pbc.13 for ; Tue, 20 Nov 2012 17:57:54 -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=Z7nDZcmSBhiFsE+6yP0nWRZe/z1Y9AovgGrYQC8yZF0=; b=Sint1BemyOBi1Kt6RMRrA411JnkBlTVaIALW9CAtF+5FgIUZeQBDuu5YPwBPCk+1y5 3B4LSoBaQ39ejxfzAiZ2UvRwXxgPXKBlU1QyN8BJRtWczM6/ra5rtoVsjqOEPT2Ps2s5 Go3s0qCXtfhl/FAM8NO+6rV8N5ruanAY6nzMt0Onp8q75vJIpy+wzOhn+DyBwGiUYDps WorIRFqSFLXepHjjKKRhWRsj1/Sfv9N0M5HJ9xg4zrgMEkoLTfd83zjBcU4dInAnUBqD u8Ly0OW7O67BR9MKIYmNadHgcii2UgCUk/iiN5nChcyVByBGbfj23U6atcV7BAxYKwx9 AHcA== MIME-Version: 1.0 Received: by 10.68.235.71 with SMTP id uk7mr55114750pbc.10.1353463074127; Tue, 20 Nov 2012 17:57:54 -0800 (PST) Received: by 10.68.8.2 with HTTP; Tue, 20 Nov 2012 17:57:54 -0800 (PST) Received: by 10.68.8.2 with HTTP; Tue, 20 Nov 2012 17:57:54 -0800 (PST) In-Reply-To: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> Date: Tue, 20 Nov 2012 20:57:54 -0500 Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. From: Kevin Wilcox To: Mark Martinec X-Mailman-Approved-At: Wed, 21 Nov 2012 03:22:26 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org, freebsd-pf@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 01:57:55 -0000 On Nov 20, 2012 9:44 AM, "Mark Martinec" wrote: > > Paul Webster wrote: > > I am aware this is a much discussed subject since the upgrade of PF, > > I believe the final decision was that too many users are used to the old > > style pf and an upgrade to the new syntax would cause too much confusion. > > I don't buy that. Think of a confusion in a year of two when > OpenBSD PF rules and the PF documentation won't match the > legacy syntax in FreeBSD's PF. Their documentation already doesn't match the legacy syntax, you have to look for older pf documentation to match that in use by FreeBSD. This has been the case since at least OpenBSD 4.7: http://www.openbsd.org/faq/upgrade47.html To get documentation for FreeBSD pf, you generally need to look for OpenBSD documentation for 4.2 or 4.3 as there were minute changes in the mid-4.x range. kmw From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 07:45:22 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12209139; Wed, 21 Nov 2012 07:45:22 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 840348FC0C; Wed, 21 Nov 2012 07:45:21 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id qAL7jJKe075376; Wed, 21 Nov 2012 11:45:19 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id qAL7jJPn075375; Wed, 21 Nov 2012 11:45:19 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Nov 2012 11:45:19 +0400 From: Gleb Smirnoff To: Olivier Smedts Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) Message-ID: <20121121074519.GP67660@FreeBSD.org> References: <20121120121333.GB88593@in-addr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Gary Palmer , Paul Webster , freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 07:45:22 -0000 Olivier, On Tue, Nov 20, 2012 at 01:24:49PM +0100, Olivier Smedts wrote: O> > The other question that I haven't seen answered (or maybe even asked), but O> > is relevant: what do we gain by going to a later version of pf? I.e. as an O> > administrator, what benefit do I get by having to expend effort converting O> > my filter rules? O> > O> > Gary O> O> At some time we'll surely *have* to upgrade our pf, because the legacy O> version won't be supported upstream. I say that a major release is the O> most appropriated place for such a change. This isn't answer to Gary's question, sorry. He asked for what exact features or performance gains are we talking about when we say "the new pf". Regarding your answer. First, OpenBSD never supports anything older than the latest release. Thus, pf in FreeBSD was never supported by OpenBSD and never would be. Second, if you carefully analyze current open problem reports in GNATS assigned to freebsd-pf, you would find, that vast majority of them are specific to FreeBSD port and are not shared with OpenBSD. Taking this into account I will state, that pf needs to be supported by FreeBSD developers, end. -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 07:47:59 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3849B29C for ; Wed, 21 Nov 2012 07:47:59 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id AB5C78FC08 for ; Wed, 21 Nov 2012 07:47:58 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id qAL7lvkv075402; Wed, 21 Nov 2012 11:47:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id qAL7lvVY075401; Wed, 21 Nov 2012 11:47:57 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Nov 2012 11:47:57 +0400 From: Gleb Smirnoff To: Chuck Burns Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. (Copied from freebsd-pf) Message-ID: <20121121074757.GQ67660@FreeBSD.org> References: <50ABAF8E.3020101@zedat.fu-berlin.de> <50ABB0C7.7070404@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <50ABB0C7.7070404@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 07:47:59 -0000 Chuck, On Tue, Nov 20, 2012 at 10:33:11AM -0600, Chuck Burns wrote: C> Why not release pf2 as a port? Then those who want the new pf can use C> it, and those that want the old one can use it. C> C> Or, another option is a knob USE_NEWPF during buildworld will build the C> new pf, otherwise it'd build the old, default one. C> C> This way you can still introduce the change, but default to the old one C> for those of us who are too crusty to change. :) Why not? The netpfil/ subdir in the source tree has enough space for zillions of packet filters. Just do the dirty coding job and post patches. If you see the point in doing this, then you are the person to do. -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 07:51:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCDC45C5; Wed, 21 Nov 2012 07:51:25 +0000 (UTC) (envelope-from andy.lavr@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C5FE68FC13; Wed, 21 Nov 2012 07:51:24 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so6475567lah.13 for ; Tue, 20 Nov 2012 23:51:23 -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=3vYxNY8Pb5yRjKh6kMV/AJKlm9f9orkguveXpTuKEr4=; b=YycLE6H53Xr/n/Fr8fbXWd9okBjmVW2WStfzPrEHQBpOJAHzhDQzfTEF50JSsgs4zX oTcqUxImimQ5Q1lBsCXvRw/6ldP23Pm/yTd9kUL9ezxhRzt6i8SIfLjRSrF9X2fxzkZC ygzN6vTdyEpNnWsEh43Ag3w0M97fSmeqPF5aOS0aj2wC4m0R7mQ1icBsGCFxt7TG7n2K yf83rFH9gFszdKsDGc1eI9ZEjOA4HkYXAdeokWAeiUZ3PHcBpDrxflq2bMVkGBIbDNSS a5P3OnPFXxKIWmenPJgKgN5W4GZ4yuatP2yYaGwkcYa/2CKMapeA1/2TpTafHaGK/XFM kDBw== MIME-Version: 1.0 Received: by 10.112.88.100 with SMTP id bf4mr621937lbb.49.1353484283468; Tue, 20 Nov 2012 23:51:23 -0800 (PST) Received: by 10.114.5.5 with HTTP; Tue, 20 Nov 2012 23:51:23 -0800 (PST) In-Reply-To: <50ABA91D.9090905@FreeBSD.org> References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> <50AB90E9.5070102@FreeBSD.org> <50AB9C5B.6030006@FreeBSD.org> <50ABA91D.9090905@FreeBSD.org> Date: Wed, 21 Nov 2012 09:51:23 +0200 Message-ID: Subject: Re: problem booting to multi-vdev root pool From: Andrei Lavreniyuk To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 07:51:25 -0000 2012/11/20 Andriy Gapon : > on 20/11/2012 17:06 Andriy Gapon said the following: >> on 20/11/2012 16:59 Andrei Lavreniyuk said the following: >>>>> Sorry to make you jump through so many hoops. >>>>> Now that I see that the probed config is entirely correct, the problem appears to >>>>> be quite obvious: vdev_alloc is not able to properly use spa_version in this >>>>> context because spa_ubsync is not initialized yet. >>>>> >>>>> Let me think about how to fix this. >>>> >>>> I hope that the following simple patch should fix the problem: >>>> http://people.freebsd.org/~avg/spa_import_rootpool.version.diff >>> >>> >>> At mount system trap and reboot. >>> >> >> Unexpected. Can you catch the backtrace of the panic? >> If you have it on the screen. >> >> > > Ah, found another bogosity in the code: > --- a/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c > +++ b/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c > @@ -3925,8 +4117,6 @@ spa_import_rootpool(const char *name) > return (error); > } > > - spa_history_log_version(spa, LOG_POOL_IMPORT); > - > spa_config_enter(spa, SCL_ALL, FTAG, RW_WRITER); > vdev_free(rvd); > spa_config_exit(spa, SCL_ALL, FTAG); > > > This previously "worked" only because the pool version was zero and thus the > action was a NOP anyway. > Problem solved. Raidz pool mount without zpool.cache. # zpool status -v pool: zsolar state: ONLINE scan: resilvered 2,56M in 0h0m with 0 errors on Tue Nov 20 10:26:35 2012 config: NAME STATE READ WRITE CKSUM zsolar ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 errors: No known data errors # uname -a FreeBSD opensolaris.technica-03.local 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r243278M: Wed Nov 21 09:28:51 EET 2012 root@opensolaris.technica-03.local:/usr/obj/usr/src/sys/SMP64R amd64 Thanks! From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 07:56:44 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12E67A97; Wed, 21 Nov 2012 07:56:44 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 7CE318FC17; Wed, 21 Nov 2012 07:56:43 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id qAL7ugOw075471; Wed, 21 Nov 2012 11:56:42 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id qAL7ugG8075470; Wed, 21 Nov 2012 11:56:42 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Nov 2012 11:56:42 +0400 From: Gleb Smirnoff To: Mark Martinec Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. Message-ID: <20121121075642.GR67660@FreeBSD.org> References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org, freebsd-pf@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 07:56:44 -0000 Mark, On Tue, Nov 20, 2012 at 03:43:17PM +0100, Mark Martinec wrote: M> For one thing, I'm desperately awaiting NAT64 support (the 'af-to' M> translation rule in newer pf (5.1?), committed on 2011-10). Backport this exact feature to FreeBSD and send patch. M> Other: packet normalization (scrub) has been reworked and simplified, M> and is now a rulset option. Considering that scrub is currently broken M> (9.1, see list of PF bugs in FreeBSD), along with several other M> bugs that need fixing, it seems the (scarce) manpower would better M> be spent in moving on, than keeping the already leaky (buggy) pf M> afloat. Yes, scrub improvements can be cherry picked and added to FreeBSD, too. But if you think that bulk import of new version would close all current bugs without opening new problems, then you are mistaking. Last bulk import introduced much more bugs than it closed. And this statement isn't a accusation towards the person who did the import. This is just a generic rule. If you take 100k lines of code that were developed for another operating system kernel and without thourough reviewing it just make it compile and link with another kernel, then you are about to miss many rough edges that will show up later, when the code would be utilized. Thus, cherry-picking is preferred over bulk imports. -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 12:10:09 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2FDB0422 for ; Wed, 21 Nov 2012 12:10:09 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 837408FC0C for ; Wed, 21 Nov 2012 12:10:08 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id k19so5969558qcs.13 for ; Wed, 21 Nov 2012 04:10:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=WrwjPlah3fDkuwnHTJE6nHpztkc6p97GhPBC2AM8jrc=; b=cqn/h7wo0r5dNY5YwSbjTJaEj71uwe+zn+PFa+SB42KCxq1m8bkg35Fg1BIumYmOpA njkAYURHn5em6CX/XxqXptUx2GzSUJoVLr6zgtDxQRpqU0QtHC3PTvV1KWS55cMZPYF0 ec8fRsrVr706aqKkXgtG3vTqURavc/K7gw96ed/g+JoX7Kzdo7GLDbL+2/rVJO7B1NHB p39Ux60Wxf8QURXS7hrKh7Cvoo6c78n/jnBjfv2FUH2K283amjunKvmpjKdYoNO2zUco uQNF+g4p+Gz90fbZtQyesbPQYqvANWFd4+1e7Bp8vBADIk/qgqy4dWdudB4g0+a3U1jX uhtg== Received: by 10.49.1.194 with SMTP id 2mr20512954qeo.56.1353499807655; Wed, 21 Nov 2012 04:10:07 -0800 (PST) Received: from [192.168.11.110] (ool-4a58bea2.dyn.optonline.net. [74.88.190.162]) by mx.google.com with ESMTPS id fl1sm130774qab.14.2012.11.21.04.10.06 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Nov 2012 04:10:06 -0800 (PST) References: <50A372EC.5080002@freebsd.org> In-Reply-To: <50A372EC.5080002@freebsd.org> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <2068A84F-0B1F-43B3-AAE8-5A8442C0B327@longcount.org> X-Mailer: iPhone Mail (9B206) From: Mark Saad Subject: Re: Looking for bge(4) , bce(4) and igb(4) cards Date: Wed, 21 Nov 2012 07:10:04 -0500 To: "andre@freebsd.org" X-Gm-Message-State: ALoCoQnlKuERL5yAT6JyoSxnLezgcUtXvtWaZePp9Nv7wO7VFtvn5Urouebm/3H5SJn4L7Rlao74 X-Mailman-Approved-At: Wed, 21 Nov 2012 12:24:13 +0000 Cc: "freebsd-net@freebsd.org" , "freebsd-current@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 12:10:09 -0000 Andre I'll try to do it today or next monday when I get back from vacation . The= y are all hp branded nic's . I ordered them with in the last few years to us= e in place of bce nic's on the main boards of hp servers .=20 --- On Nov 14, 2012, at 5:31 AM, Andre Oppermann wrote: > Hello >=20 > 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). >=20 > To properly test this I need the proper hardware as PCIe network > cards: >=20 > bge(4) Broadcom BCM57xx/BCM590x > bce(4) Broadcom NetXtreme II (BCM5706/5708/5709/5716) > igb(4) Intel PRO/1000 i82575, i82576, i82580, i210, i350 >=20 > 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. >=20 >=20 > 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: >=20 > em(4) Intel i82571 to i82573 > lem(4) Intel i82540 to i82546 > age(4) Atheros L1 GigE > ??? anything else 1GigE with PCIe >=20 >=20 > 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): >=20 > 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 >=20 > Many thanks for your support! >=20 > --=20 > Andre > _______________________________________________ > 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-current@FreeBSD.ORG Wed Nov 21 14:44:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97369691; Wed, 21 Nov 2012 14:44:15 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id 0FED18FC08; Wed, 21 Nov 2012 14:44:14 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id t11so1773074qaa.13 for ; Wed, 21 Nov 2012 06:44:14 -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=q+o60ZtSaH95tgRQk23do0PJXrm0kzNYByxWxnnNgbk=; b=nS/NMF89212RJa8mQizcRMsL55s5nC/MCfARVZhsy20l4unElblLQ1EAHVnL5cvsgN Kdt7N+BTkpHg9pia1WMu8q/l1rd2m3HQmk4KhVV/9fKMUZ8mFMOWj4xrryGSbmlwu73H 6lh8ZAWraDPprTFIyhF/VPNPYqisRMe+WEgG9Sr3PL4/KkrjnsB9OiTUag7NDpbO0NXL 7Hye/aJnbpuYcr85I2nVEcoLYxHohPL5+eTKhMNpEMup3qAPdweej8Pj6x2ny211N30k i5ndLSgFGdrR6nINkV2S72uXOa15ENq3Uwrrb55DxS1ceLoyYk0FQilok7NHGqtAp9yv g87A== MIME-Version: 1.0 Received: by 10.49.103.162 with SMTP id fx2mr21577278qeb.1.1353509053864; Wed, 21 Nov 2012 06:44:13 -0800 (PST) Sender: ermal.luci@gmail.com Received: by 10.49.121.163 with HTTP; Wed, 21 Nov 2012 06:44:13 -0800 (PST) In-Reply-To: <20121121075642.GR67660@FreeBSD.org> References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> <20121121075642.GR67660@FreeBSD.org> Date: Wed, 21 Nov 2012 15:44:13 +0100 X-Google-Sender-Auth: rXb2ohSklsfR_eCCzKTYP-EF5dw Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. From: =?ISO-8859-1?Q?Ermal_Lu=E7i?= To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Mark Martinec , freebsd-current@freebsd.org, "freebsd-pf@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 14:44:15 -0000 On Wed, Nov 21, 2012 at 8:56 AM, Gleb Smirnoff wrote: > Mark, > > On Tue, Nov 20, 2012 at 03:43:17PM +0100, Mark Martinec wrote: > M> For one thing, I'm desperately awaiting NAT64 support (the 'af-to' > M> translation rule in newer pf (5.1?), committed on 2011-10). > > Backport this exact feature to FreeBSD and send patch. > > M> Other: packet normalization (scrub) has been reworked and simplified, > M> and is now a rulset option. Considering that scrub is currently broken > M> (9.1, see list of PF bugs in FreeBSD), along with several other > M> bugs that need fixing, it seems the (scarce) manpower would better > M> be spent in moving on, than keeping the already leaky (buggy) pf > M> afloat. > > Yes, scrub improvements can be cherry picked and added to FreeBSD, too. > > The issues is you cannot without modifying rule config. > But if you think that bulk import of new version would close all current > bugs without opening new problems, then you are mistaking. Last bulk > import introduced much more bugs than it closed. And this statement isn't > a accusation towards the person who did the import. This is just a generic > rule. If you take 100k lines of code that were developed for another > operating system kernel and without thourough reviewing it just make it > compile and link with another kernel, then you are about to miss many > rough edges that will show up later, when the code would be utilized. > > Thus, cherry-picking is preferred over bulk imports. > > Well it depends on the amount of work. Cherry-picking would be when tehre is reasonable similarities. Also another argument to do this would be simplicity on locking as well as i told you when you started the changes. Though i am open to work together on this to merge the new syntax thorugh a whole bulk merge rather than cherry-pick. You already have 'broken' some functionality as if-bound in FreeBSD 10.x so why not break syntax and see to introduce if real value behind a converter as well. > -- > Totus tuus, Glebius. > _______________________________________________ > freebsd-pf@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-pf > To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org" > -- Ermal From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 14:52:48 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E91219BE; Wed, 21 Nov 2012 14:52:48 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 573368FC12; Wed, 21 Nov 2012 14:52:48 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id qALEqek5077479; Wed, 21 Nov 2012 18:52:40 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id qALEqeW4077478; Wed, 21 Nov 2012 18:52:40 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 21 Nov 2012 18:52:40 +0400 From: Gleb Smirnoff To: Ermal Lu?i Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. Message-ID: <20121121145240.GE67660@glebius.int.ru> References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> <20121121075642.GR67660@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mark Martinec , freebsd-current@FreeBSD.org, "freebsd-pf@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 14:52:49 -0000 On Wed, Nov 21, 2012 at 03:44:13PM +0100, Ermal Lu?i wrote: E> Cherry-picking would be when tehre is reasonable similarities. E> Also another argument to do this would be simplicity on locking as well as E> i told you when you started the changes. You were wrong. OpenBSD doesn't move towards SMP model. Locking more recent pf is not simplier, but the opposite. E> Though i am open to work together on this to merge the new syntax thorugh a E> whole bulk merge rather than cherry-pick. How many bugs have you closed after the previous bulk import? Why should we expect anything good from new import if the previous one was a PITA? And still I don't see any answer on the question: what exact features or perfomance improvements are we going to obtain from "the new pf"? E> You already have 'broken' some functionality as if-bound in FreeBSD 10.x so Is there any PR filed on that? I didn't even receive a mail about that. -- Totus tuus, Glebius. From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 15:20:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7558631D; Wed, 21 Nov 2012 15:20:20 +0000 (UTC) (envelope-from ermal.luci@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id E3CC98FC14; Wed, 21 Nov 2012 15:20:19 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id g24so1949001qab.13 for ; Wed, 21 Nov 2012 07:20:19 -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=KfIA0KaOZjheJVvdnfwLBWJcydmA8jDGovZHkuaAh8s=; b=vp4x510RZnJOpe69SidWuWCSOCM0vwlUXK7zcZ91nA6VG1KKlx8P2vLcYvTZudIuRH Ls9g3FwSX5t35t65rFie2NVr3CA/kVOtTpresl7FLxo2D5VJTvffJMd8Hi1o6+jr1Nl2 efXX2qdtVqm/T/wVflDlitUR0ykTNRldAPAJF8sqizlg15F+ZVEbqCcH2KzzjrOhWDL3 ZCf4H/bo1ZPGVUNYF+MPWNR67dJaZWqGcbQa9+FkKQHOxVYj2dk08By3mp8ycZjQFH+r E4GG/1Xv7iAo2AD9U/CaBnGDfTaQAWWyRBp3Fl4YL2OUfnTNS4NxpqM7o9O7NzeCFA+u djIw== MIME-Version: 1.0 Received: by 10.49.82.98 with SMTP id h2mr21375979qey.14.1353511219194; Wed, 21 Nov 2012 07:20:19 -0800 (PST) Sender: ermal.luci@gmail.com Received: by 10.49.121.163 with HTTP; Wed, 21 Nov 2012 07:20:19 -0800 (PST) In-Reply-To: <20121121145240.GE67660@glebius.int.ru> References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> <20121121075642.GR67660@FreeBSD.org> <20121121145240.GE67660@glebius.int.ru> Date: Wed, 21 Nov 2012 16:20:19 +0100 X-Google-Sender-Auth: ncNQudYbymus4Hb1yAGgVIG745U Message-ID: Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. From: =?ISO-8859-1?Q?Ermal_Lu=E7i?= To: Gleb Smirnoff Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Mark Martinec , freebsd-current@freebsd.org, "freebsd-pf@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 15:20:20 -0000 On Wed, Nov 21, 2012 at 3:52 PM, Gleb Smirnoff wrote: > On Wed, Nov 21, 2012 at 03:44:13PM +0100, Ermal Lu?i wrote: > E> Cherry-picking would be when tehre is reasonable similarities. > E> Also another argument to do this would be simplicity on locking as well > as > E> i told you when you started the changes. > > You were wrong. OpenBSD doesn't move towards SMP model. Locking more > recent pf is not simplier, but the opposite. > > I am sorry but you are asking arguments i already have given you. You didn;t listen once and i do not expect this time as well. > E> Though i am open to work together on this to merge the new syntax > thorugh a > E> whole bulk merge rather than cherry-pick. > > How many bugs have you closed after the previous bulk import? Why should > we expect anything good from new import if the previous one was a PITA? > > Well you have used it for your work so it was not so PITA. Most of the ones you closed had message 'This is to old to be true'; 'I have re-written PF and this should be fixed'. > And still I don't see any answer on the question: what exact features or > perfomance improvements are we going to obtain from "the new pf"? > > See above. > E> You already have 'broken' some functionality as if-bound in FreeBSD > 10.x so > > Is there any PR filed on that? I didn't even receive a mail about that. > > I really do not think you do the right approach or the right communication on this. Sorry for replying to you ;). > -- > Totus tuus, Glebius. > -- Ermal From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 15:45:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9E9E91E; Wed, 21 Nov 2012 15:45:55 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.freebsd.org (Postfix) with ESMTP id 1714E8FC19; Wed, 21 Nov 2012 15:45:55 +0000 (UTC) Received: from a91-153-116-96.elisa-laajakaista.fi (a91-153-116-96.elisa-laajakaista.fi [91.153.116.96]) by gw02.mail.saunalahti.fi (Postfix) with SMTP id 36381139511; Wed, 21 Nov 2012 17:45:43 +0200 (EET) Date: Wed, 21 Nov 2012 17:45:43 +0200 From: Jaakko Heinonen To: Mateusz Guzik , Ryan Stone , FreeBSD Current , bapt@freebsd.org Subject: Re: pw keeps setting /etc/group to 0600 Message-ID: <20121121154542.GA1849@a91-153-116-96.elisa-laajakaista.fi> References: <20121119222843.GB22292@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121119222843.GB22292@dft-labs.eu> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 15:45:55 -0000 On 2012-11-19, Mateusz Guzik wrote: > First, pw should not fail if other instance is running, it should wait > instead (think of parallel batch scripts adding some users/groups). > > Second, current code has a race: > lockfd = open(group_file, O_RDONLY, 0); > if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) == -1) > err(1, "%s", group_file); > if (flock(lockfd, LOCK_EX|LOCK_NB) == -1) { > [..] > gr_copy(pfd, tfd, gr, old_gr); /* copy from groupfile to tempfile */ > [..] > rename(tempfile,groupfile); Hmm, could using the O_EXLOCK flag for open() instead of flock() help here? > Now let's consider threads A and B: > > A: open() > A: lock(); > A: gr_copy > B: open() > > Now B has file descriptor to /etc/group that is about to be removed. > > A: rename() > A: unlock() > B: lock() > > Now B has a lock on unlinked file. > > B: gr_copy() > B: rename() > > ... and stores new content losing modifications done by A -- Jaakko From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 16:27:29 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4056F7BE; Wed, 21 Nov 2012 16:27:29 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB6C8FC0C; Wed, 21 Nov 2012 16:27:28 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hm6so1734822wib.13 for ; Wed, 21 Nov 2012 08:27:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=5PlpL4+yBcok7QUnKVJyqULcgrfzoHdiDiy/3Psd3w8=; b=cv6H7t6E+YsJ1YLaJT4TMQFl8jQRwh7+kJ5LbTmKOTZQjFfc/cEYQ6+Ogfmxf37nat zGaT+hAbnVz4vjUumGN+eJU47l8jTg7wOR92Vvsxq4yR8wiyqAlGBCRn2681dJzxnLyH 94JAfj5w5vH/tvRr9Fa1jNuntqGmTGyfMYa9xCgSG9yUk/jOz5+QWEKiuh+ARLRpZBJn y5ZsWqUimhbt+Dc+p+OkJWKfv/NjLzL11rlyxrLq1qbfF+KiZ/ZnyeXYkOeKbwn6aJvU //J3CfmxJffDNtCn+nn1QE/olHgX//WOr3GXrsFPWdtcTuIbKWE8r0xexoC+g42BRES8 KOYA== Received: by 10.216.227.132 with SMTP id d4mr3107879weq.33.1353515247245; Wed, 21 Nov 2012 08:27:27 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id bn7sm4480wib.8.2012.11.21.08.27.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Nov 2012 08:27:26 -0800 (PST) Date: Wed, 21 Nov 2012 17:27:18 +0100 From: Mateusz Guzik To: Jaakko Heinonen Subject: Re: pw keeps setting /etc/group to 0600 Message-ID: <20121121162718.GA10768@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Jaakko Heinonen , Ryan Stone , FreeBSD Current , bapt@freebsd.org References: <20121119222843.GB22292@dft-labs.eu> <20121121154542.GA1849@a91-153-116-96.elisa-laajakaista.fi> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20121121154542.GA1849@a91-153-116-96.elisa-laajakaista.fi> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: bapt@freebsd.org, FreeBSD Current , Ryan Stone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 16:27:29 -0000 On Wed, Nov 21, 2012 at 05:45:43PM +0200, Jaakko Heinonen wrote: > On 2012-11-19, Mateusz Guzik wrote: > > First, pw should not fail if other instance is running, it should wait > > instead (think of parallel batch scripts adding some users/groups). > > > > Second, current code has a race: > > lockfd = open(group_file, O_RDONLY, 0); > > if (lockfd < 0 || fcntl(lockfd, F_SETFD, 1) == -1) > > err(1, "%s", group_file); > > if (flock(lockfd, LOCK_EX|LOCK_NB) == -1) { > > [..] > > gr_copy(pfd, tfd, gr, old_gr); /* copy from groupfile to tempfile */ > > [..] > > rename(tempfile,groupfile); > > Hmm, could using the O_EXLOCK flag for open() instead of flock() help here? > Yes, this would fix the race. But the problem of pw exiting due to other process holding the lock remains. And I think that fixing it will require holding a lock over whole time pw is running so that we have stable snapshot of user base at least in regard of local files. One could create one lock, say /etc/.pw.lock, that would be used to synchronize any changes to /etc/master.passwd, /etc/group and whatnot. And then there is this API issue (but maybe this is just me nitpicking). -- Mateusz Guzik From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 16:49:24 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 28348CD1; Wed, 21 Nov 2012 16:49:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 3EA7F8FC0C; Wed, 21 Nov 2012 16:49:22 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA13299; Wed, 21 Nov 2012 18:49:20 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <50AD0610.1060101@FreeBSD.org> Date: Wed, 21 Nov 2012 18:49:20 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121029 Thunderbird/16.0.2 MIME-Version: 1.0 To: Andrei Lavreniyuk Subject: Re: problem booting to multi-vdev root pool References: <50AB5202.4070906@FreeBSD.org> <50AB71A7.7050101@FreeBSD.org> <50AB80C6.1090507@FreeBSD.org> <50AB8C1F.2040108@FreeBSD.org> <50AB90E9.5070102@FreeBSD.org> <50AB9C5B.6030006@FreeBSD.org> <50ABA91D.9090905@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 16:49:24 -0000 on 21/11/2012 09:51 Andrei Lavreniyuk said the following: > Problem solved. Raidz pool mount without zpool.cache. > > > # zpool status -v > pool: zsolar > state: ONLINE > scan: resilvered 2,56M in 0h0m with 0 errors on Tue Nov 20 10:26:35 2012 > config: > > NAME STATE READ WRITE CKSUM > zsolar ONLINE 0 0 0 > raidz2-0 ONLINE 0 0 0 > gpt/disk0 ONLINE 0 0 0 > gpt/disk2 ONLINE 0 0 0 > gpt/disk3 ONLINE 0 0 0 > > errors: No known data errors > > # uname -a > FreeBSD opensolaris.technica-03.local 10.0-CURRENT FreeBSD > 10.0-CURRENT #6 r243278M: Wed Nov 21 09:28:51 EET 2012 > root@opensolaris.technica-03.local:/usr/obj/usr/src/sys/SMP64R amd64 > > > Thanks! Thank you for testing! -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 16:53:41 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C8A099 for ; Wed, 21 Nov 2012 16:53:41 +0000 (UTC) (envelope-from zkolic@sbb.rs) Received: from smtp2.sbb.rs (smtp2.sbb.rs [89.216.2.34]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB6B8FC08 for ; Wed, 21 Nov 2012 16:53:40 +0000 (UTC) Received: from mycenae (cable-178-148-104-142.dynamic.sbb.rs [178.148.104.142]) by smtp2.sbb.rs (8.14.0/8.14.0) with ESMTP id qALGV9QX009864 for ; Wed, 21 Nov 2012 17:31:14 +0100 Received: by mycenae (Postfix, from userid 1001) id C76535C23; Wed, 21 Nov 2012 17:31:33 +0100 (CET) Date: Wed, 21 Nov 2012 17:31:33 +0100 From: Zoran Kolic To: freebsd-current@freebsd.org Subject: amdtemp for amd 8120 Message-ID: <20121121163133.GA1187@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-Mailman-Approved-At: Wed, 21 Nov 2012 17:32:55 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 16:53:41 -0000 Having new amd 8120 box with asus m5a97 mobo, I wait to install 9.1 on it. Both RC1 ad RC2 live memsticks images failed to show temperatures. Some posts reported of using amdtemp source from head successfully. What is the lattest amdtemp source on head? I assume I could go to /usr/src/dyd/dev/amdtemp/ and replace amdtemp.c with head code. Then to recompile the kernel as I do usually, including "device amdtemp" in it. Alternatelly, I might use that code and compile it, rena- ming final result to ie tempmeasure.ko and putting it in /boot/modules directory. With "kldload tempmeasure" later. What would be prefered method? When release comes out, I will try to use amdtemp from it before doing further com- pile. If fails, head source might help. Best regards Zoran From owner-freebsd-current@FreeBSD.ORG Wed Nov 21 20:37:07 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C290A3C1; Wed, 21 Nov 2012 20:37:07 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0C68FC08; Wed, 21 Nov 2012 20:37:07 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id EEE9B5602F; Wed, 21 Nov 2012 14:37:06 -0600 (CST) Date: Wed, 21 Nov 2012 14:37:06 -0600 From: Mark Linimon To: Dimitry Andric Subject: Re: -Current built with clang as default + ports Message-ID: <20121121203706.GB22398@lonesome.com> References: <50A36B95.4060901@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50A36B95.4060901@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: AN , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 20:37:07 -0000 This is all good advice. Note, however: On Wed, Nov 14, 2012 at 10:59:49AM +0100, Dimitry Andric wrote: > Of special interest are the results from the build cluster, where you > can get a quick overview of which ports don't build, and how many other > ports depend on them. Unfortunately those web pages are offline right now and will not be back online in the next few days. mcl From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 03:31:34 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F4DE254 for ; Thu, 22 Nov 2012 03:31:34 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id CBD4A8FC0C for ; Thu, 22 Nov 2012 03:31:33 +0000 (UTC) Received: from meatwad.mouf.net (cpe-024-162-230-236.nc.res.rr.com [24.162.230.236]) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id qAM3VOTB047177 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 21 Nov 2012 22:31:29 -0500 (EST) (envelope-from swills@FreeBSD.org) Message-ID: <50AD9C8C.9000703@FreeBSD.org> Date: Wed, 21 Nov 2012 22:31:24 -0500 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121118 Thunderbird/16.0.2 MIME-Version: 1.0 To: AN Subject: Re: -Current built with clang as default + ports References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [199.48.129.64]); Wed, 21 Nov 2012 22:31:29 -0500 (EST) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 03:31:34 -0000 On 11/13/12 18:51, AN wrote: > Can anyone comment on current built with clang as default compiler and > ports? Are there any major problems, programs that don't run? > Specifically, I am interested in how Gnome and Xorg (Gnome and Xorg > built with default system gcc) work on world built with clang. I can't comment on Gnome, but I run current on my desktop and use KDE4. I had to patch a few ports to build. Those patches have been sent in as PRs. Overall, the switch to ports built with clang was amazingly uneventful. So far, I haven't noticed anything that built but didn't work properly. > I believe the work around for ports that don't build with clang is to > put USE_GCC=4.7+ in the port makefile, is this correct? Any comments > would be appreciated, thanks in advance. A good bit of fixing for clang has already been done. I was able to fix pretty much everything I encountered that didn't build with clang, so didn't have to set USE_GCC anywhere, but it's there as a "last resort." Of course, those are just my experiences, YMMV. Steve From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 03:46:44 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A9F696B for ; Thu, 22 Nov 2012 03:46:44 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id 583238FC08 for ; Thu, 22 Nov 2012 03:46:44 +0000 (UTC) Received: from meatwad.mouf.net (cpe-024-162-230-236.nc.res.rr.com [24.162.230.236]) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id qAM3kYtF047391 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Wed, 21 Nov 2012 22:46:40 -0500 (EST) (envelope-from swills@FreeBSD.org) Message-ID: <50ADA01A.7080805@FreeBSD.org> Date: Wed, 21 Nov 2012 22:46:34 -0500 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121118 Thunderbird/16.0.2 MIME-Version: 1.0 To: current@FreeBSD.org Subject: current sluggish under load in the last few weeks X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [199.48.129.64]); Wed, 21 Nov 2012 22:46:40 -0500 (EST) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 03:46:44 -0000 Hi All, Has something changed in the scheduler recently? I don't have anything concrete, just anecdotal evidence, but my current desktop feels a little less responsive under heavy CPU load than it did a few weeks ago. Usually my high CPU processes (builds) are nice'd, but even with that, thing still get kinda sluggish, for example the mouse pointer will take it's time responding. Didn't do that a few weeks back. Wondering if it's just me? Thanks, Steve From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 05:33:32 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 651D52BB; Thu, 22 Nov 2012 05:33:32 +0000 (UTC) (envelope-from bf1783@googlemail.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 161338FC08; Thu, 22 Nov 2012 05:33:31 +0000 (UTC) Received: by mail-ia0-f182.google.com with SMTP id x2so7038073iad.13 for ; Wed, 21 Nov 2012 21:33:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=7jLgy0H4cOYqMU3l9Ka6VqheKiZ9FhL0Bjprpae5YcQ=; b=TZ0Yk1958vSLbRHrhZUZ07NWianeWMc09lmMSXbNzSZpv4wXNKtVpmO1ynVBeNeZLE jiwPzU5i6C+cAUT8ARKsNphtt18/ZAGYp8zSTEtmNE0ormsIST8OEiVtmrLUkRr4Ql4T r10fk8SRH6ZEuru6QgGnpIgBAmSoTALftebMc6jklLrLIURfqAfMjRul46e8l3DPSJoG bFgh9feCzuEBFq23oZrsRmWX8QZY0oiFudyvUXs5amTT63b8w+/3j6o6s9PlzQrpH8Nd pG8oEE91anxWKfL9+ysuvdCjgdIdMYIW5aauWxaUrCPEkCXSgKUYFDhvehd/NYUB3mbA kYLQ== MIME-Version: 1.0 Received: by 10.42.119.133 with SMTP id b5mr19602567icr.56.1353562411554; Wed, 21 Nov 2012 21:33:31 -0800 (PST) Received: by 10.50.88.137 with HTTP; Wed, 21 Nov 2012 21:33:31 -0800 (PST) Date: Thu, 22 Nov 2012 00:33:31 -0500 Message-ID: Subject: Re: current sluggish under load in the last few weeks From: "b. f." To: swills@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: bf1783@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 05:33:32 -0000 > Has something changed in the scheduler recently? Yes: r242736, r242852+r243069. Your description of your problem is a bit vague, but you might start by looking at the effect of the above commits. b. From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 09:28:30 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1E534BDF; Thu, 22 Nov 2012 09:28:30 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 312018FC0C; Thu, 22 Nov 2012 09:28:28 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA20849; Thu, 22 Nov 2012 11:28:27 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TbT58-000Gji-T2; Thu, 22 Nov 2012 11:28:26 +0200 Message-ID: <50ADF03A.3090005@FreeBSD.org> Date: Thu, 22 Nov 2012 11:28:26 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: Steve Wills Subject: Re: current sluggish under load in the last few weeks References: <50ADA01A.7080805@FreeBSD.org> In-Reply-To: <50ADA01A.7080805@FreeBSD.org> X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 09:28:30 -0000 on 22/11/2012 05:46 Steve Wills said the following: > Hi All, > > Has something changed in the scheduler recently? I don't have anything > concrete, I'd recommend getting something concrete first. Like doing some profiling. Or obtaining some ktr(4) traces that could be used with schedgraph. > just anecdotal evidence, but my current desktop feels a little > less responsive under heavy CPU load than it did a few weeks ago. > Usually my high CPU processes (builds) are nice'd, but even with that, > thing still get kinda sluggish, for example the mouse pointer will take > it's time responding. Didn't do that a few weeks back. Wondering if it's > just me? -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 09:39:21 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 445D3D7E for ; Thu, 22 Nov 2012 09:39:21 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 263D78FC12 for ; Thu, 22 Nov 2012 09:39:21 +0000 (UTC) Received: from xyf.my.dom (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qAM9dKA4083986 for ; Thu, 22 Nov 2012 09:39:20 GMT (envelope-from davidxu@freebsd.org) Message-ID: <50ADF2D4.2010805@freebsd.org> Date: Thu, 22 Nov 2012 17:39:32 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:14.0) Gecko/20120822 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Is this a typo in if_tap.c? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 09:39:21 -0000 When I was trying to create a second tap device, kernel crashed. Is this patch correct ? Index: sys/net/if_tap.c =================================================================== --- sys/net/if_tap.c (revision 243397) +++ sys/net/if_tap.c (working copy) @@ -186,7 +186,7 @@ /* Find any existing device, or allocate new unit number. */ i = clone_create(&tapclones, &tap_cdevsw, &unit, &dev, 0); if (i) { - dev = make_dev(&tap_cdevsw, 0, UID_ROOT, GID_WHEEL, 0600, + dev = make_dev(&tap_cdevsw, unit, UID_ROOT, GID_WHEEL, 0600, "%s%d", tapname, unit); } From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 14:10:42 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF262EB4; Thu, 22 Nov 2012 14:10:42 +0000 (UTC) (envelope-from kevlo@FreeBSD.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 7955F8FC15; Thu, 22 Nov 2012 14:10:41 +0000 (UTC) Received: from srg.kevlo.org (git.kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.5/8.14.5) with ESMTP id qAMEAOc5087344; Thu, 22 Nov 2012 22:10:24 +0800 (CST) (envelope-from kevlo@FreeBSD.org) Message-ID: <50AE325B.1060409@FreeBSD.org> Date: Thu, 22 Nov 2012 22:10:35 +0800 From: Kevin Lo User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20121009 Thunderbird/15.0.1 MIME-Version: 1.0 To: David Xu Subject: Re: Is this a typo in if_tap.c? References: <50ADF2D4.2010805@freebsd.org> In-Reply-To: <50ADF2D4.2010805@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 14:10:42 -0000 On 2012/11/22 17:39, David Xu wrote: > When I was trying to create a second tap device, kernel crashed. > Is this patch correct ? > > > Index: sys/net/if_tap.c > =================================================================== > --- sys/net/if_tap.c (revision 243397) > +++ sys/net/if_tap.c (working copy) > @@ -186,7 +186,7 @@ > /* Find any existing device, or allocate new unit number. */ > i = clone_create(&tapclones, &tap_cdevsw, &unit, &dev, 0); > if (i) { > - dev = make_dev(&tap_cdevsw, 0, UID_ROOT, GID_WHEEL, 0600, > + dev = make_dev(&tap_cdevsw, unit, UID_ROOT, GID_WHEEL, 0600, > "%s%d", tapname, unit); > } > The patch looks right to me. Kevin From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 15:12:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6475332F; Thu, 22 Nov 2012 15:12:42 +0000 (UTC) (envelope-from edschouten@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 17AE18FC13; Thu, 22 Nov 2012 15:12:41 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id 16so10509254obc.13 for ; Thu, 22 Nov 2012 07:12:41 -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=CDizNjdgjBjkNZapz5821y3LyDj/Te7yBDPGtSayxG0=; b=tHHMtNuEkqN+GR/ze3sYLBebnMU0yYm1nbHheZOb6ieQdoitwJ7FV163z6ayyMFF9M Qxd15BH5ABAk+wvs64sE4l1d/yxoKtYYCBQA09ttTTwEIH0Z6vTpCGApXpshn5QtzBd0 jZalSTen9Heo8HOL2XJM19jzh0dcCznPqsaGLYjv10j3UkQVcKTRK4SNy0VvDLmyvi5T flBc6kD3o6jYNnVKPQM7v+/ed8uaLHpuVkkh1peeL1G932LuGAtW5CRVJ3NtcVcDre6l 4Da0Ovkaf8MSTCzItz2VMpqhQduUl//FEJmvcSqTb0yudW7N8dHnk9z5APmF+JnAZadp MNOg== MIME-Version: 1.0 Received: by 10.182.95.205 with SMTP id dm13mr674675obb.9.1353597161387; Thu, 22 Nov 2012 07:12:41 -0800 (PST) Sender: edschouten@gmail.com Received: by 10.76.151.39 with HTTP; Thu, 22 Nov 2012 07:12:41 -0800 (PST) In-Reply-To: <50ADF2D4.2010805@freebsd.org> References: <50ADF2D4.2010805@freebsd.org> Date: Thu, 22 Nov 2012 16:12:41 +0100 X-Google-Sender-Auth: h-M4DXa9wSv3679o2URyocD-lX4 Message-ID: Subject: Re: Is this a typo in if_tap.c? From: Ed Schouten To: David Xu Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 15:12:42 -0000 2012/11/22 David Xu : > When I was trying to create a second tap device, kernel crashed. > Is this patch correct ? Yes, it looks okay. Eventually we should get rid of the entire unit numbering thing in if_tap and if_tun. If we would, we could remove a lot of dead code from sys/sys/conf.h and sys/kern/kern_conf.c. -- Ed Schouten From owner-freebsd-current@FreeBSD.ORG Thu Nov 22 16:13:08 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 206243CF for ; Thu, 22 Nov 2012 16:13:08 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id DDBE28FC08 for ; Thu, 22 Nov 2012 16:13:07 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA v2" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id 6A54D60E8 for ; Thu, 22 Nov 2012 11:12:59 -0500 (EST) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=WqUfevZSIaa37UCjWPeyMotcsX8OeDtS+/pLqjE3abbRhuvfMzf2rG6D6wQo8vUSc mlVV3ulPJptUPj/JX1r5Glg4/5fzpmT/Qx3c7cVhosadh9A+Or1TJWWn0jrfbp0 Message-ID: <50AE4F09.6000309@protected-networks.net> Date: Thu, 22 Nov 2012 11:12:57 -0500 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: FreeBSD Current Subject: troubles with one specific if_re X-Enigmail-Version: 1.4.6 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2012 16:13:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have an express-card interface which randomly decides to stop talking: Nov 21 09:22:29 toshi kernel: re0: port 0x2000-0x20ff mem 0xf0700000-0xf0700fff,0xf0200000-0xf0203fff irq 1 7 at device 0.0 on pci3 Nov 21 09:22:29 toshi kernel: re0: Using 1 MSI-X message Nov 21 09:22:29 toshi kernel: re0: ASPM disabled Nov 21 09:22:29 toshi kernel: re0: Chip rev. 0x28000000 Nov 21 09:22:29 toshi kernel: re0: MAC rev. 0x00000000 Nov 21 09:22:29 toshi kernel: miibus0: on re0 Nov 21 09:22:29 toshi kernel: rgephy0: PHY 1 on miibus0 Nov 21 09:22:29 toshi kernel: rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow Nov 21 09:22:29 toshi kernel: re0: Ethernet address: 00:0a:cd:1d:30:a2 After an indeterminate period, it logs .. Nov 21 09:23:33 toshi kernel: re0: PHY read failed Nov 21 09:23:39 toshi last message repeated 24 times Any thoughts as to how to troubleshoot/fix? imb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlCuTwkACgkQQv9rrgRC1JLJYQCgi4ljnsRn3XCz1gZVSDW4D+el JUIAoJdKDNNrlelAjw+5pZttC6Q+kyQr =T4CB -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 03:17:56 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A196D91 for ; Fri, 23 Nov 2012 03:17:56 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas-2-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:b9c::2]) by mx1.freebsd.org (Postfix) with ESMTP id BEB068FC12 for ; Fri, 23 Nov 2012 03:17:54 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5) with ESMTP id qAN3HsCE059655 for ; Thu, 22 Nov 2012 22:17:54 -0500 (EST) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5/Submit) id qAN3HsBZ059654 for current@freebsd.org; Thu, 22 Nov 2012 22:17:54 -0500 (EST) (envelope-from mwlucas) Date: Thu, 22 Nov 2012 22:17:54 -0500 From: "Michael W. Lucas" To: current@freebsd.org Subject: after upgrade, can't restart apache via cron Message-ID: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Thu, 22 Nov 2012 22:17:54 -0500 (EST) X-Mailman-Approved-At: Fri, 23 Nov 2012 03:28:39 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 03:17:56 -0000 FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC amd64 I can manually restart apache22 with the following /etc/rc.conf entries: apache22_enable="YES" apache22_fib=0 I have a cron entry that restarts apache regularly, to compensate for some mysql daftness. 13 * * * * /usr/local/etc/rc.d/apache22 restart When this job runs, I get the following email: Performing sanity check on apache22 configuration: Syntax OK Stopping apache22. Waiting for PIDS: 59501. Performing sanity check on apache22 configuration: Syntax OK Starting apache22. eval: setfib: not found /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 If I run /usr/local/etc/rc.d/apache22 restart from the command line, I can restart httpd without trouble. Any thoughts? ==ml -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlucas@michaelwlucas.com, Twitter @mwlauthor From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 03:33:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 717A910A for ; Fri, 23 Nov 2012 03:33:01 +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 404878FC08 for ; Fri, 23 Nov 2012 03:33:00 +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 qAN3X0l2019911; Thu, 22 Nov 2012 19:33:00 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id qAN3X0BY019910; Thu, 22 Nov 2012 19:33:00 -0800 (PST) (envelope-from david) Date: Thu, 22 Nov 2012 19:33:00 -0800 From: David Wolfskill To: "Michael W. Lucas" Subject: Re: after upgrade, can't restart apache via cron Message-ID: <20121123033300.GH1758@albert.catwhisker.org> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0Ed1hDcWxc3B7cn" Content-Disposition: inline In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 03:33:01 -0000 --y0Ed1hDcWxc3B7cn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 22, 2012 at 10:17:54PM -0500, Michael W. Lucas wrote: > ...=20 > 13 * * * * /usr/local/etc/rc.d/apache22 restart >=20 > When this job runs, I get the following email: >=20 > Performing sanity check on apache22 configuration: > ... > eval: setfib: not found > /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 >=20 > If I run /usr/local/etc/rc.d/apache22 restart from the command line, I > can restart httpd without trouble. >=20 > Any thoughts? PATH used by cron -- per crontab(5): Several environment variables are set up automatically by the cron(8) daemon. SHELL is set to /bin/sh, PATH is set to /usr/bin:/bin, and LOGNAME and HOME are set from the /etc/passwd line of the crontab's owner. HOME, PATH and SHELL may be overridden by settings in the crontab; LOGNAME may not. and setfib is: g1-227(9.1-P)[1] which setfib /usr/sbin/setfib g1-227(9.1-P)[2]=20 Looks as if overriding PATH (in crontab) is least disruptive change that will work. Peace, david --=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. --y0Ed1hDcWxc3B7cn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCu7mwACgkQmprOCmdXAD2gGwCfTneFyCAIGLDjkNZV9O5O1HxP ZTMAnRk4yF+toIYuiGXV9mtKMR2YhrPO =lLwj -----END PGP SIGNATURE----- --y0Ed1hDcWxc3B7cn-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 03:33:35 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E0A2216 for ; Fri, 23 Nov 2012 03:33:35 +0000 (UTC) (envelope-from amvandemore@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 EE26F8FC16 for ; Fri, 23 Nov 2012 03:33:34 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n9so11024648oag.13 for ; Thu, 22 Nov 2012 19:33:34 -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=D4hNzyMXyyuKe8aCrRIkTjrTD+5zUDu5rkf4POhk6VE=; b=ZIRwILvr7N9jircYToXbZs2YMzTWWniD4N0S7B71A4m3wPtCXAwjU82jdn2ANP4T3F vM7g+BQ2ezE1sljTyczWg/E/x60IGN1Q3AgVg9D7BHFiGsM5yGCAsgY7glIsgZW0p+E+ SjE/mBTiWRxhl6+ni8oKKnIahGX4qoxWUpfYxPd67S6EqTBjHG+3m9wOaxY2W2epj212 m70GSMIDWxL2qhVj+geVgJIvntyQ8JivA1Wd4mG8cr3fVJhi2jypaHPA7Kx7vuxonASF MtKs7MdgD5FeAZbiCWYshQsDkwvN4L6RwUbAj+OYjd8bUed/As8ofzt8ednQStqLQBa3 GimA== MIME-Version: 1.0 Received: by 10.60.31.39 with SMTP id x7mr1944015oeh.45.1353641614109; Thu, 22 Nov 2012 19:33:34 -0800 (PST) Received: by 10.76.80.104 with HTTP; Thu, 22 Nov 2012 19:33:34 -0800 (PST) In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> Date: Thu, 22 Nov 2012 21:33:34 -0600 Message-ID: Subject: Re: after upgrade, can't restart apache via cron From: Adam Vande More To: "Michael W. Lucas" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 03:33:35 -0000 On Thu, Nov 22, 2012 at 9:17 PM, Michael W. Lucas wrote: > > > FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD > 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 > mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > I can manually restart apache22 with the following /etc/rc.conf entries: > > apache22_enable="YES" > apache22_fib=0 > > I have a cron entry that restarts apache regularly, to compensate for > some mysql daftness. > > 13 * * * * /usr/local/etc/rc.d/apache22 restart > > When this job runs, I get the following email: > > Performing sanity check on apache22 configuration: > Syntax OK > Stopping apache22. > Waiting for PIDS: 59501. > Performing sanity check on apache22 configuration: > Syntax OK > Starting apache22. > eval: setfib: not found > /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 > > If I run /usr/local/etc/rc.d/apache22 restart from the command line, I > can restart httpd without trouble. > > Any thoughts? > I would guess you need /usr/sbin/ in cron's path. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 03:34:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78B7A495 for ; Fri, 23 Nov 2012 03:34:35 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id 49DB48FC13 for ; Fri, 23 Nov 2012 03:34:34 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id C77F41136D for ; Thu, 22 Nov 2012 22:34:27 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zn5v1QuP52ra for ; Thu, 22 Nov 2012 22:34:27 -0500 (EST) Received: from EGR authenticated sender Message-ID: <50AEEEC9.7080602@egr.msu.edu> Date: Thu, 22 Nov 2012 22:34:33 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: after upgrade, can't restart apache via cron References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 03:34:35 -0000 On 11/22/2012 10:17 PM, Michael W. Lucas wrote: > > FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC amd64 > > I can manually restart apache22 with the following /etc/rc.conf entries: > > apache22_enable="YES" > apache22_fib=0 > > I have a cron entry that restarts apache regularly, to compensate for > some mysql daftness. > > 13 * * * * /usr/local/etc/rc.d/apache22 restart > > When this job runs, I get the following email: > > Performing sanity check on apache22 configuration: > Syntax OK > Stopping apache22. > Waiting for PIDS: 59501. > Performing sanity check on apache22 configuration: > Syntax OK > Starting apache22. > eval: setfib: not found > /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 > > If I run /usr/local/etc/rc.d/apache22 restart from the command line, I > can restart httpd without trouble. > > Any thoughts? > > ==ml > Make sure the path to setfib is in PATH in the crontab? PATH=/blah/blah/blah:/usr/sbin * * * * * blah From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 04:06:45 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E5B26BD for ; Fri, 23 Nov 2012 04:06:45 +0000 (UTC) (envelope-from fjwcash@gmail.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 B65E88FC08 for ; Fri, 23 Nov 2012 04:06:44 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so5750512lbb.13 for ; Thu, 22 Nov 2012 20:06:43 -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=W0+C4+6ngQO3y4uf/UsIq07u/nIOx6gaPLLxgwFLcbU=; b=gU3uZH7K5fqz08cirNNl5QYal+oe6rvMeE7GPt2fbbkuSujLVWrBylgAmlMd0Hpy7/ 2RjFBPRTNdsGq3tLPbwSLrQVk1ZAZy8RIpmYRdn1m4ZOpgMEzBVfe5cKU+R64BCUCi4W VWDkMxuNEJj3SNOtwHbYaM+mxKJa0+kW8aLjd9ABcLyQJLWOThbwOq/uIWb3yd7SewLU 7vLtCf39hH4UgzMbSGH4tgCNpYezOkhz8/Fk3rMAD+SBfGl/3qv3LB3HRdAeesDr53zE YC2NzX8eULd7xL9oeMHXcjaYZ58RXDAbhGN4SJdw3Vi6yrlNTGayXdqXRG+FW2BgIhq6 c4ow== MIME-Version: 1.0 Received: by 10.152.124.83 with SMTP id mg19mr2285022lab.6.1353643603337; Thu, 22 Nov 2012 20:06:43 -0800 (PST) Received: by 10.114.24.66 with HTTP; Thu, 22 Nov 2012 20:06:43 -0800 (PST) Received: by 10.114.24.66 with HTTP; Thu, 22 Nov 2012 20:06:43 -0800 (PST) In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> Date: Thu, 22 Nov 2012 20:06:43 -0800 Message-ID: Subject: Re: after upgrade, can't restart apache via cron From: Freddie Cash To: "Michael W. Lucas" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 04:06:45 -0000 The interrupted unix faq, a wonderful thing. :) Covers this exactly. :) http://www.wonkity.com/~wblock/docs/html/interrupted.html On Nov 22, 2012 7:28 PM, "Michael W. Lucas" wrote: > > > FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD > 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 > mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > I can manually restart apache22 with the following /etc/rc.conf entries: > > apache22_enable="YES" > apache22_fib=0 > > I have a cron entry that restarts apache regularly, to compensate for > some mysql daftness. > > 13 * * * * /usr/local/etc/rc.d/apache22 restart > > When this job runs, I get the following email: > > Performing sanity check on apache22 configuration: > Syntax OK > Stopping apache22. > Waiting for PIDS: 59501. > Performing sanity check on apache22 configuration: > Syntax OK > Starting apache22. > eval: setfib: not found > /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 > > If I run /usr/local/etc/rc.d/apache22 restart from the command line, I > can restart httpd without trouble. > > Any thoughts? > > ==ml > > -- > Michael W. Lucas > http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ > Latest book: SSH Mastery > http://www.michaelwlucas.com/nonfiction/ssh-mastery > mwlucas@michaelwlucas.com, Twitter @mwlauthor > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 11:13:27 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB023762 for ; Fri, 23 Nov 2012 11:13:27 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.43]) by mx1.freebsd.org (Postfix) with SMTP id 195998FC13 for ; Fri, 23 Nov 2012 11:13:26 +0000 (UTC) Received: (qmail invoked by alias); 23 Nov 2012 08:34:29 -0000 Received: from 194.219.141.155.dsl.dyn.forthnet.gr (EHLO [192.168.1.77]) [194.219.141.155] by mail.gmx.com (mp-eu003) with SMTP; 23 Nov 2012 09:34:29 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX18hxUsAuBshyXeiCvc8Jc6T5GLpbhsqgz5oHkvmzv vdyo8MfqIYFfdP Message-ID: <50AF3509.7070402@gmx.com> Date: Fri, 23 Nov 2012 10:34:17 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: strange buildworld failure Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 11:13:28 -0000 Hi, I am trying to buildworld but it fails here: > ===> usr.bin/ypwhich (all) > cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - > Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno- > unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -c /usr/src/usr.bin/ypwhich/ypwhich.c > gzip -cn /usr/src/usr.bin/ypwhich/ypwhich.1 > ypwhich.1.gz > cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - > Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno- > unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -o ypwhich ypwhich.o > 1 error > *** [everything] Error code 2 > 1 error > *** [buildworld] Error code 2 > 1 error My make.conf has these: WITHOUT_X11=1 MALLOC_PRODUCTION=1 NO_CLEAN=1 Also, my src.conf had WITHOUT_CLANG but I deleted it and then I also deleted /usr/obj when it failed for the first time. But that didn't work. I am building with -j3. Thanks for any ideas/pointers, Nikos From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 11:34:22 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2AFC310E for ; Fri, 23 Nov 2012 11:34:22 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id D65FA8FC15 for ; Fri, 23 Nov 2012 11:34:21 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id g24so1624020qab.13 for ; Fri, 23 Nov 2012 03:34:15 -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=uJeJB1O9HLTHipmJZwSygNRH5ijoh45h2uwZxjDb7nw=; b=qww6GtS0zM1m4Ln8vB576lNGRvDZW77NdvBHIX1S82k32e+KTHOFOC5FaTL0rfqhoW azNQU1rerwrc6NuH7fbojC/UMsZLR4wIZWApSiOW6FD17Jz5cWo/zvmhl2RXr6+CTi4T m8QFj0EdBAytVvmxz2rwYUqqBZC2/cWdzOfVzhVd4iXpIc73t1TrtFes7BagcBkz/crB bYPX88XhUyiMeysO5F2pVLnehiZ16LUc6JwdXB76mprA/WHCHDikpyl38M1eCfBgcm/g Ri2P6R40SbbUZBjjzlIphEziZG/yHiGGm5WKoAG+Z0gnY8VZEnLEbfhliQ8m5ftcXwxe gvcA== MIME-Version: 1.0 Received: by 10.49.1.47 with SMTP id 15mr1189986qej.46.1353670455762; Fri, 23 Nov 2012 03:34:15 -0800 (PST) Received: by 10.229.78.96 with HTTP; Fri, 23 Nov 2012 03:34:15 -0800 (PST) In-Reply-To: <50AF3509.7070402@gmx.com> References: <50AF3509.7070402@gmx.com> Date: Fri, 23 Nov 2012 14:34:15 +0300 Message-ID: Subject: Re: strange buildworld failure From: Sergey Kandaurov To: Nikos Vassiliadis Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 11:34:22 -0000 On 23 November 2012 12:34, Nikos Vassiliadis wrote: > Hi, > > I am trying to buildworld but it fails here: >> >> ===> usr.bin/ypwhich (all) >> cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector >> -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - >> Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int >> -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno- >> unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -c >> /usr/src/usr.bin/ypwhich/ypwhich.c >> gzip -cn /usr/src/usr.bin/ypwhich/ypwhich.1 > ypwhich.1.gz >> cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector >> -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - >> Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int >> -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno- >> unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -o ypwhich >> ypwhich.o >> 1 error >> *** [everything] Error code 2 >> 1 error >> *** [buildworld] Error code 2 >> 1 error > > > My make.conf has these: > WITHOUT_X11=1 > MALLOC_PRODUCTION=1 > NO_CLEAN=1 > > Also, my src.conf had WITHOUT_CLANG but I deleted it and then I > also deleted /usr/obj when it failed for the first time. But that > didn't work. I am building with -j3. Does it always fail there at usr.bin/ypwhich? It's likely that -j3 is the culprit of why you do not see the actual build error because it might be lost off the screen. Try to restart without -jN. -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 12:04:50 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4753EFC for ; Fri, 23 Nov 2012 12:04:50 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 72FB38FC15 for ; Fri, 23 Nov 2012 12:04:49 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so3275939wey.13 for ; Fri, 23 Nov 2012 04:04:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=S84neTjc52BbwPDyvOXgUw70Rar9vewWGIiVCYw6ZxI=; b=NZ7Lww16/Jv2b32BCThK7v17F4X/W0hz6AaMBTbAU+TnhqYEynK6SoYlj8J9K+YMBy 86M3CHuuKpvoc4cJ+TeC7QVK1u/UF+v/ElrCqRdI5HNK/s9K3zNBUuNTjSDl8sSvCuH9 exJ6/oUQBsvOAsQAqjmmQQ2pbovH05TQD9rstZj9mAcD7KlyIWoBN7hRrB5x7HaX3iQB W+eIR0ission+wFuLmT/iKd96P+olFQAYBebOEvKb01SCiGmg2dffYtNu1ccWZnOuXuk uYNjK+K9FYWOlQBQeAje5YVg89xbceLhOevNWXshkvbXtOUf/xmnh7CUJgVINCFQAadD RlBw== Received: by 10.216.211.66 with SMTP id v44mr1477930weo.91.1353672289162; Fri, 23 Nov 2012 04:04:49 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPS id gk9sm8292598wib.4.2012.11.23.04.04.46 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Nov 2012 04:04:47 -0800 (PST) Date: Fri, 23 Nov 2012 13:04:40 +0100 From: Mateusz Guzik To: "Michael W. Lucas" Subject: Re: after upgrade, can't restart apache via cron Message-ID: <20121123120440.GA15116@dft-labs.eu> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 12:04:51 -0000 On Thu, Nov 22, 2012 at 10:17:54PM -0500, Michael W. Lucas wrote: > > > FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC amd64 > > I can manually restart apache22 with the following /etc/rc.conf entries: > > apache22_enable="YES" > apache22_fib=0 > > I have a cron entry that restarts apache regularly, to compensate for > some mysql daftness. > > 13 * * * * /usr/local/etc/rc.d/apache22 restart > > When this job runs, I get the following email: > [..] > eval: setfib: not found [..] > > If I run /usr/local/etc/rc.d/apache22 restart from the command line, I > can restart httpd without trouble. > As others pointers out already it is a PATH issue, but I don't think that restoring /usr/sbin in PATH is the answer here. You should be using service(8) script since it does The Right Thing(tm). Apache will be started in more-or-less same environment that was used during boot time. (My personal opinion is that startup scripts should prepare such environment on their own unless explicitly told otherwise, and by environment I mean more that 'environment' variables.) If this is a bug or not I cannot say. /etc/rc.subr contains lines like: SYSCTL="/sbin/sysctl" ID="/usr/bin/id" for few tools, rest is assumed to work with provided PATH. To sum up, use service(8) and you will be fine. -- Mateusz Guzik From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 14:39:38 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33A93703; Fri, 23 Nov 2012 14:39:38 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 4C42A8FC16; Fri, 23 Nov 2012 14:39:37 +0000 (UTC) Received: from alph.allbsd.org (p1137-ipbf1505funabasi.chiba.ocn.ne.jp [118.7.212.137]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id qANEdIUv025619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Nov 2012 23:39:28 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.allbsd.org (8.14.5/8.14.5) with ESMTP id qANEdIbS002005; Fri, 23 Nov 2012 23:39:18 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Fri, 23 Nov 2012 23:37:54 +0900 (JST) Message-Id: <20121123.233754.1596631883684484110.hrs@allbsd.org> To: mwlucas@michaelwlucas.com Subject: Re: after upgrade, can't restart apache via cron From: Hiroki Sato In-Reply-To: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart0(Fri_Nov_23_23_37_54_2012_910)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Fri, 23 Nov 2012 23:39:29 +0900 (JST) X-Spam-Status: No, score=-97.6 required=13.0 tests=CONTENT_TYPE_PRESENT, FAKEDWORD_BACKQUOTE,ONLY1HOPDIRECT,SAMEHELOBY2HOP,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-rc@FreeBSD.org, current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd-rc@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 14:39:38 -0000 ----Security_Multipart0(Fri_Nov_23_23_37_54_2012_910)-- Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Nov_23_23_37_54_2012_649)--" Content-Transfer-Encoding: 7bit ----Next_Part(Fri_Nov_23_23_37_54_2012_649)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Michael W. Lucas" wrote in <20121123031753.GA59632@bewilderbeast.blackhelicopters.org>: mw> eval: setfib: not found mw> /usr/local/etc/rc.d/apache22: WARNING: failed to start apache22 mw> mw> If I run /usr/local/etc/rc.d/apache22 restart from the command line, I mw> can restart httpd without trouble. mw> mw> Any thoughts? This was due to $PATH in the cron job as already pointed out, but this should not happen. I attached a patch to use full-path for external commands in rc.subr. If there is no objection to this change I will commit it. -- Hiroki ----Next_Part(Fri_Nov_23_23_37_54_2012_649)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="rc.subr.cmdpath.20121123-1.diff" Index: etc/rc.subr =================================================================== --- etc/rc.subr (revision 243327) +++ etc/rc.subr (working copy) @@ -49,6 +49,18 @@ IDCMD="if [ -x $ID ]; then $ID -un; fi" PS="/bin/ps -ww" JID=`$PS -p $$ -o jid=` +CHROOT_CMD="/usr/sbin/chroot" +DEVFS_CMD="/sbin/devfs" +EGREP_CMD="/usr/bin/egrep" +GREP_CMD="/usr/bin/grep" +KLDSTAT_CMD="/sbin/kldstat" +KLDLOAD_CMD="/sbin/kldload" +LOGGER_CMD="/usr/bin/logger" +MDMFS_CMD="/sbin/mdmfs" +MOUNT_CMD="/sbin/mount" +NICE_CMD="/usr/bin/nice" +SETFIB_CMD="/usr/sbin/setfib" +SU_CMD="/usr/bin/su" # # functions @@ -181,7 +193,7 @@ if $_ismounted; then : else - mount $_fs >/dev/null 2>&1 + ${MOUNT_CMD} $_fs >/dev/null 2>&1 fi ) done @@ -726,17 +738,17 @@ check_startmsgs && echo "Starting ${name}." if [ -n "$_chroot" ]; then _doit="\ -${_nice:+nice -n $_nice }\ -${_fib:+setfib -F $_fib }\ -chroot ${_user:+-u $_user }${_group:+-g $_group }${_groups:+-G $_groups }\ +${_nice:+${NICE_CMD} -n $_nice }\ +${_fib:+${SETFIB_CMD} -F $_fib }\ +${CHROOT_CMD} ${_user:+-u $_user }${_group:+-g $_group }${_groups:+-G $_groups }\ $_chroot $command $rc_flags $command_args" else _doit="\ ${_chdir:+cd $_chdir && }\ -${_fib:+setfib -F $_fib }\ +${_fib:+${SETFIB_CMD} -F $_fib }\ $command $rc_flags $command_args" if [ -n "$_user" ]; then - _doit="su -m $_user -c 'sh -c \"$_doit\"'" + _doit="${SU_CMD} -m $_user -c 'sh -c \"$_doit\"'" fi if [ -n "$_nice" ]; then if [ -z "$_user" ]; then @@ -953,7 +965,7 @@ _cmd="kill -$1 $rc_pid" if [ -n "$_user" ]; then - _cmd="su -m ${_user} -c 'sh -c \"${_cmd}\"'" + _cmd="${SU_CMD} -m ${_user} -c 'sh -c \"${_cmd}\"'" fi echo "$_cmd" } @@ -1110,8 +1122,8 @@ exitval=$1 shift - if [ -x /usr/bin/logger ]; then - logger "$0: ERROR: $*" + if [ -x ${LOGGER_CMD} ]; then + ${LOGGER_CMD} "$0: ERROR: $*" fi echo 1>&2 "$0: ERROR: $*" exit $exitval @@ -1123,8 +1135,8 @@ # warn() { - if [ -x /usr/bin/logger ]; then - logger "$0: WARNING: $*" + if [ -x ${LOGGER_CMD} ]; then + ${LOGGER_CMD} "$0: WARNING: $*" fi echo 1>&2 "$0: WARNING: $*" } @@ -1137,8 +1149,8 @@ { case ${rc_info} in [Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1) - if [ -x /usr/bin/logger ]; then - logger "$0: INFO: $*" + if [ -x ${LOGGER_CMD} ]; then + ${LOGGER_CMD} "$0: INFO: $*" fi echo "$0: INFO: $*" ;; @@ -1155,8 +1167,8 @@ { case ${rc_debug} in [Yy][Ee][Ss]|[Tt][Rr][Uu][Ee]|[Oo][Nn]|1) - if [ -x /usr/bin/logger ]; then - logger "$0: DEBUG: $*" + if [ -x ${LOGGER_CMD} ]; then + ${LOGGER_CMD} "$0: DEBUG: $*" fi echo 1>&2 "$0: DEBUG: $*" ;; @@ -1320,7 +1332,7 @@ fi eval $rulename=\$rulenum debug "found ruleset: $rulename=$rulenum" - if ! /sbin/devfs rule -s $rulenum delset; then + if ! ${DEVFS_CMD} rule -s $rulenum delset; then _err=1 break fi @@ -1331,7 +1343,7 @@ # other rules if [ -n "$rulecmd" ]; then debug "adding rule ($rulecmd)" - if ! eval /sbin/devfs rule -s $rulenum $rulecmd + if ! eval ${DEVFS_CMD} rule -s $rulenum $rulecmd then _err=1 break @@ -1389,7 +1401,7 @@ return 1 fi debug "$_me: setting ruleset ($rs) on mount-point (${devdir#-m })" - if ! /sbin/devfs $devdir ruleset $rs; then + if ! ${DEVFS_CMD} $devdir ruleset $rs; then warn "$_me: unable to set ruleset $rs to ${devdir#-m }" return 1 fi @@ -1414,7 +1426,7 @@ return 1 fi debug "$_me: applying ruleset ($rs) to mount-point (${devdir#-m })" - if ! /sbin/devfs $devdir rule -s $rs applyset; then + if ! ${DEVFS_CMD} $devdir rule -s $rs applyset; then warn "$_me: unable to apply ruleset $rs to ${devdir#-m }" return 1 fi @@ -1438,14 +1450,14 @@ return 1 fi debug "$_me: mount-point is ($devdir), ruleset is ($rs)" - if ! mount -t devfs dev "$devdir"; then + if ! ${MOUNT_CMD} -t devfs dev "$devdir"; then warn "$_me: Unable to mount devfs on $devdir" return 1 fi if [ -n "$rs" ]; then devfs_init_rulesets devfs_set_ruleset $rs $devdir - devfs -m $devdir rule applyset + ${DEVFS_CMD} -m $devdir rule applyset fi return 0 } @@ -1483,7 +1495,7 @@ if [ -n "$3" ]; then flags="$3" fi - /sbin/mdmfs $flags -s $1 md $2 + ${MDMFS_CMD} $flags -s $1 md $2 } # Code common to scripts that need to load a kernel module @@ -1512,16 +1524,16 @@ _mod=${_mod:-$1} _loaded=false if [ -n "$_re" ]; then - if kldstat -v | egrep -q -e "$_re"; then + if ${KLDSTAT_CMD} -v | ${EGREP_CMD} -q -e "$_re"; then _loaded=true fi else - if kldstat -q -m "$_mod"; then + if ${KLDSTAT_CMD} -q -m "$_mod"; then _loaded=true fi fi if ! $_loaded; then - if ! kldload "$1"; then + if ! ${KLDLOAD_CMD} "$1"; then warn "Unable to load kernel module $1" return 1 else @@ -1607,12 +1619,12 @@ for dir in ${local_startup}; do if [ -d "${dir}" ]; then for file in ${dir}/[0-9]*.sh; do - grep '^# PROVIDE:' $file >/dev/null 2>&1 && + ${GREP_CMD} '^# PROVIDE:' $file >/dev/null 2>&1 && continue zlist="$zlist $file" done for file in ${dir}/[!0-9]*.sh; do - grep '^# PROVIDE:' $file >/dev/null 2>&1 && + ${GREP_CMD} '^# PROVIDE:' $file >/dev/null 2>&1 && continue slist="$slist $file" done @@ -1624,7 +1636,7 @@ local_rc='' for dir in ${local_startup}; do if [ -d "${dir}" ]; then - for file in `grep -l '^# PROVIDE:' ${dir}/* 2>/dev/null`; do + for file in `${GREP_CMD} -l '^# PROVIDE:' ${dir}/* 2>/dev/null`; do case "$file" in *.sample) ;; *) if [ -x "$file" ]; then ----Next_Part(Fri_Nov_23_23_37_54_2012_649)---- ----Security_Multipart0(Fri_Nov_23_23_37_54_2012_910)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAlCvikIACgkQTyzT2CeTzy2yzACdEQHZqMfc6auIsEPrUgqZ2Jfi rLYAoI8ZS8Pp7aEB2a2+riVyvQBJYqvy =v0c/ -----END PGP SIGNATURE----- ----Security_Multipart0(Fri_Nov_23_23_37_54_2012_910)---- From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 15:12:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44B8F4A5 for ; Fri, 23 Nov 2012 15:12:01 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas-2-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:b9c::2]) by mx1.freebsd.org (Postfix) with ESMTP id 044268FC15 for ; Fri, 23 Nov 2012 15:11:59 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5) with ESMTP id qANFBxQL065499; Fri, 23 Nov 2012 10:11:59 -0500 (EST) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5/Submit) id qANFBw0B065498; Fri, 23 Nov 2012 10:11:59 -0500 (EST) (envelope-from mwlucas) Date: Fri, 23 Nov 2012 10:11:58 -0500 From: "Michael W. Lucas" To: Adam Vande More Subject: Re: after upgrade, can't restart apache via cron Message-ID: <20121123151158.GA65473@bewilderbeast.blackhelicopters.org> References: <20121123031753.GA59632@bewilderbeast.blackhelicopters.org> 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) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Fri, 23 Nov 2012 10:11:59 -0500 (EST) X-Mailman-Approved-At: Fri, 23 Nov 2012 16:01:39 +0000 Cc: current@freebsd.org, "Michael W. Lucas" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 15:12:01 -0000 On Thu, Nov 22, 2012 at 09:33:34PM -0600, Adam Vande More wrote: > I would guess you need*/usr/sbin/ in cron's path. Thanks everyone. The real problem here was, I didn't know setfib was a command... ==ml -- Michael W. Lucas http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Latest book: SSH Mastery http://www.michaelwlucas.com/nonfiction/ssh-mastery mwlucas@michaelwlucas.com, Twitter @mwlauthor From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 19:25:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED517B86 for ; Fri, 23 Nov 2012 19:25:24 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id BFAA08FC15 for ; Fri, 23 Nov 2012 19:25:24 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qANJOSAq021985; Fri, 23 Nov 2012 19:24:28 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 4796ikux3q2dkp6sxbt6jjscqa; Fri, 23 Nov 2012 19:24:28 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: prompt w/ uid 0 for cshrc Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Fri, 23 Nov 2012 11:24:26 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20121118234426.GA16628@dft-labs.eu> To: jb X-Mailer: Apple Mail (2.1283) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 19:25:25 -0000 On Nov 19, 2012, at 8:46 AM, jb wrote: > Eitan Adler eitanadler.com> writes: >=20 >>=20 >> On 18 November 2012 18:44, Mateusz Guzik gmail.com> = wrote: >>> Just take user name from id -nu. >>=20 >> While that does provide the $user value I want, id is in /usr/bin/ >> which may not be mounted. >=20 > /rescue/id Bad idea: * /rescue tools are not part of the "standard" world * /rescue tools are sometimes not installed * Quite a few people have customized the rescue tools to adding or = omitting things suitable for their particular installation. * /rescue tools are not guaranteed to be functionally identical to the = non-rescue versions. Better to invoke 'id' in a way that produces "reasonable" results if 'id' is unavailable. For example: /bin/sh -c 'id -nu 2>/dev/null' || echo '?' prints '?' if the id command fails or is unavailable. Tim From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 21:46:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9EAC987 for ; Fri, 23 Nov 2012 21:46:55 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.44]) by mx1.freebsd.org (Postfix) with SMTP id 2BA378FC08 for ; Fri, 23 Nov 2012 21:46:55 +0000 (UTC) Received: (qmail invoked by alias); 23 Nov 2012 21:40:13 -0000 Received: from 178.128.120.133.dsl.dyn.forthnet.gr (EHLO [192.168.1.77]) [178.128.120.133] by mail.gmx.com (mp-eu003) with SMTP; 23 Nov 2012 22:40:13 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX19oVO11ALBoPLWI5yM7vu3XbK9E6HD5El6IyehXQc xQkXEactlwNFZa Message-ID: <50AFED32.5020005@gmx.com> Date: Fri, 23 Nov 2012 23:40:02 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: Sergey Kandaurov Subject: Re: strange buildworld failure References: <50AF3509.7070402@gmx.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 21:46:55 -0000 On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: >> Also, my src.conf had WITHOUT_CLANG but I deleted it and then I >> also deleted /usr/obj when it failed for the first time. But that >> didn't work. I am building with -j3. > > Does it always fail there at usr.bin/ypwhich? > It's likely that -j3 is the culprit of why you do not see the actual build > error because it might be lost off the screen. Try to restart without -jN. > Thanks, that worked. Nikos From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 22:05:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF25BF28 for ; Fri, 23 Nov 2012 22:05:59 +0000 (UTC) (envelope-from husyh@hush.com) Received: from smtp10.hushmail.com (smtp10a.hushmail.com [65.39.178.239]) by mx1.freebsd.org (Postfix) with ESMTP id C64A18FC08 for ; Fri, 23 Nov 2012 22:05:59 +0000 (UTC) Received: from smtp10.hushmail.com (smtp10a.hushmail.com [65.39.178.239]) by smtp10.hushmail.com (Postfix) with SMTP id 249B41B50DB for ; Fri, 23 Nov 2012 21:35:52 +0000 (UTC) Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80]) by smtp10.hushmail.com (Postfix) with ESMTP; Fri, 23 Nov 2012 21:35:51 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id C2CB9E6739; Fri, 23 Nov 2012 21:35:51 +0000 (UTC) MIME-Version: 1.0 Date: Fri, 23 Nov 2012 22:35:51 +0100 To: "Adrian Chadd" , "John Baldwin" Subject: Re: ath0: unable to attach hardware From: husyh@hush.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20121123213551.C2CB9E6739@smtp.hushmail.com> Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 22:06:00 -0000 Hello everyone, since this problem hasn't got any attention in the last 14 days, I decided to file a bug report, so that this issue doesn't sink into oblivion: http://www.freebsd.org/cgi/query-pr.cgi?pr=173883 I'm still very glad for any attempt to help, and willing to provide more information and/or test things if you provide some guidance. Thanks! On Samstag, 10. November 2012 at 2:39 PM, husyh@hush.com wrote: > >Hello everyone, > >I took both the i386 and amd64 November snapshots of 10.0-CURRENT >from https://snapshots.glenbarber.us/Latest/, and when the >bootloader on the DVD appeared, I selected the verbose boot >option, waited for the installer to come up, dropped to a shell >and issued "dmesg", the output of which I piped to two files which >hopefully are attached to this e-mail. In case they are stripped >from the mailing list, I've posted their contents to a nopaste: >http://nopaste.info/a445c43d6a.html for amd64 >http://nopaste.info/bac000949c.html for i386 > >I hope this is the information you were asking for. Please let me >know if I can do anything else. > >Thank you very much. > >On Samstag, 10. November 2012 at 7:49 AM, "Adrian Chadd" > wrote: >> >>Hi, >> >>I'm CC'ing jhb@ (who is likely busy after Hurricane Sandy..) who >>spends time in the PCI bridge code. >> >>That looks correct (ie, the BAR(0) entry matches your dmesg >entry.) >> >>The 0xffffffff register response however means that it isn't >mapped >>into that particular region correctly. An asleep NIC will return >>0xdeadbeef, 0xdeadc0de, etc. >>It doesn't return 0xffffffff for registers (well, except for >>AR_ISR, >>but that isn't being probed at this point.) >> >>Did you post a boot -v to -current, showing what all the PCI >>bridges >>are? I'd like to ensure that they're all setup right. >>Unfortunately I >>don't have time to try and figure out what's going on with the PCI >>bridge and resource allocation side of things. >> >>John - I think this is a PCI-PCI bridge resource allocation / >setup >>problem. The BAR(0) for the NIC matches what the probe/attach >line >>for >>ath0 says. but the register value of 0xffffffff to me indicates >the >>NIC isn't mapped into that space correctly. The internal PCI glue >>in >>the NIC will return 0xdeadbeef, 0xdeadc0de, etc as register >>contents >>if the device is asleep and hasn't been woken up or reset >>correctly. >>It won't return 0xffffffff. >> >>I would really appreciate any help you or others can provide on >>this. >> >>Thanks, >> >> >> >>Adrian >> >>On 9 November 2012 15:25, wrote: >>> Hello, >>> >>> thank you for your reply. >>> >>> I've entered the following >>> pciconf -r ath0@pci0:2:4:0 0:255 >>> and received this output: >>> >>> 001b168c 02900406 02000001 00002008 >>> fdee0000 00000000 00000000 00000000 >>> 00000000 00000000 00005001 500111ad >>> 00000000 00000044 00000000 1c0a0110 >>> 00000000 01c20001 c6004000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> 00000000 00000000 00000000 00000000 >>> >>> I hope this helps you out. If not, please let me know what else >>I can do. >>> >>> Thanks! >>> >>> On Freitag, 9. November 2012 at 5:45 PM, "Adrian Chadd" >> wrote: >>>> >>>>Can you use pciconf to dump the config space? >>>> >>>>I think its pciconf -r 0:255 >>>> >>>>thanks! >>>> >>>> >>>> >>>>adrian >>>> >>>>On 9 November 2012 01:57, wrote: >>>>> Hello again, >>>>> >>>>> the mail I'm replying to (and which is cited below) hasn't >>>>caused a reaction yet. Seeing that this mailing list has quite a >>>>lot of traffic, I'm worried that the mail, and the issue it >tries >>>>to point out, will be forgotten. >>>>> Should I file a bug report in hopes that the issue will >>somewhen >>>>be investigated/resolved? >>>>> >>>>> Again, I'm offering any kind of help I'm able to provide, i.e. >>>>delivering more information upon (hopefully detailed enough for >>me >>>>to understand) request, testing proposed fixes and doing some >>>>progamming on my own; for the latter, please keep in mind that I >>>>have no experience with the FreeBSD codebase or hardware >>>>programming. >>>>> >>>>> Thanks! >>>>> >>>>> On Samstag, 3. November 2012 at 11:43 AM, husyh@hush.com >wrote: >>>>>> >>>>>>Hello everyone, >>>>>> >>>>>>I'm new to FreeBSD and wanted to install 9.0-RELEASE amd64 on >a >>>>PC >>>>>>I was given. At first glance, it seems like everything is >>>>working, >>>>>>except the wireless LAN PCI card. >>>>>> >>>>>>I started a thread on freebsd-wireless on the 31st of October >>>>(see >>>>>>here: http://lists.freebsd.org/pipermail/freebsd- >wireless/2012- >>>>>>October/002511.html or a repost of my original message with >>>>proper >>>>>>formatting: http://lists.freebsd.org/pipermail/freebsd- >>>>>>wireless/2012-October/002513.html ) >>>>>> >>>>>>Short summary: >>>>>>The card has the strings "Anatel", "WN5301A-H1-V02" and >>>>>>"KN160562*7" printed on it, although I'm not sure which, if >>any, >>>>>>of those is a proper product number. >>>>>>After setting >>>>>> >>>>>>hw.ath.debug=1 >>>>>>hw.ath.hal.debug=1 >>>>>> >>>>>>I receive >>>>>> >>>>>>ath0: mem 0xfdee0000-0xfdeeffff irq 16 at >device >>>>>>4.0 on pci2 >>>>>>ar5212ChipTest: address test failed addr: 0x00008000 - >>>>>>wr:0x00000000 != rd:0xffffffff >>>>>>ar5212Attach: hardware self-test failed >>>>>>ath0: unable to attach hardware; HAL status 14 >>>>>>device_attach: ath0 attach returned 6 >>>>>> >>>>>>and am left unable to use the device. >>>>>>I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and >i386 >>>>>>snapshots from https://snapshots.glenbarber.us/Latest/ >>>>(seemlingly >>>>>>built a few days ago) and received the same messages, >although >>I >>>>>>did not get the debug messages since I booted off of the >>>>>>installation media and therefore had a stock kernel, which >>>>>>seemingly doesn't enable ATH_DEBUG and AH_DEBUG. Booting the >>>>>>Ubuntu 12.04 amd64 installation media, I can use the NIC >>without >>>>>>having any problems. >>>>>> >>>>>>Adrian Chadd tried to help me via freebsd-wireless (thank you >>>>>>again,) but ultimately asked me this: >>>>>>"Please try a recent -HEAD i386 and amd64 snapshot and if that >>>>>>doesn't >>>>>>work, you could try posting for help on freebsd-current. But >>>>please >>>>>>stress that I think it's a bus enumeration and PCI bridge >>>>>>programming >>>>>>problem, _not_ a driver problem." >>>>>> >>>>>>And so I did. >>>>>> >>>>>>I'd be very glad if you could try to help me. Of course, I'm >>>>>>willing to provide any kind of information you might need, but >>>>>>please keep in mind that I'm new to FreeBSD and therefore >would >>>>be >>>>>>thankful if you stated your instructions/requests in a newbie- >>>>>>friendly way. >>>>>> >>>>>>Thank you. >>>>>> >>>>>>_______________________________________________ >>>>>>freebsd-current@freebsd.org mailing list >>>>>>http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>To unsubscribe, send any mail to "freebsd-current- >>>>>>unsubscribe@freebsd.org" >>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current- >>>>unsubscribe@freebsd.org" >>> From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 22:14:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4130A211 for ; Fri, 23 Nov 2012 22:14:02 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id BA3488FC12 for ; Fri, 23 Nov 2012 22:14:01 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9076618lah.13 for ; Fri, 23 Nov 2012 14:14:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=9lWOrywSMFpxp5mAeZ9l76uBIIYJCvNhmf1DjtftpkA=; b=UgkKECV1sU/6MSPd7EL5xSiUfyVQwN0QtGA+yETopnmDdQVTvxb/0rzueinjwbRbeS wnmB0eGk4MxlQEZQeeqVVfK7XfQWtiZmMfIzr2us3YAmaXFufzDAOI+wAxzj+ewOjUz7 /nHIS+8C+USCM6LDSvRdB/msHQuGyGpxPENLIjRCsz2ObhmM/t8lrha6hA/WqD4xlQHZ D5/RbKfWoHLX2dhVSvSScJl57azYrcXQUBTo2iiWsVBjLOGCjQ0RDv3jeVHEgitlJLHj 9zBfjVa0YYVAlGXIpZGm6vyuVHmXyVqgaMyDUlI7fbSZ96iklyJIdSdzdBybWKLR7wnm J9Sw== Received: by 10.152.123.103 with SMTP id lz7mr4597284lab.21.1353708840060; Fri, 23 Nov 2012 14:14:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.101.72 with HTTP; Fri, 23 Nov 2012 14:13:39 -0800 (PST) From: Christer Solskogen Date: Fri, 23 Nov 2012 23:13:39 +0100 Message-ID: Subject: pkg - Shared object "libarchive.so.5" not found, required by "pkg" To: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 22:14:02 -0000 I just upgraded a machine from 9.1-RC3 to 10-CURRENT. pkg was installed on 9.1, but after an upgrade to 10-CURRENT pkg no longer runs due to missing shared library. 10-CURRENT was built (and installed) twice. I guess the library was installed when I was at 9.1-RC3 but was deleted during make delete-old. Rebuilding pkg from src/usr.sbin/pkg did not do the trick. For some reason it was still linking to the old library. Any hints? -- chs, From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 22:56:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA2C0E36; Fri, 23 Nov 2012 22:56:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 21EB08FC0C; Fri, 23 Nov 2012 22:56:03 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so3553487wey.13 for ; Fri, 23 Nov 2012 14:56:02 -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=eJTfIKm+trNCYdjxZUVS1dubbRoRvkhTYoivEaNh2vc=; b=n+ZVfY3mXHOEE2wHwC9fX1K4rBiR3eS4RFPjtIy86p5vHzA6dOsSRo+kHIoM0qkAOd ZnqHL8sVNx8s7/x6fuPHE8Ew5hDg2mB5tXnGs6nyEAbr0eVgg3bmjnuFNu76W7ZPE7j6 cK6QZbVvOa9O9BfVHAO6QC2oUH6FaQ5/RXak9v7dn+qqi/LUtiWRKGe+AqouAk+4+UYP i9aIqNpH9Qo1dHz1DV3CINQ0Db3osII2ZUedsp/8KP6384zZiLp6gsW/JK+j7gcSuSKy Gv3c4yDrRh04wDf1LL6t7FLIpgiT3oBSGt9io3fkMsECCQm5L+lC71Ik97DXmfo+o0cZ NhxA== MIME-Version: 1.0 Received: by 10.180.97.137 with SMTP id ea9mr3754254wib.13.1353711362484; Fri, 23 Nov 2012 14:56:02 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 23 Nov 2012 14:56:02 -0800 (PST) In-Reply-To: <20121123213551.C2CB9E6739@smtp.hushmail.com> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> Date: Fri, 23 Nov 2012 14:56:02 -0800 X-Google-Sender-Auth: JSx1MhTfgFwsS5yDEi2Ammogo3E Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: husyh@hush.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 22:56:04 -0000 Thanks for this! I'm sorry it hasn't gotten any more attention. I've cc'ed john because he understands the PCI-PCI resource allocation stuff and I currently don't; I'm hoping he can stare at this and see what's going on. But yes, if it were an ath(4) problem, the NIC would be returning 0xdeadbeef, 0xdeadc0de, etc. It wouldn't return 0xffffffff - that happens when there's nothing mapped at that address. The PCI config space that you've provided shows BAR(0) is programmed correctly.. adrian On 23 November 2012 13:35, wrote: > Hello everyone, > > since this problem hasn't got any attention in the last 14 days, I decided to file a bug report, so that this issue doesn't sink into oblivion: http://www.freebsd.org/cgi/query-pr.cgi?pr=173883 > > I'm still very glad for any attempt to help, and willing to provide more information and/or test things if you provide some guidance. > > Thanks! > > On Samstag, 10. November 2012 at 2:39 PM, husyh@hush.com wrote: >> >>Hello everyone, >> >>I took both the i386 and amd64 November snapshots of 10.0-CURRENT >>from https://snapshots.glenbarber.us/Latest/, and when the >>bootloader on the DVD appeared, I selected the verbose boot >>option, waited for the installer to come up, dropped to a shell >>and issued "dmesg", the output of which I piped to two files which >>hopefully are attached to this e-mail. In case they are stripped >>from the mailing list, I've posted their contents to a nopaste: >>http://nopaste.info/a445c43d6a.html for amd64 >>http://nopaste.info/bac000949c.html for i386 >> >>I hope this is the information you were asking for. Please let me >>know if I can do anything else. >> >>Thank you very much. >> >>On Samstag, 10. November 2012 at 7:49 AM, "Adrian Chadd" >> wrote: >>> >>>Hi, >>> >>>I'm CC'ing jhb@ (who is likely busy after Hurricane Sandy..) who >>>spends time in the PCI bridge code. >>> >>>That looks correct (ie, the BAR(0) entry matches your dmesg >>entry.) >>> >>>The 0xffffffff register response however means that it isn't >>mapped >>>into that particular region correctly. An asleep NIC will return >>>0xdeadbeef, 0xdeadc0de, etc. >>>It doesn't return 0xffffffff for registers (well, except for >>>AR_ISR, >>>but that isn't being probed at this point.) >>> >>>Did you post a boot -v to -current, showing what all the PCI >>>bridges >>>are? I'd like to ensure that they're all setup right. >>>Unfortunately I >>>don't have time to try and figure out what's going on with the PCI >>>bridge and resource allocation side of things. >>> >>>John - I think this is a PCI-PCI bridge resource allocation / >>setup >>>problem. The BAR(0) for the NIC matches what the probe/attach >>line >>>for >>>ath0 says. but the register value of 0xffffffff to me indicates >>the >>>NIC isn't mapped into that space correctly. The internal PCI glue >>>in >>>the NIC will return 0xdeadbeef, 0xdeadc0de, etc as register >>>contents >>>if the device is asleep and hasn't been woken up or reset >>>correctly. >>>It won't return 0xffffffff. >>> >>>I would really appreciate any help you or others can provide on >>>this. >>> >>>Thanks, >>> >>> >>> >>>Adrian >>> >>>On 9 November 2012 15:25, wrote: >>>> Hello, >>>> >>>> thank you for your reply. >>>> >>>> I've entered the following >>>> pciconf -r ath0@pci0:2:4:0 0:255 >>>> and received this output: >>>> >>>> 001b168c 02900406 02000001 00002008 >>>> fdee0000 00000000 00000000 00000000 >>>> 00000000 00000000 00005001 500111ad >>>> 00000000 00000044 00000000 1c0a0110 >>>> 00000000 01c20001 c6004000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> 00000000 00000000 00000000 00000000 >>>> >>>> I hope this helps you out. If not, please let me know what else >>>I can do. >>>> >>>> Thanks! >>>> >>>> On Freitag, 9. November 2012 at 5:45 PM, "Adrian Chadd" >>> wrote: >>>>> >>>>>Can you use pciconf to dump the config space? >>>>> >>>>>I think its pciconf -r 0:255 >>>>> >>>>>thanks! >>>>> >>>>> >>>>> >>>>>adrian >>>>> >>>>>On 9 November 2012 01:57, wrote: >>>>>> Hello again, >>>>>> >>>>>> the mail I'm replying to (and which is cited below) hasn't >>>>>caused a reaction yet. Seeing that this mailing list has quite a >>>>>lot of traffic, I'm worried that the mail, and the issue it >>tries >>>>>to point out, will be forgotten. >>>>>> Should I file a bug report in hopes that the issue will >>>somewhen >>>>>be investigated/resolved? >>>>>> >>>>>> Again, I'm offering any kind of help I'm able to provide, i.e. >>>>>delivering more information upon (hopefully detailed enough for >>>me >>>>>to understand) request, testing proposed fixes and doing some >>>>>progamming on my own; for the latter, please keep in mind that I >>>>>have no experience with the FreeBSD codebase or hardware >>>>>programming. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> On Samstag, 3. November 2012 at 11:43 AM, husyh@hush.com >>wrote: >>>>>>> >>>>>>>Hello everyone, >>>>>>> >>>>>>>I'm new to FreeBSD and wanted to install 9.0-RELEASE amd64 on >>a >>>>>PC >>>>>>>I was given. At first glance, it seems like everything is >>>>>working, >>>>>>>except the wireless LAN PCI card. >>>>>>> >>>>>>>I started a thread on freebsd-wireless on the 31st of October >>>>>(see >>>>>>>here: http://lists.freebsd.org/pipermail/freebsd- >>wireless/2012- >>>>>>>October/002511.html or a repost of my original message with >>>>>proper >>>>>>>formatting: http://lists.freebsd.org/pipermail/freebsd- >>>>>>>wireless/2012-October/002513.html ) >>>>>>> >>>>>>>Short summary: >>>>>>>The card has the strings "Anatel", "WN5301A-H1-V02" and >>>>>>>"KN160562*7" printed on it, although I'm not sure which, if >>>any, >>>>>>>of those is a proper product number. >>>>>>>After setting >>>>>>> >>>>>>>hw.ath.debug=1 >>>>>>>hw.ath.hal.debug=1 >>>>>>> >>>>>>>I receive >>>>>>> >>>>>>>ath0: mem 0xfdee0000-0xfdeeffff irq 16 at >>device >>>>>>>4.0 on pci2 >>>>>>>ar5212ChipTest: address test failed addr: 0x00008000 - >>>>>>>wr:0x00000000 != rd:0xffffffff >>>>>>>ar5212Attach: hardware self-test failed >>>>>>>ath0: unable to attach hardware; HAL status 14 >>>>>>>device_attach: ath0 attach returned 6 >>>>>>> >>>>>>>and am left unable to use the device. >>>>>>>I tried 8.3-RELEASE i386 as well as 10.0-CURRENT amd64 and >>i386 >>>>>>>snapshots from https://snapshots.glenbarber.us/Latest/ >>>>>(seemlingly >>>>>>>built a few days ago) and received the same messages, >>although >>>I >>>>>>>did not get the debug messages since I booted off of the >>>>>>>installation media and therefore had a stock kernel, which >>>>>>>seemingly doesn't enable ATH_DEBUG and AH_DEBUG. Booting the >>>>>>>Ubuntu 12.04 amd64 installation media, I can use the NIC >>>without >>>>>>>having any problems. >>>>>>> >>>>>>>Adrian Chadd tried to help me via freebsd-wireless (thank you >>>>>>>again,) but ultimately asked me this: >>>>>>>"Please try a recent -HEAD i386 and amd64 snapshot and if that >>>>>>>doesn't >>>>>>>work, you could try posting for help on freebsd-current. But >>>>>please >>>>>>>stress that I think it's a bus enumeration and PCI bridge >>>>>>>programming >>>>>>>problem, _not_ a driver problem." >>>>>>> >>>>>>>And so I did. >>>>>>> >>>>>>>I'd be very glad if you could try to help me. Of course, I'm >>>>>>>willing to provide any kind of information you might need, but >>>>>>>please keep in mind that I'm new to FreeBSD and therefore >>would >>>>>be >>>>>>>thankful if you stated your instructions/requests in a newbie- >>>>>>>friendly way. >>>>>>> >>>>>>>Thank you. >>>>>>> >>>>>>>_______________________________________________ >>>>>>>freebsd-current@freebsd.org mailing list >>>>>>>http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>>>To unsubscribe, send any mail to "freebsd-current- >>>>>>>unsubscribe@freebsd.org" >>>>>> >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to "freebsd-current- >>>>>unsubscribe@freebsd.org" >>>> > From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 23:54:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D331527D for ; Fri, 23 Nov 2012 23:54:47 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id A87AD8FC0C for ; Fri, 23 Nov 2012 23:54:47 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id qANNskP6023230; Fri, 23 Nov 2012 23:54:46 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id avrdfcnqbwsi476u2kjdiepy26; Fri, 23 Nov 2012 23:54:46 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: Date: Fri, 23 Nov 2012 15:54:42 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: To: Christer Solskogen X-Mailer: Apple Mail (2.1283) Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2012 23:54:47 -0000 On Nov 23, 2012, at 2:13 PM, Christer Solskogen wrote: > 10-CURRENT was built (and installed) twice. I guess the library was > installed when I was at 9.1-RC3 but was deleted during make > delete-old. "delete-old" should not have deleted any libraries. I think you must have also done "delete-old-libs". That often requires you to reinstall all your ports as well. > Rebuilding pkg from src/usr.sbin/pkg did not do the trick. For some > reason it was still linking to the old library. > Any hints? /usr/sbin/pkg mostly just runs /usr/local/sbin/pkg You need to reinstall the pkg port as well. Tim From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 02:43:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8501EBEB for ; Sat, 24 Nov 2012 02:43:57 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id 19BDB8FC0C for ; Sat, 24 Nov 2012 02:43:56 +0000 (UTC) X-AuditID: 1209190f-b7f636d00000095b-82-50b0333a94bb Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 61.6F.02395.A3330B05; Fri, 23 Nov 2012 21:38:50 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id qAO2cnV1018818; Fri, 23 Nov 2012 21:38:50 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qAO2ckYZ000322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Nov 2012 21:38:49 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAO2cjlD000101; Fri, 23 Nov 2012 21:38:45 -0500 (EST) Date: Fri, 23 Nov 2012 21:38:45 -0500 (EST) From: Benjamin Kaduk To: Nikos Vassiliadis Subject: Re: strange buildworld failure In-Reply-To: <50AFED32.5020005@gmx.com> Message-ID: References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsUixG6nomtlvCHAoL9H0mLOmw9MFrtn7Wd2 YPKY8Wk+i8fd+wuZApiiuGxSUnMyy1KL9O0SuDKenu9lLtjFWnHnXwdjA+Nyli5GTg4JAROJ TdM3MUPYYhIX7q1n62Lk4hAS2McoMe/4VHYIZwOjxMY7U5kgnBNMEre7LkM5DYwSv/dvYwfp ZxHQlrh29iEjiM0moCIx881GNhBbREBVYtOVnWBxZgF5if9XQJo5OIQF1CWOnhYCCXMCmTPu HGcFsXkFHCSunehihJjfxiixfuF8sDmiAjoSq/dPYYEoEpQ4OfMJC8RMS4lzf66zTWAUnIUk NQtJagEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdE73czBK91JTSTYygYOWU5N/B+O2g0iFG AQ5GJR7exDPrA4RYE8uKK3MPMUpyMCmJ8q4z3BAgxJeUn1KZkVicEV9UmpNafIhRgoNZSYT3 awVQOW9KYmVValE+TEqag0VJnPdqyk1/IYH0xJLU7NTUgtQimKwMB4eSBO9nkKGCRanpqRVp mTklCGkmDk6Q4TxAwy+C1PAWFyTmFmemQ+RPMSpKifPuBUkIgCQySvPgemHJ5BWjONArwryX Qap4gIkIrvsV0GAmoMFPZ68DGVySiJCSamBk2v4w8MvuppIdC6vTL77e8+vPysOMor9y9j7X 75x88hXbEgnlfu9zlckci8TLWx+9vngj/ZySzeRH8zsSGI3kfhhxT+zRnH7GMOm2YKP2q/wJ FU95/0a8rz7yom2p7pMy7ollD64zh4pp+u60UJB43bqEgz8p6OOKVZsdH7D8971Q4dvm90pe iaU4I9FQi7moOBEAhByVcgEDAAA= Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 02:43:57 -0000 On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: > On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: >>> Also, my src.conf had WITHOUT_CLANG but I deleted it and then I >>> also deleted /usr/obj when it failed for the first time. But that >>> didn't work. I am building with -j3. >> >> Does it always fail there at usr.bin/ypwhich? >> It's likely that -j3 is the culprit of why you do not see the actual build >> error because it might be lost off the screen. Try to restart without -jN. >> > > Thanks, that worked. Hmm, buildworld is supposed to be parallel-make-safe. Perhaps a full log of the failing buildworld (e.g., with script(1)) could be posted for analysis? -Ben Kaduk From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 03:08:29 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D86FF96 for ; Sat, 24 Nov 2012 03:08:29 +0000 (UTC) (envelope-from rysto32@gmail.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 D86708FC08 for ; Sat, 24 Nov 2012 03:08:28 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fo13so13106990vcb.13 for ; Fri, 23 Nov 2012 19:08:28 -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=W/9HoR+xIfMloIZSgbFU47kczgnBqgY79qwyZFMIrLQ=; b=VZgzBXY0D7DqmhZLqnC2kGnIxiBu7uhkC+DoA2skahwATcisqjNyxV94QfTzNCfCEd DQ8i7CZCdMjHfzTvArYy0Qe+9M/NpVZzHVA+ueTlFmFgHuSxHqmOXRwLui1WY6uJkrHq emGPZzeeQgFs3lFHBI9dTyMrbYJu0xbL9DTwVXD5d3JJGVyCDIlXxlpWylQcmO+JSHR5 v4zKkDFY4UxLWG8BNcBf6lBikT5PqcS7ZJhyabcDJ/jUg7rjR3fCvLOyLqRT4s5Ufy8F ek9480DBaFbl3QocONhiN92FfNhLUHPt7m/c9YLshIY/hwOuaqZ/QpI1DzVlDqAYU7xc yVdg== MIME-Version: 1.0 Received: by 10.52.90.241 with SMTP id bz17mr7667411vdb.40.1353726508123; Fri, 23 Nov 2012 19:08:28 -0800 (PST) Received: by 10.58.207.114 with HTTP; Fri, 23 Nov 2012 19:08:28 -0800 (PST) Date: Fri, 23 Nov 2012 22:08:28 -0500 Message-ID: Subject: Spurious witness warning when destroying spin mtx From: Ryan Stone To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 03:08:29 -0000 Today I saw a spurious witness warning for "acquiring duplicate lock of same type". The root cause is that when running mtx_destroy on a spinlock that is held by the current thread, mtx_destroy calls spinlock_exit() before calling WITNESS_UNLOCK, which opens up a window in which the CPU can be interrupted and attempt to acquire another spinlock of the same type as the one being destroyed. This patch should fix it: diff --git a/sys/kern/kern_mutex.c b/sys/kern/kern_mutex.c index 2f13863..96f43f8 100644 --- a/sys/kern/kern_mutex.c +++ b/sys/kern/kern_mutex.c @@ -918,16 +918,16 @@ _mtx_destroy(volatile uintptr_t *c) else { MPASS((m->mtx_lock & (MTX_RECURSED|MTX_CONTESTED)) == 0); + lock_profile_release_lock(&m->lock_object); + /* Tell witness this isn't locked to make it happy. */ + WITNESS_UNLOCK(&m->lock_object, LOP_EXCLUSIVE, __FILE__, + __LINE__); + /* Perform the non-mtx related part of mtx_unlock_spin(). */ if (LOCK_CLASS(&m->lock_object) == &lock_class_mtx_spin) spinlock_exit(); else curthread->td_locks--; - - lock_profile_release_lock(&m->lock_object); - /* Tell witness this isn't locked to make it happy. */ - WITNESS_UNLOCK(&m->lock_object, LOP_EXCLUSIVE, __FILE__, - __LINE__); } m->mtx_lock = MTX_DESTROYED From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 09:55:54 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A65022B4 for ; Sat, 24 Nov 2012 09:55:54 +0000 (UTC) (envelope-from christer.solskogen@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 23E3B8FC08 for ; Sat, 24 Nov 2012 09:55:52 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so9305848lah.13 for ; Sat, 24 Nov 2012 01:55:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=501f6Xs8R9RLrUio7BdOca53MxlLkCHehERJoG2xL9A=; b=JOCnh/SL0LsHcxQKER4z+7GZKwzP3YN22czwdLgTvL/y+LXeW4Cfa9G52FK7XRbsNY jdei3smIMMoy+pdC2mtn47BluVXRJCH3qp+fXQzakIr/rDvfTZpwCHnIkHiH3vktnZ8Z 66vcVmSWLUXF8rB1oz+X6yvYEJxib322CJww6KtYGMlXrl869cPw/9q9a8Qv8Tr70yTp IzDgdbR9ii88v2fm/HVxXqBU8J8xLMLEc5ktoyE9NJeLbWef5oesXFKT4UWpVw8zLHyt 04ENx6ElnhdxVZHtS2swRsXnyluBTiriHKe2LWga8QmcHjhItBsw2JPsuUTsUFHWuNhv YkDQ== Received: by 10.112.29.229 with SMTP id n5mr2856980lbh.130.1353750951776; Sat, 24 Nov 2012 01:55:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.101.72 with HTTP; Sat, 24 Nov 2012 01:55:31 -0800 (PST) In-Reply-To: References: From: Christer Solskogen Date: Sat, 24 Nov 2012 10:55:31 +0100 Message-ID: Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" To: Tim Kientzle Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 09:55:54 -0000 On Sat, Nov 24, 2012 at 12:54 AM, Tim Kientzle wrote: > /usr/sbin/pkg mostly just runs /usr/local/sbin/pkg > > You need to reinstall the pkg port as well. > After a while I figured that out. I did not have a ports tree on that machine, so I just deleted /usr/local and and package database and reinstalled every ports using pkg. -- chs, From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 11:44:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D93EB1AC for ; Sat, 24 Nov 2012 11:44:57 +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 8E5F38FC08 for ; Sat, 24 Nov 2012 11:44:57 +0000 (UTC) Received: from [192.168.0.6] (spaceball.home.andric.com [192.168.0.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 18C435C37; Sat, 24 Nov 2012 12:44:56 +0100 (CET) Message-ID: <50B0B33F.4060802@FreeBSD.org> Date: Sat, 24 Nov 2012 12:45:03 +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: Benjamin Kaduk Subject: Re: strange buildworld failure References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nikos Vassiliadis , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 11:44:57 -0000 On 2012-11-24 03:38, Benjamin Kaduk wrote: > On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: >> On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: >>>> Also, my src.conf had WITHOUT_CLANG but I deleted it and then I >>>> also deleted /usr/obj when it failed for the first time. But that >>>> didn't work. I am building with -j3. >>> >>> Does it always fail there at usr.bin/ypwhich? >>> It's likely that -j3 is the culprit of why you do not see the actual build >>> error because it might be lost off the screen. Try to restart without -jN. >>> >> >> Thanks, that worked. > > Hmm, buildworld is supposed to be parallel-make-safe. > Perhaps a full log of the failing buildworld (e.g., with script(1)) could > be posted for analysis? Well, either a full log, or the tail of the log, as long as it contains the actual command(s) that failed. Sometimes it can help to search backwards with less, or your favorite editor, for the string "error:", or if there is no such string, searching for other problem indicators. Also, copies of make.conf and src.conf are often essential in finding the cause of the problem. Many build issues are caused by erroneous settings. :) From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 14:11:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8659B3E for ; Sat, 24 Nov 2012 14:11:34 +0000 (UTC) (envelope-from paul.g.webster@googlemail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8358FC0C for ; Sat, 24 Nov 2012 14:11:33 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id 12so5101366wgr.31 for ; Sat, 24 Nov 2012 06:11:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:to:subject:references:date:mime-version :content-transfer-encoding:from:organization:message-id:in-reply-to :user-agent; bh=E2oGWdkTZeoFiI8jrG1YFqrt6mEaLZeR0w6hcJ5Ho6k=; b=C54z/780la2zbBEXzWAHtVx5WqzPm4a+yxMK2UUMScWpHGZw0trZAU9m6vnTGRUjhC hcPKDM+YdRvrnhCL2UfybDqnqo+rfZTbgltyA9ID5hr1h3RaIXG5JZnG9EjNx3QsL7p1 hQQOyySnZD4ah9iLTAu5e4tL4MqorO38XFBx/lyAH1ihFtClM2aFO/TM/hL7eOheg4+R 991Rgzv9NY4IjADEGUFbRdvIDGbWpUlB86MO4sWURLVlyuu6zkb52MjuAzLJvi3IjTjh TVe9yqbGHoNa4CkmU+/l21P9aAhjpqzzDgbTAe9vY67qUWQY69ayh6HuuNUguMadAhxK wDvA== Received: by 10.216.195.225 with SMTP id p75mr2658105wen.8.1353766293062; Sat, 24 Nov 2012 06:11:33 -0800 (PST) Received: from box.dlink.com (host-78-149-65-188.as13285.net. [78.149.65.188]) by mx.google.com with ESMTPS id gz3sm12858491wib.2.2012.11.24.06.11.31 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 24 Nov 2012 06:11:32 -0800 (PST) Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: freebsd-current@freebsd.org Subject: Re: Upgrading FreeBSD to use the NEW pf syntax. References: <201211201543.17903.Mark.Martinec+freebsd@ijs.si> <20121121075642.GR67660@FreeBSD.org> <20121121145240.GE67660@glebius.int.ru> Date: Sat, 24 Nov 2012 14:11:32 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Paul Webster" Organization: Interflective Group Message-ID: In-Reply-To: User-Agent: Opera Mail/12.11 (Win64) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 14:11:35 -0000 I only really need one question answered in honesty; I personally think that by forking our own version of PF we have = essentially made something totally different to what everyone wants to = use. Which is fine, but because of that development of new features have= = dropped behind. If we had kept up with OpenBSD's version even if we trailed it by one = MAJOR release; at least part of the development would have been done. So now we end up in a situation where we have these firewalls, = IPFW2,ipf,pf(modded) and users wanting the newer features of OpenBSD's p= f. = So timewise the fork of pf may have actually cost more in time rather th= an = less. I don't however think the 'solution' to the problem is just to say no to= = the userbase by not even trying to port across the newer pf. I think we = = should look at bringing it across, slowly and seeing what the uptake is = = like; in a few MAJOR releases we can start to look at which of the = firewalls realistically are not used that much and should be deprecated.= On Wed, 21 Nov 2012 15:20:19 -0000, Ermal Lu=E7i wrote= : > On Wed, Nov 21, 2012 at 3:52 PM, Gleb Smirnoff = > wrote: > >> On Wed, Nov 21, 2012 at 03:44:13PM +0100, Ermal Lu?i wrote: >> E> Cherry-picking would be when tehre is reasonable similarities. >> E> Also another argument to do this would be simplicity on locking as= = >> well >> as >> E> i told you when you started the changes. >> >> You were wrong. OpenBSD doesn't move towards SMP model. Locking more >> recent pf is not simplier, but the opposite. >> >> > I am sorry but you are asking arguments i already have given you. > You didn;t listen once and i do not expect this time as well. > > >> E> Though i am open to work together on this to merge the new syntax >> thorugh a >> E> whole bulk merge rather than cherry-pick. >> >> How many bugs have you closed after the previous bulk import? Why sho= uld >> we expect anything good from new import if the previous one was a PIT= A? >> >> > Well you have used it for your work so it was not so PITA. > Most of the ones you closed had message 'This is to old to be true'; '= I > have re-written PF and this should be fixed'. > > >> And still I don't see any answer on the question: what exact features= or >> perfomance improvements are we going to obtain from "the new pf"? >> >> > See above. > > >> E> You already have 'broken' some functionality as if-bound in FreeBS= D >> 10.x so >> >> Is there any PR filed on that? I didn't even receive a mail about tha= t. >> >> > I really do not think you do the right approach or the right = > communication > on this. > Sorry for replying to you ;). > > >> -- >> Totus tuus, Glebius. >> > > > -- = Using Opera's revolutionary email client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 14:45:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEE8A32C for ; Sat, 24 Nov 2012 14:45:59 +0000 (UTC) (envelope-from victor@bsdes.net) Received: from equilibrium.bsdes.net (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.freebsd.org (Postfix) with ESMTP id 660AF8FC17 for ; Sat, 24 Nov 2012 14:45:58 +0000 (UTC) Received: by equilibrium.bsdes.net (Postfix, from userid 1001) id 37FF039832; Sat, 24 Nov 2012 15:45:51 +0100 (CET) Date: Sat, 24 Nov 2012 15:45:51 +0100 From: Victor Balada Diaz To: Christer Solskogen Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" Message-ID: <20121124144550.GE50873@equilibrium.bsdes.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 14:45:59 -0000 On Fri, Nov 23, 2012 at 11:13:39PM +0100, Christer Solskogen wrote: > I just upgraded a machine from 9.1-RC3 to 10-CURRENT. > pkg was installed on 9.1, but after an upgrade to 10-CURRENT pkg no > longer runs due to missing shared library. > 10-CURRENT was built (and installed) twice. I guess the library was > installed when I was at 9.1-RC3 but was deleted during make > delete-old. > > Rebuilding pkg from src/usr.sbin/pkg did not do the trick. For some > reason it was still linking to the old library. > Any hints? Hello, You have pkg-static for that kind of problems. You should rebuild pkg port to get pkg working again. Regards. Victor. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 15:01:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 632706A9; Sat, 24 Nov 2012 15:01:42 +0000 (UTC) (envelope-from asmrookie@gmail.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 9C5A58FC08; Sat, 24 Nov 2012 15:01:40 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so6847320lbb.13 for ; Sat, 24 Nov 2012 07:01:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=GHyIzlRJ2d05wThFT2PJCqJ+dd36JbEcT9vycS6ZK+E=; b=f1IOQJNNfZjRR6YLvBuo5CUGTE1B9CdMGPTBZ6FbxgRnwKBkjb4Vvgr3ItaZuVUb5V t2xdA7h+BwdLbgRrDPKLixJtxv6GIAhu+Io7CeEVNes8UqgR2TKy97awI45DtinG/Afm qBMUbr78BucTG4crGp5MrAYKLqvqcYKd+OJrQIMseQeuyOaQ8M+/LvtU/Z/40D6OmroP olYcerAFoVcpB2L0pTVL0uNV44KRZ+5V0WiuA1vNcER3pyv1/FK3cFQnngLSjvTGtR7f zeAv+sca0fLf+t5nFWleEdnv9LZScku7xBIiuBhaO9NGhWF8slNu491AvW1sCAOTkSET Zn0A== MIME-Version: 1.0 Received: by 10.152.162.1 with SMTP id xw1mr6301907lab.3.1353769300071; Sat, 24 Nov 2012 07:01:40 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sat, 24 Nov 2012 07:01:39 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Nov 2012 15:01:39 +0000 X-Google-Sender-Auth: Zr32j1vTKyIjGT-_Bc7aMC6fxao Message-ID: Subject: Re: Spurious witness warning when destroying spin mtx From: Attilio Rao To: Ryan Stone , John Baldwin Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 15:01:42 -0000 On Sat, Nov 24, 2012 at 3:08 AM, Ryan Stone wrote: > Today I saw a spurious witness warning for "acquiring duplicate lock of > same type". The root cause is that when running mtx_destroy on a spinlock > that is held by the current thread, mtx_destroy calls spinlock_exit() > before calling WITNESS_UNLOCK, which opens up a window in which the CPU can > be interrupted and attempt to acquire another spinlock of the same type as > the one being destroyed. This patch should fix it: I seriously wonder why right now we don't assume the lock is unheld. There are likely historically reasons for that, but I would like to know which one are those and eventually fix them out. FWIK, all the other locking primitives assume the lock is already unheld when destroying and I think it would be good to have that for mutexes as well. Can you please show which lock triggers the panic you saw? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 15:46:19 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5BE786E; Sat, 24 Nov 2012 15:46:19 +0000 (UTC) (envelope-from rysto32@gmail.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 CFE0B8FC0C; Sat, 24 Nov 2012 15:46:18 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so1887092vba.13 for ; Sat, 24 Nov 2012 07:46:18 -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=s2cBXDyt2xYqPX28hKnhB8A1O0zoGUMRpnJokpMRVbg=; b=OO4v2mNRSy3JqtcTI5Pq11/IM+RWlza0bIFKk6Aa+tB9KL48AcrP5sR+bfY76FVqwB UkJS9D/Dmm6MVZvrV3JQ2WVMDoaFCApgKgEtpG8GNKkcIjYNDrJNev0zQODxya3I0+4x sPaOp5lSp+6+dyFxN/ke0H0BaTOZ2y2BKWftKXWi4yHb3/OQSddyGFMKMiuex2xx2oYs CZfLQtxBa/8SSXUleJOfRTNRVT8Ih5hzPNSx9LDvwRosv0EKXTLdtIkmuohOmOKK/nrk lHymt3F1YpUTobCncUTp6SX8OQD5vDz9L2dG5cYM77htWCZE3JCKSPRUN+7Hna0ZQ8pm xncg== MIME-Version: 1.0 Received: by 10.52.27.241 with SMTP id w17mr9538649vdg.96.1353771977988; Sat, 24 Nov 2012 07:46:17 -0800 (PST) Received: by 10.58.207.114 with HTTP; Sat, 24 Nov 2012 07:46:17 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Nov 2012 10:46:17 -0500 Message-ID: Subject: Re: Spurious witness warning when destroying spin mtx From: Ryan Stone To: Attilio Rao Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 15:46:19 -0000 On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao wrote: > I seriously wonder why right now we don't assume the lock is unheld. > There are likely historically reasons for that, but I would like to > know which one are those and eventually fix them out. > FWIK, all the other locking primitives assume the lock is already > unheld when destroying and I think it would be good to have that for > mutexes as well. > > Can you please show which lock triggers the panic you saw? > > Thanks, > Attilio > > It was taskqueue_free: void taskqueue_free(struct taskqueue *queue) { TQ_LOCK(queue); queue->tq_flags &= ~TQ_FLAGS_ACTIVE; taskqueue_terminate(queue->tq_threads, queue); KASSERT(TAILQ_EMPTY(&queue->tq_active), ("Tasks still running?")); KASSERT(queue->tq_callouts == 0, ("Armed timeout tasks")); mtx_destroy(&queue->tq_mutex); free(queue->tq_threads, M_TASKQUEUE); free(queue, M_TASKQUEUE); } From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 15:48:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7EED1A8 for ; Sat, 24 Nov 2012 15:48:58 +0000 (UTC) (envelope-from nvass@gmx.com) Received: from mailout-eu.gmx.com (mailout-eu.gmx.com [213.165.64.44]) by mx1.freebsd.org (Postfix) with SMTP id 394998FC13 for ; Sat, 24 Nov 2012 15:48:58 +0000 (UTC) Received: (qmail invoked by alias); 24 Nov 2012 15:48:56 -0000 Received: from 178.128.120.133.dsl.dyn.forthnet.gr (EHLO [192.168.1.77]) [178.128.120.133] by mail.gmx.com (mp-eu002) with SMTP; 24 Nov 2012 16:48:56 +0100 X-Authenticated: #46156728 X-Provags-ID: V01U2FsdGVkX19/zME8Z61/ECctDb4W5O4uPwY2PyS0WiJHisiEVr eyBGmxZEhbziC0 Message-ID: <50B0EC5B.1080104@gmx.com> Date: Sat, 24 Nov 2012 17:48:43 +0200 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: strange buildworld failure References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> In-Reply-To: <50B0B33F.4060802@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org, Benjamin Kaduk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 15:48:58 -0000 On 11/24/2012 1:45 PM, Dimitry Andric wrote: > On 2012-11-24 03:38, Benjamin Kaduk wrote: >> On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: >>> On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: >>>>> Also, my src.conf had WITHOUT_CLANG but I deleted it and then I >>>>> also deleted /usr/obj when it failed for the first time. But that >>>>> didn't work. I am building with -j3. >>>> >>>> Does it always fail there at usr.bin/ypwhich? >>>> It's likely that -j3 is the culprit of why you do not see the actual build >>>> error because it might be lost off the screen. Try to restart without -jN. >>>> >>> >>> Thanks, that worked. >> >> Hmm, buildworld is supposed to be parallel-make-safe. >> Perhaps a full log of the failing buildworld (e.g., with script(1)) could >> be posted for analysis? > > Well, either a full log, or the tail of the log, as long as it contains > the actual command(s) that failed. Sometimes it can help to search > backwards with less, or your favorite editor, for the string "error:", > or if there is no such string, searching for other problem indicators. > > Also, copies of make.conf and src.conf are often essential in finding > the cause of the problem. Many build issues are caused by erroneous > settings. :) I installed world after the successful build, so now it probably is too late to get a more useful problem report:( By the way, I tried to add some debugging info with the help of make -d A or -d g2 but the amount of logging was excessive(the build was ran in a tmux terminal and the tmux process was using more CPU time than the build itself, so I canceled). What should I use with "make -d" in order to get some basic debugging? Or is there another way? Thanks in advance, Nikos From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 15:51:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60F722CA; Sat, 24 Nov 2012 15:51:13 +0000 (UTC) (envelope-from asmrookie@gmail.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 A4EA58FC12; Sat, 24 Nov 2012 15:51:12 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so6868074lbb.13 for ; Sat, 24 Nov 2012 07:51:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CYpgVJnXLlwLTbDc8TtDTtNpdgV3nMttj9y2gOKOzgE=; b=Ijfzhr8w9vGlRkWy4miqy6LQ45i15UeWhKY8D9q60O4xWNztuEbDVzdUHSKqiXW1vs pdn/eziIa2oOlo4auu+COVoul//y+fhFLVAqr8bGFH5j0bGHuePUOYDRB+JdZJs5Gss2 eMRHGrsyUAT5Io9j0KO0N0vtAbdN+rf/9DORqMMRk5GavTSZdaaL5iZ22h+/2svcxOc4 o/OvnGPHGWQyXVk7Bnk3+7C4PnxNR8ImLfUd5VREnNTH6pYVR0UT0srjn+oOzN9BdLHi OydOQF0ek7VHCpUOdln+fMqz8+rm5OrQiBJFUf4SZrZOLk5UIznDtBTgxK+B2uZ9uIc5 4Kvg== MIME-Version: 1.0 Received: by 10.112.24.41 with SMTP id r9mr3013236lbf.115.1353772271403; Sat, 24 Nov 2012 07:51:11 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sat, 24 Nov 2012 07:51:11 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Nov 2012 15:51:11 +0000 X-Google-Sender-Auth: x3XD8SGpDdC5-Wk70xbclgK-Zeo Message-ID: Subject: Re: Spurious witness warning when destroying spin mtx From: Attilio Rao To: Ryan Stone Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 15:51:13 -0000 On Sat, Nov 24, 2012 at 3:46 PM, Ryan Stone wrote: > > On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao wrote: >> >> I seriously wonder why right now we don't assume the lock is unheld. >> There are likely historically reasons for that, but I would like to >> know which one are those and eventually fix them out. >> FWIK, all the other locking primitives assume the lock is already >> unheld when destroying and I think it would be good to have that for >> mutexes as well. >> >> Can you please show which lock triggers the panic you saw? >> >> Thanks, >> Attilio >> > > It was taskqueue_free: taskqueue_free() must not be called in places where there are still races, so the lock is not really meaningful and should be acquired. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 16:16:03 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C96FC64B; Sat, 24 Nov 2012 16:16:03 +0000 (UTC) (envelope-from asmrookie@gmail.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 0FAE68FC08; Sat, 24 Nov 2012 16:16:02 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so6879083lbb.13 for ; Sat, 24 Nov 2012 08:16:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=yZF2MVY0AGAjBaiU5rTWKzytSPGbFEvDkgsZhOnpWqE=; b=ODpRjz35Ik8Vtfsm/kDUDUkWHAZpOVwxxD0es5/12wWCZu/wvRhs7nBSwOyuGk3F62 EpKLcpmcH4RKlv+8lzyE8s8/z1OzoHVngYtA3APlC6U2Ylin+U+uw6IkICsr9XKP1W9q WFdbJtzA9l5WDghceE8XhA6lZmfeGPuhaAZnz5pmKnK2CtHvkPzAtyGbWpnTyujLFbnB i7spD34BYftrXTcL/McekDtORGAPvPPUvUT7X5ImOJV2Wzxj0qzl9Uzxapyb6j8PEVi2 HfNGs1NrgjCm5iFgsQSoOyGeH3Bg6gPoBmrP9JxYq1SUkqtf2KN/+M/AJy/v/Bev/Pei W/rQ== MIME-Version: 1.0 Received: by 10.152.104.50 with SMTP id gb18mr6482132lab.9.1353773761333; Sat, 24 Nov 2012 08:16:01 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.112.134.5 with HTTP; Sat, 24 Nov 2012 08:16:01 -0800 (PST) In-Reply-To: References: Date: Sat, 24 Nov 2012 16:16:01 +0000 X-Google-Sender-Auth: YF6dnUXsjlGfNSfVvCS3OfD_cFY Message-ID: Subject: Re: Spurious witness warning when destroying spin mtx From: Attilio Rao To: Ryan Stone Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 16:16:03 -0000 On Sat, Nov 24, 2012 at 3:51 PM, Attilio Rao wrote: > On Sat, Nov 24, 2012 at 3:46 PM, Ryan Stone wrote: >> >> On Sat, Nov 24, 2012 at 10:01 AM, Attilio Rao wrote: >>> >>> I seriously wonder why right now we don't assume the lock is unheld. >>> There are likely historically reasons for that, but I would like to >>> know which one are those and eventually fix them out. >>> FWIK, all the other locking primitives assume the lock is already >>> unheld when destroying and I think it would be good to have that for >>> mutexes as well. >>> >>> Can you please show which lock triggers the panic you saw? >>> >>> Thanks, >>> Attilio >>> >> >> It was taskqueue_free: > > taskqueue_free() must not be called in places where there are still > races, so the lock is not really meaningful and should be acquired. Herm, I mean to say "after taskqueue_termintate() returns must not be races...". Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 18:39:09 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 47531449 for ; Sat, 24 Nov 2012 18:39:09 +0000 (UTC) (envelope-from christer.solskogen@gmail.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 B13778FC08 for ; Sat, 24 Nov 2012 18:39:08 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id go10so6933579lbb.13 for ; Sat, 24 Nov 2012 10:39:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aZtJ9Z8ltaOcbBlR88d0I2TkRcnpsgrx25/Ca6NWt6U=; b=c9KYgWIktOoLlRzqBEct7MIDSmovpieRL7bQtwJTQy0QoiZVS56PBbmOr5PrxXEYKH GSlE5mCutntaG3lzSy+cCKaEzKahh+rh5jfYXfRjySA//YgH6k/0W3G06m8JYFv3Cep1 Cd2MSjCnGXmebMHBYve3M8OZuVEsBQzlLjtKmlIlG/5ehDKjBl18JzPgD0lDnMLpM+JC 6kXjTsxinGpm7Dxl+d2p7kBoP9SF0A17qDSn4xs4FJHNfRaTe+nD+PEeqE/0Q8Khvg/x 3ElAcLlu3iR1TToR2or8Y0XTVegQQItosttNVfa7bNTut1H525eCwjWkTQJt5tPJmTQU Ma3A== Received: by 10.152.111.166 with SMTP id ij6mr6564525lab.38.1353782347227; Sat, 24 Nov 2012 10:39:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.101.72 with HTTP; Sat, 24 Nov 2012 10:38:46 -0800 (PST) In-Reply-To: <20121124144550.GE50873@equilibrium.bsdes.net> References: <20121124144550.GE50873@equilibrium.bsdes.net> From: Christer Solskogen Date: Sat, 24 Nov 2012 19:38:46 +0100 Message-ID: Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" To: Victor Balada Diaz Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 18:39:09 -0000 On Sat, Nov 24, 2012 at 3:45 PM, Victor Balada Diaz wrote: > > You have pkg-static for that kind of problems. You should rebuild pkg > port to get pkg working again. So I still need /usr/ports when I use pkg? -- chs, From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 18:54:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C4A40A2A for ; Sat, 24 Nov 2012 18:54:02 +0000 (UTC) (envelope-from jlaffaye.freebsd@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 4147E8FC08 for ; Sat, 24 Nov 2012 18:54:01 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id a14so2984346eaa.13 for ; Sat, 24 Nov 2012 10:54:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=b4w9bxCWIFosWFyQOXM24gv2PMHZmRCupxLiwjcaiic=; b=FQ03d3IV9F8HNRGRz5bKY8fCe56mE2nHEJ+yoc0BnRHryxaN/2n77Aumt1mmL1A676 iwveETGSORrbkNKQNF7ZYIyhvOFNDTKRIWCyY1csxnVGyQJXpCqlyULn16baEwOeyn8r /Clzm47LjnKT7184Pmi+D0RRhJ8dQRieRoUfVL2q6dIXLApE5XNkVwiFtw8BiHNfQFWx qdWpOvNaEJfRU8gJ1zzszzcEX2cXHSVDcF6p5mJ4DGazneVewiDx2xk0SQxBTzJY3qzk g8l2PImQl/Ow5roI1gb2zFCd6ghDOg7MnVqNL0nerL5F5OTeWZlFdrbMbQzB//i45mDw 3DUQ== Received: by 10.14.223.200 with SMTP id v48mr26898714eep.24.1353782754809; Sat, 24 Nov 2012 10:45:54 -0800 (PST) Received: from ?IPv6:2001:41d0:fc00:100:f051:70e4:5701:5854? ([2001:41d0:fc00:100:f051:70e4:5701:5854]) by mx.google.com with ESMTPS id e2sm22166278eeo.8.2012.11.24.10.45.52 (version=SSLv3 cipher=OTHER); Sat, 24 Nov 2012 10:45:53 -0800 (PST) Sender: Julien Laffaye Message-ID: <50B115E4.1080207@freebsd.org> Date: Sat, 24 Nov 2012 19:45:56 +0100 From: Julien Laffaye User-Agent: Thunderbird/7.0.1 MIME-Version: 1.0 To: Christer Solskogen Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" References: <20121124144550.GE50873@equilibrium.bsdes.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Victor Balada Diaz , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 18:54:02 -0000 On 11/24/2012 7:38 PM, Christer Solskogen wrote: > On Sat, Nov 24, 2012 at 3:45 PM, Victor Balada Diaz wrote: >> You have pkg-static for that kind of problems. You should rebuild pkg >> port to get pkg working again. > So I still need /usr/ports when I use pkg? > No. CURRENT is a special case because there is no ABI guarantee throughout its lifetime. (A package built for -CURRENT has a very little meaning, and we cant build them for every svn revision). So, yes, on CURRENT you'd better build your packages. From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 18:55:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4260EB45 for ; Sat, 24 Nov 2012 18:55:42 +0000 (UTC) (envelope-from break19@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id F27D38FC0C for ; Sat, 24 Nov 2012 18:55:41 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so10329392iec.13 for ; Sat, 24 Nov 2012 10:55:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=b7dWpS9b5bqxv+aAlxGKe+WEOvEla6ATz4teYP0W+50=; b=x0LrRZwBTEcOzxi49kejK27lTUFwDNMCO2l8C8rJnwYQn/3j1Tr7KM+rsDJ2ENBTdu ybZ5bNIR6OVOp6Ip6oc7Dk7KpQL6nnlZ5/d1bziDDGn7wt3vSv4YNtAmHxty2ikwFqOC VDSr3qcu/a2RRLSQnJQBWw/z6SaLkIuKDxCi8WYfEUmGF2uVPcKs+lfvQVLaIKrPGSBh Zq37SsrGmE1vZxC7MYV4ns0iEAgIC1LklXzP+JSmUykygRrZ9VHdjz+UXeCDIJmx59mE tBBOaO7RPZs/HZi112rn1aYaifGktVLPio44CDood2PC+3+toPnRY8+E2RP+eWOyk61l rBGg== Received: by 10.50.6.136 with SMTP id b8mr4227247iga.54.1353783341091; Sat, 24 Nov 2012 10:55:41 -0800 (PST) Received: from [192.168.0.199] (173-119-243-27.pools.spcsdns.net. [173.119.243.27]) by mx.google.com with ESMTPS id i10sm6959409igb.12.2012.11.24.10.55.38 (version=SSLv3 cipher=OTHER); Sat, 24 Nov 2012 10:55:40 -0800 (PST) Message-ID: <50B117F8.4040804@gmail.com> Date: Sat, 24 Nov 2012 12:54:48 -0600 From: Chuck Burns User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: pkg - Shared object "libarchive.so.5" not found, required by "pkg" References: <20121124144550.GE50873@equilibrium.bsdes.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 18:55:42 -0000 On 11/24/2012 12:38 PM, Christer Solskogen wrote: > On Sat, Nov 24, 2012 at 3:45 PM, Victor Balada Diaz wrote: >> >> You have pkg-static for that kind of problems. You should rebuild pkg >> port to get pkg working again. > > So I still need /usr/ports when I use pkg? > No. ports-mgmt/pkg can be self-bootstrapped with no need to compile anything. -but- If you want to use -stable or -current, then you really should use ports as well... -- Chuck Burns From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 19:48:29 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87EE78F8; Sat, 24 Nov 2012 19:48:29 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0BEE88FC12; Sat, 24 Nov 2012 19:48:28 +0000 (UTC) X-AuditID: 12074423-b7fab6d0000008f9-9c-50b12486a0f5 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 31.A5.02297.68421B05; Sat, 24 Nov 2012 14:48:22 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id qAOJmL8t026389; Sat, 24 Nov 2012 14:48:22 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qAOJmI9p027477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 24 Nov 2012 14:48:21 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAOJmIDX011861; Sat, 24 Nov 2012 14:48:18 -0500 (EST) Date: Sat, 24 Nov 2012 14:48:18 -0500 (EST) From: Benjamin Kaduk To: Nikos Vassiliadis Subject: Re: strange buildworld failure In-Reply-To: <50B0EC5B.1080104@gmx.com> Message-ID: References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIIsWRmVeSWpSXmKPExsUixCmqrNumsjHAYOVKeYslXfsYLea8+cBk sXvWfmYHZo8Zn+azeNy9v5ApgCmKyyYlNSezLLVI3y6BK+PM3QOMBbt5KjZ27WdtYPzM2cXI ySEhYCLxcPkfZghbTOLCvfVsXYxcHEIC+xglZp04CuVsYJQ4dPgRM4Rzgkliz+9nrBBOA6PE g3kPWEH6WQS0Ja7sWg82i01ARWLmm41sILaIgKrEpis7GUFsZgFHidYZ/9i7GDk4hAXUJY6e FgIJcwKZH5YtZQMJ8wo4SDx7HQYSFhL4yigxp9cExBYV0JFYvX8KC4jNKyAocXLmExaIiZYS 5/5cZ5vAKDgLSWoWktQCRqZVjLIpuVW6uYmZOcWpybrFyYl5ealFumZ6uZkleqkppZsYQSHL 7qK8g/HPQaVDjAIcjEo8vAln1gcIsSaWFVfmHmKU5GBSEuVdpbgxQIgvKT+lMiOxOCO+qDQn tfgQowQHs5IIrxFIjjclsbIqtSgfJiXNwaIkznst5aa/kEB6YklqdmpqQWoRTFaGg0NJgjdD GahRsCg1PbUiLTOnBCHNxMEJMpwHaLgySA1vcUFibnFmOkT+FKOilDhvMUhCACSRUZoH1wtL Ka8YxYFeEeZNB6niAaYjuO5XQIOZgAY/nb0OZHBJIkJKqoHRwWUhz0v+lNkB/Bd7fty+WvW9 d97eQI6JNWyLK2N0Oj6uSfscevTQ/L8Bq4+J/srpY7Iz4L/kPu3ipkvrVRXNBWzP271U+7HJ XXLytlkOX4yn9P0qd2YsZvt5j+vaHKbXk4suVRvt8De4nciSdvNG0sO9fHPt22da+bWu12p4 //ZzHb/4K8cnSizFGYmGWsxFxYkA+F78+AQDAAA= Cc: freebsd-current@FreeBSD.org, Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 19:48:29 -0000 On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: > On 11/24/2012 1:45 PM, Dimitry Andric wrote: >> On 2012-11-24 03:38, Benjamin Kaduk wrote: >>> >>> Hmm, buildworld is supposed to be parallel-make-safe. >>> Perhaps a full log of the failing buildworld (e.g., with script(1)) could >>> be posted for analysis? >> >> Well, either a full log, or the tail of the log, as long as it contains >> the actual command(s) that failed. Sometimes it can help to search >> backwards with less, or your favorite editor, for the string "error:", >> or if there is no such string, searching for other problem indicators. >> >> Also, copies of make.conf and src.conf are often essential in finding >> the cause of the problem. Many build issues are caused by erroneous >> settings. :) > > By the way, I tried to add some debugging info with the help of make -d A > or -d g2 but the amount of logging was excessive(the build was ran in a tmux > terminal and the tmux process was using more CPU time than the build itself, > so I canceled). What should I use with "make -d" in order to get some basic > debugging? Or is there another way? Most cases I know of where a parallel make fails and a serial make succeeds are due to incomplete specification of dependencies. This can usually be chased down with just a build log, without extra debugging information. I have only needed to resort to the make debugging outputs when doing more interesting things like custom suffix rules or using the SRCS+OBJS magic provided by the system makefiles in unusual ways. -Ben Kaduk From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 21:44:18 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09049BD3; Sat, 24 Nov 2012 21:44:18 +0000 (UTC) (envelope-from yanegomi@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 BE84A8FC17; Sat, 24 Nov 2012 21:44:17 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id wz12so7385389pbc.13 for ; Sat, 24 Nov 2012 13:44:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=TzkCA/GWpEvQRBhm3V93YobHr4RWlhO2xCYTTY7/S78=; b=rfe5oDT6YE58AvyBGXi6piW4jjmVLBBGL8kOvbae09nOMx3oWOYv5qGHzGNAV9v/xS QnjIzEBwpn5idkjf8g3NkF+9Eia8jG56kRwWx7Nzp3iRE4GwEytg6gepacJqDZPEn5/l v810hHEFrqO5sBhUoitYBgAPphFs51sOiMfapJbLR9zz1/FW/pzVzaby0KGhDi6xwTPH sgVzvHVxeVUQ4zK+vSABe3Ox09ddFmbOElU02PFg4UB3NnbaPevzxEhEGLd43ThXQE/Z tbn2vH07Y5+4vVTGl51mJ+aR0e8WQQ43wPVMHTfBb7JAV9C4fbb6kZcUbpY9i2JuylCr pXWQ== Received: by 10.68.137.131 with SMTP id qi3mr25339504pbb.114.1353793457132; Sat, 24 Nov 2012 13:44:17 -0800 (PST) Received: from [192.168.20.12] (c-24-19-191-56.hsd1.wa.comcast.net. [24.19.191.56]) by mx.google.com with ESMTPS id d2sm5941891paw.19.2012.11.24.13.44.15 (version=SSLv3 cipher=OTHER); Sat, 24 Nov 2012 13:44:15 -0800 (PST) References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com> X-Mailer: iPhone Mail (10A523) From: Garrett Cooper Subject: Re: strange buildworld failure Date: Sat, 24 Nov 2012 13:44:15 -0800 To: Benjamin Kaduk Cc: Nikos Vassiliadis , Dimitry Andric , "freebsd-current@FreeBSD.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 21:44:18 -0000 On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk wrote: > On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: >=20 >> On 11/24/2012 1:45 PM, Dimitry Andric wrote: >>> On 2012-11-24 03:38, Benjamin Kaduk wrote: >>>> Hmm, buildworld is supposed to be parallel-make-safe. >>>> Perhaps a full log of the failing buildworld (e.g., with script(1)) cou= ld >>>> be posted for analysis? >>> Well, either a full log, or the tail of the log, as long as it contains >>> the actual command(s) that failed. Sometimes it can help to search >>> backwards with less, or your favorite editor, for the string "error:", >>> or if there is no such string, searching for other problem indicators. >>> Also, copies of make.conf and src.conf are often essential in finding >>> the cause of the problem. Many build issues are caused by erroneous >>> settings. :) >>=20 >> By the way, I tried to add some debugging info with the help of make -d A= >> or -d g2 but the amount of logging was excessive(the build was ran in a t= mux >> terminal and the tmux process was using more CPU time than the build itse= lf, >> so I canceled). What should I use with "make -d" in order to get some bas= ic >> debugging? Or is there another way? >=20 > Most cases I know of where a parallel make fails and a serial make succeed= s are due to incomplete specification of dependencies. This can usually be c= hased down with just a build log, without extra debugging information. I ha= ve only needed to resort to the make debugging outputs when doing more inter= esting things like custom suffix rules or using the SRCS+OBJS magic provided= by the system makefiles in unusual ways. The more likely explanation is that one of the parallel threads died because= of enomem, enospc, or a number of other reasons, and it was some time earli= er on in the compile. Stating that it was a build dependency issue is probab= ly not a wise idea at this time as we do not have enough data (logs, no -d A= required) to substantiate that claim. Thanks, -Garrett= From owner-freebsd-current@FreeBSD.ORG Sat Nov 24 23:42:50 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 289165CD for ; Sat, 24 Nov 2012 23:42:50 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id B034C8FC12 for ; Sat, 24 Nov 2012 23:42:49 +0000 (UTC) X-AuditID: 1209190f-b7f636d00000095b-2e-50b15b7851a3 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 23.06.02395.87B51B05; Sat, 24 Nov 2012 18:42:48 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id qAONgmru024714; Sat, 24 Nov 2012 18:42:48 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qAONgjZE001415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 24 Nov 2012 18:42:46 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id qAONgids014618; Sat, 24 Nov 2012 18:42:44 -0500 (EST) Date: Sat, 24 Nov 2012 18:42:44 -0500 (EST) From: Benjamin Kaduk To: Garrett Cooper Subject: Re: strange buildworld failure In-Reply-To: <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com> Message-ID: References: <50AF3509.7070402@gmx.com> <50AFED32.5020005@gmx.com> <50B0B33F.4060802@FreeBSD.org> <50B0EC5B.1080104@gmx.com> <7C31A420-1072-4EB7-A83B-D14195434A16@gmail.com> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKIsWRmVeSWpSXmKPExsUixG6nrlsRvTHA4MJTFYs5bz4wWeyetZ/Z Yv33ZYwOzB4zPs1n8dg56y67x937C5kCmKO4bFJSczLLUov07RK4Mpq2GxY08lRcv3uNrYFx M2cXIyeHhICJxK7XH1ghbDGJC/fWs4HYQgL7GCU2rbHtYuQCsjcwStydd4YJInGCSaLhuA5E ooFRYtryxewgCRYBbYl5L94wgthsAioSM99sBJskIqAucenAFrAaZoFsiY9zZgAN4uAQBoof PS0EEuYUsJX4dOkCWDmvgIPEmd9NTBDz7zJJbJjxGOw6UQEdidX7p7BAFAlKnJz5hAVipqXE uT/X2SYwCs5CkpqFJLWAkWkVo2xKbpVubmJmTnFqsm5xcmJeXmqRrolebmaJXmpK6SZGUOhy SvLvYPx2UOkQowAHoxIPb+KZ9QFCrIllxZW5hxglOZiURHlNozYGCPEl5adUZiQWZ8QXleak Fh9ilOBgVhLhtVYFyvGmJFZWpRblw6SkOViUxHmvptz0FxJITyxJzU5NLUgtgsnKcHAoSfAW gQwVLEpNT61Iy8wpQUgzcXCCDOcBGt4PUsNbXJCYW5yZDpE/xagoJc7bA5IQAElklObB9cJS yytGcaBXhHkXgVTxANMSXPcroMFMQIOfzl4HMrgkESEl1cBY7+K9UVJe763mx6sn/Mxv6d9o nMNjldy2Q//k8sxpaRk8xiXpp757Sn98UcfhFqJde+ED5zqH+K+mkT9yzrBHLbdxtk2dwSsY kbpUt0bt9+9E0/0zGxuMfb9UJbE/2GmXsuq10r7rT7+d23688cKn20GGO/bbV0xkezlz+oen r/PKc2tv9akrsRRnJBpqMRcVJwIAaqqKdwgDAAA= Cc: Nikos Vassiliadis , "freebsd-current@FreeBSD.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Nov 2012 23:42:50 -0000 On Sat, 24 Nov 2012, Garrett Cooper wrote: > On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk wrote: > >> On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: >> >>> By the way, I tried to add some debugging info with the help of make -d A >>> or -d g2 but the amount of logging was excessive(the build was ran in a tmux >>> terminal and the tmux process was using more CPU time than the build itself, >>> so I canceled). What should I use with "make -d" in order to get some basic >>> debugging? Or is there another way? >> >> Most cases I know of where a parallel make fails and a serial make >> succeeds are due to incomplete specification of dependencies. This can >> usually be chased down with just a build log, without extra debugging >> information. I have only needed to resort to the make debugging >> outputs when doing more interesting things like custom suffix rules or >> using the SRCS+OBJS magic provided by the system makefiles in unusual >> ways. > > The more likely explanation is that one of the parallel threads died > because of enomem, enospc, or a number of other reasons, and it was some > time earlier on in the compile. Stating that it was a build dependency > issue is probably not a wise idea at this time as we do not have enough > data (logs, no -d A required) to substantiate that claim. The point I was trying to make is that a full build log should be sufficient to debug; 'make -d' magic is unlikely to be necessary. Sorry if it came out wrong. -Ben