From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 03:44:09 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05423106564A; Sun, 23 Oct 2011 03:44:09 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailA.acsu.buffalo.edu (localmail.buffalo.edu [128.205.5.196]) by mx1.freebsd.org (Postfix) with ESMTP id CAB678FC08; Sun, 23 Oct 2011 03:44:08 +0000 (UTC) Received: from localmailA.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 07E28F683; Sat, 22 Oct 2011 23:44:07 -0400 (EDT) Received: from localmailA.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailA.acsu.buffalo.edu (Postfix) with ESMTP id 5BDAEF6B3; Sat, 22 Oct 2011 23:44:05 -0400 (EDT) Received: from smtp3.acsu.buffalo.edu (smtp3.acsu.buffalo.edu [128.205.5.226]) by localmailA.acsu.buffalo.edu (Prefixe) with ESMTP id 546E3F683; Sat, 22 Oct 2011 23:44:05 -0400 (EDT) Received: from [192.168.1.101] (cpe-72-231-248-9.buffalo.res.rr.com [72.231.248.9]) (Authenticated sender: kensmith@buffalo.edu) by smtp3.acsu.buffalo.edu (Postfix) with ESMTPSA id 05671464F0; Sat, 22 Oct 2011 23:44:05 -0400 (EDT) From: Ken Smith To: freebsd-current@freebsd.org, freebsd-stable Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-F5yjy/3R9S6J8Iy4E/OT" Organization: U. Buffalo Date: Sat, 22 Oct 2011 23:43:53 -0400 Message-ID: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-PM-EL-Spam-Prob: XX: 27% Cc: Subject: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 03:44:09 -0000 --=-F5yjy/3R9S6J8Iy4E/OT Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The first of the Release Candidate builds of the 9.0-RELEASE release cycle is now available. Since this is the first release of a brand new branch I cross-post the announcements on both -current and -stable. But just so you know most of the developers active in head and stable/9 pay more attention to the -current mailing list. If you notice problems you can report them through the normal Gnats PR system or on the -current mailing list. The 9.0-RELEASE cycle will be tracked here: http://wiki.freebsd.org/Releng/9.0-TODO Wrapping up RC1 was a bit delayed due to a bug found during the initial testing of the RC1 images and a few glitches that came up as part of making FreeBSD-Update available. We'll update the schedule soon. NOTE: The location of the FTP install tree and ISOs is the same as it had been for BETA2/BETA3, though we are still deciding if this will be the layout we switch to for the release. ISO images for the following architectures are available, with pathnames given relative to the top-level of the FTP site: amd64: .../releases/amd64/amd64/ISO-IMAGES/9.0/ i386: .../releases/i386/i386/ISO-IMAGES/9.0/ ia64: .../releases/ia64/ia64/ISO-IMAGES/9.0/ powerpc: .../releases/powerpc/powerpc/ISO-IMAGES/9.0/ powerpc64: .../releases/powerpc/powerpc64/ISO-IMAGES/9.0/ sparc64: .../releases/sparc64/sparc64/ISO-IMAGES/9.0/ MD5/SHA256 checksums are tacked on below. If you would like to use csup/cvsup mechanisms to access the source tree the branch tag to use is now "RELENG_9", if you use "." (head) you will get 10-CURRENT. If you would like to access the source tree via SVN it is "svn://svn.freebsd.org/base/stable/9/". We still have the nit that the creation of a new SVN branch winds up causing what looks like a check-in of the entire tree in CVS (a side-effect of the svn2cvs exporter) so "mergemaster -F" is your friend if you are using csup/cvsup. FreeBSD Update -------------- The freebsd-update(8) utility supports binary upgrades of i386 and amd64 sy= stems running earlier FreeBSD releases. Systems running 7.[34]-RELEASE, 8.[12]-RELEASE, or 9.0-BETA[123] can upgrade as follows: First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message "The update metadata is correctly signed, but failed an integrity check". # sed -i '' -e 's/=3D_/=3D%@_/' /usr/sbin/freebsd-update Now freebsd-update can fetch bits belonging to 9.0-RC1. During this proces= s freebsd-update will ask for help in merging configuration files. # freebsd-update upgrade -r 9.0-RC1 Due to changes in the way that FreeBSD is packaged on the release media, tw= o complications may arise in this process: 1. The FreeBSD kernel, which previously could appear in either /boot/kernel or /boot/GENERIC, now only appears as /boot/kernel. As a result, any kerne= l appearing in /boot/GENERIC will be deleted. Please carefully read the outp= ut printed by freebsd-update and confirm that an updated kernel will be placed into /boot/kernel before proceeding beyond this point. 2. The FreeBSD source tree in /usr/src (if present) will be deleted. (Norm= ally freebsd-update will update a source tree, but in this case the changes in release packaging result in freebsd-update not recognizing that the source = tree from the old release and the source tree from the new release correspond to= the same part of FreeBSD.) # freebsd-update install The system must now be rebooted with the newly installed kernel before the non-kernel components are updated. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.2-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 9.0-RC1: # shutdown -r now Checksums: MD5 (FreeBSD-9.0-RC1-amd64-bootonly.iso) =3D 625d64340f952de2fca7102dac7f18= 0f MD5 (FreeBSD-9.0-RC1-amd64-dvd1.iso) =3D 5cccbb21a8448e54e4d631619b5f4861 MD5 (FreeBSD-9.0-RC1-amd64-memstick.img) =3D 07f83c8015a1907953b826b0c65069= f0 MD5 (FreeBSD-9.0-RC1-i386-bootonly.iso) =3D 59f1c057eaa6bff6c69d8e411adeb13= c MD5 (FreeBSD-9.0-RC1-i386-dvd1.iso) =3D 0f168bcfa832282cf6e3914ffc5a5014 MD5 (FreeBSD-9.0-RC1-i386-memstick.img) =3D ccbc2db07a19b3e77e75958cd747064= 3 MD5 (FreeBSD-9.0-RC1-ia64-bootonly.iso) =3D e2e80ffae14950d0437c067e7c6553f= 1 MD5 (FreeBSD-9.0-RC1-ia64-memstick) =3D 997bb23954682d503ba10fc3f1a2d624 MD5 (FreeBSD-9.0-RC1-ia64-release.iso) =3D 3703dc72d55fb9c66450e800b123cffe MD5 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) =3D 2a651f4af37af85e49b6a8fcaa42= a77f MD5 (FreeBSD-9.0-RC1-powerpc-memstick) =3D a2c33dfab3f98b0d83db382d73cdd87a MD5 (FreeBSD-9.0-RC1-powerpc-release.iso) =3D af4afc51149dcd61488b44ecbbf96= fc5 MD5 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) =3D 96f2bce40f2974be55578bf9cc= 7318a1 MD5 (FreeBSD-9.0-RC1-powerpc64-memstick) =3D e4647934091f4c72b4df331eb1134e= b3 MD5 (FreeBSD-9.0-RC1-powerpc64-release.iso) =3D b6989f2e4285b7479a72f4503dc= 420cf MD5 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) =3D df7146d2497a16b502e92e35ae24= 921e MD5 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) =3D 6cd56a20a6d907525077424c55a163a4 SHA256 (FreeBSD-9.0-RC1-amd64-bootonly.iso) =3D ec44fefd1c54fb724079b83951c= fe721404ecb76a4a861a2ef4c2a1b63b88aff SHA256 (FreeBSD-9.0-RC1-amd64-dvd1.iso) =3D 6558689957ce2a48f3aa235ab11cd46= 13db7afe11f102b0ae5d566b22e30c132 SHA256 (FreeBSD-9.0-RC1-amd64-memstick.img) =3D c04abe37f83c8ed07e3645cbaff= 8cfa21d223f94cda059a053bd1a469c6b753c SHA256 (FreeBSD-9.0-RC1-i386-bootonly.iso) =3D 9e720cb8306171b137ae50d3887a= bf09f90fab6f953b39a9f552c87c3221d441 SHA256 (FreeBSD-9.0-RC1-i386-dvd1.iso) =3D 488599d5328b20278e90d5489b8d2afd= 49bf466a5d7a31694f3c0eb66d97c6f1 SHA256 (FreeBSD-9.0-RC1-i386-memstick.img) =3D 9eadded30ee684840bb6ead60f98= d8d8e455e690148491b55dec9b657ab7ac10 SHA256 (FreeBSD-9.0-RC1-ia64-bootonly.iso) =3D b4b33ecc30555b532be4ebcc3a5f= 566189265066141b852a3a912ddc8e1aa203 SHA256 (FreeBSD-9.0-RC1-ia64-memstick) =3D f437f5af4c8dd780d329bb90f5189c7b= b1b270df1b05bff979e7fbcc7cf819d6 SHA256 (FreeBSD-9.0-RC1-ia64-release.iso) =3D aaa21f0244d1238b11f5af267935c= 7cbea20f0d5fb393bef7534011ab7f017f1 SHA256 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) =3D 5a45de1a72fd2c15f58c73068= 02533d48a5dee512b5e6f0377e859bf4a25200e SHA256 (FreeBSD-9.0-RC1-powerpc-memstick) =3D fe85b8232123a510468658380117e= 51a2ca3737e92cacb525717cefb73b9740c SHA256 (FreeBSD-9.0-RC1-powerpc-release.iso) =3D 8024a84ccf4962fe8ec7e03042= 1a476f96c410fe67c9c9b25935248304029682 SHA256 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) =3D 43e97f229ccf82337807834= 8390b6b75b3ca5c95db107a48087d6a5fc3980e92 SHA256 (FreeBSD-9.0-RC1-powerpc64-memstick) =3D 7323eb46e90849bab53c3b15875= 3b1824ae9e464c63ffe7bb33fe726c6a7c415 SHA256 (FreeBSD-9.0-RC1-powerpc64-release.iso) =3D 6c0643f2de33a04426d168dd= 23187a71c971d3e4bfd222eb32bdbaa65f2c0368 SHA256 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) =3D 8664ed9a0282b80341c6e2436= 43011c84b058f4c8450a5e6e2b3f99bd9df469c SHA256 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) =3D 5220f817e078024208b9ab3060518= 911c4e0ed0693575ca101a97608b73121af --=20 Ken Smith - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-F5yjy/3R9S6J8Iy4E/OT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk6jjXEACgkQ/G14VSmup/ZS6gCdGvd6UUj/WGq1STG7ovADU+8I okIAn2SZNOoAT7u2KWvMJyAm8J8Tf6Br =ngbT -----END PGP SIGNATURE----- --=-F5yjy/3R9S6J8Iy4E/OT-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 05:23:07 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4749D1065674 for ; Sun, 23 Oct 2011 05:23:07 +0000 (UTC) (envelope-from basarevych@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0154A8FC13 for ; Sun, 23 Oct 2011 05:23:06 +0000 (UTC) Received: by qadz32 with SMTP id z32so2670027qad.13 for ; Sat, 22 Oct 2011 22:23: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:content-transfer-encoding; bh=pmnVsJJOJrlITjY63FQGw1wlMaBawJ18hq5euMeb6aY=; b=BXerDTJ8Ot7D1133SgPl6MU7WmPrfbGmXpr1R6xlNfT+ib7wMXxnrVG/U729NnhoUz coWG60NPVWgGueKNj52ooD27ZnWjP3n/MOJn6fnUQ8CITviQp3u4c6qbW8R99w7rhPIm 0L6/SfiHntOX7VJXyQhwoKjsziFLW06NkN4DI= MIME-Version: 1.0 Received: by 10.224.174.68 with SMTP id s4mr16065963qaz.4.1319346034492; Sat, 22 Oct 2011 22:00:34 -0700 (PDT) Received: by 10.224.45.82 with HTTP; Sat, 22 Oct 2011 22:00:34 -0700 (PDT) In-Reply-To: <1319341433.49428.7.camel@neo.cse.buffalo.edu> References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Date: Sun, 23 Oct 2011 08:00:34 +0300 Message-ID: From: Ross To: Ken Smith Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 05:23:07 -0000 On Sun, Oct 23, 2011 at 6:43 AM, Ken Smith wrote: > > The first of the Release Candidate builds of the 9.0-RELEASE release > cycle is now available. =C2=A0Since this is the first release of a brand > new branch I cross-post the announcements on both -current and -stable. > But just so you know most of the developers active in head and stable/9 > pay more attention to the -current mailing list. =C2=A0If you notice prob= lems > you can report them through the normal Gnats PR system or on the > -current mailing list. > > The 9.0-RELEASE cycle will be tracked here: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0http://wiki.freebsd.org/Releng/9.0-TODO Is that http://wiki.freebsd.org/Releng/9.0TODO or a new page will be create= d? > > Wrapping up RC1 was a bit delayed due to a bug found during the initial > testing of the RC1 images and a few glitches that came up as part of > making FreeBSD-Update available. =C2=A0We'll update the schedule soon. > > NOTE: The location of the FTP install tree and ISOs is the same as it > had been for BETA2/BETA3, though we are still deciding if this will be > the layout we switch to for the release. > > ISO images for the following architectures are available, with pathnames > given relative to the top-level of the FTP site: > > =C2=A0amd64: .../releases/amd64/amd64/ISO-IMAGES/9.0/ > =C2=A0i386: .../releases/i386/i386/ISO-IMAGES/9.0/ > =C2=A0ia64: .../releases/ia64/ia64/ISO-IMAGES/9.0/ > =C2=A0powerpc: .../releases/powerpc/powerpc/ISO-IMAGES/9.0/ > =C2=A0powerpc64: .../releases/powerpc/powerpc64/ISO-IMAGES/9.0/ > =C2=A0sparc64: .../releases/sparc64/sparc64/ISO-IMAGES/9.0/ > > MD5/SHA256 checksums are tacked on below. > > If you would like to use csup/cvsup mechanisms to access the source > tree the branch tag to use is now "RELENG_9", if you use "." (head) > you will get 10-CURRENT. =C2=A0If you would like to access the source tre= e > via SVN it is "svn://svn.freebsd.org/base/stable/9/". =C2=A0We still have > the nit that the creation of a new SVN branch winds up causing what > looks like a check-in of the entire tree in CVS (a side-effect of the > svn2cvs exporter) so "mergemaster -F" is your friend if you are using > csup/cvsup. > > FreeBSD Update > -------------- > > The freebsd-update(8) utility supports binary upgrades of i386 and amd64 = systems > running earlier FreeBSD releases. Systems running 7.[34]-RELEASE, > 8.[12]-RELEASE, or 9.0-BETA[123] can upgrade as follows: > > First, a minor change must be made to the freebsd-update code in order > for it to accept file names appearing in FreeBSD 9.0 which contain the '%= ' > and '@' characters; without this change, freebsd-update will error out > with the message "The update metadata is correctly signed, but failed an > integrity check". > > # sed -i '' -e 's/=3D_/=3D%@_/' /usr/sbin/freebsd-update > > Now freebsd-update can fetch bits belonging to 9.0-RC1. =C2=A0During this= process > freebsd-update will ask for help in merging configuration files. > > # freebsd-update upgrade -r 9.0-RC1 > > Due to changes in the way that FreeBSD is packaged on the release media, = two > complications may arise in this process: > 1. The FreeBSD kernel, which previously could appear in either /boot/kern= el > or /boot/GENERIC, now only appears as /boot/kernel. =C2=A0As a result, an= y kernel > appearing in /boot/GENERIC will be deleted. =C2=A0Please carefully read t= he output > printed by freebsd-update and confirm that an updated kernel will be plac= ed > into /boot/kernel before proceeding beyond this point. > 2. The FreeBSD source tree in /usr/src (if present) will be deleted. =C2= =A0(Normally > freebsd-update will update a source tree, but in this case the changes in > release packaging result in freebsd-update not recognizing that the sourc= e tree > from the old release and the source tree from the new release correspond = to the > same part of FreeBSD.) > > # freebsd-update install > > The system must now be rebooted with the newly installed kernel before th= e > non-kernel components are updated. > > # shutdown -r now > > After rebooting, freebsd-update needs to be run again to install the new > userland components: > > # freebsd-update install > > At this point, users of systems being upgraded from FreeBSD 8.2-RELEASE o= r > earlier will be prompted by freebsd-update to rebuild all third-party > applications (e.g., ports installed from the ports tree) due to updates i= n > system libraries. > > After updating installed third-party applications (and again, only if > freebsd-update printed a message indicating that this was necessary), run > freebsd-update again so that it can delete the old (no longer used) syste= m > libraries: > > # freebsd-update install > Finally, reboot into 9.0-RC1: > > # shutdown -r now > > Checksums: > > MD5 (FreeBSD-9.0-RC1-amd64-bootonly.iso) =3D 625d64340f952de2fca7102dac7f= 180f > MD5 (FreeBSD-9.0-RC1-amd64-dvd1.iso) =3D 5cccbb21a8448e54e4d631619b5f4861 > MD5 (FreeBSD-9.0-RC1-amd64-memstick.img) =3D 07f83c8015a1907953b826b0c650= 69f0 > > MD5 (FreeBSD-9.0-RC1-i386-bootonly.iso) =3D 59f1c057eaa6bff6c69d8e411adeb= 13c > MD5 (FreeBSD-9.0-RC1-i386-dvd1.iso) =3D 0f168bcfa832282cf6e3914ffc5a5014 > MD5 (FreeBSD-9.0-RC1-i386-memstick.img) =3D ccbc2db07a19b3e77e75958cd7470= 643 > > MD5 (FreeBSD-9.0-RC1-ia64-bootonly.iso) =3D e2e80ffae14950d0437c067e7c655= 3f1 > MD5 (FreeBSD-9.0-RC1-ia64-memstick) =3D 997bb23954682d503ba10fc3f1a2d624 > MD5 (FreeBSD-9.0-RC1-ia64-release.iso) =3D 3703dc72d55fb9c66450e800b123cf= fe > > MD5 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) =3D 2a651f4af37af85e49b6a8fcaa= 42a77f > MD5 (FreeBSD-9.0-RC1-powerpc-memstick) =3D a2c33dfab3f98b0d83db382d73cdd8= 7a > MD5 (FreeBSD-9.0-RC1-powerpc-release.iso) =3D af4afc51149dcd61488b44ecbbf= 96fc5 > > MD5 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) =3D 96f2bce40f2974be55578bf9= cc7318a1 > MD5 (FreeBSD-9.0-RC1-powerpc64-memstick) =3D e4647934091f4c72b4df331eb113= 4eb3 > MD5 (FreeBSD-9.0-RC1-powerpc64-release.iso) =3D b6989f2e4285b7479a72f4503= dc420cf > > MD5 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) =3D df7146d2497a16b502e92e35ae= 24921e > MD5 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) =3D 6cd56a20a6d907525077424c55a163= a4 > > SHA256 (FreeBSD-9.0-RC1-amd64-bootonly.iso) =3D ec44fefd1c54fb724079b8395= 1cfe721404ecb76a4a861a2ef4c2a1b63b88aff > SHA256 (FreeBSD-9.0-RC1-amd64-dvd1.iso) =3D 6558689957ce2a48f3aa235ab11cd= 4613db7afe11f102b0ae5d566b22e30c132 > SHA256 (FreeBSD-9.0-RC1-amd64-memstick.img) =3D c04abe37f83c8ed07e3645cba= ff8cfa21d223f94cda059a053bd1a469c6b753c > > SHA256 (FreeBSD-9.0-RC1-i386-bootonly.iso) =3D 9e720cb8306171b137ae50d388= 7abf09f90fab6f953b39a9f552c87c3221d441 > SHA256 (FreeBSD-9.0-RC1-i386-dvd1.iso) =3D 488599d5328b20278e90d5489b8d2a= fd49bf466a5d7a31694f3c0eb66d97c6f1 > SHA256 (FreeBSD-9.0-RC1-i386-memstick.img) =3D 9eadded30ee684840bb6ead60f= 98d8d8e455e690148491b55dec9b657ab7ac10 > > SHA256 (FreeBSD-9.0-RC1-ia64-bootonly.iso) =3D b4b33ecc30555b532be4ebcc3a= 5f566189265066141b852a3a912ddc8e1aa203 > SHA256 (FreeBSD-9.0-RC1-ia64-memstick) =3D f437f5af4c8dd780d329bb90f5189c= 7bb1b270df1b05bff979e7fbcc7cf819d6 > SHA256 (FreeBSD-9.0-RC1-ia64-release.iso) =3D aaa21f0244d1238b11f5af26793= 5c7cbea20f0d5fb393bef7534011ab7f017f1 > > SHA256 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) =3D 5a45de1a72fd2c15f58c730= 6802533d48a5dee512b5e6f0377e859bf4a25200e > SHA256 (FreeBSD-9.0-RC1-powerpc-memstick) =3D fe85b8232123a51046865838011= 7e51a2ca3737e92cacb525717cefb73b9740c > SHA256 (FreeBSD-9.0-RC1-powerpc-release.iso) =3D 8024a84ccf4962fe8ec7e030= 421a476f96c410fe67c9c9b25935248304029682 > > SHA256 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) =3D 43e97f229ccf823378078= 348390b6b75b3ca5c95db107a48087d6a5fc3980e92 > SHA256 (FreeBSD-9.0-RC1-powerpc64-memstick) =3D 7323eb46e90849bab53c3b158= 753b1824ae9e464c63ffe7bb33fe726c6a7c415 > SHA256 (FreeBSD-9.0-RC1-powerpc64-release.iso) =3D 6c0643f2de33a04426d168= dd23187a71c971d3e4bfd222eb32bdbaa65f2c0368 > > SHA256 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) =3D 8664ed9a0282b80341c6e24= 3643011c84b058f4c8450a5e6e2b3f99bd9df469c > SHA256 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) =3D 5220f817e078024208b9ab30605= 18911c4e0ed0693575ca101a97608b73121af > > -- > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Ken Smith > - From there to here, from here to =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 = =C2=A0 kensmith@buffalo.edu > =C2=A0there, funny things are everywhere. =C2=A0 | > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0- Theodore Geisel | > From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 06:10:48 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81161106564A for ; Sun, 23 Oct 2011 06:10:48 +0000 (UTC) (envelope-from greglmiller@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 1B09A8FC2A for ; Sun, 23 Oct 2011 06:10:47 +0000 (UTC) Received: by wyi40 with SMTP id 40so6711958wyi.13 for ; Sat, 22 Oct 2011 23:10:47 -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=NUn+LIjFOJ/Xx/oirC9l1cdEi+TA8z0VWM3oidFls6o=; b=uYY/xddvHIlBdOBrooGWHEjnDby/6A9bL2eYD5P9oT87dOyUZLzX+DVocmdUugE/hI DucFdE0ERVsua6d+bpEsFX7Itn6XzU/hi0W1kAW93h6mJhgk90Ix1yY44NMIFHGcUcIU aiSyOezIiF9yRhR56zp1g3lAO0Mj56BqVinPw= MIME-Version: 1.0 Received: by 10.227.160.78 with SMTP id m14mr7970272wbx.7.1319348711696; Sat, 22 Oct 2011 22:45:11 -0700 (PDT) Received: by 10.180.89.38 with HTTP; Sat, 22 Oct 2011 22:45:11 -0700 (PDT) In-Reply-To: <1319341433.49428.7.camel@neo.cse.buffalo.edu> References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Date: Sun, 23 Oct 2011 00:45:11 -0500 Message-ID: From: Greg Miller To: Ken Smith Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org, freebsd-stable Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 06:10:48 -0000 On 10/22/11, Ken Smith wrote: > > The first of the Release Candidate builds of the 9.0-RELEASE release > cycle is now available. Since this is the first release of a brand New in RC1, with GENERIC: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=native -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/fs/devfs/devfs_devs.c cc1: warnings being treated as errors /usr/src/sys/fs/devfs/devfs_devs.c: In function 'devfs_free': /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: implicit declaration of function 'devfs_free_cdp_inode' /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: nested extern declaration of 'devfs_free_cdp_inode' [-Wnested-externs] /usr/src/sys/fs/devfs/devfs_devs.c: At top level: /usr/src/sys/fs/devfs/devfs_devs.c:689: warning: no previous prototype for 'devfs_alloc_cdp_inode' [-Wmissing-prototypes] /usr/src/sys/fs/devfs/devfs_devs.c:696: warning: no previous prototype for 'devfs_free_cdp_inode' [-Wmissing-prototypes] /usr/src/sys/fs/devfs/devfs_devs.c:696: warning: conflicting types for 'devfs_free_cdp_inode' /usr/src/sys/fs/devfs/devfs_devs.c:174: warning: previous implicit declaration of 'devfs_free_cdp_inode' was here *** Error code 1 From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 06:12:09 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E1B8106566B for ; Sun, 23 Oct 2011 06:12:09 +0000 (UTC) (envelope-from aw1@swelter.hanley.stade.co.uk) Received: from outbound-queue-2.mail.thdo.gradwell.net (outbound-queue-2.mail.thdo.gradwell.net [212.11.70.35]) by mx1.freebsd.org (Postfix) with ESMTP id F00D38FC15 for ; Sun, 23 Oct 2011 06:12:08 +0000 (UTC) Received: from outbound-edge-1.mail.thdo.gradwell.net (bonnie.gradwell.net [212.11.70.2]) by outbound-queue-2.mail.thdo.gradwell.net (Postfix) with ESMTP id 048D521FE2 for ; Sun, 23 Oct 2011 07:12:08 +0100 (BST) Received: from 93-97-22-18.zone5.bethere.co.uk (HELO swelter.hanley.stade.co.uk) (93.97.22.18) (smtp-auth username postmaster%pop3.stade.co.uk, mechanism cram-md5) by outbound-edge-1.mail.thdo.gradwell.net (qpsmtpd/0.83) with (AES256-SHA encrypted) ESMTPSA; Sun, 23 Oct 2011 07:12:07 +0100 Received: from swelter.hanley.stade.co.uk (localhost [127.0.0.1]) by swelter.hanley.stade.co.uk (8.14.4/8.14.4) with ESMTP id p9N6Bi5d083536 for ; Sun, 23 Oct 2011 07:11:44 +0100 (BST) (envelope-from aw1@swelter.hanley.stade.co.uk) Received: (from aw1@localhost) by swelter.hanley.stade.co.uk (8.14.4/8.14.4/Submit) id p9N6BiCi083535 for freebsd-stable@freebsd.org; Sun, 23 Oct 2011 07:11:44 +0100 (BST) (envelope-from aw1) Date: Sun, 23 Oct 2011 07:11:44 +0100 From: Adrian Wontroba To: "freebsd-stable@freebsd.org" Message-ID: <20111023061144.GB4834@swelter.hanley.stade.co.uk> Mail-Followup-To: Adrian Wontroba , "freebsd-stable@freebsd.org" References: <86d3eydsmf.fsf@kopusha.home.net> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> <86r52ek8pn.fsf@kopusha.home.net> <86k486m435.fsf@kopusha.home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86k486m435.fsf@kopusha.home.net> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.2-STABLE Organization: Oh dear, I've joined one again. X-Virus-Scanned: clamav-milter 0.97.1 at swelter.hanley.stade.co.uk X-Virus-Status: Clean X-Gradwell-MongoId: 4ea3b037.4d4c-2582-1 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: postmaster@pop3.stade.co.uk Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and xargs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aw1@stade.co.uk List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 06:12:09 -0000 On Sat, Oct 15, 2011 at 10:45:18PM +0300, Mikolaj Golub wrote: > On Sat, 15 Oct 2011 11:50:22 +0200 Stefan Bethke wrote: > SB> Seems to do the trick, thanks! > Thanks for testing! Committed. I am going to MFC it soon. Gentlemen, thank you! I can confirm that at $JOB with a RELENG_8 system post the MFC, script no longer hangs when run via batch nor consumes excessive amounts of CPU. -- Adrian Wontroba You are not drunk if you can lay on the floor without holding on. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 06:41:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 580B5106564A; Sun, 23 Oct 2011 06:41:12 +0000 (UTC) (envelope-from yanegomi@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 055A78FC0A; Sun, 23 Oct 2011 06:41:11 +0000 (UTC) Received: by ggnq2 with SMTP id q2so4727410ggn.13 for ; Sat, 22 Oct 2011 23:41:11 -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:content-transfer-encoding; bh=MIlAnqKAW23iTPrM4REBRX5c1RlT62RrWI5/36M8wSs=; b=s+ffyYb4W0atxqkzMOCgkHBXcnA82ILwRAiEaT8UOgDZjimn/PD0EDqW22rQQHtqyw z9lyz01wxl3LhgpcTy+JfqB8/s13PDuMT/u+by1w0Ej+h+Q5LV1zXu25J/HbRmAGDeuM vLVpY9YpECSvM2gfO+kMEi7+zxBgaa5owBg34= MIME-Version: 1.0 Received: by 10.182.7.10 with SMTP id f10mr2300365oba.56.1319350183101; Sat, 22 Oct 2011 23:09:43 -0700 (PDT) Received: by 10.182.122.33 with HTTP; Sat, 22 Oct 2011 23:09:43 -0700 (PDT) In-Reply-To: References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Date: Sat, 22 Oct 2011 23:09:43 -0700 Message-ID: From: Garrett Cooper To: Greg Miller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Konstantin Belousov , freebsd-current@freebsd.org, freebsd-stable Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 06:41:12 -0000 On Sat, Oct 22, 2011 at 10:45 PM, Greg Miller wrote= : > On 10/22/11, Ken Smith wrote: >> >> The first of the Release Candidate builds of the 9.0-RELEASE release >> cycle is now available. =A0Since this is the first release of a brand > > New in RC1, with GENERIC: Was r226041 MFCed properly? -Garrett From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 06:48:01 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59259106566B for ; Sun, 23 Oct 2011 06:48:01 +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 1B1A28FC0C for ; Sun, 23 Oct 2011 06:48:00 +0000 (UTC) Received: by iaky10 with SMTP id y10so8281433iak.13 for ; Sat, 22 Oct 2011 23:48:00 -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; bh=k72vsKsjeynyv+7AHI6Cycpk4UPJBABEJBDy2xaz0Vk=; b=HCmxrR0sOS2snD0Rt4zyHYmTOaW7SLQxEX5aqU/glHj07RDHDQPKsiqSLxbtpmKbHp hMI0bma93j4aeoWYcS92WuTWzH0nSuccWpUXftn4Ja/XObuWYINd4TSEoJst8KyLo2ej lzSE1z7sHvFBTgE9jTn6P9HfPQeZv0SVRrrCs= MIME-Version: 1.0 Received: by 10.231.49.147 with SMTP id v19mr7761449ibf.64.1319352480147; Sat, 22 Oct 2011 23:48:00 -0700 (PDT) Sender: utisoft@gmail.com Received: by 10.231.11.140 with HTTP; Sat, 22 Oct 2011 23:47:59 -0700 (PDT) Received: by 10.231.11.140 with HTTP; Sat, 22 Oct 2011 23:47:59 -0700 (PDT) In-Reply-To: <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> References: <20110918045413.GA63773@DataIX.net> <20110918053901.GA31617@icarus.home.lan> <86d3eydsmf.fsf@kopusha.home.net> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> Date: Sun, 23 Oct 2011 07:47:59 +0100 X-Google-Sender-Auth: ewiX8YZG1ZxtY-pU1ZGvqN-k9hE Message-ID: From: Chris Rees To: Stefan Bethke Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-stable@freebsd.org" , Mikolaj Golub , Jilles Tjoelker Subject: Re: /usr/bin/script eating 100% cpu with portupgrade and xargs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 06:48:01 -0000 On 14 Oct 2011 21:50, "Stefan Bethke" wrote: > > > Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker: > > > On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: > >> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: > >>> I won't be in a position to create a simpler test case, raise a PR or > >>> try patches till Tuesday evening (UK) at the earliest. > > > >> So far I have been unable to reproduce the problem with portupgrade (and > >> will probably move to portmaster). > > > >> I have however found a different but possibly related problem with the > >> new version of script in RELENG_8, for which I have raised this PR: > > > >> misc/161526: script outputs corrupt if input is not from a terminal > > > >> Blast, should of course been bin/ > > > > The extra ^D\b\b are the EOF character being echoed. These EOF > > characters are being generated by the new script(1) to pass through the > > EOF condition on stdin. > > > > One fix would be to change the termios settings temporarily to disable > > the echoing but this may cause problems if the application is changing > > termios settings concurrently and generally feels bad. > > > > It may be best to remove writing EOF characters, perhaps adding an > > option to enable it again if there is a concrete use case for it. > > I finally figured out why my ports aren't updating anymore: when running portupgrade -a --batch from cron, stdin is /dev/null, and that produces the gobs of ^D in the output, as well as the script file that portupgrade creates. What's worse is that the upgrade never completes. > Worst of all, you're running portupgrade from cron without reading UPDATING, which is just asking for trouble. Chris From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 08:12:18 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C79C010656D0 for ; Sun, 23 Oct 2011 08:12:18 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 703DC8FC17 for ; Sun, 23 Oct 2011 08:12:18 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p9N8CHVl035418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Oct 2011 01:12:17 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p9N8CHMt035417; Sun, 23 Oct 2011 01:12:17 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA11915; Sun, 23 Oct 11 01:10:34 PDT Date: Sun, 23 Oct 2011 08:09:19 -0700 From: perryh@pluto.rain.com To: kob6558@gmail.com Message-Id: <4ea42e1f.jwGZJ3vXBxYqD41h%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 08:12:18 -0000 Kevin Oberman wrote: > Wow. it's 1985 again. O remember those 10/100 hubs. They were a > royal pain! > > If I remember right, they kept costs down by building in half of > a switch. Traffic from a 10 port to a 100 port was buffered, Speed conversion had to have been buffered in both directions. If trying to convert 100 to 10 unbuffered, only 10% of a packet could have been retransmitted (at 10) by the time the entire packet had been received (at 100). In the other direction, trying to send at 100 while receiving at 10 would have had 9 bit-times of gap for every live bit sent. > but there was no forwarding table and all packets were forwarded > to all ports. I always figured that's normal for a "hub" as opposed to a "switch". > I also remember that SOME hubs of that era had series problems if > the cable was too short. > > You mentioned using a short cable. Have you tried a longer one? > I seem to recall that 3 meters was the minimum, but it was so > long ago that my memory is a bit fuzzy. The first cable I used was about 1 meter, the second less than 2. I suppose I could try a longer one. The only minimum length restriction I _remember_ with Ethernet was the separation of transceivers on a 10Base-5 backbone cable (and, perhaps, a corresponding separation between tees on 10Base-2). I think it was to avoid having two impedance "bumps" within one bit propagation time of each other or some such. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 10:32:54 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1A0E106566B; Sun, 23 Oct 2011 10:32:54 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id A24418FC08; Sun, 23 Oct 2011 10:32:54 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id 6D041DF11D; Sun, 23 Oct 2011 12:32:53 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Stefan Bethke In-Reply-To: Date: Sun, 23 Oct 2011 12:32:52 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110918045413.GA63773@DataIX.net> <20110918053901.GA31617@icarus.home.lan> <86d3eydsmf.fsf@kopusha.home.net> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> To: Chris Rees X-Mailer: Apple Mail (2.1251.1) Cc: "freebsd-stable@freebsd.org List" Subject: Running portupgrade from cron (was: /usr/bin/script eating 100% cpu with portupgrade and xargs) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 10:32:55 -0000 Am 23.10.2011 um 08:47 schrieb Chris Rees: > Worst of all, you're running portupgrade from cron without reading = UPDATING, > which is just asking for trouble. What specifically is your concern here? I've been running portupgrade from cron for six years on a multitude of = systems with great success. Yes, occasionally, things break, and = reading UPDATING becomes a necessity, but I much prefer the nightly = upgrade to running portupgrade by hand less frequently, especially when = you have to do it on 20 or more machines. Note that most of these boxes have very limited SLAs, and dealing with = the occasional breakage is much less work than regular manual = maintainance. I decided to do this after I got bitten one too many times trying to = upgrade ports after three to four months, and getting stuck in all kinds = of bad dependencies. Daily upgrades usually means that I catch every = single update by itself, so complex interdependencies are exactly what = the committer tested. Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 11:35:28 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4CAF106564A for ; Sun, 23 Oct 2011 11:35:28 +0000 (UTC) (envelope-from basarevych@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5559D8FC0A for ; Sun, 23 Oct 2011 11:35:28 +0000 (UTC) Received: by qadz32 with SMTP id z32so2728261qad.13 for ; Sun, 23 Oct 2011 04:35:27 -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:content-transfer-encoding; bh=+QgHhr6aJ3PEwCaXaaHfty2Y8AAJGHHscjpe2LCK2/M=; b=OB8dePCildLKavn2KLf3bmPKh1f9ztXdnOSxi7fb4eX1KpdPciRrxfvtF+0WlPjs2i D7XJR4E7H71A6PAWqeBALxG6aYZxCPP5hyie5XOggupnNHnIVd9wlNopQFR23qtfT7vA Jtl82baDqYOubc8frzNZhOcrZsSun1GVGwC8g= MIME-Version: 1.0 Received: by 10.224.18.210 with SMTP id x18mr8622520qaa.80.1319369727650; Sun, 23 Oct 2011 04:35:27 -0700 (PDT) Received: by 10.224.67.68 with HTTP; Sun, 23 Oct 2011 04:35:27 -0700 (PDT) In-Reply-To: <9E8E59C0-5FE6-4193-9A01-8A2DFBC311F7@lassitu.de> References: <20110918045413.GA63773@DataIX.net> <20110918053901.GA31617@icarus.home.lan> <86d3eydsmf.fsf@kopusha.home.net> <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> <9E8E59C0-5FE6-4193-9A01-8A2DFBC311F7@lassitu.de> Date: Sun, 23 Oct 2011 14:35:27 +0300 Message-ID: From: Ross To: Stefan Bethke Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Running portupgrade from cron (was: /usr/bin/script eating 100% cpu with portupgrade and xargs) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 11:35:28 -0000 On Sun, Oct 23, 2011 at 2:14 PM, Stefan Bethke wrote: > Am 23.10.2011 um 13:11 schrieb Ross: > >> On Sun, Oct 23, 2011 at 1:32 PM, Stefan Bethke wrote: >>> Am 23.10.2011 um 08:47 schrieb Chris Rees: >>> >>>> Worst of all, you're running portupgrade from cron without reading UPD= ATING, >>>> which is just asking for trouble. >>> >>> What specifically is your concern here? >> >> And what you will get with ignoring /usr/ports/UPDATING when this happen= s: >> 20100328: >> AFFECTS: users of graphics/png >> AUTHOR: dinoex@FreeBSD.org >> >> The PNG library has been updated to version 1.4.1. Please rebuild all >> ports that depend on it. > > And where exactly did I say that I never read UPDATING, and that I wouldn= 't follow it's instructions? Yes, but updating correctly in first place is better than trying to understand what happened to software looking for libpng.so.N when there is libpng.so.N+1 and _then_ reading UPDATING is better, don't you think? Other point is that during update daemons never restarted. But sometimes stopped, dovecot, for example, if I'm not mistaken. Do you also reboot after each cron update? > > > Stefan > > -- > Stefan Bethke =C2=A0 Fon +49 151 14070811 > > > > From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 12:43:58 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF5E1106566B for ; Sun, 23 Oct 2011 12:43:58 +0000 (UTC) (envelope-from allicient3141@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AD80B8FC0A for ; Sun, 23 Oct 2011 12:43:58 +0000 (UTC) Received: by vws11 with SMTP id 11so5712640vws.13 for ; Sun, 23 Oct 2011 05:43:58 -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; bh=HD/nAvZFrBXX2c2SwbVjVuq5cqgrh6NHhAcgD1DeAYw=; b=tN6gLlL4jA2liuRnqiLwvOj5/1VToLwxPofP/jAbFtNDg9scnVHoeWPDfO/ij8UMjI qOMpFoul1/BnpsoD0yycmLhOiG/ZHVrmZqrY09L71rITMEFaQZ5Gd2xDYJSfOjMSl89l xSVyOaqhUujk3BZaDYCfl9FJUWkPX6uakF0hk= MIME-Version: 1.0 Received: by 10.52.113.67 with SMTP id iw3mr19345667vdb.121.1319372046082; Sun, 23 Oct 2011 05:14:06 -0700 (PDT) Sender: allicient3141@gmail.com Received: by 10.52.108.136 with HTTP; Sun, 23 Oct 2011 05:14:06 -0700 (PDT) In-Reply-To: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> Date: Sun, 23 Oct 2011 13:14:06 +0100 X-Google-Sender-Auth: 1RWQ8V5Q6asKhLK5XOzlR016Dnw Message-ID: From: Peter Maxwell To: perryh@pluto.rain.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 12:43:59 -0000 On 21 October 2011 16:00, wrote: > > ...snip... > > Both connections were using the same (short) Cat5 cable, I tried two > different ports on the 10/100 hub, and other systems work OK on that > 10/100 hub. > > How do I get this interface to operate properly at 100MB? > > ...snip... "Auto-negotiation" is a nightmare, and *will* cause you problems. The best you can do is try to try to set every device using the switch to 100Mbps full, if that doesn't work buy a proper switch. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 13:08:17 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B40E1106564A for ; Sun, 23 Oct 2011 13:08:17 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Received: from melo.ec-m.fr (melo.ec-m.fr [147.94.19.139]) by mx1.freebsd.org (Postfix) with ESMTP id 5AB9B8FC16 for ; Sun, 23 Oct 2011 13:08:17 +0000 (UTC) Received: from amavis3.serv.int (amavis3.serv.int [10.3.0.47]) by melo.ec-m.fr (GrosseBox 1743 XXL) with ESMTP id B3CFFAC928 for ; Sun, 23 Oct 2011 14:53:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at centrale-marseille.fr Received: from melo.ec-m.fr ([10.3.0.13]) by amavis3.serv.int (amavis3.serv.int [10.3.0.47]) (amavisd-new, port 10024) with LMTP id n48KtoVU3ljf for ; Sun, 23 Oct 2011 14:53:11 +0200 (CEST) Received: from [192.168.13.1] (dgeos.mezon.dgeos.net [192.168.13.1]) (Authenticated sender: dgeo) by melo.ec-m.fr (GrosseBox 1743 XXL) with ESMTPSA id 4CF62AC91B for ; Sun, 23 Oct 2011 14:53:11 +0200 (CEST) Message-ID: <4EA40E35.9060403@centrale-marseille.fr> Date: Sun, 23 Oct 2011 14:53:09 +0200 From: geoffroy desvernay User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110805 Icedove/5.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20110913103328.GA34028@icarus.home.lan> <6F2A4E2B-9EBE-4B23-8617-B7625537FA8A@gausus.net> <4E6F3D03.7020407@gmail.com> In-Reply-To: <4E6F3D03.7020407@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: problem with LSI MegaRAID on 8.2-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 13:08:17 -0000 On 13/09/2011 13:22, Johan Hendriks wrote: > Maciej Jan Broniarz schreef: >> Wiadomo=C5=9B=C4=87 napisana przez Jeremy Chadwick w dniu 13 wrz 2011,= o godz. >> 12:33: >> >>> On Tue, Sep 13, 2011 at 11:43:29AM +0200, Maciej Jan Broniarz wrote: >>>> I'm having some trouble with LSI MegaRAID on FreeBSD 8.2-RELEASE-p2 >>>> My storage starts to freeze and the following message apears in the >>>> log: >>>> >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3005 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3035 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3065 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3095 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3125 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3156 SECONDS >>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3186 SECONDS >>>> >>>> What might be the issue here? >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063808.= html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063809.= html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063810.= html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063811.= html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/0638= 16.html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/0638= 17.html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/0638= 21.html >>> >>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/0638= 23.html >>> >>> >>> -- >> Thanks. But there is still no solution for the problem. I haven't >> applied any patch >> and yet the problem occurs. >> >> All best, >> mjb >> >> >> > > Maybe i understand your comment the wrong way, but i think the patch is= > there to prevent prevent the problem. > So by applying the following patch// > www.freebsd.org/~jhb/patches/mfi.patch// > Your issue should be SOLVED.// > // > regards > Johan Hendriks > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" Same issue here with dell's PERC H700 (LSI repackaged by dell). The patch referenced here solves the problem for me (8.2-STABLE and=20 9.0-RC1 on amd64): http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/140416 Could someone commit this, or is this problem solved y other means ? (I=20 don't follow freebsd-fs@ not freebsd-scsi@ for now...) --=20 *Geoffroy Desvernay* C.R.I - Administration syst=C3=A8mes et r=C3=A9seaux Ecole Centrale de Marseille From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 13:55:23 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE591065670 for ; Sun, 23 Oct 2011 13:55:23 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from mail.deployis.eu (mail.deployis.eu [217.20.135.253]) by mx1.freebsd.org (Postfix) with ESMTP id 23B748FC15 for ; Sun, 23 Oct 2011 13:55:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=antiszoc.hu; s=default; h=Subject:To:From:Date; bh=JS748tA3XGN/EYM+TxtDWWFHuUhOXxqmmNMdI7GFEBc=; b=Jlf1QrYzLF62SD+lO7PndH8toEJzKUehcqAKI6j+zfi0XgebsYyF3KD5vCsCOEkUE1GZdN7Bs0DqdOBGS4Ua+f5MbAn1Hf4t8Hi/SaStpHMC9mrz4Aq92DJY5dd54/CB; Received: from localhost ([127.0.0.1]:59740 helo=mail.deployis.eu) by mail.deployis.eu with esmtp (Exim 4.71 #1 (Debian)) id 1RHyWH-0007od-9T from for ; Sun, 23 Oct 2011 15:55:21 +0200 Received: from pool-233-3.ippark.hu ([31.223.233.3]) by mail.deployis.eu with HTTP (HTTP/1.1 POST); Sun, 23 Oct 2011 15:55:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sun, 23 Oct 2011 15:55:21 +0200 From: =?UTF-8?Q?G=C3=B3t_Andr=C3=A1s?= To: In-Reply-To: <4EA40E35.9060403@centrale-marseille.fr> References: <20110913103328.GA34028@icarus.home.lan> <6F2A4E2B-9EBE-4B23-8617-B7625537FA8A@gausus.net> <4E6F3D03.7020407@gmail.com> <4EA40E35.9060403@centrale-marseille.fr> Message-ID: <2fd749349acb2be1192d2a19fa63469e@antiszoc.hu> X-Sender: andrej@antiszoc.hu User-Agent: RoundCube Webmail/0.2.1 X-DKIM-Status: None (from 127.0.0.1) X-Mail-Status-postahivatal: trustedmail (from 127.0.0.1) X-Spam-Score-postahivatal: -48 Subject: Re: problem with LSI MegaRAID on 8.2-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 13:55:23 -0000 On Sun, 23 Oct 2011 14:53:09 +0200, geoffroy desvernay wrote: > On 13/09/2011 13:22, Johan Hendriks wrote: >> Maciej Jan Broniarz schreef: >>> Wiadomość napisana przez Jeremy Chadwick w dniu 13 wrz 2011, o >>> godz. >>> 12:33: >>> >>>> On Tue, Sep 13, 2011 at 11:43:29AM +0200, Maciej Jan Broniarz >>>> wrote: >>>>> I'm having some trouble with LSI MegaRAID on FreeBSD >>>>> 8.2-RELEASE-p2 >>>>> My storage starts to freeze and the following message apears in >>>>> the >>>>> log: >>>>> >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3005 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3035 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3065 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3095 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3125 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3156 SECONDS >>>>> mfi0: COMMAND 0xffffff8000b6be58 TIMEOUT AFTER 3186 SECONDS >>>>> >>>>> What might be the issue here? >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063808.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063809.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063810.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-August/063811.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063816.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063817.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.html >>>> >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063823.html >>>> >>>> >>>> -- >>> Thanks. But there is still no solution for the problem. I haven't >>> applied any patch >>> and yet the problem occurs. >>> >>> All best, >>> mjb >>> >>> >>> >> >> Maybe i understand your comment the wrong way, but i think the patch >> is >> there to prevent prevent the problem. >> So by applying the following patch// >> www.freebsd.org/~jhb/patches/mfi.patch// >> Your issue should be SOLVED.// >> // >> regards >> Johan Hendriks >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" > Same issue here with dell's PERC H700 (LSI repackaged by dell). > The patch referenced here solves the problem for me (8.2-STABLE and > 9.0-RC1 on amd64): > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 > > Could someone commit this, or is this problem solved y other means ? > (I don't follow freebsd-fs@ not freebsd-scsi@ for now...) Hi, I couldn't apply the referenced patch from the PR you mentioned. I got malformed patch error for it. How could you apply it? Thanks, Andras From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 14:44:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09AFD106564A for ; Sun, 23 Oct 2011 14:44:53 +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 BC58D8FC0C for ; Sun, 23 Oct 2011 14:44:52 +0000 (UTC) Received: by gyd8 with SMTP id 8so6541479gyd.13 for ; Sun, 23 Oct 2011 07:44:52 -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=fHIOB5eOo/EX43HB9lXBjf0keL2XABt3PjbOLDQIfUM=; b=mJysJa0lJsDKjof27GpVTNO55DUBmeLMDpEfIhrWggWP4P34m1cvX3qAk08TSlefUt UxhSGNVzwNRI1nVuk5OwTjwrwGfviRNLhNCeakhgigcm+2Ai9owZiPYcrKbCEfVG/8Xf qfM/VTBUqFzWo9Y9rmiOPmlBbIDaoZFxNn8Ww= MIME-Version: 1.0 Received: by 10.236.73.166 with SMTP id v26mr29639575yhd.100.1319381092084; Sun, 23 Oct 2011 07:44:52 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.109.39 with HTTP; Sun, 23 Oct 2011 07:44:52 -0700 (PDT) In-Reply-To: References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> Date: Sun, 23 Oct 2011 22:44:52 +0800 X-Google-Sender-Auth: hy5d7VvdRlN7uzUfIxGMNdvnTj4 Message-ID: From: Adrian Chadd To: Peter Maxwell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, perryh@pluto.rain.com Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 14:44:53 -0000 On 23 October 2011 20:14, Peter Maxwell wrote: > ...snip... > > "Auto-negotiation" is a nightmare, and *will* cause you problems. =A0The = best > you can do is try to try to set every device using the switch to 100Mbps > full, if that doesn't work buy a proper switch. .. you mean 100/half, as full on a hub =3D=3D path to fail. :P Adrian From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 15:03:57 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B676F1065677 for ; Sun, 23 Oct 2011 15:03:57 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 63BE38FC20 for ; Sun, 23 Oct 2011 15:03:57 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD)) (envelope-from ) id 1RHzag-0009RL-H5 for freebsd-stable@freebsd.org; Sun, 23 Oct 2011 17:03:58 +0200 Date: Sun, 23 Oct 2011 17:03:58 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20111023150358.GS28186@home.opsec.eu> References: <20111008002707.GA76128@swelter.hanley.stade.co.uk> <20111012222535.GB79291@swelter.hanley.stade.co.uk> <20111014120336.GB31718@stack.nl> <08C7028B-10E1-4855-B007-D2257216F077@lassitu.de> <9E8E59C0-5FE6-4193-9A01-8A2DFBC311F7@lassitu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: Running portupgrade from cron (was: /usr/bin/script eating 100% cpu with portupgrade and xargs) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 15:03:57 -0000 Hi! > >>>> Worst of all, you're running portupgrade from cron without > >>>> reading UPDATING, which is just asking for trouble. > >>> What specifically is your concern here? > Yes, but updating correctly in first place is better than trying to > understand what happened to software looking for libpng.so.N when > there is libpng.so.N+1 and _then_ reading UPDATING is better, don't > you think? It depends. I have reference boxes which daily run portupgrade from cron, just to see whether I have a consistent set of ports for our apps. If most of the packages are stable, I'll generate a pkg collection and replicate it to those destination hosts that need updating and replace every pkg on those hosts with new pkgs. > Other point is that during update daemons never restarted. But > sometimes stopped, dovecot, for example, if I'm not mistaken. Do you > also reboot after each cron update? As the reference boxes do not run services, that's not a problem. To sum it up: running portupgrade from cron is useful. -- pi@opsec.eu +49 171 3101372 9 years to go ! From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 15:54:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E9B51065673 for ; Sun, 23 Oct 2011 15:54:41 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3fd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id E668D8FC12 for ; Sun, 23 Oct 2011 15:54:40 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.5/8.14.5) with ESMTP id p9NFsapJ040706 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 23 Oct 2011 16:54:36 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) X-DKIM: OpenDKIM Filter v2.4.1 smtp.infracaninophile.co.uk p9NFsapJ040706 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infracaninophile.co.uk; s=201001-infracaninophile; t=1319385276; bh=3xxyOcBj5611A9rddFP8EF/WAEYglk1tYfO0wbH8Xtk=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Cc; b=LFUxdI5JvHpBb64YWOtG1HDTpmNk0k7VYjRZVvKnvnRKFqTRDW3LfGLUwRAcOfPnQ njOGOfl8LZ7YP/+8icfKufZM33Qal66iLSue7yyPCOwLyBo4ipm9QmYkFDz8sfO091 ZmgerLBXG+ti9jGLWEVaSIDmt4LEynNxeJnKgZCw= Message-ID: <4EA438B2.5030809@infracaninophile.co.uk> Date: Sun, 23 Oct 2011 16:54:26 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> In-Reply-To: X-Enigmail-Version: 1.3.2 OpenPGP: id=60AE908C Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig23564499A10264CF860B6040" X-Virus-Scanned: clamav-milter 0.97.3 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,SPF_FAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 15:54:41 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig23564499A10264CF860B6040 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 23/10/2011 13:14, Peter Maxwell wrote: > "Auto-negotiation" is a nightmare, and *will* cause you problems. The = best > you can do is try to try to set every device using the switch to 100Mbp= s > full, if that doesn't work buy a proper switch. Autoneg is only a nightmare if you use turn-of-the-millenium era kit, back when 100Mb/s was a big deal. xl(4) was particularly bad. On the other hand, for anything Gb capable nowadays connected to a switch autoneg pretty much just works -- em(4), bce(4) are excellent, and even re(4) gets this stuff right. Oh, and as someone else mentioned, 'full duplex' on one of those bastard devices that claim 10/100 speed because they have *one* 100Mb/s capable port, and everything else is a 10Mb/s hub... that way madness lies... Why anyone would use such a thing nowadays I don't know, as even cheapo DSL routers tend to incorporate Gb switched ports nowadays. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW --------------enig23564499A10264CF860B6040 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6kOLsACgkQ8Mjk52CukIxsYQCgjMkxeOYQCFniUZ3QSATqVjtu sDEAn2e3vBX33034RXM1CtuwxbCbdyqY =RgHT -----END PGP SIGNATURE----- --------------enig23564499A10264CF860B6040-- From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 16:05:56 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE4D4106564A for ; Sun, 23 Oct 2011 16:05:56 +0000 (UTC) (envelope-from carlj@peak.org) Received: from redcondor1.peak.org (redcondor1.peak.org [69.59.192.54]) by mx1.freebsd.org (Postfix) with ESMTP id BFA768FC0A for ; Sun, 23 Oct 2011 16:05:56 +0000 (UTC) Received: from zmail-mta01.peak.org ([207.55.16.111]) by redcondor1.peak.org ({e03e86cd-14ae-47ce-9578-3c080ce9c462}) via TCP (outbound) with ESMTP id 20111023160556140 for ; Sun, 23 Oct 2011 16:05:56 +0000 X-RC-FROM: X-RC-RCPT: Received: from maple.localnet (unknown [207.55.106.132]) by zmail-mta01.peak.org (Postfix) with ESMTPSA id 057A5490BA3 for ; Sun, 23 Oct 2011 09:05:56 -0700 (PDT) Received: from oak.localnet (oak.localnet [IPv6:2001:1938:266::6f:616b]) by maple.localnet (Postfix) with ESMTP id 8F5C261F71 for ; Sun, 23 Oct 2011 09:05:54 -0700 (PDT) Received: from oak.localnet (localhost.localnet [127.0.0.1]) by oak.localnet (Postfix) with ESMTP id 5E746C6EB for ; Sun, 23 Oct 2011 09:05:54 -0700 (PDT) Received: (from carlj@localhost) by oak.localnet (8.14.4/8.14.4/Submit) id p9NG5sg6066595; Sun, 23 Oct 2011 09:05:54 -0700 (PDT) (envelope-from carlj@peak.org) X-Authentication-Warning: oak.localnet: carlj set sender to carlj@peak.org using -f From: Carl Johnson To: freebsd-stable@freebsd.org References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Mail-Followup-To: freebsd-stable@freebsd.org Date: Sun, 23 Oct 2011 09:05:54 -0700 In-Reply-To: <1319341433.49428.7.camel@neo.cse.buffalo.edu> (Ken Smith's message of "Sat, 22 Oct 2011 23:43:53 -0400") Message-ID: <8762jf66cd.fsf@oak.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 16:05:57 -0000 Ken Smith writes: > The first of the Release Candidate builds of the 9.0-RELEASE release > cycle is now available. Since this is the first release of a brand > new branch I cross-post the announcements on both -current and -stable. > But just so you know most of the developers active in head and stable/9 > pay more attention to the -current mailing list. If you notice problems > you can report them through the normal Gnats PR system or on the > -current mailing list. > > The 9.0-RELEASE cycle will be tracked here: > > http://wiki.freebsd.org/Releng/9.0-TODO Is anybody *EVER* going to update the official web page? http://www.freebsd.org/releases/9.0R/schedule.html is now almost 3 months out of date, and it is the web page that people will find when navigating from the main page. -- Carl Johnson carlj@peak.org From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 16:27:27 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 834961065678 for ; Sun, 23 Oct 2011 16:27:27 +0000 (UTC) (envelope-from artemb@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 13C758FC0A for ; Sun, 23 Oct 2011 16:27:26 +0000 (UTC) Received: by wyi40 with SMTP id 40so7008977wyi.13 for ; Sun, 23 Oct 2011 09:27:25 -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; bh=IuGV51HQJeiDoF0WvJa0XKRm1py8n3qHEG9TOfZSZrE=; b=gb+2Uvi+fxLzyH8ezQd0S3vBIqijRbCm8z6jOdDTkoF+H4F0M2RR38U/CQ4QH7bH8V fF62r96G9ThRycXOeBsYfwFVGLTqYAv61u1Jvj8znDbO+rpnRuu7y9nckD4osodOmxZf xDUQWj8lSRGvfGtcxlAlR/G453Sy6umjyGmeI= MIME-Version: 1.0 Received: by 10.227.37.210 with SMTP id y18mr2438419wbd.15.1319387245835; Sun, 23 Oct 2011 09:27:25 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.227.178.67 with HTTP; Sun, 23 Oct 2011 09:27:25 -0700 (PDT) In-Reply-To: <4EA438B2.5030809@infracaninophile.co.uk> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA438B2.5030809@infracaninophile.co.uk> Date: Sun, 23 Oct 2011 09:27:25 -0700 X-Google-Sender-Auth: bRJTftlO3-yzWc-Lose62FYi_pc Message-ID: From: Artem Belevich To: Matthew Seaman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 16:27:27 -0000 On Sun, Oct 23, 2011 at 8:54 AM, Matthew Seaman wrote: > On the other hand, for anything Gb capable nowadays connected to a > switch autoneg pretty much just works -- em(4), bce(4) are excellent, > and even re(4) gets this stuff right. There are still cases of incompatibility. I've got a cheap D-Link GigE switch that consistently autonegotiates bge(4) devices to 100/FD unless I force mastership on the NIC end with 'ifconfig bge0 link0'. em(4) device negotiates with the switch just fine, though. --Artem From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 18:20:25 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73027106566B; Sun, 23 Oct 2011 18:20:25 +0000 (UTC) (envelope-from f0andrey@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 1D7C38FC08; Sun, 23 Oct 2011 18:20:24 +0000 (UTC) Received: by vcbfo13 with SMTP id fo13so6724564vcb.13 for ; Sun, 23 Oct 2011 11:20:24 -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:content-transfer-encoding; bh=rVEc+R2m0what9RQKNFHULWAHqnxVjO/JUmEcOR8MP8=; b=DjOo5cz0GZKtBFySQ4UfDgetHOqAOdtWUoMH6Q1vMhod6F0A9mafoYbkjocPYXkoBr NhCY5e5XP3SxgrfVeytvJKgpXviHQnYGPpXfr1EE8gWgX1QQiZKWTAeS5hpTBhnV93Zg tCdKXuoJRq55pVOODYoBzTNmNtvJgAER7vCQE= MIME-Version: 1.0 Received: by 10.52.68.240 with SMTP id z16mr20079334vdt.120.1319394024340; Sun, 23 Oct 2011 11:20:24 -0700 (PDT) Received: by 10.220.199.138 with HTTP; Sun, 23 Oct 2011 11:20:24 -0700 (PDT) In-Reply-To: <1319341433.49428.7.camel@neo.cse.buffalo.edu> References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> Date: Sun, 23 Oct 2011 22:20:24 +0400 Message-ID: From: Andrey Fesenko To: Ken Smith Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-stable Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 18:20:25 -0000 On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith wrote: > > The 9.0-RELEASE cycle will be tracked here: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0http://wiki.freebsd.org/Releng/9.0-TODO > link error, need http://wiki.freebsd.org/Releng/9.0TODO still no actual information on this page. Branch status not actual. From owner-freebsd-stable@FreeBSD.ORG Sun Oct 23 19:02:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8E3B106566B; Sun, 23 Oct 2011 19:02:45 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailB.acsu.buffalo.edu (localmailb.acsu.buffalo.edu [128.205.5.200]) by mx1.freebsd.org (Postfix) with ESMTP id AAA808FC0C; Sun, 23 Oct 2011 19:02:45 +0000 (UTC) Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 42713ADDB; Sun, 23 Oct 2011 15:02:43 -0400 (EDT) Received: from localmailB.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailB.acsu.buffalo.edu (Postfix) with ESMTP id 9A3E816A52; Sun, 23 Oct 2011 15:02:42 -0400 (EDT) Received: from smtp1.acsu.buffalo.edu (smtp1.acsu.buffalo.edu [128.205.5.253]) by localmailB.acsu.buffalo.edu (Prefixe) with ESMTP id 927FEADDB; Sun, 23 Oct 2011 15:02:42 -0400 (EDT) Received: from ken-smiths-macbook-pro.local (cpe-72-231-248-9.buffalo.res.rr.com [72.231.248.9]) (Authenticated sender: kensmith@buffalo.edu) by smtp1.acsu.buffalo.edu (Postfix) with ESMTPSA id 5044946098; Sun, 23 Oct 2011 15:02:42 -0400 (EDT) Message-ID: <4EA464C4.70105@buffalo.edu> Date: Sun, 23 Oct 2011 15:02:28 -0400 From: Ken Smith User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Andrey Fesenko References: <1319341433.49428.7.camel@neo.cse.buffalo.edu> In-Reply-To: X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-PM-EL-Spam-Prob: XX: 28% Cc: freebsd-current@freebsd.org, freebsd-stable Subject: Re: FreeBSD 9.0-RC1 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2011 19:02:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/23/11 2:20 PM, Andrey Fesenko wrote: > On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith > wrote: >> >> The 9.0-RELEASE cycle will be tracked here: >> >> http://wiki.freebsd.org/Releng/9.0-TODO >> > > link error, need http://wiki.freebsd.org/Releng/9.0TODO Correct, sorry about the hyphen sneaking in. > still no actual information on this page. Branch status not > actual. I updated the dates. If by "Branch Status" you're referring to the section with that title it is actual. We've created stable/9 but not releng/9.0 yet. That might come with RC2, sorta depends on how much people find wrong with RC1. When releng/9.0 gets created it will take one commit and two merges to get fixes into 9.0-RELEASE which is a bit of a pain if there is a lot of activity. - -- Ken Smith - - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6kZMQACgkQ/G14VSmup/amiACgj1mmb1TG+39IlZzQzFRTIcKi mGYAn2kdMJ5A8HEK6wBhE2RgrQmRKLzr =/j9J -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 05:26:13 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A674106566C for ; Mon, 24 Oct 2011 05:26:13 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 1891A8FC12 for ; Mon, 24 Oct 2011 05:26:13 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p9O5QBwl059107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Oct 2011 22:26:12 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p9O5QBvX059106; Sun, 23 Oct 2011 22:26:11 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA16099; Sun, 23 Oct 11 22:24:16 PDT Date: Mon, 24 Oct 2011 05:23:00 -0700 From: perryh@pluto.rain.com To: freebsd-stable@freebsd.org Message-Id: <4ea558a4.knypxguulwxhau70%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> In-Reply-To: <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd@jdc.parodius.com Subject: SOLVED: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 05:26:13 -0000 > > You can either replace the NIC with something else, > > or replace the hub. IMHO, I would replace both. > > I can replace the hub easily enough -- I have a 100-only > Netgear that _is_ a true hub (has been used successfully > for sniffing) ... That fixed it. For the archives, this particular xl (on a Dell mainboard) is not compatible with a Netgear DS-106 "dual-speed hub" at 100MB, at least using the driver that shipped with FreeBSD 8.1-RELEASE. (I haven't tried other xl's, or other FreeBSD versions.) It does work with a Netgear FE-104 100-only hub. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 05:36:52 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E1B41065670 for ; Mon, 24 Oct 2011 05:36:52 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 79EC58FC12 for ; Mon, 24 Oct 2011 05:36:52 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p9O5ap6Y059971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Oct 2011 22:36:52 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p9O5apZN059970; Sun, 23 Oct 2011 22:36:51 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA16113; Sun, 23 Oct 11 22:25:10 PDT Date: Mon, 24 Oct 2011 05:23:54 -0700 From: perryh@pluto.rain.com To: kob6558@gmail.com Message-Id: <4ea558da.jZWwZY1xO0HA0ohN%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> <4ea42e1f.jwGZJ3vXBxYqD41h%perryh@pluto.rain.com> In-Reply-To: <4ea42e1f.jwGZJ3vXBxYqD41h%perryh@pluto.rain.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 05:36:52 -0000 > > ... SOME hubs of that era had series problems if the cable was > > too short. > > > > You mentioned using a short cable. Have you tried a longer one? > > I seem to recall that 3 meters was the minimum, but it was so > > long ago that my memory is a bit fuzzy. > > The first cable I used was about 1 meter, the second less than 2. > I suppose I could try a longer one. I tried one of ~5 meters. Same problem. The soultion was to use a 100-only hub instead of the dual-speed hub -- see the SOLUTION post elsewhere in this thread for details. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 06:37:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A569F106566C for ; Mon, 24 Oct 2011 06:37:10 +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 64E158FC12 for ; Mon, 24 Oct 2011 06:37:10 +0000 (UTC) Received: by gyd8 with SMTP id 8so7042839gyd.13 for ; Sun, 23 Oct 2011 23:37:10 -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; bh=Z3wNSOoHPVArp79Uh592wWujpzHCV4wp2ipantPODqg=; b=SKvdGO6sgVn7XGpvFdSsFc1ByMxkf2ZziSEfIovK6wkHsw/QYw+vtGKZdsxWM6PT9T nFITJaCxPI6AldfYKvUttPBva1uVYicIBZ+Z/Nj4Zsz8vptK/5bwV+IebwSidKg6oahC ou/zy9ADUUgaIRHZikcz6Yw5pHvW9g7OqU6yk= MIME-Version: 1.0 Received: by 10.236.133.241 with SMTP id q77mr28948280yhi.117.1319438229891; Sun, 23 Oct 2011 23:37:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.109.39 with HTTP; Sun, 23 Oct 2011 23:37:09 -0700 (PDT) In-Reply-To: <4ea558a4.knypxguulwxhau70%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> <4ea558a4.knypxguulwxhau70%perryh@pluto.rain.com> Date: Mon, 24 Oct 2011 14:37:09 +0800 X-Google-Sender-Auth: X8jmWbC6LGX2E8phUq-WrF5Swrg Message-ID: From: Adrian Chadd To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: SOLVED: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 06:37:10 -0000 Out of pure interest, I'd love to see whether xl on an earlier kernel (say 4.x, if the hardware can even run it) or even 6.x would work. Adrian From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 09:53:02 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35439106566B for ; Mon, 24 Oct 2011 09:53:02 +0000 (UTC) (envelope-from carlopmart@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id C14F68FC0A for ; Mon, 24 Oct 2011 09:53:01 +0000 (UTC) Received: by eyd10 with SMTP id 10so7142262eyd.13 for ; Mon, 24 Oct 2011 02:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Z9KQluRRuB0AhCbwr4LBy5VHo/80dLEfG6djiT3oKFk=; b=AKSGLlFfGMzzBzzFI6/c5IYXCFLT79qY9cxhLqIoAjYbHBangdM/q4UpbF733+K068 cyuFDl68mcfZ/G6LNGE52PHnGRFB+epkY7dnNW64zy1lw4oigx3k7zXK/hg0bMpXJanJ wm0cQIhWvSc+MPmM/17oRLGGPqbBYB+tAhqWg= Received: by 10.14.2.207 with SMTP id 55mr2650126eef.152.1319448116641; Mon, 24 Oct 2011 02:21:56 -0700 (PDT) Received: from silmaril.hpulabs.org (71.Red-88-11-134.dynamicIP.rima-tde.net. [88.11.134.71]) by mx.google.com with ESMTPS id 49sm58605366eec.1.2011.10.24.02.21.54 (version=SSLv3 cipher=OTHER); Mon, 24 Oct 2011 02:21:55 -0700 (PDT) Message-ID: <4EA52E30.4010704@gmail.com> Date: Mon, 24 Oct 2011 11:21:52 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Questions about using gvirstor as a RAID0 solution X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 09:53:02 -0000 Hi all, I would like to use gvirstor as a thin provisioning solution for a mysql server, but I have some doubts about using it: a) Do I need to put "geom_virstor_load=YES"" on loader.conf or this kernel module is loaded automatically at boot If I create gvirstor volume using the label option?? b) Does gvirstor supports UFS journaling?? For example: gjournal label /dev/virstor/mydata newfs -O 2 -J /dev/virstor/mydata c) Can i use growfs utility If I need to expand a virstor volume at filesystem level?? Thanks P.D: I am using FreeBSD9-RC1 in this server -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 10:13:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D02C106564A for ; Mon, 24 Oct 2011 10:13:12 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BB4118FC14 for ; Mon, 24 Oct 2011 10:13:11 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RIHWm-0004rK-QL for freebsd-stable@freebsd.org; Mon, 24 Oct 2011 12:13:08 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Oct 2011 12:13:08 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Oct 2011 12:13:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 24 Oct 2011 12:12:56 +0200 Lines: 63 Message-ID: References: <4EA52E30.4010704@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA65E34382CDDD5EBFED6FDCD" X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1 In-Reply-To: <4EA52E30.4010704@gmail.com> X-Enigmail-Version: 1.1.2 Subject: Re: Questions about using gvirstor as a RAID0 solution X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 10:13:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA65E34382CDDD5EBFED6FDCD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 24/10/2011 11:21, carlopmart wrote: > Hi all, >=20 > I would like to use gvirstor as a thin provisioning solution for a > mysql server, but I have some doubts about using it: Yes, it's kind of what it was created for... > a) Do I need to put "geom_virstor_load=3DYES"" on loader.conf or this > kernel module is loaded automatically at boot If I create gvirstor > volume using the label option?? You need to load the module yourself, the same as with other GEOM modules= =2E > b) Does gvirstor supports UFS journaling?? For example: >=20 > gjournal label /dev/virstor/mydata > newfs -O 2 -J /dev/virstor/mydata You can do that. It will be very inefficient (i.e. you will only avoid fscks, there will probably be no performance gains at all) but nothing should break. Both virstor and gjournal add their overheads (specifically, they can be seek-intensive in different ways), so you wouldn't want to use either if sustained random IO performance is importa= nt. On the other hand, since you are using 9-stable, you can also use the journaled soft-updates instead of gjournal, for much better efficiency. > c) Can i use growfs utility If I need to expand a virstor volume at > filesystem level?? Not exactly; virstor will immediately create a volume with large virtual size (whatever you specify at the volume creation) ragardless of how many physical devices you have. If you add more physical devices to the virstor later, you do not have to do anything with the file system itself, it will still see the original large virtual size. If you are talking about expanding the virtual volume size, that's not implemented yet (and in that case you would need to use growfs). --------------enigA65E34382CDDD5EBFED6FDCD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6lOigACgkQldnAQVacBchSCwCgyMhV+1SbKLjsQjBjB2mFpot5 In0Anj3kTUqFKCfKtoLgz4fQ9RKmStXm =oWPK -----END PGP SIGNATURE----- --------------enigA65E34382CDDD5EBFED6FDCD-- From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 12:32:20 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC0F8106566C for ; Mon, 24 Oct 2011 12:32:20 +0000 (UTC) (envelope-from carlopmart@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 408AA8FC19 for ; Mon, 24 Oct 2011 12:32:20 +0000 (UTC) Received: by wyi40 with SMTP id 40so7872059wyi.13 for ; Mon, 24 Oct 2011 05:32:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bbv1qmpQ+mnAkBKEV9GmrN3D6IxEZTrtm3CjVIeIMM0=; b=wBgMKY1O5qK6UBL0NbkqmBWvMQ86fIGW5H72qWVBto90unZQCUP9QE9qqMhi3XKkk0 Owh1h0BP1oFwSIN7VvyrCosV+qh+7hGi1cD+GVPkJtBHtMs0xLgNiAcdbnGoFmP615Cr UOSBU0Uice2hMO7uHK4WupXgbnXXlfhBLAXN0= Received: by 10.227.7.141 with SMTP id d13mr9109609wbd.78.1319459539304; Mon, 24 Oct 2011 05:32:19 -0700 (PDT) Received: from silmaril.hpulabs.org (71.Red-88-11-134.dynamicIP.rima-tde.net. [88.11.134.71]) by mx.google.com with ESMTPS id y10sm38732422wbm.14.2011.10.24.05.32.15 (version=SSLv3 cipher=OTHER); Mon, 24 Oct 2011 05:32:16 -0700 (PDT) Message-ID: <4EA55ACD.1080608@gmail.com> Date: Mon, 24 Oct 2011 14:32:13 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA52E30.4010704@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Questions about using gvirstor as a RAID0 solution X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 12:32:20 -0000 On 10/24/2011 12:12 PM, Ivan Voras wrote: > On 24/10/2011 11:21, carlopmart wrote: >> Hi all, >> >> I would like to use gvirstor as a thin provisioning solution for a >> mysql server, but I have some doubts about using it: > > Yes, it's kind of what it was created for... > >> a) Do I need to put "geom_virstor_load=YES"" on loader.conf or this >> kernel module is loaded automatically at boot If I create gvirstor >> volume using the label option?? > > You need to load the module yourself, the same as with other GEOM modules. > >> b) Does gvirstor supports UFS journaling?? For example: >> >> gjournal label /dev/virstor/mydata >> newfs -O 2 -J /dev/virstor/mydata > > You can do that. It will be very inefficient (i.e. you will only avoid > fscks, there will probably be no performance gains at all) but nothing > should break. Both virstor and gjournal add their overheads > (specifically, they can be seek-intensive in different ways), so you > wouldn't want to use either if sustained random IO performance is important. > > On the other hand, since you are using 9-stable, you can also use the > journaled soft-updates instead of gjournal, for much better efficiency. > >> c) Can i use growfs utility If I need to expand a virstor volume at >> filesystem level?? > > Not exactly; virstor will immediately create a volume with large virtual > size (whatever you specify at the volume creation) ragardless of how > many physical devices you have. If you add more physical devices to the > virstor later, you do not have to do anything with the file system > itself, it will still see the original large virtual size. > > If you are talking about expanding the virtual volume size, that's not > implemented yet (and in that case you would need to use growfs). > Solved. Many thanks Ivan. -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 21:05:58 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C36521065670; Mon, 24 Oct 2011 21:05:58 +0000 (UTC) (envelope-from pyunyh@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 ED5938FC12; Mon, 24 Oct 2011 21:05:57 +0000 (UTC) Received: by wwi18 with SMTP id 18so9354402wwi.31 for ; Mon, 24 Oct 2011 14:05:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=kbvipacLw8lRihcOLyK7ZUf+k6sikRSc7Gz5+p/WGKo=; b=dP+nXwQnGIHTOz5Y1nv6YcGVX/NXzd8j3rXls025M9c28SUWkD+jHvITzCvp7T5bmf TeJTrvUx3Rg2l0U7eQ8f5Xa2zUEixuvhiNZqvSdTBAbEJNLUvUn6e4wRMmsnfZhgnHKE XAqLyRt8ILzmDzL2TsHsa9IxNJW40GrH9vz/0= Received: by 10.216.54.20 with SMTP id h20mr2956348wec.97.1319490356673; Mon, 24 Oct 2011 14:05:56 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id gd18sm41238063wbb.5.2011.10.24.14.05.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 24 Oct 2011 14:05:55 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 24 Oct 2011 14:04:16 -0700 From: YongHyeon PYUN Date: Mon, 24 Oct 2011 14:04:16 -0700 To: freebsd-current@FreeBSD.org Message-ID: <20111024210416.GE4663@michelle.cdnetworks.com> References: <20111017002213.GB3338@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111017002213.GB3338@michelle.cdnetworks.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Call for testers : ALi/ULi M5261/M5263 ethernet controller X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 21:05:58 -0000 On Sun, Oct 16, 2011 at 05:22:13PM -0700, YongHyeon PYUN wrote: > Hi, > > If you have ALi/ULi M5261/M5263 ethernet controller please try the > patch at the following URL and let me know how it works. > http://people.freebsd.org/~yongari/dc/dc.uli562x.diff > > The patch was generated against latest HEAD and it should be > cleanly applied to latest stable/8 and stable/7. > I committed revised version to HEAD(r226699, r226701). > Thanks. From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 22:43:13 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4AB4106566C for ; Mon, 24 Oct 2011 22:43:13 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 692E68FC0A for ; Mon, 24 Oct 2011 22:43:13 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id B72FF153434; Tue, 25 Oct 2011 00:43:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8qHxqX1zVV9; Tue, 25 Oct 2011 00:43:09 +0200 (CEST) Received: from [IPv6:2001:4cb8:3:1:c02b:ce62:71ff:9cbc] (unknown [IPv6:2001:4cb8:3:1:c02b:ce62:71ff:9cbc]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digiware.nl (Postfix) with ESMTPSA id CA5B2153433; Tue, 25 Oct 2011 00:43:09 +0200 (CEST) Message-ID: <4EA5EA04.9020403@digiware.nl> Date: Tue, 25 Oct 2011 00:43:16 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> <4ea42e1f.jwGZJ3vXBxYqD41h%perryh@pluto.rain.com> In-Reply-To: <4ea42e1f.jwGZJ3vXBxYqD41h%perryh@pluto.rain.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 22:43:13 -0000 On 23-10-2011 17:09, perryh@pluto.rain.com wrote: >> but there was no forwarding table and all packets were forwarded >> to all ports. > > I always figured that's normal for a "hub" as opposed to a "switch". > >> I also remember that SOME hubs of that era had series problems if >> the cable was too short. How come I feel old. Well I think that that was the reason why thick-Ethernet used to have repeaters and bridges. Repeaters just did what they said, on the most basic electrical level. Nothing more that a 2 port HUB, but then with MUI connectors. They where just part of the collision domain. Bridges actually learned which hosts where on the left and the right side. And only bridged when they really needed to. Otherwise they'd leave the traffic on the segment where it originated. It did segment the collision domain into two parts. And they used to be horrendously expensive and only run 10Mbit. --WjW From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 22:51:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0530106566B for ; Mon, 24 Oct 2011 22:51:12 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5710E8FC13 for ; Mon, 24 Oct 2011 22:51:11 +0000 (UTC) Received: by vws11 with SMTP id 11so7239829vws.13 for ; Mon, 24 Oct 2011 15:51:11 -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=MgBhEW+wzF+Rmbn93NetcYLc6dzvKK/FIHAZT4uGNN8=; b=mB7IYeGI699LWh3avnmCeIbHlRY+HQtOn7xIsImhgnS9d19sRqvuiF7+OvJ/bSrsBx o7jhucyLmH1qHeaUNZCFvjSjdmWA9H8lMZmmemGyi1MrGokxsWRxuzh46MWFHV89HIWX 8EE6qXn2q9CR2WozwaiCO/rjalSLDLLTS8tqs= MIME-Version: 1.0 Received: by 10.52.90.51 with SMTP id bt19mr25904335vdb.34.1319496671391; Mon, 24 Oct 2011 15:51:11 -0700 (PDT) Received: by 10.220.201.141 with HTTP; Mon, 24 Oct 2011 15:51:11 -0700 (PDT) In-Reply-To: <4EA12D26.4020104@my.gd> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> Date: Mon, 24 Oct 2011 15:51:11 -0700 Message-ID: From: Freddie Cash To: Damien Fleuriot Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 22:51:12 -0000 On Fri, Oct 21, 2011 at 1:28 AM, Damien Fleuriot wrote: > On 10/21/11 5:00 PM, perryh@pluto.rain.com wrote: > > I have an 8.1-RELEASE system with an xl on the mainboard: > > > > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc80-0xdcff mem > 0xf8fffc00-0xf8fffc7f irq 16 at device 4.0 on pci2 > > miibus0: on xl0 > > xlphy0: <3c905C 10/100 internal PHY> PHY 24 on miibus0 > > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > xl0: Ethernet address: 00:b0:d0:22:5a:14 > > xl0: [ITHREAD] > > > > It has been working properly while connected to an old 10-BaseT hub, > > but when I moved it to a (not as old) Netgear 10/100 dual-speed hub > > the link started to yo-yo: > > > > Pray tell, what's a "dual-speed hub" , marketing mumbo-jumbo ? > If that's a hub that supports negotiation of different speeds (10 vs > 100), then yes, I call that marketing mumbo-jumbo ;) > > Go back to the days of hubs, and the first 10/100 Mbps hubs from just about every manufacturer was labelled "dual-speed". Meaning, it supported 10 Mbps connections and 100 Mbps connection (dual meaning two). ;) 3Com OfficeConnect hubs are all labelled "dual-speed". With the advent of switches, the "dual-speed" moniker was pretty much universally dropped in favour of just listing the speeds it supported (10/100, 10/100/1000, etc). Maybe it's "marketing mumbo jumbo", but it was pretty universal for the time. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 23:10:23 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B40E6106564A for ; Mon, 24 Oct 2011 23:10:23 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 73EDA8FC13 for ; Mon, 24 Oct 2011 23:10:23 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8485928423 for ; Tue, 25 Oct 2011 00:50:31 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9361128422 for ; Tue, 25 Oct 2011 00:50:30 +0200 (CEST) Message-ID: <4EA5EBB5.3090101@quip.cz> Date: Tue, 25 Oct 2011 00:50:29 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 23:10:23 -0000 Hi all, I have a problem with ntpd on many of our servers running 8.2-RELEASE or newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. Ntpd can't resolve host names on boot. This error did not existed on 7.x Oct 24 12:45:22 vcela kernel: Trying to mount root from ufs:/dev/mirror/gm0s1a Oct 24 12:45:23 vcela named[757]: starting BIND 9.6.-ESV-R3 -t /var/named -u bind Oct 24 12:45:23 vcela named[757]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2' Oct 24 12:45:23 vcela named[757]: command channel listening on 127.0.0.1#953 Oct 24 12:45:23 vcela named[757]: command channel listening on ::1#953 Oct 24 12:45:23 vcela named[757]: running Oct 24 12:45:24 vcela ntpd[960]: ntpd 4.2.4p5-a (1) Oct 24 12:45:24 vcela kernel: nfe0: link state changed to UP Oct 24 12:45:24 vcela kernel: acd0: FAILURE - ATA_IDENTIFY status=51 error=4 LBA=0 Oct 24 12:45:31 vcela snmpd[1333]: send: Connection refused Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 0.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `0.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 1.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `1.freebsd.pool.ntp.org', giving up on it Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: 2.freebsd.pool.ntp.org Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve `2.freebsd.pool.ntp.org', giving up on it Is there any know changes in network drivers (nfe or bge) or in order of rc scripts? It seems that nfe interface is bringed up too late. I know there is rc.d/netwait in 8-STABLE, but it is not available on 8.2-RELEASE and I think that there is some regression as this error was not there in the time of FreeBSD 7.x. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 23:27:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E64441065673 for ; Mon, 24 Oct 2011 23:27:52 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id 957848FC19 for ; Mon, 24 Oct 2011 23:27:52 +0000 (UTC) Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta03.westchester.pa.mail.comcast.net with comcast id onTo1h0090mv7h053nTsmb; Mon, 24 Oct 2011 23:27:52 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta11.westchester.pa.mail.comcast.net with comcast id onTr1h01U1t3BNj3XnTsNi; Mon, 24 Oct 2011 23:27:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 39ECD102C1A; Mon, 24 Oct 2011 16:27:50 -0700 (PDT) Date: Mon, 24 Oct 2011 16:27:50 -0700 From: Jeremy Chadwick To: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <20111024232750.GA74032@icarus.home.lan> References: <4EA5EBB5.3090101@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EA5EBB5.3090101@quip.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 23:27:53 -0000 On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote: > I have a problem with ntpd on many of our servers running > 8.2-RELEASE or newer. Some of them are newly installed, most of them > are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. > > Ntpd can't resolve host names on boot. This error did not existed on 7.x > > Oct 24 12:45:22 vcela kernel: Trying to mount root from > ufs:/dev/mirror/gm0s1a > Oct 24 12:45:23 vcela named[757]: starting BIND 9.6.-ESV-R3 -t > /var/named -u bind > Oct 24 12:45:23 vcela named[757]: built with '--prefix=/usr' > '--infodir=/usr/share/info' '--mandir=/usr/share/man' > '--enable-threads' '--enable-getifaddrs' '--disable-linux-caps' > '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' > '--without-libxml2' > Oct 24 12:45:23 vcela named[757]: command channel listening on 127.0.0.1#953 > Oct 24 12:45:23 vcela named[757]: command channel listening on ::1#953 > Oct 24 12:45:23 vcela named[757]: running > Oct 24 12:45:24 vcela ntpd[960]: ntpd 4.2.4p5-a (1) > Oct 24 12:45:24 vcela kernel: nfe0: link state changed to UP > Oct 24 12:45:24 vcela kernel: acd0: FAILURE - ATA_IDENTIFY > status=51 error=4 LBA=0 > Oct 24 12:45:31 vcela snmpd[1333]: send: Connection refused > Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: > 0.freebsd.pool.ntp.org > Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve > `0.freebsd.pool.ntp.org', giving up on it > Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: > 1.freebsd.pool.ntp.org > Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve > `1.freebsd.pool.ntp.org', giving up on it > Oct 24 12:45:43 vcela ntpd_initres[986]: host name not found: > 2.freebsd.pool.ntp.org > Oct 24 12:45:43 vcela ntpd_initres[986]: couldn't resolve > `2.freebsd.pool.ntp.org', giving up on it > > Is there any know changes in network drivers (nfe or bge) or in > order of rc scripts? It seems that nfe interface is bringed up too > late. > > I know there is rc.d/netwait in 8-STABLE, but it is not available on > 8.2-RELEASE and I think that there is some regression as this error > was not there in the time of FreeBSD 7.x. The problem is that the networking layer is not TRULY available by the time ntpd starts. This does have to do with NIC drivers, but the same behaviour can be seen on all NICs, including excellent ones like em(4). You can use the rc.conf netwait_* variables to solve this problem. I'm the author of the script that got committed so that's how I know. :-) An example: netwait_enable="yes" netwait_ip="4.2.2.1 4.2.2.2" netwait_if="em0" If you need help setting this up, let me know. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Oct 24 23:47:24 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 557ED1065701 for ; Mon, 24 Oct 2011 23:47:24 +0000 (UTC) (envelope-from prvs=1278012240=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id CED938FC14 for ; Mon, 24 Oct 2011 23:47:23 +0000 (UTC) X-MDAV-Processed: mail1.multiplay.co.uk, Tue, 25 Oct 2011 00:37:01 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Tue, 25 Oct 2011 00:37:01 +0100 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-5.0 required=6.0 tests=USER_IN_WHITELIST shortcircuit=ham autolearn=disabled version=3.2.5 Received: from r2d2 ([188.220.16.49]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50015801903.msg for ; Tue, 25 Oct 2011 00:37:00 +0100 X-MDRemoteIP: 188.220.16.49 X-Return-Path: prvs=1278012240=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: From: "Steven Hartland" To: "Jeremy Chadwick" , "Miroslav Lachman" <000.fbsd@quip.cz> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> Date: Tue, 25 Oct 2011 00:36:56 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2011 23:47:24 -0000 ----- Original Message ----- From: "Jeremy Chadwick" > The problem is that the networking layer is not TRULY available by the > time ntpd starts. This does have to do with NIC drivers, but the same > behaviour can be seen on all NICs, including excellent ones like em(4). This is generally caused by links to high end switches e.g. cisco which havent had their "server" ports configured with portfast or similar settings. This creates quite a delay once link establishes before traffic is passed and hence the issue. netwait is an excellent script which fixes this and other network dependency issues, something we use as standard on all our machines now :) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 00:37:06 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 677BF1065688; Tue, 25 Oct 2011 00:37:06 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 42CEB8FC08; Tue, 25 Oct 2011 00:37:06 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p9P0b52K085216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Oct 2011 17:37:05 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p9P0b5uQ085215; Mon, 24 Oct 2011 17:37:05 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA20241; Mon, 24 Oct 11 17:31:43 PDT Date: Tue, 25 Oct 2011 00:30:28 -0700 From: perryh@pluto.rain.com To: adrian@freebsd.org Message-Id: <4ea66594.pewjUYOjm/V7gSFV%perryh@pluto.rain.com> References: <4ea18916.IBAr0lF5RCzEYn6G%perryh@pluto.rain.com> <4EA12D26.4020104@my.gd> <4ea2b29c.QmX94UmzdHW1HSBe%perryh@pluto.rain.com> <20111022052952.GA2371@icarus.home.lan> <4ea2e874.XnQpdCknhYCB39Py%perryh@pluto.rain.com> <4ea558a4.knypxguulwxhau70%perryh@pluto.rain.com> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: SOLVED: 8.1 xl + dual-speed Netgear hub = yoyo X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 00:37:06 -0000 Adrian Chadd wrote: > Out of pure interest, I'd love to see whether xl on an earlier > kernel (say 4.x, if the hardware can even run it) or even 6.x > would work. I'll put that on the list for the next time I need to reboot it. I'm sure I have a 6.1 CD somewhere, and probably a 4.x CD also. (The box is old enough -- a Dell Precision 420 -- that it quite likely will run 4.x.) I've also got another old Dell with an xl on the mainboard -- an OptiPlex GX1 running 6.1 -- which will need to get moved to a 100Mb port one of these days. That will provide another data point. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 01:03:29 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F77A106566B for ; Tue, 25 Oct 2011 01:03:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [76.96.59.228]) by mx1.freebsd.org (Postfix) with ESMTP id 4C60E8FC08 for ; Tue, 25 Oct 2011 01:03:28 +0000 (UTC) Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta15.westchester.pa.mail.comcast.net with comcast id oory1h00316LCl05Fp3V7H; Tue, 25 Oct 2011 01:03:29 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta06.westchester.pa.mail.comcast.net with comcast id op3U1h01E1t3BNj3Sp3Uuz; Tue, 25 Oct 2011 01:03:29 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 43B19102C1A; Mon, 24 Oct 2011 18:03:27 -0700 (PDT) Date: Mon, 24 Oct 2011 18:03:27 -0700 From: Jeremy Chadwick To: Steven Hartland Message-ID: <20111025010327.GA75437@icarus.home.lan> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 01:03:29 -0000 On Tue, Oct 25, 2011 at 12:36:56AM +0100, Steven Hartland wrote: > ----- Original Message ----- From: "Jeremy Chadwick" > > > >The problem is that the networking layer is not TRULY available by the > >time ntpd starts. This does have to do with NIC drivers, but the same > >behaviour can be seen on all NICs, including excellent ones like em(4). > > This is generally caused by links to high end switches e.g. cisco which > havent had their "server" ports configured with portfast or similar > settings. This creates quite a delay once link establishes before traffic > is passed and hence the issue. Correct. Folks using STP, RSTP, or LLDP are most likely to see this. However, in our environment we have all of these turned off on our ProCurve switches yet we still see a ~1 second period of time between when the kernel says "em0 is up" vs. when actual packets flow. My point is that even in bare-bones environments (consumer switches, etc.) it's likely that there will be a small period of time where layer 3 packets aren't actually working yet, despite layer 1 and (a portion of) layer 2 being done. > netwait is an excellent script which fixes this and other network dependency > issues, something we use as standard on all our machines now :) It's a hackish workaround for something that should be solved elsewhere, but solving it elsewhere has already been discussed at length in the past so I won't get into it here. (Simple version: we really need something like "svcs" for Solaris, or one of those service-wrapper daemons that Linux and other OSes use. But let's not discuss that here please) netwait's "design model" is very specific given people's needs; the original design worked fine on some machines (all of ours) but I started getting reports of problems from people using vlan(4) and bge(4), etc... so the way it works now is actually reliable for all current NICs and "weirder" environments. The one shortcoming of netwait is that it doesn't support waiting for multiple NICs. Some people have dual-homed environments where they really would like to wait for both, say, em0 and em1, to come up and be functional before any more scripts are started. I left that as a project for someone else, but it's something that should be added given its importance. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 08:55:49 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0952D106566C for ; Tue, 25 Oct 2011 08:55:49 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9739D8FC12 for ; Tue, 25 Oct 2011 08:55:48 +0000 (UTC) Received: by eyd10 with SMTP id 10so198040eyd.13 for ; Tue, 25 Oct 2011 01:55:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Hacg4606T8F5x8d5r+JjaSJwAbELIYGLaou9AAPaH/0=; b=Vb2iCJYHF9n62uj1y6epfY8I5DoibEHeUyv4qQxv8sHBHWbBhT0YlFyxUk3USIspro KGSWaR+Jquk8q2LR3OTzSXxGcKFDQbkXIwrfTNcTlKqEMtf8I37RAMFVxfg6VeszmWl5 fc1/nydewb5pRFDOMS69ibwy6xa1DhTM4k3Ck= Received: by 10.213.106.4 with SMTP id v4mr3306466ebo.108.1319532947644; Tue, 25 Oct 2011 01:55:47 -0700 (PDT) Received: from [192.168.50.106] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id y11sm68151749eej.5.2011.10.25.01.55.46 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 01:55:47 -0700 (PDT) Message-ID: <4EA67991.5020604@gmail.com> Date: Tue, 25 Oct 2011 10:55:45 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 08:55:49 -0000 I have a desktop test machine, and i decided to do a upgarde to 9.0RC1. I dis the buildworld, build kernel, and installkernel step, Then the reboot to do the installworld step. But it panics And it stops very early at the boot process. The console looks like the following (typed by hand) Copyright (c) 1992-2011 The FreeBSD project. Copyright (c) 1979 ................... The regents of the Uni............ FreeBSD is a regited trade................. FreeBSD 9.0-RC1 #0: Tue Oct 25 08:58:57 CEST 2011 root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL amd64 can't re-use a leaf (geom_label)! can't re-use a leaf (iscsi_initiator_max_pdus)! can't re-use a leaf (iscsi_initiator_max_sessions)! can't re-use a leaf (iscsi_initiator)! module_register: module iscsi already excists! Module iscsi failed to register: 17 module_register: module g_label already excists! Module g_label failed to register: 17 CPU: intel(R) Core(TM)2 Quad CPU ........................ origen ....... Features= ........... Features2= ............ AMD Features=................ AMD Featurres2= .............. TSC: P-state invariant, performance statistics real memory = 4294967296 (4096 MB) avail memory = 3298799616 (3145 MB) iscsi: version 2.2.4.2 module_register_init: MOD_LOAD (kdbmux, 0xffffffff8058522d, 0) error 6 panic: make_dev_credv: bad si_name (error=17, si_name=iscsi) cpuid = 0 Uptime: 1s Automatic reboot in 15 second - press a key on the console to abort Any idea what i can do? regards Johan From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 09:25:16 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53DBB106564A for ; Tue, 25 Oct 2011 09:25:16 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id D89338FC12 for ; Tue, 25 Oct 2011 09:25:15 +0000 (UTC) Received: by eyd10 with SMTP id 10so222991eyd.13 for ; Tue, 25 Oct 2011 02:25:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Q8NjDp92Mfo7f2ACYnii5rFcvoShIXNhENDZvPlwX7I=; b=R38KX2Ap2HaeFYxE8MDMiWC7Jx+PiKQSd0yOp6uKrj/Gozj3hR+oOQaQenoF4tLwN7 KTv5I5QUJahuhUOU7PaUtRBgyXoTzWvhKu0/+UY4mEpwNPfNTUNQelGDryEvHdAiPJya MjY1RRvr5xKL/FCcfm7phm5oFYVinc5vWihP0= Received: by 10.14.2.3 with SMTP id 3mr3309805eee.82.1319534714796; Tue, 25 Oct 2011 02:25:14 -0700 (PDT) Received: from [192.168.50.106] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id e62sm41345377eee.10.2011.10.25.02.25.14 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 02:25:14 -0700 (PDT) Message-ID: <4EA68078.5060109@gmail.com> Date: Tue, 25 Oct 2011 11:25:12 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA67991.5020604@gmail.com> In-Reply-To: <4EA67991.5020604@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 09:25:16 -0000 Johan Hendriks schreef: > I have a desktop test machine, and i decided to do a upgarde to 9.0RC1. > I dis the buildworld, build kernel, and installkernel step, > Then the reboot to do the installworld step. > But it panics And it stops very early at the boot process. > > The console looks like the following (typed by hand) > > Copyright (c) 1992-2011 The FreeBSD project. > Copyright (c) 1979 ................... > The regents of the Uni............ > FreeBSD is a regited trade................. > FreeBSD 9.0-RC1 #0: Tue Oct 25 08:58:57 CEST 2011 > root@beasty.testdomain.local:/usr/obj/usr/src/sys/KRNL amd64 > can't re-use a leaf (geom_label)! > can't re-use a leaf (iscsi_initiator_max_pdus)! > can't re-use a leaf (iscsi_initiator_max_sessions)! > can't re-use a leaf (iscsi_initiator)! > module_register: module iscsi already excists! > Module iscsi failed to register: 17 > module_register: module g_label already excists! > Module g_label failed to register: 17 > CPU: intel(R) Core(TM)2 Quad CPU ........................ > origen ....... > Features= ........... > Features2= ............ > AMD Features=................ > AMD Featurres2= .............. > TSC: P-state invariant, performance statistics > real memory = 4294967296 (4096 MB) > avail memory = 3298799616 (3145 MB) > iscsi: version 2.2.4.2 > module_register_init: MOD_LOAD (kdbmux, 0xffffffff8058522d, 0) error 6 > panic: make_dev_credv: bad si_name (error=17, si_name=iscsi) > cpuid = 0 > Uptime: 1s > Automatic reboot in 15 second - press a key on the console to abort > > Any idea what i can do? > > regards > Johan > > A reply to myself. I booted with the live cd. I removed the iscsi part in /boot/loader.conf and now it is doing the installworld step. The ad10s1a partition was not clean maybe it got something to do with that. I will try to load the iscsi initiator after the installworld part and see how it goes. thanks regards Johan Hendriks From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 09:34:21 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4CE3106566B for ; Tue, 25 Oct 2011 09:34:21 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id A2D608FC14 for ; Tue, 25 Oct 2011 09:34:21 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 3D30E28428; Tue, 25 Oct 2011 11:34:20 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 65E6828423; Tue, 25 Oct 2011 11:34:19 +0200 (CEST) Message-ID: <4EA6829A.9040902@quip.cz> Date: Tue, 25 Oct 2011 11:34:18 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Jeremy Chadwick References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> In-Reply-To: <20111024232750.GA74032@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 09:34:22 -0000 Jeremy Chadwick wrote: > On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote: >> I have a problem with ntpd on many of our servers running >> 8.2-RELEASE or newer. Some of them are newly installed, most of them >> are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC. >> >> Ntpd can't resolve host names on boot. This error did not existed on 7.x [...] >> I know there is rc.d/netwait in 8-STABLE, but it is not available on >> 8.2-RELEASE and I think that there is some regression as this error >> was not there in the time of FreeBSD 7.x. > > The problem is that the networking layer is not TRULY available by the > time ntpd starts. This does have to do with NIC drivers, but the same > behaviour can be seen on all NICs, including excellent ones like em(4). > > You can use the rc.conf netwait_* variables to solve this problem. I'm > the author of the script that got committed so that's how I know. :-) > An example: > > netwait_enable="yes" > netwait_ip="4.2.2.1 4.2.2.2" > netwait_if="em0" > > If you need help setting this up, let me know. Yes, I know you are the author and I tested one of the earlier version floating around a mailing list, and I already have it on some 8-STABLE machines where it is included in base /etc/rc.d - thank you for your work! My main concern is that I never needed it on previous FreeBSD versions. I am using ntpdate / ntpd from FreeBSD 4.x days and it always worked fine. So there is some "bad change" on FreeBSD 8.x. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 09:53:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19729106564A for ; Tue, 25 Oct 2011 09:53:45 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (mx1.iaf.psconsult.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id 8D6928FC0A for ; Tue, 25 Oct 2011 09:53:44 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.iaf.psconsult.nl [80.89.238.138] (may be forged)) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id p9P9KCeR051998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 25 Oct 2011 11:20:17 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id p9P9KCCR051997 for freebsd-stable@freebsd.org; Tue, 25 Oct 2011 11:20:12 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Tue, 25 Oct 2011 11:20:12 +0200 From: Paul Schenkeveld To: freebsd-stable@freebsd.org Message-ID: <20111025092012.GA41065@psconsult.nl> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> <20111025010327.GA75437@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111025010327.GA75437@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 09:53:45 -0000 On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: > The one shortcoming of netwait is that it doesn't support waiting for > multiple NICs. Some people have dual-homed environments where they > really would like to wait for both, say, em0 and em1, to come up and be > functional before any more scripts are started. I left that as a > project for someone else, but it's something that should be added given > its importance. How would you like to see multiple interfaces implemented: - All interfaces must be up at the same time - Probe interfaces one by one, proceed to the next when an interface up or bail out when any interface stays down until the loop times out Another shortcoming: ipv6 support... The patch below adds ipv6. One caveat, ping6 is used if a word in netwait_ip contains at least a colon so hostnames in netwait_ip are always pinged using ipv4. Paul Schenkeveld --- src/etc/rc.d/netwait.orig 2011-06-22 08:27:32.000000000 +0200 +++ src/etc/rc.d/netwait 2011-10-25 11:09:16.000000000 +0200 @@ -21,7 +21,7 @@ netwait_start() { - local ip rc count output link + local ip rc count output link ping_cmd if [ -z "${netwait_ip}" ]; then err 1 "You must define one or more IP addresses in netwait_ip" @@ -72,7 +72,13 @@ count=1 while [ ${count} -le ${netwait_timeout} ]; do - /sbin/ping -t 1 -c 1 -o ${ip} >/dev/null 2>&1 + case ${ip} in + *:*) + ping_cmd="/sbin/ping6 -c 1 -o";; + *) + ping_cmd="/sbin/ping -t 1 -c 1 -o";; + esac + ${ping_cmd} ${ip} >/dev/null 2>&1 rc=$? if [ $rc -eq 0 ]; then From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 10:09:18 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D83D1065670 for ; Tue, 25 Oct 2011 10:09:18 +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 6BA408FC16 for ; Tue, 25 Oct 2011 10:09:18 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1RIdgc-00085J-OX for freebsd-stable@freebsd.org; Tue, 25 Oct 2011 02:52:46 -0700 Date: Tue, 25 Oct 2011 02:52:46 -0700 (PDT) From: timp To: freebsd-stable@freebsd.org Message-ID: <1319536366754-4935645.post@n5.nabble.com> In-Reply-To: <4EA67991.5020604@gmail.com> References: <4EA67991.5020604@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 10:09:18 -0000 For installworld you should boot to 'single user mode'. This mode doesn't read loader.conf and much more. Look to the handbook or /usr/src/Makefile for upgrage instructions $ cat /usr/src/Makefile ... # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. & 4. can be combined by using the "kernel" target] # 5. `reboot' (in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster' (you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) ... -- View this message in context: http://freebsd.1045724.n5.nabble.com/From-8-stable-to-9-0-RC1-iscsi-panic-tp4935512p4935645.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 10:22:33 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B53106564A for ; Tue, 25 Oct 2011 10:22:33 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id DB48F8FC14 for ; Tue, 25 Oct 2011 10:22:32 +0000 (UTC) Received: by eyd10 with SMTP id 10so283534eyd.13 for ; Tue, 25 Oct 2011 03:22:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TRFuW35e1IV1Dq/p9guDGd+TH71oQ8fYKb+fDjMh1/Y=; b=iLn65KibGZLHYwvz0EVuH17jNlomrxYnZsqq2gySsBASqwCa7l1/YjlAWGfUIO0Iva fSqwXJ1tvTxQW8XpDdf7DiW84CBM5AoaFtZyZvoRLdZWRbOB35eEqbKfTKl5R61Lmu8M +FK1LESjokF7vz71sdRJPGrz/gQ4shajDyZTU= Received: by 10.213.17.146 with SMTP id s18mr255536eba.16.1319538151891; Tue, 25 Oct 2011 03:22:31 -0700 (PDT) Received: from [192.168.50.106] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id y11sm68867378eej.5.2011.10.25.03.22.31 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 03:22:31 -0700 (PDT) Message-ID: <4EA68DE5.80007@gmail.com> Date: Tue, 25 Oct 2011 12:22:29 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: timp References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> In-Reply-To: <1319536366754-4935645.post@n5.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 10:22:33 -0000 timp schreef: > For installworld you should boot to 'single user mode'. > This mode doesn't read loader.conf and much more. > > Look to the handbook or /usr/src/Makefile for upgrage instructions > $ cat /usr/src/Makefile > ... > # For individuals wanting to upgrade their sources (even if only a > # delta of a few days): > # > # 1. `cd /usr/src' (or to the directory containing your source > tree). > # 2. `make buildworld' > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is > GENERIC). > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is > GENERIC). > # [steps 3.& 4. can be combined by using the "kernel" target] > # 5. `reboot' (in single user mode: boot -s from the loader > prompt). > # 6. `mergemaster -p' > # 7. `make installworld' > # 8. `make delete-old' > # 9. `mergemaster' (you may wish to use -i, along with -U or > -F). > # 10. `reboot' > # 11. `make delete-old-libs' (in case no 3rd party program uses them > anymore) > ... > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/From-8-stable-to-9-0-RC1-iscsi-panic-tp4935512p4935645.html > Sent from the freebsd-stable mailing list archive at Nabble.com. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Well i did use the single user mode ! And the safe mode ! But they all gave me that error. So the did load the loader.conf file. Gr Johan Hendriks From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 10:45:42 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3131106564A for ; Tue, 25 Oct 2011 10:45:42 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124]) by mx1.freebsd.org (Postfix) with ESMTP id 8A3A58FC13 for ; Tue, 25 Oct 2011 10:45:41 +0000 (UTC) Received: from localhost ([92.162.133.50]) by mwinf5d04 with ME id oyFb1h00E15Q9dY03yFcT2; Tue, 25 Oct 2011 12:15:39 +0200 X-ME-engine: default Message-ID: <4EA68C47.2070908@orange.fr> Date: Tue, 25 Oct 2011 12:15:35 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 10:45:43 -0000 Hi, When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to atapicam (and reverting from cdN to acdN of course), vlc was OK again. It seems that I am not the only one having this kind of problem, as I found (for example) this message on questions@ (for releng9): http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html Is this a known problem ? Is somebody working on it ? Thanks, Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 10:52:18 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 636751065676; Tue, 25 Oct 2011 10:52:18 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id DDE0C8FC0A; Tue, 25 Oct 2011 10:52:17 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-211-94.lns20.adl6.internode.on.net [118.210.211.94]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9PAq6b4029987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Oct 2011 21:22:12 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: <4EA68C47.2070908@orange.fr> Date: Tue, 25 Oct 2011 21:22:06 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EA68C47.2070908@orange.fr> To: Claude Buisson X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.162 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 10:52:18 -0000 On 25/10/2011, at 20:45, Claude Buisson wrote: > When upgrading a system to 8.2-STABLE, I switched my kernel from = atapicam to > ATA_CAM, and found that vlc could not play audio CDs anymore. = Reverting to > atapicam (and reverting from cdN to acdN of course), vlc was OK again. >=20 > It seems that I am not the only one having this kind of problem, as I = found (for > example) this message on questions@ (for releng9): >=20 > = http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.h= tml >=20 > Is this a known problem ? Is somebody working on it ? Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? It may be trying old style ATA ioctls based on the device name. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 11:18:52 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEEDF106566B for ; Tue, 25 Oct 2011 11:18:52 +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 61EF38FC19 for ; Tue, 25 Oct 2011 11:18:51 +0000 (UTC) Received: from localhost ([92.162.133.50]) by mwinf5d12 with ME id ozJn1h00415Q9dY03zJnYC; Tue, 25 Oct 2011 13:18:50 +0200 X-ME-engine: default Message-ID: <4EA69B17.6020607@orange.fr> Date: Tue, 25 Oct 2011 13:18:47 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Daniel O'Connor References: <4EA68C47.2070908@orange.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 11:18:52 -0000 On 10/25/2011 12:52, Daniel O'Connor wrote: > > On 25/10/2011, at 20:45, Claude Buisson wrote: >> When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to >> ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to >> atapicam (and reverting from cdN to acdN of course), vlc was OK again. >> >> It seems that I am not the only one having this kind of problem, as I found (for >> example) this message on questions@ (for releng9): >> >> http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html >> >> Is this a known problem ? Is somebody working on it ? > > Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? > Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC) > It may be trying old style ATA ioctls based on the device name. > VLC recognize the tracks and jump quickly from one to the following, without playing it, and with a flow of messages: [0x2caf2a3c] cdda access error: Could not set block size [0x2caf2a3c] cdda access error: cannot read sector nnnnn where the sector number is incremented, and then emit (2 times if I remenber): [0x2af28bc] es demux error: cannot peek Sorry for having ommited these messages in the previous mail. I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a proposal by avg@ related to libxine: http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html These may not be the same problem, but I think they are related (a not so well documented change in the kerm interface). > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 12:02:45 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07761106564A for ; Tue, 25 Oct 2011 12:02:45 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id B81278FC27 for ; Tue, 25 Oct 2011 12:02:44 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id DC5D228423; Tue, 25 Oct 2011 14:02:42 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2C62628428; Tue, 25 Oct 2011 14:02:42 +0200 (CEST) Message-ID: <4EA6A561.80405@quip.cz> Date: Tue, 25 Oct 2011 14:02:41 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Johan Hendriks References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> <4EA68DE5.80007@gmail.com> In-Reply-To: <4EA68DE5.80007@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: timp , freebsd-stable@freebsd.org Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 12:02:45 -0000 Johan Hendriks wrote: > timp schreef: >> For installworld you should boot to 'single user mode'. >> This mode doesn't read loader.conf and much more. [...] > Well i did use the single user mode ! > And the safe mode ! > But they all gave me that error. > So the did load the loader.conf file. I think modules are loaded before displaying boot menu, where you can choose to boot in to single user mode. But you can enter the boot loader prompt, where you can unload already loaded modules or load new modules by its name, so you don't need to edit loader.conf for one time boot option. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 12:17:04 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3097F1065678 for ; Tue, 25 Oct 2011 12:17:04 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id A98C88FC15 for ; Tue, 25 Oct 2011 12:17:03 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-211-94.lns20.adl6.internode.on.net [118.210.211.94]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9PCGtJv033843 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Oct 2011 22:47:01 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: <4EA6A561.80405@quip.cz> Date: Tue, 25 Oct 2011 22:46:55 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: <25920BDD-40FE-43D3-BC0A-A34A30DFC353@gsoft.com.au> References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> <4EA68DE5.80007@gmail.com> <4EA6A561.80405@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.162 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Johan Hendriks , timp , freebsd-stable@freebsd.org Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 12:17:04 -0000 On 25/10/2011, at 22:32, Miroslav Lachman wrote: >=20 >> Well i did use the single user mode ! >> And the safe mode ! >> But they all gave me that error. >> So the did load the loader.conf file. >=20 > I think modules are loaded before displaying boot menu, where you can = choose to boot in to single user mode. > But you can enter the boot loader prompt, where you can unload already = loaded modules or load new modules by its name, so you don't need to = edit loader.conf for one time boot option. They aren't loaded before displaying the menu, but the list of modules = to load is worked out then. If you want to boot without loading the modules listed in loader.conf = you need to break into the loader and type.. unload boot -s (or whatever options you want) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 12:51:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC751106566B for ; Tue, 25 Oct 2011 12:51:10 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id A1DD58FC1A for ; Tue, 25 Oct 2011 12:51:10 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta07.emeryville.ca.mail.comcast.net with comcast id p0qn1h0011GXsucA70r3Rz; Tue, 25 Oct 2011 12:51:03 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta07.emeryville.ca.mail.comcast.net with comcast id p0kD1h00j1t3BNj8U0kEFH; Tue, 25 Oct 2011 12:44:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4C1D2102C31; Tue, 25 Oct 2011 05:51:08 -0700 (PDT) Date: Tue, 25 Oct 2011 05:51:08 -0700 From: Jeremy Chadwick To: Paul Schenkeveld Message-ID: <20111025125108.GA87567@icarus.home.lan> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> <20111025010327.GA75437@icarus.home.lan> <20111025092012.GA41065@psconsult.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111025092012.GA41065@psconsult.nl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 12:51:10 -0000 On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: > On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: > > The one shortcoming of netwait is that it doesn't support waiting for > > multiple NICs. Some people have dual-homed environments where they > > really would like to wait for both, say, em0 and em1, to come up and be > > functional before any more scripts are started. I left that as a > > project for someone else, but it's something that should be added given > > its importance. > > How would you like to see multiple interfaces implemented: > > - All interfaces must be up at the same time > - Probe interfaces one by one, proceed to the next when an interface > up or bail out when any interface stays down until the loop times > out 1) Each interface should be checked in the order specified. 2) Each ping probe should be done using that interface (ping -I). 3) In the case of success, the next interface should be checked (e.g. go back to step #1 but for the next interface defined. 4) In the case of failure, output a message on-screen (similar to what we already do) and continue on with the next interface check. So I imagine the variables for this would need to become something like: netwait_em0_ip="4.2.2.1 4.2.2.2" netwait_em1_ip="192.168.1.1 192.168.1.2" You get the idea -- think ifconfig_* in style. > Another shortcoming: ipv6 support... > > The patch below adds ipv6. > > One caveat, ping6 is used if a word in netwait_ip contains at least a > colon so hostnames in netwait_ip are always pinged using ipv4. > > {snip} Others will need to test IPv6 support -- I do not use it/have it available. It's a matter of opinion, but for IPv6 hosts/addresses, there should be a separate variable, probably netwait_ipv6 (or netwait_XXX_ipv6 if you go with the above ideal). The problem is that our existing ipv6 variables in rc.conf all conform with ipv6_*, so I'm not sure what people prefer. But then maybe the netwait_ip variable should be named netwait_*_ipv4... I'll let others hash this out, but I would prefer the former, since then you end up with something like this: netwait_em0_ipv4="4.2.2.1 4.2.2.2" netwait_em0_ipv6="fe80::202:b3ff:fe1e:8329" (And in this case you would want to test IPv4 connectivity *as well* as IPv6; two separate IP layers, thus both be tested separately; e.g. if 4.2.2.1 responds, don't just consider em0 working necessarily, because there may be daemons that are IPv6-centric that depend on packets flowing through em0. Those using tunnel brokers, however, probably won't benefit from this since netwait starts before such brokers/daemons). You get the idea. The problem is that this breaks the existing variable syntax and will upset a lot of existing users. Hmm... Not sure about this one. Gosh, I could really go either way. One final point, regarding ping6: ping6 lacks the -t argument that ping has. This is bad bad bad. In fact, I have to state up front that adding IPv6 support **should not** be done to this script until ping6 supports -t. I cannot stress this enough. The -t 1 piece is *very* important for proper behaviour. The nuances of the flag often come as a surprise to people. I can look at the ping code to figure out how -t works internally and probably submit a patch for ping6 that does this, but of course I have no way to test it. :-) IPv6 support is something that others will need to work on in general though -- I do not use it, so others are better-suited. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 12:52:18 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16E4B1065679 for ; Tue, 25 Oct 2011 12:52:18 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id B59128FC16 for ; Tue, 25 Oct 2011 12:52:17 +0000 (UTC) Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta09.westchester.pa.mail.comcast.net with comcast id p05E1h0011c6gX8590sHbs; Tue, 25 Oct 2011 12:52:17 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta23.westchester.pa.mail.comcast.net with comcast id p0sG1h00E1t3BNj3j0sGto; Tue, 25 Oct 2011 12:52:17 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id ED7A0102C1A; Tue, 25 Oct 2011 05:52:14 -0700 (PDT) Date: Tue, 25 Oct 2011 05:52:14 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20111025125214.GB87567@icarus.home.lan> References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> <4EA68DE5.80007@gmail.com> <4EA6A561.80405@quip.cz> <25920BDD-40FE-43D3-BC0A-A34A30DFC353@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25920BDD-40FE-43D3-BC0A-A34A30DFC353@gsoft.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Johan Hendriks , timp , freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 12:52:18 -0000 On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: > > On 25/10/2011, at 22:32, Miroslav Lachman wrote: > > > >> Well i did use the single user mode ! > >> And the safe mode ! > >> But they all gave me that error. > >> So the did load the loader.conf file. > > > > I think modules are loaded before displaying boot menu, where you can choose to boot in to single user mode. > > But you can enter the boot loader prompt, where you can unload already loaded modules or load new modules by its name, so you don't need to edit loader.conf for one time boot option. > > They aren't loaded before displaying the menu, but the list of modules to load is worked out then. > > If you want to boot without loading the modules listed in loader.conf you need to break into the loader and type.. > unload > boot -s > (or whatever options you want) Yup, correct. The person who said "single-user mode doesn't read loader.conf!" is absolutely incorrect. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 12:54:25 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76265106566B for ; Tue, 25 Oct 2011 12:54:25 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta01.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 221CE8FC0A for ; Tue, 25 Oct 2011 12:54:24 +0000 (UTC) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta01.westchester.pa.mail.comcast.net with comcast id ozok1h00327AodY510uRDu; Tue, 25 Oct 2011 12:54:25 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta19.westchester.pa.mail.comcast.net with comcast id p0uQ1h01Z1t3BNj3f0uQfJ; Tue, 25 Oct 2011 12:54:25 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0C6B3102C31; Tue, 25 Oct 2011 05:54:23 -0700 (PDT) Date: Tue, 25 Oct 2011 05:54:23 -0700 From: Jeremy Chadwick To: Claude Buisson Message-ID: <20111025125423.GA88097@icarus.home.lan> References: <4EA68C47.2070908@orange.fr> <4EA69B17.6020607@orange.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EA69B17.6020607@orange.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 12:54:25 -0000 On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote: > On 10/25/2011 12:52, Daniel O'Connor wrote: > > > >On 25/10/2011, at 20:45, Claude Buisson wrote: > >>When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to > >>ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to > >>atapicam (and reverting from cdN to acdN of course), vlc was OK again. > >> > >>It seems that I am not the only one having this kind of problem, as I found (for > >>example) this message on questions@ (for releng9): > >> > >>http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html > >> > >>Is this a known problem ? Is somebody working on it ? > > > >Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? > > > > Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC) > > > >It may be trying old style ATA ioctls based on the device name. > > > > VLC recognize the tracks and jump quickly from one to the following, without > playing it, and with a flow of messages: > > [0x2caf2a3c] cdda access error: Could not set block size > [0x2caf2a3c] cdda access error: cannot read sector nnnnn > > where the sector number is incremented, and then emit (2 times if I remenber): > > [0x2af28bc] es demux error: cannot peek > > Sorry for having ommited these messages in the previous mail. > > I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a > proposal by avg@ related to libxine: > > http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html > > These may not be the same problem, but I think they are related (a not so well > documented change in the kerm interface). You want atapicam(4). This is not the same thing as "options ATA_CAM". See /sys/conf/NOTES. Whether or not it works with audio CDs is unknown to me. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 13:08:30 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA6171065670; Tue, 25 Oct 2011 13:08:30 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 323EC8FC0C; Tue, 25 Oct 2011 13:08:29 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-211-94.lns20.adl6.internode.on.net [118.210.211.94]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9PD8JjH036638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Oct 2011 23:38:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <20111025125423.GA88097@icarus.home.lan> Date: Tue, 25 Oct 2011 23:38:18 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EA68C47.2070908@orange.fr> <4EA69B17.6020607@orange.fr> <20111025125423.GA88097@icarus.home.lan> To: Jeremy Chadwick X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.162 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Claude Buisson , FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 13:08:30 -0000 On 25/10/2011, at 23:24, Jeremy Chadwick wrote: >> These may not be the same problem, but I think they are related (a = not so well >> documented change in the kerm interface). >=20 > You want atapicam(4). This is not the same thing as "options = ATA_CAM". > See /sys/conf/NOTES. >=20 > Whether or not it works with audio CDs is unknown to me. atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on = CAM (as well as the ATA infrastructure). Hence they appear as /dev/cd0 = and so on. ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access = your audio CD that way.=20 I just tried and it ripped a CD fine using cdparanoia and cdcontrol = seemed to play it OK (although I don't have the analogue output of this = drive hooked up to the audio system). This is not to say that there isn't a bug in the ATA_CAM code :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 13:15:42 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35C90106564A for ; Tue, 25 Oct 2011 13:15:42 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id BDBCD8FC08 for ; Tue, 25 Oct 2011 13:15:41 +0000 (UTC) Received: by faar19 with SMTP id r19so702981faa.13 for ; Tue, 25 Oct 2011 06:15:40 -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=HKB11O3e3/0EwWGQwZ1ZjrMmrMmGpEfcMI07zTVcRgU=; b=TORtUSgnuEPREHze5BLjsNeVLM5kdPlopCq3F3uy2QvzPe/qdyXgYDo4OKMSYA62JC +gWoMCauqkOoPJLj/ysl0X1EYktU3pkPYla4nfaPeBMQTtkdP3Ycq4NNC7gHon70uDab /fkqcmahxNxBFZzVwkhIOjH89YyOOHhNIn4Fs= MIME-Version: 1.0 Received: by 10.223.76.135 with SMTP id c7mr11269070fak.14.1319547228800; Tue, 25 Oct 2011 05:53:48 -0700 (PDT) Received: by 10.152.24.67 with HTTP; Tue, 25 Oct 2011 05:53:48 -0700 (PDT) In-Reply-To: <20111025125214.GB87567@icarus.home.lan> References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> <4EA68DE5.80007@gmail.com> <4EA6A561.80405@quip.cz> <25920BDD-40FE-43D3-BC0A-A34A30DFC353@gsoft.com.au> <20111025125214.GB87567@icarus.home.lan> Date: Tue, 25 Oct 2011 16:53:48 +0400 Message-ID: From: Pavel Timofeev To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Johan Hendriks , freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 13:15:42 -0000 2011/10/25 Jeremy Chadwick > On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: > > > > On 25/10/2011, at 22:32, Miroslav Lachman wrote: > > > > > >> Well i did use the single user mode ! > > >> And the safe mode ! > > >> But they all gave me that error. > > >> So the did load the loader.conf file. > > > > > > I think modules are loaded before displaying boot menu, where you can > choose to boot in to single user mode. > > > But you can enter the boot loader prompt, where you can unload already > loaded modules or load new modules by its name, so you don't need to edit > loader.conf for one time boot option. > > > > They aren't loaded before displaying the menu, but the list of modules to > load is worked out then. > > > > If you want to boot without loading the modules listed in loader.conf you > need to break into the loader and type.. > > unload > > boot -s > > (or whatever options you want) > > Yup, correct. The person who said "single-user mode doesn't read > loader.conf!" is absolutely incorrect. > Sorry I thought so =( > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 13:18:31 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AD141065676 for ; Tue, 25 Oct 2011 13:18:31 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) by mx1.freebsd.org (Postfix) with ESMTP id EDBE58FC1A for ; Tue, 25 Oct 2011 13:18:30 +0000 (UTC) Received: from localhost ([92.162.133.50]) by mwinf5d09 with ME id p1JT1h00X15Q9dY031JUDe; Tue, 25 Oct 2011 15:18:29 +0200 X-ME-engine: default Message-ID: <4EA6B723.7090501@orange.fr> Date: Tue, 25 Oct 2011 15:18:27 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Jeremy Chadwick References: <4EA68C47.2070908@orange.fr> <4EA69B17.6020607@orange.fr> <20111025125423.GA88097@icarus.home.lan> In-Reply-To: <20111025125423.GA88097@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 13:18:31 -0000 On 10/25/2011 14:54, Jeremy Chadwick wrote: > On Tue, Oct 25, 2011 at 01:18:47PM +0200, Claude Buisson wrote: >> On 10/25/2011 12:52, Daniel O'Connor wrote: >>> >>> On 25/10/2011, at 20:45, Claude Buisson wrote: >>>> When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to >>>> ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to >>>> atapicam (and reverting from cdN to acdN of course), vlc was OK again. >>>> >>>> It seems that I am not the only one having this kind of problem, as I found (for >>>> example) this message on questions@ (for releng9): >>>> >>>> http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234737.html >>>> >>>> Is this a known problem ? Is somebody working on it ? >>> >>> Have you tried pointing VLC at /dev/cd0 when using ATA_CAM? >>> >> >> Of course yes ! (I even configured WITH_CDROM_DEVICE=/dev/cd1 when building VLC) >> >> >>> It may be trying old style ATA ioctls based on the device name. >>> >> >> VLC recognize the tracks and jump quickly from one to the following, without >> playing it, and with a flow of messages: >> >> [0x2caf2a3c] cdda access error: Could not set block size >> [0x2caf2a3c] cdda access error: cannot read sector nnnnn >> >> where the sector number is incremented, and then emit (2 times if I remenber): >> >> [0x2af28bc] es demux error: cannot peek >> >> Sorry for having ommited these messages in the previous mail. >> >> I found a PR 161760 about cdparanoia needing to be patched for 9.0 with CAM, a >> proposal by avg@ related to libxine: >> >> http://lists.freebsd.org/pipermail/freebsd-multimedia/2010-December/011414.html >> >> These may not be the same problem, but I think they are related (a not so well >> documented change in the kerm interface). > > You want atapicam(4). This is not the same thing as "options ATA_CAM". > See /sys/conf/NOTES. > > Whether or not it works with audio CDs is unknown to me. > I *know* the difference between atapicam and ATA_CAM ;-) I have done other tests on 8.X and 7.X, and found that audio CDs cannot be played with atapicam. BUT, I understood (wrongly ?) that ATA_CAM was the way to go starting with 9.X, which imply that the traditionnal acdN interface will disappear. A valid answer to my question may be: "we - kernel developpers - know about it, but we don't care, and the problem must be solved by the userland/applications developpers". With some obvious consequences on the upgrading or not upgrading of end users systems. Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 13:42:06 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1F4E1065670 for ; Tue, 25 Oct 2011 13:42:06 +0000 (UTC) (envelope-from freebsd@psconsult.nl) Received: from mx1.psconsult.nl (mx1.iaf.psconsult.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id 036AB8FC1E for ; Tue, 25 Oct 2011 13:42:05 +0000 (UTC) Received: from mx1.psconsult.nl (mx1.iaf.psconsult.nl [80.89.238.138] (may be forged)) by mx1.psconsult.nl (8.14.4/8.14.4) with ESMTP id p9PDfx4O097924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 25 Oct 2011 15:42:04 +0200 (CEST) (envelope-from freebsd@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.4/8.14.4/Submit) id p9PDfxR4097923 for freebsd-stable@freebsd.org; Tue, 25 Oct 2011 15:41:59 +0200 (CEST) (envelope-from freebsd@psconsult.nl) X-Authentication-Warning: mx1.psconsult.nl: paul set sender to freebsd@psconsult.nl using -f Date: Tue, 25 Oct 2011 15:41:59 +0200 From: Paul Schenkeveld To: freebsd-stable@freebsd.org Message-ID: <20111025134159.GA96607@psconsult.nl> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> <20111025010327.GA75437@icarus.home.lan> <20111025092012.GA41065@psconsult.nl> <20111025125108.GA87567@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111025125108.GA87567@icarus.home.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 13:42:06 -0000 On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: > On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: > > On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: > > > The one shortcoming of netwait is that it doesn't support waiting for > > > multiple NICs. Some people have dual-homed environments where they > > > really would like to wait for both, say, em0 and em1, to come up and be > > > functional before any more scripts are started. I left that as a > > > project for someone else, but it's something that should be added given > > > its importance. > > > > How would you like to see multiple interfaces implemented: > > > > - All interfaces must be up at the same time > > - Probe interfaces one by one, proceed to the next when an interface > > up or bail out when any interface stays down until the loop times > > out > > 1) Each interface should be checked in the order specified. > 2) Each ping probe should be done using that interface (ping -I). >From ping(8): -I iface Source multicast packets with the given interface address. This flag only applies if the ping destination is a multicast address. I believe that for unicast the interface used is determined by looking up the destination address in the routing table (unless overridden by a packet filter that changes the next hop). Another way to influence the next hop selection and the outgoing interface is using setfib(1) but apart from rc.d/jail I see no fib support in rc.conf at all. > 3) In the case of success, the next interface should be checked (e.g. go > back to step #1 but for the next interface defined. > 4) In the case of failure, output a message on-screen (similar to what > we already do) and continue on with the next interface check. > > So I imagine the variables for this would need to become something like: > > netwait_em0_ip="4.2.2.1 4.2.2.2" > netwait_em1_ip="192.168.1.1 192.168.1.2" > > You get the idea -- think ifconfig_* in style. This also suggests that ping can be forced to send out packets thru a certain interface which I think is misleading. Where I see the testing of multiple interfaces becoming important is in the case where interfaces are bonded using lagg(4). I usually have RTP disabled on server ports but started to see problems with ntpd and other services when I started to use LACP trunks. Paul Schenkeveld From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 14:42:08 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E244106564A for ; Tue, 25 Oct 2011 14:42:08 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id C09898FC15 for ; Tue, 25 Oct 2011 14:42:07 +0000 (UTC) Received: by eyd10 with SMTP id 10so665913eyd.13 for ; Tue, 25 Oct 2011 07:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1el6XWBEa+F/HNl//86j+r0Sup5/guESTCMQb0SfYp8=; b=s4pSIFUL2Wfvm3IsuWbGB2iZBp3hF7NvEj1QtwIvHMMvUmXkNYYEr4TsjIB0Ll+62o UAgmiCYGwQ2oxCHnFHqrN0MOJ7dgZ1Pg/7moT/+KdP2/bvScaQTlKqocF/5bZh5m5Kba 4+gq/rHJ9aOd+xBCqPkeqsWAUufLNQU9pLZ7k= Received: by 10.14.46.132 with SMTP id r4mr3368293eeb.137.1319553726602; Tue, 25 Oct 2011 07:42:06 -0700 (PDT) Received: from [192.168.50.106] (double-l.xs4all.nl. [80.126.205.144]) by mx.google.com with ESMTPS id w58sm71015502eeb.4.2011.10.25.07.42.06 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 07:42:06 -0700 (PDT) Message-ID: <4EA6CABB.3090008@gmail.com> Date: Tue, 25 Oct 2011 16:42:03 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <4EA67991.5020604@gmail.com> <1319536366754-4935645.post@n5.nabble.com> <4EA68DE5.80007@gmail.com> <4EA6A561.80405@quip.cz> <25920BDD-40FE-43D3-BC0A-A34A30DFC353@gsoft.com.au> <20111025125214.GB87567@icarus.home.lan> In-Reply-To: <20111025125214.GB87567@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: From 8-stable to 9.0 RC1 iscsi panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 14:42:08 -0000 Jeremy Chadwick schreef: > On Tue, Oct 25, 2011 at 10:46:55PM +1030, Daniel O'Connor wrote: >> On 25/10/2011, at 22:32, Miroslav Lachman wrote: >>>> Well i did use the single user mode ! >>>> And the safe mode ! >>>> But they all gave me that error. >>>> So the did load the loader.conf file. >>> I think modules are loaded before displaying boot menu, where you can choose to boot in to single user mode. >>> But you can enter the boot loader prompt, where you can unload already loaded modules or load new modules by its name, so you don't need to edit loader.conf for one time boot option. >> They aren't loaded before displaying the menu, but the list of modules to load is worked out then. >> >> If you want to boot without loading the modules listed in loader.conf you need to break into the loader and type.. >> unload >> boot -s >> (or whatever options you want) > Yup, correct. The person who said "single-user mode doesn't read > loader.conf!" is absolutely incorrect. > I really did select number 4 after the reboot, i even rebooted multiple times! I can imagine myself missing number 4 reading the options and not hitting number 4 within the 10 seconds the first time, but not the second and third time. Or my keyboard did not work at the boot loader menu, wich i can not test now because it is recompiling all my ports and i do not want to interupt a working deamon .. But anyhow it gave me the above error! I did not think about going into the loader and unload the iscsi module, so i did remove it with the live cd using fixit from the laoder.conf file. Now all is fine. regards Johan Hendriks From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 15:01:34 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D50DB1065670 for ; Tue, 25 Oct 2011 15:01:34 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp02.smtpout.orange.fr [80.12.242.124]) by mx1.freebsd.org (Postfix) with ESMTP id 525E08FC13 for ; Tue, 25 Oct 2011 15:01:33 +0000 (UTC) Received: from localhost ([92.162.133.50]) by mwinf5d56 with ME id p31V1h00F15Q9dY0331Vtc; Tue, 25 Oct 2011 17:01:33 +0200 X-ME-engine: default Message-ID: <4EA6CF49.7030603@orange.fr> Date: Tue, 25 Oct 2011 17:01:29 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Daniel O'Connor References: <4EA68C47.2070908@orange.fr> <4EA69B17.6020607@orange.fr> <20111025125423.GA88097@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 15:01:34 -0000 On 10/25/2011 15:08, Daniel O'Connor wrote: > > On 25/10/2011, at 23:24, Jeremy Chadwick wrote: >>> These may not be the same problem, but I think they are related (a not so well >>> documented change in the kerm interface). >> >> You want atapicam(4). This is not the same thing as "options ATA_CAM". >> See /sys/conf/NOTES. >> >> Whether or not it works with audio CDs is unknown to me. > > atapicam is a bridge for the old ATA code to put ATAPI devices _only_ on CAM (as well as the ATA infrastructure). Hence they appear as /dev/cd0 and so on. > As I said: I know it (after 16 years of FreeBSD use ...) > ATA_CAM puts _all_ ATA devices on CAM, so you should be able to access your audio CD that way. > > I just tried and it ripped a CD fine using cdparanoia and cdcontrol seemed to play it OK (although I don't have the analogue output of this drive hooked up to the audio system). > I just played a CD with cdcontrol on a ATA_CAMed 9.0 system from Sept 25 (hooked to the audio), but do not know what is proven that way: VLC see the tracks of the audio CD and may even identifiy them with cddb, but cannot play them (see the error messages). So my current conclusion (?) is that the problem lies with the userland librairies (cdda, ..) > This is not to say that there isn't a bug in the ATA_CAM code :) > I will do another test on 9.0 (after rebuilding the ports), and eventually get rid of ATA_CAM and wait (im)patiently for a knowledgeable one to have a look at the problem. If this is a real problem, I may hope that it will appear after the release of 9.0 and its use in the real world. > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 15:02:36 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4B1D1065673 for ; Tue, 25 Oct 2011 15:02:36 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id A31F58FC18 for ; Tue, 25 Oct 2011 15:02:36 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E261D28423; Tue, 25 Oct 2011 17:02:34 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A1E7628422; Tue, 25 Oct 2011 17:02:33 +0200 (CEST) Message-ID: <4EA6CF88.3050600@quip.cz> Date: Tue, 25 Oct 2011 17:02:32 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Paul Schenkeveld References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> <20111025010327.GA75437@icarus.home.lan> <20111025092012.GA41065@psconsult.nl> <20111025125108.GA87567@icarus.home.lan> <20111025134159.GA96607@psconsult.nl> In-Reply-To: <20111025134159.GA96607@psconsult.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 15:02:37 -0000 Paul Schenkeveld wrote: > On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: >> On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: >>> On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: >>>> The one shortcoming of netwait is that it doesn't support waiting for >>>> multiple NICs. Some people have dual-homed environments where they >>>> really would like to wait for both, say, em0 and em1, to come up and be >>>> functional before any more scripts are started. I left that as a >>>> project for someone else, but it's something that should be added given >>>> its importance. >>> >>> How would you like to see multiple interfaces implemented: >>> >>> - All interfaces must be up at the same time >>> - Probe interfaces one by one, proceed to the next when an interface >>> up or bail out when any interface stays down until the loop times >>> out >> >> 1) Each interface should be checked in the order specified. >> 2) Each ping probe should be done using that interface (ping -I). > >> From ping(8): > > -I iface > Source multicast packets with the given interface address. This > flag only applies if the ping destination is a multicast address. > > I believe that for unicast the interface used is determined by looking > up the destination address in the routing table (unless overridden by a > packet filter that changes the next hop). Another way to influence the > next hop selection and the outgoing interface is using setfib(1) but > apart from rc.d/jail I see no fib support in rc.conf at all. OT: Unfortunately there are two PRs with patches to add setfib support to rc.subr, but both of them are laying under the dust without attention of committers. conf/132483 conf/132851 I tried to bring it to attention in freebsd-rc@ without any luck. (same as my attempt to add support for cpuset conf/142434). So we have features / tools without centralized support in rc.subr and if anybody want to use them, must do it by some hacky ways in rc.local etc. http://lists.freebsd.org/pipermail/freebsd-rc/2010-January/001816.html Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 17:04:07 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8EBD106566C for ; Tue, 25 Oct 2011 17:04:07 +0000 (UTC) (envelope-from doug@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by mx1.freebsd.org (Postfix) with ESMTP id 874608FC15 for ; Tue, 25 Oct 2011 17:04:07 +0000 (UTC) Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id p9PH46EU015901 for ; Tue, 25 Oct 2011 13:04:06 -0400 (EDT) (envelope-from doug@fledge.watson.org) Received: from localhost (doug@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id p9PH46S1015896 for ; Tue, 25 Oct 2011 13:04:06 -0400 (EDT) (envelope-from doug@fledge.watson.org) Date: Tue, 25 Oct 2011 13:04:06 -0400 (EDT) From: doug To: freebsd-stable@freebsd.org In-Reply-To: <4EA6CF88.3050600@quip.cz> Message-ID: References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan> <20111025010327.GA75437@icarus.home.lan> <20111025092012.GA41065@psconsult.nl> <20111025125108.GA87567@icarus.home.lan> <20111025134159.GA96607@psconsult.nl> <4EA6CF88.3050600@quip.cz> 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.3 (fledge.watson.org [127.0.0.1]); Tue, 25 Oct 2011 13:04:06 -0400 (EDT) Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: doug@safeport.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 17:04:08 -0000 On Tue, 25 Oct 2011, Miroslav Lachman wrote: > Paul Schenkeveld wrote: >> On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote: >>> On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote: >>>> On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote: >>>>> The one shortcoming of netwait is that it doesn't support waiting for >>>>> multiple NICs. Some people have dual-homed environments where they >>>>> really would like to wait for both, say, em0 and em1, to come up and be >>>>> functional before any more scripts are started. I left that as a >>>>> project for someone else, but it's something that should be added given >>>>> its importance. >>>> >>>> How would you like to see multiple interfaces implemented: >>>> >>>> - All interfaces must be up at the same time >>>> - Probe interfaces one by one, proceed to the next when an interface >>>> up or bail out when any interface stays down until the loop times >>>> out >>> >>> 1) Each interface should be checked in the order specified. >>> 2) Each ping probe should be done using that interface (ping -I). >> >>> From ping(8): >> >> -I iface >> Source multicast packets with the given interface address. This >> flag only applies if the ping destination is a multicast address. >> >> I believe that for unicast the interface used is determined by looking >> up the destination address in the routing table (unless overridden by a >> packet filter that changes the next hop). Another way to influence the >> next hop selection and the outgoing interface is using setfib(1) but >> apart from rc.d/jail I see no fib support in rc.conf at all. > > OT: > Unfortunately there are two PRs with patches to add setfib support to > rc.subr, but both of them are laying under the dust without attention of > committers. > conf/132483 conf/132851 > > I tried to bring it to attention in freebsd-rc@ without any luck. (same as my > attempt to add support for cpuset conf/142434). So we have features / tools > without centralized support in rc.subr and if anybody want to use them, must > do it by some hacky ways in rc.local etc. > http://lists.freebsd.org/pipermail/freebsd-rc/2010-January/001816.html > I have not done any debugging, but it seems to me this may be a serialization issue. For me it almost always occurs on MP systems. I have an 8-cpu system that never starts NTP correctly, a 2-cpu laptop that mostly never does. I have never experienced this with a single processor system. My fix is simply to pick a number of geographically close open NTP servers. From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 20:53:01 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AC3B1065741 for ; Tue, 25 Oct 2011 20:53:01 +0000 (UTC) (envelope-from carlopmart@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 35D9B8FC18 for ; Tue, 25 Oct 2011 20:53:00 +0000 (UTC) Received: by wwi18 with SMTP id 18so1421592wwi.31 for ; Tue, 25 Oct 2011 13:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=+Mtu4VllanwApUSNEJcLH3UZbyKoz20uZk8z4dSs0G8=; b=q2FtX9k8nhbgrzZGpsQGV7HcmRn7/77s/lOBwOSSnZiU597+Y87OVPY3BdFzOU0vF+ LVKM/TR2XYTwrmAOEbrkUsk5czHGjxcS3t/KWXPgCMk8sWzk52R4WwZljOooVf/NpImN Dxi858BmDjmvqrI7Bbg3XHwGgvbPx4mFj22i4= Received: by 10.227.202.143 with SMTP id fe15mr5878142wbb.25.1319575980079; Tue, 25 Oct 2011 13:53:00 -0700 (PDT) Received: from silmaril.hpulabs.org (69.Red-83-43-25.dynamicIP.rima-tde.net. [83.43.25.69]) by mx.google.com with ESMTPS id x40sm41018232wbn.19.2011.10.25.13.52.57 (version=SSLv3 cipher=OTHER); Tue, 25 Oct 2011 13:52:58 -0700 (PDT) Message-ID: <4EA721A7.8050905@gmail.com> Date: Tue, 25 Oct 2011 22:52:55 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 20:53:01 -0000 Hi all, I have installed one FreeBSD 9.0-RC1 host to run different services (dns, smtp and www only) using jails. This host has two physical nics: em0 and em1. em0 is assigned to pyhiscal host, and I would like to assign em1 to jails. But em0 and em1 are on different networks: em0 is on 192.168.1.0/24 and em1 in 192.168.2.0/29. I have setup one jail using ezjail. My first surprise is that ezjail only installs -RELEASE versions and not RC versions. Ok, I supouse that it is normal. But my first question is: can I install a FreeBSD 8.2 jail under a FreeBSD 9.0 host?? And the real question: How do I need to configure network under this jail to access it? I have configured ifconfig param for em1 on host's rc.conf, but what about the default route under this jail?? I thought to use pf rules, but I am not sure. Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 21:22:04 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0E3F106566B; Tue, 25 Oct 2011 21:22:04 +0000 (UTC) (envelope-from tomelite82@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 7BA2D8FC08; Tue, 25 Oct 2011 21:22:04 +0000 (UTC) Received: by ggnq2 with SMTP id q2so1197200ggn.13 for ; Tue, 25 Oct 2011 14:22: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=Kbi/fzghKC9XyG9iurZ6SfP/8uJup/V08JGXuVcWENY=; b=iaiGMvNaYO6/lyaC++nckmOB/4p/L/V4+LGqGvDXx5OBfRWt9prVUzZyrKSK94AUqo Bb7r8yn6GD5q1DxhAhZyNR4WtWbhFHM64icEnxI4h+QQfF4RbZVuhKDK7qrTxDyTIdnN 1rB7xImxnGGAeQjaN3v22t4WgtSaKKyZXIdjk= MIME-Version: 1.0 Received: by 10.151.87.19 with SMTP id p19mr5795603ybl.71.1319577723792; Tue, 25 Oct 2011 14:22:03 -0700 (PDT) Sender: tomelite82@gmail.com Received: by 10.151.44.14 with HTTP; Tue, 25 Oct 2011 14:22:03 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 Oct 2011 14:22:03 -0700 X-Google-Sender-Auth: SQawIKIy35MXcWVzrELv13mgS28 Message-ID: From: Qing Li To: freebsd-net@freebsd.org, FreeBSD Stable List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Qing Li Subject: FreeBSD 9 IPv6 conformance test report X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 21:22:05 -0000 Since I have been receiving private reports on the test failures, I thought I just post the test report as executed against the upcoming FreeBSD 9.0 release in my own setup, so you can see where the baseline is. More test reports will be posted here. =A0 =A0 =A0 =A0http://people.freebsd.org/~qingli/ct-freebsd-9/ I am going over each failure and providing the fix. Please let me know if you already have a suggested patch that you are willing to share. Thanks. -- Qing From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 22:38:33 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36FC5106566C for ; Tue, 25 Oct 2011 22:38:33 +0000 (UTC) (envelope-from gkontos.mail@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 049038FC12 for ; Tue, 25 Oct 2011 22:38:32 +0000 (UTC) Received: by iaky10 with SMTP id y10so1693166iak.13 for ; Tue, 25 Oct 2011 15:38:32 -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:content-transfer-encoding; bh=nHeJAAxTWwzCoA1vCcroZGjsBRVvZ+VF/Ws8uK/tm8Q=; b=HDflPgbP3BIzwG5PjirYtGqu2eNI3gLl/BurFolrvYvqKtv6ksL6O9z/qvt+ioYPIk TT1wKwEDVaH7qtKXgKZVkEz1Gad0+JHzxYwYPK6Xb9LDSBtZYFeT4OQN5EM9vTfeUHUH 4Pg8gxfKiiiaYj9AmCTmhMUTRKv6geLEQKXtU= MIME-Version: 1.0 Received: by 10.231.27.203 with SMTP id j11mr968496ibc.10.1319582311515; Tue, 25 Oct 2011 15:38:31 -0700 (PDT) Received: by 10.231.34.140 with HTTP; Tue, 25 Oct 2011 15:38:31 -0700 (PDT) In-Reply-To: <4EA721A7.8050905@gmail.com> References: <4EA721A7.8050905@gmail.com> Date: Wed, 26 Oct 2011 01:38:31 +0300 Message-ID: From: George Kontostanos To: carlopmart Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2011 22:38:33 -0000 On Tue, Oct 25, 2011 at 11:52 PM, carlopmart wrote: > Hi all, > > =A0I have installed one FreeBSD 9.0-RC1 host to run different services (d= ns, > smtp and www only) using jails. This host has two physical nics: em0 and > em1. em0 is assigned to pyhiscal host, and I would like to assign em1 to > jails. But em0 and em1 are on different networks: em0 is on 192.168.1.0/2= 4 > and em1 in 192.168.2.0/29. > > =A0I have setup one jail using ezjail. My first surprise is that ezjail o= nly > installs -RELEASE versions and not RC versions. Ok, I supouse that it is > normal. But my first question is: can I install a FreeBSD 8.2 jail under = a > FreeBSD 9.0 host?? ezjail doesn't necessarily install a release version. < ezjail-admin update -p -i > will install the basejail from your source. > =A0And the real question: How do I need to configure network under this j= ail > to access it? I have configured ifconfig param for em1 on host's rc.conf, > but what about the default route under this jail?? I thought to use pf > rules, but I am not sure. gateway_enable=3D"YES" should take care of this. > > Thanks. > -- > CL Martinez > carlopmart {at} gmail {d0t} com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Regards --=20 George Kontostanos aisecure.net From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 01:12:02 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E442E1065675 for ; Wed, 26 Oct 2011 01:12:02 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id A63138FC14 for ; Wed, 26 Oct 2011 01:12:02 +0000 (UTC) Received: from baby-jane.lamaiziere.net (63.9.74.86.rev.sfr.net [86.74.9.63]) by smtp.lamaiziere.net (Postfix) with ESMTPA id E2919FAA31A5; Wed, 26 Oct 2011 03:12:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 78E0E730D8; Wed, 26 Oct 2011 03:12:04 +0200 (CEST) Date: Wed, 26 Oct 2011 03:12:02 +0200 From: Patrick Lamaiziere To: freebsd-stable@freebsd.org Message-ID: <20111026031202.2a8780f9@davenulle.org> In-Reply-To: <4EA721A7.8050905@gmail.com> References: <4EA721A7.8050905@gmail.com> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: carlopmart Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 01:12:03 -0000 Le Tue, 25 Oct 2011 22:52:55 +0200, carlopmart a écrit : Hello, > I have installed one FreeBSD 9.0-RC1 host to run different services > (dns, smtp and www only) using jails. This host has two physical > nics: em0 and em1. em0 is assigned to pyhiscal host, and I would like > to assign em1 to jails. But em0 and em1 are on different networks: > em0 is on 192.168.1.0/24 and em1 in 192.168.2.0/29. > > I have setup one jail using ezjail. My first surprise is that > ezjail only installs -RELEASE versions and not RC versions. Ok, I > supouse that it is normal. But my first question is: can I install a > FreeBSD 8.2 jail under a FreeBSD 9.0 host?? You may run 8.2 installed ports on 9.0 by using the port /usr/ports/misc/compat8x/ But I suggest to upgrade the port ASAP. > And the real question: How do I need to configure network under > this jail to access it? I have configured ifconfig param for em1 on > host's rc.conf, but what about the default route under this jail?? I > thought to use pf rules, but I am not sure. jail enforces the use of the jail IP address in the jail, but that's all. Just enable routing on the host. Also be sure that the host's daemons don't bind on the jail IP address, as explained in the man page of jail (Setting up the Host Environment). Regards. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 01:56:56 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F22A5106567C for ; Wed, 26 Oct 2011 01:56:56 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 857688FC20 for ; Wed, 26 Oct 2011 01:56:56 +0000 (UTC) Received: by bkbzt4 with SMTP id zt4so1271977bkb.13 for ; Tue, 25 Oct 2011 18:56:55 -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; bh=ADD9hi/LSB4anBLaaDctCSkoFlDbOT4vFbtqqXx9G9s=; b=rpgvT/exwDm3q2UAaVZ4SkT5PeoGdeI0FudQGjyycQxaSfGLojjuDcrpGspuMTpD37 KrZlAhpB5fgz5Z5qrwPQr496u4H1+A6nGY8aAFeFpXAriKwsjsMkD1quTTebCYDqt3JA UnBIdkvYLnwkO65GDByVjNeXt0a2LXLhjRs9s= MIME-Version: 1.0 Received: by 10.204.7.199 with SMTP id e7mr22235867bke.40.1319592509793; Tue, 25 Oct 2011 18:28:29 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.204.39.12 with HTTP; Tue, 25 Oct 2011 18:28:29 -0700 (PDT) In-Reply-To: <4EA68C47.2070908@orange.fr> References: <4EA68C47.2070908@orange.fr> Date: Tue, 25 Oct 2011 18:28:29 -0700 X-Google-Sender-Auth: 778NmCsu1WBCwUrBeMD9kn6VSAY Message-ID: From: Craig Rodrigues To: Claude Buisson Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 01:56:57 -0000 On Tue, Oct 25, 2011 at 3:15 AM, Claude Buisson wrote: > Hi, > > When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to > ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to > atapicam (and reverting from cdN to acdN of course), vlc was OK again. Hi, Would vlc have worked if, while ATA_CAM was enabled, there was a symlink so that /dev/acd0 -> cd0 ? -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 06:09:12 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57F6B106564A for ; Wed, 26 Oct 2011 06:09:12 +0000 (UTC) (envelope-from legolas@legolasweb.nl) Received: from smtp02.mail.pcextreme.nl (smtp02.mail.pcextreme.nl [IPv6:2a00:f10:101:101:0:25:587:2]) by mx1.freebsd.org (Postfix) with ESMTP id E95B68FC12 for ; Wed, 26 Oct 2011 06:09:11 +0000 (UTC) Received: from localhost (webmail02.mail.pcextreme.nl [109.72.87.146]) by smtp02.mail.pcextreme.nl (Postfix) with ESMTP id A198CDEB51 for ; Wed, 26 Oct 2011 08:09:10 +0200 (CEST) Received: from webmail.pcextreme.nl (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 736B16300B1 for ; Wed, 26 Oct 2011 08:09:10 +0200 (CEST) Received: from 83.87.233.15 (SquirrelMail authenticated user legolas@legolasweb.nl) by webmail.pcextreme.nl with HTTP; Wed, 26 Oct 2011 08:09:10 +0200 Message-ID: <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl> In-Reply-To: <20111026031202.2a8780f9@davenulle.org> References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> Date: Wed, 26 Oct 2011 08:09:10 +0200 From: legolas@legolasweb.nl To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 06:09:12 -0000 >> I have setup one jail using ezjail. My first surprise is that >> ezjail only installs -RELEASE versions and not RC versions. Ok, I >> supouse that it is normal. But my first question is: can I install a >> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? I have upgraded my ezjails using something like: env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r 9.0-RC1 upgrade install This is some hassle, for example, one has to upgrade /etc and /var in /usr/jails/newjail by hand. (And maybe even more, not completely sure there.) From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 07:51:27 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DA11106566C for ; Wed, 26 Oct 2011 07:51:27 +0000 (UTC) (envelope-from carlopmart@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 A51088FC0C for ; Wed, 26 Oct 2011 07:51:26 +0000 (UTC) Received: by wyi40 with SMTP id 40so1774802wyi.13 for ; Wed, 26 Oct 2011 00:51:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=241JM8aW3OxrjIRj9T17O+axZ5/bENyRjA+qJFyfVdk=; b=wCF8zMTMOzLXwH6nVmx7ETYxlnx2nBuiJ8DRaQd9yHq6GYcsrCPEaPiv+I7zSVMEa1 kuNrPuG5wOT9xxPjDBz4G+4tognZwnXSh9C62mhf7FrkK3e0eL/AKcR3HNrTilNIJi3n 1MTtPL/OTiRn8JxzpyL4/8meMc67WVLWKXDbc= Received: by 10.227.58.17 with SMTP id e17mr8086195wbh.18.1319615485477; Wed, 26 Oct 2011 00:51:25 -0700 (PDT) Received: from silmaril.hpulabs.org (46.Red-88-24-104.staticIP.rima-tde.net. [88.24.104.46]) by mx.google.com with ESMTPS id b5sm1553597wbh.4.2011.10.26.00.51.23 (version=SSLv3 cipher=OTHER); Wed, 26 Oct 2011 00:51:24 -0700 (PDT) Message-ID: <4EA7BBF9.3@gmail.com> Date: Wed, 26 Oct 2011 09:51:21 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl> In-Reply-To: <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 07:51:27 -0000 On 10/26/2011 08:09 AM, legolas@legolasweb.nl wrote: > >>> I have setup one jail using ezjail. My first surprise is that >>> ezjail only installs -RELEASE versions and not RC versions. Ok, I >>> supouse that it is normal. But my first question is: can I install a >>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? > > I have upgraded my ezjails using something like: > env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r 9.0-RC1 > upgrade install > > This is some hassle, for example, one has to upgrade /etc and /var in > /usr/jails/newjail by hand. (And maybe even more, not completely sure > there.) > is not possible to update the jail using "ejzail-admin update -u" instead of use freebsd-update directly?? -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 07:53:14 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1892106564A for ; Wed, 26 Oct 2011 07:53:14 +0000 (UTC) (envelope-from carlopmart@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 85C378FC12 for ; Wed, 26 Oct 2011 07:53:14 +0000 (UTC) Received: by wyi40 with SMTP id 40so1776659wyi.13 for ; Wed, 26 Oct 2011 00:53:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1fwwuC/NJxmhbJgW8XzOypyhJPp8QrWRFFlt0gRXBoI=; b=sJJN+9SGux2sU+MvavxkNdqhNBdGLkPuBA2ivcmTHkiaBAByWHBxWmROEAxq5Nq4lX y21r4BBYgtLBG7TZyiPnWsciv3d49msvZdG0hl8dzA2lJQ7nBcMjW0rDVOS0682iP4cC uWc5aUVYJ+tC1ozPJlVYVeIKeNiu1sv4K6QH0= Received: by 10.216.82.136 with SMTP id o8mr9648104wee.31.1319615593465; Wed, 26 Oct 2011 00:53:13 -0700 (PDT) Received: from silmaril.hpulabs.org (46.Red-88-24-104.staticIP.rima-tde.net. [88.24.104.46]) by mx.google.com with ESMTPS id eu16sm1555262wbb.7.2011.10.26.00.53.11 (version=SSLv3 cipher=OTHER); Wed, 26 Oct 2011 00:53:12 -0700 (PDT) Message-ID: <4EA7BC66.3090304@gmail.com> Date: Wed, 26 Oct 2011 09:53:10 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> In-Reply-To: <20111026031202.2a8780f9@davenulle.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 07:53:15 -0000 On 10/26/2011 03:12 AM, Patrick Lamaiziere wrote: > Le Tue, 25 Oct 2011 22:52:55 +0200, > carlopmart a écrit : > > Hello, > >> I have installed one FreeBSD 9.0-RC1 host to run different services >> (dns, smtp and www only) using jails. This host has two physical >> nics: em0 and em1. em0 is assigned to pyhiscal host, and I would like >> to assign em1 to jails. But em0 and em1 are on different networks: >> em0 is on 192.168.1.0/24 and em1 in 192.168.2.0/29. >> >> I have setup one jail using ezjail. My first surprise is that >> ezjail only installs -RELEASE versions and not RC versions. Ok, I >> supouse that it is normal. But my first question is: can I install a >> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? > > You may run 8.2 installed ports on 9.0 by using the port > /usr/ports/misc/compat8x/ > > But I suggest to upgrade the port ASAP. > >> And the real question: How do I need to configure network under >> this jail to access it? I have configured ifconfig param for em1 on >> host's rc.conf, but what about the default route under this jail?? I >> thought to use pf rules, but I am not sure. > > jail enforces the use of the jail IP address in the jail, but that's > all. Just enable routing on the host. > But, that is not possible. Between host and jail exists a firewall ... I can't do simple routing with the host. Maybe a posible solution is to use policy source routing ?? -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 07:54:44 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 386121065784 for ; Wed, 26 Oct 2011 07:54:44 +0000 (UTC) (envelope-from carlopmart@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 BDAB58FC1B for ; Wed, 26 Oct 2011 07:54:43 +0000 (UTC) Received: by wyi40 with SMTP id 40so1778181wyi.13 for ; Wed, 26 Oct 2011 00:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1702w4XkfYULwZ+BtjjAzhxNwy3nDx4/Yi2FGXQRbBY=; b=cIRgnQiIFergVkiy8SypWjfzZegD3wBKQf57PCedn8dT8OprqLXuv1qkoI9CpLHSTI CySJVGyMSCePnbMFamsQqow9MuAPyB5alW1u3tMOh01jhBRvu7zpUVZ/cQ2xV/qT45bq 5kCUiiaOWhM4CUOYHpkKPUcS1NzDCvj/Mipfs= Received: by 10.227.197.20 with SMTP id ei20mr8236342wbb.26.1319615682639; Wed, 26 Oct 2011 00:54:42 -0700 (PDT) Received: from silmaril.hpulabs.org (46.Red-88-24-104.staticIP.rima-tde.net. [88.24.104.46]) by mx.google.com with ESMTPS id x40sm1531721wbn.19.2011.10.26.00.54.40 (version=SSLv3 cipher=OTHER); Wed, 26 Oct 2011 00:54:41 -0700 (PDT) Message-ID: <4EA7BCBF.6030001@gmail.com> Date: Wed, 26 Oct 2011 09:54:39 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA721A7.8050905@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 07:54:44 -0000 On 10/26/2011 12:38 AM, George Kontostanos wrote: > On Tue, Oct 25, 2011 at 11:52 PM, carlopmart wrote: >> Hi all, >> >> I have installed one FreeBSD 9.0-RC1 host to run different services (dns, >> smtp and www only) using jails. This host has two physical nics: em0 and >> em1. em0 is assigned to pyhiscal host, and I would like to assign em1 to >> jails. But em0 and em1 are on different networks: em0 is on 192.168.1.0/24 >> and em1 in 192.168.2.0/29. >> >> I have setup one jail using ezjail. My first surprise is that ezjail only >> installs -RELEASE versions and not RC versions. Ok, I supouse that it is >> normal. But my first question is: can I install a FreeBSD 8.2 jail under a >> FreeBSD 9.0 host?? > > ezjail doesn't necessarily install a release version.< ezjail-admin > update -p -i> will install the basejail from your source. I have installed this jail using "ezjail-admin install". I can't compile source every time that I need to do an update in this host ... > >> And the real question: How do I need to configure network under this jail >> to access it? I have configured ifconfig param for em1 on host's rc.conf, >> but what about the default route under this jail?? I thought to use pf >> rules, but I am not sure. > > gateway_enable="YES" > should take care of this. In host or in the jail?? > >> >> Thanks. >> -- >> CL Martinez >> carlopmart {at} gmail {d0t} com >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > Regards > -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 08:09:04 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99F72106566C for ; Wed, 26 Oct 2011 08:09:04 +0000 (UTC) (envelope-from legolas@legolasweb.nl) Received: from smtp02.mail.pcextreme.nl (smtp02.mail.pcextreme.nl [IPv6:2a00:f10:101:101:0:25:587:2]) by mx1.freebsd.org (Postfix) with ESMTP id 336478FC14 for ; Wed, 26 Oct 2011 08:09:04 +0000 (UTC) Received: from localhost (webmail01.mail.pcextreme.nl [109.72.87.145]) by smtp02.mail.pcextreme.nl (Postfix) with ESMTP id 1FFA1DEB9C for ; Wed, 26 Oct 2011 10:09:03 +0200 (CEST) Received: from webmail.pcextreme.nl (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id EA9D344007A for ; Wed, 26 Oct 2011 10:09:02 +0200 (CEST) Received: from 83.87.233.15 (SquirrelMail authenticated user legolas@legolasweb.nl) by webmail.pcextreme.nl with HTTP; Wed, 26 Oct 2011 10:09:03 +0200 Message-ID: <9fefbda9bf6d16437fc7ad6c5445fe12.squirrel@webmail.pcextreme.nl> In-Reply-To: <4EA7BBF9.3@gmail.com> References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl> <4EA7BBF9.3@gmail.com> Date: Wed, 26 Oct 2011 10:09:03 +0200 From: legolas@legolasweb.nl To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 08:09:04 -0000 > On 10/26/2011 08:09 AM, legolas@legolasweb.nl wrote: >> >>>> I have setup one jail using ezjail. My first surprise is that >>>> ezjail only installs -RELEASE versions and not RC versions. Ok, I >>>> supouse that it is normal. But my first question is: can I install a >>>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? >> >> I have upgraded my ezjails using something like: >> env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r >> 9.0-RC1 >> upgrade install >> >> This is some hassle, for example, one has to upgrade /etc and /var in >> /usr/jails/newjail by hand. (And maybe even more, not completely sure >> there.) >> > > is not possible to update the jail using "ejzail-admin update -u" > instead of use freebsd-update directly?? > Updating can be done, upgrading not. (Thus, a security update can be done, a full version not, if I understand it correctly.) This functionality exists (prematurely) in CVS: https://erdgeist.org/cvsweb/ezjail/ezjail-admin.diff?r1=1.263&r2=1.264&f=h From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 08:33:16 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84CD51065670 for ; Wed, 26 Oct 2011 08:33:16 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp03.smtpout.orange.fr [80.12.242.125]) by mx1.freebsd.org (Postfix) with ESMTP id 1D8828FC14 for ; Wed, 26 Oct 2011 08:33:15 +0000 (UTC) Received: from localhost ([92.136.19.77]) by mwinf5d05 with ME id pLZD1h0091fmhbQ03LZDpP; Wed, 26 Oct 2011 10:33:14 +0200 X-ME-engine: default Message-ID: <4EA7C5C9.8010903@orange.fr> Date: Wed, 26 Oct 2011 10:33:13 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Craig Rodrigues References: <4EA68C47.2070908@orange.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 08:33:16 -0000 On 10/26/2011 03:28, Craig Rodrigues wrote: > On Tue, Oct 25, 2011 at 3:15 AM, Claude Buisson wrote: >> Hi, >> >> When upgrading a system to 8.2-STABLE, I switched my kernel from atapicam to >> ATA_CAM, and found that vlc could not play audio CDs anymore. Reverting to >> atapicam (and reverting from cdN to acdN of course), vlc was OK again. > > Hi, > > Would vlc have worked if, while ATA_CAM was enabled, > there was a symlink so that /dev/acd0 -> cd0 ? Just to be sure, I just made the test, and the answer is: NO I have already written that vlc writes a susccession of messages [0x2caf2a3c] cdda access error: Could not set block size [0x2caf2a3c] cdda access error: cannot read sector nnnnn incrementing each time the sector number. So I infer that vlc cannot set the correct (audio specific) sector size for the cam device. Thanks for your attention. Claude Buisson P.S. As I can see reading GENERIC, ATA_CAM will be the default for 9.X so there is a risk of complaints from FreeBSD workstation users (who cares ?) after the release.. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 08:33:28 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 375EF1065744 for ; Wed, 26 Oct 2011 08:33:28 +0000 (UTC) (envelope-from carlopmart@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 BD2AD8FC08 for ; Wed, 26 Oct 2011 08:33:27 +0000 (UTC) Received: by wyi40 with SMTP id 40so1822941wyi.13 for ; Wed, 26 Oct 2011 01:33:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=73qP4qv70qCo8/Tr+l3E2bhq2YMx3eiTS3j1LNyKiJA=; b=qPRjBzMb0dSh+Cp3uAOhO/r3zWmILrWet2+XatfA1YAdegwPxIs8JiPIQ86DbQqeC1 DgZH3Fwmn7/+U33HWeN8bc8QDwal1ZW5q5REMY4ixQaVXlgOr2DV9T1e3y4Wn2hXuMGw /OTDG55W6lE+PeNQhNLFCKNoKqQbZ1lH5z5WY= Received: by 10.227.198.203 with SMTP id ep11mr8485997wbb.0.1319618006620; Wed, 26 Oct 2011 01:33:26 -0700 (PDT) Received: from silmaril.hpulabs.org (46.Red-88-24-104.staticIP.rima-tde.net. [88.24.104.46]) by mx.google.com with ESMTPS id ek13sm1751886wbb.3.2011.10.26.01.33.24 (version=SSLv3 cipher=OTHER); Wed, 26 Oct 2011 01:33:25 -0700 (PDT) Message-ID: <4EA7C5D2.6030408@gmail.com> Date: Wed, 26 Oct 2011 10:33:22 +0200 From: carlopmart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110929 Red Hat/3.1.15-1.el6_1 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl> <4EA7BBF9.3@gmail.com> <9fefbda9bf6d16437fc7ad6c5445fe12.squirrel@webmail.pcextreme.nl> In-Reply-To: <9fefbda9bf6d16437fc7ad6c5445fe12.squirrel@webmail.pcextreme.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 08:33:28 -0000 On 10/26/2011 10:09 AM, legolas@legolasweb.nl wrote: >> On 10/26/2011 08:09 AM, legolas@legolasweb.nl wrote: >>> >>>>> I have setup one jail using ezjail. My first surprise is that >>>>> ezjail only installs -RELEASE versions and not RC versions. Ok, I >>>>> supouse that it is normal. But my first question is: can I install a >>>>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? >>> >>> I have upgraded my ezjails using something like: >>> env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r >>> 9.0-RC1 >>> upgrade install >>> >>> This is some hassle, for example, one has to upgrade /etc and /var in >>> /usr/jails/newjail by hand. (And maybe even more, not completely sure >>> there.) >>> >> >> is not possible to update the jail using "ejzail-admin update -u" >> instead of use freebsd-update directly?? >> > Updating can be done, upgrading not. (Thus, a security update can be done, > a full version not, if I understand it correctly.) > > This functionality exists (prematurely) in CVS: > https://erdgeist.org/cvsweb/ezjail/ezjail-admin.diff?r1=1.263&r2=1.264&f=h > Me too ... But downloading latest ezjail-admin code from cvs: 885 # Make the host systems os version our target version 886 # Users can override this by setting the UNAME_r environment variable 887 ezjail_osversion_target="`uname -r`" 888 889 # Finally run freebsd-update to upgrade our basejail 890 env UNAME_r="${ezjail_osversion_source}" freebsd-update -b ${ezjail_jailbase} -r ${ezjail_osversion_target} upgrade install If I am not wrong, it is possible to do a full upgrade between releases, right?? ezjail-admin cvs's version is 1.269: # $Id: ezjail-admin,v 1.269 2011/07/27 11:20:32 erdgeist Exp $ -- CL Martinez carlopmart {at} gmail {d0t} com From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 09:12:02 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75E041065670 for ; Wed, 26 Oct 2011 09:12:01 +0000 (UTC) (envelope-from michiel@boland.org) Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by mx1.freebsd.org (Postfix) with ESMTP id EC4E18FC0A for ; Wed, 26 Oct 2011 09:11:59 +0000 (UTC) Received: from charlemagne.boland.org (59-36-215.ftth.xms.internl.net [82.215.36.59]) (authenticated bits=0) by smtp-vbr13.xs4all.nl (8.13.8/8.13.8) with ESMTP id p9Q9BSdc000636 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 26 Oct 2011 11:11:28 +0200 (CEST) (envelope-from michiel@boland.org) Message-ID: <4EA7CEBF.8020605@boland.org> Date: Wed, 26 Oct 2011 11:11:27 +0200 From: Michiel Boland User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.23) Gecko/20110930 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: installing 9.0-RC1 via netboot still fails X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 09:12:02 -0000 Installing 9.0-RC1 via netbooting still fails, at least on sparc64. See also http://www.freebsd.org/cgi/getmsg.cgi?fetch=41704+0+/usr/local/www/db/text/2011/freebsd-sparc64/20111016.freebsd-sparc64 for a possible fix/workaround. Cheers Michiel From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 09:22:52 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05A72106566C; Wed, 26 Oct 2011 09:22:52 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7D23E8FC0A; Wed, 26 Oct 2011 09:22:51 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-211-94.lns20.adl6.internode.on.net [118.210.211.94]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9Q9MQpo059374 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Oct 2011 19:52:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: <4EA7C5C9.8010903@orange.fr> Date: Wed, 26 Oct 2011 19:52:25 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4EA68C47.2070908@orange.fr> <4EA7C5C9.8010903@orange.fr> To: Claude Buisson X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.162 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Craig Rodrigues , FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 09:22:52 -0000 On 26/10/2011, at 19:03, Claude Buisson wrote: >=20 > [0x2caf2a3c] cdda access error: Could not set block size > [0x2caf2a3c] cdda access error: cannot read sector nnnnn >=20 > incrementing each time the sector number. >=20 > So I infer that vlc cannot set the correct (audio specific) sector = size for the > cam device. >=20 > Thanks for your attention. >=20 > Claude Buisson >=20 > P.S. As I can see reading GENERIC, ATA_CAM will be the default for 9.X = so there > is a risk of complaints from FreeBSD workstation users (who cares ?) = after the > release.. Does cdparanoia work for you? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 10:20:41 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 733C71065679 for ; Wed, 26 Oct 2011 10:20:41 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp03.smtpout.orange.fr [80.12.242.125]) by mx1.freebsd.org (Postfix) with ESMTP id 129468FC1F for ; Wed, 26 Oct 2011 10:20:40 +0000 (UTC) Received: from localhost ([92.136.19.77]) by mwinf5d58 with ME id pNLb1h00A1fmhbQ03NLb9f; Wed, 26 Oct 2011 12:20:39 +0200 X-ME-engine: default Message-ID: <4EA7DEF3.7030807@orange.fr> Date: Wed, 26 Oct 2011 12:20:35 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Daniel O'Connor References: <4EA68C47.2070908@orange.fr> <4EA7C5C9.8010903@orange.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 10:20:41 -0000 On 10/26/2011 11:22, Daniel O'Connor wrote: > > On 26/10/2011, at 19:03, Claude Buisson wrote: >> >> [0x2caf2a3c] cdda access error: Could not set block size >> [0x2caf2a3c] cdda access error: cannot read sector nnnnn >> >> incrementing each time the sector number. >> >> So I infer that vlc cannot set the correct (audio specific) sector size for the >> cam device. >> >> Thanks for your attention. >> >> Claude Buisson >> >> P.S. As I can see reading GENERIC, ATA_CAM will be the default for 9.X so there >> is a risk of complaints from FreeBSD workstation users (who cares ?) after the >> release.. > > > Does cdparanoia work for you? > With cdparanoia-3.9.8_9: YES tested on 8.2 (from Sep 18) and 9.0 (from Sep 25) both with ATA_CAM Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 11:44:09 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 664471065670 for ; Wed, 26 Oct 2011 11:44:09 +0000 (UTC) (envelope-from stas@verberkt.net) Received: from smtpq2.gn.mail.iss.as9143.net (smtpq2.gn.mail.iss.as9143.net [212.54.34.165]) by mx1.freebsd.org (Postfix) with ESMTP id 1C6258FC18 for ; Wed, 26 Oct 2011 11:44:08 +0000 (UTC) Received: from [212.54.34.137] (helo=smtp6.gn.mail.iss.as9143.net) by smtpq2.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RJ1er-0005uV-4Z for freebsd-stable@freebsd.org; Wed, 26 Oct 2011 13:28:33 +0200 Received: from 5357e90f.cm-6-8d.dynamic.ziggo.nl ([83.87.233.15] helo=homey.local) by smtp6.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RJ1eq-0001NR-6a for freebsd-stable@freebsd.org; Wed, 26 Oct 2011 13:28:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 26 Oct 2011 13:28:31 +0200 From: Stas Verberkt To: In-Reply-To: <4EA7C5D2.6030408@gmail.com> References: "\"<4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org>" <4fc99dc86557581cab3484babb368572.squirrel@webmail.pcextreme.nl>" <4EA7BBF9.3@gmail.com> <9fefbda9bf6d16437fc7ad6c5445fe12.squirrel@webmail.pcextreme.nl> <4EA7C5D2.6030408@gmail.com> Message-ID: X-Sender: stas@verberkt.net User-Agent: Roundcube Webmail/0.6 X-ZiggoSMTP-MailScanner-Information: Please contact the ISP for more information X-ZiggoSMTP-MailScanner-ID: 1RJ1eq-0001NR-6a X-ZiggoSMTP-MailScanner: Found to be clean X-ZiggoSMTP-MailScanner-SpamCheck: geen spam, SpamAssassin (niet cached, score=-4.341, vereist 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, CM_REPLY_NOARROW 0.30, PROLO_TRUST_RDNS -3.00, RDNS_DYNAMIC 0.98, SPF_SOFTFAIL 0.20, TW_ZJ 0.08) X-ZiggoSMTP-MailScanner-From: stas@verberkt.net X-Spam-Status: No Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 11:44:09 -0000 On 26.10.2011 10:33, carlopmart wrote: > On 10/26/2011 10:09 AM, legolas@legolasweb.nl wrote: >>> On 10/26/2011 08:09 AM, legolas@legolasweb.nl wrote: >>>> >>>>>> I have setup one jail using ezjail. My first surprise is >>>>>> that >>>>>> ezjail only installs -RELEASE versions and not RC versions. Ok, >>>>>> I >>>>>> supouse that it is normal. But my first question is: can I >>>>>> install a >>>>>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? >>>> >>>> I have upgraded my ezjails using something like: >>>> env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r >>>> 9.0-RC1 >>>> upgrade install >>>> >>>> This is some hassle, for example, one has to upgrade /etc and /var >>>> in >>>> /usr/jails/newjail by hand. (And maybe even more, not completely >>>> sure >>>> there.) >>>> >>> >>> is not possible to update the jail using "ejzail-admin update -u" >>> instead of use freebsd-update directly?? >>> >> Updating can be done, upgrading not. (Thus, a security update can be >> done, >> a full version not, if I understand it correctly.) >> >> This functionality exists (prematurely) in CVS: >> >> https://erdgeist.org/cvsweb/ezjail/ezjail-admin.diff?r1=1.263&r2=1.264&f=h >> > > Me too ... But downloading latest ezjail-admin code from cvs: > > 885 # Make the host systems os version our target version > 886 # Users can override this by setting the UNAME_r > environment variable > 887 ezjail_osversion_target="`uname -r`" > 888 > 889 # Finally run freebsd-update to upgrade our basejail > 890 env UNAME_r="${ezjail_osversion_source}" freebsd-update > -b ${ezjail_jailbase} -r ${ezjail_osversion_target} upgrade install > > If I am not wrong, it is possible to do a full upgrade between > releases, right?? > > ezjail-admin cvs's version is 1.269: > > # $Id: ezjail-admin,v 1.269 2011/07/27 11:20:32 erdgeist Exp $ I think the installing of the new world is not included. (Thus, the part after the first reboot when doing a freebsd-update to 9.0-RC1 on the host system.) From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 11:50:32 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFC77106564A; Wed, 26 Oct 2011 11:50:32 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 71DD68FC1E; Wed, 26 Oct 2011 11:50:32 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-211-94.lns20.adl6.internode.on.net [118.210.211.94]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p9QBoHVV072931 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Oct 2011 22:20:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: <4EA7DEF3.7030807@orange.fr> Date: Wed, 26 Oct 2011 22:20:17 +1030 Content-Transfer-Encoding: quoted-printable Message-Id: <7334F735-D217-471E-B5AA-151DD9204B65@gsoft.com.au> References: <4EA68C47.2070908@orange.fr> <4EA7C5C9.8010903@orange.fr> <4EA7DEF3.7030807@orange.fr> To: Claude Buisson X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 2.162 (**) BAYES_00,KHOP_DYNAMIC,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: Craig Rodrigues , FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 11:50:33 -0000 On 26/10/2011, at 20:50, Claude Buisson wrote: >>> P.S. As I can see reading GENERIC, ATA_CAM will be the default for = 9.X so there >>> is a risk of complaints from FreeBSD workstation users (who cares ?) = after the >>> release.. >>=20 >>=20 >> Does cdparanoia work for you? >>=20 >=20 > With cdparanoia-3.9.8_9: YES >=20 > tested on 8.2 (from Sep 18) and 9.0 (from Sep 25) both with ATA_CAM Strange, I would have thought VLC would use the same sort of access = method as VLC.. I don't know what it's trying so it's hard to know why it doesn't work = :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 12:07:56 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9766E1065674 for ; Wed, 26 Oct 2011 12:07:56 +0000 (UTC) (envelope-from legolas@legolasweb.nl) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by mx1.freebsd.org (Postfix) with ESMTP id 52B308FC14 for ; Wed, 26 Oct 2011 12:07:56 +0000 (UTC) Received: from [212.54.42.133] (helo=smtp2.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RJ1vX-0000Oi-Ub for freebsd-stable@freebsd.org; Wed, 26 Oct 2011 13:45:47 +0200 Received: from 5357e90f.cm-6-8d.dynamic.ziggo.nl ([83.87.233.15] helo=homey.local) by smtp2.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RJ1vW-0007yl-7Y for freebsd-stable@freebsd.org; Wed, 26 Oct 2011 13:45:46 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 26 Oct 2011 13:45:45 +0200 From: Stas Verberkt To: Message-ID: X-Sender: legolas@legolasweb.nl User-Agent: Roundcube Webmail/0.6 X-ZiggoSMTP-MailScanner-Information: Please contact the ISP for more information X-ZiggoSMTP-MailScanner-ID: 1RJ1vW-0007yl-7Y X-ZiggoSMTP-MailScanner: Found to be clean X-ZiggoSMTP-MailScanner-SpamCheck: geen spam, SpamAssassin (niet cached, score=-4.341, vereist 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, CM_REPLY_NOARROW 0.30, PROLO_TRUST_RDNS -3.00, RDNS_DYNAMIC 0.98, SPF_SOFTFAIL 0.20, TW_ZJ 0.08) X-ZiggoSMTP-MailScanner-From: legolas@legolasweb.nl X-Spam-Status: No Subject: Fwd: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 12:07:56 -0000 On 26.10.2011 10:33, carlopmart wrote: > On 10/26/2011 10:09 AM, legolas@legolasweb.nl wrote: >>> On 10/26/2011 08:09 AM, legolas@legolasweb.nl wrote: >>>> >>>>>> I have setup one jail using ezjail. My first surprise is >>>>>> that >>>>>> ezjail only installs -RELEASE versions and not RC versions. Ok, >>>>>> I >>>>>> supouse that it is normal. But my first question is: can I >>>>>> install a >>>>>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? >>>> >>>> I have upgraded my ezjails using something like: >>>> env UNAME_r="8.2-RELEASE" freebsd-update -b /usr/jails/basejail -r >>>> 9.0-RC1 >>>> upgrade install >>>> >>>> This is some hassle, for example, one has to upgrade /etc and /var >>>> in >>>> /usr/jails/newjail by hand. (And maybe even more, not completely >>>> sure >>>> there.) >>>> >>> >>> is not possible to update the jail using "ejzail-admin update -u" >>> instead of use freebsd-update directly?? >>> >> Updating can be done, upgrading not. (Thus, a security update can be >> done, >> a full version not, if I understand it correctly.) >> >> This functionality exists (prematurely) in CVS: >> >> https://erdgeist.org/cvsweb/ezjail/ezjail-admin.diff?r1=1.263&r2=1.264&f=h >> > > Me too ... But downloading latest ezjail-admin code from cvs: > > 885 # Make the host systems os version our target version > 886 # Users can override this by setting the UNAME_r > environment variable > 887 ezjail_osversion_target="`uname -r`" > 888 > 889 # Finally run freebsd-update to upgrade our basejail > 890 env UNAME_r="${ezjail_osversion_source}" freebsd-update > -b ${ezjail_jailbase} -r ${ezjail_osversion_target} upgrade install > > If I am not wrong, it is possible to do a full upgrade between > releases, right?? > > ezjail-admin cvs's version is 1.269: > > # $Id: ezjail-admin,v 1.269 2011/07/27 11:20:32 erdgeist Exp $ I think the installing of the new world is not included. (Thus, the part after the first reboot when doing a freebsd-update to 9.0-RC1 on the host system.) From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 13:17:47 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D00A51065673 for ; Wed, 26 Oct 2011 13:17:47 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) by mx1.freebsd.org (Postfix) with ESMTP id 87DDD8FC18 for ; Wed, 26 Oct 2011 13:17:47 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id B95F425D37D1; Wed, 26 Oct 2011 13:17:46 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id E158CBD3D39; Wed, 26 Oct 2011 13:17:45 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id xU1aD01UYzC2; Wed, 26 Oct 2011 13:17:45 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id E8A83BD3D19; Wed, 26 Oct 2011 13:17:44 +0000 (UTC) Date: Wed, 26 Oct 2011 13:17:44 +0000 (UTC) From: "Bjoern A. Zeeb" To: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <4EA5EBB5.3090101@quip.cz> Message-ID: References: <4EA5EBB5.3090101@quip.cz> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 13:17:47 -0000 On Tue, 25 Oct 2011, Miroslav Lachman wrote: > Hi all, > > I have a problem with ntpd on many of our servers running 8.2-RELEASE or > newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2 > or 8-STABLE amd64 with GENERIC. hmm, could it be I didn't MFC all fixes I had done to help that, which are partly (mostly, all these days) existent in newer upstream version (esepcially the latest devels). I'll go an look in my 70 oustanding MFCs. Would be cool if you could test 9 temporary and see if things are better there. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 14:57:27 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98D1F106566B for ; Wed, 26 Oct 2011 14:57:27 +0000 (UTC) (envelope-from fbsdq@peterk.org) Received: from poshta.pknet.net (poshta.pknet.net [216.241.167.213]) by mx1.freebsd.org (Postfix) with ESMTP id 4CD298FC16 for ; Wed, 26 Oct 2011 14:57:27 +0000 (UTC) Received: (qmail 20974 invoked by uid 89); 26 Oct 2011 14:30:45 -0000 Received: from localhost (HELO pop.pknet.net) (127.0.0.1) by poshta.pknet.net with ESMTP; 26 Oct 2011 14:30:45 -0000 Received: from 74.63.162.21 (SquirrelMail authenticated user fbsdq@peterk.org) by pop.pknet.net with HTTP; Wed, 26 Oct 2011 08:30:45 -0600 Message-ID: In-Reply-To: <4EA7BC66.3090304@gmail.com> References: <4EA721A7.8050905@gmail.com> <20111026031202.2a8780f9@davenulle.org> <4EA7BC66.3090304@gmail.com> Date: Wed, 26 Oct 2011 08:30:45 -0600 From: "Peter" To: "carlopmart" User-Agent: SquirrelMail/1.4.21 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: Some questions about jails on FreeBSD9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 14:57:27 -0000 > On 10/26/2011 03:12 AM, Patrick Lamaiziere wrote: >> Le Tue, 25 Oct 2011 22:52:55 +0200, >> carlopmart a écrit : >> >> Hello, >> >>> I have installed one FreeBSD 9.0-RC1 host to run different services >>> (dns, smtp and www only) using jails. This host has two physical >>> nics: em0 and em1. em0 is assigned to pyhiscal host, and I would like >>> to assign em1 to jails. But em0 and em1 are on different networks: >>> em0 is on 192.168.1.0/24 and em1 in 192.168.2.0/29. >>> >>> I have setup one jail using ezjail. My first surprise is that >>> ezjail only installs -RELEASE versions and not RC versions. Ok, I >>> supouse that it is normal. But my first question is: can I install a >>> FreeBSD 8.2 jail under a FreeBSD 9.0 host?? >> >> You may run 8.2 installed ports on 9.0 by using the port >> /usr/ports/misc/compat8x/ >> >> But I suggest to upgrade the port ASAP. >> >>> And the real question: How do I need to configure network under >>> this jail to access it? I have configured ifconfig param for em1 on >>> host's rc.conf, but what about the default route under this jail?? I >>> thought to use pf rules, but I am not sure. >> >> jail enforces the use of the jail IP address in the jail, but that's >> all. Just enable routing on the host. >> > > But, that is not possible. Between host and jail exists a firewall ... I > can't do simple routing with the host. Maybe a posible solution is to > use policy source routing ?? > > > > -- > CL Martinez > carlopmart {at} gmail {d0t} com > _______________________________________________ I'm using FIBs. The host is in on a private network with gateway of 192.168.1.1 and jails are on public network with their own real/public gateway. FIBs work without the box becoming a gateway: %grep gateway /etc/rc.conf gateway_enable="NO" I have this in system startup to setup "public gateway" for jails: %cat /usr/local/etc/rc.d/0.setfib.sh #!/bin/sh echo setfib 1 for public jails /usr/sbin/setfib 1 /sbin/route add default 216.241.167.1 and in /usr/local/etc/ezjail/myjail I added this line to the end of configs: export jail_myjail_fib="1" [/usr/sbin/jail has FIB support built in, but at that time ezjail did not, so I had to manually add it in the config - nowadays I believe ezjail has FIB support natively, but the resulting config file is the same] The host is using NAT to get out via private IP, and jails are available via public IP. All the IPs are defined in rc.conf the normal _alias way. FIB support as I remember needs a custom kernel - not sure about 9, this is in 8.2. I even run openbsd spamd on the host and using FIBs to start the spamd daemon via a 'setfib 1' wrapper script: %cat /usr/local/etc/rc.d/obspamdfib.sh #!/bin/sh # # this just calls the orignal file, but with setfib 1 /usr/sbin/setfib 1 /usr/local/etc/rc.d.fib/obspamd $1 I had moved the 'obspamd' startup script to rc.d.fib just so a 'setfib 1' wrapper is called. ]Peter[ FIBs are awesome when you don't have many public IPs and when host is _only_ a jail host running no services From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 16:57:32 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3321F106566B for ; Wed, 26 Oct 2011 16:57:32 +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 C679D8FC16 for ; Wed, 26 Oct 2011 16:57:31 +0000 (UTC) Received: from localhost ([92.162.5.199]) by mwinf5d12 with ME id pUxS1h0034HeVn803UxSyf; Wed, 26 Oct 2011 18:57:30 +0200 X-ME-engine: default Message-ID: <4EA83BF5.4090201@orange.fr> Date: Wed, 26 Oct 2011 18:57:25 +0200 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.23) Gecko/20110928 Thunderbird/3.1.15 MIME-Version: 1.0 To: Daniel O'Connor References: <4EA68C47.2070908@orange.fr> <4EA7C5C9.8010903@orange.fr> <4EA7DEF3.7030807@orange.fr> <7334F735-D217-471E-B5AA-151DD9204B65@gsoft.com.au> In-Reply-To: <7334F735-D217-471E-B5AA-151DD9204B65@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 16:57:32 -0000 On 10/26/2011 13:50, Daniel O'Connor wrote: > > On 26/10/2011, at 20:50, Claude Buisson wrote: >>>> P.S. As I can see reading GENERIC, ATA_CAM will be the default for 9.X so there >>>> is a risk of complaints from FreeBSD workstation users (who cares ?) after the >>>> release.. >>> >>> >>> Does cdparanoia work for you? >>> >> >> With cdparanoia-3.9.8_9: YES >> >> tested on 8.2 (from Sep 18) and 9.0 (from Sep 25) both with ATA_CAM > > > Strange, I would have thought VLC would use the same sort of access method as VLC.. > > I don't know what it's trying so it's hard to know why it doesn't work :( Doing my home work step by step: I found only 1 place in VLC where the first message: [0x2caf2a3c] cdda access error: Could not set block size is emitted, after an: ioctl( p_vcddev->i_device_handle, CDRIOCSETBLOCKSIZE, &i_size ) CDRIOCSETBLOCKSIZE is defined in sys/cdrio.h, and in the kernel used in: sys/dev/ata/atapi-cd.c which is a brought into the kernel by: device atapicd So the natural question is: Is this ioctl supported with ATA_CAM (and atapicam) ? If not, what is to be used instead ? Claude Buisson From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 19:31:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 898F8106566B; Wed, 26 Oct 2011 19:31:05 +0000 (UTC) (envelope-from subbsd@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 339078FC08; Wed, 26 Oct 2011 19:31:04 +0000 (UTC) Received: by vcbfo13 with SMTP id fo13so2718408vcb.13 for ; Wed, 26 Oct 2011 12:31:04 -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; bh=Zyw96R7lHzRiYscK5TwA+KjYwONkpEw0/9xGFkQLOBY=; b=n0uHbIPEGno1WqaoY6M//GIwGWm1ha4hi4/SvXxdE01Xea+4WUOicTdX9OlqXR2qfy 94mzpwZ7RWpe3hCLG1Jjf/bWkaYr2d+PHoCCu07PRRsLHV0ISt/xgNfziaUwbH8L+4Mn vI0c+ojwDAd/eaQUJTwxsSZW7E6Ah3G9jDUac= MIME-Version: 1.0 Received: by 10.220.153.3 with SMTP id i3mr538060vcw.74.1319657464455; Wed, 26 Oct 2011 12:31:04 -0700 (PDT) Received: by 10.220.160.197 with HTTP; Wed, 26 Oct 2011 12:31:04 -0700 (PDT) Date: Wed, 26 Oct 2011 23:31:04 +0400 Message-ID: From: Subbsd To: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: FreeBSD 9.0-RC1 freeze after swapoff/swapon procedure on md/vnode-backend file X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 19:31:05 -0000 Hi I get easy reproducible a hang-up servers that use the file-based swap file after swapoff / swapon procedure (in this case, some of the data must be swapped). For example: 1) dd if=/dev/zero of=/usr/swp1 bs=1m count=100 2) mdconfig -a -t vnode -f /usr/swp1 3) swapon /dev/md0 4) begin to allocated memory, for example by simple: tail /dev/zero 5) after a filling of some percent, do swapoff /dev/md0, then swapon /dev/md0. you can try this procedure again. The system may stop responding to commands and freezes or locks up after some time. From the outside - the core lives (icmp response goes) but the disk system is not available. PS: one of my server to my mind is frozen without swapoff/on - just had three swapfile, a day after he crashed. From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 19:37:48 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9497D106564A; Wed, 26 Oct 2011 19:37:48 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E8F888FC16; Wed, 26 Oct 2011 19:37:47 +0000 (UTC) Received: by mail-bw0-f54.google.com with SMTP id zt4so2328756bkb.13 for ; Wed, 26 Oct 2011 12:37:47 -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; bh=P4/77/2YJkIkFJ5QEeJz4k0yMhqS2MYF6lL0zwPKLUc=; b=s1aS8+4vKW/lml8j/SfRgVZwolGoQj/LS3BiBG8MM4eRF6ypNexCi83MIDUf9xXhJW 5OII3d+iBlVDljtE9Eqo6PvuQfByTRzb0xKsRTpBQCZLkSPhgF/LmIZNEoLlN4av7fi4 oAxtdLEaxnXjtpQG/mbm3XKuSxc+E5CT5TaQA= MIME-Version: 1.0 Received: by 10.204.38.16 with SMTP id z16mr13873082bkd.66.1319657867513; Wed, 26 Oct 2011 12:37:47 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.204.39.12 with HTTP; Wed, 26 Oct 2011 12:37:47 -0700 (PDT) In-Reply-To: <4EA83BF5.4090201@orange.fr> References: <4EA68C47.2070908@orange.fr> <4EA7C5C9.8010903@orange.fr> <4EA7DEF3.7030807@orange.fr> <7334F735-D217-471E-B5AA-151DD9204B65@gsoft.com.au> <4EA83BF5.4090201@orange.fr> Date: Wed, 26 Oct 2011 12:37:47 -0700 X-Google-Sender-Auth: r3EkPNEtyD_PdJAA4Ws36AMEWMo Message-ID: From: Craig Rodrigues To: Claude Buisson Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: can audio CDs be played with ATA_CAM ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 19:37:48 -0000 On Wed, Oct 26, 2011 at 9:57 AM, Claude Buisson wrote: > > Doing my home work step by step: > > I found only 1 place in VLC where the first message: > > [0x2caf2a3c] cdda access error: Could not set block size > > is emitted, after an: > > ioctl( p_vcddev->i_device_handle, CDRIOCSETBLOCKSIZE, &i_size ) > > CDRIOCSETBLOCKSIZE is defined in sys/cdrio.h, and in the kernel used in: > > sys/dev/ata/atapi-cd.c > > which is a brought into the kernel by: > > device atapicd > > So the natural question is: > > Is this ioctl supported with ATA_CAM (and atapicam) ? > > If not, what is to be used instead ? Claude, Thanks for digging into this a bit. I just added some code to make it easier for applications to detect at runtime if ATA_CAM has been configured in the kernel: http://lists.freebsd.org/pipermail/svn-src-stable-9/2011-October/000114.html I am not 100% sure how the CD driver works with ATA_CAM. I think you might need to look at: src/sys/cam/scsi/scsi_cd.c and also read the cd(4) man page. We may need to extend scsi_cd.c, but I'm not sure. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-stable@FreeBSD.ORG Wed Oct 26 22:27:05 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB3511065673; Wed, 26 Oct 2011 22:27:05 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C36E8FC14; Wed, 26 Oct 2011 22:27:05 +0000 (UTC) Received: by vws11 with SMTP id 11so2900478vws.13 for ; Wed, 26 Oct 2011 15:27:04 -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:content-transfer-encoding; bh=eYX/A1DDpxXoits2a23if+JhfBsUwGu0GRaGe0lFCJk=; b=H3rD00y8MNK+xsP+XDZWHKBihHCT8W+qB8PbX2WRGvc27IDZJWejcIJNeeovyNPNlG HYrA0J1MAavv2jeN2tLaF+/+dQIWld5UH/GigBSFg3RULMYcZU2a0gb6Sa5ejQL1OscD j8Itta51LicMxEjdG2dg1Y5ww/EpiysPSsgLI= MIME-Version: 1.0 Received: by 10.182.59.5 with SMTP id v5mr2956460obq.78.1319666562689; Wed, 26 Oct 2011 15:02:42 -0700 (PDT) Received: by 10.182.160.97 with HTTP; Wed, 26 Oct 2011 15:02:42 -0700 (PDT) In-Reply-To: References: Date: Thu, 27 Oct 2011 02:02:42 +0400 Message-ID: From: Sergey Kandaurov To: Subbsd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0-RC1 freeze after swapoff/swapon procedure on md/vnode-backend file X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2011 22:27:06 -0000 On 26 October 2011 23:31, Subbsd wrote: > Hi > > I get easy reproducible =A0a hang-up servers that use the file-based > swap file after swapoff / swapon procedure (in this case, some of the > data must be swapped). For example: > > 1) dd if=3D/dev/zero of=3D/usr/swp1 bs=3D1m count=3D100 > 2) mdconfig -a -t vnode -f /usr/swp1 > 3) swapon /dev/md0 > 4) begin to allocated memory, for example by simple: > tail /dev/zero > > 5) after a filling of some percent, do swapoff /dev/md0, then swapon > /dev/md0. you can try this procedure again. > > The system may stop responding to commands and freezes or locks up > after some time. From the outside - the core lives (icmp response > goes) but the disk system is not available. > > PS: one of my server to my mind is frozen without swapoff/on - just > had three swapfile, a day after he crashed. Something interesting while trying to reproduce your problem: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1048970, size: 4096 swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1057174, size: 4096 panic: swapoff: failed to locate 16056 swap blocks cpuid =3D 1 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff802e009a =3D db_trace_self_wrapper+0x2= a kdb_backtrace() at 0xffffffff80486d87 =3D kdb_backtrace+0x37 panic() at 0xffffffff8044f6ee =3D panic+0x2ee swapoff_one() at 0xffffffff80687425 =3D swapoff_one+0x475 sys_swapoff() at 0xffffffff8068789b =3D sys_swapoff+0x1bb amd64_syscall() at 0xffffffff806c60c9 =3D amd64_syscall+0x299 Xfast_syscall() at 0xffffffff806b1467 =3D Xfast_syscall+0xf7 --- syscall (424, FreeBSD ELF64, sys_swapoff), rip =3D 0x800ab307c, rsp =3D 0x7fffffffd9c8, rbp =3D 0 --- KDB: enter: panic [ thread pid 63255 tid 100211 ] Stopped at 0xffffffff8048696b =3D kdb_enter+0x3b: movq $0,0x735f72(%rip) Below is a trace for a process on another CPU that's doing intensive malloc+bzero in userland: db> bt 63066 Tracing pid 63066 tid 100199 td 0xfffffe000e89f000 cpustop_handler() at 0xffffffff806bb46b =3D cpustop_handler+0x2b ipi_nmi_handler() at 0xffffffff806bb540 =3D ipi_nmi_handler+0x50 trap() at 0xffffffff806c7035 =3D trap+0x2a5 nmi_calltrap() at 0xffffffff806b15bf =3D nmi_calltrap+0x8 --- trap 0x13, rip =3D 0xffffffff8043e0d0, rsp =3D 0xffffffff80dc4dc0, rbp =3D 0xffffff80908de750 --- _mtx_unlock_flags() at 0xffffffff8043e0d0 =3D _mtx_unlock_flags+0x170 swp_pager_meta_ctl() at 0xffffffff806841aa =3D swp_pager_meta_ctl+0xea swap_pager_haspage() at 0xffffffff80684272 =3D swap_pager_haspage+0x42 vm_fault_hold() at 0xffffffff8068e379 =3D vm_fault_hold+0x599 trap_pfault() at 0xffffffff806c6c26 =3D trap_pfault+0xe6 trap() at 0xffffffff806c733f =3D trap+0x5af calltrap() at 0xffffffff806b1183 =3D calltrap+0x8 --- trap 0xc, rip =3D 0x4006ed, rsp =3D 0x7fffffffdad0, rbp =3D 0x7fffffffd= ae0 --- That corresponds to kgdb: #9 0xffffffff8044f6e4 in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:624 #10 0xffffffff80687425 in swapoff_one (sp=3D0xfffffe000dc3dc00, cred=3D0xffffff808e5bf340) at /usr/src/sys/vm/swap_pager.c:1774 #11 0xffffffff8068789b in sys_swapoff (td=3D0xfffffe000e90f000, uap=3DVariable "uap" is not available. ) at /usr/src/sys/vm/swap_pager.c:2236 #12 0xffffffff806c60c9 in amd64_syscall (td=3D0xfffffe000e90f000, traced=3D= 0) at subr_syscall.c:131 ---Type to continue, or q to quit--- #13 0xffffffff806b1467 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 and (kgdb) thr 108 [Switching to thread 108 (Thread 100199)]#0 cpustop_handler () at /usr/src/sys/amd64/amd64/mp_machdep.c:1394 1394 CPU_SET_ATOMIC(cpu, &stopped_cpus); (kgdb) bt #0 cpustop_handler () at /usr/src/sys/amd64/amd64/mp_machdep.c:1394 #1 0xffffffff806bb540 in ipi_nmi_handler () at /usr/src/sys/amd64/amd64/mp_machdep.c:1376 #2 0xffffffff806c7035 in trap (frame=3D0xffffffff80dc4d10) at /usr/src/sys/amd64/amd64/trap.c:200 #3 0xffffffff806b15bf in nmi_calltrap () at /usr/src/sys/amd64/amd64/exception.S:501 #4 0xffffffff8043e0d0 in _mtx_unlock_flags (m=3D0xffffffff80d8af80, opts= =3D0, file=3D0xffffffff80791e48 "/usr/src/sys/vm/swap_pager.c", line=3D2040) at /usr/src/sys/kern/kern_mutex.c:221 [smth. wrong there -- no further stack: swap_pager_*, etc] Here both swap_pager_swapoff() and swp_pager_meta_ctl() contend on swhash_mtx. Or rather that's due to low limit set on retries counter? Let's see again for another crash: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1062783, size: 4096 panic: swapoff: failed to locate 22133 swap blocks cpuid =3D 2 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff802e009a =3D db_trace_self_wrapper+0x2= a kdb_backtrace() at 0xffffffff80486d87 =3D kdb_backtrace+0x37 panic() at 0xffffffff8044f6ee =3D panic+0x2ee swapoff_one() at 0xffffffff80687425 =3D swapoff_one+0x475 sys_swapoff() at 0xffffffff8068789b =3D sys_swapoff+0x1bb amd64_syscall() at 0xffffffff806c60c9 =3D amd64_syscall+0x299 Xfast_syscall() at 0xffffffff806b1467 =3D Xfast_syscall+0xf7 --- syscall (424, FreeBSD ELF64, sys_swapoff), rip =3D 0x800ab307c, rsp =3D 0x7fffffffd9c8, rbp =3D 0 --- KDB: enter: panic [ thread pid 2807 tid 100149 ] Stopped at 0xffffffff8048696b =3D kdb_enter+0x3b: movq $0,0x735f72(%rip) Hmm... now the remain all 3 cpus are on idle. The hungry process is not on CPU now and just sleeping, nothing interesting there: Tracing command hungry pid 2707 tid 100077 td 0xfffffe00029a4900 sched_switch() at 0xffffffff804798f7 =3D sched_switch+0x167 mi_switch() at 0xffffffff80458faa =3D mi_switch+0x1ea turnstile_wait() at 0xffffffff8049872d =3D turnstile_wait+0x27d _mtx_lock_sleep() at 0xffffffff8043e500 =3D _mtx_lock_sleep+0x130 _mtx_lock_flags() at 0xffffffff8043e8ac =3D _mtx_lock_flags+0x16c pmap_enter() at 0xffffffff806c3867 =3D pmap_enter+0x87 vm_fault_hold() at 0xffffffff8068f39c =3D vm_fault_hold+0x15bc trap_pfault() at 0xffffffff806c6c26 =3D trap_pfault+0xe6 trap() at 0xffffffff806c733f =3D trap+0x5af calltrap() at 0xffffffff806b1183 =3D calltrap+0x8 --- trap 0xc, rip =3D 0x4006ed, rsp =3D 0x7fffffffdad0, rbp =3D 0x7fffffffd= ae0 --- However, a pagedaemon kernel process now stuck at the same place, although it's at _mtx_lock_sleep unlike _mtx_unlock_flags from a previous crash. Tracing command pagedaemon pid 4 tid 100059 td 0xfffffe00026b5900 sched_switch() at 0xffffffff804798f7 =3D sched_switch+0x167 mi_switch() at 0xffffffff80458faa =3D mi_switch+0x1ea turnstile_wait() at 0xffffffff8049872d =3D turnstile_wait+0x27d _mtx_lock_sleep() at 0xffffffff8043e500 =3D _mtx_lock_sleep+0x130 _mtx_lock_flags() at 0xffffffff8043e8ac =3D _mtx_lock_flags+0x16c swp_pager_meta_ctl() at 0xffffffff8068413a =3D swp_pager_meta_ctl+0x7a swap_pager_haspage() at 0xffffffff80684272 =3D swap_pager_haspage+0x42 vm_page_cache() at 0xffffffff806a133a =3D vm_page_cache+0x2ca vm_pageout() at 0xffffffff806a40a1 =3D vm_pageout+0x1201 fork_exit() at 0xffffffff8041f965 =3D fork_exit+0x135 fork_trampoline() at 0xffffffff806b16ae =3D fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff80003c5d00, rbp =3D 0 --- --=20 wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 13:16:39 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2412E106564A; Thu, 27 Oct 2011 13:16:39 +0000 (UTC) (envelope-from wkoszek@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [212.87.224.105]) by mx1.freebsd.org (Postfix) with ESMTP id 9FD1F8FC15; Thu, 27 Oct 2011 13:16:38 +0000 (UTC) Received: from wkoszek-thinkpad-t410 (freebsd.czest.pl [212.87.224.105]) by freebsd.czest.pl (8.14.5/8.14.5) with ESMTP id p9RDG6MR084257; Thu, 27 Oct 2011 13:16:06 GMT (envelope-from wkoszek@freebsd.czest.pl) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Alberto Villa" References: Date: Thu, 27 Oct 2011 15:16:36 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Wojciech A. Koszek" Organization: FreeBSD.czest.pl Message-ID: In-Reply-To: User-Agent: Opera Mail/11.52 (Linux) X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.2.7 (freebsd.czest.pl [127.0.0.2]); Thu, 27 Oct 2011 13:16:06 +0000 (UTC) Cc: marius@freebsd.org, "marcel@freebsd.org" , freebsd-stable@freebsd.org Subject: Re: (Possible fix for sbp(4)) Re: Comment out sbp driver from GENERIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 13:16:39 -0000 Dnia 18-10-2011 o 14:12:56 Alberto Villa napisa=C5=82= (a): > On Tue, Oct 18, 2011 at 1:48 PM, Wojciech A. Koszek > wrote: >> Commenting a driver out is almost always a bad idea and should >> be done as a last step. > > Well, few weeks prior to -RELEASE can be considered a last step. :) > >> If you are impacted by sbp(4) hangs please follow this thread: >> >> >> http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081= 411.html >> >> And please let me know if a fix explained in this thread works for yo= u. > > Thank you, will test it in few days. Any updates? -- = Wojciech A. Koszek wkoszek@freebsd.czest.pl http://FreeBSD.czest.pl/~wkoszek/ From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 15:00:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3B0E106564A for ; Thu, 27 Oct 2011 15:00:10 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail-chaos.rambler.ru (mail-chaos.rambler.ru [81.19.68.130]) by mx1.freebsd.org (Postfix) with ESMTP id 5C6B98FC12 for ; Thu, 27 Oct 2011 15:00:10 +0000 (UTC) Received: from citrin.office.vega.ru (office-nat.spylog.net [193.169.234.6]) (Authenticated sender: citrin@citrin.ru) by mail-chaos.rambler.ru (Postfix) with ESMTPSA id 0591D1702A for ; Thu, 27 Oct 2011 18:48:58 +0400 (MSD) Message-ID: <4EA96F59.7040308@citrin.ru> Date: Thu, 27 Oct 2011 18:48:57 +0400 From: Anton Yuzhaninov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0.2) Gecko/20110922 Thunderbird/6.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: FreeBSD 8 - bug in rename(2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 15:00:10 -0000 After upgrade from old RELENG_7 to fresh RELENG_8 I've met with error in log rotation script. After some digging I'v found, that rename(2) syscall sometime don't work properly. I can't reproduce problem with simple test case, but in production this problem appeared several time per day. After rename(2) sometimes old name still exists. stat for old and new names: 101 12153947 -rw-r--r-- 1 owner data 54507160 164374900 "Oct 27 13:58:06 2011" "Oct 27 13:58:06 2011" "Oct 27 13:58:06 2011" "Oct 27 13:56:05 2011" 16384 321248 0 /usr/local/run/nginx/access_log 101 12153947 -rw-r--r-- 1 owner data 54507160 164377726 "Oct 27 13:58:06 2011" "Oct 27 13:58:06 2011" "Oct 27 13:58:06 2011" "Oct 27 13:56:05 2011" 16384 321248 0 /usr/local/run/nginx/access_log.20111027T135806 2 files share same inode, but number of links is 1 2-nd rename for this file fail: mv: rename /usr/local/run/nginx/access_log to /usr/local/run/nginx/access_log.tmp: No such file or directory vfs.lookup_shared=0 don't affect this problem, It seems to be, that problem is related to namei (vfs) cache - old entry sometimes is not removed. Renamed file is open for write by nginx, but I don't know how this can affect namei. -- Anton Yuzhaninov From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 15:00:33 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20DAE106564A for ; Thu, 27 Oct 2011 15:00:33 +0000 (UTC) (envelope-from lattera@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 D3FE48FC17 for ; Thu, 27 Oct 2011 15:00:32 +0000 (UTC) Received: by vcbfo13 with SMTP id fo13so3896802vcb.13 for ; Thu, 27 Oct 2011 08:00:32 -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; bh=jvdN/ZPAuSkev1dGxMjWMURHicpVRl85Fb3qbJqPgf8=; b=SVG2NLtazZqqg7UguzksNN2q12lmFYRXFxgDByu79kPYK3NxqWbt7GihXifsVCwR/z sLQPfHO7xCZ5gYGsaJvWubrpahGfCN9JWtYa7bhLHBIxIcpIzhHfvxTkJGpkqcY8indx DU4fItIMhT3Mek6UuO90Wf20TfcCUd5XWF9Lc= MIME-Version: 1.0 Received: by 10.182.227.7 with SMTP id rw7mr6435422obc.70.1319725939750; Thu, 27 Oct 2011 07:32:19 -0700 (PDT) Received: by 10.182.44.135 with HTTP; Thu, 27 Oct 2011 07:32:19 -0700 (PDT) Date: Thu, 27 Oct 2011 08:32:19 -0600 Message-ID: From: Shawn Webb To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: DTrace Issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 15:00:33 -0000 Hey FreeBSD Stable, I'm having issues printing out the curpsinfo->pr_psargs. Has anyone had any success printing out the arguments passed to a program? Below is the log of what happens when I run my script the source for my script. [root@fbsd-sec ~/dtrace/security]# ./log_exec.d 80 dtrace: buffer size lowered to 2m 1319724849:80:sh:sh 1319724849:80:ls:ls ^C [root@fbsd-sec ~/dtrace/security]# cat log_exec.d #!/usr/sbin/dtrace -s #pragma D option quiet proc:::exec-success /uid == $1/ { printf("%d:%d:%s:", walltimestamp, uid, execname); trace(curpsinfo->pr_psargs); printf("\n"); } Thanks, Shawn From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 16:05:01 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10395106566B for ; Thu, 27 Oct 2011 16:05:01 +0000 (UTC) (envelope-from guy.helmer@palisadesystems.com) Received: from ps-2-a.compliancesafe.com (ps-2-a.compliancesafe.com [216.81.161.163]) by mx1.freebsd.org (Postfix) with ESMTP id BA9488FC0C for ; Thu, 27 Oct 2011 16:05:00 +0000 (UTC) Received: from mail.palisadesystems.com (localhost.compliancesafe.com [127.0.0.1]) by ps-2-a.compliancesafe.com (8.14.4/8.14.3) with ESMTP id p9RFluRF099491 for ; Thu, 27 Oct 2011 10:47:57 -0500 (CDT) (envelope-from guy.helmer@palisadesystems.com) Received: from guysmbp.dyn.palisadesys.com (GuysMBP.dyn.palisadesys.com [172.16.2.90]) (authenticated bits=0) by mail.palisadesystems.com (8.14.3/8.14.3) with ESMTP id p9RFlnwl023931 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 27 Oct 2011 10:47:50 -0500 (CDT) (envelope-from guy.helmer@palisadesystems.com) X-DKIM: Sendmail DKIM Filter v2.8.3 mail.palisadesystems.com p9RFlnwl023931 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=palisadesystems.com; s=mail; t=1319730470; bh=nkdaA8OkpIExn/YMzRX6UtdANQbw/J7FarRBGgHyO4o=; l=128; h=From:Content-Type:Content-Transfer-Encoding:Subject:Date: Message-Id:To:Mime-Version; b=ZF3d/Tl8GUYMS1TGrA5K0EW86DlTxaBv5ZJ+ZH/Y5ZnvWrZc/4iUze4vm5NJ1tAom ASjSmTxtiTfnfrTdPcgyjT0yB2CfEYI4UBHAN/dhjGBi0XvjCEP60GVrJY0+Q7ZFec j9QXWEyeZtnWpJ8avzazEl+MINlPO3wKVYP8vcsI= From: Guy Helmer Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Oct 2011 10:47:49 -0500 Message-Id: <99F436DB-108C-4235-A419-95984CA464CC@palisadesystems.com> To: FreeBSD Stable Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.5 (mail.palisadesystems.com [172.16.1.5]); Thu, 27 Oct 2011 10:47:50 -0500 (CDT) X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner-ID: p9RFlnwl023931 X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-2.9, required 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90) X-Palisade-MailScanner-From: guy.helmer@palisadesystems.com X-Spam-Status: No X-PacketSure-Scanned: Yes Subject: devfs and unionfs oddity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 16:05:01 -0000 On a build server, I have a union mount of a FreeBSD o/s build from a = point-in-time under a build directory, and then I have devfs mounted on = dev in the build directory as well so I can do a chroot install of = packages for particular target o/s versions. mount shows this: :/usr/app8xbuild/os-image on = /usr/autobuild/images/product-image (unionfs, local) devfs on /usr/autobuild/images/product-image/dev (devfs, local, = multilabel) and the system does a chroot to /usr/autobuild/images/product-image/ = while installing the ports for the product. It seems impossible, but at times, after unmounting = /usr/autobuild/images/product-image/dev and = /usr/autobuild/images/product-image, a regular file = /usr/autobuild/images/product-image/dev/null will be left as a result of = redirecting some output to /dev/null during the port installs. Could there be some odd interaction of devfs and unions that allows this = to happen? Guy= -------- This message has been scanned by ComplianceSafe, powered by Palisade's PacketSure. From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 22:52:53 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F1EC106566C for ; Thu, 27 Oct 2011 22:52:53 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0318FC17 for ; Thu, 27 Oct 2011 22:52:52 +0000 (UTC) Received: from vhoffman-macbooklocal.local ([10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p9RMqod8026726 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 27 Oct 2011 23:52:51 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4EA9E0C3.5080306@unsane.co.uk> Date: Thu, 27 Oct 2011 23:52:51 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: FreeBSD Stable Mailing List X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: mfi timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 22:52:53 -0000 Hi, I've recently installed a new NAS at work which uses a rebranded LSI megaraid sas [root@banshee ~]# mfiutil show adapter mfi0 Adapter: Product Name: Supermicro SMC2108 Serial Number: Firmware: 12.12.0-0047 RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 Battery Backup: present NVRAM: 32K Onboard Memory: 512M Minimum Stripe: 8k Maximum Stripe: 1M I'm running 8-STABLE as of 2011-10-23 (for zfs v28 as is got 26 3Tb drives) I'm seeing a lot of messages like mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 60 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 90 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 120 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 150 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 180 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 210 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 240 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 271 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 301 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 331 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 361 SECONDS mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 391 SECONDS mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 55 SECONDS mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 85 SECONDS At which time I'm seeing IO stall on the array connected to the mfi adapter, this can continue for 20 minutes or so resuming randomly (or so it seems although a little more on this later on) >From pciconf -lv mfi0@pci0:5:0:0: class=0x010400 card=0x070015d9 chip=0x00791000 rev=0x04 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' class = mass storage subclass = RAID >From dmesg mfi0: port 0xe000-0xe0ff mem 0xfbd9c000-0xfbd9ffff,0xfbdc0000-0xfbdfffff irq 32 at device 0.0 on pci5 mfi0: Megaraid SAS driver Ver 3.00 mfi0: 12330 (372962922s/0x0020/info) - Shutdown command received from host mfi0: 12331 (boot + 4s/0x0020/info) - Firmware initialization started (PCI ID 0079/1000/0700/15d9) mfi0: 12332 (boot + 4s/0x0020/info) - Firmware version 2.120.53-1235 mfi0: 12333 (boot + 7s/0x0008/info) - Battery Present mfi0: 12334 (boot + 7s/0x0020/info) - Package version 12.12.0-0047 mfi0: 12335 (boot + 7s/0x0020/info) - Board Revision I have found this thread from a bit of googleing but it doesnt end too well. http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.html Was this ever taken further? One thing I have noticed is that the stall (and timeout messages) seem to go away if I query the card using mfiutil, I currently have a cron doing this every 2 minutes to see if this has been coincidence or not. Any suggestions welcome and i'm happy to provide more info if i can but I dont have a duplicate to do too much debugging on, I'm happy to try patches though. Is this worth filing a PR? Vince From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 23:04:55 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FC291065670 for ; Thu, 27 Oct 2011 23:04:55 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 129D38FC0A for ; Thu, 27 Oct 2011 23:04:54 +0000 (UTC) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta09.westchester.pa.mail.comcast.net with comcast id pybd1h00627AodY59z4vTt; Thu, 27 Oct 2011 23:04:55 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta19.westchester.pa.mail.comcast.net with comcast id pz4u1h00a1t3BNj3fz4u1w; Thu, 27 Oct 2011 23:04:55 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id EA5EE102C19; Thu, 27 Oct 2011 16:04:52 -0700 (PDT) Date: Thu, 27 Oct 2011 16:04:52 -0700 From: Jeremy Chadwick To: Vincent Hoffman Message-ID: <20111027230452.GA22060@icarus.home.lan> References: <4EA9E0C3.5080306@unsane.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4EA9E0C3.5080306@unsane.co.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable Mailing List Subject: Re: mfi timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 23:04:55 -0000 On Thu, Oct 27, 2011 at 11:52:51PM +0100, Vincent Hoffman wrote: > I've recently installed a new NAS at work which uses a rebranded LSI > megaraid sas > [root@banshee ~]# mfiutil show adapter > mfi0 Adapter: > Product Name: Supermicro SMC2108 > Serial Number: > Firmware: 12.12.0-0047 > RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 > Battery Backup: present > NVRAM: 32K > Onboard Memory: 512M > Minimum Stripe: 8k > Maximum Stripe: 1M > > I'm running 8-STABLE as of 2011-10-23 (for zfs v28 as is got 26 3Tb drives) > > I'm seeing a lot of messages like > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 60 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 90 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 120 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 150 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 180 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 210 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 240 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 271 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 301 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 331 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 361 SECONDS > mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 391 SECONDS > mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 55 SECONDS > mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 85 SECONDS > > At which time I'm seeing IO stall on the array connected to the mfi > adapter, this can continue for > 20 minutes or so resuming randomly (or so it seems although a little > more on this later on) > > >From pciconf -lv > mfi0@pci0:5:0:0: class=0x010400 card=0x070015d9 chip=0x00791000 > rev=0x04 hdr=0x00 > vendor = 'LSI Logic (Was: Symbios Logic, NCR)' > class = mass storage > subclass = RAID > > >From dmesg > mfi0: port 0xe000-0xe0ff mem > 0xfbd9c000-0xfbd9ffff,0xfbdc0000-0xfbdfffff irq 32 at device 0.0 on pci5 > mfi0: Megaraid SAS driver Ver 3.00 > mfi0: 12330 (372962922s/0x0020/info) - Shutdown command received from host > mfi0: 12331 (boot + 4s/0x0020/info) - Firmware initialization started > (PCI ID 0079/1000/0700/15d9) > mfi0: 12332 (boot + 4s/0x0020/info) - Firmware version 2.120.53-1235 > mfi0: 12333 (boot + 7s/0x0008/info) - Battery Present > mfi0: 12334 (boot + 7s/0x0020/info) - Package version 12.12.0-0047 > mfi0: 12335 (boot + 7s/0x0020/info) - Board Revision > > I have found this thread from a bit of googleing but it doesnt end too well. > http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.html > Was this ever taken further? > > One thing I have noticed is that the stall (and timeout messages) seem > to go away if I query the card using mfiutil, I currently have a cron > doing this every 2 minutes to see if this has been coincidence or not. > > > Any suggestions welcome and i'm happy to provide more info if i can but > I dont have a duplicate to do too much debugging on, I'm happy to try > patches though. > > Is this worth filing a PR? Can you please provide uname -a output? The version of FreeBSD you're using matters greatly here. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Oct 27 23:39:35 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5468E1065753 for ; Thu, 27 Oct 2011 23:39:35 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id A30038FC14 for ; Thu, 27 Oct 2011 23:39:34 +0000 (UTC) Received: from vhoffman-macbooklocal.local ([10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p9RNdXxr028478 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 28 Oct 2011 00:39:33 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4EA9EBB5.2090004@unsane.co.uk> Date: Fri, 28 Oct 2011 00:39:33 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Jeremy Chadwick References: <4EA9E0C3.5080306@unsane.co.uk> <20111027230452.GA22060@icarus.home.lan> In-Reply-To: <20111027230452.GA22060@icarus.home.lan> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List Subject: Re: mfi timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 23:39:35 -0000 On 28/10/2011 00:04, Jeremy Chadwick wrote: > On Thu, Oct 27, 2011 at 11:52:51PM +0100, Vincent Hoffman wrote: >> I've recently installed a new NAS at work which uses a rebranded LSI >> megaraid sas >> [root@banshee ~]# mfiutil show adapter >> mfi0 Adapter: >> Product Name: Supermicro SMC2108 >> Serial Number: >> Firmware: 12.12.0-0047 >> RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 >> Battery Backup: present >> NVRAM: 32K >> Onboard Memory: 512M >> Minimum Stripe: 8k >> Maximum Stripe: 1M >> >> I'm running 8-STABLE as of 2011-10-23 (for zfs v28 as is got 26 3Tb drives) >> >> I'm seeing a lot of messages like >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 60 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 90 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 120 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 150 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 180 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 210 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 240 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 271 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 301 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 331 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 361 SECONDS >> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 391 SECONDS >> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 55 SECONDS >> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 85 SECONDS >> >> At which time I'm seeing IO stall on the array connected to the mfi >> adapter, this can continue for >> 20 minutes or so resuming randomly (or so it seems although a little >> more on this later on) >> >> >From pciconf -lv >> mfi0@pci0:5:0:0: class=0x010400 card=0x070015d9 chip=0x00791000 >> rev=0x04 hdr=0x00 >> vendor = 'LSI Logic (Was: Symbios Logic, NCR)' >> class = mass storage >> subclass = RAID >> >> >From dmesg >> mfi0: port 0xe000-0xe0ff mem >> 0xfbd9c000-0xfbd9ffff,0xfbdc0000-0xfbdfffff irq 32 at device 0.0 on pci5 >> mfi0: Megaraid SAS driver Ver 3.00 >> mfi0: 12330 (372962922s/0x0020/info) - Shutdown command received from host >> mfi0: 12331 (boot + 4s/0x0020/info) - Firmware initialization started >> (PCI ID 0079/1000/0700/15d9) >> mfi0: 12332 (boot + 4s/0x0020/info) - Firmware version 2.120.53-1235 >> mfi0: 12333 (boot + 7s/0x0008/info) - Battery Present >> mfi0: 12334 (boot + 7s/0x0020/info) - Package version 12.12.0-0047 >> mfi0: 12335 (boot + 7s/0x0020/info) - Board Revision >> >> I have found this thread from a bit of googleing but it doesnt end too well. >> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.html >> Was this ever taken further? >> >> One thing I have noticed is that the stall (and timeout messages) seem >> to go away if I query the card using mfiutil, I currently have a cron >> doing this every 2 minutes to see if this has been coincidence or not. >> >> >> Any suggestions welcome and i'm happy to provide more info if i can but >> I dont have a duplicate to do too much debugging on, I'm happy to try >> patches though. >> >> Is this worth filing a PR? > Can you please provide uname -a output? The version of FreeBSD you're > using matters greatly here. > Sure FreeBSD banshee.foobar.net 8.2-STABLE FreeBSD 8.2-STABLE #2: Wed Oct 26 16:14:09 BST 2011 toor@banshee.foobar.net:/usr/obj/usr/src/sys/BANSHEE amd64 [root@banshee /usr/src]# svn info Path: . Working Copy Root Path: /usr/src URL: http://svn.freebsd.org/base/stable/8 Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 226708 Node Kind: directory Schedule: normal Last Changed Author: brueffer Last Changed Rev: 226671 Last Changed Date: 2011-10-23 19:37:57 +0100 (Sun, 23 Oct 2011) It's looking like the mfiutil query stopping the stall is not a coincidence the last 2 have lasted less than the every 2 minutes that i set the cron to run, much less than previously. The cron is a simple /usr/sbin/mfiutil show volumes | grep -v OPTIMAL So get at least get an email if the volume breaks ;) Oct 28 00:01:06 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER 59 SECONDS Oct 28 00:01:36 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER 89 SECONDS Oct 28 00:13:09 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER 50 SECONDS Oct 28 00:13:39 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER 80 SECONDS I'm guessing this must kick something on the card. Vince From owner-freebsd-stable@FreeBSD.ORG Fri Oct 28 03:41:13 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83ADE1065674 for ; Fri, 28 Oct 2011 03:41:13 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from midgard.transactionware.com (mail2.transactionware.com [203.14.245.36]) by mx1.freebsd.org (Postfix) with SMTP id E9C898FC0A for ; Fri, 28 Oct 2011 03:41:12 +0000 (UTC) Received: (qmail 45931 invoked by uid 907); 28 Oct 2011 03:14:29 -0000 Received: from jmmacpro.transactionware.com (HELO jmmacpro.transactionware.com) (192.168.1.33) by midgard.transactionware.com (qpsmtpd/0.82) with ESMTP; Fri, 28 Oct 2011 14:14:29 +1100 Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: Jan Mikkelsen In-Reply-To: <4EA9EBB5.2090004@unsane.co.uk> Date: Fri, 28 Oct 2011 14:14:28 +1100 Content-Transfer-Encoding: quoted-printable Message-Id: <992755CA-6479-4B9A-A3D5-DD5C1871089A@transactionware.com> References: <4EA9E0C3.5080306@unsane.co.uk> <20111027230452.GA22060@icarus.home.lan> <4EA9EBB5.2090004@unsane.co.uk> To: Vincent Hoffman X-Mailer: Apple Mail (2.1251.1) Cc: FreeBSD Stable Mailing List , Jeremy Chadwick Subject: Re: mfi timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 03:41:13 -0000 Hi, There is a patch linked to from this PR, which seems very similar: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/140416 http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html The problem is also consistent with running mfiutil clearing the = problem. I'm about to deploy mfi controllers in a similar configuration, so I'd = be very curious about whether the patch fixes the problem for you. Regards, Jan Mikkelsen On 28/10/2011, at 10:39 AM, Vincent Hoffman wrote: > On 28/10/2011 00:04, Jeremy Chadwick wrote: >> On Thu, Oct 27, 2011 at 11:52:51PM +0100, Vincent Hoffman wrote: >>> I've recently installed a new NAS at work which uses a rebranded = LSI >>> megaraid sas >>> [root@banshee ~]# mfiutil show adapter >>> mfi0 Adapter: >>> Product Name: Supermicro SMC2108 >>> Serial Number: >>> Firmware: 12.12.0-0047 >>> RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 >>> Battery Backup: present >>> NVRAM: 32K >>> Onboard Memory: 512M >>> Minimum Stripe: 8k >>> Maximum Stripe: 1M >>>=20 >>> I'm running 8-STABLE as of 2011-10-23 (for zfs v28 as is got 26 3Tb = drives) >>>=20 >>> I'm seeing a lot of messages like >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 60 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 90 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 120 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 150 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 180 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 210 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 240 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 271 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 301 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 331 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 361 SECONDS >>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 391 SECONDS >>> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 55 SECONDS >>> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 85 SECONDS >>>=20 >>> At which time I'm seeing IO stall on the array connected to the mfi >>> adapter, this can continue for >>> 20 minutes or so resuming randomly (or so it seems although a little >>> more on this later on) >>>=20 >>>> =46rom pciconf -lv >>> mfi0@pci0:5:0:0: class=3D0x010400 card=3D0x070015d9 = chip=3D0x00791000 >>> rev=3D0x04 hdr=3D0x00 >>> vendor =3D 'LSI Logic (Was: Symbios Logic, NCR)' >>> class =3D mass storage >>> subclass =3D RAID >>>=20 >>>> =46rom dmesg >>> mfi0: port 0xe000-0xe0ff mem >>> 0xfbd9c000-0xfbd9ffff,0xfbdc0000-0xfbdfffff irq 32 at device 0.0 on = pci5 >>> mfi0: Megaraid SAS driver Ver 3.00 >>> mfi0: 12330 (372962922s/0x0020/info) - Shutdown command received = from host >>> mfi0: 12331 (boot + 4s/0x0020/info) - Firmware initialization = started >>> (PCI ID 0079/1000/0700/15d9) >>> mfi0: 12332 (boot + 4s/0x0020/info) - Firmware version 2.120.53-1235 >>> mfi0: 12333 (boot + 7s/0x0008/info) - Battery Present >>> mfi0: 12334 (boot + 7s/0x0020/info) - Package version 12.12.0-0047 >>> mfi0: 12335 (boot + 7s/0x0020/info) - Board Revision >>>=20 >>> I have found this thread from a bit of googleing but it doesnt end = too well. >>> = http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.ht= ml >>> Was this ever taken further? >>>=20 >>> One thing I have noticed is that the stall (and timeout messages) = seem >>> to go away if I query the card using mfiutil, I currently have a = cron >>> doing this every 2 minutes to see if this has been coincidence or = not. >>>=20 >>>=20 >>> Any suggestions welcome and i'm happy to provide more info if i can = but >>> I dont have a duplicate to do too much debugging on, I'm happy to = try >>> patches though. >>>=20 >>> Is this worth filing a PR? >> Can you please provide uname -a output? The version of FreeBSD = you're >> using matters greatly here. >>=20 > Sure > FreeBSD banshee.foobar.net 8.2-STABLE FreeBSD 8.2-STABLE #2: Wed Oct = 26 > 16:14:09 BST 2011 =20 > toor@banshee.foobar.net:/usr/obj/usr/src/sys/BANSHEE amd64 > [root@banshee /usr/src]# svn info > Path: . > Working Copy Root Path: /usr/src > URL: http://svn.freebsd.org/base/stable/8 > Repository Root: http://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 226708 > Node Kind: directory > Schedule: normal > Last Changed Author: brueffer > Last Changed Rev: 226671 > Last Changed Date: 2011-10-23 19:37:57 +0100 (Sun, 23 Oct 2011) >=20 >=20 > It's looking like the mfiutil query stopping the stall is not a = coincidence > the last 2 have lasted less than the every 2 minutes that i set the = cron > to run, much less than previously. > The cron is a simple /usr/sbin/mfiutil show volumes | grep -v OPTIMAL=20= > So get at least get an email if the volume breaks ;) > Oct 28 00:01:06 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER > 59 SECONDS > Oct 28 00:01:36 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER > 89 SECONDS > Oct 28 00:13:09 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER > 50 SECONDS > Oct 28 00:13:39 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER > 80 SECONDS >=20 > I'm guessing this must kick something on the card. >=20 > Vince >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Fri Oct 28 05:18:10 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A725A106566C for ; Fri, 28 Oct 2011 05:18:10 +0000 (UTC) (envelope-from ktouet@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 31E138FC0A for ; Fri, 28 Oct 2011 05:18:09 +0000 (UTC) Received: by wwi18 with SMTP id 18so5063155wwi.31 for ; Thu, 27 Oct 2011 22:18:09 -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; bh=GPBBr769h38uKzj9PQCGVnf5RjPqy4+1GAjMG59ULPo=; b=qF8Aj0vu+eAJ23nTbIhji0Gf403ZZo1oPtYpa+KXo0yBLxqZSrT4B/d+ejBLrcPXHc ZUPC9eW1zc5n7TN20KUR9griD8Yrqm/Ez1fhhBzHt9xtrtEWB9CC/hLaTnduPBiuwMdM wH6vXeCVUZKnPoQYNkLoEdslSqZoUtES98vNA= MIME-Version: 1.0 Received: by 10.216.229.94 with SMTP id g72mr268100weq.74.1319777231016; Thu, 27 Oct 2011 21:47:11 -0700 (PDT) Received: by 10.216.37.19 with HTTP; Thu, 27 Oct 2011 21:47:10 -0700 (PDT) Date: Thu, 27 Oct 2011 22:47:10 -0600 Message-ID: From: Kurt Touet To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Unable to compile stable/9 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 05:18:10 -0000 I am currently running FreeBSD amd64 stable/9 r225905, and I have been unable to compile the stable/9 branch for the past couple of weeks. On the chance that there were any oddities in my source-tree, I have completely erased and checked out svn://svn.freebsd.org/base/stable/9 from scratch. With r226876, I continue to have compilation errors. I believe it is continuing to break in the same place during buildworld, as shown below. Is this to be expected ATM? Is the branch broken? Is this an unrelated gcc error? Or is there something I'm missing? Thanks, -kurt ===> lib/clang/libclangarcmigrate (all) c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/ARCMTActions.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/FileRemapper.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/ARCMT.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/TransARCAssign.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/TransAutoreleasePool.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/TransBlockObjCVariable.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/TransEmptyStatementsAndDealloc.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/TransformActions.cpp c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector -fno-exceptions -fno-rtti -c /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/Transforms.cpp c++: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See for instructions. *** Error code 1 {standard input}: Assembler messages: {standard input}:4358: Warning: end of file not at end of a line; newline inserted {standard input}:4595: Error: no such instruction: `mo' c++: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See for instructions. *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error From owner-freebsd-stable@FreeBSD.ORG Fri Oct 28 05:59:58 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DDA7106566C for ; Fri, 28 Oct 2011 05:59:58 +0000 (UTC) (envelope-from apache@asoft144.accrisoft.com) Received: from asoft144.accrisoft.com (asoft144.accrisoft.com [140.174.90.226]) by mx1.freebsd.org (Postfix) with ESMTP id EB6DE8FC08 for ; Fri, 28 Oct 2011 05:59:57 +0000 (UTC) Received: from asoft144.accrisoft.com (localhost.localdomain [127.0.0.1]) by asoft144.accrisoft.com (8.14.4/8.13.1) with ESMTP id p9S40qib023595 for ; Fri, 28 Oct 2011 00:00:52 -0400 Received: (from apache@localhost) by asoft144.accrisoft.com (8.14.4/8.14.4/Submit) id p9S40qeV023586; Fri, 28 Oct 2011 00:00:52 -0400 Date: Fri, 28 Oct 2011 00:00:52 -0400 To: Friends From: Purchased Download Message-ID: <06e0ccb63c13f44075019118c5cd5e97@vampiweb.org> X-Priority: 3 X-Mailer: PHPMailer (phpmailer.codeworxtech.com) [version 2.3] X-Sender: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="iso-8859-1" Subject: Download this ONLY working *ABSOLUTE GUARANTEED FREE ENERGY DEVICE* ever invented that actually produces free electricity out of thin air X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Purchased Download List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 05:59:58 -0000 Hello, From: Purchased Download (sadakokaboomotor@motorjakmagnets.com) The person above has sent you the following message: [ IMPORTANT ] ............ [ http://fzy.co/B5j ] The United States Patent and Trademark Office awarded the `HoJo Motor` 3 U.S. Patents for being the ONLY working `free energy device` ever invented that actually produces free electricity out of thin air! . This is the real deal! rushed to the appliance store and got all the parts for 92 bucks. http://fzy.co/B5j It took me approx. three hours to build my first device... and I built a second, larger one in under an hour! We`ve already cut our electricity bill by 60 percent and planning on building a new generator next week... we`ll let you know how it goes! http://fzy.co/B5j http://fzy.co/B5j Wishing All the best, Dean Schrock, Denver, Colorado http://fzy.co/B5j http://fzy.co/B5j Click below to view the page: http://fzy.co/4Yj From owner-freebsd-stable@FreeBSD.ORG Fri Oct 28 13:15:34 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91BD0106564A for ; Fri, 28 Oct 2011 13:15:34 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id F06B98FC0C for ; Fri, 28 Oct 2011 13:15:33 +0000 (UTC) Received: from j.reilly.is.the.monkeylord.now.get.back.to.work.peon (j.reilly.is.the.monkeylord.now.get.back.to.work.peon [85.233.185.164] (may be forged)) (authenticated bits=0) by unsane.co.uk (8.14.4/8.14.4) with ESMTP id p9SDFVHp006982 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 28 Oct 2011 14:15:32 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4EAAAAF2.3030608@unsane.co.uk> Date: Fri, 28 Oct 2011 14:15:30 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Jan Mikkelsen References: <4EA9E0C3.5080306@unsane.co.uk> <20111027230452.GA22060@icarus.home.lan> <4EA9EBB5.2090004@unsane.co.uk> <992755CA-6479-4B9A-A3D5-DD5C1871089A@transactionware.com> In-Reply-To: <992755CA-6479-4B9A-A3D5-DD5C1871089A@transactionware.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Mailing List , Jeremy Chadwick Subject: Re: mfi timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2011 13:15:34 -0000 On 28/10/2011 04:14, Jan Mikkelsen wrote: > Hi, > > There is a patch linked to from this PR, which seems very similar: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416 > > http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html > > The problem is also consistent with running mfiutil clearing the problem. > > I'm about to deploy mfi controllers in a similar configuration, so I'd be very curious about whether the patch fixes the problem for you. > This looks promising, I'll give a try when I get a moment. Thanks, Vince > Regards, > > Jan Mikkelsen > > > On 28/10/2011, at 10:39 AM, Vincent Hoffman wrote: > >> On 28/10/2011 00:04, Jeremy Chadwick wrote: >>> On Thu, Oct 27, 2011 at 11:52:51PM +0100, Vincent Hoffman wrote: >>>> I've recently installed a new NAS at work which uses a rebranded LSI >>>> megaraid sas >>>> [root@banshee ~]# mfiutil show adapter >>>> mfi0 Adapter: >>>> Product Name: Supermicro SMC2108 >>>> Serial Number: >>>> Firmware: 12.12.0-0047 >>>> RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 >>>> Battery Backup: present >>>> NVRAM: 32K >>>> Onboard Memory: 512M >>>> Minimum Stripe: 8k >>>> Maximum Stripe: 1M >>>> >>>> I'm running 8-STABLE as of 2011-10-23 (for zfs v28 as is got 26 3Tb drives) >>>> >>>> I'm seeing a lot of messages like >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 60 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 90 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 120 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 150 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 180 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 210 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 240 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 271 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 301 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 331 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 361 SECONDS >>>> mfi0: COMMAND 0xffffff8000b216c8 TIMEOUT AFTER 391 SECONDS >>>> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 55 SECONDS >>>> mfi0: COMMAND 0xffffff8000b21b08 TIMEOUT AFTER 85 SECONDS >>>> >>>> At which time I'm seeing IO stall on the array connected to the mfi >>>> adapter, this can continue for >>>> 20 minutes or so resuming randomly (or so it seems although a little >>>> more on this later on) >>>> >>>>> From pciconf -lv >>>> mfi0@pci0:5:0:0: class=0x010400 card=0x070015d9 chip=0x00791000 >>>> rev=0x04 hdr=0x00 >>>> vendor = 'LSI Logic (Was: Symbios Logic, NCR)' >>>> class = mass storage >>>> subclass = RAID >>>> >>>>> From dmesg >>>> mfi0: port 0xe000-0xe0ff mem >>>> 0xfbd9c000-0xfbd9ffff,0xfbdc0000-0xfbdfffff irq 32 at device 0.0 on pci5 >>>> mfi0: Megaraid SAS driver Ver 3.00 >>>> mfi0: 12330 (372962922s/0x0020/info) - Shutdown command received from host >>>> mfi0: 12331 (boot + 4s/0x0020/info) - Firmware initialization started >>>> (PCI ID 0079/1000/0700/15d9) >>>> mfi0: 12332 (boot + 4s/0x0020/info) - Firmware version 2.120.53-1235 >>>> mfi0: 12333 (boot + 7s/0x0008/info) - Battery Present >>>> mfi0: 12334 (boot + 7s/0x0020/info) - Package version 12.12.0-0047 >>>> mfi0: 12335 (boot + 7s/0x0020/info) - Board Revision >>>> >>>> I have found this thread from a bit of googleing but it doesnt end too well. >>>> http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/063821.html >>>> Was this ever taken further? >>>> >>>> One thing I have noticed is that the stall (and timeout messages) seem >>>> to go away if I query the card using mfiutil, I currently have a cron >>>> doing this every 2 minutes to see if this has been coincidence or not. >>>> >>>> >>>> Any suggestions welcome and i'm happy to provide more info if i can but >>>> I dont have a duplicate to do too much debugging on, I'm happy to try >>>> patches though. >>>> >>>> Is this worth filing a PR? >>> Can you please provide uname -a output? The version of FreeBSD you're >>> using matters greatly here. >>> >> Sure >> FreeBSD banshee.foobar.net 8.2-STABLE FreeBSD 8.2-STABLE #2: Wed Oct 26 >> 16:14:09 BST 2011 >> toor@banshee.foobar.net:/usr/obj/usr/src/sys/BANSHEE amd64 >> [root@banshee /usr/src]# svn info >> Path: . >> Working Copy Root Path: /usr/src >> URL: http://svn.freebsd.org/base/stable/8 >> Repository Root: http://svn.freebsd.org/base >> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >> Revision: 226708 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: brueffer >> Last Changed Rev: 226671 >> Last Changed Date: 2011-10-23 19:37:57 +0100 (Sun, 23 Oct 2011) >> >> >> It's looking like the mfiutil query stopping the stall is not a coincidence >> the last 2 have lasted less than the every 2 minutes that i set the cron >> to run, much less than previously. >> The cron is a simple /usr/sbin/mfiutil show volumes | grep -v OPTIMAL >> So get at least get an email if the volume breaks ;) >> Oct 28 00:01:06 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER >> 59 SECONDS >> Oct 28 00:01:36 banshee mfi0: COMMAND 0xffffff8000b22d18 TIMEOUT AFTER >> 89 SECONDS >> Oct 28 00:13:09 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER >> 50 SECONDS >> Oct 28 00:13:39 banshee mfi0: COMMAND 0xffffff8000b205c8 TIMEOUT AFTER >> 80 SECONDS >> >> I'm guessing this must kick something on the card. >> >> Vince >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sat Oct 29 20:56:31 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 629BC1065677 for ; Sat, 29 Oct 2011 20:56:31 +0000 (UTC) (envelope-from subbsd@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 1BBEA8FC0C for ; Sat, 29 Oct 2011 20:56:30 +0000 (UTC) Received: by vcbfk26 with SMTP id fk26so219714vcb.13 for ; Sat, 29 Oct 2011 13:56:30 -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:content-transfer-encoding; bh=QokBMfzXYd8p+30QNcypTiRHi5uBkLw7RIu28U0XFVk=; b=IwoyCXJs7WSVe5gDvk14pdDFfOqss3+opDhGIyTNHif0hK4KK1a75EtLyBBftJszNj Wbq71P0z2j3ujGsu0daeqUlEBMKI+EnTery75Oi0R6YluRlbWmiaIqM84o6q9WyabJKA 8ugdzsRMcUMSunryQJPdnZf7vK4SDomkMf/eg= MIME-Version: 1.0 Received: by 10.220.151.207 with SMTP id d15mr1250170vcw.249.1319921790354; Sat, 29 Oct 2011 13:56:30 -0700 (PDT) Received: by 10.220.160.197 with HTTP; Sat, 29 Oct 2011 13:56:30 -0700 (PDT) In-Reply-To: References: Date: Sun, 30 Oct 2011 00:56:30 +0400 Message-ID: From: Subbsd To: George Kontostanos Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: problem with whereis rar and portinstall on the fresh installation of FreeBSD 9.0-RC1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2011 20:56:31 -0000 On Sat, Oct 22, 2011 at 1:51 PM, George Kontostanos wrote: > On Fri, Oct 21, 2011 at 12:28 PM, Subbsd wrote: >> > I had the same problem. It was solved by recompiling rubby1-8, and > performing a portsnap fetch extract again. > I have found that this behavior arises if to remove portupgrade checkbox by default "BDB4 Use Berkeley DB> =3D 2 as backend" When I returned back to this dependency (installed ruby =E2=80=8B=E2=80=8B{= 18,19}-bdb) - the upgrade process was successful It turns out that this option is obligatory and it shouldn't be removed. Th= anks. > > -- > George Kontostanos > aisecure.net > From owner-freebsd-stable@FreeBSD.ORG Sat Oct 29 21:55:58 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E466F106566B for ; Sat, 29 Oct 2011 21:55:58 +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 A77B98FC14 for ; Sat, 29 Oct 2011 21:55:58 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:89e1:b26d:b9ae:d0c1] (unknown [IPv6:2001:7b8:3a7:0:89e1:b26d:b9ae:d0c1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 91CCE5C37; Sat, 29 Oct 2011 23:55:57 +0200 (CEST) Message-ID: <4EAC7672.5020702@FreeBSD.org> Date: Sat, 29 Oct 2011 23:56:02 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111019 Thunderbird/8.0 MIME-Version: 1.0 To: Kurt Touet References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Unable to compile stable/9 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2011 21:55:59 -0000 On 2011-10-28 06:47, Kurt Touet wrote: > I am currently running FreeBSD amd64 stable/9 r225905, and I have been > unable to compile the stable/9 branch for the past couple of weeks. > On the chance that there were any oddities in my source-tree, I have > completely erased and checked out svn://svn.freebsd.org/base/stable/9 > from scratch. With r226876, I continue to have compilation errors. I > believe it is continuing to break in the same place during buildworld, > as shown below. > > Is this to be expected ATM? Is the branch broken? Is this an > unrelated gcc error? Or is there something I'm missing? ... > c++ -O2 -pipe -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/include > -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/include > -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate > -I. -I/usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/../../lib/clang/include > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS > -D__STDC_CONSTANT_MACROS > -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd9.0\" -fstack-protector > -fno-exceptions -fno-rtti -c > /usr/src/lib/clang/libclangarcmigrate/../../../contrib/llvm/tools/clang/lib/ARCMigrate/Transforms.cpp > c++: Internal error: Killed: 9 (program cc1plus) You are most likely running out of memory. Check dmesg and/or log messages for 'out of swap swace' errors. You can try freeing up RAM, running with a lower -j setting (if applicable), or adding swap.