From owner-freebsd-stable@FreeBSD.ORG Sun May 21 00:19:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2815216A42A for ; Sun, 21 May 2006 00:19:13 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-d5debe68.catv.broadband.hu [213.222.190.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0623B43D49 for ; Sun, 21 May 2006 00:19:07 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <446FB2B0.5090606@antiszoc.hu> Date: Sun, 21 May 2006 02:22:08 +0200 From: Andras Got User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060404 SeaMonkey/1.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <446DCCE5.6030601@antiszoc.hu> <20060520183106.GA99605@tehran.lain.pl> In-Reply-To: <20060520183106.GA99605@tehran.lain.pl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: possible tcp 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: Sun, 21 May 2006 00:19:15 -0000 Hi, Yes... This was because a bad setting in pf.conf. The state rules/buffers or something filled from time to time. The sendmail error wasn't connected to this, they just in the same jail and almost similar errors. I thought 1 means the same accross programs. :( So I'm sorry for my false letter. :( Regards, Andras Stanislaw Halik wrote: > On Fri, May 19, 2006, Andras Got wrote: >> I'm using freebsd 6.1 and _sometimes_ (one for every ~30-40 minutes) I >> get mysql connect errors with permission denied. The mysql_connect >> returns error code 1, which is permission denied. > > Quite certainly not true: > >> Errors: >> sendmail[37085]: gethostbyaddr(IP) failed: 1 > ^^^^^^^^^^^^^ >> Can't connect to MySQL server on 'IP' (1) > > /usr/include/netdb.h:#define HOST_NOT_FOUND 1 /* Authoritative Answer Host not found */ > > HTH, > > -- sh From owner-freebsd-stable@FreeBSD.ORG Sun May 21 00:25:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E04A216A446 for ; Sun, 21 May 2006 00:25:38 +0000 (UTC) (envelope-from kaiwai.gardiner@gmail.com) Received: from grunt5.ihug.co.nz (grunt5.ihug.co.nz [203.109.254.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D82243D6E for ; Sun, 21 May 2006 00:25:38 +0000 (GMT) (envelope-from kaiwai.gardiner@gmail.com) Received: from 203-173-144-115.bliink.ihug.co.nz ([192.168.1.4]) [203.173.144.115] by grunt5.ihug.co.nz with esmtp (Exim 3.35 #1 (Debian)) id 1FhblI-0005P5-00; Sun, 21 May 2006 12:25:36 +1200 From: Matthew Gardiner To: noackjr@alumni.rice.edu, freebsd-stable@freebsd.org Date: Sun, 21 May 2006 12:26:53 +1200 User-Agent: KMail/1.9.1 References: <200605211042.20646.kaiwai.gardiner@gmail.com> <446F9E14.5050701@alumni.rice.edu> In-Reply-To: <446F9E14.5050701@alumni.rice.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605211226.53471.kaiwai.gardiner@gmail.com> Cc: Subject: Re: drm/dri rocks 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, 21 May 2006 00:25:42 -0000 On Sunday 21 May 2006 10:54, Jonathan Noack wrote: > On 05/20/06 18:42, Matthew Gardiner wrote: > > On Sunday 21 May 2006 06:41, Jonathan Noack wrote: > >> On 05/19/06 01:44, Matthew Gardiner wrote: > >>> On Friday 19 May 2006 05:07, Ronald Klop wrote: > >>>> This commit of the drm/dri stuff yesterday on 6-STABLE rocks. > >>>> It works out of the box on my i810. > >>>> > >>>> I think FreeBSD is now ready for the desktop since xlock looks really > >>>> cool. > >>> > >>> Pardon? the DRM/DRI stuff yesturday? going by the ports/graphics/dri, > >>> it hasn't been touched in over three months. > >> > >> He was referring to an update of the kernel drivers: > >> http://lists.freebsd.org/pipermail/cvs-src/2006-May/063838.html > >> > >> -Jonathan > > > > So I assume that those updates will appear in 6.2 or some other future > > update? > > Correct, these updates will appear in 6.2. > > > how does RELENG_6 differ from my setup of RELENG_6_1? > > RELENG_6 is the branch from which 6.x releases are built. During the > 6.1 release cycle, the RELENG_6 branch was "copied" to create the > RELENG_6_1 errata branch, from which 6.1-RELEASE was actually built. > New features and bug fixes for 6.2 go into RELENG_6, but only security > and critical bug fixes will go into RELENG_6_1. In regards to stability, how stable are these additions? I'm assuming they've gone through a pretty rigorous testing before merging? Matty From owner-freebsd-stable@FreeBSD.ORG Sun May 21 00:31:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD64A16A44B for ; Sun, 21 May 2006 00:31:25 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl (tehran.lain.pl [85.221.230.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F1143D64 for ; Sun, 21 May 2006 00:31:25 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from sthalik by tehran.lain.pl with local (envelope-from ) id 1Fhbqt-0004uM-Sf for freebsd-stable@freebsd.org; Sun, 21 May 2006 02:31:23 +0200 Date: Sun, 21 May 2006 02:31:23 +0200 From: Stanislaw Halik To: freebsd-stable@freebsd.org Message-ID: <20060521003123.GA18813@tehran.lain.pl> Mail-Followup-To: freebsd-stable@freebsd.org References: <446DCCE5.6030601@antiszoc.hu> <20060520183106.GA99605@tehran.lain.pl> <446FB2B0.5090606@antiszoc.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <446FB2B0.5090606@antiszoc.hu> X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 X-User: sthalik: Subject: Re: possible tcp 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: Sun, 21 May 2006 00:31:26 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 21, 2006, Andras Got wrote: [top-posting corrected] >> On Fri, May 19, 2006, Andras Got wrote: >>> I'm using freebsd 6.1 and _sometimes_ (one for every ~30-40 minutes) I >>> get mysql connect errors with permission denied. The mysql_connect >>> returns error code 1, which is permission denied. >> Quite certainly not true: >>> Errors: >>> sendmail[37085]: gethostbyaddr(IP) failed: 1 >> ^^^^^^^^^^^^^ >>> Can't connect to MySQL server on 'IP' (1) >> /usr/include/netdb.h:#define HOST_NOT_FOUND 1 /* Authoritative Answe= r=20 >> Host not found */ >> HTH, > Yes... This was because a bad setting in pf.conf. The state > rules/buffers or something filled from time to time. If the state limit is being approached, try adaptive.{start,end} and/or limiting the total number of states for offending connections. > The sendmail error wasn't connected to this, they just in the same > jail and almost similar errors. I thought 1 means the same accross > programs. :( For errno -- yes. In that case, it's h_errno being set. -- sh --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEb7TbadU+vjT62TERAthLAJwKQ9WMt3VGvTYguCTyWi2o1G7fcgCfXM2G 5fRvarWuRIdDYp1i36bQIxI= =WV6/ -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 00:36:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E166716A494 for ; Sun, 21 May 2006 00:36:34 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FFAB43D46 for ; Sun, 21 May 2006 00:36:33 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002580332.msg for ; Sun, 21 May 2006 01:35:42 +0100 Message-ID: <002901c67c6e$7ac3b1d0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Matthew Gardiner" , , References: <200605211042.20646.kaiwai.gardiner@gmail.com><446F9E14.5050701@alumni.rice.edu> <200605211226.53471.kaiwai.gardiner@gmail.com> Date: Sun, 21 May 2006 01:35:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Sun, 21 May 2006 01:35:42 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-MDAV-Processed: multiplay.co.uk, Sun, 21 May 2006 01:35:42 +0100 Cc: Subject: Re: drm/dri rocks 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, 21 May 2006 00:36:35 -0000 Matthew Gardiner wrote: > In regards to stability, how stable are these additions? I'm assuming > they've gone through a pretty rigorous testing before merging? Stable is perhaps a bad word. It refers to the fact the that ABI / API's are stable, in that they aren't changing, and not that code / changes themselves are necessarily stable. Everyone does their best to commit "stable" changes but if your want very well tested -stable may not be for you -release may be a better option. That said if everyone sat on -release issues in -stable would never be found :P Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Sun May 21 09:15:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9F8F16A423 for ; Sun, 21 May 2006 09:15:00 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 524E543D48 for ; Sun, 21 May 2006 09:14:54 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout1-sn1.fre.skanova.net (7.2.072.1) id 446E043B000390F0 for freebsd-stable@freebsd.org; Sun, 21 May 2006 11:14:54 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id 9C8C261D1B for ; Sun, 21 May 2006 11:14:53 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqvZ554UogbH for ; Sun, 21 May 2006 11:14:52 +0200 (CEST) Received: from [10.10.0.6] (vpn1-c1.stromnet.org [10.10.0.6]) by elfi.stromnet.org (Postfix) with ESMTP id 81E9261D1C for ; Sun, 21 May 2006 11:14:52 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v749.3) To: freebsd-stable@freebsd.org Message-Id: Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-7-244566966; protocol="application/pkcs7-signature" From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Sun, 21 May 2006 11:16:14 +0200 X-Mailer: Apple Mail (2.749.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: GEOM problems 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: Sun, 21 May 2006 09:15:07 -0000 --Apple-Mail-7-244566966 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi I've had problems before with GEOM mirror and my SATA drives, and i've posted about it here before too. The solution seemd to be a change of motherboard, this reduced the crash very much (and also the speeds archieved was greatly improved, from 10-15MB/s to 40-50MB/s..). However after the change i had one or two crashes, but now it has been running for well over 50-60 days or so without any problems. Then, 11 days ago I upgraded to 6.1... And now I got these "crashe"s again (the mirror is crashed that is, the system still runs fine): May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached May 21 02:04:58 elfi kernel: subdisk6: detached May 21 02:04:58 elfi kernel: ad6: detached May 21 02:04:58 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad6s1 disconnected. May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ (offset=11006308352, length=2048)]error = 6 May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ (offset=164847927296, length=131072)]error = 6 May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ (offset=256680296448, length=32768)]error = 6 Some info about the controller and disks: May 9 22:46:52 elfi kernel: ata1: on atapci0 May 9 22:46:52 elfi kernel: atapci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0x7f00-0x7f0f, 0x7c0 0-0x7c7f irq 22 at device 11.0 on pci0 May 9 22:46:52 elfi kernel: ad4: 286188MB at ata2-master SATA150 May 9 22:46:52 elfi kernel: ad6: 286188MB at ata3-master SATA150 May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1 created (id=4118114647). May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad4s1 detected. May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad6s1 detected. May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad6s1 activated. May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad4s1 activated. May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. May 9 22:46:52 elfi kernel: Trying to mount root from ufs:/dev/ mirror/gm0s1a Anyone got any new clues? Afaik the disks should be working fine (they are 6 months old and this same problem has occured multiple times...) Hope to solve this ;) Thanks Johan --Apple-Mail-7-244566966-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 17:13:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1B1016A42A for ; Sun, 21 May 2006 17:13:37 +0000 (UTC) (envelope-from needacoder@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65CE243D45 for ; Sun, 21 May 2006 17:13:36 +0000 (GMT) (envelope-from needacoder@gmail.com) Received: by nf-out-0910.google.com with SMTP id x29so432123nfb for ; Sun, 21 May 2006 10:13:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nQYAzZ00VN4yx8TQrPoieKYB/4ga9Gbhjue4sSXBQfApsJ3xbUY+6/LXlrXqUIPHRJiGUrsE5iKLjb8VtZ0Jje6Qgn1dsTbeDG1YtPZKmjBCFQEHlSMj+AEvEDLtsgUmIiiiDv9XjWAYs9B4vuBOiQ35JqHBrkAKqgPKmgnEFgo= Received: by 10.49.20.8 with SMTP id x8mr3078280nfi; Sun, 21 May 2006 10:13:35 -0700 (PDT) Received: by 10.49.75.2 with HTTP; Sun, 21 May 2006 10:13:35 -0700 (PDT) Message-ID: <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> Date: Sun, 21 May 2006 13:13:35 -0400 From: "m m" To: "Alexander Kabaev" In-Reply-To: <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1e4841eb0605111757t36fdf8cfv267799a17dffc650@mail.gmail.com> <20060514195510.783fa765@kan.dnsalias.net> <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> Cc: stable@freebsd.org Subject: Re: improper handling of dlpened's C++/atexit() code? 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, 21 May 2006 17:13:38 -0000 Any hints on this available? Suggestions, more info, anything else? On 5/15/06, m m wrote: > On 5/14/06, Alexander Kabaev wrote: > > On Thu, 11 May 2006 20:57:20 -0400 > > "m m" wrote: > > > > > I am writing in regard to PR at > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin%2F59552 . I am > > > experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: > > > Sun Mar 26 00:03:52 EST 2006 which looks a lot like something that > > > would be caused by this PR. This happens when apache-1.3 processes > > > that run with Mason code receive a SIGUSR1 (when newsyslog does log > > > rotation) and apache gracefully kills off all processes when > > > restarting. The following is the stack trace that lead me to this PR= : > > You'll need to build ld-elf.so.1 and libc.so.6 to get a sensible > > backtrace. > > Please find the new stack trace below. If there is more information I > can provide, just ask. (This is 6.1-STABLE, cvsup very shortly before > May 11 23:14 EDT) > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000 in ?? () > (gdb) bt > #0 0x00000000 in ?? () > #1 0x294c0ad8 in __do_global_dtors_aux () from > /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > #2 0x294c1d4c in _fini () from > /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > #3 0x280b4c80 in ?? () > #4 0x280aaab8 in ?? () from /libexec/ld-elf.so.1 > #5 0xbfbfe6e8 in ?? () > #6 0x2808dca6 in objlist_call_fini (list=3D0x280a96d8) at > /usr/src/libexec/rtld-elf/rtld.c:1336 > #7 0x2808e1d4 in rtld_exit () at /usr/src/libexec/rtld-elf/rtld.c:1528 > #8 0x281d58ea in __cxa_finalize (dso=3D0x0) at > /usr/src/lib/libc/stdlib/atexit.c:184 > #9 0x281d55ba in exit (status=3D0) at /usr/src/lib/libc/stdlib/exit.c:69 > #10 0x0805d0cb in clean_child_exit () > #11 0x0805ea77 in just_die () > #12 0x0805ea9a in usr1_handler () > #13 0xbfbfffb4 in ?? () > #14 0x0000001e in ?? () > #15 0x00000000 in ?? () > #16 0xbfbfe7c0 in ?? () > #17 0x00000002 in ?? () > #18 0x0805ea80 in just_die () > #19 0x0806011e in child_main () > #20 0x080607de in make_child () > #21 0x08060868 in startup_children () > #22 0x08060e81 in standalone_main () > #23 0x08061702 in main () > From owner-freebsd-stable@FreeBSD.ORG Sun May 21 18:00:05 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D353C16A4D1; Sun, 21 May 2006 18:00:04 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65E3243D45; Sun, 21 May 2006 18:00:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4BF111A4D95; Sun, 21 May 2006 11:00:04 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 848E6537DE; Sun, 21 May 2006 14:00:03 -0400 (EDT) Date: Sun, 21 May 2006 14:00:03 -0400 From: Kris Kennaway To: Dmitry Pryanishnikov Message-ID: <20060521180003.GA59697@xor.obsecurity.org> References: <200605160135.TAA04838@lariat.net> <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <20060517130629.T64952@atlantis.atlantis.dp.ua> User-Agent: Mutt/1.4.2.1i Cc: Brett Glass , stable@freebsd.org, Colin Percival Subject: Re: 4.11 snapshots? 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, 21 May 2006 18:00:55 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 17, 2006 at 01:22:59PM +0300, Dmitry Pryanishnikov wrote: >=20 > Hello! >=20 > On Tue, 16 May 2006, Colin Percival wrote: > >Personally, since FreeBSD 4.11 will reach its EoL about 8 months > >from now, and the 4.x->[56].x upgrade path is non-trivial, I > >recommend installing FreeBSD 6.1 instead. >=20 > Well, have you seen my simple performance benchmarking RELENG_4 vs 6? > IMHO it mimics quote common usage pattern: it just downloads a large file > with 10Mbps rate and stores it on UFS filesystem. On the same hardware > (i386 uniprocessor Celeron-333 system with 128Mb RAM and fast SAMSUNG=20 > SP0802N > HDD using UDMA33) under the same conditions, using more optimal config=20 > (INVARIANTS removed) RELENG_6 (and 5) _still_ uses >=3D 50% of CPU time > for (Intr+Sys), while RELENG_4 doesn't use more than 28% for them. So > (unless this performance difference will be minimized) I predict _a lot_ > of requests to extend RELENG_4 support further, because people just could= n't > afford 4->6 upgrade due to a loss of performance. This is a network+filesystem benchmark, and it's probably the "network" part that is using extra CPU, not the "filesystem" part. But until you run those profiling tests we can't be sure. Kris --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcKqjWry0BWjoQKURAjYiAKCvzrsiNOg4VZM4rI9Dm45NRqelVACeLugN az7M25fmLKt6v3cD7rRbkV0= =HXQa -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 18:14:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E22416A57A for ; Sun, 21 May 2006 18:14:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDFF043D49 for ; Sun, 21 May 2006 18:14:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BFD4D1A4DD2; Sun, 21 May 2006 11:14:57 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F170E51742; Sun, 21 May 2006 14:14:55 -0400 (EDT) Date: Sun, 21 May 2006 14:14:55 -0400 From: Kris Kennaway To: Brett Glass Message-ID: <20060521181455.GB59697@xor.obsecurity.org> References: <200605160135.TAA04838@lariat.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Content-Disposition: inline In-Reply-To: <200605160135.TAA04838@lariat.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: 4.11 snapshots? 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, 21 May 2006 18:15:04 -0000 --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, May 15, 2006 at 07:35:53PM -0600, Brett Glass wrote: > Is there a server currently furnishing snapshots of the FreeBSD 4.11 security > branch? We have some servers running various 4.x versions that might not be > happy with 6.x due to memory requirements. They also might have slower file > access (The file system in FreeBSD 6.x still isn't as snappy as the one > in 4.x, though I hope this will change). So, we'd like to upgrade them to > a patch level that includes all recent security fixes. Are ISOs available? FYI, it is only soft updates (really bufdaemon, through which all the I/O passes) that has performance problems under high load on 6.x compared to 4.x. Other mount modes perform quite a bit better (e.g. 30% faster for async write performance) than 4.x on the hardware I tested. http://people.freebsd.org/~kris/bsdcan/Filesystem%20Performance.pdf Kris P.S. Don't link to the above URL, I need to send it to Dan for publication on the BSDCan site, to which you should link instead. --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD4DBQFEcK4fWry0BWjoQKURAhviAJsHUll9QnGOvq7d6kTebr3aQz8z9QCYsitn OACSo5NllCs4WU+EsX3faw== =QhC5 -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 19:04:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B9C16AA77 for ; Sun, 21 May 2006 19:04:09 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7607E43D46 for ; Sun, 21 May 2006 19:04:07 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe (circe.rz.RWTH-Aachen.DE [134.130.3.36]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IZM009ELQAU4I@ms-dienst.rz.rwth-aachen.de> for freebsd-stable@freebsd.org; Sun, 21 May 2006 21:04:07 +0200 (MEST) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Sun, 21 May 2006 21:04:06 +0200 (MEST) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.1/8.13.1/1) with ESMTP id k4LJ45Nq004699 for ; Sun, 21 May 2006 21:04:05 +0200 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FhtDi-0001pV-0M for freebsd-stable@freebsd.org; Sun, 21 May 2006 21:04:06 +0200 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id A07EE3F40B; Sun, 21 May 2006 21:04:05 +0200 (CEST) Date: Sun, 21 May 2006 21:04:05 +0200 From: Christian Brueffer To: freebsd-stable@freebsd.org Message-id: <20060521190405.GB1308@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; boundary=4SFOXa2GPu3tIq4H; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.1-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D Subject: Fatal trap 12: page fault while in kernel mode 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, 21 May 2006 19:04:13 -0000 --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, got the following trap on an i386 SMP system running with recent RELENG_6 sources. The system was doing copies from/to geli encrypted disks, using hifn(4) hardware crypto. Core and debug kernel are available, but the trace appears to be corrupted. - Christian Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0xc43cb554 fault code =3D supervisor write, page not present instruction pointer =3D 0x20:0xc07854fe stack pointer =3D 0x28:0xd44c1c34 frame pointer =3D 0x28:0xd44c1c5c code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 32 (irq19: hifn0) [thread pid 32 tid 100033 ] Stopped at generic_bcopy+0x1a: repe movsl (%esi),%es:(%edi) db> tr generic_bcopy(c4ebe118,ff0,10,c43cb554,c4ebe0a0) at generic_bcopy+0x1a hifn_callback(c351e800,c3d2e000,0,868,0) at hifn_callback+0x333 hifn_intr(c351e800,d44c1cd8,c05a0e8d,c084a8a0,1) at hifn_intr+0x2a7 ithread_execute_handlers(c33f1a3c,c3345400,c07d243c,30f,c3310780) at ithread_execute_handlers+0x128 ithread_loop(c35260f0,d44c1d38,c07d220e,31d,dfffffff) at ithread_loop+0x84 fork_exit(c0590a00,c35260f0,d44c1d38) at fork_exit+0xc1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xd44c1d6c, ebp =3D 0 --- Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0xc43cb554 fault code =3D supervisor write, page not present instruction pointer =3D 0x20:0xc07854fe stack pointer =3D 0x28:0xd44c1c34 frame pointer =3D 0x28:0xd44c1c5c code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 32 (irq19: hifn0) Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130796 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc048f326 in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D1999, dummy4= =3D0xd44c1a14 "`\027\204=C0\f") at /data/build/STABLE/src/sys/ddb/db_command.c:492 #2 0xc048f0a2 in db_command (last_cmdp=3D0xc0840e64, cmd_table=3D0x0, aux_= cmd_tablep=3D0xc07fbbc0,=20 aux_cmd_tablep_end=3D0xc07fbbc4) at /data/build/STABLE/src/sys/ddb/db_c= ommand.c:350 #3 0xc048f1b5 in db_command_loop () at /data/build/STABLE/src/sys/ddb/db_c= ommand.c:458 #4 0xc04913a5 in db_trap (type=3D12, code=3D0) at /data/build/STABLE/src/s= ys/ddb/db_main.c:221 #5 0xc05cb1be in kdb_trap (type=3D0, code=3D0, tf=3D0xd44c1bf4) at /data/build/STABLE/src/sys/kern/subr_kdb.c:473 #6 0xc0787e1b in trap_fatal (frame=3D0xd44c1bf4, eva=3D0) at /data/build/STABLE/src/sys/i386/i386/trap.c:827 #7 0xc0787ac2 in trap_pfault (frame=3D0xd44c1bf4, usermode=3D0, eva=3D3292= 312916) at /data/build/STABLE/src/sys/i386/i386/trap.c:744 #8 0xc078766d in trap (frame=3D {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D -1002654380, tf_= esi =3D -991182864, tf_ebp =3D -733209508, tf_isp =3D -733209568, tf_ebx =3D 16, tf_edx =3D 4080, tf_ecx =3D 4, tf_eax =3D -11471516, tf_trapno =3D 12, tf_e= rr =3D 2, tf_eip =3D -1065855746, tf_cs =3D 32, tf_eflags =3D 66066, tf_esp =3D 16, tf_ss =3D -991174344}) at /data/build/STABLE/src/sys/i386/i386/trap.c:434 #9 0xc07713da in calltrap () at /data/build/STABLE/src/sys/i386/i386/exception.s:139 #10 0xc07854fe in generic_bcopy () at /data/build/STABLE/src/sys/i386/i386/support.s:489 Previous frame inner to this frame (corrupt stack?) --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEcLmlbHYXjKDtmC0RAtYTAKDalDzhFGHPty/sV69OBGKZlOXjlwCfe9M5 3ENOj7XTz+1VE4hq5vAgiWQ= =SA5o -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 19:21:06 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5178116A427; Sun, 21 May 2006 19:21:06 +0000 (UTC) (envelope-from brett@lariat.org) Received: from lariat.net (lariat.net [65.122.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9784643D46; Sun, 21 May 2006 19:21:05 +0000 (GMT) (envelope-from brett@lariat.org) Received: from Anne (IDENT:ppp1000.lariat.net@lariat.net [65.122.236.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id NAA10675; Sun, 21 May 2006 13:20:38 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Sun, 21 May 2006 13:20:24 -0600 To: Kris Kennaway , Dmitry Pryanishnikov From: Brett Glass In-Reply-To: <20060521180003.GA59697@xor.obsecurity.org> References: <200605160135.TAA04838@lariat.net> <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> <20060521180003.GA59697@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: stable@freebsd.org, Colin Percival Subject: Re: 4.11 snapshots? 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, 21 May 2006 19:21:07 -0000 Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month), it shouldn't be a problem to do a 4.12 release as a "last gasp" to tide us over until September. (Hopefully, Colin and the "summer of code" folks can work on performance enhancements to the network stack, UFS2, and the hard disk device drivers in time for the 6.2 release in September. I'm just a little scared of 6.1, given the known problems that couldn't be fixed in time and the slower performance we're seeing on databases, etc.) --Brett From owner-freebsd-stable@FreeBSD.ORG Sun May 21 19:36:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3C4C16A453; Sun, 21 May 2006 19:36:14 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D1243D48; Sun, 21 May 2006 19:36:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 581DE1A4DD2; Sun, 21 May 2006 12:36:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7BD7851742; Sun, 21 May 2006 15:36:13 -0400 (EDT) Date: Sun, 21 May 2006 15:36:13 -0400 From: Kris Kennaway To: Christian Brueffer Message-ID: <20060521193613.GA38148@xor.obsecurity.org> References: <20060521190405.GB1308@haakonia.hitnet.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rwEMma7ioTxnRzrJ" Content-Disposition: inline In-Reply-To: <20060521190405.GB1308@haakonia.hitnet.RWTH-Aachen.DE> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: generic_bcopy() corrupts backtrace? 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, 21 May 2006 19:36:18 -0000 --rwEMma7ioTxnRzrJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, May 21, 2006 at 09:04:05PM +0200, Christian Brueffer wrote: > Core and debug kernel are available, but the trace appears to be > corrupted. Sorry to hijack your thread, but I'm also seeing corrupted backtraces from kgdb involving generic_bcopy(). Is there something about its asm implementation that confuses kgdb? > #10 0xc07854fe in generic_bcopy () at > /data/build/STABLE/src/sys/i386/i386/support.s:489 > Previous frame inner to this frame (corrupt stack?) Kris --rwEMma7ioTxnRzrJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcMEsWry0BWjoQKURAgCZAJ4uR0ZsdpMJXEzRsEfavBaDKjdHQQCfY9qh mHMHoVnHI0dHSX58jY3I/AU= =JI/7 -----END PGP SIGNATURE----- --rwEMma7ioTxnRzrJ-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 19:40:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17E4D16A57A for ; Sun, 21 May 2006 19:40:30 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86F9343D48 for ; Sun, 21 May 2006 19:40:28 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k4LJePv8022327 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 22 May 2006 05:40:26 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k4LJePCJ020430; Mon, 22 May 2006 05:40:25 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k4LJePJ5020429; Mon, 22 May 2006 05:40:25 +1000 (EST) (envelope-from peter) Date: Mon, 22 May 2006 05:40:25 +1000 From: Peter Jeremy To: Brett Glass Message-ID: <20060521194025.GJ1587@turion.vk2pj.dyndns.org> References: <200605160135.TAA04838@lariat.net> <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> <20060521180003.GA59697@xor.obsecurity.org> <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org Subject: Re: 4.11 snapshots? 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, 21 May 2006 19:40:35 -0000 On Sun, 2006-May-21 13:20:24 -0600, Brett Glass wrote: >Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month), it >shouldn't be a problem to do a 4.12 release as a "last gasp" to tide us over Maybe for April 1st next year - though novel April Fools Day jokes are always much better. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sun May 21 21:16:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EE9C16A5C7 for ; Sun, 21 May 2006 21:16:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 715F743D60 for ; Sun, 21 May 2006 21:16:13 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k4LLG8mZ080409 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 May 2006 00:16:08 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k4LLG8QT027669; Mon, 22 May 2006 00:16:08 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k4LLG7iT027668; Mon, 22 May 2006 00:16:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 22 May 2006 00:16:07 +0300 From: Konstantin Belousov To: m m Message-ID: <20060521211607.GG54541@deviant.kiev.zoral.com.ua> References: <1e4841eb0605111757t36fdf8cfv267799a17dffc650@mail.gmail.com> <20060514195510.783fa765@kan.dnsalias.net> <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JcvBIhDvR6w3jUPA" Content-Disposition: inline In-Reply-To: <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: improper handling of dlpened's C++/atexit() code? 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, 21 May 2006 21:16:31 -0000 --JcvBIhDvR6w3jUPA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 21, 2006 at 01:13:35PM -0400, m m wrote: > Any hints on this available? Suggestions, more info, anything else? >=20 > On 5/15/06, m m wrote: > >On 5/14/06, Alexander Kabaev wrote: > >> On Thu, 11 May 2006 20:57:20 -0400 > >> "m m" wrote: > >> > >> > I am writing in regard to PR at > >> > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin%2F59552 . I am > >> > experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: > >> > Sun Mar 26 00:03:52 EST 2006 which looks a lot like something that > >> > would be caused by this PR. This happens when apache-1.3 processes > >> > that run with Mason code receive a SIGUSR1 (when newsyslog does log > >> > rotation) and apache gracefully kills off all processes when > >> > restarting. The following is the stack trace that lead me to this P= R: > >> You'll need to build ld-elf.so.1 and libc.so.6 to get a sensible > >> backtrace. > > > >Please find the new stack trace below. If there is more information I > >can provide, just ask. (This is 6.1-STABLE, cvsup very shortly before > >May 11 23:14 EDT) > > > >Program received signal SIGSEGV, Segmentation fault. > >0x00000000 in ?? () > >(gdb) bt > >#0 0x00000000 in ?? () > >#1 0x294c0ad8 in __do_global_dtors_aux () from > >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > >#2 0x294c1d4c in _fini () from > >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > >#3 0x280b4c80 in ?? () > >#4 0x280aaab8 in ?? () from /libexec/ld-elf.so.1 > >#5 0xbfbfe6e8 in ?? () > >#6 0x2808dca6 in objlist_call_fini (list=3D0x280a96d8) at > >/usr/src/libexec/rtld-elf/rtld.c:1336 > >#7 0x2808e1d4 in rtld_exit () at /usr/src/libexec/rtld-elf/rtld.c:1528 > >#8 0x281d58ea in __cxa_finalize (dso=3D0x0) at > >/usr/src/lib/libc/stdlib/atexit.c:184 > >#9 0x281d55ba in exit (status=3D0) at /usr/src/lib/libc/stdlib/exit.c:69 > >#10 0x0805d0cb in clean_child_exit () > >#11 0x0805ea77 in just_die () > >#12 0x0805ea9a in usr1_handler () > >#13 0xbfbfffb4 in ?? () > >#14 0x0000001e in ?? () > >#15 0x00000000 in ?? () > >#16 0xbfbfe7c0 in ?? () > >#17 0x00000002 in ?? () > >#18 0x0805ea80 in just_die () > >#19 0x0806011e in child_main () > >#20 0x080607de in make_child () > >#21 0x08060868 in startup_children () > >#22 0x08060e81 in standalone_main () > >#23 0x08061702 in main () Could you, please, put somewhere: 1. /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so 2. output of lsof -p for apache running in your usual configuration. Also, could you run the apache with LD_PRELOAD=3D/usr/lib/libstdc++.so.5 and report whether the problem persists ? --JcvBIhDvR6w3jUPA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcNiWC3+MBN1Mb4gRAjcdAJoDLq2EzChgvF9VORMARyBS5uBSFwCfRGeT Zvh1B1jizsjXM4Y4iHIdY+0= =HrUB -----END PGP SIGNATURE----- --JcvBIhDvR6w3jUPA-- From owner-freebsd-stable@FreeBSD.ORG Sun May 21 22:03:45 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 716B416A705 for ; Sun, 21 May 2006 22:03:45 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from grunt7.ihug.co.nz (grunt7.ihug.co.nz [203.109.254.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id A897843D73 for ; Sun, 21 May 2006 22:03:41 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from 203-109-251-39.static.bliink.ihug.co.nz (heff.fud.org.nz) [203.109.251.39] by grunt7.ihug.co.nz with smtp (Exim 3.35 #1 (Debian)) id 1Fhw1P-0002f5-00; Mon, 22 May 2006 10:03:35 +1200 Received: by heff.fud.org.nz (Postfix, from userid 1001) id 8ED371CC1F; Mon, 22 May 2006 10:03:33 +1200 (NZST) Date: Mon, 22 May 2006 10:03:33 +1200 From: Andrew Thompson To: Brett Glass Message-ID: <20060521220333.GA58342@heff.fud.org.nz> References: <200605160135.TAA04838@lariat.net> <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> <20060521180003.GA59697@xor.obsecurity.org> <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> User-Agent: Mutt/1.5.11 Cc: Dmitry Pryanishnikov , stable@freebsd.org, Colin Percival , Kris Kennaway Subject: Re: 4.11 snapshots? 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, 21 May 2006 22:03:47 -0000 On Sun, May 21, 2006 at 01:20:24PM -0600, Brett Glass wrote: > Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last month), it > shouldn't be a problem to do a 4.12 release as a "last gasp" to tide us over > until September. (Hopefully, Colin and the "summer of code" folks can > work on performance enhancements to the network stack, UFS2, and the hard > disk device drivers in time for the 6.2 release in September. I'm just a > little scared of 6.1, given the known problems that couldn't be fixed in > time and the slower performance we're seeing on databases, etc.) release(7) "FreeBSD provides a complete build environment suitable for users to make full releases of the FreeBSD operating system." In the week that this email thread has been kicking around you could have made one yourself. Andrew From owner-freebsd-stable@FreeBSD.ORG Sun May 21 22:19:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A13016A772 for ; Sun, 21 May 2006 22:19:17 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B76143D46 for ; Sun, 21 May 2006 22:19:16 +0000 (GMT) (envelope-from kabaev@gmail.com) Received: by wr-out-0506.google.com with SMTP id i28so980283wra for ; Sun, 21 May 2006 15:19:15 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=KIj2Qi2SNqwVahw53dZAtAItUb/yuceVdIe+0pqIwk7/+ODOIycYwb//YjMY0z6e5aNmOChgr0NS+OdjYrOXdTPxrxZak9oimlGDUmI+nEUeXpx0aPNHkkTszFE30IkcSsqIRwuv119VUpMvxKbZLB2IOOfb98bZOICyohaKWVI= Received: by 10.54.104.7 with SMTP id b7mr1570118wrc; Sun, 21 May 2006 15:19:15 -0700 (PDT) Received: from kan.dnsalias.net ( [24.63.93.195]) by mx.gmail.com with ESMTP id 6sm1046822wrh.2006.05.21.15.19.14; Sun, 21 May 2006 15:19:14 -0700 (PDT) Date: Sun, 21 May 2006 18:19:20 -0400 From: Alexander Kabaev To: stable@freebsd.org Message-ID: <20060521181920.02aa278e@kan.dnsalias.net> In-Reply-To: <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> References: <1e4841eb0605111757t36fdf8cfv267799a17dffc650@mail.gmail.com> <20060514195510.783fa765@kan.dnsalias.net> <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_Lh2sDDgyR0c42_u08rpPogG; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Subject: Re: improper handling of dlpened's C++/atexit() code? 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, 21 May 2006 22:19:18 -0000 --Sig_Lh2sDDgyR0c42_u08rpPogG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 21 May 2006 13:13:35 -0400 "m m" wrote: > Any hints on this available? Suggestions, more info, anything else? >=20 > On 5/15/06, m m wrote: > > On 5/14/06, Alexander Kabaev wrote: > > > On Thu, 11 May 2006 20:57:20 -0400 > > > "m m" wrote: > > > > > > > I am writing in regard to PR at > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin%2F59552 . I am > > > > experiencing behavior on 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE > > > > #11: Sun Mar 26 00:03:52 EST 2006 which looks a lot like > > > > something that would be caused by this PR. This happens when > > > > apache-1.3 processes that run with Mason code receive a SIGUSR1 > > > > (when newsyslog does log rotation) and apache gracefully kills > > > > off all processes when restarting. The following is the stack > > > > trace that lead me to this PR: > > > You'll need to build ld-elf.so.1 and libc.so.6 to get a sensible > > > backtrace. > > > > Please find the new stack trace below. If there is more > > information I can provide, just ask. (This is 6.1-STABLE, cvsup > > very shortly before May 11 23:14 EDT) > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x00000000 in ?? () > > (gdb) bt > > #0 0x00000000 in ?? () > > #1 0x294c0ad8 in __do_global_dtors_aux () from > > /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > > #2 0x294c1d4c in _fini () from > > /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > > #3 0x280b4c80 in ?? () > > #4 0x280aaab8 in ?? () from /libexec/ld-elf.so.1 > > #5 0xbfbfe6e8 in ?? () > > #6 0x2808dca6 in objlist_call_fini (list=3D0x280a96d8) at > > /usr/src/libexec/rtld-elf/rtld.c:1336 > > #7 0x2808e1d4 in rtld_exit () > > at /usr/src/libexec/rtld-elf/rtld.c:1528 #8 0x281d58ea in > > __cxa_finalize (dso=3D0x0) at /usr/src/lib/libc/stdlib/atexit.c:184 > > #9 0x281d55ba in exit (status=3D0) > > at /usr/src/lib/libc/stdlib/exit.c:69 #10 0x0805d0cb in > > clean_child_exit () #11 0x0805ea77 in just_die () > > #12 0x0805ea9a in usr1_handler () > > #13 0xbfbfffb4 in ?? () > > #14 0x0000001e in ?? () > > #15 0x00000000 in ?? () > > #16 0xbfbfe7c0 in ?? () > > #17 0x00000002 in ?? () > > #18 0x0805ea80 in just_die () > > #19 0x0806011e in child_main () > > #20 0x080607de in make_child () > > #21 0x08060868 in startup_children () > > #22 0x08060e81 in standalone_main () > > #23 0x08061702 in main () > > Looks like normal atexit path to me. At this point a close look at Syslog.so is needed IMHO. I do not see anything criminal implicating FreeBSD in this crash in any way. --=20 Alexander Kabaev --Sig_Lh2sDDgyR0c42_u08rpPogG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcOdvQ6z1jMm+XZYRAnGxAJ9nCsw4khaOljPtg8dX8U4Zff4NfwCfSq4n V1ksEj3aedYeJJmks5t8Z38= =NsFk -----END PGP SIGNATURE----- --Sig_Lh2sDDgyR0c42_u08rpPogG-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 02:10:03 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB33616A4C0; Mon, 22 May 2006 02:10:02 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCCA43D48; Mon, 22 May 2006 02:10:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 18DC91A4DDB; Sun, 21 May 2006 19:10:02 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B3C075129D; Sun, 21 May 2006 22:10:00 -0400 (EDT) Date: Sun, 21 May 2006 22:09:58 -0400 From: Kris Kennaway To: Andrew Thompson Message-ID: <20060522020958.GA74782@xor.obsecurity.org> References: <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> <20060521180003.GA59697@xor.obsecurity.org> <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> <20060521220333.GA58342@heff.fud.org.nz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <20060521220333.GA58342@heff.fud.org.nz> User-Agent: Mutt/1.4.2.1i Cc: Dmitry Pryanishnikov , Brett Glass , stable@freebsd.org, Colin Percival , Kris Kennaway Subject: 6.1 stability (Re: 4.11 snapshots?) 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, 22 May 2006 02:10:03 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 22, 2006 at 10:03:33AM +1200, Andrew Thompson wrote: > On Sun, May 21, 2006 at 01:20:24PM -0600, Brett Glass wrote: > > Well, y'know, if they could release a FreeBSD 2.2.9 (as was done last m= onth), it > > shouldn't be a problem to do a 4.12 release as a "last gasp" to tide us= over=20 > > until September. (Hopefully, Colin and the "summer of code" folks can > > work on performance enhancements to the network stack, UFS2, and the ha= rd > > disk device drivers in time for the 6.2 release in September. I'm just a > > little scared of 6.1, given the known problems that couldn't be fixed in > > time and the slower performance we're seeing on databases, etc.) We did ourselves a big disservice by not pointing out clearly in the todo list that most of the listed problems are VERY RARE and are unlikely to affect most/all users. In future we're going to have to be clearer about that, because you're not the only user who was scared for no reason. We really had to push FreeBSD hard to find those problems; 6.1 stands up to enormous test loads that all previous tested releases could not handle. I wouldn't be surprised if 4.x cannot handle the same workloads, simply because no-one may have ever attempted such loads on a 4.x system. Kris P.S. If you're willing to put some effort into analyzing and profiling it, I'd be willing to work with you on your performance problem. --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcR11Wry0BWjoQKURAi0FAJ9/FlyME8dvaftV4fCh5yLQhijspACfdsvU MuJG27s342N9eZhEPBWCzt0= =yM9j -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 02:12:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1049916A4FD for ; Mon, 22 May 2006 02:12:06 +0000 (UTC) (envelope-from kasahara@nc.kyushu-u.ac.jp) Received: from elvenbow.cc.kyushu-u.ac.jp (elvenbow.nc.kyushu-u.ac.jp [133.5.6.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F096E43D6A for ; Mon, 22 May 2006 02:12:00 +0000 (GMT) (envelope-from kasahara@nc.kyushu-u.ac.jp) Received: from localhost (kasahara@localhost [IPv6:::1]) by elvenbow.cc.kyushu-u.ac.jp (8.13.6/8.13.6) with ESMTP id k4M2Bx2l013890 for ; Mon, 22 May 2006 11:11:59 +0900 (JST) (envelope-from kasahara@nc.kyushu-u.ac.jp) Date: Mon, 22 May 2006 11:11:58 +0900 (JST) Message-Id: <20060522.111158.-1887768549.kasahara@nc.kyushu-u.ac.jp> To: freebsd-stable@freebsd.org From: Yoshiaki Kasahara In-Reply-To: References: X-Fingerprint: CDA2 B6B6 6796 0DD3 9D80 2602 E909 4623 A15E A074 X-URL: http://www.nc.kyushu-u.ac.jp/~kasahara/ X-Mailer: Mew version 5.0.50 on Emacs 22.0.51 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_May_22_11_11_58_2006_318)--" Content-Transfer-Encoding: 7bit Subject: Re: GEOM problems 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, 22 May 2006 02:12:06 -0000 ----Next_Part(Mon_May_22_11_11_58_2006_318)-- Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Sorry this is only a 'me too' message... On Sun, 21 May 2006 11:16:14 +0200, Johan Str=F6m said: > May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached > May 21 02:04:58 elfi kernel: subdisk6: detached > May 21 02:04:58 elfi kernel: ad6: detached > May 21 02:04:58 elfi kernel: GEOM_MIRROR: Device gm0s1: provider = > ad6s1 disconnected. I have a similar problem on a different M/B (Intel D925XECV2). I'm not sure if it is only a coincidence or somewhat related. May 21 07:43:49 elvenbow kernel: ad4: FAILURE - device detached May 21 07:43:49 elvenbow kernel: subdisk4: detached May 21 07:43:49 elvenbow kernel: ad4: detached May 21 07:43:49 elvenbow kernel: GEOM_MIRROR: Device gm0s1: provider ad= 4s1 disconnected. excerpts from dmesg: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0= x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xec00-0xec07,0xe800-0xe8= 03,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f mem 0xf3afbc00-0xf3afbfff = irq 19 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 ad4: 239372MB at ata2-master SATA150 ad6: 239372MB at ata3-master SATA150 I purchased and started using this new PC last December, and the problem occurred several times by now. Both ad4 and ad6 have been detached (not at a time). 'atacontrol reinit' paused the system for a second, and returned without detecting the detached device. I need a complete power cycle or the device won't recognized by BIOS again. There is no SMART error recorded on these drives. I'm considering to change M/B, but it is difficult right now... dmesg.boot is attached. Ah, the system is running FreeBSD 6.1-STABLE amd64. FreeBSD elvenbow.cc.kyushu-u.ac.jp 6.1-STABLE FreeBSD 6.1-STABLE #0: Mo= n May 8 16:54:22 JST 2006 root@elvenbow.cc.kyushu-u.ac.jp:/usr/obj= /usr/src/sys/ELVENBOW amd64 -- = Yoshiaki Kasahara Computing and Communications Center, Kyushu University kasahara@nc.kyushu-u.ac.jp ----Next_Part(Mon_May_22_11_11_58_2006_318)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-2006 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 6.1-STABLE #0: Mon May 8 16:54:22 JST 2006 root@elvenbow.cc.kyushu-u.ac.jp:/usr/obj/usr/src/sys/ELVENBOW Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.10-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100800 Logical CPUs per core: 2 real memory = 2145579008 (2046 MB) avail memory = 2060705792 (1965 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: Please update driver or contact the maintainer. est: cpu_vendor GenuineIntel, msr f2d00000f2d, bus_clk, 64 device_attach: est0 attach returned 6 p4tcc0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 27.0 (no driver attached) pcib2: at device 28.0 on pci0 pci5: on pcib2 pcib3: at device 28.1 on pci0 pci4: on pcib3 pcib4: at device 28.2 on pci0 pci3: on pcib4 pcib5: at device 28.3 on pci0 pci2: on pcib5 uhci0: port 0xcc00-0xcc1f irq 23 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 0xd000-0xd01f 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 0xd400-0xd41f 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 0xd800-0xd81f 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 0xf3afb800-0xf3afbbff irq 23 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 pcib6: at device 30.0 on pci0 pci6: on pcib6 vge0: port 0xb800-0xb8ff mem 0xf3b00000-0xf3b000ff irq 22 at device 1.0 on pci6 miibus0: on vge0 ciphy0: on miibus0 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto vge0: Ethernet address: 00:02:2a:dd:05:41 vge1: port 0xb400-0xb4ff mem 0xf3b00400-0xf3b004ff irq 18 at device 2.0 on pci6 miibus1: on vge1 ciphy1: on miibus1 ciphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto vge1: Ethernet address: 00:02:2a:dd:0c:31 vge2: port 0xb000-0xb0ff mem 0xf3b00800-0xf3b008ff irq 19 at device 3.0 on pci6 miibus2: on vge2 ciphy2: on miibus2 ciphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto vge2: Ethernet address: 00:02:2a:dd:00:7d isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xec00-0xec07,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f mem 0xf3afbc00-0xf3afbfff irq 19 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 ichsmb0: port 0xc800-0xc81f irq 19 at device 31.3 on pci0 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f1,0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xcefff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 2.00/4.24, addr 2, iclass 3/1 ums0: 5 buttons and Z dir and a TILT dir. Timecounter "TSC" frequency 3000098070 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff8062fd50, 0) error 6 ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to deny, logging disabled acd0: DVDR at ata0-master UDMA33 ad4: 239372MB at ata2-master SATA150 ad6: 239372MB at ata3-master SATA150 GEOM_MIRROR: Device gm0s1 created (id=400615043). GEOM_MIRROR: Device gm0s1: provider ad4s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. GEOM_MIRROR: Device gm0s1: rebuilding provider ad4s1. Trying to mount root from ufs:/dev/mirror/gm0s1a ----Next_Part(Mon_May_22_11_11_58_2006_318)---- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 03:51:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A61616A420 for ; Mon, 22 May 2006 03:51:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C994243D45 for ; Mon, 22 May 2006 03:51:02 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k4M3ouvk090224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 May 2006 06:50:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k4M3ou4E036210; Mon, 22 May 2006 06:50:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k4M3otlB036209; Mon, 22 May 2006 06:50:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 22 May 2006 06:50:55 +0300 From: Konstantin Belousov To: m m Message-ID: <20060522035055.GH54541@deviant.kiev.zoral.com.ua> References: <1e4841eb0605111757t36fdf8cfv267799a17dffc650@mail.gmail.com> <20060514195510.783fa765@kan.dnsalias.net> <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> <20060521211607.GG54541@deviant.kiev.zoral.com.ua> <1e4841eb0605211522n74d79ac9gee392857620e90f1@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pE2VAHO2njSJCslu" Content-Disposition: inline In-Reply-To: <1e4841eb0605211522n74d79ac9gee392857620e90f1@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Alexander Kabaev Subject: Re: improper handling of dlpened's C++/atexit() code? 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, 22 May 2006 03:51:03 -0000 --pE2VAHO2njSJCslu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 21, 2006 at 06:22:34PM -0400, m m wrote: > n 5/21/06, Konstantin Belousov wrote: > >> >Program received signal SIGSEGV, Segmentation fault. > >> >0x00000000 in ?? () > >> >(gdb) bt > >> >#0 0x00000000 in ?? () > >> >#1 0x294c0ad8 in __do_global_dtors_aux () from > >> >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > >> >#2 0x294c1d4c in _fini () from > >> >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > >> >#3 0x280b4c80 in ?? () > >> >#4 0x280aaab8 in ?? () from /libexec/ld-elf.so.1 > >> >#5 0xbfbfe6e8 in ?? () > >> >#6 0x2808dca6 in objlist_call_fini (list=3D0x280a96d8) at > >> >/usr/src/libexec/rtld-elf/rtld.c:1336 > >> >#7 0x2808e1d4 in rtld_exit () at /usr/src/libexec/rtld-elf/rtld.c:15= 28 > >> >#8 0x281d58ea in __cxa_finalize (dso=3D0x0) at > >> >/usr/src/lib/libc/stdlib/atexit.c:184 > >> >#9 0x281d55ba in exit (status=3D0) at /usr/src/lib/libc/stdlib/exit.= c:69 > >> >#10 0x0805d0cb in clean_child_exit () > >> >#11 0x0805ea77 in just_die () > >> >#12 0x0805ea9a in usr1_handler () > >> >#13 0xbfbfffb4 in ?? () > >> >#14 0x0000001e in ?? () > >> >#15 0x00000000 in ?? () > >> >#16 0xbfbfe7c0 in ?? () > >> >#17 0x00000002 in ?? () > >> >#18 0x0805ea80 in just_die () > >> >#19 0x0806011e in child_main () > >> >#20 0x080607de in make_child () > >> >#21 0x08060868 in startup_children () > >> >#22 0x08060e81 in standalone_main () > >> >#23 0x08061702 in main () > > > >Could you, please, put somewhere: > >1. /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > >2. output of lsof -p for apache running > >in your usual configuration. > > > >Also, could you run the apache with LD_PRELOAD=3D/usr/lib/libstdc++.so.5 > >and report whether the problem persists ? >=20 > Konstantin, > Thank you for looking into this. >=20 > lsof: http://www.savefile.com/files/6494253 > Syslog.so: http://www.savefile.com/files/2163369 >=20 > Although it's not an indicator of certainty (I have had it exit > cleanly in the past), it appears that running Apache with LD_PRELOAD > of libstdc++ does allow it to exit cleanly. Please let me know how I > can further assist. If it would make things easier - I can provide > access to a jail on this machine which exhibits the same behavior. Ok, I have a theory how it happens. Investigation of your instance of Syslog.so shows that crash happens at the following code of /usr/lib/crtbeginS.o: 282: if (__deregister_frame_info) 283: __deregister_frame_info (__EH_FRAME_BEGIN__); (this comes in from contrib/gcc/crtstuff.c, lines 282-283). Symbol __deregister_frame_info is weak and undefined in all your DSOs except libstdc++.so.5. This symbol provides part of the C++ runtime support for exception handling, and reasonably included from c++ runtime support library. Both lines 282 and 283 produce dynamic relocations in final DSO, but line 282 implies R_386_GLOB_DAT, and 283 - R386_JUMP_SLOT (for PLT). First relocation is resolved immediately on DSO load, second one is resolved on demand. My theory is that, at the time of loading Syslog.so, libstdc++.so.5 is loaded in the process, resulting in first relocation being satisfied by rtld immediately. But, at the time exit() processing comes to _fini() function of Syslog.so, libstdc++.so.5 is unloaded. And weak PLT relocation is resolved to 0. As result we got the frame #0 from your trace. This theory is confirmed by presence of libstdc++ in lsof output. Please, check that it does not show up at the time of crash dump by using "show shared" gdb command on crash dump. Short-time fix is to use LD_PRELOAD hack. The real solution would be to mark the libstdc++ DSO as unloadable and implement support for unloadable DSO in rtld (BTW, I think this is also needed for threading libraries libpthread and libthr for the same reason). I know that glibc dynamic loader has support for this feature. P.S. Apache seems to call exit(3) from the signal handler. This is wrong. --pE2VAHO2njSJCslu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcTUfC3+MBN1Mb4gRAh9jAJ427LSdYSEtPiQ8BOq9hPxF7HLaUwCg2g2a ZslOU1A5F1ERrTUJEl4JMlQ= =fZkR -----END PGP SIGNATURE----- --pE2VAHO2njSJCslu-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 03:55:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EF1E16A421 for ; Mon, 22 May 2006 03:55:10 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02D8E43D45 for ; Mon, 22 May 2006 03:55:09 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mr6so.prod.shaw.ca (pd2mr6so-qfe3.prod.shaw.ca [10.0.141.9]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZN00GJIEVXG750@l-daemon> for freebsd-stable@freebsd.org; Sun, 21 May 2006 21:55:09 -0600 (MDT) Received: from pn2ml1so.prod.shaw.ca ([10.0.121.145]) by pd2mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZN00M5CEVXJ920@pd2mr6so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sun, 21 May 2006 21:55:09 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0IZN0047DEVWGYE0@l-daemon> for freebsd-stable@freebsd.org; Sun, 21 May 2006 21:55:09 -0600 (MDT) Received: (qmail 11059 invoked from network); Mon, 22 May 2006 03:55:08 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Mon, 22 May 2006 03:55:08 +0000 Date: Sun, 21 May 2006 20:55:07 -0700 From: Colin Percival To: freebsd security , FreeBSD Stable Message-id: <4471361B.5060208@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 User-Agent: Thunderbird 1.5 (X11/20060416) Cc: Subject: FreeBSD Security Survey 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, 22 May 2006 03:55:10 -0000 Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the presence of vulnerabilities. The Security Team has been concerned for some time by anecdotal reports concerning the number of FreeBSD systems which are not being promptly updated or are running FreeBSD releases which have passed their End of Life dates and are no longer supported. In order to better understand which FreeBSD versions are in use, how people are (or aren't) keeping them updated, and why it seems so many systems are not being updated, I have put together a short survey of 12 questions. The information gathered will inform the work done by the Security Team, as well as my own personal work on FreeBSD this summer. If you administrate system(s) running FreeBSD (in the broad sense of "are responsible for keeping system(s) secure and up to date"), please visit http://people.freebsd.org/~cperciva/survey.html and complete the survey below before May 31st, 2006. Thanks, Colin Percival FreeBSD Security Officer From owner-freebsd-stable@FreeBSD.ORG Mon May 22 04:07:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4270116A445; Mon, 22 May 2006 04:07:01 +0000 (UTC) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FBEF43D45; Mon, 22 May 2006 04:07:00 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.128] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id ABE457A; Mon, 22 May 2006 00:06:58 -0400 (EDT) In-Reply-To: <4471361B.5060208@freebsd.org> References: <4471361B.5060208@freebsd.org> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2DB25B04-BCE6-41D2-9D95-03C58A493E2C@ece.cmu.edu> Content-Transfer-Encoding: 7bit From: "Brandon S. Allbery KF8NH" Date: Mon, 22 May 2006 00:06:54 -0400 To: Colin Percival X-Mailer: Apple Mail (2.750) Cc: freebsd security , FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 04:07:01 -0000 On May 21, 2006, at 11:55 , Colin Percival wrote: > The Security Team has been concerned for some time by anecdotal > reports > concerning the number of FreeBSD systems which are not being promptly > updated or are running FreeBSD releases which have passed their End of > Life dates and are no longer supported. In order to better understand > which FreeBSD versions are in use, how people are (or aren't) keeping > them updated, and why it seems so many systems are not being > updated, I I have a 6-STABLE box that is not going to be updated to 6.1 any time soon, because my personal mail will have to be offline while I do so --- including nuking and rebuilding all ports because the ports tree has been thrashed by multiple low level updates that affect a large percentage of the tree --- and it's only a 600MHz box so it will be offline for most of a week during that upgrade. And I'm uncertain how downgrading it to 6.0-RELEASE+security patches will complicate things (downgrading via cvsup/buildworld is not a supported option, last I checked). Granted, I probably should have stuck with 6.0-R --- but then, experience has shown me that the more reliable option is to wait a week or two after release and then install -STABLE. In short: keeping FreeBSD up to date tends to be painful at best. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [openafs,heimdal,too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH From owner-freebsd-stable@FreeBSD.ORG Mon May 22 04:16:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A63116A57D; Mon, 22 May 2006 04:16:44 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CE5443D48; Mon, 22 May 2006 04:16:44 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.5] (pool-71-109-244-179.lsanca.dsl-w.verizon.net [71.109.244.179]) (authenticated bits=0) by zoot.lafn.org (8.13.4/8.13.4) with ESMTP id k4M4Gg9K034294 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 21 May 2006 21:16:43 -0700 (PDT) (envelope-from bc979@lafn.org) In-Reply-To: <4471361B.5060208@freebsd.org> References: <4471361B.5060208@freebsd.org> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <66DF01E1-277C-42EE-896E-1E7F4C2ABDDE@lafn.org> Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Sun, 21 May 2006 21:16:41 -0700 To: Colin Percival X-Mailer: Apple Mail (2.750) X-Virus-Scanned: ClamAV 0.88/1474/Sun May 21 06:18:22 2006 on zoot.lafn.org X-Virus-Status: Clean Cc: freebsd security , FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 04:16:45 -0000 On May 21, 2006, at 20:55, Colin Percival wrote: > If you administrate system(s) running FreeBSD (in the broad sense > of "are > responsible for keeping system(s) secure and up to date"), please > visit > http://people.freebsd.org/~cperciva/survey.html > and complete the survey below before May 31st, 2006. What doesn't fit into the survey very well is that all my servers are production ones and it causes a lot of grief for users when I bring them down. I try to hold updates to once per year because of that. I am currently in the middle of upgrading from 5.3 to 6.0. The easy machines are done but there are still a few that will take considerable on-site time which is not easy to come by. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 04:38:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F3E16A422; Mon, 22 May 2006 04:38:45 +0000 (UTC) (envelope-from b.j.casavant@ieee.org) Received: from yeppers.tdkt.org (skyline.tdkt.org [209.98.211.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CB2E43D53; Mon, 22 May 2006 04:38:45 +0000 (GMT) (envelope-from b.j.casavant@ieee.org) Received: from c-24-245-56-101.hsd1.mn.comcast.net (c-24-245-56-101.hsd1.mn.comcast.net [24.245.56.101]) (authenticated bits=0) by yeppers.tdkt.org (8.12.11/8.12.11/erikj-OpenBSD) with ESMTP id k4M4cg8V005096; Sun, 21 May 2006 23:38:43 -0500 (CDT) Date: Sun, 21 May 2006 23:38:42 -0500 (CDT) From: Brent Casavant X-X-Sender: bcasavan@abigail.angeltread.org To: Colin Percival In-Reply-To: <4471361B.5060208@freebsd.org> Message-ID: <20060521231657.O6063@abigail.angeltread.org> References: <4471361B.5060208@freebsd.org> Organization: "Angeltread Software Organization" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd security , FreeBSD Stable Subject: Re: FreeBSD Security Survey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Brent Casavant List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 04:38:45 -0000 On Sun, 21 May 2006, Colin Percival wrote: > In order to better understand > which FreeBSD versions are in use, how people are (or aren't) keeping > them updated, and why it seems so many systems are not being updated, I > have put together a short survey of 12 questions. I applaud this survey, however question 9 missed an important point, at least to me. I was torn between answering "less than once a month" and "I never update". While I find ports to be the single most useful feature of the FreeBSD experience, and can't thank contributors enough for the efforts, I on the other hand find updating my installed ports collection (for security reasons or otherwise) to be quite painful. I typically use portupgrade to perform this task. On several occasions I got "bit" by doing a portupgrade which wasn't able to completely upgrade all dependencies (particularly when X, GUI's, and desktops are in the mix -- though I always follow the special Gnome upgrade methods when appropriate). I can't rule out some form of pilot error, but the end result was pain. After several instances of unsatisfactory portupgrades (mostly in the 5.2 through early 5.4 timeframe), I adopted the practice of either not upgrading ports at all for the life of a particular installation on a machine (typically about one year), or when necessary by removing *all* ports from the machine, cvsup'ing, and reinstalling. This has served me quite well, particularly considering the minimal threat profile these particularly systems face. So, in short, that's why *I* rarely update ports for security reasons. There are steps that could be taken at the port maintenance level that would work well for my particular case, however that's beyond the scope of the survey. Thanks for taking the time put the survey together, I certainly hope it proves useful. Thank you, Brent Casavant From owner-freebsd-stable@FreeBSD.ORG Mon May 22 05:42:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4608916A41F for ; Mon, 22 May 2006 05:42:13 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from customer-domains.icp-qv1-irony8.iinet.net.au (customer-domains.icp-qv1-irony8.iinet.net.au [203.59.1.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D2C543D45 for ; Mon, 22 May 2006 05:42:11 +0000 (GMT) (envelope-from davidn@datalinktech.com.au) Received: from 203-206-162-119.perm.iinet.net.au (HELO mail.datalinktech.com.au) ([203.206.162.119]) by customer-domains.icp-qv1-irony8.iinet.net.au with ESMTP; 22 May 2006 13:42:07 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.05,152,1146412800"; d="scan'208"; a="315064299:sNHT12329638082" Received: from [192.168.4.232] ([192.168.4.232]) by mail.datalinktech.com.au with esmtp; Mon, 22 May 2006 15:42:03 +1000 id 0018D945.44714F2B.000174C3 Message-ID: <44714F23.6000504@datalinktech.com.au> Date: Mon, 22 May 2006 15:41:55 +1000 From: David Nugent User-Agent: Thunderbird 1.5.0.2 (X11/20060516) MIME-Version: 1.0 To: Doug Hardie , freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <66DF01E1-277C-42EE-896E-1E7F4C2ABDDE@lafn.org> In-Reply-To: <66DF01E1-277C-42EE-896E-1E7F4C2ABDDE@lafn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: FreeBSD Security Survey 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, 22 May 2006 05:42:13 -0000 Doug Hardie wrote: > On May 21, 2006, at 20:55, Colin Percival wrote: >> If you administrate system(s) running FreeBSD (in the broad sense of >> "are >> responsible for keeping system(s) secure and up to date"), please visit >> http://people.freebsd.org/~cperciva/survey.html >> and complete the survey below before May 31st, 2006. > > What doesn't fit into the survey very well is that all my servers are > production ones and it causes a lot of grief for users when I bring > them down. I try to hold updates to once per year because of that. I > am currently in the middle of upgrading from 5.3 to 6.0. The easy > machines are done but there are still a few that will take > considerable on-site time which is not easy to come by. A good failover strategy comes into play here. If you have one, then taking a single production machine off-line for a short period should be no big deal, even routine, and should not even be noticed by users if done correctly. This should be planned for and part of the network/system design. Yes, it definitely requires more resources to support, but I'll rephrase the same problem: what happens when (and I mean *when* and not *if*) a motherboard or network card fries or you suffer a hard disk crash (even 2+ drives failing at the same time on a raid array is not particularly unusual considering that drives are quite often from the same manufactured batch)? Lack of a failover on mission critical systems that *can't* be offline is like playing russian roulette. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 05:44:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA22116A42D; Mon, 22 May 2006 05:44:48 +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 DE28D43D45; Mon, 22 May 2006 05:44:47 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4M5icJY094620; Sun, 21 May 2006 23:44:44 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44714FBB.4000603@samsco.org> Date: Sun, 21 May 2006 23:44:27 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brent Casavant References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> In-Reply-To: <20060521231657.O6063@abigail.angeltread.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd security , FreeBSD Stable , Colin Percival Subject: Re: FreeBSD Security Survey 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, 22 May 2006 05:44:49 -0000 Brent Casavant wrote: > On Sun, 21 May 2006, Colin Percival wrote: > > >>In order to better understand >>which FreeBSD versions are in use, how people are (or aren't) keeping >>them updated, and why it seems so many systems are not being updated, I >>have put together a short survey of 12 questions. > > > I applaud this survey, however question 9 missed an important point, > at least to me. I was torn between answering "less than once a month" > and "I never update". > > While I find ports to be the single most useful feature of the FreeBSD > experience, and can't thank contributors enough for the efforts, I on > the other hand find updating my installed ports collection (for security > reasons or otherwise) to be quite painful. I typically use portupgrade > to perform this task. On several occasions I got "bit" by doing a > portupgrade which wasn't able to completely upgrade all dependencies > (particularly when X, GUI's, and desktops are in the mix -- though I > always follow the special Gnome upgrade methods when appropriate). > > I can't rule out some form of pilot error, but the end result was pain. > > After several instances of unsatisfactory portupgrades (mostly in the > 5.2 through early 5.4 timeframe), I adopted the practice of either not > upgrading ports at all for the life of a particular installation on a > machine (typically about one year), or when necessary by removing *all* > ports from the machine, cvsup'ing, and reinstalling. This has served > me quite well, particularly considering the minimal threat profile these > particularly systems face. > > So, in short, that's why *I* rarely update ports for security reasons. > > There are steps that could be taken at the port maintenance level that > would work well for my particular case, however that's beyond the scope > of the survey. Thanks for taking the time put the survey together, I > certainly hope it proves useful. > > Thank you, > Brent Casavant I share this frustration with you. I was once told that the pain in upgrading is due largely to a somewhat invisible difference between installing a pre-compiled package, and building+installing a port. In theory, if you stick to one method or the other, things will stay mostly consistent. But if you mix them, and particularly if you update the ports tree in the process, the end result is a bit more undefined. One thing that I wish for is that the ports tree would branch for releases, and that those branches would get security updates. I know that this would involve an exponentially larger amount of effort from the ports team, and I don't fault them for not doing it. Still, it would be nice to have. Scott From owner-freebsd-stable@FreeBSD.ORG Mon May 22 06:17:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F01FA16A421; Mon, 22 May 2006 06:17:23 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6FB843D45; Mon, 22 May 2006 06:17:23 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id AC5835880B; Sun, 21 May 2006 23:17:22 -0700 (PDT) Date: Sun, 21 May 2006 23:17:22 -0700 From: Paul Allen To: Scott Long Message-ID: <20060522061722.GA28128@groat.ugcs.caltech.edu> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44714FBB.4000603@samsco.org> Sender: jd@ugcs.caltech.edu Cc: FreeBSD Stable , Colin Percival , Brent Casavant Subject: Re: FreeBSD Security Survey 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, 22 May 2006 06:17:24 -0000 >From Scott Long , Sun, May 21, 2006 at 11:44:27PM -0600: > I share this frustration with you. I was once told that the pain in > upgrading is due largely to a somewhat invisible difference between > installing a pre-compiled package, and building+installing a port. In > theory, if you stick to one method or the other, things will stay mostly > consistent. But if you mix them, and particularly if you update the > ports tree in the process, the end result is a bit more undefined. One > thing that I wish for is that the ports tree would branch for releases, > and that those branches would get security updates. I know that this > would involve an exponentially larger amount of effort from the ports > team, and I don't fault them for not doing it. Still, it would be nice > to have. Huh? Really. What you say makes a certain amount of sense when pkg_add is used, but I haven't seen much evidence for problems with mixing ports and packages via portupgrade -P. The trouble comes not with packages but in the conflicting information between /var/db/pkg/ and the ports themselves. The former does not merely contain a stale version of the port dependency and origin information; it contains many snapshots of small slices of many different port dependency graphs (as the port tree evolves). Consistently using portupgade -rR, portinstall helps keep this under control but each pkg_add or make install in a port directory causes drift. Given that portupgrade is an optional tool and the handbook suggests the other form... well you see the trouble. But the situation is worse than this because of the manual interventions necessary to fixup the portsdb. These fixups easily create dependency graphs that never existed anywhere else before. Most often this happens because of ports being renamed, deleted, combined, etc--the trouble here is that the ports tree reveals no history about these actions. It is left to a program like portupgrade to heuristically guess!?! what has taken place. Now if you go through this process every week (every day?) usually the risk is small and it is obvious what to do, but this is not always so. Some speculation: I've always thought portupgrade did the Wrong Thing(tm) by consulting the dependency graph in /var/db. Better to merely learn which packages were installed and then exclusively use the port information... Maybe someone knows why that would be the wrong thing to do? Paul From owner-freebsd-stable@FreeBSD.ORG Mon May 22 06:47:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79A7316A422 for ; Mon, 22 May 2006 06:47:20 +0000 (UTC) (envelope-from robbak@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E3843D49 for ; Mon, 22 May 2006 06:47:19 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by nz-out-0102.google.com with SMTP id l8so888965nzf for ; Sun, 21 May 2006 23:47:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GwApCb+09ObLNgpCANMNM2GSOPJRIev/cqX1LCWrDZYSwaWmYRUyoXj5d+bnBdsr0jp14HyJBLNevkf9Duzu9h1JS5Kpu8tLBlUv6bOxZvtSFpRfbdYofnY/b/qnVDQCdZYldGabIvAMxn4hlnpvT/na1Ql2494/71Nt3jqeGw8= Received: by 10.37.22.75 with SMTP id z75mr5648808nzi; Sun, 21 May 2006 23:47:19 -0700 (PDT) Received: by 10.36.251.21 with HTTP; Sun, 21 May 2006 23:47:19 -0700 (PDT) Message-ID: Date: Mon, 22 May 2006 16:47:19 +1000 From: "Robert Backhaus" To: "Colin Percival" In-Reply-To: <4471361B.5060208@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4471361B.5060208@freebsd.org> Cc: FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 06:47:20 -0000 On 5/22/06, Colin Percival wrote: > > If you administrate system(s) running FreeBSD (in the broad sense of "are > responsible for keeping system(s) secure and up to date"), please visit > http://people.freebsd.org/~cperciva/survey.html > and complete the survey below before May 31st, 2006. > One of those "Missing Option" messages: Whether valid or not, the reason that I would avoid a binary update system is that I customise CPUTYPE, and believe, rightly or wrongly, that this would make binary updating impossible. Of course, the main reason I would not use binary updating you/they have made source updating so easy! From owner-freebsd-stable@FreeBSD.ORG Mon May 22 06:48:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39D3516A42F for ; Mon, 22 May 2006 06:48:59 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B994043D46 for ; Mon, 22 May 2006 06:48:58 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.5] (pool-71-109-244-179.lsanca.dsl-w.verizon.net [71.109.244.179]) (authenticated bits=0) by zoot.lafn.org (8.13.4/8.13.4) with ESMTP id k4M6mqPx036982 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 21 May 2006 23:48:53 -0700 (PDT) (envelope-from bc979@lafn.org) In-Reply-To: <44714F23.6000504@datalinktech.com.au> References: <4471361B.5060208@freebsd.org> <66DF01E1-277C-42EE-896E-1E7F4C2ABDDE@lafn.org> <44714F23.6000504@datalinktech.com.au> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2CBCDBD0-CC9F-4B9A-BC79-9F248DFE7A3F@lafn.org> Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Sun, 21 May 2006 23:48:51 -0700 To: David Nugent X-Mailer: Apple Mail (2.750) X-Virus-Scanned: ClamAV 0.88/1475/Sun May 21 22:09:26 2006 on zoot.lafn.org X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Security Survey 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, 22 May 2006 06:48:59 -0000 On May 21, 2006, at 22:41, David Nugent wrote: > A good failover strategy comes into play here. > > If you have one, then taking a single production machine off-line > for a short period should be no big deal, even routine, and should > not even be noticed by users if done correctly. This should be > planned for and part of the network/system design. Yes, it > definitely requires more resources to support, but I'll rephrase > the same problem: what happens when (and I mean *when* and not > *if*) a motherboard or network card fries or you suffer a hard disk > crash (even 2+ drives failing at the same time on a raid array is > not particularly unusual considering that drives are quite often > from the same manufactured batch)? > > Lack of a failover on mission critical systems that *can't* be > offline is like playing russian roulette. Failover sounds good in theory but has significant issues in practice that make it sometimes worse than the alternative. Take mail spools. If you failover, mail the user saw before has disappeared. Then when you "fail back" it reappears and newer messages disappear. This is hardly unnoticable. My users do not find that at all acceptable. Putting the mail spools on a different machine just moves that problem to the different machine. Trying to keep multiple spools consistent has problems also. I have watched raid system lose their data too. A nice power spike - 1.5Kv from a lightning strike in the local area will do it. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 06:49:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D28116A542; Mon, 22 May 2006 06:49:45 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A83B43D81; Mon, 22 May 2006 06:49:19 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.6) with ESMTP id k4M6oSvm079391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 May 2006 02:50:34 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Mon, 22 May 2006 02:49:34 -0400 User-Agent: KMail/1.9.1 References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> In-Reply-To: <44714FBB.4000603@samsco.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2431212.cZZkS9eTYF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605220249.50328.mistry.7@osu.edu> X-Spam-Status: No, score=-7.9 required=5.0 tests=ALL_TRUSTED,BAYES_50, J_CHICKENPOX_53,MYFREEBSD2,MYFREEBSD3 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.2/1474/Sun May 21 09:18:22 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: freebsd security , Colin Percival , Brent Casavant Subject: Re: FreeBSD Security Survey 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, 22 May 2006 06:49:46 -0000 --nextPart2431212.cZZkS9eTYF Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 22 May 2006 01:44, Scott Long wrote: > Brent Casavant wrote: > > On Sun, 21 May 2006, Colin Percival wrote: > >>In order to better understand > >>which FreeBSD versions are in use, how people are (or aren't) > >> keeping them updated, and why it seems so many systems are not > >> being updated, I have put together a short survey of 12 > >> questions. > > > > I applaud this survey, however question 9 missed an important > > point, at least to me. I was torn between answering "less than > > once a month" and "I never update". > > > > While I find ports to be the single most useful feature of the > > FreeBSD experience, and can't thank contributors enough for the > > efforts, I on the other hand find updating my installed ports > > collection (for security reasons or otherwise) to be quite > > painful. I typically use portupgrade to perform this task. On > > several occasions I got "bit" by doing a portupgrade which wasn't > > able to completely upgrade all dependencies (particularly when X, > > GUI's, and desktops are in the mix -- though I always follow the > > special Gnome upgrade methods when appropriate). > > > > I can't rule out some form of pilot error, but the end result was > > pain. > > > > After several instances of unsatisfactory portupgrades (mostly in > > the 5.2 through early 5.4 timeframe), I adopted the practice of > > either not upgrading ports at all for the life of a particular > > installation on a machine (typically about one year), or when > > necessary by removing *all* ports from the machine, cvsup'ing, > > and reinstalling. This has served me quite well, particularly > > considering the minimal threat profile these particularly systems > > face. > > > > So, in short, that's why *I* rarely update ports for security > > reasons. > > > > There are steps that could be taken at the port maintenance level > > that would work well for my particular case, however that's > > beyond the scope of the survey. Thanks for taking the time put > > the survey together, I certainly hope it proves useful. > > > > Thank you, > > Brent Casavant > > I share this frustration with you. I was once told that the pain > in upgrading is due largely to a somewhat invisible difference > between installing a pre-compiled package, and building+installing > a port. In theory, if you stick to one method or the other, things > will stay mostly consistent. But if you mix them, and particularly > if you update the ports tree in the process, the end result is a > bit more undefined. One thing that I wish for is that the ports > tree would branch for releases, and that those branches would get > security updates. I know that this would involve an exponentially > larger amount of effort from the ports team, and I don't fault them > for not doing it. Still, it would be nice to have. More ports seem to be separating out their different version into=20 portname20, portname, portname21, etc. This takes out quite a bit of=20 the updating woes without causing too much overhead for the=20 maintainers. Since maintaining a security branch for releases would=20 require too much overhead it might be nice to have mechanism to track=20 the "release version" of the installed software. eg. =46or 6.0 release I installed lang/lua which is lua-5.0 Then when I cvsup next time the maintainer has created a lang/lua50=20 port for the old version and lang/lua is now version 5.1. It would=20 be nice to have a mapping that I can say "Stay with version 5.0.x"=20 and when I do a portupgrade it will see that lua-5.0 is installed so=20 use lang/lua50 instead of lang/lua. As a port maintainer, I could probably live with that extra mapping. Though currently I try to keep a few jails configured on my desktop=20 that match customer's configurations and perform updates in the jail=20 first. Just to see it there will be any hiccups before actually=20 performing the updates on a customer's system. I only have 3 basic=20 configurations that I use so it's not that big of a deal for me. My biggest grip about updating the base system is the mergemaster=20 step, but once mergemaster -U is cut into a release it should fix=20 that annoyance. =2D-=20 Anish Mistry --nextPart2431212.cZZkS9eTYF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcV8OxqA5ziudZT0RApAxAJ0W62osv7XrsQiI8zsUBH/zJavyoACfbeeS oy5w1KdkFigb4p/HAP6Zwvc= =iEHD -----END PGP SIGNATURE----- --nextPart2431212.cZZkS9eTYF-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 06:55:26 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF52B16A447; Mon, 22 May 2006 06:55:26 +0000 (UTC) (envelope-from brett@lariat.org) Received: from lariat.net (lariat.net [65.122.236.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 101B643D67; Mon, 22 May 2006 06:55:24 +0000 (GMT) (envelope-from brett@lariat.org) Received: from Anne (IDENT:ppp1000.lariat.net@lariat.net [65.122.236.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id AAA18418; Mon, 22 May 2006 00:55:03 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <7.0.1.0.2.20060522005140.089ca378@lariat.org> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Mon, 22 May 2006 00:54:58 -0600 To: Kris Kennaway , Andrew Thompson From: Brett Glass In-Reply-To: <20060522020958.GA74782@xor.obsecurity.org> References: <57d710000605151942p2461338au561269fc5937aee7@mail.gmail.com> <7.0.1.0.2.20060515225038.08d72690@lariat.org> <446981CD.5000309@gmail.com> <4469C668.2060807@rerowe.com> <7.0.1.0.2.20060516104907.08788ad8@lariat.org> <446A0608.10608@freebsd.org> <20060517130629.T64952@atlantis.atlantis.dp.ua> <20060521180003.GA59697@xor.obsecurity.org> <7.0.1.0.2.20060521131507.0893e9e8@lariat.org> <20060521220333.GA58342@heff.fud.org.nz> <20060522020958.GA74782@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Dmitry Pryanishnikov , stable@freebsd.org, Colin Percival , Kris Kennaway Subject: Re: 6.1 stability (Re: 4.11 snapshots?) 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, 22 May 2006 06:55:28 -0000 At 08:09 PM 5/21/2006, Kris Kennaway wrote: >We did ourselves a big disservice by not pointing out clearly in the >todo list that most of the listed problems are VERY RARE and are >unlikely to affect most/all users. In future we're going to have to >be clearer about that, because you're not the only user who was scared >for no reason. > >We really had to push FreeBSD hard to find those problems; The servers I build are pushed really hard. >6.1 stands >up to enormous test loads that all previous tested releases could not >handle. I wouldn't be surprised if 4.x cannot handle the same >workloads, simply because no-one may have ever attempted such loads on >a 4.x system. > >Kris > >P.S. If you're willing to put some effort into analyzing and profiling >it, I'd be willing to work with you on your performance problem. You sound like one of those e-mails I keep getting offering to help me with my, er, performance problems. ;-) Seriously: The problem is that in my tests 6.x does not surpass Linux in performance, while 4.11 does. --Brett Glass From owner-freebsd-stable@FreeBSD.ORG Mon May 22 07:27:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1919E16A424; Mon, 22 May 2006 07:27:23 +0000 (UTC) (envelope-from bconstant@be.tiauto.com) Received: from smtp.eu.tiauto.com (smtp.eu.tiauto.com [195.127.176.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA9343D55; Mon, 22 May 2006 07:27:19 +0000 (GMT) (envelope-from bconstant@be.tiauto.com) Received: by euex01.resource.tiauto.com with Internet Mail Service (5.5.2657.72) id ; Mon, 22 May 2006 09:27:14 +0200 Message-ID: From: "Constant, Benjamin" To: 'Colin Percival' Date: Mon, 22 May 2006 09:27:10 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain Cc: freebsd security , FreeBSD Stable Subject: RE: FreeBSD Security Survey 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, 22 May 2006 07:27:23 -0000 Hi, We don't use binary update as we use custom kernels. We're using portaudit for security flaw with the installed ports but I don't think there is any equivalent for the base and kernel? I'm subscribed and I'm monitoring the FreeBSD Security Advisories mailing-list but there is (as far as I know) no easy system like portaudit to compare you installed base and kernel source tree against security advisories. Are there best practices in this area knowing that all my system are not running the same level of patches and non of them are running something else then -STABLE? I'll probably switch from -STABLE to -RELENG in the future (was not possible in the beginning as features we're looking for were only in -STABLE) and apply security fixes but I think it won't change the amount of work to perform compared to a non source based operating system. Regards, Benjamin Constant > -----Original Message----- > From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd- > stable@freebsd.org] On Behalf Of Colin Percival > Sent: lundi 22 mai 2006 5:55 > To: freebsd security; FreeBSD Stable > Subject: FreeBSD Security Survey > > Dear FreeBSD users and system administrators, > > While the FreeBSD Security Team has traditionally been very good at > investigating and responding to security issues in FreeBSD, this only > solves half of the security problem: Unless users and administrators > of FreeBSD systems apply the security patches provided, the advisories > issued accomplish little beyond alerting potential attackers to the > presence of vulnerabilities. > > The Security Team has been concerned for some time by anecdotal reports > concerning the number of FreeBSD systems which are not being promptly > updated or are running FreeBSD releases which have passed their End of > Life dates and are no longer supported. In order to better understand > which FreeBSD versions are in use, how people are (or aren't) keeping > them updated, and why it seems so many systems are not being updated, I > have put together a short survey of 12 questions. The information gathered > will inform the work done by the Security Team, as well as my own personal > work on FreeBSD this summer. > > If you administrate system(s) running FreeBSD (in the broad sense of "are > responsible for keeping system(s) secure and up to date"), please visit > http://people.freebsd.org/~cperciva/survey.html > and complete the survey below before May 31st, 2006. > > Thanks, > Colin Percival > FreeBSD Security Officer > _______________________________________________ > 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" The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 08:24:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1100616A423 for ; Mon, 22 May 2006 08:24:12 +0000 (UTC) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-174-86.sn2.eutelia.it [83.211.174.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DEAD43D4C for ; Mon, 22 May 2006 08:24:10 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 2AB0E2C90C for ; Mon, 22 May 2006 10:24:09 +0200 (CEST) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 1D3342C90A; Mon, 22 May 2006 10:24:07 +0200 (CEST) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id CE9122C906; Mon, 22 May 2006 10:24:06 +0200 (CEST) From: Massimo Lusetti To: Scott Long In-Reply-To: <44714FBB.4000603@samsco.org> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Mon, 22 May 2006 10:24:06 +0200 Message-Id: <1148286246.4303.3.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd security , FreeBSD Stable , Colin Percival , Brent Casavant Subject: Re: FreeBSD Security Survey 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, 22 May 2006 08:24:12 -0000 On Sun, 2006-05-21 at 23:44 -0600, Scott Long wrote: > ports tree in the process, the end result is a bit more undefined. One > thing that I wish for is that the ports tree would branch for releases, > and that those branches would get security updates. I know that this > would involve an exponentially larger amount of effort from the ports > team, and I don't fault them for not doing it. Still, it would be nice > to have. Yes, totally agree. That's the way OpenBSD ports tree works and it worked very well for me. Thus not to say FreeBSD's one didn't, but it takes a lot more attention, which isn't always a bad thing ;) -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Mon May 22 09:40:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 565AE16A420; Mon, 22 May 2006 09:40:18 +0000 (UTC) (envelope-from MH@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F5E643D45; Mon, 22 May 2006 09:40:17 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id 2E7244018; Mon, 22 May 2006 11:40:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at unixoid.de Received: from crivens.terrorteam.de ([127.0.0.1]) by localhost (crivens.unixoid.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prfcLaPDEUtc; Mon, 22 May 2006 11:40:15 +0200 (CEST) Received: from [10.38.0.12] (unknown [213.238.63.253]) by crivens.terrorteam.de (Postfix) with ESMTP id 607F63F99; Mon, 22 May 2006 11:40:15 +0200 (CEST) Message-ID: <44718700.2060102@kernel32.de> Date: Mon, 22 May 2006 11:40:16 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> In-Reply-To: <44714FBB.4000603@samsco.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd security , FreeBSD Stable , Colin Percival , Brent Casavant Subject: Re: FreeBSD Security Survey 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, 22 May 2006 09:40:18 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, Scott Long wrote: > Brent Casavant wrote: > >> While I find ports to be the single most useful feature of the FreeBSD >> experience, and can't thank contributors enough for the efforts, I on >> the other hand find updating my installed ports collection (for security >> reasons or otherwise) to be quite painful. I typically use portupgrade >> to perform this task. On several occasions I got "bit" by doing a >> portupgrade which wasn't able to completely upgrade all dependencies >> (particularly when X, GUI's, and desktops are in the mix -- though I >> always follow the special Gnome upgrade methods when appropriate). >> Like Scott pointed out below, stick with either building from source, or using packages. Mixing them may have strange side effects. To give an example. I usually use portupgrade without using packages. But last time I needed to update my ports (on a production server, though private not corporate server), I used portupgrade -P (to use packages if available). It updated php, using packages, but unluckily the packages were built against apache13. I'm using apache20, so my php installation was trashed. Argh. But even more painful is the fact that portupgrade _always_ fails on some perl modules. Usually p5-XML-Parser. I don't know why, but it's annoying... > ports tree in the process, the end result is a bit more undefined. One > thing that I wish for is that the ports tree would branch for releases, > and that those branches would get security updates. I know that this > would involve an exponentially larger amount of effort from the ports > team, and I don't fault them for not doing it. Still, it would be nice > to have. I have to agree on that statement. I would love to see branched ports. This can get very important on servers, were you don't want to have major upgrades, but only security updates. I guess it's a question of manpower, hm? Would a survey help? As in ask the ports team and FreeBSD administrators? Maybe some will start to become port maintainer too, just to support the increased work on ports due to branching them... I would :) best regards, Marian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEcYb+gAq87Uq5FMsRAvAeAKDY0wCnps8sNKkRqUL0+77/WEh/GgCfayuU /PH2TCKdBC7l9M6TrgY+rZM= =hbzY -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 09:43:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58AD116A45A for ; Mon, 22 May 2006 09:43:36 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EE7843D8F for ; Mon, 22 May 2006 09:43:07 +0000 (GMT) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k4M9h6xh098773 for ; Mon, 22 May 2006 11:43:06 +0200 (CEST) X-Ids: 168 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 36D16A032D for ; Mon, 22 May 2006 11:43:05 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id 2C46633; Mon, 22 May 2006 11:43:05 +0200 (CEST) Date: Mon, 22 May 2006 11:43:05 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20060522094305.GA70157@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.7.2 (shiva.jussieu.fr [134.157.0.168]); Mon, 22 May 2006 11:43:06 +0200 (CEST) X-Antivirus: scanned by sophie at shiva.jussieu.fr X-Miltered: at shiva.jussieu.fr with ID 447187AA.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: FreeBSD Security Survey 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, 22 May 2006 09:43:36 -0000 >> ports tree in the process, the end result is a bit more undefined. One >> thing that I wish for is that the ports tree would branch for releases, >> and that those branches would get security updates. I know that this >> would involve an exponentially larger amount of effort from the ports >> team, and I don't fault them for not doing it. Still, it would be nice >> to have. > >Yes, totally agree. >That's the way OpenBSD ports tree works and it worked very well for me. >Thus not to say FreeBSD's one didn't, but it takes a lot more attention, >which isn't always a bad thing ;) OpenBSD doesn't have next to 15000 ports. In my opinion, this richness is one of the main assets of FreeBSD, and by necessity implies a great difficulty to maintain everything in a coherent and secure state. You have only to contemplate the years it took to release Debian Sarge to convince yourself. Personnally i am quite pleased with the present state of the FreeBSD ports, i think it is in a much better state than a couple of years before, and for my own use, security is a very secondary issue. People who have machines exposed on the internet usually have a small number of ports installed, and can maintain them in the latest secure version. I have around 600 ports installed on my 6.1 machine, which will certainly grow in time, and no intention whatsoever to run portupgrade on that. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:02:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDA8F16A422 for ; Mon, 22 May 2006 10:02:43 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0FC8C43D45 for ; Mon, 22 May 2006 10:02:42 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 22 May 2006 10:02:38 -0000 Received: from p50911DCF.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.29.207] by mail.gmx.net (mp038) with SMTP; 22 May 2006 12:02:38 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id F18282006BF for ; Mon, 22 May 2006 12:02:16 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12751-17 for ; Mon, 22 May 2006 12:02:15 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 06152200B91; Mon, 22 May 2006 12:02:15 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <44714FBB.4000603@samsco.org> (Scott Long's message of "Sun, 21 May 2006 23:44:27 -0600") References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Mon, 22 May 2006 12:02:14 +0200 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:02:44 -0000 Scott Long writes: > I share this frustration with you. I was once told that the pain in > upgrading is due largely to a somewhat invisible difference between > installing a pre-compiled package, and building+installing a port. In > theory, if you stick to one method or the other, things will stay mostly > consistent. But if you mix them, and particularly if you update the > ports tree in the process, the end result is a bit more undefined. One > thing that I wish for is that the ports tree would branch for releases, > and that those branches would get security updates. I know that this > would involve an exponentially larger amount of effort from the ports > team, and I don't fault them for not doing it. Still, it would be nice > to have. Speaking as a port maintainer, if these branches would allow to just "MFC" updates from HEAD that are proven and meet dependency requirements for the new version, I think I'd be able to handle this. The major ports for concern I maintain (db3* db4*) have forked minor versions for compatibility anyways. If it's a "bugfix only" policy that may involve ripping out the minimum fix out of a larger patch set, it'll pretty much be a non-starter for me unless someone funds that work. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:11:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACC1016A41F for ; Mon, 22 May 2006 10:11:53 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D3B3D43D48 for ; Mon, 22 May 2006 10:11:52 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 22 May 2006 10:11:48 -0000 Received: from p50911DCF.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.29.207] by mail.gmx.net (mp029) with SMTP; 22 May 2006 12:11:48 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 210542006BF for ; Mon, 22 May 2006 12:11:13 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12751-20 for ; Mon, 22 May 2006 12:11:11 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 9419F200B91; Mon, 22 May 2006 12:11:11 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <44714FBB.4000603@samsco.org> (Scott Long's message of "Sun, 21 May 2006 23:44:27 -0600") References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Mon, 22 May 2006 12:11:11 +0200 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Subject: port vs. packages vs. FreeBSD updating (was: FreeBSD Security Survey) 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, 22 May 2006 10:11:53 -0000 Scott Long writes: > I share this frustration with you. I was once told that the pain in > upgrading is due largely to a somewhat invisible difference between > installing a pre-compiled package, and building+installing a port. Well, the last time I saw this as a major issue was when people were innocently attempting to install packages fetched from packages-6-stable .tbz with rcNG scripts, that already expected a 6.1 base system (rcorder(8) migration) on 6\.0-RELEASE(-p.*)? - this failed horribly for some users with services not being started since the new rcNG script naming wasn't at the time supported by the base system. These issues did not ever affect, AFAICS, building ports from source -- however, doing this requires a lot of machine horsepower. Regardless of the creation of a stable ports branch, I'd URGE to add "minimum and maximum OSVERSION required" tags to packages to prevent their being installed on incompatible systems. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:24:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1196E16A4D3 for ; Mon, 22 May 2006 10:24:41 +0000 (UTC) (envelope-from amon@sockar.homeip.net) Received: from sockar.homeip.net (tourist.net8.nerim.net [213.41.176.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F4143D6D for ; Mon, 22 May 2006 10:24:40 +0000 (GMT) (envelope-from amon@sockar.homeip.net) Received: from sockar.homeip.net (localhost [127.0.0.1]) by sockar.homeip.net (8.13.4/8.13.3) with ESMTP id k4MALxfV003082 for ; Mon, 22 May 2006 12:21:59 +0200 (CEST) (envelope-from amon@sockar.homeip.net) Received: (from amon@localhost) by sockar.homeip.net (8.13.4/8.13.3/Submit) id k4MALxcq003081 for freebsd-stable@freebsd.org; Mon, 22 May 2006 12:21:59 +0200 (CEST) (envelope-from amon) Date: Mon, 22 May 2006 12:21:59 +0200 From: Herve Boulouis To: freebsd-stable@freebsd.org Message-ID: <20060522102159.GI56143@ra.aabs> References: <20060522094305.GA70157@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060522094305.GA70157@lpthe.jussieu.fr> User-Agent: Mutt/1.4.2.1i Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:24:43 -0000 Le 22/05/2006 11:43, Michel Talon a écrit: > > OpenBSD doesn't have next to 15000 ports. In my opinion, this richness is > one of the main assets of FreeBSD, and by necessity implies a great difficulty > to maintain everything in a coherent and secure state. You have only to > contemplate the years it took to release Debian Sarge to convince yourself. > Personnally i am quite pleased with the present state of the FreeBSD ports, > i think it is in a much better state than a couple of years before, and > for my own use, security is a very secondary issue. People who have machines > exposed on the internet usually have a small number of ports installed, and > can maintain them in the latest secure version. I have around 600 ports > installed on my 6.1 machine, which will certainly grow in time, and no > intention whatsoever to run portupgrade on that. I completely agree with Michel. The question that I think is missing from the survey is the usage you do of your freebsd installation. All production servers I have (50) use few ports and upgrades (security related or not) are always done by hand. On the other side, I nearly always use precompiled packages on my workstation to save compile time and dependencies headaches. -- Herve Boulouis From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:34:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CCAD16A462; Mon, 22 May 2006 10:34:31 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id CED8643D53; Mon, 22 May 2006 10:34:30 +0000 (GMT) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id 8CE3B1765E; Mon, 22 May 2006 13:34:25 +0300 (EEST) Date: Mon, 22 May 2006 13:34:24 +0300 From: Ion-Mihai "IOnut" Tetcu To: Marian Hettwer Message-ID: <20060522133424.3087acfc@it.buh.tecnik93.com> In-Reply-To: <44718700.2060102@kernel32.de> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_5CY4kOIKwzjAk1s.yC=HJwC"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: FreeBSD Stable , Casavant , freebsd security , Colin Percival , Brent Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:34:33 -0000 --Sig_5CY4kOIKwzjAk1s.yC=HJwC Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 22 May 2006 11:40:16 +0200 Marian Hettwer wrote: > > ports tree in the process, the end result is a bit more undefined. One > > thing that I wish for is that the ports tree would branch for releases, > > and that those branches would get security updates. I know that this > > would involve an exponentially larger amount of effort from the ports > > team, and I don't fault them for not doing it. Still, it would be nice > > to have. > > I have to agree on that statement. I would love to see branched ports. > This can get very important on servers, were you don't want to have > major upgrades, but only security updates. > I guess it's a question of manpower, hm? With the maintainers/commiters/physical_resources we have now this is impossible. Take a look at pav@'s PR stats page: http://www.oook.cz/bsd/prstats/ There are ~1000 new ports PRs per month. The PT Team has managed to close about the same number per month (fewer during the freeze, of course). Currently there are 551 open PRs. 238 in feedback state, etc. > Would a survey help? As in ask the ports team and FreeBSD > administrators? Maybe some will start to become port maintainer too, > just to support the increased work on ports due to branching them... > I would :) There are ~4300 unmaintained ports. Maybe you could start maintaining some of them _now_ ? --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #146: Communications satellite used by the military for star wars --Sig_5CY4kOIKwzjAk1s.yC=HJwC Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcZOwBX6fi0k6KXsRAnfAAJ0YWnJkI9LswFIN7JUQeVhOrIgq6gCfcC+V pypV5rwTzJ/PQFclYYKyoPA= =3KHU -----END PGP SIGNATURE----- --Sig_5CY4kOIKwzjAk1s.yC=HJwC-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:43:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E31916A421; Mon, 22 May 2006 10:43:49 +0000 (UTC) (envelope-from MH@kernel32.de) Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5660D43D45; Mon, 22 May 2006 10:43:48 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.terrorteam.de (Postfix) with ESMTP id DA04D3F39; Mon, 22 May 2006 12:43:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at unixoid.de Received: from crivens.terrorteam.de ([127.0.0.1]) by localhost (crivens.unixoid.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CfEFdTENtU2; Mon, 22 May 2006 12:43:46 +0200 (CEST) Received: from [10.38.0.12] (unknown [213.238.63.253]) by crivens.terrorteam.de (Postfix) with ESMTP id 0FF6D3F29; Mon, 22 May 2006 12:43:46 +0200 (CEST) Message-ID: <447195E3.4000003@kernel32.de> Date: Mon, 22 May 2006 12:43:47 +0200 From: Marian Hettwer User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ion-Mihai \"IOnut\" Tetcu" References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> <20060522133424.3087acfc@it.buh.tecnik93.com> In-Reply-To: <20060522133424.3087acfc@it.buh.tecnik93.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: freebsd security , FreeBSD Stable , Brent Casavant , Colin Percival Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:43:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ion, Ion-Mihai IOnut Tetcu wrote: >>I have to agree on that statement. I would love to see branched ports. >>This can get very important on servers, were you don't want to have >>major upgrades, but only security updates. >>I guess it's a question of manpower, hm? > > > With the maintainers/commiters/physical_resources we have now this is > impossible. That's what I guessed... > Take a look at pav@'s PR stats page: http://www.oook.cz/bsd/prstats/ > There are ~1000 new ports PRs per month. The PT Team has managed to > close about the same number per month (fewer during the freeze, of > course). > Currently there are 551 open PRs. 238 in feedback state, etc. I see... > > >>Would a survey help? As in ask the ports team and FreeBSD >>administrators? Maybe some will start to become port maintainer too, >>just to support the increased work on ports due to branching them... >>I would :) > > > There are ~4300 unmaintained ports. Maybe you could start maintaining > some of them _now_ ? > I'll have a look into my ports tree. Let me guess, ports which are have the maintainer ports@freebsd.org are unmaintained? regards, Marian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEcZXhgAq87Uq5FMsRAnqFAJ4t0fO+uQTk/XRDFvTcA9ZLKuy6PACguig5 qAKibfTgwhzrVojGkHPyvpk= =6eKY -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:47:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8999616A42B; Mon, 22 May 2006 10:47:07 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id F235143D5C; Mon, 22 May 2006 10:47:05 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002582642.msg; Mon, 22 May 2006 11:46:11 +0100 Message-ID: <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Brent Casavant" , "Colin Percival" References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> Date: Mon, 22 May 2006 11:45:57 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Processed: multiplay.co.uk, Mon, 22 May 2006 11:46:11 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Mon, 22 May 2006 11:46:13 +0100 Cc: freebsd security , FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:47:07 -0000 Brent Casavant wrote: > On Sun, 21 May 2006, Colin Percival wrote: > So, in short, that's why *I* rarely update ports for security reasons. > > There are steps that could be taken at the port maintenance level that > would work well for my particular case, however that's beyond the > scope of the survey. Thanks for taking the time put the survey > together, I certainly hope it proves useful. Perfectly put there Brent portupgrade is all very powerful but: * Take an absolute age to do anything but the simplest updates * Often fails and needs significant manual fixing Here its usually 100 times quicker to just do: pkg_info | awk '{print $1}' > packages.txt cat packages.txt | xargs pkg_delete -f cat packages.txt | xargs pkg_add -r This at least brings you up to a known good set. Alternatively I also use something similar but build from ports the problem with that is often the ports need to be built with custom options to get back to how you started so unless you where very maticuls in noting down the options to every port on every machine you installed something often goes wrong :( On good example of portupgrade "going off on one" is a simple upgrade of mtr we dont install any X on our machines so mtr-nox11 is installed. Whenever I've tried portupgrade in the past its always trolled of and started downloading and build the behemoth that is X, CTRL+C hence always ensues and I forget about upgrading until I really HAVE to. Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 10:48:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73BC616A423; Mon, 22 May 2006 10:48:39 +0000 (UTC) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (it.buh.tecnik93.com [81.196.204.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DAFE43D45; Mon, 22 May 2006 10:48:38 +0000 (GMT) (envelope-from itetcu@FreeBSD.org) Received: from it.buh.tecnik93.com (localhost [127.0.0.1]) by it.buh.tecnik93.com (Postfix) with ESMTP id A3B0517660; Mon, 22 May 2006 13:48:37 +0300 (EEST) Date: Mon, 22 May 2006 13:48:37 +0300 From: Ion-Mihai "IOnut" Tetcu To: Marian Hettwer Message-ID: <20060522134837.0b88d705@it.buh.tecnik93.com> In-Reply-To: <447195E3.4000003@kernel32.de> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> <20060522133424.3087acfc@it.buh.tecnik93.com> <447195E3.4000003@kernel32.de> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_A28mgaAKj2kX7rmVPRnBcVV; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: FreeBSD Stable , Casavant , freebsd security , Colin Percival , Brent Subject: Re: FreeBSD Security Survey 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, 22 May 2006 10:48:39 -0000 --Sig_A28mgaAKj2kX7rmVPRnBcVV Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 22 May 2006 12:43:47 +0200 Marian Hettwer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi Ion, >=20 > Ion-Mihai IOnut Tetcu wrote: >=20 > >>I have to agree on that statement. I would love to see branched ports. > >>This can get very important on servers, were you don't want to have > >>major upgrades, but only security updates. > >>I guess it's a question of manpower, hm? > >=20 > >=20 > > With the maintainers/commiters/physical_resources we have now this is > > impossible. > That's what I guessed... And it's not only HR lack problem, we would need more hardware for the package building cluster too. =20 > > Take a look at pav@'s PR stats page: http://www.oook.cz/bsd/prstats/ > > There are ~1000 new ports PRs per month. The PT Team has managed to > > close about the same number per month (fewer during the freeze, of > > course). > > Currently there are 551 open PRs. 238 in feedback state, etc. > I see... >=20 > >=20 > >>Would a survey help? As in ask the ports team and FreeBSD > >>administrators? Maybe some will start to become port maintainer too, > >>just to support the increased work on ports due to branching them... > >>I would :) IMO this could work only with some funding from interested companies. Maybe that could be an idea for a survey. > > There are ~4300 unmaintained ports. Maybe you could start maintaining > > some of them _now_ ? > >=20 > I'll have a look into my ports tree. Let me guess, ports which are have > the maintainer ports@freebsd.org are unmaintained? Yup. Just ' cd /usr/ports/ ; make search key=3Dports@FreeBSD.org ' --=20 IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #324: Your packets were eaten by the terminator --Sig_A28mgaAKj2kX7rmVPRnBcVV Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcZcFBX6fi0k6KXsRAp0lAKCN+mEVZYwdMNGiiYGSrGuvHpxt2QCgtZTH lwqGJK9FqXeSVKtkWrmiDBA= =kv5w -----END PGP SIGNATURE----- --Sig_A28mgaAKj2kX7rmVPRnBcVV-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 13:44:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DD6516AB66 for ; Mon, 22 May 2006 13:44:37 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BBEF43D53 for ; Mon, 22 May 2006 13:44:36 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 2C7C0C153 for ; Mon, 22 May 2006 09:44:35 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 6D51DC448 for ; Mon, 22 May 2006 09:44:15 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 35C5FC3A9 for ; Mon, 22 May 2006 09:44:14 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=qEn0USOXHmoeax0M1SrA4MEzsw3zGoQErwy+a2fFRMJ4VYSrEPoHXWOT6R5PJib7jE+E6vdz41Ofl0VfkEoj8SkReQRU+Dr9qUYwwo9WwHnTJaLwtd8w/GfxoUxvDy+Q; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id 111F0C153 for ; Mon, 22 May 2006 09:44:04 -0400 (EDT) Message-ID: <4471C021.30602@protected-networks.net> Date: Mon, 22 May 2006 09:44:01 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: requests for mbufs denied? 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, 22 May 2006 13:44:41 -0000 On a 6-stable machine with sufficient RAM, i.e. no swapping and 215MB free in 'top', I'm seeing .. imb@sarah:/home/imb# netstat -m 386/529/915 mbufs in use (current/cache/total) 384/254/638/17088 mbuf clusters in use (current/cache/total/max) 384/128 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 864K/640K/1504K bytes allocated to network (current/cache/total) 1405/14/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/6/4528 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 28 calls to protocol drain routines What prompts this behaviour? Do I want/need to "play with" any sysctls to preallocate more space? -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net From owner-freebsd-stable@FreeBSD.ORG Mon May 22 13:49:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 739DF16A5F5 for ; Mon, 22 May 2006 13:49:37 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp104.biz.mail.mud.yahoo.com (smtp104.biz.mail.mud.yahoo.com [68.142.200.252]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E35543D45 for ; Mon, 22 May 2006 13:49:36 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 81110 invoked from network); 22 May 2006 13:49:35 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp104.biz.mail.mud.yahoo.com with SMTP; 22 May 2006 13:49:35 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 4B5006179; Mon, 22 May 2006 09:49:34 -0400 (EDT) X-Virus-Scanned: amavisd-new at noacks.org Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id l5Z-i33uJnpD; Mon, 22 May 2006 09:49:33 -0400 (EDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id F01AB60EB; Mon, 22 May 2006 09:49:32 -0400 (EDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.6/8.13.6) with ESMTP id k4MDnTfD016370; Mon, 22 May 2006 09:49:30 -0400 (EDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <4471C163.9060509@alumni.rice.edu> Date: Mon, 22 May 2006 09:49:23 -0400 From: Jonathan Noack User-Agent: Thunderbird 1.5.0.2 (X11/20060422) MIME-Version: 1.0 To: Marian Hettwer References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> In-Reply-To: <44718700.2060102@kernel32.de> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=991D8195; url=http://www.noacks.org/cert/noackjr.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig619E4558B422EB6C3AE4F158" Cc: FreeBSD Stable , Brent Casavant , Colin Percival Subject: Re: FreeBSD Security Survey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:49:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig619E4558B422EB6C3AE4F158 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 05/22/06 05:40, Marian Hettwer wrote: > Scott Long wrote: >>> Brent Casavant wrote: >>>> While I find ports to be the single most useful feature of the FreeB= SD >>>> experience, and can't thank contributors enough for the efforts, I o= n >>>> the other hand find updating my installed ports collection (for secu= rity >>>> reasons or otherwise) to be quite painful. I typically use portupgr= ade >>>> to perform this task. On several occasions I got "bit" by doing a >>>> portupgrade which wasn't able to completely upgrade all dependencies= >>>> (particularly when X, GUI's, and desktops are in the mix -- though I= >>>> always follow the special Gnome upgrade methods when appropriate). >=20 > Like Scott pointed out below, stick with either building from source, o= r > using packages. Mixing them may have strange side effects. > To give an example. > I usually use portupgrade without using packages. But last time I neede= d > to update my ports (on a production server, though private not corporat= e > server), I used portupgrade -P (to use packages if available). > It updated php, using packages, but unluckily the packages were built > against apache13. I'm using apache20, so my php installation was > trashed. Argh. > But even more painful is the fact that portupgrade _always_ fails on > some perl modules. Usually p5-XML-Parser. I don't know why, but it's > annoying... Dropping security@... Odd, I just did a 'portupgrade -fm "-s" p5-XML-Parser' and it worked fine. Note that I included the '-m "-s"' because it sometimes causes port build breakage for me (postfix comes to mind). Perhaps a 'portupgrade -Rf p5-XML-Parser' is in order? The only dependencies are perl and expat, so a recursive rebuild shouldn't take too long. My persistent port build breakages (that weren't caused by an error in the port) have always been resolved by rebuilding all dependencies or removing '-m "-s"'. -Jonathan --=20 Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 --------------enig619E4558B422EB6C3AE4F158 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.3 (FreeBSD) iD8DBQFEccFpUFz01pkdgZURAsWPAJ9US1u6lNSmqX9uBrJYrcjamJaTqgCePsiQ 5G7ndZr4VGCci+dOBHtW+pY= =OIjd -----END PGP SIGNATURE----- --------------enig619E4558B422EB6C3AE4F158-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 14:14:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE28F16AAF8 for ; Mon, 22 May 2006 14:14:33 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp107.biz.mail.mud.yahoo.com (smtp107.biz.mail.mud.yahoo.com [68.142.200.255]) by mx1.FreeBSD.org (Postfix) with SMTP id 2615043D7C for ; Mon, 22 May 2006 14:13:28 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 56403 invoked from network); 22 May 2006 14:12:41 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp107.biz.mail.mud.yahoo.com with SMTP; 22 May 2006 14:12:40 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id DD4BD6143; Mon, 22 May 2006 10:12:38 -0400 (EDT) X-Virus-Scanned: amavisd-new at noacks.org Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iWo+yoC0YJcA; Mon, 22 May 2006 10:12:37 -0400 (EDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id 73D9660E8; Mon, 22 May 2006 10:12:37 -0400 (EDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.6/8.13.6) with ESMTP id k4MECaKY016462; Mon, 22 May 2006 10:12:37 -0400 (EDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <4471C6CE.2020302@alumni.rice.edu> Date: Mon, 22 May 2006 10:12:30 -0400 From: Jonathan Noack User-Agent: Thunderbird 1.5.0.2 (X11/20060422) MIME-Version: 1.0 To: Steven Hartland References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> In-Reply-To: <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=991D8195; url=http://www.noacks.org/cert/noackjr.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig11573943D80BEA6AF373051A" Cc: FreeBSD Stable , Colin Percival , Brent Casavant Subject: Re: FreeBSD Security Survey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 14:14:35 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig11573943D80BEA6AF373051A Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 05/22/06 06:45, Steven Hartland wrote: > Brent Casavant wrote: >> On Sun, 21 May 2006, Colin Percival wrote: >=20 >> So, in short, that's why *I* rarely update ports for security reasons.= >> >> There are steps that could be taken at the port maintenance level that= >> would work well for my particular case, however that's beyond the >> scope of the survey. Thanks for taking the time put the survey >> together, I certainly hope it proves useful. >=20 > Perfectly put there Brent portupgrade is all very powerful but: > * Take an absolute age to do anything but the simplest updates > * Often fails and needs significant manual fixing >=20 > Here its usually 100 times quicker to just do: > pkg_info | awk '{print $1}' > packages.txt > cat packages.txt | xargs pkg_delete -f > cat packages.txt | xargs pkg_add -r >=20 > This at least brings you up to a known good set. Alternatively I > also use something similar but build from ports the problem with > that is often the ports need to be built with custom options to get > back to how you started so unless you where very maticuls in > noting down the options to every port on every machine you > installed something often goes wrong :( Dropping security@... The OPTIONS feature stores port preferences and helps a lot with this. Not all ports are converted yet, but that's just a matter of time. My only complaint is that when options are added I'm not prompted for my preference (I just get the default value). I have to go back and manually "make config" if I don't want the default. If automatic prompting for new options is added then we will truly have a "set it and forget it" configuration system. Because I track ports fairly closely and usually catch new options, this hasn't annoyed me enough to fix it...= > On good example of portupgrade "going off on one" is a simple > upgrade of mtr we dont install any X on our machines so mtr-nox11 > is installed. Whenever I've tried portupgrade in the past its > always trolled of and started downloading and build the behemoth > that is X, CTRL+C hence always ensues and I forget about upgrading > until I really HAVE to. You have to tell the ports system you don't want X (put the following in /etc/make.conf): WITHOUT_X11=3D yes There are also ports (like bittorrent) that install GUIs by default. You should also tell the ports system you don't want GUIs: WITHOUT_GUI=3D yes Some ports will still need the X libs (like graphviz), but that's not a huge deal. -Jonathan --=20 Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 --------------enig11573943D80BEA6AF373051A 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.3 (FreeBSD) iD8DBQFEccbUUFz01pkdgZURAmVkAJ9/XsifsxRIqcA10KpHMEHB7CcR2ACgjVQH u9KWRmjiUymjfBzTziowBww= =fDhe -----END PGP SIGNATURE----- --------------enig11573943D80BEA6AF373051A-- From owner-freebsd-stable@FreeBSD.ORG Mon May 22 14:45:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F82816A5D1 for ; Mon, 22 May 2006 14:45:29 +0000 (UTC) (envelope-from chowse@charter.net) Received: from mxsf20.cluster1.charter.net (mxsf20.cluster1.charter.net [209.225.28.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8937243D72 for ; Mon, 22 May 2006 14:45:21 +0000 (GMT) (envelope-from chowse@charter.net) Received: from mxip04a.cluster1.charter.net (mxip04a.cluster1.charter.net [209.225.28.134]) by mxsf20.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id k4MEjIUD008219 for ; Mon, 22 May 2006 10:45:19 -0400 Received: from 24-176-104-160.dhcp.jcsn.tn.charter.com (HELO [192.168.254.3]) ([24.176.104.160]) by mxip04a.cluster1.charter.net with ESMTP; 22 May 2006 10:45:17 -0400 X-IronPort-AV: i="4.05,157,1146456000"; d="scan'208"; a="1664676820:sNHT56995482" Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <4471C6CE.2020302@alumni.rice.edu> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> <4471C6CE.2020302@alumni.rice.edu> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Charles Howse Date: Mon, 22 May 2006 09:45:16 -0500 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) Subject: Re: FreeBSD Security Survey 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, 22 May 2006 14:45:34 -0000 On May 22, 2006, at 9:12 AM, Jonathan Noack wrote: > On 05/22/06 06:45, Steven Hartland wrote: >> Brent Casavant wrote: >>> On Sun, 21 May 2006, Colin Percival wrote: >> >>> So, in short, that's why *I* rarely update ports for security >>> reasons. >>> >>> There are steps that could be taken at the port maintenance level >>> that >>> would work well for my particular case, however that's beyond the >>> scope of the survey. Thanks for taking the time put the survey >>> together, I certainly hope it proves useful. >> >> Perfectly put there Brent portupgrade is all very powerful but: >> * Take an absolute age to do anything but the simplest updates >> * Often fails and needs significant manual fixing >> >> Here its usually 100 times quicker to just do: >> pkg_info | awk '{print $1}' > packages.txt >> cat packages.txt | xargs pkg_delete -f >> cat packages.txt | xargs pkg_add -r >> >> This at least brings you up to a known good set. Alternatively I >> also use something similar but build from ports the problem with >> that is often the ports need to be built with custom options to get >> back to how you started so unless you where very maticuls in >> noting down the options to every port on every machine you >> installed something often goes wrong :( > > Dropping security@... > > The OPTIONS feature stores port preferences and helps a lot with this. > Not all ports are converted yet, but that's just a matter of time. My > only complaint is that when options are added I'm not prompted for my > preference (I just get the default value). I have to go back and > manually "make config" if I don't want the default. If automatic > prompting for new options is added then we will truly have a "set > it and > forget it" configuration system. Because I track ports fairly closely > and usually catch new options, this hasn't annoyed me enough to fix > it... > >> On good example of portupgrade "going off on one" is a simple >> upgrade of mtr we dont install any X on our machines so mtr-nox11 >> is installed. Whenever I've tried portupgrade in the past its >> always trolled of and started downloading and build the behemoth >> that is X, CTRL+C hence always ensues and I forget about upgrading >> until I really HAVE to. > > You have to tell the ports system you don't want X (put the > following in > /etc/make.conf): > WITHOUT_X11= yes > > There are also ports (like bittorrent) that install GUIs by default. > You should also tell the ports system you don't want GUIs: > WITHOUT_GUI= yes > > Some ports will still need the X libs (like graphviz), but that's > not a > huge deal. Just curious, where are WITHOUT_X11 and WITHOUT_GUI documented? I don't see either in /usr/share/examples/etc/make.conf, nor in man make.conf. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 14:52:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E98516B0C1; Mon, 22 May 2006 14:52:20 +0000 (UTC) (envelope-from hans@lambermont.dyndns.org) Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.93.47.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 298BF43D53; Mon, 22 May 2006 14:52:14 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id E10DF22DE02; Mon, 22 May 2006 16:52:12 +0200 (CEST) Date: Mon, 22 May 2006 16:52:12 +0200 To: Paul Allen Message-ID: <20060522145212.GA45694@leia.lambermont.dyndns.org> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <20060522061722.GA28128@groat.ugcs.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060522061722.GA28128@groat.ugcs.caltech.edu> User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) Cc: FreeBSD Stable , freebsd-ports@freebsd.org Subject: Re: FreeBSD Security Survey 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, 22 May 2006 14:52:30 -0000 Paul Allen wrote: ... > Some speculation: I've always thought portupgrade did the Wrong > Thing(tm) by consulting the dependency graph in /var/db. Better to > merely learn which packages were installed and then exclusively use > the port information... Well, a.o. portmaster tries just to do that. Have a look at sysutils/portmaster as an alternative to sysutils/portupgrade. I think follow-ups should go to the freebsd-ports list. regards, Hans Lambermont From owner-freebsd-stable@FreeBSD.ORG Mon May 22 15:14:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5E1A16B382 for ; Mon, 22 May 2006 15:14:50 +0000 (UTC) (envelope-from anonymous@sefao.com) Received: from do.sefao.com (do.sefao.com [66.45.33.203]) by mx1.FreeBSD.org (Postfix) with SMTP id C7A9C43D78 for ; Mon, 22 May 2006 15:14:49 +0000 (GMT) (envelope-from anonymous@sefao.com) Received: (qmail 10729 invoked by uid 80); 22 May 2006 15:20:11 -0000 Date: 22 May 2006 15:20:11 -0000 Message-ID: <20060522152011.10728.qmail@do.sefao.com> From: "FreeBSD User" To: freebsd security FreeBSD Stable X-Mailer: SEFAO Collaboration Suite 2.5 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: RE: Re: FreeBSD Security Survey 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, 22 May 2006 15:14:56 -0000 As an administrator, time is always an issue. FreeBSD has proven itself time and again. Having said that, one "wish" would be to have a default/built-in security update mechanism. Since time is always and issue, if the system could by default (without an admin having to write scripts and/or apps, or manually update) update itself for both system and installed ports/packages, it likely would reduce security issues exponentially. This of course would be a massive project/challenge. Varying system and kernel configurations alone would make this a huge challenge, not to mention the potential security implications. The survey is a great idea. I suggest adding a section for administrators to add comments and/or "wishes". Sejo Brent Casavant wrote: > On Sun, 21 May 20 06, Colin Percival wrote: > > >>In order to better understand >>which FreeBSD versions are in use, how people are (or aren´t) keeping >>them updated, and why it seems so many systems are not being updated, I >>have put together a short survey of 12 questions. > > > I applaud this survey, however question 9 missed an important point, > at least to me. I was torn between answering "less than once a month" > and "I never update". > > While I find ports to be the single most useful feature of the FreeBSD > experience, and can´t thank contributors enough for the efforts, I on > the other hand find updating my installed ports collection (for security > reasons or otherwise) to be quite painful. I typically use portupgrade > to perform this task. On several occasions I got "bit" by doing a > portupgrade which wasn´t able to completely upgrade all dependencies > (particularly when X, GUI´s, and desktops are in the mix -- though I > always follow the special Gnome upgrade methods when appropriate). > > I can´t rule out some form of pilot error, but the end result was pain. > > After several instances of unsatisfactory portupgrades (mostly in the > 5.2 through early 5.4 timeframe), I adopted the practice of either not > upgrading ports at all for the life of a particular installation on a > machine (typically about one year), or when necessary by removing *all* > ports from the machine, cvsup´ing, and reinstalling. This has served > me quite well, particularly considering the minimal threat profile these > particularly systems face. > > So, in short, that´s why *I* rarely update ports for security reasons. > > There are steps that could be taken at the port maintenance level that > would work well for my particular case, however that´s beyond the scope > of the sur vey. Thanks for taking the time put the survey together, I > certainly hope it proves useful. > > Thank you, > Brent Casavant I share this frustration with you. I was once told that the pain in upgrading is due largely to a somewhat invisible difference between installing a pre-compiled package, and building+installing a port. In theory, if you stick to one method or the other, things will stay mostly consistent. But if you mix them, and particularly if you update the ports tree in the process, the end result is a bit more undefined. One thing that I wish for is that the ports tree would branch for releases, and that those branches would get security updates. I know that this would involve an exponentially larger amount of effort from the ports team, and I don´t fault them for not doing it. Still, it would be nice to have. Scott _____________________________________ __________ 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 Mon May 22 15:46:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9FA916B374 for ; Mon, 22 May 2006 15:46:25 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54CF743D7D for ; Mon, 22 May 2006 15:46:23 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id 495A159; Mon, 22 May 2006 17:46:21 +0200 (CEST) Message-ID: <4471DCCC.7020102@quip.cz> Date: Mon, 22 May 2006 17:46:20 +0200 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: cs, cz, en, en-us MIME-Version: 1.0 To: Charles Howse References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> <4471C6CE.2020302@alumni.rice.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 15:46:34 -0000 Charles Howse wrote: > > Just curious, where are WITHOUT_X11 and WITHOUT_GUI documented? I > don't see either in /usr/share/examples/etc/make.conf, nor in man > make.conf. Many options (not all) are described in /usr/ports/KNOBS (but withou WITH_/WITHOUT_ prefixes) Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Mon May 22 15:46:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BCE816B66E; Mon, 22 May 2006 15:46:56 +0000 (UTC) (envelope-from gorebofh@comcast.net) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.200.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC8F43D68; Mon, 22 May 2006 15:46:54 +0000 (GMT) (envelope-from gorebofh@comcast.net) Received: from hp.org (c-69-246-87-201.hsd1.mi.comcast.net[69.246.87.201]) by comcast.net (sccrmhc14) with ESMTP id <2006052215465301400kttjme>; Mon, 22 May 2006 15:46:53 +0000 Received: by HP.org (Postfix, from userid 1000) id 44B26507E8; Mon, 22 May 2006 11:49:34 -0400 (EDT) Date: Mon, 22 May 2006 11:49:34 -0400 From: Allen To: freebsd-security@freebsd.org, FreeBSD Stable Message-ID: <20060522154934.GB16937@HP.hsd1.mi.comcast.net> Mail-Followup-To: freebsd-security@freebsd.org, FreeBSD Stable References: <4471361B.5060208@freebsd.org> <2DB25B04-BCE6-41D2-9D95-03C58A493E2C@ece.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2DB25B04-BCE6-41D2-9D95-03C58A493E2C@ece.cmu.edu> User-Agent: Mutt/1.5.9i Cc: Subject: Re: FreeBSD Security Survey 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, 22 May 2006 15:47:04 -0000 On Mon, May 22, 2006 at 12:06:54AM -0400, Brandon S. Allbery KF8NH wrote: > > On May 21, 2006, at 11:55 , Colin Percival wrote: > > >The Security Team has been concerned for some time by anecdotal > >reports > >concerning the number of FreeBSD systems which are not being promptly > >updated or are running FreeBSD releases which have passed their End of > >Life dates and are no longer supported. In order to better understand > >which FreeBSD versions are in use, how people are (or aren't) keeping > >them updated, and why it seems so many systems are not being > >updated, I > > I have a 6-STABLE box that is not going to be updated to 6.1 any time > soon, because my personal mail will have to be offline while I do so > --- including nuking and rebuilding all ports because the ports tree > has been thrashed by multiple low level updates that affect a large > percentage of the tree --- and it's only a 600MHz box so it will be > offline for most of a week during that upgrade. And I'm uncertain > how downgrading it to 6.0-RELEASE+security patches will complicate > things (downgrading via cvsup/buildworld is not a supported option, > last I checked). Granted, I probably should have stuck with 6.0-R > --- but then, experience has shown me that the more reliable option > is to wait a week or two after release and then install -STABLE. > > In short: keeping FreeBSD up to date tends to be painful at best. I'd have to agree, though it's much better than some systems, it's still something I'd like to see some improvement on. For example, I understand the reasons for how Free BSD does things, I do. However, one thing I'd love to see is a much better tool for handling updates and upgrades. I may get reamed for what I'm about to say, but I'm willing to deal with whatever happens with this: I'd like to see Free BSD include an approach to updates in the way Slackware Linux does... Now before I get 10,000 emails saying I'm stupid or something to that effect let me explain: I've been using supporting and telling about Free BSD for many years. When I got my first computer, I had installed Free BSD not long after and that was coming from Windows 95 / 98 SE. One thing that always made me mad was when a new security flaw came out. On my Slackware machines, it was no problem at all, I'd use wget to grab the patch .tgz file, then do this: upgradepkg *.tgz I'd go get coffee or somethign and come back to all patches being installed. I know about portupgrade, and it's a good start, but I think there would be huge benifit from a tool that allows you to download a tgz file and doing the above to install patches. A lot of Linux only users I know would use Free BSD if the patching system was something more Slackware like. And I don't consider it a rip off to make a system like that because well, Slackware is a supporter of BSD. The Slackware Essentials book I bought has BSD on the back of it and BSD is also listed as a supporter of Slackware, so I see no Moral problem with creating something for Free BSD that would allow this. >From what I've seen in portupgrade, you have to use a key... Which is nice and all, but it defeats the purpose when I've personally seens omeone say "Ugh you have to do all this just to set up portupgrade? and you have to recompile the Kernel for that Telnet update????"... Explanations as to why don't work. I just personally feel there would be a lot more boxes getting patches installed if you could do it like Slackware, or Linux in general, and allow for patches that you just install with one command. RedHat and some other distros use RPM, and they have their own update tools, but if you wanted you could just download the RPMs and do rpm -U to update. Slackware I've shown already. It's a good system. >From what I've understood, Free BSD doesn't usually do binarys.... I could be wrong here as I'm no positive... But I really think it would be for the best if there was something added to Free BSD where you could juts install patches the way you do Linux. I mean you wouldn't have to remove the other system that is in use now, and as I saiud portupgrade is a good start, however for the people I talk to it doesn't seem to be enough. I'd love to see somethign like this added into Free BSD where for the people who like the updates the way they are now could keep using that way, and for the new comers and people who aren't used to it, they could use the other way. Like Is aid Linux has two ways, you can use an update tool like Redhat's up2date, or you can download the RPMs yourself. Slackware has Swaret, slackpkg, and slapt-get, or you can simply download the patches which are already .tgz files, and use upgradepkg to install them. I think the benifits would be great and more people would use it if they knew when a new security problem came out in Free BSD all they had to do was download a patch and type upgradepkg, or type patch and it installed like this. And then a front end could be done where you had a GUI to use for this too, And think of how many new users would be using it when they knew how easy it was? I support Free BSD either way, I buy books, and I buy the CD sets to help out. And I will continue using it either way, I just would love tos ee somethign like this implemented. As would a lot of others in my area. I'd do it all myself and release it if I could code good enough to do something like this but until I can I can at least point out a good idea. -Allen. Buying Free BSD power paks since 4.0 > -- > brandon s. allbery [linux,solaris,freebsd,perl] > allbery@kf8nh.com > system administrator [openafs,heimdal,too many hats] > allbery@ece.cmu.edu > electrical and computer engineering, carnegie mellon university > KF8NH > > > > _______________________________________________ > 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 May 22 16:14:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E7AE16B426 for ; Mon, 22 May 2006 16:14:31 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB69B43D7F for ; Mon, 22 May 2006 16:14:21 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id 653165880B; Mon, 22 May 2006 09:14:20 -0700 (PDT) Date: Mon, 22 May 2006 09:14:20 -0700 From: Paul Allen To: Doug Hardie Message-ID: <20060522161420.GB28128@groat.ugcs.caltech.edu> References: <4471361B.5060208@freebsd.org> <66DF01E1-277C-42EE-896E-1E7F4C2ABDDE@lafn.org> <44714F23.6000504@datalinktech.com.au> <2CBCDBD0-CC9F-4B9A-BC79-9F248DFE7A3F@lafn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2CBCDBD0-CC9F-4B9A-BC79-9F248DFE7A3F@lafn.org> Sender: jd@ugcs.caltech.edu Cc: freebsd-stable@freebsd.org, David Nugent Subject: Re: FreeBSD Security Survey 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, 22 May 2006 16:14:38 -0000 >From Doug Hardie , Sun, May 21, 2006 at 11:48:51PM -0700: > Failover sounds good in theory but has significant issues in practice > that make it sometimes worse than the alternative. Take mail > spools. If you failover, mail the user saw before has disappeared. > Then when you "fail back" it reappears and newer messages disappear. > This is hardly unnoticable. My users do not find that at all > acceptable. Putting the mail spools on a different machine just > moves that problem to the different machine. Trying to keep multiple > spools consistent has problems also. I have watched raid system lose It's a hard problem that's why you buy a box to do it: http://www.emc-rainwall.com Rainfinity (recently bought by EMC) has patents on actual peer-reviewed data-replication algorithms. Paul From owner-freebsd-stable@FreeBSD.ORG Mon May 22 17:00:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D6BD16A49A for ; Mon, 22 May 2006 17:00:36 +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 0C64743D45 for ; Mon, 22 May 2006 17:00:36 +0000 (GMT) (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 14E4B46C0B; Mon, 22 May 2006 13:00:35 -0400 (EDT) Date: Mon, 22 May 2006 18:00:35 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael Butler In-Reply-To: <4471C021.30602@protected-networks.net> Message-ID: <20060522175934.T32297@fledge.watson.org> References: <4471C021.30602@protected-networks.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: requests for mbufs denied? 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, 22 May 2006 17:00:37 -0000 On Mon, 22 May 2006, Michael Butler wrote: > On a 6-stable machine with sufficient RAM, i.e. no swapping and 215MB free > in 'top', I'm seeing .. > > imb@sarah:/home/imb# netstat -m > 386/529/915 mbufs in use (current/cache/total) > 384/254/638/17088 mbuf clusters in use (current/cache/total/max) > 384/128 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) > 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) > 864K/640K/1504K bytes allocated to network (current/cache/total) > 1405/14/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/6/4528 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 28 calls to protocol drain routines > > What prompts this behaviour? Do I want/need to "play with" any sysctls to > preallocate more space? This is believed to be a result of an error in the statistics measurement logic in UMA. I've committed the attached patch to the CVS HEAD, and am looking for feedback over the next couple of weeks before merging to RELENG_6 (and possibly the errata branches). Any testing and reports of success or failure would be most welcome. Robert N M Watson Index: uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.136 diff -u -r1.136 uma_core.c --- uma_core.c 11 Feb 2006 19:20:56 -0000 1.136 +++ uma_core.c 21 May 2006 19:25:56 -0000 @@ -2413,8 +2413,7 @@ * If nothing else caught this, we'll just do an internal free. */ zfree_internal: - uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | - ZFREE_STATFREE); + uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); return; } From owner-freebsd-stable@FreeBSD.ORG Mon May 22 17:42:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB11616AA1E; Mon, 22 May 2006 17:42:26 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A33D943D69; Mon, 22 May 2006 17:42:18 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 5F484C343; Mon, 22 May 2006 13:42:17 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id B38F9C332; Mon, 22 May 2006 13:42:09 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 3F2C2C2FA; Mon, 22 May 2006 13:42:09 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=XcDLK0FsxbRPHLGFwZz+lCw14hqY4Ae3M3wpePEUbMrlqy5BnXTTJLSf1O4fxFKO+fO71/IZcLMUeW9K6hEoautpqwwY+Se/j8hfExGCzzl3z4pO1LlqDab35EjkpRmi; Received: from [192.168.1.11] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) by aaron.protected-networks.net (Postfix) with ESMTP id A75E7C2F8; Mon, 22 May 2006 13:42:06 -0400 (EDT) Message-ID: <4471F7EC.1080301@protected-networks.net> Date: Mon, 22 May 2006 13:42:04 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Robert Watson References: <4471C021.30602@protected-networks.net> <20060522175934.T32297@fledge.watson.org> In-Reply-To: <20060522175934.T32297@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: requests for mbufs denied? 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, 22 May 2006 17:42:29 -0000 Robert Watson wrote: > This is believed to be a result of an error in the statistics > measurement logic in UMA. I've committed the attached patch to the > CVS HEAD, and am looking for feedback over the next couple of weeks > before merging to RELENG_6 (and possibly the errata branches). Any > testing and reports of success or failure would be most welcome. I've just installed the RELENG_6 equivalent of this patch (below) on 3 machines and will let you know if I see anything untoward, *** uma_core.c.orig Tue Feb 14 08:16:40 2006 --- uma_core.c Mon May 22 13:09:26 2006 *************** *** 2417,2424 **** * If nothing else caught this, we'll just do an internal free. */ zfree_internal: ! uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | ! ZFREE_STATFREE); return; } --- 2417,2423 ---- * If nothing else caught this, we'll just do an internal free. */ zfree_internal: ! uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); return; } -- Michael Butler, CISSP Security Architect Protected Networks http://www.protected-networks.net From owner-freebsd-stable@FreeBSD.ORG Mon May 22 19:23:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8004816A91F; Mon, 22 May 2006 19:23:54 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5DEA43D49; Mon, 22 May 2006 19:23:53 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k4MJNpbD005734 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 May 2006 05:23:51 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k4MJNped002458; Tue, 23 May 2006 05:23:51 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k4MJNpGr002457; Tue, 23 May 2006 05:23:51 +1000 (EST) (envelope-from peter) Date: Tue, 23 May 2006 05:23:50 +1000 From: Peter Jeremy To: FreeBSD User Message-ID: <20060522192350.GB712@turion.vk2pj.dyndns.org> References: <20060522152011.10728.qmail@do.sefao.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060522152011.10728.qmail@do.sefao.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd security , FreeBSD Stable Subject: Re: FreeBSD Security Survey 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, 22 May 2006 19:23:55 -0000 On Mon, 2006-May-22 15:20:11 -0000, FreeBSD User wrote: > Since time is always and issue, if the system could by default > (without an admin having to write scripts and/or apps, or manually > update) update itself for both system and installed ports/packages, it > likely would reduce security issues exponentially. I think it would substantially reduce the reliability and security. Firstly, automatically installing arbitrary "fixes" on a production system is almost always a bad idea. The release engineering and security teams do regression testing but can't test exactly your system configuration and there's a non-trivial likelihood that installing patch X will break something that your configuration relies on. This can be mitigated by using a test system and rolling out the updates from it, but that negates the whole point. It's also likely to inconvenience users. Our ITS department take it upon themselves to automatically roll out (wintel) desktop updates. This almost always results in your desktop machine insisting that it needs to be rebooted immediately when you are in the middle of doing something crucial - thus breaking your concentration and potentially losing data (my manager managed to lose 3 man-hours work once). I, for one, would hate it if my FreeBSD boxes started doing the same. Specific FreeBSD versions aren't maintained forever. An "install it and forget it" philosophy will increase the number of machines that aren't being patched because they are running unmaintained versions of FreeBSD. With the current approach, the sysadmin is aware that particular machines need to be updated to a newer version. If everyting is automatic, the sysadmin will probably forget. Finally, it only takes one security failure in the update process for someone undesirable to "own" all the FreeBSD machines that have been left in this default mode. Despite the best efforts of FreeBSD developers, FreeBSD will always contain bugs and some of them will be security holes. Any automatic update process needs to balance the benefits of reducing the number of unpatched boxes against the risks of the update system being subverted. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Mon May 22 19:57:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4535716AF17 for ; Mon, 22 May 2006 19:57:50 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F7E443D5A for ; Mon, 22 May 2006 19:57:49 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A75BF.dip.t-dialin.net [84.154.117.191]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k4MJvker087629 for ; Mon, 22 May 2006 21:57:47 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k4MJviGI045751 for ; Mon, 22 May 2006 21:57:45 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k4MK0Ef9005932 for ; Mon, 22 May 2006 22:00:14 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200605222000.k4MK0Ef9005932@fire.jhs.private> To: FreeBSD Stable In-Reply-To: Message from Ion-Mihai "IOnut" Tetcu of "Mon, 22 May 2006 13:48:37 +0300." <20060522134837.0b88d705@it.buh.tecnik93.com> Date: Mon, 22 May 2006 22:00:14 +0200 From: "Julian H. Stacey" Subject: Re: FreeBSD Security Survey 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, 22 May 2006 19:57:57 -0000 > And it's not only HR lack problem, we would need more hardware for the > package building cluster too. A lot of us run 24/7 netted servers with spare cycles, & wouldn't be averse to allocating the idle loop to package building for freebsd.org, but 3 problems: - package building at prsent gets done on that trusted cluster, - needs root for lots of buils, which many of us dont want to give out (sandboxes / chroot maybe ? ) - freebsd.org would need to know none of our client servers had `slipped it a mickey', which would best be protected against by anonymisining I guess, so we didnt even know what we were compiling. - It'd need some mechanised automation, like SETI A nice project for some Summer Of Code student this summer ? -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-stable@FreeBSD.ORG Mon May 22 21:43:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 752B816A8AB for ; Mon, 22 May 2006 21:43:34 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EDDF43D5C for ; Mon, 22 May 2006 21:43:32 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nz-out-0102.google.com with SMTP id l8so1072633nzf for ; Mon, 22 May 2006 14:43:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ctFO1qfBfwSw5llHlIKaGqevTOLzwRFGY5/RKF9b9Jnyan9fK7l60b+Hnje8FYVotisPoeG9VEWwOP7zfIjuk9S14XVx1Ac6rTo8FeYgG9zqxvtnCdKPKSs6K0qIKLENxVbd7p4s9MZ8sEqB9ZJblhQ0AUdJ/Zx05yQUZ/wLRUA= Received: by 10.36.74.10 with SMTP id w10mr1187905nza; Mon, 22 May 2006 14:43:32 -0700 (PDT) Received: by 10.36.60.19 with HTTP; Mon, 22 May 2006 14:43:32 -0700 (PDT) Message-ID: <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> Date: Mon, 22 May 2006 17:43:32 -0400 From: "Rong-en Fan" To: "Howard Leadmon" , "Kris Kennaway" In-Reply-To: <20060515024958.GA99002@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <017301c67784$45377a90$071872cf@Leadmon.local> <20060515024958.GA99002@xor.obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 22 May 2006 21:43:52 -0000 On 5/14/06, Kris Kennaway wrote: > On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: > > > > Hello All, > > > > I have been running FBSD a long while, and actually running since the = 5.x > > releases on the server I am having troubles with. I basically have a = small > > network and just use NIS/NFS to link my various FBSD and Solaris machin= es > > together. > > > > This has all been running fine up till a few days ago, when all of a s= udden > > NFS came to a crawl, and CPU usage so high the box appears to freeze al= most. > > When I had 6.1-RC running all seemed well, then came the announcement f= or the > > official 6.1 release, so I did the cvs updates, made world, kernel, and= ran > > mergemaster to get everything up to the 6.1 stable version. > > > > Now after doing this, something is wrong with NFS. It works, it will= return > > information and open files, just it's very very slow, and while perform= ing a > > request the CPU spike is astounding. A simple du of my home directory = can > > take minutes, and machine all but locks up if the request is done over = NFS. > > Here is top snip: > > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMM= AND > > 497 root 1 4 0 1252K 780K - 2 50:42 188.48% nfs= d > > > > > > This is a nice IBM eServer with dual P4-XEON's and a couple GB or RAM = on a > > disk array, and locally is screams, heck NFS used to scream till I upda= ted. I > > am not really sure what info would be useful in debugging, so won't pos= t tons > > of misc junk in this eMail, but if anyone has any ideas as to how best = to > > figure out and resolve this issue it would sure be appreicated... > > Use tcpdump and related tools to find out what traffic is being sent. > > Also verify that you did not change your system configuration in any > way: there have been no changes to NFS since the release, so it is > unclear why an update would cause the problem to suddenly occur. > > Kris Hi Kris and Howard, As I posted few days ago, I have similar problems like Howard's (some details in the thread "6.1-RELEASE, em0 high interrupt rate and nfsd eats lots of cpu" on stable@). After binary searching the source tree, I found that RELENG_6_1, 2006.04.30.03.57 ok RELENG_6_1, 2006.04.30.04.00 bad The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, the same problem occurs. Let me refresh what problems I'm seeing 1. a client (no matter Linux 2.6.16 or FreeBSD 6.1) runs du on a nfs directory 2. on server-side, nfsd starts to eats lots of CPU 3. the du finishes 4. on server-side, nfsd still eats lots of CPU, but there is no nfs traffic. Wait for 5 minutes, you can still see that nfsd is "running" and eats lots of CPU. On FreeBSD 6.1R client, it uses UDP mount and fstab is like "rw,-L,nosuid,bg,nodev". On Linux cleint, it uses UDP mount and fstab is like "defaults,udp,hard,intr,nfsvers=3D3,rsize=3D8192,wsize=3D8192= ". The server's kernel conf is at http://www.rafan.org/FreeBSD/nfs/KERNEL Some related configuration files: /etc/export /export/dir1 host1 host2... /export/dir2 host1 host2... /etc/rc.conf nfs_server_enable=3D"YES" nfs_server_flags=3D"-u -t -n 16" mountd_enable=3D"YES" mountd_flags=3D"-r -l -n" rpc_lockd_enable=3D"YES" rpc_statd_enable=3D"YES" rpcbind_enable=3D"YES" /etc/fstab: /dev/... /export/dir1 ufs rw,nosuid,noexec 2 2 /dev/... /export/dir2 ufs rw,nosuid,noexec,userquota 2 2 The NFS server is also using amd to mount some backup directories from another NFS server. the amd.conf is [global] browsable_dirs =3D yes map_type =3D file mount_type =3D nfs auto_dir =3D /nfs fully_qualified_hosts =3D no log_file =3D syslog nfs_proto =3D udp nfs_allow_insecure_port =3D no nfs_vers =3D 3 # plock =3D yes selectors_on_default =3D yes restart_mounts =3D yes [/backup] map_options =3D type:=3Ddirect map_name =3D /etc/amd.direct /etc/amd.direct: /defaults opts:=3Drw,grpid,resvport,vers=3D3,proto=3Dudp,nosuid,nodev,rsize=3D8192,ws= ize=3D8192 backup type:=3Dnfs;rhost:=3Dnfs2;rfs:=3D/nfs2/${host} If there are any thing I can provide to help tracking this down. Please let me know. By the way, I tried with truss/kdump to see what happens when nfsd eats lot of CPUs, but in vain. They do not return anything. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Tue May 23 00:18:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5941816AABF for ; Tue, 23 May 2006 00:18:49 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA8343D46 for ; Tue, 23 May 2006 00:18:48 +0000 (GMT) (envelope-from kabaev@gmail.com) Received: by wr-out-0506.google.com with SMTP id i28so1222778wra for ; Mon, 22 May 2006 17:18:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=Ld4EvA3sFp6ZVgt5FqZbaSjCaCUPb0gXws8jXi9y7L44peeAu3NdxS28e8ezZl7YSj9dcDjhF+rFn8Yu1KBJtQhsstJoB8lDQ8+8/1jB8YpBEGaqYDlvLcgUBcvaElEEGyzzdEWifEDCUdaoNToybOKiK4bGUds7J0bUzCa6XMw= Received: by 10.54.104.7 with SMTP id b7mr2777175wrc; Mon, 22 May 2006 17:18:47 -0700 (PDT) Received: from kan.dnsalias.net ( [24.63.93.195]) by mx.gmail.com with ESMTP id 34sm4474495wra.2006.05.22.17.18.46; Mon, 22 May 2006 17:18:47 -0700 (PDT) Date: Mon, 22 May 2006 20:18:56 -0400 From: Alexander Kabaev To: Konstantin Belousov Message-ID: <20060522201856.00332354@kan.dnsalias.net> In-Reply-To: <20060522035055.GH54541@deviant.kiev.zoral.com.ua> References: <1e4841eb0605111757t36fdf8cfv267799a17dffc650@mail.gmail.com> <20060514195510.783fa765@kan.dnsalias.net> <1e4841eb0605152058n69d4e7b8m27d3944d9af8a346@mail.gmail.com> <1e4841eb0605211013u30d83617k73ea8551480a50a9@mail.gmail.com> <20060521211607.GG54541@deviant.kiev.zoral.com.ua> <1e4841eb0605211522n74d79ac9gee392857620e90f1@mail.gmail.com> <20060522035055.GH54541@deviant.kiev.zoral.com.ua> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_1_etZrCBZy3P/9/lj0F+V/P"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org, m m Subject: Re: improper handling of dlpened's C++/atexit() code? 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, 23 May 2006 00:18:54 -0000 --Sig_1_etZrCBZy3P/9/lj0F+V/P Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 22 May 2006 06:50:55 +0300 Konstantin Belousov wrote: > On Sun, May 21, 2006 at 06:22:34PM -0400, m m wrote: > > n 5/21/06, Konstantin Belousov wrote: > > >> >Program received signal SIGSEGV, Segmentation fault. > > >> >0x00000000 in ?? () > > >> >(gdb) bt > > >> >#0 0x00000000 in ?? () > > >> >#1 0x294c0ad8 in __do_global_dtors_aux () from > > >> >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > > >> >#2 0x294c1d4c in _fini () from > > >> >/usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > > >> >#3 0x280b4c80 in ?? () > > >> >#4 0x280aaab8 in ?? () from /libexec/ld-elf.so.1 > > >> >#5 0xbfbfe6e8 in ?? () > > >> >#6 0x2808dca6 in objlist_call_fini (list=3D0x280a96d8) at > > >> >/usr/src/libexec/rtld-elf/rtld.c:1336 > > >> >#7 0x2808e1d4 in rtld_exit () > > >> >at /usr/src/libexec/rtld-elf/rtld.c:1528 #8 0x281d58ea in > > >> >__cxa_finalize (dso=3D0x0) > > >> >at /usr/src/lib/libc/stdlib/atexit.c:184 #9 0x281d55ba in exit > > >> >(status=3D0) at /usr/src/lib/libc/stdlib/exit.c:69 #10 0x0805d0cb > > >> >in clean_child_exit () #11 0x0805ea77 in just_die () > > >> >#12 0x0805ea9a in usr1_handler () > > >> >#13 0xbfbfffb4 in ?? () > > >> >#14 0x0000001e in ?? () > > >> >#15 0x00000000 in ?? () > > >> >#16 0xbfbfe7c0 in ?? () > > >> >#17 0x00000002 in ?? () > > >> >#18 0x0805ea80 in just_die () > > >> >#19 0x0806011e in child_main () > > >> >#20 0x080607de in make_child () > > >> >#21 0x08060868 in startup_children () > > >> >#22 0x08060e81 in standalone_main () > > >> >#23 0x08061702 in main () > > > > > >Could you, please, put somewhere: > > >1. /usr/local/lib/perl5/5.8.8/mach/auto/Sys/Syslog/Syslog.so > > >2. output of lsof -p for apache > > >running in your usual configuration. > > > > > >Also, could you run the apache with > > >LD_PRELOAD=3D/usr/lib/libstdc++.so.5 and report whether the problem > > >persists ? > >=20 > > Konstantin, > > Thank you for looking into this. > >=20 > > lsof: http://www.savefile.com/files/6494253 > > Syslog.so: http://www.savefile.com/files/2163369 > >=20 > > Although it's not an indicator of certainty (I have had it exit > > cleanly in the past), it appears that running Apache with LD_PRELOAD > > of libstdc++ does allow it to exit cleanly. Please let me know how > > I can further assist. If it would make things easier - I can > > provide access to a jail on this machine which exhibits the same > > behavior. >=20 > Ok, I have a theory how it happens. Investigation of your instance > of Syslog.so shows that crash happens at the following code of > /usr/lib/crtbeginS.o: >=20 > 282: if (__deregister_frame_info) > 283: __deregister_frame_info (__EH_FRAME_BEGIN__); >=20 > (this comes in from contrib/gcc/crtstuff.c, lines 282-283). > Symbol __deregister_frame_info is weak and undefined in all your > DSOs except libstdc++.so.5. This symbol provides part of the C++ > runtime support for exception handling, and reasonably included > from c++ runtime support library. >=20 > Both lines 282 and 283 produce dynamic relocations in final DSO, > but line 282 implies R_386_GLOB_DAT, and 283 - R386_JUMP_SLOT (for > PLT). First relocation is resolved immediately on DSO load, second > one is resolved on demand. >=20 > My theory is that, at the time of loading Syslog.so, libstdc++.so.5 > is loaded in the process, resulting in first relocation being > satisfied by rtld immediately. But, at the time exit() processing > comes to _fini() function of Syslog.so, libstdc++.so.5 is unloaded. > And weak PLT relocation is resolved to 0. As result we got the > frame #0 from your trace. >=20 > This theory is confirmed by presence of libstdc++ in lsof output. > Please, check that it does not show up at the time of crash dump > by using "show shared" gdb command on crash dump. >=20 > Short-time fix is to use LD_PRELOAD hack. The real solution > would be to mark the libstdc++ DSO as unloadable and > implement support for unloadable DSO in rtld (BTW, I think > this is also needed for threading libraries libpthread and libthr > for the same reason). I know that glibc dynamic loader has support > for this feature. >=20 > P.S. Apache seems to call exit(3) from the signal handler. This is > wrong. Sounds very plausible to me. This should be fixed once we have shared libgcc_s.so. --=20 Alexander Kabaev --Sig_1_etZrCBZy3P/9/lj0F+V/P Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEclT0Q6z1jMm+XZYRAr7vAJ9UgWaB3f/dYqe5T117Ls08bMG/NQCguvqa FQGGzGN1BQDbdznVQa9/D5E= =RLas -----END PGP SIGNATURE----- --Sig_1_etZrCBZy3P/9/lj0F+V/P-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 00:42:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8612416B06A for ; Tue, 23 May 2006 00:42:01 +0000 (UTC) (envelope-from anonymous@sefao.com) Received: from do.sefao.com (do.sefao.com [66.45.33.203]) by mx1.FreeBSD.org (Postfix) with SMTP id 12C9E43D6E for ; Tue, 23 May 2006 00:41:58 +0000 (GMT) (envelope-from anonymous@sefao.com) Received: (qmail 17237 invoked by uid 80); 23 May 2006 00:47:26 -0000 Date: 23 May 2006 00:47:26 -0000 Message-ID: <20060523004726.17236.qmail@do.sefao.com> From: "FreeBSD User" To: Peter Jeremy X-Mailer: SEFAO Collaboration Suite 2.5 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd security , FreeBSD Stable Subject: RE: Re: FreeBSD Security Survey 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, 23 May 2006 00:42:10 -0000 Should something like automatic security updates not be a goal? If done correctly, and on a per-stable/version basis, it is "possible" to increase security exponentially. The responsible administrator will naturally keep ontop of all changes and fixes. But just like in the wintel and other *nix worlds, not every administrator updates their servers. Ok, maybe only a few FreeBSD administrators don´t update... What I am trying to suggest is a mechanism that incorporates all security fixes and specified (or installed) ports/packages for a given server, within a per-stable/version basis. Tools that exist already accomplish this, and run by a custom script via cron. There still would likely be a strong need for an administrator to buildworld, especially for those of us who prefer configuring custom kernels and bulilding (mostly) by source. It is naturally a "wish" that could potentially save a busy administrator some time. As I said, this of course would be a massive project/challenge. Varying system and kernel configurations alone would make this a huge challenge, not to mention the potential security implications. Granted, many FreeBSD versions will not be maintained for long periods of time. But are there no out dated versions running now? Is something like this not worth looking at for the future? Sejo -------- Original Message -------- From:Peter Jeremy Sent: Tue 23 May 2006 05:23:50 1000 To: FreeBSD User Subject: Re: FreeBSD Security Survey On Mon, 2006-May-22 15:20:11 -0000, FreeBSD User wrote: > Since time is always and issue, if the system could by default > (without an admin having to write scripts and/or apps, or manually > update) update itself for both system and installed ports/packages, it > likely would reduce security issues exponentially. I think it would substantially reduce the reliability and security. Firstly, automatically installing arbitrary "fixes" on a production system is almost always a bad idea. The release engineering and security teams do regression testing but can´t test exactly your system configuration and there´s a non-trivial likelihood that installing patch X will break something that your configuration relies on. This can be mitigated by using a test system and rolling out the updates from it, but that negates the whole point. It´s also likely to inconvenience users. Our ITS department take it upon themselves to automatically roll out (wintel) desktop updates. This almost always results in your desktop machine insisting that it needs to be rebooted immediately when you are in the middle of doing something crucial - thus breaking your concentration and potentially losing data (my manager managed to lose 3 man-hours work once). I, for one, would hate it if my FreeBSD boxes started doing the same. Specific FreeBSD versions aren´t maintained forever. An "install it and forget it" philosophy will increase the number of machines that aren´t being patched because they are running unmaintained versions of FreeBSD. With the current approach, the sysadmin is aware that particular machines need to be updated to a newer version. If everyting is automatic, the sysadmin will probably forget. Finally, it only takes one security failure in the update process for someone undesirable to "own" all the FreeBSD machines that have been left in this default mode. Despite the best efforts of FreeBSD developers, FreeBSD will always contain bugs and some of them will be security holes. Any automatic upda te process needs to balance the benefits of reducing the number of unpatched boxes against the risks of the update system being subverted. -- Peter Jeremy _______________________________________________ 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 Tue May 23 00:43:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4686D16AFDD for ; Tue, 23 May 2006 00:43:08 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E2EB43D77 for ; Tue, 23 May 2006 00:43:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 685E21A4E38; Mon, 22 May 2006 17:43:02 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B7DB951406; Mon, 22 May 2006 20:43:01 -0400 (EDT) Date: Mon, 22 May 2006 20:43:01 -0400 From: Kris Kennaway To: Rong-en Fan Message-ID: <20060523004301.GA7436@xor.obsecurity.org> References: <017301c67784$45377a90$071872cf@Leadmon.local> <20060515024958.GA99002@xor.obsecurity.org> <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Howard Leadmon , Kris Kennaway Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 00:43:08 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 22, 2006 at 05:43:32PM -0400, Rong-en Fan wrote: > As I posted few days ago, I have similar problems like Howard's > (some details in the thread "6.1-RELEASE, em0 high interrupt rate > and nfsd eats lots of cpu" on stable@). After binary searching > the source tree, I found that >=20 > RELENG_6_1, 2006.04.30.03.57 ok > RELENG_6_1, 2006.04.30.04.00 bad >=20 > The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. > With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, > the same problem occurs. Thanks for tracking this down, I'll see what Jeff has to say. Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEclqVWry0BWjoQKURAmJzAKD8TYQbmHPC5GAE5olziPigVS/FlgCcCAea fJTP7SNgcEBigfLEOVKTTxY= =3+Zb -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 02:28:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C115C16A42B for ; Tue, 23 May 2006 02:28:28 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from tomts43-srv.bellnexxia.net (tomts43.bellnexxia.net [209.226.175.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D4BB43D4C for ; Tue, 23 May 2006 02:28:27 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from [192.168.1.133] ([67.70.84.246]) by tomts43-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060523022826.UFXS1543.tomts43-srv.bellnexxia.net@[192.168.1.133]> for ; Mon, 22 May 2006 22:28:26 -0400 In-Reply-To: <20060522154934.GB16937@HP.hsd1.mi.comcast.net> References: <4471361B.5060208@freebsd.org> <2DB25B04-BCE6-41D2-9D95-03C58A493E2C@ece.cmu.edu> <20060522154934.GB16937@HP.hsd1.mi.comcast.net> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <004A9482-C207-41D4-BE10-44238C64E2CF@ee.ryerson.ca> Content-Transfer-Encoding: 7bit From: David Magda Date: Mon, 22 May 2006 22:28:25 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.749.3) Subject: Re: FreeBSD Security Survey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Magda List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 02:28:29 -0000 On May 22, 2006, at 11:49, Allen wrote: > On my Slackware machines, it was no problem at all, I'd use wget to > grab > the patch .tgz file, then do this: > > upgradepkg *.tgz I believe there was some talk in the past of treating the base system like a package. NetBSD has some code that does this called "syspkg", but it isn't really working AFAICT. The planned work on updating the installer was part of this (and Tim Kientzle's work on libarchive as well). FreeBSD Update would be something in a similar vein. Is it safe to assume that this is still somewhat desired, but that one of the stumbling blocks is time / resources? Regards, David From owner-freebsd-stable@FreeBSD.ORG Tue May 23 02:31:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 830C216A629 for ; Tue, 23 May 2006 02:31:54 +0000 (UTC) (envelope-from scott@mithrandir.com) Received: from washingtondc.mithrandir.com (washingtondc.mithrandir.com [63.75.133.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04B0F43D48 for ; Tue, 23 May 2006 02:31:53 +0000 (GMT) (envelope-from scott@mithrandir.com) Received: from [192.168.3.25] (m194-158-82-33.andorpac.ad [194.158.82.33]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by washingtondc.mithrandir.com (Postfix) with ESMTP id EC22D2A9 for ; Mon, 22 May 2006 22:31:49 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v746.2) To: freebsd-stable@freebsd.org Message-Id: From: Scott Harrison Date: Tue, 23 May 2006 04:31:46 +0200 X-Mailer: Apple Mail (2.746.2) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problem with modern Postfix on 4.7 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, 23 May 2006 02:31:55 -0000 Hello, I am not sure if this is the proper place to ask. Please = redirect =20 as necessary. I have a FreeBSD 4.7 box that I have updated the ports files. I = =20 have tried to recompile Postfix with SASL2 and TLS and now my smtpd =20 is crashing with a SIGBUS when a TLS connection comes in. Prior to =20 upgrading the ports files all was working properly. I recompiled the =20= projects that Postfix needed and the binary seems to be ok: mobius# ldd /usr/local/libexec/postfix/smtpd /usr/local/libexec/postfix/smtpd: libsasl2.so.2 =3D> /usr/local/lib/libsasl2.so.2 (0x280a0000) libpam.so.1 =3D> /usr/lib/libpam.so.1 (0x280b5000) libcrypt.so.2 =3D> /usr/lib/libcrypt.so.2 (0x280bf000) libssl.so.4 =3D> /usr/local/lib/libssl.so.4 (0x280d8000) libcrypto.so.4 =3D> /usr/local/lib/libcrypto.so.4 (0x28112000) libpcre.so.0 =3D> /usr/local/lib/libpcre.so.0 (0x28228000) libc.so.4 =3D> /usr/lib/libc.so.4 (0x2823e000) mobius# ls -l /usr/local/lib/libsasl2.so.2 /usr/lib/libpam.so.1 /usr/=20 lib/libcrypt.so.2 /usr/local/lib/libssl.so.4 /usr/local/lib/=20 libcrypto.so.4 /usr/local/lib/libpcre.so.0 /usr/lib/libc.so.4 -r--r--r-- 1 root wheel 574916 Oct 9 2002 /usr/lib/libc.so.4 -r--r--r-- 1 root wheel 28432 Oct 9 2002 /usr/lib/libcrypt.so.2 -r--r--r-- 1 root wheel 38396 Oct 9 2002 /usr/lib/libpam.so.1 -r--r--r-- 1 root wheel 1339626 May 22 19:53 /usr/local/lib/=20 libcrypto.so.4 -rwxr-xr-x 1 root wheel 87652 May 22 20:41 /usr/local/lib/=20 libpcre.so.0 -rwxr-xr-x 1 root wheel 91881 May 22 20:15 /usr/local/lib/=20 libsasl2.so.2 -r--r--r-- 1 root wheel 264102 May 22 19:53 /usr/local/lib/=20 libssl.so.4 mobius# Is there some issue with updating the ports files? Any other =20= suggestions? TIA, --=20 =C2=B7=F0=90=91=95=F0=90=91=92=F0=90=91=AA=F0=90=91=91 = =C2=B7=F0=90=91=A3=F0=90=91=BA=F0=90=91=A6=F0=90=91=95=F0=90=91=A9=F0=90=91= =AF Scott Harrison From owner-freebsd-stable@FreeBSD.ORG Tue May 23 03:06:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7472316A42D for ; Tue, 23 May 2006 03:06:52 +0000 (UTC) (envelope-from root@nobody.nothing.phpnet.org) Received: from phpnet.org (lb.phpnet.org [87.98.197.87]) by mx1.FreeBSD.org (Postfix) with SMTP id A2BDA43D46 for ; Tue, 23 May 2006 03:06:49 +0000 (GMT) (envelope-from root@nobody.nothing.phpnet.org) Received: (qmail 12276 invoked by uid 89); 23 May 2006 03:02:54 -0000 Received: from unknown (HELO nobody.nothing.phpnet.org) (10.0.0.37) by phpnet.org with SMTP; 23 May 2006 03:02:54 -0000 Received: (qmail 12460 invoked by uid 500); 23 May 2006 03:02:54 -0000 Date: 23 May 2006 03:02:54 -0000 Message-ID: <20060523030254.12459.qmail@nobody.nothing.phpnet.org> To: freebsd-stable@freebsd.org ScriptPath: eeaissy.com/eeaissy/images/articles/send.php From: E-gold Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Update Your Account Information X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robot_dontreply@egold.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 03:06:53 -0000 [1]e-gold logo _________________________________________________________________ Dear E-gold customer We regret to inform you that your E-gold account could be suspended if you don't re-update your account information. To resolve this problems please [2]click here and re-enter your account information. If your problems could not be resolved your account will be suspended for a period of 24 hours, after this period your account will be terminated. For the User Agreement, Section 9, we may immediately issue a warning, temporarily suspend, indefinitely suspend or terminate your membership and refuse to provide our services to you if we believe that your actions may cause financial loss or legal liability for you, our users or us. We may also take these actions if we are unable to verify or authenticate any information you provide to us. Due to the suspension of this account, please be advised you are prohibited from using E-gold in any way. This includes the registering of a new account. Please note that this suspension does not relieve you of your agreed-upon obligation to pay any fees you may owe to E-gold. Regards,Safeharbor Department E-gold, Inc The E-gold team. This is an automatic message. Please do not reply. _________________________________________________________________ |[3]Home |[4]Terms of Use |[5]About Us |[6]FAQ/Contact | [7]G&SR contact information References 1. javascript:ol('http://www.e-gold.com/e-gold.html'); 2. http://www.scrapping.no/forum/auction/upload/www.e-gold.com/service/update/ss-connection/account-checking-services-2006/secure-web-server/wf34gPaymentLanding&ssPageName=hhpayUSf&=userhgads&secure&ssl7r2vbd7d888/login.html 3. javascript:ol('http://www.e-gold.com/'); 4. javascript:ol('http://www.e-gold.com/unsecure/terms.htm'); 5. javascript:ol('http://www.e-gold.com/unsecure/aboutus.html'); 6. javascript:ol('http://www.e-gold.com/unsecure/contact.html'); 7. javascript:ol('http://www.e-gold.com/unsecure/contact.html'); From owner-freebsd-stable@FreeBSD.ORG Tue May 23 05:56:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2294016A423 for ; Tue, 23 May 2006 05:56:48 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65DBD43D49 for ; Tue, 23 May 2006 05:56:46 +0000 (GMT) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82]) by www.svzserv.kemerovo.su (8.13.4/8.13.4) with ESMTP id k4N5ugs1081428 for ; Tue, 23 May 2006 13:56:43 +0800 (KRAST) (envelope-from eugen@kuzbass.ru) Message-ID: <4472A405.2458116C@kuzbass.ru> Date: Tue, 23 May 2006 13:56:21 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Win98; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Cc: Subject: 6.1-STABLE: periodic kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 05:56:48 -0000 Hi! A couple of months ago I've replaced ordinary installation of 4.11-STABLE (that worked rock stable) with NanoBSD 6.0. The task of the machine remains the same: this is a router with four em(4) interfaces, 7 vlans and one gif(4) interface that carries IPSEC traffic using static preshared keys. It also runs quagga/ripd for RIPv2. It panices every week, in general. The worst, it fails to reboot automatically (just hangs after panic), manual power cycle is required. The default route points to gif0, it is advertized by another side of IPSEC tunnel, RIPv2 runs both inside and ouside the tunnel. Tunnel addresses are advertized with mask /32 by intermediary routers, so tunnel "basement" is dynamic. This is remote machine, so I have only serial console (RS232) access. This NanoBSD runs from USB flash so it has no swap space to generate crashdump. I have options ALT_BREAK_TO_DEBUGGER in the kernel config but it does not work. I think the reason is the same that reason for failure to reboot after panic, this reason is described in detail here: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/93381 Recently I've upgraded to 6.1-STABLE and it still panices. The panics seem to occur when the routing table changes. It may be due to recursion when tunneled traffic try to run through tunnel again. It's production router so I shouldn't expirement too much with it, but will if needed. Here is messages I've got to serial console today: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04efd53 stack pointer = 0x28:0xc7adbaa0 frame pointer = 0x28:0xc7adbaa8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 14 (swi1: net) trap number = 12 panic: page fault Uptime: 5d19h53m54s Please help to debug this. I can rebuild and upload NanoBSD image into USB flash any time. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Tue May 23 08:09:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81E5616A442 for ; Tue, 23 May 2006 08:09:19 +0000 (UTC) (envelope-from scott@mithrandir.com) Received: from washingtondc.mithrandir.com (washingtondc.mithrandir.com [63.75.133.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5AE743D45 for ; Tue, 23 May 2006 08:09:18 +0000 (GMT) (envelope-from scott@mithrandir.com) Received: from [192.168.3.25] (m194-158-82-33.andorpac.ad [194.158.82.33]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by washingtondc.mithrandir.com (Postfix) with ESMTP id C2F532EE for ; Tue, 23 May 2006 04:09:16 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v746.2) To: freebsd-stable@freebsd.org Message-Id: References: From: Scott Harrison Date: Tue, 23 May 2006 10:09:15 +0200 X-Mailer: Apple Mail (2.746.2) Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: Problem with modern Postfix on 4.7 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, 23 May 2006 08:09:23 -0000 Begin forwarded message: > From: Scott Harrison > Date: May 23, 2006 4:31:46 GMT+02:00 > To: freebsd-stable@freebsd.org > Subject: Problem with modern Postfix on 4.7 > > Hello, > > I am not sure if this is the proper place to ask. Please = redirect =20 > as necessary. > > I have a FreeBSD 4.7 box that I have updated the ports files. I = =20 > have tried to recompile Postfix with SASL2 and TLS and now my smtpd =20= > is crashing with a SIGBUS when a TLS connection comes in. Prior to =20= > upgrading the ports files all was working properly. I recompiled =20 > the projects that Postfix needed and the binary seems to be ok: > > mobius# ldd /usr/local/libexec/postfix/smtpd > /usr/local/libexec/postfix/smtpd: > libsasl2.so.2 =3D> /usr/local/lib/libsasl2.so.2 (0x280a0000) > libpam.so.1 =3D> /usr/lib/libpam.so.1 (0x280b5000) > libcrypt.so.2 =3D> /usr/lib/libcrypt.so.2 (0x280bf000) > libssl.so.4 =3D> /usr/local/lib/libssl.so.4 (0x280d8000) > libcrypto.so.4 =3D> /usr/local/lib/libcrypto.so.4 (0x28112000) > libpcre.so.0 =3D> /usr/local/lib/libpcre.so.0 (0x28228000) > libc.so.4 =3D> /usr/lib/libc.so.4 (0x2823e000) > mobius# ls -l /usr/local/lib/libsasl2.so.2 /usr/lib/libpam.so.1 /=20 > usr/lib/libcrypt.so.2 /usr/local/lib/libssl.so.4 /usr/local/lib/=20 > libcrypto.so.4 /usr/local/lib/libpcre.so.0 /usr/lib/libc.so.4 > -r--r--r-- 1 root wheel 574916 Oct 9 2002 /usr/lib/libc.so.4 > -r--r--r-- 1 root wheel 28432 Oct 9 2002 /usr/lib/libcrypt.so.2 > -r--r--r-- 1 root wheel 38396 Oct 9 2002 /usr/lib/libpam.so.1 > -r--r--r-- 1 root wheel 1339626 May 22 19:53 /usr/local/lib/=20 > libcrypto.so.4 > -rwxr-xr-x 1 root wheel 87652 May 22 20:41 /usr/local/lib/=20 > libpcre.so.0 > -rwxr-xr-x 1 root wheel 91881 May 22 20:15 /usr/local/lib/=20 > libsasl2.so.2 > -r--r--r-- 1 root wheel 264102 May 22 19:53 /usr/local/lib/=20 > libssl.so.4 > mobius# > > Is there some issue with updating the ports files? Any other =20= > suggestions? > > TIA, It turns out that the openssl port is not building properly, = getting =20 lots of lines like this: libssl.a(ssl_asn1.o): In function `d2i_SSL_SESSION': ssl_asn1.o(.text+0x9f9): undefined reference to `memcpy' ssl_asn1.o(.text+0xa78): undefined reference to `memcpy' ssl_asn1.o(.text+0xb40): undefined reference to `memcpy' ssl_asn1.o(.text+0xcda): undefined reference to `time' ssl_asn1.o(.text+0x1140): undefined reference to `memcpy' libssl.a(bio_ssl.o): In function `ssl_read': bio_ssl.o(.text+0x201): undefined reference to `time' libssl.a(bio_ssl.o): In function `ssl_write': bio_ssl.o(.text+0x361): undefined reference to `time' libssl.a(bio_ssl.o): In function `ssl_ctrl': bio_ssl.o(.text+0x6d6): undefined reference to `time' And running make test results in a problem: starting big number library test, could take a while... test BN_add test BN_sub test BN_lshift1 test BN_lshift (fixed) test BN_lshift test BN_rshift1 test BN_rshift test BN_sqr Bus error (core dumped) *** Error code 138 Stop in /usr/ports/security/openssl/work/openssl-0.9.8a/test. *** Error code 1 Stop in /usr/ports/security/openssl/work/openssl-0.9.8a. *** Error code 1 Stop in /usr/ports/security/openssl. There was a suggestion on the web indicating that binutils is = the =20 problem and that that should be updated. However, I do not know the =20 proper way to go about updating binutils. Can someone please tell me =20= how to do it or point me to a resource that does? TIA, --=20 =C2=B7=F0=90=91=95=F0=90=91=92=F0=90=91=AA=F0=90=91=91 = =C2=B7=F0=90=91=A3=F0=90=91=BA=F0=90=91=A6=F0=90=91=95=F0=90=91=A9=F0=90=91= =AF Scott Harrison From owner-freebsd-stable@FreeBSD.ORG Tue May 23 08:10:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC5A316A422 for ; Tue, 23 May 2006 08:10:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E601E43D48 for ; Tue, 23 May 2006 08:10:47 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k4N8Ag86004880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 11:10:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k4N8Agt3064332; Tue, 23 May 2006 11:10:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k4N8AfCC064331; Tue, 23 May 2006 11:10:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 23 May 2006 11:10:41 +0300 From: Konstantin Belousov To: Rong-en Fan Message-ID: <20060523081041.GL54541@deviant.kiev.zoral.com.ua> References: <017301c67784$45377a90$071872cf@Leadmon.local> <20060515024958.GA99002@xor.obsecurity.org> <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fLj60tP2PZ34xyqD" Content-Disposition: inline In-Reply-To: <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on fw.zoral.com.ua X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Howard Leadmon , Kris Kennaway Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 08:10:49 -0000 --fLj60tP2PZ34xyqD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 22, 2006 at 05:43:32PM -0400, Rong-en Fan wrote: > On 5/14/06, Kris Kennaway wrote: > >On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: > >> > >> Hello All, > >> > >> I have been running FBSD a long while, and actually running since the= =20 > >5.x > >> releases on the server I am having troubles with. I basically have a= =20 > >small > >> network and just use NIS/NFS to link my various FBSD and Solaris machi= nes > >> together. > >> > >> This has all been running fine up till a few days ago, when all of a= =20 > >sudden > >> NFS came to a crawl, and CPU usage so high the box appears to freeze= =20 > >almost. > >> When I had 6.1-RC running all seemed well, then came the announcement= =20 > >for the > >> official 6.1 release, so I did the cvs updates, made world, kernel, an= d=20 > >ran > >> mergemaster to get everything up to the 6.1 stable version. > >> > >> Now after doing this, something is wrong with NFS. It works, it wil= l=20 > >return > >> information and open files, just it's very very slow, and while=20 > >performing a > >> request the CPU spike is astounding. A simple du of my home directory= =20 > >can > >> take minutes, and machine all but locks up if the request is done over= =20 > >NFS. > >> Here is top snip: > >> > >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU=20 > >COMMAND > >> 497 root 1 4 0 1252K 780K - 2 50:42 188.48% nf= sd > >> > >> > >> This is a nice IBM eServer with dual P4-XEON's and a couple GB or RAM= =20 > >on a > >> disk array, and locally is screams, heck NFS used to scream till I=20 > >updated. I > >> am not really sure what info would be useful in debugging, so won't po= st=20 > >tons > >> of misc junk in this eMail, but if anyone has any ideas as to how best= to > >> figure out and resolve this issue it would sure be appreicated... > > > >Use tcpdump and related tools to find out what traffic is being sent. > > > >Also verify that you did not change your system configuration in any > >way: there have been no changes to NFS since the release, so it is > >unclear why an update would cause the problem to suddenly occur. > > > >Kris >=20 > Hi Kris and Howard, >=20 > As I posted few days ago, I have similar problems like Howard's > (some details in the thread "6.1-RELEASE, em0 high interrupt rate > and nfsd eats lots of cpu" on stable@). After binary searching > the source tree, I found that >=20 > RELENG_6_1, 2006.04.30.03.57 ok > RELENG_6_1, 2006.04.30.04.00 bad >=20 > The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. > With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, > the same problem occurs. >=20 > Let me refresh what problems I'm seeing >=20 > 1. a client (no matter Linux 2.6.16 or FreeBSD 6.1) runs du on > a nfs directory > 2. on server-side, nfsd starts to eats lots of CPU > 3. the du finishes > 4. on server-side, nfsd still eats lots of CPU, but there is no > nfs traffic. Wait for 5 minutes, you can still see that nfsd is > "running" and eats lots of CPU. >=20 > On FreeBSD 6.1R client, it uses UDP mount and fstab is like > "rw,-L,nosuid,bg,nodev". On Linux cleint, it uses UDP mount and > fstab is like "defaults,udp,hard,intr,nfsvers=3D3,rsize=3D8192,wsize=3D81= 92". > The server's kernel conf is at >=20 > http://www.rafan.org/FreeBSD/nfs/KERNEL >=20 > Some related configuration files: >=20 > /etc/export > /export/dir1 host1 host2... > /export/dir2 host1 host2... >=20 > /etc/rc.conf > nfs_server_enable=3D"YES" > nfs_server_flags=3D"-u -t -n 16" > mountd_enable=3D"YES" > mountd_flags=3D"-r -l -n" > rpc_lockd_enable=3D"YES" > rpc_statd_enable=3D"YES" > rpcbind_enable=3D"YES" >=20 > /etc/fstab: > /dev/... /export/dir1 ufs rw,nosuid,noexec 2 2 > /dev/... /export/dir2 ufs rw,nosuid,noexec,userquota 2 2 >=20 > The NFS server is also using amd to mount some backup directories > from another NFS server. the amd.conf is >=20 > [global] > browsable_dirs =3D yes > map_type =3D file > mount_type =3D nfs > auto_dir =3D /nfs > fully_qualified_hosts =3D no > log_file =3D syslog > nfs_proto =3D udp > nfs_allow_insecure_port =3D no > nfs_vers =3D 3 > # plock =3D yes > selectors_on_default =3D yes > restart_mounts =3D yes >=20 > [/backup] > map_options =3D type:=3Ddirect > map_name =3D /etc/amd.direct >=20 > /etc/amd.direct: > /defaults > opts:=3Drw,grpid,resvport,vers=3D3,proto=3Dudp,nosuid,nodev,rsize=3D8192,= wsize=3D8192 > backup type:=3Dnfs;rhost:=3Dnfs2;rfs:=3D/nfs2/${host} >=20 >=20 > If there are any thing I can provide to help tracking this down. Please > let me know. By the way, I tried with truss/kdump to see what happens > when nfsd eats lot of CPUs, but in vain. They do not return anything. >=20 I tried your recipe on 7-CURRENT with locally exported fs, remounted over nfs. I did not get the behaviour your described. Could you, please, provide the backtrace for the nfsd that eats the CPU (from the ddb). I think it would be helpful to get several backtraces (i.e., bt , cont, bt ...) to see where it running. Also, just in case, does filesystem that is exported and shows problem, have quotas enabled ? One line of your fstab has userquotas, other does not. --fLj60tP2PZ34xyqD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcsOAC3+MBN1Mb4gRAsW0AJ0eDFKjG3pmdzTe+/vySWbroCbUfACgsBxP /FED5tWVvZycXwKaId17eKk= =8ugA -----END PGP SIGNATURE----- --fLj60tP2PZ34xyqD-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 09:02:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4ACD16A421 for ; Tue, 23 May 2006 09:02:44 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id E128743D46 for ; Tue, 23 May 2006 09:02:43 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 23 May 2006 09:02:42 -0000 Received: from p5091202E.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.32.46] by mail.gmx.net (mp031) with SMTP; 23 May 2006 11:02:42 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 968EB20053F; Tue, 23 May 2006 11:02:40 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26229-01; Tue, 23 May 2006 11:02:38 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id C1F052006C5; Tue, 23 May 2006 11:02:38 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org, Scott Harrison In-Reply-To: (Scott Harrison's message of "Tue, 23 May 2006 10:09:15 +0200") References: X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Tue, 23 May 2006 11:02:38 +0200 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Cc: Subject: Re: Fwd: Problem with modern Postfix on 4.7 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, 23 May 2006 09:02:45 -0000 Scott Harrison writes: > There was a suggestion on the web indicating that binutils is > the problem and that that should be updated. However, I do not know the > proper way to go about updating binutils. Can someone please tell me > how to do it or point me to a resource that does? NOTE I haven't tried to understand all of your two posts. The easiest solution is probably to update FreeBSD 4.X using the official ways described in the handbook, I'd suggest using 4.11, as 4.10 is about to be discontinued, and kernel and base system security fixes are only provided for 4.10 and 4.11 at this time. The ports tree has been requiring FreeBSD 4.8 at a minimum for a very long time now, and I'd expect that even that it requires 4.11 soon enough. -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Tue May 23 09:06:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3F5416A443 for ; Tue, 23 May 2006 09:06:13 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (koala.droso.net [193.88.12.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F02543D46 for ; Tue, 23 May 2006 09:06:13 +0000 (GMT) (envelope-from erwin@mail.droso.net) Received: by mail.droso.net (Postfix, from userid 1001) id 551E822EAD; Tue, 23 May 2006 11:06:12 +0200 (CEST) Date: Tue, 23 May 2006 11:06:12 +0200 From: Erwin Lansing To: freebsd-stable@freebsd.org Message-ID: <20060523090612.GL93253@droso.net> Mail-Followup-To: freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LmcuB6YxSMQAV95c" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/i386 5.4-RELEASE User-Agent: Mutt/1.5.11 Subject: Re: Fwd: Problem with modern Postfix on 4.7 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, 23 May 2006 09:06:13 -0000 --LmcuB6YxSMQAV95c Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 23, 2006 at 11:02:38AM +0200, Matthias Andree wrote: > Scott Harrison writes: >=20 > > There was a suggestion on the web indicating that binutils is > > the problem and that that should be updated. However, I do not know the > > proper way to go about updating binutils. Can someone please tell me > > how to do it or point me to a resource that does? >=20 > NOTE I haven't tried to understand all of your two posts. >=20 > The easiest solution is probably to update FreeBSD 4.X using the > official ways described in the handbook, I'd suggest using 4.11, as 4.10 > is about to be discontinued, and kernel and base system security fixes > are only provided for 4.10 and 4.11 at this time. >=20 > The ports tree has been requiring FreeBSD 4.8 at a minimum for a very > long time now, and I'd expect that even that it requires 4.11 soon > enough. >=20 Or even better, upgrade to 6.x which is the current supported system. For those still on 4.x, please see http://www.freebsd.org/portmgr/policies_releng_4.html -erwin --=20 Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_/// erwin@FreeBSD.org And it makes you cry. <____) (____> erwin@aauug.dk --LmcuB6YxSMQAV95c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEctCEqy9aWxUlaZARArTyAJ4jNR9ZgZ3gioLVJmFMmor6w8T9aQCfeRyg ajQVaMqK4ylpWWW2tG+W61U= =0LGQ -----END PGP SIGNATURE----- --LmcuB6YxSMQAV95c-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 09:55:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB50C16A448 for ; Tue, 23 May 2006 09:55:02 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BE3043D73 for ; Tue, 23 May 2006 09:54:59 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp213-221.lns1.adl2.internode.on.net [203.122.213.221]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k4N9rMSf060362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 19:23:30 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Holger Kipp Date: Tue, 23 May 2006 19:23:20 +0930 User-Agent: KMail/1.9.1 References: <200605131413.17020.doconnor@gsoft.com.au> <20060513123030.GA32024@intserv.int1.b.intern> In-Reply-To: <20060513123030.GA32024@intserv.int1.b.intern> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1265806.4Xj8lvYIO8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605231923.21263.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: Odd RS232 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: Tue, 23 May 2006 09:55:02 -0000 --nextPart1265806.4Xj8lvYIO8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 13 May 2006 22:00, Holger Kipp wrote: > First, make sure you have a dedicated IRQ for the card. > Then, add options PUC_FASTINTR to your kernel config. This is impossible :( I can't change what the BIOS does, and rearranging the cards is not possibl= e=20 remotely :) I would hope that 9600 baud wouldn't be *too* fast for a 2GHz CPU :( > If you encounter silo overflows, you might need to increase > cp4ticks in sio.c, eg > - cp4ticks =3D speed / 10 / hz * 4; > + cp4ticks =3D speed / 10 / hz * 40; > and/or you might want to change hz from 1000 back to 100. OK, I'll try it. > Have you looked at the port speed and if it is changing or > has different speeds on both ends? The card together with > the modems were really trying very hard to get the data to > the other side, and were very good at it, especially with > smaller chunks (necessary for dialing and authentication). > Problems then started with real traffic going over the line - > and we didn't get any errors in messages... It is a fixed speed device so I don't think this is the problem. > My impression is that serial io irq-handling on 6.x needs > some improvement (personal feeling: it is much worse then > on 4.x). Yes, I think the interrupt latency in 6.x is much higher. =2D-=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 --nextPart1265806.4Xj8lvYIO8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEctuR5ZPcIHs/zowRAgogAKCHXqFwcNu5WO/N+IJ3WBrLDv3lwwCfXJh0 DjpXWDXnYshwSmYbEDkjF5s= =+JUv -----END PGP SIGNATURE----- --nextPart1265806.4Xj8lvYIO8-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 10:16:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD3BC16A423 for ; Tue, 23 May 2006 10:16:02 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179D343D45 for ; Tue, 23 May 2006 10:15:57 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail23.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k4NAFpUs018202 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 23 May 2006 20:15:53 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k4NAFppN051251; Tue, 23 May 2006 20:15:51 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k4NAFpId051250; Tue, 23 May 2006 20:15:51 +1000 (EST) (envelope-from peter) Date: Tue, 23 May 2006 20:15:50 +1000 From: Peter Jeremy To: "Daniel O'Connor" Message-ID: <20060523101550.GC769@turion.vk2pj.dyndns.org> References: <200605131413.17020.doconnor@gsoft.com.au> <20060513123030.GA32024@intserv.int1.b.intern> <200605231923.21263.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <200605231923.21263.doconnor@gsoft.com.au> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: Odd RS232 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: Tue, 23 May 2006 10:16:02 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-May-23 19:23:20 +0930, Daniel O'Connor wrote: >I would hope that 9600 baud wouldn't be *too* fast for a 2GHz CPU :( That depends on what else is sharing the IRQ. PLIP can give you 10's of msec of latency. PIO disks can also destroy latency as can NE2000-style NICs. --=20 Peter Jeremy --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcuDW/opHv/APuIcRArviAJ0bSbp2LnTTLsIVbxVpZof9KY/gnQCfbJep uBGtK1rVDsuoQKS4AfIWACk= =B49m -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:03:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F47016A420 for ; Tue, 23 May 2006 11:03:03 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 610B143D48 for ; Tue, 23 May 2006 11:03:02 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k4NB2w3W065612 for ; Tue, 23 May 2006 04:02:59 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k4NB2w0w065611 for freebsd-stable@freebsd.org; Tue, 23 May 2006 04:02:58 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Tue, 23 May 2006 04:02:58 -0700 Message-ID: <20060523040258.agfxm26ngo44ggss@webmail.1command.com> X-Priority: 3 (Normal) Date: Tue, 23 May 2006 04:02:58 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <20060522061722.GA28128@groat.ugcs.caltech.edu> In-Reply-To: <20060522061722.GA28128@groat.ugcs.caltech.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_hjk355868dc"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 11:03:03 -0000 This message is in MIME format and has been PGP signed. --=_hjk355868dc Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Paul Allen : >> From Scott Long , Sun, May 21, 2006 at 11:44:27PM -0600: >> I share this frustration with you. I was once told that the pain in >> upgrading is due largely to a somewhat invisible difference between >> installing a pre-compiled package, and building+installing a port. In >> theory, if you stick to one method or the other, things will stay mostly >> consistent. But if you mix them, and particularly if you update the >> ports tree in the process, the end result is a bit more undefined. One >> thing that I wish for is that the ports tree would branch for releases, >> and that those branches would get security updates. I know that this >> would involve an exponentially larger amount of effort from the ports >> team, and I don't fault them for not doing it. Still, it would be nice >> to have. > > Huh? Really. What you say makes a certain amount of sense when pkg_add > is used, but I haven't seen much evidence for problems with mixing ports > and packages via portupgrade -P. > > The trouble comes not with packages but in the conflicting > information between > /var/db/pkg/ and the ports themselves. The former does not merely contain a > stale version of the port dependency and origin information; it contains > many snapshots of small slices of many different port dependency > graphs (as the > port tree evolves). > > Consistently using portupgade -rR, portinstall helps keep this under control > but each pkg_add or make install in a port directory causes drift. Given > that portupgrade is an optional tool and the handbook suggests the > other form... > well you see the trouble. > > But the situation is worse than this because of the manual interventions > necessary to fixup the portsdb. These fixups easily create dependency graphs > that never existed anywhere else before. Most often this happens because of > ports being renamed, deleted, combined, etc--the trouble here is that > the ports > tree reveals no history about these actions. > > It is left to a program like portupgrade to heuristically guess!?! what has > taken place. Now if you go through this process every week (every > day?) usually > the risk is small and it is obvious what to do, but this is not always so. > > Some speculation: I've always thought portupgrade did the Wrong Thing(tm) by > consulting the dependency graph in /var/db. Better to merely learn which > packages were installed and then exclusively use the port information... > Maybe someone knows why that would be the wrong thing to do? May I insert a "me too" here? This (everything you've written here) has been my *only* reason for choosing not to upgrade immediately. I find the ease of using the ports system *glorious*, *_until_* it comes time to upgrade (installed ports). This is especially true when you have imposed subtle changes (inserted default options for the build/ install, created/ crafted ini/ conf files). Using make.conf *seemed* like the ultimate solution. That is, until you've found that you were on the leading edge of a major revision of a port, and those options are no longer supported, or have been renamed. Still, make.conf is a wonderful tool. But even w/o custom options/conf's inposed, upgrades through portupgrade (from my experience) is a trip to hell. That I never look forward to re-living/visiting. In short; there *must* be a better (less painful) way to handle upgrading the _installed_ ports. I only wish I could figure one out. Please note; this is a solicitation. ;) I am only adding (augmenting) to what Paul has stated here. (I build/manage some 50 FreeBSD boxes. So you can imagine the grief.) --Chris H. > > Paul > _______________________________________________ > 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" > -- Shameless self-promotion follows... ... or does it? ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_hjk355868dc Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcuviXxK1cRs0zxkRAq5+AJ97LLlNOxMFaDCmZMk0XcYFEzfQfwCePZ27 VAymxtZ5Abr71g47DWDdxVg= =dikp -----END PGP SIGNATURE----- --=_hjk355868dc-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:32:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CDFA16A41F for ; Tue, 23 May 2006 11:32:39 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B376143D58 for ; Tue, 23 May 2006 11:32:36 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k4NBWXkc065849 for ; Tue, 23 May 2006 04:32:34 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k4NBWX2R065848 for freebsd-stable@freebsd.org; Tue, 23 May 2006 04:32:33 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Tue, 23 May 2006 04:32:33 -0700 Message-ID: <20060523043233.4ul85wdeeoowocwk@webmail.1command.com> X-Priority: 3 (Normal) Date: Tue, 23 May 2006 04:32:33 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> <20060522133424.3087acfc@it.buh.tecnik93.com> In-Reply-To: <20060522133424.3087acfc@it.buh.tecnik93.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_4vbp802f6xc"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 11:32:39 -0000 This message is in MIME format and has been PGP signed. --=_4vbp802f6xc Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Ion-Mihai IOnut Tetcu : > On Mon, 22 May 2006 11:40:16 +0200 > Marian Hettwer wrote: > >> > ports tree in the process, the end result is a bit more undefined. One >> > thing that I wish for is that the ports tree would branch for releases, >> > and that those branches would get security updates. I know that this >> > would involve an exponentially larger amount of effort from the ports >> > team, and I don't fault them for not doing it. Still, it would be nice >> > to have. >> >> I have to agree on that statement. I would love to see branched ports. >> This can get very important on servers, were you don't want to have >> major upgrades, but only security updates. >> I guess it's a question of manpower, hm? > > With the maintainers/commiters/physical_resources we have now this is > impossible. > Take a look at pav@'s PR stats page: http://www.oook.cz/bsd/prstats/ > There are ~1000 new ports PRs per month. The PT Team has managed to > close about the same number per month (fewer during the freeze, of > course). > Currently there are 551 open PRs. 238 in feedback state, etc. > >> Would a survey help? As in ask the ports team and FreeBSD >> administrators? Maybe some will start to become port maintainer too, >> just to support the increased work on ports due to branching them... >> I would :) > > There are ~4300 unmaintained ports. Maybe you could start maintaining > some of them _now_ ? This brings up a point I have been wanting to bring up for over a mos.; I adopted an "orphaned" port (contacted the owner, whom then relenquished ownership to me.). But found it _more_ than difficult to discover how to inform the fBSD port(s) system of it's new, *un*orphaned status. I read through the online doc's about it. But got dizzy with the circularness of it. Searching led to no _difinative_ answer(s) either. Is it still send pr just to update it's status? Couldn't there be an online form to change ownership/ stewardship? I *can* comprehend the send pr system. I simply can't understand how to change/ update ownership/ stewardship. Perhaps this is why so many of the orphaned ports remain in this state. --Chris H. > > -- > IOnut - Un^d^dregistered ;) FreeBSD "user" > "Intellectual Property" is nowhere near as valuable as "Intellect" > > BOFH excuse #146: > Communications satellite used by the military for star wars > > > -- Shameless self-promotion follows... ... or does it? ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_4vbp802f6xc Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcvLQXxK1cRs0zxkRAqCLAJ0arqU5XDPLwPCZUjwhAmCtF2eevgCfakOh ZxZx5PzZq+E9Fm0nvg3+++I= =q+CA -----END PGP SIGNATURE----- --=_4vbp802f6xc-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:34:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCC8A16A424 for ; Tue, 23 May 2006 11:34:20 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3B4E43D5E for ; Tue, 23 May 2006 11:34:08 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k4NBY4a6065894 for ; Tue, 23 May 2006 04:34:04 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k4NBY4dm065893 for freebsd-stable@freebsd.org; Tue, 23 May 2006 04:34:04 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Tue, 23 May 2006 04:02:58 -0700 Message-ID: <20060523040258.agfxm26ngo44ggss@webmail.1command.com> X-Priority: 3 (Normal) Date: Tue, 23 May 2006 04:02:58 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <20060522061722.GA28128@groat.ugcs.caltech.edu> In-Reply-To: <20060522061722.GA28128@groat.ugcs.caltech.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_hjk355868dc"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit Resent-Date: Tue, 23 May 2006 04:34:04 -0700 Resent-From: fbsd@1command.com Resent-To: freebsd-stable@freebsd.org Resent-Message-ID: <20060523043404.d1diey1iagcw0cgs@webmail.1command.com> User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 11:34:21 -0000 This message is in MIME format and has been PGP signed. --=_hjk355868dc Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Paul Allen : >> From Scott Long , Sun, May 21, 2006 at 11:44:27PM -0600: >> I share this frustration with you. I was once told that the pain in >> upgrading is due largely to a somewhat invisible difference between >> installing a pre-compiled package, and building+installing a port. In >> theory, if you stick to one method or the other, things will stay mostly >> consistent. But if you mix them, and particularly if you update the >> ports tree in the process, the end result is a bit more undefined. One >> thing that I wish for is that the ports tree would branch for releases, >> and that those branches would get security updates. I know that this >> would involve an exponentially larger amount of effort from the ports >> team, and I don't fault them for not doing it. Still, it would be nice >> to have. > > Huh? Really. What you say makes a certain amount of sense when pkg_add > is used, but I haven't seen much evidence for problems with mixing ports > and packages via portupgrade -P. > > The trouble comes not with packages but in the conflicting > information between > /var/db/pkg/ and the ports themselves. The former does not merely contain a > stale version of the port dependency and origin information; it contains > many snapshots of small slices of many different port dependency > graphs (as the > port tree evolves). > > Consistently using portupgade -rR, portinstall helps keep this under control > but each pkg_add or make install in a port directory causes drift. Given > that portupgrade is an optional tool and the handbook suggests the > other form... > well you see the trouble. > > But the situation is worse than this because of the manual interventions > necessary to fixup the portsdb. These fixups easily create dependency graphs > that never existed anywhere else before. Most often this happens because of > ports being renamed, deleted, combined, etc--the trouble here is that > the ports > tree reveals no history about these actions. > > It is left to a program like portupgrade to heuristically guess!?! what has > taken place. Now if you go through this process every week (every > day?) usually > the risk is small and it is obvious what to do, but this is not always so. > > Some speculation: I've always thought portupgrade did the Wrong Thing(tm) by > consulting the dependency graph in /var/db. Better to merely learn which > packages were installed and then exclusively use the port information... > Maybe someone knows why that would be the wrong thing to do? May I insert a "me too" here? This (everything you've written here) has been my *only* reason for choosing not to upgrade immediately. I find the ease of using the ports system *glorious*, *_until_* it comes time to upgrade (installed ports). This is especially true when you have imposed subtle changes (inserted default options for the build/ install, created/ crafted ini/ conf files). Using make.conf *seemed* like the ultimate solution. That is, until you've found that you were on the leading edge of a major revision of a port, and those options are no longer supported, or have been renamed. Still, make.conf is a wonderful tool. But even w/o custom options/conf's inposed, upgrades through portupgrade (from my experience) is a trip to hell. That I never look forward to re-living/visiting. In short; there *must* be a better (less painful) way to handle upgrading the _installed_ ports. I only wish I could figure one out. Please note; this is a solicitation. ;) I am only adding (augmenting) to what Paul has stated here. (I build/manage some 50 FreeBSD boxes. So you can imagine the grief.) --Chris H. > > Paul > _______________________________________________ > 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" > -- Shameless self-promotion follows... ... or does it? ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_hjk355868dc Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcuviXxK1cRs0zxkRAq5+AJ97LLlNOxMFaDCmZMk0XcYFEzfQfwCePZ27 VAymxtZ5Abr71g47DWDdxVg= =dikp -----END PGP SIGNATURE----- --=_hjk355868dc-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:41:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9196016A47E for ; Tue, 23 May 2006 11:41:37 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F9243D58 for ; Tue, 23 May 2006 11:41:36 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 19290 invoked from network); 23 May 2006 11:41:33 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.132.233]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 23 May 2006 11:41:33 -0000 Date: Tue, 23 May 2006 13:41:18 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20060523134118.427992d8@localhost> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_cUCdx7_SNi8VDISA+T3bDY0; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Loading geom_eli in loader.conf disables psm0 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, 23 May 2006 11:41:37 -0000 --Sig_cUCdx7_SNi8VDISA+T3bDY0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable To encrypt my home slice with geli I followed "17.16.2 Disk Encryption with geli": As I prefer to have my home directory available after boot, I additionally added: geli_devices=3D"ad0s1" geli_ad0s1_flags=3D"-k /root/ad0s1.key" to rc.conf and rebooted. geli worked, my mouse no longer did. psm0 got lost: --- dmesg-geli-enabled-in-loader.conf.txt Mon May 22 18:17:23 2006 +++ dmesg-without-geli-enabled-in-loader.conf.txt Mon May 22 18:21:33 2006 [...] @@ -76,7 +76,9 @@ atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] -acpi_ibm0: irq 12 on acpi0 +psm0: irq 12 on atkbdc0 +psm0: [GIANT-LOCKED] +psm0: model Generic PS/2 mouse, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x3bc-0x3be irq 7 on acpi0 @@ -88,12 +90,13 @@ sio1: type 16550A battery0: on acpi0 acpi_acad0: on acpi0 +acpi_ibm0: on acpi0 pmtimer0 on isa0 [...] After I removed 'geom_eli_load=3D"YES"' in loader.conf and rebooted psm0 was back and my mouse started to work again. I saw no geli regression either, I assume geom_eli.ko is loaded on demand by geli's rc script. fk@TP51 ~ $kldstat Id Refs Address Size Name 1 25 0xc0400000 41309c kernel 2 1 0xc0814000 b880 unionfs.ko 3 1 0xc0820000 5760 if_tap.ko 4 1 0xc0826000 565c snd_ich.ko 5 2 0xc082c000 258d4 sound.ko 6 1 0xc0852000 43f4 acpi_video.ko 7 3 0xc0857000 62fdc acpi.ko 8 1 0xc08ba000 21dac radeon.ko 9 2 0xc08dc000 10d80 drm.ko 10 1 0xc08ed000 4c88 acpi_ibm.ko 11 3 0xc08f2000 215cc wlan.ko 12 1 0xc0914000 2ea0 wlan_wep.ko 13 1 0xc0917000 eec8 if_iwiNG.ko 14 3 0xc0926000 2e60 firmware.ko 15 1 0xc0929000 300fc iwi_bss.ko 16 1 0xc095a000 9500 cpufreq.ko 17 1 0xc35a2000 b000 geom_eli.ko 18 1 0xc35c1000 19000 crypto.ko 19 1 0xc35ad000 a000 zlib.ko My /boot/loader.conf: loader_logo=3D"beastie" loader_color=3D"YES" autoboot_delay=3D"1" hw.ata.atapi_dma=3D"1" radeon_load=3D"YES" acpi_video_load=3D"YES" acpi_ibm_load=3D"YES" wlan_load=3D"YES" wlan_wep_load=3D"YES" if_iwiNG_load=3D"YES" iwi_bss_load=3D"YES" cpufreq_load=3D"YES" snd_ich_load=3D"YES" if_tap_load=3D"YES" unionfs_load=3D"YES" #geom_eli_load=3D"YES" hw.psm.synaptics_support=3D"1" fk@TP51 ~ $uname -a FreeBSD TP51.local 6.1-STABLE FreeBSD 6.1-STABLE #30: Mon May 22 15:52:13 CEST 2006 fk@TP51.local:/usr/obj/usr/src/sys/THINKPAD i386 Fabian --=20 http://www.fabiankeil.de/ --Sig_cUCdx7_SNi8VDISA+T3bDY0 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEcvTrjV8GA4rMKUQRAp2zAJ0VvzzB+t3Xhg0MrQgcavOha4chzgCfQjSX HRTsGghEzjUR0Q01aYpT1LQ= =fN3n -----END PGP SIGNATURE----- --Sig_cUCdx7_SNi8VDISA+T3bDY0-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:49:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBD6A16A426 for ; Tue, 23 May 2006 11:49:07 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2007943D45 for ; Tue, 23 May 2006 11:49:06 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp213-221.lns1.adl2.internode.on.net [203.122.213.221]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k4NBn4kH061819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 21:19:05 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Peter Jeremy Date: Tue, 23 May 2006 21:18:50 +0930 User-Agent: KMail/1.9.1 References: <200605131413.17020.doconnor@gsoft.com.au> <200605231923.21263.doconnor@gsoft.com.au> <20060523101550.GC769@turion.vk2pj.dyndns.org> In-Reply-To: <20060523101550.GC769@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1420584.zRyokT7iZO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605232118.59080.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: Odd RS232 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: Tue, 23 May 2006 11:49:07 -0000 --nextPart1420584.zRyokT7iZO Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 23 May 2006 19:45, Peter Jeremy wrote: > On Tue, 2006-May-23 19:23:20 +0930, Daniel O'Connor wrote: > >I would hope that 9600 baud wouldn't be *too* fast for a 2GHz CPU :( > > That depends on what else is sharing the IRQ. PLIP can give you > 10's of msec of latency. PIO disks can also destroy latency as > can NE2000-style NICs. Hmm, well I just realised I don't actually know what it IS sharing an IRQ w= ith=20 as puc/sio don't say :( I don't have any ISA hardware or PIO disks in the system. I do have a paral= lel=20 port which I am not using though. =2D-=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 --nextPart1420584.zRyokT7iZO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEcvaq5ZPcIHs/zowRAtyuAJ40LgU+fpuCnNybsVUCgMMPntXVPQCfcFtY ioB6W9wvnffPcWgp5P4fiCQ= =U9jy -----END PGP SIGNATURE----- --nextPart1420584.zRyokT7iZO-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:53:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEA5C16A447 for ; Tue, 23 May 2006 11:53:11 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 560E943D6D for ; Tue, 23 May 2006 11:53:06 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp213-221.lns1.adl2.internode.on.net [203.122.213.221]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k4NBr4AL061862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 21:23:04 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Peter Jeremy Date: Tue, 23 May 2006 21:23:01 +0930 User-Agent: KMail/1.9.1 References: <200605131413.17020.doconnor@gsoft.com.au> <20060523101550.GC769@turion.vk2pj.dyndns.org> <200605232118.59080.doconnor@gsoft.com.au> In-Reply-To: <200605232118.59080.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1991341.0hIPZGgIT0"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605232123.03222.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: Odd RS232 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: Tue, 23 May 2006 11:53:11 -0000 --nextPart1991341.0hIPZGgIT0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 23 May 2006 21:18, Daniel O'Connor wrote: > On Tuesday 23 May 2006 19:45, Peter Jeremy wrote: > > On Tue, 2006-May-23 19:23:20 +0930, Daniel O'Connor wrote: > > >I would hope that 9600 baud wouldn't be *too* fast for a 2GHz CPU :( > > > > That depends on what else is sharing the IRQ. PLIP can give you > > 10's of msec of latency. PIO disks can also destroy latency as > > can NE2000-style NICs. > > Hmm, well I just realised I don't actually know what it IS sharing an IRQ > with as puc/sio don't say :( Duh I am blind.. It shares an IRQ with the RAID controller.. atapci0: port 0x7800-0x783f,0x7400-0x= 740f,0x7000-0x707f mem 0xfb300000-0xfb300fff,0xfb200000-0xfb21ffff irq 18 a= t device 8.0 on pci0 puc0: port 0x9400-0x941f irq 18 at device 13.0 o= n pci0 The disks are SATA150 though, no PIO here! =2D-=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 --nextPart1991341.0hIPZGgIT0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEcvef5ZPcIHs/zowRAkFQAJ4tPK6jbnpDrEbiIiLZkj8C9Gm/yACdFLv8 sR2Q4Hx8tRV+U4ndI955Zwg= =JPqB -----END PGP SIGNATURE----- --nextPart1991341.0hIPZGgIT0-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:53:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0E1F16A586 for ; Tue, 23 May 2006 11:53:22 +0000 (UTC) (envelope-from vladgalu@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A0FB43D49 for ; Tue, 23 May 2006 11:53:20 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by wr-out-0506.google.com with SMTP id i28so1312412wra for ; Tue, 23 May 2006 04:53:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PrtKpx0g/RjwcrHjuc4edn+SPSxj9WrZmgw4Yv2PVdQxyaY9OKRVDX5sbOvPsdJoS8L1FDvU3e1xJiiiN0TlgJtuDNpm6dlJQUuRIlpFOOO6Y/P/gru+b10kOjcdGgPSJ6pvu53BRnWM4XxX/JMD/Vtf5NhrzHG9kPpJXcYOnpg= Received: by 10.54.160.15 with SMTP id i15mr2957842wre; Tue, 23 May 2006 04:53:20 -0700 (PDT) Received: by 10.54.128.12 with HTTP; Tue, 23 May 2006 04:53:20 -0700 (PDT) Message-ID: <79722fad0605230453vc0436d5o352f0f10c995656d@mail.gmail.com> Date: Tue, 23 May 2006 14:53:20 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org In-Reply-To: <79722fad0605111452r2e5da097x21aa86a63e4dfe52@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79722fad0605111452r2e5da097x21aa86a63e4dfe52@mail.gmail.com> Subject: Re: 6.1-stable crash 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, 23 May 2006 11:53:24 -0000 On 5/12/06, Vlad GALU wrote: [...] Just for the record, this has just happened again. --=20 If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:57:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9F4C16A455 for ; Tue, 23 May 2006 11:57:30 +0000 (UTC) (envelope-from steinex@nognu.de) Received: from shodan.nognu.de (shodan.nognu.de [85.14.216.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55C8743D46 for ; Tue, 23 May 2006 11:57:29 +0000 (GMT) (envelope-from steinex@nognu.de) Received: by shodan.nognu.de (Postfix, from userid 1002) id 0C33AB854; Tue, 23 May 2006 13:57:28 +0200 (CEST) Date: Tue, 23 May 2006 13:57:28 +0200 From: Frank Steinborn To: "Chris H." Mail-Followup-To: "Chris H." , freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> <20060522133424.3087acfc@it.buh.tecnik93.com> <20060523043233.4ul85wdeeoowocwk@webmail.1command.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060523043233.4ul85wdeeoowocwk@webmail.1command.com> User-Agent: mutt-ng/devel-r804 (FreeBSD) Message-Id: <20060523115728.0C33AB854@shodan.nognu.de> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD Security Survey 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, 23 May 2006 11:57:30 -0000 Chris H. wrote: > This brings up a point I have been wanting to bring up for over a mos.; > I adopted an "orphaned" port (contacted the owner, whom then relenquished > ownership to me.). But found it _more_ than difficult to discover how > to inform the fBSD port(s) system of it's new, *un*orphaned status. > I read through the online doc's about it. But got dizzy with the > circularness of it. Searching led to no _difinative_ answer(s) either. > Is it still send pr just to update it's status? Couldn't there be an > online form to change ownership/ stewardship? I *can* comprehend the > send pr system. I simply can't understand how to change/ update > ownership/ stewardship. Perhaps this is why so many of the orphaned > ports remain in this state. Open a PR and simply set MAINTAINER to your own address. Use category 'ports' and and class 'change-request'. Frank From owner-freebsd-stable@FreeBSD.ORG Tue May 23 11:59:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11CFE16A4E0 for ; Tue, 23 May 2006 11:59:44 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E781343D46 for ; Tue, 23 May 2006 11:59:42 +0000 (GMT) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from circe (circe.rz.RWTH-Aachen.DE [134.130.3.36]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IZP003EFVZG52@ms-dienst.rz.rwth-aachen.de> for freebsd-stable@freebsd.org; Tue, 23 May 2006 13:59:41 +0200 (MEST) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Tue, 23 May 2006 13:59:40 +0200 (MEST) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.1/8.13.1/1) with ESMTP id k4NBxduN002895; Tue, 23 May 2006 13:59:39 +0200 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1FiVY3-0008QU-WC; Tue, 23 May 2006 13:59:40 +0200 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id A3D423F40B; Tue, 23 May 2006 13:59:39 +0200 (CEST) Date: Tue, 23 May 2006 13:59:39 +0200 From: Christian Brueffer In-reply-to: <20060521193613.GA38148@xor.obsecurity.org> To: Kris Kennaway Message-id: <20060523115939.GA1601@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; boundary=r5Pyd7+fXNt84Ff3; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.1-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <20060521190405.GB1308@haakonia.hitnet.RWTH-Aachen.DE> <20060521193613.GA38148@xor.obsecurity.org> Cc: freebsd-stable@freebsd.org Subject: Re: generic_bcopy() corrupts backtrace? 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, 23 May 2006 11:59:44 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 21, 2006 at 03:36:13PM -0400, Kris Kennaway wrote: > On Sun, May 21, 2006 at 09:04:05PM +0200, Christian Brueffer wrote: >=20 > > Core and debug kernel are available, but the trace appears to be > > corrupted. >=20 > Sorry to hijack your thread, but I'm also seeing corrupted backtraces > from kgdb involving generic_bcopy(). >=20 > Is there something about its asm implementation that confuses kgdb? >=20 Hmm, not sure. As far as i recall, all traces I got from kgdb during the last months were corrupted. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEcvkrbHYXjKDtmC0RAn8IAJwLS7Ceqmknp5kefNPBgd5OZv7l6gCghOEK EZSjSD0LHuigBWFk4KaK6jA= =J96R -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 13:23:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 869AF16A433 for ; Tue, 23 May 2006 13:23:08 +0000 (UTC) (envelope-from fbsd@1command.com) Received: from mail.1command.com (mail.1command.com [216.177.243.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A76543D49 for ; Tue, 23 May 2006 13:23:06 +0000 (GMT) (envelope-from fbsd@1command.com) Received: from mail.1command.com (localhost.1command.com [127.0.0.1]) by mail.1command.com (8.13.3/8.13.3) with ESMTP id k4NDN3UW067100 for ; Tue, 23 May 2006 06:23:04 -0700 (PDT) (envelope-from fbsd@1command.com) Received: (from www@localhost) by mail.1command.com (8.13.3/8.13.3/Submit) id k4NDN35k067099 for freebsd-stable@freebsd.org; Tue, 23 May 2006 06:23:03 -0700 (PDT) (envelope-from fbsd@1command.com) Received: from ns1.1command.com (ns1.1command.com [216.177.243.34]) by webmail.1command.com (H.R. Communications Messaging System) with HTTP; Tue, 23 May 2006 06:23:03 -0700 Message-ID: <20060523062303.gipvo6f4ocogcg0s@webmail.1command.com> X-Priority: 3 (Normal) Date: Tue, 23 May 2006 06:23:03 -0700 From: "Chris H." To: freebsd-stable@freebsd.org References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <44714FBB.4000603@samsco.org> <44718700.2060102@kernel32.de> <20060522133424.3087acfc@it.buh.tecnik93.com> <20060523043233.4ul85wdeeoowocwk@webmail.1command.com> <20060523115728.0C33AB854@shodan.nognu.de> In-Reply-To: <20060523115728.0C33AB854@shodan.nognu.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_30yx9mlipugw"; protocol="application/pgp-signature"; micalg="pgp-sha1" Content-Transfer-Encoding: 7bit User-Agent: H.R. Communications Internet Messaging System (HCIMS) 4.1 Professional (not for redistribution) / FreeBSD-5.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 13:23:09 -0000 This message is in MIME format and has been PGP signed. --=_30yx9mlipugw Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit Quoting Frank Steinborn : > Chris H. wrote: >> This brings up a point I have been wanting to bring up for over a mos.; >> I adopted an "orphaned" port (contacted the owner, whom then relenquished >> ownership to me.). But found it _more_ than difficult to discover how >> to inform the fBSD port(s) system of it's new, *un*orphaned status. >> I read through the online doc's about it. But got dizzy with the >> circularness of it. Searching led to no _difinative_ answer(s) either. >> Is it still send pr just to update it's status? Couldn't there be an >> online form to change ownership/ stewardship? I *can* comprehend the >> send pr system. I simply can't understand how to change/ update >> ownership/ stewardship. Perhaps this is why so many of the orphaned >> ports remain in this state. > > Open a PR and simply set MAINTAINER to your own address. Use category > 'ports' and and class 'change-request'. Will do. Thank you very much for taking the time to respond. --Chris H. > > Frank > _______________________________________________ > 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" > -- ----------------------------------------------------------------- FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 ///////////////////////////////////////////////////////////////// --=_30yx9mlipugw Content-Type: application/pgp-signature Content-Description: PGP Digital Signature Content-Disposition: inline Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcwy3XxK1cRs0zxkRAjQhAJ9T4kxqZ4nvTLHA3W9/6sS4wQwwzQCdFJwO 6mn/Fdp6kvMxCEaPJkJj3W0= =PepX -----END PGP SIGNATURE----- --=_30yx9mlipugw-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 13:56:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DBA416A432 for ; Tue, 23 May 2006 13:56:25 +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 2E99243D45 for ; Tue, 23 May 2006 13:56:24 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k4NDuLNh049235; Tue, 23 May 2006 09:56:21 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k4NDuBlR024291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 May 2006 09:56:20 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060523095411.11c41c00@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Tue, 23 May 2006 09:55:54 -0400 To: "Daniel O'Connor" From: Mike Tancsa In-Reply-To: <200605231923.21263.doconnor@gsoft.com.au> References: <200605131413.17020.doconnor@gsoft.com.au> <20060513123030.GA32024@intserv.int1.b.intern> <200605231923.21263.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Cc: freebsd-stable@freebsd.org Subject: Re: Odd RS232 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: Tue, 23 May 2006 13:56:25 -0000 At 05:53 AM 23/05/2006, Daniel O'Connor wrote: >On Saturday 13 May 2006 22:00, Holger Kipp wrote: > > > If you encounter silo overflows, you might need to increase > > cp4ticks in sio.c, eg > > - cp4ticks = speed / 10 / hz * 4; > > + cp4ticks = speed / 10 / hz * 40; > > and/or you might want to change hz from 1000 back to 100. > >OK, I'll try it. This fixes the overflows for me as well. I have a number of boxes out in the field running with this local modification (40 vs 4). Without it, I have problems running a PCI modem at speeds better than 9600 without causing overflows. ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue May 23 13:59:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDF9516A4F7 for ; Tue, 23 May 2006 13:59:57 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 259A043D6B for ; Tue, 23 May 2006 13:59:46 +0000 (GMT) (envelope-from howard@leadmon.net) Received: from gamer (gamer.leadmon.net [207.114.24.7]) (authenticated bits=0) by ibm.leadmon.net (8.13.6/8.13.6/LNSG+ORDB+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id k4NDxflj063071; Tue, 23 May 2006 09:59:46 -0400 (EDT) (envelope-from howard@leadmon.net) Authentication-Results: ibm.leadmon.net from=howard@leadmon.net; sender-id=pass; spf=pass X-SenderID: Sendmail Sender-ID Filter v0.2.12 ibm.leadmon.net k4NDxflj063071 From: "Howard Leadmon" To: "'Rong-en Fan'" , "'Konstantin Belousov'" Date: Tue, 23 May 2006 09:59:36 -0400 Organization: Leadmon Networking Message-ID: <013b01c67e71$23aaacf0$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <6eb82e0605230556n31b86e55y1b07a2ef6ad9ca14@mail.gmail.com> Thread-Index: AcZ+aGOjBEydwH1yRvSlNpp7LGH0WQAB+TfQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (ibm.leadmon.net [207.114.24.13]); Tue, 23 May 2006 09:59:46 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.2/1478/Mon May 22 17:01:38 2006 on ibm.leadmon.net X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, 'Kris Kennaway' Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 13:59:57 -0000 > > > If there are any thing I can provide to help tracking this down. > > > Please let me know. By the way, I tried with truss/kdump > to see what > > > happens when nfsd eats lot of CPUs, but in vain. They do > not return anything. > > > > > I tried your recipe on 7-CURRENT with locally exported fs, > remounted > > over nfs. I did not get the behaviour your described. > > As noted in my previous thread, I have another 6.1-RELEASE > nfs server, which does not have this problem. > > > Could you, please, provide the backtrace for the nfsd that eats the > > CPU (from the ddb). I think it would be helpful to get several > > backtraces (i.e., bt , cont, bt ...) > to see where > > it running. > > I'm afraid that I can not do that. Last time I tried breaking > into ddb (on 5.x), it hangs my serial console and the server > is miles away :-( . Perhaps we can ask Howard to do that? I am more than willing to do that, as this machine runs here with me, so if needed I can easily get on a console, or perform a reboot. Can one of you shed a little light on exactly what I need to do, and how to do this? I ask as I have never used this ddb stuff, so not clue one on how to go about getting the information your looking to find. Guess I have been lucky, and just never had an issue that took things to this level. > > Also, just in case, does filesystem that is exported and shows > > problem, have quotas enabled ? One line of your fstab has > userquotas, other does not. As to userquotas, I just tried accessing the NFS mounts here, as some have filesystems with quotas, and some don't, and both are exibiting the exact same problem. So using quotas is for sure not the problem, or should I say not the trigger to the problem. > Regards, > Rong-En Fan --- Howard Leadmon http://www.leadmon.net From owner-freebsd-stable@FreeBSD.ORG Tue May 23 14:14:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A9ED16A464 for ; Tue, 23 May 2006 14:14:38 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DE3C43D5F for ; Tue, 23 May 2006 14:14:18 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nf-out-0910.google.com with SMTP id l24so1060926nfc for ; Tue, 23 May 2006 07:14:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p8XRJNQtnMPVAzV03Gymwwuh9luj0WZ7e16JHDpMf5W44VH4iOgbcGR8pioqKOQUAmm+9BrFeHarctO82SFQpCspHdpnYWp297amgZ/4ByJiPlP4c8gLu3iyU5Yy1J0k137v65nKMX+i3MkFv0MNYZhFNGPrmNhzhfMwzfG0Z1M= Received: by 10.48.202.1 with SMTP id z1mr4735279nff; Tue, 23 May 2006 05:56:54 -0700 (PDT) Received: by 10.48.30.7 with HTTP; Tue, 23 May 2006 05:56:54 -0700 (PDT) Message-ID: <6eb82e0605230556n31b86e55y1b07a2ef6ad9ca14@mail.gmail.com> Date: Tue, 23 May 2006 08:56:54 -0400 From: "Rong-en Fan" To: "Konstantin Belousov" In-Reply-To: <20060523081041.GL54541@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <017301c67784$45377a90$071872cf@Leadmon.local> <20060515024958.GA99002@xor.obsecurity.org> <6eb82e0605221443m5cc3c93bwaf9126ff2fb59667@mail.gmail.com> <20060523081041.GL54541@deviant.kiev.zoral.com.ua> Cc: freebsd-stable@freebsd.org, Howard Leadmon , Kris Kennaway Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 14:14:38 -0000 On 5/23/06, Konstantin Belousov wrote: > On Mon, May 22, 2006 at 05:43:32PM -0400, Rong-en Fan wrote: > > On 5/14/06, Kris Kennaway wrote: > > >On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: > > >> > > >> Hello All, > > >> > > >> I have been running FBSD a long while, and actually running since t= he > > >5.x > > >> releases on the server I am having troubles with. I basically have= a > > >small > > >> network and just use NIS/NFS to link my various FBSD and Solaris mac= hines > > >> together. > > >> > > >> This has all been running fine up till a few days ago, when all of = a > > >sudden > > >> NFS came to a crawl, and CPU usage so high the box appears to freeze > > >almost. > > >> When I had 6.1-RC running all seemed well, then came the announcemen= t > > >for the > > >> official 6.1 release, so I did the cvs updates, made world, kernel, = and > > >ran > > >> mergemaster to get everything up to the 6.1 stable version. > > >> > > >> Now after doing this, something is wrong with NFS. It works, it w= ill > > >return > > >> information and open files, just it's very very slow, and while > > >performing a > > >> request the CPU spike is astounding. A simple du of my home directo= ry > > >can > > >> take minutes, and machine all but locks up if the request is done ov= er > > >NFS. > > >> Here is top snip: > > >> > > >> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > > >COMMAND > > >> 497 root 1 4 0 1252K 780K - 2 50:42 188.48% = nfsd > > >> > > >> > > >> This is a nice IBM eServer with dual P4-XEON's and a couple GB or R= AM > > >on a > > >> disk array, and locally is screams, heck NFS used to scream till I > > >updated. I > > >> am not really sure what info would be useful in debugging, so won't = post > > >tons > > >> of misc junk in this eMail, but if anyone has any ideas as to how be= st to > > >> figure out and resolve this issue it would sure be appreicated... > > > > > >Use tcpdump and related tools to find out what traffic is being sent. > > > > > >Also verify that you did not change your system configuration in any > > >way: there have been no changes to NFS since the release, so it is > > >unclear why an update would cause the problem to suddenly occur. > > > > > >Kris > > > > Hi Kris and Howard, > > > > As I posted few days ago, I have similar problems like Howard's > > (some details in the thread "6.1-RELEASE, em0 high interrupt rate > > and nfsd eats lots of cpu" on stable@). After binary searching > > the source tree, I found that > > > > RELENG_6_1, 2006.04.30.03.57 ok > > RELENG_6_1, 2006.04.30.04.00 bad > > > > The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. > > With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, > > the same problem occurs. > > > > Let me refresh what problems I'm seeing > > > > 1. a client (no matter Linux 2.6.16 or FreeBSD 6.1) runs du on > > a nfs directory > > 2. on server-side, nfsd starts to eats lots of CPU > > 3. the du finishes > > 4. on server-side, nfsd still eats lots of CPU, but there is no > > nfs traffic. Wait for 5 minutes, you can still see that nfsd is > > "running" and eats lots of CPU. > > > > On FreeBSD 6.1R client, it uses UDP mount and fstab is like > > "rw,-L,nosuid,bg,nodev". On Linux cleint, it uses UDP mount and > > fstab is like "defaults,udp,hard,intr,nfsvers=3D3,rsize=3D8192,wsize=3D= 8192". > > The server's kernel conf is at > > > > http://www.rafan.org/FreeBSD/nfs/KERNEL > > > > Some related configuration files: > > > > /etc/export > > /export/dir1 host1 host2... > > /export/dir2 host1 host2... > > > > /etc/rc.conf > > nfs_server_enable=3D"YES" > > nfs_server_flags=3D"-u -t -n 16" > > mountd_enable=3D"YES" > > mountd_flags=3D"-r -l -n" > > rpc_lockd_enable=3D"YES" > > rpc_statd_enable=3D"YES" > > rpcbind_enable=3D"YES" > > > > /etc/fstab: > > /dev/... /export/dir1 ufs rw,nosuid,noexec 2 2 > > /dev/... /export/dir2 ufs rw,nosuid,noexec,userquota 2 2 > > > > The NFS server is also using amd to mount some backup directories > > from another NFS server. the amd.conf is > > > > [global] > > browsable_dirs =3D yes > > map_type =3D file > > mount_type =3D nfs > > auto_dir =3D /nfs > > fully_qualified_hosts =3D no > > log_file =3D syslog > > nfs_proto =3D udp > > nfs_allow_insecure_port =3D no > > nfs_vers =3D 3 > > # plock =3D yes > > selectors_on_default =3D yes > > restart_mounts =3D yes > > > > [/backup] > > map_options =3D type:=3Ddirect > > map_name =3D /etc/amd.direct > > > > /etc/amd.direct: > > /defaults > > opts:=3Drw,grpid,resvport,vers=3D3,proto=3Dudp,nosuid,nodev,rsize=3D819= 2,wsize=3D8192 > > backup type:=3Dnfs;rhost:=3Dnfs2;rfs:=3D/nfs2/${host} > > > > > > If there are any thing I can provide to help tracking this down. Please > > let me know. By the way, I tried with truss/kdump to see what happens > > when nfsd eats lot of CPUs, but in vain. They do not return anything. > > > I tried your recipe on 7-CURRENT with locally exported fs, remounted > over nfs. I did not get the behaviour your described. As noted in my previous thread, I have another 6.1-RELEASE nfs server, which does not have this problem. > Could you, please, provide the backtrace for the nfsd that > eats the CPU (from the ddb). I think it would be helpful to get several > backtraces (i.e., bt , cont, bt ...) to > see where it running. I'm afraid that I can not do that. Last time I tried breaking into ddb (on = 5.x), it hangs my serial console and the server is miles away :-( . Perhaps we can ask Howard to do that? > Also, just in case, does filesystem that is exported and shows problem, > have quotas enabled ? One line of your fstab has userquotas, other does n= ot. No. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Tue May 23 14:27:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB44416A4C5 for ; Tue, 23 May 2006 14:27:03 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9B5243D62 for ; Tue, 23 May 2006 14:27:02 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so780688nfc for ; Tue, 23 May 2006 07:27:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=okjZofwjG9cxd7UmPD/K2WiiE6sTAfbDU9fXodEYKBmqsx0AgKQmdcHjd1XORRHusaNsNdV325EfaTmthwD8LL/27zmZh5+c5GEgVPsnv9E8+oMxe8KHACKfQL08dcWQfsU0QJk0iYVF1L0dCLE3t7pXEIkElgr7iwGkm+P0BtI= Received: by 10.48.225.3 with SMTP id x3mr499804nfg; Tue, 23 May 2006 07:18:09 -0700 (PDT) Received: by 10.48.30.7 with HTTP; Tue, 23 May 2006 07:18:44 -0700 (PDT) Message-ID: <6eb82e0605230718l337a58efmc85637afdec4fffb@mail.gmail.com> Date: Tue, 23 May 2006 10:18:44 -0400 From: "Rong-en Fan" To: "Howard Leadmon" In-Reply-To: <013b01c67e71$23aaacf0$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6eb82e0605230556n31b86e55y1b07a2ef6ad9ca14@mail.gmail.com> <013b01c67e71$23aaacf0$071872cf@Leadmon.local> Cc: Konstantin Belousov , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 14:27:09 -0000 On 5/23/06, Howard Leadmon wrote: > > > > > > If there are any thing I can provide to help tracking this down. > > > > Please let me know. By the way, I tried with truss/kdump > > to see what > > > > happens when nfsd eats lot of CPUs, but in vain. They do > > not return anything. > > > > > > > I tried your recipe on 7-CURRENT with locally exported fs, > > remounted > > > over nfs. I did not get the behaviour your described. > > > > As noted in my previous thread, I have another 6.1-RELEASE > > nfs server, which does not have this problem. > > > > > Could you, please, provide the backtrace for the nfsd that eats the > > > CPU (from the ddb). I think it would be helpful to get several > > > backtraces (i.e., bt , cont, bt ...) > > to see where > > > it running. > > > > I'm afraid that I can not do that. Last time I tried breaking > > into ddb (on 5.x), it hangs my serial console and the server > > is miles away :-( . Perhaps we can ask Howard to do that? > > I am more than willing to do that, as this machine runs here with me, so= if > needed I can easily get on a console, or perform a reboot. Can one of yo= u > shed a little light on exactly what I need to do, and how to do this? I = ask > as I have never used this ddb stuff, so not clue one on how to go about > getting the information your looking to find. Guess I have been lucky, a= nd > just never had an issue that took things to this level. At least you have to add the following to your kernel: options KDB options DDB Recompile it, reboot. You would better to setup a serial console so you can easily copy thing from ddb output. To do it, you have to put "device sio" in your kernel configuration and some files below: /boot.config -Dh /boot/loader.conf comconsole_speed=3D115200 machdep.conspeed=3D115200 /etc/ttys ttyd0 "/usr/libexec/getty std.115200" cons25 on secure On the other machine, /etc/remote: com1:dv=3D/dev/cuad0:br#115200:pa=3Dnone: Then, use "tip com1" to attach the nfs server. The above settings assume your serial console on nfs server is on COM1 and on the client side is also COM1. If that's not the case, please follow Handbook for howto setup a serial console other than COM1. To break into ddb, either use ctrl+alt+esc or send a BREAK (I think ^b will do) via serial line. After that, you should see db> Then you first use "ps" to find out the nfsd pid (better to remember the pid which eats lots of cpu before enter ddb). After that, do what Konstantin suggests. I have never tried "cont" in db. I guess that will return the execution back to kernel and you need to break into ddb again to do another "bt ". By the way, could you verify that backing out vfs_lookup.c rev 1.90 helps in your situation? If not, maybe we are seeing different problems, and then I have to figure out how to make my serial console work here. Thanks, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Tue May 23 14:39:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C68B516A6CC for ; Tue, 23 May 2006 14:39:40 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9559343D46 for ; Tue, 23 May 2006 14:39:39 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 7861AB826 for ; Tue, 23 May 2006 10:39:38 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <20060521231657.O6063@abigail.angeltread.org> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-1-436769299; protocol="application/pkcs7-signature" Message-Id: <174B87B3-AD67-48C8-B44F-90F0BC8093C3@khera.org> From: Vivek Khera Date: Tue, 23 May 2006 10:39:37 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 14:39:41 -0000 --Apple-Mail-1-436769299 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 22, 2006, at 12:38 AM, Brent Casavant wrote: > So, in short, that's why *I* rarely update ports for security reasons. Another valid reason is configuration management. We run web services, and in order to ensure nothing breaks, we have to use a fixed set of code. Upgrading any piece of that requires many steps, including verifying functionality and checking for regressions, etc. Basically we have to run our full regression tests on any changes, then roll them out in a controlled fashion minimizing down time. --Apple-Mail-1-436769299-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 15:00:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9622D16A669 for ; Tue, 23 May 2006 15:00:14 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C30543D76 for ; Tue, 23 May 2006 15:00:13 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id A634AB826 for ; Tue, 23 May 2006 11:00:12 -0400 (EDT) In-Reply-To: <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> References: <4471361B.5060208@freebsd.org> <20060521231657.O6063@abigail.angeltread.org> <009101c67d8c$ee013db0$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 (Apple Message framework v750) X-Priority: 3 Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-438004074; protocol="application/pkcs7-signature" Message-Id: <9BCDA9F8-52E0-46DD-B018-2ECF1E226DFC@khera.org> From: Vivek Khera Date: Tue, 23 May 2006 11:00:12 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: FreeBSD Security Survey 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, 23 May 2006 15:00:15 -0000 --Apple-Mail-2-438004074 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 22, 2006, at 6:45 AM, Steven Hartland wrote: > On good example of portupgrade "going off on one" is a simple > upgrade of mtr we dont install any X on our machines so mtr-nox11 > is installed. Whenever I've tried portupgrade in the past its > always trolled of and started downloading and build the behemoth > that is X, CTRL+C hence always ensues and I forget about upgrading > until I really HAVE to. Well, then you've misconfigured your portupgrade. It never does so for me because I have WITHOUT_X11 and WITHOUT_GUI set in /etc/ make.conf (why two knobs, I don't know, but many ports use WITHOUT_GUI instead of WITHOUT_X11). --Apple-Mail-2-438004074-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 15:49:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A90D16A981 for ; Tue, 23 May 2006 15:49:24 +0000 (UTC) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (classis.ru [213.248.60.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B2843D46 for ; Tue, 23 May 2006 15:49:23 +0000 (GMT) (envelope-from citrin@citrin.ru) Received: from mail.classis.ru (localhost [127.0.0.1]) by mail.classis.ru (Postfix) with ESMTP id 44B491229CC2 for ; Tue, 23 May 2006 19:49:22 +0400 (MSD) Received: from citrin.rambler.stack.net (citrin.rambler.stack.net [81.19.65.41]) by mail.classis.ru (Postfix) with ESMTP id 29F2A1222059 for ; Tue, 23 May 2006 19:49:22 +0400 (MSD) Date: Tue, 23 May 2006 19:49:21 +0400 From: Anton Yuzhaninov X-Mailer: The Bat! (v3.62.14) Professional Organization: Rambler X-Priority: 3 (Normal) Message-ID: <1084886706.20060523194921@citrin.ru> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="----------BA1111181F4426B" X-AV-Checked: ClamAV using ClamSMTP on mail.classis.ru X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: mount_mfs 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, 23 May 2006 15:49:24 -0000 This is a cryptographically signed message in MIME format. ------------BA1111181F4426B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hello, How create memory disk from /etc/fstab in FreeBSD 6 without soft-updates? As I can see it impossible. flag -S not allowed in compatibility mode, but by default disk created with soft-updates turned on. I see to ways to fix this problem: 1. In compatibility mode turn off soft-updates --- mdmfs.c.orig Tue May 23 19:38:26 2006 +++ mdmfs.c Tue May 23 19:43:42 2006 @@ -133,6 +133,7 @@ if (compat) usage(); compat =3D true; + softdep =3D false; break; case 'c': argappend(&newfs_arg, "-c %s", optarg); 2. In compatibility mode allow -S option --- mdmfs.c.orig Tue May 23 19:38:26 2006 +++ mdmfs.c Tue May 23 19:45:02 2006 @@ -205,8 +205,6 @@ free(set); break; case 'S': - if (compat) - usage(); softdep =3D false; break; case 's': --=20 WBR, Anton Yuzhaninov. P. S. Benchmark show that memory disk mounted in async mode work up to 30% faster when soft-updates turned off ------------BA1111181F4426B-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 18:16:41 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C33816A430 for ; Tue, 23 May 2006 18:16:41 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id B75DD43D53 for ; Tue, 23 May 2006 18:16:40 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id AE361136CF9 for ; Tue, 23 May 2006 19:16:39 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k4NIGcGt007003 for ; Tue, 23 May 2006 22:16:38 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k4NIGcWj007002 for stable@freebsd.org; Tue, 23 May 2006 22:16:38 +0400 (MSD) (envelope-from dkirhlarov) Date: Tue, 23 May 2006 22:16:38 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060523181638.GC767@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: quota and snapshots in 6.1-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, 23 May 2006 18:16:41 -0000 Hi, list. Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock problems. What the current situation with this? I'm ready to test patches, if needed. WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Tue May 23 18:30:22 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA08C16A429 for ; Tue, 23 May 2006 18:30:22 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2512343D60 for ; Tue, 23 May 2006 18:30:21 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nf-out-0910.google.com with SMTP id k26so707105nfc for ; Tue, 23 May 2006 11:30:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VNmsydegCYA8gWWk8e8PuAqVqHPHpqc0bACDt5q7pa4qlfvJju+BTBo0FOitysXl0zN0YVibSX73mKQ6ELdRo0ctaNq7ECOYl2FttE/ryjxNLvjERptIQLePj7u2inFEIyEptxaIz25V6FLS7kOrgNqyZb2QXM/gw1ePrDHbsAg= Received: by 10.48.214.18 with SMTP id m18mr4979885nfg; Tue, 23 May 2006 11:20:07 -0700 (PDT) Received: by 10.48.30.7 with HTTP; Tue, 23 May 2006 11:20:07 -0700 (PDT) Message-ID: <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> Date: Tue, 23 May 2006 14:20:07 -0400 From: "Rong-en Fan" To: stable@freebsd.org In-Reply-To: <20060523181638.GC767@dimma.mow.oilspace.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060523181638.GC767@dimma.mow.oilspace.com> Cc: Subject: Re: quota and snapshots in 6.1-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, 23 May 2006 18:30:22 -0000 On 5/23/06, Dmitriy Kirhlarov wrote: > Hi, list. > > Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock > problems. What the current situation with this? I'm ready to test > patches, if needed. > > WBR IIRC, there are some quota and snapshots changes merged in 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want to try that. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Tue May 23 18:55:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16E8116A80F for ; Tue, 23 May 2006 18:55:45 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95F0B43D45 for ; Tue, 23 May 2006 18:55:44 +0000 (GMT) (envelope-from howard@leadmon.net) Received: from gamer (gamer.leadmon.net [207.114.24.7]) (authenticated bits=0) by ibm.leadmon.net (8.13.6/8.13.6/LNSG+ORDB+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id k4NItdYc002479; Tue, 23 May 2006 14:55:43 -0400 (EDT) (envelope-from howard@leadmon.net) Authentication-Results: ibm.leadmon.net from=howard@leadmon.net; sender-id=pass; spf=pass X-SenderID: Sendmail Sender-ID Filter v0.2.12 ibm.leadmon.net k4NItdYc002479 From: "Howard Leadmon" To: "'Rong-en Fan'" Date: Tue, 23 May 2006 14:55:34 -0400 Organization: Leadmon Networking Message-ID: <000001c67e9a$7c6c3f10$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <6eb82e0605230718l337a58efmc85637afdec4fffb@mail.gmail.com> Thread-Index: AcZ+d+hJ/JuLRj2sTcWQySMyX61z8wAHsN8g X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (ibm.leadmon.net [207.114.24.13]); Tue, 23 May 2006 14:55:43 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on ibm.leadmon.net X-Virus-Status: Clean Cc: 'Konstantin Belousov' , freebsd-stable@freebsd.org, 'Kris Kennaway' Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 18:55:45 -0000 Hello Rong-en, Thanks for the info on getting the debugger configured, and on the serial console. I will have to try and play with the serial console thing more, I just tried putting in the flags and the damn thing hung, I had to boot from CD and take the stuff back out. One thing you mention below that concerns me is that you have version 1.90 of the vfs_lookup.c file. I just did a less on /usr/src/sys/kern/vfs_lookup.c and I see the following: FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 03:57:46 kris Exp I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure I had the current stuff before rebuilding the kernel just now, and still I see the same thing. Is something fishy going on here, or did you by chance make a typo?? --- Howard Leadmon - howard@leadmon.net http://www.leadmon.net > -----Original Message----- > From: Rong-en Fan [mailto:grafan@gmail.com] > Sent: Tuesday, May 23, 2006 10:19 AM > To: Howard Leadmon > Cc: Konstantin Belousov; Kris Kennaway; freebsd-stable@freebsd.org > Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? > > On 5/23/06, Howard Leadmon wrote: > > > > > > > > > If there are any thing I can provide to help tracking > this down. > > > > > Please let me know. By the way, I tried with truss/kdump > > > to see what > > > > > happens when nfsd eats lot of CPUs, but in vain. They do > > > not return anything. > > > > > > > > > I tried your recipe on 7-CURRENT with locally exported fs, > > > remounted > > > > over nfs. I did not get the behaviour your described. > > > > > > As noted in my previous thread, I have another 6.1-RELEASE nfs > > > server, which does not have this problem. > > > > > > > Could you, please, provide the backtrace for the nfsd that eats > > > > the CPU (from the ddb). I think it would be helpful to > get several > > > > backtraces (i.e., bt , cont, bt ...) > > > to see where > > > > it running. > > > > > > I'm afraid that I can not do that. Last time I tried > breaking into > > > ddb (on 5.x), it hangs my serial console and the server is miles > > > away :-( . Perhaps we can ask Howard to do that? > > > > I am more than willing to do that, as this machine runs > here with me, > > so if needed I can easily get on a console, or perform a > reboot. Can > > one of you shed a little light on exactly what I need to > do, and how > > to do this? I ask as I have never used this ddb stuff, so not clue > > one on how to go about getting the information your looking > to find. > > Guess I have been lucky, and just never had an issue that > took things to this level. > > At least you have to add the following to your kernel: > > options KDB > options DDB > > Recompile it, reboot. You would better to setup a serial > console so you can easily copy thing from ddb output. To do > it, you have to put "device sio" in your kernel configuration > and some files > below: > > /boot.config > -Dh > > /boot/loader.conf > comconsole_speed=115200 > machdep.conspeed=115200 > > /etc/ttys > ttyd0 "/usr/libexec/getty std.115200" cons25 on secure > > On the other machine, /etc/remote: > com1:dv=/dev/cuad0:br#115200:pa=none: > > Then, use "tip com1" to attach the nfs server. The above > settings assume your serial console on nfs server is on COM1 > and on the client side is also COM1. If that's not the case, > please follow Handbook for howto setup a serial console other > than COM1. To break into ddb, either use ctrl+alt+esc or send > a BREAK (I think ^b will do) via serial line. After that, you > should see > > db> > > Then you first use "ps" to find out the nfsd pid (better to > remember the pid which eats lots of cpu before enter ddb). > After that, do what Konstantin suggests. I have never tried > "cont" in db. I guess that will return the execution back to > kernel and you need to break into ddb again to do another "bt ". > > By the way, could you verify that backing out vfs_lookup.c > rev 1.90 helps in your situation? If not, maybe we are seeing > different problems, and then I have to figure out how to make > my serial console work here. > > Thanks, > Rong-En Fan > From owner-freebsd-stable@FreeBSD.ORG Tue May 23 19:03:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8553416A7FE for ; Tue, 23 May 2006 19:03:03 +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 1528B43D48 for ; Tue, 23 May 2006 19:03:02 +0000 (GMT) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IZQ006OUFL18BD0@osl1smout1.broadpark.no> for freebsd-stable@freebsd.org; Tue, 23 May 2006 21:03:01 +0200 (CEST) Received: from kg-work.kg4.no ([80.202.172.162]) by osl1sminn1.broadpark.no (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with SMTP id <0IZQ009YEFL1WS81@osl1sminn1.broadpark.no> for freebsd-stable@freebsd.org; Tue, 23 May 2006 21:03:01 +0200 (CEST) Date: Tue, 23 May 2006 21:03:00 +0200 From: Torfinn Ingolfsen 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 In-reply-to: <43FAF33F.6080502@tirloni.org> To: freebsd-stable@freebsd.org Message-id: <20060523210300.40528fa8.torfinn.ingolfsen@broadpark.no> MIME-version: 1.0 X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.17; i386-portbld-freebsd5.5) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT References: <20060219235911.012b24b7.torfinn.ingolfsen@broadpark.no> <43FAF33F.6080502@tirloni.org> Subject: Re: Difference in slice numbering FreeBSD 4.x vs. 6.x? 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, 23 May 2006 19:03:04 -0000 It has been a long time, but today was a rainy day without plans, so now I'm following up on an old thread. On Tue, 21 Feb 2006 08:02:23 -0300 "Giovanni P. Tirloni" wrote: > I've moved hard disks around many times and this has never > happened. Can you send us `fdisk /dev/ad0` from 4.11 and 6.0 so we > can spot anything not normal ? I didn't have a live CD or fixit floppy at hand, so I just used the "fdisk" menu in systinstall (on the 6.1-RELEASE / i386 cd). It says that there are two slices: ad0s3 ad0s4 > Does it still boot in the machine after we've booted in the laptop ? Nope, it acts the same there - the boot manager says "F3" and "F4" aout slices to boot from. Unfortunately, the only slice it will boot is F3, which now is FreeBSD 4.11. Alas, the machine used for testing is a amd64 one, and it will not boot 4.11 completely - it panics with a fatal trap 9 after a ad0 READ timeout and ata0: resetting devices .. I'll guess that it is something I have done, even if I can't figure out what. For the record, I just wiped all slices on the hard drive, installed FreeBSD 6.1-RELEASE (i386) on it, put it back into the laptop and it boots with no problem. The PC card controller in the laptop is still not detected, but that's another story. -- Regards, Torfinn Ingolfsen, Norway From owner-freebsd-stable@FreeBSD.ORG Tue May 23 19:08:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4F4A16A8BA for ; Tue, 23 May 2006 19:08:56 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id B274843D49 for ; Tue, 23 May 2006 19:08:55 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nf-out-0910.google.com with SMTP id l37so693816nfc for ; Tue, 23 May 2006 12:08:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EDQsXmnDZILfw4yfcQthwl8eoNcgTXdI76WJP9M5vfD9ot2ZxUNUSerMELJ5cV9fqxXbxIOt08WqP7t3g1dOznvwGSzwVCdq6pP3iS1KzhekksfxnJItz66RwN1tcjYFwvCszk8/a+7QMD2CDil8y1qaWOfEnIS0TY4UFu17P2Y= Received: by 10.49.33.12 with SMTP id l12mr5012236nfj; Tue, 23 May 2006 12:08:54 -0700 (PDT) Received: by 10.48.30.7 with HTTP; Tue, 23 May 2006 12:08:54 -0700 (PDT) Message-ID: <6eb82e0605231208ydcd888ck578b485393f670d3@mail.gmail.com> Date: Tue, 23 May 2006 15:08:54 -0400 From: "Rong-en Fan" To: "Howard Leadmon" In-Reply-To: <000001c67e9a$7c6c3f10$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <6eb82e0605230718l337a58efmc85637afdec4fffb@mail.gmail.com> <000001c67e9a$7c6c3f10$071872cf@Leadmon.local> Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 23 May 2006 19:08:57 -0000 On 5/23/06, Howard Leadmon wrote: > > Hello Rong-en, > > Thanks for the info on getting the debugger configured, and on the seria= l > console. I will have to try and play with the serial console thing more= , I > just tried putting in the flags and the damn thing hung, I had to boot fr= om CD > and take the stuff back out. > > One thing you mention below that concerns me is that you have version 1.= 90 of > the vfs_lookup.c file. I just did a less on /usr/src/sys/kern/vfs_looku= p.c > and I see the following: > > FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 03:57:46 kris Ex= p > > > I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure I had the cur= rent > stuff before rebuilding the kernel just now, and still I see the same thi= ng. > Is something fishy going on here, or did you by chance make a typo?? Sorry for the confusion. rev 1.90 is the number for -HEAD. To back out this MFC'ed change for RELENG_6_1, please cvsup to RELENG_6_1 date=3D2006.04.30.03.57.00. Then you should see it is 1.80.2.6 2006/03/31 07:39:24 kris To verify the effect of this revision. Please run RELENG_6_1 with 2006.04.30.03.57.00 and 2006.04.30.04.00.00. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Tue May 23 19:46:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFF5216A5EB for ; Tue, 23 May 2006 19:46:48 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 55A2543D46 for ; Tue, 23 May 2006 19:46:48 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 36699 invoked from network); 23 May 2006 19:46:47 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=058YhTCArzUNRhT2002cPBjj+jx1QgTO2RPJW8UdqmNoSagDuB8IcbQyHI3vVVz0bu3uNz0g4cnGrXZI+SyiSSj+j3bDUymc8WxbRRYKX8ngpM/6H5Ui6KoClW5V7tGtImQSssTNyq1s8E8Wn++0K/sCiR8zzWVIGWvMOz1ieL8= ; Received: from unknown (HELO ?70.31.50.218?) (mikej@rogers.com@70.31.50.218 with plain) by smtp104.rog.mail.re2.yahoo.com with SMTP; 23 May 2006 19:46:46 -0000 Message-ID: <447366AD.30203@rogers.com> Date: Tue, 23 May 2006 15:46:53 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Rong-en Fan References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> In-Reply-To: <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: quota and snapshots in 6.1-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, 23 May 2006 19:46:56 -0000 Rong-en Fan wrote: > On 5/23/06, Dmitriy Kirhlarov wrote: >> Hi, list. >> >> Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock >> problems. What the current situation with this? I'm ready to test >> patches, if needed. >> >> WBR > > IIRC, there are some quota and snapshots changes merged in > 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want > to try that. Thats correct. I have been meaning to test these, but not had the time to do so yet. If you can, update to -STABLE and give it a test. From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:09:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C77F16AA71 for ; Tue, 23 May 2006 20:09:36 +0000 (UTC) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A79643D70 for ; Tue, 23 May 2006 20:09:34 +0000 (GMT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 41C0FB850; Tue, 23 May 2006 15:09:33 -0500 (CDT) X-Virus-Scanned: amavisd-new at wolves.k12.mo.us Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (mail.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3aUGl2blUZKn; Tue, 23 May 2006 15:09:32 -0500 (CDT) Received: from wolves.k12.mo.us (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 96CADB84B; Tue, 23 May 2006 15:09:32 -0500 (CDT) Received: from cdtech.int.wolves.k12.mo.us (cdtech.int.wolves.k12.mo.us [10.1.3.200]) by www.wolves.k12.mo.us (Horde MIME library) with HTTP; Tue, 23 May 2006 15:09:32 -0500 Message-ID: <20060523150932.om173ht11c8wck8o@www.wolves.k12.mo.us> Date: Tue, 23 May 2006 15:09:32 -0500 From: Chris Dillon To: Mike Jakubik References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> In-Reply-To: <447366AD.30203@rogers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-6.1 Cc: stable@freebsd.org, Rong-en Fan Subject: Re: quota and snapshots in 6.1-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, 23 May 2006 20:09:43 -0000 Quoting Mike Jakubik : >> IIRC, there are some quota and snapshots changes merged in >> 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want >> to try that. > > Thats correct. I have been meaning to test these, but not had the time > to do so yet. If you can, update to -STABLE and give it a test. I have been running the fixes without problems since this weekend, but I was only bitten by the previous bugs maybe once or twice a week, even though I used snapshots and quotas extensively. If my system manages to stay up at least two weeks it is most likely fixed. :-) From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:18:31 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D242916A9F9 for ; Tue, 23 May 2006 20:18:31 +0000 (UTC) (envelope-from mark@mkproductions.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id A139543D53 for ; Tue, 23 May 2006 20:18:28 +0000 (GMT) (envelope-from mark@mkproductions.org) Received: from pimout3-ext.prodigy.net (pimout3-int.prodigy.net [207.115.4.218]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k4NKIXg7023362 for ; Tue, 23 May 2006 16:18:33 -0400 X-ORBL: [68.94.148.44] Received: from [192.168.1.25] (adsl-68-94-148-44.dsl.spfdmo.swbell.net [68.94.148.44]) by pimout3-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k4NKIQpe109020; Tue, 23 May 2006 16:18:26 -0400 Message-ID: <44736E11.6060104@mkproductions.org> Date: Tue, 23 May 2006 15:18:25 -0500 From: Mark Kane User-Agent: Thunderbird 1.5.0.2 (X11/20060518) MIME-Version: 1.0 To: Mike Jakubik References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> In-Reply-To: <447366AD.30203@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Rong-en Fan Subject: Re: quota and snapshots in 6.1-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, 23 May 2006 20:18:41 -0000 Mike Jakubik wrote: > Rong-en Fan wrote: >> On 5/23/06, Dmitriy Kirhlarov wrote: >>> Hi, list. >>> >>> Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock >>> problems. What the current situation with this? I'm ready to test >>> patches, if needed. >>> >>> WBR >> >> IIRC, there are some quota and snapshots changes merged in >> 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want >> to try that. > > Thats correct. I have been meaning to test these, but not had the time > to do so yet. If you can, update to -STABLE and give it a test. I had a motherboard die in a server on Sunday. It is running FreeBSD 5.4-RELEASE and the only hardware they had to replace it with was an Athlon64 CPU and a motherboard with an ATI chipset. With that board and 5.4, it will only boot in Safe Mode, but then the hard drives are running at very slow speeds. It completely locked up earlier today and they had to do a hard reboot (with no errors on the screen or in /var/log/messages). My plan was to have them fully upgrade the server tonight to a new box (with the same Athlon64 and mobo with ATI chipset since that's all they have), and do a fresh install of 6.1-RELEASE because a very similar board with the same chipset was reported to work in 6.0. Every machine I have or work on runs FreeBSD, but this is the only one that needs quotas because it runs cPanel for customers. I am not sure all the details about the problems with quotas, so will running 6.1-RELEASE with quotas cause problems for sure? If so, any suggestions on what to do given my situation? Would 6.0 be any better? I'd like to have the latest version because doing updates properly remotely is difficult, but if it is not going to work then I may have to use 6.0 if that will work or figure something else out hardware wise. Thanks -Mark -- GnuPG Public Key: http://www.mkproductions.org/mk_pubkey.asc Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:31:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A9716A915 for ; Tue, 23 May 2006 20:31:31 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A0FD43D5C for ; Tue, 23 May 2006 20:31:21 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 7F50298CFB for ; Tue, 23 May 2006 15:31:20 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftVNazmtceNM for ; Tue, 23 May 2006 15:31:19 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id C388198CEE for ; Tue, 23 May 2006 15:31:19 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 23 May 2006 15:31:17 -0500 User-Agent: KMail/1.9.1 X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$))vLVz4ACChrEcb}CO^tYmMG\ ts.m?[7[6OwE*dAJ*9f+mX.7R32qeN^DJ\(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231531.18092.kirk@strauser.com> Subject: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 20:31:47 -0000 I just upgraded from 6-STABLE as of 2006-02-18 to 6-STABLE as of 2006-05-21, and was surprised to find that PostgreSQL wouldn't start because it couldn't allocate enough shared memory. Thing is, I didn't make a single hardware change during the reboot and didn't upgrade any ports on the machine. My emergency fix was to edit postgresql.conf to change shared_buffers from 8192 to 2048. Unfortunately, that seems to be hurting performance - I'm getting annoying deadlocks at 4AM whenever multiple daemons start their overnight batch runs. Has anyone else seen this behavior when upgrading from 6.0 to 6.1? Any ideas for a fix? I apologize for not having a logfiles, but I was pretty much in a panic to get it back up and running ASAP and didn't think about it until it was too late. -- Kirk Strauser From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:35:30 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A387216ACC4 for ; Tue, 23 May 2006 20:35:30 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82BDF43D66 for ; Tue, 23 May 2006 20:35:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5D95A1A3C1D; Tue, 23 May 2006 13:35:22 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BCA0451742; Tue, 23 May 2006 16:35:21 -0400 (EDT) Date: Tue, 23 May 2006 16:35:21 -0400 From: Kris Kennaway To: Mark Kane Message-ID: <20060523203521.GA48061@xor.obsecurity.org> References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> <44736E11.6060104@mkproductions.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <44736E11.6060104@mkproductions.org> User-Agent: Mutt/1.4.2.1i Cc: Mike Jakubik , stable@freebsd.org, Rong-en Fan Subject: Re: quota and snapshots in 6.1-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, 23 May 2006 20:35:38 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 23, 2006 at 03:18:25PM -0500, Mark Kane wrote: > Mike Jakubik wrote: > >Rong-en Fan wrote: > >>On 5/23/06, Dmitriy Kirhlarov wrote: > >>>Hi, list. > >>> > >>>Some time ago quota and, AFAIR, snapshots in 6.1-RELEASE has deadlock > >>>problems. What the current situation with this? I'm ready to test > >>>patches, if needed. > >>> > >>>WBR > >> > >>IIRC, there are some quota and snapshots changes merged in > >>6.1-STABLE after 6.1-RELEASE is releases. So I think you may want > >>to try that. > > > >Thats correct. I have been meaning to test these, but not had the time= =20 > >to do so yet. If you can, update to -STABLE and give it a test. >=20 > I had a motherboard die in a server on Sunday. It is running FreeBSD=20 > 5.4-RELEASE and the only hardware they had to replace it with was an=20 > Athlon64 CPU and a motherboard with an ATI chipset. With that board and= =20 > 5.4, it will only boot in Safe Mode, but then the hard drives are=20 > running at very slow speeds. It completely locked up earlier today and=20 > they had to do a hard reboot (with no errors on the screen or in=20 > /var/log/messages). My plan was to have them fully upgrade the server=20 > tonight to a new box (with the same Athlon64 and mobo with ATI chipset=20 > since that's all they have), and do a fresh install of 6.1-RELEASE=20 > because a very similar board with the same chipset was reported to work= =20 > in 6.0. >=20 > Every machine I have or work on runs FreeBSD, but this is the only one=20 > that needs quotas because it runs cPanel for customers. I am not sure=20 > all the details about the problems with quotas, so will running=20 > 6.1-RELEASE with quotas cause problems for sure? If so, any suggestions= =20 > on what to do given my situation? Would 6.0 be any better? I'd like to=20 > have the latest version because doing updates properly remotely is=20 > difficult, but if it is not going to work then I may have to use 6.0 if= =20 > that will work or figure something else out hardware wise. If you use snapshots with your quotas, update to 6.1-STABLE. If you don't use snapshots, 6.1-R should be fine. This was discussed in excruciating depth a few weeks back, so please read the archives for more. Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc3IJWry0BWjoQKURAriOAJ93Ir9r4Aj1Psqs+Nu9knYwzEBXTQCg9Mo9 rApEGpgHoAI9PBxCsri/0Ng= =6prq -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:37:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47AE116A8E8 for ; Tue, 23 May 2006 20:37:29 +0000 (UTC) (envelope-from mbp@cs.hmc.edu) Received: from happy-hardcore.st.hmc.edu (happy-hardcore.ST.HMC.Edu [134.173.56.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE68F43D76 for ; Tue, 23 May 2006 20:37:28 +0000 (GMT) (envelope-from mbp@cs.hmc.edu) Received: from [134.173.200.13] (WL-13.CINE.HMC.Edu [134.173.200.13]) by happy-hardcore.st.hmc.edu (Postfix) with ESMTP id 7AEF2B95A for ; Tue, 23 May 2006 13:37:28 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <200605231531.18092.kirk@strauser.com> References: <200605231531.18092.kirk@strauser.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit From: Marshall Pierce Date: Tue, 23 May 2006 13:37:26 -0700 X-Mailer: Apple Mail (2.750) Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 20:37:35 -0000 On May 23, 2006, at 1:31 PM, Kirk Strauser wrote: > I just upgraded from 6-STABLE as of 2006-02-18 to 6-STABLE as of > 2006-05-21, > and was surprised to find that PostgreSQL wouldn't start because it > couldn't allocate enough shared memory. Thing is, I didn't make a > single > hardware change during the reboot and didn't upgrade any ports on the > machine. > > My emergency fix was to edit postgresql.conf to change > shared_buffers from > 8192 to 2048. Unfortunately, that seems to be hurting performance > - I'm > getting annoying deadlocks at 4AM whenever multiple daemons start > their > overnight batch runs. > > Has anyone else seen this behavior when upgrading from 6.0 to 6.1? > Any > ideas for a fix? > > I apologize for not having a logfiles, but I was pretty much in a > panic to > get it back up and running ASAP and didn't think about it until it > was too > late. > -- > Kirk Strauser You need to adjust the shared memory segments allowed by the kernel; see /usr/ports/databases/postgresql-server/pkg-message- server for what to add to your kernel config. Most likely, you forgot to move over your kernel customizations to your new kernel...? -Marshall From owner-freebsd-stable@FreeBSD.ORG Tue May 23 20:58:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 444C716AF36 for ; Tue, 23 May 2006 20:58:50 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7295A43D45 for ; Tue, 23 May 2006 20:58:30 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 2215D98D34 for ; Tue, 23 May 2006 15:58:30 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UAlW4GtRBWHH for ; Tue, 23 May 2006 15:58:28 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id C4AE198BE2 for ; Tue, 23 May 2006 15:58:28 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 23 May 2006 15:58:26 -0500 User-Agent: KMail/1.9.1 References: <200605231531.18092.kirk@strauser.com> In-Reply-To: X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?utf-8?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dAJ*9f+m?= =?utf-8?q?X=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231558.27248.kirk@strauser.com> Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 20:58:54 -0000 On Tuesday 23 May 2006 15:37, Marshall Pierce wrote: > You need to adjust the shared memory segments allowed by the kernel; see > /usr/ports/databases/postgresql-server/pkg-message-server > for what to add to your kernel config. Most likely, you forgot to move > over your kernel customizations to your new kernel...? Nope, I took care of that: /etc/sysctl.conf: kern.ipc.semmap=256 kern.ipc.shmmax=268435456 /boot/loader.conf kern.ipc.semmni="256" kern.ipc.semmns="512" kern.ipc.semmnu="256" Furthermore, neither of those files (or even my kernel config file) changed between the previous reboot and the one that installed 6.1. At any rate, the kern.ipc.shmmax is much, much greater than the 64MB that I'd been using before for shared_buffers (8192 buffers * 8 KB/buffer). -- Kirk Strauser From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:05:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E06BC16B018 for ; Tue, 23 May 2006 21:05:12 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EBDB43D5E for ; Tue, 23 May 2006 21:05:02 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wx-out-0102.google.com with SMTP id i30so865998wxd for ; Tue, 23 May 2006 14:05:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=n2y6e4IPyxBYpvyNRB/dx8XQQhjt+UwP9LxgzgVSAFvzjVIVhqNTApL0fC7b4fj04Qn/kLZrQ+PKMhai0ooXsH9t5JkpHWCenJnh4OlAmfc6aTmCJeA88OZGbbpAC00Bp2pRBNiJHXkepmh7l0jJfsru4F7dJdx75fpxqiGiDUE= Received: by 10.70.60.6 with SMTP id i6mr6855167wxa; Tue, 23 May 2006 14:05:01 -0700 (PDT) Received: by 10.70.22.2 with HTTP; Tue, 23 May 2006 14:05:01 -0700 (PDT) Message-ID: Date: Tue, 23 May 2006 23:05:01 +0200 From: "Claus Guttesen" To: "Kirk Strauser" In-Reply-To: <200605231558.27248.kirk@strauser.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200605231531.18092.kirk@strauser.com> <200605231558.27248.kirk@strauser.com> Cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:05:18 -0000 > > You need to adjust the shared memory segments allowed by the kernel; se= e > > /usr/ports/databases/postgresql-server/pkg-message-server > > for what to add to your kernel config. Most likely, you forgot to move > > over your kernel customizations to your new kernel...? > > Nope, I took care of that: > > /etc/sysctl.conf: > > kern.ipc.semmap=3D256 > kern.ipc.shmmax=3D268435456 > > /boot/loader.conf > > kern.ipc.semmni=3D"256" > kern.ipc.semmns=3D"512" > kern.ipc.semmnu=3D"256" > > Furthermore, neither of those files (or even my kernel config file) chang= ed > between the previous reboot and the one that installed 6.1. At any rate, > the kern.ipc.shmmax is much, much greater than the 64MB that I'd been usi= ng > before for shared_buffers (8192 buffers * 8 KB/buffer). He probably meant the following kernel-settings: options SHMMAXPGS=3D393216 options SEMMNI=3D240 options SEMMNS=3D1440 options SEMUME=3D240 options SEMMNU=3D720 Those are for my quad-opteron server with 8 GB RAM. Adjust accordingly. Did you compile a custom-build-kernel or GENERIC? regards Claus From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:14:03 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D08AE16AFEB for ; Tue, 23 May 2006 21:14:03 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87ED843D5A for ; Tue, 23 May 2006 21:14:00 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k4NLDZTC044469; Tue, 23 May 2006 17:13:35 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 23 May 2006 17:13:20 -0400 User-Agent: KMail/1.6.2 References: <200605231531.18092.kirk@strauser.com> <200605231558.27248.kirk@strauser.com> In-Reply-To: <200605231558.27248.kirk@strauser.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200605231713.22363.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1478/Mon May 22 17:01:38 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:14:10 -0000 On Tuesday 23 May 2006 04:58 pm, Kirk Strauser wrote: > On Tuesday 23 May 2006 15:37, Marshall Pierce wrote: > > You need to adjust the shared memory segments allowed by the > > kernel; see > > /usr/ports/databases/postgresql-server/pkg-message- > >server for what to add to your kernel config. Most likely, you > > forgot to move over your kernel customizations to your new > > kernel...? > > Nope, I took care of that: > > /etc/sysctl.conf: > > kern.ipc.semmap=256 > kern.ipc.shmmax=268435456 > > /boot/loader.conf > > kern.ipc.semmni="256" > kern.ipc.semmns="512" > kern.ipc.semmnu="256" > > Furthermore, neither of those files (or even my kernel config file) > changed between the previous reboot and the one that installed 6.1. > At any rate, the kern.ipc.shmmax is much, much greater than the > 64MB that I'd been using before for shared_buffers (8192 buffers * > 8 KB/buffer). kern.ipc.shmmaxpgs? Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:17:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC0C216B18A for ; Tue, 23 May 2006 21:17:22 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C62243D45 for ; Tue, 23 May 2006 21:17:15 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id A0CE898D3D for ; Tue, 23 May 2006 16:17:14 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKuEpxI6AqbQ for ; Tue, 23 May 2006 16:17:14 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 0912698D1D for ; Tue, 23 May 2006 16:17:14 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 23 May 2006 16:17:12 -0500 User-Agent: KMail/1.9.1 References: <200605231531.18092.kirk@strauser.com> <200605231558.27248.kirk@strauser.com> In-Reply-To: X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?utf-8?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dAJ*9f+m?= =?utf-8?q?X=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231617.12526.kirk@strauser.com> Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:17:29 -0000 On Tuesday 23 May 2006 16:05, Claus Guttesen wrote: > He probably meant the following kernel-settings: > > options SHMMAXPGS=393216 > options SEMMNI=240 > options SEMMNS=1440 > options SEMUME=240 > options SEMMNU=720 > > Those are for my quad-opteron server with 8 GB RAM. Adjust > accordingly. Did you compile a custom-build-kernel or GENERIC? I hadn't compiled any of those into my custom kernel, as per some now long-forgotten web page that said I should use the sysctls to reach the same effect. What I'd *really* like to find is an explanation of how to set those numbers. I'm using a single Xeon with 3GB of RAM and have no idea how high to set those, or whether a particular value is too high. Then again, once I figure it out I guess I should have a fair amount of job security. :-) -- Kirk Strauser From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:20:17 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8EF716A962 for ; Tue, 23 May 2006 21:20:17 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08EB743D6D for ; Tue, 23 May 2006 21:20:16 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k4NLK8X3044715; Tue, 23 May 2006 17:20:08 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 23 May 2006 17:19:52 -0400 User-Agent: KMail/1.6.2 References: <200605231531.18092.kirk@strauser.com> <200605231558.27248.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> In-Reply-To: <200605231713.22363.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200605231719.56164.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1478/Mon May 22 17:01:38 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:20:20 -0000 On Tuesday 23 May 2006 05:13 pm, Jung-uk Kim wrote: > On Tuesday 23 May 2006 04:58 pm, Kirk Strauser wrote: > > On Tuesday 23 May 2006 15:37, Marshall Pierce wrote: > > > You need to adjust the shared memory segments allowed by the > > > kernel; see > > > /usr/ports/databases/postgresql-server/pkg-messag > > >e- server for what to add to your kernel config. Most likely, > > > you forgot to move over your kernel customizations to your new > > > kernel...? > > > > Nope, I took care of that: > > > > /etc/sysctl.conf: > > > > kern.ipc.semmap=256 > > kern.ipc.shmmax=268435456 > > > > /boot/loader.conf > > > > kern.ipc.semmni="256" > > kern.ipc.semmns="512" > > kern.ipc.semmnu="256" > > > > Furthermore, neither of those files (or even my kernel config > > file) changed between the previous reboot and the one that > > installed 6.1. At any rate, the kern.ipc.shmmax is much, much > > greater than the 64MB that I'd been using before for > > shared_buffers (8192 buffers * 8 KB/buffer). > > kern.ipc.shmmaxpgs? I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. :-( Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:30:50 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8FE816B3BE; Tue, 23 May 2006 21:30:50 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 163A043D7F; Tue, 23 May 2006 21:30:47 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k4NLUk2s045079; Tue, 23 May 2006 17:30:46 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Tue, 23 May 2006 17:30:32 -0400 User-Agent: KMail/1.6.2 References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> In-Reply-To: <200605231719.56164.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200605231730.34100.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1478/Mon May 22 17:01:38 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: rwatson@FreeBSD.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:30:53 -0000 On Tuesday 23 May 2006 05:19 pm, Jung-uk Kim wrote: > On Tuesday 23 May 2006 05:13 pm, Jung-uk Kim wrote: > > On Tuesday 23 May 2006 04:58 pm, Kirk Strauser wrote: > > > On Tuesday 23 May 2006 15:37, Marshall Pierce wrote: > > > > You need to adjust the shared memory segments allowed by the > > > > kernel; see > > > > /usr/ports/databases/postgresql-server/pkg-mess > > > >ag e- server for what to add to your kernel config. Most > > > > likely, you forgot to move over your kernel customizations to > > > > your new kernel...? > > > > > > Nope, I took care of that: > > > > > > /etc/sysctl.conf: > > > > > > kern.ipc.semmap=256 > > > kern.ipc.shmmax=268435456 > > > > > > /boot/loader.conf > > > > > > kern.ipc.semmni="256" > > > kern.ipc.semmns="512" > > > kern.ipc.semmnu="256" > > > > > > Furthermore, neither of those files (or even my kernel config > > > file) changed between the previous reboot and the one that > > > installed 6.1. At any rate, the kern.ipc.shmmax is much, much > > > greater than the 64MB that I'd been using before for > > > shared_buffers (8192 buffers * 8 KB/buffer). > > > > kern.ipc.shmmaxpgs? > > I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. Okay, I don't know what I am talking about here. It is still kern.ipc.shmmaxpgs to set it. In fact, I found a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=75542 However, it seems rwatson closed wrong one at the time. :-( Sorry for the noise, Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Tue May 23 21:36:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B2B316B138 for ; Tue, 23 May 2006 21:36:39 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64CD743D66 for ; Tue, 23 May 2006 21:36:30 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id BA14F98D64 for ; Tue, 23 May 2006 16:36:29 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ei99BasPX0sN for ; Tue, 23 May 2006 16:36:29 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 04A0298D41 for ; Tue, 23 May 2006 16:36:28 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 23 May 2006 16:36:27 -0500 User-Agent: KMail/1.9.1 References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> In-Reply-To: <200605231719.56164.jkim@FreeBSD.org> X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?utf-8?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dAJ*9f+m?= =?utf-8?q?X=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231636.27463.kirk@strauser.com> Subject: Re: PostgreSQL uses more memory on 6.1? 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, 23 May 2006 21:36:42 -0000 On Tuesday 23 May 2006 16:19, Jung-uk Kim wrote: > I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. :-( That did it! Bumping kern.ipc.shmall to 65536 got me back up and running with enough shared_memory to get my jobs done. -- Kirk Strauser From owner-freebsd-stable@FreeBSD.ORG Wed May 24 00:04:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02EF516A466 for ; Wed, 24 May 2006 00:04:00 +0000 (UTC) (envelope-from hackmiester@hackmiester.com) Received: from smtpout06-04.prod.mesa1.secureserver.net (smtpout06-01.prod.mesa1.secureserver.net [64.202.165.224]) by mx1.FreeBSD.org (Postfix) with SMTP id 89A0A43D49 for ; Wed, 24 May 2006 00:03:59 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 15258 invoked from network); 24 May 2006 00:03:58 -0000 Received: from unknown (70.146.241.52) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 24 May 2006 00:03:55 -0000 In-Reply-To: <79722fad0605230453vc0436d5o352f0f10c995656d@mail.gmail.com> References: <79722fad0605111452r2e5da097x21aa86a63e4dfe52@mail.gmail.com> <79722fad0605230453vc0436d5o352f0f10c995656d@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Hunter Fuller Date: Tue, 23 May 2006 19:04:18 +0000 To: Vlad GALU X-Mailer: Apple Mail (2.746.2) Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-stable crash 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, 24 May 2006 00:04:01 -0000 Am I the only one who sees the oxymoronity in "6.1-stable crash"? On 23 May 2006, at 11:53 AM, Vlad GALU wrote: > On 5/12/06, Vlad GALU wrote: > [...] > Just for the record, this has just happened again. > > -- > If it's there, and you can see it, it's real. > If it's not there, and you can see it, it's virtual. > If it's there, and you can't see it, it's transparent. > If it's not there, and you can't see it, you erased it. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Wed May 24 00:51:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D2AC16A756 for ; Wed, 24 May 2006 00:51:56 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32AE843D79 for ; Wed, 24 May 2006 00:51:44 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-2.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IZQ00CU0VPWUN@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Wed, 24 May 2006 12:51:32 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-172.dsl.clear.net.nz [218.101.29.172]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 3B23113216A6; Wed, 24 May 2006 12:51:32 +1200 (NZST) Date: Wed, 24 May 2006 12:51:03 +1200 From: Mark Kirkwood In-reply-to: <200605231636.27463.kirk@strauser.com> To: Kirk Strauser Message-id: <4473ADF7.4080101@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5 (X11/20060417) References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> <200605231636.27463.kirk@strauser.com> Cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 00:51:57 -0000 Kirk Strauser wrote: > On Tuesday 23 May 2006 16:19, Jung-uk Kim wrote: > >> I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. :-( > > That did it! Bumping kern.ipc.shmall to 65536 got me back up and running > with enough shared_memory to get my jobs done. Having not so long ago been caught by this myself, I think the relationship between shmmax and shmall is worth clarifying: $ sysctl -d kern.ipc.shmall kern.ipc.shmall: Maximum number of pages available for shared memory $ sysctl -d kern.ipc.shmmax kern.ipc.shmmax: Maximum shared memory segment size So to run 1 Postgres installation with 128Mb of shared memory: kern.ipc.shmall=32768 kern.ipc.shmmax=134217728 However suppose you want to run 2 Postgres installations, each using 128Mb of shared memory: kern.ipc.shmall=65536 kern.ipc.shmmax=134217728 i.e. maximum system wide shared memory is 65536*4096 = 256Mb, but the maximum size any single segment can be is 128Mb. Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:14:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED6916A42C for ; Wed, 24 May 2006 01:14:01 +0000 (UTC) (envelope-from dmehler26@woh.rr.com) Received: from ms-smtp-02.ohiordc.rr.com (ms-smtp-02.ohiordc.rr.com [65.24.5.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6601843D45 for ; Wed, 24 May 2006 01:14:01 +0000 (GMT) (envelope-from dmehler26@woh.rr.com) Received: from satellite (cpe-65-31-41-159.woh.res.rr.com [65.31.41.159]) by ms-smtp-02.ohiordc.rr.com (8.13.6/8.13.6) with SMTP id k4O1Dxst007208 for ; Tue, 23 May 2006 21:13:59 -0400 (EDT) Message-ID: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> From: "Dave" To: Date: Tue, 23 May 2006 21:03:06 -0400 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.2869 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: internal compiler error: segmentation fault: 11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dave List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 01:14:02 -0000 Hello, I'm trying to compile 6.0-stable on a release box, prior to upgrade. I've tried several times and all end with an internal compiler error: segmentation fault: 11. And then i'm told to submit a bug report. My problem is when this occurs it's not always at the same spot or the same file. One time it even core dumped, though only once. At this point i would appreciate any suggestions, i'm hoping this is not the indicator of a problem. Thanks. Dave. From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:19:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD53816A4DE for ; Wed, 24 May 2006 01:19:52 +0000 (UTC) (envelope-from scottro@nyc.rr.com) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A09E43D4C for ; Wed, 24 May 2006 01:19:51 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-03.rdc-nyc.rr.com (8.13.6/8.13.6) with ESMTP id k4O1FCbO014308; Tue, 23 May 2006 21:15:13 -0400 (EDT) Received: by mail.scottro.net (Postfix, from userid 1001) id DC5655C6A; Tue, 23 May 2006 21:19:49 -0400 (EDT) Date: Tue, 23 May 2006 21:19:49 -0400 From: Scott Robbins To: Dave Message-ID: <20060524011949.GA15916@mail.scottro.net> Mail-Followup-To: Dave , freebsd-stable@freebsd.org References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 01:19:55 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: > Hello, > I'm trying to compile 6.0-stable on a release box, prior to upgrade. I've > tried several times and all end with an internal compiler error: segmentation > fault: 11. And then i'm told to submit a bug report. My problem is when this > occurs it's not always at the same spot or the same file. One time it even core > dumped, though only once. Unfortunately, it's often indicative of hardware failure. See http://www.freebsd.org./doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 It's the classic hardware indicator, dying at random points in the build. Good luck. Hardware troubleshooting is often a major pain in the neck. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Willy: What are you gonna' do with him, anyway? Spike: I'm thinkin' maybe dinner and a movie. I don't want to rush into anything. I've been hurt, you know. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc7S1+lTVdes0Z9YRAsVSAJ9hwEZkyyWBIQMbdwzLvKXQnYN83wCgsHmm xkJK0VRRz7da9WHu0kYgDKw= =zCqB -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:22:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 876D916A7C8 for ; Wed, 24 May 2006 01:22:31 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from drone4.qsi.net.nz (drone4-svc-skyt.qsi.net.nz [202.89.128.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F02D43D7D for ; Wed, 24 May 2006 01:22:22 +0000 (GMT) (envelope-from jonc@chen.org.nz) Received: (qmail 21531 invoked by uid 0); 24 May 2006 01:22:21 -0000 Received: from unknown (HELO chen.org.nz) ([202.89.146.5]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 24 May 2006 01:22:20 -0000 Received: by chen.org.nz (Postfix, from userid 1000) id ED9F156440; Wed, 24 May 2006 13:22:19 +1200 (NZST) Date: Wed, 24 May 2006 13:22:19 +1200 From: Jonathan Chen To: Dave Message-ID: <20060524012219.GB15327@osiris.chen.org.nz> References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 01:22:49 -0000 On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: > Hello, > I'm trying to compile 6.0-stable on a release box, prior to upgrade. > I've tried several times and all end with an internal compiler error: > segmentation fault: 11. And then i'm told to submit a bug report. My > problem is when this occurs it's not always at the same spot or the same > file. One time it even core dumped, though only once. This is a prime-indicator of dodgy memory. -- Jonathan Chen ---------------------------------------------------------------------- "A person should be able to do a small bit of everything, specialisation is for insects" From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:36:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BE0D16A4D5 for ; Wed, 24 May 2006 01:36:06 +0000 (UTC) (envelope-from gregh@alternativesecurity.com) Received: from selectsst.com (mail.selectsst.com [216.66.248.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE27243D45 for ; Wed, 24 May 2006 01:36:04 +0000 (GMT) (envelope-from gregh@alternativesecurity.com) Received: from [192.168.0.5] [192.168.0.5] by selectsst.com with ESMTP (SMTPD-8.21) id A81A0340; Tue, 23 May 2006 18:34:18 -0700 From: Greg Organization: Alternative Security To: freebsd-stable@freebsd.org Date: Tue, 23 May 2006 18:36:02 -0700 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_Ci7cEq/3WgjOmhP" Message-Id: <200605231836.02815.gregh@alternativesecurity.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: amd64/97019: Cannot load the kernel after installation on Supermicro H8DAR-T 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, 24 May 2006 01:36:07 -0000 --Boundary-00=_Ci7cEq/3WgjOmhP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline To whom it may concern: I was informed to make a post regarding problem report 97019 (http://www.freebsd.org/cgi/query-pr.cgi?pr=97019.) According to my experiences, both i386 and am64 installations produce the same result. Although the workaround works perfectly, I suppose this post needs to get done. Before I start on the details, I need to clarify the problem report a tad. Before: Fix 1) Load fixit image with installation cd-rom and switch to holographic shell (CTRL-ALT-F4) 2) mount /dev/ad4s1a to any directory of your choice (e.g. mount /dev/ad4s1a /mnt.) 2) copy /dist/kernels/install.sh to the above partition just mounted. 3) edit the install.sh and change the line that says /$[some variable]-/boot to the newely mounted parition /boot (e.g. /mnt/boot) 4) change to the /dist/kernels directory and run the install.sh from your mounted drive with kernel kernel arguments (e.g. cd /dist/kernels && /mnt/install.sh kernel kernel) After corrections made: Fix 1) Load fixit image with installation cd-rom and switch to holographic shell (CTRL-ALT-F4) 2) mount /dev/ad4s1a to any directory of your choice (e.g. mount /dev/ad4s1a /mnt.) 3) env DESTDIR=/mnt /dist/6.1-RELEASE/kernels/install.sh GENERIC 4) mv /mnt/boot/GENERIC /mnt/boot/kernel 5) umount /mnt 6) reboot Some details: Motherboard is Supermicro. The model is H8DAR-T (taken directly from motherboard) It has the Marvel SATA Controller with a 250 Gigabyte Western Digital Hard Drive. Attached are the output files for the 'pciconf -l -v' and 'dmesg' commands. I apologize for any errors (on my part) or if I have missed anything. Just let me know. -=-Thanks in Advance -=-Greg --Boundary-00=_Ci7cEq/3WgjOmhP Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.out" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; name="dmesg.out" Copyright (c) 1992-2006 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 6.1-RELEASE #0: Sun May 7 04:04:14 UTC 2006 root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 246 (2004.55-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 1073676288 (1023 MB) avail memory = 1024700416 (977 MB) ACPI APIC Table: ioapic1: Changing APIC ID to 6 ioapic1: WARNING: intbase 40 != expected base 24 ioapic2: Changing APIC ID to 7 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 40-46 on motherboard ioapic2 irqs 47-53 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci3: on pcib1 atapci0: port 0xb800-0xb8ff mem 0xfea00000-0xfeafffff irq 42 at device 3.0 on pci3 ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 ata5: on atapci0 pci0: at device 1.1 (no driver attached) pcib2: at device 2.0 on pci0 pci2: on pcib2 bge0: mem 0xfe8f0000-0xfe8fffff irq 49 at device 3.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:30:48:57:03:40 bge1: mem 0xfe8e0000-0xfe8effff irq 50 at device 3.1 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:30:48:57:03:41 pci0: at device 2.1 (no driver attached) pcib3: at device 6.0 on pci0 pci1: on pcib3 ohci0: mem 0xfe7fe000-0xfe7fefff irq 19 at device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfe7fd000-0xfe7fdfff irq 19 at device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: at device 4.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0 ata0: on atapci1 ata1: on atapci1 pci0: at device 7.2 (no driver attached) pci0: at device 7.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: 2 Mouse> 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] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcc7ff,0xcc800-0xcdfff,0xce000-0xcf7ff 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 Timecounter "TSC" frequency 2004554345 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff806205d0, 0) error 6 acd0: DVDROM at ata1-slave UDMA33 ad4: 238475MB at ata2-master SATA150 Trying to mount root from ufs:/dev/ad4s1a --Boundary-00=_Ci7cEq/3WgjOmhP-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:51:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0972916A474 for ; Wed, 24 May 2006 01:51:46 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20B6243D48 for ; Wed, 24 May 2006 01:51:45 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IZQ00E3LYI7TD@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Wed, 24 May 2006 13:51:44 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-172.dsl.clear.net.nz [218.101.29.172]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 726B612ECBF1; Wed, 24 May 2006 13:51:43 +1200 (NZST) Date: Wed, 24 May 2006 13:51:19 +1200 From: Mark Kirkwood In-reply-to: <20060524012219.GB15327@osiris.chen.org.nz> To: Dave Message-id: <4473BC17.5030500@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5 (X11/20060417) References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> <20060524012219.GB15327@osiris.chen.org.nz> Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 01:51:47 -0000 Jonathan Chen wrote: > On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: >> Hello, >> I'm trying to compile 6.0-stable on a release box, prior to upgrade. >> I've tried several times and all end with an internal compiler error: >> segmentation fault: 11. And then i'm told to submit a bug report. My >> problem is when this occurs it's not always at the same spot or the same >> file. One time it even core dumped, though only once. > > This is a prime-indicator of dodgy memory. Yeah - but it can easily be power supply or motherboard age. I suffered the latter late last year with a Tyan Thunder LE, I'm using the same power supply and memory in a Supermicro P3TDER and it is rock solid. Best wishes Mark From owner-freebsd-stable@FreeBSD.ORG Wed May 24 01:57:07 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54C2316A63E for ; Wed, 24 May 2006 01:57:07 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7AA943D72 for ; Wed, 24 May 2006 01:57:05 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 5843 invoked from network); 24 May 2006 11:57:04 +1000 Received: from andromeda.lef.com.au (HELO localhost) (210.8.93.2) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 May 2006 11:57:04 +1000 Date: Wed, 24 May 2006 11:56:59 +1000 From: Norberto Meijome To: stable@freebsd.org Message-ID: <20060524115659.7895006a@localhost> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Increase in panics under 6.1 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, 24 May 2006 01:57:07 -0000 hi all, I've seen an increase in panics since upgrading to 6.1 (I'm tracking RELENG_6). 6.1-Release seemed ok, but since updating kernel/world to more recent updates, I've been having lockups on resume. I'm using a Thinkpad z60M with ACPI enabled. Info on the machine can be found here: http://www.meijome.net/files/freebsd/ayiin_20060524/ The new panic i'm getting is: --- Dump header from device /dev/ad0s1g Architecture: i386 Architecture Version: 2 Dump Length: 1072168960B (1022 MB) Blocksize: 512 Dumptime: Fri May 19 21:49:56 2006 Hostname: ayiin.xxxxx Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.1-STABLE #3: Tue May 16 23:35:52 EST 2006 root@ayiin.xxxxxxx:/usr/obj/usr/src/sys/AYIIN Panic String: sleeping thread Dump Parity: 2510391376 Bounds: 0 Dump Status: good --- I have also have hard locks using DRI with Radeon - on 6.0 it used to just disable itself. no kernel dump in this case Locks due to attempting to use iwi after a resume are as bad as during 6.0 How can I help to diagnose / test these issues? ( If there is a solution, i wouldn't mind having it :-) ) thanks!! Beto From owner-freebsd-stable@FreeBSD.ORG Wed May 24 02:00:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F13ED16AC64 for ; Wed, 24 May 2006 02:00:38 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B203743D45 for ; Wed, 24 May 2006 02:00:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 97F391A4E81; Tue, 23 May 2006 19:00:38 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EC4C2515B2; Tue, 23 May 2006 22:00:37 -0400 (EDT) Date: Tue, 23 May 2006 22:00:37 -0400 From: Kris Kennaway To: Dave Message-ID: <20060524020037.GA54710@xor.obsecurity.org> References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline In-Reply-To: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 02:00:39 -0000 --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: > Hello, > I'm trying to compile 6.0-stable on a release box, prior to upgrade.= =20 > I've tried several times and all end with an internal compiler error:=20 > segmentation fault: 11. And then i'm told to submit a bug report. My=20 > problem is when this occurs it's not always at the same spot or the same= =20 > file. One time it even core dumped, though only once. > At this point i would appreciate any suggestions, i'm hoping this is n= ot=20 > the indicator of a problem. It's almost certainly hardware failure. Google for more information. Kris --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc75FWry0BWjoQKURAgdUAKC/1aJYFy86mubzpdCArir8p7QHJwCg4cAq 9JhdcjniYHIjTHEyb7+zTOM= =z9jw -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 02:01:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9288116A60F for ; Wed, 24 May 2006 02:01:17 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0657243D53 for ; Wed, 24 May 2006 02:01:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E125B1A4E81; Tue, 23 May 2006 19:01:16 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3E4935155B; Tue, 23 May 2006 22:01:16 -0400 (EDT) Date: Tue, 23 May 2006 22:01:16 -0400 From: Kris Kennaway To: Norberto Meijome Message-ID: <20060524020116.GB54710@xor.obsecurity.org> References: <20060524115659.7895006a@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vGgW1X5XWziG23Ko" Content-Disposition: inline In-Reply-To: <20060524115659.7895006a@localhost> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org Subject: Re: Increase in panics under 6.1 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, 24 May 2006 02:01:17 -0000 --vGgW1X5XWziG23Ko Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2006 at 11:56:59AM +1000, Norberto Meijome wrote: > hi all, > I've seen an increase in panics since upgrading to 6.1 (I'm tracking RELE= NG_6). > 6.1-Release seemed ok, but since updating kernel/world to more recent upd= ates, > I've been having lockups on resume. >=20 > I'm using a Thinkpad z60M with ACPI enabled. Info on the machine can be f= ound > here: >=20 > http://www.meijome.net/files/freebsd/ayiin_20060524/ >=20 > The new panic i'm getting is: >=20 > --- > Dump header from device /dev/ad0s1g > Architecture: i386 > Architecture Version: 2 > Dump Length: 1072168960B (1022 MB) > Blocksize: 512 > Dumptime: Fri May 19 21:49:56 2006 > Hostname: ayiin.xxxxx > Magic: FreeBSD Kernel Dump > Version String: FreeBSD 6.1-STABLE #3: Tue May 16 23:35:52 EST 2006 > root@ayiin.xxxxxxx:/usr/obj/usr/src/sys/AYIIN > Panic String: sleeping thread > Dump Parity: 2510391376 > Bounds: 0 > Dump Status: good > --- So what is the traceback? See the developers handbook for more information. Kris --vGgW1X5XWziG23Ko Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEc75rWry0BWjoQKURAlwhAKDXptLh6MhcxAd9PtyJtF65v2bGbQCgoKmA F6caicZ44gzWdQsH5a3bIEQ= =mpGk -----END PGP SIGNATURE----- --vGgW1X5XWziG23Ko-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:14:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0296F16A41F for ; Wed, 24 May 2006 06:14:34 +0000 (UTC) (envelope-from paul.lkw@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A01743D46 for ; Wed, 24 May 2006 06:14:33 +0000 (GMT) (envelope-from paul.lkw@gmail.com) Received: by nz-out-0102.google.com with SMTP id l8so1395327nzf for ; Tue, 23 May 2006 23:14:33 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=Dg7CKc/XpuChqVSA2ZmUn73Hk9/rXBG+5QA6p+tdcKuSYJGFFjBr/PZkgw6PtW5Ke/K72pSaQVm20MZiQB0xuO/q9DSZjGd9kvjb/r5KCSPh+bZI/350tGlja82cxqT0neIh+a+NlFoWe/SNzz+9t57zg4Eu26OYGaSFyv4A/WE= Received: by 10.36.147.4 with SMTP id u4mr5367974nzd; Tue, 23 May 2006 23:14:33 -0700 (PDT) Received: by 10.36.77.3 with HTTP; Tue, 23 May 2006 23:14:33 -0700 (PDT) Message-ID: Date: Wed, 24 May 2006 14:14:33 +0800 From: Paul.LKW To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: sendmail-sasl port not work 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, 24 May 2006 06:14:35 -0000 Dear all: I find the sendmail-sasl port will not compile with the option "SASLv2" and I can not get SMTP Auth. The port will install "TLS and Cyrus-SASL" but as I use the command --sendmail -d0.1 -bv root | grep SASL-= - I can not find it compiled with SASL. Any solution to fix it. THX. From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:21:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D47D16A42A for ; Wed, 24 May 2006 06:21:22 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 933A743D46 for ; Wed, 24 May 2006 06:21:21 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 8AF2B136CF8 for ; Wed, 24 May 2006 07:21:20 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k4O6LJmB000899 for ; Wed, 24 May 2006 10:21:19 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k4O6LJwm000898 for freebsd-stable@freebsd.org; Wed, 24 May 2006 10:21:19 +0400 (MSD) (envelope-from dkirhlarov) Date: Wed, 24 May 2006 10:21:19 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060524062118.GA766@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> <44736E11.6060104@mkproductions.org> <20060523203521.GA48061@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060523203521.GA48061@xor.obsecurity.org> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: quota and snapshots in 6.1-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: Wed, 24 May 2006 06:21:22 -0000 Hi! On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: > > >>6.1-STABLE after 6.1-RELEASE is releases. So I think you may want > > If you use snapshots with your quotas, update to 6.1-STABLE. If you Sorry, guys. You are mean RELENG_6_1 or RELENG_6? WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:34:52 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A346F16A422 for ; Wed, 24 May 2006 06:34:52 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2987243D46 for ; Wed, 24 May 2006 06:34:52 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so1201393wxd for ; Tue, 23 May 2006 23:34:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EPGBLCIkPuoOD5ZaqqSGku+oHLv/lwATQW50RqZoaoR48FS1tETWzC1pgBI8ympzoAyoaHaj7MnpHt3DrIhijA1gqCNQ/STJHDlrFdISKAkT5hjPYL6Y7+nT8ZTX8MigzU/soeTqaVCdCDOqPhRmlJMIu3fHExxv+/rSMagSzNA= Received: by 10.70.21.18 with SMTP id 18mr7346085wxu; Tue, 23 May 2006 23:34:51 -0700 (PDT) Received: by 10.70.22.2 with HTTP; Tue, 23 May 2006 23:34:51 -0700 (PDT) Message-ID: Date: Wed, 24 May 2006 08:34:51 +0200 From: "Claus Guttesen" To: "Mark Kirkwood" In-Reply-To: <4473ADF7.4080101@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> <200605231636.27463.kirk@strauser.com> <4473ADF7.4080101@paradise.net.nz> Cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 06:34:52 -0000 > > That did it! Bumping kern.ipc.shmall to 65536 got me back up and runni= ng > > with enough shared_memory to get my jobs done. > > Having not so long ago been caught by this myself, I think the > relationship between shmmax and shmall is worth clarifying: > > $ sysctl -d kern.ipc.shmall > kern.ipc.shmall: Maximum number of pages available for shared memory > $ sysctl -d kern.ipc.shmmax > kern.ipc.shmmax: Maximum shared memory segment size > > So to run 1 Postgres installation with 128Mb of shared memory: > > kern.ipc.shmall=3D32768 > kern.ipc.shmmax=3D134217728 > > However suppose you want to run 2 Postgres installations, each using > 128Mb of shared memory: > > kern.ipc.shmall=3D65536 > kern.ipc.shmmax=3D134217728 > > i.e. maximum system wide shared memory is 65536*4096 =3D 256Mb, but the > maximum size any single segment can be is 128Mb. Thank you. I wasn't aware that one could alter sysctl's. I might dive into that, makes kernel-maintenance a tiny bit easier. regards Claus From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:43:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1046A16A423 for ; Wed, 24 May 2006 06:43:54 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F63D43D53 for ; Wed, 24 May 2006 06:43:52 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr6.xs4all.nl (8.13.6/8.13.6) with ESMTP id k4O6hotw038952; Wed, 24 May 2006 08:43:50 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.6/8.13.3) with ESMTP id k4O6hhZV011254; Wed, 24 May 2006 08:43:43 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.6/8.13.6/Submit) id k4O6hhHp011253; Wed, 24 May 2006 08:43:43 +0200 (CEST) (envelope-from wb) Date: Wed, 24 May 2006 08:43:43 +0200 From: Wilko Bulte To: Mark Kirkwood Message-ID: <20060524064343.GA11231@freebie.xs4all.nl> References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> <20060524012219.GB15327@osiris.chen.org.nz> <4473BC17.5030500@paradise.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4473BC17.5030500@paradise.net.nz> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Dave , freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 06:43:54 -0000 On Wed, May 24, 2006 at 01:51:19PM +1200, Mark Kirkwood wrote.. > Jonathan Chen wrote: > >On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: > >>Hello, > >> I'm trying to compile 6.0-stable on a release box, prior to upgrade. > >>I've tried several times and all end with an internal compiler error: > >>segmentation fault: 11. And then i'm told to submit a bug report. My > >>problem is when this occurs it's not always at the same spot or the same > >>file. One time it even core dumped, though only once. > > > >This is a prime-indicator of dodgy memory. > > Yeah - but it can easily be power supply or motherboard age. I suffered > the latter late last year with a Tyan Thunder LE, I'm using the same > power supply and memory in a Supermicro P3TDER and it is rock solid. CPU fan or chipset fan is also a possibility. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:44:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2E9316A41F for ; Wed, 24 May 2006 06:44:23 +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 1BCE043D45 for ; Wed, 24 May 2006 06:44:20 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4O6iChW014857; Wed, 24 May 2006 00:44:17 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <447400BB.9060603@samsco.org> Date: Wed, 24 May 2006 00:44:11 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitriy Kirhlarov References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> <44736E11.6060104@mkproductions.org> <20060523203521.GA48061@xor.obsecurity.org> <20060524062118.GA766@dimma.mow.oilspace.com> In-Reply-To: <20060524062118.GA766@dimma.mow.oilspace.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-stable@freebsd.org Subject: Re: quota and snapshots in 6.1-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: Wed, 24 May 2006 06:44:24 -0000 Dmitriy Kirhlarov wrote: > Hi! > > On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: > > >>>>>6.1-STABLE after 6.1-RELEASE is releases. So I think you may want >> >>If you use snapshots with your quotas, update to 6.1-STABLE. If you > > > Sorry, guys. You are mean RELENG_6_1 or RELENG_6? > > WBR RELENG_6. However, the changes will likely make their way into RELENG_6_1 in a few weeks as part of an errata update. Scott From owner-freebsd-stable@FreeBSD.ORG Wed May 24 06:56:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47E7E16A41F for ; Wed, 24 May 2006 06:56:55 +0000 (UTC) (envelope-from sergei@konst.donpac.ru) Received: from stc.donpac.ru (stc.donpac.ru [80.254.115.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 889E843D46 for ; Wed, 24 May 2006 06:56:53 +0000 (GMT) (envelope-from sergei@konst.donpac.ru) Received: from [127.0.0.1] (prog-kn.stc.donpac.ru [10.161.193.203]) by stc.donpac.ru (8.13.1/8.13.1/calex3.0.0.3) with ESMTP id k4O6unD6098578; Wed, 24 May 2006 10:56:49 +0400 (MSD) (envelope-from sergei@konst.donpac.ru) X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.0.10250, virus records: 102335, updated: 7.01.2006] Message-ID: <447403BF.4090207@konst.donpac.ru> Date: Wed, 24 May 2006 10:57:03 +0400 From: Sergei User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Paul.LKW" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: sendmail-sasl port not work 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, 24 May 2006 06:56:57 -0000 Did you change your make.conf? > Dear all: > I find the sendmail-sasl port will not compile with the option > "SASLv2" and I can not get SMTP Auth. The port will install "TLS and > Cyrus-SASL" but as I use the command --sendmail -d0.1 -bv root | grep > SASL-- > I can not find it compiled with SASL. > > Any solution to fix it. THX. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Wed May 24 07:28:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D74116A443 for ; Wed, 24 May 2006 07:28:38 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail28.syd.optusnet.com.au (mail28.syd.optusnet.com.au [211.29.133.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D0E43D49 for ; Wed, 24 May 2006 07:28:37 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail28.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k4O7SVi2025666 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 24 May 2006 17:28:33 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k4O7SVpl000812; Wed, 24 May 2006 17:28:31 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k4O7SU0n000811; Wed, 24 May 2006 17:28:30 +1000 (EST) (envelope-from peter) Date: Wed, 24 May 2006 17:28:29 +1000 From: Peter Jeremy To: Hunter Fuller Message-ID: <20060524072829.GA724@turion.vk2pj.dyndns.org> References: <79722fad0605111452r2e5da097x21aa86a63e4dfe52@mail.gmail.com> <79722fad0605230453vc0436d5o352f0f10c995656d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-stable crash 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, 24 May 2006 07:28:38 -0000 On Tue, 2006-May-23 19:04:18 +0000, Hunter Fuller wrote: >Am I the only one who sees the oxymoronity in "6.1-stable crash"? Hopefully. As is regularly pointed out, 'stable' refers primarily to the ABI. FreeBSD 6.1-stable is still under active development, though only code that has previously been tested in -current is supposed to be commited. There are also fairly regular postings pointing out that _all_ software has bugs. Some of these bugs will cause crashes. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Wed May 24 07:42:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A4DA16A573 for ; Wed, 24 May 2006 07:42:07 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 55DC343D8F for ; Wed, 24 May 2006 07:41:55 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 24 May 2006 07:41:54 -0000 Received: from p54A7C76C.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.199.108] by mail.gmx.net (mp035) with SMTP; 24 May 2006 09:41:54 +0200 X-Authenticated: #5465401 Message-ID: <44740E39.8000901@gmx.de> Date: Wed, 24 May 2006 09:41:45 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: Dave References: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> In-Reply-To: <00b401c67ecd$d1aba3c0$0200a8c0@satellite> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-stable@freebsd.org Subject: Re: internal compiler error: segmentation fault: 11 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, 24 May 2006 07:42:07 -0000 Dave wrote: > Hello, > I'm trying to compile 6.0-stable on a release box, prior to upgrade. > I've tried several times and all end with an internal compiler error: > segmentation fault: 11. And then i'm told to submit a bug report. My > problem is when this occurs it's not always at the same spot or the same > file. One time it even core dumped, though only once. > At this point i would appreciate any suggestions, i'm hoping this is > not the indicator of a problem. > Thanks. > Dave. > I'd say in most cases it means that either your memory or your CPU get too hot. Open the case of your machine. If the problem disappears or at least appears less often, consider better cooling for your computer. From owner-freebsd-stable@FreeBSD.ORG Wed May 24 08:20:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F32B16A456 for ; Wed, 24 May 2006 08:20:11 +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 C660643D45 for ; Wed, 24 May 2006 08:20:10 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Fiob4-0000Fn-Do for freebsd-stable@freebsd.org; Wed, 24 May 2006 10:20:02 +0200 Received: from menelaos.informatik.rwth-aachen.de ([137.226.194.73]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 May 2006 10:20:02 +0200 Received: from vs by menelaos.informatik.rwth-aachen.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 May 2006 10:20:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Volker Stolz Date: Wed, 24 May 2006 08:19:56 +0000 (UTC) Lines: 15 Message-ID: References: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: menelaos.informatik.rwth-aachen.de User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: Re: sendmail-sasl port not work 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, 24 May 2006 08:20:12 -0000 * Paul.LKW : > Dear all: > I find the sendmail-sasl port will not compile with the option > "SASLv2" and I can not get SMTP Auth. The port will install "TLS and > Cyrus-SASL" but as I use the command --sendmail -d0.1 -bv root | grep SASL-- > I can not find it compiled with SASL. Did you follow the instructions in /usr/ports/mail/sendmail/pkg-message and invoke the "right" sendmail (ie. preferably with full path in case you're unsure)? Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME FIFA go home! From owner-freebsd-stable@FreeBSD.ORG Wed May 24 08:54:50 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CB7616A42B for ; Wed, 24 May 2006 08:54:50 +0000 (UTC) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-174-86.sn2.eutelia.it [83.211.174.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id C959343D45 for ; Wed, 24 May 2006 08:54:48 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 70D652C90B for ; Wed, 24 May 2006 10:54:46 +0200 (CEST) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id A78EE2C90A; Wed, 24 May 2006 10:54:45 +0200 (CEST) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 64FD22C906; Wed, 24 May 2006 10:54:45 +0200 (CEST) From: Massimo Lusetti To: Kris Kennaway In-Reply-To: <20060523203521.GA48061@xor.obsecurity.org> References: <20060523181638.GC767@dimma.mow.oilspace.com> <6eb82e0605231120q37224c6r3b25982f556bed72@mail.gmail.com> <447366AD.30203@rogers.com> <44736E11.6060104@mkproductions.org> <20060523203521.GA48061@xor.obsecurity.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Wed, 24 May 2006 10:54:45 +0200 Message-Id: <1148460885.4305.4.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Mark Kane , stable@freebsd.org, Rong-en Fan , Mike Jakubik Subject: Re: quota and snapshots in 6.1-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: Wed, 24 May 2006 08:54:50 -0000 On Tue, 2006-05-23 at 16:35 -0400, Kris Kennaway wrote: > If you use snapshots with your quotas, update to 6.1-STABLE. If you > don't use snapshots, 6.1-R should be fine. This was discussed in > excruciating depth a few weeks back, so please read the archives for > more. Probably I've to stress the box a little more but here seems to work correctly. The box is going production really soon so we will see. Thanks to all guys involved for the very good work! -- Massimo There are more way to do things, one is the bsd-way the others are wrong From owner-freebsd-stable@FreeBSD.ORG Wed May 24 09:00:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A221F16A439 for ; Wed, 24 May 2006 09:00:13 +0000 (UTC) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-174-86.sn2.eutelia.it [83.211.174.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id E14D143D48 for ; Wed, 24 May 2006 09:00:12 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 8F6552C90B for ; Wed, 24 May 2006 11:00:11 +0200 (CEST) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id C61B22C90A; Wed, 24 May 2006 11:00:10 +0200 (CEST) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 83B802C906; Wed, 24 May 2006 11:00:10 +0200 (CEST) From: Massimo Lusetti To: Kirk Strauser In-Reply-To: <200605231636.27463.kirk@strauser.com> References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> <200605231636.27463.kirk@strauser.com> Content-Type: text/plain Organization: CEDOC - Modena Date: Wed, 24 May 2006 11:00:10 +0200 Message-Id: <1148461210.4305.8.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 09:00:15 -0000 On Tue, 2006-05-23 at 16:36 -0500, Kirk Strauser wrote: > On Tuesday 23 May 2006 16:19, Jung-uk Kim wrote: > > > I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. :-( > > That did it! Bumping kern.ipc.shmall to 65536 got me back up and running > with enough shared_memory to get my jobs done. So what changed? Why this changes have to happen between upgrade to -STABLE from a three months old -STABLE? -- Massimo.run(); From owner-freebsd-stable@FreeBSD.ORG Wed May 24 09:27:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6936A16A424 for ; Wed, 24 May 2006 09:27:19 +0000 (UTC) (envelope-from vlado@botka.homeunix.org) Received: from smtp-out4.iol.cz (smtp-out4.iol.cz [194.228.2.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA8E43D49 for ; Wed, 24 May 2006 09:27:18 +0000 (GMT) (envelope-from vlado@botka.homeunix.org) Received: from antivir4.iol.cz (avir4 [192.168.30.209]) by smtp-out4.iol.cz (Postfix) with ESMTP id 450871F8C35; Wed, 24 May 2006 11:27:13 +0200 (CEST) Received: from localhost (antivir4.iol.cz [127.0.0.1]) by antivir4.iol.cz (Postfix) with ESMTP id 2EC8124002B; Wed, 24 May 2006 11:27:13 +0200 (CEST) Received: from smtp-out4.iol.cz (smtp-out-4.iplanet.iol.cz [192.168.30.31]) by antivir4.iol.cz (Postfix) with ESMTP id 19374240028; Wed, 24 May 2006 11:27:13 +0200 (CEST) Received: from ace.botka.homeunix.org (3.77.broadband2.iol.cz [83.208.77.3]) by smtp-out4.iol.cz (Postfix) with ESMTP id E1F4222AEC0; Wed, 24 May 2006 11:27:12 +0200 (CEST) Received: by ace.botka.homeunix.org (Postfix, from userid 1001) id 75B442F; Wed, 24 May 2006 11:27:12 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ace.botka.homeunix.org X-Spam-Level: X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, TRACKER_ID autolearn=ham version=3.1.0 Received: from srv (ac.botka.homeunix.org [192.168.1.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ace.botka.homeunix.org (Postfix) with ESMTP id 95A1927; Wed, 24 May 2006 11:27:09 +0200 (CEST) Date: Wed, 24 May 2006 11:27:09 +0200 (CEST) From: Vladimir Botka X-X-Sender: vlado@srv.g1.netng.org To: "Paul.LKW" In-Reply-To: Message-ID: <20060524112559.Q5570@srv.g1.netng.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at iol.cz Cc: freebsd-stable@freebsd.org Subject: Re: sendmail-sasl port not work 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, 24 May 2006 09:27:19 -0000 There are no problems with Postfix. http://wiki.botka.homeunix.org/bin/view/Main/PostfixSaslTls Cheers, -vlado D0000000000000000000000000000000 On Wed, 24 May 2006, Paul.LKW wrote: > Dear all: > I find the sendmail-sasl port will not compile with the option > "SASLv2" and I can not get SMTP Auth. The port will install "TLS and > Cyrus-SASL" but as I use the command --sendmail -d0.1 -bv root | grep SASL-- > I can not find it compiled with SASL. > > Any solution to fix it. THX. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > From owner-freebsd-stable@FreeBSD.ORG Wed May 24 12:22:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC8BC16A435; Wed, 24 May 2006 12:22:07 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 470FC43D6B; Wed, 24 May 2006 12:22:03 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA21416; Wed, 24 May 2006 15:22:00 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <44744FE7.1070301@icyb.net.ua> Date: Wed, 24 May 2006 15:21:59 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.2 (X11/20060512) MIME-Version: 1.0 To: "[LoN]Kamikaze" References: <446DD5EB.6030300@icyb.net.ua> <446DDC3E.1080102@gmx.de> <446DE5B3.1040101@icyb.net.ua> In-Reply-To: <446DE5B3.1040101@icyb.net.ua> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, John Baldwin , freebsd-hardware@freebsd.org Subject: Re: 5.4=>6.1 regression: nforce2 vs. APIC [+fix] 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, 24 May 2006 12:22:08 -0000 on 19/05/2006 18:35 Andriy Gapon said the following: > on 19/05/2006 17:54 [LoN]Kamikaze said the following: >> Andriy Gapon wrote: >>> [Disclaimer, just in case: I do mean APIC, not ACPI] >>> >>> >>> Based on that info and the linux patch in that thread I came up with the >>> following PCI fixup. Now I am running 6.1 with both APIC and "C1 >>> disconnect" enabled for 2 days without any problems. >>> >> Did you file a PR with your fix? > > Not yet. I wanted to receive some feedback and test results first (and > kinda hoped that this will get included without a PR). > I've created a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=97785 Thanks again to John Baldwin for his very much improved version of the patch. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed May 24 13:17:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A03A016A42B; Wed, 24 May 2006 13:17:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FED743D45; Wed, 24 May 2006 13:17:54 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA22592; Wed, 24 May 2006 16:17:42 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <44745CF6.1040402@icyb.net.ua> Date: Wed, 24 May 2006 16:17:42 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.2 (X11/20060512) MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: Bruce Evans Subject: state of fs/udf 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, 24 May 2006 13:17:59 -0000 It seems that UDF fs has been in not-well-supported state for a while now. It seems that Scott Long, original author and maintainer, has moved on to other more important (and, perhaps, interesting) things. ("perhaps" - because RE does not seem to be too exciting on the first glance) Meanwhile, there are several bugs still opened for UDF. Some of them are pretty obvious, some with good patches, some not so trivial, some unhelpful and some are mine :-) I think the following PRs are good candidates for review and possible inclusion into source: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77234 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92040 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84983 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90521 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/97786 Also, from our private conversations I know that Bruce Evans has even more fixes for more problems and better fixes for some bugs described in the above PRs. Those patches that I personally submitted do WorkForMe (TM), but I think that Bruce has much better understanding of VFS stuff and done much better job. Would some committer be so kind to adopt UDF, review the PRs and fix at least the most obvious bugs before 6.2 ? I personally promise to help with testing and discussing things. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed May 24 14:11:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8593A16A48E for ; Wed, 24 May 2006 14:11:59 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7937A43D5C for ; Wed, 24 May 2006 14:11:57 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id F2A61B826 for ; Wed, 24 May 2006 10:11:53 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <200605231531.18092.kirk@strauser.com> References: <200605231531.18092.kirk@strauser.com> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-3-521504846; protocol="application/pkcs7-signature" Message-Id: <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> From: Vivek Khera Date: Wed, 24 May 2006 10:11:52 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 14:11:59 -0000 --Apple-Mail-3-521504846 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 23, 2006, at 4:31 PM, Kirk Strauser wrote: > Has anyone else seen this behavior when upgrading from 6.0 to 6.1? > Any > ideas for a fix? > no. not seen it. did you have a custom kernel with higher SHM settings on 6.0? In any case, here is what you do: in /etc/sysctl.conf add these: kern.ipc.shm_use_phys=1 kern.ipc.shmmax=1073741824 kern.ipc.shmall=262144 kern.ipc.semmsl=512 kern.ipc.semmap=256 and in /boot/loader.conf add these: kern.ipc.semmni=32 kern.ipc.semmns=512 the "sem" variables are really only needed if you want a lot of connections, say > 100. The "shm" settings will cover you for tens of thousands of shared buffers in postgres. You can obviously tune those down to your taste. --Apple-Mail-3-521504846-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 14:18:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBC8A16A566 for ; Wed, 24 May 2006 14:18:39 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2AD943D70 for ; Wed, 24 May 2006 14:18:12 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 5770BB826 for ; Wed, 24 May 2006 10:18:01 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: References: <200605231531.18092.kirk@strauser.com> <200605231713.22363.jkim@FreeBSD.org> <200605231719.56164.jkim@FreeBSD.org> <200605231636.27463.kirk@strauser.com> <4473ADF7.4080101@paradise.net.nz> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-4-521870498; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Wed, 24 May 2006 10:17:58 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: semi-custom kernel (was Re: PostgreSQL uses more memory on 6.1?) 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, 24 May 2006 14:18:42 -0000 --Apple-Mail-4-521870498 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 24, 2006, at 2:34 AM, Claus Guttesen wrote: > Thank you. I wasn't aware that one could alter sysctl's. I might dive > into that, makes kernel-maintenance a tiny bit easier. Boy does it. I've recently combined all my custom kernels into a single semi-custom configuration (actually two, one for SMP and one for UP) and adjust the sysctls either at sysctl.conf or at loader.conf depending on which needs to be where to adjust resources needed by certain servers. For example, the DB servers I set the SHM and SEM settings, on the internal not-connected-to-internet boxes, I disable the firewall via sysctl, etc. I also push into kld's the rarely used devices such as CD-ROM, floppy drive, USB keyboard, gmirror, which are used on only a handful of machines. Then I load the ones I need via loader.conf so they are probed at boot. The CDROM and floppy modules are loaded on demand (ie, basically never on a server) --Apple-Mail-4-521870498-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 14:47:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B710816A841; Wed, 24 May 2006 14:47:26 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1D8C43D60; Wed, 24 May 2006 14:47:25 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.4/8.13.3) with ESMTP id k4OElNs8080603; Wed, 24 May 2006 18:47:23 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Wed, 24 May 2006 18:47:23 +0400 (MSD) From: Maxim Konovalov To: bde@freebsd.org In-Reply-To: <44745CF6.1040402@icyb.net.ua> Message-ID: <20060524184610.W79889@mp2.macomnet.net> References: <44745CF6.1040402@icyb.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Andriy Gapon Subject: Re: state of fs/udf 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, 24 May 2006 14:47:28 -0000 [ CC: Bruce ] Bruce, On Wed, 24 May 2006, 16:17+0300, Andriy Gapon wrote: > > It seems that UDF fs has been in not-well-supported state for a while > now. It seems that Scott Long, original author and maintainer, has moved > on to other more important (and, perhaps, interesting) things. > ("perhaps" - because RE does not seem to be too exciting on the first > glance) > > Meanwhile, there are several bugs still opened for UDF. Some of them are > pretty obvious, some with good patches, some not so trivial, some > unhelpful and some are mine :-) > I think the following PRs are good candidates for review and possible > inclusion into source: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77234 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92040 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84983 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90521 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/97786 > > Also, from our private conversations I know that Bruce Evans has even > more fixes for more problems and better fixes for some bugs described in > the above PRs. Those patches that I personally submitted do WorkForMe > (TM), but I think that Bruce has much better understanding of VFS stuff > and done much better job. > > Would some committer be so kind to adopt UDF, review the PRs and fix at > least the most obvious bugs before 6.2 ? > I personally promise to help with testing and discussing things. Why don't you just commit these fixes? -- Maxim Konovalov From owner-freebsd-stable@FreeBSD.ORG Wed May 24 14:57:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AEB016A7FC for ; Wed, 24 May 2006 14:57:00 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A6DB43D48 for ; Wed, 24 May 2006 14:56:56 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id k4OEtubQ023145 for ; Wed, 24 May 2006 15:55:56 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.6/8.13.6) with ESMTP id k4OEtuhF035550 for ; Wed, 24 May 2006 15:55:56 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.6/8.13.6/Submit) id k4OEtu3r035549 for freebsd-stable@freebsd.org; Wed, 24 May 2006 15:55:56 +0100 (BST) (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: freebsd-stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 24 May 2006 15:55:55 +0100 Message-Id: <1148482556.35287.18.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: 6.1-RELEASE amd64 panic: bad pte 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, 24 May 2006 14:57:01 -0000 Hi, I've just seen the following panic on a dual cpu amd64 box: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:15:57 UTC 2006 root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP amd64 Panic happened during "cd /usr/port/databases/mysql4-server && make install" - box was otherwise idle. TPTE at 0xffff8000040028c8 IS ZERO @ VA 800519000 panic: bad pte cpuid = 1 Uptime: 7d0h12m25s Dumping 2047 MB (2 chunks) chunk 0: 1MB (150 pages) ... ok chunk 1: 2047MB (523888 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok Dump complete As this is a -RELEASE kernel, no kernel.debug exits. As an aside, what happened to the idea of generating these and putting them on the CD or the ftp site? (kgdb) bt #0 0xffffffff803d204d in doadump () #1 0xffffffff803d2074 in doadump () #2 0x0000000000000004 in ?? () #3 0xffffffff803d2677 in boot () #4 0x0000000000000019 in ?? () #5 0x000000000fd2cf65 in ?? () #6 0xffffff005d789260 in ?? () #7 0x0000000000000104 in ?? () #8 0x0000000000000000 in ?? () Previous frame identical to this frame (corrupt stack?) # this is the TPTE pointer from the panic printf (kgdb) x/20 0xffff8000040028c8 0xffff8000040028c8: Cannot access memory at address 0xffff8000040028c8 # This address appears in the backtrace (kgdb) x/40 0xffffff005d789260 0xffffff005d789260: 0x5bf62000 0xffffff00 0x7b9867e0 0xffffff00 0xffffff005d789270: 0x00000000 0x00000000 0x5bf62020 0xffffff00 0xffffff005d789280: 0x00000000 0x00000000 0x7b9867f8 0xffffff00 0xffffff005d789290: 0x00000000 0x00000000 0x62981a80 0xffffff00 0xffffff005d7892a0: 0x00000000 0x00000000 0xb420b890 0xffffffff 0xffffff005d7892b0: 0x00000000 0x00000000 0x00000000 0x00000000 0xffffff005d7892c0: 0x00000000 0x00000000 0x5d7892c0 0xffffff00 0xffffff005d7892d0: 0x62981a80 0xffffff00 0x628d8500 0xffffff00 0xffffff005d7892e0: 0x60e06b80 0xffffff00 0x000186f4 0x05010002 0xffffff005d7892f0: 0x00000000 0x00000000 0x00000000 0x00000000 Pointers to this structure are littered throughout the memory following the stack pointer - it seems to be a thread pointer. The first value (0xffffff005bf62000) appears to be a pointer to struct proc, but I'm not sure if there's anything useful that can be found from that either. The process was "grep", pid 84450, p_flags are P_EXEC|P_WEXIT|P_CONTROLT - so it happened while the process was exiting, which makes sense given the panic is called from pmap_remove_pages(). I'm happy to do more digging if there are any lines of investigation anyone can suggest. Possibly-relevant bits of dmesg: Copyright (c) 1992-2006 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 6.1-RELEASE #0: Sun May 7 04:15:57 UTC 2006 root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.76-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2146893824 (2047 MB) avail memory = 2062053376 (1966 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard I have the coredump available for further analysis if anyone wants it, but without a debug kernel I appreciate it may not be useful. I'm going to compile one up, in case it happens again. Gavin From owner-freebsd-stable@FreeBSD.ORG Wed May 24 15:21:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A0C16A700 for ; Wed, 24 May 2006 15:21:42 +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 5D2A643D46 for ; Wed, 24 May 2006 15:21:40 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FivAX-000224-7K for freebsd-stable@freebsd.org; Wed, 24 May 2006 17:21:05 +0200 Received: from dialin-145-254-131-249.pools.arcor-ip.net ([145.254.131.249]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 May 2006 17:21:05 +0200 Received: from HM-Gerhards by dialin-145-254-131-249.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 May 2006 17:21:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Michael Gerhards Date: Wed, 24 May 2006 17:14:31 +0200 Lines: 54 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: dialin-145-254-131-249.pools.arcor-ip.net User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/6.1-STABLE (i386)) Sender: news Subject: 6-STABLE crashes when surfing via modem 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, 24 May 2006 15:21:42 -0000 Hello! I am running FreeBSD 6-STABLE (last update 14.5.06) on a Fujitsu Siemens Amilo A notebook. This machine has internet access via kppp and a Creative ModemBlaster V.92 serial modem. Sometimes when surfing on the internet (most times with Opera 8.51 AFAIR) the system completly locks up and reboots. I found http://www.at.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html and tried to analysis the crash dump in /var/crash but I am totally new to these things. "kgdb kernel.debug /var/crash/vmcore.2" on my system gives the following output: [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] (...) Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x29 fault code = supervisor write, page not present instruction pointer = 0x20:0xc06ad6a6 stack pointer = 0x28:0xd992f9d0 frame pointer = 0x28:0xd992fa00 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 793 (opera) trap number = 12 panic: page fault Uptime: 19m31s Dumping 478 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 478MB (122352 pages) 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 (CTRL-C to abort) (CTRL-C to abort) 78 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 62 46 30 14 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) quit Has anybody an idea what goes wrong on my system? What could I do in order to find out what goes wrong? Many thanks in advance, Michael From owner-freebsd-stable@FreeBSD.ORG Wed May 24 15:57:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0119116A48E for ; Wed, 24 May 2006 15:57:22 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.FreeBSD.org (Postfix) with SMTP id 9A6AE43D48 for ; Wed, 24 May 2006 15:57:14 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: (qmail 6103 invoked from network); 24 May 2006 19:57:13 +0400 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 24 May 2006 19:57:13 +0400 X-AntiVirus: Checked by Dr.Web [version: 4.33, engine: 4.33.2.02271, virus records: 122697, updated: 24.05.2006] Message-ID: <302701c67f4a$b6d3d040$0c00a8c0@Artem> From: "Artem Kuchin" To: References: <44745CF6.1040402@icyb.net.ua> <20060524184610.W79889@mp2.macomnet.net> Date: Wed, 24 May 2006 19:57:07 +0400 Organization: IT Legion 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.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Subject: Quotas inside jails 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, 24 May 2006 15:57:22 -0000 Sometime ago and have setup 5.3-STABLE box with quotas for jailed users. At that time quotas did not work inside jails, so i just created some group on host machine and group with the same ID inside jail and then put a quota upon that group on the host box. That was quotas are observed. However, user iside jail cannot check their quota this way. Do quotas work now (as of 6.1-STABLE) inside jails correctly? Artem From owner-freebsd-stable@FreeBSD.ORG Wed May 24 16:14:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C566E16A84B for ; Wed, 24 May 2006 16:14:58 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2441A43D45 for ; Wed, 24 May 2006 16:14:56 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 1834598F72 for ; Wed, 24 May 2006 11:14:55 -0500 (CDT) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWWWyrjM4xgl for ; Wed, 24 May 2006 11:14:54 -0500 (CDT) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 4F22397774 for ; Wed, 24 May 2006 11:14:54 -0500 (CDT) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Wed, 24 May 2006 11:14:52 -0500 User-Agent: KMail/1.9.1 References: <200605231531.18092.kirk@strauser.com> <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> In-Reply-To: <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?iso-8859-1?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dA?= =?iso-8859-1?q?J*9f+mX=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605241114.52666.kirk@strauser.com> Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 16:15:03 -0000 On Wednesday 24 May 2006 09:11, Vivek Khera wrote: > no. not seen it. > > did you have a custom kernel with higher SHM settings on 6.0? Nope. I didn't touch the kernel config at all (it includes GENERIC and then adds a couple of nonrelated settings). > In any case, here is what you do: Bumping shmall did the trick, but semmsl was pretty low so I bumped it up just in case. Is any of this stuff well documented other than in NOTES? I can see what each setting does, but don't really have a feel for *why* I'd need to increase a given setting, what the drawback is to increasing it, or why it was so low in the first place. For that matter, why does this stuff have to be manually configured? Couldn't the kernel automatically expand a lot of these numbers as needed? -- Kirk Strauser From owner-freebsd-stable@FreeBSD.ORG Wed May 24 16:52:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 878CB16A42A for ; Wed, 24 May 2006 16:52:02 +0000 (UTC) (envelope-from mehmetpala@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F4743D4C for ; Wed, 24 May 2006 16:52:01 +0000 (GMT) (envelope-from mehmetpala@gmail.com) Received: by nz-out-0102.google.com with SMTP id n1so73756nzf for ; Wed, 24 May 2006 09:52:01 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=c2i6cZBv+/l6aPFQVxpUN6U8+5sDEx5zx7zPvIFqlJ9awDPYD8s9zwk15QcUff2QPHExvoXrB0XMzC+vwlWg7T1mQT8iZJLbwQ5py4zdsvoCJfbGaZZOvm99s/YjvjwT0+geKj4aXqkK+pogI0MsNEvkLNtymfFBQIVYRPL4baE= Received: by 10.64.125.17 with SMTP id x17mr222595qbc; Wed, 24 May 2006 09:52:00 -0700 (PDT) Received: by 10.65.220.12 with HTTP; Wed, 24 May 2006 09:52:00 -0700 (PDT) Message-ID: <412ec2a30605240952j1e5430dch738b2766a21677ca@mail.gmail.com> Date: Wed, 24 May 2006 19:52:00 +0300 From: "Mehmet Pala" To: freebsd-stable@freebsd.org In-Reply-To: <20060524120056.37B2F16A47B@hub.freebsd.org> MIME-Version: 1.0 References: <20060524120056.37B2F16A47B@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: freebsd-stable Digest, Vol 159, Issue 6 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, 24 May 2006 16:52:02 -0000 freebsd-stable-unsubscribe@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Wed May 24 16:58:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A9716A5B5 for ; Wed, 24 May 2006 16:58:09 +0000 (UTC) (envelope-from Joerg.Lehners@Informatik.Uni-Oldenburg.DE) Received: from arbi.Informatik.Uni-Oldenburg.DE (arbi.informatik.uni-oldenburg.de [134.106.1.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C0B43D49 for ; Wed, 24 May 2006 16:58:08 +0000 (GMT) (envelope-from Joerg.Lehners@Informatik.Uni-Oldenburg.DE) Received: from gneedle.Informatik.Uni-Oldenburg.DE ([134.106.11.34]) by arbi.Informatik.Uni-Oldenburg.DE (Exim 3.36) id 1FiwgQ-0005wv-00; Wed, 24 May 2006 18:58:06 +0200 Received: from localhost (missingIP) by gneedle.Informatik.Uni-Oldenburg.DE (Exim 3.36) id 1FiwgQ-0006lP-00; Wed, 24 May 2006 18:58:06 +0200 Date: Wed, 24 May 2006 18:58:06 +0200 (MEST) From: "Joerg Lehners" To: freebsd-stable@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 24 May 2006 16:58:13 -0000 "Rong-en Fan" wrote: > On 5/14/06, Kris Kennaway wrote: >> On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: >>> [...] >> Use tcpdump and related tools to find out what traffic is being sent. >> >> Also verify that you did not change your system configuration in any >> way: there have been no changes to NFS since the release, so it is >> unclear why an update would cause the problem to suddenly occur. >> >> Kris > > Hi Kris and Howard, > > As I posted few days ago, I have similar problems like Howard's > (some details in the thread "6.1-RELEASE, em0 high interrupt rate > and nfsd eats lots of cpu" on stable@). After binary searching > the source tree, I found that > > RELENG_6_1, 2006.04.30.03.57 ok > RELENG_6_1, 2006.04.30.04.00 bad > > The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. > With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, > the same problem occurs. [...] Confirmed! I can create the problem here at will. Setup 1: NFS server 'testido' FreeBSD 6.1-STABLE as of 15. May 2006 with sys/kern/vfs_lookup.c 1.80.2.7, NFS schurks FreeBSD 6.1-STABLE as of 15. May 2006. /usr/src from testido mounted on /mnt on schurks. running 'cd /mnt ; du >/dev/null' two times (first after fresh boot of testido second when all served data is in memory of testido): joerg @ schurks> cd /mnt joerg @ schurks> time du >/dev/null 86.09s real 0.14s user 1.91s system joerg @ schurks> time du >/dev/null 205.10s real 0.20s user 1.92s system joerg @ schurks> Screenfull output of top on testido AFTER both tests (testido stopped responding to screen output sometimes, especially during the second test): last pid: 329; load averages: 4.14, 2.77, 1.25 up 0+00:07:30 18:44:47 29 processes: 1 running, 28 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 8420K Active, 28M Inact, 72M Wired, 110M Buf, 880M Free Swap: 4000M Total, 4000M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 201 root 1 4 0 1232K 792K - 4:42 116.31% nfsd 329 joerg 1 96 0 2404K 1676K RUN 0:00 0.00% top 168 root 1 115 0 2456K 1760K select 0:00 0.00% sshd 313 root 1 96 0 1428K 1168K select 0:00 0.00% rlogind 194 root 1 115 0 1556K 1256K select 0:00 0.00% mountd 299 root 1 8 0 1720K 1436K wait 0:00 0.00% login 314 root 1 8 0 1748K 1460K wait 0:00 0.00% login 298 root 1 96 0 1304K 1048K select 0:00 0.00% rlogind 199 root 1 4 0 1356K 1040K accept 0:00 0.00% nfsd 256 root 1 96 0 2892K 1760K select 0:00 0.00% ntpd 315 joerg 1 20 0 1448K 1020K pause 0:00 0.00% ksh 300 root 1 5 0 1448K 996K ttyin 0:00 0.00% ksh 158 root 1 96 0 1332K 940K select 0:00 0.00% syslogd 163 root 1 96 0 1448K 1128K select 0:00 0.00% inetd 176 root 1 96 0 1408K 1044K select 0:00 0.00% rpcbind 185 root 1 96 0 1476K 1148K select 0:00 0.00% ypbind 261 root 1 115 0 1304K 952K select 0:00 0.00% lpd Setup 2: NFS server 'testido' FreeBSD 6.1-STABLE as of 15. May 2006 with sys/kern/vfs_lookup.c 1.80.2.6, NFS schurks FreeBSD 6.1-STABLE as of 15. May 2006. Same tests as before: joerg @ schurks> time du >/dev/null 22.63s real 0.15s user 1.82s system joerg @ schurks> time du >/dev/null 16.52s real 0.17s user 1.68s system joerg @ schurks> Screenfull output of top on testido AFTER both tests (testido responded fine during both tests): last pid: 329; load averages: 0.49, 0.26, 0.10 up 0+00:01:50 18:35:30 29 processes: 1 running, 28 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 8424K Active, 28M Inact, 72M Wired, 110M Buf, 880M Free Swap: 4000M Total, 4000M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 201 root 1 4 0 1232K 792K - 0:03 3.76% nfsd 168 root 1 115 0 2456K 1760K select 0:00 0.00% sshd 329 joerg 1 96 0 2404K 1676K RUN 0:00 0.00% top 313 root 1 96 0 1428K 1168K select 0:00 0.00% rlogind 194 root 1 115 0 1556K 1256K select 0:00 0.00% mountd 299 root 1 8 0 1720K 1440K wait 0:00 0.00% login 314 root 1 8 0 1748K 1464K wait 0:00 0.00% login 298 root 1 96 0 1304K 1048K select 0:00 0.00% rlogind 199 root 1 4 0 1356K 1040K accept 0:00 0.00% nfsd 315 joerg 1 20 0 1448K 1020K pause 0:00 0.00% ksh 256 root 1 96 0 2892K 1760K select 0:00 0.00% ntpd 300 root 1 5 0 1448K 996K ttyin 0:00 0.00% ksh 158 root 1 96 0 1332K 940K select 0:00 0.00% syslogd 163 root 1 96 0 1448K 1128K select 0:00 0.00% inetd 261 root 1 109 0 1304K 952K select 0:00 0.00% lpd 176 root 1 96 0 1408K 1044K select 0:00 0.00% rpcbind 185 root 1 96 0 1476K 1148K select 0:00 0.00% ypbind See the HUGE difference in consumed TIME. The only difference was sys/kern/vfs_lookup.c version 1.80.2.6 vs. 1.80.2.7. Joerg -- Mail: Joerg.Lehners@Informatik.Uni-Oldenburg.DE Tel: 2198 Real: Joerg Lehners, Informatik ARBI, Uni Oldenburg, D-26111 Oldenburg Unwoerter: Kostensenkung - Gewinnmaximierung - billig, billig, billig From owner-freebsd-stable@FreeBSD.ORG Wed May 24 17:22:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A1816A4A3 for ; Wed, 24 May 2006 17:22:58 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C16E243D48 for ; Wed, 24 May 2006 17:22:57 +0000 (GMT) (envelope-from howard@leadmon.net) Received: from gamer (gamer.leadmon.net [207.114.24.7]) (authenticated bits=0) by ibm.leadmon.net (8.13.6/8.13.6/LNSG+ORDB+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id k4OHMqiL001172; Wed, 24 May 2006 13:22:56 -0400 (EDT) (envelope-from howard@leadmon.net) Authentication-Results: ibm.leadmon.net from=howard@leadmon.net; sender-id=pass; spf=pass X-SenderID: Sendmail Sender-ID Filter v0.2.12 ibm.leadmon.net k4OHMqiL001172 From: "Howard Leadmon" To: "'Rong-en Fan'" Date: Wed, 24 May 2006 13:22:47 -0400 Organization: Leadmon Networking Message-ID: <001401c67f56$b02975e0$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: <6eb82e0605231208ydcd888ck578b485393f670d3@mail.gmail.com> Thread-Index: AcZ+nFrMjh8kgqd0TJmSfurtuMDP1AAua14A X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (ibm.leadmon.net [207.114.24.13]); Wed, 24 May 2006 13:22:56 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.2/1480/Wed May 24 12:45:51 2006 on ibm.leadmon.net X-Virus-Status: Clean Cc: 'Konstantin Belousov' , freebsd-stable@freebsd.org Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? 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, 24 May 2006 17:22:58 -0000 Hello Rong-en, As an update, I did the below, and I still had the issue with either version of vfs_lookup.c compiled in and running. On the bright side, I didn't realize you could step through the cvs by date, guess I just never paid attention. So I just stepped back to 'tag=RELENG_6 date=2006.04.20.00.00.00' on my server, rebuilt and violla nfs is now running perfect. So backing out something has fixed my problem, now to figure out just what it was. As I don't know what has caused this, I have done complete buildworlds to make sure everything updates which takes a few hours. I am going to start moving the cvs date forward till I get the problem back, once I nail this down a bit more, I'll let you know what I come up with. --- Howard Leadmon http://www.leadmon.net > -----Original Message----- > From: Rong-en Fan [mailto:grafan@gmail.com] > Sent: Tuesday, May 23, 2006 3:09 PM > To: Howard Leadmon > Cc: freebsd-stable@freebsd.org > Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? > > On 5/23/06, Howard Leadmon wrote: > > > > Hello Rong-en, > > > > Thanks for the info on getting the debugger configured, > and on the serial > > console. I will have to try and play with the serial > console thing more, I > > just tried putting in the flags and the damn thing hung, I > had to boot > > from CD and take the stuff back out. > > > > One thing you mention below that concerns me is that you > have version 1.90 of > > the vfs_lookup.c file. I just did a less on > /usr/src/sys/kern/vfs_lookup.c > > and I see the following: > > > > FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 > 03:57:46 kris > > Exp > > > > > > I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure > I had the > > current stuff before rebuilding the kernel just now, and > still I see the same thing. > > Is something fishy going on here, or did you by chance make a typo?? > > Sorry for the confusion. rev 1.90 is the number for -HEAD. To > back out this MFC'ed change for RELENG_6_1, please cvsup to > RELENG_6_1 date=2006.04.30.03.57.00. Then you should see it is > > 1.80.2.6 2006/03/31 07:39:24 kris > > To verify the effect of this revision. Please run RELENG_6_1 > with 2006.04.30.03.57.00 and 2006.04.30.04.00.00. > > Regards, > Rong-En Fan > From owner-freebsd-stable@FreeBSD.ORG Wed May 24 18:19:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC0916AB84 for ; Wed, 24 May 2006 18:19:25 +0000 (UTC) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAACF43D70 for ; Wed, 24 May 2006 18:19:18 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [192.168.1.128] (e178025128.adsl.alicedsl.de [85.178.25.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate2.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 0FE213000C7E; Wed, 24 May 2006 20:19:17 +0200 (CEST) Message-ID: <4474A3DA.7040409@mail.uni-mainz.de> Date: Wed, 24 May 2006 20:20:10 +0200 From: "O. Hartmann" User-Agent: Thunderbird 1.5.0.2 (X11/20060517) MIME-Version: 1.0 To: Damian Gerow , freebsd-stable@freebsd.org References: <4472551C.5020803@mail.uni-mainz.de> <20060524002323.GF61179@afflictions.org> In-Reply-To: <20060524002323.GF61179@afflictions.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Cc: Subject: Re: nve0: device timeout 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, 24 May 2006 18:19:30 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Damian Gerow wrote: > Thus spake O. Hartmann (ohartman@mail.uni-mainz.de) [22/05/06 20:23]: > : Is there a solution on its way? What is about the Berkeley native nfe-code? > > As someone already pointed out, the fix is already in -CURRENT. A patch for > -STABLE has been posted recently, but I don't remember if it was to stable@ > or amd64@. > > FWIW, I'd recommend if_nfe. It's proven a little more stable for me, and I > haven't had any issues with device timeouts at all. > > All right, I did as recommended an now: Voila, I have a usable computersystem! Without any patch or the new nfe driver a system based on the ASUS A8N32-SLI is unusable! The box get stuck every few minutes for a second a loose keyboard input and corrupt DVD/DVD+-RW or CD-R/CD-RW while burning. Hope the nfe driver will find it's way into stable as fast as possible ... oh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdKPY9PZHcThI6nsRAivbAJ0UE9sbLeL+0sLlRcti3jA3m4iP0wCfXNdG OmlR2KW1bSxhrDrYiw1dYjE= =Elyt -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 18:22:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0C9116AAEF for ; Wed, 24 May 2006 18:22:29 +0000 (UTC) (envelope-from mark@islandnet.com) Received: from cluster.islandnet.com (cluster.islandnet.com [199.175.106.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4907943D5E for ; Wed, 24 May 2006 18:22:29 +0000 (GMT) (envelope-from mark@islandnet.com) Received: from [199.175.106.221] (port=19844 helo=helpdesk.islandnet.com) by cluster03.islandnet.com with SMTP id 1Fiy05-000NYU-9q for freebsd-stable@freebsd.org; Wed, 24 May 2006 11:22:29 -0700 Date: Wed, 24 May 2006 11:22:29 -0700 Message-ID: <4474a465-73d1@helpdesk.islandnet.com> References: <001401c67f56$b02975e0$071872cf@Leadmon.local> From: Mark Morley To: freebsd-stable@freebsd.org Content-type: text/plain MIME-Version: 1.0 X-Priority: 3 X-Mailer: Helpdesk Webmail (http://helpdesk.islandnet.com) X-Originating-IP: [199.175.106.243] X-GeoIP: CA Canada Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Morley List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 18:22:32 -0000 Another data point: One of our NFS servers is an amd64 based system serving a cluster of web and email servers. Under 6.1-RCx it gave us the same (or better) performance than the server it replaced (which was 4.11). The server load hovered between 0.x and 1.x But after upping it to 6.1-STABLE the load now hovers between 5.x and 6.x with spikes as high as 8.x, and there has been no change at all in the NFS client traffic or other loading factors that we can tell. This in turn makes for slower NFS client accesses. I am going to try reverting to an earlier src tree and see if that helps. Mark -- Mark Morley Owner / Administrator Islandnet.com From owner-freebsd-stable@FreeBSD.ORG Wed May 24 19:10:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9704016A5C8 for ; Wed, 24 May 2006 19:10:33 +0000 (UTC) (envelope-from offbyone@xs4all.nl) Received: from smtp13.wanadoo.fr (smtp13.wanadoo.fr [193.252.22.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 833C243D72 for ; Wed, 24 May 2006 19:10:26 +0000 (GMT) (envelope-from offbyone@xs4all.nl) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1309.wanadoo.fr (SMTP Server) with ESMTP id 8CBF37000085 for ; Wed, 24 May 2006 21:10:23 +0200 (CEST) Received: from [192.168.0.4] (ADijon-151-1-39-217.w83-196.abo.wanadoo.fr [83.196.15.217]) by mwinf1309.wanadoo.fr (SMTP Server) with ESMTP id DB6C7700009D for ; Wed, 24 May 2006 21:10:22 +0200 (CEST) X-ME-UUID: 20060524191022898.DB6C7700009D@mwinf1309.wanadoo.fr Message-ID: <4474AF9D.6010408@xs4all.nl> Date: Wed, 24 May 2006 21:10:21 +0200 From: Jacques User-Agent: Thunderbird 1.5.0.2 (X11/20060423) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 6.1 troubles -- cannot "install buildworld" 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, 24 May 2006 19:10:38 -0000 On an older i386 box (Pentium III), used as a workstation, we have been running FreeBSD_4.x and 5.x for a long time without problems. Now, using cvsup, we updated FreeBSD source from 5.4p14 (default release=cvs tag=RELENG_5_4) to 6.1 (default release=cvs tag=RELENG_6_1_0_RELEASE) and updated the system according to the canonical method: # cd /usr/src # make buildworld # make buildkernel # make installkernel # mergemaster -p # shutdown # cd /usr/src/ # make installworld But that last step won't run. Output is: # make installworld mkdir -p /tmp/install.e6Vg3aX8 for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep install-info ln lockf make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.e6Vg3aX8; done cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.e6Vg3aX8 make -f Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc; make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -eU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -eU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -eU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p / cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/man; set - `grep "^[a-zA-Z]" /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done cd /usr/share/openssl/man; set - `grep "^[a-zA-Z]" /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done cd /usr/share/openssl/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/nls; set - `grep "^[a-zA-Z]" /usr/src/etc/nls.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done -------------------------------------------------------------- >>> Installing everything -------------------------------------------------------------- cd /usr/src; make -f Makefile.inc1 install ===> share/info (install) ===> include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Wonder whether anyone else has had any experience similar, or any insight on what to do about it. dmesg is: Copyright (c) 1992-2006 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 6.1-RELEASE #0: Wed May 24 18:48:01 CEST 2006 jls@bulgari.192.168.0.0:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (664.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 267386880 (255 MB) avail memory = 252182528 (240 MB) MPTable: ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0x44000000-0x47ffffff,0x40300000-0x4037ffff irq 16 at device 2.0 on pci0 pcib1: at device 30.0 on pci0 pci2: on pcib1 fxp0: port 0x1000-0x103f mem 0x40000000-0x40000fff irq 20 at device 8.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:a5:26:1e:a5 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2460-0x246f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0x2440-0x245f irq 23 at device 31.4 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 pci0: at device 31.5 (no driver attached) pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc9fff,0xca000-0xd77ff,0xe0000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/13 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (irq) Timecounter "TSC" frequency 664514056 Hz quality 800 Timecounters tick every 1.000 msec ad0: 9541MB at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 Trying to mount root from ufs:/dev/ad0s2a pid 648 (netstat), uid 1001: exited on signal 11 The last two lines look bad, but df shows / is mounted: Filesystem Size Used Avail Capacity Mounted on /dev/ad0s2a 248M 61M 167M 27% / [etc] Thanks for any suggestions. - Jacques From owner-freebsd-stable@FreeBSD.ORG Wed May 24 20:47:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 026F516A695 for ; Wed, 24 May 2006 20:47:48 +0000 (UTC) (envelope-from vivek@khera.org) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A22743D48 for ; Wed, 24 May 2006 20:47:47 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 9DCE8B826 for ; Wed, 24 May 2006 16:47:46 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <200605241114.52666.kirk@strauser.com> References: <200605231531.18092.kirk@strauser.com> <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> <200605241114.52666.kirk@strauser.com> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-11-545257533; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Wed, 24 May 2006 16:47:45 -0400 To: FreeBSD Stable X-Mailer: Apple Mail (2.750) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 20:47:48 -0000 --Apple-Mail-11-545257533 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On May 24, 2006, at 12:14 PM, Kirk Strauser wrote: > Is any of this stuff well documented other than in NOTES? I can > see what > each setting does, but don't really have a feel for *why* I'd need to > increase a given setting, what the drawback is to increasing it, or > why it > was so low in the first place. SYSV IPC falls into the black art part of the universe, unfortunately. You really have to dig into the application (ie, postgres in this case) to determine how much of those resources it wants. > > For that matter, why does this stuff have to be manually configured? > Couldn't the kernel automatically expand a lot of these numbers as > needed? Some are only settable at boot time because they make fixed sized structures (yes, still in this day and age...) I don't know the drawbacks of making them larger than necessary, but with multi-gig RAM servers I don't worry about it too much. --Apple-Mail-11-545257533-- From owner-freebsd-stable@FreeBSD.ORG Wed May 24 23:24:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9794F16A432 for ; Wed, 24 May 2006 23:24:49 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-4.paradise.net.nz (bm-4a.paradise.net.nz [203.96.152.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 275C243D48 for ; Wed, 24 May 2006 23:24:48 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb1-src-1.paradise.net.nz [203.96.152.172]) by linda-4.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IZS001XWMDA70@linda-4.paradise.net.nz> for freebsd-stable@freebsd.org; Thu, 25 May 2006 11:24:47 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-172.dsl.clear.net.nz [218.101.29.172]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 0CED138B452; Thu, 25 May 2006 11:24:26 +1200 (NZST) Date: Thu, 25 May 2006 11:23:57 +1200 From: Mark Kirkwood In-reply-to: <200605241114.52666.kirk@strauser.com> To: Kirk Strauser Message-id: <4474EB0D.5020105@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.5 (X11/20060417) References: <200605231531.18092.kirk@strauser.com> <42A89ED6-54B7-43EC-832B-A54F76C0D17B@khera.org> <200605241114.52666.kirk@strauser.com> Cc: freebsd-stable@freebsd.org Subject: Re: PostgreSQL uses more memory on 6.1? 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, 24 May 2006 23:24:49 -0000 Kirk Strauser wrote: > > Bumping shmall did the trick, but semmsl was pretty low so I bumped it up > just in case. > > Is any of this stuff well documented other than in NOTES? I can see what > each setting does, but don't really have a feel for *why* I'd need to > increase a given setting, what the drawback is to increasing it, or why it > was so low in the first place. > For the configuration of IPC for Postgresql, see: http://www.postgresql.org/docs/8.1/static/kernel-resources.html#SYSVIPC And scroll down to the section for FreeBSD. Unfortunately, that whole section on kernel resources is a bit hidden away - it usually takes me a couple of attempts to find it! cheers Mark From owner-freebsd-stable@FreeBSD.ORG Thu May 25 01:46:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3478816A41F for ; Thu, 25 May 2006 01:46:04 +0000 (UTC) (envelope-from hackmiester@hackmiester.com) Received: from smtpout08-04.prod.mesa1.secureserver.net (smtpout08-04.prod.mesa1.secureserver.net [64.202.165.12]) by mx1.FreeBSD.org (Postfix) with SMTP id B5A1543D45 for ; Thu, 25 May 2006 01:46:03 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 27214 invoked from network); 25 May 2006 01:46:03 -0000 Received: from unknown (68.220.175.103) by smtpout08-04.prod.mesa1.secureserver.net (64.202.165.12) with ESMTP; 25 May 2006 01:46:02 -0000 In-Reply-To: <20060524072829.GA724@turion.vk2pj.dyndns.org> References: <79722fad0605111452r2e5da097x21aa86a63e4dfe52@mail.gmail.com> <79722fad0605230453vc0436d5o352f0f10c995656d@mail.gmail.com> <20060524072829.GA724@turion.vk2pj.dyndns.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6A8C20E9-B1E8-46F6-B102-C52FB99D1095@hackmiester.com> Content-Transfer-Encoding: 7bit From: Hunter Fuller Date: Wed, 24 May 2006 20:46:47 +0000 To: Peter Jeremy X-Mailer: Apple Mail (2.746.2) Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-stable crash 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, 25 May 2006 01:46:04 -0000 On 24 May 2006, at 7:28 AM, Peter Jeremy wrote: > On Tue, 2006-May-23 19:04:18 +0000, Hunter Fuller wrote: >> Am I the only one who sees the oxymoronity in "6.1-stable crash"? > > Hopefully. > > As is regularly pointed out, 'stable' refers primarily to the ABI. I was just trying to make people chuckle :( > FreeBSD 6.1-stable is still under active development, though only > code that has previously been tested in -current is supposed to be > commited. > > There are also fairly regular postings pointing out that _all_ > software has bugs. Some of these bugs will cause crashes. > > -- > Peter Jeremy > From owner-freebsd-stable@FreeBSD.ORG Thu May 25 03:49:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1422216A421 for ; Thu, 25 May 2006 03:49:16 +0000 (UTC) (envelope-from howard@leadmon.net) Received: from ibm.leadmon.net (ibm.leadmon.net [207.114.24.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0742043D58 for ; Thu, 25 May 2006 03:49:10 +0000 (GMT) (envelope-from howard@leadmon.net) Received: from gamer (gamer.leadmon.net [207.114.24.7]) (authenticated bits=0) by ibm.leadmon.net (8.13.6/8.13.6/LNSG+ORDB+SCOP+NJABL+SBL+DSBL+SORBS+CBL+RHSBL) with ESMTP id k4P3mw6M003999; Wed, 24 May 2006 23:49:02 -0400 (EDT) (envelope-from howard@leadmon.net) Authentication-Results: ibm.leadmon.net from=howard@leadmon.net; sender-id=pass; spf=pass X-SenderID: Sendmail Sender-ID Filter v0.2.12 ibm.leadmon.net k4P3mw6M003999 From: "Howard Leadmon" To: "'Howard Leadmon'" , "'Rong-en Fan'" Date: Wed, 24 May 2006 23:48:53 -0400 Organization: Leadmon Networking Message-ID: <003001c67fae$27a88370$071872cf@Leadmon.local> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: <001401c67f56$b02975e0$071872cf@Leadmon.local> Thread-Index: AcZ+nFrMjh8kgqd0TJmSfurtuMDP1AAua14AABQ8pFA= X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0 (ibm.leadmon.net [207.114.24.13]); Wed, 24 May 2006 23:49:02 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on ibm.leadmon.net X-Virus-Status: Clean Cc: 'Konstantin Belousov' , freebsd-stable@freebsd.org, 'Kris Kennaway' Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? 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, 25 May 2006 03:49:16 -0000 I need to follow up to the below, as I am not sure why the below test with the vfs_lookup.c didn't pan out the first time, but with my new found knowledge on cvs I was determined to regress the system till I found the smoking gun so to speak, which I have done. First let me say that instead of running RELENG_6_1 like Rong-en is, I am running the RELENG_6 tree that I know updates more often, but seems to work well for me. OK, so as I said above I started to regress the system a couple days at a time, till suddenly NFS stared working again, so I knew at that point it was a change that was made. So then I started to narrow the time range, till I got to the point that it broke. Sure enough under the RELENG_6 branch, this time was as follows: *default tag=RELENG_6 date=2006.04.30.03.57.00 (Works OK) *default tag=RELENG_6 date=2006.04.30.03.58.00 (Broken) So what's changed at that delta, under the one that works vfs_lookup.c is: Edit src/sys/kern/vfs_lookup.c Add delta 1.80.2.6 2006.03.31.07.39.24 kris Under the one that fails the vfs_lookup.c is: Edit src/sys/kern/vfs_lookup.c Add delta 1.80.2.7 2006.04.30.03.57.46 kris So I stand corrected on my last post, the issue is in fact in this module, as just taking that module back to 1.80.2.6 fixes the problem with my server. I even took multiple NFS clients and gave them a heavy workload, and CPU still remained reasonable, and very responsive. As soon as I rev to the new version, NFS breaks badly and even a single client doing something like a du of a directory structure results in sluggishness and extreme CPU usage. I am not a coder, so not sure why this module was changed, but unless there is some good reason why the changes were needed I would suspect it needs to be rolled back, or something fixed. So Rong-en Fan, I think you were dead on with your analysis that the issue is in fact inside the vfs_lookup.c module. I hope this helps... --- Howard Leadmon - howard@leadmon.net http://www.leadmon.net > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Howard Leadmon > Sent: Wednesday, May 24, 2006 1:23 PM > To: 'Rong-en Fan' > Cc: 'Konstantin Belousov'; freebsd-stable@freebsd.org > Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? > > > Hello Rong-en, > > > As an update, I did the below, and I still had the issue with > either version > of vfs_lookup.c compiled in and running. > > On the bright side, I didn't realize you could step through > the cvs by date, guess I just never paid attention. So I > just stepped back to 'tag=RELENG_6 date=2006.04.20.00.00.00' > on my server, rebuilt and violla nfs is now running > perfect. > > So backing out something has fixed my problem, now to figure > out just what it > was. As I don't know what has caused this, I have done > complete buildworlds > to make sure everything updates which takes a few hours. I > am going to > start moving the cvs date forward till I get the problem > back, once I nail this down a bit more, I'll let you know > what I come up with. > > > > --- > Howard Leadmon > http://www.leadmon.net > > > > > -----Original Message----- > > From: Rong-en Fan [mailto:grafan@gmail.com] > > Sent: Tuesday, May 23, 2006 3:09 PM > > To: Howard Leadmon > > Cc: freebsd-stable@freebsd.org > > Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? > > > > On 5/23/06, Howard Leadmon wrote: > > > > > > Hello Rong-en, > > > > > > Thanks for the info on getting the debugger configured, > > and on the serial > > > console. I will have to try and play with the serial > > console thing more, I > > > just tried putting in the flags and the damn thing hung, I > > had to boot > > > from CD and take the stuff back out. > > > > > > One thing you mention below that concerns me is that you > > have version 1.90 of > > > the vfs_lookup.c file. I just did a less on > > /usr/src/sys/kern/vfs_lookup.c > > > and I see the following: > > > > > > FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 > > 03:57:46 kris > > > Exp > > > > > > > > > I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure > > I had the > > > current stuff before rebuilding the kernel just now, and > > still I see the same thing. > > > Is something fishy going on here, or did you by chance > make a typo?? > > > > Sorry for the confusion. rev 1.90 is the number for -HEAD. > To back out > > this MFC'ed change for RELENG_6_1, please cvsup to > > RELENG_6_1 date=2006.04.30.03.57.00. Then you should see it is > > > > 1.80.2.6 2006/03/31 07:39:24 kris > > > > To verify the effect of this revision. Please run RELENG_6_1 with > > 2006.04.30.03.57.00 and 2006.04.30.04.00.00. > > > > Regards, > > Rong-En Fan > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Thu May 25 05:19:28 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 798E316A41F for ; Thu, 25 May 2006 05:19:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31D3243D46 for ; Thu, 25 May 2006 05:19:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C61221A4ED0; Wed, 24 May 2006 22:19:27 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0930C515B5; Thu, 25 May 2006 01:19:26 -0400 (EDT) Date: Thu, 25 May 2006 01:19:26 -0400 From: Kris Kennaway To: Howard Leadmon Message-ID: <20060525051926.GB97976@xor.obsecurity.org> References: <001401c67f56$b02975e0$071872cf@Leadmon.local> <003001c67fae$27a88370$071872cf@Leadmon.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CdrF4e02JqNVZeln" Content-Disposition: inline In-Reply-To: <003001c67fae$27a88370$071872cf@Leadmon.local> User-Agent: Mutt/1.4.2.1i Cc: 'Konstantin Belousov' , freebsd-stable@freebsd.org, 'Rong-en Fan' , 'Kris Kennaway' Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 25 May 2006 05:19:28 -0000 --CdrF4e02JqNVZeln Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 24, 2006 at 11:48:53PM -0400, Howard Leadmon wrote: > So what's changed at that delta, under the one that works vfs_lookup.c is: >=20 > Edit src/sys/kern/vfs_lookup.c > Add delta 1.80.2.6 2006.03.31.07.39.24 kris >=20 >=20 > Under the one that fails the vfs_lookup.c is: >=20 > Edit src/sys/kern/vfs_lookup.c > Add delta 1.80.2.7 2006.04.30.03.57.46 kris >=20 >=20 >=20 > So I stand corrected on my last post, the issue is in fact in this modul= e, as > just taking that module back to 1.80.2.6 fixes the problem with my server= . I > even took multiple NFS clients and gave them a heavy workload, and CPU st= ill > remained reasonable, and very responsive. As soon as I rev to the new > version, NFS breaks badly and even a single client doing something like a= du > of a directory structure results in sluggishness and extreme CPU usage. Yep, unfortunately this commit was necessary to fix other bugs. Jeff said he should have time to look at it next week. Kris --CdrF4e02JqNVZeln Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdT5eWry0BWjoQKURAmD7AKDYOcZrJK2ONr5dgI7Pmi9K63pgQACeKuEw vC7wawE43VpYUG6Yc1bGQcA= =gl35 -----END PGP SIGNATURE----- --CdrF4e02JqNVZeln-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 09:49:44 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43ECD16A433 for ; Thu, 25 May 2006 09:49:44 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (office.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id A144F43D4C for ; Thu, 25 May 2006 09:49:43 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 6E6CD136CF4 for ; Thu, 25 May 2006 10:49:42 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k4P9nf9e002412 for ; Thu, 25 May 2006 13:49:41 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k4P9nfRf002411 for stable@freebsd.org; Thu, 25 May 2006 13:49:41 +0400 (MSD) (envelope-from dkirhlarov) Date: Thu, 25 May 2006 13:49:41 +0400 From: Dmitriy Kirhlarov To: stable@freebsd.org Message-ID: <20060525094940.GC771@dimma.mow.oilspace.com> Mail-Followup-To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Cc: Subject: building release problem RELENG_6 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, 25 May 2006 09:49:47 -0000 Hi, list. I'm trying build release with this script: -------- #!/bin/sh # # script for auto-build fresh release RELEASE="RELENG_6" DATE="05/24/2006 12:00:00 UTC" UNIONFSPATCH="unionfs6-p10.diff" (rm -rf /usr/src/*; rm -rf /usr/obj/*; cd /usr/; \ CVSROOT=/home/ncvs cvs co -r${RELEASE} \ -D "${DATE}" src; \ cp /root/conf/OILSPACE1 /root/conf/OILSPACE1DEB /root/conf/THINKPAD_KST /usr/src/sys/i386/conf/; \ cp /root/conf/install.cfg /usr/src/release/; \ cd /usr/src; patch -p0 < /root/conf/local.patch; \ cd /; patch -p0 < /root/tmp/${UNIONFSPATCH}; \ cd /usr/src && \ make -j4 buildworld && \ make buildkernel KERNCONF=THINKPAD_KST && \ make buildkernel KERNCONF=OILSPACE1 && \ make buildkernel KERNCONF=OILSPACE1DEB && \ cd release && make release BUILDNAME=${RELEASE} \ CHROOTDIR=/usr/release \ CVSROOT=/home/ncvs \ EXTSRCDIR=/usr/src \ KERNELS=OILSPACE1 \ MAKE_ISOS=yes \ NOPORTS=yes \ RELEASETAG=${RELEASE} \ WORLD_FLAGS="-j4") > \ /var/log/make_release.log 2>&1 -------- But it stop with diagnose: -------- rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/R/stage/kernels/usr/include -I/usr/obj/usr/src/sys/OILSPACE1 /usr/src/sys/modules/xl/../../pci/if_xl.c ===> zlib (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I@/../include -I/R/stage/kernels/usr/include -I/usr/obj/usr/src/sys/OILSPACE1 /usr/src/sys/modules/zlib/../../net/zlib.c 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. -------- It's stoping in release stage 3.1 on kernel OILSPACE1. This kernel build successful before "make release". Any ideas? Full build log archive is: http://www.higis.ru/~dimma/make_release.log.bz2 WBR From owner-freebsd-stable@FreeBSD.ORG Thu May 25 13:59:57 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6794D16A42A for ; Thu, 25 May 2006 13:59:57 +0000 (UTC) (envelope-from paul@xciv.org) Received: from mailhost.xciv.org (vantage.xciv.org [194.145.196.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id E932C43D48 for ; Thu, 25 May 2006 13:59:56 +0000 (GMT) (envelope-from paul@xciv.org) Received: from localhost ([127.0.0.1] helo=xciv.org) by mailhost.xciv.org with esmtp id 1FjGNS-0005RQ-00; Thu, 25 May 2006 14:59:50 +0100 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-stable@freebsd.org Organization: XCIV, London UK Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 May 2006 14:59:50 +0100 Message-ID: <20919.1148565590@xciv.org> From: Paul Civati X-XCIV-MailScanner: Found to be clean Subject: PXE boot images: 6.1 i386/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paul@xciv.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 13:59:57 -0000 For those of you wishing to PXE boot 6.1 RELEASE I have made some boot images that work easily with pxelinux (syslinux) PXE set-up. They are around 30MB in size each and built from the -bootonly ISO images. Note these simply boot the whole image, and don't use the pxeboot binary. In fact I've test booted both on an LGA775 3.0GHz EM64T box and they both boot fine. Download and a quick pxelinux set-up howto: http://blog.rackred.com/2006/05/25/pxe-boot-freebsd-6x/ http://blog.rackred.com/2006/04/21/pxe-boot-freebsd-howto/ I'm sure I'll have some feedback if they don't work, but I'd like to hear from anyone using them successfully too. :) -Paul- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 14:58:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A4D216A474 for ; Thu, 25 May 2006 14:58:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85AB143D53 for ; Thu, 25 May 2006 14:58:17 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k4PEwBBq047545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 May 2006 17:58:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k4PEwBm2060351; Thu, 25 May 2006 17:58:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k4PEw9Js060350; Thu, 25 May 2006 17:58:09 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 25 May 2006 17:58:09 +0300 From: Konstantin Belousov To: Kris Kennaway Message-ID: <20060525145809.GP54541@deviant.kiev.zoral.com.ua> References: <001401c67f56$b02975e0$071872cf@Leadmon.local> <003001c67fae$27a88370$071872cf@Leadmon.local> <20060525051926.GB97976@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bJ3jXuwtxrXxD2iT" Content-Disposition: inline In-Reply-To: <20060525051926.GB97976@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on fw.zoral.com.ua Cc: 'Rong-en Fan' , Howard Leadmon , freebsd-stable@freebsd.org Subject: [patch, try 1] Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 25 May 2006 14:58:18 -0000 --bJ3jXuwtxrXxD2iT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2006 at 01:19:26AM -0400, Kris Kennaway wrote: > On Wed, May 24, 2006 at 11:48:53PM -0400, Howard Leadmon wrote: >=20 > > So what's changed at that delta, under the one that works vfs_lookup.c = is: > >=20 > > Edit src/sys/kern/vfs_lookup.c > > Add delta 1.80.2.6 2006.03.31.07.39.24 kris > >=20 > >=20 > > Under the one that fails the vfs_lookup.c is: > >=20 > > Edit src/sys/kern/vfs_lookup.c > > Add delta 1.80.2.7 2006.04.30.03.57.46 kris > >=20 > >=20 > >=20 > > So I stand corrected on my last post, the issue is in fact in this mod= ule, as > > just taking that module back to 1.80.2.6 fixes the problem with my serv= er. I > > even took multiple NFS clients and gave them a heavy workload, and CPU = still > > remained reasonable, and very responsive. As soon as I rev to the new > > version, NFS breaks badly and even a single client doing something like= a du > > of a directory structure results in sluggishness and extreme CPU usage. >=20 > Yep, unfortunately this commit was necessary to fix other bugs. Jeff > said he should have time to look at it next week. >=20 > Kris I tried to debug the problem. First, I have to admit that I cannot reproduce the problem on GENERIC kernel. Only after QUOTAS where added, and, correspondingly, UFS started to require Giant, I get described behaviour. Below are the changes to GENERIC config file I made to reproduce problem. Index: amd64/conf/GENERIC =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 RCS file: /usr/local/arch/ncvs/src/sys/amd64/conf/GENERIC,v retrieving revision 1.439.2.11 diff -u -r1.439.2.11 GENERIC --- amd64/conf/GENERIC 30 Apr 2006 17:39:43 -0000 1.439.2.11 +++ amd64/conf/GENERIC 25 May 2006 14:44:14 -0000 @@ -26,6 +26,19 @@ #hints "GENERIC.hints" # Default places to look for devices. =20 makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug symbols +options KDB +options KDB_TRACE +#options KDB_UNATTENDED +options DDB +options DDB_NUMSYM +options BREAK_TO_DEBUGGER +options INVARIANTS +options INVARIANT_SUPPORT +options WITNESS +options DEBUG_LOCKS +options DEBUG_VFS_LOCKS +options DIAGNOSTIC +options MUTEX_PROFILING =20 #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler @@ -34,6 +47,7 @@ options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support +options QUOTA options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device After that, server machine easily panics on=20 KASSERT(!(debug_mpsafenet =3D=3D 1 && mtx_owned(&Giant)), ("nfssvc_nfsd(): debug.mpsafenet=3D1 && Giant")); from nfsserver/nfs_syscalls.c, line 570. As I understand the problem, kern/vfs_lookup.c:lookup() could aquire additional locks on Giant, indicating this by GIANTHELD flag in nd. All processing in nfsserver already goes with Giant held, so, I just dropped that excessive locks after return from lookup. System with patch applied survived smoke test (client did du on mounted dir, patch was generated from exported fs, etc.). nfsd eats no more than 25% of CPU (with INVARIANTS). Please, users who reported the problem and willing to help, try the patch (generated against STABLE) and give the feedback. Index: nfsserver/nfs_serv.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/sys/nfsserver/nfs_serv.c,v retrieving revision 1.156.2.2 diff -u -r1.156.2.2 nfs_serv.c --- nfsserver/nfs_serv.c 13 Mar 2006 03:06:49 -0000 1.156.2.2 +++ nfsserver/nfs_serv.c 25 May 2006 14:44:25 -0000 @@ -569,6 +569,10 @@ =20 error =3D lookup(&ind); ind.ni_dvp =3D NULL; + if (ind.ni_cnd.cn_flags & GIANTHELD) { + mtx_unlock(&Giant); + ind.ni_cnd.cn_flags &=3D ~GIANTHELD; + } =20 if (error =3D=3D 0) { /* @@ -1915,6 +1919,10 @@ =20 error =3D lookup(&nd); nd.ni_dvp =3D NULL; + if (nd.ni_cnd.cn_flags & GIANTHELD) { + mtx_unlock(&Giant); + nd.ni_cnd.cn_flags &=3D ~GIANTHELD; + } if (error) goto ereply; =20 @@ -2141,6 +2149,10 @@ =20 error =3D lookup(&nd); nd.ni_dvp =3D NULL; + if (nd.ni_cnd.cn_flags & GIANTHELD) { + mtx_unlock(&Giant); + nd.ni_cnd.cn_flags &=3D ~GIANTHELD; + } =20 if (error) goto out; @@ -2878,6 +2890,10 @@ =20 error =3D lookup(&nd); nd.ni_dvp =3D NULL; + if (nd.ni_cnd.cn_flags & GIANTHELD) { + mtx_unlock(&Giant); + nd.ni_cnd.cn_flags &=3D ~GIANTHELD; + } =20 if (error =3D=3D 0) { bzero((caddr_t)fhp, sizeof(nfh)); Index: nfsserver/nfs_srvsubs.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/local/arch/ncvs/src/sys/nfsserver/nfs_srvsubs.c,v retrieving revision 1.136.2.2 diff -u -r1.136.2.2 nfs_srvsubs.c --- nfsserver/nfs_srvsubs.c 4 Apr 2006 15:29:51 -0000 1.136.2.2 +++ nfsserver/nfs_srvsubs.c 25 May 2006 14:44:25 -0000 @@ -875,6 +875,10 @@ } if (!lockleaf) cnp->cn_flags &=3D ~LOCKLEAF; + if (cnp->cn_flags & GIANTHELD) { + mtx_unlock(&Giant); + cnp->cn_flags &=3D ~GIANTHELD; + } =20 /* * nfs_namei() guarentees that fields will not contain garbage --bJ3jXuwtxrXxD2iT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdcYAC3+MBN1Mb4gRAsSgAKDRwtPXPk/SzTdAYa4ZZ2cfKoN+BQCgi2yZ yA8iFmWWaxPDTuhH7AriVk0= =pCcP -----END PGP SIGNATURE----- --bJ3jXuwtxrXxD2iT-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 15:31:11 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7DF316A4AC for ; Thu, 25 May 2006 15:31:11 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B62043D46 for ; Thu, 25 May 2006 15:31:10 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 3047 invoked from network); 26 May 2006 01:31:09 +1000 Received: from 203-214-153-204.perm.iinet.net.au (HELO localhost) (203.214.153.204) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 May 2006 01:31:09 +1000 Date: Fri, 26 May 2006 01:31:05 +1000 From: Norberto Meijome To: stable@freebsd.org Message-ID: <20060526013105.22ee47ad@localhost> In-Reply-To: <20060524020116.GB54710@xor.obsecurity.org> References: <20060524115659.7895006a@localhost> <20060524020116.GB54710@xor.obsecurity.org> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: GELI issues ? (Re: Increase in panics under 6.1) 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, 25 May 2006 15:31:15 -0000 On Tue, 23 May 2006 22:01:16 -0400 Kris Kennaway wrote: > So what is the traceback? > > See the developers handbook for more information. doh! yes, i'll get onto this as soon as I can. Interestingly enough , i had some nasty issues todays on same laptop. I had 2 x 6 GB GELI vnodes, running mtree -K md5digest to compare contents. Disk IO was high as expected...but then it just died down (but the mtree hadnt finished). (swap is also GELI) Any subsequent process trying to access the encrypted mount points simply stalled for as long as I cared to wait (10 minutes). The processes even stalled a shutdown -r. On restart, I repeated and had the same problem with only one of the encrpyed vnodes. Had to restart again - then I got the following msgs (which seem to have blocked the bg fsck) (apologies about wrapping): May 25 16:25:51 ayiin kernel: fsync: giving up on dirty May 25 16:25:51 ayiin kernel: 0xc4fe7aa0: tag devfs, type VCHR May 25 16:25:51 ayiin kernel: usecount 1, writecount 0, refcount 628 mountedhere 0xc4da5500 May 25 16:25:51 ayiin kernel: flags () May 25 16:25:51 ayiin kernel: v_object 0xc1025738 ref 0 pages 2499 May 25 16:25:51 ayiin kernel: lock type devfs: EXCL (count 1) by thread 0xc5296300 (pid 778) May 25 16:25:51 ayiin kernel: dev ad0s1f May 25 16:25:51 ayiin kernel: fsync: giving up on dirty May 25 16:25:51 ayiin kernel: 0xc4fe7aa0: tag devfs, type VCHR May 25 16:25:51 ayiin kernel: usecount 1, writecount 0, refcount 628 mountedhere 0xc4da5500 May 25 16:25:51 ayiin kernel: flags () May 25 16:25:51 ayiin kernel: v_object 0xc1025738 ref 0 pages 2499 May 25 16:25:51 ayiin kernel: lock type devfs: EXCL (count 1) by thread 0xc5296300 (pid 778) May 25 16:25:51 ayiin kernel: dev ad0s1f manual fsck fixed other issues. What was this all about? I couldnt waste any more time, so I booted 6.1-RELEASE , went to fixit, restored source and kernel from the CD, rebooted, rebuilt world... and everything is just fine now. I still have the older kernel (but not world) if it's useful. If anyone has any idea of what could have caused all these issues, i'd love to hear :) otherwise...i'll put it to a bad week compounded with Murphy's laws... cheers, Beto From owner-freebsd-stable@FreeBSD.ORG Thu May 25 16:01:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3319516A4CD for ; Thu, 25 May 2006 16:01:41 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A42E43D77 for ; Thu, 25 May 2006 16:01:33 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k4PG1W2w094095 for ; Thu, 25 May 2006 18:01:32 +0200 (CEST) X-Ids: 168 Received: from heho.labo (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id k4PG1Utl055879 for ; Thu, 25 May 2006 18:01:30 +0200 (MEST) Received: (from arno@localhost) by heho.labo (8.13.3/8.13.1/Submit) id k4PG1Upj055876; Thu, 25 May 2006 18:01:30 +0200 (MEST) (envelope-from arno) Sender: arno@heho.snv.jussieu.fr To: freebsd-stable@freebsd.org From: "Arno J. Klaassen" Date: 25 May 2006 18:01:30 +0200 Message-ID: Lines: 91 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.168]); Thu, 25 May 2006 18:01:32 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1484/Thu May 25 17:19:23 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 4475D4DC.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: kmem leak in tmpmfs? 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, 25 May 2006 16:01:46 -0000 Hello, I get a very easy to reproduce panic on 6.1-STABLE : /etc/periodic/weekly/310.locate panics with panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc0577574 in boot (howto=260) at /files/bsd/src6/sys/kern/kern_shutdown.c:409 #2 0xc05778a6 in panic ( fmt=0xc078dc1d "kmem_malloc(%ld): kmem_map too small: %ld total allocated") at /files/bsd/src6/sys/kern/kern_shutdown.c:565 #3 0xc06df1ab in kmem_malloc (map=0xc10430c0, size=4096, flags=258) at /files/bsd/src6/sys/vm/vm_kern.c:299 #4 0xc06d49a7 in page_alloc (zone=0xc1035700, bytes=0, pflag=0x0, wait=0) at /files/bsd/src6/sys/vm/uma_core.c:958 #5 0xc06d43db in slab_zalloc (zone=0xc1035700, wait=258) at /files/bsd/src6/sys/vm/uma_core.c:823 #6 0xc06d60f6 in uma_zone_slab (zone=0xc1035700, flags=2) at /files/bsd/src6/sys/vm/uma_core.c:2025 #7 0xc06d635f in uma_zalloc_bucket (zone=0xc1035700, flags=2) at /files/bsd/src6/sys/vm/uma_core.c:2134 #8 0xc06d5f39 in uma_zalloc_arg (zone=0xc1035700, udata=0x0, flags=2) at /files/bsd/src6/sys/vm/uma_core.c:1942 #9 0xc05d17ff in cache_enter (dvp=0xc8bf1110, vp=0xc8dd4110, cnp=0xfe14bbbc) at uma.h:275 #10 0xc06c77c4 in ufs_lookup (ap=0xfe14ba40) at /files/bsd/src6/sys/ufs/ufs/ufs_lookup.c:583 #11 0xc0756073 in VOP_CACHEDLOOKUP_APV (vop=0x0, a=0x0) at vnode_if.c:150 #12 0xc05d1dfa in vfs_cache_lookup (ap=0x0) at vnode_if.h:82 #13 0xc0755fe8 in VOP_LOOKUP_APV (vop=0xc07c8a60, a=0xfe14baec) at vnode_if.c:99 #14 0xc05d71fb in lookup (ndp=0xfe14bb94) at vnode_if.h:56 #15 0xc05d6998 in namei (ndp=0xfe14bb94) at /files/bsd/src6/sys/kern/vfs_lookup.c:203 #16 0xc05e865f in kern_lstat (td=0xc6b29780, path=0x0, pathseg=UIO_USERSPACE, sbp=0x0) at /files/bsd/src6/sys/kern/vfs_syscalls.c:2125 #17 0xc05e85df in lstat (td=0x0, uap=0xfe14bd04) at /files/bsd/src6/sys/kern/vfs_syscalls.c:2109 #18 0xc073e672 in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 134664008, tf_esi = 134663936, tf_ebp = -1077941544, tf_isp = -32195228, tf_ebx = 672511016, tf_edx = 134663936, tf_ecx = 134561792, tf_eax = 190, tf_trapno = 0, tf_err = 2, tf_eip = 672396855, tf_cs = 51, tf_eflags = 582, tf_esp = -1077941700, tf_ss = 59}) at /files/bsd/src6/sys/i386/i386/trap.c:981 #19 0xc072b21f in Xint0x80_syscall () at /files/bsd/src6/sys/i386/i386/exception.s:200 #20 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) This box has nothing particular, apart from maybe a large number of stamp-file based test-databases (with a lot of zero-sized files named .key=value). Producing this bug is easy : - set tmpmfs="YES" and set tmpsize greater than around 220m - start /etc/periodic/weekly/310.locate (and nothing else!) - wait two-three hours and bang Last test is with tmpfs=1024m and I monitored df -h /tmp and vmstat -zm every minute; when the system panics, last output is : Filesystem Size Used Avail Capacity Mounted on /dev/md0 989M 219M 691M 24% /var/tmp vmstat -zm | fgrep md0 md0: 512, 0, 453257, 15, 453437 I'm quite not an expert, but looks to me as if md0 use stays almost 100% in kmem and is never swapped (as it is supposed to do by default according to the man-page). While here, and being struck as well by the nfsd-bug, at least vfs_lookup.c seems common to both problems. Full vmstat-zm logs available. Thanx, Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-stable@FreeBSD.ORG Thu May 25 16:15:34 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C8B816A7CE for ; Thu, 25 May 2006 16:15:34 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACE3A43D5A for ; Thu, 25 May 2006 16:15:32 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 5385 invoked from network); 25 May 2006 16:15:31 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.131.179]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 25 May 2006 16:15:31 -0000 Date: Thu, 25 May 2006 18:15:28 +0200 From: Fabian Keil To: freebsd-stable@freebsd.org Message-ID: <20060525181528.59c423e7@localhost> In-Reply-To: <20060526013105.22ee47ad@localhost> References: <20060524115659.7895006a@localhost> <20060524020116.GB54710@xor.obsecurity.org> <20060526013105.22ee47ad@localhost> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_pSV4gO64tvsGh6=D2AqhZOs"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Subject: Re: GELI issues ? (Re: Increase in panics under 6.1) 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, 25 May 2006 16:15:40 -0000 --Sig_pSV4gO64tvsGh6=D2AqhZOs Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Norberto Meijome wrote: > On Tue, 23 May 2006 22:01:16 -0400 > Kris Kennaway wrote: >=20 > > So what is the traceback? > >=20 > > See the developers handbook for more information. >=20 > doh! yes, i'll get onto this as soon as I can. >=20 > Interestingly enough , i had some nasty issues todays on same laptop. > I had 2 x 6 GB GELI vnodes, running mtree -K md5digest to compare > contents. Disk IO was high as expected...but then it just died down > (but the mtree hadnt finished).=20 > (swap is also GELI) >=20 > Any subsequent process trying to access the encrypted mount points > simply stalled for as long as I cared to wait (10 minutes). The > processes even stalled a shutdown -r.=20 I'm not sure if it's related, but I lately see this behaviour on NFS mounts if the server is not responding. Doing cd /mnt/mydeadnfsmount/[tab for autocompletion] is enough to render the current console unresponsive. Fabian --=20 http://www.fabiankeil.de/ --Sig_pSV4gO64tvsGh6=D2AqhZOs Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEddggjV8GA4rMKUQRAqaWAKCQAwhbZLSLpLD32Nc4V6NXXXek9ACfYGrt KRHd47E6DMylZqIsbyrq3fw= =Gbdn -----END PGP SIGNATURE----- --Sig_pSV4gO64tvsGh6=D2AqhZOs-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 17:58:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4303216B1B1 for ; Thu, 25 May 2006 17:58:07 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C8CE43D5F for ; Thu, 25 May 2006 17:58:05 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 27799 invoked from network); 25 May 2006 17:58:03 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.131.179]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 25 May 2006 17:58:03 -0000 Date: Thu, 25 May 2006 19:57:56 +0200 From: Fabian Keil To: "Arno J. Klaassen" Message-ID: <20060525195756.7eaf4aa2@localhost> In-Reply-To: References: X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_YVbxbPVeI+oV.pyGxTmd_z/"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? 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, 25 May 2006 17:58:18 -0000 --Sig_YVbxbPVeI+oV.pyGxTmd_z/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Arno J. Klaassen" wrote: > Hello, >=20 > I get a very easy to reproduce panic on 6.1-STABLE : >=20 > /etc/periodic/weekly/310.locate panics with >=20 > panic: kmem_malloc(4096): kmem_map too small: 335544320 total > allocated > This box has nothing particular, apart from maybe a large number > of stamp-file based test-databases (with a lot of zero-sized > files named .key=3Dvalue). > Producing this bug is easy : >=20 > - set tmpmfs=3D"YES" and set tmpsize greater than around 220m > - start /etc/periodic/weekly/310.locate (and nothing else!) > - wait two-three hours and bang >=20 > Last test is with tmpfs=3D1024m and I monitored df -h /tmp and > vmstat -zm every minute; when the system panics, last output is : >=20 > Filesystem Size Used Avail Capacity Mounted on > /dev/md0 989M 219M 691M 24% /var/tmp >=20 > vmstat -zm | fgrep md0 > md0: 512, 0, 453257, 15, 453437 >=20 > I'm quite not an expert, but looks to me as if md0 use stays > almost 100% in kmem and is never swapped (as it is supposed to do > by default according to the man-page). The rc script has different defaults than mdmfs: fk@TP51 ~ $grep tmpmfs_flags /etc/defaults/rc.conf=20 tmpmfs_flags=3D"-S -M" # Extra mdmfs options for the mfs /tmp You probably want to ditch the "-M". Fabian --=20 http://www.fabiankeil.de/ --Sig_YVbxbPVeI+oV.pyGxTmd_z/ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdfApjV8GA4rMKUQRAlQgAJ93eF5uhuyA9wjYsv11DVvxalTLJACeJZvg 7u40GgI18Heskl0UMJMUSBI= =wt/E -----END PGP SIGNATURE----- --Sig_YVbxbPVeI+oV.pyGxTmd_z/-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 18:00:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F8116B268 for ; Thu, 25 May 2006 18:00:39 +0000 (UTC) (envelope-from kensmith@FreeBSD.org) Received: from bloom.cse.buffalo.edu (bloom.cse.Buffalo.EDU [128.205.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFD3143D7C for ; Thu, 25 May 2006 18:00:14 +0000 (GMT) (envelope-from kensmith@FreeBSD.org) Received: from bloom.cse.buffalo.edu (localhost.cse.buffalo.edu [127.0.0.1]) by bloom.cse.buffalo.edu (8.13.6/8.12.4) with ESMTP id k4PI0D8q067523 for ; Thu, 25 May 2006 14:00:13 -0400 (EDT) Received: (from kensmith@localhost) by bloom.cse.buffalo.edu (8.13.6/8.13.6/Submit) id k4PI0Dui067522 for freebsd-stable@freebsd.org; Thu, 25 May 2006 14:00:13 -0400 (EDT) (envelope-from kensmith) Date: Thu, 25 May 2006 14:00:13 -0400 From: Ken Smith To: freebsd-stable@freebsd.org Message-ID: <20060525180013.GB67473@bloom.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: FreeBSD 5.5 Released 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, 25 May 2006 18:00:51 -0000 --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline It is my great pleasure and privilege to announce the availability of FreeBSD 5.5-RELEASE. Work done between the 5.4-RELEASE and this release has mostly been bugfixes. Some "vendor supplied" software has also been updated, mostly due to security concerns (specifically BIND and sendmail). This is the last planned release on the 5-STABLE branch. The FreeBSD development community is currently focusing its efforts on the 6-STABLE and CURRENT codelines. No new major features are planned for the 5-STABLE branch, although minor updates and bugfixes may be merged at the discretion of individual developers. The FreeBSD security team will support the FreeBSD 5.5-RELEASE-based security branch with advisories and security patches until the end-of-life date documented at http://security.freebsd.org/ (as of this writing, May 31, 2008). For a complete list of new features and known problems, please see the online release notes and errata list, available at: http://www.FreeBSD.org/releases/5.5R/relnotes.html http://www.FreeBSD.org/releases/5.5R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng Availability ------------- FreeBSD 5.5-RELEASE supports the amd64, i386, pc98, alpha, and sparc64 architectures and can be installed directly over the net using bootable media or copied to a local NFS/FTP server. Distributions for all architectures are available now. Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 5.5-based products: ~ FreeBSD Mall, Inc. http://www.freebsdmall.com/ ~ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html If you can't afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 and SHA256 checksums for the release images are included at the bottom of this message. BitTorrent ---------- 5.5-RELEASE ISOs are not available via BitTorrent at this time. They may be made available in the future on an on-demand basis. FTP --- At the time of this announcement the following FTP sites have FreeBSD 5.5-RELEASE available. ftp://ftp.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.FreeBSD.org/pub/FreeBSD/ ftp://ftp7.FreeBSD.org/pub/FreeBSD/ ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ch.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fi.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ie.FreeBSD.org/pub/FreeBSD/ ftp://ftp.is.FreeBSD.org/pub/FreeBSD/ ftp://ftp1.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ ftp://ftp.si.FreeBSD.org/pub/FreeBSD/ ftp://ftp1.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp9.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Israel, Japan, Korea, Latvia, Lithuania, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html Acknowledgments ---------------- Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 5.5 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Sentex Communications, and Copan Systems. The release engineering team for 5.5-RELEASE includes: Scott Long Release Engineering Ken Smith Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination Robert Watson Release Engineering, Security Doug White Release Engineering Maxime Henrion Release Engineering Hiroki Sato Release Engineering, Documentation Murray Stokely Release Engineering Bruce A. Mah Documentation Takahashi Yoshihiro PC98 Release Building Wilko Bulte Alpha Release Building Kris Kennaway Package Building Joe Marcus Clark Package Building Kiril Ponomarew Package Building Colin Percival Security Officer CD Image Checksums ------------------ MD5 (5.5-RELEASE-alpha-bootonly.iso) = 4de66e8aeb7d3842f36dcbd93834acaa MD5 (5.5-RELEASE-alpha-disc1.iso) = 618fc2622d1e41f7b75a38b06eb6a8ae MD5 (5.5-RELEASE-alpha-disc2.iso) = d169bbcb7870de8c54dbcdb39b0a3967 MD5 (5.5-RELEASE-amd64-bootonly.iso) = 2d79d5b7cd032b004305c0a8d6d72ce3 MD5 (5.5-RELEASE-amd64-disc1.iso) = dcaa38041be2735c2c9e8159640045b2 MD5 (5.5-RELEASE-amd64-disc2.iso) = 38d5ff06cb1dea9761cdd6f6fa39138f MD5 (5.5-RELEASE-i386-bootonly.iso) = 331e1aa238f595cc913c697ce71fc4f3 MD5 (5.5-RELEASE-i386-disc1.iso) = c66d2ff89d8177b31417f8752eadf6a8 MD5 (5.5-RELEASE-i386-disc2.iso) = 91508e819b4efcfda9b900f57aace472 MD5 (5.5-RELEASE-pc98-disc1.iso) = 7e14250d9cf44a9964fe45c1cca8b782 MD5 (5.5-RELEASE-sparc64-bootonly.iso) = 7eaa9db570cde6b36f6d6734520fdd3a MD5 (5.5-RELEASE-sparc64-disc1.iso) = 59be492e648d56f9c046459776303108 MD5 (5.5-RELEASE-sparc64-disc2.iso) = 35c393b4129b09fc16adc66a7180a23c SHA256 (5.5-RELEASE-amd64-bootonly.iso) = 36826ae8e1c2bdfe011b1b9597f5f2406f3d6bdc7e5fdfa4ec75a12652a1a51d SHA256 (5.5-RELEASE-amd64-disc1.iso) = f71eedf18ab24d973c938b473ca127018eb87ab1d1b4c96a5d8d1e9cd8f261d3 SHA256 (5.5-RELEASE-amd64-disc2.iso) = 60daae915430e60a02d577ad0f409de6f011d4ac102ea6f2c332e2c24fad9340 SHA256 (5.5-RELEASE-i386-bootonly.iso) = b9f052d2f0d2f3a9924354c0ad16c3ffda286562dbe29a28ce74a75c7b4c710c SHA256 (5.5-RELEASE-i386-disc1.iso) = 40d41ec7b567e7952d0f85729f340d409911368808256dae123ff1b97155c1ae SHA256 (5.5-RELEASE-i386-disc2.iso) = f561695f7c6bf673a1b84d0f8480d181aa3eac73cd2a14ce3d99d51f580eb42e SHA256 (5.5-RELEASE-pc98-disc1.iso) = 44526391702a21332bb5844ef2d6cf85b08447eec00dde62f930b032ee29b42d SHA256 (5.5-RELEASE-sparc64-bootonly.iso) = 7157e8ad27d8c285addf784589ed69043c4c10bff808f7a7ce6a81073c89c37f SHA256 (5.5-RELEASE-sparc64-disc1.iso) = 4d14d0547fc2bdf92c5def07f81351693c85039e5b4b05a5da89d1ca73cb577a SHA256 (5.5-RELEASE-sparc64-disc2.iso) = d4d3322d333d439e2f87cfc6476af45d8869ec9d2b5bc377bd8c89e7d43b2b4c -ken --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEdfCm/G14VSmup/YRAkbrAKCJnBKUAMOOmZse6Bs8MH0MM3/RbQCePLfp QodD1wx9JlOU0Xt7nLfTTzc= =/NqT -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 18:45:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38B7C16B428 for ; Thu, 25 May 2006 18:45:40 +0000 (UTC) (envelope-from jmz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED41F43D5A for ; Thu, 25 May 2006 18:45:39 +0000 (GMT) (envelope-from jmz@FreeBSD.org) Received: from freefall.freebsd.org (jmz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4PIjdOV070556 for ; Thu, 25 May 2006 18:45:39 GMT (envelope-from jmz@freefall.freebsd.org) Received: (from jmz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4PIjdx7070553; Thu, 25 May 2006 18:45:39 GMT (envelope-from jmz) Date: Thu, 25 May 2006 18:45:39 GMT Message-Id: <200605251845.k4PIjdx7070553@freefall.freebsd.org> From: Jean-Marc Zucconi To: freebsd-stable@freebsd.org Subject: (bsd)tar is broken on 6.1 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, 25 May 2006 18:45:46 -0000 # tar cf /dev/null X11R6.old # archive_write_pax_header: 'x' header failed?! This can't happen. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger jmz@FreeBSD.org [KeyID: 400B38E9] From owner-freebsd-stable@FreeBSD.ORG Thu May 25 20:11:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CCB716C09F for ; Thu, 25 May 2006 20:11:09 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FE3043D46 for ; Thu, 25 May 2006 20:11:07 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by nf-out-0910.google.com with SMTP id k26so148067nfc for ; Thu, 25 May 2006 13:11:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sN0v2BafHWlyuUeo+WiTLk3BxwVOAxNJVh7E/DJxX96gtuyc43+kmLX/yPd5vlUvY8sVrcZWaRsRPoE1RUwQJl4UnF5yrn4BZTQfMrrcB+fiA209q22S+XtY19QPhrBKtWlOjv2sUhAc0G5fnqMitHIjr7Fekd1OUaLE91MFO48= Received: by 10.49.7.18 with SMTP id k18mr6947891nfi; Thu, 25 May 2006 13:04:56 -0700 (PDT) Received: by 10.48.30.7 with HTTP; Thu, 25 May 2006 13:04:56 -0700 (PDT) Message-ID: <6eb82e0605251304y6cb57da5t99568bbbc19d1fa6@mail.gmail.com> Date: Thu, 25 May 2006 16:04:56 -0400 From: "Rong-en Fan" To: "Konstantin Belousov" In-Reply-To: <20060525145809.GP54541@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <001401c67f56$b02975e0$071872cf@Leadmon.local> <003001c67fae$27a88370$071872cf@Leadmon.local> <20060525051926.GB97976@xor.obsecurity.org> <20060525145809.GP54541@deviant.kiev.zoral.com.ua> Cc: freebsd-stable@freebsd.org, Howard Leadmon , Kris Kennaway Subject: Re: [patch, try 1] Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 25 May 2006 20:11:27 -0000 On 5/25/06, Konstantin Belousov wrote: > On Thu, May 25, 2006 at 01:19:26AM -0400, Kris Kennaway wrote: > > On Wed, May 24, 2006 at 11:48:53PM -0400, Howard Leadmon wrote: > > > > > So what's changed at that delta, under the one that works vfs_lookup.= c is: > > > > > > Edit src/sys/kern/vfs_lookup.c > > > Add delta 1.80.2.6 2006.03.31.07.39.24 kris > > > > > > > > > Under the one that fails the vfs_lookup.c is: > > > > > > Edit src/sys/kern/vfs_lookup.c > > > Add delta 1.80.2.7 2006.04.30.03.57.46 kris > > > > > > > > > > > > So I stand corrected on my last post, the issue is in fact in this m= odule, as > > > just taking that module back to 1.80.2.6 fixes the problem with my se= rver. I > > > even took multiple NFS clients and gave them a heavy workload, and CP= U still > > > remained reasonable, and very responsive. As soon as I rev to the ne= w > > > version, NFS breaks badly and even a single client doing something li= ke a du > > > of a directory structure results in sluggishness and extreme CPU usag= e. > > > > Yep, unfortunately this commit was necessary to fix other bugs. Jeff > > said he should have time to look at it next week. > > > > Kris > > I tried to debug the problem. First, I have to admit that I cannot > reproduce the problem on GENERIC kernel. Only after QUOTAS where added, > and, correspondingly, UFS started to require Giant, > I get described behaviour. Below are the changes to GENERIC config file > I made to reproduce problem. > [...] > After that, server machine easily panics on > > KASSERT(!(debug_mpsafenet =3D=3D 1 && mtx_owned(&Giant)), > ("nfssvc_nfsd(): debug.mpsafenet=3D1 && Giant")); > > from nfsserver/nfs_syscalls.c, line 570. > > As I understand the problem, kern/vfs_lookup.c:lookup() could > aquire additional locks on Giant, indicating this by GIANTHELD > flag in nd. All processing in nfsserver already goes with Giant held, > so, I just dropped that excessive locks after return from lookup. > System with patch applied survived smoke test (client did > du on mounted dir, patch was generated from exported fs, etc.). > nfsd eats no more than 25% of CPU (with INVARIANTS). > > Please, users who reported the problem and willing to help, > try the patch (generated against STABLE) and give the feedback. > [...] Hi Konstantin and others, I'm now running RELENG_6_1 as of Apr 30 04:00 UTC source + your patch. The nfsd is quite happy! After client's du finishes, it stays idle as expected (eats 0.00% CPU). Thank you very much. Regards, Rong-En Fan From owner-freebsd-stable@FreeBSD.ORG Thu May 25 20:55:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 615DB16A9D2 for ; Thu, 25 May 2006 20:55:26 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2726E43DA3 for ; Thu, 25 May 2006 20:52:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 09E721A4D9F; Thu, 25 May 2006 13:52:34 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6586451716; Thu, 25 May 2006 16:52:33 -0400 (EDT) Date: Thu, 25 May 2006 16:52:33 -0400 From: Kris Kennaway To: Konstantin Belousov Message-ID: <20060525205233.GA30137@xor.obsecurity.org> References: <001401c67f56$b02975e0$071872cf@Leadmon.local> <003001c67fae$27a88370$071872cf@Leadmon.local> <20060525051926.GB97976@xor.obsecurity.org> <20060525145809.GP54541@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <20060525145809.GP54541@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.1i Cc: Howard Leadmon , 'Rong-en Fan' , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: [patch, try 1] Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 25 May 2006 20:55:35 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2006 at 05:58:09PM +0300, Konstantin Belousov wrote: > +options QUOTA > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > options MD_ROOT # MD is a potential root device >=20 > After that, server machine easily panics on=20 >=20 > KASSERT(!(debug_mpsafenet =3D=3D 1 && mtx_owned(&Giant)), > ("nfssvc_nfsd(): debug.mpsafenet=3D1 && Giant")); >=20 > from nfsserver/nfs_syscalls.c, line 570. OK, I am also seeing this panic when I try and export a non-mpsafe filesystem (e.g. cd9660). I can't test the patch because my NFS server subsequently blew up :-( Kris --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdhkQWry0BWjoQKURAgqbAKDMmJ77y02Gsql089ORHDwmtTX6GgCfa7tz K2XiT4mE23T3jXrWx9aBGSM= =cxG+ -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 20:56:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 504F216C3B6 for ; Thu, 25 May 2006 20:56:23 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AB3243E48 for ; Thu, 25 May 2006 20:54:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 21B8C1A4EE7; Thu, 25 May 2006 13:54:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9B05E51716; Thu, 25 May 2006 16:54:14 -0400 (EDT) Date: Thu, 25 May 2006 16:54:14 -0400 From: Kris Kennaway To: "Arno J. Klaassen" Message-ID: <20060525205414.GC30137@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uh9ZiVrAOUUm9fzH" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? 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, 25 May 2006 20:56:29 -0000 --uh9ZiVrAOUUm9fzH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > Hello, >=20 > I get a very easy to reproduce panic on 6.1-STABLE : >=20 > /etc/periodic/weekly/310.locate panics with >=20 > panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated It looks like you are using a malloc-backed md and you do not have enough RAM to handle the size. Perhaps tmpmfs does not use swap backing, as it is supposed to? Kris --uh9ZiVrAOUUm9fzH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdhl1Wry0BWjoQKURAoidAKCmFCfxU1zyI9eWevyyvMeGnpsQhgCeKdJw ppcYcFoDPfwqRPAvFrv+cxI= =tmsg -----END PGP SIGNATURE----- --uh9ZiVrAOUUm9fzH-- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 21:49:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB04416CD6D for ; Thu, 25 May 2006 21:44:15 +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 AF5BF43D64 for ; Thu, 25 May 2006 21:44:08 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FjNcW-0000Vw-7L for freebsd-stable@freebsd.org; Thu, 25 May 2006 23:43:52 +0200 Received: from gw205.f5.com ([205.229.151.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 May 2006 23:43:52 +0200 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 25 May 2006 23:43:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: othermark Date: Thu, 25 May 2006 14:43:43 -0700 Lines: 36 Message-ID: References: <200605131413.17020.doconnor@gsoft.com.au> <20060513123030.GA32024@intserv.int1.b.intern> <200605231923.21263.doconnor@gsoft.com.au> <6.2.3.4.0.20060523095411.11c41c00@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: KNode/0.10.2 Sender: news Subject: Re: Odd RS232 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: Thu, 25 May 2006 21:49:16 -0000 Mike Tancsa wrote: > At 05:53 AM 23/05/2006, Daniel O'Connor wrote: >>On Saturday 13 May 2006 22:00, Holger Kipp wrote: >> >> > If you encounter silo overflows, you might need to increase >> > cp4ticks in sio.c, eg >> > - cp4ticks = speed / 10 / hz * 4; >> > + cp4ticks = speed / 10 / hz * 40; >> > and/or you might want to change hz from 1000 back to 100. >> >>OK, I'll try it. > > This fixes the overflows for me as well. I have a number of boxes out > in the field running with this local modification (40 vs 4). Without > it, I have problems running a PCI modem at speeds better than 9600 > without causing overflows. Yes, I had a laptop that exhibited this same problem and this change did fix it. I believe this is described in the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/51982 I had tried to work on this patch to provide a bounded sysctl for the multiplier, that way you could just set the hint on boot up in order to fix this problem. With a little trial and error you could find the lowest tick value that works for the interrupt load. One of these days I'll get back to figuring out all the places I need to add code to get that hint to work correctly. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); From owner-freebsd-stable@FreeBSD.ORG Thu May 25 23:31:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27B9D16B004 for ; Thu, 25 May 2006 23:31:29 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id A050243D4C for ; Thu, 25 May 2006 23:31:24 +0000 (GMT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.12.8) with ESMTP id k4PNVNDP094903; Thu, 25 May 2006 17:31:23 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.13.6/8.13.4) with ESMTP id k4PNVK01073863; Thu, 25 May 2006 17:31:20 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.13.6/8.13.6/Submit) id k4PNVKvd073860; Thu, 25 May 2006 17:31:20 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17526.15943.941001.738110@gromit.timing.com> Date: Thu, 25 May 2006 17:31:19 -0600 From: John E Hein To: Jacques In-Reply-To: <4474AF9D.6010408@xs4all.nl> References: <4474AF9D.6010408@xs4all.nl> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on Daffy.timing.com X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 troubles -- cannot "install buildworld" 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, 25 May 2006 23:31:32 -0000 Jacques wrote at 21:10 +0200 on May 24, 2006: > On an older i386 box (Pentium III), used as a workstation, we have been > running FreeBSD_4.x and 5.x for a long time without problems. > Now, using cvsup, we updated FreeBSD source from > 5.4p14 (default release=cvs tag=RELENG_5_4) to > 6.1 (default release=cvs tag=RELENG_6_1_0_RELEASE) > and updated the system according to the canonical method: > # cd /usr/src > # make buildworld > # make buildkernel > # make installkernel > # mergemaster -p > # shutdown > # cd /usr/src/ > # make installworld > > But that last step won't run. Output is: ... > -------------------------------------------------------------- > >>> Installing everything > -------------------------------------------------------------- > cd /usr/src; make -f Makefile.inc1 install > ===> share/info (install) > ===> include (install) > creating osreldate.h from newvers.sh > touch: not found > *** Error code 127 > > Stop in /usr/src/include. > *** Error code 1 http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TOUCH-NOT-FOUND osreldate.h should be created and up to date after buildworld. You can check that and compare it to the sources shown in src/include/Makefile osreldate.h: ${.CURDIR}/../sys/conf/newvers.sh \ ${.CURDIR}/../sys/sys/param.h \ ${.CURDIR}/Makefile Look to see if any of those sources are newer than the osreldate.h in your obj tree. You could just touch obj/usr/src/include/osreldate.h, but if that file has an incorrect timestamp, there are chances that other files do, too. The best solution would be to figure out why make thinks it needs to rebuild osreldate.h, fix what caused that if need be, and re-run your buildworld. In addition to timestamp problems, I've also seen this when you buildworld in one place, but installworld from somewhere else (usually due to mount path differences). Given the steps you outlined, this is not your problem. John From owner-freebsd-stable@FreeBSD.ORG Thu May 25 23:45:56 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBDE416ACDB for ; Thu, 25 May 2006 23:45:49 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd4mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C0C943D48 for ; Thu, 25 May 2006 23:45:49 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZU00HHPHZB2P30@l-daemon> for freebsd-stable@freebsd.org; Thu, 25 May 2006 17:45:11 -0600 (MDT) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd4mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IZU00DVCHZB57E0@pd4mr2so.prod.shaw.ca> for freebsd-stable@freebsd.org; Thu, 25 May 2006 17:45:11 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0IZU00LODHZASR30@l-daemon> for freebsd-stable@freebsd.org; Thu, 25 May 2006 17:45:11 -0600 (MDT) Received: (qmail 90393 invoked from network); Thu, 25 May 2006 23:45:10 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Thu, 25 May 2006 23:45:10 +0000 Date: Thu, 25 May 2006 16:45:10 -0700 From: Colin Percival In-reply-to: <20060525180013.GB67473@bloom.cse.buffalo.edu> To: freebsd-stable@freebsd.org Message-id: <44764186.6020400@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 References: <20060525180013.GB67473@bloom.cse.buffalo.edu> User-Agent: Thunderbird 1.5 (X11/20060416) Cc: Ken Smith Subject: Re: FreeBSD 5.5 Released 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, 25 May 2006 23:45:59 -0000 Ken Smith wrote: > BitTorrent > ---------- > > 5.5-RELEASE ISOs are not available via BitTorrent at this time. They > may be made available in the future on an on-demand basis. Thanks to ps, torrents are now available for 5.5-RELEASE: http://torrents.freebsd.org:8080/ Colin Percival From owner-freebsd-stable@FreeBSD.ORG Thu May 25 23:56:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F82016AA91 for ; Thu, 25 May 2006 23:56:13 +0000 (UTC) (envelope-from paul@xciv.org) Received: from mailhost.xciv.org (vantage.xciv.org [194.145.196.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id A45C343D46 for ; Thu, 25 May 2006 23:56:12 +0000 (GMT) (envelope-from paul@xciv.org) Received: from 82-43-154-1.cable.ubr03.newm.blueyonder.co.uk ([82.43.154.1] helo=tuscan.xciv.org) by mailhost.xciv.org with asmtp (TLSv1:AES256-SHA:256) id 1FjPgT-0008Ta-00; Fri, 26 May 2006 00:56:05 +0100 Received: from paul by tuscan.xciv.org with local id 1FjPex-0000O9-VL; Fri, 26 May 2006 00:54:32 +0100 Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Organization: iso.org.dod.internet References: <20919.1148565590@xciv.org> In-Reply-To: <20919.1148565590@xciv.org> From: paul@xciv.org (Paul Civati) X-Original-Newsgroups: xciv.lists.freebsd.stable To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii Message-Id: Sender: Paul Civati Date: Fri, 26 May 2006 00:54:31 +0100 X-XCIV-MailScanner: Found to be clean Cc: paul@xciv.org Subject: PXE boot images: 5.5 i386/amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: 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: Thu, 25 May 2006 23:56:13 -0000 In article <20919.1148565590@xciv.org>, paul@xciv.org (Paul Civati) writes: > For those of you wishing to PXE boot 6.1 RELEASE I have made some boot > images that work easily with pxelinux (syslinux) PXE set-up. [..] > Download and a quick pxelinux set-up howto: > > http://blog.rackred.com/2006/04/21/pxe-boot-freebsd-howto/ Seeing as 5.5 has just appeared I've made some 5.5 i386/amd64 images available too: http://blog.rackred.com/2006/04/18/pxe-boot-freebsd-5x/ -Paul- From owner-freebsd-stable@FreeBSD.ORG Thu May 25 23:56:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D2F16AC29 for ; Thu, 25 May 2006 23:56:15 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from mail.clickfox.com (cffw1.clickfox.com [72.16.213.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8089F43D46 for ; Thu, 25 May 2006 23:56:14 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __CP_URI_IN_BODY, __MIME_TEXT_ONLY' X-PMWin-Version: 2.5.1s, Antispam-Engine: 2.3.0.1, Antivirus-Engine: 2.34.1 thread-index: AcaAV44U/veTK7CaQ2qf169nJQ+lrA== Content-Class: urn:content-classes:message Importance: normal Priority: normal Received: from [10.20.30.156] ([72.16.213.34]) by mail.clickfox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 25 May 2006 20:01:35 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 Message-ID: <44764417.4030004@alumni.rice.edu> Date: Thu, 25 May 2006 19:56:07 -0400 From: "Jonathan Noack" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Kris Kennaway" References: <20060525205414.GC30137@xor.obsecurity.org> In-Reply-To: <20060525205414.GC30137@xor.obsecurity.org> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 May 2006 00:01:35.0959 (UTC) FILETIME=[8E012E70:01C68057] Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 23:56:16 -0000 Kris Kennaway wrote: > On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: >> I get a very easy to reproduce panic on 6.1-STABLE : >> >> /etc/periodic/weekly/310.locate panics with >> >> panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated > > It looks like you are using a malloc-backed md and you do not have > enough RAM to handle the size. Perhaps tmpmfs does not use swap > backing, as it is supposed to? If you look in /etc/defaults/rc.conf you'll note that malloc-backed is the default: tmpmfs_flags="-S -M" # Extra mdmfs options for the mfs /tmp I don't really understand why malloc-backed is the default as the performance difference between malloc- and swap-backed md's was resolved long ago: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/md/md.c#rev1.117 Ah, it looks like this was just for compatibility: http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf#rev1.259 I am currently running with the following in /etc/rc.conf and haven't experienced any problems: tmpmfs_flags="-S -o async" -Jonathan From owner-freebsd-stable@FreeBSD.ORG Fri May 26 00:02:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E623216B151 for ; Fri, 26 May 2006 00:02:05 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from mail.clickfox.com (cffw1.clickfox.com [72.16.213.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CB143D48 for ; Fri, 26 May 2006 00:02:05 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) X-PMWin-Spam: Gauge=IIIIIIII, Probability=8%, Report='__HAS_MSGID, __SANE_MSGID, __USER_AGENT, __MIME_VERSION, __CT, __CTYPE_CHARSET_QUOTED, __CT_TEXT_PLAIN, __CTE, __MIME_TEXT_ONLY' X-PMWin-Version: 2.5.1s, Antispam-Engine: 2.3.0.1, Antivirus-Engine: 2.34.1 thread-index: AcaAWGG7+1x6HFd4SNyCDvpDvXUTkw== Content-Class: urn:content-classes:message Importance: normal Priority: normal Received: from [10.20.30.156] ([72.16.213.34]) by mail.clickfox.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 25 May 2006 20:07:31 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 Message-ID: <4476457A.5050800@alumni.rice.edu> Date: Thu, 25 May 2006 20:02:02 -0400 From: "Jonathan Noack" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Jean-Marc Zucconi" References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> In-Reply-To: <200605251845.k4PIjdx7070553@freefall.freebsd.org> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 May 2006 00:07:31.0053 (UTC) FILETIME=[61A839D0:01C68058] Cc: freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 00:02:09 -0000 Jean-Marc Zucconi wrote: > # tar cf /dev/null X11R6.old > # archive_write_pax_header: 'x' header failed?! This can't happen. This seems to work fine here: [noackjr@optimator:/usr] $ uname -rm 6.1-RELEASE i386 [noackjr@optimator:/usr] $ tar --version bsdtar 1.02.023, libarchive 1.02.026 Copyright (C) 2003-2005 Tim Kientzle [noackjr@optimator:/usr] $ tar cf /dev/null X11R6 [noackjr@optimator:/usr] $ -Jonathan From owner-freebsd-stable@FreeBSD.ORG Fri May 26 00:49:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97CEB16CAD2 for ; Fri, 26 May 2006 00:43:46 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83A7E43D5F for ; Fri, 26 May 2006 00:43:44 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id ACE355880B; Thu, 25 May 2006 17:43:43 -0700 (PDT) Date: Thu, 25 May 2006 17:43:43 -0700 From: Paul Allen To: Jonathan Noack Message-ID: <20060526004343.GE28128@groat.ugcs.caltech.edu> References: <20060525205414.GC30137@xor.obsecurity.org> <44764417.4030004@alumni.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44764417.4030004@alumni.rice.edu> Sender: jd@ugcs.caltech.edu Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 00:49:24 -0000 >From Jonathan Noack , Thu, May 25, 2006 at 07:56:07PM -0400: > I am currently running with the following in /etc/rc.conf and haven't > experienced any problems: > tmpmfs_flags="-S -o async" Is there a way to accomplish this with an fstab entry? md /tmp mfs rw,async,-s1024m,-S no,I don't think so. But surely it would be better to just fixup the standard mount -t path to not call mount_mfs... From owner-freebsd-stable@FreeBSD.ORG Fri May 26 03:09:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FA4C16A4EB; Fri, 26 May 2006 03:09:02 +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 9F72E43D4C; Fri, 26 May 2006 03:09:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4Q38sAH034280; Thu, 25 May 2006 21:09:00 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44767146.30808@samsco.org> Date: Thu, 25 May 2006 21:08:54 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andriy Gapon References: <44745CF6.1040402@icyb.net.ua> In-Reply-To: <44745CF6.1040402@icyb.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: state of fs/udf 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, 26 May 2006 03:09:02 -0000 Andriy Gapon wrote: > It seems that UDF fs has been in not-well-supported state for a while > now. It seems that Scott Long, original author and maintainer, has moved > on to other more important (and, perhaps, interesting) things. > ("perhaps" - because RE does not seem to be too exciting on the first > glance) > > Meanwhile, there are several bugs still opened for UDF. Some of them are > pretty obvious, some with good patches, some not so trivial, some > unhelpful and some are mine :-) > I think the following PRs are good candidates for review and possible > inclusion into source: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77234 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92040 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84983 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90521 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/97786 > > Also, from our private conversations I know that Bruce Evans has even > more fixes for more problems and better fixes for some bugs described in > the above PRs. Those patches that I personally submitted do WorkForMe > (TM), but I think that Bruce has much better understanding of VFS stuff > and done much better job. > > Would some committer be so kind to adopt UDF, review the PRs and fix at > least the most obvious bugs before 6.2 ? > I personally promise to help with testing and discussing things. > Sorry I've been remiss. I'll look at these this weekend. Scott From owner-freebsd-stable@FreeBSD.ORG Fri May 26 03:21:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0558316A491 for ; Fri, 26 May 2006 03:21:10 +0000 (UTC) (envelope-from gcr+freebsd-stable@tharned.org) Received: from nc8000.tharned.org (rrcs-24-56-87-26.ma.biz.rr.com [24.56.87.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AB3F43D46 for ; Fri, 26 May 2006 03:21:09 +0000 (GMT) (envelope-from gcr+freebsd-stable@tharned.org) Received: from nc8000.tharned.org (gcr@localhost [127.0.0.1]) by nc8000.tharned.org (8.13.6/8.13.6) with ESMTP id k4Q3KjbL001803; Thu, 25 May 2006 22:20:45 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) Received: by nc8000.tharned.org (8.13.6/8.13.6/Submit) id k4Q3KjSG001802; Thu, 25 May 2006 22:20:45 -0500 (CDT) (envelope-from gcr+freebsd-stable@tharned.org) From: Greg Rivers To: freebsd-stable@freebsd.org Date: Thu, 25 May 2006 22:20:43 -0500 User-Agent: KMail/1.9.1 References: <44764417.4030004@alumni.rice.edu> <20060526004343.GE28128@groat.ugcs.caltech.edu> In-Reply-To: <20060526004343.GE28128@groat.ugcs.caltech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605252220.44739.gcr+freebsd-stable@tharned.org> Cc: Paul Allen , Kris Kennaway Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 03:21:12 -0000 On Thursday 25 May 2006 19:43, Paul Allen wrote: > >From Jonathan Noack , Thu, May 25, 2006 at > > 07:56:07PM -0400: I am currently running with the following in > > /etc/rc.conf and haven't experienced any problems: > > tmpmfs_flags="-S -o async" > > Is there a way to accomplish this with an fstab entry? > > md /tmp mfs rw,async,-s1024m,-S > > no,I don't think so. But surely it would be better to just fixup the > standard mount -t path to not call mount_mfs... > Actually there is a way. I too have not been satisfied with the tmpmfs features in rc, so for some time now I've simply created a hard link: cd /sbin && ln -f mdmfs mount_md and then used an entry like this in /etc/fstab: md /tmp md rw,async,-Sp1777,-s768M 0 0 This works great for me. A simple patch to mtree could make this hard link part of the base system. Nothing else is needed. -- Greg From owner-freebsd-stable@FreeBSD.ORG Fri May 26 08:37:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B008916A434 for ; Fri, 26 May 2006 08:37:55 +0000 (UTC) (envelope-from jmz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B4E643D4C; Fri, 26 May 2006 08:37:55 +0000 (GMT) (envelope-from jmz@FreeBSD.org) Received: from freefall.freebsd.org (jmz@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k4Q8btrg031488; Fri, 26 May 2006 08:37:55 GMT (envelope-from jmz@freefall.freebsd.org) Received: (from jmz@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k4Q8btpl031485; Fri, 26 May 2006 08:37:55 GMT (envelope-from jmz) Date: Fri, 26 May 2006 08:37:55 GMT Message-Id: <200605260837.k4Q8btpl031485@freefall.freebsd.org> From: Jean-Marc Zucconi To: In-Reply-To: <4476457A.5050800@alumni.rice.edu> References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> X-Mailer: Emacs 21.3.1 Cc: freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 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, 26 May 2006 08:37:59 -0000 >>>>> Jonathan Noack writes: > Jean-Marc Zucconi wrote: >> # tar cf /dev/null X11R6.old >> # archive_write_pax_header: 'x' header failed?! This can't happen. > This seems to work fine here: > [noackjr@optimator:/usr] $ uname -rm > 6.1-RELEASE i386 > [noackjr@optimator:/usr] $ tar --version > bsdtar 1.02.023, libarchive 1.02.026 > Copyright (C) 2003-2005 Tim Kientzle > [noackjr@optimator:/usr] $ tar cf /dev/null X11R6 > [noackjr@optimator:/usr] $ Sure, but the directories are not the same. I have narrowed the problem to a specific subdirectory and I think I have the explanation: -rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg Don't ask me why the date is wrong, this is really old stuff :-) On the other hand tar has no problem extracting it. If someone wants to debug it, the archive is available as http://people.freebsd.org/~jmz/a.tar Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger jmz@FreeBSD.org [KeyID: 400B38E9] From owner-freebsd-stable@FreeBSD.ORG Fri May 26 09:17:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D19216A447 for ; Fri, 26 May 2006 09:17:46 +0000 (UTC) (envelope-from dkirhlarov@oilspace.com) Received: from office.oilspace.com (ns2.oilspace.com [194.129.65.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 841FF43D4C for ; Fri, 26 May 2006 09:17:45 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dimma.mow.oilspace.com (hq.oilspace.com [81.222.156.185]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by office.oilspace.com (Postfix) with ESMTP id 2A947136CF4 for ; Fri, 26 May 2006 10:17:44 +0100 (BST) Received: from dimma.mow.oilspace.com (localhost [127.0.0.1]) by dimma.mow.oilspace.com (8.13.4/8.13.3) with ESMTP id k4Q9HhCf002541 for ; Fri, 26 May 2006 13:17:43 +0400 (MSD) (envelope-from dkirhlarov@localhost.oilspace.com) Received: (from dkirhlarov@localhost) by dimma.mow.oilspace.com (8.13.4/8.13.3/Submit) id k4Q9HhYd002540 for freebsd-stable@freebsd.org; Fri, 26 May 2006 13:17:43 +0400 (MSD) (envelope-from dkirhlarov) Date: Fri, 26 May 2006 13:17:43 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060526091742.GB785@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <001401c67f56$b02975e0$071872cf@Leadmon.local> <003001c67fae$27a88370$071872cf@Leadmon.local> <20060525051926.GB97976@xor.obsecurity.org> <20060525145809.GP54541@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060525145809.GP54541@deviant.kiev.zoral.com.ua> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 5.4-STABLE User-Agent: mutt-ng/devel-r581 (FreeBSD) Subject: Re: [patch, try 1] Re: Trouble with NFSd under 6.1-Stable, any ideas? 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, 26 May 2006 09:17:49 -0000 Hi! On Thu, May 25, 2006 at 05:58:09PM +0300, Konstantin Belousov wrote: > Please, users who reported the problem and willing to help, > try the patch (generated against STABLE) and give the feedback. I test it with RELENG_6 from 25 May 2006. It's work fine. Thank you. WBR -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.203 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Fri May 26 09:26:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A98B16A469 for ; Fri, 26 May 2006 09:26:00 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp105.biz.mail.re2.yahoo.com (smtp105.biz.mail.re2.yahoo.com [206.190.52.174]) by mx1.FreeBSD.org (Postfix) with SMTP id D8BC643D53 for ; Fri, 26 May 2006 09:25:57 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 43718 invoked from network); 26 May 2006 09:25:57 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp105.biz.mail.re2.yahoo.com with SMTP; 26 May 2006 09:25:57 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 3D5AF62F2; Fri, 26 May 2006 05:25:56 -0400 (EDT) X-Virus-Scanned: amavisd-new at noacks.org Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lMVpxexcNOho; Fri, 26 May 2006 05:25:55 -0400 (EDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id EFD2E62F8; Fri, 26 May 2006 05:25:54 -0400 (EDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by compgeek.noacks.org (8.13.6/8.13.6) with ESMTP id k4Q9PsoG039510; Fri, 26 May 2006 05:25:54 -0400 (EDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <4476C99C.50200@alumni.rice.edu> Date: Fri, 26 May 2006 05:25:48 -0400 From: Jonathan Noack User-Agent: Thunderbird 1.5.0.2 (X11/20060422) MIME-Version: 1.0 To: Jean-Marc Zucconi References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> In-Reply-To: <200605260837.k4Q8btpl031485@freefall.freebsd.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=991D8195; url=http://www.noacks.org/cert/noackjr.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig603C4494F12AB93176EFD33E" Cc: Tim Kientzle , freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 09:26:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig603C4494F12AB93176EFD33E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 05/26/06 04:37, Jean-Marc Zucconi wrote: >>>>>> Jonathan Noack writes: >=20 > > Jean-Marc Zucconi wrote: > >> # tar cf /dev/null X11R6.old > >> # archive_write_pax_header: 'x' header failed?! This can't happen.= >=20 > > This seems to work fine here: > > [noackjr@optimator:/usr] $ uname -rm > > 6.1-RELEASE i386 > > [noackjr@optimator:/usr] $ tar --version > > bsdtar 1.02.023, libarchive 1.02.026 > > Copyright (C) 2003-2005 Tim Kientzle > > [noackjr@optimator:/usr] $ tar cf /dev/null X11R6 > > [noackjr@optimator:/usr] $ >=20 > Sure, but the directories are not the same. As you provided no details in your original email, I was forced to assume that the problem was in the use of /dev/null (I used the X11R6 directory for fun). I was mistaken, but remember that not *all* of us can read your mind... :) > I have narrowed the problem to a specific subdirectory and I think I > have the explanation: >=20 > -rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg >=20 > Don't ask me why the date is wrong, this is really old stuff :-) >=20 > On the other hand tar has no problem extracting it. If someone wants > to debug it, the archive is available as > http://people.freebsd.org/~jmz/a.tar I see the same thing here. Touching supclkrd.prg to bring the date current makes the problem go away. Tim, any thoughts? -Jonathan --=20 Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195 --------------enig603C4494F12AB93176EFD33E 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.3 (FreeBSD) iD8DBQFEdsmiUFz01pkdgZURAiWgAJ9cl00ALqLtmcQJROKEKDxeJQFxNgCfbbY3 wFF/hxuSX3+L3oqP+ALXNV0= =1S+/ -----END PGP SIGNATURE----- --------------enig603C4494F12AB93176EFD33E-- From owner-freebsd-stable@FreeBSD.ORG Fri May 26 09:34:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3907116A438; Fri, 26 May 2006 09:34:49 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E1F743D53; Fri, 26 May 2006 09:34:48 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k4Q9Yl8d021305; Fri, 26 May 2006 11:34:47 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k4Q9Yh6G096204; Fri, 26 May 2006 11:34:43 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k4Q9YhXh096203; Fri, 26 May 2006 11:34:43 +0200 (CEST) (envelope-from ry93) Date: Fri, 26 May 2006 11:34:43 +0200 From: "Patrick M. Hausen" To: Jonathan Noack Message-ID: <20060526093443.GC94280@hugo10.ka.punkt.de> References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> <4476C99C.50200@alumni.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4476C99C.50200@alumni.rice.edu> User-Agent: Mutt/1.5.10i Cc: Tim Kientzle , freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 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, 26 May 2006 09:34:49 -0000 Hello! > > I have narrowed the problem to a specific subdirectory and I think I > > have the explanation: > > > > -rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg > > > > Don't ask me why the date is wrong, this is really old stuff :-) Since there cannot be a date before January 1st 1970, 0:00 on any Unix system, i guess there's something seriously broken here. Signed/unsigned overflow for the time_t value in question? Regards, Patrick M. Hausen -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Fri May 26 10:26:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67ED416A47B for ; Fri, 26 May 2006 10:26:40 +0000 (UTC) (envelope-from tbyte@otel.net) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAFE543D55 for ; Fri, 26 May 2006 10:26:37 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from dragon.otel.net ([212.36.8.135]) by mail.otel.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FjZWT-000Pm6-Ck; Fri, 26 May 2006 13:26:26 +0300 From: Iasen Kostov To: Kris Kennaway In-Reply-To: <20060525205414.GC30137@xor.obsecurity.org> References: <20060525205414.GC30137@xor.obsecurity.org> Content-Type: text/plain Date: Fri, 26 May 2006 13:26:24 +0300 Message-Id: <1148639184.78660.32.camel@DraGoN.OTEL.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 10:26:41 -0000 On Thu, 2006-05-25 at 16:54 -0400, Kris Kennaway wrote: > On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > > Hello, > > > > I get a very easy to reproduce panic on 6.1-STABLE : > > > > /etc/periodic/weekly/310.locate panics with > > > > panic: kmem_malloc(4096): kmem_map too small: 335544320 total allocated > > It looks like you are using a malloc-backed md and you do not have > enough RAM to handle the size. Perhaps tmpmfs does not use swap > backing, as it is supposed to? > > Kris First of all if there is not enough kmem (not just plain ram I think) kernel should not allow disk creation in first place, second - I think (although there could be some ... reason for that) it's stupid way to say "I don't have more kmem" by panicing :). Better way will be just to fail disk operation of that FS with "Disk is full" or something like that. At home I tried to raise kmem like that: "vm.kmem_size_max="1073741824" (I got 2G of RAM) (setting vm.kmem_size directly panices kernel at boot if I remember correctly). but for my surprise kernel panices at exact same allocated md disk space with the same panic as the original poster's. Is it possible that I should rise KVA_PAGES too ? And I don't think its documented anywhere (of course I've tried googling and it's always possible that I've missed something :). All this was on FreeBSD 6.0. From owner-freebsd-stable@FreeBSD.ORG Fri May 26 10:38:46 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F0216A433 for ; Fri, 26 May 2006 10:38:46 +0000 (UTC) (envelope-from nora@nxe.de) Received: from luka.nxe.de (luka.logivision.de [212.42.242.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id B957043D58 for ; Fri, 26 May 2006 10:38:44 +0000 (GMT) (envelope-from nora@nxe.de) Received: by localhost (8.13.6/nora-05.04.2006) with ESMTP from luka.nxe.de (localhost [127.0.0.1]) for (envelope-from nora@nxe.de) id k4QAcg4X000979; Fri, 26 May 2006 12:38:43 +0200 Received: by luka.nxe.de (8.13.6/LOCAL/nora-05.04.2006) for freebsd-stable@freebsd.org (envelope-from nora) id k4QAcgai000978; Fri, 26 May 2006 12:38:42 +0200 Apparently-To: freebsd-stable@freebsd.org Date: Fri, 26 May 2006 12:38:42 +0200 From: Nora Etukudo To: freebsd-stable@freebsd.org Message-ID: <20060526103842.GA32030@luka.nxe.de> References: <20919.1148565590@xciv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20919.1148565590@xciv.org> User-Agent: Mutt/1.5.5.1i Subject: Re: PXE boot images: 6.1 i386/amd64 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, 26 May 2006 10:39:08 -0000 Am 25. Mai 2006 um 14:59:50 +0100 schrieb Paul Civati: > For those of you wishing to PXE boot 6.1 RELEASE I have made some boot > images that work easily with pxelinux (syslinux) PXE set-up. Thank you very much! First time since several years I'm able again to install a FreeBSD at my site. My PXELINUX menu looks like this now $Id: mkpxe,v 1.7 2004/07/01 18:01:02 nora Exp $ m5 INST - Mandriva Limited Edition 2005 (10.2) m6 INST - Mandriva 2006.0 mc INST - Mandriva 2006.X (Cooker) f5 INST - Fedora Core 5 Installation debian INST - Debian Installer fbsd INST - FreeBSD 6.1-RELEASE dose WORK - DOS Werkzeug-Diskette gag TOOL - GAG Boot-Manager 4.6 mem TOOL - MEM86 Speichertest, http://www.memtest86.com/ a9 AUTO - Autoinstallation Mandrake Linux 9.2 a0 AUTO - AutoInstallation Mandrake Linux 10.0 a1 AUTO - AutoInstallation Mandrake Linux 10.1 a5 AUTO - AutoInstallation Mandriva Limited Edition 2005 (10.2) a6 AUTO - AutoInstallation 2006.0 ac AUTO - AutoInstallation 2006.X (Cooker) f5ks AUTO - Fedora Core 5 Kickstart-Installation boot: I didn't need the C/H/S options in the 'append'-line for your 6.1 image. Liebe Grüße, Nora. nora@sappho-net.de IM-NETZ Neue Medien, Berlin http://www.im-netz.de/ WWW von Frauen für Frauen, Hamburg http://www.w4w.net/ Lesbian Computer Networks, Helsinki http://www.sappho.net/ From owner-freebsd-stable@FreeBSD.ORG Fri May 26 10:58:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 759C716A42C for ; Fri, 26 May 2006 10:58:05 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACCDB43D5A for ; Fri, 26 May 2006 10:58:04 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail02.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k4QAw1SG024714 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 26 May 2006 20:58:02 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k4QAw1dD001630; Fri, 26 May 2006 20:58:01 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k4QAw11L001629; Fri, 26 May 2006 20:58:01 +1000 (EST) (envelope-from peter) Date: Fri, 26 May 2006 20:58:01 +1000 From: Peter Jeremy To: "Patrick M. Hausen" Message-ID: <20060526105801.GE744@turion.vk2pj.dyndns.org> References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> <4476C99C.50200@alumni.rice.edu> <20060526093443.GC94280@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060526093443.GC94280@hugo10.ka.punkt.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 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, 26 May 2006 10:58:05 -0000 On Fri, 2006-May-26 11:34:43 +0200, Patrick M. Hausen wrote: >> > -rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg >Since there cannot be a date before January 1st 1970, 0:00 on >any Unix system, i guess there's something seriously broken here. Why do you say that? time_t is signed so it can represent a date prior to 1970. In theory, a file prepared on an earlier computer could have been transferred onto a Unix system whilst retaining its original modification time. In this particular case, the date seems unlikely. That said, it is a perfectly valid date and it would be nice if tar could support it - though tar(5) states dates before the epoch are not handled consistently. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Fri May 26 11:15:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E5C216A423 for ; Fri, 26 May 2006 11:15:13 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B1DC43D4C for ; Fri, 26 May 2006 11:15:11 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 14122 invoked from network); 26 May 2006 11:15:09 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.135.176]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 26 May 2006 11:15:09 -0000 Date: Fri, 26 May 2006 13:15:02 +0200 From: Fabian Keil To: Iasen Kostov Message-ID: <20060526131502.2a2f984d@localhost> In-Reply-To: <1148639184.78660.32.camel@DraGoN.OTEL.net> References: <20060525205414.GC30137@xor.obsecurity.org> <1148639184.78660.32.camel@DraGoN.OTEL.net> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_jY6Le5k+toIzlxHvx5bAX/y"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 11:15:13 -0000 --Sig_jY6Le5k+toIzlxHvx5bAX/y Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Iasen Kostov wrote: > On Thu, 2006-05-25 at 16:54 -0400, Kris Kennaway wrote: > > On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > > > I get a very easy to reproduce panic on 6.1-STABLE : > > >=20 > > > /etc/periodic/weekly/310.locate panics with > > >=20 > > > panic: kmem_malloc(4096): kmem_map too small: 335544320 total > > > allocated > >=20 > > It looks like you are using a malloc-backed md and you do not have > > enough RAM to handle the size. Perhaps tmpmfs does not use swap > > backing, as it is supposed to? > First of all if there is not enough kmem (not just plain ram > I think) kernel should not allow disk creation in first place, second > - I think (although there could be some ... reason for that) it's > stupid way to say "I don't have more kmem" by panicing :). Better way > will be just to fail disk operation of that FS with "Disk is full" or > something like that. At home I tried to raise kmem like that: > "vm.kmem_size_max=3D"1073741824" (I got 2G of RAM) > (setting vm.kmem_size directly panices kernel at boot if I remember > correctly). >=20 > but for my surprise kernel panices at exact same allocated md disk > space with the same panic as the original poster's. Is it possible > that I should rise KVA_PAGES too ? And I don't think its documented > anywhere (of course I've tried googling and it's always possible that > I've missed something :). All this was on FreeBSD 6.0. man mdconfig mentions the problem: malloc Storage for this type of memory disk is allocated with malloc(9). This limits the size to the malloc bucket limit in the kernel. If the -o reserve option is not set, creating and filling a large malloc-backed memory disk is a very easy way to panic a system. Use a swap backed disk and the problem will disappear. Fabian --=20 http://www.fabiankeil.de/ --Sig_jY6Le5k+toIzlxHvx5bAX/y Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEduM7jV8GA4rMKUQRAqG2AKDBdtkz0Vjq2o/6U6vip51GMhE2XwCfdg0z 9clYMbd0gbW9TTPza0X7psk= =AYvJ -----END PGP SIGNATURE----- --Sig_jY6Le5k+toIzlxHvx5bAX/y-- From owner-freebsd-stable@FreeBSD.ORG Fri May 26 11:25:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5D5016A428 for ; Fri, 26 May 2006 11:25:22 +0000 (UTC) (envelope-from tbyte@otel.net) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F94243D82 for ; Fri, 26 May 2006 11:24:59 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from dragon.otel.net ([212.36.8.135]) by mail.otel.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FjaR8-0001HA-A8; Fri, 26 May 2006 14:24:58 +0300 From: Iasen Kostov To: Fabian Keil In-Reply-To: <20060526131502.2a2f984d@localhost> References: <20060525205414.GC30137@xor.obsecurity.org> <1148639184.78660.32.camel@DraGoN.OTEL.net> <20060526131502.2a2f984d@localhost> Content-Type: text/plain Date: Fri, 26 May 2006 14:24:57 +0300 Message-Id: <1148642697.78660.41.camel@DraGoN.OTEL.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 11:25:23 -0000 On Fri, 2006-05-26 at 13:15 +0200, Fabian Keil wrote: > Iasen Kostov wrote: > > > On Thu, 2006-05-25 at 16:54 -0400, Kris Kennaway wrote: > > > On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > > > > > I get a very easy to reproduce panic on 6.1-STABLE : > > > > > > > > /etc/periodic/weekly/310.locate panics with > > > > > > > > panic: kmem_malloc(4096): kmem_map too small: 335544320 total > > > > allocated > > > > > > It looks like you are using a malloc-backed md and you do not have > > > enough RAM to handle the size. Perhaps tmpmfs does not use swap > > > backing, as it is supposed to? > > > First of all if there is not enough kmem (not just plain ram > > I think) kernel should not allow disk creation in first place, second > > - I think (although there could be some ... reason for that) it's > > stupid way to say "I don't have more kmem" by panicing :). Better way > > will be just to fail disk operation of that FS with "Disk is full" or > > something like that. At home I tried to raise kmem like that: > > "vm.kmem_size_max="1073741824" (I got 2G of RAM) > > (setting vm.kmem_size directly panices kernel at boot if I remember > > correctly). > > > > but for my surprise kernel panices at exact same allocated md disk > > space with the same panic as the original poster's. Is it possible > > that I should rise KVA_PAGES too ? And I don't think its documented > > anywhere (of course I've tried googling and it's always possible that > > I've missed something :). All this was on FreeBSD 6.0. > > man mdconfig mentions the problem: > > malloc Storage for this type of memory disk is allocated with > malloc(9). This limits the size to the malloc bucket > limit in the kernel. If the -o reserve option is not > set, creating and filling a large malloc-backed memory > disk is a very easy way to panic a system. > > Use a swap backed disk and the problem will disappear. I ment KVA_PAGES (If it is the limit). But may be "malloc bucket limit" (which I don't realy understand what it means) has something to do with it ? But whatever is the cause I think it no good practice to leave such easy ways to panic the kernel unsecured/pached/fixed. And I wander why even when I set kmem_size_max to 1G kernel still panices around 350MB allocated md space ? I mean what is the real issue there ? Regards. From owner-freebsd-stable@FreeBSD.ORG Fri May 26 14:02:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D13FD16A42C for ; Fri, 26 May 2006 14:02:49 +0000 (UTC) (envelope-from sthalik@tehran.lain.pl) Received: from tehran.lain.pl (tehran.lain.pl [85.221.230.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D80343D5F for ; Fri, 26 May 2006 14:02:47 +0000 (GMT) (envelope-from sthalik@tehran.lain.pl) Received: from sthalik by tehran.lain.pl with local (envelope-from ) id 1Fjctp-000C9i-7j for freebsd-stable@freebsd.org; Fri, 26 May 2006 16:02:45 +0200 Date: Fri, 26 May 2006 16:02:45 +0200 From: Stanislaw Halik To: freebsd-stable@freebsd.org Message-ID: <20060526140245.GA46056@tehran.lain.pl> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060524115659.7895006a@localhost> <20060524020116.GB54710@xor.obsecurity.org> <20060526013105.22ee47ad@localhost> <20060525181528.59c423e7@localhost> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <20060525181528.59c423e7@localhost> X-PGP-Key: http://tehran.lain.pl/public.key User-Agent: Mutt/1.5.11 X-User: sthalik: Subject: Re: GELI issues ? (Re: Increase in panics under 6.1) 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, 26 May 2006 14:02:49 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2006, Fabian Keil wrote: >> Interestingly enough , i had some nasty issues todays on same laptop. >> I had 2 x 6 GB GELI vnodes, running mtree -K md5digest to compare >> contents. Disk IO was high as expected...but then it just died down >> (but the mtree hadnt finished).=20 >> (swap is also GELI) >> Any subsequent process trying to access the encrypted mount points >> simply stalled for as long as I cared to wait (10 minutes). The >> processes even stalled a shutdown -r.=20 > I'm not sure if it's related, but I lately see this behaviour on > NFS mounts if the server is not responding. > Doing cd /mnt/mydeadnfsmount/[tab for autocompletion] > is enough to render the current console unresponsive. Isn't that normal and desired for `hard' mounts? --=20 Kocia galeria - --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdwqEadU+vjT62TERAm5dAJ4+iM7G2I1GUqhSEGlLbVEFy9boCQCeKcbt y/yD/rDFeU0VVlg8DX7AA7E= =bNs0 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-stable@FreeBSD.ORG Fri May 26 17:24:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C60D116A54B; Fri, 26 May 2006 17:24:03 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24A8743D48; Fri, 26 May 2006 17:24:03 +0000 (GMT) (envelope-from tim@kientzle.com) Received: from [10.0.0.221] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id k4QHO0OZ083789; Fri, 26 May 2006 10:24:01 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <447739B0.2060806@kientzle.com> Date: Fri, 26 May 2006 10:24:00 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Patrick M. Hausen" References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> <4476C99C.50200@alumni.rice.edu> <20060526093443.GC94280@hugo10.ka.punkt.de> In-Reply-To: <20060526093443.GC94280@hugo10.ka.punkt.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Tim Kientzle , freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 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, 26 May 2006 17:24:04 -0000 Patrick M. Hausen wrote: >>>I have narrowed the problem to a specific subdirectory and I think I >>>have the explanation: >>> >>>-rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg Yes, libarchive in 6.1 has a broken assertion in the tar-writing code that causes it to (erroneously) reject files with very old dates. This is fixed in -CURRENT; I plan to MFC a bunch of fixes like this to 6-STABLE very soon. In the meantime, you can fix this by installing the most current libarchive from: http://people.freebsd.org/~kientzle/libarchive Or you can temporarily patch it by looking in src/lib/libarchive/archive_write_format_pax.c and changing the second call to __archive_write_format_header_ustar() so that the last argument is 0, not 1. (The 1 here enables the above-mentioned assertion checks.) Tim From owner-freebsd-stable@FreeBSD.ORG Fri May 26 21:03:03 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF7A316AAC0 for ; Fri, 26 May 2006 21:03:03 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8823443D4C for ; Fri, 26 May 2006 21:03:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6842A1A4DAE; Fri, 26 May 2006 14:03:03 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B9FB751559; Fri, 26 May 2006 17:03:02 -0400 (EDT) Date: Fri, 26 May 2006 17:03:02 -0400 From: Kris Kennaway To: Iasen Kostov Message-ID: <20060526210302.GA72999@xor.obsecurity.org> References: <20060525205414.GC30137@xor.obsecurity.org> <1148639184.78660.32.camel@DraGoN.OTEL.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline In-Reply-To: <1148639184.78660.32.camel@DraGoN.OTEL.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 21:03:05 -0000 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 26, 2006 at 01:26:24PM +0300, Iasen Kostov wrote: > On Thu, 2006-05-25 at 16:54 -0400, Kris Kennaway wrote: > > On Thu, May 25, 2006 at 06:01:30PM +0200, Arno J. Klaassen wrote: > > > Hello, > > >=20 > > > I get a very easy to reproduce panic on 6.1-STABLE : > > >=20 > > > /etc/periodic/weekly/310.locate panics with > > >=20 > > > panic: kmem_malloc(4096): kmem_map too small: 335544320 total alloc= ated > >=20 > > It looks like you are using a malloc-backed md and you do not have > > enough RAM to handle the size. Perhaps tmpmfs does not use swap > > backing, as it is supposed to? > >=20 > > Kris >=20 > First of all if there is not enough kmem (not just plain ram I think) > kernel should not allow disk creation in first place, second - I think > (although there could be some ... reason for that) it's stupid way to > say "I don't have more kmem" by panicing :). Better way will be just to > fail disk operation of that FS with "Disk is full" or something like > that. At home I tried to raise kmem like that: > "vm.kmem_size_max=3D"1073741824" (I got 2G of RAM) > (setting vm.kmem_size directly panices kernel at boot if I remember > correctly). >=20 > but for my surprise kernel panices at exact same allocated md disk space > with the same panic as the original poster's. Is it possible that I > should rise KVA_PAGES too ? And I don't think its documented anywhere > (of course I've tried googling and it's always possible that I've missed > something :). All this was on FreeBSD 6.0. It's documented in the mdconfig manpage including how to make it not panic. Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEd20GWry0BWjoQKURArPEAKC37ldmPhGJ6BQ64QLt1G5rwiGemwCeJ/Lr 2qpgRSSJ5yfysXkfi53Hbgw= =UE+M -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- From owner-freebsd-stable@FreeBSD.ORG Fri May 26 21:23:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 891DF16B9CA for ; Fri, 26 May 2006 21:23:08 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id C608843D6A for ; Fri, 26 May 2006 21:23:07 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.6/jtpda-5.4) with ESMTP id k4QLN66o000254 for ; Fri, 26 May 2006 23:23:06 +0200 (CEST) X-Ids: 166 Received: from heho.labo (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id k4QLN5j2063385 for ; Fri, 26 May 2006 23:23:05 +0200 (MEST) Received: (from arno@localhost) by heho.labo (8.13.3/8.13.1/Submit) id k4QLN5SM063382; Fri, 26 May 2006 23:23:05 +0200 (MEST) (envelope-from arno) Sender: arno@heho.snv.jussieu.fr To: freebsd-stable@freebsd.org References: From: "Arno J. Klaassen" Date: 26 May 2006 23:23:05 +0200 In-Reply-To: Message-ID: Lines: 9 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (shiva.jussieu.fr [134.157.0.166]); Fri, 26 May 2006 23:23:06 +0200 (CEST) X-Virus-Scanned: ClamAV 0.88.2/1486/Fri May 26 18:24:22 2006 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 447771BA.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Subject: Re: kmem leak in tmpmfs? 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, 26 May 2006 21:23:13 -0000 Hello, thanx to all who responded. Setting ' tmpmfs_flags="-S -o async" ' survived a nightly started locate script and a day of intensive 'normal' load. YMMV, but again, merci! Arno From owner-freebsd-stable@FreeBSD.ORG Sat May 27 01:17:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F30E16A96B for ; Sat, 27 May 2006 01:17:14 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDC7543D73 for ; Sat, 27 May 2006 01:17:07 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 2D184290C35 for ; Fri, 26 May 2006 22:17:01 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 36293-07 for ; Fri, 26 May 2006 22:17:06 -0300 (ADT) Received: from ganymede.hub.org (blk-7-151-244.eastlink.ca [71.7.151.244]) by hub.org (Postfix) with ESMTP id 96D92290C20 for ; Fri, 26 May 2006 22:17:00 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id DFF264A42B; Fri, 26 May 2006 22:17:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id DF2E24A3ED for ; Fri, 26 May 2006 22:17:10 -0300 (ADT) Date: Fri, 26 May 2006 22:17:10 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060526221620.P1114@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 6-STABLE on a Dual PIII server ... 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, 27 May 2006 01:17:18 -0000 ya, I still have 3 of these :) dmesg is showing something I've never seen before though: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 ACPI-0698: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [SB__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [ICNT] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [ACPI] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [LEDP] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [WUES] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [WUSE] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [CSB5] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [BIOS] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0698: *** Warning: Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) MADT: Forcing active-low polarity and level trigger for SCI Its an Intel motherboard ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sat May 27 02:56:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE60916A6FA for ; Sat, 27 May 2006 02:56:18 +0000 (UTC) (envelope-from wtd@pobox.com) Received: from as2.dm.egate.net (shell1.dm.egate.net [216.235.15.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 582F243D46 for ; Sat, 27 May 2006 02:56:18 +0000 (GMT) (envelope-from wtd@pobox.com) Received: by as2.dm.egate.net (Postfix, from userid 5562) id 39C884AEF; Fri, 26 May 2006 22:56:17 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by as2.dm.egate.net (Postfix) with ESMTP id 3036E4AE9 for ; Fri, 26 May 2006 22:56:17 -0400 (EDT) Date: Fri, 26 May 2006 22:56:17 -0400 (EDT) From: William Denton X-X-Sender: buff@as2.dm.egate.net To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: New mobo means USB problems 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, 27 May 2006 02:56:21 -0000 I recently got a new motherboard and now I have trouble with USB. I had no problems with my two USB drives before, but now a) I can't boot with my external USB hard drive connected and powered on, and b) moving files onto my Creative MP3 player causes that file system to hang. This second problem seems to be the same as was mentioned here on 5 May, at The new motherboard is an ASUS P5S800-VM and the BIOS is right up to date. It comes with USB 2.0 built in. I'm running FreeBSD 6.1-STABLE, and built a new world on 6 May, after I got this new mobo home. A healthy dmesg is at the bottom of this message. I saw some talk on mailing lists about ACPI being related to this kind of thing, so I tried booting without it (with "unset acpi_load" at the boot prompt) and it panicked, which wasn't helpful. a) Timeouts and failures when booting with external USB hard drive plugged in and turned on. I have a Maxtor drive in an external USB 2.0 enclosure. When it's connected and turned on, I cannot boot. The different bits from dmesg look like this: [same stuff as usual up to this point; see below] uhub3: 8 ports with 8 removable, self powered [ten-second or so delay, which I don't see on a normal boot] atapci1: port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef90-0xef9f,0xe480-0xe4ff irq 17 at device 5.0 on pci0 [continues as normal until ...] ad0: 39205MB at ata0-master UDMA133 ad1: 19092MB at ata0-slave UDMA100 acd0: CDRW at ata1-master UDMA33 pcm0: ac97 link rate calibration timed out after 1952041 us ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad0: TIMEOUT - FAILURE [something] ad1: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad1: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad1: TIMEOUT - FAILUER [someting] [repeats two more times] acd0: TIMEOUT - READ_BIG retrying (1 retry left) [acd0 TIMEOUTs and FAILURES repeated many times] I usually don't see that pcm0 warning. Finally after lots of errors I have to power cycle it. I can boot with the USB hard drive turned off, and then turn it on and mount it normally, in which case I see: umass0: vendor 0x04b4 USB Mass Storage Device, rev 2.00/2.40, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) I have no trouble moving files on or off the drive after that, so it's annoying that I have to worry about it when I boot, but it's still usable. b) USB Creative Muvo TX FM hangs: BBB reset failed, TIMEOUT I have an MP3 player that has a 1 GB flash drive, and it is no longer usable on this box. Here's what it is: umass0: CREATIVE MuVo TX FM, rev 2.00/11.91, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 993MB (2035456 512 byte sectors: 64H 32S/T 993C) When I mount the file and moves some files onto it, after a couple of files, it stops and hangs. I can't access the file system any more, and get these errors: umass0: BBB reset failed, TIMEOUT umass0: BBB bulk-in clear stall failed, TIMEOUT umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR umass0: BBB reset failed, IOERROR umass0: BBB bulk-in clear stall failed, IOERROR umass0: BBB bulk-out clear stall failed, IOERROR That continues on and I have to reboot, at which point I see scores of errors like this: g_vfs_done():da0[WRITE(offset=995237848, length=4096)]error = 5 Then I get more BBB reset failed messages, and I have to power cycle. As I said, I used to be able to use this just fine with my old mobo, and my other FreeBSD 6.1-STABLE box can handle it without trouble. Bill -- William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org Copyright (c) 1992-2006 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 6.1-STABLE #4: Sat May 6 22:18:56 EDT 2006 buff@sherlock.miskatonic.org:/usr/obj/usr/src/sys/SHERLOCK ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2653.54-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf49 Stepping = 9 Features=0xbfebfbff Features2=0x651d> AMD Features=0x20000000 AMD Features2=0x1 real memory = 1576730624 (1503 MB) avail memory = 1535930368 (1464 MB) ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.5 on pci0 ata0: on atapci0 ata1: on atapci0 pcm0: port 0xe800-0xe8ff,0xec00-0xec7f irq 18 at device 2.7 on pci0 pcm0: ohci0: mem 0xdfff4000-0xdfff4fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xdfff5000-0xdfff5fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ohci2: mem 0xdfff6000-0xdfff6fff irq 22 at device 3.2 on pci0 ohci2: [GIANT-LOCKED] usb2: OHCI version 1.0, legacy support usb2: on ohci2 usb2: USB revision 1.0 uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdfff7000-0xdfff7fff irq 23 at device 3.3 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered atapci1: port 0xeff0-0xeff7,0xefe4-0xefe7,0xefa8-0xefaf,0xefe0-0xefe3,0xef90-0xef9f,0xe480-0xe4ff irq 17 at device 5.0 on pci0 ata2: on atapci1 ata3: on atapci1 rl0: port 0xe000-0xe0ff mem 0xdfff3800-0xdfff38ff irq 19 at device 11.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:15:f2:5b:d3:d5 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: flags 0x200 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77b 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 ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PRINTER PJL,HBP plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 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 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff 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 Timecounter "TSC" frequency 2653536680 Hz quality 800 Timecounters tick every 1.000 msec ad0: 39205MB at ata0-master UDMA133 ad1: 19092MB at ata0-slave UDMA100 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a WARNING: /disk2 was not properly dismounted rl0: link state changed to UP From owner-freebsd-stable@FreeBSD.ORG Sat May 27 08:32:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E19F516A68D for ; Sat, 27 May 2006 08:32:40 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E0BA43D48 for ; Sat, 27 May 2006 08:32:39 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k4R8WdtY000124 for ; Sat, 27 May 2006 10:32:39 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k4R8Wc6G030918; Sat, 27 May 2006 10:32:38 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k4R8WcN1030917; Sat, 27 May 2006 10:32:38 +0200 (CEST) (envelope-from ry93) Date: Sat, 27 May 2006 10:32:38 +0200 From: "Patrick M. Hausen" To: Peter Jeremy Message-ID: <20060527083238.GA30554@hugo10.ka.punkt.de> References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> <4476C99C.50200@alumni.rice.edu> <20060526093443.GC94280@hugo10.ka.punkt.de> <20060526105801.GE744@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060526105801.GE744@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org Subject: Re: (bsd)tar is broken on 6.1 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, 27 May 2006 08:32:45 -0000 Hi, all! On Fri, May 26, 2006 at 08:58:01PM +1000, Peter Jeremy wrote: > On Fri, 2006-May-26 11:34:43 +0200, Patrick M. Hausen wrote: > >> > -rw-r--r-- 1 jmz jmz 4312 Apr 16 1947 supclkrd.prg > > >Since there cannot be a date before January 1st 1970, 0:00 on > >any Unix system, i guess there's something seriously broken here. > > Why do you say that? time_t is signed so it can represent a date > prior to 1970. In theory, a file prepared on an earlier computer > could have been transferred onto a Unix system whilst retaining > its original modification time. If I'm not mistaken, the signedness of time_t is merely historical. time_t predates explicitely unsigned integer data types in C. The historical definition seems to have been "long". Dates before the Epoch are undefined. I mean, which part of "seconds since the Epoch" implies time values _before_ the Epoch? You are not supposed to do calculations subtractions with time_t but use difftime(), for example. POSIX.1-1990. Section 2.2.2.77: seconds since the Epoch "If the year < 1970 or the value [of seconds since the Epoch] is negative, the relationship is undefined. If the year >= 1970 and the value is non-negative, the value is related to a Coordinated Universal Time name ..." Regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Sat May 27 08:54:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0966616A470 for ; Sat, 27 May 2006 08:54:45 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CA3243D48 for ; Sat, 27 May 2006 08:54:43 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 18893 invoked from network); 27 May 2006 08:54:42 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.149.180]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 27 May 2006 08:54:42 -0000 Date: Sat, 27 May 2006 10:54:31 +0200 From: Fabian Keil To: Stanislaw Halik Message-ID: <20060527105431.534bce7b@localhost> In-Reply-To: <20060526140245.GA46056@tehran.lain.pl> References: <20060524115659.7895006a@localhost> <20060524020116.GB54710@xor.obsecurity.org> <20060526013105.22ee47ad@localhost> <20060525181528.59c423e7@localhost> <20060526140245.GA46056@tehran.lain.pl> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/aTfjuX4bBgG0us+nLbfDCy"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org Subject: Re: GELI issues ? (Re: Increase in panics under 6.1) 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, 27 May 2006 08:55:02 -0000 --Sig_/aTfjuX4bBgG0us+nLbfDCy Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Stanislaw Halik wrote: > On Thu, May 25, 2006, Fabian Keil wrote: > >> Interestingly enough , i had some nasty issues todays on same > >> laptop. I had 2 x 6 GB GELI vnodes, running mtree -K md5digest to > >> compare contents. Disk IO was high as expected...but then it just > >> died down (but the mtree hadnt finished).=20 > >> (swap is also GELI) >=20 > >> Any subsequent process trying to access the encrypted mount points > >> simply stalled for as long as I cared to wait (10 minutes). The > >> processes even stalled a shutdown -r.=20 > > I'm not sure if it's related, but I lately see this behaviour on > > NFS mounts if the server is not responding. >=20 > > Doing cd /mnt/mydeadnfsmount/[tab for autocompletion] > > is enough to render the current console unresponsive. >=20 > Isn't that normal and desired for `hard' mounts? Now that you mention it I guess your right. It totally forgot that hard mounts are the default. Fabian --=20 http://www.fabiankeil.de/ --Sig_/aTfjuX4bBgG0us+nLbfDCy Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEeBPPjV8GA4rMKUQRAs9tAJ0TgZGFoMF2T3bCyeUyNmzeKkhhvACgjIy4 FKNCEvzLYjHSblVc8YWx7iE= =UR3p -----END PGP SIGNATURE----- --Sig_/aTfjuX4bBgG0us+nLbfDCy-- From owner-freebsd-stable@FreeBSD.ORG Sat May 27 08:57:23 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6571D16B2F9 for ; Sat, 27 May 2006 08:57:23 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9A1B43D70 for ; Sat, 27 May 2006 08:57:18 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id k4R8vF603633 for ; Sat, 27 May 2006 18:57:15 +1000 (EST) Date: Sat, 27 May 2006 18:57:14 +1000 (EST) From: Dave Horsfall To: FreeBSD STABLE list In-Reply-To: <20060527083238.GA30554@hugo10.ka.punkt.de> Message-ID: References: <200605251845.k4PIjdx7070553@freefall.freebsd.org> <4476457A.5050800@alumni.rice.edu> <200605260837.k4Q8btpl031485@freefall.freebsd.org> <4476C99C.50200@alumni.rice.edu> <20060526093443.GC94280@hugo10.ka.punkt.de> <20060526105801.GE744@turion.vk2pj.dyndns.org> <20060527083238.GA30554@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: (bsd)tar is broken on 6.1 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, 27 May 2006 08:57:31 -0000 On Sat, 27 May 2006, Patrick M. Hausen wrote: > If I'm not mistaken, the signedness of time_t is merely historical. > time_t predates explicitely unsigned integer data types in C. > The historical definition seems to have been "long". Actually it was int[2] - see line 0213 of the Lions Book. Or I could get really keen and dig out my old Edition 5 manual... The C compiler didn't grok "long" in those days. -- Dave