From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 01:28:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7A932BA5 for ; Sun, 27 Jan 2013 01:28:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) by mx1.freebsd.org (Postfix) with ESMTP id 00156918 for ; Sun, 27 Jan 2013 01:28:35 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id gg13so2441389lbb.2 for ; Sat, 26 Jan 2013 17:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=9e2Gn7voQ5apxz6w+XKBBD+KrfAqWFr6JIRvdxp/Tes=; b=KysZpabUaXcsYwRbLBFOYtnGmoDUgnyLfx4Y67uxC24xXYXS7SeGKRY4Fq2KPRVvQK mhzd3Qth6VdYQ7wusDk5xMfJf/6eEU3DPBqa6VP6lcDdc7vsD1NyOCoeQs4LSBR7JCCJ STS2caMFmXO4d2WTJf1mQheym2w8V80NDkIvQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=9e2Gn7voQ5apxz6w+XKBBD+KrfAqWFr6JIRvdxp/Tes=; b=HEP85sZzUXi3GI46xHIosLqYC2R7IA4BFcrmdyQaRg3nSiGUowENdmxu1+FkF/c4DV mi1Og7OKp5iJU9aN7BvXTYBlkvlM38t1MZd0N2Okp/oG7iqvE32is/dSFJZJNFR5LuZ3 lPit3L3i57EpmgdY+XYv3ICVV8ge7y9zyfwMqgwze5V5E97fftMinQCO9GmAiPb93kbm sWq+Y2LCHERbKOyPO42lb4JjlsOOovTNVox08lH7/54NS9HsBwu4S61slVpdTNZ+N7wq rBpW+RCTARcQSFW9KFO20KvXmcRRnPKdAQ/EDVPsip4JJObSPkNVMg/68+zJeq0gz3dq CJfw== X-Received: by 10.152.106.5 with SMTP id gq5mr9295779lab.5.1359250114262; Sat, 26 Jan 2013 17:28:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.100.164 with HTTP; Sat, 26 Jan 2013 17:28:03 -0800 (PST) From: Eitan Adler Date: Sat, 26 Jan 2013 20:28:03 -0500 Message-ID: Subject: looking for some help from ppp users To: freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQll3YaYsEQLIW1avRjGS/rykW38X8O8zSRDb7I3W3nWfZ6Vr9jFMIgroH40IisKawRpkPsg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 01:28:36 -0000 Can people that use PPP please review the following FAQs ==== What do we care about? Is it factually correct? Does it use deprecated functionality? Is it completely outdated to the point we should remove it? Does it need better examples? Is it clear and concise? Does it have typos or spelling mistakes? Want to help with the patches? Install devel/subversion Install textproc/docproj-nojadetex svn checkout https://svn0.us-west.FreeBSD.org/doc/head edit en_US.ISO8859-1/books/faq/book.xml Test with running "make FORMATS=html" Send diffs ("svn diff") to doc@freebsd.org It isn't hard - its just like HTML. ===== http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-nodial-auto http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-drop-random http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-hangs-random http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-same-magic http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-lcp-constant http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-auto-noreasondial http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ccp-errors http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-connectionspeed http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-ignores-backslash http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#ppp-autodialprocess-noconnect http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#fcs-errors -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 10:36:14 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C2CF3901; Sun, 27 Jan 2013 10:36:14 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4CD9DA06; Sun, 27 Jan 2013 10:36:14 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0RAaC2Y099978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 27 Jan 2013 11:36:12 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Sun, 27 Jan 2013 11:36:12 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: current@FreeBSD.org, fs@FreeBSD.org Subject: Zpool surgery Message-ID: <20130127103612.GB38645@acme.spoerlein.net> Mail-Followup-To: current@FreeBSD.org, fs@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 10:36:14 -0000 Hey all, I have a slight problem with transplanting a zpool, maybe this is not possible the way I like to do it, maybe I need to fuzz some identifiers... I want to transplant my old zpool tank from a 1TB drive to a new 2TB drive, but *not* use dd(1) or any other cloning mechanism, as the pool was very full very often and is surely severely fragmented. So, I have tank (the old one), the new one, let's call it tank' and then there's the archive pool where snapshots from tank are sent to, and these should now come from tank' in the future. I have: tank -> sending snapshots to archive I want: tank' -> sending snapshots to archive Ideally I would want archive to not even know that tank and tank' are different, so as to not have to send a full snapshot again, but continue the incremental snapshots. So I did zfs send -R tank | ssh otherhost "zfs recv -d tank" and that worked well, this contained a snapshot A that was also already on archive. Then I made a final snapshot B on tank, before turning down that pool and sent it to tank' as well. Now I have snapshot A on tank, tank' and archive and they are virtually identical. I have snapshot B on tank and tank' and would like to send this from tank' to archive, but it complains: cannot receive incremental stream: most recent snapshot of archive does not match incremental source Is there a way to tweak the identity of tank' to be *really* the same as tank, so that archive can accept that incremental stream? Or should I use dd(1) after all to transplant tank to tank'? My other option would be to turn on dedup on archive and send another full stream of tank', 99.9% of which would hopefully be deduped and not consume precious space on archive. Any ideas? Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 11:06:54 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2819E7D; Sun, 27 Jan 2013 11:06:54 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id A4930AF2; Sun, 27 Jan 2013 11:06:54 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r0RB6mRI094749; Sun, 27 Jan 2013 06:06:48 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r0RB6lLb094734; Sun, 27 Jan 2013 11:06:47 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 27 Jan 2013 11:06:47 GMT Message-Id: <201301271106.r0RB6lLb094734@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 11:06:54 -0000 TB --- 2013-01-27 10:10:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-27 10:10:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-27 10:10:20 - starting HEAD tinderbox run for arm/arm TB --- 2013-01-27 10:10:20 - cleaning the object tree TB --- 2013-01-27 10:10:20 - /usr/local/bin/svn stat /src TB --- 2013-01-27 10:10:24 - At svn revision 245977 TB --- 2013-01-27 10:10:25 - building world TB --- 2013-01-27 10:10:25 - CROSS_BUILD_TESTING=YES TB --- 2013-01-27 10:10:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-27 10:10:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-27 10:10:25 - SRCCONF=/dev/null TB --- 2013-01-27 10:10:25 - TARGET=arm TB --- 2013-01-27 10:10:25 - TARGET_ARCH=arm TB --- 2013-01-27 10:10:25 - TZ=UTC TB --- 2013-01-27 10:10:25 - __MAKE_CONF=/dev/null TB --- 2013-01-27 10:10:25 - cd /src TB --- 2013-01-27 10:10:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Jan 27 10:10:30 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Jan 27 11:06:47 UTC 2013 TB --- 2013-01-27 11:06:47 - generating LINT kernel config TB --- 2013-01-27 11:06:47 - cd /src/sys/arm/conf TB --- 2013-01-27 11:06:47 - /usr/bin/make -B LINT TB --- 2013-01-27 11:06:47 - cd /src/sys/arm/conf TB --- 2013-01-27 11:06:47 - /usr/sbin/config -m LINT TB --- 2013-01-27 11:06:47 - building LINT kernel TB --- 2013-01-27 11:06:47 - CROSS_BUILD_TESTING=YES TB --- 2013-01-27 11:06:47 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-27 11:06:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-27 11:06:47 - SRCCONF=/dev/null TB --- 2013-01-27 11:06:47 - TARGET=arm TB --- 2013-01-27 11:06:47 - TARGET_ARCH=arm TB --- 2013-01-27 11:06:47 - TZ=UTC TB --- 2013-01-27 11:06:47 - __MAKE_CONF=/dev/null TB --- 2013-01-27 11:06:47 - cd /src TB --- 2013-01-27 11:06:47 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jan 27 11:06:47 UTC 2013 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/arm/conf; PATH=/obj/arm.arm/src/tmp/legacy/usr/sbin:/obj/arm.arm/src/tmp/legacy/usr/bin:/obj/arm.arm/src/tmp/legacy/usr/games:/obj/arm.arm/src/tmp/usr/sbin:/obj/arm.arm/src/tmp/usr/bin:/obj/arm.arm/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/arm.arm/src/sys/LINT /src/sys/arm/conf/LINT WARNING: duplicate option `GEOM_PART_BSD' encountered. WARNING: duplicate option `GEOM_PART_MBR' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `CAM_DEBUG_DELAY' encountered. config: ../mv/kirkwood/files.sheevaplug: No such file or directory *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-27 11:06:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-01-27 11:06:47 - ERROR: failed to build LINT kernel TB --- 2013-01-27 11:06:47 - 2534.13 user 577.03 system 3387.27 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 12:53:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9CA0DD08; Sun, 27 Jan 2013 12:53:56 +0000 (UTC) (envelope-from bland@FreeBSD.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 3E084EF6; Sun, 27 Jan 2013 12:53:55 +0000 (UTC) Received: from eee.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 606D218C9F; Sun, 27 Jan 2013 21:53:48 +0900 (JST) Received: from nest.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) (authenticated bits=0) by eee.bbnest.net (8.14.6/8.14.5) with ESMTP id r0RCqHQX001467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 27 Jan 2013 21:52:18 +0900 (JST) (envelope-from bland@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: ZFS + usb in trouble? From: Alexander Nedotsukov In-Reply-To: <20130123134601.GB53514@garage.freebsd.pl> Date: Sun, 27 Jan 2013 21:52:20 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <845D0D19-7191-4EDD-8EDE-1331E13821CB@FreeBSD.org> References: <20130121205851.GB1341@garage.freebsd.pl> <20130121211718.GD1341@garage.freebsd.pl> <20130122181012.GD1714@garage.freebsd.pl> <20130123134601.GB53514@garage.freebsd.pl> To: Pawel Jakub Dawidek , "hselasky@FreeBSD.org" X-Mailer: Apple Mail (2.1499) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Sun Jan 27 21:53:48 2013 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 5105235b14686911810420 Cc: FreeBSD Current , "freebsd-usb@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 12:53:56 -0000 Thank you, Pawel. Hans, can please you take a look at your commits done on Dec 20 (r244500 = and r244503)? They are seems to be the culprit. On 23.01.2013, at 22:46, Pawel Jakub Dawidek wrote: > On Wed, Jan 23, 2013 at 09:11:23PM +0900, Alexander Nedotsukov wrote: >> And now both are failing, although zfs in a different way. >=20 > Yes, but now we are sure this is not ZFS issue. Sequential read simply > doesn't trigger the corruption, but ZFS access patterns do. The read > errors you are seeing are due to GELI returning EIO on integrity > verification error. >=20 >> # zpool status >> pool: testpool >> state: ONLINE >> status: One or more devices has experienced an unrecoverable error. = An >> attempt was made to correct the error. Applications are = unaffected. >> action: Determine if the device needs to be replaced, and clear the = errors >> using 'zpool clear' or replace the device with 'zpool replace'. >> see: http://illumos.org/msg/ZFS-8000-9P >> scan: scrub repaired 1M in 0h2m with 0 errors on Wed Jan 23 20:57:11 = 2013 >> config: >>=20 >> NAME STATE READ WRITE CKSUM >> testpool ONLINE 0 0 0 >> raidz1-0 ONLINE 0 0 0 >> da5.elid ONLINE 0 0 0 >> da5.elie ONLINE 21 0 0 >> da5.elif ONLINE 0 0 0 >>=20 >> # dmesg | tail -20 >> GEOM_ELI: da1.eli: Failed to authenticate 131072 bytes of data at = offset 1010827264. >> ath0: bb hang detected (0x4), resetting >> GEOM_ELI: Device da5.eli created. >> GEOM_ELI: Encryption: AES-XTS 128 >> GEOM_ELI: Integrity: HMAC/SHA1 >> GEOM_ELI: Crypto: software >> GEOM_ELI: da5.eli: Failed to authenticate 4096 bytes of data at = offset 4096. >> GEOM_ELI: da5.eli: Failed to authenticate 4096 bytes of data at = offset 0. >> GEOM_ELI: da5.eli: Failed to authenticate 5792 bytes of data at = offset 229288288. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 229429248. >> GEOM_ELI: da5.eli: Failed to authenticate 131072 bytes of data at = offset 229298176. >> GEOM_ELI: da5.eli: Failed to authenticate 26496 bytes of data at = offset 229494784. >> GEOM_ELI: da5.eli: Failed to authenticate 12288 bytes of data at = offset 270299136. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 270319616. >> GEOM_ELI: da5.eli: Failed to authenticate 5792 bytes of data at = offset 273095488. >> GEOM_ELI: da5.eli: Failed to authenticate 56864 bytes of data at = offset 273105376. >> GEOM_ELI: da5.eli: Failed to authenticate 2400 bytes of data at = offset 273326080. >> GEOM_ELI: da5.eli: Failed to authenticate 65536 bytes of data at = offset 272560128. >> GEOM_ELI: da5.eli: Failed to authenticate 131072 bytes of data at = offset 272429056. >> GEOM_ELI: da5.eli: Failed to authenticate 32768 bytes of data at = offset 272396288. >=20 > --=20 > Pawel Jakub Dawidek http://www.wheelsystems.com > FreeBSD committer http://www.FreeBSD.org > Am I Evil? Yes, I Am! http://tupytaj.pl From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 14:00:27 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD3958F3; Sun, 27 Jan 2013 14:00:27 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) by mx1.freebsd.org (Postfix) with ESMTP id 37874132; Sun, 27 Jan 2013 14:00:26 +0000 (UTC) Received: from [78.35.163.65] (helo=fabiankeil.de) by smtprelay02.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TzSmQ-0004Q3-NA; Sun, 27 Jan 2013 15:00:18 +0100 Date: Sun, 27 Jan 2013 14:56:01 +0100 From: Fabian Keil To: Ulrich =?UTF-8?B?U3DDtnJsZWlu?= Subject: Re: Zpool surgery Message-ID: <20130127145601.7f650d3c@fabiankeil.de> In-Reply-To: <20130127103612.GB38645@acme.spoerlein.net> References: <20130127103612.GB38645@acme.spoerlein.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/FJX6_h0WkAB0cAJZ1ipHtOB"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: current@FreeBSD.org, fs@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:00:27 -0000 --Sig_/FJX6_h0WkAB0cAJZ1ipHtOB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ulrich Sp=C3=B6rlein wrote: > I have a slight problem with transplanting a zpool, maybe this is not > possible the way I like to do it, maybe I need to fuzz some > identifiers... >=20 > I want to transplant my old zpool tank from a 1TB drive to a new 2TB > drive, but *not* use dd(1) or any other cloning mechanism, as the pool > was very full very often and is surely severely fragmented. >=20 > So, I have tank (the old one), the new one, let's call it tank' and > then there's the archive pool where snapshots from tank are sent to, and > these should now come from tank' in the future. >=20 > I have: > tank -> sending snapshots to archive >=20 > I want: > tank' -> sending snapshots to archive >=20 > Ideally I would want archive to not even know that tank and tank' are > different, so as to not have to send a full snapshot again, but > continue the incremental snapshots. >=20 > So I did zfs send -R tank | ssh otherhost "zfs recv -d tank" and that > worked well, this contained a snapshot A that was also already on > archive. Then I made a final snapshot B on tank, before turning down that > pool and sent it to tank' as well. >=20 > Now I have snapshot A on tank, tank' and archive and they are virtually > identical. I have snapshot B on tank and tank' and would like to send > this from tank' to archive, but it complains: >=20 > cannot receive incremental stream: most recent snapshot of archive does > not match incremental source In general this should work, so I'd suggest that you double check that you are indeed sending the correct incremental. > Is there a way to tweak the identity of tank' to be *really* the same as > tank, so that archive can accept that incremental stream? Or should I > use dd(1) after all to transplant tank to tank'? My other option would > be to turn on dedup on archive and send another full stream of tank', > 99.9% of which would hopefully be deduped and not consume precious space > on archive. The pools don't have to be the same. I wouldn't consider dedup as you'll have to recreate the pool if it turns out the the dedup performance is pathetic. On a system that hasn't been created with dedup in mind that seems rather likely. > Any ideas? Your whole procedure seems a bit complicated to me. Why don't you use "zpool replace"? Fabian --Sig_/FJX6_h0WkAB0cAJZ1ipHtOB Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEFMfgACgkQBYqIVf93VJ11YQCgst43rQ0fEPedB1gaEUIocoQS I/IAni9cEfESXBY5DZOO+mJ44csGHkYN =nniE -----END PGP SIGNATURE----- --Sig_/FJX6_h0WkAB0cAJZ1ipHtOB-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 14:31:27 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6528BEC3; Sun, 27 Jan 2013 14:31:27 +0000 (UTC) (envelope-from prvs=1739a0aae4=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id B66D4258; Sun, 27 Jan 2013 14:31:25 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001877953.msg; Sun, 27 Jan 2013 14:31:18 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 27 Jan 2013 14:31:18 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1739a0aae4=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> From: "Steven Hartland" To: =?iso-8859-1?Q?Ulrich_Sp=F6rlein?= , , References: <20130127103612.GB38645@acme.spoerlein.net> Subject: Re: Zpool surgery Date: Sun, 27 Jan 2013 14:31:56 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:31:27 -0000 ----- Original Message ----- From: "Ulrich Spörlein" > I have a slight problem with transplanting a zpool, maybe this is not > possible the way I like to do it, maybe I need to fuzz some > identifiers... > > I want to transplant my old zpool tank from a 1TB drive to a new 2TB > drive, but *not* use dd(1) or any other cloning mechanism, as the pool > was very full very often and is surely severely fragmented. > Cant you just drop the disk in the original machine, set it as a mirror then once the mirror process has completed break the mirror and remove the 1TB disk. If this is a boot disk don't forget to set the boot block as well. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 14:54:28 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E06D1738; Sun, 27 Jan 2013 14:54:28 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x22f.google.com (ie-in-x022f.1e100.net [IPv6:2607:f8b0:4001:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 748A5348; Sun, 27 Jan 2013 14:54:28 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id c12so9231ieb.20 for ; Sun, 27 Jan 2013 06:54:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+pKTfnRqzbWS09RCaOG86XD13koGRYnf2xF/rpCzF0A=; b=mpaAzVheFC3qWalXxCCrGMuIIFGN6EEd+Tybe9VwGaJ1hfzWDOsp8XL2dNNK25g88b 0CpPVENQO/qyIW3cBFH4XdhHR2w1CzllCH/IXJv+mDCsZaKjcBacieTHolK/i6b5YvGL hB6Wy3OetxbOwrGMMd4sw0NTMnXK4Hw+Mc2yXBflff616eyUGs6La8dew5KjdVrYWmHu fKBCbQ2TPEw1Tvte3A3OCUTK9mnl7Rpo/G8bkjHpwXv018hcXA9H2KHGsGhX/4gV9yyk 3d+DPm/noKY3FluVNWlq1a/x+Vw39eVMU4CHhvd7tPnSdhjd0wj+dhFX33aSfg5EL2+T C4vA== MIME-Version: 1.0 X-Received: by 10.50.214.10 with SMTP id nw10mr3061777igc.15.1359298468005; Sun, 27 Jan 2013 06:54:28 -0800 (PST) Received: by 10.64.16.73 with HTTP; Sun, 27 Jan 2013 06:54:27 -0800 (PST) Received: by 10.64.16.73 with HTTP; Sun, 27 Jan 2013 06:54:27 -0800 (PST) In-Reply-To: <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> Date: Sun, 27 Jan 2013 14:54:27 +0000 Message-ID: Subject: Re: Zpool surgery From: Chris Rees To: Steven Hartland Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:54:29 -0000 On 27 Jan 2013 14:31, "Steven Hartland" wrote: > > ----- Original Message ----- From: "Ulrich Sp=F6rlein" > > >> I have a slight problem with transplanting a zpool, maybe this is not >> possible the way I like to do it, maybe I need to fuzz some >> identifiers... >> >> I want to transplant my old zpool tank from a 1TB drive to a new 2TB >> drive, but *not* use dd(1) or any other cloning mechanism, as the pool >> was very full very often and is surely severely fragmented. >> > > Cant you just drop the disk in the original machine, set it as a mirror > then once the mirror process has completed break the mirror and remove > the 1TB disk. > > If this is a boot disk don't forget to set the boot block as well. I managed to replace a drive this way without even rebooting. I believe it's the same as a zpool replace. Chris From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 14:56:19 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 250C1A41; Sun, 27 Jan 2013 14:56:19 +0000 (UTC) (envelope-from prvs=1739a0aae4=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 976F1382; Sun, 27 Jan 2013 14:56:18 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001878220.msg; Sun, 27 Jan 2013 14:56:16 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 27 Jan 2013 14:56:16 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1739a0aae4=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> From: "Steven Hartland" To: "Vladislav Prodan" References: <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> Subject: Re: Re[2]: AHCI timeout when using ZFS + AIO + NCQ Date: Sun, 27 Jan 2013 14:56:52 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1251"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:56:19 -0000 ----- Original Message ----- From: "Vladislav Prodan" >> Is it always the same disk, of so replace it SMART helps identify issues >> but doesn't tell you 100% there's no problem. > > > Now it has fallen off a different HDD - ada0. > I'm 99% sure that MHDD will not find problems in HDD - ada0 and ada2. > I still have three servers with similar chipsets that have similar problems > with blade ahci times out. I notice your disks are connecting at SATA 3.x, which rings bells. We had a very similar issue on a new Supermicro machine here and after much testing we proved to our satisfaction that the problem was the HW. Essentially the combination of SATA 3 speeds the midplane / backplane degraded the connection between the MB and HDD enough to cause the disks to randomly drop when under load. If we connected the disks directly to the MB with SATA cables the problem went away. In the end we had midplanes changed from an AHCI pass-through to active LSI controller. So if you have any sort of midplane / backplane connecting your disks try connecting them direct to the MB / controller via known SATA 3.x compliant cables and see if that stops the drops. Another test you can do is to force the disks to connect at SATA 2.x this also fixed it in our case, but wasn't something we wanted to put into production hence the controller swap. To force SATA 2 speeds you can use the following in /boot/loader.conf where 'X' is disk identifier e.g. for ada0 X = 0:- hint.ahcich.X.sata_rev=2 Hope this helps. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 14:56:52 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BC70FBB8; Sun, 27 Jan 2013 14:56:52 +0000 (UTC) (envelope-from universite@ukr.net) Received: from ffe15.ukr.net (ffe15.ukr.net [195.214.192.50]) by mx1.freebsd.org (Postfix) with ESMTP id 44A9939A; Sun, 27 Jan 2013 14:56:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Date:Message-Id:From:To:References:In-Reply-To:Subject:Cc:Content-Type:Content-Transfer-Encoding:MIME-Version; bh=BJYHeKR7eBEVXWimtxiFQHBLwTNZ7ccMMCeS+OY67SI=; b=tT/t+Tzvfv2tHCj10pm29lc8jWiEiPQQeDvc4vUpp9k+P5Cy4vxy75XYr2wt1DWHKMPWdItBCoDrWYbm4f2EOTyy+2yAFk5ih22MqegzTJSSGQIcuuvFtVjGAkQfI31ZlDwe6ohRGikCgki6of0NnQWid+6Ypxo3jMWSam2D3F0=; Received: from mail by ffe15.ukr.net with local ID 1TzTO3-000OUJ-Cy ; Sun, 27 Jan 2013 16:39:11 +0200 MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: binary Content-Type: text/plain; charset="windows-1251" Subject: Re[2]: AHCI timeout when using ZFS + AIO + NCQ In-Reply-To: <221B307551154F489452F89E304CA5F7@multiplay.co.uk> References: <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> To: "Steven Hartland" From: "Vladislav Prodan" X-Mailer: freemail.ukr.net 4.0 Message-Id: <93308.1359297551.14145052969567453184@ffe15.ukr.net> X-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Date: Sun, 27 Jan 2013 16:39:11 +0200 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 14:56:52 -0000 > Is it always the same disk, of so replace it SMART helps identify issues > but doesn't tell you 100% there's no problem. Now it has fallen off a different HDD - ada0. I'm 99% sure that MHDD will not find problems in HDD - ada0 and ada2. I still have three servers with similar chipsets that have similar problems with blade ahci times out. > ----- Original Message ----- > From: "Vladislav Prodan" > To: > Cc: > Sent: Thursday, January 24, 2013 12:19 PM > Subject: AHCI timeout when using ZFS + AIO + NCQ > > > >I have the server: > > > > FreeBSD 9.1-PRERELEASE #0: Wed Jul 25 01:40:56 EEST 2012 > > > > Jan 24 12:53:01 vesuvius kernel: atapci0: port > > 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f mem 0xfe210000-0xfe2101ff irq 51 at device 0.0 on pci3 > > ... > > Jan 24 12:53:01 vesuvius kernel: ahci0: port > > 0xf040-0xf047,0xf030-0xf033,0xf020-0xf027,0xf010-0xf013,0xf000-0xf00f mem 0xfe307000-0xfe3073ff irq 19 at device 17.0 on pci0 > > Jan 24 12:53:01 vesuvius kernel: ahci0: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported > > ... > > Jan 24 12:53:01 vesuvius kernel: ada2 at ahcich2 bus 0 scbus4 target 0 lun 0 > > Jan 24 12:53:01 vesuvius kernel: ada2: ATA-8 SATA 3.x device > > Jan 24 12:53:01 vesuvius kernel: ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) > > Jan 24 12:53:01 vesuvius kernel: ada2: Command Queueing enabled > > Jan 24 12:53:01 vesuvius kernel: ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C) > > Jan 24 12:53:01 vesuvius kernel: ada2: Previously was known as ad12 > > ... > > I use 4 HDD in RAID10 via ZFS. > > > > With a very irregular intervals fall off HDD drives. As a result, the server stops. > > > > Jan 24 06:48:06 vesuvius kernel: ahcich2: Timeout on slot 6 port 0 > > Jan 24 06:48:06 vesuvius kernel: ahcich2: is 00000000 cs 00000000 ss 000000c0 rs 000000c0 tfd 40 serr 00000000 cmd 0000e817 > > Jan 24 06:48:06 vesuvius kernel: (ada2:ahcich2:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 4c 4e 1e 40 68 00 00 01 00 00 > > Jan 24 06:48:06 vesuvius kernel: (ada2:ahcich2:0:0:0): CAM status: Command timeout > > Jan 24 06:48:06 vesuvius kernel: (ada2:ahcich2:0:0:0): Retrying command > > Jan 24 06:51:11 vesuvius kernel: ahcich2: AHCI reset: device not ready after 31000ms (tfd = 00000080) > > Jan 24 06:51:11 vesuvius kernel: ahcich2: Timeout on slot 8 port 0 > > Jan 24 06:51:11 vesuvius kernel: ahcich2: is 00000000 cs 00000100 ss 00000000 rs 00000100 tfd 00 serr 00000000 cmd 0000e817 > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): CAM status: Command timeout > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): Error 5, Retry was blocked > > Jan 24 06:51:11 vesuvius kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4227133, size: 8192 > > Jan 24 06:51:11 vesuvius kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4227133, size: 8192 > > Jan 24 06:51:11 vesuvius kernel: ahcich2: AHCI reset: device not ready after 31000ms (tfd = 00000080) > > Jan 24 06:51:11 vesuvius kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 4227133, size: 8192 > > Jan 24 06:51:11 vesuvius kernel: ahcich2: Timeout on slot 8 port 0 > > Jan 24 06:51:11 vesuvius kernel: ahcich2: is 00000000 cs 00000100 ss 00000000 rs 00000100 tfd 00 serr 00000000 cmd 0000e817 > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): CAM status: Command timeout > > Jan 24 06:51:11 vesuvius kernel: (aprobe0:ahcich2:0:0:0): Error 5, Retry was blocked > > Jan 24 06:51:11 vesuvius kernel: swap_pager: I/O error - pagein failed; blkno 4227133,size 8192, error 6 > > Jan 24 06:51:11 vesuvius kernel: (ada2:(pass2:vm_fault: pager read error, pid 1943 (named) > > Jan 24 06:51:11 vesuvius kernel: ahcich2:0:ahcich2:0:0:0:0): lost device > > Jan 24 06:51:11 vesuvius kernel: 0): passdevgonecb: devfs entry is gone > > Jan 24 06:51:11 vesuvius kernel: pid 1943 (named), uid 53: exited on signal 11 > > ... > > > > Helps only restart by pressing Power. > > Judging by the state of SMART, HDD have no problems. SATA data cable changed. > > > > > > I found a similar problem: > > > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-February/055374.html > > PR: amd64/165547: NVIDIA MCP67 AHCI SATA controller timeout > > > > -- > > Vladislav V. Prodan > > System & Network Administrator > > http://support.od.ua > > +380 67 4584408, +380 99 4060508 > > VVP88-RIPE -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 15:29:05 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A3FE55B8; Sun, 27 Jan 2013 15:29:05 +0000 (UTC) (envelope-from universite@ukr.net) Received: from ffe11.ukr.net (ffe11.ukr.net [195.214.192.31]) by mx1.freebsd.org (Postfix) with ESMTP id 5511A734; Sun, 27 Jan 2013 15:29:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Date:Message-Id:From:To:References:In-Reply-To:Subject:Cc:Content-Type:Content-Transfer-Encoding:MIME-Version; bh=KA3pILGNPBJkWcpAOJAYYa+9vxKGxcXhrIZ+SsImMNo=; b=C/fyFj5QdF2pqtrKTZinJdNeCy1WcGK2v1aRtcfK8JlWdZ66n2w1VaslcpA2T3rskP6ez496vmWq14Y/kIdfYMbfj1M6GmyQg5Q431bDrf99VTN7cpJWdeqjLKhHPPTsh2UBMmdj0ASbG+X/Sv8Z+KsSFo4rNlE7HirG30yUXxY=; Received: from mail by ffe11.ukr.net with local ID 1TzTvB-000Idu-Kk ; Sun, 27 Jan 2013 17:13:25 +0200 MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: binary Content-Type: text/plain; charset="windows-1251" Subject: Re[2]: Re[2]: AHCI timeout when using ZFS + AIO + NCQ In-Reply-To: <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> References: <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> To: "Steven Hartland" From: "Vladislav Prodan" X-Mailer: freemail.ukr.net 4.0 Message-Id: <70362.1359299605.3196836531757973504@ffe11.ukr.net> X-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Date: Sun, 27 Jan 2013 17:13:25 +0200 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 15:29:05 -0000 > ----- Original Message ----- > From: "Vladislav Prodan" > > >> Is it always the same disk, of so replace it SMART helps identify issues > >> but doesn't tell you 100% there's no problem. > > > > > > Now it has fallen off a different HDD - ada0. > > I'm 99% sure that MHDD will not find problems in HDD - ada0 and ada2. > > I still have three servers with similar chipsets that have similar problems > > with blade ahci times out. > > I notice your disks are connecting at SATA 3.x, which rings bells. We had > a very similar issue on a new Supermicro machine here and after much > testing we proved to our satisfaction that the problem was the HW. I have a motherboard ASUS M5A97 PRO http://www.asus.com/Motherboard/M5A97_PRO/#specifications Has replacement SATA data cables. Putting hard RAID controller does not guarantee data recovery at his death. > Essentially the combination of SATA 3 speeds the midplane / backplane > degraded the connection between the MB and HDD enough to cause > the disks to randomly drop when under load. > > If we connected the disks directly to the MB with SATA cables the > problem went away. In the end we had midplanes changed from an > AHCI pass-through to active LSI controller. > > So if you have any sort of midplane / backplane connecting your disks > try connecting them direct to the MB / controller via known SATA 3.x > compliant cables and see if that stops the drops. > > Another test you can do is to force the disks to connect at SATA 2.x > this also fixed it in our case, but wasn't something we wanted to > put into production hence the controller swap. > > To force SATA 2 speeds you can use the following in /boot/loader.conf > where 'X' is disk identifier e.g. for ada0 X = 0:- > hint.ahcich.X.sata_rev=2 > > Hope this helps. > > Regards > Steve > -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 15:57:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2AA2EC47; Sun, 27 Jan 2013 15:57:27 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 58DE882D; Sun, 27 Jan 2013 15:57:26 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0RFvJE0001816; Sun, 27 Jan 2013 10:57:24 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <51054E5F.9040309@m5p.com> Date: Sun, 27 Jan 2013 10:57:19 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: devel/gobject-introspection failure on ARM Content-Type: multipart/mixed; boundary="------------030402070507010503080404" X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 27 Jan 2013 10:57:25 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 15:57:27 -0000 This is a multi-part message in MIME format. --------------030402070507010503080404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) ports: svnversion 308518 Build dies with message "sizeof(ArrayTypeBlob) is expected to be 8 but is 12." (Complete build log attached.) I made a naive attempt to fix it by rearranging the order of the structure members, but obviously I don't understand structure packing on the ARM and it didn't help. It also didn't get rid of the huge number of "cast increases required alignment of target type" warnings. I note we're at version 0.10.8 of this package, but upstream is at 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). What's the best way to proceed? -- George Mitchell --------------030402070507010503080404 Content-Type: application/octet-stream; name="typescript.xz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="typescript.xz" /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4MgnEl5dACmYykarec1wWuOyuHWSQFx0n4Zq604V nFcmHlPRkADlTlOZLw0msE/U8dPeI6SvupvWPjTwbxTU7RyBCMsH2F023Uyb+M3rzANb4C+0 Qh5FVIbHSQKjRUuvh5tqb1wMdS4dt8jepBwGAe0RZbcb0k5668HnMzhHUEiq9534prFkPl98 47VnLu2wCev4OY6jB7Kwdv73XvbnFIEFy8wYQVUJzzCrGh16gw9iC5awEqVfoit0o+Jlb1qT bISnTaqkzaC+DN7YR6SvnxVw0l0CG57oBJobtC4n5iXICQh+5vGnFvGRWNOzkYvXMgo6xcV1 BfRcMeDbu9NsaLujTLD6OYH54lHPjnNrRxHXLNUjCTzq25Zgmwf0ilu0PFYEiS6GTvlVwP30 IaNjX5+ctNpcJS4xMmabCw/igs4PBki7UmGgxJIA7HBPtsGeMGDefdI8gyGUSgX+EfsCxyhz fULkdQWz7ZubqZBWZZsVJtRxxxYlHRfSz7Z/gzIdcwjTy43k77V1Tj+0XbMVkBUzlbJu8EVV BLg8Fbcoc+3IgeO2k37YzPC5O2/rb5L1VgFRnmmSWCTyRz0KMdjPLAxuQ2onUFl8u3d73THD 6dcHcoXxxwLkxfWAyCzfq58IDhmAI8QLD+DzCpQpAZzVrVydVffcaweXda7OU9I9iO277iKh ozPlE9lPcQbmAcLVs7k3iOaGtYqGsBG9NcWrMqJNq4IL0G0EsoWwydn14vp1BxmWntLipW6p YVqoXWC8i8LKUO72tHfLKlwBC/0FFhYqTytqvcX+DaktqE8iLJC5RjFgriOnkVcBXaVn1yNJ ggtvMT3ByRe6GGb1k9aYKhBoZTXEFSxCtZ6xiztlLKKczhTXt5wkDewe12eyIIAo9hLt9tgF VV3FiQh0nPa4MnDp36JNOzyMPuRRdXKW9MQX5B77uJlDQF9o28JpbaRzWH/ySCE+/6PGlI+U JCJbAfM7tIgbniZW+9VjHJlCk6JRaY0dQF+CfcRc2wLK3esQQZtErkGZdNRWQtoJMRztn5UD 1D5l08ODFUQNA0TXY3fgrgr9sjqSTe6cl6r+7YO+3zGkw79umner0qT0OrNMlb7XkDw1n51z B1kybqwqNBoPW2tQ0nYytQjtTEWMdwGvsbLMRbQ7O3P01FEIIC7IMro4ls2prWIHYDyT1QEy rm6iMEAWKu6ZvzDum5pJOY3Fw6B06H+ac0xLmj0LotVZTIDngF8hXslSGBvBUtdKQLuzqtKf 5J4KdldpprqdkZXwjxsQesJCVmRTirRBtubzf0/tkkQavVTxShfJ4N5WCO8kwxGPBDTByW4e vcHzxViVZQeSTXZjsJjnMk8U+lr/1WtbHf+1nS/LT8Pa1LcHN6xSNdLH+gzS+W95KX7N5z2X IhurGa4LgQ1VRTpTRBBJ6mKE4L1WcaBRffL04jgwjgVcCsRPDf0YZ8FYz9h6Tt9dOKiuUGH/ lslITvxUwPxOSbPv6S2Tg4ipQIQDgsNUXM5nHcsEvrIjNjeXmt8yHOpCnQUSBgt8t9fd78xU i/N6RuVKKBH2lWhNdJFLsYfrKxvxPWkfH259/TzkWuV6ZzbEBmO6tr3IS37g5oo4Hg/l4Bdc 32T05QW6prP61eTxUD+DasYM98+djE6+4EsCTHmTza1M1qG95qdOesT3QSokai1p038hIrrC 5WvLtTYEdn4H8CloceW1U2PXZ4D638ti3wvaXdYqF7PVx3L9M6wUsHyRdG6ujk/xz3ZV3HDk NjUD9jheSTQngiD/IlCdfLEc5zBiVFsklx/2b2sMeuGpt71tsFHaleA159oIxBzlkXnj7Ked r0a3kGLATP9DOl3f3cbM2HjVHTQLUn9sIyigWRvA55Xv0XLdP5/zKX9hy80NUrP+Taiq9dyb ujTWrnD4yf4KjOs9NKYzqgYVU7t+qqa21zi5PHdNj8YmWOLJ36WbKWrm35AfkJBXZ9QFfheY AiTXm7gOsGd0PF9lXwFLFO2hFsZKNF1MRCK5BSrVSaWcE4QckDKF4pDMZcn9zL24ikcUjnau HJDiWPlSA7uZm98CKvjWvPBvSiJ4KhknNW7+7e7lQvMUfLzSBoq3eM9t1fhFKEH6LvKwewnO NTfYu/FU+XrNewcWA/VWRhGF6ft+Szfmlx+gcfvPUJgiRqRxGKtPRYcoYcN7rdtTF+8qTEoB kFPY+gdwovQnukBIul9nhAUPWwbbF2PR005vXS+vdy7bt0OHbldZ7PHJytuyDoA1knNGafrz onQwnf9ZuODsV+2cXZTkWTj/A+AmPFahnE8rjMPL9mN7H9+jgmg23C5+iPNtlmm+nRnGQIAT hPZg8DhQepAeGN35Uio8DfYWlyB8fZBoH/2QltjutSefx6yg5TJHMejLPn0hj7JjojUTbYXc 7A1MUJnQKPiXkbjKvc4TzwfxMyuTbhHssWMkPwLhwSmi8JbYWIFgQS0efnNZ7Uo/3lrsEVAq FIC4bKH/5Ev0eOJOG0MWiGfY17+7G8t8mgMvZ5Iw/GkZKjp6OLUJUuQH/fagWqDuYwLSQdZC biwBukHuqHq1TjO5h4k9B+KP7SxGmrGBp56uwQoKWnNu2AxKHa9mg+RfuiblcnwRhe7vyzSf TXUAcazioFwFvwMGH88Hzf/TUMwgzASAJNiBAzTQu3Hp0VqzREW5iyzVCszmX4ytzVm/IZbI TlfiOu5fUKf/YvAMNMKikaPP+g8SH4C+tcQMSJkN+1rA74zi++QXtLlghFLo8VtbZeQOXt0A xVfsmZO3qGkY4UVfzCCE84hveJvN/RE6uapEiDefZ7cRRmbE9gN6uqb0OMhlLA8E8opPBIfr ofg0fIxdhY8yrdaGmVtB0wMJBLxtNDN86f0kcZ3I5iK9g8avzmvnuMvLNG/ifIPQ4H93pB9f u/meAEBJiegU0dobJOKJgKTDPnySdrGgEvuASW3V6LifB68TCXzRMu8tTTXCUrbwxRtYa/Hj FgfAslvusud4aEibX5NnmxEkNRjF8q6ePUvik9QIh4x0RrNN8s1vZXlVus8bcSuDNWnwKlki j+d7gKdAq6wSV2Nfq8aZPDr2pS/1fFcNU7f+r8w+gdJ90dYtFKvnT4exI3+FgglkedQ/dje6 rpBUPi+vZH1cdf05CPG/cg9y0It3Ak4PLI1ffDIym4qO7MkOpP1FWSayKWGoG5ok8C4nX2RS UTd58UVWRHxJR/TylLtRkgTE2Z1IJqTWjoDxlq7+z5sV1Cg0wmkni7KcqCruUIS92X/mmN4O codKJYSizwqiyXffrcTACBE20WcvVsV8TKBurC3l949RLhjVoqwTiZlz4Wo17LFPNb/HXdzA hveWio9a6rRvaLUDMD6uG6RsJf8niPjG3bGtuSzHxkf28i+QNjaJxDoA4pLvUkyE60MQU4U9 5Kbnf/MFSy5aLvIt3LCYbg4cBFU3DKMCi8G+1MLh17bZPvBfA3MdJzxMOjSUHedSD2Ytea8R qQbnoTkY8ehz0uvZA51vR8aCVy00rIYJmDfHXiDpfaEM1+uPhYvRr9HRLuwyGsD3a5rz0xD3 viHIZ90FMTQEfI1YKliZcNsMLE+uid81Am19L4k5JkY1MC5Y+d0ew4kB1wbmuDNBZcSw+8S3 MlO9hzx46JxalkbHVx+BojxdKgVhC1L3lB13bQRDt7GKwScMUIougg8JP5UOdLrcxJtK850T y+n8xR7cfZIL7seyMW6xbepvvrcNdkWT2S9LPTS8FZ8+wOdBqaf9wk2zZnqOdMFYNGWENWNP LeUQ08mXuts4VScKo1E8CLTPOVqcb3hj9wYrY+O3BEG+mzK57akj3uq+DL+wb3N0K4yiExA/ i/IcVo2VowpWgaWYCvXL6KYruODLTf7LXkD5X0GAhDrT7CuJevLh6E39Eia/01yo8w+QX5J/ h9V1MCoc3RLLqhT+KeDtvO9ZdrdqEwBXQz5Yl2qbOa60jDeDLjoyXDxGOd53Xql4Owl8NdMA DhcXZ5Zn7Ul23U2oKmF8VLpduJfSwIgdSGBlYnSzKrmag+yDEP3sTCQaKAx/NeZSu+cJBiai +ys/PrNGbocN1Q6EFuopEMabiadB48ftVTFqGXV9YryKfpxKhM6P2piBdwgYtYDwrdQdbyJT 39cDMq6DhvxHp7fSHh+SnCu0qrw7IHLy8dSl8+JwOJiIzmY5zmiJMpBbhvmH7Bkn3eTNUtc1 Qxu5QBzUC0NIBq9c0YcfXbNVuq2xHhlIIKSvGmLMm4t859p1+oOGnI7W1P5IBg9nuYWrw8Ik tZ+cePc0Z64dRtxqzNfN8/VPU0I0KZpH32AkKnWHxoN19py/nms+qa/ToHorqkosWYN69goz eNomtUGCxxvzNfsGj/Vk/nUt0UVJ8/hCkNh1YUvfSVHM20heoZWmMTzgqeOZc4NuOBUqr1HW MqMin35EtqpBZvR5/8y3Hm3CsNCgHtNacdVBNnaI4OfQPWjftL+qU/n930BXgDNFy1a+eOjG U/d6oeP+PDuq/anwj5vIaTzrGYTRZqN1bk86GjrYPESt3fNnM9+9w6yUTmpmq1hAXLywEs7o nQ0Lfcchw6Xpxw2XpORVNgp8rks5D9TFDa4sRafVhilcKnI8p3Z0UPVHXD8WrZH6LMARUplj lRwhXTqBFU7xXlu4RBBhnKhpOhj6zYDK0xjbFH7plL/Ks6K2tOLlUqmkvBQJOINPvIxaYHQo H8IASDK3KIc845nNqUaTcv8ygYAefuzvJtu+idWCkmzn+jwuZtkNewfdsiCrF6gIFR4LIF9Q +0Wnl5SanS5HfDhwHl+7HT3o1SL5jnhZI/7HCQWNGi/Ar+SG5PoxMdD55JHGx7f91m6GzsOs 5r2DWzqS+KUXYqmIQlPL8sHqS8R1rCFLXZAyULW+NwyvmcT4WsPE1BCPNo8tKNxQEuiIGMPm DIrmDbmYxlcC42yE4N3lnw85iJpGPVcsq5MxOWGTcgWiJ1BCj17XWT7BSQAo+kd1fkGq0LXX +8dGjVNcMntV08JFABJD4Rp9Map1cCPdbCwlceyfClQz7fbmCTb2ZzvSGOok5+Et6retdMUl 6xvSGAhjNMdP5SjBFra/GW8Mp1ZJ72jWKGlQoOJA6DrCdYtdu7AKpZbUQt8hqKae7n6HylpF fLbtd7V0Gu+LwjmrQmJmSCsZHQ2vTbeuR2HZLJbZs8WoNro9zXqJIiNHI5tvcTeELGsFRVss CfGpnbUnAGPib+aFgwBeKO9L8aa17Jm+29+x8fIrRo9Gs8DodNl6V41CwCCIJoh2ViltcLPu LNBePChSvib+hd7tmD1b1UKW52EVvJLPqD20lN2GA8ZTSvWNYTXGl8T2eKmg0O37+pK1P8Oj GIk98u3B7PqvjVLn9dtQFnRvkqMzfMHi5aFOry6RcevC9WCC9NXEJMlqE3xqFLqT+g2e6ana JDXAht98zxuOXcMTKrv9Di1P+RqfzRUsD0pFyAR0f84o/9eBFTNFbfPm3Sfn0ZjFo11OTC9k ZX7RnktXD/7T0YEs8oAjxyOl6sYoGA91TTTVmnjp6NywJYvVojhJA2U8rX5mhB0kOHH3Kx+K VKEoGk4gJ9wXddxsil/pycquS9YkVTipqw9E/LBlVZoDfybK9HIyQCkQhPvCyMmhSCmUcqWF /R5bTdUFyIVzh3wZ5uhRygqQJkhkHUTeVMjH1O9+QVjh2RCnTdXL5jgImmYjuDGevtq32Z/p hr8kr3sSsilwwYTMcTReW4qsYppd2i90TGvbOkLSnLZkl/HNSApWM6DVTC05M0FLKnQ+QTjz DKTlo6P9vJaMsGfI9ZeEXP8D2SanOaidZFFxXc8ykglGmSTzwUD3qaCyOncY8pvtcoW7b9TV YQ7HEPqRi0c9GGaPztDc98UqpmwyK9DniZvrFixJ9LmINsuugeYDzfxe6ZyYgVdClvVbbScn PLzT2LBYakfianDVrr1bO6QLz+CUCKD1jnus97Fto6w8dxOpdGIT8XkN9Jq1zVyBgvu4eElQ mmiEmI+qT9urslU7JkiyxO1T5u4I+RAcQ8bX5ZgemyJ4F9xaBFyhUmL9PaGCIOmFx9g29swS QSk34VD38vli46Kf6D9zIEZ7VI+anDuJWnQdIS/yXtRMrAERiK/NoNz8Ju3ppNK2eYHUXb67 dHzlALpczcjJmR15ZcTrzn4d+eaaf57/ZrK5o4qQnaSS36ly5BvocqvZAJkseurTPL5Ptfsx HNUVxe/1iC4f+cSw3wIR6h5/i7xnG6FcJqkyWe//hDS/E5AAAACF5XD+j/HtswAB+iSokAMA v738HbHEZ/sCAAAAAARZWg== --------------030402070507010503080404-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 15:57:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DE837DE4; Sun, 27 Jan 2013 15:57:56 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id CFE7C84A; Sun, 27 Jan 2013 15:57:55 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 371143592; Sun, 27 Jan 2013 16:57:47 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Subject: Re: ZFS + usb in trouble? Date: Sun, 27 Jan 2013 16:59:02 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <20130123134601.GB53514@garage.freebsd.pl> <845D0D19-7191-4EDD-8EDE-1331E13821CB@FreeBSD.org> In-Reply-To: <845D0D19-7191-4EDD-8EDE-1331E13821CB@FreeBSD.org> X-Face: ?p&W)c( =?iso-8859-1?q?+80hU=3B=27=7B=2E=245K+zq=7BoC6y=7C=0A=09/D=27an*6mw?=>j'f:eBsex\Gi, Cc: FreeBSD Current , Alexander Nedotsukov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 15:57:56 -0000 On Sunday 27 January 2013 13:52:20 Alexander Nedotsukov wrote: > Thank you, Pawel. > > Hans, can please you take a look at your commits done on Dec 20 (r244500 > and r244503)? They are seems to be the culprit. Hi, I don't have 10-current machine here right now, but I tried the following on a 9-stable machine: 9.1-STABLE FreeBSD 9.1-STABLE /usr/obj/usr/src/sys/GENERIC i386 1) Copy sys/dev/usb from 10-current to 9-stable. Keep "sys/dev/usb/usb_pf. [ch]" 2) Compiled new kernel. 3) Inserted three brand new and identical memory sticks: da1 da2 da3 zpool create tank raidz da1 da2 da3 OK cd /tank tar -xvf 10-current.tar zpool export tank PANIC 100% reproducible: After reboot: zpool import tank cannot import 'tank': pool is formatted using a newer ZFS version zpool import pool: tank id: 3524585230830777970 state: FAULTED status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-5E config: tank FAULTED corrupted data raidz1-0 ONLINE 11957153069341388916 UNAVAIL corrupted data 2594767990561096052 UNAVAIL corrupted data 2009858017158938805 UNAVAIL corrupted data Fatal trap 12: page fault while in kernel mode cpuid = 6; apic id = 16 fault virtual address = 0x54 fault code = supervisor read, page not present instruction pointer = 0x20:0xcd09c584 stack pointer = 0x28:0xf0ee8a60 frame pointer = 0x28:0xf0ee8a88 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 8049 (zpool) trap number = 12 panic: page fault cpuid = 6 KDB: stack backtrace: #0 0xc0afecef at kdb_backtrace+0x4f #1 0xc0acb56f at panic+0x16f #2 0xc0e33c03 at trap_fatal+0x323 #3 0xc0e33d08 at trap_pfault+0xf8 #4 0xc0e34c8a at trap+0x46a #5 0xc0e1e22c at calltrap+0x6 #6 0xcd0bcc17 at vdev_metaslab_fini+0x57 #7 0xcd0bd654 at vdev_free+0x64 #8 0xcd0bd62f at vdev_free+0x3f #9 0xcd0a3b92 at spa_unload+0xb2 #10 0xcd0a74ab at spa_export_common+0x13b #11 0xcd0f704d at zfs_ioc_pool_export+0x3d #12 0xcd0f75ad at zfsdev_ioctl+0xcd #13 0xc09ae0ea at devfs_ioctl_f+0x10a #14 0xc0b10360 at kern_ioctl+0x2a0 #15 0xc0b104d4 at sys_ioctl+0x134 #16 0xc0e3437a at syscall+0x34a #17 0xc0e1e291 at Xint0x80_syscall+0x21 Uptime: 13m19s Physical memory: 3519 MB Dumping 351 MB: 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 #0 doadump (textdump=1) at pcpu.h:249 249 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=1) at pcpu.h:249 #1 0xc0acb2b5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #2 0xc0acb5b2 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:636 #3 0xc0e33c03 in trap_fatal (frame=0xf0ee8a20, eva=84) at /usr/src/sys/i386/i386/trap.c:1043 #4 0xc0e33d08 in trap_pfault (frame=0xf0ee8a20, usermode=0, eva=84) at /usr/src/sys/i386/i386/trap.c:895 #5 0xc0e34c8a in trap (frame=0xf0ee8a20) at /usr/src/sys/i386/i386/trap.c:555 #6 0xc0e1e22c in calltrap () at /usr/src/sys/i386/i386/exception.s:169 #7 0xcd09c584 in metaslab_fini (msp=0xcd680000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c:760 #8 0xcd0bcc17 in vdev_metaslab_fini (vd=0xcb685000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:898 #9 0xcd0bd654 in vdev_free (vd=0xcb685000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:596 #10 0xcd0bd62f in vdev_free (vd=0xcb685800) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev.c:587 #11 0xcd0a3b92 in spa_unload (spa=0xcb64d000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:1193 #12 0xcd0a74ab in spa_export_common (pool=Variable "pool" is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:4312 #13 0xcd0f704d in zfs_ioc_pool_export (zc=0xcd728000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:1328 #14 0xcd0f75ad in zfsdev_ioctl (dev=0xcb5bb500, cmd=3583531523, addr=0xcd728000 "tank", flag=0, td=0xcb7ad2f0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_ioctl.c:5248 #15 0xc09ae0ea in devfs_ioctl_f (fp=0xcdaf01f8, com=3583531523, data=0xcd728000, cred=0xcd64a400, td=0xcb7ad2f0) at /usr/src/sys/fs/devfs/devfs_vnops.c:757 #16 0xc0b10360 in kern_ioctl (td=0xcb7ad2f0, fd=3, com=3583531523, data=0xcd728000 "tank") at file.h:311 #17 0xc0b104d4 in sys_ioctl (td=0xcb7ad2f0, uap=0xf0ee8ccc) at /usr/src/sys/kern/sys_generic.c:692 #18 0xc0e3437a in syscall (frame=0xf0ee8d08) at subr_syscall.c:135 #19 0xc0e1e291 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:267 #20 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:13:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 940A1541; Sun, 27 Jan 2013 16:13:56 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.c2i.net [212.247.155.2]) by mx1.freebsd.org (Postfix) with ESMTP id A1134914; Sun, 27 Jan 2013 16:13:55 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe09.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 198132737; Sun, 27 Jan 2013 17:13:47 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Subject: Re: ZFS + usb in trouble? Date: Sun, 27 Jan 2013 17:15:02 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <845D0D19-7191-4EDD-8EDE-1331E13821CB@FreeBSD.org> <201301271659.02164.hselasky@c2i.net> In-Reply-To: <201301271659.02164.hselasky@c2i.net> X-Face: ?p&W)c( =?iso-8859-1?q?+80hU=3B=27=7B=2E=245K+zq=7BoC6y=7C=0A=09/D=27an*6mw?=>j'f:eBsex\Gi, Cc: FreeBSD Current , Alexander Nedotsukov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:13:56 -0000 On Sunday 27 January 2013 16:59:02 Hans Petter Selasky wrote: > I don't have 10-current machine here right now, but I tried the following > on a 9-stable machine: BTW: 9-stable does not have the patches you wanted me to look at. Is this issue reproducible in stock 9-stable at your side or 9-stable + USB from 10- current except usb_pf.[ch] ? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:15:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EDB1972C for ; Sun, 27 Jan 2013 16:15:02 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 56972943 for ; Sun, 27 Jan 2013 16:15:02 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0RGEthp001992 for ; Sun, 27 Jan 2013 11:15:00 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <5105527F.3010708@m5p.com> Date: Sun, 27 Jan 2013 11:14:55 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: ulpt can't attach Lexmark E120 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 27 Jan 2013 11:15:01 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:15:03 -0000 System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) By comparison, this Lexmark E120 printer attaches and prints with no difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: ugen0.5: at usbus0 ulpt1: on usbus0 device_attach: ulpt1 attach returned 12 Also, an HP CM1015 attaches without a problem. What should I try next? -- George Mitchell From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:19:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 401B099B for ; Sun, 27 Jan 2013 16:19: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 C5C5197F for ; Sun, 27 Jan 2013 16:19:30 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 372787670; Sun, 27 Jan 2013 17:19:22 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: ulpt can't attach Lexmark E120 Date: Sun, 27 Jan 2013 17:20:37 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <5105527F.3010708@m5p.com> In-Reply-To: <5105527F.3010708@m5p.com> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: George Mitchell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:19:31 -0000 On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > > By comparison, this Lexmark E120 printer attaches and prints with no > difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > > ugen0.5: at usbus0 > ulpt1: addr 5> on usbus0 > device_attach: ulpt1 attach returned 12 > > Also, an HP CM1015 attaches without a problem. What should I try next? > -- George Mitchell Hi, Can you make a trace using usbdump for both cases? Also output from usbconfig is relevant. --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:26:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 04948CCE; Sun, 27 Jan 2013 16:26:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.c2i.net [212.247.154.98]) by mx1.freebsd.org (Postfix) with ESMTP id 03F3F9CA; Sun, 27 Jan 2013 16:26:36 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe04.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 370714901; Sun, 27 Jan 2013 17:26:28 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Subject: Re: ZFS + usb in trouble? Date: Sun, 27 Jan 2013 17:27:43 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <201301271659.02164.hselasky@c2i.net> <201301271715.02607.hselasky@c2i.net> In-Reply-To: <201301271715.02607.hselasky@c2i.net> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: FreeBSD Current , Alexander Nedotsukov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:26:38 -0000 On Sunday 27 January 2013 17:15:02 Hans Petter Selasky wrote: > On Sunday 27 January 2013 16:59:02 Hans Petter Selasky wrote: > > I don't have 10-current machine here right now, but I tried the following > > > on a 9-stable machine: > BTW: 9-stable does not have the patches you wanted me to look at. Is this > issue reproducible in stock 9-stable at your side or 9-stable + USB from > 10- current except usb_pf.[ch] ? > > --HPS Over here 9-stable (r245943) w/o those patches mentioned, gives exactly the same result as with those patches mentioned, except the kernel doesn't panic. Repeating the test: zpool export tank zpool import pool: tank id: 12201072322026523554 state: FAULTED status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-5E config: tank FAULTED corrupted data raidz1-0 ONLINE 5285896356596891701 UNAVAIL corrupted data 16930095547201732694 UNAVAIL corrupted data 14565039855173467224 UNAVAIL corrupted data --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:32:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 76BF1F0A for ; Sun, 27 Jan 2013 16:32:03 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id ED0DB9F8 for ; Sun, 27 Jan 2013 16:32:02 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 371149966; Sun, 27 Jan 2013 17:31:59 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: ulpt can't attach Lexmark E120 Date: Sun, 27 Jan 2013 17:33:14 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <5105527F.3010708@m5p.com> In-Reply-To: <5105527F.3010708@m5p.com> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: George Mitchell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:32:03 -0000 On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > > By comparison, this Lexmark E120 printer attaches and prints with no > difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > > ugen0.5: at usbus0 > ulpt1: addr 5> on usbus0 > device_attach: ulpt1 attach returned 12 > > Also, an HP CM1015 attaches without a problem. What should I try next? Also try to set: sysctl hw.usb.ulpt.debug=15 before attaching. Also try to attach one printer alone. --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:46:22 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 14A6C40A for ; Sun, 27 Jan 2013 16:46:22 +0000 (UTC) (envelope-from oliver.pntr@gmail.com) Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by mx1.freebsd.org (Postfix) with ESMTP id CCF49A9D for ; Sun, 27 Jan 2013 16:46:21 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id l13so346369oag.19 for ; Sun, 27 Jan 2013 08:46:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=+459inxhY/mEvQYh6/KF5QmXqoTKyyzl62PEEQNx2Gc=; b=M7zlVifFW+5RGS6GD5YWuhIpfLv8yTBwxdDk221P8XBOVAr7xL1vWA4J7Jg9ZxBCEq oGRxtQqRRfACF4bG+t8F2eNOx50nAPNLq0NBSzfDXCHnYmi1i6R2UknrAxv3beOwZc7U 23N9/XqsfuGumAAzdF9RdtesGGYp50nqwa+7H7h5B0x9pcGNFk/ZbFKwURPvMqWMR6rY RnRkAI+u6TzveR1pCtt1AyOll/DYTh3M61e0t3aUlsoFqqVK1y/ctEbikB99SY5fTvIO qFvE1thQk6klPIgs3d7VhUDgiae0r+B1gPd+h4b5DyolQtJmLGY8WR9NFP+Hq1yNQClf DPhw== MIME-Version: 1.0 X-Received: by 10.60.25.138 with SMTP id c10mr2122555oeg.12.1359305181146; Sun, 27 Jan 2013 08:46:21 -0800 (PST) Received: by 10.182.49.202 with HTTP; Sun, 27 Jan 2013 08:46:21 -0800 (PST) Date: Sun, 27 Jan 2013 17:46:21 +0100 Message-ID: Subject: svn2git exporter is down on git-beta.freebsd.org? From: Oliver Pinter To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:46:22 -0000 Hi All! The svn2git exporter is down on git-beta.freebsd.org? The last update was 2013.jan.15. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:19:37 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 277F1A99 for ; Sun, 27 Jan 2013 16:19:37 +0000 (UTC) (envelope-from g_patrickb@yahoo.com) Received: from nm8.bullet.mail.bf1.yahoo.com (nm8.bullet.mail.bf1.yahoo.com [98.139.212.167]) by mx1.freebsd.org (Postfix) with SMTP id AFB5F985 for ; Sun, 27 Jan 2013 16:19:36 +0000 (UTC) Received: from [98.139.212.152] by nm8.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jan 2013 16:19:30 -0000 Received: from [98.139.212.197] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 27 Jan 2013 16:19:30 -0000 Received: from [127.0.0.1] by omp1006.mail.bf1.yahoo.com with NNFMP; 27 Jan 2013 16:19:30 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 361769.98790.bm@omp1006.mail.bf1.yahoo.com Received: (qmail 66773 invoked by uid 60001); 27 Jan 2013 16:19:30 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1359303570; bh=SL8SYsX8/Zt4JA0aXkmFC1w5Uy0QBwZlKTi66cpFr44=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=3sfC1YoQouzTiV7VLkm9zWKmrYywIq0kYRDP70ODDCxOEiVhSoejTGD5yhaXuxLVb3T0BbzcqhYOnxEoleZ9lVD11tkIVxZsOCTck2S+I9n0pr4217EvI9BelacJS5krpUrQ+oaggQ7ybokmvym6TQlZgRjxSASZRTQUvAtUigA= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=uQsBQ4UxZboJp/tgsEtposFViq8OV3Pv0vJOBXyoTFuRYBxkwpTqssZfIzKTKVAZexLQcrCq/PJ99TV1mdvue43kdlRiJExAwmkFrcXt67gLLT7NPpePAvDMtFsVTrSG2/Ll1AHocTS4S6UfHQxgM6fbKj63ZmwhgUIpI8K02S8=; X-YMail-OSG: CpEtqoMVM1muS7M3bocVEiE2mYsEsyh5NMsQOLNraAoSWE0 _VqhiNc12wsEQGQccO6AEUBoHVcJO_hYtxJwBy.XDlJ7hl1Cey.j7B1M.xEp xVd4RbQuAhjjy.yyy71XstfAleT7PAUDDegwQurdwoYl7t_EjThSuvX0EQkV XTiWO9vcW.KbDytI42UzUF.H6B1AXeItJtD_Snf3dRrCN6uyze6GrtMS94_h e_9TnVDzmi.0zRQpyaXF5sOlHB7kCdAAjerh8IQWA3.LENAXTXG5A8LAgCnw OzToiIceUf0Tsr.BPr5itW1LmnWJwfoL5DIGCYOZRkhqnzUPIrsHlexwT3A0 79PcQoq1YrKiTh_5LLPZ7TXkPlKNJksiOsH_Gafh.B.WjVme6t.pQFNlGJpa mNvuV1wbk53VBw46Tiye.zUNz8hnJR1A3i_EHh3pTeFN39DqQUY339GAFPZI EAJP4xDMwsLcmCoVGlON6JImEiZBE3ZSyU.zFsyuH4ixoRVfngtQLPpw1 Received: from [174.78.68.94] by web162902.mail.bf1.yahoo.com via HTTP; Sun, 27 Jan 2013 08:19:30 PST X-Rocket-MIMEInfo: 001.001, UmVjZW50bHkgSSBwdXJjaGFzZWQgYW4gSFAgcDItMTMzNCB3aXRoIGFuIEluZXRsIENvcmUgaTMgYW5kIDZHQiBvciBSQU0uwqAgTXkgc29sZSByZWFzb24gZm9yIHB1cmNoYXNpbmcgaXQgaXMgdG8gdXNlIHZpcnR1YWxpemF0aW9uIHdoaWNoIG5lZWRzIFZULXggYW5kIEVQVCB3aGljaCB0aGUgaTMgaGFzLsKgIEhvd2V2ZXIsIG15IGluc3RhbGxhdGlvbnMgb2YgRnJlZUJTRCA5LjAtUkVMRUFTRS1hbWQ2NCwgRnJlZUJTRCA5LjEtUkVMRUFTRS1hbWQ2NCwgRnJlZWVCU0QgMTAtQ1VSUkVOVC1hbWQ2NCAoMiABMAEBAQE- X-Mailer: YahooMailWebService/0.8.130.494 Message-ID: <1359303570.66711.YahooMailNeo@web162902.mail.bf1.yahoo.com> Date: Sun, 27 Jan 2013 08:19:30 -0800 (PST) From: G B Subject: HP p2-1334 To: "current@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 27 Jan 2013 16:46:41 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: G B List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:19:37 -0000 Recently I purchased an HP p2-1334 with an Inetl Core i3 and 6GB or RAM.=A0= My sole reason for purchasing it is to use virtualization which needs VT-x= and EPT which the i3 has.=A0 However, my installations of FreeBSD 9.0-RELE= ASE-amd64, FreeBSD 9.1-RELEASE-amd64, FreeeBSD 10-CURRENT-amd64 (2 snapshot= s; r245673 was one), and also an attempt with FreeBSD 9.0-RELEASE-i386 all = fail to boot.=0A=0AWhat happens after a successful installation is it tries= to PXE boot and then fails to find a bootable disk.=A0 However, OpenBSD 5.= 2-i386/amd64, NetBSD 6.0-amd64, and OpenIndiana 151a7 all succesfully insta= ll and subsequently boot.=A0 =0A=0AI tried multiple drives with FreeBSD and= they all try a PXE boot and then fail to find a bootable drive.=A0 But eac= h of the OpenBSD/NetBSD/OpenIndiana installs/boot work on each of the drive= s tried with FreeBSD. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 16:52:15 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C1D66921 for ; Sun, 27 Jan 2013 16:52:15 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 806AAAE8 for ; Sun, 27 Jan 2013 16:52:15 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from wanderer.tachypleus.net (adsl-76-208-68-53.dsl.mdsnwi.sbcglobal.net [76.208.68.53]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0MHA00KXXMV08S10@smtpauth2.wiscmail.wisc.edu> for current@freebsd.org; Sun, 27 Jan 2013 10:52:15 -0600 (CST) X-Spam-PmxInfo: Server=avs-2, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.1.27.163317, SenderIP=76.208.68.53 X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.208.68.53 X-Wisc-Sender: whitehorn@wisc.edu Message-id: <51055B3C.2030603@freebsd.org> Date: Sun, 27 Jan 2013 10:52:12 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 To: G B Subject: Re: HP p2-1334 References: <1359303570.66711.YahooMailNeo@web162902.mail.bf1.yahoo.com> In-reply-to: <1359303570.66711.YahooMailNeo@web162902.mail.bf1.yahoo.com> Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:52:15 -0000 On 01/27/13 10:19, G B wrote: > Recently I purchased an HP p2-1334 with an Inetl Core i3 and 6GB or > RAM. My sole reason for purchasing it is to use virtualization which > needs VT-x and EPT which the i3 has. However, my installations of > FreeBSD 9.0-RELEASE-amd64, FreeBSD 9.1-RELEASE-amd64, FreeeBSD > 10-CURRENT-amd64 (2 snapshots; r245673 was one), and also an attempt > with FreeBSD 9.0-RELEASE-i386 all fail to boot. > > What happens after a successful installation is it tries to PXE boot > and then fails to find a bootable disk. However, OpenBSD > 5.2-i386/amd64, NetBSD 6.0-amd64, and OpenIndiana 151a7 all > succesfully install and subsequently boot. > > I tried multiple drives with FreeBSD and they all try a PXE boot and > then fail to find a bootable drive. But each of the > OpenBSD/NetBSD/OpenIndiana installs/boot work on each of the drives > tried with FreeBSD. _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > The default partitioning type in FreeBSD 9+ is GPT, which provides a number of benefits including the ability to use disks larger than 2 TB. Some very new machines, however, have broken BIOSes that assume GPT == EFI and won't do BIOS-type boots from GPT disks. If you choose "Manual" partitioning in the installer and choose either MBR or BSD for the partition type (press delete on the disk first to erase existing partitioning), does the problem go away? -Nathan From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 17:40:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 05CB512B; Sun, 27 Jan 2013 17:40:43 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id DC5DAD8A; Sun, 27 Jan 2013 17:40:42 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id r0RHef4i029263; Sun, 27 Jan 2013 17:40:41 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id rpkpfnucv3izkke8425x66c5ms; Sun, 27 Jan 2013 17:40:41 +0000 (UTC) (envelope-from tim@kientzle.com) Subject: Re: devel/gobject-introspection failure on ARM Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-1 From: Tim Kientzle In-Reply-To: <51054E5F.9040309@m5p.com> Date: Sun, 27 Jan 2013 09:40:38 -0800 Content-Transfer-Encoding: 7bit Message-Id: References: <51054E5F.9040309@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.1283) Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:40:43 -0000 On Jan 27, 2013, at 7:57 AM, George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > ports: svnversion 308518 > > Build dies with message "sizeof(ArrayTypeBlob) is expected to be 8 but > is 12." (Complete build log attached.) I made a naive attempt to fix > it by rearranging the order of the structure members, but obviously I > don't understand structure packing on the ARM and it didn't help. The easiest way to hack around this is usually to sprinkle "packed" decorators on a lot of structure definitions. > It also didn't get rid of the huge number of "cast increases required > alignment of target type" warnings. How troublesome these are depends on the processor. I think the ARMv6 on the RaspberryPi is late enough to support misaligned accesses. It's a big performance hit but better than crashing. > I note we're at version 0.10.8 of this package, but upstream is at > 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). > > What's the best way to proceed? Given the version numbers you quote, I expect that a newer glib would be a good start. Good luck, Tim From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 17:48:15 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2E2245DE; Sun, 27 Jan 2013 17:48:15 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id BADABDEC; Sun, 27 Jan 2013 17:48:14 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id k19so974058qcs.27 for ; Sun, 27 Jan 2013 09:48:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6v52IKgURdHOGFH/H3cE+SRGm61ElUzn+hnS/Bd99K0=; b=f6mtdJy2oAWy7KjpsLW9yTzvl1T08rfh0aOOBdIAgIixgZv6Ew8aUeJVlmqe8qO+g/ +jPvETixz/rlPz3hKdGMGPAf9/G8H+r1Uxn/4oJyiIl1fFt0dqmhu0kpGxIZIZxvLro2 GTYwU4bFPryEgdTyQr8bfDmnaDqe6JM8l0fjTV/4jD+1MS4K0GKxyTr1hnJsJjPJ2htS u0xKNCOjw869TJ1MoKMjnzhUG082O/CTMtkl7NuOaIbiVrDvyPKeGS6GvHf7ms+bXXYA XEp+RM8HRGT6VXkOL2eWRl/SxG4kjxzjmpdTLFBU/mkR+ySuvOi6z1Qe9QITa/koqw9w k8mQ== MIME-Version: 1.0 X-Received: by 10.224.200.6 with SMTP id eu6mr12744613qab.62.1359308894035; Sun, 27 Jan 2013 09:48:14 -0800 (PST) Received: by 10.49.72.138 with HTTP; Sun, 27 Jan 2013 09:48:13 -0800 (PST) In-Reply-To: References: Date: Sun, 27 Jan 2013 12:48:13 -0500 Message-ID: Subject: Re: svn2git exporter is down on git-beta.freebsd.org? From: Ryan Stone To: Oliver Pinter , =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:48:15 -0000 On Sun, Jan 27, 2013 at 11:46 AM, Oliver Pinter wrote: > Hi All! > > The svn2git exporter is down on git-beta.freebsd.org? The last update > was 2013.jan.15. > The mirror on GitHub is still getting updates: https://github.com/freebsd/freebsd The git beta was supposed to be re-rolled on the 15th. GitHub clearly got the update, but git-beta.freebsd.org didn't. Perhaps uqs@ forgot to do a force push? From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:04:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E9529BBD; Sun, 27 Jan 2013 18:04:35 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id 27F9BE7B; Sun, 27 Jan 2013 18:04:34 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 204949930; Sun, 27 Jan 2013 19:04:26 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: ZFS + usb in trouble? [PATCHED] Date: Sun, 27 Jan 2013 19:05:41 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <201301271715.02607.hselasky@c2i.net> <201301271727.43074.hselasky@c2i.net> In-Reply-To: <201301271727.43074.hselasky@c2i.net> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: Alexander Nedotsukov , freebsd-usb@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:04:36 -0000 Hi, Can you try this patch: http://svnweb.freebsd.org/changeset/base/245995 It fixes the issue for me. Looks like I overlooked a corner case computing the DMA addresses. Thanks for reporting! zpool status pool: tank state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 errors: No known data errors --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:11:46 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6D932DF3; Sun, 27 Jan 2013 18:11:46 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB38ED3; Sun, 27 Jan 2013 18:11:46 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0RIBjOO031679; Sun, 27 Jan 2013 11:11:45 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0RIBgqW019718; Sun, 27 Jan 2013 11:11:42 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Trouble with recent auto-tuning changes From: Ian Lepore To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Jan 2013 11:11:42 -0700 Message-ID: <1359310302.93359.48.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:11:46 -0000 I ran into a panic while attempting to un-tar a large file on a DreamPlug (arm-based system) running -current. The source and dest of the un-tar is the root filesystem on sdcard, and I get this: panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated Just before the panic I see the tar process get hung in a "nokva" wait. 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. In r245575 the init order for mbuf limits was changed from SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the results of sizing kernel memory. Unfortunately, the process of sizing kernel memory relies on the mbuf limits; in kmeminit(): vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; Since r245575, nmbclusters is zero when this line of code runs. If I manually plugin "32768" (the number tunable_mbinit() comes up with for this platform) in that line, the panic stops happening. So we've got two problems here... one is the circular dependency in calculating the mbuf limits. The other is the fact that some non-trivial amount of kernel memory we're allowing for mbufs is actually being used for other things. That is, if my system was actually using all the mbufs that tunable_mbinit() allowed for, then this panic while untarring a huge file would still have happened. I arrive at the latter conclusion based on the fact that this panic happens even if no network interfaces (other than lo0) are configured. That is, nmbclusters == 0 is a reasonable approximation of my need for network mbufs. So something in the system needs to be taken into account when sizing kernel memory to allow for whatever it is about untarring a huge file that eats kernel memory (buffer cache?). I can easily reproduce this if you need me to gather any specific info. -- Ian From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:14:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E5DE8F19 for ; Sun, 27 Jan 2013 18:14:35 +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 835DAEF4 for ; Sun, 27 Jan 2013 18:14:34 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 372808687; Sun, 27 Jan 2013 19:14:33 +0100 From: Hans Petter Selasky To: George Mitchell Subject: Re: ulpt can't attach Lexmark E120 Date: Sun, 27 Jan 2013 19:15:47 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <5105527F.3010708@m5p.com> <201301271733.14312.hselasky@c2i.net> <51056CAC.9070105@m5p.com> In-Reply-To: <51056CAC.9070105@m5p.com> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:14:36 -0000 On Sunday 27 January 2013 19:06:36 George Mitchell wrote: > On 01/27/13 11:33, Hans Petter Selasky wrote: > > On Sunday 27 January 2013 17:14:55 George Mitchell wrote: > >> System: Raspberry Pi > >> uname: r245840M (Alie Tan's image from 25 January) > >> > >> By comparison, this Lexmark E120 printer attaches and prints with no > >> difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: > >> > >> ugen0.5: at usbus0 > >> ulpt1: >> addr 5> on usbus0 > >> device_attach: ulpt1 attach returned 12 > >> > >> Also, an HP CM1015 attaches without a problem. What should I try next? > > > > Also try to set: > > > > sysctl hw.usb.ulpt.debug=15 > > It's a non-debug build of ulpt, so that doesn't exist: > sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory > > > before attaching. > > > > Also try to attach one printer alone. > > > > --HPS > > After unplugging the HP: > > root@pi:/home/george # usbconfig > ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=SAVE > ugen0.2: at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=SAVE > ugen0.3: at usbus0, cfg=0 md=HOST > spd=HIGH (480Mbps) pwr=ON > ugen0.4: at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON > > I attached the usbdump output, though there seem to be quite a few > packets not connected with ulpt burying the interesting packets in > the noise. -- George Hi, I don't see any errors in the usbdump trace you sent. So we can at least rule that out. Hint: You can filter traffic using the -f option for usbdump. What does: usbconfig dump_device_desc dump_curr_config_desc output? Can you also get same output from working system? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:15:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C500FC9 for ; Sun, 27 Jan 2013 18:15:46 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id E2604F0E for ; Sun, 27 Jan 2013 18:15:45 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0RIFZPO003282; Sun, 27 Jan 2013 13:15:40 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <51056EC7.7090100@m5p.com> Date: Sun, 27 Jan 2013 13:15:35 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ulpt can't attach Lexmark E120 References: <5105527F.3010708@m5p.com> <201301271733.14312.hselasky@c2i.net> In-Reply-To: <201301271733.14312.hselasky@c2i.net> Content-Type: multipart/mixed; boundary="------------060302000506080603040905" X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 27 Jan 2013 13:15:40 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:15:46 -0000 This is a multi-part message in MIME format. --------------060302000506080603040905 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 01/27/13 11:33, Hans Petter Selasky wrote: > On Sunday 27 January 2013 17:14:55 George Mitchell wrote: >> System: Raspberry Pi >> uname: r245840M (Alie Tan's image from 25 January) >> >> By comparison, this Lexmark E120 printer attaches and prints with no >> difficulty on FreeBSD-9.1-RELEASE, but on CURRENT, it says: >> >> ugen0.5: at usbus0 >> ulpt1: > addr 5> on usbus0 >> device_attach: ulpt1 attach returned 12 >> >> Also, an HP CM1015 attaches without a problem. What should I try next? > > Also try to set: > > sysctl hw.usb.ulpt.debug=15 It's a non-debug build of ulpt, so that doesn't exist: sysctl: unknown oid 'hw.usb.ulpt.debug': No such file or directory > > before attaching. > > Also try to attach one printer alone. > > --HPS > After unplugging the HP: root@pi:/home/george # usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON I attached the usbdump output, though there seem to be quite a few packets not connected with ulpt burying the interesting packets in the noise. -- George --------------060302000506080603040905 Content-Type: application/octet-stream; name="ulpt.usbdump.xz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ulpt.usbdump.xz" /Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj45c3FlpdAAcAELPnThBU48PXVAEesZWhbcNiWrGo vg3xpH8aTWP71UO5H3XtUh94PCbyhZMD4pJf8SaHFcCFF+DhzlSQxALFQ3C3Qxly0L3jfYUn qcuHPIApkklO02AdxZjkQDhfDxqhbgNojsNhcUasp1RAcWuIh5NemIjHXPNO9fES66jBk6ZF scpTx1RRXwih6FQapSQepU64pZaoJHYQj67aZQDD5rZmexEddrurGe831i8hRoJaDL4j1N47 tksBiHkJzAN4qbFF/lc2IKZWim3L4KGLJQmHiq97ttJs+Bwb6qsADIL9PK8ah8lgGgKWvukS v5PgyhPr+d6/sdi9cgFMOJ/J6uRA45kdGGwPp9DMNacb1eR+gOl2TI2wwznwj7bbQJeLXlq+ EpPre2NJa48mQZ3R9zNp7MLm6+qsKNnqAWos5sh4T2442+s/0Shr5BmFu57ZSs0KdGQJg3sE GfgFvqEgAz3mNryIvtfHkv8MBeZ06sHEKQixuV5MdghkLQZdjaLpGt5pSlZp3gYxYRdWEv2D CGIGVucSJbBiabz/MkNFGyosJzEy0fsEuQNSMVSzb+t5cZjjJjdBv3EGpUEDhRvoZrhi4L8J 1VlenwnYe8uz5Fvsy56ecKX4yUebv+mdDzwbt55iGdbgIOwQhVVfOWnrC2rVbi2/Pt0geu1w csaMYeem1bKjDWCrVRwhWuwbjrMV2izucEXjaG2Tf6jL7fK/XIhly8lA8egP/GG6/zeTQG93 t9m26kwaoIJ5cQzFwFyC+UyGtxDOempHagnCqUKSJTIP7JbIOrLeX6URgezdDK3hW6SVVGI+ FTQe+f4fUJaLwOziZ+0wOlWNqPZhCJ1PnYOU0vFa7/5h6SSHxvXaVXZmGDFo5415dNwg5yle ySiNIIbWYjTloVHhimf2PTLT2rCA1w8J4iSYcgk+S+XlOQFem9/fST8S85B8sj/OR5Y/yxXu p2PGw9Dtm3W1tbbgmJ/aLPnabSkL3TWSUyuRqGEz0ZwJ7OE4/H9w96SlCIVkrlqI64Qe7sTT 4EHjPTCitLraSrUnCTRSv6d4KcEnE6XzPpnw1JwN4s0whH8c5VA2BVgSc6UIMizbzu1zwA19 bKzmWC1Fsol9HxBgb6FYJ8b2qd7KlA5IrOQyND8Fclz9cRmV/5hzRMQKsHGmrhQ4BC7nuHJB SY/EUdwnmdBzkwlDHLRqQX5R7p61jtOrFUGy+v2JHcQnDfrI6Zx2mof78EGiQgezw6RGS8Mm ZU0I5pYI1Rwjl7pUFjMDis3P5ArTIKoJzfxTE4SFNEE0+9z6RaB0BD41hL0vZmviKwZE5pFF MK7Cagi64zg/I/7S+Q2fB51XkV6+jpXy9yA9j2kZMjYYAw4nz4S68OdxMa8AN1QMouKNQv69 fc1hZc12kBA6cF26vB+tx9DB/H+4Ha3k06iiM7Nsaka3cgNbpmtSZAtfh8wngeZ4buwjHFB/ 47cEo47zWNzgwA+4i7WBPa3g/wbvljYHXz7VY4YBubSmHgBqaRrBQXjWQKSznSVwhAFUjGXD TdhGohaomG8wrOJhK+mpgraVuRLqc/0EtYGXLSBhkBVQxXtJ1AkjEGE92QrU5rGg89WNwcOq IT7rh0dTpKQ9AeUf3sLydbhBkKm8wYqihmXhtmIpy+01kgMcxl95/WlzzlwRYYrxILrcshPq APsyJNJxSAvzd77oBIz9/Q1PjV6OYooIaI2zh/QKER2NrItbOwaen8WoQOH6it3BZfPYseXM 5t+IQ2c2lBFB2lXdZVbqzCDco0glKsO39N3LVhqsTG1XymD1ZTxtB2x0WD3RM//AUwvVRJXG D3gP3xfwOSpuumtDgTjMobprGihs5SNNCu4aQlXnaGHEvOi5eU+CqceGJ8JX/jMjJSIaUmWj QRXX+OYA+wmjv5rrbm6N/np57DHFXiwN9NRdXmoV447TUzts2sgMG/e3E1//vvAAad1ROivI lJMESlSIq1q70VrJ/Uj7EIVl41NeanOCI418V150iPymyXcrP1sfif77CEbBAKDVAXi/PP/G lUkGp/DeRy63cn/u6Pwdx3govV338tEloI11BfsCHuqpuCGkIn7PFb/kHXBPQoROVIoFw9ED 3a10KhBUVOIOSbTqjzbehN6t+fOS76H2gctx282oeVZM+lgCDpiPBtvq6VZ3VuiJU5emXVwv ORq3/HApTp2bhIcAvaq4WUF+u+BWmv/RFcAplil7N1xQZEYfTm4t9EOqcUxvW65quAiwvmCy 5omcOnweb+SAAzp/jL/rVCaebf2tmJ3zS1X9vVIcpUgVGsDE31YMH3WWSwA31n1G9b6uAdUg jbrGCoO4btzqA8L6VuuSKkCh7ViO2Wxt9IO9DP8l1U0MCeXYY9yQ0bBeoTccyQx2s7Jp1540 EliH7jbw+OB0gZPC8GSYNdmbJPHLE9eMrnP22g52voSikJX4ed5SD5XSBGzKtToAVtddFP4a +E2K1pQM/S5ZXR74tngE9Jnc/tTpuHNbKmfBwJnAUaN0GG7CN9YvVXo2fg3JuwPakOLgLqR/ Me6xz5KQuoteSknli5SzsVqSAyFm/KA0uH4ziDgBVuPpemrRwdUToq/HKapHWxSWC78iHb0d B3rQVer9PoCymA7fD1FadejGeYgD4qmXCucvjjqc4ZopL1EDo4jBEowDOksnsgd0BvnQVh7a 1EiGT7yT+jqf01PKGclHXvzS5ZXH4b6jy4/zx5CmA6rO3zVEfcXqm2oACotEjiq/ev0inRjS WhmqQJl3VBb8ij1Z7NnCEqi4z4fEkjH7+/eA4QCAEDhSsWPvnnT8m0NcTtvt+lqege9OMSNx DwfzLYa5No+12x9TQSY2iGMLWlRLG6IDZMfUI9U7JfDLQxbyqgFp/XNtsZeQC4I2J6L3cMSp kHNwBi+yNjAM/Reaqm9r73dSPpmvneuS98xJ5i0waLhiqnOK2xFJzZUCHHPev3TM/21U2iWG Zj0coT6o/KbykVk2gkWrbfDtzDJallNc/UC/sL/0oXshEorw6AKfwkjJwSrYqKEuz6JLY22O B2FtpE5V8i/BndrY9+ko9f1G194IrhTc4fEAEhgRebNr7kriE8ifK9n6VuW1L+hgYHiavdMQ MfPozxdy9v9d7BZVdMJgb4lMRpFsUNFf8ul9lFUnOAzNGXWw+dzi+TOiDSysxUjhKufJVtJK 1PjNlLW8SW29ZG+hwoIhytrSOlkakUoIqo5qSK9AJcwQ+XwHpwYvBIhAU8+P32jUOgxBQQe9 BoS+jseA3vA8E7R3OHCGrUPj9DCNhlHouBmRyoAzvuVHdNJDK8bJnn2rkNgTlE/1jHenEQGk 0VwbJzuxWFKAL+RurVb5vyj3b2Dm1urM1uaDF5zQ1xDPBz4n+qTwoqmNPP/prU3B9kaqHVzx UEViENyTGP68RteFYsiuOKt2SrlAKfhYN2xY9Xrr5ftYNIukaBd2QkyHVZcBUVEZR8iEG18i tSAHxriqS+1LjDaecstfRxefucbZxFln3kTmeIoUnwBkYxIkeNq5RE2jIj7dV+K1fEus4m+3 D/cFoQZgO5+LqjroTw9tTmPNW/0PXZxLFmSHVQYDWI0C3cUF1tFYaOCB6RH81FxfsiJoz1YL tVYNR7c2toRdeWRV21W+xZuNj7HjebPBx/s0fGdBrEK38tRx1kRu+L5AxHuTXOjJi31+aiDe FWvD3MeTHLFsEF2uJG8RquI3lptGnl1bUYvbUEfTzf6CxrWtBwTkHuGvHfQTWf0URJ9cnns2 HjUizW/0MQa3xRK8BuE+oNu9bX4W9C2thgvdP9y35JpbLY9bWCuugRxaTjWmsLgpN7yXVENA txN+Rv7DZ3U3DlgX0DHT5rhaY4fgaB0yEJYY5ZLHxCb4j+BwPeE05+/uMD8vuec88iDVKh1x ldJuJrpBDk/KfWgmHBRcH0OEM9pX05wZKmim4WO7q//ensIKHcH6Wwfi8dONmAVH6+Ns8vwN /3zkYt/YJk7INkx7gDUDwEXqAtxapIEwVYOSfJETqoJkJcHkmg0OLzjlFqe/KyeXJY18A4SX 89EN+5bNAF2dINmmR6lAqYxfXlZwwtH+Z/zTpl62RHfqJrh6TWLxxaTUH4CbouF8T/l4bQwm Cp3pHQvaulRftUul/IQksp/jpo3Pnq4nFgmBEEHQuLtF53jr5ftDenBaXzoCQXJ+gkNu6JTg ksMcgc9VLVHcyEMTbtGFHhivLXDeZfH7gMew1ZpOiPtrDT32tIpcA1g5aNy9nivKmV/jIC/r a6fw89qltKYnCeRidXn8p2Sg/+uhhGjzny9Coq6nuoJ8+MglRkORAlarRzf9kIPmA4O1irX+ t1l1L7jFJbSqFvygSNuujrlgtNodcnoHQyC22EJVEuJ3ELVoaktYlH12wuLQo63/m7g+ynY/ ILvdvosRtG+GER4PLJJQn7hNNKmjKTXpcBwMGGCUgO6i+roJXVhFydvxM9kreHI2UoXf2hZ8 eH7lfsxrUBk5Ar48P/YhzltLKD1+vzdaKEP1y2seYhqIPqdOzhxykFiPbvvkgBgup/+EavgR 7aEdIA2qabRsNnNNMd2U4Z9cTIIrFyz6uAmQex7Ye1eqUKPr78E0j2QwXYCB6nLMkiAi4YCb uPw0IWjfyR7EGeahpynVoyz7rQfKbVRmz1b7iQg6SY9uixRfhL6ZPLoFDNvJReFGGX1s7d1+ PwTOq7qX/D6ncwrzYQ9FR41XnI6Q6peGpXigxNPMbwhsG1M7OYuFOHkeWfVpCrn7hoh6Rq2H t4p4sAj25pXKttGeG8d5ebivzgrfZNAM22AWXl+5v8Bl743p7SLaxn7zOuBU8xo8OTAuWDJ0 LWAXa9fZgzvHRxb3ieI8FVZRQlJ0keaRaW6jXxu34StC1WThRfp2C2p0lWc7OuHrtQURam/g zvffU35t2UXJlxXGGG6JKnAnja+0HsE+hnqXY/ibIXqY3/sNvI8uCX5uMSHTADKWewiBtwbz t4l7kyyRBm7H6dcm3ZqK+07Fko+juWMYbWKzGfGAgsVyVMpOYmioA9lmXFdAYtoAenwhbmlC bhCp3wsq4G6B/kGP+AZ1Fiukc4auk18WWYu8JKRmR34Z1HKF02/BZuSmt7sE1FT/34kKr7P9 5gmqkCuTfIRfxIohUZ5rAW1sUIEheu0F/VBQlu0VdOz0iPDVdMBxyHgMeflaZxcwtazUM9pH JNTMDBvjy8QDr4bgxoYZD+yiRpFPIv71Mz6oo/R36E5Plz2Abh4PkYesmM3a1r7XoxOuvSlj x4AwCbFhXzv45GHKKtJTnQk0AbZPSyOGK/aS7tPzD1Mm2hqBa43NETCoeQ11D6ZuNfGBc6k9 5ddsWNfaQ41aun8a/n+xMHhKj9PCholaTBLkXSJ3pPTe6MTPKBp1hR3rDKgvZf7o5rwjT4A/ iJxlE4pc7P/82WKF2dqgqSZc8wNui5N9R1hjzdQMQWC1i0EaF2ps5So7KY60q9SNqeqy79uH WbCHo2uhu1TBDg+/s9Ynsa9NpLgO9M50+zeT/G7W/EcOPkwK9vaZEvhg0uEtTVN/fT0erLxh E7E0mez+6eou5WoM/FsYB7KnosrzMXe039dRHkl7F8TgyfhsTHEubZVtrFEZYGS38NVp326g 5kgNMKV3BxxxXcHgC/EuFTtf1/q6LI71+l1CzdxKQzEA/VSrvTxDWmdKNRCoSOQsuIvEgrdC B4r0MqBFcnFZOGs49y6ACZcRJIxovsLduMZp+2QKvV64kNhuRH0c07+n9MXL6MhYIyLudXQy YncJdhLyVA3XtbAGBgcPCQwwePiVGeXMPaxETS0Ux/ph32oIRpr+9XmCxL4daXZTSAJfMVeJ 6Bbc370ti7wkfcEsw9MtMDEfXxWCfgHtnIwh2xrwZuMtcEDaCmiGWJVphPZEAHxeYKQyvp/7 MKbQrWioI0s0aE6rN9DiBpW8E4f3Mb/2SydRIt1bIlafmYOfyuMixoB63+SkYbJIzDYNgTZ0 G1NOXPOYQYR/qRDY2MkpF/+YftVQXFeQu23125eY6YFjKKfMZ67yj89nXwVSWaA/O5mZBYXz 5FA1l11gf36ibZuULlW049k5j1d7ulpMoBpf3O53NWbKWZWke1jvNqeJnjiLcjvamsMlqtMO CJahCtbGxziy9H+ebEptPwuEa2gxHlUfQHk6lZybWNJ59yUSKXwQ6qwsEKY7NPGAVZlr6knH Ye2ClotDc0qAlfK1llr02k1vLLRqLe1hbT6DokGerSYcWXJmIcYXfQ7ExCB5bwHSwjFMQtR4 BhBkmnWcQOZJhIRufIxU6jKP+6lPrqFBki1r1Tn0bVRmngdK0IAY3shmSM733qUlRPsP/515 PdENlrq3LWkQHWFvj7x2rwxVWr0YMUTZgB7XMjY7wRyW+x553FwiVoeopfRu9+YQ24Bky3tg b2U7zuYof0y9/7fkE6eRRUsScYaZd7mzK5bbDwpTrerRGqpNx/ooK7pe1Gg0S8qSQhrqPiqk 18BUwIcMl0jU4JaI7mCBs72vIf6idu6UoiT9+dmfIi6iBoxhmdIleIVAdtgXmDukoIVnzXQe uZjRAKavnPcBxtvkcPc6xZ6ZHcoBbBWxsEofyhvTtCLRu5PM5DlBEkvFHTg9T80x9TbNGMDw a4FMjJPAkIXdXJttdcL/uHO4JSzEDSJLBKk1bwXb7lO+mkNz9vI0524VEEMjQw1bwqj9d6dD U4olRVICWDv6VRz0lowB+6OxGMHGZerFAhZlQ70U6ydJbzEUKN90gb9kEnBeXo8JWNZ9HIS+ N4CpuzUQYeFpQoQ7/QQ2jJnodshe/bHr8mM4XeM6pmhBCubxX8sDMDEYpwk0aTfJWZEb43ft Nf8PaskZ5CysWdJFVB76i3N0qLfq+ToWzRWyBjTizl89DsMw1iv2ZVh8I5u4qzIvltgrbQ/W tCNo7cMed5dwYaKeYWOCUYLAk1M7YcRLlSaO56UsX3qMxr8u5F3tpF9mJLo9bYuC3QKdXcaF nAXi66HMqpTX9L7Uwug5xO3dDvt0K7lHlbtfKG0plyfLesitLMqYk+dA7uM7cGztzEMGFsoG 6XYs9tEQk4zLyydvqMMKTvDyYK174s/R8lqtvBbXOOAN5C1wYIDakQHkN2TttNfB8YYYPUtL FsnrbUh2vmb8LZsGQdFqZJwUPnlcmiUApNN2XzhJqBcneH9EghlqBRKWRNuw52FkOgJ+01JZ lulRiM/JitrYZ/2aOmfUU2q4D0P5kqqT2XdCexKF7ineIu+xK+ERxEQgbYH0Rq7F/j3O2/Vc fzAMD0uzLJy6rGpNwAWpqJ8TQRYaUHxzcQyuQ+/NUjNH5CDEUgsm6yKcIXM5r8F/yryPcO6F 5Ei6gpSvhyrrG1pPAG5SkFwjUZ+mh+vfXGCC1eGauAshVEOtMI8UDVfG2rPgssU60/xkSTNV 74/p7ENjCRe4IkIbL77Vhw54FbZCE7YZAAHsTepVSWgpJCLAlEJv4L7ai1luoMDzVyf0WeIh PTz3ctqhPhvFTVkDqGs8RR+CIglaZtMguXugEv8t2xi2KDs2T0WTuT0s+YRnyQvBRmZuNqcY Hpx1R/t/QsLxPXFD3vEsE1OtQYGRF/G2Vsn4ht0AAACGEYF1yb1bXgAB9iy4rg4ATdcMkbHE Z/sCAAAAAARZWg== --------------060302000506080603040905-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:24:14 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 70E32232 for ; Sun, 27 Jan 2013 18:24:14 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 86828F4B for ; Sun, 27 Jan 2013 18:24:13 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0RIO1aW003433; Sun, 27 Jan 2013 13:24:06 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <510570C1.1060607@m5p.com> Date: Sun, 27 Jan 2013 13:24:01 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ulpt can't attach Lexmark E120 References: <5105527F.3010708@m5p.com> <201301271733.14312.hselasky@c2i.net> <51056CAC.9070105@m5p.com> <201301271915.47712.hselasky@c2i.net> In-Reply-To: <201301271915.47712.hselasky@c2i.net> Content-Type: multipart/mixed; boundary="------------020801020001060700080805" X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 27 Jan 2013 13:24:07 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:24:14 -0000 This is a multi-part message in MIME format. --------------020801020001060700080805 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit On 01/27/13 13:15, Hans Petter Selasky wrote: > [...] > Hi, > > I don't see any errors in the usbdump trace you sent. So we can at least rule > that out. > > Hint: You can filter traffic using the -f option for usbdump. > > What does: > > usbconfig dump_device_desc dump_curr_config_desc > > output? Can you also get same output from working system? > > --HPS > Attachment 1 from Raspberry Pi. Attachment 2 from 9.1-RELEASE on amd64. -- George --------------020801020001060700080805 Content-Type: text/plain; charset=us-ascii; name="usbconfig.pi.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="usbconfig.pi.txt" [...] ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <9947W2Z> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 bmAttributes = 0x0002 wMaxPacketSize = 0x0020 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 --------------020801020001060700080805 Content-Type: text/plain; charset=us-ascii; name="usbconfig.amd64.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="usbconfig.amd64.txt" [...] ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0010 idVendor = 0x043d idProduct = 0x00cc bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <9947W2Z> bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0002 bInterfaceClass = 0x0007 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0088 bmAttributes = 0x0002 wMaxPacketSize = 0x0020 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 --------------020801020001060700080805-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 18:44:04 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ADC8F485; Sun, 27 Jan 2013 18:44:04 +0000 (UTC) (envelope-from prvs=1739a0aae4=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 17EA3FC1; Sun, 27 Jan 2013 18:44:03 +0000 (UTC) Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50001881137.msg; Sun, 27 Jan 2013 18:44:01 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 27 Jan 2013 18:44:01 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1739a0aae4=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <917933DB5C9A490D93A739058C2507A1@multiplay.co.uk> From: "Steven Hartland" To: "Vladislav Prodan" References: <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <70362.1359299605.3196836531757973504@ffe11.ukr.net> Subject: Re: AHCI timeout when using ZFS + AIO + NCQ Date: Sun, 27 Jan 2013 18:44:37 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:44:04 -0000 ----- Original Message ----- From: "Vladislav Prodan" To: "Steven Hartland" Cc: ; Sent: Sunday, January 27, 2013 3:13 PM Subject: Re[2]: Re[2]: AHCI timeout when using ZFS + AIO + NCQ > > >> ----- Original Message ----- >> From: "Vladislav Prodan" >> >> >> Is it always the same disk, of so replace it SMART helps identify issues >> >> but doesn't tell you 100% there's no problem. >> > >> > >> > Now it has fallen off a different HDD - ada0. >> > I'm 99% sure that MHDD will not find problems in HDD - ada0 and ada2. >> > I still have three servers with similar chipsets that have similar problems >> > with blade ahci times out. >> >> I notice your disks are connecting at SATA 3.x, which rings bells. We had >> a very similar issue on a new Supermicro machine here and after much >> testing we proved to our satisfaction that the problem was the HW. > > > I have a motherboard ASUS M5A97 PRO > http://www.asus.com/Motherboard/M5A97_PRO/#specifications > Has replacement SATA data cables. > Putting hard RAID controller does not guarantee data recovery at his death. Not sure what that has to do with cable / track lengths via things like a backplane? Do you or do you not have a hotswap backplane? >> Essentially the combination of SATA 3 speeds the midplane / backplane >> degraded the connection between the MB and HDD enough to cause >> the disks to randomly drop when under load. >> >> If we connected the disks directly to the MB with SATA cables the >> problem went away. In the end we had midplanes changed from an >> AHCI pass-through to active LSI controller. >> >> So if you have any sort of midplane / backplane connecting your disks >> try connecting them direct to the MB / controller via known SATA 3.x >> compliant cables and see if that stops the drops. >> >> Another test you can do is to force the disks to connect at SATA 2.x >> this also fixed it in our case, but wasn't something we wanted to >> put into production hence the controller swap. >> >> To force SATA 2 speeds you can use the following in /boot/loader.conf >> where 'X' is disk identifier e.g. for ada0 X = 0:- >> hint.ahcich.X.sata_rev=2 This is still worth trying as it could still indicate a problem with your controller, cables or disks. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:02:08 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5E7EE6BF; Sun, 27 Jan 2013 19:02:08 +0000 (UTC) (envelope-from universite@ukr.net) Received: from ffe16.ukr.net (ffe16.ukr.net [195.214.192.51]) by mx1.freebsd.org (Postfix) with ESMTP id 06DD7B1; Sun, 27 Jan 2013 19:02:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Date:Message-Id:From:To:References:In-Reply-To:Subject:Cc:Content-Type:Content-Transfer-Encoding:MIME-Version; bh=sgAv80HRGHZrDFfsP8s1dqUbMJPy4blkmHgI4So/RBw=; b=TBW+YxoNuAsbRBw0DTEacjNpHoqgd2/MiI5S12C8LYbpvjyK0JDiIwlIAYq2BJ/URRD6LK0rdE4ssuq66gE/kbB9N84f3JWlBn3se8FzCrEARihxnjm58tGxIbArgLaf6WJ7lkc5r5VQ7hhjPOUGDRxI1MZTLfJjv7oyuXypDno=; Received: from mail by ffe16.ukr.net with local ID 1TzXUN-000IPl-KG ; Sun, 27 Jan 2013 21:01:59 +0200 MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: binary Content-Type: text/plain; charset="windows-1251" Subject: Re[2]: AHCI timeout when using ZFS + AIO + NCQ In-Reply-To: <917933DB5C9A490D93A739058C2507A1@multiplay.co.uk> References: <917933DB5C9A490D93A739058C2507A1@multiplay.co.uk> <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <70362.1359299605.3196836531757973504@ffe11.ukr.net> To: "Steven Hartland" From: "Vladislav Prodan" X-Mailer: freemail.ukr.net 4.0 Message-Id: <70578.1359313319.18126575192049975296@ffe16.ukr.net> X-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Date: Sun, 27 Jan 2013 21:01:59 +0200 Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:02:08 -0000 > >> Essentially the combination of SATA 3 speeds the midplane / backplane > >> degraded the connection between the MB and HDD enough to cause > >> the disks to randomly drop when under load. > >> > >> If we connected the disks directly to the MB with SATA cables the > >> problem went away. In the end we had midplanes changed from an > >> AHCI pass-through to active LSI controller. > >> > >> So if you have any sort of midplane / backplane connecting your disks > >> try connecting them direct to the MB / controller via known SATA 3.x > >> compliant cables and see if that stops the drops. > >> > >> Another test you can do is to force the disks to connect at SATA 2.x > >> this also fixed it in our case, but wasn't something we wanted to > >> put into production hence the controller swap. > >> > >> To force SATA 2 speeds you can use the following in /boot/loader.conf > >> where 'X' is disk identifier e.g. for ada0 X = 0:- > >> hint.ahcich.X.sata_rev=2 > > This is still worth trying as it could still indicate a problem > with your controller, cables or disks. > Or, simply disable the ahci kernel module and use only ata? -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:02:08 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E3CC86C0 for ; Sun, 27 Jan 2013 19:02:08 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 77325B2 for ; Sun, 27 Jan 2013 19:02:08 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0RJ26p3009687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 27 Jan 2013 20:02:07 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Sun, 27 Jan 2013 20:02:06 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Ryan Stone Subject: Re: svn2git exporter is down on git-beta.freebsd.org? Message-ID: <20130127190206.GP35868@acme.spoerlein.net> Mail-Followup-To: Ryan Stone , Oliver Pinter , FreeBSD Current References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , Oliver Pinter X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:02:08 -0000 On Sun, 2013-01-27 at 12:48:13 -0500, Ryan Stone wrote: > > On Sun, Jan 27, 2013 at 11:46 AM, Oliver Pinter wrote: > > Hi All! > > The svn2git exporter is down on git-beta.freebsd.org? The last update > was 2013.jan.15. > > > The mirror on GitHub is still getting updates: > https://github.com/freebsd/freebsd > > The git beta was supposed to be re-rolled on the 15th.  GitHub clearly got the > update, but git-beta.freebsd.org didn't.  Perhaps uqs@ forgot to do a force > push? Rats! During the re-roll I moved the freebsd (src) repo to freebsd-base, so as to be more consistent with the other repos. And also so that I could run the re-roll next to the previous one. Anyway, the URL for the git-beta.freebsd.org repos are now: * git://git-beta.freebsd.org/freebsd-base.git * git://git-beta.freebsd.org/freebsd-doc.git * git://git-beta.freebsd.org/freebsd-ports.git (note the -base for src) Wiki was updated accordingly, but really, please, please, please pull from github.com. Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:05:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E43998F for ; Sun, 27 Jan 2013 19:05:16 +0000 (UTC) (envelope-from konfer@mikulas.com) Received: from parez.praha12.net (parez.6.praha12.net [IPv6:2a01:490:16:2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 13984F2 for ; Sun, 27 Jan 2013 19:05:16 +0000 (UTC) Received: from mech.mikulas.com (mech.platan.praha12.czf [10.27.66.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by parez.praha12.net (Postfix) with ESMTPS id EDFA8C6001 for ; Sun, 27 Jan 2013 20:05:12 +0100 (CET) Message-ID: <51057A68.7000106@mikulas.com> Date: Sun, 27 Jan 2013 20:05:12 +0100 From: Jiri Mikulas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120619 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Zpool surgery References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> In-Reply-To: <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:05:16 -0000 On 2013/01/27 15:31, Steven Hartland wrote: > ----- Original Message ----- From: "Ulrich Spörlein" > >> I have a slight problem with transplanting a zpool, maybe this is not >> possible the way I like to do it, maybe I need to fuzz some >> identifiers... >> >> I want to transplant my old zpool tank from a 1TB drive to a new 2TB >> drive, but *not* use dd(1) or any other cloning mechanism, as the pool >> was very full very often and is surely severely fragmented. >> > > Cant you just drop the disk in the original machine, set it as a mirror > then once the mirror process has completed break the mirror and remove > the 1TB disk. > > If this is a boot disk don't forget to set the boot block as well. > > Regards > Steve Hello before you start rebuilding mirror this way, don't forget zpool set autoexpand=on tank after you drop old 1TB disc from config, space will be expanded to new disc size. Regards Jiri From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:06:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A4125AA8 for ; Sun, 27 Jan 2013 19:06:19 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.c2i.net [212.247.154.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1D39010A for ; Sun, 27 Jan 2013 19:06:18 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 375347014; Sun, 27 Jan 2013 20:06:16 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: ulpt can't attach Lexmark E120 Date: Sun, 27 Jan 2013 20:07:30 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <5105527F.3010708@m5p.com> <201301271915.47712.hselasky@c2i.net> <510570C1.1060607@m5p.com> In-Reply-To: <510570C1.1060607@m5p.com> X-Face: ?p&W)c(+80hU; '{.$5K+zq{oC6y| /D'an*6mw>j'f:eBsex\Gi, Cc: George Mitchell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:06:19 -0000 On Sunday 27 January 2013 19:24:01 George Mitchell wrote: > On 01/27/13 13:15, Hans Petter Selasky wrote: > > [...] > > > > Hi, > > > > I don't see any errors in the usbdump trace you sent. So we can at least > > rule that out. > > > > Hint: You can filter traffic using the -f option for usbdump. > > > > What does: > > > > usbconfig dump_device_desc dump_curr_config_desc > > > > output? Can you also get same output from working system? > > > > --HPS > > Attachment 1 from Raspberry Pi. > Attachment 2 from 9.1-RELEASE on amd64. -- George Hi, These look identical. I suspect it is a problem to allocate memory for the USB transfers. I need output when hw.usb.ulpt.debug=15 to say exactly. Could you ask the provider of the binaries to compile having USB_DEBUG set, also for the modules. --HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:08:08 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9D773C4A; Sun, 27 Jan 2013 19:08:08 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2DFC5127; Sun, 27 Jan 2013 19:08:08 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0RJ86S1009795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 27 Jan 2013 20:08:06 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Sun, 27 Jan 2013 20:08:06 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Fabian Keil Subject: Re: Zpool surgery Message-ID: <20130127190806.GQ35868@acme.spoerlein.net> Mail-Followup-To: Fabian Keil , current@FreeBSD.org, fs@FreeBSD.org References: <20130127103612.GB38645@acme.spoerlein.net> <20130127145601.7f650d3c@fabiankeil.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130127145601.7f650d3c@fabiankeil.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@FreeBSD.org, fs@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:08:08 -0000 On Sun, 2013-01-27 at 14:56:01 +0100, Fabian Keil wrote: > Ulrich Spörlein wrote: > > > I have a slight problem with transplanting a zpool, maybe this is not > > possible the way I like to do it, maybe I need to fuzz some > > identifiers... > > > > I want to transplant my old zpool tank from a 1TB drive to a new 2TB > > drive, but *not* use dd(1) or any other cloning mechanism, as the pool > > was very full very often and is surely severely fragmented. > > > > So, I have tank (the old one), the new one, let's call it tank' and > > then there's the archive pool where snapshots from tank are sent to, and > > these should now come from tank' in the future. > > > > I have: > > tank -> sending snapshots to archive > > > > I want: > > tank' -> sending snapshots to archive > > > > Ideally I would want archive to not even know that tank and tank' are > > different, so as to not have to send a full snapshot again, but > > continue the incremental snapshots. > > > > So I did zfs send -R tank | ssh otherhost "zfs recv -d tank" and that > > worked well, this contained a snapshot A that was also already on > > archive. Then I made a final snapshot B on tank, before turning down that > > pool and sent it to tank' as well. > > > > Now I have snapshot A on tank, tank' and archive and they are virtually > > identical. I have snapshot B on tank and tank' and would like to send > > this from tank' to archive, but it complains: > > > > cannot receive incremental stream: most recent snapshot of archive does > > not match incremental source > > In general this should work, so I'd suggest that you double check > that you are indeed sending the correct incremental. > > > Is there a way to tweak the identity of tank' to be *really* the same as > > tank, so that archive can accept that incremental stream? Or should I > > use dd(1) after all to transplant tank to tank'? My other option would > > be to turn on dedup on archive and send another full stream of tank', > > 99.9% of which would hopefully be deduped and not consume precious space > > on archive. > > The pools don't have to be the same. > > I wouldn't consider dedup as you'll have to recreate the pool if > it turns out the the dedup performance is pathetic. On a system > that hasn't been created with dedup in mind that seems rather > likely. > > > Any ideas? > > Your whole procedure seems a bit complicated to me. > > Why don't you use "zpool replace"? Ehhh, .... "zpool replace", eh? I have to say I didn't know that option was available, but also because this is on a newer machine, I needed some way to do this over the network, so a direct zpool replace is not that easy. I dug out an old ATA-to-USB case and will use that to attach the old tank to the new machine and then have a try at this zpool replace thing. How will that affect the fragmentation level of the new pool? Will the resilver do something sensible wrt. keeping files together for better read-ahead performance? Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 19:12:13 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4F7EDEE0; Sun, 27 Jan 2013 19:12:13 +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 2BE98155; Sun, 27 Jan 2013 19:12:11 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 372818926; Sun, 27 Jan 2013 20:12:10 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: Zpool surgery Date: Sun, 27 Jan 2013 20:13:24 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <20130127103612.GB38645@acme.spoerlein.net> <20130127145601.7f650d3c@fabiankeil.de> <20130127190806.GQ35868@acme.spoerlein.net> In-Reply-To: <20130127190806.GQ35868@acme.spoerlein.net> X-Face: ?p&W)c( =?iso-8859-1?q?+80hU=3B=27=7B=2E=245K+zq=7BoC6y=7C=0A=09/D=27an*6mw?=>j'f:eBsex\Gi, Cc: fs@freebsd.org, current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 19:12:13 -0000 On Sunday 27 January 2013 20:08:06 Ulrich Sp=C3=B6rlein wrote: > I dug out an old ATA-to-USB case and will use that to attach the old > tank to the new machine and then have a try at this zpool replace thing. If you are using -current you might want this patch first: http://svnweb.freebsd.org/changeset/base/245995 =2D-HPS From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 20:11:57 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6B452D00; Sun, 27 Jan 2013 20:11:57 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 031062F8; Sun, 27 Jan 2013 20:11:56 +0000 (UTC) Received: from server.rulingia.com (c220-239-246-167.belrs5.nsw.optusnet.com.au [220.239.246.167]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id r0RKBltH004480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 28 Jan 2013 07:11:47 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id r0RKBgLt092002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jan 2013 07:11:42 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id r0RKBffX092001; Mon, 28 Jan 2013 07:11:41 +1100 (EST) (envelope-from peter) Date: Mon, 28 Jan 2013 07:11:40 +1100 From: Peter Jeremy To: Steven Hartland Subject: Re: Zpool surgery Message-ID: <20130127201140.GD29105@server.rulingia.com> References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QRj9sO5tAVLaXnSD" Content-Disposition: inline In-Reply-To: <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 20:11:57 -0000 --QRj9sO5tAVLaXnSD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2013-Jan-27 14:31:56 -0000, Steven Hartland wr= ote: >----- Original Message -----=20 >From: "Ulrich Sp=F6rlein" >> I want to transplant my old zpool tank from a 1TB drive to a new 2TB >> drive, but *not* use dd(1) or any other cloning mechanism, as the pool >> was very full very often and is surely severely fragmented. > >Cant you just drop the disk in the original machine, set it as a mirror >then once the mirror process has completed break the mirror and remove >the 1TB disk. That will replicate any fragmentation as well. "zfs send | zfs recv" is the only (current) way to defragment a ZFS pool. --=20 Peter Jeremy --QRj9sO5tAVLaXnSD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEFifwACgkQ/opHv/APuIeuUACgqCCNXfxYUs6MF9RcFnRvANg3 T+AAnAsdg/RXxe7Y9nCPRFmKWizYzuKB =Y809 -----END PGP SIGNATURE----- --QRj9sO5tAVLaXnSD-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 20:18:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8E7071E1 for ; Sun, 27 Jan 2013 20:18:51 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 730C23CB for ; Sun, 27 Jan 2013 20:18:51 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TzYge-0002oy-Bu for freebsd-current@freebsd.org; Sun, 27 Jan 2013 12:18:44 -0800 Date: Sun, 27 Jan 2013 12:18:44 -0800 (PST) From: Beeblebrox To: freebsd-current@freebsd.org Message-ID: <1359317924363-5781425.post@n5.nabble.com> In-Reply-To: <70578.1359313319.18126575192049975296@ffe16.ukr.net> References: <13391.1359029978.3957795939058384896@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> <70362.1359299605.3196836531757973504@ffe11.ukr.net> <917933DB5C9A490D93A739058C2507A1@multiplay.co.uk> <70578.1359313319.18126575192049975296@ffe16.ukr.net> Subject: Re: Re[2]: AHCI timeout when using ZFS + AIO + NCQ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 20:18:51 -0000 I once ran into a very severe AHCI timeout problem. After months of trying to figure it out and insane "Hardware_ECC_Recovered" error values, I found that the error was with the power connector plug / sata HDD interface. All errors disappeared after replacing that cable. Since you have error on more than 1 HDD, I suggest: 1. Check smartctl output for each AND all HDD 2. Check whether your power supply unit is still healthy or if it is supplying inconsistent power. 3. Check the main power supply line and whether it shows any voltage fluctuations or if there is a new heavy consumer of amps on the same power line as the server is plugged to. -- View this message in context: http://freebsd.1045724.n5.nabble.com/AHCI-timeout-when-using-ZFS-AIO-NCQ-tp5780454p5781425.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 20:29:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 371AB795 for ; Sun, 27 Jan 2013 20:29:12 +0000 (UTC) (envelope-from zaphod@berentweb.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD0368E for ; Sun, 27 Jan 2013 20:29:11 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TzYql-0003QM-Hw for freebsd-current@freebsd.org; Sun, 27 Jan 2013 12:29:11 -0800 Date: Sun, 27 Jan 2013 12:29:11 -0800 (PST) From: Beeblebrox To: freebsd-current@freebsd.org Message-ID: <1359318551546-5781432.post@n5.nabble.com> Subject: ccache selects wrong compiler (calls clang, not gcc46) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 20:29:12 -0000 I had posted this problem in the freebsd-ports section of the mailing list, but I got no answer. When I posted, I was using 9-Stable with clang-only world. (http://freebsd.1045724.n5.nabble.com/ccache-selects-wrong-compiler-calls-clang-not-gcc46-td5775609.html) I recently switched to 10-current but the error persisted. So I filed a bug report on the ccache bugzilla, but the maintainer has advised that he does not know FreeBSD that well and has deferred the issue back to FreeBSD. PR and full problem description from link below. Maintainer states: "I'm fairly certain that the problem you are seeing has nothing to do with ccache per se but rather with how FreeBSD uses ccache". https://bugzilla.samba.org/show_bug.cgi?id=9607 In essence the problem appears to be: With a pure clang built world, if you try to use gcc46 (lang/gcc) with ccache enabled to build ports, ccache does not use gcc46 but instead calls clang. Thanks & Regards -- View this message in context: http://freebsd.1045724.n5.nabble.com/ccache-selects-wrong-compiler-calls-clang-not-gcc46-tp5781432.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 20:36:41 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E7B43AE3; Sun, 27 Jan 2013 20:36:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id B739E6E0; Sun, 27 Jan 2013 20:36:41 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r0RKaeme056073; Sun, 27 Jan 2013 15:36:40 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r0RKaegX056069; Sun, 27 Jan 2013 20:36:40 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 27 Jan 2013 20:36:40 GMT Message-Id: <201301272036.r0RKaegX056069@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on arm/arm Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 20:36:42 -0000 TB --- 2013-01-27 19:40:17 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-27 19:40:17 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-27 19:40:17 - starting HEAD tinderbox run for arm/arm TB --- 2013-01-27 19:40:17 - cleaning the object tree TB --- 2013-01-27 19:41:07 - /usr/local/bin/svn stat /src TB --- 2013-01-27 19:41:11 - At svn revision 245995 TB --- 2013-01-27 19:41:12 - building world TB --- 2013-01-27 19:41:12 - CROSS_BUILD_TESTING=YES TB --- 2013-01-27 19:41:12 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-27 19:41:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-27 19:41:12 - SRCCONF=/dev/null TB --- 2013-01-27 19:41:12 - TARGET=arm TB --- 2013-01-27 19:41:12 - TARGET_ARCH=arm TB --- 2013-01-27 19:41:12 - TZ=UTC TB --- 2013-01-27 19:41:12 - __MAKE_CONF=/dev/null TB --- 2013-01-27 19:41:12 - cd /src TB --- 2013-01-27 19:41:12 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Jan 27 19:41:16 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Jan 27 20:36:39 UTC 2013 TB --- 2013-01-27 20:36:39 - generating LINT kernel config TB --- 2013-01-27 20:36:39 - cd /src/sys/arm/conf TB --- 2013-01-27 20:36:39 - /usr/bin/make -B LINT TB --- 2013-01-27 20:36:39 - cd /src/sys/arm/conf TB --- 2013-01-27 20:36:39 - /usr/sbin/config -m LINT TB --- 2013-01-27 20:36:39 - building LINT kernel TB --- 2013-01-27 20:36:39 - CROSS_BUILD_TESTING=YES TB --- 2013-01-27 20:36:39 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-27 20:36:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-27 20:36:39 - SRCCONF=/dev/null TB --- 2013-01-27 20:36:39 - TARGET=arm TB --- 2013-01-27 20:36:39 - TARGET_ARCH=arm TB --- 2013-01-27 20:36:39 - TZ=UTC TB --- 2013-01-27 20:36:39 - __MAKE_CONF=/dev/null TB --- 2013-01-27 20:36:39 - cd /src TB --- 2013-01-27 20:36:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jan 27 20:36:39 UTC 2013 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/arm/conf; PATH=/obj/arm.arm/src/tmp/legacy/usr/sbin:/obj/arm.arm/src/tmp/legacy/usr/bin:/obj/arm.arm/src/tmp/legacy/usr/games:/obj/arm.arm/src/tmp/usr/sbin:/obj/arm.arm/src/tmp/usr/bin:/obj/arm.arm/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/arm.arm/src/sys/LINT /src/sys/arm/conf/LINT WARNING: duplicate option `GEOM_PART_BSD' encountered. WARNING: duplicate option `GEOM_PART_MBR' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `CAM_DEBUG_DELAY' encountered. config: ../mv/kirkwood/files.sheevaplug: No such file or directory *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-01-27 20:36:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-01-27 20:36:40 - ERROR: failed to build LINT kernel TB --- 2013-01-27 20:36:40 - 2531.33 user 565.02 system 3382.85 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Sun Jan 27 22:33:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BBD3594D for ; Sun, 27 Jan 2013 22:33:08 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 23F75989 for ; Sun, 27 Jan 2013 22:33:07 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0RMWsej005680; Sun, 27 Jan 2013 17:32:59 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <5105AB16.2000607@m5p.com> Date: Sun, 27 Jan 2013 17:32:54 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: Hans Petter Selasky Subject: Re: ulpt can't attach Lexmark E120 References: <5105527F.3010708@m5p.com> <201301271915.47712.hselasky@c2i.net> <510570C1.1060607@m5p.com> <201301272007.30682.hselasky@c2i.net> In-Reply-To: <201301272007.30682.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sun, 27 Jan 2013 17:33:00 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 22:33:08 -0000 On 01/27/13 14:07, Hans Petter Selasky wrote: > On Sunday 27 January 2013 19:24:01 George Mitchell wrote: >> On 01/27/13 13:15, Hans Petter Selasky wrote: >>> [...] >>> >>> Hi, >>> >>> I don't see any errors in the usbdump trace you sent. So we can at least >>> rule that out. >>> >>> Hint: You can filter traffic using the -f option for usbdump. >>> >>> What does: >>> >>> usbconfig dump_device_desc dump_curr_config_desc >>> >>> output? Can you also get same output from working system? >>> >>> --HPS >> >> Attachment 1 from Raspberry Pi. >> Attachment 2 from 9.1-RELEASE on amd64. -- George > > Hi, > > These look identical. I suspect it is a problem to allocate memory for the USB > transfers. I need output when hw.usb.ulpt.debug=15 to say exactly. Could you > ask the provider of the binaries to compile having USB_DEBUG set, also for the > modules. > > --HPS > I'm working on getting a debug build ... Thanks for your help so far. I notice that there seem to be only trivial differences between the 9.1 release ulpt and the 10.0 current ulpt driver. -- George From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 02:10:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AF34446A for ; Mon, 28 Jan 2013 02:10:18 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id 42CD9173 for ; Mon, 28 Jan 2013 02:10:17 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id r0S0ce8u007690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 28 Jan 2013 01:38:41 +0100 Received: from [192.168.1.110] (149.Red-79-152-213.dynamicIP.rima-tde.net [79.152.213.149]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id r0S0cdVR005040 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 28 Jan 2013 01:38:40 +0100 Message-ID: <5105C88E.7080509@entel.upc.edu> Date: Mon, 28 Jan 2013 01:38:38 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: acpi resume related patch References: <510245B5.8070704@FreeBSD.org> In-Reply-To: <510245B5.8070704@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Mon, 28 Jan 2013 01:38:41 +0100 (CET) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:10:18 -0000 Al 25/01/2013 09:43, En/na Andriy Gapon ha escrit: > > If you have ACPI suspend/resume working, if it used to work but stopped working > at some time, if it never worked, but you are still hoping, could you please > test the following patch and report back? > > http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch > > > Hi, the patch applies cleanly. Suspend did work in the past and seem to work now. However resume did not work and still doesn't. The problematic system is a Fujitsu laptop running AMD64 as today's head. In the past I tried the usual things (like running without X(Intel with GEM/KMS), removing all possible hardware out the kernel, etc...) without joy. My home server runs AMD64 with gemenized Intel and suspend/resume does work. For any additional info, let me know. Gustau -- Salut i força, Gustau --------------------------------------------------------------------------- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 02:22:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0EF885E8 for ; Mon, 28 Jan 2013 02:22:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-da0-f51.google.com (mail-da0-f51.google.com [209.85.210.51]) by mx1.freebsd.org (Postfix) with ESMTP id BB4331C1 for ; Mon, 28 Jan 2013 02:22:34 +0000 (UTC) Received: by mail-da0-f51.google.com with SMTP id i30so1005847dad.24 for ; Sun, 27 Jan 2013 18:22:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=L1ElUsX9Syu+nSZKWwWAu8uNrOreSre8De0MAFu8VRE=; b=VqQWKhMuFGGT/89ohA9T4bkstthdc8DjwEB2rdroNvXEgkKqmefdNoRg2KRUjS12KK jIuImSryEDbOIIdW5o/kOAS9LUFGsUVeTdP5z/UPEniMSAtBkb1fStqql85rj/eRciZY KEds/XjkWZobsZUg+MydmCvE276xrVcJJiKTa1qUz9EOgiRav1ZRJTSOn4FmiNmN450D /4RROuvIb76ZqnYqpl/xclKiOQs+TLvobAaXu+o/PGCQ0eE51VWJzdkW8k7/aGQamLcM JUGuopTOhytuD/6DJofoA/WYsTjBZkMEPT3EJJo7OgWhX+RGsbUCw17DBJQ+j5DTDTFU psIQ== MIME-Version: 1.0 X-Received: by 10.68.233.197 with SMTP id ty5mr34468790pbc.9.1359339748664; Sun, 27 Jan 2013 18:22:28 -0800 (PST) Received: by 10.67.2.65 with HTTP; Sun, 27 Jan 2013 18:22:28 -0800 (PST) In-Reply-To: <5105C88E.7080509@entel.upc.edu> References: <510245B5.8070704@FreeBSD.org> <5105C88E.7080509@entel.upc.edu> Date: Sun, 27 Jan 2013 18:22:28 -0800 Message-ID: Subject: Re: acpi resume related patch From: Kevin Oberman To: =?UTF-8?Q?Gustau_P=C3=A9rez_i_Querol?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:22:35 -0000 On Sun, Jan 27, 2013 at 4:38 PM, Gustau P=C3=A9rez i Querol wrote: > Al 25/01/2013 09:43, En/na Andriy Gapon ha escrit: > >> >> If you have ACPI suspend/resume working, if it used to work but stopped >> working >> at some time, if it never worked, but you are still hoping, could you >> please >> test the following patch and report back? >> >> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch >> >> >> > > Hi, > > the patch applies cleanly. Suspend did work in the past and seem to wor= k > now. However resume did not work and still doesn't. > > The problematic system is a Fujitsu laptop running AMD64 as today's hea= d. > > In the past I tried the usual things (like running without X(Intel with > GEM/KMS), removing all possible hardware out the kernel, etc...) without > joy. My home server runs AMD64 with gemenized Intel and suspend/resume do= es > work. > > For any additional info, let me know. > > Gustau > > > -- > Salut i for=C3=A7a, > > Gustau Very much the same on my ThinkPad T520. Suspend looks fine. Resume turns on the backlight, but that's about it. No wireless and no display. The power light continues to pulse, indicating the system still considers itself suspended. 9.1-STABLE amd64 updated today. Patch applied cleanly. Intel Wireless card (iwn driver) and with KMS. Resume has never worked on this system. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 02:32:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 57EFC858; Mon, 28 Jan 2013 02:32:32 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 27FBE214; Mon, 28 Jan 2013 02:32:32 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 66A0223F654; Sun, 27 Jan 2013 21:32:30 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.4 onyx.glenbarber.us 66A0223F654 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Sun, 27 Jan 2013 21:32:28 -0500 From: Glen Barber To: Kevin Oberman Subject: Re: acpi resume related patch Message-ID: <20130128023228.GV1423@glenbarber.us> References: <510245B5.8070704@FreeBSD.org> <5105C88E.7080509@entel.upc.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mdGUb96ZZNqpHCXz" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Gustau =?iso-8859-1?Q?P=E9rez?= i Querol , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:32:32 -0000 --mdGUb96ZZNqpHCXz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jan 27, 2013 at 06:22:28PM -0800, Kevin Oberman wrote: > Very much the same on my ThinkPad T520. Suspend looks fine. Resume > turns on the backlight, but that's about it. No wireless and no > display. The power light continues to pulse, indicating the system > still considers itself suspended. > 9.1-STABLE amd64 updated today. Patch applied cleanly. Intel Wireless > card (iwn driver) and with KMS. Resume has never worked on this > system. To regretfully add a "me too", I have similar problems with my Asus X53E laptop. Suspend works fine. When I resume, X resumes fine - just long enough for me to see things "resume", indicating networking works, processes are resuming, etc. Things go downhill once I become hopeful. If I run top(1) before suspending, uptime can vary from anything from a few minutes, to a few days. (Sometimes, even runs backwards.) I _think_ I've narrowed down the "things go to hell" point to human input - mouse, keyboard, specifically. Glen --mdGUb96ZZNqpHCXz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRBeM8AAoJEFJPDDeguUaj/gwIAKyjw6ttCLEAxg7Nh55mphBS /kRqMYGb23QQgz+BK3kbZHzVccrt03B91HQ7ahEggds7WSAj7uEbUJ8ngShBwEnW teEyJSWshN9NDxCWtXzF/HP+hJBix6hkYmH/qD01a2ZnqbLT/gO4YMNHWzDF1dSq yVs6jaw+2i1FXZRE+vAb1Kmgz1Kwp8xj38P0JkZGBVrKlPhWGfdF8haD4ExjUN9Y SSrVnfVS2e44M7u2dq6SRmG/gx/DV85zdpDnJZheOrix0qtfaaeMQr57qZHQDldr Y4ucE6H1OemmQE4knyvkgiZ1EisX7B+MOSGr8wcQuHdkrC1lgG9lUq1bjOaKUOE= =5ohg -----END PGP SIGNATURE----- --mdGUb96ZZNqpHCXz-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 02:35:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0072C98E; Mon, 28 Jan 2013 02:35:24 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 89E2F23C; Mon, 28 Jan 2013 02:35:22 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 21B8F23F65D; Sun, 27 Jan 2013 21:35:17 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.4 onyx.glenbarber.us 21B8F23F65D Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Sun, 27 Jan 2013 21:35:14 -0500 From: Glen Barber To: Kevin Oberman Subject: Re: acpi resume related patch Message-ID: <20130128023514.GW1423@glenbarber.us> References: <510245B5.8070704@FreeBSD.org> <5105C88E.7080509@entel.upc.edu> <20130128023228.GV1423@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="36+Jv5wzUORg1Ut4" Content-Disposition: inline In-Reply-To: <20130128023228.GV1423@glenbarber.us> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Gustau =?iso-8859-1?Q?P=E9rez?= i Querol , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:35:25 -0000 --36+Jv5wzUORg1Ut4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 27, 2013 at 09:32:28PM -0500, Glen Barber wrote: > On Sun, Jan 27, 2013 at 06:22:28PM -0800, Kevin Oberman wrote: > > Very much the same on my ThinkPad T520. Suspend looks fine. Resume > > turns on the backlight, but that's about it. No wireless and no > > display. The power light continues to pulse, indicating the system > > still considers itself suspended. > > 9.1-STABLE amd64 updated today. Patch applied cleanly. Intel Wireless > > card (iwn driver) and with KMS. Resume has never worked on this > > system. >=20 > To regretfully add a "me too", I have similar problems with my Asus X53E > laptop. >=20 > Suspend works fine. When I resume, X resumes fine - just long enough > for me to see things "resume", indicating networking works, processes > are resuming, etc. >=20 > Things go downhill once I become hopeful. If I run top(1) before > suspending, uptime can vary from anything from a few minutes, to a few > days. (Sometimes, even runs backwards.) >=20 > I _think_ I've narrowed down the "things go to hell" point to human > input - mouse, keyboard, specifically. >=20 And, after realizing I am confusing different but seemingly similar threads, I realize I did not apply Andriy's patch. Will report back in about 25 minutes, then. :-) Glen --36+Jv5wzUORg1Ut4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRBePiAAoJEFJPDDeguUajGaAH/jrObQMgHQprpGL2Coi5Zzf7 1J/Vaz7f+VyLN5kpDYPwBUojSCgMEKFVGeeE/SPWCKf1hmGJUdrbolqZguSGxeNo 8afnJmELg+KHxpJH73vAsmyklBovbPEbALw1YwDo9yyMGPwYVTGrYEl+YXgvZSXT 76yAnpTOgMjIpWfj+l2yUJbATVMR6bxwEOPxmDvIUGRu4kp8evBn4uGY6RepMQ8N epyeigHYW+CXqKn/v+GQ1fj0VtvlVU6uWKFeXM+eZ1dsw29MIhW5fZ3KcL2EeFV+ 1BJ0OCFsUPyjEhoKjhBdE8ws7+KWpCDGEybhAB29rKpfpNzNReyDA3t77QB9eMc= =4I1p -----END PGP SIGNATURE----- --36+Jv5wzUORg1Ut4-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 02:52:43 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2F9CBF7E; Mon, 28 Jan 2013 02:52:43 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 072E62C1; Mon, 28 Jan 2013 02:52:43 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 5724B23F654; Sun, 27 Jan 2013 21:52:41 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.4 onyx.glenbarber.us 5724B23F654 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Sun, 27 Jan 2013 21:52:39 -0500 From: Glen Barber To: Andriy Gapon Subject: Re: acpi resume related patch Message-ID: <20130128025239.GA1296@glenbarber.us> References: <510245B5.8070704@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <510245B5.8070704@FreeBSD.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:52:43 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: >=20 > If you have ACPI suspend/resume working, if it used to work but stopped w= orking > at some time, if it never worked, but you are still hoping, could you ple= ase > test the following patch and report back? >=20 > http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch >=20 FWIW, I am (very happy) to report my laptop has resumed for longer than 10 seconds for the first time ever. root@nucleus:~ # uname -a FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #56 r245748M: Sun Jan 27 21:39:55 EST 2013 root@nucleus:/usr/obj/usr/src/sys/NUCLEUS amd64 root@nucleus:~ # kldstat=20 Id Refs Address Size Name 1 60 0xffffffff80200000 dfc0d8 kernel 2 1 0xffffffff80ffd000 21cc80 zfs.ko 3 2 0xffffffff8121a000 5e08 opensolaris.ko 4 1 0xffffffff81220000 1fc48 geom_eli.ko 5 2 0xffffffff81240000 138dd0 linux.ko 6 1 0xffffffff81379000 2a70 coretemp.ko 7 1 0xffffffff8137c000 70e8 acpi_video.ko 8 1 0xffffffff81384000 6668 sem.ko 9 1 0xffffffff8138b000 8b10 acpi_asus.ko 10 1 0xffffffff81394000 4a18 aesni.ko 11 1 0xffffffff81412000 28805 pf.ko 12 1 0xffffffff8143b000 5f590 i915kms.ko 13 1 0xffffffff8149b000 13f2 iicbb.ko 14 4 0xffffffff8149d000 136f iicbus.ko 15 1 0xffffffff8149f000 df9 iic.ko 16 2 0xffffffff814a0000 ab34 agp.ko 17 1 0xffffffff814ab000 2dce9 drm2.ko 18 1 0xffffffff814d9000 25b linux_adobe.ko Current uptime post-resume is about 5 minutes. Glen --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRBef3AAoJEFJPDDeguUajlhYIAKsP8OvwtNRSu5tIgtNRE2CS bD276rcDip8Y339vMG1pw8b/ODE/qJFBOjsssmEvFluHr/2afWDvnFddamk0eE/V TYEW8AhYNTQ4DaWN2vXdgYXyegoP9nuczotoUgvCDWDO3wN7v0xDDxqkFLQgZeqU jIqNluUwjwshebJYNqhopahvRmemGTLCIB/ns5dS4U7DIUO4foy1I0hveB/5McII 6fjXODNFY4NZ2alARMu6pd4f8zKE97g8HjX/RolTd0WmumbnaqfwhNzPEdJrYGM1 9jMFP4O1VjawM+4+YJaRe7eTu9mMkaZP4rTw4glRbwDqpIYsQOIpZmUCcKYnem0= =mWnv -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 06:09:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 568E582C; Mon, 28 Jan 2013 06:09:26 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by mx1.freebsd.org (Postfix) with ESMTP id 53E44AE2; Mon, 28 Jan 2013 06:09:24 +0000 (UTC) Received: by mail-lb0-f172.google.com with SMTP id n8so3431020lbj.31 for ; Sun, 27 Jan 2013 22:09:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:reply-to:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=uBGja5K34a6x2y2sjajZvAWWZ4YXnpH81Iwd/kG85vo=; b=WQ6eEzdiZNKLHSTYosoA20IzTZo0QVw324+4BjdXlCP56pFMfqHhKd0harEiyj3nza a5dmOtaTqsfPNx50Yw44d44B6n4sxu5liF7MZaERfMRk64Ig/Zn90RWn4q814HcIBm1V No/8/DqLsL3cHNBcTaZByxXyj02jyNAvRVzoVJyYXisx2ernLT+Khbju1oJ7vn1mlSse 7RiPDrj/DThFp1YxAUt1FfgNzfr2i+61tSatzryhMpZrXq7n4pjaft6agVLi22d1097B ikbifGoHadIFK70Y2cRl5yRjwfke5qIfhQL0DLWnpegGiJi8IdA4T96v8nQG7pk7pu0g hwHQ== MIME-Version: 1.0 X-Received: by 10.152.105.17 with SMTP id gi17mr11877132lab.46.1359353357579; Sun, 27 Jan 2013 22:09:17 -0800 (PST) Received: by 10.114.21.197 with HTTP; Sun, 27 Jan 2013 22:09:17 -0800 (PST) In-Reply-To: <1359310302.93359.48.camel@revolution.hippie.lan> References: <1359310302.93359.48.camel@revolution.hippie.lan> Date: Mon, 28 Jan 2013 00:09:17 -0600 Message-ID: Subject: Re: Trouble with recent auto-tuning changes From: Alan Cox To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: alc@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 06:09:26 -0000 On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: > I ran into a panic while attempting to un-tar a large file on a > DreamPlug (arm-based system) running -current. The source and dest of > the un-tar is the root filesystem on sdcard, and I get this: > > panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated > > Just before the panic I see the tar process get hung in a "nokva" wait. > 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. > > In r245575 the init order for mbuf limits was changed from > SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the > results of sizing kernel memory. Unfortunately, the process of sizing > kernel memory relies on the mbuf limits; in kmeminit(): > > vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; > > Since r245575, nmbclusters is zero when this line of code runs. If I > manually plugin "32768" (the number tunable_mbinit() comes up with for > this platform) in that line, the panic stops happening. > > So we've got two problems here... one is the circular dependency in > calculating the mbuf limits. The other is the fact that some > non-trivial amount of kernel memory we're allowing for mbufs is actually > being used for other things. That is, if my system was actually using > all the mbufs that tunable_mbinit() allowed for, then this panic while > untarring a huge file would still have happened. > > All of this is factually correct. However, it's a red herring. The real problem is that arm, unlike every other architecture in the tree, does not enable auto-sizing of the kmem map based on the physical memory size. Specifically, you'll find VM_KMEM_SIZE_SCALE defined in "arch"/include/vmparam.h on every other architecture, just not on arm. This auto-sizing overrides the value of VM_KMEM_SIZE. > I arrive at the latter conclusion based on the fact that this panic > happens even if no network interfaces (other than lo0) are configured. > That is, nmbclusters == 0 is a reasonable approximation of my need for > network mbufs. So something in the system needs to be taken into > account when sizing kernel memory to allow for whatever it is about > untarring a huge file that eats kernel memory (buffer cache?). > > I can easily reproduce this if you need me to gather any specific info. > > -- Ian > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 08:16:48 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A0F3848A; Mon, 28 Jan 2013 08:16:48 +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 B35B77C; Mon, 28 Jan 2013 08:16:47 +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 KAA27862; Mon, 28 Jan 2013 10:16:45 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TzjtU-000KTw-V7; Mon, 28 Jan 2013 10:16:45 +0200 Message-ID: <510633EB.9030306@FreeBSD.org> Date: Mon, 28 Jan 2013 10:16:43 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: Glen Barber Subject: Re: acpi resume related patch References: <510245B5.8070704@FreeBSD.org> <20130128025239.GA1296@glenbarber.us> In-Reply-To: <20130128025239.GA1296@glenbarber.us> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 08:16:48 -0000 on 28/01/2013 04:52 Glen Barber said the following: > On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: >> >> If you have ACPI suspend/resume working, if it used to work but stopped working >> at some time, if it never worked, but you are still hoping, could you please >> test the following patch and report back? >> >> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch >> > > FWIW, I am (very happy) to report my laptop has resumed for longer than > 10 seconds for the first time ever. Just to clarify - you mean that previously it would try to shutdown right after resume? Or something else? > root@nucleus:~ # uname -a > FreeBSD nucleus 10.0-CURRENT FreeBSD 10.0-CURRENT #56 r245748M: Sun Jan > 27 21:39:55 EST 2013 root@nucleus:/usr/obj/usr/src/sys/NUCLEUS amd64 > > root@nucleus:~ # kldstat > Id Refs Address Size Name > 1 60 0xffffffff80200000 dfc0d8 kernel > 2 1 0xffffffff80ffd000 21cc80 zfs.ko > 3 2 0xffffffff8121a000 5e08 opensolaris.ko > 4 1 0xffffffff81220000 1fc48 geom_eli.ko > 5 2 0xffffffff81240000 138dd0 linux.ko > 6 1 0xffffffff81379000 2a70 coretemp.ko > 7 1 0xffffffff8137c000 70e8 acpi_video.ko > 8 1 0xffffffff81384000 6668 sem.ko > 9 1 0xffffffff8138b000 8b10 acpi_asus.ko > 10 1 0xffffffff81394000 4a18 aesni.ko > 11 1 0xffffffff81412000 28805 pf.ko > 12 1 0xffffffff8143b000 5f590 i915kms.ko > 13 1 0xffffffff8149b000 13f2 iicbb.ko > 14 4 0xffffffff8149d000 136f iicbus.ko > 15 1 0xffffffff8149f000 df9 iic.ko > 16 2 0xffffffff814a0000 ab34 agp.ko > 17 1 0xffffffff814ab000 2dce9 drm2.ko > 18 1 0xffffffff814d9000 25b linux_adobe.ko > > Current uptime post-resume is about 5 minutes. > > Glen > -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 08:58:25 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EB380A82; Mon, 28 Jan 2013 08:58:24 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 786A9256; Mon, 28 Jan 2013 08:58:24 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0S8wLP2029200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 28 Jan 2013 09:58:22 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Mon, 28 Jan 2013 09:58:20 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Peter Jeremy Subject: Re: Zpool surgery Message-ID: <20130128085820.GR35868@acme.spoerlein.net> Mail-Followup-To: Peter Jeremy , Steven Hartland , current@freebsd.org, fs@freebsd.org References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> <20130127201140.GD29105@server.rulingia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130127201140.GD29105@server.rulingia.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Steven Hartland , current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 08:58:25 -0000 On Mon, 2013-01-28 at 07:11:40 +1100, Peter Jeremy wrote: > On 2013-Jan-27 14:31:56 -0000, Steven Hartland wrote: > >----- Original Message ----- > >From: "Ulrich Spörlein" > >> I want to transplant my old zpool tank from a 1TB drive to a new 2TB > >> drive, but *not* use dd(1) or any other cloning mechanism, as the pool > >> was very full very often and is surely severely fragmented. > > > >Cant you just drop the disk in the original machine, set it as a mirror > >then once the mirror process has completed break the mirror and remove > >the 1TB disk. > > That will replicate any fragmentation as well. "zfs send | zfs recv" > is the only (current) way to defragment a ZFS pool. But are you then also supposed to be able send incremental snapshots to a third pool from the pool that you just cloned? I did the zpool replace now over night, and it did not remove the old device yet, as it found cksum errors on the pool: root@coyote:~# zpool status -v pool: tank state: ONLINE 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://illumos.org/msg/ZFS-8000-8A scan: resilvered 873G in 11h33m with 24 errors on Mon Jan 28 09:45:32 2013 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 27 replacing-0 ONLINE 0 0 61 da0.eli ONLINE 0 0 61 ada1.eli ONLINE 0 0 61 errors: Permanent errors have been detected in the following files: tank/src@2013-01-17:/.svn/pristine/8e/8ed35772a38e0fec00bc1cbc2f05480f4fd4759b.svn-base tank/src@2013-01-17:/.svn/pristine/4f/4febd82f50bd408f958d4412ceea50cef48fe8f7.svn-base tank/src@2013-01-17:/sys/dev/mvs/mvs_soc.c tank/src@2013-01-17:/secure/usr.bin/openssl/man/pkcs8.1 tank/src@2013-01-17:/.svn/pristine/ab/ab1efecf2c0a8f67162b2ed760772337017c5a64.svn-base tank/src@2013-01-17:/.svn/pristine/90/907580a473b00f09b01815a52251fbdc3e34e8f6.svn-base tank/src@2013-01-17:/sys/dev/agp/agpreg.h tank/src@2013-01-17:/sys/dev/isci/scil/scic_sds_remote_node_context.h tank/src@2013-01-17:/.svn/pristine/a8/a8dfc65edca368c5d2af3d655859f25150795bc5.svn-base tank/src@2013-01-17:/contrib/llvm/utils/TableGen/DAGISelMatcher.cpp tank/src@2013-01-17:/contrib/tcpdump/print-babel.c tank/src@2013-01-17:/.svn/pristine/30/30ef0f53aa09a5185f55f4ecac842dbc13dab8fd.svn-base tank/src@2013-01-17:/.svn/pristine/cb/cb32411a6873621a449b24d9127305b2ee6630e9.svn-base tank/src@2013-01-17:/.svn/pristine/03/030d211b1e95f703f9a61201eed63efdbb8e41c0.svn-base tank/src@2013-01-17:/.svn/pristine/27/27f1181d33434a72308de165c04202b6159d6ac2.svn-base tank/src@2013-01-17:/lib/libpam/modules/pam_exec/pam_exec.c tank/src@2013-01-17:/contrib/llvm/include/llvm/PassSupport.h tank/src@2013-01-17:/.svn/pristine/90/90f818b5f897f26c7b301c1ac2d0ce0d3eaef28d.svn-base tank/src@2013-01-17:/sys/vm/vm_pager.c tank/src@2013-01-17:/.svn/pristine/5e/5e9331052e8c2e0fa5fd8c74c4edb04058e3b95f.svn-base tank/src@2013-01-17:/.svn/pristine/1d/1d5d6e75cfb77e48e4711ddd10148986392c4fae.svn-base tank/src@2013-01-17:/.svn/pristine/c5/c55e964c62ed759089c4bf5e49adf6e49eb59108.svn-base tank/src@2013-01-17:/crypto/openssl/crypto/cms/cms_lcl.h tank/ncvs@2013-01-17:/ports/textproc/uncrustify/distinfo,v Interestingly, these only seem to affect the snapshot, and I'm now wondering if that is the problem why the backup pool did not accept the next incremental snapshot from the new pool. How does the receiving pool known that it has the correct snapshot to store an incremental one anyway? Is there a toplevel checksum, like for git commits? How can I display and compare that? Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 10:14:34 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E27C6EA for ; Mon, 28 Jan 2013 10:14:34 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id ADC2287F for ; Mon, 28 Jan 2013 10:14:34 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r0SAEXI9010319 for ; Mon, 28 Jan 2013 02:14:33 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <51064F89.7020102@rawbw.com> Date: Mon, 28 Jan 2013 02:14:33 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 MIME-Version: 1.0 To: current@freebsd.org Subject: libproc buffer corruption patch Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 10:14:34 -0000 Please check in this obvious patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=175648 MFC to 9.X, please. Thanks, Yuri From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 10:29:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3CC0D4EA for ; Mon, 28 Jan 2013 10:29:41 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id B2C92999 for ; Mon, 28 Jan 2013 10:29:40 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0SATZgL031752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 28 Jan 2013 11:29:36 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Mon, 28 Jan 2013 11:29:35 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Hans Petter Selasky Subject: Re: Zpool surgery Message-ID: <20130128102935.GS35868@acme.spoerlein.net> Mail-Followup-To: Hans Petter Selasky , freebsd-current@freebsd.org References: <20130127103612.GB38645@acme.spoerlein.net> <20130127145601.7f650d3c@fabiankeil.de> <20130127190806.GQ35868@acme.spoerlein.net> <201301272013.24445.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201301272013.24445.hselasky@c2i.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 10:29:41 -0000 On Sun, 2013-01-27 at 20:13:24 +0100, Hans Petter Selasky wrote: > On Sunday 27 January 2013 20:08:06 Ulrich Spörlein wrote: > > I dug out an old ATA-to-USB case and will use that to attach the old > > tank to the new machine and then have a try at this zpool replace thing. > > If you are using -current you might want this patch first: > > http://svnweb.freebsd.org/changeset/base/245995 Thanks, will do. Is it supposed to fix this? root@coyote:~# geli attach da1 Segmentation fault Exit 139 root@coyote:~# geli status Name Status Components gpt/swap.eli ACTIVE gpt/swap da0.eli ACTIVE da0 ada1.eli ACTIVE ada1 As you can see geli worked fine, but at some point it stops working and can no longer attach new volumes. I'm also seeing interrupt storms for USB devices, when I plug in the drives into xhci0 instead of xhci1 (but this needs more testing, first I need to get that damn zpool moved) xhci0: mem 0xe0720000-0xe072ffff irq 21 at device 20.0 on pci0 xhci0: 32 byte context size. usbus0 on xhci0 xhci1: mem 0xe0500000-0xe050ffff,0xe0510000-0xe0511fff irq 19 at device 0.0 on pci5 xhci1: 64 byte context size. usbus2 on xhci1 xhci0@pci0:0:20:0: class=0x0c0330 card=0x72708086 chip=0x1e318086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '7 Series/C210 Series Chipset Family USB xHCI Host Controller' class = serial bus subclass = USB xhci1@pci0:5:0:0: class=0x0c0330 card=0x00000000 chip=0x8241104c rev=0x02 hdr=0x00 vendor = 'Texas Instruments' device = 'TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller' class = serial bus subclass = USB What's with the 32 vs 64 byte context size? And do you know of any problems with the Intel controller? Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 10:58:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8403CEA8; Mon, 28 Jan 2013 10:58:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id CB047B0C; Mon, 28 Jan 2013 10:58:37 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 205143302; Mon, 28 Jan 2013 11:58:34 +0100 From: Hans Petter Selasky To: Ulrich =?utf-8?q?Sp=C3=B6rlein?= Subject: Re: Zpool surgery Date: Mon, 28 Jan 2013 11:59:47 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <20130127103612.GB38645@acme.spoerlein.net> <201301272013.24445.hselasky@c2i.net> <20130128102935.GS35868@acme.spoerlein.net> In-Reply-To: <20130128102935.GS35868@acme.spoerlein.net> X-Face: ?p&W)c( =?iso-8859-1?q?+80hU=3B=27=7B=2E=245K+zq=7BoC6y=7C=0A=09/D=27an*6mw?=>j'f:eBsex\Gi, Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 10:58:38 -0000 On Monday 28 January 2013 11:29:35 Ulrich Sp=C3=B6rlein wrote: > What's with the 32 vs 64 byte context size? And do you know of any proble= ms > with the Intel controller? These are two different USB DMA descriptor layouts. =2D-HPS From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 10:59:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51332FB9; Mon, 28 Jan 2013 10:59:29 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id ACFF2B25; Mon, 28 Jan 2013 10:59:28 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 371369941; Mon, 28 Jan 2013 11:59:26 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: Zpool surgery Date: Mon, 28 Jan 2013 12:00:39 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; amd64; ; ) References: <20130127103612.GB38645@acme.spoerlein.net> <201301272013.24445.hselasky@c2i.net> <20130128102935.GS35868@acme.spoerlein.net> In-Reply-To: <20130128102935.GS35868@acme.spoerlein.net> X-Face: ?p&W)c( =?iso-8859-1?q?+80hU=3B=27=7B=2E=245K+zq=7BoC6y=7C=0A=09/D=27an*6mw?=>j'f:eBsex\Gi, X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 10:59:29 -0000 On Monday 28 January 2013 11:29:35 Ulrich Sp=C3=B6rlein wrote: > Thanks, will do. Is it supposed to fix this? >=20 > root@coyote:~# geli attach da1 > Segmentation fault > Exit 139 > root@coyote:~# geli status > Name Status Components > gpt/swap.eli ACTIVE gpt/swap > da0.eli ACTIVE da0 > ada1.eli ACTIVE ada1 >=20 >=20 > As you can see geli worked fine, but at some point it stops working and > can no longer attach new volumes. I don't know. If this doesn't happen on 9-stable, yes. =2D-HPS From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 11:11:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9E8092AE; Mon, 28 Jan 2013 11:11:23 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep12.mx.upcmail.net (fep12.mx.upcmail.net [62.179.121.32]) by mx1.freebsd.org (Postfix) with ESMTP id C2902ED5; Mon, 28 Jan 2013 11:11:22 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep12-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20130128111113.NJST2716.viefep12-int.chello.at@edge03.upcmail.net>; Mon, 28 Jan 2013 12:11:13 +0100 Received: from [192.168.1.62] ([95.96.229.21]) by edge03.upcmail.net with edge id tPAh1k0350ULilr03PB4vl; Mon, 28 Jan 2013 12:11:13 +0100 X-SourceIP: 95.96.229.21 Subject: Re: devel/gobject-introspection failure on ARM From: Koop Mast To: George Mitchell In-Reply-To: <51054E5F.9040309@m5p.com> References: <51054E5F.9040309@m5p.com> Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Jan 2013 11:55:08 +0100 Message-ID: <1359370508.15771.4.camel@oldtimer.rainbow-runner.nl> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 11:11:23 -0000 On Sun, 2013-01-27 at 10:57 -0500, George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > ports: svnversion 308518 > > Build dies with message "sizeof(ArrayTypeBlob) is expected to be 8 but > is 12." (Complete build log attached.) I made a naive attempt to fix > it by rearranging the order of the structure members, but obviously I > don't understand structure packing on the ARM and it didn't help. It > also didn't get rid of the huge number of "cast increases required > alignment of target type" warnings. > > I note we're at version 0.10.8 of this package, but upstream is at > 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). > > What's the best way to proceed? -- George Mitchell I'm currently in the process of making a patch [1] for the ports tree for glib 2.34.3 and gobject-introspection 1.34.1.1. If you want to give this a shot on ARM. Please note that the patch is WIP. Not all ports have been tested yet. -Koop [1] http://people.freebsd.org/~kwm/glib-2.34_1.diff From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 11:16:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42F68907; Mon, 28 Jan 2013 11:16:54 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) by mx1.freebsd.org (Postfix) with ESMTP id 68A2BF68; Mon, 28 Jan 2013 11:16:53 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r0SBGkcR012011; Mon, 28 Jan 2013 06:16:51 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <51065E1E.90202@m5p.com> Date: Mon, 28 Jan 2013 06:16:46 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120908 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: devel/gobject-introspection failure on ARM References: <51054E5F.9040309@m5p.com> <1359370508.15771.4.camel@oldtimer.rainbow-runner.nl> In-Reply-To: <1359370508.15771.4.camel@oldtimer.rainbow-runner.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Mon, 28 Jan 2013 06:16:51 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 11:16:54 -0000 On 01/28/13 05:55, Koop Mast wrote: > On Sun, 2013-01-27 at 10:57 -0500, George Mitchell wrote: >> System: Raspberry Pi >> uname: r245840M (Alie Tan's image from 25 January) >> ports: svnversion 308518 >> >> Build dies with message "sizeof(ArrayTypeBlob) is expected to be 8 but >> is 12." (Complete build log attached.) I made a naive attempt to fix >> it by rearranging the order of the structure members, but obviously I >> don't understand structure packing on the ARM and it didn't help. It >> also didn't get rid of the huge number of "cast increases required >> alignment of target type" warnings. >> >> I note we're at version 0.10.8 of this package, but upstream is at >> 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). >> >> What's the best way to proceed? -- George Mitchell > > I'm currently in the process of making a patch [1] for the ports tree > for glib 2.34.3 and gobject-introspection 1.34.1.1. If you want to give > this a shot on ARM. Please note that the patch is WIP. Not all ports > have been tested yet. > > -Koop > > [1] http://people.freebsd.org/~kwm/glib-2.34_1.diff Thanks! I'll try this if I have time later today. -- George From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 12:23:55 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33882994; Mon, 28 Jan 2013 12:23:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id E49C56BA; Mon, 28 Jan 2013 12:23:54 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 11D1A23F654; Mon, 28 Jan 2013 07:23:53 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.4 onyx.glenbarber.us 11D1A23F654 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Mon, 28 Jan 2013 07:23:51 -0500 From: Glen Barber To: Andriy Gapon Subject: Re: acpi resume related patch Message-ID: <20130128122351.GD1296@glenbarber.us> References: <510245B5.8070704@FreeBSD.org> <20130128025239.GA1296@glenbarber.us> <510633EB.9030306@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="x4pBfXISqBoDm8sr" Content-Disposition: inline In-Reply-To: <510633EB.9030306@FreeBSD.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 12:23:55 -0000 --x4pBfXISqBoDm8sr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 28, 2013 at 10:16:43AM +0200, Andriy Gapon wrote: > on 28/01/2013 04:52 Glen Barber said the following: > > On Fri, Jan 25, 2013 at 10:43:33AM +0200, Andriy Gapon wrote: > >> > >> If you have ACPI suspend/resume working, if it used to work but stoppe= d working > >> at some time, if it never worked, but you are still hoping, could you = please > >> test the following patch and report back? > >> > >> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch > >> > >=20 > > FWIW, I am (very happy) to report my laptop has resumed for longer than > > 10 seconds for the first time ever. >=20 > Just to clarify - you mean that previously it would try to shutdown right= after > resume? Or something else? >=20 Your description is probably the most accurate way to describe post-resume behavior. Glen --x4pBfXISqBoDm8sr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRBm3XAAoJEFJPDDeguUajx2MIAKPLpb0M8vLtJX11as/OszkC 5f95+I7xczvGkituuto3CLbgbDr8/JOCtjwAlAVrr3xx6RFNsFpVZ5HDxKspKoCX DxtXQdUkj1ETYGLWVwVielh4jo9lgawI44TLMkcSV6usyBbGtHe/Q/07CDExF+Mc ahGv8Tzbig1oZMoTuRMZz33mIs9noj4+fFd0yjTMVAKcslHxYh/OIKY5D0b11rD+ q9K0Xf1imm/y5HQjjEu0WdS1ifFbLTImPlLbdWLSRhmgih1IKyhMnFN8Y29K7yX8 w7cqnjGYUg95tUolURsIbZckw/J9PgJBom+yVknrAkWf8kfXVlc6ZmoXffrQI2k= =Mg/8 -----END PGP SIGNATURE----- --x4pBfXISqBoDm8sr-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 07:52:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8C2D4EE1 for ; Mon, 28 Jan 2013 07:52:56 +0000 (UTC) (envelope-from erich@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 3E383EFC for ; Mon, 28 Jan 2013 07:52:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:Message-ID:Subject:To:From:Date; bh=Elh37YJ0Y0ThG7WXg6mT3ncmwBl3xksxf59PrbbKYgg=; b=rXRQMXtgKkrnw8V1tSdy0CMFjN1KX6dbEklMPuPzZja9ioj5rspdPE1HXPMdQngSN7LfGZxeyb5760D8ZQR2QPaPp6gLnM9gzmyWyeRt6AuVkw3Fq7kmYlj5vNjmv1lG; Received: from [122.129.203.50] (port=33944 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1TzjWQ-001klh-Rg for freebsd-current@freebsd.org; Mon, 28 Jan 2013 00:52:55 -0700 Date: Mon, 28 Jan 2013 14:52:51 +0700 From: Erich Dollansky To: Subject: FreeBSD 10, booting from USB failes Message-ID: <20130128145251.059fb970@X220.ovitrap.com> Organization: ALO Green Technologies X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erich@alogt.com X-Source: X-Source-Args: X-Source-Dir: X-Mailman-Approved-At: Mon, 28 Jan 2013 12:38:01 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 07:52:56 -0000 Hi, I have several thumb drives and had disks. To be able to exchange the hard disks, all devices are bootable. I have tested the setup some time ago and it did not give me problems to boot from the external media via USB. I will take two hard disks as an example: => 63 976773105 ada0 MBR (465G) 63 1953 - free - (976k) 2016 976771152 1 freebsd (465G) => 0 976771152 ada0s1 BSD (465G) 0 10240000 1 freebsd-ufs (4.9G) 10240000 32768000 2 freebsd-swap (15G) 43008000 10240000 4 freebsd-ufs (4.9G) 53248000 10240000 5 freebsd-ufs (4.9G) 63488000 102400000 6 freebsd-ufs (48G) 165888000 810883144 7 freebsd-ufs (386G) 976771144 8 - free - (4.0k) => 34 976773098 da0 GPT (465G) 34 128 1 freebsd-boot (64k) 162 6 - free - (3.0k) 168 10485760 2 freebsd-ufs (5.0G) 10485928 33554432 3 freebsd-swap (16G) 44040360 10485760 4 freebsd-ufs (5.0G) 54526120 10485760 5 freebsd-ufs (5.0G) 65011880 104857600 6 freebsd-ufs (50G) 169869480 806903648 7 freebsd-ufs (384G) 976773128 4 - free - (2.0k) The system started from ada0. It fails to start from da0 now. Before I switch the disks, does anybody know of something which causes the problem? If this matters, I did this with an X220 ThinkPad. Erich From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 12:44:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4B88FE54; Mon, 28 Jan 2013 12:44:25 +0000 (UTC) (envelope-from bland@freebsd.org) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 1AE977E7; Mon, 28 Jan 2013 12:44:25 +0000 (UTC) Received: from eee.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 6CD4E1A1B5; Mon, 28 Jan 2013 21:44:23 +0900 (JST) Received: from nest.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) (authenticated bits=0) by eee.bbnest.net (8.14.6/8.14.5) with ESMTP id r0SCiBtx001328 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 28 Jan 2013 21:44:13 +0900 (JST) (envelope-from bland@freebsd.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: ZFS + usb in trouble? [PATCHED] From: Alexander Nedotsukov In-Reply-To: <201301271905.41150.hselasky@c2i.net> Date: Mon, 28 Jan 2013 21:44:13 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201301271715.02607.hselasky@c2i.net> <201301271727.43074.hselasky@c2i.net> <201301271905.41150.hselasky@c2i.net> To: Hans Petter Selasky X-Mailer: Apple Mail (2.1499) X-DSPAM-Result: Innocent X-DSPAM-Processed: Mon Jan 28 21:44:22 2013 X-DSPAM-Confidence: 0.9995 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 510672a613292140831274 Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 12:44:25 -0000 Roger. This is it. Thanks! On 28.01.2013, at 3:05, Hans Petter Selasky wrote: > Hi, >=20 > Can you try this patch: >=20 > http://svnweb.freebsd.org/changeset/base/245995 >=20 > It fixes the issue for me. Looks like I overlooked a corner case = computing the=20 > DMA addresses. Thanks for reporting! >=20 > zpool status > pool: tank > state: ONLINE > scan: none requested > config: >=20 > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > da0 ONLINE 0 0 0 > da1 ONLINE 0 0 0 > da2 ONLINE 0 0 0 >=20 > errors: No known data errors >=20 >=20 > --HPS > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 12:44:31 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F0AA9F7B; Mon, 28 Jan 2013 12:44:31 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id BD02D7EA; Mon, 28 Jan 2013 12:44:31 +0000 (UTC) Received: from localhost (dlt174.neoplus.adsl.tpnet.pl [83.24.49.174]) by mail.dawidek.net (Postfix) with ESMTPSA id F0CDBDE9; Mon, 28 Jan 2013 13:41:45 +0100 (CET) Date: Mon, 28 Jan 2013 13:45:05 +0100 From: Pawel Jakub Dawidek To: Andriy Gapon Subject: Re: acpi resume related patch Message-ID: <20130128124505.GA1361@garage.freebsd.pl> References: <510245B5.8070704@FreeBSD.org> <201301250851.25243.jhb@freebsd.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <5103E5D1.3070808@FreeBSD.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 12:44:32 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 26, 2013 at 04:18:57PM +0200, Andriy Gapon wrote: > on 25/01/2013 18:08 Andriy Gapon said the following: > > on 25/01/2013 15:51 John Baldwin said the following: > >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: > >>> > >>> If you have ACPI suspend/resume working, if it used to work but stopp= ed working > >>> at some time, if it never worked, but you are still hoping, could you= please > >>> test the following patch and report back? > >>> > >>> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch > >> > >> This will break systems not using the local APIC since you uncondition= ally > >> call lapic_setup() on resume.This was part of the feature of the previ= ous > >> code that by using a dummy pic it could register it only when the loca= l APIC > >> was used. > >=20 > > Thank you for drawing my attention to this. I will try to fix this iss= ue. > > The reason I want to remove lapic from 'pics' (and I already described = it in a > > private email) is that Local APIC is a special kind of PIC. It's alrea= dy > > explicitly initialized by APs. Putting it into 'pics' tailq just obfus= cates the code. > >=20 > >> It should also be registered before any of the I/O APICs are by > >> the design of the local_apic.c code. > >=20 > > In fact, as I see in the code, Local APIC is always registered _after_ = I/O APICs. > > And thus lapic_resume was called after ioapic_resume. > > Additionally, currently there is no synchronization between initializat= ion of > > Local APICs on APs and initialization of I/O APICs at the wakeup/resume= time. > >=20 >=20 > Here is an updated version of the patch: > http://people.freebsd.org/~avg/acpi-apic-wakeup.2.patch FYI, it doesn't change anything for me. Resume seems to work, but suspend just reset my laptop. I unload all driver modules (including if_em, sound, nvidia, usb). The only driver I keep is ahci. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEGctEACgkQForvXbEpPzRAEACg8wl3lXy0VJAPofdZLnHFs0+6 +TAAn1wxys7UTovNR+OJnCLGXLzvd2qr =5yct -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 13:08:07 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B71A0DEB; Mon, 28 Jan 2013 13:08:07 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id AF7C6986; Mon, 28 Jan 2013 13:08:06 +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 PAA00786; Mon, 28 Jan 2013 15:07:59 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5106782F.5040102@FreeBSD.org> Date: Mon, 28 Jan 2013 15:07:59 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130113 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: acpi resume related patch References: <510245B5.8070704@FreeBSD.org> <201301250851.25243.jhb@freebsd.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> <20130128124505.GA1361@garage.freebsd.pl> In-Reply-To: <20130128124505.GA1361@garage.freebsd.pl> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 13:08:07 -0000 on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > FYI, it doesn't change anything for me. Resume seems to work, but > suspend just reset my laptop. Sorry, I am a little confused by this description. How can you know that resume works if suspend resets the machine? -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 13:24:17 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 77DC23B0; Mon, 28 Jan 2013 13:24:17 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 3E1E9A64; Mon, 28 Jan 2013 13:24:16 +0000 (UTC) Received: from localhost (dlt174.neoplus.adsl.tpnet.pl [83.24.49.174]) by mail.dawidek.net (Postfix) with ESMTPSA id F018FE10; Mon, 28 Jan 2013 14:21:37 +0100 (CET) Date: Mon, 28 Jan 2013 14:24:57 +0100 From: Pawel Jakub Dawidek To: Andriy Gapon Subject: Re: acpi resume related patch Message-ID: <20130128132457.GB1361@garage.freebsd.pl> References: <510245B5.8070704@FreeBSD.org> <201301250851.25243.jhb@freebsd.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> <20130128124505.GA1361@garage.freebsd.pl> <5106782F.5040102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qcHopEYAB45HaUaB" Content-Disposition: inline In-Reply-To: <5106782F.5040102@FreeBSD.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 13:24:17 -0000 --qcHopEYAB45HaUaB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: > on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > > FYI, it doesn't change anything for me. Resume seems to work, but > > suspend just reset my laptop. >=20 > Sorry, I am a little confused by this description. > How can you know that resume works if suspend resets the machine? Because everything turns off, including display and the power led starts to "throb" and it does that until I try to resume it. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --qcHopEYAB45HaUaB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEGfCkACgkQForvXbEpPzSRIQCg1otZoYQ8dhKn7NTFyvpikluj bZAAnA2pPvHH6SVnmUQBrVCPboScuqj9 =SPwO -----END PGP SIGNATURE----- --qcHopEYAB45HaUaB-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 13:40:21 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9A34D74B; Mon, 28 Jan 2013 13:40:21 +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 A8615B17; Mon, 28 Jan 2013 13:40:20 +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 PAA01062; Mon, 28 Jan 2013 15:40:19 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <51067FC2.7010904@FreeBSD.org> Date: Mon, 28 Jan 2013 15:40:18 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130113 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: acpi resume related patch References: <510245B5.8070704@FreeBSD.org> <201301250851.25243.jhb@freebsd.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> <20130128124505.GA1361@garage.freebsd.pl> <5106782F.5040102@FreeBSD.org> <20130128132457.GB1361@garage.freebsd.pl> In-Reply-To: <20130128132457.GB1361@garage.freebsd.pl> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 13:40:21 -0000 on 28/01/2013 15:24 Pawel Jakub Dawidek said the following: > On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: >> on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: >>> FYI, it doesn't change anything for me. Resume seems to work, but >>> suspend just reset my laptop. >> >> Sorry, I am a little confused by this description. >> How can you know that resume works if suspend resets the machine? > > Because everything turns off, including display and the power led starts > to "throb" and it does that until I try to resume it. > Ah, so "suspend" and "resume" got accidentally reverted... I see, thank you for the report. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 13:51:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D4DCC2D; Mon, 28 Jan 2013 13:51:01 +0000 (UTC) (envelope-from ray@ddteam.net) Received: from smtp.dlink.ua (smtp.dlink.ua [193.138.187.146]) by mx1.freebsd.org (Postfix) with ESMTP id 36F14C0F; Mon, 28 Jan 2013 13:51:01 +0000 (UTC) Received: from terran (unknown [192.168.99.1]) (Authenticated sender: ray) by smtp.dlink.ua (Postfix) with ESMTPSA id 8C38BC4947; Mon, 28 Jan 2013 15:50:59 +0200 (EET) Date: Mon, 28 Jan 2013 15:52:45 +0200 From: Aleksandr Rybalko To: George Mitchell Subject: Re: devel/gobject-introspection failure on ARM Message-Id: <20130128155245.d28dd0f6dc60c061757907fc@ddteam.net> In-Reply-To: <51054E5F.9040309@m5p.com> References: <51054E5F.9040309@m5p.com> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 13:51:01 -0000 On Sun, 27 Jan 2013 10:57:19 -0500 George Mitchell wrote: > System: Raspberry Pi > uname: r245840M (Alie Tan's image from 25 January) > ports: svnversion 308518 > > Build dies with message "sizeof(ArrayTypeBlob) is expected to be 8 but > is 12." (Complete build log attached.) I made a naive attempt to fix > it by rearranging the order of the structure members, but obviously I > don't understand structure packing on the ARM and it didn't help. It > also didn't get rid of the huge number of "cast increases required > alignment of target type" warnings. > > I note we're at version 0.10.8 of this package, but upstream is at > 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). > > What's the best way to proceed? -- George Mitchell Hi, It can be fixed by just change gitypelib.c: CHECK_SIZE (ArrayTypeBlob, 8); to gitypelib.c: CHECK_SIZE (ArrayTypeBlob, 12); But problem not in gobject-introspection, but in old ARM ABI. I was ask andrew@, and he test it with ARM EABI, and it compiled fine with size 8. So if somebody will fix it, please #ifdef that fix to make it only with old ARM ABI. Or, better help with EABI testing :-D Thanks! WBW -- Aleksandr Rybalko From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 13:57:18 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1124CF31; Mon, 28 Jan 2013 13:57:18 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id C1153CE8; Mon, 28 Jan 2013 13:57:17 +0000 (UTC) Received: from localhost (dlt174.neoplus.adsl.tpnet.pl [83.24.49.174]) by mail.dawidek.net (Postfix) with ESMTPSA id 66734E35; Mon, 28 Jan 2013 14:54:38 +0100 (CET) Date: Mon, 28 Jan 2013 14:57:58 +0100 From: Pawel Jakub Dawidek To: Andriy Gapon Subject: Re: acpi resume related patch Message-ID: <20130128135757.GC1361@garage.freebsd.pl> References: <510245B5.8070704@FreeBSD.org> <201301250851.25243.jhb@freebsd.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> <20130128124505.GA1361@garage.freebsd.pl> <5106782F.5040102@FreeBSD.org> <20130128132457.GB1361@garage.freebsd.pl> <51067FC2.7010904@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i7F3eY7HS/tUJxUd" Content-Disposition: inline In-Reply-To: <51067FC2.7010904@FreeBSD.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 13:57:18 -0000 --i7F3eY7HS/tUJxUd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 28, 2013 at 03:40:18PM +0200, Andriy Gapon wrote: > on 28/01/2013 15:24 Pawel Jakub Dawidek said the following: > > On Mon, Jan 28, 2013 at 03:07:59PM +0200, Andriy Gapon wrote: > >> on 28/01/2013 14:45 Pawel Jakub Dawidek said the following: > >>> FYI, it doesn't change anything for me. Resume seems to work, but > >>> suspend just reset my laptop. > >> > >> Sorry, I am a little confused by this description. > >> How can you know that resume works if suspend resets the machine? > >=20 > > Because everything turns off, including display and the power led starts > > to "throb" and it does that until I try to resume it. > >=20 >=20 > Ah, so "suspend" and "resume" got accidentally reverted... > I see, thank you for the report. I just noticed that, yes, sorry. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --i7F3eY7HS/tUJxUd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEGg+UACgkQForvXbEpPzTFNgCgzs/Jjo0fwEilhLrPqUH9/ae5 Wo4AoNiu6SPihjWwesanxpFIZHLtgZan =mXQG -----END PGP SIGNATURE----- --i7F3eY7HS/tUJxUd-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 14:23:11 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EC7AE5AC; Mon, 28 Jan 2013 14:23:11 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id AC4C8E0B; Mon, 28 Jan 2013 14:23:10 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0SENAx7046060; Mon, 28 Jan 2013 07:23:10 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0SEMmAo020875; Mon, 28 Jan 2013 07:22:48 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: Trouble with recent auto-tuning changes From: Ian Lepore To: alc@FreeBSD.org In-Reply-To: References: <1359310302.93359.48.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Jan 2013 07:22:48 -0700 Message-ID: <1359382968.93359.66.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 14:23:12 -0000 On Mon, 2013-01-28 at 00:09 -0600, Alan Cox wrote: > On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: > > > I ran into a panic while attempting to un-tar a large file on a > > DreamPlug (arm-based system) running -current. The source and dest of > > the un-tar is the root filesystem on sdcard, and I get this: > > > > panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated > > > > Just before the panic I see the tar process get hung in a "nokva" wait. > > 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. > > > > In r245575 the init order for mbuf limits was changed from > > SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the > > results of sizing kernel memory. Unfortunately, the process of sizing > > kernel memory relies on the mbuf limits; in kmeminit(): > > > > vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; > > > > Since r245575, nmbclusters is zero when this line of code runs. If I > > manually plugin "32768" (the number tunable_mbinit() comes up with for > > this platform) in that line, the panic stops happening. > > > > So we've got two problems here... one is the circular dependency in > > calculating the mbuf limits. The other is the fact that some > > non-trivial amount of kernel memory we're allowing for mbufs is actually > > being used for other things. That is, if my system was actually using > > all the mbufs that tunable_mbinit() allowed for, then this panic while > > untarring a huge file would still have happened. > > > > > All of this is factually correct. However, it's a red herring. The real > problem is that arm, unlike every other architecture in the tree, does not > enable auto-sizing of the kmem map based on the physical memory size. > Specifically, you'll find VM_KMEM_SIZE_SCALE defined in > "arch"/include/vmparam.h on every other architecture, just not on arm. > This auto-sizing overrides the value of VM_KMEM_SIZE. > Aha. I'll investigate what other architectures do with that and try to get the same thing going for arm. -- Ian > > > > I arrive at the latter conclusion based on the fact that this panic > > happens even if no network interfaces (other than lo0) are configured. > > That is, nmbclusters == 0 is a reasonable approximation of my need for > > network mbufs. So something in the system needs to be taken into > > account when sizing kernel memory to allow for whatever it is about > > untarring a huge file that eats kernel memory (buffer cache?). > > > > I can easily reproduce this if you need me to gather any specific info. > > > > -- Ian > > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:13:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9A771CE6 for ; Mon, 28 Jan 2013 15:13:54 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 3F68E230 for ; Mon, 28 Jan 2013 15:13:53 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,551,1355126400"; d="scan'208";a="13011365" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 28 Jan 2013 07:13:47 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0SFDkda018562 for ; Mon, 28 Jan 2013 07:13:47 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Mon, 28 Jan 2013 07:13:45 -0800 From: "Eggert, Lars" To: "freebsd-current@freebsd.org" Subject: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3A== Date: Mon, 28 Jan 2013 15:13:44 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <1BD0C6361EBA6146BDD9332C516FA563@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:13:54 -0000 Hi, I'm trying to netboot a system where the root device is specified in the ke= rnel via ROOTDEVNAME: options BOOTP options BOOTP_NFSROOT options BOOTP_NFSV3 options BOOTP_COMPAT options BOOTP_WIRED_TO=3Dem4 options ROOTDEVNAME=3D\"nfs:10.11.12.13:/usr/home/elars/dst\" I was under the assumption that specifying a ROOTDEVNAME in the kernel conf= ig would override the "root-path" option in DHCP, or at least take effect w= hen "root-path" wasn't provided via DHCP, but that doesn't seem to be the c= ase. The system configures it's address correctly over em4, but then enters= a loop: em4: link state changed to UP Received DHCP Offer packet on em4 from 0.0.0.0 (accepted) (no root path) Sending DHCP Request packet from interface em4 (XX:XX:XX:XX:XX:XX) Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 ... If I hand out a root path via DHCP the system boots fine, but the idea here= is to be able to boot different root devices without needing to diddle dhc= pd.conf. Can this be done? Thanks, Lars= From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:24:17 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 18FD8149 for ; Mon, 28 Jan 2013 15:24:17 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0CD2C9 for ; Mon, 28 Jan 2013 15:24:04 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0SFO3qI046766 for ; Mon, 28 Jan 2013 08:24:04 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0SFNfHX020914; Mon, 28 Jan 2013 08:23:41 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: mounting root from NFS via ROOTDEVNAME From: Ian Lepore To: "Eggert, Lars" In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Jan 2013 08:23:41 -0700 Message-ID: <1359386621.93359.87.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:24:17 -0000 On Mon, 2013-01-28 at 15:13 +0000, Eggert, Lars wrote: > Hi, > > I'm trying to netboot a system where the root device is specified in the kernel via ROOTDEVNAME: > > options BOOTP > options BOOTP_NFSROOT > options BOOTP_NFSV3 > options BOOTP_COMPAT > options BOOTP_WIRED_TO=em4 > options ROOTDEVNAME=\"nfs:10.11.12.13:/usr/home/elars/dst\" > > I was under the assumption that specifying a ROOTDEVNAME in the kernel config would override the "root-path" option in DHCP, or at least take effect when "root-path" wasn't provided via DHCP, but that doesn't seem to be the case. The system configures it's address correctly over em4, but then enters a loop: > > em4: link state changed to UP > Received DHCP Offer packet on em4 from 0.0.0.0 (accepted) (no root path) > Sending DHCP Request packet from interface em4 (XX:XX:XX:XX:XX:XX) > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > DHCP/BOOTP timeout for server 255.255.255.255 > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > DHCP/BOOTP timeout for server 255.255.255.255 > ... > > If I hand out a root path via DHCP the system boots fine, but the idea here is to be able to boot different root devices without needing to diddle dhcpd.conf. Can this be done? Remove the BOOTP_NFSROOT option, it tells the bootp/dhcp code to keep querying the server until a root path is delivered. Without it, the ROOTDEVNAME option should get used (and I think even override a path from the server, if it delivers one). -- Ian From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:45:26 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30513ABD for ; Mon, 28 Jan 2013 15:45:26 +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 BE0A96A0 for ; Mon, 28 Jan 2013 15:45:25 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r0SFjHnl059510; Mon, 28 Jan 2013 16:45:17 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r0SFjHKJ059509; Mon, 28 Jan 2013 16:45:17 +0100 (CET) (envelope-from marius) Date: Mon, 28 Jan 2013 16:45:17 +0100 From: Marius Strobl To: Konstantin Belousov Subject: Re: Fast gettimeofday(2) and static linking Message-ID: <20130128154516.GA59472@alchemy.franken.de> References: <20130125123554.GQ2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130125123554.GQ2522@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:45:26 -0000 On Fri, Jan 25, 2013 at 02:35:54PM +0200, Konstantin Belousov wrote: > Bruce Evans reported that statically linked binaries on HEAD an stable/9 > use the syscall for gettimeofday(2) and clock_gettime(2). Apparently, this > is due to my use of the weak reference to the __vdso* symbols in the > libc implementations. > > Patch below reworks the __vdso* attributes to only make the symbols > weak, but keep the references strong. Since I have to add a stub for > each architecture, I would like to ask non-x86 machines owners to test > the patch. > Hi Konstantin, what's the appropriate way to test this? Marius From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:48:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C8424C39; Mon, 28 Jan 2013 15:48:08 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id A1DE36DB; Mon, 28 Jan 2013 15:48:08 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,551,1355126400"; d="scan'208";a="13032276" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 28 Jan 2013 07:48:02 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0SFm2fW027118; Mon, 28 Jan 2013 07:48:02 -0800 (PST) Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht02-prd.hq.netapp.com (10.106.76.240) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 28 Jan 2013 07:48:02 -0800 Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.02.0328.009; Mon, 28 Jan 2013 07:48:02 -0800 From: "Eggert, Lars" To: Ian Lepore Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhfYi+AgAAGzYA= Date: Mon, 28 Jan 2013 15:48:01 +0000 Message-ID: References: <1359386621.93359.87.camel@revolution.hippie.lan> In-Reply-To: <1359386621.93359.87.camel@revolution.hippie.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <5C5C6D446995C54489A5D1B3F87B1633@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:48:08 -0000 Hi, On Jan 28, 2013, at 16:23, Ian Lepore wrote: > Remove the BOOTP_NFSROOT option, it tells the bootp/dhcp code to keep > querying the server until a root path is delivered. Without it, the > ROOTDEVNAME option should get used (and I think even override a path > from the server, if it delivers one). no luck: em4: link state changed to UP Received DHCP Offer packet on em4 from 0.0.0.0 (accepted) (no root path) Sending DHCP Request packet from interface em4 (XX:XX:XX:XX:XX:XX) Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 ... The only visible difference is that the first "Received DHCP Ack packet" li= ne is now printed only once, instead of twice as in the previous log. Lars= From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:55:35 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1C98F2AC for ; Mon, 28 Jan 2013 15:55:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8B83877B for ; Mon, 28 Jan 2013 15:55:34 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r0SFtOMg084703; Mon, 28 Jan 2013 17:55:24 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r0SFtOMg084703 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r0SFtOTN084702; Mon, 28 Jan 2013 17:55:24 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 28 Jan 2013 17:55:24 +0200 From: Konstantin Belousov To: Marius Strobl Subject: Re: Fast gettimeofday(2) and static linking Message-ID: <20130128155524.GS2522@kib.kiev.ua> References: <20130125123554.GQ2522@kib.kiev.ua> <20130128154516.GA59472@alchemy.franken.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C4uhv81ga6KxT6iz" Content-Disposition: inline In-Reply-To: <20130128154516.GA59472@alchemy.franken.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 15:55:35 -0000 --C4uhv81ga6KxT6iz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 28, 2013 at 04:45:17PM +0100, Marius Strobl wrote: > On Fri, Jan 25, 2013 at 02:35:54PM +0200, Konstantin Belousov wrote: > > Bruce Evans reported that statically linked binaries on HEAD an stable/9 > > use the syscall for gettimeofday(2) and clock_gettime(2). Apparently, t= his > > is due to my use of the weak reference to the __vdso* symbols in the > > libc implementations. > >=20 > > Patch below reworks the __vdso* attributes to only make the symbols > > weak, but keep the references strong. Since I have to add a stub for > > each architecture, I would like to ask non-x86 machines owners to test > > the patch. > >=20 >=20 > Hi Konstantin, >=20 > what's the appropriate way to test this? Please rebuild the world with the patch and check that gettimeofday(2) still works on your architecture, both for the static and dynamic binaries. I think that just booting multiuser is enough. --C4uhv81ga6KxT6iz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRBp9rAAoJEJDCuSvBvK1B1X8P/jPvPKfeInlIFAqtiSysjdes IVru+ZxJQPZu8nBJfg36vlCVbmj8B5d1fyEyrsd1RvgWYjpgJOaBQc3PtCvDpBgs r7ubus2aQjMkN+lxU0eHSv3KLua8e1KO2L7mJZ1eU0yzVCAuDn8FMN1/QIQBUpoo MJvgBeA2dlBHAiKr9/34vPhCtATq0dBlKY0lJK3QkSWE1MBQW9WaBsjkBf1XuHZr pk3gB/Qv4F7VYyItym96msGQi/U7nUl4l34f2pRrokPApeD6O26yp4v7ugVG6jTj ixXp8kjGD1bitHrD1aY7UVrfDvzAXSDPgwcHqsDfrHFxobypc+3Q1DgEm0PotkGX Ojuno21iCvJIxuvqjCHqbviRSLZVhRIO5mQuXIFfpZRZvFFrDZlh+rzILmVG+2NJ YvmAgVYBReIEZlxd35ptVihmk/RQwkYzjeYxGIgeYKoumdShKQAueIgRlID6V/yL GQrPwiNphyuVVNfVXhlUuUaYovoen/CeofigAbSa4n7Hwvdm/kk5q8/o5KAfsdjM 9pBbb2De0vM7ofZcXYGPjdhvNNrjGHWQ+v/Y71zAnZpz6RJZfVNA/BtlWYMN9lTA K9qIpWteXe1apqpLqk7kPNiSrVJNfwBh9KCbLs0RndEfOAkjkUKXTzcK8mJc8Fa+ 1x28vWDLHfX+McO+9508 =ffUX -----END PGP SIGNATURE----- --C4uhv81ga6KxT6iz-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 18:58:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1039C21D; Mon, 28 Jan 2013 18:58:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E238825D; Mon, 28 Jan 2013 18:58:16 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 51DC2B953; Mon, 28 Jan 2013 13:58:16 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: some questions on kern_linker and pre-loaded modules Date: Mon, 28 Jan 2013 10:40:38 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <5103C361.6060605@FreeBSD.org> In-Reply-To: <5103C361.6060605@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201301281040.38727.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 28 Jan 2013 13:58:16 -0500 (EST) Cc: freebsd-hackers@freebsd.org, Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 18:58:17 -0000 On Saturday, January 26, 2013 6:52:01 am Andriy Gapon wrote: > > I. > It seems that linker_preload checks a module for being a duplicate module only > if the module has MDT_VERSION. > > This is probably designed to allow different version of the same module to > co-exist (for some definition of co-exist)? Yes, that is likely true, but it is a bit dubious. > But, OTOH, this doesn't work well if the module is version-less (no > MODULE_VERSION in the code) and is pre-loaded twice (e.g. once in kernel and > once in a preloaded file). Yes. > At present a good example of this is zfsctrl module, which could be present both > in kernel (options ZFS) and in zfs.ko. > > I haven't thought about any linker-level resolution for this issue. > I've just tried a plug the ZFS hole for now. I think we should require all modules declared by DECLARE_MODULE() to have a version. You might be able to enforce that by failing to register a linker file if it contains any modules that do not include at least one version metadata note in the same linker file. You could check this before running the MOD_LOAD handlers (though after running SYSINITs). Truly fixing this would mean making module data true metadata that is parsed by the linker rather than having it all provided to the kernel via SYSINITs so that you could evaluate this before running SYSINITs. That is a larger project however. I think your fix for zfsctrl is correct. > II. > It seems that linker_file_register_modules() for the kernel is called after > linker_file_register_modules() is called for all the pre-loaded files. > linker_file_register_modules() for the kernel is called from > linker_init_kernel_modules via SYSINIT(SI_SUB_KLD, SI_ORDER_ANY) and that > happens after linker_preload() which is executed via SYSINIT(SI_SUB_KLD, > SI_ORDER_MIDDLE). > > Perhaps this is designed to allow modules in the preloaded files to override > modules compiled into the kernel? Yes, likely so. > But this doesn't seem to work well. > Because modules from the kernel are not registered yet, > linker_file_register_modules() would be successful for the duplicate modules in > a preloaded file and thus any sysinits present in the file will also be registered. > So, if the module is present both in the kernel and in the preloaded file and > the module has a module event handler (modeventhand_t), then the handler will > registered and called twice. Yes, I think it is too hard at present to safely allow a linker file to override the same module in a kernel, so the duplicate linker file should just be rejected entirely. I'm not sure if your change is completely correct for that. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 18:58:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33250492; Mon, 28 Jan 2013 18:58:30 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 12E93273; Mon, 28 Jan 2013 18:58:30 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 786AAB9A0; Mon, 28 Jan 2013 13:58:29 -0500 (EST) From: John Baldwin To: Andriy Gapon Subject: Re: acpi resume related patch Date: Mon, 28 Jan 2013 13:55:31 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <510245B5.8070704@FreeBSD.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> In-Reply-To: <5103E5D1.3070808@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201301281355.31601.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 28 Jan 2013 13:58:29 -0500 (EST) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 18:58:30 -0000 On Saturday, January 26, 2013 9:18:57 am Andriy Gapon wrote: > on 25/01/2013 18:08 Andriy Gapon said the following: > > on 25/01/2013 15:51 John Baldwin said the following: > >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: > >>> > >>> If you have ACPI suspend/resume working, if it used to work but stopped working > >>> at some time, if it never worked, but you are still hoping, could you please > >>> test the following patch and report back? > >>> > >>> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch > >> > >> This will break systems not using the local APIC since you unconditionally > >> call lapic_setup() on resume.This was part of the feature of the previous > >> code that by using a dummy pic it could register it only when the local APIC > >> was used. > > > > Thank you for drawing my attention to this. I will try to fix this issue. > > The reason I want to remove lapic from 'pics' (and I already described it in a > > private email) is that Local APIC is a special kind of PIC. It's already > > explicitly initialized by APs. Putting it into 'pics' tailq just obfuscates the code. > > > >> It should also be registered before any of the I/O APICs are by > >> the design of the local_apic.c code. > > > > In fact, as I see in the code, Local APIC is always registered _after_ I/O APICs. > > And thus lapic_resume was called after ioapic_resume. > > Additionally, currently there is no synchronization between initialization of > > Local APICs on APs and initialization of I/O APICs at the wakeup/resume time. > > > > Here is an updated version of the patch: > http://people.freebsd.org/~avg/acpi-apic-wakeup.2.patch > > John, > could you please review the PIC-related part? I decided to go back to the > current approach while fixing the suspend/resume ordering and also order of > registration for Local APIC. Must say that XEN special casing makes > apic_setup_io a little bit untidy. > > Additionally this patch fixes AP Local APIC initialization ordering on i386. > In the original patch I changed only amd64 code. This looks good to me. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 19:20:45 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 62BFD526; Mon, 28 Jan 2013 19:20:45 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh1.mail.rice.edu (mh1.mail.rice.edu [128.42.201.20]) by mx1.freebsd.org (Postfix) with ESMTP id 2B41D67E; Mon, 28 Jan 2013 19:20:45 +0000 (UTC) Received: from mh1.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh1.mail.rice.edu (Postfix) with ESMTP id 8F76A4601E3; Mon, 28 Jan 2013 13:20:38 -0600 (CST) Received: from mh1.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh1.mail.rice.edu (Postfix) with ESMTP id 8DE88460172; Mon, 28 Jan 2013 13:20:38 -0600 (CST) X-Virus-Scanned: by amavis-2.7.0 at mh1.mail.rice.edu, auth channel Received: from mh1.mail.rice.edu ([127.0.0.1]) by mh1.mail.rice.edu (mh1.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id v4gHhvJd-nor; Mon, 28 Jan 2013 13:20:38 -0600 (CST) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh1.mail.rice.edu (Postfix) with ESMTPSA id 0BD684601D7; Mon, 28 Jan 2013 13:20:37 -0600 (CST) Message-ID: <5106CF85.8060004@rice.edu> Date: Mon, 28 Jan 2013 13:20:37 -0600 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130127 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Trouble with recent auto-tuning changes References: <1359310302.93359.48.camel@revolution.hippie.lan> <1359382968.93359.66.camel@revolution.hippie.lan> In-Reply-To: <1359382968.93359.66.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: alc@FreeBSD.org, freebsd-current@FreeBSD.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 19:20:45 -0000 On 01/28/2013 08:22, Ian Lepore wrote: > On Mon, 2013-01-28 at 00:09 -0600, Alan Cox wrote: >> On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: >> >>> I ran into a panic while attempting to un-tar a large file on a >>> DreamPlug (arm-based system) running -current. The source and dest of >>> the un-tar is the root filesystem on sdcard, and I get this: >>> >>> panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated >>> >>> Just before the panic I see the tar process get hung in a "nokva" wait. >>> 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. >>> >>> In r245575 the init order for mbuf limits was changed from >>> SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the >>> results of sizing kernel memory. Unfortunately, the process of sizing >>> kernel memory relies on the mbuf limits; in kmeminit(): >>> >>> vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; >>> >>> Since r245575, nmbclusters is zero when this line of code runs. If I >>> manually plugin "32768" (the number tunable_mbinit() comes up with for >>> this platform) in that line, the panic stops happening. >>> >>> So we've got two problems here... one is the circular dependency in >>> calculating the mbuf limits. The other is the fact that some >>> non-trivial amount of kernel memory we're allowing for mbufs is actually >>> being used for other things. That is, if my system was actually using >>> all the mbufs that tunable_mbinit() allowed for, then this panic while >>> untarring a huge file would still have happened. >>> >>> >> All of this is factually correct. However, it's a red herring. The real >> problem is that arm, unlike every other architecture in the tree, does not >> enable auto-sizing of the kmem map based on the physical memory size. >> Specifically, you'll find VM_KMEM_SIZE_SCALE defined in >> "arch"/include/vmparam.h on every other architecture, just not on arm. >> This auto-sizing overrides the value of VM_KMEM_SIZE. >> > Aha. I'll investigate what other architectures do with that and try to > get the same thing going for arm. > i386 or (32-bit) MIPS would be the most similar. Also, I would encourage you to look for other definitions that those architectures have that arm doesn't. As physical memory sizes continue to grow on arm-based systems, they may require other changes in vmparam.h and the machine-dependent param.h that were made on those other architectures year ago. If you have any questions about any of the definitions, feel free to e-mail me. Alan P.S. When I get a little more free time, I intend to get in touch with Andre to address the apparent circular dependency. For now just know that unless that circular dependency is combined with a lack of kmem map auto-sizing, like arm, it's basically harmless. From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 20:04:51 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0F7E7138; Mon, 28 Jan 2013 20:04:51 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.29.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7D2D584A; Mon, 28 Jan 2013 20:04:50 +0000 (UTC) Received: from [78.35.168.72] (helo=fabiankeil.de) by smtprelay03.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1TzuwH-0001SW-MR; Mon, 28 Jan 2013 21:04:21 +0100 Date: Mon, 28 Jan 2013 20:58:02 +0100 From: Fabian Keil To: Ulrich =?UTF-8?B?U3DDtnJsZWlu?= Subject: Re: Zpool surgery Message-ID: <20130128205802.1ffab53e@fabiankeil.de> In-Reply-To: <20130128085820.GR35868@acme.spoerlein.net> References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> <20130127201140.GD29105@server.rulingia.com> <20130128085820.GR35868@acme.spoerlein.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/NoSyaoazf+aPmp=rJ5E9Umz"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: Peter Jeremy , current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 20:04:51 -0000 --Sig_/NoSyaoazf+aPmp=rJ5E9Umz Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ulrich Sp=C3=B6rlein wrote: > On Mon, 2013-01-28 at 07:11:40 +1100, Peter Jeremy wrote: > > On 2013-Jan-27 14:31:56 -0000, Steven Hartland wrote: > > >----- Original Message -----=20 > > >From: "Ulrich Sp=C3=B6rlein" > > >> I want to transplant my old zpool tank from a 1TB drive to a new 2TB > > >> drive, but *not* use dd(1) or any other cloning mechanism, as the po= ol > > >> was very full very often and is surely severely fragmented. > > > > > >Cant you just drop the disk in the original machine, set it as a mirror > > >then once the mirror process has completed break the mirror and remove > > >the 1TB disk. > >=20 > > That will replicate any fragmentation as well. "zfs send | zfs recv" > > is the only (current) way to defragment a ZFS pool. It's not obvious to me why "zpool replace" (or doing it manually) would replicate the fragmentation. > But are you then also supposed to be able send incremental snapshots to > a third pool from the pool that you just cloned? Yes. > I did the zpool replace now over night, and it did not remove the old > device yet, as it found cksum errors on the pool: >=20 > root@coyote:~# zpool status -v > pool: tank > state: ONLINE > 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://illumos.org/msg/ZFS-8000-8A > scan: resilvered 873G in 11h33m with 24 errors on Mon Jan 28 09:45:32 2= 013 > config: >=20 > NAME STATE READ WRITE CKSUM > tank ONLINE 0 0 27 > replacing-0 ONLINE 0 0 61 > da0.eli ONLINE 0 0 61 > ada1.eli ONLINE 0 0 61 >=20 > errors: Permanent errors have been detected in the following files: >=20 > tank/src@2013-01-17:/.svn/pristine/8e/8ed35772a38e0fec00bc1cbc2f0= 5480f4fd4759b.svn-base [...] > tank/ncvs@2013-01-17:/ports/textproc/uncrustify/distinfo,v >=20 > Interestingly, these only seem to affect the snapshot, and I'm now > wondering if that is the problem why the backup pool did not accept the > next incremental snapshot from the new pool. I doubt that. My expectation would be that it only prevents the "zfs send" to finish successfully. BTW, you could try reading the files to be sure that the checksum problems are permanent and not just temporary USB issues. > How does the receiving pool known that it has the correct snapshot to > store an incremental one anyway? Is there a toplevel checksum, like for > git commits? How can I display and compare that? Try zstreamdump: fk@r500 ~ $sudo zfs send -i @2013-01-24_20:48 tank/etc@2013-01-26_21:14 | z= streamdump | head -11 BEGIN record hdrtype =3D 1 features =3D 4 magic =3D 2f5bacbac creation_time =3D 5104392a type =3D 2 flags =3D 0x0 toguid =3D a1eb3cfe794e675c fromguid =3D 77fb8881b19cb41f toname =3D tank/etc@2013-01-26_21:14 END checksum =3D 1047a3f2dceb/67c999f5e40ecf9/442237514c1120ed/efd508ab5203= c91c fk@r500 ~ $sudo zfs send lexmark/backup/r500/tank/etc@2013-01-24_20:48 | zs= treamdump | head -11 BEGIN record hdrtype =3D 1 features =3D 4 magic =3D 2f5bacbac creation_time =3D 51018ff4 type =3D 2 flags =3D 0x0 toguid =3D 77fb8881b19cb41f fromguid =3D 0 toname =3D lexmark/backup/r500/tank/etc@2013-01-24_20:48 END checksum =3D 1c262b5ffe935/78d8a68e0eb0c8e7/eb1dde3bd923d153/9e08291036= 49ae22 Fabian --Sig_/NoSyaoazf+aPmp=rJ5E9Umz Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEG2FAACgkQBYqIVf93VJ28pwCdElXCUi5LtiuQDigCoscMjT3q bXAAn0MaWH2Uuj3tqtaoWIKXeMBeW76D =w0Za -----END PGP SIGNATURE----- --Sig_/NoSyaoazf+aPmp=rJ5E9Umz-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 21:21:01 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 353496CB; Mon, 28 Jan 2013 21:21:01 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C78E7CBE; Mon, 28 Jan 2013 21:21:00 +0000 (UTC) Message-ID: <5106EB67.5060805@FreeBSD.org> Date: Mon, 28 Jan 2013 16:19:35 -0500 From: Jung-uk Kim User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130116 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: ACPI panic on unplugging the power cord. References: <20130122175629.GA1714@garage.freebsd.pl> <51008661.4060006@FreeBSD.org> <20130124161848.GA2386@garage.freebsd.pl> <20130125092602.GB1295@garage.freebsd.pl> <5102F6F0.4000100@FreeBSD.org> <20130126165816.GA1376@garage.freebsd.pl> In-Reply-To: <20130126165816.GA1376@garage.freebsd.pl> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 21:21:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-01-26 11:58:16 -0500, Pawel Jakub Dawidek wrote: > On Fri, Jan 25, 2013 at 04:19:44PM -0500, Jung-uk Kim wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 2013-01-25 04:26:02 -0500, Pawel Jakub Dawidek wrote: >>> On Thu, Jan 24, 2013 at 05:18:48PM +0100, Pawel Jakub Dawidek >>> wrote: >>>> One is when I leave laptop idle for some time (few hours?): >>>> >>>> http://people.freebsd.org/~pjd/misc/acpi_idle_panic_0.jpg >>>> http://people.freebsd.org/~pjd/misc/acpi_idle_panic_1.jpg >>> >>> Small update. This panic doesn't happen when the system is >>> idle, it happens we I close the lid to the point when display >>> is turned off (which is almost closed, but not entirely >>> closed). >>> >>> Closing lid doesn't trigger suspend or anything like that. It >>> just turns off the display. >> >> Please try the attached patch (with my previous patch). Also, >> available from here: >> >> http://people.freebsd.org/~jkim/acpi_exit.diff > > Your patch fixes panic triggered by unplugging power cable as well > the one triggered by closing the lid. I haven't tried booting from > battery and connecting power cable, but I expect happy end there as > well. Committed, thanks! Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRButnAAoJECXpabHZMqHO+C4IAJVcT97/ZBylUajuBpY/s+rb uiBLHALbXpKiHqRDiaTmkGdROdfMKc8IhnOB97N7YlLMzYhEFKXCL4JCMxGtxT8K sQ3FzKsbdNaEVZl0k1Ql7ogLSMaCLS9Gjbd4/4Rm7oQUf+k90x9aSavsDBPfszgD uPrhBNgAvWVP9rHjMgW7mYsM73j33cbNYE5XBBV6R6RqDF4CjbhpwD4gIIQDsx3y 0ff3lc1RFed9syjlg6suL3jL+2Cnv+JkSVon5KA77n+g1zLkI6TifnWFYJnNt48r P7mhrmknazkoEdIEpDDFJEJTt4QE0qm0VRjCfzUPhsNdR1dJy85Hrijem9HmEWg= =vdbF -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 21:44:28 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4B5FCD8B; Mon, 28 Jan 2013 21:44:28 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email2.allantgroup.com (email2.emsphone.com [199.67.51.116]) by mx1.freebsd.org (Postfix) with ESMTP id D7B1EE60; Mon, 28 Jan 2013 21:44:27 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [172.17.17.101]) by email2.allantgroup.com (8.14.5/8.14.5) with ESMTP id r0SLfD5F000686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jan 2013 15:41:13 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.6/8.14.6) with ESMTP id r0SLfCYg060240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Jan 2013 15:41:12 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.6/8.14.6/Submit) id r0SLfBWT060239; Mon, 28 Jan 2013 15:41:11 -0600 (CST) (envelope-from dan) Date: Mon, 28 Jan 2013 15:41:11 -0600 From: Dan Nelson To: Fabian Keil Subject: Re: Zpool surgery Message-ID: <20130128214111.GA14888@dan.emsphone.com> References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> <20130127201140.GD29105@server.rulingia.com> <20130128085820.GR35868@acme.spoerlein.net> <20130128205802.1ffab53e@fabiankeil.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130128205802.1ffab53e@fabiankeil.de> X-OS: FreeBSD 9.1-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (email2.allantgroup.com [172.17.19.78]); Mon, 28 Jan 2013 15:41:13 -0600 (CST) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on email2.allantgroup.com X-Scanned-By: MIMEDefang 2.73 Cc: Peter Jeremy , current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 21:44:28 -0000 In the last episode (Jan 28), Fabian Keil said: > Ulrich Spörlein wrote: > > On Mon, 2013-01-28 at 07:11:40 +1100, Peter Jeremy wrote: > > > On 2013-Jan-27 14:31:56 -0000, Steven Hartland wrote: > > > >----- Original Message ----- > > > >From: "Ulrich Spörlein" > > > >> I want to transplant my old zpool tank from a 1TB drive to a new > > > >> 2TB drive, but *not* use dd(1) or any other cloning mechanism, as > > > >> the pool was very full very often and is surely severely > > > >> fragmented. > > > > > > > >Cant you just drop the disk in the original machine, set it as a > > > >mirror then once the mirror process has completed break the mirror > > > >and remove the 1TB disk. > > > > > > That will replicate any fragmentation as well. "zfs send | zfs recv" > > > is the only (current) way to defragment a ZFS pool. > > It's not obvious to me why "zpool replace" (or doing it manually) > would replicate the fragmentation. "zpool replace" essentially adds your new disk as a mirror to the parent vdev, then deletes the original disk when the resilver is done. Since mirrors are block-identical copies of each other, the new disk will contain an exact copy of the original disk, followed by 1TB of freespace. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 22:53:10 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EAB46FAF for ; Mon, 28 Jan 2013 22:53:10 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id C3CD6225 for ; Mon, 28 Jan 2013 22:53:10 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id r0SMrAFJ088154 for ; Mon, 28 Jan 2013 14:53:10 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <51070155.2030708@rawbw.com> Date: Mon, 28 Jan 2013 14:53:09 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 MIME-Version: 1.0 To: current@freebsd.org Subject: patch fixing libdtrace dependencies Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 22:53:11 -0000 Please check in this patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=175661 MFC 9.X. Yuri From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 01:26:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BB995985 for ; Tue, 29 Jan 2013 01:26:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 63233CD7 for ; Tue, 29 Jan 2013 01:26:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEANEkB1GDaFvO/2dsb2JhbABEFoYwuC1zgh4BAQEDAQEBASArIAsFFhgCAg0ZAikBCSYGCAcEARwEh2oGDK10kkeBI4t3gliBEwOIYYp+gi6BHI8sgxWBUTU X-IronPort-AV: E=Sophos;i="4.84,555,1355115600"; d="scan'208";a="14003137" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 28 Jan 2013 20:25:59 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 62EFFB4040; Mon, 28 Jan 2013 20:25:58 -0500 (EST) Date: Mon, 28 Jan 2013 20:25:58 -0500 (EST) From: Rick Macklem To: Lars Eggert Message-ID: <808229611.2447687.1359422758386.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: mounting root from NFS via ROOTDEVNAME MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 01:26:05 -0000 Lars Eggert wrote: > Hi, > > I'm trying to netboot a system where the root device is specified in > the kernel via ROOTDEVNAME: > > options BOOTP > options BOOTP_NFSROOT > options BOOTP_NFSV3 > options BOOTP_COMPAT > options BOOTP_WIRED_TO=em4 > options ROOTDEVNAME=\"nfs:10.11.12.13:/usr/home/elars/dst\" > > I was under the assumption that specifying a ROOTDEVNAME in the kernel > config would override the "root-path" option in DHCP, or at least take > effect when "root-path" wasn't provided via DHCP, but that doesn't > seem to be the case. The system configures it's address correctly over > em4, but then enters a loop: > > em4: link state changed to UP > Received DHCP Offer packet on em4 from 0.0.0.0 (accepted) (no root > path) > Sending DHCP Request packet from interface em4 (XX:XX:XX:XX:XX:XX) > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > DHCP/BOOTP timeout for server 255.255.255.255 > Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) > DHCP/BOOTP timeout for server 255.255.255.255 > ... > > If I hand out a root path via DHCP the system boots fine, but the idea > here is to be able to boot different root devices without needing to > diddle dhcpd.conf. Can this be done? > Well, just to make it more interesting, there are 2 different ways an NFS root file system can be booted by the kernel. The other one can be configured by: - delete all options that start in BOOTP - add the "options NFS_ROOT" Now, the kernel will use information from a list of environment variables set by the loader, plus the values referenced to rootdevnames[0] and rootdevnames[1], if they are set. (The list of these environment variables is in a comment in sys/nfs/nfs_diskless.c and are normally set by pxeboot.) rootdevnames[0] gets set in nfs_diskless.c, but rootdevnames[1] does not. This source file has the magic for this way of doing it, as you might have guessed. I think rootdevnames[1] gets tried if rootdevnames[0] fails. You could try hacking sys/nfs/nfs_diskless.c and add a line to set rootdevnames[1] to ROOTDEVNAME, if it is defined. (#include "opt_rootdevname.h" so that it will be defined, if the option is specified.) I haven't tried this, but it might work? Btw, for the above to work, you need to use pxeboot and I think you'll need to have enough dhcpd setup so that it loads. (I'm not sure if option root-path is needed for pxeboot to get the loader going?) Short answer is, there may be a way to get this to work with a little source hacking, but it might be easier to just modify your dhcpd.conf;-) Btw, I use this document for how I set things up for the "options NFS_ROOT" version. http://people.freebsd.org/~rodrigc/pxe/freebsd_pxe.txt Good luck with it, rick ps: All BOOTP_NFSROOT does is tell the BOOTP version to use an NFS root and it will then expect the dhcp root-path option as you found out. > Thanks, > Lars > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 03:28:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E60D624B; Tue, 29 Jan 2013 03:28:03 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by mx1.freebsd.org (Postfix) with ESMTP id 33AD4213; Tue, 29 Jan 2013 03:28:02 +0000 (UTC) Received: by mail-ee0-f43.google.com with SMTP id c50so1677793eek.2 for ; Mon, 28 Jan 2013 19:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=4vzkCDsiPRGoddXBvHFBZvmO8DvqNN9F7Juld5PJq+A=; b=HXVPXY/nTZTJ8KnkIJqOV3Gxr4K3Qh35RMr1a5oBrugpZV+XZ5fyf2fBozhXN7kDZi QR6O6v2zycko55VN4k7SGyvXTPXxG5iZVDH8++I+cPfAz0jkApSaogt1JLE4xzuJXWfN SWg9WDVrKXegoRO1R9pvknI77BObAgChfSN/NPgKMLstP1/vfHSndx27hB/Jgx+fKImt cGYZX0AI1cqC5aZgnYRU/Rv7wuGpNgKCx/Xs2B/AGBKT60egfRpDMCzf+8nS1t2KdmBP DNv3KDzqZsJA7GgxkNy2yHvYKPN3v/vrvqHBsn95u5XY+QMvgLO/A00aZlKlfa8FJ6jy iaAQ== MIME-Version: 1.0 X-Received: by 10.14.219.3 with SMTP id l3mr306603eep.5.1359430075885; Mon, 28 Jan 2013 19:27:55 -0800 (PST) Received: by 10.14.29.78 with HTTP; Mon, 28 Jan 2013 19:27:55 -0800 (PST) In-Reply-To: References: Date: Mon, 28 Jan 2013 19:27:55 -0800 Message-ID: Subject: Re: hwpmc support for Ivy Bridge Xeon From: hiren panchasara To: freebsd-current Content-Type: text/plain; charset=UTF-8 Cc: Jim Harris , Fabien Thomas X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 03:28:04 -0000 On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara wrote: > I've tried to update hwpmc by adding support for xeon class of Ivy > bridge processors. > > Thanks Jim for pointing me to the correct document. (325462-045US Jan 2013) > > I do not have a reference machine to test with. Any help in that > regard would be appreciated. Got a machine with ivy bridge xeon. Will test my changes and update here soon. Hiren > > Here are the diffs against head (245927): > http://www.strugglingcoder.info/patches/hwpmc_ibx.txt > > Thanks, > Hiren From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 06:16:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7B3D8F53; Tue, 29 Jan 2013 06:16:15 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by mx1.freebsd.org (Postfix) with ESMTP id 50F5E927; Tue, 29 Jan 2013 06:16:15 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id bg2so186835pad.32 for ; Mon, 28 Jan 2013 22:16:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=vSJykJrYeP5MGgIU9BWPv++MSQlPx7slQR8TMF26DzQ=; b=s2ph7vhs4vS03kZHlYZVFvzgdns7l6kzSs5r/bT3C+SFAZXgOVO/vY617inzT911K1 vjHthB4XwWpmYhZAJM1PlMns/+llvLNPzlOGNe3vACLSzkHLFk5wxY/+vOiwty04rg2I 0jngOWcj3xjk9gwVAT6zYAd0GZGq0JMsoVgiDodhWyyT1G+CxjxleudErAbATkT1sq3J /jr4v5dnWyeMpj5FSdSqphMAGYOAKVCmy+BFPsoIxlj/mg1sZqMFowvSfkoZ1ac9C3D6 wdxNp+XzT81Bkg3+KR/SfS7z1wFiNpYokqRnv3yyZ++WpiUgNUfIMzl99CtXFcQiEufI h74A== MIME-Version: 1.0 X-Received: by 10.68.131.35 with SMTP id oj3mr1314183pbb.17.1359440169233; Mon, 28 Jan 2013 22:16:09 -0800 (PST) Received: by 10.67.2.65 with HTTP; Mon, 28 Jan 2013 22:16:09 -0800 (PST) In-Reply-To: <201301281355.31601.jhb@freebsd.org> References: <510245B5.8070704@FreeBSD.org> <5102ADF6.4060202@FreeBSD.org> <5103E5D1.3070808@FreeBSD.org> <201301281355.31601.jhb@freebsd.org> Date: Mon, 28 Jan 2013 22:16:09 -0800 Message-ID: Subject: Re: acpi resume related patch From: Kevin Oberman To: John Baldwin Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org, Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 06:16:15 -0000 On Mon, Jan 28, 2013 at 10:55 AM, John Baldwin wrote: > On Saturday, January 26, 2013 9:18:57 am Andriy Gapon wrote: >> on 25/01/2013 18:08 Andriy Gapon said the following: >> > on 25/01/2013 15:51 John Baldwin said the following: >> >> On Friday, January 25, 2013 3:43:33 am Andriy Gapon wrote: >> >>> >> >>> If you have ACPI suspend/resume working, if it used to work but stopped working >> >>> at some time, if it never worked, but you are still hoping, could you please >> >>> test the following patch and report back? >> >>> >> >>> http://svn.freebsd.by/files/acpi-apic-wakeup-final.patch >> >> >> >> This will break systems not using the local APIC since you unconditionally >> >> call lapic_setup() on resume.This was part of the feature of the previous >> >> code that by using a dummy pic it could register it only when the local APIC >> >> was used. >> > >> > Thank you for drawing my attention to this. I will try to fix this issue. >> > The reason I want to remove lapic from 'pics' (and I already described it in a >> > private email) is that Local APIC is a special kind of PIC. It's already >> > explicitly initialized by APs. Putting it into 'pics' tailq just obfuscates the code. >> > >> >> It should also be registered before any of the I/O APICs are by >> >> the design of the local_apic.c code. >> > >> > In fact, as I see in the code, Local APIC is always registered _after_ I/O APICs. >> > And thus lapic_resume was called after ioapic_resume. >> > Additionally, currently there is no synchronization between initialization of >> > Local APICs on APs and initialization of I/O APICs at the wakeup/resume time. >> > >> >> Here is an updated version of the patch: >> http://people.freebsd.org/~avg/acpi-apic-wakeup.2.patch >> >> John, >> could you please review the PIC-related part? I decided to go back to the >> current approach while fixing the suspend/resume ordering and also order of >> registration for Local APIC. Must say that XEN special casing makes >> apic_setup_io a little bit untidy. >> >> Additionally this patch fixes AP Local APIC initialization ordering on i386. >> In the original patch I changed only amd64 code. > > This looks good to me. No joy here. System graphics turns off as I'd expect, but it never comes back. No wireless. No access. :-( Maybe someday, but not today. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 08:29:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7C86E95E; Tue, 29 Jan 2013 08:29:52 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ea0-f180.google.com (mail-ea0-f180.google.com [209.85.215.180]) by mx1.freebsd.org (Postfix) with ESMTP id C3986F7E; Tue, 29 Jan 2013 08:29:51 +0000 (UTC) Received: by mail-ea0-f180.google.com with SMTP id c1so74168eaa.11 for ; Tue, 29 Jan 2013 00:29:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=T/t4n35ymz7NFShGWKXa7miSuM2RG4+cFwK9Deb2poQ=; b=d+yRBaFBVoBpScxITIrMKHwTFvoZ1CrTTece+LKKUUJqyan6pj7lhy+PGrFx2RfdFO GGqqyreXB2dGihkvrMnaRbdJMe/1wTObCF8Yu8+Ize9Yyh4bpzOnJfqsgBT9V0YYFDlw O86V4roeg0EmaXkuw7Q1usK01LYcAZncXgiMwwgg2oPqUnaGVw9rCTCgBlnp98+inn8s o+fzCv+QwXWNwB8QYOQSHOv/0ub77gVsU6pGwXBz7smcovVUszWMGN06FXM+yX7Xi17h eY807sE0YzzRpKu7AvzOgrVDAzKLLw0O92N+uL+UxTB/V+hdUaBfB+lSeubusg0K/zhj 5SJg== MIME-Version: 1.0 X-Received: by 10.14.174.198 with SMTP id x46mr952830eel.23.1359448190707; Tue, 29 Jan 2013 00:29:50 -0800 (PST) Received: by 10.14.29.78 with HTTP; Tue, 29 Jan 2013 00:29:50 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Jan 2013 00:29:50 -0800 Message-ID: Subject: Re: hwpmc support for Ivy Bridge Xeon From: hiren panchasara To: freebsd-current Content-Type: text/plain; charset=UTF-8 Cc: Jim Harris , Fabien Thomas X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 08:29:52 -0000 On Mon, Jan 28, 2013 at 7:27 PM, hiren panchasara wrote: > On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara > wrote: >> I've tried to update hwpmc by adding support for xeon class of Ivy >> bridge processors. >> >> Thanks Jim for pointing me to the correct document. (325462-045US Jan 2013) >> >> I do not have a reference machine to test with. Any help in that >> regard would be appreciated. > > Got a machine with ivy bridge xeon. Will test my changes and update here soon. > > Hiren It seems to be working fine: Here is o/p of "pmccontrol -L" listing all the event counters: http://www.strugglingcoder.info/patches/hwpmc_ibx_pmccontrol.txt And below is the o/p of pmctest.py script: http://www.strugglingcoder.info/patches/hwpmc_ibx_pmctest.txt cheers, Hiren >> >> Here are the diffs against head (245927): >> http://www.strugglingcoder.info/patches/hwpmc_ibx.txt >> >> Thanks, >> Hiren From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 08:34:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F2A4FAFC for ; Tue, 29 Jan 2013 08:34:07 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by mx1.freebsd.org (Postfix) with ESMTP id 61E2FFC0 for ; Tue, 29 Jan 2013 08:34:06 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id l12so379426lbo.5 for ; Tue, 29 Jan 2013 00:34:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=BmzKmTtBksi7kyPHYhbRgFZn9OiPwvkQ08bPjIJTZyY=; b=WvdTCnaf3OXfR6d0wqKNO9Pp+0t0cdKthS+gyEwQMAsJ0vW9gyf2EGb4UEkXVBOkcI rwEmsGugmKY0ZFbF+DWDtMtuXgiuYLgWbWE2hlyWUyIoZl8YU9JAvzi4AbxxSay/3DJm XvUT87yzCuvTwqQHQRACIvguR5I3QGn/i6fPBWg7B5uIcIjz8l2SBlKzlafZRx0iFPSO DXPU+EI40ABRbLVCG26oGLf6ZOuukdkIptUnZ0JKqDnYvZnPWxVvuBrF7hoEZU8S7N4/ yjbmkQifZmw+VzuxmWcW0RhdYMoySVqyERKmjwYtt8E61lgcwFujVWMBwFiffvEFvAKc SOWw== MIME-Version: 1.0 X-Received: by 10.152.133.67 with SMTP id pa3mr273382lab.44.1359448440467; Tue, 29 Jan 2013 00:34:00 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.24.225 with HTTP; Tue, 29 Jan 2013 00:34:00 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Jan 2013 00:34:00 -0800 X-Google-Sender-Auth: cMwBwS38-gJN2RJN6aMxkQ48dwA Message-ID: Subject: Re: mounting root from NFS via ROOTDEVNAME From: Craig Rodrigues To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 08:34:08 -0000 On Mon, Jan 28, 2013 at 7:13 AM, Eggert, Lars wrote: > Hi, > > I'm trying to netboot a system where the root device is specified in the > kernel via ROOTDEVNAME: > > Lars, I recommend that you do not use ROOTDEVNAME, and instead you should follow the instructions which I wrote and contributed to the FreeBSD handbook: "PXE Booting with an NFS Root File System" http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-pxe-nfs.html The content of this document is the same as the text file which Rick Macklem pointed out (I wrote that too). BTW, if you ever visit the Netapp campus in Sunnyvale, California, feel free to say hello, because I work around the corner from there. :) -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 09:13:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BD37AAA6 for ; Tue, 29 Jan 2013 09:13:58 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id A435034E for ; Tue, 29 Jan 2013 09:13:58 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,559,1355126400"; d="scan'208";a="13446895" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 29 Jan 2013 01:13:57 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0T9Dv2x002065; Tue, 29 Jan 2013 01:13:57 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Tue, 29 Jan 2013 01:13:57 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3Jhggg0AgAALKoA= Date: Tue, 29 Jan 2013 09:13:56 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 09:13:58 -0000 Hi, On Jan 29, 2013, at 9:34, Craig Rodrigues wrote: > I recommend that you do not use ROOTDEVNAME, and instead > you should follow the instructions which I wrote and contributed to the > FreeBSD handbook: >=20 > "PXE Booting with an NFS Root File System" >=20 > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-pxe-nfs= .html >=20 > The content of this document is the same as the text file which Rick > Macklem pointed out (I wrote that too). I had read both before, and they're very useful documents. Unfortunately, t= hey don't fully apply to my case, since I'm not PXE-booting the system; it = netboots the kernel from a custom loader. So once the kernel bootstraps, I = need it to obtain an IP address and then NFS-mount root. >=20 > BTW, if you ever visit the Netapp campus in Sunnyvale, California, feel > free to say hello, > because I work around the corner from there. :) > -- > Craig Rodrigues > rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 09:17:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D70ABDE for ; Tue, 29 Jan 2013 09:17:26 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 3A4A8379 for ; Tue, 29 Jan 2013 09:17:26 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,559,1355126400"; d="scan'208";a="13448474" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 29 Jan 2013 01:17:26 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0T9HPe1005473; Tue, 29 Jan 2013 01:17:25 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Tue, 29 Jan 2013 01:17:25 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3A== Date: Tue, 29 Jan 2013 09:17:24 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <6F877B7DBE173D4E8DF5E47FD92AA528@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 09:17:26 -0000 On Jan 29, 2013, at 10:13, Lars Eggert wrote: > On Jan 29, 2013, at 9:34, Craig Rodrigues wrote: >> I recommend that you do not use ROOTDEVNAME, and instead >> you should follow the instructions which I wrote and contributed to the >> FreeBSD handbook: >>=20 >> "PXE Booting with an NFS Root File System" >>=20 >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-pxe-nf= s.html >>=20 >> The content of this document is the same as the text file which Rick >> Macklem pointed out (I wrote that too). >=20 > I had read both before, and they're very useful documents. Unfortunately,= they don't fully apply to my case, since I'm not PXE-booting the system; i= t netboots the kernel from a custom loader. So once the kernel bootstraps, = I need it to obtain an IP address and then NFS-mount root. (Whoops, hit send by mistake.) That's what I was trying to achieve with the BOOTP and BOOTP_WIRED_TO optio= ns. Hm, I wonder if I could simply use the custom loader to netboot tftpboot, a= nd then follow your instructions... Will try. >> BTW, if you ever visit the Netapp campus in Sunnyvale, California, feel >> free to say hello, because I work around the corner from there. :) Am there about once a month, will do :-) Lars From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 10:06:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B8442A02; Tue, 29 Jan 2013 10:06:02 +0000 (UTC) (envelope-from davide.italiano@gmail.com) Received: from mail-ve0-f179.google.com (mail-ve0-f179.google.com [209.85.128.179]) by mx1.freebsd.org (Postfix) with ESMTP id 69969C24; Tue, 29 Jan 2013 10:06:02 +0000 (UTC) Received: by mail-ve0-f179.google.com with SMTP id cz10so141080veb.38 for ; Tue, 29 Jan 2013 02:05:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4D/bQvG2unBu3zcbAgAvg+9KlBRn0hXX1yZ1xsZp7Ak=; b=W44WNBoxbH+h5XSeR3+VQHjOl2UQgOELgxL9BkcCUpFEVhmENXtnF7/lh2rJm9DOa9 cRgOC1wkYf/PO6SHXWa6O9O+RRjfE2QP/ta9+AjdqdA2X3ZmMA8r2JDuAc3uYBSvn8MU Q+QvddhJ2ep2xYGE0vbthZM6QekcUqouUd4R6uWJDAjvZP/9b4d4J1MnNaxkgIP2+1aO n4+Xar8/wjB43fwaNIXtdAm/B8Vfm0eVmg8PzzWYBTFlRb9xOqRet6HyuY8bPGmL5Lrx 7yiSdOpf1wVdK8ALnPc/ZCx8bfpVohbqu6Te3hUZVsTcToXGgJd6YvlrA/FP+Kl5pQeZ NyOg== MIME-Version: 1.0 X-Received: by 10.52.89.106 with SMTP id bn10mr308006vdb.68.1359453955842; Tue, 29 Jan 2013 02:05:55 -0800 (PST) Sender: davide.italiano@gmail.com Received: by 10.220.114.134 with HTTP; Tue, 29 Jan 2013 02:05:55 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Jan 2013 02:05:55 -0800 X-Google-Sender-Auth: u6Pd2fLOOxbo9CqvxN1fz3KfkhM Message-ID: Subject: Re: hwpmc support for Ivy Bridge Xeon From: Davide Italiano To: hiren panchasara Content-Type: text/plain; charset=ISO-8859-1 Cc: Fabien Thomas , freebsd-current , Jim Harris , pho@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 10:06:02 -0000 On Tue, Jan 29, 2013 at 12:29 AM, hiren panchasara wrote: > On Mon, Jan 28, 2013 at 7:27 PM, hiren panchasara > wrote: >> On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara >> wrote: >>> I've tried to update hwpmc by adding support for xeon class of Ivy >>> bridge processors. >>> >>> Thanks Jim for pointing me to the correct document. (325462-045US Jan 2013) >>> >>> I do not have a reference machine to test with. Any help in that >>> regard would be appreciated. >> >> Got a machine with ivy bridge xeon. Will test my changes and update here soon. >> >> Hiren > > It seems to be working fine: > > Here is o/p of "pmccontrol -L" listing all the event counters: > http://www.strugglingcoder.info/patches/hwpmc_ibx_pmccontrol.txt > I don't see anything wrong there. > And below is the o/p of pmctest.py script: > http://www.strugglingcoder.info/patches/hwpmc_ibx_pmctest.txt > With 'pmctest.py' are you talking about the gnn@ script available in tools/ ? What are you profiling (ls, find, the kernel) ? I've recently discovered an excellent tool from Peter in stress2 suite to test pmc. Maybe you can try it. http://svnweb.freebsd.org/base/user/pho/stress2/misc/pmc.sh?revision=237222&view=markup > cheers, > Hiren >>> >>> Here are the diffs against head (245927): >>> http://www.strugglingcoder.info/patches/hwpmc_ibx.txt >>> >>> Thanks, >>> Hiren > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Thanks -- Davide From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 10:06:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2009DB03 for ; Tue, 29 Jan 2013 10:06:12 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id D8D28C28 for ; Tue, 29 Jan 2013 10:06:11 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1U084r-002CA8-F8>; Tue, 29 Jan 2013 11:06:05 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1U084r-003mR7-Ci>; Tue, 29 Jan 2013 11:06:05 +0100 Message-ID: <51079F0A.20309@zedat.fu-berlin.de> Date: Tue, 29 Jan 2013 11:06:02 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Current FreeBSD Subject: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBF9222BA75C6287D31D5202F" X-Originating-IP: 130.133.86.198 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 10:06:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBF9222BA75C6287D31D5202F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I receive this error since yesterday building world and it is still sticky on most recent sources (r246057) and I was wondering why the tinderboxes do not pick this up on the 10.0-CURRENT builds ... just for a notice for the development folks ... oh =3D=3D=3D> libexec/atf/atf-check (all) c++ -O3 -pipe -fno-strict-aliasing -march=3Dnative -march=3Dnative -DHAVE_CONFIG_H -I/usr/src/libexec/atf/atf-check/../../../contrib/atf -Qunused-arguments -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith -Wno-uninitialized -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -stdlib=3Dlibc++ -std=3Dc++11 -c /usr/src/libexec/atf/atf-check/../../../contrib/atf/atf-sh/atf-check.cpp c++ -O3 -pipe -fno-strict-aliasing -march=3Dnative -march=3Dnative -DHAVE_CONFIG_H -I/usr/src/libexec/atf/atf-check/../../../contrib/atf -Qunused-arguments -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith -Wno-uninitialized -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -stdlib=3Dlibc++ -std=3Dc++11 -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++ -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c -o atf-check atf-check.o -latf-c++ -latf-c /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf= -c++.so: undefined reference to `std::bad_alloc::bad_alloc()' /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf= -c++.so: undefined reference to `std::bad_alloc::~bad_alloc()' /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::bad_alloc()' c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [atf-check] Error code 1 Stop in /usr/src/libexec/atf/atf-check. *** [all] Error code 1 Stop in /usr/src/libexec/atf. *** [all] Error code 1 Stop in /usr/src/libexec. *** [libexec.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. --------------enigBF9222BA75C6287D31D5202F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRB58NAAoJEOgBcD7A/5N8l7oH/2hMKOwgYd9YVAJCHhU1yB6A bj/a9uMXvAZV+xbnaSVIZjuSq5TzGKCNlVzVrLahwqqxr1coz6umEScu0sWVyj00 J3xxnoX1+ykXv1nSZgC36lO/uLztryxqgJPZNRp9Qgzn/AMw70APZn5wF36tchSZ BUdUb45NLvvXLR5ilNyduduFn6mnYS4sS+zKfA2frHzNuIbA1U3J1kWTxQ/hst66 2hsUpNnJ39P4N9EHYZ/Sh2hwa6g18gimfUcr4um7RkO4eEQGWmz2HgEPNTOzdSpf lJOdneMeWAgLqenMU+JfBa1UqxDHVrN2vRbvk8uN42TmfFfwjWCh53XoPMWvhWE= =nAJH -----END PGP SIGNATURE----- --------------enigBF9222BA75C6287D31D5202F-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 10:48:50 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1078B670 for ; Tue, 29 Jan 2013 10:48:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id C5C40EF5 for ; Tue, 29 Jan 2013 10:48:49 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1U08kC-002PKz-U2>; Tue, 29 Jan 2013 11:48:48 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1U08kC-003qON-Rb>; Tue, 29 Jan 2013 11:48:48 +0100 Message-ID: <5107A90E.1090905@zedat.fu-berlin.de> Date: Tue, 29 Jan 2013 11:48:46 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: David Chisnall Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' References: <51079F0A.20309@zedat.fu-berlin.de> <44AB3F18-5BAB-45B3-9497-60D5214FBEB4@theravensnest.org> In-Reply-To: <44AB3F18-5BAB-45B3-9497-60D5214FBEB4@theravensnest.org> X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0A4939B4CE320CE2F2D557F0" X-Originating-IP: 130.133.86.198 Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 10:48:50 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0A4939B4CE320CE2F2D557F0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/29/13 11:08, David Chisnall wrote: > On 29 Jan 2013, at 10:06, O. Hartmann wrote: >=20 >> I receive this error since yesterday building world and it is still >> sticky on most recent sources (r246057) and I was wondering why the >> tinderboxes do not pick this up on the 10.0-CURRENT builds ... just fo= r >> a notice for the development folks ... >=20 > Are you building with -DNO_CLEAN or similar? This error is expected if= you have recompiled libcxxrt but not libc++. If you recompile libc++, i= t should work correctly. Alternatively, if it is accidentally trying to = link the libc++ that you build against your installed libcxxrt, then it w= ill also break. >=20 > David >=20 No, not that I'm aware of that (no -DNO_CLESN). I run a script calling "make -jX buildworld", the script evaluates simply the number of threads possible and also deletes(!) /usr/obj completely. So I'm quite sure that I start over with a virging /usr/obj when I start building world. oh --------------enig0A4939B4CE320CE2F2D557F0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRB6kQAAoJEOgBcD7A/5N8GaAIAJaU9HGcCAKbaPmqimoMUIZg 1PTlSeYaa8/QEoWiDSf6VLB/zxACQdTTSpA18daMrVXxYrrWNKl3yhHEn+tIp823 bh3+Fr+7BM+TCeKYTfjc0KIucooNHnOw87mZEJrGBwWOSua/md/n9+BzmCZyyaDC geZBuMynDTYpX4xxpLDX6Pp/AhYaSCK/PTJtjEWoC3f7WAv+R53W087UJv9XhOCY 0/powXpsSgDMbuPKw0ajglPrFAZvm+TjTDrIFySKWPgWOIUjLU95Jx2iZKhExX/I iugDT/tO+4WZ1uptclV+WY3MePS5yCBccn5bhB2JgPXCFZP68KoHPfD5PiKI34g= =RIjD -----END PGP SIGNATURE----- --------------enig0A4939B4CE320CE2F2D557F0-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 10:53:03 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 51A6A838 for ; Tue, 29 Jan 2013 10:53:03 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 0A54AF3F for ; Tue, 29 Jan 2013 10:53:02 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r0TAr1nK000192 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 29 Jan 2013 10:53:02 GMT (envelope-from theraven@FreeBSD.org) Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/signed; boundary="Apple-Mail=_0B4A655B-6352-4E8D-BEA8-40F2C205CBA6"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: David Chisnall In-Reply-To: <5107A90E.1090905@zedat.fu-berlin.de> Date: Tue, 29 Jan 2013 10:52:54 +0000 Message-Id: References: <51079F0A.20309@zedat.fu-berlin.de> <44AB3F18-5BAB-45B3-9497-60D5214FBEB4@theravensnest.org> <5107A90E.1090905@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.1278) Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 10:53:03 -0000 --Apple-Mail=_0B4A655B-6352-4E8D-BEA8-40F2C205CBA6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 29 Jan 2013, at 10:48, O. Hartmann wrote: > On 01/29/13 11:08, David Chisnall wrote: >> On 29 Jan 2013, at 10:06, O. Hartmann wrote: >>=20 >>> I receive this error since yesterday building world and it is still >>> sticky on most recent sources (r246057) and I was wondering why the >>> tinderboxes do not pick this up on the 10.0-CURRENT builds ... just = for >>> a notice for the development folks ... >>=20 >> Are you building with -DNO_CLEAN or similar? This error is expected = if you have recompiled libcxxrt but not libc++. If you recompile = libc++, it should work correctly. Alternatively, if it is accidentally = trying to link the libc++ that you build against your installed = libcxxrt, then it will also break. >>=20 >> David >>=20 >=20 >=20 > No, not that I'm aware of that (no -DNO_CLESN). >=20 > I run a script calling "make -jX buildworld", the script evaluates > simply the number of threads possible and also deletes(!) /usr/obj > completely. So I'm quite sure that I start over with a virging = /usr/obj > when I start building world. Is it building libcxxrt before building libc++? Can you check what = command it is running to link libc++? David --Apple-Mail=_0B4A655B-6352-4E8D-BEA8-40F2C205CBA6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQIcBAEBAgAGBQJRB6oHAAoJEKx65DEEsqId/vcP/20JWp8Lm1BFdEppVRaPyD03 yWiYLgXM5qEbaZeeO7itQawCM9V/tR8dUyj8qrP+rfMgUipLzNFXMce/KLwvZ0C8 Y9IdocgPUT3eeofXOjMmg5QNJxi02Ljt04Nc2Zn+9kDMUAnlUr5N709/lGib32uj Pz5VTyhKvpaXg0Jicz5RHyRdq16Fobx+YfTgv9mXlpv0dRbj/BfNxrOuAIyKGV7A m0XRUxvq7sspsWj61TVro0hFuSXUaU5ZIctJPJqJVTcIDetzz7XEmMmkLRMtq9tH a2fmjOukRehtHM6DO8howNQ8jr6XRC77OPZBx3XAI0nuy/iqjRbXatw9lWSiTr4M zMf4LzmUh0fTgfwogkLinAWFxmbPaAtFPMD7Zg44PGRJjtrtGYzx6fgkigtQbr2A qTUeMHCh1JxHK9rtq8oNm8fZYi3pC+7qUmn4H9TYgm55rbdCSRvBEPjbRRNQweDk 6MCaI9T56BWmSZ4k/jHfrFaUlZ/jDQjZ7WqyC3gz4BgWco48EX1y/Y3W6v2dQWZ0 z/2Kq9MZPpoHhoidmvJwd8V3hwtUxIVS+nj1E2Mi9RvEPqa6fZ4gmC/mIjAhJ8wm cqnxgQl2K3oaTFsCa2masRedNBZFfxrZHgkRani/eflneaRoxHz/d9KFz2zfAo99 1/gojAcvGzVzu28FS6CX =5qf5 -----END PGP SIGNATURE----- --Apple-Mail=_0B4A655B-6352-4E8D-BEA8-40F2C205CBA6-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 11:03:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8F246BE9; Tue, 29 Jan 2013 11:03:40 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ea0-f173.google.com (mail-ea0-f173.google.com [209.85.215.173]) by mx1.freebsd.org (Postfix) with ESMTP id AD821FC8; Tue, 29 Jan 2013 11:03:39 +0000 (UTC) Received: by mail-ea0-f173.google.com with SMTP id i1so131960eaa.4 for ; Tue, 29 Jan 2013 03:03:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/B6IlEEpz2k9ntjj1NzE95BgjEEB+KfSsgZ8xJrOW30=; b=gQNH7134YZIqNOmNphGe69KEEIV/FC6JAAgnVowkzel78Fr8RdzgbWdrcSuGTbaAOa 4SuYzMsHYVJKV1HInQlrJhRcYtyIWuowTRih7nymrlVlcjIaNlg8Ty68xlDnfbv4Lwyf yQevmHVqXzyY9Vpwa/Jovhh6HeF0ZUINMsDl62+d4JpBeF5GuMHlid2fyPGxiBqbO/DT CFYIt4NgP/TpaK+HBl5K+/o2b4B7w7jmMpI7xxt54vMbUVk9P/QQ9QVuUyFykb71Uua5 P3asyHMmu9sInf8p0j5oZotdqyCgtR2Ry7+6nSWNNu8Mr/nJ2TYNZaP8j8xpagDAJzUm f0qQ== MIME-Version: 1.0 X-Received: by 10.14.220.1 with SMTP id n1mr2352220eep.16.1359457412706; Tue, 29 Jan 2013 03:03:32 -0800 (PST) Received: by 10.14.29.78 with HTTP; Tue, 29 Jan 2013 03:03:32 -0800 (PST) In-Reply-To: References: Date: Tue, 29 Jan 2013 03:03:32 -0800 Message-ID: Subject: Re: hwpmc support for Ivy Bridge Xeon From: hiren panchasara To: Davide Italiano Content-Type: text/plain; charset=UTF-8 Cc: Fabien Thomas , freebsd-current , Jim Harris , pho@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 11:03:40 -0000 On Tue, Jan 29, 2013 at 2:05 AM, Davide Italiano wrote: > On Tue, Jan 29, 2013 at 12:29 AM, hiren panchasara > wrote: >> On Mon, Jan 28, 2013 at 7:27 PM, hiren panchasara >> wrote: >>> On Sat, Jan 26, 2013 at 1:58 AM, hiren panchasara >>> wrote: >>>> I've tried to update hwpmc by adding support for xeon class of Ivy >>>> bridge processors. >>>> >>>> Thanks Jim for pointing me to the correct document. (325462-045US Jan 2013) >>>> >>>> I do not have a reference machine to test with. Any help in that >>>> regard would be appreciated. >>> >>> Got a machine with ivy bridge xeon. Will test my changes and update here soon. >>> >>> Hiren >> >> It seems to be working fine: >> >> Here is o/p of "pmccontrol -L" listing all the event counters: >> http://www.strugglingcoder.info/patches/hwpmc_ibx_pmccontrol.txt >> > > I don't see anything wrong there. > >> And below is the o/p of pmctest.py script: >> http://www.strugglingcoder.info/patches/hwpmc_ibx_pmctest.txt >> > > With 'pmctest.py' are you talking about the gnn@ script available in tools/ ? Yes. > What are you profiling (ls, find, the kernel) ? I was testing simple commands like ls. > I've recently discovered an excellent tool from Peter in stress2 suite > to test pmc. Maybe you can try it. > http://svnweb.freebsd.org/base/user/pho/stress2/misc/pmc.sh?revision=237222&view=markup Interesting tool. I will spend more time in looking into it. Though I quickly did run pmc.sh run: run time 0+00:05:00, incarnations 1, load 100, verbose 1 10:48:37 Loop #1 rw: run time 0+00:02:00, incarnations 8, load 70, verbose 1 swap: run time 0+00:02:00, incarnations 38, load 80, verbose 1 creat: run time 0+00:02:00, incarnations 3, load 80, verbose 1 10:52:05 Loop #2 rw: run time 0+00:02:00, incarnations 17, load 70, verbose 1 creat: run time 0+00:02:00, incarnations 18, load 80, verbose 1 mkdir: run time 0+00:02:00, incarnations 9, load 80, verbose 1 Again, I appreciate you helping here, Thanks, Hiren > >> cheers, >> Hiren >>>> >>>> Here are the diffs against head (245927): >>>> http://www.strugglingcoder.info/patches/hwpmc_ibx.txt >>>> >>>> Thanks, >>>> Hiren >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > Thanks > > -- > Davide From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 12:02:33 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D545F3C5 for ; Tue, 29 Jan 2013 12:02:33 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 35A01747 for ; Tue, 29 Jan 2013 12:02:32 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0TC2Qku065144 for ; Tue, 29 Jan 2013 05:02:26 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0TC2NOw022233; Tue, 29 Jan 2013 05:02:23 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: mounting root from NFS via ROOTDEVNAME From: Ian Lepore To: "Eggert, Lars" In-Reply-To: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Content-Type: text/plain; charset="us-ascii" Date: Tue, 29 Jan 2013 05:02:23 -0700 Message-ID: <1359460943.93359.120.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 12:02:33 -0000 On Tue, 2013-01-29 at 09:17 +0000, Eggert, Lars wrote: > On Jan 29, 2013, at 10:13, Lars Eggert > wrote: > > On Jan 29, 2013, at 9:34, Craig Rodrigues wrote: > >> I recommend that you do not use ROOTDEVNAME, and instead > >> you should follow the instructions which I wrote and contributed to the > >> FreeBSD handbook: > >> > >> "PXE Booting with an NFS Root File System" > >> > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-pxe-nfs.html > >> > >> The content of this document is the same as the text file which Rick > >> Macklem pointed out (I wrote that too). > > > > I had read both before, and they're very useful documents. Unfortunately, they don't fully apply to my case, since I'm not PXE-booting the system; it netboots the kernel from a custom loader. So once the kernel bootstraps, I need it to obtain an IP address and then NFS-mount root. > > (Whoops, hit send by mistake.) > > That's what I was trying to achieve with the BOOTP and BOOTP_WIRED_TO options. > > Hm, I wonder if I could simply use the custom loader to netboot tftpboot, and then follow your instructions... Will try. I think that's what I used to do before I switched to configuring the boot file and root path via dhcp as well. I could've sworn I used BOOTP without BOOTP_NFSROOT, but perhaps that's just my muddled memory of what I tried to do that never worked out. I also think all of this is a bug. It seems to me that BOOTP without BOOTP_NFSROOT should obtain ip-related info from dhcp but use ROOTDEVNAME as configured, perhaps with any dhcp-provided root path as a fallback if there's a problem or ROOTDEVNAME is unconfigured. -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 10:08:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2DC57C70 for ; Tue, 29 Jan 2013 10:08:08 +0000 (UTC) (envelope-from theraven@theravensnest.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 03767CD5 for ; Tue, 29 Jan 2013 10:08:07 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r0TA86QU099954 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 29 Jan 2013 10:08:07 GMT (envelope-from theraven@theravensnest.org) Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: David Chisnall In-Reply-To: <51079F0A.20309@zedat.fu-berlin.de> Date: Tue, 29 Jan 2013 10:08:00 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <44AB3F18-5BAB-45B3-9497-60D5214FBEB4@theravensnest.org> References: <51079F0A.20309@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.1278) X-Mailman-Approved-At: Tue, 29 Jan 2013 12:24:50 +0000 Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 10:08:08 -0000 On 29 Jan 2013, at 10:06, O. Hartmann wrote: > I receive this error since yesterday building world and it is still > sticky on most recent sources (r246057) and I was wondering why the > tinderboxes do not pick this up on the 10.0-CURRENT builds ... just = for > a notice for the development folks ... Are you building with -DNO_CLEAN or similar? This error is expected if = you have recompiled libcxxrt but not libc++. If you recompile libc++, = it should work correctly. Alternatively, if it is accidentally trying = to link the libc++ that you build against your installed libcxxrt, then = it will also break. David= From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 14:15:38 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D86449A2 for ; Tue, 29 Jan 2013 14:15:38 +0000 (UTC) (envelope-from g_patrickb@yahoo.com) Received: from nm21.bullet.mail.bf1.yahoo.com (nm21.bullet.mail.bf1.yahoo.com [98.139.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id 5BAB5E18 for ; Tue, 29 Jan 2013 14:15:37 +0000 (UTC) Received: from [98.139.215.141] by nm21.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 14:15:36 -0000 Received: from [98.139.212.242] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 14:15:36 -0000 Received: from [127.0.0.1] by omp1051.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 14:15:36 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 399603.7836.bm@omp1051.mail.bf1.yahoo.com Received: (qmail 15504 invoked by uid 60001); 29 Jan 2013 14:15:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1359468936; bh=DrF7kIzQpdENRLYhLrv1LVF1ybLKsf7/WlLfUb6PYKg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=xXpwRgNTYHWVDc7iB/iRWpBK4DKhXHYUM29xMmsLvFj8yg43O3dsfTHpQ8uBBPIA7Ops3o/r67qGT5inDAEWFs8kFtdbO2fDB68banV9+ywJFtbCac+wzqH23pn0FteJ6NXDJ0ehOlG6ETTJDk97xQgpSTN+xMjFfdQz1WKbgBM= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=qM5bcwG/GYkGQxQsozzIaa1Bt1JGll5U8e/rDOmyoK1rz/GrDNsSGly55dzIWLoHDc43DN4gg5gjr4IODUlHotU8oVlfQ4j/VEVwyGAw+/Oslvg/+ZRlBNMW05e6sgZJj8rDkfltx6b6ZOqO4z2uZ59LdV4QC7cd/Y/tEvtTCz4= ; X-YMail-OSG: mG7zsXEVM1l1wBAhGIuqWW4aGGijQkoNs89SX6IfetrS2HO uRE_9ESEgRB68XO6FAbiMW0mEBW4Rv2jMBx4KWv3qBhQ4SCEXSJqZsZFGSmI sV.LWvW7H0TjyQKjDxxtVV4c48gYJ.8WVbnOHJ8Fsb2.c6KuG_npTrCF7vaA YXkWba20wS0GOX7OHhpbgclqzNwIfsLaRnOcZfgGCkXFuT.4P.Nt1Id.ArMQ FHNu1A5e0Qb2tDaxaiEEfiKXUrFKQLsP_B0wqyH2_kQS3emduP4lQdSjheaA SNNnukB9lTU8_TcvqZAf9Xq9q.RoM8ECEwkJ..CVhY9krEF9XAOu227Q2Oz. tLcA5PWnD2ud1Cqfihu2ZUFS9WregsAFG9KlK2Xu2x_r7FR7t3ci7CIQ6xxF kDJegXE3oDPf1uxPDaAhhnKQyVQiChA5KZe2FoZg_3BTEbEujsrdHcewyv5i vvmdqC4d3.Uw5ND7Y6aC5nFYcDSnxaeg.7E4BiIGgOnKARcJGNMNZwVc8qNu cTL0x7YWvL5Wpf3rIxvsyXICxpjQa8qJ5Z7V3wHxTSvcVGOSjk3gz Received: from [69.58.249.58] by web162906.mail.bf1.yahoo.com via HTTP; Tue, 29 Jan 2013 06:15:36 PST X-Rocket-MIMEInfo: 001.001, SSBhbSB1c2luZyBGcmVlQlNEIDEwLUN1cnJlbnQgcjI0NTY3MyBhcyBhIGhvc3Qgb24gYW4gSFAgcDItMTM5NC7CoCBJIGhhdmUgdGhlIGhvc3QgT1MgaW5zdGFsbGVkIG9uIDEgZHJpdmUgdXNpbmcgVUZTIGFuZCBhIHNlY29uZCBkcml2ZSB1c2luZyBaRlMgd2l0aCBhIHBvb2wgbmFtZWQgJ3RhbmsuJ8KgIFRoZXkgbGF5b3V0IGZvciB6ZnMgZm9yIG15IGd1ZXN0IGluc3RhbGwgaXMgL3RhbmsvZ3Vlc3QwMS4KwqAKV2hlbiB1c2luZyB0aGUgY29tbWFuZDoKIyBiaHl2ZWxvYWQgLWQgL3RtcC9GcmVlQlNELTkBMAEBAQE- X-Mailer: YahooMailWebService/0.8.131.499 Message-ID: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> Date: Tue, 29 Jan 2013 06:15:36 -0800 (PST) From: G B Subject: BHyVe on 10-Current r245673 To: "current@freebsd.org" MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 29 Jan 2013 14:44:52 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: G B List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 14:15:38 -0000 I am using FreeBSD 10-Current r245673 as a host on an HP p2-1394.=A0 I have= the host OS installed on 1 drive using UFS and a second drive using ZFS wi= th a pool named 'tank.'=A0 They layout for zfs for my guest install is /tan= k/guest01.=0A=A0=0AWhen using the command:=0A# bhyveload -d /tmp/FreeBSD-9.= 1-RELEASE-amd64-disk1.iso -m 512 -h /tank/guest01 guest01 && bhyve -c 2 -a = -A -m 512 -g 0 -P -H -s 1,virtio-net,tap0 -s 2,virtio-blk,diskdev guest01 &= & sleep 20 && ifconfig tap0 up=0A=A0=0AI get the boot screen for FreeBSD 9.= 1 and after the timed pause it fails with:=0ACould not open backing file: N= o such file or directory=0AACPI tables require and ioapic=0AAssertion faile= d: (error =3D=3D 0), function main, file /usr/src/usr.sbin/bhyve/bhyverun.c= , line 774.=0AAbort (core dumped)=0Aroot@localhost:/tmp#=0A=A0=0AI am using= the bhyveload comamnd from a PDF I found from BSDCan but when I used the -= m 768 -M 1024 as used in the doc it failed with a syntax error, so I switch= ed to using just -m 512.=A0 My .iso is in /tmp as indicated in my command w= ith '-d'.=A0 =0A=A0=0AI'm guessing my command is wrong, but not sure where.= =A0 Any help would be appreciated.=A0 =0A=A0=0AThanks,=0AGary From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 14:54:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF4C73D8 for ; Tue, 29 Jan 2013 14:54:51 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9917CFD2 for ; Tue, 29 Jan 2013 14:54:51 +0000 (UTC) Received: from [10.1.3.105] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id E0DD51A07B7; Tue, 29 Jan 2013 14:54:50 +0000 (UTC) Message-ID: <5107E2B9.8090607@mail.lifanov.com> Date: Tue, 29 Jan 2013 09:54:49 -0500 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130109 Thunderbird/17.0.2 MIME-Version: 1.0 To: G B Subject: Re: BHyVe on 10-Current r245673 References: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> In-Reply-To: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 14:54:51 -0000 On 01/29/2013 09:15 AM, G B wrote: > I am using FreeBSD 10-Current r245673 as a host on an HP p2-1394. > I have the host OS installed on 1 drive using UFS and a second > drive using ZFS with a pool named 'tank.' They layout for zfs for > my guest install is /tank/guest01. > > When using the command: # bhyveload -d > /tmp/FreeBSD-9.1-RELEASE-amd64-disk1.iso -m 512 -h /tank/guest01 > guest01 && bhyve -c 2 -a -A -m 512 -g 0 -P -H -s 1,virtio-net,tap0 > -s 2,virtio-blk,diskdev guest01 && sleep 20 && ifconfig tap0 up > > I get the boot screen for FreeBSD 9.1 and after the timed pause it > fails with: Could not open backing file: No such file or directory > ACPI tables require and ioapic Assertion failed: (error == 0), > function main, file /usr/src/usr.sbin/bhyve/bhyverun.c, line 774. > Abort (core dumped) root@localhost:/tmp# > > I am using the bhyveload comamnd from a PDF I found from BSDCan but > when I used the -m 768 -M 1024 as used in the doc it failed with a > syntax error, so I switched to using just -m 512. My .iso is in > /tmp as indicated in my command with '-d'. > > I'm guessing my command is wrong, but not sure where. Any help > would be appreciated. > > Thanks, Gary _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > "diskdev" is your actual disk (i.e. -s > 2,virtio-blk,/dev/zvol/tank/guest01). Also, you need a zvol if you > are doing this. Also, "-h" in bhyveload specifies a directory with > a loader config, kernel, and modules. You definitely don't need it > with an ".iso" boot. Also, see examples here: http://mirrors.nycbug.org/pub/BHyVe/r244024/INSTRUCTIONS-COPYRIGHT.txt and files here: http://mirrors.nycbug.org/pub/BHyVe/r244024/ Also, check http://callfortesting.org/ for some more examples. - Nikolai Lifanov From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 14:58:23 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A350E5D2; Tue, 29 Jan 2013 14:58:23 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3746586; Tue, 29 Jan 2013 14:58:23 +0000 (UTC) Received: from [78.35.166.2] (helo=fabiankeil.de) by smtprelay05.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1U0Cdb-0002ju-CX; Tue, 29 Jan 2013 15:58:15 +0100 Date: Tue, 29 Jan 2013 15:52:50 +0100 From: Fabian Keil To: Dan Nelson Subject: Re: Zpool surgery Message-ID: <20130129155250.29d8f764@fabiankeil.de> In-Reply-To: <20130128214111.GA14888@dan.emsphone.com> References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> <20130127201140.GD29105@server.rulingia.com> <20130128085820.GR35868@acme.spoerlein.net> <20130128205802.1ffab53e@fabiankeil.de> <20130128214111.GA14888@dan.emsphone.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/WXg2ahZC0rmXbVAQa_iy9g/"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: Peter Jeremy , current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 14:58:23 -0000 --Sig_/WXg2ahZC0rmXbVAQa_iy9g/ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dan Nelson wrote: > In the last episode (Jan 28), Fabian Keil said: > > Ulrich Sp=C3=B6rlein wrote: > > > On Mon, 2013-01-28 at 07:11:40 +1100, Peter Jeremy wrote: > > > > On 2013-Jan-27 14:31:56 -0000, Steven Hartland wrote: > > > > >----- Original Message -----=20 > > > > >From: "Ulrich Sp=C3=B6rlein" > > > > >> I want to transplant my old zpool tank from a 1TB drive to a new > > > > >> 2TB drive, but *not* use dd(1) or any other cloning mechanism, as > > > > >> the pool was very full very often and is surely severely > > > > >> fragmented. > > > > > > > > > >Cant you just drop the disk in the original machine, set it as a > > > > >mirror then once the mirror process has completed break the mirror > > > > >and remove the 1TB disk. > > > >=20 > > > > That will replicate any fragmentation as well. "zfs send | zfs rec= v" > > > > is the only (current) way to defragment a ZFS pool. > >=20 > > It's not obvious to me why "zpool replace" (or doing it manually) > > would replicate the fragmentation. >=20 > "zpool replace" essentially adds your new disk as a mirror to the parent > vdev, then deletes the original disk when the resilver is done. Since > mirrors are block-identical copies of each other, the new disk will conta= in > an exact copy of the original disk, followed by 1TB of freespace. Thanks for the explanation. I was under the impression that zfs mirrors worked at a higher level than traditional mirrors like gmirror but there seems to be indeed less magic than I expected. Fabian --Sig_/WXg2ahZC0rmXbVAQa_iy9g/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEH4kgACgkQBYqIVf93VJ1Z4ACgsP2gJkFDDqwImnab1rnKF5Xu gc8AoJuwpBMZrXVyX8ZSboeS6co0PHOk =8PGU -----END PGP SIGNATURE----- --Sig_/WXg2ahZC0rmXbVAQa_iy9g/-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 14:59:15 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 765A2754 for ; Tue, 29 Jan 2013 14:59:15 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) by mx1.freebsd.org (Postfix) with ESMTP id 653DEAC for ; Tue, 29 Jan 2013 14:59:15 +0000 (UTC) Received: from [10.1.3.105] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id 8EDF319FE68; Tue, 29 Jan 2013 14:51:41 +0000 (UTC) Message-ID: <5107E1FC.1050504@mail.lifanov.com> Date: Tue, 29 Jan 2013 09:51:40 -0500 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130109 Thunderbird/17.0.2 MIME-Version: 1.0 To: G B Subject: Re: BHyVe on 10-Current r245673 References: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> In-Reply-To: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 14:59:15 -0000 On 01/29/2013 09:15 AM, G B wrote: > I am using FreeBSD 10-Current r245673 as a host on an HP p2-1394. > I have the host OS installed on 1 drive using UFS and a second > drive using ZFS with a pool named 'tank.' They layout for zfs for > my guest install is /tank/guest01. > > When using the command: # bhyveload -d > /tmp/FreeBSD-9.1-RELEASE-amd64-disk1.iso -m 512 -h /tank/guest01 > guest01 && bhyve -c 2 -a -A -m 512 -g 0 -P -H -s 1,virtio-net,tap0 > -s 2,virtio-blk,diskdev guest01 && sleep 20 && ifconfig tap0 up > > I get the boot screen for FreeBSD 9.1 and after the timed pause it > fails with: Could not open backing file: No such file or directory > ACPI tables require and ioapic Assertion failed: (error == 0), > function main, file /usr/src/usr.sbin/bhyve/bhyverun.c, line 774. > Abort (core dumped) root@localhost:/tmp# > > I am using the bhyveload comamnd from a PDF I found from BSDCan but > when I used the -m 768 -M 1024 as used in the doc it failed with a > syntax error, so I switched to using just -m 512. My .iso is in > /tmp as indicated in my command with '-d'. > > I'm guessing my command is wrong, but not sure where. Any help > would be appreciated. > > Thanks, Gary _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > "diskdev" is your actual disk (i.e. -s 2,virtio-blk,/dev/zvol/tank/guest01). Also, you need a zvol if you are doing this. Also, "-h" in bhyveload specifies a directory with a loader config, kernel, and modules. You definitely don't need it with an ".iso" boot. - Nikolai Lifanov From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 15:42:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4116F339; Tue, 29 Jan 2013 15:42:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 10AD82EC; Tue, 29 Jan 2013 15:42:33 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 74F34B91E; Tue, 29 Jan 2013 10:42:32 -0500 (EST) From: John Baldwin To: Ryan Stone Subject: Re: Why don't we check for preemption when we unlend priority? Date: Tue, 29 Jan 2013 09:59:36 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201301290959.37166.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 29 Jan 2013 10:42:32 -0500 (EST) Cc: Attilio Rao , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 15:42:33 -0000 On Friday, January 25, 2013 3:01:14 pm Ryan Stone wrote: > I'm having a problem where userland threads are running with a loaned (via > mutex priority propagation) priority even after they have released the > mutex. This is causing the low-priority userland thread to starve > high-priority interrupt threads. One scenario is(which I am seeing on > FreeBSD 8.2, but the priority lending code does not seem to have changed in > HEAD): > > 1) I have several swi threads that are pulling packets off of interfaces > and forwarding them. Each swi thread is pinned to a CPU. > > 2) A remote user initiates an scp of a large file to this machine. > > 3) sshd (which handles the scp) takes a mutex on its socket > > 4) An interrupt or taskqueue thread belonging to the driver that is > receiving the scp traffic tries to take the same mutex. It can't and so it > lends its priority to the sshd thread. > > 5) My swi thread is woken. It is pinned to the same CPU as sshd, but it > has a lower priority than the lent priority, so it is placed on the > runqueue. > > 6) The sshd thread releases the mutex. sched_unlend_prio is called to set > its priority back to a normal user priority. However, it does not check > whether any higher-priority threads are waiting in the runqueue. > > 7) The sshd thread is allowed to run for its full quantum (100ms). This is > easily long enough for my swi thread to start and I drop packets. Well, I think there is an implicit assumption that the only higher priority things are ones that are about to be woken up later in turnstile_unpend(). The order of operations in turnstile_unpend() should handle the case where one of the threads waiting on the lock needs your inherited priority. In the absence of CPU pinning this would indeed work correctly because if the current thread's priority is lowered, it is definitely going to preempt to the thread it borrowed it from, and when that thread finishes running it will examine the run queues to find which thread to run next. CPU pinning has broken that assumption however. I can't fully evaulate your patch, though sched_unlend_prio should only be called on curthread, so I think that your sched_check_preempt() should always see tdq == TDQ_SELF()? > diff --git a/sys/kern/sched_ule.c b/sys/kern/sched_ule.c > index 01559ee..2659614 100644 > --- a/sys/kern/sched_ule.c > +++ b/sys/kern/sched_ule.c > @@ -1586,6 +1586,22 @@ sched_pctcpu_update(struct td_sched *ts) > ts->ts_ftick = ts->ts_ltick - SCHED_TICK_TARG; > } > > +static void > +sched_check_preempt(struct tdq *tdq, struct thread *td) > +{ > + > + KASSERT(TD_IS_RUNNING(td), ("thread is not running")); > + TDQ_LOCK_ASSERT(tdq, MA_OWNED); > + KASSERT(tdq == TDQ_CPU(td->td_sched->ts_cpu), ("tdq does not td")); > + > + if (tdq == TDQ_SELF()) { > + if (td->td_priority > tdq->tdq_lowpri && > + sched_shouldpreempt(tdq->tdq_lowpri, td->td_priority, > 0)) > + td->td_owepreempt = 1; > + } else > + tdq_notify(tdq, td); > +} > + > /* > * Adjust the priority of a thread. Move it to the appropriate run-queue > * if necessary. This is the back-end for several priority related > @@ -1635,8 +1651,10 @@ sched_thread_priority(struct thread *td, u_char prio) > td->td_priority = prio; > if (prio < tdq->tdq_lowpri) > tdq->tdq_lowpri = prio; > - else if (tdq->tdq_lowpri == oldpri) > + else if (tdq->tdq_lowpri == oldpri) { > tdq_setlowpri(tdq, td); > + sched_check_preempt(tdq, td); > + } > return; > } > td->td_priority = prio; > -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 16:35:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 54EA1654 for ; Tue, 29 Jan 2013 16:35:56 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 227AC803 for ; Tue, 29 Jan 2013 16:35:55 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.6/8.14.6) with ESMTP id r0TGZsKu019037; Tue, 29 Jan 2013 08:35:54 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.6/8.14.6/Submit) id r0TGZsjf019036; Tue, 29 Jan 2013 08:35:54 -0800 (PST) (envelope-from david) Date: Tue, 29 Jan 2013 08:35:54 -0800 From: David Wolfskill To: "O. Hartmann" Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' Message-ID: <20130129163554.GW1804@albert.catwhisker.org> References: <51079F0A.20309@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y974o0GblB/Ae/yP" Content-Disposition: inline In-Reply-To: <51079F0A.20309@zedat.fu-berlin.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 16:35:56 -0000 --Y974o0GblB/Ae/yP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 29, 2013 at 11:06:02AM +0100, O. Hartmann wrote: > I receive this error since yesterday building world and it is still > sticky on most recent sources (r246057) and I was wondering why the > tinderboxes do not pick this up on the 10.0-CURRENT builds ... just for > a notice for the development folks ... > ...=20 > =3D=3D=3D> libexec/atf/atf-check (all) > ... > c++ -O3 -pipe -fno-strict-aliasing -march=3Dnative -march=3Dnative > -DHAVE_CONFIG_H -I/usr/src/libexec/atf/atf-check/../../../contrib/atf > -Qunused-arguments -fstack-protector -Wsystem-headers -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith > -Wno-uninitialized -Wno-empty-body -Wno-string-plus-int > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-conversion -stdlib=3Dlibc++ -std=3Dc++11 > -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++ > -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c -o > atf-check atf-check.o -latf-c++ -latf-c > /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to > `std::bad_alloc::~bad_alloc()' > /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf= -c++.so: > undefined reference to `std::bad_alloc::bad_alloc()' > /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf= -c++.so: > undefined reference to `std::bad_alloc::~bad_alloc()' > /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to > `std::bad_alloc::bad_alloc()' > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > *** [atf-check] Error code 1 >=20 > Stop in /usr/src/libexec/atf/atf-check. > *** [all] Error code 1 > ... In contrast, I don't see a problem; most recent head build I have is: FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1057 r= 246057M/246068: Tue Jan 29 07:29:55 PST 2013 root@freebeast.catwhisker.= org:/usr/obj/usr/src/sys/GENERIC i386 For reference, yesterday's was: FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1056 r= 246028M/246028: Mon Jan 28 06:49:44 PST 2013 root@freebeast.catwhisker.= org:/usr/obj/usr/src/sys/GENERIC i386 That said (and this may be relevant), I'm using clang/clang++ to build FreeBSD. Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Y974o0GblB/Ae/yP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEH+moACgkQmprOCmdXAD1sIACeLD24wF+QncFmOw/I1o6js8Um xxEAn1iShHpuZyx4tSXZ6hMW/93MdNaY =ydPH -----END PGP SIGNATURE----- --Y974o0GblB/Ae/yP-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 17:07:08 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1D133A1 for ; Tue, 29 Jan 2013 17:07:08 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-ia0-x233.google.com (mail-ia0-x233.google.com [IPv6:2607:f8b0:4001:c02::233]) by mx1.freebsd.org (Postfix) with ESMTP id 78B619AD for ; Tue, 29 Jan 2013 17:07:08 +0000 (UTC) Received: by mail-ia0-f179.google.com with SMTP id x24so887578iak.10 for ; Tue, 29 Jan 2013 09:07:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=WOXUqv+gu8YzXrvIpTlzjTtFJZgubis+BaGhEcM72s0=; b=fpKYwOUfViPpdlOFcu311ar37yoy+5KQ7P2eJ9+cgX/LN/DZWA2Wt44quXIHlC+ZnG S5pHHZiTeTDTDCAyAMqUV6zzcmHH4LglrCWCV/3/14Nc3+bp8u4xLYOmAYJXhGilsWhP t8/6ZIEmALQTuGwlPTwAmMv8e4Qf6yZDb40Oir/yWp7AcQDfv7bHKimqCA7jsF5crmt7 uYFnKWlq4mkJ73eeMUxeOszjtw5Tgdgs1Xl3RcLehY+PDQW9i5k3afSxkUpDjCoseZi9 hzohO+ycMeMjT4TOOWZkLQw2zu4WFm3+5kg87kqkyKZ19XVhqCLnz8alHjaSLdYQ0/fg ne+g== MIME-Version: 1.0 X-Received: by 10.50.170.69 with SMTP id ak5mr1280966igc.56.1359479227408; Tue, 29 Jan 2013 09:07:07 -0800 (PST) Received: by 10.43.112.194 with HTTP; Tue, 29 Jan 2013 09:07:07 -0800 (PST) In-Reply-To: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> References: <1359468936.78130.YahooMailNeo@web162906.mail.bf1.yahoo.com> Date: Tue, 29 Jan 2013 09:07:07 -0800 Message-ID: Subject: Re: BHyVe on 10-Current r245673 From: Neel Natu To: G B Content-Type: text/plain; charset=ISO-8859-1 Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 17:07:08 -0000 Hi Gary, On Tue, Jan 29, 2013 at 6:15 AM, G B wrote: > I am using FreeBSD 10-Current r245673 as a host on an HP p2-1394. I have the host OS installed on 1 drive using UFS and a second drive using ZFS with a pool named 'tank.' They layout for zfs for my guest install is /tank/guest01. > > When using the command: > # bhyveload -d /tmp/FreeBSD-9.1-RELEASE-amd64-disk1.iso -m 512 -h /tank/guest01 guest01 && bhyve -c 2 -a -A -m 512 -g 0 -P -H -s 1,virtio-net,tap0 -s 2,virtio-blk,diskdev guest01 && sleep 20 && ifconfig tap0 up > > I get the boot screen for FreeBSD 9.1 and after the timed pause it fails with: > Could not open backing file: No such file or directory > ACPI tables require and ioapic > Assertion failed: (error == 0), function main, file /usr/src/usr.sbin/bhyve/bhyverun.c, line 774. > Abort (core dumped) > root@localhost:/tmp# > > I am using the bhyveload comamnd from a PDF I found from BSDCan but when I used the -m 768 -M 1024 as used in the doc it failed with a syntax error, so I switched to using just -m 512. My .iso is in /tmp as indicated in my command with '-d'. > > I'm guessing my command is wrong, but not sure where. Any help would be appreciated. > Can you try out the following instructions to get you started? http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt The script that I use is pretty basic and has less bells and whistles than other howto guides out there. But that makes it easier to figure out what is happening under the hood. best Neel > Thanks, > Gary > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 18:42:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DAADD951 for ; Tue, 29 Jan 2013 18:42:33 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm38-vm7.bullet.mail.bf1.yahoo.com (nm38-vm7.bullet.mail.bf1.yahoo.com [72.30.239.23]) by mx1.freebsd.org (Postfix) with ESMTP id A915FF44 for ; Tue, 29 Jan 2013 18:42:32 +0000 (UTC) Received: from [98.139.214.32] by nm38.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 18:42:31 -0000 Received: from [98.139.213.4] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 18:42:31 -0000 Received: from [127.0.0.1] by smtp104.mail.bf1.yahoo.com with NNFMP; 29 Jan 2013 18:42:31 -0000 X-Yahoo-Newman-Id: 410131.83413.bm@smtp104.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: OxeNg.gVM1lW72Cv92OMgv0OekU8f5rG1a0oaQSU.oI4ipZ C_B6sFz7.3lzHwplcnvmMt7HvvXYPFkdtSNwGEr1Xj.zOfqVBNvNPgHqkPVi kLcF8YONL1g4_XD9vTzkorULYvTluqT351sCAySK4dySmkVDgGXyeLjuVX8j 87bdP46RCe0bU0y5S6edQstoiuS76aXN5aFr24rDv.KbBkBgkL_fJv6h_cTJ rNpDGpc7LTOyR0llr5QUrzNPKSFokKJV0PJG_AIlZHYf.E7fLa3TU4y5MkC7 dwUlk54ABVz3aAvvjpj1NXjvLAUhK4sM8fvHabF7BYDUXVQqotpIl2uAnhdQ PKBH1B.A3J6_DfIhfKG6UJ1NdOfD5p9v4GfkuBDGdG_yfBQmrwBuGUksOYy5 9TRcx3TisYPtzOtKfdcuy6kL4S90KZ0qTWloY7MRvofDQ2ABw2OIY6vlA7pz XfeEROY2oLsuC9pUGTKSwGWbQ0QBpXhNSs8j0B2f0Iug1GiYXaFBWv3C1LEo pzxHgIpz.uHSyhNIxLXgFfplcDjRP6EoFoYMUujCtNXV7yhzNgxhZCrkBgm3 NQ3TB5yXUjrCfK1Udkg-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf Received: from [192.168.10.102] (pfg@200.118.157.7 with plain) by smtp104.mail.bf1.yahoo.com with SMTP; 29 Jan 2013 10:42:31 -0800 PST Message-ID: <5108181D.9090805@FreeBSD.org> Date: Tue, 29 Jan 2013 13:42:37 -0500 From: Pedro Giffuni User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: [CFT] WITH_BSD_PATCH References: <201301291703.r0TH3JaO078248@svn.freebsd.org> In-Reply-To: <201301291703.r0TH3JaO078248@svn.freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 18:42:33 -0000 (Not sure the first announcement made it - Sorry if you get this twice) Fellow FreeBSD developers; As many of you may have noticed as of r246074 we have a new version of patch(1) in the tree! The brief history is this: - Larry Wall developed the first patch(1) implementation which was taken by the FSF and greatly enhanced into what today is GNU patch. - FreeBSD has been using an early version of GNU patch (2.1) and made some relatively small enhancements on it. Two of the files in FreeBSD are under the GPL. -OpenBSD took a very old version of patch (2.0) and started from there. The GPL'd files were replaced with PD or otherwise unrestricted versions. - The OpenBSD version was ported to DragonFly BSD and after further enhancements the DF version was also adopted by NetBSD. I took the DragonFly version and back-ported some of the changes that we had in the FreeBSD version. As a result the new "BSD patch" that is available as an option in the tree covers most of the functionality of the patch in FreeBSD with two exceptions: -I and -S. Both options seem to be obsolete and don't seem to be used in ports. Furthermore GNU and BSD patch already uses -I to ignore white spaces. The new version is expected to be a complete replacement for our previous GNU patch but has only been lightly tested. Please test extensively, report bugs, and submit patches. We would love to use the new patch by default in 10.0 but only testing will let us know when it's ready. Special thanks to: Christoph Mallon - for porting the perforce diff support. Gabor Kovesdan - for doing the import since he has experience bringing these jewels into tree :). Enjoy! Pedro. On 01/29/2013 12:03, Gabor Kovesdan wrote: > Author: gabor > Date: Tue Jan 29 17:03:18 2013 > New Revision: 246074 > URL: http://svnweb.freebsd.org/changeset/base/246074 > > Log: > - Add a BSD-licensed patch, ported by Pedro F. Giffuni (pfg) from > DragonflyBSD and install it as bsdpatch. WITH_BSD_PATCH makes it > default and installs GNU patch as gnupatch. > > Submitted by: pfg > Obtained from: The DragonflyBSD Project > > Added: > head/tools/build/options/WITH_BSD_PATCH (contents, props changed) > head/usr.bin/patch/ > head/usr.bin/patch/Makefile (contents, props changed) > head/usr.bin/patch/backupfile.c (contents, props changed) > head/usr.bin/patch/backupfile.h (contents, props changed) > head/usr.bin/patch/common.h (contents, props changed) > head/usr.bin/patch/inp.c (contents, props changed) > head/usr.bin/patch/inp.h (contents, props changed) > head/usr.bin/patch/mkpath.c (contents, props changed) > head/usr.bin/patch/patch.1 (contents, props changed) > head/usr.bin/patch/patch.c (contents, props changed) > head/usr.bin/patch/pathnames.h (contents, props changed) > head/usr.bin/patch/pch.c (contents, props changed) > head/usr.bin/patch/pch.h (contents, props changed) > head/usr.bin/patch/util.c (contents, props changed) > head/usr.bin/patch/util.h (contents, props changed) > Modified: > head/UPDATING > head/gnu/usr.bin/patch/Makefile > head/share/mk/bsd.own.mk > head/usr.bin/Makefile > From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 19:22:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EEBBD4FE for ; Tue, 29 Jan 2013 19:22:54 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by mx1.freebsd.org (Postfix) with ESMTP id A192E15C for ; Tue, 29 Jan 2013 19:22:54 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id j6so846895oag.36 for ; Tue, 29 Jan 2013 11:22:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mLnsmp9ZwooXgMGuYlNeN0ujLAB7GmWBecAyNv8TozI=; b=X1PKhpjeUcwcpTmg6IP+m+z2A1d/4WLcs1ng7uyo71J1QPpmozSfVrmTM5TLR03Rng Dk9qxGfjJM85MVMlwY+1o8ovw7/36bT9VxzgWR5gnazicCa4ezgREUzW8d1RAVxEhQO7 a3Fll+VPf2JHUh7Njud1esKVdXidGGybPLsRno4ECfullwmL2m2WbZY7zycMbCLB++n9 UWKAy1EAtEOfAcUBTi22MFfv9NexrtyDGd6KfY6jPGKhSw3XDTMKpl9/c7V46nAM1qIR +ETc91ateSO0YNZtZA8fjxlIKHgLNKOElErHKyvA3iew5kXgChZ7x1kG6uFwKLYHTne1 9O4Q== MIME-Version: 1.0 X-Received: by 10.60.170.242 with SMTP id ap18mr1613896oec.97.1359487368216; Tue, 29 Jan 2013 11:22:48 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.60.172.225 with HTTP; Tue, 29 Jan 2013 11:22:48 -0800 (PST) In-Reply-To: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Date: Tue, 29 Jan 2013 11:22:48 -0800 X-Google-Sender-Auth: 0VE8J7N2axDyAFKxiReI_jO9DJw Message-ID: Subject: Re: mounting root from NFS via ROOTDEVNAME From: Craig Rodrigues To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 19:22:55 -0000 On Tue, Jan 29, 2013 at 1:17 AM, Eggert, Lars wrote: > > On Jan 29, 2013, at 10:13, Lars Eggert > wrote: > > On Jan 29, 2013, at 9:34, Craig Rodrigues wrote: > > I had read both before, and they're very useful documents. Unfortunately, they don't fully apply to my case, since I'm not PXE-booting the system; it netboots the kernel from a custom loader. So once the kernel bootstraps, I need it to obtain an IP address and then NFS-mount root. > Hi, What kind of architecture are you trying to do this on? Is this i386/amd64 or something else? I am not familiar with netboot compared to PXE. Is TFTP involved at all with netboot? What does your dhcpd configuration file look like? Also, are you using the FreeBSD loader, or something else? What kinds of customizations have you done on the loader? If through your setup you have already managed to load the kernel over the network, then a lot of the hard work has been done. Telling the kernel where the root file system is located becomes the next tricky part. In src/sys/boot/common/boot.c which is part of the loader (not the kernel), if you look in the getrootmount() function, you will see that the loader will try to figure out where the root file system is by parsing /etc/fstab, and looking for the "/" mount. So, if your kernel is located in: /usr/home/elars/dst/boot/kernel/kernel Then create a file /usr/home/elars/dst/etc/fstab file with something like: # Device Mountpoint FSType Options Dump Pass 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 Alternatively, if you don't want to create an /etc/fstab file, then you could put something like this in your loader.conf file: vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst If you can get this to work without introducing new kernel options, that would be ideal, because the kernel options you are enabling are triggering behaviors. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 21:49:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF07318F; Tue, 29 Jan 2013 21:49:23 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 2BBCF98B; Tue, 29 Jan 2013 21:49:23 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id t57so707956wey.27 for ; Tue, 29 Jan 2013 13:49:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Ww/pUTMZkw3cuAPnlbO9gi00e5H5B2fLMgh/iMgvEoI=; b=V2EqUZN1kpdxwgaVPOfYAYcqnVYNnVpsHG8ZEFLjcK1zpGFdQLbhyg5lAr4PK13C9b GWDchcfp0ERAUf0n4VbrJXmHTUCwWVanFVohKjpN1dd7Y47QxrA2HO3h/TtAEmhexfIj VzTCgzZ7OT3Ra8gmN8O0ecgTRZgS7aMd4/ow8e5pWrgzuZ4lXWaXgvN87CU8lxfpowrj uewqb3vYKcrEzaSHjktRNfRrfucVJtJucCvLuQx/rfexl6vxhCoeQzwU9K7mUtc/H4An xzdyIuXrWOx7VLU1YUgv5FPHX6QQcrvy9K3cqDNGfd2nfisEHrr/BVMopnqnsDhxjT0G 5M8g== MIME-Version: 1.0 X-Received: by 10.180.72.232 with SMTP id g8mr5218404wiv.0.1359496161730; Tue, 29 Jan 2013 13:49:21 -0800 (PST) Received: by 10.194.41.10 with HTTP; Tue, 29 Jan 2013 13:49:21 -0800 (PST) In-Reply-To: <4F6126A2.7050301@mehnert.org> References: <4E836C06.9070405@gmail.com> <4E8374A7.90105@gmail.com> <4E9BDF13.4040006@gmail.com> <4F38211D.4070305@mehnert.org> <4F40A2D4.6000000@gmail.com> <4F57A8FC.8090106@gmail.com> <20120308092234.M18590@martymac.org> <4F5AC96A.3050600@gmail.com> <4F5FE9C1.7010901@gmail.com> <4F6020C0.60405@gmail.com> <4F6126A2.7050301@mehnert.org> Date: Tue, 29 Jan 2013 21:49:21 +0000 Message-ID: Subject: Re: x220 notes From: Andrey Fesenko To: Hannes Mehnert Content-Type: text/plain; charset=UTF-8 Cc: matt , Vrachnis Ilias-Dimitrios , freebsd-current@freebsd.org, freebsd-mobile@freebsd.org, Ganael LAPLANCHE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 21:49:23 -0000 On Wed, Mar 14, 2012 at 11:15 PM, Hannes Mehnert wrote: > Ciao, > > On 03/14/2012 00:38, matt wrote: >> I have brightness control through raw acpi..."\_BCL" and friends seem to >> do nothing. >> >> Most of the video methods differentiate between \VIGD (which seems to be >> a check for integrated graphics vs optimus, but that's still a guess) >> If \VIGD is true, brightness commands are sent to the EC, where they >> don't seem to do much yet. This is probably where we could enable >> something via EC/ibm-acpi? >> If \VIGD is false, brightness commands are handled in ACPI, although >> coarsely, via \VBRC. >> >> \VBRC seems to allow control over the backlight, at least, so those of >> you with sore eyes or the 3-cell battery may have some success using the >> acpi_call port (Danger!) >> kldload acpi_call >> acpi_call -p '\VBRC' -i n (where n is 0-10) > > Great news! Works for me. n is actually 0-16 (plus any other value which > turns the backlight off (-1 or 17 eg). > > > Thanks, > > Hannes Thanks, acpi_call -p '\VBRC' -i n [0-15] work fine, if set 17 black screen :) And other problems. 1) wi-fi standart rtl8192cu - not work change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS dev.acpi_ibm.0.wlan: 1 <- read only hardware switch work, not send mesage 2) sound # cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: (play/rec) pcm1: (play/rec) default pcm2: (play) pcm3: (play) pcm4: (play) sound headphones only, if set sysctl hw.snd.default_unit=0 and restart application, on's speakers (if remove headphones). Automatic switching possible? 2.2) sound control in mplayer automatic fine work multimedia key multimedia key and system mixer, and sysctl not work xev data VolUP, VolDn, mute (release event similar) KeyPress event, serial 27, synthetic NO, window 0x1e00001, root 0x120, subw 0x0, time 210234226, (623,634), root:(623,650), state 0x10, keycode 176 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x1e00001, root 0x120, subw 0x0, time 210235273, (623,634), root:(623,650), state 0x10, keycode 174 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 27, synthetic NO, window 0x1e00001, root 0x120, subw 0x0, time 210241638, (623,634), root:(623,650), state 0x10, keycode 140 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False 3) ACPI work poorly 19 1 0xffffffff81f01000 37c7 acpi_video.ko 20 1 0xffffffff81f05000 330f acpi_ibm.ko 21 1 0xffffffff81f09000 1fc acpi_call.ko # sysctl -a | grep ibm acpi_ibm0: on acpi0 acpi_ibm0: detached acpi_ibm0: on acpi0 dev.acpi_ibm.0.%desc: IBM ThinkPad ACPI Extras dev.acpi_ibm.0.%driver: acpi_ibm dev.acpi_ibm.0.%location: handle=\_SB_.PCI0.LPC_.EC__.HKEY dev.acpi_ibm.0.%pnpinfo: _HID=LEN0068 _UID=0 dev.acpi_ibm.0.%parent: acpi0 dev.acpi_ibm.0.initialmask: 2060 dev.acpi_ibm.0.availmask: 134217727 dev.acpi_ibm.0.events: 1 dev.acpi_ibm.0.eventmask: 134217727 dev.acpi_ibm.0.hotkey: 3353 dev.acpi_ibm.0.lcd_brightness: 0 <- not work dev.acpi_ibm.0.volume: 0 <- not work dev.acpi_ibm.0.mute: 0 <- not work dev.acpi_ibm.0.thinklight: 0 <- work fine :) dev.acpi_ibm.0.bluetooth: 0 <- work LED (bt not use, not test) dev.acpi_ibm.0.wlan: 1 <- read only dev.acpi_ibm.0.fan_speed: 3880 <- not work or read only dev.acpi_ibm.0.fan_level: 0 dev.acpi_ibm.0.fan: 1 LED HDD may be work blink infrequently SSD :) 3) video work acceptable WITH_NEW_XORG=true WITH_KMS=true from terminal adjustable brightness acpi_call -p '\VBRC' -i n [0-15] I would like to consolidate these actions on the standard key # cat /var/run/devd.pipe !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x10 ( Fn+Home) !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x11 (Fn+End) 4) mouse Xorg with out config standard trackpad and other work fine if hook up USB mouse not work Jan 27 17:53:23 x220 kernel: ugen1.3: at usbus1 Jan 27 17:53:23 x220 kernel: ums0: on usbus1 Jan 27 17:53:23 x220 kernel: ums0: 8 buttons and [XYZ] coordinates ID=0 and disconnect Jan 27 17:53:42 x220 kernel: ugen1.3: at usbus1 (disconnected) Jan 27 17:53:42 x220 kernel: ums0: at uhub3, port 2, addr 3 (disconnected) 5) suspend/resume not test while, if there is a manual will be grateful Trick, to work without xorg.conf :) # cat /home/andrey/.xsession /usr/local/bin/xset +fp /usr/local/lib/X11/fonts/terminus-font/ <- need some applications xkbset -b <- hate beep setxkbmap -layout "us,ru" -option "grp:caps_toggle,grp_led:caps" <- for two layouts and indication ... <-favorite WM % uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r245946: Sat Jan 26 19:54:05 UTC 2013 root@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 kernel generic+wifi(n-mode) and ipfw dmesg http://www.nycbug.org/?action=dmesgd&dmesgid=2434 From owner-freebsd-current@FreeBSD.ORG Tue Jan 29 22:16:08 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 761AFA9D for ; Tue, 29 Jan 2013 22:16:08 +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 EFCDBB34 for ; Tue, 29 Jan 2013 22:16:07 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r0TMG1l9075897; Tue, 29 Jan 2013 23:16:01 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r0TMG0Lc075896; Tue, 29 Jan 2013 23:16:00 +0100 (CET) (envelope-from marius) Date: Tue, 29 Jan 2013 23:16:00 +0100 From: Marius Strobl To: Konstantin Belousov Subject: Re: Fast gettimeofday(2) and static linking Message-ID: <20130129221600.GG85306@alchemy.franken.de> References: <20130125123554.GQ2522@kib.kiev.ua> <20130128154516.GA59472@alchemy.franken.de> <20130128155524.GS2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130128155524.GS2522@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 22:16:08 -0000 On Mon, Jan 28, 2013 at 05:55:24PM +0200, Konstantin Belousov wrote: > On Mon, Jan 28, 2013 at 04:45:17PM +0100, Marius Strobl wrote: > > On Fri, Jan 25, 2013 at 02:35:54PM +0200, Konstantin Belousov wrote: > > > Bruce Evans reported that statically linked binaries on HEAD an stable/9 > > > use the syscall for gettimeofday(2) and clock_gettime(2). Apparently, this > > > is due to my use of the weak reference to the __vdso* symbols in the > > > libc implementations. > > > > > > Patch below reworks the __vdso* attributes to only make the symbols > > > weak, but keep the references strong. Since I have to add a stub for > > > each architecture, I would like to ask non-x86 machines owners to test > > > the patch. > > > > > > > Hi Konstantin, > > > > what's the appropriate way to test this? > > Please rebuild the world with the patch and check that gettimeofday(2) still > works on your architecture, both for the static and dynamic binaries. > I think that just booting multiuser is enough. Okay, looks good on sparc64 (tested with a dynamically as well as a statically built time(1)). Marius From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 06:13:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 90FA8F67 for ; Wed, 30 Jan 2013 06:13:03 +0000 (UTC) (envelope-from alie@affle.com) Received: from mail-qc0-f175.google.com (mail-qc0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 324E1F44 for ; Wed, 30 Jan 2013 06:13:02 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id j3so573012qcs.6 for ; Tue, 29 Jan 2013 22:12:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=sHGfT4XNPcCfm+NkjCAxyM0aW4ZFxndkwXec7426a2A=; b=M6enN2VOQ/JC658q8BIhJpTVDqdEgkuIP7BwX3SIqgG3jwxBDeQwWhuzbNQLAZ5jua 9RNkOXyKNiADqLoSabjv8wctM/TuUfi8eB50esoJM2OheiTFKr7uIBOg/iEavrWtaZlg SNhHiLtBZ5mPcDSYR+8BVfyv5aqAWP3xzcdicNmkhtl7jXr2IbzTsn1oJ6P36JmKL85c g02tHRb9ODb2HiJsX73lFOLKvYGwReAWDA3a+6PPv4N5t03Qd1kVxKZYi/mVjuLakSjX UlnQaMndOQxug4rBmsgIUai2KXCOvVfp0RsAcNKznp8+AiKFbZeUJUOkxM1MbQNqXW61 4goQ== MIME-Version: 1.0 X-Received: by 10.224.39.210 with SMTP id h18mr3842449qae.15.1359526376460; Tue, 29 Jan 2013 22:12:56 -0800 (PST) Received: by 10.49.2.72 with HTTP; Tue, 29 Jan 2013 22:12:56 -0800 (PST) Date: Wed, 30 Jan 2013 14:12:56 +0800 Message-ID: Subject: Missing compile_et and kerberos breaks buildworld From: Alie Tan To: freebsd-current@freebsd.org X-Gm-Message-State: ALoCoQm3ZtVFvGwBX10eQTASO43Yyk3z99CYADP9oACYerT8ginWA0WBjWhELe6ORfuSjwevYW4+ Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 06:13:03 -0000 Hi, Is there any way to fix this issue? This issue happens when I compile world without KRB then re-enable again for second compilation. I have to disable KRB with WITHOUT_KERBEROS=yes for me to compile the world :-( Regards, Alie T From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 06:28:19 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0ECA945C for ; Wed, 30 Jan 2013 06:28:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7C8ABFDB for ; Wed, 30 Jan 2013 06:28:18 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r0U6S85g036416; Wed, 30 Jan 2013 08:28:08 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r0U6S85g036416 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r0U6S8WJ036415; Wed, 30 Jan 2013 08:28:08 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 30 Jan 2013 08:28:08 +0200 From: Konstantin Belousov To: Marius Strobl Subject: Re: Fast gettimeofday(2) and static linking Message-ID: <20130130062808.GZ2522@kib.kiev.ua> References: <20130125123554.GQ2522@kib.kiev.ua> <20130128154516.GA59472@alchemy.franken.de> <20130128155524.GS2522@kib.kiev.ua> <20130129221600.GG85306@alchemy.franken.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+yR+/VMiVFvFdL5Q" Content-Disposition: inline In-Reply-To: <20130129221600.GG85306@alchemy.franken.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 06:28:19 -0000 --+yR+/VMiVFvFdL5Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 29, 2013 at 11:16:00PM +0100, Marius Strobl wrote: > On Mon, Jan 28, 2013 at 05:55:24PM +0200, Konstantin Belousov wrote: > > Please rebuild the world with the patch and check that gettimeofday(2) = still > > works on your architecture, both for the static and dynamic binaries. > > I think that just booting multiuser is enough. >=20 > Okay, looks good on sparc64 (tested with a dynamically as well as a > statically built time(1)). Thank you very much. --+yR+/VMiVFvFdL5Q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRCL13AAoJEJDCuSvBvK1BfAgP/2uhO1eShgDFYxaT/zgIIyxE hIOcNwUrpho3yaRpE6Knb0as6dF8V3qO/1tuohtxHoog64wzv3XOeV8DJBwwEmFj wHl7oS8V6tbPybFa0cpsFiZOZoFKYKYc4DW8wBXv088L7+MuNZF8Xcvox/TSH8Yp nE1GZL3xW05hY+tDO2feRfUSBH9KcZ1zRRWbLgYWDcp4QzqvyaoFDwVoPvWr726U z0uUOuN5ZQ7dStTqJfTBqAr3zHK3gWFDi/nAbXWv24OL6140gxPVVZ2RPIf9yuSo uF3vth7w8XoRRGYKREghVcv1CKUJB6vRNWIaoab+83uskrEO94tplIniTgxs6ATX mzCAsnnZRDZOx0fp7yWFHm0+2sCvBIoOodXQNWuh+W7g2U3j/+0Yae5xu1yHKTwp DVfotbd+1qi/+MYsoaTZ3Xt+9ltD5d8VNN9cO6aIDIuQhcKsoOJH3OE573u9uQDs 6qKOO26OzdG9vdtu7lGRXfEg/hf01L+JMLUDLu+L8iLr7Ii29/+b4Q5BYmSJgm+L P9b0bPucQ5u7xN0em8FTN4JAOdlaB8mwecWm8IeHkf2I+1JPf+/STr24qCgzezMw IDNzwhJrLuSrtDx3mKBPn+HpKTBjrUy/YgXZQEhHMH0aZqR1knKLoHNE3odS1Xvg XRM8kuIfXPcXjOwxVcz2 =bL9u -----END PGP SIGNATURE----- --+yR+/VMiVFvFdL5Q-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 07:21:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 322BA1C5; Wed, 30 Jan 2013 07:21:03 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from mx.lissyara.su (mx.lissyara.su [91.227.18.11]) by mx1.freebsd.org (Postfix) with ESMTP id C5127255; Wed, 30 Jan 2013 07:21:02 +0000 (UTC) Received: from [195.93.240.5] (port=19895 helo=lissyara.moskb.local) by mx.lissyara.su with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80 (FreeBSD)) (envelope-from ) id 1U0Rjp-0005Wd-DB; Wed, 30 Jan 2013 11:05:41 +0400 Message-ID: <5108C645.80001@lissyara.su> Date: Wed, 30 Jan 2013 11:05:41 +0400 From: Alex Keda User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; ru-RU; rv:1.8.1.23) Gecko/20091202 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: hardware@freebsd.org, freebsd-drivers@freebsd.org, freebsd-current@freebsd.org Subject: FreeBSD 9.1 - not work IPMI Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-White-List: YES X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: mx.lissyara.su X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 07:21:03 -0000 srv3# dmesg -a | grep -i ipmi ipmi0: on isa0 ipmi0: KCS mode found at io 0xca2 alignment 0x1 on isa ipmi0: Timed out waiting for GET_DEVICE_ID srv3# ll /dev/ipmi* ls: No match. srv3# srv3# uname -a FreeBSD srv3.host-food.ru 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Wed Dec 5 04:53:34 MSK 2012 toor@srv3.host-food.ru:/usr/obj/usr/src/sys/HOST-FOOD amd64 srv3# not work on HP Proliant DL165 G7, SuperMicro AS-1022G-URF work on Tyan B8236G24W4HR-IL before update, on 8.3, it work on all From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 09:32:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C0E91A9 for ; Wed, 30 Jan 2013 09:32:27 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 4DA4DA2F for ; Wed, 30 Jan 2013 09:32:26 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,566,1355126400"; d="scan'208";a="14041674" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 30 Jan 2013 01:32:26 -0800 Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0U9WQAF021140; Wed, 30 Jan 2013 01:32:26 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0328.009; Wed, 30 Jan 2013 01:32:25 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYA= Date: Wed, 30 Jan 2013 09:32:25 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <5EF283655378804F86C58C3F6E4CA976@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 09:32:27 -0000 Hi, On Jan 29, 2013, at 20:22, Craig Rodrigues wrote: > What kind of architecture are you trying to do this on? Is this > i386/amd64 or something else? amd64 > I am not familiar with netboot compared to > PXE. Is TFTP involved at all with netboot? TFTP is not involved. The kernel gets booted by our custom loader (over HTT= P) and the root FS is supposed to be mounted over NFS. > What does your dhcpd configuration file look like? Completely standard, with the addition of a "root-path" option. (Which I wo= uld like to get rid of by setting ROOTDEVNAME in the kernel.) > Also, are you using the FreeBSD loader, or something else? What kinds of > customizations have you done on the loader? Custom loader.=20 > If through your setup you have already managed to load the kernel over > the network, then a lot of the hard work has been done. Telling the kern= el > where the root file system is located becomes the next tricky part. Right, that's the step I am struggeling with.=20 > In src/sys/boot/common/boot.c which is part of the loader (not the kernel= ), > if you look in the getrootmount() function, > you will see that the loader will try to figure out where the root file > system > is by parsing /etc/fstab, and looking for the "/" mount. >=20 > So, if your kernel is located in: >=20 > /usr/home/elars/dst/boot/kernel/kernel >=20 > Then create a file /usr/home/elars/dst/etc/fstab file with something like= : >=20 > # Device Mountpoint FSType > Options Dump Pass > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 = 0 Thanks, will try that! > Alternatively, if you don't want to create an /etc/fstab file, then > you could put something like this in your loader.conf file: >=20 > vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst Will try that too, but not sure if this works with our custom loader. Lars >=20 > If you can get this to work without introducing new kernel options, > that would be ideal, because the kernel options you are > enabling are triggering behaviors. >=20 > -- > Craig Rodrigues > rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 09:43:34 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CAA2F5F1; Wed, 30 Jan 2013 09:43:34 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3A1EAAC8; Wed, 30 Jan 2013 09:43:34 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.6/8.14.6) with ESMTP id r0U9hQMG090453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 30 Jan 2013 10:43:26 +0100 (CET) (envelope-from uqs@FreeBSD.org) Date: Wed, 30 Jan 2013 10:43:26 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Fabian Keil Subject: Re: Zpool surgery Message-ID: <20130130094326.GT35868@acme.spoerlein.net> Mail-Followup-To: Fabian Keil , Dan Nelson , Peter Jeremy , current@freebsd.org, fs@freebsd.org References: <20130127103612.GB38645@acme.spoerlein.net> <1F0546C4D94D4CCE9F6BB4C8FA19FFF2@multiplay.co.uk> <20130127201140.GD29105@server.rulingia.com> <20130128085820.GR35868@acme.spoerlein.net> <20130128205802.1ffab53e@fabiankeil.de> <20130128214111.GA14888@dan.emsphone.com> <20130129155250.29d8f764@fabiankeil.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130129155250.29d8f764@fabiankeil.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Peter Jeremy , Dan Nelson , current@freebsd.org, fs@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 09:43:34 -0000 On Tue, 2013-01-29 at 15:52:50 +0100, Fabian Keil wrote: > Dan Nelson wrote: > > > In the last episode (Jan 28), Fabian Keil said: > > > Ulrich Spörlein wrote: > > > > On Mon, 2013-01-28 at 07:11:40 +1100, Peter Jeremy wrote: > > > > > On 2013-Jan-27 14:31:56 -0000, Steven Hartland wrote: > > > > > >----- Original Message ----- > > > > > >From: "Ulrich Spörlein" > > > > > >> I want to transplant my old zpool tank from a 1TB drive to a new > > > > > >> 2TB drive, but *not* use dd(1) or any other cloning mechanism, as > > > > > >> the pool was very full very often and is surely severely > > > > > >> fragmented. > > > > > > > > > > > >Cant you just drop the disk in the original machine, set it as a > > > > > >mirror then once the mirror process has completed break the mirror > > > > > >and remove the 1TB disk. > > > > > > > > > > That will replicate any fragmentation as well. "zfs send | zfs recv" > > > > > is the only (current) way to defragment a ZFS pool. > > > > > > It's not obvious to me why "zpool replace" (or doing it manually) > > > would replicate the fragmentation. > > > > "zpool replace" essentially adds your new disk as a mirror to the parent > > vdev, then deletes the original disk when the resilver is done. Since > > mirrors are block-identical copies of each other, the new disk will contain > > an exact copy of the original disk, followed by 1TB of freespace. > > Thanks for the explanation. > > I was under the impression that zfs mirrors worked at a higher > level than traditional mirrors like gmirror but there seems to > be indeed less magic than I expected. > > Fabian To wrap this up, while the zpool replace worked for the disk, I played around with it some more, and using snapshots instead *did* work the second time. I'm not sure what I did wrong the first time ... So basically this: # zfs send -R oldtank@2013-01-22 | zfs recv -F -d newtank (takes ages, then do a final snapshot before unmounting and send the incremental) # zfs send -R -i 2013-01-22 oldtank@2013-01-29 | zfs recv -F -d newtank Allows me to send snapshots up to 2013-01-29 to the "archive" pool from either oldtank or newtank. Yay! Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 10:11:35 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 910FEA75 for ; Wed, 30 Jan 2013 10:11:35 +0000 (UTC) (envelope-from sergey.dyatko@gmail.com) Received: from mail-ee0-f41.google.com (mail-ee0-f41.google.com [74.125.83.41]) by mx1.freebsd.org (Postfix) with ESMTP id 03591CB4 for ; Wed, 30 Jan 2013 10:11:34 +0000 (UTC) Received: by mail-ee0-f41.google.com with SMTP id c13so729367eek.0 for ; Wed, 30 Jan 2013 02:11:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:x-mailer:mime-version :content-type:content-transfer-encoding; bh=XqGMILGh4LqB3ixXUko+Vs+/2W/7XgXF5C/JsN2cO0Y=; b=Om07A8JwnEio/xU55M80JqYLVUF3mA4JYlMI0BPNNv71knO5GN8yA6s7DrwHZjkzer 2Q8CXFM2XQK+69cOeTa/7HzsL/IOQBspK303q1rN2Dlh5A4vfU5fgoRXROl86cg0QMgM qQXgqOvk+7FaVZCXg3KciD/aLjX/1QQXViPVgk0a9JOtZU4+ct7/OnCq2UNgG7t1BH0I fvY4ty1xaOojf+jsOeLDoHPx2bjbtY+efJKmX6X8r/ZyS8MB0YsYPQXYCLUUr8SSJ5vq 8gM54KPjdQZkHHjlsUwXYhVVKlrteuOuyM+bn/eLc2JPtpa/+d3y/rs45vuOdCm+XhXb jFuA== X-Received: by 10.14.210.132 with SMTP id u4mr13097113eeo.19.1359540687901; Wed, 30 Jan 2013 02:11:27 -0800 (PST) Received: from laptop (m-s.agava.net. [195.222.84.203]) by mx.google.com with ESMTPS id l3sm1182773een.14.2013.01.30.02.11.26 (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 30 Jan 2013 02:11:26 -0800 (PST) Date: Wed, 30 Jan 2013 13:11:30 +0300 From: "Sergey V. Dyatko" To: Subject: stable/8 to HEAD Message-ID: <20130130131130.69fc8e48@laptop> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 10:11:35 -0000 Hi, Possible stupid question, but.. Can I update my stable/8 r228757 to HEAD? sandbox# svnversion 246112 sandbox# cat /etc/src.conf WITHOUT_PROFILE=YES WITHOUT_GAMES=YES WITHOUT_BLUETOOTH=YES WITHOUT_FREEBSD_UPDATE=YES WITHOUT_LPR=YES WITHOUT_NDIS=YES WITHOUT_WPA_SUPPLICANT_EAPOL=YES WITHOUT_WIRELESS_SUPPORT=YES WITHOUT_WIRELESS=YES sandbox# cat /etc/make.conf # added by use.perl 2011-01-12 09:43:24 PERL_VERSION=5.10.1 sandbox# make buildworld [skipped] ===> usr.bin/lex/lib (all) cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/usr.bin/lex/lib/libmain.c -o libmain.o cc -O2 -pipe -std=gnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/usr.bin/lex/lib/libyywrap.c -o libyywrap.o building static ln library ranlib libln.a sh /usr/src/tools/install.sh -s -o root -g wheel -m 555 lex /usr/obj/usr/src/tmp/legacy/usr/bin sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/tmp/legacy/usr/include ===> usr.bin/lex/lib (install) sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libln.a /usr/obj/usr/src/tmp/legacy/usr/lib /usr/obj/usr/src/tmp/legacy/usr/lib/libl.a -> /usr/obj/usr/src/tmp/legacy/usr/lib/libln.a /usr/obj/usr/src/tmp/legacy/usr/lib/libfl.a -> /usr/obj/usr/src/tmp/legacy/usr/lib/libln.a /usr/obj/usr/src/tmp/legacy/usr/bin/lex++ -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex /usr/obj/usr/src/tmp/legacy/usr/bin/flex -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex /usr/obj/usr/src/tmp/legacy/usr/bin/flex++ -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex ===> usr.bin/xinstall (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/usr.bin/xinstall created for /usr/src/usr.bin/xinstall rm -f .depend mkdep -f .depend -a -I/usr/src/usr.bin/xinstall/../../contrib/mtree -I/usr/src/usr.bin/xinstall/../../lib/libnetbsd -I/usr/obj/usr/src/tmp/legacy/usr/include -std=gnu99 /usr/src/usr.bin/xinstall/xinstall.c /usr/src/usr.bin/xinstall/../../contrib/mtree/getid.c /usr/src/usr.bin/xinstall/xinstall.c:64:20: error: sha512.h: No such file or directory mkdep: compile failed *** [.depend] Error code 1 Stop in /usr/src/usr.bin/xinstall. *** [bootstrap-tools] Error code 1 Stop in /usr/src. *** [_bootstrap-tools] Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- wbr, tiger From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 11:18:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EE506CAB for ; Wed, 30 Jan 2013 11:18:21 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by mx1.freebsd.org (Postfix) with ESMTP id C9A4D94 for ; Wed, 30 Jan 2013 11:18:21 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,567,1355126400"; d="scan'208";a="7395983" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 30 Jan 2013 03:18:15 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0UBIF0n011523; Wed, 30 Jan 2013 03:18:15 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Wed, 30 Jan 2013 03:18:15 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAB2QgA== Date: Wed, 30 Jan 2013 11:18:14 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <1D18576AD0CF1B45B1A8358AA4F6CE08@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 11:18:22 -0000 Hi, On Jan 30, 2013, at 10:32, "Eggert, Lars" wrote: > On Jan 29, 2013, at 20:22, Craig Rodrigues wrote= : >> In src/sys/boot/common/boot.c which is part of the loader (not the kerne= l), >> if you look in the getrootmount() function, >> you will see that the loader will try to figure out where the root file >> system >> is by parsing /etc/fstab, and looking for the "/" mount. >>=20 >> So, if your kernel is located in: >>=20 >> /usr/home/elars/dst/boot/kernel/kernel >>=20 >> Then create a file /usr/home/elars/dst/etc/fstab file with something lik= e: >>=20 >> # Device Mountpoint FSType >> Options Dump Pass >> 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 = 0 >=20 > Thanks, will try that! doesn't work. The kernel never leaves the "DHCP/BOOTP timeout for server"-loop unless I h= and out a root-path option via DHCP. I tried your tip above, I tried setting ROOTDEVNAME in the kernel, I create= d a /boot.config with "-r" in it on the NFS root - all to no avail.=20 >> Alternatively, if you don't want to create an /etc/fstab file, then >> you could put something like this in your loader.conf file: >>=20 >> vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst >=20 > Will try that too, but not sure if this works with our custom loader. Doesn't seem to work either. Lars= From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 11:22:41 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EE44BDEB for ; Wed, 30 Jan 2013 11:22:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4BCB6C9 for ; Wed, 30 Jan 2013 11:22:41 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r0UBMaKV070442; Wed, 30 Jan 2013 13:22:36 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r0UBMaKV070442 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r0UBMaO7070441; Wed, 30 Jan 2013 13:22:36 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 30 Jan 2013 13:22:36 +0200 From: Konstantin Belousov To: "Sergey V. Dyatko" Subject: Re: stable/8 to HEAD Message-ID: <20130130112236.GC2522@kib.kiev.ua> References: <20130130131130.69fc8e48@laptop> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OUxsNpkpJxkQzCsS" Content-Disposition: inline In-Reply-To: <20130130131130.69fc8e48@laptop> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 11:22:42 -0000 --OUxsNpkpJxkQzCsS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 30, 2013 at 01:11:30PM +0300, Sergey V. Dyatko wrote: > Hi, >=20 > Possible stupid question, but.. Can I update my stable/8 r228757 to > HEAD?=20 You need at least r231588. Generally, only updates from the latest last stable branches are supported, i.e. latest stable/9. =46rom the hand-on experience, it does work to update from even a year-old stable/8, assuming you do make all install in the _latest_ checkout of stable/8/lib/libmd and add auditdistd user. >=20 > sandbox# svnversion > 246112 > sandbox# cat /etc/src.conf > WITHOUT_PROFILE=3DYES > WITHOUT_GAMES=3DYES > WITHOUT_BLUETOOTH=3DYES > WITHOUT_FREEBSD_UPDATE=3DYES > WITHOUT_LPR=3DYES > WITHOUT_NDIS=3DYES > WITHOUT_WPA_SUPPLICANT_EAPOL=3DYES > WITHOUT_WIRELESS_SUPPORT=3DYES > WITHOUT_WIRELESS=3DYES >=20 > sandbox# cat /etc/make.conf > # added by use.perl 2011-01-12 09:43:24 > PERL_VERSION=3D5.10.1 >=20 > sandbox# make buildworld >=20 > [skipped] > =3D=3D=3D> usr.bin/lex/lib (all) > cc -O2 -pipe -std=3Dgnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include > -c /usr/src/usr.bin/lex/lib/libmain.c -o libmain.o cc -O2 -pipe > -std=3Dgnu99 -I/usr/obj/usr/src/tmp/legacy/usr/include > -c /usr/src/usr.bin/lex/lib/libyywrap.c -o libyywrap.o building static > ln library ranlib libln.a sh /usr/src/tools/install.sh -s -o root -g > wheel -m 555 lex /usr/obj/usr/src/tmp/legacy/usr/bin > sh /usr/src/tools/install.sh -C -o root -g wheel -m > 444 /usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/tmp/legacy/usr/inc= lude > =3D=3D=3D> usr.bin/lex/lib (install) sh /usr/src/tools/install.sh -C -o r= oot > -g wheel -m 444 > libln.a /usr/obj/usr/src/tmp/legacy/usr/lib /usr/obj/usr/src/tmp/legacy/u= sr/lib/libl.a > -> /usr/obj/usr/src/tmp/legacy/usr/lib/libln.a /usr/obj/usr/src/tmp/legac= y/usr/lib/libfl.a > -> /usr/obj/usr/src/tmp/legacy/usr/lib/libln.a /usr/obj/usr/src/tmp/legac= y/usr/bin/lex++ > -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex /usr/obj/usr/src/tmp/legacy/us= r/bin/flex > -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex /usr/obj/usr/src/tmp/legacy/us= r/bin/flex++ > -> /usr/obj/usr/src/tmp/legacy/usr/bin/lex =3D=3D=3D> usr.bin/xinstall > (obj,depend,all,install) /usr/obj/usr/src/tmp/usr/src/usr.bin/xinstall > created for /usr/src/usr.bin/xinstall rm -f .depend mkdep -f .depend > -a -I/usr/src/usr.bin/xinstall/../../contrib/mtree > -I/usr/src/usr.bin/xinstall/../../lib/libnetbsd > -I/usr/obj/usr/src/tmp/legacy/usr/include > -std=3Dgnu99 /usr/src/usr.bin/xinstall/xinstall.c /usr/src/usr.bin/xins= tall/../../contrib/mtree/getid.c /usr/src/usr.bin/xinstall/xinstall.c:64:20: > error: sha512.h: No such file or directory mkdep: compile failed *** > [.depend] Error code 1 >=20 > Stop in /usr/src/usr.bin/xinstall. > *** [bootstrap-tools] Error code 1 >=20 > Stop in /usr/src. > *** [_bootstrap-tools] Error code 1 >=20 > Stop in /usr/src. > *** Error code 1 >=20 > Stop in /usr/src. >=20 > --=20 > wbr, tiger > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --OUxsNpkpJxkQzCsS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRCQJ7AAoJEJDCuSvBvK1BvrwP/iZFxC3MNBJ7ESYvtj8vngfu C5fydKL2J2Lg/MoO8K7/MWxrehD2BHLicGd+FUKrGqxFenrjFM/sTl8XpxKso2t2 AyzlMV0xJ6nTW/sy5B3WsYco3TWIJk3uWzk+KEK6bzBElUbS4hJOL9WPsehDiwrP g87tesyAimXjLRh5UePXy1CV2bXIu1yCJfd22sAadMK3Cgji97g5EQPPK38umFYA hETkNP4Sn5DzdLMGcy8ya8V0Km9zF6ce3M+YgYAdWb8dFQ59vT6uaAsThsjOVf/l iW89YuLmr4RTyuyrjzsaaoWnGxUjzbM6tC4rRBPsojgGPAwdGgzvzqZzxJwnIbMK HUycqxCeU4AbsnoEzLj7XuQ3AJmCC+2l86PzFykddPSLBoV2g6m0D+rsC+xDzudc DoJ3mjTD8kA7T8C5S4Fu+izP0FdGm9M+qszc8XC1WtYJ9bpUcwLcuSG9vd3SZ8ol cdmj2/dfUtZ6i7oi2w918tKEOlIx3XExKpVZiRI5oxd2ckjn2C6LEo5vQWkS+WAZ 4rzT6/aKVezjUWkpAs6G8+abbYAnznUOgqYf2/qXiFkjeguLcFtsmeK7fhllNrw9 pTaxrX7JN23iNy7X51qbldikutAyGjsi3aB9XjNhiqI/W5KVVJXjzf1ERuWk+B3C WrPBZOeVeG2t/Nbb38FE =wpXQ -----END PGP SIGNATURE----- --OUxsNpkpJxkQzCsS-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 11:49:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 73D52560 for ; Wed, 30 Jan 2013 11:49:13 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id D8FA7234 for ; Wed, 30 Jan 2013 11:49:12 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id s43so1094847wey.21 for ; Wed, 30 Jan 2013 03:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type; bh=UlMSVnAPkdEHRbFI6p7lNpdvER1A91r0fdliPq+xPOI=; b=D1yJYCwuu9wMVS5hKJE4I899WYoawdK2NnGdCa+CKY9zg8NI9i+ovdhW/yKpawoEyq OvxohWUVWDy1cb8sZKjmMLEcTZvF6xTOg9I43fPfSW+IPb/a0JOcWtkFZedD95bdeQC2 90iNjhOixMuJxLUhE0rRuZYAt4RU34rVec1bQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=UlMSVnAPkdEHRbFI6p7lNpdvER1A91r0fdliPq+xPOI=; b=WgUDgx/HILv72+QWotW2HUcvpOdBn9nkNgHUzCO9ml3KF9cOqZu8JUoZ9mxVeAHFOz liUID1I/oix1yRvvHoawDZhUwVHtN3dyjmxVraudykdmixTSTDw8jdZ/1li0wwCKybXK LVo9ZzOTSJfQaBzhvwm473dgPnszveKe7BI7DSxgKugpDt38aOQlu0pad9cNEIsGZBGE bULNeqPZeGavx6jRj1LRYgbrMGKMsncwnImaVy7MPyy81GHrCXX+4qIS0Jh65OiMqqhg R7iDKTAaj0EifQEeX5EeGPW+54BzSU1KXfSxJPK2kbgZ1XvGpwmiArgdz/tbKh6CYkHA vfkQ== MIME-Version: 1.0 X-Received: by 10.180.73.80 with SMTP id j16mr8162169wiv.5.1359546551961; Wed, 30 Jan 2013 03:49:11 -0800 (PST) Received: by 10.194.165.135 with HTTP; Wed, 30 Jan 2013 03:49:11 -0800 (PST) X-Originating-IP: [101.82.22.219] Date: Wed, 30 Jan 2013 19:49:11 +0800 Message-ID: Subject: buildworld errors From: Jesse To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQl7kVvY3OsZj6WBbBucgprB6mfdhk4c7lWv8rlTuN6TOgK0GT2V0rLxD6Mx5ikqohpZ2V3n X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 11:49:13 -0000 I updated /usr/src and buildworld just now. The building process stopped at here. It's FreeBSD 10.0 ===> lib/clang/libllvmlinker (all) ===> lib/clang/libllvmmc (all) ===> lib/clang/libllvmmcparser (all) ===> lib/clang/libllvmobject (all) ===> lib/clang/libllvmscalaropts (all) ===> lib/clang/libllvmselectiondag (all) ===> lib/clang/libllvmsupport (all) ===> lib/clang/libllvmtablegen (all) ===> lib/clang/libllvmtarget (all) ===> lib/clang/libllvmtransformutils (all) ===> lib/clang/libllvmvectorize (all) ===> lib/clang/libllvmarmasmparser (all) ===> lib/clang/libllvmarmcodegen (all) ===> lib/clang/libllvmarmdesc (all) ===> lib/clang/libllvmarmdisassembler (all) ===> lib/clang/libllvmarminfo (all) ===> lib/clang/libllvmarminstprinter (all) ===> lib/clang/libllvmmipsasmparser (all) ===> lib/clang/libllvmmipscodegen (all) ===> lib/clang/libllvmmipsdesc (all) ===> lib/clang/libllvmmipsdisassembler (all) ===> lib/clang/libllvmmipsinfo (all) ===> lib/clang/libllvmmipsinstprinter (all) ===> lib/clang/libllvmpowerpccodegen (all) ===> lib/clang/libllvmpowerpcdesc (all) ===> lib/clang/libllvmpowerpcinfo (all) ===> lib/clang/libllvmpowerpcinstprinter (all) ===> lib/clang/libllvmx86asmparser (all) ===> lib/clang/libllvmx86codegen (all) ===> lib/clang/libllvmx86desc (all) ===> lib/clang/libllvmx86disassembler (all) ===> lib/clang/libllvmx86info (all) ===> lib/clang/libllvmx86instprinter (all) ===> lib/clang/libllvmx86utils (all) ===> lib/clang/libllvmdebuginfo (all) ===> lib/clang/libllvmexecutionengine (all) ===> lib/clang/libllvminterpreter (all) ===> lib/clang/libllvmjit (all) ===> lib/clang/libllvmmcdisassembler (all) ===> lib/clang/libllvmmcjit (all) ===> lib/clang/libllvmruntimedyld (all) ===> lib/clang/include (all) 1 error *** [everything] Error code 2 1 error *** [buildworld] Error code 2 1 error From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 09:37:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1073E4EF for ; Wed, 30 Jan 2013 09:37:35 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id 8CC3CA8A for ; Wed, 30 Jan 2013 09:37:34 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hj13so1358160wib.13 for ; Wed, 30 Jan 2013 01:37:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type; bh=u54OzW3OSF3G57MuxSb3HKm3RMcRob9eNMqDYv71UmM=; b=tGZleEp8KfPWv8zyutk8wJc+fS6c2XlQtP/mfsBpjqxr/w0WtfMsstYPxix5X3uiPG 54JdAh7MfV208sHLHMzO6JCCv+6O44HOLtoVLEGS/wX8YXvJNx+I7UDF9bkPuZLxyexJ 2Ec4IFXXNFNr6SjvSluuzSEXqfP5uWOoR/nPo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:date:message-id:subject :from:to:content-type:x-gm-message-state; bh=u54OzW3OSF3G57MuxSb3HKm3RMcRob9eNMqDYv71UmM=; b=lykPh8aSFCw9mYBKt/W4PeF25NeObFTrGCfm9HmZj7qF1mOsx7F3tZX5/BEIoubnHH KQ0to8iE+1dcNpj8OHq7OmXENwYSS2QXrcFJQkiNFIaFS1OSHi9pxxMvCl0WEuaTEVAY MQbKGLy67z/1vZG7EVh8E087eY0AVQ6I8OthfiyLQm/LTRYBz3iNcM5YcJnMVsV2qvQp UrOCKswpn6PKetwJGlCBk/MlBQQ1PTdbYK2zI/ySEi+93Lkvyh8HJOnmqisytRCwxCzv MRb3RdzaF3Z4aYLuFw/Zo5Z6pgWtgR86iKazJJXylf5PB8bUjtBTjWBY9sEmCOzWZkYH iD4g== MIME-Version: 1.0 X-Received: by 10.194.57.82 with SMTP id g18mr7489664wjq.25.1359538653458; Wed, 30 Jan 2013 01:37:33 -0800 (PST) Received: by 10.194.165.135 with HTTP; Wed, 30 Jan 2013 01:37:33 -0800 (PST) X-Originating-IP: [101.82.22.219] Date: Wed, 30 Jan 2013 09:37:33 +0000 Message-ID: Subject: buildworld error From: Jesse To: freebsd-current@freebsd.org X-Gm-Message-State: ALoCoQmLoPOTevZyUJbybeFSlEqU4PPKwYMY/o9K411oARZue/DP6DVPCnqowFfZHVJkKRyuuFuX X-Mailman-Approved-At: Wed, 30 Jan 2013 12:38:06 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 09:37:35 -0000 Hi, I just update /usr/src and make buildworld. The building proccess stop as errors: ===> lib/clang/libllvmx86asmparser (all) ===> lib/clang/libllvmx86codegen (all) ===> lib/clang/libllvmx86desc (all) ===> lib/clang/libllvmx86disassembler (all) ===> lib/clang/libllvmx86info (all) ===> lib/clang/libllvmx86instprinter (all) ===> lib/clang/libllvmx86utils (all) ===> lib/clang/libllvmdebuginfo (all) ===> lib/clang/libllvmexecutionengine (all) ===> lib/clang/libllvminterpreter (all) ===> lib/clang/libllvmjit (all) ===> lib/clang/libllvmmcdisassembler (all) ===> lib/clang/libllvmmcjit (all) ===> lib/clang/libllvmruntimedyld (all) ===> lib/clang/include (all) 1 error *** [everything] Error code 2 1 error *** [buildworld] Error code 2 1 error From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 13:29:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C3146199 for ; Wed, 30 Jan 2013 13:29:15 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 88B3B9C1 for ; Wed, 30 Jan 2013 13:29:15 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:1d8f:9e64:ac72:f29e] (unknown [IPv6:2001:7b8:3a7:0:1d8f:9e64:ac72:f29e]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0F6045C5A; Wed, 30 Jan 2013 14:29:12 +0100 (CET) Message-ID: <51092025.1070906@FreeBSD.org> Date: Wed, 30 Jan 2013 14:29:09 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20130117 Thunderbird/19.0 MIME-Version: 1.0 To: Jesse , freebsd-current@freebsd.org Subject: Re: buildworld error References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 13:29:15 -0000 On 2013-01-30 10:37, Jesse wrote: > I just update /usr/src and make buildworld. The building proccess stop as > errors: > > ===> lib/clang/libllvmx86asmparser (all) > ===> lib/clang/libllvmx86codegen (all) > ===> lib/clang/libllvmx86desc (all) > ===> lib/clang/libllvmx86disassembler (all) > ===> lib/clang/libllvmx86info (all) > ===> lib/clang/libllvmx86instprinter (all) > ===> lib/clang/libllvmx86utils (all) > ===> lib/clang/libllvmdebuginfo (all) > ===> lib/clang/libllvmexecutionengine (all) > ===> lib/clang/libllvminterpreter (all) > ===> lib/clang/libllvmjit (all) > ===> lib/clang/libllvmmcdisassembler (all) > ===> lib/clang/libllvmmcjit (all) > ===> lib/clang/libllvmruntimedyld (all) > ===> lib/clang/include (all) > 1 error > *** [everything] Error code 2 > 1 error > *** [buildworld] Error code 2 > 1 error Because you are making buildworld with -j, the actual error message is not visible. Try searching back in the log to find the actual error, and post that. Alternatively, make buildworld without -j. From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 13:36:17 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9122E3F2 for ; Wed, 30 Jan 2013 13:36:17 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE5BA32 for ; Wed, 30 Jan 2013 13:36:15 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0UDa8rH090494 for ; Wed, 30 Jan 2013 06:36:08 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0UDZsSL023725; Wed, 30 Jan 2013 06:35:54 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: mounting root from NFS via ROOTDEVNAME From: Ian Lepore To: "Eggert, Lars" In-Reply-To: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Jan 2013 06:35:54 -0700 Message-ID: <1359552954.93359.224.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 13:36:17 -0000 On Wed, 2013-01-30 at 09:32 +0000, Eggert, Lars wrote: > Hi, > > On Jan 29, 2013, at 20:22, Craig Rodrigues wrote: > > What kind of architecture are you trying to do this on? Is this > > i386/amd64 or something else? > > amd64 > > > I am not familiar with netboot compared to > > PXE. Is TFTP involved at all with netboot? > > TFTP is not involved. The kernel gets booted by our custom loader (over HTTP) and the root FS is supposed to be mounted over NFS. > > > What does your dhcpd configuration file look like? > > Completely standard, with the addition of a "root-path" option. (Which I would like to get rid of by setting ROOTDEVNAME in the kernel.) > > > Also, are you using the FreeBSD loader, or something else? What kinds of > > customizations have you done on the loader? > > Custom loader. > > > If through your setup you have already managed to load the kernel over > > the network, then a lot of the hard work has been done. Telling the kernel > > where the root file system is located becomes the next tricky part. > > Right, that's the step I am struggeling with. > > > In src/sys/boot/common/boot.c which is part of the loader (not the kernel), > > if you look in the getrootmount() function, > > you will see that the loader will try to figure out where the root file > > system > > is by parsing /etc/fstab, and looking for the "/" mount. > > > > So, if your kernel is located in: > > > > /usr/home/elars/dst/boot/kernel/kernel > > > > Then create a file /usr/home/elars/dst/etc/fstab file with something like: > > > > # Device Mountpoint FSType > > Options Dump Pass > > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 > > Thanks, will try that! > > > Alternatively, if you don't want to create an /etc/fstab file, then > > you could put something like this in your loader.conf file: > > > > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Will try that too, but not sure if this works with our custom loader. > > Lars > > > > > If you can get this to work without introducing new kernel options, > > that would be ideal, because the kernel options you are > > enabling are triggering behaviors. > > Just FYI, I believe the current behavior of BOOTP and BOOTP_NFSROOT is a bug, and I've entered a PR for it http://www.freebsd.org/cgi/query-pr.cgi?pr=175671 I also put a little effort into changing the behavior so that BOOTP without BOOTP_NFSROOT gets you an address and then moves on to use the ROOTDEVNAME you have configured, but I didn't have any success yet (it stays stuck in the state of waiting for the root path). I intend to get back to it after wrapping up some other work, if someone else doesn't get to it first. -- Ian From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 14:51:37 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 34DE19B4 for ; Wed, 30 Jan 2013 14:51:37 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 1413FE81 for ; Wed, 30 Jan 2013 14:51:36 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.6/8.14.6) with ESMTP id r0UEpZcV026366 for ; Wed, 30 Jan 2013 06:51:35 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.6/8.14.6/Submit) id r0UEpZ53026365 for current@freebsd.org; Wed, 30 Jan 2013 06:51:35 -0800 (PST) (envelope-from david) Date: Wed, 30 Jan 2013 06:51:35 -0800 From: David Wolfskill To: current@freebsd.org Subject: x11/nvidia-driver build fails in head @r246115 Message-ID: <20130130145135.GM1804@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45kFsbCJmK9J4C/8" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 14:51:37 -0000 --45kFsbCJmK9J4C/8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I include PORTS_MODULES=3Dx11/nvidia-driver in /etc/src.conf in order to keep nvidia-driver in sync with my kernel. It last built OK yesterday, @r246057; @r246115, I see: =3D=3D=3D> nvidia-driver-304.64 depends on file: /usr/local/libdata/pkgco= nfig/xorg-server.pc - found =3D=3D=3D> nvidia-driver-304.64 depends on shared library: GL.1 - found =3D=3D=3D> Configuring for nvidia-driver-304.64 =3D=3D=3D> Building for nvidia-driver-304.64 =3D=3D=3D> src (all) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include x86 -> /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h clang -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=3D\"304.64\" -D__K= ERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -UDEBUG -U_DEBUG -DN= DEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/alt= q -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestan= ding -fstack-protector -std=3Diso9899:1999 -Qunused-arguments -fstack-prote= ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissin= g-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sig= n -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -W= no-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses= -equality -c nvidia_ctl.c clang -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=3D\"304.64\" -D__K= ERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -UDEBUG -U_DEBUG -DN= DEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/alt= q -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestan= ding -fstack-protector -std=3Diso9899:1999 -Qunused-arguments -fstack-prote= ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissin= g-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sig= n -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -W= no-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses= -equality -c nvidia_dev.c clang -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=3D\"304.64\" -D__K= ERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -UDEBUG -U_DEBUG -DN= DEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/alt= q -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestan= ding -fstack-protector -std=3Diso9899:1999 -Qunused-arguments -fstack-prote= ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissin= g-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sig= n -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -W= no-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses= -equality -c nvidia_i2c.c clang -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=3D\"304.64\" -D__K= ERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O -UDEBUG -U_DEBUG -DN= DEBUG -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I. -I@ -I@/contrib/alt= q -fno-common -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestan= ding -fstack-protector -std=3Diso9899:1999 -Qunused-arguments -fstack-prote= ctor -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissin= g-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sig= n -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -W= no-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses= -equality -c nvidia_linux.c nvidia_linux.c:51:28: error: variable has incomplete type 'struct linux_ioc= tl_handler' struct linux_ioctl_handler nvidia_handler =3D { ^ nvidia_linux.c:51:8: note: forward declaration of 'struct linux_ioctl_handl= er' struct linux_ioctl_handler nvidia_handler =3D { ^ nvidia_linux.c:62:5: error: implicit declaration of function 'linux_ioctl_r= egister_handler' is invalid in C99 [-Werror,-Wimplicit-function-declaration] linux_ioctl_register_handler(&nvidia_handler); ^ nvidia_linux.c:69:5: error: implicit declaration of function 'linux_ioctl_u= nregister_handler' is invalid in C99 [-Werror,-Wimplicit-function-declarati= on] linux_ioctl_unregister_handler(&nvidia_handler); ^ nvidia_linux.c:69:5: note: did you mean 'linux_ioctl_register_handler'? linux_ioctl_unregister_handler(&nvidia_handler); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ linux_ioctl_register_handler nvidia_linux.c:62:5: note: 'linux_ioctl_register_handler' declared here linux_ioctl_register_handler(&nvidia_handler); ^ 3 errors generated. *** [nvidia_linux.o] Error code 1 Stop in /common/S4/obj/usr/src/sys/CANARY/common/ports/x11/nvidia-driver/wo= rk/NVIDIA-FreeBSD-x86-304.64/src. *** [all] Error code 1 Stop in /common/S4/obj/usr/src/sys/CANARY/common/ports/x11/nvidia-driver/wo= rk/NVIDIA-FreeBSD-x86-304.64. *** [do-build] Error code 1 Stop in /common/ports/x11/nvidia-driver. *** [build] Error code 1 Stop in /common/ports/x11/nvidia-driver. *** [all] Error code 1 1 error *** [buildkernel] Error code 2 1 error *** [buildkernel] Error code 2 1 error I note that there were several changes in src/sys/compat/linux within the last 24 hrs. Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --45kFsbCJmK9J4C/8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlEJM3YACgkQmprOCmdXAD30PwCfYF0UFliKTFbsCbhAUdKuzuHY ICAAnRpQMJDonjxVBuJRIVT6DITyDJMk =v1k1 -----END PGP SIGNATURE----- --45kFsbCJmK9J4C/8-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 15:35:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 16E9EACE for ; Wed, 30 Jan 2013 15:35:08 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id CC50B131 for ; Wed, 30 Jan 2013 15:35:07 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAEs9CVGDaFvO/2dsb2JhbABFhki4WnOCHgEBAQMBAQEBICsgCxsSBgICDRkCKQEJGA4GCAcEARwEh2oGDK8jkmCBI4t+gliBEwOIYYp+gi6BHI8vgxWBUTU X-IronPort-AV: E=Sophos;i="4.84,569,1355115600"; d="scan'208";a="11566987" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 30 Jan 2013 10:34:44 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id B544DB3F19; Wed, 30 Jan 2013 10:34:44 -0500 (EST) Date: Wed, 30 Jan 2013 10:34:44 -0500 (EST) From: Rick Macklem To: Lars Eggert Message-ID: <1676091515.2505116.1359560084705.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: mounting root from NFS via ROOTDEVNAME MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: Craig Rodrigues , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 15:35:08 -0000 Lars Eggert wrote: > Hi, > > On Jan 29, 2013, at 20:22, Craig Rodrigues > wrote: > > What kind of architecture are you trying to do this on? Is this > > i386/amd64 or something else? > > amd64 > > > I am not familiar with netboot compared to > > PXE. Is TFTP involved at all with netboot? > > TFTP is not involved. The kernel gets booted by our custom loader > (over HTTP) and the root FS is supposed to be mounted over NFS. > > > What does your dhcpd configuration file look like? > > Completely standard, with the addition of a "root-path" option. (Which > I would like to get rid of by setting ROOTDEVNAME in the kernel.) > > > Also, are you using the FreeBSD loader, or something else? What > > kinds of > > customizations have you done on the loader? > > Custom loader. > > > If through your setup you have already managed to load the kernel > > over > > the network, then a lot of the hard work has been done. Telling the > > kernel > > where the root file system is located becomes the next tricky part. > > Right, that's the step I am struggeling with. > If you have "options BOOTP" and "options BOOTP_NFSROOT", the VFS_MOUNT()/nfs_mount() call early in vfs_mountroot() calls bootpc_init(). This function and related code is in sys/nfs/bootp_subr.c. At a glance, the code in sys/nfs/bootp_subr.c tries very hard to get "root-path" in several places, so it will take some fiddling to get it to work without the dhcpd returning a root-path option. (I think Ian Lepore has started to work on this.) I don't have any way of testing this until at least April, so I can't really help. It should be possible to modify bootp_subr.c, so that it uses ROOTDEVNAME instead of trying to get "root-path" from the dhcp server when it is specified, but the change will take some work. If you want bootpc_init() to be called when "options BOOTP_NFSROOT" isn't specified, that is a one line change in sys/fs/nfsclient/nfs_clvfsops.c. (Just look for the bootpc_init() call, but I don't see that as being useful? I think changing bootpc_init() and friends to avoid getting root-path when it has already been specified (by ROOTDEVNAME and/or vfs.root.mountfrom) is the best approach, but will require a significant patch to bootp_subr.c. I can see two other approaches to doing this: 1 - Supply a root-path via the dhcpd, but override what it says later in the kernel boot, to use what is specified by ROOTDEVNAME or vfs.root.mountfrom. I haven't looked at what this would take, but I didn't see how it could be done with the current code, because the NFS client code expects a structure called nfsv3_diskless to be filled in by bootpc_init() OR 2 - nfs_diskless(). The call to nfs_diskless() is done when "options NFS_ROOT" is specified, but "options BOOTP" + "options BOOTP_NFSROOT" is not. (Just look at the calls in sys/fs/nfs/nfs_clvfsops.c or sys/nfsclient/nfs_vfsops.c.) It fills the structure in from a bunch of environment variables. These are normally filled in by pxeboot, but you could modify your custom loader to fill them in, which would be this approach. Once eithe nfs_diskless() or bootpc_init() has filled in nfsv3_diskless and set nfs_diskless_valid, then the rest of the code uses what is in that structure, so one of these 2 functions needs to be called, unless you do a major re-write of the diskless NFS booting stuff. Good luck with it, rick > > In src/sys/boot/common/boot.c which is part of the loader (not the > > kernel), > > if you look in the getrootmount() function, > > you will see that the loader will try to figure out where the root > > file > > system > > is by parsing /etc/fstab, and looking for the "/" mount. > > > > So, if your kernel is located in: > > > > /usr/home/elars/dst/boot/kernel/kernel > > > > Then create a file /usr/home/elars/dst/etc/fstab file with something > > like: > > > > # Device Mountpoint FSType > > Options Dump Pass > > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 > > Thanks, will try that! > > > Alternatively, if you don't want to create an /etc/fstab file, then > > you could put something like this in your loader.conf file: > > > > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Will try that too, but not sure if this works with our custom loader. > > Lars > > > > > If you can get this to work without introducing new kernel options, > > that would be ideal, because the kernel options you are > > enabling are triggering behaviors. > > > > -- > > Craig Rodrigues > > rodrigc@crodrigues.org > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 16:30:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5F839DE8; Wed, 30 Jan 2013 16:30:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3DE75717; Wed, 30 Jan 2013 16:30:42 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 76A6DB926; Wed, 30 Jan 2013 11:30:41 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org, danfe@freebsd.org Subject: Re: x11/nvidia-driver build fails in head @r246115 Date: Wed, 30 Jan 2013 10:42:45 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <20130130145135.GM1804@albert.catwhisker.org> In-Reply-To: <20130130145135.GM1804@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201301301042.45219.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 30 Jan 2013 11:30:41 -0500 (EST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 16:30:42 -0000 On Wednesday, January 30, 2013 9:51:35 am David Wolfskill wrote: > I include > > PORTS_MODULES=x11/nvidia-driver > > in /etc/src.conf in order to keep nvidia-driver in sync with my kernel. > > It last built OK yesterday, @r246057; @r246115, I see: Oof, it needs to use instead of one of the headers on HEAD. (and this is my fault) Alexey, can you patch the port for that? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 21:23:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3E6B743D; Wed, 30 Jan 2013 21:23:42 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [199.48.129.194]) by mx1.freebsd.org (Postfix) with ESMTP id E8A2C7AD; Wed, 30 Jan 2013 21:23:41 +0000 (UTC) Received: from neu.net (neu.net [199.48.129.194]) by mail.neu.net (8.14.6/8.14.5) with ESMTP id r0ULNd2N055647; Wed, 30 Jan 2013 16:23:39 -0500 (EST) (envelope-from andy@neu.net) Date: Wed, 30 Jan 2013 16:23:39 -0500 (EST) From: AN To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.97.6 at my.mail.server X-Virus-Status: Clean X-Spam-Status: No, score=1.8 required=4.5 tests=MISSING_SUBJECT, RP_MATCHES_RCVD autolearn=no version=3.3.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.neu.net Cc: theraven@FreeBSD.org, vbox@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 21:23:42 -0000 FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r246130: Wed Jan 30 15:00:08 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 I just rebuilt the world and kernel. Then I rebuilt /usr/ports/emulators/virtualbox-ose-kmod. # kldstat Id Refs Address Size Name 1 24 0xffffffff80200000 116fac0 kernel 2 1 0xffffffff81370000 ee74c8 nvidia.ko 3 3 0xffffffff82258000 1393f8 linux.ko 4 1 0xffffffff82412000 997d linprocfs.ko 5 1 0xffffffff8241c000 344b ums.ko 6 1 0xffffffff82420000 29c3 uhid.ko 7 1 0xffffffff82423000 2e7b0 vboxdrv.ko # pkg info |grep box virtualbox-ose-4.2.6 A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.6_1 VirtualBox kernel module for FreeBSD Virtualbox suddenly broke for me, possibly related to this: http://svnweb.FreeBSD.org/base?view=revision&revision=246028 Fix some symbol version mismatches between libstdc++ and libsupc++/libcxxrt that were causing the runtime and STL libraries to see different versions of various classes and functions when libstdc++ is used as a filter. When I try to start Vbox it fails with: # VirtualBox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found With all due respect to developers, are these changes tested at all before they are added to the codebase? I understand this is a development branch. I am not a developer, but it seems to me more thought and testing should be done before changes like this are committed. From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 21:43:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 485FFAE6 for ; Wed, 30 Jan 2013 21:43:53 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-la0-x232.google.com (la-in-x0232.1e100.net [IPv6:2a00:1450:4010:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id B2F908AA for ; Wed, 30 Jan 2013 21:43:52 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id ec20so1448929lab.23 for ; Wed, 30 Jan 2013 13:43:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fVUpoKaLGcB2YXy7bxO6GvWWmvvQadyPEtYYZg7RdrY=; b=qzumAFlg9SIHNUHtXaQm72Pv1+Cp2W3QvZyxK013lEBEjKb431ksSZf7Us6PmfDLBy E9JK0bW5DDAZF2jBnK+m1JC9q5LIj/uubnlJaVvT9nU19rdhrVNRXDBOD5TLYKZrl1At 7Gq1m8ybulMik0Os09EwRcGxJnEeBzcw8l3hSCcQQg5+tjnz6gFCs6/B9A3h5gAgQ+4z Ud5NUD65wU8j7qd7bjuIA50kYSmVXp/PaMWLsgVJH2Ftmsy2+3Xzq/XXiVKC1KS9tFcD 1xDkLhpzoDyJjNe5HzouBVwmMsvjKPoErcKfhC605fBVAOj6z8ZFtEd8nwPIt1OwQQ7I j15w== MIME-Version: 1.0 X-Received: by 10.112.98.105 with SMTP id eh9mr2490406lbb.131.1359582231626; Wed, 30 Jan 2013 13:43:51 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.24.225 with HTTP; Wed, 30 Jan 2013 13:43:51 -0800 (PST) In-Reply-To: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Date: Wed, 30 Jan 2013 13:43:51 -0800 X-Google-Sender-Auth: rhHl5nCiZXPAXw6eLPL1qMf8JT0 Message-ID: Subject: Re: mounting root from NFS via ROOTDEVNAME From: Craig Rodrigues To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 21:43:53 -0000 On Wed, Jan 30, 2013 at 1:32 AM, Eggert, Lars wrote: > Hi, > > On Jan 29, 2013, at 20:22, Craig Rodrigues wrote: > > > TFTP is not involved. The kernel gets booted by our custom loader (over > HTTP) and the root FS is supposed to be mounted over NFS. > > If through your setup you have already managed to load the kernel over > > the network, then a lot of the hard work has been done. Telling the > kernel > > where the root file system is located becomes the next tricky part. > > Right, that's the step I am struggeling with. > > > In src/sys/boot/common/boot.c which is part of the loader (not the > kernel), > > if you look in the getrootmount() function, > > you will see that the loader will try to figure out where the root file > > system > > is by parsing /etc/fstab, and looking for the "/" mount. > > > > So, if your kernel is located in: > > > > /usr/home/elars/dst/boot/kernel/kernel > > > > Then create a file /usr/home/elars/dst/etc/fstab file with something > like: > > > > # Device Mountpoint FSType > > Options Dump Pass > > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 > 0 > > Thanks, will try that! > > > Alternatively, if you don't want to create an /etc/fstab file, then > > you could put something like this in your loader.conf file: > > > > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Will try that too, but not sure if this works with our custom loader. > > > Hi, Thanks for the clarification. I have a better idea of what you are trying to do. As you can imagine, not too many people have been playing with this type of stuff. A lot of this root mounting/NFS code was written about 14-15 years ago, and not a lot of folks have been using it, but it is highly useful once you get it to work. Rick Macklem has been dusting off a lot of the cobwebs in the NFS code thankfully. Since your custom loader can load the kernel without using TFTP, I think that this is a very good point. Does your custom loader use any of the FreeBSD bootstrap or loader code? What you need to do is, before the FreeBSD kernel boots, your loader needs to export some environment variables. This will trigger the various behaviors in the FreeBSD mount code. So as I suggested before, you should continue with: (1) Have /usr/home/elars/dst/etc/fstab with: # Options Dump Pass 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 (2) From your loader, you need to export this environment variable, so that the kernel can get it with getenv(). You need at least: vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst Now, there are some other environment variables you need to export from the loader. If you look in src/sys/boot/i386/libi386/pxe.c, you will see that several environment variables are set by the FreeBSD loader (which is /boot/pxeboot on a FreeBSD system): boot.netif.ip boot.netif.netmask boot.netif.gateway boot.nfsroot.server boot.nfsroot.path dchp.host-name These variables are then read by the FreeBSD kernel's NFS client root mount code in src/sys/nfsclient/nfs_diskless.c. If you can get those variables set properly in your loader, so that the FreeBSD kernel can read them, then I think this might work. :) Basically, you need to give the kernel enough basic info about the IP address, gateway, and netmask so it can NFS mount the root file system. Also, unless you really need them, I would recommend removing the BOOTP options from your kernel config (unless you really feel you need them). As others have pointed out, some of these options have not been tested for a long time and might be buggy. That is always the risk when kernel options are not part of the GENERIC config. Good luck! -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 22:16:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 93A218A7; Wed, 30 Jan 2013 22:16:19 +0000 (UTC) (envelope-from universite@ukr.net) Received: from ffe17.ukr.net (ffe17.ukr.net [195.214.192.83]) by mx1.freebsd.org (Postfix) with ESMTP id 225C0A11; Wed, 30 Jan 2013 22:16:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Date:Message-Id:From:To:References:In-Reply-To:Subject:Cc:Content-Type:Content-Transfer-Encoding:MIME-Version; bh=fV+Bh0N8JNjGFvYk/bb45iFUqDQptup1FImZtFB/6Y4=; b=Q0ixxUY3cZf4anPbmhMYsDqjv1snjiiijqH2XruWglCDasyj6SNa9gw5XRB1FxfAadL4Izu8PVH+dwDODFd8CEUmO0JLUu5G3eZAtb7lYI3BmRCzYdzYDqul4dlpcTyCDc7S1ny+Vy0Cp5+/vP8OXYFb6/rk7zs2Vg8V1m4tamc=; Received: from mail by ffe17.ukr.net with local ID 1U0fZJ-000N1z-3y ; Wed, 30 Jan 2013 23:51:45 +0200 MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: binary Content-Type: text/plain; charset="windows-1251" Subject: Re[2]: Re[2]: AHCI timeout when using ZFS + AIO + NCQ In-Reply-To: <1359317924363-5781425.post@n5.nabble.com> References: <70362.1359299605.3196836531757973504@ffe11.ukr.net> <16B555759C2041ED8185DF478193A59D@multiplay.co.uk> <917933DB5C9A490D93A739058C2507A1@multiplay.co.uk> <93308.1359297551.14145052969567453184@ffe15.ukr.net> <13391.1359029978.3957795939058384896@ffe16.ukr.net> <70578.1359313319.18126575192049975296@ffe16.ukr.net> <221B307551154F489452F89E304CA5F7@multiplay.co.uk> <1359317924363-5781425.post@n5.nabble.com> To: "Beeblebrox" From: "Vladislav Prodan" X-Mailer: freemail.ukr.net 4.0 Message-Id: <87448.1359582705.624376220320202752@ffe17.ukr.net> X-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 Date: Wed, 30 Jan 2013 23:51:45 +0200 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 22:16:19 -0000 > I once ran into a very severe AHCI timeout problem. After months of trying to > figure it out and insane "Hardware_ECC_Recovered" error values, I found that > the error was with the power connector plug / sata HDD interface. All errors > disappeared after replacing that cable. Since you have error on more than 1 > HDD, I suggest: > 1. Check smartctl output for each AND all HDD > 2. Check whether your power supply unit is still healthy or if it is > supplying inconsistent power. > 3. Check the main power supply line and whether it shows any voltage > fluctuations or if there is a new heavy consumer of amps on the same power > line as the server is plugged to. > > I've deliberately chose a different server that has a different chipset, and that there were no problems with the HDD. Added kernel support: device ahci # AHCI-compatible SATA controllers And now, after 2.5 days fell off one HDD. [3:14]beastie:root->/root# zpool status pool: tank state: DEGRADED status: One or more devices has been removed by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: none requested config: NAME STATE READ WRITE CKSUM tank DEGRADED 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 mirror-1 DEGRADED 0 0 0 gpt/disk1 ONLINE 0 0 0 4931885954389536913 REMOVED 0 0 0 was /dev/gpt/disk3 errors: No known data errors Jan 30 09:49:28 beastie kernel: ahcich3: Timeout on slot 29 port 0 Jan 30 09:49:28 beastie kernel: ahcich3: is 00000000 cs 20000000 ss 00000000 rs 20000000 tfd c0 serr 00000000 cmd 0004dd17 Jan 30 09:49:28 beastie kernel: (ada3:ahcich3:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00 Jan 30 09:49:28 beastie kernel: (ada3:ahcich3:0:0:0): CAM status: Command timeout Jan 30 09:49:28 beastie kernel: (ada3:ahcich3:0:0:0): Retrying command Jan 30 09:51:31 beastie kernel: ahcich3: AHCI reset: device not ready after 31000ms (tfd = 00000080) Jan 30 09:51:31 beastie kernel: ahcich3: Timeout on slot 29 port 0 Jan 30 09:51:31 beastie kernel: ahcich3: is 00000000 cs 20000000 ss 00000000 rs 20000000 tfd 80 serr 00000000 cmd 0004dd17 Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): CAM status: Command timeout Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): Error 5, Retry was blocked Jan 30 09:51:31 beastie kernel: ahcich3: AHCI reset: device not ready after 31000ms (tfd = 00000080) Jan 30 09:51:31 beastie kernel: ahcich3: Timeout on slot 29 port 0 Jan 30 09:51:31 beastie kernel: ahcich3: is 00000000 cs 00000000 ss 00000000 rs 20000000 tfd 58 serr 00000000 cmd 0004dd17 Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00 Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): CAM status: Command timeout Jan 30 09:51:31 beastie kernel: (aprobe0:ahcich3:0:0:0): Error 5, Retry was blocked Jan 30 09:51:31 beastie kernel: (ada3:ahcich3:0:0:0): lost device Jan 30 09:51:31 beastie kernel: (pass3:ahcich3:0:0:0): passdevgonecb: devfs entry is gone -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 23:46:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 96ACC674 for ; Wed, 30 Jan 2013 23:46:29 +0000 (UTC) (envelope-from jbeich@tormail.org) Received: from outgoing.tormail.org (outgoing.tormail.org [82.221.96.22]) by mx1.freebsd.org (Postfix) with ESMTP id 3301AD8F for ; Wed, 30 Jan 2013 23:46:28 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=internal.tormail.org) by outgoing.tormail.org with esmtp (Exim 4.72) (envelope-from ) id 1U0hM6-0004Ae-62 for freebsd-current@freebsd.org; Thu, 31 Jan 2013 02:46:21 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Type:MIME-Version:References:Date:In-Reply-To:Subject:To:From; bh=lk5IPU21tG+/QSr4lrv+7JByTUvw9fF6ssjRG/Ed0eo=; b=Ds+/C17VO1HQ3sgN7BupntlEluIOWuSsdK/7+eEJfZ0gFGOjyDetWXzcdd3OIjPWK/8mVvTEVW1egzWcb5Xx1CVjUgte4px5O+Y9qQSyVys+zYM6Nx/UXV6HQJLoAjHXlGCOGagaogOQ8uuiec96TI+fiEeLo/fM+VXtlOVsR3M=; Received: from jbeich by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1U0hJQ-0008zb-Do for freebsd-current@freebsd.org; Wed, 30 Jan 2013 23:43:29 +0000 From: Jan Beich To: freebsd-current@freebsd.org Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' In-Reply-To: <51079F0A.20309@zedat.fu-berlin.de> (O. Hartmann's message of "Tue, 29 Jan 2013 11:06:02 +0100") Date: Thu, 31 Jan 2013 11:43:09 +1200 References: <51079F0A.20309@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain X-TorMail-User: jbeich Message-Id: <1U0hJQ-0008zb-Do@internal.tormail.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 23:46:29 -0000 "O. Hartmann" writes: > c++ -O3 -pipe -fno-strict-aliasing -march=native -march=native > -DHAVE_CONFIG_H -I/usr/src/libexec/atf/atf-check/../../../contrib/atf > -Qunused-arguments -fstack-protector -Wsystem-headers -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith > -Wno-uninitialized -Wno-empty-body -Wno-string-plus-int > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-conversion -stdlib=libc++ -std=c++11 > -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++ > -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c -o > atf-check atf-check.o -latf-c++ -latf-c > /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to > `std::bad_alloc::~bad_alloc()' > /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf-c++.so: > undefined reference to `std::bad_alloc::bad_alloc()' > /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/libatf-c++.so: > undefined reference to `std::bad_alloc::~bad_alloc()' > /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to > `std::bad_alloc::bad_alloc()' > c++: error: linker command failed with exit code 1 (use -v to see > invocation) > *** [atf-check] Error code 1 Try stage binaries built with default CXXFLAGS from allbsd.org snapshot. With them installed do you see smth like the following? $ clang++ -stdlib=libc++ foo.c clang++: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated /usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::bad_alloc()' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::bad_alloc()' clang++: error: linker command failed with exit code 1 (use -v to see invocation) It's different from the error when you build libc++ before libcxxrt. $ clang++ -stdlib=libc++ foo.c clang++: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated /usr/lib/libc++.so: undefined reference to `std::uncaught_exception()@CXXABI_1.3' /usr/lib/libc++.so: undefined reference to `std::exception::~exception()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `typeinfo for std::exception@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::bad_alloc()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `typeinfo for std::bad_cast@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::bad_cast::~bad_cast()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `typeinfo for std::bad_alloc@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::bad_alloc::bad_alloc()@CXXRT_1.0' /usr/lib/libc++.so: undefined reference to `std::terminate()@CXXABI_1.3' clang++: error: linker command failed with exit code 1 (use -v to see invocation) -- #! /bin/sh # fetch/install stage binaries from allbsd.org snapshots TARGET=amd64 TARGET_ARCH=amd64 BRANCH=10.0-HEAD #REVISION=r245980 # works fine REVISION=r246034 # doesn't work LIBS="lib/libcxxrt/libcxxrt.so.1:/lib \ lib/libc++/libc++.so.1:/usr/lib \ gnu/lib/libsupc++/libsupc++.so.1:/usr/lib" for f in $LIBS; do # chflags 0 $dir/${file##*/} fetch -o ${f#*:} https://pub.allbsd.org/FreeBSD-snapshots/${TARGET}-${TARGET_ARCH}/${BRANCH}-${REVISION}-JPSNAP/stage/usr/obj/usr/src/${f%:*} done From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 02:37:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 649AA9CA for ; Thu, 31 Jan 2013 02:37:28 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id D7F3635E for ; Thu, 31 Jan 2013 02:37:27 +0000 (UTC) Received: from JRE-MBP-2.local (c-98-210-232-101.hsd1.ca.comcast.net [98.210.232.101]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id r0V2auR3018440 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 30 Jan 2013 18:36:57 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <5109D8C7.8000608@freebsd.org> Date: Wed, 30 Jan 2013 18:36:55 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Eggert, Lars" Subject: Re: mounting root from NFS via ROOTDEVNAME References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 02:37:28 -0000 On 1/30/13 1:32 AM, Eggert, Lars wrote: > Hi, > > On Jan 29, 2013, at 20:22, Craig Rodrigues wrote: > >> Alternatively, if you don't want to create an /etc/fstab file, then >> you could put something like this in your loader.conf file: >> >> vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > Will try that too, but not sure if this works with our custom loader. your custom loader should have some way to set kernel environment values. it's a pretty basic requirement and, surprisingly, not that hard to do. From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 04:05:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 952D4531 for ; Thu, 31 Jan 2013 04:05:26 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 2B6B68C3 for ; Thu, 31 Jan 2013 04:05:26 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so1701352wey.2 for ; Wed, 30 Jan 2013 20:05:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=LfrWYtD4KTP/ptiltffc4JqCT5pRsSxd47026JE+/lA=; b=NqQmB9JiFfi3gQdklKLo7pl+MLRpZ4gzsT2x5l4HRK9AfL9HTodcxsAUwf9muovts+ Sr3A9A550mkZlc9NBSVCS2t5hSKQKyWhAnvyywjPhMFIxVc6mW81/GrLalWNea2dtQh9 Nx/Nt25r/wzaksNq5XbPCmeSYFWdE8sfDOmeg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=LfrWYtD4KTP/ptiltffc4JqCT5pRsSxd47026JE+/lA=; b=awnAsLaBSAoptgUU0zlx1xw562nNt7ja6ylnbbnxx+q9xcl22tumw1ocG373Tpt8z0 rWaElj46XU8JZesEq1NR3IhllS6SQNY6Je3bboLdx24eFT6xcLjYTsrXqS/KFfCxsvgK md9sf6XzGkHenqPnZ4ue6TfDjwDQvLnCTBaJJkkmFxoYZ+r8/PKCLjJoqf9VanE6fvQt l7bGO9JNmKSbmeyokEu8M3zYapJwWKiVsunpJ5shSViTm2L//iSBHUwoARd6ekhbyr11 VjPf/OwJsLT7YrgeXY0LUx8obbD/qnRjLftOtac5CtFfx7nvGsU3shGeAr744uP7o8b5 c/Pg== MIME-Version: 1.0 X-Received: by 10.194.57.82 with SMTP id g18mr12680902wjq.25.1359605125038; Wed, 30 Jan 2013 20:05:25 -0800 (PST) Received: by 10.194.165.135 with HTTP; Wed, 30 Jan 2013 20:05:24 -0800 (PST) X-Originating-IP: [101.82.221.98] In-Reply-To: <51092025.1070906@FreeBSD.org> References: <51092025.1070906@FreeBSD.org> Date: Thu, 31 Jan 2013 12:05:24 +0800 Message-ID: Subject: Re: buildworld error From: Jesse To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnmyYjg1A4lSEkuRSbi1zfosI1Ffl8T1Ypr2Vczr4yDWTiG+scYtfS+TSHiAXIAQgc7ETdX Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 04:05:26 -0000 i set these in make.conf: CXXFLAGS+=-stdlib=libc++ CXXFLAGS+=-std=c++11 i comment them and rebuild world ok but it works at previous revision. On 1/30/13, Dimitry Andric wrote: > On 2013-01-30 10:37, Jesse wrote: >> I just update /usr/src and make buildworld. The building proccess stop as >> errors: >> >> ===> lib/clang/libllvmx86asmparser (all) >> ===> lib/clang/libllvmx86codegen (all) >> ===> lib/clang/libllvmx86desc (all) >> ===> lib/clang/libllvmx86disassembler (all) >> ===> lib/clang/libllvmx86info (all) >> ===> lib/clang/libllvmx86instprinter (all) >> ===> lib/clang/libllvmx86utils (all) >> ===> lib/clang/libllvmdebuginfo (all) >> ===> lib/clang/libllvmexecutionengine (all) >> ===> lib/clang/libllvminterpreter (all) >> ===> lib/clang/libllvmjit (all) >> ===> lib/clang/libllvmmcdisassembler (all) >> ===> lib/clang/libllvmmcjit (all) >> ===> lib/clang/libllvmruntimedyld (all) >> ===> lib/clang/include (all) >> 1 error >> *** [everything] Error code 2 >> 1 error >> *** [buildworld] Error code 2 >> 1 error > > Because you are making buildworld with -j, the actual error message is > not visible. Try searching back in the log to find the actual error, > and post that. Alternatively, make buildworld without -j. > From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 04:06:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C6B7B64E for ; Thu, 31 Jan 2013 04:06:11 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by mx1.freebsd.org (Postfix) with ESMTP id 62E698DF for ; Thu, 31 Jan 2013 04:06:11 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id 8so1743820wgl.30 for ; Wed, 30 Jan 2013 20:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=HV1OAJqe9TmdKtv5RqYSqBwJXEEg9+MW+6rjaN1ldtM=; b=CF7eRB+Dux22jYKgtLuQYXd1hCs9YrEgsaymqj4zyhnZ8tiVxfiXl0iseC32qraX57 bMGpBxQzSupaSh0GM1UIMxt3U8jrfcwvZkC2DFbiJCARHOSJub1Z/rO+DfpFGeDwR8Rh 4curZ2diaGtmIGNS7/g+U4Zf6BrumTNTAoxYw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=HV1OAJqe9TmdKtv5RqYSqBwJXEEg9+MW+6rjaN1ldtM=; b=BtWCxJ3vVV6MsI/6QYeJdJ0dG+66Xp/spHK5DaR7sA9zbwlXhmzUNCAB8qkJCwtdMX xsLxGRhIYwhchPaUMcvAogpw1iPMtNjrFyx6hgSnWZtSTBZobxKqBYTXDAi38Ix8w7bz B3snVYKquYUg4i/MFoj757GtBH/24+148aWMQeAzNN4XXeWJD1a8RcG39unqTzDyt0FG Do1Z63dP1m3t0fa7uZ9SuSAuuUaTTyYcfI53jUghHnR/buq3bKFv8wNjcf8ijyhIbLgJ TpKWlTPe71D7wHa3mQN5v76hsH2E6GYScrQKxorzJ8AYDrDBAQfnyqaIzIxaR/PonWYo GOQA== MIME-Version: 1.0 X-Received: by 10.180.72.232 with SMTP id g8mr12625541wiv.0.1359605163850; Wed, 30 Jan 2013 20:06:03 -0800 (PST) Received: by 10.194.165.135 with HTTP; Wed, 30 Jan 2013 20:06:03 -0800 (PST) X-Originating-IP: [101.82.221.98] In-Reply-To: References: <51092025.1070906@FreeBSD.org> Date: Thu, 31 Jan 2013 12:06:03 +0800 Message-ID: Subject: Re: buildworld error From: Jesse To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQn1mBNA/hYWl6kXvUeQ05MhiEPlfWh2f8R0CIWbaxuq6u+KzxRL/e8udAwXnISdZ6Oa4QOX Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 04:06:11 -0000 z On 1/31/13, Jesse wrote: > i set these in make.conf: > CXXFLAGS+=-stdlib=libc++ > CXXFLAGS+=-std=c++11 > > i comment them and rebuild world ok > but it works at previous revision. > > On 1/30/13, Dimitry Andric wrote: >> On 2013-01-30 10:37, Jesse wrote: >>> I just update /usr/src and make buildworld. The building proccess stop >>> as >>> errors: >>> >>> ===> lib/clang/libllvmx86asmparser (all) >>> ===> lib/clang/libllvmx86codegen (all) >>> ===> lib/clang/libllvmx86desc (all) >>> ===> lib/clang/libllvmx86disassembler (all) >>> ===> lib/clang/libllvmx86info (all) >>> ===> lib/clang/libllvmx86instprinter (all) >>> ===> lib/clang/libllvmx86utils (all) >>> ===> lib/clang/libllvmdebuginfo (all) >>> ===> lib/clang/libllvmexecutionengine (all) >>> ===> lib/clang/libllvminterpreter (all) >>> ===> lib/clang/libllvmjit (all) >>> ===> lib/clang/libllvmmcdisassembler (all) >>> ===> lib/clang/libllvmmcjit (all) >>> ===> lib/clang/libllvmruntimedyld (all) >>> ===> lib/clang/include (all) >>> 1 error >>> *** [everything] Error code 2 >>> 1 error >>> *** [buildworld] Error code 2 >>> 1 error >> >> Because you are making buildworld with -j, the actual error message is >> not visible. Try searching back in the log to find the actual error, >> and post that. Alternatively, make buildworld without -j. >> > From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 04:38:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3CCF79E3; Thu, 31 Jan 2013 04:38:03 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 5B7569B4; Thu, 31 Jan 2013 04:38:02 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1U0luT-001MwR-FN>; Thu, 31 Jan 2013 05:38:01 +0100 Received: from e178012136.adsl.alicedsl.de ([85.178.12.136] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1U0luT-00297d-9F>; Thu, 31 Jan 2013 05:38:01 +0100 Message-ID: <5109F527.2030702@zedat.fu-berlin.de> Date: Thu, 31 Jan 2013 05:37:59 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: David Wolfskill Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' References: <51079F0A.20309@zedat.fu-berlin.de> <20130129163554.GW1804@albert.catwhisker.org> In-Reply-To: <20130129163554.GW1804@albert.catwhisker.org> X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6CFC32B69C58CA091C756559" X-Originating-IP: 85.178.12.136 Cc: Current FreeBSD , David Chisnall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 04:38:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6CFC32B69C58CA091C756559 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 01/29/13 17:35, schrieb David Wolfskill: > On Tue, Jan 29, 2013 at 11:06:02AM +0100, O. Hartmann wrote: >> I receive this error since yesterday building world and it is still >> sticky on most recent sources (r246057) and I was wondering why the >> tinderboxes do not pick this up on the 10.0-CURRENT builds ... just fo= r >> a notice for the development folks ... >> ...=20 >> =3D=3D=3D> libexec/atf/atf-check (all) >> ... >> c++ -O3 -pipe -fno-strict-aliasing -march=3Dnative -march=3Dnative >> -DHAVE_CONFIG_H -I/usr/src/libexec/atf/atf-check/../../../contrib/atf >> -Qunused-arguments -fstack-protector -Wsystem-headers -Wall >> -Wno-format-y2k -W -Wno-unused-parameter -Wpointer-arith >> -Wno-uninitialized -Wno-empty-body -Wno-string-plus-int >> -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality >> -Wno-unused-function -Wno-conversion -stdlib=3Dlibc++ -std=3Dc++11 >> -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++ >> -L/usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c -o >> atf-check atf-check.o -latf-c++ -latf-c >> /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to >> `std::bad_alloc::~bad_alloc()' >> /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/lib= atf-c++.so: >> undefined reference to `std::bad_alloc::bad_alloc()' >> /usr/obj/usr/src/libexec/atf/atf-check/../../../lib/atf/libatf-c++/lib= atf-c++.so: >> undefined reference to `std::bad_alloc::~bad_alloc()' >> /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to >> `std::bad_alloc::bad_alloc()' >> c++: error: linker command failed with exit code 1 (use -v to see >> invocation) >> *** [atf-check] Error code 1 >> >> Stop in /usr/src/libexec/atf/atf-check. >> *** [all] Error code 1 >> ... >=20 > In contrast, I don't see a problem; most recent head build I have is: >=20 > FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #105= 7 r246057M/246068: Tue Jan 29 07:29:55 PST 2013 root@freebeast.catwh= isker.org:/usr/obj/usr/src/sys/GENERIC i386 >=20 >=20 > For reference, yesterday's was: >=20 > FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #105= 6 r246028M/246028: Mon Jan 28 06:49:44 PST 2013 root@freebeast.catwh= isker.org:/usr/obj/usr/src/sys/GENERIC i386 >=20 >=20 > That said (and this may be relevant), I'm using clang/clang++ to > build FreeBSD. >=20 > Peace, > david >=20 First, I suspected the c++ option "-std=3Dc++11" I issued in /etc/src.con= f when building the sources - I did this before without any problems. Then, leaving the build without "-std=3Dc++11" option, I get the followin= g error below and compilation stops. Maybe this reveals the real issue. The revision of the OS I compile on and where it fails is FreeBSD 10.0-CURRENT #2 r245995: Sun Jan 27 19:56:47 CET 2013. This is maybe of any help. The sources are at Revision: 246142 Oliver [...] /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:3771:14: error: default template arguments for a function template are a C++11 extension [-Werror,-Wc++11-extensions] class =3D typename enable_if ^ ~~~~~~~~~~~~~~~~~~ fatal error: too many errors emitted, stopping now [-ferror-limit=3D] In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applicati= on.cpp:42: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:597:= /usr/obj/usr/src/tmp/usr/include/c++/v1/__functional_base:22:1: error: inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] _LIBCPP_BEGIN_NAMESPACE_STD ^ /usr/obj/usr/src/tmp/usr/include/c++/v1/__config:275:52: note: expanded from macro '_LIBCPP_BEGIN_NAMESPACE_STD' #define _LIBCPP_BEGIN_NAMESPACE_STD namespace std {inline namespace _LIBCPP_NAMESPACE { ^ /usr/obj/usr/src/tmp/usr/include/c++/v1/__config:275:52: note: expanded from macro '_LIBCPP_BEGIN_NAMESPACE_STD' #define _LIBCPP_BEGIN_NAMESPACE_STD namespace std {inline namespace _LIBCPP_NAMESPACE { ^ In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applicati= on.cpp:42: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:614:1: error: inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] _LIBCPP_BEGIN_NAMESPACE_STD ^ /usr/obj/usr/src/tmp/usr/include/c++/v1/__config:275:52: note: expanded from macro '_LIBCPP_BEGIN_NAMESPACE_STD' In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/build.cpp:36: In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/build.hpp:33: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:3764:14: error: default template arguments for a function template are a C++11 extension [-Werror,-Wc++11-extensions] class =3D typename enable_if ^ ~~~~~~~~~~~~~~~~~~ /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:3771:14: error: default template arguments for a function template are a C++11 extension [-Werror,-Wc++11-extensions] class =3D typename enable_if ^ ~~~~~~~~~~~~~~~~~~ fatal error: too many errors emitted, stopping now [-ferror-limit=3D] In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applicati= on.cpp:42: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:599:= /usr/obj/usr/src/tmp/usr/include/c++/v1/tuple:126:1: error: inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] _LIBCPP_BEGIN_NAMESPACE_STD ^ /usr/obj/usr/src/tmp/usr/include/c++/v1/__config:275:52: note: expanded from macro '_LIBCPP_BEGIN_NAMESPACE_STD' #define _LIBCPP_BEGIN_NAMESPACE_STD namespace std {inline namespace _LIBCPP_NAMESPACE { ^ #define _LIBCPP_BEGIN_NAMESPACE_STD namespace std {inline namespace _LIBCPP_NAMESPACE { ^ fatal error: too many errors emitted, stopping now [-ferror-limit=3D] In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applicati= on.cpp:42: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:614:1: error: inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] _LIBCPP_BEGIN_NAMESPACE_STD ^ /usr/obj/usr/src/tmp/usr/include/c++/v1/__config:275:52: note: expanded from macro '_LIBCPP_BEGIN_NAMESPACE_STD' #define _LIBCPP_BEGIN_NAMESPACE_STD namespace std {inline namespace _LIBCPP_NAMESPACE { ^ fatal error: too many errors emitted, stopping now [-ferror-limit=3D] 20 errors generated. 20 errors generated. *** [application.o] Error code 1 *** [application.So] Error code 1 20 errors generated. *** [build.o] Error code 1 20 errors generated. *** [build.So] Error code 1 4 errors *** [all] Error code 2 1 error *** [all] Error code 2 1 error *** [lib__L] Error code 2 1 error *** [libraries] Error code 2 1 error *** [_libraries] Error code 2 1 error *** [buildworld] Error code 2 1 error --------------enig6CFC32B69C58CA091C756559 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRCfUpAAoJEOgBcD7A/5N8J1gH/1Yt0JRbuyugiZatFNOopv98 hH06FuWqC52RJ1OxTdhTYpvTY4roIP0u2B2KE0EQiUxt83pOX0sAJwVw3fDJhTPh od0e+5cEu24Yh2UUKJSbnoNzgs2eXSmM1r7LvWC6jqlNa7PZ7/foXnx17joRaN7m h4imA2unaJAnilAJbYHr52ych7oTNphGqaYKOhmueWrxuMlCj3NwY5Mpe9lVz1zs ss5YDonDZCTjQs/ZBGGSXPConpXrjZbV7ovP3Qd9FG82B+sbb+IbHq95P/YkhoeV p/dVXtPXEWRWL7Ki2fz+w2x0Wa51akgYvWDPfc8mf647o8wO8l1KYZ3wvuxzxQE= =o8B/ -----END PGP SIGNATURE----- --------------enig6CFC32B69C58CA091C756559-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 04:43:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6804CB6C; Thu, 31 Jan 2013 04:43:49 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0B10E9E8; Thu, 31 Jan 2013 04:43:48 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1U0m03-001NOl-LQ>; Thu, 31 Jan 2013 05:43:47 +0100 Received: from e178012136.adsl.alicedsl.de ([85.178.12.136] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1U0m03-0029M4-Gw>; Thu, 31 Jan 2013 05:43:47 +0100 Message-ID: <5109F682.3060604@zedat.fu-berlin.de> Date: Thu, 31 Jan 2013 05:43:46 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jesse Subject: Re: buildworld error References: <51092025.1070906@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE4AB9F986DFE1143261DBD38" X-Originating-IP: 85.178.12.136 Cc: freebsd-current@freebsd.org, Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 04:43:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE4AB9F986DFE1143261DBD38 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 01/31/13 05:06, schrieb Jesse: > z >=20 > On 1/31/13, Jesse wrote: >> i set these in make.conf: >> CXXFLAGS+=3D-stdlib=3Dlibc++ >> CXXFLAGS+=3D-std=3Dc++11 >> >> i comment them and rebuild world ok >> but it works at previous revision. >> >> On 1/30/13, Dimitry Andric wrote: >>> On 2013-01-30 10:37, Jesse wrote: >>>> I just update /usr/src and make buildworld. The building proccess st= op >>>> as >>>> errors: >>>> >>>> =3D=3D=3D> lib/clang/libllvmx86asmparser (all) >>>> =3D=3D=3D> lib/clang/libllvmx86codegen (all) >>>> =3D=3D=3D> lib/clang/libllvmx86desc (all) >>>> =3D=3D=3D> lib/clang/libllvmx86disassembler (all) >>>> =3D=3D=3D> lib/clang/libllvmx86info (all) >>>> =3D=3D=3D> lib/clang/libllvmx86instprinter (all) >>>> =3D=3D=3D> lib/clang/libllvmx86utils (all) >>>> =3D=3D=3D> lib/clang/libllvmdebuginfo (all) >>>> =3D=3D=3D> lib/clang/libllvmexecutionengine (all) >>>> =3D=3D=3D> lib/clang/libllvminterpreter (all) >>>> =3D=3D=3D> lib/clang/libllvmjit (all) >>>> =3D=3D=3D> lib/clang/libllvmmcdisassembler (all) >>>> =3D=3D=3D> lib/clang/libllvmmcjit (all) >>>> =3D=3D=3D> lib/clang/libllvmruntimedyld (all) >>>> =3D=3D=3D> lib/clang/include (all) >>>> 1 error >>>> *** [everything] Error code 2 >>>> 1 error >>>> *** [buildworld] Error code 2 >>>> 1 error >>> >>> Because you are making buildworld with -j, the actual error message i= s >>> not visible. Try searching back in the log to find the actual error,= >>> and post that. Alternatively, make buildworld without -j. >>> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 I see the very same issue and reported this already. Since I'm not a professional developer, I'm not quite sure what and how to report the issue in exactly and accurate. In my case, this issue came "out of the blue". I also have set CXXFLAGS+=3D -stdlib=3Dlibc++ -std=3Dc++11 but in /etc/src.conf. Commenting out "-std=3Dc++11" makes the build of world fail with something like [...] fatal error: too many errors emitted, stopping now [-ferror-limit=3D] In file included from /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applicati= on.cpp:42: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15= : In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434:= In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:5= 94: In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:597:= /usr/obj/usr/src/tmp/usr/include/c++/v1/__functional_base:22:1: error: inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] [...] which sounds strange to me, since I completely erase /usr/obj before building and I do not use a ccache or any other similar facility. Regards, Oliver --------------enigE4AB9F986DFE1143261DBD38 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRCfaDAAoJEOgBcD7A/5N8+GcIAOflxonR+VMye5hROQYu7qwz aVmp26UkuYR/di49BHter+JCd0z5sKfyFLvranVuO6qb6hl+zQRUrcpTg7Rr4EgK udPMDcR4MEARsUz4+v2RfRKyRL4Gz05/svrqlpYxCUJ+x/YFHRldA/bPQkN+5TGP diXdHKlj4CSdurVJgxcUfMKWQKAlHvETJXjADFFMjGhdjIhg8uQPVEs0Gb4eMFsR TEjoEBLoRRwply/QEDb5hGu5zuSsXYHEuvjdEVWaNm5g5QaIr1i0YIGIQQKx/1Ik o10C6EN1aw1g+7+XlwgHc26rEn6QJrStF/S74zzRlCy+l7SI4WF9IjgRJqT99yM= =noou -----END PGP SIGNATURE----- --------------enigE4AB9F986DFE1143261DBD38-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 04:56:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 192A2DA9 for ; Thu, 31 Jan 2013 04:56:27 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp1.insight.synacor.com [208.47.185.23]) by mx1.freebsd.org (Postfix) with ESMTP id B5497A4A for ; Thu, 31 Jan 2013 04:56:25 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.0 cv=Br4fMPr5 c=1 sm=0 a=Dm9TOXL4taQ+Gy1KovpL+A==:17 a=DvSzqBOGy98A:10 a=pedpZTtsAAAA:8 a=pGLkceISAAAA:8 a=JLhMTlgXY2PyJJi2jwEA:9 a=MSl-tDqOz04A:10 a=Dm9TOXL4taQ+Gy1KovpL+A==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Authentication-Results: smtp02.insight.synacor.com header.from=mueller6724@bellsouth.net; sender-id=neutral Received-SPF: softfail (smtp02.insight.synacor.com: transitional domain insightbb.com does not designate 74.130.198.7 as permitted sender) Received: from [74.130.198.7] ([74.130.198.7:50794] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id 13/8E-30544-279F9015; Wed, 30 Jan 2013 23:56:18 -0500 Date: Wed, 30 Jan 2013 23:56:18 -0500 Message-ID: <13.8E.30544.279F9015@smtp02.insight.synacor.com> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: x220 notes Cc: Andrey Fesenko , freebsd-mobile@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 04:56:27 -0000 Excerpt from Andrey Fesenko : > And other problems. > 1) wi-fi > standart rtl8192cu - not work > change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS > dev.acpi_ibm.0.wlan: 1 <- read only > hardware switch work, not send mesage What did you try to make rtl8192cu work? Did you try NDIS? I have Hiro USB wireless adapter with rtl8191s chip, am still trying, on and off, to get it to work. OpenBSD has urtwn driver that should work, ported to NetBSD, but why not FreeBSD? ALso, there is a Linux driver. Tom From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 08:29:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 36743F1D for ; Thu, 31 Jan 2013 08:29:57 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-ea0-f169.google.com (mail-ea0-f169.google.com [209.85.215.169]) by mx1.freebsd.org (Postfix) with ESMTP id C72F8253 for ; Thu, 31 Jan 2013 08:29:56 +0000 (UTC) Received: by mail-ea0-f169.google.com with SMTP id d13so1120600eaa.28 for ; Thu, 31 Jan 2013 00:29:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=dVgpDnIJj1ZouQuJBb0fKu++3lTvsU9xrWczKffcSU0=; b=P2iwHdbpWWdA7sXk/nDawV8oNvgcf0J5KC2ulp06CeRM2g7whD+Em72Q3vrytHOCgu 0nzHFeINizvVF4lVol+jEaZGsJctscwbYf32/sOSjAEtdZV3Ywbq/g4S8VAsShS00qgB nwng4/m6G8Gw3KIs3WWKO2XawwW0LNcfJcnIX/VYjPUCXtLpEIZ4jj8+1jc6ZQny86r5 uXQk94Agc6aSa7qi1w48uY49o+kDBkP+bHy5cwU2QKXOoJ/Yl0fgxPy1atfBZvgnxpx8 cZtLcHrKK0rEfLZ/S55jQgHni95OegqTH6Zfj6OM0nWzvEyC3AdmUx3uCk6GXhKcgCdn Q3tA== MIME-Version: 1.0 X-Received: by 10.14.178.196 with SMTP id f44mr24966330eem.14.1359620990198; Thu, 31 Jan 2013 00:29:50 -0800 (PST) Received: by 10.14.189.5 with HTTP; Thu, 31 Jan 2013 00:29:50 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 09:29:50 +0100 Message-ID: Subject: Re: From: Olivier Smedts To: AN Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkFUNmPRa+TCx61A/uVQ6BsDOUlUp8eZ76bPNOUv1Cmsj5eM6ib9QIdfWDiYE9FZWgphe15 Cc: vbox@freebsd.org, freebsd-current@freebsd.org, theraven@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 08:29:57 -0000 2013/1/30 AN : > With all due respect to developers, are these changes tested at all before > they are added to the codebase? Won't sound respectful if the problem is not related to that commit. Which compiler are you using for the base system, and for ports ? (more specifically for the virtualbox ports) I had the same kind of errors when compiling virtualbox with gcc46, not the one in base. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 09:10:55 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 054FEA29 for ; Thu, 31 Jan 2013 09:10:55 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9DCCC67F for ; Thu, 31 Jan 2013 09:10:54 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r0V9Ae2q010675 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Thu, 31 Jan 2013 09:10:42 GMT (envelope-from theraven@FreeBSD.org) Subject: Re: r246057: buildworld fails with: /usr/obj/usr/src/tmp/usr/lib/libc++.so: undefined reference to `std::bad_alloc::~bad_alloc()' Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/signed; boundary="Apple-Mail=_6659D075-2D74-4D42-AF8A-E5112F8C3092"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: David Chisnall In-Reply-To: <5109F527.2030702@zedat.fu-berlin.de> Date: Thu, 31 Jan 2013 09:10:34 +0000 Message-Id: References: <51079F0A.20309@zedat.fu-berlin.de> <20130129163554.GW1804@albert.catwhisker.org> <5109F527.2030702@zedat.fu-berlin.de> To: "O. Hartmann" X-Mailer: Apple Mail (2.1278) Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 09:10:55 -0000 --Apple-Mail=_6659D075-2D74-4D42-AF8A-E5112F8C3092 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 31 Jan 2013, at 04:37, O. Hartmann wrote: > First, I suspected the c++ option "-std=3Dc++11" I issued in = /etc/src.conf > when building the sources - I did this before without any problems. > Then, leaving the build without "-std=3Dc++11" option, I get the = following > error below and compilation stops. >=20 > Maybe this reveals the real issue. >=20 > The revision of the OS I compile on and where it fails is FreeBSD > 10.0-CURRENT #2 r245995: Sun Jan 27 19:56:47 CET 2013. This is maybe = of > any help. If you are going to compile with -stdlib=3Dlibc++ and not -std=3Dc++11, = then you probably need to add -Wno-c++11-extensions. Some C++11isms = have crept into the libc++ headers. I think some have been fixed = upstream, so I'll do a new import soon and see. David --Apple-Mail=_6659D075-2D74-4D42-AF8A-E5112F8C3092 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQIcBAEBAgAGBQJRCjULAAoJEKx65DEEsqIdA7IP/jfxdUY5d8AGKII979uTc6js qkbdmm+FgygR2NadEclxcX0jBbvtaPRUogkC/TA1Fxcoh4WNT17/0rwJna4KsD5t Bnoc/W556jfV7mACBmJ2qVtQ94V6BNbTZZM0mA7QS4zG5Q22qDM5lRXJdNl/N2gE Q8dINiAsF/toie6yeF4DwZDxhJX9O4c53G9wk8p0MHD5Sw2kofgtE4xZBJ+1bKvK 8f4Q9TeuAruzcPSghUfjUr7qNIpuky9uNGVpzFhfXlBXD2BNv72bVtAfHppS8mPu XRCg013B9iy0F49gMvjfgb1l/HTh1FP63lbf+RsPEZXlSJ7CLIUBrWIZX/UzwRgr EYyVhT0jI6eJh58VFg/i16M4pd0Jtw0+pTkoU9parTC3xZlAXxAzv2Yx9tn0rcGM Ewc6YcjM6RL7e78ZiPDaUZ+nEoO9sAvDfJZsNlbfyPHRSbetINHLzlcIQ66/7c7O P3iTIVUv1oqkHzRH93y6rtP8Q7UuNpCz92NjijTXv21NAgilHBxWVSiEWS6re3rI 3JH0odf6Gd1thKIO1/y7rAIcz0Ff7iuXS1kxVSK/6fy/I0neDGAYv6rOU5ngay62 hwO0v30UE9f5/Ad0NOC7ha+MqsQiEVtP5GHMHED3ZyOWnNLtrBpRSXwGyM41bmpL 7ItyXmq74N9BMEh+lYSH =vIfg -----END PGP SIGNATURE----- --Apple-Mail=_6659D075-2D74-4D42-AF8A-E5112F8C3092-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 09:19:35 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D05FAE55; Thu, 31 Jan 2013 09:19:35 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id A22666FA; Thu, 31 Jan 2013 09:19:35 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r0V9JXdv010705 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Thu, 31 Jan 2013 09:19:34 GMT (envelope-from theraven@FreeBSD.org) Subject: Re: Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/signed; boundary="Apple-Mail=_B8198924-3451-484C-89EB-2BE6FFD81BFA"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: David Chisnall In-Reply-To: Date: Thu, 31 Jan 2013 09:19:27 +0000 Message-Id: <350A05C6-C650-417A-9AD9-09CD54F0838F@FreeBSD.org> References: To: AN X-Mailer: Apple Mail (2.1278) Cc: freebsd-current@FreeBSD.org, vbox@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 09:19:35 -0000 --Apple-Mail=_B8198924-3451-484C-89EB-2BE6FFD81BFA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 30 Jan 2013, at 21:23, AN wrote: > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: = /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by = /usr/local/lib/virtualbox/VBoxRT.so not found GLIBCXX_3.4.15 is the symbol version of the libstdc++ that ships with = gcc 4.6. You are trying to compile something against a (newer) = libstdc++ from ports and then run it linked against the (older) = libstdc++ from the base system. Oddly enough, this doesn't work. David --Apple-Mail=_B8198924-3451-484C-89EB-2BE6FFD81BFA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQIcBAEBAgAGBQJRCjcgAAoJEKx65DEEsqIdvHQQANDCKLiFyeTN1TK0BH4+TRMA X23t3aVpnzH5131YvH6YiblqbHRseEmdK7uYHlr1gJoHZTngfjZ1GMSikJLYVjnn letGpbxL+uNTsICI93upCqYEch6FrZf5hqrZq5qJNHMYEvZQesquy93c7YhcO7Co Mo6WwhUntnV7lJ4fzhCKZGCkKZfa6kYmHX0q4bpvAYHqlMaCmLxuQ9Ni2D8VMMxE 7x1JYhWewQ9zsCrvrSPy5Kw4K4vNeJpjKd9Jt5aaJcQ9YgaySgEEjEdMRY6Lts2T yKKl5AJ1RLrp6X2ZmMJfs7VPm52gQTKQsNwGapTW2pYbxpVs8iAHmrLuX0aiH6fr ZyOp6yC5jLU0S7Rjg5r/cU8c6dhW2RCn06eOyv4/R1QliV1ZaK1vTUh0MNDVI+A5 TpOTs7RU3CHFAgbzszqbIqOnuTISH05mQ1FO5swHpnFVHgNsZI2cGLl5C38HRqxz k9giYIlBRYGjQR039uJG8C6JPG/4VmiXYr3op/anh4qFwIFEWqaF/DhlQv/7KfPn ytj3Ax4lzTEQxpTlWw6J8BZ8PlO+C0vRFVAjq63SPgxzTx3Y1dq/WVPFDr95SWvu x4pkuMn6LRyU/UbLg1QfPTOWUfhL3jn5WpNXqvNT7v6756+Dt56qiNOMFbOJnPBm x3+g08gqEFeozyqxcu3c =wSDs -----END PGP SIGNATURE----- --Apple-Mail=_B8198924-3451-484C-89EB-2BE6FFD81BFA-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 11:20:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C0FC148C; Thu, 31 Jan 2013 11:20:52 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 6C18AD06; Thu, 31 Jan 2013 11:20:52 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1U0sCD-002jTb-9C>; Thu, 31 Jan 2013 12:20:45 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1U0sCD-002Zaj-6g>; Thu, 31 Jan 2013 12:20:45 +0100 Message-ID: <510A5382.6040007@zedat.fu-berlin.de> Date: Thu, 31 Jan 2013 12:20:34 +0100 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130130 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jesse Subject: Re: buildworld error References: <51092025.1070906@FreeBSD.org> <5109F682.3060604@zedat.fu-berlin.de> In-Reply-To: <5109F682.3060604@zedat.fu-berlin.de> X-Enigmail-Version: 1.4.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3399AC121686F78FE176EFED" X-Originating-IP: 130.133.86.198 Cc: David Chisnall , freebsd-current@freebsd.org, Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 11:20:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3399AC121686F78FE176EFED Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/31/13 05:43, O. Hartmann wrote: > Am 01/31/13 05:06, schrieb Jesse: >> z >> >> On 1/31/13, Jesse wrote: >>> i set these in make.conf: >>> CXXFLAGS+=3D-stdlib=3Dlibc++ >>> CXXFLAGS+=3D-std=3Dc++11 >>> >>> i comment them and rebuild world ok >>> but it works at previous revision. >>> >>> On 1/30/13, Dimitry Andric wrote: >>>> On 2013-01-30 10:37, Jesse wrote: >>>>> I just update /usr/src and make buildworld. The building proccess s= top >>>>> as >>>>> errors: >>>>> >>>>> =3D=3D=3D> lib/clang/libllvmx86asmparser (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86codegen (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86desc (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86disassembler (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86info (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86instprinter (all) >>>>> =3D=3D=3D> lib/clang/libllvmx86utils (all) >>>>> =3D=3D=3D> lib/clang/libllvmdebuginfo (all) >>>>> =3D=3D=3D> lib/clang/libllvmexecutionengine (all) >>>>> =3D=3D=3D> lib/clang/libllvminterpreter (all) >>>>> =3D=3D=3D> lib/clang/libllvmjit (all) >>>>> =3D=3D=3D> lib/clang/libllvmmcdisassembler (all) >>>>> =3D=3D=3D> lib/clang/libllvmmcjit (all) >>>>> =3D=3D=3D> lib/clang/libllvmruntimedyld (all) >>>>> =3D=3D=3D> lib/clang/include (all) >>>>> 1 error >>>>> *** [everything] Error code 2 >>>>> 1 error >>>>> *** [buildworld] Error code 2 >>>>> 1 error >>>> >>>> Because you are making buildworld with -j, the actual error message = is >>>> not visible. Try searching back in the log to find the actual error= , >>>> and post that. Alternatively, make buildworld without -j. >>>> >>> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.= org" >> >=20 >=20 > I see the very same issue and reported this already. Since I'm not a > professional developer, I'm not quite sure what and how to report the > issue in exactly and accurate. >=20 > In my case, this issue came "out of the blue". I also have set >=20 > CXXFLAGS+=3D -stdlib=3Dlibc++ -std=3Dc++11 >=20 > but in /etc/src.conf. Commenting out "-std=3Dc++11" makes the build of > world fail with something like >=20 > [...] > fatal error: too many errors emitted, stopping now [-ferror-limit=3D] > In file included from > /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/applica= tion.cpp:42: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:= 38: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:= 15: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:43= 4: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm= :594: > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:59= 7: > /usr/obj/usr/src/tmp/usr/include/c++/v1/__functional_base:22:1: error: > inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] > [...] >=20 > which sounds strange to me, since I completely erase /usr/obj before > building and I do not use a ccache or any other similar facility. >=20 > Regards, > Oliver >=20 >=20 I can confirm, that disabling CXXFLAGS+=3D -stdlib=3Dlibc++ -std=3Dc++11 completely solves the problem. Using -stdlib=3Dlibc++ building the system's sources decalres CURRENT bro= ken. --------------enig3399AC121686F78FE176EFED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJRClONAAoJEOgBcD7A/5N8uaUIALPpEpetxl1X6YFn6LA+m8Yw XFq+pWzR+IXxZYMfaNuTn0JytY//EKmFH4Iv1uSUoevv42pAN+TFW0yKqBYWmODL 61i3hqSfVL7dqgKwFkWcoO3GqeqLgPE/o2lnZYXPv7LArRXUU21LvmIrV3g+BH9M jbhnJbgfYIFPXPmozx9e35QXPyVTQok6vYNJna0xnHvPACoXS4q4gjGMlT8XMj1b fAX8Fr7zboRR22lZZ3uJvi8YjrWZZRDHFFrme/g7dc8zy9jSO/rnQXwAMwvDOpGt H+HWSBrbKw/CsLLMkEii9iaQj5UOYVWti/E9TBY4n8p91Z4vEK/SyWONZIdElNU= =E6NG -----END PGP SIGNATURE----- --------------enig3399AC121686F78FE176EFED-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 11:27:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9A3A96AD for ; Thu, 31 Jan 2013 11:27:38 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 74A39D63 for ; Thu, 31 Jan 2013 11:27:38 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,575,1355126400"; d="scan'208";a="14654774" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 31 Jan 2013 03:27:37 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0VBRbEa014013; Thu, 31 Jan 2013 03:27:37 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Thu, 31 Jan 2013 03:27:36 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAMxdgIAA5iiA Date: Thu, 31 Jan 2013 11:27:36 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <5F5F1DCAE6CC3C46B543F06F365BA3A7@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 11:27:38 -0000 Hi, On Jan 30, 2013, at 22:43, Craig Rodrigues wrote: > What you need to do is, before the FreeBSD kernel boots, your > loader needs to export some environment variables. This will trigger > the various behaviors in the FreeBSD mount code. the loader can export some environment variables (this is how I get the ser= ial console working.) > So as I suggested before, you should continue with: >=20 > (1) Have /usr/home/elars/dst/etc/fstab with: > # Options Dump Pass > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 = 0 Done. > (2) From your loader, you need to export this environment variable, so > that the kernel can get it with getenv(). You need at least: >=20 > vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst Done. > Now, there are some other environment variables you need to export from t= he > loader. =20 >=20 > boot.netif.ip > boot.netif.netmask > boot.netif.gateway > boot.nfsroot.server > boot.nfsroot.path Done. I also ripped out all the BOOTP* options from the kernel. However, this still fails: Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error 19. Loader variables: vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot>=20 I did a tcpdump and no traffic shows up on the correct interface (em4). I g= uess I need to set yet another loader environment variable to indicate whic= h interface I'd like to use. Looking at the source, I only see boot.netif.n= ame, but setting that to em4 doesn't help either. Any further ideas? Thanks, Lars= From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 11:45:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 256C79DD for ; Thu, 31 Jan 2013 11:45:32 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by mx1.freebsd.org (Postfix) with ESMTP id BF341E2F for ; Thu, 31 Jan 2013 11:45:31 +0000 (UTC) Received: by mail-oa0-f48.google.com with SMTP id j1so1597207oag.35 for ; Thu, 31 Jan 2013 03:45:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=RQY+rY7KIFr/XTFFhZ0EwyKdbYj8/ZTe3AjTG3q/Ids=; b=kXH5V5SwCEYYJVR3jQ16Zx3EqEvlJXEM1411oN85AVczAU46SBJUq5YV4HHuuBfx7g arj/EB9UGV8a+taVPADyb2RYHEWPq3ajfJzlwk0fwTlIFomDxI0mQY6vAyeXE0wsAmj1 8HBN46+GqJ8lrlAHX5R7uyLNxEmDFjnXb/iHr9Gb/UbFkcllDaTSyKN76CUbYpmMS8Bc VdcDrhMljlMwRsv1crg8oaFJNXYXBBjLCEGmW1ecyDXGKLaa2BvBO6Os3QeU+rGaZUg9 9okXpCQQfRBAI5nisIUnjc/M4SMLGi4x3m5paqld7FoFceSRO7XeVEgAxvrI4va+Tyy0 emAA== MIME-Version: 1.0 X-Received: by 10.60.32.200 with SMTP id l8mr6558341oei.43.1359632731086; Thu, 31 Jan 2013 03:45:31 -0800 (PST) Received: by 10.76.98.133 with HTTP; Thu, 31 Jan 2013 03:45:30 -0800 (PST) In-Reply-To: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> Date: Thu, 31 Jan 2013 12:45:30 +0100 Message-ID: Subject: Re: mounting root from NFS via ROOTDEVNAME From: Andreas Nilsson To: "Eggert, Lars" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 11:45:32 -0000 Done. I also ripped out all the BOOTP* options from the kernel. > > However, this still fails: > > Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... > mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... > Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error 19. > > Loader variables: > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Manual root filesystem specification: > : [options] > Mount using filesystem > and with the specified (optional) option list. > > eg. ufs:/dev/da0s1a > zfs:tank > cd9660:/dev/acd0 ro > (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) > > ? List valid disk boot devices > . Yield 1 second (for background tasks) > Abort manual input > > mountroot> > > I did a tcpdump and no traffic shows up on the correct interface (em4). I > guess I need to set yet another loader environment variable to indicate > which interface I'd like to use. Looking at the source, I only see > boot.netif.name, but setting that to em4 doesn't help either. > > Any further ideas? > > Thanks, > Lars > Just a shot in the dark, did you actually tell it to do the root mount ro, or try with the nfs share as rw? Best regards Andreas From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 11:53:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1B504CA4 for ; Thu, 31 Jan 2013 11:53:38 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 572B5E88 for ; Thu, 31 Jan 2013 11:53:36 +0000 (UTC) Received: (qmail 35526 invoked from network); 31 Jan 2013 13:13:21 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 31 Jan 2013 13:13:21 -0000 Message-ID: <510A5B32.4070501@freebsd.org> Date: Thu, 31 Jan 2013 12:53:22 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Eggert, Lars" Subject: Re: mounting root from NFS via ROOTDEVNAME References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 11:53:38 -0000 On 31.01.2013 12:27, Eggert, Lars wrote: > Hi, > > On Jan 30, 2013, at 22:43, Craig Rodrigues wrote: >> What you need to do is, before the FreeBSD kernel boots, your >> loader needs to export some environment variables. This will trigger >> the various behaviors in the FreeBSD mount code. > > the loader can export some environment variables (this is how I get the serial console working.) > >> So as I suggested before, you should continue with: >> >> (1) Have /usr/home/elars/dst/etc/fstab with: >> # Options Dump Pass >> 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 > > Done. > >> (2) From your loader, you need to export this environment variable, so >> that the kernel can get it with getenv(). You need at least: >> >> vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Done. > >> Now, there are some other environment variables you need to export from the >> loader. >> >> boot.netif.ip >> boot.netif.netmask >> boot.netif.gateway >> boot.nfsroot.server >> boot.nfsroot.path > > Done. I also ripped out all the BOOTP* options from the kernel. > > However, this still fails: > > Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... > mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... > Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error 19. > > Loader variables: > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Manual root filesystem specification: > : [options] > Mount using filesystem > and with the specified (optional) option list. > > eg. ufs:/dev/da0s1a > zfs:tank > cd9660:/dev/acd0 ro > (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) > > ? List valid disk boot devices > . Yield 1 second (for background tasks) > Abort manual input > > mountroot> > > I did a tcpdump and no traffic shows up on the correct interface (em4). I guess I need to set yet another loader environment variable to indicate which interface I'd like to use. Looking at the source, I only see boot.netif.name, but setting that to em4 doesn't help either. > > Any further ideas? The interface doesn't have a name during loader stage. The kernel finds the interface to use based on the MAC address. You should set boot.netif.hwaddr as well in the kernel environment. -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 12:05:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 92F4C13D for ; Thu, 31 Jan 2013 12:05:52 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0D3F53 for ; Thu, 31 Jan 2013 12:05:52 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,576,1355126400"; d="scan'208";a="14674193" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 31 Jan 2013 04:05:51 -0800 Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0VC5pdE029084; Thu, 31 Jan 2013 04:05:51 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Thu, 31 Jan 2013 04:05:50 -0800 From: "Eggert, Lars" To: Andreas Nilsson Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAMxdgIAA5iiAgAAE/wCAAAWwgA== Date: Thu, 31 Jan 2013 12:05:50 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <720C240043C0274DBA1AC4E058DA35B0@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 12:05:52 -0000 On Jan 31, 2013, at 12:45, Andreas Nilsson wrote: > Just a shot in the dark, did you actually tell it to do the root mount ro= , > or try with the nfs share as rw? ro Lars From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 12:09:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A21472D5; Thu, 31 Jan 2013 12:09:42 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 83CDEFA0; Thu, 31 Jan 2013 12:09:42 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,576,1355126400"; d="scan'208";a="14675909" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 31 Jan 2013 04:09:42 -0800 Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0VC9fia018915; Thu, 31 Jan 2013 04:09:42 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0328.009; Thu, 31 Jan 2013 04:09:41 -0800 From: "Eggert, Lars" To: Andre Oppermann Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAMxdgIAA5iiAgAAHMgCAAASQAA== Date: Thu, 31 Jan 2013 12:09:40 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> <510A5B32.4070501@freebsd.org> In-Reply-To: <510A5B32.4070501@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Craig Rodrigues , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 12:09:42 -0000 On Jan 31, 2013, at 12:53, Andre Oppermann wrote: > The interface doesn't have a name during loader stage. The kernel > finds the interface to use based on the MAC address. You should > set boot.netif.hwaddr as well in the kernel environment. Done, no change. Here is what's in my loader environment: boot.netif.netmask 255.255.255.0 boot.netif.gateway 10.11.12.13 boot.nfsroot.server 10.11.12.13 boot.nfsroot.path /usr/home/elars/dst boot.netif.ip 10.11.12.15 boot.netif.name em4 boot.netif.hwaddr xx:xx:xx:xx:xx:xx vfs.root.mountfrom nfs:10.11.12.13:/usr/home/elars/dst And here is what I see during boot: Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error 19. Lars From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 13:13:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 662EB3CF for ; Thu, 31 Jan 2013 13:13:04 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id DE6A9684 for ; Thu, 31 Jan 2013 13:13:03 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so2117447wey.30 for ; Thu, 31 Jan 2013 05:13:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=rmw8yC4ayMdqsM5rAw5aOJ3FNTAoN5G5snI83CVJfc4=; b=IZwzbBX5pe6bWLmAdBQg/g8LUNUcktjvjKAFqg2CcvYZhfpGzQjYoi+971WduE1py0 sXVmDqAXtK2lkPzmEGn0eql3M+VTakY6iuCqpAIJrbzXEHU9GxfUhjMbeP+4rQUgYGLx d+pEPvAttQ7T6T0OMB3IIJnNoSI5n9qA7YZZ0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=rmw8yC4ayMdqsM5rAw5aOJ3FNTAoN5G5snI83CVJfc4=; b=KJo6/FLX2Nh3tZjQzQruIeuoJzpXNDot0LkZhuMmHBfDKGYox2QG6xBf5LJymywu5s xFaUED0THGj1GZXLufNlHlCeUf+Qbn2lMYPHXTT8a+ohgQs/QBDyKp7k6/sYeoCPkzh6 4a6gl8KfHx2sj8oubUZ18bga2uqEojIs3SsnsSDkTG+reON+8Vum63jUYugy6k04uJAR dlf8u+Dp54ms8ejHM2axUou6jQ1ceOXmDXzTD7OxKxTIfDSEDGMHleIUxtgNGf58mMF/ UksmAiWhOW1McrAT8UFnc28FcpCTGE6vh3HcQyTJ1HDE0uvQzMDSoHb8+vtb/UvC7Wes tH1Q== MIME-Version: 1.0 X-Received: by 10.194.122.98 with SMTP id lr2mr15493249wjb.7.1359637981374; Thu, 31 Jan 2013 05:13:01 -0800 (PST) Received: by 10.194.165.135 with HTTP; Thu, 31 Jan 2013 05:13:01 -0800 (PST) X-Originating-IP: [101.83.47.37] In-Reply-To: <510A5382.6040007@zedat.fu-berlin.de> References: <51092025.1070906@FreeBSD.org> <5109F682.3060604@zedat.fu-berlin.de> <510A5382.6040007@zedat.fu-berlin.de> Date: Thu, 31 Jan 2013 21:13:01 +0800 Message-ID: Subject: Re: buildworld error From: Jesse To: "O. Hartmann" X-Gm-Message-State: ALoCoQnHe2amC2jcFGuSJuzE2uXdo73/LVEVBod56mtvg3cMq/rghFJegQHdh1rjx/fVgaTWQY3x Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: David Chisnall , freebsd-current@freebsd.org, Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 13:13:04 -0000 yes, that may be the reason. I write a simple c++ program in the built-complete system. and compile it: clang++ hello.cpp -std=c++11 -stdlib=libc++ -o hello it reports undefined reference to bad_alloc errors message same as someones discuss in this mail list. I find that it is because -stdlib=libc++ will link /usr/lib/libc++.so. If compile and link the c++ code like this it reports no error: clang++ hello.cpp -c -o hello.o -std=c++11 -stdlib=libc++ clang++ hello.o -o hello /usr/lib/libc++.a The second command will force clang++ to link the static libc++ instead of the shared lib. I think the current src build the libc++.so by false. Maybe libc++.so lacks some object files to wrap. ar -tv /usr/lib/libc++.a will print all of the necessary object files. On Thu, Jan 31, 2013 at 7:20 PM, O. Hartmann wrote: > On 01/31/13 05:43, O. Hartmann wrote: > > Am 01/31/13 05:06, schrieb Jesse: > >> z > >> > >> On 1/31/13, Jesse wrote: > >>> i set these in make.conf: > >>> CXXFLAGS+=-stdlib=libc++ > >>> CXXFLAGS+=-std=c++11 > >>> > >>> i comment them and rebuild world ok > >>> but it works at previous revision. > >>> > >>> On 1/30/13, Dimitry Andric wrote: > >>>> On 2013-01-30 10:37, Jesse wrote: > >>>>> I just update /usr/src and make buildworld. The building proccess > stop > >>>>> as > >>>>> errors: > >>>>> > >>>>> ===> lib/clang/libllvmx86asmparser (all) > >>>>> ===> lib/clang/libllvmx86codegen (all) > >>>>> ===> lib/clang/libllvmx86desc (all) > >>>>> ===> lib/clang/libllvmx86disassembler (all) > >>>>> ===> lib/clang/libllvmx86info (all) > >>>>> ===> lib/clang/libllvmx86instprinter (all) > >>>>> ===> lib/clang/libllvmx86utils (all) > >>>>> ===> lib/clang/libllvmdebuginfo (all) > >>>>> ===> lib/clang/libllvmexecutionengine (all) > >>>>> ===> lib/clang/libllvminterpreter (all) > >>>>> ===> lib/clang/libllvmjit (all) > >>>>> ===> lib/clang/libllvmmcdisassembler (all) > >>>>> ===> lib/clang/libllvmmcjit (all) > >>>>> ===> lib/clang/libllvmruntimedyld (all) > >>>>> ===> lib/clang/include (all) > >>>>> 1 error > >>>>> *** [everything] Error code 2 > >>>>> 1 error > >>>>> *** [buildworld] Error code 2 > >>>>> 1 error > >>>> > >>>> Because you are making buildworld with -j, the actual error message is > >>>> not visible. Try searching back in the log to find the actual error, > >>>> and post that. Alternatively, make buildworld without -j. > >>>> > >>> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > >> > > > > > > I see the very same issue and reported this already. Since I'm not a > > professional developer, I'm not quite sure what and how to report the > > issue in exactly and accurate. > > > > In my case, this issue came "out of the blue". I also have set > > > > CXXFLAGS+= -stdlib=libc++ -std=c++11 > > > > but in /etc/src.conf. Commenting out "-std=c++11" makes the build of > > world fail with something like > > > > [...] > > fatal error: too many errors emitted, stopping now [-ferror-limit=] > > In file included from > > > /usr/src/lib/atf/libatf-c++/../../../contrib/atf/atf-c++/detail/application.cpp:42: > > In file included from > /usr/obj/usr/src/tmp/usr/include/c++/v1/iostream:38: > > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/ios:216: > > In file included from > /usr/obj/usr/src/tmp/usr/include/c++/v1/__locale:15: > > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/string:434: > > In file included from > /usr/obj/usr/src/tmp/usr/include/c++/v1/algorithm:594: > > In file included from /usr/obj/usr/src/tmp/usr/include/c++/v1/memory:597: > > /usr/obj/usr/src/tmp/usr/include/c++/v1/__functional_base:22:1: error: > > inline namespaces are a C++11 feature [-Werror,-Wc++11-extensions] > > [...] > > > > which sounds strange to me, since I completely erase /usr/obj before > > building and I do not use a ccache or any other similar facility. > > > > Regards, > > Oliver > > > > > > > I can confirm, that disabling CXXFLAGS+= -stdlib=libc++ > -std=c++11 completely solves the problem. > > Using -stdlib=libc++ building the system's sources decalres CURRENT broken. > > From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 13:29:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 53FC68CF for ; Thu, 31 Jan 2013 13:29:30 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qc0-f173.google.com (mail-qc0-f173.google.com [209.85.216.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3CD759 for ; Thu, 31 Jan 2013 13:29:29 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id b12so1246200qca.18 for ; Thu, 31 Jan 2013 05:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=1ACWtYK/T05iD0vbu+r+mcHacQPWwFz5zXh2pvFH3DM=; b=AfidqAowsiQNqwEIuQ9mk/ka2lgDfIEs0GLcCNLZNosXIVgxfquiZ4M+e/zxBFsMtU Tg/rixFOZGbHLLQOy+KmsynAssw639Rh5YWcBRsusCMvp4his4GUzU2MFDeAvn+Dr99o 4M8Eq0IO3OTMwimpNfhlCJhjVaReALUSdLIhNHN0TfWMnKbLMtHXPm2yugCJD2KgYpRQ iwCqnW1AeAy52F2GJhPOhm7GQW5/e/ZjpsYfmykO7BJcB4kFh+TTjb8Chhc3zf6j2bTD kf9f3WZu0nGGrk5iGfWVwwxCgZWXZKPYQnUbtXqYVbkhVjCNlUDw8mRvj6/W5mccLoCl oBqg== MIME-Version: 1.0 X-Received: by 10.49.127.199 with SMTP id ni7mr10186899qeb.17.1359638969353; Thu, 31 Jan 2013 05:29:29 -0800 (PST) Received: by 10.229.78.96 with HTTP; Thu, 31 Jan 2013 05:29:29 -0800 (PST) Date: Thu, 31 Jan 2013 16:29:29 +0300 Message-ID: Subject: panic: LK_RETRY set with incompatible flags From: Sergey Kandaurov To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 13:29:30 -0000 Hi. Got this assertion on idle NFS server while `ls -la /.zfs/shares/' issued on NFS client. kern/vfs_vnops.c:_vn_lock() KASSERT((flags & LK_RETRY) == 0 || error == 0, ("LK_RETRY set with incompatible flags (0x%x) or an error occured (%d)", panic: LK_RETRY set with incompatible flags (0x200400) or an error occured (11) What does that mean and how is it possible? As you can see, both parts of assertion failed. 11 is EDEADLK 0x200400: LK_RETRY & LK_UPGRADE Tracing pid 2943 tid 101532 td 0xfffffe004f5b7000 kdb_enter() at kdb_enter+0x3e/frame 0xffffff848e45ef50 vpanic() at vpanic+0x147/frame 0xffffff848e45ef90 kassert_panic() at kassert_panic+0x136/frame 0xffffff848e45f000 _vn_lock() at _vn_lock+0x70/frame 0xffffff848e45f070 zfs_lookup() at zfs_lookup+0x392/frame 0xffffff848e45f100 zfs_freebsd_lookup() at zfs_freebsd_lookup+0x6d/frame 0xffffff848e45f240 VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xc2/frame 0xffffff848e45f260 vfs_cache_lookup() at vfs_cache_lookup+0xcf/frame 0xffffff848e45f2b0 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xc2/frame 0xffffff848e45f2d0 lookup() at lookup+0x548/frame 0xffffff848e45f350 nfsvno_namei() at nfsvno_namei+0x1a5/frame 0xffffff848e45f400 nfsrvd_lookup() at nfsrvd_lookup+0x13a/frame 0xffffff848e45f6b0 nfsrvd_dorpc() at nfsrvd_dorpc+0xca5/frame 0xffffff848e45f8a0 nfssvc_program() at nfssvc_program+0x482/frame 0xffffff848e45fa00 svc_run_internal() at svc_run_internal+0x1e9/frame 0xffffff848e45fba0 svc_thread_start() at svc_thread_start+0xb/frame 0xffffff848e45fbb0 fork_exit() at fork_exit+0x84/frame 0xffffff848e45fbf0 fork_trampoline() at fork_trampoline+0xe/frame 0xffffff848e45fbf0 --- trap 0xc, rip = 0x800883e9a, rsp = 0x7fffffffd488, rbp = 0x7fffffffd730 --- db> show lockedvnods Locked vnodes 0xfffffe02e21b11d8: tag zfs, type VDIR usecount 4, writecount 0, refcount 4 mountedhere 0 flags (VI_ACTIVE) v_object 0xfffffe02d9f2eb40 ref 0 pages 0 lock type zfs: EXCL by thread 0xfffffe004f5b7000 (pid 2943, nfsd, tid 101532) -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 13:37:40 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DB9A0D3C for ; Thu, 31 Jan 2013 13:37:40 +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 1A6277CF for ; Thu, 31 Jan 2013 13:37:39 +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 PAA08400; Thu, 31 Jan 2013 15:37:37 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <510A73A0.9000607@FreeBSD.org> Date: Thu, 31 Jan 2013 15:37:36 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130113 Thunderbird/17.0.2 MIME-Version: 1.0 To: Sergey Kandaurov Subject: Re: panic: LK_RETRY set with incompatible flags References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 13:37:40 -0000 on 31/01/2013 15:29 Sergey Kandaurov said the following: > Hi. > > Got this assertion on idle NFS server while `ls -la /.zfs/shares/' > issued on NFS client. > kern/vfs_vnops.c:_vn_lock() > KASSERT((flags & LK_RETRY) == 0 || error == 0, > ("LK_RETRY set with incompatible flags (0x%x) or > an error occured (%d)", > > panic: LK_RETRY set with incompatible flags (0x200400) or an error occured (11) > > What does that mean and how is it possible? As you can see, both parts > of assertion failed. > 11 is EDEADLK > 0x200400: LK_RETRY & LK_UPGRADE LK_SHARED, not LK_UPGRADE. Apparently the thread already holds an exlusive lock on the vnode, which you confirm below. > Tracing pid 2943 tid 101532 td 0xfffffe004f5b7000 > kdb_enter() at kdb_enter+0x3e/frame 0xffffff848e45ef50 > vpanic() at vpanic+0x147/frame 0xffffff848e45ef90 > kassert_panic() at kassert_panic+0x136/frame 0xffffff848e45f000 > _vn_lock() at _vn_lock+0x70/frame 0xffffff848e45f070 > zfs_lookup() at zfs_lookup+0x392/frame 0xffffff848e45f100 > zfs_freebsd_lookup() at zfs_freebsd_lookup+0x6d/frame 0xffffff848e45f240 > VOP_CACHEDLOOKUP_APV() at VOP_CACHEDLOOKUP_APV+0xc2/frame 0xffffff848e45f260 > vfs_cache_lookup() at vfs_cache_lookup+0xcf/frame 0xffffff848e45f2b0 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xc2/frame 0xffffff848e45f2d0 > lookup() at lookup+0x548/frame 0xffffff848e45f350 > nfsvno_namei() at nfsvno_namei+0x1a5/frame 0xffffff848e45f400 > nfsrvd_lookup() at nfsrvd_lookup+0x13a/frame 0xffffff848e45f6b0 > nfsrvd_dorpc() at nfsrvd_dorpc+0xca5/frame 0xffffff848e45f8a0 > nfssvc_program() at nfssvc_program+0x482/frame 0xffffff848e45fa00 > svc_run_internal() at svc_run_internal+0x1e9/frame 0xffffff848e45fba0 > svc_thread_start() at svc_thread_start+0xb/frame 0xffffff848e45fbb0 > fork_exit() at fork_exit+0x84/frame 0xffffff848e45fbf0 > fork_trampoline() at fork_trampoline+0xe/frame 0xffffff848e45fbf0 > --- trap 0xc, rip = 0x800883e9a, rsp = 0x7fffffffd488, rbp = 0x7fffffffd730 --- > > db> show lockedvnods > Locked vnodes > > 0xfffffe02e21b11d8: tag zfs, type VDIR > usecount 4, writecount 0, refcount 4 mountedhere 0 > flags (VI_ACTIVE) > v_object 0xfffffe02d9f2eb40 ref 0 pages 0 > lock type zfs: EXCL by thread 0xfffffe004f5b7000 (pid 2943, nfsd, > tid 101532) > > > -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 14:54:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4860A1FA; Thu, 31 Jan 2013 14:54:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id E6A6DB37; Thu, 31 Jan 2013 14:54:16 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1U0vWc-0006AD-Vu; Thu, 31 Jan 2013 16:54:03 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: "Eggert, Lars" Subject: Re: mounting root from NFS via ROOTDEVNAME In-reply-to: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> <510A5B32.4070501@freebsd.org> Comments: In-reply-to "Eggert, Lars" message dated "Thu, 31 Jan 2013 12:09:40 +0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Jan 2013 16:54:02 +0200 From: Daniel Braniss Message-ID: Cc: Craig Rodrigues , "freebsd-current@freebsd.org" , Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 14:54:17 -0000 > On Jan 31, 2013, at 12:53, Andre Oppermann > wrote: > > The interface doesn't have a name during loader stage. The kernel > > finds the interface to use based on the MAC address. You should > > set boot.netif.hwaddr as well in the kernel environment. > > Done, no change. Here is what's in my loader environment: > > boot.netif.netmask 255.255.255.0 > boot.netif.gateway 10.11.12.13 > boot.nfsroot.server 10.11.12.13 > boot.nfsroot.path /usr/home/elars/dst > boot.netif.ip 10.11.12.15 > boot.netif.name em4 > boot.netif.hwaddr xx:xx:xx:xx:xx:xx > vfs.root.mountfrom nfs:10.11.12.13:/usr/home/elars/dst > > And here is what I see during boot: > > Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... > mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... > Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error 19. > > Lars a shot in the dark, but is /usr/home/elars/dst properly exported? danny From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 15:03:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EF5BB7C9; Thu, 31 Jan 2013 15:03:56 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id D7BDEC2D; Thu, 31 Jan 2013 15:03:55 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,577,1355126400"; d="scan'208";a="14754200" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 31 Jan 2013 07:03:55 -0800 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0VF3sSH009208; Thu, 31 Jan 2013 07:03:55 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Thu, 31 Jan 2013 07:03:54 -0800 From: "Eggert, Lars" To: Daniel Braniss Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAMxdgIAA5iiAgAAHMgCAAASQAIAALeoAgAACwYA= Date: Thu, 31 Jan 2013 15:03:54 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> <510A5B32.4070501@freebsd.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <6EBB125781D5894DAA770950EC7E4468@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Craig Rodrigues , "freebsd-current@freebsd.org" , Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 15:03:57 -0000 On Jan 31, 2013, at 15:54, Daniel Braniss wrote: > a shot in the dark, but is /usr/home/elars/dst properly exported? Yep, the NFS mount works fine when I use BOOTP with a root-path option Lars From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 15:25:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D5385D30 for ; Thu, 31 Jan 2013 15:25:42 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8EC0DDD7 for ; Thu, 31 Jan 2013 15:25:42 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAL2LClGDaFvO/2dsb2JhbABFhki4a3OCHgEBAQMBAQEBICsgCwUWGAICDRkCKQEJJgYIBwQBHASHagYMrzmSY4Eji36CWIETA4hkin+CL4EcjzCDFYFRNQ X-IronPort-AV: E=Sophos;i="4.84,577,1355115600"; d="scan'208";a="11749121" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 31 Jan 2013 10:25:40 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 0BDDEB3F45; Thu, 31 Jan 2013 10:25:41 -0500 (EST) Date: Thu, 31 Jan 2013 10:25:41 -0500 (EST) From: Rick Macklem To: Lars Eggert Message-ID: <1435656219.2547176.1359645941027.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: mounting root from NFS via ROOTDEVNAME MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: Craig Rodrigues , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 15:25:42 -0000 Lars Eggert wrote: > Hi, > > On Jan 30, 2013, at 22:43, Craig Rodrigues > wrote: > > What you need to do is, before the FreeBSD kernel boots, your > > loader needs to export some environment variables. This will trigger > > the various behaviors in the FreeBSD mount code. > > the loader can export some environment variables (this is how I get > the serial console working.) > > > So as I suggested before, you should continue with: > > > > (1) Have /usr/home/elars/dst/etc/fstab with: > > # Options Dump Pass > > 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 0 > > Done. > > > (2) From your loader, you need to export this environment variable, > > so > > that the kernel can get it with getenv(). You need at least: > > > > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > > Done. > > > Now, there are some other environment variables you need to export > > from the > > loader. > > > > boot.netif.ip > > boot.netif.netmask > > boot.netif.gateway > > boot.nfsroot.server > > boot.nfsroot.path > > Done. I also ripped out all the BOOTP* options from the kernel. > Here is the complete list of environment variables from the comment in sys/nfs/nfs_diskless.c: * The loader is expected to export the following environment variables: 149 * 150 * boot.netif.name name of boot interface 151 * boot.netif.ip IP address on boot interface 152 * boot.netif.netmask netmask on boot interface 153 * boot.netif.gateway default gateway (optional) 154 * boot.netif.hwaddr hardware address of boot interface 155 * boot.nfsroot.server IP address of root filesystem server 156 * boot.nfsroot.path path of the root filesystem on server 157 * boot.nfsroot.nfshandle NFS handle for root filesystem on server 158 * boot.nfsroot.nfshandlelen and length of this handle (for NFSv3 only) 159 * boot.nfsroot.options NFS options for the root filesystem Note that boot.nfsroot.nfshandle and boot.nfsroot.nfshandlelen are not easy to get. pxeboot does a Mount RPC against the NFS server to get them. (Probably the easiest way to find out what they are is to capture packets while doing a mount of the same path and then looking at the capture via wireshark.) For this method to work, you have to specify "options NFS_BOOT", but not the BOOTP* ones for the kernel. > However, this still fails: > > Trying to mount root from nfs:10.11.12.13:/usr/home/elars/dst []... > mountroot: waiting for device 10.11.12.13:/usr/home/elars/dst ... > Mounting from nfs:10.11.12.13:/usr/home/elars/dst failed with error > 19. > > Loader variables: > vfs.root.mountfrom=nfs:10.11.12.13:/usr/home/elars/dst > As far as I can see, the current code does not know how to turn this into a root file handle via a Mount RPC. I think a non-trivial patch to sys/nfs/bootp_subr.c would be required. As such, the only other way to make it work is to use "options NFS_ROOT" and specify the root file handle in the environment variables, as above. (If I recall correctly, the root file handle is specified as a string of hex digits, but look in the code in sys/nfs/nfs_diskless.c to confirm this.) rick > Manual root filesystem specification: > : [options] > Mount using filesystem > and with the specified (optional) option list. > > eg. ufs:/dev/da0s1a > zfs:tank > cd9660:/dev/acd0 ro > (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) > > ? List valid disk boot devices > . Yield 1 second (for background tasks) > Abort manual input > > mountroot> > > I did a tcpdump and no traffic shows up on the correct interface > (em4). I guess I need to set yet another loader environment variable > to indicate which interface I'd like to use. Looking at the source, I > only see boot.netif.name, but setting that to em4 doesn't help either. > > Any further ideas? > > Thanks, > Lars > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 17:13:43 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 14175424 for ; Thu, 31 Jan 2013 17:13:43 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8504063F for ; Thu, 31 Jan 2013 17:13:42 +0000 (UTC) Received: (qmail 36811 invoked from network); 31 Jan 2013 18:33:30 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 31 Jan 2013 18:33:30 -0000 Message-ID: <510AA63D.2080301@freebsd.org> Date: Thu, 31 Jan 2013 18:13:33 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Trouble with recent auto-tuning changes References: <1359310302.93359.48.camel@revolution.hippie.lan> <1359382968.93359.66.camel@revolution.hippie.lan> <5106CF85.8060004@rice.edu> In-Reply-To: <5106CF85.8060004@rice.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@FreeBSD.org, freebsd-current@FreeBSD.org, Alan Cox X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 17:13:43 -0000 On 28.01.2013 20:20, Alan Cox wrote: > On 01/28/2013 08:22, Ian Lepore wrote: >> On Mon, 2013-01-28 at 00:09 -0600, Alan Cox wrote: >>> On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: >>> >>>> I ran into a panic while attempting to un-tar a large file on a >>>> DreamPlug (arm-based system) running -current. The source and dest of >>>> the un-tar is the root filesystem on sdcard, and I get this: >>>> >>>> panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated >>>> >>>> Just before the panic I see the tar process get hung in a "nokva" wait. >>>> 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. >>>> >>>> In r245575 the init order for mbuf limits was changed from >>>> SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the >>>> results of sizing kernel memory. Unfortunately, the process of sizing >>>> kernel memory relies on the mbuf limits; in kmeminit(): >>>> >>>> vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; >>>> >>>> Since r245575, nmbclusters is zero when this line of code runs. If I >>>> manually plugin "32768" (the number tunable_mbinit() comes up with for >>>> this platform) in that line, the panic stops happening. >>>> >>>> So we've got two problems here... one is the circular dependency in >>>> calculating the mbuf limits. The other is the fact that some >>>> non-trivial amount of kernel memory we're allowing for mbufs is actually >>>> being used for other things. That is, if my system was actually using >>>> all the mbufs that tunable_mbinit() allowed for, then this panic while >>>> untarring a huge file would still have happened. >>>> >>>> >>> All of this is factually correct. However, it's a red herring. The real >>> problem is that arm, unlike every other architecture in the tree, does not >>> enable auto-sizing of the kmem map based on the physical memory size. >>> Specifically, you'll find VM_KMEM_SIZE_SCALE defined in >>> "arch"/include/vmparam.h on every other architecture, just not on arm. >>> This auto-sizing overrides the value of VM_KMEM_SIZE. >>> >> Aha. I'll investigate what other architectures do with that and try to >> get the same thing going for arm. >> > > i386 or (32-bit) MIPS would be the most similar. Also, I would > encourage you to look for other definitions that those architectures > have that arm doesn't. As physical memory sizes continue to grow on > arm-based systems, they may require other changes in vmparam.h and the > machine-dependent param.h that were made on those other architectures > year ago. Ian, The patch below should do the trick. Can you please test? > If you have any questions about any of the definitions, feel free to > e-mail me. > > Alan > > P.S. When I get a little more free time, I intend to get in touch with > Andre to address the apparent circular dependency. For now just know > that unless that circular dependency is combined with a lack of kmem map > auto-sizing, like arm, it's basically harmless. I'm working myself through it and will post a patch shortly that untangles a lot of the obscure VM initialization stuff and moves it into the modern SYSINIT world. -- Andre Index: arm/include/vmparam.h =================================================================== --- arm/include/vmparam.h (revision 246082) +++ arm/include/vmparam.h (working copy) @@ -134,13 +134,16 @@ #endif #define VM_MAX_KERNEL_ADDRESS 0xffffffff + /* * Virtual size (bytes) for various kernel submaps. */ - #ifndef VM_KMEM_SIZE -#define VM_KMEM_SIZE (12*1024*1024) +#define VM_KMEM_SIZE (12*1024*1024) #endif +#ifndef VM_KMEM_SIZE_SCALE +#define VM_KMEM_SIZE_SCALE (2) +#endif #define MAXTSIZ (16*1024*1024) #ifndef DFLDSIZ From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 18:17:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5D8AC88; Thu, 31 Jan 2013 18:17:20 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [199.48.129.194]) by mx1.freebsd.org (Postfix) with ESMTP id 5010F927; Thu, 31 Jan 2013 18:17:19 +0000 (UTC) Received: from neu.net (neu.net [199.48.129.194]) by mail.neu.net (8.14.6/8.14.5) with ESMTP id r0VIHBb1010403; Thu, 31 Jan 2013 13:17:12 -0500 (EST) (envelope-from andy@neu.net) Date: Thu, 31 Jan 2013 13:17:11 -0500 (EST) From: AN To: Olivier Smedts Subject: Re: In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.97.6 at my.mail.server X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=4.5 tests=RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.neu.net Cc: vbox@freebsd.org, freebsd-current@freebsd.org, theraven@freebsd.org, decke@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 18:17:20 -0000 On Thu, 31 Jan 2013, Olivier Smedts wrote: > 2013/1/30 AN : >> With all due respect to developers, are these changes tested at all before >> they are added to the codebase? > > Won't sound respectful if the problem is not related to that commit. > > Which compiler are you using for the base system, and for ports ? > (more specifically for the virtualbox ports) I had the same kind of > errors when compiling virtualbox with gcc46, not the one in base. > > -- > Olivier Smedts _ > ASCII ribbon campaign ( ) > e-mail: olivier@gid0.org - against HTML email & vCards X > www: http://www.gid0.org - against proprietary attachments / \ > > "Il y a seulement 10 sortes de gens dans le monde : > ceux qui comprennent le binaire, > et ceux qui ne le comprennent pas." > Hi Olivier: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r246130: Wed Jan 30 15:00:08 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 # cc -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd10.0 Thread model: posix # c++ -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd10.0 Thread model: posix I also have installed as ports: # pkg info |grep gcc gcc-4.7.3.20130119 GNU Compiler Collection 4.7 gcc-4.6.4.20130125 GNU Compiler Collection 4.6 gcc-aux-20120614_1 Version of GCC 4.7 with full Ada support gccmakedep-1.0.2 Create dependencies in makefiles using 'gcc -M' Here is: # cat /etc/make.conf # added by use.perl 2012-12-05 00:36:53 PERL_VERSION=5.16.2 #.include "/usr/local/etc/port_sites.conf" QT4_OPTIONS= QGTKSTYLE MALLOC_PRODUCTION=yes OVERRIDE_LINUX_BASE_PORT=f10 I do not have anything in src.conf I rebuilt Vbox with both gcc-4.6.4.20130125 and gcc-4.7.3.20130119, and I get the same failure which is: # VirtualBox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found If I build Vbox with gcc4.2.1 it fails with: 6 warnings and 2 errors generated. kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o] Error 1 The failing command: @c++ -c -O2 -fPIC -g -pipe -pedantic -Wshadow -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-long-long -Wno-long-long -Wno-delete-non-virtual-dtor -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Main/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/Main/ -I/usr/include -I/usr/X11R6/include -I/usr/local/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/string -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/ipcd -I/usr/local/include/libpng -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" -DPIC -DIN_RING3 -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DIN_RING3 -DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_NETFLT -DVBOX_WITH_CROGL -DVBOX_WITH_GUEST_PROPS -DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_USB_CARDREADER -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_COM_INPROC -DVBOX_WITH_VRDP_VIDEO_CHANNEL -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_EFI -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_VUSB -DVBOX_WITH_HGSMI -DVBOX_WITH_VIDEOHWACCEL -DVBOX_WITH_USB -DVBOX_WITH_EHCI -DVBOX_WITH_EXTPACK -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_CRHGSMI -DVBOX_WITH_NETSHAPER -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o.dep -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Main/src-client/ConsoleImpl2.cpp *** [do-build] Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** [install] Error code 1 See full log here: http://sebsauvage.net/paste/?ca19b77777ca1a9e#4ZPQHnM4hsCAIk2mUxbejW1zvNfCv3uGqR52u4j6fLs= So it seems Vbox is broken using any GCC compiler right now. I do not know how to get Vbox to use clang compiler. IIRC, Vbox will not build with clang (I could be wrong). You said "I had the same kind of > errors when compiling virtualbox with gcc46, not the one in base." What revision number are you at? Does Vbox work for you right now? How do you compile VBox? What do I need to do to make Vbox work again? From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 16:58:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 140B2F40; Thu, 31 Jan 2013 16:58:01 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by mx1.freebsd.org (Postfix) with ESMTP id BF311342; Thu, 31 Jan 2013 16:58:00 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id h2so1073659oag.24 for ; Thu, 31 Jan 2013 08:57:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=exYsyx9mMwbYGHT1Ep73bN5lFBwt9kpNs5V2/LJFpl0=; b=Xh+1Nk8sgmAR6hjEaQYz7QkThjZbKDGkSv4JOObyetLkuY8kYzr8SHA4Ma3SzvOE7J Dl3W7a9tQnHE1Zg4gAohcJ5wuYW7HEdHaMSzGdf9FhhGyabj+dZlSn2ZPmUyYX5gVsjD hjNTQdCS+uEp/aM2wvZlqYjG/QQgrqL9DxTLlnvpMnbVLVH6Wqr8Rpe3NEJMscCoPPKe NfdKYdD29HcbRP49n+7jEn0FjHJRgENNDdiC72DIRMvBq/hgEOpg7hY1KU0TJjzpt4Hm YpwdAkah8ELyc7RI6GNdJlG3osjw9TLO+TeAX0MYT4pFh4GEtyfqSXZaXEexnO8MOR8A Ydww== MIME-Version: 1.0 X-Received: by 10.182.152.9 with SMTP id uu9mr7068046obb.9.1359651474136; Thu, 31 Jan 2013 08:57:54 -0800 (PST) Received: by 10.76.27.9 with HTTP; Thu, 31 Jan 2013 08:57:54 -0800 (PST) Date: Thu, 31 Jan 2013 08:57:54 -0800 Message-ID: Subject: Panic when closing lid on CURRENT with netbook From: Garrett Cooper To: Jung-uk Kim Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Thu, 31 Jan 2013 21:14:22 +0000 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 16:58:01 -0000 I updated my Asus EEEPC netbook from sources earlier on this month to yesterday's sources, and whenever I shut the lid it now panics with use after free (0xcacacaca) in AcpiEvNotifyDispatch. I understand that ACPICA was updated recently, so my guess is that this is the root cause (was the fix for this r246042?). I was wondering if this is a known issue. Have coredumps if needed. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 22:25:24 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 423C022A; Thu, 31 Jan 2013 22:25:24 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id F2EFF7F4; Thu, 31 Jan 2013 22:25:23 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r0VMPNPf015077; Thu, 31 Jan 2013 15:25:23 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r0VMPLIJ025445; Thu, 31 Jan 2013 15:25:21 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: Trouble with recent auto-tuning changes From: Ian Lepore To: Andre Oppermann In-Reply-To: <510AA63D.2080301@freebsd.org> References: <1359310302.93359.48.camel@revolution.hippie.lan> <1359382968.93359.66.camel@revolution.hippie.lan> <5106CF85.8060004@rice.edu> <510AA63D.2080301@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Thu, 31 Jan 2013 15:25:20 -0700 Message-ID: <1359671120.93359.343.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: alc@FreeBSD.org, freebsd-current@FreeBSD.org, Alan Cox X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 22:25:24 -0000 On Thu, 2013-01-31 at 18:13 +0100, Andre Oppermann wrote: > On 28.01.2013 20:20, Alan Cox wrote: > > On 01/28/2013 08:22, Ian Lepore wrote: > >> On Mon, 2013-01-28 at 00:09 -0600, Alan Cox wrote: > >>> On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: > >>> > >>>> I ran into a panic while attempting to un-tar a large file on a > >>>> DreamPlug (arm-based system) running -current. The source and dest of > >>>> the un-tar is the root filesystem on sdcard, and I get this: > >>>> > >>>> panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated > >>>> > >>>> Just before the panic I see the tar process get hung in a "nokva" wait. > >>>> 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. > >>>> > >>>> In r245575 the init order for mbuf limits was changed from > >>>> SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the > >>>> results of sizing kernel memory. Unfortunately, the process of sizing > >>>> kernel memory relies on the mbuf limits; in kmeminit(): > >>>> > >>>> vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; > >>>> > >>>> Since r245575, nmbclusters is zero when this line of code runs. If I > >>>> manually plugin "32768" (the number tunable_mbinit() comes up with for > >>>> this platform) in that line, the panic stops happening. > >>>> > >>>> So we've got two problems here... one is the circular dependency in > >>>> calculating the mbuf limits. The other is the fact that some > >>>> non-trivial amount of kernel memory we're allowing for mbufs is actually > >>>> being used for other things. That is, if my system was actually using > >>>> all the mbufs that tunable_mbinit() allowed for, then this panic while > >>>> untarring a huge file would still have happened. > >>>> > >>>> > >>> All of this is factually correct. However, it's a red herring. The real > >>> problem is that arm, unlike every other architecture in the tree, does not > >>> enable auto-sizing of the kmem map based on the physical memory size. > >>> Specifically, you'll find VM_KMEM_SIZE_SCALE defined in > >>> "arch"/include/vmparam.h on every other architecture, just not on arm. > >>> This auto-sizing overrides the value of VM_KMEM_SIZE. > >>> > >> Aha. I'll investigate what other architectures do with that and try to > >> get the same thing going for arm. > >> > > > > i386 or (32-bit) MIPS would be the most similar. Also, I would > > encourage you to look for other definitions that those architectures > > have that arm doesn't. As physical memory sizes continue to grow on > > arm-based systems, they may require other changes in vmparam.h and the > > machine-dependent param.h that were made on those other architectures > > year ago. > > Ian, > > The patch below should do the trick. Can you please test? Yep, that fixed the problem with untarring the large file. Here are some before/after numbers from sysctl, converted from bytes to KBytes for readability: vm.kmem_size_scale: 0 2 vm.kmem_map_free: 5740 246440 vm.kmem_map_size: 6548 7176 vm.kmem_size: 12288 253616 real memory = 536870912 (512 MB) avail memory = 516718592 (492 MB) -- Ian From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 22:52:47 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B31D5CFA for ; Thu, 31 Jan 2013 22:52:47 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by mx1.freebsd.org (Postfix) with ESMTP id 5A9DB929 for ; Thu, 31 Jan 2013 22:52:47 +0000 (UTC) Received: by mail-vc0-f177.google.com with SMTP id m18so2080956vcm.8 for ; Thu, 31 Jan 2013 14:52:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=l8OeIY2z62pFWa9RMFpwYjpaOxkXziqn3dCr9XLVsEA=; b=e7XxRo1XuaGnHo7Iq2iKqvz7/dMVsPLLORltzZLOoMphzOK107rXY4hVa0VekXG+bA EqwwAqUJWlw2ZLCYwgnAuv+WZ74SeWHRisqzFqLrur0PrEbCsDkq06uTC0U87WVGimUr 811a/FEk4au++ABEFdK2bIb+Kiks6CqewYUtTQdeJAkkwoq0cjjex9RJFY4glQVFIAuP DA+PixOFV3J6f4qPeACecEc4nSvpuv+uALNuPysCRMH++i5eJ1eaeYo2gPa13ij1+Gy9 aI+CdTmQFpQkkH9H81/QAgUyj60WiUyLqqpcBIORRymnXrqhA7BA4beo5Yirmsq6+MHR P6/g== MIME-Version: 1.0 X-Received: by 10.52.26.229 with SMTP id o5mr8418951vdg.66.1359672766837; Thu, 31 Jan 2013 14:52:46 -0800 (PST) Received: by 10.220.21.141 with HTTP; Thu, 31 Jan 2013 14:52:46 -0800 (PST) Date: Thu, 31 Jan 2013 14:52:46 -0800 Message-ID: Subject: PATCH: display MSI-X table and pba offsets from "pciconf -c" From: Neel Natu To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 22:52:47 -0000 Hi, The following patch teaches pciconf(8) to display the table and pba offsets when it displays the MSI-X capability. The new output format will look like: cap 11[70] = MSI-X supports 10 messages in map 0x1c[0x0][0x2000] enabled OR cap 11[70] = MSI-X supports 10 messages in maps 0x10[0x0] and 0x14[0x1000] enabled Any objections to committing the patch? best Neel Index: usr.sbin/pciconf/cap.c =================================================================== --- cap.c (revision 246087) +++ cap.c (working copy) @@ -449,22 +449,30 @@ static void cap_msix(int fd, struct pci_conf *p, uint8_t ptr) { - uint32_t val; + uint32_t val, table_offset, pba_offset; uint16_t ctrl; int msgnum, table_bar, pba_bar; ctrl = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_CTRL, 2); msgnum = (ctrl & PCIM_MSIXCTRL_TABLE_SIZE) + 1; + val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_TABLE, 4); table_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); + table_offset = val & ~PCIM_MSIX_BIR_MASK; + val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_PBA, 4); - pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); + pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); + pba_offset = val & ~PCIM_MSIX_BIR_MASK; + printf("MSI-X supports %d message%s ", msgnum, (msgnum == 1) ? "" : "s"); - if (table_bar == pba_bar) - printf("in map 0x%x", table_bar); - else - printf("in maps 0x%x and 0x%x", table_bar, pba_bar); + if (table_bar == pba_bar) { + printf("in map 0x%x[0x%x][0x%x]", + table_bar, table_offset, pba_offset); + } else { + printf("in maps 0x%x[0x%x] and 0x%x[0x%x]", + table_bar, table_offset, pba_bar, pba_offset); + } if (ctrl & PCIM_MSIXCTRL_MSIX_ENABLE) printf(" enabled"); } From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 23:14:01 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 455A2FF8 for ; Thu, 31 Jan 2013 23:14:01 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by mx1.freebsd.org (Postfix) with ESMTP id C91E89FF for ; Thu, 31 Jan 2013 23:14:00 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id dr13so2403530wgb.26 for ; Thu, 31 Jan 2013 15:13:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Y/NZnWhQHuS7kRVOW0spt79qokXPuHIjjshvaUGTnQ4=; b=kznJD76lkDg7KkYpOSKDMgLRMU4Wb1WWrNM77164Ni3ojCaPlxQJRjiVvOXadukuhw SHRCHfFCeIWTFwyE5neM9AR4dDVGOeKdplXx26KK0r4LBrlHBUgvYUp9WLa+qiu9uj+J pjLHpy6K1jxFl1wbVYo1DUa9XJZSK2qwUXGkv+cOiZym632iVe9aBanThnZIwJU1+9SL JQ5BwNTgW2b/ozwoLSmUfmM3a0yqagZr/3m0g95AZRBt70XS7ULoAkPwY9hOV8wUTHrC DwTHHp1Whf/US+KIgcH2f8bxfLPUGBLg+jaxzGu/T+3mpV9ZtcxpiOMzhedfOwulSm64 1hcw== MIME-Version: 1.0 X-Received: by 10.180.97.4 with SMTP id dw4mr17863049wib.16.1359674039711; Thu, 31 Jan 2013 15:13:59 -0800 (PST) Received: by 10.216.118.7 with HTTP; Thu, 31 Jan 2013 15:13:59 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 16:13:59 -0700 Message-ID: Subject: Re: PATCH: display MSI-X table and pba offsets from "pciconf -c" From: Jim Harris To: Neel Natu Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 23:14:01 -0000 On Thu, Jan 31, 2013 at 3:52 PM, Neel Natu wrote: > Hi, > > The following patch teaches pciconf(8) to display the table and pba > offsets when it displays the MSI-X capability. > > The new output format will look like: > > cap 11[70] = MSI-X supports 10 messages in map 0x1c[0x0][0x2000] enabled > OR > cap 11[70] = MSI-X supports 10 messages in maps 0x10[0x0] and > 0x14[0x1000] enabled > > Any objections to committing the patch? > Functionally I think this is a good addition. More information from pciconf the better. Other comments below. > best > Neel > > Index: usr.sbin/pciconf/cap.c > =================================================================== > --- cap.c (revision 246087) > +++ cap.c (working copy) > @@ -449,22 +449,30 @@ > static void > cap_msix(int fd, struct pci_conf *p, uint8_t ptr) > { > - uint32_t val; > + uint32_t val, table_offset, pba_offset; > Variables should be in alphabetical order. > uint16_t ctrl; > int msgnum, table_bar, pba_bar; > > ctrl = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_CTRL, 2); > msgnum = (ctrl & PCIM_MSIXCTRL_TABLE_SIZE) + 1; > + > Newline added intentionally? > val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_TABLE, 4); > table_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > + table_offset = val & ~PCIM_MSIX_BIR_MASK; > + > val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_PBA, 4); > - pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > + pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > Looks like these two lines only have whitespace difference. > + pba_offset = val & ~PCIM_MSIX_BIR_MASK; > + > printf("MSI-X supports %d message%s ", msgnum, > (msgnum == 1) ? "" : "s"); > - if (table_bar == pba_bar) > - printf("in map 0x%x", table_bar); > - else > - printf("in maps 0x%x and 0x%x", table_bar, pba_bar); > + if (table_bar == pba_bar) { > + printf("in map 0x%x[0x%x][0x%x]", > + table_bar, table_offset, pba_offset); > + } else { > + printf("in maps 0x%x[0x%x] and 0x%x[0x%x]", > + table_bar, table_offset, pba_bar, pba_offset); > + } > Seems like at least for the case where the table and pba are behind different BARs, this will exceed 80 characters. So maybe the maps always go on a new line? Similar to what's done at the end of cap_express for printing the link speed. > if (ctrl & PCIM_MSIXCTRL_MSIX_ENABLE) > printf(" enabled"); > } > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Jan 31 23:18:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 258981E7 for ; Thu, 31 Jan 2013 23:18:44 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-ee0-f46.google.com (mail-ee0-f46.google.com [74.125.83.46]) by mx1.freebsd.org (Postfix) with ESMTP id B7D58A3E for ; Thu, 31 Jan 2013 23:18:43 +0000 (UTC) Received: by mail-ee0-f46.google.com with SMTP id e49so1761604eek.19 for ; Thu, 31 Jan 2013 15:18:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=9NCu+kBCfodWuf1cWXsoso8weB4KgjQRIt+KJP+YnL0=; b=mBU7vZ0MjXBjdVHzcLL/vJYU8f6IUq+RulH12wJtctlxzeSozuxpcso4IkKS7vzubD JzeMZurR98VwlG9VWAZZTEzOENYn4L0Y7TuWPY11TUR8wkJ6jt+Rx7/W5LtpP2dqMEBj NKCKnTJxT8TDa8eINr7InE2WQeYWhGhdlCA/ADsLXkRp6uyEMKnQPITobwLgVtQIbpql /YgC6us5SBTgqH6dnxqOmJFTqULV+JLI6ZGa56xEd02TM3/lCKVFYZ37WsPkgWXabgaH NVVBcweWPGzgh8UQN36vdPFTPHoVbPLfDeCUyBieTSr/ggcmHNqF5ydPqooMUCtRqUrz cXGQ== MIME-Version: 1.0 X-Received: by 10.14.194.195 with SMTP id m43mr32488890een.44.1359674317319; Thu, 31 Jan 2013 15:18:37 -0800 (PST) Received: by 10.14.189.5 with HTTP; Thu, 31 Jan 2013 15:18:37 -0800 (PST) In-Reply-To: References: Date: Fri, 1 Feb 2013 00:18:37 +0100 Message-ID: Subject: Re: From: Olivier Smedts To: AN Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl01STIn+yRG+GPOtvqlrkV+xPAHY34mnSRWR3zy6d41jcGv4oVs7jxJbfnKYbSMlK5UPi9 Cc: vbox@freebsd.org, freebsd-current@freebsd.org, theraven@freebsd.org, decke@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 23:18:44 -0000 2013/1/31 AN : > > > On Thu, 31 Jan 2013, Olivier Smedts wrote: > >> 2013/1/30 AN : >>> >>> With all due respect to developers, are these changes tested at all >>> before >>> they are added to the codebase? >> >> >> Won't sound respectful if the problem is not related to that commit. >> >> Which compiler are you using for the base system, and for ports ? >> (more specifically for the virtualbox ports) I had the same kind of >> errors when compiling virtualbox with gcc46, not the one in base. >> >> -- >> Olivier Smedts _ >> ASCII ribbon campaign ( ) >> e-mail: olivier@gid0.org - against HTML email & vCards X >> www: http://www.gid0.org - against proprietary attachments / \ >> >> "Il y a seulement 10 sortes de gens dans le monde : >> ceux qui comprennent le binaire, >> et ceux qui ne le comprennent pas." >> > > > Hi Olivier: > > > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r246130: Wed Jan 30 > 15:00:08 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > # cc -v > FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 > Target: x86_64-unknown-freebsd10.0 > Thread model: posix > The answers are in your reply : > # c++ -v > FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 > Target: x86_64-unknown-freebsd10.0 > Thread model: posix So "c++" is clang, not base gcc. > I also have installed as ports: > > # pkg info |grep gcc > gcc-4.7.3.20130119 GNU Compiler Collection 4.7 > gcc-4.6.4.20130125 GNU Compiler Collection 4.6 > gcc-aux-20120614_1 Version of GCC 4.7 with full Ada support > gccmakedep-1.0.2 Create dependencies in makefiles using 'gcc > -M' > > Here is: > > # cat /etc/make.conf > > # added by use.perl 2012-12-05 00:36:53 > PERL_VERSION=5.16.2 > > #.include "/usr/local/etc/port_sites.conf" > > QT4_OPTIONS= QGTKSTYLE > MALLOC_PRODUCTION=yes > > OVERRIDE_LINUX_BASE_PORT=f10 > > > I do not have anything in src.conf > > I rebuilt Vbox with both gcc-4.6.4.20130125 and gcc-4.7.3.20130119, and I > get the same failure which is: > > # VirtualBox > VirtualBox: Error -610 in supR3HardenedMainInitRuntime! > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: > /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by > /usr/local/lib/virtualbox/VBoxRT.so not found > > > If I build Vbox with gcc4.2.1 it fails with: > > 6 warnings and 2 errors generated. > kmk: *** > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o] > Error 1 > The failing command: > @c++ -c -O2 -fPIC -g -pipe -pedantic -Wshadow -Wshadow -Wall -Wextra > -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs > -fdiagnostics-show-option -Wno-long-long -Wno-long-long > -Wno-delete-non-virtual-dtor -Wno-variadic-macros -Wno-long-long > -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions > -frtti -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing > -fvisibility-inlines-hidden -fvisibility=hidden > -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64 > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Main/include > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/Main/ > -I/usr/include -I/usr/X11R6/include -I/usr/local/include > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/string > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/ipcd > -I/usr/local/include/libpng > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/include > -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release > -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS > -DVBOX_WITH_HARDENING -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 > -D__AMD64__ -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" > -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" > -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" > -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" -DPIC -DIN_RING3 > -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DIN_RING3 > -DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE > -DVBOX_WITH_NETFLT -DVBOX_WITH_CROGL -DVBOX_WITH_GUEST_PROPS > -DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_USB_CARDREADER > -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_COM_INPROC > -DVBOX_WITH_VRDP_VIDEO_CHANNEL -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA > -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_EFI > -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_VUSB -DVBOX_WITH_HGSMI > -DVBOX_WITH_VIDEOHWACCEL -DVBOX_WITH_USB -DVBOX_WITH_EHCI > -DVBOX_WITH_EXTPACK -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_CRHGSMI > -DVBOX_WITH_NETSHAPER You can see the command failing is "c++", so... clang. Because WITH_CLANG_IS_CC is default on 10-CURRENT now. > -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o.dep > -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o > -Wp,-MP -o > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Main/src-client/ConsoleImpl2.cpp > *** [do-build] Error code 2 > > Stop in /usr/ports/emulators/virtualbox-ose. > *** [install] Error code 1 > > See full log here: > http://sebsauvage.net/paste/?ca19b77777ca1a9e#4ZPQHnM4hsCAIk2mUxbejW1zvNfCv3uGqR52u4j6fLs= > > So it seems Vbox is broken using any GCC compiler right now. I do not know > how to get Vbox to use clang compiler. IIRC, Vbox will not build with clang > (I could be wrong). > > > You said "I had the same kind of > >> errors when compiling virtualbox with gcc46, not the one in base." > > > What revision number are you at? Does Vbox work for you right now? How do > you compile VBox? Yes, it works when I compile it with base gcc (4.2). > What do I need to do to make Vbox work again? You can compile it with base gcc (read : not "c++" but "g++"). And apologise for your flames against the r246028 commiter ;-) Cheers -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 00:37:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1CD96E9E; Fri, 1 Feb 2013 00:37:53 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [199.48.129.194]) by mx1.freebsd.org (Postfix) with ESMTP id BC3F4E10; Fri, 1 Feb 2013 00:37:51 +0000 (UTC) Received: from neu.net (neu.net [199.48.129.194]) by mail.neu.net (8.14.6/8.14.5) with ESMTP id r110bnZT011462; Thu, 31 Jan 2013 19:37:50 -0500 (EST) (envelope-from andy@neu.net) Date: Thu, 31 Jan 2013 19:37:49 -0500 (EST) From: AN To: Olivier Smedts Subject: Re: In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.97.6 at my.mail.server X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=4.5 tests=RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.neu.net Cc: vbox@freebsd.org, freebsd-current@freebsd.org, theraven@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 00:37:53 -0000 On Fri, 1 Feb 2013, Olivier Smedts wrote: > 2013/1/31 AN : >> >> >> On Thu, 31 Jan 2013, Olivier Smedts wrote: >> >>> 2013/1/30 AN : >>>> >>>> With all due respect to developers, are these changes tested at all >>>> before >>>> they are added to the codebase? >>> >>> >>> Won't sound respectful if the problem is not related to that commit. >>> >>> Which compiler are you using for the base system, and for ports ? >>> (more specifically for the virtualbox ports) I had the same kind of >>> errors when compiling virtualbox with gcc46, not the one in base. >>> >>> -- >>> Olivier Smedts _ >>> ASCII ribbon campaign ( ) >>> e-mail: olivier@gid0.org - against HTML email & vCards X >>> www: http://www.gid0.org - against proprietary attachments / \ >>> >>> "Il y a seulement 10 sortes de gens dans le monde : >>> ceux qui comprennent le binaire, >>> et ceux qui ne le comprennent pas." >>> >> >> >> Hi Olivier: >> >> >> FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #33 r246130: Wed Jan 30 >> 15:00:08 EST 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 >> >> # cc -v >> FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 >> Target: x86_64-unknown-freebsd10.0 >> Thread model: posix >> > > The answers are in your reply : > >> # c++ -v >> FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 >> Target: x86_64-unknown-freebsd10.0 >> Thread model: posix > > So "c++" is clang, not base gcc. > >> I also have installed as ports: >> >> # pkg info |grep gcc >> gcc-4.7.3.20130119 GNU Compiler Collection 4.7 >> gcc-4.6.4.20130125 GNU Compiler Collection 4.6 >> gcc-aux-20120614_1 Version of GCC 4.7 with full Ada support >> gccmakedep-1.0.2 Create dependencies in makefiles using 'gcc >> -M' >> >> Here is: >> >> # cat /etc/make.conf >> >> # added by use.perl 2012-12-05 00:36:53 >> PERL_VERSION=5.16.2 >> >> #.include "/usr/local/etc/port_sites.conf" >> >> QT4_OPTIONS= QGTKSTYLE >> MALLOC_PRODUCTION=yes >> >> OVERRIDE_LINUX_BASE_PORT=f10 >> >> >> I do not have anything in src.conf >> >> I rebuilt Vbox with both gcc-4.6.4.20130125 and gcc-4.7.3.20130119, and I >> get the same failure which is: >> >> # VirtualBox >> VirtualBox: Error -610 in supR3HardenedMainInitRuntime! >> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: >> /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by >> /usr/local/lib/virtualbox/VBoxRT.so not found >> >> >> If I build Vbox with gcc4.2.1 it fails with: >> >> 6 warnings and 2 errors generated. >> kmk: *** >> [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC/src-client/ConsoleImpl2.o] >> Error 1 >> The failing command: >> @c++ -c -O2 -fPIC -g -pipe -pedantic -Wshadow -Wshadow -Wall -Wextra >> -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs >> -fdiagnostics-show-option -Wno-long-long -Wno-long-long >> -Wno-delete-non-virtual-dtor -Wno-variadic-macros -Wno-long-long >> -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions >> -frtti -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing >> -fvisibility-inlines-hidden -fvisibility=hidden >> -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64 >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/src/VBox/Main/include >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/VBoxC >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/obj/Main/ >> -I/usr/include -I/usr/X11R6/include -I/usr/local/include >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/string >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/xpcom >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release/bin/sdk/bindings/xpcom/include/ipcd >> -I/usr/local/include/libpng >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/include >> -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.6/out/freebsd.amd64/release >> -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS >> -DVBOX_WITH_HARDENING -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 >> -D__AMD64__ -DRTPATH_APP_PRIVATE=\"/usr/local/share/virtualbox-ose\" >> -DRTPATH_APP_PRIVATE_ARCH=\"/usr/local/lib/virtualbox\" >> -DRTPATH_SHARED_LIBS=\"/usr/local/lib/virtualbox\" >> -DRTPATH_APP_DOCS=\"/usr/local/share/doc/virtualbox-ose\" -DPIC -DIN_RING3 >> -DUNICODE -DNDEBUG=1 -DVBOX_WITH_XPCOM -DIN_RING3 >> -DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE >> -DVBOX_WITH_NETFLT -DVBOX_WITH_CROGL -DVBOX_WITH_GUEST_PROPS >> -DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_USB_CARDREADER >> -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_COM_INPROC >> -DVBOX_WITH_VRDP_VIDEO_CHANNEL -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA >> -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_EFI >> -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_VUSB -DVBOX_WITH_HGSMI >> -DVBOX_WITH_VIDEOHWACCEL -DVBOX_WITH_USB -DVBOX_WITH_EHCI >> -DVBOX_WITH_EXTPACK -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_CRHGSMI >> -DVBOX_WITH_NETSHAPER > > You can see the command failing is "c++", so... clang. Because > WITH_CLANG_IS_CC is default on 10-CURRENT now. Hi Olivier: After adding USE_GCC= 4.2+ to the VBox makefile and recompiling Vbox is working again. I sincerely apologize to theraven@, and all developers. My intention was not to flame or disrespect anyone. I appreciate and am grateful to all the developers who work on FreeBSD, thank you for your efforts. Thanks for your help, Andy From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 00:37:55 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EF6A7F91 for ; Fri, 1 Feb 2013 00:37:55 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by mx1.freebsd.org (Postfix) with ESMTP id B63CAE12 for ; Fri, 1 Feb 2013 00:37:55 +0000 (UTC) Received: by mail-vb0-f51.google.com with SMTP id fq11so2106397vbb.38 for ; Thu, 31 Jan 2013 16:37:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hY366jadNzK+iBGNSG/LCfYlrHONne3Pd+vjteD3lcM=; b=EEJZdiTx8Ap/WfC2EVIoNnh63C5UlBW8X4jgYsFUbGDX6NqiTM+AwH+toVEXOjSOIf JiMzqB3T29fNG5cci2OlaByL4frjHBMF84BoF8fqyKOiFUlppexCZqZvcCyCzXI9CRQ4 GdCSRCjlpkwySpTWzyFsKanoaG3Ls03nrvfdgIEgbikQPMQVIcUdM2vMaMclLnIAFy7u /Ee39EUuwzuX+xt8NxqcQvdbOsLmMdqsBLbmNm6gIk7Vi+VYNvFi3kz4dmTWNDH+We/5 D3RYVxFHPNifvbH9lVKKjg6d1IdfRMdKbIsUWZqoz63P0YJMOdPmXXvSvIy78oqt08M8 EYQA== MIME-Version: 1.0 X-Received: by 10.58.8.82 with SMTP id p18mr5612286vea.54.1359679068944; Thu, 31 Jan 2013 16:37:48 -0800 (PST) Received: by 10.220.21.141 with HTTP; Thu, 31 Jan 2013 16:37:48 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 16:37:48 -0800 Message-ID: Subject: Re: PATCH: display MSI-X table and pba offsets from "pciconf -c" From: Neel Natu To: Jim Harris Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 00:37:56 -0000 Hi Jim, On Thu, Jan 31, 2013 at 3:13 PM, Jim Harris wrote: > > > On Thu, Jan 31, 2013 at 3:52 PM, Neel Natu wrote: >> >> Hi, >> >> The following patch teaches pciconf(8) to display the table and pba >> offsets when it displays the MSI-X capability. >> >> The new output format will look like: >> >> cap 11[70] = MSI-X supports 10 messages in map 0x1c[0x0][0x2000] enabled >> OR >> cap 11[70] = MSI-X supports 10 messages in maps 0x10[0x0] and >> 0x14[0x1000] enabled >> >> Any objections to committing the patch? > > > Functionally I think this is a good addition. More information from pciconf > the better. > > Other comments below. > >> >> best >> Neel >> >> Index: usr.sbin/pciconf/cap.c >> =================================================================== >> --- cap.c (revision 246087) >> +++ cap.c (working copy) >> @@ -449,22 +449,30 @@ >> static void >> cap_msix(int fd, struct pci_conf *p, uint8_t ptr) >> { >> - uint32_t val; >> + uint32_t val, table_offset, pba_offset; > > > Variables should be in alphabetical order. > Ok. >> >> uint16_t ctrl; >> int msgnum, table_bar, pba_bar; >> >> ctrl = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_CTRL, 2); >> msgnum = (ctrl & PCIM_MSIXCTRL_TABLE_SIZE) + 1; >> + > > > Newline added intentionally? > Yes. >> >> val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_TABLE, 4); >> table_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); >> + table_offset = val & ~PCIM_MSIX_BIR_MASK; >> + >> val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_PBA, 4); >> - pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); >> + pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > > > Looks like these two lines only have whitespace difference. > Yes, there was trailing whitespace there previously. >> >> + pba_offset = val & ~PCIM_MSIX_BIR_MASK; >> + >> printf("MSI-X supports %d message%s ", msgnum, >> (msgnum == 1) ? "" : "s"); >> - if (table_bar == pba_bar) >> - printf("in map 0x%x", table_bar); >> - else >> - printf("in maps 0x%x and 0x%x", table_bar, pba_bar); >> + if (table_bar == pba_bar) { >> + printf("in map 0x%x[0x%x][0x%x]", >> + table_bar, table_offset, pba_offset); >> + } else { >> + printf("in maps 0x%x[0x%x] and 0x%x[0x%x]", >> + table_bar, table_offset, pba_bar, pba_offset); >> + } > > > Seems like at least for the case where the table and pba are behind > different BARs, this will exceed 80 characters. So maybe the maps always go > on a new line? Similar to what's done at the end of cap_express for > printing the link speed. > Ok, the new format will look like: cap 11[70] = MSI-X supports 10 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] Updated patch at the end of the email. best Neel >> >> if (ctrl & PCIM_MSIXCTRL_MSIX_ENABLE) >> printf(" enabled"); >> } Index: usr.sbin/pciconf/cap.c =================================================================== --- usr.sbin/pciconf/cap.c (revision 246087) +++ usr.sbin/pciconf/cap.c (working copy) @@ -449,24 +449,28 @@ static void cap_msix(int fd, struct pci_conf *p, uint8_t ptr) { - uint32_t val; + uint32_t pba_offset, table_offset, val; + int msgnum, pba_bar, table_bar; uint16_t ctrl; - int msgnum, table_bar, pba_bar; ctrl = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_CTRL, 2); msgnum = (ctrl & PCIM_MSIXCTRL_TABLE_SIZE) + 1; + val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_TABLE, 4); table_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); + table_offset = val & ~PCIM_MSIX_BIR_MASK; + val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_PBA, 4); - pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); - printf("MSI-X supports %d message%s ", msgnum, - (msgnum == 1) ? "" : "s"); - if (table_bar == pba_bar) - printf("in map 0x%x", table_bar); - else - printf("in maps 0x%x and 0x%x", table_bar, pba_bar); - if (ctrl & PCIM_MSIXCTRL_MSIX_ENABLE) - printf(" enabled"); + pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); + pba_offset = val & ~PCIM_MSIX_BIR_MASK; + + printf("MSI-X supports %d message%s%s\n", msgnum, + (msgnum == 1) ? "" : "s", + (ctrl & PCIM_MSIXCTRL_MSIX_ENABLE) ? ", enabled" : ""); + + printf(" "); + printf("Table in map 0x%x[0x%x], PBA in map 0x%x[0x%x]", + table_bar, table_offset, pba_bar, pba_offset); } static void From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 01:14:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51ABA5E4; Fri, 1 Feb 2013 01:14:03 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by mx1.freebsd.org (Postfix) with ESMTP id 9E248F85; Fri, 1 Feb 2013 01:14:02 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hm14so74969wib.10 for ; Thu, 31 Jan 2013 17:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=03Su6mUxv1KC2ecl4iEPBy2wXwveAN2akfk0fsfsahM=; b=r3aI9QUq8OIX2QEhimDSZxG5Rt8iB5/u3tPaUmMOS5DyupX89qd19Fbjh7qVJZohOk mQIMMKK+ZgKZ+gTGSt/GWqNBPJTgtOjB7NsdEdHiIRtwqXlpRtMC0clOcJBO1S+b9y2g N+BAhlnCyQ1zclGbdx71Q1/aQOgNIYheitEIIj8oMt3euyUJceydkQVA/JiNatDHIzKG spwMW98ZpOphF+wvP/7IqUguCU4gTK+/tevyayb/hyXYyZLmPqGjgt79ER2otmsyptEk vsLJbPxSebxmBTHBwn4wQLvJngK4rae8Vzl6v+aTlGtLZBqOT6okk4NTiOQiQXreMsIM M6hw== MIME-Version: 1.0 X-Received: by 10.180.101.99 with SMTP id ff3mr368wib.21.1359681241483; Thu, 31 Jan 2013 17:14:01 -0800 (PST) Received: by 10.194.41.10 with HTTP; Thu, 31 Jan 2013 17:14:01 -0800 (PST) In-Reply-To: <13.8E.30544.279F9015@smtp02.insight.synacor.com> References: <13.8E.30544.279F9015@smtp02.insight.synacor.com> Date: Fri, 1 Feb 2013 04:14:01 +0300 Message-ID: Subject: Re: x220 notes From: Andrey Fesenko To: Thomas Mueller Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 01:14:03 -0000 On Thu, Jan 31, 2013 at 8:56 AM, Thomas Mueller wrote: > Excerpt from Andrey Fesenko : > >> And other problems. >> 1) wi-fi >> standart rtl8192cu - not work >> change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS >> dev.acpi_ibm.0.wlan: 1 <- read only >> hardware switch work, not send mesage > > What did you try to make rtl8192cu work? Did you try NDIS? > > I have Hiro USB wireless adapter with rtl8191s chip, am still trying, on and > off, to get it to work. > > OpenBSD has urtwn driver that should work, ported to NetBSD, but why not > FreeBSD? ALso, there is a Linux driver. > > Tom NDIS failed to raise working version. Win driver terrible ~5 firmware and other. urtwn such as usb devices and no porting FreeBSD only dirty hack http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html just wanted to get wi-fi n-mode :) actively developed now like only ath. From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 01:17:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AC2939B0; Fri, 1 Feb 2013 01:17:22 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ea0-f174.google.com (mail-ea0-f174.google.com [209.85.215.174]) by mx1.freebsd.org (Postfix) with ESMTP id D5BADFBE; Fri, 1 Feb 2013 01:17:21 +0000 (UTC) Received: by mail-ea0-f174.google.com with SMTP id 1so1473183eaa.5 for ; Thu, 31 Jan 2013 17:17:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=D5Y5q5BmOfKpbwhn11jTozr6dFi3aUJFziU1LB5SHC8=; b=0vehAFpygbivQvp3RdZSAvm3klgyEHZA+QUPwY2C18l8FsN3BxuskWADx0faYxxV+o OACEbotqgPIXo69WETkDIW6scVtWLt3kqQE31nZJeuW4ERgpuvUPpoAw9fiLd9oVas9d 4NdKhi+jACKsgJIVfWryaErjF8CKWE0L+iycWRmqvOY0W9DabMIBOxPXcxtBb4ZZS0lR 0nhFuRN52sVLlvBRr/15VosPaPH+iMAZ5tcsJOyglndU/XEyGQIYInUopPflVuCQ/5u8 OGnpMozh3SUjQ/J88Big/jPTglmXAt2LwPQ24NL3AdorexlCxmbwZPH6Y/kI366SJm1K JsTw== MIME-Version: 1.0 X-Received: by 10.14.215.194 with SMTP id e42mr33501412eep.32.1359681435217; Thu, 31 Jan 2013 17:17:15 -0800 (PST) Received: by 10.14.133.204 with HTTP; Thu, 31 Jan 2013 17:17:15 -0800 (PST) Date: Thu, 31 Jan 2013 17:17:15 -0800 Message-ID: Subject: hwpmc support for haswell From: hiren panchasara To: freebsd-current Content-Type: text/plain; charset=UTF-8 Cc: Davide Italiano , Jim Harris X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 01:17:22 -0000 Hi, I've prepared a patch to add core and uncore events support for haswell processor. I do not have the hardware to test this. It applies cleanly and compiles fine though. http://www.strugglingcoder.info/patches/hwpmc_hw.txt This is initial version of patch and manpage is still missing. I will add it in a few days. Any help in testing is appreciated. Thanks, Hiren From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 01:47:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 21F16EF4; Fri, 1 Feb 2013 01:47:53 +0000 (UTC) (envelope-from davide.italiano@gmail.com) Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by mx1.freebsd.org (Postfix) with ESMTP id AC263126; Fri, 1 Feb 2013 01:47:52 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id m8so2154080vcd.23 for ; Thu, 31 Jan 2013 17:47:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ib5xKG8hMq/yUsqm121nJ/FUKkIIxTKzXfCSjrlO6FI=; b=n8hGjLEg6mSQy3fg7AxJiiy1OxqXhJljbM6d9jxsw9PQ++fwxWmsc3y9OPhMhYgZeq ecr9tnFr9fdagapqqM3K5t7hJg3QgeB+MqLm2kA9PHAIzG05bXr/QcQaI5R91Kimehc1 xjSBdmcTaomjEoXMilfwLnjTq55ippSY3N6hFqMLYhpQCO9BW2mdJgfGvw0qJOBVjQtQ W9nfDpG607a0LdnRYMdbyCGzCkuY7873aA8NPZezva3RQuRrxwa2BglWWWEk6NidEYoc ZSjnFc5J5D8OGarnDMDyVb6582qn7xXmagzIyl/zo8w20jrOyU7EduMr19TF8igzx2xL JDBA== MIME-Version: 1.0 X-Received: by 10.220.153.69 with SMTP id j5mr9839422vcw.35.1359683266003; Thu, 31 Jan 2013 17:47:46 -0800 (PST) Sender: davide.italiano@gmail.com Received: by 10.220.114.134 with HTTP; Thu, 31 Jan 2013 17:47:45 -0800 (PST) In-Reply-To: References: Date: Fri, 1 Feb 2013 02:47:45 +0100 X-Google-Sender-Auth: yYKaIznVe6KtwSqNt0rK9VnCvCI Message-ID: Subject: Re: hwpmc support for haswell From: Davide Italiano To: hiren panchasara Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , Jim Harris X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 01:47:53 -0000 On Fri, Feb 1, 2013 at 2:17 AM, hiren panchasara wrote: > Hi, > > I've prepared a patch to add core and uncore events support for > haswell processor. > I do not have the hardware to test this. It applies cleanly and > compiles fine though. > > http://www.strugglingcoder.info/patches/hwpmc_hw.txt > > This is initial version of patch and manpage is still missing. I will > add it in a few days. > > Any help in testing is appreciated. > > Thanks, > Hiren It seems Intel won't release this before June (at least to my knowledge). I would claim it'll be difficult to real test this before that date unless someone has prerelease hardware. Thanks Davide From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 02:26:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A72D764A; Fri, 1 Feb 2013 02:26:55 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by mx1.freebsd.org (Postfix) with ESMTP id C282F26C; Fri, 1 Feb 2013 02:26:54 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id e53so1765069eek.26 for ; Thu, 31 Jan 2013 18:26:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=XhFcB2AYaNtu1aBgxLPSaDSImNBJ+szgd46Q/y90jiw=; b=orE3t6M1a4Omo+9iYq98QrVrFH/OA9NhnXLbkD/os4mhp54SxzPAgTurE1XuRjhCKr UCgdu7y3mHyPFjYeEV30w9re05dT30X63PPJVA2QqWfCa0iCzY5a7WQXbG67J4sGlUZR RrlUZfCceOXOI2b6HbZuUNTikYFoq3NvOMKn3lUGw2I4CP787SnEny1L0Q/WVSgW2AKN dFKR4NMIv1Tbs3z7mQxc0cklfUNNZgIjtJ52TyKa8jPGFTszcM/qvKsGwhF/H7nNYBwj Q1yGCtnjWnBNeOw2jdD2lzpaRFkWwcHSELMYI3rYP256+FXY7VpfM5bXwEYv9kchVrdF YWiQ== MIME-Version: 1.0 X-Received: by 10.14.174.198 with SMTP id x46mr34130230eel.23.1359685608146; Thu, 31 Jan 2013 18:26:48 -0800 (PST) Received: by 10.14.133.204 with HTTP; Thu, 31 Jan 2013 18:26:48 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 18:26:48 -0800 Message-ID: Subject: Re: hwpmc support for haswell From: hiren panchasara To: Davide Italiano Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current , Jim Harris X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 02:26:55 -0000 On Thu, Jan 31, 2013 at 5:47 PM, Davide Italiano wrote: > On Fri, Feb 1, 2013 at 2:17 AM, hiren panchasara > wrote: >> Hi, >> >> I've prepared a patch to add core and uncore events support for >> haswell processor. >> I do not have the hardware to test this. It applies cleanly and >> compiles fine though. >> >> http://www.strugglingcoder.info/patches/hwpmc_hw.txt >> >> This is initial version of patch and manpage is still missing. I will >> add it in a few days. >> >> Any help in testing is appreciated. >> >> Thanks, >> Hiren > > It seems Intel won't release this before June (at least to my knowledge). > I would claim it'll be difficult to real test this before that date > unless someone has prerelease hardware. Indeed. I've posted it here just to let larger audience know and avoid possible duplicate work. We will wait till we get the hardware to test with. Thanks, Hiren > > Thanks > > Davide From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 08:35:29 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33C8B453; Fri, 1 Feb 2013 08:35:29 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id DEBA131B; Fri, 1 Feb 2013 08:35:28 +0000 (UTC) Received: from [192.168.0.2] (cpc10-cmbg15-2-0-cust123.5-4.cable.virginmedia.com [86.30.246.124]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r118ZQGL015939 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 1 Feb 2013 08:35:27 GMT (envelope-from theraven@FreeBSD.org) Subject: Re: Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: multipart/signed; boundary="Apple-Mail=_329600D2-C14D-4BCC-8783-62A1D8132E25"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: David Chisnall In-Reply-To: Date: Fri, 1 Feb 2013 08:35:22 +0000 Message-Id: <43BDAC65-626F-4B2B-AE1B-A5EA9C1AAC6A@FreeBSD.org> References: To: AN X-Mailer: Apple Mail (2.1278) Cc: Olivier Smedts , freebsd-current@FreeBSD.org, vbox@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 08:35:29 -0000 --Apple-Mail=_329600D2-C14D-4BCC-8783-62A1D8132E25 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 1 Feb 2013, at 00:37, AN wrote: > I sincerely apologize to theraven@, and all developers. My intention = was not to flame or disrespect anyone. I appreciate and am grateful to = all the developers who work on FreeBSD, thank you for your efforts. Bug reports are always helpful, even when not sent in exactly the right = direction. Thank you for taking the time to send them.=20 David --Apple-Mail=_329600D2-C14D-4BCC-8783-62A1D8132E25 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) iQIcBAEBAgAGBQJRC35KAAoJEKx65DEEsqIdbbkQAI5ZaKPslTtAO8MYtd8pY+9y wDXv+HroSAvzahTYa4QkK3W9J3LYhl4u+nKE3P0GEw40eiEOnKoL/MHfC0aQnKOX ICmqGfFQxPXcvdaR6xgiXFaj7peQYYz16wj0/i+JMvQOAbV46ZoKSGqrd6TQYBzq ulGhDIMBacBkoigDTUhwpn6HdR+K640yNYCLdddSmMY7GulKg9qiTm1MeI7KHvRf c++w5A5KqXCdWAxsd2xr5tNkxtuHcZsOcRbn80CxpKPGfD0nQc+AyFSdB9/LNMAz coqg1c0zURZTAOxUkrPsPUPxbU7sJhy8fysr45OjQmxW6qyhuIObOi6PsD0Fzc9t Sv0ERMNOSGlKnmtYf7HrMSh3CgkVulw7J9r+vokOndj/WzAvnzdxmhtD+pekaXZo GAqIZfNOOlN1kIjyfHJFGkMjttz6+NfV7h8WYjQQp1vlex1fcRJoGHPryPuwYsZd DnPonHu7VENLhL8jYdLWiYD1MV27lhozWQHu78CJIUWz927D/HmYPrJuz1l4OifP 06DH6vIC4R2CNQdtaly5mAW+qfoLL37gYAZxtEIsJZ33UI65qdaAYU4l7y7CqOtu 77rfaseLsq+rRoye3A8S1BEDG1KxXwrVeOilyuaj9an5g2AGA32o7+SMNB8ydWzI cGUkx6hmmvFHNmjIvlY1 =JUoc -----END PGP SIGNATURE----- --Apple-Mail=_329600D2-C14D-4BCC-8783-62A1D8132E25-- From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 10:30:51 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 95504E9B for ; Fri, 1 Feb 2013 10:30:51 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id C27A7A0E for ; Fri, 1 Feb 2013 10:30:50 +0000 (UTC) Received: (qmail 42006 invoked from network); 1 Feb 2013 11:50:29 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Feb 2013 11:50:29 -0000 Message-ID: <510B9950.9080308@freebsd.org> Date: Fri, 01 Feb 2013 11:30:40 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Trouble with recent auto-tuning changes References: <1359310302.93359.48.camel@revolution.hippie.lan> <1359382968.93359.66.camel@revolution.hippie.lan> <5106CF85.8060004@rice.edu> <510AA63D.2080301@freebsd.org> <1359671120.93359.343.camel@revolution.hippie.lan> In-Reply-To: <1359671120.93359.343.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@FreeBSD.org, freebsd-current@FreeBSD.org, Alan Cox X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 10:30:51 -0000 On 31.01.2013 23:25, Ian Lepore wrote: > On Thu, 2013-01-31 at 18:13 +0100, Andre Oppermann wrote: >> On 28.01.2013 20:20, Alan Cox wrote: >>> On 01/28/2013 08:22, Ian Lepore wrote: >>>> On Mon, 2013-01-28 at 00:09 -0600, Alan Cox wrote: >>>>> On Sun, Jan 27, 2013 at 12:11 PM, Ian Lepore wrote: >>>>> >>>>>> I ran into a panic while attempting to un-tar a large file on a >>>>>> DreamPlug (arm-based system) running -current. The source and dest of >>>>>> the un-tar is the root filesystem on sdcard, and I get this: >>>>>> >>>>>> panic: kmem_malloc(4096): kmem_map too small: 12582912 total allocated >>>>>> >>>>>> Just before the panic I see the tar process get hung in a "nokva" wait. >>>>>> 12582912 is the value of VM_KMEM_SIZE from arm/include/vmparam.h. >>>>>> >>>>>> In r245575 the init order for mbuf limits was changed from >>>>>> SI_SUB_TUNABLES to SI_SUB_KMEM so that mbuf limits could be based on the >>>>>> results of sizing kernel memory. Unfortunately, the process of sizing >>>>>> kernel memory relies on the mbuf limits; in kmeminit(): >>>>>> >>>>>> vm_kmem_size = VM_KMEM_SIZE + nmbclusters * PAGE_SIZE; >>>>>> >>>>>> Since r245575, nmbclusters is zero when this line of code runs. If I >>>>>> manually plugin "32768" (the number tunable_mbinit() comes up with for >>>>>> this platform) in that line, the panic stops happening. >>>>>> >>>>>> So we've got two problems here... one is the circular dependency in >>>>>> calculating the mbuf limits. The other is the fact that some >>>>>> non-trivial amount of kernel memory we're allowing for mbufs is actually >>>>>> being used for other things. That is, if my system was actually using >>>>>> all the mbufs that tunable_mbinit() allowed for, then this panic while >>>>>> untarring a huge file would still have happened. >>>>>> >>>>>> >>>>> All of this is factually correct. However, it's a red herring. The real >>>>> problem is that arm, unlike every other architecture in the tree, does not >>>>> enable auto-sizing of the kmem map based on the physical memory size. >>>>> Specifically, you'll find VM_KMEM_SIZE_SCALE defined in >>>>> "arch"/include/vmparam.h on every other architecture, just not on arm. >>>>> This auto-sizing overrides the value of VM_KMEM_SIZE. >>>>> >>>> Aha. I'll investigate what other architectures do with that and try to >>>> get the same thing going for arm. >>>> >>> >>> i386 or (32-bit) MIPS would be the most similar. Also, I would >>> encourage you to look for other definitions that those architectures >>> have that arm doesn't. As physical memory sizes continue to grow on >>> arm-based systems, they may require other changes in vmparam.h and the >>> machine-dependent param.h that were made on those other architectures >>> year ago. >> >> Ian, >> >> The patch below should do the trick. Can you please test? > > Yep, that fixed the problem with untarring the large file. Here are > some before/after numbers from sysctl, converted from bytes to KBytes > for readability: > > vm.kmem_size_scale: 0 2 > vm.kmem_map_free: 5740 246440 > vm.kmem_map_size: 6548 7176 > vm.kmem_size: 12288 253616 > > real memory = 536870912 (512 MB) > avail memory = 516718592 (492 MB) Thank you for testing. Committed as r246204. If any other problems come up please report. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 08:18:27 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1F90912A; Fri, 1 Feb 2013 08:18:27 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by mx1.freebsd.org (Postfix) with ESMTP id E94FE274; Fri, 1 Feb 2013 08:18:26 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id hz11so2167162pad.31 for ; Fri, 01 Feb 2013 00:18:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=kMUzonXOEcIYvt2otpLAQHwaGOuIHImzWewvssRv1Wc=; b=rSXHfktbv6f9/1YHlmXWk0odSEPhPlTOtHBKFetU8uGeUqSpxRYkcvNUo4JLYGFuNm oX92IJjZi43poPpOcgqBRk0KunaXL+ieJBJzkJe9wG+DFCps4GNOnJsYAC9hgQjRq8fv uklIf3l1utZ/NVnxGFyez9yN71PD6BywrcYZfHCB/6I0jXlPCFtAW2Nb1CsLVoHw0ZoG 4/Hl1tlm/zImz0s+XTty07JnxAI5oDc0GO76oAiHBbsakgz6tXmNEZykbyHfUSayJTkc m2UU70b1W3XycR1Y/FnOyBIUxCJAk2mkbmn41qKWn70urXgs2Ftp3aEfH//B35zID3Nj WHrQ== X-Received: by 10.68.138.229 with SMTP id qt5mr29432382pbb.122.1359706700747; Fri, 01 Feb 2013 00:18:20 -0800 (PST) Received: from [192.168.20.12] (c-24-19-191-56.hsd1.wa.comcast.net. [24.19.191.56]) by mx.google.com with ESMTPS id ba3sm7736762pbd.29.2013.02.01.00.18.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Feb 2013 00:18:19 -0800 (PST) References: <510AA5A8.1090402@FreeBSD.org> Mime-Version: 1.0 (1.0) In-Reply-To: <510AA5A8.1090402@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: iPhone Mail (10A523) From: Garrett Cooper Subject: Re: Panic when closing lid on CURRENT with netbook Date: Fri, 1 Feb 2013 00:18:17 -0800 To: Jung-uk Kim X-Mailman-Approved-At: Fri, 01 Feb 2013 12:36:03 +0000 Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 08:18:27 -0000 On Jan 31, 2013, at 9:11 AM, Jung-uk Kim wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2013-01-31 11:57:54 -0500, Garrett Cooper wrote: >> I updated my Asus EEEPC netbook from sources earlier on this month >> to yesterday's sources, and whenever I shut the lid it now panics >> with use after free (0xcacacaca) in AcpiEvNotifyDispatch. I >> understand that ACPICA was updated recently, so my guess is that >> this is the root cause (was the fix for this r246042?). I was >> wondering if this is a known issue. Have coredumps if needed. > > This problem should be fixed in r246042. Are you saying you're still > experiencing the problem after the revision? Did it happen before > r245582? That commit fixed it -- thanks! -Garrett From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 12:52:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 98E88AFC for ; Fri, 1 Feb 2013 12:52:21 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp.insight.synacor.com [208.47.185.22]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB5A2CB for ; Fri, 1 Feb 2013 12:52:20 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.0 cv=Br4fMPr5 c=1 sm=0 a=Dm9TOXL4taQ+Gy1KovpL+A==:17 a=DvSzqBOGy98A:10 a=pedpZTtsAAAA:8 a=pGLkceISAAAA:8 a=6I5d2MoRAAAA:8 a=WFCrcO4VFK_H2dbcgeMA:9 a=bB32x0tA_RAA:10 a=MSl-tDqOz04A:10 a=Dm9TOXL4taQ+Gy1KovpL+A==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp02.insight.synacor.com header.from=mueller6724@bellsouth.net; sender-id=neutral Authentication-Results: smtp02.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Received-SPF: softfail (smtp02.insight.synacor.com: transitional domain insightbb.com does not designate 74.130.198.7 as permitted sender) Received: from [74.130.198.7] ([74.130.198.7:55240] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id B9/4D-30544-E7ABB015; Fri, 01 Feb 2013 07:52:14 -0500 Date: Fri, 01 Feb 2013 07:52:14 -0500 Message-ID: From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: x220 notes Cc: Andrey Fesenko , freebsd-mobile@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 12:52:21 -0000 >From Andrey Fesenko : > NDIS failed to raise working version. Win driver terrible ~5 firmware and other. > urtwn such as usb devices and no porting FreeBSD only dirty hack > http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html > just wanted to get wi-fi n-mode :) actively developed now like only ath. > I'll have to try again; NDIS failed the first time, but that might have been > due to something missing in kernel config regarding NDIS and ndisapi. > I can try with both WinXP and Win7 versions. I also want to try urtwn in NetBSD (I build the kernel and userland) and OpenBSD live USB. OpenBSD apparently has no support for either USB 3.0 or GPT, can't access my hard drive at all. NetBSD has no USB 3.0 support but supports GPT with partitions in a strange way, /dev/dk0, /dev/dk1, /dev/dk2, and so on, with this sequence spanning all GPT devices including USB hard drives and USB sticks. I install NetBSD to a USB stick but have the source, and pkgsrc too, on an older FreeBSD UFS2/ffsv2 hard-drive partition where all the heavy work is done. Aside from the possibility of porting urtwn from OpenBSD or NetBSD, maybe it could be ported from Linux? Tom From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 13:25:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A80306C4 for ; Fri, 1 Feb 2013 13:25:44 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 806E4706 for ; Fri, 1 Feb 2013 13:25:42 +0000 (UTC) Received: (qmail 42730 invoked from network); 1 Feb 2013 14:45:21 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Feb 2013 14:45:21 -0000 Message-ID: <510BC24D.2090406@freebsd.org> Date: Fri, 01 Feb 2013 14:25:33 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Cleanup and untangling of kernel VM initialization Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, kib@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 13:25:44 -0000 As an outcome of the recent problems with auto-sizing and auto-tuning of the various kernel subsystems and related memory structures I've taken a closer look at the whole KVM inner working and initialization process. I've found the VM and KVM initialization to be somewhat obscure and stuck half-way between the old 4.4BSD way and our modern SYSINIT concept. While trying to understand all the steps I started to move things around, into their own units and converted them to use SYSINITs. The result is a patch that cleans up the majority of initialization process, removes bitrot and moves it into the modern world order: http://people.freebsd.org/~andre/kernel_init_mem-20130201.diff The changes in particular are: Move large parts of vm/vm_init.c to SYSINIT()s and de-magic old-style kernel vm initialization. Move vm_ksubmap_init(), bufinit() and vm_pager_bufferinit() from machdep.c to SYSINIT's. It was duplicated among all architectures which means that is wasn't architecture specific. Centralize definition of virtual_avail and virtual_end from the architectures pmap.h to vm_extern.h. Move various initializations from kern/subr_param.c to where it is actually used and SYSINIT() in particular vm_pager (pager_map / nswbuf), vm_kern (kernel_map), swap_pager (maxswzone), sys_pipe (pipe_map / maxpipekva), vfs_bio (buffer_map / nbuf), kern_exec (exec_map / exec_map_entries), kern_malloc (kmem_map), kern_timeout (callwheel, ncallout). Move subsystem initializations from init_main.c to SYSINIT()s. Add sysctl's to give detailed information on all kernel vm_maps and sub maps Remove unused struct kva_md_info. Rebase auto-sizing of limits on the available KVM/kmem_map instead of physical memory. Depending on the kernel and architecture configuration these two can be very different. Comments and reviews appreciated. For committing it'll be broken into meaningful and functional pieces with an appropriate commit message each. I've tested on amd64. Feedback from other architectures welcome. Especially for powerpc where I had to modify the minidump routine slighly to avoid dumping of buffer_map memory. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 14:54:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1AA8E2C6; Fri, 1 Feb 2013 14:54:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E74FCAF2; Fri, 1 Feb 2013 14:54:23 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 04EDBB977; Fri, 1 Feb 2013 09:54:23 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: PATCH: display MSI-X table and pba offsets from "pciconf -c" Date: Fri, 1 Feb 2013 09:30:41 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201302010930.41743.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 01 Feb 2013 09:54:23 -0500 (EST) Cc: Jim Harris , current@freebsd.org, Neel Natu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 14:54:24 -0000 On Thursday, January 31, 2013 7:37:48 pm Neel Natu wrote: > Hi Jim, > > On Thu, Jan 31, 2013 at 3:13 PM, Jim Harris wrote: > > > > > > On Thu, Jan 31, 2013 at 3:52 PM, Neel Natu wrote: > >> > >> Hi, > >> > >> The following patch teaches pciconf(8) to display the table and pba > >> offsets when it displays the MSI-X capability. > >> > >> The new output format will look like: > >> > >> cap 11[70] = MSI-X supports 10 messages in map 0x1c[0x0][0x2000] enabled > >> OR > >> cap 11[70] = MSI-X supports 10 messages in maps 0x10[0x0] and > >> 0x14[0x1000] enabled > >> > >> Any objections to committing the patch? > > > > > > Functionally I think this is a good addition. More information from pciconf > > the better. > > > > Other comments below. > > > >> > >> best > >> Neel > >> > >> Index: usr.sbin/pciconf/cap.c > >> =================================================================== > >> --- cap.c (revision 246087) > >> +++ cap.c (working copy) > >> @@ -449,22 +449,30 @@ > >> static void > >> cap_msix(int fd, struct pci_conf *p, uint8_t ptr) > >> { > >> - uint32_t val; > >> + uint32_t val, table_offset, pba_offset; > > > > > > Variables should be in alphabetical order. > > > > Ok. > > >> > >> uint16_t ctrl; > >> int msgnum, table_bar, pba_bar; > >> > >> ctrl = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_CTRL, 2); > >> msgnum = (ctrl & PCIM_MSIXCTRL_TABLE_SIZE) + 1; > >> + > > > > > > Newline added intentionally? > > > > Yes. > > >> > >> val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_TABLE, 4); > >> table_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > >> + table_offset = val & ~PCIM_MSIX_BIR_MASK; > >> + > >> val = read_config(fd, &p->pc_sel, ptr + PCIR_MSIX_PBA, 4); > >> - pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > >> + pba_bar = PCIR_BAR(val & PCIM_MSIX_BIR_MASK); > > > > > > Looks like these two lines only have whitespace difference. > > > > Yes, there was trailing whitespace there previously. > > >> > >> + pba_offset = val & ~PCIM_MSIX_BIR_MASK; > >> + > >> printf("MSI-X supports %d message%s ", msgnum, > >> (msgnum == 1) ? "" : "s"); > >> - if (table_bar == pba_bar) > >> - printf("in map 0x%x", table_bar); > >> - else > >> - printf("in maps 0x%x and 0x%x", table_bar, pba_bar); > >> + if (table_bar == pba_bar) { > >> + printf("in map 0x%x[0x%x][0x%x]", > >> + table_bar, table_offset, pba_offset); > >> + } else { > >> + printf("in maps 0x%x[0x%x] and 0x%x[0x%x]", > >> + table_bar, table_offset, pba_bar, pba_offset); > >> + } > > > > > > Seems like at least for the case where the table and pba are behind > > different BARs, this will exceed 80 characters. So maybe the maps always go > > on a new line? Similar to what's done at the end of cap_express for > > printing the link speed. > > > > Ok, the new format will look like: > > cap 11[70] = MSI-X supports 10 messages, enabled > Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] > > Updated patch at the end of the email. Looks good to me. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 16:38:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BD66419C; Fri, 1 Feb 2013 16:38:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id 3687FD2; Fri, 1 Feb 2013 16:38:56 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so792067wib.9 for ; Fri, 01 Feb 2013 08:38:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Cpqfm3OM9IgGRzC3O84G+tjOrVUAU7ATqh+L6DVQASc=; b=rVduHwY8cr2+e/Gpq6CaGzaPz0afEb1BTpkUPVmZsXvVriv35WPJxKBPBmTbeGk+bp U7J+m1GNxfojVuKAm2YYtTk8GInxiYtOnUWJQA6sYDOBlaWYTr+B9cKoj/fVL6D09vfs qsKrZhPyhhHs3ExN6Zc9lD02SyrRlPeJn37uurxoCFbWbAu0l0b0XSyBGoNSgFXR8WFS 66cBeE3UyqJjeNJgHo7eWzAexPzOZFnyzoGxs9VRpuWPPncXHMkAaYyc1XaA3lW83QnZ XJ2WdeSYSdJ5L5sDTd7cZs8m4ZjP2Bbgk6NVa6qYFEAaiRMhJQB8aOnp/JGGGYnDJ9f3 LyPQ== MIME-Version: 1.0 X-Received: by 10.180.82.65 with SMTP id g1mr3964245wiy.22.1359736729785; Fri, 01 Feb 2013 08:38:49 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.98.5 with HTTP; Fri, 1 Feb 2013 08:38:49 -0800 (PST) In-Reply-To: References: Date: Fri, 1 Feb 2013 08:38:49 -0800 X-Google-Sender-Auth: 4iAg9_eczli_mpnjShs8gu3HVRI Message-ID: Subject: Re: x220 notes From: Adrian Chadd To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 Cc: Andrey Fesenko , freebsd-current@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 16:38:57 -0000 Someone needs to pick that porting effort up, polish/finish it up, and get it into FreeBSD. I'm happy to commit whatever people agree to tidy up and maintain. Thanks, Adrian On 1 February 2013 04:52, Thomas Mueller wrote: > From Andrey Fesenko : > >> NDIS failed to raise working version. Win driver terrible ~5 firmware and other. > >> urtwn such as usb devices and no porting FreeBSD only dirty hack >> http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html > >> just wanted to get wi-fi n-mode :) actively developed now like only ath. > >> I'll have to try again; NDIS failed the first time, but that might have been >> due to something missing in kernel config regarding NDIS and ndisapi. > >> I can try with both WinXP and Win7 versions. > > I also want to try urtwn in NetBSD (I build the kernel and userland) and > OpenBSD live USB. OpenBSD apparently has no support for either USB 3.0 or > GPT, can't access my hard drive at all. NetBSD has no USB 3.0 support but > supports GPT with partitions in a strange way, /dev/dk0, /dev/dk1, /dev/dk2, > and so on, with this sequence spanning all GPT devices including USB hard > drives and USB sticks. I install NetBSD to a USB stick but have the source, > and pkgsrc too, on an older FreeBSD UFS2/ffsv2 hard-drive partition where all > the heavy work is done. > > Aside from the possibility of porting urtwn from OpenBSD or NetBSD, maybe it > could be ported from Linux? > > Tom > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 17:07:44 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C1A32EDE for ; Fri, 1 Feb 2013 17:07:44 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9AC22223 for ; Fri, 1 Feb 2013 17:07:44 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r11H7bUs076671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 1 Feb 2013 09:07:37 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r11H7bd1076670 for current@FreeBSD.org; Fri, 1 Feb 2013 09:07:37 -0800 (PST) (envelope-from jmg) Date: Fri, 1 Feb 2013 09:07:37 -0800 From: John-Mark Gurney To: current@FreeBSD.org Subject: -current broken on pre-PPro machines (w/ work around) Message-ID: <20130201170737.GP1410@funkthat.com> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 01 Feb 2013 09:07:37 -0800 (PST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 17:07:44 -0000 Just a warning to others so they don't hit the same issue I did, and spend time trying to figure it out. clang (in -current) does not compile code properly for pre-PPro machines... Compiled output includes the cmov instructions... This affects both loader, and kernel, so if you update loader, you'll see a few spins, and the machine will probably reset... if you use an older loader, your kernel will fault a/ an illegal instruction... If you want to run -current on one of these machines, make sure you set WITHOUT_CLANG_IS_CC= for *BOTH* buildworld and installworld so that you use gcc instead of clang... A bug has been filed: http://llvm.org/bugs/show_bug.cgi?id=15115 -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Fri Feb 1 17:17:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1099D12F; Fri, 1 Feb 2013 17:17:06 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh2.mail.rice.edu (mh2.mail.rice.edu [128.42.201.21]) by mx1.freebsd.org (Postfix) with ESMTP id B883326D; Fri, 1 Feb 2013 17:17:05 +0000 (UTC) Received: from mh2.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh2.mail.rice.edu (Postfix) with ESMTP id 84E6650011D; Fri, 1 Feb 2013 11:09:54 -0600 (CST) Received: from mh2.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh2.mail.rice.edu (Postfix) with ESMTP id 8203B500116; Fri, 1 Feb 2013 11:09:54 -0600 (CST) X-Virus-Scanned: by amavis-2.7.0 at mh2.mail.rice.edu, auth channel Received: from mh2.mail.rice.edu ([127.0.0.1]) by mh2.mail.rice.edu (mh2.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id DI8VZTOp-Y8K; Fri, 1 Feb 2013 11:09:54 -0600 (CST) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh2.mail.rice.edu (Postfix) with ESMTPSA id EC584500108; Fri, 1 Feb 2013 11:09:53 -0600 (CST) Message-ID: <510BF6E0.8070007@rice.edu> Date: Fri, 01 Feb 2013 11:09:52 -0600 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130127 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andre Oppermann Subject: Re: Cleanup and untangling of kernel VM initialization References: <510BC24D.2090406@freebsd.org> In-Reply-To: <510BC24D.2090406@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, freebsd-current@freebsd.org, kib@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 17:17:06 -0000 On 02/01/2013 07:25, Andre Oppermann wrote: > As an outcome of the recent problems with auto-sizing and auto-tuning of > the various kernel subsystems and related memory structures I've taken a > closer look at the whole KVM inner working and initialization process. > > I've found the VM and KVM initialization to be somewhat obscure and stuck > half-way between the old 4.4BSD way and our modern SYSINIT concept. > > While trying to understand all the steps I started to move things around, > into their own units and converted them to use SYSINITs. The result is > a patch that cleans up the majority of initialization process, removes > bitrot and moves it into the modern world order: > > http://people.freebsd.org/~andre/kernel_init_mem-20130201.diff > > The changes in particular are: > > Move large parts of vm/vm_init.c to SYSINIT()s and de-magic old-style > kernel vm initialization. > > Move vm_ksubmap_init(), bufinit() and vm_pager_bufferinit() from > machdep.c > to SYSINIT's. It was duplicated among all architectures which means > that > is wasn't architecture specific. > > Centralize definition of virtual_avail and virtual_end from the > architectures > pmap.h to vm_extern.h. > I think vm/pmap.h would be more appropriate place than vm/vm_extern.h. These variables have only been used for communication between the pmap and the machine-independent layer at initialization time. > Move various initializations from kern/subr_param.c to where it is > actually > used and SYSINIT() in particular vm_pager (pager_map / nswbuf), vm_kern > (kernel_map), swap_pager (maxswzone), sys_pipe (pipe_map / maxpipekva), > vfs_bio (buffer_map / nbuf), kern_exec (exec_map / exec_map_entries), > kern_malloc (kmem_map), kern_timeout (callwheel, ncallout). > > Move subsystem initializations from init_main.c to SYSINIT()s. > > Add sysctl's to give detailed information on all kernel vm_maps and > sub maps > > Remove unused struct kva_md_info. > It is used by assertions that block people from writing code that uses the wrong pmap functions for mapping pages into the buffer and pager maps. > Rebase auto-sizing of limits on the available KVM/kmem_map instead of > physical > memory. Depending on the kernel and architecture configuration these > two can > be very different. > > Comments and reviews appreciated. > I would really like to see the issues with the current auto-sizing code addressed before any of the stylistic changes or en-masse conversions to SYSINIT()s are considered. In particular, can we please start with the patch that moves the pipe_map initialization? After that, I think that we should revisit tunable_mbinit() and "maxmbufmem". > For committing it'll be broken into meaningful and functional pieces > with an > appropriate commit message each. > > I've tested on amd64. Feedback from other architectures welcome. > Especially > for powerpc where I had to modify the minidump routine slighly to > avoid dumping > of buffer_map memory. > From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 01:49:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DCB98ECF; Sat, 2 Feb 2013 01:49:07 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-da0-f45.google.com (mail-da0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 82DAB9A9; Sat, 2 Feb 2013 01:49:07 +0000 (UTC) Received: by mail-da0-f45.google.com with SMTP id w4so1929755dam.4 for ; Fri, 01 Feb 2013 17:49:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=/0WjVNGSuNMtsO0e8IrFgp9SfCGLB41TEOL353wXk5Q=; b=FIG/Wh5fO9tWQQUDVfutgvZ0s2UTkBfQOiFbl418OyKrPXtxgMrsILhjDwFXsJeyUD 30GVLoIFcyNWltnGz5KmcWXCaHxCX3eRN0+gkucmvpuljKZlegS1g41azyR/yQwOawXr 5vD3z7te4JS5oxA57h9tJ2Ik5Uk3eiY4KPDh1DrnmJ+8EkXOZ412x2+9hRoYh92VbSBb xotenDxYx4WhX1XKi+Fjxb34MPl2dM4g+p1K7oxknmGSe88IiujJaNJkC8m1bvYrwe79 i8zZL6T1p+ajXAa0PVdGsBoLBCitF1rXT0kLp5V2DUQ7z2YVtw51k22VvcGPkIAdAYBh ULxg== MIME-Version: 1.0 X-Received: by 10.68.233.197 with SMTP id ty5mr38202147pbc.9.1359769741757; Fri, 01 Feb 2013 17:49:01 -0800 (PST) Received: by 10.67.2.65 with HTTP; Fri, 1 Feb 2013 17:49:01 -0800 (PST) In-Reply-To: References: <4E836C06.9070405@gmail.com> <4E8374A7.90105@gmail.com> <4E9BDF13.4040006@gmail.com> <4F38211D.4070305@mehnert.org> <4F40A2D4.6000000@gmail.com> <4F57A8FC.8090106@gmail.com> <20120308092234.M18590@martymac.org> <4F5AC96A.3050600@gmail.com> <4F5FE9C1.7010901@gmail.com> <4F6020C0.60405@gmail.com> <4F6126A2.7050301@mehnert.org> Date: Fri, 1 Feb 2013 17:49:01 -0800 Message-ID: Subject: Re: x220 notes From: Kevin Oberman To: Andrey Fesenko Content-Type: text/plain; charset=UTF-8 Cc: matt , freebsd-mobile@freebsd.org, Hannes Mehnert , freebsd-current@freebsd.org, Ganael LAPLANCHE , Vrachnis Ilias-Dimitrios X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 01:49:07 -0000 On Tue, Jan 29, 2013 at 1:49 PM, Andrey Fesenko wrote: > On Wed, Mar 14, 2012 at 11:15 PM, Hannes Mehnert wrote: >> Ciao, >> >> On 03/14/2012 00:38, matt wrote: >>> I have brightness control through raw acpi..."\_BCL" and friends seem to >>> do nothing. >>> >>> Most of the video methods differentiate between \VIGD (which seems to be >>> a check for integrated graphics vs optimus, but that's still a guess) >>> If \VIGD is true, brightness commands are sent to the EC, where they >>> don't seem to do much yet. This is probably where we could enable >>> something via EC/ibm-acpi? >>> If \VIGD is false, brightness commands are handled in ACPI, although >>> coarsely, via \VBRC. >>> >>> \VBRC seems to allow control over the backlight, at least, so those of >>> you with sore eyes or the 3-cell battery may have some success using the >>> acpi_call port (Danger!) >>> kldload acpi_call >>> acpi_call -p '\VBRC' -i n (where n is 0-10) >> >> Great news! Works for me. n is actually 0-16 (plus any other value which >> turns the backlight off (-1 or 17 eg). >> >> >> Thanks, >> >> Hannes > > > Thanks, acpi_call -p '\VBRC' -i n [0-15] work fine, if set 17 black screen :) > > And other problems. > 1) wi-fi > standart rtl8192cu - not work > change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS > dev.acpi_ibm.0.wlan: 1 <- read only > hardware switch work, not send mesage > > 2) sound > # cat /dev/sndstat > FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) > Installed devices: > pcm0: (play/rec) > pcm1: (play/rec) default > pcm2: (play) > pcm3: (play) > pcm4: (play) > sound headphones only, if set sysctl hw.snd.default_unit=0 and restart > application, on's speakers (if remove headphones). > Automatic switching possible? Yes. Put this in /boot/loader.conf: # Load the sound driver snd_hda_load="YES" # and setup headphones # Out : speaker + headphones hint.hdac.0.cad0.nid25.config="as=1 seq=15" # In : mic + external mic hint.hdac.0.cad0.nid35.config="as=2" hint.hdac.0.cad0.nid27.config="as=2 seq=15" # Drivers for memory card reader mmc_load="YES" mmcsd_load="YES" sdhci_load="YES" # Load module to read the CPU temp coretemp_load="YES" This also enables the SD card reader and reading the CPU temp. > 2.2) sound control > in mplayer automatic fine work multimedia key > multimedia key and system mixer, and sysctl not work Don't know what desktop you use, but both gnome and KDE allow you to define the sound buttons. In gnome it is under Preferences/Keyboard Shortcuts Set "Vol Up" to "XF86AudioRaiseVolume" and "Vol Down" to "XF86AudioLowerVolume" > > 3) ACPI work poorly > 19 1 0xffffffff81f01000 37c7 acpi_video.ko > 20 1 0xffffffff81f05000 330f acpi_ibm.ko > 21 1 0xffffffff81f09000 1fc acpi_call.ko > # sysctl -a | grep ibm > acpi_ibm0: on acpi0 > acpi_ibm0: detached > acpi_ibm0: on acpi0 > dev.acpi_ibm.0.%desc: IBM ThinkPad ACPI Extras > dev.acpi_ibm.0.%driver: acpi_ibm > dev.acpi_ibm.0.%location: handle=\_SB_.PCI0.LPC_.EC__.HKEY > dev.acpi_ibm.0.%pnpinfo: _HID=LEN0068 _UID=0 > dev.acpi_ibm.0.%parent: acpi0 > dev.acpi_ibm.0.initialmask: 2060 > dev.acpi_ibm.0.availmask: 134217727 > dev.acpi_ibm.0.events: 1 > dev.acpi_ibm.0.eventmask: 134217727 > dev.acpi_ibm.0.hotkey: 3353 > dev.acpi_ibm.0.lcd_brightness: 0 <- not work > dev.acpi_ibm.0.volume: 0 <- not work > dev.acpi_ibm.0.mute: 0 <- not work > dev.acpi_ibm.0.thinklight: 0 <- work fine :) > dev.acpi_ibm.0.bluetooth: 0 <- work LED (bt not use, not test) > dev.acpi_ibm.0.wlan: 1 <- read only > dev.acpi_ibm.0.fan_speed: 3880 <- not work or read only > dev.acpi_ibm.0.fan_level: 0 > dev.acpi_ibm.0.fan: 1 The fan speed is read-only. > LED HDD may be work blink infrequently SSD :) > > 3) video work acceptable > WITH_NEW_XORG=true > WITH_KMS=true > > from terminal adjustable brightness > acpi_call -p '\VBRC' -i n [0-15] > I would like to consolidate these actions on the standard key # cat > /var/run/devd.pipe > !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x10 ( Fn+Home) > !system=ACPI subsystem=IBM type=\_SB_.PCI0.LPC_.EC__.HKEY notify=0x11 (Fn+End) Sounds good, but you need to know the current brightness to incrementally adjust it, I have not figured out a way to get it. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 10:55:35 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E816F1BF; Sat, 2 Feb 2013 10:55:35 +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 C2586A25; Sat, 2 Feb 2013 10:55:34 +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 MAA28996; Sat, 02 Feb 2013 12:55:27 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U1ako-00046L-QH; Sat, 02 Feb 2013 12:55:26 +0200 Message-ID: <510CF09C.7020109@FreeBSD.org> Date: Sat, 02 Feb 2013 12:55:24 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: John Baldwin Subject: Re: some questions on kern_linker and pre-loaded modules References: <5103C361.6060605@FreeBSD.org> <201301281040.38727.jhb@freebsd.org> In-Reply-To: <201301281040.38727.jhb@freebsd.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 10:55:36 -0000 on 28/01/2013 17:40 John Baldwin said the following: > Yes, I think it is too hard at present to safely allow a linker file to > override the same module in a kernel, so the duplicate linker file should > just be rejected entirely. I'm not sure if your change is completely > correct for that. Incidentally that particular patch was broken. Here is a working patch: http://people.freebsd.org/~avg/linker_file_register_modules-linker_kernel_file.diff But I really need to get a better understanding of the bigger picture and then discuss what has to be done in that scope. I plan to write a larger response to your complete followup. Thank you. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 11:50:44 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BD501402; Sat, 2 Feb 2013 11:50:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A771ECC0; Sat, 2 Feb 2013 11:50:43 +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 NAA29528; Sat, 02 Feb 2013 13:50:42 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1U1bcH-0004Bz-PW; Sat, 02 Feb 2013 13:50:41 +0200 Message-ID: <510CFD90.9000304@FreeBSD.org> Date: Sat, 02 Feb 2013 13:50:40 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130121 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: scheduler->swapper, SI_SUB_RUN_SCHEDULER->SI_SUB_LAST X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 11:50:44 -0000 I would like to propose the following mostly cosmetic change: http://people.freebsd.org/~avg/scheduler-swapper.diff This is something that bit me early in my FreeBSD days, so I am kind of obsessed with it. The current naming is confusing/misleading indeed. And magic properties of SI_SUB_RUN_SCHEDULER:SI_ORDER_LAST is a "hidden gem". -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 14:50:18 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8D7A2A97; Sat, 2 Feb 2013 14:50:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id DB51A6A5; Sat, 2 Feb 2013 14:50:17 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r12EoDIg077606; Sat, 2 Feb 2013 16:50:13 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r12EoDIg077606 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r12EoDq1077604; Sat, 2 Feb 2013 16:50:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 2 Feb 2013 16:50:13 +0200 From: Konstantin Belousov To: Andriy Gapon Subject: Re: scheduler->swapper, SI_SUB_RUN_SCHEDULER->SI_SUB_LAST Message-ID: <20130202145013.GV2522@kib.kiev.ua> References: <510CFD90.9000304@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0ujaWV404FI0kHa9" Content-Disposition: inline In-Reply-To: <510CFD90.9000304@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 14:50:18 -0000 --0ujaWV404FI0kHa9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 02, 2013 at 01:50:40PM +0200, Andriy Gapon wrote: >=20 > I would like to propose the following mostly cosmetic change: > http://people.freebsd.org/~avg/scheduler-swapper.diff >=20 > This is something that bit me early in my FreeBSD days, so I am kind of o= bsessed > with it. > The current naming is confusing/misleading indeed. > And magic properties of SI_SUB_RUN_SCHEDULER:SI_ORDER_LAST is a "hidden g= em". You may remove the Giant unlock from the scheduler()/swapper() as well then, doing it before the swapper() call in the mi_startup(). Note that the wait chain for the idle swapper is still called "sched". --0ujaWV404FI0kHa9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRDSelAAoJEJDCuSvBvK1B6usP/i4nVfbHVB++Sk8BUy5+zrIM B+dAEnb64hEnELVjcQfAYO7+UDkgMMo63eVmgq8kYtiVBJ7bF6+QxbjNObubXM7B 0MbLpcHgnwtwuqMF4swVofJzR7pqbqo7lq3E5R9Bd57kZJfhzNS7CPhycX4HQiV0 WZZB1SLz+eoc+jfyFgOSfR+Eq9hrrPS2lH2k76FwScU1x0IpiTnkaYkfcs0QYqgW z0AqRmQjAEl9V8HyM4b2qTa+6k0K+HiXaQMNzpn+GZhlpjmmVe7pQy2fy/5NBAzU rK0dxu2J0FH1PEJgLwJIIlMYl0MI3KjeX1O4QmCkQLros0o6+ZwQ7t0irRsydGsX dJI7T57i3+BZvo61Uq3snFRbkiIBKhUtnwTBWF9z+qSJW10Ma+UcASltN0/6YFhP trdcVqbN4jsOLpYTAGBLgxzf4LjqzVHeNPX3wmL42LfFXmwPm7mYbbKsucbfxFCQ WJvbJCvo/PMzwHCK+aC0UueZ1yI8nx95oGp+HWQGc6AgD9PmmzWMZng9gAdUK5kO +v1S4t7aQymjASwUtNpHZnjC+keQy/Zk/L7GT0mveD0hm7+jtlAKqzBkqTS/7dfJ yba9uoxT3gZpYkEA7GmSerERJfDvXAF1azYUdzhk9Kcu8lX8OTvsov0xjUrXIL5J 9oH+HRNGtfKWsdN2QH1y =qdWH -----END PGP SIGNATURE----- --0ujaWV404FI0kHa9-- From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 16:33:27 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1C9F34C5; Sat, 2 Feb 2013 16:33:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5F6A29; Sat, 2 Feb 2013 16:33:26 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r12GXMsX088485; Sat, 2 Feb 2013 18:33:22 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.7.4 kib.kiev.ua r12GXMsX088485 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r12GXMVP088484; Sat, 2 Feb 2013 18:33:22 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 2 Feb 2013 18:33:22 +0200 From: Konstantin Belousov To: current@freebsd.org, arch@freebsd.org Subject: Physbio changes final call for tests and reviews Message-ID: <20130202163322.GA2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xIk0xHvQc0Ku+QuL" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: powerpc@freebsd.org, mips@freebsd.org, ia64@freebsd.org, sparc64@freebsd.org, arm@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 16:33:27 -0000 --xIk0xHvQc0Ku+QuL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I finished the last (insignificant) missed bits in the Jeff' physbio work. Now I am asking for the last round of testing and review, esp. for the !x86 architectures. Another testing focus are the SCSI HBAs and RAID controllers which drivers are changed by the patchset. Please do test this before the patchset is committed into HEAD ! The plan is to commit the patch somewhere in two weeks from this moment. The patch is required for the finalizing of the unmapped I/O work for UFS I did in parallel, which I hope to finish shortly after the commit. Patch is available at http://people.freebsd.org/~kib/misc/physbio.5.diff Thank you in advance. --xIk0xHvQc0Ku+QuL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRDT/SAAoJEJDCuSvBvK1BmGoP/314FHxSTtWQ22v30ZkLUUHw p/5C3qRV+xjpEWfE80WQtMobuh9XMxaHGLJxz9UvVJQIqx5WUe0bINN4PfwzVbSm r+Zw+LtyVrBdVgMzuq48h4IEFHkcxN1O6VznBKPBBDYcIZTTZ7y/bdljiB7q0HRP G7SHsOfpIN8CSZNXPodVMIeagDPcbVDb3yVtW5zIsHeMyxCtjWIRCczVCwr0vpXQ kfOGqAquLrXlv95e04LB08REJnrymkoPpMmA6mHdxY3a8ggMXcd4wFVP8YjX23iR rEY8idLlW4rLfMwZuCcyR5w4UIcsx2NOhcyouFVRDYs5HxLDoDBUx+GYFu5fOlaL NShrb/pc6AQZHucLjDfLxn+479Z7zgfxFDDiDdnGjUdmcYHZds1v+6WuwwIi+HwD X6Edqfd37h+itGBt2h8LNgNA4urbWW7Xq7amsojjmOBgqdJ2Pe6ML+L0txwtY/cN ICcBuDlJj3qXf81JZqr2zBa7+1DOYB+EFMTtOBwIUQKixAh1PL/+EbarDNLTOKld tiRL9wjkiGKGXgX5fBj06949XMP2Nsi4xyQwc9hhvujsY4zNmBJvvj/ui6w7tRGI P68tmOBeVPwVVHzfFvOm4MgHZpS0gzL9cr04p+knB6IBzjkfBEmUjGXC/85MGmXG TY4uqxb8dCMidsn6TG3D =lu5h -----END PGP SIGNATURE----- --xIk0xHvQc0Ku+QuL-- From owner-freebsd-current@FreeBSD.ORG Sat Feb 2 21:47:17 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 945863D3; Sat, 2 Feb 2013 21:47:17 +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 2E8377A7; Sat, 2 Feb 2013 21:47:16 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id r12Ll9JK099456; Sat, 2 Feb 2013 22:47:09 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.5/8.14.5/Submit) id r12Ll9dm099455; Sat, 2 Feb 2013 22:47:09 +0100 (CET) (envelope-from marius) Date: Sat, 2 Feb 2013 22:47:09 +0100 From: Marius Strobl To: Konstantin Belousov Subject: Re: Physbio changes final call for tests and reviews Message-ID: <20130202214709.GA99418@alchemy.franken.de> References: <20130202163322.GA2522@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130202163322.GA2522@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: powerpc@freebsd.org, mips@freebsd.org, current@freebsd.org, ia64@freebsd.org, arch@freebsd.org, sparc64@freebsd.org, arm@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 21:47:17 -0000 On Sat, Feb 02, 2013 at 06:33:22PM +0200, Konstantin Belousov wrote: > Hi, > I finished the last (insignificant) missed bits in the Jeff' physbio > work. Now I am asking for the last round of testing and review, esp. for > the !x86 architectures. Another testing focus are the SCSI HBAs and RAID > controllers which drivers are changed by the patchset. Please do test > this before the patchset is committed into HEAD ! > > The plan is to commit the patch somewhere in two weeks from this moment. > The patch is required for the finalizing of the unmapped I/O work for UFS > I did in parallel, which I hope to finish shortly after the commit. > > Patch is available at http://people.freebsd.org/~kib/misc/physbio.5.diff > First tests on sparc64 with ata(4), mpt(4) and sym(4) look good (to be sure I still need to test with a machine using a streaming buffer in addition to the IOMMU, though). However, by accident I noticed that your patch (i.e. stock head is fine) somehow breaks smartd of smartmontools with ata(4): root@b1k2:/root # smartd ata3: timeout waiting for write DRQ The machine just hangs at this point (it's also strange that the above message is from the PIO rather than from the DMA path). One note: mjacob@ probably will be annoyed if you don't wrap the changes to isp(4) in __FreeBSD_version so the same source still compiles on older ones. Marius