From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 00:31: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 40FA816A407 for ; Sun, 10 Sep 2006 00:31:42 +0000 (UTC) (envelope-from umbilical.blisters@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75D0B43D46 for ; Sun, 10 Sep 2006 00:31:41 +0000 (GMT) (envelope-from umbilical.blisters@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1383322pye for ; Sat, 09 Sep 2006 17:31:41 -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=lv5u88RjA+DjBPdFyJ7hY1xWFoRoRdYoy0VVtlKRUCi9/5pMdlSGTEJIOtCHOP304Wbz5qf16Oxpw0edBQ4cTsgVPtTt2KENk8Nz2tJkkPH8s6wcm5bb259J32uCrY6hUImSEQlLpk6tERpgda68eacLPa4xXC6jS8oyCJ8dGro= Received: by 10.35.54.1 with SMTP id g1mr5804844pyk; Sat, 09 Sep 2006 17:31:40 -0700 (PDT) Received: by 10.35.126.16 with HTTP; Sat, 9 Sep 2006 17:31:40 -0700 (PDT) Message-ID: <40c4bb930609091731q81d4e4agb0418e3b60d519c1@mail.gmail.com> Date: Sat, 9 Sep 2006 19:31:40 -0500 From: "Alex Salazar" To: "Matthew Jacob" In-Reply-To: <7579f7fb0609091127o2962d4dcxa0d658cd09899156@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> <40c4bb930609081046m1e94266al6be8873e2149c607@mail.gmail.com> <7579f7fb0609091125j7f8abcebq3075d4bd474f21d@mail.gmail.com> <7579f7fb0609091127o2962d4dcxa0d658cd09899156@mail.gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 00:31:42 -0000 On 9/9/06, Matthew Jacob wrote: > Oops- mangled reply. > > > > On 9/9/06, Matthew Jacob wrote: > > > > > > is gone, but a new error message appears as often as the former, > > > and under the same circumstances: > > > > > > > mpt0: QUEUE_FULL: Bus 0x00 Target 0x00 Depth 128 > > > > Do you see these all the time? If so I'll have to connect up some > logic to take and shut down openings to match the Depth field- > although this is a step I've been resisting. > If by "all the time" you mean every time certain disk operations are performed (tarball extraction, files download...), then, yes. All the time. Otherwise, no error shows up. > > Insofar as the Error 22- that's normal to see those for verbose > booting. They should be more informative as to why those are > occurring. > You're right. Those messages are evident only while verbose booting, so, I'm not really concerned about them but the huge delay on booting (up to 18 min) they represent on 6-STABLE. -- Alex From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 01:59: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 13AD116A407 for ; Sun, 10 Sep 2006 01:59:16 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8EB143D46 for ; Sun, 10 Sep 2006 01:59:15 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 38188E601F for ; Sun, 10 Sep 2006 01:59:14 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.8/8.13.6) with ESMTP id k8A1xAIn089481 for ; Sun, 10 Sep 2006 11:59:11 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> To: freebsd-stable@freebsd.org From: Mark Andrews Mail-Followup-To: freebsd-stable@freebsd.org In-reply-to: Your message of "Sat, 09 Sep 2006 13:28:31 EST." <20060909182831.GA32004@FS.denninger.net> Date: Sun, 10 Sep 2006 11:59:10 +1000 Sender: Mark_Andrews@isc.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 01:59:16 -0000 > Yeah, -STABLE is what you should run if you want stable code, right? No. STABLE means STABLE API. If you want stable code you run releases. Between releases stable can become unstable. Think of stable as permanent BETA code. Changes have passed the first level of testing in current which is permanent ALPHA code. Most of the time beta code is perfectly fine to run but occasionally things will go wrong. The point of BETA code is to catch those errors that escape detection in the ALPHA stage before they make it into a release. That is done by having a wider diversity of clients run the BETA code. Occasionally you have bugs that make it through both the ALPHA and BETA stages. Mark -- ISC Training! October 16-20, 2006, in the San Francisco Bay Area, covering topics from DNS to DHCP. Email training@isc.org. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 02:16: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 2836016A403 for ; Sun, 10 Sep 2006 02:16:31 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9FE043D45 for ; Sun, 10 Sep 2006 02:16:30 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 06DF3291AFE; Sat, 9 Sep 2006 23:16:27 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 30942-07; Sun, 10 Sep 2006 02:16:29 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 6FC43290C74; Sat, 9 Sep 2006 23:16:26 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 8943833D53; Sat, 9 Sep 2006 23:16:29 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 887B133C25; Sat, 9 Sep 2006 23:16:29 -0300 (ADT) Date: Sat, 9 Sep 2006 23:16:29 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Mark Andrews In-Reply-To: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> Message-ID: <20060909231448.E1031@ganymede.hub.org> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 02:16:31 -0000 This should be documented somewhere clearly then, as my understanding was that -STABLE meant that anything MFCd back to it *was* tested and deemed stable ... and yes, I do run stable, and yes, I do expect to hit the occasional 'oopses', but "blantant and obvious bugs due to insufficient testing", IMHO, doesn't classify as an 'oops' .... On Sun, 10 Sep 2006, Mark Andrews wrote: > >> Yeah, -STABLE is what you should run if you want stable code, right? > > No. STABLE means STABLE API. > > If you want stable code you run releases. Between releases > stable can become unstable. Think of stable as permanent > BETA code. Changes have passed the first level of testing > in current which is permanent ALPHA code. > > Most of the time beta code is perfectly fine to run but > occasionally things will go wrong. The point of BETA code > is to catch those errors that escape detection in the ALPHA > stage before they make it into a release. That is done by > having a wider diversity of clients run the BETA code. > > Occasionally you have bugs that make it through both the ALPHA > and BETA stages. > > Mark > -- > ISC Training! October 16-20, 2006, in the San Francisco Bay Area, > covering topics from DNS to DHCP. Email training@isc.org. > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org > _______________________________________________ > 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" > ---- 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 Sun Sep 10 02:36: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 D075F16A403; Sun, 10 Sep 2006 02:36:19 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9545A43D46; Sun, 10 Sep 2006 02:36:19 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 4893C1113; Sat, 9 Sep 2006 21:36:19 -0500 (CDT) Date: Sat, 9 Sep 2006 21:36:19 -0500 To: "Marc G. Fournier" Message-ID: <20060910023619.GA32206@soaustin.net> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060909231448.E1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060909231448.E1031@ganymede.hub.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: Mark Andrews , freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 02:36:19 -0000 On Sat, Sep 09, 2006 at 11:16:29PM -0300, Marc G. Fournier wrote: > This should be documented somewhere clearly then, as my understanding was > that -STABLE meant that anything MFCd back to it *was* tested and deemed > stable ... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/decision-points.html > but "blantant and obvious bugs due to insufficient testing", IMHO, doesn't > classify as an 'oops' .... You've already made this point -- 3 times. What would you like us to do now, punish the committer? Simply reiterating your criticism and unhappiness isn't going to do anything to fix this problem (for which, of course, a fix has already been made), or the next one(s) either. It was an error, it's been fixed, may I suggest we move on to the next bug? mcl From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 02:40: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 85A3F16A40F; Sun, 10 Sep 2006 02:40:49 +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 44E0943D45; Sun, 10 Sep 2006 02:40:49 +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 277B81A3C1F; Sat, 9 Sep 2006 19:40:49 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9A0B05148C; Sat, 9 Sep 2006 22:40:47 -0400 (EDT) Date: Sat, 9 Sep 2006 22:40:47 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060910024047.GA73879@xor.obsecurity.org> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060909231448.E1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20060909231448.E1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i Cc: Mark Andrews , freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 02:40:49 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 09, 2006 at 11:16:29PM -0300, Marc G. Fournier wrote: >=20 > This should be documented somewhere clearly then, as my understanding was= =20 > that -STABLE meant that anything MFCd back to it *was* tested and deemed= =20 > stable ... You mean like in the FreeBSD handbook? It's not anyone else's fault if you haven't read the documentation. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.= html Kris --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFA3suWry0BWjoQKURAszfAJ9ToOOr8K3tD4SajX6mVqWgPGQnWQCffnQG gQ8XUBzHXESlhhNHjQbI2uw= =Ehyn -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 02:42: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 5AF8216A407 for ; Sun, 10 Sep 2006 02:42:28 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id D10D543D49 for ; Sun, 10 Sep 2006 02:42:27 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1151353wxd for ; Sat, 09 Sep 2006 19:42:27 -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=SgTKCZSte/rTqwm8nyqFzxpnqo4HlZaOsnSGkg4zN3nfMVdgoGSdcADueFWTLZvSzLvw3l3aGoEpwjxZGdzctIH5r/L1+EwVrLl/4eNktenQHTg/pdruS8p7Ox3U4Y2aDhPBaXufst7TPN2E67O6bZ3l4KVwXf+MUWwpU1R4ubs= Received: by 10.90.118.12 with SMTP id q12mr1290041agc; Sat, 09 Sep 2006 19:42:27 -0700 (PDT) Received: by 10.90.70.6 with HTTP; Sat, 9 Sep 2006 19:42:26 -0700 (PDT) Message-ID: <7579f7fb0609091942p2f52d710v3daa0ccb291e67e4@mail.gmail.com> Date: Sat, 9 Sep 2006 19:42:26 -0700 From: "Matthew Jacob" To: "Alex Salazar" In-Reply-To: <40c4bb930609091731q81d4e4agb0418e3b60d519c1@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> <40c4bb930609081046m1e94266al6be8873e2149c607@mail.gmail.com> <7579f7fb0609091125j7f8abcebq3075d4bd474f21d@mail.gmail.com> <7579f7fb0609091127o2962d4dcxa0d658cd09899156@mail.gmail.com> <40c4bb930609091731q81d4e4agb0418e3b60d519c1@mail.gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 02:42:28 -0000 > If by "all the time" you mean every time certain disk operations > are performed (tarball extraction, files download...), then, yes. > All the time. Otherwise, no error shows up. Hmm. Okay. I'll work on this. > > > > > > Insofar as the Error 22- that's normal to see those for verbose > > booting. They should be more informative as to why those are > > occurring. > > > > You're right. Those messages are evident only while verbose booting, > so, I'm not really concerned about them but the huge delay on booting > (up to 18 min) they represent on 6-STABLE. > Hmm. I'll have to dig back thru the mail here but I don't get this. From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 03:53: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 8D47916A47B; Sun, 10 Sep 2006 03:53:57 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD0A43D46; Sun, 10 Sep 2006 03:53:56 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 66EAF291AFE; Sun, 10 Sep 2006 00:53:55 -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 28350-05; Sun, 10 Sep 2006 00:54:07 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id A7ACE290C74; Sun, 10 Sep 2006 00:53:54 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id B6477344CD; Sun, 10 Sep 2006 00:53:54 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id B57CB33D53; Sun, 10 Sep 2006 00:53:54 -0300 (ADT) Date: Sun, 10 Sep 2006 00:53:54 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Mark Linimon In-Reply-To: <20060910023619.GA32206@soaustin.net> Message-ID: <20060910005241.O1031@ganymede.hub.org> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060909231448.E1031@ganymede.hub.org> <20060910023619.GA32206@soaustin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Mark Andrews , "Marc G. Fournier" Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 03:53:58 -0000 On Sat, 9 Sep 2006, Mark Linimon wrote: > On Sat, Sep 09, 2006 at 11:16:29PM -0300, Marc G. Fournier wrote: >> This should be documented somewhere clearly then, as my understanding was >> that -STABLE meant that anything MFCd back to it *was* tested and deemed >> stable ... > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/decision-points.html > >> but "blantant and obvious bugs due to insufficient testing", IMHO, doesn't >> classify as an 'oops' .... > > You've already made this point -- 3 times. What would you like us to do > now, punish the committer? Huh? My first post on this thread was in defense of MFCng into STABLE and acknowledging that 'mistakes happen', and then this one ... ---- 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 Sun Sep 10 03:55:47 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 226A016A403; Sun, 10 Sep 2006 03:55:47 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8967B43D46; Sun, 10 Sep 2006 03:55:44 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 54201291AFE; Sun, 10 Sep 2006 00:55:43 -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 21731-09; Sun, 10 Sep 2006 00:55:55 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 9F0E9290C74; Sun, 10 Sep 2006 00:55:42 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id D3927354CD; Sun, 10 Sep 2006 00:55:42 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D2C1833D53; Sun, 10 Sep 2006 00:55:42 -0300 (ADT) Date: Sun, 10 Sep 2006 00:55:42 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Kris Kennaway In-Reply-To: <20060910024047.GA73879@xor.obsecurity.org> Message-ID: <20060910005505.H1031@ganymede.hub.org> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060909231448.E1031@ganymede.hub.org> <20060910024047.GA73879@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Mark Andrews , "Marc G. Fournier" Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 03:55:47 -0000 On Sat, 9 Sep 2006, Kris Kennaway wrote: > On Sat, Sep 09, 2006 at 11:16:29PM -0300, Marc G. Fournier wrote: >> >> This should be documented somewhere clearly then, as my understanding was >> that -STABLE meant that anything MFCd back to it *was* tested and deemed >> stable ... > > You mean like in the FreeBSD handbook? It's not anyone else's fault > if you haven't read the documentation. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html I swear, the last time I searched for a definition of STABLE vs CURRENT/HEAD, that wsan't there ... but, granted, that was a very very long time ago ... ---- 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 Sun Sep 10 04:08: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 C504B16A407; Sun, 10 Sep 2006 04:08:39 +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 7D7BF43D46; Sun, 10 Sep 2006 04:08:39 +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 4A24F1A3C1F; Sat, 9 Sep 2006 21:08:39 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 73F8B5148C; Sun, 10 Sep 2006 00:08:34 -0400 (EDT) Date: Sun, 10 Sep 2006 00:08:34 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060910040834.GA75404@xor.obsecurity.org> References: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060909231448.E1031@ganymede.hub.org> <20060910024047.GA73879@xor.obsecurity.org> <20060910005505.H1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <20060910005505.H1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i Cc: Mark Andrews , freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 04:08:41 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 12:55:42AM -0300, Marc G. Fournier wrote: > On Sat, 9 Sep 2006, Kris Kennaway wrote: >=20 > >On Sat, Sep 09, 2006 at 11:16:29PM -0300, Marc G. Fournier wrote: > >> > >>This should be documented somewhere clearly then, as my understanding w= as > >>that -STABLE meant that anything MFCd back to it *was* tested and deemed > >>stable ... > > > >You mean like in the FreeBSD handbook? It's not anyone else's fault > >if you haven't read the documentation. > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stabl= e.html >=20 > I swear, the last time I searched for a definition of STABLE vs=20 > CURRENT/HEAD, that wsan't there ... but, granted, that was a very very=20 > long time ago ... Well, now you know. Might be a good idea to reread the handbook and other documentation to bring yourself up to date on anything else you might have missed too. Kris --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFA4/BWry0BWjoQKURAhjaAJ9giikk23NfqZKvR6QtYpRmwF2SwgCfdH/L +3209rwivvoEBnR8Aqgyfsk= =MYbA -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 04:28: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 50B7616A403 for ; Sun, 10 Sep 2006 04:28:14 +0000 (UTC) (envelope-from umbilical.blisters@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65F8543D49 for ; Sun, 10 Sep 2006 04:28:13 +0000 (GMT) (envelope-from umbilical.blisters@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1445689pye for ; Sat, 09 Sep 2006 21:28:12 -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=tWdjFBEQVjzMw0MFvTfOvq3uHu3K+trV4kMHFDXXVjlJFI0Q6dJPM6yHIbHeggXzxKaeQMo7pwRxXR0Yx7366cChrSHkMBpRf1T9+EhPvPXV8l0O25gkRjeNbfhVM9uzvcDVQqD92TU3fDVifNr03d8gdR7whRKDiJpinT1mDQ0= Received: by 10.35.50.1 with SMTP id c1mr6122028pyk; Sat, 09 Sep 2006 21:28:12 -0700 (PDT) Received: by 10.35.126.16 with HTTP; Sat, 9 Sep 2006 21:28:12 -0700 (PDT) Message-ID: <40c4bb930609092128l104cc3femb53e810b3f719dc2@mail.gmail.com> Date: Sat, 9 Sep 2006 23:28:12 -0500 From: "Alex Salazar" To: "Matthew Jacob" In-Reply-To: <7579f7fb0609091942p2f52d710v3daa0ccb291e67e4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> <40c4bb930609081046m1e94266al6be8873e2149c607@mail.gmail.com> <7579f7fb0609091125j7f8abcebq3075d4bd474f21d@mail.gmail.com> <7579f7fb0609091127o2962d4dcxa0d658cd09899156@mail.gmail.com> <40c4bb930609091731q81d4e4agb0418e3b60d519c1@mail.gmail.com> <7579f7fb0609091942p2f52d710v3daa0ccb291e67e4@mail.gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 04:28:15 -0000 On 9/9/06, Matthew Jacob wrote: > > > > > > Insofar as the Error 22- that's normal to see those for verbose > > > booting. They should be more informative as to why those are > > > occurring. > > > > > > > You're right. Those messages are evident only while verbose booting, > > so, I'm not really concerned about them but the huge delay on booting > > (up to 18 min) they represent on 6-STABLE. > > > > Hmm. I'll have to dig back thru the mail here but I don't get this. > On 6-STABLE, those "Error 22" messages on boot, show up too slowly, one character at a time, at about one line every 30 seconds, which delays the boot process on almost 20 (twenty) minutes. After that huge delay, the disc information is shown and the file system is fsck'ed, as usually. However, disabling APIC, eliminates this delay. On 7-CURRENT, there is not such delay, even though APIC was enabled. Regards. -- Alex From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 06:59: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 9C91916A412 for ; Sun, 10 Sep 2006 06:59:33 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C2743D46 for ; Sun, 10 Sep 2006 06:59:33 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1197882wxd for ; Sat, 09 Sep 2006 23:59: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=qBpPzUeK5JPD+ee4mLVRAU2MVIlXNXy756KH/+Jn66ZX6q8TPAjOb0z/YQfv1zi1LbQU/PVlRwHgZZTweT5FBd/lwW7hBQ7vD3YcsvtHxYDFC2V0QODD3klnDH1A3hKNv03qCyN+aIPwakibkLmVcan/fpHc0gCToW8Cr/JRpuM= Received: by 10.90.28.12 with SMTP id b12mr1294196agb; Sat, 09 Sep 2006 23:59:32 -0700 (PDT) Received: by 10.90.70.6 with HTTP; Sat, 9 Sep 2006 23:59:31 -0700 (PDT) Message-ID: <7579f7fb0609092359k58ed21c2tbe52eb81f453dbb4@mail.gmail.com> Date: Sat, 9 Sep 2006 23:59:31 -0700 From: "Matthew Jacob" To: "Alex Salazar" In-Reply-To: <40c4bb930609092128l104cc3femb53e810b3f719dc2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40c4bb930609020223h50c43537n1c8b32081ef5c1bf@mail.gmail.com> <7579f7fb0609021220y2d530c93pebb59bb2c0a70945@mail.gmail.com> <40c4bb930609081046m1e94266al6be8873e2149c607@mail.gmail.com> <7579f7fb0609091125j7f8abcebq3075d4bd474f21d@mail.gmail.com> <7579f7fb0609091127o2962d4dcxa0d658cd09899156@mail.gmail.com> <40c4bb930609091731q81d4e4agb0418e3b60d519c1@mail.gmail.com> <7579f7fb0609091942p2f52d710v3daa0ccb291e67e4@mail.gmail.com> <40c4bb930609092128l104cc3femb53e810b3f719dc2@mail.gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 06:59:33 -0000 > On 6-STABLE, those "Error 22" messages on boot, show up too slowly, > one character at a time, at about one line every 30 seconds, which delays > the boot process on almost 20 (twenty) minutes. After that huge delay, the > disc information is shown and the file system is fsck'ed, as usually. However, > disabling APIC, eliminates this delay. > > On 7-CURRENT, there is not such delay, even though APIC was enabled. Oh, okay. Not an mpt issue (I'm somewhat narrowly focussed). From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 10:35: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 B363316A403 for ; Sun, 10 Sep 2006 10:35:03 +0000 (UTC) (envelope-from roth@droopy.unibe.ch) Received: from mailhub03.unibe.ch (mailhub.unibe.ch [130.92.9.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C9D643D67 for ; Sun, 10 Sep 2006 10:35:02 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from localhost (scanhub02.unibe.ch [130.92.5.62]) by mailhub03.unibe.ch (Postfix) with ESMTP id AF5DF4BCDA; Sun, 10 Sep 2006 12:35:00 +0200 (CEST) X-Virus-checked: by University of Berne Received: from mailhub03.unibe.ch ([130.92.9.70]) by localhost (scanhub02.unibe.ch [130.92.5.62]) (amavisd-new, port 10024) with LMTP id a+fTTXAwUYF9; Sun, 10 Sep 2006 12:34:59 +0200 (CEST) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub03.unibe.ch (Postfix) with ESMTP id 1CCBE4BC58; Sun, 10 Sep 2006 12:34:59 +0200 (CEST) Received: from droopy.unibe.ch (droopy [130.92.64.20]) by asterix.unibe.ch (8.13.6+Sun/8.13.6) with ESMTP id k8AAYxcw010923; Sun, 10 Sep 2006 12:34:59 +0200 (MEST) Received: (from roth@localhost) by droopy.unibe.ch (8.12.10+Sun/8.12.9/Submit) id k8AAYxWF009275; Sun, 10 Sep 2006 12:34:59 +0200 (MEST) Date: Sun, 10 Sep 2006 12:34:59 +0200 From: Tobias Roth To: Daniel Bond Message-ID: <20060910103459.GA9229@droopy.unibe.ch> References: <20060907181311.GA25768@spearburn.danielbond.org> <20060908121348.GA5534@droopy.unibe.ch> <20060909212208.GA16312@spearburn.danielbond.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060909212208.GA16312@spearburn.danielbond.org> User-Agent: Mutt/1.4i X-message-flag: Warning! Using Outlook is insecure and promotes virus distribution. Please use a different email client. Cc: freebsd-stable@freebsd.org Subject: Re: Patch for GBDE rc-script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 10:35:03 -0000 On Sat, Sep 09, 2006 at 11:22:08PM +0200, Daniel Bond wrote: > On 14:13 Fri 08 Sep, Tobias Roth wrote: > > > > How is this better/different from just adding the gbde device to > > /etc/fstab and have it mounted along with all other filesystems? > > > It says in the handbook: > > "Since encrypted file systems cannot yet be listed in /etc/fstab for automatic > mounting, the file systems must be checked for errors by running fsck(8) > manually before mounting." Interesting. I have had this line in my /etc/fstab for almost a year now and it just works(tm): /dev/ad0s4d.bde /home ufs rw 2 2 Since during startup, gbde is run before fsck, I don't see why there would be any problems with this. Thanks, Tobias From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 15:05: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 1DC1016A417 for ; Sun, 10 Sep 2006 15:05:34 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DC2843D49 for ; Sun, 10 Sep 2006 15:05:27 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8AF5RM4031572 for ; Sun, 10 Sep 2006 10:05:27 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 10:05:27 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8AF5QSJ031569 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 10:05:26 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 10:05:26 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060910150526.GA31323@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 15:05:34 -0000 On Sun, Sep 10, 2006 at 11:59:10AM +1000, Mark Andrews wrote: > > > Yeah, -STABLE is what you should run if you want stable code, right? > > No. STABLE means STABLE API. > > If you want stable code you run releases. Between releases > stable can become unstable. Think of stable as permanent > BETA code. Changes have passed the first level of testing > in current which is permanent ALPHA code. > > Most of the time beta code is perfectly fine to run but > occasionally things will go wrong. The point of BETA code > is to catch those errors that escape detection in the ALPHA > stage before they make it into a release. That is done by > having a wider diversity of clients run the BETA code. > > Occasionally you have bugs that make it through both the ALPHA > and BETA stages. Of course this assumes that -RELEASE is actually stable and fully suitable for production use. As soon as you find a bug that you can't live with in -RELEASE, you have darn few options other than to updade to -STABLE, especially if there's a commit in the tree that appears to fix the bug in -STABLE. Once the -RELEASE branch is taken, code updates there . Not even Microsoft expects people to live from release to release without bug fixes! In the 10 years I've been running FreeBSD in a production environment I've yet to find a -RELEASE branch that is actually suitable for production use for the duration between -RELEASEs; inevitably a bug that I can't live with requires that I update the source, and what does one update to in this instance? -STABLE. If the project wishes to have -RELEASE be "the stable point" then bug fixes (once FULLY tested) must be back-ported to -RELEASE - otherwise the appearance of a bug you can't live with gives you no other real option than to run the -STABLE track. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 15:21: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 A148616A47C for ; Sun, 10 Sep 2006 15:21:34 +0000 (UTC) (envelope-from pokui@psg.com) Received: from psg.com (psg.com [147.28.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37F7C43D45 for ; Sun, 10 Sep 2006 15:21:34 +0000 (GMT) (envelope-from pokui@psg.com) Received: from pokui (helo=localhost) by psg.com with local-esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1GMR7l-0005K2-UJ; Sun, 10 Sep 2006 15:21:33 +0000 Date: Sun, 10 Sep 2006 15:21:33 +0000 (GMT) From: Patrick J Okui To: Karl Denninger In-Reply-To: <20060910150526.GA31323@FS.denninger.net> Message-ID: <20060910151817.H8856@psg.com> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 15:21:34 -0000 On Sun, 10 Sep 2006, Karl Denninger wrote: > > Once the -RELEASE branch is taken, code updates there . > I take it you haven't read the text in the handbook that has been linked to by a few posters. You can track changes to a particular release - say by using RELENG_6_1 rather than RELENG_6. In which case, would you still say you are tracking STABLE? -- patrick From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 15:28: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 41D8E16A40F for ; Sun, 10 Sep 2006 15:28:16 +0000 (UTC) (envelope-from adam@adamretter.eclipse.co.uk) Received: from mra02.ch.as12513.net (mra02.ch.as12513.net [82.153.254.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7FBE43D55 for ; Sun, 10 Sep 2006 15:28:15 +0000 (GMT) (envelope-from adam@adamretter.eclipse.co.uk) Received: from localhost (localhost [127.0.0.1]) by mra02.ch.as12513.net (Postfix) with ESMTP id 998A7D426E; Sun, 10 Sep 2006 16:28:13 +0100 (BST) Received: from mra02.ch.as12513.net ([127.0.0.1]) by localhost (mra02.ch.as12513.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05724-01-56; Sun, 10 Sep 2006 16:28:13 +0100 (BST) Received: from funkalicious.home.dom (unknown [82.152.93.225]) by mra02.ch.as12513.net (Postfix) with ESMTP id D065DD423E; Sun, 10 Sep 2006 16:28:12 +0100 (BST) From: Adam Retter To: Tony Maher In-Reply-To: <4500B648.4000009@uts.edu.au> References: <1157632691.58001.6.camel@funkalicious.home.dom> <4500A1A0.3060706@uts.edu.au> <1157673230.58001.11.camel@funkalicious.home.dom> <4500B648.4000009@uts.edu.au> Content-Type: text/plain Date: Sun, 10 Sep 2006 16:28:12 +0100 Message-Id: <1157902092.855.1.camel@funkalicious.home.dom> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by Eclipse VIRUSshield at eclipse.net.uk Cc: freebsd-stable@freebsd.org Subject: Re: Broken loader in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 15:28:16 -0000 Thanks very much Tony :-D I removed my CFLAGS and COPTFLAGS from make.conf and just left the CPUTYPE flag and rebuilt and installed kernel and world, all seems to work fine again now, if anything the system seems a bit faster :-D Thanks again. Adam. On Fri, 2006-09-08 at 10:16 +1000, Tony Maher wrote: > Adam Retter wrote: > > On Fri, 2006-09-08 at 08:48 +1000, Tony Maher wrote: > >>Do you have any compile options in /etc/make.conf? > >>These can affect loader. > > > > Yes, these are set in make.conf, but I have always had these set and > > there have been no problems in the past... > > > > > > # Compile for Pentium 4 CPU > > CPUTYPE=p4 > > > > # Compiler optimisation flags > > CFLAGS= -O2 -pipe -funroll-loops -ffast-math > > > > # Compiler optimisation flags for the Kernel > > COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math > > >From private email from someone else with same problem (they had > -funroll-loops in make.conf), > > "optimizations are bad for the loader"... but it still works fine for me > using -O -pipe. > > -- > tonym > _______________________________________________ > 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 Sun Sep 10 15:42: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 0063D16A415 for ; Sun, 10 Sep 2006 15:42:19 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id F120843D46 for ; Sun, 10 Sep 2006 15:42:18 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1630616pye for ; Sun, 10 Sep 2006 08:42:18 -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=d+o5HETsXWL2Y9Uggf5ZLJjVHNV8u8KKx39X0IgDhVEzW4YKdFXKFbOb3F+iLlNQjCOoWfAu+LHocVrCeaiZ28jmcnzTAhhc98HRBliZacGf+iyTYc/t22VKTbyzr2wYrRCeLgtOJMxS+5vaMXkPWYF06da6BzU9+e1xibg7aNY= Received: by 10.35.72.6 with SMTP id z6mr6990195pyk; Sun, 10 Sep 2006 08:42:18 -0700 (PDT) Received: by 10.35.114.2 with HTTP; Sun, 10 Sep 2006 08:42:18 -0700 (PDT) Message-ID: <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> Date: Sun, 10 Sep 2006 16:42:18 +0100 From: "Joao Barros" To: freebsd-current@freebsd.org In-Reply-To: <20060909200549.GA66552@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70e8236f0609090456l31cb39d8if9bdf2d664886a13@mail.gmail.com> <200609091907.06716.max@love2party.net> <70e8236f0609091302i1c98f8f7t6ad32cd602b054c@mail.gmail.com> <20060909200549.GA66552@xor.obsecurity.org> Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: panic: integer divide fault 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: Sun, 10 Sep 2006 15:42:20 -0000 On 9/9/06, Kris Kennaway wrote: > On Sat, Sep 09, 2006 at 09:02:35PM +0100, Joao Barros wrote: > > On 9/9/06, Max Laier wrote: > > > > > >Can you try to get a dump, trace, or at least figure out which function > > >the IP is refering to? > > > > > > > Well, the problem only occurs when I boot from the disk and the > > installed kernel doesn't have debug support. > > Does 'set dumpdev=' work from the boot loader? I tried some > > combinations with no success. > > No. > > > I can try and install a 6-STABLE snapshot if there's no way of getting > > the info needed. > > You can either try to install a new kernel with DDB support, or follow > the "instruction pointer" method in the developers handbook chapter on > kernel debugging. I copied a CURRENT kernel from a 200608 snapshot and the problem also occurs thus I'm adding current@. My current laptop doesn't have a serial port so I'm copying this by hand: Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xc08a1fb7 stack pointer = 0x28:0xc0c20b14 frame pointer = 0x28:0xc0c20b9c 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 = 0 (swapper) [thread pid 0 tid 0 ] Stopped at __qdivrem+0x3b: divl %ecx,%eax db> bt Tracing pid 0 tid0 td 0xc0a0c818 __qdivrem(37fdfa0,0,0,0,0,...) at __qdivrem+0x3b __udivdi3(37fdfa0,0,0,0) at __udivdi3+0x16 ata_raid_promise_read_meta(c37a5000,c09f4a80,1,8086,c37a5000,...) at ata_raid_promise_read_meta+0x9b ata_raid_read_metadata(c37a5000,c37a5000,c0c20c70,c06b58a4,c37a5000,...) at ata_raid_metadata+0x2be ata_raid_subdisk_attach(c37a5000) at ata_raid_subdisk_attach+0x33 device_attach(c37a5000,c37a5180,c37a5000,c36885c0,0,...) at device_attach+0x58 device_probe_and_attach(c37a5200,c37a5200,c08ec9a9,0,c37a5180,...) at bus_generic_attach+0x16 ad_attach(c37a5200) at ad_attach+0x2c8 device_attach(c37a5200,c095f2d0,c37a5200,0,c368d800,...) at device_attach+0x58 device_probe_and_attach(c37a5200) at device_probe_and_atach+0xe0 bus_generic_attach(c3659080,c3659080,ffffffff,0,c37a5200,...) at bus_generic_attach+0x16 ata_identify(c3659080) at ata_identify+0x1c8 ata_boot_attach(0xc0a11d80,0,c09212e7,47,...) at ata_boot_attach+0x3e run_interrupt_drive_config_hooks(0,c1ec00,c1e000,0,c0451065,...) at run_interrupt_drive_config_hooks+0x43 mi_startup() at mi_startup+0x96 begin() at begin+0x2c This board has a Promise SATA raid controller and it is disabled in the BIOS. I even tried disabling it through a jumper but it still stops. -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 16:16: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 C69B116A403; Sun, 10 Sep 2006 16:16:19 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D22843D4C; Sun, 10 Sep 2006 16:16:19 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.2] ([10.0.0.2]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k8AGGI82092996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Sep 2006 09:16:18 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <45043A4F.3010308@errno.com> Date: Sun, 10 Sep 2006 09:16:15 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: Joao Barros References: <70e8236f0609090456l31cb39d8if9bdf2d664886a13@mail.gmail.com> <200609091907.06716.max@love2party.net> <70e8236f0609091302i1c98f8f7t6ad32cd602b054c@mail.gmail.com> <20060909200549.GA66552@xor.obsecurity.org> <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> In-Reply-To: <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: panic: integer divide fault 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: Sun, 10 Sep 2006 16:16:20 -0000 Joao Barros wrote: > On 9/9/06, Kris Kennaway wrote: >> On Sat, Sep 09, 2006 at 09:02:35PM +0100, Joao Barros wrote: >> > On 9/9/06, Max Laier wrote: >> > > >> > >Can you try to get a dump, trace, or at least figure out which >> function >> > >the IP is refering to? >> > > >> > >> > Well, the problem only occurs when I boot from the disk and the >> > installed kernel doesn't have debug support. >> > Does 'set dumpdev=' work from the boot loader? I tried some >> > combinations with no success. >> >> No. >> >> > I can try and install a 6-STABLE snapshot if there's no way of getting >> > the info needed. >> >> You can either try to install a new kernel with DDB support, or follow >> the "instruction pointer" method in the developers handbook chapter on >> kernel debugging. > > I copied a CURRENT kernel from a 200608 snapshot and the problem also > occurs thus I'm adding current@. > My current laptop doesn't have a serial port so I'm copying this by hand: > > Fatal trap 18: integer divide fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xc08a1fb7 > stack pointer = 0x28:0xc0c20b14 > frame pointer = 0x28:0xc0c20b9c > 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 = 0 (swapper) > [thread pid 0 tid 0 ] > Stopped at __qdivrem+0x3b: divl %ecx,%eax > > db> bt > Tracing pid 0 tid0 td 0xc0a0c818 > __qdivrem(37fdfa0,0,0,0,0,...) at __qdivrem+0x3b > __udivdi3(37fdfa0,0,0,0) at __udivdi3+0x16 > ata_raid_promise_read_meta(c37a5000,c09f4a80,1,8086,c37a5000,...) at > ata_raid_promise_read_meta+0x9b > ata_raid_read_metadata(c37a5000,c37a5000,c0c20c70,c06b58a4,c37a5000,...) > at ata_raid_metadata+0x2be > ata_raid_subdisk_attach(c37a5000) at ata_raid_subdisk_attach+0x33 > device_attach(c37a5000,c37a5180,c37a5000,c36885c0,0,...) at > device_attach+0x58 > device_probe_and_attach(c37a5200,c37a5200,c08ec9a9,0,c37a5180,...) at > bus_generic_attach+0x16 > ad_attach(c37a5200) at ad_attach+0x2c8 > device_attach(c37a5200,c095f2d0,c37a5200,0,c368d800,...) at > device_attach+0x58 > device_probe_and_attach(c37a5200) at device_probe_and_atach+0xe0 > bus_generic_attach(c3659080,c3659080,ffffffff,0,c37a5200,...) at > bus_generic_attach+0x16 > ata_identify(c3659080) at ata_identify+0x1c8 > ata_boot_attach(0xc0a11d80,0,c09212e7,47,...) at ata_boot_attach+0x3e > run_interrupt_drive_config_hooks(0,c1ec00,c1e000,0,c0451065,...) at > run_interrupt_drive_config_hooks+0x43 > mi_startup() at mi_startup+0x96 > begin() at begin+0x2c > > This board has a Promise SATA raid controller and it is disabled in > the BIOS. I even tried disabling it through a jumper but it still > stops. > In sys/dev/ata/ata-raid.h the PROMISE_LBA macro does an unchecked calculation that apparently can divide by zero. Soren would likely understand the root cause of this problem but until then you can patch the driver to workaround the problem. Sam From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 16:19: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 95DBE16A412 for ; Sun, 10 Sep 2006 16:19:12 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 956D343D55 for ; Sun, 10 Sep 2006 16:19:11 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.2] ([10.0.0.2]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k8AGJA7K093014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Sep 2006 09:19:11 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <45043AFA.4080001@errno.com> Date: Sun, 10 Sep 2006 09:19:06 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: dandee@volny.cz References: <000001c6d340$004fdf40$6508280a@tocnet28.jspoj.czf> In-Reply-To: <000001c6d340$004fdf40$6508280a@tocnet28.jspoj.czf> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: Where is the maximum of hw.ath.txbuf and rxbuf ? (former: atheros driver under high load, panics and even more freezes) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 16:19:12 -0000 Daniel Dvořák wrote: > Hi Sam, > > thank you for your answer. I think it is connected to this problem somehow, but not fully. > > I increased txbuf and rxbuf twice to 200 and 80, I saw some > betterment in less of "no buffers space ...", but latency went up to 2000 ms. > > Now I ended at txbuf=800 and rxbuf=320 on both sides R1 and R2. > > But still, there is the same problem: > > It was tested after the rebooting R2 almost at once. > > --- R1 ping statistics --- > 10000 packets transmitted, 8752 packets received, 12% packet loss > round-trip min/avg/max/stddev = 1.324/920.480/6323.454/766.399 ms up to 6k ms > > R2# athstats -i ath0 > 11309 data frames received > 11384 data frames transmit > 12508 long on-chip tx retries > 769 tx failed 'cuz too many retries > 24M current transmit rate > 2 tx management frames > 6 tx frames discarded prior to association > 31 tx stopped 'cuz no xmit buffer > 38 tx frames with no ack marked > 3 rx failed 'cuz of bad CRC > 4464 rx failed 'cuz of PHY err > 4464 OFDM timing > 24 periodic calibrations > 27 rssi of last ack > 27 avg recv rssi > -96 rx noise floor > 1 switched default/rx antenna > Antenna profile: > [1] tx 10614 rx 11449 > > > Where is the maximum of txbuf and rxbuf ? The max is derived from available memory. The h/w has no upper bounds. > > I would like to test it. > > Thank you for your attention. > > Daniel > > >> -----Original Message----- >> From: Sam Leffler [mailto:sam@errno.com] >> Sent: Friday, September 08, 2006 6:30 AM >> To: dandee@volny.cz >> Cc: freebsd-stable@freebsd.org >> Subject: Re: atheros driver under high load, panics and even >> more freezes >> >> Daniel DvoÞák wrote: >>> Hi Sam and all, >>> >>> I am not sure if I understand your answer, but I try it. >>> >>> When I use start my test, athstats shows this: >>> >>> athstats -i ath0 >>> >>> 19308912 data frames received >>> 15723536 data frames transmit >>> 6536 tx frames with an alternate rate >>> 2188280 long on-chip tx retries >>> 62583 tx failed 'cuz too many retries >>> 348 tx linearized to cluster >>> 24M current transmit rate >>> 6 tx management frames >>> 6 tx frames discarded prior to association >>> 27129 tx stopped 'cuz no xmit buffer >>> 23057 tx frames with no ack marked >>> 1182 rx failed 'cuz of bad CRC >>> 761604 rx failed 'cuz of PHY err >>> 761604 OFDM timing >>> 4829 periodic calibrations >>> 28 rssi of last ack >>> 27 avg recv rssi >>> -96 rx noise floor >>> 1 switched default/rx antenna >>> Antenna profile: >>> [1] tx 15660942 rx 19451935 >>> [2] tx 2 rx 0 >>> >>> ... >>> >>> >>> I use this ping command from R2: >>> ping -i .002 -c 10000 -s 1472 opposite side R1 >>> >>> --- R1 ping statistics --- >>> 10000 packets transmitted, 10000 packets received, 0% packet loss >>> round-trip min/avg/max/stddev = 1.316/1.442/49.391/1.757 ms >>> >>> You can see nice average latency about 1,4 ms and no one >> packet was lost. >>> athstats almost wasnŽt changed. >>> >>> 19309465 data frames received >>> 15724079 data frames transmit >>> 6536 tx frames with an alternate rate >>> 2188281 long on-chip tx retries >>> 62583 tx failed 'cuz too many retries >>> 348 tx linearized to cluster >>> 24M current transmit rate >>> 6 tx management frames >>> 6 tx frames discarded prior to association >>> 27129 tx stopped 'cuz no xmit buffer >>> 23075 tx frames with no ack marked >>> 1182 rx failed 'cuz of bad CRC >>> 761605 rx failed 'cuz of PHY err >>> 761605 OFDM timing >>> 4834 periodic calibrations >>> 29 rssi of last ack >>> 27 avg recv rssi >>> -96 rx noise floor >>> 1 switched default/rx antenna >>> Antenna profile: >>> [1] tx 15661485 rx 19452488 >>> [2] tx 2 rx 0 >>> >>> For compare with flood ping at once: >>> >>> --- R1 ping statistics --- >>> 10000 packets transmitted, 10000 packets received, 0% packet loss >>> round-trip min/avg/max/stddev = 1.319/1.516/5.594/0.120 ms >>> >>> Almost the same, yes max is even better. >>> >>> >> ---------------------------------------------------------------------- >>> ------ >>> -------------- >>> >>> If I use interval 1/1000 s to send the echo request, the >> situation is >>> rapidly changed. >>> ping -i .001 -c 10000 -s 1472 opposite side R1 >>> >>> --- R1 ping statistics --- >>> 10000 packets transmitted, 9681 packets received, 3% packet loss >>> round-trip min/avg/max/stddev = 1.319/335.806/564.946/170.691 ms >>> >>> R2# ifconfig -v ath0 >>> ath0: >> flags=8c43 mtu >>> 1500 >>> ------ ??????????? OACTIVE FLAG ????????? ---- >>> inet6 fe80::20b:6bff:fe2a:c78e%ath0 prefixlen 64 scopeid 0x2 >>> inet 10.XX.YY.ZZ netmask 0xfffffffc broadcast 10.40.64.19 >>> ether xxxxxxxxxxxxxxxx >>> media: IEEE 802.11 Wireless Ethernet OFDM/24Mbps mode 11a >>> (OFDM/24Mbps) >>> status: associated >>> >>> 19350739 data frames received >>> 15765446 data frames transmit >>> 6536 tx frames with an alternate rate >>> 2194842 long on-chip tx retries >>> 62590 tx failed 'cuz too many retries >>> 348 tx linearized to cluster >>> 24M current transmit rate >>> 6 tx management frames >>> 6 tx frames discarded prior to association >>> 29242 tx stopped 'cuz no xmit buffer >>> 23155 tx frames with no ack marked >>> 1182 rx failed 'cuz of bad CRC >>> 764641 rx failed 'cuz of PHY err >>> 764641 OFDM timing >>> 4856 periodic calibrations >>> 28 rssi of last ack >>> 27 avg recv rssi >>> -96 rx noise floor >>> 1 switched default/rx antenna >>> Antenna profile: >>> [1] tx 15702845 rx 19493774 >>> [2] tx 2 rx 0 >>> >>> I observe flags of ath and when latency is going to high more and >>> more, there is a new flag which IŽve never seen before, >> OACTIVE FLAG ? >>> R2# man ifconfig | grep "OACTIVE" >>> >>> When ping ends oactive flag disappears. >>> >>> When the same ping test is done from linux box to fbsd, >> nice latency >>> 1,2ms and no "no buffer". >>> >>> with -i 0.002 the throughput is about 0,5MB/s in and out of cource >>> >>> with -i 0.001 until no buffer is about 0,85MB/s in and out. >>> >>> when no buffer and octive appears, the throughput is about >> 0,1MB/s or >>> 128KB/s if you like or 1Mbit/s. >>> >>> I attached the progress of pinging ip address. >> You ask why you're seeing OACTIVE when you lower the >> inter-packet wait time to ping. This is because you're >> flooding the tx queue of the ath driver and using up all the >> tx buffers/descriptors. When ath is handed a frame to send >> and it has no resources available it will mark the interface >> "active' (OACTIVE) and drop the packet. You can also see >> this in the athstats output ("tx stopped 'cuz no xmit >> buffer"). Linux behaves differently because it blocks the >> user process when this happens until such time as there are >> resources to do the send. This behaviour likely also >> explains the variability in the ping times; I think the rx >> processing may be deferred while the driver deals with the tx flood. >> >> You can up the number of tx buffers available with the >> ATH_TXBUF config option or by setting the hw.ath.txbuf >> tunable from the loader. The default is 100 buffers which is >> usually plenty for sta-mode operation--which is what the >> driver is optimized for (it appears linux defaults to 200 tx >> buffers which would also explain different behaviour). >> Likewise there is a rx-side tunable for the number of rx buffers. >> >> Sam >> > > > From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 16:49: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 5DFF716A416 for ; Sun, 10 Sep 2006 16:49:00 +0000 (UTC) (envelope-from christopher@schulte.org) Received: from monster.schulte.org (monster.schulte.org [209.134.156.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC69543D49 for ; Sun, 10 Sep 2006 16:48:59 +0000 (GMT) (envelope-from christopher@schulte.org) Received: from localhost (localhost.schulte.org [127.0.0.1]) by monster.schulte.org (Postfix) with ESMTP id B30C51CC0F; Sun, 10 Sep 2006 11:48:58 -0500 (CDT) X-Virus-Scanned: amavisd-new at schulte.org Received: from monster.schulte.org ([127.0.0.1]) by localhost (monster.schulte.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id so4invfbb5G1; Sun, 10 Sep 2006 11:48:54 -0500 (CDT) Received: from 2k3.windows2003.schulte.org (exchange.windows2003.schulte.org [209.134.156.205]) by monster.schulte.org (Postfix) with ESMTP; Sun, 10 Sep 2006 11:48:54 -0500 (CDT) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-mimeole: Produced By Microsoft Exchange V6.5 Date: Sun, 10 Sep 2006 11:48:52 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Thread-Index: AcbU7YT7J80Lj0s/SqW2bbZ/HpuI1gABiqNA From: "Christopher Schulte" To: "Patrick J Okui" , "Karl Denninger" Cc: freebsd-stable@freebsd.org Subject: RE: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 16:49:00 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org=20 > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Patrick J Okui > Sent: Sunday, September 10, 2006 10:22 AM > To: Karl Denninger > Cc: freebsd-stable@freebsd.org > Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! >=20 > You can track changes to a particular release - say by using > RELENG_6_1 rather than RELENG_6. In which case, would you=20 > still say you are tracking STABLE? Well, that depends. For security and "critical fixes" (as the handbook phrases it) you can track RELENG_6_1 (in the case of 6.1-RELEASE) and be happy. But what happens if the needed fix isn't security or "critical" in the minds of the FreeBSD developers? At that point you either need to wait for the next RELEASE, manually merge fixes into your production source (which depending on the fix(s) could be non-trivial) or cross your fingers and follow -STABLE. This problem isn't specific to FreeBSD (or unix in general) by Any means, of course. Sure, we could broaden the scope of RELENG_X_Y. Or introduce a new branch that's closer to -STABLE yet tuned for something like, "security, critical and major fixes" for production systems. I'm not sure either of those options are preferable, would be effective in alleviating the problem, or even workable in the first place. Personally, I've been served quite well for many years with the current configuration. Since I don't track -STABLE on anything important (or more accurately have yet NEEDED to do so), I've never been hit by any of these transient issues that crop up from time to time and can elicit loud complaints. --Chris From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 17:28:32 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 AE7BE16A40F for ; Sun, 10 Sep 2006 17:28:32 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77BA943D4C for ; Sun, 10 Sep 2006 17:28:31 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1657943pye for ; Sun, 10 Sep 2006 10:28:31 -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=JitDUxjYNBDp+0bhzs1KYpXQTX0fEO4YxdAe8Adw64UPe1FtgYeO2WCMFKw3rWD/JiDoljDWLZyvlAAcc5tZy9vwPRlIzyjQ8n0MDdWP94WAoHpl7gUZw6yCwXqgGlUxTZC/Xz5f/ZWc3Kp3AHLKO9bp2Z0fop8vrH5CgLQQYZQ= Received: by 10.35.96.7 with SMTP id y7mr7152873pyl; Sun, 10 Sep 2006 10:28:30 -0700 (PDT) Received: by 10.35.114.2 with HTTP; Sun, 10 Sep 2006 10:28:30 -0700 (PDT) Message-ID: <70e8236f0609101028i20b0069dl5501d0fbb0647741@mail.gmail.com> Date: Sun, 10 Sep 2006 18:28:30 +0100 From: "Joao Barros" To: "Sam Leffler" In-Reply-To: <45043A4F.3010308@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70e8236f0609090456l31cb39d8if9bdf2d664886a13@mail.gmail.com> <200609091907.06716.max@love2party.net> <70e8236f0609091302i1c98f8f7t6ad32cd602b054c@mail.gmail.com> <20060909200549.GA66552@xor.obsecurity.org> <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> <45043A4F.3010308@errno.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: panic: integer divide fault 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: Sun, 10 Sep 2006 17:28:32 -0000 On 9/10/06, Sam Leffler wrote: > Joao Barros wrote: > > On 9/9/06, Kris Kennaway wrote: > >> On Sat, Sep 09, 2006 at 09:02:35PM +0100, Joao Barros wrote: > >> > On 9/9/06, Max Laier wrote: > >> > > > >> > >Can you try to get a dump, trace, or at least figure out which > >> function > >> > >the IP is refering to? > >> > > > >> > > >> > Well, the problem only occurs when I boot from the disk and the > >> > installed kernel doesn't have debug support. > >> > Does 'set dumpdev=' work from the boot loader? I tried some > >> > combinations with no success. > >> > >> No. > >> > >> > I can try and install a 6-STABLE snapshot if there's no way of getting > >> > the info needed. > >> > >> You can either try to install a new kernel with DDB support, or follow > >> the "instruction pointer" method in the developers handbook chapter on > >> kernel debugging. > > > > I copied a CURRENT kernel from a 200608 snapshot and the problem also > > occurs thus I'm adding current@. > > My current laptop doesn't have a serial port so I'm copying this by hand: > > > > Fatal trap 18: integer divide fault while in kernel mode > > cpuid = 0; apic id = 00 > > instruction pointer = 0x20:0xc08a1fb7 > > stack pointer = 0x28:0xc0c20b14 > > frame pointer = 0x28:0xc0c20b9c > > 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 = 0 (swapper) > > [thread pid 0 tid 0 ] > > Stopped at __qdivrem+0x3b: divl %ecx,%eax > > > > db> bt > > Tracing pid 0 tid0 td 0xc0a0c818 > > __qdivrem(37fdfa0,0,0,0,0,...) at __qdivrem+0x3b > > __udivdi3(37fdfa0,0,0,0) at __udivdi3+0x16 > > ata_raid_promise_read_meta(c37a5000,c09f4a80,1,8086,c37a5000,...) at > > ata_raid_promise_read_meta+0x9b > > ata_raid_read_metadata(c37a5000,c37a5000,c0c20c70,c06b58a4,c37a5000,...) > > at ata_raid_metadata+0x2be > > ata_raid_subdisk_attach(c37a5000) at ata_raid_subdisk_attach+0x33 > > device_attach(c37a5000,c37a5180,c37a5000,c36885c0,0,...) at > > device_attach+0x58 > > device_probe_and_attach(c37a5200,c37a5200,c08ec9a9,0,c37a5180,...) at > > bus_generic_attach+0x16 > > ad_attach(c37a5200) at ad_attach+0x2c8 > > device_attach(c37a5200,c095f2d0,c37a5200,0,c368d800,...) at > > device_attach+0x58 > > device_probe_and_attach(c37a5200) at device_probe_and_atach+0xe0 > > bus_generic_attach(c3659080,c3659080,ffffffff,0,c37a5200,...) at > > bus_generic_attach+0x16 > > ata_identify(c3659080) at ata_identify+0x1c8 > > ata_boot_attach(0xc0a11d80,0,c09212e7,47,...) at ata_boot_attach+0x3e > > run_interrupt_drive_config_hooks(0,c1ec00,c1e000,0,c0451065,...) at > > run_interrupt_drive_config_hooks+0x43 > > mi_startup() at mi_startup+0x96 > > begin() at begin+0x2c > > > > This board has a Promise SATA raid controller and it is disabled in > > the BIOS. I even tried disabling it through a jumper but it still > > stops. > > > > In sys/dev/ata/ata-raid.h the PROMISE_LBA macro does an unchecked > calculation that apparently can divide by zero. Soren would likely > understand the root cause of this problem but until then you can patch > the driver to workaround the problem. > > Sam > > Thanks for narrowing it down! -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 18:18: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 6294616A403 for ; Sun, 10 Sep 2006 18:18:48 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5385743F48 for ; Sun, 10 Sep 2006 18:13:33 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8AIDW1h035239 for ; Sun, 10 Sep 2006 13:13:32 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 13:13:32 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8AIDVMw035236 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 13:13:31 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 13:13:31 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060910181331.GA35166@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910151817.H8856@psg.com> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 18:18:48 -0000 On Sun, Sep 10, 2006 at 03:21:33PM +0000, Patrick J Okui wrote: > On Sun, 10 Sep 2006, Karl Denninger wrote: > > > > >Once the -RELEASE branch is taken, code updates there . > > > > I take it you haven't read the text in the handbook that has been > linked to by a few posters. > > You can track changes to a particular release - say by using > RELENG_6_1 rather than RELENG_6. In which case, would you still > say you are tracking STABLE? Yes. If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition tracking -STABLE. Indeed, the current tag on my CVS tree is TRELENG_6! -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 18:36: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 1210816A416 for ; Sun, 10 Sep 2006 18:36:33 +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 A4A0743D55 for ; Sun, 10 Sep 2006 18:36:32 +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 84AC61A4D8E for ; Sun, 10 Sep 2006 11:36:32 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DDDBE5148C; Sun, 10 Sep 2006 14:36:31 -0400 (EDT) Date: Sun, 10 Sep 2006 14:36:31 -0400 From: Kris Kennaway To: freebsd-stable@freebsd.org Message-ID: <20060910183631.GA6406@xor.obsecurity.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20060910181331.GA35166@FS.denninger.net> User-Agent: Mutt/1.4.2.2i Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 18:36:33 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 01:13:31PM -0500, Karl Denninger wrote: > On Sun, Sep 10, 2006 at 03:21:33PM +0000, Patrick J Okui wrote: > > On Sun, 10 Sep 2006, Karl Denninger wrote: > >=20 > > > > > >Once the -RELEASE branch is taken, code updates there . > > > > >=20 > > I take it you haven't read the text in the handbook that has been=20 > > linked to by a few posters. > >=20 > > You can track changes to a particular release - say by using=20 > > RELENG_6_1 rather than RELENG_6. In which case, would you still=20 > > say you are tracking STABLE? >=20 > Yes. >=20 > If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > tracking -STABLE. >=20 > Indeed, the current tag on my CVS tree is TRELENG_6! Not the question he asked, please re-read. Kris --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBFsuWry0BWjoQKURAkkeAKCLnZEkoa1a2dXd3dyM5jm1+XptGgCfVZi+ Unof9l3bmde0EJT5vZWyhEg= =523P -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 18:39: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 E02A516A417 for ; Sun, 10 Sep 2006 18:39:59 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54EB743D45 for ; Sun, 10 Sep 2006 18:39:58 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8AIdwp4035739 for ; Sun, 10 Sep 2006 13:39:58 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 13:39:58 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8AIdwp0035736 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 13:39:58 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 13:39:58 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060910183958.GA35701@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910183631.GA6406@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910183631.GA6406@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 18:40:00 -0000 On Sun, Sep 10, 2006 at 02:36:31PM -0400, Kris Kennaway wrote: > On Sun, Sep 10, 2006 at 01:13:31PM -0500, Karl Denninger wrote: > > On Sun, Sep 10, 2006 at 03:21:33PM +0000, Patrick J Okui wrote: > > > On Sun, 10 Sep 2006, Karl Denninger wrote: > > > > > > > > > > >Once the -RELEASE branch is taken, code updates there . > > > > > > > > > > I take it you haven't read the text in the handbook that has been > > > linked to by a few posters. > > > > > > You can track changes to a particular release - say by using > > > RELENG_6_1 rather than RELENG_6. In which case, would you still > > > say you are tracking STABLE? > > > > Yes. > > > > If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > > tracking -STABLE. > > > > Indeed, the current tag on my CVS tree is TRELENG_6! > > Not the question he asked, please re-read. > > Kris Yes it is, in the general case; in any event if you track RELENG_6_1 you will get no bug fixes in general - security related items to filter back down but in general bug reports posted against a -RELEASE are, if addressed, put into -STABLE. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 19:10:32 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 EAA6716A40F for ; Sun, 10 Sep 2006 19:10:32 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49FF343D73 for ; Sun, 10 Sep 2006 19:10:29 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k8AJARbi099809 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 10 Sep 2006 21:10:27 +0200 (CEST) (envelope-from stb@lassitu.de) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Stefan Bethke Date: Sun, 10 Sep 2006 21:10:26 +0200 X-Mailer: Apple Mail (2.752.2) Subject: Still possible to directly boot without loader? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:10:33 -0000 I just tried to load my standard kernel from the boot blocks (instead of using loader(8)), but I either get a hang before the kernel prints anything, or a BTX halted. Is this still supposed to work in 6- stable, or has it finally disappeared? Thanks, Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 19: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 310B016A40F for ; Sun, 10 Sep 2006 19:14:01 +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 7455A43DC5 for ; Sun, 10 Sep 2006 19:13:24 +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 9A9E41A4D8D; Sun, 10 Sep 2006 12:13:24 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1C0B5513F0; Sun, 10 Sep 2006 15:13:24 -0400 (EDT) Date: Sun, 10 Sep 2006 15:13:24 -0400 From: Kris Kennaway To: Stefan Bethke Message-ID: <20060910191323.GA7721@xor.obsecurity.org> References: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: Still possible to directly boot without loader? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:14:01 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 09:10:26PM +0200, Stefan Bethke wrote: > I just tried to load my standard kernel from the boot blocks (instead =20 > of using loader(8)), but I either get a hang before the kernel prints =20 > anything, or a BTX halted. Is this still supposed to work in 6-=20 > stable, or has it finally disappeared? Without access to the device.hints (either from loader or compiled in) you won't have a working console (and possibly other devices), so the kernel may appear to hang while booting. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBGPTWry0BWjoQKURAp9nAKDn6L59SvK0wMO/sYQRtO2R3I4ixACbBEMu nRtzAn/EXKK//zIjEhPpKJ8= =3k9L -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 19:25: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 9B01116A566 for ; Sun, 10 Sep 2006 19:25:40 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7246343D69 for ; Sun, 10 Sep 2006 19:24:52 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k8AJOosg000258 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Sun, 10 Sep 2006 21:24:51 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20060910191323.GA7721@xor.obsecurity.org> References: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> <20060910191323.GA7721@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <8D05EC30-27A0-418B-B91F-DBA26C797F11@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Sun, 10 Sep 2006 21:24:50 +0200 To: Kris Kennaway X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: Still possible to directly boot without loader? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:25:40 -0000 Am 10.09.2006 um 21:13 schrieb Kris Kennaway: > On Sun, Sep 10, 2006 at 09:10:26PM +0200, Stefan Bethke wrote: >> I just tried to load my standard kernel from the boot blocks (instead >> of using loader(8)), but I either get a hang before the kernel prints >> anything, or a BTX halted. Is this still supposed to work in 6- >> stable, or has it finally disappeared? > > Without access to the device.hints (either from loader or compiled in) > you won't have a working console (and possibly other devices), so the > kernel may appear to hang while booting. Ah, thanks! I'll try building a self-contained kernel then... Cheers, Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 19:44: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 8A05616A416 for ; Sun, 10 Sep 2006 19:44:00 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C952F43D68 for ; Sun, 10 Sep 2006 19:43:59 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 7612B290407 for ; Sun, 10 Sep 2006 16:43:56 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 20458-02 for ; Sun, 10 Sep 2006 19:43:59 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 0456F290406 for ; Sun, 10 Sep 2006 16:43:56 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 15D4E5C2F4; Sun, 10 Sep 2006 16:44:00 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0F47C48D4F for ; Sun, 10 Sep 2006 16:44:00 -0300 (ADT) Date: Sun, 10 Sep 2006 16:44:00 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060910164158.C1031@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: check if file system is clean ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:44:00 -0000 I checked both fsck and fsck_ffs man page, and don't see anything in either ... is there some way I can check if a file system is actually 'clean', without running fsck? ---- 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 Sun Sep 10 19:52: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 E8CBA16A415 for ; Sun, 10 Sep 2006 19:52:18 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40F8843D45 for ; Sun, 10 Sep 2006 19:52:18 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 1030F290406 for ; Sun, 10 Sep 2006 16:52:15 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 22683-02 for ; Sun, 10 Sep 2006 19:52:18 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 83512290401 for ; Sun, 10 Sep 2006 16:52:14 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id DE2DC354CD; Sun, 10 Sep 2006 16:52:18 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D956933DF1 for ; Sun, 10 Sep 2006 16:52:18 -0300 (ADT) Date: Sun, 10 Sep 2006 16:52:18 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060910165049.O1031@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Neat error ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:52:19 -0000 Not sure if there is anything thta I can do with this, no dump and it crashes, so no DDB ... but figured I'd post it ... Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, length=16384)]error = 5 Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, length=16384)]error = 5 Sep 10 16:49:34 jupiter kernel: g_vfs_done(): Sep 10 16:49:34 jupiter kernel: da0s1g[READ(offset=-2048 Sep 10 16:49:34 jupiter kernel: , length=1638o Sep 10 16:49:34 jupiter kernel: )]error = 5 Sep 10 16:49:34 jupiter kernel: Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, length=16384)]error = 5 Sep 10 16:49:34 jupiter kernel: Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, length=16384)]error = 5 Sep 10 16:49:34 jupiter last message repeated 2 times Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset= Sep 10 16:49:34 jupiter kernel: -2048, length=163 Sep 10 16:49:34 jupiter kernel: 84)]error = 5 Sep 10 16:49:34 jupiter kernel: Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, length=16384)]error = 5 Sep 10 16:49:34 jupiter kernel: g_vfs_done():d Sep 10 16:49:34 jupiter kernel: a0s1g[READ(o1 Sep 10 16:49:34 jupiter kernel: fset=-2048, l Sep 10 16:49:34 jupiter kernel: ength=16384)e ---- 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 Sun Sep 10 19:53: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 E088216A40F for ; Sun, 10 Sep 2006 19:53:08 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from mxfep02.bredband.com (mxfep02.bredband.com [195.54.107.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id D194243D72 for ; Sun, 10 Sep 2006 19:52:56 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from moria.endor.swagman.org ([213.113.4.185] [213.113.4.185]) by mxfep02.bredband.com with ESMTP id <20060910191516.CMKB12418.mxfep02.bredband.com@moria.endor.swagman.org> for ; Sun, 10 Sep 2006 21:15:16 +0200 Received: from rivendell (rivendell.endor.swagman.org [192.168.10.10]) by moria.endor.swagman.org (Postfix) with SMTP id B993CC for ; Sun, 10 Sep 2006 22:14:55 +0300 (EEST) Message-ID: <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> From: "Reko Turja" To: References: <20060909182831.GA32004@FS.denninger.net><200609100159.k8A1xAIn089481@drugs.dv.isc.org><20060910150526.GA31323@FS.denninger.net><20060910151817.H8856@psg.com><20060910181331.GA35166@FS.denninger.net><20060910183631.GA6406@xor.obsecurity.org> <20060910183958.GA35701@FS.denninger.net> Date: Sun, 10 Sep 2006 22:15:20 +0300 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.2962 Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 19:53:09 -0000 From: "Karl Denninger" To: Sent: Sunday, September 10, 2006 9:39 PM > Yes it is, in the general case; in any event if you track RELENG_6_1 > you will > get no bug fixes in general - security related items to filter back > down but > in general bug reports posted against a -RELEASE are, if addressed, > put into > -STABLE. You would like untested fixes to hit the release version first? By the way, possible breakage of STABLE due MFC process was announced a good while ago... -Reko From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 19:54: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 1CFE316A415 for ; Sun, 10 Sep 2006 19:54:22 +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 F393D43DBB for ; Sun, 10 Sep 2006 19:53:58 +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 BA31F1A4D8D; Sun, 10 Sep 2006 12:53:58 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 38B32515C0; Sun, 10 Sep 2006 15:53:58 -0400 (EDT) Date: Sun, 10 Sep 2006 15:53:58 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060910195358.GA8499@xor.obsecurity.org> References: <20060910165049.O1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga" Content-Disposition: inline In-Reply-To: <20060910165049.O1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: Neat error ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 19:54:22 -0000 --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 04:52:18PM -0300, Marc G. Fournier wrote: >=20 > Not sure if there is anything thta I can do with this, no dump and it=20 > crashes, so no DDB ... but figured I'd post it ... >=20 > Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=3D-2048,= =20 > length=3D16384)]error =3D 5 > Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=3D-2048,= =20 > length=3D16384)]error =3D 5 > Sep 10 16:49:34 jupiter kernel: g_vfs_done(): > Sep 10 16:49:34 jupiter kernel: da0s1g[READ(offset=3D-2048 > Sep 10 16:49:34 jupiter kernel: , length=3D1638o > Sep 10 16:49:34 jupiter kernel: )]error =3D 5 What do you expect us to do about your failing hard disk? :) Kris --opJtzjQTFsWo+cga Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBG1VWry0BWjoQKURAjC/AJ4ny5SjiLv3gyqZdWsS/VSuMEm2hwCgii4v IVEuIvUdbOTRuCjvBsHQa2s= =EtZ5 -----END PGP SIGNATURE----- --opJtzjQTFsWo+cga-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 20:11: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 9B2B416A40F for ; Sun, 10 Sep 2006 20:11:26 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCDBC43D5A for ; Sun, 10 Sep 2006 20:11:23 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k8AKBMYa022445 for ; Sun, 10 Sep 2006 20:11:22 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k8AKBMd8022442 for ; Sun, 10 Sep 2006 20:11:22 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Sun, 10 Sep 2006 20:11:22 +0000 (GMT) From: Michael Abbott To: freebsd-stable@freebsd.org In-Reply-To: <20060910181331.GA35166@FS.denninger.net> Message-ID: <20060910200554.J22428@saturn.araneidae.co.uk> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 20:11:26 -0000 >> You can track changes to a particular release - say by using >> RELENG_6_1 rather than RELENG_6. In which case, would you still >> say you are tracking STABLE? > If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > tracking -STABLE. Damn, I'm confused now. Let me try and get this straight: CURRENT This is, by definition, broken a good part of the time, and is what it says, namely current, ie work in progress. STABLE This is broken some of the time and .. uh .. isn't really all that stable, actually. RELENG_n_m This is completely stable and only tracks security fixes. RELENG_n (RELENG_6 at the moment) Has somebody just said that RELENG_6 = STABLE? I'm going to guess then that RELENG_7 is CURRENT. No, this doesn't make sense to me at all. > Indeed, the current tag on my CVS tree is TRELENG_6! Eh? T? From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 20:25: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 D15E116A416 for ; Sun, 10 Sep 2006 20:25:58 +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 B7FE343D66 for ; Sun, 10 Sep 2006 20:25:51 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd3mr1so.prod.shaw.ca (pd3mr1so-qfe3.prod.shaw.ca [10.0.141.177]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J5E00B848NC5L90@l-daemon> for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 14:23:36 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd3mr1so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J5E00IJM8NCNCB0@pd3mr1so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 14:23:36 -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 <0J5E00H8D8NBZOL0@l-daemon> for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 14:23:36 -0600 (MDT) Received: (qmail 15288 invoked from network); Sun, 10 Sep 2006 20:23:27 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Sun, 10 Sep 2006 20:23:27 +0000 Date: Sun, 10 Sep 2006 13:23:27 -0700 From: Colin Percival In-reply-to: <20060910200554.J22428@saturn.araneidae.co.uk> To: Michael Abbott Message-id: <4504743F.1050406@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: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910200554.J22428@saturn.araneidae.co.uk> User-Agent: Thunderbird 1.5 (X11/20060416) Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 20:25:58 -0000 Michael Abbott wrote: > Damn, I'm confused now. Let me try and get this straight: > > CURRENT > This is, by definition, broken a good part of the time, and is what > it says, namely current, ie work in progress. Yes. > STABLE > This is broken some of the time and .. uh .. isn't really all that > stable, actually. "STABLE" means "you can update FreeBSD along this branch without needing to recompile applications or kernel modules". This means that companies can ship binary drivers for their hardware and say "this driver will work on FreeBSD 6.x" (which isn't possible on Linux). The fact that there are occasionally bugs introduced... well, that's an inevitable consequence of the stable branches being development branches. > RELENG_n_m > This is completely stable and only tracks security fixes. Security fixes and "critical errata". The requirements for something being committed to such a branch after the release are that: 1. It must be an important bugfix, and 2. I must be absolutely certain that nothing bad will ever happen as a result of someone updating a FreeBSD n.m system to the latest updates on RELENG_n_m. > RELENG_n (RELENG_6 at the moment) > Has somebody just said that RELENG_6 = STABLE? Yes. > I'm going to guess then that RELENG_7 is CURRENT. > No, this doesn't make sense to me at all. RELENG_7 doesn't exist yet. RELENG_7 will be 7-STABLE once it exists, some time in 2007. Colin Percival From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 20:26: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 B770F16A5A0 for ; Sun, 10 Sep 2006 20:26:05 +0000 (UTC) (envelope-from scottro@nyc.rr.com) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ED1C43D5E for ; Sun, 10 Sep 2006 20:26:04 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from localhost (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-02.rdc-nyc.rr.com (8.13.6/8.13.6) with ESMTP id k8AKQ3An027867 for ; Sun, 10 Sep 2006 16:26:03 -0400 (EDT) Date: Sun, 10 Sep 2006 16:26:03 -0400 From: Scott Robbins To: freebsd-stable@freebsd.org Message-ID: <20060910202603.GA56616@mail.scottro.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910200554.J22428@saturn.araneidae.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20060910200554.J22428@saturn.araneidae.co.uk> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 20:26:05 -0000 On Sun, Sep 10, 2006 at 08:11:22PM +0000, Michael Abbott wrote: > >>You can track changes to a particular release - say by using > >>RELENG_6_1 rather than RELENG_6. In which case, would you still > >>say you are tracking STABLE? > >If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > >tracking -STABLE. > > Damn, I'm confused now. Let me try and get this straight: Perhaps this might help? http://home.nyc.rr.com/computertaijutsu/release.html -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Well, that works out great. You won't tell anyone that I'm the Slayer, and I won't tell anyone you're a moron. From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 20:42: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 57F9316A417 for ; Sun, 10 Sep 2006 20:42:59 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp102.biz.mail.re2.yahoo.com (smtp102.biz.mail.re2.yahoo.com [68.142.229.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 73E2543D5C for ; Sun, 10 Sep 2006 20:42:58 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 57899 invoked from network); 10 Sep 2006 20:42:57 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp102.biz.mail.re2.yahoo.com with SMTP; 10 Sep 2006 20:42:57 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 34AFC61FA; Sun, 10 Sep 2006 16:43:01 -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 AGxSyFCnu59a; Sun, 10 Sep 2006 16:42:59 -0400 (EDT) Received: from [192.168.1.102] (unknown [192.168.1.102]) by optimator.noacks.org (Postfix) with ESMTP id D25AD61CE; Sun, 10 Sep 2006 16:42:59 -0400 (EDT) Message-ID: <450478C8.4000504@alumni.rice.edu> Date: Sun, 10 Sep 2006 16:42:48 -0400 From: Jonathan Noack User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: "Marc G. Fournier" References: <20060910164158.C1031@ganymede.hub.org> In-Reply-To: <20060910164158.C1031@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: check if file system is clean ... 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: Sun, 10 Sep 2006 20:42:59 -0000 Marc G. Fournier wrote: > I checked both fsck and fsck_ffs man page, and don't see anything in > either ... is there some way I can check if a file system is actually > 'clean', without running fsck? Google Groups revealed the following: http://lists.freebsd.org/pipermail/freebsd-questions/2003-June/008898.html [root@optimator:~] $ dumpfs /usr | grep clean cgrotor 512 fmod 0 ronly 0 clean 0 [root@optimator:~] $ Using dumpfs(8) for this purpose is a little like using a jackhammer to drive a nail into drywall; it Gets The Job Done but there sure is a lot of noise and heavy lifting... :) -Jonathan From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 21:04: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 DCEC916A40F for ; Sun, 10 Sep 2006 21:04:12 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (noop.in-addr.com [208.58.23.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E3AA43D4C for ; Sun, 10 Sep 2006 21:04:12 +0000 (GMT) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1GMWTL-000Cn7-PK; Sun, 10 Sep 2006 17:04:11 -0400 Date: Sun, 10 Sep 2006 17:04:11 -0400 From: Gary Palmer To: Michael Abbott Message-ID: <20060910210411.GA17002@in-addr.com> Mail-Followup-To: Michael Abbott , freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910200554.J22428@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910200554.J22428@saturn.araneidae.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 21:04:13 -0000 On Sun, Sep 10, 2006 at 08:11:22PM +0000, Michael Abbott wrote: > >Indeed, the current tag on my CVS tree is TRELENG_6! > > Eh? T? cd /usr/src cat CVS/Tag CVS places a "T" infront of the tag name in the Tag file. From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 22:09: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 9E59B16A415 for ; Sun, 10 Sep 2006 22:09:24 +0000 (UTC) (envelope-from rloef@forethought.net) Received: from mz2.forethought.net (mzpi4.forethought.net [216.241.36.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87CC043D46 for ; Sun, 10 Sep 2006 22:09:22 +0000 (GMT) (envelope-from rloef@forethought.net) Received: from 206-124-7-199.denver.dsl.forethought.net ([206.124.7.199] helo=auden.jmla.com) by mz2.forethought.net with esmtps (TLSv1:DES-CBC3-SHA:168) (Exim 4.51) id 1GMXUJ-00081h-Ml; Sun, 10 Sep 2006 16:09:15 -0600 Date: Sun, 10 Sep 2006 16:11:04 -0600 (MDT) From: Reed Loefgren X-X-Sender: rloef@auden.jmla.com To: Kris Kennaway In-Reply-To: <20060910195358.GA8499@xor.obsecurity.org> Message-ID: <20060910160211.H1517@auden.jmla.com> References: <20060910165049.O1031@ganymede.hub.org> <20060910195358.GA8499@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, "Marc G. Fournier" Subject: Re: Neat error ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 22:09:24 -0000 On Sun, 10 Sep 2006, Kris Kennaway wrote: > On Sun, Sep 10, 2006 at 04:52:18PM -0300, Marc G. Fournier wrote: >> >> Not sure if there is anything thta I can do with this, no dump and it >> crashes, so no DDB ... but figured I'd post it ... >> >> Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, >> length=16384)]error = 5 >> Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, >> length=16384)]error = 5 >> Sep 10 16:49:34 jupiter kernel: g_vfs_done(): >> Sep 10 16:49:34 jupiter kernel: da0s1g[READ(offset=-2048 >> Sep 10 16:49:34 jupiter kernel: , length=1638o >> Sep 10 16:49:34 jupiter kernel: )]error = 5 > > What do you expect us to do about your failing hard disk? :) > > Kris > Sight unseen, I'd concur on bad hardware. I earlier was bitten by the broken gmirror code and the only way I found out was that a failing disk froze the machine with just this sort of g_vfs_done() error. The disk was "Recertified" (thanks Western Digital for stellar warrantee behavior. Yeah), and was just waiting to do this to me. The reboot and mirror re-sync demonstrated the broken gmirror code, completely :) All in all, a very fun-filled Sunday. But it's rib roast tonight, and that will make it easier... r From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 22:27: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 8896B16A407 for ; Sun, 10 Sep 2006 22:27:43 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA27843D66 for ; Sun, 10 Sep 2006 22:27:08 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-012.eplus-online.de [212.23.126.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 8006333D21 for ; Mon, 11 Sep 2006 00:26:24 +0200 (CEST) Received: from [127.0.0.1] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 429342E546 for ; Mon, 11 Sep 2006 00:26:04 +0200 (CEST) Message-ID: <45049112.3@vwsoft.com> Date: Mon, 11 Sep 2006 00:26:26 +0200 From: Volker User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060910035614.282CD16A58D@hub.freebsd.org> In-Reply-To: <20060910035614.282CD16A58D@hub.freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 22:27:43 -0000 > This should be documented somewhere clearly then, as my understanding was that -STABLE meant that anything MFCd back to it *was* tested and deemed stable ... and yes, I do run stable, and yes, I do expect to hit the occasional 'oopses', but "blantant and obvious bugs due to insufficient testing", IMHO, doesn't classify as an 'oops' .... > Guys, we're talking about software. Have you ever seen a piece of software which has been really bug-free? Not the hello-world, I'm talking about real software. Also, you should never go with -STABLE on a production server. I'm sure this has been made clear in the handbook. If it's really a that import server in production use, go with a RELEASE. -STABLE is not a technology playground as CURRENT but should be seen as a BETA testing system. If that's not the case, then why use RELEASE at all? Sure you may blame a developer for not testing enough but you're on your own if you use beta quality software on your production systems. As a developer I've seen many bugs which haven't been found during testing and I know it's nearly impossible to find _all_ bugs while testing. I've seen applications failing just because the user typed the wrong key at the wrong time (or an unexpected key). As a user I'm thankful for bugs being fast fixed bugs but on the other side I really know what I'm doing when using -STABLE software on my system. I do see this as a give-back to the community to find bugs early before -RELEASE. Also keep in mind most kernel hackers do kernel hacking in their spare time. Everyone using FreeBSD (or any other OS system) is profiting from their spare time and it's unfair to be not that polite. And back to the issue: The gmirror bug has already been fixed and I posted a note to the ML hours before the first "who the f... did cause that bug" post. A short look into ML postings would have made this thread needless. If you blame developers, then please shut off your computer. my2ct Volker From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 22:51: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 8587616A40F for ; Sun, 10 Sep 2006 22:51:08 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189FE43D45 for ; Sun, 10 Sep 2006 22:51:08 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 59FCB290405; Sun, 10 Sep 2006 19:51:03 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 78099-03; Sun, 10 Sep 2006 22:51:08 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id B9635290401; Sun, 10 Sep 2006 19:51:02 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 51F5B3583C; Sun, 10 Sep 2006 19:51:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 512E1344CF; Sun, 10 Sep 2006 19:51:10 -0300 (ADT) Date: Sun, 10 Sep 2006 19:51:10 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Kris Kennaway In-Reply-To: <20060910195358.GA8499@xor.obsecurity.org> Message-ID: <20060910195013.W1031@ganymede.hub.org> References: <20060910165049.O1031@ganymede.hub.org> <20060910195358.GA8499@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Neat error ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 10 Sep 2006 22:51:08 -0000 On Sun, 10 Sep 2006, Kris Kennaway wrote: > On Sun, Sep 10, 2006 at 04:52:18PM -0300, Marc G. Fournier wrote: >> >> Not sure if there is anything thta I can do with this, no dump and it >> crashes, so no DDB ... but figured I'd post it ... >> >> Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, >> length=16384)]error = 5 >> Sep 10 16:49:34 jupiter kernel: g_vfs_done():da0s1g[READ(offset=-2048, >> length=16384)]error = 5 >> Sep 10 16:49:34 jupiter kernel: g_vfs_done(): >> Sep 10 16:49:34 jupiter kernel: da0s1g[READ(offset=-2048 >> Sep 10 16:49:34 jupiter kernel: , length=1638o >> Sep 10 16:49:34 jupiter kernel: )]error = 5 > > What do you expect us to do about your failing hard disk? :) Just what you did ... confirm that that is what it is :) Thank you ... one way to get rid of the 'hanging file system with iir driver issue' ... hard way, but it does it :) ---- 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 Sun Sep 10 23:33: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 950D516A415 for ; Sun, 10 Sep 2006 23:33:30 +0000 (UTC) (envelope-from parv@pair.com) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F4E543D5D for ; Sun, 10 Sep 2006 23:33:27 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([69.160.66.115]) by mta10.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060910233326.HKLH27224.mta10.adelphia.net@default.chvlva.adelphia.net>; Sun, 10 Sep 2006 19:33:26 -0400 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id 0E502B5D9; Sun, 10 Sep 2006 19:33:26 -0400 (EDT) Date: Sun, 10 Sep 2006 19:33:25 -0400 From: "'Anubhav A.'" To: Volker Message-ID: <20060910233325.GA3845@holestein.holy.cow> Mail-Followup-To: Volker , freebsd-stable@freebsd.org References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45049112.3@vwsoft.com> Cc: freebsd-stable@freebsd.org Subject: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 23:33:30 -0000 in message <45049112.3@vwsoft.com>, wrote Volker thusly... > > we're talking about software. Have you ever seen a piece of software which has > been really bug-free? Not the hello-world, I'm talking Recently i read about which is more than "hello-world" ... They Write the Right Stuff http://www.fastcompany.com/online/06/writestuff.html ... but you did ask. - Parv -- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 10 23:57: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 771DE16A407 for ; Sun, 10 Sep 2006 23:57:09 +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 33D3143D45 for ; Sun, 10 Sep 2006 23:57:09 +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 CE96E1A3C20; Sun, 10 Sep 2006 16:57:08 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 83864515F4; Sun, 10 Sep 2006 19:57:07 -0400 (EDT) Date: Sun, 10 Sep 2006 19:57:07 -0400 From: Kris Kennaway To: Volker , freebsd-stable@freebsd.org Message-ID: <20060910235707.GA13170@xor.obsecurity.org> References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <20060910233325.GA3845@holestein.holy.cow> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 10 Sep 2006 23:57:09 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 07:33:25PM -0400, 'Anubhav A.' wrote: > in message <45049112.3@vwsoft.com>, wrote Volker thusly... > > > > we're talking about software. Have you ever seen a piece of software wh= ich has > > been really bug-free? Not the hello-world, I'm talking >=20 > Recently i read about which is more than "hello-world" ... >=20 > They Write the Right Stuff > http://www.fastcompany.com/online/06/writestuff.html >=20 >=20 > ... but you did ask. -- This software is bug-free. It is perfect, as perfect as human beings have achieved. Consider these stats : the last three versions of the program -- each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. -- But that just proves the point: despite all that careful engineering, "one error each" and "a total of 17 errors" !=3D "bug-free". Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBKZSWry0BWjoQKURAge6AKDSwkui80ikXHfJP8R3Yu30fTnDZwCg4BYC 0zmQXTMcyZ8vErc/RwRwAuY= =tAxl -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:07: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 C5BDC16A40F for ; Mon, 11 Sep 2006 00:07:04 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2658F43D49 for ; Mon, 11 Sep 2006 00:07:04 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-012.eplus-online.de [212.23.126.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 37C9333D21 for ; Mon, 11 Sep 2006 02:06:55 +0200 (CEST) Received: from [127.0.0.1] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id 9A70B2E546; Mon, 11 Sep 2006 02:06:28 +0200 (CEST) Message-ID: <4504A89A.5070400@vwsoft.com> Date: Mon, 11 Sep 2006 02:06:50 +0200 From: Volker User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Volker , freebsd-stable@freebsd.org References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> In-Reply-To: <20060910233325.GA3845@holestein.holy.cow> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: Subject: Re: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 00:07:04 -0000 On 2006-09-11 01:33, 'Anubhav A.' wrote: > in message <45049112.3@vwsoft.com>, wrote Volker thusly... >> we're talking about software. Have you ever seen a piece of software which has >> been really bug-free? Not the hello-world, I'm talking > > Recently i read about which is more than "hello-world" ... > > They Write the Right Stuff > http://www.fastcompany.com/online/06/writestuff.html > > > ... but you did ask. > > > - Parv > Interesting article but I really do not believe even the shuttle software is 100% bug free. Just because there has been only one bug found in the last version, does not mean it's really guaranteed to be bug free. It's just: No one experienced one and no one discovered one more. On the other side they do not implement much new features every day and they do not have to care about hardware and market changes every other day. I suspect a lot of trouble even for NASA's mission does come from software bugs and who knows how many lifes can be accounted for software bugs. Remembering the first launch of a Ariane-5 rocket? It has been self destroyed because of nothing but a software bug. Or what about the first NAVY combat ship w/ steering controlled by Windows NT? Out of control by a blue screen... A developer can't always foresee the environment where his code will later work in and that is even causing trouble. And again, errors and mistakes are human. And those who shout out "why didn't you test enough" should ask themself, how much have THEY contributed to the community? The hackers are contributing enough (my view) and are really doing a good job. I do not care about HOW MANY bugs a beta quality piece of software does contain but what IMHO matters is the timeframe to FIX them and the FreeBSD project and other OS communities are good in that. Greetings, Volker From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:11: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 3C4BC16A63F for ; Mon, 11 Sep 2006 00:11:19 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9964E43D46 for ; Mon, 11 Sep 2006 00:11:18 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8B0BHlr044969 for ; Sun, 10 Sep 2006 19:11:17 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 19:11:17 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8B0BHgw044967 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 19:11:17 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 19:11:17 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060911001117.GA44739@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060910183958.GA35701@FS.denninger.net> <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 00:11:19 -0000 On Sun, Sep 10, 2006 at 10:15:20PM +0300, Reko Turja wrote: > From: "Karl Denninger" > To: > Sent: Sunday, September 10, 2006 9:39 PM > >Yes it is, in the general case; in any event if you track RELENG_6_1 > >you will > >get no bug fixes in general - security related items to filter back > >down but > >in general bug reports posted against a -RELEASE are, if addressed, > >put into > >-STABLE. > > You would like untested fixes to hit the release version first? By the > way, possible breakage of STABLE due MFC process was announced a good > while ago... No, I would like -STABLE to be treated as what it is claimed to be - BETA code, not ALPHA code. There's a huge difference between the two, and MFCing something back to -STABLE without testing the functionality of the module you're working with first does not fit the BETA model (it DOES fit the Alpha model.) This is coming from someone who has run FreeBSD in a production environment for basically 10 years, and has even sometimes used -CURRENT during that time (with full knowledge that running THAT is, indeed, ALPHA code!) -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:13: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 0099716A407 for ; Mon, 11 Sep 2006 00:13:50 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E599343D6E for ; Mon, 11 Sep 2006 00:13:46 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8B0DkD1045043 for ; Sun, 10 Sep 2006 19:13:46 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 19:13:46 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8B0Dkr9045040 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 19:13:46 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 19:13:46 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060911001346.GB44739@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910200554.J22428@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910200554.J22428@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 00:13:50 -0000 On Sun, Sep 10, 2006 at 08:11:22PM +0000, Michael Abbott wrote: > >>You can track changes to a particular release - say by using > >>RELENG_6_1 rather than RELENG_6. In which case, would you still > >>say you are tracking STABLE? > >If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > >tracking -STABLE. > > Damn, I'm confused now. Let me try and get this straight: > > CURRENT > This is, by definition, broken a good part of the time, and is > what it says, namely current, ie work in progress. > > STABLE > This is broken some of the time and .. uh .. isn't really all that > stable, actually. > > RELENG_n_m > This is completely stable and only tracks security fixes. Incorrect. This is "completely FIXED", which is not the same thing as STABLE. "Fixed in a broken state" is still broken, aka the serial I/O problems in 6.x that I've found (and for which there is apparently no current fix in any of the branches of 6.x.) > RELENG_n (RELENG_6 at the moment) > Has somebody just said that RELENG_6 = STABLE? I'm going to guess > then that RELENG_7 is CURRENT. > No, this doesn't make sense to me at all. > > >Indeed, the current tag on my CVS tree is TRELENG_6! > > Eh? T? As in "Tag", which is the syntax that acutally shows up in the "CVS" directory under the source tree. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:22: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 411B816A412 for ; Mon, 11 Sep 2006 00:22:52 +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 B707243D45 for ; Mon, 11 Sep 2006 00:22:51 +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 k8B0HN6v063767 for ; Mon, 11 Sep 2006 02:17:23 +0200 (CEST) (envelope-from amon@sockar.homeip.net) Received: (from amon@localhost) by sockar.homeip.net (8.13.4/8.13.3/Submit) id k8B0HMHf063766 for freebsd-stable@freebsd.org; Mon, 11 Sep 2006 02:17:22 +0200 (CEST) (envelope-from amon) Date: Mon, 11 Sep 2006 02:17:22 +0200 From: Herve Boulouis To: freebsd-stable@freebsd.org Message-ID: <20060911001722.GR611@ra.aabs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: bge watchdog timeouts still happening X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 00:22:52 -0000 Hi, I've recently put into production 2 web servers with 6.0-STABLE from mid january and was bitten by the bge watchdog timeouts problems. I cvsupped the 2 boxes with the latest -stable (latest if_bge.c, rev 1.91.2.17) but the problem still persists :( Server hardware is Dell poweredge 2550 with SMP kernel. Relevant portion of dmesg : bge0: mem 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:06:5b:1a:7f:4a On the first box, the load is quite light so the problem as not yet re-appaeared since the upgrade. On the 2d box, which usually outputs 10-15 Mbit/s, the timeouts came back very shortly after the ugprade. Extract of logs from the 2d box : (uptime < 1h) Sep 11 01:19:50 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:19:50 www1 kernel: bge0: link state changed to DOWN Sep 11 01:19:54 www1 kernel: bge0: link state changed to UP Sep 11 01:26:10 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:26:10 www1 kernel: bge0: link state changed to DOWN Sep 11 01:26:13 www1 kernel: bge0: link state changed to UP Sep 11 01:27:32 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:27:32 www1 kernel: bge0: link state changed to DOWN Sep 11 01:27:35 www1 kernel: bge0: link state changed to UP Sep 11 01:28:52 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:28:52 www1 kernel: bge0: link state changed to DOWN Sep 11 01:28:55 www1 kernel: bge0: link state changed to UP Sep 11 01:31:12 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:31:12 www1 kernel: bge0: link state changed to DOWN Sep 11 01:31:15 www1 kernel: bge0: link state changed to UP Sep 11 01:33:57 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:33:57 www1 kernel: bge0: link state changed to DOWN Sep 11 01:34:00 www1 kernel: bge0: link state changed to UP Sep 11 01:34:16 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:34:16 www1 kernel: bge0: link state changed to DOWN Sep 11 01:34:19 www1 kernel: bge0: link state changed to UP Sep 11 01:34:41 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:34:41 www1 kernel: bge0: link state changed to DOWN Sep 11 01:34:44 www1 kernel: bge0: link state changed to UP Sep 11 01:35:06 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:35:06 www1 kernel: bge0: link state changed to DOWN Sep 11 01:35:09 www1 kernel: bge0: link state changed to UP Sep 11 01:36:17 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:36:17 www1 kernel: bge0: link state changed to DOWN Sep 11 01:36:20 www1 kernel: bge0: link state changed to UP Sep 11 01:37:47 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:37:47 www1 kernel: bge0: link state changed to DOWN Sep 11 01:37:50 www1 kernel: bge0: link state changed to UP Sep 11 01:38:53 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:38:53 www1 kernel: bge0: link state changed to DOWN Sep 11 01:38:56 www1 kernel: bge0: link state changed to UP Sep 11 01:39:56 www1 kernel: bge0: watchdog timeout -- resetting Sep 11 01:39:56 www1 kernel: bge0: link state changed to DOWN Sep 11 01:39:59 www1 kernel: bge0: link state changed to UP I've removed 'options SMP' from the kernel config of the loaded box but the timeouts continue to happen. What can I do to help resolve this bug ? -- Herve Boulouis From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:25: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 5C70A16A407 for ; Mon, 11 Sep 2006 00:25:30 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout07-04.prod.mesa1.secureserver.net (smtpout07-01.prod.mesa1.secureserver.net [64.202.165.230]) by mx1.FreeBSD.org (Postfix) with SMTP id 179FA43D68 for ; Mon, 11 Sep 2006 00:25:26 +0000 (GMT) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 28221 invoked from network); 11 Sep 2006 00:25:26 -0000 Received: from unknown (24.144.77.138) by smtpout07-04.prod.mesa1.secureserver.net (64.202.165.233) with ESMTP; 11 Sep 2006 00:25:26 -0000 Message-ID: <4504ACF5.6050303@seclark.us> Date: Sun, 10 Sep 2006 20:25:25 -0400 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Volker References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> <4504A89A.5070400@vwsoft.com> In-Reply-To: <4504A89A.5070400@vwsoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 00:25:30 -0000 Volker wrote: >On 2006-09-11 01:33, 'Anubhav A.' wrote: > > >>in message <45049112.3@vwsoft.com>, wrote Volker thusly... >> >> >>>we're talking about software. Have you ever seen a piece of software which has >>>been really bug-free? Not the hello-world, I'm talking >>> >>> >>Recently i read about which is more than "hello-world" ... >> >> They Write the Right Stuff >> http://www.fastcompany.com/online/06/writestuff.html >> >> >>... but you did ask. >> >> >> - Parv >> >> >> > >Interesting article but I really do not believe even the shuttle >software is 100% bug free. Just because there has been only one bug >found in the last version, does not mean it's really guaranteed to >be bug free. It's just: No one experienced one and no one discovered >one more. On the other side they do not implement much new features >every day and they do not have to care about hardware and market >changes every other day. > >I suspect a lot of trouble even for NASA's mission does come from >software bugs and who knows how many lifes can be accounted for >software bugs. Remembering the first launch of a Ariane-5 rocket? It >has been self destroyed because of nothing but a software bug. Or >what about the first NAVY combat ship w/ steering controlled by >Windows NT? Out of control by a blue screen... > >A developer can't always foresee the environment where his code will >later work in and that is even causing trouble. > >And again, errors and mistakes are human. And those who shout out >"why didn't you test enough" should ask themself, how much have THEY >contributed to the community? The hackers are contributing enough >(my view) and are really doing a good job. > >I do not care about HOW MANY bugs a beta quality piece of software >does contain but what IMHO matters is the timeframe to FIX them and >the FreeBSD project and other OS communities are good in that. > >Greetings, > >Volker >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > Sorry to be dense but what does MFCing mean. I have googled for it but can find nothing that explains it. Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:37: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 295CE16A40F for ; Mon, 11 Sep 2006 00:37:38 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.ipactive.de [85.214.39.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79EF43D45 for ; Mon, 11 Sep 2006 00:37:37 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (gprs-pool-1-012.eplus-online.de [212.23.126.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id A8E6433D21 for ; Mon, 11 Sep 2006 02:37:31 +0200 (CEST) Received: from [127.0.0.1] (cesar.sz.vwsoft.com [192.168.16.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id ED9A72E54D; Mon, 11 Sep 2006 02:37:14 +0200 (CEST) Message-ID: <4504AFD1.2070703@vwsoft.com> Date: Mon, 11 Sep 2006 02:37:37 +0200 From: Volker User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Stephen.Clark@seclark.us References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> <4504A89A.5070400@vwsoft.com> <4504ACF5.6050303@seclark.us> In-Reply-To: <4504ACF5.6050303@seclark.us> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-stable@freebsd.org Subject: Re: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 00:37:38 -0000 On 2006-09-11 02:25, Stephen Clark wrote: > Sorry to be dense but what does MFCing mean. I have googled for it but > can find > nothing that explains it. > > Thanks, > Steve > Steve, MFC means "merge from current" (read as: merge from CURRENT [HEAD] cvs tree into the current -STABLE tree). I'm seeing -CURRENT as a playground for new features, technologies and support for latest hardware. If something has worked out there, the changes are merged from the -CURRENT tree into the (non-release) -STABLE tree. -STABLE has a broader audience and mistakes will probably being detected there. At a time before RELEASE date the -STABLE tree is being frozen (no new features are allowed to be merged into -STABLE) and after a testing phase (BETA / PRE-RELEASE) the code will be released. Greetings, Volker From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 01:19: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 DA67416A403 for ; Mon, 11 Sep 2006 01:19:34 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EA7143D49 for ; Mon, 11 Sep 2006 01:19:34 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so1782705pye for ; Sun, 10 Sep 2006 18:19:34 -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:content-transfer-encoding; b=JpWYmeohbo7touRAU66Wwx3nV4lDBJIYs8EPJ5PzJaF7LwQtNhBhSN/3OgwTGNDjS01kECITgxmUxQzmB7o1211wko8EisYXc1rQCA2uRiZAIFSqHc18wY79pSs42HQ6drteH/omZ6oqhPUL5fnp6QPZyfRhB8OHJnEJqAShUpU= Received: by 10.65.176.7 with SMTP id d7mr1222967qbp; Sun, 10 Sep 2006 18:19:33 -0700 (PDT) Received: from sauron.lan.box ( [200.203.39.168]) by mx.gmail.com with ESMTP id e15sm624964qbe.2006.09.10.18.19.32; Sun, 10 Sep 2006 18:19:33 -0700 (PDT) Date: Sun, 10 Sep 2006 22:19:30 -0300 From: Ricardo Nabinger Sanchez To: freebsd-stable@freebsd.org Message-Id: <20060910221930.735d2624.rnsanchez@gmail.com> In-Reply-To: <4504AFD1.2070703@vwsoft.com> References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> <4504A89A.5070400@vwsoft.com> <4504ACF5.6050303@seclark.us> <4504AFD1.2070703@vwsoft.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [OT] Re: Bug-free software (Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 01:19:34 -0000 On Mon, 11 Sep 2006 02:37:37 +0200, Volker wrote: > MFC means "merge from current" (read as: merge from CURRENT [HEAD] > cvs tree into the current -STABLE tree). Way off-topic: I had a patch around my stuff to add this (and some others I don't remember now) to the wtf (1) base, or even a "FreeBSD Glossary" section in the handbook. It certainly wouldn't hurt to have one, and at least me would thank the brave fellow who did it :) -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 02:02: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 D9ED116A40F for ; Mon, 11 Sep 2006 02:02:30 +0000 (UTC) (envelope-from jfarmer@goldsword.com) Received: from imf22aec.mail.bellsouth.net (imf22aec.mail.bellsouth.net [205.152.59.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A30643D45 for ; Mon, 11 Sep 2006 02:02:30 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from ibm67aec.bellsouth.net ([65.13.105.239]) by imf22aec.mail.bellsouth.net with ESMTP id <20060911020229.VFDZ22536.imf22aec.mail.bellsouth.net@ibm67aec.bellsouth.net> for ; Sun, 10 Sep 2006 22:02:29 -0400 Received: from [192.168.1.33] (really [65.13.105.239]) by ibm67aec.bellsouth.net with ESMTP id <20060911020227.LPUM2428.ibm67aec.bellsouth.net@[192.168.1.33]> for ; Sun, 10 Sep 2006 22:02:27 -0400 Message-ID: <4504C3B7.7090400@goldsword.com> Date: Sun, 10 Sep 2006 22:02:31 -0400 From: "J. T. Farmer" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> In-Reply-To: <45049112.3@vwsoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 02:02:30 -0000 Volker wrote: >> This should be documented somewhere clearly then, as my understanding was that -STABLE meant that anything MFCd back to it *was* tested and deemed stable ... and yes, I do run stable, and yes, I do expect to hit the occasional 'oopses', but "blantant and obvious bugs due to insufficient testing", IMHO, doesn't classify as an 'oops' .... >> >> > > Guys, > > we're talking about software. Have you ever seen a piece of software > which has been really bug-free? Not the hello-world, I'm talking > about real software. > > Also, you should never go with -STABLE on a production server. I'm > sure this has been made clear in the handbook. If it's really a that > import server in production use, go with a RELEASE. -STABLE is not a > technology playground as CURRENT but should be seen as a BETA > testing system. If that's not the case, then why use RELEASE at all? > Pardon me, but I do have to interject a very large laugh here. What's the first recommendation that's made _every_ time someone posts a problem with a -RELEASE installation? It's "Well, go update to -STABLE and then we will might be able to help you." Simply put, running a -RELEASE means that you _are_ running software with _known_ problems. I'm very thankful for all the work that people put into FreeBSD. However, that doesn't blind me to problems with the current setup. It may be the best that we have, it may be better than the Linux world, but that doesn't mean that it solves all our problems and that we can't improve it. John (FreeBSD since 2.0.x on an AMD K5-100 with 16MB of ram...) ------------------------------------------------------------------ John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 02:07:47 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 532ED16A403 for ; Mon, 11 Sep 2006 02:07:47 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (linda-3.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC70F43D46 for ; Mon, 11 Sep 2006 02:07:46 +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 <0J5E00LYBOKU8O@linda-3.paradise.net.nz> for freebsd-stable@freebsd.org; Mon, 11 Sep 2006 14:07:42 +1200 (NZST) Received: from [192.168.1.11] (218-101-29-47.dsl.clear.net.nz [218.101.29.47]) by smtp-2.paradise.net.nz (Postfix) with ESMTP id 27953CA4210 for ; Mon, 11 Sep 2006 14:07:42 +1200 (NZST) Date: Mon, 11 Sep 2006 14:07:25 +1200 From: Mark Kirkwood In-reply-to: <20060911001117.GA44739@FS.denninger.net> To: freebsd-stable@freebsd.org Message-id: <4504C4DD.5020902@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.0.4 (X11/20060704) References: <20060910183958.GA35701@FS.denninger.net> <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> <20060911001117.GA44739@FS.denninger.net> Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 11 Sep 2006 02:07:47 -0000 Karl Denninger wrote: > > > > No, I would like -STABLE to be treated as what it is claimed to be - BETA > code, not ALPHA code. > > There's a huge difference between the two, and MFCing something back to > -STABLE without testing the functionality of the module you're working > with first does not fit the BETA model (it DOES fit the Alpha model.) > > This is coming from someone who has run FreeBSD in a production environment > for basically 10 years, and has even sometimes used -CURRENT during that time > (with full knowledge that running THAT is, indeed, ALPHA code!) > > I guess part of the problem is not enough of us running -CURRENT, so bugs can slip through into -STABLE via MFC (I know I'm guilty here - 2 boxes running -STABLE, none on -CURRENT....) Cheers Mark From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 03:34: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 67A3416A40F for ; Mon, 11 Sep 2006 03:34:42 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2547D43D55 for ; Mon, 11 Sep 2006 03:34:41 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so421951nzn for ; Sun, 10 Sep 2006 20:34:40 -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:content-transfer-encoding; b=kkldiAFRgCO7HcTBA9epFOve5xCgqdaok9uN2mxkZQFlht/UmrFK4VSOIq9QtQpybrQqSmxSb4lNj3bGbkrFPvoRR4WnTERePHAPNVMCuqKAh+hheGgmgPxqqT0iz9dfaoqrT5x8cRpHoXhMowWtUsZRiKF1BJSuGv7m4fd6lgM= Received: by 10.64.209.6 with SMTP id h6mr1301300qbg; Sun, 10 Sep 2006 20:34:39 -0700 (PDT) Received: from sauron.lan.box ( [200.203.39.168]) by mx.gmail.com with ESMTP id e17sm4084739qbe.2006.09.10.20.34.38; Sun, 10 Sep 2006 20:34:39 -0700 (PDT) Date: Mon, 11 Sep 2006 00:34:36 -0300 From: Ricardo Nabinger Sanchez To: Lowell Gilbert Message-Id: <20060911003436.f2150578.rnsanchez@gmail.com> In-Reply-To: <44d5a3w5sv.fsf_-_@be-well.ilk.org> References: <20060910035614.282CD16A58D@hub.freebsd.org> <45049112.3@vwsoft.com> <20060910233325.GA3845@holestein.holy.cow> <4504A89A.5070400@vwsoft.com> <4504ACF5.6050303@seclark.us> <4504AFD1.2070703@vwsoft.com> <20060910221930.735d2624.rnsanchez@gmail.com> <44d5a3w5sv.fsf_-_@be-well.ilk.org> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: [OT] Re: Bug-free software X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 03:34:42 -0000 On Sun, 10 Sep 2006 21:28:00 -0400, Lowell Gilbert wrote: > It *is* in the Handbook's glossary. Geez. I can't believe all those times I've searched for the FreeBSD jargon, the glossary *never* appeared in my results, so I'm getting to know it right now, after your comment. As I own a copy of Greg's "The Complete FreeBSD", I rarely check the online handbook. Shame on me. Well, now I've bookmarked it (glossary). Thanks for the tip, and sorry for the noise. -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 08:38: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 5123016A415 for ; Mon, 11 Sep 2006 08:38:39 +0000 (UTC) (envelope-from android@oberon.pfi.lt) Received: from oberon.pfi.lt (oberon.pfi.lt [193.219.52.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F9E643D49 for ; Mon, 11 Sep 2006 08:38:38 +0000 (GMT) (envelope-from android@oberon.pfi.lt) Received: from [10.10.10.1] (82-135-145-2.ip.rygveda.lt [82.135.145.2]) by oberon.pfi.lt (8.13.3/8.13.3) with ESMTP id k8B8w4KC081011; Mon, 11 Sep 2006 11:58:04 +0300 (EEST) (envelope-from android@oberon.pfi.lt) Message-ID: <45052086.3050900@oberon.pfi.lt> Date: Mon, 11 Sep 2006 11:38:30 +0300 From: "Android Andrew [:]" User-Agent: Thunderbird 1.5.0.5 (X11/20060907) MIME-Version: 1.0 To: "Android Andrew [:]" References: <44E392C3.2000605@oberon.pfi.lt> In-Reply-To: <44E392C3.2000605@oberon.pfi.lt> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Christian Walther , freebsd-stable@freebsd.org, Ian Smith Subject: Re: FreeBSD 6.1-STABLE: Unexplained power off X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 08:38:39 -0000 Hello everyone! I want to thank all of you for ideas and support! Finally I've resolved this annoying problem with "Unexplained power off". Right were those who supposed hardware problem. I've replaced PSU, and everything is OK - system is stable under any load... Android Andrew [:] wrote: > Thank you for answers! > > Yesterday the last iteration of high load testing finished with just > another power off. > There are two ways of problem-solving have been outlined in this thread. > One way - hardware problem, e.g. PSU. > Another way - software, e.g. APM/ACPI problem. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 12:28: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 3325516A4A0 for ; Mon, 11 Sep 2006 12:28:11 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6305C43D55 for ; Mon, 11 Sep 2006 12:28:10 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 11 Sep 2006 12:28:08 -0000 Received: from p54A7FC43.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.252.67] by mail.gmx.net (mp040) with SMTP; 11 Sep 2006 14:28:08 +0200 X-Authenticated: #5465401 Message-ID: <45055654.7040808@gmx.de> Date: Mon, 11 Sep 2006 14:28:04 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: non critical mounts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 12:28:11 -0000 Failing NFS mounts with the -b option take a lot of time, because they fork AFTER an attempt has failed. And that normally takes a lot of time. So I have written that patch, which fixes the behaviour by forking even before the first attempt is made. http://www.freebsd.org/cgi/query-pr.cgi?pr=103089 But now I wonder weather it wouldn't be better to introduce an option like nocrit for non critical mounts in sbin/mount that generally forks mounts with that option into the background. It would be useful for all kinds of replaceable drives and network shares. Especially in an ever changing environment such as a Laptop. Now why not amd you say, the answer being that it costs significant CPU time when using such a mount. That does not matter on an optical drive, but when you want to build the world on an external HD, it makes a difference. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 14:12: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 36DA416A403 for ; Mon, 11 Sep 2006 14:12:28 +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 97B0543D45 for ; Mon, 11 Sep 2006 14:12:27 +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 E7645B80F for ; Mon, 11 Sep 2006 10:12:25 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <20060910164158.C1031@ganymede.hub.org> References: <20060910164158.C1031@ganymede.hub.org> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-10--711881419; protocol="application/pkcs7-signature" Message-Id: <940C72E7-3428-4771-88A8-3AB861097D8E@khera.org> From: Vivek Khera Date: Mon, 11 Sep 2006 10:12:24 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: check if file system is clean ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 14:12:28 -0000 --Apple-Mail-10--711881419 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 10, 2006, at 3:44 PM, Marc G. Fournier wrote: > I checked both fsck and fsck_ffs man page, and don't see anything > in either ... is there some way I can check if a file system is > actually 'clean', without running fsck? run dump? not sure how picky that is. --Apple-Mail-10--711881419-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 16:23: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 7BE0E16A403 for ; Mon, 11 Sep 2006 16:23:01 +0000 (UTC) (envelope-from db@spearburn.danielbond.org) Received: from spearburn.danielbond.org (ti221110a080-5119.bb.online.no [83.109.147.255]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB53243D6B for ; Mon, 11 Sep 2006 16:22:54 +0000 (GMT) (envelope-from db@spearburn.danielbond.org) Received: by spearburn.danielbond.org (Postfix, from userid 1001) id F34595C49; Mon, 11 Sep 2006 18:26:07 +0200 (CEST) Date: Mon, 11 Sep 2006 18:26:07 +0200 From: Daniel Bond To: Tobias Roth Message-ID: <20060911162607.GA32178@spearburn.danielbond.org> References: <20060907181311.GA25768@spearburn.danielbond.org> <20060908121348.GA5534@droopy.unibe.ch> <20060909212208.GA16312@spearburn.danielbond.org> <20060910103459.GA9229@droopy.unibe.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910103459.GA9229@droopy.unibe.ch> X-GPG-Key-Id: 37898D6C X-GPG-Key-Server: http://pgp.mit.edu X-GPG-Key-FingerPrint: DA2F 6D5F 052B 0180 6E12 F62D 85E6 9276 59CC E5B6 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-stable@freebsd.org Subject: Re: Patch for GBDE rc-script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 16:23:01 -0000 On 12:34 Sun 10 Sep, Tobias Roth wrote: > On Sat, Sep 09, 2006 at 11:22:08PM +0200, Daniel Bond wrote: > > On 14:13 Fri 08 Sep, Tobias Roth wrote: > > > > > > How is this better/different from just adding the gbde device to > > > /etc/fstab and have it mounted along with all other filesystems? > > > > > It says in the handbook: > > > > "Since encrypted file systems cannot yet be listed in /etc/fstab for automatic > > mounting, the file systems must be checked for errors by running fsck(8) > > manually before mounting." > > Interesting. I have had this line in my /etc/fstab for almost a year > now and it just works(tm): > > /dev/ad0s4d.bde /home ufs rw 2 2 > > Since during startup, gbde is run before fsck, I don't see why there would > be any problems with this. > > Thanks, > Tobias Maybee this should be updated in the handbook then? (Along with the placement for the lockfile, since GBDE defaultly looks in /etc/.lock (not: /etc/gbde/)) I could do it if I knew how. -- Med vennlig hilsen / Best regards, ------------------------------------------ Daniel Bond PGP: C822C4BD ------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 18:09: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 6255B16A407 for ; Mon, 11 Sep 2006 18:09:38 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A2F43D5D for ; Mon, 11 Sep 2006 18:09:30 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20060911180919m92000uefme>; Mon, 11 Sep 2006 18:09:29 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k8BI9H0v035277; Mon, 11 Sep 2006 13:09:17 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k8BI9GFN035276; Mon, 11 Sep 2006 13:09:16 -0500 (CDT) (envelope-from brooks) Date: Mon, 11 Sep 2006 13:09:15 -0500 From: Brooks Davis To: Stefan Bethke Message-ID: <20060911180915.GB33304@lor.one-eyed-alien.net> References: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2" Content-Disposition: inline In-Reply-To: <3A8131D4-881E-4873-A682-543A1A88C063@lassitu.de> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: Still possible to directly boot without loader? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 18:09:38 -0000 --lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 10, 2006 at 09:10:26PM +0200, Stefan Bethke wrote: > I just tried to load my standard kernel from the boot blocks (instead =20 > of using loader(8)), but I either get a hang before the kernel prints =20 > anything, or a BTX halted. Is this still supposed to work in 6-=20 > stable, or has it finally disappeared? You may be able to get this to work, but it is unsupported. -- Brooks --lEGEL1/lMxI0MVQ2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBaZAXY6L6fI4GtQRAiriAJ0cgtmy1uHQwGPjd36VNU0a49e9YACgooUD bh2DlDhnMeMsNf2OMRcsiiU= =I3eL -----END PGP SIGNATURE----- --lEGEL1/lMxI0MVQ2-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 19:56: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 5BC4016A4D1; Mon, 11 Sep 2006 19:56:19 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0B043D98; Mon, 11 Sep 2006 19:55:22 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id 83C8C2A586; Mon, 11 Sep 2006 16:55:21 -0300 (BRT) Date: Mon, 11 Sep 2006 16:55:21 -0300 From: Marcelo Gardini do Amaral To: freebsd-stable@freebsd.org Message-ID: <20060911195521.GD63300@registro.br> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060904130827.GE12975@registro.br> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org Subject: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 19:56:19 -0000 I would like to discuss a little bit more about UDP performance. I've made some tests and the results may have some value here. In this test is easy to see that there is something different in the FreeBSD 6 branch. I made a benchmark with bind 9.3.2 (without threads support) and nsd 3.0.1 (1 server forked) on a HP Proliant Dual AMD Opteron 2.4GHz among FreeBSD 4.11, 6.1 and Linux kernel 2.6.15, all of them for i386 systems. I used this simple zone file: # cat db.FOO.BAR $TTL 86400 @ 172800 in soa foo.dns.bar. hostmaster.foo.bar. ( 2006090601 ;serial 1800 ;refresh 30 minutos 900 ;retry 15 minutos 604800 ;expire 7 dias 900 ) ;negative caching 15 minutos 172800 in ns foo.dns.bar. ; zone delegation begin test1 IN NS qq1.bsd. test2 IN NS qq2.bsd. test3 IN NS qq3.bsd. test4 IN NS qq4.bsd. test5 IN NS qq5.bsd. test6 IN NS qq6.bsd. test7 IN NS qq7.bsd. test8 IN NS qq8.bsd. test9 IN NS qq9.bsd. In another box with the same hardware I used FreeBSD 4.11 and queryperf (DNS Query Performance Testing Tool) as a client to realize 1.000.000 of NS queries on the servers. Below I show the results: queries per second OS Bind 9.3.2 NSD 3.0.1 ---- ---- ---- Linux 2.6 SMP 38845 59645 FreeBSD 4.11 SMP 34977 59417 FreeBSD 4.11 UP 33926 59547 FreeBSD 6.1 SMP 14953 15908 FreeBSD 6.1 UP 15516 14752 Comments: Linux had a performance just 10% better than FreeBSD 4.11 with bind. With nsd I didn't see any difference between them. There is no difference also tweaking the kernel from UP to SMP. With nsd the performance was improved to ~60k queries per second on 4.11 and Linux, i.e., it was almost doubled comparing with bind. I couldn't see any packet loss in any case. On the other hand, on FreeBSD 6.1 the result was lower than half of bind's performance on the others systems tested. And with nsd the result didn't get better (unlike happend on FreeBSD 4.11). I also got some 'timeout' on FreeBSD 6.1 - about 200 from 1M packets were lost. In actual fact, I think that is important to emphasize that the same limit was reached on both name servers - no more than ~15k queries per second was possible on 6.1. I think there is an issue on the system, not on bind neither nsd. Besides this, I've noticed some problems with bge interface driver. Many times the interface is up and running and suddenly goes down, without any reason, or after a reboot it doesn't go up. And if you just remove and insert again the cable, everything returns to work. On up-to-date FreeBSD 6 boxes I don't see this problem so often, but with 'netstat -i' it's possible to find some input errors - I was used to see no errors on 4.11 and others. Does anybody noticed this behavior? For my purpose, the UDP performance is very important. I would be glad with any kind of help to tune my box and improve its performance. For those who wants to try, the queryperf can be found in the bind source tree, at bind-9.3.2/contrib/queryperf. I used a query load file like this (1M of lines making reference to the zones in db.FOO.BAR): # cat query.txt test1.foo.bar NS test7.foo.bar NS test8.foo.bar NS test9.foo.bar NS test2.foo.bar NS ... Cheers, Marcelo Gardini From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 20:00:47 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 910F216A412 for ; Mon, 11 Sep 2006 20:00:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id DEDC343D70 for ; Mon, 11 Sep 2006 20:00:46 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 19531 invoked by uid 399); 11 Sep 2006 20:00:46 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Sep 2006 20:00:46 -0000 Message-ID: <4505C06A.5020804@FreeBSD.org> Date: Mon, 11 Sep 2006 13:00:42 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Daniel Bond References: <20060907181311.GA25768@spearburn.danielbond.org> <20060908121348.GA5534@droopy.unibe.ch> <20060909212208.GA16312@spearburn.danielbond.org> <20060910103459.GA9229@droopy.unibe.ch> <20060911162607.GA32178@spearburn.danielbond.org> In-Reply-To: <20060911162607.GA32178@spearburn.danielbond.org> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Tobias Roth Subject: Re: Patch for GBDE rc-script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Sep 2006 20:00:47 -0000 Daniel Bond wrote: > Maybee this should be updated in the handbook then? (Along with the placement > for the lockfile, since GBDE defaultly looks in /etc/.lock (not: /etc/gbde/)) > > I could do it if I knew how. You don't have to know docbook to contribute to the docs. You can write up your suggested changes in plain english, and submit a PR. The doc committers are usually pretty good about handling the docbook stuff for you, especially if it's a minor change to existing text. >From what you've said here, it sounds like this would be a welcome addition, thanks for looking into it. :) hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 07:05: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 6C05B16A403 for ; Tue, 12 Sep 2006 07:05:59 +0000 (UTC) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0990043D46 for ; Tue, 12 Sep 2006 07:05:58 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-42-252.dynamic.qsc.de [212.202.42.252]) by efacilitas.de (Postfix) with ESMTP id E6AA94CD54; Tue, 12 Sep 2006 09:05:57 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id EA0875285C; Tue, 12 Sep 2006 09:05:56 +0200 (CEST) Message-ID: <45065C67.6040503@cs.tu-berlin.de> Date: Tue, 12 Sep 2006 09:06:15 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.13) Gecko/20060519 X-Accept-Language: de, en MIME-Version: 1.0 To: Karl Denninger References: <20060909173813.GA1388@FS.denninger.net> In-Reply-To: <20060909173813.GA1388@FS.denninger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 07:05:59 -0000 Karl Denninger schrieb: > This is not cool folks. I think you misunderstood what -STABLE means. (Or maybe I do?) -STABLE is still a development branch without guarantee of a stable and working operating system. -STABLE guarantees that interfaces remain stable. If you want reliability then jump from release to release. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 08:22: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 2185416A416 for ; Tue, 12 Sep 2006 08:22:02 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA0B43D4C for ; Tue, 12 Sep 2006 08:22:01 +0000 (GMT) (envelope-from bsd@kuehlbox.de) Received: (qmail 79987 invoked from network); 12 Sep 2006 08:21:59 -0000 Received: from unknown (HELO [10.0.47.117]) (webmaster@kuehlbox.de@[62.159.47.1]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 12 Sep 2006 08:21:59 -0000 Message-ID: <45066E19.2040405@kuehlbox.de> Date: Tue, 12 Sep 2006 10:21:45 +0200 From: "bsd@kuehlbox.de" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 08:22:02 -0000 I've just watched over some of the gjournal threads. My main question now is, whats the difference from gjournal and softupdates in case of reability ? Wasn't SU design to make the use of journals needless? As far i remember, SU was designed to write in the cache in such a way, that whenever the system crashed, the FS is always consistent. Only bgfsck has todo a snapshot and cleanup "unused" space that got lost cause the SU did not finish as the crash occured. Maybe someone can give me some light into that :). I always tought that *BSD don't need a journaling FS as it has already SU Greetings Teufel From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 09:41: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 0E0DB16A6C9 for ; Tue, 12 Sep 2006 09:41:10 +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 EADCA43D55 for ; Tue, 12 Sep 2006 09:41:08 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GN4lN-00089w-P1 for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 11:41:05 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 11:41:05 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 11:41:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 12 Sep 2006 11:40:31 +0200 Lines: 37 Message-ID: References: <45066E19.2040405@kuehlbox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: <45066E19.2040405@kuehlbox.de> Sender: news Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 09:41:10 -0000 bsd@kuehlbox.de wrote: > Only bgfsck > has todo a snapshot and cleanup "unused" space that got lost cause the > SU did not finish as the crash occured. > > Maybe someone can give me some light into that :). I always tought that > *BSD don't need a journaling FS as it has already SU Soft-updates was a good idea that was implemented a bit too late (with regards to development in journaling and file system technologies), and now there are several problems with it: - [bg]fsck is still needed, and it takes way too long on large (terabyte-size) file systems. This was not a problem with small file systems when SU was designed. - bgfsck relies on snapshots, and there still are several problems with those (judging from information on mailing lists, not personal experience): they take too long to create on large file systems, there are problems with taking snapshots when the drive is almost full, and (possibly? don't remember exactly now) some NFS issues with either the snapshot or the underlying file system. - (most?) kernel developers tend to disable bgfsck completely on the file systems actively used during development because of possible panic during testing new code while bgfsck is still running, and normal fsck takes too long - todays desktop drives can lie about writing data. SoftUpdates relies on some assumptions about when the data is physically written to media, and those are not always valid today - every now and then there appear some anecdotal evidence that file systems do get destroyed even with SoftUpdates, which are probably related to the previous point, but it can't be investigated - AFAIK the addition of SoftUpdates to file system code made file system code more than usually complex, with bugs that are discovered even now. The basic idea behind SU is good and valid, but judging from side-effects of its practical implementation, right now journaling appears to be a simpler and more effective solution to the problem. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 10:04: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 7C6A316A403 for ; Tue, 12 Sep 2006 10:04:11 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E54843D5D for ; Tue, 12 Sep 2006 10:04:07 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from dominion.borderworlds.dk (dominion.borderworlds.dk [10.1.0.10]) by ferengi.borderworlds.dk (Postfix) with ESMTP id 1B6ADB817 for ; Tue, 12 Sep 2006 12:04:02 +0200 (CEST) Received: by dominion.borderworlds.dk (Postfix, from userid 2000) id 97E978C8; Tue, 12 Sep 2006 12:04:01 +0200 (CEST) To: freebsd-stable@freebsd.org References: <45066E19.2040405@kuehlbox.de> From: Christian Laursen Date: Tue, 12 Sep 2006 12:04:01 +0200 In-Reply-To: (Ivan Voras's message of "Tue, 12 Sep 2006 11:40:31 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 10:04:11 -0000 Ivan Voras writes: > - todays desktop drives can lie about writing data. SoftUpdates relies > on some assumptions about when the data is physically written to > media, and those are not always valid today I think journaling relies on the same assumptions. However, with journaling you can have filesystem corruption and not know about it. With fsck, bg or not, at least you will know. -- Christian Laursen From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 10:36: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 38A1916A407 for ; Tue, 12 Sep 2006 10:36:05 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (smtp1.utsp.utwente.nl [130.89.2.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 700F143D45 for ; Tue, 12 Sep 2006 10:36:03 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id k8CAZww4000310; Tue, 12 Sep 2006 12:35:58 +0200 From: Pieter de Goeje To: Marcelo Gardini do Amaral Date: Tue, 12 Sep 2006 12:35:58 +0200 User-Agent: KMail/1.9.3 References: <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> In-Reply-To: <20060911195521.GD63300@registro.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609121235.58619.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 10:36:05 -0000 On Monday 11 September 2006 21:55, Marcelo Gardini do Amaral wrote: > I would like to discuss a little bit more about UDP performance. I've > made some tests and the results may have some value here. > > In this test is easy to see that there is something different in the > FreeBSD 6 branch. > > I made a benchmark with bind 9.3.2 (without threads support) and nsd > 3.0.1 (1 server forked) on a HP Proliant Dual AMD Opteron 2.4GHz among > FreeBSD 4.11, 6.1 and Linux kernel 2.6.15, all of them for i386 > systems. I used this simple zone file: > > queries per second > > OS Bind 9.3.2 NSD 3.0.1 > ---- ---- ---- > > Linux 2.6 SMP 38845 59645 > > FreeBSD 4.11 SMP 34977 59417 > > FreeBSD 4.11 UP 33926 59547 > > FreeBSD 6.1 SMP 14953 15908 > > FreeBSD 6.1 UP 15516 14752 I did some UDP performance testing on my own and these are my results: Both systems are running FreeBSD 6.1-STABLE i386, connected using gigabit ethernet. The server is an AMD Athlon64 2Ghz with an onboard sk(4) gbit nic. The server program is a simple UDP echo server, collecting various performance data. UDP "requests" are handled completely synchronously. It ofcourse differs from the DNS server in the sense that is doesn't actually do anything with the received data. The client is an AMD Sempron 1,6Ghz with a cheap re(4) gbit nic which offers no interrupt moderation. The client program forks into a part that sends packets as fast as possible to the server and a part that receives echo'ed packets from the server. The client is thus capable of doing asynchronous "requests". For these tests the client sent 1000000 packets. Packet Size Queries/Second Loss Total Bandwidth Bytes % 10^6 bits/sec 100 57348 0.5 92 200 44873 0.5 144 300 39117 0.4 198 400 35672 0.4 228 1000 27124 0.4 434 Also note that the client was using 100% cpu during the tests. The server was approx. 50% idle, using most (28%) cpu in the interrupt handlers, leaving in in my opinion enough room for the actual data processing. My conclusion: there's definately something wrong with your setup. Maybe you could try a different NIC to see if the performance issues are driver related. - Pieter de Goeje From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:01: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 DB5E516A403 for ; Tue, 12 Sep 2006 11:01:03 +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 69B6C43D45 for ; Tue, 12 Sep 2006 11:01:02 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GN604-00071o-22 for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 13:00:20 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:00:20 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:00:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 12 Sep 2006 12:59:13 +0200 Lines: 12 Message-ID: References: <45066E19.2040405@kuehlbox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: Sender: news Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:01:03 -0000 Christian Laursen wrote: > Ivan Voras writes: > >> - todays desktop drives can lie about writing data. SoftUpdates relies >> on some assumptions about when the data is physically written to >> media, and those are not always valid today > > I think journaling relies on the same assumptions. Doesn't it rely less since a journal is written sequentially, but SU expects ordering of many writes to different parts of the file system to be persistent and in sequence? From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:13: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 BC24B16A403 for ; Tue, 12 Sep 2006 11:13:33 +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 C513543D5D for ; Tue, 12 Sep 2006 11:13:31 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GN6CJ-0001Dg-9E for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 13:12:59 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:12:59 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:12:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 12 Sep 2006 13:12:22 +0200 Lines: 7 Message-ID: References: <45066E19.2040405@kuehlbox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: Sender: news Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:13:33 -0000 Christian Laursen wrote: > However, with journaling you can have filesystem corruption and not know > about it. With fsck, bg or not, at least you will know. Also, I'm interested about this - what kind of silent corruption? The same kind that can generally come from on-drive caches? From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:26: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 27BF016A403 for ; Tue, 12 Sep 2006 11:26:37 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF15543D45 for ; Tue, 12 Sep 2006 11:26:36 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from dominion.borderworlds.dk (dominion.borderworlds.dk [10.1.0.10]) by ferengi.borderworlds.dk (Postfix) with ESMTP id D9826B817 for ; Tue, 12 Sep 2006 13:26:35 +0200 (CEST) Received: by dominion.borderworlds.dk (Postfix, from userid 2000) id 816718C8; Tue, 12 Sep 2006 13:26:35 +0200 (CEST) To: freebsd-stable@freebsd.org References: <45066E19.2040405@kuehlbox.de> From: Christian Laursen Date: Tue, 12 Sep 2006 13:26:35 +0200 In-Reply-To: (Ivan Voras's message of "Tue, 12 Sep 2006 12:59:13 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:26:37 -0000 Ivan Voras writes: > Christian Laursen wrote: >> Ivan Voras writes: >> >>> - todays desktop drives can lie about writing data. SoftUpdates relies >>> on some assumptions about when the data is physically written to >>> media, and those are not always valid today >> >> I think journaling relies on the same assumptions. > > Doesn't it rely less since a journal is written sequentially, but SU > expects ordering of many writes to different parts of the file system > to be persistent and in sequence? Journaling also needs writes to be done in the correct order. You don't want to write the real update to the filesystem before you have made sure that it has been committed to the journal. If that can happen you are no better off than without the journal. -- Christian Laursen From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:30: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 67EF916A40F for ; Tue, 12 Sep 2006 11:30:52 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC8B643D55 for ; Tue, 12 Sep 2006 11:30:51 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from dominion.borderworlds.dk (dominion.borderworlds.dk [10.1.0.10]) by ferengi.borderworlds.dk (Postfix) with ESMTP id 05AFCB817 for ; Tue, 12 Sep 2006 13:30:51 +0200 (CEST) Received: by dominion.borderworlds.dk (Postfix, from userid 2000) id C4BCB8C8; Tue, 12 Sep 2006 13:30:50 +0200 (CEST) To: freebsd-stable@freebsd.org References: <45066E19.2040405@kuehlbox.de> From: Christian Laursen Date: Tue, 12 Sep 2006 13:30:50 +0200 In-Reply-To: (Ivan Voras's message of "Tue, 12 Sep 2006 13:12:22 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:30:52 -0000 Ivan Voras writes: > Christian Laursen wrote: > >> However, with journaling you can have filesystem corruption and not know >> about it. With fsck, bg or not, at least you will know. > > Also, I'm interested about this - what kind of silent corruption? The > same kind that can generally come from on-drive caches? Yes, as well as corruption resulting from bugs in the kernel code. The point is that you will never know because you never check your filesystems. -- Christian Laursen From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:39: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 1339316A4D2 for ; Tue, 12 Sep 2006 11:39:46 +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 6EF7843D68 for ; Tue, 12 Sep 2006 11:39:43 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GN6bq-0006mp-Pd for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 13:39:22 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:39:22 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 12 Sep 2006 13:39:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Tue, 12 Sep 2006 13:38:49 +0200 Lines: 7 Message-ID: References: <45066E19.2040405@kuehlbox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: Sender: news Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:39:46 -0000 Christian Laursen wrote: > Journaling also needs writes to be done in the correct order. You don't > want to write the real update to the filesystem before you have made sure Ok, but journal is (or should be) protected by checksumming or some kind of record markers, so invalid entries are not replayed. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:53: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 BAC6516A403 for ; Tue, 12 Sep 2006 11:53:37 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E939C43D69 for ; Tue, 12 Sep 2006 11:53:36 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 12 Sep 2006 11:53:33 -0000 Received: from p54A7FC6A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.252.106] by mail.gmx.net (mp038) with SMTP; 12 Sep 2006 13:53:33 +0200 X-Authenticated: #5465401 Message-ID: <45069FB8.3030704@gmx.de> Date: Tue, 12 Sep 2006 13:53:28 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Releng_6 suddenly no longer -j safe X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:53:37 -0000 Last time I built a kernel on Releng_6 (only a couple of days ago) everything was fine with "-j 4". Now buildkernel stops, this is an example: ===> sound/driver/als4000 (depend) awk -f @/tools/makeobjops.awk @/kern/device_if.m -h machine -> /usr/src/sys/i386/include awk: can't open file @/tools/makeobjops.awk source line number 1 source file @/tools/makeobjops.awk context is >>> <<< *** Error code 2 @ -> /usr/src/sys 1 error ... Where it stops is random (I suppose it sometimes is accidentally built in the right order), but the error is always similar. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 11:57: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 A410F16A415 for ; Tue, 12 Sep 2006 11:57:12 +0000 (UTC) (envelope-from xi@borderworlds.dk) Received: from ferengi.borderworlds.dk (ferengi.borderworlds.dk [80.166.152.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 202FA43D73 for ; Tue, 12 Sep 2006 11:57:12 +0000 (GMT) (envelope-from xi@borderworlds.dk) Received: from dominion.borderworlds.dk (dominion.borderworlds.dk [10.1.0.10]) by ferengi.borderworlds.dk (Postfix) with ESMTP id 4990EB913 for ; Tue, 12 Sep 2006 13:57:11 +0200 (CEST) Received: by dominion.borderworlds.dk (Postfix, from userid 2000) id 674748C8; Tue, 12 Sep 2006 13:57:10 +0200 (CEST) To: freebsd-stable@freebsd.org References: <45066E19.2040405@kuehlbox.de> From: Christian Laursen Date: Tue, 12 Sep 2006 13:57:10 +0200 In-Reply-To: (Ivan Voras's message of "Tue, 12 Sep 2006 13:38:49 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 11:57:12 -0000 Ivan Voras writes: > Christian Laursen wrote: > >> Journaling also needs writes to be done in the correct order. You don't >> want to write the real update to the filesystem before you have made sure > > Ok, but journal is (or should be) protected by checksumming or some > kind of record markers, so invalid entries are not replayed. That is not the issue. Recognizing valid journal entries should be easy enough. Consider the following sequence of events: 1. Data A is written to the journal 2. The journal is flushed to disk 3. Data A is written to the filesystem Now consider what happens if the disk is reordering writes: 1. Data A is partially written to the journal 2. Data A is partially written to the filesystem 3. The system crashes You now have an invalid journal entry for data A which will not be replayed and some unkown amount of the data is already written to the filesysten possibly leaving it in an inconsistent state. -- Christian Laursen From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 12:15: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 9917D16A403 for ; Tue, 12 Sep 2006 12:15:08 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC8E843D4C for ; Tue, 12 Sep 2006 12:15:07 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 618E55E3A; Tue, 12 Sep 2006 16:15:06 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id 3F7495E23; Tue, 12 Sep 2006 16:15:06 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8CCFEgR033477; Tue, 12 Sep 2006 16:15:14 +0400 (MSD) (envelope-from ru) Date: Tue, 12 Sep 2006 16:15:14 +0400 From: Ruslan Ermilov To: "[LoN]Kamikaze" Message-ID: <20060912121513.GA31799@rambler-co.ru> References: <45069FB8.3030704@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <45069FB8.3030704@gmx.de> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable@freebsd.org Subject: Re: Releng_6 suddenly no longer -j safe X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 12:15:08 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 12, 2006 at 01:53:28PM +0200, [LoN]Kamikaze wrote: > Last time I built a kernel on Releng_6 (only a couple of days ago) > everything was fine with "-j 4". > Now buildkernel stops, this is an example: >=20 > =3D=3D=3D> sound/driver/als4000 (depend) > awk -f @/tools/makeobjops.awk @/kern/device_if.m -h > machine -> /usr/src/sys/i386/include > awk: can't open file @/tools/makeobjops.awk > source line number 1 source file @/tools/makeobjops.awk > context is > >>> <<< > *** Error code 2 > @ -> /usr/src/sys > 1 error > ... >=20 > Where it stops is random (I suppose it sometimes is accidentally > built in the right order), but the error is always similar. >=20 This puzzled me for a while, since kmod.mk has mechanisms that try to ensure `@' is built before it's accessed. What the implementation is missing is anti-footshooting measures. I bet your /usr/src/sys/modules/ has some stray `@' symlinks possibly left from compiling modules manually without creating object directories, and forgetting to run "make clean" afterwards. Here's how I can reproduce the behavior you're seeing: : # pwd : /usr/src/sys/modules/sound/driver/als4000 : # make -s cleandir : # make -s cleandir : # make @ : @ -> /usr/src/sys : # make obj : /usr/obj/usr/src/sys/modules/sound/driver/als4000 created for /usr/src/sy= s/modules/sound/driver/als4000 : # make device_if.h : awk -f @/tools/makeobjops.awk @/kern/device_if.m -h : awk: can't open file @/tools/makeobjops.awk : source line number 1 source file @/tools/makeobjops.awk : context is : >>> <<<=20 : *** Error code 2 :=20 : Stop in /usr/src/sys/modules/sound/driver/als4000. Fix: cd /usr/src/sys/modules && make cleandir && make cleandir Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBqTRqRfpzJluFF4RAmTFAJwJarG0pR+SQZ09G4q+b4WrvTAw+wCgnDX9 xWlh7gL8XiGy6qsWgcZTjTk= =CBA+ -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 12:29: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 6D1D216A47B for ; Tue, 12 Sep 2006 12:29:10 +0000 (UTC) (envelope-from smibrahim@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3CF343D45 for ; Tue, 12 Sep 2006 12:29:09 +0000 (GMT) (envelope-from smibrahim@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so2010676wxd for ; Tue, 12 Sep 2006 05:29:09 -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=fu1Cz+RqlhvIXGPy5Wj1+25ibX7k3JuTOJvlUNrYuZoUlVFZ6P0JdAm2hqMMPQStwkjV5dKjgPb0f82l7cdPV4SDGnZy7MzaiWnuggDDqgldqBe40ixjA8+SIqIhPKqJLKR8tMvWRYSY+EC7uEhuT9z0QPUtVVV/JnEDYY8sH5E= Received: by 10.70.109.4 with SMTP id h4mr8221168wxc; Tue, 12 Sep 2006 05:27:28 -0700 (PDT) Received: by 10.70.10.6 with HTTP; Tue, 12 Sep 2006 05:27:28 -0700 (PDT) Message-ID: <4997275b0609120527s54fc815gb9f9d03943a05d55@mail.gmail.com> Date: Tue, 12 Sep 2006 18:27:28 +0600 From: "S. M. Ibrahim (Lavlu)" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 12:29:10 -0000 Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD 6.1-Stable. What is the easy process ? -- S. M. Ibrahim (Lavlu) Home page: http://lavluda.tripod.com Blog: http://lavluda.tk Yahoo!! ID: lavluda MSN ID: lavluda Skype : lavluda From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 12:39: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 B652816A416 for ; Tue, 12 Sep 2006 12:39:10 +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 48CC143D6D for ; Tue, 12 Sep 2006 12:39:09 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 12 Sep 2006 12:39:07 -0000 Received: from p54A7FC6A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.252.106] by mail.gmx.net (mp004) with SMTP; 12 Sep 2006 14:39:07 +0200 X-Authenticated: #5465401 Message-ID: <4506AA66.40203@gmx.de> Date: Tue, 12 Sep 2006 14:39:02 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Ruslan Ermilov References: <45069FB8.3030704@gmx.de> <20060912121513.GA31799@rambler-co.ru> In-Reply-To: <20060912121513.GA31799@rambler-co.ru> 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: Releng_6 suddenly no longer -j safe X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 12:39:10 -0000 Ruslan Ermilov wrote: > On Tue, Sep 12, 2006 at 01:53:28PM +0200, [LoN]Kamikaze wrote: >> Last time I built a kernel on Releng_6 (only a couple of days ago) >> everything was fine with "-j 4". >> Now buildkernel stops, this is an example: >> >> ... >> >> Where it stops is random (I suppose it sometimes is accidentally >> built in the right order), but the error is always similar. >> > This puzzled me for a while, since kmod.mk has mechanisms that > try to ensure `@' is built before it's accessed. What the > implementation is missing is anti-footshooting measures. I bet > your /usr/src/sys/modules/ has some stray `@' symlinks possibly > left from compiling modules manually without creating object > directories, and forgetting to run "make clean" afterwards. Thank you, since I don't know how and where I messed up the source tree, I deleted it and recvsupped it. It's building at the moment and it seems to work fine. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 12:48: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 667BE16A416 for ; Tue, 12 Sep 2006 12:48:11 +0000 (UTC) (envelope-from heli@mikestammer.com) Received: from smtp114.sbc.mail.re2.yahoo.com (smtp114.sbc.mail.re2.yahoo.com [68.142.229.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 4755E43D4C for ; Tue, 12 Sep 2006 12:48:03 +0000 (GMT) (envelope-from heli@mikestammer.com) Received: (qmail 93453 invoked from network); 12 Sep 2006 12:48:02 -0000 Received: from unknown (HELO gondolin.mikestammer.com) (mikestammer@sbcglobal.net@75.3.23.178 with login) by smtp114.sbc.mail.re2.yahoo.com with SMTP; 12 Sep 2006 12:48:02 -0000 Received: from localhost (localhost [127.0.0.1]) by gondolin.mikestammer.com (Postfix) with ESMTP id EABA0B0 for ; Tue, 12 Sep 2006 07:48:01 -0500 (CDT) X-Virus-Scanned: amavisd-new at mikestammer.com Received: from gondolin.mikestammer.com ([127.0.0.1]) by localhost (gondolin.middleearth.mikestammer.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oj6SMQCKozbm for ; Tue, 12 Sep 2006 07:47:56 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eric) by gondolin.mikestammer.com (Postfix) with ESMTP id DE51594 for ; Tue, 12 Sep 2006 07:47:56 -0500 (CDT) Message-ID: <4506AC7C.9040007@mikestammer.com> Date: Tue, 12 Sep 2006 07:47:56 -0500 From: Eric User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4997275b0609120527s54fc815gb9f9d03943a05d55@mail.gmail.com> In-Reply-To: <4997275b0609120527s54fc815gb9f9d03943a05d55@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 12:48:11 -0000 S. M. Ibrahim (Lavlu) wrote: > Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD > 6.1-Stable. What is the easy process ? > > this works well http://mikestammer.com/dokuwiki/doku.php?id=bsd:updateos From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 13:39: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 5D15B16A407 for ; Tue, 12 Sep 2006 13:39:53 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (unsane.co.uk [62.140.220.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E3F43D45 for ; Tue, 12 Sep 2006 13:39:52 +0000 (GMT) (envelope-from jhary@unsane.co.uk) Received: from [192.168.10.217] (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.13.7/8.13.3) with ESMTP id k8CDdrgC065195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Sep 2006 14:39:54 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <4506B89F.30505@unsane.co.uk> Date: Tue, 12 Sep 2006 14:39:43 +0100 From: Vince User-Agent: Thunderbird 1.5.0.5 (X11/20060811) MIME-Version: 1.0 To: Eric References: <4997275b0609120527s54fc815gb9f9d03943a05d55@mail.gmail.com> <4506AC7C.9040007@mikestammer.com> In-Reply-To: <4506AC7C.9040007@mikestammer.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 13:39:53 -0000 Eric wrote: > S. M. Ibrahim (Lavlu) wrote: >> Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD >> 6.1-Stable. What is the easy process ? >> >> > > this works well > > http://mikestammer.com/dokuwiki/doku.php?id=bsd:updateos the cvsup part looks ok but for the actual build then read /usr/src/Makefile for the recommended procedure. Vince > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 13:59: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 4B55216A417 for ; Tue, 12 Sep 2006 13:59:08 +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 BF24343D6A for ; Tue, 12 Sep 2006 13:59:01 +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 47296B80F for ; Tue, 12 Sep 2006 09:59:01 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <45065C67.6040503@cs.tu-berlin.de> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-6--626283465; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Tue, 12 Sep 2006 09:59:02 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 13:59:08 -0000 --Apple-Mail-6--626283465 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed On Sep 12, 2006, at 3:06 AM, Bj=F6rn K=F6nig wrote: > -STABLE is still a development branch without guarantee of a stable =20= > and working operating system. -STABLE guarantees that interfaces =20 > remain stable. If you want reliability then jump from release to =20 > release. If you want reliability, then you need to do your own testing on your =20= own hardware on your own application prior to replacing your working =20 version with the new one. Never rely on anyone else saying "Yeah, it =20= will work". It will come back and bite you where you don't want to =20 be bit. The other side of this is "don't replace what works" and just leave =20 things as they are. --Apple-Mail-6--626283465-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 13:59:21 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 1537D16A4A0 for ; Tue, 12 Sep 2006 13:59:21 +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 1AE1243D76 for ; Tue, 12 Sep 2006 13:59:09 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp228-73.lns2.adl4.internode.on.net [203.122.228.73]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k8CDwaaZ064527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Sep 2006 23:28:37 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 12 Sep 2006 23:28:35 +0930 User-Agent: KMail/1.9.3 References: <45066E19.2040405@kuehlbox.de> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1273612.mW7mACUaMD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609122328.36605.doconnor@gsoft.com.au> X-Spam-Score: -2.291 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Christian Laursen Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 13:59:21 -0000 --nextPart1273612.mW7mACUaMD Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 12 September 2006 19:34, Christian Laursen wrote: > Ivan Voras writes: > > - todays desktop drives can lie about writing data. SoftUpdates relies > > on some assumptions about when the data is physically written to > > media, and those are not always valid today > > I think journaling relies on the same assumptions. You can disable write caching on your disks (most even honour it :) however= a=20 lot of people choke at the performance hit.. One big problem is that high capacity disks use track writing - if you modi= fy=20 a single sector the disk re-writes the whole track. If the power fails during the track write then you lose potentially complet= ely=20 unrelated data. This affects all file systems equally 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 --nextPart1273612.mW7mACUaMD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBFBr0M5ZPcIHs/zowRAmpJAJ9pz20mKs49Pg8L4H5rpFUXd2AA6ACdEKKe mnce7A0RRAwbLfbRPcSKCds= =gPc3 -----END PGP SIGNATURE----- --nextPart1273612.mW7mACUaMD-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 14: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 2DA4616A412 for ; Tue, 12 Sep 2006 14:14:50 +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 7F95443D62 for ; Tue, 12 Sep 2006 14:14:38 +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 E063BC272; Tue, 12 Sep 2006 10:14:36 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 973EAC56B; Tue, 12 Sep 2006 10:06:43 -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 34E5BC4F6; Tue, 12 Sep 2006 10:06:43 -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:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=OttSvyj00s2yUWj3mTmBBFzemjcpW2LpGexIFm2ghCMccHhi6U3egL39jFSysYVsPuB6nQklSxJ8uYZFNIV+Gc/3/fbBxGHvA8Q2KnGkJkm0H5Roy5e/LZxDoN/FcF8l; Received: from [192.168.1.10] (socker.hsd1.ma.comcast.net [24.218.145.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id C2E51C272; Tue, 12 Sep 2006 10:06:42 -0400 (EDT) Message-ID: <4506BEF2.6050706@protected-networks.net> Date: Tue, 12 Sep 2006 10:06:42 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Vivek Khera References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> In-Reply-To: X-Enigmail-Version: 0.94.0.0 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 14:14:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vivek Khera wrote: | If you want reliability, then you need to do your own testing on your | own hardware on your own application prior to replacing your working | version with the new one. Never rely on anyone else saying "Yeah, it | will work". It will come back and bite you where you don't want to be bit. | | The other side of this is "don't replace what works" and just leave | things as they are. I must say that this one critical point is what made me choose FreeBSD over Linux way back in ~1992. It is possible, indeed almost mandatory in a commercial setting, to build a local repository containing the OS and *everything* required to build it. Good change management is not about tracking the latest and greatest, it's about being able to make sensible decisions about which changes to implement, when and, most of all, knowing why. Security isn't just about firewalls, it's about business continuity too, Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBr7xQv9rrgRC1JIRAnboAJ4vHl7UAF149CavttzqVwD/r8aIlgCggmY8 JyW4le67COyphcFoUUbZ7ng= =0rDL -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 14:15: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 809F216A601 for ; Tue, 12 Sep 2006 14:15:55 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DB5443D72 for ; Tue, 12 Sep 2006 14:15:51 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8CEFmDK011949 for ; Tue, 12 Sep 2006 09:15:48 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Tue Sep 12 09:15:48 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8CEFlDK011946 for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 09:15:47 -0500 (CDT) (envelope-from karl) Date: Tue, 12 Sep 2006 09:15:47 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060912141547.GA11713@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45065C67.6040503@cs.tu-berlin.de> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 14:15:55 -0000 On Tue, Sep 12, 2006 at 09:06:15AM +0200, Bj?rn K?nig wrote: > Karl Denninger schrieb: > > >This is not cool folks. > > I think you misunderstood what -STABLE means. (Or maybe I do?) > > -STABLE is still a development branch without guarantee of a stable and > working operating system. -STABLE guarantees that interfaces remain > stable. If you want reliability then jump from release to release. > > Regards > Bj?rn You've never been able to get reliability by jumping from release to release, and every time someone comes in the lists to complain about something being broken in -RELEASE, the advice is to go to and track -STABLE! Guys, what's written in a handbook may be all well and good, but its what that matters - and this is what has "really happened" for the last ten years with FreeBSD! I don't think its too much to ask that before something is MFC'd back to -STABLE from -CURRENT that it be tested for the most common functionality (that is, does it work at all?) In this case all that someone had to do was boot the system and then detach and reattach a mirror component - the most basic of functionality - to detect that the patch was bad. That obviously wasn't done in this instance. I understand that finding corner cases and expecting exhaustive testing is unreasonable from a free project - even in a -RELEASE we don't get that. But this wasn't a corner case - it was a situation where absolutely zero testing was performed before the MFC was sent back to the source tree. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 14:20: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 3397D16A417 for ; Tue, 12 Sep 2006 14:20:03 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96D5843D7C for ; Tue, 12 Sep 2006 14:19:52 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8CEJp8l012069 for ; Tue, 12 Sep 2006 09:19:51 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Tue Sep 12 09:19:51 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8CEJpmw012066 for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 09:19:51 -0500 (CDT) (envelope-from karl) Date: Tue, 12 Sep 2006 09:19:51 -0500 From: Karl Denninger To: freebsd-stable Message-ID: <20060912141951.GB11713@FS.denninger.net> Mail-Followup-To: freebsd-stable References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 14:20:03 -0000 On Tue, Sep 12, 2006 at 09:59:02AM -0400, Vivek Khera wrote: > > On Sep 12, 2006, at 3:06 AM, Bj?rn K?nig wrote: > > >-STABLE is still a development branch without guarantee of a stable > >and working operating system. -STABLE guarantees that interfaces > >remain stable. If you want reliability then jump from release to > >release. > > If you want reliability, then you need to do your own testing on your > own hardware on your own application prior to replacing your working > version with the new one. Never rely on anyone else saying "Yeah, it > will work". It will come back and bite you where you don't want to > be bit. > > The other side of this is "don't replace what works" and just leave > things as they are. That'd be nice - but in this case the reason for the replacement was that there's SERIOUS breakage in the serial drivers (at least the Rocketport ones, and perhaps more) in 6.x, which was what prompted the update. Finding a totally-unrelated thing MFCd back with zero testing was QUITE a surprise....and not something I would have tested for ANYWAY, since the commitlog for sys and this module suggested that the change made to that section of code was in fact to remove some "inappropriate" comments - not change functionality in a way that could potentially cause this sort of breakage! -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 14:52: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 CC9D016A416 for ; Tue, 12 Sep 2006 14:52:30 +0000 (UTC) (envelope-from rvenne@dental-on-line.fr) Received: from smtp.dental-on-line.fr (smtp.dental-on-line.fr [82.234.245.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F17443D53 for ; Tue, 12 Sep 2006 14:52:29 +0000 (GMT) (envelope-from rvenne@dental-on-line.fr) Received: from [192.168.1.7] (triton.dental-on-line.net [192.168.1.7]) by smtp.dental-on-line.fr (Postfix) with ESMTP id 268111386A9 for ; Tue, 12 Sep 2006 16:52:28 +0200 (CEST) Message-ID: <4506C9B0.5040807@dental-on-line.fr> Date: Tue, 12 Sep 2006 16:52:32 +0200 From: rvenne@dental-on-line.fr User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-stable References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: cap_mkdb: illegal option -i. upgrade 5.4->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, 12 Sep 2006 14:52:30 -0000 Hi list I'm upgrading 5.4 p18 to 6.1 p6. here's my tag: RELENG_6_1 I did: make update make cleanworld make buildworld which gives following issue: cap_mkdb: illegal option -i It seems a known problem on netbsd during buildworld compilation. here's the solution I'm tring: cd /usr/src/usr.bin/cap_mkdb make clean make make install and I'm building world again. is that a known problem on freebsd? thanks for your anwsers From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 15:23: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 E3C5316A4B3 for ; Tue, 12 Sep 2006 15:23:24 +0000 (UTC) (envelope-from "cyb."@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DAC843D96 for ; Tue, 12 Sep 2006 15:21:31 +0000 (GMT) (envelope-from "cyb."@gmx.net) Received: (qmail invoked by alias); 12 Sep 2006 15:21:19 -0000 Received: from pD952DA2F.dip0.t-ipconnect.de (EHLO p4-3200) [217.82.218.47] by mail.gmx.net (mp016) with SMTP; 12 Sep 2006 17:21:19 +0200 X-Authenticated: #4870692 Date: Tue, 12 Sep 2006 17:21:27 +0200 To: rvenne@dental-on-line.fr From: "Andreas Rudisch" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4506C9B0.5040807@dental-on-line.fr> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <4506C9B0.5040807@dental-on-line.fr> User-Agent: Opera Mail/9.01 (Win32) X-Y-GMX-Trusted: 0 Cc: freebsd-stable Subject: Re: cap_mkdb: illegal option -i. upgrade 5.4->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, 12 Sep 2006 15:23:25 -0000 You might want to read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html Andreas From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 15:33: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 4E70616A415 for ; Tue, 12 Sep 2006 15:33:13 +0000 (UTC) (envelope-from ob@gruft.de) Received: from obh.snafu.de (obh.snafu.de [213.73.92.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id F302943D83 for ; Tue, 12 Sep 2006 15:33:10 +0000 (GMT) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GNAG6-000AIu-0F for freebsd-stable@freebsd.org; Tue, 12 Sep 2006 17:33:10 +0200 Date: Tue, 12 Sep 2006 17:33:09 +0200 From: Oliver Brandmueller To: freebsd-stable@freebsd.org Message-ID: <20060912153309.GL91327@e-Gitt.NET> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060912141547.GA11713@FS.denninger.net> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: Oliver Brandmueller Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 15:33:13 -0000 Hi. On Tue, Sep 12, 2006 at 09:15:47AM -0500, Karl Denninger wrote: > I don't think its too much to ask that before something is MFC'd back > to -STABLE from -CURRENT that it be tested for the most > common functionality (that is, does it work at all?) In this case all > that someone had to do was boot the system and then detach and > reattach a mirror component - the most basic of functionality - to > detect that the patch was bad. Thank god, nothing really can happen, if you deploy a new -STABLE on your servers, since of course before deploying a new piece of software it's being tested on a non-prod test setup, where you'll notice such apparent problems - especially when using -STABLE, where you never know, if you are probably just in the middle of a bigger commit. So, since nothing important could break, what's the hassle all about? - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 15:55: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 802B416A415 for ; Tue, 12 Sep 2006 15:55:58 +0000 (UTC) (envelope-from nalists@scls.lib.wi.us) Received: from mail.scls.lib.wi.us (mail.scls.lib.wi.us [198.150.40.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8760C43D8B for ; Tue, 12 Sep 2006 15:55:49 +0000 (GMT) (envelope-from nalists@scls.lib.wi.us) Received: from [10.1.99.103] ([10.1.99.103]) by mail.scls.lib.wi.us (8.13.1/8.13.1) with ESMTP id k8CFsUo0014130 for ; Tue, 12 Sep 2006 10:54:30 -0500 (CDT) (envelope-from nalists@scls.lib.wi.us) Message-ID: <4506D884.4050605@scls.lib.wi.us> Date: Tue, 12 Sep 2006 10:55:48 -0500 From: Greg Barniskis User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> In-Reply-To: <20060912141547.GA11713@FS.denninger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 15:55:58 -0000 Karl Denninger wrote: > You've never been able to get reliability by jumping from release to release, eh? Been doing that for 10 years without a single significant problem. Granted, we've been lucky enough here not to encounter (a) flakier hardware components and/or (b) flakier combos of drivers & apps & configs & heavy loads (a.k.a. bugs in FreeBSD) that other folks admittedly have encountered in the most painful ways. Releases aren't guaranteed to be perfect, nothing is, but plenty of users have no complaints at all about release point reliability. They're just not posting their non-problems to the lists. > and every time someone comes in the lists to complain about something being > broken in -RELEASE, the advice is to go to and track -STABLE! Maybe splitting hairs, but advising a user with a problem to try using the -STABLE code that exists at the time of the problem report is really not the same as advising them to /track/ STABLE. If you /track/ STABLE by frequently cvsupping it and rebuilding your system, you will very likely encounter a serious problem sooner or later. That's why tracking it is not recommended for production systems. On the other hand if you update a production system to a point in time of STABLE that fixes a particular bug that plagued a release point, and then you don't update again until the next release point or security advisory, you will very likely find joy. -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) , (608) 266-6348 From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 15:58: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 3247C16A47B for ; Tue, 12 Sep 2006 15:58:03 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D6CF43D78 for ; Tue, 12 Sep 2006 15:58:00 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (vidqfm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8CFvrEn009004 for ; Tue, 12 Sep 2006 17:57:59 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8CFvr86009003; Tue, 12 Sep 2006 17:57:53 +0200 (CEST) (envelope-from olli) Date: Tue, 12 Sep 2006 17:57:53 +0200 (CEST) Message-Id: <200609121557.k8CFvr86009003@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4506B89F.30505@unsane.co.uk> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 12 Sep 2006 17:57:59 +0200 (CEST) Cc: Subject: Re: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable 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: Tue, 12 Sep 2006 15:58:03 -0000 Vince wrote: > Eric wrote: > > S. M. Ibrahim (Lavlu) wrote: > > > Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD > > > 6.1-Stable. What is the easy process ? > > > > this works well > > > > http://mikestammer.com/dokuwiki/doku.php?id=bsd:updateos > the cvsup part looks ok but for the actual build then read > /usr/src/Makefile > for the recommended procedure. It's better to read /usr/src/UPDATING. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I learned Java 3 years before Python. It was my language of choice. It took me two weekends with Python before I was more productive with it than with Java." -- Anthony Roberts From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 16:09: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 22BA916A40F for ; Tue, 12 Sep 2006 16:09:09 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9887243D45 for ; Tue, 12 Sep 2006 16:09:08 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id B86115CA9; Tue, 12 Sep 2006 20:09:07 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id B12F35CA6; Tue, 12 Sep 2006 20:09:07 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8CG971l001101; Tue, 12 Sep 2006 20:09:07 +0400 (MSD) (envelope-from ru) Date: Tue, 12 Sep 2006 20:09:07 +0400 From: Ruslan Ermilov To: rvenne@dental-on-line.fr Message-ID: <20060912160907.GC962@rambler-co.ru> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4506C9B0.5040807@dental-on-line.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+xNpyl7Qekk2NvDX" Content-Disposition: inline In-Reply-To: <4506C9B0.5040807@dental-on-line.fr> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable Subject: Re: cap_mkdb: illegal option -i. upgrade 5.4->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, 12 Sep 2006 16:09:09 -0000 --+xNpyl7Qekk2NvDX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 12, 2006 at 04:52:32PM +0200, rvenne@dental-on-line.fr wrote: > Hi list >=20 > I'm upgrading 5.4 p18 to 6.1 p6. >=20 > here's my tag: RELENG_6_1 >=20 > I did: > make update > make cleanworld > make buildworld >=20 > which gives following issue: >=20 > cap_mkdb: illegal option -i >=20 > It seems a known problem on netbsd during buildworld compilation. here's= =20 > the solution I'm tring: >=20 > cd /usr/src/usr.bin/cap_mkdb > make clean > make > make install >=20 > and I'm building world again. >=20 > is that a known problem on freebsd? >=20 This shouldn't happen. The buildworld target detects the current version of your system, and bootstraps cap_mkdb if necessary: : .if ${BOOTSTRAPPING} < 600015 : _cap_mkdb=3D usr.bin/cap_mkdb : .endif BOOTSTRAPPING is defined as follows: : .if !defined(OSRELDATE) : .if exists(/usr/include/osreldate.h) : OSRELDATE!=3D awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $= $3 }' \ : /usr/include/osreldate.h : .else : OSRELDATE=3D 0 : .endif That is, it's the value of __FreeBSD_version as defined in /usr/include/osreldate.h. If your /usr/include/osreldate.h is lying about the current version, e.g. if you accidentally installed the new headers, then you can force it to zero, such as: make buildworld OSRELDATE=3D0 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --+xNpyl7Qekk2NvDX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBtujqRfpzJluFF4RAtC/AJ0bs1kmUDGMULn8DJ++/iko876cmACdHkHo UCkYZ5eTUPL+MhpEHPlj3zk= =SHfW -----END PGP SIGNATURE----- --+xNpyl7Qekk2NvDX-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 16:16:21 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 B3A4416A403 for ; Tue, 12 Sep 2006 16:16:21 +0000 (UTC) (envelope-from steve@sohara.org) Received: from sohara.org (sohara.org [192.220.64.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 745A043D45 for ; Tue, 12 Sep 2006 16:16:21 +0000 (GMT) (envelope-from steve@sohara.org) Received: (qmail 67995 invoked by uid 16563); 12 Sep 2006 16:16:20 -0000 Received: from unknown (HELO df1.marelmo.com) ([194.145.135.241]) (envelope-sender ) by 192.220.64.179 (qmail-ldap-1.03) with SMTP for ; 12 Sep 2006 16:16:20 -0000 Date: Tue, 12 Sep 2006 17:16:17 +0100 From: Steve O'Hara-Smith To: freebsd-stable@freebsd.org Message-Id: <20060912171617.556a43cc.steve@sohara.org> In-Reply-To: <4506D884.4050605@scls.lib.wi.us> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> <4506D884.4050605@scls.lib.wi.us> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-pc-dragonfly) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX, Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 16:16:21 -0000 On Tue, 12 Sep 2006 10:55:48 -0500 Greg Barniskis wrote: > If you /track/ STABLE by frequently cvsupping it and rebuilding your > system, you will very likely encounter a serious problem sooner or > later. That's why tracking it is not recommended for production > systems. I did exactly that all the way from 2.0 to 4.11 on various machines without ever having any trouble. -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 16:20: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 C039116A403 for ; Tue, 12 Sep 2006 16:20:13 +0000 (UTC) (envelope-from heli@mikestammer.com) Received: from smtp113.sbc.mail.re2.yahoo.com (smtp113.sbc.mail.re2.yahoo.com [68.142.229.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 0560F43D46 for ; Tue, 12 Sep 2006 16:20:12 +0000 (GMT) (envelope-from heli@mikestammer.com) Received: (qmail 17772 invoked from network); 12 Sep 2006 16:20:12 -0000 Received: from unknown (HELO gondolin.mikestammer.com) (mikestammer@sbcglobal.net@75.3.23.178 with login) by smtp113.sbc.mail.re2.yahoo.com with SMTP; 12 Sep 2006 16:20:11 -0000 Received: from localhost (localhost [127.0.0.1]) by gondolin.mikestammer.com (Postfix) with ESMTP id 5A42554 for ; Tue, 12 Sep 2006 11:20:11 -0500 (CDT) X-Virus-Scanned: amavisd-new at mikestammer.com Received: from gondolin.mikestammer.com ([127.0.0.1]) by localhost (gondolin.middleearth.mikestammer.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PI6Kqb-xY33v for ; Tue, 12 Sep 2006 11:20:08 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eric) by gondolin.mikestammer.com (Postfix) with ESMTP id C8A0153 for ; Tue, 12 Sep 2006 11:20:08 -0500 (CDT) Message-ID: <4506DE38.10803@mikestammer.com> Date: Tue, 12 Sep 2006 11:20:08 -0500 From: Eric User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <200609121557.k8CFvr86009003@lurza.secnetix.de> In-Reply-To: <200609121557.k8CFvr86009003@lurza.secnetix.de> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 16:20:13 -0000 Oliver Fromme wrote: > Vince wrote: > > Eric wrote: > > > S. M. Ibrahim (Lavlu) wrote: > > > > Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD > > > > 6.1-Stable. What is the easy process ? > > > > > > this works well > > > > > > http://mikestammer.com/dokuwiki/doku.php?id=bsd:updateos > > the cvsup part looks ok but for the actual build then read > > /usr/src/Makefile > > for the recommended procedure. > > It's better to read /usr/src/UPDATING. > > Best regards > Oliver > my wiki above mentions reading UPDATING (in step 3) before starting... UPDATING pretty much says exactly the same thing, except its 80% of the way into UPDATING. The wiki above also explains things a bit more for someone who has never done it. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 18:46: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 6280616A407 for ; Tue, 12 Sep 2006 18:46:26 +0000 (UTC) (envelope-from jfarmer@goldsword.com) Received: from imf20aec.mail.bellsouth.net (imf20aec.mail.bellsouth.net [205.152.59.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC99343D78 for ; Tue, 12 Sep 2006 18:46:22 +0000 (GMT) (envelope-from jfarmer@goldsword.com) Received: from ibm64aec.bellsouth.net ([65.13.105.239]) by imf20aec.mail.bellsouth.net with ESMTP id <20060912184622.YWXK16843.imf20aec.mail.bellsouth.net@ibm64aec.bellsouth.net> for ; Tue, 12 Sep 2006 14:46:22 -0400 Received: from [192.168.1.33] (really [65.13.105.239]) by ibm64aec.bellsouth.net with ESMTP id <20060912184621.EZLW18973.ibm64aec.bellsouth.net@[192.168.1.33]> for ; Tue, 12 Sep 2006 14:46:21 -0400 Message-ID: <4507008D.4070901@goldsword.com> Date: Tue, 12 Sep 2006 14:46:37 -0400 From: "J. T. Farmer" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> <4506D884.4050605@scls.lib.wi.us> In-Reply-To: <4506D884.4050605@scls.lib.wi.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 18:46:26 -0000 Greg Barniskis wrote: > Karl Denninger wrote: >> and every time someone comes in the lists to complain about something >> being >> broken in -RELEASE, the advice is to go to and track -STABLE! > Maybe splitting hairs, but advising a user with a problem to try using > the -STABLE code that exists at the time of the problem report is > really not the same as advising them to /track/ STABLE. > > If you /track/ STABLE by frequently cvsupping it and rebuilding your > system, you will very likely encounter a serious problem sooner or > later. That's why tracking it is not recommended for production systems. > > On the other hand if you update a production system to a point in time > of STABLE that fixes a particular bug that plagued a release point, > and then you don't update again until the next release point or > security advisory, you will very likely find joy. See my similar comment that echoes Karl's. Now go back and read what Karl said. He's not tracking -STABLE on a production box, he updated to -STABLE to fix an existing problem. What bit him in the ass is a problem with code that "in theory" had not changed and _was_supposed_ to have been tested. That is, it was working, he upgraded, as everyone tells you to do, to get fixes to -RELEASE bugs, not to track -STABLE. John ------------------------------------------------------------------ John T. Farmer Owner & CTO GoldSword Systems jfarmer@goldsword.com 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 18:59: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 5F58416A40F for ; Tue, 12 Sep 2006 18:59:08 +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 C662043D45 for ; Tue, 12 Sep 2006 18:59:07 +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 k8CIx4du041116; Tue, 12 Sep 2006 14:59:04 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id k8CIx4tW051622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Sep 2006 14:59:04 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <7.0.1.0.0.20060912144758.171c0c38@sentex.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 12 Sep 2006 14:59:04 -0400 To: Karl Denninger , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20060912141547.GA11713@FS.denninger.net> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 18:59:08 -0000 At 10:15 AM 9/12/2006, Karl Denninger wrote: >On Tue, Sep 12, 2006 at 09:06:15AM +0200, Bj?rn K?nig wrote: > > Karl Denninger schrieb: > > > > >This is not cool folks. > > > > I think you misunderstood what -STABLE means. (Or maybe I do?) > > > > -STABLE is still a development branch without guarantee of a stable and > > working operating system. -STABLE guarantees that interfaces remain > > stable. If you want reliability then jump from release to release. > > > > Regards > > Bj?rn > >You've never been able to get reliability by jumping from release to release, I think FreeBSD does not work for everyone with every setup, but works really well for some number of people. For me, I am in b). In fact it works really well for me and the some 250 boxes I look after of varying age and configs... There have been some unfortunate bugs, but I take that as part of what FreeBSD is-- a volunteer project. If FreeBSD releases have *never* worked for you (I will take your word you are not being childish and exaggerating here), why on earth are you using FreeBSD ? Also, what are you comparing FreeBSD to, where the RELEASE works for everyone out of the box for ever and ever ? You cant mean Windows, as they release monthly updates-- some of which after having gone through tens of thousands of dollars of regression testing (FreeBSD does not have an army of employees to do planned regression testing let alone tens of thousands of dollars), and manage to introduce BIGGER bugs than they were fixing like they did last month with Win2k. You cant mean LINUX as they seem to be doing a kernel a month (or more) recently. Which OS are you talking about that is so perfect from release to release ? ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 19:19: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 73FCB16A403 for ; Tue, 12 Sep 2006 19:19:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id DCB6843D46 for ; Tue, 12 Sep 2006 19:19:41 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 31799 invoked by uid 399); 12 Sep 2006 19:19:40 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 12 Sep 2006 19:19:40 -0000 Message-ID: <4507084A.4080002@FreeBSD.org> Date: Tue, 12 Sep 2006 12:19:38 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> In-Reply-To: <20060912141547.GA11713@FS.denninger.net> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 19:19:42 -0000 Karl Denninger wrote: > You've never been able to get reliability by jumping from release to release, I think there are a lot of users who disagree with you on that one. > and every time someone comes in the lists to complain about something being > broken in -RELEASE, the advice is to go to and track -STABLE! These are different issues. > I don't think its too much to ask that before something is MFC'd back to > -STABLE from -CURRENT that it be tested for the most common > functionality (that is, does it work at all?) In this case all that someone > had to do was boot the system and then detach and reattach a mirror component - > the most basic of functionality - to detect that the patch was bad. > > That obviously wasn't done in this instance. No one has disagreed with you about this. Several people have apologized already. It's past time that you got over it. That said, no matter how stable (in the dictionary term of the word) a given branch of FreeBSD is (or is not) at any given time, nothing replaces the need to test changes/updates yourself, on non-production hardware, before deploying them to anything you care about. That is just as true of FreeBSD as it is of any commercial software. Time to move on here folks, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 19:24: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 BF2CA16A403 for ; Tue, 12 Sep 2006 19:24:44 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5807C43D46 for ; Tue, 12 Sep 2006 19:24:44 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (unknown [200.46.204.128]) by hub.org (Postfix) with ESMTP id 1CC0958650A for ; Tue, 12 Sep 2006 16:24:44 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 63297-09 for ; Tue, 12 Sep 2006 19:22:50 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 05568586509 for ; Tue, 12 Sep 2006 16:22:50 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 751A35D4FC; Tue, 12 Sep 2006 16:22:51 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 702685D4F9 for ; Tue, 12 Sep 2006 16:22:51 -0300 (ADT) Date: Tue, 12 Sep 2006 16:22:51 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060912161603.R1031@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 19:24:44 -0000 What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for building kernel/world? I know awhile back it wasn't recommended to go above -O2, for instance, but suspect that has changed ... ? Thanks ... ---- 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 Tue Sep 12 19:31:32 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 926CD16A40F for ; Tue, 12 Sep 2006 19:31:32 +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 0879A43D45 for ; Tue, 12 Sep 2006 19:31:32 +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 39111C4F2; Tue, 12 Sep 2006 15:31:31 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id E22E9C4B4; Tue, 12 Sep 2006 15:31:21 -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 6C17CC4EC; Tue, 12 Sep 2006 15:31:21 -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:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=UC3K3ed6CWvo6BCuK9rC+zmrYQ54MPzNeMYq1P7o/sBnaT8iviioQarLNkFT4dvWdvHy9yx/OR109NBLkA+uOASkhq/y4Z60i1X4NLT0ggaCcNqpQQBGM0blriFimqLr; Received: from [192.168.1.10] (socker.hsd1.ma.comcast.net [24.218.145.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 0CE94C48F; Tue, 12 Sep 2006 15:31:20 -0400 (EDT) Message-ID: <45070B08.6010507@protected-networks.net> Date: Tue, 12 Sep 2006 15:31:20 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: "Marc G. Fournier" References: <20060912161603.R1031@ganymede.hub.org> In-Reply-To: <20060912161603.R1031@ganymede.hub.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=0442D492 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 19:31:32 -0000 Marc G. Fournier wrote: > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > building kernel/world? I know awhile back it wasn't recommended to go > above -O2, for instance, but suspect that has changed ... ? CFLAGS=-O2 -pipe -fno-strict-aliasing COPTFLAGS=-O2 -pipe -fno-strict-aliasing CPUTYPE?=prescott .. just works(tm) for an Intel T-2300 dual core ;-) Using -O3 will get you into bother with the amount of inlining the compiler wants to do to the kernel, Michael From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 19:39: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 004FA16A47E for ; Tue, 12 Sep 2006 19:39:32 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D0A243D70 for ; Tue, 12 Sep 2006 19:39:30 +0000 (GMT) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net ([12.207.12.9]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20060912193915m9100smpuie>; Tue, 12 Sep 2006 19:39:15 +0000 Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.6/8.13.6) with ESMTP id k8CJcwlN049675; Tue, 12 Sep 2006 14:38:58 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.6/8.13.6/Submit) id k8CJcvdN049667; Tue, 12 Sep 2006 14:38:57 -0500 (CDT) (envelope-from brooks) Date: Tue, 12 Sep 2006 14:38:57 -0500 From: Brooks Davis To: "Marc G. Fournier" Message-ID: <20060912193856.GA49540@lor.one-eyed-alien.net> References: <20060912161603.R1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20060912161603.R1031@ganymede.hub.org> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 19:39:33 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 12, 2006 at 04:22:51PM -0300, Marc G. Fournier wrote: >=20 > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for= =20 > building kernel/world? I know awhile back it wasn't recommended to go=20 > above -O2, for instance, but suspect that has changed ... ? Nothing above -O2 is supported. Period. If you try another value and something breaks, don't report it unless you can verify it happens with -O or -O2. For many applications, -O2 will perform better than -O3 so you need to benchmark individual applications. For most applications, there's simply no point. -- Brooks --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBwzQXY6L6fI4GtQRAr+WAJ4rWEsmLHEYk1jkv1om7X+JV716dACfbDDM pdPRE8w9/OqhGdl9fGmAD20= =+UK3 -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 19:40: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 3130516A594 for ; Tue, 12 Sep 2006 19:40:24 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB56B43D45 for ; Tue, 12 Sep 2006 19:40:23 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [10.242.169.21] (c-67-171-135-169.hsd1.or.comcast.net [67.171.135.169]) by mail.twinthornes.com (Postfix) with ESMTP id 00761D8B; Tue, 12 Sep 2006 12:40:22 -0700 (PDT) Message-ID: <45070D24.8000709@bitfreak.org> Date: Tue, 12 Sep 2006 12:40:20 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: karl@denninger.net References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> In-Reply-To: <20060912141547.GA11713@FS.denninger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 19:40:24 -0000 Karl Denninger wrote: > I don't think its too much to ask that before something is MFC'd back to > -STABLE from -CURRENT that it be tested for the most common > functionality (that is, does it work at all?) In this case all that someone > had to do was boot the system and then detach and reattach a mirror component - > the most basic of functionality - to detect that the patch was bad. > > That obviously wasn't done in this instance. > > I understand that finding corner cases and expecting exhaustive testing > is unreasonable from a free project - even in a -RELEASE we don't get that. > > But this wasn't a corner case - it was a situation where absolutely zero > testing was performed before the MFC was sent back to the source tree. So when can the FreeBSD Foundation expect your donation of computers for the purpose of GEOM testing? -- Darren Pilgrim From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 19:48: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 C2D4C16A403 for ; Tue, 12 Sep 2006 19:48:11 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A248543D55 for ; Tue, 12 Sep 2006 19:48:10 +0000 (GMT) (envelope-from bsd@kuehlbox.de) Received: (qmail 89355 invoked from network); 12 Sep 2006 19:48:09 -0000 Received: from unknown (HELO [172.16.21.119]) (webmaster@kuehlbox.de@[82.135.94.49]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 12 Sep 2006 19:48:09 -0000 Message-ID: <45070EE6.3090104@kuehlbox.de> Date: Tue, 12 Sep 2006 21:47:50 +0200 From: Teufel User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: <45066E19.2040405@kuehlbox.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 19:48:11 -0000 Christian Laursen wrote: > Ivan Voras writes: > > >> Christian Laursen wrote: >> >> >>> However, with journaling you can have filesystem corruption and not know >>> about it. With fsck, bg or not, at least you will know. >>> >> Also, I'm interested about this - what kind of silent corruption? The >> same kind that can generally come from on-drive caches? >> > > Yes, as well as corruption resulting from bugs in the kernel code. The point > is that you will never know because you never check your filesystems. > Well, thats why i actually don't find journaling filesystems very sexy. So the question is, if it is still safe to use fsck on a gjournal enabled FS ? Having a bgfsck running on a 1 TB volume is not so terrible when it afterwards confirms a valid and consistent filesystem.. Just trusting the journal is a false sense of security in my opinion. my 2cp Stephan From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 20:23: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 48F0F16A403 for ; Tue, 12 Sep 2006 20:23:31 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0605143DA8 for ; Tue, 12 Sep 2006 20:19:57 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id F1C1C18CCCD for ; Tue, 12 Sep 2006 13:29:04 -0700 (PDT) X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WVZn-jmw50-o for ; Tue, 12 Sep 2006 13:29:03 -0700 (PDT) Received: from webmail.sd73.bc.ca (unknown [10.10.10.17]) by smtp.sd73.bc.ca (Postfix) with ESMTP id CF56718CCC7 for ; Tue, 12 Sep 2006 13:29:03 -0700 (PDT) Received: from 142.24.8.227 (SquirrelMail authenticated user fcash) by webmail.sd73.bc.ca with HTTP; Tue, 12 Sep 2006 13:19:49 -0700 (PDT) Message-ID: <50575.142.24.8.227.1158092389.squirrel@webmail.sd73.bc.ca> In-Reply-To: <20060912161603.R1031@ganymede.hub.org> References: <20060912161603.R1031@ganymede.hub.org> Date: Tue, 12 Sep 2006 13:19:49 -0700 (PDT) From: "Freddie Cash" To: stable@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 20:23:31 -0000 On Tue, September 12, 2006 12:22 pm, Marc G. Fournier wrote: > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf > for building kernel/world? I know awhile back it wasn't recommended > to go above -O2, for instance, but suspect that has changed ... ? The defaults are "-O2 -pipe -fno-strict-aliasing". I stopped manually setting CFLAGS/COPTFLAGS around the time of 5.1 and haven't really noticed any changes in performance. Prior to that, I used "-Os -pipe". There are reported problems with not using -fno-strict-aliasing with parts of the base and/or kernel. And, the first thing anyone will tell you if you run into any compile/runtime errors is to put CFLAGS/COPTFLAGS back to the defaults. :) ---- Freddie Cash fcash@ocis.net From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 21:26: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 F1EC116A412 for ; Tue, 12 Sep 2006 21:26:39 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B87943D72 for ; Tue, 12 Sep 2006 21:24:52 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so2161881wxd for ; Tue, 12 Sep 2006 14:24:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Bdc3RVrtVRWPOjRn4sY+kVI3eOthFdVOrCMb3ARHH13kKuSbnPqkTWpZsWMNUDQQENgk05JUYl5NnRmIbOTgJ7CBySdecBGTg3xvENAIgKYZckisSiFLQQNaDAGQZtpn2WaRKB2k2koLs9z6whOd6whGlzc2gkW36jE5nWqwcAY= Received: by 10.70.125.11 with SMTP id x11mr9103182wxc; Tue, 12 Sep 2006 14:24:51 -0700 (PDT) Received: from ?192.168.0.21? ( [84.129.227.138]) by mx.gmail.com with ESMTP id 65sm7574039wra.2006.09.12.14.24.50; Tue, 12 Sep 2006 14:24:51 -0700 (PDT) From: "Pascal G. Hofstee" To: freebsd-stable@freebsd.org Content-Type: text/plain Date: Tue, 12 Sep 2006 23:24:46 +0200 Message-Id: <1158096286.2270.3.camel@chekov> Mime-Version: 1.0 X-Mailer: Evolution 2.8.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: RELENG_6 buildkernel broken ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 21:26:40 -0000 A RELENG_6 buildkernel with sources updated about 2 hours ago seems to break down (after a successfull buildworld) on the following error. cc -c -O -pipe -march=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/dev/ata/ata-chipset.c /usr/src/sys/dev/ata/ata-chipset.c: In function `ata_nvidia_ident': /usr/src/sys/dev/ata/ata-chipset.c:2827: error: `ENX300' undeclared (first use in this function) /usr/src/sys/dev/ata/ata-chipset.c:2827: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/ata/ata-chipset.c:2827: error: for each function it appears in.) /usr/src/sys/dev/ata/ata-chipset.c:2827: error: syntax error before '}' token /usr/src/sys/dev/ata/ata-chipset.c: At top level: /usr/src/sys/dev/ata/ata-chipset.c:2800: warning: unused variable `ctlr' /usr/src/sys/dev/ata/ata-chipset.c:2824: warning: unused variable `buffer' Followed by about another full screen of "defined but not used" and "declared static but never defined" warnings. I tried updating from at least 3 different cvsup-servers but i am not seeing any differences. Can anybody confirm this breakage ? -- Pascal Hofstee From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 21:46: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 52BB616A407 for ; Tue, 12 Sep 2006 21:46:23 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id D797843D45 for ; Tue, 12 Sep 2006 21:46:22 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so2167644wxd for ; Tue, 12 Sep 2006 14:46:22 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=KfrUyZpPp+FfdFOqyGZ3SddFvp+So4fMad0K0DaXKs6I1XypVixUqe+LsscM2j+A3g8A1RuEbUUS7a9X0Yz/wfkALiuj/kEFPrMPheIgYefOqlR34xyrfpU5x1qhBIy3Qf1MnwMDhgW0YstINYRvtyJ6sJJ3+Ke0T4Se8cfTJYg= Received: by 10.70.113.15 with SMTP id l15mr9116848wxc; Tue, 12 Sep 2006 14:46:22 -0700 (PDT) Received: from ?192.168.0.21? ( [84.129.227.138]) by mx.gmail.com with ESMTP id 12sm991526wrl.2006.09.12.14.46.19; Tue, 12 Sep 2006 14:46:21 -0700 (PDT) From: "Pascal G. Hofstee" To: freebsd-stable@freebsd.org In-Reply-To: <1158096286.2270.3.camel@chekov> References: <1158096286.2270.3.camel@chekov> Content-Type: text/plain Date: Tue, 12 Sep 2006 23:46:15 +0200 Message-Id: <1158097575.2270.7.camel@chekov> Mime-Version: 1.0 X-Mailer: Evolution 2.8.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: RELENG_6 buildkernel broken ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 21:46:23 -0000 On Tue, 2006-09-12 at 23:24 +0200, Pascal G. Hofstee wrote: > A RELENG_6 buildkernel with sources updated about 2 hours ago seems to > break down (after a successfull buildworld) on the following error. > I tried updating from at least 3 different cvsup-servers but i am not > seeing any differences. Can anybody confirm this breakage ? I checked the date of the last commit to ata-chipset.c and found it hard to believe nobody had stepped up and notified of a build breakage. I decided to remove the old ata-chipset.c and reupdate (after first generating md5 sums) .. and noticed that after re-fetching ata-chipset.c the new md5-sum changed from the original. Please ignore the line-noise. -- Pascal Hofstee From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 22:04: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 0472116A412 for ; Tue, 12 Sep 2006 22:04:48 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD0BB43D45 for ; Tue, 12 Sep 2006 22:04:45 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id EBF99111B8; Tue, 12 Sep 2006 17:04:44 -0500 (CDT) Date: Tue, 12 Sep 2006 17:04:43 -0500 From: Craig Boston To: Teufel Message-ID: <20060912220442.GA75667@nowhere> Mail-Followup-To: Craig Boston , Teufel , freebsd-stable@FreeBSD.org References: <45066E19.2040405@kuehlbox.de> <45070EE6.3090104@kuehlbox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45070EE6.3090104@kuehlbox.de> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Sep 2006 22:04:48 -0000 On Tue, Sep 12, 2006 at 09:47:50PM +0200, Teufel wrote: > Well, thats why i actually don't find journaling filesystems very sexy. > So the question is, if it is still safe to use fsck on a gjournal > enabled FS ? Well, if you just want to check, you can take a snapshot and run fsck -n on it. That will at least tell you if there's any problems that need to be dealt with. Running fsck on a journal-enabled UFS should be safe modulo the usual requirements (not mounted, which probably means single-user mode). Craig From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 22:58: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 5EF7D16A403 for ; Tue, 12 Sep 2006 22:58:54 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECED543D46 for ; Tue, 12 Sep 2006 22:58:53 +0000 (GMT) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 6BB0E4206; Tue, 12 Sep 2006 15:58:27 -0700 (PDT) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id 22BC34201; Tue, 12 Sep 2006 15:58:26 -0700 (PDT) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id k8CMxW9t034047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Sep 2006 15:59:33 -0700 (PDT) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id k8CMxW4o034042; Tue, 12 Sep 2006 15:59:32 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17671.15316.710301.84433@satchel.alerce.com> Date: Tue, 12 Sep 2006 15:59:32 -0700 To: freebsd-stable@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Subject: question about rebuiding a gmirror on 6.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Sep 2006 22:58:54 -0000 A friend of mine decided to take me up on my offer to help him set up and run a freebsd-stable system (he's a photographer who's only ever used shell accounts onto linux systems before). We setup a gmirror using Approach 2 from http://people.freebsd.org/~rse/mirror. It's been up and running for a while and I just noticed that it was running in DEGRADED mode, having failed ad4. I had him reboot it with either ad4 or ad6 attached, and both seem to work individually. The data on ad4 looks "older", which makes sense because hasn't been being updated. Since we're not sure why it was failed in the first place and it seems to work, we're going to hook it up and try again. I'm nervous about whether the system will sync the newer ad6s1 data onto ad4s1 (what I'd like to happen) or sync the ad4s1 data onto the ad6s1 (which would suck). Our solution is to boot off a CD with only ad4 hooked up, use gmirror clear ad4s1 to blow away the metadata on ad4s1, then reboot with both drives and do gmirror forget gm0s1 and gmirror insert gm0s1 ad4s1. Am I being overly paranoid about the direction in which it'll sync the data? Is there a better way that I should have handled this (other than forcing a practice run back when we got started...)? Thanks, g. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 12 23:07: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 0C8C316A403 for ; Tue, 12 Sep 2006 23:07:31 +0000 (UTC) (envelope-from hackmiester@hackmiester.com) Received: from smtpauth01.prod.mesa1.secureserver.net (smtpauth01.prod.mesa1.secureserver.net [64.202.165.181]) by mx1.FreeBSD.org (Postfix) with SMTP id 88A1B43D45 for ; Tue, 12 Sep 2006 23:07:30 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 18465 invoked from network); 12 Sep 2006 23:07:30 -0000 Received: from unknown (74.230.48.254) by smtpauth01-04.prod.mesa1.secureserver.net (64.202.165.181) with ESMTP; 12 Sep 2006 23:07:29 -0000 In-Reply-To: <45065C67.6040503@cs.tu-berlin.de> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: "hackmiester (Hunter Fuller)" Date: Tue, 12 Sep 2006 17:23:24 -0500 To: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org, Karl Denninger Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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, 12 Sep 2006 23:07:31 -0000 On 12 September 2006, at 02:06, Bj=F6rn K=F6nig wrote: > Karl Denninger schrieb: > >> This is not cool folks. > > I think you misunderstood what -STABLE means. (Or maybe I do?) > > -STABLE is still a development branch without guarantee of a stable =20= > and working operating system. Hahahahaha... That's ironic... (For lack of a better word, really.) > -STABLE guarantees that interfaces remain stable. If you want =20 > reliability then jump from release to release. > > Regards > Bj=F6rn > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-=20 > unsubscribe@freebsd.org" > --=20 hackmiester (Hunter Fuller) yknow when you go to a party, and everyones hooked up except =20 one guy and one girl and so they look at each other like.. do we have to? intel & nvidia must be lookin at each other like that right now Phone Voice: +1 251 589 6348 Fax: Call the voice number and ask. Email General chat: hackmiester@hackmiester.com Large attachments: hackmiester@gmail.com SPS-related stuff: hfuller@stpaulsmobile.net IM AIM: hackmiester1337 Skype: hackmiester31337 YIM: hackm1ester Gtalk: hackmiester MSN: hackmiester@hackmiester.com Xfire: hackmiester From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 00:38: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 EBE3816A47B for ; Wed, 13 Sep 2006 00:38:56 +0000 (UTC) (envelope-from spamd@kc8onw.net) Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id E480B43D49 for ; Wed, 13 Sep 2006 00:38:55 +0000 (GMT) (envelope-from spamd@kc8onw.net) Received: from gx5.fuse.net ([72.49.10.62]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060913003850.LUR2008.smtp2.fuse.net@gx5.fuse.net> for ; Tue, 12 Sep 2006 20:38:50 -0400 Received: from kb8fcl.kc8onw.net ([72.49.10.62]) by gx5.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060913003845.QZQG5373.gx5.fuse.net@kb8fcl.kc8onw.net> for ; Tue, 12 Sep 2006 20:38:45 -0400 Received: from mail.kc8onw.net (unknown [204.117.152.87]) by kb8fcl.kc8onw.net (Postfix) with ESMTP id 63FBCA1737 for ; Tue, 12 Sep 2006 20:38:28 -0400 (EDT) Received: by mail.kc8onw.net (Postfix, from userid 58) id 46B4D285A5; Tue, 12 Sep 2006 20:38:23 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on server.kc8onw.net X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=ham version=3.1.5 Received: from [10.70.3.254] (unknown [10.70.3.254]) by mail.kc8onw.net (Postfix) with ESMTP id E2F25285A2 for ; Tue, 12 Sep 2006 20:38:16 -0400 (EDT) Message-ID: <450752F6.4050109@kc8onw.net> Date: Tue, 12 Sep 2006 20:38:14 -0400 From: Jonathan Stewart User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 00:38:57 -0000 (I know double posting is bad form but this includes new information and it's been several days. Suggestions on where else to look for help are welcome, highpoint was no help) I set up a new server recently and transferred all the information from my old server over. I tried to use unison to synchronize the backup of pictures I have taken and noticed that a large number of pictures where marked as changed on the server. After checking the pictures by hand I confirmed that many of the pictures on the server were corrupted. I attempted to use unison to update the files on the server with the correct local copies but it would fail on almost all the files with the message "destination updated during synchronization." It appears the corruption happens during the read process because when I recompare the files in a graphical diff tool between cache flushes the differences move around!?!?!? The differences also appear to be very small for the most part, single bytes scattered throughout the file. I really have no idea what is causing the problem and would like to pin it down so I can either replace hardware if it's bad or fix whatever the bug is. I cvsuped and rebuilt world and kernel recently hoping that it had been fixed but with no luck. I have not seen any error messages on the console at all either. I have a pair of 320GB SATA hard drives setup as RAID0 on a HighPoint RocketRaid 1520 card the card BIOS is the latest revision as is the motherboard BIOS. This being a data corruption issue I can afford any amount of downtime needed for trouble shooting as it's not very useful to have the server up if everything is going to get corrupted. Thank you, Jonathan uname -a: FreeBSD XXXXX 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun Sep 10 22:54:17 EDT 2006 root@XXXXX:/usr/obj/usr/src/sys/SERVER i386 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-STABLE #0: Sun Sep 10 22:54:17 EDT 2006 root@XXXXX:/usr/obj/usr/src/sys/SERVER mptable_probe: MP Config Table has bad signature: 4\^C\^_ Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 3200+ (2090.16-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 real memory = 1073676288 (1023 MB) avail memory = 1041698816 (993 MB) kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 Correcting nForce2 C1 CPU disconnect hangs agp0: mem 0xd8000000-0xdbffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xe1085000-0xe1085fff irq 5 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe1082000-0xe1082fff irq 5 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xe1083000-0xe10830ff irq 12 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered nve0: port 0xe400-0xe407 mem 0xe1084000-0xe1084fff irq 12 at device 4.0 on pci0 nve0: Ethernet address 00:0c:6e:7d:e0:79 miibus0: on nve0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto nve0: Ethernet address: 00:0c:6e:7d:e0:79 pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) pcib1: at device 8.0 on pci0 pci1: on pcib1 atapci0: port 0xa000-0xa007,0xa400-0xa403,0xa800-0xa807,0xac00-0xac03,0xb000-0xb0ff irq 11 at device 6.0 on pci1 ata2: on atapci0 ata3: on atapci0 pci1: at device 9.0 (no driver attached) pci1: at device 9.1 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: on atapci1 ata1: on atapci1 pcib2: at device 12.0 on pci0 pci2: on pcib2 xl0: <3Com 3c920B-EMB Integrated Fast Etherlink XL> port 0xc000-0xc07f mem 0xdd000000-0xdd00007f irq 5 at device 1.0 on pci2 miibus1: on xl0 acphy0: on miibus1 acphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:26:54:10:8c:0f pcib3: at device 30.0 on pci0 pci3: on pcib3 pci3: at device 0.0 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 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 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/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd17ff,0xd6000-0xd67ff 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 2090164914 Hz quality 800 Timecounters tick every 1.000 msec ad0: 194481MB at ata0-master UDMA133 acd0: DVDROM at ata0-slave UDMA33 ad4: 305245MB at ata2-master UDMA133 ad6: 305245MB at ata3-master UDMA133 ar0: 610490MB status: READY ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad6 at ata3-master Trying to mount root from ufs:/dev/ad0s1a From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 01:07: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 1C1E916A403 for ; Wed, 13 Sep 2006 01:07:38 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (w094.z064001164.sjc-ca.dsl.cnc.net [64.1.164.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02A6643D6A for ; Wed, 13 Sep 2006 01:07:33 +0000 (GMT) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 8077F421A; Tue, 12 Sep 2006 18:07:07 -0700 (PDT) Received: from satchel.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "satchel.alerce.com", Issuer "alerce.com" (verified OK)) by merlin.alerce.com (Postfix) with ESMTP id 4C3024217; Tue, 12 Sep 2006 18:07:07 -0700 (PDT) Received: from satchel.alerce.com (localhost [127.0.0.1]) by satchel.alerce.com (8.13.4/8.13.4) with ESMTP id k8D18Gpn065279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Sep 2006 18:08:16 -0700 (PDT) (envelope-from hartzell@satchel.alerce.com) Received: (from hartzell@localhost) by satchel.alerce.com (8.13.4/8.13.4/Submit) id k8D18FE9065272; Tue, 12 Sep 2006 18:08:15 -0700 (PDT) (envelope-from hartzell) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17671.23039.815831.701428@satchel.alerce.com> Date: Tue, 12 Sep 2006 18:08:15 -0700 To: Jonathan Stewart In-Reply-To: <450752F6.4050109@kc8onw.net> References: <450752F6.4050109@kc8onw.net> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: Re: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 01:07:38 -0000 Jonathan Stewart writes: > [...] > I set up a new server recently and transferred all the information from > my old server over. I tried to use unison to synchronize the backup of > pictures I have taken and noticed that a large number of pictures where > marked as changed on the server. After checking the pictures by hand I > confirmed that many of the pictures on the server were corrupted. I > attempted to use unison to update the files on the server with the > correct local copies but it would fail on almost all the files with the > message "destination updated during synchronization." > > It appears the corruption happens during the read process because when I > recompare the files in a graphical diff tool between cache flushes the > differences move around!?!?!? The differences also appear to be very > small for the most part, single bytes scattered throughout the file. I > really have no idea what is causing the problem and would like to pin it > down so I can either replace hardware if it's bad or fix whatever the > bug is. > [...] It might be a memory problem. I had a linux server that was serving a subversion repository, plus some web stuff. I added some additional memory to keep it from wheezing and it seemed to be running fine. We started noticing problems with things that had been checked out of the repository (e.g. binary tarballs). Removing the extra memory made things work again. memtest86 didn't find anything wrong, which I gather isn't that unusual in these situations. Then again, your problem might be something else entirely.... g. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 01:40: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 026EB16A47B for ; Wed, 13 Sep 2006 01:40:34 +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 DD77E43D46 for ; Wed, 13 Sep 2006 01:40:32 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 9522 invoked from network); 13 Sep 2006 11:40:31 +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; 13 Sep 2006 11:40:31 +1000 Date: Wed, 13 Sep 2006 11:40:27 +1000 From: Norberto Meijome To: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20060913114027.4c26e702@localhost> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: ACPI resume problems in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 01:40:34 -0000 Hi all, I have a Thinkpad z60m, with a custom kernel conf. I was trailing RELENG_6 (aka STABLE) on an almost daily basis (and world updates every week). ACPI enabled, APIC disabled. I can't tell for sure when trouble started, but roughly about 2 weeks ago I couldn't resume from suspend anymore. It would come back and the screen would white out, or stay completelly black (white out == a nice warm white colour... but dead otherwise). Caps lock would not light up LED. There was no kernel dump happening either (no HD activity, i even let it sit for 10 minutes to see if it would help). No info on dmesg or /var/log/messages. I simplified my kernel conf (removed vesa, agp and graphic options for sc) - no changes. I thought there was an improvement when I removed agp, but it was just false hopes. I then decided to revert kernel + world to RELENG_6_1, without otherwise changing my kernel or /etc configuration (other than the obvious mergemaster changes to /etc). and.. voila, everything back to normal. My current uname is: $ uname -a FreeBSD ayiin.xxx.com 6.1-RELEASE-p6 FreeBSD 6.1-RELEASE-p6 #23: Tue Sep 12 14:52:32 EST 2006 root@ayiin.xxx.com:/usr/obj/usr/src/sys/AYIIN i386 The only thing I've noticed that in how my lappy works now is that if_iwi0 is loaded on startup, but iw_bss and firmware.ko are not. I can load them by hand, but haven't been able to test to see if it actually works (i have a feeling it doesnt). I have installed iwi-firmware-kmod-3.0_1 Intel PRO/Wireless 2200 Firmware Kernel Module I have kernel dump from my last RELENG_6 attempt when I removed agp - for once it actually died with a dump. I have a copy of the RELENG_6 /boot/ as well. If I can help debugging this problem, please let me know. I can try to move to STABLE from 2 or 3 weeks ago and see if that makes any difference - any significant date I should look at? cheers! My kernel config is: ----- # AYIIN - Beto's laptop - Kernel config # IBM/Lenovo Thinkpad z60m # BASED ON # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.429.2.5 2006/01/23 14:19:36 marius Exp $ machine i386 #cpu I586_CPU cpu I686_CPU ident AYIIN options PERFMON # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE # Include this file in kernel #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking ## As as 2006/01/30, IPSEC is still under GIANT - Disabling until i actually need it. #options IPSEC #IP security #options IPSEC_ESP #IP security (crypto; define w/ IPSEC) device crypto # TCP_SIGNATURE adds support for RFC 2385 (TCP-MD5) digests. These are # carried in TCP option 19. This option is commonly used to protect # TCP sessions (e.g. BGP) where IPSEC is not available nor desirable. # This is enabled on a per-socket basis using the TCP_MD5SIG socket option. # This requires the use of 'device crypto', 'options FAST_IPSEC' or 'options # IPSEC', and 'device cryptodev'. #options TCP_SIGNATURE #include support for RFC 2385 device cryptodev options NETGRAPH # netgraph(4) system # altq(9). Enable the base part of the hooks with the ALTQ option. # Individual disciplines must be built into the base system and can not be # loaded as modules at this point. options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Detection options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing #options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #enable logging to syslogd(8) #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity #options IPFIREWALL_FORWARD #packet destination changes ##options IPFIREWALL_FORWARD_EXTENDED #all packet dest changes #options IPDIVERT #divert sockets #options IPSTEALTH #support for stealth forwarding #options DUMMYNET options ZERO_COPY_SOCKETS # SMB/CIFS requester # NETSMB enables support for SMB protocol, it requires LIBMCHAIN and LIBICONV # options. # NETSMBCRYPTO enables support for encrypted passwords. #options NETSMB #SMB/CIFS requester options NETSMBCRYPTO #encrypted password support for SMB # Kernel side iconv library options LIBICONV options LIBMCHAIN options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_DIRHASH # Improve performance on big directories # Extended attributes allow additional data to be associated with files, # and is used for ACLs, Capabilities, and MAC labels. # See src/sys/ufs/ufs/README.extattr for more information. options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART # Access Control List support for UFS filesystems. The current ACL # implementation requires extended attribute support, UFS_EXTATTR, # for the underlying filesystem. # See src/sys/ufs/ufs/README.acls for more information. options UFS_ACL options QUOTA options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_ELI # Disk encryption. options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores ##################################################################### # SYSV IPC KERNEL PARAMETERS # # Maximum number of entries in a semaphore map. #options SEMMAP=31 # Maximum number of System V semaphores that can be used on the system at # one time. #options SEMMNI=11 # Total number of semaphores system wide #options SEMMNS=61 # Total number of undo structures in system #options SEMMNU=31 # Maximum number of System V semaphores that can be used by a single process # at one time. #options SEMMSL=61 # Maximum number of operations that can be outstanding on a single System V # semaphore at one time. #options SEMOPM=101 # Maximum number of undo operations that can be outstanding on a single # System V semaphore at one time. #options SEMUME=11 # Maximum number of shared memory pages system wide. #options SHMALL=1025 # Maximum size, in bytes, of a single System V shared memory region. #options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) #options SHMMAXPGS=1025 # Minimum size, in bytes, of a single System V shared memory region. #options SHMMIN=2 # Maximum number of shared memory regions that can be used on the system # at one time. #options SHMMNI=33 # Maximum number of System V shared memory regions that can be attached to # a single process at one time. #options SHMSEG=9 ############################################################ options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. options DEVICE_POLLING options HZ=1600 ###################################################################### # The apic device enables the use of the I/O APIC for interrupt delivery. # The apic device can be used in both UP and SMP kernels, but is required # for SMP kernels. Thus, the apic device is not strictly an SMP option, # but it is a prerequisite for SMP. ## COMMENTED OUT - BREAKS ACPI IN Thinkpad Z60M #device apic # I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives device atapicam # emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus & pass) device cd # CD device pass # Passthrough device (direct SCSI access) options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver #device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc ## The following (VESA, SC_PIXEL_MODE, VGA_WIDTH90) improve behaviour of text virtual console...not REALLY needed... ## if Enabled may cause resume problems? (2006-09-06) #options VESA #options SC_PIXEL_MODE # The following option probably won't work with the LCD displays. #options VGA_WIDTH90 # support 90 column modes #The following lines will set the default colors of the kernel message. #The kernel message will be printed bright red on black background. The #reversed message will be black on red background. options SC_KERNEL_CONS_ATTR=(FG_RED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_LIGHTGREY|BG_RED) # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor #device agp # support several AGP chipsets #device drm #device radeondrm # Power management support (see NOTES for more options) #USING ACPI in z60m #device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support device cbb # cardbus (yenta) bridge device pccard # PC Card (16-bit) bus device cardbus # CardBus (32-bit) bus # Serial (COM) ports #device sio # 8250, 16[45]50 based serial ports # Parallel port #device ppc #device ppbus # Parallel port bus (required) #device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device bfe # Broadcom BCM440x 10/100 Ethernet device bge # Broadcom BCM570xx Gigabit Ethernet device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Wireless NIC cards device wlan #802.11 support device wlan_wep #802.11 WEP support device wlan_ccmp #802.11 CCMP support device wlan_tkip #802.11 TKIP support device wlan_xauth #802.11 external authenticator support device wlan_acl #802.11 MAC ACL support #device iwi #Intel(R) PRO/Wireless 2200BG> - builtin wireless card. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) device tap #Ethernet tunnel software network interface device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device disc #Discard device (ds0, ds1, etc) device gre #IP over IP tunneling # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter device pf device pflog # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device ucom # serial port over USB device uplcom # Prolific PL-2303 - Comsol's USB-Serial port device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) ---- _________________________ {Beto|Norberto|Numard} Meijome "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." Albert Einstein I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 08:20: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 4F6AF16A40F for ; Wed, 13 Sep 2006 08:20:39 +0000 (UTC) (envelope-from rvenne@dental-on-line.fr) Received: from smtp.dental-on-line.fr (smtp.dental-on-line.fr [82.234.245.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AB043D5F for ; Wed, 13 Sep 2006 08:20:37 +0000 (GMT) (envelope-from rvenne@dental-on-line.fr) Received: from [192.168.1.7] (triton.dental-on-line.net [192.168.1.7]) by smtp.dental-on-line.fr (Postfix) with ESMTP id 29495138632 for ; Wed, 13 Sep 2006 10:20:36 +0200 (CEST) Message-ID: <4507BF57.2000301@dental-on-line.fr> Date: Wed, 13 Sep 2006 10:20:39 +0200 From: rvenne@dental-on-line.fr User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: freebsd-stable References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4506C9B0.5040807@dental-on-line.fr> <20060912160907.GC962@rambler-co.ru> In-Reply-To: <20060912160907.GC962@rambler-co.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: cap_mkdb: illegal option -i. upgrade 5.4->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, 13 Sep 2006 08:20:39 -0000 Ruslan Ermilov wrote: >On Tue, Sep 12, 2006 at 04:52:32PM +0200, rvenne@dental-on-line.fr wrote: > > >>Hi list >> >>I'm upgrading 5.4 p18 to 6.1 p6. >> >>here's my tag: RELENG_6_1 >> >>I did: >>make update >>make cleanworld >>make buildworld >> >>which gives following issue: >> >>cap_mkdb: illegal option -i >> >>It seems a known problem on netbsd during buildworld compilation. here's >>the solution I'm tring: >> >>cd /usr/src/usr.bin/cap_mkdb >>make clean >>make >>make install >> >>and I'm building world again. >> >>is that a known problem on freebsd? >> >> >> >This shouldn't happen. The buildworld target detects the current >version of your system, and bootstraps cap_mkdb if necessary: > >: .if ${BOOTSTRAPPING} < 600015 >: _cap_mkdb= usr.bin/cap_mkdb >: .endif > >BOOTSTRAPPING is defined as follows: > >: .if !defined(OSRELDATE) >: .if exists(/usr/include/osreldate.h) >: OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print $$3 }' \ >: /usr/include/osreldate.h >: .else >: OSRELDATE= 0 >: .endif > >That is, it's the value of __FreeBSD_version as defined in >/usr/include/osreldate.h. If your /usr/include/osreldate.h >is lying about the current version, e.g. if you accidentally >installed the new headers, then you can force it to zero, >such as: > > make buildworld OSRELDATE=0 > > >Cheers, > > I'm pretty sure about what's happing i'd propably built my world twice...or something like that. anyway, building cap_mkdb before the world resolved the issue. -- Richard VENNE www.dental-on-line.com Phone: 01 43 27 94 24 fax: 01 43 27 66 85 From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 08:43: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 6E3D216A412 for ; Wed, 13 Sep 2006 08:43:45 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B4F343D45 for ; Wed, 13 Sep 2006 08:43:44 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 2760E5D8B; Wed, 13 Sep 2006 12:43:43 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id E0BB25D61; Wed, 13 Sep 2006 12:43:42 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8D8hiAf089904; Wed, 13 Sep 2006 12:43:44 +0400 (MSD) (envelope-from ru) Date: Wed, 13 Sep 2006 12:43:44 +0400 From: Ruslan Ermilov To: rvenne@dental-on-line.fr Message-ID: <20060913084344.GH72105@rambler-co.ru> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4506C9B0.5040807@dental-on-line.fr> <20060912160907.GC962@rambler-co.ru> <4507BF57.2000301@dental-on-line.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w3uUfsyyY1Pqa/ej" Content-Disposition: inline In-Reply-To: <4507BF57.2000301@dental-on-line.fr> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable Subject: Re: cap_mkdb: illegal option -i. upgrade 5.4->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, 13 Sep 2006 08:43:45 -0000 --w3uUfsyyY1Pqa/ej Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 10:20:39AM +0200, rvenne@dental-on-line.fr wrote: > Ruslan Ermilov wrote: >=20 > >On Tue, Sep 12, 2006 at 04:52:32PM +0200, rvenne@dental-on-line.fr wrote: > >=20 > > > >>Hi list > >> > >>I'm upgrading 5.4 p18 to 6.1 p6. > >> > >>here's my tag: RELENG_6_1 > >> > >>I did: > >>make update > >>make cleanworld > >>make buildworld > >> > >>which gives following issue: > >> > >>cap_mkdb: illegal option -i > >> > >>It seems a known problem on netbsd during buildworld compilation. here'= s=20 > >>the solution I'm tring: > >> > >>cd /usr/src/usr.bin/cap_mkdb > >>make clean > >>make > >>make install > >> > >>and I'm building world again. > >> > >>is that a known problem on freebsd? > >> > >> =20 > >> > >This shouldn't happen. The buildworld target detects the current > >version of your system, and bootstraps cap_mkdb if necessary: > > > >: .if ${BOOTSTRAPPING} < 600015 > >: _cap_mkdb=3D usr.bin/cap_mkdb > >: .endif > > > >BOOTSTRAPPING is defined as follows: > > > >: .if !defined(OSRELDATE) > >: .if exists(/usr/include/osreldate.h) > >: OSRELDATE!=3D awk '/^\#define[[:space:]]*__FreeBSD_version/ { prin= t=20 > >$$3 }' \ > >: /usr/include/osreldate.h > >: .else > >: OSRELDATE=3D 0 > >: .endif > > > >That is, it's the value of __FreeBSD_version as defined in > >/usr/include/osreldate.h. If your /usr/include/osreldate.h > >is lying about the current version, e.g. if you accidentally > >installed the new headers, then you can force it to zero, > >such as: > > > > make buildworld OSRELDATE=3D0 > > > > > >Cheers, > >=20 > > > I'm pretty sure about what's happing >=20 > i'd propably built my world twice...or something like that. anyway,=20 > building >=20 > cap_mkdb before the world resolved the issue.=20 >=20 But that's what buildworld already does (when it detects the need to do so). My point was to make it clear. :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --w3uUfsyyY1Pqa/ej Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFB8TAqRfpzJluFF4RAvUOAJ48wlBRxO5la4xeNrPcE98YQ/pu1ACgnwXg UvNq9TwZrX3DkSqZmbWUtf4= =SPLL -----END PGP SIGNATURE----- --w3uUfsyyY1Pqa/ej-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 08:54: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 BB21B16A412; Wed, 13 Sep 2006 08:54:27 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from ns2.pil.dk (ns2.pil.dk [195.41.47.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5067543D49; Wed, 13 Sep 2006 08:54:27 +0000 (GMT) (envelope-from henrik@brixandersen.dk) Received: from tirith.brixandersen.dk (osgiliath.brixandersen.dk [87.53.223.189]) by ns2.pil.dk (Postfix) with ESMTP id AD3177BAA66; Wed, 13 Sep 2006 10:54:26 +0200 (CEST) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id 1158EB93B; Wed, 13 Sep 2006 10:54:12 +0200 (CEST) Date: Wed, 13 Sep 2006 10:54:12 +0200 From: Henrik Brix Andersen To: Norberto Meijome Message-ID: <20060913085412.GB14957@tirith.brixandersen.dk> Mail-Followup-To: Norberto Meijome , freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org References: <20060913114027.4c26e702@localhost> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kORqDWCi7qDJ0mEj" Content-Disposition: inline In-Reply-To: <20060913114027.4c26e702@localhost> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ACPI resume problems in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 08:54:27 -0000 --kORqDWCi7qDJ0mEj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 11:40:27AM +1000, Norberto Meijome wrote: > $ uname -a > FreeBSD ayiin.xxx.com 6.1-RELEASE-p6 FreeBSD 6.1-RELEASE-p6 #23: > Tue Sep 12 14:52:32 EST 2006 > root@ayiin.xxx.com:/usr/obj/usr/src/sys/AYIIN i386 >=20 > The only thing I've noticed that in how my lappy works now is that if_iwi= 0 is > loaded on startup, but iw_bss and firmware.ko are not. I can load them by= hand, > but haven't been able to test to see if it actually works (i have a feeli= ng it > doesnt). >=20 > I have installed > iwi-firmware-kmod-3.0_1 Intel PRO/Wireless 2200 Firmware Kernel Module You will need net/iwi-firmware (not net/iwi-firmware-kmod) for 6.1-RELEASE. Regards, Brix --=20 Henrik Brix Andersen --kORqDWCi7qDJ0mEj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: GnuPG signed iD8DBQFFB8c0v+Q4flTiePgRAsGuAJ9Li0aYZGsB3cqKWeZOm50PPeBv6ACeOLG/ u1NY9qzLwIZudSFl1SDxi0o= =v03U -----END PGP SIGNATURE----- --kORqDWCi7qDJ0mEj-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 08:56:51 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 C780216A403 for ; Wed, 13 Sep 2006 08:56:51 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBE0943D98 for ; Wed, 13 Sep 2006 08:56:34 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tedgnm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8D8uRv4062186 for ; Wed, 13 Sep 2006 10:56:33 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8D8uR5U062185; Wed, 13 Sep 2006 10:56:27 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 10:56:27 +0200 (CEST) Message-Id: <200609130856.k8D8uR5U062185@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4506DE38.10803@mikestammer.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 10:56:33 +0200 (CEST) Cc: Subject: Re: FreeBSD 6.1-RELEASE ->FreeBSD 6.1-Stable 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: Wed, 13 Sep 2006 08:56:51 -0000 Eric wrote: > Oliver Fromme wrote: > > Vince wrote: > > > Eric wrote: > > > > S. M. Ibrahim (Lavlu) wrote: > > > > > Now i am using FreeBSD 6.1-RELEASE. Now want to upgrade to FreeBSD > > > > > 6.1-Stable. What is the easy process ? > > > > > > > > this works well > > > > > > > > http://mikestammer.com/dokuwiki/doku.php?id=bsd:updateos > > > the cvsup part looks ok but for the actual build then read > > > /usr/src/Makefile > > > for the recommended procedure. > > > > It's better to read /usr/src/UPDATING. > > my wiki above mentions reading UPDATING (in step 3) before starting... > > UPDATING pretty much says exactly the same thing, except its 80% of the > way into UPDATING. The wiki above also explains things a bit more for > someone who has never done it. I wasn't refering to your wiki (I didn't even look at it). I was refering to Vince's comment that /usr/src/Makefile should be read for the recommended procedure, which is wrong. The recommended procedure (according to the FreeBSD Handbook) is in /usr/src/UPDATING, which is more up-to-date than the comments in the Makefile. All of that is explained in great detail in the FreeBSD Handbook, section 21.4 "Rebuilding ``world''". I think people should look at the Handbook more often; it contains answers to many questions on the mailing lists, including the one that started this thread. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "We, the unwilling, led by the unknowing, are doing the impossible for the ungrateful. We have done so much, for so long, with so little, we are now qualified to do anything with nothing."         -- Mother Teresa From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:01: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 F306A16A4EB for ; Wed, 13 Sep 2006 09:01:39 +0000 (UTC) (envelope-from kama@pvp.se) Received: from ms1.as.pvp.se (dns.pvp.se [213.64.187.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE37943D62 for ; Wed, 13 Sep 2006 08:59:53 +0000 (GMT) (envelope-from kama@pvp.se) Received: by ms1.as.pvp.se (Postfix, from userid 1001) id DF3CEA9; Wed, 13 Sep 2006 10:59:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ms1.as.pvp.se (Postfix) with ESMTP id DB2B3A7 for ; Wed, 13 Sep 2006 10:59:51 +0200 (CEST) Date: Wed, 13 Sep 2006 10:59:51 +0200 (CEST) From: kama X-X-Sender: kama@ns1.as.pvp.se To: freebsd-stable@freebsd.org Message-ID: <20060913105935.P87498@ns1.as.pvp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 09:01:40 -0000 ---------- Forwarded message ---------- Date: Tue, 12 Sep 2006 11:02:42 -0400 From: John Baldwin To: freebsd-current@freebsd.org Cc: kama Subject: Re: 6.2? On Tuesday 12 September 2006 07:12, kama wrote: > > I just updated the sources on two of my machines and found: > > $ uname -sr > FreeBSD 6.2-PRERELEASE > > Is this a mistake or is it actually a prerelease? Why isnt there any > notice about it on the webpage or on this mailing list? The notice would be sent to stable@, not current@ as RELENG_6 is a stable branch. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:06: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 601BB16A4ED for ; Wed, 13 Sep 2006 09:06:15 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id F221A43DEB for ; Wed, 13 Sep 2006 09:05:50 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ividqf@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8D95ipZ062790 for ; Wed, 13 Sep 2006 11:05:49 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8D95idk062789; Wed, 13 Sep 2006 11:05:44 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 11:05:44 +0200 (CEST) Message-Id: <200609130905.k8D95idk062789@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20060912161603.R1031@ganymede.hub.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 11:05:50 +0200 (CEST) Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} 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: Wed, 13 Sep 2006 09:06:15 -0000 Marc G. Fournier wrote: > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > building kernel/world? I know awhile back it wasn't recommended to go > above -O2, for instance, but suspect that has changed ... ? The best optimization is probably to not override the defaults at all, because they're already pretty optimal. In fact, by overriding the defaults there's a good chance to make things worse. :-) The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". Anything above -O2 isn't supported, and using -O2 without -fno-strict-aliasing also isn't supported (and will create broken code for some programs). A common mistake is to specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. That'll shot you in the foot sooner or later. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:12: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 858C716A501 for ; Wed, 13 Sep 2006 09:12:44 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6117343D45 for ; Wed, 13 Sep 2006 09:12:43 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mrgrip@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8D9CaQN063257; Wed, 13 Sep 2006 11:12:42 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8D9CaUP063256; Wed, 13 Sep 2006 11:12:36 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 11:12:36 +0200 (CEST) Message-Id: <200609130912.k8D9CaUP063256@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, jonathan@kc8onw.net In-Reply-To: <450752F6.4050109@kc8onw.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 11:12:42 +0200 (CEST) Cc: Subject: Re: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, jonathan@kc8onw.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 09:12:44 -0000 Jonathan Stewart wrote: > I set up a new server recently and transferred all the information from > my old server over. I tried to use unison to synchronize the backup of > pictures I have taken and noticed that a large number of pictures where > marked as changed on the server. After checking the pictures by hand I > confirmed that many of the pictures on the server were corrupted. I > attempted to use unison to update the files on the server with the > correct local copies but it would fail on almost all the files with the > message "destination updated during synchronization." > > It appears the corruption happens during the read process because when I > recompare the files in a graphical diff tool between cache flushes the > differences move around!?!?!? The differences also appear to be very > small for the most part, single bytes scattered throughout the file. I > really have no idea what is causing the problem and would like to pin it > down so I can either replace hardware if it's bad or fix whatever the > bug is. That very much sounds like bad RAM, or overclocked CPU or bus. I assume you do not overclock, so I recommend you replace your RAM modules and check if the symptoms are gone. Also check your BIOS settings for the RAM timings. Setting the timings to more conservative values might already solve the problem. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code" (taken from comp.lang.awk FAQ) From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:17: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 A80D816A416 for ; Wed, 13 Sep 2006 09:17:19 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F12243D4C for ; Wed, 13 Sep 2006 09:17:18 +0000 (GMT) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (localhost.cmotd.com [127.0.0.1]) by sun-fish.com (Postfix) with ESMTP id 188A8384F5 for ; Wed, 13 Sep 2006 11:17:16 +0200 (CEST) Received: from [192.168.3.112] (boar.cmotd.com [192.168.3.112]) by sun-fish.com (Postfix) with ESMTP id D51F4384F3 for ; Wed, 13 Sep 2006 11:17:15 +0200 (CEST) Message-ID: <4507CC9B.60704@sun-fish.com> Date: Wed, 13 Sep 2006 12:17:15 +0300 From: Stefan Lambrev User-Agent: Thunderbird 1.5.0.5 (X11/20060808) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <200609130905.k8D95idk062789@lurza.secnetix.de> In-Reply-To: <200609130905.k8D95idk062789@lurza.secnetix.de> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 09:17:19 -0000 Hello, Oliver Fromme wrote: > Marc G. Fournier wrote: > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > building kernel/world? I know awhile back it wasn't recommended to go > > above -O2, for instance, but suspect that has changed ... ? > > The best optimization is probably to not override the > defaults at all, because they're already pretty optimal. > In fact, by overriding the defaults there's a good chance > to make things worse. :-) > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > Anything above -O2 isn't supported, and using -O2 without > -fno-strict-aliasing also isn't supported (and will create > broken code for some programs). A common mistake is to > specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > That'll shot you in the foot sooner or later. > > Best regards > Oliver > > May be default flags have to be set here: /usr/src/share/examples/etc/make.conf ? I'm asking because in this file I read: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to "-O" or -O2 before submitting bug # reports without patches to the developers. # #CFLAGS= -O -pipe May be "-fno-strict-aliasing" have to be added here then ? -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:21: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 8667C16A403 for ; Wed, 13 Sep 2006 09:21:41 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id D65D643D49 for ; Wed, 13 Sep 2006 09:21:40 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (efezkl@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8D9LYRK063611; Wed, 13 Sep 2006 11:21:39 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8D9LYxd063610; Wed, 13 Sep 2006 11:21:34 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 11:21:34 +0200 (CEST) Message-Id: <200609130921.k8D9LYxd063610@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, kama@pvp.se In-Reply-To: <20060913105935.P87498@ns1.as.pvp.se> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 11:21:39 +0200 (CEST) Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, kama@pvp.se List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 09:21:41 -0000 kama wrote: > I just updated the sources on two of my machines and found: > > $ uname -sr > FreeBSD 6.2-PRERELEASE > > Is this a mistake or is it actually a prerelease? It's not a mistake. RELENG_6 has been frozen on Sep. 10th in preparation of the upcoming 6.2-RELEASE, so it's now in "pre-release" state. > Why isnt there any notice about it on the webpage > or on this mailing list? It's on the webpage (under "Release Engineering"): http://www.freebsd.org/releng/ I don't think there's need to announce it on this mailing list. The fact that RELENG_6 entered code-freeze is important for comitters and (some) developers, but not for normal users of the -stable branch. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:26: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 2650616A40F for ; Wed, 13 Sep 2006 09:26:07 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DBF143D55 for ; Wed, 13 Sep 2006 09:26:06 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wfwnet@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8D9Q0qO063754 for ; Wed, 13 Sep 2006 11:26:05 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8D9Q0XZ063753; Wed, 13 Sep 2006 11:26:00 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 11:26:00 +0200 (CEST) Message-Id: <200609130926.k8D9Q0XZ063753@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4507CC9B.60704@sun-fish.com> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 11:26:05 +0200 (CEST) Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} 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: Wed, 13 Sep 2006 09:26:07 -0000 Stefan Lambrev wrote: > Oliver Fromme wrote: > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > Anything above -O2 isn't supported, and using -O2 without > > -fno-strict-aliasing also isn't supported (and will create > > broken code for some programs). A common mistake is to > > specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > > That'll shot you in the foot sooner or later. > > May be default flags have to be set here: > /usr/src/share/examples/etc/make.conf ? > I'm asking because in this file I read: > > # CFLAGS controls the compiler settings used when compiling C code. > # Note that optimization settings other than -O and -O2 are not recommended > # or supported for compiling the world or the kernel - please revert any > # nonstandard optimization settings to "-O" or -O2 before submitting bug > # reports without patches to the developers. > # > #CFLAGS= -O -pipe > > May be "-fno-strict-aliasing" have to be added here then ? Yes, you are right. I think a clarification should be added to the make.conf(5) manual page and to the /usr/share/examples/etc/make.conf file. Someone care to submit a PR ...? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." -- RFC 1925 From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 09:40: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 4311C16A40F for ; Wed, 13 Sep 2006 09:40:25 +0000 (UTC) (envelope-from robert@mpe.mpg.de) Received: from mpemail.mpe.mpg.de (mpemail.mpe-garching.mpg.de [130.183.137.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5948743D82 for ; Wed, 13 Sep 2006 09:40:15 +0000 (GMT) (envelope-from robert@mpe.mpg.de) Received: from robert3.mpe-garching.mpg.de ([130.183.136.84]) by mpemail.mpe.mpg.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1GNRE4-0002J2-Sq for freebsd-stable@freebsd.org; Wed, 13 Sep 2006 11:40:13 +0200 Message-ID: <4507D1F8.7040508@mpe.mpg.de> Date: Wed, 13 Sep 2006 11:40:08 +0200 From: Klaus Robert Suetterlin User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20060629 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Id: robert Subject: PAE-SMP kernel generates NMI (PCI bus errors) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 09:40:25 -0000 Hi all, I have a legacy system --- 4xXeon (PIII, 700MHz, 2MB cache), 16GB ECC RAM and 300GB Harddisk on an ICP Vortex Raid Controller --- which I tried to bring from RedHat6 to something more current and supported. (Un)Fortunately the only system that wanted to install on the machine is FreeBSD6. When I use a non-SMP kernel either with or without PAE everything works ok. When I use a SMP non-PAE kernel everything works ok, too. When I use a SMP+PAE kernel the system starts throwing NMIs (most likely due to PCI system bus errors, which is the only error reporting activated in BIOS) until the system finally freezes (which is most likely when the system event log of the server is full). I can give a lot more diagnostics to anyone interested in solving this, but I need a little handholding. Regards, Robert S From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 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 103DA16A407 for ; Wed, 13 Sep 2006 10:02:43 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-50634715.catv.broadband.hu [80.99.71.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C92943D45 for ; Wed, 13 Sep 2006 10:02:39 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <4507D7FB.7030404@antiszoc.hu> Date: Wed, 13 Sep 2006 12:05:47 +0200 From: =?ISO-8859-1?Q?Andras_G=F3t?= User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG References: <200609130921.k8D9LYxd063610@lurza.secnetix.de> In-Reply-To: <200609130921.k8D9LYxd063610@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 10:02:43 -0000 Oliver Fromme wrote: > kama wrote: > > I just updated the sources on two of my machines and found: > > > > $ uname -sr > > FreeBSD 6.2-PRERELEASE > > > > Is this a mistake or is it actually a prerelease? > > It's not a mistake. RELENG_6 has been frozen on Sep. 10th > in preparation of the upcoming 6.2-RELEASE, so it's now in > "pre-release" state. > > > Why isnt there any notice about it on the webpage > > or on this mailing list? > > It's on the webpage (under "Release Engineering"): > > http://www.freebsd.org/releng/ > > I don't think there's need to announce it on this mailing > list. The fact that RELENG_6 entered code-freeze is > important for comitters and (some) developers, but not for > normal users of the -stable branch. > > Best regards > Oliver > > Sure but it's only a schedule. The main purpose of the public release process would be that WE the users can see/check what are the problems that needs testing or anything. And an other main purpose is to do planning of the upgrade, if needed. I think I shouldn't have to remind you on this. :) Regards, Andras From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:08: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 AD6AA16A403 for ; Wed, 13 Sep 2006 10:08:55 +0000 (UTC) (envelope-from freebsd-stable@voidcaptain.com) Received: from mx4.x15.net (mx4.x15.net [69.55.237.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E0243D45 for ; Wed, 13 Sep 2006 10:08:55 +0000 (GMT) (envelope-from freebsd-stable@voidcaptain.com) Received: from j1.x15.net [63.196.213.76] by mx4.x15.net with ESMTP id 608060222X1GNRfq0006AT5J; Wed, 13 Sep 2006 10:08:54 +0000 Message-ID: <4507D897.4030502@voidcaptain.com> Date: Wed, 13 Sep 2006 03:08:23 -0700 From: Pete Slagle MIME-Version: 1.0 To: olli@lurza.secnetix.de References: <200609130905.k8D95idk062789@lurza.secnetix.de> In-Reply-To: <200609130905.k8D95idk062789@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@Freebsd.org Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 10:08:55 -0000 Oliver Fromme wrote: > Marc G. Fournier wrote: > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > building kernel/world? I know awhile back it wasn't recommended to go > > above -O2, for instance, but suspect that has changed ... ? > > The best optimization is probably to not override the > defaults at all, because they're already pretty optimal. > In fact, by overriding the defaults there's a good chance > to make things worse. :-) > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > Anything above -O2 isn't supported, and using -O2 without > -fno-strict-aliasing also isn't supported (and will create > broken code for some programs). A common mistake is to > specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > That'll shot you in the foot sooner or later. /etc/make.conf on most of my 6.1 machines contains (in part) this: CFLAGS= -O2 -pipe -fno-strict-aliasing COPTFLAGS= -O2 -pipe I no longer remember exactly why, but at some point I must have understood or assumed that to be the recommendation. Just to be completely clear, are you saying that this CFLAGS= -O2 -pipe -fno-strict-aliasing COPTFLAGS= -O2 -pipe -fno-strict-aliasing would be better in the general case? From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:19: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 0008116A407 for ; Wed, 13 Sep 2006 10:19:15 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7256143D45 for ; Wed, 13 Sep 2006 10:19:15 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 2188D5C74; Wed, 13 Sep 2006 14:19:14 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id DC1AE5C0D; Wed, 13 Sep 2006 14:19:13 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8DAJFw9014148; Wed, 13 Sep 2006 14:19:15 +0400 (MSD) (envelope-from ru) Date: Wed, 13 Sep 2006 14:19:15 +0400 From: Ruslan Ermilov To: Pete Slagle Message-ID: <20060913101915.GA13946@rambler-co.ru> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507D897.4030502@voidcaptain.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <4507D897.4030502@voidcaptain.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable@freebsd.org, olli@lurza.secnetix.de Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 10:19:16 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 03:08:23AM -0700, Pete Slagle wrote: > Oliver Fromme wrote: >=20 > > Marc G. Fournier wrote: > > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf = for=20 > > > building kernel/world? I know awhile back it wasn't recommended to = go=20 > > > above -O2, for instance, but suspect that has changed ... ? > >=20 > > The best optimization is probably to not override the > > defaults at all, because they're already pretty optimal. > > In fact, by overriding the defaults there's a good chance > > to make things worse. :-) > >=20 > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > Anything above -O2 isn't supported, and using -O2 without > > -fno-strict-aliasing also isn't supported (and will create > > broken code for some programs). A common mistake is to > > specify CFLAGS=3D"-O2 -pipe" and omit -fno-strict-aliasing. > > That'll shot you in the foot sooner or later. >=20 > /etc/make.conf on most of my 6.1 machines contains (in part) this: >=20 > CFLAGS=3D -O2 -pipe -fno-strict-aliasing > COPTFLAGS=3D -O2 -pipe >=20 > I no longer remember exactly why, but at some point I must have > understood or assumed that to be the recommendation. >=20 > Just to be completely clear, are you saying that this >=20 > CFLAGS=3D -O2 -pipe -fno-strict-aliasing > COPTFLAGS=3D -O2 -pipe -fno-strict-aliasing >=20 > would be better in the general case? >=20 Doesn't matter; kern.pre.mk will automatically add -fno-strict-aliasing to COPTFLAGS if needed: : . if !empty(COPTFLAGS:M-O[23s]) && empty(COPTFLAGS:M-fno-strict-aliasing) : COPTFLAGS+=3D -fno-strict-aliasing : . endif Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFB9sjqRfpzJluFF4RAoyBAJ9IHM20tsHAKNyrBKgGcHhMIk2b1ACghzQ/ nXWu0UoZxA5foao4PwGhf2k= =SMqG -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:21:47 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 3361516A782 for ; Wed, 13 Sep 2006 10:21:47 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id C06A043D66 for ; Wed, 13 Sep 2006 10:21:34 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id E8B4D5DCB for ; Wed, 13 Sep 2006 14:21:33 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id C80D55DC4 for ; Wed, 13 Sep 2006 14:21:33 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8DALZUc014213 for freebsd-stable@FreeBSD.ORG; Wed, 13 Sep 2006 14:21:35 +0400 (MSD) (envelope-from ru) Date: Wed, 13 Sep 2006 14:21:35 +0400 From: Ruslan Ermilov To: freebsd-stable@FreeBSD.ORG Message-ID: <20060913102135.GB13946@rambler-co.ru> References: <4507CC9B.60704@sun-fish.com> <200609130926.k8D9Q0XZ063753@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H+4ONPRPur6+Ovig" Content-Disposition: inline In-Reply-To: <200609130926.k8D9Q0XZ063753@lurza.secnetix.de> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 10:21:47 -0000 --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 11:26:00AM +0200, Oliver Fromme wrote: > Stefan Lambrev wrote: > > Oliver Fromme wrote: > > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > > Anything above -O2 isn't supported, and using -O2 without > > > -fno-strict-aliasing also isn't supported (and will create > > > broken code for some programs). A common mistake is to > > > specify CFLAGS=3D"-O2 -pipe" and omit -fno-strict-aliasing. > > > That'll shot you in the foot sooner or later. > >=20 > > May be default flags have to be set here: > > /usr/src/share/examples/etc/make.conf ? > > I'm asking because in this file I read: > >=20 > > # CFLAGS controls the compiler settings used when compiling C code. > > # Note that optimization settings other than -O and -O2 are not recomm= ended > > # or supported for compiling the world or the kernel - please revert a= ny > > # nonstandard optimization settings to "-O" or -O2 before submitting b= ug > > # reports without patches to the developers. > > # > > #CFLAGS=3D -O -pipe > >=20 > > May be "-fno-strict-aliasing" have to be added here then ? >=20 > Yes, you are right. I think a clarification should > be added to the make.conf(5) manual page and to the > /usr/share/examples/etc/make.conf file. >=20 > Someone care to submit a PR ...? >=20 Should be fixed in src/share/examples/etc/make.conf,v 1.277. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --H+4ONPRPur6+Ovig Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFB9uvqRfpzJluFF4RAholAJ0QvR8eODNp49f1ndQQBrUrWe6JlgCggj8z 7j5fzEriQVqZNubb6Z/DQFk= =9C7R -----END PGP SIGNATURE----- --H+4ONPRPur6+Ovig-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:38: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 648E116A407 for ; Wed, 13 Sep 2006 10:38:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958DF43D45 for ; Wed, 13 Sep 2006 10:38:58 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tedgnm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8DAcpa0068954 for ; Wed, 13 Sep 2006 12:38:57 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8DAcpc7068953; Wed, 13 Sep 2006 12:38:51 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 12:38:51 +0200 (CEST) Message-Id: <200609131038.k8DAcpc7068953@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <4507D7FB.7030404@antiszoc.hu> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 12:38:57 +0200 (CEST) Cc: Subject: Re: 6.2? (fwd) 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: Wed, 13 Sep 2006 10:38:59 -0000 Andras Gót wrote: > Oliver Fromme wrote: > > kama wrote: > > > Why isnt there any notice about it on the webpage > > > or on this mailing list? > > > > It's on the webpage (under "Release Engineering"): > > > > http://www.freebsd.org/releng/ > > > > I don't think there's need to announce it on this mailing > > list. The fact that RELENG_6 entered code-freeze is > > important for comitters and (some) developers, but not for > > normal users of the -stable branch. > > Sure but it's only a schedule. That's true, and the schedule will most probably change. Currently the release is listed for Oct. 9th, but I bet that it'll be delayed. > The main purpose of the public release process would be that WE > the users can see/check what are the problems that needs testing > or anything. Yes, which will be announced when BETA state begins, I assume. PRERELEASE isn't BETA (yet). > And an other main purpose is to do planning of the upgrade Uhm, would you please explain? What kind of upgrade depends on entering the pre-release state? When you're tracking -stable, then now is neither better nor worse a time for updating, except for the fact that -- due to the code freeze -- the code might have a tendency to stabilize better than before, because MFCs and commits that aren't bug fixes are held off. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 10:56: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 A66C816A412 for ; Wed, 13 Sep 2006 10:56:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1C8443D46 for ; Wed, 13 Sep 2006 10:56:44 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (pkdapa@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8DAubux069762; Wed, 13 Sep 2006 12:56:43 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8DAubr9069760; Wed, 13 Sep 2006 12:56:37 +0200 (CEST) (envelope-from olli) From: Oliver Fromme Message-Id: <200609131056.k8DAubr9069760@lurza.secnetix.de> To: freebsd-stable@voidcaptain.com (Pete Slagle) Date: Wed, 13 Sep 2006 12:56:37 +0200 (CEST) In-Reply-To: <4507D897.4030502@voidcaptain.com> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 12:56:43 +0200 (CEST) Cc: freebsd-stable@Freebsd.org Subject: Re: optimization levels for 6-STABLE build{kernel,world} 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: Wed, 13 Sep 2006 10:56:45 -0000 Pete Slagle wrote: > Oliver Fromme wrote: > > Marc G. Fournier wrote: > > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > > building kernel/world? I know awhile back it wasn't recommended to go > > > above -O2, for instance, but suspect that has changed ... ? > > > > The best optimization is probably to not override the > > defaults at all, because they're already pretty optimal. > > In fact, by overriding the defaults there's a good chance > > to make things worse. :-) > > > > The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > Anything above -O2 isn't supported, and using -O2 without > > -fno-strict-aliasing also isn't supported (and will create > > broken code for some programs). A common mistake is to > > specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > > That'll shot you in the foot sooner or later. > > /etc/make.conf on most of my 6.1 machines contains (in part) this: > > CFLAGS= -O2 -pipe -fno-strict-aliasing Which is exactly the default, so there's no reason to specify it at all. If, at some point in the future, the default changes (e.g. -O3 is considered "good and safe", or any other -fno-xxx option becomes necessary with -O2), then you won't benefit from it, because you override it. > COPTFLAGS= -O2 -pipe As Ruslan explained, -fno-strict-aliasing will be added automatically in the case of COPTFLAGS if necessary. So my recommendation is still: Don't override CFLAGS or COPTFLAGS. Chances are that you make things worse, now or at some point in the future. > Just to be completely clear, are you saying that this > > CFLAGS= -O2 -pipe -fno-strict-aliasing > COPTFLAGS= -O2 -pipe -fno-strict-aliasing > > would be better in the general case? In the general case, it would be better to remove those two lines completely. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. (On the statement print "42 monkeys" + "1 snake":) By the way, both perl and Python get this wrong. Perl gives 43 and Python gives "42 monkeys1 snake", when the answer is clearly "41 monkeys and 1 fat snake". -- Jim Fulton From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 11:07: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 A652A16A415 for ; Wed, 13 Sep 2006 11:07:26 +0000 (UTC) (envelope-from kama@pvp.se) Received: from ms1.as.pvp.se (dns.pvp.se [213.64.187.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADC2043D73 for ; Wed, 13 Sep 2006 11:07:21 +0000 (GMT) (envelope-from kama@pvp.se) Received: by ms1.as.pvp.se (Postfix, from userid 1001) id 5E05AA9; Wed, 13 Sep 2006 13:07:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ms1.as.pvp.se (Postfix) with ESMTP id 59DF0A7 for ; Wed, 13 Sep 2006 13:07:20 +0200 (CEST) Date: Wed, 13 Sep 2006 13:07:20 +0200 (CEST) From: kama X-X-Sender: kama@ns1.as.pvp.se To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200609131038.k8DAcpc7068953@lurza.secnetix.de> Message-ID: <20060913125850.T90966@ns1.as.pvp.se> References: <200609131038.k8DAcpc7068953@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 11:07:26 -0000 On Wed, 13 Sep 2006, Oliver Fromme wrote: > Andras Gót wrote: > > Oliver Fromme wrote: > > > kama wrote: > > > > Why isnt there any notice about it on the webpage > > > > or on this mailing list? > > > > > > It's on the webpage (under "Release Engineering"): > > > > > > http://www.freebsd.org/releng/ > > > > > > I don't think there's need to announce it on this mailing > > > list. The fact that RELENG_6 entered code-freeze is > > > important for comitters and (some) developers, but not for > > > normal users of the -stable branch. > > > > Sure but it's only a schedule. > > That's true, and the schedule will most probably change. > Currently the release is listed for Oct. 9th, but I bet > that it'll be delayed. I disagree, I would like to have an notice about it. Even though it might not say much. Just a "The code of the stable branch has been freezed due to the upcomming release of X.Y" > > The main purpose of the public release process would be that WE > > the users can see/check what are the problems that needs testing > > or anything. > > Yes, which will be announced when BETA state begins, I > assume. PRERELEASE isn't BETA (yet). PR->BETA->RC->REL ? Is that the correct order? Never the less. I was thinking of RC and not PR, when I posted the message. And search for the TODO list on the webpage. /Bjorn From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 11:53:32 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 6E7FD16A403 for ; Wed, 13 Sep 2006 11:53:32 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1329343D45 for ; Wed, 13 Sep 2006 11:53:31 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1GNTJ4-000AS4-1E; Wed, 13 Sep 2006 12:53:30 +0100 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.61 (FreeBSD)) (envelope-from ) id 1GNTJ3-000JMQ-MJ; Wed, 13 Sep 2006 12:53:29 +0100 To: freebsd-stable@FreeBSD.ORG, kama@pvp.se In-Reply-To: <20060913125850.T90966@ns1.as.pvp.se> Message-Id: From: Pete French Date: Wed, 13 Sep 2006 12:53:29 +0100 Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 11:53:32 -0000 > I disagree, I would like to have an notice about it. Even though it might > not say much. Just a "The code of the stable branch has been freezed due > to the upcomming release of X.Y" It is kind of useful, because it's the code freeze point at which I start re-scheduling my work day so I can do BSD testing. I can't justify tracking all the time on work machine unfortunately, but I do like to make an effort to test thoroughly before something is released (the more the better, right?) so it's good to know these things. -pcf. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 12:09: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 B928416A40F for ; Wed, 13 Sep 2006 12:09:26 +0000 (UTC) (envelope-from spamd@kc8onw.net) Received: from smtp3.fuse.net (mail-out3.fuse.net [216.68.8.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 615BC43D77 for ; Wed, 13 Sep 2006 12:09:16 +0000 (GMT) (envelope-from spamd@kc8onw.net) Received: from gx6.fuse.net ([72.49.10.62]) by smtp3.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060913120911.JSZX20597.smtp3.fuse.net@gx6.fuse.net> for ; Wed, 13 Sep 2006 08:09:11 -0400 Received: from kb8fcl.kc8onw.net ([72.49.10.62]) by gx6.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060913120911.DFHU10743.gx6.fuse.net@kb8fcl.kc8onw.net> for ; Wed, 13 Sep 2006 08:09:11 -0400 Received: from mail.kc8onw.net (unknown [204.117.152.87]) by kb8fcl.kc8onw.net (Postfix) with ESMTP id 04D85A173F for ; Wed, 13 Sep 2006 08:09:08 -0400 (EDT) Received: by mail.kc8onw.net (Postfix, from userid 58) id 69BB2285EE; Wed, 13 Sep 2006 08:09:07 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on server.kc8onw.net X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=ham version=3.1.5 Received: from [10.70.3.254] (unknown [10.70.3.254]) by mail.kc8onw.net (Postfix) with ESMTP id 09E5028568; Wed, 13 Sep 2006 08:09:05 -0400 (EDT) Message-ID: <4507F4DF.3000605@kc8onw.net> Date: Wed, 13 Sep 2006 08:09:03 -0400 From: Jonathan Stewart User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, jonathan@kc8onw.net References: <200609130912.k8D9CaUP063256@lurza.secnetix.de> In-Reply-To: <200609130912.k8D9CaUP063256@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 12:09:26 -0000 Oliver Fromme wrote: > Jonathan Stewart wrote: > > I set up a new server recently and transferred all the information from > > my old server over. I tried to use unison to synchronize the backup of > > pictures I have taken and noticed that a large number of pictures where > > marked as changed on the server. After checking the pictures by hand I > > confirmed that many of the pictures on the server were corrupted. I > > attempted to use unison to update the files on the server with the > > correct local copies but it would fail on almost all the files with the > > message "destination updated during synchronization." > > > > It appears the corruption happens during the read process because when I > > recompare the files in a graphical diff tool between cache flushes the > > differences move around!?!?!? The differences also appear to be very > > small for the most part, single bytes scattered throughout the file. I > > really have no idea what is causing the problem and would like to pin it > > down so I can either replace hardware if it's bad or fix whatever the > > bug is. > > That very much sounds like bad RAM, or overclocked CPU > or bus. I assume you do not overclock, so I recommend > you replace your RAM modules and check if the symptoms > are gone. > > Also check your BIOS settings for the RAM timings. > Setting the timings to more conservative values might > already solve the problem. Thanks for the suggestions but I have tried lowering the clock rate on the processor and and the RAM speed with no luck whatsoever. I appear to have forgotten to mention that the problem appears no matter how I read the file, unison, md5, etc. 1 out of maybe 100 times it will read correctly. I have another drive that I use for the OS and I have done many buildworlds/kernels without problems on that drive as well as compiling some very large software packages. I'm wondering if a possible cause is the controller ignoring read errors from the hard drive but I would think more than the occasional single byte would be changed. I'm thinking about maybe trying to dd the file from the raw device in an attempt to see if the problem is occurring in the filesystem code or is lower level yet. Any suggestions on how to locate the file on the disk or how to isolate the problem better are welcome. I don't mind doing the work I just have no idea where to look/what to try next. Thanks, Jonathan From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 13:13: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 7CCA316A403 for ; Wed, 13 Sep 2006 13:13:35 +0000 (UTC) (envelope-from smtpreturn@resp.powersourceonline.com) Received: from mediab.resp.powersourceonline.com (mediab.resp.powersourceonline.com [66.161.124.233]) by mx1.FreeBSD.org (Postfix) with SMTP id 2782A43D45 for ; Wed, 13 Sep 2006 13:13:34 +0000 (GMT) (envelope-from smtpreturn@resp.powersourceonline.com) Date: Wed, 13 Sep 2006 09:13:24 -0400 Message-Id: <1158153204.240.447117MSOSI3232017:133OSIMS@resp.powersourceonline.com> From: "PowerSource Online" To: freebsd-stable@freebsd.org X-Mailer: eBizmailer3.6 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Request quotes for Computer equipment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PowerSource Online List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 13:13:35 -0000 =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D IBM, HP, Compaq, Dell, Toshiba, Cisco, 3Com, Epson, Samsung, Sony and Ma= ny More =0D Laptops, Desktops, Servers, Printers, Networking and Po= int of Sale & More=0D =0D =0D =0D =0D =0D =0D =0D Dealers =0D Resellers =0D Brokers =0D Service Companies<= /p>=0D Maintenance Companies =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D [1][USEMAP:Fre=]=0D =0D =0D =0D =0D [3D"h=] =0D Search Inven= tory =0D =0D =0D [marketi=] =0D Send Requests For Quotes=0D =0D =0D [marketi=] =0D Contact Vendors Directly=0D =0D =0D [marketi=] =0D Access Classifieds =0D =0D =0D [marketi=] =0D For Sale =0D =0D =0D [marketi=] =0D Want to Buy=0D =0D =0D =0D =0D =0D =0D =0D =0D 100= 0's of Buyers, =0D 100's of Stocking Vendor= s, =0D 1.5 million lines of Inventory= , =0D Nearly 2 million part searches= a month =0D Contact us today=0D [2]support@powersourceonline.com =0D 888-265-3302 (U.S. = & Canada) =0D 1-450-677-7399 (International) = =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D Please do not reply to this email . If you have = any comments or questions regarding this message or the PowerSource Onlin= e service, please send an email to: [3]info@powersourceonline.com or visit us online: [4]www.powersourceonline.c= om =0D =0D This is an advertisement from PowerSource= Online. =0D If you no longer wish to receive news and special o= ffers from PowerSource Online, [5]unsubscribe . =0D PowerSource Online =0D 1010 de Sérigny Suite 800 - Longueuil, CANADA - J4K 5G7 =0D Tel: 1(888) 265-3302 - International: 001 (450) 677-7399 =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D [3D] =0D References Visible links 1. LYNXIMGMAP:file://localhost/tmp/3D"#Map" 2. 3D"mailto:support@powersourceonline.= 3. 3D"mailto:info@powersourceonl= 4. file://localhost/tmp/3D= 5. 3D"http://resp.powersourceonline.c=/ Hidden links: 6. 3D"http://re=/ 7. 3D"http://resp.powersourceonline.com/rspbp/= 8. 3D"http://resp.powersou=/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 13:17:27 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 1A1FE16A403 for ; Wed, 13 Sep 2006 13:17:27 +0000 (UTC) (envelope-from smtpreturn@resp.powersourceonline.com) Received: from mediaa.resp.powersourceonline.com (mediaa.resp.powersourceonline.com [66.161.124.232]) by mx1.FreeBSD.org (Postfix) with SMTP id 8838243D6B for ; Wed, 13 Sep 2006 13:17:26 +0000 (GMT) (envelope-from smtpreturn@resp.powersourceonline.com) Date: Wed, 13 Sep 2006 09:17:21 -0400 Message-Id: <1158153441.240.447117MSOSI3237297:133OSIMS@resp.powersourceonline.com> From: "PowerSource Online" To: stable@freebsd.org X-Mailer: eBizmailer3.6 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Request quotes for Computer equipment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PowerSource Online List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 13:17:27 -0000 =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D IBM, HP, Compaq, Dell, Toshiba, Cisco, 3Com, Epson, Samsung, Sony and Ma= ny More =0D Laptops, Desktops, Servers, Printers, Networking and Po= int of Sale & More=0D =0D =0D =0D =0D =0D =0D =0D Dealers =0D Resellers =0D Brokers =0D Service Companies<= /p>=0D Maintenance Companies =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D [1][USEMAP:Fre=]=0D =0D =0D =0D =0D [3D"h=] =0D Search Inven= tory =0D =0D =0D [marketi=] =0D Send Requests For Quotes=0D =0D =0D [marketi=] =0D Contact Vendors Directly=0D =0D =0D [marketi=] =0D Access Classifieds =0D =0D =0D [marketi=] =0D For Sale =0D =0D =0D [marketi=] =0D Want to Buy=0D =0D =0D =0D =0D =0D =0D =0D =0D 100= 0's of Buyers, =0D 100's of Stocking Vendor= s, =0D 1.5 million lines of Inventory= , =0D Nearly 2 million part searches= a month =0D Contact us today=0D [2]support@powersourceonline.com =0D 888-265-3302 (U.S. = & Canada) =0D 1-450-677-7399 (International) = =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D Please do not reply to this email . If you have = any comments or questions regarding this message or the PowerSource Onlin= e service, please send an email to: [3]info@powersourceonline.com or visit us online: [4]www.powersourceonline.c= om =0D =0D This is an advertisement from PowerSource= Online. =0D If you no longer wish to receive news and special o= ffers from PowerSource Online, [5]unsubscribe . =0D PowerSource Online =0D 1010 de Sérigny Suite 800 - Longueuil, CANADA - J4K 5G7 =0D Tel: 1(888) 265-3302 - International: 001 (450) 677-7399 =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D [3D] =0D References Visible links 1. LYNXIMGMAP:file://localhost/tmp/3D"#Map" 2. 3D"mailto:support@powersourceonline.= 3. 3D"mailto:info@powersourceonl= 4. file://localhost/tmp/3D= 5. 3D"http://resp.powersourceonline.c=/ Hidden links: 6. 3D"http://re=/ 7. 3D"http://resp.powersourceonline.com/rspbp/= 8. 3D"http://resp.powersou=/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 14:22: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 6138316A403 for ; Wed, 13 Sep 2006 14:22:19 +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 0811D43D45 for ; Wed, 13 Sep 2006 14:22:18 +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 EE3A3B810 for ; Wed, 13 Sep 2006 10:22:17 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-4--538488844; protocol="application/pkcs7-signature" Message-Id: <6AF9F647-881A-448F-933C-743D295400B3@khera.org> From: Vivek Khera Date: Wed, 13 Sep 2006 10:22:17 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 14:22:19 -0000 --Apple-Mail-4--538488844 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 12, 2006, at 6:23 PM, hackmiester (Hunter Fuller) wrote: >> -STABLE is still a development branch without guarantee of a >> stable and working operating system. > > Hahahahaha... That's ironic... No, just misinterpretation of which attribute of the system to which the word "stable" applies. --Apple-Mail-4--538488844-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 14:24: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 7AF5716A4AB for ; Wed, 13 Sep 2006 14:24:04 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5B8A43D7C for ; Wed, 13 Sep 2006 14:23:47 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id D284F48A31; Wed, 13 Sep 2006 16:23:45 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 3593748A25; Wed, 13 Sep 2006 16:23:41 +0200 (CEST) Date: Wed, 13 Sep 2006 16:23:29 +0200 From: Pawel Jakub Dawidek To: Christian Laursen Message-ID: <20060913142329.GC70245@garage.freebsd.pl> References: <45066E19.2040405@kuehlbox.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HWvPVVuAAfuRc6SZ" Content-Disposition: inline In-Reply-To: X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 14:24:04 -0000 --HWvPVVuAAfuRc6SZ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 12, 2006 at 12:04:01PM +0200, Christian Laursen wrote: > Ivan Voras writes: >=20 > > - todays desktop drives can lie about writing data. SoftUpdates relies > > on some assumptions about when the data is physically written to > > media, and those are not always valid today >=20 > I think journaling relies on the same assumptions. Not gjournal, because it uses BIO_FLUSH I/O requests which flushes disk write cache when needed. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --HWvPVVuAAfuRc6SZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFCBRhForvXbEpPzQRAg+FAKCYMD1uZ4ppB0+SKQ83F1zac3Tl5wCfbGtu eWoun4Ozf4ajchr2V9ALZc8= =hEmD -----END PGP SIGNATURE----- --HWvPVVuAAfuRc6SZ-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 14:25: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 EF79A16A403 for ; Wed, 13 Sep 2006 14:25:49 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2FA843D5D for ; Wed, 13 Sep 2006 14:25:43 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id C425C2A56B; Wed, 13 Sep 2006 11:25:42 -0300 (BRT) Date: Wed, 13 Sep 2006 11:25:42 -0300 From: Marcelo Gardini do Amaral To: Pieter de Goeje Message-ID: <20060913142542.GM63300@registro.br> References: <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <200609121235.58619.pieter@degoeje.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609121235.58619.pieter@degoeje.nl> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 14:25:50 -0000 Hi Pieter, > My conclusion: there's definately something wrong with your setup. Maybe you > could try a different NIC to see if the performance issues are driver > related. I made a new test with another hardware because HP Blade Proliant doesn't allow me to put an additional NIC - there isn't any slot available. I posted the results at freebsd-net. If you want, I think you should try my test. It's pretty simple. -- Att., Marcelo Gardini From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 14:46:32 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 6B9BB16A407 for ; Wed, 13 Sep 2006 14:46:32 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CB1143D62 for ; Wed, 13 Sep 2006 14:46:24 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C0F7648A32; Wed, 13 Sep 2006 16:46:22 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4534645696 for ; Wed, 13 Sep 2006 16:46:17 +0200 (CEST) Date: Wed, 13 Sep 2006 16:46:05 +0200 From: Pawel Jakub Dawidek To: freebsd-stable@freebsd.org Message-ID: <20060913144605.GD70245@garage.freebsd.pl> References: <20060909173813.GA1388@FS.denninger.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WBsA/oQW3eTA3LlM" Content-Disposition: inline In-Reply-To: <20060909173813.GA1388@FS.denninger.net> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=ALL_TRUSTED,BAYES_00, MANY_EXCLAMATIONS,PLING_QUERY autolearn=ham version=3.0.4 Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 14:46:32 -0000 --WBsA/oQW3eTA3LlM Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 09, 2006 at 12:38:13PM -0500, Karl Denninger wrote: > This is not cool folks. I'm really sorry for the breakage. I'm trying to treat -STABLE very gently, unfortunately this time I made a mistake. The change was committed to HEAD at 9 August. The change fixed one bug, but introduced another, which I didn't expected. The change seemed to be trivial and I only tested that it fixes the bug I was tracking down, I haven't looked for regressions. After nearly one month in HEAD, I MFCed the change (at 4 September), because I wanted it to be released in -BETAs, so people can test it if they already didn't in HEAD and I was quite sure that after 1 month in HEAD the change is ok. I found the problem after 4 days (at 8 September) and backed the change out from the RELENG_6 branch. Once again, I'm really sorry, I'm trying not to make such surprises to the users, unfortunately it sometimes happens and you have to be ready that many changes goes to -STABLE branch just before release, so they can be tested by a wider audience. That's why we prepare -BETAs and not release -RELEASEs immediately. I'm not writting this to justify my mistake, just trying to show how you can avoid such bad days in the future. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --WBsA/oQW3eTA3LlM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFCBmtForvXbEpPzQRApyNAKCsH7ZBCG2VrRbNV6ZX2n5IVYgwTACfSbkY 8QxYDmM+JFKzIjOPYfXM+Ws= =brY8 -----END PGP SIGNATURE----- --WBsA/oQW3eTA3LlM-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 14:47: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 1029616A40F for ; Wed, 13 Sep 2006 14:47:12 +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 03CEA43D64 for ; Wed, 13 Sep 2006 14:47:02 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 6793 invoked from network); 14 Sep 2006 00:47:01 +1000 Received: from 124-168-25-250.dyn.iinet.net.au (HELO localhost) (124.168.25.250) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Sep 2006 00:47:01 +1000 Date: Thu, 14 Sep 2006 00:46:52 +1000 From: Norberto Meijome To: Henrik Brix Andersen Message-ID: <20060914004652.2dd01378@localhost> In-Reply-To: <20060913085412.GB14957@tirith.brixandersen.dk> References: <20060913114027.4c26e702@localhost> <20060913085412.GB14957@tirith.brixandersen.dk> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: ACPI resume problems in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 14:47:12 -0000 On Wed, 13 Sep 2006 10:54:12 +0200 Henrik Brix Andersen wrote: > > I have installed > > iwi-firmware-kmod-3.0_1 Intel PRO/Wireless 2200 Firmware Kernel Module > > You will need net/iwi-firmware (not net/iwi-firmware-kmod) for > 6.1-RELEASE. > > Regards, > Brix Hi Brix, yes, that's correct, i actually rebuilt my RELENG_6_1 kernel with if_iwi and firmware built in, then installed net/iwi-firmware and it's working just fine. Resume still works great with RELENG_6_1 - i assume broken in STABLE for me... will test 6_2 when out... or earlier if anyone could kindly point me to a date where I should test between RELENG_6_1 and current to test. thanks, B _________________________ {Beto|Norberto|Numard} Meijome "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea." RFC 1925 (quoting an unnamed source) I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 15:28: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 CDB2A16A407 for ; Wed, 13 Sep 2006 15:28:56 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABC943D46 for ; Wed, 13 Sep 2006 15:28:55 +0000 (GMT) (envelope-from bsd@kuehlbox.de) Received: (qmail 4663 invoked from network); 13 Sep 2006 15:28:53 -0000 Received: from unknown (HELO [192.168.16.84]) (bsd@kuehlbox.de@[213.182.157.102]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Sep 2006 15:28:53 -0000 Message-ID: <450823B1.2090809@kuehlbox.de> Date: Wed, 13 Sep 2006 17:28:49 +0200 From: Teufel User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Pawel Jakub Dawidek , freebsd-stable@FreeBSD.org References: <45066E19.2040405@kuehlbox.de> <20060913142329.GC70245@garage.freebsd.pl> In-Reply-To: <20060913142329.GC70245@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 15:28:56 -0000 Pawel Jakub Dawidek wrote: >>> - todays desktop drives can lie about writing data. SoftUpdates relies >>> on some assumptions about when the data is physically written to >>> media, and those are not always valid today >>> >> I think journaling relies on the same assumptions. >> > > Not gjournal, because it uses BIO_FLUSH I/O requests which flushes disk > write cache when needed so when the crash occur exactly when BIO_FLUSH is sent or while the cache is flushing, there is still no corruption possbile? If so, this would be an advantage over SU, as it does surely not use the new introduced BIO_FLUSH. In the other hand i've seen couple of other JFS that went corrupt for "no reason". I don't want to be paranoid, but i really want to be "sure" that the design is trustable. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 15:40: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 0C1E616A412 for ; Wed, 13 Sep 2006 15:40:00 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C20A043D4C for ; Wed, 13 Sep 2006 15:39:33 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6D5E346DA5; Wed, 13 Sep 2006 17:39:32 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4001F48A26; Wed, 13 Sep 2006 17:39:21 +0200 (CEST) Date: Wed, 13 Sep 2006 17:39:09 +0200 From: Pawel Jakub Dawidek To: Teufel Message-ID: <20060913153909.GE70245@garage.freebsd.pl> References: <45066E19.2040405@kuehlbox.de> <20060913142329.GC70245@garage.freebsd.pl> <450823B1.2090809@kuehlbox.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="65ImJOski3p8EhYV" Content-Disposition: inline In-Reply-To: <450823B1.2090809@kuehlbox.de> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 15:40:00 -0000 --65ImJOski3p8EhYV Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 05:28:49PM +0200, Teufel wrote: > Pawel Jakub Dawidek wrote: > >>>- todays desktop drives can lie about writing data. SoftUpdates relies > >>>on some assumptions about when the data is physically written to > >>>media, and those are not always valid today > >>> =20 > >>I think journaling relies on the same assumptions. > >> =20 > > > >Not gjournal, because it uses BIO_FLUSH I/O requests which flushes disk > >write cache when needed > so when the crash occur exactly when BIO_FLUSH is sent or while the > cache is flushing, there is still no corruption possbile? [...] That's right. One BIO_FLUSH is send to ensure the data are safely stored, and another one is send when metadata is updated to point at the last consistent journal. > [...] If so, this would be an advantage over SU, as=20 > it does surely not use the new introduced BIO_FLUSH. [...] Soft-updates doesn't handle disk write caches at all. > [...] In the other hand i've seen couple of other JFS that went corrupt f= or "no reason". I don't want to be paranoid, but i=20 > really want to be "sure" that the design is trustable. Of course a bug in file system (or gjournal) implementation is still possible and can lead to file system corruption, but such a bug can still corrupt file system in the way it will not be fixable by fsck. =46rom what I saw, file systems with journaling still enforce fsck every X reboots or on the next reboot after Y days of uptime, whatever comes first. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --65ImJOski3p8EhYV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFCCYdForvXbEpPzQRAhWdAJ9+Ow8IbGTYTCeDdGeqGBw4xXGLcgCbBhmu oSPG3J7sxUJRTZSi2qF58PE= =cTBj -----END PGP SIGNATURE----- --65ImJOski3p8EhYV-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 17:15: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 D026716A4B3 for ; Wed, 13 Sep 2006 17:15:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAFFD43DAC for ; Wed, 13 Sep 2006 17:15:23 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uxoxqv@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8DHFGnS090765; Wed, 13 Sep 2006 19:15:22 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8DHFGKK090764; Wed, 13 Sep 2006 19:15:16 +0200 (CEST) (envelope-from olli) Date: Wed, 13 Sep 2006 19:15:16 +0200 (CEST) Message-Id: <200609131715.k8DHFGKK090764@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, bsd@kuehlbox.de In-Reply-To: <450823B1.2090809@kuehlbox.de> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 13 Sep 2006 19:15:22 +0200 (CEST) Cc: Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, bsd@kuehlbox.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 17:15:40 -0000 Teufel wrote: > so when the crash occur exactly when BIO_FLUSH is sent or while the > cache is flushing, there is still no corruption possbile? A small additional note ... If there's a _hardware_ crash (e.g. power outage) which causes a track write of the HDD to be interrupted, you will get corruption. There is *no* file system that protects you from such damage, except probably Sun's ZFS in a mirror configuration (because of its COW, checksumming and self-healing features). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Perl is worse than Python because people wanted it worse. -- Larry Wall From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 17:22: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 3709116A403; Wed, 13 Sep 2006 17:22:55 +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 0083343D6D; Wed, 13 Sep 2006 17:22:53 +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 E95A546BFF; Wed, 13 Sep 2006 13:22:46 -0400 (EDT) Date: Wed, 13 Sep 2006 18:22:46 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marcelo Gardini do Amaral In-Reply-To: <20060911195521.GD63300@registro.br> Message-ID: <20060913182019.R50147@fledge.watson.org> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 17:22:55 -0000 On Mon, 11 Sep 2006, Marcelo Gardini do Amaral wrote: > I would like to discuss a little bit more about UDP performance. I've made > some tests and the results may have some value here. > > In this test is easy to see that there is something different in the FreeBSD > 6 branch. > > I made a benchmark with bind 9.3.2 (without threads support) and nsd 3.0.1 > (1 server forked) on a HP Proliant Dual AMD Opteron 2.4GHz among FreeBSD > 4.11, 6.1 and Linux kernel 2.6.15, all of them for i386 systems. I used this > simple zone file: Are you able to boot a 7.x kernel on this box? An as yet un-MFC'd optimization to the UDP send path is present in the 7.x kernel, suggested by ISC, which significantly improves threaded BIND9 performance. I've not benchmarked unthreaded BIND9 with the change. If you want to test specifically the before/after case for that change, you can find the reference to sosend_dgram in src/sys/netinet/udp_usrreq.c and swap it to sosend, which restores the old behavior. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 17: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 2C58A16A4A0; Wed, 13 Sep 2006 17:27:19 +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 1577D43D8E; Wed, 13 Sep 2006 17:27:12 +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 0246646C1D; Wed, 13 Sep 2006 13:27:11 -0400 (EDT) Date: Wed, 13 Sep 2006 18:27:11 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marcelo Gardini do Amaral In-Reply-To: <20060913182019.R50147@fledge.watson.org> Message-ID: <20060913182457.W50147@fledge.watson.org> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 17:27:19 -0000 On Wed, 13 Sep 2006, Robert Watson wrote: > On Mon, 11 Sep 2006, Marcelo Gardini do Amaral wrote: > >> I would like to discuss a little bit more about UDP performance. I've made >> some tests and the results may have some value here. >> >> In this test is easy to see that there is something different in the >> FreeBSD 6 branch. >> >> I made a benchmark with bind 9.3.2 (without threads support) and nsd 3.0.1 >> (1 server forked) on a HP Proliant Dual AMD Opteron 2.4GHz among FreeBSD >> 4.11, 6.1 and Linux kernel 2.6.15, all of them for i386 systems. I used >> this simple zone file: > > Are you able to boot a 7.x kernel on this box? An as yet un-MFC'd > optimization to the UDP send path is present in the 7.x kernel, suggested by > ISC, which significantly improves threaded BIND9 performance. I've not > benchmarked unthreaded BIND9 with the change. If you want to test > specifically the before/after case for that change, you can find the > reference to sosend_dgram in src/sys/netinet/udp_usrreq.c and swap it to > sosend, which restores the old behavior. The other common optimization advice that you may already have received is to check which time counter FreeBSD has selected. Right now, 6.x/7.x err on the side of accurate over fast. There's been quite a bit of debate about this approach, and it's useful to investigate the issue. You can view and set the current choice by looking at the sysctl kern.timecounter.hardware, and you can see the choices on your hardware by looking at kern.timecounter.choice. Typically, TSC is the fastest, but may suffer from drift as the CPU changes speed (as a result of temperature, power saving, etc). Set it to TSC if it's not already TSC, and see what the effect is. As many event libraries read time stamps frequently to set up sleeping in user space, it can have a substantial performance impact. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 17:49: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 9BCA916A407; Wed, 13 Sep 2006 17:49:46 +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 2D11B43D70; Wed, 13 Sep 2006 17:49:45 +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 k8DHni6U039282; Wed, 13 Sep 2006 13:49:44 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id k8DHnihK057510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Sep 2006 13:49:44 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <7.0.1.0.0.20060913134509.159096f0@sentex.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 13 Sep 2006 13:49:44 -0400 To: Robert Watson From: Mike Tancsa In-Reply-To: <20060913182457.W50147@fledge.watson.org> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 17:49:46 -0000 At 01:27 PM 9/13/2006, Robert Watson wrote: >The other common optimization advice that you may already have >received is to check which time counter FreeBSD has selected. Right >now, 6.x/7.x err on the side of accurate over fast. There's been >quite a bit of debate about this approach, and it's useful to >investigate the issue. You can view and set the current choice by >looking at the sysctl kern.timecounter.hardware, and you can see the >choices on your hardware by looking at kern.timecounter.choice. >Typically, TSC is the fastest, but may suffer from drift as the CPU changes Hi, How safe is TSC on SMP systems on RELENG_6 ? Do you still have to boot with kern.timecounter.smp_tsc="1" in /boot/loader.conf ? I was able to set it to TSC on my SMP box # sysctl kern.timecounter kern.timecounter.tick: 1 kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-1000000) kern.timecounter.hardware: TSC kern.timecounter.nsetclock: 4 kern.timecounter.ngetmicrotime: 1710689523 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetmicrouptime: 417696361 kern.timecounter.ngetnanouptime: 6622371 kern.timecounter.ngetbinuptime: 17943777 kern.timecounter.nmicrotime: 2454574760 kern.timecounter.nnanotime: 1315721638 kern.timecounter.nbintime: 3770262461 kern.timecounter.nmicrouptime: 407340 kern.timecounter.nnanouptime: 1397760 kern.timecounter.nbinuptime: 3787035688 kern.timecounter.stepwarnings: 0 kern.timecounter.smp_tsc: 0 But the console fills up with Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379728 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379758 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379789 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379819 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379849 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379879 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379910 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379940 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335379970 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380002 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380032 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380065 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380096 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380126 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380156 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380186 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380216 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380247 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380277 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380307 usec for pid 66442 (clamd) Sep 13 13:47:57 pumice1 kernel: calcru: runtime went backwards from 6336196518 usec to 6335380337 usec for pid 66442 (clamd) So I set things back to kern.timecounter.hardware: ACPI-fast ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 18:15: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 BBF8E16A415; Wed, 13 Sep 2006 18:15:09 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B494643D4C; Wed, 13 Sep 2006 18:15:08 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8DIF6jc090495; Wed, 13 Sep 2006 11:15:07 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8DIF6HS090494; Wed, 13 Sep 2006 11:15:06 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 11:15:04 -0700 From: Gary Kline To: Pawel Jakub Dawidek Message-ID: <20060913181504.GB90378@thought.org> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060913144605.GD70245@garage.freebsd.pl> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 18:15:09 -0000 On Wed, Sep 13, 2006 at 04:46:05PM +0200, Pawel Jakub Dawidek wrote: > On Sat, Sep 09, 2006 at 12:38:13PM -0500, Karl Denninger wrote: > > This is not cool folks. > > I'm really sorry for the breakage. I'm trying to treat -STABLE very > gently, unfortunately this time I made a mistake. > > The change was committed to HEAD at 9 August. The change fixed one bug, > but introduced another, which I didn't expected. The change seemed to be > trivial and I only tested that it fixes the bug I was tracking down, I > haven't looked for regressions. > Well, after this lengthy discussion, I've switched to -RELEASE. -STABLE just ain't... We all realize that none of us would put out a buggy release--not even -CURRENT. But let me ask the next obvious question. How difficult would it be to build a regression test, or suite of tests? Obviously, this could be done over months -> years. (In my last lifetime as a hacker I was in the kernel test group [a BSD-4.4 based release on new architecture]. ) It's a bit hard to believe that with all the genius in this effort, that no regression testing is done. gary -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 18:22: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 EF21716A412 for ; Wed, 13 Sep 2006 18:22:08 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A963F43D6A for ; Wed, 13 Sep 2006 18:22:04 +0000 (GMT) (envelope-from bsd@kuehlbox.de) Received: (qmail 8170 invoked from network); 13 Sep 2006 18:22:03 -0000 Received: from unknown (HELO [172.16.21.119]) (bsd@kuehlbox.de@[82.135.94.49]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 13 Sep 2006 18:22:03 -0000 Message-ID: <45084C3F.1030600@kuehlbox.de> Date: Wed, 13 Sep 2006 20:21:51 +0200 From: Teufel User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: <45066E19.2040405@kuehlbox.de> <20060913142329.GC70245@garage.freebsd.pl> <450823B1.2090809@kuehlbox.de> <20060913153909.GE70245@garage.freebsd.pl> In-Reply-To: <20060913153909.GE70245@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 18:22:09 -0000 Pawel Jakub Dawidek wrote: >> [...] If so, this would be an advantage over SU, as >> it does surely not use the new introduced BIO_FLUSH. [...] >> > Soft-updates doesn't handle disk write caches at all. > you're totaly right. I was refering to the assumption of SU that the drive cache will not "lie" about its handling. >> [...] In the other hand i've seen couple of other JFS that went corrupt for "no reason". I don't want to be paranoid, but i >> really want to be "sure" that the design is trustable. >> > > Of course a bug in file system (or gjournal) implementation is still > possible and can lead to file system corruption, but such a bug can > still corrupt file system in the way it will not be fixable by fsck. > sooner or later bugs should be fixed. At least i will do some terrible test to gjournal in the next days. So in case expect some feedback. > From what I saw, file systems with journaling still enforce fsck every X > reboots or on the next reboot after Y days of uptime, whatever comes first. > That is also my experience. So hopefully gjournal will be an exception for this in the future :-) Thanks for clarifying and the great job. Stephan From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 18:24: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 C491D16A49E for ; Wed, 13 Sep 2006 18:24:46 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 031AC43D99 for ; Wed, 13 Sep 2006 18:24:34 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout13/MantshX 4.0) with ESMTP id k8DIOYwX024135; Wed, 13 Sep 2006 11:24:34 -0700 (PDT) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id k8DIOW3q005237; Wed, 13 Sep 2006 11:24:33 -0700 (PDT) In-Reply-To: <20060913181504.GB90378@thought.org> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> <20060913181504.GB90378@thought.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <08081DAA-E496-452A-AC08-FEC3221869BF@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Wed, 13 Sep 2006 11:24:31 -0700 To: Gary Kline X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAQAAA+k= X-Language-Identified: TRUE Cc: freebsd-stable Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 18:24:46 -0000 On Sep 13, 2006, at 11:15 AM, Gary Kline wrote: > Well, after this lengthy discussion, I've switched to -RELEASE. > -STABLE just ain't... We all realize that none of us would > put out a buggy release--not even -CURRENT. But let me ask > the next obvious question. How difficult would it be to > build a regression test, or suite of tests? There are already a number of regression tests under /usr/src/tools/ regression; Peter Holm has additional stress testing tools at http://www.holm.cc/ stress/ -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 18:59: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 65AC416A407 for ; Wed, 13 Sep 2006 18:59:30 +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 2B38043D88 for ; Wed, 13 Sep 2006 18:59:15 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 50FF722DC01; Wed, 13 Sep 2006 20:59:14 +0200 (CEST) Date: Wed, 13 Sep 2006 20:59:14 +0200 To: freebsd-stable@freebsd.org Message-ID: <20060913185914.GB15445@leia.lambermont.dyndns.org> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> <20060913181504.GB90378@thought.org> <08081DAA-E496-452A-AC08-FEC3221869BF@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <08081DAA-E496-452A-AC08-FEC3221869BF@mac.com> User-Agent: Mutt/1.4.2.2i From: hans@lambermont.dyndns.org (Hans Lambermont) Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 18:59:30 -0000 Chuck Swiger wrote: > On Sep 13, 2006, at 11:15 AM, Gary Kline wrote: ... >> How difficult would it be to build a regression test, or suite >> of tests? > > There are already a number of regression tests under /usr/src/tools/ > regression; Are they part of an (automated) tinderbox system somewhere ? regards, Hans Lambermont From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 19:51: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 5AAD716A403; Wed, 13 Sep 2006 19:51:15 +0000 (UTC) (envelope-from ingom-list@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0061743D45; Wed, 13 Sep 2006 19:51:14 +0000 (GMT) (envelope-from ingom-list@freenet.de) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.62) (envelope-from ) id 1GNalN-0003rm-RV; Wed, 13 Sep 2006 21:51:13 +0200 Received: from p54b18990.dip0.t-ipconnect.de ([84.177.137.144] helo=medion-8800) by mx1.freenet.de with esmtpa (ID ingom-list@freenet.de) (Exim 4.62 #12) id 1GNalN-0001rG-JH; Wed, 13 Sep 2006 21:51:13 +0200 Date: Wed, 13 Sep 2006 21:51:09 +0200 To: freebsd-performance@freebsd.org From: Ingo Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 Message-ID: User-Agent: Opera Mail/9.01 (Win32) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: network performance problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2006 19:51:15 -0000 Hello, I`ve some problems with the network performance on my Soekris NET 4801. (Freebsd 6.1 release-p3) When I start "netio" on the soekris and do a "netio localhost", I get about 8.4 MB/sec, and when I start with "netio 192.168.0.11"(itÂŽs localhost address) I get only ~2.3 MB/sec. ThatÂŽs what top says when I do: localhost CPU states: 2.3% user, 0.0% nice, 72.5% system, 25.2% interrupt, 0.0% idle 192.168.0.11 CPU states: 1.2% user, 0.0% nice, 46.3% system, 52.5% interrupt, 0.0% idle As you can see, the interrupt load is more than doubled when I use the Ip address, and IÂŽve no idea why. Here are some other throughput results of the soekris: openbsd# ftp 192.16.8.0.20 2.0 MB/sec openbsd# iperf localhost 1.4 Mbit/sec openbsd# iperf 192.168.0.11(itÂŽs localhost address) 1.4 Mbit/sec openbsd# netperf localhost 70MB/sec openbsd# netperf 192.168.0.11(itÂŽs localhost address) 70MB/sec freebsd# ftp 192.168.0.20 2.3 MB/sec Freebsd# iperf localhost 45 Mbit/sec Freebsd# iperf 192.168.0.11 (itÂŽs localhost address) 19 Mbit/sec Freebsd# netperf localhost 67 Mbit/sec Freebsd# netperf 192.168.0.11 (itÂŽs localhost address) 19 Mbit/sec What causes the difference between localhost and the ip address on Freebsd? On Openbsd there is no diffenerce at all. Greetings -- Erstellt mit Operas revolutionÀrem E-Mail-Modul: http://www.opera.com/mail/ From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 20:26: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 7269116A494 for ; Wed, 13 Sep 2006 20:26:31 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 807BA43D73 for ; Wed, 13 Sep 2006 20:26:23 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 802BD48A2B; Wed, 13 Sep 2006 22:26:22 +0200 (CEST) Received: from localhost (dlx163.neoplus.adsl.tpnet.pl [83.24.53.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id CB2CE48A26; Wed, 13 Sep 2006 22:26:16 +0200 (CEST) Date: Wed, 13 Sep 2006 22:26:03 +0200 From: Pawel Jakub Dawidek To: Gary Kline Message-ID: <20060913202603.GA72187@garage.freebsd.pl> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> <20060913181504.GB90378@thought.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20060913181504.GB90378@thought.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.2 required=3.0 tests=BAYES_00,MANY_EXCLAMATIONS, PLING_QUERY,RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 20:26:31 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 11:15:04AM -0700, Gary Kline wrote: > On Wed, Sep 13, 2006 at 04:46:05PM +0200, Pawel Jakub Dawidek wrote: > > On Sat, Sep 09, 2006 at 12:38:13PM -0500, Karl Denninger wrote: > > > This is not cool folks. > >=20 > > I'm really sorry for the breakage. I'm trying to treat -STABLE very > > gently, unfortunately this time I made a mistake. > >=20 > > The change was committed to HEAD at 9 August. The change fixed one bug, > > but introduced another, which I didn't expected. The change seemed to be > > trivial and I only tested that it fixes the bug I was tracking down, I > > haven't looked for regressions. > >=20 > =09 > Well, after this lengthy discussion, I've switched to -RELEASE. > -STABLE just ain't... We all realize that none of us would=20 > put out a buggy release--not even -CURRENT. But let me ask > the next obvious question. How difficult would it be to > build a regression test, or suite of tests? Obviously, this > could be done over months -> years. (In my last lifetime > as a hacker I was in the kernel test group [a BSD-4.4 based=20 > release on new architecture]. ) It's a bit hard to believe=20 > that with all the genius in this effort, that no regression > testing is done. I'm trying to implement regression tests to the code I add. You can find them in /usr/src/tools/regression/: geom_concat 2 files, 2 tests geom_eli 15 files, 5818 tests geom_gate 3 files, 6 tests geom_mirror 7 files, 27 tests geom_nop 2 files, 2 tests geom_raid3 12 files, 13 tests geom_shsec 2 files, 6 tests geom_stripe 2 files, 2 tests ipsec 1 file, 306 tests redzone9 1 file, 6 tests usr.bin/pkill 27 files, 49 tests As I said already, I mistakenly thought the change was trivial and the only thing I tested was if it fixes a bug I was tracking down back then. We dicuss from time to time that we should have service simlar to tinderbox, which will run regression tests regularly and report regressions to the mailing lists - the more we automate the smaller chance for a human mistake like mine. Unfortunately this is not yet done. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFCGlbForvXbEpPzQRAqh/AJ9Oa4wxGgrZArBYDFXKn9kYAlTX7ACgmF0j Vt7lhluRoNiwClItmRZhbEk= =8Tx0 -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 21: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 A442716A415; Wed, 13 Sep 2006 21:24:41 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B1043D49; Wed, 13 Sep 2006 21:24:39 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8DLOdH8091122; Wed, 13 Sep 2006 14:24:39 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8DLOceP091121; Wed, 13 Sep 2006 14:24:38 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 14:24:38 -0700 From: Gary Kline To: Pawel Jakub Dawidek Message-ID: <20060913212438.GA90960@thought.org> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> <20060913181504.GB90378@thought.org> <20060913202603.GA72187@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060913202603.GA72187@garage.freebsd.pl> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: Gary Kline , freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Wed, 13 Sep 2006 21:24:41 -0000 On Wed, Sep 13, 2006 at 10:26:03PM +0200, Pawel Jakub Dawidek wrote: > On Wed, Sep 13, 2006 at 11:15:04AM -0700, Gary Kline wrote: > > On Wed, Sep 13, 2006 at 04:46:05PM +0200, Pawel Jakub Dawidek wrote: > > > On Sat, Sep 09, 2006 at 12:38:13PM -0500, Karl Denninger wrote: > > > > This is not cool folks. > > > > > > I'm really sorry for the breakage. I'm trying to treat -STABLE very > > > gently, unfortunately this time I made a mistake. > > > > > > The change was committed to HEAD at 9 August. The change fixed one bug, > > > but introduced another, which I didn't expected. The change seemed to be > > > trivial and I only tested that it fixes the bug I was tracking down, I > > > haven't looked for regressions. > > > > > > > Well, after this lengthy discussion, I've switched to -RELEASE. > > -STABLE just ain't... We all realize that none of us would > > put out a buggy release--not even -CURRENT. But let me ask > > the next obvious question. How difficult would it be to > > build a regression test, or suite of tests? Obviously, this > > could be done over months -> years. (In my last lifetime > > as a hacker I was in the kernel test group [a BSD-4.4 based > > release on new architecture]. ) It's a bit hard to believe > > that with all the genius in this effort, that no regression > > testing is done. > > I'm trying to implement regression tests to the code I add. You can find > them in /usr/src/tools/regression/: > > geom_concat 2 files, 2 tests > geom_eli 15 files, 5818 tests > geom_gate 3 files, 6 tests > geom_mirror 7 files, 27 tests > geom_nop 2 files, 2 tests > geom_raid3 12 files, 13 tests > geom_shsec 2 files, 6 tests > geom_stripe 2 files, 2 tests > ipsec 1 file, 306 tests > redzone9 1 file, 6 tests > usr.bin/pkill 27 files, 49 tests > > As I said already, I mistakenly thought the change was trivial and the > only thing I tested was if it fixes a bug I was tracking down back then. > > We dicuss from time to time that we should have service simlar to > tinderbox, which will run regression tests regularly and report > regressions to the mailing lists - the more we automate the smaller > chance for a human mistake like mine. Unfortunately this is not yet > done. You're right in saying that the more automation, the more stability. Hats off for all this good work (from somebody who has been there before:).... This is the kind of thing tht needs to be done (i) to catch bugs before they are committed, and (ii) to make BSD all the more trustworthy and bullet-proof. HAving run FBSD since 2.0.5 and only *one* "fatal trap" is pretty hard to beat. gary > > -- > Pawel Jakub Dawidek http://www.wheel.pl > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 22:41:47 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 4CA7216A407; Wed, 13 Sep 2006 22:41:47 +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 A8B1243D45; Wed, 13 Sep 2006 22:41:44 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp119-42.lns1.adl2.internode.on.net [121.44.119.42]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k8DMfKA1051753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Sep 2006 08:11:21 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 14 Sep 2006 08:11:01 +0930 User-Agent: KMail/1.9.3 References: <45066E19.2040405@kuehlbox.de> <20060913142329.GC70245@garage.freebsd.pl> In-Reply-To: <20060913142329.GC70245@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2444454.qAASHZU8ZZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609140811.19245.doconnor@gsoft.com.au> X-Spam-Score: -2.312 () BAYES_00 X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Pawel Jakub Dawidek , Christian Laursen Subject: Re: gjournal and Softupdates X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 22:41:47 -0000 --nextPart2444454.qAASHZU8ZZ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 13 September 2006 23:53, Pawel Jakub Dawidek wrote: > On Tue, Sep 12, 2006 at 12:04:01PM +0200, Christian Laursen wrote: > > Ivan Voras writes: > > > - todays desktop drives can lie about writing data. SoftUpdates relies > > > on some assumptions about when the data is physically written to > > > media, and those are not always valid today > > > > I think journaling relies on the same assumptions. > > Not gjournal, because it uses BIO_FLUSH I/O requests which flushes disk > write cache when needed. It should be possible to use this same mechanism for SU too, right? Of course that may result in really poor write performance :) =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 --nextPart2444454.qAASHZU8ZZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBFCIkP5ZPcIHs/zowRAoCJAKCqpS5dZCqGj2WF1ruQulAn1cavJACfcu/q ll+yj9RFjUVOKXKQhdn4Jr4= =yFqA -----END PGP SIGNATURE----- --nextPart2444454.qAASHZU8ZZ-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 13 23:49: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 4F56416A47E for ; Wed, 13 Sep 2006 23:49:43 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D56943D46 for ; Wed, 13 Sep 2006 23:49:42 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8DNnZqQ092125; Wed, 13 Sep 2006 16:49:35 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8DNnY37092124; Wed, 13 Sep 2006 16:49:34 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 16:49:34 -0700 From: Gary Kline To: Stefan Lambrev Message-ID: <20060913234934.GA92067@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4507CC9B.60704@sun-fish.com> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 13 Sep 2006 23:49:43 -0000 On Wed, Sep 13, 2006 at 12:17:15PM +0300, Stefan Lambrev wrote: > Hello, > > Oliver Fromme wrote: > >Marc G. Fournier wrote: > > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > > building kernel/world? I know awhile back it wasn't recommended to go > > > above -O2, for instance, but suspect that has changed ... ? > > > >The best optimization is probably to not override the > >defaults at all, because they're already pretty optimal. > >In fact, by overriding the defaults there's a good chance > >to make things worse. :-) > > > >The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > >Anything above -O2 isn't supported, and using -O2 without > >-fno-strict-aliasing also isn't supported (and will create > >broken code for some programs). A common mistake is to > >specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > >That'll shot you in the foot sooner or later. > > > >Best regards > > Oliver > > > > > May be default flags have to be set here: > /usr/src/share/examples/etc/make.conf ? > I'm asking because in this file I read: > > # CFLAGS controls the compiler settings used when compiling C code. > # Note that optimization settings other than -O and -O2 are not recommended > # or supported for compiling the world or the kernel - please revert any > # nonstandard optimization settings to "-O" or -O2 before submitting bug > # reports without patches to the developers. > # > #CFLAGS= -O -pipe > > May be "-fno-strict-aliasing" have to be added here then ? > A couple of things. Will having gcc unroll loops have any negative consequences? (I can't imagine how:: but better informed than to have something crash inexplicability.) With 6.X safe at -O2 and with -funroll-loops, that should be a slight gain, right? (It also will make an upgrade from 5.5 to 6.[12] that much more rational.) [Dumb] questions:: first, what does the compiler do with "-fno-strict-aliasing"? And is there any guess, any SWAG even, on when FreeBSD will safe with -O3?? thanks, people, gary > -- > Best Wishes, > Stefan Lambrev > ICQ# 24134177 > > _______________________________________________ > 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" -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 00: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 49E4916A403 for ; Thu, 14 Sep 2006 00:02:44 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id F33BF43D46 for ; Thu, 14 Sep 2006 00:02:43 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 5F585E6084 for ; Thu, 14 Sep 2006 00:02:43 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.8/8.13.6) with ESMTP id k8E02b11073990; Thu, 14 Sep 2006 10:02:38 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200609140002.k8E02b11073990@drugs.dv.isc.org> To: Gary Kline From: Mark Andrews In-reply-to: Your message of "Wed, 13 Sep 2006 16:49:34 MST." <20060913234934.GA92067@thought.org> Date: Thu, 14 Sep 2006 10:02:37 +1000 Sender: Mark_Andrews@isc.org Cc: freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 00:02:44 -0000 > On Wed, Sep 13, 2006 at 12:17:15PM +0300, Stefan Lambrev wrote: > > Hello, > > > > Oliver Fromme wrote: > > >Marc G. Fournier wrote: > > > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > > > > building kernel/world? I know awhile back it wasn't recommended to go > > > > above -O2, for instance, but suspect that has changed ... ? > > > > > >The best optimization is probably to not override the > > >defaults at all, because they're already pretty optimal. > > >In fact, by overriding the defaults there's a good chance > > >to make things worse. :-) > > > > > >The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > >Anything above -O2 isn't supported, and using -O2 without > > >-fno-strict-aliasing also isn't supported (and will create > > >broken code for some programs). A common mistake is to > > >specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > > >That'll shot you in the foot sooner or later. > > > > > >Best regards > > > Oliver > > > > > > > > May be default flags have to be set here: > > /usr/src/share/examples/etc/make.conf ? > > I'm asking because in this file I read: > > > > # CFLAGS controls the compiler settings used when compiling C code. > > # Note that optimization settings other than -O and -O2 are not recommended > > # or supported for compiling the world or the kernel - please revert any > > # nonstandard optimization settings to "-O" or -O2 before submitting bug > > # reports without patches to the developers. > > # > > #CFLAGS= -O -pipe > > > > May be "-fno-strict-aliasing" have to be added here then ? > > > > > A couple of things. Will having gcc unroll loops have any > negative consequences? (I can't imagine how:: but better > informed than to have something crash inexplicability.) > With 6.X safe at -O2 and with -funroll-loops, that should be > a slight gain, right? (It also will make an upgrade from 5.5 > to 6.[12] that much more rational.) > > [Dumb] questions:: first, what does the compiler do with > "-fno-strict-aliasing"? And is there any guess, any SWAG even, > on when FreeBSD will safe with -O3?? Lots of code is not strict-aliasing safe. Gcc itself can't determine all the cases which a construct is not strict-aliasing safe so even after getting rid of all the warnings gcc produces you can't be sure your code is strict-aliasing safe. Think of -fstrict-aliasing as optimisation without a saftey net. If your code doesn't cast pointers you should be safe otherwise you need to be really, really, really careful when you turn this on. > thanks, people, > > gary > > > -- > > Best Wishes, > > Stefan Lambrev > > ICQ# 24134177 > > > > _______________________________________________ > > 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" > > -- > Gary Kline kline@thought.org www.thought.org Public service Unix > > _______________________________________________ > 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" -- ISC Training! October 16-20, 2006, in the San Francisco Bay Area, covering topics from DNS to DHCP. Email training@isc.org. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 00:07: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 74B6716A407 for ; Thu, 14 Sep 2006 00:07:37 +0000 (UTC) (envelope-from anthony.maher@uts.edu.au) Received: from dib.itd.uts.edu.au (dib.itd.uts.edu.au [138.25.22.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 034EE43D45 for ; Thu, 14 Sep 2006 00:07:36 +0000 (GMT) (envelope-from anthony.maher@uts.edu.au) Received: by dib.itd.uts.edu.au (Postfix, from userid 1011) id 3B259DFDC3; Thu, 14 Sep 2006 10:03:28 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by dib.itd.uts.edu.au (Postfix/Intermediary) with ESMTP id 2C1FADFE5A; Thu, 14 Sep 2006 10:03:28 +1000 (EST) Received: from vimes (vimes.itd.uts.edu.au [138.25.243.34]) by dib.itd.uts.edu.au (Postfix/Ingress) with ESMTP id 19801DFDC3; Thu, 14 Sep 2006 10:03:28 +1000 (EST) Received: from [138.25.81.112] by postoffice.uts.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTPS id <0J5K0031X30N0360@postoffice.uts.edu.au>; Thu, 14 Sep 2006 10:07:35 +1000 (EST) Date: Thu, 14 Sep 2006 10:07:35 +1000 From: Tony Maher In-reply-to: <20060913234934.GA92067@thought.org> To: Gary Kline Message-id: <45089D47.6070005@uts.edu.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Enigmail-Version: 0.93.0.0 References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060511 Cc: freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 00:07:37 -0000 Gary Kline wrote: > > > A couple of things. Will having gcc unroll loops have any > negative consequences? (I can't imagine how:: but better > informed than to have something crash inexplicability.) > With 6.X safe at -O2 and with -funroll-loops, that should be > a slight gain, right? (It also will make an upgrade from 5.5 > to 6.[12] that much more rational.) -funroll-loops affect loader see http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028145.html -- tonym From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 00:25: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 DBE3816A40F for ; Thu, 14 Sep 2006 00:25:41 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76C7543D6A for ; Thu, 14 Sep 2006 00:25:38 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout16/MantshX 4.0) with ESMTP id k8E0PcH7006020; Wed, 13 Sep 2006 17:25:38 -0700 (PDT) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id k8E0PahO023606; Wed, 13 Sep 2006 17:25:37 -0700 (PDT) In-Reply-To: <20060913234934.GA92067@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0B8BF03E-8F4A-4279-850B-2EA7FF5E1B89@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Wed, 13 Sep 2006 17:25:35 -0700 To: Gary Kline X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAQAAA+k= X-Language-Identified: TRUE Cc: freebsd-stable Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 00:25:41 -0000 On Sep 13, 2006, at 4:49 PM, Gary Kline wrote: > A couple of things. Will having gcc unroll loops have any > negative consequences? Yes, it certainly can have negative consequences. The primary intent of using that option is to change a loop from executing the test or control block for each iteration that the body is executed, to executing the loop body several times and checking the test or control block less often. The issue is that there is often additional setup or post-loop fixups to ensure that the loop body actually is executed the right number of times, which makes the generated binary code much larger. This can mean that the loop no longer fits within the L1 instruction cache, which will usually result in the program going slower, rather than faster. Using the option will always increase the size of compiled executables. > (I can't imagine how:: but better > informed than to have something crash inexplicability.) > With 6.X safe at -O2 and with -funroll-loops, that should be > a slight gain, right? -funroll-loops is as likely to decrease performance for a particular program as it is to help. One particular caveat with using that option is that the increase in program size apparently causes the initial bootloader code to no longer fit within a single sector, making the system unbootable. > [Dumb] questions:: first, what does the compiler do with > "-fno-strict-aliasing"? It prevents the compiler from generating buggy output from source code which uses type-punning. http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html A safe optimizer must assume that an arbitrary assignment via a pointer dereference can change any value in memory, which means that you have to spill and reload any data being cached in CPU registers around the use of the pointer, except for const's, variables declared as "register", and possibly function arguments being passed via registers and not on the stack (cf "register windows" on the SPARC hardware, or HP/PA's calling conventions). -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 00:27: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 219F316A403 for ; Thu, 14 Sep 2006 00:27:42 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out3.tiscali.nl (smtp-out3.tiscali.nl [195.241.79.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F7C043D82 for ; Thu, 14 Sep 2006 00:27:32 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out3.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1GNf4l-0002Vz-Oq for ; Thu, 14 Sep 2006 02:27:31 +0200 Received: (qmail 10984 invoked from network); 14 Sep 2006 00:27:30 -0000 Received: from localhost.thuis.klop.ws (HELO guido.klop.ws) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 14 Sep 2006 00:27:30 -0000 Date: Thu, 14 Sep 2006 02:27:29 +0200 To: freebsd-stable@freebsd.org From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: User-Agent: Opera Mail/9.01 (FreeBSD) Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 00:27:42 -0000 On Tue, 05 Sep 2006 23:52:05 +0200, Ronald Klop wrote: > Hello, > > I get these errors a lot. > > Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting > Sep 5 11:55:12 ronald kernel: em0: link state changed to DOWN > Sep 5 11:55:14 ronald kernel: em0: link state changed to UP > Sep 5 12:00:37 ronald kernel: em0: watchdog timeout -- resetting > Sep 5 12:00:37 ronald kernel: em0: link state changed to DOWN > Sep 5 12:00:39 ronald kernel: em0: link state changed to UP > > I tried turning off rxcsum/txcsum and set these sysctl's. > dev.em.0.rx_int_delay: 0 > dev.em.0.tx_int_delay: 0 (default 66) > But the error is still there. > Searching the internet and the list provides more of the same problems, > but I didn't find an answer. > > My dmesg is attached. > > Is there any info I need to provide to debug this or can I try patches? Them manual page em(4) mentions trying another cable when the watchdog timeout happens, so I tried that. But it didn't help. Is there anything I can test to (help) debug this? It happens a lot when my machine is under load. (100% CPU) Is it possible that it happens since I upgraded the memory from 1GB to 2 GB? (dmesg was attached to my previous mail, but I can provide it again.) Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 01:00: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 B34A416A403 for ; Thu, 14 Sep 2006 01:00:48 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30D0F43D46 for ; Thu, 14 Sep 2006 01:00:47 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8E10lhp061915 for ; Wed, 13 Sep 2006 20:00:47 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Wed Sep 13 20:00:47 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8E10kVS061912 for freebsd-stable@freebsd.org; Wed, 13 Sep 2006 20:00:46 -0500 (CDT) (envelope-from karl) Date: Wed, 13 Sep 2006 20:00:46 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060914010046.GA61525@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060913144605.GD70245@garage.freebsd.pl> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! - back to Pawel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 01:00:48 -0000 On Wed, Sep 13, 2006 at 04:46:05PM +0200, Pawel Jakub Dawidek wrote: > On Sat, Sep 09, 2006 at 12:38:13PM -0500, Karl Denninger wrote: > > This is not cool folks. > > I'm really sorry for the breakage. I'm trying to treat -STABLE very > gently, unfortunately this time I made a mistake. .... (elided) Thank you Pawel for the explanation. I understand that things go wrong; as a software developer I've let bad code "out of the barn" before. I try like hell not to have it happen, but it has.... The explanation is appreciated. BTW, part of the issue here with the -BETA thing is that there's no clear timeline on this available to people. I certainly was not aware that you were in a pre-check period to locking down the code to start the process of burning the next minor "official" rev. BTW, if this is indeed the case, you guys definitely need to look at the PR I filed on the Rcoketport driver. That problem either needs to be found and taken care of or those boards need to come out of the supported hardware list for the next release - its definitely broken, and the cause is not something immediately obvious (or I would have fixed it by now!) I efforting this but its its only got a moderate priority around here right now. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 01:16: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 EDFE616A4E0 for ; Thu, 14 Sep 2006 01:16:45 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from tomts25-srv.bellnexxia.net (tomts25.bellnexxia.net [209.226.175.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CFDF43D45 for ; Thu, 14 Sep 2006 01:16:45 +0000 (GMT) (envelope-from dmagda@ee.ryerson.ca) Received: from [192.168.1.132] ([67.71.54.4]) by tomts25-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060914011643.WTDH1747.tomts25-srv.bellnexxia.net@[192.168.1.132]>; Wed, 13 Sep 2006 21:16:43 -0400 In-Reply-To: <20060914010046.GA61525@FS.denninger.net> References: <20060909173813.GA1388@FS.denninger.net> <20060913144605.GD70245@garage.freebsd.pl> <20060914010046.GA61525@FS.denninger.net> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Magda Date: Wed, 13 Sep 2006 21:16:42 -0400 To: Karl Denninger X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! - back to Pawel 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: Thu, 14 Sep 2006 01:16:46 -0000 On Sep 13, 2006, at 21:00, Karl Denninger wrote: > BTW, part of the issue here with the -BETA thing is that there's no > clear > timeline on this available to people. I certainly was not aware > that you were > in a pre-check period to locking down the code to start the process > of burning > the next minor "official" rev. Some upcoming release information is available online: http://www.freebsd.org/releng/ From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 01:20: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 3FED316A501 for ; Thu, 14 Sep 2006 01:20:38 +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 C5C1043D55 for ; Thu, 14 Sep 2006 01:20:37 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 31883 invoked from network); 14 Sep 2006 11:20:36 +1000 Received: from 124-168-25-250.dyn.iinet.net.au (HELO localhost) (124.168.25.250) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Sep 2006 11:20:36 +1000 Date: Thu, 14 Sep 2006 11:20:31 +1000 From: Norberto Meijome To: freebsd-stable@FreeBSD.ORG Message-ID: <20060914112031.130597f5@localhost> In-Reply-To: References: <20060913125850.T90966@ns1.as.pvp.se> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 01:20:38 -0000 On Wed, 13 Sep 2006 12:53:29 +0100 Pete French wrote: > > I disagree, I would like to have an notice about it. Even though it might > > not say much. Just a "The code of the stable branch has been freezed due > > to the upcomming release of X.Y" > > It is kind of useful, because it's the code freeze point at which I start > re-scheduling my work day so I can do BSD testing. I can't justify tracking > all the time on work machine unfortunately, but I do like to make an effort > to test thoroughly before something is released (the more the better, right?) > so it's good to know these things. I agree with this - yet another automated email wont really hurt, specially if it conveys useful information ;) _________________________ {Beto|Norberto|Numard} Meijome ...using the internet as it was originally intended... for the further research of pornography and pipebombs. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 02:20: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 8F36D16A403 for ; Thu, 14 Sep 2006 02:20:36 +0000 (UTC) (envelope-from myers@aedifice.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AF4C43D4C for ; Thu, 14 Sep 2006 02:20:36 +0000 (GMT) (envelope-from myers@aedifice.net) Received: from veetwin.aedifice.net (c-24-6-65-32.hsd1.ca.comcast.net[24.6.65.32]) by comcast.net (rwcrmhc12) with ESMTP id <20060914022034m1200rtl2be>; Thu, 14 Sep 2006 02:20:35 +0000 Received: from veetwin (veetwin [10.0.0.1]) by veetwin.aedifice.net (8.13.8/8.13.1) with ESMTP id k8E2KYYd099644; Wed, 13 Sep 2006 19:20:34 -0700 (PDT) (envelope-from myers@aedifice.net) Date: Wed, 13 Sep 2006 19:20:34 -0700 (PDT) From: David Myers To: Ronald Klop In-Reply-To: Message-ID: <20060913191743.N99632@veetwin.aedifice.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 02:20:36 -0000 >> Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting I got a bazillion of these, and a completely unusable machine, when I upgraded to 6.1-stable sources as of two days ago. The machine would simply freeze for minutes at a time. Going back to my previous kernel (dating from late July) made everything just fine. So something got seriously broken in the em driver in the last few weeks. -David. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 02:25: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 3D55B16A407 for ; Thu, 14 Sep 2006 02:25:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B31CD43D45 for ; Thu, 14 Sep 2006 02:25:10 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.8/8.13.8) with ESMTP id k8E2P8X3072885; Wed, 13 Sep 2006 22:25:08 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.6/8.13.3) with ESMTP id k8E2P79G059684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Sep 2006 22:25:07 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <7.0.1.0.0.20060913222425.148b78e0@sentex.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Wed, 13 Sep 2006 22:25:09 -0400 To: David Myers From: Mike Tancsa In-Reply-To: <20060913191743.N99632@veetwin.aedifice.net> References: <20060913191743.N99632@veetwin.aedifice.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 02:25:11 -0000 At 10:20 PM 9/13/2006, David Myers wrote: >>>Sep 5 11:55:12 ronald kernel: em0: watchdog timeout -- resetting > > >I got a bazillion of these, and a completely unusable machine, when >I upgraded to 6.1-stable sources as of two days ago. The machine >would simply freeze for minutes at a time. Going back to my >previous kernel (dating from late July) made everything just fine. > >So something got seriously broken in the em driver in the last few weeks. Which version of the NIC do you have ? (pciconf -lv ) ---Mike From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 03:24: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 22A4E16A403 for ; Thu, 14 Sep 2006 03:24:00 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB0B943D45 for ; Thu, 14 Sep 2006 03:23:59 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so3143549pye for ; Wed, 13 Sep 2006 20:23:59 -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=l+Xpf1xkAow6yqIqe1iDRyYbQJeoYJXSil0Z/yiMZSjdhU7/ATbrsfBS0ZTPe4MSs8K8ERB4q2KhuqopxLhRLAFQnNAaGiOglpZeUfkucKRwuoK8LPxe5+cYs0ezNwJjgHcxIqCb8APHf8WwY9nM6Dyt/KZwccdlF+SGjiqxuIM= Received: by 10.35.96.7 with SMTP id y7mr14207318pyl; Wed, 13 Sep 2006 20:23:59 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Wed, 13 Sep 2006 20:23:58 -0700 (PDT) Message-ID: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> Date: Wed, 13 Sep 2006 20:23:58 -0700 From: "Jack Vogel" To: "Ronald Klop" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 03:24:00 -0000 On 9/13/06, Ronald Klop wrote: ... > Them manual page em(4) mentions trying another cable when the watchdog > timeout happens, so I tried that. But it didn't help. > Is there anything I can test to (help) debug this? > It happens a lot when my machine is under load. (100% CPU) > Is it possible that it happens since I upgraded the memory from 1GB to 2 > GB? watchdogs mean that the transmit ring is not being cleaned, so the question is what is your machine doing at 100% cpu, if its that busy the network watchdogs may just be a side effect and not the real problem? Jack From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 04:37:00 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 25C9416A403 for ; Thu, 14 Sep 2006 04:37:00 +0000 (UTC) (envelope-from huang@gddsn.org.cn) Received: from gddsn.org.cn (gddsn.org.cn [218.19.164.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 330D043D46 for ; Thu, 14 Sep 2006 04:36:59 +0000 (GMT) (envelope-from huang@gddsn.org.cn) Received: from [220.205.69.128] (unknown [220.205.69.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gddsn.org.cn (Postfix) with ESMTP id 0246B38CB73 for ; Thu, 14 Sep 2006 12:36:49 +0800 (CST) Message-ID: <4508DC51.4060300@gddsn.org.cn> Date: Thu, 14 Sep 2006 12:36:33 +0800 From: Huang wen hui User-Agent: Thunderbird 1.5.0.4 (X11/20060727) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Cc: Subject: FreeBSD does not use all cpus on top show. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 04:37:00 -0000 hi, I have HP Server install FreeBSD 6.1R/amd64 with 2CPUs ,2 logical CPUs per core. On top show, It should show 4 cpus, but I never see 1 and 3 cpu on show. Does anything I miss? --hwh # 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: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0xf4a Stepping = 10 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20000800 AMD Features2=0x1 Logical CPUs per core: 2 real memory = 6912208896 (6591 MB) avail memory = 6150582272 (5865 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci2: on pcib1 pcib2: at device 0.0 on pci2 pci3: on pcib2 bge0: mem 0xfdef0000-0xfdefffff irq 25 at device 1.0 on pci3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:18:71:74:2a:bf bge1: mem 0xfdee0000-0xfdeeffff irq 26 at device 1.1 on pci3 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:18:71:74:2a:be pcib3: at device 0.2 on pci2 pci4: on pcib3 ciss0: port 0x4000-0x40ff mem 0xfdff0000-0xfdff1fff,0xfdf80000-0xfdfbffff irq 51 at device 3.0 on pci4 ciss0: [GIANT-LOCKED] pcib4: at device 6.0 on pci0 pci5: on pcib4 pcib5: at device 0.0 on pci5 pci6: on pcib5 pcib6: at device 0.2 on pci5 pci10: on pcib6 uhci0: port 0x2000-0x201f irq 16 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 0x2020-0x203f 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 0x2040-0x205f 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 0x2060-0x207f 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 0xfbef0000-0xfbef03ff 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 pcib7: at device 30.0 on pci0 pci1: on pcib7 pci1: at device 3.0 (no driver attached) pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 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 sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xeffff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (amr_linux, 0xffffffff8062a040, 0) error 6 acd0: CDROM at ata0-master PIO4 SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 700049MB (1433700592 512 byte sectors: 255H 63S/T 65535C) Trying to mount root from ufs:/dev/da0s1a bge0: link state changed to DOWN bge0: link state changed to UP ciss0: *** Parity/consistency initialization complete, logical drive 0 ciss0: logical drive 0 () completed consistency initialisation #top last pid: 70381; load averages: 0.45, 0.48, 0.46 up 6+16:30:06 12:35:43 91 processes: 2 running, 89 sleeping CPU states: 12.2% user, 0.0% nice, 0.0% system, 0.2% interrupt, 87.6% idle Mem: 1177M Active, 3993M Inact, 269M Wired, 265M Cache, 214M Buf, 19M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 51047 root 6 20 0 748M 198M kserel 0 704:28 0.98% java 4887 root 9 20 0 359M 84468K kserel 0 134:36 0.00% java 97183 mysql 14 20 0 1175M 729M kserel 0 55:03 0.00% mysqld 4883 root 11 20 0 383M 88096K kserel 0 27:03 0.00% java 34821 root 5 20 0 1240M 43328K kserel 0 9:03 0.00% java 4938 root 1 96 0 7612K 1808K select 0 0:21 0.00% ntpd 2353 root 1 96 0 9356K 2644K select 0 0:10 0.00% sendmail 56321 root 1 96 0 28680K 5356K select 0 0:03 0.00% xterm 56318 root 1 96 0 28688K 5364K select 0 0:03 0.00% xterm 56322 root 1 96 0 28672K 5284K select 0 0:03 0.00% xterm 56315 root 1 96 0 51940K 10428K select 0 0:02 0.00% Xorg 2363 root 1 8 0 3560K 1064K nanslp 0 0:01 0.00% cron 2197 root 1 96 0 3540K 996K select 0 0:01 0.00% syslogd 2385 root 1 4 0 3504K 804K select 0 0:01 0.00% moused 2294 root 1 96 0 2420K 836K select 0 0:01 0.00% usbd 56320 root 1 96 0 27288K 5016K select 2 0:00 0.00% xclock 34284 root 1 20 0 7420K 2968K pause 0 0:00 0.00% csh 2357 smmsp 1 20 0 9224K 2368K pause 0 0:00 0.00% sendmail 70316 hwh 1 96 0 29368K 3380K select 2 0:00 0.00% sshd 2347 root 1 96 0 18428K 2256K select 0 0:00 0.00% sshd 56319 root 1 4 0 16056K 2904K select 0 0:00 0.00% twm 2145 root 1 4 0 620K 340K select 0 0:00 0.00% devd 70313 root 1 4 0 29392K 3356K sbwait 2 0:00 0.00% sshd 59068 root 1 4 0 29392K 3348K sbwait 0 0:00 0.00% sshd 70334 root 1 20 0 7352K 3008K pause 2 0:00 0.00% csh 56323 root 1 5 0 7092K 2900K ttyin 0 0:00 0.00% csh 59079 root 1 5 0 13304K 3308K ttyin 0 0:00 0.00% mysql 70317 hwh 1 20 0 7096K 2956K pause 2 0:00 0.00% csh 59071 hwh 1 4 0 29368K 3372K select 0 0:00 0.00% sshd 34038 root 1 8 0 17136K 1312K wait 0 0:00 0.00% login 51502 root 1 8 0 17136K 1444K wait 0 0:00 0.00% login 56292 root 1 20 0 7080K 2904K pause 2 0:00 0.00% csh 51547 root 1 5 0 7076K 2892K ttyin 2 0:00 0.00% csh 56324 root 1 5 0 7080K 2860K ttyin 0 0:00 0.00% csh 56325 root 1 5 0 7080K 2860K ttyin 0 0:00 0.00% csh 59072 hwh 1 20 0 7096K 2924K pause 0 0:00 0.00% csh 59076 root 1 20 0 7080K 2888K pause 2 0:00 0.00% csh 97159 mysql 1 8 0 5064K 1212K wait 0 0:00 0.00% sh 59075 hwh 1 8 0 17136K 1420K wait 0 0:00 0.00% su 70333 hwh 1 8 0 17136K 1428K wait 0 0:00 0.00% su 56296 root 1 8 0 5044K 1540K wait 0 0:00 0.00% sh 70381 root 1 96 0 6912K 2076K CPU2 2 0:00 0.00% top 56291 root 1 8 0 17112K 1356K wait 2 0:00 0.00% su 56314 root 1 8 0 4352K 1404K wait 0 0:00 0.00% xinit 50549 root 1 5 0 3504K 916K ttyin 2 0:00 0.00% getty 51509 root 1 5 0 3504K 932K ttyin 0 0:00 0.00% getty From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 04:39: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 5AC5716A416 for ; Thu, 14 Sep 2006 04:39:13 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B837643D46 for ; Thu, 14 Sep 2006 04:39:12 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (unknown [200.46.204.128]) by hub.org (Postfix) with ESMTP id 20C4B3A464E; Thu, 14 Sep 2006 01:39:09 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 48865-04; Thu, 14 Sep 2006 04:37:54 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id A3E9A3A464B; Thu, 14 Sep 2006 01:37:52 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 08AA446E41; Thu, 14 Sep 2006 01:37:54 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 04E4833C25; Thu, 14 Sep 2006 01:37:54 -0300 (ADT) Date: Thu, 14 Sep 2006 01:37:53 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Steve O'Hara-Smith In-Reply-To: <20060912171617.556a43cc.steve@sohara.org> Message-ID: <20060914012316.V1031@ganymede.hub.org> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> <4506D884.4050605@scls.lib.wi.us> <20060912171617.556a43cc.steve@sohara.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 04:39:13 -0000 On Tue, 12 Sep 2006, Steve O'Hara-Smith wrote: > On Tue, 12 Sep 2006 10:55:48 -0500 > Greg Barniskis wrote: > >> If you /track/ STABLE by frequently cvsupping it and rebuilding your >> system, you will very likely encounter a serious problem sooner or >> later. That's why tracking it is not recommended for production >> systems. > > I did exactly that all the way from 2.0 to 4.11 on various machines > without ever having any trouble. Ditto ... in fact, I do that on my desktop and have yet to hit a problem ... -STABLE *is* generally very stable ... Stupid question here ... if -STABLE shouldn't be tracked, who exactly is doing testing on it? Those doing "the work" on -CURRENT, I would imagine, are tracking -CURRENT, and testing the code put in there for bugs ... when deemed 'bug free', then its being MFCd to -STABLE, but if those of us that *are* tracking -STABLE stop'd tracking it ... who would be testing it? ---- 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 Thu Sep 14 04:42: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 7279816A4E0 for ; Thu, 14 Sep 2006 04:42:48 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE78543D68 for ; Thu, 14 Sep 2006 04:42:43 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8E4ggB9094003; Wed, 13 Sep 2006 21:42:43 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8E4ggLT093998; Wed, 13 Sep 2006 21:42:42 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 21:42:41 -0700 From: Gary Kline To: Chuck Swiger Message-ID: <20060914044241.GA92358@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> <0B8BF03E-8F4A-4279-850B-2EA7FF5E1B89@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0B8BF03E-8F4A-4279-850B-2EA7FF5E1B89@mac.com> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: Gary Kline , freebsd-stable Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 04:42:48 -0000 On Wed, Sep 13, 2006 at 05:25:35PM -0700, Chuck Swiger wrote: > On Sep 13, 2006, at 4:49 PM, Gary Kline wrote: > > A couple of things. Will having gcc unroll loops have any > > negative consequences? > > Yes, it certainly can have negative consequences. The primary intent > of using that option is to change a loop from executing the test or > control block for each iteration that the body is executed, to > executing the loop body several times and checking the test or > control block less often. The issue is that there is often > additional setup or post-loop fixups to ensure that the loop body > actually is executed the right number of times, which makes the > generated binary code much larger. > > This can mean that the loop no longer fits within the L1 instruction > cache, which will usually result in the program going slower, rather > than faster. Using the option will always increase the size of > compiled executables. > > > (I can't imagine how:: but better > > informed than to have something crash inexplicability.) > > With 6.X safe at -O2 and with -funroll-loops, that should be > > a slight gain, right? > > -funroll-loops is as likely to decrease performance for a particular > program as it is to help. Isn't the compiler intelligent enough to have a reasonable limit, N, of the loops it will unroll to ensure a faster runtime? Something much less than 1000, say; possibly less than 100. At least, if the initializiation and end-loop code *plus* the loop code itself were too large for the cache, my thought is that gcc would back out. Imay be giving RMS too much credit; but if memory serves, thed compiler was GNU's first project. And Stallman was into GOFAI, &c, for better/worse.[1] Anyway, for now I'll comment out the unroll-loops arg. > > One particular caveat with using that option is that the increase in > program size apparently causes the initial bootloader code to no > longer fit within a single sector, making the system unbootable. > > > [Dumb] questions:: first, what does the compiler do with > > "-fno-strict-aliasing"? > > It prevents the compiler from generating buggy output from source > code which uses type-punning. > > http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html > > A safe optimizer must assume that an arbitrary assignment via a > pointer dereference can change any value in memory, which means that > you have to spill and reload any data being cached in CPU registers > around the use of the pointer, except for const's, variables declared > as "register", and possibly function arguments being passed via > registers and not on the stack (cf "register windows" on the SPARC > hardware, or HP/PA's calling conventions). Well, I'd added the no-strict-aliasing flag to make.conf! Pointers give me indigestion ... even after all these years. Thanks for your insights. And the URL. gary [1]. Seems to me that "good old-fashioned AI" techniques would work in something like a compiler where you probblyhave a good idea of most heuristics. -gk > > -- > -Chuck > > > > _______________________________________________ > 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" -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 04:46: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 E9D6F16A492; Thu, 14 Sep 2006 04:46: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 9CDE743D49; Thu, 14 Sep 2006 04:46:23 +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 65CD51A4D88; Wed, 13 Sep 2006 21:46:23 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 43C82511D9; Thu, 14 Sep 2006 00:46:22 -0400 (EDT) Date: Thu, 14 Sep 2006 00:46:22 -0400 From: Kris Kennaway To: "Marc G. Fournier" Message-ID: <20060914044621.GA26351@xor.obsecurity.org> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> <4506D884.4050605@scls.lib.wi.us> <20060912171617.556a43cc.steve@sohara.org> <20060914012316.V1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a8Wt8u1KmwUX3Y2C" Content-Disposition: inline In-Reply-To: <20060914012316.V1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 04:46:24 -0000 --a8Wt8u1KmwUX3Y2C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 14, 2006 at 01:37:53AM -0300, Marc G. Fournier wrote: > On Tue, 12 Sep 2006, Steve O'Hara-Smith wrote: >=20 > >On Tue, 12 Sep 2006 10:55:48 -0500 > >Greg Barniskis wrote: > > > >>If you /track/ STABLE by frequently cvsupping it and rebuilding your > >>system, you will very likely encounter a serious problem sooner or > >>later. That's why tracking it is not recommended for production > >>systems. > > > > I did exactly that all the way from 2.0 to 4.11 on various machines > >without ever having any trouble. >=20 > Ditto ... in fact, I do that on my desktop and have yet to hit a problem= =20 > ... -STABLE *is* generally very stable ... >=20 > Stupid question here ... if -STABLE shouldn't be tracked No-one's said that, so yeah, not the best question ;^) Kris --a8Wt8u1KmwUX3Y2C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCN6dWry0BWjoQKURAqP0AKD2pT+qGEqPFUQUrG9YoNVkOOCM1gCgvDeg aUUOrl72rYvy2JIvKCmhr5o= =NT5p -----END PGP SIGNATURE----- --a8Wt8u1KmwUX3Y2C-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 04:52: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 2886F16A403; Thu, 14 Sep 2006 04:52:18 +0000 (UTC) (envelope-from anthony.maher@uts.edu.au) Received: from gaz.itd.uts.edu.au (gaz.itd.uts.edu.au [138.25.22.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A91443D72; Thu, 14 Sep 2006 04:52:08 +0000 (GMT) (envelope-from anthony.maher@uts.edu.au) Received: by gaz.itd.uts.edu.au (Postfix, from userid 1011) id 1B6CEAE783; Thu, 14 Sep 2006 14:47:43 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by gaz.itd.uts.edu.au (Postfix/Intermediary) with ESMTP id 0C7C4AE86C; Thu, 14 Sep 2006 14:47:43 +1000 (EST) Received: from vimes (vimes.itd.uts.edu.au [138.25.243.34]) by gaz.itd.uts.edu.au (Postfix/Ingress) with ESMTP id ED931AE783; Thu, 14 Sep 2006 14:47:42 +1000 (EST) Received: from [138.25.81.112] by postoffice.uts.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTPS id <0J5K001VRG6VBH70@postoffice.uts.edu.au>; Thu, 14 Sep 2006 14:52:07 +1000 (EST) Date: Thu, 14 Sep 2006 14:52:07 +1000 From: Tony Maher In-reply-to: <20060914012316.V1031@ganymede.hub.org> To: "Marc G. Fournier" Message-id: <4508DFF7.1060808@uts.edu.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-Enigmail-Version: 0.93.0.0 References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <20060912141547.GA11713@FS.denninger.net> <4506D884.4050605@scls.lib.wi.us> <20060912171617.556a43cc.steve@sohara.org> <20060914012316.V1031@ganymede.hub.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060511 Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 04:52:18 -0000 Marc G. Fournier wrote: > On Tue, 12 Sep 2006, Steve O'Hara-Smith wrote: > >> On Tue, 12 Sep 2006 10:55:48 -0500 >> Greg Barniskis wrote: >> >>> If you /track/ STABLE by frequently cvsupping it and rebuilding your >>> system, you will very likely encounter a serious problem sooner or >>> later. That's why tracking it is not recommended for production >>> systems. >> >> >> I did exactly that all the way from 2.0 to 4.11 on various machines >> without ever having any trouble. > > > Ditto ... in fact, I do that on my desktop and have yet to hit a problem > ... -STABLE *is* generally very stable ... > > Stupid question here ... if -STABLE shouldn't be tracked, who exactly is > doing testing on it? Those doing "the work" on -CURRENT, I would > imagine, are tracking -CURRENT, and testing the code put in there for > bugs ... when deemed 'bug free', then its being MFCd to -STABLE, but if > those of us that *are* tracking -STABLE stop'd tracking it ... who would > be testing it? It is not that you should not track it but where you should be tracking/testing it. Not on critical production servers would be a good start ;-) -- tonym From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 04:57: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 DC6B216A407 for ; Thu, 14 Sep 2006 04:57:34 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E0DE43D45 for ; Thu, 14 Sep 2006 04:57:34 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8E4vRqF094102; Wed, 13 Sep 2006 21:57:27 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8E4vPkH094101; Wed, 13 Sep 2006 21:57:25 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 21:57:25 -0700 From: Gary Kline To: Tony Maher Message-ID: <20060914045725.GB92358@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> <45089D47.6070005@uts.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45089D47.6070005@uts.edu.au> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: Gary Kline , freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 04:57:34 -0000 On Thu, Sep 14, 2006 at 10:07:35AM +1000, Tony Maher wrote: > Gary Kline wrote: > > > > > > > A couple of things. Will having gcc unroll loops have any > > negative consequences? (I can't imagine how:: but better > > informed than to have something crash inexplicability.) > > With 6.X safe at -O2 and with -funroll-loops, that should be > > a slight gain, right? (It also will make an upgrade from 5.5 > > to 6.[12] that much more rational.) > > -funroll-loops affect loader see > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028145.html > Right. This is probably what Chuck Swiger was talking about. I've never had this problems on my 5.[345] releases. And not with 6.1 (knock-wood!!). I've just upgraded to -RELEASE and going to rebuild overnight on the server that traped out. With -funroll-loops gone :-) gary > -- > tonym -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 05:01: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 B3BA916A40F for ; Thu, 14 Sep 2006 05:01:37 +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 8031A43D5D for ; Thu, 14 Sep 2006 05:01:35 +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 10DC01A3C20; Wed, 13 Sep 2006 22:01:35 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5E55B5134B; Thu, 14 Sep 2006 01:01:33 -0400 (EDT) Date: Thu, 14 Sep 2006 01:01:33 -0400 From: Kris Kennaway To: Gary Kline Message-ID: <20060914050133.GA26618@xor.obsecurity.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> <45089D47.6070005@uts.edu.au> <20060914045725.GB92358@thought.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <20060914045725.GB92358@thought.org> User-Agent: Mutt/1.4.2.2i Cc: Tony Maher , freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 05:01:37 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 13, 2006 at 09:57:25PM -0700, Gary Kline wrote: > On Thu, Sep 14, 2006 at 10:07:35AM +1000, Tony Maher wrote: > > Gary Kline wrote: > >=20 > > > > > > > > > A couple of things. Will having gcc unroll loops have any > > > negative consequences? (I can't imagine how:: but better=20 > > > informed than to have something crash inexplicability.) > > > With 6.X safe at -O2 and with -funroll-loops, that should be > > > a slight gain, right? (It also will make an upgrade from 5.5=20 > > > to 6.[12] that much more rational.) > >=20 > > -funroll-loops affect loader see > > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028145= .html > >=20 >=20 > Right. This is probably what Chuck Swiger was talking about. > I've never had this problems on my 5.[345] releases. And not > with 6.1 (knock-wood!!).=20 >=20 > I've just upgraded to -RELEASE and going to rebuild overnight on > the server that traped out. With -funroll-loops gone :-) Just leave it alone unless you know what you're doing...fiddling with the compiler flags just isn't going to give you a secret performance boost for general workloads, no matter how cool it might make you feel :) Kris --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCOIsWry0BWjoQKURAjp+AKD7LQQZMDV0Vz/FyxStvzRqu+MAAwCgyweA GC93zK7LS0GR7YX3k9G6vrs= =gYjq -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 05:02: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 7255316A403 for ; Thu, 14 Sep 2006 05:02:57 +0000 (UTC) (envelope-from ota@j.email.ne.jp) Received: from mail.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEBD143D58 for ; Thu, 14 Sep 2006 05:02:56 +0000 (GMT) (envelope-from ota@j.email.ne.jp) Received: from dynabook.advok.com (pool-151-197-217-80.phil.east.verizon.net [151.197.217.80]) by mail.asahi-net.or.jp (Postfix) with ESMTP id D3181D04B; Thu, 14 Sep 2006 14:02:52 +0900 (JST) Date: Thu, 14 Sep 2006 01:02:49 -0500 From: Yoshihiro Ota To: kama , freebsd-stable@FreeBSD.ORG Message-Id: <20060914010249.672ac405.ota@j.email.ne.jp> In-Reply-To: <20060913125850.T90966@ns1.as.pvp.se> References: <200609131038.k8DAcpc7068953@lurza.secnetix.de> <20060913125850.T90966@ns1.as.pvp.se> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: 6.2? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 05:02:57 -0000 On Wed, 13 Sep 2006 13:07:20 +0200 (CEST) kama wrote: > > On Wed, 13 Sep 2006, Oliver Fromme wrote: > > > > > That's true, and the schedule will most probably change. > > Currently the release is listed for Oct. 9th, but I bet > > that it'll be delayed. > > I disagree, I would like to have an notice about it. Even though it might > not say much. Just a "The code of the stable branch has been freezed due > to the upcomming release of X.Y" > I agree with Kama. I specificly switched once to stable for pre-release testing purpose. I saw email from one of the developers claiming that not many people join pre-release testing. (I do not remember whether it was not many people join BETA testing or RC testing. Anyway, I saw it in one of the quota issue e-mail chain on 6.1-RELEASE.) If we are not in such a stage, I personally prefer to stick with releases. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 05:23: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 54B3E16A407 for ; Thu, 14 Sep 2006 05:23:22 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF80743D6D for ; Thu, 14 Sep 2006 05:23:20 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8E5NJKs094210; Wed, 13 Sep 2006 22:23:19 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8E5NIOW094209; Wed, 13 Sep 2006 22:23:18 -0700 (PDT) (envelope-from kline) Date: Wed, 13 Sep 2006 22:23:18 -0700 From: Gary Kline To: Mark Andrews Message-ID: <20060914052318.GC92358@thought.org> References: <20060913234934.GA92067@thought.org> <200609140002.k8E02b11073990@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609140002.k8E02b11073990@drugs.dv.isc.org> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: Gary Kline , freebsd-stable@freebsd.org, Stefan Lambrev Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 05:23:22 -0000 On Thu, Sep 14, 2006 at 10:02:37AM +1000, Mark Andrews wrote: > > > On Wed, Sep 13, 2006 at 12:17:15PM +0300, Stefan Lambrev wrote: > > > Hello, > > > > > > Oliver Fromme wrote: > > > >Marc G. Fournier wrote: > > > > > What are ppl currently using for CFLAGS/COPTFLAGS in /etc/make.conf for > > > > > > > building kernel/world? I know awhile back it wasn't recommended to go > > > > > above -O2, for instance, but suspect that has changed ... ? > > > > > > > >The best optimization is probably to not override the > > > >defaults at all, because they're already pretty optimal. > > > >In fact, by overriding the defaults there's a good chance > > > >to make things worse. :-) > > > > > > > >The default CFLAGS are "-O2 -pipe -fno-strict-aliasing". > > > >Anything above -O2 isn't supported, and using -O2 without > > > >-fno-strict-aliasing also isn't supported (and will create > > > >broken code for some programs). A common mistake is to > > > >specify CFLAGS="-O2 -pipe" and omit -fno-strict-aliasing. > > > >That'll shot you in the foot sooner or later. > > > > > > > >Best regards > > > > Oliver > > > > [[ ... ]] > > > > > > A couple of things. Will having gcc unroll loops have any > > negative consequences? (I can't imagine how:: but better > > informed than to have something crash inexplicability.) > > With 6.X safe at -O2 and with -funroll-loops, that should be > > a slight gain, right? (It also will make an upgrade from 5.5 > > to 6.[12] that much more rational.) > > > > [Dumb] questions:: first, what does the compiler do with > > "-fno-strict-aliasing"? And is there any guess, any SWAG even, > > on when FreeBSD will safe with -O3?? > > Lots of code is not strict-aliasing safe. Gcc itself can't > determine all the cases which a construct is not strict-aliasing > safe so even after getting rid of all the warnings gcc > produces you can't be sure your code is strict-aliasing > safe. Think of -fstrict-aliasing as optimisation without > a saftey net. If your code doesn't cast pointers you should > be safe otherwise you need to be really, really, really > careful when you turn this on. > Well, my own pointer code is pretty trustworthy. It's also pretty simple-minded and thoroughly tested, even tho it's just for my own use. Other's code, dunno. People who cut their teeth on pointers and may be just a wee bit cavalier: *Bzzz* Point well taken. -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 06:27: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 3DC5F16A403 for ; Thu, 14 Sep 2006 06:27:38 +0000 (UTC) (envelope-from verbo.solo@sbcglobal.net) Received: from smtp101.plus.mail.re2.yahoo.com (smtp101.plus.mail.re2.yahoo.com [206.190.53.26]) by mx1.FreeBSD.org (Postfix) with SMTP id 97D7543D49 for ; Thu, 14 Sep 2006 06:27:37 +0000 (GMT) (envelope-from verbo.solo@sbcglobal.net) Received: (qmail 63158 invoked from network); 14 Sep 2006 06:27:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=bc7Vr8uGD2jgYYg1Fnh4eTBLuLnGv1eSs09KQoZseqTMjgKVLeaIdAKENWUgQMfibgSQrtU5ASzVwOEFXdc8RNsBgVEuVVbhd8hfyAuxvriJXbamCRZq2Nn3nWV4+LAXlHXUBKDqemrJKW5IpSZFC7cM4C3QTXJeUTaYCYglcKs= ; Received: from unknown (HELO elbereth.gateway.2wire.net) (verbo.solo@sbcglobal.net@69.151.15.132 with plain) by smtp101.plus.mail.re2.yahoo.com with SMTP; 14 Sep 2006 06:27:35 -0000 From: "Charles P. Schaum" To: "freebsd-stable@freebsd.org" Content-Type: text/plain Date: Thu, 14 Sep 2006 01:27:34 -0500 Message-Id: <1158215254.2889.49.camel@elbereth.gateway.2wire.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Thanks! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 06:27:38 -0000 In the midst of bugs and issues, to which I can empathize and relate, I wish to offer thanks for all your hard work. My history: In late 03 my one computer died hot death. I built a new one after a quick parts dash. With new parts, Windows would still eventually die. Drivers were unstable. Not fun. Not my scene. In 04 I started looking at Linux. Even tried fink on the Mac. Gravitated to Debian. Did a partition and an install. Ouch! My NIC wasn't supported in Woody. Got source from Intel, compiled the module and upgraded to Sarge. That was the first two days. Used Debian but it was just ancient. Backports were their own headache. Dealt with early 2.6 kernel woes. Went to Fedora 3. Worked OK until 4. Switched to Mandrake 10 and blew an O-ring. Switched to SUSE. Learned to hate YaST. Learned to hate how they did repos. Switched to Ubuntu. Liked the setup for a while, then broke it by hooking to a noncanonical repo. Dealt with the ongoing civil war between livna and freshrpms again, although Fedora 5 was better. Then I found FreeBSD in March 06. After three months I had learned, broken, cussed and whatever else. And in frustration I tried Fedora 5 again and new Ubuntu. Neither did Samba well. Both could be made to hang by a neat little trick I do with Xsane called using my scanner for more than about ten scans. Udev is evil on both. Networking looks like a GUI and acts like...a mother. So I came back to FreeBSD. And I got STABLE up and it has been running great since I did a repartition in August. (It WAS running great since June but I wanted to retune the FS.) STABLE gave me DRM (i845), newer CUPS (after I figured out a few issues and evoked fond memories of my JCL tantrum mat), and as with RELEASE, no hangs with Xsane, all the software I want to run, not just what a distro says I can, and a community that treats thinking people like more than trogs. I never met a Linux distro where the people involved were so accessible and actually answered questions and had discussions instead of just referring one to a Bugzilla page. There's a helluva lot more slack (Bob-style) here than elsewhere. And after reading manpages and googling, I found out that I learned more than most reference books at Borders can tell, especially the ficticious Unix: The Complete Reference. FreeBSD people are helpful, as is reading the man/docs. FreeBSD requires people to kick it to a higher level. But permissions mean what they say, Samba works and os/port maintainers will work with you when a build fails. Software MIDI without ALSA works faster than any Linux. The same for Mplayer and Xine. I can use sudo and nice to crank the heck out of emulators and the system doesn't just die. I got caught a little before 6.1 came out, but I passed that hurdle and got a lot more cautious about how often I update the OS. I learned NetBSD as well. I relearned a lot of computer skills I had forgotten. I also did some just-plain dumb things and got what I asked for. I am real happy with FreeBSD. I would be interested in seeing more desktop stuff become a reality. Neither of the desktop variants of FreeBSD works so well for me, yet. But I would rather stick with it and try to help what little I can. Because this OS is not just an anti-Windows effulgent with GNUish pride. It's like the Unix I remember from yesterday and it is what will provide an alternative to Windows-template mentalities in the future. Cause Windows just breaks when used long enough. Why should I pay for that? Why should I use operating systems that want to think that way and yet pretend to be different? I don't need to become my worst enemy to survive and neither will my OS. You do a lot and know a lot more than I ever will. And when my box turns on, dang it, it works. Sweeeet! Charles From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 06:50: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 DCB4416A4A0 for ; Thu, 14 Sep 2006 06:50:33 +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 1B39E43D92 for ; Thu, 14 Sep 2006 06:50:09 +0000 (GMT) (envelope-from dkirhlarov@oilspace.com) Received: from dkirhlarov.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 E125E136CD8 for ; Thu, 14 Sep 2006 07:50:07 +0100 (BST) Received: from dkirhlarov.mow.oilspace.com (localhost [127.0.0.1]) by dkirhlarov.mow.oilspace.com (8.13.6/8.13.6) with ESMTP id k8E6o7ev076058 for ; Thu, 14 Sep 2006 10:50:07 +0400 (MSD) (envelope-from dkirhlarov@dkirhlarov.mow.oilspace.com) Received: (from dkirhlarov@localhost) by dkirhlarov.mow.oilspace.com (8.13.6/8.13.6/Submit) id k8E6o6mx076057 for freebsd-stable@freebsd.org; Thu, 14 Sep 2006 10:50:06 +0400 (MSD) (envelope-from dkirhlarov) Date: Thu, 14 Sep 2006 10:50:06 +0400 From: Dmitriy Kirhlarov To: freebsd-stable@freebsd.org Message-ID: <20060914065005.GA75610@dimma.mow.oilspace.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <4508DC51.4060300@gddsn.org.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4508DC51.4060300@gddsn.org.cn> X-Mailer: Mutt-ng devel (2005-03-13) based on Mutt 1.5.9 X-Operating-System: FreeBSD 6.1-STABLE User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: Re: FreeBSD does not use all cpus on top show. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 06:50:33 -0000 On Thu, Sep 14, 2006 at 12:36:33PM +0800, Huang wen hui wrote: > hi, > I have HP Server install FreeBSD 6.1R/amd64 with 2CPUs ,2 logical CPUs > per core. > On top show, It should show 4 cpus, but I never see 1 and 3 cpu on show. > Does anything I miss? You must switch off hiper threading in bios and in your system. > > --hwh > > # 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: Intel(R) Xeon(TM) CPU 3.20GHz (3200.13-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0xf4a Stepping = 10 > Features=0xbfebfbff > Features2=0x641d> > AMD Features=0x20000800 > AMD Features2=0x1 > Logical CPUs per core: 2 > real memory = 6912208896 (6591 MB) > avail memory = 6150582272 (5865 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > ioapic3 irqs 72-95 on motherboard > ioapic4 irqs 96-119 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > pcib0: on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci2: on pcib1 > pcib2: at device 0.0 on pci2 > pci3: on pcib2 > bge0: mem > 0xfdef0000-0xfdefffff irq 25 at device 1.0 on pci3 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:18:71:74:2a:bf > bge1: mem > 0xfdee0000-0xfdeeffff irq 26 at device 1.1 on pci3 > miibus1: on bge1 > brgphy1: on miibus1 > brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge1: Ethernet address: 00:18:71:74:2a:be > pcib3: at device 0.2 on pci2 > pci4: on pcib3 > ciss0: port 0x4000-0x40ff mem > 0xfdff0000-0xfdff1fff,0xfdf80000-0xfdfbffff irq 51 at device 3.0 on pci4 > ciss0: [GIANT-LOCKED] > pcib4: at device 6.0 on pci0 > pci5: on pcib4 > pcib5: at device 0.0 on pci5 > pci6: on pcib5 > pcib6: at device 0.2 on pci5 > pci10: on pcib6 > uhci0: port 0x2000-0x201f > irq 16 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 0x2020-0x203f > 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 0x2040-0x205f > 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 0x2060-0x207f > 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 > 0xfbef0000-0xfbef03ff 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 > pcib7: at device 30.0 on pci0 > pci1: on pcib7 > pci1: at device 3.0 (no driver attached) > pci1: at device 4.0 (no driver attached) > pci1: at device 4.2 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x500-0x50f at device 31.1 on pci0 > ata0: on atapci0 > ata1: on atapci0 > acpi_tz0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: flags 0x1 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 > sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio0: type 16550A > fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 > fdc0: [FAST] > orm0: at iomem > 0xc0000-0xc7fff,0xc8000-0xcbfff,0xee000-0xeffff on isa0 > ppc0: cannot reserve I/O port range > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > module_register_init: MOD_LOAD (amr_linux, 0xffffffff8062a040, 0) error 6 > acd0: CDROM at ata0-master PIO4 > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > da0 at ciss0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 135.168MB/s transfers > da0: 700049MB (1433700592 512 byte sectors: 255H 63S/T 65535C) > Trying to mount root from ufs:/dev/da0s1a > bge0: link state changed to DOWN > bge0: link state changed to UP > ciss0: *** Parity/consistency initialization complete, logical drive 0 > ciss0: logical drive 0 () completed consistency initialisation > > > #top > last pid: 70381; load averages: 0.45, 0.48, 0.46 up 6+16:30:06 12:35:43 > 91 processes: 2 running, 89 sleeping > CPU states: 12.2% user, 0.0% nice, 0.0% system, 0.2% interrupt, 87.6% idle > Mem: 1177M Active, 3993M Inact, 269M Wired, 265M Cache, 214M Buf, 19M Free > Swap: 4096M Total, 4096M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 51047 root 6 20 0 748M 198M kserel 0 704:28 0.98% java > 4887 root 9 20 0 359M 84468K kserel 0 134:36 0.00% java > 97183 mysql 14 20 0 1175M 729M kserel 0 55:03 0.00% mysqld > 4883 root 11 20 0 383M 88096K kserel 0 27:03 0.00% java > 34821 root 5 20 0 1240M 43328K kserel 0 9:03 0.00% java > 4938 root 1 96 0 7612K 1808K select 0 0:21 0.00% ntpd > 2353 root 1 96 0 9356K 2644K select 0 0:10 0.00% sendmail > 56321 root 1 96 0 28680K 5356K select 0 0:03 0.00% xterm > 56318 root 1 96 0 28688K 5364K select 0 0:03 0.00% xterm > 56322 root 1 96 0 28672K 5284K select 0 0:03 0.00% xterm > 56315 root 1 96 0 51940K 10428K select 0 0:02 0.00% Xorg > 2363 root 1 8 0 3560K 1064K nanslp 0 0:01 0.00% cron > 2197 root 1 96 0 3540K 996K select 0 0:01 0.00% syslogd > 2385 root 1 4 0 3504K 804K select 0 0:01 0.00% moused > 2294 root 1 96 0 2420K 836K select 0 0:01 0.00% usbd > 56320 root 1 96 0 27288K 5016K select 2 0:00 0.00% xclock > 34284 root 1 20 0 7420K 2968K pause 0 0:00 0.00% csh > 2357 smmsp 1 20 0 9224K 2368K pause 0 0:00 0.00% sendmail > 70316 hwh 1 96 0 29368K 3380K select 2 0:00 0.00% sshd > 2347 root 1 96 0 18428K 2256K select 0 0:00 0.00% sshd > 56319 root 1 4 0 16056K 2904K select 0 0:00 0.00% twm > 2145 root 1 4 0 620K 340K select 0 0:00 0.00% devd > 70313 root 1 4 0 29392K 3356K sbwait 2 0:00 0.00% sshd > 59068 root 1 4 0 29392K 3348K sbwait 0 0:00 0.00% sshd > 70334 root 1 20 0 7352K 3008K pause 2 0:00 0.00% csh > 56323 root 1 5 0 7092K 2900K ttyin 0 0:00 0.00% csh > 59079 root 1 5 0 13304K 3308K ttyin 0 0:00 0.00% mysql > 70317 hwh 1 20 0 7096K 2956K pause 2 0:00 0.00% csh > 59071 hwh 1 4 0 29368K 3372K select 0 0:00 0.00% sshd > 34038 root 1 8 0 17136K 1312K wait 0 0:00 0.00% login > 51502 root 1 8 0 17136K 1444K wait 0 0:00 0.00% login > 56292 root 1 20 0 7080K 2904K pause 2 0:00 0.00% csh > 51547 root 1 5 0 7076K 2892K ttyin 2 0:00 0.00% csh > 56324 root 1 5 0 7080K 2860K ttyin 0 0:00 0.00% csh > 56325 root 1 5 0 7080K 2860K ttyin 0 0:00 0.00% csh > 59072 hwh 1 20 0 7096K 2924K pause 0 0:00 0.00% csh > 59076 root 1 20 0 7080K 2888K pause 2 0:00 0.00% csh > 97159 mysql 1 8 0 5064K 1212K wait 0 0:00 0.00% sh > 59075 hwh 1 8 0 17136K 1420K wait 0 0:00 0.00% su > 70333 hwh 1 8 0 17136K 1428K wait 0 0:00 0.00% su > 56296 root 1 8 0 5044K 1540K wait 0 0:00 0.00% sh > 70381 root 1 96 0 6912K 2076K CPU2 2 0:00 0.00% top > 56291 root 1 8 0 17112K 1356K wait 2 0:00 0.00% su > 56314 root 1 8 0 4352K 1404K wait 0 0:00 0.00% xinit > 50549 root 1 5 0 3504K 916K ttyin 2 0:00 0.00% getty > 51509 root 1 5 0 3504K 932K ttyin 0 0:00 0.00% getty > > > _______________________________________________ > 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" -- Dmitriy Kirhlarov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7247 ext.208 F:+7 495 105 7246 E:DmitriyKirhlarov@oilspace.com OILspace - The resource enriched - www.oilspace.com From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 08:34: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 222EA16A47B for ; Thu, 14 Sep 2006 08:34:50 +0000 (UTC) (envelope-from jared@little-miracles.org) Received: from mail-ihug.icp-qv1-irony2.iinet.net.au (ihug-mail.icp-qv1-irony2.iinet.net.au [203.59.1.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B575843D69 for ; Thu, 14 Sep 2006 08:34:46 +0000 (GMT) (envelope-from jared@little-miracles.org) Received: from 203-206-67-174.dyn.iinet.net.au (HELO eternity.thanhandjared.net) ([203.206.67.174]) by mail-ihug.icp-qv1-irony2.iinet.net.au with ESMTP; 14 Sep 2006 16:34:45 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,162,1157299200"; d="scan'208"; a="631415187:sNHT16203476" Received: from [192.168.0.1] (seduction.thanhandjared.net [192.168.0.1]) by eternity.thanhandjared.net (Postfix) with ESMTP id 126E3B827; Thu, 14 Sep 2006 18:38:06 +1000 (EST) Message-ID: <45091426.2090709@little-miracles.org> Date: Thu, 14 Sep 2006 18:34:46 +1000 From: Jared Ring User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: Michael Butler References: <44FF4909.9020108@vwsoft.com> <44FF5B02.3090804@vwsoft.com> <44FF6FE6.4080602@protected-networks.net> In-Reply-To: <44FF6FE6.4080602@protected-networks.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: gmirror RAID-1: rebuilding freezes machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 08:34:50 -0000 I have cvsup'd today to make sure I get the updated g_mirror.c, have rebuilt world and kernel, installed both. however when i rebuild the degraded drive the same thing happens. during the rebuild the good drive is reading, but the dirty drive is not gettin written to according to gstat. all i have done is a gmirror remove gm0 ad0 after i realised what had happened, updated to the reverted version, gmirror insert gm0 ad0. the rebuild process began automatically. Am I missing something? Do i have to wipe and start again? This isnt a production machine, its still preproduction, but its supposed to be deployed in a week. Michael Butler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm backing out the attached change to see if it fixes it .. > > Michael > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFE/2/mQv9rrgRC1JIRArNYAJsEuTtrmig9bdW4aDQQ8W1May+EfQCfUjDQ > Xc1A9gUrrLS2jgbDP4xyC7I= > =5DtW > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------ > > Index: src/sys/geom/mirror/g_mirror.c > =================================================================== > RCS file: /usr/home/ncvs/src/sys/geom/mirror/g_mirror.c,v > retrieving revision 1.66.2.7 > retrieving revision 1.66.2.8 > diff -u -r1.66.2.7 -r1.66.2.8 > --- src/sys/geom/mirror/g_mirror.c 16 Jul 2006 15:47:46 -0000 1.66.2.7 > +++ src/sys/geom/mirror/g_mirror.c 4 Sep 2006 12:55:43 -0000 1.66.2.8 > @@ -1813,12 +1813,19 @@ > bioq_remove(&sc->sc_queue, bp); > mtx_unlock(&sc->sc_queue_mtx); > > - if ((bp->bio_cflags & G_MIRROR_BIO_FLAG_REGULAR) != 0) > - g_mirror_regular_request(bp); > - else if ((bp->bio_cflags & G_MIRROR_BIO_FLAG_SYNC) != 0) > - g_mirror_sync_request(bp); > - else > + if (bp->bio_to != sc->sc_provider) { > + if ((bp->bio_cflags & G_MIRROR_BIO_FLAG_REGULAR) != 0) > + g_mirror_regular_request(bp); > + else if ((bp->bio_cflags & G_MIRROR_BIO_FLAG_SYNC) != 0) > + g_mirror_sync_request(bp); > + else { > + KASSERT(0, > + ("Invalid request cflags=0x%hhx to=%s.", > + bp->bio_cflags, bp->bio_to->name)); > + } > + } else { > g_mirror_register_request(bp); > + } > G_MIRROR_DEBUG(5, "%s: I'm here 9.", __func__); > } > } > > > ------------------------------------------------------------------------ > > _______________________________________________ > 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 Sep 14 11:42: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 A0CE016A40F for ; Thu, 14 Sep 2006 11:42:33 +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 0AE7D43D49 for ; Thu, 14 Sep 2006 11:42:32 +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 AAE01C525; Thu, 14 Sep 2006 07:42:31 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 8577AC496; Thu, 14 Sep 2006 07:42:27 -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 16159C455; Thu, 14 Sep 2006 07:42:27 -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:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=Q5DgYWMdyE8RKRkYubuXnzAvvFY3t3a+sRpYWq59tJ/KLyhqQiEKZviCQsuyExL8FxTayhhrsdKibnAIkpnW1z97pPrlqdJFAbgK/k5HJOfBhYjNPa70wdeKE9Zhv6go; Received: from [192.168.1.10] (socker.hsd1.ma.comcast.net [24.218.145.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id B4BAEC454; Thu, 14 Sep 2006 07:42:26 -0400 (EDT) Message-ID: <45094021.70109@protected-networks.net> Date: Thu, 14 Sep 2006 07:42:25 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Jared Ring References: <44FF4909.9020108@vwsoft.com> <44FF5B02.3090804@vwsoft.com> <44FF6FE6.4080602@protected-networks.net> <45091426.2090709@little-miracles.org> In-Reply-To: <45091426.2090709@little-miracles.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: gmirror RAID-1: rebuilding freezes machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 11:42:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jared Ring wrote: | I have cvsup'd today to make sure I get the updated g_mirror.c, have | rebuilt world and kernel, installed both. however when i rebuild the | degraded drive the same thing happens. | | during the rebuild the good drive is reading, but the dirty drive is not | gettin written to according to gstat. I've been bitten by this - make sure that the first slice on the mirrored partition does not start at offset 0. For example, this disk is mirrored on slice 2 .. imb@aaron:/home/imb> sudo bsdlabel mirror/gm0s2 # /dev/mirror/gm0s2: 8 partitions: # size offset fstype [fsize bsize bps/cpg] ~ a: 524272 16 4.2BSD 2048 16384 32768 ~ ^^^^^^^ ~ c: 284655734 0 unused 0 0 # "raw" part .. ~ d: 1048576 524288 4.2BSD 0 0 0 ~ e: 1048576 1572864 4.2BSD 0 0 0 ~ f: 282034294 2621440 4.2BSD 0 0 0 Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCUAhQv9rrgRC1JIRAnPHAJ9AMnr1PzCfqJBx99zs6BhWSHI4NwCggUpo aI3LrwU8cHDmyLZpKB98EKw= =QPtF -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 11:43: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 24E0416A403 for ; Thu, 14 Sep 2006 11:43:15 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BFB743D45 for ; Thu, 14 Sep 2006 11:43:13 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (vuhupc@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8EBh7nn043026 for ; Thu, 14 Sep 2006 13:43:12 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8EBh7Tg043025; Thu, 14 Sep 2006 13:43:07 +0200 (CEST) (envelope-from olli) Date: Thu, 14 Sep 2006 13:43:07 +0200 (CEST) Message-Id: <200609141143.k8EBh7Tg043025@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: <20060914012316.V1031@ganymede.hub.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 14 Sep 2006 13:43:12 +0200 (CEST) Cc: Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! 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, 14 Sep 2006 11:43:15 -0000 Marc G. Fournier wrote: > Steve O'Hara-Smith wrote: > > Greg Barniskis wrote: > > > > > If you /track/ STABLE by frequently cvsupping it and rebuilding your > > > system, you will very likely encounter a serious problem sooner or > > > later. That's why tracking it is not recommended for production > > > systems. > > > > I did exactly that all the way from 2.0 to 4.11 on various machines > > without ever having any trouble. > > Ditto ... in fact, I do that on my desktop and have yet to hit a problem > ... -STABLE *is* generally very stable ... Same here. However, if you want (or need) to track stable, there are certain possibilities to avoid trouble. Of course watching the -stable mailing list (and possibly even -cvs-all) and reading /usr/src/UPDATING should be a "must". But there are more things that can be done. On important production machines, it might be a good idea to track -stable with some delay. For example, always update to the -stable date of 4 weeks ago (using the -D option of cvs, or the "date=" keyword of cvsup), after making sure that no critical problems have been reported in the mailing list in the past 4 weeks. Chances are that critical bugs are detected and fixed pretty quickly in the -stable branch. And of course: Always make sure that you have good backups. But that's even true if you don't track -stable. Best regards Oliver PS: Some people think that a RAID1 (mirror) is a substitute for a backup. It's not. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 12:44: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 6D93716A403 for ; Thu, 14 Sep 2006 12:44:23 +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 E7F6443D45 for ; Thu, 14 Sep 2006 12:44:22 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GNqZc-0005HZ-1I for freebsd-stable@freebsd.org; Thu, 14 Sep 2006 14:44:08 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Sep 2006 14:44:08 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Sep 2006 14:44:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Thu, 14 Sep 2006 14:43:24 +0200 Lines: 18 Message-ID: References: <4508DC51.4060300@gddsn.org.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: <4508DC51.4060300@gddsn.org.cn> Sender: news Subject: Re: FreeBSD does not use all cpus on top show. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 12:44:23 -0000 Huang wen hui wrote: > hi, > I have HP Server install FreeBSD 6.1R/amd64 with 2CPUs ,2 logical CPUs > per core. > On top show, It should show 4 cpus, but I never see 1 and 3 cpu on show. > Does anything I miss? This is a simplified version of things, but it will help you: CPUs 0 and 2 are "real" CPUs, while 1 and 3 are additional hyperthreaded "counterparts" of those. Since hyperthreading is disabled in FreeBSD by default (because it generally doesn't help performance and has a sort-of security hole in the hardware itself), processes are never scheduled to run on CPUs 1 and 3. You can either disable hyperthreading in BIOS, so you'll have only CPUs 0 and 1, or enable hyperthreading in FreeBSD with machdep.hyperthreading_allowed=1 sysctl, which will enable you to use all 4 logical CPUs. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 13: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 3D5F116A412 for ; Thu, 14 Sep 2006 13:32:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD88343D66 for ; Thu, 14 Sep 2006 13:32:36 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (pipknw@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k8EDWTer048255; Thu, 14 Sep 2006 15:32:35 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k8EDWTKa048254; Thu, 14 Sep 2006 15:32:29 +0200 (CEST) (envelope-from olli) Date: Thu, 14 Sep 2006 15:32:29 +0200 (CEST) Message-Id: <200609141332.k8EDWTKa048254@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, kline@sage.thought.org In-Reply-To: <20060913234934.GA92067@thought.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 14 Sep 2006 15:32:35 +0200 (CEST) Cc: Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, kline@sage.thought.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 13:32:40 -0000 Gary Kline wrote: > A couple of things. Will having gcc unroll loops have any > negative consequences? Yes. It will make the code slower, in most cases. In modern processors, the loop overhead is almost zero. That's because the "branch prediction unit" of a processor also predicts loop instructions (which are just a special case of conditional branches), and chances are that the whole loop body is in the L1 cache. If it is too large to fit into the L1 cache, then the loop overhead doesn't matter anyhow. There are very, very few special cases where unrolling a small loop might give a little speed improvement. Bit in most cases, it makes things worse. Also, don't expect miracles from -O3. It certainly won't make your kernel run twice as fast, and I even doubt that there would be any measurable difference. Therefore I'm not concerned at all that -O3 isn't officially supported. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "C++ is to C as Lung Cancer is to Lung." -- Thomas Funke From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 14:36: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 D0F8616A40F; Thu, 14 Sep 2006 14:36:24 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AC7743D49; Thu, 14 Sep 2006 14:36:24 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k8EEaN1R017157; Thu, 14 Sep 2006 09:36:23 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <450968E8.3000000@centtech.com> Date: Thu, 14 Sep 2006 09:36:24 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <44F7320E.6040608@centtech.com> <20060901111615.GB1819@garage.freebsd.pl> <44F831B7.90807@centtech.com> <20060901145939.GC1819@garage.freebsd.pl> <44F84EB9.6000006@centtech.com> <20060901185637.GA6759@garage.freebsd.pl> In-Reply-To: <20060901185637.GA6759@garage.freebsd.pl> X-Virus-Scanned: ClamAV 0.87.1/1882/Thu Sep 14 06:04:02 2006 on mh2.centtech.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@FreeBSD.org Subject: Re: gjournal questions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 14:36:24 -0000 it's working great now that i've redone the whole thing ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com Pawel Jakub Dawidek wrote the following on 09/01/06 13:56: > On Fri, Sep 01, 2006 at 10:16:09AM -0500, Kevin Kramer wrote: > >> I've already redone the whole thing. here are the steps i took >> >> umount /scr09 >> umount /scr10 >> gjournal stop da2.journal >> gjournal stop da4.journal >> >> ** had not done this on the first attempt >> newfs /dev/da1 >> newfs /dev/da3 >> > > This is not needed. > > >> gjournal label -v /dev/da2 /dev/da1 >> gjournal label -v /dev/da4 /dev/da3 >> >> newfs -J -L scr09 /dev/da2.journal >> newfs -J -L scr10 /dev/da4.journal >> >> mount /scr09 >> mount /scr10 >> > > Don't know how your /etc/fstab looks like, but you definiately should > use 'async' mount option, which is safe to use with gjournaled file > systems. > > >> it is looking much better so far. before, i was getting this in the debug (only on /scr10) and my mountd process was always the top process >> >> Sep 1 00:00:11 donkey kernel: fsync: giving up on dirty >> Sep 1 00:00:11 donkey kernel: 0xc9ee1bb0: tag devfs, type VCHR >> Sep 1 00:00:11 donkey kernel: usecount 1, writecount 0, refcount 198 mountedher >> e 0xc9ebfb00 >> Sep 1 00:00:11 donkey kernel: flags () >> Sep 1 00:00:11 donkey kernel: v_object 0xc9fbb528 ref 0 pages 5933 >> Sep 1 00:00:11 donkey kernel: lock type devfs: EXCL (count 1) by thread 0xc9bd4 >> 180 (pid 38) >> Sep 1 00:00:11 donkey kernel: dev ufs/scr10 >> Sep 1 00:00:11 donkey kernel: GEOM_JOURNAL: Cannot suspend file system /scr10 ( >> error=35). >> > > It happens sometimes under load, haven't investigated yet what exactly > is happening, but you can ignore it for now, it's harmless, it just > means journal switch will be done a bit later. > > BTW. 8GB for journals is much. You should not need more than 2GB > probably. Of course it will work with 8GB just fine. > > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 14:46: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 BEBEB16A403 for ; Thu, 14 Sep 2006 14:46:12 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57E1D43D67 for ; Thu, 14 Sep 2006 14:46:04 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k8EEk3tv079510 for ; Thu, 14 Sep 2006 09:46:03 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <45096B2C.5010907@centtech.com> Date: Thu, 14 Sep 2006 09:46:04 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1882/Thu Sep 14 06:04:02 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: Dell Precision 390 issues (heads-up) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 14:46:12 -0000 We have one of these new boxes. The latest ISOs for i386/AMD64 install fails with a RAM Parity error if the onboard Broadcom NIC is enabled in the BIOS. To get past this error just disable in the bios to get past. I'll repost after I do a source update to see if the Broadcom is supported. -- ------------------------------ Kevin Kramer Sr. Systems Administrator 512.418.5725 Centaur Technology, Inc. www.centtech.com From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 15:44: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 8E85D16A412 for ; Thu, 14 Sep 2006 15:44:14 +0000 (UTC) (envelope-from jsbowden@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14C6343D73 for ; Thu, 14 Sep 2006 15:44:13 +0000 (GMT) (envelope-from jsbowden@gmail.com) Received: by wr-out-0506.google.com with SMTP id 71so904074wri for ; Thu, 14 Sep 2006 08:44:13 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=jJhOsEhBxVHEvN92uoMUGKixy1F+FftmR9MEh6HvqB/Rdhnah+M95vLi/nZxQDYPI6tLhqH4kZkwmeA9Gliym3+xbQjQ9PZYiBtIRx58HoLXAjMct+metdMuWrzSX4RaoxvoKLW4cN/QHNaElBGY8w6eDRn4vIj1ML+QE6+qkts= Received: by 10.66.222.9 with SMTP id u9mr4870079ugg; Thu, 14 Sep 2006 08:44:12 -0700 (PDT) Received: by 10.66.243.6 with HTTP; Thu, 14 Sep 2006 08:44:12 -0700 (PDT) Message-ID: Date: Thu, 14 Sep 2006 11:44:12 -0400 From: "Jamie Bowden" Sender: jsbowden@gmail.com To: freebsd-stable@freebsd.org In-Reply-To: <200609100159.k8A1xAIn089481@drugs.dv.isc.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> X-Google-Sender-Auth: 01fefeb45e014f2e Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 15:44:14 -0000 On 9/9/06, Mark Andrews wrote: > > Yeah, -STABLE is what you should run if you want stable code, right? > No. STABLE means STABLE API. > If you want stable code you run releases. Between releases > stable can become unstable. Think of stable as permanent > BETA code. Changes have passed the first level of testing > in current which is permanent ALPHA code. No, this is what it means now. I've been running FreeBSD since 1.1, and -STABLE used to mean exactly that. The developement branch was -C, and -S was where things went after extensive testing. You were not allowed to break -S or Jordan would rip your fingers off. This change to the current structure wasn't meant to be permanent when it was done (between 4 and 5, IIRC), and was only done out of necessity because the changes across that major release were huge. FreeBSD needs an interim track that mirrors what -STABLE used to be, which is a track between point releases that can be relied upon (and RELEASE_x_y doesn't work, since it only addresses security and bugs deemed worthy, which most aren't). -- Jamie Bowden -- "It was half way to Rivendell when the drugs began to take hold" Hunter S Tolkien "Fear and Loathing in Barad Dur" Iain Bowen From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 16:28: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 404AB16A47B for ; Thu, 14 Sep 2006 16:28:03 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FF6543D6D for ; Thu, 14 Sep 2006 16:27:57 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so1176482nzn for ; Thu, 14 Sep 2006 09:27:56 -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:content-transfer-encoding; b=AJkXzV3ngaKBNkPCjAveNYAqh+GxXSJr1IlagjJWaNkReTDW/TVdRRWi51BkNe+As5/zixMuzOB8KILuflLskTq8QKcf16IiqonjbCWKpjDwJ6yJxj9S6CMX+ssAhd/0AKLjMsEt4aM66BvBacqUZOwdHIgUNa3Q04GvmIC8UEU= Received: by 10.64.149.15 with SMTP id w15mr7684453qbd; Thu, 14 Sep 2006 09:27:56 -0700 (PDT) Received: from sauron.lan.box ( [201.3.138.45]) by mx.gmail.com with ESMTP id e15sm7886897qba.2006.09.14.09.27.55; Thu, 14 Sep 2006 09:27:56 -0700 (PDT) Date: Thu, 14 Sep 2006 13:27:51 -0300 From: Ricardo Nabinger Sanchez To: freebsd-stable@freebsd.org Message-Id: <20060914132751.72c76a72.rnsanchez@gmail.com> In-Reply-To: <20060914044241.GA92358@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> <0B8BF03E-8F4A-4279-850B-2EA7FF5E1B89@mac.com> <20060914044241.GA92358@thought.org> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 16:28:03 -0000 On Wed, 13 Sep 2006 21:42:41 -0700, Gary Kline wrote: > Isn't the compiler intelligent enough to have a reasonable > limit, N, of the loops it will unroll to ensure a faster runtime? Yes, and also permits the user to choose if internal heuristics should be used, user-specified loop size to unroll, and unroll-all-loops. -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 16: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 328BF16A403 for ; Thu, 14 Sep 2006 16:36:39 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 048A243D6E for ; Thu, 14 Sep 2006 16:36:37 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so117597uge for ; Thu, 14 Sep 2006 09:36:37 -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:content-transfer-encoding; b=X6lr4K8A2iKaP2X/ncp2Q9iov4X308TS6ZIZPr6/R5q4uM68CrEuj0ox9+P59mn3NF1RNNcmG8MaBNRNCShW/8AkQaJ8KwfF9ACx+zV3IY+XorfHKUEnxVuGbzv4HI6XgYbqNtbdhvvzqKwcRW8WuMfBtrIVFQULdbxYt5+J7gI= Received: by 10.65.211.13 with SMTP id n13mr7703779qbq; Thu, 14 Sep 2006 09:36:36 -0700 (PDT) Received: from sauron.lan.box ( [201.3.138.45]) by mx.gmail.com with ESMTP id e18sm8917028qba.2006.09.14.09.36.34; Thu, 14 Sep 2006 09:36:35 -0700 (PDT) Date: Thu, 14 Sep 2006 13:36:30 -0300 From: Ricardo Nabinger Sanchez To: freebsd-stable@freebsd.org Message-Id: <20060914133630.8387f936.rnsanchez@gmail.com> In-Reply-To: <1158215254.2889.49.camel@elbereth.gateway.2wire.net> References: <1158215254.2889.49.camel@elbereth.gateway.2wire.net> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Thanks! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 16:36:39 -0000 On Thu, 14 Sep 2006 01:27:34 -0500, "Charles P. Schaum" wrote: > I am real happy with FreeBSD. I would be interested in seeing more > desktop stuff become a reality. Neither of the desktop variants of > FreeBSD works so well for me, yet. Have you tried Desktop BSD and/or PCBSD? IIRC, they're based on FreeBSD and very desktop oriented -- perhaps they'll work well for you. -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 16:45: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 7B8EF16A403 for ; Thu, 14 Sep 2006 16:45:46 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10F9F43D6B for ; Thu, 14 Sep 2006 16:45:46 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout12/MantshX 4.0) with ESMTP id k8EGjj2s017395; Thu, 14 Sep 2006 09:45:45 -0700 (PDT) Received: from [17.214.13.96] (a17-214-13-96.apple.com [17.214.13.96]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id k8EGjho9014519; Thu, 14 Sep 2006 09:45:44 -0700 (PDT) In-Reply-To: <20060914044241.GA92358@thought.org> References: <200609130905.k8D95idk062789@lurza.secnetix.de> <4507CC9B.60704@sun-fish.com> <20060913234934.GA92067@thought.org> <0B8BF03E-8F4A-4279-850B-2EA7FF5E1B89@mac.com> <20060914044241.GA92358@thought.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <549CD0AC-2CED-4112-B708-5F4FB1DA69D2@mac.com> Content-Transfer-Encoding: 7bit From: Chuck Swiger Date: Thu, 14 Sep 2006 09:45:42 -0700 To: Gary Kline X-Mailer: Apple Mail (2.752.2) X-Brightmail-Tracker: AAAAAQAAA+k= X-Language-Identified: TRUE Cc: freebsd-stable Subject: Re: optimization levels for 6-STABLE build{kernel,world} X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 16:45:46 -0000 On Sep 13, 2006, at 9:42 PM, Gary Kline wrote: >> -funroll-loops is as likely to decrease performance for a particular >> program as it is to help. > > Isn't the compiler intelligent enough to have a reasonable > limit, N, of the loops it will unroll to ensure a faster runtime? > Something much less than 1000, say; possibly less than 100. Of course; in fact, N is probably closer to 4 or 8 than it is to 100. > At least, if the initializiation and end-loop code *plus* the > loop code itself were too large for the cache, my thought is that > gcc would back out. Unless you've indicated that the compiler should target a specific CPU architecture, there is no way for it to know whether the size of the L1 cache on the machine doing the compile is the same as, or even similar to the size of the system where the code will run. > I may be giving RMS too much credit; but > if memory serves, thed compiler was GNU's first project. And > Stallman was into GOFAI, &c, for better/worse.[1] Anyway, for now > I'll comment out the unroll-loops arg. cd /usr/src/contrib/gcc && grep Stallman ChangeLog ...returns no results. A tool I wrote suggests: % histogram.py -F' ' -f 2,3 -p @ -c 10 ChangeLog 61 Kazu Hirata 51 Eric Botcazou 48 Jan Hubicka 39 Richard Sandiford 37 Alan Modra 30 Richard Henderson 29 Joseph S. Myers 27 Jakub Jelinek 25 Zack Weinberg 22 Mark Mitchell 20 John David Anglin 20 Ulrich Weigand 17 Rainer Orth 16 Kelley Cook 16 Roger Sayle 13 David Edelsohn 12 Aldy Hernandez 11 Stephane Carrez 11 Ian Lance Taylor 10 Andrew Pinski 10 Kaz Kojima 10 James E Wilson >> A safe optimizer must assume that an arbitrary assignment via a >> pointer dereference can change any value in memory, which means that >> you have to spill and reload any data being cached in CPU registers >> around the use of the pointer, except for const's, variables declared >> as "register", and possibly function arguments being passed via >> registers and not on the stack (cf "register windows" on the SPARC >> hardware, or HP/PA's calling conventions). > > Well, I'd added the no-strict-aliasing flag to make.conf! > Pointers give me indigestion ... even after all these years. > Thanks for your insights. And the URL. You're welcome. > gary > > [1]. Seems to me that "good old-fashioned AI" techniques would work in > something like a compiler where you probblyhave a good idea of > most heuristics. -gk Of course. The compiler enables those optimizations with -O or -O2 which are almost certain to result in beneficial improvements to performance and code size, most of the time. Potential optimizations which are not helpful on average are not enabled by default, until the situations where they are known to be useful can be identified by the compiler at compile-time. Using non-default optimization options isn't like discovering buried treasure that nobody else was aware of; the options aren't enabled by default for good reason(s), usually because the tradeoffs they make aren't helpful in general (yet), or because their usage has known bugs which result in faulty executables being produced. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 16:55: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 39E4616A403; Thu, 14 Sep 2006 16:55:37 +0000 (UTC) (envelope-from rabe@p-i-n.com) Received: from dns.p-i-n.com (dns.p-i-n.com [145.253.185.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAE5F43D6D; Thu, 14 Sep 2006 16:55:26 +0000 (GMT) (envelope-from rabe@p-i-n.com) Received: from p-i-n.com (pinserv2.p-i-n.com [10.101.240.52]) by dns.p-i-n.com (8.12.9p2/8.12.9) with ESMTP id k8EGtOgM095102; Thu, 14 Sep 2006 18:55:24 +0200 (CEST) (envelope-from rabe@p-i-n.com) Received: from pinserv2.p-i-n.com (localhost.p-i-n.com [127.0.0.1]) by p-i-n.com (8.13.6/8.13.6) with ESMTP id k8EGtOaq032940; Thu, 14 Sep 2006 18:55:24 +0200 (CEST) (envelope-from rabe@pinserv2.p-i-n.com) Received: (from rabe@localhost) by pinserv2.p-i-n.com (8.13.6/8.13.6/Submit) id k8EGtOuV032939; Thu, 14 Sep 2006 18:55:24 +0200 (CEST) (envelope-from rabe) Date: Thu, 14 Sep 2006 18:55:24 +0200 From: "Raphael H. Becker" To: freebsd-stable@freebsd.org Message-ID: <20060914165523.GA31808@p-i-n.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Organization: PHOENIX Pharmahandel AG & Co KG, Mannheim, Deutschland Cc: freebsd-amd64@freebsd.org Subject: 6.2-PRE/amd64: make installworld fails: btxld:No such file or directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 16:55:37 -0000 Hi * today i checked out fresh RELENG_6 on my amd64, build(world|kernel) seems fine, installworld fails: [...] ===> sys/boot/i386/btx (install) ===> sys/boot/i386/btx/btx (install) ===> sys/boot/i386/btx/btxldr (install) ===> sys/boot/i386/btx/lib (install) ===> sys/boot/i386/boot2 (install) btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 [...] I found an unanswered question about this: http://lists.freebsd.org/pipermail/freebsd-amd64/2004-August/001906.html Why i386 here: "boot/i386/boot2/"? I did the following procedure: 1) install new Dell PE2950 with amd64/6.1-RELEASE from CD (minimal) 2) cvsup /usr/src to RELENG_6 this afternoon 3) make clean buildworld buildkernel (forgot to build it for SMP) 4) make buildkernel KERNCONF=PE2950 (which is just SMP plus ident a.t.m) 5) make installkernel KERNCONF=PE2950 6) reboot 7) make installworld --> fails. Did I miss something here? How to fix? Is this amd64 specific? Regards Raphael Becker PS: if this is an amd64 specific issue it might be forwarded to the amd64 mailing list. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 17:48: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 2743316A407 for ; Thu, 14 Sep 2006 17:48:52 +0000 (UTC) (envelope-from kramer@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20B0943D96 for ; Thu, 14 Sep 2006 17:48:40 +0000 (GMT) (envelope-from kramer@centtech.com) Received: from [10.177.171.221] (roddick.centtech.com [10.177.171.221]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k8EHmdho009778 for ; Thu, 14 Sep 2006 12:48:39 -0500 (CDT) (envelope-from kramer@centtech.com) Message-ID: <450995F5.3000804@centtech.com> Date: Thu, 14 Sep 2006 12:48:37 -0500 From: Kevin Kramer User-Agent: Thunderbird 1.5.0.5 (X11/20060802) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <45096B2C.5010907@centtech.com> In-Reply-To: <45096B2C.5010907@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1882/Thu Sep 14 06:04:02 2006 on mh1.centtech.com X-Virus-Status: Clean Subject: Re: Dell Precision 390 issues (heads-up) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kramer@centtech.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 17:48:52 -0000 Well, I've cvs'd this morning and rebuilt world and kernel and the Broadcom nic driver still panics the machine. The device is identified as BCM5787 and immediately after it loads the kernel gives RAM Parity Error some other suff like a trace panic , non-maskable interrupt trap it now shows 6.2-pre-release as the version. what can i do to help fix this and maybe get this into 6.2. thanks Kevin Kramer wrote the following on 09/14/06 09:46: > We have one of these new boxes. The latest ISOs for i386/AMD64 install > fails with a RAM Parity error if the onboard Broadcom NIC is enabled > in the BIOS. To get past this error just disable in the bios to get > past. I'll repost after I do a source update to see if the Broadcom is > supported. > From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 17:50: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 16AD716A415; Thu, 14 Sep 2006 17:50:55 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A22A43D7E; Thu, 14 Sep 2006 17:50:51 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id F35E62A576; Thu, 14 Sep 2006 14:50:49 -0300 (BRT) Date: Thu, 14 Sep 2006 14:50:49 -0300 From: Marcelo Gardini do Amaral To: Robert Watson Message-ID: <20060914175049.GH49126@registro.br> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060913182457.W50147@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 17:50:55 -0000 > >Are you able to boot a 7.x kernel on this box? An as yet un-MFC'd > >optimization to the UDP send path is present in the 7.x kernel, suggested > >by ISC, which significantly improves threaded BIND9 performance. I've not > >benchmarked unthreaded BIND9 with the change. If you want to test > >specifically the before/after case for that change, you can find the > >reference to sosend_dgram in src/sys/netinet/udp_usrreq.c and swap it to > >sosend, which restores the old behavior. I booted 7.x kernel UP and SMP on my blade. When I swaped both of them to sosend I got a panic to any DNS query: # dig @localhost test1.foo.bar panic: sosend: protocol calls sosend KDB: enter: panic [thread pid 671 tid 100053 ] Stopped at kdb_enter+0x2b: nop db> db> bt Tracing pid 671 tid 100053 td 0xc4a52bd0 kdb_enter(c091d7b6) at kdb_enter+0x2b panic(c0925143,e502dc10,c06e6511,c4f9c14c,c4a66370,...) at panic+0xbb sosend(c4f9c14c,c4a66370,e502dbe4,0,0,0,c4a52bd0) at sosend+0x1f kern_sendit(c4a52bd0,15,e502dc5c,0,0,0) at kern_sendit+0x101 sendit(c4a52bd0,15,e502dc5c,0,c4a66150,...) at sendit+0x87 sendmsg(c4a52bd0,e502dd04) at sendmsg+0x53 syscall(3b,3b,3b,1,0,...) at syscall+0x256 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (28, FreeBSD ELF32, sendmsg), eip = 0x28353d6f, esp = 0xbfbfe8ec, eb p = 0xbfbfea68 --- db> c Uptime: 1m44s Physical memory: 2039 MB Dumping 99 MB: 84 68 52 36 20 4 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort > The other common optimization advice that you may already have received is > to check which time counter FreeBSD has selected. Right now, 6.x/7.x err > on the side of accurate over fast. There's been quite a bit of debate > about this approach, and it's useful to investigate the issue. You can > view and set the current choice by looking at the sysctl > kern.timecounter.hardware, and you can see the choices on your hardware by > looking at kern.timecounter.choice. Typically, TSC is the fastest, but may > suffer from drift as the CPU changes speed (as a result of temperature, > power saving, etc). Set it to TSC if it's not already TSC, and see what > the effect is. As many event libraries read time stamps frequently to set > up sleeping in user space, it can have a substantial performance impact. With the 7.x kernel and no changes in src/sys/netinet/udp_usrreq.c I tried different timecounters and I couldn't see any performance difference. Here we see the results for bind 9.3.2, same zone file and queries: Kernel UP Timecounter queries/s ----------- --------- ACPI-safe 16200 TSC 16584 i8254 16319 Kernel SMP Timecounter queries/s ----------- --------- ACPI-safe 15323 TSC 15930 i8254 14155 Any other tip? -- Att., Marcelo Gardini From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 19:02: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 3C7C416A49E for ; Thu, 14 Sep 2006 19:02:37 +0000 (UTC) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de (mail.smartterra.de [195.225.132.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id B91EA43D4C for ; Thu, 14 Sep 2006 19:02:36 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de ([195.225.132.203]) by localhost (liberty-mail [195.225.132.203]) (amavisd-new, port 10024) with ESMTP id 95299-03; Thu, 14 Sep 2006 21:02:46 +0200 (CEST) Received: from smtp.alpha-tierchen.de (port-212-202-42-252.dynamic.qsc.de [212.202.42.252]) by mail.liberty-hosting.de (Postfix) with ESMTP id 75D5B160186; Thu, 14 Sep 2006 21:02:46 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by smtp.alpha-tierchen.de (Postfix) with ESMTP id A9A6452861; Thu, 14 Sep 2006 21:02:31 +0200 (CEST) Message-ID: <4509A74C.5060507@cs.tu-berlin.de> Date: Thu, 14 Sep 2006 21:02:36 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Vivek Khera , hackmiester@hackmiester.com References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <6AF9F647-881A-448F-933C-743D295400B3@khera.org> In-Reply-To: <6AF9F647-881A-448F-933C-743D295400B3@khera.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mail.smartterra.de Cc: freebsd-stable Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 19:02:37 -0000 Vivek Khera schrieb: > > On Sep 12, 2006, at 6:23 PM, hackmiester (Hunter Fuller) wrote: > >>> -STABLE is still a development branch without guarantee of a stable >>> and working operating system. >> >> >> Hahahahaha... That's ironic... > > > No, just misinterpretation of which attribute of the system to which > the word "stable" applies. > Do you really think I misinterpreted the meaning of -STABLE? *I* think most people misinterprete -STABLE because the first thing that comes to mind is runtime stability. The same issue exists in the GNU/Debian Linux world: Debian stable doesn't mean that the system run always rock-solid and works perfectly, but rather the state of software is stable, i.e. maintainers ensure 100% compatibility between updates. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 19:05: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 560D216A407 for ; Thu, 14 Sep 2006 19:05:19 +0000 (UTC) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de (mail.liberty-hosting.de [195.225.132.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26C3E43D46 for ; Thu, 14 Sep 2006 19:05:16 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de ([195.225.132.203]) by localhost (liberty-mail [195.225.132.203]) (amavisd-new, port 10024) with ESMTP id 95274-08; Thu, 14 Sep 2006 21:05:27 +0200 (CEST) Received: from smtp.alpha-tierchen.de (port-212-202-42-252.dynamic.qsc.de [212.202.42.252]) by mail.liberty-hosting.de (Postfix) with ESMTP id 46F7415DAD6; Thu, 14 Sep 2006 21:05:27 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by smtp.alpha-tierchen.de (Postfix) with ESMTP id 91B7852861; Thu, 14 Sep 2006 21:05:12 +0200 (CEST) Message-ID: <4509A7ED.4090701@cs.tu-berlin.de> Date: Thu, 14 Sep 2006 21:05:17 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "hackmiester (Hunter Fuller)" References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mail.smartterra.de Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 19:05:19 -0000 hackmiester (Hunter Fuller) schrieb: > > On 12 September 2006, at 02:06, Björn König wrote: > >> Karl Denninger schrieb: >> >>> This is not cool folks. >> >> >> I think you misunderstood what -STABLE means. (Or maybe I do?) >> >> -STABLE is still a development branch without guarantee of a stable >> and working operating system. > > > Hahahahaha... That's ironic... That wasn't meant to be ironic. Years of experience and observations of development lead to this conclusion. Regards Björn From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 20:27: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 E4C9316A403 for ; Thu, 14 Sep 2006 20:27:05 +0000 (UTC) (envelope-from jared@little-miracles.org) Received: from mail-ihug.icp-qv1-irony1.iinet.net.au (ihug-mail.icp-qv1-irony1.iinet.net.au [203.59.1.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35EC343D45 for ; Thu, 14 Sep 2006 20:27:04 +0000 (GMT) (envelope-from jared@little-miracles.org) Received: from 203-206-67-174.dyn.iinet.net.au (HELO eternity.thanhandjared.net) ([203.206.67.174]) by mail-ihug.icp-qv1-irony1.iinet.net.au with ESMTP; 15 Sep 2006 04:27:03 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,166,1157299200"; d="scan'208"; a="644578295:sNHT22317328" Received: from [192.168.0.1] (seduction.thanhandjared.net [192.168.0.1]) by eternity.thanhandjared.net (Postfix) with ESMTP id 64BD2B827; Fri, 15 Sep 2006 06:30:24 +1000 (EST) Message-ID: <4509BB15.3020105@little-miracles.org> Date: Fri, 15 Sep 2006 06:27:01 +1000 From: Jared Ring User-Agent: Thunderbird 1.5.0.5 (X11/20060728) MIME-Version: 1.0 To: Michael Butler References: <44FF4909.9020108@vwsoft.com> <44FF5B02.3090804@vwsoft.com> <44FF6FE6.4080602@protected-networks.net> <45091426.2090709@little-miracles.org> <45094021.70109@protected-networks.net> In-Reply-To: <45094021.70109@protected-networks.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: gmirror RAID-1: rebuilding freezes machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 20:27:06 -0000 I traced the problem back to BIOS booting off ad0 instead of ad1. Because ad0 was still a perfectly functioning drive BIOS didnt complain about booting off it. Once the kernel started and gmirror loaded it proceeded to use ad1, but the kernel was loaded from ad0, which was the old, broken one. I noticed my first partition does start at offset 0 though, is this going to come and bite me in the future? J Michael Butler wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jared Ring wrote: > | I have cvsup'd today to make sure I get the updated g_mirror.c, have > | rebuilt world and kernel, installed both. however when i rebuild the > | degraded drive the same thing happens. > | > | during the rebuild the good drive is reading, but the dirty drive is not > | gettin written to according to gstat. > > I've been bitten by this - make sure that the first slice on the > mirrored partition does not start at offset 0. > > For example, this disk is mirrored on slice 2 .. > > imb@aaron:/home/imb> sudo bsdlabel mirror/gm0s2 > # /dev/mirror/gm0s2: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > ~ a: 524272 16 4.2BSD 2048 16384 32768 > ~ ^^^^^^^ > ~ c: 284655734 0 unused 0 0 # "raw" part .. > ~ d: 1048576 524288 4.2BSD 0 0 0 > ~ e: 1048576 1572864 4.2BSD 0 0 0 > ~ f: 282034294 2621440 4.2BSD 0 0 0 > > Michael > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFCUAhQv9rrgRC1JIRAnPHAJ9AMnr1PzCfqJBx99zs6BhWSHI4NwCggUpo > aI3LrwU8cHDmyLZpKB98EKw= > =QPtF > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Sep 14 20:32: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 CFCE316A403 for ; Thu, 14 Sep 2006 20:32:50 +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 49B4643D46 for ; Thu, 14 Sep 2006 20:32:50 +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 25932C4C6; Thu, 14 Sep 2006 16:32:49 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 42524C496; Thu, 14 Sep 2006 16:32:45 -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 C8165C455; Thu, 14 Sep 2006 16:32:44 -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:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=i4MF4NLYv4D6ImkkzDTXJ0edqJgiCY/ya2vGMivCuvHb7QZFdEj8SPA7LcF8cYv1+Z2IUx7DPDRu4HGFYYImJbGLVeS/uY8PgUEVFlE3WJmrkRZ+i0jTNnaDQ2rlhHAo; Received: from [192.168.1.10] (socker.hsd1.ma.comcast.net [24.218.145.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by aaron.protected-networks.net (Postfix) with ESMTP id 6A4C7C454; Thu, 14 Sep 2006 16:32:44 -0400 (EDT) Message-ID: <4509BC6B.3080501@protected-networks.net> Date: Thu, 14 Sep 2006 16:32:43 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.7 (X11/20060914) MIME-Version: 1.0 To: Jared Ring References: <44FF4909.9020108@vwsoft.com> <44FF5B02.3090804@vwsoft.com> <44FF6FE6.4080602@protected-networks.net> <45091426.2090709@little-miracles.org> <45094021.70109@protected-networks.net> <4509BB15.3020105@little-miracles.org> In-Reply-To: <4509BB15.3020105@little-miracles.org> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: gmirror RAID-1: rebuilding freezes machine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 20:32:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jared Ring wrote: > I traced the problem back to BIOS booting off ad0 instead of ad1. > Because ad0 was still a perfectly functioning drive BIOS didnt complain > about booting off it. Once the kernel started and gmirror loaded it > proceeded to use ad1, but the kernel was loaded from ad0, which was the > old, broken one. Ah .. that'll do it .. > I noticed my first partition does start at offset 0 though, is this > going to come and bite me in the future? My guess is 'yes, it will eventually' .. better to fix it now before it does and you've forgotten about it, Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCbxrQv9rrgRC1JIRAk6MAJ9xPYkp0Vr7T38Qf1SMQ3pYtP3v2QCfdzs5 57tFy03R0Zv8AzKsHR0mpv4= =XK+M -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 20:45: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 B046216A40F; Thu, 14 Sep 2006 20:45:07 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B1EC43D5F; Thu, 14 Sep 2006 20:44:58 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 0D4745D72; Fri, 15 Sep 2006 00:44:58 +0400 (MSD) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id E03AC5DC6; Fri, 15 Sep 2006 00:44:57 +0400 (MSD) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id k8EKj2Em083508; Fri, 15 Sep 2006 00:45:02 +0400 (MSD) (envelope-from ru) Date: Fri, 15 Sep 2006 00:45:02 +0400 From: Ruslan Ermilov To: "Raphael H. Becker" Message-ID: <20060914204502.GC83387@rambler-co.ru> References: <20060914165523.GA31808@p-i-n.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline In-Reply-To: <20060914165523.GA31808@p-i-n.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: 6.2-PRE/amd64: make installworld fails: btxld:No such file or directory X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 20:45:07 -0000 --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 14, 2006 at 06:55:24PM +0200, Raphael H. Becker wrote: >=20 > Hi * >=20 > today i checked out fresh RELENG_6 on my amd64, build(world|kernel) > seems fine, installworld fails: >=20 > [...] > =3D=3D=3D> sys/boot/i386/btx (install) > =3D=3D=3D> sys/boot/i386/btx/btx (install) > =3D=3D=3D> sys/boot/i386/btx/btxldr (install) > =3D=3D=3D> sys/boot/i386/btx/lib (install) > =3D=3D=3D> sys/boot/i386/boot2 (install) > btxld -v -E 0x2000 -f bin -b > /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot= 2.ld -P 1 boot2.bin > btxld:No such file or directory > *** Error code 1 >=20 > Stop in /usr/src/sys/boot/i386/boot2. > *** Error code 1 > [...] >=20 It's trying to build things at an inappropriate time (install phase), hence the error. > Why i386 here: "boot/i386/boot2/"? >=20 amd64 shares the boot code with i386. > I did the following procedure: >=20 > 1) install new Dell PE2950 with amd64/6.1-RELEASE from CD (minimal) > 2) cvsup /usr/src to RELENG_6 this afternoon > 3) make clean buildworld buildkernel > (forgot to build it for SMP) > 4) make buildkernel KERNCONF=3DPE2950 (which is just SMP plus ident a.t.m) > 5) make installkernel KERNCONF=3DPE2950 > 6) reboot > 7) make installworld --> fails. >=20 > Did I miss something here? >=20 > How to fix? >=20 1) Check that your date/time is correct during the build. 2) Check that your date/time is correct during the install (perhaps missed "adjkerntz -i" after rebooting into SU?) 3) Check that /usr/src doesn't have files from the future. > Is this amd64 specific? >=20 No. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCb9OqRfpzJluFF4RAplsAJ4gBxh3SrBQrtUDtCAgxHTOStOV3QCdEe2G 9Xt2j6TRMAdwaIvcOplQ72I= =1kUa -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 20:53: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 2117416A40F for ; Thu, 14 Sep 2006 20:53:02 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from virtual.micronet.sk (smtp.micronet.sk [84.16.32.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA38543D45 for ; Thu, 14 Sep 2006 20:53:01 +0000 (GMT) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id E511810E639; Thu, 14 Sep 2006 22:52:38 +0200 (CEST) X-Virus-Scanned: by amavisd-new at virtual.micronet.sk Received: from virtual.micronet.sk ([127.0.0.1]) by localhost (virtual.micronet.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6IWyT6xfCTe; Thu, 14 Sep 2006 22:52:37 +0200 (CEST) Received: from danger.mcrn.sk (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id 0749410E5DD; Thu, 14 Sep 2006 22:52:37 +0200 (CEST) Date: Thu, 14 Sep 2006 22:52:58 +0200 From: Daniel Gerzo Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <492332980.20060914225258@rulez.sk> To: Jonathan Stewart In-Reply-To: <450752F6.4050109@kc8onw.net> References: <450752F6.4050109@kc8onw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Sep 2006 20:53:02 -0000 Hello Jonathan, Wednesday, September 13, 2006, 2:38:14 AM, you wrote: > I set up a new server recently and transferred all the information from > my old server over. I tried to use unison to synchronize the backup of > pictures I have taken and noticed that a large number of pictures where > marked as changed on the server. After checking the pictures by hand I > confirmed that many of the pictures on the server were corrupted. > It appears the corruption happens during the read process because when I > recompare the files in a graphical diff tool between cache flushes the > differences move around!?!?!? The differences also appear to be very > small for the most part, single bytes scattered throughout the file. I > really have no idea what is causing the problem and would like to pin it > down so I can either replace hardware if it's bad or fix whatever the > bug is. > CPU: AMD Athlon(tm) XP 3200+ (2090.16-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 I saw very similar simptons on p4 3.2ghz. I was able to build world without any problems and the overall stability of the machine was completely good, but when I tried to install some ports, the md5 sums didn't match the source and I was sure that they were all right. The following simple test demonstrates the problem I was hitting: root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = b95ddf27bc0ffa379c9aa881ca39e92a7d79e0d08999b4dff6d7d9547ee2a72d root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = 71432841b3965b7ab2d83f0dc7c3049195ea4e9267a8dc2d825a8a0466982930 root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = 83e44f5301b3270e821850164c74d275f6721bed5d126480cf518a9fe5ca0d6c root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz bd8c2e593e1fa4b01fd98eaf016329bb root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz bd8c2e593e1fa4b01fd98eaf016329bb root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz b9342bb213393238dd37322d4e2ee3fe root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz 88efa7977fd3febaa8d260e3d5f21917 The memtest didn't show any problems with RAM and we were unable to clarify what is really going on. Then we managed to get the machine replaced with the complete new hardware and the problem was gone. Later, I was told that it is some kind of known bug in older p4's bioses (and advised to update the bios which should have been fixed in the meantime) but we were unable to find out any information about the problem. Fortunately the colo company replaced the hardware with no problems. So long so good and the box is running flawlessly. -- Best regards, Daniel mailto:danger@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 21:50: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 B2A1716A403 for ; Thu, 14 Sep 2006 21:50:55 +0000 (UTC) (envelope-from mahmoh@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83D5143D49 for ; Thu, 14 Sep 2006 21:50:52 +0000 (GMT) (envelope-from mahmoh@gmail.com) Received: by ug-out-1314.google.com with SMTP id m2so140728uge for ; Thu, 14 Sep 2006 14:50:50 -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=WmzJqdLTL7xIdcgQAFTJVrgxd8FoojMgbqcpY931LeUjPOmX0ycBGibv9CHdMPL5pQaabHcGZN9E3XlUU4cauBqj/84nnXWriVEre9Y7JpFCEdeNjZ+w0YfIeQL9SEO4aOx4BRBvld30N5pQfXUr3OZ4DhREmx6Oyba7jJSCj1s= Received: by 10.66.242.20 with SMTP id p20mr5074900ugh; Thu, 14 Sep 2006 14:50:50 -0700 (PDT) Received: by 10.67.21.18 with HTTP; Thu, 14 Sep 2006 14:50:50 -0700 (PDT) Message-ID: Date: Fri, 15 Sep 2006 00:50:50 +0300 From: "Maher Mohamed" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ACPI it failed in Acer Ferrari 4005 wmli X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 21:50:55 -0000 Dear friends. The ACPI is not working on my machine, I am using FreeBSD 6.1 Stable. How can i fix and if there is any instruction regarding the fix, please do not just mention just some files, but rather instruct me where and how to put them. Thank you in Advanced -- Mohamed M. Maher From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:07: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 CC38916A416 for ; Thu, 14 Sep 2006 23:07:09 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4C3043D4C for ; Thu, 14 Sep 2006 23:07:08 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8EN77lS099890 for ; Thu, 14 Sep 2006 16:07:07 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8EN75qa099887; Thu, 14 Sep 2006 16:07:05 -0700 (PDT) (envelope-from kline) Date: Thu, 14 Sep 2006 16:07:05 -0700 From: Gary Kline To: Jamie Bowden Message-ID: <20060914230705.GB99220@thought.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 23:07:09 -0000 On Thu, Sep 14, 2006 at 11:44:12AM -0400, Jamie Bowden wrote: > On 9/9/06, Mark Andrews wrote: > > >> Yeah, -STABLE is what you should run if you want stable code, right? > > > No. STABLE means STABLE API. > > > If you want stable code you run releases. Between releases > > stable can become unstable. Think of stable as permanent > > BETA code. Changes have passed the first level of testing > > in current which is permanent ALPHA code. > > No, this is what it means now. I've been running FreeBSD since 1.1, > and -STABLE used to mean exactly that. The developement branch was > -C, and -S was where things went after extensive testing. You were > not allowed to break -S or Jordan would rip your fingers off. This > change to the current structure wasn't meant to be permanent when it > was done (between 4 and 5, IIRC), and was only done out of necessity > because the changes across that major release were huge. > > FreeBSD needs an interim track that mirrors what -STABLE used to be, > which is a track between point releases that can be relied upon (and > RELEASE_x_y doesn't work, since it only addresses security and bugs > deemed worthy, which most aren't). > YES [bar]. Until then I'm wedged into running -RELEASE (and occasionally praying to the computer gods. > -- > Jamie Bowden > -- > "It was half way to Rivendell when the drugs began to take hold" > Hunter S Tolkien "Fear and Loathing in Barad Dur" > Iain Bowen > _______________________________________________ > 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" -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:11: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 1C83D16A40F for ; Thu, 14 Sep 2006 23:11: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 9256D43D53 for ; Thu, 14 Sep 2006 23:10:59 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 15546 invoked from network); 14 Sep 2006 23:10:58 -0000 Received: from unknown (74.230.48.254) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 14 Sep 2006 23:10:57 -0000 In-Reply-To: <4509A7ED.4090701@cs.tu-berlin.de> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4509A7ED.4090701@cs.tu-berlin.de> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: "hackmiester (Hunter Fuller)" Date: Thu, 14 Sep 2006 17:34:08 -0500 To: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 23:11:00 -0000 On 14 September 2006, at 14:05, Bj=F6rn K=F6nig wrote: > hackmiester (Hunter Fuller) schrieb: >> On 12 September 2006, at 02:06, Bj=F6rn K=F6nig wrote: >>> Karl Denninger schrieb: >>> >>>> This is not cool folks. >>> >>> >>> I think you misunderstood what -STABLE means. (Or maybe I do?) >>> >>> -STABLE is still a development branch without guarantee of a =20 >>> stable and working operating system. >> Hahahahaha... That's ironic... > > That wasn't meant to be ironic. Years of experience and =20 > observations of development lead to this conclusion. RIght. All i can say, though, is that someone that doesn't know any =20 better would probably not think "Oh! That means that upgrades are =20 possible between releases, and not that my system will actually run, =20 or anything!" It just seems it'd be quite a cause of confusion. > > Regards > Bj=F6rn > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-=20 > unsubscribe@freebsd.org" > --=20 hackmiester (Hunter Fuller) yknow when you go to a party, and everyones hooked up except =20 one guy and one girl and so they look at each other like.. do we have to? intel & nvidia must be lookin at each other like that right now Phone Voice: +1 251 589 6348 Fax: Call the voice number and ask. Email General chat: hackmiester@hackmiester.com Large attachments: hackmiester@gmail.com SPS-related stuff: hfuller@stpaulsmobile.net IM AIM: hackmiester1337 Skype: hackmiester31337 YIM: hackm1ester Gtalk: hackmiester MSN: hackmiester@hackmiester.com Xfire: hackmiester From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:11: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 1C65F16A5D3 for ; Thu, 14 Sep 2006 23:11:10 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E6A543D4C for ; Thu, 14 Sep 2006 23:11:09 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8ENB8Ri099918; Thu, 14 Sep 2006 16:11:08 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8ENB8E9099917; Thu, 14 Sep 2006 16:11:08 -0700 (PDT) (envelope-from kline) Date: Thu, 14 Sep 2006 16:11:08 -0700 From: Gary Kline To: Ricardo Nabinger Sanchez Message-ID: <20060914231108.GC99220@thought.org> References: <1158215254.2889.49.camel@elbereth.gateway.2wire.net> <20060914133630.8387f936.rnsanchez@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060914133630.8387f936.rnsanchez@gmail.com> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: Thanks! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 23:11:10 -0000 On Thu, Sep 14, 2006 at 01:36:30PM -0300, Ricardo Nabinger Sanchez wrote: > On Thu, 14 Sep 2006 01:27:34 -0500, "Charles P. Schaum" > wrote: > > > I am real happy with FreeBSD. I would be interested in seeing more > > desktop stuff become a reality. Neither of the desktop variants of > > FreeBSD works so well for me, yet. > > Have you tried Desktop BSD and/or PCBSD? IIRC, they're based on FreeBSD > and very desktop oriented -- perhaps they'll work well for you. > I *thought* there was a Desktop distro. URL's? or should I just google around? gary > -- > Ricardo Nabinger Sanchez > Powered by FreeBSD > > "Left to themselves, things tend to go from bad to worse." > _______________________________________________ > 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" -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:15: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 5137E16A4A7 for ; Thu, 14 Sep 2006 23:15:36 +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 2712743D6D for ; Thu, 14 Sep 2006 23:15:30 +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 0C44F1A3C20; Thu, 14 Sep 2006 16:15:30 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 592C351448; Thu, 14 Sep 2006 19:15:29 -0400 (EDT) Date: Thu, 14 Sep 2006 19:15:29 -0400 From: Kris Kennaway To: "hackmiester (Hunter Fuller)" Message-ID: <20060914231529.GA59423@xor.obsecurity.org> References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4509A7ED.4090701@cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 23:15:36 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 14, 2006 at 05:34:08PM -0500, hackmiester (Hunter Fuller) wrote: >=20 > On 14 September 2006, at 14:05, Bj?rn K?nig wrote: >=20 > >hackmiester (Hunter Fuller) schrieb: > >>On 12 September 2006, at 02:06, Bj?rn K?nig wrote: > >>>Karl Denninger schrieb: > >>> > >>>>This is not cool folks. > >>> > >>> > >>>I think you misunderstood what -STABLE means. (Or maybe I do?) > >>> > >>>-STABLE is still a development branch without guarantee of a =20 > >>>stable and working operating system. > >>Hahahahaha... That's ironic... > > > >That wasn't meant to be ironic. Years of experience and =20 > >observations of development lead to this conclusion. >=20 > RIght. All i can say, though, is that someone that doesn't know any =20 > better would probably not think "Oh! That means that upgrades are =20 > possible between releases, and not that my system will actually run, =20 > or anything!" > It just seems it'd be quite a cause of confusion. Anyone who is confused but doesn't attempt to enlighten themselves by reading the provided documentation deserves to stay confused :) Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCeKRWry0BWjoQKURAgOtAKChLnMJBKeD+MC7NJdYhN+k1tNbgACgltDc RVBBxSK9YFS5OM3Tb2SC9dU= =179j -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:25: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 7B1DF16A4E7 for ; Thu, 14 Sep 2006 23:25:30 +0000 (UTC) (envelope-from danolson@visi.com) Received: from conn.mc.mpls.visi.com (conn.mc.mpls.visi.com [208.42.156.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62D5943DDF for ; Thu, 14 Sep 2006 23:25:23 +0000 (GMT) (envelope-from danolson@visi.com) Received: from [192.168.240.220] (danolson.dsl.visi.com [209.98.225.50]) by conn.mc.mpls.visi.com (Postfix) with ESMTP id 67C2881B2; Thu, 14 Sep 2006 18:25:20 -0500 (CDT) Message-ID: <4509E4CD.8050102@visi.com> Date: Thu, 14 Sep 2006 18:25:01 -0500 From: Dan Olson User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> In-Reply-To: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 23:25:30 -0000 Jack Vogel wrote: > On 9/13/06, Ronald Klop wrote: > ... > >> Them manual page em(4) mentions trying another cable when the watchdog >> timeout happens, so I tried that. But it didn't help. >> Is there anything I can test to (help) debug this? >> It happens a lot when my machine is under load. (100% CPU) >> Is it possible that it happens since I upgraded the memory from 1GB to 2 >> GB? > > watchdogs mean that the transmit ring is not being cleaned, so the > question is what is your machine doing at 100% cpu, if its that busy > the network watchdogs may just be a side effect and not the real > problem? > > Jack I see these too when installing packages over nfs on my Laptop. If I run with a low level of network traffic, i.e. ssh compile, and peg out the cpu with a benchmark such as flops, I don't see these timeouts. 6.1-STABLE FreeBSD 6.1-STABLE #0: Sat Aug 26 14:45:40 CDT 2006 em0@pci2:1:0: class=0x020000 card=0x05491014 chip=0x101e8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82540EP Gigabit Ethernet Controller (Mobile)' class = network Any suggestions? Thanks Dan From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:37: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 CCEF116A403 for ; Thu, 14 Sep 2006 23:37:50 +0000 (UTC) (envelope-from benlutz@datacomm.ch) Received: from popeye1.ggamaur.net (popeye1.ggamaur.net [213.160.40.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10CBE43D45 for ; Thu, 14 Sep 2006 23:37:49 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from maxlor.mine.nu (maxlor@c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by popeye1.ggamaur.net (8.13.7/8.13.7/Submit) with ESMTP id k8ENbkvJ047927; Fri, 15 Sep 2006 01:37:47 +0200 (CEST) (envelope-from benlutz@datacomm.ch) Received: from localhost (unknown [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 255452E0F7; Fri, 15 Sep 2006 01:37:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at atlantis.intranet Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (atlantis.intranet [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fS19Y2D6GqB7; Fri, 15 Sep 2006 01:37:45 +0200 (CEST) Received: from mini.intranet (mini.intranet [10.0.0.17]) by maxlor.mine.nu (Postfix) with ESMTP id DC8002E0F6; Fri, 15 Sep 2006 01:37:45 +0200 (CEST) From: Benjamin Lutz To: freebsd-stable@freebsd.org Date: Fri, 15 Sep 2006 01:37:43 +0200 User-Agent: KMail/1.9.1 References: <20060909173813.GA1388@FS.denninger.net> <20060914231529.GA59423@xor.obsecurity.org> In-Reply-To: <20060914231529.GA59423@xor.obsecurity.org> X-Face: $Ov27?7*N,h60fIEfNJdb!m,@#4T/d; 1hw|W0zvsHM(a$Yn6BYQ0^SEEXvi8>D`|V*F"=?iso-8859-1?q?=5F+R=0A?= 2@Aq>+mNb4`,'[[%z9v0Fa~]AD1}xQO3|>b.z&}l#R-_(P`?@Mz"kS; XC>Eti,i3>%@g?4f,=?iso-8859-1?q?=5Cc7=7CGh=0A?= =?iso-8859-1?q?_wb=26ky=24b2PJ=5E=5C0b83NkLsFKv=7CsmL/cI4UD=25Tu8alAD?= MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6292370.C4ClTDOheQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200609150137.43850.benlutz@datacomm.ch> X-Scanned-By: MIMEDefang 2.57 on 213.160.40.60 Cc: Kris Kennaway Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Thu, 14 Sep 2006 23:37:50 -0000 --nextPart6292370.C4ClTDOheQ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Friday 15 September 2006 01:15, Kris Kennaway wrote: > Anyone who is confused but doesn't attempt to enlighten themselves by > reading the provided documentation deserves to stay confused :) What if they're unaware of their own confusion? Cheers Benjamin --nextPart6292370.C4ClTDOheQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFCefHgShs4qbRdeQRAr7QAJ47BGJ3N5L+d5+BCXz1vcBLyEGl/ACdG8jD cG3oCGkkVB33g8rMQwZg5Zc= =kqBs -----END PGP SIGNATURE----- --nextPart6292370.C4ClTDOheQ-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 14 23:52: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 C575816A403 for ; Thu, 14 Sep 2006 23:52:18 +0000 (UTC) (envelope-from rnsanchez@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E72C43D45 for ; Thu, 14 Sep 2006 23:52:18 +0000 (GMT) (envelope-from rnsanchez@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so3511209pye for ; Thu, 14 Sep 2006 16:52:17 -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:content-transfer-encoding; b=bAA5LuxdMsM3sHm8GakkXMMN2dWo6fZBupHF0P0zpLCuoY8GtddEJLaqYqnmF3kXX9nwGPNuzYKoJ2Ram2wk9OAUMw8JuB2j9mhneZ/svJa6g9g6h2IMS5wF5Ny075ER33Zftslt7eYznoDiNhpNvyTCUxUTdCcDBqW/mzTPO3U= Received: by 10.65.160.7 with SMTP id m7mr11170582qbo; Thu, 14 Sep 2006 16:52:17 -0700 (PDT) Received: from sauron.lan.box ( [200.203.39.184]) by mx.gmail.com with ESMTP id d5sm1012496qbd.2006.09.14.16.52.15; Thu, 14 Sep 2006 16:52:17 -0700 (PDT) Date: Thu, 14 Sep 2006 20:52:13 -0300 From: Ricardo Nabinger Sanchez To: Gary Kline Message-Id: <20060914205213.3c0aeb51.rnsanchez@gmail.com> In-Reply-To: <20060914231108.GC99220@thought.org> References: <1158215254.2889.49.camel@elbereth.gateway.2wire.net> <20060914133630.8387f936.rnsanchez@gmail.com> <20060914231108.GC99220@thought.org> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Thanks! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 14 Sep 2006 23:52:18 -0000 On Thu, 14 Sep 2006 16:11:08 -0700, Gary Kline wrote: > I *thought* there was a Desktop distro. URL's? or should I > just google around? There you go: http://www.pcbsd.org/ http://www.desktopbsd.net/ :) -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 00:06: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 413C316A403 for ; Fri, 15 Sep 2006 00:06:10 +0000 (UTC) (envelope-from myers@aedifice.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.192.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2ACF43D45 for ; Fri, 15 Sep 2006 00:06:09 +0000 (GMT) (envelope-from myers@aedifice.net) Received: from veetwin.aedifice.net (c-24-6-65-32.hsd1.ca.comcast.net[24.6.65.32]) by comcast.net (rwcrmhc12) with ESMTP id <20060915000609m1200robr8e>; Fri, 15 Sep 2006 00:06:09 +0000 Received: from [10.0.0.20] (nazirite [10.0.0.20]) by veetwin.aedifice.net (8.13.8/8.13.1) with ESMTP id k8F068CJ094913; Thu, 14 Sep 2006 17:06:09 -0700 (PDT) (envelope-from myers@aedifice.net) Message-ID: <4509EE70.1040907@aedifice.net> Date: Thu, 14 Sep 2006 17:06:08 -0700 From: "David C. Myers" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051128) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> In-Reply-To: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 00:06:10 -0000 > watchdogs mean that the transmit ring is not being cleaned, so the > question is what is your machine doing at 100% cpu, if its that busy > the network watchdogs may just be a side effect and not the real > problem? I get them with a completely idle machine. My home directory is mounted via NFS (from FreeBSD 6.1 on an amd64 machine), and with the kernel from earlier this week, the machine would just hang for 30 seconds to a couple of minutes. A slew of "watchdog timeout" messages would appear. Then I'd get a moment's responsiveness out of the machine, then another long wait, then a moment's responsiveness, then a long wait... The machine would never recover from this cycle (at least, so far as I was patient enough to wait). Going back to a kernel dated late July resolved everything. Someone else asked me for the hardware version of my em0 board... em0@pci2:10:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82540EM Gigabit Ethernet Controller' class = network subclass = ethernet -David. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 00:10: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 27FD016A412 for ; Fri, 15 Sep 2006 00:10:18 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83E0C43D5D for ; Fri, 15 Sep 2006 00:10:08 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (unknown [200.46.208.251]) by hub.org (Postfix) with ESMTP id 6CD4B3A4650; Thu, 14 Sep 2006 21:09:52 -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 19053-05; Thu, 14 Sep 2006 21:08:37 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id DDEAE3A464F; Thu, 14 Sep 2006 21:08:36 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id EABE04AAC7; Thu, 14 Sep 2006 21:08:56 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E6A03343F5; Thu, 14 Sep 2006 21:08:56 -0300 (ADT) Date: Thu, 14 Sep 2006 21:08:56 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Jamie Bowden In-Reply-To: Message-ID: <20060914210742.P1031@ganymede.hub.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 00:10:18 -0000 On Thu, 14 Sep 2006, Jamie Bowden wrote: > No, this is what it means now. I've been running FreeBSD since 1.1, > and -STABLE used to mean exactly that. The developement branch was > -C, and -S was where things went after extensive testing. You were > not allowed to break -S or Jordan would rip your fingers off. Ah, QA through fear of the mighty hand of Jordan coming flying out your monitor and ripping your fingers off :) ---- 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 Fri Sep 15 00:10: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 A30BE16A583 for ; Fri, 15 Sep 2006 00:10:30 +0000 (UTC) (envelope-from freebsd@orchid.homeunix.org) Received: from orchid.homeunix.org (aur177.neoplus.adsl.tpnet.pl [83.27.25.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C32243D5A for ; Fri, 15 Sep 2006 00:10:19 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from [192.168.1.66] (blackacidevil.orchid.homeunix.org [192.168.1.66]) (authenticated bits=0) by orchid.homeunix.org (8.13.6/8.13.6) with ESMTP id k8F09m0v055013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Sep 2006 02:10:13 +0200 (CEST) (envelope-from freebsd@orchid.homeunix.org) Message-ID: <4509EF42.7040705@orchid.homeunix.org> Date: Fri, 15 Sep 2006 02:09:38 +0200 From: Karol Kwiatkowski User-Agent: Thunderbird 1.5.0.5 (X11/20060731) MIME-Version: 1.0 To: Benjamin Lutz References: <20060909173813.GA1388@FS.denninger.net> <20060914231529.GA59423@xor.obsecurity.org> <200609150137.43850.benlutz@datacomm.ch> In-Reply-To: <200609150137.43850.benlutz@datacomm.ch> X-Enigmail-Version: 0.94.1.0 OpenPGP: id=06E09309; url=http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig953980C50686FB43F350E3A0" X-Virus-Scanned: ClamAV 0.88.4/1884/Thu Sep 14 22:15:20 2006 on orchid.homeunix.org X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@orchid.homeunix.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 00:10:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig953980C50686FB43F350E3A0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable On 15/09/2006 01:37, Benjamin Lutz wrote: > On Friday 15 September 2006 01:15, Kris Kennaway wrote: >> Anyone who is confused but doesn't attempt to enlighten themselves by >> reading the provided documentation deserves to stay confused :) >=20 > What if they're unaware of their own confusion? I guess they get what they deserves ;) Is there a be better source of enlightenment than a handbook? To quote[1]: ------------------------------------------------------>% 21.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. ------------------------------------------------------>% Regards, Karol [1]http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stab= le.html --=20 Karol Kwiatkowski OpenPGP: http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc --------------enig953980C50686FB43F350E3A0 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.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCe9MezeoPAwGIYsRCODuAKCEMpVIMrJXZjFGjmOb/LEdqRmTwQCfdh8F oaiYxbkUL9o8snzZT9K9VRA= =9ao5 -----END PGP SIGNATURE----- --------------enig953980C50686FB43F350E3A0-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 01:54: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 38E4216A412 for ; Fri, 15 Sep 2006 01:54:41 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE29243D45 for ; Fri, 15 Sep 2006 01:54:40 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (unknown [200.46.208.251]) by hub.org (Postfix) with ESMTP id 09D883A464F for ; Thu, 14 Sep 2006 22:54:21 -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 45573-02 for ; Thu, 14 Sep 2006 22:53:05 -0300 (ADT) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id 69A833A42B3 for ; Thu, 14 Sep 2006 22:53:05 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id A8127343F5; Thu, 14 Sep 2006 22:53:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id A3B2C33CC9 for ; Thu, 14 Sep 2006 22:53:27 -0300 (ADT) Date: Thu, 14 Sep 2006 22:53:27 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20060914224333.P1031@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Regression Tests ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 01:54:41 -0000 With all the talk about -STABLE, and how bad things can get, and how in 'the good old days, this would never have happened' ... instead of griping about what is, could and should be ... why not focus on how to improve the process? For instance, we know that *most* of the time, -STABLE is exactly that, -STABLE ... and there are several of us that feel that -STABLE is more stable then -RELEASE ... not everyone agrees, but, hey, everyone has a right to disagree ... For the PostgreSQL Project, we have a 'build farm' ... something that I think is similar to the tinderboxes ... but, their point isn't to just build the source tree, but to run its regression tests, and report when something fails: http://www.pgbuildfarm.org/cgi-bin/show_status.pl I saw the post from the guy that caused the original thread, talking about how he was working on regression tests as he's developing the code ... is there some way that we can extend the tinderboxes to run these regression tests, and put a report up on freebsd.org reporting things like 'last successful build/test', so that one could use CVSup to upgrade to that date? ---- 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 Fri Sep 15 02: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 B99FF16A40F for ; Fri, 15 Sep 2006 02:14:31 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BBF843D49 for ; Fri, 15 Sep 2006 02:14:31 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1GO3Dq-0006Ht-6x for ; Fri, 15 Sep 2006 04:14:30 +0200 Received: (qmail 21250 invoked from network); 15 Sep 2006 02:14:28 -0000 Received: from localhost.thuis.klop.ws (HELO guido.klop.ws) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 15 Sep 2006 02:14:28 -0000 Date: Fri, 15 Sep 2006 04:14:28 +0200 To: freebsd-stable@freebsd.org From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> <4509EE70.1040907@aedifice.net> Content-Transfer-Encoding: Quoted-Printable Message-ID: In-Reply-To: <4509EE70.1040907@aedifice.net> User-Agent: Opera Mail/9.01 (FreeBSD) Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 02:14:31 -0000 On Fri, 15 Sep 2006 02:06:08 +0200, David C. Myers = = wrote: > >> watchdogs mean that the transmit ring is not being cleaned, so the >> question is what is your machine doing at 100% cpu, if its that busy >> the network watchdogs may just be a side effect and not the real >> problem? > > > I get them with a completely idle machine. My home directory is mount= ed = > via NFS (from FreeBSD 6.1 on an amd64 machine), and with the kernel fr= om = > earlier this week, the machine would just hang for 30 seconds to a = > couple of minutes. A slew of "watchdog timeout" messages would appear= . = > Then I'd get a moment's responsiveness out of the machine, then = > another long wait, then a moment's responsiveness, then a long wait...= > > The machine would never recover from this cycle (at least, so far as I= = > was patient enough to wait). > > Going back to a kernel dated late July resolved everything. > > Someone else asked me for the hardware version of my em0 board... > > > em0@pci2:10:0: class=3D0x020000 card=3D0x002e8086 chip=3D0x100e8086 r= ev=3D0x02 = > hdr=3D0x00 vendor =3D 'Intel Corporation' > device =3D '82540EM Gigabit Ethernet Controller' > class =3D network > subclass =3D ethernet > > > -David. This sounds familiar to my problem. I solved it today by enabling pollin= g. = I know it's a workaround. -- = Ronald Klop Amsterdam, The Netherlands From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 02:27: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 8336D16A407 for ; Fri, 15 Sep 2006 02:27:26 +0000 (UTC) (envelope-from spamd@kc8onw.net) Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id D97E243D46 for ; Fri, 15 Sep 2006 02:27:25 +0000 (GMT) (envelope-from spamd@kc8onw.net) Received: from gx5.fuse.net ([72.49.10.62]) by smtp2.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060915022724.SUFH2008.smtp2.fuse.net@gx5.fuse.net> for ; Thu, 14 Sep 2006 22:27:24 -0400 Received: from kb8fcl.kc8onw.net ([72.49.10.62]) by gx5.fuse.net (InterMail vG.1.02.00.02 201-2136-104-102-20041210) with ESMTP id <20060915022724.EBXA5373.gx5.fuse.net@kb8fcl.kc8onw.net> for ; Thu, 14 Sep 2006 22:27:24 -0400 Received: from mail.kc8onw.net (unknown [204.117.152.87]) by kb8fcl.kc8onw.net (Postfix) with ESMTP id C187EA1737 for ; Thu, 14 Sep 2006 22:27:19 -0400 (EDT) Received: by mail.kc8onw.net (Postfix, from userid 58) id 89BEA288AB; Thu, 14 Sep 2006 22:27:17 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on server.kc8onw.net X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=ALL_TRUSTED,AWL, MISSING_HEADERS autolearn=ham version=3.1.5 Received: from [10.70.3.254] (unknown [10.70.3.254]) by mail.kc8onw.net (Postfix) with ESMTP id 85904285BD for ; Thu, 14 Sep 2006 22:27:13 -0400 (EDT) Message-ID: <450A0F7E.7020600@kc8onw.net> Date: Thu, 14 Sep 2006 22:27:10 -0400 From: Jonathan Stewart User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <450752F6.4050109@kc8onw.net> <492332980.20060914225258@rulez.sk> In-Reply-To: <492332980.20060914225258@rulez.sk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Anyone??? (was Reproducible data corruption on 6.1-Stable) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 02:27:26 -0000 Daniel Gerzo wrote: > Hello Jonathan, > > Wednesday, September 13, 2006, 2:38:14 AM, you wrote: > >> I set up a new server recently and transferred all the information from >> my old server over. I tried to use unison to synchronize the backup of >> pictures I have taken and noticed that a large number of pictures where >> marked as changed on the server. After checking the pictures by hand I >> confirmed that many of the pictures on the server were corrupted. > >> It appears the corruption happens during the read process because when I >> recompare the files in a graphical diff tool between cache flushes the >> differences move around!?!?!? The differences also appear to be very >> small for the most part, single bytes scattered throughout the file. I >> really have no idea what is causing the problem and would like to pin it >> down so I can either replace hardware if it's bad or fix whatever the >> bug is. > >> CPU: AMD Athlon(tm) XP 3200+ (2090.16-MHz 686-class CPU) >> Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > I saw very similar simptons on p4 3.2ghz. I was able to build world > without any problems and the overall stability of the machine was > completely good, but when I tried to install some ports, the md5 > sums didn't match the source and I was sure that they were all right. > > The following simple test demonstrates the problem I was hitting: > > root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = b95ddf27bc0ffa379c9aa881ca39e92a7d79e0d08999b4dff6d7d9547ee2a72d > root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = 71432841b3965b7ab2d83f0dc7c3049195ea4e9267a8dc2d825a8a0466982930 > root@[bigbang ~]# sha256 /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > SHA256 (/usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz) = 83e44f5301b3270e821850164c74d275f6721bed5d126480cf518a9fe5ca0d6c > root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > bd8c2e593e1fa4b01fd98eaf016329bb > root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > bd8c2e593e1fa4b01fd98eaf016329bb > root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > b9342bb213393238dd37322d4e2ee3fe > root@[bigbang ~]# md5 < /usr/ports/distfiles/ruby/ruby-1.8.4.tar.gz > 88efa7977fd3febaa8d260e3d5f21917 > > The memtest didn't show any problems with RAM and we were unable to > clarify what is really going on. Then we managed to get the machine > replaced with the complete new hardware and the problem was gone. > Later, I was told that it is some kind of known bug in older p4's > bioses (and advised to update the bios which should have been fixed > in the meantime) but we were unable to find out any information about > the problem. Fortunately the colo company replaced the hardware with > no problems. So long so good and the box is running flawlessly. > I don't think it's quite the same as my problem as I have to use dd on a large file to flush the cache and force freebsd to go back to the disk before the checksum changes. At this point I think I need to further narrow down where the error is occurring but I don't know what to try next. I am 99.999% sure memory and cpu are not the problem but after that point I'm getting into driver and filesystem code testing which is a little overwhelming to just dive into. Jonathan From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 04:22: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 CC20816A417; Fri, 15 Sep 2006 04:22:19 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.223.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DE5243D5E; Fri, 15 Sep 2006 04:22:17 +0000 (GMT) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([81.18.142.225]:37132 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S2077741AbWIOEWJ (ORCPT + 2 others); Fri, 15 Sep 2006 08:22:09 +0400 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <450A2A6E.3040408@yandex.ru> Date: Fri, 15 Sep 2006 08:22:06 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Marcelo Gardini do Amaral References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> <20060914175049.GH49126@registro.br> In-Reply-To: <20060914175049.GH49126@registro.br> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Robert Watson , freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 04:22:19 -0000 Marcelo Gardini do Amaral wrote: > With the 7.x kernel and no changes in src/sys/netinet/udp_usrreq.c I > tried different timecounters and I couldn't see any performance > difference. You have tested with a GENERIC kernel? You should remove all debugging kernel options before testing performance. -- WBR, Andrey V. Elsukov From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 05:49: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 9883D16A40F for ; Fri, 15 Sep 2006 05:49:36 +0000 (UTC) (envelope-from verbo.solo@sbcglobal.net) Received: from smtp101.plus.mail.re2.yahoo.com (smtp101.plus.mail.re2.yahoo.com [206.190.53.26]) by mx1.FreeBSD.org (Postfix) with SMTP id 136B743D46 for ; Fri, 15 Sep 2006 05:49:35 +0000 (GMT) (envelope-from verbo.solo@sbcglobal.net) Received: (qmail 65971 invoked from network); 15 Sep 2006 05:49:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=hPyAgU4TihTX9UgZ0IZFMnjEUZ89/EX6icNolXTElydy66Zi8udKhPpvk5qBkwkk0oKXGWzNjEN82ZJZTYSBX2ueFEGyWAA+fF8HMSVAwEACjJiU480YRPlFNpO+OTwuOPD5QBRMtZJWkEPENCeHJ4dEZUvBKib3BXc9F+Fqv1Q= ; Received: from unknown (HELO elbereth.gateway.2wire.net) (verbo.solo@sbcglobal.net@69.151.15.132 with plain) by smtp101.plus.mail.re2.yahoo.com with SMTP; 15 Sep 2006 05:49:35 -0000 From: "Charles P. Schaum" To: "freebsd-stable@freebsd.org" Content-Type: text/plain Date: Fri, 15 Sep 2006 00:49:33 -0500 Message-Id: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: PC-BSD and DesktopBSD compared to FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 05:49:36 -0000 A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: -STABLE works best. First, PC-BSD will panic under more conditions than -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found that to be true, especially with older boxes. Second, DesktopBSD works better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. So that kinda throws a spanner in the works. Both desktop installers, however, do not easily support an install over multiple disks or a lot of customization. FreeBSD does. That's the same reason why I like the Debian installer and the old Ubuntu installer over many of the others. (Although the Ubuntu installer, old and new, has geometry issues.) Fedora's default is to use an LVM setup that will be a pain in the tush if you install anything else over it unless you use a third-party util to hose all the LVM info. Merely creating a new FS, i.e., installing FBSD in the slice where Fedora was, won't cut it; you will get weirdness in the boot loader. When I want desktop, I don't want dumb. I want defaults for those that want them and then I want to depart from that when needed. The desktop attempts based on FreeBSD do not easily handle this. I see that as basically a show-stopper. The elegant thing about FreeBSD is the way in which one can vary things to meet individual needs. This is no "canonical distro" template mentality. The real trick is to make a desktop work with such variation. One thing I see, for example, is an opportunity to have a decision like "here is some default art, themes, whatever" in a port/package for those that want a "my machine looks like FreeBSD" feel. One might suggest that all ports that would normally be associated with menus and MIME types in XFCE, KDE and Gnome, etc. would arrange to install these in the expected places. Presently, some do; some don't. One need not integrate a lot into the OS. Indeed, scripts for removable media events and the like can safely remain in ports. But it strikes me that Linux and Windows, as well as MacOS, all have a certain "look and feel" per distro and that a move to say "for those that want a default option of >>look and feel<< and don't want to continually edit menus (for which KDE is easiest) then we have a plan for you." This would not add too much burden to the port maintainers and it would just make the learning curve a little easier for noobs, until they do a BOFH-recommended action after failing to RTFM. Even running the autoconfig for X, if X is installed, and allowing a GUI login manager selection menu in the installer couldn't hurt. After all, if one bundles things like Gnome and KDE on distribution media, why not go the distance and give the option to do all the preliminary integration in the installer, if so selected? For example, I have no problem installing NetBSD, knowing that I first go to the utility menu and set up the NIC, then install, then say yes, I want those NIC settings to save some work, then do the reboots and set things up. Then I tweak more files and add software with pkgsrc. But that's extra work that FreeBSD already integrates to some extent into one installer session. Why not continue along that path? What about a menu that allows an expert mode for certain stages as well as just a default decision like "I want FreeBSD with KDE/Gnome." For example, if pdftk or ImageMagick blow up /var/tmp when batch converting or if OpenOffice takes about 9G to compile, then one could consider a resource needs database correlating to packages desired at install time. Given, that puts stress on the size of the image. It could also be a DVD-only option. One could select the ports that one would eventually like (perhaps like synaptic) and the needs could be anticipated for install-time FS-tuning. A subsequent option might allow installation via pkg_add or simply set up a script and notify root to run it in the background to fetch and install the desired packages at a later time. Such an approach would take the selection of distributions and packages to perhaps another level. Yes, it violates the "small is better" dictum but it also recognizes that the folks at the middle of the bell curve are great in number and short on technical mastery. The decision comes when the target market is determined. It would also give a certain "slick" factor. That might not always be good, but remembering old Amiga demos, I can hardly deny that eye candy and ease of use does attract. Part of the desktop thing for me is that I am partially blind and I find that Gnome is very friendly to my vision, or lack thereof. It causes much less eye strain than other desktops. So I like working from that environment for accessibility issues. I like the idea of a challenge and solving a problem. I like FreeBSD. I don't get off on messing with pixmaps, menus, MIME types and other mickey-mouse stuff. Requiring a certain standard of desktop integration by port maintainers, giving the option of a default look and feel and otherwise keeping things robust and packing more configuration steps into the installer would suit me fine. Charles From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 06:03: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 E534E16A417 for ; Fri, 15 Sep 2006 06:03:45 +0000 (UTC) (envelope-from subhro.kar@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 CA97443D5A for ; Fri, 15 Sep 2006 06:03:44 +0000 (GMT) (envelope-from subhro.kar@gmail.com) Received: by nf-out-0910.google.com with SMTP id n29so2280037nfc for ; Thu, 14 Sep 2006 23:03:43 -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=pCck6ga6GzAqbU7h6x6qLtehRNbync3ZUvc2p6NjvpiouScKM5nOeQOnCvy5iyjeEgHwqdQispHdNsEYGBO+W+iFUteY3mS6dEbXFCz/X4HQK1E0OGOTn21GN/Oabtp4W9eONxhWf+LxiMCzMyzPsjRujbwC27aMoq/CwP/z1uU= Received: by 10.48.163.19 with SMTP id l19mr12769232nfe; Thu, 14 Sep 2006 23:03:42 -0700 (PDT) Received: by 10.49.60.11 with HTTP; Thu, 14 Sep 2006 23:03:42 -0700 (PDT) Message-ID: Date: Fri, 15 Sep 2006 11:33:42 +0530 From: Subhro To: "Charles P. Schaum" In-Reply-To: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> Cc: "freebsd-stable@freebsd.org" Subject: Re: PC-BSD and DesktopBSD compared to FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 06:03:46 -0000 Hello Charles, Thanks for your insight. I would also like to express my views in this regard. Every OS has a target audience and every OS has its own strengths and weaknesses. Something which would nicely for you does not mean that it would work exactly the same way for everyone else in the world. You are free to have personal opinions but please be kind enough to keep them *personal*. What you have done could very well generate a troll. PLEASE DO NOT TROLL. Also to the best of my knowledge the purpose of this list is to discuss about the different features/ changes of the STABLE tree. Feel free to move the discussion to advocacy@ mailing list. Thanks and Best Regards Subhro On 9/15/06, Charles P. Schaum wrote: > A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: > > -STABLE works best. First, PC-BSD will panic under more conditions than > -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found > that to be true, especially with older boxes. Second, DesktopBSD works > better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. > So that kinda throws a spanner in the works. > > Both desktop installers, however, do not easily support an install over > multiple disks or a lot of customization. FreeBSD does. > > That's the same reason why I like the Debian installer and the old > Ubuntu installer over many of the others. (Although the Ubuntu > installer, old and new, has geometry issues.) Fedora's default is to use > an LVM setup that will be a pain in the tush if you install anything > else over it unless you use a third-party util to hose all the LVM info. > Merely creating a new FS, i.e., installing FBSD in the slice where > Fedora was, won't cut it; you will get weirdness in the boot loader. > > When I want desktop, I don't want dumb. I want defaults for those that > want them and then I want to depart from that when needed. The desktop > attempts based on FreeBSD do not easily handle this. I see that as > basically a show-stopper. The elegant thing about FreeBSD is the way in > which one can vary things to meet individual needs. This is no > "canonical distro" template mentality. The real trick is to make a > desktop work with such variation. > > One thing I see, for example, is an opportunity to have a decision like > "here is some default art, themes, whatever" in a port/package for those > that want a "my machine looks like FreeBSD" feel. One might suggest that > all ports that would normally be associated with menus and MIME types in > XFCE, KDE and Gnome, etc. would arrange to install these in the expected > places. Presently, some do; some don't. > > One need not integrate a lot into the OS. Indeed, scripts for removable > media events and the like can safely remain in ports. But it strikes me > that Linux and Windows, as well as MacOS, all have a certain "look and > feel" per distro and that a move to say "for those that want a default > option of >>look and feel<< and don't want to continually edit menus > (for which KDE is easiest) then we have a plan for you." This would not > add too much burden to the port maintainers and it would just make the > learning curve a little easier for noobs, until they do a > BOFH-recommended action after failing to RTFM. > > Even running the autoconfig for X, if X is installed, and allowing a GUI > login manager selection menu in the installer couldn't hurt. After all, > if one bundles things like Gnome and KDE on distribution media, why not > go the distance and give the option to do all the preliminary > integration in the installer, if so selected? > > For example, I have no problem installing NetBSD, knowing that I first > go to the utility menu and set up the NIC, then install, then say yes, I > want those NIC settings to save some work, then do the reboots and set > things up. Then I tweak more files and add software with pkgsrc. > > But that's extra work that FreeBSD already integrates to some extent > into one installer session. Why not continue along that path? What about > a menu that allows an expert mode for certain stages as well as just a > default decision like "I want FreeBSD with KDE/Gnome." For example, if > pdftk or ImageMagick blow up /var/tmp when batch converting or if > OpenOffice takes about 9G to compile, then one could consider a resource > needs database correlating to packages desired at install time. Given, > that puts stress on the size of the image. It could also be a DVD-only > option. One could select the ports that one would eventually like > (perhaps like synaptic) and the needs could be anticipated for > install-time FS-tuning. A subsequent option might allow installation via > pkg_add or simply set up a script and notify root to run it in the > background to fetch and install the desired packages at a later time. > > Such an approach would take the selection of distributions and packages > to perhaps another level. Yes, it violates the "small is better" dictum > but it also recognizes that the folks at the middle of the bell curve > are great in number and short on technical mastery. The decision comes > when the target market is determined. > > It would also give a certain "slick" factor. That might not always be > good, but remembering old Amiga demos, I can hardly deny that eye candy > and ease of use does attract. Part of the desktop thing for me is that I > am partially blind and I find that Gnome is very friendly to my vision, > or lack thereof. It causes much less eye strain than other desktops. So > I like working from that environment for accessibility issues. > > I like the idea of a challenge and solving a problem. I like FreeBSD. I > don't get off on messing with pixmaps, menus, MIME types and other > mickey-mouse stuff. Requiring a certain standard of desktop integration > by port maintainers, giving the option of a default look and feel and > otherwise keeping things robust and packing more configuration steps > into the installer would suit me fine. > > Charles > > > _______________________________________________ > 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" > -- Subhro Kar Security Engineer iViZ Techno Solutions Pvt. Ltd. Dhanshree Bldg, 1st Floor Plot XI-16, Sector V Salt Lake City 700091 India From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 06:43: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 D164716A40F for ; Fri, 15 Sep 2006 06:43:01 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 0CA8943D45 for ; Fri, 15 Sep 2006 06:43:00 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 15 Sep 2006 07:42:42 +0100 (BST) Date: Fri, 15 Sep 2006 07:42:37 +0100 From: David Malone To: "Marc G. Fournier" Message-ID: <20060915064237.GA89843@walton.maths.tcd.ie> References: <20060914224333.P1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060914224333.P1031@ganymede.hub.org> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-stable@freebsd.org Subject: Re: Regression Tests ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 06:43:01 -0000 On Thu, Sep 14, 2006 at 10:53:27PM -0300, Marc G. Fournier wrote: > For the PostgreSQL Project, we have a 'build farm' ... something that I > think is similar to the tinderboxes ... but, their point isn't to just > build the source tree, but to run its regression tests, and report when > something fails: > > http://www.pgbuildfarm.org/cgi-bin/show_status.pl We do have something similar - Peter Holm's Stress: http://people.freebsd.org/~pho/stress/ He has a presentation at: http://www.linuxforum.dk/2006/slides/peterholm-lf06.pdf David. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 06:54: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 24C3A16A403 for ; Fri, 15 Sep 2006 06:54:59 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 487EC43D45 for ; Fri, 15 Sep 2006 06:54:57 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 15 Sep 2006 06:54:56 -0000 Received: from p54A7FDF1.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.253.241] by mail.gmx.net (mp034) with SMTP; 15 Sep 2006 08:54:56 +0200 X-Authenticated: #5465401 Message-ID: <450A4E37.6090703@gmx.de> Date: Fri, 15 Sep 2006 08:54:47 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: "Charles P. Schaum" References: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> In-Reply-To: <1158299373.1608.72.camel@elbereth.gateway.2wire.net> 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: PC-BSD and DesktopBSD compared to FreeBSD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 06:54:59 -0000 Charles P. Schaum wrote: > A note on PC-BSD and DesktopBSD as compared to my -STABLE experiences: > > -STABLE works best. First, PC-BSD will panic under more conditions than > -RELEASE, -STABLE or DesktopBSD. I did some monkeying around and found > that to be true, especially with older boxes. Second, DesktopBSD works > better than PC-BSD, and noticeably so. But it's based on 5 and I want 6. > So that kinda throws a spanner in the works. The DesktopBSD development version is based on 6-Stable. they're waiting for the 6.2 release to release their new release. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 06:58: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 DDA0C16A407 for ; Fri, 15 Sep 2006 06:58:41 +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 404EC43D4C for ; Fri, 15 Sep 2006 06:58:38 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.3) with ESMTP id k8F6wb50064427; Fri, 15 Sep 2006 10:58:37 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Fri, 15 Sep 2006 10:58:37 +0400 (MSD) From: Maxim Konovalov To: David Malone In-Reply-To: <20060915064237.GA89843@walton.maths.tcd.ie> Message-ID: <20060915104954.I64240@mp2.macomnet.net> References: <20060914224333.P1031@ganymede.hub.org> <20060915064237.GA89843@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, "Marc G. Fournier" Subject: Re: Regression Tests ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 06:58:41 -0000 On Fri, 15 Sep 2006, 07:42+0100, David Malone wrote: > On Thu, Sep 14, 2006 at 10:53:27PM -0300, Marc G. Fournier wrote: > > For the PostgreSQL Project, we have a 'build farm' ... something that I > > think is similar to the tinderboxes ... but, their point isn't to just > > build the source tree, but to run its regression tests, and report when > > something fails: > > > > http://www.pgbuildfarm.org/cgi-bin/show_status.pl > > We do have something similar - Peter Holm's Stress: > > http://people.freebsd.org/~pho/stress/ > > He has a presentation at: > > http://www.linuxforum.dk/2006/slides/peterholm-lf06.pdf Actually, stress & perfomance tests are a different class of the tests. What we have in tools/regression are regression tests but the main problem we still don't have a unified way to write them and no infrastructure to run and report results. E.g. at the moment you can't cd /usr/src/tools/regression/ && make. Perhaps we just need to steal NetBSD's bits until we invent something better. Btw, there is an item in the project ideas list: http://www.freebsd.org/projects/ideas/#p-regression -- Maxim Konovalov From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 07:44: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 379A316A415 for ; Fri, 15 Sep 2006 07:44:14 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6745A43D46 for ; Fri, 15 Sep 2006 07:44:13 +0000 (GMT) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from localhost (localhost.internal [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 79C5D8051 for ; Fri, 15 Sep 2006 09:43:48 +0200 (CEST) Received: from [10.236.150.4] (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 69ED38020; Fri, 15 Sep 2006 09:43:45 +0200 (CEST) In-Reply-To: References: <20060909173813.GA1388@FS.denninger.net> <45065C67.6040503@cs.tu-berlin.de> <4509A7ED.4090701@cs.tu-berlin.de> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0AE8B3AB-1709-4724-94C8-D25558B27EFF@solfertje.student.utwente.nl> Content-Transfer-Encoding: 7bit From: Alban Hertroys Date: Fri, 15 Sep 2006 09:44:07 +0200 To: "hackmiester (Hunter Fuller)" X-Mailer: Apple Mail (2.752.2) X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Sep 15 09:43:48 2006 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 74,450a59b47241130310126 X-DSPAM-Factors: 27, Received*Sep, 0.40000, That, 0.40000, That, 0.40000, From*Alban, 0.40000, Subject*Guys+who's, 0.40000, just, 0.40000, (Hunter+Fuller), 0.40000, Mime-Version*Message, 0.40000, All+i, 0.40000, and+not, 0.40000, Subject*Guys, 0.40000, or, 0.40000, In-Reply-To*489A+87D1, 0.40000, an, 0.40000, References*87D1+1304D0D05F2D, 0.40000, meant, 0.40000, be+quite, 0.40000, >+It, 0.40000, of, 0.40000, of, 0.40000, References*<45065C67.6040503, 0.40000, Cc* List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Sep 2006 07:44:14 -0000 On Sep 15, 2006, at 24:34, hackmiester (Hunter Fuller) wrote: >>> Hahahahaha... That's ironic... >> >> That wasn't meant to be ironic. Years of experience and >> observations of development lead to this conclusion. > > RIght. All i can say, though, is that someone that doesn't know any > better would probably not think "Oh! That means that upgrades are > possible between releases, and not that my system will actually > run, or anything!" > It just seems it'd be quite a cause of confusion. So, actually Microsoft may be correctly claiming that WindowsXP is more stable than Linux. That it spontaneously reboots as soon as I bore it isn't related at all... -- Alban Hertroys "This person has performed an illegal operation, and will be shot down." !DSPAM:74,450a59b47241130310126! From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 08:25: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 E8C9916A417 for ; Fri, 15 Sep 2006 08:25:20 +0000 (UTC) (envelope-from verbo.solo@sbcglobal.net) Received: from smtp102.plus.mail.re2.yahoo.com (smtp102.plus.mail.re2.yahoo.com [206.190.53.27]) by mx1.FreeBSD.org (Postfix) with SMTP id 524EF43D45 for ; Fri, 15 Sep 2006 08:25:20 +0000 (GMT) (envelope-from verbo.solo@sbcglobal.net) Received: (qmail 41526 invoked from network); 15 Sep 2006 08:25:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:Subject:From:To:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=ttYGnCqnU2BwJN565tpxNjqKyoUUt5Pzau7NDkE9JHIyLs7NGXQJx2JcAao8cl/fDaUmvq8MaeI/hZe63wk1yVoZxz2PfxzTxqx7g2MpLg6A6zRcfe5FD1rQtpz7rEVGByEZZfdczTu/gYF/1hWxcpvfiSRmL07Ci4QRggmulUo= ; Received: from unknown (HELO elbereth.gateway.2wire.net) (verbo.solo@sbcglobal.net@69.151.15.132 with plain) by smtp102.plus.mail.re2.yahoo.com with SMTP; 15 Sep 2006 08:25:19 -0000 From: "Charles P. Schaum" To: "freebsd-stable@freebsd.org" Content-Type: text/plain Date: Fri, 15 Sep 2006 03:25:17 -0500 Message-Id: <1158308717.801.1.camel@elbereth.gateway.2wire.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Thanks X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 08:25:21 -0000 Thank you for the information and direction. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 09:49: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 33C5E16A407 for ; Fri, 15 Sep 2006 09:49:38 +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 82B9D43D46 for ; Fri, 15 Sep 2006 09:49:37 +0000 (GMT) (envelope-from freebsd@meijome.net) Received: (qmail 7856 invoked from network); 15 Sep 2006 19:49:36 +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; 15 Sep 2006 19:49:36 +1000 Date: Fri, 15 Sep 2006 19:49:30 +1000 From: Norberto Meijome To: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20060915194930.2fda6a0a@localhost> X-Mailer: Sylpheed-Claws 2.4.0 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Followup on ACPI resume problems in STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 09:49:38 -0000 [ followup to http://lists.freebsd.org/pipermail/freebsd-mobile/2006-September/008993.html ] Hi all, I went back to RELENG_6, updated, and rebuilt world and kernel, but this time the GENERIC one. Similar (or possibly the same) lockup as with RELENG_6 and my custom kernel. I tried the suspend/ resume several times, each of them end up with a crash and no info on log/messages or kernel dump. On resume, the screen would turn a soft white colour. I could press Caps lock and the LED would respond. In some instances, going to the console where X is running would work, but it'd lock up within seconds. In most cases, everything would lock up within 10 seconds, with no change in what I'd see on screen. Caps lock LED would stop responding too. I'm back to RELENG_6_1 now with my custom kernel...and rebuilding some of my installed ports as some didnt like the regression. I'd love to help, but i'm at loss wrt what to try next. Cheers, B _________________________ {Beto|Norberto|Numard} Meijome Unix is user friendly. However, it isn't idiot friendly. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 10:13:51 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 A977716A40F for ; Fri, 15 Sep 2006 10:13:51 +0000 (UTC) (envelope-from anders@FreeBSD.org) Received: from fupp.net (totem.fix.no [80.91.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 264AC43D53 for ; Fri, 15 Sep 2006 10:13:50 +0000 (GMT) (envelope-from anders@FreeBSD.org) Received: from localhost (totem.fix.no [80.91.36.20]) by fupp.net (Postfix) with ESMTP id 8E8C88D98A2; Fri, 15 Sep 2006 12:13:49 +0200 (CEST) Received: from fupp.net ([80.91.36.20]) by localhost (totem.fix.no [80.91.36.20]) (amavisd-new, port 10024) with LMTP id 22689-01-9; Fri, 15 Sep 2006 12:13:49 +0200 (CEST) Received: by fupp.net (Postfix, from userid 1000) id ECB7A8D98B4; Fri, 15 Sep 2006 12:13:48 +0200 (CEST) Date: Fri, 15 Sep 2006 12:13:48 +0200 From: Anders Nordby To: Pawel Worach Message-ID: <20060915101348.GA88551@totem.fix.no> References: <44BABBAD.5060606@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44BABBAD.5060606@gmail.com> X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: panic: page fault in kern_kevent X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 10:13:51 -0000 Hi, Just wanted to say that I have the same problem, kernel crashing because of kernel queues usage in Squid 2.6. I've reported some more information on: http://www.freebsd.org/cgi/query-pr.cgi?pr=103127 On Mon, Jul 17, 2006 at 12:20:29AM +0200, Pawel Worach wrote: > Under moderate kqueue load I caught the following: > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x20:0x0 > stack pointer = 0x28:0xe745db78 > frame pointer = 0x28:0xe745dbb8 > 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 = 582 (squid) > trap number = 12 > panic: page fault > KDB: stack backtrace: > kdb_backtrace(c065b33b,c06a4780,c065344e,e745da80,100) at kdb_backtrace+0x2e > panic(c065344e,c066df69,c49c0dd0,1,1) at panic+0xb7 > trap_fatal(e745db38,0,1,0,c05239e2) at trap_fatal+0x33e > trap_pfault(e745db38,0,0,e745db38,0) at trap_pfault+0x242 > trap(c05e0008,c7310028,28,0,4) at trap+0x350 > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0, esp = 0xe745db78, ebp = 0xe745dbb8 --- > MAXCPU(c4b20500,e745dbe8,c65c3300,1,c0c38000) at 0 > kern_kevent(c65c3300,3,5,80,e745dcbc) at kern_kevent+0xf8 > kevent(c65c3300,e745dd04,18,16,c65c3300) at kevent+0x7a > syscall(821003b,3b,822003b,48106cf0,bfbfeec8) at syscall+0x380 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (363, FreeBSD ELF32, kevent), eip = 0x4821ccfb, esp = > 0xbfbfedfc, ebp = 0xbfbfee48 --- > Uptime: 3d15h16m7s > Dumping 1023 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 1023MB (261884 pages) 1008 992 976 960 944 928 912 896 880 > 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592 > 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304 > 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 > > (kgdb) bt > #0 doadump () at pcpu.h:165 > #1 0xc04c261c in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc04c299d in panic (fmt=0xc065344e "%s") > at /usr/src/sys/kern/kern_shutdown.c:565 > #3 0xc0637f7e in trap_fatal (frame=0xe745db38, eva=0) > at /usr/src/sys/i386/i386/trap.c:836 > #4 0xc0637c12 in trap_pfault (frame=0xe745db38, usermode=0, eva=0) > at /usr/src/sys/i386/i386/trap.c:744 > #5 0xc0637780 in trap (frame= > {tf_fs = -1067581432, tf_es = -953090008, tf_ds = 40, tf_edi = 0, > tf_esi = 4, tf_ebp = -414852168, tf_isp = -414852252, tf_ebx = 4, tf_edx > = -953052640, tf_ecx = -1066925280, tf_eax = -1066924800, tf_trapno = > 12, tf_err = 0, tf_eip = 0, tf_cs = 32, tf_eflags = 66118, tf_esp = > -1068903001, tf_ss = -953052640}) > at /usr/src/sys/i386/i386/trap.c:434 > #6 0xc062498a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #7 0x00000000 in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) l *kern_kevent+0xf8 > 0xc049c6d8 is in kern_kevent (/usr/src/sys/kern/kern_event.c:637). > 632 goto done; > 633 changes = keva; > 634 for (i = 0; i < n; i++) { > 635 kevp = &changes[i]; > 636 kevp->flags &= ~EV_SYSFLAGS; > 637 error = kqueue_register(kq, kevp, td, 1); > 638 if (error) { > 639 if (nevents != 0) { > 640 kevp->flags = EV_ERROR; > 641 kevp->data = error; > > System is i386 UP running FreeBSD 6.1-STABLE #0: Sun Jul 9 01:11:16 > CEST 2006 > > -- > Pawel > _______________________________________________ > 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" -- Anders. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 11:57: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 CC2DB16A47E for ; Fri, 15 Sep 2006 11:57:48 +0000 (UTC) (envelope-from martin@gneto.com) Received: from av12-2-sn2.hy.skanova.net (av12-2-sn2.hy.skanova.net [81.228.8.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A6743D5F for ; Fri, 15 Sep 2006 11:57:43 +0000 (GMT) (envelope-from martin@gneto.com) Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502) id EAA46381FD; Fri, 15 Sep 2006 13:57:41 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP id DBC0B37F98 for ; Fri, 15 Sep 2006 13:57:41 +0200 (CEST) Received: from [192.168.2.30] (h33n2fls31o985.telia.com [213.67.213.33]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id C2C9037E56 for ; Fri, 15 Sep 2006 13:57:41 +0200 (CEST) Message-ID: <450A952C.9080600@gneto.com> Date: Fri, 15 Sep 2006 13:57:32 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> <4509E4CD.8050102@visi.com> In-Reply-To: <4509E4CD.8050102@visi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 11:57:48 -0000 I'm also seeing these on a Supermicro PDSMi board with a recent stable. Please tell me what debugging info that is needed to fix this. /Martin FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 10 17:43:15 CEST 2006 root@mailbox:/usr/obj-local/usr/src/sys/SMP amd64 lspci -v output: 04:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03) Subsystem: Super Micro Computer Inc Unknown device 108c Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at ed200000 (32-bit, non-prefetchable) I/O ports at 4000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 05:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller Subsystem: Super Micro Computer Inc Unknown device 109a Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at ed300000 (32-bit, non-prefetchable) I/O ports at 5000 Capabilities: [c8] Power Management version 2 Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [e0] Express Endpoint IRQ 0 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 12:54: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 61E5A16A412 for ; Fri, 15 Sep 2006 12:54:52 +0000 (UTC) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de (mail.smartterra.de [195.225.132.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEEE243D46 for ; Fri, 15 Sep 2006 12:54:51 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from mail.liberty-hosting.de ([195.225.132.203]) by localhost (liberty-mail [195.225.132.203]) (amavisd-new, port 10024) with ESMTP id 21979-04; Fri, 15 Sep 2006 14:55:02 +0200 (CEST) Received: from smtp.alpha-tierchen.de (port-212-202-42-252.dynamic.qsc.de [212.202.42.252]) by mail.liberty-hosting.de (Postfix) with ESMTP id 4AF2C16022E; Fri, 15 Sep 2006 14:55:02 +0200 (CEST) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by smtp.alpha-tierchen.de (Postfix) with ESMTP id 4D7775288A; Fri, 15 Sep 2006 14:54:48 +0200 (CEST) Message-ID: <450AA29D.9000700@cs.tu-berlin.de> Date: Fri, 15 Sep 2006 14:54:53 +0200 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Jamie Bowden References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mail.smartterra.de Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 12:54:52 -0000 Jamie Bowden schrieb: > On 9/9/06, Mark Andrews wrote: > >> > Yeah, -STABLE is what you should run if you want stable code, right? > > >> No. STABLE means STABLE API. > > >> If you want stable code you run releases. Between releases >> stable can become unstable. Think of stable as permanent >> BETA code. Changes have passed the first level of testing >> in current which is permanent ALPHA code. > > > No, this is what it means now. [...] Why do you say "No" if you mean "Yes, but in former times ..."? Björn From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 14:05: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 B5C5816A416 for ; Fri, 15 Sep 2006 14:05:34 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1802F43D45 for ; Fri, 15 Sep 2006 14:05:33 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k8FE5WSC080625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Sep 2006 18:05:32 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k8FE5V8w080624; Fri, 15 Sep 2006 18:05:31 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 15 Sep 2006 18:05:31 +0400 From: Gleb Smirnoff To: Herve Boulouis Message-ID: <20060915140531.GQ27667@FreeBSD.org> References: <20060911001722.GR611@ra.aabs> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060911001722.GR611@ra.aabs> User-Agent: Mutt/1.5.6i Cc: freebsd-stable@FreeBSD.org Subject: Re: bge watchdog timeouts still happening X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 14:05:34 -0000 On Mon, Sep 11, 2006 at 02:17:22AM +0200, Herve Boulouis wrote: H> Hi, H> H> I've recently put into production 2 web servers with 6.0-STABLE from H> mid january and was bitten by the bge watchdog timeouts problems. H> H> I cvsupped the 2 boxes with the latest -stable (latest if_bge.c, H> rev 1.91.2.17) but the problem still persists :( H> H> Server hardware is Dell poweredge 2550 with SMP kernel. H> H> Relevant portion of dmesg : H> H> bge0: mem 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 H> miibus0: on bge0 H> brgphy0: on miibus0 H> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto H> bge0: Ethernet address: 00:06:5b:1a:7f:4a Is it integrated or not? I've got exactly the same NIC and I can try to reproduce the problem if you describe the workload. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 14:15: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 06E9D16A5C6 for ; Fri, 15 Sep 2006 14:15:33 +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 5820143D55 for ; Fri, 15 Sep 2006 14:15:32 +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 A74A0B80F for ; Fri, 15 Sep 2006 10:15:31 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-13--366095498; protocol="application/pkcs7-signature" Message-Id: From: Vivek Khera Date: Fri, 15 Sep 2006 10:15:30 -0400 To: freebsd-stable X-Mailer: Apple Mail (2.752.2) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ACPI it failed in Acer Ferrari 4005 wmli X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 14:15:33 -0000 --Apple-Mail-13--366095498 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Sep 14, 2006, at 5:50 PM, Maher Mohamed wrote: > The ACPI is not working on my machine, I am using FreeBSD 6.1 > Stable. How > can i fix and if there is any instruction regarding the fix, please > do not > just mention just some files, but rather instruct me where and how > to put So you want specific instructions to fix a vague problem description? First, state precisely how "ACPI is not working" and the perhaps someone can tell you what to do. Also, is this "Acer Ferrari 4005 wmli" machine i386 or amd64? Are you booting from CD to install or what? Upgrade? You should also try backing to 6.1-RELEASE CD and see what happens. I'll put on my mindreader hat and guess that you probably need to just disable the ACPI timer. You do that at the boot menu by escaping to the boot prompt (option 6) then typing set debug.acpi.disabled="timer" then type 'boot'. To make it permanent, put the above line without the word "set" into /boot/loader.conf --Apple-Mail-13--366095498-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 14:51: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 5FE6516A403; Fri, 15 Sep 2006 14:51:22 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0357143D45; Fri, 15 Sep 2006 14:51:21 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id A45B52A580; Fri, 15 Sep 2006 11:51:20 -0300 (BRT) Date: Fri, 15 Sep 2006 11:51:20 -0300 From: Marcelo Gardini do Amaral To: "Andrey V. Elsukov" Message-ID: <20060915145120.GA93074@registro.br> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> <20060914175049.GH49126@registro.br> <450A2A6E.3040408@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <450A2A6E.3040408@yandex.ru> User-Agent: Mutt/1.4.2.1i Cc: freebsd-net@freebsd.org, Robert Watson , freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 14:51:22 -0000 > You have tested with a GENERIC kernel? You should remove all > debugging kernel options before testing performance. Sure. Removing debug I got: Kernel UP Timecounter queries/s ----------- --------- TSC 16541 There is no difference. -- Att., Marcelo Gardini From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 14:59: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 260B016A492 for ; Fri, 15 Sep 2006 14:59:16 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DD7543D45 for ; Fri, 15 Sep 2006 14:59:06 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id B081F1116B; Fri, 15 Sep 2006 09:59:02 -0500 (CDT) Date: Fri, 15 Sep 2006 09:58:58 -0500 From: Craig Boston To: Ronald Klop Message-ID: <20060915145858.GA14416@nowhere> Mail-Followup-To: Craig Boston , Ronald Klop , freebsd-stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 14:59:16 -0000 On Thu, Sep 14, 2006 at 02:27:29AM +0200, Ronald Klop wrote: > Them manual page em(4) mentions trying another cable when the watchdog > timeout happens, so I tried that. But it didn't help. > Is there anything I can test to (help) debug this? > It happens a lot when my machine is under load. (100% CPU) > Is it possible that it happens since I upgraded the memory from 1GB to 2 > GB? I don't think it's the cable. I started getting these recently as well (starting about a week ago). Always when there's a lot of CPU and disk I/O load. Also sometimes my USB keyboard would become unresponsive at about the same time (under high load). Sometimes it would stutter and act like the key was being held down for a second or two. I built a new kernel (6.2-PRE now) on 9/12. The keyboard problem seems to be gone but I still get the em watchdog timeouts occasionally. Craig From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 16:16: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 4495A16A417 for ; Fri, 15 Sep 2006 16:16:06 +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 7F00643D5C for ; Fri, 15 Sep 2006 16:16:04 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A69C6.dip.t-dialin.net [84.154.105.198]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8FGG0h8066597 for ; Fri, 15 Sep 2006 18:16:01 +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.13.6/8.13.6) with ESMTP id k8FGG4q7005171 for ; Fri, 15 Sep 2006 18:16:04 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8FGG23C065997 for ; Fri, 15 Sep 2006 18:16:02 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609151616.k8FGG23C065997@fire.jhs.private> To: freebsd-stable@freebsd.org In-reply-to: <450AA29D.9000700@cs.tu-berlin.de> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> Comments: In-reply-to =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= message dated "Fri, 15 Sep 2006 14:54:53 +0200." Date: Fri, 15 Sep 2006 18:16:02 +0200 From: "Julian H. Stacey" Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 16:16:06 -0000 =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= wrote: > Jamie Bowden schrieb: > > On 9/9/06, Mark Andrews wrote: > > > >> > Yeah, -STABLE is what you should run if you want stable code, right? > >> No. STABLE means STABLE API. > >> If you want stable code you run releases. Between releases > >> stable can become unstable. Think of stable as permanent > >> BETA code. Changes have passed the first level of testing > >> in current which is permanent ALPHA code. > > No, this is what it means now. [...] > Why do you say "No" if you mean "Yes, but in former times ..."? Stable is a misnomer that harms FreeBSD somewhat. A promoter of FreeBSD I know has long encouraged people to upgrade from release to stable. Some don't & won't realise Stable is Not necessarily Stable, & may get burnt. Much of the world speaks English only as a 2nd language. They won't benefit from the double trouble of foreign + weird BSD geek speak: "Stable isn't Stable ? Yes or No !" "It's stable, but it's OK to crash ? - I'll go Linux !" Imagine a boat labelled Stable: It sinks. The designers claim: "Tough! We left the Application Interface (routes to bars & toilets) stable, but changed other stuff. Hey ! Stable never meant Stable ! It'd be some work to eradicate the misnomer, but the name's perhaps less entrenched than one might guess, eg: ftp ftp.freebsd.org cd /pub/FreeBSD dir lrwxr-xr-x 1 ftpuser ftpusers 19 Mar 24 14:58 FreeBSD-stable -> branches/4.0-stable cd FreeBSD-stable 550 No such directory. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 16:33: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 4904F16A416 for ; Fri, 15 Sep 2006 16:33:58 +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 02BA043D55 for ; Fri, 15 Sep 2006 16:33:56 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 25686 invoked from network); 15 Sep 2006 16:33:56 -0000 Received: from unknown (67.32.30.240) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 15 Sep 2006 16:33:55 -0000 In-Reply-To: <200609151616.k8FGG23C065997@fire.jhs.private> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6218828A-2540-47F4-A888-03821F97E113@hackmiester.com> Content-Transfer-Encoding: 7bit From: "hackmiester (Hunter Fuller)" Date: Fri, 15 Sep 2006 11:33:52 -0500 To: "Julian H. Stacey" X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 16:33:58 -0000 On 15 September 2006, at 11:16, Julian H. Stacey wrote: > > > Stable is a misnomer that harms FreeBSD somewhat. A promoter of > FreeBSD I know has long encouraged people to upgrade from release > to stable. Some don't & won't realise Stable is Not necessarily > Stable, & may get burnt. Much of the world speaks English only as > a 2nd language. They won't benefit from the double trouble of > foreign + weird BSD geek speak: "Stable isn't Stable ? Yes or No !" > "It's stable, but it's OK to crash ? - I'll go Linux !" > > Imagine a boat labelled Stable: It sinks. The designers claim: > "Tough! We left the Application Interface (routes to bars & toilets) > stable, but changed other stuff. Hey ! Stable never meant Stable ! This is the perfect explanation. Thank you for putting what I am trying to say in words so well. :-) > > It'd be some work to eradicate the misnomer, but the name's perhaps > less entrenched than one might guess, eg: > ftp ftp.freebsd.org > cd /pub/FreeBSD > dir > lrwxr-xr-x 1 ftpuser ftpusers 19 Mar 24 14:58 FreeBSD- > stable -> branches/4.0-stable > cd FreeBSD-stable > 550 No such directory. > -- > Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http:// > berklix.com > Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. > Don't buy it ! Get it free ! http://berklix.org/free-software > _______________________________________________ > 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" > -- hackmiester (Hunter Fuller) yknow when you go to a party, and everyones hooked up except one guy and one girl and so they look at each other like.. do we have to? intel & nvidia must be lookin at each other like that right now Phone Voice: +1 251 589 6348 Fax: Call the voice number and ask. Email General chat: hackmiester@hackmiester.com Large attachments: hackmiester@gmail.com SPS-related stuff: hfuller@stpaulsmobile.net IM AIM: hackmiester1337 Skype: hackmiester31337 YIM: hackm1ester Gtalk: hackmiester MSN: hackmiester@hackmiester.com Xfire: hackmiester From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 16:34: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 B27A916A403; Fri, 15 Sep 2006 16:34:45 +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 2BAE843D68; Fri, 15 Sep 2006 16:34:43 +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 k8FGSeeY080512; Fri, 15 Sep 2006 18:28:40 +0200 (CEST) (envelope-from amon@sockar.homeip.net) Received: (from amon@localhost) by sockar.homeip.net (8.13.4/8.13.3/Submit) id k8FGSerH080511; Fri, 15 Sep 2006 18:28:40 +0200 (CEST) (envelope-from amon) Date: Fri, 15 Sep 2006 18:28:40 +0200 From: Herve Boulouis To: Gleb Smirnoff Message-ID: <20060915162840.GU611@ra.aabs> References: <20060911001722.GR611@ra.aabs> <20060915140531.GQ27667@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060915140531.GQ27667@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@FreeBSD.org Subject: Re: bge watchdog timeouts still happening X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 16:34:45 -0000 Le 15/09/2006 18:05, Gleb Smirnoff a écrit: > H> bge0: mem 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 > H> miibus0: on bge0 > H> brgphy0: on miibus0 > H> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto > H> bge0: Ethernet address: 00:06:5b:1a:7f:4a > > Is it integrated or not? I've got exactly the same NIC and I can > try to reproduce the problem if you describe the workload. Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. -- Herve Boulouis From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 17:53: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 C297716A4C8 for ; Fri, 15 Sep 2006 17:53:50 +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 EF28643D45 for ; Fri, 15 Sep 2006 17:53:49 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 9A1D022DC00; Fri, 15 Sep 2006 19:53:46 +0200 (CEST) Date: Fri, 15 Sep 2006 19:53:46 +0200 To: freebsd-stable@freebsd.org Message-ID: <20060915175346.GF15445@leia.lambermont.dyndns.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200609151616.k8FGG23C065997@fire.jhs.private> User-Agent: Mutt/1.4.2.2i From: hans@lambermont.dyndns.org (Hans Lambermont) Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 17:53:50 -0000 Julian H. Stacey wrote: > Stable is a misnomer that harms FreeBSD somewhat. I agree. > A promoter of FreeBSD I know has long encouraged people to upgrade > from release to stable. Some don't & won't realise Stable is Not > necessarily Stable, & may get burnt. Much of the world speaks English > only as a 2nd language. They won't benefit from the double trouble of > foreign + weird BSD geek speak: "Stable isn't Stable ? Yes or No !" > "It's stable, but it's OK to crash ? - I'll go Linux !" > > Imagine a boat labelled Stable: It sinks. The designers claim: "Tough! > We left the Application Interface (routes to bars & toilets) stable, > but changed other stuff. Hey ! Stable never meant Stable ! > > It'd be some work to eradicate the misnomer, but the name's perhaps > less entrenched than one might guess, eg: > ftp ftp.freebsd.org > cd /pub/FreeBSD > dir > lrwxr-xr-x 1 ftpuser ftpusers 19 Mar 24 14:58 FreeBSD-stable -> branches/4.0-stable > cd FreeBSD-stable > 550 No such directory. Why not rename 'stable' into 'stable-api' ? -- Hans Lambermont From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 18:42: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 7562016A40F for ; Fri, 15 Sep 2006 18:42:41 +0000 (UTC) (envelope-from scrappy@freebsd.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECFDD43D45 for ; Fri, 15 Sep 2006 18:42:40 +0000 (GMT) (envelope-from scrappy@freebsd.org) Received: from localhost (unknown [200.46.204.128]) by hub.org (Postfix) with ESMTP id 1C6693A4632; Fri, 15 Sep 2006 15:42:35 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 82615-01; Fri, 15 Sep 2006 18:41:04 +0000 (UTC) Received: from ganymede.hub.org (blk-137-86-60.eastlink.ca [24.137.86.60]) by hub.org (Postfix) with ESMTP id D05F43A464A; Fri, 15 Sep 2006 15:41:00 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id D0C504AB72; Fri, 15 Sep 2006 15:41:04 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id CFF7B34122; Fri, 15 Sep 2006 15:41:04 -0300 (ADT) Date: Fri, 15 Sep 2006 15:41:04 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: freebsd@ganymede.hub.org To: Hans Lambermont In-Reply-To: <20060915175346.GF15445@leia.lambermont.dyndns.org> Message-ID: <20060915153624.X1031@ganymede.hub.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 18:42:41 -0000 On Fri, 15 Sep 2006, Hans Lambermont wrote: > Julian H. Stacey wrote: > >> Stable is a misnomer that harms FreeBSD somewhat. > > I agree. > >> A promoter of FreeBSD I know has long encouraged people to upgrade >> from release to stable. Some don't & won't realise Stable is Not >> necessarily Stable, & may get burnt. Much of the world speaks English >> only as a 2nd language. They won't benefit from the double trouble of >> foreign + weird BSD geek speak: "Stable isn't Stable ? Yes or No !" >> "It's stable, but it's OK to crash ? - I'll go Linux !" >> >> Imagine a boat labelled Stable: It sinks. The designers claim: "Tough! >> We left the Application Interface (routes to bars & toilets) stable, >> but changed other stuff. Hey ! Stable never meant Stable ! >> >> It'd be some work to eradicate the misnomer, but the name's perhaps >> less entrenched than one might guess, eg: >> ftp ftp.freebsd.org >> cd /pub/FreeBSD >> dir >> lrwxr-xr-x 1 ftpuser ftpusers 19 Mar 24 14:58 FreeBSD-stable -> branches/4.0-stable >> cd FreeBSD-stable >> 550 No such directory. > > Why not rename 'stable' into 'stable-api' ? Or rename it what it is: 6.x-BETA Where x == the next -RELEASE ... But, I'm just curious here ... for all of the talk going around about this whole issue, how many ppl have truly ever been bitten by an unstable -STABLE? And for those that have, how long did it take to get help from a developer to get it fixed? In the case that started this thread, it seems to be that the developer fixed his mistake fairly quickly, which is what one would expect ... it shouldn't be so much that he *broke* -STABLE (shit happens, do you want your money back?), but it should be 'was he around to reverse his mistake in a reasonable amount of time?' ... ? ---- 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 Fri Sep 15 18:47: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 1A70916A47B for ; Fri, 15 Sep 2006 18:47:01 +0000 (UTC) (envelope-from martin@gneto.com) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0755643D62 for ; Fri, 15 Sep 2006 18:46:59 +0000 (GMT) (envelope-from martin@gneto.com) Received: from ua-83-227-181-30.cust.bredbandsbolaget.se ([83.227.181.30] [83.227.181.30]) by mxfep01.bredband.com with ESMTP id <20060915184658.FHKR28839.mxfep01.bredband.com@ua-83-227-181-30.cust.bredbandsbolaget.se> for ; Fri, 15 Sep 2006 20:46:58 +0200 Received: from [192.168.10.11] (euklides.gneto.com [192.168.10.11]) by ua-83-227-181-30.cust.bredbandsbolaget.se (Postfix) with ESMTP id EA8B267922 for ; Fri, 15 Sep 2006 20:46:57 +0200 (CEST) Message-ID: <450AF521.60003@gneto.com> Date: Fri, 15 Sep 2006 20:46:57 +0200 From: Martin Nilsson User-Agent: Thunderbird 1.5.0.5 (X11/20060804) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> In-Reply-To: <20060915175346.GF15445@leia.lambermont.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 18:47:01 -0000 Hans Lambermont wrote: > > Why not rename 'stable' into 'stable-api' ? .. or just stop calling it STABLE and call it RELENG_6 instead, which is what you are actually fetching from cvs :-) /Martin From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 18: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 BF3D216A403; Fri, 15 Sep 2006 18:59:57 +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 8875343D5E; Fri, 15 Sep 2006 18:59:56 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 895C422DC00; Fri, 15 Sep 2006 20:59:55 +0200 (CEST) Date: Fri, 15 Sep 2006 20:59:55 +0200 To: "Marc G. Fournier" Message-ID: <20060915185955.GG15445@leia.lambermont.dyndns.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <20060915153624.X1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060915153624.X1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i From: hans@lambermont.dyndns.org (Hans Lambermont) Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 18:59:57 -0000 Marc G. Fournier wrote: > On Fri, 15 Sep 2006, Hans Lambermont wrote: >>Julian H. Stacey wrote: >>>Stable is a misnomer that harms FreeBSD somewhat. ... >>Why not rename 'stable' into 'stable-api' ? > > Or rename it what it is: > > 6.x-BETA > > Where x == the next -RELEASE ... Also fine by me :) I followed this long thread in slight amazement, but the 'what is stable' confusion is very recognizable. I'm open for changing the name. > In the case that started this thread, it seems to be that the > developer fixed his mistake fairly quickly, which is what one would > expect ... it shouldn't be so much that he *broke* -STABLE (shit > happens, do you want your money back?), but it should be 'was he > around to reverse his mistake in a reasonable amount of time?' ... ? I think the answer is yes (and always has been afaik). regards, Hans Lambermont From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 19:03: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 337E816A407 for ; Fri, 15 Sep 2006 19:03:28 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from opus.cse.buffalo.edu (opus.cse.Buffalo.EDU [128.205.32.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41C1C43D76 for ; Fri, 15 Sep 2006 19:03:27 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from localhost.cse.buffalo.edu (localhost.cse.buffalo.edu [127.0.0.1]) by opus.cse.buffalo.edu (8.13.8/8.12.4) with ESMTP id k8FJ3Qs6059036 for ; Fri, 15 Sep 2006 15:03:26 -0400 (EDT) From: Ken Smith To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9W+Sa+j49CMpXnwJIGde" Organization: U. Buffalo CSE Department Date: Fri, 15 Sep 2006 15:03:25 -0400 Message-Id: <1158347005.60026.65.camel@opus.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port Subject: FreeBSD 6.2 Release Cycle X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 19:03:28 -0000 --=-9W+Sa+j49CMpXnwJIGde Content-Type: text/plain Content-Transfer-Encoding: quoted-printable FYI - we have begun the release cycle for FreeBSD-6.2. Code freeze on the RELENG_6 branch started last week. For people in the habit of tracking RELENG_6 you will start to notice various pieces of it that start saying "6.2" for version numbers (despite 6.2 not being officially released) as we progress through the release cycle. Sorry if that causes a bit of confusion or problems but we need to do this as part of the BETA/RC testing that gets done. Bumping things like the FreeBSD_version to reflect 6.2 now gives the ports folks a chance to get ready for it as part of their preparations for the release, etc. The current targets for the BETAs/RCs/Release are: BETA1 Sep. 17 BETA2 Oct. 1 RC1 Oct. 15 RC2 Oct. 29 RELEASE Nov. 13 We'll give a bit more information along with the BETA1 announcement. --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-9W+Sa+j49CMpXnwJIGde Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFCvj9/G14VSmup/YRAgDPAJ45QB8aXO6lWpW82FABkNxq27DK4gCfZT/9 ASxqag3h1i4SEhmFvs7ja3E= =2aqz -----END PGP SIGNATURE----- --=-9W+Sa+j49CMpXnwJIGde-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 19:11: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 015CC16A40F; Fri, 15 Sep 2006 19:11:22 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr9.xs4all.nl (smtp-vbr9.xs4all.nl [194.109.24.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 451A143D46; Fri, 15 Sep 2006 19:11:20 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr9.xs4all.nl (8.13.6/8.13.6) with ESMTP id k8FJBJNV033639; Fri, 15 Sep 2006 21:11:19 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id CD0E5B826; Fri, 15 Sep 2006 21:11:18 +0200 (CEST) Date: Fri, 15 Sep 2006 21:11:18 +0200 From: Roland Smith To: "Marc G. Fournier" Message-ID: <20060915191118.GA67073@slackbox.xs4all.nl> Mail-Followup-To: "Marc G. Fournier" , Hans Lambermont , freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <20060915153624.X1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20060915153624.X1031@ganymede.hub.org> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 19:11:22 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: > But, I'm just curious here ... for all of the talk going around about thi= s=20 > whole issue, how many ppl have truly ever been bitten by an unstable=20 > -STABLE? And for those that have, how long did it take to get help from = a=20 > developer to get it fixed? After installing from 5.4-RELEASE, I've tracked stable, and I haven't had any real problems. This is a desktop system, not a server, BTW. Maybe it depends on the frequency of updating? I usually update after there has been a security advisory that affects me. Otherwise, if it ain't broken... =20 > shouldn't be so much that he *broke* -STABLE (shit happens, do you want= =20 > your money back?),=20 :-) Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCvrWEnfvsMMhpyURAs6XAKCEiZ/TqtCnYrwzpJk8ZfOjX/rCbwCaA3By veupDsiuAXRSO8u5W0g//rU= =uO3J -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 19:16: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 E618416A403 for ; Fri, 15 Sep 2006 19:16:10 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AE7B43D45 for ; Fri, 15 Sep 2006 19:16:10 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr12.xs4all.nl (8.13.6/8.13.6) with ESMTP id k8FJG3kH027520; Fri, 15 Sep 2006 21:16:04 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 4D347B826; Fri, 15 Sep 2006 21:16:03 +0200 (CEST) Date: Fri, 15 Sep 2006 21:16:03 +0200 From: Roland Smith To: Martin Nilsson Message-ID: <20060915191603.GB67073@slackbox.xs4all.nl> Mail-Followup-To: Martin Nilsson , freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <450AF521.60003@gneto.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <450AF521.60003@gneto.com> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 19:16:11 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 15, 2006 at 08:46:57PM +0200, Martin Nilsson wrote: > Hans Lambermont wrote: > > > >Why not rename 'stable' into 'stable-api' ? >=20 > .. or just stop calling it STABLE and call it RELENG_6 instead, which is= =20 > what you are actually fetching from cvs :-) That's a good idea, IMHO. When I started with FreeBSD I found the difference between the branch names and cvs tags confusing. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --K8nIJk4ghYZn606h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFCvvzEnfvsMMhpyURAilUAKCgs8l36gal1NrKAIIyiUmTjN4cAgCfadcl +OZ1e9CZpZaIaVf66AKLOVc= =W7h4 -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 19:33: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 E6FA616A412; Fri, 15 Sep 2006 19:33:06 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B056F43D5D; Fri, 15 Sep 2006 19:33:02 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id k8FJX0uR017876; Fri, 15 Sep 2006 12:33:01 -0700 From: Kent Stewart To: freebsd-stable@freebsd.org Date: Fri, 15 Sep 2006 12:33:00 -0700 User-Agent: KMail/1.9.3 References: <20060911001722.GR611@ra.aabs> <20060915140531.GQ27667@FreeBSD.org> <20060915162840.GU611@ra.aabs> In-Reply-To: <20060915162840.GU611@ra.aabs> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200609151233.01137.kstewart@owt.com> Cc: Gleb Smirnoff , Herve Boulouis Subject: Re: bge watchdog timeouts still happening X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 19:33:07 -0000 On Friday 15 September 2006 09:28, Herve Boulouis wrote: > Le 15/09/2006 18:05, Gleb Smirnoff a =E9crit: > > H> bge0: mem > > 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 H> miibus0: > bus> on bge0 > > H> brgphy0: on miibus0 > > H> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > > 1000baseTX, 1000baseTX-FDX, auto H> bge0: Ethernet address: > > 00:06:5b:1a:7f:4a > > > > Is it integrated or not? I've got exactly the same NIC and I can > > try to reproduce the problem if you describe the workload. > > Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. It seems to be at the top of the tree somewhere because people are also=20 seeing the watchdog timeouts on em and I get them on the gigabit re's. I got them downloading the kde-3.5.4 distfiles on a 768kb DSL line. I=20 had setiathome running, which keeps the cpu useage close to 100%. Kent =2D-=20 Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 19:55: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 C09E916A403; Fri, 15 Sep 2006 19:55:34 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 610CB43D60; Fri, 15 Sep 2006 19:55:27 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-71-254-64-121.ronkva.east.verizon.net [71.254.64.121]) by gromit.dlib.vt.edu (8.13.6/8.13.4) with ESMTP id k8FJtPpL005849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 15 Sep 2006 15:55:26 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.8/8.13.8) with ESMTP id k8FJtOmM004092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 15 Sep 2006 15:55:25 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.8/8.13.8/Submit) id k8FJtOVU004091; Fri, 15 Sep 2006 15:55:24 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) From: Paul Mather To: Kent Stewart In-Reply-To: <200609151233.01137.kstewart@owt.com> References: <20060911001722.GR611@ra.aabs> <20060915140531.GQ27667@FreeBSD.org> <20060915162840.GU611@ra.aabs> <200609151233.01137.kstewart@owt.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 15 Sep 2006 15:55:23 -0400 Message-Id: <1158350123.3921.8.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 FreeBSD GNOME Team Port X-Greylist: Sender succeeded STARTTLS authentication, not delayed by milter-greylist-2.0.2 (gromit.dlib.vt.edu [128.173.49.29]); Fri, 15 Sep 2006 15:55:26 -0400 (EDT) Cc: Gleb Smirnoff , freebsd-stable@freebsd.org, Herve Boulouis Subject: Re: bge watchdog timeouts still happening X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 19:55:34 -0000 On Fri, 2006-09-15 at 12:33 -0700, Kent Stewart wrote: > On Friday 15 September 2006 09:28, Herve Boulouis wrote: > > Le 15/09/2006 18:05, Gleb Smirnoff a =E9crit: > > > H> bge0: mem > > > 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 H> miibus0: > > bus> on bge0 > > > H> brgphy0: on miibus0 > > > H> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > > > 1000baseTX, 1000baseTX-FDX, auto H> bge0: Ethernet address: > > > 00:06:5b:1a:7f:4a > > > > > > Is it integrated or not? I've got exactly the same NIC and I can > > > try to reproduce the problem if you describe the workload. > > > > Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. >=20 > It seems to be at the top of the tree somewhere because people are also=20 > seeing the watchdog timeouts on em and I get them on the gigabit re's. >=20 > I got them downloading the kde-3.5.4 distfiles on a 768kb DSL line. I=20 > had setiathome running, which keeps the cpu useage close to 100%. FWIW, I get repeated "watchdog timeout" errors on 6-STABLE with a dc-based Cardus NIC (Netgear FA511). The worst behaviour I observed was under heavy NFS load, with the link being unavailable for extended periods of time. Mostly, though, the problem manifests itself when the card is inserted and the interface is trying to be brought up via DHCP using dhclient, as if the NIC is not being initialised properly, perhaps. I don't know if this is the same problem, but I thought I'd mention it. Cheers, Paul. --=20 e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 21:47: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 18F9B16A40F for ; Fri, 15 Sep 2006 21:47:01 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id E565A43D72 for ; Fri, 15 Sep 2006 21:46:52 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k8FLkpAr067371 for ; Fri, 15 Sep 2006 21:46:51 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k8FLkoXR067368 for ; Fri, 15 Sep 2006 21:46:51 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Fri, 15 Sep 2006 21:46:50 +0000 (GMT) From: Michael Abbott To: freebsd-stable@freebsd.org In-Reply-To: <20060915191603.GB67073@slackbox.xs4all.nl> Message-ID: <20060915214303.J67333@saturn.araneidae.co.uk> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <450AF521.60003@gneto.com> <20060915191603.GB67073@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Fri, 15 Sep 2006 21:47:01 -0000 On Fri, 15 Sep 2006, Roland Smith wrote: > On Fri, Sep 15, 2006 at 08:46:57PM +0200, Martin Nilsson wrote: >> Hans Lambermont wrote: >> .. or just stop calling it STABLE and call it RELENG_6 instead > That's a good idea, IMHO. When I started with FreeBSD I found the > difference between the branch names and cvs tags confusing. Let me second that. I hadn't realised that STABLE==RELENG_n (where n is the current version number) until very recently, and I've seen the "STABLE isn't stable" thing crop up over and over again over the last few years, both on mailing lists and IRC. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 15 23:52: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 01D8F16A40F for ; Fri, 15 Sep 2006 23:52:17 +0000 (UTC) (envelope-from kmd@milshop.ru) Received: from ug-out-f131.google.com (ug-out-f131.google.com [66.249.92.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53D7043D45 for ; Fri, 15 Sep 2006 23:52:15 +0000 (GMT) (envelope-from kmd@milshop.ru) Received: by ug-out-f131.google.com with SMTP id 23so10653ugm for ; Fri, 15 Sep 2006 16:52:15 -0700 (PDT) Received: by 10.66.220.17 with SMTP id s17mr5716304ugg; Fri, 15 Sep 2006 16:52:14 -0700 (PDT) Received: by 10.66.252.14 with HTTP; Fri, 15 Sep 2006 16:52:14 -0700 (PDT) Message-ID: <519867a90609151652t1905d56n30dde41485e8ec11@mail.gmail.com> Date: Sat, 16 Sep 2006 03:52:14 +0400 From: "Eugene Kazarinov" Sender: kmd@milshop.ru To: "Craig Boston" , "Ronald Klop" , freebsd-stable@freebsd.org In-Reply-To: <20060915145858.GA14416@nowhere> MIME-Version: 1.0 References: <20060915145858.GA14416@nowhere> X-Google-Sender-Auth: edb745acfe28a719 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 15 Sep 2006 23:52:17 -0000 Something with em0 is really wrong. I dont get timeouts, but.... Before cvsup I had 6.0-PRERELEASE and didn't have a problem. Now I have "FreeBSD 6.2-PRERELEASE #8: Fri Sep 15 03:44:49 MSD 2006" and the problem is so: (On machine I have LARGE_NAT, em0, em1, em2) on fresh system ping to www.ru from client computer (goes to inet via nat) is 3-5ms after few hours (i see it in the night) then traffic is smaller ping to www.ru is 11-12 ms. Why? after reboot it still gut for a few ours. FreeBSD/amd64 kernel with options DEVICE_POLLING options HZ=2500 with HZ=1000 and without DEVICE_POLLING nothing changes - 11-12 still goes after few hours. PS Should I downgrade to 6.0-RELEASE or earlier or tonight cvsup updates could resolve a problem (files sounds like tcp...): Checkout src/sys/contrib/ipfilter/netinet/ip_nat.h Edit src/sys/netinet/in_pcb.c Edit src/sys/netinet/tcp_input.c Edit src/sys/netinet/tcp_subr.c Edit src/sys/netinet/tcp_timer.c Edit src/sys/netinet/tcp_timer.h Edit src/sys/netinet/tcp_var.h Edit src/sys/sys/param.h Edit src/usr.sbin/pkg_install/add/main.c PPS Now I rebuild kernels and .... tomorrow night will se. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 00:43: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 8AD0716A416; Sat, 16 Sep 2006 00:43:52 +0000 (UTC) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (dsl231-043-140.sea1.dsl.speakeasy.net [216.231.43.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DF6743D66; Sat, 16 Sep 2006 00:43:47 +0000 (GMT) (envelope-from kline@sage.thought.org) Received: from sage.thought.org (kline@localhost [127.0.0.1]) by sage.thought.org (8.13.6/8.12.10) with ESMTP id k8G0hjeT015616; Fri, 15 Sep 2006 17:43:46 -0700 (PDT) (envelope-from kline@sage.thought.org) Received: (from kline@localhost) by sage.thought.org (8.13.6/8.13.1/Submit) id k8G0hj4F015615; Fri, 15 Sep 2006 17:43:45 -0700 (PDT) (envelope-from kline) Date: Fri, 15 Sep 2006 17:43:45 -0700 From: Gary Kline To: "Marc G. Fournier" Message-ID: <20060916004345.GA15415@thought.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <20060915153624.X1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060915153624.X1031@ganymede.hub.org> X-Organization: Thought Unlimited. Public service Unix since 1986. X-Of_Interest: Observing twenty years of service to the Unix community User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Sat, 16 Sep 2006 00:43:52 -0000 On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: > On Fri, 15 Sep 2006, Hans Lambermont wrote: > > >Julian H. Stacey wrote: > > > >>Stable is a misnomer that harms FreeBSD somewhat. > > > >I agree. > > > >>A promoter of FreeBSD I know has long encouraged people to upgrade > >>from release to stable. Some don't & won't realise Stable is Not > >>necessarily Stable, & may get burnt. Much of the world speaks English > >>only as a 2nd language. They won't benefit from the double trouble of > >>foreign + weird BSD geek speak: "Stable isn't Stable ? Yes or No !" > >>"It's stable, but it's OK to crash ? - I'll go Linux !" > >> > >>Imagine a boat labelled Stable: It sinks. The designers claim: "Tough! > >>We left the Application Interface (routes to bars & toilets) stable, > >>but changed other stuff. Hey ! Stable never meant Stable ! > >> You've got a good point. Wouldn't be be best to merge the mythical last-bug from x-BETA+ into x and have release-x be the (abs) most stable *for that release*? I have generally run -STABLE ((now/then -RELEASE)); it is to the developers' credit [[all get 5 stars from here!]] that -STABLE has run so flawlessly until now. ---Yeah, I am speaking only for myself; what else :-). > > Or rename it what it is: > > 6.x-BETA > > Where x == the next -RELEASE ... > > But, I'm just curious here ... for all of the talk going around about this > whole issue, how many ppl have truly ever been bitten by an unstable > -STABLE? And for those that have, how long did it take to get help from a > developer to get it fixed? Indeed. This snafu didn't bite me because I was at 5.4... and right, hat's off and cheers for Pawel Dawidek. Everyone shouldbe as consciencious --it'd be a vastly better world (.) gary > > In the case that started this thread, it seems to be that the developer > fixed his mistake fairly quickly, which is what one would expect ... it > shouldn't be so much that he *broke* -STABLE (shit happens, do you want > your money back?), but it should be 'was he around to reverse his mistake > in a reasonable amount of time?' ... ? > -- Gary Kline kline@thought.org www.thought.org Public service Unix From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 01:31: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 C21C416A40F for ; Sat, 16 Sep 2006 01:31:42 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A01F43D45 for ; Sat, 16 Sep 2006 01:31:42 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so3989940pye for ; Fri, 15 Sep 2006 18:31:41 -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=jB7XNmXMcTRxOiL534S8jr9Onx/MhX3eK1SxWzJeDghErQC1/9pMIVsnD0dW8ouSef2QUxEVPcvqQz75/IQVPLi+k3ZPb90aTqQxz04X/2e6bksgj4xobuxBcnUjKDdRMDjT19zC41XNiDR8J0srFOV19XV8ShJhJPdJClV86Y0= Received: by 10.35.50.1 with SMTP id c1mr18486286pyk; Fri, 15 Sep 2006 18:31:41 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Fri, 15 Sep 2006 18:31:41 -0700 (PDT) Message-ID: <2a41acea0609151831waba112cubaf959513ec34a38@mail.gmail.com> Date: Fri, 15 Sep 2006 18:31:41 -0700 From: "Jack Vogel" To: "David C. Myers" In-Reply-To: <4509EE70.1040907@aedifice.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> <4509EE70.1040907@aedifice.net> Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 01:31:42 -0000 On 9/14/06, David C. Myers wrote: > > > watchdogs mean that the transmit ring is not being cleaned, so the > > question is what is your machine doing at 100% cpu, if its that busy > > the network watchdogs may just be a side effect and not the real > > problem? > > > I get them with a completely idle machine. My home directory is mounted > via NFS (from FreeBSD 6.1 on an amd64 machine), and with the kernel from > earlier this week, the machine would just hang for 30 seconds to a > couple of minutes. A slew of "watchdog timeout" messages would appear. > Then I'd get a moment's responsiveness out of the machine, then > another long wait, then a moment's responsiveness, then a long wait... > > The machine would never recover from this cycle (at least, so far as I > was patient enough to wait). > > Going back to a kernel dated late July resolved everything. > > Someone else asked me for the hardware version of my em0 board... > > > em0@pci2:10:0: class=0x020000 card=0x002e8086 chip=0x100e8086 rev=0x02 > hdr=0x00 vendor = 'Intel Corporation' > device = '82540EM Gigabit Ethernet Controller' > class = network > subclass = ethernet Could you perhaps go back to the kernel you say was stable and then drop in the latest em driver? Or if that has issues building do it the other way around, take the em driver from the build that gave you no problems and put it on this kernel you are running now? It would be helpful to know if this is a driver problem or something in the stack. Cheers, Jack From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 01:38: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 C861216A403 for ; Sat, 16 Sep 2006 01:38:29 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53B9B43D46 for ; Sat, 16 Sep 2006 01:38:29 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so3992106pye for ; Fri, 15 Sep 2006 18:38:28 -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=tKsDhpFtqXA9tJlvJS45/jao9By2UwNb7c93gzIDBwem95PmI5xJ5m8o2HtvXQwWKvRgXfsrK3wj1LcExOa+iseYropP/RoveVTALSAmUyY1FiWFXExGqnce9Hrtd1o8zbP4j01P29aojERTYEw191EEJf/GYJmHjqxwDZ9rE+Q= Received: by 10.35.66.12 with SMTP id t12mr3904268pyk; Fri, 15 Sep 2006 18:38:28 -0700 (PDT) Received: by 10.35.119.1 with HTTP; Fri, 15 Sep 2006 18:38:28 -0700 (PDT) Message-ID: <2a41acea0609151838r57125657p2b20499d30f694b4@mail.gmail.com> Date: Fri, 15 Sep 2006 18:38:28 -0700 From: "Jack Vogel" To: "Martin Nilsson" In-Reply-To: <450A952C.9080600@gneto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> <4509E4CD.8050102@visi.com> <450A952C.9080600@gneto.com> Cc: freebsd-stable@freebsd.org Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 01:38:29 -0000 On 9/15/06, Martin Nilsson wrote: > I'm also seeing these on a Supermicro PDSMi board with a recent stable. > Please tell me what debugging info that is needed to fix this. > > /Martin > > > FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sun Sep 10 > 17:43:15 CEST 2006 root@mailbox:/usr/obj-local/usr/src/sys/SMP amd64 > > lspci -v output: > > 04:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet > Controller (Copper) (rev 03) > Subsystem: Super Micro Computer Inc Unknown device 108c > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at ed200000 (32-bit, non-prefetchable) > I/O ports at 4000 > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > Queue=0/0 Enable- > Capabilities: [e0] Express Endpoint IRQ 0 > > 05:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet > Controller > Subsystem: Super Micro Computer Inc Unknown device 109a > Flags: bus master, fast devsel, latency 0, IRQ 17 > Memory at ed300000 (32-bit, non-prefetchable) > I/O ports at 5000 > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > Queue=0/0 Enable- > Capabilities: [e0] Express Endpoint IRQ 0 Martin, do you see similar problems using either port, I ask because this system may be similar to one that Yahoo has and there was only a problem with one port and not the other, can you check this out please? Jack From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 02:34: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 AF23D16A407 for ; Sat, 16 Sep 2006 02:34:54 +0000 (UTC) (envelope-from rblayzor@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 317B2445B8 for ; Sat, 16 Sep 2006 02:34:54 +0000 (GMT) (envelope-from rblayzor@inoc.net) Received: from [172.16.16.54] (cpe-24-29-66-248.nycap.res.rr.com [24.29.66.248]) by mx1-a.inoc.net (build v6.3.3) with ESMTP id 78737363 for ; Sat, 16 Sep 2006 02:34:53 +0000 (UTC) Message-ID: <450B62C9.5000706@inoc.net> Date: Fri, 15 Sep 2006 22:34:49 -0400 From: Robert Blayzor Organization: Independent Network Operations Consortium, LLC User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 02:34:54 -0000 Anyone know if there is a working driver for either the QLogic QLA4050C or Adaptec 7211C iSCSI HBAs? I know there is a software based initiator in the works, but having a driver for the iSCSI HBA's would provide a great alternative to running diskless or FC SAN. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC Press Ctrl-Alt-Del now for IQ test. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 03:32: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 E61ED16A417 for ; Sat, 16 Sep 2006 03:32:44 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id D5FCE43D49 for ; Sat, 16 Sep 2006 03:32:43 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 21419 invoked from network); 16 Sep 2006 03:32:42 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 16 Sep 2006 03:32:42 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 15 Sep 2006 22:33:16 -0500 (CDT) From: Mike Silbersack To: Marcelo Gardini do Amaral In-Reply-To: <20060915145120.GA93074@registro.br> Message-ID: <20060915223211.R65248@odysseus.silby.com> References: <2a41acea0608301145j7bbed961j33ce903a27d8963d@mail.gmail.com> <20060904130827.GE12975@registro.br> <20060911195521.GD63300@registro.br> <20060913182019.R50147@fledge.watson.org> <20060913182457.W50147@fledge.watson.org> <20060914175049.GH49126@registro.br> <450A2A6E.3040408@yandex.ru> <20060915145120.GA93074@registro.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, "Andrey V. Elsukov" , Robert Watson , freebsd-stable@freebsd.org Subject: Re: DNS query performance X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 03:32:45 -0000 Although it sounds silly, could you try recompiling 6.1 and 7.0 with a non-SMP kernel and see how they perform? That would at least tell us if it's a general performance problem in 6.x and 7.x, or if SMP is somehow hurting performance in this case. Mike "Silby" Silbersack From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 05:46: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 023DF16A40F for ; Sat, 16 Sep 2006 05:46:55 +0000 (UTC) (envelope-from umbilical.blisters@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EB0E43D4C for ; Sat, 16 Sep 2006 05:46:54 +0000 (GMT) (envelope-from umbilical.blisters@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so4062587pye for ; Fri, 15 Sep 2006 22:46:53 -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=Ui9EnUw9wQ6IzPHCQdoAO0er2jOWa52/J+AYAN42bAIBGbevIE6gxY9CAIuHJxJbT1vARKj+BdPiE9faYU7zn6bG46/12AcyMGZAOu71Xo+CYTIUI6zHMVfkc8HL/xXMs/5u94Vl0K0V51NUdLa2SEXX+kBY9KKeR2BXyr3fMg4= Received: by 10.35.93.1 with SMTP id v1mr18820578pyl; Fri, 15 Sep 2006 22:46:53 -0700 (PDT) Received: by 10.35.126.16 with HTTP; Fri, 15 Sep 2006 22:46:53 -0700 (PDT) Message-ID: <40c4bb930609152246m190e5359o79efaacae8571d47@mail.gmail.com> Date: Sat, 16 Sep 2006 00:46:53 -0500 From: "Alex Salazar" To: "Conrad Burger" In-Reply-To: <88B5DDE8C1A06741B754B910DE2DEFBB010783ED@HERMES.swistgroup.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <88B5DDE8C1A06741B754B910DE2DEFBB010783ED@HERMES.swistgroup.com> Cc: freebsd-stable@freebsd.org Subject: Re: Several issues on Dell 1950/2950 servers (6-STABLE and 7-CURRENT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 05:46:55 -0000 On 9/15/06, Conrad Burger wrote: > Hi > > Has anyone been able to solve the problem with the bce driver on 6.1-stab= le? > > I am running 6.1-stable(200609013)AMD64 on a Dell 1950 with a SMP kernel. > > The system boots up fine. When I copy data to an nfs mount the bce networ= k > interface times out and then resets. It never recovers from this state. > > From /var/log/messages----------- > Sep 13 05:01:13 gold kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): W= atchdog > timeout occurred, resetting! > Sep 13 05:01:13 gold kernel: bce0: link state changed to DOWN > Sep 13 05:01:16 gold kernel: bce0: link state changed to UP > Sep 13 05:02:41 gold kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): W= atchdog > timeout occurred, resetting! > Sep 13 05:02:41 gold kernel: bce0: link state changed to DOWN > Sep 13 05:02:44 gold kernel: bce0: link state changed to UP > > Any help would be appreciated. > > Regards > Conrad > I was almost sure this problem had been solved by the 6-STABLE version of sys/dev/bce/, a month ago, or so. I can't back it up, however, since I'm currently using 7-CURRENT (i386) on my PE 1950, and this behaviour is n= ot present in this FreeBSD version. By the way, is your server equipped with a LSI SAS 5/i controller, or Dell PERC 5/i? --=20 Alex Salazar BSD M=E9xico www.bsd.org.mx From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 05:52: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 B008B16A412 for ; Sat, 16 Sep 2006 05:52:17 +0000 (UTC) (envelope-from lydianconcepts@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35ABE43D69 for ; Sat, 16 Sep 2006 05:52:14 +0000 (GMT) (envelope-from lydianconcepts@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so3331851wxd for ; Fri, 15 Sep 2006 22:52:13 -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=n4zGLKhGvi9Mes+WjCzdUv5ddCSx6CDryjE0FEwgE1HE5yVgg6G5h7UdF6x7QwvqUNhvSdeeRDmak7IcJXYYPwe+ranaruQwIzLQFiSaxlC4MBl8i+RbkqybM2pedqQDEzkSAm5P5LFE6RblC0UsVhaDyFRPFr5zW06JaLgAWDE= Received: by 10.90.78.9 with SMTP id a9mr4098951agb; Fri, 15 Sep 2006 22:52:13 -0700 (PDT) Received: by 10.90.70.14 with HTTP; Fri, 15 Sep 2006 22:52:13 -0700 (PDT) Message-ID: <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> Date: Fri, 15 Sep 2006 22:52:13 -0700 From: "Matthew Jacob" To: "Robert Blayzor" In-Reply-To: <450B62C9.5000706@inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <450B62C9.5000706@inoc.net> Cc: freebsd-stable@freebsd.org Subject: Re: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 05:52:17 -0000 There was some interest in QLogic's part a couple of years ago to get 4000 support and they contacted me, but I was pretty much uninterested in it as a project. Go poke them again and see if they want to try. Why do you think an iSCSI HBA would be of any benefit to anything other than the target mode side as a server? On 9/15/06, Robert Blayzor wrote: > Anyone know if there is a working driver for either the QLogic QLA4050C > or Adaptec 7211C iSCSI HBAs? > > I know there is a software based initiator in the works, but having a > driver for the iSCSI HBA's would provide a great alternative to running > diskless or FC SAN. > > -- > Robert Blayzor, BOFH > INOC, LLC > rblayzor\@(inoc.net|gmail.com) > PGP: 0x66F90BFC @ http://pgp.mit.edu > Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC > > Press Ctrl-Alt-Del now for IQ test. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 06:48: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 049EF16A492 for ; Sat, 16 Sep 2006 06:48:40 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 461EB43D55 for ; Sat, 16 Sep 2006 06:48:39 +0000 (GMT) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.68.98) by 209.67.61.254 with SMTP; 16 Sep 2006 06:48:38 -0000 Date: Sat, 16 Sep 2006 09:48:09 +0300 From: Nikolay Pavlov To: freebsd-stable@freebsd.org Message-ID: <20060916064809.GA59517@zone3000.net> Mail-Followup-To: Nikolay Pavlov , 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-Operating-System: FreeBSD 6.1-RELEASE Subject: loader can't load kernel on FreeBSD 6.1-p6. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 06:48:40 -0000 Hi, folks. While booting 6.1-RELEASE-p6 i have this error on /boot/loader stage: can't load kernel ls shows nothing... lsdev shows me: disk devices: disk0: BIOS drive C: disk0s1: FFS bad disklabel But when i am booting from LiveCD i see all my labels, i can mount them, i can produce read/write operations. Other thing that confused me is that when i am using second stage bootstrap file i see my root partition: FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: ?. .. .snap bin boot dev etc lib libexec mnt proc and so on... But when i am trying to boot kernel (GENERIC) directly from bootstrap i have "BTX halted" error, don't know if this actually supported. World was builded on other box and installed to this drive using tar. Here is additional information that i can get from LiveCD: root@ccv:~# fdisk /dev/ad0 ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=19679 heads=16 sectors/track=255 (4080 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=19679 heads=16 sectors/track=255 (4080 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 80293185 (39205 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 807/ head 15/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: root@ccv:~# disklabel /dev/ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 524288 0 4.2BSD 2048 16384 32776 b: 4161280 524288 swap c: 80293185 0 unused 0 0 # "raw" part, don't edit d: 2097152 4685568 4.2BSD 2048 16384 28552 e: 20971520 6782720 4.2BSD 2048 16384 28552 f: 10485760 27754240 4.2BSD 2048 16384 28552 g: 42053185 38240000 4.2BSD 2048 16384 28552 root@ccv:~# atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 7 Slave: no device present ATA channel 1: Master: no device present Slave: no device present root@ccv:~# mount /dev/iso9660/FreeSBIE on / (cd9660, local, read-only) devfs on /dev (devfs, local) /dev/md0.uzip on /usr (ufs, local, read-only) /dev/md1 on /etc (ufs, local) /dev/md2 on /usr/local/etc (ufs, local) /dev/md3 on /root (ufs, local) /dev/md4 on /var (ufs, local) /dev/md5 on /tmp (ufs, local) /dev/ad0s1a on /mnt/ufs.1 (ufs, local, read-only) /dev/ad0s1d on /mnt/ufs.2 (ufs, local, read-only) /dev/ad0s1e on /mnt/ufs.3 (ufs, local, read-only) /dev/ad0s1f on /mnt/ufs.4 (ufs, local, read-only) /dev/ad0s1g on /mnt/ufs.5 (ufs, local, read-only) root@ccv:~# ls -al /mnt/ufs.1/boot/ total 588 drwxr-xr-x 5 root wheel 512 Sep 16 00:52 . drwxr-xr-x 20 root wheel 512 Sep 15 10:05 .. -r--r--r-- 1 root wheel 7638 Sep 6 18:43 beastie.4th -r--r--r-- 1 root wheel 8192 Sep 6 18:43 boot -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot0 -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot0sio -r--r--r-- 1 root wheel 512 Sep 6 18:43 boot1 -r--r--r-- 1 root wheel 7680 Sep 6 18:43 boot2 -r--r--r-- 1 root wheel 1200 Sep 6 18:43 cdboot drwxr-xr-x 2 root wheel 512 Sep 6 18:43 defaults -r--r--r-- 1 root wheel 1741 Sep 6 18:43 device.hints -r--r--r-- 1 root wheel 2249 Sep 6 18:43 frames.4th drwxr-xr-x 2 root wheel 9216 Sep 6 18:44 kernel -r-xr-xr-x 1 root wheel 212992 Sep 6 18:43 loader -r--r--r-- 1 root wheel 7772 Sep 6 18:43 loader.4th -rw-r--r-- 1 root wheel 463 Sep 6 18:44 loader.conf -r--r--r-- 1 root wheel 15058 Sep 6 18:43 loader.help -r--r--r-- 1 root wheel 389 Sep 6 18:43 loader.rc -r--r--r-- 1 root wheel 512 Sep 6 18:43 mbr drwxr-xr-x 2 root wheel 512 Sep 6 18:41 modules -r--r--r-- 1 root wheel 215040 Sep 6 18:43 pxeboot -r--r--r-- 1 root wheel 692 Sep 6 18:43 screen.4th -r--r--r-- 1 root wheel 36440 Sep 6 18:43 support.4th root@ccv:~# ls -al /mnt/ufs.1/boot/kernel/kernel -r-xr-xr-x 1 root wheel 6640118 Sep 6 18:21 /mnt/ufs.1/boot/kernel/kernel root@ccv:~# file /mnt/ufs.1/boot/kernel/kernel /mnt/ufs.1/boot/kernel/kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped -- ========================================================================= = Best regards, Nikolay Pavlov. <<<------------------------------------ = ========================================================================= From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 07:18: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 C180C16A415 for ; Sat, 16 Sep 2006 07:18:09 +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 AE3C643D53 for ; Sat, 16 Sep 2006 07:18:08 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A4CCE.dip.t-dialin.net [84.154.76.206]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8G7I5Ts068915; Sat, 16 Sep 2006 09:18:06 +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.13.6/8.13.6) with ESMTP id k8G7I4FQ007039; Sat, 16 Sep 2006 09:18:05 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8G7I4Bd070920; Sat, 16 Sep 2006 09:18:04 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609160718.k8G7I4Bd070920@fire.jhs.private> To: hans@lambermont.dyndns.org (Hans Lambermont) In-reply-to: <20060915175346.GF15445@leia.lambermont.dyndns.org> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> Comments: In-reply-to hans@lambermont.dyndns.org (Hans Lambermont) message dated "Fri, 15 Sep 2006 19:53:46 +0200." Date: Sat, 16 Sep 2006 09:18:04 +0200 From: "Julian H. Stacey" Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Sat, 16 Sep 2006 07:18:09 -0000 Hans Lambermont wrote: > Julian H. Stacey wrote: > > Stable is a misnomer that harms FreeBSD somewhat. > Why not rename 'stable' into 'stable-api' ? Nice, an improvement on what we have :-) If enough agree, the name of this mail list could be changed for a start. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 08:54: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 E759B16A416 for ; Sat, 16 Sep 2006 08:54:28 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id E412043D6E for ; Sat, 16 Sep 2006 08:54:27 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id 96C7B81FF for ; Sat, 16 Sep 2006 10:54:25 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <450A952C.9080600@gneto.com> References: <2a41acea0609132023q2d23ac2eq4960cd93fb45a69b@mail.gmail.com> <4509E4CD.8050102@visi.com> <450A952C.9080600@gneto.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <510F40D0-FC4B-4888-8BAD-E2B69949D7DC@nordahl.net> Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sat, 16 Sep 2006 10:54:24 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.752.2) Subject: Re: em0: watchdog timeout -- resetting (6.1-STABLE) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 08:54:29 -0000 Hello, Just wanted to send a me too on this issue. Whenever it happends I can see our Cisco switch reporting the interface going down and up as well (Line Protocol). FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/ usr/obj/usr/src/sys/PT i386 em0: flags=8843 mtu 1500 options=b media: Ethernet autoselect (1000baseTX ) status: active em0@pci1:11:0: class=0x020000 card=0x10048086 chip=0x10048086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82543GC Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet (This is a add-in 64bit PCI card.) I am stress-testing -STABLE on a spare server to aid in making 6.2 as bugfree as possible. It is set up as a NFS server with two Linux NFS clients connected that is concurrently extracting 5 copies of /usr/src to it, and running a program that creates millions of files with random UID's to test for QUOTA issues. On the server I repeatedly dump the exported filesystem with snapshot and cache enabled. (dump -L -C 32 -af /dev/null ...) I'm building todays -STABLE on a different server with SMP and two em NIC's onboard, and will start similar tests on it to see if I can reproduce the watchdog timeouts there as well. -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 11:02: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 A030E16A412; Sat, 16 Sep 2006 11:02:14 +0000 (UTC) (envelope-from aturetta@commit.it) Received: from mail.logital.it (85-18-201-99.ip.fastwebnet.it [85.18.201.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF00443D53; Sat, 16 Sep 2006 11:02:10 +0000 (GMT) (envelope-from aturetta@commit.it) Received: from [151.37.26.7] (adsl-7-26.37-151.net24.it [151.37.26.7]) (authenticated bits=0) by mail.logital.it (8.13.8/8.13.8) with ESMTP id k8GB1nQx009207; Sat, 16 Sep 2006 13:01:57 +0200 (CEST) (envelope-from aturetta@commit.it) Message-ID: <450BD996.8090104@commit.it> Date: Sat, 16 Sep 2006 13:01:42 +0200 From: Angelo Turetta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b2) Gecko/20060821 SeaMonkey/1.1a MIME-Version: 1.0 To: David References: <200608200300.k7K30eH5092848@freefall.freebsd.org> <44F09E9B.5090303@commit.it> <44F10396.6000903@undermydesk.org> <44F2C9C6.7040907@commit.it> <44FDF4EC.50800@commit.it> <44F7D529.2070503@undermydesk.org> <45093A25.40401@commit.it> <44FDF4EC.50800@commit.it> <1157242244.1772.6.camel@monkey.sofsis.cl> <44DB1093.8070203@commit.it> <20060810200328.GA90274@freebsd.org.ua> <200608120731.k7C7VbXx067370@www.freebsd.org> In-Reply-To: <200608120731.k7C7VbXx067370@www.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_50,FU_FREE, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.1.5 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on mail.logital.it X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on mail.logital.it X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, bug-followup@FreeBSD.org Subject: Re: amd64/101873: Freebsd amd64 hangs on booting sata drive? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 11:02:14 -0000 David wrote: > I attempted to do a test install of FreeBSD 6.1 ISO on a new machine I was building, the specs were: > *AMD AM2 5000+ dual core > *Asus M2N32-SLI Deluxe Motherboard > *1GBx4 Mushkin ddr2 800Mhz > *750GBx4 S-ATA Seagate Barracuda Hard Drive (Tested with and without motherboard NV RAID in 0+1 mode with the same results) > *ATI Radeon 1800 video card > *standard dvd-rom > > When attempting to boot in verbose and non verbose mode the machine would hang (to the best of what I recall) on the hard drives. > >> Audit-Trail: > > From: Frank Reppin > > I've had the same experience with my brand new and shiny > amd64 equipmnent...: > > Mainboard -> ASUS M2N-E (nforce 570 - *no* SLI) Both 7.0-CURRENT-200607 and 6.1-STABLE-200607 (july) snapshots failed. The 7.0-CURRENT-200608 passed the disk probes, and indeed finished the install, but was subject to a massive interrupt storm. As of today (2006-sep-16) the problem is solved in both 7-CURRENT and 6-STABLE (soon to be 6.2-RELEASE), I verified personally with 2 home-built snapshot CDROMs. I think this PR can be closed (FIXED). http://www.freebsd.org/cgi/query-pr.cgi?pr=101873 Angelo Turetta From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 11:03: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 6930116A403 for ; Sat, 16 Sep 2006 11:03:05 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB31343D46 for ; Sat, 16 Sep 2006 11:03:03 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id 6F9D97E6F for ; Sat, 16 Sep 2006 13:02:58 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) To: freebsd-stable@freebsd.org Message-Id: Content-Type: multipart/mixed; boundary=Apple-Mail-23--291249582 From: Frode Nordahl Date: Sat, 16 Sep 2006 13:02:56 +0200 X-Mailer: Apple Mail (2.752.2) Subject: RELENG_6 Livelock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 11:03:05 -0000 --Apple-Mail-23--291249582 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hello, FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/ usr/obj/usr/src/sys/PT i386 After running some stress tests for 3 days, I wanted to remove some large directories. drwxrwxrwt 2 root wheel 34726400 Sep 16 11:43 uidtmp drwxrwxrwt 2 root wheel 75099648 Sep 3 10:59 uidtmp.bak.1 drwxrwxrwt 2 root wheel 61301760 Sep 12 23:10 uidtmp.bak.2 drwxrwxrwt 2 root wheel 56146944 Sep 15 00:35 uidtmp.bak.3 I fired up 4 copies of rm -rf that ran on separate directories and monitored the system with iostat. The directories to be removed was located in the root of an NFS export. I saw very little I/O and 100% cpu time spent in sys, so I attempted to kill off all the rm processes. However one of them seemed to be stuck. After some time the last rm process finally exited. I had another go at removing the direcotires, firing up 4 copies of rm on seperate directories simultaniously, and boom. Everything got stuck. The machine responded to ping, but nothing else but the debugger. After the system is back up, attemping to remove one of these directories still makes the system behave erraticly: CPU states: 0.0% user, 0.0% nice, 98.0% system, 0.3% interrupt, 1.7% idle Mem: 115M Active, 1667M Inact, 154M Wired, 64M Cache, 112M Buf, 2996K Free Swap: 4071M Total, 4071M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 929 root 1 -8 0 1284K 592K biord 7:51 102.93% rm dmesg, output from debugger and kernel config attached -- Frode Nordahl --Apple-Mail-23--291249582 Content-Transfer-Encoding: 7bit Content-Type: text/plain; x-unix-mode=0644; x-mac-hide-extension=yes; name=dmesg.txt Content-Disposition: attachment; filename=dmesg.txt GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb 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.2-PRERELEASE #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/usr/obj/usr/src/sys/PT Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (999.72-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x387fbff real memory = 2147418112 (2047 MB) avail memory = 2096590848 (1999 MB) ACPI APIC Table: ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 31 acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x404-0x407 on acpi0 acpi_ec0: port 0xca6,0xca7 on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 2.0 (no driver attached) fxp0: port 0x1400-0x143f mem 0xf0001000-0xf0001fff,0xf0100000-0xf01fffff irq 18 at device 3.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:d0:b7:b8:1d:f6 isab0: port 0x580-0x58f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x374-0x377,0x1440-0x144f at device 15.1 on pci0 ata0: on atapci0 ata2: on atapci0 pcib1: on acpi0 pci1: on pcib1 ahc0: port 0x1800-0x18ff mem 0xf2010000-0xf2010fff irq 16 at device 4.0 on pci1 ahc0: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x2000-0x20ff mem 0xf2011000-0xf2011fff irq 17 at device 4.1 on pci1 ahc1: [GIANT-LOCKED] aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs pcib2: at device 10.0 on pci1 pci2: on pcib2 pcib3: at device 0.0 on pci2 pci3: on pcib3 amr0: mem 0xf4000000-0xf7ffffff irq 20 at device 0.0 on pci3 amr0: delete logical drives supported by controller amr0: Firmware 111U, BIOS F320, 64MB RAM pci2: at device 1.0 (no driver attached) em0: mem 0xf2020000-0xf203ffff,0xf2000000-0xf200ffff irq 21 at device 11.0 on pci1 em0: Ethernet address: 00:03:47:9a:f2:05 em0: [FAST] acpi_tz0: on acpi0 acpi_tz1: on acpi0 acpi_tz2: on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc97ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 999721181 Hz quality 800 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 561184MB (1149304832 sectors) RAID 5 (optimal) em0: link state changed to UP Trying to mount root from ufs:/dev/amrd0s1a WARNING: / was not properly dismounted --Apple-Mail-23--291249582 Content-Transfer-Encoding: 7bit Content-Type: text/plain; x-unix-mode=0644; name=debugger.txt Content-Disposition: attachment; filename=debugger.txt KDB: enter: Line break on console [thread pid 15042 tid 100144 ] Stopped at kdb_enter+0x2b: nop db> where Tracing pid 15042 tid 100144 td 0xcfb11d80 kdb_enter(c0921739) at kdb_enter+0x2b siointr1(c6554000) at siointr1+0xce siointr(c6554000) at siointr+0x38 intr_execute_handlers(c63854c4,ecfce8f8,4,ecfce950,c087f853,...) at intr_execute_handlers+0xe1 lapic_handle_intr(38) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc07d79dc, esp = 0xecfce93c, ebp = 0xecfce950 --- ufsdirhash_adjfree(ca780200,a9d720,fffffff0) at ufsdirhash_adjfree+0x80 ufsdirhash_build(c68414a4) at ufsdirhash_build+0x4f0 ufs_lookup(ecfcea7c) at ufs_lookup+0xf9 VOP_CACHEDLOOKUP_APV(c09b5300,ecfcea7c) at VOP_CACHEDLOOKUP_APV+0x38 vfs_cache_lookup(ecfceb18) at vfs_cache_lookup+0xb2 VOP_LOOKUP_APV(c09b5300,ecfceb18) at VOP_LOOKUP_APV+0x43 lookup(ecfceba0) at lookup+0x4c1 namei(ecfceba0) at namei+0x38e kern_lstat(cfb11d80,804f2a8,0,ecfcec74) at kern_lstat+0x47 lstat(cfb11d80,ecfced04) at lstat+0x1b syscall(3b,3b,3b,804f248,804f200,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x2812d473, esp = 0xbfbfeb3c, ebp = 0xbfbfebd8 --- db> show allpcpu Current CPU: 0 cpuid = 0 curthread = 0xcfb11d80: pid 15042 "rm" curpcb = 0xecfced90 fpcurthread = none idlethread = 0xc638b600: pid 10 "idle" APIC ID = 0 currentldt = 0x50 db> show lock db> show lockedvnods Locked vnodes 0xcc21f880: tag ufs, type VDIR usecount 3, writecount 0, refcount 685 mountedhere 0 flags () v_object 0xcc1208c4 ref 0 pages 2724 lock type ufs: EXCL (count 1) by thread 0xcfb11d80 (pid 15042) ino 43490161, on dev amrd0s1g 0xcc04bdd0: tag ufs, type VDIR usecount 3, writecount 0, refcount 682 mountedhere 0 flags () v_object 0xc7538108 ref 0 pages 2712 lock type ufs: EXCL (count 1) by thread 0xc697f000 (pid 15041) ino 31210587, on dev amrd0s1g db> allt Tracing command rm pid 15044 tid 100155 td 0xcfb47000 sched_switch(cfb47000,0,2) at sched_switch+0x14b mi_switch(2,0,cfb47000,b4) at mi_switch+0x1ba ast(ed034d38) at ast+0x3c5 doreti_ast() at doreti_ast+0x17 Tracing command rm pid 15043 tid 100114 td 0xcfb11a80 sched_switch(cfb11a80,0,2) at sched_switch+0x14b mi_switch(2,0) at mi_switch+0x1ba critical_exit(ecfc8bc8,ecfc8b94,c087fa80,0,cfb10008,...) at critical_exit+0x78 lapic_handle_timer(0) at lapic_handle_timer+0xc9 Xtimerint(ecfc8ba0) at Xtimerint+0x30 kern_lstat(cfb11a80,805dfa8,0,ecfc8c74) at kern_lstat+0x47 lstat(cfb11a80,ecfc8d04) at lstat+0x1b syscall(3b,3b,3b,805df48,805df00,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x2812d473, esp = 0xbfbfeb3c, ebp = 0xbfbfebd8 --- Tracing command rm pid 15042 tid 100144 td 0xcfb11d80 kdb_enter(c0921739) at kdb_enter+0x2b siointr1(c6554000) at siointr1+0xce siointr(c6554000) at siointr+0x38 intr_execute_handlers(c63854c4,ecfce8f8,4,ecfce950,c087f853,...) at intr_execute_handlers+0xe1 lapic_handle_intr(38) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc07d79dc, esp = 0xecfce93c, ebp = 0xecfce950 --- ufsdirhash_adjfree(ca780200,a9d720,fffffff0) at ufsdirhash_adjfree+0x80 ufsdirhash_build(c68414a4) at ufsdirhash_build+0x4f0 ufs_lookup(ecfcea7c) at ufs_lookup+0xf9 VOP_CACHEDLOOKUP_APV(c09b5300,ecfcea7c) at VOP_CACHEDLOOKUP_APV+0x38 vfs_cache_lookup(ecfceb18) at vfs_cache_lookup+0xb2 VOP_LOOKUP_APV(c09b5300,ecfceb18) at VOP_LOOKUP_APV+0x43 lookup(ecfceba0) at lookup+0x4c1 namei(ecfceba0) at namei+0x38e kern_lstat(cfb11d80,804f2a8,0,ecfcec74) at kern_lstat+0x47 lstat(cfb11d80,ecfced04) at lstat+0x1b syscall(3b,3b,3b,804f248,804f200,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x2812d473, esp = 0xbfbfeb3c, ebp = 0xbfbfebd8 --- Tracing command rm pid 15041 tid 100075 td 0xc697f000 sched_switch(c697f000,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba turnstile_wait(c09e6800,cfb11d80) at turnstile_wait+0x280 _mtx_lock_sleep(c09e6800,c697f000,0,0,0) at _mtx_lock_sleep+0xb4 msleep(da608828,c09ec1a0,4c,c090b351,0) at msleep+0x29b bwait(da608828,4c,c090b351) at bwait+0x5b bufwait(da608828,1,0,0,2a4,...) at bufwait+0x1a breadn(cc04bdd0,2a4,0,4000,0,...) at breadn+0x1e6 bread(cc04bdd0,2a4,0,4000,0,ecef6938) at bread+0x20 ffs_blkatoff(cc04bdd0,a90000,0,0,ecef6984) at ffs_blkatoff+0x9e ufsdirhash_build(d3bbb420) at ufsdirhash_build+0x428 ufs_lookup(ecef6a7c) at ufs_lookup+0xf9 VOP_CACHEDLOOKUP_APV(c09b5300,ecef6a7c) at VOP_CACHEDLOOKUP_APV+0x38 vfs_cache_lookup(ecef6b18) at vfs_cache_lookup+0xb2 VOP_LOOKUP_APV(c09b5300,ecef6b18) at VOP_LOOKUP_APV+0x43 lookup(ecef6ba0) at lookup+0x4c1 namei(ecef6ba0) at namei+0x38e kern_lstat(c697f000,804f2a8,0,ecef6c74) at kern_lstat+0x47 lstat(c697f000,ecef6d04) at lstat+0x1b syscall(3b,3b,3b,804f248,804f200,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip = 0x2812d473, esp = 0xbfbfeb3c, ebp = 0xbfbfebd8 --- Tracing command gstat pid 15038 tid 100064 td 0xc6737000 sched_switch(c6737000,0,1) at sched_switch+0x14b mi_switch(1,0,c09e70ec,eacc1c48,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09e70ec) at sleepq_switch+0x86 sleepq_timedwait_sig(c09e70ec) at sleepq_timedwait_sig+0x1e msleep(c09e70ec,0,15c,c0907bb7,1f5,...) at msleep+0x200 kern_nanosleep(c6737000,eacc1ccc,eacc1cc4) at kern_nanosleep+0xab nanosleep(c6737000,eacc1d04) at nanosleep+0x4f syscall(3b,3b,3b,8055214,c,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (240, FreeBSD ELF32, nanosleep), eip = 0x28199f63, esp = 0xbfbfea0c, ebp = 0xbfbfea38 --- Tracing command bash pid 14979 tid 100140 td 0xcfb2c480 sched_switch(cfb2c480,0,1) at sched_switch+0x14b mi_switch(1,0,c6516010,ecff49bc,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6516010) at sleepq_switch+0x86 sleepq_wait_sig(c6516010) at sleepq_wait_sig+0x1d msleep(c6516010,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6516000,c6516010,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6516000,ecff4cbc,0) at ttread+0x50f ptsread(c7f34d00,ecff4cbc,0) at ptsread+0x2d giant_read(c7f34d00,ecff4cbc,0,1,c7f34d00,...) at giant_read+0x48 devfs_read_f(c69564c8,ecff4cbc,c83d9d00,0,cfb2c480) at devfs_read_f+0x62 dofileread(cfb2c480,0,c69564c8,ecff4cbc,ffffffff,...) at dofileread+0x85 kern_readv(cfb2c480,0,ecff4cbc,bfbfe80f,1,...) at kern_readv+0x36 read(cfb2c480,ecff4d04) at read+0x45 syscall(80f003b,3b,bfbf003b,0,bfbfe80f,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x282f638f, esp = 0xbfbfe7ec, ebp = 0xbfbfe818 --- Tracing command sshd pid 14975 tid 100078 td 0xc6738a80 sched_switch(c6738a80,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eacf4b28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6738a80,8,807ab50,807ab60,0,...) at kern_select+0x56f select(c6738a80,eacf4d04) at select+0x44 syscall(807003b,807003b,bfbf003b,0,bfbfde7c,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2834730f, esp = 0xbfbfde0c, ebp = 0xbfbfde58 --- Tracing command bash pid 14970 tid 100143 td 0xcfb2c000 sched_switch(cfb2c000,0,1) at sched_switch+0x14b mi_switch(1,0,cfb46648,ecfebc18,c069be8d,...) at mi_switch+0x1ba sleepq_switch(cfb46648) at sleepq_switch+0x86 sleepq_wait_sig(cfb46648) at sleepq_wait_sig+0x1d msleep(cfb46648,cfb466b0,15c,c0907390,0) at msleep+0x22a kern_wait(cfb2c000,ffffffff,ecfebc84,6,0) at kern_wait+0x89c wait4(cfb2c000,ecfebd04) at wait4+0x2a syscall(80f003b,3b,bfbf003b,3abe,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (7, FreeBSD ELF32, wait4), eip = 0x2828d70f, esp = 0xbfbfe8bc, ebp = 0xbfbfe8d8 --- Tracing command sshd pid 14967 tid 100152 td 0xcfb47480 sched_switch(cfb47480,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,ed03db28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(cfb47480,8,807ab50,807ab60,0,...) at kern_select+0x56f select(cfb47480,ed03dd04) at select+0x44 syscall(bfbf003b,bfbf003b,bfbf003b,0,bfbfde7c,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2834730f, esp = 0xbfbfde0c, ebp = 0xbfbfde58 --- Tracing command bash pid 14952 tid 100171 td 0xcfb48900 sched_switch(cfb48900,0,1) at sched_switch+0x14b mi_switch(1,0,c6552010,ed0649bc,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6552010) at sleepq_switch+0x86 sleepq_wait_sig(c6552010) at sleepq_wait_sig+0x1d msleep(c6552010,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6552000,c6552010,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6552000,ed064cbc,0) at ttread+0x50f ptsread(c6a3e000,ed064cbc,0) at ptsread+0x2d giant_read(c6a3e000,ed064cbc,0,1,c6a3e000,...) at giant_read+0x48 devfs_read_f(c87d9510,ed064cbc,cf16c900,0,cfb48900) at devfs_read_f+0x62 dofileread(cfb48900,0,c87d9510,ed064cbc,ffffffff,...) at dofileread+0x85 kern_readv(cfb48900,0,ed064cbc,bfbfe80f,1,...) at kern_readv+0x36 read(cfb48900,ed064d04) at read+0x45 syscall(3b,3b,3b,0,bfbfe80f,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x282f638f, esp = 0xbfbfe7ec, ebp = 0xbfbfe818 --- Tracing command sshd pid 14949 tid 100168 td 0xcfb48d80 sched_switch(cfb48d80,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,ed06db28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(cfb48d80,8,807ab50,807ab60,0,...) at kern_select+0x56f select(cfb48d80,ed06dd04) at select+0x44 syscall(bfbf003b,807003b,bfbf003b,0,bfbfde7c,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2834730f, esp = 0xbfbfde0c, ebp = 0xbfbfde58 --- Tracing command getty pid 852 tid 100067 td 0xc697fc00 sched_switch(c697fc00,0,1) at sched_switch+0x14b mi_switch(1,0,c6385c10,ecf0e9c4,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6385c10) at sleepq_switch+0x86 sleepq_wait_sig(c6385c10) at sleepq_wait_sig+0x1d msleep(c6385c10,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6385c00,c6385c10,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6385c00,ecf0ecbc,0) at ttread+0x50f ttyread(c6557400,ecf0ecbc,0) at ttyread+0x2f giant_read(c6557400,ecf0ecbc,0,1,c6557400,...) at giant_read+0x48 devfs_read_f(c6759ca8,ecf0ecbc,c6388d80,0,c697fc00) at devfs_read_f+0x62 dofileread(c697fc00,0,c6759ca8,ecf0ecbc,ffffffff,...) at dofileread+0x85 kern_readv(c697fc00,0,ecf0ecbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697fc00,ecf0ed04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 851 tid 100063 td 0xc6737180 sched_switch(c6737180,0,1) at sched_switch+0x14b mi_switch(1,0,c6569010,eacc49b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6569010) at sleepq_switch+0x86 sleepq_wait_sig(c6569010) at sleepq_wait_sig+0x1d msleep(c6569010,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6569000,c6569010,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6569000,eacc4cbc,0) at ttread+0x50f ttyread(c6558600,eacc4cbc,0,eacc4c14,c0653514,...) at ttyread+0x2f scread(c6558600,eacc4cbc,0) at scread+0x22 giant_read(c6558600,eacc4cbc,0,1,c6558600,...) at giant_read+0x48 devfs_read_f(c675ad80,eacc4cbc,c6388d80,0,c6737180) at devfs_read_f+0x62 dofileread(c6737180,0,c675ad80,eacc4cbc,ffffffff,...) at dofileread+0x85 kern_readv(c6737180,0,eacc4cbc,bfbfee1f,1,...) at kern_readv+0x36 read(c6737180,eacc4d04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 850 tid 100068 td 0xc697fa80 sched_switch(c697fa80,0,1) at sched_switch+0x14b mi_switch(1,0,c6568c10,ecf0b9b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6568c10) at sleepq_switch+0x86 sleepq_wait_sig(c6568c10) at sleepq_wait_sig+0x1d msleep(c6568c10,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6568c00,c6568c10,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6568c00,ecf0bcbc,0) at ttread+0x50f ttyread(c6558700,ecf0bcbc,0,ecf0bc14,c0653514,...) at ttyread+0x2f scread(c6558700,ecf0bcbc,0) at scread+0x22 giant_read(c6558700,ecf0bcbc,0,1,c6558700,...) at giant_read+0x48 devfs_read_f(c675a5a0,ecf0bcbc,c6388d80,0,c697fa80) at devfs_read_f+0x62 dofileread(c697fa80,0,c675a5a0,ecf0bcbc,ffffffff,...) at dofileread+0x85 kern_readv(c697fa80,0,ecf0bcbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697fa80,ecf0bd04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 849 tid 100066 td 0xc697fd80 sched_switch(c697fd80,0,1) at sched_switch+0x14b mi_switch(1,0,c6569c10,ecf119b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6569c10) at sleepq_switch+0x86 sleepq_wait_sig(c6569c10) at sleepq_wait_sig+0x1d msleep(c6569c10,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6569c00,c6569c10,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6569c00,ecf11cbc,0) at ttread+0x50f ttyread(c6558800,ecf11cbc,0,ecf11c14,c0653514,...) at ttyread+0x2f scread(c6558800,ecf11cbc,0) at scread+0x22 giant_read(c6558800,ecf11cbc,0,1,c6558800,...) at giant_read+0x48 devfs_read_f(c675a798,ecf11cbc,c6388d80,0,c697fd80) at devfs_read_f+0x62 dofileread(c697fd80,0,c675a798,ecf11cbc,ffffffff,...) at dofileread+0x85 kern_readv(c697fd80,0,ecf11cbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697fd80,ecf11d04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 848 tid 100071 td 0xc697f600 sched_switch(c697f600,0,1) at sched_switch+0x14b mi_switch(1,0,c6569810,ecf029b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6569810) at sleepq_switch+0x86 sleepq_wait_sig(c6569810) at sleepq_wait_sig+0x1d msleep(c6569810,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6569800,c6569810,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6569800,ecf02cbc,0) at ttread+0x50f ttyread(c6558900,ecf02cbc,0,ecf02c14,c0653514,...) at ttyread+0x2f scread(c6558900,ecf02cbc,0) at scread+0x22 giant_read(c6558900,ecf02cbc,0,1,c6558900,...) at giant_read+0x48 devfs_read_f(c675ac60,ecf02cbc,c6388d80,0,c697f600) at devfs_read_f+0x62 dofileread(c697f600,0,c675ac60,ecf02cbc,ffffffff,...) at dofileread+0x85 kern_readv(c697f600,0,ecf02cbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697f600,ecf02d04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 847 tid 100069 td 0xc697f900 sched_switch(c697f900,0,1) at sched_switch+0x14b mi_switch(1,0,c6568410,ecf089b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6568410) at sleepq_switch+0x86 sleepq_wait_sig(c6568410) at sleepq_wait_sig+0x1d msleep(c6568410,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6568400,c6568410,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6568400,ecf08cbc,0) at ttread+0x50f ttyread(c6558a00,ecf08cbc,0,ecf08c14,c0653514,...) at ttyread+0x2f scread(c6558a00,ecf08cbc,0) at scread+0x22 giant_read(c6558a00,ecf08cbc,0,1,c6558a00,...) at giant_read+0x48 devfs_read_f(c675a1f8,ecf08cbc,c6388d80,0,c697f900) at devfs_read_f+0x62 dofileread(c697f900,0,c675a1f8,ecf08cbc,ffffffff,...) at dofileread+0x85 kern_readv(c697f900,0,ecf08cbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697f900,ecf08d04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 846 tid 100073 td 0xc697f300 sched_switch(c697f300,0,1) at sched_switch+0x14b mi_switch(1,0,c6568010,ecefc9b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6568010) at sleepq_switch+0x86 sleepq_wait_sig(c6568010) at sleepq_wait_sig+0x1d msleep(c6568010,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6568000,c6568010,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6568000,ecefccbc,0) at ttread+0x50f ttyread(c655aa00,ecefccbc,0,ecefcc14,c0653514,...) at ttyread+0x2f scread(c655aa00,ecefccbc,0) at scread+0x22 giant_read(c655aa00,ecefccbc,0,1,c655aa00,...) at giant_read+0x48 devfs_read_f(c675a828,ecefccbc,c6388d80,0,c697f300) at devfs_read_f+0x62 dofileread(c697f300,0,c675a828,ecefccbc,ffffffff,...) at dofileread+0x85 kern_readv(c697f300,0,ecefccbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697f300,ecefcd04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 845 tid 100070 td 0xc697f780 sched_switch(c697f780,0,1) at sched_switch+0x14b mi_switch(1,0,c6567810,ecf059b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6567810) at sleepq_switch+0x86 sleepq_wait_sig(c6567810) at sleepq_wait_sig+0x1d msleep(c6567810,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6567800,c6567810,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6567800,ecf05cbc,0) at ttread+0x50f ttyread(c655a300,ecf05cbc,0,ecf05c14,c0653514,...) at ttyread+0x2f scread(c655a300,ecf05cbc,0) at scread+0x22 giant_read(c655a300,ecf05cbc,0,1,c655a300,...) at giant_read+0x48 devfs_read_f(c675ac18,ecf05cbc,c6388d80,0,c697f780) at devfs_read_f+0x62 dofileread(c697f780,0,c675ac18,ecf05cbc,ffffffff,...) at dofileread+0x85 kern_readv(c697f780,0,ecf05cbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697f780,ecf05d04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command getty pid 844 tid 100072 td 0xc697f480 sched_switch(c697f480,0,1) at sched_switch+0x14b mi_switch(1,0,c6567c10,eceff9b0,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6567c10) at sleepq_switch+0x86 sleepq_wait_sig(c6567c10) at sleepq_wait_sig+0x1d msleep(c6567c10,0,159,c0909f78,0) at msleep+0x22a ttysleep(c6567c00,c6567c10,159,c0909f78,0,...) at ttysleep+0x21 ttread(c6567c00,eceffcbc,0) at ttread+0x50f ttyread(c655a000,eceffcbc,0,eceffc14,c0653514,...) at ttyread+0x2f scread(c655a000,eceffcbc,0) at scread+0x22 giant_read(c655a000,eceffcbc,0,1,c655a000,...) at giant_read+0x48 devfs_read_f(c675a5e8,eceffcbc,c6388d80,0,c697f480) at devfs_read_f+0x62 dofileread(c697f480,0,c675a5e8,eceffcbc,ffffffff,...) at dofileread+0x85 kern_readv(c697f480,0,eceffcbc,bfbfee1f,1,...) at kern_readv+0x36 read(c697f480,eceffd04) at read+0x45 syscall(3b,3b,3b,0,804e580,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2814738f, esp = 0xbfbfedfc, ebp = 0xbfbfee28 --- Tracing command cron pid 802 tid 100055 td 0xc6737d80 sched_switch(c6737d80,0,1) at sched_switch+0x14b mi_switch(1,0,c09e70ec,eacdcc48,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09e70ec) at sleepq_switch+0x86 sleepq_timedwait_sig(c09e70ec) at sleepq_timedwait_sig+0x1e msleep(c09e70ec,0,15c,c0907bb7,ea61,...) at msleep+0x200 kern_nanosleep(c6737d80,eacdcccc,eacdccc4) at kern_nanosleep+0xab nanosleep(c6737d80,eacdcd04) at nanosleep+0x4f syscall(805003b,3b,bfbf003b,805008c,3c,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (240, FreeBSD ELF32, nanosleep), eip = 0x28130f63, esp = 0xbfbfecdc, ebp = 0xbfbfed08 --- Tracing command sendmail pid 796 tid 100059 td 0xc6737780 sched_switch(c6737780,0,1) at sched_switch+0x14b mi_switch(1,0,c68e067c,eacd0c68,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c68e067c) at sleepq_switch+0x86 sleepq_wait_sig(c68e067c) at sleepq_wait_sig+0x1d msleep(c68e067c,c68e06b0,168,c08d5a58,0) at msleep+0x22a kern_sigsuspend(c6737780,0,0,0,0,...) at kern_sigsuspend+0xbf sigsuspend(c6737780,eacd0d04) at sigsuspend+0x33 syscall(3b,bfbf003b,bfbf003b,0,bfbfd000,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (341, FreeBSD ELF32, sigsuspend), eip = 0x282797f7, esp = 0xbfbfcfec, ebp = 0xbfbfd018 --- Tracing command sendmail pid 792 tid 100058 td 0xc6737900 sched_switch(c6737900,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eacd3b1c,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_timedwait_sig(c09ebb64,c09ebb64,1389,c09ebb64,c09ebb40,...) at sleepq_timedwait_sig+0x1e cv_timedwait_sig(c09ebb64,c09ebb40,1389) at cv_timedwait_sig+0x11e kern_select(c6737900,5,bfbfc500,0,0,...) at kern_select+0x559 select(c6737900,eacd3d04) at select+0x44 syscall(80d003b,bfbf003b,bfbf003b,1,1,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x282f730f, esp = 0xbfbfc40c, ebp = 0xbfbfd008 --- Tracing command sshd pid 786 tid 100050 td 0xc6738600 sched_switch(c6738600,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eacebb28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6738600,7,807a8e0,0,0,...) at kern_select+0x56f select(c6738600,eacebd04) at select+0x44 syscall(3b,3b,bfbf003b,1,a,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2834730f, esp = 0xbfbfdecc, ebp = 0xbfbfee78 --- Tracing command ntpd pid 765 tid 100043 td 0xc6533300 sched_switch(c6533300,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,e6c71b28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6533300,b,bfbfed60,0,0,...) at kern_select+0x56f select(c6533300,e6c71d04) at select+0x44 syscall(c087003b,3b,3b,bfbfed60,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2828930f, esp = 0xbfbfed1c, ebp = 0xbfbfedf8 --- Tracing command rpc.lockd pid 731 tid 100051 td 0xc6738480 sched_switch(c6738480,0,1) at sched_switch+0x14b mi_switch(1,0,c09f4128,eace8bcc,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09f4128) at sleepq_switch+0x86 sleepq_wait_sig(c09f4128) at sleepq_wait_sig+0x1d msleep(c09f4128,c09f4100,158,c0914b2b,0) at msleep+0x22a nfslock_read(c6412000,eace8cbc,4,194,c6412000,...) at nfslock_read+0x7f devfs_read_f(c675a8b8,eace8cbc,c6902000,0,c6738480) at devfs_read_f+0x62 dofileread(c6738480,8,c675a8b8,eace8cbc,ffffffff,...) at dofileread+0x85 kern_readv(c6738480,8,eace8cbc,bfbfec60,194,...) at kern_readv+0x36 read(c6738480,eace8d04) at read+0x45 syscall(3b,3b,3b,4,806e300,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x2815438f, esp = 0xbfbfec2c, ebp = 0xbfbfee08 --- Tracing command rpc.lockd pid 725 tid 100038 td 0xc6533a80 sched_switch(c6533a80,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,e6c80b1c,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_timedwait_sig(c09ebb64,c09ebb64,7531,c09ebb64,c09ebb40,...) at sleepq_timedwait_sig+0x1e cv_timedwait_sig(c09ebb64,c09ebb40,7531) at cv_timedwait_sig+0x11e kern_select(c6533a80,7,bfbfed70,0,0,...) at kern_select+0x559 select(c6533a80,e6c80d04) at select+0x44 syscall(2817003b,bfbf003b,bfbf003b,2817a3a0,bfbfed70,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2815430f, esp = 0xbfbfecac, ebp = 0xbfbfee08 --- Tracing command rpc.statd pid 720 tid 100052 td 0xc6738300 sched_switch(c6738300,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eace5b1c,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_timedwait_sig(c09ebb64,c09ebb64,7531,c09ebb64,c09ebb40,...) at sleepq_timedwait_sig+0x1e cv_timedwait_sig(c09ebb64,c09ebb40,7531) at cv_timedwait_sig+0x11e kern_select(c6738300,8,bfbfed80,0,0,...) at kern_select+0x559 select(c6738300,eace5d04) at select+0x44 syscall(2816003b,bfbf003b,bfbf003b,281683a0,bfbfed80,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2814230f, esp = 0xbfbfecbc, ebp = 0xbfbfee18 --- Tracing command nfsd pid 718 tid 100053 td 0xc6738180 sched_switch(c6738180,0,1) at sched_switch+0x14b mi_switch(1,0,c671f000,eace2c40,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c671f000) at sleepq_switch+0x86 sleepq_wait_sig(c671f000) at sleepq_wait_sig+0x1d msleep(c671f000,c09f91c0,158,c0902a56,0,...) at msleep+0x22a nfssvc_nfsd(c6738180) at nfssvc_nfsd+0xdd nfssvc(c6738180,eace2d04) at nfssvc+0x1bc syscall(3b,3b,3b,1,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280bd1f7, esp = 0xbfbfeb1c, ebp = 0xbfbfeb38 --- Tracing command nfsd pid 717 tid 100062 td 0xc6737300 sched_switch(c6737300,0,1) at sched_switch+0x14b mi_switch(1,0,c6720800,eacc7c40,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6720800) at sleepq_switch+0x86 sleepq_wait_sig(c6720800) at sleepq_wait_sig+0x1d msleep(c6720800,c09f91c0,158,c0902a56,0,...) at msleep+0x22a nfssvc_nfsd(c6737300) at nfssvc_nfsd+0xdd nfssvc(c6737300,eacc7d04) at nfssvc+0x1bc syscall(3b,3b,3b,1,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280bd1f7, esp = 0xbfbfeb1c, ebp = 0xbfbfeb38 --- Tracing command nfsd pid 716 tid 100057 td 0xc6737a80 sched_switch(c6737a80,0,1) at sched_switch+0x14b mi_switch(1,0,c6715800,eacd6c40,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c6715800) at sleepq_switch+0x86 sleepq_wait_sig(c6715800) at sleepq_wait_sig+0x1d msleep(c6715800,c09f91c0,158,c0902a56,0,...) at msleep+0x22a nfssvc_nfsd(c6737a80) at nfssvc_nfsd+0xdd nfssvc(c6737a80,eacd6d04) at nfssvc+0x1bc syscall(3b,3b,3b,1,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280bd1f7, esp = 0xbfbfeb1c, ebp = 0xbfbfeb38 --- Tracing command nfsd pid 712 tid 100056 td 0xc6737c00 sched_switch(c6737c00,0,1) at sched_switch+0x14b mi_switch(1,0,c671f200,eacd9c40,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c671f200) at sleepq_switch+0x86 sleepq_wait_sig(c671f200) at sleepq_wait_sig+0x1d msleep(c671f200,c09f91c0,158,c0902a56,0,...) at msleep+0x22a nfssvc_nfsd(c6737c00) at nfssvc_nfsd+0xdd nfssvc(c6737c00,eacd9d04) at nfssvc+0x1bc syscall(3b,3b,3b,1,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280bd1f7, esp = 0xbfbfeb1c, ebp = 0xbfbfeb38 --- Tracing command nfsd pid 710 tid 100042 td 0xc6533480 sched_switch(c6533480,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,e6c74b28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6533480,5,bfbfed30,0,0,...) at kern_select+0x56f select(c6533480,e6c74d04) at select+0x44 syscall(3b,3b,3b,bfbfee40,4,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2813a30f, esp = 0xbfbfeb2c, ebp = 0xbfbfee68 --- Tracing command mountd pid 708 tid 100040 td 0xc6533780 sched_switch(c6533780,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,e6c7ab28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6533780,8,bfbfede0,0,0,...) at kern_select+0x56f select(c6533780,e6c7ad04) at select+0x44 syscall(3b,3b,3b,8,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2814a30f, esp = 0xbfbfed3c, ebp = 0xbfbfee78 --- Tracing command rpcbind pid 639 tid 100039 td 0xc6533900 sched_switch(c6533900,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,e6c7db60,c069bf6a,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_timedwait_sig(c09ebb64,c09ebb64,7531,c09ebb64,c09ebb40,...) at sleepq_timedwait_sig+0x1e cv_timedwait_sig(c09ebb64,c09ebb40,7531) at cv_timedwait_sig+0x11e poll(c6533900,e6c7dd04) at poll+0x48f syscall(3b,3b,bfbf003b,1,7,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (209, FreeBSD ELF32, poll), eip = 0x2810adff, esp = 0xbfbfcc5c, ebp = 0xbfbfee28 --- Tracing command syslogd pid 604 tid 100054 td 0xc6738000 sched_switch(c6738000,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eacdfb28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6738000,9,8056060,0,0,...) at kern_select+0x56f select(c6738000,eacdfd04) at select+0x44 syscall(805003b,bfbf003b,bfbf003b,8056064,8056060,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x2814b30f, esp = 0xbfbfda2c, ebp = 0xbfbfee78 --- Tracing command devd pid 530 tid 100061 td 0xc6737480 sched_switch(c6737480,0,1) at sched_switch+0x14b mi_switch(1,0,c09ebb64,eaccab28,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c09ebb64) at sleepq_switch+0x86 sleepq_wait_sig(c09ebb64,c09ebb64,c09ebb40,c09094fa,101,...) at sleepq_wait_sig+0x1d cv_wait_sig(c09ebb64,c09ebb40) at cv_wait_sig+0x113 kern_select(c6737480,5,bfbfe9d0,0,0,...) at kern_select+0x56f select(c6737480,eaccad04) at select+0x44 syscall(3b,3b,3b,1,8,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (93, FreeBSD ELF32, select), eip = 0x80757f7, esp = 0xbfbfe96c, ebp = 0xbfbfee78 --- Tracing command schedcpu pid 43 tid 100045 td 0xc6533000 sched_switch(c6533000,0,1) at sched_switch+0x14b mi_switch(1,0,c6533000,e6c6bccc,c069bf12,...) at mi_switch+0x1ba sleepq_switch(e6c6bd08,e6c6bd08,e6c6bcec,c06835ed,e6c6bd08,...) at sleepq_switch+0x86 sleepq_timedwait(e6c6bd08) at sleepq_timedwait+0x36 msleep(e6c6bd08,0,0,c0902a56,3e8) at msleep+0x215 schedcpu_thread(0,e6c6bd38) at schedcpu_thread+0x26 fork_exit(c068e408,0,e6c6bd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6c6bd6c, ebp = 0 --- Tracing command softdepflush pid 42 tid 100046 td 0xc6493d80 sched_switch(c6493d80,0,1) at sched_switch+0x14b mi_switch(1,0,c6493d80,e6a2ccc0,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09f9554,c6493d80,e6a2cce0,c06835ed,c09f9554,...) at sleepq_switch+0x86 sleepq_timedwait(c09f9554) at sleepq_timedwait+0x36 msleep(c09f9554,c09f9520,44,c0918caf,3e8) at msleep+0x215 softdep_flush(0,e6a2cd38) at softdep_flush+0x2b9 fork_exit(c07c4b6c,0,e6a2cd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a2cd6c, ebp = 0 --- Tracing command syncer pid 41 tid 100047 td 0xc6493c00 sched_switch(c6493c00,0,1) at sched_switch+0x14b mi_switch(1,0,c6493c00,e6a29cb0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c09e6e5c) at sleepq_switch+0x86 sleepq_wait(c09e6e5c,0,c6493c00,0,c651e700,...) at sleepq_wait+0x36 msleep(c09e6e5c,0,68,c090c238,0) at msleep+0x239 sched_sync(0,e6a29d38) at sched_sync+0x3d6 fork_exit(c06d4960,0,e6a29d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a29d6c, ebp = 0 --- Tracing command vnlru pid 40 tid 100048 td 0xc6493a80 sched_switch(c6493a80,0,1) at sched_switch+0x14b mi_switch(1,0,c6493a80,e6a26cb8,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c6735c90,c6493a80,e6a26cd8,c06835ed,c6735c90,...) at sleepq_switch+0x86 sleepq_timedwait(c6735c90) at sleepq_timedwait+0x36 msleep(c6735c90,c09ec4c0,250,c090c19d,3e8,c09ec540) at msleep+0x215 vnlru_proc(0,e6a26d38) at vnlru_proc+0x113 fork_exit(c06d2d20,0,e6a26d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a26d6c, ebp = 0 --- Tracing command bufdaemon pid 39 tid 100049 td 0xc6493900 sched_switch(c6493900,0,1) at sched_switch+0x14b mi_switch(1,0,c6493900,e6a23cd0,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09ec0cc,c6493900,e6a23cf0,c06835ed,c09ec0cc,...) at sleepq_switch+0x86 sleepq_timedwait(c09ec0cc) at sleepq_timedwait+0x36 msleep(c09ec0cc,c09ec0e0,44,c090b1fa,3e8) at msleep+0x215 buf_daemon(0,e6a23d38) at buf_daemon+0x16b fork_exit(c06c55f0,0,e6a23d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a23d6c, ebp = 0 --- Tracing command pagezero pid 38 tid 100027 td 0xc6493180 sched_switch(c6493180,0,1) at sched_switch+0x14b mi_switch(1,0,c6493180,e6a14cd4,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09fa4c4,4,e6a14cf4,c06835ed,c09fa4c4,...) at sleepq_switch+0x86 sleepq_timedwait(c09fa4c4) at sleepq_timedwait+0x36 msleep(c09fa4c4,c09f9fa0,200,c091c89d,493e0) at msleep+0x215 vm_pagezero(0,e6a14d38) at vm_pagezero+0x8a fork_exit(c07fa45c,0,e6a14d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a14d6c, ebp = 0 --- Tracing command vmdaemon pid 37 tid 100028 td 0xc6493000 sched_switch(c6493000,0,1) at sched_switch+0x14b mi_switch(1,0,c6493000,e6a11ca8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c09fa014) at sleepq_switch+0x86 sleepq_wait(c09fa014,0,c6493000,c6530000,c07f9394,...) at sleepq_wait+0x36 msleep(c09fa014,0,68,c090b1fa,0) at msleep+0x239 vm_daemon(0,e6a11d38) at vm_daemon+0x4f fork_exit(c07f9394,0,e6a11d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a11d6c, ebp = 0 --- Tracing command pagedaemon pid 36 tid 100029 td 0xc6391d80 sched_switch(c6391d80,0,1) at sched_switch+0x14b mi_switch(1,0,c6391d80,e4febccc,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09f9fd0,c6391d80,e4febcec,c06835ed,c09f9fd0,...) at sleepq_switch+0x86 sleepq_timedwait(c09f9fd0) at sleepq_timedwait+0x36 msleep(c09f9fd0,c09f9fa0,44,c090b1fa,1388) at msleep+0x215 vm_pageout(0,e4febd38) at vm_pageout+0x280 fork_exit(c07f9004,0,e4febd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4febd6c, ebp = 0 --- Tracing command irq1: atkbd0 pid 35 tid 100030 td 0xc6391c00 fork_trampoline() at fork_trampoline Tracing command fdc0 pid 34 tid 100031 td 0xc6391a80 sched_switch(c6391a80,0,1) at sched_switch+0x14b mi_switch(1,0,c6391a80,e4fe5c88,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c6560a3c,c6391a80,e4fe5ca8,c06835ed,c6560a3c,...) at sleepq_switch+0x86 sleepq_timedwait(c6560a3c) at sleepq_timedwait+0x36 msleep(c6560a3c,c6560af0,4c,c0902a56,3e8) at msleep+0x215 fdc_worker(c6560a00) at fdc_worker+0x256 fdc_thread(c6560a00,e4fe5d38) at fdc_thread+0x86 fork_exit(c0857064,c6560a00,e4fe5d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fe5d6c, ebp = 0 --- Tracing command irq7: ppc0 pid 33 tid 100032 td 0xc6391900 fork_trampoline() at fork_trampoline Tracing command swi0: sio pid 32 tid 100033 td 0xc6391780 sched_switch(c6391780,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c65590f0,e4fdfd38) at ithread_loop+0xb3 fork_exit(c0667d78,c65590f0,e4fdfd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fdfd6c, ebp = 0 --- Tracing command acpi_thermal pid 31 tid 100034 td 0xc6391600 sched_switch(c6391600,c6533d80,6) at sched_switch+0x14b mi_switch(6,c6533d80,c6533ed8,c6533d80,e4fdcaac,...) at mi_switch+0x1ba maybe_preempt(c6533d80) at maybe_preempt+0xc4 sched_add(c6533d80,4,c6391600,c6533d80,c6388380,...) at sched_add+0x27 setrunqueue(c6533d80,4) at setrunqueue+0x63 intr_event_schedule_thread(c6388380) at intr_event_schedule_thread+0xb5 intr_execute_handlers(c63850c4,e4fdcb24,14,e4fdcb8c,c087f853,...) at intr_execute_handlers+0x118 lapic_handle_intr(36) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc0b485ab, esp = 0xe4fdcb68, ebp = 0xe4fdcb8c --- AcpiNsGetNextNode(c445,c655c400,c649d080,e4fdcbc0,c0b4a55e,...) at AcpiNsGetNextNode+0x3f AcpiDsTerminateControlMethod(c655c400,0,c649d080,0,c655d800,...) at AcpiDsTerminateControlMethod+0x7b AcpiPsParseAml(c655d800,c649d780,c63d6380,0,e4fdcc38,...) at AcpiPsParseAml+0x1a6 AcpiPsxExecute(e4fdcc38,e4fdcc38,e4fdcc38,e4fdcc04,c0b47174,...) at AcpiPsxExecute+0x1b9 AcpiNsExecuteControlMethod(e4fdcc38,0,e4fdcc24,c0b472a8,e4fdcc38,...) at AcpiNsExecuteControlMethod+0x3b AcpiNsEvaluateByHandle(e4fdcc38,c63d3b80,c9d083f0,1001,c63d3ba0,...) at AcpiNsEvaluateByHandle+0x84 AcpiNsEvaluateRelative(c0b6a5bd,e4fdcc38,c6391600,c63d3b80,0,...) at AcpiNsEvaluateRelative+0xa4 AcpiEvaluateObject(c63d3ba0,c0b6a5bd,0,e4fdcc6c,10,...) at AcpiEvaluateObject+0x74 acpi_GetInteger(c63d3ba0,c0b6a5bd,e4fdcca4,0,0,...) at acpi_GetInteger+0x30 acpi_tz_get_temperature(c06726a9,c097a200,10,0,c104e960,...) at acpi_tz_get_temperature+0x19 acpi_tz_monitor(cad2f9b0,d25c20c0,3,c6530c90,c0b59d48,...) at acpi_tz_monitor+0x10 acpi_tz_thread(0,e4fdcd38) at acpi_tz_thread+0x143 fork_exit(c0b59d48,0,e4fdcd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fdcd6c, ebp = 0 --- Tracing command em0 taskq pid 30 tid 100035 td 0xc6391480 sched_switch(c6391480,0,1) at sched_switch+0x14b mi_switch(1,0,c6391480,e4fd9cd0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c651dd00) at sleepq_switch+0x86 sleepq_wait(c651dd00,c069ce91,c651dd00,c651dd1c,c651dd00,...) at sleepq_wait+0x36 msleep_spin(c651dd00,c651dd1c,c0902a56,0) at msleep_spin+0x132 taskqueue_thread_loop(c6487a14,e4fd9d38) at taskqueue_thread_loop+0x85 fork_exit(c069d1f0,c6487a14,e4fd9d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd9d6c, ebp = 0 --- Tracing command irq20: amr0 pid 29 tid 100036 td 0xc6533d80 sched_switch(c6533d80,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c651c360,e6c86d38) at ithread_loop+0xb3 fork_exit(c0667d78,c651c360,e6c86d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6c86d6c, ebp = 0 --- Tracing command aic_recovery1 pid 28 tid 100037 td 0xc6533c00 sched_switch(c6533c00,0,1) at sched_switch+0x14b mi_switch(1,0,c6533c00,e6c83cd0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c651b000) at sleepq_switch+0x86 sleepq_wait(c651b000,0,c6533c00,c651b000,c04b6cb0,...) at sleepq_wait+0x36 msleep(c651b000,0,a0,c08d39c8,0) at msleep+0x239 ahc_recovery_thread(c651b000,e6c83d38) at ahc_recovery_thread+0x5b fork_exit(c04b6cb0,c651b000,e6c83d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6c83d6c, ebp = 0 --- Tracing command irq17: ahc1 pid 27 tid 100017 td 0xc638c900 sched_switch(c638c900,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c6518950,e4fc4d38) at ithread_loop+0xb3 fork_exit(c0667d78,c6518950,e4fc4d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fc4d6c, ebp = 0 --- Tracing command aic_recovery1 pid 26 tid 100018 td 0xc638c780 sched_switch(c638c780,0,1) at sched_switch+0x14b mi_switch(1,0,c638c780,e4fc1cd0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c651b000) at sleepq_switch+0x86 sleepq_wait(c651b000,0,c638c780,c651b000,c04b6cb0,...) at sleepq_wait+0x36 msleep(c651b000,0,a0,c08d39c8,0) at msleep+0x239 ahc_recovery_thread(c651b000,e4fc1d38) at ahc_recovery_thread+0x5b fork_exit(c04b6cb0,c651b000,e4fc1d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fc1d6c, ebp = 0 --- Tracing command aic_recovery0 pid 25 tid 100019 td 0xc638c600 sched_switch(c638c600,0,1) at sched_switch+0x14b mi_switch(1,0,c638c600,e4fbecd0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c648a600) at sleepq_switch+0x86 sleepq_wait(c648a600,0,c638c600,c648a600,c04b6cb0,...) at sleepq_wait+0x36 msleep(c648a600,0,a0,c08d39c8,0) at msleep+0x239 ahc_recovery_thread(c648a600,e4fbed38) at ahc_recovery_thread+0x5b fork_exit(c04b6cb0,c648a600,e4fbed38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fbed6c, ebp = 0 --- Tracing command irq16: ahc0 pid 24 tid 100020 td 0xc638c480 sched_switch(c638c480,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c651c130,e4fbbd38) at ithread_loop+0xb3 fork_exit(c0667d78,c651c130,e4fbbd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fbbd6c, ebp = 0 --- Tracing command aic_recovery0 pid 23 tid 100021 td 0xc638c300 sched_switch(c638c300,0,1) at sched_switch+0x14b mi_switch(1,0,c638c300,e4fb8cd0,c069be42,...) at mi_switch+0x1ba sleepq_switch(c648a600) at sleepq_switch+0x86 sleepq_wait(c648a600,0,c638c300,c648a600,c04b6cb0,...) at sleepq_wait+0x36 msleep(c648a600,0,a0,c08d39c8,0) at msleep+0x239 ahc_recovery_thread(c648a600,e4fb8d38) at ahc_recovery_thread+0x5b fork_exit(c04b6cb0,c648a600,e4fb8d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fb8d6c, ebp = 0 --- Tracing command irq15: ata2 pid 22 tid 100022 td 0xc638c180 fork_trampoline() at fork_trampoline Tracing command irq14: ata0 pid 21 tid 100023 td 0xc6493780 fork_trampoline() at fork_trampoline Tracing command irq18: fxp0 pid 20 tid 100024 td 0xc6493600 fork_trampoline() at fork_trampoline Tracing command irq31: acpi0 pid 19 tid 100025 td 0xc6493480 sched_switch(c6493480,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c6488000,e6a1ad38) at ithread_loop+0xb3 fork_exit(c0667d78,c6488000,e6a1ad38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe6a1ad6c, ebp = 0 --- Tracing command swi6: Giant taskq pid 18 tid 100026 td 0xc6493300 fork_trampoline() at fork_trampoline Tracing command swi6: task queue pid 17 tid 100008 td 0xc638b300 sched_switch(c638b300,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c6488610,e4f9ad38) at ithread_loop+0xb3 fork_exit(c0667d78,c6488610,e4f9ad38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4f9ad6c, ebp = 0 --- Tracing command acpi_task_2 pid 9 tid 100009 td 0xc638b180 sched_switch(c638b180,0,1) at sched_switch+0x14b mi_switch(1,0,c638b180,e4f97cc8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c63dfb00) at sleepq_switch+0x86 sleepq_wait(c63dfb00,0,c638b180,c63dfb00,c63dfb1c,...) at sleepq_wait+0x36 msleep(c63dfb00,c63dfb1c,0,c0902a56,0) at msleep+0x239 taskqueue_thread_loop(c0b70860,e4f97d38) at taskqueue_thread_loop+0x9c fork_exit(c069d1f0,c0b70860,e4f97d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4f97d6c, ebp = 0 --- Tracing command acpi_task_1 pid 8 tid 100010 td 0xc638b000 sched_switch(c638b000,0,1) at sched_switch+0x14b mi_switch(1,0,c638b000,e4f94cc8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c63dfb00) at sleepq_switch+0x86 sleepq_wait(c63dfb00,0,c638b000,c63dfb00,c63dfb1c,...) at sleepq_wait+0x36 msleep(c63dfb00,c63dfb1c,0,c0902a56,0) at msleep+0x239 taskqueue_thread_loop(c0b70860,e4f94d38) at taskqueue_thread_loop+0x9c fork_exit(c069d1f0,c0b70860,e4f94d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4f94d6c, ebp = 0 --- Tracing command acpi_task_0 pid 7 tid 100011 td 0xc6391300 sched_switch(c6391300,0,1) at sched_switch+0x14b mi_switch(1,0,c6391300,e4fd6cc8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c63dfb00) at sleepq_switch+0x86 sleepq_wait(c63dfb00,0,c6391300,c63dfb00,c63dfb1c,...) at sleepq_wait+0x36 msleep(c63dfb00,c63dfb1c,0,c0902a56,0) at msleep+0x239 taskqueue_thread_loop(c0b70860,e4fd6d38) at taskqueue_thread_loop+0x9c fork_exit(c069d1f0,c0b70860,e4fd6d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd6d6c, ebp = 0 --- Tracing command kqueue taskq pid 6 tid 100012 td 0xc6391180 sched_switch(c6391180,0,1) at sched_switch+0x14b mi_switch(1,0,c6391180,e4fd3cc8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c63dfb80) at sleepq_switch+0x86 sleepq_wait(c63dfb80,0,c6391180,c63dfb80,c63dfb9c,...) at sleepq_wait+0x36 msleep(c63dfb80,c63dfb9c,0,c0902a56,0) at msleep+0x239 taskqueue_thread_loop(c09e4e60,e4fd3d38) at taskqueue_thread_loop+0x9c fork_exit(c069d1f0,c09e4e60,e4fd3d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd3d6c, ebp = 0 --- Tracing command swi2: cambio pid 16 tid 100013 td 0xc6391000 sched_switch(c6391000,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c6488650,e4fd0d38) at ithread_loop+0xb3 fork_exit(c0667d78,c6488650,e4fd0d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fd0d6c, ebp = 0 --- Tracing command swi5: + pid 15 tid 100014 td 0xc638cd80 sched_switch(c638cd80,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c641e380,e4fcdd38) at ithread_loop+0xb3 fork_exit(c0667d78,c641e380,e4fcdd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fcdd6c, ebp = 0 --- Tracing command thread taskq pid 5 tid 100015 td 0xc638cc00 sched_switch(c638cc00,0,1) at sched_switch+0x14b mi_switch(1,0,c638cc00,e4fcacc8,c069be42,...) at mi_switch+0x1ba sleepq_switch(c63dfe00) at sleepq_switch+0x86 sleepq_wait(c63dfe00,0,c638cc00,c63dfe00,c63dfe1c,...) at sleepq_wait+0x36 msleep(c63dfe00,c63dfe1c,0,c0902a56,0) at msleep+0x239 taskqueue_thread_loop(c09ea628,e4fcad38) at taskqueue_thread_loop+0x9c fork_exit(c069d1f0,c09ea628,e4fcad38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fcad6c, ebp = 0 --- Tracing command yarrow pid 14 tid 100016 td 0xc638ca80 sched_switch(c638ca80,0,1) at sched_switch+0x14b mi_switch(1,0,c638ca80,e4fc7cbc,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09e1aa0,c638ca80,e4fc7cdc,c06835ed,c09e1aa0,...) at sleepq_switch+0x86 sleepq_timedwait(c09e1aa0) at sleepq_timedwait+0x36 msleep(c09e1aa0,0,0,c0902a56,64) at msleep+0x215 random_kthread(0,e4fc7d38) at random_kthread+0x1bb fork_exit(c05c6bdc,0,e4fc7d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fc7d6c, ebp = 0 --- Tracing command g_down pid 4 tid 100000 td 0xc638c000 sched_switch(c638c000,0,1) at sched_switch+0x14b mi_switch(1,0,c638c000,e4fb2cb8,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09e45c8,c638c000,e4fb2cd8,c06835ed,c09e45c8,...) at sleepq_switch+0x86 sleepq_timedwait(c09e45c8) at sleepq_timedwait+0x36 msleep(c09e45c8,c09e44a8,24c,c0902a56,64) at msleep+0x215 g_io_schedule_down(c638c000) at g_io_schedule_down+0x56 g_down_procbody(0,e4fb2d38) at g_down_procbody+0x6e fork_exit(c0643bb4,0,e4fb2d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fb2d6c, ebp = 0 --- Tracing command g_up pid 3 tid 100001 td 0xc638bd80 sched_switch(c638bd80,0,1) at sched_switch+0x14b mi_switch(1,0,c638bd80,e4fafcbc,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09e45c4,c638bd80,e4fafcdc,c06835ed,c09e45c4,...) at sleepq_switch+0x86 sleepq_timedwait(c09e45c4) at sleepq_timedwait+0x36 msleep(c09e45c4,c09e44e8,24c,c0902a56,64) at msleep+0x215 g_io_schedule_up(c638bd80) at g_io_schedule_up+0xcc g_up_procbody(0,e4fafd38) at g_up_procbody+0x6e fork_exit(c0643b40,0,e4fafd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fafd6c, ebp = 0 --- Tracing command g_event pid 2 tid 100002 td 0xc638bc00 sched_switch(c638bc00,0,1) at sched_switch+0x14b mi_switch(1,0,c638bc00,e4faccc4,c069bf12,...) at mi_switch+0x1ba sleepq_switch(c09e45bc,c638bc00,e4facce4,c06835ed,c09e45bc,...) at sleepq_switch+0x86 sleepq_timedwait(c09e45bc) at sleepq_timedwait+0x36 msleep(c09e45bc,0,4c,c0902a56,64) at msleep+0x215 g_event_procbody(0,e4facd38) at g_event_procbody+0xa6 fork_exit(c0643c28,0,e4facd38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4facd6c, ebp = 0 --- Tracing command swi3: vm pid 13 tid 100003 td 0xc638ba80 fork_trampoline() at fork_trampoline Tracing command swi4: clock sio pid 12 tid 100004 td 0xc638b900 sched_switch(c638b900,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba turnstile_wait(c09e6800,cfb11d80) at turnstile_wait+0x280 _mtx_lock_sleep(c09e6800,c638b900,0,0,0) at _mtx_lock_sleep+0xb4 softclock(0) at softclock+0x1e7 ithread_execute_handlers(c638a860,c6389e00) at ithread_execute_handlers+0x121 ithread_loop(c636e640,e4fa6d38) at ithread_loop+0x54 fork_exit(c0667d78,c636e640,e4fa6d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fa6d6c, ebp = 0 --- Tracing command swi1: net pid 11 tid 100005 td 0xc638b780 sched_switch(c638b780,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba ithread_loop(c636e650,e4fa3d38) at ithread_loop+0xb3 fork_exit(c0667d78,c636e650,e4fa3d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fa3d6c, ebp = 0 --- Tracing command idle pid 10 tid 100006 td 0xc638b600 sched_switch(c638b600,0,2) at sched_switch+0x14b mi_switch(2,0) at mi_switch+0x1ba critical_exit(0,c638b600,0,c646e818,c646e800,...) at critical_exit+0x78 intr_execute_handlers(c63850e8,e4fa0c98,15,e4fa0cdc,c087f853,...) at intr_execute_handlers+0x10c lapic_handle_intr(37) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc0b62135, esp = 0xe4fa0cdc, ebp = 0xe4fa0cdc --- acpi_cpu_c1(0,c638b600,3e8,c638ac90,c0666e88,...) at acpi_cpu_c1+0x5 acpi_cpu_idle(e4fa0d10,c0666e99,c638ac90,e4fa0d24,c0666c48,...) at acpi_cpu_idle+0x152 cpu_idle(c638ac90,e4fa0d24,c0666c48,0,e4fa0d38,...) at cpu_idle+0x1f idle_proc(0,e4fa0d38) at idle_proc+0x11 fork_exit(c0666e88,0,e4fa0d38) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4fa0d6c, ebp = 0 --- Tracing command init pid 1 tid 100007 td 0xc638b480 sched_switch(c638b480,0,1) at sched_switch+0x14b mi_switch(1,0,c638f000,e4f9dc18,c069be8d,...) at mi_switch+0x1ba sleepq_switch(c638f000) at sleepq_switch+0x86 sleepq_wait_sig(c638f000) at sleepq_wait_sig+0x1d msleep(c638f000,c638f068,15c,c0907390,0) at msleep+0x22a kern_wait(c638b480,ffffffff,e4f9dc84,0,0) at kern_wait+0x89c wait4(c638b480,e4f9dd04) at wait4+0x2a syscall(3b,3b,3b,0,0,...) at syscall+0x2b7 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (7, FreeBSD ELF32, wait4), eip = 0x8052f47, esp = 0xbfbfed7c, ebp = 0xbfbfed98 --- Tracing command swapper pid 0 tid 0 td 0xc09e48e0 sched_switch(c09e48e0,0,1) at sched_switch+0x14b mi_switch(1,0) at mi_switch+0x1ba scheduler(0,c1ec00,c1e000,0,c044f085,...) at scheduler+0x1e1 mi_startup() at mi_startup+0x96 begin() at begin+0x2c db> --Apple-Mail-23--291249582 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0644; name=KERNCONF Content-Disposition: attachment; filename=KERNCONF include GENERIC ident PT options KDB # Enable kernel debugger support. options BREAK_TO_DEBUGGER options DDB # Support DDB. options GDB # Support remote GDB. options QUOTA --Apple-Mail-23--291249582 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed --Apple-Mail-23--291249582-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 11:15: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 1941616A412 for ; Sat, 16 Sep 2006 11:15:48 +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 5EAC543D46 for ; Sat, 16 Sep 2006 11:15:46 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GOY8x-0002lZ-CN for freebsd-stable@freebsd.org; Sat, 16 Sep 2006 13:15:31 +0200 Received: from r5k156.net.upc.cz ([86.49.10.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Sep 2006 13:15:31 +0200 Received: from martinkov by r5k156.net.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Sep 2006 13:15:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: martinko Date: Sat, 16 Sep 2006 13:15:19 +0200 Lines: 29 Message-ID: References: <200608071254.k77Csk5Q027399@lurza.secnetix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5k156.net.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.0.6) Gecko/20060805 SeaMonkey/1.0.4 In-Reply-To: <200608071254.k77Csk5Q027399@lurza.secnetix.de> Sender: news Subject: Re: final message in buildworld as there is in buildkernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 11:15:48 -0000 Oliver Fromme wrote: > martinko wrote: > > i've been wondering why there is no "footer" in buildworld > > Because it's not necessary. When you see your shell prompt > again, you know that it's finished. And if there's no error > message or exit code != 0, ithas finished successfully. > > Also, historically the sendmail build is always the last > part of buildworld (and installworld), so it's easy to > recognize. > > Best regards > Oliver > well, i still think it's not clear enough. and you don't really want users to investigate what the exit status was, do you. (also not many know about sendmail i believe.) anyway, we've got it with buildkernel and i can't see any reason why not to have it with buildworld. well, i'm not a hacker and this is not something i can decide. i just thought it'd be a good idea and that it'd help freebsd users. cheers, martin From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 11:46: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 85BF616A40F; Sat, 16 Sep 2006 11:46:22 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF06D43D55; Sat, 16 Sep 2006 11:46:21 +0000 (GMT) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.13.8/8.13.8) with ESMTP id k8GBkJu6006517; Sat, 16 Sep 2006 13:46:19 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.13.8/8.13.8/Submit) id k8GBkJKt006516; Sat, 16 Sep 2006 13:46:19 +0200 (CEST) (envelope-from byshenknet) Date: Sat, 16 Sep 2006 13:46:18 +0200 From: Greg Byshenk To: freebsd-stable@freebsd.org Message-ID: <20060916114618.GD71980@core.byshenk.net> References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <450AA29D.9000700@cs.tu-berlin.de> <200609151616.k8FGG23C065997@fire.jhs.private> <20060915175346.GF15445@leia.lambermont.dyndns.org> <20060915153624.X1031@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060915153624.X1031@ganymede.hub.org> User-Agent: Mutt/1.4.2.2i X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED, MANY_EXCLAMATIONS,PLING_QUERY autolearn=failed version=3.1.5 X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on core.byshenk.net Cc: "Marc G. Fournier" Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Sat, 16 Sep 2006 11:46:22 -0000 On Fri, Sep 15, 2006 at 03:41:04PM -0300, Marc G. Fournier wrote: > But, I'm just curious here ... for all of the talk going around about this > whole issue, how many ppl have truly ever been bitten by an unstable > -STABLE? And for those that have, how long did it take to get help from a > developer to get it fixed? I run -STABLE on a number of production machines. I have twice been "bitten by an unstable -STABLE" -- but "bitten" in a very small way. When we build a new -STABLE (on average perhaps once per month), we build it on a test machine, so that we can be sure that it actually works. Once it is tested and we know it works, then we can roll it out to the production machines without undue concern. I note that we follow the same process with out Linux machines, our Irix machines, and our Windows machines. Blindly rolling out updates or patches to critical production machines is unwise and dangerous (at least IMO). I will add that I have never even needed to contact a maintainer. When there has been a problem, I checked the lists. In one case the fix was already committed, in the other there was already an "I'm working on it" message and a fix was commited in less than 24 hours. In the interim, my test machine had a problem -- but that's what a test machine is for. > In the case that started this thread, it seems to be that the developer > fixed his mistake fairly quickly, which is what one would expect ... it > shouldn't be so much that he *broke* -STABLE (shit happens, do you want > your money back?), but it should be 'was he around to reverse his mistake > in a reasonable amount of time?' ... ? Exactly. -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 11:52: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 4BA5716A403 for ; Sat, 16 Sep 2006 11:52:10 +0000 (UTC) (envelope-from rblayzor@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id CADAF43D53 for ; Sat, 16 Sep 2006 11:52:09 +0000 (GMT) (envelope-from rblayzor@inoc.net) Received: from [172.16.16.54] (cpe-24-29-66-248.nycap.res.rr.com [24.29.66.248]) by mx1-a.inoc.net (build v6.3.3) with ESMTP id 78793714 for multiple; Sat, 16 Sep 2006 11:52:08 +0000 (UTC) Message-ID: <450BE564.20106@inoc.net> Date: Sat, 16 Sep 2006 07:52:04 -0400 From: Robert Blayzor Organization: Independent Network Operations Consortium, LLC User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: Matthew Jacob References: <450B62C9.5000706@inoc.net> <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> In-Reply-To: <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 11:52:10 -0000 Matthew Jacob wrote: > Why do you think an iSCSI HBA would be of any benefit to anything > other than the target mode side as a server? Mostly for deploying servers that are diskless, quickly. No need to depend on another server (other than the iSCSI target) to get servers up without a lot of fusing around. Diskless + the software initiator seems like a lot of fusing around to get one server up. I mean I could be wrong, I'm not really sure how the FreeBSD software initiator works or if it's actual optimized and stable. If it's as easy as setting up a DHCP and TFTP server just to boot the kernel, then mount the iSCSI volume, that might be an option. But right now, if an iSCSI HBA driver was available it might be the more reliable way to go. Again, I could be way off base. We use FreeBSD in all of our server clusters now, most via RAID1 mirrors on every server, I'd like to stay with FreeBSD, but sometimes it's lack of support for new server beneficial drivers make that choice hard to make. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC One picture is worth 128K words. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 12:35: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 5100B16A403 for ; Sat, 16 Sep 2006 12:35:54 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1A0143D58 for ; Sat, 16 Sep 2006 12:35:53 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GOZOi-0009lJ-7g; Sat, 16 Sep 2006 15:35:52 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Robert Blayzor In-reply-to: <450BE564.20106@inoc.net> References: <450B62C9.5000706@inoc.net> <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> <450BE564.20106@inoc.net> Comments: In-reply-to Robert Blayzor message dated "Sat, 16 Sep 2006 07:52:04 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Sep 2006 15:35:52 +0300 From: Danny Braniss Message-ID: Cc: Matthew Jacob , freebsd-stable@freebsd.org Subject: Re: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 12:35:54 -0000 > Matthew Jacob wrote: > > Why do you think an iSCSI HBA would be of any benefit to anything > > other than the target mode side as a server? > > > Mostly for deploying servers that are diskless, quickly. No need to > depend on another server (other than the iSCSI target) to get servers up > without a lot of fusing around. Diskless + the software initiator seems > like a lot of fusing around to get one server up. I mean I could be > wrong, I'm not really sure how the FreeBSD software initiator works or > if it's actual optimized and stable. If it's as easy as setting up a > DHCP and TFTP server just to boot the kernel, then mount the iSCSI > volume, that might be an option. But right now, if an iSCSI HBA driver > was available it might be the more reliable way to go. Again, I could > be way off base. We use FreeBSD in all of our server clusters now, most > via RAID1 mirrors on every server, I'd like to stay with FreeBSD, but > sometimes it's lack of support for new server beneficial drivers make > that choice hard to make. we have been running diskless clients for a few hundred work stations, so i think i have some experience :-) 1- setting a diskless freebsd is far easier than linux 2- it's by far much easier to manage. btw, the majority of ws are running linux. being involved with the iSCSI initiator for FreeBSD, I can't see where this can help for a diskless host, or in other words, what's wrong with NFS? also, the TOE cards are not that cheep either :-) my 2c, danny From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 13:30: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 45EAC16A403 for ; Sat, 16 Sep 2006 13:30:16 +0000 (UTC) (envelope-from kmd@milshop.ru) Received: from ug-out-f131.google.com (ug-out-f131.google.com [66.249.92.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7516043D4C for ; Sat, 16 Sep 2006 13:30:14 +0000 (GMT) (envelope-from kmd@milshop.ru) Received: by ug-out-f131.google.com with SMTP id 23so11422ugm for ; Sat, 16 Sep 2006 06:30:13 -0700 (PDT) Received: by 10.66.224.3 with SMTP id w3mr6006381ugg; Sat, 16 Sep 2006 06:30:13 -0700 (PDT) Received: by 10.66.252.14 with HTTP; Sat, 16 Sep 2006 06:30:13 -0700 (PDT) Message-ID: <519867a90609160630u15241982q8b6951fd8ac605a4@mail.gmail.com> Date: Sat, 16 Sep 2006 17:30:13 +0400 From: "Eugene Kazarinov" Sender: kmd@milshop.ru To: freebsd-stable@freebsd.org MIME-Version: 1.0 X-Google-Sender-Auth: 0d8c9b00316dce2a Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ERROR: StepTime does not match Avc 900. Please Report this. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 13:30:16 -0000 FreeBSD 6.2-PRERELEASE #10: Sat Sep 16 04:13:37 MSD 2006 ==== 16-09-2006 16:50:01, ERROR: StepTime does not match Avc 900. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -2100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -3600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -5100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -6600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -8100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -9600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -11100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -12600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -14100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -15600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -17100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -18600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -20100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -21600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -23100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -24600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -26100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -27600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -29100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -30600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -32100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -33600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -35100. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -36600. Please Report this. ..... 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -493200. Please Report this. From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 13:57: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 9D1D816A407 for ; Sat, 16 Sep 2006 13:57:43 +0000 (UTC) (envelope-from rblayzor@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 225A943D5F for ; Sat, 16 Sep 2006 13:57:42 +0000 (GMT) (envelope-from rblayzor@inoc.net) Received: from [172.16.16.54] (cpe-24-29-66-248.nycap.res.rr.com [24.29.66.248]) by mx1-a.inoc.net (build v6.3.3) with ESMTP id 78808459 for multiple; Sat, 16 Sep 2006 13:57:42 +0000 (UTC) Message-ID: <450C02D2.7040202@inoc.net> Date: Sat, 16 Sep 2006 09:57:38 -0400 From: Robert Blayzor Organization: Independent Network Operations Consortium, LLC User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: Danny Braniss References: <450B62C9.5000706@inoc.net> <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> <450BE564.20106@inoc.net> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Matthew Jacob , freebsd-stable@freebsd.org Subject: Re: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 13:57:43 -0000 Danny Braniss wrote: > we have been running diskless clients for a few hundred work stations, so > i think i have some experience :-) > 1- setting a diskless freebsd is far easier than linux > 2- it's by far much easier to manage. > btw, the majority of ws are running linux. > being involved with the iSCSI initiator for FreeBSD, I can't see where > this can help for a diskless host, or in other words, what's > wrong with NFS? > also, the TOE cards are not that cheep either :-) TOE cards are no more expensive than putting a RAID card and two drives in a box. Is it more expensive than native FreeBSD diskless? Sure. I'm not saying that NFS is bad, we use it all over the place. What's nice about iSCSI is you can setup servers for anything and not care what runs on the box. Thus making almost any server diskless so long as it supports the HBA. This works great when you deploy things like Plesk, etc, which don't support NFS or diskless environements. Does it run? Sure, but not without a lot of messing around. Also, if you have the one or two Windows servers you may be forced to have, you can run them diskless as well using the same iSCSI system. I agree that diskless is a nice system to consider, and it's one of our alternate choices, but we do have some applications, virtual servers, etc, which do not support running in native FreeBSD diskless fashion. -- Robert Blayzor, BOFH INOC, LLC rblayzor\@(inoc.net|gmail.com) PGP: 0x66F90BFC @ http://pgp.mit.edu Key fingerprint = 6296 F715 038B 44C1 2720 292A 8580 500E 66F9 0BFC Esc key to reboot Universe, or any other key to continue... From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 13:58: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 6D34816A40F for ; Sat, 16 Sep 2006 13:58:38 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1C8F43D58 for ; Sat, 16 Sep 2006 13:58:35 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id XAA17950; Sat, 16 Sep 2006 23:58:16 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 16 Sep 2006 23:58:16 +1000 (EST) From: Ian Smith To: "Julian H. Stacey" In-Reply-To: <200609160718.k8G7I4Bd070920@fire.jhs.private> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Sat, 16 Sep 2006 13:58:38 -0000 On Sat, 16 Sep 2006, Julian H. Stacey wrote: > Hans Lambermont wrote: > > Julian H. Stacey wrote: > > > Stable is a misnomer that harms FreeBSD somewhat. > > Why not rename 'stable' into 'stable-api' ? > > Nice, an improvement on what we have :-) If enough agree, > the name of this mail list could be changed for a start. Sure, but what colour the new bikeshed? Cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 14:16:53 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 CB58C16A415 for ; Sat, 16 Sep 2006 14:16:53 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id B055143D5D for ; Sat, 16 Sep 2006 14:16:52 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so4204765pye for ; Sat, 16 Sep 2006 07:16:52 -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=hbi6wTh3mmqIyiEonE/hEslq5/icPWF+AbKYBmUJW3CgbUvsAtjr9x+ffiuetp/amyQY5j9+tQKbfyqzyIGxdCnY9cKNjnifBPlJym/GAwHFRrZn5W/3VH0yYTle1o7vA7t/JK1PpMDq9zgug8hYcrLUc8u3AKJyx6jtdzlU52g= Received: by 10.35.18.3 with SMTP id v3mr19543838pyi; Sat, 16 Sep 2006 07:16:51 -0700 (PDT) Received: by 10.35.112.18 with HTTP; Sat, 16 Sep 2006 07:16:51 -0700 (PDT) Message-ID: <70e8236f0609160716y56f2a8a6lfabc60966feb1a43@mail.gmail.com> Date: Sat, 16 Sep 2006 15:16:51 +0100 From: "Joao Barros" To: current@freebsd.org, stable@freebsd.org, Chris , "=?ISO-8859-1?Q?S=F8ren_Schmidt?=" In-Reply-To: <70e8236f0609141204k57cc16e8v640a692783cdbb77@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: <70e8236f0609090456l31cb39d8if9bdf2d664886a13@mail.gmail.com> <200609091907.06716.max@love2party.net> <70e8236f0609091302i1c98f8f7t6ad32cd602b054c@mail.gmail.com> <20060909200549.GA66552@xor.obsecurity.org> <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> <45043A4F.3010308@errno.com> <70e8236f0609121614h7457f75cufcd232555e0ae5c@mail.gmail.com> <4507A35B.6080205@deepcore.dk> <70e8236f0609130336q66d426dcwa11cede423bcc6f0@mail.gmail.com> <70e8236f0609141204k57cc16e8v640a692783cdbb77@mail.gmail.com> Cc: Subject: panic: integer divide fault 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, 16 Sep 2006 14:16:53 -0000 Hi all, I was contacted by Chris who had the same problem. Since I didn't follow up on my problem he asked me if it was solved and indeed it was solved by S=F8ren and the fix has been committed to CURRENT: http://lists.freebsd.org/pipermail/cvs-all/2006-September/188353.html I'm hoping this gets MFC'ed in time for 6.2 My conversation with S=F8ren is bellow: ---------- Forwarded message ---------- From: Joao Barros Date: Sep 14, 2006 8:04 PM Subject: Re: Fwd: panic: integer divide fault on 6.1 To: S=F8ren Schmidt On 9/13/06, Joao Barros wrote: > On 9/13/06, S=F8ren Schmidt wrote: > > Joao Barros wrote: > > > ---------- Forwarded message ---------- > > > From: Sam Leffler > > > Date: Sep 10, 2006 5:16 PM > > > Subject: Re: panic: integer divide fault on 6.1 > > > To: Joao Barros > > > Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Kris > > > Kennaway > > > > > > > > > Joao Barros wrote: > > >> On 9/9/06, Kris Kennaway wrote: > > >>> On Sat, Sep 09, 2006 at 09:02:35PM +0100, Joao Barros wrote: > > >>> > On 9/9/06, Max Laier wrote: > > >>> > > > > >>> > >Can you try to get a dump, trace, or at least figure out which > > >>> function > > >>> > >the IP is refering to? > > >>> > > > > >>> > > > >>> > Well, the problem only occurs when I boot from the disk and the > > >>> > installed kernel doesn't have debug support. > > >>> > Does 'set dumpdev=3D' work from the boot loader? I tried some > > >>> > combinations with no success. > > >>> > > >>> No. > > >>> > > >>> > I can try and install a 6-STABLE snapshot if there's no way of > > >>> getting > > >>> > the info needed. > > >>> > > >>> You can either try to install a new kernel with DDB support, or fol= low > > >>> the "instruction pointer" method in the developers handbook chapter= on > > >>> kernel debugging. > > >> > > >> I copied a CURRENT kernel from a 200608 snapshot and the problem als= o > > >> occurs thus I'm adding current@. > > >> My current laptop doesn't have a serial port so I'm copying this by > > >> hand: > > >> > > >> Fatal trap 18: integer divide fault while in kernel mode > > >> cpuid =3D 0; apic id =3D 00 > > >> instruction pointer =3D 0x20:0xc08a1fb7 > > >> stack pointer =3D 0x28:0xc0c20b14 > > >> frame pointer =3D 0x28:0xc0c20b9c > > >> 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 0 (swapper) > > >> [thread pid 0 tid 0 ] > > >> Stopped at __qdivrem+0x3b: divl %ecx,%eax > > >> > > >> db> bt > > >> Tracing pid 0 tid0 td 0xc0a0c818 > > >> __qdivrem(37fdfa0,0,0,0,0,...) at __qdivrem+0x3b > > >> __udivdi3(37fdfa0,0,0,0) at __udivdi3+0x16 > > >> ata_raid_promise_read_meta(c37a5000,c09f4a80,1,8086,c37a5000,...) at > > >> ata_raid_promise_read_meta+0x9b > > >> ata_raid_read_metadata(c37a5000,c37a5000,c0c20c70,c06b58a4,c37a5000,= ...) > > >> at ata_raid_metadata+0x2be > > >> ata_raid_subdisk_attach(c37a5000) at ata_raid_subdisk_attach+0x33 > > >> device_attach(c37a5000,c37a5180,c37a5000,c36885c0,0,...) at > > >> device_attach+0x58 > > >> device_probe_and_attach(c37a5200,c37a5200,c08ec9a9,0,c37a5180,...) a= t > > >> bus_generic_attach+0x16 > > >> ad_attach(c37a5200) at ad_attach+0x2c8 > > >> device_attach(c37a5200,c095f2d0,c37a5200,0,c368d800,...) at > > >> device_attach+0x58 > > >> device_probe_and_attach(c37a5200) at device_probe_and_atach+0xe0 > > >> bus_generic_attach(c3659080,c3659080,ffffffff,0,c37a5200,...) at > > >> bus_generic_attach+0x16 > > >> ata_identify(c3659080) at ata_identify+0x1c8 > > >> ata_boot_attach(0xc0a11d80,0,c09212e7,47,...) at ata_boot_attach+0x3= e > > >> run_interrupt_drive_config_hooks(0,c1ec00,c1e000,0,c0451065,...) at > > >> run_interrupt_drive_config_hooks+0x43 > > >> mi_startup() at mi_startup+0x96 > > >> begin() at begin+0x2c > > >> > > >> This board has a Promise SATA raid controller and it is disabled in > > >> the BIOS. I even tried disabling it through a jumper but it still > > >> stops. > > >> > > > > > > In sys/dev/ata/ata-raid.h the PROMISE_LBA macro does an unchecked > > > calculation that apparently can divide by zero. Soren would likely > > > understand the root cause of this problem but until then you can patc= h > > > the driver to workaround the problem. > > > > > > Sam > > > > > > > > > Hi S=F8ren, > > > > > > I don't know if you bumped into this thread but this should definitel= y > > > be fixed. > > > Do you want me to open a PR? > > > > > Hmm, the problem seems to be that the geometry thats gotten from the > > disk has (all) zero's in it, which we cannot handle. > > Its most likely because your BIOS put invalid or no current geometry > > info in the disks parameters page. > > > > If you are up to a little debugging, you could try this patch: > > > > diff -u -r1.189.2.4 ata-disk.c > > --- ata-disk.c 4 Apr 2006 16:07:42 -0000 1.189.2.4 > > +++ ata-disk.c 13 Sep 2006 06:18:59 -0000 > > @@ -97,7 +97,8 @@ > > } > > device_set_ivars(dev, adp); > > > > - if (atadev->param.atavalid & ATA_FLAG_54_58) { > > + if ((atadev->param.atavalid & ATA_FLAG_54_58) && > > + atadev->param.current_heads && atadev->param.current_sectors) { > > adp->heads =3D atadev->param.current_heads; > > adp->sectors =3D atadev->param.current_sectors; > > adp->total_secs =3D (u_int32_t)atadev->param.current_size_1 | > > > > > > -S=F8ren > > > > Sure, I'll test it when I get home later today and start building a > kernel on another machine that's currently off. > I'll give you feedback tomorrow. > Thanks, > > -- > Joao Barros > I'm happy to report that your patch did the trick. The machine happily boot a today's CURRENT+patch :) Tell me if you need to test something more. Thanks! -- Joao Barros From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 14:47: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 998E816A47B for ; Sat, 16 Sep 2006 14:47:00 +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 EBCAE43D49 for ; Sat, 16 Sep 2006 14:46:59 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A5040.dip.t-dialin.net [84.154.80.64]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8GEkvKf069961 for ; Sat, 16 Sep 2006 16:46:58 +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.13.6/8.13.6) with ESMTP id k8GEkuRt003063 for ; Sat, 16 Sep 2006 16:46:56 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8GEkufu076827 for ; Sat, 16 Sep 2006 16:46:56 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609161446.k8GEkufu076827@fire.jhs.private> To: freebsd-stable@freebsd.org In-reply-to: References: Comments: In-reply-to Ian Smith message dated "Sat, 16 Sep 2006 23:58:16 +1000." Date: Sat, 16 Sep 2006 16:46:56 +0200 From: "Julian H. Stacey" Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR 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: Sat, 16 Sep 2006 14:47:00 -0000 Ian Smith wrote: > On Sat, 16 Sep 2006, Julian H. Stacey wrote: > > > Hans Lambermont wrote: > > > Julian H. Stacey wrote: > > > > Stable is a misnomer that harms FreeBSD somewhat. > > > Why not rename 'stable' into 'stable-api' ? > > > > Nice, an improvement on what we have :-) If enough agree, > > the name of this mail list could be changed for a start. > > Sure, but what colour the new bikeshed? Trite. Stable != stable. Let Core choose any non misnomer. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 16:11:19 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 4BBA516A407; Sat, 16 Sep 2006 16:11:19 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BF1343D45; Sat, 16 Sep 2006 16:11:18 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.130] (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.13.6/8.13.4) with ESMTP id k8GGBHsA001017; Sat, 16 Sep 2006 18:11:17 +0200 (CEST) (envelope-from sos@deepcore.dk) Message-ID: <450C2227.7090002@deepcore.dk> Date: Sat, 16 Sep 2006 18:11:19 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 1.5.0.2 (X11/20060531) MIME-Version: 1.0 To: Joao Barros References: <70e8236f0609090456l31cb39d8if9bdf2d664886a13@mail.gmail.com> <200609091907.06716.max@love2party.net> <70e8236f0609091302i1c98f8f7t6ad32cd602b054c@mail.gmail.com> <20060909200549.GA66552@xor.obsecurity.org> <70e8236f0609100842v2d10408blca90b966a1f5ff7@mail.gmail.com> <45043A4F.3010308@errno.com> <70e8236f0609121614h7457f75cufcd232555e0ae5c@mail.gmail.com> <4507A35B.6080205@deepcore.dk> <70e8236f0609130336q66d426dcwa11cede423bcc6f0@mail.gmail.com> <70e8236f0609141204k57cc16e8v640a692783cdbb77@mail.gmail.com> <70e8236f0609160716y56f2a8a6lfabc60966feb1a43@mail.gmail.com> In-Reply-To: <70e8236f0609160716y56f2a8a6lfabc60966feb1a43@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v2.0beta Cc: Chris , stable@freebsd.org, current@freebsd.org Subject: Re: panic: integer divide fault 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, 16 Sep 2006 16:11:19 -0000 Joao Barros wrote: > Hi all, > > I was contacted by Chris who had the same problem. > Since I didn't follow up on my problem he asked me if it was solved > and indeed it was solved by Søren and the fix has been committed to > CURRENT: > http://lists.freebsd.org/pipermail/cvs-all/2006-September/188353.html > > I'm hoping this gets MFC'ed in time for 6.2 It will be, I'm collecting fixes in -current that I'll get MFC'd soon... -Søren From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 16:27: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 5750E16A416 for ; Sat, 16 Sep 2006 16:27:04 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9718143D69 for ; Sat, 16 Sep 2006 16:27:00 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 42F4410F24; Sat, 16 Sep 2006 11:27:00 -0500 (CDT) Date: Sat, 16 Sep 2006 11:26:58 -0500 From: Craig Boston To: Danny Braniss Message-ID: <20060916162657.GA31096@nowhere> Mail-Followup-To: Craig Boston , Danny Braniss , Robert Blayzor , Matthew Jacob , freebsd-stable@freebsd.org References: <450B62C9.5000706@inoc.net> <7579f7fb0609152252y5660195fo419a67dbe90904cd@mail.gmail.com> <450BE564.20106@inoc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: Matthew Jacob , freebsd-stable@freebsd.org Subject: Re: iSCSI HBAs X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 16:27:04 -0000 On Sat, Sep 16, 2006 at 03:35:52PM +0300, Danny Braniss wrote: > being involved with the iSCSI initiator for FreeBSD, I can't see where > this can help for a diskless host, or in other words, what's > wrong with NFS? Well, for one thing since iSCSI is designed for SAN use, the filesystem can safely assume that nothing else is accessing it concurrently and do a lot more aggressive caching. NFS has to play it safe and check with the server every time a file is accessed to make sure it hasn't changed. It sounds to me like the OP is thinking about servers in a large data center booting off an iSCSI SAN. Makes migrating off of dead hardware to a new machine (or even a VM) a snap. > also, the TOE cards are not that cheep either :-) my 2c, danny They're usually cheaper than fibre channel HBAs though ;-) Craig From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 18:51: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 6E1CC16A417 for ; Sat, 16 Sep 2006 18:51:52 +0000 (UTC) (envelope-from bblue@netoldies.com) Received: from netoldies.com (nada.netoldies.com [66.146.162.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2551943D49 for ; Sat, 16 Sep 2006 18:51:52 +0000 (GMT) (envelope-from bblue@netoldies.com) Received: from sovaio.netoldies.com by netoldies.com (MDaemon PRO v9.0.6) with ESMTP id md50000130612.msg for ; Sat, 16 Sep 2006 11:51:50 -0700 Date: Sat, 16 Sep 2006 11:51:31 -0700 To: "freebsd-stable@freebsd.org" From: "Bill Blue" Content-Type: text/plain; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable Message-ID: User-Agent: Opera Mail/9.01 (Win32) X-Spam-Processed: netoldies.com, Sat, 16 Sep 2006 11:51:50 -0700 (not processed: message from valid local sender) X-Return-Path: bblue@netoldies.com X-Envelope-From: bblue@netoldies.com X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Subject: Polling and em0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 18:51:52 -0000 polling(4) says that supported devices include em(4) and that polling su= pport is turned on and off with ifconfig's 'polling' option. But ifconf= ig doesn't seem to recognize that option either as a standalone request = or with the initial em0 setup at boot. This is after a source cvsup (releng=3D6 for the frozen for 6.2 sources)= yesterday and buildworld + buildkernel. em support is compiled in the = kernel rather than loaded. Mobo is a Supermicro P4SCT-0 with Intel 875 = chipset. Is this a known issue that I haven't found references to, or perhaps som= ething related to my specific configuration? FreeBSD v2.netoldies.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri S= ep 15 15:14:07 PDT 2006 root@v2.netoldies.com:/usr/obj/usr/src/sys/V= 2KERNEL i386 Thanks --Bill From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 19:12: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 014CA16A415 for ; Sat, 16 Sep 2006 19:12:59 +0000 (UTC) (envelope-from artdesign@mail.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DEA143D4C for ; Sat, 16 Sep 2006 19:12:58 +0000 (GMT) (envelope-from artdesign@mail.ru) Received: from [83.171.86.20] (port=47393 helo=crea7or) by mx27.mail.ru with smtp id 1GOfaz-000O7W-00 for freebsd-stable@freebsd.org; Sat, 16 Sep 2006 23:12:57 +0400 Message-ID: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> From: "Pavel Sokolov" To: Date: Sat, 16 Sep 2006 23:12:45 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Subject: sshd failed to update ( /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 19:12:59 -0000 I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) and by mistake ( or my stupid hands ) I did : cd /usr/src/secure make install now sshd does not work. it tells: /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" I tried to build the system again but the result is same. I did make cleandir ( twice ) in /usr/src and tried this solution: # cd /usr/src/secure/lib/libssh # make obj && make depend && make && make install # cd /usr/src/secure/usr.sbin/sshd # make obj && make depend && make && make install but build fails at: /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:50:31: bsm/audit_uevents.h: No such file or directory /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:51:30: bsm/audit_record.h: No such file or directory mkdep: compile failed *** Error code 1 But make buildworld did the job without error ( at the end of compilation ) If I try to copy libbsm.so/a/1 ( or install libbsm ) to the /usr/lib - sshd can be launched, , but does not allow to login ( abort connection ) without any messages in the log. -- Pavel Sokolov From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 19:34:21 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 D086616A412 for ; Sat, 16 Sep 2006 19:34:21 +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 A71D943D53 for ; Sat, 16 Sep 2006 19:34:21 +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 84C761A4D87 for ; Sat, 16 Sep 2006 12:34:21 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E9E6E5156C; Sat, 16 Sep 2006 15:34:20 -0400 (EDT) Date: Sat, 16 Sep 2006 15:34:20 -0400 From: Kris Kennaway To: stable@FreeBSD.org Message-ID: <20060916193420.GA15647@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Cc: Subject: Attention Julian Stacey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 19:34:21 -0000 You are refusing personal email. This is a bit antisocial since it leaves me no way to reply privately to your email. Kris From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20:11: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 96CA816A407 for ; Sat, 16 Sep 2006 20:11:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17ACC43D49 for ; Sat, 16 Sep 2006 20:11:29 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k8GKBLD7061333; Sat, 16 Sep 2006 16:11:21 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Sat, 16 Sep 2006 16:09:28 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609161609.28528.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Sat, 16 Sep 2006 16:11:22 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1887/Sat Sep 16 14:37:01 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Frode Nordahl Subject: Re: RELENG_6 Livelock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:11:29 -0000 On Saturday 16 September 2006 07:02, Frode Nordahl wrote: > Hello, > > FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE > #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/ > usr/obj/usr/src/sys/PT i386 > > After running some stress tests for 3 days, I wanted to remove some > large directories. Do you have a coredump? I assume you do from your debug output. Can you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply with the output from that? -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20:11:32 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 914E216A524 for ; Sat, 16 Sep 2006 20:11:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E03C643D5D for ; Sat, 16 Sep 2006 20:11:31 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k8GKBLD8061333; Sat, 16 Sep 2006 16:11:28 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Sat, 16 Sep 2006 16:11:11 -0400 User-Agent: KMail/1.9.1 References: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> In-Reply-To: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609161611.11359.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Sat, 16 Sep 2006 16:11:29 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1887/Sat Sep 16 14:37:01 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Pavel Sokolov Subject: Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:11:32 -0000 On Saturday 16 September 2006 15:12, Pavel Sokolov wrote: > I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) > > and by mistake ( or my stupid hands ) I did : > cd /usr/src/secure > make install > > now sshd does not work. it tells: > /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" > > I tried to build the system again but the result is same. > > I did make cleandir ( twice ) in /usr/src and tried this solution: > > # cd /usr/src/secure/lib/libssh > # make obj && make depend && make && make install > # cd /usr/src/secure/usr.sbin/sshd > # make obj && make depend && make && make install > > but build fails at: Use NO_AUDIT=yes in your build and see if that gives you a working sshd. (i.e. make NO_AUDIT=yes depend && make NO_AUDIT=yes && make NO_AUDIT=yes install) -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20:13: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 993EA16A407 for ; Sat, 16 Sep 2006 20:13:11 +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 C48AE43D95 for ; Sat, 16 Sep 2006 20:12:51 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A57B2.dip.t-dialin.net [84.154.87.178]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8GKCho2070502; Sat, 16 Sep 2006 22:12:49 +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.13.6/8.13.6) with ESMTP id k8GKCiGF002312; Sat, 16 Sep 2006 22:12:44 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8GKCi3x080193; Sat, 16 Sep 2006 22:12:44 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609162012.k8GKCi3x080193@fire.jhs.private> To: Kris Kennaway In-reply-to: <20060916193420.GA15647@xor.obsecurity.org> References: <20060916193420.GA15647@xor.obsecurity.org> Comments: In-reply-to Kris Kennaway message dated "Sat, 16 Sep 2006 15:34:20 -0400." Date: Sat, 16 Sep 2006 22:12:44 +0200 From: "Julian H. Stacey" Cc: stable@freebsd.org Subject: Re: Attention Julian Stacey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:13:11 -0000 Kris Kennaway wrote: > You are refusing personal email. This is a bit antisocial since it > leaves me no way to reply privately to your email. Hi Kris, Huh ? Some mistake. No intent to block, except the usual list of spam domains & phrases get filtered. Maybe something got wrongly listed there though. But I have had problems a while back, & been reconfiging lots of things, inc named etc last few days. Wasn't aware anyone inconvenienced, sorry if so. Please private mail max info on nature of the block you see & I'll try to solve it. I'll private mail you (don't want 'em in list archive :-) some addresses you can use to send the debug of the blockage you see & I'm unaware of. Cheers. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20:22:32 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 B62FB16A415; Sat, 16 Sep 2006 20:22:32 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5906943D7E; Sat, 16 Sep 2006 20:22:31 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id B1FB78402; Sat, 16 Sep 2006 22:22:30 +0200 (CEST) In-Reply-To: <200609161609.28528.jhb@freebsd.org> References: <200609161609.28528.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sat, 16 Sep 2006 22:22:29 +0200 To: John Baldwin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6 Livelock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:22:32 -0000 On 16. sep. 2006, at 22.09, John Baldwin wrote: > On Saturday 16 September 2006 07:02, Frode Nordahl wrote: >> Hello, >> >> FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE >> #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/ >> usr/obj/usr/src/sys/PT i386 >> >> After running some stress tests for 3 days, I wanted to remove some >> large directories. > > Do you have a coredump? I assume you do from your debug output. Can > you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and > once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply > with the output from that? I am sorry, I have not. I tried to call doadump, but there was no dumpdevice configured :-( Somehow I have convinced myself that this was turned on by default now, so I have not enabled it explicitly in rc.conf. Is there any way to tell DDB what dumpdevice to use directly? I will configure a dumpdevice and try really hard to make it happen again. -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20: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 DE3D416A494; Sat, 16 Sep 2006 20:55:09 +0000 (UTC) (envelope-from frode@nordahl.net) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA1643D55; Sat, 16 Sep 2006 20:55:08 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.148.126] (dhcp7.xu.nordahl.net [195.159.148.126]) by smtp1.powertech.no (Postfix) with ESMTP id 8E14A828B; Sat, 16 Sep 2006 22:55:07 +0200 (CEST) In-Reply-To: References: <200609161609.28528.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5D255995-5E67-4D21-88A5-54A8385C4935@nordahl.net> Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sat, 16 Sep 2006 22:55:06 +0200 To: John Baldwin X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6 Livelock X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:55:10 -0000 On 16. sep. 2006, at 22.22, Frode Nordahl wrote: > On 16. sep. 2006, at 22.09, John Baldwin wrote: > >> On Saturday 16 September 2006 07:02, Frode Nordahl wrote: >>> Hello, >>> >>> FreeBSD localhost.localdomain 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE >>> #1: Wed Sep 13 00:10:04 CEST 2006 frode@localhost.localdomain:/ >>> usr/obj/usr/src/sys/PT i386 >>> >>> After running some stress tests for 3 days, I wanted to remove some >>> large directories. >> >> Do you have a coredump? I assume you do from your debug output. Can >> you download http://www.FreeBSD.org/~jhb/gdb/gdb6, fire up kgdb, and >> once in kgdb, do 'source /path/to/gdb6' and then run 'ps' and reply >> with the output from that? > > I am sorry, I have not. I tried to call doadump, but there was no > dumpdevice configured :-( > > Somehow I have convinced myself that this was turned on by default > now, so I have not enabled it explicitly in rc.conf. Is there any > way to tell DDB what dumpdevice to use directly? > > I will configure a dumpdevice and try really hard to make it happen > again. I was able to reproduce the livelock again, and this time I had the system armed with dumpon :-) Here is the output you requested: (kgdb) ps pid ppid pgrp uid state wmesg wchan cmd 2535 2499 2535 0 R+ CPU 0 rm 2534 2499 2534 0 L+ *Giant 0xc6704580 rm 2533 2499 2533 0 L+ *Giant 0xc6704580 rm 2532 2499 2532 0 R+ rm 2531 2499 2531 0 L+ *Giant 0xc6704580 rm 2499 2496 2499 0 Ss+ ttyin 0xc655d810 bash 2496 784 2496 0 Rs sshd 852 1 852 0 Rs+ getty 851 1 851 0 Ss+ ttyin 0xc6569010 getty 850 1 850 0 Ss+ ttyin 0xc6568c10 getty 849 1 849 0 Ss+ ttyin 0xc6569c10 getty 848 1 848 0 Ss+ ttyin 0xc6569810 getty 847 1 847 0 Ss+ ttyin 0xc6568410 getty 846 1 846 0 Ss+ ttyin 0xc6568010 getty 845 1 845 0 Ss+ ttyin 0xc6567810 getty 844 1 844 0 Ss+ ttyin 0xc6567c10 getty 802 1 802 0 Rs cron 796 1 796 25 Ss pause 0xc673524c sendmail 790 1 790 0 Rs sendmail 784 1 784 0 Ss select 0xc09ebb64 sshd 763 1 763 0 Rs ntpd 731 725 725 0 S nfslockd 0xc09f4128 rpc.lockd ---Type to continue, or q to quit--- 725 1 725 0 Rs rpc.lockd 720 1 720 0 Rs rpc.statd 715 710 710 0 S - 0xc6715800 nfsd 714 710 710 0 S - 0xc671f000 nfsd 713 710 710 0 S - 0xc651b600 nfsd 712 710 710 0 S - 0xc6715e00 nfsd 710 1 710 0 Ss select 0xc09ebb64 nfsd 708 1 708 0 Ss select 0xc09ebb64 mountd 639 1 639 0 Rs rpcbind 604 1 604 0 Rs syslogd 530 1 530 0 Ss select 0xc09ebb64 devd 43 0 0 0 RL [schedcpu] 42 0 0 0 DL sdflush 0xc09f9554 [softdepflush] 41 0 0 0 RL [syncer] 40 0 0 0 RL [vnlru] 39 0 0 0 DL psleep 0xc09ec0cc [bufdaemon] 38 0 0 0 RL [pagezero] 37 0 0 0 DL psleep 0xc09fa014 [vmdaemon] 36 0 0 0 DL psleep 0xc09f9fd0 [pagedaemon] 35 0 0 0 WL [irq1: atkbd0] 34 0 0 0 DL - 0xc6560a3c [fdc0] 33 0 0 0 WL [irq7: ppc0] 32 0 0 0 WL [swi0: sio] ---Type to continue, or q to quit--- 31 0 0 0 RL [acpi_thermal] 30 0 0 0 DL - 0xc651dd00 [em0 taskq] 29 0 0 0 WL [irq20: amr0] 28 0 0 0 DL idle 0xc651b000 [aic_recovery1] 27 0 0 0 WL [irq17: ahc1] 26 0 0 0 DL idle 0xc651b000 [aic_recovery1] 25 0 0 0 DL idle 0xc648a600 [aic_recovery0] 24 0 0 0 WL [irq16: ahc0] 23 0 0 0 DL idle 0xc648a600 [aic_recovery0] 22 0 0 0 WL [irq15: ata2] 21 0 0 0 WL [irq14: ata0] 20 0 0 0 WL [irq18: fxp0] 19 0 0 0 WL [irq31: acpi0] 18 0 0 0 WL [swi6: Giant taskq] 17 0 0 0 WL [swi6: task queue] 9 0 0 0 DL - 0xc63dfb00 [acpi_task_2] 8 0 0 0 DL - 0xc63dfb00 [acpi_task_1] 7 0 0 0 DL - 0xc63dfb00 [acpi_task_0] 6 0 0 0 DL - 0xc63dfb80 [kqueue taskq] 16 0 0 0 WL [swi2: cambio] 15 0 0 0 WL [swi5: +] 5 0 0 0 DL - 0xc63dfe00 [thread taskq] 14 0 0 0 DL - 0xc09e1aa0 [yarrow] ---Type to continue, or q to quit--- 4 0 0 0 DL - 0xc09e45c8 [g_down] 3 0 0 0 DL - 0xc09e45c4 [g_up] 2 0 0 0 DL - 0xc09e45bc [g_event] 13 0 0 0 WL [swi3: vm] 12 0 0 0 LL *Giant 0xc6704580 [swi4: clock sio] 11 0 0 0 WL [swi1: net] 10 0 0 0 RL [idle] 1 0 1 0 SLs wait 0xc638f000 [init] 0 0 0 0 WLs [swapper] (kgdb) -- Frode Nordahl From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 20: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 E658A16A407 for ; Sat, 16 Sep 2006 20:58:18 +0000 (UTC) (envelope-from perl@ipchains.ru) Received: from www.ebash.ru (ebash.ru [212.158.162.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D77343D60 for ; Sat, 16 Sep 2006 20:58:17 +0000 (GMT) (envelope-from perl@ipchains.ru) Received: from [83.237.248.195] (helo=[192.168.1.40]) by www.ebash.ru with esmtpa (Exim 4.62) (envelope-from ) id 1GOft3-0007ul-Ey; Sat, 16 Sep 2006 23:31:38 +0400 Message-ID: <450C506F.4010007@ipchains.ru> Date: Sat, 16 Sep 2006 23:28:47 +0400 From: "Oleg D." User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Pavel Sokolov References: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> In-Reply-To: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050106090004080009090902" Cc: freebsd-stable@freebsd.org Subject: Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 20:58:19 -0000 This is a cryptographically signed message in MIME format. --------------ms050106090004080009090902 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Pavel Sokolov wrote: > I have RELENG_6 ( just updated and installed kernel , 6_2 prerelease ) > > and by mistake ( or my stupid hands ) I did : > cd /usr/src/secure > make install > > now sshd does not work. it tells: > /libexec/ld-elf.so.1: Shared object "libbsm.so.1" not found, required by "sshd" > > I tried to build the system again but the result is same. > > I did make cleandir ( twice ) in /usr/src and tried this solution: > > # cd /usr/src/secure/lib/libssh > # make obj && make depend && make && make install > # cd /usr/src/secure/usr.sbin/sshd > # make obj && make depend && make && make install > > but build fails at: > > /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:50:31: bsm/audit_uevents.h: No such file or directory > /usr/src/secure/usr.sbin/sshd/../../../crypto/openssh/audit-bsm.c:51:30: bsm/audit_record.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > But make buildworld did the job without error ( at the end of compilation ) > If I try to copy libbsm.so/a/1 ( or install libbsm ) to the /usr/lib - sshd can be launched, , but does not allow to login ( > abort connection ) without any messages in the log. > > -- > Pavel Sokolov > man ldconfig Try to `ldconfig -m /PATH/TO/LIB` - here PATH_TO_LIB not meaning point to lib as it s but only on dir where it placed. if it works fine insert into /etc/defaults/rc.conf in ``ldconfig'' section. Hope it works. And use portupgrade for the future, because it places copy to /usr/local/lib/compat of previous versions of needed libs... -- Oleg D. -- don't believe every word people use to say, they might be wrong. an undefined problem has infinitive number of solutions. --------------ms050106090004080009090902 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII/zCC AtowggJDoAMCAQICEHZ8L/U1RkMGbaQ1o3z0oGcwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDkxNjExNDA1NVoX DTA3MDkxNjExNDA1NVowQjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEfMB0G CSqGSIb3DQEJARYQcGVybEBpcGNoYWlucy5ydTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAN1yMh/VS93G+/+j2ONas+26A1OXNPV2Y27x0TcKtuWQP4OOUOV5qOrS2cLGcsUt xS08gLEEDMqcxzTXt8fAnbgo4z/oyqNcHct2S/UhPWwmlzuAQkC4jz25X6NeJDPIB6u08d4u s84p39wshhXZrZPt+Qkndms7MJ76M8Jo+QPsaSmBD6trjvtK3aU/lQzYpqLLQKchh0HpJ5Zl yOIZY5RcOyVwEj1If7ECJOZJnnjDAMIWy9Psl9npP07RMuJqi8Dcr2LL3e3T++1/wmlar4LX 92EZiYLsWK4FgnBvdh5WqOeFIpeVtFbBqJOBsPDSNhqJbPqGwCcI+O+NY5/0tecCAwEAAaMt MCswGwYDVR0RBBQwEoEQcGVybEBpcGNoYWlucy5ydTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3 DQEBBQUAA4GBAHWBHs8O4Q3G4TISxG1COEDStIoNajnwhoeCvUr/Ye8yJLsHafjqfRupCNYS BY7mNJHjfLTgujL1Ql+ewkwxIi8CFfpBkxf35J+1CQkgD2x7q+LaNztk4/9pnarpRTM+PUgW ueDZ6Yux381cNgTmsWqhD2ZORIgJCK7uU0UZSOIrMIIC2jCCAkOgAwIBAgIQdnwv9TVGQwZt pDWjfPSgZzANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0EwHhcNMDYwOTE2MTE0MDU1WhcNMDcwOTE2MTE0MDU1WjBCMR8wHQYD VQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR8wHQYJKoZIhvcNAQkBFhBwZXJsQGlwY2hh aW5zLnJ1MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3XIyH9VL3cb7/6PY41qz 7boDU5c09XZjbvHRNwq25ZA/g45Q5Xmo6tLZwsZyxS3FLTyAsQQMypzHNNe3x8CduCjjP+jK o1wdy3ZL9SE9bCaXO4BCQLiPPblfo14kM8gHq7Tx3i6zzinf3CyGFdmtk+35CSd2azswnvoz wmj5A+xpKYEPq2uO+0rdpT+VDNimostApyGHQeknlmXI4hljlFw7JXASPUh/sQIk5kmeeMMA whbL0+yX2ek/TtEy4mqLwNyvYsvd7dP77X/CaVqvgtf3YRmJguxYrgWCcG92Hlao54Uil5W0 VsGok4Gw8NI2Gols+obAJwj4741jn/S15wIDAQABoy0wKzAbBgNVHREEFDASgRBwZXJsQGlw Y2hhaW5zLnJ1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEFBQADgYEAdYEezw7hDcbhMhLE bUI4QNK0ig1qOfCGh4K9Sv9h7zIkuwdp+Op9G6kI1hIFjuY0keN8tOC6MvVCX57CTDEiLwIV +kGTF/fkn7UJCSAPbHur4to3O2Tj/2mdqulFMz49SBa54Nnpi7HfzVw2BOaxaqEPZk5EiAkI ru5TRRlI4iswggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcN MTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRp bmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3Vp bmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f 6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/Ef kTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7 AgMBAAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRw Oi8vY3JsLnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8E BAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqG SIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQc UCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bG CE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDZDCCA2ACAQEwdjBiMQswCQYD VQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEHZ8L/U1RkMGbaQ1o3z0 oGcwCQYFKw4DAhoFAKCCAcMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0B CQUxDxcNMDYwOTE2MTkyODQ3WjAjBgkqhkiG9w0BCQQxFgQU1CKTgxGduNdNQFII7iYw9vkE O5gwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZI hvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjEL MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhB2fC/1NUZDBm2k NaN89KBnMIGHBgsqhkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRo YXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBG cmVlbWFpbCBJc3N1aW5nIENBAhB2fC/1NUZDBm2kNaN89KBnMA0GCSqGSIb3DQEBAQUABIIB ABM5Eej/t5GJlmIW6OFHiB/RFJTbqb9hBXQIADCYeKWqp715BVhrUTVESzpd44gYx6q/6MIp nsJmvNzasuGifbVz0DZsfELh3wyjP6FsYamiMc80LzXqr1GUYf/5oSO/p9ica+GGMLtfOdim t5frRPNzLx2/AvOolteRc8zV2r9t3329xK6SZt1bzDsJ+YYxQeI8UgX0LLeZfbkQBo2LW5e2 7VbJwPs8YNxz4YL7kPjH8HYqm2/yUyukJpURKIeAgYZWUIWFrlB3MCdcZO4tuBKMmJE1tORL sp/IChXhBga4RT6mwxEwcjv5LZ+IC8yRy2WmK3jR3+cooEdbhCGM/5sAAAAAAAA= --------------ms050106090004080009090902-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 21:14: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 3A42516A4A7 for ; Sat, 16 Sep 2006 21:14:41 +0000 (UTC) (envelope-from artdesign@mail.ru) Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 409F643D8D for ; Sat, 16 Sep 2006 21:14:23 +0000 (GMT) (envelope-from artdesign@mail.ru) Received: from [83.171.86.20] (port=59698 helo=crea7or) by mx27.mail.ru with smtp id 1GOhUU-000CL5-00 for freebsd-stable@freebsd.org; Sun, 17 Sep 2006 01:14:22 +0400 Message-ID: <002801c6d9d5$14f156e0$7b8dfea9@crea7or> From: "Pavel Sokolov" To: References: <006101c6d9c4$1e7c0720$7b8dfea9@crea7or> <200609161611.11359.jhb@freebsd.org> Date: Sun, 17 Sep 2006 01:14:19 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Subject: Re: sshd failed to update ( /libexec/ld-elf.so.1: Shared object"libbsm.so.1" not found, required by "sshd" ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 21:14:41 -0000 > > # cd /usr/src/secure/lib/libssh > > # make obj && make depend && make && make install > > # cd /usr/src/secure/usr.sbin/sshd > > # make obj && make depend && make && make install > > > > but build fails at: > > Use NO_AUDIT=yes in your build and see if that gives you a working sshd. > (i.e. make NO_AUDIT=yes depend && make NO_AUDIT=yes && > make NO_AUDIT=yes install) > > John Baldwin It works ! Thanks! -- Pavel Sokolov From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 21:36: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 6D18016A4A0 for ; Sat, 16 Sep 2006 21:36:45 +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 EDD5643DA4 for ; Sat, 16 Sep 2006 21:35:46 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A57B2.dip.t-dialin.net [84.154.87.178]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k8GLZiC3070726 for ; Sat, 16 Sep 2006 23:35:45 +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.13.6/8.13.6) with ESMTP id k8GLZlPe002671 for ; Sat, 16 Sep 2006 23:35:47 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id k8GLZkiO081098 for ; Sat, 16 Sep 2006 23:35:46 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200609162135.k8GLZkiO081098@fire.jhs.private> To: stable@freebsd.org In-reply-to: <200609162012.k8GKCi3x080193@fire.jhs.private> References: <20060916193420.GA15647@xor.obsecurity.org> <200609162012.k8GKCi3x080193@fire.jhs.private> Comments: In-reply-to "Julian H. Stacey" message dated "Sat, 16 Sep 2006 22:12:44 +0200." Date: Sat, 16 Sep 2006 23:35:46 +0200 From: "Julian H. Stacey" Cc: Subject: Re: Attention Julian Stacey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 21:36:45 -0000 "Julian H. Stacey" wrote: > Kris Kennaway wrote: > > You are refusing personal email. This is a bit antisocial since it > > leaves me no way to reply privately to your email. > > Hi Kris, > Huh ? Some mistake. No intent to block, except the usual list of > spam domains & phrases get filtered. Maybe something got wrongly > listed there though. But I have had problems a while back, & been > reconfiging lots of things, inc named etc last few days. Wasn't > aware anyone inconvenienced, sorry if so. Please private mail max > info on nature of the block you see & I'll try to solve it. I'll > private mail you (don't want 'em in list archive :-) > some addresses you can use to send the debug of the blockage you > see & I'm unaware of. > Cheers. That mail routed through mu.org which is listed as a spam domain here, so my SMTP issued "Access denied http://berklix.com/~jhs/phone/" (To rescue the occasional non spammer that might inadvertently get caught). I dont keep records of each spam that causes each domain to be added to the spam list. Looking at mu.org To see what it is: http://www.mu.org/ features a female nude. Tableware, Hosting for christians & hodge podge of strange domain names - I wouldn't be suprised if spammers had lurked @ mu.org. Not a tight unified ship. nslookup doesn't show an MX for obsecurity.org @ mu.org, but mu.org was an uplink on Dyn-DNS from kris@obsecurity. Whois lists Paul Saab, not a name I know. I don't use external RBL services, so don't know if public RBLs block mu.org ? -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software From owner-freebsd-stable@FreeBSD.ORG Sat Sep 16 21:42:51 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 7A0C816A59F for ; Sat, 16 Sep 2006 21:42:51 +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 2D4CA43DF3 for ; Sat, 16 Sep 2006 21:42:32 +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 0AA311A3C1C; Sat, 16 Sep 2006 14:42:22 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CE67D5134B; Sat, 16 Sep 2006 17:42:19 -0400 (EDT) Date: Sat, 16 Sep 2006 17:42:19 -0400 From: Kris Kennaway To: "Julian H. Stacey" Message-ID: <20060916214219.GA19007@xor.obsecurity.org> References: <20060916193420.GA15647@xor.obsecurity.org> <200609162012.k8GKCi3x080193@fire.jhs.private> <200609162135.k8GLZkiO081098@fire.jhs.private> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline In-Reply-To: <200609162135.k8GLZkiO081098@fire.jhs.private> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org Subject: Re: Attention Julian Stacey X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 16 Sep 2006 21:42:51 -0000 --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 16, 2006 at 11:35:46PM +0200, Julian H. Stacey wrote: > "Julian H. Stacey" wrote: > > Kris Kennaway wrote: > > > You are refusing personal email. This is a bit antisocial since it > > > leaves me no way to reply privately to your email. > >=20 > > Hi Kris, > > Huh ? Some mistake. No intent to block, except the usual list of > > spam domains & phrases get filtered. Maybe something got wrongly > > listed there though. But I have had problems a while back, & been > > reconfiging lots of things, inc named etc last few days. Wasn't > > aware anyone inconvenienced, sorry if so. Please private mail max > > info on nature of the block you see & I'll try to solve it. I'll > > private mail you (don't want 'em in list archive :-) > > some addresses you can use to send the debug of the blockage you > > see & I'm unaware of. > > Cheers. >=20 > That mail routed through mu.org which is listed as a spam domain here, > so my SMTP issued "Access denied http://berklix.com/~jhs/phone/" > (To rescue the occasional non spammer that might inadvertently get caught= ). >=20 > I dont keep records of each spam that causes each domain to be > added to the spam list. Looking at mu.org To see what it is: > http://www.mu.org/ features a female nude. Tableware, Hosting > for christians & hodge podge of strange domain names - I > wouldn't be suprised if spammers had lurked @ mu.org. Not > a tight unified ship. nslookup doesn't show an MX for > obsecurity.org @ mu.org, but mu.org was an uplink on Dyn-DNS > from kris@obsecurity. Whois lists Paul Saab, not a name I know. > I don't use external RBL services, so don't know if public RBLs block mu.= org ? =20 lol, that's the stupidest thing I've heard all week. finger ps@FreeBSD.org Kris --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFDG+6Wry0BWjoQKURAvjJAKD+n6wHiDMYJCongmqRFK0e5+qViwCcD7lT u8XspHNSguZCw+Ur2/iECwc= =xl0y -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--