From owner-freebsd-current Sun May 12 0:12:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B948C37B401; Sun, 12 May 2002 00:12:45 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4C7Cgf80012; Sun, 12 May 2002 10:12:42 +0300 (EEST) (envelope-from ru) Date: Sun, 12 May 2002 10:12:42 +0300 From: Ruslan Ermilov To: "David O'Brien" , current@FreeBSD.org, Peter Wemm Subject: Re: cvs commit: src/gnu/lib/csu Makefile src/gnu/lib/libgcc Makefile src/gnu/lib/libiberty Makefile src/gnu/lib/libobjc Makefile src/gnu/lib/libstdc++ Makefile config.h src/gnu/lib/libsupc++ Makefile src/gnu/usr.bin/cc Makefile Makefile.fe Makefile.inc ... Message-ID: <20020512071242.GB79173@sunbay.com> References: <200205100854.g4A8soc37068@freefall.freebsd.org> <20020510150427.GA14295@sunbay.com> <20020510164153.B1221@dragon.nuxi.com> <20020511074411.GA87663@sunbay.com> <20020511010027.A84223@dragon.nuxi.com> <20020511093538.GB87663@sunbay.com> <20020511103303.D11340@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="St7VIuEGZ6dlpu13" Content-Disposition: inline In-Reply-To: <20020511103303.D11340@dragon.nuxi.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --St7VIuEGZ6dlpu13 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 11, 2002 at 10:33:03AM -0700, David O'Brien wrote: > On Sat, May 11, 2002 at 12:35:38PM +0300, Ruslan Ermilov wrote: > > > I say again, the malloc usage is not in c-parse.in, it is in the pars= er > > > driver produced by Byacc. > > >=20 > > OK, now that you've explained it: >=20 > I'll look this patch over carefully, but at first glance it all seems > like stylistic changes. Does it fix a bug, or you just don't like how I > did things? >=20 The changes are mostly _not_ stylistic like .ORDER with one argument not making any sense. The reason of this patch is as before -- to avoid redefining system Yacc building rules. The changes also fix the -j buildworld breakage in gnu/usr.bin/cc/cc1plus: # cd gnu/usr.bin/cc/cc1plus # make -j8 depend make: don't know how to make y.tab.h. Stop There're also some unrelated changes sitting in my tree like removing old cruft, which I will submit later when the dust settles down. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --St7VIuEGZ6dlpu13 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE83hXqUkv4P6juNwoRAhW0AJ9H1GHDj2w5tXw1w+ykwgOLeskiJQCeKgI6 0yJzE8DE6JPztLEDcWPP1SE= =q/zI -----END PGP SIGNATURE----- --St7VIuEGZ6dlpu13-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 1:35:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id E4ABD37B401 for ; Sun, 12 May 2002 01:35:18 -0700 (PDT) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 563BE2ABB; Sun, 12 May 2002 10:35:17 +0200 (CEST) Date: Sun, 12 May 2002 10:35:17 +0200 From: Ollivier Robert To: Steve Kargl Cc: FreeBSD Current Users' list Subject: Re: [panic] panic during probe with a gcc 3.1 kernel Message-ID: <20020512083517.GA31209@tara.freenix.org> Mail-Followup-To: Steve Kargl , FreeBSD Current Users' list References: <20020511232828.GA28525@tara.freenix.org> <20020511172316.A73652@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020511172316.A73652@troutmask.apl.washington.edu> User-Agent: Mutt/1.3.28i X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PIII/800 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG According to Steve Kargl: > I reported this earlier today. I had > hint.acpi.0.disable="1" > in /boot/loader.conf to disable ACPI. > If I comment out this hint, the system > boots, but I end up with the following in dmesg. Right, but if I want to be able to suspend / resume my laptop, I *need* to use APM and not ACPI. So I'm fscked up... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 4:15: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 6603137B404 for ; Sun, 12 May 2002 04:14:52 -0700 (PDT) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.2/8.12.2) with ESMTP id g4CBEniL048885; Sun, 12 May 2002 12:14:49 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.2/8.12.2/Submit) with UUCP id g4CBEnSE048884; Sun, 12 May 2002 12:14:49 +0100 (BST) Received: from grimreaper.grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.3/8.12.3) with ESMTP id g4CBBhjV034783; Sun, 12 May 2002 12:11:44 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Message-Id: <200205121111.g4CBBhjV034783@grimreaper.grondar.org> To: Hajimu UMEMOTO Cc: current@FreeBSD.ORG Subject: Re: Perl scripts that need rewriting - Progress! References: In-Reply-To: ; from Hajimu UMEMOTO "Sat, 11 May 2002 02:30:44 +0900." Date: Sun, 12 May 2002 12:11:43 +0100 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > > >>>>> On Thu, 09 May 2002 20:33:22 +0100 > >>>>> Mark Murray said: > > mark> /usr/sbin/scriptdump > > This script is from KAME. It seems that NetBSD doesn't install it. > Is someone actually using it? If okay, I'll change to don't install > it. That sounds good to me! Go right ahead! :) M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn #text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc #application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 4:43:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 9C78537B404; Sun, 12 May 2002 04:43:45 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g4CBhXev019480; Sun, 12 May 2002 04:43:33 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g4CBhXs2019479; Sun, 12 May 2002 04:43:33 -0700 (PDT) Date: Sun, 12 May 2002 04:43:33 -0700 From: "David O'Brien" To: Ruslan Ermilov Cc: current@FreeBSD.org, Peter Wemm Subject: Re: cvs commit: src/gnu/lib/csu Makefile src/gnu/lib/libgcc Makefile src/gnu/lib/libiberty Makefile src/gnu/lib/libobjc Makefile src/gnu/lib/libstdc++ Makefile config.h src/gnu/lib/libsupc++ Makefile src/gnu/usr.bin/cc Makefile Makefile.fe Makefile.inc ... Message-ID: <20020512044333.A19431@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Ruslan Ermilov , current@FreeBSD.org, Peter Wemm References: <200205100854.g4A8soc37068@freefall.freebsd.org> <20020510150427.GA14295@sunbay.com> <20020510164153.B1221@dragon.nuxi.com> <20020511074411.GA87663@sunbay.com> <20020511010027.A84223@dragon.nuxi.com> <20020511093538.GB87663@sunbay.com> <20020511103303.D11340@dragon.nuxi.com> <20020512071242.GB79173@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020512071242.GB79173@sunbay.com>; from ru@FreeBSD.org on Sun, May 12, 2002 at 10:12:42AM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Sat, May 11, 2002 at 10:33:03AM -0700, David O'Brien wrote: > > I'll look this patch over carefully, but at first glance it all seems > > like stylistic changes. Does it fix a bug, or you just don't like how I > > did things? > > The changes are mostly _not_ stylistic like .ORDER with one argument > not making any sense. The reason of this patch is as before -- to > avoid redefining system Yacc building rules. The changes also fix > the -j buildworld breakage in gnu/usr.bin/cc/cc1plus: Maybe they are "cleaner" to you -- but the YACC rules for GCC are rather complicated and what I use is much more direct. You way requires me to remember the 3-4 different ways the YACC _implicit_ rules can affect the build. I feel that for every except you (and maybe BDE) the explicit rules are clearer and more straight forward. I do not see anything wrong with redefining system implicit YACC rules. You have repeatedly hounded me for quite a while about GCC. Since so much of my blood and sweat are not acceptable to you, I encourage you to become the GCC maintainer and do everything to your heart's desire. People are really making me regret that I sweated over GCC 3 to bring it into our tree for all of our architectures and to get many serious bugs fixed in the FSF CVS repository. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 5:26:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 38C3B37B409; Sun, 12 May 2002 05:26:10 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4CCQ6a99943; Sun, 12 May 2002 15:26:06 +0300 (EEST) (envelope-from ru) Date: Sun, 12 May 2002 15:26:06 +0300 From: Ruslan Ermilov To: "David O'Brien" , current@FreeBSD.org, Peter Wemm Subject: Re: cvs commit: src/gnu/lib/csu Makefile src/gnu/lib/libgcc Makefile src/gnu/lib/libiberty Makefile src/gnu/lib/libobjc Makefile src/gnu/lib/libstdc++ Makefile config.h src/gnu/lib/libsupc++ Makefile src/gnu/usr.bin/cc Makefile Makefile.fe Makefile.inc ... Message-ID: <20020512122606.GB96840@sunbay.com> References: <200205100854.g4A8soc37068@freefall.freebsd.org> <20020510150427.GA14295@sunbay.com> <20020510164153.B1221@dragon.nuxi.com> <20020511074411.GA87663@sunbay.com> <20020511010027.A84223@dragon.nuxi.com> <20020511093538.GB87663@sunbay.com> <20020511103303.D11340@dragon.nuxi.com> <20020512071242.GB79173@sunbay.com> <20020512044333.A19431@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <20020512044333.A19431@dragon.nuxi.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, May 12, 2002 at 04:43:33AM -0700, David O'Brien wrote: > > On Sat, May 11, 2002 at 10:33:03AM -0700, David O'Brien wrote: > > > I'll look this patch over carefully, but at first glance it all seems > > > like stylistic changes. Does it fix a bug, or you just don't like ho= w I > > > did things? > >=20 > > The changes are mostly _not_ stylistic like .ORDER with one argument > > not making any sense. The reason of this patch is as before -- to > > avoid redefining system Yacc building rules. The changes also fix > > the -j buildworld breakage in gnu/usr.bin/cc/cc1plus: >=20 > Maybe they are "cleaner" to you -- but the YACC rules for GCC are rather > complicated and what I use is much more direct. You way requires me to > remember the 3-4 different ways the YACC _implicit_ rules can affect the > build. I feel that for every except you (and maybe BDE) the explicit > rules are clearer and more straight forward. I do not see anything wrong > with redefining system implicit YACC rules. >=20 They are not wrong, they are just redundant for most of the part. My changes tell how to build FreeBSD versions of YACC input (.y) files, and how to build FreeBSD versions of YACC output (.c and .h) files. This is only different from your version by letting sys.mk rules run yacc(1), in one well defined way. These changes also resemble those that were before your WIP_GCC31 merge, and for which you already agreed by committing them. Not to say they fix a real bug in the -j case and fix CLEANFILES. > You have repeatedly hounded me for quite a while about GCC. Since so > much of my blood and sweat are not acceptable to you, I encourage you to > become the GCC maintainer and do everything to your heart's desire. >=20 Sorry I was working on cross-platform building issues in the past that also needed some changes in GCC and Binutils. Sorry I sent you too many patches which fixed bugs or added features. Sorry you can't hold an exclusive lock on the whole FreeBSD. Is this really your sight at things? I'm amazed. What you call "hounding" would better be classified as a pure technical feedback including patches and asking related questions, and maintainer is excepted to deal with this load, either accepting patches or rejecting them (giving valid technical reasons). If you aren't capable of accepting useful "critics" (in the form of patches and answering questions), I think you should seriously reconsider whether you really want to continue be a MAINTAINER. (I say "critics" because that's how you probably take what I call "feedback".) > People are really making me regret that I sweated over GCC 3 to bring it > into our tree for all of our architectures and to get many serious bugs > fixed in the FSF CVS repository. >=20 What reward do you need for this? So that nobody reviews your commits, or looks to anything you are maintaining? You want the "god mode" in FreeBSD? Sorry but I'm affraid this is not possible, or FreeBSD should be renamed to ObrienBSD. GCC and Binutils are essential part of FreeBSD, sitting in its heart, and many other folks including me work on related issues, and apparently look to the work you're doing. From my first days in the project, I took it as a joint effort thing, in fact that's one of the reasons I agreed to become a committer, but behavior like you are demonstrating doesn't fold into this. What you don't seem to realize is that people like me and BDE _don't_ blame you but are just trying to help you do the work done. It's a real pita you see the things in a different light. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE83l9eUkv4P6juNwoRAuJvAJwJcJipUxuSjQXV58yGqywvafz3VQCfSF4r umf1EX8UX4AQkzB8gIF5Suo= =Lmqe -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 7:54:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by hub.freebsd.org (Postfix) with ESMTP id 1BFB437B404 for ; Sun, 12 May 2002 07:54:20 -0700 (PDT) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.2/8.12.2) with ESMTP id g4CEsJpf078213 for ; Sun, 12 May 2002 07:54:19 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.2/8.12.2/Submit) id g4CEsJFh078211 for current@freebsd.org; Sun, 12 May 2002 07:54:19 -0700 (PDT) Date: Sun, 12 May 2002 07:54:19 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200205121454.g4CEsJFh078211@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- ===> cpp0 ... Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/gnu/lib/csu. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 8:46:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by hub.freebsd.org (Postfix) with SMTP id 2D76137B408 for ; Sun, 12 May 2002 08:46:48 -0700 (PDT) Message-ID: <20020512154647.16357.qmail@web21106.mail.yahoo.com> Received: from [62.254.0.5] by web21106.mail.yahoo.com via HTTP; Sun, 12 May 2002 08:46:47 PDT Date: Sun, 12 May 2002 08:46:47 -0700 (PDT) From: Hiten Pandya Reply-To: hiten@uk.FreeBSD.org Subject: Review requested for newly added manual page devinfo(8) To: ru@FreeBSD.org Cc: Robert Watson , current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, As per the request of rwatson; and a courtesy which I would like to fulfil. I would be very greatful if you could take a look at the newly added manual page, available at: src/usr.sbin/devinfo/devinfo.8 It was added on Sunday May/12 by Robert Watson. Thank you, Regards. -- Hiten Pandya -- P.S. CC'ed to rwatson@ __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 9:38:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id B03C737B400 for ; Sun, 12 May 2002 09:38:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Sun, 12 May 2002 09:38:15 -0700 Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@encontacto.net@encontacto.net by mail.encontacto.net with HTTP; Sun, 12 May 2002 09:38:15 -0700 Message-ID: <1021221495.3cde9a7742b66@mail.encontacto.net> Date: Sun, 12 May 2002 09:38:15 -0700 From: Edwin Culp To: current@freebsd.org Subject: Problems with ssh connections and Pam on today's current. MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG With this morning's build I have somehow lost ssh. I get the following error: May 12 10:11:03 worldinternet sshd[24224]: in openpam_load_module(): no pam_nologin.so found May 12 10:11:03 worldinternet sshd[24224]: fatal: PAM initialisation failed[1]: failed to load module May 12 10:27:32 worldinternet sshd[24674]: in openpam_load_module(): no pam_nologin.so found May 12 10:27:32 worldinternet sshd[24674]: fatal: PAM initialisation failed[1]: failed to load module It was so strange that I opened a port for telnet as a test and it works fine and the same pam modules are found. Have I done something wrong? I'm going back to look at the changes and see if I can catch what happened. Thanks for any suggestions. ed ------------------------------------------------------------- http://insourcery.com - Mergence of Business and Technology a "Griffin Plaza Partners, LLC" Company To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 10:32:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 073C137B425 for ; Sun, 12 May 2002 10:32:33 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g4CHWX9Q079028 for ; Sun, 12 May 2002 10:32:33 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g4CHWXoj079027 for freebsd-current@freebsd.org; Sun, 12 May 2002 10:32:33 -0700 (PDT) Date: Sun, 12 May 2002 10:32:33 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: buildworld broken in gcc Message-ID: <20020512103233.A78985@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cc -O -pipe -march=athlon -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DHAVE_CONFIG_H -DTARGET_NAME=\"i386-undermydesk-freebsd\" -DIN_GCC -D__FBSDID=__RCSID -c /usr/src/contrib/gcc/final.c -o final.o /usr/src/contrib/gcc/final.c: In function `final_scan_insn': /usr/src/contrib/gcc/final.c:2019: syntax error before "else" *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc_int. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Sources were updated via cvsup at 9:56 PDT on 12 May 02. I believe the above is a side effect of other problems in the build, because /usr/src/contrib/gcc/final.c was last updated 2 days ago and it compiled fine yesterday. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 11:18: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 0E60437B404; Sun, 12 May 2002 11:18:04 -0700 (PDT) Received: from pool0083.cvx40-bradley.dialup.earthlink.net ([216.244.42.83] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 176xv1-0006Ga-00; Sun, 12 May 2002 11:18:03 -0700 Message-ID: <3CDEB1BD.F4923D53@mindspring.com> Date: Sun, 12 May 2002 11:17:33 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.org Cc: Ruslan Ermilov , current@FreeBSD.org, Peter Wemm Subject: Re: cvs commit: src/gnu/lib/csu Makefile src/gnu/lib/libgcc Makefile src/gnu/lib/libiberty Makefile src/gnu/lib/libobjc Makefile src/gnu/lib/libstdc++ Makefile config.h src/gnu/lib/libsupc++ Makefile src/gnu/usr.bin/cc Makefile Makefile.fe Makefile.inc ... References: <200205100854.g4A8soc37068@freefall.freebsd.org> <20020510150427.GA14295@sunbay.com> <20020510164153.B1221@dragon.nuxi.com> <20020511074411.GA87663@sunbay.com> <20020511010027.A84223@dragon.nuxi.com> <20020511093538.GB87663@sunbay.com> <20020511103303.D11340@dragon.nuxi.com> <20020512071242.GB79173@sunbay.com> <20020512044333.A19431@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > People are really making me regret that I sweated over GCC 3 to bring it > into our tree for all of our architectures and to get many serious bugs > fixed in the FSF CVS repository. Really? It must be in private email... from what I've seen, everything went incredibly smoothly -- moreso than could be reasonably expected. The only think I personally saw that was anywhere close to a real problem was the 96 byte boot bloat, which I think can be resolved with explicit aligns/#pragma pack(1), and disabling one of the speed vs. space optimizations (the instruction pipelining). The mailing lists have been, as far as I could tell, blissfully silent on the subject. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 11:23:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx3.datanet.hu (mx3.datanet.hu [194.149.13.160]) by hub.freebsd.org (Postfix) with ESMTP id 2F15C37B407 for ; Sun, 12 May 2002 11:23:35 -0700 (PDT) Received: from fonix.adamsfamily.xx (nilus-1053.adsl.datanet.hu [195.56.92.37]) by mx3.datanet.hu (DataNet) with ESMTP id CC6EB1E9EBB for ; Sun, 12 May 2002 20:23:32 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.3/8.12.3) with ESMTP id g4CINnIr077366 for ; Sun, 12 May 2002 20:23:49 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.3/8.12.3/Submit) id g4CINmvE077365 for freebsd-current@freebsd.org; Sun, 12 May 2002 20:23:48 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sun, 12 May 2002 20:23:48 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: Special fx with disklabel(8)? Message-ID: <20020512182347.GD613@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I have a -CURRENT from May 5th. I recently bought a new 40 gig IDE disk and proceeded to install it. I went for "compatible" (as opposed to "dangerously dedicated") mode. I first used fdisk to initialize the slice table and create a FreeBSD slice that would take in the whole disk. After that, I proceeded to disklabel the slice thus created. This used to work just fine with a commandline like this: disklabel -B -w -r /dev/ad1s1 auto But now, although the kernel complaints about the disk not having a disklabel stopped, I could not edit the label I supposedly just created, with the command: disklabel -e /dev/ad1s1 After checking with fdisk, it turned out that the slice I created there (which was the first "partition" in DOS parlance) got deleted, and replaced by a very small (something like 24 megs) slice listed as the fourth primary. In addition, although up till then the kernel detected the disk's size properly on bootup, it got confused and guessed it was bigger than in reality. I deleted and started over, again, fdisk went fine, the slice got created, I could see it with fdisk, it spanned the whole disk, but after the disklabel we were back to square one. When doing it for the third time, I, for the heck of it, tried "disklabel -e" right after the "fdisk -Bi". And, to my great surprise, a disklabel *was* found on the slice, and it was even mostly correct, save for the fact that now it seemed to stick to the erroneous values for c/h/s and size that it snatched out of thin air previously. (Note: The bad values are not necessarily a bug. The BIOS has no opinion on the disk because it is too big for it. When it tries to detect it, the machine just hangs. So, it is set to "None" in the BIOS setup, which allows the system to boot, but obviously the BIOS hints are not there. Obviously, this is not the only disk in the system, and not even the system disk:-) I am aware of disklabel changes recently, the question is: Was this some sort of expected, or are these special fx only fata morgana on my machine, or...? In other words, has the recommended way of installing a disk in "compatible" mode into the system changed? Is fdisk somehow supposed to create a disklabel? And, is disklabel expected to mess with the fdisk tabales? (when it is used on a slice, not the whole disk) Any and all hardware details available if needed. Have a nice weekend! -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 11:36: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id CEA2B37B40C for ; Sun, 12 May 2002 11:35:50 -0700 (PDT) Received: from pool0083.cvx40-bradley.dialup.earthlink.net ([216.244.42.83] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 176yCC-0006UR-00; Sun, 12 May 2002 11:35:48 -0700 Message-ID: <3CDEB5E6.17F4509B@mindspring.com> Date: Sun, 12 May 2002 11:35:18 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: freebsd-current@freebsd.org Subject: Re: Special fx with disklabel(8)? References: <20020512182347.GD613@fonix.adamsfamily.xx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG DOS partition tables use a 24b C/H/S value. With 512B sectors, this means they are incapable of representing more than 8G of disk space. To support a 32b sector offset, you have to go to LBA mode. This isn't really supported by any BIOS that still respects the C/H/S offsets, since they will override. What probably happened is that you had an overflow that wrapped you back to the start of the disk. The general answer on this is: use "dangerously dedicated mode for very large disks". It's possible to work around this, but it's really a pain, and you have to know what you are doing. Chapter 5 of the PReP specification has an excellent tutorial on LBA addressing and DOS partition tables (much better than any Intel related information I have seen to date), if you want to fix this problem, rather than just ignoring it. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 11:46:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 47FE337B404 for ; Sun, 12 May 2002 11:46:33 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g4CIjrHA002199; Sun, 12 May 2002 20:45:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Terry Lambert Cc: Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? In-Reply-To: Your message of "Sun, 12 May 2002 11:35:18 PDT." <3CDEB5E6.17F4509B@mindspring.com> Date: Sun, 12 May 2002 20:45:53 +0200 Message-ID: <2198.1021229153@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CDEB5E6.17F4509B@mindspring.com>, Terry Lambert writes: >DOS partition tables use a 24b C/H/S value. With 512B sectors, this >means they are incapable of representing more than 8G of disk space. Ahh, I love these time-warp emails from Terry. [*] This is the way the world looked circa 1990. I doubt any normal person has any MBR records which hasn't valid contents in the 32 bit sector count fields which have been part of the MBR record from at least 1994, and probably earlier. Please do not follow Terrys advice, unless and until you have independent confirmation that his 10 year old knowledge is still current. Poul-Henning [*] Not! > >To support a 32b sector offset, you have to go to LBA mode. This >isn't really supported by any BIOS that still respects the C/H/S >offsets, since they will override. > >What probably happened is that you had an overflow that wrapped >you back to the start of the disk. > >The general answer on this is: use "dangerously dedicated mode for >very large disks". > >It's possible to work around this, but it's really a pain, and you >have to know what you are doing. Chapter 5 of the PReP specification >has an excellent tutorial on LBA addressing and DOS partition tables >(much better than any Intel related information I have seen to date), >if you want to fix this problem, rather than just ignoring it. > >-- Terry > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 11:59:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 9020C37B408 for ; Sun, 12 May 2002 11:59:41 -0700 (PDT) Received: from pool0083.cvx40-bradley.dialup.earthlink.net ([216.244.42.83] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 176yZE-0004tx-00; Sun, 12 May 2002 11:59:36 -0700 Message-ID: <3CDEBB7A.D67A8F7A@mindspring.com> Date: Sun, 12 May 2002 11:59:06 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? References: <2198.1021229153@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > Please do not follow Terrys advice, unless and until you have > independent confirmation that his 10 year old knowledge is still > current. Poul: "I will say that advice is bad, but I will not provide advice of my own, because it might be bad, too, and open me to the same type of attack I like to make on others. It's just so much easier to criticize someone than it is to help solve a problem and risk being attacked by someone else like me". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 12: 4:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 1A0BC37B403 for ; Sun, 12 May 2002 12:04:55 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g4CJ4GHA002476; Sun, 12 May 2002 21:04:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Terry Lambert Cc: Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? In-Reply-To: Your message of "Sun, 12 May 2002 11:59:06 PDT." <3CDEBB7A.D67A8F7A@mindspring.com> Date: Sun, 12 May 2002 21:04:16 +0200 Message-ID: <2475.1021230256@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CDEBB7A.D67A8F7A@mindspring.com>, Terry Lambert writes: >Poul-Henning Kamp wrote: >> Please do not follow Terrys advice, unless and until you have >> independent confirmation that his 10 year old knowledge is still >> current. > >Poul: "I will say that advice is bad, but I will not provide advice > of my own, because it might be bad, too, and open me to the > same type of attack I like to make on others. It's just so > much easier to criticize someone than it is to help solve a > problem and risk being attacked by someone else like me". Terry: "I would appreciate if you would ensure that your knowledge is up to date before you mislead people with it." -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 13:39:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from herbelot.dyndns.org (d013.dhcp212-198-27.noos.fr [212.198.27.13]) by hub.freebsd.org (Postfix) with ESMTP id CD44337B404 for ; Sun, 12 May 2002 13:39:16 -0700 (PDT) Received: from herbelot.com (tulipe.herbelot.nom [192.168.1.5]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id WAA71385 for ; Sun, 12 May 2002 22:39:10 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3CDED2ED.E9300AEE@herbelot.com> Date: Sun, 12 May 2002 22:39:09 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: compilation failure (in the kernel SCSI code) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, the import of GCC3.1 seems to reveal old bugs : (while cross-compiling a new kernel atfer cross-compiling a new -Current world under a fresh -Stable) (the %b flag is not recognized in the printf()s of scsi_low.c) %----------------------------- cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I/files2/SrcCurrent/src/sys -I/files2/SrcCurrent/src/sys/dev -I/files2/SrcCurrent/src/sys/contrib/dev/acpica -I/files2/SrcCurrent/src/sys/contrib/ipfilter -I/files2/SrcCurrent/src/sys/../include -D_KERNEL -ffreestanding -include opt_global.h -fno-common -mpreferred-stack-boundary=2 -ffreestanding -Werror /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c cc1: warnings being treated as errors /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c: In function `scsi_low_calcf_show': /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4661: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4661: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c: In function `scsi_low_print': /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4896: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4896: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4916: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4916: warning: too many arguments for format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4929: warning: unknown conversion type character `b' in format /files2/SrcCurrent/src/sys/cam/scsi/scsi_low.c:4929: warning: too many arguments for format *** Error code 1 Stop in /files2/obj/files2/SrcCurrent/src/sys/multi-Cur. *** Error code 1 Stop in /files2/SrcCurrent/src. *** Error code 1 Stop in /files2/SrcCurrent/src. portable# pwd %----------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 13:46:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.165]) by hub.freebsd.org (Postfix) with ESMTP id C378037B405 for ; Sun, 12 May 2002 13:46:05 -0700 (PDT) Received: from fonix.adamsfamily.xx (nilus-1053.adsl.datanet.hu [195.56.92.37]) by mx1.datanet.hu (DataNet) with ESMTP id 620A126A702 for ; Sun, 12 May 2002 22:46:03 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.3/8.12.3) with ESMTP id g4CKkKIr086168 for ; Sun, 12 May 2002 22:46:20 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.3/8.12.3/Submit) id g4CKkKRR086167 for freebsd-current@FreeBSD.ORG; Sun, 12 May 2002 22:46:20 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sun, 12 May 2002 22:46:19 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? Message-ID: <20020512204619.GH613@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <3CDEBB7A.D67A8F7A@mindspring.com> <2475.1021230256@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2475.1021230256@critter.freebsd.dk> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello everybody, OK, just in order to clarify before things get out of hand.:-) There is no immediate problem, the drive in question has been installed and works fine. (using it this instant). As for the BIOS part, the mobo could probably use an upgrade, because the BIOS is still from spring of 1998. Award BIOS-en from around that date had a problem that became known, as I learned through research, as the "65536 cyl", or "32GB barrier." The behaviour of the BIOS is very much like it. And yes, this is an Award PnP v4.51PG on a Shuttle Spacewalker HOT-637/P (Intel 440LX chipset. Yes, old:-) I was more curious than anything else: Since I disabled the drive in the BIOS, it was entirely up to FreeBSD to decide what to do. The boot process detected it with 79408/16/63, which is OK. The disklabel however, somehow contained a larger number than the disk's capacity and got the C value wrong. Of course, this was easily fixed with "disklabel -e". Indeed, an overflow somewhere might have caused the symptoms. This definitely did not happen on this system, under an earlier -CURRENT and with a then-new 15 gig disk. And no, I do not think 40 gig drives count as "very large" these days. I am not sure what would have happened, if the BIOS support had been correct to begin with. In fact, I did not even expect that the drive would be found and probed correctly under the present circumstances, in other words, FreeBSD caused a pleasant surprise. I just got a bit worried, since 80 gig disks are quickly becoming commonplace in modern PCs, and I was hoping that dd mode would not be *the* way to use them under FreeBSD:-). And Terry and Poul-Henning, please stop fighting, I am not going to do anything to the system wrt this just now:-) -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 14:22:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 8E9C537B400 for ; Sun, 12 May 2002 14:22:27 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id g4CLMRJ98980 for ; Sun, 12 May 2002 14:22:27 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3) with ESMTP id g4CLMbfF021013 for ; Sun, 12 May 2002 14:22:37 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3/Submit) id g4CLMbLh021012 for current@FreeBSD.org; Sun, 12 May 2002 14:22:37 -0700 (PDT) Date: Sun, 12 May 2002 14:22:36 -0700 From: Marcel Moolenaar To: current@FreeBSD.org Subject: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Message-ID: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gang, I occasionally get tcsh coredumps (signal 6). I mostly ignored it, but today I decided to track it down for once. This is the backtrace: (gdb) bt #0 0x808e4a3 in access () #1 0x80ba9fa in abort () at /usr/src/lib/libc/../libc/stdlib/abort.c:78 #2 0x80b97a9 in wrtwarning (p=0x80ef54e "in free():") at /usr/src/lib/libc/../libc/stdlib/malloc.c:314 #3 0x80b97c8 in wrtwarning (p=0x80ef54e "in free():") at /usr/src/lib/libc/../libc/stdlib/malloc.c:315 #4 0x80ba5aa in malloc (size=1644) at /usr/src/lib/libc/../libc/stdlib/malloc.c:1093 #5 0x8079163 in smalloc (n=1644) at /usr/src/bin/csh/../../contrib/tcsh/tc.alloc.c:505 #6 0x80757d8 in ReBufferDisplay () at /usr/src/bin/csh/../../contrib/tcsh/ed.screen.c:506 #7 0x8077cf9 in ChangeSize (lins=24, cols=80) at /usr/src/bin/csh/../../contrib/tcsh/ed.screen.c:1742 #8 0x8071542 in check_window_size (force=0) at /usr/src/bin/csh/../../contrib/tcsh/ed.init.c:128 #9 0x8071564 in window_change (snum=28) at /usr/src/bin/csh/../../contrib/tcsh/ed.init.c:148 #10 #11 0x80baa8f in memcpy () #12 0x80ba6c9 in free (ptr=0x814f600) at /usr/src/lib/libc/../libc/stdlib/malloc.c:1125 #13 0x8079287 in sfree (p=0x814f600) at /usr/src/bin/csh/../../contrib/tcsh/tc.alloc.c:586 #14 0x805c2ca in blkfree (av0=0x814f600) at /usr/src/bin/csh/../../contrib/tcsh/sh.misc.c:169 #15 0x8057600 in backeval (cp=0x8150900, literal=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:842 #16 0x80574e8 in dobackp (cp=0x8147060, literal=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:784 #17 0x8056aa1 in globexpand (v=0x814ac54) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:386 #18 0x8057171 in globall (v=0x814ac50) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:632 #19 0x80622c1 in set1 (var=0x814acf0, vec=0x814ac50, head=0x8130fc4, flags=2) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:616 #20 0x806227a in set (var=0x814acf0, val=0x8147060, flags=2) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:601 #21 0x8061a41 in doset (v=0x814f200, c=0x814cce0) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:292 #22 0x8053428 in func (t=0x814cce0, bp=0x80f4a44) at /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:149 #23 0x80608d7 in execute (t=0x814cce0, wanttty=634, pipein=0x0, pipeout=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:657 #24 0x8060b15 in execute (t=0x814ccc0, wanttty=634, pipein=0x0, pipeout=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:734 #25 0x804a847 in process (catch=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:2125 #26 0x804a0f9 in srcunit (unit=3, onlyown=1, hflg=0, av=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1661 #27 0x8049cce in srcfile (f=0x814b700 "USER", onlyown=1, flag=0, av=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1468 #28 0x8049c70 in srccat (cp=0x814ca00, dp=0x80f64a4) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1441 #29 0x8049973 in main (argc=0, argv=0xbfbffaa4) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1301 Apparently what's happening is that tcsh get's interrupted while in free() and the signal handler itself calls malloc(). Note that this typically happens when I open a new GNOME terminal. I guess the grand question is: is this a genuine bug or just a nasty side effect of our malloc options? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 14:28:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id BDCE537B401 for ; Sun, 12 May 2002 14:28:19 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g4CLRgHA003859; Sun, 12 May 2002 23:27:42 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal In-Reply-To: Your message of "Sun, 12 May 2002 14:22:36 PDT." <20020512212236.GB20876@dhcp01.pn.xcllnt.net> Date: Sun, 12 May 2002 23:27:42 +0200 Message-ID: <3858.1021238862@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That one's easy to diagnose: You change your windowsize while tcsh happened to be in free(3) (frame #12). tcsh gets the SIGWINSZ (sp?) signal, and tries to allocate a buffer, probably a new line-edit buffer, calls malloc(3) (fram #4) and malloc abort(3)'s the program. It is not legal to recursively call malloc/free/realloc, and therefore you should either protect all calls to malloc/free/realloc by blocking signals or better: not call them in signal handlers. The correct solution is probably to set a flag in the signal handler and resize the buffer before the next line is read. Poul-Henning In message <20020512212236.GB20876@dhcp01.pn.xcllnt.net>, Marcel Moolenaar writ es: >Gang, > >I occasionally get tcsh coredumps (signal 6). I mostly ignored it, >but today I decided to track it down for once. This is the backtrace: > >(gdb) bt >#0 0x808e4a3 in access () >#1 0x80ba9fa in abort () at /usr/src/lib/libc/../libc/stdlib/abort.c:78 >#2 0x80b97a9 in wrtwarning (p=0x80ef54e "in free():") at /usr/src/lib/libc/../libc/stdlib/malloc.c:314 >#3 0x80b97c8 in wrtwarning (p=0x80ef54e "in free():") at /usr/src/lib/libc/../libc/stdlib/malloc.c:315 >#4 0x80ba5aa in malloc (size=1644) at /usr/src/lib/libc/../libc/stdlib/malloc.c:1093 >#5 0x8079163 in smalloc (n=1644) at /usr/src/bin/csh/../../contrib/tcsh/tc.alloc.c:505 >#6 0x80757d8 in ReBufferDisplay () at /usr/src/bin/csh/../../contrib/tcsh/ed.screen.c:506 >#7 0x8077cf9 in ChangeSize (lins=24, cols=80) at /usr/src/bin/csh/../../contrib/tcsh/ed.screen.c:1742 >#8 0x8071542 in check_window_size (force=0) at /usr/src/bin/csh/../../contrib/tcsh/ed.init.c:128 >#9 0x8071564 in window_change (snum=28) at /usr/src/bin/csh/../../contrib/tcsh/ed.init.c:148 >#10 >#11 0x80baa8f in memcpy () >#12 0x80ba6c9 in free (ptr=0x814f600) at /usr/src/lib/libc/../libc/stdlib/malloc.c:1125 >#13 0x8079287 in sfree (p=0x814f600) at /usr/src/bin/csh/../../contrib/tcsh/tc.alloc.c:586 >#14 0x805c2ca in blkfree (av0=0x814f600) at /usr/src/bin/csh/../../contrib/tcsh/sh.misc.c:169 >#15 0x8057600 in backeval (cp=0x8150900, literal=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:842 >#16 0x80574e8 in dobackp (cp=0x8147060, literal=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:784 >#17 0x8056aa1 in globexpand (v=0x814ac54) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:386 >#18 0x8057171 in globall (v=0x814ac50) at /usr/src/bin/csh/../../contrib/tcsh/sh.glob.c:632 >#19 0x80622c1 in set1 (var=0x814acf0, vec=0x814ac50, head=0x8130fc4, flags=2) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:616 >#20 0x806227a in set (var=0x814acf0, val=0x8147060, flags=2) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:601 >#21 0x8061a41 in doset (v=0x814f200, c=0x814cce0) at /usr/src/bin/csh/../../contrib/tcsh/sh.set.c:292 >#22 0x8053428 in func (t=0x814cce0, bp=0x80f4a44) at /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:149 >#23 0x80608d7 in execute (t=0x814cce0, wanttty=634, pipein=0x0, pipeout=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:657 >#24 0x8060b15 in execute (t=0x814ccc0, wanttty=634, pipein=0x0, pipeout=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.sem.c:734 >#25 0x804a847 in process (catch=0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:2125 >#26 0x804a0f9 in srcunit (unit=3, onlyown=1, hflg=0, av=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1661 >#27 0x8049cce in srcfile (f=0x814b700 "USER", onlyown=1, flag=0, av=0x0) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1468 >#28 0x8049c70 in srccat (cp=0x814ca00, dp=0x80f64a4) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1441 >#29 0x8049973 in main (argc=0, argv=0xbfbffaa4) at /usr/src/bin/csh/../../contrib/tcsh/sh.c:1301 > >Apparently what's happening is that tcsh get's interrupted while >in free() and the signal handler itself calls malloc(). Note that >this typically happens when I open a new GNOME terminal. > >I guess the grand question is: is this a genuine bug or just a nasty >side effect of our malloc options? > >-- > Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 14:30:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 3A9C337B401 for ; Sun, 12 May 2002 14:30:09 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g4CLU8ev046112; Sun, 12 May 2002 14:30:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g4CLU892046111; Sun, 12 May 2002 14:30:08 -0700 (PDT) Date: Sun, 12 May 2002 14:30:08 -0700 From: "David O'Brien" To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: buildworld broken in gcc Message-ID: <20020512143008.A46067@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020512103233.A78985@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020512103233.A78985@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Sun, May 12, 2002 at 10:32:33AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 12, 2002 at 10:32:33AM -0700, Steve Kargl wrote: > cc -O -pipe -march=athlon -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/i386/usr\" -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DHAVE_CONFIG_H -DTARGET_NAME=\"i386-undermydesk-freebsd\" -DIN_GCC -D__FBSDID=__RCSID -c /usr/src/contrib/gcc/final.c -o final.o > /usr/src/contrib/gcc/final.c: In function `final_scan_insn': > /usr/src/contrib/gcc/final.c:2019: syntax error before "else" > *** Error code 1 This is fixed. Please cvsup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 14:32:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3ADD337B403 for ; Sun, 12 May 2002 14:32:56 -0700 (PDT) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.3/8.12.3) with ESMTP id g4CLWmEN017652; Sun, 12 May 2002 17:32:49 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.3/8.12.3/Submit) id g4CLWmHl017649; Sun, 12 May 2002 17:32:48 -0400 (EDT) Date: Sun, 12 May 2002 17:32:48 -0400 (EDT) From: Garrett Wollman Message-Id: <200205122132.g4CLWmHl017649@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal In-Reply-To: <3858.1021238862@critter.freebsd.dk> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > The correct solution is probably to set a flag in the signal handler > and resize the buffer before the next line is read. Or, somewhat less optimally, to block SIGWINCH (and any other signals with similar handler behavior) around calls to malloc and free. This is still not *correct*, mind you, but will make the condition less likely. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 14:53:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id DBF8337B406; Sun, 12 May 2002 14:53:04 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 88E0D117; Sun, 12 May 2002 22:52:33 +0100 (BST) Date: Sun, 12 May 2002 22:52:33 +0100 From: Josef Karthauser To: Ollivier Robert Cc: FreeBSD Current Users' list , joe@FreeBSD.org Subject: Re: [panic] USB related panic Message-ID: <20020512215233.GB1346@genius.tao.org.uk> References: <20020511120038.GA506@sidhe.freenix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020511120038.GA506@sidhe.freenix.org> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, May 11, 2002 at 02:00:38PM +0200, Ollivier Robert wrote: > > FreeBSD sidhe.freenix.org FreeBSD 5.0-CURRENT #6: Thu May 9 17:14:15 CEST 2002 > roberto@sidhe.freenix.org:/local/src/src/sys/i386/compile/SIDHE i386 > > Sony VAIO Z600TEK, current just before gcc 3.1. > > Having tested the usb subsystem a few weeks ago (it hung during resume), I > decided to try after the latest fixes from Joe. kldload usb; kldload ums > and I plugged my optical mouse (see below the messages). > > Then I suspend/resume the machine. This time it didn't hung (thanks Joe!) > but the mouse wasn't functionning. Killing and restarting usbd gave > nothing. I then decided to kill moused: instant panic... > > Joe, any idea? > Both uhci and ohci have suspend/resume code in them that's not activated yet (it didn't port clean, and I've not put the time into sorting it out yet). I guess that stack frame #13 to #19 are usb code and that you're running it from a module so the debugger doesn't have access to the symbols. If you get a moment perhaps you could track down where in the usb code the panic occured. I compile the usb driver into the kernel to get around the symbol problem. Joe > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xdeadc0de > fault code = supervisor read, page not present > instruction pointer = 0x8:0xce8fd9f7 > stack pointer = 0x10:0xce7f6ac8 > frame pointer = 0x10:0xce7f6adc > 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 = 536 (moused) > trap number = 12 > panic: page fault > syncing disks... panic: bremfree: bp 0xc7496f60 not locked > Uptime: 30m26s > pfs_vncache_unload(): 1 entries remaining > Dumping 255 MB > ata0: resetting devices .. done > 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 > --- > #0 doadump () at ../../../kern/kern_shutdown.c:213 > 213 dumping++; > #0 doadump () at ../../../kern/kern_shutdown.c:213 > #1 0xc017e53d in boot (howto=260) at ../../../kern/kern_shutdown.c:346 > #2 0xc017e6d5 in panic (fmt=0xc026fd99 "bremfree: bp %p not locked") > at ../../../kern/kern_shutdown.c:490 > #3 0xc01aa811 in bremfree (bp=0xc7496f60) at ../../../kern/vfs_bio.c:619 > #4 0xc01abf47 in vfs_bio_awrite (bp=0xc7496f60) > at ../../../kern/vfs_bio.c:1593 > #5 0xc020c118 in ffs_fsync (ap=0xce7f6980) at > ../../../ufs/ffs/ffs_vnops.c:219 > #6 0xc020a93e in ffs_sync (mp=0xcda98000, waitfor=2, cred=0xc7373f00, > td=0xc0298cc0) at vnode_if.h:441 > #7 0xc01b8c71 in sync (td=0xc0298cc0, uap=0x0) > at ../../../kern/vfs_syscalls.c:1224 > #8 0xc017e1fb in boot (howto=256) at ../../../kern/kern_shutdown.c:254 > #9 0xc017e6d5 in panic (fmt=0xc0289b3e "%s") > at ../../../kern/kern_shutdown.c:490 > #10 0xc024c1e2 in trap_fatal (frame=0xce7f6a88, eva=3735929054) > at ../../../i386/i386/trap.c:826 > #11 0xc024bf2d in trap_pfault (frame=0xce7f6a88, usermode=0, eva=3735929054) > at ../../../i386/i386/trap.c:740 > #12 0xc024bb73 in trap (frame={tf_fs = -1070858216, tf_es = -830537712, > tf_ds = 16, tf_edi = -34, tf_esi = -833817856, tf_ebp = -830510372, > tf_isp = -830510412, tf_ebx = -830098048, tf_edx = 0, tf_ecx = 4, > tf_eax = -559038242, tf_trapno = 12, tf_err = 0, tf_eip = -829433353, > tf_cs = 8, tf_eflags = 66182, tf_esp = -833817856, tf_ss = -833298432}) > at ../../../i386/i386/trap.c:426 > #13 0xce8fd9f7 in ?? () > #14 0xce900969 in ?? () > #15 0xce900b34 in ?? () > #16 0xce8fd9c5 in ?? () > #17 0xce8fd6f0 in ?? () > #18 0xce7bca11 in ?? () > #19 0xce7bca8e in ?? () > #20 0xc015c201 in spec_close (ap=0xce7f6b90) > at ../../../fs/specfs/spec_vnops.c:617 > #21 0xc015b839 in spec_vnoperate (ap=0xce7f6b90) > at ../../../fs/specfs/spec_vnops.c:121 > #22 0xc01beb20 in vn_close (vp=0xce500000, flags=7, cred=0xce85b380, > td=0xce7f2728) at vnode_if.h:183 > #23 0xc01bf726 in vn_closefile (fp=0xce39ad98, td=0xce7f2728) > at ../../../kern/vfs_vnops.c:798 > #24 0xc0169c8a in fdrop_locked (fp=0xce39ad98, td=0xce7f2728) > at ../../../sys/file.h:225 > #25 0xc016946f in fdrop (fp=0xce39ad98, td=0xce7f2728) > at ../../../kern/kern_descrip.c:1635 > #26 0xc016943c in closef (fp=0xce39ad98, td=0xce7f2728) > at ../../../kern/kern_descrip.c:1621 > #27 0xc0168e2d in fdfree (td=0xce7f2728) at > ../../../kern/kern_descrip.c:1375 > #28 0xc016d8bf in exit1 (td=0xce7f2728, rv=0) at > ../../../kern/kern_exit.c:201 > #29 0xc016d642 in sys_exit (td=0xce7f2728, uap=0xce7f6d20) > at ../../../kern/kern_exit.c:109 > #30 0xc024c46b in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = 0, tf_esi = -1, tf_ebp = -1077938896, tf_isp = -830509708, > tf_ebx = 672189240, tf_edx = 672188640, tf_ecx = -1077938384, > tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 671786631, tf_cs = 31, > tf_eflags = 647, tf_esp = -1077938940, tf_ss = 47}) > at ../../../i386/i386/trap.c:1019 > #31 0xc024002d in syscall_with_err_pushed () > #32 0x8049f31 in ?? () > #33 > #34 0x8049843 in ?? () > #35 0x8049843 in ?? () > #36 0x8048de9 in ?? () > > -=-=-=- > May 11 13:50:32 sidhe kernel: uhci0: p > ort 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 > May 11 13:50:32 sidhe kernel: usb0: on > uhci0 > May 11 13:50:32 sidhe kernel: usb0: USB revision 1.0 > May 11 13:50:32 sidhe kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1. > 00, addr 1 > May 11 13:50:32 sidhe kernel: uhub0: 2 ports with 2 removable, self powered > May 11 13:50:34 sidhe kernel: uhub1: Philips Semiconductors hub, class 9/0, rev > 1.10/1.10, addr 2 > May 11 13:50:34 sidhe kernel: uhub1: 3 ports with 3 removable, self powered > May 11 13:51:13 sidhe kernel: ums0: Microsoft Microsoft IntelliMouse ? with Inte > lliEye, rev 1.10/1.00, addr 4, iclass 3/1 > May 11 13:51:13 sidhe kernel: ums0: 3 buttons and Z dir. > -=-=-=- > > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 15: 0:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 48A0837B405 for ; Sun, 12 May 2002 15:00:19 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id g4CM03J99062; Sun, 12 May 2002 15:00:03 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3) with ESMTP id g4CM0DfF021106; Sun, 12 May 2002 15:00:13 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3/Submit) id g4CM07aS021105; Sun, 12 May 2002 15:00:07 -0700 (PDT) Date: Sun, 12 May 2002 15:00:07 -0700 From: Marcel Moolenaar To: Terry Lambert Cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: does the order of .a files matter? Message-ID: <20020512220007.GA21019@dhcp01.pn.xcllnt.net> References: <200205101233.g4ACXctb041093@corbulon.video-collage.com> <3CDBFA7E.A2A1F09F@mindspring.com> <200205101343.01636.mi+mx@aldan.algebra.com> <3CDC2F2C.2CB9C818@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CDC2F2C.2CB9C818@mindspring.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, May 10, 2002 at 01:35:56PM -0700, Terry Lambert wrote: > Mikhail Teterin wrote: > > = For my information: Why didn't you take John De Bowsky's advice to: > > = > > = ld $objlist `lorder $liblist | tsort -q` > > > > I tried that before I asked on the mailing list the first time. It > > did reduce the number of the undefined symbols, but not to zero. > > It's possible that the symbols are truly undefined (e.g. "stat64"), > but I think that is unlikely. > > Here is what I think: > > Your proximal problem is that your libraries are badly organized, and > therefore certain object files in them are not being pulled into the > linking process, because your order of operation on the objects is not > in dependency order, because of the improper organization. A challenge: Linkers normally pull in everything they can from archive libraries and do not require that object files in archive libraries be ordered in dependency order, nor do they require archive libraries to contain object files multiple times to break circular dependencies. They do this by iterating over the archive library until no new binding is possible (whether it's iterating over the index or over the whole archive). If you think that providing bits on the link line in dependency order is a natural way of linking and the "proper" way of doing it, how do you explain our improper use of putting object files in lexical order in libraries and how do you resolve the contradiction that from a build point of view the lexical order is the proper way of building and we only get away with that because the linker doesn't require object files in archive libraries to be in dependency order (or we manually correct the situation by duplication)? Also, to me it looks like a gross inconsistency that can be easily solved by having the linker remember symbols it has seen (and where) even though they are not unresolved at the time the symbols are seen. How does reordering or restructuring source code solely to make the linker happy be in anyway better than simply make the linker less dumb (be it optional)? I don't intend to start a discussion, just contemplation when I say: The reason linkers behave the way they do does not necessarily have to be a good one according to current standards. I've often wondered about what makes the current behaviour good and have never found a reason better than "it's easier for the linker". This however can easily be rejected as unimportant, because tools are supposed to make it easier for the user. To me the behaviour of linkers is therefore mostly hysterical and I personally would not use it as an argument to distinguish good source organisation from bad... > Most linkers don't do what you want, which is make up for programmer > incompetence by doing an automatic topological sort on all symbol Which programmers do you mean: the programmers writing linkers or...? :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 15:20:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id D68BB37B405 for ; Sun, 12 May 2002 15:20:46 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id g4CMKdJ99095; Sun, 12 May 2002 15:20:39 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3) with ESMTP id g4CMKnfF021165; Sun, 12 May 2002 15:20:49 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3/Submit) id g4CMKnmu021164; Sun, 12 May 2002 15:20:49 -0700 (PDT) Date: Sun, 12 May 2002 15:20:48 -0700 From: Marcel Moolenaar To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Message-ID: <20020512222048.GB21019@dhcp01.pn.xcllnt.net> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3858.1021238862@critter.freebsd.dk> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: > > It is not legal to recursively call malloc/free/realloc, and therefore > you should either protect all calls to malloc/free/realloc by blocking > signals or better: not call them in signal handlers. Ok, thanks. I guess we have a genuine tcsh(1) bug here. Who's maintaining tcsh? Can he/she suggest what to do or otherwise take it from here? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 15:32:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.pair.com (relay1.pair.com [209.68.1.20]) by hub.freebsd.org (Postfix) with SMTP id 4163437B403 for ; Sun, 12 May 2002 15:32:52 -0700 (PDT) Received: (qmail 16012 invoked from network); 12 May 2002 22:32:51 -0000 Received: from 12-236-91-101.client.attbi.com (HELO ?10.1.1.198?) (12.236.91.101) by relay1.pair.com with SMTP; 12 May 2002 22:32:51 -0000 X-pair-Authenticated: 12.236.91.101 Mime-Version: 1.0 X-Sender: (Unverified) Message-Id: In-Reply-To: <20020512222048.GB21019@dhcp01.pn.xcllnt.net> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> <20020512222048.GB21019@dhcp01.pn.xcllnt.net> Date: Sun, 12 May 2002 15:32:49 -0700 To: Marcel Moolenaar From: Mark Peek Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Cc: current@FreeBSD.ORG, Poul-Henning Kamp Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 3:20 PM -0700 5/12/02, Marcel Moolenaar wrote: >On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: >> >> It is not legal to recursively call malloc/free/realloc, and therefore >> you should either protect all calls to malloc/free/realloc by blocking >> signals or better: not call them in signal handlers. > >Ok, thanks. I guess we have a genuine tcsh(1) bug here. > >Who's maintaining tcsh? Can he/she suggest what to do or otherwise >take it from here? I've been maintaining tcsh. Can you file a PR and assign it to me? I'll follow up with the tcsh owner to resolve the problem. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 16:25:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id A2B2937B404; Sun, 12 May 2002 16:25:13 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.6/8.11.4) with ESMTP id g4CNPDJ99250; Sun, 12 May 2002 16:25:13 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3) with ESMTP id g4CNPMfF041137; Sun, 12 May 2002 16:25:23 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.3/8.12.3/Submit) id g4CNPMm9041136; Sun, 12 May 2002 16:25:22 -0700 (PDT) Date: Sun, 12 May 2002 16:25:21 -0700 From: Marcel Moolenaar To: Mark Peek Cc: current@FreeBSD.org Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal Message-ID: <20020512232521.GA21913@dhcp01.pn.xcllnt.net> References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> <20020512222048.GB21019@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 12, 2002 at 03:32:49PM -0700, Mark Peek wrote: > > I've been maintaining tcsh. Can you file a PR and assign it to me? > I'll follow up with the tcsh owner to resolve the problem. PR: bin/38006. Backtrace and and libc hack to easily reproduce the condition included. Thanks, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 20:51:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from ref5.freebsd.org (ref5.FreeBSD.org [216.136.204.102]) by hub.freebsd.org (Postfix) with ESMTP id ADFDB37B401 for ; Sun, 12 May 2002 20:51:13 -0700 (PDT) Received: from ref5.freebsd.org (localhost [127.0.0.1]) by ref5.freebsd.org (8.12.2/8.12.2) with ESMTP id g4D3pDuH003095 for ; Sun, 12 May 2002 20:51:13 -0700 (PDT) (envelope-from des@ref5.freebsd.org) Received: (from des@localhost) by ref5.freebsd.org (8.12.2/8.12.2/Submit) id g4D3pDr6003063 for current@freebsd.org; Sun, 12 May 2002 20:51:13 -0700 (PDT) Date: Sun, 12 May 2002 20:51:13 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200205130351.g4D3pDr6003063@ref5.freebsd.org> To: current@freebsd.org Subject: i386 tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tmp/des/obj/i386/d/home/des/tinderbox/src/i386/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- ===> kerberosIV/lib/libkdb ... /d/home/des/tinderbox/src/crypto/kerberosIV/lib/kdb/krb_kdb_utils.c:200: warning: passing arg 1 of `des_pcbc_encrypt' from incompatible pointer type /d/home/des/tinderbox/src/crypto/kerberosIV/lib/kdb/krb_kdb_utils.c:200: warning: passing arg 2 of `des_pcbc_encrypt' from incompatible pointer type /d/home/des/tinderbox/src/crypto/kerberosIV/lib/kdb/krb_kdb_utils.c: In function `kdb_encrypt_key': /d/home/des/tinderbox/src/crypto/kerberosIV/lib/kdb/krb_kdb_utils.c:200: warning: passing arg 1 of `des_pcbc_encrypt' from incompatible pointer type /d/home/des/tinderbox/src/crypto/kerberosIV/lib/kdb/krb_kdb_utils.c:200: warning: passing arg 2 of `des_pcbc_encrypt' from incompatible pointer type ===> kerberosIV/lib/libkrb ===> kerberosIV/lib/libtelnet cc1: warnings being treated as errors /d/home/des/tinderbox/src/crypto/telnet/libtelnet/kerberos.c: In function `kerberos4_cksum': /d/home/des/tinderbox/src/crypto/telnet/libtelnet/kerberos.c:496: warning: unreachable code at beginning of switch statement *** Error code 1 Stop in /d/home/des/tinderbox/src/kerberosIV/lib/libtelnet. *** Error code 1 Stop in /d/home/des/tinderbox/src/kerberosIV/lib. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 22:20:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 0A59B37B404 for ; Sun, 12 May 2002 22:20:24 -0700 (PDT) Received: from pool0365.cvx40-bradley.dialup.earthlink.net ([216.244.43.110] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 1778Fr-0003f4-00; Sun, 12 May 2002 22:20:15 -0700 Message-ID: <3CDF4CF1.410E6589@mindspring.com> Date: Sun, 12 May 2002 22:19:45 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? References: <2475.1021230256@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > >> Please do not follow Terrys advice, unless and until you have > >> independent confirmation that his 10 year old knowledge is still > >> current. > > > >Poul: "I will say that advice is bad, but I will not provide advice > > of my own, because it might be bad, too, and open me to the > > same type of attack I like to make on others. It's just so > > much easier to criticize someone than it is to help solve a > > problem and risk being attacked by someone else like me". > > Terry: "I would appreciate if you would ensure that your knowledge > is up to date before you mislead people with it." Poul: "Of course, *my* knowledge is up to date because *I'm* Poul; but I'll be damned if I'll share it, because then I can't beat people over the head for not having it, and beating people over the head is ever so much more fun, isn't it? Meanwhile, I'm still not going to answer the original poster's question...". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 22:34: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 491DC37B411 for ; Sun, 12 May 2002 22:33:51 -0700 (PDT) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.3/8.12.2) with ESMTP id g4D5Xmla047022; Mon, 13 May 2002 07:33:48 +0200 (CEST) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.3/8.12.3/Submit) id g4D5XmIK047021; Mon, 13 May 2002 07:33:48 +0200 (CEST) Date: Mon, 13 May 2002 07:33:48 +0200 From: Wilko Bulte To: Terry Lambert Cc: Poul-Henning Kamp , Szilveszter Adam , freebsd-current@FreeBSD.ORG Subject: Re: Special fx with disklabel(8)? Message-ID: <20020513073348.D46885@freebie.xs4all.nl> References: <2475.1021230256@critter.freebsd.dk> <3CDF4CF1.410E6589@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3CDF4CF1.410E6589@mindspring.com>; from tlambert2@mindspring.com on Sun, May 12, 2002 at 10:19:45PM -0700 X-OS: FreeBSD 4.6-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 12, 2002 at 10:19:45PM -0700, Terry Lambert wrote: > Poul-Henning Kamp wrote: > > >> Please do not follow Terrys advice, unless and until you have > > >> independent confirmation that his 10 year old knowledge is still > > >> current. > > > > > >Poul: "I will say that advice is bad, but I will not provide advice > > > of my own, because it might be bad, too, and open me to the > > > same type of attack I like to make on others. It's just so > > > much easier to criticize someone than it is to help solve a > > > problem and risk being attacked by someone else like me". > > > > Terry: "I would appreciate if you would ensure that your knowledge > > is up to date before you mislead people with it." > > Poul: "Of course, *my* knowledge is up to date because *I'm* Poul; but > I'll be damned if I'll share it, because then I can't beat people > over the head for not having it, and beating people over the head > is ever so much more fun, isn't it? Meanwhile, I'm still not > going to answer the original poster's question...". Gentlemen.. does this discussion on a public list serve any useful purpose? -- | / o / /_ _ FreeBSD core team secretary |/|/ / / /( (_) Bulte wilko@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 23:10:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id E8B4837B40E for ; Sun, 12 May 2002 23:07:46 -0700 (PDT) Received: from pool0246.cvx40-bradley.dialup.earthlink.net ([216.244.42.246] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 1778zh-0003Mz-00; Sun, 12 May 2002 23:07:37 -0700 Message-ID: <3CDF57EF.443F3BE7@mindspring.com> Date: Sun, 12 May 2002 23:06:39 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Marcel Moolenaar Cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: does the order of .a files matter? References: <200205101233.g4ACXctb041093@corbulon.video-collage.com> <3CDBFA7E.A2A1F09F@mindspring.com> <200205101343.01636.mi+mx@aldan.algebra.com> <3CDC2F2C.2CB9C818@mindspring.com> <20020512220007.GA21019@dhcp01.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > > Here is what I think: > > > > Your proximal problem is that your libraries are badly organized, and > > therefore certain object files in them are not being pulled into the > > linking process, because your order of operation on the objects is not > > in dependency order, because of the improper organization. > > A challenge: > > Linkers normally pull in everything they can from archive libraries Actually, they don't. They only pull in onjects that define symbols that are undefined at the time the library is encountered, in order, on the linker line. Anyone who doesn't believe this needs to write an X11 application that uses Xt, Xext, and some widget toolkit, and then play with library order other than "-lX11 -lXt -lXext". > and do not require that object files in archive libraries be ordered > in dependency order, nor do they require archive libraries to contain > object files multiple times to break circular dependencies. They do > this by iterating over the archive library until no new binding is > possible (whether it's iterating over the index or over the whole > archive). Actually, they do this by looking at the library symbol index, which is either created automatically by the ar, or, on BSD based systems, added by the program "ranlib". > If you think that providing bits on the link line in dependency order > is a natural way of linking and the "proper" way of doing it, how do > you explain our improper use of putting object files in lexical order > in libraries and how do you resolve the contradiction that from a build > point of view the lexical order is the proper way of building and we > only get away with that because the linker doesn't require object > files in archive libraries to be in dependency order (or we manually > correct the situation by duplication)? I explain the lexical ordering by way of the following commands when exiting the Makefile in "vi" in command mode: !!ls *.c JJJJJJJJJJJJJJJJJ[...] ISRCS= 8-). > Also, to me it looks like a gross inconsistency that can be easily > solved by having the linker remember symbols it has seen (and where) > even though they are not unresolved at the time the symbols are seen. "info ld" This is not historical UNIX "ld" behaviour, and it is not default GNU "ld" behaviour. > How does reordering or restructuring source code solely to make the > linker happy be in anyway better than simply make the linker less > dumb (be it optional)? When you are using a library as a library, rather than as a silly workaround to command line length limitations, you only want to pull in the object files from the archive which are actually used. By ordering the source code properly, less code gets pulled in when you are not actually using every function within a library. Linking fewer object files into an executable makes the executable smaller. Smaller executables are better than larger executables from a putatively "smarter" linker (personally, I measure linker intelligence as inversely proportional to the resulting executable size, relative to the idealized executable size). Also, putting related code adjacently results in the code fitting within the peephole. This permits the cimplier's optimizer to do things that it would otherwise be unable to do. Optimized executables are better than those that aren't. So organizing functions into the correct object modules, and the object modules into correct libraries, rather than choosing the organization at random, is important, if you care about code size and/or optimizer efficiency. > I don't intend to start a discussion, just contemplation when I say: > > The reason linkers behave the way they do does not necessarily have > to be a good one according to current standards. I've often wondered > about what makes the current behaviour good and have never found a > reason better than "it's easier for the linker". This however can > easily be rejected as unimportant, because tools are supposed to make > it easier for the user. To me the behaviour of linkers is therefore > mostly hysterical and I personally would not use it as an argument > to distinguish good source organisation from bad... The most common excuse I'm aware of is "To get faster compile times when benchmarked against other compilers". On slow enough, or emulated, hardware, though, it's a legitimate complaint that linking speed becomes a developement bottleneck. > > Most linkers don't do what you want, which is make up for programmer > > incompetence by doing an automatic topological sort on all symbol > > Which programmers do you mean: the programmers writing linkers or...? > > :-) I had a big gripe, complete with examples involving famous names, ready to go. But I will replace it with a much smaller response: "A craftsman must know his tools". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 23:12:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 3550637B400 for ; Sun, 12 May 2002 23:12:49 -0700 (PDT) Received: from pool0246.cvx40-bradley.dialup.earthlink.net ([216.244.42.246] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 17794i-0006ZV-00; Sun, 12 May 2002 23:12:48 -0700 Message-ID: <3CDF5942.7E9BF47E@mindspring.com> Date: Sun, 12 May 2002 23:12:18 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: Keywords: pre-GCC3 tcsh coredump free/malloc reentrancy signal References: <20020512212236.GB20876@dhcp01.pn.xcllnt.net> <3858.1021238862@critter.freebsd.dk> <20020512222048.GB21019@dhcp01.pn.xcllnt.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > On Sun, May 12, 2002 at 11:27:42PM +0200, Poul-Henning Kamp wrote: > > It is not legal to recursively call malloc/free/realloc, and therefore > > you should either protect all calls to malloc/free/realloc by blocking > > signals or better: not call them in signal handlers. > > Ok, thanks. I guess we have a genuine tcsh(1) bug here. > > Who's maintaining tcsh? Can he/she suggest what to do or otherwise > take it from here? The Single UNIX Specification Standard and POSIX both explicitly state that it is not safe to call memory management functions from signal handlers. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 12 23:44:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from nova.anchoragerescue.org (95-7-237-24-cable.anchorageak.net [24.237.7.95]) by hub.freebsd.org (Postfix) with ESMTP id 87E3437B403 for ; Sun, 12 May 2002 23:44:47 -0700 (PDT) Received: from there (localhost.anchoragerescue.org [127.0.0.1]) by nova.anchoragerescue.org (Postfix) with SMTP id 24A203443 for ; Sun, 12 May 2002 22:44:41 -0800 (AKDT) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul Reply-To: akbeech@sinbad.net To: freebsd-current@freebsd.org Subject: -current Build Error Date: Sun, 12 May 2002 22:44:40 -0800 X-Mailer: KMail [version 1.3] Organization: Sinbad Network Communications MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020513064441.24A203443@nova.anchoragerescue.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting the following on today's -current: cc1: warnings being treated as errors /usr/src/sys/dev/ata/atapi-fd.c: In function `afd_describe': /usr/src/sys/dev/ata/atapi-fd.c:191: warning: too many arguments for format *** Error code 1 Stop in /usr/obj/usr/src/sys/NOVA. *** Error code 1 I built with -DNO_WERROR, but it didn't seem to matter. Also, cvsup was done just prior, and an hour later. Any suggestions? Beech -- ------------------------------------------------------------------- Beech Rintoul - SysAdmin - akbeech@sinbad.net /"\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 0:51:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E16A237B406 for ; Mon, 13 May 2002 00:51:47 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAB13064; Mon, 13 May 2002 17:51:39 +1000 Date: Mon, 13 May 2002 17:53:50 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Thierry Herbelot Cc: "current@FreeBSD.ORG" Subject: Re: compilation failure (in the kernel SCSI code) In-Reply-To: <3CDED2ED.E9300AEE@herbelot.com> Message-ID: <20020513175142.C12713-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 12 May 2002, Thierry Herbelot wrote: > the import of GCC3.1 seems to reveal old bugs : > (while cross-compiling a new kernel atfer cross-compiling a new -Current > world under a fresh -Stable) > (the %b flag is not recognized in the printf()s of scsi_low.c) This is just because gcc-3's format recognizer doesn't recognize %b or any of the other nonstandard kernel printf formats yet. Kernels must be compiled with warnings ignored or printf format checking turned off until this is fixed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 2:37:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id CFB6B37B405 for ; Mon, 13 May 2002 02:37:17 -0700 (PDT) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 177CG8-000K2C-00; Mon, 13 May 2002 11:36:48 +0200 From: Sheldon Hearn To: "David W. Chapman Jr." Cc: Jeff Ito , current@FreeBSD.org Subject: Re: make.conf and -CURRENT In-reply-to: Your message of "Fri, 10 May 2002 17:46:31 EST." <20020510224631.GD40656@leviathan.inethouston.net> Date: Mon, 13 May 2002 11:36:48 +0200 Message-ID: <77015.1021282608@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 10 May 2002 17:46:31 EST, "David W. Chapman Jr." wrote: > > sysctl.conf is also missing. If its not there, it doesn't get > > parsed. You only need make.conf if you wish to put stuff in there. > > same with rc.conf, except everyone puts something in rc.conf > > > N/m on the sysctl.conf I think that one exists now. I think it'd be nice if it didn't. Files that don't contain anything just make for mergemaster annoyance. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 3:42:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by hub.freebsd.org (Postfix) with ESMTP id 31FC137B403 for ; Mon, 13 May 2002 03:42:33 -0700 (PDT) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 0747A2A9B; Mon, 13 May 2002 12:42:32 +0200 (CEST) Date: Mon, 13 May 2002 12:42:31 +0200 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Re: [panic] USB related panic Message-ID: <20020513104231.GA62405@tara.freenix.org> Mail-Followup-To: FreeBSD Current Users' list References: <20020511120038.GA506@sidhe.freenix.org> <20020512215233.GB1346@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020512215233.GB1346@genius.tao.org.uk> User-Agent: Mutt/1.3.28i X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PIII/800 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG According to Josef Karthauser: > and that you're running it from a module so the debugger doesn't have > access to the symbols. If you get a moment perhaps you could track > down where in the usb code the panic occured. I compile the usb driver > into the kernel to get around the symbol problem. I'll compile a kernel with usb builtin and test it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 6:58:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id E853837B401 for ; Mon, 13 May 2002 06:58:07 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g4DDvSHA015005 for ; Mon, 13 May 2002 15:57:29 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: GCC 3.1 generates bounds traps for bogous va_arg() use... From: Poul-Henning Kamp Date: Mon, 13 May 2002 15:57:28 +0200 Message-ID: <15004.1021298248@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG GCC 3.1 whines about these two instances of va_arg() and generates code which calls "int 5" if they are executed. This workaround works for me, but I don't know if this is the correct fix so I won't commit it. In light of this, we may want to change the kernels panic message for these traps to be more informative. Poul-Henning Index: bios.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/bios.c,v retrieving revision 1.52 diff -u -r1.52 bios.c --- bios.c 17 Apr 2002 13:06:35 -0000 1.52 +++ bios.c 13 May 2002 13:53:27 -0000 @@ -363,7 +363,11 @@ break; case 's': /* 16-bit integer */ +#if 0 i = va_arg(ap, u_short); +#else + i = va_arg(ap, u_int); +#endif stack -= 2; break; @@ -435,7 +439,11 @@ break; case 's': /* 16-bit integer */ +#if 0 i = va_arg(ap, u_short); +#else + i = va_arg(ap, u_int); +#endif *(u_short *)stack = i; stack += 2; break; -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7: 1:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.wineasy.se (smtp.wineasy.se [195.42.198.20]) by hub.freebsd.org (Postfix) with ESMTP id DF54037B400; Mon, 13 May 2002 07:01:37 -0700 (PDT) Received: from veidit.net ([213.88.130.20]) by relay.wineasy.se with ESMTP id g4DE1an02503; Mon, 13 May 2002 16:01:36 +0200 Message-ID: <3CDFC73D.4020208@veidit.net> Date: Mon, 13 May 2002 16:01:33 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020510 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current Cc: freebsd-mobile Subject: Problem with Intel 2011b Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello I just got my hands on a Intel 2011b Wireless card, I'm running FreeBSD current (dated just before gcc 3.1). Now my problem is that I insert the card and well nothing happens, the system gets locked, when I remove the card I everything starts working once again, and it says it can't manage card ("null"), ("null") Any one got any idea? mvh /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:13:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by hub.freebsd.org (Postfix) with ESMTP id 0FBCE37B40D; Mon, 13 May 2002 07:13:36 -0700 (PDT) Received: from misha (250-217.customer.cloud9.net [168.100.250.217]) by corbulon.video-collage.com (8.12.2/8.12.2) with ESMTP id g4DEDV5D053971 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 13 May 2002 10:13:33 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: corbulon.video-collage.com: Host 250-217.customer.cloud9.net [168.100.250.217] claimed to be misha Content-Type: text/plain; charset="iso-8859-1" From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Giorgos Keramidas , Makoto Matsushita Subject: Re: cvs commit: src/sbin/newfs newfs.8 newfs.c Date: Mon, 13 May 2002 10:12:15 -0400 X-Mailer: KMail [version 1.4] Cc: current@FreeBSD.ORG References: <200205021323.g42DNOMG025311@250-217.customer.cloud9.net> <20020502230656U.matusita@jp.FreeBSD.org> <20020510193552.GG2699@hades.hell.gr> In-Reply-To: <20020510193552.GG2699@hades.hell.gr> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200205131012.15962.mi+mx@aldan.algebra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday 10 May 2002 03:35 pm, Giorgos Keramidas wrote: = On 2002-05-02 23:06, Makoto Matsushita wrote: = > = > Mikhail.Teterin> BTW, whatever became of the effort to make a = > Mikhail.Teterin> wrapper called mount_mfs? = > = > See mdmfs(8). It was been there since Jun/2001 (about 10 months = > ago). = = By casully skimming through the text of mdmfs(8) I don't see how it = could be used to mount an MFS filesystem from fstab though :/ It could be -- by making a mount_mfs a symlink to mdmfs. That was the compromise agreed on :-\ However, the entire md things is lacking one important feature of the the old mfs. Mfs was using virtual memory, subject to the general memory management by the OS. md will use either a the real RAM (malloc type) or the swap (swap). This is acceptable for many, but not for all. I, for example, don't have a dedicated swap partition to list in the fstab -- I use the Windows' swap file^ (pagefile.sys) instead*. This is also in the /etc/rc.local, so when the /etc/fstab is processed during boot there is no swap at all and mount_mfs-ing fails... -mi ^This should be offered by sysinstall if the dual-boot configuration is detected at the install time. Also, why can swapon(2), or, at least, swapon(8) automaticly handle swapping onto files? *Since md replaced another system -- vn(4), I'll mention another missing feature -- /etc/vntab. I suspect, one has to be a long entrenched veteran of the FreeBSD project to be allowed to push out features (vnconfig, mount_mfs) without providing _complete_ replacements first. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:22:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by hub.freebsd.org (Postfix) with ESMTP id 7216037B405 for ; Mon, 13 May 2002 07:22:31 -0700 (PDT) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.2/8.12.2) with ESMTP id g4DEMVpf057551 for ; Mon, 13 May 2002 07:22:31 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.2/8.12.2/Submit) id g4DEMUTM057549 for current@freebsd.org; Mon, 13 May 2002 07:22:30 -0700 (PDT) Date: Mon, 13 May 2002 07:22:30 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200205131422.g4DEMUTM057549@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- ===> lib/libtacplus ===> lib/libutil ===> lib/libypclnt ===> lib/compat ===> lib/libalias ===> lib/libatm ===> lib/libbind ===> lib/libbz2 ===> lib/libc /bin/sh:Argument list too long *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:48: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 0B36B37B831; Mon, 13 May 2002 07:39:22 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4DEcUA62724; Mon, 13 May 2002 17:38:30 +0300 (EEST) (envelope-from ru) Date: Mon, 13 May 2002 17:38:30 +0300 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: alpha tinderbox failure Message-ID: <20020513143830.GB59752@sunbay.com> References: <200205131422.g4DEMUTM057549@beast.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="St7VIuEGZ6dlpu13" Content-Disposition: inline In-Reply-To: <200205131422.g4DEMUTM057549@beast.freebsd.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --St7VIuEGZ6dlpu13 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 13, 2002 at 07:22:30AM -0700, Dag-Erling Smorgrav wrote: > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > >>> stage 1: bootstrap tools > -------------------------------------------------------------- > >>> stage 2: cleaning up the object tree > -------------------------------------------------------------- > =3D=3D=3D> lib/libtacplus > =3D=3D=3D> lib/libutil > =3D=3D=3D> lib/libypclnt > =3D=3D=3D> lib/compat > =3D=3D=3D> lib/libalias > =3D=3D=3D> lib/libatm > =3D=3D=3D> lib/libbind > =3D=3D=3D> lib/libbz2 > =3D=3D=3D> lib/libc > /bin/sh:Argument list too long > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. >=20 Doh! My "make release" test for bsd.lib.mk changes wasn't sane -- "make buildworld" is ran with -DNOCLEAN here. I will fix it soon. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --St7VIuEGZ6dlpu13 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE838/mUkv4P6juNwoRAqJkAJ9eZFtMMajqiTgfbkywQyuCttNEOgCdHpnn TnNu6myMMp1u902ihEnIKLA= =7AdK -----END PGP SIGNATURE----- --St7VIuEGZ6dlpu13-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:52:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from nevada.tpi.pl (plug.eu.org [193.110.121.29]) by hub.freebsd.org (Postfix) with ESMTP id D79F337BB7A for ; Mon, 13 May 2002 07:49:28 -0700 (PDT) Received: from plug.eu.org (plug.eu.org [193.110.121.29]) by nevada.tpi.pl (Postfix) with ESMTP id 93F8B50D0F for ; Mon, 13 May 2002 16:49:23 +0200 (CEST) Date: Mon, 13 May 2002 16:49:23 +0200 (CEST) From: Andrzej Kwiatkowski X-Sender: kwiatek@plug.eu.org To: freebsd-current@freebsd.org Subject: VLock and 5.0 DP1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG When i try to compile Vlock from ports, i get: cc -O -pipe -DUSE_PAM -c vlock.c cc -O -pipe -DUSE_PAM -c signals.c cc -O -pipe -DUSE_PAM -c help.c cc -O -pipe -DUSE_PAM -c terminal.c cc -O -pipe -DUSE_PAM -c input.c input.c:64: security/pam_misc.h: No such file or directory input.c:67: `misc_conv' undeclared here (not in a function) input.c:67: initializer element is not constant input.c:67: (near initialization for `PAM_conversation.conv') Have got any idea how to solve this problem?? Greetings Andrzej Kwiatkowski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:54:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235]) by hub.freebsd.org (Postfix) with ESMTP id D041D37B447; Mon, 13 May 2002 07:51:16 -0700 (PDT) Received: from g8pbt.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Mon, 13 May 2002 16:50:07 +0200 Received: by G8PBT.blf01.telekom.de with Internet Mail Service (5.5.2653.19) id ; Mon, 13 May 2002 16:51:13 +0200 Message-Id: <5D90F2332B50D411BE8A00209412104C0385090D@QHS63> From: alan.edmonds@t-motion.net To: john@veidit.net, current@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: RE: Problem with Intel 2011b Date: Mon, 13 May 2002 16:47:05 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have used the non-B version with -current and an IBM thinkpad. What kind of laptop? dmesg output would be nice. Do any other cards work? Alan Edmonds -----Original Message----- From: John Angelmo [mailto:john@veidit.net] Sent: 13 May 2002 15:02 To: current Cc: freebsd-mobile Subject: Problem with Intel 2011b Hello I just got my hands on a Intel 2011b Wireless card, I'm running FreeBSD current (dated just before gcc 3.1). Now my problem is that I insert the card and well nothing happens, the system gets locked, when I remove the card I everything starts working once again, and it says it can't manage card ("null"), ("null") Any one got any idea? mvh /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:55:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by hub.freebsd.org (Postfix) with ESMTP id A44B637B64A for ; Mon, 13 May 2002 07:53:56 -0700 (PDT) Received: from misha (250-217.customer.cloud9.net [168.100.250.217]) by corbulon.video-collage.com (8.12.2/8.12.2) with ESMTP id g4DErq5D054395 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 13 May 2002 10:53:54 -0400 (EDT) (envelope-from mi+mx@aldan.algebra.com) X-Authentication-Warning: corbulon.video-collage.com: Host 250-217.customer.cloud9.net [168.100.250.217] claimed to be misha Content-Type: text/plain; charset="iso-8859-1" From: Mikhail Teterin Organization: Virtual Estates, Inc. To: Terry Lambert , Marcel Moolenaar Subject: Re: does the order of .a files matter? Date: Mon, 13 May 2002 10:52:36 -0400 X-Mailer: KMail [version 1.4] Cc: current@FreeBSD.ORG References: <200205101233.g4ACXctb041093@corbulon.video-collage.com> <20020512220007.GA21019@dhcp01.pn.xcllnt.net> <3CDF57EF.443F3BE7@mindspring.com> In-Reply-To: <3CDF57EF.443F3BE7@mindspring.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200205131052.36927.mi+mx@aldan.algebra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 13 May 2002 02:06 am, Terry Lambert wrote: = > If you think that providing bits on the link line in dependency = > order is a natural way of linking and the "proper" way of doing = > it, how do you explain our improper use of putting object files in = > lexical order in libraries and how do you resolve the contradiction = > that from a build point of view the lexical order is the proper = > way of building and we only get away with that because the = > linker doesn't require object files in archive libraries to be = > in dependency order (or we manually correct the situation by = > duplication)? = I explain the lexical ordering by way of the following commands when = exiting the Makefile in "vi" in command mode: = = !!ls *.c = JJJJJJJJJJJJJJJJJ[...] = ISRCS= = = 8-). This does not explain anything. Whatever the joke was, I did not get it. The question stands -- why can the object files be given to the linker in arbitrary order, but the the static libraries must be carefully ordered -- possibly even listed multiple times! There is nothing apparent in the .a format, that forces such behaviour. All of our Makefiles list objects in the alphabetical order -- why not sort them once with lorder/tsort and skip the lorder/tsort step from the library build (in bsd.lib.mk)? That would also speed up world-building... = Linking fewer object files into an executable makes the executable = smaller. Smaller executables are better than larger executables from a = putatively "smarter" linker (personally, I measure linker intelligence = as inversely proportional to the resulting executable size, relative = to the idealized executable size). Terry, NONE of this is relevant to the subject. Nobody is criticizing our linker for not putting UNNEEDED objects into the executables. The gaping hole in the linker, that is the subject of this thread, is the linker's inability to find NEEDED objects, which are right in front of its nose. = I had a big gripe, complete with examples involving famous names, = ready to go. But I will replace it with a much smaller response: = = "A craftsman must know his tools". And always seek to improve them. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 7:59:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 8F43237B407; Mon, 13 May 2002 07:58:56 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA14547; Tue, 14 May 2002 00:58:54 +1000 Date: Tue, 14 May 2002 01:01:05 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: GCC 3.1 generates bounds traps for bogous va_arg() use... In-Reply-To: <15004.1021298248@critter.freebsd.dk> Message-ID: <20020514003906.J369-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 13 May 2002, Poul-Henning Kamp wrote: > GCC 3.1 whines about these two instances of va_arg() and generates > code which calls "int 5" if they are executed. > > This workaround works for me, but I don't know if this is the > correct fix so I won't commit it. I just committed a correct fix (essentially s/u_short/int/). About the bug: i = va_arg(ap, u_short); has always given undefined behaviour. gcc now detects this at compile time. Whoever changed gcc to do this must feel as strongly as me about this error since they made it a fatal runtime error :-). 4.4BSD-Lite also attempted to detect this error and make it fatal except in the kernel. From the i386 stdarg.h: #ifdef KERNEL #define va_arg(ap, type) \ ((type *)(ap += sizeof(type)))[-1] #else #define va_arg(ap, type) \ ((type *)(ap += sizeof(type) < sizeof(int) ? \ (abort(), 0) : sizeof(type)))[-1] #endif but it is not really possible to do this without using a compiler builtin, and the above code was changed in FreeBSD after a PR or two about it. The most obvious bug in it is that va_arg() is specified to work on structs, and the size of a struct may be smaller than sizeof(int). I first noticed the 4.4BSDLite2 code when every single test prorgam in NIST-PCTS (NIST POSIX Conformance Test Suite) aborted in it. The NIST sources perpetrate va_arg(ap, char) and va_arg(ap, foo_t) (where foo_t _might_ be a sub-integer type) in a central place. Fixing bugs in the test suite is not permitted for attaining conformance, so FreeBSD is again 100% POSIX-non-conformant according to NIST-PCTS :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 8:20:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay.wineasy.se (smtp.wineasy.se [195.42.198.20]) by hub.freebsd.org (Postfix) with ESMTP id 28EDA37B407; Mon, 13 May 2002 08:19:53 -0700 (PDT) Received: from veidit.net ([213.88.130.20]) by relay.wineasy.se with ESMTP id g4DFEhn20756; Mon, 13 May 2002 17:14:43 +0200 Message-ID: <3CDFD860.90609@veidit.net> Date: Mon, 13 May 2002 17:14:40 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc2) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: alan.edmonds@t-motion.net Cc: current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Problem with Intel 2011b References: <5D90F2332B50D411BE8A00209412104C0385090D@QHS63> Content-Type: multipart/mixed; boundary="------------080105000503070204080304" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------080105000503070204080304 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit alan.edmonds@t-motion.net wrote: > I have used the non-B version with -current and an IBM thinkpad. > > What kind of laptop? dmesg output would be nice. > Do any other cards work? > > Alan Edmonds > > -----Original Message----- > From: John Angelmo [mailto:john@veidit.net] > Sent: 13 May 2002 15:02 > To: current > Cc: freebsd-mobile > Subject: Problem with Intel 2011b > > > Hello > > I just got my hands on a Intel 2011b Wireless card, I'm running FreeBSD > current (dated just before gcc 3.1). > Now my problem is that I insert the card and well nothing happens, the > system gets locked, when I remove the card I everything starts working > once again, and it says it can't manage card ("null"), ("null") > > Any one got any idea? > > mvh /John > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Well 2011b is a 32bit card (if I'm not mistaking) the 2011 card is the same as the symbol card but the 2011b card uses 3.3v instead of 5v So perhaps I need to use: device pccbb # cardbus (yenta) bridge device pccard device cardbus instead of: device card # pccard bus device pcic # PCMCIA bridge What else can I do? I use a C Series Lifebook from Fujitsu Siemens /John --------------080105000503070204080304 Content-Type: application/x-java-vm; name="dmesg" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="dmesg" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDIgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0 IChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAx OTkzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBUdWUgTWF5 ICA3IDIwOjI0OjA0IENFU1QgMjAwMgogICAgcm9vdEBBbW5lc2lhYzovdXNyL29iai91c3Iv c3JjL3N5cy9MaW5uClByZWxvYWRlZCBlbGYga2VybmVsICIvYm9vdC9rZXJuZWwva2VybmVs IiBhdCAweGMwNDdiMDAwLgpQcmVsb2FkZWQgZWxmIG1vZHVsZSAiL2Jvb3Qva2VybmVsL3Nw bGFzaF9ibXAua28iIGF0IDB4YzA0N2IwYTguClByZWxvYWRlZCBzcGxhc2hfaW1hZ2VfZGF0 YSAiL2Jvb3QvZGFydGhfbWF1bC5ibXAiIGF0IDB4YzA0N2IxNTguClByZWxvYWRlZCBlbGYg bW9kdWxlICIvYm9vdC9rZXJuZWwvYWdwLmtvIiBhdCAweGMwNDdiMWFjLgpQcmVsb2FkZWQg ZWxmIG1vZHVsZSAiL2Jvb3Qva2VybmVsL2FjcGkua28iIGF0IDB4YzA0N2IyNTQuClRpbWVj b3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6ClRpbWVjb3VudGVyICJUU0Mi ICBmcmVxdWVuY3kgODQ3MTc4MjQ4IEh6CkNQVTogUGVudGl1bSBJSUkvUGVudGl1bSBJSUkg WGVvbi9DZWxlcm9uICg4NDcuMTgtTUh6IDY4Ni1jbGFzcyBDUFUpCiAgT3JpZ2luID0gIkdl bnVpbmVJbnRlbCIgIElkID0gMHg2OGEgIFN0ZXBwaW5nID0gMTAKICBGZWF0dXJlcz0weDM4 M2Y5ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxTRVAsTVRSUixQR0Us TUNBLENNT1YsUEFULFBTRTM2LE1NWCxGWFNSLFNTRT4KcmVhbCBtZW1vcnkgID0gMjY2Nzk3 MDU2ICgyNjA1NDRLIGJ5dGVzKQphdmFpbCBtZW1vcnkgPSAyNTQ1NTQxMTIgKDI0ODU4OEsg Ynl0ZXMpClBlbnRpdW0gUHJvIE1UUlIgc3VwcG9ydCBlbmFibGVkClZFU0E6IHYzLjAsIDEw MjRrIG1lbW9yeSwgZmxhZ3M6MHgxLCBtb2RlIHRhYmxlOjB4YzAzNjllODAgKDEwMDAwNDAp ClZFU0E6IEludGVsODE1TShUTSkgR3JhcGhpY3MgQ2hpcCBBY2NlbGVyYXRlZCBWR0EgQklP UwpVc2luZyAkUElSIHRhYmxlLCA2IGVudHJpZXMgYXQgMHhjMDBmZGY2MApucHgwOiA8bWF0 aCBwcm9jZXNzb3I+IG9uIG1vdGhlcmJvYXJkCm5weDA6IElOVCAxNiBpbnRlcmZhY2UKYWNw aTA6IDxQVExURCAgCSBSU0RUICA+IG9uIG1vdGhlcmJvYXJkCmFjcGkwOiBwb3dlciBidXR0 b24gaXMgaGFuZGxlZCBhcyBhIGZpeGVkIGZlYXR1cmUgcHJvZ3JhbW1pbmcgbW9kZWwuClRp bWVjb3VudGVyICJBQ1BJLWZhc3QiICBmcmVxdWVuY3kgMzU3OTU0NSBIegphY3BpX3RpbWVy MDogPDI0LWJpdCB0aW1lciBhdCAzLjU3OTU0NU1Iej4gcG9ydCAweDEwMDgtMHgxMDBiIG9u IGFjcGkwCmFjcGlfY3B1MDogPENQVT4gb24gYWNwaTAKYWNwaV9wY2liMDogPEhvc3QtUENJ IGJyaWRnZT4gcG9ydCAweGNmOC0weGNmZiBvbiBhY3BpMApwY2kwOiA8UENJIGJ1cz4gb24g YWNwaV9wY2liMAphZ3AwOiA8SW50ZWwgODI4MTUgKGk4MTUgR01DSCkgU1ZHQSBjb250cm9s bGVyPiBtZW0gMHhmNDAwMDAwMC0weGY0MDdmZmZmLDB4ZjgwMDAwMDAtMHhmYmZmZmZmZiBp cnEgNSBhdCBkZXZpY2UgMi4wIG9uIHBjaTAKcGNpYjE6IDxQQ0ktUENJIGJyaWRnZT4gYXQg ZGV2aWNlIDMwLjAgb24gcGNpMApwY2kxOiA8UENJIGJ1cz4gb24gcGNpYjEKcGNpYzA6IDxP Mm1pY3JvIDY5MzMgUENJLUNhcmRidXMgQnJpZGdlPiBtZW0gMHhmNDMwMDAwMC0weGY0MzAw ZmZmIGlycSA1IGF0IGRldmljZSAyLjAgb24gcGNpMQpwY2ljMDogV2FybmluZzogTzJtaWNy byBPWjY4eHggY2hpcHMgbWF5IG5vdCB3b3JrCnBjY2FyZDA6IDxQQyBDYXJkIGJ1cyAoY2xh c3NpYyk+IG9uIHBjaWMwCnBjaWMxOiA8TzJtaWNybyA2OTMzIFBDSS1DYXJkYnVzIEJyaWRn ZT4gbWVtIDB4ZjQzMDEwMDAtMHhmNDMwMWZmZiBpcnEgOSBhdCBkZXZpY2UgMi4xIG9uIHBj aTEKcGNpYzE6IFdhcm5pbmc6IE8ybWljcm8gT1o2OHh4IGNoaXBzIG1heSBub3Qgd29yawpw Y2NhcmQxOiA8UEMgQ2FyZCBidXMgKGNsYXNzaWMpPiBvbiBwY2ljMQpybDA6IDxSZWFsVGVr IDgxMzkgMTAvMTAwQmFzZVRYPiBwb3J0IDB4ZWUwMC0weGVlZmYgbWVtIDB4ZjQzMDIwMDAt MHhmNDMwMjBmZiBpcnEgNSBhdCBkZXZpY2UgNi4wIG9uIHBjaTEKcmwwOiBSZWFsdGVrIDgx MzlCIGRldGVjdGVkLiBXYXJuaW5nLCB0aGlzIG1heSBiZSB1bnN0YWJsZSBpbiBhdXRvc2Vs ZWN0IG1vZGUKcmwwOiBFdGhlcm5ldCBhZGRyZXNzOiAwMDo5MDo5NjoxOTo2YjpiMgptaWli dXMwOiA8TUlJIGJ1cz4gb24gcmwwCnJscGh5MDogPFJlYWxUZWsgaW50ZXJuYWwgbWVkaWEg aW50ZXJmYWNlPiBvbiBtaWlidXMwCnJscGh5MDogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAx MDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIGF1dG8KaXNhYjA6IDxQQ0ktSVNBIGJyaWRnZT4g YXQgZGV2aWNlIDMxLjAgb24gcGNpMAppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjAKYXRhcGNp MDogPEludGVsIElDSDIgQVRBMTAwIGNvbnRyb2xsZXI+IHBvcnQgMHgxODAwLTB4MTgwZiBh dCBkZXZpY2UgMzEuMSBvbiBwY2kwCmF0YTA6IGF0IDB4MWYwIGlycSAxNCBvbiBhdGFwY2kw CmF0YTE6IGF0IDB4MTcwIGlycSAxNSBvbiBhdGFwY2kwCnVoY2kwOiA8SW50ZWwgODI4MDFC QS9CQU0gKElDSDIpIFVTQiBjb250cm9sbGVyIFVTQi1BPiBwb3J0IDB4MTgyMC0weDE4M2Yg aXJxIDcgYXQgZGV2aWNlIDMxLjIgb24gcGNpMAp1c2IwOiA8SW50ZWwgODI4MDFCQS9CQU0g KElDSDIpIFVTQiBjb250cm9sbGVyIFVTQi1BPiBvbiB1aGNpMAp1c2IwOiBVU0IgcmV2aXNp b24gMS4wCnVodWIwOiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAw LzEuMDAsIGFkZHIgMQp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBv d2VyZWQKaWNoc21iMDogPEludGVsIDgyODAxQkEgKElDSDIpIFNNQnVzIGNvbnRyb2xsZXI+ IHBvcnQgMHgxODEwLTB4MTgxZiBpcnEgOSBhdCBkZXZpY2UgMzEuMyBvbiBwY2kwCnNtYnVz MDogPFN5c3RlbSBNYW5hZ2VtZW50IEJ1cz4gb24gaWNoc21iMApzbWIwOiA8U01CdXMgZ2Vu ZXJpYyBJL08+IG9uIHNtYnVzMAp1aGNpMTogPEludGVsIDgyODAxQkEvQkFNIChJQ0gyKSBV U0IgY29udHJvbGxlciBVU0ItQj4gcG9ydCAweDE4NDAtMHgxODVmIGlycSAxMCBhdCBkZXZp Y2UgMzEuNCBvbiBwY2kwCnVzYjE6IDxJbnRlbCA4MjgwMUJBL0JBTSAoSUNIMikgVVNCIGNv bnRyb2xsZXIgVVNCLUI+IG9uIHVoY2kxCnVzYjE6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjE6 IEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAx CnVodWIxOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1bXMwOiBM b2dpdGVjaCBVU0ItUFMvMiBNb3VzZSwgcmV2IDEuMDAvMS4yMCwgYWRkciAyLCBpY2xhc3Mg My8xCnVtczA6IDMgYnV0dG9ucyBhbmQgWiBkaXIuCnBjbTA6IDxJbnRlbCA4MjgwMUJBIChJ Q0gyKT4gcG9ydCAweGZmODAtMHhmZmJmLDB4ZmMwMC0weGZjZmYgaXJxIDkgYXQgZGV2aWNl IDMxLjUgb24gcGNpMApwY20wOiBtZWFzdXJlZCBhYzk3IGxpbmsgcmF0ZSBhdCAyOTQ3MyBI egphY3BpX2J1dHRvbjA6IDxQb3dlciBCdXR0b24+IG9uIGFjcGkwCmF0a2JkYzA6IDxLZXli b2FyZCBjb250cm9sbGVyIChpODA0Mik+IHBvcnQgMHg2NCwweDYwIGlycSAxIG9uIGFjcGkw CmF0a2JkMDogPEFUIEtleWJvYXJkPiBmbGFncyAweDEgaXJxIDEgb24gYXRrYmRjMAprYmQw IGF0IGF0a2JkMApwc20wOiA8UFMvMiBNb3VzZT4gaXJxIDEyIG9uIGF0a2JkYzAKcHNtMDog bW9kZWwgR2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZpY2UgSUQgMAphY3BpX2VjMDogPGVtYmVk ZGVkIGNvbnRyb2xsZXI+IHBvcnQgMHg2NiwweDYyIG9uIGFjcGkwCmFjcGlfbGlkMDogPENv bnRyb2wgTWV0aG9kIExpZCBTd2l0Y2g+IG9uIGFjcGkwCmFjcGlfYWNhZDA6IDxBQyBhZGFw dGVyPiBvbiBhY3BpMAphY3BpX2NtYmF0MDogPENvbnRyb2wgbWV0aG9kIEJhdHRlcnk+IG9u IGFjcGkwCnNpbzAgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBvbiBhY3BpMApzaW8wOiB0eXBl IDE2NTUwQQpmZGMwOiA8ZW5oYW5jZWQgZmxvcHB5IGNvbnRyb2xsZXIgKGk4MjA3NywgTkU3 MjA2NSBvciBjbG9uZSk+IHBvcnQgMHgzZjcsMHgzZjAtMHgzZjUgaXJxIDYgZHJxIDIgb24g YWNwaTAKZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZApmZDA6IDwxNDQw LUtCIDMuNSIgZHJpdmU+IG9uIGZkYzAgZHJpdmUgMApvcm0wOiA8T3B0aW9uIFJPTT4gYXQg aW9tZW0gMHhjMDAwMC0weGNiZmZmIG9uIGlzYTAKcG10aW1lcjAgb24gaXNhMApwcGMwOiBw YXJhbGxlbCBwb3J0IG5vdCBmb3VuZC4Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdz IDB4MTAwIG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4 MzAwPgpzaW8xIGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMApzaW8xOiB0eXBl IDE2NTUwQQp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlv bWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwClRpbWVjb3VudGVycyB0aWNrIGV2ZXJ5IDEw LjAwMCBtc2VjCmFjcGlfY3B1OiBDUFUgdGhyb3R0bGluZyBlbmFibGVkLCA4IHN0ZXBzIGZy b20gMTAwJSB0byAxMi41JQogICAgQUNQSS0xMzA1OiAqKiogRXJyb3I6IE1ldGhvZCBleGVj dXRpb24gZmFpbGVkLCBBRV9BTUxfQlVGRkVSX0xJTUlUCiAgICBBQ1BJLTEzMDU6ICoqKiBF cnJvcjogTWV0aG9kIGV4ZWN1dGlvbiBmYWlsZWQsIEFFX0FNTF9CVUZGRVJfTElNSVQKICAg IEFDUEktMTMwNTogKioqIEVycm9yOiBNZXRob2QgZXhlY3V0aW9uIGZhaWxlZCwgQUVfQU1M X0JVRkZFUl9MSU1JVAphZDA6IDk1OTBNQiA8VE9TSElCQSBNSzEwMTZHQVA+IFsxOTQ4NS8x Ni82M10gYXQgYXRhMC1tYXN0ZXIgVURNQTY2CmFjZDA6IENEUk9NIDxRU0kgQ0QtUk9NIFND Ui0yNDI+IGF0IGF0YTEtbWFzdGVyIFBJTzQKTW91bnRpbmcgcm9vdCBmcm9tIHVmczovZGV2 L2FkMHMyYQpXQVJOSU5HOiAvIHdhcyBub3QgcHJvcGVybHkgZGlzbW91bnRlZAovOiBsb3N0 IGJsb2NrcyA2OCBmaWxlcyAxMwovOiByZWxvYWQgcGVuZGluZyBlcnJvcjogYmxvY2tzIDY4 IGZpbGVzIDEzCg== --------------080105000503070204080304-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 8:25:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 37E6B37B401; Mon, 13 May 2002 08:24:59 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4DFOmP68066; Mon, 13 May 2002 18:24:48 +0300 (EEST) (envelope-from ru) Date: Mon, 13 May 2002 18:24:48 +0300 From: Ruslan Ermilov To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: alpha tinderbox failure Message-ID: <20020513152448.GC59752@sunbay.com> References: <200205131422.g4DEMUTM057549@beast.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qtZFehHsKgwS5rPz" Content-Disposition: inline In-Reply-To: <200205131422.g4DEMUTM057549@beast.freebsd.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Fixed in bsd.lib.mk,v 1.125. On Mon, May 13, 2002 at 07:22:30AM -0700, Dag-Erling Smorgrav wrote: > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > >>> stage 1: bootstrap tools > -------------------------------------------------------------- > >>> stage 2: cleaning up the object tree > -------------------------------------------------------------- > =3D=3D=3D> lib/libtacplus > =3D=3D=3D> lib/libutil > =3D=3D=3D> lib/libypclnt > =3D=3D=3D> lib/compat > =3D=3D=3D> lib/libalias > =3D=3D=3D> lib/libatm > =3D=3D=3D> lib/libbind > =3D=3D=3D> lib/libbz2 > =3D=3D=3D> lib/libc > /bin/sh:Argument list too long > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib/libc. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/lib. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. > *** Error code 1 >=20 > Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE839rAUkv4P6juNwoRApguAJ47s8euW+pDOHv3qsi3stP+BtGVBACcD//S 6K/ListNbHJ2hckpxE4dbV4= =ZTJP -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 8:36:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail1.telekom.de (mail1.telekom.de [62.225.183.235]) by hub.freebsd.org (Postfix) with ESMTP id B5FC737B400; Mon, 13 May 2002 08:36:13 -0700 (PDT) Received: from g8pbt.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Mon, 13 May 2002 17:35:05 +0200 Received: by G8PBT.blf01.telekom.de with Internet Mail Service (5.5.2653.19) id ; Mon, 13 May 2002 17:36:12 +0200 Message-Id: <5D90F2332B50D411BE8A00209412104C0385090F@QHS63> From: alan.edmonds@t-motion.net To: john@veidit.net, alan.edmonds@t-motion.net Cc: current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: RE: Problem with Intel 2011b Date: Mon, 13 May 2002 17:32:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I haven't tried the NEWCARD stuff (it panics my hp 510 - 16bit bridge chips) so I can't comment on that. Did you try booting with the card installed? If you boot verbose (boot -v) should see it dump the pci id contents. Also check if /etc/defaults/pccard.conf contains an entry for the card. The version of -current I have (maybe a few days old) has no entry explicitly for a 2011B. It might use the same entry as a 2011, but might have a different id string. I've exceeded my knowledge at this point, so I'll stop speculating. Over to you, Warner :-) -----Original Message----- From: John Angelmo [mailto:john@veidit.net] Sent: 13 May 2002 16:15 To: alan.edmonds@t-motion.net Cc: current@FreeBSD.ORG; freebsd-mobile@FreeBSD.ORG Subject: Re: Problem with Intel 2011b alan.edmonds@t-motion.net wrote: > I have used the non-B version with -current and an IBM thinkpad. > > What kind of laptop? dmesg output would be nice. > Do any other cards work? > > Alan Edmonds > > -----Original Message----- > From: John Angelmo [mailto:john@veidit.net] > Sent: 13 May 2002 15:02 > To: current > Cc: freebsd-mobile > Subject: Problem with Intel 2011b > > > Hello > > I just got my hands on a Intel 2011b Wireless card, I'm running FreeBSD > current (dated just before gcc 3.1). > Now my problem is that I insert the card and well nothing happens, the > system gets locked, when I remove the card I everything starts working > once again, and it says it can't manage card ("null"), ("null") > > Any one got any idea? > > mvh /John > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Well 2011b is a 32bit card (if I'm not mistaking) the 2011 card is the same as the symbol card but the 2011b card uses 3.3v instead of 5v So perhaps I need to use: device pccbb # cardbus (yenta) bridge device pccard device cardbus instead of: device card # pccard bus device pcic # PCMCIA bridge What else can I do? I use a C Series Lifebook from Fujitsu Siemens /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 13 9:34:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from math.teaser.net (math.teaser.net [213.91.2.4]) by hub.freebsd.org (Postfix) with ESMTP id A6D1A37B400; Mon, 13 May 2002 09:33:59 -0700 (PDT) Received: from notbsdems.nantes.kisoft-services.com (chantilly.kisoft-services.com [193.56.60.242]) by math.teaser.net (Postfix) with ESMTP id 4FD1E6C815; Mon, 13 May 2002 18:33:57 +0200 (CEST) Received: by notbsdems.nantes.kisoft-services.com (Postfix, from userid 1001) id 3A07B5A535; Mon, 13 May 2002 18:33:57 +0200 (CEST) To: John Angelmo Cc: alan.edmonds@t-motion.net, current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Problem with Intel 2011b References: <5D90F2332B50D411BE8A00209412104C0385090D@QHS63> <3CDFD860.90609@veidit.net> From: Eric Masson In-Reply-To: <3CDFD860.90609@veidit.net> (John Angelmo's message of "Mon, 13 May 2002 17:14:40 +0200") Message-ID: <86elgg58w7.fsf@notbsdems.nantes.kisoft-services.com> X-Operating-System: FreeBSD 4.6-PRERELEASE i386 Date: Mon, 13 May 2002 18:33:56 +0200 Lines: 175 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Common Lisp, i386--freebsd) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "John" == John Angelmo writes: John> Well 2011b is a 32bit card (if I'm not mistaking) Nope, it's only a 3,3V 16 bits card. If you're using -stable, the following is needed : > cat /etc/pccard.conf # Intel PRO/Wireless 2011B LAN PC Card card "Intel" "PRO/Wireless LAN PC Card" config auto "wi" ? 0x10000 insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop The 2011 nor the 2011b work on my box (Thinkpad 390) whilst the 2011 works on a Satellite Pro 430 CDS (no 3,3 V slot for the 2011b). dmesg on the Satellite : Copyright (c) 1992-2002 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 4.5-STABLE #0: Tue Apr 30 12:29:58 CEST 2002 emss@srvbsdchassv.chantilly.kisoft-services.com:/usr/src/sys/compile/TSP430CDS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (120.00-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 50528256 (49344K bytes) avail memory = 46747648 (45652K bytes) pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "kernel" at 0xc0278000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc027809c. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface isa0: on motherboard orm0: Subscriber Online
If you have trouble seeing this movie click here.
SubscriberOnline
An eMediaPartners, Inc. Services Company
Click Here
for the CD Quality
World Music Webcast


