From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 06:19:06 2008 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 0E5CD16A418 for ; Sun, 17 Feb 2008 06:19:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 08BB413C45D for ; Sun, 17 Feb 2008 06:19:05 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id DDFC11CC033; Sat, 16 Feb 2008 22:19:05 -0800 (PST) Date: Sat, 16 Feb 2008 22:19:05 -0800 From: Jeremy Chadwick To: "Carlos A. M. dos Santos" Message-ID: <20080217061905.GA35005@eos.sc1.parodius.com> References: <20080216210736.GA17517@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 06:19:06 -0000 On Sat, Feb 16, 2008 at 09:08:38PM -0200, Carlos A. M. dos Santos wrote: > On Feb 16, 2008 7:07 PM, Jeremy Chadwick wrote: > > Is anyone aware of the situation where FreeBSD behaves erratically when > > a disk is physically removed without "atacontrol detach ataX" being run > > prior to removal (at least on RELENG_7)? > > Yes, I have seen this since 4.5, IIRC. Wonderful. > > Also FWIW: I also tested all this for comparison on Ubuntu Linux earlier > > this morning. I was able to yank the disk in the middle of an I/O > > operation, resulting in an immediate I/O error from dd. I took no > > precautions prior to yanking the disk. Upon reinsertion, the system > > found the disk and I could continue I/O operations on it as if it had > > never been removed. Only reason I'm pointing this out is that it > > confirms the issue isn't hardware or with vendor implementation, but > > rather specific to the OS. > > Congratulations to the Linux folks. Or not, since this looks like a > very risky behavior. Who warrants you that the *same* disk was plugged > back? Blindly continuing to write could easily corrupt the contents of > the second drive. I'm not sure I understand. There were no filesystems on the drive, and nothing mounted prior to removal: just like what I did with FreeBSD. The procedure: * Boot Ubuntu CD, get a shell * dd if=/dev/sdb of=/dev/null bs=8k * In the middle of I/O, yank the disk * dd exits with "I/O error" * System continued to be responsive; no ATA subsystem oddities * Reinserted disk; kernel saw the disk without any issue * dd if=/dev/sdb of=/dev/null bs=8k * I/O still operating as before; no system "oddities" If you'd like, I can try inserting a completely different disk (both in size and vendor), but I really don't think anything odd will happen. If there were filesystems mounted or other whatnots, yes, I could see how there might be concern. I can try that as well if you're interested. I am a bit curious to see what Linux does if I pull a disk that has mounted filesystems which are being accessed at the time. This test was done solely to see how FreeBSD behaved when a disk was removed. The fact that the entire ATA channel goes into some bizarre non-recoverable state when a disk is removed without detaching first warrants the need for investigation, especially if this behaviour has existed since the mid-4.x days. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 07:25:50 2008 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 D3B0B16A417 for ; Sun, 17 Feb 2008 07:25:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail26.yandex.ru (webmail26.yandex.ru [213.180.200.91]) by mx1.freebsd.org (Postfix) with ESMTP id 7003E13C447 for ; Sun, 17 Feb 2008 07:25:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail26) by mail.yandex.ru id S1736723AbYBQHZk for ; Sun, 17 Feb 2008 10:25:40 +0300 X-Yandex-Spam: 0 Received: from [77.72.136.70] ([77.72.136.70]) by mail.yandex.ru with HTTP; Sun, 17 Feb 2008 10:25:40 +0300 From: "Andrey V. Elsukov" To: unixmania@gmail.com In-Reply-To: 9060000000163393529 References: <20080216210736.GA17517@eos.sc1.parodius.com> 9060000000163393529 MIME-Version: 1.0 Message-Id: <886021203233140@webmail26.yandex.ru> Date: Sun, 17 Feb 2008 10:25:40 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 07:25:50 -0000 17.02.08, 02:08, "Carlos A. M. dos Santos" : > > precautions prior to yanking the disk. Upon reinsertion, the system > > found the disk and I could continue I/O operations on it as if it had > > never been removed. Only reason I'm pointing this out is that it > > confirms the issue isn't hardware or with vendor implementation, but > > rather specific to the OS. > Congratulations to the Linux folks. Or not, since this looks like a > very risky behavior. Who warrants you that the *same* disk was plugged > back? Blindly continuing to write could easily corrupt the contents of > the second drive. There is no risk. Linux's libata detects it when you inserts a different disk. You can read some details here: http://www.mail-archive.com/linux-ide@vger.kernel.org/msg11742.html -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 07:35:29 2008 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 5E20B16A41A for ; Sun, 17 Feb 2008 07:35:29 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 2F11613C455 for ; Sun, 17 Feb 2008 07:35:29 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so1516917pyb.10 for ; Sat, 16 Feb 2008 23:35:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=U7Ta/m9P7tYkZGpZFe4fgcJde8zpcnSZnOam/7JGOfA=; b=vr+X6Ys+abbeHiHSVsUQbSnA8Gy0Yb5oA8/KScmK7VZyS44kqNP87YH8j8NebWomw2vGzEDU2bSottoYXenWy3YKRYg4WvuaaXzukb9wE1lSSxTz/kOXgVuUnR8IzO6XqQVlS8JOWuObUkF2DsfZA2PMkFPHE3eblGeOkMyYRPA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=Yi2rdvqXMp7xxbxaUn5s483nEgEdNS3JuTtdBS0rOVicMFN2Oh5b7wIaKdHV/qNbZYFs0wR7NLjgGsYJOEKz1RBnu6MLJfGSWVTTCzcLXhfhc4lccTS8wond4MT7Ao0vV8qnqUeD+uP7EEHvM6iP/CJ2TNh2bbyVc4PBwCInU9A= Received: by 10.65.158.9 with SMTP id k9mr7652534qbo.47.1203233728248; Sat, 16 Feb 2008 23:35:28 -0800 (PST) Received: by 10.64.232.17 with HTTP; Sat, 16 Feb 2008 23:35:28 -0800 (PST) Message-ID: Date: Sun, 17 Feb 2008 09:35:28 +0200 From: "David Naylor" Sender: naylor.b.david@gmail.com To: freebsd-stable@freebsd.org, blackdragon@highveldmail.co.za MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: c8ff8c7f4384b16d Cc: Subject: tmpfs: strange behaviour (was: broken buildkernel (scsi_low and -Os) and duplicate manpages) 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, 17 Feb 2008 07:35:29 -0000 On 14/02/2008, Oliver Fromme wrote: > David Naylor wrote: > > It is a strange problem, normal installworld works fine, but somehow > > the duplicate manpages result in a failure when installing with > > DESTDIR=, here are some possible reasons: > > > > 1) I use tmpfs when using DESTDIR (could be tmpfs does something strange) > > 2) Base system (compiled and installed) is compiled using -O2??? > > What is the exact CFLAGS setting that you use? > Do you use -O2 (or -Os) without -fno-strict-aliasing? I have managed to isolate the problem and it is definitely tmpfs related. If the directory that I'm installing into is tmpfs then it will fail, if it is ufs then it works. I recompiled tmpfs module (and reloaded) with CFLAGS='' with the same result. As an aside I have found that the default CFLAGS for src are: -O2 -fno-strict-aliasing -pipe. Would -fstrict-aliasing break anything in base/sys? David From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 09:46:30 2008 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 59F1416A41A; Sun, 17 Feb 2008 09:46:30 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 2107B13C458; Sun, 17 Feb 2008 09:46:29 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 5F7FA19E019; Sun, 17 Feb 2008 10:27:58 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id CCCA419E023; Sun, 17 Feb 2008 10:27:55 +0100 (CET) Message-ID: <47B7FE2A.50502@quip.cz> Date: Sun, 17 Feb 2008 10:28:10 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: Jeremy Chadwick References: <20080216210736.GA17517@eos.sc1.parodius.com> In-Reply-To: <20080216210736.GA17517@eos.sc1.parodius.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 09:46:30 -0000 Jeremy Chadwick wrote: > Is anyone aware of the situation where FreeBSD behaves erratically when > a disk is physically removed without "atacontrol detach ataX" being run > prior to removal (at least on RELENG_7)? I can confirm this behaviour on FreeBSD 6.2. It sometimes freezes or panic when I atacontrol detach ataX and then physically remove the disk. (disk is used in gmirror). I saw some panics on reinsertion too. The strange is that it behaves better when disk is removed / reinserted without detaching ata channnel by atacontrol. (tested on Sun Fire X2100) Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 10:44:55 2008 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 C73C816A41B for ; Sun, 17 Feb 2008 10:44:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 7F1BD13C448 for ; Sun, 17 Feb 2008 10:44:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JQh0u-0006Q7-5T for freebsd-stable@freebsd.org; Sun, 17 Feb 2008 12:44:54 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m1HAiB1Z050895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Feb 2008 12:44:11 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m1HAiWNP048141; Sun, 17 Feb 2008 12:44:32 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m1HAiVFj048140; Sun, 17 Feb 2008 12:44:31 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 17 Feb 2008 12:44:31 +0200 From: Kostik Belousov To: David Naylor Message-ID: <20080217104431.GN57756@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="b5bTySBq8oFySjZL" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 717fb1dce93df3d9117221529acf11a8 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2246 [Feb 15 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release Cc: freebsd-stable@freebsd.org Subject: Re: tmpfs: strange behaviour (was: broken buildkernel (scsi_low and -Os) and duplicate manpages) 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, 17 Feb 2008 10:44:55 -0000 --b5bTySBq8oFySjZL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 17, 2008 at 09:35:28AM +0200, David Naylor wrote: > On 14/02/2008, Oliver Fromme wrote: > > David Naylor wrote: > > > It is a strange problem, normal installworld works fine, but somehow > > > the duplicate manpages result in a failure when installing with > > > DESTDIR=3D, here are some possible reasons: > > > > > > 1) I use tmpfs when using DESTDIR (could be tmpfs does something str= ange) > > > 2) Base system (compiled and installed) is compiled using -O2??? > > > > What is the exact CFLAGS setting that you use? > > Do you use -O2 (or -Os) without -fno-strict-aliasing? > I have managed to isolate the problem and it is definitely tmpfs > related. If the directory that I'm installing into is tmpfs then it > will fail, if it is ufs then it works. >=20 > I recompiled tmpfs module (and reloaded) with CFLAGS=3D'' with the same r= esult. >=20 > As an aside I have found that the default CFLAGS for src are: -O2 > -fno-strict-aliasing -pipe. Would -fstrict-aliasing break anything in > base/sys? I suspect this is a known issue. See the following commit: delphij 2007-11-18 04:52:41 UTC FreeBSD src repository Modified files: sys/fs/tmpfs tmpfs.h tmpfs_subr.c tmpfs_vfsops.c=20 tmpfs_vnops.c=20 Log: MFp4: Several fixes to tmpfs which makes it to survive from pho@'s strees2 suite, to quote his letter, this change: =20 1. It removes the tn_lookup_dirent stuff. I think this cannot be fixed, because nothing protects vnode/tmpfs node between lookup is done, and actual operation is performed, in the case the vnode lock is dropped. At least, this is the case with the from vnode for rename. =20 For now, we do the linear lookup in the parent node. This has its own drawbacks. Not mentioning speed (that could be fixed by using hash), t= he real problem is the situation where several hardlinks exist in the dvp. But, I think this is fixable. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Esp. this part. =20 2. The patch restores the VV_ROOT flag on the root vnode after it became reclaimed and allocated again. This fixes MPASS assertion at the start of the tmpfs_lookup() reported by many. =20 Submitted by: kib =20 Revision Changes Path 1.12 +2 -6 src/sys/fs/tmpfs/tmpfs.h 1.13 +25 -3 src/sys/fs/tmpfs/tmpfs_subr.c 1.14 +0 -1 src/sys/fs/tmpfs/tmpfs_vfsops.c 1.12 +19 -23 src/sys/fs/tmpfs/tmpfs_vnops.c --b5bTySBq8oFySjZL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAke4EA4ACgkQC3+MBN1Mb4jgcgCgs7/8yHTjrp+lDcSdqwm1thtY lDoAmwSSHYltWWHvdWQRauYbjvdsYo3d =veEp -----END PGP SIGNATURE----- --b5bTySBq8oFySjZL-- From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 13:51:53 2008 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 909E716A41A for ; Sun, 17 Feb 2008 13:51:53 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.184]) by mx1.freebsd.org (Postfix) with ESMTP id 276F513C43E for ; Sun, 17 Feb 2008 13:51:52 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: by gv-out-0910.google.com with SMTP id n40so141759gve.39 for ; Sun, 17 Feb 2008 05:51:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gCxuP5J7Qai67+LeehHRkMH7cT53e7HxOTYwgVmk4Oc=; b=sa27QTQ7VhyA78gR52V7s7LeiJuZvZe2fvEWGgGD1t4Ontcbh5+AYx8L9fRJzHQsASdjzAAAb1r7tZ9qJpgiJ93kFw6JiXoPOutBU6I52T6JJAbZZ6iS9/InBB24FUbTTr0UP0xWQgIrmrNEn+5J8Wju6IyQByNsdr/keOcDe8w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Xv8DQU08jfyaUXj4I3s8EQwAyz9RQd6pQnRdYBMyJ3kkOnC/h5aZDN6ZFK6LKfsF6bItn4Q2nh4y+Vct5zAfqiTJyM2IFV2A0gsITjQQiCDszJ4SPgnwx0WFfA18vxEJ23BF7aH8z4P+MEB1znuP7tMhJHT/VRHAGsry6CLCJyA= Received: by 10.66.243.13 with SMTP id q13mr1920706ugh.59.1203256311266; Sun, 17 Feb 2008 05:51:51 -0800 (PST) Received: by 10.67.95.3 with HTTP; Sun, 17 Feb 2008 05:51:51 -0800 (PST) Message-ID: Date: Sun, 17 Feb 2008 10:51:51 -0300 From: "Carlos A. M. dos Santos" To: freebsd-stable@freebsd.org In-Reply-To: <886021203233140@webmail26.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080216210736.GA17517@eos.sc1.parodius.com> <886021203233140@webmail26.yandex.ru> Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 13:51:53 -0000 On Feb 17, 2008 4:25 AM, Andrey V. Elsukov wrote: > 17.02.08, 02:08, "Carlos A. M. dos Santos" : > > > > precautions prior to yanking the disk. Upon reinsertion, the system > > > > found the disk and I could continue I/O operations on it as if it had > > > > never been removed. Only reason I'm pointing this out is that it > > > > confirms the issue isn't hardware or with vendor implementation, but > > > > rather specific to the OS. > > > Congratulations to the Linux folks. Or not, since this looks like a > > > very risky behavior. Who warrants you that the *same* disk was plugged > > > back? Blindly continuing to write could easily corrupt the contents of > > > the second drive. > > > > There is no risk. Linux's libata detects it when you inserts a different disk. > > > > You can read some details here: > > http://www.mail-archive.com/linux-ide@vger.kernel.org/msg11742.html Quoting the message you pointed out: "You might lose cached and in-flight data of course, and userspace applications may or may not handle the disappearance of their underlying filesystem with grace and aplomb :)" Perhaps you believe that allowing userland applications to lose data is not risky. I strongly disagree. -- Carlos A. M. dos Santos From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 14:03:33 2008 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 1DED516A418 for ; Sun, 17 Feb 2008 14:03:33 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 9956413C45B for ; Sun, 17 Feb 2008 14:03:32 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so436096uge.37 for ; Sun, 17 Feb 2008 06:03:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=y0dsBs+E+8NZGbFF1qBTMOwtUIo48JRQJ5YMyhszxd8=; b=sNxL6E3hrmEl+/2AoJV2BEU3y1lMg+182zJWxqtjDwxzbZeBtwOzG1HYM+y+f8m/2FAIGO5iS7UFyVCDqR2td2Ro2rgzT9uMPETVJYbcrE+IWC0eAyy4YOFRp1RsvBYgFe82g9Kifd0XqoUQTi+4g/5DlXYvzaPfp2bNcFgIsA8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=i1SoojahGJhO8T+JLW/jb0o8Ikr7vy7xl384E9MJT3z/RWeFVnFK1yipXl9mVzTJzcx9R8D03fOt/1FaoNEPOHe92VtbLCvMrBMRz2XXzxtmiMmBXIjeVERiedGf54oN6seWF5vrfQecIJXrYP7oEpMwq0nkdJw9CYFO+w8Pv5Y= Received: by 10.66.237.14 with SMTP id k14mr1922612ugh.72.1203257011118; Sun, 17 Feb 2008 06:03:31 -0800 (PST) Received: by 10.67.95.3 with HTTP; Sun, 17 Feb 2008 06:03:31 -0800 (PST) Message-ID: Date: Sun, 17 Feb 2008 11:03:31 -0300 From: "Carlos A. M. dos Santos" To: freebsd-stable@freebsd.org In-Reply-To: <20080217061905.GA35005@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080216210736.GA17517@eos.sc1.parodius.com> <20080217061905.GA35005@eos.sc1.parodius.com> Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 14:03:33 -0000 On Feb 17, 2008 3:19 AM, Jeremy Chadwick wrote: > On Sat, Feb 16, 2008 at 09:08:38PM -0200, Carlos A. M. dos Santos wrote: > > On Feb 16, 2008 7:07 PM, Jeremy Chadwick wrote: > > > Is anyone aware of the situation where FreeBSD behaves erratically when > > > a disk is physically removed without "atacontrol detach ataX" being run > > > prior to removal (at least on RELENG_7)? > > > > Yes, I have seen this since 4.5, IIRC. > > Wonderful. > > > > Also FWIW: I also tested all this for comparison on Ubuntu Linux earlier > > > this morning. I was able to yank the disk in the middle of an I/O > > > operation, resulting in an immediate I/O error from dd. I took no > > > precautions prior to yanking the disk. Upon reinsertion, the system > > > found the disk and I could continue I/O operations on it as if it had > > > never been removed. Only reason I'm pointing this out is that it > > > confirms the issue isn't hardware or with vendor implementation, but > > > rather specific to the OS. > > > > Congratulations to the Linux folks. Or not, since this looks like a > > very risky behavior. Who warrants you that the *same* disk was plugged > > back? Blindly continuing to write could easily corrupt the contents of > > the second drive. > > I'm not sure I understand. There were no filesystems on the drive, and > nothing mounted prior to removal: just like what I did with FreeBSD. > The procedure: > > * Boot Ubuntu CD, get a shell > * dd if=/dev/sdb of=/dev/null bs=8k > * In the middle of I/O, yank the disk > * dd exits with "I/O error" > * System continued to be responsive; no ATA subsystem oddities > * Reinserted disk; kernel saw the disk without any issue > * dd if=/dev/sdb of=/dev/null bs=8k > * I/O still operating as before; no system "oddities" I'm still not convinced that this is a valid use case. > If you'd like, I can try inserting a completely different disk (both in > size and vendor), but I really don't think anything odd will happen. If > there were filesystems mounted or other whatnots, yes, I could see how > there might be concern. [...] This is exctly what I was talking about when I said "risky". > [...] I can try that as well if you're interested. I > am a bit curious to see what Linux does if I pull a disk that has > mounted filesystems which are being accessed at the time. Yes, do it please. I must admit [precious brat mode on] that I'm very curious about what would happen. :-) > This test was done solely to see how FreeBSD behaved when a disk was > removed. The fact that the entire ATA channel goes into some bizarre > non-recoverable state when a disk is removed without detaching first > warrants the need for investigation, especially if this behaviour has > existed since the mid-4.x days. > > -- > > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | -- Carlos A. M. dos Santos From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 14:31:44 2008 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 566AB16A418 for ; Sun, 17 Feb 2008 14:31:44 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail33.yandex.ru (webmail33.yandex.ru [213.180.223.180]) by mx1.freebsd.org (Postfix) with ESMTP id D530C13C457 for ; Sun, 17 Feb 2008 14:31:43 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail33) by mail.yandex.ru id S1082652AbYBQObj for ; Sun, 17 Feb 2008 17:31:39 +0300 X-Yandex-Spam: 0 Received: from [77.72.136.70] ([77.72.136.70]) by mail.yandex.ru with HTTP; Sun, 17 Feb 2008 17:31:39 +0300 From: "Andrey V. Elsukov" To: unixmania@gmail.com In-Reply-To: 9060000000163621627 References: <20080216210736.GA17517@eos.sc1.parodius.com> <886021203233140@webmail26.yandex.ru> 9060000000163621627 MIME-Version: 1.0 Message-Id: <2103371203258699@webmail33.yandex.ru> Date: Sun, 17 Feb 2008 17:31:39 +0300 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 14:31:44 -0000 17.02.08, 16:51, "Carlos A. M. dos Santos" : > Quoting the message you pointed out: > "You might lose cached and in-flight data of course, and userspace > applications may or may not handle the disappearance of their > underlying filesystem with grace and aplomb :)" > Perhaps you believe that allowing userland applications to lose data > is not risky. I strongly disagree. An userland application will be noticed by kernel and it may retransfer data. And i don't see here any problems. In FreeBSD case you will have a panic and crash. Also after panic you may lost a lot of data. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 15:22:43 2008 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 C42AA16A50C for ; Sun, 17 Feb 2008 15:22:43 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id B724A13C455 for ; Sun, 17 Feb 2008 15:22:43 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id A44E51CC05B; Sun, 17 Feb 2008 07:22:43 -0800 (PST) Date: Sun, 17 Feb 2008 07:22:43 -0800 From: Jeremy Chadwick To: "Carlos A. M. dos Santos" Message-ID: <20080217152243.GA51742@eos.sc1.parodius.com> References: <20080216210736.GA17517@eos.sc1.parodius.com> <20080217061905.GA35005@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: ATA -- erratic behaviour when removing disk 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, 17 Feb 2008 15:22:43 -0000 On Sun, Feb 17, 2008 at 11:03:31AM -0300, Carlos A. M. dos Santos wrote: > On Feb 17, 2008 3:19 AM, Jeremy Chadwick wrote: > > On Sat, Feb 16, 2008 at 09:08:38PM -0200, Carlos A. M. dos Santos wrote: > > > On Feb 16, 2008 7:07 PM, Jeremy Chadwick wrote: > > > > Is anyone aware of the situation where FreeBSD behaves erratically when > > > > a disk is physically removed without "atacontrol detach ataX" being run > > > > prior to removal (at least on RELENG_7)? > > > > > > Yes, I have seen this since 4.5, IIRC. > > > > Wonderful. > > > > > > Also FWIW: I also tested all this for comparison on Ubuntu Linux earlier > > > > this morning. I was able to yank the disk in the middle of an I/O > > > > operation, resulting in an immediate I/O error from dd. I took no > > > > precautions prior to yanking the disk. Upon reinsertion, the system > > > > found the disk and I could continue I/O operations on it as if it had > > > > never been removed. Only reason I'm pointing this out is that it > > > > confirms the issue isn't hardware or with vendor implementation, but > > > > rather specific to the OS. > > > > > > Congratulations to the Linux folks. Or not, since this looks like a > > > very risky behavior. Who warrants you that the *same* disk was plugged > > > back? Blindly continuing to write could easily corrupt the contents of > > > the second drive. > > > > I'm not sure I understand. There were no filesystems on the drive, and > > nothing mounted prior to removal: just like what I did with FreeBSD. > > The procedure: > > > > * Boot Ubuntu CD, get a shell > > * dd if=/dev/sdb of=/dev/null bs=8k > > * In the middle of I/O, yank the disk > > * dd exits with "I/O error" > > * System continued to be responsive; no ATA subsystem oddities > > * Reinserted disk; kernel saw the disk without any issue > > * dd if=/dev/sdb of=/dev/null bs=8k > > * I/O still operating as before; no system "oddities" > > I'm still not convinced that this is a valid use case. The fact of the matter is this: If while running FreeBSD, a disk (with no mounted filesystems) is lost or removed WITHOUT using "atacontrol detach" first, the entire ATA subsystem goes into a state of confusion, and remains broken until a reboot. Even a full reinit of the ATA channel does not solve the problem. If while running FreeBSD, someone uses "atacontrol detach channel" to disconnect an ATA channel (and thus the disk) PRIOR to the disk being lost or the disk being removed, FreeBSD behaves properly. Upon re- insertion of the disk, and "atacontrol attach", the disk is found on the controller. The reason I performed the same test on Linux is because I wanted to rule out "hardware issues" or "vendor implementation issues". By using another operating system, I've managed to confirm that there is indeed a bug within the ATA subsystem on FreeBSD. > > If you'd like, I can try inserting a completely different disk (both in > > size and vendor), but I really don't think anything odd will happen. If > > there were filesystems mounted or other whatnots, yes, I could see how > > there might be concern. [...] > > This is exctly what I was talking about when I said "risky". But this is a moot point anyways, because FreeBSD kernel panics when any storage medium is removed while a filesystem is still mounted. It doesn't matter if it's ATA, SCSI, USB umass, firewire, whatever. It panics. This is apparently by design, and thus I can't argue against it. But at least when there's a panic, the risk is significantly lower, since the system is dead in the water from that point on. > > [...] I can try that as well if you're interested. I > > am a bit curious to see what Linux does if I pull a disk that has > > mounted filesystems which are being accessed at the time. > > Yes, do it please. I must admit [precious brat mode on] that I'm very > curious about what would happen. :-) You got it: * Netbooted Ubuntu Server, spawned a shell * fdisk /dev/sda * Created a primary partition, all cylinders, type 0x83 (Linux) ~ # mke2fs /dev/sda1 {snip lots of output} ~ # mount /dev/sda1 /mnt ~ # dd if=/dev/urandom of=/mnt/testfile bs=8M count=1 1+0 records in 1+0 records out ~ # ls -l /mnt/testfile -rw-r--r-- 1 root root 8388608 Feb 17 15:09 /mnt/testfile ~ # md5sum /mnt/testfile 9745a2c5455d23be8bae300b7323ed49 /mnt/testfile ~ # while cp -f /mnt/testfile /mnt/testfile.copy; do sleep 0; done * Yanked disk cp: Write Error: Input/output error ~ # ls -l /mnt/testfile* ls: /mnt/testfile: Input/output error ls: /mnt/testfile.copy: Input/output error ~ # df -k Filesystem 1k-blocks Used Available Use% Mounted on tmpfs 1037424 40 1037384 0% /dev tmpfs 1037424 40 1037384 0% /.dev /dev/sda1 192292124 69004 182455200 0% /mnt ~ # dmesg {see output below my signature; just trying to keep this part clear} * Reattached disk; disk is now /dev/sdc, which apparently can happen based on what I've read about libata {see output below my signature} ~ # mkdir /mnt2 ~ # mount /dev/sdc1 /mnt2 [ 691.740671] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended ~ # df -k Filesystem 1k-blocks Used Available Use% Mounted on tmpfs 1037424 40 1037384 0% /dev tmpfs 1037424 40 1037384 0% /.dev /dev/sda1 192292124 69004 182455200 0% /mnt /dev/sdc1 192292124 69204 182455000 0% /mnt2 ~ # cd /mnt2 /mnt2 # ls -l drwx------ 2 root root 16384 Feb 17 15:08 lost+found -rw-r--r-- 1 root root 8388608 Feb 17 15:09 testfile -rw-r--r-- 1 root root 6324224 Feb 17 15:12 testfile.copy * Then I decided to poke at /mnt a bit to see what would happen... ~ # ls -l /mnt ls: /mnt/lost+found: Input/output error ls: /mnt/testfile: Input/output error ls: /mnt/testfile.copy: Input/output error ~ # umount /mnt ~ # df -k Filesystem 1k-blocks Used Available Use% Mounted on tmpfs 1037424 40 1037384 0% /dev tmpfs 1037424 40 1037384 0% /.dev /dev/sdc1 192292124 69204 182455000 0% /mnt2 I don't see anything wrong with the above scenario. Yes, testfile.copy is smaller than the original, but that's expected -- cp exited with an I/O error, which is good, because that's what I'd expect to happen under such circumstances. If it blindly kept working, that WOULD be bad. Anything else you want me to try? I seem pretty satisfied with the reliability of this, which is why I would like to see said issue in FreeBSD addressed. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | [ 465.905156] ata3: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0x2 frozen [ 465.905160] ata3: (irq_stat 0x00400000, PHY RDY changed) [ 468.115595] ata3: soft resetting port [ 468.115602] ata3: SATA link down (SStatus 11 SControl 300) [ 468.115609] ata3: failed to recover some devices, retrying in 5 secs [ 473.117426] ata3: hard resetting port [ 473.841112] ata3: SATA link down (SStatus 0 SControl 300) [ 473.841119] ata3.00: limiting speed to UDMA/133:PIO3 [ 473.841122] ata3: failed to recover some devices, retrying in 5 secs [ 478.842942] ata3: hard resetting port [ 479.566632] ata3: SATA link down (SStatus 0 SControl 300) [ 479.566637] ata3.00: disabled [ 479.566642] sd 2:0:0:0: rejecting I/O to offline device [ 479.566646] sd 2:0:0:0: rejecting I/O to offline device [ 479.566652] Buffer I/O error on device sda1, logical block 0 [ 479.566655] lost page write due to I/O error on sda1 [ 479.566660] Buffer I/O error on device sda1, logical block 1 [ 479.566663] lost page write due to I/O error on sda1 [ 479.566751] sd 2:0:0:0: rejecting I/O to offline device [ 479.566753] Buffer I/O error on device sda1, logical block 1025 [ 479.566755] lost page write due to I/O error on sda1 [ 479.566757] sd 2:0:0:0: rejecting I/O to offline device [ 479.566759] Buffer I/O error on device sda1, logical block 1027 [ 479.566761] lost page write due to I/O error on sda1 [ 479.566764] sd 2:0:0:0: rejecting I/O to offline device [ 479.566772] sd 2:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK [ 479.566776] end_request: I/O error, dev sda, sector 65695 [ 479.566778] Buffer I/O error on device sda1, logical block 8204 [ 479.566780] lost page write due to I/O error on sda1 [ 479.567404] sd 2:0:0:0: rejecting I/O to offline device [ 479.574627] sd 2:0:0:0: rejecting I/O to offline device [ 479.574630] Buffer I/O error on device sda1, logical block 0 [ 479.574631] lost page write due to I/O error on sda1 [ 479.574749] EXT2-fs error (device sda1): read_block_bitmap: Cannot read block bitmap - block_group = 0, block_bitmap = 1025 [ 479.574814] sd 2:0:0:0: rejecting I/O to offline device [ 479.574889] sd 2:0:0:0: rejecting I/O to offline device [ 479.574892] Buffer I/O error on device sda1, logical block 0 [ 479.574894] lost page write due to I/O error on sda1 [ 479.575009] EXT2-fs error (device sda1): read_block_bitmap: Cannot read block bitmap - block_group = 0, block_bitmap = 1025 [ 480.070416] ata3: EH complete [ 480.070420] ata3.00: detaching (SCSI 2:0:0:0) [ 480.070560] Buffer I/O error on device sda1, logical block 0 [ 480.070562] lost page write due to I/O error on sda1 [ 480.070564] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=13, block=1027 [ 480.070590] Buffer I/O error on device sda1, logical block 1 [ 480.070592] lost page write due to I/O error on sda1 [ 480.070595] Buffer I/O error on device sda1, logical block 1025 [ 480.070597] lost page write due to I/O error on sda1 [ 480.072352] sd 2:0:0:0: [sda] Synchronizing SCSI cache [ 480.072757] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK [ 480.072761] sd 2:0:0:0: [sda] Stopping disk [ 480.072867] sd 2:0:0:0: [sda] START_STOP FAILED [ 480.072869] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK [ 507.467114] scsi 2:0:0:0: rejecting I/O to dead device [ 507.474543] scsi 2:0:0:0: rejecting I/O to dead device [ 507.474546] printk: 2 messages suppressed. [ 507.474549] Buffer I/O error on device sda1, logical block 0 [ 507.474599] lost page write due to I/O error on sda1 [ 507.474603] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=12, block=1027 [ 507.474683] scsi 2:0:0:0: rejecting I/O to dead device [ 507.474713] scsi 2:0:0:0: rejecting I/O to dead device [ 507.474715] Buffer I/O error on device sda1, logical block 0 [ 507.474716] lost page write due to I/O error on sda1 [ 507.474718] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=13, block=1027 [ 538.888948] scsi 2:0:0:0: rejecting I/O to dead device [ 538.888981] scsi 2:0:0:0: rejecting I/O to dead device [ 538.888984] Buffer I/O error on device sda1, logical block 0 [ 538.888986] lost page write due to I/O error on sda1 [ 538.888988] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=2, block=1027 After reattach: [ 583.767068] ata3: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0x2 frozen [ 583.767071] ata3: (irq_stat 0x00000040, connection status changed) [ 584.481189] ata3: soft resetting port [ 589.690932] ata3: port is slow to respond, please be patient (Status 0x80) [ 592.937529] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 592.941346] ata3.00: ATA-6: WDC WD2000JD-00HBB0, 08.02D08, max UDMA/133 [ 592.941349] ata3.00: 390721968 sectors, multi 0: LBA48 [ 592.946372] ata3.00: configured for UDMA/133 [ 592.946375] ata3: EH complete [ 592.946511] scsi 2:0:0:0: Direct-Access ATA WDC WD2000JD-00H 08.0 PQ: 0 ANSI: 5 [ 592.946616] sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB) [ 592.946673] sd 2:0:0:0: [sdc] Write Protect is off [ 592.946676] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 592.946769] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 592.946851] sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB) [ 592.946906] sd 2:0:0:0: [sdc] Write Protect is off [ 592.946908] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 592.947001] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 592.947005] sdc: sdc1 [ 592.950021] sd 2:0:0:0: [sdc] Attached SCSI disk [ 592.950047] sd 2:0:0:0: Attached scsi generic sg1 type 0 After umount /mnt (which was already dead): [ 837.935980] scsi 2:0:0:0: rejecting I/O to dead device [ 837.943410] scsi 2:0:0:0: rejecting I/O to dead device [ 837.943413] Buffer I/O error on device sda1, logical block 0 [ 837.943452] lost page write due to I/O error on sda1 [ 837.943456] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=11, block=1027 [ 842.438081] scsi 2:0:0:0: rejecting I/O to dead device [ 842.445461] scsi 2:0:0:0: rejecting I/O to dead device [ 842.445464] Buffer I/O error on device sda1, logical block 0 [ 842.445466] lost page write due to I/O error on sda1 [ 842.445588] EXT2-fs error (device sda1): ext2_get_inode: unable to read inode block - inode=2, block=1027 [ 842.445675] scsi 2:0:0:0: rejecting I/O to dead device [ 842.445678] Buffer I/O error on device sda1, logical block 0 [ 842.445680] lost page write due to I/O error on sda1 From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 16:02:51 2008 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 2EB0A16A419 for ; Sun, 17 Feb 2008 16:02:51 +0000 (UTC) (envelope-from me@che78-3-82-246-30-233.fbx.proxad.net) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by mx1.freebsd.org (Postfix) with ESMTP id EBEDC13C461 for ; Sun, 17 Feb 2008 16:02:50 +0000 (UTC) (envelope-from me@che78-3-82-246-30-233.fbx.proxad.net) Received: from smtp8-g19.free.fr (localhost [127.0.0.1]) by smtp8-g19.free.fr (Postfix) with ESMTP id 05A6717F543 for ; Sun, 17 Feb 2008 17:02:49 +0100 (CET) Received: from che78-3-82-246-30-233.fbx.proxad.net (che78-3-82-246-30-233.fbx.proxad.net [82.246.30.233]) by smtp8-g19.free.fr (Postfix) with ESMTP id D8D5117F50B for ; Sun, 17 Feb 2008 17:02:48 +0100 (CET) Received: by che78-3-82-246-30-233.fbx.proxad.net (Postfix, from userid 1001) id 65A4A45260; Sun, 17 Feb 2008 17:02:42 +0100 (CET) Date: Sun, 17 Feb 2008 17:02:42 +0100 From: Harald Weis To: freebsd-stable@freebsd.org Message-ID: <20080217160242.GA2841@pollux> Mail-Followup-To: freebsd-stable@freebsd.org References: <20080207124403.GA2792@pollux> <20080210181332.A23724@eskimo.com> <20080211093702.GA2367@pollux> <20080211122913.A9514@eskimo.com> <20080215124413.GB2938@pollux> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080215124413.GB2938@pollux> User-Agent: Mutt/1.4.2.3i Subject: Re: X.org: Fatal server error [Solved] 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, 17 Feb 2008 16:02:51 -0000 On Fri, Feb 15, 2008 at 01:44:13PM +0100, Harald Weis wrote: > Fatal server error: > could not open default font 'fixed' I've learned two lessons. 1. As a constant user of portupgrade since ages, this time, before and after the xorg-upgrade procedure, I have carelessly omitted the `-R' option. No wonder that required packages were missing. 2. The `pkg_info -L' check does not certify that the file is actually in its place: between two checks I have removed all the empty fontfiles in misc/, thereby getting rid again of fonts.alias as well :-( and forgot about it. Now I know that the server is indeed looking first for the `fixed' line in fonts.alias. If he does not find it, he complains no matter how many fixed fonts are stored in misc/. The fact that misc/ and three other directories in that machine were only populated with a large number of empty fontfiles remains weird though. Thanks again for every reply, on-list and off-list. HW -- FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:56:09 UTC 2007 From owner-freebsd-stable@FreeBSD.ORG Sun Feb 17 20:56:51 2008 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 C48B816A417; Sun, 17 Feb 2008 20:56:51 +0000 (UTC) (envelope-from mcc@fid4.com) Received: from mail102.csoft.net (mail102.csoft.net [205.205.219.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9704C13C455; Sun, 17 Feb 2008 20:56:51 +0000 (UTC) (envelope-from mcc@fid4.com) Received: from [172.16.6.246] (c-24-61-74-156.hsd1.ma.comcast.net [24.61.74.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail102.csoft.net (Postfix) with ESMTP id 3F6FE1D117; Sun, 17 Feb 2008 15:39:45 -0500 (EST) Message-ID: <47B89BE7.9020809@fid4.com> Date: Sun, 17 Feb 2008 15:41:11 -0500 From: "Michael C. Cambria" User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Nathan Lay References: <47B73F59.1030409@comcast.net> In-Reply-To: <47B73F59.1030409@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable Subject: Re: ath and cardbus 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, 17 Feb 2008 20:56:51 -0000 Nathan Lay wrote: [deleted] > Anyone else experience this strange behavior? It is of note, that if > the card is plugged in before booting, it is properly detected and > attached during boot. It is only when plugging it into a running > FreeBSD 7.0 system for the first time that it behaves this way. I can't even get this far. My Atheros AR5212 (Netgate WPN511) isn't even detected by FreeBSD 7 (csup as of this a.m. - 17 Feb 2008). In my case, I am using a PCI to Cardbus adapter. Details posted on mobile@ Which card are you using? MikeC From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 04:36:46 2008 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 6C8BB16A421; Mon, 18 Feb 2008 04:36:46 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by mx1.freebsd.org (Postfix) with ESMTP id 3367613C468; Mon, 18 Feb 2008 04:36:46 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from [10.0.0.100] (c-66-41-19-246.hsd1.mn.comcast.net [66.41.19.246]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JQxY10LmJ-0007KF; Sun, 17 Feb 2008 23:24:13 -0500 Message-ID: <47B90868.7000900@electron-tube.net> Date: Sun, 17 Feb 2008 22:24:08 -0600 From: Jim Bryant User-Agent: Thunderbird 1.5 (X11/20061230) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18m4aZlpkrjVLAus8S+nj9gMeQSg5ef1kVfeL5 kBvaXrPkqcAljL7hUedzmZ1BOHwODKY8ldhtqzyKn8pRB4DeKh 4bKiIPYGZxwcwiK7ZMCUAgx2hLv+EHY Cc: freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 04:36:46 -0000 One line summary: Too many files in a top-level UFS-2 filesystem directory will cause a panic on mount. Kern/Critical/High Priority/SW-Bug Which FreeBSD Release You Are Using: 6.3-STABLE Environment (output of "uname -a" on the problem machine): FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008 jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 Note: I just cvsupped earlier, and no changes have been put into cvsup that would fix this problem. Full Description: I was doing a reorganization of my filesystems, and since I do offline installs, I keep a local distfiles collection (or did until yesterday when this happened), and in the process, put all of the distfiles on their own filesystem to be mounted under /usr/ports/distfiles. All was fine until I rebooted. On rebooting, I got a page fault panic on mount of the new distfiles filesystem. i booted again, got it again, booted again this time into single-user, and did a fsck on the filesystem, and it only showed as being "dirty", but otherwise had no problems in the eyes of fsck. booted again, instant panic. i booted an older 6.2 CD and mounted the filesystem fine. i then put that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing everything into it, but on reboot it still paniced on mount. only a newfs was able to enable the filesystem to be mounted. today i did further research, thinking it had to do with the number of files in the top-level filesystem directory, and found that to be true. the short c program in the next section (how to repeat the problem) contains this. a second test shows that, after a newfs, if this done in any subdirectory of that filesystem, the panic is averted, and all is well. apparently this bug only effects top-level directories of a UFS2 filesystem. I have not attempted this to a non-UFS2 filesystem. IMHO, a security advisory should be released, since any user with write access to ANY top level directory of ANY mounted filesystem (most systems have /tmp as a world writable top level filesystem directory) can create a panic situation requiring a newfs of the said filesystem. A malicious user with root access can do this to /. Either way, on boot, or any attempt to mount said filesystem on a running system, will cause a panic, which of course will cause an unbootable system on reboot. How to repeat the problem: Compile and run the following as instructed: #include #include int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i); system((const char *)buf);} return(0);} /* pass a top-level mountpoint directory name of a mounted filesystem, with a trailing slash to the above as argv[1], and run. This will create 10,000 zero-length files in the specified directory. umount that filesystem. perform a shitload of sync's to make sure everything outstanding is flushed to disk on all filesystems. mount the target filesystem (preferably from a vty or serial console to catch the messages when it panics, which it will as soon as the mount is attempted). */ Fix to the problem if known: newfs(8) From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 04:58:47 2008 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 847FE16A419; Mon, 18 Feb 2008 04:58:47 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4D54213C447; Mon, 18 Feb 2008 04:58:47 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from [10.0.0.100] (c-66-41-19-246.hsd1.mn.comcast.net [66.41.19.246]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1JQy5R0Kry-0003kN; Sun, 17 Feb 2008 23:58:46 -0500 Message-ID: <47B91080.9010109@electron-tube.net> Date: Sun, 17 Feb 2008 22:58:40 -0600 From: Jim Bryant User-Agent: Thunderbird 1.5 (X11/20061230) MIME-Version: 1.0 To: Jim Bryant References: <47B90868.7000900@electron-tube.net> In-Reply-To: <47B90868.7000900@electron-tube.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+TSUngQSCLZj+rWqUub9RwbMJN1nqDMkMpISR 1WRDrxdOUfQ9zTCoTOTZMh1eiKT5A/hSaexTQe1EGjGhEOSK3r B28Pl8SI7AAWxjBu2uOxFvX6z4laLVr Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 04:58:47 -0000 FYI: The system assigned kern/120781 to this bug report. IMHO, a security advisory should be issued ASAP. Jim Bryant wrote: > One line summary: > Too many files in a top-level UFS-2 filesystem directory will cause > a panic on mount. > > Kern/Critical/High Priority/SW-Bug > > Which FreeBSD Release You Are Using: > 6.3-STABLE > > Environment (output of "uname -a" on the problem machine): > FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb > 10 21:13:39 CST 2008 > jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 > > Note: I just cvsupped earlier, and no changes have been put into > cvsup that would fix this problem. > > Full Description: > I was doing a reorganization of my filesystems, and since I do > offline installs, I keep a local distfiles collection (or did until > yesterday when this happened), and in the process, put all of the > distfiles on their own filesystem to be mounted under > /usr/ports/distfiles. > > All was fine until I rebooted. > > On rebooting, I got a page fault panic on mount of the new distfiles > filesystem. > > i booted again, got it again, booted again this time into single-user, > and did a fsck on the filesystem, and it only showed as being "dirty", > but otherwise had no problems in the eyes of fsck. booted again, > instant panic. > > i booted an older 6.2 CD and mounted the filesystem fine. i then put > that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing > everything into it, but on reboot it still paniced on mount. > > only a newfs was able to enable the filesystem to be mounted. > > today i did further research, thinking it had to do with the number of > files in the top-level filesystem directory, and found that to be > true. the short c program in the next section (how to repeat the > problem) contains this. > > a second test shows that, after a newfs, if this done in any > subdirectory of that filesystem, the panic is averted, and all is > well. apparently this bug only effects top-level directories of a > UFS2 filesystem. > > I have not attempted this to a non-UFS2 filesystem. > > IMHO, a security advisory should be released, since any user with > write access to ANY top level directory of ANY mounted filesystem > (most systems have /tmp as a world writable top level filesystem > directory) can create a panic situation requiring a newfs of the said > filesystem. A malicious user with root access can do this to /. > Either way, on boot, or any attempt to mount said filesystem on a > running system, will cause a panic, which of course will cause an > unbootable system on reboot. > > How to repeat the problem: > Compile and run the following as instructed: > > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, > 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", > argv[1], i); system((const char *)buf);} return(0);} > > /* pass a top-level mountpoint directory name of a mounted filesystem, > with a trailing slash to the above as argv[1], and run. > > This will create 10,000 zero-length files in the specified directory. > > umount that filesystem. > > perform a shitload of sync's to make sure everything outstanding is > flushed to disk on all filesystems. > > mount the target filesystem (preferably from a vty or serial console > to catch the messages when it panics, which it will as soon as the > mount is attempted). > */ > > Fix to the problem if known: > newfs(8) > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 04:58:52 2008 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 1D27516A4D4; Mon, 18 Feb 2008 04:58:52 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 1AACC13C442; Mon, 18 Feb 2008 04:58:50 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id D958F1D0E7; Mon, 18 Feb 2008 06:38:51 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=6.0 tests=MR_NOT_ATTRIBUTED_IP, RATWR10_MESSID,RCVD_IN_SORBS autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 9DE601D093 for ; Mon, 18 Feb 2008 06:38:46 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 944255C137; Mon, 18 Feb 2008 04:37:23 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BC9216A509; Mon, 18 Feb 2008 04:37:21 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C8BB16A421; Mon, 18 Feb 2008 04:36:46 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by mx1.freebsd.org (Postfix) with ESMTP id 3367613C468; Mon, 18 Feb 2008 04:36:46 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from [10.0.0.100] (c-66-41-19-246.hsd1.mn.comcast.net [66.41.19.246]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JQxY10LmJ-0007KF; Sun, 17 Feb 2008 23:24:13 -0500 Message-ID: <47B90868.7000900@electron-tube.net> Date: Sun, 17 Feb 2008 22:24:08 -0600 From: Jim Bryant User-Agent: Thunderbird 1.5 (X11/20061230) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18m4aZlpkrjVLAus8S+nj9gMeQSg5ef1kVfeL5 kBvaXrPkqcAljL7hUedzmZ1BOHwODKY8ldhtqzyKn8pRB4DeKh 4bKiIPYGZxwcwiK7ZMCUAgx2hLv+EHY X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 04:58:52 -0000 One line summary: Too many files in a top-level UFS-2 filesystem directory will cause a panic on mount. Kern/Critical/High Priority/SW-Bug Which FreeBSD Release You Are Using: 6.3-STABLE Environment (output of "uname -a" on the problem machine): FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 21:13:39 CST 2008 jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 Note: I just cvsupped earlier, and no changes have been put into cvsup that would fix this problem. Full Description: I was doing a reorganization of my filesystems, and since I do offline installs, I keep a local distfiles collection (or did until yesterday when this happened), and in the process, put all of the distfiles on their own filesystem to be mounted under /usr/ports/distfiles. All was fine until I rebooted. On rebooting, I got a page fault panic on mount of the new distfiles filesystem. i booted again, got it again, booted again this time into single-user, and did a fsck on the filesystem, and it only showed as being "dirty", but otherwise had no problems in the eyes of fsck. booted again, instant panic. i booted an older 6.2 CD and mounted the filesystem fine. i then put that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing everything into it, but on reboot it still paniced on mount. only a newfs was able to enable the filesystem to be mounted. today i did further research, thinking it had to do with the number of files in the top-level filesystem directory, and found that to be true. the short c program in the next section (how to repeat the problem) contains this. a second test shows that, after a newfs, if this done in any subdirectory of that filesystem, the panic is averted, and all is well. apparently this bug only effects top-level directories of a UFS2 filesystem. I have not attempted this to a non-UFS2 filesystem. IMHO, a security advisory should be released, since any user with write access to ANY top level directory of ANY mounted filesystem (most systems have /tmp as a world writable top level filesystem directory) can create a panic situation requiring a newfs of the said filesystem. A malicious user with root access can do this to /. Either way, on boot, or any attempt to mount said filesystem on a running system, will cause a panic, which of course will cause an unbootable system on reboot. How to repeat the problem: Compile and run the following as instructed: #include #include int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i); system((const char *)buf);} return(0);} /* pass a top-level mountpoint directory name of a mounted filesystem, with a trailing slash to the above as argv[1], and run. This will create 10,000 zero-length files in the specified directory. umount that filesystem. perform a shitload of sync's to make sure everything outstanding is flushed to disk on all filesystems. mount the target filesystem (preferably from a vty or serial console to catch the messages when it panics, which it will as soon as the mount is attempted). */ Fix to the problem if known: newfs(8) _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 05:03:57 2008 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 8B78016A419; Mon, 18 Feb 2008 05:03:57 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 140FD13C442; Mon, 18 Feb 2008 05:03:57 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 3AE731D0A6; Mon, 18 Feb 2008 07:03:56 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: *** X-Spam-Status: No, score=3.2 required=6.0 tests=MR_NOT_ATTRIBUTED_IP, RATWR10_MESSID,RCVD_IN_SORBS autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 6C1A91D058 for ; Mon, 18 Feb 2008 07:03:51 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 51BF55D0E0; Mon, 18 Feb 2008 04:59:11 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 726E316A681; Mon, 18 Feb 2008 04:59:02 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 847FE16A419; Mon, 18 Feb 2008 04:58:47 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from mout.perfora.net (mout.perfora.net [74.208.4.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4D54213C447; Mon, 18 Feb 2008 04:58:47 +0000 (UTC) (envelope-from freebsd@electron-tube.net) Received: from [10.0.0.100] (c-66-41-19-246.hsd1.mn.comcast.net [66.41.19.246]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1JQy5R0Kry-0003kN; Sun, 17 Feb 2008 23:58:46 -0500 Message-ID: <47B91080.9010109@electron-tube.net> Date: Sun, 17 Feb 2008 22:58:40 -0600 From: Jim Bryant User-Agent: Thunderbird 1.5 (X11/20061230) MIME-Version: 1.0 To: Jim Bryant References: <47B90868.7000900@electron-tube.net> In-Reply-To: <47B90868.7000900@electron-tube.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+TSUngQSCLZj+rWqUub9RwbMJN1nqDMkMpISR 1WRDrxdOUfQ9zTCoTOTZMh1eiKT5A/hSaexTQe1EGjGhEOSK3r B28Pl8SI7AAWxjBu2uOxFvX6z4laLVr X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 05:03:57 -0000 FYI: The system assigned kern/120781 to this bug report. IMHO, a security advisory should be issued ASAP. Jim Bryant wrote: > One line summary: > Too many files in a top-level UFS-2 filesystem directory will cause > a panic on mount. > > Kern/Critical/High Priority/SW-Bug > > Which FreeBSD Release You Are Using: > 6.3-STABLE > > Environment (output of "uname -a" on the problem machine): > FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb > 10 21:13:39 CST 2008 > jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 > > Note: I just cvsupped earlier, and no changes have been put into > cvsup that would fix this problem. > > Full Description: > I was doing a reorganization of my filesystems, and since I do > offline installs, I keep a local distfiles collection (or did until > yesterday when this happened), and in the process, put all of the > distfiles on their own filesystem to be mounted under > /usr/ports/distfiles. > > All was fine until I rebooted. > > On rebooting, I got a page fault panic on mount of the new distfiles > filesystem. > > i booted again, got it again, booted again this time into single-user, > and did a fsck on the filesystem, and it only showed as being "dirty", > but otherwise had no problems in the eyes of fsck. booted again, > instant panic. > > i booted an older 6.2 CD and mounted the filesystem fine. i then put > that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing > everything into it, but on reboot it still paniced on mount. > > only a newfs was able to enable the filesystem to be mounted. > > today i did further research, thinking it had to do with the number of > files in the top-level filesystem directory, and found that to be > true. the short c program in the next section (how to repeat the > problem) contains this. > > a second test shows that, after a newfs, if this done in any > subdirectory of that filesystem, the panic is averted, and all is > well. apparently this bug only effects top-level directories of a > UFS2 filesystem. > > I have not attempted this to a non-UFS2 filesystem. > > IMHO, a security advisory should be released, since any user with > write access to ANY top level directory of ANY mounted filesystem > (most systems have /tmp as a world writable top level filesystem > directory) can create a panic situation requiring a newfs of the said > filesystem. A malicious user with root access can do this to /. > Either way, on boot, or any attempt to mount said filesystem on a > running system, will cause a panic, which of course will cause an > unbootable system on reboot. > > How to repeat the problem: > Compile and run the following as instructed: > > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, > 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", > argv[1], i); system((const char *)buf);} return(0);} > > /* pass a top-level mountpoint directory name of a mounted filesystem, > with a trailing slash to the above as argv[1], and run. > > This will create 10,000 zero-length files in the specified directory. > > umount that filesystem. > > perform a shitload of sync's to make sure everything outstanding is > flushed to disk on all filesystems. > > mount the target filesystem (preferably from a vty or serial console > to catch the messages when it panics, which it will as soon as the > mount is attempted). > */ > > Fix to the problem if known: > newfs(8) > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" > _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 05:55:42 2008 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 E70F416A418 for ; Mon, 18 Feb 2008 05:55:42 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.87.78.132]) by mx1.freebsd.org (Postfix) with ESMTP id CEFFF13C45D for ; Mon, 18 Feb 2008 05:55:42 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id DBF868FD79; Sun, 17 Feb 2008 22:28:55 -0700 (MST) Date: Sun, 17 Feb 2008 22:28:55 -0700 From: Brad Davis To: freebsd-hackers@FreeBSD.org Message-ID: <20080218052855.GE49382@valentine.liquidneon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: FreeBSD Status Reports for the Fourth Quarter of 2007 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, 18 Feb 2008 05:55:43 -0000 Hi Everyone, The FreeBSD Status Reports for the Fourth Quarter of 2007 are now available at: http://www.freebsd.org/news/status/report-2007-10-2007-12.html Regards, Brad Davis From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 07:36:09 2008 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 0C61516A41A for ; Mon, 18 Feb 2008 07:36:09 +0000 (UTC) (envelope-from parv@pair.com) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id BD43B13C458 for ; Mon, 18 Feb 2008 07:36:08 +0000 (UTC) (envelope-from parv@pair.com) Received: from localhost.hawaii.res.rr.com ([66.91.120.58]) by hrndva-omta06.mail.rr.com with ESMTP id <20080218073607.PKCZ1990.hrndva-omta06.mail.rr.com@localhost.hawaii.res.rr.com> for ; Mon, 18 Feb 2008 07:36:07 +0000 Received: from holstein.holy.cow (localhost [127.0.0.1]) by localhost.hawaii.res.rr.com (Postfix) with ESMTP id AF47432C6 for ; Sun, 17 Feb 2008 21:37:51 -1000 (HST) Received: (from parv@localhost) by holstein.holy.cow (8.13.8/8.13.8/Submit) id m1I7boXq004624 for freebsd-stable@freebsd.org; Sun, 17 Feb 2008 21:37:50 -1000 (HST) (envelope-from parv@pair.com) X-Authentication-Warning: holstein.holy.cow: parv set sender to parv@pair.com using -f Date: Sun, 17 Feb 2008 21:37:50 -1000 From: Parv To: freebsd-stable@freebsd.org Message-ID: <20080218073750.GA1639@holstein.holy.cow> Mail-Followup-To: freebsd-stable@freebsd.org References: <20080207124403.GA2792@pollux> <20080210181332.A23724@eskimo.com> <20080211093702.GA2367@pollux> <20080211122913.A9514@eskimo.com> <20080215124413.GB2938@pollux> <20080217160242.GA2841@pollux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080217160242.GA2841@pollux> Subject: Re: X.org: Fatal server error [Solved] 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, 18 Feb 2008 07:36:09 -0000 in message <20080217160242.GA2841@pollux>, wrote Harald Weis thusly... > > 2. The `pkg_info -L' check does not certify that the file is > actually in its place To actually verify the existence of the files, stat(2) them somehow (will work at least in bourne like shells) ... pkg_info -L \ | awk '!/^(Info|Files:|$)/ { print $0 }' \ | xargs ls -l >/dev/null ... above will only show the error messages for missing files of a port|package. - Parv -- From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 10:06:33 2008 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 462D216A46B for ; Mon, 18 Feb 2008 10:06:33 +0000 (UTC) (envelope-from huub@wirelessleiden.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.freebsd.org (Postfix) with ESMTP id D403813C457 for ; Mon, 18 Feb 2008 10:06:32 +0000 (UTC) (envelope-from huub@wirelessleiden.nl) Received: from [192.168.1.197] (a213-84-65-193.adsl.xs4all.nl [213.84.65.193]) by smtp-vbr12.xs4all.nl (8.13.8/8.13.8) with ESMTP id m1I9sZhS001910 for ; Mon, 18 Feb 2008 10:54:45 +0100 (CET) (envelope-from huub@wirelessleiden.nl) From: huub To: freebsd-stable@freebsd.org Content-Type: text/plain Date: Mon, 18 Feb 2008 10:54:34 +0100 Message-Id: <1203328474.3957.23.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2-2.1mdv2007.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: interrupt storms with AR5414 on 6.3 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: Mon, 18 Feb 2008 10:06:33 -0000 I have a problem running the Atheros AR5414 wireless mini-pci-card (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a Soekris 4521. I get lots of messages: "interrupt storm detected on "irq10:"; throttling interrupt source" and "ath0: device timeout" And after sometime the interface stops functioning. Anybody any suggestion? Thanks, Huub Information on system follows: # dmesg: .... ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ..... ath0: mem 0xa0000000-0xa000ffff irq 10 at device 16.0 on pci0 ath0: Ethernet address: 00:80:48:54:c0:92 ath0: mac 10.5 phy 6.1 radio 6.3 # ifconfig ath0: flags=8843 mtu 1500 inet6 fe80::280:48ff:fe54:c092%ath0 prefixlen 64 scopeid 0x1 inet 172.16.0.214 netmask 0xfffffffc broadcast 172.16.0.215 ether 00:80:48:54:c0:92 media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) status: associated ssid ap-omni.renv0.wleiden.net channel 1 bssid 00:02:6f:06:d6:14 authmode OPEN privacy OFF txpowmax 46 protmode CTS bintval 100 # wicontrol -i ath0 NIC serial number: [ ] Station name: [ CNodeHuub.wLeiden.NET ] SSID for IBSS creation: [ ap-omni.renv0.wleiden.net ] Current netname (SSID): [ ap-omni.renv0.wleiden.net ] Desired netname (SSID): [ ap-omni.renv0.wleiden.net ] Current BSSID: [ 00:02:6f:06:d6:14 ] Channel list: [ ffe 0 1110 1111 1 0 0 0 0 2220 22 ] IBSS channel: [ 1 ] Current channel: [ 1 ] Comms quality/signal/noise: [ 0 24 0 ] Promiscuous mode: [ Off ] Intersil-Prism2 based card: [ 1 ] Port type (1=BSS, 3=ad-hoc): [ 1 ] MAC address: [ 00:80:48:54:c0:92 ] TX rate (selection): [ 0 ] TX rate (actual speed): [ 2 ] RTS/CTS handshake threshold: [ 2346 ] Create IBSS: [ Off ] Access point density: [ 1 ] Power Mgmt (1=on, 0=off): [ 0 ] Max sleep time: [ 100 ] WEP encryption: [ Off ] TX encryption key: [ 0 ] Encryption keys: [ ][ ][ ][ ] From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 10:28:42 2008 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BDBE16A421 for ; Mon, 18 Feb 2008 10:28:42 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.freebsd.org (Postfix) with ESMTP id 58AB513C46A for ; Mon, 18 Feb 2008 10:28:42 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from dhcp250-210.yandex.ru ([87.250.250.210]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1JR318-000ECs-NT; Mon, 18 Feb 2008 13:14:34 +0300 Message-ID: <47B95990.8070808@FreeBSD.org> Date: Mon, 18 Feb 2008 13:10:24 +0300 From: Sergey Matveychuk User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Yoshihiro Ota References: <36e46ac80802171226p6a18997ao21e03b626425695e@mail.gmail.com> <47B8A3B2.8090202@infracaninophile.co.uk> <1203283417.6223.3.camel@pclmills> <20080217212857.c4df5d25.ota@j.email.ne.jp> In-Reply-To: <20080217212857.c4df5d25.ota@j.email.ne.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Atanas Gendov , stable@FreeBSD.org, oscartheduck@gmail.com Subject: ldconfig -R issue (Was: Problems with icu - 3.8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 10:28:42 -0000 +stable@ Yoshihiro Ota wrote: > Why are so many people are bitten by this? Is that the jobs of port-upgrading > tool to safe copy these libraries to compat so that all programs using > the old libraries works? Portupgrade preserves the libraries in /usr/local/lib/compat/pkg: % ls /usr/local/lib/compat/pkg/ libicudata.so.36.0 libicule.so.36.0 libicuuc.so.36.0 libicui18n.so.36.0 libiculx.so.36.0 libicuio.so.36.0 libicutu.so.36.0 ldconfig knows about the directory: % ldconfig -r | head -2 /var/run/ld-elf.so.hints: search directories: /lib:/usr/lib:/usr/lib/compat:/usr/X11R6/lib:/usr/local/lib:/usr/local/lib/mysql:/usr/local/lib/compat/pkg But ldconfig -R don't rescan them: % ldconfig -R % ldconfig -r | grep libicudata 231:-licudata.38 => /usr/X11R6/lib/libicudata.so.38 386:-licudata.38 => /usr/local/lib/libicudata.so.38 Could anybody investigate it? I have no time now. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:24:36 2008 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 B8D2816A46C; Mon, 18 Feb 2008 13:24:36 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 2EC9A13C4E5; Mon, 18 Feb 2008 13:24:35 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 5DE1E1D13D; Mon, 18 Feb 2008 15:24:34 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id BFBBF1CFDA for ; Mon, 18 Feb 2008 15:24:29 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 7003D1C25A; Mon, 18 Feb 2008 13:23:17 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 17F1816A52C; Mon, 18 Feb 2008 13:23:15 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B30616A46C; Mon, 18 Feb 2008 13:23:07 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 21B0E13C4D1; Mon, 18 Feb 2008 13:23:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 5BF4F2083; Mon, 18 Feb 2008 14:23:00 +0100 (CET) Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 46FD9207F; Mon, 18 Feb 2008 14:23:00 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 2A84F8449D; Mon, 18 Feb 2008 14:23:00 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jim Bryant References: <47B90868.7000900@electron-tube.net> Date: Mon, 18 Feb 2008 14:23:00 +0100 In-Reply-To: <47B90868.7000900@electron-tube.net> (Jim Bryant's message of "Sun\, 17 Feb 2008 22\:24\:08 -0600") Message-ID: <86odae5rgr.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 13:24:36 -0000 Jim Bryant writes: > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024)= ; for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i)= ; system((const char *)buf);} return(0);} Subject should be "how to take down a system [...] with three lines of badly written C, provided you have root privileges already and are too lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which would accomplish the job much faster. Purely in the interest of showing off, here is my version. It is 81 bytes shorter than yours, it is valid C99 with POSIX extensions (yours is not), and it produces 11,450 files in about 0.2% of the time yours takes to produce 10,000. #include #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; #define a(i) b(i,v##i) int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:39:03 2008 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 D459816A420; Mon, 18 Feb 2008 13:39:03 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 9421313C4D3; Mon, 18 Feb 2008 13:39:03 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 5BF4F2083; Mon, 18 Feb 2008 14:23:00 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 46FD9207F; Mon, 18 Feb 2008 14:23:00 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 2A84F8449D; Mon, 18 Feb 2008 14:23:00 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jim Bryant References: <47B90868.7000900@electron-tube.net> Date: Mon, 18 Feb 2008 14:23:00 +0100 In-Reply-To: <47B90868.7000900@electron-tube.net> (Jim Bryant's message of "Sun\, 17 Feb 2008 22\:24\:08 -0600") Message-ID: <86odae5rgr.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 13:39:03 -0000 Jim Bryant writes: > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024)= ; for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i)= ; system((const char *)buf);} return(0);} Subject should be "how to take down a system [...] with three lines of badly written C, provided you have root privileges already and are too lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which would accomplish the job much faster. Purely in the interest of showing off, here is my version. It is 81 bytes shorter than yours, it is valid C99 with POSIX extensions (yours is not), and it produces 11,450 files in about 0.2% of the time yours takes to produce 10,000. #include #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; #define a(i) b(i,v##i) int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:40:55 2008 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 112B916A46D for ; Mon, 18 Feb 2008 13:40:55 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.244]) by mx1.freebsd.org (Postfix) with ESMTP id C215113C4E9 for ; Mon, 18 Feb 2008 13:40:49 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by ag-out-0708.google.com with SMTP id 5so2473871agb.7 for ; Mon, 18 Feb 2008 05:40:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vq0l9z0xMsw4JpD6hWHmXb0iheAhmfajBGVA7nobMCk=; b=lgoHdV8xuG3Pk6wCyUOgAl7p80M3ORTq0MVs5nh9eJA3Naq8xE8P97UYQ5I52EwhcDykO5Q27gxOOE9A7Uhvfs+XrE1qK1UDs2c/8iWVkXpLvT20pp+fJHZEdZN618DSKUBOg4idF6fx32Zhtg9cG1TxIStgteykuruxSNCU/xc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kFxUD/W+qYjD81YNTsovhIihqaMZv14XDq+2mbEOhXyGfNOZBQ9LZb7NaUMYeJvbcI40zqqqK/MhQWnVj2FAiGs6jeEzI7MtSA0jLmTp682GLnnMlJ00rx6ql9r8e24FAqlcpnkDmp3JNZ4TMZ8QrWakjDVEm1t19eu9JARwe7I= Received: by 10.142.216.9 with SMTP id o9mr4282453wfg.173.1203341221352; Mon, 18 Feb 2008 05:27:01 -0800 (PST) Received: by 10.142.87.9 with HTTP; Mon, 18 Feb 2008 05:27:01 -0800 (PST) Message-ID: Date: Mon, 18 Feb 2008 13:27:01 +0000 From: "Kurt Buff" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86odae5rgr.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 13:40:55 -0000 Patient: Doctor, it hurts when I do this! Doctor: Don't do that... On Feb 18, 2008 1:23 PM, Dag-Erling Sm=F8rgrav wrote: > Jim Bryant writes: > > #include > > #include > > > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 102= 4); for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], = i); system((const char *)buf);} return(0);} > > Subject should be "how to take down a system [...] with three lines of > badly written C, provided you have root privileges already and are too > lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which would > accomplish the job much faster. > > Purely in the interest of showing off, here is my version. It is 81 > bytes shorter than yours, it is valid C99 with POSIX extensions (yours > is not), and it produces 11,450 files in about 0.2% of the time yours > takes to produce 10,000. > > #include > #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; > #define a(i) b(i,v##i) > int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.or= g" > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:42:46 2008 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 44DEA16A417; Mon, 18 Feb 2008 13:42:46 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id BE89313C4CE; Mon, 18 Feb 2008 13:42:45 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id C38341D0F3; Mon, 18 Feb 2008 15:42:43 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 251651D09E for ; Mon, 18 Feb 2008 15:42:39 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C8D4C5F4A0; Mon, 18 Feb 2008 13:41:13 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B4A2816A4EF; Mon, 18 Feb 2008 13:41:13 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9267016A418 for ; Mon, 18 Feb 2008 13:41:06 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.244]) by mx1.freebsd.org (Postfix) with ESMTP id 501F913C455 for ; Mon, 18 Feb 2008 13:41:06 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: by ag-out-0708.google.com with SMTP id 5so2473871agb.7 for ; Mon, 18 Feb 2008 05:41:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vq0l9z0xMsw4JpD6hWHmXb0iheAhmfajBGVA7nobMCk=; b=lgoHdV8xuG3Pk6wCyUOgAl7p80M3ORTq0MVs5nh9eJA3Naq8xE8P97UYQ5I52EwhcDykO5Q27gxOOE9A7Uhvfs+XrE1qK1UDs2c/8iWVkXpLvT20pp+fJHZEdZN618DSKUBOg4idF6fx32Zhtg9cG1TxIStgteykuruxSNCU/xc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kFxUD/W+qYjD81YNTsovhIihqaMZv14XDq+2mbEOhXyGfNOZBQ9LZb7NaUMYeJvbcI40zqqqK/MhQWnVj2FAiGs6jeEzI7MtSA0jLmTp682GLnnMlJ00rx6ql9r8e24FAqlcpnkDmp3JNZ4TMZ8QrWakjDVEm1t19eu9JARwe7I= Received: by 10.142.216.9 with SMTP id o9mr4282453wfg.173.1203341221352; Mon, 18 Feb 2008 05:27:01 -0800 (PST) Received: by 10.142.87.9 with HTTP; Mon, 18 Feb 2008 05:27:01 -0800 (PST) Message-ID: Date: Mon, 18 Feb 2008 13:27:01 +0000 From: "Kurt Buff" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86odae5rgr.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 13:42:46 -0000 Patient: Doctor, it hurts when I do this! Doctor: Don't do that... On Feb 18, 2008 1:23 PM, Dag-Erling Sm=F8rgrav wrote: > Jim Bryant writes: > > #include > > #include > > > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 102= 4); for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], = i); system((const char *)buf);} return(0);} > > Subject should be "how to take down a system [...] with three lines of > badly written C, provided you have root privileges already and are too > lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which would > accomplish the job much faster. > > Purely in the interest of showing off, here is my version. It is 81 > bytes shorter than yours, it is valid C99 with POSIX extensions (yours > is not), and it produces 11,450 files in about 0.2% of the time yours > takes to produce 10,000. > > #include > #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; > #define a(i) b(i,v##i) > int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.or= g" > _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:54:06 2008 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 E9ED916A418; Mon, 18 Feb 2008 13:54:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A49D413C45E; Mon, 18 Feb 2008 13:54:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 59B252090; Mon, 18 Feb 2008 14:53:59 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 438A52087; Mon, 18 Feb 2008 14:53:59 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 1A0068449D; Mon, 18 Feb 2008 14:53:59 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jim Bryant References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> Date: Mon, 18 Feb 2008 14:53:59 +0100 In-Reply-To: <86odae5rgr.fsf@ds4.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?= =?utf-8?Q?rav=22's?= message of "Mon\, 18 Feb 2008 14\:23\:00 +0100") Message-ID: <863arq5q14.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 13:54:07 -0000 Dag-Erling Sm=C3=B8rgrav writes: > Purely in the interest of showing off, here is my version. It is 81 > bytes shorter than yours, it is valid C99 with POSIX extensions (yours > is not), and it produces 11,450 files in about 0.2% of the time yours > takes to produce 10,000. > > #include > #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; > #define a(i) b(i,v##i) > int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} Two bugs: 1) I forgot to include the correct version of the code 2) the version I had created a few files with '/' in their names; this slightly nastier creates 10,648 files with only letters. #include #define b(i,v)for(int v=3D65;v<87;){i[f]=3Dv++; #define a(i)b(i,v##i) int main(void){char f[4]=3D{47};a(1)a(2)a(3)truncate(f,0);}}}} DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 13:54:49 2008 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 0DDC116A418; Mon, 18 Feb 2008 13:54:49 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 7991B13C46A; Mon, 18 Feb 2008 13:54:48 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 801CF1D170; Mon, 18 Feb 2008 15:54:46 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 685781D058 for ; Mon, 18 Feb 2008 15:54:41 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A6D4F5F38A; Mon, 18 Feb 2008 13:54:16 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 275C516A4E5; Mon, 18 Feb 2008 13:54:16 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9ED916A418; Mon, 18 Feb 2008 13:54:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A49D413C45E; Mon, 18 Feb 2008 13:54:06 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 59B252090; Mon, 18 Feb 2008 14:53:59 +0100 (CET) Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 438A52087; Mon, 18 Feb 2008 14:53:59 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 1A0068449D; Mon, 18 Feb 2008 14:53:59 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jim Bryant References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> Date: Mon, 18 Feb 2008 14:53:59 +0100 In-Reply-To: <86odae5rgr.fsf@ds4.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8rg?= =?utf-8?Q?rav=22's?= message of "Mon\, 18 Feb 2008 14\:23\:00 +0100") Message-ID: <863arq5q14.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 13:54:49 -0000 Dag-Erling Sm=C3=B8rgrav writes: > Purely in the interest of showing off, here is my version. It is 81 > bytes shorter than yours, it is valid C99 with POSIX extensions (yours > is not), and it produces 11,450 files in about 0.2% of the time yours > takes to produce 10,000. > > #include > #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; > #define a(i) b(i,v##i) > int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} Two bugs: 1) I forgot to include the correct version of the code 2) the version I had created a few files with '/' in their names; this slightly nastier creates 10,648 files with only letters. #include #define b(i,v)for(int v=3D65;v<87;){i[f]=3Dv++; #define a(i)b(i,v##i) int main(void){char f[4]=3D{47};a(1)a(2)a(3)truncate(f,0);}}}} DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:00:28 2008 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 E400C16A46E for ; Mon, 18 Feb 2008 14:00:28 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 2A14913C4D5 for ; Mon, 18 Feb 2008 14:00:27 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m1IDxmF0062860; Mon, 18 Feb 2008 20:59:48 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m1IDxmFb062859; Mon, 18 Feb 2008 20:59:48 +0700 (KRAT) (envelope-from eugen) Date: Mon, 18 Feb 2008 20:59:48 +0700 From: Eugene Grosbein To: des@des.no Message-ID: <20080218135948.GB62360@svzserv.kemerovo.su> References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <863arq5q14.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:00:29 -0000 On Mon, Feb 18, 2008 at 02:53:59PM +0100, Dag-Erling Sm??rgrav wrote: > Two bugs: [skip] That's all very funny, but what about a panic? It it true that it's possible for non-root to bring a file system to not-mountable state? Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:09:31 2008 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 ED54C16A417; Mon, 18 Feb 2008 14:09:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 9D8F013C442; Mon, 18 Feb 2008 14:09:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scoo-longs-computer.local (74-92-209-69-Colorado.hfc.comcastbusiness.net [74.92.209.69] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1IE9FaX012939; Mon, 18 Feb 2008 07:09:21 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47B9918B.6010301@samsco.org> Date: Mon, 18 Feb 2008 07:09:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> In-Reply-To: <863arq5q14.fsf@ds4.des.no> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.0 required=5.4 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:09:32 -0000 Dag-Erling Smørgrav wrote: > Dag-Erling Smørgrav writes: >> Purely in the interest of showing off, here is my version. It is 81 >> bytes shorter than yours, it is valid C99 with POSIX extensions (yours >> is not), and it produces 11,450 files in about 0.2% of the time yours >> takes to produce 10,000. >> >> #include >> #define b(i,v) for(int v=48;v<127;++v){f[i]=v; >> #define a(i) b(i,v##i) >> int main(void){char f[5]={'/'};a(1)a(2)a(3)truncate(f,0);}}}} > > Two bugs: > > 1) I forgot to include the correct version of the code > > 2) the version I had created a few files with '/' in their names; this > slightly nastier creates 10,648 files with only letters. > > #include > #define b(i,v)for(int v=65;v<87;){i[f]=v++; > #define a(i)b(i,v##i) > int main(void){char f[4]={47};a(1)a(2)a(3)truncate(f,0);}}}} > > DES This version also omits the constructive comments on the actual problem that the original poster identified. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:09:54 2008 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 727A916A496 for ; Mon, 18 Feb 2008 14:09:54 +0000 (UTC) (envelope-from dennis.melentyev@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id B984913C4F4 for ; Mon, 18 Feb 2008 14:09:53 +0000 (UTC) (envelope-from dennis.melentyev@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so1482630fgg.35 for ; Mon, 18 Feb 2008 06:09:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=m93MpZz/8SABrOJL8fhChbYxABBoZrU/I6gZdAejGwY=; b=txNLQ2SjYuOIbAUpQNLdCiQOfw36vRAHofiUK/6IMYTZJbD02yK/3EJLLrxvApzQsImy6Puy98qlc61mEW7eaR50f8ExqkUFgUOsIRBTpBSZTG2QnPu6rkhHyOrAdCLu0+kQbAbCX8nhUBci8D0g7en+FElD4BOwe+nMg712NGc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DQnQj+OULRiP+GLoCW5uQBfwI+Nqj8s3nchEhyPsJp19Lq0MduJlfJS7kpFdoJpzVYOO0iFVdlj9JzzmiuMN35yYn4X4mEy8ADiK9l7qBd4kwbv8RntJ85SD7P318YHoF7Za3oHu0BSpqgWSwqpm4vcvDbzp6BMOW6BqiWIZ8hg= Received: by 10.86.57.9 with SMTP id f9mr347796fga.28.1203343792243; Mon, 18 Feb 2008 06:09:52 -0800 (PST) Received: by 10.86.74.13 with HTTP; Mon, 18 Feb 2008 06:09:52 -0800 (PST) Message-ID: Date: Mon, 18 Feb 2008 16:09:52 +0200 From: "Dennis Melentyev" To: "=?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?=" In-Reply-To: <863arq5q14.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:09:54 -0000 RGFnLUVybGluZzogeW91IHdpbiEgWW91cidzIGxvbmdlciBhIGNvdXBsZSBvZiBpbmNoZXMgOikK ClNvcnJ5LCBteSBoYW5kcyBydW5zIGluIGZyb250IG9mIHRoZSBsb2NvLi4uCkhvcGUgdGhlcmUg YXJlIG5vdCBtdWNoIG9mICpzdWNoKiBzdHlsZWQgcHJlcHJvY2Vzc29yIGNvZGUgaW4gRnJlZUJT RD8KSXQgc2hvdWxkIGJlIGEgcGxhaW4gc3VpY2lkZSB0byBmaXggYSBidWcgaW4gaXQuCgoyMDA4 LzIvMTgsIERhZy1FcmxpbmcgU23DuHJncmF2IDxkZXNAZGVzLm5vPjoKPiBEYWctRXJsaW5nIFNt w7hyZ3JhdiA8ZGVzQGRlcy5ubz4gd3JpdGVzOgo+ID4gUHVyZWx5IGluIHRoZSBpbnRlcmVzdCBv ZiBzaG93aW5nIG9mZiwgaGVyZSBpcyBteSB2ZXJzaW9uLiAgSXQgaXMgODEKPiA+IGJ5dGVzIHNo b3J0ZXIgdGhhbiB5b3VycywgaXQgaXMgdmFsaWQgQzk5IHdpdGggUE9TSVggZXh0ZW5zaW9ucyAo eW91cnMKPiA+IGlzIG5vdCksIGFuZCBpdCBwcm9kdWNlcyAxMSw0NTAgZmlsZXMgaW4gYWJvdXQg MC4yJSBvZiB0aGUgdGltZSB5b3Vycwo+ID4gdGFrZXMgdG8gcHJvZHVjZSAxMCwwMDAuCj4gPgo+ ID4gI2luY2x1ZGUgPHVuaXN0ZC5oPgo+ID4gI2RlZmluZSBiKGksdikgZm9yKGludCB2PTQ4O3Y8 MTI3Oysrdil7ZltpXT12Owo+ID4gI2RlZmluZSBhKGkpIGIoaSx2IyNpKQo+ID4gaW50IG1haW4o dm9pZCl7Y2hhciBmWzVdPXsnLyd9O2EoMSlhKDIpYSgzKXRydW5jYXRlKGYsMCk7fX19fQo+Cj4g VHdvIGJ1Z3M6Cj4KPiAxKSBJIGZvcmdvdCB0byBpbmNsdWRlIHRoZSBjb3JyZWN0IHZlcnNpb24g b2YgdGhlIGNvZGUKPgo+IDIpIHRoZSB2ZXJzaW9uIEkgaGFkIGNyZWF0ZWQgYSBmZXcgZmlsZXMg d2l0aCAnLycgaW4gdGhlaXIgbmFtZXM7IHRoaXMKPiAgICBzbGlnaHRseSBuYXN0aWVyIGNyZWF0 ZXMgMTAsNjQ4IGZpbGVzIHdpdGggb25seSBsZXR0ZXJzLgo+Cj4gI2luY2x1ZGUgPHVuaXN0ZC5o Pgo+ICNkZWZpbmUgYihpLHYpZm9yKGludCB2PTY1O3Y8ODc7KXtpW2ZdPXYrKzsKPiAjZGVmaW5l IGEoaSliKGksdiMjaSkKPiBpbnQgbWFpbih2b2lkKXtjaGFyIGZbNF09ezQ3fTthKDEpYSgyKWEo Myl0cnVuY2F0ZShmLDApO319fX0KPgo+IERFUwo+IC0tCj4gRGFnLUVybGluZyBTbcO4cmdyYXYg LSBkZXNAZGVzLm5vCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KPiBmcmVlYnNkLXN0YWJsZUBmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QKPiBodHRwOi8v bGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXN0YWJsZQo+IFRvIHVu c3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLXN0YWJsZS11bnN1YnNjcmliZUBm cmVlYnNkLm9yZyIKPgoKCi0tIApEZW5uaXMgTWVsZW50eWV2Cg== From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:13:22 2008 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 A708916A473 for ; Mon, 18 Feb 2008 14:13:22 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by mx1.freebsd.org (Postfix) with ESMTP id 556A013C45A for ; Mon, 18 Feb 2008 14:13:22 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so1634540qbd.7 for ; Mon, 18 Feb 2008 06:13:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to:in-reply-to:content-type:x-mailer:mime-version:subject:content-transfer-encoding:date:cc; bh=9bLxeBN1YR5P3J2TSpLos4itvksm2Ux1AanE2niW2bg=; b=ZOyEdss95X3i8MhsBN78Bfix8JDkL7TFMi4gMJYZ9EUIZPkyEujwimahKNvfu/IqNOGN38fjogkwzGfq4ywdYDY+5ieboOoWspZCZgkd4yhDEKMEqn8uAfIAIkPBGw/xp91bDgLf4mcd+dThBCKcxBmeiUjytb45XtIO5EnwCgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type:x-mailer:mime-version:subject:content-transfer-encoding:date:cc; b=K8WTuo+gYNAU8BscKx9WUJ+sYcbKzVrxD9L63QBa+ggoz5AZwSDBAoRJnt5kcjoqK1gwLS8RG0+1Dc3JWgBSId99lhXsVcrKKB1Tn4I9SrI4c70JG3jGYX7THSqyBt1KufWhilFPjRl9dlaefKk8JM6FiKRPfsv+v8FPT5B5/ms= Received: by 10.110.68.10 with SMTP id q10mr3339856tia.28.1203343083226; Mon, 18 Feb 2008 05:58:03 -0800 (PST) Received: from ?10.6.146.10? ( [166.193.195.177]) by mx.google.com with ESMTPS id h18sm10024404wxd.18.2008.02.18.05.57.55 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Feb 2008 05:58:01 -0800 (PST) References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> Message-Id: From: Speedtoys To: Kurt Buff In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes X-Mailer: iPhone Mail (4A93) Mime-Version: 1.0 (iPhone Mail 4A93) Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Feb 2008 08:57:46 -0500 Cc: "freebsd-fs@freebsd.org" , =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , "FreeBSD-bugs@freebsd.org" , "freebsd-stable@freebsd.org" , "freebsd-security@freebsd.org" Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:13:22 -0000 Time for the idiot(proof) function call. Got brakes? =3D=3D=3D=3D=3D=3D 25hrs or one season with one pad set is possible. Save money and pit =20= time, compromise nothing. Ask how. TXT or Tone: 8414546712@txt.att.net http://www.speedtoys.com On Feb 18, 2008, at 8:27 AM, "Kurt Buff" wrote: > Patient: Doctor, it hurts when I do this! > > Doctor: Don't do that... > > On Feb 18, 2008 1:23 PM, Dag-Erling Sm=C3=B8rgrav wrote: >> Jim Bryant writes: >>> #include >>> #include >>> >>> int main(int argc, char **argv) { int i; char buf[1024]; bzero=20 >>> (buf, 1024); for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%=20= >>> 05d\n", argv[1], i); system((const char *)buf);} return(0);} >> >> Subject should be "how to take down a system [...] with three lines =20= >> of >> badly written C, provided you have root privileges already and are =20= >> too >> lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which = would >> accomplish the job much faster. >> >> Purely in the interest of showing off, here is my version. It is 81 >> bytes shorter than yours, it is valid C99 with POSIX extensions =20 >> (yours >> is not), and it produces 11,450 files in about 0.2% of the time yours >> takes to produce 10,000. >> >> #include >> #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; >> #define a(i) b(i,v##i) >> int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} >> >> DES >> -- >> Dag-Erling Sm=C3=B8rgrav - des@des.no >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to = "freebsd-security-unsubscribe@freebsd.org=20 >> " >> > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to = "freebsd-security-unsubscribe@freebsd.org=20 > " > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:14:22 2008 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 E2DD116A4C1; Mon, 18 Feb 2008 14:14:22 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by mx1.freebsd.org (Postfix) with ESMTP id 76FE213C468; Mon, 18 Feb 2008 14:14:22 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.1) with ESMTP id m1IEE8bd075081; Tue, 19 Feb 2008 01:14:08 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> To: "Kurt Buff" From: Mark Andrews In-reply-to: Your message of "Mon, 18 Feb 2008 13:27:01 -0000." Date: Tue, 19 Feb 2008 01:14:08 +1100 Sender: marka@isc.org Cc: FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:14:23 -0000 > Patient: Doctor, it hurts when I do this! > > Doctor: Don't do that... Did you actually bother to read his report? While his example is used "/", if the report is correct then you just need to replace "/" with the path of any file system mount point that is world writable like say "/tmp". Do you have /tmp mounted like this? /dev/ad0s4e 507630 162050 304970 35% /tmp Have you tried using "/tmp" or some other suitable mount point before slinging off with the old Doctor joke? Even if it is only "/", having the system die and not be recoverable due to having a excessive number of files in "/" is a critical error. I'm sure you have *never* accidently copied a set of files to "/" in your life. Me, I know I've made that sort of mistake in the past, and as I'm not perfect, I'm sure I'll make that sort of mistake at some point in the future. I would however like the machine not to fallover when I do make that mistake. Now why don't you be constructive and verify whether the report is valid or not. I don't have a spare machine to test it on so I'm not going to attempt it. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:15:07 2008 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 377C516A46D; Mon, 18 Feb 2008 14:15:07 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id A217C13C4EF; Mon, 18 Feb 2008 14:15:06 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 6BE6E1D187; Mon, 18 Feb 2008 16:15:04 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 114E61D0A9 for ; Mon, 18 Feb 2008 16:14:59 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id F3BFC60026; Mon, 18 Feb 2008 14:14:25 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 48AD816A4D1; Mon, 18 Feb 2008 14:14:25 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14D5A16A46C for ; Mon, 18 Feb 2008 14:14:15 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by mx1.freebsd.org (Postfix) with ESMTP id C166D13C45E for ; Mon, 18 Feb 2008 14:14:09 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.1) with ESMTP id m1IEE8bd075081; Tue, 19 Feb 2008 01:14:08 +1100 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> To: "Kurt Buff" From: Mark Andrews In-reply-to: Your message of "Mon, 18 Feb 2008 13:27:01 -0000." Date: Tue, 19 Feb 2008 01:14:08 +1100 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 14:15:07 -0000 > Patient: Doctor, it hurts when I do this! > > Doctor: Don't do that... Did you actually bother to read his report? While his example is used "/", if the report is correct then you just need to replace "/" with the path of any file system mount point that is world writable like say "/tmp". Do you have /tmp mounted like this? /dev/ad0s4e 507630 162050 304970 35% /tmp Have you tried using "/tmp" or some other suitable mount point before slinging off with the old Doctor joke? Even if it is only "/", having the system die and not be recoverable due to having a excessive number of files in "/" is a critical error. I'm sure you have *never* accidently copied a set of files to "/" in your life. Me, I know I've made that sort of mistake in the past, and as I'm not perfect, I'm sure I'll make that sort of mistake at some point in the future. I would however like the machine not to fallover when I do make that mistake. Now why don't you be constructive and verify whether the report is valid or not. I don't have a spare machine to test it on so I'm not going to attempt it. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:27:25 2008 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 E949516A41A; Mon, 18 Feb 2008 14:27:24 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 5EF1113C4E3; Mon, 18 Feb 2008 14:27:23 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 721A41D0F3; Mon, 18 Feb 2008 16:27:22 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 043AD1CE9C for ; Mon, 18 Feb 2008 16:27:17 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5CC425E979; Mon, 18 Feb 2008 14:26:01 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 188A416A4C9; Mon, 18 Feb 2008 14:25:59 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9647C16A418; Mon, 18 Feb 2008 14:25:51 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id EB16813C467; Mon, 18 Feb 2008 14:25:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F094046B62; Mon, 18 Feb 2008 09:25:48 -0500 (EST) Date: Mon, 18 Feb 2008 14:25:48 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jim Bryant In-Reply-To: <47B91080.9010109@electron-tube.net> Message-ID: <20080218142004.O49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <47B91080.9010109@electron-tube.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 14:27:25 -0000 On Sun, 17 Feb 2008, Jim Bryant wrote: > FYI: The system assigned kern/120781 to this bug report. > > IMHO, a security advisory should be issued ASAP. Thanks for the report, I'm sure your widely distributed e-mail will get someone looking at it quickly. In the future if you run into an issue you think might require a security advisory, consider e-mailing it privately to secteam@FreeBSD.org so that the release of patches can cooincide with publication of the problem. That said, this is probably more a candidate for an errata patch rather than a security advisory -- security advisories are normally limited to local/remote privilege escalation or serious remote denial of service. Local denial of service problems occur in all operating systems I'm aware of with such frequency that the world would be continuously innundated with advisories to the point of rendering advisories useless if we did them every time someone discovered a way users could crash the system. You need only watch the change logs of the various open source kernels for the words "fix panic", "don't dereference NULL pointer", "don't leak a lock...", etc, to get a sense of the quantity of locally exercisable system bugs, many of which can lead to reboots, hangs, or data loss, to see why. Hopefully this bug will get resolved shortly, and then we can evaluate if an errata notice is necessary. Robert N M Watson Computer Laboratory University of Cambridge > > Jim Bryant wrote: >> One line summary: >> Too many files in a top-level UFS-2 filesystem directory will cause a >> panic on mount. >> >> Kern/Critical/High Priority/SW-Bug >> >> Which FreeBSD Release You Are Using: >> 6.3-STABLE >> >> Environment (output of "uname -a" on the problem machine): >> FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 >> 21:13:39 CST 2008 >> jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 >> >> Note: I just cvsupped earlier, and no changes have been put into cvsup >> that would fix this problem. >> >> Full Description: >> I was doing a reorganization of my filesystems, and since I do offline >> installs, I keep a local distfiles collection (or did until yesterday when >> this happened), and in the process, put all of the distfiles on their own >> filesystem to be mounted under /usr/ports/distfiles. >> >> All was fine until I rebooted. >> >> On rebooting, I got a page fault panic on mount of the new distfiles >> filesystem. >> >> i booted again, got it again, booted again this time into single-user, and >> did a fsck on the filesystem, and it only showed as being "dirty", but >> otherwise had no problems in the eyes of fsck. booted again, instant >> panic. >> >> i booted an older 6.2 CD and mounted the filesystem fine. i then put that >> filesystem the way it was by mkdir'ing a distfiles dir and mv'ing >> everything into it, but on reboot it still paniced on mount. >> >> only a newfs was able to enable the filesystem to be mounted. >> >> today i did further research, thinking it had to do with the number of >> files in the top-level filesystem directory, and found that to be true. >> the short c program in the next section (how to repeat the problem) >> contains this. >> >> a second test shows that, after a newfs, if this done in any subdirectory >> of that filesystem, the panic is averted, and all is well. apparently this >> bug only effects top-level directories of a UFS2 filesystem. >> >> I have not attempted this to a non-UFS2 filesystem. >> >> IMHO, a security advisory should be released, since any user with write >> access to ANY top level directory of ANY mounted filesystem (most systems >> have /tmp as a world writable top level filesystem directory) can create a >> panic situation requiring a newfs of the said filesystem. A malicious user >> with root access can do this to /. Either way, on boot, or any attempt to >> mount said filesystem on a running system, will cause a panic, which of >> course will cause an unbootable system on reboot. >> >> How to repeat the problem: >> Compile and run the following as instructed: >> >> #include >> #include >> >> int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024); >> for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i); >> system((const char *)buf);} return(0);} >> >> /* pass a top-level mountpoint directory name of a mounted filesystem, with >> a trailing slash to the above as argv[1], and run. >> >> This will create 10,000 zero-length files in the specified directory. >> >> umount that filesystem. >> >> perform a shitload of sync's to make sure everything outstanding is flushed >> to disk on all filesystems. >> >> mount the target filesystem (preferably from a vty or serial console to >> catch the messages when it panics, which it will as soon as the mount is >> attempted). >> */ >> >> Fix to the problem if known: >> newfs(8) >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:35:53 2008 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 F353916A41A for ; Mon, 18 Feb 2008 14:35:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id B0DB613C455 for ; Mon, 18 Feb 2008 14:35:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id F094046B62; Mon, 18 Feb 2008 09:25:48 -0500 (EST) Date: Mon, 18 Feb 2008 14:25:48 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jim Bryant In-Reply-To: <47B91080.9010109@electron-tube.net> Message-ID: <20080218142004.O49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <47B91080.9010109@electron-tube.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:35:53 -0000 On Sun, 17 Feb 2008, Jim Bryant wrote: > FYI: The system assigned kern/120781 to this bug report. > > IMHO, a security advisory should be issued ASAP. Thanks for the report, I'm sure your widely distributed e-mail will get someone looking at it quickly. In the future if you run into an issue you think might require a security advisory, consider e-mailing it privately to secteam@FreeBSD.org so that the release of patches can cooincide with publication of the problem. That said, this is probably more a candidate for an errata patch rather than a security advisory -- security advisories are normally limited to local/remote privilege escalation or serious remote denial of service. Local denial of service problems occur in all operating systems I'm aware of with such frequency that the world would be continuously innundated with advisories to the point of rendering advisories useless if we did them every time someone discovered a way users could crash the system. You need only watch the change logs of the various open source kernels for the words "fix panic", "don't dereference NULL pointer", "don't leak a lock...", etc, to get a sense of the quantity of locally exercisable system bugs, many of which can lead to reboots, hangs, or data loss, to see why. Hopefully this bug will get resolved shortly, and then we can evaluate if an errata notice is necessary. Robert N M Watson Computer Laboratory University of Cambridge > > Jim Bryant wrote: >> One line summary: >> Too many files in a top-level UFS-2 filesystem directory will cause a >> panic on mount. >> >> Kern/Critical/High Priority/SW-Bug >> >> Which FreeBSD Release You Are Using: >> 6.3-STABLE >> >> Environment (output of "uname -a" on the problem machine): >> FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb 10 >> 21:13:39 CST 2008 >> jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 >> >> Note: I just cvsupped earlier, and no changes have been put into cvsup >> that would fix this problem. >> >> Full Description: >> I was doing a reorganization of my filesystems, and since I do offline >> installs, I keep a local distfiles collection (or did until yesterday when >> this happened), and in the process, put all of the distfiles on their own >> filesystem to be mounted under /usr/ports/distfiles. >> >> All was fine until I rebooted. >> >> On rebooting, I got a page fault panic on mount of the new distfiles >> filesystem. >> >> i booted again, got it again, booted again this time into single-user, and >> did a fsck on the filesystem, and it only showed as being "dirty", but >> otherwise had no problems in the eyes of fsck. booted again, instant >> panic. >> >> i booted an older 6.2 CD and mounted the filesystem fine. i then put that >> filesystem the way it was by mkdir'ing a distfiles dir and mv'ing >> everything into it, but on reboot it still paniced on mount. >> >> only a newfs was able to enable the filesystem to be mounted. >> >> today i did further research, thinking it had to do with the number of >> files in the top-level filesystem directory, and found that to be true. >> the short c program in the next section (how to repeat the problem) >> contains this. >> >> a second test shows that, after a newfs, if this done in any subdirectory >> of that filesystem, the panic is averted, and all is well. apparently this >> bug only effects top-level directories of a UFS2 filesystem. >> >> I have not attempted this to a non-UFS2 filesystem. >> >> IMHO, a security advisory should be released, since any user with write >> access to ANY top level directory of ANY mounted filesystem (most systems >> have /tmp as a world writable top level filesystem directory) can create a >> panic situation requiring a newfs of the said filesystem. A malicious user >> with root access can do this to /. Either way, on boot, or any attempt to >> mount said filesystem on a running system, will cause a panic, which of >> course will cause an unbootable system on reboot. >> >> How to repeat the problem: >> Compile and run the following as instructed: >> >> #include >> #include >> >> int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024); >> for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i); >> system((const char *)buf);} return(0);} >> >> /* pass a top-level mountpoint directory name of a mounted filesystem, with >> a trailing slash to the above as argv[1], and run. >> >> This will create 10,000 zero-length files in the specified directory. >> >> umount that filesystem. >> >> perform a shitload of sync's to make sure everything outstanding is flushed >> to disk on all filesystems. >> >> mount the target filesystem (preferably from a vty or serial console to >> catch the messages when it panics, which it will as soon as the mount is >> attempted). >> */ >> >> Fix to the problem if known: >> newfs(8) >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:48:17 2008 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 7C33516A417; Mon, 18 Feb 2008 14:48:17 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 0D4A713C457; Mon, 18 Feb 2008 14:48:16 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 83BD31D16E; Mon, 18 Feb 2008 16:48:15 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id D2CFE1D0DC for ; Mon, 18 Feb 2008 16:48:10 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 2EF402EFED; Mon, 18 Feb 2008 14:47:39 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BA7D116A547; Mon, 18 Feb 2008 14:47:36 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C03F516A418 for ; Mon, 18 Feb 2008 14:47:28 +0000 (UTC) (envelope-from ady@ady.ro) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.242]) by mx1.freebsd.org (Postfix) with ESMTP id 863AE13C45A for ; Mon, 18 Feb 2008 14:47:28 +0000 (UTC) (envelope-from ady@ady.ro) Received: by ag-out-0708.google.com with SMTP id 5so2548706agb.7 for ; Mon, 18 Feb 2008 06:47:28 -0800 (PST) Received: by 10.142.72.21 with SMTP id u21mr4365062wfa.82.1203345155884; Mon, 18 Feb 2008 06:32:35 -0800 (PST) Received: by 10.142.109.6 with HTTP; Mon, 18 Feb 2008 06:32:35 -0800 (PST) Message-ID: <78cb3d3f0802180632u1d38ec67i432052d9c77dd706@mail.gmail.com> Date: Mon, 18 Feb 2008 16:32:35 +0200 From: "Adrian Penisoara" To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, freebsd-security@freebsd.org In-Reply-To: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> MIME-Version: 1.0 References: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> X-Google-Sender-Auth: 624f5be56ab92cd1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 14:48:17 -0000 Hi, I would agree with Mark and Jim, this is a serious issue for enterprise servers. Yet another example where I would have wanted to see a more supportive response from the FreeBSD project members, like Robert Watson just did. This would benefit keeping a good relation with the business users. Thanks, Adrian Penisoara ROFUG / EnterpriseBSD On Feb 18, 2008 4:14 PM, Mark Andrews wrote: > > > Patient: Doctor, it hurts when I do this! > > > > Doctor: Don't do that... > > Did you actually bother to read his report? > > While his example is used "/", if the report is correct then you > just need to replace "/" with the path of any file system mount > point that is world writable like say "/tmp". > > Do you have /tmp mounted like this? > /dev/ad0s4e 507630 162050 304970 35% /tmp > > Have you tried using "/tmp" or some other suitable mount point > before slinging off with the old Doctor joke? > > Even if it is only "/", having the system die and not be recoverable > due to having a excessive number of files in "/" is a critical > error. I'm sure you have *never* accidently copied a set of files > to "/" in your life. Me, I know I've made that sort of mistake in > the past, and as I'm not perfect, I'm sure I'll make that sort of > mistake at some point in the future. I would however like the > machine not to fallover when I do make that mistake. > > Now why don't you be constructive and verify whether the report is > valid or not. I don't have a spare machine to test it on so I'm > not going to attempt it. > > Mark > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " > _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 14:48:38 2008 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 4D1E716A480 for ; Mon, 18 Feb 2008 14:48:38 +0000 (UTC) (envelope-from ady@ady.ro) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.242]) by mx1.freebsd.org (Postfix) with ESMTP id E857A13C447 for ; Mon, 18 Feb 2008 14:48:37 +0000 (UTC) (envelope-from ady@ady.ro) Received: by ag-out-0708.google.com with SMTP id 5so2550084agb.7 for ; Mon, 18 Feb 2008 06:48:37 -0800 (PST) Received: by 10.142.72.21 with SMTP id u21mr4365062wfa.82.1203345155884; Mon, 18 Feb 2008 06:32:35 -0800 (PST) Received: by 10.142.109.6 with HTTP; Mon, 18 Feb 2008 06:32:35 -0800 (PST) Message-ID: <78cb3d3f0802180632u1d38ec67i432052d9c77dd706@mail.gmail.com> Date: Mon, 18 Feb 2008 16:32:35 +0200 From: "Adrian Penisoara" Sender: ady@ady.ro To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, freebsd-security@freebsd.org In-Reply-To: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> MIME-Version: 1.0 References: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> X-Google-Sender-Auth: 624f5be56ab92cd1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 14:48:38 -0000 Hi, I would agree with Mark and Jim, this is a serious issue for enterprise servers. Yet another example where I would have wanted to see a more supportive response from the FreeBSD project members, like Robert Watson just did. This would benefit keeping a good relation with the business users. Thanks, Adrian Penisoara ROFUG / EnterpriseBSD On Feb 18, 2008 4:14 PM, Mark Andrews wrote: > > > Patient: Doctor, it hurts when I do this! > > > > Doctor: Don't do that... > > Did you actually bother to read his report? > > While his example is used "/", if the report is correct then you > just need to replace "/" with the path of any file system mount > point that is world writable like say "/tmp". > > Do you have /tmp mounted like this? > /dev/ad0s4e 507630 162050 304970 35% /tmp > > Have you tried using "/tmp" or some other suitable mount point > before slinging off with the old Doctor joke? > > Even if it is only "/", having the system die and not be recoverable > due to having a excessive number of files in "/" is a critical > error. I'm sure you have *never* accidently copied a set of files > to "/" in your life. Me, I know I've made that sort of mistake in > the past, and as I'm not perfect, I'm sure I'll make that sort of > mistake at some point in the future. I would however like the > machine not to fallover when I do make that mistake. > > Now why don't you be constructive and verify whether the report is > valid or not. I don't have a spare machine to test it on so I'm > not going to attempt it. > > Mark > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:07:38 2008 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 CFE1E16A418; Mon, 18 Feb 2008 15:07:38 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 45D7513C46E; Mon, 18 Feb 2008 15:07:37 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 4E5F81D09A; Mon, 18 Feb 2008 17:07:36 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: ** X-Spam-Status: No, score=2.0 required=6.0 tests=RATWR8_MESSID autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 6AADC1CFDA for ; Mon, 18 Feb 2008 17:07:23 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 8F5B619CEC; Mon, 18 Feb 2008 15:06:49 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D10316A481; Mon, 18 Feb 2008 15:06:49 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAA9516A49E for ; Mon, 18 Feb 2008 14:13:57 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.227]) by mx1.freebsd.org (Postfix) with ESMTP id 513E313C4D5 for ; Mon, 18 Feb 2008 14:13:56 +0000 (UTC) (envelope-from speedtoys.racing@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so1634968qbd.7 for ; Mon, 18 Feb 2008 06:13:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to:in-reply-to:content-type:x-mailer:mime-version:subject:content-transfer-encoding:date:cc; bh=9bLxeBN1YR5P3J2TSpLos4itvksm2Ux1AanE2niW2bg=; b=ZOyEdss95X3i8MhsBN78Bfix8JDkL7TFMi4gMJYZ9EUIZPkyEujwimahKNvfu/IqNOGN38fjogkwzGfq4ywdYDY+5ieboOoWspZCZgkd4yhDEKMEqn8uAfIAIkPBGw/xp91bDgLf4mcd+dThBCKcxBmeiUjytb45XtIO5EnwCgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type:x-mailer:mime-version:subject:content-transfer-encoding:date:cc; b=K8WTuo+gYNAU8BscKx9WUJ+sYcbKzVrxD9L63QBa+ggoz5AZwSDBAoRJnt5kcjoqK1gwLS8RG0+1Dc3JWgBSId99lhXsVcrKKB1Tn4I9SrI4c70JG3jGYX7THSqyBt1KufWhilFPjRl9dlaefKk8JM6FiKRPfsv+v8FPT5B5/ms= Received: by 10.110.68.10 with SMTP id q10mr3339856tia.28.1203343083226; Mon, 18 Feb 2008 05:58:03 -0800 (PST) Received: from ?10.6.146.10? ( [166.193.195.177]) by mx.google.com with ESMTPS id h18sm10024404wxd.18.2008.02.18.05.57.55 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Feb 2008 05:58:01 -0800 (PST) References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> Message-Id: From: Speedtoys To: Kurt Buff In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes X-Mailer: iPhone Mail (4A93) Mime-Version: 1.0 (iPhone Mail 4A93) Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Feb 2008 08:57:46 -0500 X-Mailman-Approved-At: Mon, 18 Feb 2008 15:06:44 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: "freebsd-fs@freebsd.org" , =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= , "FreeBSD-bugs@freebsd.org" , "freebsd-stable@freebsd.org" , "freebsd-security@freebsd.org" Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 15:07:39 -0000 Time for the idiot(proof) function call. Got brakes? =3D=3D=3D=3D=3D=3D 25hrs or one season with one pad set is possible. Save money and pit =20= time, compromise nothing. Ask how. TXT or Tone: 8414546712@txt.att.net http://www.speedtoys.com On Feb 18, 2008, at 8:27 AM, "Kurt Buff" wrote: > Patient: Doctor, it hurts when I do this! > > Doctor: Don't do that... > > On Feb 18, 2008 1:23 PM, Dag-Erling Sm=C3=B8rgrav wrote: >> Jim Bryant writes: >>> #include >>> #include >>> >>> int main(int argc, char **argv) { int i; char buf[1024]; bzero=20 >>> (buf, 1024); for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%=20= >>> 05d\n", argv[1], i); system((const char *)buf);} return(0);} >> >> Subject should be "how to take down a system [...] with three lines =20= >> of >> badly written C, provided you have root privileges already and are =20= >> too >> lazy to just dd if=3D/dev/zero of=3D/dev/ad0s1 count=3D100", which = would >> accomplish the job much faster. >> >> Purely in the interest of showing off, here is my version. It is 81 >> bytes shorter than yours, it is valid C99 with POSIX extensions =20 >> (yours >> is not), and it produces 11,450 files in about 0.2% of the time yours >> takes to produce 10,000. >> >> #include >> #define b(i,v) for(int v=3D48;v<127;++v){f[i]=3Dv; >> #define a(i) b(i,v##i) >> int main(void){char f[5]=3D{'/'};a(1)a(2)a(3)truncate(f,0);}}}} >> >> DES >> -- >> Dag-Erling Sm=C3=B8rgrav - des@des.no >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to = "freebsd-security-unsubscribe@freebsd.org=20 >> " >> > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to = "freebsd-security-unsubscribe@freebsd.org=20 > " > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:08:29 2008 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 9FAFF16A473; Mon, 18 Feb 2008 15:08:29 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id 18E5613C467; Mon, 18 Feb 2008 15:08:29 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 3A8D41D151; Mon, 18 Feb 2008 17:08:28 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.2 required=6.0 tests=MR_NOT_ATTRIBUTED_IP autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id E35731D09A for ; Mon, 18 Feb 2008 17:08:23 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 322F36082E; Mon, 18 Feb 2008 15:06:59 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F6DB16A4E9; Mon, 18 Feb 2008 15:06:59 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54DAA16A41A; Mon, 18 Feb 2008 14:32:14 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 0407C13C4F7; Mon, 18 Feb 2008 14:32:13 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scoo-longs-computer.local (74-92-209-69-Colorado.hfc.comcastbusiness.net [74.92.209.69] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1IE9FaX012939; Mon, 18 Feb 2008 07:09:21 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47B9918B.6010301@samsco.org> Date: Mon, 18 Feb 2008 07:09:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> In-Reply-To: <863arq5q14.fsf@ds4.des.no> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 18 Feb 2008 15:06:52 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 15:08:29 -0000 Dag-Erling Smørgrav wrote: > Dag-Erling Smørgrav writes: >> Purely in the interest of showing off, here is my version. It is 81 >> bytes shorter than yours, it is valid C99 with POSIX extensions (yours >> is not), and it produces 11,450 files in about 0.2% of the time yours >> takes to produce 10,000. >> >> #include >> #define b(i,v) for(int v=48;v<127;++v){f[i]=v; >> #define a(i) b(i,v##i) >> int main(void){char f[5]={'/'};a(1)a(2)a(3)truncate(f,0);}}}} > > Two bugs: > > 1) I forgot to include the correct version of the code > > 2) the version I had created a few files with '/' in their names; this > slightly nastier creates 10,648 files with only letters. > > #include > #define b(i,v)for(int v=65;v<87;){i[f]=v++; > #define a(i)b(i,v##i) > int main(void){char f[4]={47};a(1)a(2)a(3)truncate(f,0);}}}} > > DES This version also omits the constructive comments on the actual problem that the original poster identified. Scott _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:11:08 2008 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 2F55D16A419; Mon, 18 Feb 2008 15:11:08 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id BD87513C447; Mon, 18 Feb 2008 15:11:07 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id DD2031D190; Mon, 18 Feb 2008 17:11:06 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id 2DE801D09A for ; Mon, 18 Feb 2008 17:11:02 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 0D77817E3D; Mon, 18 Feb 2008 15:07:21 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DCF8316A4D5; Mon, 18 Feb 2008 15:07:21 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7D7316A417; Mon, 18 Feb 2008 14:35:36 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 99F3213C45B; Mon, 18 Feb 2008 14:35:35 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m1IDxmF0062860; Mon, 18 Feb 2008 20:59:48 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m1IDxmFb062859; Mon, 18 Feb 2008 20:59:48 +0700 (KRAT) (envelope-from eugen) Date: Mon, 18 Feb 2008 20:59:48 +0700 From: Eugene Grosbein To: des@des.no Message-ID: <20080218135948.GB62360@svzserv.kemerovo.su> References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <863arq5q14.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Mon, 18 Feb 2008 15:07:16 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 15:11:08 -0000 On Mon, Feb 18, 2008 at 02:53:59PM +0100, Dag-Erling Sm??rgrav wrote: > Two bugs: [skip] That's all very funny, but what about a panic? It it true that it's possible for non-root to bring a file system to not-mountable state? Eugene Grosbein _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:13:31 2008 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 4C0B916A418; Mon, 18 Feb 2008 15:13:31 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 025F613C46A; Mon, 18 Feb 2008 15:13:30 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from scoo-longs-computer.local (74-92-209-69-Colorado.hfc.comcastbusiness.net [74.92.209.69] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m1IFDKtl013565; Mon, 18 Feb 2008 08:13:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <47B9A08F.4080703@samsco.org> Date: Mon, 18 Feb 2008 08:13:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Adrian Penisoara References: <200802181414.m1IEE8bd075081@drugs.dv.isc.org> <78cb3d3f0802180632u1d38ec67i432052d9c77dd706@mail.gmail.com> In-Reply-To: <78cb3d3f0802180632u1d38ec67i432052d9c77dd706@mail.gmail.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.4 tests=none autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 15:13:31 -0000 Adrian Penisoara wrote: > Hi, > > I would agree with Mark and Jim, this is a serious issue for enterprise > servers. Yet another example where I would have wanted to see a more > supportive response from the FreeBSD project members, like Robert Watson > just did. This would benefit keeping a good relation with the business > users. > The responses from Dag-Erling was pretty much what I'd expect to see on a linux mailing list. Hopefully this filesystem issue gets some attention. Scott From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:29:30 2008 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 1669E16A41B for ; Mon, 18 Feb 2008 15:29:30 +0000 (UTC) (envelope-from phisher1@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.239]) by mx1.freebsd.org (Postfix) with ESMTP id 9DBB813C474 for ; Mon, 18 Feb 2008 15:29:29 +0000 (UTC) (envelope-from phisher1@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so1687349qbd.7 for ; Mon, 18 Feb 2008 07:29:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=C1CPtFis2TVigXkW1JLW7KwnehKe6ffMD4EnW37XqqU=; b=DTj0KFzOweXJ8dyFSpL0mTA1swb4dBdUR+Zq7Xe4TPAq10bNEgfCKGZR+dkMkPK5GBSPuSZFX/vvteyaZmGBYAws5kiYwMuQRW/G6HOOtPVS/qZILjjIY9bVKdLQwPTX4sbJf07y8R33N2x47VFN3Yz0TtvaabEdyaqKyWGqLMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=i0GtlivR/YwwY3zY4XVY43RfbVZG++mLScK1pNeT5NQCTnv/Cjd8/3gRkDEDJ2mkySrp/jE5zsmNHE5DPTE96RcEnxbxnOX7ese9xQZNpW+eiKEQLiEBauHNS7dtVZaqFqG6/0gTrHJOna0mte0c3vFGW/EPa50tENj8y0BXhSw= Received: by 10.114.37.1 with SMTP id k1mr2931815wak.6.1203347670178; Mon, 18 Feb 2008 07:14:30 -0800 (PST) Received: by 10.114.109.15 with HTTP; Mon, 18 Feb 2008 07:14:30 -0800 (PST) Message-ID: <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> Date: Mon, 18 Feb 2008 09:14:30 -0600 From: "Daniel Corrigan" To: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: <47B90868.7000900@electron-tube.net> MIME-Version: 1.0 References: <47B90868.7000900@electron-tube.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 15:29:30 -0000 Since this was released to a public mailing list, I can only assume some less than nice user will attempt this. The only top level file system I have that can be written to by normal users is /tmp Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from causing harm? Dan On Feb 17, 2008 10:24 PM, Jim Bryant wrote: > One line summary: > Too many files in a top-level UFS-2 filesystem directory will cause > a panic on mount. > > Kern/Critical/High Priority/SW-Bug > > Which FreeBSD Release You Are Using: > 6.3-STABLE > > Environment (output of "uname -a" on the problem machine): > FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb > 10 21:13:39 CST 2008 > jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 > > Note: I just cvsupped earlier, and no changes have been put into > cvsup that would fix this problem. > > Full Description: > I was doing a reorganization of my filesystems, and since I do > offline installs, I keep a local distfiles collection (or did until > yesterday when this happened), and in the process, put all of the > distfiles on their own filesystem to be mounted under > /usr/ports/distfiles. > > All was fine until I rebooted. > > On rebooting, I got a page fault panic on mount of the new distfiles > filesystem. > > i booted again, got it again, booted again this time into single-user, > and did a fsck on the filesystem, and it only showed as being "dirty", > but otherwise had no problems in the eyes of fsck. booted again, > instant panic. > > i booted an older 6.2 CD and mounted the filesystem fine. i then put > that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing > everything into it, but on reboot it still paniced on mount. > > only a newfs was able to enable the filesystem to be mounted. > > today i did further research, thinking it had to do with the number of > files in the top-level filesystem directory, and found that to be true. > the short c program in the next section (how to repeat the problem) > contains this. > > a second test shows that, after a newfs, if this done in any > subdirectory of that filesystem, the panic is averted, and all is well. > apparently this bug only effects top-level directories of a UFS2 > filesystem. > > I have not attempted this to a non-UFS2 filesystem. > > IMHO, a security advisory should be released, since any user with write > access to ANY top level directory of ANY mounted filesystem (most > systems have /tmp as a world writable top level filesystem directory) > can create a panic situation requiring a newfs of the said filesystem. > A malicious user with root access can do this to /. Either way, on > boot, or any attempt to mount said filesystem on a running system, will > cause a panic, which of course will cause an unbootable system on reboot. > > How to repeat the problem: > Compile and run the following as instructed: > > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, > 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", > argv[1], i); system((const char *)buf);} return(0);} > > /* pass a top-level mountpoint directory name of a mounted filesystem, > with a trailing slash to the above as argv[1], and run. > > This will create 10,000 zero-length files in the specified directory. > > umount that filesystem. > > perform a shitload of sync's to make sure everything outstanding is > flushed to disk on all filesystems. > > mount the target filesystem (preferably from a vty or serial console to > catch the messages when it panics, which it will as soon as the mount is > attempted). > */ > > Fix to the problem if known: > newfs(8) > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:30:06 2008 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 4125316A420; Mon, 18 Feb 2008 15:30:06 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: from mail.radiokom.kr.ua (smtp.radiokom.kr.ua [193.17.174.11]) by mx1.freebsd.org (Postfix) with ESMTP id BC4F313C4EE; Mon, 18 Feb 2008 15:30:05 +0000 (UTC) (envelope-from filter@mail.radiokom.kr.ua) Received: by mail.radiokom.kr.ua (Postfix, from userid 1003) id 02F0B1D215; Mon, 18 Feb 2008 17:30:02 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on shayba.homenet.kr.ua X-Spam-Level: X-Spam-Status: No, score=0.0 required=6.0 tests=none autolearn=disabled version=3.1.8 Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by mail.radiokom.kr.ua (Postfix) with ESMTP id BD0BD1D187 for ; Mon, 18 Feb 2008 17:29:55 +0200 (EET) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id E76445FCB3; Mon, 18 Feb 2008 15:29:10 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D390416A4EB; Mon, 18 Feb 2008 15:29:10 +0000 (UTC) (envelope-from owner-freebsd-security@freebsd.org) Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BC1B16A420 for ; Mon, 18 Feb 2008 15:29:02 +0000 (UTC) (envelope-from phisher1@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.239]) by mx1.freebsd.org (Postfix) with ESMTP id F0CB513C448 for ; Mon, 18 Feb 2008 15:29:01 +0000 (UTC) (envelope-from phisher1@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so1687349qbd.7 for ; Mon, 18 Feb 2008 07:29:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=C1CPtFis2TVigXkW1JLW7KwnehKe6ffMD4EnW37XqqU=; b=DTj0KFzOweXJ8dyFSpL0mTA1swb4dBdUR+Zq7Xe4TPAq10bNEgfCKGZR+dkMkPK5GBSPuSZFX/vvteyaZmGBYAws5kiYwMuQRW/G6HOOtPVS/qZILjjIY9bVKdLQwPTX4sbJf07y8R33N2x47VFN3Yz0TtvaabEdyaqKyWGqLMk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=i0GtlivR/YwwY3zY4XVY43RfbVZG++mLScK1pNeT5NQCTnv/Cjd8/3gRkDEDJ2mkySrp/jE5zsmNHE5DPTE96RcEnxbxnOX7ese9xQZNpW+eiKEQLiEBauHNS7dtVZaqFqG6/0gTrHJOna0mte0c3vFGW/EPa50tENj8y0BXhSw= Received: by 10.114.37.1 with SMTP id k1mr2931815wak.6.1203347670178; Mon, 18 Feb 2008 07:14:30 -0800 (PST) Received: by 10.114.109.15 with HTTP; Mon, 18 Feb 2008 07:14:30 -0800 (PST) Message-ID: <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> Date: Mon, 18 Feb 2008 09:14:30 -0600 From: "Daniel Corrigan" To: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: <47B90868.7000900@electron-tube.net> MIME-Version: 1.0 References: <47B90868.7000900@electron-tube.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Sender: owner-freebsd-security@freebsd.org Errors-To: owner-freebsd-security@freebsd.org Cc: Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 15:30:06 -0000 Since this was released to a public mailing list, I can only assume some less than nice user will attempt this. The only top level file system I have that can be written to by normal users is /tmp Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from causing harm? Dan On Feb 17, 2008 10:24 PM, Jim Bryant wrote: > One line summary: > Too many files in a top-level UFS-2 filesystem directory will cause > a panic on mount. > > Kern/Critical/High Priority/SW-Bug > > Which FreeBSD Release You Are Using: > 6.3-STABLE > > Environment (output of "uname -a" on the problem machine): > FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb > 10 21:13:39 CST 2008 > jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 > > Note: I just cvsupped earlier, and no changes have been put into > cvsup that would fix this problem. > > Full Description: > I was doing a reorganization of my filesystems, and since I do > offline installs, I keep a local distfiles collection (or did until > yesterday when this happened), and in the process, put all of the > distfiles on their own filesystem to be mounted under > /usr/ports/distfiles. > > All was fine until I rebooted. > > On rebooting, I got a page fault panic on mount of the new distfiles > filesystem. > > i booted again, got it again, booted again this time into single-user, > and did a fsck on the filesystem, and it only showed as being "dirty", > but otherwise had no problems in the eyes of fsck. booted again, > instant panic. > > i booted an older 6.2 CD and mounted the filesystem fine. i then put > that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing > everything into it, but on reboot it still paniced on mount. > > only a newfs was able to enable the filesystem to be mounted. > > today i did further research, thinking it had to do with the number of > files in the top-level filesystem directory, and found that to be true. > the short c program in the next section (how to repeat the problem) > contains this. > > a second test shows that, after a newfs, if this done in any > subdirectory of that filesystem, the panic is averted, and all is well. > apparently this bug only effects top-level directories of a UFS2 > filesystem. > > I have not attempted this to a non-UFS2 filesystem. > > IMHO, a security advisory should be released, since any user with write > access to ANY top level directory of ANY mounted filesystem (most > systems have /tmp as a world writable top level filesystem directory) > can create a panic situation requiring a newfs of the said filesystem. > A malicious user with root access can do this to /. Either way, on > boot, or any attempt to mount said filesystem on a running system, will > cause a panic, which of course will cause an unbootable system on reboot. > > How to repeat the problem: > Compile and run the following as instructed: > > #include > #include > > int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, > 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", > argv[1], i); system((const char *)buf);} return(0);} > > /* pass a top-level mountpoint directory name of a mounted filesystem, > with a trailing slash to the above as argv[1], and run. > > This will create 10,000 zero-length files in the specified directory. > > umount that filesystem. > > perform a shitload of sync's to make sure everything outstanding is > flushed to disk on all filesystems. > > mount the target filesystem (preferably from a vty or serial console to > catch the messages when it panics, which it will as soon as the mount is > attempted). > */ > > Fix to the problem if known: > newfs(8) > > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " > _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 15:31:26 2008 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 9484F16A417 for ; Mon, 18 Feb 2008 15:31:26 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from mail.beenic.net (mail.beenic.net [83.246.72.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5E40B13C458 for ; Mon, 18 Feb 2008 15:31:26 +0000 (UTC) (envelope-from wundram@beenic.net) Received: from [192.168.1.38] (a89-182-91-221.net-htp.de [89.182.91.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.beenic.net (Postfix) with ESMTP id 79A3CA44529 for ; Mon, 18 Feb 2008 16:00:58 +0100 (CET) From: "Heiko Wundram (Beenic)" Organization: Beenic Networks GmbH To: freebsd-stable@freebsd.org Date: Mon, 18 Feb 2008 16:01:08 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802181601.08435.wundram@beenic.net> Subject: Duplicate mails, again... 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, 18 Feb 2008 15:31:26 -0000 Would someone from the mail admins please remove the recipient at: mail.radiokom.kr.ua from the mailing list? He/She/It keeps reposting all mails sent to freebsd-stable, as other should've also noticed already, and this is getting severely annoying for my filters. -- Heiko Wundram Product & Application Development From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 16:29:05 2008 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 DC8E816A419 for ; Mon, 18 Feb 2008 16:29:04 +0000 (UTC) (envelope-from admin@su29.net) Received: from aliska.alo.ru (aliska.alo.ru [80.251.131.12]) by mx1.freebsd.org (Postfix) with ESMTP id 08BCE13C442 for ; Mon, 18 Feb 2008 16:29:04 +0000 (UTC) (envelope-from admin@su29.net) Received: from aliska (aliska.alo.ru [80.251.131.12]) by aliska.alo.ru (Postfix) with SMTP id 1E49824C9F3 for ; Mon, 18 Feb 2008 18:56:57 +0300 (MSK) Received: from ws.su29.net (ppp85-141-155-76.pppoe.mtu-net.ru [85.141.155.76]) by aliska.alo.ru (Postfix) with ESMTP id A181124CC11; Mon, 18 Feb 2008 18:56:54 +0300 (MSK) Message-ID: <47B9AAB3.4090407@su29.net> Date: Mon, 18 Feb 2008 18:56:35 +0300 From: "Alexander V. Chernikov" Organization: AlmazTelecom User-Agent: Thunderbird 2.0.0.9 (X11/20080210) MIME-Version: 1.0 To: Daniel Corrigan References: <47B90868.7000900@electron-tube.net> <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> In-Reply-To: <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: admin@su29.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Feb 2008 16:29:05 -0000 Daniel Corrigan wrote: > Since this was released to a public mailing list, I can only assume some > less than nice user will attempt this. > The only top level file system I have that can be written to by normal users > is /tmp > > Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from causing > harm? /etc/rc.d/cleartmp does /tmp clearing only at startup, after file systems are mounted. > > Dan > > On Feb 17, 2008 10:24 PM, Jim Bryant wrote: > >> One line summary: >> Too many files in a top-level UFS-2 filesystem directory will cause >> a panic on mount. >> >> Kern/Critical/High Priority/SW-Bug >> >> Which FreeBSD Release You Are Using: >> 6.3-STABLE >> >> Environment (output of "uname -a" on the problem machine): >> FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb >> 10 21:13:39 CST 2008 >> jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 >> >> Note: I just cvsupped earlier, and no changes have been put into >> cvsup that would fix this problem. >> >> Full Description: >> I was doing a reorganization of my filesystems, and since I do >> offline installs, I keep a local distfiles collection (or did until >> yesterday when this happened), and in the process, put all of the >> distfiles on their own filesystem to be mounted under >> /usr/ports/distfiles. >> >> All was fine until I rebooted. >> >> On rebooting, I got a page fault panic on mount of the new distfiles >> filesystem. >> >> i booted again, got it again, booted again this time into single-user, >> and did a fsck on the filesystem, and it only showed as being "dirty", >> but otherwise had no problems in the eyes of fsck. booted again, >> instant panic. >> >> i booted an older 6.2 CD and mounted the filesystem fine. i then put >> that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing >> everything into it, but on reboot it still paniced on mount. >> >> only a newfs was able to enable the filesystem to be mounted. >> >> today i did further research, thinking it had to do with the number of >> files in the top-level filesystem directory, and found that to be true. >> the short c program in the next section (how to repeat the problem) >> contains this. >> >> a second test shows that, after a newfs, if this done in any >> subdirectory of that filesystem, the panic is averted, and all is well. >> apparently this bug only effects top-level directories of a UFS2 >> filesystem. >> >> I have not attempted this to a non-UFS2 filesystem. >> >> IMHO, a security advisory should be released, since any user with write >> access to ANY top level directory of ANY mounted filesystem (most >> systems have /tmp as a world writable top level filesystem directory) >> can create a panic situation requiring a newfs of the said filesystem. >> A malicious user with root access can do this to /. Either way, on >> boot, or any attempt to mount said filesystem on a running system, will >> cause a panic, which of course will cause an unbootable system on reboot. >> >> How to repeat the problem: >> Compile and run the following as instructed: >> >> #include >> #include >> >> int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, >> 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", >> argv[1], i); system((const char *)buf);} return(0);} >> >> /* pass a top-level mountpoint directory name of a mounted filesystem, >> with a trailing slash to the above as argv[1], and run. >> >> This will create 10,000 zero-length files in the specified directory. >> >> umount that filesystem. >> >> perform a shitload of sync's to make sure everything outstanding is >> flushed to disk on all filesystems. >> >> mount the target filesystem (preferably from a vty or serial console to >> catch the messages when it panics, which it will as soon as the mount is >> attempted). >> */ >> >> Fix to the problem if known: >> newfs(8) >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org >> " >> > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 17:21:24 2008 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 DCCA316A421; Mon, 18 Feb 2008 17:21:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id B462913C4D3; Mon, 18 Feb 2008 17:21:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2541D46B45; Mon, 18 Feb 2008 12:21:24 -0500 (EST) Date: Mon, 18 Feb 2008 17:21:24 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jim Bryant In-Reply-To: <20080218142004.O49202@fledge.watson.org> Message-ID: <20080218171841.O49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <47B91080.9010109@electron-tube.net> <20080218142004.O49202@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 17:21:25 -0000 On Mon, 18 Feb 2008, Robert Watson wrote: > Hopefully this bug will get resolved shortly, and then we can evaluate if an > errata notice is necessary. FYI, I have been unable, thus far, to reproduce it with 150,000 entries in the root of a test file system on an 8.x kernel. I'm not set up to test 6.x and 7.x currently, and have other obligations tht will prevent me from setting up 6.x and 7.x test images for a few days. If people who can reproduce this problem could send kernel stack traces (etc) as a follow-up to the PR, that would be most helpful. Right now it's sparse on actual debugging data. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 17:27:35 2008 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 21DC816A468; Mon, 18 Feb 2008 17:27:35 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id CB98F13C46A; Mon, 18 Feb 2008 17:27:34 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7326646B66; Mon, 18 Feb 2008 12:27:34 -0500 (EST) Date: Mon, 18 Feb 2008 17:27:34 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Daniel Corrigan In-Reply-To: <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> Message-ID: <20080218172503.G49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 17:27:35 -0000 On Mon, 18 Feb 2008, Daniel Corrigan wrote: > Since this was released to a public mailing list, I can only assume some > less than nice user will attempt this. The only top level file system I have > that can be written to by normal users is /tmp > > Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from causing > harm? There are a few things that come to mind, depending on how reproduceable this is. If we think it's purely a property of the number of files in the root directory (I think this is an unlikely single cause -- it might have to do with the size of the directory, or such, which loosely corresponds to it), then you can limit the number of inodes in the file system at all. The example code in the report suggests 10,000 entries does the trick. You could create a /tmp limited to, say, 5000 entries. You can also use quotas to limit the number of inodes allocated by any one user but leave the file system unmodified, as while modifying the file system may be OK for /tmp, it's probably less OK for /home. Robert N M Watson Computer Laboratory University of Cambridge > > Dan > > On Feb 17, 2008 10:24 PM, Jim Bryant wrote: > >> One line summary: >> Too many files in a top-level UFS-2 filesystem directory will cause >> a panic on mount. >> >> Kern/Critical/High Priority/SW-Bug >> >> Which FreeBSD Release You Are Using: >> 6.3-STABLE >> >> Environment (output of "uname -a" on the problem machine): >> FreeBSD wahoo.sd67dfl.org 6.3-STABLE FreeBSD 6.3-STABLE #0: Sun Feb >> 10 21:13:39 CST 2008 >> jbryant@wahoo.sd67dfl.org:/usr/obj/usr/src/sys/WAHOO-SMP i386 >> >> Note: I just cvsupped earlier, and no changes have been put into >> cvsup that would fix this problem. >> >> Full Description: >> I was doing a reorganization of my filesystems, and since I do >> offline installs, I keep a local distfiles collection (or did until >> yesterday when this happened), and in the process, put all of the >> distfiles on their own filesystem to be mounted under >> /usr/ports/distfiles. >> >> All was fine until I rebooted. >> >> On rebooting, I got a page fault panic on mount of the new distfiles >> filesystem. >> >> i booted again, got it again, booted again this time into single-user, >> and did a fsck on the filesystem, and it only showed as being "dirty", >> but otherwise had no problems in the eyes of fsck. booted again, >> instant panic. >> >> i booted an older 6.2 CD and mounted the filesystem fine. i then put >> that filesystem the way it was by mkdir'ing a distfiles dir and mv'ing >> everything into it, but on reboot it still paniced on mount. >> >> only a newfs was able to enable the filesystem to be mounted. >> >> today i did further research, thinking it had to do with the number of >> files in the top-level filesystem directory, and found that to be true. >> the short c program in the next section (how to repeat the problem) >> contains this. >> >> a second test shows that, after a newfs, if this done in any >> subdirectory of that filesystem, the panic is averted, and all is well. >> apparently this bug only effects top-level directories of a UFS2 >> filesystem. >> >> I have not attempted this to a non-UFS2 filesystem. >> >> IMHO, a security advisory should be released, since any user with write >> access to ANY top level directory of ANY mounted filesystem (most >> systems have /tmp as a world writable top level filesystem directory) >> can create a panic situation requiring a newfs of the said filesystem. >> A malicious user with root access can do this to /. Either way, on >> boot, or any attempt to mount said filesystem on a running system, will >> cause a panic, which of course will cause an unbootable system on reboot. >> >> How to repeat the problem: >> Compile and run the following as instructed: >> >> #include >> #include >> >> int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, >> 1024); for(i = 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", >> argv[1], i); system((const char *)buf);} return(0);} >> >> /* pass a top-level mountpoint directory name of a mounted filesystem, >> with a trailing slash to the above as argv[1], and run. >> >> This will create 10,000 zero-length files in the specified directory. >> >> umount that filesystem. >> >> perform a shitload of sync's to make sure everything outstanding is >> flushed to disk on all filesystems. >> >> mount the target filesystem (preferably from a vty or serial console to >> catch the messages when it panics, which it will as soon as the mount is >> attempted). >> */ >> >> Fix to the problem if known: >> newfs(8) >> >> _______________________________________________ >> freebsd-security@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-security >> To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org >> " >> > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 18:13:33 2008 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 9E0C416A477; Mon, 18 Feb 2008 18:13:33 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6580713C45B; Mon, 18 Feb 2008 18:13:33 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id m1IHYeTD001189; Mon, 18 Feb 2008 11:34:40 -0600 (CST) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id m1IHYe95001188; Mon, 18 Feb 2008 11:34:40 -0600 (CST) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Mon, 18 Feb 2008 11:34:40 -0600 From: Scott Lambert To: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20080218173439.GA40800@sysmon.tcworks.net> Mail-Followup-To: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, FreeBSD-bugs@freebsd.org, freebsd-stable@freebsd.org References: <47B90868.7000900@electron-tube.net> <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <291ddc4f0802180714g3d326626v9d9b767a61232cec@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 18:13:33 -0000 On Mon, Feb 18, 2008 at 09:14:30AM -0600, Daniel Corrigan wrote: > Since this was released to a public mailing list, I can only assume > some less than nice user will attempt this. The only top level file > system I have that can be written to by normal users is /tmp > > Should clear_tmp_enable="YES" in /etc/rc.conf prevent this from > causing harm? Probably not. But an inode quota might, if your users can deal with having less than 10000 inodes - (what is supposed to be in the root of such file systems). It would at least make it more difficult for one rogue user to hurt you. Perhaps an /usr/local/etc/rc.d script could look for problems such as this in the stop process. Or one could simply remount the /tmp disk to /data and make a symlink from /tmp to /data/tmp. It seems like there should be several possible workarounds. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 20:35:50 2008 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 0C57F16A468; Mon, 18 Feb 2008 20:35:50 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6A87D13C468; Mon, 18 Feb 2008 20:35:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47B9EC1D.6060606@FreeBSD.org> Date: Mon, 18 Feb 2008 21:35:41 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Eugene Grosbein References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> <20080218135948.GB62360@svzserv.kemerovo.su> In-Reply-To: <20080218135948.GB62360@svzserv.kemerovo.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, des@des.no, Jim Bryant , freebsd-stable@freebsd.org, freebsd-security@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 20:35:50 -0000 Eugene Grosbein wrote: > On Mon, Feb 18, 2008 at 02:53:59PM +0100, Dag-Erling Sm??rgrav wrote: > >> Two bugs: > > [skip] > > That's all very funny, but what about a panic? > > It it true that it's possible for non-root to bring a file system > to not-mountable state? The issue appears to be more subtle than claimed, because no-one else reports being able to reproduce it yet. Kris From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 21:11:26 2008 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 9FE5A16A420 for ; Mon, 18 Feb 2008 21:11:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3D0DE13C4DB for ; Mon, 18 Feb 2008 21:11:26 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1ILB7qj009708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Feb 2008 08:11:08 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1ILB6pj055067; Tue, 19 Feb 2008 08:11:06 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1ILB6gK055066; Tue, 19 Feb 2008 08:11:06 +1100 (EST) (envelope-from peter) Date: Tue, 19 Feb 2008 08:11:06 +1100 From: Peter Jeremy To: Jim Bryant Message-ID: <20080218211106.GA55016@server.vk2pj.dyndns.org> References: <47B90868.7000900@electron-tube.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <47B90868.7000900@electron-tube.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 18 Feb 2008 21:11:26 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [CC list trimmed] On Sun, Feb 17, 2008 at 10:24:08PM -0600, Jim Bryant wrote: >How to repeat the problem: > Compile and run the following as instructed: > >#include >#include > >int main(int argc, char **argv) { int i; char buf[1024]; bzero(buf, 1024);= =20 >for(i =3D 0; i < 10000; i++) { sprintf(buf, "touch %s%05d\n", argv[1], i);= =20 >system((const char *)buf);} return(0);} > >/* pass a top-level mountpoint directory name of a mounted filesystem, wit= h=20 >a trailing slash to the above as argv[1], and run. > >This will create 10,000 zero-length files in the specified directory. > >umount that filesystem. > >perform a shitload of sync's to make sure everything outstanding is flushe= d=20 >to disk on all filesystems. > >mount the target filesystem (preferably from a vty or serial console to=20 >catch the messages when it panics, which it will as soon as the mount is= =20 >attempted). >*/ FreeBSD pjfbsd6.alcatel.com.au 6.3-STABLE FreeBSD 6.3-STABLE #4: Wed Jan 23= 08:21:27 EST 2008 root@pjfbsd6.alcatel.com.au:/var/obj/usr/src/sys/pjf= bsd6 i386 I have been unable to reproduce the problem as described with or without softupdates, even when I run the filesystem out of inodes. I have also tried filling '/'=C3=A4 and rebooting to no avail. That said, I did run into a bug where, for some time after deleting the files from a soft-updates partition, 'df' would report that the inodes were freed but attempting to create a new file would fail with ENOSPC. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHufRq/opHv/APuIcRAnMXAJwMiw8ELN36bz7MTRWac7vOyGubngCgwmfE Wcwr3bQlf9N8adqPNsZ8gh8= =Rd2N -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 22:04:19 2008 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 F0FEF16A469 for ; Mon, 18 Feb 2008 22:04:19 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id A124213C500 for ; Mon, 18 Feb 2008 22:04:19 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from crater.wildlava.net (crater.wildlava.net [67.40.138.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id C38E48F425 for ; Mon, 18 Feb 2008 15:04:18 -0700 (MST) Message-ID: <47BA00E1.5000605@skyrush.com> Date: Mon, 18 Feb 2008 15:04:17 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Revisiting jerky/freezing mouse issue in 7.0 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, 18 Feb 2008 22:04:20 -0000 I spent some time looking again at a trace I posted last month showing mouse "jerkiness/freezing" under load (note that I see it all of the time under light load too, but it is harder to reproduce on demand). Here's the trace: http://www.skyrush.com/downloads/ktr_ule_4.out The large stretches of yellow in the Xorg process are what trouble me. Clearly, Xorg is yielding processor time mostly to, in this case, xtrs, which is getting a whole lot of time. If you look at the fairly regular mouse events, you'll notice that moused runs for a short time on each mouse even from psm0 and then sleeps. This makes sense, and it appears moused is acting correctly. But many of these mouse events are seemingly ignored by Xorg, which spends most of its time yielding (yellow) and not getting "woken up" by the events to simply process them. I've noticed, also, that Xorg can "get behind" easily and spend its time catching up on event processing for a while after I stop using the mouse. It just doesn't seem to be getting an appropriate amount of CPU time, or at least it yields too long between runs, to make interactivity smooth. These yields, I believe, are the freezes I see. Here's a question: does Xorg "respond" to mouse events, or does it just wake up every now and then and check? Note that even when Xorg runs, it only runs for a very short time. If the ULE scheduluer is being fair, I would think this might give Xorg *more* of a share of the CPU to use to service these events, since it is running a lot less than xtrs. One interesting point is at timestamp 1478223777518. It looks like Xorg *starts* to yield when moused runs. Here's the line: 1478223777518 sched_add: 0xa7be1660(Xorg) prio 160 by 0xa5eb7aa0(moused) Does this mean that moused *caused* Xorg to yield, or am I reading this incorrectly)? The yield then lasts through a series of mouse moves. A quick look through the graph shows that this happens quite a bit, which seems like the reverse of what we'd like. This issue (especially since it does not even require continuous heavy CPU use to see) is a constant distraction while using the system, and again I want to volunteer my time to help track it down. I am not sure how to further delve into it, so if there is some additional data I can gather, please let me know, and I'll gladly do it. Thanks, Joe From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 22:17:30 2008 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 D2CEA16A47A for ; Mon, 18 Feb 2008 22:17:30 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 767B313C458 for ; Mon, 18 Feb 2008 22:17:30 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 287F1405493; Mon, 18 Feb 2008 23:17:28 +0100 (CET) Message-ID: <47BA03E9.8020106@bsdforen.de> Date: Mon, 18 Feb 2008 23:17:13 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20080205) MIME-Version: 1.0 To: Joe Peterson References: <47BA00E1.5000605@skyrush.com> In-Reply-To: <47BA00E1.5000605@skyrush.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Revisiting jerky/freezing mouse issue in 7.0 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, 18 Feb 2008 22:17:30 -0000 Joe Peterson wrote: > ... > > This issue (especially since it does not even require continuous heavy > CPU use to see) is a constant distraction while using the system, and > again I want to volunteer my time to help track it down. I am not sure > how to further delve into it, so if there is some additional data I can > gather, please let me know, and I'll gladly do it. > > Thanks, Joe This issue is very strong on my notebook. X is always frozen and only ever catches up with events while the mouse is moving. From owner-freebsd-stable@FreeBSD.ORG Mon Feb 18 23:10:39 2008 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 4234716A41B for ; Mon, 18 Feb 2008 23:10:39 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0186C13C467 for ; Mon, 18 Feb 2008 23:10:38 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m1INAaYN041139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Feb 2008 15:10:38 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <47BA106C.60008@errno.com> Date: Mon, 18 Feb 2008 15:10:36 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: huub References: <1203328474.3957.23.camel@localhost> In-Reply-To: <1203328474.3957.23.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-stable@freebsd.org Subject: Re: interrupt storms with AR5414 on 6.3 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: Mon, 18 Feb 2008 23:10:39 -0000 huub wrote: > I have a problem running the Atheros AR5414 wireless mini-pci-card > (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a > Soekris 4521. > > I get lots of messages: > "interrupt storm detected on "irq10:"; throttling interrupt source" > and > "ath0: device timeout" > > And after sometime the interface stops functioning. > > Anybody any suggestion? > Thanks, > Huub > > > Information on system follows: > > > # dmesg: > .... > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413) > ..... > ath0: mem 0xa0000000-0xa000ffff irq 10 at device 16.0 on > pci0 > ath0: Ethernet address: 00:80:48:54:c0:92 > ath0: mac 10.5 phy 6.1 radio 6.3 > > # ifconfig > ath0: flags=8843 mtu 1500 > inet6 fe80::280:48ff:fe54:c092%ath0 prefixlen 64 scopeid 0x1 > inet 172.16.0.214 netmask 0xfffffffc broadcast 172.16.0.215 > ether 00:80:48:54:c0:92 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) > status: associated > ssid ap-omni.renv0.wleiden.net channel 1 bssid 00:02:6f:06:d6:14 > authmode OPEN privacy OFF txpowmax 46 protmode CTS bintval 100 > > # wicontrol -i ath0 > NIC serial number: [ ] > Station name: [ CNodeHuub.wLeiden.NET ] > SSID for IBSS creation: [ ap-omni.renv0.wleiden.net ] > Current netname (SSID): [ ap-omni.renv0.wleiden.net ] > Desired netname (SSID): [ ap-omni.renv0.wleiden.net ] > Current BSSID: [ 00:02:6f:06:d6:14 ] > Channel list: [ ffe 0 1110 1111 1 0 0 0 0 2220 > 22 ] > IBSS channel: [ 1 ] > Current channel: [ 1 ] > Comms quality/signal/noise: [ 0 24 0 ] > Promiscuous mode: [ Off ] > Intersil-Prism2 based card: [ 1 ] > Port type (1=BSS, 3=ad-hoc): [ 1 ] > MAC address: [ 00:80:48:54:c0:92 ] > TX rate (selection): [ 0 ] > TX rate (actual speed): [ 2 ] > RTS/CTS handshake threshold: [ 2346 ] > Create IBSS: [ Off ] > Access point density: [ 1 ] > Power Mgmt (1=on, 0=off): [ 0 ] > Max sleep time: [ 100 ] > WEP encryption: [ Off ] > TX encryption key: [ 0 ] > Encryption keys: [ ][ ][ ][ ] > > Some people have reported problems like this when powerd is in use. Sam From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 02:01:44 2008 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 1E2DB16A418 for ; Tue, 19 Feb 2008 02:01:44 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.242]) by mx1.freebsd.org (Postfix) with ESMTP id CEF3013C465 for ; Tue, 19 Feb 2008 02:01:43 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by ag-out-0708.google.com with SMTP id 5so2989515agb.7 for ; Mon, 18 Feb 2008 18:01:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=LDOCXQnUVv9TPPuAOG+kRE2uARyM7BS0dSu+BU3+kvY=; b=bKsKPeSEPPYwJsfjy5Df4wPwj0HEZakKNdC2I8mD/ppQZkDXgUjYfxvZsS5j2kzgXhW2/4q6416UEG7zYuu47Opa04oEB7wW3GyvGJKbVaev2p3ACP/r9qjJ75G3Ww1/lUKojjZ66GYBKIhbxCpr7jpPV1BWhrUUwwY82wEcHN8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=vQdWNSdN6kMh5cNfzLm4zD2M31jF2GoW6GhsqfWO/C9f5oyge8NBhDZNSKCGFZAelGCILlQxI3bEtAMjJwP/r52bh0xStsz0uo1DIbZqlr2Rw8HWqud8WTHfxrg79IImKyqi7kZ5gJgJnTmyhm9x0lUIGYwe0I0G7iga87BIxD0= Received: by 10.100.210.9 with SMTP id i9mr12949610ang.40.1203386502590; Mon, 18 Feb 2008 18:01:42 -0800 (PST) Received: from ?10.0.3.231? ( [70.111.176.151]) by mx.google.com with ESMTPS id d29sm12618930and.28.2008.02.18.18.01.39 (version=SSLv3 cipher=RC4-MD5); Mon, 18 Feb 2008 18:01:41 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: Robert Watson In-Reply-To: <20080218171841.O49202@fledge.watson.org> References: <47B90868.7000900@electron-tube.net> <47B91080.9010109@electron-tube.net> <20080218142004.O49202@fledge.watson.org> <20080218171841.O49202@fledge.watson.org> Content-Type: text/plain; charset=utf-8 Date: Mon, 18 Feb 2008 21:01:13 -0500 Message-Id: <1203386473.19985.14.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-security@freebsd.org, Jim Bryant , freebsd-stable@freebsd.org, FreeBSD-bugs@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 19 Feb 2008 02:01:44 -0000 On Mon, 2008-02-18 at 17:21 +0000, Robert Watson wrote: > On Mon, 18 Feb 2008, Robert Watson wrote: > > > Hopefully this bug will get resolved shortly, and then we can evaluate if an > > errata notice is necessary. > > FYI, I have been unable, thus far, to reproduce it with 150,000 entries in the > root of a test file system on an 8.x kernel. I'm not set up to test 6.x and > 7.x currently, and have other obligations tht will prevent me from setting up > 6.x and 7.x test images for a few days. FWIW: I can not reproduce this on the 7.0-RC2: twinhead# umount /usr/ports/distfiles twinhead# sync twinhead# sync twinhead# sync twinhead# sync twinhead# mount /usr/ports/distfiles twinhead# df -k Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0s1a 8119416 4714312 2755552 63% / devfs 1 1 0 100% /dev /dev/da0s3d 7054514 1032194 5457960 16% /home /dev/stripe/shared 103288206 66041510 28983640 69% /SHARED /dev/stripe/S0 378425950 116115180 232036694 33% /STORAGE procfs 4 4 0 100% /proc /dev/ad4s2 47298314 4314412 39200038 10% /usr/ports/distfiles twinhead# cd /usr/ports/distfiles twinhead# ls | egrep "^[0-9]" | wc -l 10000 twinhead# ls | wc -l 10673 twinhead# uname -a FreeBSD twinhead.rabbitslawn.verizon.net 7.0-RC2 FreeBSD 7.0-RC2 #0: Sat Feb 16 08:44:12 EST 2008 root@twinhead.rabbitslawn.verizon.net:/usr/obj/usr/src/sys/TWINHEAD i386 If this makes any difference, this is SMP machine running SMP kernel. > > If people who can reproduce this problem could send kernel stack traces (etc) > as a follow-up to the PR, that would be most helpful. Right now it's sparse > on actual debugging data. > > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > 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" -- Alexandre "Sunny" Kovalenko (ОлексаМЎр КПвалеМкП) From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 02:06:05 2008 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 8A2AC16A468 for ; Tue, 19 Feb 2008 02:06:05 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 7388C13C455 for ; Tue, 19 Feb 2008 02:06:05 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 286118C08D; Mon, 18 Feb 2008 20:06:05 -0600 (CST) Date: Mon, 18 Feb 2008 20:06:05 -0600 To: freebsd-stable@freebsd.org Message-ID: <20080219020605.GB23674@soaustin.net> References: <20080216231335.GA20538@spinnaker.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080216231335.GA20538@spinnaker.com> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) Subject: Re: 7.0-RC2 package glitch 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, 19 Feb 2008 02:06:05 -0000 On Sat, Feb 16, 2008 at 03:13:35PM -0800, Wayne Chapeskie wrote: > The RC2 sysinstall misses six packages, which are included on disc 1, > which RC1 did install: > > imake-1.0.2_4,1 > makedepend-1.0.1,1 > gccmakedep-1.0.2 > xorg-cf-files-1.0.2_2 > xorg-nestserver-1.4,1 > xorg-vfbserver-1.4,1 > > Between RC1 and RC2, sysinstall was cleaned up to install X by using > the single top level xorg meta-package rather than the old method > of specifying a number of different meta-packages. Unfortunately, > the xorg-7.3_1 package in 7.0-release does not pull in the above six > packages. There are two differences. imake (which brings in makedepend, gccmakedep, and xorg-cf-files) is only a BUILD_DEPENDS of the xorg metaport. If you're simply installing from packages, you won't need them. If you want to rebuild them at any future time, you will. vfbserver and nestserver are depended on by 4 and zero ports respectively, none of which are in the xorg metaport. They'll only be brought in if you need one of them. So, AFAIAC, this is "working as designed". mcl From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 02:38:40 2008 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 A819516A421; Tue, 19 Feb 2008 02:38:40 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 88C0D13C469; Tue, 19 Feb 2008 02:38:40 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.13.7) with ESMTP id m1J2QHgb093024; Mon, 18 Feb 2008 18:26:17 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m1J2QHNI093023; Mon, 18 Feb 2008 18:26:17 -0800 (PST) Date: Mon, 18 Feb 2008 18:26:17 -0800 (PST) From: Matthew Dillon Message-Id: <200802190226.m1J2QHNI093023@apollo.backplane.com> To: Jim Bryant References: <47B90868.7000900@electron-tube.net> <86odae5rgr.fsf@ds4.des.no> <863arq5q14.fsf@ds4.des.no> <20080218135948.GB62360@svzserv.kemerovo.su> <47B9EC1D.6060606@FreeBSD.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) 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, 19 Feb 2008 02:38:40 -0000 Jim's original report seemed to indicate that the filesystem paniced on mount even after repeated fsck's. That implies that Jim has a filesystem image that panics on mount. Maybe Jim can make that image available and a few people can see if downloading and mounting it reproduces the problem. It would narrow things down anyhow. Also, I didn't see a system backtrace anywhere. If it paniced, where did it panic? The first thing that came to my mind was the dirhash code, but simply mounting a filesystem doesn't scan the mount point directory at all, except possibly for '.' or '..'... I don't think it even does that. All it does is resolve the root inode of the filesystem. The code path for mounting a UFS or UFS2 filesystem is very short. -Matt From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 08:10:23 2008 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 59F0A16A418 for ; Tue, 19 Feb 2008 08:10:23 +0000 (UTC) (envelope-from nicki@astcape.co.za) Received: from ns0.astcape.co.za (ns0.astcape.co.za [196.41.11.91]) by mx1.freebsd.org (Postfix) with ESMTP id DE0AA13C448 for ; Tue, 19 Feb 2008 08:10:22 +0000 (UTC) (envelope-from nicki@astcape.co.za) Received: from localhost (localhost.local [127.0.0.1]) by ns0.astcape.co.za (Postfix) with ESMTP id 46BC0D4C7B for ; Tue, 19 Feb 2008 09:54:57 +0200 (SAST) X-Virus-Scanned: amavisd-new at astcape.co.za Received: from ns0.astcape.co.za ([10.4.1.21]) by localhost (ns0.astcape.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Zbac7sszuPu for ; Tue, 19 Feb 2008 09:54:52 +0200 (SAST) Received: from CC10673 (unknown [196.211.10.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ns0.astcape.co.za (Postfix) with ESMTP id 416F5D4C75 for ; Tue, 19 Feb 2008 09:54:52 +0200 (SAST) Message-ID: <003301c872cc$b5799c80$e501a8c0@CC10673> From: "Nicki de Wet" To: Date: Tue, 19 Feb 2008 09:54:50 +0200 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.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: local periodic executed twice 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, 19 Feb 2008 08:10:23 -0000 I found a solution for the local periodic scripts that is executed twice. Various pages on the net suggested putting local_periodic="/usr/local/etc/periodic" in /etc/rc.conf. This did not work, I found the solution to be to put it in /etc/periodic.conf.local. Regards, Nicki From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 10:01:44 2008 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 DFD9E16A419 for ; Tue, 19 Feb 2008 10:01:44 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml11.kpnxchange.com (hpsmtp-eml11.kpnxchange.com [213.75.38.111]) by mx1.freebsd.org (Postfix) with ESMTP id 67DDB13C43E for ; Tue, 19 Feb 2008 10:01:44 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml102.kpnxchange.com ([213.75.84.102]) by hpsmtp-eml11.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Feb 2008 10:49:34 +0100 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml102.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Feb 2008 10:49:33 +0100 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m1J9nRHJ029471; Tue, 19 Feb 2008 10:49:28 +0100 (CET) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1JRP7M-0001Jd-HV; Tue, 19 Feb 2008 10:50:28 +0100 Date: Tue, 19 Feb 2008 10:50:28 +0100 From: Willy Offermans To: Nicki de Wet Message-ID: <20080219095028.GA4219@wiz.vpn.offrom.nl> References: <003301c872cc$b5799c80$e501a8c0@CC10673> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003301c872cc$b5799c80$e501a8c0@CC10673> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92/5885/Tue Feb 19 07:57:27 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on koko.offrom.nl X-OriginalArrivalTime: 19 Feb 2008 09:49:33.0446 (UTC) FILETIME=[BAEC0260:01C872DC] Cc: freebsd-stable@FreeBSD.ORG Subject: Re: local periodic executed twice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2008 10:01:45 -0000 Hello Nicki and FreeBSD friends, On Tue, Feb 19, 2008 at 09:54:50AM +0200, Nicki de Wet wrote: > I found a solution for the local periodic scripts that is executed twice. > Various pages on the net suggested putting > local_periodic="/usr/local/etc/periodic" in /etc/rc.conf. > > This did not work, I found the solution to be to put it in > /etc/periodic.conf.local. > > Regards, > Nicki > Sorry I missed the e-mail thread completely, but I want to add the following: koko ~>cat /etc/periodic.conf # added by mergebase.sh local_periodic="/usr/local/etc/periodic" So there is a file in /etc, called periodic.conf with the statement: local_periodic="/usr/local/etc/periodic" So why do you use /etc/periodic.conf.local? Is periodic.conf.local not touched by a possible FreeBSD upgrade? Is local_periodic="/usr/local/etc/periodic" not the default? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 10:25:56 2008 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 E982116A478 for ; Tue, 19 Feb 2008 10:25:56 +0000 (UTC) (envelope-from nicki@astcape.co.za) Received: from ns0.astcape.co.za (ns0.astcape.co.za [196.41.11.91]) by mx1.freebsd.org (Postfix) with ESMTP id 797BD13C457 for ; Tue, 19 Feb 2008 10:25:56 +0000 (UTC) (envelope-from nicki@astcape.co.za) Received: from localhost (localhost.local [127.0.0.1]) by ns0.astcape.co.za (Postfix) with ESMTP id 152FBD4C46; Tue, 19 Feb 2008 12:26:00 +0200 (SAST) X-Virus-Scanned: amavisd-new at astcape.co.za Received: from ns0.astcape.co.za ([10.4.1.21]) by localhost (ns0.astcape.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1RUzAZtjryb; Tue, 19 Feb 2008 12:25:49 +0200 (SAST) Received: from CC10673 (unknown [196.211.10.10]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by ns0.astcape.co.za (Postfix) with ESMTP id B5BE4D4C35; Tue, 19 Feb 2008 12:25:48 +0200 (SAST) Message-ID: <00fd01c872e1$cb818410$e501a8c0@CC10673> From: "Nicki de Wet" To: References: <003301c872cc$b5799c80$e501a8c0@CC10673> <20080219095028.GA4219@wiz.vpn.offrom.nl> Date: Tue, 19 Feb 2008 12:25:47 +0200 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.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: local periodic executed twice 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, 19 Feb 2008 10:25:57 -0000 Willy, You are right, I can actually put it in /etc/periodic.conf. The periodic scripts all contain the following line: . /etc/defaults/periodic.conf This file contains the following: # periodic script dirs local_periodic="/usr/local/etc/periodic /usr/X11R6/etc/periodic" On the system where I had the problem, /usr/X11R6 points to /usr/local, so the scripts get executed twice. By overriding it with local_periodic="/usr/local/etc/periodic" the 2nd call is removed. Regards, Nicki ----- Original Message ----- From: "Willy Offermans" To: "Nicki de Wet" Cc: Sent: Tuesday, February 19, 2008 11:50 AM Subject: Re: local periodic executed twice > Hello Nicki and FreeBSD friends, > > On Tue, Feb 19, 2008 at 09:54:50AM +0200, Nicki de Wet wrote: >> I found a solution for the local periodic scripts that is executed twice. >> Various pages on the net suggested putting >> local_periodic="/usr/local/etc/periodic" in /etc/rc.conf. >> >> This did not work, I found the solution to be to put it in >> /etc/periodic.conf.local. >> >> Regards, >> Nicki >> > > Sorry I missed the e-mail thread completely, but I want to add the > following: > > koko ~>cat /etc/periodic.conf > # added by mergebase.sh > local_periodic="/usr/local/etc/periodic" > > So there is a file in /etc, called periodic.conf with the statement: > local_periodic="/usr/local/etc/periodic" > > So why do you use /etc/periodic.conf.local? Is periodic.conf.local not > touched by a possible FreeBSD upgrade? Is > local_periodic="/usr/local/etc/periodic" not the default? > > > -- > Met vriendelijke groeten, > With kind regards, > Mit freundlichen Gruessen, > De jrus wah, > > Willy > > ************************************* > W.K. Offermans > Home: +31 45 544 49 44 > Mobile: +31 653 27 16 23 > e-mail: Willy@Offermans.Rompen.nl > > Powered by .... > > (__) > \\\'',) > \/ \ ^ > .\._/_) > > www.FreeBSD.org > > From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 11:04:14 2008 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 4FDDE16A46B for ; Tue, 19 Feb 2008 11:04:14 +0000 (UTC) (envelope-from bounce-380703-10097911@m18.xoopa.net) Received: from m18.xoopa.net (m18.xoopa.net [70.47.43.38]) by mx1.freebsd.org (Postfix) with SMTP id D800813C4E8 for ; Tue, 19 Feb 2008 11:04:13 +0000 (UTC) (envelope-from bounce-380703-10097911@m18.xoopa.net) From: "Brand Alley" To: FREEBSD-STABLE@freebsd.org Date: Mon, 18 Feb 2008 21:32:34 -0500 MIME-Version: 1.0 Message-ID: X-time: 10097911 X-member: FREEBSD-STABLE@freebsd.org X-unsub: leave-380703-10097911.8106bbb2c4f1fd8cdda2fc111e50eb96@m18.xoopa.net Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Free Membership - 70% off leading designer clothes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: laura@swearch.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2008 11:04:14 -0000 Hey, Claim your FREE membership of BrandAlley, the hottest fashion site that offers it's members up to 70% off leading designer clothes and accessories! Click Here to join now: http://e.swearch.com/t/380703/10097911/230/0/?u=3DaHR0cDovL3d3dy5waW5rc3BpZ= GVyLmNvLnVrL2JyYW5kL2FsbGV5Lmh0bQ%3d%3d&x=3Dca7df625 Kind Regards, Jessica Newman -------------------------- You have received this email update as you are a member of an ISM Group Web= site. To unsubscribe click here: http://e.swearch.com/t/380703/10097911/63/0/?u= =3DaHR0cDovL2Uuc3dlYXJjaC5jb20vdT9pZD0xMDA5NzkxMS44MTA2YmJiMmM0ZjFmZDhjZGRhM= mZjMTExZTUwZWI5NiZuPVQmbD1zdy0yJm89MzgwNzAz&x=3Df2bb0000 From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 12:07:42 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF84716A418 for ; Tue, 19 Feb 2008 12:07:42 +0000 (UTC) (envelope-from prcontad@jackson.nswebhost.com) Received: from jackson.nswebhost.com (jackson.nswebhost.com [66.246.252.19]) by mx1.freebsd.org (Postfix) with ESMTP id 877EF13C469 for ; Tue, 19 Feb 2008 12:07:42 +0000 (UTC) (envelope-from prcontad@jackson.nswebhost.com) Received: from prcontad by jackson.nswebhost.com with local (Exim 4.68) (envelope-from ) id 1JRRG9-0001Zb-I1 for stable@freebsd.org; Tue, 19 Feb 2008 06:07:41 -0600 To: stable@freebsd.org X-PHP-Script: prcontadores.com/badung.php for 193.93.99.138 From: MARY MOHAMED MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: Date: Tue, 19 Feb 2008 06:07:41 -0600 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - jackson.nswebhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [33692 32592] / [47 12] X-AntiAbuse: Sender Address Domain - jackson.nswebhost.com Cc: Subject: MY HEART DESIRE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mohamedmary5@hotmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2008 12:07:42 -0000 Good day and God bless, Greetings to you in the name of God Almighty. I am former Mrs. Memunat Mohamed Galal, now I am Mrs. Mary Mohamed Galal a widow to Late Dr.Mohamed Galal. I am an old woman; suffering from cancer. From all indications, my condition is really deteriorating and is quite obvious that I may not live long, because the cancer stage has gotten to a very severe stage. My late husband died in an air crash on the 31st October 1999 in an Egyptian airline Boeing 990 with other passengers on board. You can confirm this fact from the website which was aired by the BBC WORLDNEWS:(http://news.bbc.co.uk/1/hi/world/americas/502503.stm) and my only daughter died in BOMB ATTACK LONDON. My late husband was very wealthy and after his death, I inherited all his business and wealth. My personal physician told me that I may not live for so long and I am so scared about this. So, I now decided to divide part of this wealth, by contributing to the well being of less privileged people and handicapped in the society of world America, Canada,Africa,Europe and Asian Countries. This mission, who will no doubt be tasking had made me to recently relocate to Africa where I live presently. I selected you for this Purpose and prayed over it, I am willing to donate the sum of $7,300,000.00 Million US Dollars to you for the development of the well being of handicapped in the society and also as aids for the less privileged around your country,and i have map out $1,700.000.00 for your own personal use to help me for this work. Please note that, this fund is lying in a Security Bank.Therefore immediate application for the transfer of the money in your name or your home. Please, do not reply me if you have the intention of using this fund for personal use, than enhancement of the comfort of the Handicapped. Lastly, I want you/your home to be praying for me as regards my entire life and my health because I have come to find out since my spiritual birth lately that wealth acquisition without God one's life is vanity upon vanity. I await your reply. MRS MARY MOHAMED From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 14:10:08 2008 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 82BAB16A468 for ; Tue, 19 Feb 2008 14:10:08 +0000 (UTC) (envelope-from huub@wirelessleiden.nl) Received: from smtp-vbr16.xs4all.nl (smtp.ipv6.xs4all.nl [IPv6:2001:888:0:15::25]) by mx1.freebsd.org (Postfix) with ESMTP id 1ADD813C442 for ; Tue, 19 Feb 2008 14:10:07 +0000 (UTC) (envelope-from huub@wirelessleiden.nl) Received: from [192.168.1.197] (a213-84-65-193.adsl.xs4all.nl [213.84.65.193]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id m1JEA1bM014918 for ; Tue, 19 Feb 2008 15:10:06 +0100 (CET) (envelope-from huub@wirelessleiden.nl) From: huub To: freebsd-stable@freebsd.org In-Reply-To: <47BA106C.60008@errno.com> References: <1203328474.3957.23.camel@localhost> <47BA106C.60008@errno.com> Content-Type: text/plain Date: Tue, 19 Feb 2008 15:10:01 +0100 Message-Id: <1203430201.6063.46.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2-2.1mdv2007.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: interrupt storms with AR5414 on 6.3 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: Tue, 19 Feb 2008 14:10:08 -0000 On Mon, 2008-02-18 at 15:10 -0800, Sam Leffler wrote: > huub wrote: > > I have a problem running the Atheros AR5414 wireless mini-pci-card > > (Compex model WLM54AGP23) with FreeBSD 6.3-RELEASE (GENERIC i 386) on a > > Soekris 4521. > > > > I get lots of messages: > > "interrupt storm detected on "irq10:"; throttling interrupt source" > > and > > "ath0: device timeout" > > > > And after sometime the interface stops functioning. ....... > > Some people have reported problems like this when powerd is in use. > > Sam > > I am not running powerd. I have now replaced the Compex WLM54AGP23 with the AR5414 chip with a Winstron CM9 card (AR5212 chip). This card also gives problems although messages are different and less frequent, see below. Feb 18 15:07:29 kernel: ath0: mem 0xa0000000-0xa000ffff irq 10 at device 16.0 on pci0 Feb 18 15:07:29 kernel: ath0: Ethernet address: 00:0b:6b:81:a8:80 Feb 18 15:07:29 kernel: ath0: mac 5.9 phy 4.3 radio 3.6 Feb 18 15:07:36 kernel: ath0: link state changed to UP Feb 18 15:59:21 kernel: ath0: link state changed to DOWN Feb 18 16:01:23 kernel: ath0: link state changed to UP Feb 18 17:58:11 kernel: ath0: device timeout Feb 18 18:16:44 kernel: ath0: device timeout Feb 18 20:05:00 kernel: ath0: device timeout Feb 18 22:22:19 kernel: ath0: device timeout Feb 18 23:20:49 kernel: ath0: device timeout Feb 19 00:03:44 kernel: ath0: device timeout Feb 19 00:30:11 kernel: ath0: link state changed to DOWN Feb 19 00:30:21 kernel: ath0: link state changed to UP Feb 19 00:30:36 kernel: ath0: link state changed to DOWN Feb 19 00:30:46 kernel: ath0: link state changed to UP Feb 19 00:31:11 kernel: ath0: link state changed to DOWN Feb 19 00:31:21 kernel: ath0: link state changed to UP Feb 19 00:31:25 kernel: ath0: link state changed to DOWN Feb 19 00:31:35 kernel: ath0: link state changed to UP Feb 19 00:40:43 kernel: ath0: link state changed to DOWN Feb 19 00:40:53 kernel: ath0: link state changed to UP Feb 19 02:38:59 kernel: ath0: device timeout Feb 19 03:42:20 kernel: ath0: device timeout Feb 19 05:03:34 kernel: ath0: device timeout Feb 19 05:34:56 kernel: ath0: device timeout Feb 19 05:37:54 kernel: ath0: device timeout Feb 19 06:39:43 kernel: ath0: device timeout Feb 19 07:14:58 kernel: ath0: device timeout Feb 19 07:29:57 kernel: ath0: link state changed to DOWN Feb 19 07:30:07 kernel: ath0: link state changed to UP Feb 19 07:31:25 kernel: ath0: link state changed to DOWN Feb 19 07:31:35 kernel: ath0: link state changed to UP Feb 19 07:31:38 kernel: ath0: link state changed to DOWN Feb 19 07:31:48 kernel: ath0: link state changed to UP Feb 19 07:31:52 kernel: ath0: link state changed to DOWN Feb 19 07:32:44 kernel: ath0: link state changed to UP Feb 19 07:54:11 kernel: ath0: device timeout etc. From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 18:00:30 2008 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 C163016A501 for ; Tue, 19 Feb 2008 18:00:30 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from anduin.net (anduin.net [213.225.74.230]) by mx1.freebsd.org (Postfix) with ESMTP id 7D42413C455 for ; Tue, 19 Feb 2008 18:00:30 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from ranger.anduin.net ([212.62.248.147] helo=[192.168.2.10]) by anduin.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JRWlX-00067B-A6; Tue, 19 Feb 2008 19:00:27 +0100 Message-Id: <78796912-6D98-4433-A5C9-622854C7DFB2@anduin.net> From: =?ISO-8859-1?Q?Eirik_=D8verby?= To: FreeBSD Stable In-Reply-To: <200802131851.15014.doconnor@gsoft.com.au> Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 19 Feb 2008 19:00:26 +0100 References: <79029E40-6E43-4482-8E39-D1DE49C8C53A@anduin.net> <200802122311.43247.doconnor@gsoft.com.au> <5B010AC7-C292-45E6-A109-20E39B370604@anduin.net> <200802131851.15014.doconnor@gsoft.com.au> X-Mailer: Apple Mail (2.919.2) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: UFS snapshot weirdness 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, 19 Feb 2008 18:00:31 -0000 On Feb 13, 2008, at 9:21 AM, Daniel O'Connor wrote: > On Wed, 13 Feb 2008, Eirik =D8verby wrote: >> Yes, I am absolutely sure of this. >> >> I considered using the snapshot tool, however I need to reduce >> dependencies to an absolute minimum (as one target environment is >> very strict on allowing additional software installs).. >> >> I use the snapshots to get a consistent file-backup with history. >> This one puzzles me to no end. > > Hmm, that is very odd.. > Maybe the FS is stuffed somehow :( I read somewhere else about NFS issues on 7-RC* where snapshots have =20 been used. In particular - and this is something I'm seeing too - =20 changing the exports file or reloading mountd gives the following in =20 messages log: Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /tmp: =20 Invalid argument Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /usr: =20 Cross-device link Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /var: =20 Cross-device link Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /export/=20= home: Cross-device link Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /opt: =20 Cross-device link Can this be related? I'm starting to worry here - what will be the =20 long-term consequences if snapshots are stuck around in this =20 "invisible" state? /Eirik > > > --=20 > 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 Feb 19 19:44:59 2008 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 6864716A46D for ; Tue, 19 Feb 2008 19:44:59 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id 40D3A13C4D1 for ; Tue, 19 Feb 2008 19:44:59 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from crater.wildlava.net (crater.wildlava.net [67.40.138.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id 24A278F428 for ; Tue, 19 Feb 2008 12:44:58 -0700 (MST) Message-ID: <47BB31B8.1070503@skyrush.com> Date: Tue, 19 Feb 2008 12:44:56 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Multiple key presses are hindered when repeat turned off 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, 19 Feb 2008 19:44:59 -0000 I have verified this on two machines, but it would be helpful if others out there can reproduce it too. Also, I do not know if it is Xorg or the FreeBSD keyboard drivers, since I see no way to reproduce on the console (i.e. turn off repeat). In an xterm, type: "xset r off". Then try some multiple-key combinations (i.e. keep holding first key(s) when you type the next one): po (o does not appear) lk (k does not appear) grep (e does not appear) When you release the keys, the press events will show up. Keyboards in general have limited multiple-key (rollover) capabilities, but using "xset r off" reduces these to the point that you will often mistype things, and it seems unique to FreeBSD. I am using 7.0-RC2 at the moment. Thanks, Joe From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 22:39:51 2008 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 93D2C16A419 for ; Tue, 19 Feb 2008 22:39:51 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) Received: from ironport2-out.pppoe.ca (ironport2-out.pppoe.ca [206.248.154.182]) by mx1.freebsd.org (Postfix) with ESMTP id B120813C465 for ; Tue, 19 Feb 2008 22:39:50 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAEziukdMCqa7/2dsb2JhbACCQDGIAYcxnR8E X-IronPort-AV: E=Sophos;i="4.25,378,1199682000"; d="scan'208,217";a="14725164" Received: from mail.pppoe.ca ([65.39.192.132]) by ironport2-out.pppoe.ca with ESMTP; 19 Feb 2008 17:10:23 -0500 Received: from kevin ([76.10.166.187]) by mail.pppoe.ca (Internet Mail Server v1.0) with ASMTP id ZYD19622 for ; Tue, 19 Feb 2008 17:10:22 -0500 From: "Kevin K" To: Date: Tue, 19 Feb 2008 17:10:17 -0500 Message-ID: <002e01c87344$371766b0$a5463410$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AchzRDN1NALL2j54QPKLdccLOnQMMw== Content-Language: en-us x-cr-hashedpuzzle: AsyI BKr1 BagD CDjn CMBf Ddmb Dq9U EKAz Epzv GbNa G1GQ Ibmv ItM3 J9HQ KYez Kvtz; 1; ZgByAGUAZQBiAHMAZAAtAHMAdABhAGIAbABlAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {6F996ECE-B162-4CC1-A874-8746F1C2D9CA}; awBrAHUAdAB6AGsAbwBAAHQAZQBrAHMAYQB2AHYAeQAuAGMAbwBtAA==; Tue, 19 Feb 2008 22:10:13 GMT; RAB1AGEAbAAgAEMAbwByAGUAIABYAGUAbwBuACAALwAgACAAaQAzADgANgAgAGkAbgBzAHQAYQBsAGwAIAB3AC8AIABtAG8AcgBlACAAdABoAGEAbgAgADQAZwBiACAAbwBmACAAUgBBAE0A x-cr-puzzleid: {6F996ECE-B162-4CC1-A874-8746F1C2D9CA} Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 19 Feb 2008 22:39:51 -0000 I have a box that we recently installed 16GB of RAM on. The box is i386 FreeBSD 6.2. It only recognizes 4gb. I am currently recompiling the kernel to support options PAE (KERNCONF=PAE) in order to see this. I understand this is still considered a Beta implementation ,and this is a production box. Does anyone have any alternative solutions that would provide a more reliable environment other than PAE? Dmesg Output is as follows : Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 3489005568 (3327 MB) avail memory = 3414196224 (3256 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: on acpi0 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 cpu3: on acpi0 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: irq 18 at device 2.0 on pci2 pci4: on pcib4 em0: port 0x2000-0x201f mem 0xd8000000-0xd801ffff irq 18 at device 0.0 on pci4 em0: Ethernet address: 00:30:48:8d:e7:8e em1: port 0x2020-0x203f mem 0xd8020000-0xd803ffff irq 19 at device 0.1 on pci4 em1: Ethernet address: 00:30:48:8d:e7:8f pcib5: at device 0.3 on pci1 pci5: on pcib5 pci0: at device 8.0 (no driver attached) pcib6: irq 17 at device 28.0 on pci0 pci6: on pcib6 uhci0: port 0x1800-0x181f irq 17 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1860-0x187f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xd8500000-0xd85003ff irq 17 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib7: at device 30.0 on pci0 pci7: on pcib7 pci7: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x18c0-0x18c7,0x1894-0x1897,0x1898-0x189f,0x1890-0x1893,0x18a0-0x18bf mem 0xd8500400-0xd85007ff irq 19 at device 31.2 on pci0 atapci1: AHCI Version 01.10 controller with 6 ports detected ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 ata6: on atapci1 ata7: on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDRW at ata0-slave UDMA33 ad4: 239372MB at ata2-master SATA300 ad6: 239372MB at ata3-master SATA300 ar0: 239370MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/ar0s1a ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled em0: link state changed to UP From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 23:19:40 2008 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 10F3D16A419 for ; Tue, 19 Feb 2008 23:19:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0532E13C45B for ; Tue, 19 Feb 2008 23:19:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id A0DA91CC033; Tue, 19 Feb 2008 15:19:39 -0800 (PST) Date: Tue, 19 Feb 2008 15:19:39 -0800 From: Jeremy Chadwick To: Kevin K Message-ID: <20080219231939.GA13625@eos.sc1.parodius.com> References: <002e01c87344$371766b0$a5463410$@com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c87344$371766b0$a5463410$@com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 19 Feb 2008 23:19:40 -0000 On Tue, Feb 19, 2008 at 05:10:17PM -0500, Kevin K wrote: > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE? You have two options, and these are the only two I'm aware of: 1) Run amd64 (64-bit). 2) Run i386 with PAE enabled. I would choose the 64-bit option in your situation. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 23:26:56 2008 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 E928116A41A for ; Tue, 19 Feb 2008 23:26:56 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id 7BBD213C502 for ; Tue, 19 Feb 2008 23:26:56 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:52271 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1JRbrT-0007g1-7k for freebsd-stable@freebsd.org; Wed, 20 Feb 2008 00:26:55 +0100 Received: (qmail 32628 invoked from network); 20 Feb 2008 00:26:52 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 20 Feb 2008 00:26:52 +0100 Received: (qmail 13458 invoked by uid 1001); 20 Feb 2008 00:26:52 +0100 Date: Wed, 20 Feb 2008 00:26:52 +0100 From: Erik Trulsson To: Kevin K Message-ID: <20080219232652.GA13404@owl.midgard.homeip.net> Mail-Followup-To: Kevin K , freebsd-stable@freebsd.org References: <002e01c87344$371766b0$a5463410$@com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c87344$371766b0$a5463410$@com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1JRbrT-0007g1-7k. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1JRbrT-0007g1-7k 070b48f15d952ae5bf438d49d39e5cfa Cc: freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 19 Feb 2008 23:26:57 -0000 On Tue, Feb 19, 2008 at 05:10:17PM -0500, Kevin K wrote: > I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. > > > > I am currently recompiling the kernel to support options PAE (KERNCONF=PAE) > in order to see this. I understand this is still considered a Beta > implementation ,and this is a production box. > > > > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE? If you want to use all the 16GB RAM on that machine then your only options is to use the amd64 version of FreeBSD or i386+PAE. amd64 is likely to work better. (Yes, the amd64 version of FreeBSD should work on your hardware according to the quoted dmesg output.) > > > > Dmesg Output is as follows : > > > > Copyright (c) 1992-2007 The FreeBSD Project. > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > > The Regents of the University of California. All rights reserved. > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 > > root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3000.13-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 > > > Features=0xbfebfbff ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0xe4bd,> > > AMD Features=0x20100000 > > AMD Features2=0x1 > > Cores per package: 2 > > Logical CPUs per core: 2 > > real memory = 3489005568 (3327 MB) > > avail memory = 3414196224 (3256 MB) > > ACPI APIC Table: > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > [snip] -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 00:46:03 2008 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 735D216A417 for ; Wed, 20 Feb 2008 00:46:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 530B113C442 for ; Wed, 20 Feb 2008 00:46:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3693604waf.3 for ; Tue, 19 Feb 2008 16:46:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=rZytH1JwnKG9jNpEjhszLXgXRyXQ3GVk55I40zofiP0=; b=grP3xiKdhwFRhqCZMkOtUqqDVABGoUjz+4mLyIVhXioJU+2V95LR4/piZiPg3fNnJiQo7TD2YQXpZufm2LvezXblcacmPEmxn3ILUWOtAZGxNV59gqV1t80PbA4L42A38q0qEnDHAl7112+oFSTM9HflIKQwoOyhwHNHC5oeCjM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VSzl7tL09IfOllMUsnmsjwqmp6k6mvvlqtE4H6Kz1T1FMjgJxAJ1I1Lkgqpr1blGAjDqCR1omWQ/c9+CpwQt4RJqmcobWn4AZrbuIeZMxhSC+rsKWhCRNzdHNLPB8sYnHOAaE0ZSlaV8YomRHDD7+lBX93jyuXbyBDMnsI50078= Received: by 10.115.93.16 with SMTP id v16mr1901272wal.126.1203468363007; Tue, 19 Feb 2008 16:46:03 -0800 (PST) Received: by 10.114.241.9 with HTTP; Tue, 19 Feb 2008 16:46:02 -0800 (PST) Message-ID: <4956a5e50802191646p6757ff54gad377ad60a36efb2@mail.gmail.com> Date: Tue, 19 Feb 2008 21:46:02 -0300 From: Nenhum_de_Nos To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: is there any raid5 in software in FreeBSD ? 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, 20 Feb 2008 00:46:03 -0000 i've seen RAID 0 through 3 (skip 2 ;) ) thanks, matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 01:07:00 2008 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 9FDB616A47C for ; Wed, 20 Feb 2008 01:07:00 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id AB20313C64F for ; Wed, 20 Feb 2008 00:51:35 +0000 (UTC) (envelope-from joe@skyrush.com) Received: from crater.wildlava.net (crater.wildlava.net [67.40.138.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id 8FD558F42B; Tue, 19 Feb 2008 17:51:34 -0700 (MST) Message-ID: <47BB7994.7090500@skyrush.com> Date: Tue, 19 Feb 2008 17:51:32 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Nenhum_de_Nos References: <4956a5e50802191646p6757ff54gad377ad60a36efb2@mail.gmail.com> In-Reply-To: <4956a5e50802191646p6757ff54gad377ad60a36efb2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: is there any raid5 in software in FreeBSD ? 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, 20 Feb 2008 01:07:00 -0000 ZFS has RAIDZ - very similar to RAID5 (with added features), if you don't mind ZFS's current experimental state. -Joe Nenhum_de_Nos wrote: > i've seen RAID 0 through 3 (skip 2 ;) ) > > thanks, > > matheus > From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 02:06:23 2008 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 11FA716A400 for ; Wed, 20 Feb 2008 02:06:23 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id F0CB813C45B for ; Wed, 20 Feb 2008 02:06:22 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from [192.168.3.245] (jn@stealth.jnielsen.net [74.218.226.254]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id m1K26Km4005109; Tue, 19 Feb 2008 21:06:22 -0500 (EST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-stable@freebsd.org Date: Tue, 19 Feb 2008 21:05:41 -0500 User-Agent: KMail/1.9.7 References: <4956a5e50802191646p6757ff54gad377ad60a36efb2@mail.gmail.com> <47BB7994.7090500@skyrush.com> In-Reply-To: <47BB7994.7090500@skyrush.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802192105.42348.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Nenhum_de_Nos Subject: Re: is there any raid5 in software in FreeBSD ? 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, 20 Feb 2008 02:06:23 -0000 On Tuesday 19 February 2008 07:51:32 pm Joe Peterson wrote: > Nenhum_de_Nos wrote: > > i've seen RAID 0 through 3 (skip 2 ;) ) > > > > thanks, > > ZFS has RAIDZ - very similar to RAID5 (with added features), if you > don't mind ZFS's current experimental state. gvinum supports RAID5, but is a bit more complicated than g[mirror|stripe| raid3]. There is also an experimental graid5 module but last I heard it was a long way from being ready to commit and it doesn't seem to have much momentum (although FreeNAS uses it). If/when I get around to buying more disks for my home server I'll be using ZFS. YMMV. JN From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 03:57:52 2008 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 60A0F16A400 for ; Wed, 20 Feb 2008 03:57:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 560DE13C4D3 for ; Wed, 20 Feb 2008 03:57:52 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 3B1311A4D80; Tue, 19 Feb 2008 19:57:52 -0800 (PST) Date: Tue, 19 Feb 2008 19:57:52 -0800 From: Alfred Perlstein To: Kevin K Message-ID: <20080220035752.GR99258@elvis.mu.org> References: <002e01c87344$371766b0$a5463410$@com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c87344$371766b0$a5463410$@com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 03:57:52 -0000 * Kevin K [080219 14:40] wrote: > I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. > > > > I am currently recompiling the kernel to support options PAE (KERNCONF=PAE) > in order to see this. I understand this is still considered a Beta > implementation ,and this is a production box. > > > > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE? Besideds PAE some people have mentioned running an amd64 system. One thing to consider is that PAE in 6-stable (6.3 and beyond) is considered very stable, so if you can't make the jump to amd64 system because you'd have to recompile too much, you might have luck updating sources to 6-stable and trying that kernel, then installing 6.3 userland. good luck, -Alfred From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 07:00:29 2008 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 B81FA16A407; Wed, 20 Feb 2008 07:00:29 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by mx1.freebsd.org (Postfix) with ESMTP id 7A29C13C467; Wed, 20 Feb 2008 07:00:29 +0000 (UTC) (envelope-from tom@samplonius.org) Received: from localhost (localhost [127.0.0.1]) by ly.sdf.com (Postfix) with ESMTP id BBACA37C002; Tue, 19 Feb 2008 22:56:13 -0800 (PST) X-Virus-Scanned: amavisd-new at X-Spam-Score: -4.044 X-Spam-Level: X-Spam-Status: No, score=-4.044 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, AWL=0.355, BAYES_00=-2.599] Received: from ly.sdf.com ([127.0.0.1]) by localhost (ly.sdf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NX8u5LAA+tY1; Tue, 19 Feb 2008 22:56:09 -0800 (PST) Received: from ly.sdf.com (ly.sdf.com [216.113.193.83]) by ly.sdf.com (Postfix) with ESMTP id 54BF337C001; Tue, 19 Feb 2008 22:56:09 -0800 (PST) Date: Tue, 19 Feb 2008 22:56:09 -0800 (PST) From: Tom Samplonius To: Alfred Perlstein Message-ID: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> In-Reply-To: <20080220035752.GR99258@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [216.113.193.90] Cc: Kevin K , freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 07:00:29 -0000 ----- "Alfred Perlstein" wrote: > > > > Does anyone have any alternative solutions that would provide a > more > > reliable environment other than PAE? > > Besideds PAE some people have mentioned running an amd64 system. > > One thing to consider is that PAE in 6-stable (6.3 and beyond) > is considered very stable, so if you can't make the jump to amd64 > system because you'd have to recompile too much, you might have luck > updating sources to 6-stable and trying that kernel, then installing > 6.3 userland. Is PAE really that stable? I thought it was fairly unpolished, mainly because PAE is seen as a weak kludge implemented by Intel because they all thought we would all be using Itanium's by now. Intel reversed their folly pretty quickly, adopted the x86-64 extensions as-is from AMD, and pushed them onto every piece of silicon they make. I also really don't know how anyone would properly use 16GB of RAM under PAE anyways? Each process is going to limited to just under 4GB. The kernel memory space can't be bigger than 4GB either, so forget about a huge disk cache. And is there some really stability fear about FreeBSD on x86-64? Seems just the same as i386. > good luck, > -Alfred Tom From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 10:47:39 2008 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 AF8A816A402; Wed, 20 Feb 2008 10:47:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11C7413C4EE; Wed, 20 Feb 2008 10:47:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47BC0548.3060801@FreeBSD.org> Date: Wed, 20 Feb 2008 11:47:36 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Tom Samplonius References: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> In-Reply-To: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Kevin K , Alfred Perlstein , freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 10:47:39 -0000 Tom Samplonius wrote: > ----- "Alfred Perlstein" wrote: > >>> Does anyone have any alternative solutions that would provide a >> more >>> reliable environment other than PAE? >> Besideds PAE some people have mentioned running an amd64 system. >> >> One thing to consider is that PAE in 6-stable (6.3 and beyond) >> is considered very stable, so if you can't make the jump to amd64 >> system because you'd have to recompile too much, you might have luck >> updating sources to 6-stable and trying that kernel, then installing >> 6.3 userland. > > Is PAE really that stable? I thought it was fairly unpolished, mainly because PAE is seen as a weak kludge implemented by Intel because they all thought we would all be using Itanium's by now. Intel reversed their folly pretty quickly, adopted the x86-64 extensions as-is from AMD, and pushed them onto every piece of silicon they make. Enough people run PAE without issue that there's a pretty good chance it will run for you too. Some drivers were never adapted to work with PAE so hardware support is a smaller subset than regular i386. > I also really don't know how anyone would properly use 16GB of RAM under PAE anyways? Each process is going to limited to just under 4GB. The kernel memory space can't be bigger than 4GB either, so forget about a huge disk cache. If you have many moderate-sized processes then PAE can be a reasonable fit. > And is there some really stability fear about FreeBSD on x86-64? Seems just the same as i386. No stability issues in general. Kris From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 12:09:19 2008 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 8035C16A40B; Wed, 20 Feb 2008 12:09:19 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 3D64513C442; Wed, 20 Feb 2008 12:09:19 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JRnlF-000LWc-Iw; Wed, 20 Feb 2008 12:09:17 +0000 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JRnlF-0006xP-Gx; Wed, 20 Feb 2008 12:09:17 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JRnlF-0009RV-GR; Wed, 20 Feb 2008 12:09:17 +0000 To: alfred@freebsd.org, kkutzko@teksavvy.com In-Reply-To: <20080220035752.GR99258@elvis.mu.org> Message-Id: From: Pete French Date: Wed, 20 Feb 2008 12:09:17 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 12:09:19 -0000 > Does anyone have any alternative solutions that would provide a more > reliable environment other than PAE? I was faced with a similar problem last autmumn - we had been running 6.2 on a set of servers with 4 gig or RAM, but purchased new servers with 16 gig in them. I experimented with various things - PAE being my initial try, and ended up opting for 7.0 (prerelease) usin amd64. It worked like a charm. Note that I only shifted the OS to amd64 - I still ran my application code as the existing 6.2/i386 binaries. Didn't want to make a drastic shift in the application at the same time. It all ran fine - but our application is staticly linked, so that did make things simpler. Since then I;ve migrated almost everything we have over to amd64 and 7.0 and we are very happy with it - the only machines that havent been moved are those which cannot run in 64 bit mode (two desktops and two older servers). So, I would recommend going with amd64 if you can. -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 15:16:44 2008 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 9F63316A405 for ; Wed, 20 Feb 2008 15:16:44 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (thingy.kcilink.com [74.92.149.59]) by mx1.freebsd.org (Postfix) with ESMTP id 6BE3913C45B for ; Wed, 20 Feb 2008 15:16:44 +0000 (UTC) (envelope-from vivek@khera.org) Received: from host-121.int.kcilink.com (host-121.int.kcilink.com [192.168.7.121]) by yertle.kcilink.com (Postfix) with ESMTP id 70FD18A0B6 for ; Wed, 20 Feb 2008 10:16:43 -0500 (EST) Message-Id: <32DF7439-5B15-4212-BE92-36F80A7A2224@khera.org> From: Vivek Khera To: FreeBSD Stable List In-Reply-To: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Wed, 20 Feb 2008 10:16:43 -0500 References: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> X-Mailer: Apple Mail (2.919.2) Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 15:16:44 -0000 On Feb 20, 2008, at 1:56 AM, Tom Samplonius wrote: > And is there some really stability fear about FreeBSD on x86-64? > Seems just the same as i386. Some poorly written software fails to run properly in 64-bit environment. I have one such package, and my solution was to compile it on a 32-bit box, and copy the binaries over. Works just fine with 32-bit compat enabled on the amd64 kernel. Other than that, the FreeBSD/amd64 has been 100% rock solid for me since 6.0 when I started getting 64-bit boxes. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 15:55:51 2008 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 9765F16A4D7 for ; Wed, 20 Feb 2008 15:55:51 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id E100D13C45E for ; Wed, 20 Feb 2008 15:55:50 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1KFtiKL094043; Wed, 20 Feb 2008 16:55:49 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1KFtiiU094042; Wed, 20 Feb 2008 16:55:44 +0100 (CET) (envelope-from olli) Date: Wed, 20 Feb 2008 16:55:44 +0100 (CET) Message-Id: <200802201555.m1KFtiiU094042@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, kkutzko@teksavvy.com In-Reply-To: <002e01c87344$371766b0$a5463410$@com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 20 Feb 2008 16:55:49 +0100 (CET) Cc: Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, kkutzko@teksavvy.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2008 15:55:51 -0000 Kevin K wrote: > I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. Several people have already pointed out that you can either run FreeBSD/i386+PAE or FreeBSD/amd64 (64bit). However, there's an important piece of information missing: _Why_ did you install 16 GB of RAM? The answer to that question might give an indication which of the two ways would be best for you. For example, if you need to run a single large application that needs much RAM, then i386+PAE won't help you at all, because you still have a 4 GB address space limit and a 4 GB process size limit. Actually much less than 4 GB because the 32bit address space is shared between kernel and userland. To get rid of the 4 GB limit completely, you must install FreeBSD/amd64. Also, amd64 code is often (but not always) faster than i386 code. My recommendation is that you use amd64, unless there is a specific reason you can't do that, e.g. you depend on a driver or third-party software that won't run on amd64. Then i386+PAE is your only choice, unfortunately. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549 From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 16:32:29 2008 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 8A41C16A401 for ; Wed, 20 Feb 2008 16:32:29 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD0313C442 for ; Wed, 20 Feb 2008 16:32:28 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JRrrv-0003wC-1y for freebsd-stable@freebsd.org; Wed, 20 Feb 2008 16:32:27 +0000 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 ; Wed, 20 Feb 2008 16:32:27 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Feb 2008 16:32:27 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Wed, 20 Feb 2008 17:34:54 +0100 Lines: 48 Message-ID: References: <20080220035752.GR99258@elvis.mu.org> <4594886.5961203490569242.JavaMail.root@ly.sdf.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig46158382CB1A284B25B1008B" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20071022) In-Reply-To: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 16:32:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig46158382CB1A284B25B1008B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tom Samplonius wrote: > Is PAE really that stable? I thought it was fairly unpolished, mainl= y because PAE is seen as a weak kludge implemented by Intel because they = all thought we would all be using Itanium's by now. Intel reversed their= folly pretty quickly, adopted the x86-64 extensions as-is from AMD, and = pushed them onto every piece of silicon they make. Architecturally, it's a nasty kludge. As far as stability on FreeBSD is concerned, my only machine under PAE with 4 GB RAM (without PAE it would use a bit over 3 GB) is very solid on 6-STABLE. > I also really don't know how anyone would properly use 16GB of RAM un= der PAE anyways? Each process is going to limited to just under 4GB. Th= e kernel memory space can't be bigger than 4GB either, so forget about a = huge disk cache. As I understand it, one possible benefit could be to use the memory for disk / file cache. AFAIK the pages are just pages, without distinction where they are mapped, and for example, if you run PostgreSQL, it couldn't use more than 4 GB for its own data (actually closer to 2 GB because of some sysvshm issues) but it will indirectly use the cache. > And is there some really stability fear about FreeBSD on x86-64? See= ms just the same as i386. I agree, FreeBSD on amd64 is very stable. --------------enig46158382CB1A284B25B1008B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHvFauldnAQVacBcgRAnqVAKCvALurLcNegpBmsOf6kI5ZFfomsACbBLY6 70XfN7SP3Bm7s53lPVbeQvw= =VxSl -----END PGP SIGNATURE----- --------------enig46158382CB1A284B25B1008B-- From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 16:37:34 2008 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 8713F16A400 for ; Wed, 20 Feb 2008 16:37:34 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) Received: from ironport2-out.pppoe.ca (ironport2-out.pppoe.ca [206.248.154.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2F1D213C45A for ; Wed, 20 Feb 2008 16:37:33 +0000 (UTC) (envelope-from kkutzko@teksavvy.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAHPmu0dMCqa7/2dsb2JhbACKc6V3BA X-IronPort-AV: E=Sophos;i="4.25,381,1199682000"; d="scan'208";a="14753692" Received: from mail.pppoe.ca ([65.39.192.132]) by ironport2-out.pppoe.ca with ESMTP; 20 Feb 2008 11:37:30 -0500 Received: from kevin ([76.10.166.187]) by mail.pppoe.ca (Internet Mail Server v1.0) with ASMTP id ASF60230; Wed, 20 Feb 2008 11:37:30 -0500 From: "Kevin K" To: "'Ivan Voras'" , References: <20080220035752.GR99258@elvis.mu.org> <4594886.5961203490569242.JavaMail.root@ly.sdf.com> In-Reply-To: Date: Wed, 20 Feb 2008 11:37:28 -0500 Message-ID: <001d01c873de$e1cef5b0$a56ce110$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Achz3lsyvJK8x8YrRpSiatAhfRYETgAABJoA Content-Language: en-us Cc: Subject: RE: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 16:37:34 -0000 Thank you all for your suggestions. I have been trying to push to move = to amd64 architecture for all the reasons you all stated. For the = record, we tested PAE on one machine, booted the kernel w/ nextboot and = it crashed about 15 minutes later. I will consider configuring a dump = device to analyze the kernel dumps, but for now we reverted to the = original i386 kernel and are likely going to scrap the PAE idea and move = to amd64. This was a management decision (obviously) and the people who originally = built this box (long before I was there), did not have enough experience = or foresight. i was hoping for alternative suggestions to reduce = downtime of these boxes, such as recompiling amd64 manually instead of a = fresh install. These boxes are just Apache, Mysql, PHP type boxes. Nothing exotic or = fancy. Thanks again for your suggestions. I am trying my best to relay the = reasoning and rock-solid logic ;) -----Original Message----- From: owner-freebsd-stable@freebsd.org = [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Ivan Voras Sent: Wednesday, February 20, 2008 11:35 AM To: freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM Tom Samplonius wrote: > Is PAE really that stable? I thought it was fairly unpolished, = mainly because PAE is seen as a weak kludge implemented by Intel because = they all thought we would all be using Itanium's by now. Intel reversed = their folly pretty quickly, adopted the x86-64 extensions as-is from = AMD, and pushed them onto every piece of silicon they make. Architecturally, it's a nasty kludge. As far as stability on FreeBSD is = concerned, my only machine under PAE with 4 GB RAM (without PAE it would = use a bit over 3 GB) is very solid on 6-STABLE. > I also really don't know how anyone would properly use 16GB of RAM = under PAE anyways? Each process is going to limited to just under 4GB. = The kernel memory space can't be bigger than 4GB either, so forget about = a huge disk cache. As I understand it, one possible benefit could be to use the memory for = disk / file cache. AFAIK the pages are just pages, without distinction = where they are mapped, and for example, if you run PostgreSQL, it = couldn't use more than 4 GB for its own data (actually closer to 2 GB = because of some sysvshm issues) but it will indirectly use the cache. > And is there some really stability fear about FreeBSD on x86-64? = Seems just the same as i386. I agree, FreeBSD on amd64 is very stable. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 16:55:59 2008 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 A9EBD16A403; Wed, 20 Feb 2008 16:55:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from angel.ticketswitch.com (angel.ticketswitch.com [IPv6:2002:57e0:1d4e::1]) by mx1.freebsd.org (Postfix) with ESMTP id 610EC13C458; Wed, 20 Feb 2008 16:55:59 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [10.50.50.2] (helo=smaug.rattatosk) by angel.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JRsEg-000127-KD; Wed, 20 Feb 2008 16:55:58 +0000 Received: from dilbert.rattatosk ([10.50.50.6] helo=dilbert.ticketswitch.com) by smaug.rattatosk with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JRsEg-000Aou-H0; Wed, 20 Feb 2008 16:55:58 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JRsEg-0002RH-GA; Wed, 20 Feb 2008 16:55:58 +0000 To: freebsd-stable@freebsd.org, ivoras@freebsd.org In-Reply-To: Message-Id: From: Pete French Date: Wed, 20 Feb 2008 16:55:58 +0000 Cc: Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 16:55:59 -0000 > Architecturally, it's a nasty kludge. As far as stability on FreeBSD is > concerned, my only machine under PAE with 4 GB RAM (without PAE it would > use a bit over 3 GB) is very solid on 6-STABLE. To the original poster - does a PAE kernel actually boot on your 16 gig machines ? My problem was that I had tested PAE of 4 gig machines (to avoid the "bit over 3" problem) but when it came down to 16 gig on the Xeons then it wouldnt actually boot :-( -pete. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 17:17:50 2008 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 CA8E416A401 for ; Wed, 20 Feb 2008 17:17:50 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 25CF113C468 for ; Wed, 20 Feb 2008 17:17:49 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1KHHgge098089; Wed, 20 Feb 2008 18:17:48 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1KHHfQv098088; Wed, 20 Feb 2008 18:17:41 +0100 (CET) (envelope-from olli) Date: Wed, 20 Feb 2008 18:17:41 +0100 (CET) Message-Id: <200802201717.m1KHHfQv098088@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, blackdragon@highveldmail.co.za In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 20 Feb 2008 18:17:49 +0100 (CET) Cc: Subject: Re: tmpfs: strange behaviour X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, blackdragon@highveldmail.co.za List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2008 17:17:50 -0000 David Naylor wrote: > Oliver Fromme wrote: > > What is the exact CFLAGS setting that you use? > > Do you use -O2 (or -Os) without -fno-strict-aliasing? > > I have managed to isolate the problem and it is definitely tmpfs > related. If the directory that I'm installing into is tmpfs then it > will fail, if it is ufs then it works. > > I recompiled tmpfs module (and reloaded) with CFLAGS='' with the same result. > > As an aside I have found that the default CFLAGS for src are: -O2 > -fno-strict-aliasing -pipe. For most parts of src, but some override it. > Would -fstrict-aliasing break anything in base/sys? I think src/sys is clean with regards to aliasing, but I'm not 100% sure. Someone please correct me if I'm wrong. I recommend not to put a CFLAGS line in /etc/make.conf at all. So far I haven't seen an example of a really useful CFLAGS line in this thread, but several examples that could possibly cause damage. It's best not to override the default (which is there for a reason). If you want better optimization, a appropriate CPUTYPE=... line is probably a better idea. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing."         -- Mother Teresa From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 17:56:35 2008 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 C814516A409 for ; Wed, 20 Feb 2008 17:56:35 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1201513C4DB for ; Wed, 20 Feb 2008 17:56:34 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1KHuVS3099746; Wed, 20 Feb 2008 18:56:31 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1KHuVO4099745; Wed, 20 Feb 2008 18:56:31 +0100 (CET) (envelope-from olli) Date: Wed, 20 Feb 2008 18:56:31 +0100 (CET) Message-Id: <200802201756.m1KHuVO4099745@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, jhs@berklix.org In-Reply-To: <200802150009.m1F09IPr045943@fire.js.berklix.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 20 Feb 2008 18:56:32 +0100 (CET) Cc: Subject: Re: dmesg : no output on 1 of 2 7-stable boxes 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, 20 Feb 2008 17:56:35 -0000 Julian H. Stacey wrote: > Oliver Fromme wrote: > > The dmesg buffer is a circular buffer containing both > > kernel output and console output. However, "dmesg" > > displays only the kernel output. If there was lots of > > console output, it filled all of the dmesg buffer, > > so "dmesg" displays nothing (all of the kernel output > > was overwritten by console output). "dmesg -a" will > > display everything, i.e. kernel + console output. > > Some of that description could usefuly be added to `man dmesg` ? I agree. > Might some commiter wnat to hack a few words in ? Or do we neeed > a formal send-pr (that a commiter would rephrase likely anyway, so > best skip the send-pr ? ). If you have the time, please submit a PR (docs category). I'll take care of it. You're a native English speaker. I am not. So chances are that I won't rephrase it, except for technical reasons. And even if I did rephrase it, it's still a good thing to have a PR, so the issue doesn't get lost and forgotten. > > > - I tried loader.conf kern.msgbuf=64000 > > > > I think it must be a multiple of the pages size, i,e, > > 4K = 4096 on FreeBSD/i386. I usually set it to 65536 > > or 131072. > [...] > Puzzled on syntax to set size in loader.conf ? Unfortunately it's a kernel constant, not a tunable. The only way to change it is via "options MSGBUF_SIZE=..." in your kernel config file, and rebuild the kernel. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Whatever happened to the days when hacking started at the cerebral cortex, and not at the keyboard?" -- Sid on userfriendly.org by Illiad, 2007-06-20 From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 18:41:32 2008 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 9CC4316A406 for ; Wed, 20 Feb 2008 18:41:32 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.freebsd.org (Postfix) with ESMTP id 4F34713C4EE for ; Wed, 20 Feb 2008 18:41:32 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so3297029pyb.10 for ; Wed, 20 Feb 2008 10:41:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; bh=rxsm9TJnXZfDxmusG2ONTynEPwD+jeuh/uFYlGhc83A=; b=mc9Bxu+kprG4mitMHcTVy5RlDbNwubp79V3200NmLyJ/baZ1ddqfeOrqA0noe6/t83KYp7+cCa/VqtooaONFsMkISu0Y3Uft77awyeltgbC0iqZ9fSpBEEmPe99SfZyKNOGrjPG+UWRplV/kmSgQ3+AHKlsq8ExUJsh/h+XLhxM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=GFYYJgApvWzIXp91xxw/Mju7NKyfvBOdxAxoGzYCHLPf+OWnNTLF8TXvx6HD1qos8CZB88bUVwEZSGKpA43hcGbetU4JaCMivFngII9B69mjRx3F/9BXv/IDZEAG8LM5NK7glZYGKs5zHziaoHe6RYpdmKtQpz2VPbiNeSTEYu4= Received: by 10.65.51.15 with SMTP id d15mr17096963qbk.6.1203532890038; Wed, 20 Feb 2008 10:41:30 -0800 (PST) Received: by 10.64.195.8 with HTTP; Wed, 20 Feb 2008 10:41:30 -0800 (PST) Message-ID: <5f67a8c40802201041m66e8aa89yabce4ba87c5c1b4c@mail.gmail.com> Date: Wed, 20 Feb 2008 13:41:30 -0500 From: "Zaphod Beeblebrox" To: "Kevin K" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re:more than 4gb of RAM (configurations) 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, 20 Feb 2008 18:41:32 -0000 On Feb 19, 2008 5:10 PM, Kevin K wrote: > I have a box that we recently installed 16GB of RAM on. The box is i386 > FreeBSD 6.2. It only recognizes 4gb. Siding with most of the group (go amd64), I'll add my own comment: Using PAE to access 4G of RAM (because 4G shows up as 2.5 to 3.5 gig, depending on the motherboard) under i386 is a reasonable solution, IMHO. Maybe even 6 gig or 8 gig... if you're trying to extend the life of an ia32 server. But with amd64 supporting ia32 binaries well, it seems the only reason left might be drivers --- except ... are there _any_ drivers that support PAE and _not_ amd64? I'm using amd64 on my laptop (which has 4gig) because the only driver I care about (the nvidia binary driver) doesn't work under either PAE or amd64 (and ... it also doesn't support 8xxx series mobile chipsets ... so I'm screwed anyways) . I'd be curious to know if anyone's still hedging their bets by making their machine dual-boot i386/amd64 --- and how they configure it. Have you thought about sharing /usr or parts of it? Installed ports can seemingly mess things up. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 19:12:37 2008 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 ED20116A41B for ; Wed, 20 Feb 2008 19:12:37 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 1168E13C458 for ; Wed, 20 Feb 2008 19:12:36 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 20 Feb 2008 13:45:54 -0500 From: "Brian A. Seklecki" To: Andriy Gapon In-Reply-To: <479A0053.5020409@icyb.net.ua> References: <479A0053.5020409@icyb.net.ua> Content-Type: text/plain Organization: Collaborative Fusion, Inc. Date: Wed, 20 Feb 2008 13:45:54 -0500 Message-Id: <1203533154.10391.45.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall: weird ui problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2008 19:12:38 -0000 On Fri, 2008-01-25 at 17:29 +0200, Andriy Gapon wrote: > FreeBSD 6.3-RELEASE amd64 > Running sysinstall for "post-installation configuration" of sorts in > xterm/konsole/gnome-terminal. Hmm your $TERM environmental variable is set to vt100? vt200? wscons? ~BAS > Very strange issue: arrow keys work quite well throughout sysinstall > menus but in Fdisk and Label screens both up and down arrow keys are > interpreted as down key. This is not fatal in Label screen because > navigation cycles, but in Fdisk menu you can not reach up from the > bottom entry (slice). > > In system console everything is OK, though. > -- Brian A. Seklecki Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 20:58:37 2008 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 4B28916A401 for ; Wed, 20 Feb 2008 20:58:37 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3747913C46E for ; Wed, 20 Feb 2008 20:58:37 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 151911A4D7E; Wed, 20 Feb 2008 12:58:37 -0800 (PST) Date: Wed, 20 Feb 2008 12:58:37 -0800 From: Alfred Perlstein To: Tom Samplonius Message-ID: <20080220205837.GX99258@elvis.mu.org> References: <20080220035752.GR99258@elvis.mu.org> <4594886.5961203490569242.JavaMail.root@ly.sdf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4594886.5961203490569242.JavaMail.root@ly.sdf.com> User-Agent: Mutt/1.4.2.3i Cc: Kevin K , freebsd-stable@freebsd.org Subject: Re: Dual Core Xeon / i386 install w/ more than 4gb of RAM 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, 20 Feb 2008 20:58:37 -0000 * Tom Samplonius [080219 23:00] wrote: > > ----- "Alfred Perlstein" wrote: > > > > > > > Does anyone have any alternative solutions that would provide a > > more > > > reliable environment other than PAE? > > > > Besideds PAE some people have mentioned running an amd64 system. > > > > One thing to consider is that PAE in 6-stable (6.3 and beyond) > > is considered very stable, so if you can't make the jump to amd64 > > system because you'd have to recompile too much, you might have luck > > updating sources to 6-stable and trying that kernel, then installing > > 6.3 userland. > > Is PAE really that stable? I thought it was fairly unpolished, mainly because PAE is seen as a weak kludge implemented by Intel because they all thought we would all be using Itanium's by now. Intel reversed their folly pretty quickly, adopted the x86-64 extensions as-is from AMD, and pushed them onto every piece of silicon they make. The 6-stable (6.3 and beyond) has been in use at Yahoo and other sites for quite some time. > I also really don't know how anyone would properly use 16GB of RAM under PAE anyways? Each process is going to limited to just under 4GB. The kernel memory space can't be bigger than 4GB either, so forget about a huge disk cache. Actually this is incorrect, the kernel can use physical memory outside of its address space as cache, so you can get more than 4GB of cache. > And is there some really stability fear about FreeBSD on x86-64? Seems just the same as i386. It's fine, people are just suggesting that the person upgrade to -stable (not stay at 6.2) and are concerned that reinstalling the machine as amd64 might be too much of a move. -Alfred From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 21:11:57 2008 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 B8FA116A405 for ; Wed, 20 Feb 2008 21:11:57 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 6566213C4E1 for ; Wed, 20 Feb 2008 21:11:56 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 96282744006; Wed, 20 Feb 2008 23:11:55 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id P2uYEHek6-bh; Wed, 20 Feb 2008 23:11:55 +0200 (EET) Received: from [10.74.70.239] (unknown [193.138.145.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id E21E6744004; Wed, 20 Feb 2008 23:11:54 +0200 (EET) Message-ID: <47BC9796.5040303@icyb.net.ua> Date: Wed, 20 Feb 2008 23:11:50 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: bseklecki@collaborativefusion.com References: <479A0053.5020409@icyb.net.ua> <1203533154.10391.45.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> In-Reply-To: <1203533154.10391.45.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall: weird ui problem 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, 20 Feb 2008 21:11:57 -0000 on 20/02/2008 20:45 Brian A. Seklecki said the following: > > On Fri, 2008-01-25 at 17:29 +0200, Andriy Gapon wrote: >> FreeBSD 6.3-RELEASE amd64 >> Running sysinstall for "post-installation configuration" of sorts in >> xterm/konsole/gnome-terminal. > > Hmm your $TERM environmental variable is set to vt100? vt200? wscons? $ echo $TERM xterm > ~BAS > >> Very strange issue: arrow keys work quite well throughout sysinstall >> menus but in Fdisk and Label screens both up and down arrow keys are >> interpreted as down key. This is not fatal in Label screen because >> navigation cycles, but in Fdisk menu you can not reach up from the >> bottom entry (slice). >> >> In system console everything is OK, though. >> -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 23:26:19 2008 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 6D50816A401 for ; Wed, 20 Feb 2008 23:26:19 +0000 (UTC) (envelope-from gil.bidon@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5C213C447 for ; Wed, 20 Feb 2008 23:26:19 +0000 (UTC) (envelope-from gil.bidon@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so1416343ele.3 for ; Wed, 20 Feb 2008 15:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=RLmciALMAq131POJsIXcDn9rfl/NNdXfhTmXiPkOPEY=; b=o7NrHu/LjhH0Rspc4in0k5EUb3X8TovM99sMSAQG8MuCzHISKQshmXqqD74P+nnP/3MP1TWqP04u1H4g4Z1D3yuMz8H5u+9JaAV2MvYt0onqI4bh0cEaQqiwSAvM1K0F2pE39SZyHx5nowd17ISoh1DFr2sQ6LmZXgdQ1FRwvlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=KNswToVBcQ8UdOkhpAQXVc5Aphkow6G0/yc7VidB0jYKJnM/Vaxwqj6JLskXJJGRXSzOv+wiqsIQ2J6TWv6T9+NfnMdq/IzwEdmabqAKynWmgWLXhTN+/Vq2+dnEUL9qYmwGgZtfgFDpLtWUjywFZj0IOzVWGiHYZJBUTEuapyE= Received: by 10.142.177.7 with SMTP id z7mr7055206wfe.0.1203548379000; Wed, 20 Feb 2008 14:59:39 -0800 (PST) Received: by 10.142.116.21 with HTTP; Wed, 20 Feb 2008 14:59:38 -0800 (PST) Message-ID: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> Date: Wed, 20 Feb 2008 23:59:38 +0100 From: "Gil Bidon" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 6.3 update and process freeze 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, 20 Feb 2008 23:26:19 -0000 Hi, Since i've updated my machine to FreeBSD 6.3 some process randomly start using 100% CPU or are locked to STOP state (in top). Is there a known solution / patch ? Except the rollback :) Regards, Gil From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 23:44:53 2008 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 E127216A403 for ; Wed, 20 Feb 2008 23:44:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3FAA113C457; Wed, 20 Feb 2008 23:44:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47BCBB74.1060509@FreeBSD.org> Date: Thu, 21 Feb 2008 00:44:52 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Gil Bidon References: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> In-Reply-To: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 update and process freeze 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, 20 Feb 2008 23:44:54 -0000 Gil Bidon wrote: > Hi, > Since i've updated my machine to FreeBSD 6.3 some process randomly start > using 100% CPU or are locked to STOP state (in top). > > Is there a known solution / patch ? Except the rollback :) You need to tell us more information. What processes are they? Kris From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 23:53:23 2008 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 364D216A400 for ; Wed, 20 Feb 2008 23:53:23 +0000 (UTC) (envelope-from ml@proficuous.com) Received: from mail.proficuous.com (www.proficuous.com [209.240.79.128]) by mx1.freebsd.org (Postfix) with ESMTP id 0AAE613C46E for ; Wed, 20 Feb 2008 23:53:22 +0000 (UTC) (envelope-from ml@proficuous.com) Received: from [192.168.3.99] (unknown [192.168.3.99]) by mail.proficuous.com (Postfix) with ESMTP id ECAA8298204; Wed, 20 Feb 2008 17:32:21 -0600 (CST) Message-ID: <47BCB886.8090900@proficuous.com> Date: Wed, 20 Feb 2008 17:32:22 -0600 From: Aaron Martinez User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Gil Bidon References: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> In-Reply-To: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 update and process freeze 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, 20 Feb 2008 23:53:23 -0000 Gil Bidon wrote: > Hi, > Since i've updated my machine to FreeBSD 6.3 some process randomly start > using 100% CPU or are locked to STOP state (in top). > > Is there a known solution / patch ? Except the rollback :) > > Regards, > > Gil > _______________________________________________ > 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" > Gil, You'll need to provide significantly more information before anyone will be able to help you. Some of which might be, a list of the offending processes, output from top, dmesg, what patchlevel you're running, any errors from syslog. Aaron From owner-freebsd-stable@FreeBSD.ORG Thu Feb 21 05:05:19 2008 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 923BF16A400 for ; Thu, 21 Feb 2008 05:05:19 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) by mx1.freebsd.org (Postfix) with ESMTP id 2F1E113C4DD for ; Thu, 21 Feb 2008 05:05:18 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from Internal Mail-Server by mx01 (envelope-from bseklecki@collaborativefusion.com) with SMTP; 21 Feb 2008 00:05:17 -0500 From: "Brian A. Seklecki (Mobile)" To: Andriy Gapon In-Reply-To: <47BC9796.5040303@icyb.net.ua> References: <479A0053.5020409@icyb.net.ua> <1203533154.10391.45.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <47BC9796.5040303@icyb.net.ua> Content-Type: text/plain Organization: Collaborative Fusion, Inc. Date: Thu, 21 Feb 2008 00:04:50 -0500 Message-Id: <1203570290.3372.0.camel@new-host> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-1.fc8) Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: sysinstall: weird ui problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bseklecki@collaborativefusion.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2008 05:05:19 -0000 On Wed, 2008-02-20 at 23:11 +0200, Andriy Gapon wrote: > on 20/02/2008 20:45 Brian A. Seklecki said the following: > > > > On Fri, 2008-01-25 at 17:29 +0200, Andriy Gapon wrote: > >> FreeBSD 6.3-RELEASE amd64 > >> Running sysinstall for "post-installation configuration" of sorts in > >> xterm/konsole/gnome-terminal. > > > > Hmm your $TERM environmental variable is set to vt100? vt200? wscons? > I would experiment here. It is really meant to be used on wscons/pcons. Try a different terminal emulator and/or a real VTY on your control. Try vt100, vt220, vt420, pccons, etc... > $ echo $TERM > xterm > > > ~BAS > > IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. From owner-freebsd-stable@FreeBSD.ORG Thu Feb 21 08:17:40 2008 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 9B21316A405 for ; Thu, 21 Feb 2008 08:17:40 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.freebsd.org (Postfix) with ESMTP id 376E613C4E9 for ; Thu, 21 Feb 2008 08:17:39 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m1L8HcQh023295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Feb 2008 19:17:38 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m1L8Hb97044798; Thu, 21 Feb 2008 19:17:37 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m1L8Hbrs044797; Thu, 21 Feb 2008 19:17:37 +1100 (EST) (envelope-from peter) Date: Thu, 21 Feb 2008 19:17:37 +1100 From: Peter Jeremy To: Zaphod Beeblebrox Message-ID: <20080221081737.GH51095@server.vk2pj.dyndns.org> References: <5f67a8c40802201041m66e8aa89yabce4ba87c5c1b4c@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5xSkJheCpeK0RUEJ" Content-Disposition: inline In-Reply-To: <5f67a8c40802201041m66e8aa89yabce4ba87c5c1b4c@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: more than 4gb of RAM (configurations) 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, 21 Feb 2008 08:17:40 -0000 --5xSkJheCpeK0RUEJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 20, 2008 at 01:41:30PM -0500, Zaphod Beeblebrox wrote: >I'd be curious to know if anyone's still hedging their bets by making their >machine dual-boot i386/amd64 --- and how they configure it. Have you >thought about sharing /usr or parts of it? Installed ports can seemingly >mess things up. I dual-boot my laptop (actually triple-boot if you include 7.x) and have all 3 filesystem trees visible. I have my 6.x/amd64 paths setup to see the 6.x/i386 executables. Mostly it works OK but I have run into a couple of problems when building a 6.x/amd64 port and the port build process had found a 6.x/i386 version of a dependency - which causes the port build to fail at some later point. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --5xSkJheCpeK0RUEJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHvTOh/opHv/APuIcRAsPcAKCdifdY48/UwQytclWn9NxXiGJCbACgqYCZ 6wY/rNdYMGp0pX5P1ARS5qE= =5JiJ -----END PGP SIGNATURE----- --5xSkJheCpeK0RUEJ-- From owner-freebsd-stable@FreeBSD.ORG Thu Feb 21 13:43:51 2008 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 96F7D16A400 for ; Thu, 21 Feb 2008 13:43:51 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml17.kpnxchange.com (hpsmtp-eml17.KPNXCHANGE.COM [213.75.38.117]) by mx1.freebsd.org (Postfix) with ESMTP id 2F9B613C457 for ; Thu, 21 Feb 2008 13:43:50 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml103.kpnxchange.com ([213.75.84.103]) by hpsmtp-eml17.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Feb 2008 14:43:49 +0100 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml103.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Feb 2008 14:43:49 +0100 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m1LDhjfx048589 for ; Thu, 21 Feb 2008 14:43:45 +0100 (CET) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1JSBjL-0001GN-Lh for freebsd-stable@FreeBSD.ORG; Thu, 21 Feb 2008 14:44:55 +0100 Date: Thu, 21 Feb 2008 14:44:55 +0100 From: Willy Offermans To: freebsd-stable@FreeBSD.ORG Message-ID: <20080221134455.GA4324@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92/5911/Thu Feb 21 12:04:47 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on koko.offrom.nl X-OriginalArrivalTime: 21 Feb 2008 13:43:49.0896 (UTC) FILETIME=[CA0B9080:01C8748F] Cc: Subject: pervasive running on FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2008 13:43:51 -0000 Hello FreeBSD friends, Does someone has experiences of running Pervasive PSQL v9 Server under FreeBSD? I can download the trial version und try myself, but if I already get feedback I would be much grateful. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 06:14:13 2008 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 06F3016A403 for ; Fri, 22 Feb 2008 06:14:13 +0000 (UTC) (envelope-from iamdxy@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id AD6E313C474 for ; Fri, 22 Feb 2008 06:14:12 +0000 (UTC) (envelope-from iamdxy@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so550548pyb.10 for ; Thu, 21 Feb 2008 22:14:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=GasC5n05jEQfH169Jjn5oypHXpHNorstiBUHSU46zJ4=; b=J00WXI8276gf+Ct52rU5bhhQkuRHthG1i9blGBrnqez0bPLZf/6p/Z9+8uRzuvgtQoONl9m37e6W/3n3BiTtfGFm7M/a+EqtoglmAlAL7v//UiILcDGKN/QEtCtEIKL8rrTpDaIN9dFs9YeQShhHnb9ubrBJuVYJ+Z/WOJF3e98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=a0bPBf4sHadLRCCqv154iqDGIEf+N2G7GSZV4Z9y2m82Yede+zt7FWPlaPyC5+U7xIQrICX83x1iTcnhckJoqwobSdy7GYL7mjqUuoVuuAKV9NPplVaHWZfReZbpmyXYpGKkHIhzIE5bNlOCsrDOBmGFMrYf2y4NihN3taz88Nc= Received: by 10.141.163.12 with SMTP id q12mr7359101rvo.190.1203659118385; Thu, 21 Feb 2008 21:45:18 -0800 (PST) Received: by 10.141.40.19 with HTTP; Thu, 21 Feb 2008 21:45:18 -0800 (PST) Message-ID: <9c2955e10802212145m30315c18o7249d83db19e8b98@mail.gmail.com> Date: Fri, 22 Feb 2008 13:45:18 +0800 From: "Xinyu Dong" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: mddisk(ramdisk) root system that image size limit ? 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, 22 Feb 2008 06:14:13 -0000 OS: FreeBSD 6.2-RELEASE Environment = VMWare (Version 5) and Computer (CPU=Intel P4 2.4G, Memory=Kingston 1G DDR400, Storage=2G CF) create a less-than 100MB of image (image for ramdisk, mfs root) The loader.rc { load kernel // The kernel used 6.2 GENERIC load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=95k } above config can boot normal. create a greater than 100MB of image (image for ramdisk, mfs root) The loader.rc { load kernel // The kernel used 6.2 GENERIC load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=128k } above config can't boot normal, reboot immediately. create a equal 100MB or equal 99MB of image (image for ramdisk, mfs root) The loader.rc { load kernel // The kernel used 6.2 GENERIC load -t mfs_root /image // dd if=/dev/zero of=/image bs=1k count=100k (or count=99k) } above config can't boot normal, kernel panic. [TEST after system up] 1. dd if=/dev/zero of=/image bs=1k count=128k 2. mdconfig -a -t vnode -f /image -u 0 3. bsdlabel -Bw /dev/md0 auto 4. newfs /dev/md0a 5. mount /dev/md0a /mnt When system up normally: df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 23G 1.5G 20G 7% / devfs 1.0K 1.0K 0B 100% /dev /dev/md0a 124M 4.0K 114M 0% /mnt system not panic. but config loader.rc, add "load -t mfs_root /image" or "load -t md_image /image" will panic. I tried configuring the kernel, change MD_ROOT_SIZE and MAXDSIZ=(1024UL*1024*1024); MAXSSIZ=(512UL*1024*1024); DFLDSIZ=(1024UL*1024*1024), panic still. From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 09:35:25 2008 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 7585B16A404 for ; Fri, 22 Feb 2008 09:35:25 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 3BEC913C461 for ; Fri, 22 Feb 2008 09:35:24 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (F72f4.f.ppp-pool.de [195.4.114.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id A25E3128844 for ; Fri, 22 Feb 2008 10:35:14 +0100 (CET) Received: from cesar.sz.vwsoft.com (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 68E813F64E for ; Fri, 22 Feb 2008 10:33:36 +0100 (CET) Message-ID: <47BE973D.8010607@vwsoft.com> Date: Fri, 22 Feb 2008 10:34:53 +0100 From: Volker User-Agent: Thunderbird 2.0.0.9 (X11/20080125) MIME-Version: 1.0 To: FreeBSD Stable X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1204277623.43506@8s44pIuQls+oFRWcDastTQ X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Subject: arp: unknown hardware address 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, 22 Feb 2008 09:35:25 -0000 Hi! This morning, I found this in the daily periodic mail from a RELENG_7 machine: +arp: unknown hardware address format (0x0000) +arp: unknown hardware address format (0x0000) +arp: unknown hardware address format (0x0000) +arp: unknown hardware address format (0x0000) +arp: unknown hardware address format (0x0000) I checked my yesterdays' logs and found: Feb 21 20:56:39 bellona dhcpd: DHCPREQUEST for 192.168.178.20 from 00:18:de:a4:b 8:6a via aue0: wrong network. Feb 21 20:56:39 bellona dhcpd: DHCPNAK on 192.168.178.20 to 00:18:de:a4:b8:6a vi a aue0 Feb 21 20:56:40 bellona kernel: arp: unknown hardware address format (0x0000) Feb 21 20:56:40 bellona kernel: Feb 21 20:56:40 bellona kernel: arp: unknown hardware address format (0x0000) Feb 21 20:56:42 bellona kernel: arp: unknown hardware address format (0x0000) Feb 21 20:56:47 bellona last message repeated 3 times Feb 21 20:56:51 bellona dhcpd: DHCPDISCOVER from 00:18:de:a4:b8:6a via aue0 Feb 21 20:56:51 bellona kernel: Feb 21 20:56:51 bellona dhcpd: icmp_echorequest 192.168.20.249: Operation not permitted Feb 21 20:56:52 bellona dhcpd: DHCPOFFER on 192.168.20.249 to 00:18:de:a4:b8:6a (lp4) via aue0 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #8: Sun Feb 17 19:13:08 CET 2008 The network the dhcp client was requesting (192.168.178.20) is not mine, dhcpd rejected that address and offered another one. But why does FreeBSD complain about the bad hardware address? Any explanations? Volker From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 10:42:28 2008 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 4254816A503 for ; Fri, 22 Feb 2008 10:42:28 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from mail.demax.sk (mail.demax.sk [213.215.102.234]) by mx1.freebsd.org (Postfix) with ESMTP id BCD8813C469 for ; Fri, 22 Feb 2008 10:42:27 +0000 (UTC) (envelope-from sebosik@demax.sk) Received: from mail.demax.sk (localhost [127.0.0.1]) by nod32.demax.sk (Postfix) with ESMTP id BA0ED42AEA; Fri, 22 Feb 2008 11:09:23 +0100 (CET) X-Virus-Scanner: This message was checked by NOD32 Antivirus system NOD32 for Linux Mail Server. For more information on NOD32 Antivirus System, please, visit our website: http://www.nod32.com/. Received: from sql.demax.sk (sql.demax.sk [213.215.102.236]) by mail.demax.sk (Postfix) with ESMTP id 8A36042AC7; Fri, 22 Feb 2008 11:09:23 +0100 (CET) Received: from 158.193.82.109 (SquirrelMail authenticated user sebosik) by webmail.demax.sk with HTTP; Fri, 22 Feb 2008 11:09:23 +0100 (CET) Message-ID: <53113.158.193.82.109.1203674963.squirrel@webmail.demax.sk> In-Reply-To: <47BE973D.8010607@vwsoft.com> References: <47BE973D.8010607@vwsoft.com> Date: Fri, 22 Feb 2008 11:09:23 +0100 (CET) From: sebosik@demax.sk To: "Volker" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-2 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org Subject: Re: arp: unknown hardware address 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, 22 Feb 2008 10:42:28 -0000 Hi I`ve got the same messages on FreeBSD 6-STABLE (tracked every second week). I think that somebody is using default MAC address on network. Best regards > Hi! > > This morning, I found this in the daily periodic mail from a RELENG_7 > machine: > > +arp: unknown hardware address format (0x0000) > +arp: unknown hardware address format (0x0000) > +arp: unknown hardware address format (0x0000) > +arp: unknown hardware address format (0x0000) > +arp: unknown hardware address format (0x0000) > > I checked my yesterdays' logs and found: > > Feb 21 20:56:39 bellona dhcpd: DHCPREQUEST for 192.168.178.20 from > 00:18:de:a4:b > 8:6a via aue0: wrong network. > Feb 21 20:56:39 bellona dhcpd: DHCPNAK on 192.168.178.20 to > 00:18:de:a4:b8:6a vi > a aue0 > Feb 21 20:56:40 bellona kernel: arp: unknown hardware address format > (0x0000) > Feb 21 20:56:40 bellona kernel: Feb 21 20:56:40 bellona kernel: arp: > unknown hardware address format (0x0000) > Feb 21 20:56:42 bellona kernel: arp: unknown hardware address format > (0x0000) > Feb 21 20:56:47 bellona last message repeated 3 times > Feb 21 20:56:51 bellona dhcpd: DHCPDISCOVER from 00:18:de:a4:b8:6a via > aue0 > Feb 21 20:56:51 bellona kernel: Feb 21 20:56:51 bellona dhcpd: > icmp_echorequest 192.168.20.249: Operation not permitted > Feb 21 20:56:52 bellona dhcpd: DHCPOFFER on 192.168.20.249 to > 00:18:de:a4:b8:6a (lp4) via aue0 > > > 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #8: Sun Feb 17 19:13:08 CET 2008 > > The network the dhcp client was requesting (192.168.178.20) is not mine, > dhcpd rejected that address and offered another one. But why does > FreeBSD complain about the bad hardware address? > > Any explanations? > > Volker > _______________________________________________ > 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" > --- Jan Sebosik sebosik@demax.sk From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 11:42:17 2008 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 DBC8816A400 for ; Fri, 22 Feb 2008 11:42:17 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.de [194.25.134.20]) by mx1.freebsd.org (Postfix) with ESMTP id A4B1913C46E for ; Fri, 22 Feb 2008 11:42:17 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd28.aul.t-online.de by mailout08.sul.t-online.com with smtp id 1JSWIC-00030a-03; Fri, 22 Feb 2008 12:42:16 +0100 Received: from localhost (b7DvC4Z1wtITm6fA0fyGQ0eKWVPTS29Q83itfxpPIHyZ0Q2My113tzKsJ2HiDc0bTb+xRnONqH@[91.21.74.205]) by fwd28.t-online.de with esmtp id 1JSWHw-0S6pyS0; Fri, 22 Feb 2008 12:42:00 +0100 Date: Fri, 22 Feb 2008 12:41:59 +0100 From: Oliver Herold To: freebsd-stable@freebsd.org Message-ID: <20080222114159.GA8167@asgard.home> Mail-Followup-To: Oliver Herold , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline X-PGP-Key: http://www.fixmbr.de/wp-content/uploads/oliver-gpg-key.asc User-Agent: Mutt/1.5.17 (2007-11-01) X-ID: b7DvC4Z1wtITm6fA0fyGQ0eKWVPTS29Q83itfxpPIHyZ0Q2My113tzKsJ2HiDc0bTb+xRnONqH X-TOI-MSGID: 5cd562a0-3444-413a-be5d-fd87eb3f68d3 Subject: serious problem with if_rum 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, 22 Feb 2008 11:42:17 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there is some serious problem with driver if_rum. Maybe there is some work = arround=20 I'm not aware of, but sacrificing encryption isn't an adequate path and to = some degree impossible in different places. I did send the first PR from the url= s below. http://www.freebsd.org/cgi/query-pr.cgi?pr=3D120966 http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dusb/120873 http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dusb/119945 Cheers, Oliver=20 --=20 It was kinda like stuffing the wrong card in a computer, when you're stickin' those artificial stimulants in your arm. -- Dion, noted computer scientist --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAke+tQYACgkQbZFSiGSuUEi05wCfZr3Rvfr5P+DKeUio5hRKXqJq lowAnjOc3swELR54sxxuDCS3+teVk09o =4J3H -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 12:07:01 2008 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 3F8B416A400 for ; Fri, 22 Feb 2008 12:07:01 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id CE4AB13C457 for ; Fri, 22 Feb 2008 12:07:00 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id m1MC6vXd016998; Fri, 22 Feb 2008 12:06:57 GMT Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JSWg5-0004eq-63; Fri, 22 Feb 2008 12:06:57 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m1MC6sIr073304; Fri, 22 Feb 2008 12:06:54 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m1MC6slU073303; Fri, 22 Feb 2008 12:06:54 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Oliver Herold In-Reply-To: <20080222114159.GA8167@asgard.home> References: <20080222114159.GA8167@asgard.home> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 22 Feb 2008 12:06:51 +0000 Message-Id: <1203682011.68767.7.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-stable@freebsd.org Subject: Re: serious problem with if_rum 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, 22 Feb 2008 12:07:01 -0000 On Fri, 2008-02-22 at 12:41 +0100, Oliver Herold wrote: > Hi > > there is some serious problem with driver if_rum. Maybe there is some work arround > I'm not aware of, but sacrificing encryption isn't an adequate path and to some > degree impossible in different places. I did send the first PR from the urls below. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=120966 > http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/120873 > http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/119945 Does the suggested change in the third PR help? Also, can you recompile your kernel with options GDB and KDB, and when it panics type "bt" at the debugger prompt? Gavin From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 13:46:46 2008 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 20C9316A405 for ; Fri, 22 Feb 2008 13:46:46 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.de [194.25.134.85]) by mx1.freebsd.org (Postfix) with ESMTP id B643213C45E for ; Fri, 22 Feb 2008 13:46:45 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd32.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1JSYEe-00083P-00; Fri, 22 Feb 2008 14:46:44 +0100 Received: from localhost (GMv6UGZcQt1-brc0ksdOvU-UY1eFFN8CpCydW9iBmrIYXIA97Lb6Kaacz82c9eiM+uKVt1lWCK@[91.21.74.205]) by fwd32.t-online.de with esmtp id 1JSYE9-0T7oAq0; Fri, 22 Feb 2008 14:46:13 +0100 Date: Fri, 22 Feb 2008 14:46:13 +0100 From: Oliver Herold To: freebsd-stable@freebsd.org Message-ID: <20080222134613.GA1273@asgard.home> Mail-Followup-To: Oliver Herold , freebsd-stable@freebsd.org References: <20080222114159.GA8167@asgard.home> <1203682011.68767.7.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <1203682011.68767.7.camel@buffy.york.ac.uk> X-PGP-Key: http://www.fixmbr.de/wp-content/uploads/oliver-gpg-key.asc User-Agent: Mutt/1.5.17 (2007-11-01) X-ID: GMv6UGZcQt1-brc0ksdOvU-UY1eFFN8CpCydW9iBmrIYXIA97Lb6Kaacz82c9eiM+uKVt1lWCK X-TOI-MSGID: 14b538c8-4ac2-426a-9c0a-57a0450e4d60 Subject: Re: serious problem with if_rum 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, 22 Feb 2008 13:46:46 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Gavin Atkinson wrote: > On Fri, 2008-02-22 at 12:41 +0100, Oliver Herold wrote: > > Hi > >=20 > > there is some serious problem with driver if_rum. Maybe there is some w= ork arround=20 > > I'm not aware of, but sacrificing encryption isn't an adequate path and= to some > > degree impossible in different places. I did send the first PR from the= urls below. > >=20 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D120966 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dusb/120873 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dusb/119945 >=20 > Does the suggested change in the third PR help? Also, can you recompile > your kernel with options GDB and KDB, and when it panics type "bt" at > the debugger prompt? >=20 > Gavin Hi I tried it with the kernel options but to no avail, I couldn't enter any= thing. Furthermore I tried the patch (deleting of the specified line) but again to no avail, t= his time there was no kernel panic, but a hard reset. Last not least there is a massive performan= ce drop before the panic/reset. I could test it with another nic (Atheros) at my second machine (same time,= same server), so there isn't any problem with the server or the router. Oliver --=20 I have hardly ever known a mathematician who was capable of reasoning. -- Plato --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAke+0iQACgkQbZFSiGSuUEhs+QCfeSYruhR54FyzLKi8T9MjsDTm hLIAn3rTGjYB5IFMzpfhvifvwFEYQLLj =pDEQ -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 14:29:09 2008 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 D9B3A16A401; Fri, 22 Feb 2008 14:29:09 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id AA77213C4EA; Fri, 22 Feb 2008 14:29:09 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id m1MET2NY096167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Feb 2008 09:29:02 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: freebsd-current@freebsd.org, freebsd-stable Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-sqWt6IoV40Qa3lSJXSgZ" Organization: U. Buffalo CSE Department Date: Fri, 22 Feb 2008 09:29:02 -0500 Message-Id: <1203690542.10026.19.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: Subject: FreeBSD 7.0-RC3 (for amd64/i386 only) 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: Fri, 22 Feb 2008 14:29:09 -0000 --=-sqWt6IoV40Qa3lSJXSgZ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable We're doing a "mini-RC3" to encourage testing of the Highpoint driver (hptrr) backout. Testing of 7.0-RC2 showed there were problems with the driver update done between RC1 and RC2. Because it's a "mini-RC" targetted at testing of one particular thing we have not bothered with setting up FreeBSD Update. You can use the normal cvsup-and-build method of doing an update for machines that are already up and running (branch tag RELENG_7_0) or install from scratch using the ISOs available on the FTP sites. If those who experienced problems related to the hptrr driver update could let us know one way or another whether or not you are still having problems with it that would be appreciated. Thanks. Sums for the ISOs: MD5 (7.0-RC3-amd64-bootonly.iso) =3D f2a546a58026651069d2e332df1c9861 MD5 (7.0-RC3-amd64-disc1.iso) =3D 1f1ab0c6006150f075acf0c14aa381e4 MD5 (7.0-RC3-amd64-disc2.iso) =3D 172d0e28a283d6ca6c4334887a80c10b MD5 (7.0-RC3-amd64-disc3.iso) =3D 20bbfadcf4c77466541f817ded520a03 MD5 (7.0-RC3-amd64-docs.iso) =3D 3bd7f636bce99a8276af91b512efe9d1 MD5 (7.0-RC3-amd64-livefs.iso) =3D cef35c58ef525818cb7a451db670312e MD5 (7.0-RC3-i386-bootonly.iso) =3D a201126726b3ce8f0c64ee5bd58c64f4 MD5 (7.0-RC3-i386-disc1.iso) =3D b2424432eaca4741a9df0d87165c1285 MD5 (7.0-RC3-i386-disc2.iso) =3D 51646452d777fbe875462384e924c39a MD5 (7.0-RC3-i386-disc3.iso) =3D 23450ec1bfaeeeda3945201975bb117a MD5 (7.0-RC3-i386-docs.iso) =3D 0c6963cf39c63471eeebbdc6494a4e04 MD5 (7.0-RC3-i386-livefs.iso) =3D b08c3761085e8ad63fe220f9ef279e22 SHA256 (7.0-RC3-amd64-bootonly.iso) =3D f71a8ee8151f72bcb91e6ce8d06eadccded= 333fac0ac617dc9cd4b9d5ab27e7c SHA256 (7.0-RC3-amd64-disc1.iso) =3D 7f8248711909fac0fef1a4be4d8845f69e32cc= 27dfc5bf2998f3548677d20068 SHA256 (7.0-RC3-amd64-disc2.iso) =3D bb7a426dc8e73f3cfa8fb9849d8b64423c5f3d= 765d33c03492b14d5ee362422e SHA256 (7.0-RC3-amd64-disc3.iso) =3D 6918c68ee49fa3d6382e380d36018438b4060e= b6637c48712c8df69eb03d12b3 SHA256 (7.0-RC3-amd64-docs.iso) =3D fa7c714cc7aac4ba02d538b2d08fd276c6ff212= dedb34d9cf275885a7ce3044a SHA256 (7.0-RC3-amd64-livefs.iso) =3D 078a21078904caf1f3a205031432a018ead5f= fd8834f4348b31e148ae162f186 SHA256 (7.0-RC3-i386-bootonly.iso) =3D 886fde7fc85cec484c03f5ac53ce842133a8= 1853418bffe429fcf13f5699fd08 SHA256 (7.0-RC3-i386-disc1.iso) =3D febbbdf5e632aacf73ef118d0310c8bbc0360d8= 51e3c5986301dd01bb7994690 SHA256 (7.0-RC3-i386-disc2.iso) =3D e16e6141f5f2e97024ad28215e9f8c70b4232b6= 63859b74538061908a2e1bb2e SHA256 (7.0-RC3-i386-disc3.iso) =3D 994ef5741f74c805c106bcdf1ebb2ef7b23bddd= fa2667f2df9f64169acb4b434 SHA256 (7.0-RC3-i386-docs.iso) =3D ce9a2c6b4b918fc19203cb8ce3bcb427b6957a28= a3c34925d66c6ecb12845ec7 SHA256 (7.0-RC3-i386-livefs.iso) =3D 04e79cd45a6498ffc71a033f3d4e6f2dcb34d1= 07f371a349d8db74edd7568712 --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-sqWt6IoV40Qa3lSJXSgZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHvtwk/G14VSmup/YRAsv7AJ440h9Td5MwktLO5U4Q0E/qBzV1cACffR6b UXJ5/tN5tTUnqQNVk1FqwC0= =8m1o -----END PGP SIGNATURE----- --=-sqWt6IoV40Qa3lSJXSgZ-- From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 15:11:53 2008 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 E32D316A404 for ; Fri, 22 Feb 2008 15:11:53 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 77F9B13C45E for ; Fri, 22 Feb 2008 15:11:52 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A4E0A.dip.t-dialin.net [84.154.78.10]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m1MFBQka068109; Fri, 22 Feb 2008 16:11:27 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m1MFEIFp049869; Fri, 22 Feb 2008 16:14:19 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m1MFE38O049367; Fri, 22 Feb 2008 16:14:13 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802221514.m1MFE38O049367@fire.js.berklix.net> To: dirk.meyer@dinoex.sub.org (Dirk Meyer) In-reply-to: References: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> Comments: In-reply-to dirk.meyer@dinoex.sub.org (Dirk Meyer) message dated "Fri, 22 Feb 2008 09:34:28 +0100." Date: Fri, 22 Feb 2008 16:14:03 +0100 From: "Julian H. Stacey" Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 update and process freeze 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, 22 Feb 2008 15:11:54 -0000 Dirk Meyer wrote: > Gil Bidon schrieb:, > > > Since i've updated my machine to FreeBSD 6.3 some process randomly start > > using 100% CPU or are locked to STOP state (in top). > > > > Is there a known solution / patch ? Except the rollback :) > > I see this for mail/antivirus-milter too. > But I have not been able to trace it down, > the machine is remote and locks up fully. > On normal load it runs fine, > Maybe an resource-limit is not enforced? > > It looks similar to the nagios thread problem. > > kind regards Dirk Watch out for evil mailman ! Default settings in crontab have locked up servers for 5 years http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/ports/gen/mail/mailman/ Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 16:48:47 2008 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 14D6A16A400 for ; Fri, 22 Feb 2008 16:48:47 +0000 (UTC) (envelope-from louie@transsys.com) Received: from ringworld.transsys.com (ringworld.transsys.com [144.202.0.15]) by mx1.freebsd.org (Postfix) with ESMTP id E90B513C4E5 for ; Fri, 22 Feb 2008 16:48:46 +0000 (UTC) (envelope-from louie@transsys.com) Received: from PM-G5.transsys.com (c-69-141-143-164.hsd1.nj.comcast.net [69.141.143.164]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by ringworld.transsys.com (Postfix) with ESMTP id 2E3FC5C5E; Fri, 22 Feb 2008 11:17:33 -0500 (EST) From: Louis Mamakos To: sebosik@demax.sk In-Reply-To: <53113.158.193.82.109.1203674963.squirrel@webmail.demax.sk> X-Priority: 3 (Normal) References: <47BE973D.8010607@vwsoft.com> <53113.158.193.82.109.1203674963.squirrel@webmail.demax.sk> Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Fri, 22 Feb 2008 11:17:32 -0500 X-Mailer: Apple Mail (2.919.2) Cc: Volker , freebsd-stable@freebsd.org Subject: Re: arp: unknown hardware address 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, 22 Feb 2008 16:48:47 -0000 The Address Resolution Protocol (ARP) contains an address format identifiers as part of the frame format. This is so it could be used as generalized solution to discover different types of addresses on a broadcast network. For IP, the address format in the frame ought to be (as I recall) 0x0800 to denote an IPv4 protocol addresses and 0x0001 to denote Ethernet hardware addresses. It seems like some other host on your network has likely emitted malformed ARP messages. UTSL: /usr/src/sys/netinet/if_ether.c:arpintr() louie On Feb 22, 2008, at 5:09 AM, sebosik@demax.sk wrote: > Hi > > I`ve got the same messages on FreeBSD 6-STABLE (tracked every second > week). I think that somebody is using default MAC address on network. > > Best regards > >> Hi! >> >> This morning, I found this in the daily periodic mail from a RELENG_7 >> machine: >> >> +arp: unknown hardware address format (0x0000) >> +arp: unknown hardware address format (0x0000) >> +arp: unknown hardware address format (0x0000) >> +arp: unknown hardware address format (0x0000) >> +arp: unknown hardware address format (0x0000) >> >> I checked my yesterdays' logs and found: >> >> Feb 21 20:56:39 bellona dhcpd: DHCPREQUEST for 192.168.178.20 from >> 00:18:de:a4:b >> 8:6a via aue0: wrong network. >> Feb 21 20:56:39 bellona dhcpd: DHCPNAK on 192.168.178.20 to >> 00:18:de:a4:b8:6a vi >> a aue0 >> Feb 21 20:56:40 bellona kernel: arp: unknown hardware address format >> (0x0000) >> Feb 21 20:56:40 bellona kernel: Feb 21 20:56:40 bellona kernel: arp: >> unknown hardware address format (0x0000) >> Feb 21 20:56:42 bellona kernel: arp: unknown hardware address format >> (0x0000) >> Feb 21 20:56:47 bellona last message repeated 3 times >> Feb 21 20:56:51 bellona dhcpd: DHCPDISCOVER from 00:18:de:a4:b8:6a >> via >> aue0 >> Feb 21 20:56:51 bellona kernel: Feb 21 20:56:51 bellona dhcpd: >> icmp_echorequest 192.168.20.249: Operation not permitted >> Feb 21 20:56:52 bellona dhcpd: DHCPOFFER on 192.168.20.249 to >> 00:18:de:a4:b8:6a (lp4) via aue0 >> >> >> 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #8: Sun Feb 17 19:13:08 CET >> 2008 >> >> The network the dhcp client was requesting (192.168.178.20) is not >> mine, >> dhcpd rejected that address and offered another one. But why does >> FreeBSD complain about the bad hardware address? >> >> Any explanations? >> >> Volker >> _______________________________________________ >> 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 >> " >> > > > --- > Jan Sebosik > sebosik@demax.sk > > _______________________________________________ > 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 Feb 22 17:18:59 2008 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 79E2816A409; Fri, 22 Feb 2008 17:18:59 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 44C7313C458; Fri, 22 Feb 2008 17:18:58 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m1MHIsPx068700; Fri, 22 Feb 2008 12:18:54 -0500 (EST) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m1MHIrL6029816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Feb 2008 12:18:53 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <200802221718.m1MHIrL6029816@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 22 Feb 2008 12:18:56 -0500 To: Ken Smith , freebsd-current@freebsd.org, freebsd-stable From: Mike Tancsa In-Reply-To: <1203690542.10026.19.camel@bauer.cse.buffalo.edu> References: <1203690542.10026.19.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: FreeBSD 7.0-RC3 (for amd64/i386 only) 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: Fri, 22 Feb 2008 17:18:59 -0000 At 09:29 AM 2/22/2008, Ken Smith wrote: >If those who experienced problems related to the hptrr driver update >could let us know one way or another whether or not you are still having >problems with it that would be appreciated. Hi, I just did a fresh test install with RC3 on a HighPoint hptrr controller with 2 disks in RAID1 config and all looks good. hpoint# dmesg | grep hpt hptrr: HPT RocketRAID controller driver v1.1 (Feb 20 2008 18:33:35) hptrr0: port 0x2000-0x20ff mem 0x30100000-0x301fffff irq 16 at device 0.0 on pci1 hptrr: adapter at PCI 1:0:0, IRQ 16 hptrr: start channel [0,0] hptrr: start channel [0,1] hptrr: start channel [0,2] hptrr: start channel [0,3] hptrr: channel [0,2] started successfully hptrr: channel [0,3] started successfully hptrr: channel [0,0]: failed to perform Hard Reset hptrr: channel [0,1]: failed to perform Hard Reset hptrr0: [GIANT-LOCKED] hptrr0: [ITHREAD] da0 at hptrr0 bus 0 target 0 lun 0hpoint# hptrr0@pci0:1:0:0: class=0x010000 card=0x11ab11ab chip=0x23101103 rev=0x02 hdr=0x00 vendor = 'Triones Technologies Inc. (HighPoint)' device = 'RocketRAID 231x SATA Controller' class = mass storage subclass = SCSI cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 10[60] = PCI-Express 1 legacy endpoint hpoint# dd if=/dev/zero of=/tmp/junk bs=1024k count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 1.415491 secs (74078613 bytes/sec) hpoint# hpoint# uname -a FreeBSD hpoint.sentex.ca 7.0-RC3 FreeBSD 7.0-RC3 #0: Wed Feb 20 18:34:00 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 hpoint# From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 01:49:45 2008 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 D6FD716A408 for ; Sat, 23 Feb 2008 01:49:45 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from outbound.icp-qv1-irony-out1.iinet.net.au (outbound.icp-qv1-irony-out1.iinet.net.au [203.59.1.108]) by mx1.freebsd.org (Postfix) with ESMTP id 5D2C213C459 for ; Sat, 23 Feb 2008 01:49:44 +0000 (UTC) (envelope-from lstewart@freebsd.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4HALICv0fSVCQt/2dsb2JhbACMBqJl X-IronPort-AV: E=Sophos;i="4.25,393,1199631600"; d="scan'208";a="290069082" Received: from unknown (HELO newbox.caia.swin.edu.au) ([210.84.36.45]) by outbound.icp-qv1-irony-out1.iinet.net.au with ESMTP; 23 Feb 2008 10:19:40 +0900 Message-ID: <47BF74AB.6040001@freebsd.org> Date: Sat, 23 Feb 2008 12:19:39 +1100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.4 (X11/20070625) MIME-Version: 1.0 To: Dirk Meyer , Gil Bidon References: <2de9b4690802201459y7d916bc9i3a0d5548d3025327@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.3 update and process freeze 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, 23 Feb 2008 01:49:45 -0000 Dirk Meyer wrote: > Gil Bidon schrieb:, > >> Since i've updated my machine to FreeBSD 6.3 some process randomly start >> using 100% CPU or are locked to STOP state (in top). >> >> Is there a known solution / patch ? Except the rollback :) > > I see this for mail/antivirus-milter too. > But I have not been able to trace it down, > the machine is remote and locks up fully. > On normal load it runs fine, > Maybe an resource-limit is not enforced? > > It looks similar to the nagios thread problem. > To add another data point, I've been seeing similar problems as reported in this thread on a server I upgraded 2 weeks ago from 6.2-RELEASE-p10 to 6.3-RELEASE. I run the spamass-milter-0.3.1_3 port with sendmail and since the upgrade, spamass-milter processes would randomly wedge and spin using 100% CPU. I used GDB to attach to a spinning process and got the following backtrace: (gdb) backtrace 0 0x281a8198 in pthread_sigmask () from /lib/libpthread.so.2 1 0x281a8148 in sigprocmask () from /lib/libpthread.so.2 2 0x281b260c in pthread_mutexattr_init () from /lib/libpthread.so.2 3 0x281a52db in fork () from /lib/libpthread.so.2 4 0x0804d944 in ?? () 5 0x0804e0cf in ?? () 6 0x28089d31 in mi_engine () from /usr/lib/libmilter.so.3 7 0x28089427 in mi_engine () from /usr/lib/libmilter.so.3 8 0x28088c15 in mi_handle_session () from /usr/lib/libmilter.so.3 9 0x2808833b in mi_opensocket () from /usr/lib/libmilter.so.3 10 0x281ac3c9 in pthread_create () from /lib/libpthread.so.2 11 0x2826a837 in _ctx_start () from /lib/libc.so.6 Some time on google found these seemingly related links: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-01/msg00570.html http://www.freebsd.org/cgi/query-pr.cgi?pr=119920 My understanding of the way spamass-milter works is that it forks a child for each email it processes, which does make it seem plausible I'm seeing the pthread fork problem. Assuming this is true, the solution I'm currently testing might solve the problem i.e using /etc/libmap.conf to globally map libpthread to libthr using the following line: libpthread.so.2 libthr.so.2 You of course have to restart all the processes that link against libpthread.so.2 in order for the libmap.conf change to take effect. I only made the change and restarted the processes a couple of days ago so I won't know for a week or two whether it has fixed the problem. So far everything is working as it did before so nothing appears to have regressed since the change. Cheers, Lawrence From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 12:07:18 2008 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 5D61E16A402 for ; Sat, 23 Feb 2008 12:07:18 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.de [194.25.134.81]) by mx1.freebsd.org (Postfix) with ESMTP id 1323813C442 for ; Sat, 23 Feb 2008 12:07:17 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from fwd33.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1JSt9w-0000BI-00; Sat, 23 Feb 2008 13:07:16 +0100 Received: from localhost (GMvkuwZYZttPnirtmowoDJjY0rqIBOfSJmOENYMHwhYJO5t1UPgN4NT6x7YTjAmJ3OxuGrPvjA@[91.21.95.217]) by fwd33.t-online.de with esmtp id 1JSt9e-0lwHdg0; Sat, 23 Feb 2008 13:06:58 +0100 Date: Sat, 23 Feb 2008 13:06:58 +0100 From: Oliver Herold To: freebsd-stable@freebsd.org Message-ID: <20080223120658.GA30178@asgard.home> Mail-Followup-To: Oliver Herold , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline X-PGP-Key: http://www.fixmbr.de/wp-content/uploads/oliver-gpg-key.asc User-Agent: Mutt/1.5.17 (2007-11-01) X-ID: GMvkuwZYZttPnirtmowoDJjY0rqIBOfSJmOENYMHwhYJO5t1UPgN4NT6x7YTjAmJ3OxuGrPvjA X-TOI-MSGID: 27c14539-a87e-4d47-80d7-b8425e1fb7cb Subject: FreeBSD 7, Razer Copperhead mouse patch 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, 23 Feb 2008 12:07:18 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long time, but after some period it stopped working. This patch from Uwe Grohnwaldt: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dusb/118670 fixes this wrong behaviour (it's detected as keyboard) and makes the mouse work in FreeBSD 7 again. Would be imho a nice addition for=20 RELENG_7 (stable) or even Release. Cheers, Oliver --=20 GREAT MOMENTS IN AMERICAN HISTORY (#17): On November 13, Felix Unger was asked to remove himself from his place of residence. --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkfADGEACgkQbZFSiGSuUEhMQwCghorVZ1Cyo6S9dAeWTaMW0auR tHwAnibCOZss3m9PwqY0vlmHf0I3xv26 =SJn8 -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 12:14:22 2008 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 3DAE116A406 for ; Sat, 23 Feb 2008 12:14:22 +0000 (UTC) (envelope-from arun.balakrishnan@wipro.com) Received: from wipro-blr-out01.wipro.com (wipro-blr-out01.wipro.com [203.91.198.74]) by mx1.freebsd.org (Postfix) with ESMTP id 83B2E13C448 for ; Sat, 23 Feb 2008 12:14:21 +0000 (UTC) (envelope-from arun.balakrishnan@wipro.com) X-AuditID: cb5bdd57-adf37bb000000741-d8-47c0171d213b Received: from blr-ec-bh02.wipro.com (unknown [10.201.50.92]) by wipro-blr-out01.wipro.com (Symantec Mail Security) with ESMTP id 5F2824E4004 for ; Sat, 23 Feb 2008 18:22:45 +0530 (IST) Received: from BLR-SJP-MBX01.wipro.com ([10.101.50.182]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 23 Feb 2008 17:28:10 +0530 Received: from [127.0.0.1] ([10.115.5.159]) by BLR-SJP-MBX01.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 23 Feb 2008 17:27:20 +0530 Message-ID: <47C00A1B.5030708@wipro.com> Date: Sat, 23 Feb 2008 17:27:15 +0530 From: "Arun Balakrishnan (WT01 - Computing, Storage & Software Products)" User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) To: freebsd-stable@freebsd.org content-transfer-encoding: 7bit X-OriginalArrivalTime: 23 Feb 2008 11:57:20.0368 (UTC) FILETIME=[3E6A7700:01C87613] X-Brightmail-Tracker: AAAAAA== MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Memory Leak under FreeBSD 6.0 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: Sat, 23 Feb 2008 12:14:22 -0000 Hi, We are currently working on a project wherein we are porting a library from GNU/Linux to FreeBSD 6.0 - RELEASE 32-bit and 64-bit. As part of the standard memory leak tests, we noticed that the ported library is leaking memory. After lots of analysis we found something very strange. Just repeatedly loading and unloading our library was itself throwing up a leak. We are able to reproduce a similar leak using the following steps: 1. SimpleLib.cpp - Simple dummy library 2. LibLoader.cpp - Utility to repeatedly load the library 3. Compile as mentioned 4. Run under Valgrind for multiple times (31 times in our example. Hard coded for simpilicity) =================SimpleLib.cpp=================== #include #include class CLeaker { public: CLeaker() { }; virtual ~CLeaker() { }; }; CLeaker obj; ================LibLoader.cpp====================== #include "stdio.h" #include "dlfcn.h" #include #include #include int main() { int i = 0; int loop = 31; while (i 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 61FF516A400 for ; Sat, 23 Feb 2008 16:13:58 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (neilhoggarth-2.dsl.easynet.co.uk [217.206.124.94]) by mx1.freebsd.org (Postfix) with ESMTP id A3F8513C45D for ; Sat, 23 Feb 2008 16:13:57 +0000 (UTC) (envelope-from neil@hoggarth.me.uk) Received: from neilhoggarth-2.dsl.easynet.co.uk (localhost [127.0.0.1]) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2) with ESMTP id m1NFwGig001404 for ; Sat, 23 Feb 2008 15:58:16 GMT (envelope-from neil@hoggarth.me.uk) Received: from localhost (njh@localhost) by neilhoggarth-2.dsl.easynet.co.uk (8.14.2/8.14.2/Submit) with ESMTP id m1NFwFE7001401 for ; Sat, 23 Feb 2008 15:58:16 GMT (envelope-from neil@hoggarth.me.uk) X-Authentication-Warning: neilhoggarth-2.dsl.easynet.co.uk: njh owned process doing -bs Date: Sat, 23 Feb 2008 15:58:15 +0000 (GMT) From: Neil Hoggarth X-X-Sender: njh@neilhoggarth-2.dsl.easynet.co.uk To: freebsd-stable@freebsd.org Message-ID: User-Agent: Alpine 1.00 (BSF 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: RELENG_7 - Witness warnings re USB audio 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, 23 Feb 2008 16:13:58 -0000 I'm running RELENG_7 on a dual-core AMD64 system, with a kernel that is configured the same as GENERIC but with the WITNESS and INVARIANTS options added. Warnings of the form shown below are getting logged when I play multimedia files with mplayer. Is this anything to be concerned about? Should I open a PR? uma_zalloc_arg: zone "4096" with the following non-sleepable locks held: exclusive sleep mutex pcm0:play:dsp0.p0 (pcm play channel) r = 0 (0xffffff00033017c0) locked @ /usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/vchan.c:448 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a witness_warn() at witness_warn+0x248 uma_zalloc_arg() at uma_zalloc_arg+0x33a malloc() at malloc+0x8a usbd_alloc_buffer() at usbd_alloc_buffer+0x8a uaudio_chan_alloc_buffers() at uaudio_chan_alloc_buffers+0x4d uaudio_trigger_output() at uaudio_trigger_output+0x3b ua_chan_trigger() at ua_chan_trigger+0x7a chn_trigger() at chn_trigger+0x117 chn_notify() at chn_notify+0xd5 vchan_trigger() at vchan_trigger+0x95 chn_trigger() at chn_trigger+0x117 chn_write() at chn_write+0x11b dsp_write() at dsp_write+0x2ef devfs_write_f() at devfs_write_f+0x9c dofilewrite() at dofilewrite+0x85 kern_writev() at kern_writev+0x4c write() at write+0x54 syscall() at syscall+0x1ce Xfast_syscall() at Xfast_syscall+0xab --- syscall (4, FreeBSD ELF64, write), rip = 0x80311fdcc, rsp = 0x7fffffffd6b8, rbp = 0x9485471f --- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 16:49:57 2008 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 19E3716A402 for ; Sat, 23 Feb 2008 16:49:57 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from smtpi2.ngi.it (smtpi2.ngi.it [88.149.128.21]) by mx1.freebsd.org (Postfix) with ESMTP id 89FCA13C44B for ; Sat, 23 Feb 2008 16:49:56 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (88-149-173-206.static.ngi.it [88.149.173.206]) by smtpi2.ngi.it (8.13.8/8.13.8) with ESMTP id m1NFkkZs013585 for ; Sat, 23 Feb 2008 16:46:46 +0100 Received: from megatron.madpilot.net (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 6C468130C74; Sat, 23 Feb 2008 16:46:45 +0100 (CET) Received: from anakin.madpilot.net (anakin.madpilot.net [172.24.42.10]) by megatron.madpilot.net (Postfix) with ESMTP id 48000130C6E; Sat, 23 Feb 2008 16:46:45 +0100 (CET) Message-ID: <47C03FE5.8030703@madpilot.net> Date: Sat, 23 Feb 2008 16:46:45 +0100 From: Guido Falsi User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Eirik_=D8verby?= References: <79029E40-6E43-4482-8E39-D1DE49C8C53A@anduin.net> <200802122311.43247.doconnor@gsoft.com.au> <5B010AC7-C292-45E6-A109-20E39B370604@anduin.net> <200802131851.15014.doconnor@gsoft.com.au> <78796912-6D98-4433-A5C9-622854C7DFB2@anduin.net> In-Reply-To: <78796912-6D98-4433-A5C9-622854C7DFB2@anduin.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: FreeBSD Stable Subject: Re: UFS snapshot weirdness 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, 23 Feb 2008 16:49:57 -0000 Eirik Øverby wrote: > > I read somewhere else about NFS issues on 7-RC* where snapshots have > been used. In particular - and this is something I'm seeing too - > changing the exports file or reloading mountd gives the following in > messages log: > > Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /tmp: > Invalid argument > Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /usr: > Cross-device link > Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /var: > Cross-device link > Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for > /export/home: Cross-device link > Feb 19 18:58:09 anduin mountd[38867]: can't delete exports for /opt: > Cross-device link > > Can this be related? I'm starting to worry here - what will be the > long-term consequences if snapshots are stuck around in this "invisible" > state? > I have been experiencing these too. But it looks more like a bug in mountd, since it shows up only is snapshots are created with mount. If snapshots are created with mksnap_ffs this does not seem to show up. I still have to make more in depth experiments, but before experimenting by myself I'd like to have some more informed directions on what to experiment. -- Guido Falsi From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 18:40:09 2008 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 131C816A401 for ; Sat, 23 Feb 2008 18:40:09 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 0245713C469 for ; Sat, 23 Feb 2008 18:40:08 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (unknown [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id 99951654FB for ; Sat, 23 Feb 2008 12:07:24 -0600 (CST) Date: Sat, 23 Feb 2008 12:07:24 -0600 From: Paul Schmehl To: FreeBSD Stable Message-ID: X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Flaky USB behavior on 7.0 RC3 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, 23 Feb 2008 18:40:09 -0000 I just installed STABLE on a brand new Dell, and I'm encountering some strange problems with USB. At first I couldn't get the keyboard or the mouse to work. After some reviewing some of the posts to this list, I tried a trick that had worked for one individual. I plugged a usb extension into a port on the back of the box and into the port on one of my monitors. I then plugged the keyboard and mouse into the monitor. They both worked. After getting xorg up and running, I discovered that the mouse wasn't working. I installed kde, got the virtual display working and then returned to trying to resolve the mouse problem. The only way I could get the mouse to work in the GUI was to add moused_enable="YES" and moused_port="/dev/ums0" to /etc/rc.conf. The non-default mouse setup that works flawlessly on my 6.3 RELENG box doesn't work at all on this box. Unplugging and plugging the mouse cable into various ports, both on the box and on the monitor, has no effect. I don't even get the normal console messages you would expect to see when usb devices are unplugged and plugged into ports. At this point I don't know what to do next. Is there some specific data I could provide that would help track this problem down? Would the output of any particular utilities be useful? I doubt that it matters, but this is a dual dual core processor box with 4GB of memory and cutting edge peripherals such as a Radeon RV610 video card. Yet all those things are working fine. It's just usb that's acting oddly. uname -a FreeBSD utd65257.utdallas.edu 7.0-RC3 FreeBSD 7.0-RC3 #1: Thu Feb 21 11:45:24 CST 2008 root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC i386 CPU: Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz (2660.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 4 real memory = 3487559680 (3325 MB) avail memory = 3408392192 (3250 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 grep usb /var/run/dmesg.boot usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 usb3: on uhci2 usb3: USB revision 1.0 uhub4: on usb3 usb4: on uhci3 usb4: USB revision 1.0 uhub5: on usb4 usb5: on uhci4 usb5: USB revision 1.0 uhub6: on usb5 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub7: on usb6 usbdevs addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: EHCI root hub, Intel addr 2: product 0x2504, vendor 0x0424 addr 3: product 0x4d15, vendor 0x0461 addr 4: product 0x2105, vendor 0x413c addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: EHCI root hub, Intel usbhidctl -a -f /dev/usb usb usb0 usb1 usb2 usb3 usb4 usb5 usb6 usbhidctl -a -f /dev/usb0 usbhidctl: USB_GET_REPORT_DESC usbhidctl -a -f /dev/usb1 usbhidctl: USB_GET_REPORT_DESC usbhidctl -a -f /dev/usb usbhidctl: USB_GET_REPORT_DESC usbhidctl -r -f /dev/usb usbhidctl: USB_GET_REPORT_DESC scanpci pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x8086 device 0x29b0 Intel Corporation DRAM Controller pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x8086 device 0x29b1 Intel Corporation PCI Express Root Port pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x8086 device 0x29b4 Intel Corporation MEI Controller pci bus 0x0000 cardnum 0x03 function 0x02: vendor 0x8086 device 0x29b6 Intel Corporation PT IDER Controller pci bus 0x0000 cardnum 0x03 function 0x03: vendor 0x8086 device 0x29b7 Intel Corporation Serial KT Controller pci bus 0x0000 cardnum 0x19 function 0x00: vendor 0x8086 device 0x10bd Intel Corporation 82566DM-2 Gigabit Network Connection pci bus 0x0000 cardnum 0x1a function 0x00: vendor 0x8086 device 0x2937 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 pci bus 0x0000 cardnum 0x1a function 0x01: vendor 0x8086 device 0x2938 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 pci bus 0x0000 cardnum 0x1a function 0x07: vendor 0x8086 device 0x293c Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 pci bus 0x0000 cardnum 0x1b function 0x00: vendor 0x8086 device 0x293e Intel Corporation 82801I (ICH9 Family) HD Audio Controller pci bus 0x0000 cardnum 0x1c function 0x00: vendor 0x8086 device 0x2940 Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 pci bus 0x0000 cardnum 0x1d function 0x00: vendor 0x8086 device 0x2934 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 pci bus 0x0000 cardnum 0x1d function 0x01: vendor 0x8086 device 0x2935 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 pci bus 0x0000 cardnum 0x1d function 0x02: vendor 0x8086 device 0x2936 Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 pci bus 0x0000 cardnum 0x1d function 0x07: vendor 0x8086 device 0x293a Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 pci bus 0x0000 cardnum 0x1e function 0x00: vendor 0x8086 device 0x244e Intel Corporation 82801 PCI Bridge pci bus 0x0000 cardnum 0x1f function 0x00: vendor 0x8086 device 0x2914 Intel Corporation LPC Interface Controller pci bus 0x0000 cardnum 0x1f function 0x02: vendor 0x8086 device 0x2922 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller pci bus 0x0000 cardnum 0x1f function 0x03: vendor 0x8086 device 0x2930 Intel Corporation 82801I (ICH9 Family) SMBus Controller pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x94c1 ATI Technologies Inc Device unknown pci bus 0x0003 cardnum 0x02 function 0x00: vendor 0x11c1 device 0x5811 Agere Systems FW323 Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 20:01:27 2008 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 A0C3B16A403 for ; Sat, 23 Feb 2008 20:01:27 +0000 (UTC) (envelope-from dan@langille.org) Received: from supernews.unixathome.org (supernews.unixathome.org [216.168.29.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9A513C4D1 for ; Sat, 23 Feb 2008 20:01:27 +0000 (UTC) (envelope-from dan@langille.org) Received: from localhost (localhost [127.0.0.1]) by supernews.unixathome.org (Postfix) with ESMTP id 19FE317039 for ; Sat, 23 Feb 2008 19:44:59 +0000 (GMT) X-Virus-Scanned: amavisd-new at unixathome.org Received: from supernews.unixathome.org ([127.0.0.1]) by localhost (supernews.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xg77snZYLDjw for ; Sat, 23 Feb 2008 19:44:56 +0000 (GMT) Received: from [192.168.1.2] (bast.unixathome.org [72.94.192.69]) by supernews.unixathome.org (Postfix) with ESMTP id 594B21703C for ; Sat, 23 Feb 2008 19:44:56 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v753) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Dan Langille Date: Sat, 23 Feb 2008 14:44:49 -0500 X-Mailer: Apple Mail (2.753) Subject: packet loss with re(4) 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, 23 Feb 2008 20:01:27 -0000 With FreeBSD 6.3-RELEASE, I'm finding significant packet loss (sometimes 85%). If I insert an Intel nic (fxp), there is nil packet loss with similar tests (ping -c 100). re0: port 0xc800-0xc8ff mem 0xf9fff000-0xf9ffffff irq 17 at device 0.0 on pci1 I have seen a thread on current mentioning similar problems: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=862039+0+current/freebsd- current -- Dan Langille -- http://www.langille.org/ dan@langille.org From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 20:32:44 2008 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 25EF216A400 for ; Sat, 23 Feb 2008 20:32:44 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id E9EEE13C46E for ; Sat, 23 Feb 2008 20:32:43 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 89D2040548C; Sat, 23 Feb 2008 21:32:42 +0100 (CET) Message-ID: <47C082E9.5000608@bsdforen.de> Date: Sat, 23 Feb 2008 21:32:41 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20080205) MIME-Version: 1.0 To: Oliver Herold , freebsd-stable@freebsd.org References: <20080223120658.GA30178@asgard.home> In-Reply-To: <20080223120658.GA30178@asgard.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: FreeBSD 7, Razer Copperhead mouse patch 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, 23 Feb 2008 20:32:44 -0000 Oliver Herold wrote: > Hi > > the Razer Copperhead mouse did work in FreeBSD 7 (current) for a long > time, but after some period it stopped working. This patch from Uwe > Grohnwaldt: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/118670 > > fixes this wrong behaviour (it's detected as keyboard) and makes the > mouse work in FreeBSD 7 again. Would be imho a nice addition for > RELENG_7 (stable) or even Release. > > Cheers, Oliver Being a Razer fan and user I totally agree. From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 21:43:27 2008 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 EA21C16A403 for ; Sat, 23 Feb 2008 21:43:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay03.kiev.sovam.com (relay03.kiev.sovam.com [62.64.120.201]) by mx1.freebsd.org (Postfix) with ESMTP id 9762E13C448 for ; Sat, 23 Feb 2008 21:43:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay03.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JT29O-0004zn-1Q; Sat, 23 Feb 2008 23:43:20 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m1NLgqdX020240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Feb 2008 23:42:52 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m1NLhExQ017409; Sat, 23 Feb 2008 23:43:14 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m1NLhDIt017284; Sat, 23 Feb 2008 23:43:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 23 Feb 2008 23:43:13 +0200 From: Kostik Belousov To: "Arun Balakrishnan (WT01 - Computing, Storage & Software Products)" Message-ID: <20080223214313.GF57756@deviant.kiev.zoral.com.ua> References: <47C00A1B.5030708@wipro.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gDKptnH9ef5/6wqy" Content-Disposition: inline In-Reply-To: <47C00A1B.5030708@wipro.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on skuns.kiev.zoral.com.ua X-Scanner-Signature: 6bea4dd5e7a98ea238edf764fb0a12e1 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 2291 [Feb 22 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0278], KAS30/Release Cc: kan@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Memory Leak under FreeBSD 6.0 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: Sat, 23 Feb 2008 21:43:28 -0000 --gDKptnH9ef5/6wqy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 23, 2008 at 05:27:15PM +0530, Arun Balakrishnan (WT01 - Computi= ng, Storage & Software Products) wrote: >=20 > Hi, > We are currently working on a project wherein we are porting a library > from GNU/Linux to FreeBSD 6.0 - RELEASE 32-bit and 64-bit. As part of > the standard memory leak tests, we noticed that the ported library is > leaking memory. After lots of analysis we found something very > strange. Just repeatedly loading and unloading our library was itself > throwing up a leak. We are able to reproduce a similar leak using the > following steps: > 1. SimpleLib.cpp - Simple dummy library > 2. LibLoader.cpp - Utility to repeatedly load the library > 3. Compile as mentioned > 4. Run under Valgrind for multiple times (31 times in our example. > Hard coded for simpilicity) > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DSimpleLib.cpp=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > #include > #include > class CLeaker > { > public: > CLeaker() { }; > virtual ~CLeaker() { }; > }; > CLeaker obj; > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DLibLoader.cpp=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > #include "stdio.h" > #include "dlfcn.h" > #include > #include > #include > int main() > { > int i =3D 0; > int loop =3D 31; > while (i { > i++; > void *handle =3D dlopen(argv[1], RTLD_LAZY); > if ( !handle ) > exit(1); > dlclose(handle); > } > return 0; > } > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D > Compilation: > g++ -shared -Wl,-soname,SimpleLib.so -o SimpleLib.so SimpleLib.cpp -g > g++ -o LibLoader_FreeBSD LibLoader.cpp -g > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D > Execution: > valgrind --trace-pthread=3Dall --show-below-main=3Dyes > --show-reachable=3Dyes --leak-check=3Dyes ./LibLoader_FreeBSD > ./SimpleLib.so > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D > Output: (snipped off irrelevant portions) > =3D=3D1155=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: = 0 from > 0) > =3D=3D1155=3D=3D malloc/free: in use at exit: 520 bytes in 1 blocks. > =3D=3D1155=3D=3D malloc/free: 1 allocs, 0 frees, 520 bytes allocated. > =3D=3D1155=3D=3D For counts of detected errors, rerun with: -v > =3D=3D1155=3D=3D searching for pointers to 1 not-freed blocks. > =3D=3D1155=3D=3D checked 2140912 bytes. > =3D=3D1155=3D=3D > =3D=3D1155=3D=3D 520 bytes in 1 blocks are still reachable in loss rec= ord 1 of > 1 > =3D=3D1155=3D=3D at 0x3C032183: malloc (in > /usr/local/lib/valgrind/vgpreload_memcheck.so) > =3D=3D1155=3D=3D by 0x3C1CB018: (within /lib/libc.so.6) > =3D=3D1155=3D=3D by 0x3C1CB206: __cxa_atexit (in /lib/libc.so.6) > =3D=3D1155=3D=3D by 0x3C1F0898: ??? > =3D=3D1155=3D=3D > =3D=3D1155=3D=3D LEAK SUMMARY: > =3D=3D1155=3D=3D definitely lost: 0 bytes in 0 blocks. > =3D=3D1155=3D=3D possibly lost: 0 bytes in 0 blocks. > =3D=3D1155=3D=3D still reachable: 520 bytes in 1 blocks. > =3D=3D1155=3D=3D suppressed: 0 bytes in 0 blocks. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D > Queries: > 1. As seen in the Valgrind output, there is a 520bytes leak. This > happens only after around 31 loops and keeps increasing. By 100 loops, > the leak goes up to 1560 bytes. In our situation with our library, the > 520bytes leak starts by the third iteration itself and by around 23 > iterations it reaches 5KB. We are really stumped as to what could be > the possible reason for this leak? Where is the malloc called from? > Why only after executing 31 times? Executing the same code under > GNU/Linux does not show any leak even for over 1000 iterations. > 2. While executing this without Valgrind, in another terminal we did a > "ps -Aopid,rss | grep LibLoader_" continuously in a loop and saw that > the RSS (resident set size) field value keeps increasing by 4KB every > now and then. The same experiment on GNU/Linux shows that RSS remains > at the same value. What could be the cause for the ever rising RSS > value? > Any help in this regard would be really helpful. Thanks in advance. > Rgds, > ~Arun The valgrind report points to memory used by the atexit_register() for keeping the information on the functions registered by means of atexit(3) and __cxa_atexit(). See the lib/libc/stdlib/atexit.c. In your (non-compilable) example, __cxa_atexit() is used by shared objects to register the destructor for global objects to be called at the dso unload. The handling of the memory is complicated because atexit() specification states that: - functions shall be called in the reverse order of their registration; - at least 32 functions can be registered with atexit(). The current implementation never frees the struct atexit to try to conform to the requirement of order. The static __atexit0, intended to guarantee success of the first 32 atexit() calls, may not guarantee it, because the space can be consumed by the interleaved __cxa_atexit() instead. Patch below may help with the libc leak. diff --git a/lib/libc/stdlib/atexit.c b/lib/libc/stdlib/atexit.c index 05dad84..8389637 100644 --- a/lib/libc/stdlib/atexit.c +++ b/lib/libc/stdlib/atexit.c @@ -41,6 +41,7 @@ __FBSDID("$FreeBSD: src/lib/libc/stdlib/atexit.c,v 1.8 20= 07/01/09 00:28:09 imp E #include #include #include +#include #include "atexit.h" #include "un-namespace.h" =20 @@ -56,7 +57,7 @@ static pthread_mutex_t atexit_mutex =3D PTHREAD_MUTEX_INI= TIALIZER; #define _MUTEX_UNLOCK(x) if (__isthreaded) _pthread_mutex_unlock(x) =20 struct atexit { - struct atexit *next; /* next in list */ + LIST_ENTRY(atexit) link; int ind; /* next index in this table */ struct atexit_fn { int fn_type; /* ATEXIT_? from above */ @@ -69,7 +70,10 @@ struct atexit { } fns[ATEXIT_SIZE]; /* the table itself */ }; =20 -static struct atexit *__atexit; /* points to head of LIFO stack */ +/* Head of LIFO stack */ +LIST_HEAD(, atexit) __atexit =3D LIST_HEAD_INITIALIZER(__atexit); +static struct atexit __atexit0; /* one guaranteed table */ +static unsigned long __atexit_gen; =20 /* * Register the function described by 'fptr' to be called at application @@ -79,30 +83,33 @@ static struct atexit *__atexit; /* points to head of L= IFO stack */ static int atexit_register(struct atexit_fn *fptr) { - static struct atexit __atexit0; /* one guaranteed table */ struct atexit *p; + unsigned long old__atexit_gen; =20 _MUTEX_LOCK(&atexit_mutex); - if ((p =3D __atexit) =3D=3D NULL) - __atexit =3D p =3D &__atexit0; - else while (p->ind >=3D ATEXIT_SIZE) { - struct atexit *old__atexit; - old__atexit =3D __atexit; - _MUTEX_UNLOCK(&atexit_mutex); - if ((p =3D (struct atexit *)malloc(sizeof(*p))) =3D=3D NULL) - return (-1); - _MUTEX_LOCK(&atexit_mutex); - if (old__atexit !=3D __atexit) { - /* Lost race, retry operation */ + if (LIST_EMPTY(&__atexit)) { + p =3D &__atexit0; + LIST_INSERT_HEAD(&__atexit, p, link); + } else { + retry: + p =3D LIST_FIRST(&__atexit); + if (p->ind >=3D ATEXIT_SIZE) { + old__atexit_gen =3D __atexit_gen; _MUTEX_UNLOCK(&atexit_mutex); - free(p); + if ((p =3D (struct atexit *)malloc(sizeof(*p))) =3D=3D NULL) + return (-1); _MUTEX_LOCK(&atexit_mutex); - p =3D __atexit; - continue; + if (old__atexit_gen !=3D __atexit_gen) { + /* Lost race, retry operation */ + _MUTEX_UNLOCK(&atexit_mutex); + free(p); + _MUTEX_LOCK(&atexit_mutex); + goto retry; + } + p->ind =3D 0; + LIST_INSERT_HEAD(&__atexit, p, link); + __atexit_gen++; } - p->ind =3D 0; - p->next =3D __atexit; - __atexit =3D p; } p->fns[p->ind++] =3D *fptr; _MUTEX_UNLOCK(&atexit_mutex); @@ -119,7 +126,7 @@ atexit(void (*func)(void)) int error; =20 fn.fn_type =3D ATEXIT_FN_STD; - fn.fn_ptr.std_func =3D func;; + fn.fn_ptr.std_func =3D func; fn.fn_arg =3D NULL; fn.fn_dso =3D NULL; =20 @@ -138,7 +145,7 @@ __cxa_atexit(void (*func)(void *), void *arg, void *dso) int error; =20 fn.fn_type =3D ATEXIT_FN_CXA; - fn.fn_ptr.cxa_func =3D func;; + fn.fn_ptr.cxa_func =3D func; fn.fn_arg =3D arg; fn.fn_dso =3D dso; =20 @@ -154,32 +161,55 @@ __cxa_atexit(void (*func)(void *), void *arg, void *d= so) void __cxa_finalize(void *dso) { - struct atexit *p; - struct atexit_fn fn; - int n; + struct atexit *p, *p1, cp; + struct atexit_fn *fn; + int i, n, inuse; + unsigned long orig__atexit_gen; =20 _MUTEX_LOCK(&atexit_mutex); - for (p =3D __atexit; p; p =3D p->next) { + restart: + inuse =3D 0; + LIST_FOREACH_SAFE(p, &__atexit, link, p1) { + cp.ind =3D 0; for (n =3D p->ind; --n >=3D 0;) { if (p->fns[n].fn_type =3D=3D ATEXIT_FN_EMPTY) continue; /* already been called */ - if (dso !=3D NULL && dso !=3D p->fns[n].fn_dso) + if (dso !=3D NULL && dso !=3D p->fns[n].fn_dso) { + inuse =3D 1; continue; /* wrong DSO */ - fn =3D p->fns[n]; + } + cp.fns[cp.ind++] =3D p->fns[n]; /* Mark entry to indicate that this particular handler has already been called. */ p->fns[n].fn_type =3D ATEXIT_FN_EMPTY; - _MUTEX_UNLOCK(&atexit_mutex); - =09 + } + if (!inuse && p !=3D &__atexit0) { + LIST_REMOVE(p, link); + __atexit_gen++; + } else { + /* + * The current entry cannot be removed, and so + * any consequent entries. + */ + inuse =3D 1; + p =3D NULL; + } + orig__atexit_gen =3D __atexit_gen; + _MUTEX_UNLOCK(&atexit_mutex); + free(p); + for (i =3D 0; i < cp.ind; i++) { + fn =3D &cp.fns[i]; /* Call the function of correct type. */ - if (fn.fn_type =3D=3D ATEXIT_FN_CXA) - fn.fn_ptr.cxa_func(fn.fn_arg); - else if (fn.fn_type =3D=3D ATEXIT_FN_STD) - fn.fn_ptr.std_func(); - _MUTEX_LOCK(&atexit_mutex); + if (fn->fn_type =3D=3D ATEXIT_FN_CXA) + fn->fn_ptr.cxa_func(fn->fn_arg); + else if (fn->fn_type =3D=3D ATEXIT_FN_STD) + fn->fn_ptr.std_func(); } + _MUTEX_LOCK(&atexit_mutex); + if (orig__atexit_gen !=3D __atexit_gen) + goto restart; } _MUTEX_UNLOCK(&atexit_mutex); } --gDKptnH9ef5/6wqy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkfAk3EACgkQC3+MBN1Mb4iYzgCgnIjlPDHsOllc5U33+sV5hceS L9MAnjXVjleHRdMhZhSytwoF6tr6Uk+2 =Dz5Y -----END PGP SIGNATURE----- --gDKptnH9ef5/6wqy-- From owner-freebsd-stable@FreeBSD.ORG Sat Feb 23 22:55:09 2008 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 9A58616A401 for ; Sat, 23 Feb 2008 22:55:09 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 3804013C458 for ; Sat, 23 Feb 2008 22:55:09 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0JWP004JRRNV3MA0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Sat, 23 Feb 2008 23:55:07 +0100 (CET) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0JWP004B7RNU5U80@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Sat, 23 Feb 2008 23:55:07 +0100 (CET) Date: Sat, 23 Feb 2008 23:55:06 +0100 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Message-id: <20080223235506.53584a06.torfinn.ingolfsen@broadpark.no> In-reply-to: References: X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.8; i386-portbld-freebsd6.3) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: packet loss with re(4) 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, 23 Feb 2008 22:55:09 -0000 On Sat, 23 Feb 2008 14:44:49 -0500 Dan Langille wrote: > With FreeBSD 6.3-RELEASE, I'm finding significant packet loss > (sometimes 85%). > If I insert an Intel nic (fxp), there is nil packet loss with > similar tests (ping -c 100). Perhaps the recent MFC's for re helps? see http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/re/if_re.c I have just upgraded my machine[1] to the latest 7-stable,so it is still too early to tell if re(4) is stable now. References: 1) http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd -- Regards, Torfinn Ingolfsen