From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 12:56:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1DDC106564A for ; Sun, 24 Jul 2011 12:56:36 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id CDD2D8FC12 for ; Sun, 24 Jul 2011 12:56:35 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 63823E62BF for ; Sun, 24 Jul 2011 13:56:34 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; s=mail; bh=ot63uHWvTpOOIoFL0nZ12YIrToc=; b=hEK f3lHq49W6Qt7ySuSj9BbVH7okXd+QnR1PXkDBj9K22LpQKXJjGPOIXwnq6R6ck3X TcL/hNLaQILdyDDJiME2U0OTNn1UlKhLK8B2h5G0nX5P0Ig8K3UmOmM9Gn6lhoma c+IfGgIbRyplf5oJpBSqTQaKT6dkvXjLvdujlFhA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; q=dns; s=mail; b=aX8vjb/dB8nWnd7+6N4G2hqtf77D+ 5glDYQguLlQdx0VytpAM6FkBCHSRiS6/z7KW03FVobXStm2Knbfp/MvrMBucBUK/ ULCSKny5+SvP6RrXhbjL7y8L7wPDUxB1/CjBk+pYrShOJprvS33H3YAxErjHG69O LHpFuOwToU3XlY= Received: from neutrino.lan (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 4564DE62B4 for ; Sun, 24 Jul 2011 13:56:34 +0100 (BST) From: Bruce Cran Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 24 Jul 2011 13:56:33 +0100 Message-Id: To: freebsd-current@freebsd.org Mime-Version: 1.0 (Apple Message framework v1244.3) X-Mailer: Apple Mail (2.1244.3) Subject: 8th July snapshot: bsdinstall not creating homedir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 12:56:36 -0000 I've installed FreeBSD snapshots a couple of times this week. With = Virtualbox 4.1 on both Windows and OS X with a 20GB disk I've found the = installer forgets to create the homedir - /home doesn't exist, so when = you get placed at / when logging in. Unfortunately pub.allbsd.org seems = to be queued up so I've not been able to try any more recent snapshots = (should the snapshot ISOs be labelled with "-release.iso")? --=20 Bruce Cran= From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 13:34:46 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9E30106566B for ; Sun, 24 Jul 2011 13:34:46 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.vlsi.ee.noda.tus.ac.jp (sekine00.ee.noda.sut.ac.jp [133.31.107.40]) by mx1.freebsd.org (Postfix) with ESMTP id 6D7938FC0A for ; Sun, 24 Jul 2011 13:34:46 +0000 (UTC) Received: from alph.allbsd.org (p3028-ipbf608funabasi.chiba.ocn.ne.jp [125.175.94.28]) (user=hrs mech=DIGEST-MD5 bits=128) by mail.vlsi.ee.noda.tus.ac.jp (8.14.4/8.14.4) with ESMTP id p6ODG6bt017069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 24 Jul 2011 22:16:16 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.14.4/8.14.4) with ESMTP id p6ODG4lJ045999; Sun, 24 Jul 2011 22:16:06 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 24 Jul 2011 22:16:02 +0900 (JST) Message-Id: <20110724.221602.928409367144947054.hrs@allbsd.org> To: bruce@cran.org.uk From: Hiroki Sato In-Reply-To: References: X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sun_Jul_24_22_16_02_2011_988)--" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (mail.vlsi.ee.noda.tus.ac.jp [133.31.107.40]); Sun, 24 Jul 2011 22:16:17 +0900 (JST) X-Spam-Status: No, score=-1.7 required=14.0 tests=BAYES_05, CONTENT_TYPE_PRESENT,RCVD_IN_CHINA,RCVD_IN_CHINA_KR,RCVD_IN_RP_RNBL, RCVD_IN_TAIWAN, SPF_SOFTFAIL, X_MAILER_PRESENT autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.vlsi.ee.noda.tus.ac.jp Cc: freebsd-current@FreeBSD.org Subject: Re: 8th July snapshot: bsdinstall not creating homedir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 13:34:47 -0000 ----Security_Multipart(Sun_Jul_24_22_16_02_2011_988)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bruce Cran wrote in : br> I've installed FreeBSD snapshots a couple of times this week. With br> Virtualbox 4.1 on both Windows and OS X with a 20GB disk I've found br> the installer forgets to create the homedir - /home doesn't exist, so br> when you get placed at / when logging in. Unfortunately br> pub.allbsd.org seems to be queued up so I've not been able to try any br> more recent snapshots (should the snapshot ISOs be labelled with br> "-release.iso")? Sorry, due to a hardware trouble on Saturday some of the snapshots had to be removed. It recovered already and generating ones as of July 21-24 now, FYI. -- Hiroki ----Security_Multipart(Sun_Jul_24_22_16_02_2011_988)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk4sGxIACgkQTyzT2CeTzy249gCfaFHH+0ir8+XHEZL7PB93vKu7 bs4AoNLMTVy7Gc2OV2gjSZILECFFX/2Y =CnpZ -----END PGP SIGNATURE----- ----Security_Multipart(Sun_Jul_24_22_16_02_2011_988)---- From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 14:06:06 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52A9E106566B for ; Sun, 24 Jul 2011 14:06:06 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id D94978FC12 for ; Sun, 24 Jul 2011 14:06:05 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id 72F377E884; Sun, 24 Jul 2011 15:48:02 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 24 Jul 2011 13:48:02 +0000 From: Baptiste Daroussin Message-ID: X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Cc: Subject: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 14:06:06 -0000 Hi, Trying to upgrade one of my box from 8-stable to 9-current lead be to some important problems. I'm have tried both from sources (svn buildworld etc.) and from memdisk provided by allbsd.org. The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 more informations here : http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and http://people.freebsd.org/~bapt/P5N-E.pciconv.txt Both memstick and install current stopped claiming they can mount the root filesystem. when trying to list disks in the "mountroot>" prompt it doesn't list anythings. before failing in the boot process, there are some warning : run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config I have no way to netboot this box. regards, Bapt From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 21:25:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id DF90B106566C; Sun, 24 Jul 2011 21:25:44 +0000 (UTC) Date: Sun, 24 Jul 2011 21:25:44 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20110724212544.GA57733@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: freebsd-chromium@freebsd.org Subject: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 21:25:45 -0000 hi there, i noticed that chromium, expecially in combination with nspluginwrapper and flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 999999' and after only ~ 4 hours of running chromium (most of the time not loading any new pages), i got the following data: last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 72 processes: 2 running, 70 sleeping Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free Swap: 10G Total, 159M Used, 10G Free, 1% Inuse PID UID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 39908 1001 7409 51112 0 0 4 4 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39605 1001 598315 233115 11 0 3 14 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 1752 1001 22292378 29644471 138 0 696 834 0.38% /usr/local/bin/Xorg -nolisten inet6 1756 1001 1551733 2002630 480 0 455 935 0.43% /usr/local/bin/awesome 39140 1001 10672291 1240670 0 0 6522 6522 2.97% chrome: --type=zygote (chrome) 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% chromium-browser: (chrome) 39138 1001 6436642 994546 0 0 1785 1785 0.81% chrome: --type=zygote (chrome) 39135 1001 4334272 169320 0 0 1723 1723 0.78% chrome: --type=zygote (chrome) 39133 1001 4321593 169574 1 0 1717 1718 0.78% chrome: --type=zygote (chrome) 39132 1001 4292029 164913 6 0 1766 1772 0.81% chrome: --type=zygote (chrome) 39137 1001 4152284 139225 1 0 1762 1763 0.80% chrome: --type=zygote (chrome) 1629 560 356784 70399 25 0 40 65 0.03% /usr/local/sbin/hald 1767 1001 355603 87998 32 0 0 32 0.01% /usr/local/libexec/gam_server 39144 1001 2659919 409841 0 0 3578 3578 1.63% chrome: --type=plugin --plugin-path=/usr/home/arundel/.mozill 10217 1001 472898 258689 601 1 8 610 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf 39121 1001 552140 44286 1 0 181 182 0.08% chrome: --type=zygote (chrome) 39358 1001 103237 20357 223 1479 211 1913 0.87% /usr/local/bin/sakura 39119 1001 91173 58899 2 0 14795 14797 6.74% chrome: --type=zygote (chrome) 39846 1001 275524 51575 0 0 7085 7085 3.23% chrome: --type=zygote (chrome) 39120 1001 60470 18204 0 0 22 22 0.01% chrome: --type=zygote (chrome) 1538 0 53910 6390 0 0 1 1 0.00% sendmail: accepting connections (sendmail) 39363 1001 33822 9157 1 1113 3 1117 0.51% /usr/local/bin/sakura 39805 1001 55542 43060 0 0 2787 2787 1.27% chrome: --type=zygote (chrome) 39117 1001 2935 13041 156 0 155 311 0.14% chromium-browser: (chrome) 39902 1001 43829 31005 0 0 4477 4477 2.04% chrome: --type=zygote (chrome) 362 0 28923 1878 1 0 5 6 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant 1548 0 5122 672 11 0 0 11 0.01% /usr/sbin/cron -s 1217 0 13118 676 21 39 0 60 0.03% /usr/sbin/syslogd -s 39907 1001 16179 6366 0 0 2 2 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi 39118 1001 976 716 90 0 81 171 0.08% chrome: --type=zygote (chrome) 1345 0 1362 201 1 0 2 3 0.00% /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et 1685 1001 180 22 52 0 30 82 0.04% -zsh (zsh) 1458 65534 512 62 2 0 0 2 0.00% /usr/local/bin/mpdscribble --daemon-user nobody 39360 1001 394 287 14 0 5 19 0.01% /usr/local/bin/zsh 1636 0 184 181 8 0 0 8 0.00% hald-runner 39365 1001 98 113 18 0 0 18 0.01% /usr/local/bin/zsh 1633 0 648 133 29 0 5 34 0.02% /usr/local/libexec/polkitd 1631 0 608 71 15 0 24 39 0.02% /usr/local/sbin/console-kit-daemon --no-daemon 39931 1001 53 81 1 0 1 2 0.00% /usr/local/bin/zsh 1713 1001 21 16 0 0 2 2 0.00% ssh-agent 1352 556 176 125 2 0 0 2 0.00% /usr/local/bin/dbus-daemon --system 1494 0 62 17 45 0 14 59 0.03% /usr/local/sbin/cupsd -C /usr/local/etc/cups/cupsd.conf 1733 1001 20 0 1 0 0 1 0.00% /bin/sh /usr/local/bin/startx 1617 0 33 15 7 0 0 7 0.00% login [pam] (login) 1751 1001 16 4 0 0 4 4 0.00% xinit /home/arundel/.xinitrc -- /home/arundel/.xserverrc :0 -a 39953 1001 18 33 1 0 0 1 0.00% /bin/sh /usr/bin/man top 1635 0 28 8 18 0 0 18 0.01% /usr/local/libexec/gam_server 1618 0 7 3 1 0 2 3 0.00% /usr/libexec/getty Pc ttyv1 1755 1001 3 0 1 0 0 1 0.00% sh /home/arundel/.xinitrc ... is anybody else experiencing the same behavior? i also noticed a massive fault burst (~ 1500/sec), when closing chromium. cheers. alex P.S.: i'm running HEAD on amd64 and the chromium port is @ 12.0.742.124. From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 21:29:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27972106564A for ; Sun, 24 Jul 2011 21:29:41 +0000 (UTC) (envelope-from eculp@encontacto.net) Received: from ns2.bafirst.com (ns2.bafirst.com [97.67.198.91]) by mx1.freebsd.org (Postfix) with ESMTP id A9B658FC08 for ; Sun, 24 Jul 2011 21:29:40 +0000 (UTC) Received: from unixmania.com ([189.251.157.180]) by ns2.bafirst.com with esmtp; Sun, 24 Jul 2011 16:29:38 -0500 id 000DA804.4E2C8EC2.0000DF77 Received: from localhost (localhost [127.0.0.1]) (uid 80) by unixmania.com with local; Sun, 24 Jul 2011 16:29:37 -0500 id 000CF710.4E2C8EC1.00016DC8 Received: from dsl-189-251-133-16-dyn.prod-infinitum.com.mx (dsl-189-251-133-16-dyn.prod-infinitum.com.mx [189.251.133.16]) by econet.encontacto.net (Horde Framework) with HTTP; Sun, 24 Jul 2011 16:29:37 -0500 Message-ID: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> Date: Sun, 24 Jul 2011 16:29:37 -0500 From: eculp To: freebsd-current MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs) X-Remote-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0.1) Gecko/20100101 Firefox/5.0.1 X-IMP-Server: 189.251.157.180 X-Originating-IP: 189.251.133.16 X-Originating-User: eculp@encontacto.net Subject: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 21:29:41 -0000 I have been hearing about a new installer but I obviously have not payed enough attention, I am afraid. I started running freebsd at 2.0 and never really had a problem with understanding the installation program. There is always a first time, I guess. ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ When booting I seem to get a screen that makes me remember installer screens of the 1980s. (They were not exactly intuitive.) I somehow got the idea that the new installer was graphic. Maybe something like PCBsd that is not bad at all. I use it on all our employees computers. Actually, after seeing this, I would love to have the old installer back. Is their an option for that? Does this new ASCII installer have a "how to" with a bit of information on the flow of the installation. Thanks, ed P.D. The handbook does not seem to cover the installer I am seeing because it is 8.2. It shows what I would love to see. Maybe I need to install 8.2 and upgrade? From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 21:33:53 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66AFD1065674 for ; Sun, 24 Jul 2011 21:33:53 +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 397DC8FC13 for ; Sun, 24 Jul 2011 21:33:53 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOU00N00X8G1V00@smtpauth2.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 24 Jul 2011 16:33:52 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOU00CFTX8F6620@smtpauth2.wiscmail.wisc.edu>; Sun, 24 Jul 2011 16:33:51 -0500 (CDT) Date: Sun, 24 Jul 2011 16:33:50 -0500 From: Nathan Whitehorn In-reply-to: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> To: eculp Message-id: <4E2C8FBE.7040003@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-11, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.24.212414, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 21:33:53 -0000 On 07/24/11 16:29, eculp wrote: > I have been hearing about a new installer but I obviously have not > payed enough attention, I am afraid. I started running freebsd at 2.0 > and never really had a problem with understanding the installation > program. There is always a first time, I guess. > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ > > When booting I seem to get a screen that makes me remember installer > screens of the 1980s. (They were not exactly intuitive.) > > I somehow got the idea that the new installer was graphic. Maybe > something like PCBsd that is not bad at all. I use it on all our > employees computers. Actually, after seeing this, I would love to > have the old installer back. Is their an option for that? > > Does this new ASCII installer have a "how to" with a bit of > information on the flow of the installation. > > Thanks, Can you please describe what you didn't like about it, and what you would prefer be changed? "Reminiscent of the 1980s" is not really helpful, especially given that the new installer in fact looks very much like sysinstall, which you seemed to like. -Nathan From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 22:15:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFA21106564A for ; Sun, 24 Jul 2011 22:15:38 +0000 (UTC) (envelope-from eculp@encontacto.net) Received: from ns2.bafirst.com (ns2.bafirst.com [97.67.198.91]) by mx1.freebsd.org (Postfix) with ESMTP id 838878FC18 for ; Sun, 24 Jul 2011 22:15:38 +0000 (UTC) Received: from unixmania.com ([189.251.157.180]) by ns2.bafirst.com with esmtp; Sun, 24 Jul 2011 17:15:36 -0500 id 000DA802.4E2C9988.0000DFF1 Received: from localhost (localhost [127.0.0.1]) (uid 80) by unixmania.com with local; Sun, 24 Jul 2011 17:15:36 -0500 id 000CF710.4E2C9988.0001729C Received: from dsl-189-251-133-16-dyn.prod-infinitum.com.mx (dsl-189-251-133-16-dyn.prod-infinitum.com.mx [189.251.133.16]) by econet.encontacto.net (Horde Framework) with HTTP; Sun, 24 Jul 2011 17:15:36 -0500 Message-ID: <20110724171536.148015fc381jjog0@econet.encontacto.net> Date: Sun, 24 Jul 2011 17:15:36 -0500 From: eculp To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> In-Reply-To: <4E2C8FBE.7040003@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs) X-Remote-Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0.1) Gecko/20100101 Firefox/5.0.1 X-IMP-Server: 189.251.157.180 X-Originating-IP: 189.251.133.16 X-Originating-User: eculp@encontacto.net Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 22:15:39 -0000 Quoting Nathan Whitehorn : > On 07/24/11 16:29, eculp wrote: >> I have been hearing about a new installer but I obviously have not =20 >> payed enough attention, I am afraid. I started running freebsd at =20 >> 2.0 and never really had a problem with understanding the =20 >> installation program. There is always a first time, I guess. >> >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >> >> When booting I seem to get a screen that makes me remember =20 >> installer screens of the 1980s. (They were not exactly intuitive.) >> >> I somehow got the idea that the new installer was graphic. Maybe =20 >> something like PCBsd that is not bad at all. I use it on all our =20 >> employees computers. Actually, after seeing this, I would love to =20 >> have the old installer back. Is their an option for that? >> >> Does this new ASCII installer have a "how to" with a bit of =20 >> information on the flow of the installation. >> >> Thanks, > > Can you please describe what you didn't like about it, and what you =20 > would prefer be changed? "Reminiscent of the 1980s" is not really =20 > helpful, especially given that the new installer in fact looks very =20 > much like sysinstall, which you seemed to like. > -Nathan I do not get a menu that I can understand or relate to any of the =20 installations that I have done previously. I will give it another try =20 and try to explain what I don't understand. Thanks, ed P.S. Is their no documentation on what to expect? > _______________________________________________ > 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 Sun Jul 24 23:03:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9AF5106564A; Sun, 24 Jul 2011 23:03:08 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 82B118FC0C; Sun, 24 Jul 2011 23:03:08 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id p6ON33EC087717; Sun, 24 Jul 2011 18:03:04 -0500 (CDT) (envelope-from rcm@fuzzwad.org) Message-ID: <4E2CA4A7.7020100@fuzzwad.org> Date: Sun, 24 Jul 2011 18:03:03 -0500 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> In-Reply-To: <4E2C8FBE.7040003@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 23:03:08 -0000 Nathan Whitehorn wrote: > On 07/24/11 16:29, eculp wrote: >> I have been hearing about a new installer but I obviously have not >> payed enough attention, I am afraid. I started running freebsd at 2.0 >> and never really had a problem with understanding the installation >> program. There is always a first time, I guess. >> >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >> >> When booting I seem to get a screen that makes me remember installer >> screens of the 1980s. (They were not exactly intuitive.) >> >> I somehow got the idea that the new installer was graphic. Maybe >> something like PCBsd that is not bad at all. I use it on all our >> employees computers. Actually, after seeing this, I would love to >> have the old installer back. Is their an option for that? >> >> Does this new ASCII installer have a "how to" with a bit of >> information on the flow of the installation. >> >> Thanks, > > Can you please describe what you didn't like about it, and what you > would prefer be changed? "Reminiscent of the 1980s" is not really > helpful, especially given that the new installer in fact looks very > much like sysinstall, which you seemed to like. > -Nathan > I'll have to agree with the original poster. I have no problem with the look and feel of the new installer, but when functionality that WAS there is now gone, that's a problem. My two, make that three, biggest gripes are: 1) no "back" button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. 2) no "minimal" install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. 3) I see no "post-install" uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. -- Ron McDowell San Antonio TX From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 23:41:49 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D8DA1065670; Sun, 24 Jul 2011 23:41:49 +0000 (UTC) (envelope-from nlopes.ml@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 365768FC08; Sun, 24 Jul 2011 23:41:48 +0000 (UTC) Received: by ywf7 with SMTP id 7so2359679ywf.13 for ; Sun, 24 Jul 2011 16:41:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=XjOxyxEqvkTueUD67nURvMhmle3pPj55s4HXVl8LeeA=; b=w+VwVbcRpQACO0VaGP2IQVJ9Rt0+nF3zoN8iv5ZTD8yVypoiZuskTTlDoXTNaKJ6UH /VOIjWV0tC1PVkmhYe5dSd2pVfGvMsC4IuZX3yMH8cVl0qyJGKrZeLMxCMXiqmMwnM0S zxbEHAdMMfzK1fmyTBYylHqY/8gpyHv37DDvI= Received: by 10.150.229.16 with SMTP id b16mr3940899ybh.155.1311549604905; Sun, 24 Jul 2011 16:20:04 -0700 (PDT) Received: from [192.168.1.131] (ip72-211-218-249.oc.oc.cox.net [72.211.218.249]) by mx.google.com with ESMTPS id k8sm2712513yhm.31.2011.07.24.16.20.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 24 Jul 2011 16:20:04 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Norberto Lopes In-Reply-To: <20110724212544.GA57733@freebsd.org> Date: Sun, 24 Jul 2011 16:19:54 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <6202EFC8-449C-4AC9-B6F2-306E836642BC@gmail.com> References: <20110724212544.GA57733@freebsd.org> To: Alexander Best X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-chromium@freebsd.org, freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jul 2011 23:41:49 -0000 Same here. I have no way of sending my dump as I'm leaving for OScon and have no = access to my desktop, but I did see this behavior. I'm also running HEAD on amd64. Cheers, Norberto On Jul 24, 2011, at 2:25 PM, Alexander Best wrote: > hi there, >=20 > i noticed that chromium, expecially in combination with = nspluginwrapper and > flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 999999' = and after > only ~ 4 hours of running chromium (most of the time not loading any = new > pages), i got the following data: >=20 > last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 = 23:15:26 > 72 processes: 2 running, 70 sleeping >=20 > Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M = Free > Swap: 10G Total, 159M Used, 10G Free, 1% Inuse >=20 >=20 > PID UID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT = COMMAND > 39908 1001 7409 51112 0 0 4 4 0.00% = /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > 39605 1001 598315 233115 11 0 3 14 0.01% = /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > 1752 1001 22292378 29644471 138 0 696 834 0.38% = /usr/local/bin/Xorg -nolisten inet6 > 1756 1001 1551733 2002630 480 0 455 935 0.43% = /usr/local/bin/awesome > 39140 1001 10672291 1240670 0 0 6522 6522 2.97% = chrome: --type=3Dzygote (chrome) > 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% = chromium-browser: (chrome) > 39138 1001 6436642 994546 0 0 1785 1785 0.81% = chrome: --type=3Dzygote (chrome) > 39135 1001 4334272 169320 0 0 1723 1723 0.78% = chrome: --type=3Dzygote (chrome) > 39133 1001 4321593 169574 1 0 1717 1718 0.78% = chrome: --type=3Dzygote (chrome) > 39132 1001 4292029 164913 6 0 1766 1772 0.81% = chrome: --type=3Dzygote (chrome) > 39137 1001 4152284 139225 1 0 1762 1763 0.80% = chrome: --type=3Dzygote (chrome) > 1629 560 356784 70399 25 0 40 65 0.03% = /usr/local/sbin/hald > 1767 1001 355603 87998 32 0 0 32 0.01% = /usr/local/libexec/gam_server > 39144 1001 2659919 409841 0 0 3578 3578 1.63% = chrome: --type=3Dplugin --plugin-path=3D/usr/home/arundel/.mozill > 10217 1001 472898 258689 601 1 8 610 0.28% = /usr/local/bin/musicpd /usr/local/etc/musicpd.conf > 39121 1001 552140 44286 1 0 181 182 0.08% = chrome: --type=3Dzygote (chrome) > 39358 1001 103237 20357 223 1479 211 1913 0.87% = /usr/local/bin/sakura > 39119 1001 91173 58899 2 0 14795 14797 6.74% = chrome: --type=3Dzygote (chrome) > 39846 1001 275524 51575 0 0 7085 7085 3.23% = chrome: --type=3Dzygote (chrome) > 39120 1001 60470 18204 0 0 22 22 0.01% = chrome: --type=3Dzygote (chrome) > 1538 0 53910 6390 0 0 1 1 0.00% = sendmail: accepting connections (sendmail) > 39363 1001 33822 9157 1 1113 3 1117 0.51% = /usr/local/bin/sakura > 39805 1001 55542 43060 0 0 2787 2787 1.27% = chrome: --type=3Dzygote (chrome) > 39117 1001 2935 13041 156 0 155 311 0.14% = chromium-browser: (chrome) > 39902 1001 43829 31005 0 0 4477 4477 2.04% = chrome: --type=3Dzygote (chrome) > 362 0 28923 1878 1 0 5 6 0.00% = /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant > 1548 0 5122 672 11 0 0 11 0.01% = /usr/sbin/cron -s > 1217 0 13118 676 21 39 0 60 0.03% = /usr/sbin/syslogd -s > 39907 1001 16179 6366 0 0 2 2 0.00% = /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > 39118 1001 976 716 90 0 81 171 0.08% = chrome: --type=3Dzygote (chrome) > 1345 0 1362 201 1 0 2 3 0.00% = /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et > 1685 1001 180 22 52 0 30 82 0.04% -zsh = (zsh) > 1458 65534 512 62 2 0 0 2 0.00% = /usr/local/bin/mpdscribble --daemon-user nobody > 39360 1001 394 287 14 0 5 19 0.01% = /usr/local/bin/zsh > 1636 0 184 181 8 0 0 8 0.00% = hald-runner > 39365 1001 98 113 18 0 0 18 0.01% = /usr/local/bin/zsh > 1633 0 648 133 29 0 5 34 0.02% = /usr/local/libexec/polkitd > 1631 0 608 71 15 0 24 39 0.02% = /usr/local/sbin/console-kit-daemon --no-daemon > 39931 1001 53 81 1 0 1 2 0.00% = /usr/local/bin/zsh > 1713 1001 21 16 0 0 2 2 0.00% = ssh-agent > 1352 556 176 125 2 0 0 2 0.00% = /usr/local/bin/dbus-daemon --system > 1494 0 62 17 45 0 14 59 0.03% = /usr/local/sbin/cupsd -C /usr/local/etc/cups/cupsd.conf > 1733 1001 20 0 1 0 0 1 0.00% = /bin/sh /usr/local/bin/startx > 1617 0 33 15 7 0 0 7 0.00% login = [pam] (login) > 1751 1001 16 4 0 0 4 4 0.00% xinit = /home/arundel/.xinitrc -- /home/arundel/.xserverrc :0 -a > 39953 1001 18 33 1 0 0 1 0.00% = /bin/sh /usr/bin/man top > 1635 0 28 8 18 0 0 18 0.01% = /usr/local/libexec/gam_server > 1618 0 7 3 1 0 2 3 0.00% = /usr/libexec/getty Pc ttyv1 > 1755 1001 3 0 1 0 0 1 0.00% sh = /home/arundel/.xinitrc >=20 > ... is anybody else experiencing the same behavior? i also noticed a = massive > fault burst (~ 1500/sec), when closing chromium. >=20 > cheers. > alex >=20 > P.S.: i'm running HEAD on amd64 and the chromium port is @ = 12.0.742.124. > _______________________________________________ > 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 Jul 25 00:41:28 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE841065670 for ; Mon, 25 Jul 2011 00:41:28 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 17AD58FC12 for ; Mon, 25 Jul 2011 00:41:27 +0000 (UTC) Received: (qmail invoked by alias); 25 Jul 2011 00:14:45 -0000 Received: from g225198214.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.225.198.214] by mail.gmx.net (mp031) with SMTP; 25 Jul 2011 02:14:45 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX18DkB1dmF8D3ArHZ/R/JmVgBJ5ccGXIyAeI0fD0va IopFNPOKCqJz8d Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id AA13223CE50 for ; Mon, 25 Jul 2011 02:14:44 +0200 (CEST) Message-ID: <4E2CB574.7060303@gmx.de> Date: Mon, 25 Jul 2011 02:14:44 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Mnenhy/0.8.3 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20110724212544.GA57733@freebsd.org> In-Reply-To: <20110724212544.GA57733@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:41:28 -0000 Am 24.07.2011 23:25, schrieb Alexander Best: > hi there, > > i noticed that chromium, expecially in combination with nspluginwrapper and > flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 999999' and after It's causing page faults, which is a massive difference. > only ~ 4 hours of running chromium (most of the time not loading any new > pages), i got the following data: > > last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 > 72 processes: 2 running, 70 sleeping > > Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free > Swap: 10G Total, 159M Used, 10G Free, 1% Inuse > ... is anybody else experiencing the same behavior? i also noticed a massive > fault burst (~ 1500/sec), when closing chromium. Is that special to Chrome or -CURRENT? Or does it also happen with Firefox, for instance, or on -STABLE? I suppose FF might cause even more, it readily consumes 1.5 GB on my Linux computer after some time running. A page fault affecting 1500 pages/s (note it's "s" NOT "sec"!) amounts to 6 MB/s which appears to be on the comfortable side for any halfway modern system. Page in/page out is quite normal behaviour for any system that has swap space available and is running (especially idle) applications with nontrivial memory requirements and ultimately filling up its ram. At some point in time, when applications have been idle for long enough, it's more useful to page out unused pages and use them as cache instead. Why would a swap usage of 8% of physical RAM size be a reason for concern on a 2 GB RAM 64-bit computer? From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 00:41:31 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FD501065672 for ; Mon, 25 Jul 2011 00:41:31 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr [80.12.242.128]) by mx1.freebsd.org (Postfix) with ESMTP id 9C4808FC15 for ; Mon, 25 Jul 2011 00:41:29 +0000 (UTC) Received: from localhost ([92.156.103.33]) by mwinf5d29 with ME id C0BR1h0020jEdKQ030BRc6; Mon, 25 Jul 2011 02:11:26 +0200 X-ME-engine: default Message-ID: <4E2CB4AC.3070403@orange.fr> Date: Mon, 25 Jul 2011 02:11:24 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.18) Gecko/20110622 Thunderbird/3.1.11 MIME-Version: 1.0 To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> In-Reply-To: <4E2C8FBE.7040003@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:41:31 -0000 On 07/24/2011 23:33, Nathan Whitehorn wrote: > On 07/24/11 16:29, eculp wrote: >> I have been hearing about a new installer but I obviously have not >> payed enough attention, I am afraid. I started running freebsd at 2.0 >> and never really had a problem with understanding the installation >> program. There is always a first time, I guess. >> >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >> >> When booting I seem to get a screen that makes me remember installer >> screens of the 1980s. (They were not exactly intuitive.) >> >> I somehow got the idea that the new installer was graphic. Maybe >> something like PCBsd that is not bad at all. I use it on all our >> employees computers. Actually, after seeing this, I would love to >> have the old installer back. Is their an option for that? >> >> Does this new ASCII installer have a "how to" with a bit of >> information on the flow of the installation. >> >> Thanks, > > Can you please describe what you didn't like about it, and what you > would prefer be changed? "Reminiscent of the 1980s" is not really > helpful, especially given that the new installer in fact looks very much > like sysinstall, which you seemed to like. > -Nathan Recently I installed a system from the "official" memory stick May snapshot (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: - the 1st thing I need to do is to configure the keyboard, as I am not in the US. This is needed for an install, but also for using it as a live system. And the keyboard configuration dialog is only a part of the installation procedure. - the partition tool is too simple/rudimentary, compared to the old sysinstall dialog. I always want to have a total control of the partitions e.g. to have a proper alignement. So one must use the shell escape or the live system, which is a regression. - extracting the tarballs lead to (cryptic) errors: I discovered the hard way that I needed to execute a newfs. - I followed a succession of screens asking me to do the usual configuration steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I get back a screen asking me if a wanted to do the steps I had done just before... - booting the installed system, I found that the hostname disappeared, the keyboard was not configured, nor the network, and so on - during the whole process the screen was scrambled by the occurence of a number of LORs displayed on top of the dialogs/messages of the installer. - the file system of the installer/live system seems to be too small, leading to a number of "system full" messages as soon a few files are written to it. So the sole value added of the installer was the extraction of the tarballs.. It seems that (on a memory stick which is writable) that every aborted attempt to do a configuration step leaves a "trace" in some files used by the installer, which is able to show it (e.g. the hostname) at the following attempts, but without garantee that it will effectively be used. (On the other hand, the advantage of the memory stick is that the system on it can be configured at will) Referring to a thread I found recently a propos the documentation on the install media, I also want to say that a proper installer must be able to do its work without any Internet connectivity. There exist systems which are not connected, and networks without any communication with the Internet. Claude Buisson From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 00:54:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 182A1106567A; Mon, 25 Jul 2011 00:54:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id B8C2D8FC1D; Mon, 25 Jul 2011 00:54:37 +0000 (UTC) Received: by yxl31 with SMTP id 31so2373810yxl.13 for ; Sun, 24 Jul 2011 17:54:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Ds2R+XmS2F1Onu1fkjmdnLRBAA+I6GHz4KjMkZz6ZRc=; b=w08BjAEpTvdDHoXVCP4JFIDtPiBmW/FmzwjDqr0YnQP0o2eTxlIaQpM1IffptlJRJV fVgZ28MsAt1m11dsNcV78XoREgFav+5RcWuF5iMSrh31lbz7jQuD60qthv0Jaf4VwEL5 3FEUodfTaRNYG3gXeDHEt+V/CQUmxvf3zj9dk= MIME-Version: 1.0 Received: by 10.150.74.3 with SMTP id w3mr3866608yba.329.1311555277014; Sun, 24 Jul 2011 17:54:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Sun, 24 Jul 2011 17:54:36 -0700 (PDT) In-Reply-To: <4E2CB4AC.3070403@orange.fr> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> Date: Mon, 25 Jul 2011 08:54:36 +0800 X-Google-Sender-Auth: SMzopNCcK7f0AeB0__D7VrMIEAo Message-ID: From: Adrian Chadd To: Claude Buisson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current , Nathan Whitehorn Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:54:38 -0000 .. wait, the install-off-USB doesn't default to a read-only boot? Adrian On 25 July 2011 08:11, Claude Buisson wrote: > On 07/24/2011 23:33, Nathan Whitehorn wrote: >> >> On 07/24/11 16:29, eculp wrote: >>> >>> I have been hearing about a new installer but I obviously have not >>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>> and never really had a problem with understanding the installation >>> program. =A0There is always a first time, I guess. >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>> >>> When booting I seem to get a screen that makes me remember installer >>> screens of the 1980s. =A0(They were not exactly intuitive.) >>> >>> I somehow got the idea that the new installer was graphic. =A0Maybe >>> something like PCBsd that is not bad at all. =A0I use it on all our >>> employees computers. =A0Actually, after seeing this, I would love to >>> have the old installer back. =A0Is their an option for that? >>> >>> Does this new ASCII installer have a "how to" with a bit of >>> information on the flow of the installation. >>> >>> Thanks, >> >> Can you please describe what you didn't like about it, and what you >> would prefer be changed? "Reminiscent of the 1980s" is not really >> helpful, especially given that the new installer in fact looks very much >> like sysinstall, which you seemed to like. >> -Nathan > > Recently I installed a system from the "official" memory stick May snapsh= ot > (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: > > - the 1st thing I need to do is to configure the keyboard, as I am not in > the > US. This is needed for an install, but also for using it as a live system= . > And > the keyboard configuration dialog is only a part of the installation > procedure. > > - the partition tool is too simple/rudimentary, compared to the old > sysinstall > dialog. I always want to have a total control of the partitions e.g. to h= ave > a > proper alignement. So one must use the shell escape or the live system, > which is > a regression. > > - extracting the tarballs lead to (cryptic) errors: I discovered the hard > way > that I needed to execute a newfs. > > - I followed a succession of screens asking me to do the usual configurat= ion > steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I > get > back a screen asking me if a wanted to do the steps I had done just > before... > > - booting the installed system, I found that the hostname disappeared, th= e > keyboard was not configured, nor the network, and so on > > - during the whole process the screen was scrambled by the occurence of a > number > of LORs displayed on top of the dialogs/messages of the installer. > > - the file system of the installer/live system seems to be too small, > leading to > a number of "system full" messages as soon a few files are written to it. > > So the sole value added of the installer was the extraction of the > tarballs.. > > It seems that (on a memory stick which is writable) that every aborted > attempt > to do a configuration step leaves a "trace" in some files used by the > installer, > which is able to show it (e.g. the hostname) at the following attempts, b= ut > without garantee that it will effectively be used. > > (On the other hand, the advantage of the memory stick is that the system = on > it > can be configured at will) > > Referring to a thread I found recently a propos the documentation on the > install > media, I also want to say that a proper installer must be able to do its > work > without any Internet connectivity. There exist systems which are not > connected, > and networks without any communication with the Internet. > > Claude Buisson > _______________________________________________ > 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 Jul 25 00:56:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD2B31065673 for ; Mon, 25 Jul 2011 00:56:38 +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 7E8758FC16 for ; Mon, 25 Jul 2011 00:56:38 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOV004006MDHD00@smtpauth2.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 24 Jul 2011 19:56:37 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOV00L916MCQI10@smtpauth2.wiscmail.wisc.edu>; Sun, 24 Jul 2011 19:56:37 -0500 (CDT) Date: Sun, 24 Jul 2011 19:56:35 -0500 From: Nathan Whitehorn In-reply-to: <4E2CB4AC.3070403@orange.fr> To: Claude Buisson Message-id: <4E2CBF43.1070302@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-9, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.25.4520, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:56:38 -0000 On 07/24/11 19:11, Claude Buisson wrote: > On 07/24/2011 23:33, Nathan Whitehorn wrote: >> On 07/24/11 16:29, eculp wrote: >>> I have been hearing about a new installer but I obviously have not >>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>> and never really had a problem with understanding the installation >>> program. There is always a first time, I guess. >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>> >>> When booting I seem to get a screen that makes me remember installer >>> screens of the 1980s. (They were not exactly intuitive.) >>> >>> I somehow got the idea that the new installer was graphic. Maybe >>> something like PCBsd that is not bad at all. I use it on all our >>> employees computers. Actually, after seeing this, I would love to >>> have the old installer back. Is their an option for that? >>> >>> Does this new ASCII installer have a "how to" with a bit of >>> information on the flow of the installation. >>> >>> Thanks, >> >> Can you please describe what you didn't like about it, and what you >> would prefer be changed? "Reminiscent of the 1980s" is not really >> helpful, especially given that the new installer in fact looks very much >> like sysinstall, which you seemed to like. >> -Nathan > > Recently I installed a system from the "official" memory stick May > snapshot > (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: Thank you for testing! > - the 1st thing I need to do is to configure the keyboard, as I am not > in the > US. This is needed for an install, but also for using it as a live > system. And > the keyboard configuration dialog is only a part of the installation > procedure. Which is why this is the very first screen of the installer? > - the partition tool is too simple/rudimentary, compared to the old > sysinstall > dialog. I always want to have a total control of the partitions e.g. > to have a > proper alignement. So one must use the shell escape or the live > system, which is > a regression. The alignment is done to match the disk stripe size automatically, and the partition editor has many, many more features than the sysinstall one. Is there something in particular you wanted? > - extracting the tarballs lead to (cryptic) errors: I discovered the > hard way > that I needed to execute a newfs. This is what the directions at the top of the partitioning shell say. > - I followed a succession of screens asking me to do the usual > configuration > steps (hostname, clock, network - IPv4 only ?? -, users) and at the > end I get > back a screen asking me if a wanted to do the steps I had done just > before... The network configuration also allows IPv6 in newer versions -- that snapshot is 2 months out of date. The final screen says at the top that is there to modify earlier choices. Can you suggest a clearer wording? > - booting the installed system, I found that the hostname disappeared, > the > keyboard was not configured, nor the network, and so on This is inexplicable. This has worked perfectly for everyone else -- it's possible you made a mistake in the partitioning, but I can't imagine how it would have caused this. Are you able to reproduce the problem? > - during the whole process the screen was scrambled by the occurence > of a number > of LORs displayed on top of the dialogs/messages of the installer. The actual 9.0 CDs will not have WITNESS enabled. It would be nice if the LORs in question were actually fixed, however. > - the file system of the installer/live system seems to be too small, > leading to > a number of "system full" messages as soon a few files are written to it. The live system is designed more as a fixit medium. What were you trying to do with it? > > Referring to a thread I found recently a propos the documentation on > the install > media, I also want to say that a proper installer must be able to do > its work > without any Internet connectivity. There exist systems which are not > connected, > and networks without any communication with the Internet. Which is why it behaves in exactly the way you suggest. -Nathan From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 00:57:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 225491065672; Mon, 25 Jul 2011 00:57:48 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from adsum.doit.wisc.edu (adsum.doit.wisc.edu [144.92.197.210]) by mx1.freebsd.org (Postfix) with ESMTP id E82CC8FC1A; Mon, 25 Jul 2011 00:57:47 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOV006006OBYQ00@smtpauth1.wiscmail.wisc.edu>; Sun, 24 Jul 2011 19:57:47 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOV00MGE6O9SJ10@smtpauth1.wiscmail.wisc.edu>; Sun, 24 Jul 2011 19:57:46 -0500 (CDT) Date: Sun, 24 Jul 2011 19:57:45 -0500 From: Nathan Whitehorn In-reply-to: To: Adrian Chadd Message-id: <4E2CBF89.7070104@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-11, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.25.4520, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: Claude Buisson , freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:57:48 -0000 It does not. I had tried to match the behavior of the 8.x memsticks. It's an easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however. -Nathan On 07/24/11 19:54, Adrian Chadd wrote: > .. wait, the install-off-USB doesn't default to a read-only boot? > > > > Adrian > > On 25 July 2011 08:11, Claude Buisson wrote: >> On 07/24/2011 23:33, Nathan Whitehorn wrote: >>> On 07/24/11 16:29, eculp wrote: >>>> I have been hearing about a new installer but I obviously have not >>>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>>> and never really had a problem with understanding the installation >>>> program. There is always a first time, I guess. >>>> >>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>>> >>>> When booting I seem to get a screen that makes me remember installer >>>> screens of the 1980s. (They were not exactly intuitive.) >>>> >>>> I somehow got the idea that the new installer was graphic. Maybe >>>> something like PCBsd that is not bad at all. I use it on all our >>>> employees computers. Actually, after seeing this, I would love to >>>> have the old installer back. Is their an option for that? >>>> >>>> Does this new ASCII installer have a "how to" with a bit of >>>> information on the flow of the installation. >>>> >>>> Thanks, >>> Can you please describe what you didn't like about it, and what you >>> would prefer be changed? "Reminiscent of the 1980s" is not really >>> helpful, especially given that the new installer in fact looks very much >>> like sysinstall, which you seemed to like. >>> -Nathan >> Recently I installed a system from the "official" memory stick May snapshot >> (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: >> >> - the 1st thing I need to do is to configure the keyboard, as I am not in >> the >> US. This is needed for an install, but also for using it as a live system. >> And >> the keyboard configuration dialog is only a part of the installation >> procedure. >> >> - the partition tool is too simple/rudimentary, compared to the old >> sysinstall >> dialog. I always want to have a total control of the partitions e.g. to have >> a >> proper alignement. So one must use the shell escape or the live system, >> which is >> a regression. >> >> - extracting the tarballs lead to (cryptic) errors: I discovered the hard >> way >> that I needed to execute a newfs. >> >> - I followed a succession of screens asking me to do the usual configuration >> steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I >> get >> back a screen asking me if a wanted to do the steps I had done just >> before... >> >> - booting the installed system, I found that the hostname disappeared, the >> keyboard was not configured, nor the network, and so on >> >> - during the whole process the screen was scrambled by the occurence of a >> number >> of LORs displayed on top of the dialogs/messages of the installer. >> >> - the file system of the installer/live system seems to be too small, >> leading to >> a number of "system full" messages as soon a few files are written to it. >> >> So the sole value added of the installer was the extraction of the >> tarballs.. >> >> It seems that (on a memory stick which is writable) that every aborted >> attempt >> to do a configuration step leaves a "trace" in some files used by the >> installer, >> which is able to show it (e.g. the hostname) at the following attempts, but >> without garantee that it will effectively be used. >> >> (On the other hand, the advantage of the memory stick is that the system on >> it >> can be configured at will) >> >> Referring to a thread I found recently a propos the documentation on the >> install >> media, I also want to say that a proper installer must be able to do its >> work >> without any Internet connectivity. There exist systems which are not >> connected, >> and networks without any communication with the Internet. >> >> Claude Buisson >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 00:58:12 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A4F2106566B for ; Mon, 25 Jul 2011 00:58:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id A99CD8FC0C for ; Mon, 25 Jul 2011 00:58:11 +0000 (UTC) Received: by gwb15 with SMTP id 15so2804738gwb.13 for ; Sun, 24 Jul 2011 17:58:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rpWZCsuACk1SQW+HEJ3w7sT7Xt2x0k/Skaaze0YpO6k=; b=aOqijACG6RK1i5CltYn4tEEAA/tLUP+X2DmbenLhPweLW41jSZitUdzUoljqOsUclr c12rqXXLKMB/r4cZ9iBTeiP3xfpIpQPt4gN23rJdTpeeWOTAjjLmKew1+I3Z4VZg1Hlu gBncHgVV5q2Ytj8pLgOYZRYXdiaAz1vtu9Mhk= MIME-Version: 1.0 Received: by 10.151.86.11 with SMTP id o11mr132344ybl.386.1311555490904; Sun, 24 Jul 2011 17:58:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Sun, 24 Jul 2011 17:58:10 -0700 (PDT) In-Reply-To: <20110724212544.GA57733@freebsd.org> References: <20110724212544.GA57733@freebsd.org> Date: Mon, 25 Jul 2011 08:58:10 +0800 X-Google-Sender-Auth: XmY6vMYzUrLq97_0cyZecRSFHTc Message-ID: From: Adrian Chadd To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-chromium@freebsd.org, freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 00:58:12 -0000 Is it perhaps doing disk IO using mmap? adrian On 25 July 2011 05:25, Alexander Best wrote: > hi there, > > i noticed that chromium, expecially in combination with nspluginwrapper a= nd > flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 999999' and = after > only ~ 4 hours of running chromium (most of the time not loading any new > pages), i got the following data: > > last pid: 39976; =A0load averages: =A00.37, =A00.26, =A00.19 =A0up 3+02:3= 8:30 =A0 =A023:15:26 > 72 processes: =A02 running, 70 sleeping > > Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free > Swap: 10G Total, 159M Used, 10G Free, 1% Inuse > > > =A0PID =A0 =A0UID =A0 =A0 VCSW =A0IVCSW =A0 READ =A0WRITE =A0FAULT =A0TOT= AL PERCENT COMMAND > 39908 =A0 1001 =A0 =A0 7409 =A051112 =A0 =A0 =A00 =A0 =A0 =A00 =A0 =A0 = =A04 =A0 =A0 =A04 =A0 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npvie= wer.bin --plugi > 39605 =A0 1001 =A0 598315 233115 =A0 =A0 11 =A0 =A0 =A00 =A0 =A0 =A03 =A0= =A0 14 =A0 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --= plugi > =A01752 =A0 1001 =A0 22292378 29644471 =A0 =A0138 =A0 =A0 =A00 =A0 =A0696= =A0 =A0834 =A0 0.38% /usr/local/bin/Xorg -nolisten inet6 > =A01756 =A0 1001 =A0 1551733 2002630 =A0 =A0480 =A0 =A0 =A00 =A0 =A0455 = =A0 =A0935 =A0 0.43% /usr/local/bin/awesome > 39140 =A0 1001 =A0 10672291 1240670 =A0 =A0 =A00 =A0 =A0 =A00 =A0 6522 = =A0 6522 =A0 2.97% chrome: --type=3Dzygote (chrome) > 39116 =A0 1001 =A0 5967965 3237798 =A0 8249 =A020401 136394 165044 =A075.= 14% chromium-browser: =A0(chrome) > 39138 =A0 1001 =A0 6436642 994546 =A0 =A0 =A00 =A0 =A0 =A00 =A0 1785 =A0 = 1785 =A0 0.81% chrome: --type=3Dzygote (chrome) > 39135 =A0 1001 =A0 4334272 169320 =A0 =A0 =A00 =A0 =A0 =A00 =A0 1723 =A0 = 1723 =A0 0.78% chrome: --type=3Dzygote (chrome) > 39133 =A0 1001 =A0 4321593 169574 =A0 =A0 =A01 =A0 =A0 =A00 =A0 1717 =A0 = 1718 =A0 0.78% chrome: --type=3Dzygote (chrome) > 39132 =A0 1001 =A0 4292029 164913 =A0 =A0 =A06 =A0 =A0 =A00 =A0 1766 =A0 = 1772 =A0 0.81% chrome: --type=3Dzygote (chrome) > 39137 =A0 1001 =A0 4152284 139225 =A0 =A0 =A01 =A0 =A0 =A00 =A0 1762 =A0 = 1763 =A0 0.80% chrome: --type=3Dzygote (chrome) > =A01629 =A0 =A0560 =A0 356784 =A070399 =A0 =A0 25 =A0 =A0 =A00 =A0 =A0 40= =A0 =A0 65 =A0 0.03% /usr/local/sbin/hald > =A01767 =A0 1001 =A0 355603 =A087998 =A0 =A0 32 =A0 =A0 =A00 =A0 =A0 =A00= =A0 =A0 32 =A0 0.01% /usr/local/libexec/gam_server > 39144 =A0 1001 =A0 2659919 409841 =A0 =A0 =A00 =A0 =A0 =A00 =A0 3578 =A0 = 3578 =A0 1.63% chrome: --type=3Dplugin --plugin-path=3D/usr/home/arundel/.m= ozill > 10217 =A0 1001 =A0 472898 258689 =A0 =A0601 =A0 =A0 =A01 =A0 =A0 =A08 =A0= =A0610 =A0 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf > 39121 =A0 1001 =A0 552140 =A044286 =A0 =A0 =A01 =A0 =A0 =A00 =A0 =A0181 = =A0 =A0182 =A0 0.08% chrome: --type=3Dzygote (chrome) > 39358 =A0 1001 =A0 103237 =A020357 =A0 =A0223 =A0 1479 =A0 =A0211 =A0 191= 3 =A0 0.87% /usr/local/bin/sakura > 39119 =A0 1001 =A0 =A091173 =A058899 =A0 =A0 =A02 =A0 =A0 =A00 =A014795 = =A014797 =A0 6.74% chrome: --type=3Dzygote (chrome) > 39846 =A0 1001 =A0 275524 =A051575 =A0 =A0 =A00 =A0 =A0 =A00 =A0 7085 =A0= 7085 =A0 3.23% chrome: --type=3Dzygote (chrome) > 39120 =A0 1001 =A0 =A060470 =A018204 =A0 =A0 =A00 =A0 =A0 =A00 =A0 =A0 22= =A0 =A0 22 =A0 0.01% chrome: --type=3Dzygote (chrome) > =A01538 =A0 =A0 =A00 =A0 =A053910 =A0 6390 =A0 =A0 =A00 =A0 =A0 =A00 =A0 = =A0 =A01 =A0 =A0 =A01 =A0 0.00% sendmail: accepting connections (sendmail) > 39363 =A0 1001 =A0 =A033822 =A0 9157 =A0 =A0 =A01 =A0 1113 =A0 =A0 =A03 = =A0 1117 =A0 0.51% /usr/local/bin/sakura > 39805 =A0 1001 =A0 =A055542 =A043060 =A0 =A0 =A00 =A0 =A0 =A00 =A0 2787 = =A0 2787 =A0 1.27% chrome: --type=3Dzygote (chrome) > 39117 =A0 1001 =A0 =A0 2935 =A013041 =A0 =A0156 =A0 =A0 =A00 =A0 =A0155 = =A0 =A0311 =A0 0.14% chromium-browser: =A0(chrome) > 39902 =A0 1001 =A0 =A043829 =A031005 =A0 =A0 =A00 =A0 =A0 =A00 =A0 4477 = =A0 4477 =A0 2.04% chrome: --type=3Dzygote (chrome) > =A0362 =A0 =A0 =A00 =A0 =A028923 =A0 1878 =A0 =A0 =A01 =A0 =A0 =A00 =A0 = =A0 =A05 =A0 =A0 =A06 =A0 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c = /etc/wpa_supplicant > =A01548 =A0 =A0 =A00 =A0 =A0 5122 =A0 =A0672 =A0 =A0 11 =A0 =A0 =A00 =A0 = =A0 =A00 =A0 =A0 11 =A0 0.01% /usr/sbin/cron -s > =A01217 =A0 =A0 =A00 =A0 =A013118 =A0 =A0676 =A0 =A0 21 =A0 =A0 39 =A0 = =A0 =A00 =A0 =A0 60 =A0 0.03% /usr/sbin/syslogd -s > 39907 =A0 1001 =A0 =A016179 =A0 6366 =A0 =A0 =A00 =A0 =A0 =A00 =A0 =A0 = =A02 =A0 =A0 =A02 =A0 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npvie= wer.bin --plugi > 39118 =A0 1001 =A0 =A0 =A0976 =A0 =A0716 =A0 =A0 90 =A0 =A0 =A00 =A0 =A0 = 81 =A0 =A0171 =A0 0.08% chrome: --type=3Dzygote (chrome) > =A01345 =A0 =A0 =A00 =A0 =A0 1362 =A0 =A0201 =A0 =A0 =A01 =A0 =A0 =A00 = =A0 =A0 =A02 =A0 =A0 =A03 =A0 0.00% /usr/local/sbin/smartd -p /var/run/smar= td.pid -c /usr/local/et > =A01685 =A0 1001 =A0 =A0 =A0180 =A0 =A0 22 =A0 =A0 52 =A0 =A0 =A00 =A0 = =A0 30 =A0 =A0 82 =A0 0.04% -zsh (zsh) > =A01458 =A065534 =A0 =A0 =A0512 =A0 =A0 62 =A0 =A0 =A02 =A0 =A0 =A00 =A0 = =A0 =A00 =A0 =A0 =A02 =A0 0.00% /usr/local/bin/mpdscribble --daemon-user no= body > 39360 =A0 1001 =A0 =A0 =A0394 =A0 =A0287 =A0 =A0 14 =A0 =A0 =A00 =A0 =A0 = =A05 =A0 =A0 19 =A0 0.01% /usr/local/bin/zsh > =A01636 =A0 =A0 =A00 =A0 =A0 =A0184 =A0 =A0181 =A0 =A0 =A08 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 =A08 =A0 0.00% hald-runner > 39365 =A0 1001 =A0 =A0 =A0 98 =A0 =A0113 =A0 =A0 18 =A0 =A0 =A00 =A0 =A0 = =A00 =A0 =A0 18 =A0 0.01% /usr/local/bin/zsh > =A01633 =A0 =A0 =A00 =A0 =A0 =A0648 =A0 =A0133 =A0 =A0 29 =A0 =A0 =A00 = =A0 =A0 =A05 =A0 =A0 34 =A0 0.02% /usr/local/libexec/polkitd > =A01631 =A0 =A0 =A00 =A0 =A0 =A0608 =A0 =A0 71 =A0 =A0 15 =A0 =A0 =A00 = =A0 =A0 24 =A0 =A0 39 =A0 0.02% /usr/local/sbin/console-kit-daemon --no-dae= mon > 39931 =A0 1001 =A0 =A0 =A0 53 =A0 =A0 81 =A0 =A0 =A01 =A0 =A0 =A00 =A0 = =A0 =A01 =A0 =A0 =A02 =A0 0.00% /usr/local/bin/zsh > =A01713 =A0 1001 =A0 =A0 =A0 21 =A0 =A0 16 =A0 =A0 =A00 =A0 =A0 =A00 =A0 = =A0 =A02 =A0 =A0 =A02 =A0 0.00% ssh-agent > =A01352 =A0 =A0556 =A0 =A0 =A0176 =A0 =A0125 =A0 =A0 =A02 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 =A02 =A0 0.00% /usr/local/bin/dbus-daemon --system > =A01494 =A0 =A0 =A00 =A0 =A0 =A0 62 =A0 =A0 17 =A0 =A0 45 =A0 =A0 =A00 = =A0 =A0 14 =A0 =A0 59 =A0 0.03% /usr/local/sbin/cupsd -C /usr/local/etc/cup= s/cupsd.conf > =A01733 =A0 1001 =A0 =A0 =A0 20 =A0 =A0 =A00 =A0 =A0 =A01 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 =A01 =A0 0.00% /bin/sh /usr/local/bin/startx > =A01617 =A0 =A0 =A00 =A0 =A0 =A0 33 =A0 =A0 15 =A0 =A0 =A07 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 =A07 =A0 0.00% login [pam] (login) > =A01751 =A0 1001 =A0 =A0 =A0 16 =A0 =A0 =A04 =A0 =A0 =A00 =A0 =A0 =A00 = =A0 =A0 =A04 =A0 =A0 =A04 =A0 0.00% xinit /home/arundel/.xinitrc -- /home/a= rundel/.xserverrc :0 -a > 39953 =A0 1001 =A0 =A0 =A0 18 =A0 =A0 33 =A0 =A0 =A01 =A0 =A0 =A00 =A0 = =A0 =A00 =A0 =A0 =A01 =A0 0.00% /bin/sh /usr/bin/man top > =A01635 =A0 =A0 =A00 =A0 =A0 =A0 28 =A0 =A0 =A08 =A0 =A0 18 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 18 =A0 0.01% /usr/local/libexec/gam_server > =A01618 =A0 =A0 =A00 =A0 =A0 =A0 =A07 =A0 =A0 =A03 =A0 =A0 =A01 =A0 =A0 = =A00 =A0 =A0 =A02 =A0 =A0 =A03 =A0 0.00% /usr/libexec/getty Pc ttyv1 > =A01755 =A0 1001 =A0 =A0 =A0 =A03 =A0 =A0 =A00 =A0 =A0 =A01 =A0 =A0 =A00 = =A0 =A0 =A00 =A0 =A0 =A01 =A0 0.00% sh /home/arundel/.xinitrc > > ... is anybody else experiencing the same behavior? i also noticed a mass= ive > fault burst (~ 1500/sec), when closing chromium. > > cheers. > alex > > P.S.: i'm running HEAD on amd64 and the chromium port is @ 12.0.742.124. > _______________________________________________ > 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 Jul 25 01:02:44 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DD20106564A; Mon, 25 Jul 2011 01:02:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC86B8FC0C; Mon, 25 Jul 2011 01:02:39 +0000 (UTC) Received: by ywf7 with SMTP id 7so2373939ywf.13 for ; Sun, 24 Jul 2011 18:02:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yyCHukF8UIatlCdO0DbiY8GaUb4oRQvl29BX3ICMQXo=; b=Is1eUdCY8VnYEeOABKAhQ1QGFrABEFD+pD80dK0L2lx868ht8VUrveufVV2gOIgW2J lJ7k2cx3DbjEPkaHRIE5RlzzQ+XZZLJsRwnXwIBm8IL3UwTgi/k1xAMbtsJjs6LbHaRg zaqz7CTeWug2ZlnvVnYGh6M8tvD3Bli72TzVE= MIME-Version: 1.0 Received: by 10.150.252.6 with SMTP id z6mr3785125ybh.101.1311555759125; Sun, 24 Jul 2011 18:02:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Sun, 24 Jul 2011 18:02:39 -0700 (PDT) In-Reply-To: <4E2CBF89.7070104@freebsd.org> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> <4E2CBF89.7070104@freebsd.org> Date: Mon, 25 Jul 2011 09:02:39 +0800 X-Google-Sender-Auth: nP5uIoouVAynaIbLXbjder9oLKw Message-ID: From: Adrian Chadd To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Claude Buisson , freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 01:02:44 -0000 Something tells me that's a disaster waiting to happen. Eg, if something happens, and the installer disk gets corrupted, people may blame freebsd for being unstable, email questions to freebsd-* mailing lists asking why X doesn't work (only for it to work when the image is written out again), etc, etc. If it's going to double as a live image versus an installer than maybe have a boot option that mounts the root filesystem read-write (complete with some fingerprint that says that the image has been booted read-write at least once?) Adrian On 25 July 2011 08:57, Nathan Whitehorn wrote: > It does not. I had tried to match the behavior of the 8.x memsticks. It's= an > easy change in /usr/src/release/ARCH/make-memstick.sh to change it, howev= er. > -Nathan > > On 07/24/11 19:54, Adrian Chadd wrote: >> >> .. wait, the install-off-USB doesn't default to a read-only boot? >> >> >> >> Adrian >> >> On 25 July 2011 08:11, Claude Buisson =A0wrote: >>> >>> On 07/24/2011 23:33, Nathan Whitehorn wrote: >>>> >>>> On 07/24/11 16:29, eculp wrote: >>>>> >>>>> I have been hearing about a new installer but I obviously have not >>>>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>>>> and never really had a problem with understanding the installation >>>>> program. =A0There is always a first time, I guess. >>>>> >>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>>>> >>>>> When booting I seem to get a screen that makes me remember installer >>>>> screens of the 1980s. =A0(They were not exactly intuitive.) >>>>> >>>>> I somehow got the idea that the new installer was graphic. =A0Maybe >>>>> something like PCBsd that is not bad at all. =A0I use it on all our >>>>> employees computers. =A0Actually, after seeing this, I would love to >>>>> have the old installer back. =A0Is their an option for that? >>>>> >>>>> Does this new ASCII installer have a "how to" with a bit of >>>>> information on the flow of the installation. >>>>> >>>>> Thanks, >>>> >>>> Can you please describe what you didn't like about it, and what you >>>> would prefer be changed? "Reminiscent of the 1980s" is not really >>>> helpful, especially given that the new installer in fact looks very mu= ch >>>> like sysinstall, which you seemed to like. >>>> -Nathan >>> >>> Recently I installed a system from the "official" memory stick May >>> snapshot >>> (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks= : >>> >>> - the 1st thing I need to do is to configure the keyboard, as I am not = in >>> the >>> US. This is needed for an install, but also for using it as a live >>> system. >>> And >>> the keyboard configuration dialog is only a part of the installation >>> procedure. >>> >>> - the partition tool is too simple/rudimentary, compared to the old >>> sysinstall >>> dialog. I always want to have a total control of the partitions e.g. to >>> have >>> a >>> proper alignement. So one must use the shell escape or the live system, >>> which is >>> a regression. >>> >>> - extracting the tarballs lead to (cryptic) errors: I discovered the ha= rd >>> way >>> that I needed to execute a newfs. >>> >>> - I followed a succession of screens asking me to do the usual >>> configuration >>> steps (hostname, clock, network - IPv4 only ?? -, users) and at the end= I >>> get >>> back a screen asking me if a wanted to do the steps I had done just >>> before... >>> >>> - booting the installed system, I found that the hostname disappeared, >>> the >>> keyboard was not configured, nor the network, and so on >>> >>> - during the whole process the screen was scrambled by the occurence of= a >>> number >>> of LORs displayed on top of the dialogs/messages of the installer. >>> >>> - the file system of the installer/live system seems to be too small, >>> leading to >>> a number of "system full" messages as soon a few files are written to i= t. >>> >>> So the sole value added of the installer was the extraction of the >>> tarballs.. >>> >>> It seems that (on a memory stick which is writable) that every aborted >>> attempt >>> to do a configuration step leaves a "trace" in some files used by the >>> installer, >>> which is able to show it (e.g. the hostname) at the following attempts, >>> but >>> without garantee that it will effectively be used. >>> >>> (On the other hand, the advantage of the memory stick is that the syste= m >>> on >>> it >>> can be configured at will) >>> >>> Referring to a thread I found recently a propos the documentation on th= e >>> install >>> media, I also want to say that a proper installer must be able to do it= s >>> work >>> without any Internet connectivity. There exist systems which are not >>> connected, >>> and networks without any communication with the Internet. >>> >>> Claude Buisson >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" > > From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 01:03:16 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A64CB1065672; Mon, 25 Jul 2011 01:03:16 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 35EDB8FC17; Mon, 25 Jul 2011 01:03:16 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id CD0B0E62C1; Mon, 25 Jul 2011 02:03:14 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=tmslXdQD1lPO QbWgnjO1X+SiClk=; b=T2fh8JtH2+X121vjBj5G15LFqyR+SsYBWNAIGuv5qYDm cyFboeQl/tH/Irp+btg/WT3wbxUwrQ+wzftdVzyGj4lzsh0Lrh5alYM53ALTSc5L jAE9Px7lTe8hRKXHRCIT1NGz3PlC3X0s6F0df+xg/tmh/RNQF99LC39RmTsW9MI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=pxdLn/ zzoCy/n23K/40si4D93HCOlxOjjNRk6wBonRvdSROqD5ETg6vlZLv+CuBQEm9vLw Vkhzlq+6ac+GaJUSKntJzyuj3hzTZZPVMCQnDETLCpDRIPriu53347v+ywEV1kii 0yA+dYjXSaE03tZ1QME8FxqrJAnnY3j6n1qhk= Received: from [192.168.1.64] (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 9CE10E62BF; Mon, 25 Jul 2011 02:03:14 +0100 (BST) Message-ID: <4E2CC0D0.4090309@cran.org.uk> Date: Mon, 25 Jul 2011 02:03:12 +0100 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Ron McDowell References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> In-Reply-To: <4E2CA4A7.7020100@fuzzwad.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , Nathan Whitehorn , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 01:03:16 -0000 On 25/07/2011 00:03, Ron McDowell wrote: > 1) no "back" button/selection/mechanism on each screen. Rebooting > because I fat-fingered something on the previous screen is, well, > unacceptable. > 2) no "minimal" install. Most of my installs are single- or few-task > servers where I need a base os and a couple ports. > 3) I see no "post-install" uses on the new one. Sysinstall could be > used on an up-and-running system to do everything from adding a user > to changing a nameserver and more. Another potential problem is that the new version of libdialog that the new installer uses changes the way navigation is done: on Linux and in the previous version on FreeBSD it's possible to press to change focus to the buttons and different UI elements. That doesn't work any more. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 01:03:29 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2DC91065746 for ; Mon, 25 Jul 2011 01:03:28 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from adsum.doit.wisc.edu (adsum.doit.wisc.edu [144.92.197.210]) by mx1.freebsd.org (Postfix) with ESMTP id B45498FC0A for ; Mon, 25 Jul 2011 01:03:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOV007006XSSW00@smtpauth1.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 24 Jul 2011 20:03:28 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOV00MLM6XQSJ10@smtpauth1.wiscmail.wisc.edu>; Sun, 24 Jul 2011 20:03:27 -0500 (CDT) Date: Sun, 24 Jul 2011 20:03:26 -0500 From: Nathan Whitehorn In-reply-to: <4E2CA4A7.7020100@fuzzwad.org> To: Ron McDowell Message-id: <4E2CC0DE.9050802@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-11, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.25.5414, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: freebsd-current , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 01:03:29 -0000 On 07/24/11 18:03, Ron McDowell wrote: > Nathan Whitehorn wrote: >> On 07/24/11 16:29, eculp wrote: >>> I have been hearing about a new installer but I obviously have not >>> payed enough attention, I am afraid. I started running freebsd at >>> 2.0 and never really had a problem with understanding the >>> installation program. There is always a first time, I guess. >>> >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>> >>> When booting I seem to get a screen that makes me remember installer >>> screens of the 1980s. (They were not exactly intuitive.) >>> >>> I somehow got the idea that the new installer was graphic. Maybe >>> something like PCBsd that is not bad at all. I use it on all our >>> employees computers. Actually, after seeing this, I would love to >>> have the old installer back. Is their an option for that? >>> >>> Does this new ASCII installer have a "how to" with a bit of >>> information on the flow of the installation. >>> >>> Thanks, >> >> Can you please describe what you didn't like about it, and what you >> would prefer be changed? "Reminiscent of the 1980s" is not really >> helpful, especially given that the new installer in fact looks very >> much like sysinstall, which you seemed to like. >> -Nathan >> > > I'll have to agree with the original poster. I have no problem with > the look and feel of the new installer, but when functionality that > WAS there is now gone, that's a problem. My two, make that three, > biggest gripes are: > > 1) no "back" button/selection/mechanism on each screen. Rebooting > because I fat-fingered something on the previous screen is, well, > unacceptable. This is why almost all screens have a "cancel" button. You can also restart the installer by control-C at any time without rebooting. Providing an actual back button is quite tricky and not necessarily always well defined in behavior, since the installed system will then be in an inconsistent state at which previous steps cannot necessarily be repeated. For those steps where that is not true, they can be reentered from the menu at the end in case of fat-fingering. > 2) no "minimal" install. Most of my installs are single- or few-task > servers where I need a base os and a couple ports. I'm not sure what you mean by this. You can install just a kernel and the base system by deselecting the ports tree, games, and docs when you select which system components to install. > 3) I see no "post-install" uses on the new one. Sysinstall could be > used on an up-and-running system to do everything from adding a user > to changing a nameserver and more. > This is deliberate. This particular feature of sysinstall made it almost unmaintainable, especially as those features slowly bitrotted. We have very good system configuration utilities already -- there is no need to duplicate them in the installer, especially when it makes maintaining and improving that installer more difficult. -Nathan From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 01:04:23 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79536106564A; Mon, 25 Jul 2011 01:04:23 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 48EA88FC0C; Mon, 25 Jul 2011 01:04:22 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOV005006ZAX600@smtpauth3.wiscmail.wisc.edu>; Sun, 24 Jul 2011 20:04:22 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOV001OJ6Z87U10@smtpauth3.wiscmail.wisc.edu>; Sun, 24 Jul 2011 20:04:21 -0500 (CDT) Date: Sun, 24 Jul 2011 20:04:20 -0500 From: Nathan Whitehorn In-reply-to: To: Adrian Chadd Message-id: <4E2CC114.1060606@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-10, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.25.5414, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> <4E2CBF89.7070104@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: Claude Buisson , freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 01:04:23 -0000 Yes, I agree. I'll ask re@ to change it. -Nathan On 07/24/11 20:02, Adrian Chadd wrote: > Something tells me that's a disaster waiting to happen. Eg, if > something happens, and the installer disk gets corrupted, people may > blame freebsd for being unstable, email questions to freebsd-* mailing > lists asking why X doesn't work (only for it to work when the image is > written out again), etc, etc. > > If it's going to double as a live image versus an installer than maybe > have a boot option that mounts the root filesystem read-write > (complete with some fingerprint that says that the image has been > booted read-write at least once?) > > > > Adrian > > On 25 July 2011 08:57, Nathan Whitehorn wrote: >> It does not. I had tried to match the behavior of the 8.x memsticks. It's an >> easy change in /usr/src/release/ARCH/make-memstick.sh to change it, however. >> -Nathan >> >> On 07/24/11 19:54, Adrian Chadd wrote: >>> .. wait, the install-off-USB doesn't default to a read-only boot? >>> >>> >>> >>> Adrian >>> >>> On 25 July 2011 08:11, Claude Buisson wrote: >>>> On 07/24/2011 23:33, Nathan Whitehorn wrote: >>>>> On 07/24/11 16:29, eculp wrote: >>>>>> I have been hearing about a new installer but I obviously have not >>>>>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>>>>> and never really had a problem with understanding the installation >>>>>> program. There is always a first time, I guess. >>>>>> >>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>>>>> >>>>>> When booting I seem to get a screen that makes me remember installer >>>>>> screens of the 1980s. (They were not exactly intuitive.) >>>>>> >>>>>> I somehow got the idea that the new installer was graphic. Maybe >>>>>> something like PCBsd that is not bad at all. I use it on all our >>>>>> employees computers. Actually, after seeing this, I would love to >>>>>> have the old installer back. Is their an option for that? >>>>>> >>>>>> Does this new ASCII installer have a "how to" with a bit of >>>>>> information on the flow of the installation. >>>>>> >>>>>> Thanks, >>>>> Can you please describe what you didn't like about it, and what you >>>>> would prefer be changed? "Reminiscent of the 1980s" is not really >>>>> helpful, especially given that the new installer in fact looks very much >>>>> like sysinstall, which you seemed to like. >>>>> -Nathan >>>> Recently I installed a system from the "official" memory stick May >>>> snapshot >>>> (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: >>>> >>>> - the 1st thing I need to do is to configure the keyboard, as I am not in >>>> the >>>> US. This is needed for an install, but also for using it as a live >>>> system. >>>> And >>>> the keyboard configuration dialog is only a part of the installation >>>> procedure. >>>> >>>> - the partition tool is too simple/rudimentary, compared to the old >>>> sysinstall >>>> dialog. I always want to have a total control of the partitions e.g. to >>>> have >>>> a >>>> proper alignement. So one must use the shell escape or the live system, >>>> which is >>>> a regression. >>>> >>>> - extracting the tarballs lead to (cryptic) errors: I discovered the hard >>>> way >>>> that I needed to execute a newfs. >>>> >>>> - I followed a succession of screens asking me to do the usual >>>> configuration >>>> steps (hostname, clock, network - IPv4 only ?? -, users) and at the end I >>>> get >>>> back a screen asking me if a wanted to do the steps I had done just >>>> before... >>>> >>>> - booting the installed system, I found that the hostname disappeared, >>>> the >>>> keyboard was not configured, nor the network, and so on >>>> >>>> - during the whole process the screen was scrambled by the occurence of a >>>> number >>>> of LORs displayed on top of the dialogs/messages of the installer. >>>> >>>> - the file system of the installer/live system seems to be too small, >>>> leading to >>>> a number of "system full" messages as soon a few files are written to it. >>>> >>>> So the sole value added of the installer was the extraction of the >>>> tarballs.. >>>> >>>> It seems that (on a memory stick which is writable) that every aborted >>>> attempt >>>> to do a configuration step leaves a "trace" in some files used by the >>>> installer, >>>> which is able to show it (e.g. the hostname) at the following attempts, >>>> but >>>> without garantee that it will effectively be used. >>>> >>>> (On the other hand, the advantage of the memory stick is that the system >>>> on >>>> it >>>> can be configured at will) >>>> >>>> Referring to a thread I found recently a propos the documentation on the >>>> install >>>> media, I also want to say that a proper installer must be able to do its >>>> work >>>> without any Internet connectivity. There exist systems which are not >>>> connected, >>>> and networks without any communication with the Internet. >>>> >>>> Claude Buisson >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 01:08:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 368C0106567A for ; Mon, 25 Jul 2011 01:08:07 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 082518FC15 for ; Mon, 25 Jul 2011 01:08:06 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOV0060075G8I00@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Sun, 24 Jul 2011 20:08:06 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOV001SO75E7U10@smtpauth3.wiscmail.wisc.edu>; Sun, 24 Jul 2011 20:08:03 -0500 (CDT) Date: Sun, 24 Jul 2011 20:08:02 -0500 From: Nathan Whitehorn In-reply-to: <4E2CC0D0.4090309@cran.org.uk> To: Bruce Cran Message-id: <4E2CC1F2.2070607@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-13, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.25.10022, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2CC0D0.4090309@cran.org.uk> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: freebsd-current , Ron McDowell , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 01:08:07 -0000 On 07/24/11 20:03, Bruce Cran wrote: > On 25/07/2011 00:03, Ron McDowell wrote: >> 1) no "back" button/selection/mechanism on each screen. Rebooting >> because I fat-fingered something on the previous screen is, well, >> unacceptable. >> 2) no "minimal" install. Most of my installs are single- or few-task >> servers where I need a base os and a couple ports. >> 3) I see no "post-install" uses on the new one. Sysinstall could be >> used on an up-and-running system to do everything from adding a user >> to changing a nameserver and more. > > Another potential problem is that the new version of libdialog that > the new installer uses changes the way navigation is done: on Linux > and in the previous version on FreeBSD it's possible to press to > change focus to the buttons and different UI elements. That doesn't > work any more. > It's a change from before, but a normalization with respect to most Linux distributions, since we are now using the same dialog as, e.g., Debian and Ubuntu. -Nathan From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 02:18:23 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD44C106564A; Mon, 25 Jul 2011 02:18:23 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 399498FC12; Mon, 25 Jul 2011 02:18:23 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 54705E62C1; Mon, 25 Jul 2011 03:18:22 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=rHA23GaMbjAP qGcZo/u1CUmaPBs=; b=Sx656XaaHrPE9u3hHlXY9be+aarKAQvGkKl+sBCE36E8 q9I/uvG4VgAzb0WxtpdBRqBbKLw+0RHrdzkQU+SUf6VybwOHlgJziSarEfh6MXch CYXYGOnTuDzMCXM3uGM1kBGu5NfT2Kiu41oCMtrqfqHuyUmBIphf/bdK3fbEy+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=aO7rse nUvsUMX4pDxXGA3J548nNSm7tEdYJTWpW08iuOS5P8GOGg8pavRviPv7uEW1TlX3 dPold0GPQVt1Q3BmjxtyZsEL9qRgBcy6ek8cier8WnGGI98ff2D5OFnKqVOyPrQk hn5ISqkKB+QsuowbY0/85YryIW2XB5AkVaZOA= Received: from [192.168.1.64] (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 138D6E62B5; Mon, 25 Jul 2011 03:18:22 +0100 (BST) Message-ID: <4E2CD26B.7090503@cran.org.uk> Date: Mon, 25 Jul 2011 03:18:19 +0100 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2CC0D0.4090309@cran.org.uk> <4E2CC1F2.2070607@freebsd.org> In-Reply-To: <4E2CC1F2.2070607@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , Ron McDowell , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 02:18:23 -0000 On 25/07/2011 02:08, Nathan Whitehorn wrote: > On 07/24/11 20:03, Bruce Cran wrote: >> On 25/07/2011 00:03, Ron McDowell wrote: >>> 1) no "back" button/selection/mechanism on each screen. Rebooting >>> because I fat-fingered something on the previous screen is, well, >>> unacceptable. >>> 2) no "minimal" install. Most of my installs are single- or >>> few-task servers where I need a base os and a couple ports. >>> 3) I see no "post-install" uses on the new one. Sysinstall could be >>> used on an up-and-running system to do everything from adding a user >>> to changing a nameserver and more. >> >> Another potential problem is that the new version of libdialog that >> the new installer uses changes the way navigation is done: on Linux >> and in the previous version on FreeBSD it's possible to press >> to change focus to the buttons and different UI elements. That >> doesn't work any more. >> > > It's a change from before, but a normalization with respect to most > Linux distributions, since we are now using the same dialog as, e.g., > Debian and Ubuntu. The Debian 6.0.2.1 installer appears to use the old navigation method, and SuSE 11.4 seems to too. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 05:01:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A194F106566B for ; Mon, 25 Jul 2011 05:01:45 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4D1F28FC14 for ; Mon, 25 Jul 2011 05:01:44 +0000 (UTC) Received: by gwb15 with SMTP id 15so2861789gwb.13 for ; Sun, 24 Jul 2011 22:01:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KgeYmol9TsH+GjZDMnWXqd6sbaYnpu0gxYUdU3wMEYM=; b=Iq2aNYdm8yH4PEC969g7Xr2/qTDSdC2VSAn766pIoRO9x3VywEWZ784F/COJ8dKzn4 Tm9tFUw2VcN14iHSLxLNKJWPACG1KI7A0ivQwIbo5c0hpU18OxpjjlQgKjj3GJk16kkm xPmmdNVTjF/smJcbixX/jH3otwEUqxm3N3/G4= MIME-Version: 1.0 Received: by 10.90.249.31 with SMTP id w31mr3955400agh.202.1311570104355; Sun, 24 Jul 2011 22:01:44 -0700 (PDT) Received: by 10.90.209.12 with HTTP; Sun, 24 Jul 2011 22:01:44 -0700 (PDT) In-Reply-To: <4E2CA4A7.7020100@fuzzwad.org> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> Date: Sun, 24 Jul 2011 22:01:44 -0700 Message-ID: From: Freddie Cash To: Ron McDowell Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current , Nathan Whitehorn , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 05:01:45 -0000 On Sunday, July 24, 2011, Ron McDowell wrote: >> > > I'll have to agree with the original poster. I have no problem with the look and feel of the new installer, but when functionality that WAS there is now gone, that's a problem. My two, make that three, biggest gripes are: > > 1) no "back" button/selection/mechanism on each screen. Rebooting because I fat-fingered something on the previous screen is, well, unacceptable. > 2) no "minimal" install. Most of my installs are single- or few-task servers where I need a base os and a couple ports. The nice thing about bsdinstall is that every install is identical. It's basically just dumping an image file to disk. > 3) I see no "post-install" uses on the new one. Sysinstall could be used on an up-and-running system to do everything from adding a user to changing a nameserver and more. Thank goodness. The worst thing about sysinstall was that it tried to be a Swiss Army knife doing everything, yet not doing any one thing well. It made a royal mess of rc.conf if you tried to use it to configure a system. Usually the first time someone mentions they use it for post-install configuration, the recommendation is to stop doing that! An os installer should do just that: install the os and nothing else. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 05:23:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F35E106564A; Mon, 25 Jul 2011 05:23:30 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id D4F058FC17; Mon, 25 Jul 2011 05:23:29 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p6P4lr49009751; Sun, 24 Jul 2011 22:47:53 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p6P4lrS6009748; Sun, 24 Jul 2011 22:47:53 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 24 Jul 2011 22:47:53 -0600 (MDT) From: Warren Block To: Nathan Whitehorn In-Reply-To: <4E2C8FBE.7040003@freebsd.org> Message-ID: References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sun, 24 Jul 2011 22:47:53 -0600 (MDT) Cc: freebsd-current , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 05:23:30 -0000 On Sun, 24 Jul 2011, Nathan Whitehorn wrote: > Can you please describe what you didn't like about it, and what you would > prefer be changed? "Reminiscent of the 1980s" is not really helpful, > especially given that the new installer in fact looks very much like > sysinstall, which you seemed to like. For myself, two things jumped out: 1. The use of tab and enter in the dialogs is different enough to be a problem, particularly when other dialogs like port options still work as before. 2. The disk setup screen is unclear, or unintuitive, at least for me. For reference, here's a copy: Please review the disk setup. When complete, press the Exit button. ad0 8.7 GB GPT ad0p1 64 KB freebsd-boot ad0p2 8.3 GB freebsd-ufs / ad0p3 446 MB freebsd-swap none < Auto > < Exit > 1. Extending the highlight bar the whole width of the window would help to show what is being operated on. 2. The options don't always really apply. Create when ad0 is highlighted leads the user to think they can create a new device, like ad1. But it will really create another partition. Delete on ad0 deletes all the partitions, not ad0. No warning, either. 3. Tab in the Modify partition window doesn't go to the next field, but to the OK button. Backtab closes the window instead of going back a field. 4. "The partition scheme requires a boot partition". But there's one already there. Possibly this is a bug. ad0 8.7 GB GPT ad0p1 64 KB freebsd-boot ad0p2 8.3 GB freebsd-ufs / ad0p3 446 MB freebsd-swap none ad0p4 64 KB freebsd-boot ad0p5 926 KB freebsd-ufs / 5. This one's about method rather than user interface... Auto creation should probably follow the standard of separate partitions for /, swap, /var, /tmp, and /usr. Swap at the end of the disk will be slower, and combining all the filesystems is a big change. From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 06:23:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F336106566C for ; Mon, 25 Jul 2011 06:23:30 +0000 (UTC) (envelope-from martin@sugioarto.com) Received: from mailserv.regfish.com (mailserv.regfish.com [79.140.61.33]) by mx1.freebsd.org (Postfix) with ESMTP id AB82A8FC12 for ; Mon, 25 Jul 2011 06:23:29 +0000 (UTC) Received: (qmail 29536 invoked from network); 25 Jul 2011 05:56:48 -0000 Received: from pd9ec0e3c.dip0.t-ipconnect.de (HELO yuni.sugioarto.com) (46959-0001@[217.236.14.60]) (envelope-sender ) by mailserv.regfish.com (qmail-ldap-1.03) with SMTP for ; 25 Jul 2011 05:56:48 -0000 Received: from zelda.sugioarto.com (zelda.sugioarto.com [192.168.0.12]) by yuni.sugioarto.com (Postfix) with ESMTP id 0336F1BAC57; Mon, 25 Jul 2011 07:56:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sugioarto.com; s=mail; t=1311573406; bh=CPZuNgeuelgElOtaxmuPHrpYCZfgW9W++wyNzCSes5s=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: Mime-Version:Content-Type; b=V6eTlE2W8FPbCe1aY8V+DigcUG17IDK/keMpigkvqyPAW/LJIfF4Xk3AcndTA7zGB foEMqndaRae/0bDo8ESfP3azhNtqOLRiDj7ixjzAH7RMsl9qPkiQPBFB2CoHu4PnTJ XCglSl81h2W/c2/fHwYofxYu8f9JzpKHLIGbaNv0= Date: Mon, 25 Jul 2011 07:56:32 +0200 From: Martin Sugioarto To: Nathan Whitehorn Message-ID: <20110725075632.0a482641@zelda.sugioarto.com> In-Reply-To: <4E2CC1F2.2070607@freebsd.org> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2CC0D0.4090309@cran.org.uk> <4E2CC1F2.2070607@freebsd.org> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/9l3BBQH7vZkYA_ckJRYJ5aR"; protocol="application/pgp-signature" Cc: Bruce Cran , freebsd-current , Ron McDowell , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 06:23:30 -0000 --Sig_/9l3BBQH7vZkYA_ckJRYJ5aR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Sun, 24 Jul 2011 20:08:02 -0500 schrieb Nathan Whitehorn : > It's a change from before, but a normalization with respect to most=20 > Linux distributions, since we are now using the same dialog as, e.g.,=20 > Debian and Ubuntu. > -Nathan Hi, yes. And I want to thank you (and everyone) for this change in libdialog. This was something I immediately liked especially while configuring ports. It saves many key presses and is perfectly logical and provides more usability. I've done a CURRENT installation, too. And it looks like you did a good job. I've liked what I've seen so far. I have one request though: Please provide more recent snapshots for more platforms. It's very difficult to find an acceptable one. It would be nice when you get some early feedback from users instead of making a typical dot-zero release that needs to be fixed and no one will be able to accept. -- Martin --Sig_/9l3BBQH7vZkYA_ckJRYJ5aR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) Comment: Anständige Signaturen und Verschlüsselung gibt es nur mit GNUpg Comment: und nicht mit De-Mail. iQIcBAEBAgAGBQJOLQWdAAoJEF8wvLx/5p/7jPgP/iQU5cKC0xr4dPoe00RqGVxc 1dvc0a6avN/KiHsqugCLZ2nATj9lEYHihVaLySdrjUwpVo++P6T4ddSqblf/75bV w/J6QR0fUjzgsY44JyaEG/dVB2C9odEtn8SK0jGVWuE09dgNe36LHaILe354cinT ZFy/eMyDSIEfg+k63bppcmqpgZYdkCE3JDtDVMSDotblYE2sOZ99JhILr50qN5UM ZgpF2kxUuc9a5nA+qamzyLrIF3MKp0fV2Ptt81xmpJKbr82MB+3JhHUf5ijF3Tln sGjk/ZhgfPfjUH/oHiRTz1lc7AL5SsWf9YrqfbFs8r2EsgGq09ftFNhwsPsYbqLG 8RVPiDkiVetccpc7KeUB0wk5FpAPCsGIBU8cRqZUEkp9AHnNkdWyw2bYnnqAx+ox 1F02duLrwVzgLYmrr1emxdUAiv72BQyzsMN4+stBJWvfWAru8kL8UFTcBp4OGwqQ 8Y9gPOBpZdHPHHVRWs7SHVnUzwBwa2c0dHb4usuhAYkclrmxP1W1ba0XDcADkvdr q1N/Szlas9pRNm9E/B6yrNE3B6zUK3X54SzMqwo9gHHQzK+tpqORfA7dn42u/brX qQyWLE2pLCGLhfOl+OY8g0Q8acG1Gzj+2YhFmD/C7p6eD1K2rLVZO9t8fCFzhwKW VB5NE8xcnlRPlTan8zV2 =/D0M -----END PGP SIGNATURE----- --Sig_/9l3BBQH7vZkYA_ckJRYJ5aR-- From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 06:51:15 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C171065670; Mon, 25 Jul 2011 06:51:15 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id 401428FC1D; Mon, 25 Jul 2011 06:51:15 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 50633E62C1; Mon, 25 Jul 2011 07:51:14 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=cFBO8hwoabPM gvrDODkMQWas4dk=; b=Qi7OT61KXs6Qhzh4hTzZ4zQrNdLX/UX50EiqSCVZrsXa oTLOIfV+Bse6nFjRwDloGpcCD/CJz+7WS3QLeUNNbZGF+6u/F41AlB45RGNhal9O 8wpSC5CygvcFrn99GFd695uKIobc4/12lGiLHrUYv0VFh8ciZ8DApDILXNpJnW0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=EJ7NAl UQwM1iMCa1mtcA2o2YHm6/VJJbIDjoaRBcaVuvoUKxDT2L4659+3bvNZR3f+Pusn ecvhkSpHvc23M0alpd03USFVFRHIdDhbbo+MooOHWfk8UzFspwGRvXlKMcEFMBR0 I+g3CJS2Qnsj/6x4KhiZPkWe6kHVJ/PlRXyRI= Received: from [192.168.1.64] (188-222-18-231.zone13.bethere.co.uk [188.222.18.231]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 18E0BE62B5; Mon, 25 Jul 2011 07:51:14 +0100 (BST) Message-ID: <4E2D125F.6040909@cran.org.uk> Date: Mon, 25 Jul 2011 07:51:11 +0100 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Freddie Cash References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , Ron McDowell , Nathan Whitehorn , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 06:51:15 -0000 On 25/07/2011 06:01, Freddie Cash wrote: > Thank goodness. The worst thing about sysinstall was that it tried to > be a Swiss Army knife doing everything, yet not doing any one thing > well. It made a royal mess of rc.conf if you tried to use it to > configure a system. Usually the first time someone mentions they use > it for post-install configuration, the recommendation is to stop doing > that! An os installer should do just that: install the os and nothing > else. I tend to disagree with this. For people unfamiliar with FreeBSD using it as a systems administration tool can be really useful, at least until they understand where all the various configuration files are and how they work. Having recently switched to opensuse from Ubuntu I know I find the YaST tool incredibly useful, and probably wouldn't have continued using SuSE if it hadn't been there. Its installer mode is one of the better installers I've come across, and lets you fine-tune the configuration. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 07:21:02 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id DFD6A1065670; Mon, 25 Jul 2011 07:21:02 +0000 (UTC) Date: Mon, 25 Jul 2011 07:21:02 +0000 From: Alexander Best To: Adrian Chadd Message-ID: <20110725072102.GA24938@freebsd.org> References: <20110724212544.GA57733@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: freebsd-chromium@freebsd.org, freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 07:21:03 -0000 On Mon Jul 25 11, Adrian Chadd wrote: > Is it perhaps doing disk IO using mmap? how can i check, whether that's the case or not? > > > > adrian > > On 25 July 2011 05:25, Alexander Best wrote: > > hi there, > > > > i noticed that chromium, expecially in combination with nspluginwrapper and > > flash, is causing a lot of I/O faults. i ran 'top -mio -I -n 999999' and after > > only ~ 4 hours of running chromium (most of the time not loading any new > > pages), i got the following data: > > > > last pid: 39976; load averages: 0.37, 0.26, 0.19 up 3+02:38:30 23:15:26 > > 72 processes: 2 running, 70 sleeping > > > > Mem: 755M Active, 662M Inact, 447M Wired, 51M Cache, 212M Buf, 45M Free > > Swap: 10G Total, 159M Used, 10G Free, 1% Inuse > > > > > > PID UID VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND > > 39908 1001 7409 51112 0 0 4 4 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > > 39605 1001 598315 233115 11 0 3 14 0.01% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > > 1752 1001 22292378 29644471 138 0 696 834 0.38% /usr/local/bin/Xorg -nolisten inet6 > > 1756 1001 1551733 2002630 480 0 455 935 0.43% /usr/local/bin/awesome > > 39140 1001 10672291 1240670 0 0 6522 6522 2.97% chrome: --type=zygote (chrome) > > 39116 1001 5967965 3237798 8249 20401 136394 165044 75.14% chromium-browser: (chrome) > > 39138 1001 6436642 994546 0 0 1785 1785 0.81% chrome: --type=zygote (chrome) > > 39135 1001 4334272 169320 0 0 1723 1723 0.78% chrome: --type=zygote (chrome) > > 39133 1001 4321593 169574 1 0 1717 1718 0.78% chrome: --type=zygote (chrome) > > 39132 1001 4292029 164913 6 0 1766 1772 0.81% chrome: --type=zygote (chrome) > > 39137 1001 4152284 139225 1 0 1762 1763 0.80% chrome: --type=zygote (chrome) > > 1629 560 356784 70399 25 0 40 65 0.03% /usr/local/sbin/hald > > 1767 1001 355603 87998 32 0 0 32 0.01% /usr/local/libexec/gam_server > > 39144 1001 2659919 409841 0 0 3578 3578 1.63% chrome: --type=plugin --plugin-path=/usr/home/arundel/.mozill > > 10217 1001 472898 258689 601 1 8 610 0.28% /usr/local/bin/musicpd /usr/local/etc/musicpd.conf > > 39121 1001 552140 44286 1 0 181 182 0.08% chrome: --type=zygote (chrome) > > 39358 1001 103237 20357 223 1479 211 1913 0.87% /usr/local/bin/sakura > > 39119 1001 91173 58899 2 0 14795 14797 6.74% chrome: --type=zygote (chrome) > > 39846 1001 275524 51575 0 0 7085 7085 3.23% chrome: --type=zygote (chrome) > > 39120 1001 60470 18204 0 0 22 22 0.01% chrome: --type=zygote (chrome) > > 1538 0 53910 6390 0 0 1 1 0.00% sendmail: accepting connections (sendmail) > > 39363 1001 33822 9157 1 1113 3 1117 0.51% /usr/local/bin/sakura > > 39805 1001 55542 43060 0 0 2787 2787 1.27% chrome: --type=zygote (chrome) > > 39117 1001 2935 13041 156 0 155 311 0.14% chromium-browser: (chrome) > > 39902 1001 43829 31005 0 0 4477 4477 2.04% chrome: --type=zygote (chrome) > > 362 0 28923 1878 1 0 5 6 0.00% /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant > > 1548 0 5122 672 11 0 0 11 0.01% /usr/sbin/cron -s > > 1217 0 13118 676 21 39 0 60 0.03% /usr/sbin/syslogd -s > > 39907 1001 16179 6366 0 0 2 2 0.00% /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin --plugi > > 39118 1001 976 716 90 0 81 171 0.08% chrome: --type=zygote (chrome) > > 1345 0 1362 201 1 0 2 3 0.00% /usr/local/sbin/smartd -p /var/run/smartd.pid -c /usr/local/et > > 1685 1001 180 22 52 0 30 82 0.04% -zsh (zsh) > > 1458 65534 512 62 2 0 0 2 0.00% /usr/local/bin/mpdscribble --daemon-user nobody > > 39360 1001 394 287 14 0 5 19 0.01% /usr/local/bin/zsh > > 1636 0 184 181 8 0 0 8 0.00% hald-runner > > 39365 1001 98 113 18 0 0 18 0.01% /usr/local/bin/zsh > > 1633 0 648 133 29 0 5 34 0.02% /usr/local/libexec/polkitd > > 1631 0 608 71 15 0 24 39 0.02% /usr/local/sbin/console-kit-daemon --no-daemon > > 39931 1001 53 81 1 0 1 2 0.00% /usr/local/bin/zsh > > 1713 1001 21 16 0 0 2 2 0.00% ssh-agent > > 1352 556 176 125 2 0 0 2 0.00% /usr/local/bin/dbus-daemon --system > > 1494 0 62 17 45 0 14 59 0.03% /usr/local/sbin/cupsd -C /usr/local/etc/cups/cupsd.conf > > 1733 1001 20 0 1 0 0 1 0.00% /bin/sh /usr/local/bin/startx > > 1617 0 33 15 7 0 0 7 0.00% login [pam] (login) > > 1751 1001 16 4 0 0 4 4 0.00% xinit /home/arundel/.xinitrc -- /home/arundel/.xserverrc :0 -a > > 39953 1001 18 33 1 0 0 1 0.00% /bin/sh /usr/bin/man top > > 1635 0 28 8 18 0 0 18 0.01% /usr/local/libexec/gam_server > > 1618 0 7 3 1 0 2 3 0.00% /usr/libexec/getty Pc ttyv1 > > 1755 1001 3 0 1 0 0 1 0.00% sh /home/arundel/.xinitrc > > > > ... is anybody else experiencing the same behavior? i also noticed a massive > > fault burst (~ 1500/sec), when closing chromium. > > > > cheers. > > alex > > > > P.S.: i'm running HEAD on amd64 and the chromium port is @ 12.0.742.124. > > _______________________________________________ > > 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 Jul 25 07:57:33 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22AAA106564A; Mon, 25 Jul 2011 07:57:32 +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 013538FC0C; Mon, 25 Jul 2011 07:57:31 +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 KAA11552; Mon, 25 Jul 2011 10:57:22 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QlG2T-000GaX-PH; Mon, 25 Jul 2011 10:57:21 +0300 Message-ID: <4E2D21DE.5070201@FreeBSD.org> Date: Mon, 25 Jul 2011 10:57:18 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Warren Block References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current , Nathan Whitehorn Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 07:57:33 -0000 on 25/07/2011 07:47 Warren Block said the following: > 2. The options don't always really apply. Create when ad0 is highlighted leads > the user to think they can create a new device, like ad1. But it will really > create another partition. Delete on ad0 deletes all the partitions, not ad0. > No warning, either. Are you sure about this one? I have never expected that any installer would be able to create or delete hardware (a hard disk) in my computer. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 08:41:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD7CA106566B for ; Mon, 25 Jul 2011 08:41:25 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 028F38FC08 for ; Mon, 25 Jul 2011 08:41:24 +0000 (UTC) Received: (qmail invoked by alias); 25 Jul 2011 08:41:23 -0000 Received: from g229210208.adsl.alicedsl.de (EHLO apollo.emma.line.org) [92.229.210.208] by mail.gmx.net (mp018) with SMTP; 25 Jul 2011 10:41:23 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX19Q/lxy7ttQLkSLMRjKDJvinLeRTtdDeg2dV+Sq8I CqWiVO6fYKzJ80 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id 90D8F23CE50 for ; Mon, 25 Jul 2011 10:41:22 +0200 (CEST) Message-ID: <4E2D2C32.5010602@gmx.de> Date: Mon, 25 Jul 2011 10:41:22 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Mnenhy/0.8.3 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> In-Reply-To: <20110725072102.GA24938@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 08:41:25 -0000 Am 25.07.2011 09:21, schrieb Alexander Best: > On Mon Jul 25 11, Adrian Chadd wrote: >> Is it perhaps doing disk IO using mmap? > > how can i check, whether that's the case or not? Use truss(1) for instance. However, unless there are *practical* problems, a high number of page faults is not an indication for problems. Although it may sound scary, page faults are a feature of the memory management. From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 10:00:35 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7180C1065670 for ; Mon, 25 Jul 2011 10:00: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 BA6C88FC13 for ; Mon, 25 Jul 2011 10:00: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 NAA13998; Mon, 25 Jul 2011 13:00:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QlHxd-000GfE-7N; Mon, 25 Jul 2011 13:00:29 +0300 Message-ID: <4E2D3EBB.9060508@FreeBSD.org> Date: Mon, 25 Jul 2011 13:00:27 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Steve Kargl References: <20110706170132.GA68775@troutmask.apl.washington.edu> <5080.1309971941@critter.freebsd.dk> <20110706180001.GA69157@troutmask.apl.washington.edu> <4E14A54A.4050106@freebsd.org> <4E155FF9.5090905@FreeBSD.org> <20110707151440.GA75537@troutmask.apl.washington.edu> <4E160C2F.8020001@FreeBSD.org> <20110707200845.GA77049@troutmask.apl.washington.edu> <4E1B1198.6090308@FreeBSD.org> <20110711161654.GA97361@troutmask.apl.washington.edu> <4E1C003B.4090604@FreeBSD.org> In-Reply-To: <4E1C003B.4090604@FreeBSD.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 10:00:35 -0000 on 12/07/2011 11:05 Andriy Gapon said the following: > I think that the best thing you can further provide (as objective evidence for > the problem at hand) is ktr(4) traces for at least KTR_SCHED mask. Perhaps you > even already have them from your previous sessions with Jeff. > > P.S. This is not a promise to actually debug this issue based on the traces :-) So do you have an opportunity to provide this kind of information? Actually I would like KTR_SCHED|KTR_INTR|KTR_PROC|KTR_SYSC mask. Also, sysctl kern.sched output would be useful too. This is for the ULE case, of course. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 10:30:56 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6164C1065673 for ; Mon, 25 Jul 2011 10:30:56 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp11.smtpout.orange.fr [80.12.242.133]) by mx1.freebsd.org (Postfix) with ESMTP id CE31D8FC19 for ; Mon, 25 Jul 2011 10:30:55 +0000 (UTC) Received: from localhost ([92.134.126.250]) by mwinf5d21 with ME id CAWs1h0045QGTlY03AWsTg; Mon, 25 Jul 2011 12:30:54 +0200 X-ME-engine: default Message-ID: <4E2D45DB.8070000@orange.fr> Date: Mon, 25 Jul 2011 12:30:51 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.18) Gecko/20110622 Thunderbird/3.1.11 MIME-Version: 1.0 To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CB4AC.3070403@orange.fr> <4E2CBF43.1070302@freebsd.org> In-Reply-To: <4E2CBF43.1070302@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 10:30:56 -0000 On 07/25/2011 02:56, Nathan Whitehorn wrote: > On 07/24/11 19:11, Claude Buisson wrote: >> On 07/24/2011 23:33, Nathan Whitehorn wrote: >>> On 07/24/11 16:29, eculp wrote: >>>> I have been hearing about a new installer but I obviously have not >>>> payed enough attention, I am afraid. I started running freebsd at 2.0 >>>> and never really had a problem with understanding the installation >>>> program. There is always a first time, I guess. >>>> >>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>>> >>>> When booting I seem to get a screen that makes me remember installer >>>> screens of the 1980s. (They were not exactly intuitive.) >>>> >>>> I somehow got the idea that the new installer was graphic. Maybe >>>> something like PCBsd that is not bad at all. I use it on all our >>>> employees computers. Actually, after seeing this, I would love to >>>> have the old installer back. Is their an option for that? >>>> >>>> Does this new ASCII installer have a "how to" with a bit of >>>> information on the flow of the installation. >>>> >>>> Thanks, >>> >>> Can you please describe what you didn't like about it, and what you >>> would prefer be changed? "Reminiscent of the 1980s" is not really >>> helpful, especially given that the new installer in fact looks very much >>> like sysinstall, which you seemed to like. >>> -Nathan >> >> Recently I installed a system from the "official" memory stick May >> snapshot >> (FreeBSD-9.0-CURRENT-201105-amd64-memstick.img). here are a few remarks: > > Thank you for testing! > My intent was not to test the installer, but I needed to install a recent 9.0-CURRENT with gpt on a brand new hardware >> - the 1st thing I need to do is to configure the keyboard, as I am not >> in the >> US. This is needed for an install, but also for using it as a live >> system. And >> the keyboard configuration dialog is only a part of the installation >> procedure. > > Which is why this is the very first screen of the installer? > If my memory is good, it was in the first screen of the install dialog, not before the choice of installation / live system >> - the partition tool is too simple/rudimentary, compared to the old >> sysinstall >> dialog. I always want to have a total control of the partitions e.g. >> to have a >> proper alignement. So one must use the shell escape or the live >> system, which is >> a regression. > > The alignment is done to match the disk stripe size automatically, and > the partition editor has many, many more features than the sysinstall > one. Is there something in particular you wanted? > I don't use any "stripe" (only plain UFS), and the "many, many features" where too well hidden for my old brain. >> - extracting the tarballs lead to (cryptic) errors: I discovered the >> hard way >> that I needed to execute a newfs. > > This is what the directions at the top of the partitioning shell say. > As I not clearly understood these directions, I skipped to the live system for doing the gpart work. >> - I followed a succession of screens asking me to do the usual >> configuration >> steps (hostname, clock, network - IPv4 only ?? -, users) and at the >> end I get >> back a screen asking me if a wanted to do the steps I had done just >> before... > > The network configuration also allows IPv6 in newer versions -- that > snapshot is 2 months out of date. The final screen says at the top that > is there to modify earlier choices. Can you suggest a clearer wording? > Clear wording is certainly a plus. >> - booting the installed system, I found that the hostname disappeared, >> the >> keyboard was not configured, nor the network, and so on > > This is inexplicable. This has worked perfectly for everyone else -- > it's possible you made a mistake in the partitioning, but I can't > imagine how it would have caused this. Are you able to reproduce the > problem? > My system is now running, and I don't have any other system to play with. >> - during the whole process the screen was scrambled by the occurence >> of a number >> of LORs displayed on top of the dialogs/messages of the installer. > > The actual 9.0 CDs will not have WITNESS enabled. It would be nice if > the LORs in question were actually fixed, however. > A "good" installer cannot suppose that there will not be any kernel message during its use, some of them will be benign. Furthermore the installer (and the whole make release process) has not for sole use the installation (and creation) of official releases. I started building my own releases at 2.2.X time.. >> - the file system of the installer/live system seems to be too small, >> leading to >> a number of "system full" messages as soon a few files are written to it. > > The live system is designed more as a fixit medium. What were you trying > to do with it? > I first copied the dmesg to be able to retrieve it on another system (was thinking that /var was a memory file system), then I saw the "system full" at different steps of the install. >> >> Referring to a thread I found recently a propos the documentation on >> the install >> media, I also want to say that a proper installer must be able to do >> its work >> without any Internet connectivity. There exist systems which are not >> connected, >> and networks without any communication with the Internet. > > Which is why it behaves in exactly the way you suggest. > -Nathan > I hope so Let us say that the new installer is a moving target, and relying on snapshots found on the FreeBSD ftp site is not the proper way of knowing it. But my only other -current system (i386 on VMWare in a very ressource constrained environment) is not the proper platform for building amd64 releases. Claude Buisson From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 11:01:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF50A1065670 for ; Mon, 25 Jul 2011 11:01:45 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id CBA2E8FC16 for ; Mon, 25 Jul 2011 11:01:45 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QlIgO-00037U-De for freebsd-current@freebsd.org; Mon, 25 Jul 2011 03:46:44 -0700 Date: Mon, 25 Jul 2011 03:46:44 -0700 (PDT) From: timp To: freebsd-current@freebsd.org Message-ID: <1311590804416-4630323.post@n5.nabble.com> In-Reply-To: References: <4E263EFE.3040200@FreeBSD.org> <4E2698D9.90106@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 25 Jul 2011 11:10:52 +0000 Subject: Re: em problem in virtualbox since the weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 11:01:46 -0000 I have same problems with em and ahci. Now in VirtialBox I temporarily set net iface to PCNet-PCI II (Am79C970A). It works with if_le driver. VirtualBox 4.1, recent FreeBSD 9. -- View this message in context: http://freebsd.1045724.n5.nabble.com/em-problem-in-virtualbox-since-the-weekend-tp4614403p4630323.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 14:06:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 137831065673; Mon, 25 Jul 2011 14:06:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C0E728FC14; Mon, 25 Jul 2011 14:06:05 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p6PE64Ff012058; Mon, 25 Jul 2011 08:06:04 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p6PE64E8012055; Mon, 25 Jul 2011 08:06:04 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 25 Jul 2011 08:06:04 -0600 (MDT) From: Warren Block To: Andriy Gapon In-Reply-To: <4E2D21DE.5070201@FreeBSD.org> Message-ID: References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2D21DE.5070201@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Mon, 25 Jul 2011 08:06:05 -0600 (MDT) Cc: freebsd-current , Nathan Whitehorn Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 14:06:06 -0000 On Mon, 25 Jul 2011, Andriy Gapon wrote: > on 25/07/2011 07:47 Warren Block said the following: >> 2. The options don't always really apply. Create when ad0 is highlighted leads >> the user to think they can create a new device, like ad1. But it will really >> create another partition. Delete on ad0 deletes all the partitions, not ad0. >> No warning, either. > > Are you sure about this one? > I have never expected that any installer would be able to create or delete > hardware (a hard disk) in my computer. "Device" as in entry in /dev. It's a little blurrier than that. With no partitioning scheme, Create makes one, having the user select the type. After that, it creates new partitions. Having messed with this editor more, I can make it work and see the intent of the user interface. I wish I could suggest a good way to make it more clear, but can't quite get my brain around it right now. From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 15:32:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D682A106566C for ; Mon, 25 Jul 2011 15:32:24 +0000 (UTC) (envelope-from tjg@soe.ucsc.edu) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mx1.freebsd.org (Postfix) with ESMTP id C3F5C8FC0C for ; Mon, 25 Jul 2011 15:32:24 +0000 (UTC) Received: from mail-01.cse.ucsc.edu (mail-01.cse.ucsc.edu [128.114.48.32]) by mail-01.cse.ucsc.edu (Postfix) with ESMTP id ADA201009B5F for ; Mon, 25 Jul 2011 08:32:24 -0700 (PDT) Date: Mon, 25 Jul 2011 08:32:24 -0700 (PDT) From: Tim Gustafson To: freebsd-current@freebsd.org Message-ID: <1276536870.10404.1311607944573.JavaMail.root@mail-01.cse.ucsc.edu> In-Reply-To: <568934638.10381.1311607558539.JavaMail.root@mail-01.cse.ucsc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [128.114.49.22] X-Mailer: Zimbra 6.0.9_GA_2686 (ZimbraWebClient - FF3.0 ([unknown])/6.0.9_GA_2686) Subject: FreeBSD 9 + ZFS + MPS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 15:32:24 -0000 I'm seeing some odd behavior on FreeBSD 9 with ZFS and an MPS controller. For two or three weeks, this configuration was working like a champ. It's a Bacula storage daemon server and was getting considerable usage - our backup set is in the multiple-terabytes-per-week of data being written to the disk. However, during the last two weeks something has broken. Starting on about July 15th or so we started to loose the data zpool which is connected via the mps driver. The disks are an external array of 32 drives, etc 2TB. When I did a "zpool status", I saw that some of the drives had dropped out of the array. Rebooting the server brought them back until the next heavy write time. On July 22nd I did a "make world" to see if there were any kernel updates that may have fixed the problem, but any updates that may have happened did not seem to help. I'm including the last entry in my dmesg.yesterday file below. Have I stumbled upon a bug? lock order reversal: 1st 0xfffffe0019cf6db8 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:829 2nd 0xfffffe0019cf69f8 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2134 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x807 __lockmgr_args() at __lockmgr_args+0xd42 vop_stdlock() at vop_stdlock+0x39 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b devfs_allocv() at devfs_allocv+0x13f devfs_root() at devfs_root+0x4d vfs_donmount() at vfs_donmount+0x988 nmount() at nmount+0x63 syscallenter() at syscallenter+0x1aa syscall() at syscall+0x4c Xfast_syscall() at Xfast_syscall+0xdd --- syscall (378, FreeBSD ELF64, nmount), rip = 0x800ab4dfc, rsp = 0x7fffffffccc8, rbp = 0x801009048 --- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tim Gustafson tjg@soe.ucsc.edu Baskin School of Engineering 831-459-5354 UC Santa Cruz Baskin Engineering 317B -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 16:23:24 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79767106566C; Mon, 25 Jul 2011 16:23:24 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 56DEA8FC1A; Mon, 25 Jul 2011 16:23:24 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id p6PGNNRo027433; Mon, 25 Jul 2011 09:23:23 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id p6PGNNdE027432; Mon, 25 Jul 2011 09:23:23 -0700 (PDT) (envelope-from sgk) Date: Mon, 25 Jul 2011 09:23:23 -0700 From: Steve Kargl To: Andriy Gapon Message-ID: <20110725162323.GA27425@troutmask.apl.washington.edu> References: <4E14A54A.4050106@freebsd.org> <4E155FF9.5090905@FreeBSD.org> <20110707151440.GA75537@troutmask.apl.washington.edu> <4E160C2F.8020001@FreeBSD.org> <20110707200845.GA77049@troutmask.apl.washington.edu> <4E1B1198.6090308@FreeBSD.org> <20110711161654.GA97361@troutmask.apl.washington.edu> <4E1C003B.4090604@FreeBSD.org> <4E2D3EBB.9060508@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E2D3EBB.9060508@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 16:23:24 -0000 On Mon, Jul 25, 2011 at 01:00:27PM +0300, Andriy Gapon wrote: > on 12/07/2011 11:05 Andriy Gapon said the following: > > I think that the best thing you can further provide (as objective evidence for > > the problem at hand) is ktr(4) traces for at least KTR_SCHED mask. Perhaps you > > even already have them from your previous sessions with Jeff. > > > > P.S. This is not a promise to actually debug this issue based on the traces :-) > > So do you have an opportunity to provide this kind of information? > Actually I would like KTR_SCHED|KTR_INTR|KTR_PROC|KTR_SYSC mask. > Also, sysctl kern.sched output would be useful too. > This is for the ULE case, of course. > I won't have time until next week to investigate. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 16:30:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AAE21065670 for ; Mon, 25 Jul 2011 16:30:36 +0000 (UTC) (envelope-from eric@shadowsun.net) Received: from mail.atlantawebhost.com (dns1.atlantawebhost.com [66.223.40.39]) by mx1.freebsd.org (Postfix) with ESMTP id 200A78FC1D for ; Mon, 25 Jul 2011 16:30:35 +0000 (UTC) Received: (qmail 881 invoked from network); 25 Jul 2011 12:23:54 -0400 Received: from yktgi01e0-s5.watson.ibm.com (HELO dyn9002034054.watson.ibm.com) (129.34.20.19) by mail.atlantawebhost.com with SMTP; 25 Jul 2011 12:23:54 -0400 Message-ID: <4E2D9899.6020900@shadowsun.net> Date: Mon, 25 Jul 2011 12:23:53 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <1276536870.10404.1311607944573.JavaMail.root@mail-01.cse.ucsc.edu> In-Reply-To: <1276536870.10404.1311607944573.JavaMail.root@mail-01.cse.ucsc.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 9 + ZFS + MPS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 16:30:36 -0000 On 7/25/11 11:32 AM, Tim Gustafson wrote: > I'm seeing some odd behavior on FreeBSD 9 with ZFS and an MPS controller. > > For two or three weeks, this configuration was working like a champ. It's a Bacula storage daemon server and was getting considerable usage - our backup set is in the multiple-terabytes-per-week of data being written to the disk. However, during the last two weeks something has broken. Starting on about July 15th or so we started to loose the data zpool which is connected via the mps driver. The disks are an external array of 32 drives, etc 2TB. When I did a "zpool status", I saw that some of the drives had dropped out of the array. Rebooting the server brought them back until the next heavy write time. On July 22nd I did a "make world" to see if there were any kernel updates that may have fixed the problem, but any updates that may have happened did not seem to help. > > I'm including the last entry in my dmesg.yesterday file below. Have I stumbled upon a bug? > > lock order reversal: > 1st 0xfffffe0019cf6db8 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:829 > 2nd 0xfffffe0019cf69f8 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2134 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x807 > __lockmgr_args() at __lockmgr_args+0xd42 > vop_stdlock() at vop_stdlock+0x39 > VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b > _vn_lock() at _vn_lock+0x47 > vget() at vget+0x7b > devfs_allocv() at devfs_allocv+0x13f > devfs_root() at devfs_root+0x4d > vfs_donmount() at vfs_donmount+0x988 > nmount() at nmount+0x63 > syscallenter() at syscallenter+0x1aa > syscall() at syscall+0x4c > Xfast_syscall() at Xfast_syscall+0xdd > --- syscall (378, FreeBSD ELF64, nmount), rip = 0x800ab4dfc, rsp = 0x7fffffffccc8, rbp = 0x801009048 --- > I've seen similar messages on a ZFS-based system, when rebooting, and when unmounting a USB memory stick (curiously, with an msdosfs filesystem, though my hard drive contains ZFS) From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 16:46:15 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6961065673; Mon, 25 Jul 2011 16:46:15 +0000 (UTC) (envelope-from eculp@encontacto.net) Received: from ns2.bafirst.com (ns2.bafirst.com [97.67.198.91]) by mx1.freebsd.org (Postfix) with ESMTP id 1995D8FC17; Mon, 25 Jul 2011 16:46:14 +0000 (UTC) Received: from unixmania.com ([189.251.157.180]) by ns2.bafirst.com with esmtp; Mon, 25 Jul 2011 11:46:12 -0500 id 000DA804.4E2D9DD5.00011C04 Received: from localhost (localhost [127.0.0.1]) (uid 80) by unixmania.com with local; Mon, 25 Jul 2011 11:46:12 -0500 id 000CF70B.4E2D9DD4.00011C7A Received: from dsl-189-251-133-16-dyn.prod-infinitum.com.mx (dsl-189-251-133-16-dyn.prod-infinitum.com.mx [189.251.133.16]) by econet.encontacto.net (Horde Framework) with HTTP; Mon, 25 Jul 2011 11:46:12 -0500 Message-ID: <20110725114612.15892pix5tua52io@econet.encontacto.net> Date: Mon, 25 Jul 2011 11:46:12 -0500 From: eculp To: Warren Block References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2D21DE.5070201@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs) X-Remote-Browser: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 X-IMP-Server: 189.251.157.180 X-Originating-IP: 189.251.133.16 X-Originating-User: eculp@encontacto.net Cc: freebsd-current , Nathan Whitehorn , Andriy Gapon Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 16:46:15 -0000 Quoting Warren Block : > On Mon, 25 Jul 2011, Andriy Gapon wrote: > >> on 25/07/2011 07:47 Warren Block said the following: >>> 2. The options don't always really apply. Create when ad0 is =20 >>> highlighted leads >>> the user to think they can create a new device, like ad1. But it =20 >>> will really >>> create another partition. Delete on ad0 deletes all the =20 >>> partitions, not ad0. >>> No warning, either. >> >> Are you sure about this one? >> I have never expected that any installer would be able to create or delet= e >> hardware (a hard disk) in my computer. > > "Device" as in entry in /dev. > > It's a little blurrier than that. With no partitioning scheme, =20 > Create makes one, having the user select the type. After that, it =20 > creates new partitions. > > Having messed with this editor more, I can make it work and see the =20 > intent of the user interface. I wish I could suggest a good way to =20 > make it more clear, but can't quite get my brain around it right now. That makes two of us right now. I gave up, accepted the automatic =20 partition and everything else went as expected, I suppose. The disk =20 results are: # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ada0p2 941441086 2150880 863974920 0% / devfs 1 1 0 100% /dev In my world from the beginning of commercial unix, I have never had a =20 one partition disk. I'm not sure if it is that bad with today's, =20 controllers, drives, drivers, etc. I hope someone chimes in with a "I =20 see no major problems with gpt." My major problem was editing the automatic swap that was set at 4G and =20 the menu would not let me change the 4G. The experienced option would =20 not accept a blank value as swap even though there was message that =20 said it would. I feel like a real idiot and am beginning to believe that it might be true. The rest of the install was brain dead. It was possibly a bit simpler =20 than the previous. Less decisions ;) I had the idea the following were available in the new installer. 1. Raid configuration 2. ZFS 3. Regular everyday simple disk partitioning as before. I wasn't able to find any functional option except the one mentioned above. Now, I have to accept this single partition or upgrade sources to =20 date, build a release and reinstall but I don't know if the problem =20 has been fixed. I'll probably give it a try. It isn't that much of a =20 deal. Thanks, ed > _______________________________________________ > 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 Jul 25 17:22:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A18EB1065673; Mon, 25 Jul 2011 17:22:36 +0000 (UTC) (envelope-from rcm@fuzzwad.org) Received: from mail.volente.us (unknown [IPv6:2001:470:7:d47::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE5F8FC14; Mon, 25 Jul 2011 17:22:36 +0000 (UTC) Received: from zombie.fuzzwad.net (localhost [127.0.0.1]) by mail.volente.us (8.14.4/8.14.4) with ESMTP id p6PHMVRF061952; Mon, 25 Jul 2011 12:22:32 -0500 (CDT) (envelope-from rcm@fuzzwad.org) Message-ID: <4E2DA657.4070905@fuzzwad.org> Date: Mon, 25 Jul 2011 12:22:31 -0500 From: Ron McDowell User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Nathan Whitehorn References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2CC0DE.9050802@freebsd.org> In-Reply-To: <4E2CC0DE.9050802@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:22:36 -0000 Nathan Whitehorn wrote: > On 07/24/11 18:03, Ron McDowell wrote: >> Nathan Whitehorn wrote: >>> On 07/24/11 16:29, eculp wrote: >>>> I have been hearing about a new installer but I obviously have not >>>> payed enough attention, I am afraid. I started running freebsd at >>>> 2.0 and never really had a problem with understanding the >>>> installation program. There is always a first time, I guess. >>>> >>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ >>>> >>>> When booting I seem to get a screen that makes me remember >>>> installer screens of the 1980s. (They were not exactly intuitive.) >>>> >>>> I somehow got the idea that the new installer was graphic. Maybe >>>> something like PCBsd that is not bad at all. I use it on all our >>>> employees computers. Actually, after seeing this, I would love to >>>> have the old installer back. Is their an option for that? >>>> >>>> Does this new ASCII installer have a "how to" with a bit of >>>> information on the flow of the installation. >>>> >>>> Thanks, >>> >>> Can you please describe what you didn't like about it, and what you >>> would prefer be changed? "Reminiscent of the 1980s" is not really >>> helpful, especially given that the new installer in fact looks very >>> much like sysinstall, which you seemed to like. >>> -Nathan >>> >> >> I'll have to agree with the original poster. I have no problem with >> the look and feel of the new installer, but when functionality that >> WAS there is now gone, that's a problem. My two, make that three, >> biggest gripes are: >> >> 1) no "back" button/selection/mechanism on each screen. Rebooting >> because I fat-fingered something on the previous screen is, well, >> unacceptable. > > This is why almost all screens have a "cancel" button. You can also > restart the installer by control-C at any time without rebooting. > Providing an actual back button is quite tricky and not necessarily > always well defined in behavior, since the installed system will then > be in an inconsistent state at which previous steps cannot necessarily > be repeated. For those steps where that is not true, they can be > reentered from the menu at the end in case of fat-fingering. 22 screens require user input in a basic install [on my box, taking the default choices]. Only 7 have a 'cancel' button, which puts you back one screen, most likely to a screen you can't escape from. ctl-c to restart is about a half-step up from rebooting. How about a note at the start stating that you will be able to make changes later before committing to the install? > >> 2) no "minimal" install. Most of my installs are single- or few-task >> servers where I need a base os and a couple ports. > > I'm not sure what you mean by this. You can install just a kernel and > the base system by deselecting the ports tree, games, and docs when > you select which system components to install. I see now that this is outside of the "install" program's scope...in 9.0 the number of distributions has been shrunk, so the install program has to work with what's available to it. > >> 3) I see no "post-install" uses on the new one. Sysinstall could be >> used on an up-and-running system to do everything from adding a user >> to changing a nameserver and more. >> > > This is deliberate. This particular feature of sysinstall made it > almost unmaintainable, especially as those features slowly bitrotted. > We have very good system configuration utilities already vi-ing /etc/resolv.conf is a configuration utility? > -- there is no need to duplicate them in the installer, especially > when it makes maintaining and improving that installer more difficult. Fire up sysinstall on a system. Hit 'C'. Where else can a beginner go to find all this good stuff in one spot? I agree it doesn't need to be part of the install program, but it does need to be part of the OS. > -Nathan One new thing I noticed is the new install does not eject the CD at the end before rebooting. I've seen systems where 'eject' didn't do anything...but it never caused a problem either. Please consider adding that. -- Ron McDowell San Antonio TX From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:23:14 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 469821065677 for ; Mon, 25 Jul 2011 17:23:14 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by mx1.freebsd.org (Postfix) with ESMTP id CD4A58FC19 for ; Mon, 25 Jul 2011 17:23:13 +0000 (UTC) Received: by fxe6 with SMTP id 6so7008411fxe.17 for ; Mon, 25 Jul 2011 10:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Cel7+uqbEZDuhMLN2xlM2oBaAM6J18lUZRIC4k2ryoE=; b=qsmryF7fk4K4oaveRyrfc6rUYA5X6fsBIbtuf6tCTRKPgKUh+OYI35jOTdsL46rqeS FQH41RVZqdbJ9dICbIKsnYZy3EQ+J33HMQ+7o4dq8arAwtL4zV7EDYQEQkJON17F5ZDt HykzqRwKLLxbxJJlsNkiyphQVwGQ3I2Gg1dWY= MIME-Version: 1.0 Received: by 10.223.144.136 with SMTP id z8mr4462651fau.31.1311612906225; Mon, 25 Jul 2011 09:55:06 -0700 (PDT) Received: by 10.223.124.67 with HTTP; Mon, 25 Jul 2011 09:55:06 -0700 (PDT) In-Reply-To: <20110725114612.15892pix5tua52io@econet.encontacto.net> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2D21DE.5070201@FreeBSD.org> <20110725114612.15892pix5tua52io@econet.encontacto.net> Date: Mon, 25 Jul 2011 11:55:06 -0500 Message-ID: From: Adam Vande More To: eculp Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:23:14 -0000 On Mon, Jul 25, 2011 at 11:46 AM, eculp wrote: > That makes two of us right now. I gave up, accepted the automatic > partition and everything else went as expected, I suppose. The disk results > are: > > # df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ada0p2 941441086 2150880 863974920 0% / > devfs 1 1 0 100% /dev > > In my world from the beginning of commercial unix, I have never had a one > partition disk. I'm not sure if it is that bad with today's, controllers, > drives, drivers, etc. I hope someone chimes in with a "I see no major > problems with gpt." > > My major problem was editing the automatic swap that was set at 4G and the > menu would not let me change the 4G. The experienced option would not > accept a blank value as swap even though there was message that said it > would. > > I feel like a real idiot and am beginning to believe that it might be true. > The rest of the install was brain dead. It was possibly a bit simpler than > the previous. Less decisions ;) > > I had the idea the following were available in the new installer. > 1. Raid configuration > 2. ZFS > 3. Regular everyday simple disk partitioning as before. > > I wasn't able to find any functional option except the one mentioned above. > > Now, I have to accept this single partition or upgrade sources to date, > build a release and reinstall but I don't know if the problem has been > fixed. I'll probably give it a try. It isn't that much of a deal. > Hopefully I add something of value to this thread, but as a workaround you can use a PCBSD image and installer to install/partion plain vanilla FreeBSD with the options you mentioned earlier in a graphical enviroment. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:30:05 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AA851065674 for ; Mon, 25 Jul 2011 17:30:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3218D8FC18 for ; Mon, 25 Jul 2011 17:30:05 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D81D846B24; Mon, 25 Jul 2011 13:30:04 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 72D268A02E; Mon, 25 Jul 2011 13:30:04 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 25 Jul 2011 13:08:03 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E263EFE.3040200@FreeBSD.org> <1311590804416-4630323.post@n5.nabble.com> In-Reply-To: <1311590804416-4630323.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107251308.03742.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 25 Jul 2011 13:30:04 -0400 (EDT) Cc: timp Subject: Re: em problem in virtualbox since the weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:30:05 -0000 On Monday, July 25, 2011 6:46:44 am timp wrote: > I have same problems with em and ahci. > > Now in VirtialBox I temporarily set net iface to PCNet-PCI II (Am79C970A). > It works with if_le driver. > > VirtualBox 4.1, recent FreeBSD 9. So are you having problems with the latest FreeBSD 9? Can you capture a verbose dmesg if so? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:30:06 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF8AD106566B; Mon, 25 Jul 2011 17:30:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 893D98FC13; Mon, 25 Jul 2011 17:30:06 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3E18C46B06; Mon, 25 Jul 2011 13:30:06 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 8E2BE8A02F; Mon, 25 Jul 2011 13:30:05 -0400 (EDT) From: John Baldwin To: Baptiste Daroussin Date: Mon, 25 Jul 2011 13:09:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107251309.04133.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 25 Jul 2011 13:30:05 -0400 (EDT) Cc: current@freebsd.org Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:30:06 -0000 On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: > Hi, > > Trying to upgrade one of my box from 8-stable to 9-current lead be to > some important problems. > > I'm have tried both from sources (svn buildworld etc.) and from memdisk > provided by allbsd.org. > > The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 > > more informations here : > http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and > http://people.freebsd.org/~bapt/P5N-E.pciconv.txt Can you get a verbose dmesg from 8-stable? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:30:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2EA3106566B for ; Mon, 25 Jul 2011 17:30:52 +0000 (UTC) (envelope-from eculp@encontacto.net) Received: from ns2.bafirst.com (ns2.bafirst.com [97.67.198.91]) by mx1.freebsd.org (Postfix) with ESMTP id 702C28FC08 for ; Mon, 25 Jul 2011 17:30:51 +0000 (UTC) Received: from unixmania.com ([189.251.157.180]) by ns2.bafirst.com with esmtp; Mon, 25 Jul 2011 12:30:50 -0500 id 000DA805.4E2DA84A.00011D02 Received: from localhost (localhost [127.0.0.1]) (uid 80) by unixmania.com with local; Mon, 25 Jul 2011 12:30:49 -0500 id 000CF70B.4E2DA849.0001219C Received: from dsl-189-251-133-16-dyn.prod-infinitum.com.mx (dsl-189-251-133-16-dyn.prod-infinitum.com.mx [189.251.133.16]) by econet.encontacto.net (Horde Framework) with HTTP; Mon, 25 Jul 2011 12:30:49 -0500 Message-ID: <20110725123049.181470bkj1qfm1gc@econet.encontacto.net> Date: Mon, 25 Jul 2011 12:30:49 -0500 From: eculp To: Adam Vande More References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2D21DE.5070201@FreeBSD.org> <20110725114612.15892pix5tua52io@econet.encontacto.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs) X-Remote-Browser: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 X-IMP-Server: 189.251.157.180 X-Originating-IP: 189.251.133.16 X-Originating-User: eculp@encontacto.net Cc: freebsd-current Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:30:53 -0000 Quoting Adam Vande More : > On Mon, Jul 25, 2011 at 11:46 AM, eculp wrote: > >> That makes two of us right now. I gave up, accepted the automatic >> partition and everything else went as expected, I suppose. The disk resu= lts >> are: >> >> # df >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/ada0p2 941441086 2150880 863974920 0% / >> devfs 1 1 0 100% /dev >> >> In my world from the beginning of commercial unix, I have never had a one >> partition disk. I'm not sure if it is that bad with today's, controllers= , >> drives, drivers, etc. I hope someone chimes in with a "I see no major >> problems with gpt." >> >> My major problem was editing the automatic swap that was set at 4G and th= e >> menu would not let me change the 4G. The experienced option would not >> accept a blank value as swap even though there was message that said it >> would. >> >> I feel like a real idiot and am beginning to believe that it might be tru= e. >> The rest of the install was brain dead. It was possibly a bit simpler th= an >> the previous. Less decisions ;) >> >> I had the idea the following were available in the new installer. >> 1. Raid configuration >> 2. ZFS >> 3. Regular everyday simple disk partitioning as before. >> >> I wasn't able to find any functional option except the one mentioned abov= e. >> >> Now, I have to accept this single partition or upgrade sources to date, >> build a release and reinstall but I don't know if the problem has been >> fixed. I'll probably give it a try. It isn't that much of a deal. >> > > Hopefully I add something of value to this thread, but as a workaround you > can use a PCBSD image and installer to install/partion plain vanilla FreeB= SD > with the options you mentioned earlier in a graphical enviroment. Thanks Adam, I suppose that I could just pull it into this machine and execute it =20 as if it were sysinstall and reconfigure from the same box without =20 having to update, make release, etc. I'm going to give that a try. Have a great day. ed > > -- > Adam Vande More > From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 17:37:01 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BC1A106564A; Mon, 25 Jul 2011 17:37:01 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 06D578FC0C; Mon, 25 Jul 2011 17:37:00 +0000 (UTC) Received: by ywf7 with SMTP id 7so2882530ywf.13 for ; Mon, 25 Jul 2011 10:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jjzyNr1q73UKu9logqiqGKSfbLwOHP1YeQHUiJWIPHQ=; b=b5jcOar8Rt/SiGctOKvVYboIigMsjGaZZwKwV7Zqd5/i+ShkO188phjTVdqNUWIIUA UlsQGZEWRbL/TzW1iaQQDYuP01lDe/B6TYldnADPtGD9+ci0mEbhyyuPW/2xnWo9uqpY q7nyApV8PTKvnXPrEnNz0th9W0JzJU8sRm0Bg= MIME-Version: 1.0 Received: by 10.90.249.31 with SMTP id w31mr4700958agh.202.1311615420162; Mon, 25 Jul 2011 10:37:00 -0700 (PDT) Received: by 10.90.209.12 with HTTP; Mon, 25 Jul 2011 10:36:59 -0700 (PDT) In-Reply-To: <4E2D125F.6040909@cran.org.uk> References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2D125F.6040909@cran.org.uk> Date: Mon, 25 Jul 2011 10:36:59 -0700 Message-ID: From: Freddie Cash To: Bruce Cran Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current , Ron McDowell , Nathan Whitehorn , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 17:37:01 -0000 On Sun, Jul 24, 2011 at 11:51 PM, Bruce Cran wrote: > On 25/07/2011 06:01, Freddie Cash wrote: > >> Thank goodness. The worst thing about sysinstall was that it tried to be a >> Swiss Army knife doing everything, yet not doing any one thing well. It made >> a royal mess of rc.conf if you tried to use it to configure a system. >> Usually the first time someone mentions they use it for post-install >> configuration, the recommendation is to stop doing that! An os installer >> should do just that: install the os and nothing else. >> > > I tend to disagree with this. For people unfamiliar with FreeBSD using it > as a systems administration tool can be really useful, at least until they > understand where all the various configuration files are and how they work. > Having recently switched to opensuse from Ubuntu I know I find the YaST > tool incredibly useful, and probably wouldn't have continued using SuSE if > it hadn't been there. Its installer mode is one of the better installers > I've come across, and lets you fine-tune the configuration. > The difference is that YaST was designed from the get-go to be both a system management tool and a software installation tool and a system installation tool. Sysinstall was not, and sysinstall used as a post-install management tool the past couple of years has caused more issues for newbies than it's "solved". If nothing else happened to sysinstall but all the post-install crud was removed from it, it would be improved a thousand-fold. Since no one has stepped up to fix the issues with the post-install management facets of sysinstall, it's only natural to remove those bits. And, since no one wants to create a new TUI management tool, there's no reason to burden the bsdinstall devs with it. Let's make an installation tool. Later, we can worry about a TUI management tool, if it's really needed. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 18:43:00 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DDBD10656EF; Mon, 25 Jul 2011 18:43:00 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id 459738FC14; Mon, 25 Jul 2011 18:43:00 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id 60C8F7E81F; Mon, 25 Jul 2011 20:42:59 +0200 (CEST) To: John Baldwin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Jul 2011 18:42:59 +0000 From: Baptiste Daroussin In-Reply-To: <201107251309.04133.jhb@freebsd.org> References: <201107251309.04133.jhb@freebsd.org> Message-ID: <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Cc: current@freebsd.org Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 18:43:00 -0000 On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >> Hi, >> >> Trying to upgrade one of my box from 8-stable to 9-current lead be >> to >> some important problems. >> >> I'm have tried both from sources (svn buildworld etc.) and from >> memdisk >> provided by allbsd.org. >> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >> >> more informations here : >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt > > Can you get a verbose dmesg from 8-stable? A boot -v from current memdisk is full of: (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata0:0:1:0): CAM status: Command timeout here is the dmesg from boot -v on 8-stable: http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt the xpt_config message disapear by removing sbp from the kernel regards, Bapt From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 19:19:44 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BE021065672; Mon, 25 Jul 2011 19:19:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 63FF18FC21; Mon, 25 Jul 2011 19:19:44 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1864F46B23; Mon, 25 Jul 2011 15:19:44 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A35E78A02C; Mon, 25 Jul 2011 15:19:43 -0400 (EDT) From: John Baldwin To: Baptiste Daroussin Date: Mon, 25 Jul 2011 15:19:42 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <201107251309.04133.jhb@freebsd.org> <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> In-Reply-To: <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107251519.43056.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 25 Jul 2011 15:19:43 -0400 (EDT) Cc: current@freebsd.org Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 19:19:44 -0000 On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: > On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: > > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: > >> Hi, > >> > >> Trying to upgrade one of my box from 8-stable to 9-current lead be > >> to > >> some important problems. > >> > >> I'm have tried both from sources (svn buildworld etc.) and from > >> memdisk > >> provided by allbsd.org. > >> > >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 > >> > >> more informations here : > >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and > >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt > > > > Can you get a verbose dmesg from 8-stable? > > A boot -v from current memdisk is full of: > (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 > 00 00 00 > (aprobe0:ata0:0:1:0): CAM status: Command timeout > > here is the dmesg from boot -v on 8-stable: > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt > > the xpt_config message disapear by removing sbp from the kernel It seems that you have an ATAPI floppy-drive device that 8 doesn't like: afd0: setting PIO3 device_attach: afd0 attach returned 6 Have you tried enabling ATA_CAM on 8 as a test, or removing the ATAPI floppy- drive as a test? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 19:37:37 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C310106566B; Mon, 25 Jul 2011 19:37:37 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id E3FE88FC12; Mon, 25 Jul 2011 19:37:36 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id 1A0FC7E81F; Mon, 25 Jul 2011 21:37:36 +0200 (CEST) To: John Baldwin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Jul 2011 19:37:36 +0000 From: Baptiste Daroussin In-Reply-To: <201107251519.43056.jhb@freebsd.org> References: <201107251309.04133.jhb@freebsd.org> <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> <201107251519.43056.jhb@freebsd.org> Message-ID: <90f2b6c9a9f0b7badfeb24d5849ef21c@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Cc: current@freebsd.org Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 19:37:37 -0000 On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: > On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >> >> Hi, >> >> >> >> Trying to upgrade one of my box from 8-stable to 9-current lead >> be >> >> to >> >> some important problems. >> >> >> >> I'm have tried both from sources (svn buildworld etc.) and from >> >> memdisk >> >> provided by allbsd.org. >> >> >> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >> >> >> >> more informations here : >> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >> > >> > Can you get a verbose dmesg from 8-stable? >> >> A boot -v from current memdisk is full of: >> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 >> 00 >> 00 00 00 >> (aprobe0:ata0:0:1:0): CAM status: Command timeout >> >> here is the dmesg from boot -v on 8-stable: >> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >> >> the xpt_config message disapear by removing sbp from the kernel > > It seems that you have an ATAPI floppy-drive device that 8 doesn't > like: > > afd0: setting PIO3 > device_attach: afd0 attach returned 6 > > Have you tried enabling ATA_CAM on 8 as a test, or removing the ATAPI > floppy- > drive as a test? kldload atapicam is happy with it: $> camcontrol devlist at scbus0 target 0 lun 0 (cd0,pass0) at scbus0 target 1 lun 0 (da0,pass1) Anyway I removed it and restart booting on the memstick but it fails the same way as before. Each time it fails booting on current, if I reset to reboot 8-stable it fails finding the disks. if I turn off and on again I am able to boot the 8-stable again... really strange. bapt From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 20:02:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C687106564A; Mon, 25 Jul 2011 20:02:07 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1D0BC8FC0A; Mon, 25 Jul 2011 20:02:06 +0000 (UTC) Received: by iyb11 with SMTP id 11so6863729iyb.13 for ; Mon, 25 Jul 2011 13:02:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WFDn7vK/5TyQh9rLGYlEwqFj5S9DqPc3tp4gM6rf87U=; b=U9Slw4lwhbExg4PQhSfktes9hO2/iu5ZR7/L+zcfpa0S0WV8K/YKHyKsH8W5vaTsLM 0jzUB27l9UEKA3qKs61FduqOqKlVkSNIUKZl7ETKV7yWUnK7kIXqQxacB5kBTKN+oVb3 iA8Z19wyDk3VycPh3jrtv01F+uoP0YNRf6PGc= MIME-Version: 1.0 Received: by 10.231.112.193 with SMTP id x1mr5040480ibp.59.1311622724007; Mon, 25 Jul 2011 12:38:44 -0700 (PDT) Received: by 10.231.34.6 with HTTP; Mon, 25 Jul 2011 12:38:43 -0700 (PDT) In-Reply-To: <201107251308.03742.jhb@freebsd.org> References: <4E263EFE.3040200@FreeBSD.org> <1311590804416-4630323.post@n5.nabble.com> <201107251308.03742.jhb@freebsd.org> Date: Mon, 25 Jul 2011 23:38:43 +0400 Message-ID: From: Pavel Timofeev To: John Baldwin X-Mailman-Approved-At: Mon, 25 Jul 2011 20:08:44 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: em problem in virtualbox since the weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 20:02:08 -0000 Hmm, it was a few days ago. Something like "Unable to allocate bus resource: memory" Today I rebuilt latest kernel & world and now em and ahci works! 2011/7/25 John Baldwin > On Monday, July 25, 2011 6:46:44 am timp wrote: > > I have same problems with em and ahci. > > > > Now in VirtialBox I temporarily set net iface to PCNet-PCI II > (Am79C970A). > > It works with if_le driver. > > > > VirtualBox 4.1, recent FreeBSD 9. > > So are you having problems with the latest FreeBSD 9? Can you capture a > verbose dmesg if so? > > -- > John Baldwin > From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 21:31:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7EF3106564A for ; Mon, 25 Jul 2011 21:31:07 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id 8B75D8FC08 for ; Mon, 25 Jul 2011 21:31:07 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id 9C2D77E81F; Mon, 25 Jul 2011 23:12:33 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Jul 2011 21:12:33 +0000 From: Baptiste Daroussin In-Reply-To: <90f2b6c9a9f0b7badfeb24d5849ef21c@etoilebsd.net> References: <201107251309.04133.jhb@freebsd.org> <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> <201107251519.43056.jhb@freebsd.org> <90f2b6c9a9f0b7badfeb24d5849ef21c@etoilebsd.net> Message-ID: <6f13480c7167dadf4e40debaa09927a8@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 21:31:07 -0000 On Mon, 25 Jul 2011 19:37:36 +0000, Baptiste Daroussin wrote: > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >>> >> Hi, >>> >> >>> >> Trying to upgrade one of my box from 8-stable to 9-current lead >>> be >>> >> to >>> >> some important problems. >>> >> >>> >> I'm have tried both from sources (svn buildworld etc.) and from >>> >> memdisk >>> >> provided by allbsd.org. >>> >> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >>> >> >>> >> more informations here : >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >>> > >>> > Can you get a verbose dmesg from 8-stable? >>> >>> A boot -v from current memdisk is full of: >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 >>> 00 >>> 00 00 00 >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout >>> >>> here is the dmesg from boot -v on 8-stable: >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >>> >>> the xpt_config message disapear by removing sbp from the kernel >> >> It seems that you have an ATAPI floppy-drive device that 8 doesn't >> like: >> >> afd0: setting PIO3 >> device_attach: afd0 attach returned 6 >> >> Have you tried enabling ATA_CAM on 8 as a test, or removing the >> ATAPI floppy- >> drive as a test? > > kldload atapicam is happy with it: > > $> camcontrol devlist > at scbus0 target 0 lun 0 > (cd0,pass0) > at scbus0 target 1 lun 0 > (da0,pass1) > > > Anyway I removed it and restart booting on the memstick but it fails > the same way as before. > > Each time it fails booting on current, if I reset to reboot 8-stable > it fails finding the disks. if I turn off and on again I am able to > boot the 8-stable again... really strange. > > bapt > _______________________________________________ > 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" Even after having disabled the disk or even remove them, the boot still fail from both cdrom and memstick. BApt From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 21:44:05 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB2231065672 for ; Mon, 25 Jul 2011 21:44:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 893658FC08 for ; Mon, 25 Jul 2011 21:44:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4EALviLU6DaFvO/2dsb2JhbAA0AQEFKVwdDgoCAg0lAhZRBQKEbaN8uG6RFIErhAWBDwSScJApUw X-IronPort-AV: E=Sophos;i="4.67,264,1309752000"; d="scan'208";a="128527713" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 25 Jul 2011 17:44:04 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id BCC47B3F0C; Mon, 25 Jul 2011 17:44:04 -0400 (EDT) Date: Mon, 25 Jul 2011 17:44:04 -0400 (EDT) From: Rick Macklem To: Steve Kargl Message-ID: <254152988.989678.1311630244759.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110725162323.GA27425@troutmask.apl.washington.edu> 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: freebsd-current@FreeBSD.org, Andriy Gapon Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 21:44:05 -0000 Steve Kargl wrote: > On Mon, Jul 25, 2011 at 01:00:27PM +0300, Andriy Gapon wrote: > > on 12/07/2011 11:05 Andriy Gapon said the following: > > > I think that the best thing you can further provide (as objective > > > evidence for > > > the problem at hand) is ktr(4) traces for at least KTR_SCHED mask. > > > Perhaps you > > > even already have them from your previous sessions with Jeff. > > > > > > P.S. This is not a promise to actually debug this issue based on > > > the traces :-) > > > > So do you have an opportunity to provide this kind of information? > > Actually I would like KTR_SCHED|KTR_INTR|KTR_PROC|KTR_SYSC mask. > > Also, sysctl kern.sched output would be useful too. > > This is for the ULE case, of course. > > > > I won't have time until next week to investigate. > hrs sent me this panic. I'm wondering if it might be relevant to this? spin lock 0xffffffff80cb52c0 (sched lock 1) held by 0xffffff0012c7f8c0 (tid 100317) too long panic: spin lock held too long cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x187 _mtx_lock_spin_failed() at _mtx_lock_spin_failed+0x39 _mtx_lock_spin() at _mtx_lock_spin+0x9e sched_add() at sched_add+0x117 setrunnable() at setrunnable+0x78 sleepq_signal() at sleepq_signal+0x7a cv_signal() at cv_signal+0x3b xprt_active() at xprt_active+0xe3 svc_vc_soupcall() at svc_vc_soupcall+0xc sowakeup() at sowakeup+0x69 tcp_do_segment() at tcp_do_segment+0x2cbd tcp_input() at tcp_input+0xcdd ip_input() at ip_input+0xac netisr_dispatch_src() at netisr_dispatch_src+0x7e ether_demux() at ether_demux+0x14d ether_input() at ether_input+0x17d em_rxeof() at em_rxeof+0x1ca em_handle_que() at em_handle_que+0x5b taskqueue_run_locked() at taskqueue_run_locked+0x85 taskqueue_thread_loop() at taskqueue_thread_loop+0x4e fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff8000160d00, rbp = 0 --- KDB: enter: panic [thread pid 0 tid 100033 ] Stopped at kdb_enter+0x3b: movq $0,0x6b4e62(%rip) db> ps From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 21:49:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A239D106564A for ; Mon, 25 Jul 2011 21:49:45 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id 6B7738FC13 for ; Mon, 25 Jul 2011 21:49:45 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id B62637E81F; Mon, 25 Jul 2011 23:49:44 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Jul 2011 21:49:44 +0000 From: Baptiste Daroussin In-Reply-To: <201107251519.43056.jhb@freebsd.org> References: <201107251309.04133.jhb@freebsd.org> <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> <201107251519.43056.jhb@freebsd.org> Message-ID: <7042b10f5837cf0b5cd8805ab3a46795@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 21:49:45 -0000 On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: > On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >> >> Hi, >> >> >> >> Trying to upgrade one of my box from 8-stable to 9-current lead >> be >> >> to >> >> some important problems. >> >> >> >> I'm have tried both from sources (svn buildworld etc.) and from >> >> memdisk >> >> provided by allbsd.org. >> >> >> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >> >> >> >> more informations here : >> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >> > >> > Can you get a verbose dmesg from 8-stable? >> >> A boot -v from current memdisk is full of: >> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 >> 00 >> 00 00 00 >> (aprobe0:ata0:0:1:0): CAM status: Command timeout >> >> here is the dmesg from boot -v on 8-stable: >> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >> >> the xpt_config message disapear by removing sbp from the kernel > > It seems that you have an ATAPI floppy-drive device that 8 doesn't > like: > > afd0: setting PIO3 > device_attach: afd0 attach returned 6 > > Have you tried enabling ATA_CAM on 8 as a test, or removing the ATAPI > floppy- > drive as a test? Ok I'm dumb, I tested atapicam instead of ata_cam. I rebuild 8-stable kernel with ATA_CAM and it works (with lots of warnings concerning the dvdrw). Here is the 8-stable dmesg with boot -v: http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt Bapt From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 22:14:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8342106564A for ; Mon, 25 Jul 2011 22:14:13 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id 9D8A28FC15 for ; Mon, 25 Jul 2011 22:14:13 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id BD4567E81F; Tue, 26 Jul 2011 00:14:12 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Jul 2011 22:14:12 +0000 From: Baptiste Daroussin In-Reply-To: <7042b10f5837cf0b5cd8805ab3a46795@etoilebsd.net> References: <201107251309.04133.jhb@freebsd.org> <97cdc91ac6409923bfd035d4401c4a69@etoilebsd.net> <201107251519.43056.jhb@freebsd.org> <7042b10f5837cf0b5cd8805ab3a46795@etoilebsd.net> Message-ID: <6ffed3eeaecff37888be8aa07d6157d7@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 22:14:13 -0000 On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote: > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >>> >> Hi, >>> >> >>> >> Trying to upgrade one of my box from 8-stable to 9-current lead >>> be >>> >> to >>> >> some important problems. >>> >> >>> >> I'm have tried both from sources (svn buildworld etc.) and from >>> >> memdisk >>> >> provided by allbsd.org. >>> >> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >>> >> >>> >> more informations here : >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >>> > >>> > Can you get a verbose dmesg from 8-stable? >>> >>> A boot -v from current memdisk is full of: >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 >>> 00 >>> 00 00 00 >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout >>> >>> here is the dmesg from boot -v on 8-stable: >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >>> >>> the xpt_config message disapear by removing sbp from the kernel >> >> It seems that you have an ATAPI floppy-drive device that 8 doesn't >> like: >> >> afd0: setting PIO3 >> device_attach: afd0 attach returned 6 >> >> Have you tried enabling ATA_CAM on 8 as a test, or removing the >> ATAPI floppy- >> drive as a test? > > Ok I'm dumb, I tested atapicam instead of ata_cam. > > I rebuild 8-stable kernel with ATA_CAM and it works (with lots of > warnings concerning the dvdrw). > > Here is the 8-stable dmesg with boot -v: > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt > > Bapt > > _______________________________________________ > 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" New informations it doesn't work either on -CURRENT without ATA_CAM. regards, Bapt From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 23:12:17 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21AFD1065670 for ; Mon, 25 Jul 2011 23:12:17 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A31248FC0A for ; Mon, 25 Jul 2011 23:12:16 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QlUJq-0004ZH-Uh for freebsd-current@freebsd.org; Tue, 26 Jul 2011 01:12:14 +0200 Received: from 208.88.188.90.adsl.tomsknet.ru ([90.188.88.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jul 2011 01:12:14 +0200 Received: from vadim_nuclight by 208.88.188.90.adsl.tomsknet.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jul 2011 01:12:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Vadim Goncharov Date: Mon, 25 Jul 2011 23:12:01 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 27 Message-ID: References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 208.88.188.90.adsl.tomsknet.ru X-Comment-To: Freddie Cash User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 23:12:17 -0000 Hi Freddie Cash! On Sun, 24 Jul 2011 22:01:44 -0700; Freddie Cash wrote about 'Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.': >> 3) I see no "post-install" uses on the new one. Sysinstall could be used > on an up-and-running system to do everything from adding a user to changing > a nameserver and more. > Thank goodness. The worst thing about sysinstall was that it tried to be a > Swiss Army knife doing everything, yet not doing any one thing well. It made > a royal mess of rc.conf if you tried to use it to configure a system. > Usually the first time someone mentions they use it for post-install > configuration, the recommendation is to stop doing that! > An os installer should do just that: install the os and nothing else. No. That's wrong. An installer should make a usable system. While using sysinstall for configuration multiple times made a mess, it is still needed to make configuration the _first time_ - and it really did, without any mess. You've got a working keyboard, TTY, network, users/passwords, etc. - before reboot. This is something which must be intuitive for a new user, even if it is used only one time in the system's life (at the installation). Cutting it - is a regression. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 23:23:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61C941065677 for ; Mon, 25 Jul 2011 23:23:07 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id E13718FC23 for ; Mon, 25 Jul 2011 23:23:06 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QlUUL-0007YG-2q for freebsd-current@freebsd.org; Tue, 26 Jul 2011 01:23:05 +0200 Received: from 208.88.188.90.adsl.tomsknet.ru ([90.188.88.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jul 2011 01:23:05 +0200 Received: from vadim_nuclight by 208.88.188.90.adsl.tomsknet.ru with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jul 2011 01:23:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Vadim Goncharov Date: Mon, 25 Jul 2011 23:22:53 +0000 (UTC) Organization: Nuclear Lightning @ Tomsk, TPU AVTF Hostel Lines: 56 Message-ID: References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2D125F.6040909@cran.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 208.88.188.90.adsl.tomsknet.ru X-Comment-To: Freddie Cash User-Agent: slrn/0.9.9p1 (FreeBSD) Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 23:23:07 -0000 Hi Freddie Cash! On Mon, 25 Jul 2011 10:36:59 -0700; Freddie Cash wrote about 'Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.': >>> Thank goodness. The worst thing about sysinstall was that it tried to be a >>> Swiss Army knife doing everything, yet not doing any one thing well. It made >>> a royal mess of rc.conf if you tried to use it to configure a system. >>> Usually the first time someone mentions they use it for post-install >>> configuration, the recommendation is to stop doing that! An os installer >>> should do just that: install the os and nothing else. >>> >> >> I tend to disagree with this. For people unfamiliar with FreeBSD using it >> as a systems administration tool can be really useful, at least until they >> understand where all the various configuration files are and how they work. >> Having recently switched to opensuse from Ubuntu I know I find the YaST >> tool incredibly useful, and probably wouldn't have continued using SuSE if >> it hadn't been there. Its installer mode is one of the better installers >> I've come across, and lets you fine-tune the configuration. >> > The difference is that YaST was designed from the get-go to be both a system > management tool and a software installation tool and a system installation > tool. Sysinstall was not, and sysinstall used as a post-install management > tool the past couple of years has caused more issues for newbies than it's > "solved". > If nothing else happened to sysinstall but all the post-install crud was > removed from it, it would be improved a thousand-fold. > Since no one has stepped up to fix the issues with the post-install > management facets of sysinstall, it's only natural to remove those bits. The bad tool is better than absence of the tool. The sysinstall could at least something similar to YaST. The primary purpose is people unfamiliar with FreeBSD, of course. And for experiences - even YaST sucks in many aspects. > And, since no one wants to create a new TUI management tool, there's no > reason to burden the bsdinstall devs with it. Sure, no reason to burden with creation, but already existing couldbe adapted a little. E.g. disk partitioning was cutted to sade from sysinstall, the same could be done with parts of sysinstall, until something better is delivered. > Let's make an installation tool. Later, we can worry about a TUI management > tool, if it's really needed. The point is not a full-blown TUI tool like YaST but rather a regress in comparison with sysinstall. A something minimal must be present, not worse in features than something already existed. When "later" a userbase of FreeBSD will shrink due to installer issues, it will be much harder to regain it than to prevent it today. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-current@FreeBSD.ORG Mon Jul 25 23:33:24 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9472F106566C; Mon, 25 Jul 2011 23:33:24 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3E6FF8FC1E; Mon, 25 Jul 2011 23:33:23 +0000 (UTC) Received: by yic13 with SMTP id 13so3114432yic.13 for ; Mon, 25 Jul 2011 16:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Y5Pbs8CuDbqLP63XAGXS0sACEE0UoqGr0LFyrrIWdpQ=; b=vzwJ4Nl0aM5Dx2vNFZ4F8DEqgxI4TH8EMIGLby0ngF10sQBeowJquOklr40LASOt9s PRYDMqNxJMQ7H8l8Ao5A5pvM+7uZmvq0fWNl5YH8QdKZ2JaIZoBmhesTfd0jVn3KoLTd p8lN9H9/UEIQ+SjM/ylSA9mfuAQ2ZKeHeGg7g= MIME-Version: 1.0 Received: by 10.236.175.35 with SMTP id y23mr7034754yhl.495.1311636803488; Mon, 25 Jul 2011 16:33:23 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.236.108.129 with HTTP; Mon, 25 Jul 2011 16:33:23 -0700 (PDT) In-Reply-To: <254152988.989678.1311630244759.JavaMail.root@erie.cs.uoguelph.ca> References: <20110725162323.GA27425@troutmask.apl.washington.edu> <254152988.989678.1311630244759.JavaMail.root@erie.cs.uoguelph.ca> Date: Tue, 26 Jul 2011 01:33:23 +0200 X-Google-Sender-Auth: 73DkEYepctWxLfWgU052WZtKUmM Message-ID: From: Attilio Rao To: Rick Macklem Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Andriy Gapon , Steve Kargl Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Jul 2011 23:33:24 -0000 Do you have a corefile for this panic? Attilio 2011/7/25 Rick Macklem : > Steve Kargl wrote: >> On Mon, Jul 25, 2011 at 01:00:27PM +0300, Andriy Gapon wrote: >> > on 12/07/2011 11:05 Andriy Gapon said the following: >> > > I think that the best thing you can further provide (as objective >> > > evidence for >> > > the problem at hand) is ktr(4) traces for at least KTR_SCHED mask. >> > > Perhaps you >> > > even already have them from your previous sessions with Jeff. >> > > >> > > P.S. This is not a promise to actually debug this issue based on >> > > the traces :-) >> > >> > So do you have an opportunity to provide this kind of information? >> > Actually I would like KTR_SCHED|KTR_INTR|KTR_PROC|KTR_SYSC mask. >> > Also, sysctl kern.sched output would be useful too. >> > This is for the ULE case, of course. >> > >> >> I won't have time until next week to investigate. >> > hrs sent me this panic. I'm wondering if it might be relevant to this? > spin lock 0xffffffff80cb52c0 (sched lock 1) held by 0xffffff0012c7f8c0 (t= id 100317) too long > panic: spin lock held too long > cpuid =3D 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > _mtx_lock_spin_failed() at _mtx_lock_spin_failed+0x39 > _mtx_lock_spin() at _mtx_lock_spin+0x9e > sched_add() at sched_add+0x117 > setrunnable() at setrunnable+0x78 > sleepq_signal() at sleepq_signal+0x7a > cv_signal() at cv_signal+0x3b > xprt_active() at xprt_active+0xe3 > svc_vc_soupcall() at svc_vc_soupcall+0xc > sowakeup() at sowakeup+0x69 > tcp_do_segment() at tcp_do_segment+0x2cbd > tcp_input() at tcp_input+0xcdd > ip_input() at ip_input+0xac > netisr_dispatch_src() at netisr_dispatch_src+0x7e > ether_demux() at ether_demux+0x14d > ether_input() at ether_input+0x17d > em_rxeof() at em_rxeof+0x1ca > em_handle_que() at em_handle_que+0x5b > taskqueue_run_locked() at taskqueue_run_locked+0x85 > taskqueue_thread_loop() at taskqueue_thread_loop+0x4e > fork_exit() at fork_exit+0x11f > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip =3D 0, rsp =3D 0xffffff8000160d00, rbp =3D 0 --- > KDB: enter: panic > [thread pid 0 tid 100033 ] > Stopped at =C2=A0 =C2=A0 =C2=A0kdb_enter+0x3b: movq =C2=A0 =C2=A0$0,0x6b4= e62(%rip) > db> ps > > _______________________________________________ > 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 Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 00:09:40 2011 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C440E1065678; Tue, 26 Jul 2011 00:09:40 +0000 (UTC) (envelope-from vadim@nuclight.avtf.net) Received: from nuclight.avtf.net (208.88.188.90.adsl.tomsknet.ru [90.188.88.208]) by mx1.freebsd.org (Postfix) with ESMTP id BEAC58FC1D; Tue, 26 Jul 2011 00:09:39 +0000 (UTC) Received: from kernblitz.nuclight.avtf.net (vadim@localhost [127.0.0.1]) by nuclight.avtf.net (8.14.4/8.14.4) with ESMTP id p6PNg7WW076229; Tue, 26 Jul 2011 06:42:08 +0700 (NOVST) (envelope-from vadim@kernblitz.nuclight.avtf.net) Received: (from vadim@localhost) by kernblitz.nuclight.avtf.net (8.14.4/8.14.4/Submit) id p6PNg6Pn076226; Tue, 26 Jul 2011 06:42:06 +0700 (NOVST) (envelope-from vadim) Message-Id: <201107252342.p6PNg6Pn076226@kernblitz.nuclight.avtf.net> To: Daniel Gerzo From: Vadim Goncharov In-Reply-To: <4E0B0299.2020205@FreeBSD.org> References: <4E0B0299.2020205@FreeBSD.org> X-Comment-To: Daniel Gerzo Date: Tue, 26 Jul 2011 06:42:05 +0700 User-Agent: slrn/0.9.9p1 (FreeBSD) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADSUP: Call for FreeBSD Status Reports - 2Q/2011 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vadim_nuclight@mail.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 00:09:40 -0000 Hi Daniel Gerzo! On Wed, 29 Jun 2011 12:46:49 +0200; Daniel Gerzo wrote: > Do not hesitate and write us a few lines; a short description about > what you are working on, what your plans and goals are, or any other > information that you consider interested is always welcome. This way > we can inform our community about your great work! > Check out the reports from the past to get some inspiration of what > your submission should look like. [...] > Note that the submissions are accepted from anyone involved within the > FreeBSD community, you do not have to be a FreeBSD committer. Anything > related to FreeBSD can be covered. > Please email us the filled-in XML template which can be found at > http://www.freebsd.org/news/status/report-sample.xml to > monthly@FreeBSD.org, or alternatively use our web based form located at > http://www.freebsd.org/cgi/monthly.cgi. A note for the future: you will tend to receive more submissions if you will make life a lot easier for submitter. The most natural way of using the aforementioned Web form - as, surprise, a Web form (BTW, the field to type in is too small and thus uncomfortable). That is, result of clicking "Submit" button must be immediately sending info to central base, requiring no further work from submitter to cut-n-paste the thing to e-mail. This is just frightening to everyone who is not a FreeBSD committer, with regard to needing to send this info to another e-mail which it suggests! (I was told that in IRC, and fro where has the Joe Random Contributor to know this?) We will have more docs when a contributor is not forced to efforts which are unneeded. Having to do such things which could be easily done on server-side looks just too unpolite for those who came in - and some of them will turn away from sending. P.S. This is general principle, not only for docs - forcing user to do something which could be already done by maintainer turns away from the system many of them. -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight] From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 01:51:43 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 447CD1065675 for ; Tue, 26 Jul 2011 01:51:43 +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 149618FC1A for ; Tue, 26 Jul 2011 01:51:42 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LOX00A003U67D00@smtpauth2.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Mon, 25 Jul 2011 20:51:42 -0500 (CDT) Received: from comporellon.tachypleus.net ([unknown] [76.210.68.180]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LOX002M23U4C510@smtpauth2.wiscmail.wisc.edu>; Mon, 25 Jul 2011 20:51:41 -0500 (CDT) Date: Mon, 25 Jul 2011 20:51:40 -0500 From: Nathan Whitehorn In-reply-to: To: vadim_nuclight@mail.ru Message-id: <4E2E1DAC.9030906@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.210.68.180 X-Spam-PmxInfo: Server=avs-9, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.7.26.14515, SenderIP=76.210.68.180 References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110704 Thunderbird/5.0 Cc: freebsd-current@freebsd.org Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 01:51:43 -0000 On 07/25/11 18:12, Vadim Goncharov wrote: > Hi Freddie Cash! > > On Sun, 24 Jul 2011 22:01:44 -0700; Freddie Cash wrote about 'Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer.': > >>> 3) I see no "post-install" uses on the new one. Sysinstall could be used >> on an up-and-running system to do everything from adding a user to changing >> a nameserver and more. >> Thank goodness. The worst thing about sysinstall was that it tried to be a >> Swiss Army knife doing everything, yet not doing any one thing well. It made >> a royal mess of rc.conf if you tried to use it to configure a system. >> Usually the first time someone mentions they use it for post-install >> configuration, the recommendation is to stop doing that! >> An os installer should do just that: install the os and nothing else. > No. That's wrong. An installer should make a usable system. While using > sysinstall for configuration multiple times made a mess, it is still needed > to make configuration the _first time_ - and it really did, without any mess. > You've got a working keyboard, TTY, network, users/passwords, etc. - before > reboot. This is something which must be intuitive for a new user, even if > it is used only one time in the system's life (at the installation). Cutting > it - is a regression. > That all works perfectly fine. The issue is whether it is useful for post-install configuration, which is something different entirely. -Nathan From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 04:04:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0B20106564A for ; Tue, 26 Jul 2011 04:04:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 8D44D8FC08 for ; Tue, 26 Jul 2011 04:04:25 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id p6Q445gQ010336; Mon, 25 Jul 2011 22:04:05 -0600 (MDT) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Scott Long In-Reply-To: Date: Mon, 25 Jul 2011 22:04:05 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110724162937.33865zm0kn4ztdwk@econet.encontacto.net> <4E2C8FBE.7040003@freebsd.org> <4E2CA4A7.7020100@fuzzwad.org> <4E2D125F.6040909@cran.org.uk> To: Freddie Cash X-Mailer: Apple Mail (2.1084) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: Bruce Cran , freebsd-current , Ron McDowell , Nathan Whitehorn , eculp Subject: Re: Trying to install current from a memory stick and then a DVD and got a new and strange installer. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 04:04:26 -0000 On Jul 25, 2011, at 11:36 AM, Freddie Cash wrote: > On Sun, Jul 24, 2011 at 11:51 PM, Bruce Cran = wrote: >=20 >> On 25/07/2011 06:01, Freddie Cash wrote: >>=20 >>> Thank goodness. The worst thing about sysinstall was that it tried = to be a >>> Swiss Army knife doing everything, yet not doing any one thing well. = It made >>> a royal mess of rc.conf if you tried to use it to configure a = system. >>> Usually the first time someone mentions they use it for post-install >>> configuration, the recommendation is to stop doing that! An os = installer >>> should do just that: install the os and nothing else. >>>=20 >>=20 >> I tend to disagree with this. For people unfamiliar with FreeBSD = using it >> as a systems administration tool can be really useful, at least until = they >> understand where all the various configuration files are and how they = work. >> Having recently switched to opensuse from Ubuntu I know I find the = YaST >> tool incredibly useful, and probably wouldn't have continued using = SuSE if >> it hadn't been there. Its installer mode is one of the better = installers >> I've come across, and lets you fine-tune the configuration. >>=20 >=20 > The difference is that YaST was designed from the get-go to be both a = system > management tool and a software installation tool and a system = installation > tool. Sysinstall was not, and sysinstall used as a post-install = management > tool the past couple of years has caused more issues for newbies than = it's > "solved". Um, no. Though sysinstall started life as a stop-gap until the "real" = installer was written (which never happened), it quickly switched gears = and strived to be both an installer and a configuration tool. It was = designed to do both, and there are volumes of emails from the last... = what... 15-18 years?... that will attest to this. The design flaw of = sysinstall was that it didn't follow the model-view-controller design = pattern, so over time it became harder and harder to maintain it, and it = essentially rotted as the system evolved around it, despite many valiant = efforts by many tireless developers. YaST did a much better job of = following the MVC pattern, and it shows 10 years later. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 12:05:19 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E7AB1065675; Tue, 26 Jul 2011 12:05:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 241728FC0C; Tue, 26 Jul 2011 12:05:19 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BDAB146B0C; Tue, 26 Jul 2011 08:05:18 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 318038A02E; Tue, 26 Jul 2011 08:05:18 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 26 Jul 2011 08:03:47 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <7042b10f5837cf0b5cd8805ab3a46795@etoilebsd.net> <6ffed3eeaecff37888be8aa07d6157d7@etoilebsd.net> In-Reply-To: <6ffed3eeaecff37888be8aa07d6157d7@etoilebsd.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107260803.47625.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Jul 2011 08:05:18 -0400 (EDT) Cc: Baptiste Daroussin Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 12:05:19 -0000 On Monday, July 25, 2011 6:14:12 pm Baptiste Daroussin wrote: > On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote: > > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: > >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: > >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: > >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: > >>> >> Hi, > >>> >> > >>> >> Trying to upgrade one of my box from 8-stable to 9-current lead > >>> >> be to some important problems. > >>> >> > >>> >> I'm have tried both from sources (svn buildworld etc.) and from > >>> >> memdisk provided by allbsd.org. > >>> >> > >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 > >>> >> > >>> >> more informations here : > >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and > >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt > >>> > > >>> > Can you get a verbose dmesg from 8-stable? > >>> > >>> A boot -v from current memdisk is full of: > >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 > >>> 00 > >>> 00 00 00 > >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout > >>> > >>> here is the dmesg from boot -v on 8-stable: > >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt > >>> > >>> the xpt_config message disapear by removing sbp from the kernel > >> > >> It seems that you have an ATAPI floppy-drive device that 8 doesn't > >> like: > >> > >> afd0: setting PIO3 > >> device_attach: afd0 attach returned 6 > >> > >> Have you tried enabling ATA_CAM on 8 as a test, or removing the > >> ATAPI floppy-drive as a test? > > > > Ok I'm dumb, I tested atapicam instead of ata_cam. > > > > I rebuild 8-stable kernel with ATA_CAM and it works (with lots of > > warnings concerning the dvdrw). > > > > Here is the 8-stable dmesg with boot -v: > > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt > > New informations it doesn't work either on -CURRENT without ATA_CAM. Hmm, can you break into ddb on 9 and run 'show intrcnt' to see if you have non-zero interrupt counts for IRQs 14 and 15? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 13:46:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8D86106564A for ; Tue, 26 Jul 2011 13:46:41 +0000 (UTC) (envelope-from alp@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id 15A348FC1E for ; Tue, 26 Jul 2011 13:46:40 +0000 (UTC) Received: from pyhalov.cc.rsu.ru (pyhalov.cc.rsu.ru [195.208.252.128]) (authenticated bits=0) by mail.r61.net (8.14.4/8.14.4) with ESMTP id p6QDW560012075 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Tue, 26 Jul 2011 17:32:05 +0400 (MSD) (envelope-from alp@rsu.ru) Message-ID: <4E2EC1D4.20302@rsu.ru> Date: Tue, 26 Jul 2011 17:32:04 +0400 From: Alexander Pyhalov User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110306 Thunderbird/3.1.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: rctl limit cpu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 13:46:41 -0000 Hello. I see in rctl man page, that I can limit cpu time in milliseconds, e.g., for jail. But I can't deny allocation of the resource (according to man page). In Solaris I can assign different amount of cpu shares to different projects. How can I achieve this with rctl? For example, I'd like to give jail:www 40% CPU, jail:db - 50% CPU and leave 10% to the base system... -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 17:40:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D0641065676 for ; Tue, 26 Jul 2011 17:40:22 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id 154698FC21 for ; Tue, 26 Jul 2011 17:40:21 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id F2A8C7E823; Tue, 26 Jul 2011 19:40:20 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Jul 2011 17:40:20 +0000 From: Baptiste Daroussin In-Reply-To: <201107260803.47625.jhb@freebsd.org> References: <7042b10f5837cf0b5cd8805ab3a46795@etoilebsd.net> <6ffed3eeaecff37888be8aa07d6157d7@etoilebsd.net> <201107260803.47625.jhb@freebsd.org> Message-ID: X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 17:40:22 -0000 On Tue, 26 Jul 2011 08:03:47 -0400, John Baldwin wrote: > On Monday, July 25, 2011 6:14:12 pm Baptiste Daroussin wrote: >> On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote: >> > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: >> >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >> >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >> >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: >> >>> >> Hi, >> >>> >> >> >>> >> Trying to upgrade one of my box from 8-stable to 9-current >> lead >> >>> >> be to some important problems. >> >>> >> >> >>> >> I'm have tried both from sources (svn buildworld etc.) and >> from >> >>> >> memdisk provided by allbsd.org. >> >>> >> >> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >> >>> >> >> >>> >> more informations here : >> >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >> >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >> >>> > >> >>> > Can you get a verbose dmesg from 8-stable? >> >>> >> >>> A boot -v from current memdisk is full of: >> >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 >> 00 >> >>> 00 >> >>> 00 00 00 >> >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout >> >>> >> >>> here is the dmesg from boot -v on 8-stable: >> >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >> >>> >> >>> the xpt_config message disapear by removing sbp from the kernel >> >> >> >> It seems that you have an ATAPI floppy-drive device that 8 >> doesn't >> >> like: >> >> >> >> afd0: setting PIO3 >> >> device_attach: afd0 attach returned 6 >> >> >> >> Have you tried enabling ATA_CAM on 8 as a test, or removing the >> >> ATAPI floppy-drive as a test? >> > >> > Ok I'm dumb, I tested atapicam instead of ata_cam. >> > >> > I rebuild 8-stable kernel with ATA_CAM and it works (with lots of >> > warnings concerning the dvdrw). >> > >> > Here is the 8-stable dmesg with boot -v: >> > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt >> >> New informations it doesn't work either on -CURRENT without ATA_CAM. > > Hmm, can you break into ddb on 9 and run 'show intrcnt' to see if you > have non-zero interrupt counts for IRQs 14 and 15? the result is: db> show intrcnt cpu0: timer 4510 irq256: hdac0 1 cpu3: timer 29 cpu1: timer 3036 cpu2: timer 31 db> I did break at the mountfrom> prompt If I break before I only have the cpu0 and irq256 entries. regards, Bapt From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 19:45:17 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50E96106564A; Tue, 26 Jul 2011 19:45:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E39DA8FC0A; Tue, 26 Jul 2011 19:45:16 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7A5F546B3C; Tue, 26 Jul 2011 15:45:16 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 178858A037; Tue, 26 Jul 2011 15:45:16 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 26 Jul 2011 15:44:51 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <201107260803.47625.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201107261544.51244.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Jul 2011 15:45:16 -0400 (EDT) Cc: Baptiste Daroussin Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 19:45:17 -0000 On Tuesday, July 26, 2011 1:40:20 pm Baptiste Daroussin wrote: > On Tue, 26 Jul 2011 08:03:47 -0400, John Baldwin wrote: > > On Monday, July 25, 2011 6:14:12 pm Baptiste Daroussin wrote: > >> On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote: > >> > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: > >> >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: > >> >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: > >> >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin wrote: > >> >>> >> Hi, > >> >>> >> > >> >>> >> Trying to upgrade one of my box from 8-stable to 9-current > >> lead > >> >>> >> be to some important problems. > >> >>> >> > >> >>> >> I'm have tried both from sources (svn buildworld etc.) and > >> from > >> >>> >> memdisk provided by allbsd.org. > >> >>> >> > >> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 > >> >>> >> > >> >>> >> more informations here : > >> >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and > >> >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt > >> >>> > > >> >>> > Can you get a verbose dmesg from 8-stable? > >> >>> > >> >>> A boot -v from current memdisk is full of: > >> >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 > >> 00 > >> >>> 00 > >> >>> 00 00 00 > >> >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout > >> >>> > >> >>> here is the dmesg from boot -v on 8-stable: > >> >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt > >> >>> > >> >>> the xpt_config message disapear by removing sbp from the kernel > >> >> > >> >> It seems that you have an ATAPI floppy-drive device that 8 > >> doesn't > >> >> like: > >> >> > >> >> afd0: setting PIO3 > >> >> device_attach: afd0 attach returned 6 > >> >> > >> >> Have you tried enabling ATA_CAM on 8 as a test, or removing the > >> >> ATAPI floppy-drive as a test? > >> > > >> > Ok I'm dumb, I tested atapicam instead of ata_cam. > >> > > >> > I rebuild 8-stable kernel with ATA_CAM and it works (with lots of > >> > warnings concerning the dvdrw). > >> > > >> > Here is the 8-stable dmesg with boot -v: > >> > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt > >> > >> New informations it doesn't work either on -CURRENT without ATA_CAM. > > > > Hmm, can you break into ddb on 9 and run 'show intrcnt' to see if you > > have non-zero interrupt counts for IRQs 14 and 15? > > > the result is: > db> show intrcnt > cpu0: timer 4510 > irq256: hdac0 1 > cpu3: timer 29 > cpu1: timer 3036 > cpu2: timer 31 > db> > > I did break at the mountfrom> prompt > If I break before I only have the cpu0 and irq256 entries. Hmmm, is there any way you can build a 9 kernel without sound support (since that clutters up bootverbose) and capture a verbose dmesg, using a serial console or PXE booting to an NFS root of some sort? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 21:23:57 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27690106566B for ; Tue, 26 Jul 2011 21:23:57 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from xiurhn.etoilebsd.net (xiurhn.etoilebsd.net [94.23.37.58]) by mx1.freebsd.org (Postfix) with ESMTP id E32768FC0C for ; Tue, 26 Jul 2011 21:23:56 +0000 (UTC) Received: by xiurhn.etoilebsd.net (Postfix, from userid 80) id 160F37E81F; Tue, 26 Jul 2011 23:23:56 +0200 (CEST) To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 26 Jul 2011 21:23:56 +0000 From: Baptiste Daroussin In-Reply-To: <201107261544.51244.jhb@freebsd.org> References: <201107260803.47625.jhb@freebsd.org> <201107261544.51244.jhb@freebsd.org> Message-ID: <1307f14f363d9ee49105220ed2697fa0@etoilebsd.net> X-Sender: bapt@FreeBSD.org User-Agent: Roundcube Webmail/0.5.3 Subject: Re: No disks usable on a P5NE MB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 21:23:57 -0000 On Tue, 26 Jul 2011 15:44:51 -0400, John Baldwin wrote: > On Tuesday, July 26, 2011 1:40:20 pm Baptiste Daroussin wrote: >> On Tue, 26 Jul 2011 08:03:47 -0400, John Baldwin wrote: >> > On Monday, July 25, 2011 6:14:12 pm Baptiste Daroussin wrote: >> >> On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote: >> >> > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote: >> >> >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote: >> >> >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote: >> >> >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin >> wrote: >> >> >>> >> Hi, >> >> >>> >> >> >> >>> >> Trying to upgrade one of my box from 8-stable to 9-current >> >> lead >> >> >>> >> be to some important problems. >> >> >>> >> >> >> >>> >> I'm have tried both from sources (svn buildworld etc.) and >> >> from >> >> >>> >> memdisk provided by allbsd.org. >> >> >>> >> >> >> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901 >> >> >>> >> >> >> >>> >> more informations here : >> >> >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and >> >> >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt >> >> >>> > >> >> >>> > Can you get a verbose dmesg from 8-stable? >> >> >>> >> >> >>> A boot -v from current memdisk is full of: >> >> >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 >> 00 >> >> 00 >> >> >>> 00 >> >> >>> 00 00 00 >> >> >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout >> >> >>> >> >> >>> here is the dmesg from boot -v on 8-stable: >> >> >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt >> >> >>> >> >> >>> the xpt_config message disapear by removing sbp from the >> kernel >> >> >> >> >> >> It seems that you have an ATAPI floppy-drive device that 8 >> >> doesn't >> >> >> like: >> >> >> >> >> >> afd0: setting PIO3 >> >> >> device_attach: afd0 attach returned 6 >> >> >> >> >> >> Have you tried enabling ATA_CAM on 8 as a test, or removing >> the >> >> >> ATAPI floppy-drive as a test? >> >> > >> >> > Ok I'm dumb, I tested atapicam instead of ata_cam. >> >> > >> >> > I rebuild 8-stable kernel with ATA_CAM and it works (with lots >> of >> >> > warnings concerning the dvdrw). >> >> > >> >> > Here is the 8-stable dmesg with boot -v: >> >> > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt >> >> >> >> New informations it doesn't work either on -CURRENT without >> ATA_CAM. >> > >> > Hmm, can you break into ddb on 9 and run 'show intrcnt' to see if >> you >> > have non-zero interrupt counts for IRQs 14 and 15? >> >> >> the result is: >> db> show intrcnt >> cpu0: timer 4510 >> irq256: hdac0 1 >> cpu3: timer 29 >> cpu1: timer 3036 >> cpu2: timer 31 >> db> >> >> I did break at the mountfrom> prompt >> If I break before I only have the cpu0 and irq256 entries. > > Hmmm, is there any way you can build a 9 kernel without sound support > (since > that clutters up bootverbose) and capture a verbose dmesg, using a > serial > console or PXE booting to an NFS root of some sort? Hum unfortunatly not, this box is ... alone, so I can't netboot it :( Bapt From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 12:29:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FA96106566B for ; Tue, 26 Jul 2011 12:29:50 +0000 (UTC) (envelope-from benalexanders@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 536F08FC0A for ; Tue, 26 Jul 2011 12:29:50 +0000 (UTC) Received: by gwb15 with SMTP id 15so242968gwb.13 for ; Tue, 26 Jul 2011 05:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=OobPiDZximRTMluu/27XcQiVSK1wGlGYfLfgtlXqodg=; b=s20vMO/4MeJgw1Uu9W8DYlr7z18Omp1Qj72/MHacVWgWb7mVM2kdWRypKXuSCawaAO BFhypu/iuNuMC37C5spCCY/8CE8YzCg7H0MeDzU8N9IDIPDqqD+LTclHR4DkK7B15sqk aC5jXy4DRa6Ww/1MuY5YE60YgXY2P2rBtJqkc= MIME-Version: 1.0 Received: by 10.223.155.130 with SMTP id s2mr597664faw.2.1311681630650; Tue, 26 Jul 2011 05:00:30 -0700 (PDT) Received: by 10.223.95.198 with HTTP; Tue, 26 Jul 2011 05:00:30 -0700 (PDT) Date: Tue, 26 Jul 2011 22:00:30 +1000 Message-ID: From: Ben Ellis To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 26 Jul 2011 23:03:07 +0000 Subject: virtualbox-ose 4.0.8 fails X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 12:29:50 -0000 > On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim >> > >> > wrote: >> >> >> Any ideas regarding the virtualbox itself ? >> >> > >> >> > I am rebuilding world/kernel now. =EF=BF=BDAfter that, I'll rebuild >> >> > virtualbox-ose and try to fix it unless someone beat me to it. >> >> > >> >> > :-) >> >> > >> >> > Jung-uk Kim >> >> >> >> Brilliant !!! >> > >> > Please try this patch: >> > >> > http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server-fr >> >eebsd-HostHardwareFreeBSD.cpp >> > >> > Just drop this in ports/emulators/virtualbox-ose/files and >> > rebuild. >> >> Thanks a lot, they look good. Do you agree that those two patches >> are licensed under MIT License so that i can push them upstream? > > Yes, of course. Please feel free. Hi guys, I am still having this issue building virtualbox on freebsd-current. I initially had some errors with some lib32 files (crt*) but thought I had over-come these issues. The HostHardwareFreeBSD.cpp patch described above appears to have been applied already, so I am at a loss as to what do next. It's a fairly vanilla build, the main difference is that I used the text installer to get a GUI-less build (for my headless machine). For this reason, I have also excluded qt in the virtualbox-ose config. As this is my first post on here, please allow me to overshare my setup, as well as the actual error below: Cheers # uname -a FreeBSD jupiter 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu May 12 15:34:46 UTC 2011 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # grep \=3D /usr/ports/emulators/virtualbox-ose/Makefile | head -2 PORTNAME=3D =C2=A0 =C2=A0 =C2=A0 virtualbox-ose DISTVERSION=3D =C2=A0 =C2=A04.0.12 # grep -v \# /var/db/ports/virtualbox-ose/options _OPTIONS_READ=3Dvirtualbox-ose-4.0.12 WITHOUT_QT4=3Dtrue WITHOUT_DEBUG=3Dtrue WITH_GUESTADDITIONS=3Dtrue WITH_DBUS=3Dtrue WITHOUT_PULSEAUDIO=3Dtrue WITHOUT_X11=3Dtrue WITH_VDE=3Dtrue WITH_VNC=3Dtrue WITHOUT_WEBSERVICE=3Dtrue WITHOUT_NLS=3Dtrue # And the final stage of the build... kBuild: Pass - Programs kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp kBuild: Compiling VBoxSVC - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/PerformanceFreeBSD.cpp /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp: In function 'int getDVDInfoFromCAM(DriveInfoList*, bool*)': /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:195: error: 'struct device_match_pattern' has no member named 'data' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:196: error: 'struct device_match_pattern' has no member named 'data' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:197: error: 'struct device_match_pattern' has no member named 'data' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:198: error: 'struct device_match_pattern' has no member named 'data' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:199: error: 'struct device_match_pattern' has no member named 'data' /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp:253: warning: invalid conversion from 'int' to 'periph_pattern_flags' kmk: *** [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/ou= t/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.= o] Error 1 The failing command: @c++ -c -O2 -g -pipe -Wshadow -Wno-long-long -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -O2 -mtune=3Dgeneric -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=3Dhidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -g -pipe -Wshadow -Wno-long-long -Wno-variadic-macros -Wno-long-long -Wno-non-virtual-dtor -Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -O2 -mtune=3Dgeneric -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden -fvisibility=3Dhidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -m64 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/M= ain/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/obj/VBoxSVC -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/obj/Main/ -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/M= ain -I/usr/include -I/usr/X11R6/include -I/usr/local/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include/string -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include/xpcom -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include/nsprpub -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release/bin/sdk/bindings/xpcom/include/ipcd -I/usr/local/include/libpng -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/include -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/freebs= d.amd64/release -DVBOX -DVBOX_WITH_DEBUGGER -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=3D\"/usr/local/share/virtualbox-ose\" -DRTPATH_APP_PRIVATE_ARCH=3D\"/usr/local/lib/virtualbox\" -DRTPATH_SHARED_LIBS=3D\"/usr/local/lib/virtualbox\" -DRTPATH_APP_DOCS=3D\"/usr/local/share/doc/virtualbox-ose\" -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DIN_RING3 -DUNICODE -DNDEBUG=3D1 -DVBOX_WITH_XPCOM -DVBOX_MAIN_SETTINGS_ADDONS -DIN_VMM_STATIC -DVBOX_WITH_SYS_V_IPC_SESSION_WATCHER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_NETFLT -DVBOX_WITH_GUEST_PROPS -DVBOX_WITH_GUEST_CONTROL -DVBOX_WITH_HOSTNETIF_API -DVBOX_WITH_VDE -DVBOX_WITH_NEW_SYS_V_KEYGEN -DVBOX_WITH_HEADLESS -DVBOX_WITH_HGCM -DVBOX_WITH_ALSA -DVBOX_WITH_E1000 -DVBOX_WITH_VIRTIO -DVBOX_WITH_AHCI -DVBOX_WITH_LSILOGIC -DVBOX_WITH_RESOURCE_USAGE_API -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_EXTPACK -DVBOX_WITH_VUSB -DVBOX_WITH_S3 -DVBOX_WITH_USB -DVBOX_WITH_EHCI -DVBOX_WITH_NEW_USB_CODE_ON_DARWIN -DVBOX_WITH_HOSTNETIF_API -DVBOX_USE_LIBHAL -Wp,-MD,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/= freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o.= dep -Wp,-MT,/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/out/= freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD.o -Wp,-MP -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/o= ut/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/HostHardwareFreeBSD= .o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.12_OSE/src/VBox/Mai= n/src-server/freebsd/HostHardwareFreeBSD.cpp kmk: *** Waiting for unfinished jobs.... kmk: *** Exiting with status 2 *** Error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 23:16:30 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 47050106566B; Tue, 26 Jul 2011 23:16:30 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 26 Jul 2011 19:16:15 -0400 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Message-Id: <201107261916.18299.jkim@FreeBSD.org> Cc: Ben Ellis Subject: Re: virtualbox-ose 4.0.8 fails X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 23:16:30 -0000 On Tuesday 26 July 2011 08:00 am, Ben Ellis wrote: > > On Saturday 25 June 2011 10:28 am, Bernhard Froehlich wrote: > >> On Fri, 24 Jun 2011 16:11:27 -0400, Jung-uk Kim wrote: > >> > On Friday 24 June 2011 02:58 pm, George Kontostanos wrote: > >> >> On Fri, Jun 24, 2011 at 9:51 PM, Jung-uk Kim >> >> freebsd.org> > >> > > >> > wrote: > >> >> >> Any ideas regarding the virtualbox itself ? > >> >> > > >> >> > I am rebuilding world/kernel now. 占�After that, I'll > >> >> > rebuild virtualbox-ose and try to fix it unless someone > >> >> > beat me to it. > >> >> > > >> >> > :-) > >> >> > > >> >> > Jung-uk Kim > >> >> > >> >> Brilliant !!! > >> > > >> > Please try this patch: > >> > > >> > http://people.freebsd.org/~jkim/patch-src-VBox-Main-src-server > >> >-fr eebsd-HostHardwareFreeBSD.cpp > >> > > >> > Just drop this in ports/emulators/virtualbox-ose/files and > >> > rebuild. > >> > >> Thanks a lot, they look good. Do you agree that those two > >> patches are licensed under MIT License so that i can push them > >> upstream? > > > > Yes, of course. Please feel free. > > Hi guys, > > I am still having this issue building virtualbox on > freebsd-current. > > I initially had some errors with some lib32 files (crt*) but > thought I had over-come these issues. > The HostHardwareFreeBSD.cpp patch described above appears to have > been applied already, so I am at a loss as to what do next. > > It's a fairly vanilla build, the main difference is that I used the > text installer to get a GUI-less build (for my headless machine). > For this reason, I have also excluded qt in the virtualbox-ose > config. > > As this is my first post on here, please allow me to overshare my > setup, as well as the actual error below: > > Cheers > > > # uname -a > FreeBSD jupiter 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu May 12 > 15:34:46 UTC 2011 > root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 [SNIP] Your world/kernel is too old. Rebuild and install world/kernel or install 9.0-BETA1 when it is ready. Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 23:38:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id A4F88106566C; Tue, 26 Jul 2011 23:38:13 +0000 (UTC) Date: Tue, 26 Jul 2011 23:38:13 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20110726233813.GA55491@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: issues with vmstat and latest HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Jul 2011 23:38:13 -0000 hi there, 'vmstat -m' and 'vmstat -z' report: otaku% vmstat -m vmstat: memstat_sysctl_malloc: Too many CPUs otaku% vmstat -z vmstat: memstat_sysctl_uma: Too many CPUs world and kernel are in sync. i'm running r224294 on amd64. cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 00:30:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 157C21065676; Wed, 27 Jul 2011 00:30:04 +0000 (UTC) Date: Wed, 27 Jul 2011 00:30:04 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20110727003004.GA61713@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: truss crashing process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 00:30:04 -0000 hi there, i was trying to attach truss to chromium via 'truss -p 18445' and got: [...] kevent(26,{},0,{0x1b,EVFILT_READ,0x0,0,0x1,0x44cb600 0x0,0x0,0x0,0,0x0,0x0 = 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0= x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,= 0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0= x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,= 0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0= x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x= 0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0= x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x= 0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0= x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x= 0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0= ,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x= 0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0= ,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x= 0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0= ,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,= 0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0= 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,= 0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0= ,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,= 0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0= ,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 = 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0= x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,= 0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0= x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,= 0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0= x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x= 0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0= x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x= 0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0= x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x= 0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0= ,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0},64,{9.469312000 }) =3D 116 (0x74) -- UNKNOWN SYSCALL -14720592 -- write(-14720976,0x8080808080808000,0) =3D 41 (0x29) select(94,0x6acd,{0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 2= 2 23 24 25 26 27 28 29 30 31 40 41 42 43 44 45 46 70 71 72 73 76 77 78 79 8= 0 81 82 84 87 88 91},0x1,{0.85048848 }) =3D 73 (0x49) -- UNKNOWN SYSCALL 303120384 -- #94(0x0,0x0,0x5e,0xb6cd600,0x83ed780,0x3dae410) =3D 189 (0xbd) truss: Cannot malloc -14740096 bytes for fd_set array: Cannot allocate memo= ry =2E.. this is 100% reproducable, if i wait long enough. this will crash tru= ss along with chromium. using '-f' in addition to the flags above gives me: [...] truss: Cannot malloc -4220992 bytes for fd_set array: Cannot allocate memory otaku% truss: can not attach to target process: No such process strange thing though, when i redirect the first command via '> bla 2>&1', t= russ leaves behind a core file, because it segfaults. without redirecting the output, no core file gets created, because truss doesn't segfault. cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 00:48:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 3EB211065675; Wed, 27 Jul 2011 00:48:50 +0000 (UTC) Date: Wed, 27 Jul 2011 00:48:50 +0000 From: Alexander Best To: Matthias Andree Message-ID: <20110727004850.GA63109@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E2D2C32.5010602@gmx.de> Cc: Norberto Lopes , Adrian Chadd , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 00:48:50 -0000 On Mon Jul 25 11, Matthias Andree wrote: > Am 25.07.2011 09:21, schrieb Alexander Best: > > On Mon Jul 25 11, Adrian Chadd wrote: > >> Is it perhaps doing disk IO using mmap? > > > > how can i check, whether that's the case or not? > > Use truss(1) for instance. > > However, unless there are *practical* problems, a high number of page > faults is not an indication for problems. Although it may sound scary, > page faults are a feature of the memory management. unfortunately truss(1) is crashing chromium :( i opened up a new thread reagarding this issue on freebsd-current@. another thing i noticed is the increase in system calls caused by chromium. let's have a look at hub.freebsd.org: uptime = 149 days and 'vmstat -s' reports: 2168697753 cpu context switches 2266220366 device interrupts 2902880931 software interrupts 3779075897 traps 902107847 system calls now on my box: uptime = 2 days and 'vmstat -s' reports: 1155995386 cpu context switches 164577882 device interrupts 189456976 software interrupts 137007580 traps 2178434582 system calls i ran the following command twice. first time without running chromium and the second time with chromium running: otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" 2178187850 system calls 2178189739 system calls otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" 2177998835 system calls 2178022003 system calls so it's 2k/sec vs. 23k/sec!!!! cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 02:28:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CEB4106566C; Wed, 27 Jul 2011 02:28:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 184CE8FC15; Wed, 27 Jul 2011 02:28:03 +0000 (UTC) Received: by gyf3 with SMTP id 3so956179gyf.13 for ; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tLhPL3U9r5xEFzf/C1seLSpczzjdFqU5ZCdo/NUHFC0=; b=xcjk/Jf3C4XYI9Gp71qBOMuzP+i/hULufw/BPKo/MdJ5ydv9FgV3qBWFhfcXNx3nQb MlOh9b4GEAB7rat7DNhuFgTb+QErUT0zcjkOycXu481nMRDgUIKw9YPizayuZAsMk/0y u2t9YCl//CE0oLy4+TvEvxip0yIvMfuHRKfBE= MIME-Version: 1.0 Received: by 10.150.72.23 with SMTP id u23mr3345939yba.443.1311733683320; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Tue, 26 Jul 2011 19:28:03 -0700 (PDT) In-Reply-To: <20110727004850.GA63109@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> Date: Wed, 27 Jul 2011 10:28:03 +0800 X-Google-Sender-Auth: DKoVhWZk8jIwxJVms-cOLaLPNJg Message-ID: From: Adrian Chadd To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Norberto Lopes , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 02:28:04 -0000 Again, if it's doing lots of mmap based IO, it's likely not a big deal. Try getting dtrace to give you useful info? Adrian On 27 July 2011 08:48, Alexander Best wrote: > On Mon Jul 25 11, Matthias Andree wrote: >> Am 25.07.2011 09:21, schrieb Alexander Best: >> > On Mon Jul 25 11, Adrian Chadd wrote: >> >> Is it perhaps doing disk IO using mmap? >> > >> > how can i check, whether that's the case or not? >> >> Use truss(1) for instance. >> >> However, unless there are *practical* problems, a high number of page >> faults is not an indication for problems. =A0Although it may sound scary= , >> page faults are a feature of the memory management. > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > reagarding this issue on freebsd-current@. > > another thing i noticed is the increase in system calls caused by chromiu= m. > let's have a look at hub.freebsd.org: > > uptime =3D 149 days > > and 'vmstat -s' reports: > > 2168697753 cpu context switches > 2266220366 device interrupts > 2902880931 software interrupts > 3779075897 traps > 902107847 system calls > > now on my box: > > uptime =3D 2 days > > and 'vmstat -s' reports: > > 1155995386 cpu context switches > 164577882 device interrupts > 189456976 software interrupts > 137007580 traps > 2178434582 system calls > > i ran the following command twice. first time without running chromium an= d the > second time with chromium running: > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system cal= ls" > 2178187850 system calls > 2178189739 system calls > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system cal= ls" > 2177998835 system calls > 2178022003 system calls > > so it's 2k/sec vs. 23k/sec!!!! > > cheers. > alex > From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 08:35:02 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB85C1065672 for ; Wed, 27 Jul 2011 08:35:02 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by mx1.freebsd.org (Postfix) with ESMTP id 52E848FC08 for ; Wed, 27 Jul 2011 08:35:01 +0000 (UTC) Received: by fxe6 with SMTP id 6so63595fxe.17 for ; Wed, 27 Jul 2011 01:35:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=YNKfcHDDEi26smW7BNv/X3NBuOorMCXJG42iJR2zk5Q=; b=WSMaN+z8doTXx6iPfrj5Ga19kPsKp2oV+yV/5TBmZz/qFkY0xwe1B/Sc2tZQtYn62o CNfRS4KZcLknwEz5UkC2cim4i98TXW1Tpk17K7R2ViB52+0rbJsjnB9motLx6oxuotqC FZ0Yt+bl1lQl5VRZwQtrSzfhOEW13kBRYn9QI= Received: by 10.223.91.156 with SMTP id n28mr8050534fam.102.1311755700822; Wed, 27 Jul 2011 01:35:00 -0700 (PDT) Received: from localhost (lan-78-157-92-5.vln.skynet.lt [78.157.92.5]) by mx.google.com with ESMTPS id c1sm212409fam.22.2011.07.27.01.34.58 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 01:34:59 -0700 (PDT) Date: Wed, 27 Jul 2011 11:33:39 +0300 From: Gleb Kurtsou To: Alexander Best Message-ID: <20110727083339.GA12233@tops> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20110727004850.GA63109@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Norberto Lopes , Adrian Chadd , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 08:35:02 -0000 On (27/07/2011 00:48), Alexander Best wrote: > On Mon Jul 25 11, Matthias Andree wrote: > > Am 25.07.2011 09:21, schrieb Alexander Best: > > > On Mon Jul 25 11, Adrian Chadd wrote: > > >> Is it perhaps doing disk IO using mmap? > > > > > > how can i check, whether that's the case or not? > > > > Use truss(1) for instance. > > > > However, unless there are *practical* problems, a high number of page > > faults is not an indication for problems. Although it may sound scary, > > page faults are a feature of the memory management. > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > reagarding this issue on freebsd-current@. Could you try ktrace? It works for me > another thing i noticed is the increase in system calls caused by chromium. > let's have a look at hub.freebsd.org: > > uptime = 149 days > > and 'vmstat -s' reports: > > 2168697753 cpu context switches > 2266220366 device interrupts > 2902880931 software interrupts > 3779075897 traps > 902107847 system calls > > now on my box: > > uptime = 2 days > > and 'vmstat -s' reports: > > 1155995386 cpu context switches > 164577882 device interrupts > 189456976 software interrupts > 137007580 traps > 2178434582 system calls About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k without chrome. Looks like there is a lot of clock_gettime and gettimeofday syscalls. ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l 24343 ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) Some work was done by kib@ to create a kernel page strong current time and other misc info to eliminate gettimeofday kind syscalls. Bits of it were commited but I'm not sure if it was finished. But anyway calling gettimeofday hundreds of times per second is a chrome bug. FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 chromium-11.0.696.57_1 > i ran the following command twice. first time without running chromium and the > second time with chromium running: > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" > 2178187850 system calls > 2178189739 system calls > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" > 2177998835 system calls > 2178022003 system calls > > so it's 2k/sec vs. 23k/sec!!!! > > cheers. > alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 09:18:08 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 9653A1065673; Wed, 27 Jul 2011 09:18:08 +0000 (UTC) Date: Wed, 27 Jul 2011 09:18:08 +0000 From: Alexander Best To: Gleb Kurtsou Message-ID: <20110727091808.GA9024@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110727083339.GA12233@tops> Cc: Norberto Lopes , Adrian Chadd , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 09:18:08 -0000 On Wed Jul 27 11, Gleb Kurtsou wrote: > On (27/07/2011 00:48), Alexander Best wrote: > > On Mon Jul 25 11, Matthias Andree wrote: > > > Am 25.07.2011 09:21, schrieb Alexander Best: > > > > On Mon Jul 25 11, Adrian Chadd wrote: > > > >> Is it perhaps doing disk IO using mmap? > > > > > > > > how can i check, whether that's the case or not? > > > > > > Use truss(1) for instance. > > > > > > However, unless there are *practical* problems, a high number of page > > > faults is not an indication for problems. Although it may sound scary, > > > page faults are a feature of the memory management. > > > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > > reagarding this issue on freebsd-current@. > Could you try ktrace? It works for me > > > another thing i noticed is the increase in system calls caused by chromium. > > let's have a look at hub.freebsd.org: > > > > uptime = 149 days > > > > and 'vmstat -s' reports: > > > > 2168697753 cpu context switches > > 2266220366 device interrupts > > 2902880931 software interrupts > > 3779075897 traps > > 902107847 system calls > > > > now on my box: > > > > uptime = 2 days > > > > and 'vmstat -s' reports: > > > > 1155995386 cpu context switches > > 164577882 device interrupts > > 189456976 software interrupts > > 137007580 traps > > 2178434582 system calls > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > without chrome. > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > 24343 > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > > Some work was done by kib@ to create a kernel page strong current time > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > were commited but I'm not sure if it was finished. > But anyway calling gettimeofday hundreds of times per second is a chrome > bug. *lol* i did exactly the same measurements, you did. :) here are my results: otaku% kdump|grep "CALL mmap"|wc 724 2896 58468 otaku% kdump -s|grep "CALL clock_gettime"|wc 49545 198180 2772674 otaku% kdump -s|grep "CALL linux_clock_gettime"|wc 40185 160740 2491298 otaku% kdump -s|grep "CALL linux_gettimeofday"|wc 21670 86680 1278530 otaku% kdump -s|grep "CALL gettimeofday"|wc 8173 32692 525053 otaku% kdump -s|grep "CALL linux_sys_futex"|wc 6191 24764 548800 cheers. alex > > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 > chromium-11.0.696.57_1 > > > i ran the following command twice. first time without running chromium and the > > second time with chromium running: > > > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" > > 2178187850 system calls > > 2178189739 system calls > > > > otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" > > 2177998835 system calls > > 2178022003 system calls > > > > so it's 2k/sec vs. 23k/sec!!!! > > > > cheers. > > alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 09:21:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F9D6106564A; Wed, 27 Jul 2011 09:21:21 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id BADC28FC15; Wed, 27 Jul 2011 09:21:20 +0000 (UTC) Received: by yic13 with SMTP id 13so1127962yic.13 for ; Wed, 27 Jul 2011 02:21:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=08hIy+H3a3Da1pxlTucfset5gn68oYYx+DV/vyGxgjI=; b=AZJK1juT3DJFoS0aKc8B1cRo2F06MUagNp/oafakaooQoaA6Hevhq7iWfRZwMLHF0U g4vuYE2KoBkmyiVMr5nrcVCt+C5m9P0rRjTokJ1i0aGbTN6tS06Tt5nFz20ragLSZA1u IWaXktbsdBeoiIpqKF4RbM63PRfBWdLg3gTD4= MIME-Version: 1.0 Received: by 10.142.152.23 with SMTP id z23mr4384953wfd.186.1311756896134; Wed, 27 Jul 2011 01:54:56 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.142.199.16 with HTTP; Wed, 27 Jul 2011 01:54:56 -0700 (PDT) In-Reply-To: <20110727083339.GA12233@tops> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> Date: Wed, 27 Jul 2011 10:54:56 +0200 X-Google-Sender-Auth: _stpbdD83859XpYEUzTf7BPh3DY Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: Gleb Kurtsou Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Norberto Lopes , Alexander Best , Adrian Chadd , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 09:21:21 -0000 2011/7/27 Gleb Kurtsou : > On (27/07/2011 00:48), Alexander Best wrote: >> On Mon Jul 25 11, Matthias Andree wrote: >> > Am 25.07.2011 09:21, schrieb Alexander Best: >> > > On Mon Jul 25 11, Adrian Chadd wrote: >> > >> Is it perhaps doing disk IO using mmap? >> > > >> > > how can i check, whether that's the case or not? >> > >> > Use truss(1) for instance. >> > >> > However, unless there are *practical* problems, a high number of page >> > faults is not an indication for problems. =A0Although it may sound sca= ry, >> > page faults are a feature of the memory management. >> >> unfortunately truss(1) is crashing chromium :( i opened up a new thread >> reagarding this issue on freebsd-current@. > Could you try ktrace? It works for me > >> another thing i noticed is the increase in system calls caused by chromi= um. >> let's have a look at hub.freebsd.org: >> >> uptime =3D 149 days >> >> and 'vmstat -s' reports: >> >> 2168697753 cpu context switches >> 2266220366 device interrupts >> 2902880931 software interrupts >> 3779075897 traps >> 902107847 system calls >> >> now on my box: >> >> uptime =3D 2 days >> >> and 'vmstat -s' reports: >> >> 1155995386 cpu context switches >> 164577882 device interrupts >> 189456976 software interrupts >> 137007580 traps >> 2178434582 system calls > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > without chrome. > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > =A0 24343 > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > =A012747 chrome =A0 15.077376 CALL =A0gettimeofday(0x7fffff7f9630,0x7ffff= f7f9640) > =A012747 chrome =A0 15.077396 CALL =A0clock_gettime(0x4,0x7fffffbfb6f0) > =A012747 chrome =A0 15.077497 CALL =A0gettimeofday(0x7fffffbfb650,0x7ffff= fbfb660) > =A012747 chrome =A0 15.077609 CALL =A0gettimeofday(0x7fffffbfb650,0x7ffff= fbfb660) > =A012747 chrome =A0 15.077723 CALL =A0gettimeofday(0x7fffffbfb650,0) > =A012747 chrome =A0 15.077845 CALL =A0clock_gettime(0,0x7fffffbfb2b0) > =A012747 chrome =A0 15.078337 CALL =A0clock_gettime(0x4,0x7fffff9fa630) > =A012747 chrome =A0 15.078544 CALL =A0clock_gettime(0x4,0x7fffff9fa650) > =A012747 chrome =A0 15.078587 CALL =A0clock_gettime(0x4,0x7fffff9fa650) > =A012747 chrome =A0 15.078632 CALL =A0clock_gettime(0x4,0x7fffff9fa650) > =A012747 chrome =A0 15.078674 CALL =A0clock_gettime(0x4,0x7fffff9fa650) > =A012747 chrome =A0 15.082803 CALL =A0gettimeofday(0x7ffffedd3630,0x7ffff= edd3640) > =A012747 chrome =A0 15.084644 CALL =A0gettimeofday(0x7fffffbfb650,0x7ffff= fbfb660) > =A012747 chrome =A0 15.084746 CALL =A0clock_gettime(0x4,0x7fffffbfb670) > =A012747 chrome =A0 15.084815 CALL =A0clock_gettime(0x4,0x7fffffbfb670) > =A012747 chrome =A0 15.086620 CALL =A0gettimeofday(0x7ffffefd4650,0x7ffff= efd4660) > =A012747 chrome =A0 15.086736 CALL =A0clock_gettime(0x4,0x7ffffefd4670) > =A012747 chrome =A0 15.086815 CALL =A0clock_gettime(0x4,0x7ffffefd4670) > =A012747 chrome =A0 15.098315 CALL =A0gettimeofday(0x7fffffffafe0,0x7ffff= fffaff0) > =A012747 chrome =A0 15.098680 CALL =A0clock_gettime(0x4,0x7fffffffb250) > > Some work was done by kib@ to create a kernel page strong current time > and other misc info to eliminate gettimeofday kind syscalls. =A0Bits of i= t > were commited but I'm not sure if it was finished. > But anyway calling gettimeofday hundreds of times per second is a chrome > bug. > > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 > chromium-11.0.696.57_1 ^^^^^^^^^^^^^ Can you retry with an up-to-date version of www/chromium? The codebase of chromium changes quite fast so not using the latest version in ports might render obsolete (and upstream unsupported) results. Ren=E9 --=20 http://www.rene-ladan.nl/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 09:23:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 8BA78106566B; Wed, 27 Jul 2011 09:23:38 +0000 (UTC) Date: Wed, 27 Jul 2011 09:23:38 +0000 From: Alexander Best To: =?iso-8859-15?Q?Ren=E9?= Ladan Message-ID: <20110727092338.GA10526@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: Norberto Lopes , Gleb Kurtsou , Matthias Andree , Adrian Chadd , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 09:23:38 -0000 On Wed Jul 27 11, Ren Ladan wrote: > 2011/7/27 Gleb Kurtsou : > > On (27/07/2011 00:48), Alexander Best wrote: > >> On Mon Jul 25 11, Matthias Andree wrote: > >> > Am 25.07.2011 09:21, schrieb Alexander Best: > >> > > On Mon Jul 25 11, Adrian Chadd wrote: > >> > >> Is it perhaps doing disk IO using mmap? > >> > > > >> > > how can i check, whether that's the case or not? > >> > > >> > Use truss(1) for instance. > >> > > >> > However, unless there are *practical* problems, a high number of page > >> > faults is not an indication for problems. Although it may sound scary, > >> > page faults are a feature of the memory management. > >> > >> unfortunately truss(1) is crashing chromium :( i opened up a new thread > >> reagarding this issue on freebsd-current@. > > Could you try ktrace? It works for me > > > >> another thing i noticed is the increase in system calls caused by chromium. > >> let's have a look at hub.freebsd.org: > >> > >> uptime = 149 days > >> > >> and 'vmstat -s' reports: > >> > >> 2168697753 cpu context switches > >> 2266220366 device interrupts > >> 2902880931 software interrupts > >> 3779075897 traps > >> 902107847 system calls > >> > >> now on my box: > >> > >> uptime = 2 days > >> > >> and 'vmstat -s' reports: > >> > >> 1155995386 cpu context switches > >> 164577882 device interrupts > >> 189456976 software interrupts > >> 137007580 traps > >> 2178434582 system calls > > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > > without chrome. > > > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > > 24343 > > > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > > > > Some work was done by kib@ to create a kernel page strong current time > > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > > were commited but I'm not sure if it was finished. > > But anyway calling gettimeofday hundreds of times per second is a chrome > > bug. > > > > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 > > chromium-11.0.696.57_1 > ^^^^^^^^^^^^^ > Can you retry with an up-to-date version of www/chromium? The > codebase of chromium > changes quite fast so not using the latest version in ports might > render obsolete (and > upstream unsupported) results. my tests were done with chromium-12.0.742.124 btw. > > Ren > -- > http://www.rene-ladan.nl/ From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 09:32:22 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 417DA106564A; Wed, 27 Jul 2011 09:32:22 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id C791E8FC15; Wed, 27 Jul 2011 09:32:21 +0000 (UTC) Received: by gwb15 with SMTP id 15so1129287gwb.13 for ; Wed, 27 Jul 2011 02:32:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6PCzi4wBEErGdqpK/bBva5ESWUzreivjbzkSE0zg6hE=; b=rF3H9SsytSdsTDvQCImrjHvrJrGr+DQ4zPBT+Bh74DuoP/nDwxzcTSe/n9QpcmsMFD nCTwwJ8pxGXkb0VePE2hnhkC9+7FClKhvnnqx9232fC+ynUdkUJEFQ/vU2FCZAAC8Y83 R3FyeNEXaGmSzncAH1cEprmu4jPQWEW4jhr+o= MIME-Version: 1.0 Received: by 10.142.75.9 with SMTP id x9mr4756761wfa.129.1311759140427; Wed, 27 Jul 2011 02:32:20 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.142.199.16 with HTTP; Wed, 27 Jul 2011 02:32:20 -0700 (PDT) In-Reply-To: <20110727092338.GA10526@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> <20110727092338.GA10526@freebsd.org> Date: Wed, 27 Jul 2011 11:32:20 +0200 X-Google-Sender-Auth: PiT6g8AJN8EF4am3rDb6wmTd4oc Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Norberto Lopes , Gleb Kurtsou , Matthias Andree , Adrian Chadd , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 09:32:22 -0000 2011/7/27 Alexander Best : > On Wed Jul 27 11, Ren=E9 Ladan wrote: >> 2011/7/27 Gleb Kurtsou : >> > On (27/07/2011 00:48), Alexander Best wrote: >> >> On Mon Jul 25 11, Matthias Andree wrote: >> >> > Am 25.07.2011 09:21, schrieb Alexander Best: >> >> > > On Mon Jul 25 11, Adrian Chadd wrote: >> >> > >> Is it perhaps doing disk IO using mmap? >> >> > > >> >> > > how can i check, whether that's the case or not? >> >> > >> >> > Use truss(1) for instance. >> >> > >> >> > However, unless there are *practical* problems, a high number of pa= ge >> >> > faults is not an indication for problems. =A0Although it may sound = scary, >> >> > page faults are a feature of the memory management. >> >> >> >> unfortunately truss(1) is crashing chromium :( i opened up a new thre= ad >> >> reagarding this issue on freebsd-current@. >> > Could you try ktrace? It works for me >> > >> >> another thing i noticed is the increase in system calls caused by chr= omium. >> >> let's have a look at hub.freebsd.org: >> >> >> >> uptime =3D 149 days >> >> >> >> and 'vmstat -s' reports: >> >> >> >> 2168697753 cpu context switches >> >> 2266220366 device interrupts >> >> 2902880931 software interrupts >> >> 3779075897 traps >> >> 902107847 system calls >> >> >> >> now on my box: >> >> >> >> uptime =3D 2 days >> >> >> >> and 'vmstat -s' reports: >> >> >> >> 1155995386 cpu context switches >> >> 164577882 device interrupts >> >> 189456976 software interrupts >> >> 137007580 traps >> >> 2178434582 system calls >> > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k >> > without chrome. >> > >> > Looks like there is a lot of clock_gettime and gettimeofday syscalls. >> > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l >> > =A0 24343 >> > >> > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 >> > =A012747 chrome =A0 15.077376 CALL =A0gettimeofday(0x7fffff7f9630,0x7f= ffff7f9640) >> > =A012747 chrome =A0 15.077396 CALL =A0clock_gettime(0x4,0x7fffffbfb6f0= ) >> > =A012747 chrome =A0 15.077497 CALL =A0gettimeofday(0x7fffffbfb650,0x7f= ffffbfb660) >> > =A012747 chrome =A0 15.077609 CALL =A0gettimeofday(0x7fffffbfb650,0x7f= ffffbfb660) >> > =A012747 chrome =A0 15.077723 CALL =A0gettimeofday(0x7fffffbfb650,0) >> > =A012747 chrome =A0 15.077845 CALL =A0clock_gettime(0,0x7fffffbfb2b0) >> > =A012747 chrome =A0 15.078337 CALL =A0clock_gettime(0x4,0x7fffff9fa630= ) >> > =A012747 chrome =A0 15.078544 CALL =A0clock_gettime(0x4,0x7fffff9fa650= ) >> > =A012747 chrome =A0 15.078587 CALL =A0clock_gettime(0x4,0x7fffff9fa650= ) >> > =A012747 chrome =A0 15.078632 CALL =A0clock_gettime(0x4,0x7fffff9fa650= ) >> > =A012747 chrome =A0 15.078674 CALL =A0clock_gettime(0x4,0x7fffff9fa650= ) >> > =A012747 chrome =A0 15.082803 CALL =A0gettimeofday(0x7ffffedd3630,0x7f= fffedd3640) >> > =A012747 chrome =A0 15.084644 CALL =A0gettimeofday(0x7fffffbfb650,0x7f= ffffbfb660) >> > =A012747 chrome =A0 15.084746 CALL =A0clock_gettime(0x4,0x7fffffbfb670= ) >> > =A012747 chrome =A0 15.084815 CALL =A0clock_gettime(0x4,0x7fffffbfb670= ) >> > =A012747 chrome =A0 15.086620 CALL =A0gettimeofday(0x7ffffefd4650,0x7f= fffefd4660) >> > =A012747 chrome =A0 15.086736 CALL =A0clock_gettime(0x4,0x7ffffefd4670= ) >> > =A012747 chrome =A0 15.086815 CALL =A0clock_gettime(0x4,0x7ffffefd4670= ) >> > =A012747 chrome =A0 15.098315 CALL =A0gettimeofday(0x7fffffffafe0,0x7f= ffffffaff0) >> > =A012747 chrome =A0 15.098680 CALL =A0clock_gettime(0x4,0x7fffffffb250= ) >> > >> > Some work was done by kib@ to create a kernel page strong current time >> > and other misc info to eliminate gettimeofday kind syscalls. =A0Bits o= f it >> > were commited but I'm not sure if it was finished. >> > But anyway calling gettimeofday hundreds of times per second is a chro= me >> > bug. >> > >> > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 >> > chromium-11.0.696.57_1 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0^^^^^^^^^^^^^ >> Can you retry with an up-to-date version of www/chromium? =A0The >> codebase of chromium >> changes quite fast so not using the latest version in ports might >> render obsolete (and >> upstream unsupported) results. > > my tests were done with chromium-12.0.742.124 btw. > Ok, I'll do some tests with the beta version from the chruetertee repository (13.0.782.99). >> >> Ren=E9 >> -- >> http://www.rene-ladan.nl/ > From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 09:38:57 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 089261065783; Wed, 27 Jul 2011 09:38:57 +0000 (UTC) Date: Wed, 27 Jul 2011 09:38:57 +0000 From: Alexander Best To: =?iso-8859-15?Q?Ren=E9?= Ladan Message-ID: <20110727093857.GA12549@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> <20110727092338.GA10526@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: Norberto Lopes , Gleb Kurtsou , Matthias Andree , Adrian Chadd , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 09:38:57 -0000 On Wed Jul 27 11, Ren Ladan wrote: > 2011/7/27 Alexander Best : > > On Wed Jul 27 11, Ren Ladan wrote: > >> 2011/7/27 Gleb Kurtsou : > >> > On (27/07/2011 00:48), Alexander Best wrote: > >> >> On Mon Jul 25 11, Matthias Andree wrote: > >> >> > Am 25.07.2011 09:21, schrieb Alexander Best: > >> >> > > On Mon Jul 25 11, Adrian Chadd wrote: > >> >> > >> Is it perhaps doing disk IO using mmap? > >> >> > > > >> >> > > how can i check, whether that's the case or not? > >> >> > > >> >> > Use truss(1) for instance. > >> >> > > >> >> > However, unless there are *practical* problems, a high number of page > >> >> > faults is not an indication for problems. Although it may sound scary, > >> >> > page faults are a feature of the memory management. > >> >> > >> >> unfortunately truss(1) is crashing chromium :( i opened up a new thread > >> >> reagarding this issue on freebsd-current@. > >> > Could you try ktrace? It works for me > >> > > >> >> another thing i noticed is the increase in system calls caused by chromium. > >> >> let's have a look at hub.freebsd.org: > >> >> > >> >> uptime = 149 days > >> >> > >> >> and 'vmstat -s' reports: > >> >> > >> >> 2168697753 cpu context switches > >> >> 2266220366 device interrupts > >> >> 2902880931 software interrupts > >> >> 3779075897 traps > >> >> 902107847 system calls > >> >> > >> >> now on my box: > >> >> > >> >> uptime = 2 days > >> >> > >> >> and 'vmstat -s' reports: > >> >> > >> >> 1155995386 cpu context switches > >> >> 164577882 device interrupts > >> >> 189456976 software interrupts > >> >> 137007580 traps > >> >> 2178434582 system calls > >> > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > >> > without chrome. > >> > > >> > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > >> > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > >> > 24343 > >> > > >> > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > >> > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > >> > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > >> > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > >> > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > >> > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > >> > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > >> > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > >> > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > >> > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > >> > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > >> > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > >> > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > >> > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > >> > > >> > Some work was done by kib@ to create a kernel page strong current time > >> > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > >> > were commited but I'm not sure if it was finished. > >> > But anyway calling gettimeofday hundreds of times per second is a chrome > >> > bug. ...also the number of context switches is very high. the following 'vmstat -s' output was taken after only 32 minutes of uptime and chromium running for ~ 10 minutes: 39775038 cpu context switches 1716910 device interrupts 1707161 software interrupts 1764371 traps 57319358 system calls 15 kernel threads created 2120 fork() calls 11 vfork() calls 25 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 71184 vnode pager pageins 102181 vnode pager pages paged in 13321 vnode pager pageouts 67437 vnode pager pages paged out 0 page daemon wakeups 0 pages examined by the page daemon 4662 pages reactivated 93964 copy-on-write faults 274 copy-on-write optimized faults 358563 zero fill pages zeroed 319 zero fill pages prezeroed 302 intransit blocking page faults 740518 total VM faults taken 0 pages affected by kernel thread creation 1130760 pages affected by fork() 17316 pages affected by vfork() 22319 pages affected by rfork() 7162 pages cached 693935 pages freed 0 pages freed by daemon 396060 pages freed by exiting processes 34690 pages active 88551 pages inactive 164 pages in VM cache 76703 pages wired down 301738 pages free 4096 bytes per page 426219 total name lookups cache hits (87% pos + 2% neg) system 0% per-directory deletions 2%, falsehits 0%, toolong 0% with chromium running: otaku% vmstat -s|grep "context switches"; sleep 1; vmstat -s|grep "context switches" 39604188 cpu context switches 39610679 cpu context switches without: otaku% vmstat -s|grep "context switches"; sleep 1; vmstat -s|grep "context switches" 39722188 cpu context switches 39722998 cpu context switches cheers. alex > >> > > >> > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 > >> > chromium-11.0.696.57_1 > >> ^^^^^^^^^^^^^ > >> Can you retry with an up-to-date version of www/chromium? The > >> codebase of chromium > >> changes quite fast so not using the latest version in ports might > >> render obsolete (and > >> upstream unsupported) results. > > > > my tests were done with chromium-12.0.742.124 btw. > > > Ok, I'll do some tests with the beta version from the chruetertee > repository (13.0.782.99). > >> > >> Ren > >> -- > >> http://www.rene-ladan.nl/ > > From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 10:44:21 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 640AE106566C for ; Wed, 27 Jul 2011 10:44:21 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (wrz3028.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 1D3BC8FC13 for ; Wed, 27 Jul 2011 10:44:20 +0000 (UTC) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id 590BB5ACA1 for ; Wed, 27 Jul 2011 12:19:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id 573355AC9D for ; Wed, 27 Jul 2011 12:19:20 +0200 (CEST) X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id 3A3935D19A for ; Wed, 27 Jul 2011 12:19:20 +0200 (CEST) Received: from lexx.ifp.tuwien.ac.at ([128.131.127.223]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.5.2FP2HF144) with ESMTP id 2011072712191990-48252 ; Wed, 27 Jul 2011 12:19:19 +0200 Date: Wed, 27 Jul 2011 12:19:18 +0200 From: Alexey Shuvaev To: freebsd-current@freebsd.org Message-ID: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> MIME-Version: 1.0 Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.21 (2010-09-15) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.5.2FP2HF144 | May 11, 2011) at 07/27/2011 12:19:20 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.5.2FP2HF144 | May 11, 2011) at 07/27/2011 12:19:20 PM, Serialize complete at 07/27/2011 12:19:20 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [clang] OpenOffice does not work with clang-compiled libgcc_s.so.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 10:44:21 -0000 Hello list! I have decided that clang in mature enough to give it a try on a main desktop. Everything is working fine except OpenOffice. The problem was already reported [1] and even analyzed [2]. Although the OP has reported [3] that since r218915 he has no problems anymore, I still have :( Note, that according to [4] it seems it was not specifically fixed upstream. So, if I compile the whole world (and kernel) with clang, soffice.bin dumps core. If I recompile the world with gcc and replace /lib/libgcc_s.so.1 with the new one, OpenOffice works fine again. Here are some information about the system that may be useful: ~> uname -a FreeBSD lexx.ifp.tuwien.ac.at 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224414: Tue Jul 26 16:00:43 CEST 2011 root@lexx.ifp.tuwien.ac.at:/usr/obj/usr/src/sys/GENERIC amd64 ~> gcc --version gcc (GCC) 4.2.2 20070831 prerelease [FreeBSD] Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ~> clang --version FreeBSD clang version 3.0 (trunk 135360) 20110717 Target: x86_64-unknown-freebsd9.0 Thread model: posix ~> cat /etc/make.conf SUP_UPDATE= YES PORTSSUPFILE= /root/ports-supfile DOCSUPFILE= /root/doc-supfile DOC_LANG= en_US.ISO8859-1 .if ${.CURDIR:M*/usr/ports*} .include "/etc/ports.conf" .endif # Building base with clang .if ${.CURDIR:M*/usr/src*} .if !defined(CC) || ${CC} == "cc" CC= clang .endif .if !defined(CXX) || ${CXX} == "c++" CXX= clang++ .endif .if !defined(CPP) || ${CPP} == "cpp" CPP= clang -E .endif # Don't die on warnings NO_WERROR= WERROR= .endif # added by use.perl 2011-07-18 17:50:51 PERL_VERSION=5.14.1 I don't have much time recently, so any further debugging will be on a "best effort" basis. Anyway I thought it is better to post it here, so it won't be just lost. If necessary I can file a PR about it. Thanks, Alexey. [1] http://lists.freebsd.org/pipermail/freebsd-current/2010-October/020668.html [2] http://lists.freebsd.org/pipermail/freebsd-current/2010-November/020838.html [3] http://lists.freebsd.org/pipermail/freebsd-current/2011-February/023003.html [4] http://llvm.org/bugs/show_bug.cgi?id=8541 From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 10:44:41 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EF571065787; Wed, 27 Jul 2011 10:44:41 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by mx1.freebsd.org (Postfix) with ESMTP id 787618FC1E; Wed, 27 Jul 2011 10:44:40 +0000 (UTC) Received: by fxe6 with SMTP id 6so189131fxe.17 for ; Wed, 27 Jul 2011 03:44:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ozzg8Xl8qER/b/ujzpp7eJ2uNpcLz0z+rI8qlQm5jGM=; b=i9XSwJWvikdQNmhqeYuCP4YgpJT4Fd7FFspe13Mc1ZpEfaWrdrj4WEEQ3ErGMWqVVG asCWaS2vtP1A8Y2BlOtEcXB9CWunA81YqBgh+ELUq9Fq36GkrGh6fOdpkhfom0hROZKB qoiTXZ4MrNsOkEk2XXMw/UA5Ih2XK8NILjgPo= Received: by 10.223.21.141 with SMTP id j13mr1016912fab.79.1311763479250; Wed, 27 Jul 2011 03:44:39 -0700 (PDT) Received: from localhost (lan-78-157-92-5.vln.skynet.lt [78.157.92.5]) by mx.google.com with ESMTPS id l22sm269594fam.33.2011.07.27.03.44.37 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 03:44:38 -0700 (PDT) Date: Wed, 27 Jul 2011 13:43:17 +0300 From: Gleb Kurtsou To: Alexander Best Message-ID: <20110727104316.GA6040@tops> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> <20110727091808.GA9024@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20110727091808.GA9024@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Norberto Lopes , Adrian Chadd , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 10:44:41 -0000 On (27/07/2011 09:18), Alexander Best wrote: > On Wed Jul 27 11, Gleb Kurtsou wrote: > > On (27/07/2011 00:48), Alexander Best wrote: > > > On Mon Jul 25 11, Matthias Andree wrote: > > > > Am 25.07.2011 09:21, schrieb Alexander Best: > > > > > On Mon Jul 25 11, Adrian Chadd wrote: > > > > >> Is it perhaps doing disk IO using mmap? > > > > > > > > > > how can i check, whether that's the case or not? > > > > > > > > Use truss(1) for instance. > > > > > > > > However, unless there are *practical* problems, a high number of page > > > > faults is not an indication for problems. Although it may sound scary, > > > > page faults are a feature of the memory management. > > > > > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > > > reagarding this issue on freebsd-current@. > > Could you try ktrace? It works for me > > > > > another thing i noticed is the increase in system calls caused by chromium. > > > let's have a look at hub.freebsd.org: > > > > > > uptime = 149 days > > > > > > and 'vmstat -s' reports: > > > > > > 2168697753 cpu context switches > > > 2266220366 device interrupts > > > 2902880931 software interrupts > > > 3779075897 traps > > > 902107847 system calls > > > > > > now on my box: > > > > > > uptime = 2 days > > > > > > and 'vmstat -s' reports: > > > > > > 1155995386 cpu context switches > > > 164577882 device interrupts > > > 189456976 software interrupts > > > 137007580 traps > > > 2178434582 system calls > > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > > without chrome. > > > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > > 24343 > > > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > > > > Some work was done by kib@ to create a kernel page strong current time > > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > > were commited but I'm not sure if it was finished. > > But anyway calling gettimeofday hundreds of times per second is a chrome > > bug. > > *lol* i did exactly the same measurements, you did. :) here are my results: > > otaku% kdump|grep "CALL mmap"|wc > 724 2896 58468 > otaku% kdump -s|grep "CALL clock_gettime"|wc > 49545 198180 2772674 > otaku% kdump -s|grep "CALL linux_clock_gettime"|wc > 40185 160740 2491298 > otaku% kdump -s|grep "CALL linux_gettimeofday"|wc > 21670 86680 1278530 > otaku% kdump -s|grep "CALL gettimeofday"|wc > 8173 32692 525053 > otaku% kdump -s|grep "CALL linux_sys_futex"|wc > 6191 24764 548800 I suppose linux_* stuff comes from flashplugin. Clearly flash generates more gettime syscalls than chrome itself. Unfortunately the only way to fix this mess in a linux centric world is to implement syscall free gettimeofday with linux ABI support. syscall-free gettimeofday discussion: http://freebsd.1045724.n5.nabble.com/fast-syscall-free-gettimeofday-td4488301.html From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 11:08:36 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 889131065670; Wed, 27 Jul 2011 11:08:36 +0000 (UTC) Date: Wed, 27 Jul 2011 11:08:36 +0000 From: Alexander Best To: Gleb Kurtsou Message-ID: <20110727110836.GA22511@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> <20110727091808.GA9024@freebsd.org> <20110727104316.GA6040@tops> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110727104316.GA6040@tops> Cc: Norberto Lopes , Adrian Chadd , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 11:08:36 -0000 On Wed Jul 27 11, Gleb Kurtsou wrote: > On (27/07/2011 09:18), Alexander Best wrote: > > On Wed Jul 27 11, Gleb Kurtsou wrote: > > > On (27/07/2011 00:48), Alexander Best wrote: > > > > On Mon Jul 25 11, Matthias Andree wrote: > > > > > Am 25.07.2011 09:21, schrieb Alexander Best: > > > > > > On Mon Jul 25 11, Adrian Chadd wrote: > > > > > >> Is it perhaps doing disk IO using mmap? > > > > > > > > > > > > how can i check, whether that's the case or not? > > > > > > > > > > Use truss(1) for instance. > > > > > > > > > > However, unless there are *practical* problems, a high number of page > > > > > faults is not an indication for problems. Although it may sound scary, > > > > > page faults are a feature of the memory management. > > > > > > > > unfortunately truss(1) is crashing chromium :( i opened up a new thread > > > > reagarding this issue on freebsd-current@. > > > Could you try ktrace? It works for me > > > > > > > another thing i noticed is the increase in system calls caused by chromium. > > > > let's have a look at hub.freebsd.org: > > > > > > > > uptime = 149 days > > > > > > > > and 'vmstat -s' reports: > > > > > > > > 2168697753 cpu context switches > > > > 2266220366 device interrupts > > > > 2902880931 software interrupts > > > > 3779075897 traps > > > > 902107847 system calls > > > > > > > > now on my box: > > > > > > > > uptime = 2 days > > > > > > > > and 'vmstat -s' reports: > > > > > > > > 1155995386 cpu context switches > > > > 164577882 device interrupts > > > > 189456976 software interrupts > > > > 137007580 traps > > > > 2178434582 system calls > > > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > > > without chrome. > > > > > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > > > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > > > 24343 > > > > > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > > > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > > > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > > > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > > > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > > > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > > > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > > > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > > > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > > > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > > > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > > > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > > > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > > > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > > > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > > > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > > > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > > > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > > > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > > > > > > Some work was done by kib@ to create a kernel page strong current time > > > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > > > were commited but I'm not sure if it was finished. > > > But anyway calling gettimeofday hundreds of times per second is a chrome > > > bug. > > > > *lol* i did exactly the same measurements, you did. :) here are my results: > > > > otaku% kdump|grep "CALL mmap"|wc > > 724 2896 58468 > > otaku% kdump -s|grep "CALL clock_gettime"|wc > > 49545 198180 2772674 > > otaku% kdump -s|grep "CALL linux_clock_gettime"|wc > > 40185 160740 2491298 > > otaku% kdump -s|grep "CALL linux_gettimeofday"|wc > > 21670 86680 1278530 > > otaku% kdump -s|grep "CALL gettimeofday"|wc > > 8173 32692 525053 > > otaku% kdump -s|grep "CALL linux_sys_futex"|wc > > 6191 24764 548800 > I suppose linux_* stuff comes from flashplugin. Clearly flash generates > more gettime syscalls than chrome itself. Unfortunately the only way to > fix this mess in a linux centric world is to implement syscall free > gettimeofday with linux ABI support. > > syscall-free gettimeofday discussion: > http://freebsd.1045724.n5.nabble.com/fast-syscall-free-gettimeofday-td4488301.html thanks. this linux article is also very interesting in this context: http://lwn.net/Articles/18411/ ...they sorta claim that implementing gettimeofday() in userland is extremely difficult. cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 12:57:42 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 4E54A1065672; Wed, 27 Jul 2011 12:57:42 +0000 (UTC) Date: Wed, 27 Jul 2011 12:57:42 +0000 From: Alexander Best To: freebsd-current@freebsd.org Message-ID: <20110727125742.GA38304@freebsd.org> References: <20110726233813.GA55491@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110726233813.GA55491@freebsd.org> Subject: Re: issues with vmstat and latest HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 12:57:42 -0000 On Tue Jul 26 11, Alexander Best wrote: > hi there, > > 'vmstat -m' and 'vmstat -z' report: > > otaku% vmstat -m > vmstat: memstat_sysctl_malloc: Too many CPUs > otaku% vmstat -z > vmstat: memstat_sysctl_uma: Too many CPUs > > world and kernel are in sync. i'm running r224294 on amd64. please disregard this thread. there's a discussion on svn-src-head@ which deals with this issue. cheers. alex > > cheers. > alex From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 15:32:04 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0018B106566C; Wed, 27 Jul 2011 15:32:03 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 69F438FC17; Wed, 27 Jul 2011 15:32:03 +0000 (UTC) Received: by wwe6 with SMTP id 6so1475523wwe.31 for ; Wed, 27 Jul 2011 08:32:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=YCTQDNHWOvws2GUYok5Ya8iW2F8V7ROjsyr4BTyDTBY=; b=cuYhixf27q9z7QMW4HQPvHrXXXbSzfmXK1ddY659xCMjd3BxNBtqSGiOsM53KfNatM M23CMHuP0DcN2JnEEo33GB/OIuQnNdNvSFhTnHDfQ39iQchFBC9BnLUwKK1z7OqQHOpA xLDAP/kMEw4bMkJxAHAZITG2c9HTXHG3sEcQA= MIME-Version: 1.0 Received: by 10.216.237.233 with SMTP id y83mr42394weq.9.1311779301185; Wed, 27 Jul 2011 08:08:21 -0700 (PDT) Received: by 10.216.87.83 with HTTP; Wed, 27 Jul 2011 08:08:21 -0700 (PDT) Received: by 10.216.87.83 with HTTP; Wed, 27 Jul 2011 08:08:21 -0700 (PDT) Date: Wed, 27 Jul 2011 10:08:21 -0500 Message-ID: From: Brandon Gooch To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: issues with vmstat and latest HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 15:32:04 -0000 On Jul 27, 2011 7:58 AM, "Alexander Best" wrote: > > On Tue Jul 26 11, Alexander Best wrote: > > hi there, > > > > 'vmstat -m' and 'vmstat -z' report: > > > > otaku% vmstat -m > > vmstat: memstat_sysctl_malloc: Too many CPUs > > otaku% vmstat -z > > vmstat: memstat_sysctl_uma: Too many CPUs > > > > world and kernel are in sync. i'm running r224294 on amd64. > > please disregard this thread. there's a discussion on svn-src-head@ which deals > with this issue. > > cheers. > alex > > > > > cheers. > > alex > Do you have a link to the discussion handy? -Brandon From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 15:43:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96AC51065673; Wed, 27 Jul 2011 15:43:37 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4823B8FC0A; Wed, 27 Jul 2011 15:43:37 +0000 (UTC) Received: by yxl31 with SMTP id 31so1061299yxl.13 for ; Wed, 27 Jul 2011 08:43:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Sk//9VyfjS6+tVn8W+XbWzcfZg8PXBDFxdc+ufoAMtI=; b=DHPpPFvKNTfD69KbyL89Qje97SMaHwx8wCOXlVtlxflmTuYYOpcEbKQ0xoVlbblo+b Fj8DFByUugbWc1pskKmnO1MFEtowil9KywC5rP6ayFpWrjDa2Sa6x/1kpcqdezbEzpux Ynh4I1KossfRH1xUas4KsKEO95tnNNuoQokSc= MIME-Version: 1.0 Received: by 10.150.103.1 with SMTP id a1mr177849ybc.244.1311781416535; Wed, 27 Jul 2011 08:43:36 -0700 (PDT) Received: by 10.150.200.3 with HTTP; Wed, 27 Jul 2011 08:43:36 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Jul 2011 19:43:36 +0400 Message-ID: From: Sergey Kandaurov To: Brandon Gooch Content-Type: text/plain; charset=ISO-8859-1 Cc: Alexander Best , freebsd-current@freebsd.org Subject: Re: issues with vmstat and latest HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 15:43:37 -0000 On 27 July 2011 19:08, Brandon Gooch wrote: > On Jul 27, 2011 7:58 AM, "Alexander Best" wrote: >> >> On Tue Jul 26 11, Alexander Best wrote: >> > hi there, >> > >> > 'vmstat -m' and 'vmstat -z' report: >> > >> > otaku% vmstat -m >> > vmstat: memstat_sysctl_malloc: Too many CPUs >> > otaku% vmstat -z >> > vmstat: memstat_sysctl_uma: Too many CPUs >> > >> > world and kernel are in sync. i'm running r224294 on amd64. >> >> please disregard this thread. there's a discussion on svn-src-head@ which > deals >> with this issue. >> >> cheers. >> alex >> >> > >> > cheers. >> > alex >> > > Do you have a link to the discussion handy? > A fix for vmstat will be committed after BETA1 announce. Please be patient. -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 15:44:49 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 2E0321065670; Wed, 27 Jul 2011 15:44:49 +0000 (UTC) Date: Wed, 27 Jul 2011 15:44:49 +0000 From: Alexander Best To: Brandon Gooch Message-ID: <20110727154449.GA60310@freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-current@freebsd.org Subject: Re: issues with vmstat and latest HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 15:44:49 -0000 On Wed Jul 27 11, Brandon Gooch wrote: > On Jul 27, 2011 7:58 AM, "Alexander Best" wrote: > > > > On Tue Jul 26 11, Alexander Best wrote: > > > hi there, > > > > > > 'vmstat -m' and 'vmstat -z' report: > > > > > > otaku% vmstat -m > > > vmstat: memstat_sysctl_malloc: Too many CPUs > > > otaku% vmstat -z > > > vmstat: memstat_sysctl_uma: Too many CPUs > > > > > > world and kernel are in sync. i'm running r224294 on amd64. > > > > please disregard this thread. there's a discussion on svn-src-head@ which > deals > > with this issue. > > > > cheers. > > alex > > > > > > > > cheers. > > > alex > > > > Do you have a link to the discussion handy? http://www.mail-archive.com/svn-src-head@freebsd.org/msg14793.html > > -Brandon From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 16:46:25 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77E42106566C for ; Wed, 27 Jul 2011 16:46:25 +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 23B5A8FC15 for ; Wed, 27 Jul 2011 16:46:24 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email2.allantgroup.com (8.14.4/8.14.4) with ESMTP id p6RGZoJU024102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Jul 2011 11:35:50 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.5/8.14.5) with ESMTP id p6RGZo9m035530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Jul 2011 11:35:50 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.5/8.14.5/Submit) id p6RGZnON035529; Wed, 27 Jul 2011 11:35:49 -0500 (CDT) (envelope-from dan) Date: Wed, 27 Jul 2011 11:35:49 -0500 From: Dan Nelson To: Alexander Best Message-ID: <20110727163549.GD6562@dan.emsphone.com> References: <20110727003004.GA61713@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110727003004.GA61713@freebsd.org> X-OS: FreeBSD 8.2-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by dan.emsphone.com id p6RGZo9m035530 X-Virus-Scanned: clamav-milter 0.97.2 at email2.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6 (email2.allantgroup.com [199.67.51.78]); Wed, 27 Jul 2011 11:35:50 -0500 (CDT) X-Scanned-By: MIMEDefang 2.68 on 199.67.51.78 Cc: freebsd-current@freebsd.org Subject: Re: truss crashing process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 16:46:25 -0000 In the last episode (Jul 27), Alexander Best said: > hi there, > > i was trying to attach truss to chromium via > > 'truss -p 18445' and got: > > [...] > kevent(26,{},0,{0x1b,EVFILT_READ,0x0,0,0x1,0x44cb600 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x! 0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,! 0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,! 0x0,0x0, > -- UNKNOWN SYSCALL -14720592 -- > write(-14720976,0x8080808080808000,0) = 41 (0x29) > select(94,0x6acd,{0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 40 41 42 43 44 45 46 70 71 72 73 76 77 78 79 80 81 82 84 87 88 91},0x1,{0.85048848 }) = 73 (0x49) > -- UNKNOWN SYSCALL 303120384 -- > #94(0x0,0x0,0x5e,0xb6cd600,0x83ed780,0x3dae410) = 189 (0xbd) > truss: Cannot malloc -14740096 bytes for fd_set array: Cannot allocate memory Invalid syscalls numbers like that usually mean that truss has attached to a process in the middle of a syscall. The ptrace API fires the same event for syscall enter and exit, so if truss is expecting an enter and gets an exit, you get a mangled syscall number and eventually truss will coredump trying to decode incorrect data. Try applying the patch at https://www.evoy.net/FreeBSD/truss.diff , which amongst other things, fixes this problem. If you just want the syscall fix, search the diff for "50-50 chance" and manually patch that if(){} block in your source. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 18:12:33 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3666106566B for ; Wed, 27 Jul 2011 18:12:33 +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 878E58FC17 for ; Wed, 27 Jul 2011 18:12:33 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:24ff:498:f97a:a670] (unknown [IPv6:2001:7b8:3a7:0:24ff:498:f97a:a670]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 71C605C37; Wed, 27 Jul 2011 20:12:32 +0200 (CEST) Message-ID: <4E305510.1010900@FreeBSD.org> Date: Wed, 27 Jul 2011 20:12:32 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Alexey Shuvaev References: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> In-Reply-To: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [clang] OpenOffice does not work with clang-compiled libgcc_s.so.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 18:12:33 -0000 On 2011-07-27 12:19, Alexey Shuvaev wrote: ... > So, if I compile the whole world (and kernel) with clang, soffice.bin > dumps core. If I recompile the world with gcc and replace /lib/libgcc_s.so.1 > with the new one, OpenOffice works fine again. Hmm, OpenOffice is a rather unwieldy testcase, not in the least because it takes ages and many gigabytes to build. :( Did you or anyone else ever find a smaller testcase? From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 18:18:38 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72B3C106564A; Wed, 27 Jul 2011 18:18:38 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0E9588FC13; Wed, 27 Jul 2011 18:18:37 +0000 (UTC) Received: by gxk28 with SMTP id 28so1604742gxk.13 for ; Wed, 27 Jul 2011 11:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=FV7PVEzwcbU8MckAIBwAreAA1+VdFgGFxLufFGfWyms=; b=evJKo37hlRxKJzJN0T+J775+W7/4U93CpgOb+NbUyagM74L5Oy4ujIT5T8Oydb+nWI KUxtFxstVQhJ9L3xbOlWYocZEXPNx2HxzyyajnIPcYbPQ144Q0Sbnh6LvuUYoPAJBij6 IrMHeKXHrN0wkd2XtdBabQCMhic1v5r0pThHw= Received: by 10.43.64.66 with SMTP id xh2mr83515icb.391.1311790717152; Wed, 27 Jul 2011 11:18:37 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.67.211 with HTTP; Wed, 27 Jul 2011 11:18:07 -0700 (PDT) In-Reply-To: <4E305510.1010900@FreeBSD.org> References: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> <4E305510.1010900@FreeBSD.org> From: Chris Rees Date: Wed, 27 Jul 2011 19:18:07 +0100 X-Google-Sender-Auth: A0JYDSMBkbchuHzLR4sWg6K0QME Message-ID: To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Alexey Shuvaev , freebsd-current@freebsd.org, office@freebsd.org Subject: Re: [clang] OpenOffice does not work with clang-compiled libgcc_s.so.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 18:18:38 -0000 On 27 July 2011 19:12, Dimitry Andric wrote: > On 2011-07-27 12:19, Alexey Shuvaev wrote: > ... >> >> So, if I compile the whole world (and kernel) with clang, soffice.bin >> dumps core. If I recompile the world with gcc and replace >> /lib/libgcc_s.so.1 >> with the new one, OpenOffice works fine again. > > Hmm, OpenOffice is a rather unwieldy testcase, not in the least because > it takes ages and many gigabytes to build. :( =A0Did you or anyone else > ever find a smaller testcase? CCing office@, maintainers -- could be interested and may give answers. FWIW, LibreOffice is probably a better target for clang -- seems to be The Future. Chris From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 18:21:47 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 514DE1065677; Wed, 27 Jul 2011 18:21:47 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 001798FC1F; Wed, 27 Jul 2011 18:21:46 +0000 (UTC) Received: by iyb11 with SMTP id 11so2698209iyb.13 for ; Wed, 27 Jul 2011 11:21:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=AGL5unY3sayzJYOxC4CNoM57glPHPDbPI22D13/sjHw=; b=uR7sNcLN0A3tgbwVYKFMb2LRGhg0TfbgdP1QJcimlS9oLGQBE1wOmnHpDfaVGzF8FV iisn2DEQUWnVLFuMLswPW3oj8Lb+Hw9ejj6XwVWoy1tyRJUJ7+90Tzld19hL+MtZQaDw IcQI6N+ETv84W4T+rkxp3dn9dnPDslYRdBJzE= Received: by 10.231.183.11 with SMTP id ce11mr91638ibb.60.1311790906087; Wed, 27 Jul 2011 11:21:46 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.67.211 with HTTP; Wed, 27 Jul 2011 11:21:16 -0700 (PDT) In-Reply-To: References: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> <4E305510.1010900@FreeBSD.org> From: Chris Rees Date: Wed, 27 Jul 2011 19:21:16 +0100 X-Google-Sender-Auth: yW89_lpaSCKOr2une-Bq3ondVWo Message-ID: To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Alexey Shuvaev , freebsd-current@freebsd.org, office@freebsd.org Subject: Re: [clang] OpenOffice does not work with clang-compiled libgcc_s.so.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 18:21:47 -0000 On 27 July 2011 19:18, Chris Rees wrote: > On 27 July 2011 19:12, Dimitry Andric wrote: >> On 2011-07-27 12:19, Alexey Shuvaev wrote: >> ... >>> >>> So, if I compile the whole world (and kernel) with clang, soffice.bin >>> dumps core. If I recompile the world with gcc and replace >>> /lib/libgcc_s.so.1 >>> with the new one, OpenOffice works fine again. >> >> Hmm, OpenOffice is a rather unwieldy testcase, not in the least because >> it takes ages and many gigabytes to build. :( =A0Did you or anyone else >> ever find a smaller testcase? > > CCing office@, maintainers -- could be interested and may give answers. > > FWIW, LibreOffice is probably a better target for clang -- seems to be > The Future. By the way, I didn't mean that OOo is 'deprecated' at all; maho is still working on it. Chris From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 19:21:52 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B14981065708 for ; Wed, 27 Jul 2011 19:21:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 362B38FC0C for ; Wed, 27 Jul 2011 19:21:51 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p6RJLgIo013058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jul 2011 22:21:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p6RJLgT7038832; Wed, 27 Jul 2011 22:21:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p6RJLfT9038831; Wed, 27 Jul 2011 22:21:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 27 Jul 2011 22:21:41 +0300 From: Kostik Belousov To: Dan Nelson Message-ID: <20110727192141.GB17489@deviant.kiev.zoral.com.ua> References: <20110727003004.GA61713@freebsd.org> <20110727163549.GD6562@dan.emsphone.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IMEGvgzHT1iQOmnS" Content-Disposition: inline In-Reply-To: <20110727163549.GD6562@dan.emsphone.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Alexander Best , freebsd-current@freebsd.org Subject: Re: truss crashing process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 19:21:52 -0000 --IMEGvgzHT1iQOmnS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 27, 2011 at 11:35:49AM -0500, Dan Nelson wrote: > In the last episode (Jul 27), Alexander Best said: > > hi there, > >=20 > > i was trying to attach truss to chromium via > >=20 > > 'truss -p 18445' and got: > >=20 > > [...] > > kevent(26,{},0,{0x1b,EVFILT_READ,0x0,0,0x1,0x44cb600 0x0,0x0,0x0,0,0x0,= 0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0= x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,= 0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0= x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x= 0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0= x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x= 0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0= x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x= 0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0= ,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x= 0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0= ,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x= 0,0x0 0x0,0x0,0x! > 0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x= 0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0= ,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,= 0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0= 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,= 0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0= ,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,= 0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0= ,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 = 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0= x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,= 0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0= x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,= 0x0,0x0 0x0,0x0,! > 0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,0x0,0x0,0,0x0,0x0 0x0,! > 0x0,0x0, > > -- UNKNOWN SYSCALL -14720592 -- > > write(-14720976,0x8080808080808000,0) =3D 41 (0x29) > > select(94,0x6acd,{0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 = 21 22 23 24 25 26 27 28 29 30 31 40 41 42 43 44 45 46 70 71 72 73 76 77 78 = 79 80 81 82 84 87 88 91},0x1,{0.85048848 }) =3D 73 (0x49) > > -- UNKNOWN SYSCALL 303120384 -- > > #94(0x0,0x0,0x5e,0xb6cd600,0x83ed780,0x3dae410) =3D 189 (0xbd) > > truss: Cannot malloc -14740096 bytes for fd_set array: Cannot allocate = memory >=20 > Invalid syscalls numbers like that usually mean that truss has attached t= o a > process in the middle of a syscall. The ptrace API fires the same event = for > syscall enter and exit, so if truss is expecting an enter and gets an exi= t, > you get a mangled syscall number and eventually truss will coredump trying > to decode incorrect data. >=20 > Try applying the patch at https://www.evoy.net/FreeBSD/truss.diff , which > amongst other things, fixes this problem. If you just want the syscall f= ix, > search the diff for "50-50 chance" and manually patch that if(){} block in > your source. We have PL_FLAG_SCE/PL_FLAG_SCX for some time. I planned to update truss to use the flags, as well as to take advantage of PL_FLAG_FORKED to close the race where truss can miss the forked child. Unfortunately, the project stalled. --IMEGvgzHT1iQOmnS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk4wZUUACgkQC3+MBN1Mb4iuxwCfXGBbDEJbOEGSXLEzPNN+XKqS nI0AnRA36KMbUmgYXZb41t/cwZNaRc8B =rYU4 -----END PGP SIGNATURE----- --IMEGvgzHT1iQOmnS-- From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 19:57:45 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C40B0106566C for ; Wed, 27 Jul 2011 19:57:45 +0000 (UTC) (envelope-from etnapierala@googlemail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5AAAB8FC16 for ; Wed, 27 Jul 2011 19:57:44 +0000 (UTC) Received: by wwg11 with SMTP id 11so3403369wwg.1 for ; Wed, 27 Jul 2011 12:57:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=+JnCeGmO03W0D3myaPY3mwvyupXofCPDKFwu21S+pcc=; b=WnZiUfXQVOT4ydNXMdJ0cMv387uMTWg9YBUpOS0XojLiVnWx94l7Bgr3nGWhXWFdye dLf9+gzHKJes8DgF/IdUunLfVptAbW6Jn9rf9i+qGY36sRL0mnspvnIHoAvnw/dbC2qQ Ng7pIZL8fuZotsFJNTPiotJrCH12EzO1tRhAU= Received: by 10.216.74.74 with SMTP id w52mr126117wed.113.1311795173291; Wed, 27 Jul 2011 12:32:53 -0700 (PDT) Received: from [192.168.1.106] (45.81.datacomsa.pl [195.34.81.45]) by mx.google.com with ESMTPS id w45sm143149wec.24.2011.07.27.12.32.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 27 Jul 2011 12:32:52 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <4E2EC1D4.20302@rsu.ru> Date: Wed, 27 Jul 2011 21:32:49 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5690C0E7-5FD5-49B1-B1C1-6D56EB95B810@FreeBSD.org> References: <4E2EC1D4.20302@rsu.ru> To: Alexander Pyhalov X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-current@freebsd.org Subject: Re: rctl limit cpu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 19:57:45 -0000 Wiadomo=B6=E6 napisana przez Alexander Pyhalov w dniu 26 lip 2011, o = godz. 15:32: > Hello. > I see in rctl man page, that I can limit cpu time in milliseconds, = e.g., for jail. But I can't deny allocation of the resource (according = to man page). > In Solaris I can assign different amount of cpu shares to different = projects. How can I achieve this with rctl? For example, I'd like to = give jail:www 40% CPU, jail:db - 50% CPU and leave 10% to the base = system... The cputime resource (it got renamed shortly before the code freeze to = match resource names in login.conf(5)) defines amount of CPU time used, not = the percentage. That's why you cannot deny it - if you could, it would just make the = offending process (jail, login class, user) hang indefinitely. The %CPU limit is not implemented yet. I plan to do this before = sometime after 9.0 is out. -- If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 20:40:18 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BC26106564A for ; Wed, 27 Jul 2011 20:40:18 +0000 (UTC) (envelope-from rbgarga@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id D3B0B8FC0A for ; Wed, 27 Jul 2011 20:40:17 +0000 (UTC) Received: by wyg24 with SMTP id 24so1705342wyg.13 for ; Wed, 27 Jul 2011 13:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=1LpG8bzOZXC/gwhC1t99kIZOmz272j8IvQJ6ZZrhKjo=; b=ItgwFE5Sp9Gd9h5BCcCSXkvXnlcBrhl6an3E4TF8KmTJDMqv/BtsvKeWEyiO7DT8Oq ClXPowA3p2JheJgBPXe1mb/BV2cFju3se9q8MQVgRJH1CRfJzBXP4plLC2qCmNTCyeXk D3fvsZjuvGLnv080JstJ1lkMJzxghpcG91Yb4= Received: by 10.216.202.9 with SMTP id c9mr186750weo.14.1311795281974; Wed, 27 Jul 2011 12:34:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.168.147 with HTTP; Wed, 27 Jul 2011 12:20:21 -0700 (PDT) In-Reply-To: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> References: <20110727101918.GA86589@lexx.ifp.tuwien.ac.at> From: Renato Botelho Date: Wed, 27 Jul 2011 16:20:21 -0300 Message-ID: To: Alexey Shuvaev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: [clang] OpenOffice does not work with clang-compiled libgcc_s.so.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Jul 2011 20:40:18 -0000 On Wed, Jul 27, 2011 at 7:19 AM, Alexey Shuvaev wrote: > Hello list! > > I have decided that clang in mature enough to give it a try on a main > desktop. Everything is working fine except OpenOffice. The problem was > already reported [1] and even analyzed [2]. Although the OP has reported = [3] > that since r218915 he has no problems anymore, I still have :( > Note, that according to [4] it seems it was not specifically fixed upstre= am. > > So, if I compile the whole world (and kernel) with clang, soffice.bin > dumps core. If I recompile the world with gcc and replace /lib/libgcc_s.s= o.1 > with the new one, OpenOffice works fine again. Here are some information > about the system that may be useful: > > ~> uname -a > FreeBSD lexx.ifp.tuwien.ac.at 9.0-BETA1 FreeBSD 9.0-BETA1 #0 r224414: Tue= Jul 26 16:00:43 CEST 2011 =A0 =A0 root@lexx.ifp.tuwien.ac.at:/usr/obj/usr/= src/sys/GENERIC =A0amd64 > > ~> gcc --version > gcc (GCC) 4.2.2 20070831 prerelease [FreeBSD] > Copyright (C) 2007 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. =A0There is= NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOS= E. > > ~> clang --version > FreeBSD clang version 3.0 (trunk 135360) 20110717 > Target: x86_64-unknown-freebsd9.0 > Thread model: posix > > ~> cat /etc/make.conf > SUP_UPDATE=3D =A0 =A0 YES > PORTSSUPFILE=3D =A0 /root/ports-supfile > DOCSUPFILE=3D =A0 =A0 /root/doc-supfile > DOC_LANG=3D =A0 =A0 =A0 en_US.ISO8859-1 > > .if ${.CURDIR:M*/usr/ports*} > .include "/etc/ports.conf" > .endif > > # Building base with clang > .if ${.CURDIR:M*/usr/src*} > .if !defined(CC) || ${CC} =3D=3D "cc" > CC=3D =A0 =A0 =A0 =A0 =A0 =A0 clang > .endif > .if !defined(CXX) || ${CXX} =3D=3D "c++" > CXX=3D =A0 =A0 =A0 =A0 =A0 =A0clang++ > .endif > .if !defined(CPP) || ${CPP} =3D=3D "cpp" > CPP=3D =A0 =A0 =A0 =A0 =A0 =A0clang -E > .endif > # Don't die on warnings > NO_WERROR=3D > WERROR=3D > .endif > # added by use.perl 2011-07-18 17:50:51 > PERL_VERSION=3D5.14.1 > > I don't have much time recently, so any further debugging will be on a > "best effort" basis. Anyway I thought it is better to post it here, so > it won't be just lost. If necessary I can file a PR about it. Hello, I had a similar problem in the past, but IIRC after rebuild openoffice it started to work again. The machine where it happened is not available anymore. Regards --=20 Renato Botelho From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 21:01:12 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DFC51065672 for ; Wed, 27 Jul 2011 21:01:12 +0000 (UTC) (envelope-from samspeed@mail.ru) Received: from f98.mail.ru (f98.mail.ru [217.69.129.121]) by mx1.freebsd.org (Postfix) with ESMTP id E6A608FC17 for ; Wed, 27 Jul 2011 21:01:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Message-Id:Content-Transfer-Encoding:Content-Type:Reply-To:Date:Mime-Version:Subject:To:From; bh=ysTAGhxMXEhjcLZqCwWBMxC+3UQVe8pSdQ5rSa0npYU=; b=JkKmYf9PN0XysNP2InFH6q0tYiCmNfMv7UwZ1KbxDLs8VA3MZuGXsMf7yzIU7mCGqOMxFZSf5nUN4rRgV2n8+Qt3Bi1KhTYh7Zoy3pRXdmfg37pvAoFZNSsN7k9RQf0O; Received: from mail by f98.mail.ru with local id 1QmBE6-00044w-00 for freebsd-current@freebsd.org; Thu, 28 Jul 2011 01:01:10 +0400 Received: from [91.202.27.126] by e.mail.ru with HTTP; Thu, 28 Jul 2011 01:01:10 +0400 From: Andrey Smagin To: freebsd-current@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 172.17.2.191 via proxy [91.202.27.126] Date: Thu, 28 Jul 2011 01:01:10 +0400 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Message-Id: X-Spam: Not detected X-Mras: Ok Subject: r224468 amd64 kernel panic on boot: No init found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Smagin List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 21:01:12 -0000 UGxlYXNlIGhlbHAhIENhbid0IGxvYWQgc3lzdGVtIGFmdGVyIHVwZGF0ZSBvbiByMjI0NDY4Cm1v dW50IHBhcnRpdGlvbiBpcyBVRlMsIG5vIHN0YXJ0dXAgc2V0dGluZ3MgY2hhbmdlZCwgCm5vIENP TkYgZmlsZSBjaGFuZ2VkLgptYWtlIGJ1aWxkd29ybGQgYnVpbGRrZXJuZWwgaW5zdGFsbHdvcmxk IGluc3RhbGxrZXJuZWwKbm93IEkgbG9hZGVkIG9sZCByMjIxNzI1Lgo= From owner-freebsd-current@FreeBSD.ORG Wed Jul 27 21:45:06 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41E68106564A for ; Wed, 27 Jul 2011 21:45:06 +0000 (UTC) (envelope-from samspeed@mail.ru) Received: from f283.mail.ru (f283.mail.ru [217.69.128.250]) by mx1.freebsd.org (Postfix) with ESMTP id A91578FC13 for ; Wed, 27 Jul 2011 21:45:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Message-Id:Content-Transfer-Encoding:Content-Type:Reply-To:In-Reply-To:References:Date:Mime-Version:Subject:To:From; bh=IAi7v+pHFahBhrDGj2jpmU34VjFqxzf8gNKlGj92Y2k=; b=QvolPvw6Af1XicrVOTGgvjYkq00D7zA7TPPU2JSIBQQUywd8EzzqAF1tpjuPzKOT9qXjbeJpz0rZYUr6CvGck4Sly+XiSPuesqljMjGS00s7QFy1IFXDi42Uagm9dmh8; Received: from mail by f283.mail.ru with local id 1QmBuZ-0001Sa-00 for freebsd-current@freebsd.org; Thu, 28 Jul 2011 01:45:03 +0400 Received: from [2.95.11.9] by e.mail.ru with HTTP; Thu, 28 Jul 2011 01:45:03 +0400 From: Andrey Smagin To: freebsd-current@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 172.17.2.191 via proxy [2.95.11.9] Date: Thu, 28 Jul 2011 01:45:03 +0400 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Message-Id: X-Spam: Not detected X-Mras: Ok Subject: Re: r224468 amd64 kernel panic on boot: No init found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrey Smagin List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 21:45:06 -0000 U29ycnkgZm9yIHBhbmljLiBJIGhhdmUgYW5vdGhlciBIREQgd2l0aCBwYXJ0aXRpb24gczFhLCBh ZnRlciB1cGRhdGUsIEhERCByZW51bWVyYXRlZC4KdmZzLnJvb3QubW91bnRmcm9tIGluIGxvYWRl ci5jb25mIHNvbHZlZCBteSBwcm9ibGVtCgoyOCDQuNGO0LvRjyAyMDExLCAwMTowMiDQvtGCIEFu ZHJleSBTbWFnaW4gPHNhbXNwZWVkQG1haWwucnU+Ogo+IFBsZWFzZSBoZWxwISBDYW4ndCBsb2Fk IHN5c3RlbSBhZnRlciB1cGRhdGUgb24gcjIyNDQ2OAo+IG1vdW50IHBhcnRpdGlvbiBpcyBVRlMs IG5vIHN0YXJ0dXAgc2V0dGluZ3MgY2hhbmdlZCwgCj4gbm8gQ09ORiBmaWxlIGNoYW5nZWQuCj4g bWFrZSBidWlsZHdvcmxkIGJ1aWxka2VybmVsIGluc3RhbGx3b3JsZCBpbnN0YWxsa2VybmVsCj4g bm93IEkgbG9hZGVkIG9sZCByMjIxNzI1Lgo+IA== From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 02:12:25 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FC07106566B; Thu, 28 Jul 2011 02:12:25 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f11:66f:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id CFAE68FC0A; Thu, 28 Jul 2011 02:12:24 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f11:66f:1::5]) by mail.farley.org (8.14.5/8.14.5) with ESMTP id p6S2CM9T090126; Wed, 27 Jul 2011 22:12:22 -0400 (EDT) (envelope-from scf@FreeBSD.org) Date: Wed, 27 Jul 2011 22:12:22 -0400 (EDT) From: "Sean C. Farley" To: Gleb Kurtsou In-Reply-To: <20110727083339.GA12233@tops> Message-ID: References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> User-Agent: Alpine 2.02 (BSF 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.1 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.farley.org Cc: Norberto Lopes , Alexander Best , Adrian Chadd , Matthias Andree , freebsd-current@FreeBSD.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 02:12:25 -0000 On Wed, 27 Jul 2011, Gleb Kurtsou wrote: > On (27/07/2011 00:48), Alexander Best wrote: >> On Mon Jul 25 11, Matthias Andree wrote: >>> Am 25.07.2011 09:21, schrieb Alexander Best: >>>> On Mon Jul 25 11, Adrian Chadd wrote: >>>>> Is it perhaps doing disk IO using mmap? >>>> >>>> how can i check, whether that's the case or not? >>> >>> Use truss(1) for instance. >>> >>> However, unless there are *practical* problems, a high number of >>> page faults is not an indication for problems. Although it may >>> sound scary, page faults are a feature of the memory management. >> >> unfortunately truss(1) is crashing chromium :( i opened up a new >> thread reagarding this issue on freebsd-current@. > Could you try ktrace? It works for me > >> another thing i noticed is the increase in system calls caused by >> chromium. let's have a look at hub.freebsd.org: *snip* > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > without chrome. > > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > 24343 > > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) *snip* > Some work was done by kib@ to create a kernel page strong current time > and other misc info to eliminate gettimeofday kind syscalls. Bits of > it were commited but I'm not sure if it was finished. But anyway > calling gettimeofday hundreds of times per second is a chrome bug. Is it Chrome or a supporting library that is making the call. I have been trying, when I have time, to track down an issue similar to this with Firefox (at least 4 and 5) that causes Xorg to run close to 100% while Firefox creates a new tab under certain circumstances. The best example is to start the Add-ons Manager, search for something such as Google in the Add-ons search box and click the "See all 1003 results" at the bottom of the results page. Xorg is busy making a large number of gettimeofday() and clock_gettime() calls amongst other calls. This is with stable/8 r223876. The window manager does not matter. At least, Fluxbox and TWM exhibit this. However, the size of the Firefox window does (close to 1680x1050). Also, the window must be the top window and not minimized. I have seen it on my system with nVidia drivers and a VirtualBox guest hosted by WinXP. I read a rumor in a forum--it must be true! ;)-- that it was Firefox updating the title of the window incessantly as the tab is created. An interesting workaround to this tab creation issue is to set browser.tabs.loadDivertedInBackground to True. It does not fix all cases. >> i ran the following command twice. first time without running >> chromium and the second time with chromium running: >> >> otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" >> 2178187850 system calls >> 2178189739 system calls >> >> otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system calls" >> 2177998835 system calls >> 2178022003 system calls >> >> so it's 2k/sec vs. 23k/sec!!!! For my situation with Firefox, it jumps from about 2K/sec to 49K/sec. Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 08:05:50 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D19891065673; Thu, 28 Jul 2011 08:05:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gw0-f50.google.com (mail-gw0-f50.google.com [74.125.83.50]) by mx1.freebsd.org (Postfix) with ESMTP id 463AA8FC13; Thu, 28 Jul 2011 08:05:49 +0000 (UTC) Received: by gwj16 with SMTP id 16so2020564gwj.37 for ; Thu, 28 Jul 2011 01:05:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EAEDmejwhh1vRngxHp+dYNrn7YX2xyK8YPq9l9ZAlt0=; b=n0e4K9/gXPbYXghCIVluM4ZZliI9UYYN6idWRydcD88NAiYhktPPvRdO1oVYrARdo4 rDb53FQoWecMz9f++kgyp2auftVNUU8u37tz0zAPCb0Vpkt/ONlhY9Vg0sZariOOkDkH /5/FHEOq/HcHJRiq02YTK3YEJU+n8Lpmp6BAs= MIME-Version: 1.0 Received: by 10.151.86.11 with SMTP id o11mr529408ybl.386.1311840349205; Thu, 28 Jul 2011 01:05:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.197.5 with HTTP; Thu, 28 Jul 2011 01:05:48 -0700 (PDT) In-Reply-To: References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> Date: Thu, 28 Jul 2011 16:05:48 +0800 X-Google-Sender-Auth: A_rIVt2NrtWRAhoZnydGJv_tewI Message-ID: From: Adrian Chadd To: "Sean C. Farley" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Norberto Lopes , Alexander Best , Gleb Kurtsou , Matthias Andree , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 08:05:50 -0000 Surely you could trace the X11 IPC in dtrace or something, and see what the actual messages are? (Surely there's X11 protocol profiling stuff out there?) Adrian On 28 July 2011 10:12, Sean C. Farley wrote: > On Wed, 27 Jul 2011, Gleb Kurtsou wrote: > >> On (27/07/2011 00:48), Alexander Best wrote: >>> >>> On Mon Jul 25 11, Matthias Andree wrote: >>>> >>>> Am 25.07.2011 09:21, schrieb Alexander Best: >>>>> >>>>> On Mon Jul 25 11, Adrian Chadd wrote: >>>>>> >>>>>> Is it perhaps doing disk IO using mmap? >>>>> >>>>> how can i check, whether that's the case or not? >>>> >>>> Use truss(1) for instance. >>>> >>>> However, unless there are *practical* problems, a high number of page >>>> faults is not an indication for problems. =A0Although it may sound sca= ry, page >>>> faults are a feature of the memory management. >>> >>> unfortunately truss(1) is crashing chromium :( i opened up a new thread >>> reagarding this issue on freebsd-current@. >> >> Could you try ktrace? It works for me >> >>> another thing i noticed is the increase in system calls caused by >>> chromium. =A0let's have a look at hub.freebsd.org: > > *snip* > >> About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k >> without chrome. >> >> Looks like there is a lot of clock_gettime and gettimeofday syscalls. >> ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l >> =A024343 >> >> ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 >> 12747 chrome =A0 15.077376 CALL =A0gettimeofday(0x7fffff7f9630,0x7fffff7= f9640) >> 12747 chrome =A0 15.077396 CALL =A0clock_gettime(0x4,0x7fffffbfb6f0) > > *snip* > >> Some work was done by kib@ to create a kernel page strong current time a= nd >> other misc info to eliminate gettimeofday kind syscalls. =A0Bits of it w= ere >> commited but I'm not sure if it was finished. =A0But anyway calling >> gettimeofday hundreds of times per second is a chrome bug. > > Is it Chrome or a supporting library that is making the call. > > I have been trying, when I have time, to track down an issue similar to t= his > with Firefox (at least 4 and 5) that causes Xorg to run close to 100% whi= le > Firefox creates a new tab under certain circumstances. =A0The best exampl= e is > to start the Add-ons Manager, search for something such as Google in the > Add-ons search box and click the "See all 1003 results" at the bottom of = the > results page. =A0Xorg is busy making a large number of gettimeofday() and > clock_gettime() calls amongst other calls. > > This is with stable/8 r223876. =A0The window manager does not matter. =A0= At > least, Fluxbox and TWM exhibit this. =A0However, the size of the Firefox > window does (close to 1680x1050). =A0Also, the window must be the top win= dow > and not minimized. =A0I have seen it on my system with nVidia drivers and= a > VirtualBox guest hosted by WinXP. > > I read a rumor in a forum--it must be true! =A0;)-- that it was Firefox > updating the title of the window incessantly as the tab is created. =A0An > interesting workaround to this tab creation issue is to set > browser.tabs.loadDivertedInBackground to True. =A0It does not fix all cas= es. > >>> i ran the following command twice. first time without running chromium >>> and the second time with chromium running: >>> >>> otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system >>> calls" >>> 2178187850 system calls >>> 2178189739 system calls >>> >>> otaku% vmstat -s|grep "system calls"; sleep 1; vmstat -s|grep "system >>> calls" >>> 2177998835 system calls >>> 2178022003 system calls >>> >>> so it's 2k/sec vs. 23k/sec!!!! > > For my situation with Firefox, it jumps from about 2K/sec to 49K/sec. > > Sean > -- > scf@FreeBSD.org > From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 14:09:35 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CB7F106564A for ; Thu, 28 Jul 2011 14:09: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 55EBF8FC1F for ; Thu, 28 Jul 2011 14:09:33 +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 RAA24652 for ; Thu, 28 Jul 2011 17:09:32 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E316D9C.6060007@FreeBSD.org> Date: Thu, 28 Jul 2011 17:09:32 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: oddities with fgrep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 14:09:35 -0000 $ fgrep -w -r CS drm ... drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (1<<8) $ fgrep -w -r CSY drm ... drm/include/drm/drm_mode.h:#define DRM_MODE_FLAG_NCSYNC (1<<8) $ fgrep -w -r CSYN drm (exit 1) $ fgrep -w -r NCS drm (exit 1) $ fgrep -w CS drm/include/drm/drm_mode.h (exit 1) So looks like a potential bug in some optimization. -w works correctly without -r. With -r it works correctly for some substrings, but not for others. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 14:11:42 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDCB1065672; Thu, 28 Jul 2011 14:11:42 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id E4E1A8FC15; Thu, 28 Jul 2011 14:11:41 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id CE024167157; Thu, 28 Jul 2011 16:11:40 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1Ye+jXhIbmzV; Thu, 28 Jul 2011 16:11:38 +0200 (CEST) Received: from [10.0.3.3] (188-167-66-148.dynamic.chello.sk [188.167.66.148]) by mail.vx.sk (Postfix) with ESMTPSA id E3EF916714E; Thu, 28 Jul 2011 16:11:37 +0200 (CEST) Message-ID: <4E316E19.9040309@FreeBSD.org> Date: Thu, 28 Jul 2011 16:11:37 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110627 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 1.2pre Content-Type: multipart/mixed; boundary="------------000605040303080100060003" Cc: Subject: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 14:11:42 -0000 This is a multi-part message in MIME format. --------------000605040303080100060003 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit The attached patch allows better fine-tuning of jails started via /etc/rc.d, uses the new jail(8) flags (-c -m), the persist parameter and adds ZFS support. Patch is fully backward compatible. Please review, comment and/or test my attached patch. Cheers, mm -- Martin Matuska FreeBSD committer http://blog.vx.sk --------------000605040303080100060003 Content-Type: text/x-patch; name="etc_jail.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="etc_jail.patch" Index: etc/rc.d/jail =================================================================== --- etc/rc.d/jail (revision 224471) +++ etc/rc.d/jail (working copy) @@ -43,6 +43,7 @@ eval _ip=\"\$jail_${_j}_ip\" eval _interface=\"\${jail_${_j}_interface:-${jail_interface}}\" eval _exec=\"\$jail_${_j}_exec\" + eval _params=\"\$jail_${_j}_params\" i=0 while : ; do @@ -83,6 +84,8 @@ i=$((i + 1)) done + eval _zfs=\"\${jail_${_j}_zfs:-}\" + if [ -n "${_exec}" ]; then # simple/backward-compatible execution _exec_start="${_exec}" @@ -98,6 +101,9 @@ fi # The default jail ruleset will be used by rc.subr if none is specified. + if [ -n "jail_devfs_ruleset" -a -n "_zfs" ]; then + jail_devfs_ruleset="devfsrules_jail_zfs" + fi eval _ruleset=\"\${jail_${_j}_devfs_ruleset:-${jail_devfs_ruleset}}\" eval _devfs=\"\${jail_${_j}_devfs_enable:-${jail_devfs_enable}}\" [ -z "${_devfs}" ] && _devfs="NO" @@ -200,6 +206,58 @@ if [ -z "${_rootdir}" ]; then err 3 "$name: No root directory has been defined for ${_j}" fi + + # Security-related parameters + eval _enforce_statfs=\"\$jail_${_j}_enforce_statfs\" + eval _allow_set_hostname=\"\$jail_${_j}_allow_set_hostname\" + eval _allow_sysvipc=\"\$jail_${_j}_allow_sysvipc\" + eval _allow_raw_sockets=\"\$jail_${_j}_allow_raw_sockets\" + eval _allow_chflags=\"\$jail_${_j}_allow_chflags\" + eval _allow_mount=\"\$jail_${_j}_allow_mount\" + eval _allow_socket_af=\"\$jail_${_j}_allow_socket_af\" + eval _allow_quotas=\"\$jail_${_j}_allow_quotas:-0\" + + if [ -z "${_enforce_statfs}" ]; then + _enforce_statfs=`${SYSCTL} -n security.jail.enforce_statfs` + fi + + if [ -z "${_allow_set_hostname}" ]; then + _allow_set_hostname=`${SYSCTL} -n security.jail.set_hostname_allowed` + fi + + if [ -z "${_allow_sysvipc}" ]; then + _allow_sysvipc=`${SYSCTL} -n security.jail.sysvipc_allowed` + fi + + if [ -z "${_allow_raw_sockets}" ]; then + _allow_raw_sockets=`${SYSCTL} -n security.jail.allow_raw_sockets` + fi + + if [ -z "${_allow_chflags}" ]; then + _allow_chflags=`${SYSCTL} -n security.jail.chflags_allowed` + fi + + if [ -z "${_allow_mount}" ]; then + _allow_mount=`${SYSCTL} -n security.jail.mount_allowed` + fi + + if [ -z "${_allow_socket_af}" ]; then + _tmpval=`${SYSCTL} -n security.jail.socket_unixiproute_only` + if [ "${_tmpval}" = "0" ]; then + _allow_socket_af=1 + else + _allow_socket_af=0 + fi + fi + + _security_params="enforce_statfs=${_enforce_statfs} \ + allow.set_hostname=${_allow_set_hostname} \ + allow.sysvipc=${_allow_sysvipc} \ + allow.raw_sockets=${_allow_raw_sockets} \ + allow.chflags=${_allow_chflags} \ + allow.mount=${_allow_mount} \ + allow.socket_af=${_allow_socket_af} \ + allow.quotas=${allow_quotas}" } # set_sysctl rc_knob mib msg @@ -345,6 +403,36 @@ mount -a -F "${_fstab}" } +# jail_zfs_jailin +# Make zfs datasets manageable from inside a jail +# the "jailed" dataset property must be set to "on" +jail_zfs_jailin() +{ + if [ -n "${_zfs}" ]; then + for _ds in ${_zfs}; do + _jailed=`zfs get -H jailed ${_ds} 2>/dev/null | awk '{ print $3 }'` + if [ "$_jailed" = "on" ]; then + zfs jail "${_jail_id}" ${_ds} 2>/dev/null + fi + done + fi +} + +# jail_zfs_jailout +# Unjail zfs datasets +# the "jailed" dataset property must be set to "on" +jail_zfs_jailout() +{ + if [ -n "${_zfs}" ]; then + for _ds in ${_zfs}; do + _jailed=`zfs get -H jailed ${_ds} 2>/dev/null | awk '{ print $3 }'` + if [ "$_jailed" = "on" ]; then + zfs unjail "${_jail_id}" ${_ds} 2>/dev/null + fi + done + fi +} + # jail_show_addresses jail # Debug print the input for the given _multi aliases # for a jail for init_variables(). @@ -483,10 +571,27 @@ *) ;; esac - # Append address to list of addresses for the jail command. - case "${_addrl}" in - "") _addrl="${_addr}" ;; - *) _addrl="${_addrl},${_addr}" ;; + case "${_type}" in + inet) + # Append address to list of ipv4 addresses for the + # jail command. + case "${_addrl}" in + "") _addrl="${_addr}" ;; + *) _addrl="${_addrl},${_addr}" ;; + esac + ;; + inet6) + # Append address to list of ipv6 addresses for the + # jail command. + case "${_addrl6}" in + "") _addrl6="${_addr}" ;; + *) _addrl6="${_addrl6},${_addr}" ;; + esac + ;; + *) warn "Could not determine address family. Not going" \ + "to set address '${_addr}' for ${_jail}." + continue + ;; esac # Configure interface alias if requested by a given interface @@ -494,14 +599,7 @@ case "${_iface}" in "") continue ;; esac - case "${_type}" in - inet) ;; - inet6) ;; - *) warn "Could not determine address family. Not going" \ - "to ${_action} address '${_addr}' for ${_jail}." - continue - ;; - esac + case "${_action}" in add) ifconfig ${_iface} ${_type} ${_addr}${_mask} alias ;; @@ -576,6 +674,7 @@ continue; fi _addrl="" + _addrl6="" jail_ips "add" if [ -n "${_fib}" ]; then _setfib="setfib -F '${_fib}'" @@ -644,42 +743,54 @@ i=$((i + 1)) done - eval ${_setfib} jail ${_flags} -i ${_rootdir} ${_hostname} \ - \"${_addrl}\" ${_exec_start} > ${_tmp_jail} 2>&1 \ - ${_tmp_jail} 2>&1 \ + ${_consolelog} - echo ${_jail_id} > /var/run/jail_${_jail}.id + echo -n " $_hostname" + tail +2 ${_tmp_jail} >${_consolelog} + echo ${_jail_id} > /var/run/jail_${_jail}.id - i=0 - while : ; do - eval out=\"\${_exec_poststart${i}:-''}\" - [ -z "$out" ] && break - ${out} - i=$((i + 1)) - done - else - jail_umount_fs - jail_ips "del" - echo " cannot start jail \"${_jail}\": " - tail +2 ${_tmp_jail} + i=0 + while : ; do + eval out=\"\${_exec_poststart${i}:-''}\" + [ -z "$out" ] && break + ${out} + i=$((i + 1)) + done + else + jail_zfs_jailout + jail -m jid="${_jail_id}" persist=0 + jail_umount_fs + jail_ips "del" + echo " cannot start jail \"${_jail}\": " + tail +2 ${_tmp_jail} + fi + rm -f ${_tmp_jail} fi - rm -f ${_tmp_jail} done rmdir ${_tmp_dir} echo '.' @@ -707,6 +818,7 @@ eval env -i /usr/sbin/jexec ${_jail_id} ${_exec_stop} \ >> ${_consolelog} 2>&1 fi + jail_zfs_jailout killall -j ${_jail_id} -TERM > /dev/null 2>&1 sleep 1 killall -j ${_jail_id} -KILL > /dev/null 2>&1 Index: etc/defaults/devfs.rules =================================================================== --- etc/defaults/devfs.rules (revision 224471) +++ etc/defaults/devfs.rules (working copy) @@ -83,3 +83,9 @@ add include $devfsrules_hide_all add include $devfsrules_unhide_basic add include $devfsrules_unhide_login + +# Jail with zfs support +# +[devfsrules_jail_zfs=5] +add include $devfsrules_jail +add path zfs unhide Index: etc/defaults/rc.conf =================================================================== --- etc/defaults/rc.conf (revision 224471) +++ etc/defaults/rc.conf (working copy) @@ -695,6 +695,21 @@ #jail_example_mount_enable="NO" # mount/umount jail's fs #jail_example_fstab="" # fstab(5) for mount/umount #jail_example_flags="-l -U root" # flags for jail(8) +#jail_example_params="" # additional parameters for jail(8) +#jail_example_enforce_statfs="" # jail(8) enforce_statfs parameter +#jail_example_allow_set_hostname="" # jail(8) allow.set_hostname parameter +#jail_example_allow_sysvipc="" # jail(8) allow.sysvipc parameter +#jail_example_allow_raw_sockets="" # jail(8) allow.raw_sockets parameter +#jail_example_allow_chflags="" # jail(8) allow.chflags parameter +#jail_example_allow_mount="" # jail(8) allow.mount parameter +#jail_example_allow_socket_af="" # jail(8) allow.socket_af parameter +#jail_example_allow_quotas="" # jail(8) allow.quotas parameter +#jail_example_zfs="" # Space-separated list of ZFS datasets to be + # managed from this jail. For proper operation, + # allow_mount must be defined and enforce_statfs + # must be lower than 2. The "jailed" property + # must be set to "on" on these datasets before starting + # the jail. ############################################################## ### Define source_rc_confs, the mechanism used by /etc/rc.* ## --------------000605040303080100060003-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 14:59:33 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6C67106564A for ; Thu, 28 Jul 2011 14:59:33 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 3EDA58FC17 for ; Thu, 28 Jul 2011 14:59:33 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 9E45818998C for ; Thu, 28 Jul 2011 16:59:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QO-jG1MCINQl for ; Thu, 28 Jul 2011 16:59:30 +0200 (CEST) Received: from [10.0.3.3] (188-167-66-148.dynamic.chello.sk [188.167.66.148]) by mail.vx.sk (Postfix) with ESMTPSA id 75884189980 for ; Thu, 28 Jul 2011 16:59:30 +0200 (CEST) Message-ID: <4E317951.40601@FreeBSD.org> Date: Thu, 28 Jul 2011 16:59:29 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110627 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 1.2pre Content-Type: multipart/mixed; boundary="------------000904070400010408090707" Cc: Subject: [PATCH] jail mount/unmount patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 14:59:33 -0000 This is a multi-part message in MIME format. --------------000904070400010408090707 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Please review my attached patch. The patch fixes f_mntonname with mount/unmount inside a jail with allow.mount enabled. Filesystems mountable in a jail require the VFCF_JAIL flag (currently only ZFS). With this patch, mount and unmount works both with enforce_statfs = 0 and enforce_statfs = 1. I suggest disabling mount/unmount for jails with enforce_statfs = 2, as this is contradictory and does not play well with or without this patch. I have successfully tested this patch with ZFS, nullfs and tmpfs. To enable nullfs for a jail, you have to modify tmpfs/tmpfs_vfsops.c and recompile the tmpfs module: -VFS_SET(tmpfs_vfsops, tmpfs, 0); +VFS_SET(tmpfs_vfsops, tmpfs, VFCF_JAIL); To enable tmpfs for a jail, you have to modify nullfs/null_vfsops.c and recompile the nullfs module: -VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK); +VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK | VFCF_JAIL); The filesystems can be successfully mounted/unmounted inside a jail and also unmounted from the parent host without problems. The mount inside jail, a jail needs allow.mount=1 and enforce.statfs=0 or enforce.statfs=1, for more information see jail(8) I assume other filesystem not dealing with devices may work correctly with this patch, too (e.g. nfs). With jailed nullfs we can run tinderbox in a jail ;) Please review, comment and/or test my attached patch. Cheers, mm -- Martin Matuska FreeBSD committer http://blog.vx.sk --------------000904070400010408090707 Content-Type: text/x-patch; name="jail_mount_unmount.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="jail_mount_unmount.patch" Index: src/sys/kern/kern_jail.c =================================================================== --- src/sys/kern/kern_jail.c (revision 224297) +++ src/sys/kern/kern_jail.c (working copy) @@ -3858,7 +3858,8 @@ case PRIV_VFS_UNMOUNT: case PRIV_VFS_MOUNT_NONUSER: case PRIV_VFS_MOUNT_OWNER: - if (cred->cr_prison->pr_allow & PR_ALLOW_MOUNT) + if (cred->cr_prison->pr_allow & PR_ALLOW_MOUNT && + cred->cr_prison->pr_enforce_statfs != 2) return (0); else return (EPERM); Index: src/sys/kern/vfs_mount.c =================================================================== --- src/sys/kern/vfs_mount.c (revision 224297) +++ src/sys/kern/vfs_mount.c (working copy) @@ -1007,6 +1007,7 @@ struct vfsconf *vfsp; struct nameidata nd; struct vnode *vp; + char realfspath[MNAMELEN]; int error; /* @@ -1023,6 +1024,21 @@ } /* + * If we are jailed, construct real filesystem path + */ + if (jailed(td->td_ucred) && + strcmp(td->td_ucred->cr_prison->pr_path, "/") != 0) { + if (strlen(td->td_ucred->cr_prison->pr_path) + + strlen(fspath) >= MNAMELEN) + return (ENAMETOOLONG); + strlcpy(realfspath, td->td_ucred->cr_prison->pr_path, + sizeof(realfspath)); + strlcat(realfspath, fspath, sizeof(realfspath)); + } else { + strlcpy(realfspath, fspath, sizeof(realfspath)); + } + + /* * Do not allow NFS export or MNT_SUIDDIR by unprivileged users. */ if (fsflags & MNT_EXPORTED) { @@ -1070,7 +1086,7 @@ NDFREE(&nd, NDF_ONLY_PNBUF); vp = nd.ni_vp; if ((fsflags & MNT_UPDATE) == 0) { - error = vfs_domount_first(td, vfsp, fspath, vp, fsflags, + error = vfs_domount_first(td, vfsp, realfspath, vp, fsflags, optlist); } else { error = vfs_domount_update(td, vp, fsflags, optlist); @@ -1107,6 +1123,7 @@ struct mount *mp; char *pathbuf; int error, id0, id1; + char realfspath[MNAMELEN]; AUDIT_ARG_VALUE(uap->flags); if (jailed(td->td_ucred) || usermount == 0) { @@ -1139,10 +1156,23 @@ } mtx_unlock(&mountlist_mtx); } else { - AUDIT_ARG_UPATH1(td, pathbuf); + /* + * If we are jailed and enforce_statfs == 1 + * construct real filesystem path + */ + if (jailed(td->td_ucred) && + td->td_ucred->cr_prison->pr_enforce_statfs == 1 && + strcmp(td->td_ucred->cr_prison->pr_path, "/") != 0) { + strlcpy(realfspath, td->td_ucred->cr_prison->pr_path, + sizeof(realfspath)); + strlcat(realfspath, pathbuf, sizeof(realfspath)); + } else { + strlcpy(realfspath, pathbuf, sizeof(realfspath)); + } + AUDIT_ARG_UPATH1(td, realfspath); mtx_lock(&mountlist_mtx); TAILQ_FOREACH_REVERSE(mp, &mountlist, mntlist, mnt_list) { - if (strcmp(mp->mnt_stat.f_mntonname, pathbuf) == 0) + if (strcmp(mp->mnt_stat.f_mntonname, realfspath) == 0) break; } mtx_unlock(&mountlist_mtx); --------------000904070400010408090707-- From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 16:25:32 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1BAE106566C; Thu, 28 Jul 2011 16:25:32 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [64.34.175.71]) by mx1.freebsd.org (Postfix) with ESMTP id 629828FC15; Thu, 28 Jul 2011 16:25:32 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by m2.gritton.org (8.14.4/8.14.4) with ESMTP id p6SGPVpF048742; Thu, 28 Jul 2011 10:25:31 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4E318D75.608@FreeBSD.org> Date: Thu, 28 Jul 2011 10:25:25 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110727 Thunderbird/5.0 MIME-Version: 1.0 To: FreeBSD Current References: <4E316E19.9040309@FreeBSD.org> In-Reply-To: <4E316E19.9040309@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Martin Matuska Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 16:25:32 -0000 Since I missed the 9.0 boat with jail config file capability, something like this seems necessary; rc.d/jail has long been unable to handle the full scale of what jail(8) can do. I gather that setting persist is necessary for the ZFS operation. As long as we're making the parameter setting more generic from rc, we should handle the case where persist is specified in ${_params}, and not always set/reset it around the jail creation unless ZFS is used. Also, why the specific inclusion of the security-related parameters? They could just be folded into ${_params}, and if left unspecified then jail(8) should by default do the right thing. - Jamie On 07/28/11 08:11, Martin Matuska wrote: > The attached patch allows better fine-tuning of jails started via > /etc/rc.d, uses the new jail(8) flags (-c -m), the persist parameter and > adds ZFS support. > Patch is fully backward compatible. > > Please review, comment and/or test my attached patch. > > Cheers, > mm From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 16:31:32 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E32861065672; Thu, 28 Jul 2011 16:31:32 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [64.34.175.71]) by mx1.freebsd.org (Postfix) with ESMTP id 8AC7C8FC1F; Thu, 28 Jul 2011 16:31:32 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by m2.gritton.org (8.14.4/8.14.4) with ESMTP id p6SGCUxh048618; Thu, 28 Jul 2011 10:12:31 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4E318A69.2080303@FreeBSD.org> Date: Thu, 28 Jul 2011 10:12:25 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110727 Thunderbird/5.0 MIME-Version: 1.0 To: FreeBSD Current References: <4E317951.40601@FreeBSD.org> In-Reply-To: <4E317951.40601@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Martin Matuska Subject: Re: [PATCH] jail mount/unmount patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 16:31:33 -0000 There's a curious asymmetry here: enforce_statfs==1 is checked for munging the name on unmounting, but not on mounting. I see the point on the unmount side, as statfs would give the full un-jailed pathname and an admin would naturally want to unmount what he sees mounted, but without the same logic on the mount side, it would mean the unmount path is different from the mount path which would make fstab not use for mounting inside a jail. But then, enforce_statfs==0 is a strange world to be in anyway. I'm not sure about enforce_statfs!=2 in the privilege check. It seems a reasonable response to a contradictory set of permissions, but then so does the strange case if being able to mount a filesystem and then not being able to see it in statfs. - Jamie On 07/28/11 08:59, Martin Matuska wrote: > Please review my attached patch. > > The patch fixes f_mntonname with mount/unmount inside a jail with allow.mount enabled. > Filesystems mountable in a jail require the VFCF_JAIL flag (currently only ZFS). > > With this patch, mount and unmount works both with enforce_statfs = 0 and enforce_statfs = 1. > I suggest disabling mount/unmount for jails with enforce_statfs = 2, as this is contradictory and does not play well with or without this patch. > > I have successfully tested this patch with ZFS, nullfs and tmpfs. > > To enable nullfs for a jail, you have to modify tmpfs/tmpfs_vfsops.c and recompile the tmpfs module: > -VFS_SET(tmpfs_vfsops, tmpfs, 0); > +VFS_SET(tmpfs_vfsops, tmpfs, VFCF_JAIL); > > To enable tmpfs for a jail, you have to modify nullfs/null_vfsops.c and recompile the nullfs module: > -VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK); > +VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK | VFCF_JAIL); > > The filesystems can be successfully mounted/unmounted inside a jail and also unmounted from the parent host without problems. > > The mount inside jail, a jail needs allow.mount=1 and enforce.statfs=0 or enforce.statfs=1, for more information see jail(8) > I assume other filesystem not dealing with devices may work correctly with this patch, too (e.g. nfs). > > With jailed nullfs we can run tinderbox in a jail ;) > > Please review, comment and/or test my attached patch. > > Cheers, > mm From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 18:00:47 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83BBA106566C; Thu, 28 Jul 2011 18:00:47 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 1E3648FC08; Thu, 28 Jul 2011 18:00:47 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 40D7618AC7E; Thu, 28 Jul 2011 20:00:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0fFdb-01nGoL; Thu, 28 Jul 2011 20:00:44 +0200 (CEST) Received: from [10.9.8.3] (chello085216231078.chello.sk [85.216.231.78]) by mail.vx.sk (Postfix) with ESMTPSA id 686C718AC76; Thu, 28 Jul 2011 20:00:43 +0200 (CEST) Message-ID: <4E31A3CD.60500@FreeBSD.org> Date: Thu, 28 Jul 2011 20:00:45 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Jamie Gritton References: <4E316E19.9040309@FreeBSD.org> <4E318D75.608@FreeBSD.org> In-Reply-To: <4E318D75.608@FreeBSD.org> X-Enigmail-Version: 1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: FreeBSD Current Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 18:00:47 -0000 If you start jail(8) witth "-c" (the new "param" way,) the values of the actual security.jail. variables are not initialized inside the jail, default values are used instead. I don't know if this is intentional, but probably yes. Default enforce_statfs=2, allow.mount=0. As of me we can leave everything for ${_params}, but then ${_zfs} makes sense only if enforce_statfs<2 and allow.mount=1. Regarding zfs, if you want to operate zfs from the very start of a jail (and e.g. make use of /etc/rc.d/zfs which has jail support), you have to pair datasets with an existing jail. In simple words, you have to create a process-less jail (persist=1), attach zfs datasets and then run the command. The persist option can be made optional - but we always start with persist=1, then we can set (or not) persist=0 depending on user setting. The question that opens, should we remove a persisting jail on "stop"? Or should we support new commands "create" and "remove" in addition to "start" and "stop"? Create would just make a processless jail, remove would wipe out a jail and start/stop would just deal with the processes (if persist=0 the old way, of course)? Cheers, mm Dňa 28. 7. 2011 18:25, Jamie Gritton wrote / napísal(a): > Since I missed the 9.0 boat with jail config file capability, something > like this seems necessary; rc.d/jail has long been unable to handle the > full scale of what jail(8) can do. > > I gather that setting persist is necessary for the ZFS operation. As > long as we're making the parameter setting more generic from rc, we > should handle the case where persist is specified in ${_params}, and not > always set/reset it around the jail creation unless ZFS is used. > > Also, why the specific inclusion of the security-related parameters? > They could just be folded into ${_params}, and if left unspecified then > jail(8) should by default do the right thing. > > - Jamie > > > On 07/28/11 08:11, Martin Matuska wrote: >> The attached patch allows better fine-tuning of jails started via >> /etc/rc.d, uses the new jail(8) flags (-c -m), the persist parameter and >> adds ZFS support. >> Patch is fully backward compatible. >> >> Please review, comment and/or test my attached patch. >> >> Cheers, >> mm -- Martin Matuska FreeBSD committer http://blog.vx.sk From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 18:47:41 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1B941065673; Thu, 28 Jul 2011 18:47:41 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [64.34.175.71]) by mx1.freebsd.org (Postfix) with ESMTP id 790A28FC0C; Thu, 28 Jul 2011 18:47:41 +0000 (UTC) Received: from guppy.corp.verio.net (fw.oremut02.us.wh.verio.net [198.65.168.24]) (authenticated bits=0) by m2.gritton.org (8.14.4/8.14.4) with ESMTP id p6SIlegg050284; Thu, 28 Jul 2011 12:47:40 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4E31AEC6.8080106@FreeBSD.org> Date: Thu, 28 Jul 2011 12:47:34 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110727 Thunderbird/5.0 MIME-Version: 1.0 To: FreeBSD Current References: <4E316E19.9040309@FreeBSD.org> <4E318D75.608@FreeBSD.org> <4E31A3CD.60500@FreeBSD.org> In-Reply-To: <4E31A3CD.60500@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Martin Matuska Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 18:47:41 -0000 Yes, it was intentional to move away from the global sysctls and to the per-jail parameters instead. It makes more sense once config files come into play, which can do a better job of providing global defaults as well as per-jail parameters. The connection between ZFS and persist makes sense. So for ZFS-based jail you'd want to set (and then reset) persist. For others, this could be left to the user. The changes to jail(8) for config files also sets persist when creating jails, and then clears it at a later stage unless the user specifies to keep it set. It looks like I might want to add some ZFS support to the new jail(8). I would prefer to keep things simpler regarding create/start and remove/stop, and keep them tied together. - Jamie On 07/28/11 12:00, Martin Matuska wrote: > If you start jail(8) witth "-c" (the new "param" way,) the values of the > actual security.jail. variables are not initialized inside the jail, > default values are used instead. I don't know if this is intentional, > but probably yes. Default enforce_statfs=2, allow.mount=0. > As of me we can leave everything for ${_params}, but then ${_zfs} makes > sense only if enforce_statfs<2 and allow.mount=1. > > Regarding zfs, if you want to operate zfs from the very start of a jail > (and e.g. make use of /etc/rc.d/zfs which has jail support), you have to > pair datasets with an existing jail. In simple words, you have to create > a process-less jail (persist=1), attach zfs datasets and then run the > command. The persist option can be made optional - but we always start > with persist=1, then we can set (or not) persist=0 depending on user > setting. > > The question that opens, should we remove a persisting jail on "stop"? > Or should we support new commands "create" and "remove" in addition to > "start" and "stop"? Create would just make a processless jail, remove > would wipe out a jail and start/stop would just deal with the processes > (if persist=0 the old way, of course)? > > Cheers, > mm > > Dňa 28. 7. 2011 18:25, Jamie Gritton wrote / napísal(a): >> Since I missed the 9.0 boat with jail config file capability, something >> like this seems necessary; rc.d/jail has long been unable to handle the >> full scale of what jail(8) can do. >> >> I gather that setting persist is necessary for the ZFS operation. As >> long as we're making the parameter setting more generic from rc, we >> should handle the case where persist is specified in ${_params}, and not >> always set/reset it around the jail creation unless ZFS is used. >> >> Also, why the specific inclusion of the security-related parameters? >> They could just be folded into ${_params}, and if left unspecified then >> jail(8) should by default do the right thing. >> >> - Jamie >> >> >> On 07/28/11 08:11, Martin Matuska wrote: >>> The attached patch allows better fine-tuning of jails started via >>> /etc/rc.d, uses the new jail(8) flags (-c -m), the persist parameter and >>> adds ZFS support. >>> Patch is fully backward compatible. >>> >>> Please review, comment and/or test my attached patch. >>> >>> Cheers, >>> mm From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 19:36:37 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1297E106570F for ; Thu, 28 Jul 2011 19:36:37 +0000 (UTC) (envelope-from lwhalen@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C1A568FC1D for ; Thu, 28 Jul 2011 19:36:36 +0000 (UTC) Received: by vxg33 with SMTP id 33so3046604vxg.13 for ; Thu, 28 Jul 2011 12:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=VTmoiJuIo/uix4XA1X3R6x8MumkjCa+s9Ff4qSWppyQ=; b=I/jVvjkygxiYXZm4767YbqaJp4zorG+ArrObZJn7MZuCbjcpAKVW/NGkmgrrW7K268 p4muiVKCSWn62yKJ6QOxymk4zCBRyJ9cWLR2SSQNBBjehAs/pQTqA1IqARc60xS4ZjgV FXSHr2Lc51i4vimelY5cdVfewUvlmQ70VVzfo= Received: by 10.220.117.143 with SMTP id r15mr114851vcq.113.1311880381919; Thu, 28 Jul 2011 12:13:01 -0700 (PDT) Received: from lwhalen-mbpro.local (bastion-ext.sermo.com [38.104.7.126]) by mx.google.com with ESMTPS id o3sm434698vca.26.2011.07.28.12.13.00 (version=SSLv3 cipher=OTHER); Thu, 28 Jul 2011 12:13:01 -0700 (PDT) Message-ID: <4E31B4BC.5060604@gmail.com> Date: Thu, 28 Jul 2011 15:13:00 -0400 From: Lee Whalen User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: recovering data from a RAID1 array from a single disk on a different system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 19:36:37 -0000 Hi there, my apologies in advance if this is the wrong mailing list for this type of question. I have a problem with a previously-RAID1'd FreeBSD filesystem I was hoping someone could help me with. The background is this: The disks originally belong to a client of a friend running an old obsolete (as in, the company doesn't exist any more) home NAS device by Fastera (model NAS-T2, two 200GB IDE disks in a RAID1 configuration, unknown version of FreeBSD). The NAS gave up the ghost when the OS (stored on a CF card) recently melted down, rendering the device unbootable. The IDE drives seem unharmed, after sticking them in a USB drive cage they present themselves to both Linux and FreeBSD operating systems and both OSes can see partition tables, disklabels, etc. Unfortunately, because of what appears to be a previously-configured software RAID1 scheme I can't seem to simply mount the slices under *nix or *BSD and copy the data off. Currently one of the drives is attached via USB cradle to a freshly installed FreeBSD 8.2 VM. I was able to get a good chunk of the data back off of it with a tool called "photorec", which (to be brief) scans the block device looking for file-header signatures and makes educated guesses as to whether it's $file_type_x, $file_type_y and so forth, copying to a separate recovery directory without the benefit of the original file name or previous directory structure. It's cool, the guy technically has his data back (or will, after a couple of hours of manual sorting), but I've got enough time into this that, by $deity, I Have To Win() by being able to mount the (by all accounts happy and uncorrupted) filesystem. I was hoping this might be the proper mailing list for insight into ccd/geom/vinum. What I think needs to happen at some level (and please feel free to correct me if I'm wrong) is one of two things: 1. Using CCD or one of the other utilities, I need to add this USB-caged disk into a temporary RAID-1 array in a 'degraded' state so FreeBSD sees the disklabels as something other than type "raid". This will allow me to mount the preexisting partitions as normal, and copy the data off the disk. If there's some way I can positively identify a given partition/slice as having been created by either ccd/geom/vinum, that would be awesome. 2. Using dd or something similar, I need to image the existing disk to a file and strip the first N bytes that (presumably) hold the software RAID headers. My hope is that if I get the offset right, the mount command will pick up on the partition/slice data it needs and allow me to mount the image via loopback, copying the data off as above. Does anyone have any insight that could help me accomplish the above, or a better way to approach the problem? Here's some information about the disk itself (all commands run from the FreeBSD 8.2 VM): ls -l /dev/da0* http://pastebin.com/6Sv8T4Mg fdisk /dev/da0 output http://pastebin.com/ZzPKUXDL bsdlabel /dev/da0* http://pastebin.com/3BPKbYZ6 newfs -N "dry run" data (possible superblock locations, blocksize defaults, etc for /dev/da0s3a, the 'important' one) http://pastebin.com/b9nLFsjK incomplete "scan_ffs /dev/da0" run: http://pastebin.com/28T8Fr67 I hope this helps, any assistance folks could provide would be MOST helpful! Please don't hesitate to let me know if you need more information, I'm happy to respond as quick as I possibly can. Many thanks in advance, --Lee From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 20:03:07 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id B99781065678; Thu, 28 Jul 2011 20:03:07 +0000 (UTC) Date: Thu, 28 Jul 2011 20:03:07 +0000 From: Alexander Best To: =?iso-8859-15?Q?Ren=E9?= Ladan Message-ID: <20110728200307.GA65254@freebsd.org> References: <20110724212544.GA57733@freebsd.org> <20110725072102.GA24938@freebsd.org> <4E2D2C32.5010602@gmx.de> <20110727004850.GA63109@freebsd.org> <20110727083339.GA12233@tops> <20110727092338.GA10526@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: Norberto Lopes , Gleb Kurtsou , Matthias Andree , Adrian Chadd , freebsd-current@freebsd.org Subject: Re: chromium port causing massive I/O faults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 20:03:07 -0000 On Wed Jul 27 11, Ren Ladan wrote: > 2011/7/27 Alexander Best : > > On Wed Jul 27 11, Ren Ladan wrote: > >> 2011/7/27 Gleb Kurtsou : > >> > On (27/07/2011 00:48), Alexander Best wrote: > >> >> On Mon Jul 25 11, Matthias Andree wrote: > >> >> > Am 25.07.2011 09:21, schrieb Alexander Best: > >> >> > > On Mon Jul 25 11, Adrian Chadd wrote: > >> >> > >> Is it perhaps doing disk IO using mmap? > >> >> > > > >> >> > > how can i check, whether that's the case or not? > >> >> > > >> >> > Use truss(1) for instance. > >> >> > > >> >> > However, unless there are *practical* problems, a high number of page > >> >> > faults is not an indication for problems. Although it may sound scary, > >> >> > page faults are a feature of the memory management. > >> >> > >> >> unfortunately truss(1) is crashing chromium :( i opened up a new thread > >> >> reagarding this issue on freebsd-current@. > >> > Could you try ktrace? It works for me > >> > > >> >> another thing i noticed is the increase in system calls caused by chromium. > >> >> let's have a look at hub.freebsd.org: > >> >> > >> >> uptime = 149 days > >> >> > >> >> and 'vmstat -s' reports: > >> >> > >> >> 2168697753 cpu context switches > >> >> 2266220366 device interrupts > >> >> 2902880931 software interrupts > >> >> 3779075897 traps > >> >> 902107847 system calls > >> >> > >> >> now on my box: > >> >> > >> >> uptime = 2 days > >> >> > >> >> and 'vmstat -s' reports: > >> >> > >> >> 1155995386 cpu context switches > >> >> 164577882 device interrupts > >> >> 189456976 software interrupts > >> >> 137007580 traps > >> >> 2178434582 system calls > >> > About 2.5k syscalls with chrome + a lot of other stuff running. 1.5k > >> > without chrome. > >> > > >> > Looks like there is a lot of clock_gettime and gettimeofday syscalls. > >> > ~ % kdump -m 1 -f ktrace.out | grep 'CALL .*gettime' | wc -l > >> > 24343 > >> > > >> > ~ % kdump -E -m 1 -f ktrace.out | grep 'CALL .*gettime' | tail -20 > >> > 12747 chrome 15.077376 CALL gettimeofday(0x7fffff7f9630,0x7fffff7f9640) > >> > 12747 chrome 15.077396 CALL clock_gettime(0x4,0x7fffffbfb6f0) > >> > 12747 chrome 15.077497 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.077609 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.077723 CALL gettimeofday(0x7fffffbfb650,0) > >> > 12747 chrome 15.077845 CALL clock_gettime(0,0x7fffffbfb2b0) > >> > 12747 chrome 15.078337 CALL clock_gettime(0x4,0x7fffff9fa630) > >> > 12747 chrome 15.078544 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078587 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078632 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.078674 CALL clock_gettime(0x4,0x7fffff9fa650) > >> > 12747 chrome 15.082803 CALL gettimeofday(0x7ffffedd3630,0x7ffffedd3640) > >> > 12747 chrome 15.084644 CALL gettimeofday(0x7fffffbfb650,0x7fffffbfb660) > >> > 12747 chrome 15.084746 CALL clock_gettime(0x4,0x7fffffbfb670) > >> > 12747 chrome 15.084815 CALL clock_gettime(0x4,0x7fffffbfb670) > >> > 12747 chrome 15.086620 CALL gettimeofday(0x7ffffefd4650,0x7ffffefd4660) > >> > 12747 chrome 15.086736 CALL clock_gettime(0x4,0x7ffffefd4670) > >> > 12747 chrome 15.086815 CALL clock_gettime(0x4,0x7ffffefd4670) > >> > 12747 chrome 15.098315 CALL gettimeofday(0x7fffffffafe0,0x7fffffffaff0) > >> > 12747 chrome 15.098680 CALL clock_gettime(0x4,0x7fffffffb250) > >> > > >> > Some work was done by kib@ to create a kernel page strong current time > >> > and other misc info to eliminate gettimeofday kind syscalls. Bits of it > >> > were commited but I'm not sure if it was finished. > >> > But anyway calling gettimeofday hundreds of times per second is a chrome > >> > bug. > >> > > >> > FreeBSD 9.0-CURRENT #2 r224003+777e962: Thu Jul 14 13:04:55 EEST 2011 > >> > chromium-11.0.696.57_1 > >> ^^^^^^^^^^^^^ > >> Can you retry with an up-to-date version of www/chromium? The > >> codebase of chromium > >> changes quite fast so not using the latest version in ports might > >> render obsolete (and > >> upstream unsupported) results. > > > > my tests were done with chromium-12.0.742.124 btw. > > > Ok, I'll do some tests with the beta version from the chruetertee > repository (13.0.782.99). it looks as if this issue was fixed somewhere between 14.0.797.0 and 14.0.817.0 according to http://code.google.com/p/chromium/issues/detail?id=77625 > >> > >> Ren > >> -- > >> http://www.rene-ladan.nl/ > > From owner-freebsd-current@FreeBSD.ORG Thu Jul 28 20:10:09 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DBFE106566C; Thu, 28 Jul 2011 20:10:09 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 00D1C8FC0A; Thu, 28 Jul 2011 20:10:09 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 0EA4F189694; Thu, 28 Jul 2011 22:10:08 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NN7rb2JsR+Z0; Thu, 28 Jul 2011 22:10:05 +0200 (CEST) Received: from [10.9.8.3] (chello085216231078.chello.sk [85.216.231.78]) by mail.vx.sk (Postfix) with ESMTPSA id 2B294189677; Thu, 28 Jul 2011 22:10:02 +0200 (CEST) Message-ID: <4E31C21B.2090906@FreeBSD.org> Date: Thu, 28 Jul 2011 22:10:03 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Jamie Gritton References: <4E317951.40601@FreeBSD.org> <4E318A69.2080303@FreeBSD.org> In-Reply-To: <4E318A69.2080303@FreeBSD.org> X-Enigmail-Version: 1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: FreeBSD Current Subject: Re: [PATCH] jail mount/unmount patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Jul 2011 20:10:09 -0000 For vfs_mount, the easiest way to look at this is to follow the path of the "realfspath" argument. It goes to vfs_domount_first() and ends up in vfs_mount_alloc() where is the only place it is consumed: strlcpy(mp->mnt_stat.f_mntonname, fspath, MNAMELEN); The original fspath (not realfspath) is correctly consumed in vnode initialization - vfs_domount(): NDINIT(...) that ends in namei() of vfs_lookup.c - here we are processing jail paths again so it gets translated properly and the correct vnode is picked. We cannot write the supplied fspath to f_mntonname as this won't reflect real path and we cannot unmount by name anymore from host and from jail. If reading, f_mntonname gets translated by prison_enforce_statfs so we should translate it correctly if writing so that it matches the vnode. We cannot add the check to vfs_mount_alloc() because we may blow MNAMELEN. The check could be theoretically moved to vfs_domount_first() before mp = vfs_mount_alloc(...) at the latest. For the enforce_statfs privilege check: with enforce_statfs=2 you are unable to unmount filesystems in a jail as they are simply not found (mount works). Cheers, mm Dňa 28. 7. 2011 18:12, Jamie Gritton wrote / napísal(a): > There's a curious asymmetry here: enforce_statfs==1 is checked for > munging the name on unmounting, but not on mounting. I see the point on > the unmount side, as statfs would give the full un-jailed pathname and > an admin would naturally want to unmount what he sees mounted, but > without the same logic on the mount side, it would mean the unmount path > is different from the mount path which would make fstab not use for > mounting inside a jail. But then, enforce_statfs==0 is a strange world > to be in anyway. > > I'm not sure about enforce_statfs!=2 in the privilege check. It seems a > reasonable response to a contradictory set of permissions, but then so > does the strange case if being able to mount a filesystem and then not > being able to see it in statfs. > > - Jamie > > > On 07/28/11 08:59, Martin Matuska wrote: >> Please review my attached patch. >> >> The patch fixes f_mntonname with mount/unmount inside a jail with >> allow.mount enabled. >> Filesystems mountable in a jail require the VFCF_JAIL flag (currently >> only ZFS). >> >> With this patch, mount and unmount works both with enforce_statfs = 0 >> and enforce_statfs = 1. >> I suggest disabling mount/unmount for jails with enforce_statfs = 2, >> as this is contradictory and does not play well with or without this >> patch. >> >> I have successfully tested this patch with ZFS, nullfs and tmpfs. >> >> To enable nullfs for a jail, you have to modify tmpfs/tmpfs_vfsops.c >> and recompile the tmpfs module: >> -VFS_SET(tmpfs_vfsops, tmpfs, 0); >> +VFS_SET(tmpfs_vfsops, tmpfs, VFCF_JAIL); >> >> To enable tmpfs for a jail, you have to modify nullfs/null_vfsops.c >> and recompile the nullfs module: >> -VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK); >> +VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK | VFCF_JAIL); >> >> The filesystems can be successfully mounted/unmounted inside a jail >> and also unmounted from the parent host without problems. >> >> The mount inside jail, a jail needs allow.mount=1 and >> enforce.statfs=0 or enforce.statfs=1, for more information see jail(8) >> I assume other filesystem not dealing with devices may work correctly >> with this patch, too (e.g. nfs). >> >> With jailed nullfs we can run tinderbox in a jail ;) >> >> Please review, comment and/or test my attached patch. >> >> Cheers, >> mm -- Martin Matuska FreeBSD committer http://blog.vx.sk From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 09:10:34 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2791C106564A for ; Fri, 29 Jul 2011 09:10:34 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id D0D558FC15 for ; Fri, 29 Jul 2011 09:10:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 734A580B2 for ; Fri, 29 Jul 2011 10:54:03 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 5E9D480B1; Fri, 29 Jul 2011 10:53:54 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Alban Hertroys In-Reply-To: <4E31B4BC.5060604@gmail.com> Date: Fri, 29 Jul 2011 10:53:54 +0200 Content-Transfer-Encoding: 8bit Message-Id: <1F86C608-1F80-4144-939C-D46C2180F634@solfertje.student.utwente.nl> References: <4E31B4BC.5060604@gmail.com> To: Lee Whalen X-Mailer: Apple Mail (2.1084) X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Jul 29 10:54:03 2011 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 909,4e32752b12094789815349 X-DSPAM-Factors: 27, Subject*recovering+data, 0.40000, but, 0.40000, but, 0.40000, contains, 0.40000, insights, 0.40000, From*Alban, 0.40000, mount+the, 0.40000, Mime-Version*Message, 0.40000, preexisting, 0.40000, by+either, 0.40000, "RAIDFrame, 0.40000, char, 0.40000, having+been, 0.40000, //www+netbsd, 0.40000, 1+array, 0.40000, or, 0.40000, Message-Id*<1F86C608+1F80, 0.40000, never, 0.40000, an, 0.40000, This+will, 0.40000, indeed, 0.40000, apparently+it's, 0.40000, h+and, 0.40000, of, 0.40000, of, 0.40000, something+that's, 0.40000, as+I, 0.40000 Cc: freebsd-current@freebsd.org Subject: Re: recovering data from a RAID1 array from a single disk on a different system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 09:10:34 -0000 On 28 Jul 2011, at 21:13, Lee Whalen wrote: I'm no expert, but I'll add my insights regardless ;) > 1. Using CCD or one of the other utilities, I need to add this USB-caged > disk into a temporary RAID-1 array in a 'degraded' state so FreeBSD sees As far as I know, CCD (concatenated disk) can not do mirroring, so your RAID-1 disk won't be created using CCD. > the disklabels as something other than type "raid". This will allow me > to mount the preexisting partitions as normal, and copy the data off the > disk. If there's some way I can positively identify a given > partition/slice as having been created by either ccd/geom/vinum, that > would be awesome. According to the man page, descriptions of the various fs_type's are in /usr/include/sys/disklabel.h, and indeed: ... #define FS_RAID 15 /* RAIDFrame drive */ ... static const char *fstypenames[] = { ... "raid", ... }; So, apparently your disk contains a "RAIDFrame drive". I never heard of that before, but apparently it's something that's part of NetBSD: http://www.netbsd.org/docs/guide/en/chap-rf.html So my guess is that the NAS device contained NetBSD instead of FreeBSD. Alban Hertroys -- The scale of a problem often equals the size of an ego. !DSPAM:909,4e32752b12094789815349! From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 10:08:35 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C44C1106564A for ; Fri, 29 Jul 2011 10:08: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 F36968FC0A for ; Fri, 29 Jul 2011 10:08: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 NAA08815 for ; Fri, 29 Jul 2011 13:08:33 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qmjzc-00041p-Ne for freebsd-current@FreeBSD.org; Fri, 29 Jul 2011 13:08:32 +0300 Message-ID: <4E32869E.6080702@FreeBSD.org> Date: Fri, 29 Jul 2011 13:08:30 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: FreeBSD-Current X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: Subject: some smp documentation fixes for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 10:08:35 -0000 This is to account for the recent changes in x86 SMP code: http://people.freebsd.org/~avg/hlt_cpus-doc.diff Please review. Thank you! -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 10:12:00 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC145106564A for ; Fri, 29 Jul 2011 10:12:00 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6DA328FC0C for ; Fri, 29 Jul 2011 10:11:59 +0000 (UTC) Received: by wwe6 with SMTP id 6so3289212wwe.31 for ; Fri, 29 Jul 2011 03:11:59 -0700 (PDT) Received: by 10.227.39.14 with SMTP id d14mr1682368wbe.33.1311932425045; Fri, 29 Jul 2011 02:40:25 -0700 (PDT) Received: from clue.co.za (dsl-185-175-80.dynamic.wa.co.za [41.185.175.80]) by mx.google.com with ESMTPS id gd1sm1585628wbb.61.2011.07.29.02.40.21 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jul 2011 02:40:22 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1QmjYI-0000l5-Ik; Fri, 29 Jul 2011 11:40:18 +0200 Message-Id: To: Alban Hertroys From: Ian FREISLICH In-Reply-To: <1F86C608-1F80-4144-939C-D46C2180F634@solfertje.student.utwente.nl> References: <1F86C608-1F80-4144-939C-D46C2180F634@solfertje.student.utwente.nl> <4E31B4BC.5060604@gmail.com> X-Attribution: BOFH Date: Fri, 29 Jul 2011 11:40:18 +0200 Cc: Lee Whalen , freebsd-current@freebsd.org Subject: Re: recovering data from a RAID1 array from a single disk on a different system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 10:12:00 -0000 Alban Hertroys wrote: > On 28 Jul 2011, at 21:13, Lee Whalen wrote: > > I'm no expert, but I'll add my insights regardless ;) > > > 1. Using CCD or one of the other utilities, I need to add this USB-caged > > disk into a temporary RAID-1 array in a 'degraded' state so FreeBSD sees > > As far as I know, CCD (concatenated disk) can not do mirroring, so > your RAID-1 disk won't be created using CCD. If it's a ccd, just configure a 1 disk mirror using ccdconfig. See ccdconfig(8) for more info. But it sounds like this may be some proprietry RAID format used by the controller in the NAS device. Often the controller doesn't actually do the RAID, so the OP might have some success using ataraid(4) to attach the disks. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 13:54:32 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1EA6106564A; Fri, 29 Jul 2011 13:54:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9B7888FC0C; Fri, 29 Jul 2011 13:54:32 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id DE85246B0C; Fri, 29 Jul 2011 09:54:31 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7CBA98A02C; Fri, 29 Jul 2011 09:54:31 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 29 Jul 2011 09:52:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E32869E.6080702@FreeBSD.org> In-Reply-To: <4E32869E.6080702@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107290952.21332.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Fri, 29 Jul 2011 09:54:31 -0400 (EDT) Cc: Andriy Gapon Subject: Re: some smp documentation fixes for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 13:54:32 -0000 On Friday, July 29, 2011 6:08:30 am Andriy Gapon wrote: > > This is to account for the recent changes in x86 SMP code: > http://people.freebsd.org/~avg/hlt_cpus-doc.diff > Please review. Thank you! Looks good to me. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 20:01:47 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BACF106566C for ; Fri, 29 Jul 2011 20:01:47 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id CF2E78FC14 for ; Fri, 29 Jul 2011 20:01:46 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 08FED14F77A for ; Fri, 29 Jul 2011 22:01:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id i8J86cEivKNi for ; Fri, 29 Jul 2011 22:01:43 +0200 (CEST) Received: from [10.9.8.3] (chello085216231078.chello.sk [85.216.231.78]) by mail.vx.sk (Postfix) with ESMTPSA id 820A314F765 for ; Fri, 29 Jul 2011 22:01:42 +0200 (CEST) Message-ID: <4E3311AA.9080006@FreeBSD.org> Date: Fri, 29 Jul 2011 22:01:46 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <4E317951.40601@FreeBSD.org> In-Reply-To: <4E317951.40601@FreeBSD.org> X-Enigmail-Version: 1.2 Content-Type: multipart/mixed; boundary="------------030307010502070904020200" Cc: Subject: [PATCH] Updated jail mount/unmount patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 20:01:47 -0000 This is a multi-part message in MIME format. --------------030307010502070904020200 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit After implementing a suggestion from pjd@, a new version of the patch is attached, now using a more universal solution - vn_fullpath_global() in the mount part. Dňa 28. 7. 2011 16:59, Martin Matuska wrote / napísal(a): > Please review my attached patch. > > The patch fixes f_mntonname with mount/unmount inside a jail with allow.mount enabled. > Filesystems mountable in a jail require the VFCF_JAIL flag (currently only ZFS). > > With this patch, mount and unmount works both with enforce_statfs = 0 and enforce_statfs = 1. > I suggest disabling mount/unmount for jails with enforce_statfs = 2, as this is contradictory and does not play well with or without this patch. > > I have successfully tested this patch with ZFS, nullfs and tmpfs. > > To enable nullfs for a jail, you have to modify tmpfs/tmpfs_vfsops.c and recompile the tmpfs module: > -VFS_SET(tmpfs_vfsops, tmpfs, 0); > +VFS_SET(tmpfs_vfsops, tmpfs, VFCF_JAIL); > > To enable tmpfs for a jail, you have to modify nullfs/null_vfsops.c and recompile the nullfs module: > -VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK); > +VFS_SET(null_vfsops, nullfs, VFCF_LOOPBACK | VFCF_JAIL); > > The filesystems can be successfully mounted/unmounted inside a jail and also unmounted from the parent host without problems. > > The mount inside jail, a jail needs allow.mount=1 and enforce.statfs=0 or enforce.statfs=1, for more information see jail(8) > I assume other filesystem not dealing with devices may work correctly with this patch, too (e.g. nfs). > > With jailed nullfs we can run tinderbox in a jail ;) > > Please review, comment and/or test my attached patch. > > Cheers, > mm -- Martin Matuska FreeBSD committer http://blog.vx.sk --------------030307010502070904020200 Content-Type: text/plain; name="jail_mount.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="jail_mount.patch" SW5kZXg6IHN5cy9rZXJuL2tlcm5famFpbC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHN5cy9rZXJu L2tlcm5famFpbC5jCShyZXZpc2lvbiAyMjQ0NzEpCisrKyBzeXMva2Vybi9rZXJuX2phaWwu Ywkod29ya2luZyBjb3B5KQpAQCAtMzg1OCw3ICszODU4LDggQEAKIAljYXNlIFBSSVZfVkZT X1VOTU9VTlQ6CiAJY2FzZSBQUklWX1ZGU19NT1VOVF9OT05VU0VSOgogCWNhc2UgUFJJVl9W RlNfTU9VTlRfT1dORVI6Ci0JCWlmIChjcmVkLT5jcl9wcmlzb24tPnByX2FsbG93ICYgUFJf QUxMT1dfTU9VTlQpCisJCWlmIChjcmVkLT5jcl9wcmlzb24tPnByX2FsbG93ICYgUFJfQUxM T1dfTU9VTlQgJiYKKwkJCWNyZWQtPmNyX3ByaXNvbi0+cHJfZW5mb3JjZV9zdGF0ZnMgIT0g MikKIAkJCXJldHVybiAoMCk7CiAJCWVsc2UKIAkJCXJldHVybiAoRVBFUk0pOwpJbmRleDog c3lzL2tlcm4vdmZzX21vdW50LmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gc3lzL2tlcm4vdmZzX21v dW50LmMJKHJldmlzaW9uIDIyNDQ3MSkKKysrIHN5cy9rZXJuL3Zmc19tb3VudC5jCSh3b3Jr aW5nIGNvcHkpCkBAIC03NDUsNyArNzQ1LDYgQEAKIHZmc19kb21vdW50X2ZpcnN0KAogCXN0 cnVjdCB0aHJlYWQgKnRkLAkJLyogQ2FsbGluZyB0aHJlYWQuICovCiAJc3RydWN0IHZmc2Nv bmYgKnZmc3AsCQkvKiBGaWxlIHN5c3RlbSB0eXBlLiAqLwotCWNoYXIgKmZzcGF0aCwJCQkv KiBNb3VudCBwYXRoLiAqLwogCXN0cnVjdCB2bm9kZSAqdnAsCQkvKiBWbm9kZSB0byBiZSBj b3ZlcmVkLiAqLwogCWludCBmc2ZsYWdzLAkJCS8qIEZsYWdzIGNvbW1vbiB0byBhbGwgZmls ZXN5c3RlbXMuICovCiAJc3RydWN0IHZmc29wdGxpc3QgKipvcHRsaXN0CS8qIE9wdGlvbnMg bG9jYWwgdG8gdGhlIGZpbGVzeXN0ZW0uICovCkBAIC03NTUsMTEgKzc1NCwyMyBAQAogCXN0 cnVjdCBtb3VudCAqbXA7CiAJc3RydWN0IHZub2RlICpuZXdkcDsKIAlpbnQgZXJyb3I7CisJ Y2hhciAqZnNwYXRoLCAqZmJ1ZjsKIAogCW10eF9hc3NlcnQoJkdpYW50LCBNQV9PV05FRCk7 CiAJQVNTRVJUX1ZPUF9FTE9DS0VEKHZwLCBfX2Z1bmNfXyk7CiAJS0FTU0VSVCgoZnNmbGFn cyAmIE1OVF9VUERBVEUpID09IDAsICgiTU5UX1VQREFURSBzaG91bGRuJ3QgYmUgaGVyZSIp KTsKIAorCS8qIENvbnN0cnVjdCBnbG9iYWwgZmlsZXN5c3RlbSBwYXRoIGZyb20gdnAgKi8K KwllcnJvciA9IHZuX2Z1bGxwYXRoX2dsb2JhbCh0ZCwgdnAsICZmc3BhdGgsICZmYnVmKTsK KwlpZiAoZXJyb3IgPT0gMCAmJiBzdHJsZW4oZnNwYXRoKSA+PSBNTkFNRUxFTikKKwkJZXJy b3IgPSBFTkFNRVRPT0xPTkc7CisJaWYgKGVycm9yICE9IDApIHsKKwkJdnB1dCh2cCk7CisJ CWlmIChmYnVmICE9IE5VTEwpCisJCQlmcmVlKGZidWYsIE1fVEVNUCk7CisJCXJldHVybihl cnJvcik7CisJfQorCiAJLyoKIAkgKiBJZiB0aGUgdXNlciBpcyBub3Qgcm9vdCwgZW5zdXJl IHRoYXQgdGhleSBvd24gdGhlIGRpcmVjdG9yeQogCSAqIG9udG8gd2hpY2ggd2UgYXJlIGF0 dGVtcHRpbmcgdG8gbW91bnQuCkBAIC03ODEsMTIgKzc5MiwxNCBAQAogCX0KIAlpZiAoZXJy b3IgIT0gMCkgewogCQl2cHV0KHZwKTsKKwkJZnJlZShmYnVmLCBNX1RFTVApOwogCQlyZXR1 cm4gKGVycm9yKTsKIAl9CiAJVk9QX1VOTE9DSyh2cCwgMCk7CiAKIAkvKiBBbGxvY2F0ZSBh bmQgaW5pdGlhbGl6ZSB0aGUgZmlsZXN5c3RlbS4gKi8KIAltcCA9IHZmc19tb3VudF9hbGxv Yyh2cCwgdmZzcCwgZnNwYXRoLCB0ZC0+dGRfdWNyZWQpOworCWZyZWUoZmJ1ZiwgTV9URU1Q KTsKIAkvKiBYWFhNQUM6IHBhc3MgdG8gdmZzX21vdW50X2FsbG9jPyAqLwogCW1wLT5tbnRf b3B0bmV3ID0gKm9wdGxpc3Q7CiAJLyogU2V0IHRoZSBtb3VudCBsZXZlbCBmbGFncy4gKi8K QEAgLTEwNzAsNyArMTA4Myw3IEBACiAJTkRGUkVFKCZuZCwgTkRGX09OTFlfUE5CVUYpOwog CXZwID0gbmQubmlfdnA7CiAJaWYgKChmc2ZsYWdzICYgTU5UX1VQREFURSkgPT0gMCkgewot CQllcnJvciA9IHZmc19kb21vdW50X2ZpcnN0KHRkLCB2ZnNwLCBmc3BhdGgsIHZwLCBmc2Zs YWdzLAorCQllcnJvciA9IHZmc19kb21vdW50X2ZpcnN0KHRkLCB2ZnNwLCB2cCwgZnNmbGFn cywKIAkJICAgIG9wdGxpc3QpOwogCX0gZWxzZSB7CiAJCWVycm9yID0gdmZzX2RvbW91bnRf dXBkYXRlKHRkLCB2cCwgZnNmbGFncywgb3B0bGlzdCk7CkBAIC0xMTA1LDcgKzExMTgsNyBA QAogCX0gKi8gKnVhcDsKIHsKIAlzdHJ1Y3QgbW91bnQgKm1wOwotCWNoYXIgKnBhdGhidWY7 CisJY2hhciAqcGF0aGJ1ZiwgKnJwYXRoYnVmOwogCWludCBlcnJvciwgaWQwLCBpZDE7CiAK IAlBVURJVF9BUkdfVkFMVUUodWFwLT5mbGFncyk7CkBAIC0xMTQwLDEyICsxMTUzLDI3IEBA CiAJCW10eF91bmxvY2soJm1vdW50bGlzdF9tdHgpOwogCX0gZWxzZSB7CiAJCUFVRElUX0FS R19VUEFUSDEodGQsIHBhdGhidWYpOworCQkvKgorCQkgKiBJZiB3ZSBhcmUgamFpbGVkIGFu ZCBlbmZvcmNlX3N0YXRmcz0xCisJCSAqIGNvbnN0cnVjdCByZWFsIGZpbGVzeXN0ZW0gcGF0 aAorCQkgKi8KKwkJcnBhdGhidWYgPSBtYWxsb2MoTU5BTUVMRU4sIE1fVEVNUCwgTV9XQUlU T0spOworCQlpZiAoamFpbGVkKHRkLT50ZF91Y3JlZCkgJiYKKwkJICAgIHRkLT50ZF91Y3Jl ZC0+Y3JfcHJpc29uLT5wcl9lbmZvcmNlX3N0YXRmcyA9PSAxICYmCisJCSAgICBzdHJjbXAo dGQtPnRkX3VjcmVkLT5jcl9wcmlzb24tPnByX3BhdGgsICIvIikgIT0gMCkgeworCQkJc3Ry bGNweShycGF0aGJ1ZiwgdGQtPnRkX3VjcmVkLT5jcl9wcmlzb24tPnByX3BhdGgsCisJCQkg ICAgTU5BTUVMRU4pOworCQkJc3RybGNhdChycGF0aGJ1ZiwgcGF0aGJ1ZiwgTU5BTUVMRU4p OworCQl9IGVsc2UgeworCQkJc3RybGNweShycGF0aGJ1ZiwgcGF0aGJ1ZiwgTU5BTUVMRU4p OworCQl9CiAJCW10eF9sb2NrKCZtb3VudGxpc3RfbXR4KTsKIAkJVEFJTFFfRk9SRUFDSF9S RVZFUlNFKG1wLCAmbW91bnRsaXN0LCBtbnRsaXN0LCBtbnRfbGlzdCkgewotCQkJaWYgKHN0 cmNtcChtcC0+bW50X3N0YXQuZl9tbnRvbm5hbWUsIHBhdGhidWYpID09IDApCisJCQlpZiAo c3RyY21wKG1wLT5tbnRfc3RhdC5mX21udG9ubmFtZSwgcnBhdGhidWYpID09IDApCiAJCQkJ YnJlYWs7CiAJCX0KIAkJbXR4X3VubG9jaygmbW91bnRsaXN0X210eCk7CisJCWZyZWUocnBh dGhidWYsIE1fVEVNUCk7CiAJfQogCWZyZWUocGF0aGJ1ZiwgTV9URU1QKTsKIAlpZiAobXAg PT0gTlVMTCkgewo= --------------030307010502070904020200-- From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 20:53:22 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35286106564A; Fri, 29 Jul 2011 20:53:22 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5FA0B8FC14; Fri, 29 Jul 2011 20:53:21 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id A9F2115CF76; Fri, 29 Jul 2011 22:53:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id sdDmL4i3Ws4A; Fri, 29 Jul 2011 22:53:18 +0200 (CEST) Received: from [10.9.8.3] (chello085216231078.chello.sk [85.216.231.78]) by mail.vx.sk (Postfix) with ESMTPSA id CB70015CF68; Fri, 29 Jul 2011 22:53:17 +0200 (CEST) Message-ID: <4E331DC1.5000108@FreeBSD.org> Date: Fri, 29 Jul 2011 22:53:21 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Jamie Gritton References: <4E316E19.9040309@FreeBSD.org> <4E318D75.608@FreeBSD.org> <4E31A3CD.60500@FreeBSD.org> <4E31AEC6.8080106@FreeBSD.org> In-Reply-To: <4E31AEC6.8080106@FreeBSD.org> X-Enigmail-Version: 1.2 Content-Type: multipart/mixed; boundary="------------090000000605080708000202" Cc: FreeBSD Current Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Jul 2011 20:53:22 -0000 This is a multi-part message in MIME format. --------------090000000605080708000202 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit So what do you think about this updated patch (attached)? Here we leave everything possible for jail_example_params. Btw. you can also set jid=xxx in params to have a "static" jail id for this jail. Also stopping a persistent jail doesn't delete it (but you cannot start it again). Dňa 28. 7. 2011 20:47, Jamie Gritton wrote / napísal(a): > Yes, it was intentional to move away from the global sysctls and to > the per-jail parameters instead. It makes more sense once config > files come into play, which can do a better job of providing global > defaults as well as per-jail parameters. > > The connection between ZFS and persist makes sense. So for ZFS-based > jail you'd want to set (and then reset) persist. For others, this > could be left to the user. The changes to jail(8) for config files > also sets persist when creating jails, and then clears it at a later > stage unless the user specifies to keep it set. It looks like I might > want to add some ZFS support to the new jail(8). > > I would prefer to keep things simpler regarding create/start and > remove/stop, and keep them tied together. > > - Jamie > > > On 07/28/11 12:00, Martin Matuska wrote: >> If you start jail(8) witth "-c" (the new "param" way,) the values of the >> actual security.jail. variables are not initialized inside the jail, >> default values are used instead. I don't know if this is intentional, >> but probably yes. Default enforce_statfs=2, allow.mount=0. >> As of me we can leave everything for ${_params}, but then ${_zfs} makes >> sense only if enforce_statfs<2 and allow.mount=1. >> >> Regarding zfs, if you want to operate zfs from the very start of a jail >> (and e.g. make use of /etc/rc.d/zfs which has jail support), you have to >> pair datasets with an existing jail. In simple words, you have to create >> a process-less jail (persist=1), attach zfs datasets and then run the >> command. The persist option can be made optional - but we always start >> with persist=1, then we can set (or not) persist=0 depending on user >> setting. >> >> The question that opens, should we remove a persisting jail on "stop"? >> Or should we support new commands "create" and "remove" in addition to >> "start" and "stop"? Create would just make a processless jail, remove >> would wipe out a jail and start/stop would just deal with the processes >> (if persist=0 the old way, of course)? >> >> Cheers, >> mm >> >> Dňa 28. 7. 2011 18:25, Jamie Gritton wrote / napísal(a): >>> Since I missed the 9.0 boat with jail config file capability, something >>> like this seems necessary; rc.d/jail has long been unable to handle the >>> full scale of what jail(8) can do. >>> >>> I gather that setting persist is necessary for the ZFS operation. As >>> long as we're making the parameter setting more generic from rc, we >>> should handle the case where persist is specified in ${_params}, and >>> not >>> always set/reset it around the jail creation unless ZFS is used. >>> >>> Also, why the specific inclusion of the security-related parameters? >>> They could just be folded into ${_params}, and if left unspecified then >>> jail(8) should by default do the right thing. >>> >>> - Jamie >>> >>> >>> On 07/28/11 08:11, Martin Matuska wrote: >>>> The attached patch allows better fine-tuning of jails started via >>>> /etc/rc.d, uses the new jail(8) flags (-c -m), the persist >>>> parameter and >>>> adds ZFS support. >>>> Patch is fully backward compatible. >>>> >>>> Please review, comment and/or test my attached patch. >>>> >>>> Cheers, >>>> mm -- Martin Matuska FreeBSD committer http://blog.vx.sk --------------090000000605080708000202 Content-Type: text/plain; name="etc_jail.2.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="etc_jail.2.patch" SW5kZXg6IGV0Yy9yYy5kL2phaWwKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQotLS0gZXRjL3JjLmQvamFpbAko cmV2aXNpb24gMjI0NDk0KQorKysgZXRjL3JjLmQvamFpbAkod29ya2luZyBjb3B5KQpAQCAt NDMsNiArNDMsOSBAQAogCWV2YWwgX2lwPVwiXCRqYWlsXyR7X2p9X2lwXCIKIAlldmFsIF9p bnRlcmZhY2U9XCJcJHtqYWlsXyR7X2p9X2ludGVyZmFjZTotJHtqYWlsX2ludGVyZmFjZX19 XCIKIAlldmFsIF9leGVjPVwiXCRqYWlsXyR7X2p9X2V4ZWNcIgorCWV2YWwgX3BhcmFtcz1c IlwkamFpbF8ke19qfV9wYXJhbXNcIgorCWV2YWwgX3BlcnNpc3Q9XCJcJGphaWxfJHtfan1f cGVyc2lzdFwiCisJZXZhbCBfemZzPVwiXCR7amFpbF8ke19qfV96ZnM6LX1cIgogCiAJaT0w CiAJd2hpbGUgOiA7IGRvCkBAIC05OCw2ICsxMDEsOSBAQAogCWZpCiAKIAkjIFRoZSBkZWZh dWx0IGphaWwgcnVsZXNldCB3aWxsIGJlIHVzZWQgYnkgcmMuc3ViciBpZiBub25lIGlzIHNw ZWNpZmllZC4KKwlpZiBbIC1uICJqYWlsX2RldmZzX3J1bGVzZXQiIC1hIC1uICJfemZzIiBd OyB0aGVuCisJCWphaWxfZGV2ZnNfcnVsZXNldD0iZGV2ZnNydWxlc19qYWlsX3pmcyIKKwlm aQogCWV2YWwgX3J1bGVzZXQ9XCJcJHtqYWlsXyR7X2p9X2RldmZzX3J1bGVzZXQ6LSR7amFp bF9kZXZmc19ydWxlc2V0fX1cIgogCWV2YWwgX2RldmZzPVwiXCR7amFpbF8ke19qfV9kZXZm c19lbmFibGU6LSR7amFpbF9kZXZmc19lbmFibGV9fVwiCiAJWyAteiAiJHtfZGV2ZnN9IiBd ICYmIF9kZXZmcz0iTk8iCkBAIC0zNDUsNiArMzUxLDM2IEBACiAJbW91bnQgLWEgLUYgIiR7 X2ZzdGFifSIKIH0KIAorIyBqYWlsX3pmc19qYWlsaW4KKyMJTWFrZSB6ZnMgZGF0YXNldHMg bWFuYWdlYWJsZSBmcm9tIGluc2lkZSBhIGphaWwKKyMJdGhlICJqYWlsZWQiIGRhdGFzZXQg cHJvcGVydHkgbXVzdCBiZSBzZXQgdG8gIm9uIgoramFpbF96ZnNfamFpbGluKCkKK3sKKwlp ZiBbIC1uICIke196ZnN9IiBdOyB0aGVuCisJCWZvciBfZHMgaW4gJHtfemZzfTsgZG8KKwkJ CV9qYWlsZWQ9YHpmcyBnZXQgLUggamFpbGVkICR7X2RzfSAyPi9kZXYvbnVsbCB8IGF3ayAn eyBwcmludCAkMyB9J2AKKwkJCWlmIFsgIiRfamFpbGVkIiA9ICJvbiIgXTsgdGhlbgorCQkJ CXpmcyBqYWlsICIke19qYWlsX2lkfSIgJHtfZHN9IDI+L2Rldi9udWxsCisJCQlmaQorCQlk b25lCisJZmkKK30KKworIyBqYWlsX3pmc19qYWlsb3V0CisjCVVuamFpbCB6ZnMgZGF0YXNl dHMKKyMJdGhlICJqYWlsZWQiIGRhdGFzZXQgcHJvcGVydHkgbXVzdCBiZSBzZXQgdG8gIm9u IgoramFpbF96ZnNfamFpbG91dCgpCit7CisJaWYgWyAtbiAiJHtfemZzfSIgXTsgdGhlbgor CQlmb3IgX2RzIGluICR7X3pmc307IGRvCisJCQlfamFpbGVkPWB6ZnMgZ2V0IC1IIGphaWxl ZCAke19kc30gMj4vZGV2L251bGwgfCBhd2sgJ3sgcHJpbnQgJDMgfSdgCisJCQlpZiBbICIk X2phaWxlZCIgPSAib24iIF07IHRoZW4KKwkJCQl6ZnMgdW5qYWlsICIke19qYWlsX2lkfSIg JHtfZHN9IDI+L2Rldi9udWxsCisJCQlmaQorCQlkb25lCisJZmkKK30KKwogIyBqYWlsX3No b3dfYWRkcmVzc2VzIGphaWwKICMJRGVidWcgcHJpbnQgdGhlIGlucHV0IGZvciB0aGUgZ2l2 ZW4gX211bHRpIGFsaWFzZXMKICMJZm9yIGEgamFpbCBmb3IgaW5pdF92YXJpYWJsZXMoKS4K QEAgLTQ4MywxMCArNTE5LDI3IEBACiAJCSopCTs7CiAJCWVzYWMKIAotCQkjIEFwcGVuZCBh ZGRyZXNzIHRvIGxpc3Qgb2YgYWRkcmVzc2VzIGZvciB0aGUgamFpbCBjb21tYW5kLgotCQlj YXNlICIke19hZGRybH0iIGluCi0JCSIiKQlfYWRkcmw9IiR7X2FkZHJ9IiA7OwotCQkqKQlf YWRkcmw9IiR7X2FkZHJsfSwke19hZGRyfSIgOzsKKwkJY2FzZSAiJHtfdHlwZX0iIGluCisJ CWluZXQpCisJCQkjIEFwcGVuZCBhZGRyZXNzIHRvIGxpc3Qgb2YgaXB2NCBhZGRyZXNzZXMg Zm9yIHRoZQorCQkJIyBqYWlsIGNvbW1hbmQuCisJCQljYXNlICIke19hZGRybH0iIGluCisJ CQkiIikJX2FkZHJsPSIke19hZGRyfSIgOzsKKwkJCSopCV9hZGRybD0iJHtfYWRkcmx9LCR7 X2FkZHJ9IiA7OworCQkJZXNhYworCQkJOzsKKwkJaW5ldDYpCisJCQkjIEFwcGVuZCBhZGRy ZXNzIHRvIGxpc3Qgb2YgaXB2NiBhZGRyZXNzZXMgZm9yIHRoZQorCQkJIyBqYWlsIGNvbW1h bmQuCisJCQljYXNlICIke19hZGRybDZ9IiBpbgorCQkJIiIpCV9hZGRybDY9IiR7X2FkZHJ9 IiA7OworCQkJKikJX2FkZHJsNj0iJHtfYWRkcmw2fSwke19hZGRyfSIgOzsKKwkJCWVzYWMK KwkJCTs7CisJCSopCXdhcm4gIkNvdWxkIG5vdCBkZXRlcm1pbmUgYWRkcmVzcyBmYW1pbHku ICBOb3QgZ29pbmciIFwKKwkJCSAgICAidG8gc2V0IGFkZHJlc3MgJyR7X2FkZHJ9JyBmb3Ig JHtfamFpbH0uIgorCQkJY29udGludWUKKwkJCTs7CiAJCWVzYWMKIAogCQkjIENvbmZpZ3Vy ZSBpbnRlcmZhY2UgYWxpYXMgaWYgcmVxdWVzdGVkIGJ5IGEgZ2l2ZW4gaW50ZXJmYWNlCkBA IC00OTQsMTQgKzU0Nyw3IEBACiAJCWNhc2UgIiR7X2lmYWNlfSIgaW4KIAkJIiIpCWNvbnRp bnVlIDs7CiAJCWVzYWMKLQkJY2FzZSAiJHtfdHlwZX0iIGluCi0JCWluZXQpCTs7Ci0JCWlu ZXQ2KQk7OwotCQkqKQl3YXJuICJDb3VsZCBub3QgZGV0ZXJtaW5lIGFkZHJlc3MgZmFtaWx5 LiAgTm90IGdvaW5nIiBcCi0JCQkgICAgInRvICR7X2FjdGlvbn0gYWRkcmVzcyAnJHtfYWRk cn0nIGZvciAke19qYWlsfS4iCi0JCQljb250aW51ZQotCQkJOzsKLQkJZXNhYworCiAJCWNh c2UgIiR7X2FjdGlvbn0iIGluCiAJCWFkZCkJaWZjb25maWcgJHtfaWZhY2V9ICR7X3R5cGV9 ICR7X2FkZHJ9JHtfbWFza30gYWxpYXMKIAkJCTs7CkBAIC01NzYsNiArNjIyLDcgQEAKIAkJ CWNvbnRpbnVlOwogCQlmaQogCQlfYWRkcmw9IiIKKwkJX2FkZHJsNj0iIgogCQlqYWlsX2lw cyAiYWRkIgogCQlpZiBbIC1uICIke19maWJ9IiBdOyB0aGVuCiAJCQlfc2V0ZmliPSJzZXRm aWIgLUYgJyR7X2ZpYn0nIgpAQCAtNjQ0LDQyICs2OTEsNTYgQEAKIAkJCWk9JCgoaSArIDEp KQogCQlkb25lCiAKLQkJZXZhbCAke19zZXRmaWJ9IGphaWwgJHtfZmxhZ3N9IC1pICR7X3Jv b3RkaXJ9ICR7X2hvc3RuYW1lfSBcCi0JCQlcIiR7X2FkZHJsfVwiICR7X2V4ZWNfc3RhcnR9 ID4gJHtfdG1wX2phaWx9IDI+JjEgXAotCQkJPC9kZXYvbnVsbAorCQlfamFpbF9pZD1gJHtf c2V0ZmlifSBqYWlsIC1pICR7X2ZsYWdzfSAtYyBcCisJCQlwYXRoPSIke19yb290ZGlyfSIg XAorCQkJaG9zdC5ob3N0bmFtZT0iJHtfaG9zdG5hbWV9IiBcCisJCQlpcDQuYWRkcj0iJHtf YWRkcmx9IiBcCisJCQlpcDYuYWRkcj0iJHtfYWRkcmw2fSIgXAorCQkJJHtfcGFyYW1zfSBc CisJCQlwZXJzaXN0PTFgCiAKLQkJaWYgWyAiJD8iIC1lcSAwIF0gOyB0aGVuCi0JCQlfamFp bF9pZD0kKGhlYWQgLTEgJHtfdG1wX2phaWx9KQotCQkJaT0xCi0JCQl3aGlsZSA6IDsgZG8K LQkJCQlldmFsIG91dD1cIlwke19leGVjX2FmdGVyc3RhcnQke2l9Oi0nJ31cIgotCi0JCQkJ aWYgWyAteiAiJG91dCIgXTsgdGhlbgotCQkJCQlicmVhazsKKwkJaWYgWyAtbiAiJF9qYWls X2lkIiBdOyB0aGVuCisJCQlqYWlsX3pmc19qYWlsaW4KKwkJCWV2YWwgamFpbCAke19mbGFn c30gLW0gamlkPSIke19qYWlsX2lkfSIgXAorCQkJICAgIGNvbW1hbmQ9IiR7X2V4ZWNfc3Rh cnR9IiA+ICR7X3RtcF9qYWlsfSAyPiYxIFwKKwkJCSAgICA8L2Rldi9udWxsCisJCQlpZiBb ICIkPyIgLWVxIDAgXSA7IHRoZW4KKwkJCQlpZiBbICIke19wZXJzaXN0fSIgIT0gIjEiIF07 IHRoZW4KKwkJCQkJamFpbCAtbSBqaWQ9IiR7X2phaWxfaWR9IiBwZXJzaXN0PTAKIAkJCQlm aQorCQkJCWk9MQorCQkJCXdoaWxlIDogOyBkbworCQkJCQlldmFsIG91dD1cIlwke19leGVj X2FmdGVyc3RhcnQke2l9Oi0nJ31cIgogCi0JCQkJamV4ZWMgIiR7X2phaWxfaWR9IiAke291 dH0KLQkJCQlpPSQoKGkgKyAxKSkKLQkJCWRvbmUKKwkJCQkJaWYgWyAteiAiJG91dCIgXTsg dGhlbgorCQkJCQkJYnJlYWs7CisJCQkJCWZpCiAKLQkJCWVjaG8gLW4gIiAkX2hvc3RuYW1l IgotCQkJdGFpbCArMiAke190bXBfamFpbH0gPiR7X2NvbnNvbGVsb2d9Ci0JCQllY2hvICR7 X2phaWxfaWR9ID4gL3Zhci9ydW4vamFpbF8ke19qYWlsfS5pZAorCQkJCQlqZXhlYyAiJHtf amFpbF9pZH0iICR7b3V0fQorCQkJCQlpPSQoKGkgKyAxKSkKKwkJCQlkb25lCiAKLQkJCWk9 MAotCQkJd2hpbGUgOiA7IGRvCi0JCQkJZXZhbCBvdXQ9XCJcJHtfZXhlY19wb3N0c3RhcnQk e2l9Oi0nJ31cIgotCQkJCVsgLXogIiRvdXQiIF0gJiYgYnJlYWsKLQkJCQkke291dH0KLQkJ CQlpPSQoKGkgKyAxKSkKLQkJCWRvbmUKLQkJZWxzZQotCQkJamFpbF91bW91bnRfZnMKLQkJ CWphaWxfaXBzICJkZWwiCi0JCQllY2hvICIgY2Fubm90IHN0YXJ0IGphaWwgXCIke19qYWls fVwiOiAiCi0JCQl0YWlsICsyICR7X3RtcF9qYWlsfQorCQkJCWVjaG8gLW4gIiAkX2hvc3Ru YW1lIgorCQkJCXRhaWwgKzIgJHtfdG1wX2phaWx9ID4ke19jb25zb2xlbG9nfQorCQkJCWVj aG8gJHtfamFpbF9pZH0gPiAvdmFyL3J1bi9qYWlsXyR7X2phaWx9LmlkCisKKwkJCQlpPTAK KwkJCQl3aGlsZSA6IDsgZG8KKwkJCQkJZXZhbCBvdXQ9XCJcJHtfZXhlY19wb3N0c3RhcnQk e2l9Oi0nJ31cIgorCQkJCQlbIC16ICIkb3V0IiBdICYmIGJyZWFrCisJCQkJCSR7b3V0fQor CQkJCQlpPSQoKGkgKyAxKSkKKwkJCQlkb25lCisJCQllbHNlCisJCQkJamFpbF96ZnNfamFp bG91dAorCQkJCWphaWwgLW0gamlkPSIke19qYWlsX2lkfSIgcGVyc2lzdD0wCisJCQkJamFp bF91bW91bnRfZnMKKwkJCQlqYWlsX2lwcyAiZGVsIgorCQkJCWVjaG8gIiBjYW5ub3Qgc3Rh cnQgamFpbCBcIiR7X2phaWx9XCI6ICIKKwkJCQl0YWlsICsyICR7X3RtcF9qYWlsfQorCQkJ ZmkKKwkJCXJtIC1mICR7X3RtcF9qYWlsfQogCQlmaQotCQlybSAtZiAke190bXBfamFpbH0K IAlkb25lCiAJcm1kaXIgJHtfdG1wX2Rpcn0KIAllY2hvICcuJwpAQCAtNzA3LDYgKzc2OCw3 IEBACiAJCQkJCWV2YWwgZW52IC1pIC91c3Ivc2Jpbi9qZXhlYyAke19qYWlsX2lkfSAke19l eGVjX3N0b3B9IFwKIAkJCQkJCT4+ICR7X2NvbnNvbGVsb2d9IDI+JjEKIAkJCQlmaQorCQkJ CWphaWxfemZzX2phaWxvdXQKIAkJCQlraWxsYWxsIC1qICR7X2phaWxfaWR9IC1URVJNID4g L2Rldi9udWxsIDI+JjEKIAkJCQlzbGVlcCAxCiAJCQkJa2lsbGFsbCAtaiAke19qYWlsX2lk fSAtS0lMTCA+IC9kZXYvbnVsbCAyPiYxCkluZGV4OiBldGMvZGVmYXVsdHMvZGV2ZnMucnVs ZXMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PQotLS0gZXRjL2RlZmF1bHRzL2RldmZzLnJ1bGVzCShyZXZpc2lv biAyMjQ0NzEpCisrKyBldGMvZGVmYXVsdHMvZGV2ZnMucnVsZXMJKHdvcmtpbmcgY29weSkK QEAgLTgzLDMgKzgzLDkgQEAKIGFkZCBpbmNsdWRlICRkZXZmc3J1bGVzX2hpZGVfYWxsCiBh ZGQgaW5jbHVkZSAkZGV2ZnNydWxlc191bmhpZGVfYmFzaWMKIGFkZCBpbmNsdWRlICRkZXZm c3J1bGVzX3VuaGlkZV9sb2dpbgorCisjIEphaWwgd2l0aCB6ZnMgc3VwcG9ydAorIworW2Rl dmZzcnVsZXNfamFpbF96ZnM9NV0KK2FkZCBpbmNsdWRlICRkZXZmc3J1bGVzX2phaWwKK2Fk ZCBwYXRoIHpmcyB1bmhpZGUKSW5kZXg6IGV0Yy9kZWZhdWx0cy9yYy5jb25mCj09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT0KLS0tIGV0Yy9kZWZhdWx0cy9yYy5jb25mCShyZXZpc2lvbiAyMjQ0NzEpCisrKyBl dGMvZGVmYXVsdHMvcmMuY29uZgkod29ya2luZyBjb3B5KQpAQCAtNjk1LDYgKzY5NSwxNSBA QAogI2phaWxfZXhhbXBsZV9tb3VudF9lbmFibGU9Ik5PIgkJCSMgbW91bnQvdW1vdW50IGph aWwncyBmcwogI2phaWxfZXhhbXBsZV9mc3RhYj0iIgkJCQkjIGZzdGFiKDUpIGZvciBtb3Vu dC91bW91bnQKICNqYWlsX2V4YW1wbGVfZmxhZ3M9Ii1sIC1VIHJvb3QiCQkjIGZsYWdzIGZv ciBqYWlsKDgpCisjamFpbF9leGFtcGxlX3BlcnNpc3Q9IiIJCQkjIFNldCB0byAxIHRvIGNy ZWF0ZSBhIHBlcnNpc3RlbnQgamFpbAorI2phaWxfZXhhbXBsZV9wYXJhbXM9IiIJCQkJIyBT cGFjZS1zZXBhcmF0ZWQgbGlzdCBvZiBhZGRpdGlvbmFsCisJCQkJCQkjIHVzZXItc3VwcGxp ZWQgcGFyYW1ldGVycyBmb3IgamFpbCg4KQorI2phaWxfZXhhbXBsZV96ZnM9IiIJCQkJIyBT cGFjZS1zZXBhcmF0ZWQgbGlzdCBvZiBaRlMgZGF0YXNldHMgdG8gYmUKKwkJCQkJCSMgbWFu YWdlZCBmcm9tIHRoaXMgamFpbC4gRm9yIHByb3BlciBvcGVyYXRpb24sCisJCQkJCQkjIGFs bG93Lm1vdW50PTEgYW5kIGVuZm9yY2Vfc3RhdGZzPTEgKG9yIDApCisJCQkJCQkjIG11c3Qg YmUgYWRkZWQgdG8gamFpbF9leGFtcGxlX3BhcmFtcy4KKwkJCQkJCSMgVGhlICJqYWlsZWQi IHByb3BlcnR5IG11c3QgYmUgc2V0IHRvICJvbiIKKwkJCQkJCSMgb24gZGVzaXJlZCBkYXRh c2V0cyBiZWZvcmUgc3RhcnRpbmcgdGhlIGphaWwuCiAKICMjIyMjIyMjIyMjIyMjIyMjIyMj IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjCiAjIyMgRGVmaW5l IHNvdXJjZV9yY19jb25mcywgdGhlIG1lY2hhbmlzbSB1c2VkIGJ5IC9ldGMvcmMuKiAjIwo= --------------090000000605080708000202-- From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 06:49:56 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A121C106564A; Sat, 30 Jul 2011 06:49:56 +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 BD5C48FC0A; Sat, 30 Jul 2011 06:49:55 +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 JAA23736; Sat, 30 Jul 2011 09:49:54 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qn3Mv-0007y2-R6; Sat, 30 Jul 2011 09:49:53 +0300 Message-ID: <4E33A990.7040006@FreeBSD.org> Date: Sat, 30 Jul 2011 09:49:52 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: John Baldwin References: <4E23EE49.5040801@FreeBSD.org> <201107181308.14624.jhb@freebsd.org> <4E24B21C.3070402@FreeBSD.org> <201107191116.07116.jhb@freebsd.org> In-Reply-To: <201107191116.07116.jhb@freebsd.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: ichwd0: unable to reserve GCS registers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 06:49:56 -0000 on 19/07/2011 18:16 John Baldwin said the following: > Hmm, can you get devinfo -r output from a working kernel with ichwd loaded? > You might be able to just build the kernel with 'nooptions NEW_PCIB'. I believe that I've got a similar problem with amdsbwd(4). It needs some resources (I/O ports) that belong to ACPI. The problem is that the driver attaches to isa bus which is under isab->pci->pcib and those particular resources are not assigned to the Host-PCI bridge. I think that you already made a suggestion that perhaps isa bus should directly attach to acpi bus when acpi is available. Not sure if there are any alternative approaches. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 08:07:05 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2460106566B for ; Sat, 30 Jul 2011 08:07:05 +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 041798FC0C for ; Sat, 30 Jul 2011 08:07:04 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA24422; Sat, 30 Jul 2011 11:07:01 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Qn4ZZ-00080q-FN; Sat, 30 Jul 2011 11:07:01 +0300 Message-ID: <4E33BBA5.4030805@FreeBSD.org> Date: Sat, 30 Jul 2011 11:07:01 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110706 Thunderbird/5.0 MIME-Version: 1.0 To: Rick Macklem References: <254152988.989678.1311630244759.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <254152988.989678.1311630244759.JavaMail.root@erie.cs.uoguelph.ca> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 08:07:06 -0000 on 26/07/2011 00:44 Rick Macklem said the following: > hrs sent me this panic. I'm wondering if it might be relevant to this? To 'this' what? A panic is a panic. > spin lock 0xffffffff80cb52c0 (sched lock 1) held by 0xffffff0012c7f8c0 (tid 100317) too long > panic: spin lock held too long I guess it's more related to the thread on stable@ which has the panic message as its subject. > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at kdb_backtrace+0x37 > panic() at panic+0x187 > _mtx_lock_spin_failed() at _mtx_lock_spin_failed+0x39 > _mtx_lock_spin() at _mtx_lock_spin+0x9e > sched_add() at sched_add+0x117 > setrunnable() at setrunnable+0x78 > sleepq_signal() at sleepq_signal+0x7a > cv_signal() at cv_signal+0x3b > xprt_active() at xprt_active+0xe3 > svc_vc_soupcall() at svc_vc_soupcall+0xc > sowakeup() at sowakeup+0x69 > tcp_do_segment() at tcp_do_segment+0x2cbd > tcp_input() at tcp_input+0xcdd > ip_input() at ip_input+0xac > netisr_dispatch_src() at netisr_dispatch_src+0x7e > ether_demux() at ether_demux+0x14d > ether_input() at ether_input+0x17d > em_rxeof() at em_rxeof+0x1ca > em_handle_que() at em_handle_que+0x5b > taskqueue_run_locked() at taskqueue_run_locked+0x85 > taskqueue_thread_loop() at taskqueue_thread_loop+0x4e > fork_exit() at fork_exit+0x11f > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff8000160d00, rbp = 0 --- > KDB: enter: panic > [thread pid 0 tid 100033 ] > Stopped at kdb_enter+0x3b: movq $0,0x6b4e62(%rip) > db> ps > -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 12:34:31 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F212E106564A; Sat, 30 Jul 2011 12:34:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C90F48FC14; Sat, 30 Jul 2011 12:34:31 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7F04346B2D; Sat, 30 Jul 2011 08:34:31 -0400 (EDT) Received: from kavik.baldwin.cx (c-68-36-150-83.hsd1.nj.comcast.net [68.36.150.83]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 21DD48A02C; Sat, 30 Jul 2011 08:34:31 -0400 (EDT) From: John Baldwin To: Andriy Gapon Date: Sat, 30 Jul 2011 08:34:28 -0400 User-Agent: KMail/1.13.7 (FreeBSD/9.0-CURRENT; KDE/4.6.5; i386; ; ) References: <4E23EE49.5040801@FreeBSD.org> <201107191116.07116.jhb@freebsd.org> <4E33A990.7040006@FreeBSD.org> In-Reply-To: <4E33A990.7040006@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201107300834.29194.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Sat, 30 Jul 2011 08:34:31 -0400 (EDT) Cc: freebsd-current@freebsd.org Subject: Re: ichwd0: unable to reserve GCS registers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 12:34:32 -0000 On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote: > on 19/07/2011 18:16 John Baldwin said the following: > > Hmm, can you get devinfo -r output from a working kernel with ichwd > > loaded? You might be able to just build the kernel with 'nooptions > > NEW_PCIB'. > > I believe that I've got a similar problem with amdsbwd(4). > It needs some resources (I/O ports) that belong to ACPI. > The problem is that the driver attaches to isa bus which is under > isab->pci->pcib and those particular resources are not assigned to the > Host-PCI bridge. > > I think that you already made a suggestion that perhaps isa bus should > directly attach to acpi bus when acpi is available. Not sure if there are > any alternative approaches. Actually, my suggestion was the other way around (we should move certain ACPI devices down behind isab so they are behind the Host-PCI bridge as they are in hardware). In this case the BIOS clearly does not list the reosurces for the GCS as valid resources for the Host-PCI bridge. This is part of the reason that I added the 'debug.acpi.disable="hostres"'. One thing we may be able to do is allow non-wildcard requests that are outside the range to still pass if they are in ACPI's system resource range perhaps. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 15:30:03 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16C6D106564A for ; Sat, 30 Jul 2011 15:30:03 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id B601A8FC13 for ; Sat, 30 Jul 2011 15:30:02 +0000 (UTC) Received: from outgoing.leidinger.net (p4FC46CA8.dip.t-dialin.net [79.196.108.168]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id C1DFD844016; Sat, 30 Jul 2011 17:29:47 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.1.12]) by outgoing.leidinger.net (Postfix) with ESMTP id 1EC2420F3; Sat, 30 Jul 2011 17:29:45 +0200 (CEST) Date: Sat, 30 Jul 2011 17:29:45 +0200 From: Alexander Leidinger To: Martin Matuska Message-ID: <20110730172945.00001576@unknown> In-Reply-To: <4E316E19.9040309@FreeBSD.org> References: <4E316E19.9040309@FreeBSD.org> X-Mailer: Claws Mail 3.7.8cvs47 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: C1DFD844016.A1D5E X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1312644589.49982@qqdmFE1Qlq5RhKpPLtN6yQ X-EBL-Spam-Status: No Cc: freebsd-current@FreeBSD.org Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 15:30:03 -0000 On Thu, 28 Jul 2011 16:11:37 +0200 Martin Matuska wrote: > The attached patch allows better fine-tuning of jails started via > /etc/rc.d, uses the new jail(8) flags (-c -m), the persist parameter > and adds ZFS support. > Patch is fully backward compatible. > > Please review, comment and/or test my attached patch. Can you please have a look at the jail part of http://www.leidinger.net/FreeBSD/current-patches/etc:rc.d.diff and take some parts which you didn't take care about (jailname/securelevel/correctness check for fstab entries)? Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 22:32:22 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A691E106566B; Sat, 30 Jul 2011 22:32:22 +0000 (UTC) (envelope-from jamie@FreeBSD.org) Received: from m2.gritton.org (gritton.org [64.34.175.71]) by mx1.freebsd.org (Postfix) with ESMTP id 5C8F28FC0C; Sat, 30 Jul 2011 22:32:21 +0000 (UTC) Received: from glorfindel.gritton.org (c-174-52-133-59.hsd1.ut.comcast.net [174.52.133.59]) (authenticated bits=0) by m2.gritton.org (8.14.4/8.14.4) with ESMTP id p6UMWKRA056335; Sat, 30 Jul 2011 16:32:21 -0600 (MDT) (envelope-from jamie@FreeBSD.org) Message-ID: <4E348673.6080406@FreeBSD.org> Date: Sat, 30 Jul 2011 16:32:19 -0600 From: Jamie Gritton User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101110 Thunderbird/3.1.6 MIME-Version: 1.0 To: FreeBSD Current References: <4E316E19.9040309@FreeBSD.org> <4E318D75.608@FreeBSD.org> <4E31A3CD.60500@FreeBSD.org> <4E31AEC6.8080106@FreeBSD.org> <4E331DC1.5000108@FreeBSD.org> In-Reply-To: <4E331DC1.5000108@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Martin Matuska Subject: Re: [PATCH] updated /etc/rc.d/jail and added ZFS support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 22:32:22 -0000 Yes, that looks good. It keeps what I'd call expected behavior for persist (at least on the startup side). - Jamie On 07/29/11 14:53, Martin Matuska wrote: > So what do you think about this updated patch (attached)? > Here we leave everything possible for jail_example_params. > Btw. you can also set jid=xxx in params to have a "static" jail id for > this jail. > > Also stopping a persistent jail doesn't delete it (but you cannot start > it again). > > Dňa 28. 7. 2011 20:47, Jamie Gritton wrote / napísal(a): >> Yes, it was intentional to move away from the global sysctls and to >> the per-jail parameters instead. It makes more sense once config >> files come into play, which can do a better job of providing global >> defaults as well as per-jail parameters. >> >> The connection between ZFS and persist makes sense. So for ZFS-based >> jail you'd want to set (and then reset) persist. For others, this >> could be left to the user. The changes to jail(8) for config files >> also sets persist when creating jails, and then clears it at a later >> stage unless the user specifies to keep it set. It looks like I might >> want to add some ZFS support to the new jail(8). >> >> I would prefer to keep things simpler regarding create/start and >> remove/stop, and keep them tied together. >> >> - Jamie >> >> >> On 07/28/11 12:00, Martin Matuska wrote: >>> If you start jail(8) witth "-c" (the new "param" way,) the values of the >>> actual security.jail. variables are not initialized inside the jail, >>> default values are used instead. I don't know if this is intentional, >>> but probably yes. Default enforce_statfs=2, allow.mount=0. >>> As of me we can leave everything for ${_params}, but then ${_zfs} makes >>> sense only if enforce_statfs<2 and allow.mount=1. >>> >>> Regarding zfs, if you want to operate zfs from the very start of a jail >>> (and e.g. make use of /etc/rc.d/zfs which has jail support), you have to >>> pair datasets with an existing jail. In simple words, you have to create >>> a process-less jail (persist=1), attach zfs datasets and then run the >>> command. The persist option can be made optional - but we always start >>> with persist=1, then we can set (or not) persist=0 depending on user >>> setting. >>> >>> The question that opens, should we remove a persisting jail on "stop"? >>> Or should we support new commands "create" and "remove" in addition to >>> "start" and "stop"? Create would just make a processless jail, remove >>> would wipe out a jail and start/stop would just deal with the processes >>> (if persist=0 the old way, of course)? >>> >>> Cheers, >>> mm >>> >>> Dňa 28. 7. 2011 18:25, Jamie Gritton wrote / napísal(a): >>>> Since I missed the 9.0 boat with jail config file capability, something >>>> like this seems necessary; rc.d/jail has long been unable to handle the >>>> full scale of what jail(8) can do. >>>> >>>> I gather that setting persist is necessary for the ZFS operation. As >>>> long as we're making the parameter setting more generic from rc, we >>>> should handle the case where persist is specified in ${_params}, and >>>> not >>>> always set/reset it around the jail creation unless ZFS is used. >>>> >>>> Also, why the specific inclusion of the security-related parameters? >>>> They could just be folded into ${_params}, and if left unspecified then >>>> jail(8) should by default do the right thing. >>>> >>>> - Jamie >>>> >>>> >>>> On 07/28/11 08:11, Martin Matuska wrote: >>>>> The attached patch allows better fine-tuning of jails started via >>>>> /etc/rc.d, uses the new jail(8) flags (-c -m), the persist >>>>> parameter and >>>>> adds ZFS support. >>>>> Patch is fully backward compatible. >>>>> >>>>> Please review, comment and/or test my attached patch. >>>>> >>>>> Cheers, >>>>> mm > > From owner-freebsd-current@FreeBSD.ORG Sat Jul 30 22:55:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47B24106566C; Sat, 30 Jul 2011 22:55:20 +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 E01588FC13; Sat, 30 Jul 2011 22:55:19 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEALiKNE6DaFvO/2dsb2JhbABBhEekFIFAAQEBAQIBAQEBIAQnIAsFFg4KAgINGQIpAQkmBggHBAEcBIdLBK5FkBmBK4QHgRAEkG+CDJEA X-IronPort-AV: E=Sophos;i="4.67,292,1309752000"; d="scan'208";a="132868065" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 30 Jul 2011 18:55:18 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9F376B3F0F; Sat, 30 Jul 2011 18:55:18 -0400 (EDT) Date: Sat, 30 Jul 2011 18:55:18 -0400 (EDT) From: Rick Macklem To: Andriy Gapon Message-ID: <557218859.1217065.1312066518634.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4E33BBA5.4030805@FreeBSD.org> 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 Subject: Re: Heavy I/O blocks FreeBSD box for several seconds X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 22:55:20 -0000 Andriv Gapon wrote: > on 26/07/2011 00:44 Rick Macklem said the following: > > hrs sent me this panic. I'm wondering if it might be relevant to > > this? > > To 'this' what? Well, my thinking was (and it is quite likely completely incorrect) is that, since this panic is a result of holding the spin lock too long, that it might be another symptom of the same problem as when the scheduler seems to "lock up" for several seconds. --> The bug might be some case where the spin lock isn't being released when it should be, and that "could" result in "Heavy I/O blocks FreeBSD box for several seconds". Note that the server was under heavy I/O load when this panic occurred. > A panic is a panic. > > > spin lock 0xffffffff80cb52c0 (sched lock 1) held by > > 0xffffff0012c7f8c0 (tid 100317) too long > > panic: spin lock held too long > > I guess it's more related to the thread on stable@ which has the panic > message > as its subject. > > > cpuid = 0 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > kdb_backtrace() at kdb_backtrace+0x37 > > panic() at panic+0x187 > > _mtx_lock_spin_failed() at _mtx_lock_spin_failed+0x39 > > _mtx_lock_spin() at _mtx_lock_spin+0x9e > > sched_add() at sched_add+0x117 > > setrunnable() at setrunnable+0x78 > > sleepq_signal() at sleepq_signal+0x7a > > cv_signal() at cv_signal+0x3b > > xprt_active() at xprt_active+0xe3 > > svc_vc_soupcall() at svc_vc_soupcall+0xc > > sowakeup() at sowakeup+0x69 > > tcp_do_segment() at tcp_do_segment+0x2cbd > > tcp_input() at tcp_input+0xcdd > > ip_input() at ip_input+0xac > > netisr_dispatch_src() at netisr_dispatch_src+0x7e > > ether_demux() at ether_demux+0x14d > > ether_input() at ether_input+0x17d > > em_rxeof() at em_rxeof+0x1ca > > em_handle_que() at em_handle_que+0x5b > > taskqueue_run_locked() at taskqueue_run_locked+0x85 > > taskqueue_thread_loop() at taskqueue_thread_loop+0x4e > > fork_exit() at fork_exit+0x11f > > fork_trampoline() at fork_trampoline+0xe > > --- trap 0, rip = 0, rsp = 0xffffff8000160d00, rbp = 0 --- > > KDB: enter: panic > > [thread pid 0 tid 100033 ] > > Stopped at kdb_enter+0x3b: movq $0,0x6b4e62(%rip) > > db> ps > > > > -- > Andriy Gapon > _______________________________________________ > 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 Sat Jul 30 23:56:20 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 91CDE106564A; Sat, 30 Jul 2011 23:56:20 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-4.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 470A11552A8; Sat, 30 Jul 2011 23:55:52 +0000 (UTC) Message-ID: <4E349A08.50801@FreeBSD.org> Date: Sat, 30 Jul 2011 16:55:52 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:5.0) Gecko/20110723 Thunderbird/5.0 MIME-Version: 1.0 To: John Baldwin References: <4E23EE49.5040801@FreeBSD.org> <201107191116.07116.jhb@freebsd.org> <4E33A990.7040006@FreeBSD.org> <201107300834.29194.jhb@freebsd.org> In-Reply-To: <201107300834.29194.jhb@freebsd.org> X-Enigmail-Version: 1.2pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: ichwd0: unable to reserve GCS registers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 30 Jul 2011 23:56:20 -0000 On 07/30/2011 05:34, John Baldwin wrote: > On Saturday, July 30, 2011 02:49:52 AM Andriy Gapon wrote: >> on 19/07/2011 18:16 John Baldwin said the following: >>> Hmm, can you get devinfo -r output from a working kernel with ichwd >>> loaded? You might be able to just build the kernel with 'nooptions >>> NEW_PCIB'. So is this still relevant? I'm sorry I haven't had a chance to get this done, but I may be able to this weekend if you still think it's useful. Doug >> I believe that I've got a similar problem with amdsbwd(4). >> It needs some resources (I/O ports) that belong to ACPI. >> The problem is that the driver attaches to isa bus which is under >> isab->pci->pcib and those particular resources are not assigned to the >> Host-PCI bridge. >> >> I think that you already made a suggestion that perhaps isa bus should >> directly attach to acpi bus when acpi is available. Not sure if there are >> any alternative approaches. > > Actually, my suggestion was the other way around (we should move certain ACPI > devices down behind isab so they are behind the Host-PCI bridge as they are in > hardware). In this case the BIOS clearly does not list the reosurces for the > GCS as valid resources for the Host-PCI bridge. This is part of the reason > that I added the 'debug.acpi.disable="hostres"'. One thing we may be able to > do is allow non-wildcard requests that are outside the range to still pass if > they are in ACPI's system resource range perhaps. > -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/