Check Out Our
DSL Special Offer

Copyright (C) 2! 001-2002 by eMediaPartners, Inc. All rights reserved.

To view this animated presentation enable HTML, ActiveX/Scripts and Flash/Shockwave plug-ins
in your email security or just click on this URL to view it in your browser:
http://webworldmall.com/wmr/flash/world.html
For more information visit us at Subscriber Online.  Download Fla! sh


To unsubscribe return this email with UNSUBSCRIBE in the subject field.


-----=_NEXT_ec4e25f0c5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 13: 9:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id E820437B409 for ; Fri, 17 May 2002 13:09:46 -0700 (PDT) Received: from pool0392.cvx22-bradley.dialup.earthlink.net ([209.179.199.137] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 178o2g-0005cs-00; Fri, 17 May 2002 13:09:35 -0700 Message-ID: <3CE56361.67EB4549@mindspring.com> Date: Fri, 17 May 2002 13:09:05 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Cc: freebsd-current Subject: Re: df References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian wrote: > On 05/17/02 10:27, Riccardo Torrini wrote: > > I manually mount nfs fs after a reboot (current -> stable) and > > if I do a "df" I got two different output. First time it get > > garbled, all other times it is aligned. I'm alone? > > I looked at the df code because I was intensely curious how this could > happen. It obtains the list of mounts using a NOWAIT flag, and NFS mount > info may not be available immediately so it doesn't get included in the > field width calculations. Then later it re-gets the list of mounts using a > WAIT flag (unless you used -n on the command line) so this time it has the > info from NFS filesystems, but it doesn't recalculate the field widths. The > following patch should fix it without breaking other behaviors, I belive. I guess the real question is why the NOWAIT flag results in the NFS FS's not being included, since the purpose of NOWAIT is to keep it from hanging indefinitely, not to keep high latency FS's out of consideration. Also, one would expect that the FS's that failed "NOWAIT" would have their details left out, and be marked as "could cause hang if examined". > - if (vfslist != NULL) { > + if (!nflag) { Uh, think this wants to be: > + if (!nflag || vfslist != NULL) { The reason is that an explicit list of FS's on the command line still means "look these up, come hell or high water, and hang, if you have to". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 16:40:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 8567037B400 for ; Fri, 17 May 2002 16:40:30 -0700 (PDT) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.12.3/8.12.3) with ESMTP id g4HNeT6r012165; Fri, 17 May 2002 17:40:30 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Fri, 17 May 2002 17:40:30 -0600 Subject: Re: df From: Ian To: Terry Lambert Cc: freebsd-current Message-ID: In-Reply-To: <3CE56361.67EB4549@mindspring.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 05/17/02 14:09, Terry Lambert wrote: > Ian wrote: >> On 05/17/02 10:27, Riccardo Torrini wrote: >>> I manually mount nfs fs after a reboot (current -> stable) and >>> if I do a "df" I got two different output. First time it get >>> garbled, all other times it is aligned. I'm alone? >> >> I looked at the df code because I was intensely curious how this could >> happen. It obtains the list of mounts using a NOWAIT flag, and NFS mount >> info may not be available immediately so it doesn't get included in the >> field width calculations. Then later it re-gets the list of mounts using a >> WAIT flag (unless you used -n on the command line) so this time it has the >> info from NFS filesystems, but it doesn't recalculate the field widths. The >> following patch should fix it without breaking other behaviors, I belive. > > I guess the real question is why the NOWAIT flag results in the > NFS FS's not being included, since the purpose of NOWAIT is to > keep it from hanging indefinitely, not to keep high latency FS's > out of consideration. I leave troublesome questions like that to people who like mucking around in kernel and filesystem internals. I was just looking for something that could cause apparently-stateful behavior across runs of the program and decided I'd found a candidate cause. > Also, one would expect that the FS's that failed "NOWAIT" would > have their details left out, and be marked as "could cause hang > if examined". > >> - if (vfslist != NULL) { >> + if (!nflag) { > > > Uh, think this wants to be: > >> + if (!nflag || vfslist != NULL) { > > The reason is that an explicit list of FS's on the command line > still means "look these up, come hell or high water, and hang, if > you have to". vfslist != NULL means the stats array could have had some entries filtered out of it. Only if nflag is false could the array have grown to have new entries. Still, if the array got filtered, then potentially some fields could be displayed narrower than the first-cut calcs set up, so your suggestion is more-correct. (Naming filesystems on the command line leads to a completely different path thru the code where this change doesn't come into play.) Actually, I now think a more-correct fix would be to have no if statement at all, and just always recalculate the field widths after calling the routine to re-get the stats. The if statement strikes me as a troublesome micro-optimization that smears info about the internal state of the re-get routine's behavior to another outside routine. All to save a couple microseconds. (Consider that this whole problem happened because already the code was assuming the re-get routine wouldn't have changed the stats array if vfslist was NULL, which incorrectly reflects the behavior of the re-get routine.) If it's really important to save these cycles, the recalc of the field widths should move closer to the point at which the raw data is (re-)obtained. But then you start asking yourself questions like "why does it bother to get the list with a NOWAIT then later get the list again with a WAIT instead of just getting it once using the method 'nflag' implies?" and before you know it you're rewriting half the code. :-) -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 19:13: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 54CCC37B421; Fri, 17 May 2002 19:12:37 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id BA4991036AD; Fri, 17 May 2002 23:12:31 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 12CDB103694; Fri, 17 May 2002 23:12:31 -0300 (ADT) Date: Fri, 17 May 2002 23:12:31 -0300 (ADT) From: "Marc G. Fournier" To: Andrew Gallatin Cc: freebsd-current@freebsd.org, Subject: Re: How to dump a 4gig system on panic ? In-Reply-To: <15589.13737.302689.294546@grasshopper.cs.duke.edu> Message-ID: <20020517210219.P41731-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Okay, seem to be about halfway there ... client kldload's no problem, server runs ... do a ctl-alt-esc to get into DDB and type panic, and it gives a message that its looking for the server and it finds it on the right IP ... then it prints out a '1023' and finishes the panic ... On the 'dump server', a vmcore gets created, but its zero length ... thoughts? On Fri, 17 May 2002, Andrew Gallatin wrote: > > Marc G. Fournier writes: > > > > Well, downloaded the files (a .tar.gz would be nice? *grin*) and the > > client built perfectly, and kldload worked fine ... is there some way > > someone can suggest of 'simulating a crash'? Some way to test to make > > sure that it is working as expected? I have a 4.6-PRE machine on my desk > > that I'd like to test with before I try it on "the real thing", if at all > > possible? > > break into ddb & do: > ddb > call dumpsys() > > Unless you're running a savecore which supports partial dumps, you > need to disable partial dumps (sysctl net.net_dump.partial=0). > > And remember, you'll be spewing the contents of your ram (possibly > passwords, etc) across the network in clear text. > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 20:41: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 829B537B401; Fri, 17 May 2002 20:40:54 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g4I3eqC05425; Fri, 17 May 2002 21:40:53 -0600 (MDT) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g4I3emN06015; Fri, 17 May 2002 21:40:49 -0600 (MDT) (envelope-from imp@village.org) Date: Fri, 17 May 2002 21:40:22 -0600 (MDT) Message-Id: <20020517.214022.116606158.imp@village.org> To: e-masson@kisoft-services.com Cc: john@veidit.net, alan.edmonds@t-motion.net, current@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Problem with Intel 2011b From: "M. Warner Losh" In-Reply-To: <86ptzyk0dm.fsf@notbsdems.nantes.kisoft-services.com> References: <3CDFD860.90609@veidit.net> <200205131755.g4DHt8r96292@harmony.village.org> <86ptzyk0dm.fsf@notbsdems.nantes.kisoft-services.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <86ptzyk0dm.fsf@notbsdems.nantes.kisoft-services.com> Eric Masson writes: : >>>>> "Warner" == Warner Losh writes: : : Warner> Hmmmm, I've found that the Intel PRO/Wireless are 5.0V devices. : Warner> Maybe this is a different card than what I'm used to dealing : Warner> with. : : From the reseller, this is the main difference beetween 2011 & 2011b : (chipset difference too, but no specs available atm) : : Warner> Looks like i82365A/B do not have 3.3V support at all. I can't : Warner> find the data sheets for them, and the people that do have : Warner> access tell me that this is correct. : : Seems to, the 2011b can't physically plug into the slot on the : Satellite. That's because it has a low power key on it. You can file things down and often get away with running on some older laptops. However, not this one. : Warner> I'm not sure why your thinkpad isn't working. Maybe it is an : Warner> issue related to the COR reset proceedure that we're not doing : Warner> anymore. : : Is there anything I can do to confirm/infirm this fact ? (cvs revision : to extract ?) Not easily. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 22:40: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D8CC337B408; Fri, 17 May 2002 22:39:51 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4I5dot36191; Fri, 17 May 2002 23:39:50 -0600 (MDT) (envelope-from ken) Date: Fri, 17 May 2002 23:39:50 -0600 From: "Kenneth D. Merry" To: current@FreeBSD.org Cc: net@FreeBSD.org Subject: new zero copy sockets patches available Message-ID: <20020517233950.A36169@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have released a new set of zero copy sockets patches, against -current from today (May 17th, 2002). The main change is to deal with the vfs_ioopt changes that Alan Cox made in kern_subr.c. (They conflicted a bit with the zero copy receive code.) The patches and the FAQ are available here: http://people.freebsd.org/~ken/zero_copy/ Comments, questions and reviews are all welcome! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 23: 3: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id E877937B403; Fri, 17 May 2002 23:02:55 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id B9EA6AE1FB; Fri, 17 May 2002 23:02:55 -0700 (PDT) Date: Fri, 17 May 2002 23:02:55 -0700 From: Alfred Perlstein To: "Kenneth D. Merry" Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available Message-ID: <20020518060255.GN20683@elvis.mu.org> References: <20020517233950.A36169@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020517233950.A36169@panzer.kdm.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kenneth D. Merry [020517 22:40] wrote: > > I have released a new set of zero copy sockets patches, against -current > from today (May 17th, 2002). > > The main change is to deal with the vfs_ioopt changes that Alan Cox made in > kern_subr.c. (They conflicted a bit with the zero copy receive code.) > > The patches and the FAQ are available here: > > http://people.freebsd.org/~ken/zero_copy/ > > Comments, questions and reviews are all welcome! jumbo_vm_init() has a bunch of bugs first it doesn't work right if called concurrently. you need to protect the initialization of jumbo_vm_object otherwise bad things can happen. my suggestion is to store the results of vm_object_allocate into a temporary, grab the mutex and then check to see if jumbo_vm_object has been initialized again if it has then free the object, otherwise store the allocated object into the global and continue. you may not call malloc(9) with M_WAITOK while holding a mutex. --- entry = jumbo_kmap_inuse.slh_first; I'm sure that should use a list macro. --- That's all I see off the bat. :) Looks cool though. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 23:30:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtp.kolej.mff.cuni.cz (smtp.kolej.mff.cuni.cz [195.113.25.225]) by hub.freebsd.org (Postfix) with ESMTP id 8DB9237B40D for ; Fri, 17 May 2002 23:30:06 -0700 (PDT) X-Envelope-From: kacem0am@artax.karlin.mff.cuni.cz Received: from amutor.kolej.mff.cuni.cz (amutor.kolej.mff.cuni.cz [195.113.26.152]) by smtp.kolej.mff.cuni.cz (8.11.6/8.11.6) with ESMTP id g4I6U1K35067 for ; Sat, 18 May 2002 08:30:02 +0200 (CEST) (envelope-from kacem0am@artax.karlin.mff.cuni.cz) Received: from wizard by amutor.kolej.mff.cuni.cz with local (Exim 3.35 #1 (FreeBSD)) id 178xjD-0001Dn-00 for ; Sat, 18 May 2002 08:30:07 +0200 Date: Sat, 18 May 2002 08:30:07 +0200 From: Martin Kacerovsky To: current@freebsd.org Subject: kernel panic in 5.0-20020302-PREVIEW with drm-kmod Message-ID: <20020518083007.A4658@amutor.kolej.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a problem with DRM, I have ATI Xpert2000 AGP card, in 4.5-RELEASE I used r128.ko , and all was fine, in current my kernel hangs up saying: malloc type lacks magic number. I have compiled the kernel with 'device agp' so what can be wrong? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 17 23:31: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 46D8F37B400; Fri, 17 May 2002 23:30:49 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4I6UkX36632; Sat, 18 May 2002 00:30:46 -0600 (MDT) (envelope-from ken) Date: Sat, 18 May 2002 00:30:46 -0600 From: "Kenneth D. Merry" To: Alfred Perlstein Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available Message-ID: <20020518003046.A36510@panzer.kdm.org> References: <20020517233950.A36169@panzer.kdm.org> <20020518060255.GN20683@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020518060255.GN20683@elvis.mu.org>; from bright@mu.org on Fri, May 17, 2002 at 11:02:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, May 17, 2002 at 23:02:55 -0700, Alfred Perlstein wrote: > * Kenneth D. Merry [020517 22:40] wrote: > > > > I have released a new set of zero copy sockets patches, against -current > > from today (May 17th, 2002). > > > > The main change is to deal with the vfs_ioopt changes that Alan Cox made in > > kern_subr.c. (They conflicted a bit with the zero copy receive code.) > > > > The patches and the FAQ are available here: > > > > http://people.freebsd.org/~ken/zero_copy/ > > > > Comments, questions and reviews are all welcome! > > jumbo_vm_init() has a bunch of bugs > > first it doesn't work right if called concurrently. > you need to protect the initialization of jumbo_vm_object otherwise > bad things can happen. my suggestion is to store the results of > vm_object_allocate into a temporary, grab the mutex and then check > to see if jumbo_vm_object has been initialized again if it has then > free the object, otherwise store the allocated object into the > global and continue. The problem here is that the mutex needs to be initialized before I can acquire it, and there's going to be a race between checking to see whether it has been initialized and actually initializing it. e.g.: if (!mtx_initialized(&jumbo_mutex)) mtx_init(&jumbo_mutex, "jumbo mutex", NULL, MTX_DEF); mtx_lock(&jumbo_mutex); if (jumbo_vm_object != NULL) { mtx_unlock(&jumbo_mutex); return (1); } /* allocate our object */ jumbo_vm_object = vm_object_allocate(OBJT_DEFAULT, JUMBO_MAX_PAGES); The above would work, I think, if it weren't for the race in the mutex initialization, and assuming I can allocate a vm object while holding the jumbo mutex. Suggestions? > you may not call malloc(9) with M_WAITOK while holding a mutex. Ahh, okay. > entry = jumbo_kmap_inuse.slh_first; > > I'm sure that should use a list macro. Yes, SLIST_FIRST(), thanks. > That's all I see off the bat. :) Looks cool though. Cool, thanks for the feedback! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 1:41:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id C92E737B408; Sat, 18 May 2002 01:41:24 -0700 (PDT) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 178zmD-0003sK-00; Sat, 18 May 2002 12:41:21 +0400 To: FreeBSD-gnats-submit@freebsd.org Subject: gdb do not work with gcc-3.1 From: Vladimir B.Grebenschikov Reply-To: Vladimir B.Grebenschikov Cc: current@freebsd.org X-send-pr-version: 3.113 X-GNATS-Notify: Message-Id: Date: Sat, 18 May 2002 12:41:21 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: Vladimir B. Grebenschikov >Organization: SWsoft >Confidential: no >Synopsis: gdb do not work with gcc-3.1 >Severity: serious >Priority: high >Category: bin >Class: sw-bug >Release: FreeBSD 5.0-CURRENT i386 >Environment: System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri May 17 13:42:09 MSD 2002 root@vbook.express.ru:/usr/obj/usr/local/src/sys/VBOOK i386 make world done at May 16. >Description: GDB do not work with strange diagnostic: Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. >How-To-Repeat: vbook:/home/vova/src 164_> cat > aa.c #include main() { printf("hello world\n"); } ^D vbook:/home/vova/src 165_> gcc -g aa.c vbook:/home/vova/src 166_> gdb a.out GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader. (gdb) b main No symbol table is loaded. Use the "file" command. (gdb) r Starting program: /usr/local/home/vova/src/a.out hello world (no debugging symbols found)...(no debugging symbols found)... Program exited with code 015. (gdb) q vbook:/home/vova/src 167_> gdb --version GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". vbook:/home/vova/src 168_> gcc --version gcc (GCC) 3.1 [FreeBSD] 20020509 (prerelease) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >Fix: Get GCC before 3.1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 2: 0:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 0264037B405; Sat, 18 May 2002 02:00:33 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id D5EDEAE1D1; Sat, 18 May 2002 02:00:32 -0700 (PDT) Date: Sat, 18 May 2002 02:00:32 -0700 From: Alfred Perlstein To: "Kenneth D. Merry" Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available Message-ID: <20020518090032.GO20683@elvis.mu.org> References: <20020517233950.A36169@panzer.kdm.org> <20020518060255.GN20683@elvis.mu.org> <20020518003046.A36510@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020518003046.A36510@panzer.kdm.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kenneth D. Merry [020517 23:31] wrote: > > The problem here is that the mutex needs to be initialized before I can > acquire it, and there's going to be a race between checking to see > whether it has been initialized and actually initializing it. > ... > Suggestions? *slaps forhead* Probably a SYSINIT? > Cool, thanks for the feedback! np, this is promising work! -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 2: 9:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from goose.prod.itd.earthlink.net (goose.mail.pas.earthlink.net [207.217.120.18]) by hub.freebsd.org (Postfix) with ESMTP id 4F1C637B405; Sat, 18 May 2002 02:09:33 -0700 (PDT) Received: from pool0026.cvx40-bradley.dialup.earthlink.net ([216.244.42.26] helo=mindspring.com) by goose.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 1790DP-0002Gf-00; Sat, 18 May 2002 02:09:27 -0700 Message-ID: <3CE61A25.61C789FA@mindspring.com> Date: Sat, 18 May 2002 02:08:53 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: "Kenneth D. Merry" , current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available References: <20020517233950.A36169@panzer.kdm.org> <20020518060255.GN20683@elvis.mu.org> <20020518003046.A36510@panzer.kdm.org> <20020518090032.GO20683@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Kenneth D. Merry [020517 23:31] wrote: > > The problem here is that the mutex needs to be initialized before I can > > acquire it, and there's going to be a race between checking to see > > whether it has been initialized and actually initializing it. > > > ... > > Suggestions? > > *slaps forhead* > > Probably a SYSINIT? God, it's annoying that a statically declared mutex is not defacto initialized. Yeah, I understand the "witness" crap (if it's there); that doesn't make it any less annoying. Actually, a linker set (not a SYSINIT) could fix that... you would still need one sysinit to do the linkage of the statically declared structures, but it's at least doable. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 6: 4:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by hub.freebsd.org (Postfix) with ESMTP id 8298137B408 for ; Sat, 18 May 2002 06:03:53 -0700 (PDT) Received: (qmail 23564 invoked from network); 18 May 2002 13:03:52 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 May 2002 13:03:52 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g4ID3oF82147; Sat, 18 May 2002 09:03:50 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020518003046.A36510@panzer.kdm.org> Date: Sat, 18 May 2002 09:03:38 -0400 (EDT) From: John Baldwin To: "Kenneth D. Merry" Subject: Re: new zero copy sockets patches available Cc: net@FreeBSD.org, current@FreeBSD.org, Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-May-2002 Kenneth D. Merry wrote: > On Fri, May 17, 2002 at 23:02:55 -0700, Alfred Perlstein wrote: >> * Kenneth D. Merry [020517 22:40] wrote: >> > >> > I have released a new set of zero copy sockets patches, against -current >> > from today (May 17th, 2002). >> > >> > The main change is to deal with the vfs_ioopt changes that Alan Cox made >> > in >> > kern_subr.c. (They conflicted a bit with the zero copy receive code.) >> > >> > The patches and the FAQ are available here: >> > >> > http://people.freebsd.org/~ken/zero_copy/ >> > >> > Comments, questions and reviews are all welcome! >> >> jumbo_vm_init() has a bunch of bugs >> >> first it doesn't work right if called concurrently. >> you need to protect the initialization of jumbo_vm_object otherwise >> bad things can happen. my suggestion is to store the results of >> vm_object_allocate into a temporary, grab the mutex and then check >> to see if jumbo_vm_object has been initialized again if it has then >> free the object, otherwise store the allocated object into the >> global and continue. > > The problem here is that the mutex needs to be initialized before I can > acquire it, and there's going to be a race between checking to see > whether it has been initialized and actually initializing it. > > e.g.: > > if (!mtx_initialized(&jumbo_mutex)) > mtx_init(&jumbo_mutex, "jumbo mutex", NULL, MTX_DEF); > > mtx_lock(&jumbo_mutex); > > if (jumbo_vm_object != NULL) { > mtx_unlock(&jumbo_mutex); > return (1); > } > > /* allocate our object */ > jumbo_vm_object = vm_object_allocate(OBJT_DEFAULT, JUMBO_MAX_PAGES); > > The above would work, I think, if it weren't for the race in the mutex > initialization, and assuming I can allocate a vm object while holding > the jumbo mutex. > > Suggestions? Either use a sysinit or something gross like this: static int jumbo_init = 0; ... while (jumbo_init != 2) { if (atomic_cmpset_acq_int(&jumbo_init, 0, 1) { mtx_init(&jumbo_mutex, "jumbo_mutex", NULL, MTX_DEF); atomic_store_rel_int(&jumbo_init, 2); } } mtx_lock(&jumbo_mutex); ... a sysinit is probably best though. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 6: 4:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by hub.freebsd.org (Postfix) with ESMTP id 919B237B406 for ; Sat, 18 May 2002 06:03:58 -0700 (PDT) Received: (qmail 23408 invoked from network); 18 May 2002 13:03:54 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 May 2002 13:03:54 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g4ID3qF82151; Sat, 18 May 2002 09:03:52 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3CE61A25.61C789FA@mindspring.com> Date: Sat, 18 May 2002 09:03:40 -0400 (EDT) From: John Baldwin To: Terry Lambert Subject: Re: new zero copy sockets patches available Cc: net@FreeBSD.org, current@FreeBSD.org, "Kenneth D. Merry" , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-May-2002 Terry Lambert wrote: > Alfred Perlstein wrote: >> * Kenneth D. Merry [020517 23:31] wrote: >> > The problem here is that the mutex needs to be initialized before I can >> > acquire it, and there's going to be a race between checking to see >> > whether it has been initialized and actually initializing it. >> > >> ... >> > Suggestions? >> >> *slaps forhead* >> >> Probably a SYSINIT? > > God, it's annoying that a statically declared mutex is not > defacto initialized. Is it in solaris? > Yeah, I understand the "witness" crap (if it's there); that > doesn't make it any less annoying. > > Actually, a linker set (not a SYSINIT) could fix that... you > would still need one sysinit to do the linkage of the statically > declared structures, but it's at least doable. a SYSINIT just is a linker set, and there is a convenience SYSINIT MTX_SYSINIT() or what not that just registers a sysinit to initialize a mutex. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 7:42:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 89D4037B401; Sat, 18 May 2002 07:42:31 -0700 (PDT) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.3/8.12.3) with ESMTP id g4IEZGb4072709; Sat, 18 May 2002 10:35:16 -0400 (EDT) (envelope-from arr@FreeBSD.org) Received: from localhost (arr@localhost) by fledge.watson.org (8.12.3/8.12.3/Submit) with SMTP id g4IEZFuK072706; Sat, 18 May 2002 10:35:16 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Sat, 18 May 2002 10:35:15 -0400 (EDT) From: "Andrew R. Reiter" X-Sender: arr@fledge.watson.org To: Alfred Perlstein Cc: "Kenneth D. Merry" , current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available In-Reply-To: <3CE61A25.61C789FA@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Alfred Perlstein wrote: :> * Kenneth D. Merry [020517 23:31] wrote: :> > The problem here is that the mutex needs to be initialized before I can :> > acquire it, and there's going to be a race between checking to see :> > whether it has been initialized and actually initializing it. :> > :> ... :> > Suggestions? :> :> *slaps forhead* :> :> Probably a SYSINIT? mutex(9) and sx(9) describe two macros for this purpose. -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 8:30:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 9CF9937B403 for ; Sat, 18 May 2002 08:30:41 -0700 (PDT) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 1796AK-0005hR-00; Sat, 18 May 2002 17:30:40 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.3/8.12.2) with ESMTP id g4IEpnur057185 for ; Sat, 18 May 2002 16:51:49 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.3/8.12.3/Submit) id g4IEpnk5057184 for freebsd-current@freebsd.org; Sat, 18 May 2002 16:51:49 +0200 (CEST) From: naddy@mips.inka.de (Christian Weisgerber) Subject: ppc(4) vs. ppbus(4) module? Date: Sat, 18 May 2002 14:51:48 +0000 (UTC) Message-ID: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So far, I've had device ppc device ppbus device lpt in my KERNEL file to provide parallel printer support. Now I've noticed that ppbus and lpt are also available as modules. However, when I try to build a kernel with just device ppc (intending to load ppbus.ko and lpt.ko later), the build aborts because sys/isa/ppc.c tries to include ppbus_if.h, which isn't available without "device ppbus". Okay, so I'll just include "device ppbus" again, I guess. But then, what's the point of having a ppbus.ko at all? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 9:21:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 1324F37B40F; Sat, 18 May 2002 09:21:22 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA13874; Sat, 18 May 2002 12:21:20 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g4IGKox81993; Sat, 18 May 2002 12:20:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15590.32610.702310.769782@grasshopper.cs.duke.edu> Date: Sat, 18 May 2002 12:20:50 -0400 (EDT) To: "Marc G. Fournier" Cc: freebsd-current@freebsd.org, Subject: Re: How to dump a 4gig system on panic ? In-Reply-To: <20020517210219.P41731-100000@mail1.hub.org> References: <15589.13737.302689.294546@grasshopper.cs.duke.edu> <20020517210219.P41731-100000@mail1.hub.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Marc G. Fournier writes: > > Okay, seem to be about halfway there ... client kldload's no problem, > server runs ... do a ctl-alt-esc to get into DDB and type panic, and it > gives a message that its looking for the server and it finds it on the > right IP ... then it prints out a '1023' and finishes the panic ... > > On the 'dump server', a vmcore gets created, but its zero length ... > > thoughts? As I said, it hasn't been used for quite some time. It may require work to get it working again. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 9:41:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 27CF037B40B; Sat, 18 May 2002 09:41:08 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g4IGf79Q071299; Sat, 18 May 2002 09:41:07 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g4IGf74k071298; Sat, 18 May 2002 09:41:07 -0700 (PDT) Date: Sat, 18 May 2002 09:41:07 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Cc: ru@freebsd.org Subject: "make includes" and 30.rogue, 31.trek problem Message-ID: <20020518094107.A71256@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG root[415] pwd /usr/src/share/doc/usd root[416] make -k includes ===> title ===> contents ===> 04.csh ===> 07.mail ===> 10.exref ===> 10.exref/exref ===> 10.exref/summary ===> 11.vitut ===> 12.vi ===> 12.vi/vi ===> 12.vi/viapwh ===> 12.vi/summary ===> 13.viref ===> 18.msdiffs ===> 19.memacros ===> 20.meref ===> 30.rogue make: don't know how to make includes(continuing) ===> 31.trek make: don't know how to make includes(continuing) I do not run games on this system, so src/games has been removed. The Makefile in 30.rogue checks for the existence of the directory. With Ruslan's recent "make includes" make over, the build dies in the .else part of the Makefile. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 9:50:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from m2.annnet.or.jp (m2.annnet.or.jp [210.236.10.52]) by hub.freebsd.org (Postfix) with ESMTP id 8689737B406; Sat, 18 May 2002 09:50:14 -0700 (PDT) Received: from mcp47 (210.232.26.182) by m2.annnet.or.jp with SMTP (Eudora Internet Mail Server 3.0.2); Sun, 19 May 2002 01:24:52 +0900 Message-ID: <013d01c1fe88$b7de6fa0$7b00a8c0@kakita.co.jp> From: "=?iso-2022-jp?B?GyRCPXdNJSVrITwlSBsoQg==?=" To: Subject: =?iso-2022-jp?B?GyRCPXdNJSEmJSIlSiRySnokLyVrITwlSBsoQg==?= Date: Sun, 19 May 2002 00:55:28 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG $B2?$H$7$F$bJz$$$F$_$?$$$H??7u$K$*9M$($N=wM%!"%"%J%&%s%5!<$r(B $B#5L>0J>e#7L>?M$*J9$+$;$/$@$5$$!#!J(B18$B:P0J2<%?%l%s%H!"El5~0J(B $B30$N%?%l%s%H!"%"%J$O=|$/!K(B $B$=$NCf$G$4AjCL2DG=$JL>A0$,$"$C$?>l9g$N$_$*JV;v$$$?$7$^$9!#(B $B>l=j$OK\=#$N8)D#=j:_CO$K8B$j$^$9!#(B $BHkL)$r!J#5L>0J>e!K!"4uK>ET;T!"G/Na(B $B$r$*Aw$j$/$@$5$$!#JV?.%\%?%s$O;H$o$J$$$G$/$@$5$$!#(B $B5-:\!"?M?t$,7g$1$F$$$?>l9gJV?.$G$-$J$$>l9g$,$"$j$^$9!#(B joyuu02@finebody.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 10: 6:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 56E1137B404 for ; Sat, 18 May 2002 10:06:13 -0700 (PDT) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.3/8.12.3) with ESMTP id g4IH6CEP061443 for ; Sat, 18 May 2002 18:06:12 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.3/8.12.3/Submit) with UUCP id g4IH6CuT061442 for current@freebsd.org; Sat, 18 May 2002 18:06:12 +0100 (BST) Received: from grimreaper.grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.3/8.12.3) with ESMTP id g4IH5LMl029574 for ; Sat, 18 May 2002 18:05:21 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Message-Id: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> To: current@freebsd.org Subject: Perl script rewrites - progress (2) Date: Sat, 18 May 2002 18:05:21 +0100 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all The perl script rewrite is going really well! Here is my progress file, as it currently stands: /usr/bin/afmtodit Kyle Martin - re /usr/bin/catman John Rochester - re - done /usr/bin/makewhatis John Rochester - re - done /usr/bin/mmroff /usr/bin/sockstat des - re /usr/bin/whereis sheldonh - re /usr/sbin/adduser Mike Makonnen - re /usr/sbin/kbdmap Jonathan Belson - re /usr/sbin/pkg_update paul - del - done /usr/sbin/pkg_version Jeremy Lea - re - ready? /usr/sbin/rmuser Mike Makonnen - re /usr/sbin/scriptdump Hajimu UMEMOTO - del - done /usr/sbin/spkrtest Riccardo Torrini - re - done /usr/sbin/vidfont Jonathan Belson - re etc/periodic/* (needs to have perl usage removed) Key - "re" == to be rewritten "del" == to be deleted "ready" == work done, just waiting for commit. "done" == completed Thanks to contributors! M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 10:12:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0381037B40C; Sat, 18 May 2002 10:12:40 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA14847; Sat, 18 May 2002 13:12:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g4IHC9S82047; Sat, 18 May 2002 13:12:09 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15590.35689.201153.550505@grasshopper.cs.duke.edu> Date: Sat, 18 May 2002 13:12:09 -0400 (EDT) To: "Kenneth D. Merry" Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available In-Reply-To: <20020517233950.A36169@panzer.kdm.org> References: <20020517233950.A36169@panzer.kdm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kenneth D. Merry writes: > > I have released a new set of zero copy sockets patches, against -current > from today (May 17th, 2002). > > The main change is to deal with the vfs_ioopt changes that Alan Cox made in > kern_subr.c. (They conflicted a bit with the zero copy receive code.) > > The patches and the FAQ are available here: > > http://people.freebsd.org/~ken/zero_copy/ > > Comments, questions and reviews are all welcome! > Hi Ken, I'm glad to see that you're still maintining this! Assuming the mutex issues get sorted out, what do you think the odds are of getting this into the tree? The only possible issue I see is with the tigon firmware. Is the firmware you're using of the same vintage as what's in the tree now? Does it contain all the same fixes? Thanks again for keeping this alive, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 10:15:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.sandvine.com (sandvine.com [209.167.74.226]) by hub.freebsd.org (Postfix) with ESMTP id 3759737B408; Sat, 18 May 2002 10:15:45 -0700 (PDT) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Sat, 18 May 2002 13:15:44 -0400 Message-ID: From: Don Bowman To: 'Andrew Gallatin' , "Kenneth D. Merry" Cc: current@FreeBSD.org, net@FreeBSD.org Subject: RE: new zero copy sockets patches available Date: Sat, 18 May 2002 13:15:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Andrew Gallatin writes: >> Kenneth D. Merry writes: >> > >> > I have released a new set of zero copy sockets patches, against -current >> > from today (May 17th, 2002). > > Hi Ken, > > I'm glad to see that you're still maintining this! > > Assuming the mutex issues get sorted out, what do you think the odds > are of getting this into the tree? The only possible issue I see is > with the tigon firmware. Is the firmware you're using of the same > vintage as what's in the tree now? Does it contain all the same > fixes? As a related question, will this work with the broadcom gigabit (bge) driver, which is the Tigon III? If not, what would it take to get it working? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 10:28:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from nala.dohd.org (a29150.upc-a.chello.nl [62.163.29.150]) by hub.freebsd.org (Postfix) with ESMTP id B4AAA37B405 for ; Sat, 18 May 2002 10:28:07 -0700 (PDT) Received: by nala.dohd.org (Postfix, from userid 1008) id 633EDD91A; Sat, 18 May 2002 19:28:06 +0200 (MET DST) Date: Sat, 18 May 2002 19:28:06 +0200 From: Mark Huizer To: current@freebsd.org Subject: Re: Perl script rewrites - progress (2) Message-ID: <20020518172806.GA25059@eeyore.local.dohd.org> References: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, May 18, 2002 at 06:05:21PM +0100, Mark Murray wrote: > Hi all > > The perl script rewrite is going really well! > > Here is my progress file, as it currently stands: > > Thanks to contributors! > I just upgraded my machine, removed perl as far as I could find it, and tried to rebuild perl from the ports tree. So far, I had to change the Makefile first, since it used perl for the post-patch target. That was easy: change the CP and the PERL -pi to a: ${SED} <${FILES}/use.perl >$WRKDIR/use.perl But so far it doesn't compile :-( Anyone else seeing this? Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 11:23:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from omega.lovett.com (omega.lovett.com [209.249.90.123]) by hub.freebsd.org (Postfix) with ESMTP id 9E00E37B405 for ; Sat, 18 May 2002 11:23:28 -0700 (PDT) Received: from [24.243.55.247] (helo=[10.0.0.2] ident=ident) by omega.lovett.com with esmtp (Exim 3.36 #1) id 1798rN-0009Cp-00; Sat, 18 May 2002 11:23:17 -0700 User-Agent: Microsoft-Entourage/10.0.0.1331 Date: Sat, 18 May 2002 13:23:13 -0500 Subject: Re: Perl script rewrites - progress (2) From: Ade Lovett To: Mark Murray , Message-ID: In-Reply-To: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 05/18/02 12:05, "Mark Murray" wrote: > Hi all > > The perl script rewrite is going really well! > > Here is my progress file, as it currently stands: To add one to the list.. /usr/sbin/mergemaster has two calls to perl in it, to extract file/directory permissions -- anyone (doug?) working on this? -aDe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 11:40:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 8B30A37B400; Sat, 18 May 2002 11:40:32 -0700 (PDT) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.3/8.12.3) with ESMTP id g4IIeVEP062113; Sat, 18 May 2002 19:40:31 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.3/8.12.3/Submit) with UUCP id g4IIeVr5062112; Sat, 18 May 2002 19:40:31 +0100 (BST) Received: from grimreaper.grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.3/8.12.3) with ESMTP id g4IId9Ml033376; Sat, 18 May 2002 19:39:09 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Message-Id: <200205181839.g4IId9Ml033376@grimreaper.grondar.org> To: Ade Lovett Cc: current@FreeBSD.org Subject: Re: Perl script rewrites - progress (2) References: In-Reply-To: ; from Ade Lovett "Sat, 18 May 2002 13:23:13 CDT." Date: Sat, 18 May 2002 19:39:09 +0100 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On 05/18/02 12:05, "Mark Murray" wrote: > > > Hi all > > > > The perl script rewrite is going really well! > > > > Here is my progress file, as it currently stands: > > To add one to the list.. /usr/sbin/mergemaster has two calls to perl in it, > to extract file/directory permissions -- anyone (doug?) working on this? Thank you! Added and assigned to doug locally. Doug, I hope that is OK?? M -- o Mark Murray \_ O.\_ Warning: this .sig is umop ap!sdn #text/plain; name=cv.doc [Mark Murray CV Plain Text] cv.doc #application/octet-stream; name=cv.pdf [Mark Murray CV PDF] cv.pdf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 11:54:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 9899137B40C for ; Sat, 18 May 2002 11:54:11 -0700 (PDT) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.3/8.12.2) with ESMTP id g4IIsAJn033510 for ; Sat, 18 May 2002 11:54:10 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.3/8.12.3/Submit) id g4IIsAXj033509 for current@freebsd.org; Sat, 18 May 2002 11:54:10 -0700 (PDT) Date: Sat, 18 May 2002 11:54:10 -0700 From: "David O'Brien" To: current@freebsd.org Subject: mergemaster(8) broken -- uses Perl Message-ID: <20020518115410.A33493@dragon.nuxi.com> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anyone got a patch? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 12: 9:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 219DC37B409; Sat, 18 May 2002 12:09:17 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id 6FB6A103706; Sat, 18 May 2002 16:09:15 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 6D8791036B4; Sat, 18 May 2002 16:09:14 -0300 (ADT) Date: Sat, 18 May 2002 16:09:14 -0300 (ADT) From: "Marc G. Fournier" To: Andrew Gallatin Cc: freebsd-current@freebsd.org, Subject: Re: How to dump a 4gig system on panic ? In-Reply-To: <15590.32610.702310.769782@grasshopper.cs.duke.edu> Message-ID: <20020518160635.M41731-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, I have a machine to debug/test this on, if you can provide some directions on how to debug and get her up to date? :) With the larger and larger systems that ppl are implementing, is this something that might be useful to get into the core system? On Sat, 18 May 2002, Andrew Gallatin wrote: > > Marc G. Fournier writes: > > > > Okay, seem to be about halfway there ... client kldload's no problem, > > server runs ... do a ctl-alt-esc to get into DDB and type panic, and it > > gives a message that its looking for the server and it finds it on the > > right IP ... then it prints out a '1023' and finishes the panic ... > > > > On the 'dump server', a vmcore gets created, but its zero length ... > > > > thoughts? > > As I said, it hasn't been used for quite some time. It may require > work to get it working again. > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 12:56: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 35B8A37B401 for ; Sat, 18 May 2002 12:56:05 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g4IJu49Q072491 for ; Sat, 18 May 2002 12:56:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g4IJu4VT072490 for freebsd-current@freebsd.org; Sat, 18 May 2002 12:56:04 -0700 (PDT) Date: Sat, 18 May 2002 12:56:04 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: gdb breaks world Message-ID: <20020518125604.A72462@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ===> gnu/usr.bin/binutils/gdb cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c cc1: warnings being treated as errors init.c:3: warning: function declaration isn't a prototype init.c: In function `initialize_all_files': init.c:4: warning: function declaration isn't a prototype init.c:5: warning: function declaration isn't a prototype init.c:6: warning: function declaration isn't a prototype init.c:7: warning: function declaration isn't a prototype init.c:8: warning: function declaration isn't a prototype init.c:9: warning: function declaration isn't a prototype init.c:10: warning: function declaration isn't a prototype init.c:11: warning: function declaration isn't a prototype init.c:12: warning: function declaration isn't a prototype init.c:13: warning: function declaration isn't a prototype skiping 51 more warnings init.c:64: warning: function declaration isn't a prototype *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils/gdb. *** Error code 1 Stop in /usr/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 14:12: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 21CCE37B408 for ; Sat, 18 May 2002 14:12:05 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 May 2002 22:12:04 +0100 (BST) To: Ian Cc: Terry Lambert , freebsd-current Subject: Re: df In-Reply-To: Your message of "Fri, 17 May 2002 17:40:30 MDT." Date: Sat, 18 May 2002 22:12:03 +0100 From: Ian Dowse Message-ID: <200205182212.aa91110@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Ian writes: >Actually, I now think a more-correct fix would be to have no if statement at >all, and just always recalculate the field widths after calling the routine >to re-get the stats. Yes, I agree. Committed, thanks! Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16: 0:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from gatesrv.RZ.UniBw-Muenchen.de (gatesrv.RZ.UniBW-Muenchen.de [137.193.11.27]) by hub.freebsd.org (Postfix) with ESMTP id 5F4A137B407; Sat, 18 May 2002 16:00:15 -0700 (PDT) Received: from nemesis.informatik.unibw-muenchen.de (nemesis.Informatik.UniBw-Muenchen.de [137.193.60.30]) by gatesrv.RZ.UniBw-Muenchen.de (8.11.2/8.11.2) with ESMTP id g4IMWB218642; Sun, 19 May 2002 00:32:11 +0200 (MEST) Received: from localhost (localhost.informatik.unibw-muenchen.de [127.0.0.1]) by nemesis.informatik.unibw-muenchen.de (Postfix) with ESMTP id 296545A54A; Sun, 19 May 2002 00:32:10 +0200 (CEST) Received: by nemesis.informatik.unibw-muenchen.de (Postfix, from userid 1001) id 517C15A547; Sun, 19 May 2002 00:32:07 +0200 (CEST) Date: Sun, 19 May 2002 00:32:07 +0200 From: Oliver Braun To: current@freebsd.org, ports@freebsd.org Subject: machine/endian.h revision 1.33 breaks port x11-fm/gentoo Message-ID: <20020518223207.GA74796@nemesis.informatik.unibw-muenchen.de> Mail-Followup-To: Oliver Braun , current@freebsd.org, ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.99i Organization: University of the Federal Armed Forces Munich, Germany X-Mailer: Mutt http://www.mutt.org/ X-OS: FreeBSD 4.6-PRERELEASE i386 http://www.freebsd.org/ X-Newsreader: SLRN http://www.slrn.org/ X-Uptime: 16 days X-URL: http://ist.unibw-muenchen.de/People/obraun X-Accept-Language: de en X-Location: Europe, Germany, Munich X-Editor: Vim-601 http://www.vim.org/ X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am the ports maintainer of x11-fm/gentoo. Building gentoo dies since revision 1.33 of machine/endian.h with the following error: In file included from cmdseq.c:18: /usr/include/sys/wait.h:114: duplicate member `w_Filler' /usr/include/sys/wait.h:115: duplicate member `w_Retcode' /usr/include/sys/wait.h:116: duplicate member `w_Coredump' /usr/include/sys/wait.h:117: duplicate member `w_Termsig' /usr/include/sys/wait.h:132: duplicate member `w_Filler' /usr/include/sys/wait.h:133: duplicate member `w_Stopsig' /usr/include/sys/wait.h:134: duplicate member `w_Stopval' *** Error code 1 With machine/endian.h revision 1.32 it works. A workaround for x11-fm/gentoo is to declare the functions needed explicit and avoid including whole sys/wait.h. Has anyone an idea for a "not-so-dirty" hack? What could be the problem? Is this a system-wide issue or a x11-fm/gentoo -specific one? Defining __BSD_VISIBLE in cmdseq.c did not help. Regards, Olli -- IST & IIS _ INF _ UniBwM ____ http://ist.unibw-muenchen.de/People/obraun/ Tele-Consulting GmbH ________ http://www.tele-consulting.com/ ___ obraun@ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16: 3:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id CF79A37B40B; Sat, 18 May 2002 16:03:07 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179DEA-0001yS-00; Sat, 18 May 2002 16:03:07 -0700 Message-ID: <3CE6DD8C.FC95386F@mindspring.com> Date: Sat, 18 May 2002 16:02:36 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: net@FreeBSD.org, current@FreeBSD.org, "Kenneth D. Merry" , Alfred Perlstein Subject: Re: new zero copy sockets patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > God, it's annoying that a statically declared mutex is not > > defacto initialized. > > Is it in solaris? It isn't in FreeBSD because of the need to link mutex'es into the "witness protection program". 8-). > > Yeah, I understand the "witness" crap (if it's there); that > > doesn't make it any less annoying. > > > > Actually, a linker set (not a SYSINIT) could fix that... you > > would still need one sysinit to do the linkage of the statically > > declared structures, but it's at least doable. > > a SYSINIT just is a linker set, and there is a convenience SYSINIT > MTX_SYSINIT() or what not that just registers a sysinit to initialize > a mutex. What you want to do is implement a: MUTEX_DECLARE(mutex_name). This would implicitly add the mutex into the limker set containing the addresses of statically declared mutex'es. The SYSINIT()'s purpose would be to traverse this linker set, calling the moral equivalent of "mutex_init" on each one of them. You could do this with a SYSINIT(), as has been suggested, but that would add a relatively large per mutex overhead for each one you want to declare, since you'd basically be repeating the common components for doing the job for each and every mutex, instead of sharing them. Technically, some later programmer could come along and recover the linker set memory, actually, since it's only used once, for the traversal, at kernel startup. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:13:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id E3FE937B407 for ; Sat, 18 May 2002 16:13:23 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179DNy-0002of-00; Sat, 18 May 2002 16:13:15 -0700 Message-ID: <3CE6DFED.8604C72C@mindspring.com> Date: Sat, 18 May 2002 16:12:45 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: Ian , freebsd-current Subject: Re: df References: <200205182212.aa91110@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > In message , Ian writes: > >Actually, I now think a more-correct fix would be to have no if statement at > >all, and just always recalculate the field widths after calling the routine > >to re-get the stats. > > Yes, I agree. Committed, thanks! Ian agrees with Ian...? ...I know, different Ian's. 8-). I think the reason for the "if" is to keep the df from hanging indefinitely, particularly when you give it an explicit list. Doesn't removing the "if" break that? 8-) -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:23: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id 9592037B406 for ; Sat, 18 May 2002 16:22:47 -0700 (PDT) Received: (qmail 11331 invoked from network); 18 May 2002 23:22:43 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 May 2002 23:22:43 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g4INLxF83616; Sat, 18 May 2002 19:21:59 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3CE6DD8C.FC95386F@mindspring.com> Date: Sat, 18 May 2002 19:21:48 -0400 (EDT) From: John Baldwin To: Terry Lambert Subject: Re: new zero copy sockets patches available Cc: Alfred Perlstein , "Kenneth D. Merry" , current@FreeBSD.org, net@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-May-2002 Terry Lambert wrote: > John Baldwin wrote: >> > God, it's annoying that a statically declared mutex is not >> > defacto initialized. >> >> Is it in solaris? > > It isn't in FreeBSD because of the need to link mutex'es into > the "witness protection program". 8-). Actually, there is more to it than that. Or at least, there will be when turnstiles are added (turnstiles require some function callouts to work properly). > MUTEX_DECLARE(mutex_name). Umm, yes, like MTX_SYSINIT(). :) > You could do this with a SYSINIT(), as has been suggested, but > that would add a relatively large per mutex overhead for each > one you want to declare, since you'd basically be repeating the > common components for doing the job for each and every mutex, > instead of sharing them. Umm, this is a boot-up thing so it's not that big of a deal, plus the actual code isn't duplicated, we call a common function for the actual mutex initialization. > Technically, some later programmer could come along and recover > the linker set memory, actually, since it's only used once, for > the traversal, at kernel startup. Erm, they could do the same with the little mtx_args structs if they want to as well, but I think it's more effor than its worth. > -- Terry -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:23:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id BB5CB37B403; Sat, 18 May 2002 16:23:51 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179DY9-0001UX-00; Sat, 18 May 2002 16:23:46 -0700 Message-ID: <3CE6E263.77E337E0@mindspring.com> Date: Sat, 18 May 2002 16:23:15 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Don Bowman Cc: 'Andrew Gallatin' , "Kenneth D. Merry" , current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Don Bowman wrote: > > Andrew Gallatin writes: > >> Kenneth D. Merry writes: > >> > > >> > I have released a new set of zero copy sockets patches, against > -current > >> > from today (May 17th, 2002). > > > > Hi Ken, > > > > I'm glad to see that you're still maintining this! > > > > Assuming the mutex issues get sorted out, what do you think the odds > > are of getting this into the tree? The only possible issue I see is > > with the tigon firmware. Is the firmware you're using of the same > > vintage as what's in the tree now? Does it contain all the same > > fixes? > > As a related question, will this work with the broadcom gigabit (bge) > driver, which is the Tigon III? If not, what would it take to get > it working? Broadcom is a bit more anal about people having access to their firmware to make their products meet their design capabilities. Really annoying about the whole Broadcom/Alteon thing... To do the work, you'd have to do it on your own, after licensing the firmware, after signing an NDA. Unlike the rather public Tigon II firmware, the Tigon III doesn't have a lot of synergy or interesting work going for it. Most people doing interesting work tend to use Tigon II cards, because of this. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:41:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 204C237B40B for ; Sat, 18 May 2002 16:41:47 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 May 2002 00:41:46 +0100 (BST) To: Terry Lambert Cc: Ian , freebsd-current Subject: Re: df In-Reply-To: Your message of "Sat, 18 May 2002 16:12:45 PDT." <3CE6DFED.8604C72C@mindspring.com> Date: Sun, 19 May 2002 00:41:44 +0100 From: Ian Dowse Message-ID: <200205190041.aa04845@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CE6DFED.8604C72C@mindspring.com>, Terry Lambert writes: >I think the reason for the "if" is to keep the df from hanging >indefinitely, particularly when you give it an explicit list. No, I believe the "if (vfslist != NULL)" code was there to reduce the maximum column widths to those necessary for an explicit list of filesystems rather than using the maximum widths for all filesystems. The regetmntinfo() call before the "if" has already performed any operations that could hang indefinitely, so it makes sense to unconditionally use these up-to-date results instead of the potentially stale list from getmntinfo(..., MNT_NOWAIT). Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:42:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id E354137B41C; Sat, 18 May 2002 16:41:54 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179Dph-0002IH-00; Sat, 18 May 2002 16:41:53 -0700 Message-ID: <3CE6E6A2.4A42228B@mindspring.com> Date: Sat, 18 May 2002 16:41:22 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Alfred Perlstein , "Kenneth D. Merry" , current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > On 18-May-2002 Terry Lambert wrote: > > John Baldwin wrote: > >> > God, it's annoying that a statically declared mutex is not > >> > defacto initialized. > >> > >> Is it in solaris? > > > > It isn't in FreeBSD because of the need to link mutex'es into > > the "witness protection program". 8-). > > Actually, there is more to it than that. Or at least, there will be > when turnstiles are added (turnstiles require some function callouts > to work properly). It's the function callouts that are the problem. 8-(. > > MUTEX_DECLARE(mutex_name). > > Umm, yes, like MTX_SYSINIT(). :) No. An MTX_SYSINIT() that wrapped a declaration and a SYSINIT() would als imply the definition of an static function to do the initialization, that then got called by the SYSINIT() itself. This is actually what I was saying was bad: a static function per mutex declaration. You really want to avoid the pthreads "mutex initializer" thing; the compiler doesn't have code that can attach to data declarations to fix the problem. So, among other things, you want to use the same initializer function instance for all statically declared mutexes. So you have to use something other than a SYSINIT() for the declarations, but you could use *one SYSINIT()* to do the pre-use initialization of *all* declarations. > > You could do this with a SYSINIT(), as has been suggested, but > > that would add a relatively large per mutex overhead for each > > one you want to declare, since you'd basically be repeating the > > common components for doing the job for each and every mutex, > > instead of sharing them. > > Umm, this is a boot-up thing so it's not that big of a deal, plus > the actual code isn't duplicated, we call a common function for > the actual mutex initialization. Maybe. I don't think a large sysinit structure is as useful as an array of addresses of mutexes needing initialization. There would be a serious tempation in the former case to provide for some type of non-uniform initialization of statically declared sysinit objects. It would be nice if the non-uniformity could be limited to the fact that if the WITNESS code was there, it needed to be linked onto the list. With the WITNESS code not compiled into the kernel, I'd prefer not to include the initialization code at all. It would encorage bad practice, if it weren't conditional on WITNESS. > > Technically, some later programmer could come along and recover > > the linker set memory, actually, since it's only used once, for > > the traversal, at kernel startup. > > Erm, they could do the same with the little mtx_args structs if > they want to as well, but I think it's more effor than its worth. Actually, I don't think they could. The intermediate stage for that would really suck. The only way to handle it is to use different ELF sections for that datam so that you could discard the section later. This is worthwhile for device probe code, maybe attach code, any linker set contents, but not really for individial small structures each getting jammed into their own page size object. 8-). You'd need to do a lot more work, including KVA defragmentation by being able to sectionally attribute anything in the paging path, to keep it from being moved around, or the move-it-around code itself. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:53:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id 8CEE137B411 for ; Sat, 18 May 2002 16:53:28 -0700 (PDT) Received: (qmail 27112 invoked from network); 18 May 2002 23:53:25 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 18 May 2002 23:53:25 -0000 Received: from laptop.baldwin.cx (laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g4INqkF83718; Sat, 18 May 2002 19:52:46 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3CE6E6A2.4A42228B@mindspring.com> Date: Sat, 18 May 2002 19:52:36 -0400 (EDT) From: John Baldwin To: Terry Lambert Subject: Re: new zero copy sockets patches available Cc: net@FreeBSD.org, current@FreeBSD.org, "Kenneth D. Merry" , Alfred Perlstein Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18-May-2002 Terry Lambert wrote: > John Baldwin wrote: >> On 18-May-2002 Terry Lambert wrote: >> > John Baldwin wrote: >> >> > God, it's annoying that a statically declared mutex is not >> >> > defacto initialized. >> >> >> >> Is it in solaris? >> > >> > It isn't in FreeBSD because of the need to link mutex'es into >> > the "witness protection program". 8-). >> >> Actually, there is more to it than that. Or at least, there will be >> when turnstiles are added (turnstiles require some function callouts >> to work properly). > > It's the function callouts that are the problem. 8-(. Unfortunately there aren't easy solutions to this. Even solaris 7 uses callouts. We would use fewer of them at least. >> > MUTEX_DECLARE(mutex_name). >> >> Umm, yes, like MTX_SYSINIT(). :) > > No. An MTX_SYSINIT() that wrapped a declaration and a SYSINIT() > would als imply the definition of an static function to do the > initialization, that then got called by the SYSINIT() itself. This is a false implication. > This is actually what I was saying was bad: a static function > per mutex declaration. Umm, no, there is _one_ global function that we call. Why not check the actual code? > So, among other things, you want to use the same initializer function > instance for all statically declared mutexes. Um, we already do this. > So you have to use something other than a SYSINIT() for the declarations, > but you could use *one SYSINIT()* to do the pre-use initialization of > *all* declarations. Why don't you read the code? Here, I'll quote it for you: struct mtx_args { struct mtx *ma_mtx; const char *ma_desc; int ma_opts; }; #define MTX_SYSINIT(name, mtx, desc, opts) \ static struct mtx_args name##_args = { \ mtx, \ desc, \ opts \ }; \ SYSINIT(name##_mtx_sysinit, SI_SUB_LOCK, SI_ORDER_MIDDLE, \ mtx_sysinit, &name##_args) Note no static function, instead we use the global function mtx_sysinit() in kern_mutex.c: /* * General init routine used by the MTX_SYSINIT() macro. */ void mtx_sysinit(void *arg) { struct mtx_args *margs = arg; mtx_init(margs->ma_mtx, margs->ma_desc, NULL, margs->ma_opts); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 16:55:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by hub.freebsd.org (Postfix) with ESMTP id B61C037B401 for ; Sat, 18 May 2002 16:55:26 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by gull.prod.itd.earthlink.net with esmtp (Exim 3.33 #2) id 179E2j-0006Xf-00; Sat, 18 May 2002 16:55:21 -0700 Message-ID: <3CE6E9CB.597E0BC@mindspring.com> Date: Sat, 18 May 2002 16:54:51 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ian Dowse Cc: Ian , freebsd-current Subject: Re: df References: <200205190041.aa04845@salmon.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ian Dowse wrote: > In message <3CE6DFED.8604C72C@mindspring.com>, Terry Lambert writes: > >I think the reason for the "if" is to keep the df from hanging > >indefinitely, particularly when you give it an explicit list. > > No, I believe the "if (vfslist != NULL)" code was there to reduce > the maximum column widths to those necessary for an explicit list > of filesystems rather than using the maximum widths for all > filesystems. The regetmntinfo() call before the "if" has already > performed any operations that could hang indefinitely, so it makes > sense to unconditionally use these up-to-date results instead of > the potentially stale list from getmntinfo(..., MNT_NOWAIT). Like "ps", "df" is a snapshot. As such, "staleness" after a few tenths of a second is really irrelevent, since the information is never really "the real and precise information". It's more important to be able to get information in a misbehaving system, without hanging your shell forever. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 17: 7: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 9CF1337B40A; Sat, 18 May 2002 17:06:55 -0700 (PDT) Received: from pool0271.cvx22-bradley.dialup.earthlink.net ([209.179.199.16] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 179EDu-0000VZ-00; Sat, 18 May 2002 17:06:54 -0700 Message-ID: <3CE6EC7F.F75B00F9@mindspring.com> Date: Sat, 18 May 2002 17:06:23 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: net@FreeBSD.org, current@FreeBSD.org, "Kenneth D. Merry" , Alfred Perlstein Subject: Re: new zero copy sockets patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > > This is actually what I was saying was bad: a static function > > per mutex declaration. > > Umm, no, there is _one_ global function that we call. Why not check > the actual code? Are you talking about a P4 branch, and not the main repository? > Why don't you read the code? > > Here, I'll quote it for you: > > struct mtx_args { > struct mtx *ma_mtx; > const char *ma_desc; > int ma_opts; > }; > > #define MTX_SYSINIT(name, mtx, desc, opts) \ > static struct mtx_args name##_args = { \ > mtx, \ > desc, \ > opts \ > }; \ > SYSINIT(name##_mtx_sysinit, SI_SUB_LOCK, SI_ORDER_MIDDLE, \ > mtx_sysinit, &name##_args) This is *EXACTLY* what I thought should be avoided. The linker set should not contain the address of a bunch of static mtx_args structs, because there shouldn't *be* a bunch of static mtx_args structs. And the ability to pass different initialization values to different mutex instances is broken, in that it makes it impossible to look at a mutex, and know what you need to know about it, merely because it's a mutex. Minimally, you are going to add 12 bytes per mutex (24 on 64 bit machines), plus however much memory is taken up by the "ma_desc", plus it makes the memory unrecoverable, because the address of the string that's in the supposedly "recoverable" data segment can't be recovered any more, because making the data segment "go away" would invalidate dereferences of the pointer. This is about as ugly the mutex code taking parameters (we've had that discussion before). > Note no static function, instead we use the global function mtx_sysinit() > in kern_mutex.c: > > /* > * General init routine used by the MTX_SYSINIT() macro. > */ > void > mtx_sysinit(void *arg) > { > struct mtx_args *margs = arg; > > mtx_init(margs->ma_mtx, margs->ma_desc, NULL, margs->ma_opts); > } On a per instance basis. For which you create not only an mtx_args structure, but also a sysinit structure, to act as a container for the reference to the mtx_args struct address, and the mtx_sysinit function, etc.. Bleh. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 18:48: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 5C5E637B407 for ; Sat, 18 May 2002 18:47:59 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J1lfQJ000543; Sun, 19 May 2002 04:47:56 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J1leIu006910; Sun, 19 May 2002 04:47:40 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J1lWCj006905; Sun, 19 May 2002 04:47:32 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 04:47:31 +0300 From: Giorgos Keramidas To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: Perl script rewrites - progress (2) Message-ID: <20020519014731.GA6848@hades.hell.gr> References: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205181705.g4IH5LMl029574@grimreaper.grondar.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-18 18:05, Mark Murray wrote: > The perl script rewrite is going really well! > > Here is my progress file, as it currently stands: > ... > > etc/periodic/* (needs to have perl usage removed) Hello Mark and all, I've started digging around /etc/periodic, and have already done part of the work. You might as well, have this assigned to me, unless someone proves faster than me and gets it done in less than a day or two. What I've done so far (and only slightly tested) is available at http://www.FreeBSD.org/~keramida/diff/periodic.diff -- Giorgos Keramidas - http://www.FreeBSD.org keramida@FreeBSD.org - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 18:51:36 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 79B7037B400; Sat, 18 May 2002 18:51:31 -0700 (PDT) Date: Sat, 18 May 2002 18:51:31 -0700 From: John De Boskey To: Current List Subject: Inetd configuration message logging (or lack thereof) Message-ID: <20020518185131.A86082@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Comments on the following patch. The messages are invisible with a default install. This patch gets them into /var/log/messages where they can be seen. -John ps: Not in this patch, but I wonder if syslog cannot be redirected to the console when run -d. Something like: #define syslog InetdSyslog void InetdSyslog(int,char *, ...); void InetdSyslog(int priority,char *message, ...) { va_list ap; va_start(ap, message); if (debug) { vfprintf(stderr,message,ap); fprintf(stderr,"\n"); } else vsyslog(priority,message,ap); va_end(message); return; } RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.96 diff -u -r1.96 inetd.c --- inetd.c 8 May 2002 17:20:08 -0000 1.96 +++ inetd.c 19 May 2002 01:04:56 -0000 @@ -1613,7 +1613,7 @@ } if (strncmp(sep->se_proto, "rpc/", 4) == 0) { if (no_v4bind != 0) { - syslog(LOG_INFO, "IPv4 bind is ignored for %s", + syslog(LOG_NOTICE, "IPv4 bind is ignored for %s", sep->se_service); freeconfig(sep); goto more; @@ -1654,7 +1654,7 @@ #ifdef INET6 if (sep->se_proto[strlen(sep->se_proto) - 1] == '6') { if (no_v6bind != 0) { - syslog(LOG_INFO, "IPv6 bind is ignored for %s", + syslog(LOG_NOTICE, "IPv6 bind is ignored for %s", sep->se_service); freeconfig(sep); goto more; @@ -1686,7 +1686,7 @@ #endif { /* default to v4 bind if not v6 bind */ if (no_v4bind != 0) { - syslog(LOG_INFO, "IPv4 bind is ignored for %s", + syslog(LOG_NOTICE, "IPv4 bind is ignored for %s", sep->se_service); freeconfig(sep); goto more; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 19:29:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 472BF37B40C for ; Sat, 18 May 2002 19:29:28 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J2TPQJ016480 for ; Sun, 19 May 2002 05:29:26 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J2TOIu010302 for ; Sun, 19 May 2002 05:29:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J2TOvV010301 for current@FreeBSD.ORG; Sun, 19 May 2002 05:29:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 05:29:22 +0300 From: Giorgos Keramidas To: current@FreeBSD.ORG Subject: Re: mergemaster(8) broken -- uses Perl Message-ID: <20020519022922.GA10039@hades.hell.gr> References: <20020518115410.A33493@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020518115410.A33493@dragon.nuxi.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-18 11:54, David O'Brien wrote: > Anyone got a patch? Part of the problems I had when I tried to replace perl in mergemaster.sh with something `native' was that the perl code uses stat(2) to obtain the permission bits of a directory/file and I can't think of a way to do this with tools in the base system without resorting to ugly awk scripts that parse and translate ls(1) output. Any ideas? I am not really sure I like something like: % /bin/ls -ld /tmp | sed -e 's/[[:space:]].*$//' |\ awk -v mode=0 '{ if (match($0, "^.r........")) { mode += 00400; } if (match($0, "^..w.......")) { mode += 00200; } if (match($0, "^...S......")) { mode += 04000; } if (match($0, "^...s......")) { mode += 04100; } if (match($0, "^...x......")) { mode += 00100; } if (match($0, "^....r.....")) { mode += 00040; } if (match($0, "^.....w....")) { mode += 00020; } if (match($0, "^......S...")) { mode += 02000; } if (match($0, "^......s...")) { mode += 02010; } if (match($0, "^......x...")) { mode += 00010; } if (match($0, "^.......r..")) { mode += 00004; } if (match($0, "^........w.")) { mode += 00002; } if (match($0, "^.........T")) { mode += 01000; } if (match($0, "^.........t")) { mode += 01001; } if (match($0, "^.........x")) { mode += 00001; } } END { printf "0%o\n", mode; }' [ The above should print in stdout just 01777 as a number. ] It seems to work, but it's a bit ugly for my taste. Plus it will break if the permission bits ever change representation (although this is unlikely to happen any time real soon). Does anyone know of any other (possibly more elegant way) of reading the numeric value of the permission bits for a file? -- Giorgos Keramidas - http://www.FreeBSD.org keramida@FreeBSD.org - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 19:31:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id B1CF037B405 for ; Sat, 18 May 2002 19:31:13 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J2VAQJ017039; Sun, 19 May 2002 05:31:11 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J2V9Iu010324; Sun, 19 May 2002 05:31:09 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J2V8mq010323; Sun, 19 May 2002 05:31:08 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 05:31:08 +0300 From: Giorgos Keramidas To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: gdb breaks world Message-ID: <20020519023108.GB10039@hades.hell.gr> References: <20020518125604.A72462@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020518125604.A72462@troutmask.apl.washington.edu> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-18 12:56, Steve Kargl wrote: > ===> gnu/usr.bin/binutils/gdb > cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c > cc1: warnings being treated as errors Known problem. Warnings are treated as errors. Since GCC 3.1 has brought a hell of a lot more warnings with us, you should use -DNO_WERROR until the dust of the GCC 3.1 import settles down. -- Giorgos Keramidas - http://www.FreeBSD.org keramida@FreeBSD.org - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:11:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by hub.freebsd.org (Postfix) with ESMTP id F18E037B407 for ; Sat, 18 May 2002 20:11:31 -0700 (PDT) Received: (qmail 30223 invoked from network); 19 May 2002 03:11:30 -0000 Received: from unknown (HELO VINZCLORTHO) ([66.92.70.186]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 May 2002 03:11:30 -0000 From: "Benjamin P. Grubin" To: "'Giorgos Keramidas'" , Subject: RE: mergemaster(8) broken -- uses Perl Date: Sat, 18 May 2002 23:11:24 -0400 Message-ID: <000301c1fee2$dc221650$080aa8c0@VINZCLORTHO> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020519022922.GA10039@hades.hell.gr> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is [t]csh's `filetest` builtin viable here? Relurking, Ben > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of > Giorgos Keramidas > Sent: Saturday, May 18, 2002 10:29 PM > To: current@FreeBSD.ORG > Subject: Re: mergemaster(8) broken -- uses Perl > > > On 2002-05-18 11:54, David O'Brien wrote: > > Anyone got a patch? > > Part of the problems I had when I tried to replace perl in > mergemaster.sh with something `native' was that the perl code uses > stat(2) to obtain the permission bits of a directory/file and I can't > think of a way to do this with tools in the base system without > resorting to ugly awk scripts that parse and translate ls(1) output. > > Any ideas? I am not really sure I like something like: > > % /bin/ls -ld /tmp | sed -e 's/[[:space:]].*$//' |\ > awk -v mode=0 '{ > if (match($0, "^.r........")) { mode += 00400; } > if (match($0, "^..w.......")) { mode += 00200; } > if (match($0, "^...S......")) { mode += 04000; } > if (match($0, "^...s......")) { mode += 04100; } > if (match($0, "^...x......")) { mode += 00100; } > if (match($0, "^....r.....")) { mode += 00040; } > if (match($0, "^.....w....")) { mode += 00020; } > if (match($0, "^......S...")) { mode += 02000; } > if (match($0, "^......s...")) { mode += 02010; } > if (match($0, "^......x...")) { mode += 00010; } > if (match($0, "^.......r..")) { mode += 00004; } > if (match($0, "^........w.")) { mode += 00002; } > if (match($0, "^.........T")) { mode += 01000; } > if (match($0, "^.........t")) { mode += 01001; } > if (match($0, "^.........x")) { mode += 00001; } > } > END { printf "0%o\n", mode; }' > > [ The above should print in stdout just 01777 as a number. ] > > It seems to work, but it's a bit ugly for my taste. Plus it will > break if the permission bits ever change representation (although this > is unlikely to happen any time real soon). > > Does anyone know of any other (possibly more elegant way) of reading > the numeric value of the permission bits for a file? > > -- > Giorgos Keramidas - http://www.FreeBSD.org > keramida@FreeBSD.org - The Power to Serve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:12:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 344F237B40F; Sat, 18 May 2002 20:12:16 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g4J3CF9Q074620; Sat, 18 May 2002 20:12:15 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g4J3CFp1074619; Sat, 18 May 2002 20:12:15 -0700 (PDT) Date: Sat, 18 May 2002 20:12:15 -0700 From: Steve Kargl To: Giorgos Keramidas Cc: freebsd-current@FreeBSD.ORG Subject: Re: gdb breaks world Message-ID: <20020518201215.A74579@troutmask.apl.washington.edu> References: <20020518125604.A72462@troutmask.apl.washington.edu> <20020519023108.GB10039@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020519023108.GB10039@hades.hell.gr>; from keramida@FreeBSD.ORG on Sun, May 19, 2002 at 05:31:08AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote: > On 2002-05-18 12:56, Steve Kargl wrote: > > ===> gnu/usr.bin/binutils/gdb > > cc -O -pipe -march=athlon -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -Dprint_insn_i386=print_insn_i386_att -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb.291/gdb/config -DFREEBSD_ELF -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c init.c > > cc1: warnings being treated as errors > > Known problem. I read this list everyday. I did not recall seeing this particular failure mentioned, so I thought I'd report it. > Warnings are treated as errors. Since GCC 3.1 has brought a hell of a > lot more warnings with us, you should use -DNO_WERROR until the dust > of the GCC 3.1 import settles down. If everyone is using -DNO_WERROR, then who would report build problems :-). -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:23:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 5B4B337B413 for ; Sat, 18 May 2002 20:23:33 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J3NNQJ005089; Sun, 19 May 2002 06:23:24 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J3NNIu016102; Sun, 19 May 2002 06:23:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J3NMv1016101; Sun, 19 May 2002 06:23:22 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 06:23:22 +0300 From: Giorgos Keramidas To: "Benjamin P. Grubin" Cc: current@FreeBSD.ORG Subject: Re: mergemaster(8) broken -- uses Perl Message-ID: <20020519032321.GA15987@hades.hell.gr> References: <20020519022922.GA10039@hades.hell.gr> <000301c1fee2$dc221650$080aa8c0@VINZCLORTHO> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000301c1fee2$dc221650$080aa8c0@VINZCLORTHO> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-18 23:11, Benjamin P. Grubin wrote: > Giorgos Keramidas wrote: > > > > [ The above should print in stdout just 01777 as a number. ] > > ... > > Does anyone know of any other (possibly more elegant way) of > > reading the numeric value of the permission bits for a file? > > Is [t]csh's `filetest` builtin viable here? Ah, very good hint. Unfortunately even with -P: I can't get the `special' bits like sticky, etc. as I can see: $ /bin/tcsh -c 'filetest -P: /tmp' 0777 and mergemaster.sh uses this as an argument to `install -m num' to set the mode of installed files :-/ - Giorgos [ That was a VERY good hint, BTW. I didn't know about `filetest' and it seems a rather useful feature of tcsh. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:25:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 758DF37B40A for ; Sat, 18 May 2002 20:25:27 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J3PPQJ005697; Sun, 19 May 2002 06:25:25 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J3POIu016127; Sun, 19 May 2002 06:25:24 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J3PNhI016126; Sun, 19 May 2002 06:25:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 06:25:22 +0300 From: Giorgos Keramidas To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: gdb breaks world Message-ID: <20020519032522.GB15987@hades.hell.gr> References: <20020518125604.A72462@troutmask.apl.washington.edu> <20020519023108.GB10039@hades.hell.gr> <20020518201215.A74579@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020518201215.A74579@troutmask.apl.washington.edu> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-18 20:12, Steve Kargl wrote: > On Sun, May 19, 2002 at 05:31:08AM +0300, Giorgos Keramidas wrote: > > Warnings are treated as errors. Since GCC 3.1 has brought a hell > > of a lot more warnings with us, you should use -DNO_WERROR until > > the dust of the GCC 3.1 import settles down. > > If everyone is using -DNO_WERROR, then who would report build > problems :-). True. I mentioned -DNO_WERROR to help you complete the buildworld. If you can help with those warnings, then I'm sure David O'Brien will be very glad to see patches ;-) -- Giorgos Keramidas - http://www.FreeBSD.org keramida@FreeBSD.org - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:36: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6CC7C37B40F; Sat, 18 May 2002 20:35:56 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4J3ZtU46246; Sat, 18 May 2002 21:35:55 -0600 (MDT) (envelope-from ken) Date: Sat, 18 May 2002 21:35:55 -0600 From: "Kenneth D. Merry" To: John Baldwin Cc: net@FreeBSD.org, current@FreeBSD.org, Alfred Perlstein Subject: Re: new zero copy sockets patches available Message-ID: <20020518213555.A46216@panzer.kdm.org> References: <20020518003046.A36510@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jhb@FreeBSD.org on Sat, May 18, 2002 at 09:03:38AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, May 18, 2002 at 09:03:38 -0400, John Baldwin wrote: > > On 18-May-2002 Kenneth D. Merry wrote: > > On Fri, May 17, 2002 at 23:02:55 -0700, Alfred Perlstein wrote: > >> * Kenneth D. Merry [020517 22:40] wrote: > >> > > >> > I have released a new set of zero copy sockets patches, against -current > >> > from today (May 17th, 2002). > >> > > >> > The main change is to deal with the vfs_ioopt changes that Alan Cox made > >> > in > >> > kern_subr.c. (They conflicted a bit with the zero copy receive code.) > >> > > >> > The patches and the FAQ are available here: > >> > > >> > http://people.freebsd.org/~ken/zero_copy/ > >> > > >> > Comments, questions and reviews are all welcome! > >> > >> jumbo_vm_init() has a bunch of bugs > >> > >> first it doesn't work right if called concurrently. > >> you need to protect the initialization of jumbo_vm_object otherwise > >> bad things can happen. my suggestion is to store the results of > >> vm_object_allocate into a temporary, grab the mutex and then check > >> to see if jumbo_vm_object has been initialized again if it has then > >> free the object, otherwise store the allocated object into the > >> global and continue. > > > > The problem here is that the mutex needs to be initialized before I can > > acquire it, and there's going to be a race between checking to see > > whether it has been initialized and actually initializing it. > > > > e.g.: > > > > if (!mtx_initialized(&jumbo_mutex)) > > mtx_init(&jumbo_mutex, "jumbo mutex", NULL, MTX_DEF); > > > > mtx_lock(&jumbo_mutex); > > > > if (jumbo_vm_object != NULL) { > > mtx_unlock(&jumbo_mutex); > > return (1); > > } > > > > /* allocate our object */ > > jumbo_vm_object = vm_object_allocate(OBJT_DEFAULT, JUMBO_MAX_PAGES); > > > > The above would work, I think, if it weren't for the race in the mutex > > initialization, and assuming I can allocate a vm object while holding > > the jumbo mutex. > > > > Suggestions? > > Either use a sysinit or something gross like this: > > static int jumbo_init = 0; > > ... > while (jumbo_init != 2) { > if (atomic_cmpset_acq_int(&jumbo_init, 0, 1) { > mtx_init(&jumbo_mutex, "jumbo_mutex", NULL, MTX_DEF); > atomic_store_rel_int(&jumbo_init, 2); > } > } > > mtx_lock(&jumbo_mutex); > > ... > > a sysinit is probably best though. Sounds like a sysinit is probably the way to go. I'll give it a try, thanks! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:39:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 30E8137B400; Sat, 18 May 2002 20:39:30 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4J3dKe46299; Sat, 18 May 2002 21:39:20 -0600 (MDT) (envelope-from ken) Date: Sat, 18 May 2002 21:39:20 -0600 From: "Kenneth D. Merry" To: Andrew Gallatin Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available Message-ID: <20020518213920.B46216@panzer.kdm.org> References: <20020517233950.A36169@panzer.kdm.org> <15590.35689.201153.550505@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <15590.35689.201153.550505@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Sat, May 18, 2002 at 01:12:09PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, May 18, 2002 at 13:12:09 -0400, Andrew Gallatin wrote: > > Kenneth D. Merry writes: > > > > I have released a new set of zero copy sockets patches, against -current > > from today (May 17th, 2002). > > > > The main change is to deal with the vfs_ioopt changes that Alan Cox made in > > kern_subr.c. (They conflicted a bit with the zero copy receive code.) > > > > The patches and the FAQ are available here: > > > > http://people.freebsd.org/~ken/zero_copy/ > > > > Comments, questions and reviews are all welcome! > > > > Hi Ken, > > I'm glad to see that you're still maintining this! > > Assuming the mutex issues get sorted out, what do you think the odds > are of getting this into the tree? The only possible issue I see is > with the tigon firmware. Is the firmware you're using of the same > vintage as what's in the tree now? Does it contain all the same > fixes? I think the odds of getting into the tree are pretty good. I certainly plan to give it a shot. The firmware is basically identical to what we currently have in the tree (12.4.11 plus some fixes Bill Paul picked out from 12.4.13), plus the header splitting patches. There have been some newer firmware releases, up to 12.4.18 I think, but I haven't yet been able to get anything from 3Com. I know 12.4.18 at least fixes some checksum offloading issues in a few strange cases. > Thanks again for keeping this alive, > > Drew Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:45:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C82B137B40B; Sat, 18 May 2002 20:45:20 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4J3j9m46348; Sat, 18 May 2002 21:45:09 -0600 (MDT) (envelope-from ken) Date: Sat, 18 May 2002 21:45:09 -0600 From: "Kenneth D. Merry" To: Don Bowman Cc: "'Andrew Gallatin'" , current@FreeBSD.org, net@FreeBSD.org Subject: Re: new zero copy sockets patches available Message-ID: <20020518214509.C46216@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from don@sandvine.com on Sat, May 18, 2002 at 01:15:43PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, May 18, 2002 at 13:15:43 -0400, Don Bowman wrote: > > Andrew Gallatin writes: > >> Kenneth D. Merry writes: > >> > > >> > I have released a new set of zero copy sockets patches, against > -current > >> > from today (May 17th, 2002). > > > > Hi Ken, > > > > I'm glad to see that you're still maintining this! > > > > Assuming the mutex issues get sorted out, what do you think the odds > > are of getting this into the tree? The only possible issue I see is > > with the tigon firmware. Is the firmware you're using of the same > > vintage as what's in the tree now? Does it contain all the same > > fixes? > > As a related question, will this work with the broadcom gigabit (bge) > driver, which is the Tigon III? If not, what would it take to get > it working? Unfortunately, it won't work with the Tigon III. If you can get firmware source for the Tigon III, I can probably get header splitting working. (The only way it wouldn't work is if they've offloaded most of the packet processing into the hardware.) The send side code will work on any NIC, and you can kludge up special case header splitting on the receive side if the NIC allows you to break jumbo frames into multiple chunks of data. (This is what Drew originally did for the Tigon II -- you just size the initial chunk of data so that it'll just hold the ethernet header, IP header, TCP header and TCP options, and the payload will "magically" end up page aligned. This doesn't work for protocols other than TCP, and it won't work if your TCP header changes in length.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 20:46:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.deltanet.com (mail.deltanet.com [216.237.144.132]) by hub.freebsd.org (Postfix) with ESMTP id 0443F37B407; Sat, 18 May 2002 20:46:43 -0700 (PDT) Received: from mammoth.eat.frenchfries.net (da001d0308.lax-ca.osd.concentric.net [64.0.145.53]) by mail.deltanet.com (8.11.6/8.11.6) with ESMTP id g4J3PqO31626; Sat, 18 May 2002 20:25:54 -0700 Received: by mammoth.eat.frenchfries.net (Postfix, from userid 1000) id F18444DDB; Sat, 18 May 2002 20:45:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mammoth.eat.frenchfries.net (Postfix) with ESMTP id E54B149CA; Sat, 18 May 2002 20:45:15 -0700 (PDT) Date: Sat, 18 May 2002 20:45:15 -0700 (PDT) From: Paul Herman X-X-Sender: pherman@mammoth.eat.frenchfries.net To: Giorgos Keramidas Cc: "Benjamin P. Grubin" , Subject: Re: mergemaster(8) broken -- uses Perl In-Reply-To: <20020519032321.GA15987@hades.hell.gr> Message-ID: <20020518203835.W923-100000@mammoth.eat.frenchfries.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 19 May 2002, Giorgos Keramidas wrote: > On 2002-05-18 23:11, Benjamin P. Grubin wrote: > > Giorgos Keramidas wrote: > > > > > > [ The above should print in stdout just 01777 as a number. ] > > > ... > > > Does anyone know of any other (possibly more elegant way) of > > > reading the numeric value of the permission bits for a file? Hmmm, it's ugly but perhaps not as ugly: bash$ fstat -n /kernel < /kernel | grep -v PID pherman fstat 942 0 116,196608 235 100555 4114305 r /kernel (the 100555). The bad side is that you'd have to do a little trickery to catch the correct process. It'd probably be better just to add an option to fstat to display /usr/ports/sysutils/stat type info... -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 21: 5: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id 1B16537B406 for ; Sat, 18 May 2002 21:04:59 -0700 (PDT) Received: (qmail 19234 invoked from network); 19 May 2002 04:04:58 -0000 Received: from unknown (HELO VINZCLORTHO) ([66.92.70.186]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 19 May 2002 04:04:58 -0000 From: "Benjamin P. Grubin" To: "'Paul Herman'" , "'Giorgos Keramidas'" Cc: Subject: RE: mergemaster(8) broken -- uses Perl Date: Sun, 19 May 2002 00:04:56 -0400 Message-ID: <002e01c1feea$599cb890$080aa8c0@VINZCLORTHO> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20020518203835.W923-100000@mammoth.eat.frenchfries.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear god, you guys really like hurting yourselves. If filetest doesn't do it, why not just something on the order of: #include #include main (argc, argv) int argc; char *argv[]; { struct stat stbuf; if (!stat(argv[1], &stbuf)) printf("%o\n", stbuf.st_mode); else printf("error: stat failed\n"); } Cheers, Ben > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG] On Behalf Of Paul Herman > Sent: Saturday, May 18, 2002 11:45 PM > To: Giorgos Keramidas > Cc: Benjamin P. Grubin; current@FreeBSD.ORG > Subject: Re: mergemaster(8) broken -- uses Perl > > > On Sun, 19 May 2002, Giorgos Keramidas wrote: > > > On 2002-05-18 23:11, Benjamin P. Grubin wrote: > > > Giorgos Keramidas wrote: > > > > > > > > [ The above should print in stdout just 01777 as a number. ] > > > > ... > > > > Does anyone know of any other (possibly more elegant way) of > > > > reading the numeric value of the permission bits for a file? > > Hmmm, it's ugly but perhaps not as ugly: > > bash$ fstat -n /kernel < /kernel | grep -v PID > pherman fstat 942 0 116,196608 235 100555 > 4114305 r /kernel > > (the 100555). The bad side is that you'd have to do a little > trickery to catch the correct process. It'd probably be better > just to add an option to fstat to display /usr/ports/sysutils/stat > type info... > > -Paul. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 21: 9: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id CC18137B40A for ; Sat, 18 May 2002 21:08:59 -0700 (PDT) Received: from hades.hell.gr (patr530-b181.otenet.gr [212.205.244.189]) by mailsrv.otenet.gr (8.12.3/8.12.3) with ESMTP id g4J48qQJ020893; Sun, 19 May 2002 07:08:53 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.3/8.12.3) with ESMTP id g4J48oIu030491; Sun, 19 May 2002 07:08:50 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.3/8.12.3/Submit) id g4J48mBa030485; Sun, 19 May 2002 07:08:48 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 19 May 2002 07:08:47 +0300 From: Giorgos Keramidas To: "Benjamin P. Grubin" Cc: "'Paul Herman'" , current@FreeBSD.ORG Subject: Re: mergemaster(8) broken -- uses Perl Message-ID: <20020519040846.GA30448@hades.hell.gr> References: <20020518203835.W923-100000@mammoth.eat.frenchfries.net> <002e01c1feea$599cb890$080aa8c0@VINZCLORTHO> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002e01c1feea$599cb890$080aa8c0@VINZCLORTHO> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-05-19 00:04, Benjamin P. Grubin wrote: > Dear god, you guys really like hurting yourselves. > > If filetest doesn't do it, why not just something on the order of: > > #include > #include I was looking for a scriptable version of exactly this :) -- Giorgos Keramidas - http://www.FreeBSD.org keramida@FreeBSD.org - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 21:54:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from ref5.freebsd.org (ref5.FreeBSD.org [216.136.204.102]) by hub.freebsd.org (Postfix) with ESMTP id 1736437B407 for ; Sat, 18 May 2002 21:54:45 -0700 (PDT) Received: from ref5.freebsd.org (localhost [127.0.0.1]) by ref5.freebsd.org (8.12.2/8.12.2) with ESMTP id g4J4siuH070590 for ; Sat, 18 May 2002 21:54:44 -0700 (PDT) (envelope-from des@ref5.freebsd.org) Received: (from des@localhost) by ref5.freebsd.org (8.12.2/8.12.2/Submit) id g4J4sikj070583 for current@freebsd.org; Sat, 18 May 2002 21:54:44 -0700 (PDT) Date: Sat, 18 May 2002 21:54:44 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200205190454.g4J4sikj070583@ref5.freebsd.org> To: current@freebsd.org Subject: i386 tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- >>> stage 2: cleaning up the object tree -------------------------------------------------------------- >>> stage 2: rebuilding the object tree -------------------------------------------------------------- >>> stage 2: build tools -------------------------------------------------------------- >>> stage 3: cross tools -------------------------------------------------------------- >>> stage 4: populating /tmp/des/obj/i386/d/home/des/tinderbox/src/i386/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> usr.bin/unexpand ... Patching file inc-hist.texi using Plan A... Hunk #1 succeeded at 26. Hunk #2 succeeded at 39. done /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/gdb.texinfo:4647: warning: unlikely character , in @var. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/gdb.texinfo:5284: warning: @sc argument all uppercase, thus no effect. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/gdb.texinfo:6531: warning: @sc argument all uppercase, thus no effect. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/gdbint.texinfo:1026: warning: @sc argument all uppercase, thus no effect. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:875: warning: `.' or `,' must follow cross reference, not f. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:2040: warning: unlikely character , in @var. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:2040: warning: unlikely character , in @var. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:2139: warning: unlikely character , in @var. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:2139: warning: unlikely character , in @var. /d/home/des/tinderbox/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb.291/gdb/doc/stabs.texinfo:3373: warning: `.' or `,' must follow cross reference, not @. ===> gnu/usr.bin/binutils/gdb cc1: warnings being treated as errors init.c:3: warning: function declaration isn't a prototype init.c: In function `initialize_all_files': init.c:4: warning: function declaration isn't a prototype init.c:5: warning: function declaration isn't a prototype init.c:6: warning: function declaration isn't a prototype init.c:7: warning: function declaration isn't a prototype init.c:8: warning: function declaration isn't a prototype init.c:9: warning: function declaration isn't a prototype init.c:10: warning: function declaration isn't a prototype init.c:11: warning: function declaration isn't a prototype init.c:12: warning: function declaration isn't a prototype init.c:13: warning: function declaration isn't a prototype init.c:14: warning: function declaration isn't a prototype init.c:15: warning: function declaration isn't a prototype init.c:16: warning: function declaration isn't a prototype init.c:17: warning: function declaration isn't a prototype init.c:18: warning: function declaration isn't a prototype init.c:19: warning: function declaration isn't a prototype init.c:20: warning: function declaration isn't a prototype init.c:21: warning: function declaration isn't a prototype init.c:22: warning: function declaration isn't a prototype init.c:23: warning: function declaration isn't a prototype init.c:24: warning: function declaration isn't a prototype init.c:25: warning: function declaration isn't a prototype init.c:26: warning: function declaration isn't a prototype init.c:27: warning: function declaration isn't a prototype init.c:28: warning: function declaration isn't a prototype init.c:29: warning: function declaration isn't a prototype init.c:30: warning: function declaration isn't a prototype init.c:31: warning: function declaration isn't a prototype init.c:32: warning: function declaration isn't a prototype init.c:33: warning: function declaration isn't a prototype init.c:34: warning: function declaration isn't a prototype init.c:35: warning: function declaration isn't a prototype init.c:36: warning: function declaration isn't a prototype init.c:37: warning: function declaration isn't a prototype init.c:38: warning: function declaration isn't a prototype init.c:39: warning: function declaration isn't a prototype init.c:40: warning: function declaration isn't a prototype init.c:41: warning: function declaration isn't a prototype init.c:42: warning: function declaration isn't a prototype init.c:43: warning: function declaration isn't a prototype init.c:44: warning: function declaration isn't a prototype init.c:45: warning: function declaration isn't a prototype init.c:46: warning: function declaration isn't a prototype init.c:47: warning: function declaration isn't a prototype init.c:48: warning: function declaration isn't a prototype init.c:49: warning: function declaration isn't a prototype init.c:50: warning: function declaration isn't a prototype init.c:51: warning: function declaration isn't a prototype init.c:52: warning: function declaration isn't a prototype init.c:53: warning: function declaration isn't a prototype init.c:54: warning: function declaration isn't a prototype init.c:55: warning: function declaration isn't a prototype init.c:56: warning: function declaration isn't a prototype init.c:57: warning: function declaration isn't a prototype init.c:58: warning: function declaration isn't a prototype init.c:59: warning: function declaration isn't a prototype init.c:60: warning: function declaration isn't a prototype init.c:61: warning: function declaration isn't a prototype init.c:62: warning: function declaration isn't a prototype init.c:63: warning: function declaration isn't a prototype init.c:64: warning: function declaration isn't a prototype *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin/binutils/gdb. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 23: 1:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from turbine.trit.org (turbine.trit.org [63.198.170.141]) by hub.freebsd.org (Postfix) with ESMTP id 9A41837B401; Sat, 18 May 2002 23:01:35 -0700 (PDT) Received: from turbine.trit.org (localhost [127.0.0.1]) by turbine.trit.org (Postfix) with ESMTP id AF15F3E1A; Sun, 19 May 2002 06:01:34 +0000 (UTC) To: Giorgos Keramidas Cc: current@FreeBSD.ORG Subject: Re: mergemaster(8) broken -- uses Perl In-Reply-To: <20020519022922.GA10039@hades.hell.gr>; from keramida@FreeBSD.ORG on "Sun, 19 May 2002 05:29:22 +0300" Date: Sun, 19 May 2002 06:01:34 +0000 From: Dima Dorfman Message-Id: <20020519060134.AF15F3E1A@turbine.trit.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Giorgos Keramidas wrote: > On 2002-05-18 11:54, David O'Brien wrote: > > Anyone got a patch? > > Part of the problems I had when I tried to replace perl in > mergemaster.sh with something `native' was that the perl code uses > stat(2) to obtain the permission bits of a directory/file and I can't > think of a way to do this with tools in the base system without > resorting to ugly awk scripts that parse and translate ls(1) output. How about fixing ls(1) to output the numeric mode if asked to? E.g., instead of > % /bin/ls -ld /tmp | sed -e 's/[[:space:]].*$//' |\ > awk -v mode=0 '{ >[...] /bin/ls -ldN /tmp | awk '{ print $1 }' A proof-of-concept (i.e., not polished or fully-tested (in particular, it lacks a manual page update)) patch to implement ls -N is attached below. I've wanted this feature a number of times in the past, but never had occasion to actually implement it until now. Note also that if this is used in mergemaster, we need to deal with the issue of what to do if mergemaster is run on a system that doesn't have this option yet (perhaps try it first, and fall back to Perl (which should exist on systems without ls -N) if it doesn't work?). Index: ls.c =================================================================== RCS file: /ref/cvsf/src/bin/ls/ls.c,v retrieving revision 1.56 diff -u -r1.56 ls.c --- ls.c 19 Feb 2002 00:05:50 -0000 1.56 +++ ls.c 19 May 2002 05:49:53 -0000 @@ -106,6 +106,7 @@ static int f_nosort; /* don't sort output */ int f_notabs; /* don't use tab-separated multi-col output */ static int f_numericonly; /* don't convert uid/gid to name */ + int f_numeric_mode; /* don't convert file modes to a string */ int f_octal; /* show unprintables as \xxx */ int f_octal_escape; /* like f_octal but use C escapes if possible */ static int f_recursive; /* ls subdirectories also */ @@ -167,7 +168,7 @@ f_listdot = 1; fts_options = FTS_PHYSICAL; - while ((ch = getopt(argc, argv, "1ABCFGHLPRTWZabcdfghiklnoqrstuw")) != -1) { + while ((ch = getopt(argc, argv, "1ABCFGHLNPRTWZabcdfghiklnoqrstuw")) != -1) { switch (ch) { /* * The -1, -C and -l options all override each other so shell @@ -246,6 +247,9 @@ break; case 'n': f_numericonly = 1; + break; + case 'N': + f_numeric_mode = 1; break; case 'o': f_flags = 1; Index: ls.h =================================================================== RCS file: /ref/cvsf/src/bin/ls/ls.h,v retrieving revision 1.17 diff -u -r1.17 ls.h --- ls.h 3 Feb 2002 19:11:32 -0000 1.17 +++ ls.h 19 May 2002 05:49:07 -0000 @@ -48,6 +48,7 @@ extern int f_lomac; /* show LOMAC attributes */ extern int f_inode; /* print inode */ extern int f_longform; /* long listing format */ +extern int f_numeric_mode; /* don't convert file modes to a string */ extern int f_octal; /* print unprintables in octal */ extern int f_octal_escape; /* like f_octal but use C escapes if possible */ extern int f_nonprint; /* show unprintables as ? */ Index: print.c =================================================================== RCS file: /ref/cvsf/src/bin/ls/print.c,v retrieving revision 1.53 diff -u -r1.53 print.c --- print.c 25 Feb 2002 01:36:59 -0000 1.53 +++ print.c 19 May 2002 05:49:30 -0000 @@ -177,7 +177,10 @@ if (f_size) (void)printf("%*lld ", dp->s_block, howmany(sp->st_blocks, blocksize)); - strmode(sp->st_mode, buf); + if (f_numeric_mode) + snprintf(buf, sizeof(buf), "%.6o", sp->st_mode); + else + strmode(sp->st_mode, buf); np = p->fts_pointer; (void)printf("%s %*u %-*s %-*s ", buf, dp->s_nlink, sp->st_nlink, dp->s_user, np->user, dp->s_group, Index: util.c =================================================================== RCS file: /ref/cvsf/src/bin/ls/util.c,v retrieving revision 1.29 diff -u -r1.29 util.c --- util.c 28 Feb 2002 18:52:47 -0000 1.29 +++ util.c 19 May 2002 05:50:08 -0000 @@ -158,9 +158,9 @@ { (void)fprintf(stderr, #ifdef COLORLS - "usage: ls [-ABCFGHLPRTWZabcdfghiklnoqrstu1]" + "usage: ls [-ABCFGHLNPRTWZabcdfghiklnoqrstu1]" #else - "usage: ls [-ABCFHLPRTWZabcdfghiklnoqrstu1]" + "usage: ls [-ABCFHLNPRTWZabcdfghiklnoqrstu1]" #endif " [file ...]\n"); exit(1); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 23:20:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.deltanet.com (mail.deltanet.com [216.237.144.132]) by hub.freebsd.org (Postfix) with ESMTP id BEF9B37B405; Sat, 18 May 2002 23:20:10 -0700 (PDT) Received: from mammoth.eat.frenchfries.net (da001d0251.lax-ca.osd.concentric.net [64.0.144.252]) by mail.deltanet.com (8.11.6/8.11.6) with ESMTP id g4J5xQO28999; Sat, 18 May 2002 22:59:27 -0700 Received: by mammoth.eat.frenchfries.net (Postfix, from userid 1000) id 4E99E50F1; Sat, 18 May 2002 23:20:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mammoth.eat.frenchfries.net (Postfix) with ESMTP id 4C08A50E8; Sat, 18 May 2002 23:20:07 -0700 (PDT) Date: Sat, 18 May 2002 23:20:07 -0700 (PDT) From: Paul Herman X-X-Sender: pherman@mammoth.eat.frenchfries.net To: Dima Dorfman Cc: Giorgos Keramidas , Subject: Re: mergemaster(8) broken -- uses Perl In-Reply-To: <20020519060134.AF15F3E1A@turbine.trit.org> Message-ID: <20020518231328.W1980-100000@mammoth.eat.frenchfries.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 19 May 2002, Dima Dorfman wrote: > How about fixing ls(1) to output the numeric mode if asked to? That's good, but while you're at it you'd probably want to get *everything* out of (struct stat) and print it numerically (device, flags, atime since epoch, etc.) You could do this in ls(1), but I'll have a patch for fstat(1) soon (working on it) that gives you: bash$ /usr/obj/usr/src/usr.bin/fstat/fstat -s /tmp /kernel INODE DEV SIZE BLOCKS MODE FLAGS LNK UID GID ATIME MTIME CTIME NAME 235 226304 4114305 8096 100555 400000 1 0 0 1021779222 1021740354 1021740354 /kernel 56651 226304 512 4 041777 000000 6 0 0 1021787523 1021787657 1021787657 /tmp so you can parse it however you like. Either way, ls(1) or fstat(1), as long as you can get the info you need. :-) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 23:26:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from turbine.trit.org (turbine.trit.org [63.198.170.141]) by hub.freebsd.org (Postfix) with ESMTP id 245B137B40A; Sat, 18 May 2002 23:26:39 -0700 (PDT) Received: from turbine.trit.org (localhost [127.0.0.1]) by turbine.trit.org (Postfix) with ESMTP id 04B153E1A; Sun, 19 May 2002 06:26:12 +0000 (UTC) To: Paul Herman Cc: Giorgos Keramidas , current@FreeBSD.ORG Subject: Re: mergemaster(8) broken -- uses Perl In-Reply-To: <20020518231328.W1980-100000@mammoth.eat.frenchfries.net>; from pherman@frenchfries.net on "Sat, 18 May 2002 23:20:07 -0700 (PDT)" Date: Sun, 19 May 2002 06:26:12 +0000 From: Dima Dorfman Message-Id: <20020519062613.04B153E1A@turbine.trit.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Paul Herman wrote: > On Sun, 19 May 2002, Dima Dorfman wrote: > > > How about fixing ls(1) to output the numeric mode if asked to? > > That's good, but while you're at it you'd probably want to get > *everything* out of (struct stat) and print it numerically (device, > flags, atime since epoch, etc.) You could do this in ls(1), but > I'll have a patch for fstat(1) soon (working on it) that gives you: > > bash$ /usr/obj/usr/src/usr.bin/fstat/fstat -s /tmp /kernel > INODE DEV SIZE BLOCKS MODE FLAGS LNK UID GID ATIME MTIME CTIME NAME > 235 226304 4114305 8096 100555 400000 1 0 0 1021779222 10217403541021740354 /kernel > 56651 226304 512 4 041777 000000 6 0 0 1021787523 10217876571021787657 /tmp > > so you can parse it however you like. Either way, ls(1) or > fstat(1), as long as you can get the info you need. :-) This looks much better than my extention. I look forward to seeing this get into the tree. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 18 23:42:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 5100337B403 for ; Sat, 18 May 2002 23:42:38 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g4J6gc9Q076067 for ; Sat, 18 May 2002 23:42:38 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g4J6gbiC076066 for freebsd-current@freebsd.org; Sat, 18 May 2002 23:42:37 -0700 (PDT) Date: Sat, 18 May 2002 23:42:37 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: [PATCH] fixed buildworld in absences of src/games Message-ID: <20020518234237.A76042@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If you don't have src/games, the "make buildworld" dies without the following patch. -- Steve --- share/doc/usd/30.rogue/Makefile.orig Sat May 18 21:29:07 2002 +++ share/doc/usd/30.rogue/Makefile Sat May 18 22:50:21 2002 @@ -10,5 +10,5 @@ .include .else -all clean cleandepend cleandir depend distribute install obj: +all clean cleandepend cleandir depend includes buildincludes installincludes distribute install obj: .endif --- share/doc/usd/31.trek/Makefile.orig Sat May 18 21:30:12 2002 +++ share/doc/usd/31.trek/Makefile Sat May 18 22:50:46 2002 @@ -10,5 +10,5 @@ .include .else -all clean cleandepend cleandir depend distribute install obj: +all clean cleandepend cleandir depend includes buildincludes installincludes distribute install obj: .endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message