From owner-freebsd-stable@FreeBSD.ORG Sun Jun 5 19:49:22 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 076BD1065673; Sun, 5 Jun 2011 19:49:22 +0000 (UTC) (envelope-from joerg_surmann@snafu.de) Received: from waikiki.ops.eusc.inter.net (waikiki.ops.eusc.inter.net [84.23.254.155]) by mx1.freebsd.org (Postfix) with ESMTP id BA3108FC08; Sun, 5 Jun 2011 19:49:21 +0000 (UTC) X-Trace: 507c73757269697c38352e3137392e3134332e3138377c3151544a4b332d303030 4835462d54577c31333037333033333539 Received: from waikiki.ops.eusc.inter.net ([10.155.10.19] helo=localhost) by waikiki.ops.eusc.inter.net with esmtpsa (Exim 4.72) id 1QTJK3-000H5F-TW; Sun, 05 Jun 2011 21:49:20 +0200 Message-ID: <4DEBDDB8.30001@snafu.de> Date: Sun, 05 Jun 2011 21:49:12 +0200 From: joerg_surmann User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Freebsd_mailinglist_PORTS , FreeBSD_mailiglist_KERNEL X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 85.179.143.187 X-SA-Exim-Mail-From: joerg_surmann@snafu.de X-SA-Exim-Scanned: No (on waikiki.ops.eusc.inter.net); SAEximRunCond expanded to false Cc: Subject: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2011 19:49:22 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, /usr/ports/textproc/py-libxml2# make install clean ===> Building for py27-libxml2-2.7.8_1 Making all in . gmake[1]: Entering directory `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' /bin/sh ../libtool --tag=CC --mode=link cc -O2 -pipe - -fno-strict-aliasing -std=gnu89 -pedantic -W -Wformat -Wunused - -Wimplicit -Wreturn-type -Wswitch -Wcomment -Wtrigraphs -Wformat - -Wchar-subscripts -Wuninitialized -Wparentheses -Wshadow -Wpointer-arith - -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes - -Wmissing-prototypes -Wnested-externs -Winline -Wredundant-decls -module - -avoid-version -L/usr/local/lib -o libxml2mod.la -rpath /usr/local/lib/python2.7/site-packages libxml.lo types.lo libxml2-py.lo - -lxml2 -L/usr/local/lib/python2.7/config -lpth -lutil -lm -lpython2.7 - -Wl,--export-dynamic libtool: link: cc -shared .libs/libxml.o .libs/types.o .libs/libxml2-py.o -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath - -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libxml2.so -lz /usr/local/lib/libiconv.so -L/usr/local/lib/python2.7/config -lpth - -lutil -lm -lpython2.7 -Wl,--export-dynamic -Wl,-soname - -Wl,libxml2mod.so -o .libs/libxml2mod.so /usr/bin/ld: cannot find -lpth gmake[1]: *** [libxml2mod.la] Fehler 1 gmake[1]: Leaving directory `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' gmake: *** [all-recursive] Fehler 1 *** Error code 1 Stop in /usr/ports/textproc/py-libxml2. have anyone a idea? thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3r3bgACgkQcEHvP2uxrTPMEgCgwnHvxLeDCnSTmy5FuEW4hW/c 3bUAnRVHz1vpfRvKq99fuPC3wp1zglRn =Q6/i -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 00:32:38 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17080106566B for ; Mon, 6 Jun 2011 00:32:38 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id C333E8FC14 for ; Mon, 6 Jun 2011 00:32:37 +0000 (UTC) Received: by qwc9 with SMTP id 9so2041768qwc.13 for ; Sun, 05 Jun 2011 17:32:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iT7Ywsl09luyutDCyDEXzsPM4DyT3xW9Xsw0zRPmtjo=; b=jeuvlCtA2lWKMssrAZc8vi9jxw3Ko09mNOVKW2Drdg5YvnEKi0mpCS/F1wZXz6rBEc KZeWs+9TbUWJy0JdorU43QppkMplWqaC4N1jO1pxxL14fiGyY9H59EHhRkhtMF4Z17m7 uz4Pkl/O0xARqlP1qzNHvw8nyqEGdnjfa3JeQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YlCpvEXGI04PWqrtZg5kx3HAvwKkcdmEW++9ZnycDcZA+wEbWgEEbCPryZnI5bLJr1 oHpyIUX2mbdPbmOBQCX7icItDNL1FQXCLDbe0C2WjSsaKF+YgRD/KWMCpQ9sBv/5s0wB d3anUrRufvZIRv2IyAlEctQa9AdiMqGgZhhdc= MIME-Version: 1.0 Received: by 10.224.113.15 with SMTP id y15mr1475946qap.270.1307318607625; Sun, 05 Jun 2011 17:03:27 -0700 (PDT) Received: by 10.224.80.130 with HTTP; Sun, 5 Jun 2011 17:03:27 -0700 (PDT) In-Reply-To: <4DEBDDB8.30001@snafu.de> References: <4DEBDDB8.30001@snafu.de> Date: Mon, 6 Jun 2011 08:03:27 +0800 Message-ID: From: wen heping To: joerg_surmann Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD_mailiglist_KERNEL , Freebsd_mailinglist_PORTS Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 00:32:38 -0000 This is a unresolved problem. Currently you can use "make CFLAGS+=3D-I/usr/local/include/pth -L/usr/local/lib/pth install" to install it. wen 2011/6/6 joerg_surmann : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi all, > > /usr/ports/textproc/py-libxml2# make install clean > =3D=3D=3D> =C2=A0Building for py27-libxml2-2.7.8_1 > Making all in . > gmake[1]: Entering directory > `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' > /bin/sh ../libtool --tag=3DCC =C2=A0 --mode=3Dlink cc =C2=A0-O2 -pipe > - -fno-strict-aliasing -std=3Dgnu89 -pedantic -W -Wformat -Wunused > - -Wimplicit -Wreturn-type -Wswitch -Wcomment -Wtrigraphs -Wformat > - -Wchar-subscripts -Wuninitialized -Wparentheses -Wshadow -Wpointer-arit= h > - -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes > - -Wmissing-prototypes -Wnested-externs -Winline -Wredundant-decls -modul= e > - -avoid-version =C2=A0-L/usr/local/lib -o libxml2mod.la -rpath > /usr/local/lib/python2.7/site-packages libxml.lo types.lo libxml2-py.lo > - -lxml2 =C2=A0 -L/usr/local/lib/python2.7/config -lpth -lutil -lm -lpyth= on2.7 > - -Wl,--export-dynamic > libtool: link: cc -shared =C2=A0.libs/libxml.o .libs/types.o > .libs/libxml2-py.o =C2=A0 -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath > - -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libxml2.so -lz > /usr/local/lib/libiconv.so -L/usr/local/lib/python2.7/config -lpth > - -lutil -lm -lpython2.7 =C2=A0-Wl,--export-dynamic =C2=A0 -Wl,-soname > - -Wl,libxml2mod.so -o .libs/libxml2mod.so > /usr/bin/ld: cannot find -lpth > gmake[1]: *** [libxml2mod.la] Fehler 1 > gmake[1]: Leaving directory > `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' > gmake: *** [all-recursive] Fehler 1 > *** Error code 1 > > Stop in /usr/ports/textproc/py-libxml2. > > > have anyone a idea? > > thanks > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.12 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk3r3bgACgkQcEHvP2uxrTPMEgCgwnHvxLeDCnSTmy5FuEW4hW/c > 3bUAnRVHz1vpfRvKq99fuPC3wp1zglRn > =3DQ6/i > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 05:37:59 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F364106566B; Mon, 6 Jun 2011 05:37:59 +0000 (UTC) (envelope-from joerg_surmann@snafu.de) Received: from waikiki.ops.eusc.inter.net (waikiki.ops.eusc.inter.net [84.23.254.155]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5FE8FC14; Mon, 6 Jun 2011 05:37:59 +0000 (UTC) X-Trace: 507c73757269697c38352e3137392e33392e3136307c3151545356682d30303042 61492d48417c31333037333338363737 Received: from waikiki.ops.eusc.inter.net ([10.155.10.19] helo=localhost) by waikiki.ops.eusc.inter.net with esmtpsa (Exim 4.72) id 1QTSVh-000BaI-HA; Mon, 06 Jun 2011 07:37:57 +0200 Message-ID: <4DEC67AA.3060500@snafu.de> Date: Mon, 06 Jun 2011 07:37:46 +0200 From: joerg_surmann User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: wen heping , FreeBSD_mailiglist_KERNEL , Freebsd_mailinglist_PORTS References: <4DEBDDB8.30001@snafu.de> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 85.179.39.160 X-SA-Exim-Mail-From: joerg_surmann@snafu.de X-SA-Exim-Scanned: No (on waikiki.ops.eusc.inter.net); SAEximRunCond expanded to false Cc: Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 05:37:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Wen, Thanks for your reply but it's the same issue: /usr/ports/textproc/py-libxml2# make CFLAGS+=-I/usr/local/include/pth-L/usr/local/lib/pth install ===> Building for py27-libxml2-2.7.8_1 Making all in . gmake[1]: Entering directory `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' /bin/sh ../libtool --tag=CC --mode=link cc - -I/usr/local/include/pth-L/usr/local/lib/pth - -I/usr/local/include/pth-L/usr/local/lib/pth -module -avoid-version - -L/usr/local/lib -o libxml2mod.la -rpath /usr/local/lib/python2.7/site-packages libxml.lo types.lo libxml2-py.lo - -lxml2 -L/usr/local/lib/python2.7/config -lpth -lutil -lm -lpython2.7 - -Wl,--export-dynamic libtool: link: cc -shared .libs/libxml.o .libs/types.o .libs/libxml2-py.o -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath - -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libxml2.so -lz /usr/local/lib/libiconv.so -L/usr/local/lib/python2.7/config -lpth - -lutil -lm -lpython2.7 -Wl,--export-dynamic -Wl,-soname - -Wl,libxml2mod.so -o .libs/libxml2mod.so /usr/bin/ld: cannot find -lpth gmake[1]: *** [libxml2mod.la] Fehler 1 gmake[1]: Leaving directory `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' gmake: *** [all-recursive] Fehler 1 *** Error code 1 You have a another idea? Thanks for help. Suri Am 06.06.11 02:03, schrieb wen heping: > This is a unresolved problem. > > Currently you can use "make CFLAGS+=-I/usr/local/include/pth > -L/usr/local/lib/pth install" to install it. > > wen > > 2011/6/6 joerg_surmann : > hi all, > > /usr/ports/textproc/py-libxml2# make install clean > ===> Building for py27-libxml2-2.7.8_1 > Making all in . > gmake[1]: Entering directory > `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' > /bin/sh ../libtool --tag=CC --mode=link cc -O2 -pipe > -fno-strict-aliasing -std=gnu89 -pedantic -W -Wformat -Wunused > -Wimplicit -Wreturn-type -Wswitch -Wcomment -Wtrigraphs -Wformat > -Wchar-subscripts -Wuninitialized -Wparentheses -Wshadow -Wpointer-arith > -Wcast-align -Wwrite-strings -Waggregate-return -Wstrict-prototypes > -Wmissing-prototypes -Wnested-externs -Winline -Wredundant-decls -module > -avoid-version -L/usr/local/lib -o libxml2mod.la -rpath > /usr/local/lib/python2.7/site-packages libxml.lo types.lo libxml2-py.lo > -lxml2 -L/usr/local/lib/python2.7/config -lpth -lutil -lm -lpython2.7 > -Wl,--export-dynamic > libtool: link: cc -shared .libs/libxml.o .libs/types.o > .libs/libxml2-py.o -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath > -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libxml2.so -lz > /usr/local/lib/libiconv.so -L/usr/local/lib/python2.7/config -lpth > -lutil -lm -lpython2.7 -Wl,--export-dynamic -Wl,-soname > -Wl,libxml2mod.so -o .libs/libxml2mod.so > /usr/bin/ld: cannot find -lpth > gmake[1]: *** [libxml2mod.la] Fehler 1 > gmake[1]: Leaving directory > `/usr/ports/textproc/py-libxml2/work/libxml2-2.7.8/python' > gmake: *** [all-recursive] Fehler 1 > *** Error code 1 > > Stop in /usr/ports/textproc/py-libxml2. > > > have anyone a idea? > > thanks _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> > _______________________________________________ > 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3sZ6oACgkQcEHvP2uxrTPg+gCfbm/FFp9csy3Fdn3uj54886JI M08AnRl6LOPU2hMB2RYvLkqJ6tLcyz7q =q0k+ -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 05:44:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AC6A1065670 for ; Mon, 6 Jun 2011 05:44:41 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 6091C8FC13 for ; Mon, 6 Jun 2011 05:44:41 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta08.emeryville.ca.mail.comcast.net with comcast id sViE1g0041GXsucA8VkfKP; Mon, 06 Jun 2011 05:44:39 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id sVkf1g00c1t3BNj8UVkf7q; Mon, 06 Jun 2011 05:44:40 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 717E3102C19; Sun, 5 Jun 2011 22:44:39 -0700 (PDT) Date: Sun, 5 Jun 2011 22:44:39 -0700 From: Jeremy Chadwick To: joerg_surmann Message-ID: <20110606054439.GA73301@icarus.home.lan> References: <4DEBDDB8.30001@snafu.de> <4DEC67AA.3060500@snafu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DEC67AA.3060500@snafu.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: wen heping , FreeBSD_mailiglist_KERNEL , Freebsd_mailinglist_PORTS Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 05:44:41 -0000 On Mon, Jun 06, 2011 at 07:37:46AM +0200, joerg_surmann wrote: > Thanks for your reply but it's the same issue: It appears you made a copy-paste typo. Look closely (missing whitespace): > /usr/ports/textproc/py-libxml2# make CFLAGS+=-I/usr/local/include/pth-L/usr/local/lib/pth install > ... I don't know if this will work, but what you want is: make CFLAGS+="-I/usr/local/include/pth -L/usr/local/lib/pth" install Also, this looks to be a freebsd-ports topic, not freebsd-stable. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 05:50:21 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53A791065679; Mon, 6 Jun 2011 05:50:21 +0000 (UTC) (envelope-from joerg_surmann@snafu.de) Received: from waikiki.ops.eusc.inter.net (waikiki.ops.eusc.inter.net [84.23.254.155]) by mx1.freebsd.org (Postfix) with ESMTP id 0261F8FC0A; Mon, 6 Jun 2011 05:50:20 +0000 (UTC) X-Trace: 507c73757269697c38352e3137392e33392e3136307c3151545368652d30303043 6a342d42797c31333037333339343138 Received: from waikiki.ops.eusc.inter.net ([10.155.10.19] helo=localhost) by waikiki.ops.eusc.inter.net with esmtpsa (Exim 4.72) id 1QTShe-000Cj4-By; Mon, 06 Jun 2011 07:50:18 +0200 Message-ID: <4DEC6A99.2020307@snafu.de> Date: Mon, 06 Jun 2011 07:50:17 +0200 From: joerg_surmann User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Jeremy Chadwick , Freebsd_mailinglist_PORTS , FreeBSD_mailiglist_KERNEL References: <4DEBDDB8.30001@snafu.de> <4DEC67AA.3060500@snafu.de> <20110606054439.GA73301@icarus.home.lan> In-Reply-To: <20110606054439.GA73301@icarus.home.lan> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 85.179.39.160 X-SA-Exim-Mail-From: joerg_surmann@snafu.de X-SA-Exim-Scanned: No (on waikiki.ops.eusc.inter.net); SAEximRunCond expanded to false Cc: Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 05:50:21 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 oh, i forgot the quotes. Yes it's work. Thanks Am 06.06.11 07:44, schrieb Jeremy Chadwick: > make CFLAGS+="-I/usr/local/include/pth -L/usr/local/lib/pth" install -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3sapkACgkQcEHvP2uxrTOzpACg4cxfJFIrXgjZmBYXgpYWYHYR fX8AoIo/56E+SPH4vHKfoG/jE4c31V/2 =LxfI -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 05:56:03 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8792106566C; Mon, 6 Jun 2011 05:56:03 +0000 (UTC) (envelope-from wenheping@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 566678FC08; Mon, 6 Jun 2011 05:56:02 +0000 (UTC) Received: by qwc9 with SMTP id 9so2111717qwc.13 for ; Sun, 05 Jun 2011 22:56:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=58QKHnevclfWw743ERTg+2y7H4Z10MLHBtdbCaqaCYw=; b=lclHkAGG9Qdf/Xy4pYXJN2Z/XMpwQYJiFjD0kbotRsTFHDQ1tUAqbYw+alu4wamsbI ufqtAvU6ytQ63bG8JcBnbuw+tC2/B64GlyskZf68y2zfgmlJGzu2vemPrZ9QNVCNRVDb aEf8n1VcxaGLiLq//eIYzSIr7uJMd0g7nOOMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YLeLaRxxT80T2vtnzEZ+ex8vHgyDTNlDyXPa34bNQWlFQvf+l3Hl67dNPSC+sjILQ1 nDYCSZrrxPtKQERV/vXGGDH28msEVnHd13YB5fsUAcelgMa44/zk+5dUdzBXxsEE7iPj J0vCddK46W4KVxTi5kMblJ0unU11/pVt1Y3MY= MIME-Version: 1.0 Received: by 10.224.214.136 with SMTP id ha8mr1613621qab.220.1307339762304; Sun, 05 Jun 2011 22:56:02 -0700 (PDT) Received: by 10.224.80.130 with HTTP; Sun, 5 Jun 2011 22:56:02 -0700 (PDT) In-Reply-To: <20110606054439.GA73301@icarus.home.lan> References: <4DEBDDB8.30001@snafu.de> <4DEC67AA.3060500@snafu.de> <20110606054439.GA73301@icarus.home.lan> Date: Mon, 6 Jun 2011 13:56:02 +0800 Message-ID: From: wen heping To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD_mailiglist_KERNEL , Freebsd_mailinglist_PORTS , joerg_surmann Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 05:56:03 -0000 try make CFLAGS+=3D-L/usr/local/lib/pth install still fail? then try: ln -s /usr/local/lib/pth/* /usr/local/lib/ wen 2011/6/6 Jeremy Chadwick : > On Mon, Jun 06, 2011 at 07:37:46AM +0200, joerg_surmann wrote: >> Thanks for your reply but it's the same issue: > > It appears you made a copy-paste typo. =C2=A0Look closely (missing > whitespace): > >> /usr/ports/textproc/py-libxml2# make CFLAGS+=3D-I/usr/local/include/pth-= L/usr/local/lib/pth install >> ... > > I don't know if this will work, but what you want is: > > make CFLAGS+=3D"-I/usr/local/include/pth -L/usr/local/lib/pth" install > > Also, this looks to be a freebsd-ports topic, not freebsd-stable. > > -- > | Jeremy Chadwick =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 jdc@parodiu= s.com | > | Parodius Networking =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://www.parodius.com/ | > | UNIX Systems Administrator =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 Mountain View, CA, US | > | Making life hard for others since 1977. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 PGP 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 06:07:22 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C7F71065670; Mon, 6 Jun 2011 06:07:22 +0000 (UTC) (envelope-from joerg_surmann@snafu.de) Received: from sour.ops.eusc.inter.net (sour.ops.eusc.inter.net [84.23.254.154]) by mx1.freebsd.org (Postfix) with ESMTP id DB71C8FC0A; Mon, 6 Jun 2011 06:07:21 +0000 (UTC) X-Trace: 507c73757269697c38352e3137392e33392e3136307c3151545379382d30303033 6a612d30787c31333037333430343430 Received: from sour.ops.eusc.inter.net ([10.154.10.19] helo=localhost) by sour.ops.eusc.inter.net with esmtpsa (Exim 4.72) id 1QTSy8-0003ja-0x; Mon, 06 Jun 2011 08:07:20 +0200 Message-ID: <4DEC6E95.4000606@snafu.de> Date: Mon, 06 Jun 2011 08:07:17 +0200 From: joerg_surmann User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: wen heping , FreeBSD_mailiglist_KERNEL , Freebsd_mailinglist_PORTS References: <4DEBDDB8.30001@snafu.de> <4DEC67AA.3060500@snafu.de> <20110606054439.GA73301@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 85.179.39.160 X-SA-Exim-Mail-From: joerg_surmann@snafu.de X-SA-Exim-Scanned: No (on sour.ops.eusc.inter.net); SAEximRunCond expanded to false Cc: Subject: Re: cannot install textproc/py-libxml2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 06:07:22 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Wen, sorry i forgot the quotes in command. make CFLAGS+="-I/usr/local/include/pth -L/usr/local/lib/pth" install works fine. Now i have next problem in multimedia/py-gstreamer: checking for libraries required to embed python... no configure: error: could not find Python lib ===> Script "configure" failed unexpectedly. Please report the problem to multimedia@FreeBSD.org [maintainer] and attach the "/usr/ports/multimedia/py-gstreamer/work/gst-python-0.10.21/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/multimedia/py-gstreamer. You have a idea? Thanks Suri Am 06.06.11 07:56, schrieb wen heping: > try > > make CFLAGS+=-L/usr/local/lib/pth install > > still fail? > > then try: > > ln -s /usr/local/lib/pth/* /usr/local/lib/ > > wen > > 2011/6/6 Jeremy Chadwick : >> On Mon, Jun 06, 2011 at 07:37:46AM +0200, joerg_surmann wrote: >>> Thanks for your reply but it's the same issue: >> >> It appears you made a copy-paste typo. Look closely (missing >> whitespace): >> >>> /usr/ports/textproc/py-libxml2# make CFLAGS+=-I/usr/local/include/pth-L/usr/local/lib/pth install >>> ... >> >> I don't know if this will work, but what you want is: >> >> make CFLAGS+="-I/usr/local/include/pth -L/usr/local/lib/pth" install >> >> Also, this looks to be a freebsd-ports topic, not freebsd-stable. >> >> -- >> | Jeremy Chadwick jdc@parodius.com | >> | Parodius Networking http://www.parodius.com/ | >> | UNIX Systems Administrator Mountain View, CA, US | >> | Making life hard for others since 1977. PGP 4BD6C0CB | >> >> > _______________________________________________ > 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" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3sbpUACgkQcEHvP2uxrTMJMQCggkX2l6nVaH5xFFKh8etSvUpJ 9MEAoIKinzuTPH5wed8HgDBKMy5vcLl5 =t6pc -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 10:53:15 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC8D5106566C; Mon, 6 Jun 2011 10:53:15 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 90E678FC0A; Mon, 6 Jun 2011 10:53:15 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id DDA09172B94; Mon, 6 Jun 2011 12:53:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vINgTtvpvdv7; Mon, 6 Jun 2011 12:53:12 +0200 (CEST) Received: from [10.0.3.160] (188-167-50-235.dynamic.chello.sk [188.167.50.235]) by mail.vx.sk (Postfix) with ESMTPSA id 9080F172B8C; Mon, 6 Jun 2011 12:53:12 +0200 (CEST) Message-ID: <4DECB197.8020102@FreeBSD.org> Date: Mon, 06 Jun 2011 12:53:11 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org, freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 10:53:15 -0000 Hi, I have merged ZFS version 28 to 8-STABLE (revision 222741) New major features: - data deduplication - triple parity RAIDZ (RAIDZ3) - zfs diff - zpool split - snapshot holds - zpool import -F. Allows to rewind corrupted pool to earlier transaction group - possibility to import pool in read-only mode For updating, there is a compatibility layer so that in the update phase most functionality of the new zfs binaries can be used with the old kernel module and old zfs binaries with the new kernel module. If upgrading your boot pool to version 28, please don't forget to read UPDATING and properly update your boot code. Thanks to everyone working on the ZFS port, especially to Pawel Jakub Dawidek (pjd) for doing most of the work! -- Martin Matuska FreeBSD committer http://blog.vx.sk From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 12:57:08 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9690F106564A for ; Mon, 6 Jun 2011 12:57:08 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 7F22D8FC12 for ; Mon, 6 Jun 2011 12:57:08 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta14.emeryville.ca.mail.comcast.net with comcast id scg91g0020lTkoCAEcx7BF; Mon, 06 Jun 2011 12:57:07 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta04.emeryville.ca.mail.comcast.net with comcast id scx61g00Q1t3BNj8Qcx6hC; Mon, 06 Jun 2011 12:57:06 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 02621102C36; Mon, 6 Jun 2011 05:57:07 -0700 (PDT) Date: Mon, 6 Jun 2011 05:57:06 -0700 From: Jeremy Chadwick To: Martin Matuska Message-ID: <20110606125706.GA2047@icarus.home.lan> References: <4DECB197.8020102@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DECB197.8020102@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 12:57:08 -0000 On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) > > New major features: > > - data deduplication > - triple parity RAIDZ (RAIDZ3) > - zfs diff > - zpool split > - snapshot holds > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group > - possibility to import pool in read-only mode > > For updating, there is a compatibility layer so that in the update phase > most functionality of the new zfs binaries can be used with the old > kernel module and old zfs binaries with the new kernel module. > > If upgrading your boot pool to version 28, please don't forget to read > UPDATING and properly update your boot code. > > Thanks to everyone working on the ZFS port, especially to > Pawel Jakub Dawidek (pjd) for doing most of the work! Thanks for the work on this, guys! I've already managed to find something odd. This message only appears on console, not via pty/tty. icarus# zpool create backups ada2 Solaris(cont): !created version 28 pool backups using 28 src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_history.c contains: 490 void 491 spa_history_log_version(spa_t *spa, history_internal_events_t event) 492 { 493 #ifdef _KERNEL 494 uint64_t current_vers = spa_version(spa); 495 496 if (current_vers >= SPA_VERSION_ZPOOL_HISTORY) { 497 spa_history_log_internal(event, spa, NULL, 498 "pool spa %llu; zfs spa %llu; zpl %d; uts %s %s %s %s", 499 (u_longlong_t)current_vers, SPA_VERSION, ZPL_VERSION, 500 utsname.nodename, utsname.release, utsname.version, 501 utsname.machine); 502 } 503 cmn_err(CE_CONT, "!%s version %llu pool %s using %llu", 504 event == LOG_POOL_IMPORT ? "imported" : 505 event == LOG_POOL_CREATE ? "created" : "accessed", 506 (u_longlong_t)current_vers, spa_name(spa), SPA_VERSION); 507 #endif 508 } A "zpool destroy", etc. does not print any similar message. It only happens on pool creation. Is this intentional behaviour? What does "Solaris(cont)" represent in the context of FreeBSD? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 14:16:17 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24C43106564A for ; Mon, 6 Jun 2011 14:16:17 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7FDFB8FC12 for ; Mon, 6 Jun 2011 14:16:16 +0000 (UTC) Received: (qmail 62440 invoked from network); 6 Jun 2011 13:49:34 -0000 Received: from unknown (HELO ?10.50.50.207?) (spawk@64.147.100.2) by acm.poly.edu with CAMELLIA256-SHA encrypted SMTP; 6 Jun 2011 13:49:34 -0000 Message-ID: <4DECDB22.7000809@acm.poly.edu> Date: Mon, 06 Jun 2011 09:50:26 -0400 From: Boris Kochergin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110408 Thunderbird/3.1.9 MIME-Version: 1.0 To: Martin Matuska References: <4DECB197.8020102@FreeBSD.org> In-Reply-To: <4DECB197.8020102@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 14:16:17 -0000 On 06/06/11 06:53, Martin Matuska wrote: > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) > > New major features: > > - data deduplication > - triple parity RAIDZ (RAIDZ3) > - zfs diff > - zpool split > - snapshot holds > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group > - possibility to import pool in read-only mode > > For updating, there is a compatibility layer so that in the update phase > most functionality of the new zfs binaries can be used with the old > kernel module and old zfs binaries with the new kernel module. > > If upgrading your boot pool to version 28, please don't forget to read > UPDATING and properly update your boot code. > > Thanks to everyone working on the ZFS port, especially to > Pawel Jakub Dawidek (pjd) for doing most of the work! > Thanks for everyone's hard work (and the __FreeBSD_version bump!). -Boris From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 14:39:01 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8C33106566B for ; Mon, 6 Jun 2011 14:39:01 +0000 (UTC) (envelope-from laa@cemu.ru) Received: from m.cemu.ru (m.cemu.ru [194.186.216.68]) by mx1.freebsd.org (Postfix) with ESMTP id 9FEA88FC14 for ; Mon, 6 Jun 2011 14:39:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=laa.zp.ua; s=dkim; h=Sender:In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=hCrmCLtWP+TiIvJkk1o53WwyQleIp1ZZyLG0iKv8nF0=; b=dLjX35ipBnuMNzh0ougzBoN1feiG2NbWAl4rFz52EP+mZ7oLnJ27SMYlokDxvteY8qbw2b2rZCKGASJyUjhaZ/4AmZyUvKj/+Ljkvq1MVoGIGzaS4RdE9RtGNDWg+l+VIfsVPQp2/xkOXyxrHkCSLQReDXzlOWxAVfPxq8Z9+7s=; Received: by m.cemu.ru with local (Exim) (envelope-from ) id 1QTaxH-000M7X-Dk for freebsd-stable@FreeBSD.org; Mon, 06 Jun 2011 18:38:59 +0400 Date: Mon, 6 Jun 2011 18:38:59 +0400 From: Lystopad Olexandr To: freebsd-stable@FreeBSD.org Message-ID: <20110606143859.GA74833@laa.zp.ua> References: <4DECB197.8020102@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4DECB197.8020102@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Sender: laa Cc: Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 14:39:02 -0000 Hello, Martin Matuska! On Mon, Jun 06, 2011 at 12:53:11PM +0200 mm@FreeBSD.org wrote about "HEADS UP: ZFS v28 merged to 8-STABLE": > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) finally! Thanks! My home server works ok with this update. -- Lystopad Olexandr From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 14:46:58 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31A131065674 for ; Mon, 6 Jun 2011 14:46:58 +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 DBD2A8FC13 for ; Mon, 6 Jun 2011 14:46:57 +0000 (UTC) Received: by equilibrium.bsdes.net (Postfix, from userid 1001) id B22C639836; Mon, 6 Jun 2011 16:46:55 +0200 (CEST) Date: Mon, 6 Jun 2011 16:46:55 +0200 From: Victor Balada Diaz To: stable@freebsd.org Message-ID: <20110606144655.GG6624@equilibrium.bsdes.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Subject: Unusable hastd in FreeBSD 8.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 14:46:58 -0000 Hello, Hastd in it's current form is not usable on FreeBSD 8.2-RELEASE or in 8-STABLE. You can see why in this thread: http://lists.freebsd.org/pipermail/freebsd-fs/2011-February/010752.html You can see the committed fix in: http://svnweb.freebsd.org/base?view=revision&revision=219721 But it's never been MFCd. Is it possible to MFC it to 8-STABLE and maybe do an errata notice for RELENG_8_2? Thanks a lot. Regards. -- La prueba ms fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 6 19:37:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B34B61065673 for ; Mon, 6 Jun 2011 19:37:05 +0000 (UTC) (envelope-from lichray@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3AF8FC0A for ; Mon, 6 Jun 2011 19:37:04 +0000 (UTC) Received: by fxm11 with SMTP id 11so3952345fxm.13 for ; Mon, 06 Jun 2011 12:37:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VOFs5OSUtOtHgGg2vE7cJTz5b+OJi8XtV7WW6GSmpvg=; b=wK99qJPRnbwVAe4BpWVIpD5h/1mxN9s4EOdBpDTWk8U6jDbomYG1gS5gTuI/A14Mbs GCRj4maJ+VPSWXF7PX6H1OQl9+Z36sTnjTIzVA4Fa2U54yDPNhc5tKzvEGqhE9Em5TG/ bJeGjd5hAhRF2pHxqL9PZvYezo5Go+z/g4R/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LuAR1D4kMPOffz+RYG73lF3pi0TrGQ6kqWVKYm9NT7vTMxebfCBGkrZ5cObdH3fBTp IPkCJNCzHQGMk+eMgBqiRpTPGqywiFKmDA1eOk1S5cpiabdt1gY3GBGuGzfVeDV7cAe4 G6Pu7qGdQXhOtRSV1Ttq3JiMHBWH9drlQ7DPI= MIME-Version: 1.0 Received: by 10.223.55.27 with SMTP id s27mr3543771fag.121.1307389023505; Mon, 06 Jun 2011 12:37:03 -0700 (PDT) Received: by 10.223.72.13 with HTTP; Mon, 6 Jun 2011 12:37:03 -0700 (PDT) In-Reply-To: <20110606143859.GA74833@laa.zp.ua> References: <4DECB197.8020102@FreeBSD.org> <20110606143859.GA74833@laa.zp.ua> Date: Mon, 6 Jun 2011 14:37:03 -0500 Message-ID: From: Zhihao Yuan To: Lystopad Olexandr Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 19:37:05 -0000 Thanks. Everything works fine. 2011/6/6 Lystopad Olexandr : > =C2=A0Hello, Martin Matuska! > > On Mon, Jun 06, 2011 at 12:53:11PM +0200 > mm@FreeBSD.org wrote about "HEADS UP: ZFS v28 merged to 8-STABLE": >> Hi, >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) > > finally! Thanks! > > My home server works ok with this update. > > -- > =C2=A0Lystopad Olexandr > _______________________________________________ > 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" > --=20 Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___________________________________________________ 4BSD -- http://4bsd.biz/ From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 04:33:07 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B17F0106564A for ; Tue, 7 Jun 2011 04:33:07 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [69.163.100.197]) by mx1.freebsd.org (Postfix) with ESMTP id 7D97F8FC12 for ; Tue, 7 Jun 2011 04:33:07 +0000 (UTC) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.4/8.14.1) with ESMTP id p572XIgG056330; Mon, 6 Jun 2011 19:33:18 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.4/8.13.4/Submit) id p572XI8T056329; Mon, 6 Jun 2011 19:33:18 -0700 (PDT) Date: Mon, 6 Jun 2011 19:33:18 -0700 (PDT) From: Matthew Dillon Message-Id: <201106070233.p572XI8T056329@apollo.backplane.com> To: Matt Thyer References: Cc: stable@freebsd.org Subject: Re: PCIe SATA HBA for ZFS on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 04:33:07 -0000 :I'm not on the -STABLE list so please reply to me. : :I'm using an Intel Core i3-530 on a Gigabyte H55M-D2H motherboard with 8 x :2TB drives & 2 x 1TB drives. :The plan is to have the 1 TB drives in a zmirror and the 8 in a raidz2. : :Now the Intel chipset has only 6 on board SATA II ports so ideally I'm :looking for a non RAID SATA II HBA to give me 6 extra ports (4 min). :Why 6 extra ? :Well the case I'm using has 2 x eSATA ports so 6 would be ideal, 5 OK, and 4 :the minimum I need to do the job. : :So... : :What do people recommend for 8-STABLE as a PCIe SATA II HBA for someone :using ZFS ? : :Not wanting to break the bank. :Not interested in SATA III 6GB at this time... though it could be useful if :I add an SSD for... (is it ZIL ?). :Can this be added at any time ? : :The main issue is I need at least 10 ports total for all existing drives... :ZIL would require 11 so ideally we are talking a 6 port HBA. The absolute cheapest solution is to buy a Sil-3132 PCIe card (providing 2 E-SATA ports), and then connect an external port multiplier to each port. External port multiplier enclosures typically support 5 drives each so that would give you your 10 drives. Even the 3132 is a piss-ant little card it does support FIS-Based switching so performance will be very good... it will just be limited to SATA-II speeds is all. Motherboard AHCI-based SATA ports typically do NOT have FIS-Based switching support (this would be the FBSS capability flag when the AHCI driver probes the chipset). This means that while you can attach an external port multiplier enclosure to mobo SATA ports (see later on E-SATA vs SATA), read performance from multiple drives concurrently will be horrible. Write performance will still be decent due to drive write caches despite being serialized. On E-SATA vs SATA. Essentially there are only two differences between E-SATA and SATA. One is the cable and connector format. The other is hot swap detection. Most mobo SATA ports can be strung out to E-SATA with an appropriate adapter. High-end Intel ASUS mobos often come with such adapters (this is why they usually don't sport an actual E-Sata port on the backplane) and the BIOS has setup features to specify E-SATA on a port-by-port basis. -- For SSDs you want to directly connect the SSD to a mobo SATA port and then either mount the SSD in the case or mount it in a hot-swap gadget that you can screw into a PCI slot (it doesn't actually use the PCI connector, just the slot). A SATA-III port with a SATA-III SSD really shines here and 400-500 MBytes/sec random read performance from a single SSD is possible, but it isn't an absolute requirement. A SATA-II port will still work fine as long as you don't mind maxing out the bandwidth at 250 MBytes/sec. -- I can't help with any of the other questions. Someone also suggested the MPS driver for FreeBSD, with caveats. I'll add a caveat on the port multiplier enclosures. Nearly all such enclosures use another SIL chipset internally and it works pretty well EXCEPT that it isn't 100% dependable if you try to hot-swap drives in the enclosure while other drives in the enclosure are active. So with that caveat, I recommend the port multiplier enclosure as the cheapest solution. To get robust hot-swap enclosures you either need to go with SAS or you need to go with discrete SATA ports (no port multiplication), and the ports have to support hot-swap. The best hot-swap support for an AHCI port is if the AHCI chipset supports cold-presence-detect (CPD), and again Mobo AHCI chipsets usually don't. Hot-swap is a bit hit or miss without CPD because power savings modes can effectively prevent hot-swap detect from working properly. Drive disconnects will always be detected but drive connects might not be. And even with discrete SATA ports the AHCI firmware on mobos does not necessarily handle hot-swap properly. For example my Intel-I7 ASUS mobo will generate spurious interrupts and status on a DIFFERENT discrete SATA port when I hot swap on some other discrete SATA port, in addition to generating the status interrupt on the correct port. So then it comes down to the driver in the operating system properly handling the spurious status and properly stopping and restarting pending commands when necessary. So, again, it is best for the machine to be idle before attempting a hot-swap. Lots of caveats. Sorry... you can blame Intel for all the blasted issues with AHCI and SATA. Intel didn't produce a very good chipset spec and vendors took all sorts of liberties. -Matt Matthew Dillon From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 06:07:11 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E46B3106564A; Tue, 7 Jun 2011 06:07:11 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7B73A8FC16; Tue, 7 Jun 2011 06:07:11 +0000 (UTC) Received: by iyj12 with SMTP id 12so5673938iyj.13 for ; Mon, 06 Jun 2011 23:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :reply-to:references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=qYoGzsrFF+aV+FKWIvpyztwB5nnBcsEfC2SSy7ZQetw=; b=XWCPfW13SQjV7AR++3HuzbIcg8tHoRvneruWxdBg7y+kGAjapIUEFVR4ji+BvgFSpl JlNBpQVMYlRgTg+jb5Z6u3Y8YVWROSW4IO9bfp8P7WiZD43ZSfhgD1NvoxWeRJu+U//Z WnuYjX9/UKcFHr2WwT0lEdq+5iO3joSMuVHzU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :x-openpgp-key-id:x-openpgp-key-fingerprint:x-openpgp-key-url; b=dlppni1s8A1B+7It9hsnLmwFSAEhW3tUHp5PCxpWEaMCZybpdE5WC5HdmV949EIGo+ cZSljpDj3Evn4nTRGSc46sd8X3zciCGRdh2h6SdF1UtnPynhsfpcFvwahKcv9z/IoloC L25YyDdsCFUSZUXc0covBV8d3SusXJ+3FffiA= Received: by 10.43.55.84 with SMTP id vx20mr9209732icb.49.1307426830760; Mon, 06 Jun 2011 23:07:10 -0700 (PDT) Received: from DataIX.net (adsl-99-19-42-166.dsl.klmzmi.sbcglobal.net [99.19.42.166]) by mx.google.com with ESMTPS id ex14sm3382644icb.13.2011.06.06.23.07.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Jun 2011 23:07:09 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p576744m012959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jun 2011 02:07:05 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p57673nN012958; Tue, 7 Jun 2011 02:07:03 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Tue, 7 Jun 2011 02:07:03 -0400 From: Jason Hellenthal To: Jeremy Chadwick Message-ID: <20110607060703.GA80203@DataIX.net> References: <4DECB197.8020102@FreeBSD.org> <20110606125706.GA2047@icarus.home.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20110606125706.GA2047@icarus.home.lan> X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Martin Matuska Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jhell@DataIX.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 06:07:12 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jeremy, On Mon, Jun 06, 2011 at 05:57:06AM -0700, Jeremy Chadwick wrote: > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > > Hi, > >=20 > > I have merged ZFS version 28 to 8-STABLE (revision 222741) > >=20 > > New major features: > >=20 > > - data deduplication > > - triple parity RAIDZ (RAIDZ3) > > - zfs diff > > - zpool split > > - snapshot holds > > - zpool import -F. Allows to rewind corrupted pool to earlier > > transaction group > > - possibility to import pool in read-only mode > >=20 > > For updating, there is a compatibility layer so that in the update phase > > most functionality of the new zfs binaries can be used with the old > > kernel module and old zfs binaries with the new kernel module. > >=20 > > If upgrading your boot pool to version 28, please don't forget to read > > UPDATING and properly update your boot code. > >=20 > > Thanks to everyone working on the ZFS port, especially to > > Pawel Jakub Dawidek (pjd) for doing most of the work! >=20 > Thanks for the work on this, guys! >=20 > I've already managed to find something odd. This message only appears > on console, not via pty/tty. >=20 > icarus# zpool create backups ada2 > Solaris(cont): !created version 28 pool backups using 28 >=20 > src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_history.c > contains: >=20 > 490 void > 491 spa_history_log_version(spa_t *spa, history_internal_events_t event) > 492 { > 493 #ifdef _KERNEL > 494 uint64_t current_vers =3D spa_version(spa); > 495 > 496 if (current_vers >=3D SPA_VERSION_ZPOOL_HISTORY) { > 497 spa_history_log_internal(event, spa, NULL, > 498 "pool spa %llu; zfs spa %llu; zpl %d; uts %s %s %= s %s", > 499 (u_longlong_t)current_vers, SPA_VERSION, ZPL_VERS= ION, > 500 utsname.nodename, utsname.release, utsname.versio= n, > 501 utsname.machine); > 502 } > 503 cmn_err(CE_CONT, "!%s version %llu pool %s using %llu", > 504 event =3D=3D LOG_POOL_IMPORT ? "imported" : > 505 event =3D=3D LOG_POOL_CREATE ? "created" : "accessed", > 506 (u_longlong_t)current_vers, spa_name(spa), SPA_VERSION); > 507 #endif > 508 } >=20 > A "zpool destroy", etc. does not print any similar message. It only > happens on pool creation. Is this intentional behaviour? What does > "Solaris(cont)" represent in the context of FreeBSD? Nothing other than a line in-difference that someone does not have to track from import/merge's. The smaller the diff's the better ;) Would be nice to trap this at some other point so it doesnt have to be displayed or changed through the whole structure of files. /me is waiting for the next big move... ;) Cheers to all the ZFS folks out there! --=20 "Unity can only be manifested by the Binary. Unity itself and the idea of U= nity are already two." -- Buddha Regards, (jhell) Jason Hellenthal --FCuugMFkClbJLl1L Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJN7cAGAAoJEJBXh4mJ2FR++24H/RzuViZWlwcpw0EkQE0WaSGu x1+LJZKHMTOWUgC+vcxKijLOjdqp+7x7HJJ/mzsPan3McZEsH3zVAqxKl666TYhu p8MSXX/AzR5d+OKQ+J7J/8/SR/ohvUhDp/v9UkFae6xPRkHNprZGJ1EgJDXl+of/ gR+fdZv9VkbhwFFvN30fiyetdllFkwV3KSlpH7KWu3gceRmipIqT8w/CNKll9jKj 9WRYe3UiVppFSkqg2GCr/lorSjuDka5X/6C4fHM7v0Q9ytfqcIoKEducDdnWM4Ue sCdBflZCdx7CaHFkX4UCI/PKwaKYbQCZEdfLRZ8upki0PI+J8kyEGq19OY7JcV8= =WzWw -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 08:35:58 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB4E01065670 for ; Tue, 7 Jun 2011 08:35:58 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 34A8F8FC14 for ; Tue, 7 Jun 2011 08:35:57 +0000 (UTC) Received: by fxm11 with SMTP id 11so4367166fxm.13 for ; Tue, 07 Jun 2011 01:35:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rc+p5trwSJ8csOsS3h1PqrppqEiehGP2FpL3mFDXIWk=; b=N0v6UWc/UzoY7uSvMEwLj1yJzGD4Pct5V6+BvzEw+XNAAge0zAp31ZMPjCRPYpPqE9 Gz6aDCdxxn4kiFSot/m9r05uwNSXkEPfL6SeVPJfDtQ4ayWp9BISndkpdyXNjncKKlHq waLBZgD8AY3vbzNMG5nuuZwV5Fy2fX9Y5hLv4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ba0Ws1a9HI3ejd/mMm3m9dnuSUvr9Hh8TVHqei/E1zqTL82LpNHP6KLcbe7/1rzmT5 e8bu2jUNF11H9xeewDWlVrr3vom0AVpINKnM/vevOqX65mC00CDDVbIiR2qHeMIPzXKg QdAQLjU1YT379PJFpnWz4SL93Qb6qDUKPp5bs= Received: by 10.223.57.5 with SMTP id a5mr3642506fah.90.1307435757009; Tue, 07 Jun 2011 01:35:57 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id e16sm1627599fak.41.2011.06.07.01.35.55 (version=SSLv3 cipher=OTHER); Tue, 07 Jun 2011 01:35:56 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DEDE2E5.6080406@FreeBSD.org> Date: Tue, 07 Jun 2011 11:35:49 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110310 Thunderbird/3.1.9 MIME-Version: 1.0 To: FreeBSD Stable References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PCIe SATA HBA for ZFS on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 08:35:58 -0000 On 07.06.2011 05:33, Matthew Dillon wrote: > The absolute cheapest solution is to buy a Sil-3132 PCIe card > (providing 2 E-SATA ports), and then connect an external port multiplier > to each port. External port multiplier enclosures typically support > 5 drives each so that would give you your 10 drives. > > Even the 3132 is a piss-ant little card it does support FIS-Based > switching so performance will be very good... it will just be limited > to SATA-II speeds is all. SiI3132 is indeed good for it's price and it is quite good for random I/O. But at burst speeds it is limited lower then SATA-II. Even lower then PCIe 1.0 x1 it uses. IIRC I've seen about 150MB/s from one port and about 170MB/s from two. If burst rate is important, SiI3124 chip is much better -- up to about 900MB/s measured from 4 ports. The only issue is PCI-X interface: either motherboard with PCI-X needed, or card with PCIe x8 bridge (like these http://www.addonics.com/products/host_controller/adsa3gpx8-4e.asp), but last case is too expensive. There are also much cheaper (~$50) PCIe x1 bridge SiI3124 cards (http://www.sybausa.com/productInfo.php?iid=537). They are not so fast -- about 200MB/s, but still more then SiI3132. And they still have 4 SATA ports. > For SSDs you want to directly connect the SSD to a mobo SATA port and > then either mount the SSD in the case or mount it in a hot-swap gadget > that you can screw into a PCI slot (it doesn't actually use the PCI > connector, just the slot). A SATA-III port with a SATA-III SSD really > shines here and 400-500 MBytes/sec random read performance from a single > SSD is possible, but it isn't an absolute requirement. A SATA-II port > will still work fine as long as you don't mind maxing out the bandwidth > at 250 MBytes/sec. Agree. Intel on-board ports rock! Recently I've built new system with two OCZ Vertex 3 SSDs connected to 6Gbps SATA ports on Intel Sandy Bridge class motherboard. UFS on top of graid RAID0 volume gives me about 950MB/s on both read and write! > To get robust hot-swap enclosures you either need to go with SAS or you > need to go with discrete SATA ports (no port multiplication), and the > ports have to support hot-swap. The best hot-swap support for an AHCI > port is if the AHCI chipset supports cold-presence-detect (CPD), and > again Mobo AHCI chipsets usually don't. Hot-swap is a bit hit or miss > without CPD because power savings modes can effectively prevent hot-swap > detect from working properly. Drive disconnects will always be detected > but drive connects might not be. I would say it depends. In some cases it is easier to detect hot-plug then hot-unplug, as device sends COMINIT that should wake up port even from power-save state. With ICH10, for example, I've managed to make both hot plug and unplug work even with power-management enabled: hot-plug via tracking COMINIT, unplug via it's CPD capability. Without PM it "just works". :) -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 14:14:33 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 081D8106566C; Tue, 7 Jun 2011 14:14: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 B939C8FC15; Tue, 7 Jun 2011 14:14: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 RAA23855; Tue, 07 Jun 2011 17:14:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DEE3245.5030708@FreeBSD.org> Date: Tue, 07 Jun 2011 17:14:29 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Attilio Rao References: <4DE8FA2E.4030202@FreeBSD.org> <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> <4DE9EB61.3000006@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org, "Robert N. M. Watson" Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 14:14:33 -0000 on 05/06/2011 01:35 Attilio Rao said the following: > 2011/6/4 Andriy Gapon : >> commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016 >> >> generic_stop_cpus: move timeout detection code from under DIAGNOSTIC >> >> ... and also increase it a bit. >> IMO it's better to detect and report the (rather serious) condition and >> allow a system to proceed somehow rather than be stuck in an endless >> loop. >> >> diff --git a/sys/kern/subr_smp.c b/sys/kern/subr_smp.c >> index ae52f4b..4bd766b 100644 >> --- a/sys/kern/subr_smp.c >> +++ b/sys/kern/subr_smp.c >> @@ -232,12 +232,10 @@ generic_stop_cpus(cpumask_t map, u_int type) >> /* spin */ >> cpu_spinwait(); >> i++; >> -#ifdef DIAGNOSTIC >> - if (i == 100000) { >> + if (i == 100000000) { >> printf("timeout stopping cpus\n"); >> break; >> } >> -#endif >> } >> >> stopping_cpu = NOCPU; > > I'd also add the ability, once the deadlock is detected, to break in > KDB, and put that under DIAGNOSTIC. > I had such a patch and I used it to debug some deadlocks on shutdown > code, but now it seems I can't find it anymore. I think that this could be useful. Of course, it would have to honor KDB_UNATTENDED. However, I am not sure how to implement it safely. E.g. panic() should stop other CPUs before setting panicstr and if some CPU is stuck for good, then we would just be recursively calling panic() until triple-fault. Ditto for kdb_trap(). So if you could dig up your code for implementing this that would be useful. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Tue Jun 7 14:20:34 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F4171065670; Tue, 7 Jun 2011 14:20:34 +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 2D4CE8FC16; Tue, 7 Jun 2011 14:20:32 +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 RAA24026; Tue, 07 Jun 2011 17:20:31 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DEE33AF.5090100@FreeBSD.org> Date: Tue, 07 Jun 2011 17:20:31 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Robert N. M. Watson" References: <4DE8FA2E.4030202@FreeBSD.org> <5E4D0F56-4338-4157-8BC6-17EE2831725F@FreeBSD.org> <4DE9EB61.3000006@FreeBSD.org> <8AA26086-DA05-4DDA-9973-AE57328E2C81@FreeBSD.org> In-Reply-To: <8AA26086-DA05-4DDA-9973-AE57328E2C81@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: [poll / rfc] kdb_stop_cpus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2011 14:20:34 -0000 on 04/06/2011 12:11 Robert N. M. Watson said the following: > > On 4 Jun 2011, at 09:22, Andriy Gapon wrote: >> commit 458ebd9aca7e91fc6e0825c727c7220ab9f61016 >> >> generic_stop_cpus: move timeout detection code from under DIAGNOSTIC >> >> ... and also increase it a bit. IMO it's better to detect and report the >> (rather serious) condition and allow a system to proceed somehow rather than >> be stuck in an endless loop. > > Agreed on detecting and reporting. It would be good to confirm that it works in > practice, however, What is your concern here? :) The code seems rather simple - the loop is no longer infinite. > and also that there are no false positives. I'm not sure > what the best test scenarios are for that. As to the false positives - I think that that can only be verified by practice (very wide testing), because that would greatly depend on hardware. Maybe we should use some time-based approach instead of the iteration count approach or maybe we should calibrate the iteration count based on hardware characteristics... -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 11:25:52 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C2221065670 for ; Wed, 8 Jun 2011 11:25:52 +0000 (UTC) (envelope-from matt.thyer@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id CEBB68FC13 for ; Wed, 8 Jun 2011 11:25:51 +0000 (UTC) Received: by wwc33 with SMTP id 33so414355wwc.31 for ; Wed, 08 Jun 2011 04:25:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7ZKCoTLN2u8m5aiu51nEjoGfApwHp31dOux+/ezsgS0=; b=AZ8BLjyKFiku6zcH0d8r6QRYygxyNAmMtxAkEywglF/+rD5feJ6Lw4XEBOImfn1SQf gLuXkH1fm/OQLdtp0Jkk3XC/B10G84fcqwHG75ltEAOh0o9KphRVH6g3bpY+0MB2309C 1SFwfx6dAePaLE6mShw+g/eDa399E+p+jyBC8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=t9duH33CHqJfjn1Sfa8TgQGchPcc9zXWqvNeZ0/vIfE8/drcoJEU/nqMLx9o5knvDV WhizPSoj8xiT8pM9hwf0yMaghJZ/xoWZ/MyMdRiTmfWMGjrQ/99ukAbKie6qDv65iDcA zhXVq4OLh+CRc87pdkkwcT5gLUEx0HFUW35bU= MIME-Version: 1.0 Received: by 10.216.239.67 with SMTP id b45mr4968628wer.44.1307532350667; Wed, 08 Jun 2011 04:25:50 -0700 (PDT) Received: by 10.216.54.67 with HTTP; Wed, 8 Jun 2011 04:25:50 -0700 (PDT) In-Reply-To: <201106070233.p572XI8T056329@apollo.backplane.com> References: <201106070233.p572XI8T056329@apollo.backplane.com> Date: Wed, 8 Jun 2011 20:55:50 +0930 Message-ID: From: Matt Thyer To: Matthew Dillon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: stable@freebsd.org Subject: Re: PCIe SATA HBA for ZFS on -STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 11:25:52 -0000 On 7 June 2011 12:03, Matthew Dillon wrote: > The absolute cheapest solution is to buy a Sil-3132 PCIe card > (providing 2 E-SATA ports), and then connect an external port multiplier > to each port. External port multiplier enclosures typically support > 5 drives each so that would give you your 10 drives. > I've decided to avoid issues with port multiplication by going for a Supermicro AOC-USAS2-L8i and then to flash it to IT (as opposed to IR) mode to make it run as a standard non-RAID HBA. As I've got 8 x 2 TB drives for the ZFS raidz2 I'll put them all on the AOC-USAS2-L8i and save my onboard SATA-II ports for my 2 x 1TB drives for the FreeBSD O.S. and any eSATA use. Now the only remaining issue is whether to go with the Supermicro firmware or the generic Lsi Logic firmware as some have reported better performance with the version 9 Lsi Logic firmware. I'll report on my experiences (as I keep a record of the revision of my -STABLE build this should actually be useful!). From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 12:17:54 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5421106566B; Wed, 8 Jun 2011 12:17:54 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 911AD8FC16; Wed, 8 Jun 2011 12:17:54 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC41CD9.dip.t-dialin.net [79.196.28.217]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id D3AB6844015; Wed, 8 Jun 2011 14:01:13 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 297F73B04; Wed, 8 Jun 2011 14:01:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1307534471; bh=a1ZfEbWOnVgZalSaPJT6XOcFsG2Uk4KcRFqljkbZRnI=; h=Message-ID:Date:From:To:Cc:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding; b=XS/qryOFwTY+Pm4kBwObCNLc73eFgypsLWduuubuT/ENocO3HXDEYasYcY2GZMnfp T4JbWdIw0kogZmw1WHnfCstZBqjoK9aGoAUyNavsMzBUgx/MhjLZnYjNsnAbYFXcFM JpYyIXYLJH4qceXum1YFwrEsB5Qw2iS96tn8Vee4wgj8khJGTUJkX2zBCHGZhjlzr7 WGOBvyrB0HW/iYASfdDdLHo2iZjBatmxI0NEakNUYP5yG4uK1/E4RfKzJEvrm3YmqA W/khd/I0JuQWsF/YeDNoAkPQoyui9PoDU//I0Rzy3AKwwoBt9drepabh/n8PrXG76T XFtjWqJ3kVutA== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p58C1Ala074646; Wed, 8 Jun 2011 14:01:10 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 08 Jun 2011 14:01:10 +0200 Message-ID: <20110608140110.18986ku70sxmm07a@webmail.leidinger.net> Date: Wed, 08 Jun 2011 14:01:10 +0200 From: Alexander Leidinger To: emulation@FreeBSD.org, stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: D3AB6844015.A001A X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.1, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1308139274.29096@TI7E8YeadcDJOw/pI++e5Q X-EBL-Spam-Status: No Cc: nox@FreeBSD.org Subject: v4l2 8-stable MFC: testers needed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 12:17:55 -0000 Hi, at http://www.Leidinger.net/test/v4l2-stable8.diff I have the v4l2 code I want to commit to 8-stable. Can someone please compile it, test it and give feedback? Bye, Alexander. -- "How many people work here?" "Oh, about half." http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 12:30:14 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52DF7106566B; Wed, 8 Jun 2011 12:30:14 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A31738FC0C; Wed, 8 Jun 2011 12:30:13 +0000 (UTC) Received: by fxm11 with SMTP id 11so412331fxm.13 for ; Wed, 08 Jun 2011 05:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=jM5TBuXo1vf8ha0SGMRU8S+ePfy7PhjPyRoOFxXhya4=; b=rYp13DhEjZPFOqtzXDzTKCZKRgpiyK8WOL0+GIyLv1MQO4XZfKMCarVRWyvp87q1/P VLov4uE4zESRUzeUaXNd3UC9QDv9g8ZKKLKdS/7ZFRKwto3hfkHqKmkBnzmgfc3dkokj Q1xG5Kq2yL6OtckCelG31OReYD46P9tswrHQM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=IEjpyL3OzXMSwIvgLHcBXzAXPmAMaehi6KE4GVXAvXXAEerqNGhNRuENttJLlTXOYo N7n0C5AgJn/4jqZW+QTBptaYyKhBnKl1kTTe7P/lmKKXZ1054bxmTpO7qqla6HlkR5Ps eLDHswqjarCCni/Tt0xcbn2id6ejfKmifav2o= Received: by 10.223.17.141 with SMTP id s13mr3977892faa.23.1307536212647; Wed, 08 Jun 2011 05:30:12 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id l26sm210749fam.45.2011.06.08.05.30.10 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 08 Jun 2011 05:30:11 -0700 (PDT) From: Mikolaj Golub To: Yurius Radomskyi References: X-Comment-To: Yurius Radomskyi Sender: Mikolaj Golub Date: Wed, 08 Jun 2011 15:30:09 +0300 In-Reply-To: (Yurius Radomskyi's message of "Thu, 2 Jun 2011 11:47:26 +0300") Message-ID: <86r574ijzi.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: hast syncronization speed issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 12:30:14 -0000 On Thu, 2 Jun 2011 11:47:26 +0300 Yurius Radomskyi wrote: YR> Hi, YR> I have a HAST device set up between two systems. I experience very low YR> speed with dirty blocks synchronization after split-brain condition YR> been recovered: it's 200KB/s average on 1Gbit link. On the other side, YR> when i copy a big file to the zfs partition that is created on top of YR> the hast device the synchronization speed between the host is 50MB/s YR> (wich is not too high for 1Gbit link, but acceptable.) Could you please try the patch (the kernel needs rebuilding)? http://people.freebsd.org/~trociny/uipc_socket.c.patch The patch was committed to current (r222454) and is going to be MFCed after some time. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 12:33:34 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29C43106564A for ; Wed, 8 Jun 2011 12:33:34 +0000 (UTC) (envelope-from plan@sitesplans.com) Received: from sites.sitesplans.com (rrcs-98-101-219-205.midsouth.biz.rr.com [98.101.219.205]) by mx1.freebsd.org (Postfix) with ESMTP id DFD3C8FC1C for ; Wed, 8 Jun 2011 12:33:33 +0000 (UTC) Received: by sites.sitesplans.com (Postfix, from userid 500) id 3321EDD09C5; Wed, 8 Jun 2011 08:14:49 -0400 (EDT) Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: MIME::Lite 2.117 (F2.74) Date: Wed, 8 Jun 2011 12:14:49 UT From: Salman D Hameed To: stable@freebsd.org Message-Id: <20110608121449.3321EDD09C5@sites.sitesplans.com> MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Watch thousands of tv channels on your computer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: plan@sitesplans.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 12:33:34 -0000 Satellite Direct Introduces the Internet Television Revolution 06/07/2011 Are you rea dy for a new way to watch TV? What if I told you that there was a way for you to watch all of your favorite shows, along with news, sports, movies, and even dozens of music stations... all for a one time fee that's less than half of what you currently pay for cable? (And yes, it's 100% legal!) [1]You Can Join NOW The internet changed the way you work, shop, book travel, and spend your fre e time. Now, your computer can revolutionize the way you enjoy watching television, too. Imagine: no more cable or satellite bills, no hardware to install, no worrying about bandwidth limits- just thousands of channels and crystal clear picture and sound quality. With Satellite Direct, you get unlimite d 24/7 access to over 3,500 channels. That's thousands more than cable TV, including dozens of hard to find international channels, as well as all the best premium, movie, sports, news, and music programming. And unlike tra ditional satellite television, you don't need to worry about expensive equipment or heavy satellite dishes. In fact, you don't even have to wait for installation at all! Our easy to use software can be downloa ded in about a minute... meaning you are only 60 seconds away from great television, without paying another cable bill ever again. For a limite d time, Satellite Direct is offering their revolutionary software at the unbelievable price of only $49.95. That's about half the average monthly cost of cable... for a lifetime of television service! [2]Why You are not joining NOW ??? You join our very useful items to your biz and yourself. [3]Visit now Best Wishes and Regards, This is a marketing email sent to stable@freebsd.org with no desire to send you information that is unwanted, therefore, if you wish to be removed from receiving future emails, just [4]Unsubscribe from our mailing list. References 1. http://abfc76x4xkbjw7y-3ujcvebvfk.hop.clickbank.net/?tid=08071981 2. http://abfc76x4xkbjw7y-3ujcvebvfk.hop.clickbank.net/?tid=08071981 3. http://emarketplans.com/auto/subscribe.htm 4. http://sitesplans.com/cgi-bin/responder/register.cgi?un=GpA1S5WQTj7v From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 12:45:06 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1737F1065674 for ; Wed, 8 Jun 2011 12:45:06 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8D7278FC1C for ; Wed, 8 Jun 2011 12:45:05 +0000 (UTC) Received: by fxm11 with SMTP id 11so424255fxm.13 for ; Wed, 08 Jun 2011 05:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=9s08qi3X/wrkPMUo4pGZLK3nldQ9skZ/y7uD86Hlpm0=; b=HjDhwrEQwcGOSxdD92Xi6ylzqjEaVRMO+SCZRDmnGPlOC0tk75P8+ef7+4UkhBfUZs K7/0Dtc0BkpCy6ts8DieAyyH5NKiAGhnmKm2ORCmn5yimK7TBcaRljtNDiKFI15J7Rf8 CYPALUX4LYxCNp7Xp6AT+G89RFGDOa32vHp48= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=XZc4Dt+PaiNZToXvKja6xAN2zmcnjdnCY6FA6X3JzNkUaWjrnllt+T0V6rLWyeqPeZ thzeoINykNlYMweIv17MzNAWTNnD7vW4li1UFhblMqJJSM/DrOnz9Vef2Y/MxDWD5P4Y klw18RR99E7kA2z/UsbexNK0qHSKOFzG8eNCY= Received: by 10.223.55.27 with SMTP id s27mr812565fag.121.1307535790010; Wed, 08 Jun 2011 05:23:10 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id b22sm209429fak.25.2011.06.08.05.23.08 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 08 Jun 2011 05:23:08 -0700 (PDT) From: Mikolaj Golub To: Victor Balada Diaz References: <20110606144655.GG6624@equilibrium.bsdes.net> X-Comment-To: Victor Balada Diaz Sender: Mikolaj Golub Date: Wed, 08 Jun 2011 15:23:06 +0300 In-Reply-To: <20110606144655.GG6624@equilibrium.bsdes.net> (Victor Balada Diaz's message of "Mon, 6 Jun 2011 16:46:55 +0200") Message-ID: <86vcwgikb9.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: stable@freebsd.org Subject: Re: Unusable hastd in FreeBSD 8.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 12:45:06 -0000 Hi, On Mon, 6 Jun 2011 16:46:55 +0200 Victor Balada Diaz wrote: VBD> Hello, VBD> Hastd in it's current form is not usable on FreeBSD 8.2-RELEASE or in 8-STABLE. You VBD> can see why in this thread: VBD> http://lists.freebsd.org/pipermail/freebsd-fs/2011-February/010752.html VBD> You can see the committed fix in: VBD> http://svnweb.freebsd.org/base?view=revision&revision=219721 VBD> But it's never been MFCd. Is it possible to MFC it to 8-STABLE and maybe VBD> do an errata notice for RELENG_8_2? Actually, it was MFCed. In r220151. Also, I don't think this is an issue that makes hastd unusable in FreeBSD 8.2 :-). The issue is the following. Before switching the node to primary the failover (third-party) script is checking if secondary process is still alive (assuming that in this case the primary on another node is still alive too) and fails if it is -- some protection against split brain. But before r219721 secondary might not die automatically when primary host was down. This can be workarounded. E.g. by removing the check in the script :-). Or setting net.inet.tcp.keepidle to some small value (e.g. 10 seconds) -- this should make secondary notice that another end is dead after this interval. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 13:03:34 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 407251065673 for ; Wed, 8 Jun 2011 13:03:34 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 8EC528FC1A for ; Wed, 8 Jun 2011 13:03:33 +0000 (UTC) Received: (qmail invoked by alias); 08 Jun 2011 13:03:31 -0000 Received: from g230111069.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.230.111.69] by mail.gmx.net (mp069) with SMTP; 08 Jun 2011 15:03:31 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX1/17aFBnkP1UbqCe2Jw/zflt8erwLl17fCqP9GLUF 9bT7IsvAPJY23L Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 99F9723DB2F for ; Wed, 8 Jun 2011 15:03:30 +0200 (CEST) Message-ID: <4DEF7322.8030907@gmx.de> Date: Wed, 08 Jun 2011 15:03:30 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Mnenhy/0.8.3 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 13:03:34 -0000 Greetings, I've tried to re-label an existing (and up to date) 8-STABLE installation's root partition. This failed, tunefs reports it cannot write the super block. I have attempted this sequence: 1. reboot (through BIOS and loader) directly into single-user mode (boot -s) 2. sysctl kern.geom.debugflags=16 3. tunefs -L root /dev/ada0s4a # that's the dev I mount the root # partition from Still no joy => tunefs cannot update the super block. Remounting / as rw doesn't help, as expected. The root fs uses softupdates but no journalling -- what other hoops do I need to jump through to create labels for my root ufs file system? Thanks. Best regards, Matthias From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 13:11:40 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 950E41065670 for ; Wed, 8 Jun 2011 13:11:40 +0000 (UTC) (envelope-from nickolasbug@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 1B30D8FC19 for ; Wed, 8 Jun 2011 13:11:39 +0000 (UTC) Received: by qyk35 with SMTP id 35so2229101qyk.13 for ; Wed, 08 Jun 2011 06:11:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nhUHKXVor3e3vpEP8bCCkYWENYduCIi7BP7+pkB2ARY=; b=LpOg6J2FwwhAQ/9PAku0J8BGrKBj7F9NLrWMagQ8mcRE7VGJnGzVqn/chG/dkiNjan VhZU93KLEGA0VfurZLaE4gqowlYW91U2WRzrWn6+MHDEb0kCHmnVlp08EaDmjTKmekeC 4YlhbO2Awt38uzIYfTrLyhx6gCG+I2RlQqsVQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Yqg3DHJsWT8ExBRV0quyH3CdCys1llJFGndiH3ELRL/hezBmaFaVamiVKmvoXHa5bd E+eu1IFEHQXmWetiDxba5eEvk5JBlLcJS2SQU1nlcsz6Tr35UNUeMWgZzMP9hnMrA2Le h0RKmDCMpzCi06OIaBJDlsWzdsYzJZ/ggQiNc= MIME-Version: 1.0 Received: by 10.229.140.195 with SMTP id j3mr5553734qcu.5.1307538698777; Wed, 08 Jun 2011 06:11:38 -0700 (PDT) Received: by 10.229.82.65 with HTTP; Wed, 8 Jun 2011 06:11:38 -0700 (PDT) In-Reply-To: <4DEF7322.8030907@gmx.de> References: <4DEF7322.8030907@gmx.de> Date: Wed, 8 Jun 2011 16:11:38 +0300 Message-ID: From: nickolasbug@gmail.com To: Matthias Andree Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 13:11:40 -0000 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot to single mode and try to re-label partition. 2. Try boot from live CD or installation CD (fixup console) and label file system without mounting 2011/6/8 Matthias Andree : > Greetings, > > I've tried to re-label an existing (and up to date) 8-STABLE > installation's root partition. =A0This failed, tunefs reports it cannot > write the super block. > > I have attempted this sequence: > > 1. reboot (through BIOS and loader) directly into single-user mode > (boot -s) > 2. sysctl kern.geom.debugflags=3D16 > 3. tunefs -L root /dev/ada0s4a =A0 =A0# that's the dev I mount the root > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# part= ition from > > Still no joy =3D> tunefs cannot update the super block. > > Remounting / as rw doesn't help, as expected. > > The root fs uses softupdates but no journalling -- what other hoops do I > need to jump through to create labels for my root ufs file system? > > Thanks. > > Best regards, > Matthias > _______________________________________________ > 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" > ------- wbr, Nickolas From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 13:18:37 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89965106564A for ; Wed, 8 Jun 2011 13:18:37 +0000 (UTC) (envelope-from tzim@tzim.net) Received: from orlith.tzim.net (unknown [IPv6:2001:41d0:2:1d32:21c:c0ff:fe82:92c6]) by mx1.freebsd.org (Postfix) with ESMTP id 2965E8FC18 for ; Wed, 8 Jun 2011 13:18:37 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=secure.tzim.net) by orlith.tzim.net with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QUIea-000LIX-6g for freebsd-stable@freebsd.org; Wed, 08 Jun 2011 15:18:36 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 08 Jun 2011 15:18:36 +0200 From: Arnaud Houdelette To: Message-ID: X-Sender: tzim@tzim.net User-Agent: RoundCube Webmail/0.5.2 Subject: Renaming ZFS datasets without unmount. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 13:18:37 -0000 When I try to rename a mounted dataset with open files, I get the following error : [carenath] /home/tzim# zfs rename unsafe/tmp unsafe/temp cannot unmount '/tmp': Device busy The mountpoint property is set locally : [carenath] /home/tzim# zfs get mountpoint unsafe/tmp NAME PROPERTY VALUE SOURCE unsafe/tmp mountpoint /tmp local zfs(1M) says : Renamed file systems can inherit new mount points, in which case they are unmounted and remounted at the new mount point. But here, the mountpoint should not change. So the file system does not need to be remounted ... Either I don't understand something, or there's an "error" in the man, or a bug in zfs rename. It could be great if zfs allowed "live" renaming of mounted filesystem, as It can avoid headaches... Thanks Arnaud Houdelette From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 14:02:47 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82E211065673 for ; Wed, 8 Jun 2011 14:02:47 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id CEA7B8FC13 for ; Wed, 8 Jun 2011 14:02:46 +0000 (UTC) Received: (qmail invoked by alias); 08 Jun 2011 14:02:44 -0000 Received: from g230111069.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.230.111.69] by mail.gmx.net (mp010) with SMTP; 08 Jun 2011 16:02:44 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX18N8xxWs08No2feeL+AXUFj0pnKdgvUBMnM7XNxie AHrMPs052E+5jf Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id DCC5023DB2F for ; Wed, 8 Jun 2011 16:02:43 +0200 (CEST) Message-ID: <4DEF8103.9030401@gmx.de> Date: Wed, 08 Jun 2011 16:02:43 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Mnenhy/0.8.3 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4DEF7322.8030907@gmx.de> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 14:02:47 -0000 Am 08.06.2011 15:11, schrieb nickolasbug@gmail.com: > 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot > to single mode and try to re-label partition. Indeed not mounting from the label was (apparently) the key to solve this. Thank you. In fact the successful procedure was: - from boot menu, escape to loader prompt - set vfs.root.mountfrom=ufs:/dev/ada0s4a - boot -s - tunefs -L mylabel /dev/ada0s4a - mount -a - edit /etc/fstab to use /dev/ufs/mylabel as device for / - shutdown -r now Best regards, Matthias From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 14:38:42 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 937D0106566C; Wed, 8 Jun 2011 14:38:42 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3AF538FC15; Wed, 8 Jun 2011 14:38:38 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC41CD9.dip.t-dialin.net [79.196.28.217]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 33A60844015; Wed, 8 Jun 2011 16:38:26 +0200 (CEST) Received: from webmail.leidinger.net (webmail.Leidinger.net [IPv6:fd73:10c7:2053:1::3:102]) by outgoing.leidinger.net (Postfix) with ESMTP id 441443B19; Wed, 8 Jun 2011 16:38:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1307543903; bh=rNIuvUAKk/12E/j4XQHWBqf48KPkz5XLA6lXbLzpd7o=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=PhoT5v4SFVZp081hHyCtZhkeuUWGTwaDRhdRRUc2Tc9QwzvY6/glM/JLhDKl2HmT8 pc73QpqsUL3ek6jfqXexgbzb7UsqsyEBY1hns3XbkfaNcmjkvrI+szcXwKAJNxgU/P Y4aQQpUVD3LcbzkEL6W38RTDB4qSKa4MTuRnzGR3F2kFUPA2m2e1bNvH8KW35S1t7o GVI50Iuzq2E4oEir31FEBn1HrVKtyvRhddGBWRyn22TVmyI5gp9w3pKtGDu9FbX7dG oUaw+Om3o7Ve85Xsy32fIbgQCO2eXVzYTADOEnNCkP92XQyzYwOC272V8Q7yFoFpHB wLdMxAkg2qqEg== Received: (from www@localhost) by webmail.leidinger.net (8.14.4/8.14.4/Submit) id p58EcMZc084244; Wed, 8 Jun 2011 16:38:22 +0200 (CEST) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: webmail.leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from pslux.ec.europa.eu (pslux.ec.europa.eu [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 08 Jun 2011 16:38:22 +0200 Message-ID: <20110608163822.13026mwi7kvcuna6@webmail.leidinger.net> Date: Wed, 08 Jun 2011 16:38:22 +0200 From: Alexander Leidinger To: emulation@FreeBSD.org, stable@FreeBSD.org References: <20110608140110.18986ku70sxmm07a@webmail.leidinger.net> In-Reply-To: <20110608140110.18986ku70sxmm07a@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.6) X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 33A60844015.AE1CC X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-0.023, required 6, autolearn=disabled, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, TW_SV 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1308148706.48358@GZZ+0O+Eu8T9yRgsQRU4Gg X-EBL-Spam-Status: No Cc: nox@FreeBSD.org Subject: Re: v4l2 8-stable MFC: testers needed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 14:38:42 -0000 Quoting Alexander Leidinger (from Wed, 08 Jun 2011 14:01:10 +0200): > at http://www.Leidinger.net/test/v4l2-stable8.diff I have the v4l2 > code I want to commit to 8-stable. Can someone please compile it, > test it and give feedback? It looks like svn does not take added files into account, so everyone who wants to give it a try should take linux_videodev2.h and linux_videodev2_compat.h from -current. Bye, Alexander. -- "I need a guy I can trust." "Yeah, OK, let me think about it." -- Johnny Fontane and Nino Valenti, "Chapter 12", page 177 http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 16:26:29 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 682EF106564A for ; Wed, 8 Jun 2011 16:26:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 29C7E8FC1C for ; Wed, 8 Jun 2011 16:26:28 +0000 (UTC) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta07.westchester.pa.mail.comcast.net with comcast id tUHB1g0070cZkys57USVCt; Wed, 08 Jun 2011 16:26:29 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta10.westchester.pa.mail.comcast.net with comcast id tUST1g00L1t3BNj3WUSU9S; Wed, 08 Jun 2011 16:26:28 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 14FB9102C36; Wed, 8 Jun 2011 09:26:26 -0700 (PDT) Date: Wed, 8 Jun 2011 09:26:26 -0700 From: Jeremy Chadwick To: Matthias Andree Message-ID: <20110608162626.GA94883@icarus.home.lan> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DEF8103.9030401@gmx.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 16:26:29 -0000 On Wed, Jun 08, 2011 at 04:02:43PM +0200, Matthias Andree wrote: > Am 08.06.2011 15:11, schrieb nickolasbug@gmail.com: > > 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot > > to single mode and try to re-label partition. > > Indeed not mounting from the label was (apparently) the key to solve > this. Thank you. > > In fact the successful procedure was: > > - from boot menu, escape to loader prompt > - set vfs.root.mountfrom=ufs:/dev/ada0s4a > - boot -s > - tunefs -L mylabel /dev/ada0s4a > - mount -a > - edit /etc/fstab to use /dev/ufs/mylabel as device for / > - shutdown -r now I have the exact same question except not with regards to labels but toggling TRIM capability on the root filesystem. - Start system - At loader, boot single-user (option 4) - At prompt choose /bin/sh - mount -a - tunefs -t enable /dev/ada0s1a --- fails - sysctl kern.geom.debugflags=16 - tunefs -t enable /dev/ada0s1a --- works - tunefs -p /dev/ada0s1a -- shows TRIM enabled - reboot - Boot into single-user, multi-user, whatever - tunefs -p /dev/ada0s1a -- shows TRIM disabled -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 16:40:08 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5FEC106566B for ; Wed, 8 Jun 2011 16:40:08 +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 0FB7F8FC15 for ; Wed, 8 Jun 2011 16:40:07 +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 TAA22681; Wed, 08 Jun 2011 19:40:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DEFA5E3.8080806@FreeBSD.org> Date: Wed, 08 Jun 2011 19:40:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> In-Reply-To: <20110608162626.GA94883@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 16:40:08 -0000 on 08/06/2011 19:26 Jeremy Chadwick said the following: > I have the exact same question except not with regards to labels but > toggling TRIM capability on the root filesystem. > > - Start system > - At loader, boot single-user (option 4) > - At prompt choose /bin/sh > - mount -a I think that this is a culprit. > - tunefs -t enable /dev/ada0s1a --- fails Shouldn't you have / mounted r/o here? BTW, AFAIR, *re*-mounting root read-only won't help; it needs to have never been mounted r/w. > - sysctl kern.geom.debugflags=16 > - tunefs -t enable /dev/ada0s1a --- works > - tunefs -p /dev/ada0s1a -- shows TRIM enabled > - reboot I think that at this step your superblock on disk gets re-written with its copy in memory which has never been updated. But not sure. > - Boot into single-user, multi-user, whatever > - tunefs -p /dev/ada0s1a -- shows TRIM disabled -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 16:55:18 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E8C2106564A for ; Wed, 8 Jun 2011 16:55:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 285F38FC0A for ; Wed, 8 Jun 2011 16:55:17 +0000 (UTC) Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta09.westchester.pa.mail.comcast.net with comcast id tUHt1g0080cZkys59UvJBD; Wed, 08 Jun 2011 16:55:18 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta10.westchester.pa.mail.comcast.net with comcast id tUvH1g00c1t3BNj3WUvHSg; Wed, 08 Jun 2011 16:55:18 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id ECE84102C36; Wed, 8 Jun 2011 09:55:15 -0700 (PDT) Date: Wed, 8 Jun 2011 09:55:15 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20110608165515.GA95345@icarus.home.lan> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DEFA5E3.8080806@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 16:55:18 -0000 On Wed, Jun 08, 2011 at 07:40:03PM +0300, Andriy Gapon wrote: > on 08/06/2011 19:26 Jeremy Chadwick said the following: > > I have the exact same question except not with regards to labels but > > toggling TRIM capability on the root filesystem. > > > > - Start system > > - At loader, boot single-user (option 4) > > - At prompt choose /bin/sh > > - mount -a > > I think that this is a culprit. I'll try removing this step. > > - tunefs -t enable /dev/ada0s1a --- fails > > Shouldn't you have / mounted r/o here? > BTW, AFAIR, *re*-mounting root read-only won't help; it needs to have never been > mounted r/w. I'm a little confused by this sentence, so my apologise in advance. / is mounted read-only in single-user by default. Did you mean I should make it r/w by doing "mount -u -o rw /" ? I may have omitted this step. I will re-verify the exact procedure and exact steps in a moment, and reply here. > > - sysctl kern.geom.debugflags=16 > > - tunefs -t enable /dev/ada0s1a --- works > > - tunefs -p /dev/ada0s1a -- shows TRIM enabled > > - reboot > > I think that at this step your superblock on disk gets re-written with its copy in > memory which has never been updated. But not sure. Hmm, I sure hope that isn't the case. That would mean the only time a person can use tunefs on a root filesystem is when they either do it manually during the FreeBSD installation (adding "-t" to the list of newfs flags in the filesystem creation UI), or if they boot off of some other medium (USB flash drive, CD, PXE, etc.). -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 17:05:55 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1474C106564A for ; Wed, 8 Jun 2011 17:05:55 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id B35FA8FC0C for ; Wed, 8 Jun 2011 17:05:54 +0000 (UTC) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta07.westchester.pa.mail.comcast.net with comcast id tUZS1g0030QuhwU57V5vfm; Wed, 08 Jun 2011 17:05:55 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta02.westchester.pa.mail.comcast.net with comcast id tV5q1g01E1t3BNj3NV5tlU; Wed, 08 Jun 2011 17:05:54 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 00959102C19; Wed, 8 Jun 2011 10:05:48 -0700 (PDT) Date: Wed, 8 Jun 2011 10:05:48 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20110608170548.GA2031@icarus.home.lan> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110608165515.GA95345@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@FreeBSD.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 17:05:55 -0000 On Wed, Jun 08, 2011 at 09:55:15AM -0700, Jeremy Chadwick wrote: > On Wed, Jun 08, 2011 at 07:40:03PM +0300, Andriy Gapon wrote: > > on 08/06/2011 19:26 Jeremy Chadwick said the following: > > > I have the exact same question except not with regards to labels but > > > toggling TRIM capability on the root filesystem. > > > > > > - Start system > > > - At loader, boot single-user (option 4) > > > - At prompt choose /bin/sh > > > - mount -a > > > > I think that this is a culprit. > > I'll try removing this step. > > > > - tunefs -t enable /dev/ada0s1a --- fails > > > > Shouldn't you have / mounted r/o here? > > BTW, AFAIR, *re*-mounting root read-only won't help; it needs to have never been > > mounted r/w. > > I'm a little confused by this sentence, so my apologise in advance. / > is mounted read-only in single-user by default. Did you mean I should > make it r/w by doing "mount -u -o rw /" ? I may have omitted this step. > > I will re-verify the exact procedure and exact steps in a moment, and > reply here. > > > > - sysctl kern.geom.debugflags=16 > > > - tunefs -t enable /dev/ada0s1a --- works > > > - tunefs -p /dev/ada0s1a -- shows TRIM enabled > > > - reboot > > > > I think that at this step your superblock on disk gets re-written with its copy in > > memory which has never been updated. But not sure. > > Hmm, I sure hope that isn't the case. That would mean the only time a > person can use tunefs on a root filesystem is when they either do it > manually during the FreeBSD installation (adding "-t" to the list of > newfs flags in the filesystem creation UI), or if they boot off of some > other medium (USB flash drive, CD, PXE, etc.). Interestingly enough, the long procedure I originally described is probably what was causing the problem. Not sure how to phrase it. The exact procedure which worked was: - Start system - Boot into single-user - Hit enter at prompt (choose /bin/sh) - mount --- shows root filesystem mounted read-only (normal) - tunefs -t enable /dev/ada0s1a --- says it enabled TRIM support - tunefs -p /dev/ada0s1a --- shows TRIM support enabled - reboot - After system starts, as root: tunefs -p /dev/ada0s1a --- shows TRIM enabled So the extra rigmarole I was doing somehow caused the problem. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 18:27:33 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5766106566B; Wed, 8 Jun 2011 18:27:33 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 632358FC0C; Wed, 8 Jun 2011 18:27:33 +0000 (UTC) Received: by vws18 with SMTP id 18so860336vws.13 for ; Wed, 08 Jun 2011 11:27:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=predatorlabs.net; s=google; h=domainkey-signature:mime-version:x-originating-ip:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bz8pJjQrP6JgVvjX5lwvX1Zr7igbCHcdpc2aS09UXKc=; b=jQ/zvwA/f3vO8M6xyaltDJa/HzLtHCqgmBw3PtgbTQU6oYNkc4kalJSY1lx/IiMMYb Bn4oBnF9ipsvT3CRjAjVUjekS6TMp57wHJVfLUcTMylqxxLOLrhIjjxqDHDZNUWE9Z3D K+wZn5ju5bJUdnxP8ZwoMoVn1LKgqV2Hhja2E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=predatorlabs.net; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Pd8mFzJ7aBiC8QecET7FMlRl81+PZKSljL8Htn85LPjDZM4LUfU3MWtROb6SeMkJ3N WQD2FPt3D7nWzJcsXg+lOz9zRRzljNNCiwXYis75qqwp7qa1XlGHcX5gnIJjnUeDjZM3 QMvkWMWEkrdAhO4fySs48izEgikVLRWU3baeM= MIME-Version: 1.0 Received: by 10.220.202.137 with SMTP id fe9mr1727544vcb.79.1307555993488; Wed, 08 Jun 2011 10:59:53 -0700 (PDT) Received: by 10.220.184.73 with HTTP; Wed, 8 Jun 2011 10:59:53 -0700 (PDT) X-Originating-IP: [128.95.133.213] In-Reply-To: <20110608170548.GA2031@icarus.home.lan> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> <20110608170548.GA2031@icarus.home.lan> Date: Wed, 8 Jun 2011 10:59:53 -0700 Message-ID: From: Rob Farmer To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 18:27:33 -0000 On Wed, Jun 8, 2011 at 10:05 AM, Jeremy Chadwick wrote: > Interestingly enough, the long procedure I originally described is > probably what was causing the problem. =A0Not sure how to phrase it. > I don't have a reference for this, but I'm pretty sure it was on one of the mailing lists at some point. The kernel reads the super-block into memory and uses that copy when the file system is mounted. If you have the it mounted rw, then at unmount it is written back out to the disk. If it's mounted ro, the in-memory copy is thrown out and the disk isn't changed. If you upgrade a file system from ro to rw, it does not re-read the on disk copy. tunefs directly modifies on the on-disk copy regardless of mount status, so when you unmount a rw file system, anything it has done is overwritten. The only way to modify / (without alternate boot media) is what you've described below: boot single user, leave it ro, tunefs, then reboot while still ro. Also, I've seen the sysctl kern.geom.debugflags=3D16 thing in zfs tutorials and such, but haven't seen where it's actually necessary. I think this is outdated and changed circa 8.0. --=20 Rob Farmer > The exact procedure which worked was: > > - Start system > - Boot into single-user > - Hit enter at prompt (choose /bin/sh) > - mount --- shows root filesystem mounted read-only (normal) > - tunefs -t enable /dev/ada0s1a --- says it enabled TRIM support > - tunefs -p /dev/ada0s1a --- shows TRIM support enabled > - reboot > - After system starts, as root: tunefs -p /dev/ada0s1a --- shows TRIM > =A0enabled > > So the extra rigmarole I was doing somehow caused the problem. > > -- > | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 jdc@parodius.com | > | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.parodius.com/ | > | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mountain= View, CA, US | > | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0 PGP= 4BD6C0CB | > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 19:21:12 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B90D4106564A for ; Wed, 8 Jun 2011 19:21:12 +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 0AAB68FC08 for ; Wed, 8 Jun 2011 19:21:11 +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 WAA24666; Wed, 08 Jun 2011 22:21:08 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QUOJQ-000IOI-Dm; Wed, 08 Jun 2011 22:21:08 +0300 Message-ID: <4DEFCBA2.10908@FreeBSD.org> Date: Wed, 08 Jun 2011 22:21:06 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> In-Reply-To: <20110608165515.GA95345@icarus.home.lan> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 19:21:12 -0000 on 08/06/2011 19:55 Jeremy Chadwick said the following: > On Wed, Jun 08, 2011 at 07:40:03PM +0300, Andriy Gapon wrote: >> on 08/06/2011 19:26 Jeremy Chadwick said the following: >>> I have the exact same question except not with regards to labels but >>> toggling TRIM capability on the root filesystem. >>> >>> - Start system >>> - At loader, boot single-user (option 4) >>> - At prompt choose /bin/sh >>> - mount -a >> >> I think that this is a culprit. > > I'll try removing this step. > >>> - tunefs -t enable /dev/ada0s1a --- fails >> >> Shouldn't you have / mounted r/o here? >> BTW, AFAIR, *re*-mounting root read-only won't help; it needs to have never been >> mounted r/w. > > I'm a little confused by this sentence, so my apologise in advance. / > is mounted read-only in single-user by default. Did you mean I should > make it r/w by doing "mount -u -o rw /" ? I may have omitted this step. No. My English is not perfect it seems - my point was that you should never mount your root fs r/w if you want to do tunefs on it. > I will re-verify the exact procedure and exact steps in a moment, and > reply here. > >>> - sysctl kern.geom.debugflags=16 >>> - tunefs -t enable /dev/ada0s1a --- works >>> - tunefs -p /dev/ada0s1a -- shows TRIM enabled >>> - reboot >> >> I think that at this step your superblock on disk gets re-written with its copy in >> memory which has never been updated. But not sure. > > Hmm, I sure hope that isn't the case. I think that this is the case. > That would mean the only time a > person can use tunefs on a root filesystem is when they either do it > manually during the FreeBSD installation (adding "-t" to the list of > newfs flags in the filesystem creation UI), or if they boot off of some > other medium (USB flash drive, CD, PXE, etc.). Or when your root fs is mounted r/o, which is not as bad as what you listed above. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 19:48:39 2011 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7C661065670 for ; Wed, 8 Jun 2011 19:48:39 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 9DCDA8FC14 for ; Wed, 8 Jun 2011 19:48:39 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 87F671E002C4; Wed, 8 Jun 2011 21:30:01 +0200 (CEST) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.4/8.14.3) with ESMTP id p58JSDcK074599; Wed, 8 Jun 2011 21:28:13 +0200 (CEST) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.4/8.14.3/Submit) id p58JSC2Y074598; Wed, 8 Jun 2011 21:28:12 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Wed, 8 Jun 2011 21:28:12 +0200 To: Alexander Leidinger Message-ID: <20110608192812.GA74580@triton8.kn-bremen.de> References: <20110608140110.18986ku70sxmm07a@webmail.leidinger.net> <20110608163822.13026mwi7kvcuna6@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110608163822.13026mwi7kvcuna6@webmail.leidinger.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: emulation@FreeBSD.org, nox@FreeBSD.org, stable@FreeBSD.org Subject: Re: v4l2 8-stable MFC: testers needed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 19:48:40 -0000 On Wed, Jun 08, 2011 at 04:38:22PM +0200, Alexander Leidinger wrote: > Quoting Alexander Leidinger (from Wed, 08 > Jun 2011 14:01:10 +0200): > > > at http://www.Leidinger.net/test/v4l2-stable8.diff I have the v4l2 > > code I want to commit to 8-stable. Can someone please compile it, > > test it and give feedback? > > It looks like svn does not take added files into account, so everyone > who wants to give it a try should take linux_videodev2.h and > linux_videodev2_compat.h from -current. Looking good... skype at least works. :) Thanx, Juergen From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 20:37:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51D05106566B for ; Wed, 8 Jun 2011 20:37:12 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3A58FC19 for ; Wed, 8 Jun 2011 20:37:11 +0000 (UTC) Received: by pzk27 with SMTP id 27so545190pzk.13 for ; Wed, 08 Jun 2011 13:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=4u/5CoNiV2FvlwOEkqh9DR8bbaecZrMz0ChGEz/mv1k=; b=m2YiCfJPFzwEihjWcAyASora4pljY7daN5z4VjyAXCVImY0MXuWQ07nvrgB/mJbl8h VUejemhzce5UGm6djkqmDXzwn573NinuJKK9SP12HfFe4X745IVaizwBR/TxC/G4JtJ+ t9gNSL8GgkX/7is7xnzlWq2k4H1od/qhb3BBo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=CUGGLATDh4QQiEivq4TATy8EgHojBqHbVTwuYaMtPxg7rky61/anX5y75Pb+3LXWwD rxOp7az3PW0vO7qlzPXxqifoYquxtZbBOhW3bsw+rVS+oscso0M+NLgv8/VtUCi8aRQK ovr8zLf+XawZ6InyOM1pvwKagwnjuVCHhYXlE= MIME-Version: 1.0 Received: by 10.68.1.42 with SMTP id 10mr532320pbj.33.1307565431614; Wed, 08 Jun 2011 13:37:11 -0700 (PDT) Received: by 10.68.51.169 with HTTP; Wed, 8 Jun 2011 13:37:11 -0700 (PDT) In-Reply-To: <4DEFCBA2.10908@FreeBSD.org> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> <4DEFCBA2.10908@FreeBSD.org> Date: Wed, 8 Jun 2011 13:37:11 -0700 Message-ID: From: Josh Carroll To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 20:37:12 -0000 >> That would mean the only time a >> person can use tunefs on a root filesystem is when they either do it >> manually during the FreeBSD installation (adding "-t" to the list of >> newfs flags in the filesystem creation UI), or if they boot off of some >> other medium (USB flash drive, CD, PXE, etc.). > > Or when your root fs is mounted r/o, which is not as bad as what you listed above. Perhaps I'm doing something wrong, but in my experience, at least with glabel, the label will not stick even if you have the root fs mounted ro. I have had to boot from an alternative media (boot cd, alternate root fs, etc) in order to create a label for the root fs with glabel. To be specific, I'm talking about the "automatic" labels created with glabel label . I just tested this again in a VM, and sure enough if I boot single user mode but use ad0s1a as the ro root file system during single user mode, it still doesn't stick and upon reboot I don't have a /dev/label entry. Here is the exact sequence I used: 1. boot single user with the default root fs (ad0s1a). 2. leave / mounted read only 3. glabel label -v root ad0s1a # reports successful addition of metadata 4. /dev/label/root exists as expected 5. reboot 6. /dev/label/root does not exist If I boot from a boot cd for example and do it from there, it works fine. So it seems (at least for glabel) that you can't have the fs mounted at all when adding a glabel. If that's the expected behavior, perhaps we can add a mention of this in the man page(s)? Otherwise, I'm curious what I'm doing wrong and how I can get it to stick and still not need a boot CD/etc. Thanks, Josh From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 21:29:23 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3009106564A; Wed, 8 Jun 2011 21:29:22 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 73D698FC0A; Wed, 8 Jun 2011 21:29:22 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id p58LC3BI035488; Wed, 8 Jun 2011 23:12:03 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id p58LC30b035487; Wed, 8 Jun 2011 23:12:03 +0200 (CEST) (envelope-from marius) Date: Wed, 8 Jun 2011 23:12:03 +0200 From: Marius Strobl To: Martin Matuska , ppc@freebsd.org, sparc64@freebsd.org Message-ID: <20110608211203.GA35440@alchemy.franken.de> References: <4DECB197.8020102@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DECB197.8020102@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 21:29:23 -0000 On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) > > New major features: > > - data deduplication > - triple parity RAIDZ (RAIDZ3) > - zfs diff > - zpool split > - snapshot holds > - zpool import -F. Allows to rewind corrupted pool to earlier > transaction group > - possibility to import pool in read-only mode > > For updating, there is a compatibility layer so that in the update phase > most functionality of the new zfs binaries can be used with the old > kernel module and old zfs binaries with the new kernel module. Beware that the compatibility layer is known broken on big-endian architectures, i.e. powerpc64 and sparc64. > > If upgrading your boot pool to version 28, please don't forget to read > UPDATING and properly update your boot code. > > Thanks to everyone working on the ZFS port, especially to > Pawel Jakub Dawidek (pjd) for doing most of the work! > Marius From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 22:55:59 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87AD9106566B for ; Wed, 8 Jun 2011 22:55:59 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 091398FC14 for ; Wed, 8 Jun 2011 22:55:58 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id p58MtuSr036218; Thu, 9 Jun 2011 00:55:56 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id p58MtuAg036217; Thu, 9 Jun 2011 00:55:56 +0200 (CEST) (envelope-from marius) Date: Thu, 9 Jun 2011 00:55:56 +0200 From: Marius Strobl To: "C. P. Ghost" Message-ID: <20110608225556.GQ7064@alchemy.franken.de> References: <4DECB197.8020102@FreeBSD.org> <20110608211203.GA35440@alchemy.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 22:55:59 -0000 On Thu, Jun 09, 2011 at 12:46:19AM +0200, C. P. Ghost wrote: > On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl > wrote: > > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > >> Hi, > >> > >> I have merged ZFS version 28 to 8-STABLE (revision 222741) > >> > >> New major features: > >> > >> - data deduplication > >> - triple parity RAIDZ (RAIDZ3) > >> - zfs diff > >> - zpool split > >> - snapshot holds > >> - zpool import -F. Allows to rewind corrupted pool to earlier > >> ? transaction group > >> - possibility to import pool in read-only mode > >> > >> For updating, there is a compatibility layer so that in the update phase > >> most functionality of the new zfs binaries can be used with the old > >> kernel module and old zfs binaries with the new kernel module. > > > > Beware that the compatibility layer is known broken on big-endian > > architectures, i.e. powerpc64 and sparc64. > > Thanks for the heads-up! I was just about to update a couple of sparc64 > machines here. Fortunately, the only ZFS file systems there are external > file systems (no /, /usr, /var etc...), so it's gonna be painless, I suppose. > But what about other layouts? Does it mean that an installkernel, reboot, > and installworld won't work? No, using the old zfs binaries with the new kernel module triggers the problem. Using the new zfs binaries with the new kernel module works (at least with CURRENT) so you'd need disregard everything that is documented and do what is not guaranteed to work but usually also does, i.e. do installkernel, installworld and then reboot. > > >> If upgrading your boot pool to version 28, please don't forget to read > >> UPDATING and properly update your boot code. > >> > >> Thanks to everyone working on the ZFS port, especially to > >> Pawel Jakub Dawidek (pjd) for doing most of the work! > > Marius From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 22:59:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00D3C106564A for ; Wed, 8 Jun 2011 22:59:41 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id BAE828FC12 for ; Wed, 8 Jun 2011 22:59:40 +0000 (UTC) Received: by vws18 with SMTP id 18so1133308vws.13 for ; Wed, 08 Jun 2011 15:59:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.177.205 with SMTP id bj13mr14786vcb.39.1307573979505; Wed, 08 Jun 2011 15:59:39 -0700 (PDT) Received: by 10.220.80.144 with HTTP; Wed, 8 Jun 2011 15:59:39 -0700 (PDT) X-Originating-IP: [93.221.173.86] In-Reply-To: <20110608225556.GQ7064@alchemy.franken.de> References: <4DECB197.8020102@FreeBSD.org> <20110608211203.GA35440@alchemy.franken.de> <20110608225556.GQ7064@alchemy.franken.de> Date: Thu, 9 Jun 2011 00:59:39 +0200 Message-ID: From: "C. P. Ghost" To: Marius Strobl Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 22:59:41 -0000 On Thu, Jun 9, 2011 at 12:55 AM, Marius Strobl wrote: > On Thu, Jun 09, 2011 at 12:46:19AM +0200, C. P. Ghost wrote: >> On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl >> wrote: >> > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: >> >> Hi, >> >> >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) >> >> >> >> New major features: >> >> >> >> - data deduplication >> >> - triple parity RAIDZ (RAIDZ3) >> >> - zfs diff >> >> - zpool split >> >> - snapshot holds >> >> - zpool import -F. Allows to rewind corrupted pool to earlier >> >> ? transaction group >> >> - possibility to import pool in read-only mode >> >> >> >> For updating, there is a compatibility layer so that in the update phase >> >> most functionality of the new zfs binaries can be used with the old >> >> kernel module and old zfs binaries with the new kernel module. >> > >> > Beware that the compatibility layer is known broken on big-endian >> > architectures, i.e. powerpc64 and sparc64. >> >> Thanks for the heads-up! I was just about to update a couple of sparc64 >> machines here. Fortunately, the only ZFS file systems there are external >> file systems (no /, /usr, /var etc...), so it's gonna be painless, I suppose. >> But what about other layouts? Does it mean that an installkernel, reboot, >> and installworld won't work? > > No, using the old zfs binaries with the new kernel module triggers the > problem. Using the new zfs binaries with the new kernel module works > (at least with CURRENT) so you'd need disregard everything that is > documented and do what is not guaranteed to work but usually also does, > i.e. do installkernel, installworld and then reboot. Ah, yes, that's what I expected. Thank you! -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 23:11:06 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92B8E106566B for ; Wed, 8 Jun 2011 23:11:06 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 576CA8FC15 for ; Wed, 8 Jun 2011 23:11:06 +0000 (UTC) Received: by vxc34 with SMTP id 34so1132626vxc.13 for ; Wed, 08 Jun 2011 16:11:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.177.205 with SMTP id bj13mr10568vcb.39.1307573179184; Wed, 08 Jun 2011 15:46:19 -0700 (PDT) Received: by 10.220.80.144 with HTTP; Wed, 8 Jun 2011 15:46:19 -0700 (PDT) X-Originating-IP: [93.221.173.86] In-Reply-To: <20110608211203.GA35440@alchemy.franken.de> References: <4DECB197.8020102@FreeBSD.org> <20110608211203.GA35440@alchemy.franken.de> Date: Thu, 9 Jun 2011 00:46:19 +0200 Message-ID: From: "C. P. Ghost" To: Marius Strobl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2011 23:11:06 -0000 On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl wrote: > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: >> Hi, >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) >> >> New major features: >> >> - data deduplication >> - triple parity RAIDZ (RAIDZ3) >> - zfs diff >> - zpool split >> - snapshot holds >> - zpool import -F. Allows to rewind corrupted pool to earlier >> =A0 transaction group >> - possibility to import pool in read-only mode >> >> For updating, there is a compatibility layer so that in the update phase >> most functionality of the new zfs binaries can be used with the old >> kernel module and old zfs binaries with the new kernel module. > > Beware that the compatibility layer is known broken on big-endian > architectures, i.e. powerpc64 and sparc64. Thanks for the heads-up! I was just about to update a couple of sparc64 machines here. Fortunately, the only ZFS file systems there are external file systems (no /, /usr, /var etc...), so it's gonna be painless, I suppos= e. But what about other layouts? Does it mean that an installkernel, reboot, and installworld won't work? >> If upgrading your boot pool to version 28, please don't forget to read >> UPDATING and properly update your boot code. >> >> Thanks to everyone working on the ZFS port, especially to >> Pawel Jakub Dawidek (pjd) for doing most of the work! > > Marius Thanks, -cpghost. --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 07:37:30 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7ACA106564A for ; Thu, 9 Jun 2011 07:37:30 +0000 (UTC) (envelope-from nickolasbug@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 72E0C8FC12 for ; Thu, 9 Jun 2011 07:37:30 +0000 (UTC) Received: by qyk35 with SMTP id 35so2761450qyk.13 for ; Thu, 09 Jun 2011 00:37:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=66ZuYnEI4oTbIfWtgHgPvbjf3EehtiTKfnQvilVu8aw=; b=mpo2OvId1VzGJinpWndtYMgkwQWGOpWAdrv5FLdadbt19SmQC7bbMsLzc0HvLMM8AP aSSBDpoSwhh7A0LhhfZti+yeCVW8DyEk/nepqAZ+GtAWnLoeRbS9KUbFWM2S7c/Gegb9 O/oDV6Xopi1B/v6HUc/4H2HbG1XfInNzrfsDA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nxdD9wVrktI9jzAUZUaQ5WgziIoGtTY/OXuJ4XNt3GRcessmU2RvYNAY3/lG1sQz4B ZjMdWL9pz6BxJzLFZX+g9UUchEuTNjW5eSv53ppUjdUROaoCyzYGMoesLQ27BhowMS67 /7pvvVcB34gqmniYH/KOuR8YMZEIvVFjxdWqw= MIME-Version: 1.0 Received: by 10.224.187.12 with SMTP id cu12mr268264qab.67.1307605049770; Thu, 09 Jun 2011 00:37:29 -0700 (PDT) Received: by 10.229.82.65 with HTTP; Thu, 9 Jun 2011 00:37:29 -0700 (PDT) In-Reply-To: <4DEF8103.9030401@gmx.de> References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> Date: Thu, 9 Jun 2011 10:37:29 +0300 Message-ID: From: nickolasbug@gmail.com To: Matthias Andree Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 07:37:30 -0000 2011/6/8 Matthias Andree : > Am 08.06.2011 15:11, schrieb nickolasbug@gmail.com: >> 1. Change your root fstab record to /dev/ada0s4a (not label!), reboot >> to single mode and try to re-label partition. > > Indeed not mounting from the label was (apparently) the key to solve > this. =A0Thank you. > > In fact the successful procedure was: > > - from boot menu, escape to loader prompt > - set vfs.root.mountfrom=3Dufs:/dev/ada0s4a > - boot -s > - tunefs -L mylabel /dev/ada0s4a > - mount -a > - edit /etc/fstab to use /dev/ufs/mylabel as device for / > - shutdown -r now > Right, you cannot re-label partition because you've mount filesystem through label device. So this device is already in use and re-labeling would destroy label device. ----- wbr, Nickolas From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 07:57:02 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D5E5106566B for ; Thu, 9 Jun 2011 07:57:02 +0000 (UTC) (envelope-from nickolasbug@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id D039D8FC14 for ; Thu, 9 Jun 2011 07:57:01 +0000 (UTC) Received: by qwc9 with SMTP id 9so839046qwc.13 for ; Thu, 09 Jun 2011 00:57:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iJ4E0Lo6IvpOn3QVl1h8k7j0PtNukl9h3ydH/x+jqSY=; b=Lts+OnPPB2iT7bXnDLyMGM7L/0kPWlImVIdpK5ioUDffiLT+1ALuMadkxczfF7OWu9 N9duPNHAVu/KPXc/xTNp/Nx+/9OIMbJLxKl6VrZ6h00cPY+0u/xSsUtzMoUgScmuAmQo D/OKP5rpyd1boVHfzEOPT/1dBU0i25F8GRUJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OHdTmL3sowwX4HOqYdT/MCgYKd/ZUpvpBLLVYnuzwS2+aKQMlNEjvREEozoFC4+hjN kCC/CTYBp/uY8Lh7yhyeJ7aCKM1BsxbUvaeu4tdPYGNELUs4ZL6sB9UwM/JJ6xfAe2Hc QUlfa1YWImb0sCKf4MAN8XKL8KIi59yhm9fpY= MIME-Version: 1.0 Received: by 10.229.25.211 with SMTP id a19mr273202qcc.81.1307606220991; Thu, 09 Jun 2011 00:57:00 -0700 (PDT) Received: by 10.229.82.65 with HTTP; Thu, 9 Jun 2011 00:57:00 -0700 (PDT) In-Reply-To: References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> <4DEFCBA2.10908@FreeBSD.org> Date: Thu, 9 Jun 2011 10:57:00 +0300 Message-ID: From: nickolasbug@gmail.com To: josh.carroll@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, Jeremy Chadwick , Andriy Gapon Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 07:57:02 -0000 2011/6/8 Josh Carroll : >>> That would mean the only time a >>> person can use tunefs on a root filesystem is when they either do it >>> manually during the FreeBSD installation (adding "-t" to the list of >>> newfs flags in the filesystem creation UI), or if they boot off of some >>> other medium (USB flash drive, CD, PXE, etc.). >> >> Or when your root fs is mounted r/o, which is not as bad as what you lis= ted above. Or when you've booted form device (not label), e.g. /dev/ada0s1a and have set sysctl kern.geom.debugflags=3D16 > > Perhaps I'm doing something wrong, but in my experience, at least with > glabel, the label will not stick even if you have the root fs mounted > ro. I have had to boot from an alternative media (boot cd, alternate > root fs, etc) in order to create a label for the root fs with glabel. > To be specific, I'm talking about the "automatic" labels created with > glabel label . > > I just tested this again in a VM, and sure enough if I boot single > user mode but use ad0s1a as the ro root file system during single user > mode, it still doesn't stick and upon reboot I don't have a /dev/label > entry. Here is the exact sequence I used: > > 1. boot single user with the default root fs (ad0s1a). > 2. leave / mounted read only > 3. glabel label -v root ad0s1a =A0 # reports successful addition of metad= ata > 4. /dev/label/root exists as expected > 5. reboot > 6. /dev/label/root does not exist You should mount fs from label device - /dev/label/root in your case, which must be in /etc/fstab, e.g.: /dev/label/root / ufs rw 1 1 Otherwise if you mount fs from device directly (not from label) label entry (/dev/label/root) would be removed from /dev file system as unused device. This action will be reported in dmesg (you may check it) So, afrer labeling device you should add fstab record. After that you can reboot. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 14:37:26 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE5561065672 for ; Thu, 9 Jun 2011 14:37:26 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [IPv6:2001:470:a80a:1:21f:d0ff:fe22:b8a8]) by mx1.freebsd.org (Postfix) with ESMTP id 815CA8FC0A for ; Thu, 9 Jun 2011 14:37:26 +0000 (UTC) Received: from kanga.honeypot.net (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id C26A2B94D5 for ; Thu, 9 Jun 2011 09:37:25 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by kanga.honeypot.net (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QW0kBL35OO0K for ; Thu, 9 Jun 2011 09:37:23 -0500 (CDT) Received: from pooh.honeypot.net (pooh.honeypot.net [IPv6:2001:470:a80a:1:20a:95ff:fed5:10f2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTPSA id E799FB94C8 for ; Thu, 9 Jun 2011 09:37:23 -0500 (CDT) Message-Id: <84E92041-C897-4744-B432-CA3537EE156F@strauser.com> From: Kirk Strauser To: FreeBSD Stable Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 9 Jun 2011 09:37:23 -0500 X-Mailer: Apple Mail (2.936) Subject: re0 died last night; here's how I half-revived it X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 14:37:26 -0000 I have a FreeBSD 8-STABLE system that's been running stably since I last upgraded and rebooted on May 8. Yesterday, I updated /usr/src to get ZFS v28 and also seem to have gotten rid of my nice, solid re0 network interface: re0: port 0xb000-0xb0ff mem 0xea210000-0xea210fff,0xea200000-0xea20ffff irq 16 at device 0.0 on pci5 re0: Using 1 MSI-X message re0: Chip rev. 0x3c000000 re0: MAC rev. 0x00400000 miibus0: on re0 I'm too tired from lack of sleep due to getting the system back up and running to remember all the details, but the summary is that it started autodetecting its media as 10baseT/UTP. Almost immediately after boot - sometimes while still playing in single-user mode - I'd start seeing "no buffer space available" error messages all over the place. Forcing media to 1000baseTX/full-duplex fixed the problem for a few minutes, but it wouldn't stay in that state and would shortly start throwing "no buffer space available" errors again. Until I've gotten some sleep and have more mental energy to figure out exactly what's going on, I've found that forcing the media to 100baseTX keeps it solidly chugging along (if a little slowly). Anyway, that's where I'm at now. If your re NIC is giving you fits this morning, try setting it to 100baseTX and see if that'll get you running until a better fix comes along. - Kirk From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 15:28:28 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA539106566C for ; Thu, 9 Jun 2011 15:28:28 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 601AC8FC12 for ; Thu, 9 Jun 2011 15:28:28 +0000 (UTC) Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 225781478 for ; Thu, 9 Jun 2011 17:28:27 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:content-disposition:content-type:content-type :mime-version:message-id:subject:subject:from:from:date:date :received:received; s=mail; t=1307633301; x=1309447701; bh=QX5d2 aXSFN+6GjVuvYxihv8gMUAKY+X0A8HRBEZMZeM=; b=qztUkK7yuO6kN63MaZK/M Ohtbw2kb9WJhbgXvOqEwBXSyiL4emBJ2yGG1w3ARktwl0O+wrASh9YC6xrEAGI1F fhzj3MiNexAEaYgxcwFUddia1G6oLN+hAOvbsxySv+v2dPvjRHIkmiCKafJQtsbP Dcifxeewg4CMjqSax0sp04= X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by megatron.madpilot.net (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3DYHRmL7qDY8 for ; Thu, 9 Jun 2011 17:28:21 +0200 (CEST) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 0F7BA1470; Thu, 9 Jun 2011 17:28:21 +0200 (CEST) Date: Thu, 9 Jun 2011 17:28:20 +0200 From: Guido Falsi To: FreeBSD Stable Message-ID: <20110609152820.GC57263@megatron.madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Subject: BTX loader problem on specific hardware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 15:28:28 -0000 Hi! I'm having a problem with BTX hanging on an HP 6005 Pro PC. I have filed a followup to an existing PR about this exact problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=151122 All the information there looks correct and stands true. I have tried performing some trivial debugging on btxld and btx, but not having any ASM skills and not knowing much about PC booting process I could not conjure much. It looks that it hangs between the end of btxld.S just before relocating it's own start.8 routine and the first few instructions in btx.S. Could really not make up much more. I tried using old btx code, but it does not compile with present tools. So I'm a little stuck. I have the machine handy and can perform tests, run code and even debug further if instructed a little on what needs to be done. I hope someone with some specific knowledge could have a look at this(strange) problem. Thanks in advance! -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 17:22:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADA5D106566B for ; Thu, 9 Jun 2011 17:22:05 +0000 (UTC) (envelope-from mgiurgeu@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 89E758FC13 for ; Thu, 9 Jun 2011 17:22:05 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QUicZ-0006Q1-Px for freebsd-stable@freebsd.org; Thu, 09 Jun 2011 10:02:15 -0700 Date: Thu, 9 Jun 2011 10:02:15 -0700 (PDT) From: mgiurgeu To: freebsd-stable@freebsd.org Message-ID: <1307638935798-4473468.post@n5.nabble.com> In-Reply-To: <7B8A7FC8-2547-4A63-8BCC-3CCDF39211D2@gsoft.com.au> References: <20110309101734.GA42208@alchemy.franken.de> <7B8A7FC8-2547-4A63-8BCC-3CCDF39211D2@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Disable probing of bge1? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 17:22:05 -0000 we managed to disable bge0, by inserting the following: + if (device_get_unit(dev) == 0) + return (ENXIO); + -- View this message in context: http://freebsd.1045724.n5.nabble.com/Disable-probing-of-bge1-tp3961580p4473468.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 18:20:56 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76E4C106566B for ; Thu, 9 Jun 2011 18:20:56 +0000 (UTC) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from krusty.dt.e-technik.tu-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0288FC19 for ; Thu, 9 Jun 2011 18:20:55 +0000 (UTC) Received: from [192.168.0.4] (g227003072.adsl.alicedsl.de [92.227.3.72]) by mail.dt.e-technik.tu-dortmund.de (Postfix) with ESMTPSA id 1D9DE48CA6 for ; Thu, 9 Jun 2011 20:01:05 +0200 (CEST) Message-ID: <4DF10A60.4080200@dt.e-technik.uni-dortmund.de> Date: Thu, 09 Jun 2011 20:01:04 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Mnenhy/0.8.3 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4DEF7322.8030907@gmx.de> <4DEF8103.9030401@gmx.de> <20110608162626.GA94883@icarus.home.lan> <4DEFA5E3.8080806@FreeBSD.org> <20110608165515.GA95345@icarus.home.lan> <20110608170548.GA2031@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 09 Jun 2011 20:00:19 +0000 Subject: Re: [SOLVED] Re: labelling root file system (RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 18:20:56 -0000 Am 08.06.2011 19:59, schrieb Rob Farmer: > Also, I've seen the sysctl kern.geom.debugflags=16 thing in zfs > tutorials and such, but haven't seen where it's actually necessary. I > think this is outdated and changed circa 8.0. Possibly - it's still a de-facto standard reflex action whenever a newer FreeBSD kernel refuses to write a superblock or MBR or partition stuff. 8-) From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 20:12:35 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12F06106566B for ; Thu, 9 Jun 2011 20:12:35 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DE72E8FC17 for ; Thu, 9 Jun 2011 20:12:34 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 66AA246B0A; Thu, 9 Jun 2011 16:12:34 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id EB51A8A01F; Thu, 9 Jun 2011 16:12:33 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 9 Jun 2011 15:43:15 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <20110609152820.GC57263@megatron.madpilot.net> In-Reply-To: <20110609152820.GC57263@megatron.madpilot.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106091543.16028.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 09 Jun 2011 16:12:34 -0400 (EDT) Cc: Guido Falsi Subject: Re: BTX loader problem on specific hardware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 20:12:35 -0000 On Thursday, June 09, 2011 11:28:20 am Guido Falsi wrote: > Hi! > > I'm having a problem with BTX hanging on an HP 6005 Pro PC. > > I have filed a followup to an existing PR about this exact problem: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=151122 > > All the information there looks correct and stands true. > > I have tried performing some trivial debugging on btxld and btx, but not > having any ASM skills and not knowing much about PC booting process I > could not conjure much. > > It looks that it hangs between the end of btxld.S just before > relocating it's own start.8 routine and the first few instructions > in btx.S. Could really not make up much more. > > I tried using old btx code, but it does not compile with present tools. > So I'm a little stuck. > > I have the machine handy and can perform tests, run code and even debug > further if instructed a little on what needs to be done. > > I hope someone with some specific knowledge could have a look at > this(strange) problem. > > Thanks in advance! Hmm, these are not so easy to debug. You can try putting a 'foo: jmp foo' instruction in various places as a sort of 'while (1)' loop. The first test I would do is to put it earlier in btxld before the messages that BTXLDR_VERBOSE logs to see if when it hangs the cursor stays at its current location rather than jumping back up. If that works out then you can start moving the 'foo: jmp foo' later until you find a point where it hangs and moves the cursor (which means it hung in between your previous 'jmp foo' and the one you most recently added). I would start by walking down through btxldr.S. If it makes it all the way through that, start walking through the BTX init code. Oddly enough, BTX had to run at least once so that boot2 could find the loader and kick off the btxldr.S. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 20:16:49 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AF8C106564A for ; Thu, 9 Jun 2011 20:16:49 +0000 (UTC) (envelope-from greg@bonett.org) Received: from bonett.org (bonett.org [66.249.7.150]) by mx1.freebsd.org (Postfix) with ESMTP id 597DF8FC18 for ; Thu, 9 Jun 2011 20:16:49 +0000 (UTC) Received: from [192.168.1.216] (unknown [76.91.19.169]) by bonett.org (Postfix) with ESMTPSA id C054C124245 for ; Thu, 9 Jun 2011 20:00:11 +0000 (UTC) From: Greg Bonett To: "stable@freebsd.org" Content-Type: text/plain; charset="UTF-8" Date: Thu, 09 Jun 2011 13:00:10 -0700 Message-ID: <1307649610.2135.29.camel@ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: Subject: recover file from destroyed zfs snapshot - is it possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 20:16:49 -0000 Hi all, I know this is a long shot, but I figure it's worth asking. Is there anyway to recover a file from a zfs snapshot which was destroyed? I know the name of the file and a unique string that should be in it. The zfs pool is on geli devices so I can't dd the raw device and look for it. Any suggestions? Thanks for the help. -Greg From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 20:27:55 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CDDB106564A; Thu, 9 Jun 2011 20:27:55 +0000 (UTC) (envelope-from kc5vdj.freebsd@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id CA1FE8FC0C; Thu, 9 Jun 2011 20:27:54 +0000 (UTC) Received: by iwn33 with SMTP id 33so2351685iwn.13 for ; Thu, 09 Jun 2011 13:27:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:content-type:content-transfer-encoding; bh=8I2N3K3lfAiV5eGwU6j4dMSAIf+2AIfhX1fy8yET7k4=; b=is7WcQAlKLfblxzAD3HMBflDj0khhhC5BBNHmn+yLcZ5QFoxWtNYwHy+KnDcWVIDJX bUsj13bk0Cmj1JlviPdMNhVszYnNvyDhD3q3BdFU/FC983sJf0O0BbGYS8dHHPjRvVwj WMy3YioSle+cTGd+T7rVtcKB3kLQAdOg5RKc0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; b=s6gBsDQg8CBi8W1EYcBYT1ofAwTvwmP6BnY3Zw1VCG0b//mXEx5qUoo3HtNxtJpSQr d9GWI0y8o2LWxfnBm3hIqTs6CmX9NNQ7ox/98e4a0RB1fajHTuvatouiTLJyP3Zzb/yj BpFNTOcWGmY5Q/Nhbh0/k+8cPCFWEYMiW/R0g= Received: by 10.231.44.65 with SMTP id z1mr1418360ibe.95.1307649729183; Thu, 09 Jun 2011 13:02:09 -0700 (PDT) Received: from argus.electron-tube.net (desm-45-047.dsl.netins.net [167.142.45.47]) by mx.google.com with ESMTPS id w8sm926520ibh.52.2011.06.09.13.02.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2011 13:02:08 -0700 (PDT) Message-ID: <4DF126B5.8040800@gmail.com> Date: Thu, 09 Jun 2011 15:01:57 -0500 From: Jim Bryant User-Agent: Thunderbird 2.0.0.24 (X11/20100911) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: kvm_open errors on /proc/*/mem in top X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 20:27:55 -0000 i'm not sure which list this belongs to, so i'm posting to -hackers and -stable. i've noticed for a while now that during heavy activity (for instance buildworld), that top will get these kvm_read errors when reading proc mem entries. i have included a screenshot of what happens during such events... last pid: 92024; load averages: 4.79, 4.58, 4.10 up 0+00:49:07 15:30:53 225 processes: 10 running, 197 sleeping, 18 waiting CPU: 90.6% user, 0.0% nice, 9.4% system, 0.0% interrupt, 0.0% idle Mem: 493M Active, 1337M Inact, 604M Wired, 632K Cache, 315M Buf, 524M Free Swap: 4097M Total, 4097M Free kvm_open: cannot open /proc/86755/mem PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 91943 root 1 97 0 39536K 33620K RUN 1 0:01 7.37% [cc1plus] 2859 jbryant 1 48 0 406M 72332K select 0 3:10 5.96% kwin -session 1028b2382461f5000127042056000000019550000_13 2747 root 1 46 0 419M 370M select 0 1:43 4.39% /usr/local/bin/X :0 -nolisten tcp -auth /var/run/xauth/A:0 1464 root 1 44 0 8068K 1384K select 0 0:03 0.39% /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.u 11219 jbryant 7 44 0 299M 109M select 1 0:17 0.29% /usr/local/lib/thunderbird/thunderbird-bin 2865 jbryant 1 45 0 453M 86140K select 0 0:21 0.20% kdeinit4: kdeinit4: plasma-desktop (kdeinit4) 2882 jbryant 1 44 0 391M 60996K select 0 0:17 0.10% kdeinit4: kdeinit4: kmix -session 102511e52251c60001304471 92001 root 1 97 0 23452K 22256K CPU1 1 0:00 0.00% [cc1] 92017 root 1 96 0 16172K 13440K RUN 0 0:00 0.00% [cc1] and such as this: last pid: 19348; load averages: 1.03, 1.93, 2.84 up 1+04:42:07 15:31:37 201 processes: 4 running, 178 sleeping, 19 waiting CPU: 47.4% user, 0.0% nice, 3.4% system, 0.0% interrupt, 49.3% idle Mem: 318M Active, 2400M Inact, 679M Wired, 1948K Cache, 407M Buf, 428M Free Swap: 8192M Total, 6488K Used, 8186M Free kvm_open: cannot open /proc/1141/memm kvm_open: cannot open /proc/92606/mem RES STATE C TIME WCPU COMMAND 10 root 2 171 ki31 0K 32K RUN 0 55.9H 103.81% [idle] 19344 root 1 96 0 17188K 14300K CPU1 0 0:00 0.00% [cc1] 19341 root 1 76 0 3204K 1068K select 1 0:00 0.00% make all DIRPRFX=fdc/ 19342 root 1 76 0 8340K 1848K wait 1 0:00 0.00% sh -ev 19343 root 1 76 0 3204K 596K wait 0 0:00 0.00% [cc] 19345 root 1 76 0 3204K 1292K piperd 0 0:00 0.00% /usr/obj/usr/src/tmp/usr/bin/as -Qy -o fdc.o the current fix for this is to [CTRL]-L. i assume that what is happening is that top just loosing track of what's running, and the procs are dead by the time it tries to read them, or that the proc ends during top reading. is there any way to fix this? it's annoying as f&#k. ps: running 8-STABLE. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 20:34:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41011106566B; Thu, 9 Jun 2011 20:34:53 +0000 (UTC) (envelope-from kc5vdj.freebsd@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id E20B58FC08; Thu, 9 Jun 2011 20:34:52 +0000 (UTC) Received: by iyj12 with SMTP id 12so2381911iyj.13 for ; Thu, 09 Jun 2011 13:34:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:content-type:content-transfer-encoding; bh=nU43C5RRiyiswbsRwHDoO7KW3/Px576PRxghlBkpEjs=; b=mYDA/q+XWF2lOMRXAHc4HUEhQZmE/unK+fRiLAWZ/dKC55pPnvvS7fpZDbZi9oRUZq RdIdsf2LuyRwOKc/VJvvYhD7Z87dGlwzBSYWLVdyihBJ+nGnwvaRVaR0+pwkkHMTaE7O Ap0GEbyr17sDMZ4phXYUSq576Oi704LGcKLMM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; b=LW3GVZ5d3mraY5POfv8aRrbgHd5DM77YIm15NJ4+4EBl87w7Jm0Trous7rikrpQeFD ED+zzcL+ef9lCMF2TYw2+Lfe4+KLmcuhx3XGiHZZQhIw8zYUFyIkPx6VfC+9Ks55v3IT 9m6+dDkGInabB/KjaviaFyVR87z2TWbW3eW7s= Received: by 10.43.69.209 with SMTP id yd17mr1707241icb.201.1307651690156; Thu, 09 Jun 2011 13:34:50 -0700 (PDT) Received: from argus.electron-tube.net (desm-45-047.dsl.netins.net [167.142.45.47]) by mx.google.com with ESMTPS id v15sm937814ibh.62.2011.06.09.13.34.37 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2011 13:34:49 -0700 (PDT) Message-ID: <4DF12E4A.5020906@gmail.com> Date: Thu, 09 Jun 2011 15:34:18 -0500 From: Jim Bryant User-Agent: Thunderbird 2.0.0.24 (X11/20100911) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: weongyo@FreeBSD.org, freebsd-usb@freebsd.org Subject: problem with urtw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 20:34:53 -0000 I just bought one of those chinese (apparently the same unit relabeled and being sold by multiple companies) realtek RTL8187B wifi units. The price is right. The label name on this one is WiFySky 1500mW. other than the fact that the case it is enclosed in is really cheesy, there is a more immediate problem with this. the current urtw driver returns a 6. here we go: on insert: ugen3.2: at usbus3 after kldload if_urtw.ko: urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 3:28:35pm argus(48): usbconfig -u 3 -a 2 dump_device_desc ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0bda idProduct = 0x8187 bcdDevice = 0x0200 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 3:28:48pm argus(49): usbconfig -u 3 -a 2 dump_curr_config_desc ugen3.2: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0051 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0004 bmAttributes = 0x0080 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0009 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0002 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0004 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0005 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 3 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0006 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 4 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0007 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 5 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0089 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 6 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x000a bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 7 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x000b bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 8 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x000c bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 If a verbose boot or any other info is needed to get this working, please tell me, and I'll get you the info. I do have to admit, at the price these are going for, they are rather nice, and do reach out and touch a router. Review complaints: heat dissipation. If you buy one, don't operate it in a hot environment. I'd like to see it working in FreeBSD, but I don't have a handle on the wifi driver structure. Linux source code was included on the driver disk. I can email that directly to whomever needs it for comparison. Thanks, Jim, KC5VDJ From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 21:57:17 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88E4E1065673 for ; Thu, 9 Jun 2011 21:57:17 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3A88B8FC27 for ; Thu, 9 Jun 2011 21:57:16 +0000 (UTC) Received: by vxc34 with SMTP id 34so2275311vxc.13 for ; Thu, 09 Jun 2011 14:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0jdxjCGEJ1a8fP/4idZPwj88mNLjV1vU0KQabb9gM4E=; b=prsJoFtDvwYTuxm+Tmr9GPcE0PVBEBHxMynQBeoZUplcJYS1urJx4v6OOvdmzD/9n/ kzhDxkjKqwaoizUEYXMFh67mLqA/cxzG8HKrU3cJZUAEAY90Q0X+3o/1IWcd9m15f58S ZQIQDKZ/vAHaVlR33gnnjc8V7uTNIyfDn8lHQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=w7Ek77/6D/u9wBNDXT034lTP5L+7Amq1sll24vzV0akjgVdxFZic28zi3JTjiAOwta 2OO4C/sbo6wuNJUtYdN8jXNz6DG6b3Ngf9Jflf+Zg7U816tQi6zPblwk4HtuPdGzkrfb USf8BADb8TA6ZY51Zdm+OJg3WwcK1Ouy1cADA= MIME-Version: 1.0 Received: by 10.236.88.51 with SMTP id z39mr1813624yhe.183.1307656635560; Thu, 09 Jun 2011 14:57:15 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.236.208.70 with HTTP; Thu, 9 Jun 2011 14:57:15 -0700 (PDT) In-Reply-To: <1307649610.2135.29.camel@ubuntu> References: <1307649610.2135.29.camel@ubuntu> Date: Thu, 9 Jun 2011 14:57:15 -0700 X-Google-Sender-Auth: 3dQXjmhZFNkZZ-Nk0rDmTG8fB28 Message-ID: From: Artem Belevich To: Greg Bonett Content-Type: text/plain; charset=ISO-8859-1 Cc: "stable@freebsd.org" Subject: Re: recover file from destroyed zfs snapshot - is it possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 21:57:17 -0000 On Thu, Jun 9, 2011 at 1:00 PM, Greg Bonett wrote: > Hi all, > I know this is a long shot, but I figure it's worth asking. Is there > anyway to recover a file from a zfs snapshot which was destroyed? I know > the name of the file and a unique string that should be in it. The zfs > pool is on geli devices so I can't dd the raw device and look for it. > Any suggestions? > > Thanks for the help. Theoretically it may be possible. Practically it will not be trivial. ZFS state at any given point in time is determined by it's uberblock. ZFS keeps number of previous uberblocks (and thus -- ZFS states). If you're familiar with ZDB and with ZFS filesystem layout, you may be able to use information in the last saved uberblock before the snapshot was nuked and, with some luck, would be able to find the data tat was in your file. That, however, relies on an optimistic assumption that a) such uberblock is still around and, b) appropriate disk blocks have not been reused by more recent transactions.I believe recent ZFS versions (v28 should qualify) make an effort to keep recent transaction groups in consistent state to improve chances of recovery with "zpool import -F" in case disks lied about cache flushes. In case you do want to dig in, ZFS on-disk data structures are documented here: http://opensolaris.org/os/community/zfs/docs/ondiskformat0822.pdf This script (WARNING -- DESCTRUCTIVE) should allow you to roll back ZFS state to an earlier point in time on single-device pools: http://www.solarisinternals.com/wiki/index.php/ZFS_forensics_scrollback_script Good luck. --Artem P.S. You wouldn't happen to have backup of your file, would you? That would make things so much easier. :-) From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 22:43:47 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0FBA1065677; Thu, 9 Jun 2011 22:43:47 +0000 (UTC) (envelope-from greg@bonett.org) Received: from bonett.org (bonett.org [66.249.7.150]) by mx1.freebsd.org (Postfix) with ESMTP id 0B1028FC1E; Thu, 9 Jun 2011 22:43:47 +0000 (UTC) Received: from [192.168.1.216] (unknown [76.91.19.169]) by bonett.org (Postfix) with ESMTPSA id BC168124245; Thu, 9 Jun 2011 22:43:45 +0000 (UTC) From: Greg Bonett To: Artem Belevich In-Reply-To: References: <1307649610.2135.29.camel@ubuntu> Content-Type: text/plain; charset="UTF-8" Date: Thu, 09 Jun 2011 15:43:44 -0700 Message-ID: <1307659424.2135.43.camel@ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" Subject: Re: recover file from destroyed zfs snapshot - is it possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 22:43:47 -0000 On Thu, 2011-06-09 at 14:57 -0700, Artem Belevich wrote: On Thu, Jun 9, 2011 at 1:00 PM, Greg Bonett wrote: > > Hi all, > > I know this is a long shot, but I figure it's worth asking. Is there > > anyway to recover a file from a zfs snapshot which was destroyed? I know > > the name of the file and a unique string that should be in it. The zfs > > pool is on geli devices so I can't dd the raw device and look for it. > > Any suggestions? > > > > Thanks for the help. > > Theoretically it may be possible. Practically it will not be trivial. > > ZFS state at any given point in time is determined by it's uberblock. > ZFS keeps number of previous uberblocks (and thus -- ZFS states). If > you're familiar with ZDB and with ZFS filesystem layout, you may be > able to use information in the last saved uberblock before the > snapshot was nuked and, with some luck, would be able to find the data > tat was in your file. That, however, relies on an optimistic > assumption that a) such uberblock is still around and, b) appropriate > disk blocks have not been reused by more recent transactions.I believe > recent ZFS versions (v28 should qualify) make an effort to keep recent > transaction groups in consistent state to improve chances of recovery > with "zpool import -F" in case disks lied about cache flushes. > > In case you do want to dig in, ZFS on-disk data structures are documented here: > http://opensolaris.org/os/community/zfs/docs/ondiskformat0822.pdf > > This script (WARNING -- DESCTRUCTIVE) should allow you to roll back > ZFS state to an earlier point in time on single-device pools: > http://www.solarisinternals.com/wiki/index.php/ZFS_forensics_scrollback_script > > Good luck. > > Thanks for the response. I'll follow these links and see if I think I can pull it off. One question though, you say it's necessary that "appropriate disk blocks have not been reused by more recent transactions" Is it not possible for me to just read all the disk blocks looking for the filename and string it contained? How big are disk blocks, is it possible the whole 16k file is on one or a few contiguous blocks? Thanks! -Greg --Artem > > P.S. You wouldn't happen to have backup of your file, would you? That > would make things so much easier. :-) > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu Jun 9 23:07:18 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B59A9106564A for ; Thu, 9 Jun 2011 23:07:18 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3688FC14 for ; Thu, 9 Jun 2011 23:07:18 +0000 (UTC) Received: by qyk27 with SMTP id 27so1367389qyk.13 for ; Thu, 09 Jun 2011 16:07:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=iQYdP9mU8Clnc2eJyD4OhhEe1HKFflpDsNMU2HYJy6A=; b=GdTEwnR3VL1JPxFE8tBfotsRb9ZU321wSatuGNPttBP1KUCsq5JehxQ7+NvzZ+Dz8x HSsgJmLXbT/6XY10G4rl1zawvxsgeLbn1WXa8+DhCdo5u3gLmeqcfe3dOln5dwFHqy7D xE5R6NapkhMyCHe6i35XVab4NBMWhAdupm6TY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=EMWBuCQF95+1l5q5ACPFjFLQEoOSo4UFCDMqMytK/puz2qBfykl8xy1qIBg0DOpvfn FK0OSLl42rOjX10rZA4/L7YZD5em+YLAj4KA24sdpkCCEP26Dw3Zk5E5ahQ9Pmn/50jM 5F0EoYS2jP9vMculciaq/ZvTbIJzqy2mGiChA= MIME-Version: 1.0 Received: by 10.229.130.141 with SMTP id t13mr1023831qcs.117.1307660837419; Thu, 09 Jun 2011 16:07:17 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.229.212.76 with HTTP; Thu, 9 Jun 2011 16:07:17 -0700 (PDT) In-Reply-To: <1307659424.2135.43.camel@ubuntu> References: <1307649610.2135.29.camel@ubuntu> <1307659424.2135.43.camel@ubuntu> Date: Thu, 9 Jun 2011 16:07:17 -0700 X-Google-Sender-Auth: djPr7mgRt662KSWaUZUXsHnPmMk Message-ID: From: Artem Belevich To: Greg Bonett Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "stable@freebsd.org" Subject: Re: recover file from destroyed zfs snapshot - is it possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2011 23:07:18 -0000 On Thu, Jun 9, 2011 at 3:43 PM, Greg Bonett wrote: > One question though, you say it's necessary that "appropriate > =A0disk blocks have not been reused by more recent transactions" > Is it not possible for me to just read all the disk blocks looking for > the filename and string it contained? How big are disk blocks, is it > possible the whole 16k file is on one or a few contiguous blocks? Whether all your data is in a single block would depend on how large the file is and how exactly it was written out. If it's something that's been written all at once, chances are that it will end up located sequentially somewhere on disk. If the file was written more than once, you may find several file variants. Telling which one is the most recent one without parsing ZFS metadata would be up to you. Another question is whether the content would be easy to identify. If you have compression turned on, then simple grepping for content will not work. So, if your pool does not have compression on, you know what was in the file and are reasonably sure that you will be able to tell whether the data you recover is consistent or not, then by all means start with searching for this content in a raw data. Default ZFS block size is 128K, so for the small file written at once there's a good chance that it's been written out in a single chunk. --Artem From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 01:16:31 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E03106566B for ; Fri, 10 Jun 2011 01:16:31 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 444878FC17 for ; Fri, 10 Jun 2011 01:16:30 +0000 (UTC) Received: by iyj12 with SMTP id 12so2615766iyj.13 for ; Thu, 09 Jun 2011 18:16:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :reply-to:references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=BYkxXxklQ9CQ/P12Rjo4lIVfkVvkYDa3uML+8WjjdYs=; b=bKWFKBxOzvacB8kGpAf1+C39Jplp2bZHiFXlcghCVTaMWH9oR9uR5/tJK6cZvLnAep F3uknOsU3H7WEy0DIJQewlVf8kBJB3IBeAnpMcqOisNRTphGLcznpFQzH5XltSm++G8c sCG1ZmygZXXhWPE+bq2cJ9t1oEMR38SOTov/U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :x-openpgp-key-id:x-openpgp-key-fingerprint:x-openpgp-key-url; b=W3RO1psGPpOWp895fLi/hPYreAtLYqTrYKD75yypSix6YbBEUV8C+R4l+mHDKzGRPR E+N2eQoFG1H+N5Gg2Vx65Fs+xQhczet26/q8sVSY+THkh7vpIQ4dDZiBFI1LOmXVekGH EXBy5UlVildzzshXJg4vlP8zBwkaOdR5dCypo= Received: by 10.42.35.198 with SMTP id r6mr1725342icd.240.1307668590493; Thu, 09 Jun 2011 18:16:30 -0700 (PDT) Received: from DataIX.net (adsl-99-181-139-216.dsl.klmzmi.sbcglobal.net [99.181.139.216]) by mx.google.com with ESMTPS id d6sm1825658icx.13.2011.06.09.18.16.27 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 09 Jun 2011 18:16:28 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p5A1GO8X048281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jun 2011 21:16:25 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p5A1GNa7048280; Thu, 9 Jun 2011 21:16:23 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Thu, 9 Jun 2011 21:16:23 -0400 From: Jason Hellenthal To: "C. P. Ghost" Message-ID: <20110610011623.GA45624@DataIX.net> References: <4DECB197.8020102@FreeBSD.org> <20110608211203.GA35440@alchemy.franken.de> <20110608225556.GQ7064@alchemy.franken.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-stable , Marius Strobl Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jhell@DataIX.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 01:16:31 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 09, 2011 at 12:59:39AM +0200, C. P. Ghost wrote: > On Thu, Jun 9, 2011 at 12:55 AM, Marius Strobl > wrote: > > On Thu, Jun 09, 2011 at 12:46:19AM +0200, C. P. Ghost wrote: > >> On Wed, Jun 8, 2011 at 11:12 PM, Marius Strobl > >> wrote: > >> > On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > >> >> Hi, > >> >> > >> >> I have merged ZFS version 28 to 8-STABLE (revision 222741) > >> >> > >> >> New major features: > >> >> > >> >> - data deduplication > >> >> - triple parity RAIDZ (RAIDZ3) > >> >> - zfs diff > >> >> - zpool split > >> >> - snapshot holds > >> >> - zpool import -F. Allows to rewind corrupted pool to earlier > >> >> ? transaction group > >> >> - possibility to import pool in read-only mode > >> >> > >> >> For updating, there is a compatibility layer so that in the update = phase > >> >> most functionality of the new zfs binaries can be used with the old > >> >> kernel module and old zfs binaries with the new kernel module. > >> > > >> > Beware that the compatibility layer is known broken on big-endian > >> > architectures, i.e. powerpc64 and sparc64. > >> > >> Thanks for the heads-up! I was just about to update a couple of sparc64 > >> machines here. Fortunately, the only ZFS file systems there are extern= al > >> file systems (no /, /usr, /var etc...), so it's gonna be painless, I s= uppose. > >> But what about other layouts? Does it mean that an installkernel, rebo= ot, > >> and installworld won't work? > > > > No, using the old zfs binaries with the new kernel module triggers the > > problem. Using the new zfs binaries with the new kernel module works > > (at least with CURRENT) so you'd need disregard everything that is > > documented and do what is not guaranteed to work but usually also does, > > i.e. do installkernel, installworld and then reboot. >=20 > Ah, yes, that's what I expected. Thank you! >=20 To add to this, what may or may not help you. If you installkernel+installworld and shutdown your pool might not umount cleanly or system might hang. If you create a copy of all the old zfs binaries into a seperate directory and run ldconfig -m /path/to/directory and make sure that the zfs and zpool binaries are in the PATH before shutdown for the scripts that run then you should be able to do this flawlessly and have a perfect working system after you reboot. This may require editing the zfs rcNG scripts to adjust the path for only shutdown. If all else fails remove the /boot/zfs/zpool.cache file after a reboot into single user mode then unload and reload the zfs and opensolaris modules and this should get you going in the right direction. Good luck. --=20 "Unity can only be manifested by the Binary. Unity itself and the idea of U= nity are already two." -- Buddha Regards, (jhell) Jason Hellenthal --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJN8XBmAAoJEJBXh4mJ2FR+ZiwH/RyirgX7KgnsKtZARN0Y60k4 YhoZbjevonyutcETENKo7D11WxcFKYhl9sS1oKmT+Qxlr69qJtEFGha2QlYN3V2h 62g+yGxm9N43ZoZygRkkTV3B74k8v+39Hj2H1TcYwpTBiajwvc6PGvsVZhqtY7aH THVwJtwPn/INv1T+hMsgyqa2yUAKZdUPIQrBj8jAiQqW/8dI4dRlg3UT+hiXqtpA amjqpWIbY3l15madIimL7RmAjOp4czpjhXB5h0izZz0XdfzR7Z52K1ribXul6fgV KAsTpOXlbNUDHmBAHb8trFw1GKd1HIctJ3jR6LRYSRsS8m6XrtjeJjWFn7j16Tg= =u+LK -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 07:23:31 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5B071065672 for ; Fri, 10 Jun 2011 07:23:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF1C8FC19 for ; Fri, 10 Jun 2011 07:23:30 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mailfe02.swip.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_20 autolearn=ham version=3.3.1 X-TFF-CGPSA-Version: 1.7 X-T2-CGPSA-Filter: Scanned X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=6YwywTXDltnW4viG0YW+xGnSOPPSCXZBKiVv2UswsZM= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=5u8LjNP_KlWWU78WeAoA:9 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 138465714; Fri, 10 Jun 2011 09:13:25 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 10 Jun 2011 09:12:02 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DF12E4A.5020906@gmail.com> In-Reply-To: <4DF12E4A.5020906@gmail.com> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106100912.02762.hselasky@c2i.net> Cc: weongyo@freebsd.org, freebsd-stable@freebsd.org, Jim Bryant Subject: Re: problem with urtw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 07:23:31 -0000 On Thursday 09 June 2011 22:34:18 Jim Bryant wrote: > I just bought one of those chinese (apparently the same unit relabeled > and being sold by multiple companies) realtek RTL8187B wifi units. The > price is right. > > The label name on this one is WiFySky 1500mW. > > other than the fact that the case it is enclosed in is really cheesy, > there is a more immediate problem with this. > > the current urtw driver returns a 6. > > here we go: > > on insert: > > ugen3.2: at usbus3 > > after kldload if_urtw.ko: > > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > > 3:28:35pm argus(48): usbconfig -u 3 -a 2 dump_device_desc > ugen3.2: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0bda > idProduct = 0x8187 > bcdDevice = 0x0200 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > 3:28:48pm argus(49): usbconfig -u 3 -a 2 dump_curr_config_desc > ugen3.2: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0051 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x0004 > bmAttributes = 0x0080 > bMaxPower = 0x00fa > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0009 > bInterfaceClass = 0x00ff > bInterfaceSubClass = 0x00ff > bInterfaceProtocol = 0x00ff > iInterface = 0x0002 > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0083 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 1 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0004 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 2 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0005 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 3 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0006 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 4 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0007 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 5 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0089 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 6 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000a > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 7 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000b > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 8 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000c > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > If a verbose boot or any other info is needed to get this working, > please tell me, and I'll get you the info. > > I do have to admit, at the price these are going for, they are rather > nice, and do reach out and touch a router. Review complaints: heat > dissipation. If you buy one, don't operate it in a hot environment. > I'd like to see it working in FreeBSD, but I don't have a handle on the > wifi driver structure. Linux source code was included on the driver > disk. I can email that directly to whomever needs it for comparison. > > > Thanks, > > Jim, KC5VDJ Hi, I think there is some firmware you need to load before it works. --HPS From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 07:40:43 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91DDA106566B; Fri, 10 Jun 2011 07:40:43 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A71DA8FC1A; Fri, 10 Jun 2011 07:40:42 +0000 (UTC) Received: by bwz12 with SMTP id 12so2808511bwz.13 for ; Fri, 10 Jun 2011 00:40:41 -0700 (PDT) Received: by 10.204.154.74 with SMTP id n10mr1552411bkw.33.1307690111949; Fri, 10 Jun 2011 00:15:11 -0700 (PDT) Received: from jessie.localnet (p5B2EC7C2.dip0.t-ipconnect.de [91.46.199.194]) by mx.google.com with ESMTPS id g2sm2271770bkz.23.2011.06.10.00.15.10 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 00:15:10 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Jim Bryant Date: Fri, 10 Jun 2011 09:12:47 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.32-32-generic; KDE/4.4.5; i686; ; ) References: <4DF12E4A.5020906@gmail.com> In-Reply-To: <4DF12E4A.5020906@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201106100913.42480.bschmidt@freebsd.org> Cc: weongyo@freebsd.org, freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: problem with urtw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bschmidt@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 07:40:43 -0000 On Thursday, June 09, 2011 22:34:18 Jim Bryant wrote: > I just bought one of those chinese (apparently the same unit relabeled > and being sold by multiple companies) realtek RTL8187B wifi units. The > price is right. > > The label name on this one is WiFySky 1500mW. > > other than the fact that the case it is enclosed in is really cheesy, > there is a more immediate problem with this. > > the current urtw driver returns a 6. > > here we go: > > on insert: > > ugen3.2: at usbus3 > > after kldload if_urtw.ko: > > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > urtw0: > on usbus3 > urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE > device_attach: urtw0 attach returned 6 > > 3:28:35pm argus(48): usbconfig -u 3 -a 2 dump_device_desc > ugen3.2: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x0bda > idProduct = 0x8187 > bcdDevice = 0x0200 > iManufacturer = 0x0001 > iProduct = 0x0002 > iSerialNumber = 0x0000 > bNumConfigurations = 0x0001 > > 3:28:48pm argus(49): usbconfig -u 3 -a 2 dump_curr_config_desc > ugen3.2: at usbus3, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0051 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x0004 > bmAttributes = 0x0080 > bMaxPower = 0x00fa > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x0000 > bAlternateSetting = 0x0000 > bNumEndpoints = 0x0009 > bInterfaceClass = 0x00ff > bInterfaceSubClass = 0x00ff > bInterfaceProtocol = 0x00ff > iInterface = 0x0002 > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0083 I have no clue what I'm talking about, so, this might be wrong.. Anyways.. the urtw(4) driver supports two different chips the 8187B and 8187L. One difference between those is the number of endpoints and its addresses. The 8187L uses 3 endpoints with 0x81 as the RX endpoint, the 8187B uses 7 endpoints with 0x83 as RX. % vendor REALTEK 0x0bda Realtek % product REALTEK RTL8187 0x8187 RTL8187 Wireless Adapter Quoting from the driver: % #define URTW_DEV_B(v,p) \ % { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, URTW_REV_RTL8187B) } % #define URTW_DEV_L(v,p) \ % { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, URTW_REV_RTL8187L) } % .. % static const struct usb_device_id urtw_devs[] = { % URTW_DEV_L(REALTEK, RTL8187), % .. % static const struct usb_config urtw_8187b_usbconfig[URTW_8187B_N_XFERS] = { % [URTW_8187B_BULK_RX] = { % .type = UE_BULK, % .endpoint = 0x83, % .. % static const struct usb_config urtw_8187l_usbconfig[URTW_8187L_N_XFERS] = { % [URTW_8187L_BULK_RX] = { % .type = UE_BULK, % .endpoint = 0x81, It occurs to me that yours might actually be a B chip not a L, because there is a 0x83 endpoint but none for 0x81. Wanna give that a shot? Index: if_urtw.c =================================================================== --- if_urtw.c (revision 222807) +++ if_urtw.c (working copy) @@ -112,7 +112,7 @@ static const struct usb_device_id urtw_devs[] = { URTW_DEV_L(BELKIN, F5D7050E), URTW_DEV_L(LINKSYS4, WUSB54GCV2), URTW_DEV_L(NETGEAR, WG111V2), - URTW_DEV_L(REALTEK, RTL8187), + URTW_DEV_B(REALTEK, RTL8187), URTW_DEV_L(SITECOMEU, WL168V1), URTW_DEV_L(SURECOM, EP9001G2A), { USB_VPI(0x1b75, 0x8187, URTW_REV_RTL8187L) }, > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 1 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0004 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 2 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0005 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 3 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0006 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 4 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0007 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 5 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0089 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 6 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000a > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 7 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000b > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > Endpoint 8 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x000c > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x0000 > bRefresh = 0x0000 > bSynchAddress = 0x0000 > > If a verbose boot or any other info is needed to get this working, > please tell me, and I'll get you the info. > > I do have to admit, at the price these are going for, they are rather > nice, and do reach out and touch a router. Review complaints: heat > dissipation. If you buy one, don't operate it in a hot environment. > I'd like to see it working in FreeBSD, but I don't have a handle on the > wifi driver structure. Linux source code was included on the driver > disk. I can email that directly to whomever needs it for comparison. > > > Thanks, > > Jim, KC5VDJ > > _______________________________________________ > 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" -- Bernhard From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 08:56:14 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6C6D1065675 for ; Fri, 10 Jun 2011 08:56:14 +0000 (UTC) (envelope-from bartosz.stec@it4pro.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 977DA8FC16 for ; Fri, 10 Jun 2011 08:56:14 +0000 (UTC) Received: from mb01.admin.lan.kkip.pl ([10.66.3.0]) by mainframe.kkip.pl with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QUxVe-0003Dl-Li; Fri, 10 Jun 2011 10:56:13 +0200 Message-ID: <4DF1DC26.5010600@it4pro.pl> Date: Fri, 10 Jun 2011 10:56:06 +0200 From: Bartosz Stec Organization: IT4Pro User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Andriy Gapon References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> In-Reply-To: <4DCD1672.4020405@FreeBSD.org> 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.76 (build at 12-May-2011 10:41:54) X-Date: 2011-06-10 10:56:13 X-Connected-IP: 10.66.3.0:4653 X-Message-Linecount: 46 X-Body-Linecount: 30 X-Message-Size: 1701 X-Body-Size: 890 X-Received-Count: 1 X-Recipient-Count: 2 X-Local-Recipient-Count: 2 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: FreeBSD Stable Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 08:56:15 -0000 W dniu 2011-05-13 13:30, Andriy Gapon pisze: > on 12/05/2011 22:43 Bartosz Stec said the following: >> Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=156974 >> > I suspect that your best course here is to add some diagnostic printfs in > igb_refresh_mbufs and in m_getzone to see what value is actually passed to > m_getjcl and why. > You're probably right, although I would need some guidance how to do it. Sorry :( Yesterday I rebuilt this machine with fresh sources to upgrade filesystem to ZFSv28 which was MFC'ed lately. After that server started to panic regardless of igb loaded as module or integrated into kernel. Finally I found that problem was caused by MSIX somehow. No more panic after hw.pci.enable_msix=0 was included in loader.conf. There's also no panic with GENERIC kernel. Should I really care abou MSIX? -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 09:37:29 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9D591065675 for ; Fri, 10 Jun 2011 09:37:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by mx1.freebsd.org (Postfix) with ESMTP id BD8198FC1A for ; Fri, 10 Jun 2011 09:37:29 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta11.emeryville.ca.mail.comcast.net with comcast id u9bF1g0011vN32cAB9dUtC; Fri, 10 Jun 2011 09:37:28 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id u9dP1g00H1t3BNj8i9dPoF; Fri, 10 Jun 2011 09:37:24 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 35D23102C19; Fri, 10 Jun 2011 02:37:28 -0700 (PDT) Date: Fri, 10 Jun 2011 02:37:28 -0700 From: Jeremy Chadwick To: Bartosz Stec Message-ID: <20110610093728.GA39453@icarus.home.lan> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DF1DC26.5010600@it4pro.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable , "Vogel, Jack" , Andriy Gapon Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 09:37:29 -0000 On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: > W dniu 2011-05-13 13:30, Andriy Gapon pisze: > >on 12/05/2011 22:43 Bartosz Stec said the following: > >>Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=156974 > >> > >I suspect that your best course here is to add some diagnostic printfs in > >igb_refresh_mbufs and in m_getzone to see what value is actually passed to > >m_getjcl and why. > > > You're probably right, although I would need some guidance how to do > it. Sorry :( > > Yesterday I rebuilt this machine with fresh sources to upgrade > filesystem to ZFSv28 which was MFC'ed lately. After that server > started to panic regardless of igb loaded as module or integrated > into kernel. > > Finally I found that problem was caused by MSIX somehow. > No more panic after > > hw.pci.enable_msix=0 > > was included in loader.conf. > > There's also no panic with GENERIC kernel. > > Should I really care abou MSIX? Yes, you absolutely should. The performance hit, depending on your interrupt load, can be quite dramatic with this turned off. Remember: what you just turned off was MSI-X for the *entire system*, not just for NICs. Please read about it here: http://en.wikipedia.org/wiki/Message_Signaled_Interrupts CC'ing Jack Vogel here, because your issue pertains to igb(4). Please provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as well as relevant dmesg info that pertains to them (driver, etc.). You can XXX out MAC addresses if you're worried. Jack, original thread starts here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#62596 -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 10:02:14 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1716C106564A for ; Fri, 10 Jun 2011 10:02:14 +0000 (UTC) (envelope-from bartosz.stec@it4pro.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 3408F8FC15 for ; Fri, 10 Jun 2011 10:02:12 +0000 (UTC) Received: from mb01.admin.lan.kkip.pl ([10.66.3.0]) by mainframe.kkip.pl with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1QUyXR-0009jc-Fb; Fri, 10 Jun 2011 12:02:09 +0200 Message-ID: <4DF1EB98.9080109@it4pro.pl> Date: Fri, 10 Jun 2011 12:02:00 +0200 From: Bartosz Stec Organization: IT4Pro User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jeremy Chadwick References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> <20110610093728.GA39453@icarus.home.lan> In-Reply-To: <20110610093728.GA39453@icarus.home.lan> 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.76 (build at 12-May-2011 10:41:54) X-Date: 2011-06-10 12:02:09 X-Connected-IP: 10.66.3.0:1511 X-Message-Linecount: 704 X-Body-Linecount: 687 X-Message-Size: 36654 X-Body-Size: 35717 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable , "Vogel, Jack" Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 10:02:14 -0000 W dniu 2011-06-10 11:37, Jeremy Chadwick pisze: > On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: >> W dniu 2011-05-13 13:30, Andriy Gapon pisze: >>> on 12/05/2011 22:43 Bartosz Stec said the following: >>>> Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=156974 >>>> >>> I suspect that your best course here is to add some diagnostic printfs in >>> igb_refresh_mbufs and in m_getzone to see what value is actually passed to >>> m_getjcl and why. >>> >> You're probably right, although I would need some guidance how to do >> it. Sorry :( >> >> Yesterday I rebuilt this machine with fresh sources to upgrade >> filesystem to ZFSv28 which was MFC'ed lately. After that server >> started to panic regardless of igb loaded as module or integrated >> into kernel. >> >> Finally I found that problem was caused by MSIX somehow. >> No more panic after >> >> hw.pci.enable_msix=0 >> >> was included in loader.conf. >> >> There's also no panic with GENERIC kernel. >> >> Should I really care abou MSIX? > Yes, you absolutely should. The performance hit, depending on your > interrupt load, can be quite dramatic with this turned off. Remember: > what you just turned off was MSI-X for the *entire system*, not just for > NICs. Please read about it here: > > http://en.wikipedia.org/wiki/Message_Signaled_Interrupts > > CC'ing Jack Vogel here, because your issue pertains to igb(4). Please > provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as > well as relevant dmesg info that pertains to them (driver, etc.). You > can XXX out MAC addresses if you're worried. > > Jack, original thread starts here: > > http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#62596 > Thanks Jeremy, you are helpful as always :) Full dmesg output (was already included in this thread): http://pastebin.com/Es0CKD64 #pciconf -lcvb hostb0@pci0:0:0:0: class=0x060000 card=0x330b103c chip=0x34068086 rev=0x13 hdr=0x00 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub to ESI Port' class = bridge subclass = HOST-PCI cap 05[60] = MSI supports 2 messages, vector masks cap 10[90] = PCI-Express 2 root port max data 128(128) link x4(x4) cap 01[e0] = powerspec 3 supports D0 D3 current D0 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] = unknown 1 ecap 000b[160] = unknown 0 pcib1@pci0:0:1:0: class=0x060400 card=0x330b103c chip=0x34088086 rev=0x13 hdr=0x01 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub PCI Express Root Port 1' class = bridge subclass = PCI-PCI cap 0d[40] = PCI Bridge card=0x330b103c cap 05[60] = MSI supports 2 messages, vector masks cap 10[90] = PCI-Express 2 root port max data 256(256) link x4(x4) cap 01[e0] = powerspec 3 supports D0 D3 current D0 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] = unknown 1 ecap 000b[160] = unknown 0 pcib2@pci0:0:3:0: class=0x060400 card=0x330b103c chip=0x340a8086 rev=0x13 hdr=0x01 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub PCI Express Root Port 3' class = bridge subclass = PCI-PCI cap 0d[40] = PCI Bridge card=0x330b103c cap 05[60] = MSI supports 2 messages, vector masks cap 10[90] = PCI-Express 2 root port max data 256(256) link x0(x16) cap 01[e0] = powerspec 3 supports D0 D3 current D0 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] = unknown 1 ecap 000b[160] = unknown 0 pcib3@pci0:0:7:0: class=0x060400 card=0x330b103c chip=0x340e8086 rev=0x13 hdr=0x01 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub PCI Express Root Port 7' class = bridge subclass = PCI-PCI cap 0d[40] = PCI Bridge card=0x330b103c cap 05[60] = MSI supports 2 messages, vector masks cap 10[90] = PCI-Express 2 root port max data 256(256) link x0(x16) cap 01[e0] = powerspec 3 supports D0 D3 current D0 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] = unknown 1 ecap 000b[160] = unknown 0 pcib4@pci0:0:9:0: class=0x060400 card=0x330b103c chip=0x34108086 rev=0x13 hdr=0x01 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub PCI Express Root Port 9' class = bridge subclass = PCI-PCI cap 0d[40] = PCI Bridge card=0x330b103c cap 05[60] = MSI supports 2 messages, vector masks cap 10[90] = PCI-Express 2 root port max data 256(256) link x0(x4) cap 01[e0] = powerspec 3 supports D0 D3 current D0 ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] = unknown 1 none0@pci0:0:20:0: class=0x080000 card=0x000b003c chip=0x342e8086 rev=0x13 hdr=0x00 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub System Management Registers' class = base peripheral subclass = interrupt controller cap 10[40] = PCI-Express 2 root endpoint max data 128(128) link x0(x0) none1@pci0:0:20:1: class=0x080000 card=0x000b003c chip=0x34228086 rev=0x13 hdr=0x00 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub GPIO and Scratch Pad Registers' class = base peripheral subclass = interrupt controller cap 10[40] = PCI-Express 2 root endpoint max data 128(128) link x0(x0) none2@pci0:0:20:2: class=0x080000 card=0x000b003c chip=0x34238086 rev=0x13 hdr=0x00 vendor = 'Intel Corporation' device = 'QuickPath Architecture I/O Hub Control Status and RAS Registers' class = base peripheral subclass = interrupt controller cap 10[40] = PCI-Express 2 root endpoint max data 128(128) link x0(x0) uhci0@pci0:0:26:0: class=0x0c0300 card=0x330b103c chip=0x3a378086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB UHCI Controller *4' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xc800, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP ehci0@pci0:0:26:7: class=0x0c0320 card=0x330b103c chip=0x3a3c8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB EHCI Controller *2' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xfaff8000, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP pcib5@pci0:0:28:0: class=0x060400 card=0x330b103c chip=0x3a408086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = 'PCI Express Port 1' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 1 root port max data 128(128) link x0(x4) cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x330b103c cap 01[a0] = powerspec 2 supports D0 D3 current D0 ecap 0002[100] = VC 1 max VC0 ecap 0005[180] = unknown 1 pcib6@pci0:0:28:4: class=0x060400 card=0x330b103c chip=0x3a488086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = 'PCI Express Port 5' class = bridge subclass = PCI-PCI cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x2) cap 05[80] = MSI supports 1 message cap 0d[90] = PCI Bridge card=0x330b103c cap 01[a0] = powerspec 2 supports D0 D3 current D0 ecap 0002[100] = VC 1 max VC0 ecap 0005[180] = unknown 1 uhci1@pci0:0:29:0: class=0x0c0300 card=0x330b103c chip=0x3a348086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB UHCI Controller *1' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xc880, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci2@pci0:0:29:1: class=0x0c0300 card=0x330b103c chip=0x3a358086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB UHCI Controller *2' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xcc00, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP uhci3@pci0:0:29:2: class=0x0c0300 card=0x330b103c chip=0x3a368086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB UHCI Controller *3' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xd000, size 32, enabled cap 13[50] = PCI Advanced Features: FLR TP ehci1@pci0:0:29:7: class=0x0c0320 card=0x330b103c chip=0x3a3a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'USB EHCI Controller *1' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xfaffa000, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP pcib7@pci0:0:30:0: class=0x060401 card=0x330b103c chip=0x244e8086 rev=0x90 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI cap 0d[50] = PCI Bridge card=0x330b103c isab0@pci0:0:31:0: class=0x060100 card=0x330b103c chip=0x3a168086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'LPC Interface Controller' class = bridge subclass = PCI-ISA cap 09[e0] = vendor (length 12) Intel cap 1 version 0 features: SATA RAID-5, 4 PCI-e x1 slots atapci0@pci0:0:31:2: class=0x010601 card=0x330b103c chip=0x3a228086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '6 port SATA AHCI Controller' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0xd880, size 8, enabled bar [14] = type I/O Port, range 32, base 0xd800, size 4, enabled bar [18] = type I/O Port, range 32, base 0xd480, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xd400, size 4, enabled bar [20] = type I/O Port, range 32, base 0xd080, size 32, enabled bar [24] = type Memory, range 32, base 0xfaffc000, size 2048, enabled cap 05[80] = MSI supports 16 messages cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair cap 13[b0] = PCI Advanced Features: FLR TP igb0@pci0:7:0:0: class=0x020000 card=0x323f103c chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfbe60000, size 131072, enabled bar [14] = type Memory, range 32, base 0xfbe40000, size 131072, enabled bar [18] = type I/O Port, range 32, base 0xe880, size 32, enabled cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks enabled with 1 message cap 11[70] = MSI-X supports 10 messages in map 0x1c cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x4(x4) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 d8d385ffffe3e4f6 ecap 000e[150] = unknown 1 ecap 0010[160] = unknown 1 igb1@pci0:7:0:1: class=0x020000 card=0x323f103c chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfbee0000, size 131072, enabled bar [14] = type Memory, range 32, base 0xfbec0000, size 131072, enabled bar [18] = type I/O Port, range 32, base 0xec00, size 32, enabled cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks enabled with 1 message cap 11[70] = MSI-X supports 10 messages in map 0x1c cap 10[a0] = PCI-Express 2 endpoint max data 256(512) link x4(x4) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 d8d385ffffe3e4f6 ecap 000e[150] = unknown 1 ecap 0010[160] = unknown 1 vgapci0@pci0:2:0:0: class=0x030000 card=0x010019a2 chip=0x0522102b rev=0x02 hdr=0x00 vendor = 'Matrox Electronic Systems Ltd.' device = 'Matrox G200e (ServerEngines) - English (G200e)' class = display subclass = VGA bar [10] = type Prefetchable Memory, range 32, base 0xf8000000, size 16777216, enabled bar [14] = type Memory, range 32, base 0xfbdfc000, size 16384, enabled bar [18] = type Memory, range 32, base 0xfb000000, size 8388608, enabled cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 10[e4] = PCI-Express 1 legacy endpoint max data 128(128) link x1(x1) cap 05[54] = MSI supports 1 message -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 11:13:13 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6C2E106564A for ; Fri, 10 Jun 2011 11:13:13 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id A73FD8FC0A for ; Fri, 10 Jun 2011 11:13:11 +0000 (UTC) Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 056001B16; Fri, 10 Jun 2011 13:13:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= user-agent:in-reply-to:content-disposition:content-type :content-type:mime-version:references:message-id:subject:subject :from:from:date:date:received:received; s=mail; t=1307704388; x= 1309518788; bh=B0KByhGNL6JK5XlgfhR/raoP1Yt+URqs4aHBJLiBJhs=; b=e Z/YeHhlHfWHWk3rbvGm4aWnA7XJe1qgPmtwSC7nKrDmx16XYu5XCRSnreSYEWZk9 UXT/ektbhqr8hn+22j76n2YDsqZ85/GRTXwVDN0VW0LKcSRsnKlJVh26/NTYh83J OAhRzsiKHWXDmgl6YzRriSBSrpuA6pa0Uk/JI+xO2c= X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by megatron.madpilot.net (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Q5BridWKuZbw; Fri, 10 Jun 2011 13:13:08 +0200 (CEST) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 0E70F1B0E; Fri, 10 Jun 2011 13:13:07 +0200 (CEST) Date: Fri, 10 Jun 2011 13:13:07 +0200 From: Guido Falsi To: John Baldwin Message-ID: <20110610111307.GD76732@megatron.madpilot.net> References: <20110609152820.GC57263@megatron.madpilot.net> <201106091543.16028.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201106091543.16028.jhb@freebsd.org> X-Operating-System: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: BTX loader problem on specific hardware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 11:13:13 -0000 On Thu, Jun 09, 2011 at 03:43:15PM -0400, John Baldwin wrote: > On Thursday, June 09, 2011 11:28:20 am Guido Falsi wrote: > > > > I'm having a problem with BTX hanging on an HP 6005 Pro PC. > > > > I have filed a followup to an existing PR about this exact problem: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=151122 > > > > Hmm, these are not so easy to debug. You can try putting a 'foo: jmp foo' Thank you for your reply! I have something to try now, at least :P I really see the difficulty in this kind of debugging. It's something I'd really like to help solve, if possible. I forgot to mention that I fear the blame goes to the machine BIOS, and the FreeBSD boot loaders are just victims. > instruction in various places as a sort of 'while (1)' loop. The first test I > would do is to put it earlier in btxld before the messages that BTXLDR_VERBOSE > logs to see if when it hangs the cursor stays at its current location rather > than jumping back up. If that works out then you can start moving the 'foo: > jmp foo' later until you find a point where it hangs and moves the cursor > (which means it hung in between your previous 'jmp foo' and the one you most > recently added). I would start by walking down through btxldr.S. If it makes > it all the way through that, start walking through the BTX init code. Unluckily it did not work this well. Wherever I put the loop in btxldr makes the cursor go to the top and stay there, the machine hanging.(num lock not reacting too) This happens even if the loop is the first statement, but I observed a small delay from when the code reaches the loop and the hang. It looks like something times out. Considering what I write below I have a theory about boot2 leaving something in an incorrect state for whatever stage comes next. > > Oddly enough, BTX had to run at least once so that boot2 could find the loader > and kick off the btxldr.S. I experimented with boot2 too. I tried to make boot2 load the kernel directly (as described in boot(8)) and got this error from BTX: / FreeBSD/x86 boot Default: 0:ad(0,a)/boot/loader boot: 0:da(0,a)/boot/kernel/kernel-_ int=00000006 err=00000000 efl=00010002 eip=23ec42c6 eax=0018e070 ebx=00000000 ecx=00000000 edx=a0500004 esi=ffff6000 edi=0018e070 ebp=000003fa esp=00210608 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip=ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff es:esp=d9 03 00 00 00 00 00 00-00 00 00 00 00 00 20 00 40 00 60 00 8d 64 24 00-55 4e 44 49 16 1d 00 00 BTX halted (the -_ after kernel are the spinner and the cursor, which really are in the same place) This makes me think that it is really boot2 to blame, I'm trying to understand something there, but I'm really stuck. I'm trying to add some output to boot2 to see what it is doing. I don't really know what to look for though. The above error is fully reproduceable giving always the exact same values in the dump. I also filed this information as a followup to PR i386/151122. -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 12:37:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D17A61065674 for ; Fri, 10 Jun 2011 12:37:45 +0000 (UTC) (envelope-from howie@thingy.com) Received: from post1.inband.network-i.net (tobago.network-i.net [212.21.96.30]) by mx1.freebsd.org (Postfix) with SMTP id 4D8F28FC18 for ; Fri, 10 Jun 2011 12:37:44 +0000 (UTC) Received: (qmail 61095 invoked from network); 10 Jun 2011 12:05:54 -0000 Received: from unknown (HELO ?10.1.1.188?) (212.21.99.52) by post2.inband.network-i.net with SMTP; 10 Jun 2011 12:05:54 -0000 Message-ID: <4DF209D6.4000107@thingy.com> Date: Fri, 10 Jun 2011 13:11:02 +0100 From: Howard Jones User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS on 8.1 - various problems after a disk failure. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 12:37:45 -0000 I have a FreeBSD 8.2 server at home with 4 2TB drives in it running ZFS in a raidz. Some time ago, I had a disk fail. Initially it wasn't totally obvious the disk had failed so I ran a 'zpool scrub' on the pool, which threw up a lot of errors, and also produces a lot of sense errors, making it obvious I had a dead disk. I replaced the disk, then ran "zpool replace zjumbo ad4 ad4" to replace the bad disk in-place, and start a resilver. Now I have a few problems: 1) The old ad4 is still listed, even after several scrub/resilvers. Shouldn't it go away? 2) Although I lost a whole directory with ~1TB of music, the space allocated to that directory is still around according df. 3) I have another bunch of files that appear in directory listings, but if I get "Illegal byte sequence" errors when trying to read them (with anything - du, file, wc). I have backups of most of the stuff on the pool (although it'd be nice to recover the more recent data), but how do I get out of this situation without nuking the site from orbit? (my current plan) Firstly, to get a reliable representation of what's actually on the filesystem, and for bonus points, getting back some of the data that should be intact (only one disk in the set was actually bad, right?). Here's my current zpool status. Thanks in advance for any pointers! Howie # zpool status pool: zjumbo state: DEGRADED status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: resilver completed after 10h57m with 15190 errors on Thu May 19 09:26:59 2011 config: NAME STATE READ WRITE CKSUM zjumbo DEGRADED 0 0 199K raidz1 DEGRADED 0 0 792K replacing DEGRADED 0 0 0 ad4/old UNAVAIL 0 16.1M 0 cannot open ad4 ONLINE 0 0 0 1.15T resilvered ad6 ONLINE 0 0 0 677M resilvered ad8 ONLINE 0 0 0 660M resilvered ad10 ONLINE 0 0 0 535M resilvered errors: 15190 data errors, use '-v' for a list From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 13:43:04 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B8D91065674 for ; Fri, 10 Jun 2011 13:43:04 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id D83298FC0C for ; Fri, 10 Jun 2011 13:43:03 +0000 (UTC) Received: by qyk27 with SMTP id 27so1764270qyk.13 for ; Fri, 10 Jun 2011 06:43:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TyXY3xZwbxsjV/La3Ewl7APdwH0jbP+FnIymO8BC8H8=; b=jDWB1OOlQHoGeLvTNnPIJvBhft5L3Wy85iXwY7ZXivBJUY/VpjMZXUVLlVhau/itsX 7bGIyOKCizVTZcZAa7VbmMITuO7sWHA3ASKbhs5g4NmHkqzJiBXThplcKNQF36aZkhK/ FKNvLxym387tb5NxDcPxpywwgYajKRNKjjYv4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Fv5bQ8nk4twOF7RxQ+Wa8CHvZuqBLHoYNRrFQxSsAgHEd7VGBbJs+J54fizpa1PMsa uVoB1Z709vo/nJbw0D7hE47lrEMOMkhDsPJ/lbNKZpzcuPYMZLtWs75TeG+nGTaDGe7I Mnvjs6QF8RSGoHF/XwyHwIQJ8xnEGYU0JzrcI= MIME-Version: 1.0 Received: by 10.229.43.99 with SMTP id v35mr1576264qce.8.1307712056510; Fri, 10 Jun 2011 06:20:56 -0700 (PDT) Received: by 10.229.99.197 with HTTP; Fri, 10 Jun 2011 06:20:56 -0700 (PDT) In-Reply-To: <4DF126B5.8040800@gmail.com> References: <4DF126B5.8040800@gmail.com> Date: Fri, 10 Jun 2011 17:20:56 +0400 Message-ID: From: Sergey Kandaurov To: Jim Bryant Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kvm_open errors on /proc/*/mem in top X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 13:43:04 -0000 On 10 June 2011 00:01, Jim Bryant wrote: > i'm not sure which list this belongs to, so i'm posting to -hackers and > -stable. > > i've noticed for a while now that during heavy activity (for instance > buildworld), that top will get these kvm_read errors when reading proc > mem entries. Hi. I think that is a question of whether it's acceptable to hide all errors originated in kvm(3): Index: usr.bin/top/machine.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- usr.bin/top/machine.c (revision 222893) +++ usr.bin/top/machine.c (working copy) @@ -265,7 +265,7 @@ else if (namelength > UPUNAMELEN) namelength =3D UPUNAMELEN; - kd =3D kvm_open(NULL, _PATH_DEVNULL, NULL, O_RDONLY, "kvm_open"); + kd =3D kvm_open(NULL, _PATH_DEVNULL, NULL, O_RDONLY, NULL); if (kd =3D=3D NULL) return (-1); Or rewrite top(1) a little more to open kvm with kvm_openfiles(), to let the caller decide itself in what places it needs to print an error with kvm_geterr(). > > i have included a screenshot of what happens during such events... > > last pid: 92024; =A0load averages: =A04.79, =A04.58, > 4.10 > up 0+00:49:07 =A015:30:53 > 225 processes: 10 running, 197 sleeping, 18 waiting > CPU: 90.6% user, =A00.0% nice, =A09.4% system, =A00.0% interrupt, =A00.0%= idle > Mem: 493M Active, 1337M Inact, 604M Wired, 632K Cache, 315M Buf, 524M Fre= e > Swap: 4097M Total, 4097M Free > kvm_open: cannot open /proc/86755/mem > =A0PID USERNAME =A0 =A0THR PRI NICE =A0 SIZE =A0 =A0RES STATE =A0 C =A0 T= IME =A0 WCPU COMMAND > 91943 root =A0 =A0 =A0 =A0 =A01 =A097 =A0 =A00 39536K 33620K RUN =A0 =A0 = 1 =A0 0:01 =A07.37% > [cc1plus] > 2859 jbryant =A0 =A0 =A0 1 =A048 =A0 =A00 =A0 406M 72332K select =A00 =A0= 3:10 =A05.96% > kwin -session 1028b2382461f5000127042056000000019550000_13 > 2747 root =A0 =A0 =A0 =A0 =A01 =A046 =A0 =A00 =A0 419M =A0 370M select = =A00 =A0 1:43 =A04.39% > /usr/local/bin/X :0 -nolisten tcp -auth /var/run/xauth/A:0 > 1464 root =A0 =A0 =A0 =A0 =A01 =A044 =A0 =A00 =A08068K =A01384K select = =A00 =A0 0:03 =A00.39% > /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.u > 11219 jbryant =A0 =A0 =A0 7 =A044 =A0 =A00 =A0 299M =A0 109M select =A01 = =A0 0:17 =A00.29% > /usr/local/lib/thunderbird/thunderbird-bin > 2865 jbryant =A0 =A0 =A0 1 =A045 =A0 =A00 =A0 453M 86140K select =A00 =A0= 0:21 =A00.20% > kdeinit4: kdeinit4: plasma-desktop (kdeinit4) > 2882 jbryant =A0 =A0 =A0 1 =A044 =A0 =A00 =A0 391M 60996K select =A00 =A0= 0:17 =A00.10% > kdeinit4: kdeinit4: kmix -session 102511e52251c60001304471 > 92001 root =A0 =A0 =A0 =A0 =A01 =A097 =A0 =A00 23452K 22256K CPU1 =A0 =A0= 1 =A0 0:00 =A00.00% [cc1] > 92017 root =A0 =A0 =A0 =A0 =A01 =A096 =A0 =A00 16172K 13440K RUN =A0 =A0 = 0 =A0 0:00 =A00.00% [cc1] > [snip] --=20 wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 17:05:49 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BFE3106564A for ; Fri, 10 Jun 2011 17:05:49 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A7B038FC08 for ; Fri, 10 Jun 2011 17:05:48 +0000 (UTC) Received: by fxm11 with SMTP id 11so2577774fxm.13 for ; Fri, 10 Jun 2011 10:05:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=Ng8F86eZbW/m5zb9AdCNW5VupsjquGnDMFR4sc5B39g=; b=gVg9dqQxoCt8zWNuYg1dIy/31r2g2gT8o4a+pTQfyXWnLr3uxr50Fsj96JKUU2gGrR ljfyjSMMfthUIEDz9WpMqW8YFLv6EkzOk76MzfiK4IK7WL35P2AbJiYORnW232kjOmf1 9m+BB0HDwVz+0MBxdeVlTJNtgdYJbXwkCcB6I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=Lp55jgEV1ulM5b+Rt1YlcTXlInwZnvhknwaLAmYW89O3+4H95Rxb1x6FuOnUR2sruD BHZtO/6ZlH73kCZEbBACxGGxbyi85LwKevCWKmHft5QWDrezPIiVJrUtd5oVXz2az5R4 zbhM3dqqEEEAKaIjWUpLufglVj7K4ier4tKpQ= Received: by 10.223.64.66 with SMTP id d2mr313415fai.116.1307725547495; Fri, 10 Jun 2011 10:05:47 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id q21sm1135484fan.16.2011.06.10.10.05.44 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Jun 2011 10:05:45 -0700 (PDT) From: Mikolaj Golub To: Daniel Kalchev References: <4DE21C64.8060107@digsys.bg> <4DE3ACF8.4070809@digsys.bg> <86d3j02fox.fsf@kopusha.home.net> <4DE4E43B.7030302@digsys.bg> <86zkm3t11g.fsf@in138.ua3> <4DE5048B.3080206@digsys.bg> <4DE5D535.20804@digsys.bg> <4DE8FE78.6070401@digsys.bg> <4DE90955.9020505@digsys.bg> X-Comment-To: Daniel Kalchev Sender: Mikolaj Golub Date: Fri, 10 Jun 2011 20:05:43 +0300 In-Reply-To: <4DE90955.9020505@digsys.bg> (Daniel Kalchev's message of "Fri, 03 Jun 2011 19:18:29 +0300") Message-ID: <86zklp8vmg.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org Subject: Re: HAST instability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 17:05:49 -0000 On Fri, 03 Jun 2011 19:18:29 +0300 Daniel Kalchev wrote: DK> Well, apparently my HAST joy was short. On a second run, I got stuck with DK> Jun 3 19:08:16 b1a hastd[1900]: [data2] (primary) Unable to receive DK> reply header: Operation timed out. DK> on the primary. No messages on the secondary. DK> On primary: DK> # netstat -an | grep 8457 DK> tcp4 0 0 10.2.101.11.42659 10.2.101.12.8457 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.11.62058 10.2.101.12.8457 CLOSE_WAIT DK> tcp4 0 0 10.2.101.11.34646 10.2.101.12.8457 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.11.11419 10.2.101.12.8457 CLOSE_WAIT DK> tcp4 0 0 10.2.101.11.37773 10.2.101.12.8457 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.11.21911 10.2.101.12.8457 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.11.40169 10.2.101.12.8457 CLOSE_WAIT DK> tcp4 0 97749 10.2.101.11.44360 10.2.101.12.8457 CLOSE_WAIT DK> tcp4 0 0 10.2.101.11.8457 *.* LISTEN DK> on secondary DK> # netstat -an | grep 8457 DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.42659 CLOSE_WAIT DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.62058 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.34646 CLOSE_WAIT DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.11419 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.37773 CLOSE_WAIT DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.21911 CLOSE_WAIT DK> tcp4 0 0 10.2.101.12.8457 10.2.101.11.40169 FIN_WAIT_2 DK> tcp4 66415 0 10.2.101.12.8457 10.2.101.11.44360 FIN_WAIT_2 DK> tcp4 0 0 10.2.101.12.8457 *.* LISTEN DK> on primary DK> # hastctl status DK> data0: DK> role: primary DK> provname: data0 DK> localpath: /dev/gpt/data0 DK> extentsize: 2097152 (2.0MB) DK> keepdirty: 64 DK> remoteaddr: 10.2.101.12 DK> sourceaddr: 10.2.101.11 DK> replication: fullsync DK> status: complete DK> dirty: 0 (0B) DK> data1: DK> role: primary DK> provname: data1 DK> localpath: /dev/gpt/data1 DK> extentsize: 2097152 (2.0MB) DK> keepdirty: 64 DK> remoteaddr: 10.2.101.12 DK> sourceaddr: 10.2.101.11 DK> replication: fullsync DK> status: complete DK> dirty: 0 (0B) DK> data2: DK> role: primary DK> provname: data2 DK> localpath: /dev/gpt/data2 DK> extentsize: 2097152 (2.0MB) DK> keepdirty: 64 DK> remoteaddr: 10.2.101.12 DK> sourceaddr: 10.2.101.11 DK> replication: fullsync DK> status: complete DK> dirty: 6291456 (6.0MB) DK> data3: DK> role: primary DK> provname: data3 DK> localpath: /dev/gpt/data3 DK> extentsize: 2097152 (2.0MB) DK> keepdirty: 64 DK> remoteaddr: 10.2.101.12 DK> sourceaddr: 10.2.101.11 DK> replication: fullsync DK> status: complete DK> dirty: 0 (0B) DK> Sits in this state for over 10 minutes. DK> Unfortunately, no KDB in kernel. Any ideas what other to look for? Could you please try this patch? http://people.freebsd.org/~trociny/hastd.no_shutdown.patch After patching you need to rebuild hastd and restart it (I expect only on secondary is enough but it is better to do this on both nodes). No server restart is needed. -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 17:07:43 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA690106567A for ; Fri, 10 Jun 2011 17:07:43 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3DF458FC16 for ; Fri, 10 Jun 2011 17:07:42 +0000 (UTC) Received: by fxm11 with SMTP id 11so2579235fxm.13 for ; Fri, 10 Jun 2011 10:07:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:references:x-comment-to :sender:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=3+7MdbzPkdbegpj98DZQa9oun25qvVfGdPRdTf7i0zQ=; b=NPDakLHV70t765SOXtTwIKDqnk1Yl6XE1lV46KywN5z488hso2vesYHQmLM3ktGAKi V9zr4b9nfsKxWrxE5x7IVH7geAH7nd7cjdEbRMmC6XRCrix8nMskxDHKNjMNjQVlUWzS tTIBBEE5BLUutI95wQHLZEEtQMT+QdmBoAlb0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:x-comment-to:sender:date:in-reply-to :message-id:user-agent:mime-version:content-type; b=P1x4uh5wDdzq2/GM4VjlGjRk0FQ62fdfzIHKxwfFwNPsYcLSz8VcEO5EMSNsdsUsGp 9M+fYCKaALqw/c403+UxB2ingt0W9ABWE0E8mfsqUw8ZsWHFMyGsnf1X7RX6JugLyT9Z yfJHglNOFBpqYVbafxLOMaVE4MnGEV9f3uSIg= Received: by 10.223.10.150 with SMTP id p22mr2266731fap.86.1307725662189; Fri, 10 Jun 2011 10:07:42 -0700 (PDT) Received: from localhost ([95.69.172.154]) by mx.google.com with ESMTPS id l26sm1135779fah.14.2011.06.10.10.07.40 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Jun 2011 10:07:40 -0700 (PDT) From: Mikolaj Golub To: Daniel Kalchev References: <4DE21C64.8060107@digsys.bg> <4DE3ACF8.4070809@digsys.bg> <86d3j02fox.fsf@kopusha.home.net> <4DE4E43B.7030302@digsys.bg> <86zkm3t11g.fsf@in138.ua3> <4DE5048B.3080206@digsys.bg> <4DE5D535.20804@digsys.bg> <4DE8FE78.6070401@digsys.bg> <4DE90955.9020505@digsys.bg> <86zklp8vmg.fsf@kopusha.home.net> X-Comment-To: Mikolaj Golub Sender: Mikolaj Golub Date: Fri, 10 Jun 2011 20:07:39 +0300 In-Reply-To: <86zklp8vmg.fsf@kopusha.home.net> (Mikolaj Golub's message of "Fri, 10 Jun 2011 20:05:43 +0300") Message-ID: <86vcwd8vj8.fsf@kopusha.home.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org Subject: Re: HAST instability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 17:07:43 -0000 On Fri, 10 Jun 2011 20:05:43 +0300 Mikolaj Golub wrote to Daniel Kalchev: MG> Could you please try this patch? MG> http://people.freebsd.org/~trociny/hastd.no_shutdown.patch Sure you still have to have your kernel patched with uipc_socket.c.patch :-) -- Mikolaj Golub From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 18:26:35 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 721681065670 for ; Fri, 10 Jun 2011 18:26:35 +0000 (UTC) (envelope-from jack.vogel@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id 4BDF58FC0C for ; Fri, 10 Jun 2011 18:26:35 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 10 Jun 2011 11:23:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,348,1304319600"; d="scan'208,217";a="16893832" Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by fmsmga001.fm.intel.com with ESMTP; 10 Jun 2011 11:23:28 -0700 Received: from orsmsx508.amr.corp.intel.com ([10.22.226.46]) by orsmsx602.amr.corp.intel.com ([10.22.226.211]) with mapi; Fri, 10 Jun 2011 11:23:28 -0700 From: "Vogel, Jack" To: Bartosz Stec , Jeremy Chadwick Date: Fri, 10 Jun 2011 11:23:26 -0700 Thread-Topic: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE Thread-Index: AcwnVYBUcuo8XheLQNWOHMu2XuizMgARbQUg Message-ID: <1DB50624F8348F48840F2E2CF6040A9D018ACA75C7@orsmsx508.amr.corp.intel.com> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> <20110610093728.GA39453@icarus.home.lan> <4DF1EB98.9080109@it4pro.pl> In-Reply-To: <4DF1EB98.9080109@it4pro.pl> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: RE: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 18:26:35 -0000 Er, so what if you get rid of ZFS, does your panic go away? It doesn't rea= lly matter what type adapter it is, the igb driver only requests standard s= ize clusters, so memory is getting trashed somewhere I suspect. Jack From: Bartosz Stec [mailto:bartosz.stec@it4pro.pl] Sent: Friday, June 10, 2011 3:02 AM To: Jeremy Chadwick Cc: FreeBSD Stable; Vogel, Jack Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest = STABLE W dniu 2011-06-10 11:37, Jeremy Chadwick pisze: On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: W dniu 2011-05-13 13:30, Andriy Gapon pisze: on 12/05/2011 22:43 Bartosz Stec said the following: Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi= ?pr=3D156974 I suspect that your best course here is to add some diagnostic printfs in igb_refresh_mbufs and in m_getzone to see what value is actually passed to m_getjcl and why. You're probably right, although I would need some guidance how to do it. Sorry :( Yesterday I rebuilt this machine with fresh sources to upgrade filesystem to ZFSv28 which was MFC'ed lately. After that server started to panic regardless of igb loaded as module or integrated into kernel. Finally I found that problem was caused by MSIX somehow. No more panic after hw.pci.enable_msix=3D0 was included in loader.conf. There's also no panic with GENERIC kernel. Should I really care abou MSIX? Yes, you absolutely should. The performance hit, depending on your interrupt load, can be quite dramatic with this turned off. Remember: what you just turned off was MSI-X for the *entire system*, not just for NICs. Please read about it here: http://en.wikipedia.org/wiki/Message_Signaled_Interrupts CC'ing Jack Vogel here, because your issue pertains to igb(4). Please provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as well as relevant dmesg info that pertains to them (driver, etc.). You can XXX out MAC addresses if you're worried. Jack, original thread starts here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#6259= 6 Thanks Jeremy, you are helpful as always :) Full dmesg output (was already included in this thread): http://pastebin.co= m/Es0CKD64 #pciconf -lcvb hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x330b103c chip=3D0x34068086 = rev=3D0x13 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub to ESI Port' class =3D bridge subclass =3D HOST-PCI cap 05[60] =3D MSI supports 2 messages, vector masks cap 10[90] =3D PCI-Express 2 root port max data 128(128) link x4(x4) cap 01[e0] =3D powerspec 3 supports D0 D3 current D0 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] =3D unknown 1 ecap 000b[160] =3D unknown 0 pcib1@pci0:0:1:0: class=3D0x060400 card=3D0x330b103c chip=3D0x34088086 r= ev=3D0x13 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub PCI Express Root Port 1' class =3D bridge subclass =3D PCI-PCI cap 0d[40] =3D PCI Bridge card=3D0x330b103c cap 05[60] =3D MSI supports 2 messages, vector masks cap 10[90] =3D PCI-Express 2 root port max data 256(256) link x4(x4) cap 01[e0] =3D powerspec 3 supports D0 D3 current D0 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] =3D unknown 1 ecap 000b[160] =3D unknown 0 pcib2@pci0:0:3:0: class=3D0x060400 card=3D0x330b103c chip=3D0x340a8086 r= ev=3D0x13 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub PCI Express Root Port 3' class =3D bridge subclass =3D PCI-PCI cap 0d[40] =3D PCI Bridge card=3D0x330b103c cap 05[60] =3D MSI supports 2 messages, vector masks cap 10[90] =3D PCI-Express 2 root port max data 256(256) link x0(x16) cap 01[e0] =3D powerspec 3 supports D0 D3 current D0 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] =3D unknown 1 ecap 000b[160] =3D unknown 0 pcib3@pci0:0:7:0: class=3D0x060400 card=3D0x330b103c chip=3D0x340e8086 r= ev=3D0x13 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub PCI Express Root Port 7' class =3D bridge subclass =3D PCI-PCI cap 0d[40] =3D PCI Bridge card=3D0x330b103c cap 05[60] =3D MSI supports 2 messages, vector masks cap 10[90] =3D PCI-Express 2 root port max data 256(256) link x0(x16) cap 01[e0] =3D powerspec 3 supports D0 D3 current D0 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] =3D unknown 1 ecap 000b[160] =3D unknown 0 pcib4@pci0:0:9:0: class=3D0x060400 card=3D0x330b103c chip=3D0x34108086 r= ev=3D0x13 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub PCI Express Root Port 9' class =3D bridge subclass =3D PCI-PCI cap 0d[40] =3D PCI Bridge card=3D0x330b103c cap 05[60] =3D MSI supports 2 messages, vector masks cap 10[90] =3D PCI-Express 2 root port max data 256(256) link x0(x4) cap 01[e0] =3D powerspec 3 supports D0 D3 current D0 ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected ecap 000d[150] =3D unknown 1 none0@pci0:0:20:0: class=3D0x080000 card=3D0x000b003c chip=3D0x342e8086 = rev=3D0x13 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub System Management Regist= ers' class =3D base peripheral subclass =3D interrupt controller cap 10[40] =3D PCI-Express 2 root endpoint max data 128(128) link x0(x0= ) none1@pci0:0:20:1: class=3D0x080000 card=3D0x000b003c chip=3D0x34228086 = rev=3D0x13 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub GPIO and Scratch Pad Reg= isters' class =3D base peripheral subclass =3D interrupt controller cap 10[40] =3D PCI-Express 2 root endpoint max data 128(128) link x0(x0= ) none2@pci0:0:20:2: class=3D0x080000 card=3D0x000b003c chip=3D0x34238086 = rev=3D0x13 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'QuickPath Architecture I/O Hub Control Status and RAS R= egisters' class =3D base peripheral subclass =3D interrupt controller cap 10[40] =3D PCI-Express 2 root endpoint max data 128(128) link x0(x0= ) uhci0@pci0:0:26:0: class=3D0x0c0300 card=3D0x330b103c chip=3D0x3a378086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB UHCI Controller *4' class =3D serial bus subclass =3D USB bar [20] =3D type I/O Port, range 32, base 0xc800, size 32, enabled cap 13[50] =3D PCI Advanced Features: FLR TP ehci0@pci0:0:26:7: class=3D0x0c0320 card=3D0x330b103c chip=3D0x3a3c8086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB EHCI Controller *2' class =3D serial bus subclass =3D USB bar [10] =3D type Memory, range 32, base 0xfaff8000, size 1024, enabl= ed cap 01[50] =3D powerspec 2 supports D0 D3 current D0 cap 0a[58] =3D EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] =3D PCI Advanced Features: FLR TP pcib5@pci0:0:28:0: class=3D0x060400 card=3D0x330b103c chip=3D0x3a408086 = rev=3D0x00 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'PCI Express Port 1' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(128) link x0(x4) cap 05[80] =3D MSI supports 1 message cap 0d[90] =3D PCI Bridge card=3D0x330b103c cap 01[a0] =3D powerspec 2 supports D0 D3 current D0 ecap 0002[100] =3D VC 1 max VC0 ecap 0005[180] =3D unknown 1 pcib6@pci0:0:28:4: class=3D0x060400 card=3D0x330b103c chip=3D0x3a488086 = rev=3D0x00 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'PCI Express Port 5' class =3D bridge subclass =3D PCI-PCI cap 10[40] =3D PCI-Express 1 root port max data 128(128) link x1(x2) cap 05[80] =3D MSI supports 1 message cap 0d[90] =3D PCI Bridge card=3D0x330b103c cap 01[a0] =3D powerspec 2 supports D0 D3 current D0 ecap 0002[100] =3D VC 1 max VC0 ecap 0005[180] =3D unknown 1 uhci1@pci0:0:29:0: class=3D0x0c0300 card=3D0x330b103c chip=3D0x3a348086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB UHCI Controller *1' class =3D serial bus subclass =3D USB bar [20] =3D type I/O Port, range 32, base 0xc880, size 32, enabled cap 13[50] =3D PCI Advanced Features: FLR TP uhci2@pci0:0:29:1: class=3D0x0c0300 card=3D0x330b103c chip=3D0x3a358086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB UHCI Controller *2' class =3D serial bus subclass =3D USB bar [20] =3D type I/O Port, range 32, base 0xcc00, size 32, enabled cap 13[50] =3D PCI Advanced Features: FLR TP uhci3@pci0:0:29:2: class=3D0x0c0300 card=3D0x330b103c chip=3D0x3a368086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB UHCI Controller *3' class =3D serial bus subclass =3D USB bar [20] =3D type I/O Port, range 32, base 0xd000, size 32, enabled cap 13[50] =3D PCI Advanced Features: FLR TP ehci1@pci0:0:29:7: class=3D0x0c0320 card=3D0x330b103c chip=3D0x3a3a8086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'USB EHCI Controller *1' class =3D serial bus subclass =3D USB bar [10] =3D type Memory, range 32, base 0xfaffa000, size 1024, enabl= ed cap 01[50] =3D powerspec 2 supports D0 D3 current D0 cap 0a[58] =3D EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] =3D PCI Advanced Features: FLR TP pcib7@pci0:0:30:0: class=3D0x060401 card=3D0x330b103c chip=3D0x244e8086 = rev=3D0x90 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface= to PCI Bridge' class =3D bridge subclass =3D PCI-PCI cap 0d[50] =3D PCI Bridge card=3D0x330b103c isab0@pci0:0:31:0: class=3D0x060100 card=3D0x330b103c chip=3D0x3a168086 = rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'LPC Interface Controller' class =3D bridge subclass =3D PCI-ISA cap 09[e0] =3D vendor (length 12) Intel cap 1 version 0 features: SATA RAID-5, 4 PCI-e x1 slots atapci0@pci0:0:31:2: class=3D0x010601 card=3D0x330b103c chip=3D0x3a22808= 6 rev=3D0x00 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '6 port SATA AHCI Controller' class =3D mass storage subclass =3D SATA bar [10] =3D type I/O Port, range 32, base 0xd880, size 8, enabled bar [14] =3D type I/O Port, range 32, base 0xd800, size 4, enabled bar [18] =3D type I/O Port, range 32, base 0xd480, size 8, enabled bar [1c] =3D type I/O Port, range 32, base 0xd400, size 4, enabled bar [20] =3D type I/O Port, range 32, base 0xd080, size 32, enabled bar [24] =3D type Memory, range 32, base 0xfaffc000, size 2048, enabl= ed cap 05[80] =3D MSI supports 16 messages cap 01[70] =3D powerspec 3 supports D0 D3 current D0 cap 12[a8] =3D SATA Index-Data Pair cap 13[b0] =3D PCI Advanced Features: FLR TP igb0@pci0:7:0:0: class=3D0x020000 card=3D0x323f103c chip=3D0x10c98086 re= v=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 32, base 0xfbe60000, size 131072, ena= bled bar [14] =3D type Memory, range 32, base 0xfbe40000, size 131072, ena= bled bar [18] =3D type I/O Port, range 32, base 0xe880, size 32, enabled cap 01[40] =3D powerspec 3 supports D0 D3 current D0 cap 05[50] =3D MSI supports 1 message, 64 bit, vector masks enabled wit= h 1 message cap 11[70] =3D MSI-X supports 10 messages in map 0x1c cap 10[a0] =3D PCI-Express 2 endpoint max data 256(512) link x4(x4) ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] =3D Serial 1 d8d385ffffe3e4f6 ecap 000e[150] =3D unknown 1 ecap 0010[160] =3D unknown 1 igb1@pci0:7:0:1: class=3D0x020000 card=3D0x323f103c chip=3D0x10c98086 re= v=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D network subclass =3D ethernet bar [10] =3D type Memory, range 32, base 0xfbee0000, size 131072, ena= bled bar [14] =3D type Memory, range 32, base 0xfbec0000, size 131072, ena= bled bar [18] =3D type I/O Port, range 32, base 0xec00, size 32, enabled cap 01[40] =3D powerspec 3 supports D0 D3 current D0 cap 05[50] =3D MSI supports 1 message, 64 bit, vector masks enabled wit= h 1 message cap 11[70] =3D MSI-X supports 10 messages in map 0x1c cap 10[a0] =3D PCI-Express 2 endpoint max data 256(512) link x4(x4) ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] =3D Serial 1 d8d385ffffe3e4f6 ecap 000e[150] =3D unknown 1 ecap 0010[160] =3D unknown 1 vgapci0@pci0:2:0:0: class=3D0x030000 card=3D0x010019a2 chip=3D0x0522102b= rev=3D0x02 hdr=3D0x00 vendor =3D 'Matrox Electronic Systems Ltd.' device =3D 'Matrox G200e (ServerEngines) - English (G200e)' class =3D display subclass =3D VGA bar [10] =3D type Prefetchable Memory, range 32, base 0xf8000000, siz= e 16777216, enabled bar [14] =3D type Memory, range 32, base 0xfbdfc000, size 16384, enab= led bar [18] =3D type Memory, range 32, base 0xfb000000, size 8388608, en= abled cap 01[dc] =3D powerspec 2 supports D0 D3 current D0 cap 10[e4] =3D PCI-Express 1 legacy endpoint max data 128(128) link x1(= x1) cap 05[54] =3D MSI supports 1 message -- Bartosz Stec From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 18:27:15 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E49E91065676; Fri, 10 Jun 2011 18:27:14 +0000 (UTC) (envelope-from jack.vogel@intel.com) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx1.freebsd.org (Postfix) with ESMTP id BF5A08FC1C; Fri, 10 Jun 2011 18:27:14 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP; 10 Jun 2011 11:15:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,348,1304319600"; d="scan'208";a="16891275" Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by fmsmga001.fm.intel.com with ESMTP; 10 Jun 2011 11:15:17 -0700 Received: from orsmsx605.amr.corp.intel.com (10.22.226.10) by orsmsx602.amr.corp.intel.com (10.22.226.211) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 10 Jun 2011 11:15:16 -0700 Received: from orsmsx508.amr.corp.intel.com ([10.22.226.46]) by orsmsx605.amr.corp.intel.com ([10.22.226.10]) with mapi; Fri, 10 Jun 2011 11:15:16 -0700 From: "Vogel, Jack" To: Jeremy Chadwick , Bartosz Stec Date: Fri, 10 Jun 2011 11:15:15 -0700 Thread-Topic: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE Thread-Index: AcwnUgRyDHsFle/sSm6yqTbf60dO8wAR9VbA Message-ID: <1DB50624F8348F48840F2E2CF6040A9D018ACA75B2@orsmsx508.amr.corp.intel.com> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> <20110610093728.GA39453@icarus.home.lan> In-Reply-To: <20110610093728.GA39453@icarus.home.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: FreeBSD Stable , Andriy Gapon Subject: RE: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 18:27:15 -0000 I looked at the dmesg and I didn't see a panic that was igb related? What I could see it looked like igb loaded normally, sounds like it's just = a victim of another problem perhaps? You certainly don't want to use it wit= hout MSIX. So far I've seen no data that would help understand this. Jack =20 -----Original Message----- From: Jeremy Chadwick [mailto:freebsd@jdc.parodius.com]=20 Sent: Friday, June 10, 2011 2:37 AM To: Bartosz Stec Cc: Andriy Gapon; FreeBSD Stable; Vogel, Jack Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest = STABLE On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: > W dniu 2011-05-13 13:30, Andriy Gapon pisze: > >on 12/05/2011 22:43 Bartosz Stec said the following: > >>Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr= .cgi?pr=3D156974 > >> > >I suspect that your best course here is to add some diagnostic printfs i= n > >igb_refresh_mbufs and in m_getzone to see what value is actually passed = to > >m_getjcl and why. > > > You're probably right, although I would need some guidance how to do > it. Sorry :( >=20 > Yesterday I rebuilt this machine with fresh sources to upgrade > filesystem to ZFSv28 which was MFC'ed lately. After that server > started to panic regardless of igb loaded as module or integrated > into kernel. >=20 > Finally I found that problem was caused by MSIX somehow. > No more panic after >=20 > hw.pci.enable_msix=3D0 >=20 > was included in loader.conf. >=20 > There's also no panic with GENERIC kernel. >=20 > Should I really care abou MSIX? Yes, you absolutely should. The performance hit, depending on your interrupt load, can be quite dramatic with this turned off. Remember: what you just turned off was MSI-X for the *entire system*, not just for NICs. Please read about it here: http://en.wikipedia.org/wiki/Message_Signaled_Interrupts CC'ing Jack Vogel here, because your issue pertains to igb(4). Please provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as well as relevant dmesg info that pertains to them (driver, etc.). You can XXX out MAC addresses if you're worried. Jack, original thread starts here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#6259= 6 --=20 | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 18:28:38 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49F1A106564A; Fri, 10 Jun 2011 18:28:38 +0000 (UTC) (envelope-from jack.vogel@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id 244688FC17; Fri, 10 Jun 2011 18:28:38 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 10 Jun 2011 11:19:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,348,1304319600"; d="scan'208";a="16892529" Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by fmsmga001.fm.intel.com with ESMTP; 10 Jun 2011 11:19:14 -0700 Received: from orsmsx605.amr.corp.intel.com (10.22.226.10) by orsmsx602.amr.corp.intel.com (10.22.226.211) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 10 Jun 2011 11:19:12 -0700 Received: from orsmsx508.amr.corp.intel.com ([10.22.226.46]) by orsmsx605.amr.corp.intel.com ([10.22.226.10]) with mapi; Fri, 10 Jun 2011 11:19:11 -0700 From: "Vogel, Jack" To: Jeremy Chadwick , Bartosz Stec Date: Fri, 10 Jun 2011 11:19:11 -0700 Thread-Topic: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE Thread-Index: AcwnUgRyDHsFle/sSm6yqTbf60dO8wASHHEw Message-ID: <1DB50624F8348F48840F2E2CF6040A9D018ACA75BA@orsmsx508.amr.corp.intel.com> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> <20110610093728.GA39453@icarus.home.lan> In-Reply-To: <20110610093728.GA39453@icarus.home.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: FreeBSD Stable , Andriy Gapon Subject: RE: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 18:28:38 -0000 Whoops, ignore the last message, I saw your screen picture. I have NEVER seen this particular message, I'm wondering if you're getting = some corrupt bits or something. Make sure you have a clean build of the ke= rnel and driver.=20 Jack -----Original Message----- From: Jeremy Chadwick [mailto:freebsd@jdc.parodius.com]=20 Sent: Friday, June 10, 2011 2:37 AM To: Bartosz Stec Cc: Andriy Gapon; FreeBSD Stable; Vogel, Jack Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest = STABLE On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: > W dniu 2011-05-13 13:30, Andriy Gapon pisze: > >on 12/05/2011 22:43 Bartosz Stec said the following: > >>Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr= .cgi?pr=3D156974 > >> > >I suspect that your best course here is to add some diagnostic printfs i= n > >igb_refresh_mbufs and in m_getzone to see what value is actually passed = to > >m_getjcl and why. > > > You're probably right, although I would need some guidance how to do > it. Sorry :( >=20 > Yesterday I rebuilt this machine with fresh sources to upgrade > filesystem to ZFSv28 which was MFC'ed lately. After that server > started to panic regardless of igb loaded as module or integrated > into kernel. >=20 > Finally I found that problem was caused by MSIX somehow. > No more panic after >=20 > hw.pci.enable_msix=3D0 >=20 > was included in loader.conf. >=20 > There's also no panic with GENERIC kernel. >=20 > Should I really care abou MSIX? Yes, you absolutely should. The performance hit, depending on your interrupt load, can be quite dramatic with this turned off. Remember: what you just turned off was MSI-X for the *entire system*, not just for NICs. Please read about it here: http://en.wikipedia.org/wiki/Message_Signaled_Interrupts CC'ing Jack Vogel here, because your issue pertains to igb(4). Please provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as well as relevant dmesg info that pertains to them (driver, etc.). You can XXX out MAC addresses if you're worried. Jack, original thread starts here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#6259= 6 --=20 | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 19:48:54 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0852106566C; Fri, 10 Jun 2011 19:48:54 +0000 (UTC) (envelope-from kc5vdj.freebsd@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3CED88FC12; Fri, 10 Jun 2011 19:48:53 +0000 (UTC) Received: by iyj12 with SMTP id 12so3550314iyj.13 for ; Fri, 10 Jun 2011 12:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WtRfyROM73H5pm2YnI4v2JM9naiIA6N3qtrijouY2yo=; b=aBtdEjn4fxxC38T9oVmBr4fVi4CrN45y7WGNHDHiujc3DRDIB7zaXoEAUoueob/NWz G0lGLVE2rRrQuexunhkOmVz9UJB4A3Vd9mGQPw27a7pknrbg26WevI27TSmdr7sAKE2x tgnYF1dvtWfhYuW+tB78WSwHN8PqsjEuYNiEg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=NjgvfQ4P9zJpYC+2pz8zSKFaYK12tjtTcDLcDOxA8vAP0dTOdkQxxTwpaurWIjVxdN 1EkIS7oHKvgJfjYU5UesyhpfMsTVc0Dn+rDuuwsIV/4f4XfmnBBN8kWmapllUH+bPs8d gauDOjMKhKTAMXPMaJKRJVBLDD7hfXns0yvZk= Received: by 10.231.112.88 with SMTP id v24mr2713981ibp.80.1307735333427; Fri, 10 Jun 2011 12:48:53 -0700 (PDT) Received: from argus.electron-tube.net (desm-45-047.dsl.netins.net [167.142.45.47]) by mx.google.com with ESMTPS id 4sm1457653ibc.42.2011.06.10.12.48.25 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Jun 2011 12:48:52 -0700 (PDT) Message-ID: <4DF274F6.6050905@gmail.com> Date: Fri, 10 Jun 2011 14:48:06 -0500 From: Jim Bryant User-Agent: Thunderbird 2.0.0.24 (X11/20100911) MIME-Version: 1.0 To: bschmidt@freebsd.org References: <4DF12E4A.5020906@gmail.com> <201106100913.42480.bschmidt@freebsd.org> In-Reply-To: <201106100913.42480.bschmidt@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: weongyo@freebsd.org, freebsd-wireless@freebsd.org, freebsd-stable@freebsd.org, freebsd-usb@freebsd.org Subject: Re: problem with urtw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 19:48:54 -0000 the patch didn't get it. ugen3.2: at usbus3 urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 urtw0: on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 ugen3.2: at usbus3 (disconnected) [the last line was me unplugging it] this is with if_urtw.c patched to change L to B as you supplied. I'm here for testing.. any more ideas? If anyone wants to play themselves, look on ebay for WiFiSky 1500mW B/G with 6dBi antenna. It seems that half of Hong Kong is selling these for under $20 USD. Bernhard Schmidt wrote: > On Thursday, June 09, 2011 22:34:18 Jim Bryant wrote: > >> I just bought one of those chinese (apparently the same unit relabeled >> and being sold by multiple companies) realtek RTL8187B wifi units. The >> price is right. >> >> The label name on this one is WiFySky 1500mW. >> >> other than the fact that the case it is enclosed in is really cheesy, >> there is a more immediate problem with this. >> >> the current urtw driver returns a 6. >> >> here we go: >> >> on insert: >> >> ugen3.2: at usbus3 >> >> after kldload if_urtw.ko: >> >> urtw0: >> on usbus3 >> urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE >> device_attach: urtw0 attach returned 6 >> urtw0: >> on usbus3 >> urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE >> device_attach: urtw0 attach returned 6 >> urtw0: >> on usbus3 >> urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE >> device_attach: urtw0 attach returned 6 >> urtw0: >> on usbus3 >> urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE >> device_attach: urtw0 attach returned 6 >> >> 3:28:35pm argus(48): usbconfig -u 3 -a 2 dump_device_desc >> ugen3.2: at usbus3, cfg=0 md=HOST >> spd=HIGH (480Mbps) pwr=ON >> >> bLength = 0x0012 >> bDescriptorType = 0x0001 >> bcdUSB = 0x0200 >> bDeviceClass = 0x0000 >> bDeviceSubClass = 0x0000 >> bDeviceProtocol = 0x0000 >> bMaxPacketSize0 = 0x0040 >> idVendor = 0x0bda >> idProduct = 0x8187 >> bcdDevice = 0x0200 >> iManufacturer = 0x0001 >> iProduct = 0x0002 >> iSerialNumber = 0x0000 >> bNumConfigurations = 0x0001 >> >> 3:28:48pm argus(49): usbconfig -u 3 -a 2 dump_curr_config_desc >> ugen3.2: at usbus3, cfg=0 md=HOST >> spd=HIGH (480Mbps) pwr=ON >> >> >> Configuration index 0 >> >> bLength = 0x0009 >> bDescriptorType = 0x0002 >> wTotalLength = 0x0051 >> bNumInterfaces = 0x0001 >> bConfigurationValue = 0x0001 >> iConfiguration = 0x0004 >> bmAttributes = 0x0080 >> bMaxPower = 0x00fa >> >> Interface 0 >> bLength = 0x0009 >> bDescriptorType = 0x0004 >> bInterfaceNumber = 0x0000 >> bAlternateSetting = 0x0000 >> bNumEndpoints = 0x0009 >> bInterfaceClass = 0x00ff >> bInterfaceSubClass = 0x00ff >> bInterfaceProtocol = 0x00ff >> iInterface = 0x0002 >> >> Endpoint 0 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0083 >> > > I have no clue what I'm talking about, so, this might be wrong.. > > Anyways.. the urtw(4) driver supports two different chips the > 8187B and 8187L. One difference between those is the number of > endpoints and its addresses. The 8187L uses 3 endpoints with > 0x81 as the RX endpoint, the 8187B uses 7 endpoints with 0x83 as > RX. > > % vendor REALTEK 0x0bda Realtek > % product REALTEK RTL8187 0x8187 RTL8187 Wireless Adapter > > Quoting from the driver: > > % #define URTW_DEV_B(v,p) \ > % { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, URTW_REV_RTL8187B) } > % #define URTW_DEV_L(v,p) \ > % { USB_VPI(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, URTW_REV_RTL8187L) } > % .. > % static const struct usb_device_id urtw_devs[] = { > % URTW_DEV_L(REALTEK, RTL8187), > % .. > % static const struct usb_config urtw_8187b_usbconfig[URTW_8187B_N_XFERS] = { > % [URTW_8187B_BULK_RX] = { > % .type = UE_BULK, > % .endpoint = 0x83, > % .. > % static const struct usb_config urtw_8187l_usbconfig[URTW_8187L_N_XFERS] = { > % [URTW_8187L_BULK_RX] = { > % .type = UE_BULK, > % .endpoint = 0x81, > > It occurs to me that yours might actually be a B chip not a L, > because there is a 0x83 endpoint but none for 0x81. > > Wanna give that a shot? > > Index: if_urtw.c > =================================================================== > --- if_urtw.c (revision 222807) > +++ if_urtw.c (working copy) > @@ -112,7 +112,7 @@ static const struct usb_device_id urtw_devs[] = { > URTW_DEV_L(BELKIN, F5D7050E), > URTW_DEV_L(LINKSYS4, WUSB54GCV2), > URTW_DEV_L(NETGEAR, WG111V2), > - URTW_DEV_L(REALTEK, RTL8187), > + URTW_DEV_B(REALTEK, RTL8187), > URTW_DEV_L(SITECOMEU, WL168V1), > URTW_DEV_L(SURECOM, EP9001G2A), > { USB_VPI(0x1b75, 0x8187, URTW_REV_RTL8187L) }, > > > > >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 1 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0004 >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 2 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0005 >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 3 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0006 >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 4 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0007 >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 5 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x0089 >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 6 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x000a >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 7 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x000b >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> Endpoint 8 >> bLength = 0x0007 >> bDescriptorType = 0x0005 >> bEndpointAddress = 0x000c >> bmAttributes = 0x0002 >> wMaxPacketSize = 0x0200 >> bInterval = 0x0000 >> bRefresh = 0x0000 >> bSynchAddress = 0x0000 >> >> If a verbose boot or any other info is needed to get this working, >> please tell me, and I'll get you the info. >> >> I do have to admit, at the price these are going for, they are rather >> nice, and do reach out and touch a router. Review complaints: heat >> dissipation. If you buy one, don't operate it in a hot environment. >> I'd like to see it working in FreeBSD, but I don't have a handle on the >> wifi driver structure. Linux source code was included on the driver >> disk. I can email that directly to whomever needs it for comparison. >> >> >> Thanks, >> >> Jim, KC5VDJ >> >> _______________________________________________ >> 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" >> > > -- > Bernhard > > From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 21:12:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA9E106564A for ; Fri, 10 Jun 2011 21:12:05 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id 1C3A68FC15 for ; Fri, 10 Jun 2011 21:12:04 +0000 (UTC) Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta04.westchester.pa.mail.comcast.net with comcast id uM4u1g0030EZKEL54MC5cD; Fri, 10 Jun 2011 21:12:05 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta01.westchester.pa.mail.comcast.net with comcast id uMC31g0291t3BNj3MMC4gn; Fri, 10 Jun 2011 21:12:05 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8E119102C19; Fri, 10 Jun 2011 14:12:02 -0700 (PDT) Date: Fri, 10 Jun 2011 14:12:02 -0700 From: Jeremy Chadwick To: Martin Matuska Message-ID: <20110610211202.GA52253@icarus.home.lan> References: <4DECB197.8020102@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DECB197.8020102@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 21:12:05 -0000 On Mon, Jun 06, 2011 at 12:53:11PM +0200, Martin Matuska wrote: > I have merged ZFS version 28 to 8-STABLE (revision 222741) Follow-up, since we're gradually upgrading our ZFS-based RELENG_8 servers to ZFSv28. Committers/those involved should see my very last paragraph. First, server upgrades: We've upgraded 2 of the 4 (including updating zfs and zpools), and so far things are working wonderfully. One of those 2 boxes is our NFS filer (which also does backups via rsync/rsnapshot), so that one's been a big worry-point of mine. The next rsync/rsnapshot runs tonight, so I'll be awake watching intently. All these systems are graphed via bsnmpd (memory, CPU, disk I/O, etc.). Second, performance tweaks: We're testing changing to our tweaks; the following directives have been commented out in our /boot/loader.conf files (e.g. we're now using prefetching): # vfs.zfs.prefetch_disable="1" And the following tunable has been removed completely, because it's now the default in ZFSv28 (see cvsweb, look at line 40 of the relevant commit for src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/txg.c): vfs.zfs.txg.timeout="5" Finally, talking a bit about dedup: In the ZFSv28 commit, did the zfs.8 man page get updated? I find no mention of the dedup property in the zfs(8) man page, and yes I did remove the old /usr/share/man/cat8/zfs.8.gz file. We tried using dedup on one of our systems, but within 10-15 minutes turned it off. I believe the added CPU overhead of dedup was causing the system to act "bursty" in other non-ZFS-related tasks; e.g. turn on dedup, then in a SSH window hold down the letter "q" indefinitely, then in another window do some ZFS I/O. The "q" would stall for 1-2 seconds at times (SSH connectivity was via direct private LAN, so network latency was not what we seen). Without dedup this behaviour wasn't seen at all. I'm happy to try any advice/patches on a locally-accessible box (e.g. private LAN, VGA console is right behind me, etc.). I have not tried tinkering with the following settings to find out what may relieve this issue. I'm referring to the sections titled "Trust or verify" and "Selecting a checksum" on Jeff's blog here: http://blogs.oracle.com/bonwick/entry/zfs_dedup All in all, thank you everyone for the work that's gone in to MFC'ing this to RELENG_8. I really do mean that. I'm a harsh bastard on the mailing lists, no question about it. But I always appreciate people doing the grunt work that I myself cannot do (over my head). I state this seriously: if any of you folks who participated in this MFC have donation links (PayPal, etc.), please give them to me. You absolutely will see some worthwhile kick-backs for your efforts, with no strings attached. Just my way of saying "thank you". -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 21:40:22 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5B511065673 for ; Fri, 10 Jun 2011 21:40:22 +0000 (UTC) (envelope-from bfriesen@simple.dallas.tx.us) Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9FD8FC0C for ; Fri, 10 Jun 2011 21:40:22 +0000 (UTC) Received: from freddy.simplesystems.org (freddy.simplesystems.org [65.66.246.65]) by blade.simplesystems.org (8.14.4+Sun/8.14.4) with ESMTP id p5ALO5af017885; Fri, 10 Jun 2011 16:24:05 -0500 (CDT) Date: Fri, 10 Jun 2011 16:24:05 -0500 (CDT) From: Bob Friesenhahn X-X-Sender: bfriesen@freddy.simplesystems.org To: Jeremy Chadwick In-Reply-To: <20110610211202.GA52253@icarus.home.lan> Message-ID: References: <4DECB197.8020102@FreeBSD.org> <20110610211202.GA52253@icarus.home.lan> User-Agent: Alpine 2.01 (GSO 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (blade.simplesystems.org [65.66.246.90]); Fri, 10 Jun 2011 16:24:05 -0500 (CDT) Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 21:40:22 -0000 On Fri, 10 Jun 2011, Jeremy Chadwick wrote: > > We tried using dedup on one of our systems, but within 10-15 minutes > turned it off. I believe the added CPU overhead of dedup was causing > the system to act "bursty" in other non-ZFS-related tasks; e.g. turn on > dedup, then in a SSH window hold down the letter "q" indefinitely, then > in another window do some ZFS I/O. The "q" would stall for 1-2 seconds > at times (SSH connectivity was via direct private LAN, so network > latency was not what we seen). Without dedup this behaviour wasn't seen > at all. I'm happy to try any advice/patches on a locally-accessible > box (e.g. private LAN, VGA console is right behind me, etc.). Dedup can require a huge amount of RAM, or a dedicated L2ARC SSD, depending on the size of your storage. You should not enable it unless you are prepared for the consequences. Solaris 11 Express does not admit to supporting dedup even though it can be enabled in previous OpenSolaris and is supported in Oracle's NAS products (which run a variant of Solaris 11). Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 21:49:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D65DE106564A; Fri, 10 Jun 2011 21:49:12 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id F20568FC14; Fri, 10 Jun 2011 21:49:11 +0000 (UTC) Received: by bwz12 with SMTP id 12so3622477bwz.13 for ; Fri, 10 Jun 2011 14:49:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3aAe6MM1dl4CXTn2MIAEerYJVKmlI2BNVOono2h/Amw=; b=miV1926b6wDpqXh1toN9GxTS0XIPCzIF1J4dnMMZ6cZdb067MFuvEEtPOdu4Z6uVst yDxfeP+/6PxGJpY738Ugm8ncNzeSYcYCAF9SucWKM0bfzm/svQ6dx7bkcaMWigH7heC4 7m2tbFGo3xy0JmVBHN0J2YuRkf/5wox5f6IsQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=FB1HQLUVOJGaItJYPYhzcOa76O+hP76qoGONcFvYeulscsDNosSIYEVu9DkF9s1KZ7 KooBshtiileUmptmNk1lB3yL3zNHF2YlU9Vj6BLjNJN+pRkrFrX1gjeZF+XNz4vSQ9VH LcASyftvnTcBYe3tAwOGvUDHkyj80q60cSgk4= Received: by 10.204.232.73 with SMTP id jt9mr2211337bkb.214.1307741139831; Fri, 10 Jun 2011 14:25:39 -0700 (PDT) Received: from limbo.lan ([195.225.157.86]) by mx.google.com with ESMTPS id j7sm2931635bka.8.2011.06.10.14.25.37 (version=SSLv3 cipher=OTHER); Fri, 10 Jun 2011 14:25:38 -0700 (PDT) Message-ID: <4DF28BCF.3060008@gmail.com> Date: Sat, 11 Jun 2011 00:25:35 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.2.17) Gecko/20110509 Thunderbird/3.1.10 MIME-Version: 1.0 To: Martin Matuska References: <4DECB197.8020102@FreeBSD.org> In-Reply-To: <4DECB197.8020102@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: HEADS UP: ZFS v28 merged to 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 21:49:12 -0000 06.06.2011 13:53, Martin Matuska написав(ла): > Hi, > > I have merged ZFS version 28 to 8-STABLE (revision 222741) > > New major features: > > - data deduplication Am I missing something? How about using fletcher[24] for dedup? -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 22:15:26 2011 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F29A1065670; Fri, 10 Jun 2011 22:15:26 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0D5088FC12; Fri, 10 Jun 2011 22:15:26 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.5/8.14.5) with ESMTP id p5AMFPBR032368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 10 Jun 2011 15:15:25 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id A1C791CC0B; Fri, 10 Jun 2011 15:15:25 -0700 (PDT) To: delphij@freebsd.org Date: Fri, 10 Jun 2011 15:15:25 -0700 From: "Kevin Oberman" Message-Id: <20110610221525.A1C791CC0B@ptavv.es.net> Cc: stable@freebsd.org Subject: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 22:15:26 -0000 I am hitting the problem reported some time ago with atkbd and svn 197392. It's not clear that this has ben finally resolved, but I am still hitting it with -stable on my new T520. I really want to get FreeBSD up on it, but I am dead in the water at this time. I guess I'll have to build a new kernel with any fix and replace the kernel in the ISO. Also, I am hoping to use it on an amd64 kernel and I am even less sure that any patch will work on that arch. The original thread was http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-td3926276.html Thanks in advance for any help. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Last work day before retirement is Jun 17, 2011 From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 23:15:57 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 870D11065670 for ; Fri, 10 Jun 2011 23:15:57 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) by mx1.freebsd.org (Postfix) with ESMTP id 6F6BD8FC0C for ; Fri, 10 Jun 2011 23:15:57 +0000 (UTC) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 3FBB09808; Fri, 10 Jun 2011 16:15:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=anubis; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:mime-version:to: subject:references:in-reply-to:openpgp:content-type:content-transfer-encoding; b=x7OR6B5tWvAQTvlQCYA83O1Qn27zR810Sq8X/JxhBOxrJlxMLNYEjXQQjDajymasg Y+Sw156HeTKZnEpRgJHUqKJZy6tC/Py5s+RKk18C7+aiErrsU51npuU4e0/i7oheUcL m4qfjmepWwEaULdUuF+3CGtkSPb9+c1SsqYhSfc= Message-ID: <4DF2A5AC.6070804@delphij.net> Date: Fri, 10 Jun 2011 16:15:56 -0700 From: Xin LI Organization: The FreeBSD Project MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20110610221525.A1C791CC0B@ptavv.es.net> In-Reply-To: <20110610221525.A1C791CC0B@ptavv.es.net> OpenPGP: id=3FCA37C1; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 23:15:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/10/11 15:15, Kevin Oberman wrote: > I am hitting the problem reported some time ago with atkbd and svn > 197392. > > It's not clear that this has ben finally resolved, but I am still > hitting it with -stable on my new T520. I really want to get FreeBSD up > on it, but I am dead in the water at this time. I guess I'll have to > build a new kernel with any fix and replace the kernel in the ISO. > > Also, I am hoping to use it on an amd64 kernel and I am even less sure > that any patch will work on that arch. > > The original thread was > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-td3926276.html The fix was not (yet) merged back to 8-STABLE. You may use a 8.0-RELEASE kernel to boot the system temporarily and apply this patch: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff?r1=1.63;r2=1.64 (If hunk #1 fails to apply, it's Ok to just ignore it). Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBCAAGBQJN8qWrAAoJEATO+BI/yjfBfNgH/1FBHJzQuRIkG1gIKrhAi2ES tyvxsaBc/6e/htXSsRSLoXXZ+Ds427Yes6MVVjyMlVPne7QzF9HxRQVTzNv9sTmc /Jx3pIbnIaugg/tVR+K49s+IU3UxtkSl4f7aKXG2eacWz52S/A8DzXFbe5WX41lE xn47myobsiGEBv6wnss7Q9gW42CoVfAp753lrBlKUMqGpZR04cPIGMsxjgPGoBpg QUTxoYbXj53ZdEMI3gYCF69m/Nf3lNY33nb7TI//I7qYBTspXdoCJ221MFJWYn04 hhxOdvo3xJ2shZOSJ4IH3waSk0G2hlOjPhud2m+t1KMtDt2e09A3ZD1xhmCxs0s= =fDcF -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 23:42:29 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CF841065670 for ; Fri, 10 Jun 2011 23:42:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id 75E8F8FC0C for ; Fri, 10 Jun 2011 23:42:29 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta14.emeryville.ca.mail.comcast.net with comcast id uPai1g0041Y3wxoAEPiTLP; Fri, 10 Jun 2011 23:42:27 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta15.emeryville.ca.mail.comcast.net with comcast id uPi71g00D1t3BNj8bPi7Wy; Fri, 10 Jun 2011 23:42:08 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id C708B102C19; Fri, 10 Jun 2011 16:42:27 -0700 (PDT) Date: Fri, 10 Jun 2011 16:42:27 -0700 From: Jeremy Chadwick To: d@delphij.net Message-ID: <20110610234227.GA54846@icarus.home.lan> References: <20110610221525.A1C791CC0B@ptavv.es.net> <4DF2A5AC.6070804@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DF2A5AC.6070804@delphij.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 23:42:29 -0000 On Fri, Jun 10, 2011 at 04:15:56PM -0700, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 06/10/11 15:15, Kevin Oberman wrote: > > I am hitting the problem reported some time ago with atkbd and svn > > 197392. > > > > It's not clear that this has ben finally resolved, but I am still > > hitting it with -stable on my new T520. I really want to get FreeBSD up > > on it, but I am dead in the water at this time. I guess I'll have to > > build a new kernel with any fix and replace the kernel in the ISO. > > > > Also, I am hoping to use it on an amd64 kernel and I am even less sure > > that any patch will work on that arch. > > > > The original thread was > > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-td3926276.html > > The fix was not (yet) merged back to 8-STABLE. You may use a > 8.0-RELEASE kernel to boot the system temporarily and apply this patch: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff?r1=1.63;r2=1.64 > > (If hunk #1 fails to apply, it's Ok to just ignore it). Specifically: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c#rev1.64 - if (x86bios_get_intr(0x15) == 0 || x86bios_get_intr(0x16) == 0) + if (x86bios_get_intr(0x15) != 0xf000f859 || + x86bios_get_intr(0x16) != 0xf000e82e) What are these magic numbers? Where did they come from? What do they represent? Why are they not documented in the source code/commit itself? No offence, but this is an open-source project; anyone looking at this code isn't going to know what those vectors represent. The commit message is also lacking (again: magic values not mentioned), and expecting a developer to dig through commits/annotations to determine what this piece of code is for is unreasonable. No I'm not in a bad mood (honest!), I just find this kind of thing infuriating the more I dig through kernel source code. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 00:15:14 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69450106566C for ; Sat, 11 Jun 2011 00:15:14 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1DFAA8FC08 for ; Sat, 11 Jun 2011 00:15:13 +0000 (UTC) Received: by vxc34 with SMTP id 34so3720729vxc.13 for ; Fri, 10 Jun 2011 17:15:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=GO9gVdwFOnYQwVHyLJBAhn7IRl3XAdDLCFgLdmRPBmU=; b=EN/ekYWYC3dSo4H2F/gxjwoM1Zx8m8zQJgudhSrUER67wxg3Pv39VS4GsUN35hThZO gxVVGBEikUzMy1+8kurDepz2cSqeUGJpK5NNfFI0xDq/eELsDvnqkYPferN7IozNs73n uowtPR8my39Q+YNiLlmYPfkp9gD3FW52tCzZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=WuEZwULr6YOhRiogoaJIuDJOjYYpLzuiakbaefJZr1ZVlspZB2M75lyDDO5Y8NQ3xT 8Qyb5ijWp/QxzaqLgDmR0qOXTA3BQuB7UEGlG+Q/W+UrMKo9GyQNObDdY5B5Z0HsA383 oIKSJNT6pDyRCcqsFgKOrM6pluTlxuYO0tE7E= MIME-Version: 1.0 Received: by 10.52.97.33 with SMTP id dx1mr766243vdb.34.1307749711981; Fri, 10 Jun 2011 16:48:31 -0700 (PDT) Received: by 10.52.108.132 with HTTP; Fri, 10 Jun 2011 16:48:31 -0700 (PDT) In-Reply-To: <20110610234227.GA54846@icarus.home.lan> References: <20110610221525.A1C791CC0B@ptavv.es.net> <4DF2A5AC.6070804@delphij.net> <20110610234227.GA54846@icarus.home.lan> Date: Fri, 10 Jun 2011 16:48:31 -0700 Message-ID: From: Xin LI To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 00:15:14 -0000 On Fri, Jun 10, 2011 at 4:42 PM, Jeremy Chadwick wrote: > On Fri, Jun 10, 2011 at 04:15:56PM -0700, Xin LI wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 06/10/11 15:15, Kevin Oberman wrote: >> > I am hitting the problem reported some time ago with atkbd and svn >> > 197392. >> > >> > It's not clear that this has ben finally resolved, but I am still >> > hitting it with -stable on my new T520. I really want to get FreeBSD u= p >> > on it, but I am dead in the water at this time. I guess I'll have to >> > build a new kernel with any fix and replace the kernel in the ISO. >> > >> > Also, I am hoping to use it on an amd64 kernel and I am even less sure >> > that any patch will work on that arch. >> > >> > The original thread was >> > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-= td3926276.html >> >> The fix was not (yet) merged back to 8-STABLE. =C2=A0You may use a >> 8.0-RELEASE kernel to boot the system temporarily and apply this patch: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff?r1= =3D1.63;r2=3D1.64 >> >> (If hunk #1 fails to apply, it's Ok to just ignore it). > > Specifically: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c#rev1.64 > > - =C2=A0 =C2=A0 =C2=A0 if (x86bios_get_intr(0x15) =3D=3D 0 || x86bios_get= _intr(0x16) =3D=3D 0) > + =C2=A0 =C2=A0 =C2=A0 if (x86bios_get_intr(0x15) !=3D 0xf000f859 || > + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 x86bios_get_intr(0x16) !=3D 0xf000e8= 2e) > > What are these magic numbers? =C2=A0Where did they come from? =C2=A0What = do they > represent? =C2=A0Why are they not documented in the source code/commit > itself? =C2=A0No offence, but this is an open-source project; anyone look= ing > at this code isn't going to know what those vectors represent. =C2=A0The > commit message is also lacking (again: magic values not mentioned), and > expecting a developer to dig through commits/annotations to determine > what this piece of code is for is unreasonable. > > No I'm not in a bad mood (honest!), I just find this kind of thing > infuriating the more I dig through kernel source code. The commit log explicitly say: Validate INT 15h and 16h vectors more strictly. Traditionally these entry points are fixed addresses and (U)EFI CSM specification also mandated that. Unfortunately, (U)EFI CSM specification does not specifically mention this is to call service routine via interrupt vector table or to jump directly to the entry point. As a result, some CSM seems to install two routines and acts differently, depending on how it was executed, unfortunately. When INT 15h is used, it calls a function pointer (which is probably a UEFI service function). When it jumps directly to the entry point, it executes a simple and traditional INT 15h service routine. Therefore, actually ther= e are two possible fixes, i. e., this fix or jumping directly to the fixed entry point. However, we chose this fix because a) keyboard typematic support via BIOS is becoming extremely rarer and b) we cannot support rando= m service routine installed by a firmware or a boot loader. This should fix Lenovo X220 laptop, specifically. Be reasonable, please. Cheers, --=20 Xin LI http://www.delphij.net From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 00:59:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9A1E1065672 for ; Sat, 11 Jun 2011 00:59:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by mx1.freebsd.org (Postfix) with ESMTP id 82F868FC17 for ; Sat, 11 Jun 2011 00:59:53 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta01.emeryville.ca.mail.comcast.net with comcast id uQeQ1g0061GXsucA1Qzr3G; Sat, 11 Jun 2011 00:59:51 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id uQzu1g0041t3BNj8UQzuC9; Sat, 11 Jun 2011 00:59:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8395C102C19; Fri, 10 Jun 2011 17:59:51 -0700 (PDT) Date: Fri, 10 Jun 2011 17:59:51 -0700 From: Jeremy Chadwick To: Xin LI Message-ID: <20110611005951.GA55990@icarus.home.lan> References: <20110610221525.A1C791CC0B@ptavv.es.net> <4DF2A5AC.6070804@delphij.net> <20110610234227.GA54846@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 00:59:53 -0000 On Fri, Jun 10, 2011 at 04:48:31PM -0700, Xin LI wrote: > On Fri, Jun 10, 2011 at 4:42 PM, Jeremy Chadwick > wrote: > > On Fri, Jun 10, 2011 at 04:15:56PM -0700, Xin LI wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> On 06/10/11 15:15, Kevin Oberman wrote: > >> > I am hitting the problem reported some time ago with atkbd and svn > >> > 197392. > >> > > >> > It's not clear that this has ben finally resolved, but I am still > >> > hitting it with -stable on my new T520. I really want to get FreeBSD up > >> > on it, but I am dead in the water at this time. I guess I'll have to > >> > build a new kernel with any fix and replace the kernel in the ISO. > >> > > >> > Also, I am hoping to use it on an amd64 kernel and I am even less sure > >> > that any patch will work on that arch. > >> > > >> > The original thread was > >> > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-td3926276.html > >> > >> The fix was not (yet) merged back to 8-STABLE. ??You may use a > >> 8.0-RELEASE kernel to boot the system temporarily and apply this patch: > >> > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff?r1=1.63;r2=1.64 > >> > >> (If hunk #1 fails to apply, it's Ok to just ignore it). > > > > Specifically: > > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c#rev1.64 > > > > - ?? ?? ?? if (x86bios_get_intr(0x15) == 0 || x86bios_get_intr(0x16) == 0) > > + ?? ?? ?? if (x86bios_get_intr(0x15) != 0xf000f859 || > > + ?? ?? ?? ?? ?? x86bios_get_intr(0x16) != 0xf000e82e) > > > > What are these magic numbers? ??Where did they come from? ??What do they > > represent? ??Why are they not documented in the source code/commit > > itself? ??No offence, but this is an open-source project; anyone looking > > at this code isn't going to know what those vectors represent. ??The > > commit message is also lacking (again: magic values not mentioned), and > > expecting a developer to dig through commits/annotations to determine > > what this piece of code is for is unreasonable. > > > > No I'm not in a bad mood (honest!), I just find this kind of thing > > infuriating the more I dig through kernel source code. > > The commit log explicitly say: > > Validate INT 15h and 16h vectors more strictly. Traditionally these entry > points are fixed addresses and (U)EFI CSM specification also mandated that. > Unfortunately, (U)EFI CSM specification does not specifically mention this > is to call service routine via interrupt vector table or to jump directly > to the entry point. As a result, some CSM seems to install two routines > and acts differently, depending on how it was executed, unfortunately. > When INT 15h is used, it calls a function pointer (which is probably a UEFI > service function). When it jumps directly to the entry point, it executes > a simple and traditional INT 15h service routine. Therefore, actually there > are two possible fixes, i. e., this fix or jumping directly to the fixed > entry point. However, we chose this fix because a) keyboard typematic > support via BIOS is becoming extremely rarer and b) we cannot support random > service routine installed by a firmware or a boot loader. This should fix > Lenovo X220 laptop, specifically. > > Be reasonable, please. I read the commit message -- sadly it also does not explain what the numbers mean. 0xf000f859 and 0xf000e82e appear to be 32-bit vector addresses (e.g. used for indirect JMP), except nobody explains where those values came from or what they actually point to. Therefore, they are "magic values" until they can be defined otherwise. Someone digging through the source code is not going to see the commit message. They're going to have to track it down by hand using cvsweb or SVN, just to look at annotations. Don't worry, I don't mean for this to sound like I'm picking on this single commit -- this kind of craziness is all over the FreeBSD source tree, and as I said, it's infuriating when trying to look at the code (it is an open-source project, right?) and figure out what's going on/why something is the way it is. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 01:24:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F8E2106564A for ; Sat, 11 Jun 2011 01:24:53 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id E30EE8FC13 for ; Sat, 11 Jun 2011 01:24:52 +0000 (UTC) Received: by vxc34 with SMTP id 34so3749945vxc.13 for ; Fri, 10 Jun 2011 18:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kxAbghUDJXcj65V9S5eqEif4+T6/lXA61+Gg2qgUBmk=; b=TOSsYfPiLylixhFAbkOvSxZTOU2VwTkgbcC68naZvVLPFQ0LQioqWl4vo4nveaCokt 27rUy6SS0cwNfuj4PVQlOWV4zJvaUf7k9j82qWa4VIycJ8HILr7BIbVlqmf4GpeIURci ZytD2Q3s4u72V3VoE3Gdg/pp/NfdpfXYrKwLc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=aHIU1Y9aZh5ddMq5wIdWljzc9+l7W/gnQyFvMGLdF9VFagw/RX9mPuIeY7GaUq2l9D 7CDXZPSGG+7s24Su72a/EYSJsJLgnqoEGCh8drYJ4OmUv+8Mk55mmeIcKDRjg2Z+3PE8 QZNidE09Rz5OCl55jaiDAq9BzIqqYglbzRgtk= MIME-Version: 1.0 Received: by 10.52.97.161 with SMTP id eb1mr723685vdb.74.1307755491966; Fri, 10 Jun 2011 18:24:51 -0700 (PDT) Received: by 10.52.108.132 with HTTP; Fri, 10 Jun 2011 18:24:51 -0700 (PDT) In-Reply-To: <20110611005951.GA55990@icarus.home.lan> References: <20110610221525.A1C791CC0B@ptavv.es.net> <4DF2A5AC.6070804@delphij.net> <20110610234227.GA54846@icarus.home.lan> <20110611005951.GA55990@icarus.home.lan> Date: Fri, 10 Jun 2011 18:24:51 -0700 Message-ID: From: Xin LI To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 01:24:53 -0000 On Fri, Jun 10, 2011 at 5:59 PM, Jeremy Chadwick wrote: > On Fri, Jun 10, 2011 at 04:48:31PM -0700, Xin LI wrote: >> On Fri, Jun 10, 2011 at 4:42 PM, Jeremy Chadwick >> wrote: >> > On Fri, Jun 10, 2011 at 04:15:56PM -0700, Xin LI wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA256 >> >> >> >> On 06/10/11 15:15, Kevin Oberman wrote: >> >> > I am hitting the problem reported some time ago with atkbd and svn >> >> > 197392. >> >> > >> >> > It's not clear that this has ben finally resolved, but I am still >> >> > hitting it with -stable on my new T520. I really want to get FreeBS= D up >> >> > on it, but I am dead in the water at this time. I guess I'll have t= o >> >> > build a new kernel with any fix and replace the kernel in the ISO. >> >> > >> >> > Also, I am hoping to use it on an amd64 kernel and I am even less s= ure >> >> > that any patch will work on that arch. >> >> > >> >> > The original thread was >> >> > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-bo= ot-td3926276.html >> >> >> >> The fix was not (yet) merged back to 8-STABLE. ??You may use a >> >> 8.0-RELEASE kernel to boot the system temporarily and apply this patc= h: >> >> >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff= ?r1=3D1.63;r2=3D1.64 >> >> >> >> (If hunk #1 fails to apply, it's Ok to just ignore it). >> > >> > Specifically: >> > >> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c#rev1.= 64 >> > >> > - ?? ?? ?? if (x86bios_get_intr(0x15) =3D=3D 0 || x86bios_get_intr(0x1= 6) =3D=3D 0) >> > + ?? ?? ?? if (x86bios_get_intr(0x15) !=3D 0xf000f859 || >> > + ?? ?? ?? ?? ?? x86bios_get_intr(0x16) !=3D 0xf000e82e) >> > >> > What are these magic numbers? ??Where did they come from? ??What do th= ey >> > represent? ??Why are they not documented in the source code/commit >> > itself? ??No offence, but this is an open-source project; anyone looki= ng >> > at this code isn't going to know what those vectors represent. ??The >> > commit message is also lacking (again: magic values not mentioned), an= d >> > expecting a developer to dig through commits/annotations to determine >> > what this piece of code is for is unreasonable. >> > >> > No I'm not in a bad mood (honest!), I just find this kind of thing >> > infuriating the more I dig through kernel source code. >> >> The commit log explicitly say: >> >> Validate INT 15h and 16h vectors more strictly. =C2=A0Traditionally thes= e entry >> points are fixed addresses and (U)EFI CSM specification also mandated th= at. >> Unfortunately, (U)EFI CSM specification does not specifically mention th= is >> is to call service routine via interrupt vector table or to jump directl= y >> to the entry point. =C2=A0As a result, some CSM seems to install two rou= tines >> and acts differently, depending on how it was executed, unfortunately. >> When INT 15h is used, it calls a function pointer (which is probably a U= EFI >> service function). =C2=A0When it jumps directly to the entry point, it e= xecutes >> a simple and traditional INT 15h service routine. =C2=A0Therefore, actua= lly there >> are two possible fixes, i. e., this fix or jumping directly to the fixed >> entry point. =C2=A0However, we chose this fix because a) keyboard typema= tic >> support via BIOS is becoming extremely rarer and b) we cannot support ra= ndom >> service routine installed by a firmware or a boot loader. =C2=A0This sho= uld fix >> Lenovo X220 laptop, specifically. >> >> Be reasonable, please. > > I read the commit message -- sadly it also does not explain what the > numbers mean. =C2=A00xf000f859 and 0xf000e82e appear to be 32-bit vector > addresses (e.g. used for indirect JMP), except nobody explains where > those values came from or what they actually point to. =C2=A0Therefore, t= hey > are "magic values" until they can be defined otherwise. > > Someone digging through the source code is not going to see the commit > message. =C2=A0They're going to have to track it down by hand using cvswe= b or > SVN, just to look at annotations. =C2=A0Don't worry, I don't mean for thi= s to > sound like I'm picking on this single commit -- this kind of craziness > is all over the FreeBSD source tree, and as I said, it's infuriating > when trying to look at the code (it is an open-source project, right?) > and figure out what's going on/why something is the way it is. I'm not in good mood and I find it a waste of my time, sorry for that. I have committed a fix (r222967). Just want to say that Jung-uk have spend a lot of his time investigating and fixing this issue, and I just don't see why people typing that much doesn't want to submit a patch. I think Open Source projects expect everyone there to contribute rather than asking someone else to do the work. Cheers, --=20 Xin LI http://www.delphij.net From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 01:29:27 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9470106566B for ; Sat, 11 Jun 2011 01:29:27 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 8E8A98FC08 for ; Sat, 11 Jun 2011 01:29:27 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta07.emeryville.ca.mail.comcast.net with comcast id uRUe1g0021HpZEsA7RVRsB; Sat, 11 Jun 2011 01:29:25 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta14.emeryville.ca.mail.comcast.net with comcast id uRVU1g00F1t3BNj8aRVU3F; Sat, 11 Jun 2011 01:29:28 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 101AE102C19; Fri, 10 Jun 2011 18:29:26 -0700 (PDT) Date: Fri, 10 Jun 2011 18:29:26 -0700 From: Jeremy Chadwick To: Xin LI Message-ID: <20110611012926.GA56546@icarus.home.lan> References: <20110610221525.A1C791CC0B@ptavv.es.net> <4DF2A5AC.6070804@delphij.net> <20110610234227.GA54846@icarus.home.lan> <20110611005951.GA55990@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot Lenovo T520 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 01:29:27 -0000 On Fri, Jun 10, 2011 at 06:24:51PM -0700, Xin LI wrote: > On Fri, Jun 10, 2011 at 5:59 PM, Jeremy Chadwick > wrote: > > On Fri, Jun 10, 2011 at 04:48:31PM -0700, Xin LI wrote: > >> On Fri, Jun 10, 2011 at 4:42 PM, Jeremy Chadwick > >> wrote: > >> > On Fri, Jun 10, 2011 at 04:15:56PM -0700, Xin LI wrote: > >> >> -----BEGIN PGP SIGNED MESSAGE----- > >> >> Hash: SHA256 > >> >> > >> >> On 06/10/11 15:15, Kevin Oberman wrote: > >> >> > I am hitting the problem reported some time ago with atkbd and svn > >> >> > 197392. > >> >> > > >> >> > It's not clear that this has ben finally resolved, but I am still > >> >> > hitting it with -stable on my new T520. I really want to get FreeBSD up > >> >> > on it, but I am dead in the water at this time. I guess I'll have to > >> >> > build a new kernel with any fix and replace the kernel in the ISO. > >> >> > > >> >> > Also, I am hoping to use it on an amd64 kernel and I am even less sure > >> >> > that any patch will work on that arch. > >> >> > > >> >> > The original thread was > >> >> > http://freebsd.1045724.n5.nabble.com/svn-rev-197392-hangs-during-boot-td3926276.html > >> >> > >> >> The fix was not (yet) merged back to 8-STABLE. ??You may use a > >> >> 8.0-RELEASE kernel to boot the system temporarily and apply this patch: > >> >> > >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c.diff?r1=1.63;r2=1.64 > >> >> > >> >> (If hunk #1 fails to apply, it's Ok to just ignore it). > >> > > >> > Specifically: > >> > > >> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/atkbdc/atkbd.c#rev1.64 > >> > > >> > - ?? ?? ?? if (x86bios_get_intr(0x15) == 0 || x86bios_get_intr(0x16) == 0) > >> > + ?? ?? ?? if (x86bios_get_intr(0x15) != 0xf000f859 || > >> > + ?? ?? ?? ?? ?? x86bios_get_intr(0x16) != 0xf000e82e) > >> > > >> > What are these magic numbers? ??Where did they come from? ??What do they > >> > represent? ??Why are they not documented in the source code/commit > >> > itself? ??No offence, but this is an open-source project; anyone looking > >> > at this code isn't going to know what those vectors represent. ??The > >> > commit message is also lacking (again: magic values not mentioned), and > >> > expecting a developer to dig through commits/annotations to determine > >> > what this piece of code is for is unreasonable. > >> > > >> > No I'm not in a bad mood (honest!), I just find this kind of thing > >> > infuriating the more I dig through kernel source code. > >> > >> The commit log explicitly say: > >> > >> Validate INT 15h and 16h vectors more strictly. ??Traditionally these entry > >> points are fixed addresses and (U)EFI CSM specification also mandated that. > >> Unfortunately, (U)EFI CSM specification does not specifically mention this > >> is to call service routine via interrupt vector table or to jump directly > >> to the entry point. ??As a result, some CSM seems to install two routines > >> and acts differently, depending on how it was executed, unfortunately. > >> When INT 15h is used, it calls a function pointer (which is probably a UEFI > >> service function). ??When it jumps directly to the entry point, it executes > >> a simple and traditional INT 15h service routine. ??Therefore, actually there > >> are two possible fixes, i. e., this fix or jumping directly to the fixed > >> entry point. ??However, we chose this fix because a) keyboard typematic > >> support via BIOS is becoming extremely rarer and b) we cannot support random > >> service routine installed by a firmware or a boot loader. ??This should fix > >> Lenovo X220 laptop, specifically. > >> > >> Be reasonable, please. > > > > I read the commit message -- sadly it also does not explain what the > > numbers mean. ??0xf000f859 and 0xf000e82e appear to be 32-bit vector > > addresses (e.g. used for indirect JMP), except nobody explains where > > those values came from or what they actually point to. ??Therefore, they > > are "magic values" until they can be defined otherwise. > > > > Someone digging through the source code is not going to see the commit > > message. ??They're going to have to track it down by hand using cvsweb or > > SVN, just to look at annotations. ??Don't worry, I don't mean for this to > > sound like I'm picking on this single commit -- this kind of craziness > > is all over the FreeBSD source tree, and as I said, it's infuriating > > when trying to look at the code (it is an open-source project, right?) > > and figure out what's going on/why something is the way it is. > > I'm not in good mood and I find it a waste of my time, sorry for that. > I have committed a fix (r222967). It's quite alright. I realise it sounds like I'm harping about nothing, but "magic numbers" usually are things that should be documented, even if just a one or two-line comment. The next time someone looks at the code, they'll say "Oh that's what those numbers are!" rather than "...what the heck?" > Just want to say that Jung-uk have spend a lot of his time > investigating and fixing this issue, and I just don't see why people > typing that much doesn't want to submit a patch. I think Open Source > projects expect everyone there to contribute rather than asking > someone else to do the work. And I appreciate his efforts, please don't get me wrong. I truly, honestly do. I wouldn't have known enough to fix the issue, for example, so it's not right for me to judge someone in comparison. My point was just that "magic number" concepts should usually be documented in the source, that way they're not arbitrary and future readers/committers won't have to mail -hackers 5 years from now asking "What do these values mean?" :-) Hope your day goes better! -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 01:51:09 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2A91106564A for ; Sat, 11 Jun 2011 01:51:09 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7787A8FC08 for ; Sat, 11 Jun 2011 01:51:09 +0000 (UTC) Received: by iwn33 with SMTP id 33so3764379iwn.13 for ; Fri, 10 Jun 2011 18:51:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:cc:subject:message-id :reply-to:references:mime-version:content-type:content-disposition :in-reply-to:x-openpgp-key-id:x-openpgp-key-fingerprint :x-openpgp-key-url; bh=nMiJp8Vs6gSZ9t3jZHEG1Gvy8IGD6qdqHNpnadjCcFo=; b=RLb05x6o4QX/S3BdL2WdFXUK32V4WBg/UjNuk7FsTH2Ki3bFfwYd8wp2LoB6n6yno3 PzU7BWA4r9UoY/byu9/m4wBIGiLfOlAMJbgEgmJcnDWLt1/AQkzVFZIVm4vDfl4FAk+t pdbW3/WZq/N9ro7K93/18vxu8k+03A8EQ4/aI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :x-openpgp-key-id:x-openpgp-key-fingerprint:x-openpgp-key-url; b=SbGFEoFLDJl5fxNn9azg2Is7nWaIM6RMXnD5DmjIn4oOE2jL6hXlpgjUzRwSC1SuI3 jzV37t/853ZffAbl8tFsdsl9WcUsHuAewSNhJ2JsqUoPch7/kb1JNjbza6XKz0bjiUXW VjTN/U+4MdWz0YLkxfz9zRz5L+OB/WV7y8fhc= Received: by 10.42.247.194 with SMTP id md2mr235180icb.478.1307757068923; Fri, 10 Jun 2011 18:51:08 -0700 (PDT) Received: from DataIX.net (adsl-99-181-139-216.dsl.klmzmi.sbcglobal.net [99.181.139.216]) by mx.google.com with ESMTPS id w11sm1601886ibw.41.2011.06.10.18.51.06 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Jun 2011 18:51:07 -0700 (PDT) Sender: "J. Hellenthal" Received: from DataIX.net (localhost [127.0.0.1]) by DataIX.net (8.14.4/8.14.4) with ESMTP id p5B1p34M040592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jun 2011 21:51:04 -0400 (EDT) (envelope-from jhell@DataIX.net) Received: (from jhell@localhost) by DataIX.net (8.14.4/8.14.4/Submit) id p5B1p2Fx040591; Fri, 10 Jun 2011 21:51:03 -0400 (EDT) (envelope-from jhell@DataIX.net) Date: Fri, 10 Jun 2011 21:51:02 -0400 From: Jason Hellenthal To: Arnaud Houdelette Message-ID: <20110611015101.GA52847@DataIX.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline In-Reply-To: X-OpenPGP-Key-Id: 0x89D8547E X-OpenPGP-Key-Fingerprint: 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E X-OpenPGP-Key-URL: http://bit.ly/0x89D8547E Cc: freebsd-stable@freebsd.org Subject: Re: Renaming ZFS datasets without unmount. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jhell@DataIX.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 01:51:09 -0000 --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Arnaud, On Wed, Jun 08, 2011 at 03:18:36PM +0200, Arnaud Houdelette wrote: >=20 > When I try to rename a mounted dataset with open files, I get the=20 > following error : >=20 > [carenath] /home/tzim# zfs rename unsafe/tmp unsafe/temp > cannot unmount '/tmp': Device busy >=20 > The mountpoint property is set locally : >=20 > [carenath] /home/tzim# zfs get mountpoint unsafe/tmp > NAME PROPERTY VALUE SOURCE > unsafe/tmp mountpoint /tmp local >=20 >=20 > zfs(1M) says : >=20 > Renamed file systems can inherit new mount points, in which case=20 > they are unmounted and remounted at the new mount point. >=20 >=20 > But here, the mountpoint should not change. So the file system does not= =20 > need to be remounted ... >=20 > Either I don't understand something, or there's an "error" in the man,=20 > or a bug in zfs rename. >=20 I think your confusion here is coming from the word 'rename' which is not operating at the file-level but at the VFS level. And in order to rename filesystem objects on any filesystem that I know of these days you need to free it by 'unmount' before you can perform any other operation on it that would dereference its name. Any other condition could result in a panic condition and also there is no way for the proccesses that were using it to be notified it was being moved. Generally filesystems like /tmp would not normally be renamed after they are created anyway and planning your filesystem layout properly will prevent from having too much downtime or maintenance time. AFAIS the correct description and result from using such commands is adequate to the results that can be obtained and the administrators knowledge of filesystems. Noone would dream of renaming /dev/ad0s1a while in operation so I think the same thing could be thought of 'zfs rename'. Think of datasets as devices. > It could be great if zfs allowed "live" renaming of mounted filesystem,= =20 > as It can avoid headaches... >=20 --=20 "Unity can only be manifested by the Binary. Unity itself and the idea of U= nity are already two." -- Buddha Regards, (jhell) Jason Hellenthal --SUOF0GtieIMvvwua Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: http://bit.ly/0x89D8547E iQEcBAEBAgAGBQJN8soFAAoJEJBXh4mJ2FR+UvAH/2PrOKkVeb1u7OO2YyXZznz9 NVDzNqnGArkk914pNdmVfp9YujUwal6rdVBmZ8APRmduP+zWL1Grgl4/4zn4Hsby BWlHUxSvnsQmCjf5HRe4F5O3mjm6tQ+Ucj5vIZyVH36CKBsQtbP+MUOyDm+8Hu06 kDo3ICZLlW16wK/6+A4F+G74r3bC6aro8wu8oe3S5LMqQB1TUl20qoUiC9AY1CrV h3Vbxhn+jP7RIDTnWGv5NjGmI/71nlSba6BArUR33QTEUIbb5JgnsBZOuyFf7Frs jAfhtQlLEKjVV78ve+q6JlnKnTi5Anqo3plnudX4iWUxISjaaXm1Z+Ai0eoZonM= =rBVy -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 02:47:35 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E68F106566C; Sat, 11 Jun 2011 02:47:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id DC6BD8FC0C; Sat, 11 Jun 2011 02:47:34 +0000 (UTC) Received: by yxm34 with SMTP id 34so275244yxm.13 for ; Fri, 10 Jun 2011 19:47:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=AVUNT3na6BEeA7N4mlQWYOCpj2I4JqTe+do2V+Pkq9M=; b=Opfv0WvaRTleG4XzbdStfXPv31RLgVXYlUoY5E4nL7oQb90c4RyXdjE7mRj5srE9Od A5VnBbTEz/FwsqUMjWnORmHemQlhGIo5Xz8RhCfznnoDiqjwQxyPNB39YXObkAY0H2a2 +Us+/CRaR/3GKkUGmp3V9Jkb1aPJnijIqu72Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=PN1diwKqOxPBpsd60Fwq6Noe5U/4iyuMUisKHbe7B08l0l3PN1iQvwVGbrN5Dpw/kH JrwKVUxrFEtR0sRQ/2vGZHpYTj7oYkVctoxDluoPa4k4mTT4EI8QS41Ey2bDEo0Q0d5/ d4WeAtHP8pH09WlPrrOEIa8xwCMcYeOLAO7CA= MIME-Version: 1.0 Received: by 10.151.95.16 with SMTP id x16mr4149737ybl.46.1307760454084; Fri, 10 Jun 2011 19:47:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.216.3 with HTTP; Fri, 10 Jun 2011 19:47:34 -0700 (PDT) In-Reply-To: <4DF274F6.6050905@gmail.com> References: <4DF12E4A.5020906@gmail.com> <201106100913.42480.bschmidt@freebsd.org> <4DF274F6.6050905@gmail.com> Date: Sat, 11 Jun 2011 10:47:34 +0800 X-Google-Sender-Auth: nOeR2esA9tyl5WyrkBtgVKkcSrg Message-ID: From: Adrian Chadd To: Jim Bryant Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, freebsd-wireless@freebsd.org, weongyo@freebsd.org, freebsd-usb@freebsd.org, bschmidt@freebsd.org Subject: Re: problem with urtw X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 02:47:35 -0000 On 11 June 2011 03:48, Jim Bryant wrote: > this is with if_urtw.c patched to change L to B as you supplied. > > I'm here for testing.. =A0any more ideas? =A0If anyone wants to play them= selves, > look on ebay for WiFiSky 1500mW B/G with 6dBi antenna. =A0It seems that h= alf > of Hong Kong is selling these for under $20 USD. I've enough wireless hardware. :) If someone: * buys me a pair; * demonstrates it runs fine under linux or some other open source operating system; * gives me enough time; Then sure, I may make this work. (The offer stands for Linux carl9170 compatible devices btw. I'll likely take a crack at porting that driver after my exams, but only once I've finished off the Atheros 11n TX code.) Adrian From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 15:30:10 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0C861065670 for ; Sat, 11 Jun 2011 15:30:10 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6677A8FC18 for ; Sat, 11 Jun 2011 15:30:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id p5BFU8gM065045 for ; Sat, 11 Jun 2011 19:30:08 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Sat, 11 Jun 2011 19:30:08 +0400 (MSD) From: Dmitry Morozovsky To: freebsd-stable@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (woozle.rinet.ru [0.0.0.0]); Sat, 11 Jun 2011 19:30:08 +0400 (MSD) Cc: Subject: stable/8-amd64 on ZFS as a vSphere backend X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 15:30:11 -0000 Dear colleagues, any particular hints to tune FreeBSD NFS server for efficient work as a VMware vSphere backend? For now, I set up 16G amd64 with ZFSv28, 4k recordsize and no other particular tuning, roundrobin lagg on 2 ems, mtu 9000. There are 4 WD RE3 1T disks as AHCI, on raid10 ZFS config. Local However, performance seems to be far from optimal (more deep testing is due, but at least average latency is too far, more than 100 ms). Local tests from zvol's (yes, that's not directly comparable but still) provide more than 500 MB/s on single/dual thread. Thanks in advance! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 16:17:31 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AFD11065783 for ; Sat, 11 Jun 2011 16:17:31 +0000 (UTC) (envelope-from listreader@lazlarlyricon.com) Received: from mailgw13.surf-town.net (mail13.surf-town.net [212.97.132.53]) by mx1.freebsd.org (Postfix) with ESMTP id 431F98FC0C for ; Sat, 11 Jun 2011 16:17:30 +0000 (UTC) Received: by mailgw13.surf-town.net (Postfix, from userid 65534) id 781C541314; Sat, 11 Jun 2011 18:01:09 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailgw13.surf-town.net (Postfix) with ESMTP id 62B0041312 for ; Sat, 11 Jun 2011 18:01:09 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailgw3.surf-town.net X-Spam-Flag: NO X-Spam-Score: -1.44 X-Spam-Level: X-Spam-Status: No, score=-1.44 tagged_above=-999 required=7 tests=[ALL_TRUSTED=-1.44] autolearn=disabled Received: from mailgw13.surf-town.net ([127.0.0.1]) by localhost (mailgw13.surf-town.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7Ykf3fReNGpp for ; Sat, 11 Jun 2011 18:01:04 +0200 (CEST) Received: from lazlar.kicks-ass.net (c-0987e355.09-42-6e6b7010.cust.bredbandsbolaget.se [85.227.135.9]) by mailgw13.surf-town.net (Postfix) with ESMTPA id 2DD7C41310 for ; Sat, 11 Jun 2011 18:01:04 +0200 (CEST) Message-ID: <4DF3913F.1000108@lazlarlyricon.com> Date: Sat, 11 Jun 2011 18:01:03 +0200 From: Rolf Nielsen User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; sv-SE; rv:1.9.2.17) Gecko/20110520 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: "log_sysevent: type 19 is not implemented" messages during boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 16:17:31 -0000 Hi all, After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get log_sysevent: type 19 is not implemented exactly 20 times during boot. What does that message mean? Need I worry about it? And even if it's harmless, it annoys me, so can I get rid of it, and if so, how? TIA, Rolf Nielsen From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 16:43:56 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A299106566B for ; Sat, 11 Jun 2011 16:43:56 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 57A8A8FC14 for ; Sat, 11 Jun 2011 16:43:56 +0000 (UTC) Received: by qyk35 with SMTP id 35so388299qyk.13 for ; Sat, 11 Jun 2011 09:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8ahDv0UTe2XABEeBaUvp0O9SwWdalUM+43OzU+FXloc=; b=KbtCACtBh8Mgx1f963Ejpsv8zCDqGosZjTnvKx7fSZfRfIWrgUlsxGRYNO1Ai9mEBa ysx/kN7SafH5cS4Ee1oQtM8Wp5N8Fm6ie4wj/uhnrdkyL0kP2lR704m+Gu6a10HIJfzU apRmS93YLzQ2nBznKyt9tX4sSrn9JWdnVgugw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dgR8xFwwGCK74dZqwpW7wFsrf8jCKXlrStPsjzrxluFGP21tiuAAfpPc+4w4CrxhST wnc3f8P4EcKd5WTZJUFoMomNwu86EwUtG8tA4lzFg1pGNXaqCRARfomeMPKNVgJr0onk 3Bbrkaf/ZIpPOHTAWNQa3WrEvxu2hhZf+S5Vg= MIME-Version: 1.0 Received: by 10.229.43.99 with SMTP id v35mr2560178qce.8.1307810635446; Sat, 11 Jun 2011 09:43:55 -0700 (PDT) Received: by 10.229.99.197 with HTTP; Sat, 11 Jun 2011 09:43:55 -0700 (PDT) In-Reply-To: <4DF3913F.1000108@lazlarlyricon.com> References: <4DF3913F.1000108@lazlarlyricon.com> Date: Sat, 11 Jun 2011 20:43:55 +0400 Message-ID: From: Sergey Kandaurov To: Rolf Nielsen Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: "log_sysevent: type 19 is not implemented" messages during boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 16:43:56 -0000 On 11 June 2011 20:01, Rolf Nielsen wrote: > Hi all, > > After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get > > log_sysevent: type 19 is not implemented > > exactly 20 times during boot. What does that message mean? Need I worry > about it? And even if it's harmless, it annoys me, so can I get rid of it, > and if so, how? > Hi. This warning indeed came with ZFS v28 recently merged to 8-STABLE. AFAIK it's rather harmless. It was silenced in current recently (see svn r222343), and the fix is expected to be merged to 8-STABLE soon. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 16:46:20 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02D77106566B for ; Sat, 11 Jun 2011 16:46:19 +0000 (UTC) (envelope-from listreader@lazlarlyricon.com) Received: from mailgw1.surf-town.net (mail11.surf-town.net [212.97.132.51]) by mx1.freebsd.org (Postfix) with ESMTP id AFBDC8FC0A for ; Sat, 11 Jun 2011 16:46:18 +0000 (UTC) Received: by mailgw1.surf-town.net (Postfix, from userid 65534) id A92891CD79B; Sat, 11 Jun 2011 18:46:17 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailgw1.surf-town.net (Postfix) with ESMTP id 7E32D1CD763; Sat, 11 Jun 2011 18:46:17 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mailgw1.surf-town.net X-Spam-Flag: NO X-Spam-Score: -1.44 X-Spam-Level: X-Spam-Status: No, score=-1.44 tagged_above=-999 required=7 tests=[ALL_TRUSTED=-1.44] autolearn=disabled Received: from mailgw1.surf-town.net ([127.0.0.1]) by localhost (mailgw1.surf-town.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KxVF+HERUbX4; Sat, 11 Jun 2011 18:46:12 +0200 (CEST) Received: from lazlar.kicks-ass.net (c-0987e355.09-42-6e6b7010.cust.bredbandsbolaget.se [85.227.135.9]) by mailgw1.surf-town.net (Postfix) with ESMTPA id 115441CD75D; Sat, 11 Jun 2011 18:46:11 +0200 (CEST) Message-ID: <4DF39BD2.2090607@lazlarlyricon.com> Date: Sat, 11 Jun 2011 18:46:10 +0200 From: Rolf Nielsen User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; sv-SE; rv:1.9.2.17) Gecko/20110520 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Sergey Kandaurov References: <4DF3913F.1000108@lazlarlyricon.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: "log_sysevent: type 19 is not implemented" messages during boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2011 16:46:20 -0000 2011-06-11 18:43, Sergey Kandaurov skrev: > On 11 June 2011 20:01, Rolf Nielsen wrote: >> Hi all, >> >> After going from 8.2-RELEASE to 8-STABLE (to get ZFS v28), I get >> >> log_sysevent: type 19 is not implemented >> >> exactly 20 times during boot. What does that message mean? Need I worry >> about it? And even if it's harmless, it annoys me, so can I get rid of it, >> and if so, how? >> > > Hi. > This warning indeed came with ZFS v28 recently merged to 8-STABLE. > AFAIK it's rather harmless. It was silenced in current recently (see svn > r222343), and the fix is expected to be merged to 8-STABLE soon. > Ok. Thanks. :)