From owner-freebsd-current Sun Jun 30 0:45:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B85CB37B401; Sun, 30 Jun 2002 00:45:45 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECFE043E09; Sun, 30 Jun 2002 00:45:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g5U7hX6I038221; Sun, 30 Jun 2002 09:43:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Juli Mallett Cc: Garance A Drosihn , audit@FreeBSD.ORG, current@FreeBSD.ORG, Kirk McKusick Subject: Re: libufs, a library for dealing with UFS from userland. In-Reply-To: Your message of "Sat, 29 Jun 2002 20:36:42 PDT." <20020629203642.A9605@FreeBSD.ORG> Date: Sun, 30 Jun 2002 09:43:33 +0200 Message-ID: <38220.1025423013@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 <20020629203642.A9605@FreeBSD.ORG>, Juli Mallett writes: >* Garance A Drosihn escriuréres >> At 5:37 AM -0700 6/29/02, Juli Mallett wrote: >> >I get identical output from dumpfs and libufs-dumpfs currently >> >and I can toggle softdep flags fine with tunefs. I'd like to >> >commit this by the coming Tuesday as I will be out of town >> >from Tuesday morning and will not have any way to further >> >work on this, etc. >> >> When do you get back into town? > >Unknown. We are in no rush on this, so just take your time. Feel free to take the precaution of email'ing me the code/patch so that I can take over if you fail to get back for a very long time. -- 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 Jun 30 1: 3: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F2F937B400 for ; Sun, 30 Jun 2002 01:03:03 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5C7C43E09 for ; Sun, 30 Jun 2002 01:03:02 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g5U830T4092904; Sun, 30 Jun 2002 01:03:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g5U830fr092903; Sun, 30 Jun 2002 01:03:00 -0700 (PDT) (envelope-from dillon) Date: Sun, 30 Jun 2002 01:03:00 -0700 (PDT) From: Matthew Dillon Message-Id: <200206300803.g5U830fr092903@apollo.backplane.com> To: Julian Elischer Cc: FreeBSD current users Subject: Re: I think KSE-MIII import complete References: 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 got the ithread_loop/setrunqueue panic again while building the world normally (no memory pressure). I'm too tired to deal with it tonight but tomorrow morning I'll attach a gdb and track it down. -Matt db> db> trace Debugger(c02ec1da) at Debugger+0x46 panic(c02ec7a9,c270b780,c270b780,c270b780,c01af9b0) at panic+0xd6 setrunqueue(c270b780) at setrunqueue+0x1dd cv_timedwait_end(c270b780) at cv_timedwait_end+0x36 softclock(0) at softclock+0x159 ithread_loop(c0ee0600,cd3dfd48,c0eefc00,c01b9bec,0) at ithread_loop+0x12c fork_exit(c01b9bec,c0ee0600,cd3dfd48) at fork_exit+0xa8 fork_trampoline() at fork_trampoline+0x37 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 1:20:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36C0B37B400 for ; Sun, 30 Jun 2002 01:20:11 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id A938443E09 for ; Sun, 30 Jun 2002 01:20:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630082009.MHNV29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 08:20:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id BAA84061; Sun, 30 Jun 2002 01:19:33 -0700 (PDT) Date: Sun, 30 Jun 2002 01:19:32 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: FreeBSD current users Subject: Re: I think KSE-MIII import complete In-Reply-To: <200206300803.g5U830fr092903@apollo.backplane.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 which panic message? the code here is still FULL of asserts. On Sun, 30 Jun 2002, Matthew Dillon wrote: > I got the ithread_loop/setrunqueue panic again while building the > world normally (no memory pressure). I'm too tired to deal with > it tonight but tomorrow morning I'll attach a gdb and track it down. > > -Matt > > db> > db> trace > Debugger(c02ec1da) at Debugger+0x46 > panic(c02ec7a9,c270b780,c270b780,c270b780,c01af9b0) at panic+0xd6 > setrunqueue(c270b780) at setrunqueue+0x1dd > cv_timedwait_end(c270b780) at cv_timedwait_end+0x36 > softclock(0) at softclock+0x159 > ithread_loop(c0ee0600,cd3dfd48,c0eefc00,c01b9bec,0) at ithread_loop+0x12c > fork_exit(c01b9bec,c0ee0600,cd3dfd48) at fork_exit+0xa8 > fork_trampoline() at fork_trampoline+0x37 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 1:36: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60BBA37B400 for ; Sun, 30 Jun 2002 01:35:54 -0700 (PDT) Received: from mx2.datanet.hu (mx2.datanet.hu [194.149.13.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B55343E13 for ; Sun, 30 Jun 2002 01:35:53 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-584.adsl.datanet.hu [195.56.50.76]) by mx2.datanet.hu (DataNet) with ESMTP id 2DC1A590F for ; Sun, 30 Jun 2002 10:35:51 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g5U8ZxgF019674 for ; Sun, 30 Jun 2002 10:35:59 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g5U8ZwZ0019673 for freebsd-current@FreeBSD.ORG; Sun, 30 Jun 2002 10:35:58 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sun, 30 Jun 2002 10:35:58 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: [PATCH] Re: Which .info files have been disabled? Message-ID: <20020630083557.GA852@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <20020628154933.GA1938@fonix.adamsfamily.xx> <20020629132919.GC883@fonix.adamsfamily.xx> <20020629103511.A10195@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: <20020629103511.A10195@dragon.nuxi.com> User-Agent: Mutt/1.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 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello everybody, Sorry for taking a tad long with this, here is the second patch set for the GDB info files. I implemented both of David's suggestions, so the third patch is no longer needed and GDBvn.texi can be safely cvs rm-d now, it is generated dynamically at build time. If you want to go all the way, you can change the name of inc-hist.texi.diff to inc-hist.texinfo.diff, but that involves a repo copy. Have a good weekend! -- Regards: Szilveszter ADAM Szombathely Hungary --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="binutils::doc::Makefile.diff" Index: Makefile =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//src/gnu/usr.bin/binutils/doc/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- Makefile 28 Jun 2002 03:41:56 -0000 1.11 +++ Makefile 30 Jun 2002 08:27:15 -0000 @@ -5,9 +5,9 @@ GDBDIR= ${.CURDIR}/../../../../contrib/gdb CONTRIBDIR= ${.CURDIR}/../../../../contrib -.PATH: ${SRCDIR}/gas/doc ${SRCDIR}/ld ${SRCDIR}/bfd/doc ${GDBDIR}/gdb/doc +.PATH: ${SRCDIR}/gas/doc ${SRCDIR}/ld ${SRCDIR}/bfd/doc ${GDBDIR}/gdb/doc ${GDBDIR}/gdb/mi -INFO = as ld annotate gasp stabs binutils +INFO = as ld annotate gasp gdb gdbint stabs binutils INFOSECTION= "Programming & development tools." INFOENTRY_as= "* As: (as). The GNU assembler." INFOENTRY_gasp= "* Gasp: (gasp). The GNU Assembler Macro Preprocessor." @@ -19,6 +19,7 @@ MAKEINFOFLAGS+= -I ${SRCDIR}/gas/doc -I ${SRCDIR}/ld -I ${SRCDIR}/bfd/doc MAKEINFOFLAGS+= -I ${SRCDIR}/binutils MAKEINFOFLAGS+= -I ${GDBDIR}/gdb/doc +MAKEINFOFLAGS+= -I ${GDBDIR}/gdb/mi MAKEINFOFLAGS+= -I ${CONTRIBDIR}/libreadline/doc CLEANFILES= gdb-cfg.texi inc-hist.texi inc-hist.texi.orig \ @@ -27,20 +28,26 @@ as.info: as.texinfo asconfig.texi c-i386.texi gasver.texi ld.info: ld.texinfo bfdsumm.texi ldver.texi -gdb.info: gdb.texinfo gdb-cfg.texi GDBvn.texi remote.texi \ - rluser.texinfo inc-hist.texi +gdb.info: gdb.texinfo gdb-cfg.texi GDBvn.texi annotate.texi \ + fdl.texi gpl.texi gdbmi.texinfo \ + rluser.texinfo inc-hist.texinfo +gdbint.info: gdbint.texinfo fdl.texi + gdb-cfg.texi: all-cfg.texi ln -sf ${.ALLSRC} ${.TARGET} +GDBvn.texi: ${GDBDIR}/gdb/version.in + echo "@set GDBVN `sed q ${.ALLSRC}`" > ${.TARGET} + .PATH: ${SRCDIR}/binutils binutils.info: binutils.texi config.texi gasver.texi ldver.texi: - echo "@set VERSION ${VERSION}" > ${.TARGET} + echo '"@set VERSION ${VERSION}"' > ${.TARGET} .PATH: ${CONTRIBDIR}/libreadline/doc -inc-hist.texi: hsuser.texinfo inc-hist.diff +inc-hist.texinfo: hsuser.texinfo inc-hist.diff cp ${.ALLSRC:M*.texinfo} ${.TARGET} patch -b .orig < ${.ALLSRC:M*.diff} --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="binutils::doc::inc-hist.diff.diff" Index: inc-hist.diff =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//src/gnu/usr.bin/binutils/doc/inc-hist.diff,v retrieving revision 1.3 diff -u -r1.3 inc-hist.diff --- inc-hist.diff 11 Apr 2001 04:27:10 -0000 1.3 +++ inc-hist.diff 29 Jun 2002 12:20:56 -0000 @@ -1,7 +1,7 @@ $FreeBSD: src/gnu/usr.bin/binutils/doc/inc-hist.diff,v 1.3 2001/04/11 04:27:10 ache Exp $ ---- inc-hist.texi.orig Wed Apr 11 08:20:01 2001 -+++ inc-hist.texi Wed Apr 11 08:21:57 2001 +--- inc-hist.texinfo.orig Wed Apr 11 08:20:01 2001 ++++ inc-hist.texinfo Wed Apr 11 08:21:57 2001 @@ -26,9 +26,9 @@ @node Using History Interactively @chapter Using History Interactively --HcAYCG3uE/tztfnV-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 1:40:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 593A137B400 for ; Sun, 30 Jun 2002 01:40:16 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD9B343E0A for ; Sun, 30 Jun 2002 01:40:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630084015.IOSO9178.rwcrmhc51.attbi.com@InterJet.elischer.org> for ; Sun, 30 Jun 2002 08:40:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id BAA84123 for ; Sun, 30 Jun 2002 01:32:17 -0700 (PDT) Date: Sun, 30 Jun 2002 01:32:17 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: KSE M-III status: 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 well afte a day I'm releatively happy.. there seem to be 4 bugs showing themselves.. plus one braino I just fixed.. (there was a bug where ps would panic the kernel when it got to a zombie process because it tried to print thread info but ther eis no thread). in addition the following problems have been noted: A machine doing REAL HEAVY work asn SWAPPING LIKE CRAZY eventually paniced. A machine has panic'd whendoing a killall during shutdown. this MAY be related to teh one above re: Zombies but it is not yet known. Matt triggered a panic we put into the code and thought we'd never see again.. I thought tomorrow was looking too empty.. I have one report that GNOME apps freeze and chew all cpu time.. (I'll bet it's signals.. I hate them) If this happens to you too let me know. At least we still seem to have basic functionality.. I'm off to bed.. see ya in 8 hours! Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 1:40:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5F3F37B400 for ; Sun, 30 Jun 2002 01:40:26 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDC7243E0A for ; Sun, 30 Jun 2002 01:40:25 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630084025.IOVD9178.rwcrmhc51.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 08:40:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id BAA84115; Sun, 30 Jun 2002 01:29:50 -0700 (PDT) Date: Sun, 30 Jun 2002 01:29:49 -0700 (PDT) From: Julian Elischer To: walt Cc: freebsd-current@freebsd.org Subject: Re: mozilla and gnome apps won't run after KSE [June 29] In-Reply-To: <3D1C6C98.2000908@hotmail.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 Ithink these may be threaded it's possible the are using signals and they may be broken.... On Fri, 28 Jun 2002, walt wrote: > Following make world && make kernel after the KSE update > I find that mozilla and any gnome app will suck up 98% > of the CPU and will never actually write anything to > the display. No crashes, no error messages, they > just chew up cycles. > > I don't have KDE installed on my -current machine, > so I can't comment on it, but most other basic X apps > seem to work fine--like xterm, xvidtune, the X > interface to emacs and the X interface for cvsup > all work OK. > > Any one else seeing this? > > > 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 Jun 30 2:12:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 758BD37B401 for ; Sun, 30 Jun 2002 02:12:48 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D36FF43E09 for ; Sun, 30 Jun 2002 02:12:46 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 5791 invoked by uid 0); 30 Jun 2002 09:12:45 -0000 Received: from pd950a5d3.dip.t-dialin.net (HELO gmx.net) (217.80.165.211) by mail.gmx.net (mp008-rz3) with SMTP; 30 Jun 2002 09:12:45 -0000 Message-ID: <3D1ECB85.7010809@gmx.net> Date: Sun, 30 Jun 2002 11:12:37 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: buildworld errors X-Enigmail-Version: 0.61.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA95B79FCB392D14AE75BA411" 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 The following is an OpenPGP/MIME signed message created by Enigmail/Mozilla, following RFC 2440 and RFC 2015 --------------enigA95B79FCB392D14AE75BA411 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit - One in usr.bin/gcore/gcore.c (open #ifndef, lost the errorlog, commit-accident?) - Another: cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /usr/src/lib/libkvm/kvm_proc.c:271: invalid operands to binary != /usr/src/lib/libkvm/kvm_proc.c:310: invalid operands to binary != /usr/src/lib/libkvm/kvm_proc.c:324: invalid operands to binary != *** Error code 1 Stop in /usr/src/lib/libkvm. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish --------------enigA95B79FCB392D14AE75BA411 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9HsuKXhc68WspdLARAjJiAKCTEh0mG+bKiq0EM6OIYctsky2btgCffZJR ayO6SDCcAwWJIQ7rCHFmWAE= =BcOh -----END PGP SIGNATURE----- --------------enigA95B79FCB392D14AE75BA411-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 2:15:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A8C237B401 for ; Sun, 30 Jun 2002 02:15:05 -0700 (PDT) Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F4B643E0A for ; Sun, 30 Jun 2002 02:15:04 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-584.adsl.datanet.hu [195.56.50.76]) by mx1.datanet.hu (DataNet) with ESMTP id 2C28126A972 for ; Sun, 30 Jun 2002 11:15:01 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g5U9FAgF025650 for ; Sun, 30 Jun 2002 11:15:10 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g5U9F93j025649 for freebsd-current@FreeBSD.ORG; Sun, 30 Jun 2002 11:15:09 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sun, 30 Jun 2002 11:15:09 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: [PATCH] Re: Which .info files have been disabled? Message-ID: <20020630091509.GB852@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <20020628154933.GA1938@fonix.adamsfamily.xx> <20020629132919.GC883@fonix.adamsfamily.xx> <20020629103511.A10195@dragon.nuxi.com> <20020630083557.GA852@fonix.adamsfamily.xx> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="98e8jtXdkpgskNou" Content-Disposition: inline In-Reply-To: <20020630083557.GA852@fonix.adamsfamily.xx> User-Agent: Mutt/1.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 --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Grrr, hit me baby one more time. One of the diffs included a completely gratuitous one-line change which I made yesterday night while I was tired and neglected to correct today. So, the patchset again. (Take three!) -- Regards: Szilveszter ADAM Szombathely Hungary --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="binutils::doc::Makefile.diff" Index: Makefile =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//src/gnu/usr.bin/binutils/doc/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- Makefile 28 Jun 2002 03:41:56 -0000 1.11 +++ Makefile 30 Jun 2002 09:11:34 -0000 @@ -5,9 +5,9 @@ GDBDIR= ${.CURDIR}/../../../../contrib/gdb CONTRIBDIR= ${.CURDIR}/../../../../contrib -.PATH: ${SRCDIR}/gas/doc ${SRCDIR}/ld ${SRCDIR}/bfd/doc ${GDBDIR}/gdb/doc +.PATH: ${SRCDIR}/gas/doc ${SRCDIR}/ld ${SRCDIR}/bfd/doc ${GDBDIR}/gdb/doc ${GDBDIR}/gdb/mi -INFO = as ld annotate gasp stabs binutils +INFO = as ld annotate gasp gdb gdbint stabs binutils INFOSECTION= "Programming & development tools." INFOENTRY_as= "* As: (as). The GNU assembler." INFOENTRY_gasp= "* Gasp: (gasp). The GNU Assembler Macro Preprocessor." @@ -19,6 +19,7 @@ MAKEINFOFLAGS+= -I ${SRCDIR}/gas/doc -I ${SRCDIR}/ld -I ${SRCDIR}/bfd/doc MAKEINFOFLAGS+= -I ${SRCDIR}/binutils MAKEINFOFLAGS+= -I ${GDBDIR}/gdb/doc +MAKEINFOFLAGS+= -I ${GDBDIR}/gdb/mi MAKEINFOFLAGS+= -I ${CONTRIBDIR}/libreadline/doc CLEANFILES= gdb-cfg.texi inc-hist.texi inc-hist.texi.orig \ @@ -27,12 +28,18 @@ as.info: as.texinfo asconfig.texi c-i386.texi gasver.texi ld.info: ld.texinfo bfdsumm.texi ldver.texi -gdb.info: gdb.texinfo gdb-cfg.texi GDBvn.texi remote.texi \ - rluser.texinfo inc-hist.texi +gdb.info: gdb.texinfo gdb-cfg.texi GDBvn.texi annotate.texi \ + fdl.texi gpl.texi gdbmi.texinfo \ + rluser.texinfo inc-hist.texinfo +gdbint.info: gdbint.texinfo fdl.texi + gdb-cfg.texi: all-cfg.texi ln -sf ${.ALLSRC} ${.TARGET} +GDBvn.texi: ${GDBDIR}/gdb/version.in + echo "@set GDBVN `sed q ${.ALLSRC}`" > ${.TARGET} + .PATH: ${SRCDIR}/binutils binutils.info: binutils.texi config.texi @@ -40,7 +47,7 @@ echo "@set VERSION ${VERSION}" > ${.TARGET} .PATH: ${CONTRIBDIR}/libreadline/doc -inc-hist.texi: hsuser.texinfo inc-hist.diff +inc-hist.texinfo: hsuser.texinfo inc-hist.diff cp ${.ALLSRC:M*.texinfo} ${.TARGET} patch -b .orig < ${.ALLSRC:M*.diff} --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="binutils::doc::inc-hist.diff.diff" Index: inc-hist.diff =================================================================== RCS file: /usr/home/cc/ncvs/freebsd//src/gnu/usr.bin/binutils/doc/inc-hist.diff,v retrieving revision 1.3 diff -u -r1.3 inc-hist.diff --- inc-hist.diff 11 Apr 2001 04:27:10 -0000 1.3 +++ inc-hist.diff 29 Jun 2002 12:20:56 -0000 @@ -1,7 +1,7 @@ $FreeBSD: src/gnu/usr.bin/binutils/doc/inc-hist.diff,v 1.3 2001/04/11 04:27:10 ache Exp $ ---- inc-hist.texi.orig Wed Apr 11 08:20:01 2001 -+++ inc-hist.texi Wed Apr 11 08:21:57 2001 +--- inc-hist.texinfo.orig Wed Apr 11 08:20:01 2001 ++++ inc-hist.texinfo Wed Apr 11 08:21:57 2001 @@ -26,9 +26,9 @@ @node Using History Interactively @chapter Using History Interactively --98e8jtXdkpgskNou-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 3:25:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEBA337B400; Sun, 30 Jun 2002 03:25:10 -0700 (PDT) Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A44E243E26; Sun, 30 Jun 2002 03:25:09 -0700 (PDT) (envelope-from brian@FreeBSD.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [IPv6:fec0::1:12]) by Awfulhak.org (8.12.4/8.12.4) with ESMTP id g5UAP6w0003594; Sun, 30 Jun 2002 11:25:06 +0100 (BST) (envelope-from brian@FreeBSD.org) Received: from hak.lan.Awfulhak.org (brian@localhost [IPv6:::1]) by hak.lan.Awfulhak.org (8.12.5/8.12.5) with SMTP id g5UAP4Mr000573; Sun, 30 Jun 2002 11:25:05 +0100 (BST) (envelope-from brian@FreeBSD.org) Date: Sun, 30 Jun 2002 11:25:04 +0100 From: Brian Somers To: obrien@FreeBSD.org Cc: ijliao@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: make install failed on XFree86-4-client (with 6/10 -current) Message-Id: <20020630112504.60ea491a.brian@FreeBSD.org> In-Reply-To: <20020629194151.C51177@dragon.nuxi.com> References: <20020617040914.GA8595@terry.dragon2.net> <20020629233048.49c6244f.brian@FreeBSD.org> <20020629194151.C51177@dragon.nuxi.com> X-Mailer: Sylpheed version 0.7.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) 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 Well, this has been happening for about a year on my dev box. It's not gcc 3.1 specific. I've never gotten around to figuring out why it works on some machines. On Sat, 29 Jun 2002 19:41:51 -0700, David O'Brien wrote: > On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Somers wrote: > > The problem is because the glxinfo program uses CCLINK to > > link, but it's a c++ program. Changing the CCLINK to CXXLINK > > works. > > We can't be the only ones seeing this -- surely anyone using Gcc 3.1 on > their i386 (any OS) box. Has anyone [that cares] emailed any of the > XFree86 guys?? -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 6:39:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 819EA37B400 for ; Sun, 30 Jun 2002 06:39:27 -0700 (PDT) Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id D185143E0A for ; Sun, 30 Jun 2002 06:39:26 -0700 (PDT) (envelope-from tomppa@ultrahot.Finland.Sun.COM) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA18949 for ; Sun, 30 Jun 2002 07:39:25 -0600 (MDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.3beta) with ESMTP id g5UDdNsn023042 for ; Sun, 30 Jun 2002 16:39:23 +0300 (EEST) Received: from ultrahot.Finland.Sun.COM (localhost [127.0.0.1]) by ultrahot.Finland.Sun.COM (8.12.2+Sun/8.12.2) with ESMTP id g5UDdMQX000588 for ; Sun, 30 Jun 2002 16:39:22 +0300 (EEST) Received: (from tomppa@localhost) by ultrahot.Finland.Sun.COM (8.12.2+Sun/8.12.2/Submit) id g5UDdM39000585; Sun, 30 Jun 2002 16:39:22 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15647.2570.270243.127833@gargle.gargle.HOWL> Date: Sun, 30 Jun 2002 16:39:22 +0300 To: freebsd-current@freebsd.org Subject: Any newcard success with Linksys PCMPC100 X-Mailer: VM 7.05 under 21.4 (patch 8) "Honest Recruiter" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.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 I'm still using old 16bit Linksys card and it's not working with newcard. Otherwise newcard is just fine with my Toshiba 3440 when using Cisco Aironet 340. Newcard don't detect Linksys as it should. Is anyone using this card? --- newcard --- Jun 30 14:58:38 phb kernel: ed0: at port 0x100-0x11f irq 11 function 0 config 16 on pccard1 Jun 30 14:58:38 phb kernel: ed0: address 01:d4:ff:03:00:20, type NE2000 (16 bit) --- oldcard --- Jun 30 16:30:01 phb pccardd[131]: Card "Linksys"("EtherFast 10/100 PC Card (PCMPC100 V2)") [V2.0] [ ] matched "Linksys" ("/Ether[Ff]ast 10/100 PC Card \(PCMPC100.*\)/") [(null)] [(null)] Jun 30 16:30:01 phb pccardd[131]: Using I/O addr 0x300, size 32 Jun 30 16:30:01 phb pccardd[131]: Setting config reg at offs 0x400 to 0x41, Reset time = 50 ms Jun 30 16:30:06 phb kernel: ed0 at port 0x300-0x31f irq 11 flags 0x80000 slot 1 on pccard1 Jun 30 16:30:06 phb kernel: ed0: address 00:e0:98:87:99:a7, type Linksys (16 bit) Jun 30 16:30:06 phb kernel: ukphy0: on miibus1 Jun 30 16:30:06 phb kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jun 30 16:30:06 phb pccardd[131]: Assigning I/O window 0, start 0x300, size 0x20 flags 0x5 Jun 30 16:30:06 phb pccardd[131]: Assign ed-1, io 0x300-0x31f, mem 0x0, 0 bytes, irq 11, flags 80000 Jun 30 16:30:06 phb pccardd[131]: ed0: Linksys (/Ether[Ff]ast 10/100 PC Card \(PCMPC100.*\)/) inserted. -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 7: 0:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD96A37B400 for ; Sun, 30 Jun 2002 07:00:09 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419E343E1A for ; Sun, 30 Jun 2002 07:00:09 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.5/8.12.5) with ESMTP id g5UE08JW001888 for ; Sun, 30 Jun 2002 07:00:08 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.5/8.12.5/Submit) id g5UE08k0001886 for current@freebsd.org; Sun, 30 Jun 2002 07:00:08 -0700 (PDT) Date: Sun, 30 Jun 2002 07:00:08 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200206301400.g5UE08k0001886@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 Sun Jun 30 07:00:07 PDT 2002 cd: can't cd to /home/des/tinderbox/alpha/src To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 7: 0:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 863E837B40E for ; Sun, 30 Jun 2002 07:00:14 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id F050343E09 for ; Sun, 30 Jun 2002 07:00:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630140012.GSLT6023.sccrmhc02.attbi.com@InterJet.elischer.org> for ; Sun, 30 Jun 2002 14:00:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id GAA85179 for ; Sun, 30 Jun 2002 06:58:28 -0700 (PDT) Date: Sun, 30 Jun 2002 06:58:26 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: Revised: KSE M-III status: In-Reply-To: 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 On Sun, 30 Jun 2002, Julian Elischer wrote: Well after 1 day I'm releatively happy.. There seem to have been 4 bugs showing themselves.. A machine doing REAL HEAVY work and SWAPPING LIKE CRAZY eventually paniced. (one instance) Matt triggered a panic we put into the code and thought we'd never see again.. I thought tomorrow was looking too empty.. (one instance) I have one report that GNOME apps freeze and chew all cpu time.. (I'll bet it's signals.. I hate them) If this happens to you too let me know. Alternatively if you can debug gnome stuff (you are a gnome expert baybe you can tell me what is happenning.. a Ktrace might be a good start) (compared to a good ktrace) In addition I fixed one bug where zombie processes were incorrectly handled and ps or w or killall could cause a crash. At least we still seem to have basic functionality.. I'm off to bed.. see ya in 8 hours! Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 7:20:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 401B737B401 for ; Sun, 30 Jun 2002 07:20:15 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id E379143E1A for ; Sun, 30 Jun 2002 07:20:14 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630142014.TDNO8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Sun, 30 Jun 2002 14:20:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id HAA85250 for ; Sun, 30 Jun 2002 07:04:43 -0700 (PDT) Date: Sun, 30 Jun 2002 07:04:43 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: Re: Revised: KSE M-III status: In-Reply-To: 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 On Sun, 30 Jun 2002, Julian Elischer wrote: > > > > On Sun, 30 Jun 2002, Julian Elischer wrote: > > > Well after 1 day I'm releatively happy.. that's "relatively" > > There seem to have been 4 bugs showing themselves.. > > A machine doing REAL HEAVY work and SWAPPING LIKE CRAZY > eventually paniced. (one instance) > > Matt triggered a panic we put into the code and thought > we'd never see again.. I thought tomorrow was looking too empty.. > (one instance) > > I have one report that GNOME apps freeze and chew all cpu time.. > (I'll bet it's signals.. I hate them) If this happens to you too let me > know. Alternatively if you can debug gnome stuff (you are a gnome expert > baybe you can tell me what is happenning.. a Ktrace might be a good start) > (compared to a good ktrace) > > In addition I fixed one bug where zombie processes were incorrectly > handled and ps or w or killall could cause a crash. > > At least we still seem to have basic functionality.. > I'm off to bed.. see ya in 8 hours! duh, It's morning .. should have removed that line too > > Julian > > > > > 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 Jun 30 7:44:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B65037B400 for ; Sun, 30 Jun 2002 07:44:08 -0700 (PDT) Received: from mail44.fg.online.no (mail44-s.fg.online.no [148.122.161.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2C4143E09 for ; Sun, 30 Jun 2002 07:44:06 -0700 (PDT) (envelope-from frode@nordahl.net) Received: from ti200720a080-0245.bb.online.no (ti200720a080-0245.bb.online.no [80.212.244.245]) by mail44.fg.online.no (8.9.3/8.9.3) with ESMTP id QAA21333; Sun, 30 Jun 2002 16:43:26 +0200 (MET DST) Subject: Re: mozilla and gnome apps won't run after KSE [June 29] From: Frode Nordahl To: Julian Elischer Cc: walt , freebsd-current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 30 Jun 2002 16:43:17 +0200 Message-Id: <1025448203.500.7.camel@samwise.xu.nordahl.net> Mime-Version: 1.0 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 see no problems with neither GNOME nor Mozilla. Kernel compiled about an hour ago (15:30:13 CEST / GMT+2). Userland last compiled on June 27. On Sun, 2002-06-30 at 10:29, Julian Elischer wrote: > Ithink these may be threaded > it's possible the are using signals and they may be broken.... > > > On Fri, 28 Jun 2002, walt wrote: > > > Following make world && make kernel after the KSE update > > I find that mozilla and any gnome app will suck up 98% > > of the CPU and will never actually write anything to > > the display. No crashes, no error messages, they > > just chew up cycles. > > > > I don't have KDE installed on my -current machine, > > so I can't comment on it, but most other basic X apps > > seem to work fine--like xterm, xvidtune, the X > > interface to emacs and the X interface for cvsup > > all work OK. > > > > Any one else seeing this? > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 10:40:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5750F37B400 for ; Sun, 30 Jun 2002 10:40:18 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6E4943E09 for ; Sun, 30 Jun 2002 10:40:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630174017.SESL29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 17:40:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA85893; Sun, 30 Jun 2002 10:39:13 -0700 (PDT) Date: Sun, 30 Jun 2002 10:39:12 -0700 (PDT) From: Julian Elischer To: walt Cc: freebsd-current@freebsd.org Subject: Re: mozilla and gnome apps won't run after KSE [June 29] In-Reply-To: <3D1C6C98.2000908@hotmail.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 Hi so far..... you are the only person who has reported this.. please let me know if anything changes.. It's now the 'top' item in my list of problems. On Fri, 28 Jun 2002, walt wrote: > Following make world && make kernel after the KSE update > I find that mozilla and any gnome app will suck up 98% > of the CPU and will never actually write anything to > the display. No crashes, no error messages, they > just chew up cycles. > > I don't have KDE installed on my -current machine, > so I can't comment on it, but most other basic X apps > seem to work fine--like xterm, xvidtune, the X > interface to emacs and the X interface for cvsup > all work OK. > > Any one else seeing this? > > > 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 Jun 30 10:43:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72C8837B400 for ; Sun, 30 Jun 2002 10:43:42 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id F13F443E0A for ; Sun, 30 Jun 2002 10:43:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g5UHheT4099015; Sun, 30 Jun 2002 10:43:40 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g5UHheh1099010; Sun, 30 Jun 2002 10:43:40 -0700 (PDT) (envelope-from dillon) Date: Sun, 30 Jun 2002 10:43:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200206301743.g5UHheh1099010@apollo.backplane.com> To: Julian Elischer Cc: FreeBSD current users Subject: Re: I think KSE-MIII import complete References: 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 : :which panic message? :the code here is still FULL of asserts. : "Unexpected ke present". I'm resynching and will run the build test again. If it crunches again I'll do a more detailed check. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 10:55: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1902237B400 for ; Sun, 30 Jun 2002 10:55:07 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9692343E09 for ; Sun, 30 Jun 2002 10:55:06 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.5/8.12.5) with ESMTP id g5UHt5ZY091548; Sun, 30 Jun 2002 10:55:05 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.5/8.12.5/Submit) id g5UHt5hF091547; Sun, 30 Jun 2002 10:55:05 -0700 (PDT) Date: Sun, 30 Jun 2002 10:55:05 -0700 From: Steve Kargl To: Julian Elischer Cc: walt , freebsd-current@FreeBSD.ORG Subject: Re: mozilla and gnome apps won't run after KSE [June 29] Message-ID: <20020630105505.A91499@troutmask.apl.washington.edu> References: <3D1C6C98.2000908@hotmail.com> 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 julian@elischer.org on Sun, Jun 30, 2002 at 10:39:12AM -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 Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: > Hi > > so far..... you are the only person who has reported this.. > please let me know if anything changes.. > > It's now the 'top' item in my list of problems. > kargl[34] mozilla [1] 1347 Segmentation fault :-) -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 11:28:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81CB137B40B for ; Sun, 30 Jun 2002 11:28:43 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C48743E09 for ; Sun, 30 Jun 2002 11:28:43 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [67.114.252.78] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare via secured & encrypted transport (TLS); Sun, 30 Jun 2002 12:28:43 -0600 Message-ID: <3D1EEBE3.8040105@hotmail.com> Date: Sun, 30 Jun 2002 11:30:43 +0000 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020323 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: More on gnome and mozilla (post-KSE) 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 Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still compiling, so whatever this problem is it was not due to changes in the kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 13:20:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B08F137B400 for ; Sun, 30 Jun 2002 13:20:15 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CECF43E13 for ; Sun, 30 Jun 2002 13:20:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630202010.NHNU6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 20:20:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA86518; Sun, 30 Jun 2002 13:17:03 -0700 (PDT) Date: Sun, 30 Jun 2002 13:17:01 -0700 (PDT) From: Julian Elischer To: Steve Kargl Cc: walt , freebsd-current@FreeBSD.ORG Subject: Re: mozilla and gnome apps won't run after KSE [June 29] In-Reply-To: <20020630105505.A91499@troutmask.apl.washington.edu> 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 well, that's different :-) any chance to get a ktrace ? On Sun, 30 Jun 2002, Steve Kargl wrote: > On Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: > > Hi > > > > so far..... you are the only person who has reported this.. > > please let me know if anything changes.. > > > > It's now the 'top' item in my list of problems. > > > kargl[34] mozilla > [1] 1347 Segmentation fault > > :-) > > -- > Steve > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 13:40:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E7C637B400 for ; Sun, 30 Jun 2002 13:40:18 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E2BE43E09 for ; Sun, 30 Jun 2002 13:40:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630204016.NRGS6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 20:40:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA86552; Sun, 30 Jun 2002 13:21:25 -0700 (PDT) Date: Sun, 30 Jun 2002 13:21:23 -0700 (PDT) From: Julian Elischer To: walt Cc: freebsd-current@freebsd.org Subject: Re: More on gnome and mozilla (post-KSE) In-Reply-To: <3D1EEBE3.8040105@hotmail.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 hmmmmmmm well, since the only changes were in the kernel except for libkvm I'm puzzled. If you boot off the old kernel (You still have it right? :-) does it still act the same? On Sun, 30 Jun 2002, walt wrote: > Dunno if this is important, but I meant to mention it in my > initial problem report: the problem with gnome and mozilla > chewing up CPU cycles begain just after the make world > finished and while the make kernel was still compiling, > so whatever this problem is it was not due to changes > in the kernel. > > > 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 Jun 30 13:40:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A136137B40B for ; Sun, 30 Jun 2002 13:40:22 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12B6843E0A for ; Sun, 30 Jun 2002 13:40:22 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630204021.NRHW6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 20:40:21 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA86579; Sun, 30 Jun 2002 13:38:32 -0700 (PDT) Date: Sun, 30 Jun 2002 13:38:30 -0700 (PDT) From: Julian Elischer To: Steve Kargl Cc: walt , freebsd-current@FreeBSD.ORG Subject: Re: mozilla and gnome apps won't run after KSE [June 29] In-Reply-To: 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 ty a new libkvm.. also please try the same binary booted off the old non KSE kernel.. (what, you don't still have it?) On Sun, 30 Jun 2002, Julian Elischer wrote: > well, that's different :-) > > any chance to get a ktrace ? > > On Sun, 30 Jun 2002, Steve Kargl wrote: > > > On Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: > > > Hi > > > > > > so far..... you are the only person who has reported this.. > > > please let me know if anything changes.. > > > > > > It's now the 'top' item in my list of problems. > > > > > kargl[34] mozilla > > [1] 1347 Segmentation fault > > > > :-) > > > > -- > > Steve > > > > > 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 Jun 30 13:43:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 237D637B405 for ; Sun, 30 Jun 2002 13:43:39 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E99943E13 for ; Sun, 30 Jun 2002 13:43:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g5UKhaT4006419; Sun, 30 Jun 2002 13:43:37 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g5UKha9t006418; Sun, 30 Jun 2002 13:43:36 -0700 (PDT) (envelope-from dillon) Date: Sun, 30 Jun 2002 13:43:36 -0700 (PDT) From: Matthew Dillon Message-Id: <200206302043.g5UKha9t006418@apollo.backplane.com> To: Julian Elischer Cc: Steve Kargl , walt , freebsd-current@FreeBSD.ORG Subject: KSE / interrupt panic References: 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 Got another one. Different panic, same place. panic: setrunqueue: bad thread state cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db> trace Debugger(c02ec2ba) at Debugger+0x46 panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 setrunqueue(c6461d80) at setrunqueue+0x1dd cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 softclock(0) at softclock+0x159 ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at ithread_loop+0x12c fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 fork_trampoline() at fork_trampoline+0x37 db> gdb ... #0 Debugger (msg=0xc02ec2ba "panic") at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 #1 0xc01c878a in panic (fmt=0xc02ec8a9 "setrunqueue: bad thread state") at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 #2 0xc01cc6cd in setrunqueue (td=0xc6461d80) at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 #3 0xc01afa66 in cv_timedwait_end (arg=0xc6461d80) at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 #4 0xc01d22c9 in softclock (dummy=0x0) at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 #5 0xc01b9d98 in ithread_loop (arg=0xc229c700) at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 #6 0xc01b923c in fork_exit (callout=0xc01b9c6c , arg=0xc229c700, frame=0xdf3eed48) at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 I'm not sure why the panic was 'bad thread state' when gdb seems to show it being stuck on 'unexpected ke present'. Maybe it was an optimization and gdb is confused. The panic is definitely 'bad thread state'. (gdb) print td->td_state $2 = TDS_RUNQ setrunqueue() is being called on a thread which is already on the run queue. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 14: 0:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB8D037B400 for ; Sun, 30 Jun 2002 14:00:15 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1B6743E13 for ; Sun, 30 Jun 2002 14:00:14 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630210013.LXSD903.sccrmhc03.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 21:00:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA86679; Sun, 30 Jun 2002 13:59:55 -0700 (PDT) Date: Sun, 30 Jun 2002 13:59:53 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Steve Kargl , walt , freebsd-current@FreeBSD.ORG Subject: Re: KSE / interrupt panic In-Reply-To: <200206302043.g5UKha9t006418@apollo.backplane.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 others have seen this one too and the common element is that it's always in setrunqueue() called from an interrupt. it is also often via cv_*SOMETHING*() I Thought we had cleared these up but apparently not :-/ On Sun, 30 Jun 2002, Matthew Dillon wrote: > Got another one. Different panic, same place. > > panic: setrunqueue: bad thread state > cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > db> trace > Debugger(c02ec2ba) at Debugger+0x46 > panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 > setrunqueue(c6461d80) at setrunqueue+0x1dd > cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 > softclock(0) at softclock+0x159 > ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at ithread_loop+0x12c > fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 > fork_trampoline() at fork_trampoline+0x37 > db> gdb > ... > > #0 Debugger (msg=0xc02ec2ba "panic") > at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 > #1 0xc01c878a in panic (fmt=0xc02ec8a9 "setrunqueue: bad thread state") > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 > #2 0xc01cc6cd in setrunqueue (td=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 > #3 0xc01afa66 in cv_timedwait_end (arg=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 > #4 0xc01d22c9 in softclock (dummy=0x0) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 > #5 0xc01b9d98 in ithread_loop (arg=0xc229c700) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 > #6 0xc01b923c in fork_exit (callout=0xc01b9c6c , > arg=0xc229c700, frame=0xdf3eed48) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 > > I'm not sure why the panic was 'bad thread state' when gdb seems to > show it being stuck on 'unexpected ke present'. Maybe it was an > optimization and gdb is confused. The panic is definitely > 'bad thread state'. > > (gdb) print td->td_state > $2 = TDS_RUNQ > > setrunqueue() is being called on a thread which is already on the run > queue. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 14: 6:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B54837B406 for ; Sun, 30 Jun 2002 14:06:05 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B0A543E09 for ; Sun, 30 Jun 2002 14:06:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g5UL5tT4014171; Sun, 30 Jun 2002 14:05:55 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g5UL5trx014170; Sun, 30 Jun 2002 14:05:55 -0700 (PDT) (envelope-from dillon) Date: Sun, 30 Jun 2002 14:05:55 -0700 (PDT) From: Matthew Dillon Message-Id: <200206302105.g5UL5trx014170@apollo.backplane.com> To: Julian Elischer Cc: Steve Kargl , walt , freebsd-current@FreeBSD.ORG Subject: Re: KSE / interrupt panic References: 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 :others have seen this one too :and the common element is that it's always in :setrunqueue() called from an interrupt. :it is also often via cv_*SOMETHING*() : :I Thought we had cleared these up but apparently not :-/ : There are a bunch of wakeup race conditions in the CV code where the TIMEOUT flag may be left set while the thread is still running. There are two calls to setrunqueue() in kern_condvar.c. One looks like it covers the case, the other needs help. I'm trying this patch now: -Matt Index: kern_condvar.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_condvar.c,v retrieving revision 1.23 diff -u -r1.23 kern_condvar.c --- kern_condvar.c 29 Jun 2002 17:26:18 -0000 1.23 +++ kern_condvar.c 30 Jun 2002 20:51:31 -0000 @@ -605,7 +605,8 @@ mtx_lock_spin(&sched_lock); if (td->td_flags & TDF_TIMEOUT) { td->td_flags &= ~TDF_TIMEOUT; - setrunqueue(td); + if (td->td_state != TDS_RUNQ) + setrunqueue(td); } else if (td->td_wchan != NULL) { if (td->td_state == TDS_SLP) /* XXXKSE */ setrunnable(td); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 14: 7: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56A4A37B400 for ; Sun, 30 Jun 2002 14:06:57 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id F25DB43E0A for ; Sun, 30 Jun 2002 14:06:56 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g5UL6ug86404; Sun, 30 Jun 2002 14:06:56 -0700 (PDT) (envelope-from rizzo) Date: Sun, 30 Jun 2002 14:06:56 -0700 From: Luigi Rizzo To: current@freebsd.org Subject: buildworld problems with today's sources Message-ID: <20020630140656.A86137@iguana.icir.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 did the following (on a -STABLE system): cvs co src cd src make MAKEOBJDIRPREFIX=`pwd`/../usr/obj buildworld and got the error below. Any ideas ? Am i doing something wrong ? cheers luigi ===> gnu/usr.bin/tar rm -f tar addext.o argmatch.o backupfile.o basename.o dirname.o error.o exclude.o full-write.o getdate.o getline.o getopt.o getopt1.o getstr.o hash.o human.o mktime.o modechange.o prepargs.o print-copyr.o quotearg.o safe-read.o save-cwd.o savedir.o unicodeio.o xgetcwd.o xmalloc.o xstrdup.o xstrtoul.o xstrtoumax.o buffer.o compare.o create.o delete.o extract.o incremen.o list.o mangle.o misc.o names.o rtapelib.o tar.o update.o tar.1.gz tar.1.cat.gz rm: tar: is a directory *** Error code 1 Stop in /home/luigi/XORP/HEAD_020630/src/gnu/usr.bin/tar. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 14:20:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6191C37B401 for ; Sun, 30 Jun 2002 14:20:14 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D48AC43E0A for ; Sun, 30 Jun 2002 14:20:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020630212013.BARN8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sun, 30 Jun 2002 21:20:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA86732; Sun, 30 Jun 2002 14:05:22 -0700 (PDT) Date: Sun, 30 Jun 2002 14:05:20 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Steve Kargl , walt , freebsd-current@FreeBSD.ORG Subject: Re: KSE / interrupt panic In-Reply-To: <200206302043.g5UKha9t006418@apollo.backplane.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 On Sun, 30 Jun 2002, Matthew Dillon wrote: > Got another one. Different panic, same place. > > panic: setrunqueue: bad thread state > cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > db> trace > Debugger(c02ec2ba) at Debugger+0x46 > panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 > setrunqueue(c6461d80) at setrunqueue+0x1dd > cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 > softclock(0) at softclock+0x159 > ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at ithread_loop+0x12c > fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 > fork_trampoline() at fork_trampoline+0x37 > db> gdb > ... > > #0 Debugger (msg=0xc02ec2ba "panic") > at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 > #1 0xc01c878a in panic (fmt=0xc02ec8a9 "setrunqueue: bad thread state") > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 > #2 0xc01cc6cd in setrunqueue (td=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 > #3 0xc01afa66 in cv_timedwait_end (arg=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 > #4 0xc01d22c9 in softclock (dummy=0x0) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 > #5 0xc01b9d98 in ithread_loop (arg=0xc229c700) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 > #6 0xc01b923c in fork_exit (callout=0xc01b9c6c , > arg=0xc229c700, frame=0xdf3eed48) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 > > I'm not sure why the panic was 'bad thread state' when gdb seems to > show it being stuck on 'unexpected ke present'. Maybe it was an > optimization and gdb is confused. The panic is definitely > 'bad thread state'. > > (gdb) print td->td_state > $2 = TDS_RUNQ well IS it on the run queue? print td->td_ksegrp->kg_runq->tqh.first > > setrunqueue() is being called on a thread which is already on the run > queue. > > -Matt > > > 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 Jun 30 14:42: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF97637B400 for ; Sun, 30 Jun 2002 14:42:01 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EBFA43E13 for ; Sun, 30 Jun 2002 14:42:01 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.110.69] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare via secured & encrypted transport (TLS); Sun, 30 Jun 2002 15:42:00 -0600 Message-ID: <3D1D786E.4010508@hotmail.com> Date: Sat, 29 Jun 2002 02:05:50 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020620 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current Subject: Re More on gnome and mozilla (post-KSE) 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 Julian on FreeBSD-CURRENT wrote: > On Sun, 30 Jun 2002, walt wrote: >> Dunno if this is important, but I meant to mention it in my >> initial problem report: the problem with gnome and mozilla >> chewing up CPU cycles begain just after the make world >> finished and while the make kernel was still compiling, >> so whatever this problem is it was not due to changes >> in the kernel. > hmmmmmmm > well, since the only changes were in the kernel except for libkvm > I'm puzzled. If you boot off the old kernel (You still have it right? > :-) does it still act the same? Yes. The bad behavior started with the old kernel and still does the same thing when I reboot it today. I should mention I also did see one segfault from mozilla after it churned away for 30 seconds or so, but I only saw that once--I think it was while the kernel was still compiling--and haven't seen it since. I notice today that gnumeric also segfaults with both old and new kernels. It may be possible (sorry I can't be sure) that what I'm calling the 'old' kernel may have been compiled in the middle of your KSE commit--it's dated only a couple of hours older that the 'new' kernel which was definitely made after your commit was done. If this is the case then the bad behavior may have started earlier than I thought--at the previous reboot--and I just didn't notice it. I run xfce routinely on the -CURRENT machine so I wouldn't notice the gnome breakage until my wife sat down at the machine and started whining that gnome-mahjongg didn't work ...and she couldn't read her Hotmail with mozilla either. As to your question about debugging skills--alas, few and far between. I've never used gdb but I'm willing to try if someone could give me an example of what I would need to do to give you the right info. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 15:26:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DFFC37B400 for ; Sun, 30 Jun 2002 15:26:50 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD03E43E09 for ; Sun, 30 Jun 2002 15:26:48 -0700 (PDT) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) by srv1.cosmo-project.de (8.12.3/8.12.3) with ESMTP id g5UMQdMa025854 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Mon, 1 Jul 2002 00:26:42 +0200 (CEST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (localhost [IPv6:::1]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g5UMQdFJ033603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 1 Jul 2002 00:26:39 +0200 (CEST)?g (envelope-from ticso@cicely5.cicely.de) Received: (from ticso@localhost) by cicely5.cicely.de (8.12.1/8.12.1/Submit) id g5UMQcPg033602; Mon, 1 Jul 2002 00:26:38 +0200 (CEST)?g (envelope-from ticso) Date: Mon, 1 Jul 2002 00:26:38 +0200 From: Bernd Walter To: Julian Elischer Cc: walt , freebsd-current@FreeBSD.ORG Subject: Re: mozilla and gnome apps won't run after KSE [June 29] Message-ID: <20020630222637.GL70344@cicely5.cicely.de> Reply-To: ticso@cicely.de References: <3D1C6C98.2000908@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely5.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.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 On Sun, Jun 30, 2002 at 10:39:12AM -0700, Julian Elischer wrote: > Hi > > so far..... you are the only person who has reported this.. > please let me know if anything changes.. FWIW: I'm running gimp on an alpha running a post KSE kernel. The world is about 2 weeks older on that machine. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 15:53:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1012C37B400 for ; Sun, 30 Jun 2002 15:53:24 -0700 (PDT) Received: from www.fastmail.fm (fastmail.fm [209.61.183.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DD343E09 for ; Sun, 30 Jun 2002 15:53:23 -0700 (PDT) (envelope-from freebsd@fastmail.fm) Received: from www.fastmail.fm (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id C2A536D9DB for ; Sun, 30 Jun 2002 17:53:15 -0500 (CDT) Received: by www.fastmail.fm (Postfix, from userid 99) id BC2486D9D3; Sun, 30 Jun 2002 17:53:15 -0500 (CDT) Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 2.117 (F2.6; T0.14; A1.46; B2.12; Q2.03) Date: Sun, 30 Jun 2002 22:53:15 +0000 From: "Glenn Gombert" To: current@freebsd.org Reply-To: "Glenn Gombert" X-Epoch: 1025477595 X-Sasl-enc: bHs4JfPnObPhzndZbyJtiQ Subject: Build world problems in todays sources Message-Id: <20020630225315.BC2486D9D3@www.fastmail.fm> 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 get the following error when trying to rebuild the last couple of days... ../sys/kern/syscalls.master syscall.master : line 55: syscall number out of sync at 7 ... line is: struct rusage * rsuage ) ; } wait4 wait_args int **** Error code 1 .... -- Glenn Gombert freebsd@fastmail.fm "Never trust any operating system you don't have the source code for" -- http://fastmail.fm - Come on home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 16:19:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5051137B400 for ; Sun, 30 Jun 2002 16:19:34 -0700 (PDT) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E84F243E0A for ; Sun, 30 Jun 2002 16:19:32 -0700 (PDT) (envelope-from charon@labs.gr) Received: from hades.hell.gr (patr530-a049.otenet.gr [212.205.215.49]) by mailsrv.otenet.gr (8.12.4/8.12.4) with ESMTP id g5UNJTlm028078 for ; Mon, 1 Jul 2002 02:19:30 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.4/8.12.4) with ESMTP id g5UNJSgi003002 for ; Mon, 1 Jul 2002 02:19:28 +0300 (EEST) (envelope-from charon@labs.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.4/8.12.4/Submit) id g5UNJQqi003001; Mon, 1 Jul 2002 02:19:26 +0300 (EEST) (envelope-from charon@labs.gr) Date: Mon, 1 Jul 2002 02:19:25 +0300 From: Giorgos Keramidas To: Glenn Gombert Cc: current@FreeBSD.ORG Subject: Re: Build world problems in todays sources Message-ID: <20020630231924.GA2837@hades.hell.gr> References: <20020630225315.BC2486D9D3@www.fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020630225315.BC2486D9D3@www.fastmail.fm> X-Operating-System: FreeBSD 5.0-CURRENT i386 X-PGP-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-Phone: +30-944-116520 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-06-30 22:53 +0000, Glenn Gombert wrote: > I get the following error when trying to rebuild the last couple of > days... > > ../sys/kern/syscalls.master > syscall.master : line 55: syscall number out of sync at 7 ... > > line is: struct rusage * rsuage ) ; } wait4 wait_args int > > **** Error code 1 > .... The last commit that touched this line was revision 1.17. You have somehow edited this file and changed /rusage/rsuage/. This can be fixed by editing again and replacing "rsuage" with "rusage". - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 16:19:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6998737B407 for ; Sun, 30 Jun 2002 16:19:50 -0700 (PDT) Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05BA643E1A for ; Sun, 30 Jun 2002 16:19:49 -0700 (PDT) (envelope-from charon@labs.gr) Received: from hades.hell.gr (patr530-a049.otenet.gr [212.205.215.49]) by mailsrv.otenet.gr (8.12.4/8.12.4) with ESMTP id g5UNJklm028187 for ; Mon, 1 Jul 2002 02:19:47 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.4/8.12.4) with ESMTP id g5UNJjgi003013 for ; Mon, 1 Jul 2002 02:19:45 +0300 (EEST) (envelope-from charon@labs.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.4/8.12.4/Submit) id g5UNJjNU003012; Mon, 1 Jul 2002 02:19:45 +0300 (EEST) (envelope-from charon@labs.gr) Date: Mon, 1 Jul 2002 02:19:44 +0300 From: Giorgos Keramidas To: Glenn Gombert Cc: current@FreeBSD.ORG Subject: Re: Build world problems in todays sources Message-ID: <20020630231924.GA2837@hades.hell.gr> References: <20020630225315.BC2486D9D3@www.fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020630225315.BC2486D9D3@www.fastmail.fm> X-Operating-System: FreeBSD 5.0-CURRENT i386 X-PGP-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-Phone: +30-944-116520 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-06-30 22:53 +0000, Glenn Gombert wrote: > I get the following error when trying to rebuild the last couple of > days... > > ../sys/kern/syscalls.master > syscall.master : line 55: syscall number out of sync at 7 ... > > line is: struct rusage * rsuage ) ; } wait4 wait_args int > > **** Error code 1 > .... The last commit that touched this line was revision 1.17. You have somehow edited this file and changed /rusage/rsuage/. This can be fixed by editing again and replacing "rsuage" with "rusage". - Giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 16:31: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50EC537B400 for ; Sun, 30 Jun 2002 16:31:05 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A44043E0A for ; Sun, 30 Jun 2002 16:31:05 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g5UNV3T4014696; Sun, 30 Jun 2002 16:31:03 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g5UNV322014695; Sun, 30 Jun 2002 16:31:03 -0700 (PDT) (envelope-from dillon) Date: Sun, 30 Jun 2002 16:31:03 -0700 (PDT) From: Matthew Dillon Message-Id: <200206302331.g5UNV322014695@apollo.backplane.com> To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Re: KSE / interrupt panic References: 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 Got a weird one. No backtrace. gdb got confused and wouldn't attach properly. -Matt Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 01000000 fault virtual address = 0xd0c45a fault code = supervisor write, page not present instruction pointer = 0x8:0xe5650b87 stack pointer = 0x10:0xe5650b68 frame pointer = 0x10:0xc02b9bf7 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 = 12950 (make) kernel: type 12 trap, code=0 Stopped at 0xe5650b87: rolb $0x32,0x58(%eax) db> trace _end(81537ef6,fffe,8d287f00,48db604,86048d46) at 0xe5650b87 db> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 16:46:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C166137B400 for ; Sun, 30 Jun 2002 16:46:19 -0700 (PDT) Received: from web20903.mail.yahoo.com (web20903.mail.yahoo.com [216.136.226.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 85BFD43E0A for ; Sun, 30 Jun 2002 16:46:19 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020630234619.7290.qmail@web20903.mail.yahoo.com> Received: from [218.108.151.136] by web20903.mail.yahoo.com via HTTP; Sun, 30 Jun 2002 16:46:19 PDT Date: Sun, 30 Jun 2002 16:46:19 -0700 (PDT) From: David Xu Subject: Re: KSE / interrupt panic To: Matthew Dillon Cc: julian@elischer.org, sgk@troutmask.apl.washington.edu, wa1ter@hotmail.com, freebsd-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 setrunqueue() call can be simply removed from cv_timedwait_end(), because there is a race in softclock() and callout_stop(), when cv_timedwait_end() losts a race, it means that that thread is already running(wokenup by another thread), when you setrunqueue() it, of course it will panic. in cv_timedwait_end(), sentence "if (td->td_flags & TDF_TIMEOUT) {...}" is to check this race condition. -David Xu ----- Original Message ----- From: "Matthew Dillon" To: "Julian Elischer" Cc: "Steve Kargl" ; "walt" ; Sent: Monday, July 01, 2002 4:43 AM Subject: KSE / interrupt panic > Got another one. Different panic, same place. > > panic: setrunqueue: bad thread state > cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > db> trace > Debugger(c02ec2ba) at Debugger+0x46 > panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 > setrunqueue(c6461d80) at setrunqueue+0x1dd > cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 > softclock(0) at softclock+0x159 > ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at ithread_loop+0x12c > fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 > fork_trampoline() at fork_trampoline+0x37 > db> gdb > ... > > #0 Debugger (msg=0xc02ec2ba "panic") > at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 > #1 0xc01c878a in panic (fmt=0xc02ec8a9 "setrunqueue: bad thread state") > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 > #2 0xc01cc6cd in setrunqueue (td=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 > #3 0xc01afa66 in cv_timedwait_end (arg=0xc6461d80) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 > #4 0xc01d22c9 in softclock (dummy=0x0) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 > #5 0xc01b9d98 in ithread_loop (arg=0xc229c700) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 > #6 0xc01b923c in fork_exit (callout=0xc01b9c6c , > arg=0xc229c700, frame=0xdf3eed48) > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 > > I'm not sure why the panic was 'bad thread state' when gdb seems to > show it being stuck on 'unexpected ke present'. Maybe it was an > optimization and gdb is confused. The panic is definitely > 'bad thread state'. > > (gdb) print td->td_state > $2 = TDS_RUNQ > > setrunqueue() is being called on a thread which is already on the run > queue. > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.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 Jun 30 17:11:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B882037B400 for ; Sun, 30 Jun 2002 17:11:45 -0700 (PDT) Received: from web20903.mail.yahoo.com (web20903.mail.yahoo.com [216.136.226.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A85043E1A for ; Sun, 30 Jun 2002 17:11:45 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020701001144.10685.qmail@web20903.mail.yahoo.com> Received: from [218.108.152.96] by web20903.mail.yahoo.com via HTTP; Sun, 30 Jun 2002 17:11:44 PDT Date: Sun, 30 Jun 2002 17:11:44 -0700 (PDT) From: David Xu Subject: ppp begin core dump To: freebsd-current@freebsd.org, freebsd-net@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 cvsup from yesterday, ppp began core dump on my machine. back trace: GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 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-undermydesk-freebsd"...(no debugging symbols found)... Core was generated by `ppp'. Program terminated with signal 10, Bus error. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcrypt.so.2 Reading symbols from /usr/lib/libmd.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libmd.so.2 Reading symbols from /usr/lib/libutil.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libutil.so.3 Reading symbols from /usr/lib/libz.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.2 Reading symbols from /usr/lib/libalias.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libalias.so.4 Reading symbols from /usr/lib/libcrypto.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcrypto.so.2 Reading symbols from /usr/lib/libradius.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libradius.so.1 Reading symbols from /usr/lib/libnetgraph.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libnetgraph.so.1 Reading symbols from /usr/lib/libc.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 0x280f886f in PunchFWHole () from /usr/lib/libalias.so.4 (gdb) bt #0 0x280f886f in PunchFWHole () from /usr/lib/libalias.so.4 #1 0x280f694a in FindNewPortGroup () from /usr/lib/libalias.so.4 #2 0x280f68f2 in FindNewPortGroup () from /usr/lib/libalias.so.4 #3 0x280f7e89 in HouseKeeping () from /usr/lib/libalias.so.4 #4 0x280f2815 in PacketAliasOut () from /usr/lib/libalias.so.4 #5 0x0807cfa5 in NgRecvData () #6 0x0806b0c2 in NgRecvData () #7 0x08067705 in NgRecvData () #8 0x08070968 in NgRecvData () #9 0x080708bf in NgRecvData () #10 0x0804d1a5 in NgRecvData () #11 0x0806d7e7 in NgRecvData () #12 0x0806d700 in NgRecvData () #13 0x0804b5c9 in NgRecvData () (gdb) quit -David Xu __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.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 Jun 30 18:49:14 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id A881537B400; Sun, 30 Jun 2002 18:49:07 -0700 (PDT) Date: Sun, 30 Jun 2002 18:49:07 -0700 From: Juli Mallett To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Cc: current@FreeBSD.ORG Subject: libufs commit [Was Re: cvs commit: CVSROOT modules src MAINTAINERS src/lib Makefile src/lib/libufs Makefile block.c inode.c libufs.h sblock.c type.c] Message-ID: <20020630184907.A18765@FreeBSD.ORG> References: <200207010145.g611j3AA091698@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5.1i In-Reply-To: <200207010145.g611j3AA091698@freefall.freebsd.org>; from jmallett@FreeBSD.org on Sun, Jun 30, 2002 at 06:45:03PM -0700 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , X-Affiliated-Projects: FreeBSD, xMach, ircd-hybrid-7 X-Towel: Yes X-LiveJournal: flata X-Negacore: Yes X-Warning: If you make me read stupid email, don't be surprised if I respond. If you don't want me to reply to something, don't send it to me. 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 * Juli Mallett escriuréres > jmallett 2002/06/30 18:45:03 PDT > > Modified files: > . modules > . MAINTAINERS > lib Makefile > Added files: > lib/libufs Makefile block.c inode.c libufs.h > sblock.c type.c I have not modified anything to use libufs yet, as there was some objection to doing this when I am about to go away from my only sit-down testing boxes for a period of time, and would be unable to fix resulting breakage, however it is in tree, and I am confident it works, now, and anyone is welcome (nee, invited) to convert utilities to use it, or embrace and extend it. In particular, if someone who understands cylinder groups more than I do wants to write a cylinder.c, to abstract the cg functionality, it'd be totally wonderful. Hopefully any build breakage (and there should be none, I've been using this extensively here at home) will show up before I go out of town on Tuesday. Thanks juli. -- Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@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 Jun 30 19:19:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7EEB37B400 for ; Sun, 30 Jun 2002 19:19:05 -0700 (PDT) Received: from mail.viasoft.com.cn (ip-167-164-97-218.anlai.com [218.97.164.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ADE443E26 for ; Sun, 30 Jun 2002 19:19:00 -0700 (PDT) (envelope-from davidx@viasoft.com.cn) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id KAA10242; Mon, 1 Jul 2002 10:33:37 +0800 Message-ID: <002801c220a4$4637c2a0$ef01a8c0@davidwnt> From: "David Xu" To: "\"Matthew Dillon\"" Cc: "Julian Elischer" , , , Subject: Re: KSE / interrupt panic (patch) Date: Mon, 1 Jul 2002 10:09:03 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 Now let me describe where the race is: Thread A: | Thread B: cv_timedwait() | softclock() | = cv_timedwait_end() | =20 mtx_lock_spin(&sched_lock); | = mtx_lock_spin(&sched_lock); /* suppose blocked!!! */ ... | =20 callout_stop(&td->td_slpcallout) | td->td_flags |=3D TDF_TIMEOUT; | td->td_proc->p_stats->p_ru.ru_nivcsw++; | // problem, does not set thread state to TDS_SLP!!! | mi_switch(); | // run at once again | ... | mtx_unlock_spin(&sched_lock); | mtx_lock_spin() = returned !!! thread is still running | if (td->td_flags & = TDF_TIMEOUT) { ... | td->td_flags = &=3D ~TDF_TIMEOUT; some place call mi_switch() and now on runqueue | = setrunqueue(td); // crash | } ---------------------------------------------------------- here is the patch: --- /sys/kern/kern_condvar.c.old Mon Jul 1 09:06:01 2002 +++ /sys/kern/kern_condvar.c Mon Jul 1 09:32:50 2002 @@ -396,6 +396,7 @@ * between msleep and endtsleep. */ td->td_flags |=3D TDF_TIMEOUT; + td->td_state =3D TDS_SLP; td->td_proc->p_stats->p_ru.ru_nivcsw++; mi_switch(); } @@ -472,6 +473,7 @@ * between msleep and endtsleep. */ td->td_flags |=3D TDF_TIMEOUT; + td->td_state =3D TDS_SLP; td->td_proc->p_stats->p_ru.ru_nivcsw++; mi_switch(); } ------------------------------------------------------------------- bug is because cv_timedwait() detects timeout callout is running,=20 but it does not correctly wait callout to complete, so panic. BTW, the bug seems also exists in msleep() and endtsleep(), please=20 fix it! -David Xu --- David Xu wrote: > setrunqueue() call can be simply removed from cv_timedwait_end(), = because > there > is a race in softclock() and callout_stop(), when cv_timedwait_end() = losts a=20 > race, it means that that thread is already running(wokenup by another > thread), > when you setrunqueue() it, of course it will panic. > in cv_timedwait_end(), sentence "if (td->td_flags & TDF_TIMEOUT) = {...}" > is to check this race condition. >=20 > -David Xu >=20 > ----- Original Message -----=20 > From: "Matthew Dillon" > To: "Julian Elischer" > Cc: "Steve Kargl" ; "walt" > ; > Sent: Monday, July 01, 2002 4:43 AM > Subject: KSE / interrupt panic >=20 >=20 > > Got another one. Different panic, same place. > >=20 > > panic: setrunqueue: bad thread state > > cpuid =3D 0; lapic.id =3D 01000000 > > Debugger("panic") > > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > > db> trace > > Debugger(c02ec2ba) at Debugger+0x46 > > panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 > > setrunqueue(c6461d80) at setrunqueue+0x1dd > > cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 > > softclock(0) at softclock+0x159 > > ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at = ithread_loop+0x12c > > fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 > > fork_trampoline() at fork_trampoline+0x37 > > db> gdb > > ... > >=20 > > #0 Debugger (msg=3D0xc02ec2ba "panic") > > at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 > > #1 0xc01c878a in panic (fmt=3D0xc02ec8a9 "setrunqueue: bad thread = state") > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 > > #2 0xc01cc6cd in setrunqueue (td=3D0xc6461d80) > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 > > #3 0xc01afa66 in cv_timedwait_end (arg=3D0xc6461d80) > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 > > #4 0xc01d22c9 in softclock (dummy=3D0x0) > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 > > #5 0xc01b9d98 in ithread_loop (arg=3D0xc229c700) > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 > > #6 0xc01b923c in fork_exit (callout=3D0xc01b9c6c ,=20 > > arg=3D0xc229c700, frame=3D0xdf3eed48) > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 > > =20 > > I'm not sure why the panic was 'bad thread state' when gdb seems = to > > show it being stuck on 'unexpected ke present'. Maybe it was an = > > optimization and gdb is confused. The panic is definitely > > 'bad thread state'. > >=20 > > (gdb) print td->td_state > > $2 =3D TDS_RUNQ > >=20 > > setrunqueue() is being called on a thread which is already on = the run > > queue. > >=20 > > -Matt > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message >=20 > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 19:31:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B2E37B42B for ; Sun, 30 Jun 2002 19:30:28 -0700 (PDT) Received: from relay5.kornet.net (relay5.kornet.net [211.48.62.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A94443E1A for ; Sun, 30 Jun 2002 19:30:28 -0700 (PDT) (envelope-from amimi0404@kornet.net) Received: from ns (61.73.89.202) by relay5.kornet.net; 1 Jul 2002 11:30:24 +0900 Message-ID: <3d1fbec23d417692@relay5.kornet.net> (added by relay5.kornet.net) From: =?ks_c_5601-1987?B?v+y4rsSrteXIuL/4IL+1vvfGwMDl?= To: freebsd-current@freebsd.org Subject: =?ks_c_5601-1987?B?W7GksO1dIGZyZWVic2QtY3VycmVudLTUIMDnuczA1rTCILvnwLrHsMC7ILXluK6w2r3AtM+02SE=?= Date: Mon, 01 Jul 2002 11:35:35 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0117_01C0F35A.93A35C00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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. ------=_NextPart_000_0117_01C0F35A.93A35C00 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 v+y4rsSrteUgICAgDQoNCiAgICAgDQogICAgCQkJCQkJILy6uO0gIAkJICDB1rnOte63zyC5 +MijICANCsH3wOUgwPzIrSAgICAgIMjetOvG+SAgCSAgICAgDQogICANCiAgICAgILHNx8/A xyAguN7Az8HWvNK0wiDApbytx87AuyDF68fYILz2wf3H0SCwzcDMuOcsILHXv9y/oSC+7raw x9EgwaS6uLW1ILCusO0gIMDWwfYgvsrAvcC7ILngyPy0z7TZLg0KICDAzCBFLW1haWzAuiC5 373FwPy/68DMuOcsIL/4xKEgvsrAuL3HICCw5r/sIL7Gt6Egw6K/oSC43sDPwda80rimIMDU t8LHz7+pIMHWvcO46SC1ziC5+CC02b3DILjewM8gIMDMICCwocH2IL7KtbW3zyDHz7DavcC0 z7TZLg0KICAgICAJICC89r3FsMW6ziAgLyByZWZ1c2FsIG9mIHJlY2VpcHQgICAJICAgIAkg IA0KIA0KDQogDQo= ------=_NextPart_000_0117_01C0F35A.93A35C00 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PGh0bWw+DQoNCjxoZWFkPg0KPFNDUklQVCBsYW5ndWFnZT1qYXZhc2NyaXB0Pg0KPCEtLQ0K ZnVuY3Rpb24gY2xpY2tNb3VzZSgpDQoJew0KCSAgDQoJCWlmICgoZXZlbnQuYnV0dG9uPT0y KSB8fCAoZXZlbnQuYnV0dG9uPT0zKSl7DQoJCQlyZXR1cm4gKGZhbHNlKTsNCgkJfQkNCgl9 DQoJDQoJZnVuY3Rpb24gY2xpY2tLZXkoKQ0KCXsNCgkJaWYoKGV2ZW50LnNoaWZ0S2V5KSAm JiAoZXZlbnQua2V5Q29kZSA9PSAxMjEpKQ0KCQl7CQkNCgkJCXJldHVybiBmYWxzZTsNCgkJ fQkNCgl9DQoJDQoJZnVuY3Rpb24gbm9BY3Rpb24oKXsNCgkJcmV0dXJuIGZhbHNlOw0KCX0N Cg0KZG9jdW1lbnQub25tb3VzZWRvd249Y2xpY2tNb3VzZQ0KZG9jdW1lbnQub25rZXlkb3du PWNsaWNrS2V5DQpkb2N1bWVudC5vbmNvbnRleHRtZW51PW5vQWN0aW9uDQpkb2N1bWVudC5v bmRyYWdzdGFydD1ub0FjdGlvbg0KZG9jdW1lbnQub25zZWxlY3RzdGFydD1ub0FjdGlvbg0K Ly8tLT4NCjwvU0NSSVBUPg0KDQoNCg0KPG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBl IiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9ZXVjLWtyIj4NCjx0aXRsZT6/7LiuxKu1 5SAgPC90aXRsZT4NCg0KPC9oZWFkPg0KDQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgdGV4dD0i YmxhY2siIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiIGFsaW5rPSJyZWQiPg0KPHRhYmxl IGFsaWduPSJjZW50ZXIiIGJvcmRlcj0iMSIgY2VsbHNwYWNpbmc9IjAiIHdpZHRoPSI1ODki IGhlaWdodD0iOTIiIGJvcmRlcmNvbG9yZGFyaz0id2hpdGUiIGJvcmRlcmNvbG9ybGlnaHQ9 ImJsYWNrIj4NCiAgICA8dHI+DQogICAgICAgIDx0ZCB3aWR0aD0iNTkyIiBjb2xzcGFuPSIy Ij4NCiAgICAgICAgICAgIDxwPjxpbWcgc3JjPSJodHRwOi8vd3d3Lml5ZXNjYXJkLmNvbS9p bWFnZS90b3BfNy5naWYiIHdpZHRoPSI1OTciIGhlaWdodD0iOTIiIGJvcmRlcj0iMCI+PC9w Pg0KICAgICAgICA8L3RkPg0KICAgIDwvdHI+DQogICAgPHRyPg0KICAgICAgICA8dGQgd2lk dGg9IjU5MiIgY29sc3Bhbj0iMiI+DQogICAgICAgICAgICA8cCBhbGlnbj0iY2VudGVyIj48 aW1nIHNyYz0iaHR0cDovL3d3dy5peWVzY2FyZC5jb20vaW1hZ2UvYm90dG9tNi5naWYiIHdp ZHRoPSI1OTciIGhlaWdodD0iMjExIiBib3JkZXI9IjAiPjwvcD4NCiAgICAgICAgPC90ZD4N CiAgICA8L3RyPg0KICAgIDx0cj4NCiAgICAgICAgPHRkIHdpZHRoPSI1ODkiIGNvbHNwYW49 IjIiPg0KCQkJCQk8Zm9ybSBuYW1lPSJtYWlsZnJtIiBhY3Rpb249Imh0dHA6Ly93d3cuaXdv b3JpY2FyZC5jb20vbWFpbC9pbnNlcnQxLmFzcCIgbWV0aG9kPSJwb3N0IiA+CQ0KICAgICAg ICAgICAgPHAgYWxpZ249ImNlbnRlciIgc3R5bGU9InRleHQtaW5kZW50Oi0xOyBsaW5lLWhl aWdodDowOyBtYXJnaW46MDsiPjxmb250IHNpemU9IjIiIGNvbG9yPSIjNjY2NjY2Ij68urjt PC9mb250Pjxmb250IHNpemU9IjIiPiAgDQogICAgICAgICAgPC9mb250PjxpbnB1dCB0eXBl PSJ0ZXh0IiBuYW1lPSJuYW1lIiBzaXplPSI2Ij4NCgkJICAmbmJzcDs8Zm9udCBzaXplPSIy IiBjb2xvcj0iIzY2NjY2NiI+wda5zrXut88gufjIoyA8L2ZvbnQ+PGlucHV0IHR5cGU9InRl eHQiIG5hbWU9Imp1bWluIiBzaXplPSIxNCIgbWF4bGVuZ3RoPSIxNCI+DQogICAgICAgICAg PGJyPjxmb250IHNpemU9IjIiIGNvbG9yPSIjNjY2NjY2Ij7B98DlIMD8yK0gIA0KICAgICAg ICAgIDwvZm9udD48aW5wdXQgdHlwZT0idGV4dCIgbmFtZT0idGVsbnVtIiBzaXplPSIxMyI+ DQogICAgICAgICAgJm5ic3A7Jm5ic3A7Jm5ic3A7PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiM2 NjY2NjYiPsjetOvG+SA8L2ZvbnQ+PGZvbnQgc2l6ZT0iMiI+PGlucHV0IHR5cGU9InRleHQi IG5hbWU9ImhhbmRudW0iIHNpemU9IjE1Ij4NCiAgICAgICAgICA8L2ZvbnQ+PGlucHV0IHR5 cGU9InN1Ym1pdCIgbmFtZT0iU3VibWl0MiIgdmFsdWU9Ir3Fw7siPiA8L2Zvcm0+DQoNCgkN CiAgICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICAgIDx0cj4NCiAgICAgICAgPHRkIHdpZHRo PSIyOTQiPg0KICAgICAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+PGltZyBzcmM9Imh0dHA6 Ly93d3cuaXllc2NhcmQuY29tL2ltYWdlL2V2ZW50MS5naWYiIHdpZHRoPSIyOTQiIGhlaWdo dD0iMjAwIiBib3JkZXI9IjAiPjwvcD4NCiAgICAgICAgPC90ZD4NCiAgICAgICAgPHRkIHdp ZHRoPSIyOTQiPg0KICAgICAgICAgICAgPHAgYWxpZ249ImNlbnRlciI+PGltZyBzcmM9Imh0 dHA6Ly93d3cuaXllc2NhcmQuY29tL2ltYWdlL2V2ZW50Mi5naWYiIHdpZHRoPSIyOTQiIGhl aWdodD0iMjAwIiBib3JkZXI9IjAiPjwvcD4NCiAgICAgICAgPC90ZD4NCiAgICA8L3RyPg0K ICAgIDx0cj4NCiAgICAgICAgPHRkIHdpZHRoPSI1OTIiIGNvbHNwYW49IjIiPg0KICAgICAg ICAgICAgPHAgYWxpZ249ImxlZnQiPiZuYnNwOzxmb250IHNpemU9IjIiIGZhY2U9IrG8uLIi IGNvbG9yPSIjNjY2NjY2Ij6xzcfPwMcgDQogICAgICAgICAgICC43sDPwda80rTCIMClvK3H zsC7IMXrx9ggvPbB/cfRILDNwMy45ywgsde/3L+hIL7utrDH0SDBpLq4tbUgsK6w7SANCiAg ICAgICAgICAgIMDWwfYgvsrAvcC7ILngyPy0z7TZLjxicj4gJm5ic3A7wMwgRS1tYWlswLog ud+9xcD8v+vAzLjnLCC/+MShIL7KwLi9xyANCiAgICAgICAgICAgILDmv+wgvsa3oSDDor+h ILjewM/B1rzSuKYgwNS3wsfPv6kgwda9w7jpILXOILn4ILTZvcMguN7AzyAmbmJzcDvAzCAN CiAgICAgICAgICAgILChwfYgvsq1tbfPIMfPsNq9wLTPtNkuPC9mb250PjwvcD4NCiAgICAg ICAgPC90ZD4NCiAgICA8L3RyPg0KICAgIDx0cj4NCiAgICAgICAgPHRkIHdpZHRoPSI1ODki IGNvbHNwYW49IjIiPg0KICA8Zm9ybSBuYW1lPSJtYWlsZnJtMiIgYWN0aW9uPSJodHRwOi8v d3d3Lml3b29yaWNhcmQuY29tL21haWwvbm8uYXNwIiBtZXRob2Q9InBvc3QiID4gIAkgIA0K ICAgICAgICAgICAgICAgIDxwIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJtYXJnaW4tbGVmdDow OyI+PGZvbnQgc2l6ZT0iMiIgY29sb3I9IiM2NjY2NjYiPrz2vcWwxbrOIA0KICAgICAgICAg ICAgICAgIC8gcmVmdXNhbCBvZiByZWNlaXB0PC9mb250PiANCiAgICAgICAgICA8aW5wdXQg dHlwZT0idGV4dCIgbmFtZT0iZW1haWwiIHNpemU9IjI1Ij4NCiAgICAgICAgICA8aW5wdXQg dHlwZT0ic3VibWl0IiBuYW1lPSJTdWJtaXQiIHZhbHVlPSJFTlRFUiI+PC9mb3JtPgkNCiAg ICAgICAgPC90ZD4NCiAgICA8L3RyPg0KICAgIDx0cj4NCiAgICAgICAgPHRkIHdpZHRoPSI1 ODkiIGNvbHNwYW49IjIiPg0KCTxwIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWluZGVu dDotMTsgbWFyZ2luLXJpZ2h0OjA7IG1hcmdpbi1sZWZ0OjA7Ij48aW1nIHNyYz0iaHR0cDov L3d3dy5peWVzY2FyZC5jb20vaW1hZ2UvZjMuZ2lmIiB3aWR0aD0iNjAwIiBoZWlnaHQ9IjYw IiBib3JkZXI9IjAiIGFsaWduPSJtaWRkbGUiIHZzcGFjZT0iMCIgaHNwYWNlPSIwIj4gICAg ICAgIDwvdGQ+DQogICAgPC90cj4NCjwvdGFibGU+DQo8cD4mbmJzcDs8L3A+DQo8cD4mbmJz cDs8L3A+DQo8L2JvZHk+DQoNCjwvaHRtbD4NCg0K ------=_NextPart_000_0117_01C0F35A.93A35C00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 20: 0:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2727937B400 for ; Sun, 30 Jun 2002 20:00:20 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F78643E0A for ; Sun, 30 Jun 2002 20:00:19 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701030018.VQYB6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 03:00:18 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA88029; Sun, 30 Jun 2002 19:47:41 -0700 (PDT) Date: Sun, 30 Jun 2002 19:47:40 -0700 (PDT) From: Julian Elischer To: David Xu Cc: "\"Matthew Dillon\"" , sgk@troutmask.apl.washington.edu, wa1ter@hotmail.com, freebsd-current@FreeBSD.ORG Subject: Re: KSE / interrupt panic (patch) In-Reply-To: <002801c220a4$4637c2a0$ef01a8c0@davidwnt> 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 thanks.. I was aware of he race but it looks as if I miscaldulated it somehow.. I will look at the source again and confirm your patch. As you say, msleep() is of the same form and has the same problems. On Mon, 1 Jul 2002, David Xu wrote: > Now let me describe where the race is: > > Thread A: | Thread B: > cv_timedwait() | softclock() > | cv_timedwait_end() > | > mtx_lock_spin(&sched_lock); | mtx_lock_spin(&sched_lock); /* suppose blocked!!! */ > ... | > callout_stop(&td->td_slpcallout) | > td->td_flags |= TDF_TIMEOUT; | > td->td_proc->p_stats->p_ru.ru_nivcsw++; | > // problem, does not set thread state to TDS_SLP!!! | > mi_switch(); | > // run at once again | > ... | > mtx_unlock_spin(&sched_lock); | mtx_lock_spin() returned !!! > thread is still running | if (td->td_flags & TDF_TIMEOUT) { > ... | td->td_flags &= ~TDF_TIMEOUT; > some place call mi_switch() and now on runqueue | setrunqueue(td); // crash > | } > > ---------------------------------------------------------- > here is the patch: > --- /sys/kern/kern_condvar.c.old Mon Jul 1 09:06:01 2002 > +++ /sys/kern/kern_condvar.c Mon Jul 1 09:32:50 2002 > @@ -396,6 +396,7 @@ > * between msleep and endtsleep. > */ > td->td_flags |= TDF_TIMEOUT; > + td->td_state = TDS_SLP; > td->td_proc->p_stats->p_ru.ru_nivcsw++; > mi_switch(); > } > @@ -472,6 +473,7 @@ > * between msleep and endtsleep. > */ > td->td_flags |= TDF_TIMEOUT; > + td->td_state = TDS_SLP; > td->td_proc->p_stats->p_ru.ru_nivcsw++; > mi_switch(); > } > ------------------------------------------------------------------- > > bug is because cv_timedwait() detects timeout callout is running, > but it does not correctly wait callout to complete, so panic. > BTW, the bug seems also exists in msleep() and endtsleep(), please > fix it! > > -David Xu > > > --- David Xu wrote: > > setrunqueue() call can be simply removed from cv_timedwait_end(), because > > there > > is a race in softclock() and callout_stop(), when cv_timedwait_end() losts a > > race, it means that that thread is already running(wokenup by another > > thread), > > when you setrunqueue() it, of course it will panic. > > in cv_timedwait_end(), sentence "if (td->td_flags & TDF_TIMEOUT) {...}" > > is to check this race condition. > > > > -David Xu > > > > ----- Original Message ----- > > From: "Matthew Dillon" > > To: "Julian Elischer" > > Cc: "Steve Kargl" ; "walt" > > ; > > Sent: Monday, July 01, 2002 4:43 AM > > Subject: KSE / interrupt panic > > > > > > > Got another one. Different panic, same place. > > > > > > panic: setrunqueue: bad thread state > > > cpuid = 0; lapic.id = 01000000 > > > Debugger("panic") > > > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > > > db> trace > > > Debugger(c02ec2ba) at Debugger+0x46 > > > panic(c02ec8a9,c6461d80,c6461d80,c6461d80,c01afa30) at panic+0xd6 > > > setrunqueue(c6461d80) at setrunqueue+0x1dd > > > cv_timedwait_end(c6461d80) at cv_timedwait_end+0x36 > > > softclock(0) at softclock+0x159 > > > ithread_loop(c229c700,df3eed48,c22aec00,c01b9c6c,0) at ithread_loop+0x12c > > > fork_exit(c01b9c6c,c229c700,df3eed48) at fork_exit+0xa8 > > > fork_trampoline() at fork_trampoline+0x37 > > > db> gdb > > > ... > > > > > > #0 Debugger (msg=0xc02ec2ba "panic") > > > at /FreeBSD/FreeBSD-current/src/sys/i386/i386/db_interface.c:324 > > > #1 0xc01c878a in panic (fmt=0xc02ec8a9 "setrunqueue: bad thread state") > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_shutdown.c:482 > > > #2 0xc01cc6cd in setrunqueue (td=0xc6461d80) > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_switch.c:396 > > > #3 0xc01afa66 in cv_timedwait_end (arg=0xc6461d80) > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_condvar.c:608 > > > #4 0xc01d22c9 in softclock (dummy=0x0) > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_timeout.c:187 > > > #5 0xc01b9d98 in ithread_loop (arg=0xc229c700) > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_intr.c:535 > > > #6 0xc01b923c in fork_exit (callout=0xc01b9c6c , > > > arg=0xc229c700, frame=0xdf3eed48) > > > at /FreeBSD/FreeBSD-current/src/sys/kern/kern_fork.c:863 > > > > > > I'm not sure why the panic was 'bad thread state' when gdb seems to > > > show it being stuck on 'unexpected ke present'. Maybe it was an > > > optimization and gdb is confused. The panic is definitely > > > 'bad thread state'. > > > > > > (gdb) print td->td_state > > > $2 = TDS_RUNQ > > > > > > setrunqueue() is being called on a thread which is already on the run > > > queue. > > > > > > -Matt > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > __________________________________________________ > > Do You Yahoo!? > > Yahoo! - Official partner of 2002 FIFA World Cup > > http://fifaworldcup.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 Jun 30 20:59: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EB8537B400 for ; Sun, 30 Jun 2002 20:59:00 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7262243E13 for ; Sun, 30 Jun 2002 20:58:59 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g613wr1i011092; Sun, 30 Jun 2002 23:58:54 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <40690.1025103465@axl.seasidesoftware.co.za> References: <40690.1025103465@axl.seasidesoftware.co.za> Date: Sun, 30 Jun 2002 23:58:51 -0400 To: Sheldon Hearn , Szilveszter Adam From: Garance A Drosihn Subject: Re: What's the right way to build XFree86-4 now? Cc: current@FreeBSD.ORG, taguchi@tohoku.iij.ad.jp Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 4:57 PM +0200 6/26/02, Sheldon Hearn wrote: >Here's what I did to get XFree86-4 to build with the base system's >toolchain in -CURRENT: > >a) ports/devel/imake-4: > > Replace files/patch-d and files/patch-xthreads with the attached > patch-config::cf::FreeBSD.cf. > > Add the attached patch-config::cf::bsdLib.tmpl. > >b) ports/x11/XFree86-4-libraries: > > Replace files/patch-z45 with the attached patch-z45. > > Note that this isn't quite right, because the linking gets done with > cc as a front-end, not c++. But the job gets done, all the same, > and I'm not writing a SharedDepCplusplusLibraryTarget rule myself. > :-) > >c) ports/x11-servers/XFree86-4-Server: > > Add the attached patch-gcc31, taken from Motoyuki Konno's post to > with the following Message-ID: > > <200206041243.g54Chxc16331@sakura.mk.bsdclub.org> Have many people had a chance to test this? I wanted to try it out this weekend, but I lost most of the weekend due to other problems with compiling current on my test machine. I finally got by those problems, but now it's midnight on Sunday and I can't really afford to start on this right now... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 21: 0:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2606D37B400 for ; Sun, 30 Jun 2002 21:00:50 -0700 (PDT) Received: from ref5.freebsd.org (ref5.FreeBSD.org [216.136.204.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3E3943E09 for ; Sun, 30 Jun 2002 21:00:49 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from ref5.freebsd.org (localhost [127.0.0.1]) by ref5.freebsd.org (8.12.5/8.12.5) with ESMTP id g6140n7b025135 for ; Sun, 30 Jun 2002 21:00:49 -0700 (PDT) (envelope-from des@ref5.freebsd.org) Received: (from des@localhost) by ref5.freebsd.org (8.12.5/8.12.5/Submit) id g6140nqf025123 for current@freebsd.org; Sun, 30 Jun 2002 21:00:49 -0700 (PDT) Date: Sun, 30 Jun 2002 21:00:49 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200207010400.g6140nqf025123@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 /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> bin/realpath ===> bin/rm ===> bin/rmdir ===> bin/setfacl ===> bin/sh ===> bin/sleep ===> bin/stty ===> bin/sync ===> bin/test /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/libexec/elf/ld: cannot open /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/lib/crt1.o: Interrupted system call *** Error code 1 Stop in /local0/scratch/des/src/bin/test. *** Error code 1 Stop in /local0/scratch/des/src/bin. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 22:11:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE9837B400 for ; Sun, 30 Jun 2002 22:11:39 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A8FD43E09 for ; Sun, 30 Jun 2002 22:11:38 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 5243 invoked by uid 0); 1 Jul 2002 05:11:36 -0000 Received: from pd900332a.dip.t-dialin.net (HELO gmx.net) (217.0.51.42) by mail.gmx.net (mp001-rz3) with SMTP; 1 Jul 2002 05:11:36 -0000 Message-ID: <3D1FE483.4010002@gmx.net> Date: Mon, 01 Jul 2002 07:11:31 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Post-KSE desaster X-Enigmail-Version: 0.61.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig616F59A84514CDE2316F7158" 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 The following is an OpenPGP/MIME signed message created by Enigmail/Mozilla, following RFC 2440 and RFC 2015 --------------enig616F59A84514CDE2316F7158 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Everything that links to libc_r is now completely hosed here, this includes all of KDE. Since KDE is a tad too big to make a handy test, here comes ogg123 from the vorbis-tools port: [lofi@kiste]:1:~ > gdb ogg123 GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 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-undermydesk-freebsd"... (no debugging symbols found)... (gdb) run /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02­Ordinary_World.ogg Starting program: /usr/local/bin/ogg123 /home/lofi/mp3/Duran_Duran/The_Wedding_A lbum/02­Ordinary_World.ogg (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... Device: OSS audio driver output Author: Aaron Holtzman Comments: Outputs audio to the Open Sound System driver. Playing: /home/lofi/mp3/Duran_Duran/The_Wedding_Album/02­Ordinary_World.ogg Title: Ordinary World Artist: Duran Duran Album: The Wedding Album (no debugging symbols found)...(no debugging symbols found)...ffer 6.2% Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish --------------enig616F59A84514CDE2316F7158 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9H+SHXhc68WspdLARAhxPAJ4h2owyFxKwoVZh97la6n565NGL6wCfZ5hE 6xLPSQSVnzyi/AYjrS9jj00= =KIXi -----END PGP SIGNATURE----- --------------enig616F59A84514CDE2316F7158-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 22:31: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F10137B400 for ; Sun, 30 Jun 2002 22:30:59 -0700 (PDT) Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A9EC43E13 for ; Sun, 30 Jun 2002 22:30:59 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17Otm4-0000V5-00; Sun, 30 Jun 2002 22:30:56 -0700 Date: Sun, 30 Jun 2002 22:30:56 -0700 To: Michael Nottebrock Cc: freebsd-current@freebsd.org, Bill Huey Subject: Re: Post-KSE desaster Message-ID: <20020701053056.GA1907@gnuppy.monkey.org> References: <3D1FE483.4010002@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D1FE483.4010002@gmx.net> User-Agent: Mutt/1.4i From: Bill Huey 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, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > (gdb) bt > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > /usr/lib/libc_r.so.5 > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > #2 0xd0d0d0d0 in ?? () > #3 0x080570b0 in ?? () This is unlikely to be a KSE problem. What do the rest of the threads look like ? Try "info threads" in gdb and then progressively walking through the thread list with "thread N", N being the thread number. I ran into a funny create at thread start up time crash and I'm wondering if it could be the same thing. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 22:39:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2130237B400 for ; Sun, 30 Jun 2002 22:39:13 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1041343E09 for ; Sun, 30 Jun 2002 22:39:12 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 29929 invoked by uid 0); 1 Jul 2002 05:39:09 -0000 Received: from pd900332a.dip.t-dialin.net (HELO gmx.net) (217.0.51.42) by mail.gmx.net (mp008-rz3) with SMTP; 1 Jul 2002 05:39:09 -0000 Message-ID: <3D1FEAFA.4090500@gmx.net> Date: Mon, 01 Jul 2002 07:39:06 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Huey Cc: freebsd-current@freebsd.org Subject: Re: Post-KSE desaster References: <3D1FE483.4010002@gmx.net> <20020701053056.GA1907@gnuppy.monkey.org> X-Enigmail-Version: 0.61.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA13CC028C41EBC1118B50277" 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 The following is an OpenPGP/MIME signed message created by Enigmail/Mozilla, following RFC 2440 and RFC 2015 --------------enigA13CC028C41EBC1118B50277 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Bill Huey wrote: > Try "info threads" in gdb and then progressively walking through the thread > list with "thread N", N being the thread number. (...) Program received signal SIGSEGV, Segmentation fault. 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread 3 Process 14606, Thread 3 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 2 Process 14606, Thread 2 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 * 1 Process 14606, Thread 1 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) thread 1 [Switching to thread 1 (Process 14606, Thread 1)]#0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x080570b0 in ?? () (gdb) thread 2 [Switching to thread 2 (Process 14606, Thread 2)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc502 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #2 0x281ced1d in pthread_cond_timedwait () from /usr/lib/libc_r.so.5 #3 0x281c58f2 in _thread_gc () from /usr/lib/libc_r.so.5 #4 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 (gdb) thread 3 [Switching to thread 3 (Process 14606, Thread 3)]#0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x281cbd4e in _thread_kern_sched () from /usr/lib/libc_r.so.5 #1 0x281cc49d in _thread_kern_sched_state () from /usr/lib/libc_r.so.5 #2 0x281c60ff in _write () from /usr/lib/libc_r.so.5 #3 0x281c6187 in write () from /usr/lib/libc_r.so.5 #4 0x2828ccc2 in ao_plugin_play () from /usr/local/lib/ao/plugins-2/liboss.so #5 0x280b4f8d in ao_play () from /usr/local/lib/libao.so.3 #6 0x08049bed in free () #7 0x0804a9a1 in free () #8 0x0804a066 in free () #9 0x281c4f31 in _thread_start () from /usr/lib/libc_r.so.5 As a comparison, artsd: [lofi@kiste]:0:~ > gdb artsd GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 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-undermydesk-freebsd"... (no debugging symbols found)... (gdb) run Starting program: /usr/local/bin/artsd (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... unix_connect: can't connect to server (unix:/tmp/mcop-lofi/kiste_localdomain-01c2-3d1fe3ca) There are already artsd objects registered, looking if they are active... ... cleaned 5 unused mcop global references. (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) info thread * 1 Process 15847, Thread 1 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) bt #0 0x28424918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x284242e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish --------------enigA13CC028C41EBC1118B50277 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9H+r9Xhc68WspdLARAjBeAJ4/DNzkpJPBoBpCKCrSh6SvnPjbZwCfaAE9 oDGQY9axC8GdbNBlw3t951M= =2w8b -----END PGP SIGNATURE----- --------------enigA13CC028C41EBC1118B50277-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 22:54: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D86C37B400 for ; Sun, 30 Jun 2002 22:54:06 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF9F643E09 for ; Sun, 30 Jun 2002 22:54:05 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with ESMTP id g615s47C011338; Mon, 1 Jul 2002 01:54:04 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Jul 2002 01:54:03 -0400 (EDT) From: Wesley Morgan To: Bill Huey Cc: Michael Nottebrock , Subject: Re: Post-KSE desaster In-Reply-To: <20020701053056.GA1907@gnuppy.monkey.org> Message-ID: <20020701015122.I11313-100000@volatile.chemikals.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 I see this problem too. Luckily I have my entire KDE and QT system build with debugging symbols... However, the problem is definitely in the libc_r... I get virtually the same dump as Michael. #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #2 0xd0d0d0d0 in ?? () #3 0x00000001 in ?? () #4 0x00005f28 in ?? () On Sun, 30 Jun 2002, Bill Huey wrote: > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > Program received signal SIGSEGV, Segmentation fault. > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > (gdb) bt > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > /usr/lib/libc_r.so.5 > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > #2 0xd0d0d0d0 in ?? () > > #3 0x080570b0 in ?? () > > This is unlikely to be a KSE problem. > > What do the rest of the threads look like ? > > Try "info threads" in gdb and then progressively walking through the thread > list with "thread N", N being the thread number. I ran into a funny > create at thread start up time crash and I'm wondering if it could > be the same thing. > > bill > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 22:56: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D2F637B400 for ; Sun, 30 Jun 2002 22:55:57 -0700 (PDT) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 943C043E0A for ; Sun, 30 Jun 2002 22:55:56 -0700 (PDT) (envelope-from chuckr@april.chuckr.org) Received: from localhost (chuckr@localhost) by april.chuckr.org (8.11.6/8.11.3) with ESMTP id g615tkE60446 for ; Mon, 1 Jul 2002 01:55:46 -0400 (EDT) (envelope-from chuckr@april.chuckr.org) Date: Mon, 1 Jul 2002 01:55:45 -0400 (EDT) From: Chuck Robey To: FreeBSD-current Subject: getting back to current Message-ID: <20020701013954.W378-100000@april.chuckr.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 I've just finished going thru another medical session, this one took about 5 months, and because of the extended time spent away, I'm running 4.5 (I've been running current since 1.1, this feels really odd). I need a little bit of help (or advice, maybe) to get me back to current. I just finished cvsupping, and the main sources built just fine. I installed a new config (static, the libs are now too old) and fixed all the changes in my config file, so now my kernel file configs .... but it doesn't build (breaks in 'make depend', I think in genassym). I'm guessing that this is only one of a string of incompatibilities, in jumping from 4.5 back to current. I could drag myself thru fixing the bugs I'm hitting, but I was wondering if I could get someone to use my config file (on freefall, APRIL and APRIL.hints, in ~chuckr/) and build me a kernel and a set of modules. I'm asking this because my health isn't yet back fully, and I would like to shortcut this a bit. [my FreeBSD machine is april.chuckr.org, hence the config filename]. I'm not sure what changes have occurred in kernel/module installation, but *you'd* have to be really sure about that, because I wouldn't want someone to scrag their system whilst doing me a favor. If you're not certain, please don't even offer, I'd hate to be the cause of your system meltdown. I appreciate any consideration I get ... ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 23: 3:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89C9137B400 for ; Sun, 30 Jun 2002 23:03:48 -0700 (PDT) Received: from sbk-gw.sibnet.ru (sbk-gw.sibnet.ru [217.70.96.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47BC043E09 for ; Sun, 30 Jun 2002 23:03:44 -0700 (PDT) (envelope-from stranger@sberbank.sibnet.ru) Received: from sbk-gw.sibnet.ru (localhost.sibnet.ru [127.0.0.1]) by sbk-gw.sibnet.ru (8.12.5/8.12.5) with ESMTP id g6163fKQ093118 for ; Mon, 1 Jul 2002 13:03:41 +0700 (NOVST) (envelope-from stranger@sberbank.sibnet.ru) Received: from localhost (stranger@localhost) by sbk-gw.sibnet.ru (8.12.5/8.12.5/Submit) with ESMTP id g6163eiH093115 for ; Mon, 1 Jul 2002 13:03:40 +0700 (NOVST) X-Authentication-Warning: sbk-gw.sibnet.ru: stranger owned process doing -bs Date: Mon, 1 Jul 2002 13:03:40 +0700 (NOVST) From: "Maxim M. Kazachek" X-X-Sender: stranger@sbk-gw.sibnet.ru To: freebsd-current@freebsd.org Subject: Is pcm broken? Message-ID: <20020701130018.K92214-100000@sbk-gw.sibnet.ru> 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 Looks like someone broke AC97 rate measurement in -CURRENT -STABLE measures AC97 rate well (about 55900). Current gives about 41000... Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT) Both are i815 equipped with SoundMAX AC97 codec... Sincerely, Maxim M. Kazachek mailto:stranger@sberbank.sibnet.ru mailto:stranger@fpm.ami.nstu.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 23:20:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34DED37B4B1 for ; Sun, 30 Jun 2002 23:20:30 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D44E43E13 for ; Sun, 30 Jun 2002 23:20:26 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701062025.ZOUE6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 06:20:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA88795; Sun, 30 Jun 2002 23:03:11 -0700 (PDT) Date: Sun, 30 Jun 2002 23:03:09 -0700 (PDT) From: Julian Elischer To: Bill Huey Cc: Michael Nottebrock , freebsd-current@freebsd.org Subject: Re: Post-KSE desaster In-Reply-To: <20020701053056.GA1907@gnuppy.monkey.org> 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 It COULD be related to KSE if I've broken some signal delivery types.. do we have a signal guru in the house that can run a diagnostic on signals? On Sun, 30 Jun 2002, Bill Huey wrote: > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > Program received signal SIGSEGV, Segmentation fault. > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > (gdb) bt > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > /usr/lib/libc_r.so.5 > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > #2 0xd0d0d0d0 in ?? () > > #3 0x080570b0 in ?? () > > This is unlikely to be a KSE problem. > > What do the rest of the threads look like ? > > Try "info threads" in gdb and then progressively walking through the thread > list with "thread N", N being the thread number. I ran into a funny > create at thread start up time crash and I'm wondering if it could > be the same thing. > > bill > > > 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 Jun 30 23:20:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C23237B407 for ; Sun, 30 Jun 2002 23:20:38 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3D5943E09 for ; Sun, 30 Jun 2002 23:20:37 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701062036.ZOVT6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 06:20:36 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA88816; Sun, 30 Jun 2002 23:09:07 -0700 (PDT) Date: Sun, 30 Jun 2002 23:09:06 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: Bill Huey , Michael Nottebrock , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE desaster In-Reply-To: <20020701015122.I11313-100000@volatile.chemikals.org> 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 My guess is that it's relying on getting a signal for pre-emtion and it's not arriving due to KSE breakage. On Mon, 1 Jul 2002, Wesley Morgan wrote: > I see this problem too. Luckily I have my entire KDE and QT system build > with debugging symbols... However, the problem is definitely in the > libc_r... I get virtually the same dump as Michael. > > #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > #2 0xd0d0d0d0 in ?? () > #3 0x00000001 in ?? () > #4 0x00005f28 in ?? () > > > > On Sun, 30 Jun 2002, Bill Huey wrote: > > > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > > Program received signal SIGSEGV, Segmentation fault. > > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > (gdb) bt > > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > > /usr/lib/libc_r.so.5 > > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > #2 0xd0d0d0d0 in ?? () > > > #3 0x080570b0 in ?? () > > > > This is unlikely to be a KSE problem. > > > > What do the rest of the threads look like ? > > > > Try "info threads" in gdb and then progressively walking through the thread > > list with "thread N", N being the thread number. I ran into a funny > > create at thread start up time crash and I'm wondering if it could > > be the same thing. > > > > bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > 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 Jun 30 23:27:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7332637B400 for ; Sun, 30 Jun 2002 23:27:45 -0700 (PDT) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 347B943E13 for ; Sun, 30 Jun 2002 23:27:45 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from FreeBSD.org (12-234-90-219.client.attbi.com [12.234.90.219]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 19AB28B5D0; Sun, 30 Jun 2002 23:27:44 -0700 (PDT) Message-ID: <3D1FF65C.E8AC60B5@FreeBSD.org> Date: Sun, 30 Jun 2002 23:27:40 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; FreeBSD 4.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey Cc: FreeBSD-current Subject: Re: getting back to current References: <20020701013954.W378-100000@april.chuckr.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 Chuck Robey wrote: > > I've just finished going thru another medical session, this one took about > 5 months, and because of the extended time spent away, I'm running 4.5 > (I've been running current since 1.1, this feels really odd). I need > a little bit of help (or advice, maybe) to get me back to current. Glad to hear you're feeling better. :) The bad news is that this is a really terrible time to upgrade to -current. The KSE mark III update just went in, so things are very unstable right now. > I just finished cvsupping, and the main sources built just fine. I > installed a new config (static, the libs are now too old) and fixed all > the changes in my config file, so now my kernel file configs .... but it > doesn't build (breaks in 'make depend', I think in genassym). I'm > guessing that this is only one of a string of incompatibilities, in > jumping from 4.5 back to current. At this point, the only way to build -current on a -stable system is make buildworld; make buildkernel. Make sure that KERNCONF is defined in /etc/make.conf. You'll probably want to read -current and cvs-all for a while before you finish the upgrade though.... HTH, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 23:32:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8E8B37B400 for ; Sun, 30 Jun 2002 23:32:18 -0700 (PDT) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C4F243E35 for ; Sun, 30 Jun 2002 23:32:18 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from FreeBSD.org (12-234-90-219.client.attbi.com [12.234.90.219]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 5143F8B5BE; Sun, 30 Jun 2002 23:32:18 -0700 (PDT) Message-ID: <3D1FF771.CED62563@FreeBSD.org> Date: Sun, 30 Jun 2002 23:32:17 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; FreeBSD 4.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Chuck Robey , FreeBSD-current Subject: Re: getting back to current References: <20020701013954.W378-100000@april.chuckr.org> <3D1FF65C.E8AC60B5@FreeBSD.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 Doug Barton wrote: > At this point, the only way to build -current on a -stable system is > make buildworld; make buildkernel. Make sure that KERNCONF is defined in > /etc/make.conf. I left out, read /usr/src/UPDATING in the -current source tree, there are a lot of other steps... the above just gets your stuff built. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 30 23:40:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72E3F37B406 for ; Sun, 30 Jun 2002 23:40:26 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7996243E1A for ; Sun, 30 Jun 2002 23:40:25 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701064024.ZVGK6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 06:40:24 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA88923; Sun, 30 Jun 2002 23:27:09 -0700 (PDT) Date: Sun, 30 Jun 2002 23:27:08 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: Bill Huey , Michael Nottebrock , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701015122.I11313-100000@volatile.chemikals.org> 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 Can someone please check out a libc_r tree as of 3 days ago and try that... There was a commit in libc_r/uthreads 2 days ago that might be relevant. failing that, can someone try newly compiled utilities on an older pre-KSE kernel? We need to eliminate one of these two changes... I think it's likely that it's breakage in signals from KSE but I'd like to know that before I tear even more hair out chasing this.. SO, I'm suffering from brain fade now.. but please, signals is known to be in dire need of cleanup after the KSE edit, (signals are delivered to processes but can effect individual threads. yuck) Anyone who can help identify the problem please do.. I'm off to bed before my head explodes.. I'll be back tomorrow AM. I'm going to spend as much of msuspension sleeping as possible :-) On Mon, 1 Jul 2002, Wesley Morgan wrote: > I see this problem too. Luckily I have my entire KDE and QT system build > with debugging symbols... However, the problem is definitely in the > libc_r... I get virtually the same dump as Michael. > > #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > #2 0xd0d0d0d0 in ?? () > #3 0x00000001 in ?? () > #4 0x00005f28 in ?? () > > > > On Sun, 30 Jun 2002, Bill Huey wrote: > > > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > > Program received signal SIGSEGV, Segmentation fault. > > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > (gdb) bt > > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > > /usr/lib/libc_r.so.5 > > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > #2 0xd0d0d0d0 in ?? () > > > #3 0x080570b0 in ?? () > > > > This is unlikely to be a KSE problem. > > > > What do the rest of the threads look like ? > > > > Try "info threads" in gdb and then progressively walking through the thread > > list with "thread N", N being the thread number. I ran into a funny > > create at thread start up time crash and I'm wondering if it could > > be the same thing. > > > > bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > 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 Jun 30 23:59:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F33537B400 for ; Sun, 30 Jun 2002 23:59:14 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AEF43E09 for ; Sun, 30 Jun 2002 23:59:13 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with ESMTP id g616x97C011736; Mon, 1 Jul 2002 02:59:10 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Jul 2002 02:59:09 -0400 (EDT) From: Wesley Morgan To: Julian Elischer Cc: Bill Huey , Michael Nottebrock , Subject: Re: Post-KSE disaster with libc_r In-Reply-To: Message-ID: <20020701024638.X11550-100000@volatile.chemikals.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 Reverting to: uthread_sigpending.c 1.8 uthread_sigsuspend.c 1.11 Makefile.inc 1.32 Has no effect. As far as I can tell theres no more changes... Looking at some ktrace / gdb output shows the funny business starting right after kdeinit tries to fork into something else: 2723 kdeinit CALL gettimeofday(0x28e94ab8,0) 2723 kdeinit RET gettimeofday 0 2723 kdeinit CALL wait4(0xffffffff,0,0x1,0) 2723 kdeinit RET wait4 2724/0xaa4 2723 kdeinit CALL poll(0x8059000,0x1,0) 2723 kdeinit RET poll 1 2723 kdeinit PSIG SIGSEGV SIG_DFL 2723 kdeinit NAMI "kdeinit.core" Both the kdeinit and a child it forks are dying... Setting a breakpoint of fork() in the binary shows: Breakpoint 1, 0x28eda7d4 in fork () from /usr/lib/libc.so.5 (gdb) bt #0 0x28eda7d4 in fork () from /usr/lib/libc.so.5 #1 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 #2 0x0804e8d5 in QGListIterator::~QGListIterator() () #3 0x0804add1 in QGListIterator::~QGListIterator() () (gdb) s Single stepping until exit from function fork, which has no line number information. 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 (gdb) Single stepping until exit from function fork, which has no line number information. warning: Cannot insert breakpoint 0: Error accessing memory address 0xd0d0d0d0: Bad address. (gdb) the 0xd0d0d0d0 is the same as in the coredump earlier. Rebuilt libc_r with debugging symbols and... (gdb) bt #0 thread_kern_poll (wait_reqd=0) at /usr/src/lib/libc_r/uthread/uthread_kern.c:862 #1 0x28e8c8d7 in _thread_kern_scheduler () at /usr/src/lib/libc_r/uthread/uthread_kern.c:372 #2 0xd0d0d0d0 in ?? () #3 0x00000001 in ?? () #4 0x00005f28 in ?? () Error accessing memory address 0xbecf2000: Bad address. Hope some of this is useful to anyone out there! On Sun, 30 Jun 2002, Julian Elischer wrote: > Can someone please check out a libc_r tree as of 3 days ago > and try that... > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > failing that, can someone try newly compiled utilities on an older pre-KSE > kernel? > > We need to eliminate one of these two changes... > > I think it's likely that it's breakage in signals from KSE > but I'd like to know that before I tear even more hair out chasing this.. > > SO, I'm suffering from brain fade now.. > but please, signals is known to be in dire need of cleanup > after the KSE edit, (signals are delivered to processes but can effect > individual threads. yuck) > > Anyone who can help identify the problem please do.. I'm off to bed before > my head explodes.. > I'll be back tomorrow AM. > I'm going to spend as much of msuspension sleeping as possible :-) > > On Mon, 1 Jul 2002, Wesley Morgan wrote: > > > I see this problem too. Luckily I have my entire KDE and QT system build > > with debugging symbols... However, the problem is definitely in the > > libc_r... I get virtually the same dump as Michael. > > > > #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > #2 0xd0d0d0d0 in ?? () > > #3 0x00000001 in ?? () > > #4 0x00005f28 in ?? () > > > > > > > > On Sun, 30 Jun 2002, Bill Huey wrote: > > > > > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > > > Program received signal SIGSEGV, Segmentation fault. > > > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > > (gdb) bt > > > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > > > /usr/lib/libc_r.so.5 > > > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > > #2 0xd0d0d0d0 in ?? () > > > > #3 0x080570b0 in ?? () > > > > > > This is unlikely to be a KSE problem. > > > > > > What do the rest of the threads look like ? > > > > > > Try "info threads" in gdb and then progressively walking through the thread > > > list with "thread N", N being the thread number. I ran into a funny > > > create at thread start up time crash and I'm wondering if it could > > > be the same thing. > > > > > > bill > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > -- > > _ __ ___ ____ ___ ___ ___ > > Wesley N Morgan _ __ ___ | _ ) __| \ > > morganw@chemikals.org _ __ | _ \._ \ |) | > > FreeBSD: The Power To Serve _ |___/___/___/ > > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0: 0:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 143EE37B401 for ; Mon, 1 Jul 2002 00:00:38 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9185043E1D for ; Mon, 1 Jul 2002 00:00:37 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701070037.NUBN8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Mon, 1 Jul 2002 07:00:37 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA89003 for ; Sun, 30 Jun 2002 23:40:22 -0700 (PDT) Date: Sun, 30 Jun 2002 23:40:20 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: Request for UPDATING notice In-Reply-To: <3D1FF771.CED62563@FreeBSD.org> 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 Who's doing UPDATING now? can someone who is allowed to commit to it put in a note that right now might be a bad time to upgade if you want to use anything that uses libc_r. Either libc_r or KSE is causing problems. I don't yet know which. Things that use libc_r include KDE and GNOME apparently. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0: 8:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEAD537B400; Mon, 1 Jul 2002 00:08:49 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F16643E0A; Mon, 1 Jul 2002 00:08:48 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17OvJi-000LZP-00; Mon, 01 Jul 2002 09:09:46 +0200 Date: Mon, 1 Jul 2002 09:09:46 +0200 From: Sheldon Hearn To: Jeremy Lea Cc: current@FreeBSD.ORG, taguchi@tohoku.iij.ad.jp Subject: Re: What's the right way to build XFree86-4 now? Message-ID: <20020701070946.GA82907@starjuice.net> Mail-Followup-To: Jeremy Lea , current@FreeBSD.ORG, taguchi@tohoku.iij.ad.jp References: <20020626112557.GA958@starjuice.net> <40690.1025103465@axl.seasidesoftware.co.za> <20020630004644.A92462@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020630004644.A92462@shale.csir.co.za> User-Agent: Mutt/1.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 On (2002/06/30 00:46), Jeremy Lea wrote: > +#ifndef SharedDepCplusplusLibraryTarget > +#define SharedDepCplusplusLibraryTarget [...] This patch would fix the build. Did it also fix the linking problems involving -lstdc++ for glxinfo, or were the patches that handle ${CXXLIB} still required? 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 Jul 1 0:14:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CA7437B400 for ; Mon, 1 Jul 2002 00:14:23 -0700 (PDT) Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08DDC43E0A for ; Mon, 1 Jul 2002 00:14:23 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17OvO5-0000ai-00; Mon, 01 Jul 2002 00:14:17 -0700 Date: Mon, 1 Jul 2002 00:14:17 -0700 To: Wesley Morgan Cc: Julian Elischer , Michael Nottebrock , freebsd-current@FreeBSD.ORG, Bill Huey Subject: Re: Post-KSE disaster with libc_r Message-ID: <20020701071417.GA2208@gnuppy.monkey.org> References: <20020701024638.X11550-100000@volatile.chemikals.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020701024638.X11550-100000@volatile.chemikals.org> User-Agent: Mutt/1.4i From: Bill Huey 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, Jul 01, 2002 at 02:59:09AM -0400, Wesley Morgan wrote: > 2723 kdeinit CALL gettimeofday(0x28e94ab8,0) > 2723 kdeinit RET gettimeofday 0 > 2723 kdeinit CALL wait4(0xffffffff,0,0x1,0) > 2723 kdeinit RET wait4 2724/0xaa4 > 2723 kdeinit CALL poll(0x8059000,0x1,0) > 2723 kdeinit RET poll 1 > 2723 kdeinit PSIG SIGSEGV SIG_DFL > 2723 kdeinit NAMI "kdeinit.core" > > Both the kdeinit and a child it forks are dying... Setting a breakpoint of > fork() in the binary shows: That's almost definitely the same problem I'm running into with the JVM, however it registered itself has an infinite hang since SEGV deliveries are turned off when inside in a crashing/SEGVing libc_r thread-kernel. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0:20:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AFC37B400 for ; Mon, 1 Jul 2002 00:20:08 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE0B943E09 for ; Mon, 1 Jul 2002 00:20:07 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701072007.NYFD8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Mon, 1 Jul 2002 07:20:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id AAA89195 for ; Mon, 1 Jul 2002 00:09:20 -0700 (PDT) Date: Mon, 1 Jul 2002 00:09:19 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: UMA question.. 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 Jeff , (current included because it may be an interesting answer) As you know I'm using UMA to allocate threads and cache them. The 'constructor methods allow me to allocated threads that have been pre-set up with thread stacks and other special items. When they are being cached they still have their stacks etc. attached to them. These are only splitt off when the UMA decides to stop caching an item and actualy return it's memory to the system. In this regard the UMA allocator is not a memory alocator but a 'complex object allocator'... Very cool. Now my question.. I ant to allocate proc structures the same way... in other words, I want a cached proc structure to already have a thread attached to it and a stack attached to the thread.. Is it legal for teh init function which is called by UMA to in turn call UMA to allocate a sub element.. so if I do uma_zalloc(proc args) that in turn should do a uma_zalloc(thread args). would this work? is it legal? I need to allocate extra threads independantly of processes, but I could work it so that freed process structures always had a single thread left on them, which would save on allocations.. In the future I need to do teh same for KSEs and KSEGRPS. sp having UMA cache pre-constructed complex items made up of groups of separatly UMA-allocated objects would be a great saving.. the question is.. will it work? can I call UMA from withing a UMA constructor? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0:26: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC1AF37B400 for ; Mon, 1 Jul 2002 00:26:06 -0700 (PDT) Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCB6343E0A for ; Mon, 1 Jul 2002 00:26:05 -0700 (PDT) (envelope-from imp@village.org) 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 g617Q4Y24026; Mon, 1 Jul 2002 01:26:04 -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 g617Q3G41238; Mon, 1 Jul 2002 01:26:04 -0600 (MDT) (envelope-from imp@village.org) Date: Mon, 01 Jul 2002 01:25:26 -0600 (MDT) Message-Id: <20020701.012526.17249506.imp@village.org> To: julian@elischer.org Cc: current@FreeBSD.ORG Subject: Re: Request for UPDATING notice From: "M. Warner Losh" In-Reply-To: References: <3D1FF771.CED62563@FreeBSD.org> 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: Julian Elischer writes: : Who's doing UPDATING now? Nobody owns it. I've committed your change. I have a few more changes I should commit. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0:40:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AF6237B400 for ; Mon, 1 Jul 2002 00:40:10 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4B9443E1D for ; Mon, 1 Jul 2002 00:40:09 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701074009.OCCB8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Mon, 1 Jul 2002 07:40:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id AAA89304 for ; Mon, 1 Jul 2002 00:33:42 -0700 (PDT) Date: Mon, 1 Jul 2002 00:33:41 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: is buildworld broken? 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 I just cvsup'd but when I do a "make buildworld" get: [...] [stuff that scrolled off] [...] Warning: this is the location of the previous definition In file included from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/att.h:22, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/tconfig.h:10, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/hconfig.h:2, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/timevar.c:22: /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:70: warning: `TARGET_DEFAULT' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:400: warning: this is the location of the previous definition /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:83: warning: `FUNCTION_VALUE_REGNO_P' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:1654: warning: this is the location of the previous definition In file included from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/att.h:22, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/tconfig.h:10, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/hconfig.h:2, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/ssa-dce.c:70: /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:70: warning: `TARGET_DEFAULT' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:400: warning: this is the location of the previous definition /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:83: warning: `FUNCTION_VALUE_REGNO_P' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:1654: warning: this is the location of the previous definition In file included from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/att.h:22, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/tconfig.h:10, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/hconfig.h:2, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/ssa-ccp.c:62: /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:70: warning: `TARGET_DEFAULT' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:400: warning: this is the location of the previous definition /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/unix.h:83: warning: `FUNCTION_VALUE_REGNO_P' redefined /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.h:1654: warning: this is the location of the previous definition In file included from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/att.h:22, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/tconfig.h:10, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/hconfig.h:2, from /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/df.c:158: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0:40:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D0F37B405 for ; Mon, 1 Jul 2002 00:40:11 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B3FC43E0A for ; Mon, 1 Jul 2002 00:40:11 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701074010.OCCF8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 07:40:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id AAA89254; Mon, 1 Jul 2002 00:25:00 -0700 (PDT) Date: Mon, 1 Jul 2002 00:24:58 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: Bill Huey , Michael Nottebrock , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701024638.X11550-100000@volatile.chemikals.org> 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 On Mon, 1 Jul 2002, Wesley Morgan wrote: > > Both the kdeinit and a child it forks are dying... Setting a breakpoint of > fork() in the binary shows: > > > Breakpoint 1, 0x28eda7d4 in fork () from /usr/lib/libc.so.5 > (gdb) bt > #0 0x28eda7d4 in fork () from /usr/lib/libc.so.5 > #1 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 > #2 0x0804e8d5 in QGListIterator::~QGListIterator() () > #3 0x0804add1 in QGListIterator::~QGListIterator() () > (gdb) s > Single stepping until exit from function fork, > which has no line number information. > 0x28e83a5c in fork () from /usr/lib/libc_r.so.5 > (gdb) > Single stepping until exit from function fork, > which has no line number information. > warning: Cannot insert breakpoint 0: > Error accessing memory address 0xd0d0d0d0: Bad address. > (gdb) > > the 0xd0d0d0d0 is the same as in the coredump earlier. > > Rebuilt libc_r with debugging symbols and... > In the ktrace, an you show context switches? (add -w to both ktrace and kdump) Is this where is broke? it doesn't look much like the above.. > > (gdb) bt > #0 thread_kern_poll (wait_reqd=0) > at /usr/src/lib/libc_r/uthread/uthread_kern.c:862 > #1 0x28e8c8d7 in _thread_kern_scheduler () > at /usr/src/lib/libc_r/uthread/uthread_kern.c:372 > #2 0xd0d0d0d0 in ?? () > #3 0x00000001 in ?? () > #4 0x00005f28 in ?? () > Error accessing memory address 0xbecf2000: Bad address. > can you do what you did before and try singlestep a bit? also.. instead of checking out an older libc_r, can you try see if there is actually on old copy (say from teh DP1-image) somewhere and try that... it's possible we have symbol polution problemm.. a lot of the names in libc_r look awfully familliar from the KSE code.. (this shouldn;t be possible but.... > Hope some of this is useful to anyone out there! not on its own, but as a part of a developing picture. > > On Sun, 30 Jun 2002, Julian Elischer wrote: > > > Can someone please check out a libc_r tree as of 3 days ago > > and try that... > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > failing that, can someone try newly compiled utilities on an older pre-KSE > > kernel? > > > > We need to eliminate one of these two changes... > > > > I think it's likely that it's breakage in signals from KSE > > but I'd like to know that before I tear even more hair out chasing this.. > > > > SO, I'm suffering from brain fade now.. > > but please, signals is known to be in dire need of cleanup > > after the KSE edit, (signals are delivered to processes but can effect > > individual threads. yuck) > > > > Anyone who can help identify the problem please do.. I'm off to bed before > > my head explodes.. > > I'll be back tomorrow AM. > > I'm going to spend as much of msuspension sleeping as possible :-) > > > > On Mon, 1 Jul 2002, Wesley Morgan wrote: > > > > > I see this problem too. Luckily I have my entire KDE and QT system build > > > with debugging symbols... However, the problem is definitely in the > > > libc_r... I get virtually the same dump as Michael. > > > > > > #0 0x28e8d280 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > #1 0x28e8c9a7 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > #2 0xd0d0d0d0 in ?? () > > > #3 0x00000001 in ?? () > > > #4 0x00005f28 in ?? () > > > > > > > > > > > > On Sun, 30 Jun 2002, Bill Huey wrote: > > > > > > > On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote: > > > > > Program received signal SIGSEGV, Segmentation fault. > > > > > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > > > (gdb) bt > > > > > #0 0x281cc918 in _thread_kern_sched_state_unlock () from > > > > > /usr/lib/libc_r.so.5 > > > > > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 > > > > > #2 0xd0d0d0d0 in ?? () > > > > > #3 0x080570b0 in ?? () > > > > > > > > This is unlikely to be a KSE problem. > > > > > > > > What do the rest of the threads look like ? > > > > > > > > Try "info threads" in gdb and then progressively walking through the thread > > > > list with "thread N", N being the thread number. I ran into a funny > > > > create at thread start up time crash and I'm wondering if it could > > > > be the same thing. > > > > > > > > bill > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > -- > > > _ __ ___ ____ ___ ___ ___ > > > Wesley N Morgan _ __ ___ | _ ) __| \ > > > morganw@chemikals.org _ __ | _ \._ \ |) | > > > FreeBSD: The Power To Serve _ |___/___/___/ > > > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > -- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 0:59:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABE0637B401 for ; Mon, 1 Jul 2002 00:59:55 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF8D43E26 for ; Mon, 1 Jul 2002 00:59:52 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17Ow6z-000Lf4-00; Mon, 01 Jul 2002 10:00:41 +0200 Date: Mon, 1 Jul 2002 10:00:41 +0200 From: Sheldon Hearn To: Szilveszter Adam Cc: freebsd-current@FreeBSD.ORG Subject: Re: [PATCH] Re: Which .info files have been disabled? Message-ID: <20020701080041.GE82907@starjuice.net> Mail-Followup-To: Szilveszter Adam , freebsd-current@FreeBSD.ORG References: <20020628154933.GA1938@fonix.adamsfamily.xx> <20020629132919.GC883@fonix.adamsfamily.xx> <20020629103511.A10195@dragon.nuxi.com> <20020630083557.GA852@fonix.adamsfamily.xx> <20020630091509.GB852@fonix.adamsfamily.xx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020630091509.GB852@fonix.adamsfamily.xx> User-Agent: Mutt/1.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 On (2002/06/30 11:15), Szilveszter Adam wrote: > Grrr, hit me baby one more time. > > One of the diffs included a completely gratuitous one-line change which > I made yesterday night while I was tired and neglected to correct today. > > So, the patchset again. (Take three!) I've tested your patch through a 'make world' and have committed your patch: rev 1.12 src/gnu/usr.bin/binutils/doc/Makefile rev 1.4 src/gnu/usr.bin/binutils/doc/inc-hist.diff Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 1:14:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D58037B400 for ; Mon, 1 Jul 2002 01:14:33 -0700 (PDT) Received: from boggy.acest.tutrp.tut.ac.jp (boggy.acest.tutrp.tut.ac.jp [133.15.67.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E93AB43E09 for ; Mon, 1 Jul 2002 01:14:32 -0700 (PDT) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: from boggy.acest.tutrp.tut.ac.jp (localhost [127.0.0.1]) by boggy.acest.tutrp.tut.ac.jp (8.12.4/8.12.3) with ESMTP id g618EGj7064009 for ; Mon, 1 Jul 2002 17:14:16 +0900 (JST) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: (from nakaji@localhost) by boggy.acest.tutrp.tut.ac.jp (8.12.4/8.12.4/Submit) id g618EEUS064006; Mon, 1 Jul 2002 17:14:14 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: buildworld fails at share/doc/smm/10.named MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: Mon, 01 Jul 2002 17:14:14 +0900 Message-ID: <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> Lines: 40 User-Agent: T-gnus/6.15.6 (based on Oort Gnus v0.06) (revision 02) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.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 Hi, I noticed share/doc/smm/10.named fails after dougb's commit deleting contrib/bind/doc/bog/*. === Revision 1.1.1.2 (vendor branch), Mon Jul 1 01:27:59 2002 UTC (6 hours, 43 minutes ago) by dougb Branch: VIXIE, MAIN, ISC CVS Tags: HEAD Changes since 1.1.1.1: +0 -0 lines FILE REMOVED I don't think we ever installed these files, and they are more than a little dated. === Error message is, ===> share/doc/smm/10.named make: don't know how to make 00macs.me. Stop *** Error code 2 Stop in /usr/src/share/doc/smm. *** Error code 1 Stop in /usr/src/share/doc. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 1:18:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9243437B400 for ; Mon, 1 Jul 2002 01:18:17 -0700 (PDT) Received: from boggy.acest.tutrp.tut.ac.jp (boggy.acest.tutrp.tut.ac.jp [133.15.67.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FB9943E09 for ; Mon, 1 Jul 2002 01:18:16 -0700 (PDT) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: from boggy.acest.tutrp.tut.ac.jp (localhost [127.0.0.1]) by boggy.acest.tutrp.tut.ac.jp (8.12.4/8.12.3) with ESMTP id g618IDj7073942 for ; Mon, 1 Jul 2002 17:18:13 +0900 (JST) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: (from nakaji@localhost) by boggy.acest.tutrp.tut.ac.jp (8.12.4/8.12.4/Submit) id g618IBUc073939; Mon, 1 Jul 2002 17:18:11 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: buildworld fails at share/doc/smm/10.named References: <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: Mon, 01 Jul 2002 17:18:11 +0900 In-Reply-To: <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> (NAKAJI Hiroyuki's message of "Mon, 01 Jul 2002 17:14:14 +0900") Message-ID: <87u1njyi7w.fsf@boggy.acest.tutrp.tut.ac.jp> Lines: 11 User-Agent: T-gnus/6.15.6 (based on Oort Gnus v0.06) (revision 02) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.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 >>>>> In <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> >>>>> NAKAJI Hiroyuki wrote: NH> I noticed share/doc/smm/10.named fails after dougb's commit deleting NH> contrib/bind/doc/bog/*. Oops. Dougb already fixed the problem about 2 hours ago. I'm now under fourth buildworld today. Thanks. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 1:21:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A910137B401; Mon, 1 Jul 2002 01:21:56 -0700 (PDT) Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D62A743E1D; Mon, 1 Jul 2002 01:21:55 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 746B22A90; Mon, 1 Jul 2002 10:21:54 +0200 (CEST) Date: Mon, 1 Jul 2002 10:21:54 +0200 From: Ollivier Robert To: Gavin Atkinson Cc: freebsd-current@freebsd.org, sos@freebsd.org Subject: Re: Panic on apm resume with ata Message-ID: <20020701082154.GA82772@tara.freenix.org> Mail-Followup-To: Gavin Atkinson , freebsd-current@freebsd.org, sos@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PIII/800 SMP User-Agent: Mutt/1.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 According to Gavin Atkinson: > My laptop powered off due to a flat battery, and upon powerup, i > immediately experienced a panic. > > ata0: resetting devices .. done > panic: ata_dmasetup: transfer active on this device! It does happen sometimes on my Z600TEL Vaio too. -- 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 Jul 1 1:38:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF02737B400; Mon, 1 Jul 2002 01:38:51 -0700 (PDT) Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 367B343E0A; Mon, 1 Jul 2002 01:38:51 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id 5E4582A90; Mon, 1 Jul 2002 10:38:50 +0200 (CEST) Date: Mon, 1 Jul 2002 10:38:50 +0200 From: Ollivier Robert To: current@freebsd.org, ports@freebsd.org Subject: Re: kde3 compile probs.. Message-ID: <20020701083850.GB82772@tara.freenix.org> Mail-Followup-To: current@freebsd.org, ports@freebsd.org References: <20020629124354.GA84733@mich2.itxmarket.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020629124354.GA84733@mich2.itxmarket.com> X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PIII/800 SMP User-Agent: Mutt/1.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 According to Michael L. Hostbaek: > When trying to compile the kdebase3 port under recent -CURRENT - I get > the following error: Are you sure your libstdc++ is in sync ? Hvae you compiled QT with the ports gcc (it will break if not) ? -- 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 Jul 1 1:40: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C892D37B400 for ; Mon, 1 Jul 2002 01:39:58 -0700 (PDT) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89A3643E0A for ; Mon, 1 Jul 2002 01:39:58 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from FreeBSD.org (12-234-90-219.client.attbi.com [12.234.90.219]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 4FD0C8B5C4; Mon, 1 Jul 2002 01:39:58 -0700 (PDT) Message-ID: <3D20155E.624F0BED@FreeBSD.org> Date: Mon, 01 Jul 2002 01:39:58 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; FreeBSD 4.6-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: NAKAJI Hiroyuki Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld fails at share/doc/smm/10.named References: <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> <87u1njyi7w.fsf@boggy.acest.tutrp.tut.ac.jp> 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 NAKAJI Hiroyuki wrote: > > >>>>> In <87wusfyieh.fsf@boggy.acest.tutrp.tut.ac.jp> > >>>>> NAKAJI Hiroyuki wrote: > > NH> I noticed share/doc/smm/10.named fails after dougb's commit deleting > NH> contrib/bind/doc/bog/*. > > Oops. Dougb already fixed the problem about 2 hours ago. Yep, sorry about that.... my pre-commit build/installworld went fine, but I caught the problem after checking out a clean tree and doing the buildworld again. Mea culpa. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 1:40:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6110337B400 for ; Mon, 1 Jul 2002 01:40:24 -0700 (PDT) Received: from tara.freenix.org (keltia.freenix.org [62.4.20.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB20643E09 for ; Mon, 1 Jul 2002 01:40:23 -0700 (PDT) (envelope-from roberto@tara.freenix.org) Received: by tara.freenix.org (Postfix/TLS, from userid 101) id D0B402A90; Mon, 1 Jul 2002 10:40:22 +0200 (CEST) Date: Mon, 1 Jul 2002 10:40:22 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org Subject: Re: qt3 and kde-2.2.2 Message-ID: <20020701084022.GC82772@tara.freenix.org> Mail-Followup-To: freebsd-current@freebsd.org References: <20020629144536.C3918100@nebula.anchoragerescue.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020629144536.C3918100@nebula.anchoragerescue.org> X-Operating-System: FreeBSD 5.0-CURRENT K6-3D/266 & 2x PIII/800 SMP User-Agent: Mutt/1.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 According to Beech Rintoul: > Will kde-2.2.2 work with qt3? No. Qt3 is only for kde 3.x. > Or will I completely hose my desktop? > My qt2 got borked during a restore and I can't get it to build with the new > gcc31. Add that to several others that won't build either. Best way is to go to kde3. It is faster anyway (although the speed of C++ compilation with gcc31 makes it a dog to compile...). -- 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 Jul 1 1:47:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60AD137B400 for ; Mon, 1 Jul 2002 01:47:54 -0700 (PDT) Received: from kathmandu.sun.com (kathmandu.sun.com [192.18.98.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE4DE43E09 for ; Mon, 1 Jul 2002 01:47:53 -0700 (PDT) (envelope-from tomppa@ultrahot.Finland.Sun.COM) Received: from sunfin.Finland.Sun.COM ([129.159.101.10]) by kathmandu.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA20965; Mon, 1 Jul 2002 02:47:52 -0600 (MDT) Received: from ultrahot.Finland.Sun.COM (ultrahot [129.159.101.87]) by sunfin.Finland.Sun.COM (8.12.2+Sun/8.12.2/ENSMAIL,v2.3beta) with ESMTP id g618losn005408; Mon, 1 Jul 2002 11:47:50 +0300 (EEST) Received: from ultrahot.finland.sun.com (localhost [127.0.0.1]) by ultrahot.Finland.Sun.COM (8.12.2+Sun/8.12.2) with ESMTP id g618loQX001799; Mon, 1 Jul 2002 11:47:50 +0300 (EEST) Received: (from tomppa@localhost) by ultrahot.finland.sun.com (8.12.2+Sun/8.12.2/Submit) id g618loaL001796; Mon, 1 Jul 2002 11:47:50 +0300 (EEST) From: Tomi Vainio - Sun Finland - MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15648.5941.784299.428591@gargle.gargle.HOWL> Date: Mon, 1 Jul 2002 11:47:49 +0300 To: "Glenn Gombert" Cc: current@FreeBSD.ORG Subject: Build world problems in todays sources In-Reply-To: <20020630225315.BC2486D9D3@www.fastmail.fm> References: <20020630225315.BC2486D9D3@www.fastmail.fm> X-Mailer: VM 7.05 under 21.4 (patch 8) "Honest Recruiter" XEmacs Lucid Reply-To: Tomi.Vainio@Sun.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 Glenn Gombert writes: > I get the following error when trying to rebuild the last couple of > days... > > ../sys/kern/syscalls.master > syscall.master : line 55: syscall number out of sync at 7 ... > > line is: struct rusage * rsuage ) ; } wait4 wait_args int > I've seen this and if I remember anything it was sed or awk problem. Do first cd /usr/src/usr.bin/sed ; make all install and then try buildworld again. Tomppa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 2:38: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BF9137B400 for ; Mon, 1 Jul 2002 02:38:00 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id DF46543E13 for ; Mon, 1 Jul 2002 02:37:58 -0700 (PDT) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 22817 invoked from network); 1 Jul 2002 09:36:32 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.82.121.7) by www.contentmedia.de with SMTP; 1 Jul 2002 09:36:32 -0000 Subject: Re: Post-KSE disaster with libc_r From: Marc Recht To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 01 Jul 2002 11:37:52 +0200 Message-Id: <1025516273.442.5.camel@leeloo.intern.geht.de> Mime-Version: 1.0 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 > Can someone please check out a libc_r tree as of 3 days ago > and try that... > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > failing that, can someone try newly compiled utilities on an older pre-KSE > kernel? > > We need to eliminate one of these two changes... I don't know if this helps, but I've a pre-KSE userland (28.06.), a post-KSE kernel (30.06.) and I've none of the described problems. Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 4: 0:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE11937B400 for ; Mon, 1 Jul 2002 04:00:18 -0700 (PDT) Received: from boggy.acest.tutrp.tut.ac.jp (boggy.acest.tutrp.tut.ac.jp [133.15.67.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E1D143E0A for ; Mon, 1 Jul 2002 04:00:17 -0700 (PDT) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: from boggy.acest.tutrp.tut.ac.jp (localhost [127.0.0.1]) by boggy.acest.tutrp.tut.ac.jp (8.12.5/8.12.5) with ESMTP id g61B0FmM008662 for ; Mon, 1 Jul 2002 20:00:16 +0900 (JST) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: (from nakaji@localhost) by boggy.acest.tutrp.tut.ac.jp (8.12.5/8.12.5/Submit) id g61B0FZB008659; Mon, 1 Jul 2002 20:00:15 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r References: <1025516273.442.5.camel@leeloo.intern.geht.de> MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: Mon, 01 Jul 2002 20:00:15 +0900 In-Reply-To: <1025516273.442.5.camel@leeloo.intern.geht.de> (Marc Recht's message of "01 Jul 2002 11:37:52 +0200") Message-ID: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> Lines: 41 User-Agent: T-gnus/6.15.6 (based on Oort Gnus v0.06) (revision 02) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) 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 <1025516273.442.5.camel@leeloo.intern.geht.de> >>>>> Marc Recht wrote: > Can someone please check out a libc_r tree as of 3 days ago > and try that... > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > failing that, can someone try newly compiled utilities on an older pre-KSE > kernel? MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a MR> post-KSE kernel (30.06.) and I've none of the described problems. MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. I updated my current box about an hour ago, and got into trouble too. My case is that amavis-milter dumps core with signal 11 and I cannot check virus in emails. :( $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 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-undermydesk-freebsd"... Core was generated by `amavis-milter'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libmilter.so.2...done. Loaded symbols for /usr/lib/libmilter.so.2 Reading symbols from /usr/lib/libc_r.so.5...done. Loaded symbols for /usr/lib/libc_r.so.5 Reading symbols from /usr/lib/libc.so.5...done. Loaded symbols for /usr/lib/libc.so.5 Reading symbols from /usr/libexec/ld-elf.so.1...done. Loaded symbols for /usr/libexec/ld-elf.so.1 #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 (gdb) -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 4:11:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B187837B400 for ; Mon, 1 Jul 2002 04:11:48 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 96C6243E0A for ; Mon, 1 Jul 2002 04:11:47 -0700 (PDT) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 23930 invoked from network); 1 Jul 2002 11:10:24 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.82.121.7) by www.contentmedia.de with SMTP; 1 Jul 2002 11:10:24 -0000 Subject: Re: Post-KSE disaster with libc_r From: Marc Recht To: NAKAJI Hiroyuki Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> References: <1025516273.442.5.camel@leeloo.intern.geht.de> <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 01 Jul 2002 13:11:45 +0200 Message-Id: <1025521906.417.1.camel@leeloo.intern.geht.de> Mime-Version: 1.0 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 > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > MR> post-KSE kernel (30.06.) and I've none of the described problems. > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > I updated my current box about an hour ago, and got into trouble too. But you've updated the userland _and_ the kernel. I've only updated the kernel and left the userland int the pre-KSE state. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 4:19:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB79137B400 for ; Mon, 1 Jul 2002 04:19:18 -0700 (PDT) Received: from espresso.q9media.com (espresso.q9media.com [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B89243E09 for ; Mon, 1 Jul 2002 04:19:18 -0700 (PDT) (envelope-from des@sparc64.style9.org) Received: from bowie.private (d141-203-124.home.cgocable.net [24.141.203.124]) by espresso.q9media.com (Postfix) with ESMTP id 6AB879C11 for ; Mon, 1 Jul 2002 07:15:38 -0400 (EDT) Received: from bowie.private (localhost [127.0.0.1]) by bowie.private (8.12.5/8.12.5) with ESMTP id g61BJhDm094870 for ; Mon, 1 Jul 2002 11:19:43 GMT (envelope-from des@bowie.private) Received: (from des@localhost) by bowie.private (8.12.5/8.12.5/Submit) id g61BJfuP094868 for current@freebsd.org; Mon, 1 Jul 2002 11:19:42 GMT Date: Mon, 1 Jul 2002 11:19:42 GMT From: Dag-Erling Smorgrav Message-Id: <200207011119.g61BJfuP094868@bowie.private> To: current@freebsd.org Subject: sparc64 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 /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> share/doc/smm/title ===> share/doc/smm/contents ===> share/doc/smm/01.setup ===> share/doc/smm/02.config ===> share/doc/smm/03.fsck ===> share/doc/smm/04.quotas ===> share/doc/smm/05.fastfs ===> share/doc/smm/06.nfs ===> share/doc/smm/10.named make: don't know how to make 00macs.me. Stop *** Error code 2 Stop in /usr/home/des/tinderbox/sparc64/src/share/doc/smm. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/share/doc. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/share. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 4:51:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17BA637B400 for ; Mon, 1 Jul 2002 04:51:37 -0700 (PDT) Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id D590F43E1A for ; Mon, 1 Jul 2002 04:51:36 -0700 (PDT) (envelope-from des@FreeBSD.org) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.5/8.12.5) with ESMTP id g61BpaJW041175 for ; Mon, 1 Jul 2002 04:51:36 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.5/8.12.5/Submit) id g61Bpatr041173 for current@freebsd.org; Mon, 1 Jul 2002 04:51:36 -0700 (PDT) Date: Mon, 1 Jul 2002 04:51:36 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200207011151.g61Bpatr041173@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 /home/des/tinderbox/alpha/obj/j/des/src/alpha/usr/include -------------------------------------------------------------- >>> stage 4: building libraries -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- >>> stage 4: building everything.. -------------------------------------------------------------- ===> gnu/usr.bin/dialog ===> gnu/usr.bin/dialog/TESTS ===> gnu/usr.bin/diff /j/des/src/contrib/diff/prepend_args.c: In function `prepend_default_options': /j/des/src/contrib/diff/prepend_args.c:74: warning: initialization makes pointer from integer without a cast /j/des/src/contrib/diff/prepend_args.c:78: warning: cast to pointer from integer of different size ===> gnu/usr.bin/diff/doc /j/des/src/gnu/usr.bin/diff/doc/../../../../contrib/diff/diff.texi:2678: warning: unlikely character ] in @var. gzip: stdout: No space left on device *** Error code 1 Stop in /j/des/src/gnu/usr.bin/diff/doc. *** Error code 1 Stop in /j/des/src/gnu/usr.bin/diff. *** Error code 1 Stop in /j/des/src/gnu/usr.bin. *** Error code 1 Stop in /j/des/src/gnu. *** Error code 1 Stop in /j/des/src. *** Error code 1 Stop in /j/des/src. *** Error code 1 Stop in /j/des/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 5:46:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 680B137B400 for ; Mon, 1 Jul 2002 05:46:31 -0700 (PDT) Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59C7E43E13 for ; Mon, 1 Jul 2002 05:46:30 -0700 (PDT) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 17P0ZZ-0001eL-00; Mon, 1 Jul 2002 14:46:29 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.5/8.12.5) with ESMTP id g61BkBoU006785 for ; Mon, 1 Jul 2002 13:46:11 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.5/8.12.5/Submit) id g61BkBQ2006784 for freebsd-current@freebsd.org; Mon, 1 Jul 2002 13:46:11 +0200 (CEST) From: naddy@freebsd.org (Christian Weisgerber) Subject: LP64: (int)signal() Date: Mon, 1 Jul 2002 11:46:10 +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 I would like to clean up the last instances of (int)signal(...) in the tree. Any objection to the changes below? Other occurrences not worth touching: - contrib/opie/opieftpd.c: contrib, not used - libexec/bootpd/bootpd.c: #ifdef'ed out in favor of sigaction(). Index: atmarpd/atmarpd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/atm/atmarpd/atmarpd.c,v retrieving revision 1.4 diff -u -r1.4 atmarpd.c --- atmarpd/atmarpd.c 9 Dec 2000 09:35:42 -0000 1.4 +++ atmarpd/atmarpd.c 1 Jul 2002 11:38:07 -0000 @@ -294,8 +294,7 @@ /* * Set up signal handlers */ - rc = (int)signal(SIGINT, atmarp_sigint); - if (rc == -1) { + if (signal(SIGINT, atmarp_sigint) == SIG_ERR) { atmarp_log(LOG_ERR, "SIGINT signal setup failed"); exit(1); } Index: scspd/scspd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/atm/scspd/scspd.c,v retrieving revision 1.4 diff -u -r1.4 scspd.c --- scspd/scspd.c 9 Dec 2000 09:35:42 -0000 1.4 +++ scspd/scspd.c 1 Jul 2002 11:38:08 -0000 @@ -319,14 +319,12 @@ /* * Set up signal handlers */ - rc = (int)signal(SIGHUP, scsp_sighup); - if (rc == -1) { + if (signal(SIGHUP, scsp_sighup) == SIG_ERR) { scsp_log(LOG_ERR, "SIGHUP signal setup failed"); exit(1); } - rc = (int)signal(SIGINT, scsp_sigint); - if (rc == -1) { + if (signal(SIGINT, scsp_sigint) == SIG_ERR) { scsp_log(LOG_ERR, "SIGINT signal setup failed"); exit(1); } -- 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 Mon Jul 1 6:47:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6C5B37B400 for ; Mon, 1 Jul 2002 06:47:57 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E87C743E13 for ; Mon, 1 Jul 2002 06:47:56 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 JAA19678; Mon, 1 Jul 2002 09:47:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g61DlQh21831; Mon, 1 Jul 2002 09:47:26 -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: <15648.23918.162377.985452@grasshopper.cs.duke.edu> Date: Mon, 1 Jul 2002 09:47:26 -0400 (EDT) To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: buildworld problems with today's sources In-Reply-To: <20020630140656.A86137@iguana.icir.org> References: <20020630140656.A86137@iguana.icir.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 The same thing happened to me when buildworlding on a ~june 20th current box. I removed CPUTYPE from /etc/make.conf, and I fsck'ed the disk in question (after a crash resulting from the condvar problem discussed here). And I removed -j4 from my make flags. One of these things (sorry that I don't know which), cured the problem. I was mainly interested in getting a -current world, not diagnosing the breakage. Drew Luigi Rizzo writes: <...> > Stop in /home/luigi/XORP/HEAD_020630/src/gnu/usr.bin/tar. > *** Error code 1 <...> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 6:51:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2CBD37B400 for ; Mon, 1 Jul 2002 06:51:30 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 140B943E1D for ; Mon, 1 Jul 2002 06:51:30 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g61DpSo93565; Mon, 1 Jul 2002 06:51:28 -0700 (PDT) (envelope-from rizzo) Date: Mon, 1 Jul 2002 06:51:28 -0700 From: Luigi Rizzo To: Andrew Gallatin Cc: current@freebsd.org Subject: Re: buildworld problems with today's sources Message-ID: <20020701065128.A93489@iguana.icir.org> References: <20020630140656.A86137@iguana.icir.org> <15648.23918.162377.985452@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: <15648.23918.162377.985452@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Jul 01, 2002 at 09:47:26AM -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 Mon, Jul 01, 2002 at 09:47:26AM -0400, Andrew Gallatin wrote: > > The same thing happened to me when buildworlding on a ~june 20th > current box. Ruslan explained me the source of the problem... cvs does not prune empty directories unless you specify a revision or a date. In my case i wanted HEAD so i did cvs co src whereas I should have done cvs co -P src After doing that, mostly things worked (modulo the fact that i probably was in the middle of some commit and there was some breakage somewhere, but nothing important) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 6:58:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E93DD37B400 for ; Mon, 1 Jul 2002 06:58:35 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4564A43E0A for ; Mon, 1 Jul 2002 06:58:35 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 JAA19998; Mon, 1 Jul 2002 09:58:34 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g61Dw4u21842; Mon, 1 Jul 2002 09:58:04 -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: <15648.24556.798303.759083@grasshopper.cs.duke.edu> Date: Mon, 1 Jul 2002 09:58:04 -0400 (EDT) To: Luigi Rizzo Cc: current@freebsd.org Subject: Re: buildworld problems with today's sources In-Reply-To: <20020701065128.A93489@iguana.icir.org> References: <20020630140656.A86137@iguana.icir.org> <15648.23918.162377.985452@grasshopper.cs.duke.edu> <20020701065128.A93489@iguana.icir.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 Luigi Rizzo writes: > On Mon, Jul 01, 2002 at 09:47:26AM -0400, Andrew Gallatin wrote: > > > > The same thing happened to me when buildworlding on a ~june 20th > > current box. > > Ruslan explained me the source of the problem... cvs does not > prune empty directories unless you specify a revision or a date. > In my case i wanted HEAD so i did > > cvs co src > > whereas I should have done > > cvs co -P src > > After doing that, mostly things worked (modulo the fact that i probably > was in the middle of some commit and there was some breakage > somewhere, but nothing important) Ah! That makes sense. I lost a few hundred files after the fsck, so I did an 'lcvs up' to make sure none of the src tree was missing. And my .cvsrc has 'update -Pd' in it. It had been a fresh checkout previously. That's actually rather scary. It implies that a freshly checked out tree checked out with plain 'cvs co src' is no longer buildable. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 7: 2:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4E5637B400 for ; Mon, 1 Jul 2002 07:02:41 -0700 (PDT) Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 248B943E1A for ; Mon, 1 Jul 2002 07:02:41 -0700 (PDT) (envelope-from rizzo@iguana.icir.org) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g61E2db93686; Mon, 1 Jul 2002 07:02:39 -0700 (PDT) (envelope-from rizzo) Date: Mon, 1 Jul 2002 07:02:39 -0700 From: Luigi Rizzo To: Andrew Gallatin Cc: current@freebsd.org Subject: Re: buildworld problems with today's sources Message-ID: <20020701070239.A93672@iguana.icir.org> References: <20020630140656.A86137@iguana.icir.org> <15648.23918.162377.985452@grasshopper.cs.duke.edu> <20020701065128.A93489@iguana.icir.org> <15648.24556.798303.759083@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: <15648.24556.798303.759083@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Mon, Jul 01, 2002 at 09:58:04AM -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 Mon, Jul 01, 2002 at 09:58:04AM -0400, Andrew Gallatin wrote: ... > That's actually rather scary. It implies that a freshly checked out > tree checked out with plain 'cvs co src' is no longer buildable. c'mon... it is not that terrible, just a matter of adding a -P flag luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 7:21:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F048537B400 for ; Mon, 1 Jul 2002 07:21:56 -0700 (PDT) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8594143E09 for ; Mon, 1 Jul 2002 07:21:56 -0700 (PDT) (envelope-from Scott_Long@adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.10.2+Sun/8.10.2) with ESMTP id g61ELfE21558; Mon, 1 Jul 2002 07:21:42 -0700 (PDT) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA00079; Mon, 1 Jul 2002 07:21:40 -0700 (PDT) Received: from btcexc01.btc.adaptec.com (btcexc01 [10.100.0.23]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id IAA01442; Mon, 1 Jul 2002 08:21:31 -0600 (MDT) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id ; Mon, 1 Jul 2002 08:21:31 -0600 Message-ID: <2C7CBDC6EA58D6119E4A00065B3A24CB0463F5@btcexc01.btc.adaptec.com> From: "Long, Scott" To: "'Maxim M. Kazachek'" , freebsd-current@freebsd.org Subject: RE: Is pcm broken? Date: Mon, 1 Jul 2002 08:21:27 -0600 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 > > Looks like someone broke AC97 rate measurement in -CURRENT > > -STABLE measures AC97 rate well (about 55900). Current gives about > 41000... > > Hardware is Compaq EXD C600 (-STABLE) and Compaq iPAQ C700 (-CURRENT) > Both are i815 equipped with SoundMAX AC97 codec... > > Sincerely, Maxim M. Kazachek > mailto:stranger@sberbank.sibnet.ru > mailto:stranger@fpm.ami.nstu.ru > Hi, My calibration fix for the ich driver might have broken your setup. Could you boot with bootverbose set and send me the dmesg output? Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 7:42:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1BB837B400 for ; Mon, 1 Jul 2002 07:42:33 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 111C743E13 for ; Mon, 1 Jul 2002 07:42:33 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id A35155349; Mon, 1 Jul 2002 16:42:31 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: Re: alpha tinderbox failure References: <200207011151.g61Bpatr041173@beast.freebsd.org> From: Dag-Erling Smorgrav Date: 01 Jul 2002 16:42:30 +0200 In-Reply-To: <200207011151.g61Bpatr041173@beast.freebsd.org> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 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 Dag-Erling Smorgrav writes: > gzip: stdout: No space left on device > *** Error code 1 I moved the Alpha build to a different disk, the next run should be OK. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 7:59:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9AC837B400 for ; Mon, 1 Jul 2002 07:59:41 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E9043E13 for ; Mon, 1 Jul 2002 07:59:40 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g61ExVTa001255 for ; Mon, 1 Jul 2002 18:59:38 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g61ExVkx001254 for current@freebsd.org; Mon, 1 Jul 2002 18:59:31 +0400 (MSD) (envelope-from ache) Date: Mon, 1 Jul 2002 18:59:31 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: libc_r now dumps core Message-ID: <20020701145931.GA1212@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.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 Several threaded applications like mnogosearch, drweb-sendmail now dumps core (recent -current). When libc_r replaced by old variant, they works again. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 8: 7:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24DCB37B43E for ; Mon, 1 Jul 2002 08:07:35 -0700 (PDT) Received: from beastie.jocose.org (www.jocose.org [216.239.16.179]) by mx1.FreeBSD.org (Postfix) with SMTP id 45B1A43E1A for ; Mon, 1 Jul 2002 08:07:34 -0700 (PDT) (envelope-from peter@jocose.org) Received: (qmail 62558 invoked from network); 1 Jul 2002 15:07:33 -0000 Received: from unknown (HELO max.jocose.org) (10.0.0.100) by 0 with SMTP; 1 Jul 2002 15:07:33 -0000 Subject: Re: buildworld problems with today's sources From: Peter Schultz To: Luigi Rizzo Cc: Andrew Gallatin , current@freebsd.org In-Reply-To: <20020701070239.A93672@iguana.icir.org> References: <20020630140656.A86137@iguana.icir.org> <15648.23918.162377.985452@grasshopper.cs.duke.edu> <20020701065128.A93489@iguana.icir.org> <15648.24556.798303.759083@grasshopper.cs.duke.edu> <20020701070239.A93672@iguana.icir.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 01 Jul 2002 10:08:59 -0500 Message-Id: <1025536139.381.52.camel@max.jocose.org> Mime-Version: 1.0 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, 2002-07-01 at 09:02, Luigi Rizzo wrote: > On Mon, Jul 01, 2002 at 09:58:04AM -0400, Andrew Gallatin wrote: > ... > > That's actually rather scary. It implies that a freshly checked out > > tree checked out with plain 'cvs co src' is no longer buildable. > > c'mon... it is not that terrible, just a matter of adding a -P flag > Do these problems concern someone using cvsup? I've been having a terrible time with -current lately. Of course I realize development is going full speed, I'm being patient and using the down time to encourage others to turn to FreeBSD. The file system is blazing fast and as soon as the kernel smooths out FreeBSD-5.0 is going to rock. I'm very happy with FreeBSD. It does take a very great deal of studying, but once you've done that it's so ultimately powerful. To my dismay I've only just scratched the surface, but I'm not giving up yet! My thanks goes out to all those valuable FreeBSD commits. Pete... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 8: 8:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D25837B400; Mon, 1 Jul 2002 08:08:10 -0700 (PDT) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75EA343E26; Mon, 1 Jul 2002 08:08:09 -0700 (PDT) (envelope-from chuckr@april.chuckr.org) Received: from localhost (chuckr@localhost) by april.chuckr.org (8.11.6/8.11.3) with ESMTP id g61F7x561992; Mon, 1 Jul 2002 11:07:59 -0400 (EDT) (envelope-from chuckr@april.chuckr.org) Date: Mon, 1 Jul 2002 11:07:58 -0400 (EDT) From: Chuck Robey To: Doug Barton Cc: FreeBSD-current Subject: Re: getting back to current In-Reply-To: <3D1FF65C.E8AC60B5@FreeBSD.org> Message-ID: <20020701110524.E378-100000@april.chuckr.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, 30 Jun 2002, Doug Barton wrote: > Chuck Robey wrote: > > > > I've just finished going thru another medical session, this one took about > > 5 months, and because of the extended time spent away, I'm running 4.5 > > (I've been running current since 1.1, this feels really odd). I need > > a little bit of help (or advice, maybe) to get me back to current. > > Glad to hear you're feeling better. :) The bad news is that this is a > really terrible time to upgrade to -current. The KSE mark III update > just went in, so things are very unstable right now. Clearing out about 50,000 old mails today ... need to update myself. Much thanks for the heads-up. I'm OK with instability, I'm used to that, as long as it works at least a bit. > > I just finished cvsupping, and the main sources built just fine. I > > installed a new config (static, the libs are now too old) and fixed all > > the changes in my config file, so now my kernel file configs .... but it > > doesn't build (breaks in 'make depend', I think in genassym). I'm > > guessing that this is only one of a string of incompatibilities, in > > jumping from 4.5 back to current. > > At this point, the only way to build -current on a -stable system is > make buildworld; make buildkernel. Make sure that KERNCONF is defined in > /etc/make.conf. > > You'll probably want to read -current and cvs-all for a while before > you finish the upgrade though.... > > HTH, > > Doug > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 8:23: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91CAF37B400; Mon, 1 Jul 2002 08:22:59 -0700 (PDT) Received: from espresso.q9media.com (espresso.q9media.com [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B6DC43E1A; Mon, 1 Jul 2002 08:22:59 -0700 (PDT) (envelope-from mike@espresso.q9media.com) Received: by espresso.q9media.com (Postfix, from userid 1002) id 2126D9C11; Mon, 1 Jul 2002 11:19:19 -0400 (EDT) Date: Mon, 1 Jul 2002 11:19:19 -0400 From: Mike Barcroft To: Christian Weisgerber Cc: freebsd-current@freebsd.org Subject: Re: LP64: (int)signal() Message-ID: <20020701111919.B20124@espresso.q9media.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from naddy@freebsd.org on Mon, Jul 01, 2002 at 11:46:10AM +0000 Organization: The FreeBSD Project 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 Christian Weisgerber writes: > I would like to clean up the last instances of (int)signal(...) in > the tree. Any objection to the changes below? > > Other occurrences not worth touching: > - contrib/opie/opieftpd.c: contrib, not used > - libexec/bootpd/bootpd.c: #ifdef'ed out in favor of sigaction(). > > Index: atmarpd/atmarpd.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/atm/atmarpd/atmarpd.c,v > retrieving revision 1.4 > diff -u -r1.4 atmarpd.c > --- atmarpd/atmarpd.c 9 Dec 2000 09:35:42 -0000 1.4 > +++ atmarpd/atmarpd.c 1 Jul 2002 11:38:07 -0000 > @@ -294,8 +294,7 @@ > /* > * Set up signal handlers > */ > - rc = (int)signal(SIGINT, atmarp_sigint); > - if (rc == -1) { > + if (signal(SIGINT, atmarp_sigint) == SIG_ERR) { > atmarp_log(LOG_ERR, "SIGINT signal setup failed"); > exit(1); > } You might want to get rid of the other misuse of `rc' above this and just remove the variable. > Index: scspd/scspd.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/atm/scspd/scspd.c,v > retrieving revision 1.4 > diff -u -r1.4 scspd.c > --- scspd/scspd.c 9 Dec 2000 09:35:42 -0000 1.4 > +++ scspd/scspd.c 1 Jul 2002 11:38:08 -0000 > @@ -319,14 +319,12 @@ > /* > * Set up signal handlers > */ > - rc = (int)signal(SIGHUP, scsp_sighup); > - if (rc == -1) { > + if (signal(SIGHUP, scsp_sighup) == SIG_ERR) { > scsp_log(LOG_ERR, "SIGHUP signal setup failed"); > exit(1); > } > > - rc = (int)signal(SIGINT, scsp_sigint); > - if (rc == -1) { > + if (signal(SIGINT, scsp_sigint) == SIG_ERR) { > scsp_log(LOG_ERR, "SIGINT signal setup failed"); > exit(1); > } [Repeat above sentence.] :) Otherwise it looks good. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 9:11:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A35F337B400 for ; Mon, 1 Jul 2002 09:11:39 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id E539043E0A for ; Mon, 1 Jul 2002 09:11:38 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from chemikals.org (www@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with SMTP id g61GBZ7B015123; Mon, 1 Jul 2002 12:11:35 -0400 (EDT) (envelope-from morganw@chemikals.org) From: Wesley Morgan Received: from 148.175.49.1 (SquirrelMail authenticated user morganw) by www.chemikals.org with HTTP; Mon, 1 Jul 2002 12:11:35 -0400 (EDT) Message-ID: <20866.148.175.49.1.1025539895.squirrel@www.chemikals.org> Date: Mon, 1 Jul 2002 12:11:35 -0400 (EDT) Subject: Re: Post-KSE disaster with libc_r To: In-Reply-To: References: <20020701024638.X11550-100000@volatile.chemikals.org> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.6) 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 Ktracing with context switches look the same as before.... Stepping into libc_r leads me on a merry chase through what appears to be normal execution, until somewhere in uthread_sig.c about line 552... (gdb) r Starting program: /usr/local/bin/kdeinit Breakpoint 1 at 0x28e839f6: file /usr/src/lib/libc_r/uthread/uthread_fork.c, line 49.Breakpoint 1, 0x28eda7d4 in fork () from /usr/lib/libc.so.5 (gdb) b /usr/src/lib/libc_r/uthread/uthread_sig.c:546 Breakpoint 2 at 0x28e8723d: file /usr/src/lib/libc_r/uthread/uthread_sig.c, line 546.(gdb) c Continuing. Breakpoint 2, thread_sig_handle_special (sig=20) at /usr/src/lib/libc_r/uthread/uthread_sig.c:546 546 for (pthread = TAILQ_FIRST(&_waitingq); (gdb) print _waitingq $1 = {tqh_first = 0x8054000, tqh_last = 0x8054210} (gdb) s 0x28e8723e in thread_sig_handle_special (sig=20) at /usr/src/lib/libc_r/uthread/uthread_sig.c:546 546 for (pthread = TAILQ_FIRST(&_waitingq); Program received signal SIGSEGV, Segmentation fault. 0x28e8723e in thread_sig_handle_special (sig=20) at /usr/src/lib/libc_r/uthread/uthread_sig.c:546 546 for (pthread = TAILQ_FIRST(&_waitingq); Odd... Now if I set a breakpoint inside of the for() loop at line 552, it will actually get past that: Breakpoint 2, thread_sig_handle_special (sig=20) at /usr/src/lib/libc_r/uthread/uthread_sig.c:552 552 pthread_next = TAILQ_NEXT(pthread, pqe); (gdb) s 558 if (pthread->state == PS_WAIT_WAIT) { (gdb) s Program received signal SIGSEGV, Segmentation fault. thread_sig_handle_special (sig=20) at /usr/src/lib/libc_r/uthread/uthread_sig.c:558 558 if (pthread->state == PS_WAIT_WAIT) { (gdb) print pthread $1 = (struct pthread *) 0x210 That definitely is not right! Backing up, this is the content of the pthread struct before it gets munched into 0x210 (re-ran the process of course)$1 = {magic = 3499860245, name = 0x8056030 "_thread_initial", uniqueid = 0, lock = {access_lock = 686322256, lock_owner = 0, fname = 0x0, lineno = 0}, tle = {tqe_next = 0x0, tqe_prev = 0x28e94a88}, dle = {tqe_next = 0x0, tqe_prev = 0x0}, start_routine = 0, arg = 0x0, stack = 0xbfb00000, attr = { sched_policy = 3, sched_inherit = 0, sched_interval = 20000, prio = 15, suspend = 0, flags = 0, arg_attr = 0x0, cleanup_attr = 0, stackaddr_attr = 0xbfb00000, stacksize_attr = 1048576, guardsize_attr = 4096}, ctx = {jb = {{_jb = {686343554, 686378132, -1077939364, -1077939336, -1, 134561792, 4735, 0, 0, 0, 0, 0}}}, uc = {uc_sigmask = {__bits = {686343554, 686378132, 3217027932, 3217027960}}, uc_mcontext = {mc_onstack = -1, mc_gs = 134561792, mc_fs = 4735, mc_es = 0, mc_ds = 0, mc_edi = 0, mc_esi = 0, mc_ebp = 0, mc_isp = 0, mc_ebx = 0, mc_edx = 0, mc_ecx = 0, mc_eax = 0, mc_trapno = 0, mc_err = 0, mc_eip = 0, mc_cs = 0, mc_eflags = 0, mc_esp = 0, mc_ss = 0, mc_fpregs = { 0 }, mc_flags = 0, __spare__ = { 0 }}, uc_link = 0x0, uc_stack = {ss_sp = 0x0, ss_size = 0, ss_flags = 0}, __spare__ = {0, 0, 0, 0, 0, 0, 0, 0}}}, curframe = 0x0, cancelflags = 4, continuation = 0, sigmask = {__bits = {0, 0, 0, 0}}, sigpend = {__bits = {0, 0, 0, 0}}, sigmask_seqno = 0, check_pending = 0, state = PS_FDR_WAIT, last_active = 0, last_inactive = 0, slice_usec = -1, wakeup_time = {tv_sec = -1, tv_nsec = -1}, timeout = 0, error = 0, joiner = 0x0, join_status = {thread = 0x0, ret = 0x0, error = 0}, pqe = {tqe_next = 0x0, tqe_prev = 0x28e9a8d0}, sqe = {tqe_next = 0x0, tqe_prev = 0x0}, qe = {tqe_next = 0x0, tqe_prev = 0x28e97080}, data = { mutex = 0x7, cond = 0x7, sigwait = 0x7, fd = {fd = 7, branch = 0, fname = 0x0}, fp = 0x7, poll_data = 0x7, spinlock = 0x7, thread = 0x7}, poll_data = {nfds = 0, fds = 0x0}, interrupted = 0, signo = 0, sig_defer_count = 0, yield_on_sig_undefer = 0, flags = 20, base_priority = 15 '\017', inherited_priority = 0 '\0', active_priority = 15 '\017', priority_mutex_count = 0, mutexq = { tqh_first = 0x0, tqh_last = 0x8054254}, ret = 0x0, specific = 0x0, specific_data_count = 0, cleanup = 0x0, fname = 0x28e925a0 "/usr/src/lib/libc_r/uthread/uthread_read.c", lineno = 81} Of course all this means absolutely nothing to me :) ... Setting the breakpoint just past the for() loop give me the same old crash as before: #0 thread_kern_poll (wait_reqd=0) at /usr/src/lib/libc_r/uthread/uthread_kern.c:862 #1 0x28e8c8d7 in _thread_kern_scheduler () at /usr/src/lib/libc_r/uthread/uthread_kern.c:372 #2 0xd0d0d0d0 in ?? () (gdb) print pthread $2 = (struct pthread *) 0xffffffff That's all I've got for now. Someone please tell me if posting this much junk to -current is frowned upon. I'm looking for an old libc_r now, but there could be some problems with the GCC changeout since DP1 that won't work too well with KDE... > can you do what you did before and try singlestep > a bit? > > also.. instead of checking out an older libc_r, > can you try see if there is actually on old copy > (say from teh DP1-image) somewhere and try that... > it's possible we have symbol polution problemm.. > a lot of the names in libc_r look awfully familliar > from the KSE code.. (this shouldn;t be possible but.... > >> Hope some of this is useful to anyone out there! > > not on its own, but as a part of a developing picture. > >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 9:26:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB8937B429 for ; Mon, 1 Jul 2002 09:26:18 -0700 (PDT) Received: from mx2.datanet.hu (mx2.datanet.hu [194.149.13.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA9B43E0A for ; Mon, 1 Jul 2002 09:26:17 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-976.adsl.datanet.hu [195.56.51.214]) by mx2.datanet.hu (DataNet) with ESMTP id 16E275807 for ; Mon, 1 Jul 2002 18:26:16 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g61GQPRG002431 for ; Mon, 1 Jul 2002 18:26:25 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g61GQPWb002430 for current@FreeBSD.ORG; Mon, 1 Jul 2002 18:26:25 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Mon, 1 Jul 2002 18:26:25 +0200 From: Szilveszter Adam To: current@FreeBSD.ORG Subject: Re: What's the right way to build XFree86-4 now? Message-ID: <20020701162625.GA2344@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.ORG References: <40690.1025103465@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.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 On Sun, Jun 30, 2002 at 11:58:51PM -0400, Garance A Drosihn wrote: > Have many people had a chance to test this? I wanted to try it out > this weekend, but I lost most of the weekend due to other problems > with compiling current on my test machine. I finally got by those > problems, but now it's midnight on Sunday and I can't really afford > to start on this right now... Sorry, me not. I also was struggling with -CURRENT buildworld during the weekend and my machine is slow. I rebuilt X with the most recent patch to libGLU from this list and libGLU now seems working. (with the system compiler) The machine freezes under X quite frequently however, but I don't know what is causing it. (and X freezes have the disgusting property of locking up the system solid: no console, no network, nothing in the logs.) Life is sometimes hard in -CURRENT land, but hey, we should never loose our sense of humour. (And yes, maybe I really should get another graphics card... the S3 Virge GX2 may also take part of the blame for the lockups...) -- 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 Mon Jul 1 10: 4:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C99337B400 for ; Mon, 1 Jul 2002 10:04:17 -0700 (PDT) Received: from draco.macsch.com (ns1.mscsoftware.com [192.207.69.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7650E43E26 for ; Mon, 1 Jul 2002 10:04:16 -0700 (PDT) (envelope-from Georg.Koltermann@mscsoftware.com) Received: from mailmuc.muc.eu.mscsoftware.com (mailmuc.muc.macsch.com [161.34.37.20]) by draco.macsch.com (8.9.3/8.9.3) with ESMTP id KAA21225 for ; Mon, 1 Jul 2002 10:04:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailmuc.muc.eu.mscsoftware.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g61H2Lp27845 for ; Mon, 1 Jul 2002 19:02:21 +0200 Content-Transfer-Encoding: 7bit Content-Type: text/plain Date: 01 Jul 2002 19:02:45 +0200 From: "Georg-W. Koltermann" Message-Id: <1025542965.628.8.camel@hunter.muc.macsch.com> Mime-Version: 1.0 Received: from hunter.muc.macsch.com by mailmuc.muc.eu.mscsoftware.com (AvMailGate-2.0.0.6) id 27818-36B8452F; Mon, 01 Jul 2002 19:02:11 +0200 Subject: PANIC Most recently used by routetbl To: freebsd-current@freebsd.org X-AntiVirus: OK! AvMailGate Version 6.12.1.30 at mailmuc has not found any known virus in this email. X-Mailer: Ximian Evolution 1.0.5 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, panic: Most recently used by routetbl I get this type of panic withing minutes of uptime with a -current of 25-Jun-2002 around 13:52 GMT-2. Another anomaly is that name resolution doesn't seem to work reliably, or maybe even TCP in general has a problem -- it all takes very long if it works at all. This is still a pre-KSE-III system. As a workaround I am currently running with a kernel of about 11 Apr in the same userland, which seems to work. hunter[4]$ gdb -k kernel.debug vmcore.25 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"...Deprecated bfd_read called at /usr/src/contrib/gdb/gdb/dbxread.c line 2617 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/contrib/gdb/gdb/dbxread.c line 930 in fill_symbuf IdlePTD at physical address 0x00498000 initial pcb at physical address 0x003b3cc0 panicstr: bremfree: bp 0xd2a84230 not locked panic messages: --- panic: Most recently used by routetbl syncing disks... panic: bremfree: bp 0xd2a84230 not locked Uptime: 24m55s pfs_vncache_unload(): 2 entries remaining /dev/vmmon: Module vmmon: unloaded Dumping 1023 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 --- #0 0xc01cff40 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353 353 } (kgdb) where #0 0xc01cff40 in doadump () at /usr/src/sys/kern/kern_shutdown.c:353 #1 0xc01d054b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:353 #2 0xc01d0767 in panic (fmt=0xc034f0a9 "bremfree: bp %p not locked") at /usr/src/sys/kern/kern_shutdown.c:353 #3 0xc02146a6 in bremfree (bp=0xd2a84230) at /usr/src/sys/kern/vfs_bio.c:1368 #4 0xc021723b in getblk (vp=0xc624e000, blkno=262208, size=8192, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_bio.c:1368 #5 0xc02147d1 in breadn (vp=0xc624e000, blkno=262208, size=8192, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0xe557aa40) at /usr/src/sys/kern/vfs_bio.c:1368 #6 0xc0214793 in bread (vp=0xc624e000, blkno=262208, size=8192, cred=0x0, bpp=0xe557aa40) at /usr/src/sys/kern/vfs_bio.c:1368 #7 0xc029cb62 in ffs_update (vp=0xc6658e00, waitfor=0) at /usr/src/sys/ufs/ffs/ffs_inode.c:441 #8 0xc02b24ba in ffs_fsync (ap=0xe557aab4) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:596 #9 0xc02b0b9c in VOP_FSYNC (vp=0xc6658e00, cred=0xc21a1f00, waitfor=2, td=0xc037d6a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:813 #10 0xc02afff4 in ffs_sync (mp=0xc60d8600, waitfor=2, cred=0xc21a1f00, td=0xc037d6a0) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:813 #11 0xc022736c in sync (td=0xc037d6a0, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:584 #12 0xc01d0055 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:353 #13 0xc01d0767 in panic (fmt=0xc0360748 "Most recently used by %s\n") at /usr/src/sys/kern/kern_shutdown.c:353 #14 0xc02d6f3a in mtrash_ctor (mem=0xc697cc00, size=252, arg=0x0) at /usr/src/sys/vm/uma_dbg.c:284 #15 0xc02d5765 in uma_zalloc_arg (zone=0xc2179140, udata=0x0, flags=0) at /usr/src/sys/vm/uma_core.c:663 #16 0xc01c5254 in uma_zalloc (zone=0xc2179140, flags=0) at /usr/src/sys/kern/kern_malloc.c:555 #17 0xc01c484b in malloc (size=224, type=0xc037e760, flags=0) at /usr/src/sys/kern/kern_malloc.c:555 #18 0xc01b34d2 in fdcopy (td=0xc62ccd70) at /usr/src/sys/kern/kern_descrip.c:476 #19 0xc01bb7bd in fork1 (td=0xc62ccd70, flags=20, procp=0xe557acd8) at /usr/src/sys/kern/kern_fork.c:734 #20 0xc01baea6 in fork (td=0xc62ccd70, uap=0xe557acfc) at /usr/src/sys/kern/kern_fork.c:734 #21 0xc0310af6 in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 70, tf_ebp = -1077937164, tf_isp = -447238796, tf_ebx = 678978900, tf_edx = 484, tf_ecx = -33, tf_eax = 2, tf_trapno = 12, tf_err = 2, tf_eip = 672142263, tf_cs = 31, tf_eflags = 642, tf_esp = -1077937224, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:655 #22 0xc02ff8ed in syscall_with_err_pushed () at /var/tmp//ccMqLVIG.s:128 #23 0x2877f460 in ?? () #24 0x2877e79b in ?? () #25 0x28776f62 in ?? () #26 0x28776e45 in ?? () #27 0x287765c1 in ?? () #28 0x8055304 in ?? () #29 0x805caea in ?? () #30 0x805d267 in ?? () #31 0x804fdad in ?? () (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 10:40:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0BC337B400 for ; Mon, 1 Jul 2002 10:40:13 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FAD843E0A for ; Mon, 1 Jul 2002 10:40:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701174010.SXTD29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 17:40:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA91624; Mon, 1 Jul 2002 10:26:23 -0700 (PDT) Date: Mon, 1 Jul 2002 10:26:22 -0700 (PDT) From: Julian Elischer To: NAKAJI Hiroyuki Cc: freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> 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 the question is: did you update both kernel and userland? On Mon, 1 Jul 2002, NAKAJI Hiroyuki wrote: > >>>>> In <1025516273.442.5.camel@leeloo.intern.geht.de> > >>>>> Marc Recht wrote: > > > Can someone please check out a libc_r tree as of 3 days ago > > and try that... > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > failing that, can someone try newly compiled utilities on an older pre-KSE > > kernel? > > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > MR> post-KSE kernel (30.06.) and I've none of the described problems. > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > I updated my current box about an hour ago, and got into trouble too. > > My case is that amavis-milter dumps core with signal 11 and I cannot check > virus in emails. :( > > $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core > GNU gdb 5.2.0 (FreeBSD) 20020627 > Copyright 2002 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-undermydesk-freebsd"... > Core was generated by `amavis-milter'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /usr/lib/libmilter.so.2...done. > Loaded symbols for /usr/lib/libmilter.so.2 > Reading symbols from /usr/lib/libc_r.so.5...done. > Loaded symbols for /usr/lib/libc_r.so.5 > Reading symbols from /usr/lib/libc.so.5...done. > Loaded symbols for /usr/lib/libc.so.5 > Reading symbols from /usr/libexec/ld-elf.so.1...done. > Loaded symbols for /usr/libexec/ld-elf.so.1 > #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > (gdb) > -- > NAKAJI Hiroyuki > > 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 Jul 1 10:59:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37DB237B400 for ; Mon, 1 Jul 2002 10:59:17 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D95543E0A for ; Mon, 1 Jul 2002 10:59:16 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g61HxEe36420; Mon, 1 Jul 2002 13:59:14 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Mon, 1 Jul 2002 13:59:14 -0400 (EDT) From: Jeff Roberson To: julian@elischer.org Cc: current@freebsd.org Subject: Re: FW: UMA question.. In-Reply-To: Message-ID: <20020701135029.A91055-100000@mail.chesapeake.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 > > Jeff , (current included because it may be an interesting answer) > > > As you know I'm using UMA to allocate threads and cache them. > The 'constructor methods allow me to allocated threads that have been > pre-set up with thread stacks and other special items. > > > When they are being cached they still have their stacks etc. attached to > them. These are only splitt off when the UMA decides to stop caching an > item and actualy return it's memory to the system. > In this regard the UMA allocator is not a memory alocator but a 'complex > object allocator'... Very cool. > > Now my question.. > > I ant to allocate proc structures the same way... > in other words, I want a cached proc structure to already have a thread > attached to it and a stack attached to the thread.. > Is it legal for teh init function which is called by UMA to in turn > call UMA to allocate a sub element.. > > so if I do uma_zalloc(proc args) > that in turn should do a uma_zalloc(thread args). > would this work? is it legal? No locks are held when doing init ctor or fini. The zone and possibly per cpu queue lock is held while doing the dtor though. So it is safe as long as you don't cause a recursive allocation in the same zone. In short, what you want to do is perfectly reasonable. > > I need to allocate extra threads independantly of processes, but I could > work it so that freed process structures always had a single thread left > on them, which would save on allocations.. > In the future I need to do teh same for KSEs and KSEGRPS. sp having > UMA cache pre-constructed complex items made up of groups of separatly > UMA-allocated objects would be a great saving.. > > the question is.. will it work? can I call UMA from withing a UMA > constructor? > > > > 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 Jul 1 12: 2:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06E8837B400 for ; Mon, 1 Jul 2002 12:02:55 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0FD143E0A for ; Mon, 1 Jul 2002 12:02:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g61J2rT4019381; Mon, 1 Jul 2002 12:02:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g61J2r6k019380; Mon, 1 Jul 2002 12:02:53 -0700 (PDT) (envelope-from dillon) Date: Mon, 1 Jul 2002 12:02:53 -0700 (PDT) From: Matthew Dillon Message-Id: <200207011902.g61J2r6k019380@apollo.backplane.com> To: Julian Elischer Cc: freebsd-current@FreeBSD.ORG Subject: Weird panic (possibly KSE related) References: 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've been doing buildworld tests on an SMP build, 2-cpu 2550 w/ 2G of ram configured. It gets through two or three builds and then crashes. Unfortunately the crash seems to be completely undebuggable. It drops into DDB> but the serial port is completely screwed up and I can't type. Hitting gives me colons and semicolons at db> prompt. Changing baud rates does not seem to help. This has occured twice. I am going to try dropping back to a standard console to see if I can get better debugging. I don't know if this is KSE related or not. I've included the serial console output. -Matt Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 01000000 fault virtual address = 0xb fault code = supervisor write, page not present instruction pointer = 0xd35:0xe Fatal trap 12: page fault while in kernel mode cpuid = 0; lapic.id = 01000000 fault virtual addrepsasn i=: t nceode! p= cs puupeirdv =is o1r; lraeapdi n c, .pidag e= n0o0t00 0pr00es0e tDe niugnsgetrru("cptaioninc "p)oi Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 db> ;;: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 12: 9:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05F5D37B400 for ; Mon, 1 Jul 2002 12:09:45 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02DDA43E35 for ; Mon, 1 Jul 2002 12:02:00 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g61IbKTa003574; Mon, 1 Jul 2002 22:47:27 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g61IXDk5003541; Mon, 1 Jul 2002 22:33:20 +0400 (MSD) (envelope-from ache) Date: Mon, 1 Jul 2002 22:32:48 +0400 From: "Andrey A. Chernov" To: Julian Elischer Cc: NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r Message-ID: <20020701183102.GA2833@nagual.pp.ru> References: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.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 On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > the question is: > did you update both kernel and userland? This bug is not related to in-kernel KSE code (but, maybe related to header files compiled in). I got it even with updated userland and old pre-KSE kernel (with both updated I have it too). Only switching to libc_r old about month ago helps. > > > On Mon, 1 Jul 2002, NAKAJI Hiroyuki wrote: > > > >>>>> In <1025516273.442.5.camel@leeloo.intern.geht.de> > > >>>>> Marc Recht wrote: > > > > > Can someone please check out a libc_r tree as of 3 days ago > > > and try that... > > > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > > failing that, can someone try newly compiled utilities on an older pre-KSE > > > kernel? > > > > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > > MR> post-KSE kernel (30.06.) and I've none of the described problems. > > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > > > I updated my current box about an hour ago, and got into trouble too. > > > > My case is that amavis-milter dumps core with signal 11 and I cannot check > > virus in emails. :( > > > > $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core > > GNU gdb 5.2.0 (FreeBSD) 20020627 > > Copyright 2002 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-undermydesk-freebsd"... > > Core was generated by `amavis-milter'. > > Program terminated with signal 11, Segmentation fault. > > Reading symbols from /usr/lib/libmilter.so.2...done. > > Loaded symbols for /usr/lib/libmilter.so.2 > > Reading symbols from /usr/lib/libc_r.so.5...done. > > Loaded symbols for /usr/lib/libc_r.so.5 > > Reading symbols from /usr/lib/libc.so.5...done. > > Loaded symbols for /usr/lib/libc.so.5 > > Reading symbols from /usr/libexec/ld-elf.so.1...done. > > Loaded symbols for /usr/libexec/ld-elf.so.1 > > #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > (gdb) > > -- > > NAKAJI Hiroyuki > > > > 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 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 12:20:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BCF537B400 for ; Mon, 1 Jul 2002 12:20:13 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1294143E13 for ; Mon, 1 Jul 2002 12:20:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701192012.THPX9178.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 19:20:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA92142; Mon, 1 Jul 2002 12:09:09 -0700 (PDT) Date: Mon, 1 Jul 2002 12:09:08 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird panic (possibly KSE related) In-Reply-To: <200207011902.g61J2r6k019380@apollo.backplane.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 looks like 2 processors runing the ddb at the same time... On Mon, 1 Jul 2002, Matthew Dillon wrote: > I've been doing buildworld tests on an SMP build, 2-cpu 2550 w/ 2G of > ram configured. It gets through two or three builds and then crashes. > > Unfortunately the crash seems to be completely undebuggable. It drops > into DDB> but the serial port is completely screwed up and I can't type. > Hitting gives me colons and semicolons at db> prompt. Changing > baud rates does not seem to help. > > This has occured twice. I am going to try dropping back to a standard > console to see if I can get better debugging. I don't know if this is > KSE related or not. > > I've included the serial console output. > > -Matt > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; lapic.id = 01000000 > fault virtual address = 0xb > fault code = supervisor write, page not present > instruction pointer = 0xd35:0xe > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; lapic.id = 01000000 > fault virtual addrepsasn i=: > t nceode! > p= > > cs > puupeirdv =is o1r; lraeapdi > n c, .pidag e= n0o0t00 0pr00es0e > tDe > niugnsgetrru("cptaioninc "p)oi > Stopped at Debugger+0x46: xchgl %ebx,in_Debugger.0 > db> ;;: > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 12:30:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AABCA37B400 for ; Mon, 1 Jul 2002 12:30:44 -0700 (PDT) Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4399043E26 for ; Mon, 1 Jul 2002 12:30:43 -0700 (PDT) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 17P6sk-0003Fl-00; Mon, 1 Jul 2002 21:30:42 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.5/8.12.5) with ESMTP id g61IonoU013387 for ; Mon, 1 Jul 2002 20:50:49 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.5/8.12.5/Submit) id g61IomHx013386 for freebsd-current@freebsd.org; Mon, 1 Jul 2002 20:50:48 +0200 (CEST) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: LP64: (int)signal() Date: Mon, 1 Jul 2002 18:50:48 +0000 (UTC) Message-ID: References: <20020701111919.B20124@espresso.q9media.com> 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 Mike Barcroft wrote: > You might want to get rid of the other misuse of `rc' above this and > just remove the variable. The use of an gratuitous int variable rc to capture return values is rampant throughout this code. In fact, not using it is something of a violation of the local style, but in the case of signal() I think it's justifiable because SIG_ERR is so much neater than changing rc to long and messing around with explicit casts. -- 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 Mon Jul 1 12:39: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 149A737B400 for ; Mon, 1 Jul 2002 12:38:59 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 824ED43E13 for ; Mon, 1 Jul 2002 12:38:57 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 30926 invoked by uid 0); 1 Jul 2002 19:38:56 -0000 Received: from pd900332a.dip.t-dialin.net (HELO gmx.net) (217.0.51.42) by mail.gmx.net (mp013-rz3) with SMTP; 1 Jul 2002 19:38:56 -0000 Message-ID: <3D20AFC7.8020006@gmx.net> Date: Mon, 01 Jul 2002 21:38:47 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: Julian Elischer , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r References: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> <20020701183102.GA2833@nagual.pp.ru> X-Enigmail-Version: 0.61.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC4EDBCAA613597D61A840380" 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 The following is an OpenPGP/MIME signed message created by Enigmail/Mozilla, following RFC 2440 and RFC 2015 --------------enigC4EDBCAA613597D61A840380 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Andrey A. Chernov wrote: > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > >>the question is: >>did you update both kernel and userland? > > > This bug is not related to in-kernel KSE code (but, maybe related to > header files compiled in). I got it even with updated userland and old > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > old about month ago helps. I applied "thediff" to a -CURRENT box as of June 25th and it promptly shows the symptoms, so I still think it's somewhere in the KSE-code. Regards, -- Michael Nottebrock "The circumstance ends uglily in the cruel result." - Babelfish --------------enigC4EDBCAA613597D61A840380 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9IK/LXhc68WspdLARAtx/AJ4+RmsemwJbilcfSfxzJBwzebcL4ACfRWxw S2Ohg/flU1K/tLSKIFhP1Ao= =EYvD -----END PGP SIGNATURE----- --------------enigC4EDBCAA613597D61A840380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 12:40:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DE4537B406 for ; Mon, 1 Jul 2002 12:40:08 -0700 (PDT) Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id A65D643E0A for ; Mon, 1 Jul 2002 12:40:07 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701194007.UOLT15755.rwcrmhc53.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 19:40:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA92199; Mon, 1 Jul 2002 12:20:30 -0700 (PDT) Date: Mon, 1 Jul 2002 12:20:28 -0700 (PDT) From: Julian Elischer To: "Andrey A. Chernov" Cc: NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701183102.GA2833@nagual.pp.ru> 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 On Mon, 1 Jul 2002, Andrey A. Chernov wrote: > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > > the question is: > > did you update both kernel and userland? > > This bug is not related to in-kernel KSE code (but, maybe related to > header files compiled in). I got it even with updated userland and old > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > old about month ago helps. Ok this is good news becasue it helps narrow the problem. If an old libc_r runs well it at least suggests that the kernel is working as it should. That is a great relief to me! My current guess is that something in an include file is poisonning the compile of a new libc_r. I think we may need Dan to help us find it.. > > > > > > > On Mon, 1 Jul 2002, NAKAJI Hiroyuki wrote: > > > > > >>>>> In <1025516273.442.5.camel@leeloo.intern.geht.de> > > > >>>>> Marc Recht wrote: > > > > > > > Can someone please check out a libc_r tree as of 3 days ago > > > > and try that... > > > > > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > > > failing that, can someone try newly compiled utilities on an older pre-KSE > > > > kernel? > > > > > > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > > > MR> post-KSE kernel (30.06.) and I've none of the described problems. > > > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > > > > > I updated my current box about an hour ago, and got into trouble too. > > > > > > My case is that amavis-milter dumps core with signal 11 and I cannot check > > > virus in emails. :( > > > > > > $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core > > > GNU gdb 5.2.0 (FreeBSD) 20020627 > > > Copyright 2002 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-undermydesk-freebsd"... > > > Core was generated by `amavis-milter'. > > > Program terminated with signal 11, Segmentation fault. > > > Reading symbols from /usr/lib/libmilter.so.2...done. > > > Loaded symbols for /usr/lib/libmilter.so.2 > > > Reading symbols from /usr/lib/libc_r.so.5...done. > > > Loaded symbols for /usr/lib/libc_r.so.5 > > > Reading symbols from /usr/lib/libc.so.5...done. > > > Loaded symbols for /usr/lib/libc.so.5 > > > Reading symbols from /usr/libexec/ld-elf.so.1...done. > > > Loaded symbols for /usr/libexec/ld-elf.so.1 > > > #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > (gdb) > > > -- > > > NAKAJI Hiroyuki > > > > > > 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 > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > 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 Jul 1 13: 0:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0227A37B400 for ; Mon, 1 Jul 2002 13:00:18 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 935F543E0A for ; Mon, 1 Jul 2002 13:00:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701200017.ULZU9178.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 20:00:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA92346; Mon, 1 Jul 2002 12:56:04 -0700 (PDT) Date: Mon, 1 Jul 2002 12:56:03 -0700 (PDT) From: Julian Elischer To: "Andrey A. Chernov" Cc: NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701183102.GA2833@nagual.pp.ru> 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 is there any chance you can try compile a new libc_r but with old versions of proc.h and queue.h in the system? On Mon, 1 Jul 2002, Andrey A. Chernov wrote: > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > > the question is: > > did you update both kernel and userland? > > This bug is not related to in-kernel KSE code (but, maybe related to > header files compiled in). I got it even with updated userland and old > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > old about month ago helps. > > > > > > > On Mon, 1 Jul 2002, NAKAJI Hiroyuki wrote: > > > > > >>>>> In <1025516273.442.5.camel@leeloo.intern.geht.de> > > > >>>>> Marc Recht wrote: > > > > > > > Can someone please check out a libc_r tree as of 3 days ago > > > > and try that... > > > > > > > > There was a commit in libc_r/uthreads 2 days ago that might be relevant. > > > > failing that, can someone try newly compiled utilities on an older pre-KSE > > > > kernel? > > > > > > MR> I don't know if this helps, but I've a pre-KSE userland (28.06.), a > > > MR> post-KSE kernel (30.06.) and I've none of the described problems. > > > MR> Evolution, KDE3, Mozilla, ogg123, jdk13 all run without a problem. > > > > > > I updated my current box about an hour ago, and got into trouble too. > > > > > > My case is that amavis-milter dumps core with signal 11 and I cannot check > > > virus in emails. :( > > > > > > $ sudo gdb ./amavis-milter /etc/mail/amavis-milter.core > > > GNU gdb 5.2.0 (FreeBSD) 20020627 > > > Copyright 2002 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-undermydesk-freebsd"... > > > Core was generated by `amavis-milter'. > > > Program terminated with signal 11, Segmentation fault. > > > Reading symbols from /usr/lib/libmilter.so.2...done. > > > Loaded symbols for /usr/lib/libmilter.so.2 > > > Reading symbols from /usr/lib/libc_r.so.5...done. > > > Loaded symbols for /usr/lib/libc_r.so.5 > > > Reading symbols from /usr/lib/libc.so.5...done. > > > Loaded symbols for /usr/lib/libc.so.5 > > > Reading symbols from /usr/libexec/ld-elf.so.1...done. > > > Loaded symbols for /usr/libexec/ld-elf.so.1 > > > #0 0x2808e918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5 > > > (gdb) > > > -- > > > NAKAJI Hiroyuki > > > > > > 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 > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > 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 Jul 1 13: 7:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3140337B421 for ; Mon, 1 Jul 2002 13:07:44 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7692643E0A for ; Mon, 1 Jul 2002 13:07:43 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g61K7BoL028628; Mon, 1 Jul 2002 16:07:11 -0400 (EDT) Date: Mon, 1 Jul 2002 16:07:11 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > is there any chance you can try compile a new libc_r but with old versions > of proc.h and queue.h in the system? What changed in queue.h? We do have some macros defined for presetting queue.h *_HEAD's. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 13: 7:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CB3E37B406 for ; Mon, 1 Jul 2002 13:07:48 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13FAB43E13 for ; Mon, 1 Jul 2002 13:07:48 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g61K56Fe028298; Mon, 1 Jul 2002 16:05:06 -0400 (EDT) Date: Mon, 1 Jul 2002 16:05:06 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > > On Mon, 1 Jul 2002, Andrey A. Chernov wrote: > > > On Mon, Jul 01, 2002 at 10:26:22 -0700, Julian Elischer wrote: > > > the question is: > > > did you update both kernel and userland? > > > > This bug is not related to in-kernel KSE code (but, maybe related to > > header files compiled in). I got it even with updated userland and old > > pre-KSE kernel (with both updated I have it too). Only switching to libc_r > > old about month ago helps. > > Ok this is good news becasue it helps narrow the problem. > If an old libc_r runs well it at least suggests that the kernel is > working as it should. That is a great relief to me! > > My current guess is that something in an include file is poisonning the > compile of a new libc_r. > > I think we may need Dan to help us find it.. I'm a few days away from being able to upgrade to the latest -current. I'd suspect that it is something to do with the layout of the fpregs, mcontext or something like that. Libc_r mucks about in jmp_buf (userland) and ucontext/mcontext, so anything that changed those would cause problems. You can enable error checking when compiling libc_r and see if anything comes up too. It should be relatively error free (other than a few _ not being defined). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 13:10:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7227137B400 for ; Mon, 1 Jul 2002 13:10:35 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABE0A43E0A for ; Mon, 1 Jul 2002 13:10:34 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g61KAYL7029158; Mon, 1 Jul 2002 16:10:34 -0400 (EDT) Date: Mon, 1 Jul 2002 16:10:33 -0400 (EDT) From: Daniel Eischen To: Christian Weisgerber Cc: freebsd-current@FreeBSD.ORG Subject: Re: LP64: (int)signal() In-Reply-To: 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 On Mon, 1 Jul 2002, Christian Weisgerber wrote: > Mike Barcroft wrote: > > > You might want to get rid of the other misuse of `rc' above this and > > just remove the variable. > > The use of an gratuitous int variable rc to capture return values > is rampant throughout this code. In fact, not using it is something > of a violation of the local style, but in the case of signal() I > think it's justifiable because SIG_ERR is so much neater than > changing rc to long and messing around with explicit casts. How about eliminating signal() all together and using sigaction()? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 13:40:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0CE337B401 for ; Mon, 1 Jul 2002 13:40:12 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DA4B43E2F for ; Mon, 1 Jul 2002 13:40:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701204012.VQDT9178.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 20:40:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA92519; Mon, 1 Jul 2002 13:20:41 -0700 (PDT) Date: Mon, 1 Jul 2002 13:20:40 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 I have some debug stuff added for TAILQs theoretically it should be defined out but I don't trust theory :-) On Mon, 1 Jul 2002, Daniel Eischen wrote: > On Mon, 1 Jul 2002, Julian Elischer wrote: > > > is there any chance you can try compile a new libc_r but with old versions > > of proc.h and queue.h in the system? > > What changed in queue.h? We do have some macros defined for presetting > queue.h *_HEAD's. > > -- > Dan Eischen > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 13:40:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD44037B47F for ; Mon, 1 Jul 2002 13:40:19 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49BC443E0A for ; Mon, 1 Jul 2002 13:40:19 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701204018.VQGB9178.rwcrmhc51.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 20:40:18 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA92521; Mon, 1 Jul 2002 13:23:32 -0700 (PDT) Date: Mon, 1 Jul 2002 13:23:32 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 I don't change any of those. On Mon, 1 Jul 2002, Daniel Eischen wrote: > > I'd suspect that it is something to do with the layout of > the fpregs, mcontext or something like that. Libc_r mucks > about in jmp_buf (userland) and ucontext/mcontext, so anything > that changed those would cause problems. > It's still unclear if a KSE kernel works with an old libc_r or visa versa. I'd like to see if a new libc_r works with an old kernel (someone who can boot kernel.back and test...) to check if you have a non KSE kernel, sysctl kern.threads will only succeed in a new kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 13:50:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CFF637B401 for ; Mon, 1 Jul 2002 13:50:52 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72EF543E39 for ; Mon, 1 Jul 2002 13:50:50 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g61Koaud005132; Mon, 1 Jul 2002 16:50:36 -0400 (EDT) Date: Mon, 1 Jul 2002 16:50:35 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > I don't change any of those. > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > > I'd suspect that it is something to do with the layout of > > the fpregs, mcontext or something like that. Libc_r mucks > > about in jmp_buf (userland) and ucontext/mcontext, so anything > > that changed those would cause problems. > > > > > It's still unclear if a KSE kernel works with an old libc_r or visa versa. > > I'd like to see if a new libc_r works with an old kernel (someone who can > boot kernel.back and test...) > > to check if you have a non KSE kernel, > sysctl kern.threads will only succeed in a new kernel. I also made changes to uthread_sigpending.c and uthread_sigsuspend.c 3 days ago (lib/libc_r/uthread/...). You can try reverting those changes and go back to revisions 1.18 and 1.11 respectively. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 14:34:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE9DF37B400 for ; Mon, 1 Jul 2002 14:34:20 -0700 (PDT) Received: from vbook.express.ru (vbook.nc.express.ru [212.24.37.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A723643E0A for ; Mon, 1 Jul 2002 14:34:19 -0700 (PDT) (envelope-from vova@express.ru) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 17P8o9-0000RL-00; Tue, 02 Jul 2002 01:34:05 +0400 Subject: Re: More on gnome and mozilla (post-KSE) From: "Vladimir B. " Grebenschikov To: Julian Elischer Cc: walt , freebsd-current@freebsd.org In-Reply-To: References: Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.7 Date: 02 Jul 2002 01:34:05 +0400 Message-Id: <1025559245.866.17.camel@vbook.express.ru> Mime-Version: 1.0 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 =F7 Mon, 01.07.2002, =D7 00:21, Julian Elischer =CE=C1=D0=C9=D3=C1=CC: > hmmmmmmm > well, since the only changes were in the kernel except for libkvm > I'm puzzled. If you boot off the old kernel (You still have it right? :-) > does it still act the same? I have same problem, reverting to old (20020625) kernel not helps :( I was forced to get old world and make world. gkrellm gets 11 signal too, licq eats 100%CPU after forking qt plugin > On Sun, 30 Jun 2002, walt wrote: >=20 > > Dunno if this is important, but I meant to mention it in my > > initial problem report: the problem with gnome and mozilla > > chewing up CPU cycles begain just after the make world > > finished and while the make kernel was still compiling, > > so whatever this problem is it was not due to changes > > in the kernel. > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message >=20 --=20 Vladimir B. Grebenschikov vova@sw.ru, SWsoft, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 14:40:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A10537B401 for ; Mon, 1 Jul 2002 14:40:03 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36FBA43E2F for ; Mon, 1 Jul 2002 14:40:00 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from chemikals.org (www@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with SMTP id g61Ldl7B017273; Mon, 1 Jul 2002 17:39:47 -0400 (EDT) (envelope-from morganw@chemikals.org) From: Wesley Morgan Received: from 148.175.49.1 (SquirrelMail authenticated user morganw) by www.chemikals.org with HTTP; Mon, 1 Jul 2002 17:39:48 -0400 (EDT) Message-ID: <17419.148.175.49.1.1025559588.squirrel@www.chemikals.org> Date: Mon, 1 Jul 2002 17:39:48 -0400 (EDT) Subject: Re: Post-KSE disaster with libc_r To: In-Reply-To: References: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: , , , X-Mailer: SquirrelMail (version 1.2.6) 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 Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, still crashes all threaded systems. Same behavior on a 20020620 kernel. > I don't change any of those. > > On Mon, 1 Jul 2002, Daniel Eischen wrote: >> >> I'd suspect that it is something to do with the layout of >> the fpregs, mcontext or something like that. Libc_r mucks >> about in jmp_buf (userland) and ucontext/mcontext, so anything >> that changed those would cause problems. >> > > > It's still unclear if a KSE kernel works with an old libc_r or visa > versa. > > I'd like to see if a new libc_r works with an old kernel (someone who > can boot kernel.back and test...) > > to check if you have a non KSE kernel, > sysctl kern.threads will only succeed in a new kernel. > > > > 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 Jul 1 14:55:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB91837B400 for ; Mon, 1 Jul 2002 14:55:04 -0700 (PDT) Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CFC143E09 for ; Mon, 1 Jul 2002 14:55:04 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g61LsuC49780 for ; Mon, 1 Jul 2002 14:54:56 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by mail.meer.net (8.12.2/8.12.1/meer) with ESMTP id g61Lt3pb037741 for ; Mon, 1 Jul 2002 14:55:03 -0700 (PDT) Message-Id: <200207012155.g61Lt3pb037741@mail.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: freebsd-current@freebsd.org Subject: picobsd redux Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Jul 2002 14:55:03 -0700 From: "George V. Neville-Neil" 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 Hey Folks, So now I'm working somewhere that we're trying to use Picobsd on the Soekris boards (www.soekris.com). Right now there is a build problem I'm trying to solve. When picobsd goes to build the libraries etc. it chokes on the csu stuff: CC="cc" MKDEP_CPP_OPTS="-M -DCRT_BEGIN" mkdep -f .depend -a -nostdinc -I/sandb oxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/sandboxes /gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/config -I/sandboxes/gnn/FreeBS D/src/gnu/lib/csu/../../../contrib/gcc -I. -I/sandboxes/gnn/FreeBSD/src/gnu/lib / csu/../../usr.bin/cc/cc_tools /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../ c ontrib/gcc/crtstuff.c cc -nostdinc -I/sandboxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_ FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-o mit-frame-pointer -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc / config -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc -I. -I/san dboxes/gnn/FreeBSD/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN - c -o crtbegin.o /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crt s tuff.c In file included from /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/g c c/crtstuff.c:63: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37 : field `array' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:13 5 : field `augmentation' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:14 3 : field `pc_begin' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: warn ing: `used' attribute directive ignored /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In funct ion `__do_global_dtors_aux': /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: synt ax error before `completed' /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: `com pleted' undeclared (first use in this function) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: (Eac h undeclared identifier is reported only once /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for each function it appears in.) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top l evel: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: warn ing: `used' attribute directive ignored *** Error code 1 Any pointers would be great, I need to get this stuff back up to snuff fast. Thanks, George -- George V. Neville-Neil gnn@neville-neil.com Neville-Neil Consulting www.neville-neil.com "I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan -- George V. Neville-Neil gnn@neville-neil.com Neville-Neil Consulting www.neville-neil.com "I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 14:56:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C74637B401 for ; Mon, 1 Jul 2002 14:56:36 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 72B7143E09 for ; Mon, 1 Jul 2002 14:56:35 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 16547 invoked by uid 0); 1 Jul 2002 21:56:33 -0000 Received: from pd900332a.dip.t-dialin.net (HELO gmx.net) (217.0.51.42) by mail.gmx.net (mp007-rz3) with SMTP; 1 Jul 2002 21:56:33 -0000 Message-ID: <3D20D00D.4080301@gmx.net> Date: Mon, 01 Jul 2002 23:56:29 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0rc2) Gecko/20020513 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current Subject: [Fwd: Re: Post-KSE disaster with libc_r] X-Enigmail-Version: 0.61.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE33884B7E865AD679ADC17E8" 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 The following is an OpenPGP/MIME signed message created by Enigmail/Mozilla, following RFC 2440 and RFC 2015 --------------enigE33884B7E865AD679ADC17E8 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Somehow this thread slipped into privmail. -------- Original Message -------- Subject: Re: Post-KSE disaster with libc_r Date: Mon, 1 Jul 2002 14:23:23 -0700 (PDT) From: Julian Elischer To: Michael Nottebrock > [Applied 'thediff' to pre-KSE CURRENT and rebuilt world, things > break, things remain broken when booting the old kernel with the > new world.] THANKS!!! ok so it's libc_r for sure.. now we have two possibilities: 1/ It's ingherrently broken because of a recent change. if so, checking out 1 month old sources to libc_r and compiling it should yield a working libc_r. 2/ Something I've committed is polluting the compile. e.g. a namespace clash or similar in a new include file. In this case, teh new compile of old sources should yield a bad libc_r. can someone test this? --------------enigE33884B7E865AD679ADC17E8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9INAQXhc68WspdLARAviCAKCj8zNGdIVUHe2Jo4+h5L0JHkHCkgCfaAoZ jlAnHgZpqhsOIT7/qeayJlQ= =2ZN3 -----END PGP SIGNATURE----- --------------enigE33884B7E865AD679ADC17E8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 15:20:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6689537B406 for ; Mon, 1 Jul 2002 15:20:26 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5F2743E0A for ; Mon, 1 Jul 2002 15:20:24 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020701222023.RUXK903.sccrmhc03.attbi.com@InterJet.elischer.org>; Mon, 1 Jul 2002 22:20:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA93120; Mon, 1 Jul 2002 15:14:09 -0700 (PDT) Date: Mon, 1 Jul 2002 15:14:07 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: eischen@pcnet1.pcnet.com, ache@nagual.pp.ru, nakaji@boggy.acest.tutrp.tut.ac.jp, freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <17419.148.175.49.1.1025559588.squirrel@www.chemikals.org> 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 can you try compiling a new libc_r with th efollowing change suggested by Dan Eischen: ------begin quote: I also made changes to uthread_sigpending.c and uthread_sigsuspend.c 3 days ago (lib/libc_r/uthread/...). You can try reverting those changes and go back to revisions 1.18 and 1.11 respectively. ------end quote.. so that is uthread_sigpending.c version 1.18 and uthread_sigsuspend.c version 1.11 Thanks Julian On Mon, 1 Jul 2002, Wesley Morgan wrote: > Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, > still crashes all threaded systems. Same behavior on a 20020620 kernel. > > I don't change any of those. > > > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > >> > >> I'd suspect that it is something to do with the layout of > >> the fpregs, mcontext or something like that. Libc_r mucks > >> about in jmp_buf (userland) and ucontext/mcontext, so anything > >> that changed those would cause problems. > >> > > > > > > It's still unclear if a KSE kernel works with an old libc_r or visa > > versa. > > > > I'd like to see if a new libc_r works with an old kernel (someone who > > can boot kernel.back and test...) > > > > to check if you have a non KSE kernel, > > sysctl kern.threads will only succeed in a new kernel. > > > > > > > > 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 Jul 1 16: 4:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF74E37B400 for ; Mon, 1 Jul 2002 16:04:30 -0700 (PDT) Received: from volatile.chemikals.org (cae88-49-048.sc.rr.com [24.88.49.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 043AD43E09 for ; Mon, 1 Jul 2002 16:04:30 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.3/8.12.3) with ESMTP id g61N4F7C017813; Mon, 1 Jul 2002 19:04:15 -0400 (EDT) (envelope-from morganw@chemikals.org) Date: Mon, 1 Jul 2002 19:04:15 -0400 (EDT) From: Wesley Morgan To: Julian Elischer Cc: eischen@pcnet1.pcnet.com, , , Subject: Re: Post-KSE disaster with libc_r In-Reply-To: Message-ID: <20020701190330.G17798-100000@volatile.chemikals.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 I already tried that this morning, it had no effect ... Unless you would like me to try an old kernel with it On Mon, 1 Jul 2002, Julian Elischer wrote: > can you try compiling a new libc_r with th efollowing change suggested by > Dan Eischen: > > ------begin quote: > > I also made changes to uthread_sigpending.c and uthread_sigsuspend.c > 3 days ago (lib/libc_r/uthread/...). You can try reverting those > changes and go back to revisions 1.18 and 1.11 respectively. > > ------end quote.. > > so that is uthread_sigpending.c version 1.18 > and > uthread_sigsuspend.c version 1.11 > > Thanks > > Julian > > > > > On Mon, 1 Jul 2002, Wesley Morgan wrote: > > > Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, > > still crashes all threaded systems. Same behavior on a 20020620 kernel. > > > I don't change any of those. > > > > > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > >> > > >> I'd suspect that it is something to do with the layout of > > >> the fpregs, mcontext or something like that. Libc_r mucks > > >> about in jmp_buf (userland) and ucontext/mcontext, so anything > > >> that changed those would cause problems. > > >> > > > > > > > > > It's still unclear if a KSE kernel works with an old libc_r or visa > > > versa. > > > > > > I'd like to see if a new libc_r works with an old kernel (someone who > > > can boot kernel.back and test...) > > > > > > to check if you have a non KSE kernel, > > > sysctl kern.threads will only succeed in a new kernel. > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 17: 0:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2312B37B405 for ; Mon, 1 Jul 2002 17:00:24 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8513343E09 for ; Mon, 1 Jul 2002 17:00:23 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702000022.WRUA6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 00:00:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA93479; Mon, 1 Jul 2002 16:54:53 -0700 (PDT) Date: Mon, 1 Jul 2002 16:54:52 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: eischen@pcnet1.pcnet.com, ache@nagual.pp.ru, nakaji@boggy.acest.tutrp.tut.ac.jp, freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: <20020701190330.G17798-100000@volatile.chemikals.org> 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 oops,, sorry, you are right.. still it's being so confusing with people saying this and that, that it's only now that I'm starting to believe that it's not the kernel doing something nasty. On Mon, 1 Jul 2002, Wesley Morgan wrote: > I already tried that this morning, it had no effect ... Unless you would > like me to try an old kernel with it > > On Mon, 1 Jul 2002, Julian Elischer wrote: > > > can you try compiling a new libc_r with th efollowing change suggested by > > Dan Eischen: > > > > ------begin quote: > > > > I also made changes to uthread_sigpending.c and uthread_sigsuspend.c > > 3 days ago (lib/libc_r/uthread/...). You can try reverting those > > changes and go back to revisions 1.18 and 1.11 respectively. > > > > ------end quote.. > > > > so that is uthread_sigpending.c version 1.18 > > and > > uthread_sigsuspend.c version 1.11 > > > > Thanks > > > > Julian > > > > > > > > > > On Mon, 1 Jul 2002, Wesley Morgan wrote: > > > > > Reverting proc.h and queue.h do nothing. Booting a kernel from 20020624, > > > still crashes all threaded systems. Same behavior on a 20020620 kernel. > > > > I don't change any of those. > > > > > > > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > >> > > > >> I'd suspect that it is something to do with the layout of > > > >> the fpregs, mcontext or something like that. Libc_r mucks > > > >> about in jmp_buf (userland) and ucontext/mcontext, so anything > > > >> that changed those would cause problems. > > > >> > > > > > > > > > > > > It's still unclear if a KSE kernel works with an old libc_r or visa > > > > versa. > > > > > > > > I'd like to see if a new libc_r works with an old kernel (someone who > > > > can boot kernel.back and test...) > > > > > > > > to check if you have a non KSE kernel, > > > > sysctl kern.threads will only succeed in a new kernel. > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > > > > > > > -- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 17:19:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F7CE37B400 for ; Mon, 1 Jul 2002 17:19:06 -0700 (PDT) Received: from relay4.kornet.net (relay4.kornet.net [211.48.62.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC0943E09 for ; Mon, 1 Jul 2002 17:19:05 -0700 (PDT) (envelope-from hyun10310@kornet.net) Received: from your-afc98a0fg0 (61.73.155.230) by relay4.kornet.net; 2 Jul 2002 09:18:56 +0900 Message-ID: <3d20f1743d571313@relay4.kornet.net> (added by relay4.kornet.net) From: =?ks_c_5601-1987?B?vLy9ur+1vu4=?= To: freebsd-current@freebsd.org Subject: =?ks_c_5601-1987?B?W7GksO1dIGZyZWVic2QtY3VycmVudLTUICC3zrn2xq7H0riuwMcgvNO8ur+1vu668bn9wMwgtOOx5CC5q7fhu/nHw8XXwMzHwbimIL3Fw7vHz7y8v+Qu?= Date: Tue, 02 Jul 2002 09:18:56 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0097_01C0F18A.93A56C00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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. ------=_NextPart_000_0097_01C0F18A.93A56C00 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 Y2VzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KILHNx8/AxyC9 wrb0vvjAzCDIq7q4vLogwPzA2iC/7MbtwLsgurizu7DUILXIIMGhIMGkwd/I9yC757D6ILXl uLO0z7TZLg0KIMGkurjF673FuMHAzL/rw8vB+Ln9ILHUwaTAuyDB2Lz2x8+/qSCxpLDtuN7A z8DTwLsgx6W9w8fPv7TAuLjnLCAgvPa9xbDFus4gwOXEobimILi2t8PHz7DtIMDWvcC0z7TZ Lg0KILHNx8/AxyDA/MDaIL/sxu0gwda80rTCIMDOxc2z3SC788DHILD4sLO1yCDA5bzSv6G8 rSC9wLXmx8+/tMC4uOcsIMD6yPG0wiCxzcfPwMcgwPzA2r/sxu0gwda80iC/3A0KIL7utrDH 0SCws8DOwaS6uLW1ILChwfaw7SDA1sH2IL7KwLi5x7fOIL7IvcnHz73DseIgudm2+LTPtNku DQogvPa9xcC7IL/4xKEgvsrAuL3DuOkgvPa9xbDFus64piAgxay4r8fYIMHWvcq9w7/kLg0K ICAgICAg ------=_NextPart_000_0097_01C0F18A.93A56C00 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCEtLSBzYXZlZCBmcm9tIHVybD0oMDAyMilodHRwOi8vaW50ZXJuZXQuZS1tYWlsIC0tPg0K PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT5jZXM8L3RpdGxlPg0KPG1ldGEgaHR0cC1lcXVpdj0i Q29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9ZXVjLWtyIj4NCjxz Y3JpcHQgbGFuZ3VhZ2U9IkphdmFTY3JpcHQiPg0KPCEtLQ0KZnVuY3Rpb24gTU1fb3BlbkJy V2luZG93KHRoZVVSTCx3aW5OYW1lLGZlYXR1cmVzKSB7IC8vdjIuMA0KICB3aW5kb3cub3Bl bih0aGVVUkwsd2luTmFtZSxmZWF0dXJlcyk7DQp9DQovLy0tPg0KPC9zY3JpcHQ+DQo8L2hl YWQ+DQoNCjxib2R5IGJnY29sb3I9IiNGRkZGRkYiIHRleHQ9IiMwMDAwMDAiPg0KPHRhYmxl IGJvcmRlcj0wIGNlbGxwYWRkaW5nPTAgY2VsbHNwYWNpbmc9MD4NCiAgPHRyPiANCiAgICA8 dGQ+PGltZyBzcmM9Imh0dHA6Ly93d3cubWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9p bWcvY2VzdG9ja3lfbWFpbF8wMS5qcGciIHdpZHRoPTIzMiBoZWlnaHQ9MjI3PjwvdGQ+DQog ICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1 MDEvaW1nL2Nlc3RvY2t5X21haWxfMDIuanBnIiB3aWR0aD0xMjggaGVpZ2h0PTIyNz48L3Rk Pg0KICAgIDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9lbWFp bC8wNTAxL2ltZy9jZXN0b2NreV9tYWlsXzAzLmpwZyIgd2lkdGg9NjMgaGVpZ2h0PTIyNz48 L3RkPg0KICAgIDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9l bWFpbC8wNTAxL2ltZy8vY2VzdG9ja3lfbWFpbF8wNC5qcGciIHdpZHRoPTEyOCBoZWlnaHQ9 MjI3PjwvdGQ+DQogICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNv LmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5X21haWxfMDUuanBnIiB3aWR0aD02MCBoZWln aHQ9MjI3PjwvdGQ+DQogIDwvdHI+DQogIDx0cj4gDQogICAgPHRkPjxpbWcgc3JjPSJodHRw Oi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5X21haWxf MDYuanBnIiB3aWR0aD0yMzIgaGVpZ2h0PTE4PjwvdGQ+DQogICAgPHRkPjxpbWcgc3JjPSJo dHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5X21h aWxfMDcuanBnIiB3aWR0aD0xMjggaGVpZ2h0PTE4PjwvdGQ+DQogICAgPHRkPjxpbWcgc3Jj PSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5 X21haWxfMDguanBnIiB3aWR0aD02MyBoZWlnaHQ9MTg+PC90ZD4NCiAgICA8dGQ+PGEgaHJl Zj0iamF2YXNjcmlwdDo7IiBvbkNsaWNrPSJNTV9vcGVuQnJXaW5kb3coJ2h0dHA6Ly93d3cu bWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9mb3JtLmh0bScsJ2Zvcm0nLCd3aWR0aD01 NzAsaGVpZ2h0PTQxMCcpIj48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5r ci9lbWFpbC8wNTAxL2ltZy9jZXN0b2NreV9tYWlsXzA5LmpwZyIgd2lkdGg9MTI4IGhlaWdo dD0xOCBib3JkZXI9MD48L2E+PC90ZD4NCiAgICA8dGQ+PGltZyBzcmM9Imh0dHA6Ly93d3cu bWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9pbWcvY2VzdG9ja3lfbWFpbF8xMC5qcGci IHdpZHRoPTYwIGhlaWdodD0xOD48L3RkPg0KICA8L3RyPg0KICA8dHI+IA0KICAgIDx0ZD48 aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9lbWFpbC8wNTAxL2ltZy9j ZXN0b2NreV9tYWlsXzExLmpwZyIgd2lkdGg9MjMyIGhlaWdodD03MDg+PC90ZD4NCiAgICA8 dGQ+PGltZyBzcmM9Imh0dHA6Ly93d3cubWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9p bWcvY2VzdG9ja3lfbWFpbF8xMi5qcGciIHdpZHRoPTEyOCBoZWlnaHQ9NzA4PjwvdGQ+DQog ICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1 MDEvaW1nL2Nlc3RvY2t5X21haWxfMTMuanBnIiB3aWR0aD02MyBoZWlnaHQ9NzA4PjwvdGQ+ DQogICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWls LzA1MDEvaW1nL2Nlc3RvY2t5X21haWxfMTQuanBnIiB3aWR0aD0xMjggaGVpZ2h0PTcwOD48 L3RkPg0KICAgIDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9l bWFpbC8wNTAxL2ltZy9jZXN0b2NreV9tYWlsXzE1LmpwZyIgd2lkdGg9NjAgaGVpZ2h0PTcw OD48L3RkPg0KICA8L3RyPg0KICA8dHI+IA0KICAgIDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3 dy5tYWlscGFydG5lci5jby5rci9lbWFpbC8wNTAxL2ltZy9jZXN0b2NreV9tYWlsXzE2Lmpw ZyIgd2lkdGg9MjMyIGhlaWdodD0xOD48L3RkPg0KICAgIDx0ZD48YSBocmVmPSJqYXZhc2Ny aXB0OjsiIG9uQ2xpY2s9Ik1NX29wZW5CcldpbmRvdygnaHR0cDovL3d3dy5tYWlscGFydG5l ci5jby5rci9lbWFpbC8wNTAxL2Zvcm0uaHRtJywnZm9ybScsJ3dpZHRoPTU3MCxoZWlnaHQ9 NDAwJykiPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0bmVyLmNvLmtyL2VtYWlsLzA1 MDEvaW1nL2Nlc3RvY2t5X21haWxfMTcuanBnIiB3aWR0aD0xMjggaGVpZ2h0PTE4IGJvcmRl cj0wPjwvYT48L3RkPg0KICAgIDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5l ci5jby5rci9lbWFpbC8wNTAxL2ltZy9jZXN0b2NreV9tYWlsXzE4LmpwZyIgd2lkdGg9NjMg aGVpZ2h0PTE4PjwvdGQ+DQogICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxwYXJ0 bmVyLmNvLmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5X21haWxfMTkuanBnIiB3aWR0aD0x MjggaGVpZ2h0PTE4PjwvdGQ+DQogICAgPHRkPjxpbWcgc3JjPSJodHRwOi8vd3d3Lm1haWxw YXJ0bmVyLmNvLmtyL2VtYWlsLzA1MDEvaW1nL2Nlc3RvY2t5X21haWxfMjAuanBnIiB3aWR0 aD02MCBoZWlnaHQ9MTg+PC90ZD4NCiAgPC90cj4NCiAgPHRyPiANCiAgICA8dGQ+PGltZyBz cmM9Imh0dHA6Ly93d3cubWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9pbWcvY2VzdG9j a3lfbWFpbF8yMS5qcGciIHdpZHRoPTIzMiBoZWlnaHQ9Mjk+PC90ZD4NCiAgICA8dGQ+PGlt ZyBzcmM9Imh0dHA6Ly93d3cubWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9pbWcvY2Vz dG9ja3lfbWFpbF8yMi5qcGciIHdpZHRoPTEyOCBoZWlnaHQ9Mjk+PC90ZD4NCiAgICA8dGQ+ PGltZyBzcmM9Imh0dHA6Ly93d3cubWFpbHBhcnRuZXIuY28ua3IvZW1haWwvMDUwMS9pbWcv Y2VzdG9ja3lfbWFpbF8yMy5qcGciIHdpZHRoPTYzIGhlaWdodD0yOT48L3RkPg0KICAgIDx0 ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9lbWFpbC8wNTAxL2lt Zy9jZXN0b2NreV9tYWlsXzI0LmpwZyIgd2lkdGg9MTI4IGhlaWdodD0yOT48L3RkPg0KICAg IDx0ZD48aW1nIHNyYz0iaHR0cDovL3d3dy5tYWlscGFydG5lci5jby5rci9lbWFpbC8wNTAx L2ltZy9jZXN0b2NreV9tYWlsXzI1LmpwZyIgd2lkdGg9NjAgaGVpZ2h0PTI5PjwvdGQ+DQog IDwvdHI+DQo8L3RhYmxlPg0KPHRhYmxlIHdpZHRoPSI2MTEiIGJvcmRlcj0iMCIgY2VsbHNw YWNpbmc9IjAiIGNlbGxwYWRkaW5nPSIwIj4NCiAgPHRyPiANCiAgICA8dGQ+DQogICAgICA8 dGFibGUgd2lkdGg9IjYxMCIgYm9yZGVyPSIwIiBhbGlnbj0iY2VudGVyIj4NCiAgICAgICAg PHRyPiANCiAgICAgICAgICA8dGQgYmdjb2xvcj0iI2U2ZTZlNiIgYWxpZ249ImNlbnRlciI+ PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5cHQ7Ij48YnI+DQogICAgICAgICAgICCxzcfPwMcg vcK29L74wMwgyKu6uLy6IMD8wNogv+zG7cC7ILq4s7uw1CC1yCDBoSDBpMHfyPcgu+ew+iC1 5biztM+02S48YnI+DQogICAgICAgICAgICDBpLq4xeu9xbjBwMy/68PLwfi5/SCx1MGkwLsg wdi89sfPv6kgPGI+PGZvbnQgY29sb3I9IiNGRjAwMDAiPrGksO243sDPPC9mb250PjwvYj7A 08C7IMelvcPHz7+0wLi45ywgDQogICAgICAgICAgICC89r3FsMW6ziDA5cShuKYguLa3w8fP sO0gwNa9wLTPtNkuPGJyPg0KICAgICAgICAgICAgsc3Hz8DHIMD8wNogv+zG7SDB1rzStMIg wM7FzbPdILvzwMcgsPiws7XIIMDlvNK/obytIL3AtebHz7+0wLi45ywgwPrI8bTCILHNx8/A xyDA/MDav+zG7SDB1rzSIL/cPGJyPg0KICAgICAgICAgICAgvu62sMfRILCzwM7BpLq4tbUg sKHB9rDtIMDWwfYgvsrAuLnHt84gvsi9ycfPvcOx4iC52bb4tM+02S48YnI+DQogICAgICAg ICAgICC89r3FwLsgv/jEoSC+ysC4vcO46SA8YSBocmVmPSJtYWlsdG86aHl1bjEwMzEwQGtv cm5ldC5uZXQ/c3ViamVjdD289r3FsMW6ziI+PGZvbnQgY29sb3I9ImJsdWUiPrz2vcWwxbrO PC9mb250PjwvYT64piANCiAgICAgICAgICAgIMWsuK/H2CDB1r3KvcO/5C48L3NwYW4+PGJy Pg0KICAgICAgICAgICAgJm5ic3A7PC90ZD4NCiAgICAgICAgPC90cj4NCiAgICAgIDwvdGFi bGU+DQogICAgPC90ZD4NCiAgPC90cj4NCjwvdGFibGU+DQo8L2JvZHk+DQo8L2h0bWw+DQo= ------=_NextPart_000_0097_01C0F18A.93A56C00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 17:20:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A54A37B400 for ; Mon, 1 Jul 2002 17:20:13 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCD9D43E13 for ; Mon, 1 Jul 2002 17:20:09 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702002009.XGJK6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 00:20:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA93542; Mon, 1 Jul 2002 17:01:31 -0700 (PDT) Date: Mon, 1 Jul 2002 17:01:30 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Daniel Eischen wrote: > > I also made changes to uthread_sigpending.c and uthread_sigsuspend.c > 3 days ago (lib/libc_r/uthread/...). You can try reverting those > changes and go back to revisions 1.18 and 1.11 respectively. It seems that you have been exhonorated.. I guess this means that teh KSE changes are in some way contaminating the build of libc_r.. but what? and how? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 17:35:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8ED837B400; Mon, 1 Jul 2002 17:35:11 -0700 (PDT) Received: from overcee.wemm.org (12-232-114-102.client.attbi.com [12.232.114.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 583BE43E13; Mon, 1 Jul 2002 17:35:11 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id E58DE390F; Mon, 1 Jul 2002 17:35:17 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: julian@freebsd.org Cc: current@freebsd.org Subject: Another post-KSE bug? Date: Mon, 01 Jul 2002 17:35:17 -0700 From: Peter Wemm Message-Id: <20020702003517.E58DE390F@overcee.wemm.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 This is on beast.freebsd.org, running -current as of about 20 minutes ago. I just rm'ed a .o file and did a make: peter@beast[5:32pm]/usr/src/sys/alpha/compile/BEAST-6# rm yarrow.o peter@beast[5:32pm]/usr/src/sys/alpha/compile/BEAST-7# make cc -c -O -pipe -mcpu=ev56 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wno-format -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -D_KERNEL -include opt_global.h -fno-common -mno-fp-regs -ffixed-8 -Wa,-mev56 -ffreestanding ../../../dev/random/yarrow.c ^Z [1] + Suspended make peter@beast[5:33pm]/usr/src/sys/alpha/compile/BEAST-8# fg make [1] 327 Abort trap (core dumped) *** Error code 134 Stop in /usr/src/sys/alpha/compile/BEAST. Since we're all having fun now, I thought I'd mention this one too. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 17:44:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 569B437B400 for ; Mon, 1 Jul 2002 17:44:20 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43EF443E0A for ; Mon, 1 Jul 2002 17:44:19 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g620i6WG001997; Mon, 1 Jul 2002 20:44:06 -0400 (EDT) Date: Mon, 1 Jul 2002 20:44:06 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > > > I also made changes to uthread_sigpending.c and uthread_sigsuspend.c > > 3 days ago (lib/libc_r/uthread/...). You can try reverting those > > changes and go back to revisions 1.18 and 1.11 respectively. > > It seems that you have been exhonorated.. > I guess this means that teh KSE changes are in some way contaminating the > build of libc_r.. but what? and how? I'm not sure. I would be interested in seeing any warnings from building new libc_r. The only places I can think of are the queues (with the QMD debug defined, that would definitely cause problems), but that seems to have been ruled out also when queue.h was reverted. Did USRSTACK or SIGSTKSZ get changed somehow? Someone can also try going into lib/libc_r/test and running the tests in there, to see if even simple threaded programs are borken or not. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 18: 0:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4627637B401 for ; Mon, 1 Jul 2002 18:00:24 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E44643E26 for ; Mon, 1 Jul 2002 18:00:23 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702010022.GHXK29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 01:00:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA93727; Mon, 1 Jul 2002 17:52:01 -0700 (PDT) Date: Mon, 1 Jul 2002 17:52:01 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Daniel Eischen wrote: > I'm not sure. I would be interested in seeing any warnings from building > new libc_r. The only places I can think of are the queues (with the > QMD debug defined, that would definitely cause problems), but that > seems to have been ruled out also when queue.h was reverted. Did > USRSTACK or SIGSTKSZ get changed somehow? > > Someone can also try going into lib/libc_r/test and running the > tests in there, to see if even simple threaded programs are borken > or not. I'd try but... cc -Wall -pipe -g3 -D_LIBC_R_ -D_REENTRANT -c mutex_d.c -o mutex_d_a.o mutex_d.c:168: initializer element is not constant mutex_d.c: In function `waiter': mutex_d.c:358: warning: too few arguments for format *** Error code 1 Stop in /usr/src/lib/libc_r/test. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 18: 0:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D45E937B400; Mon, 1 Jul 2002 18:00:21 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576DC43E13; Mon, 1 Jul 2002 18:00:20 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702010019.GHWG29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 01:00:19 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA93719; Mon, 1 Jul 2002 17:47:58 -0700 (PDT) Date: Mon, 1 Jul 2002 17:47:57 -0700 (PDT) From: Julian Elischer To: Peter Wemm Cc: julian@freebsd.org, current@freebsd.org Subject: Re: Another post-KSE bug? In-Reply-To: <20020702003517.E58DE390F@overcee.wemm.org> 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 I have seen this an dhoped that fixing some of the less scary ones would fix it too.. ^Z seems to occasionally kill the (or one of) process instead. I have not figured it out.. Peter, did you see the mail I forwarded to you regarding the condvar/msleep race? I was hoping for a second opinion.. (and since I can't comit for a couple more hours....) On Mon, 1 Jul 2002, Peter Wemm wrote: > This is on beast.freebsd.org, running -current as of about 20 minutes > ago. I just rm'ed a .o file and did a make: > > peter@beast[5:32pm]/usr/src/sys/alpha/compile/BEAST-6# rm yarrow.o > peter@beast[5:32pm]/usr/src/sys/alpha/compile/BEAST-7# make > cc -c -O -pipe -mcpu=ev56 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wno-format -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -D_KERNEL -include opt_global.h -fno-common -mno-fp-regs -ffixed-8 -Wa,-mev56 -ffreestanding ../../../dev/random/yarrow.c > ^Z > [1] + Suspended make > peter@beast[5:33pm]/usr/src/sys/alpha/compile/BEAST-8# fg > make > [1] 327 Abort trap (core dumped) > *** Error code 134 > > Stop in /usr/src/sys/alpha/compile/BEAST. > > Since we're all having fun now, I thought I'd mention this one too. > > Cheers, > -Peter > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 18:18:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E30A37B400 for ; Mon, 1 Jul 2002 18:18:14 -0700 (PDT) Received: from white.imgsrc.co.jp (ns.imgsrc.co.jp [210.226.20.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2755F43E13 for ; Mon, 1 Jul 2002 18:18:14 -0700 (PDT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by white.imgsrc.co.jp (Postfix) with ESMTP id 4CEBE24D1C for ; Tue, 2 Jul 2002 10:18:13 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by white.imgsrc.co.jp (Postfix) with ESMTP id 9218824D06 for ; Tue, 2 Jul 2002 10:18:09 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [2001:218:422:2::130]) by black.imgsrc.co.jp (Postfix) with ESMTP id 379C71E46E4 for ; Tue, 2 Jul 2002 10:18:08 +0900 (JST) Date: Tue, 02 Jul 2002 10:18:08 +0900 Message-ID: <7mit3zc4hb.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: ATAPI_SET_SPEED on Panasonic LF-D321 User-Agent: Wanderlust/2.9.10 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS on ns.imgsrc.co.jp 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 got this drive ("LF-D321" is printed in front of drive), but burncd cannot set speed. > acd1: DVD-R at ata1-slave PIO4 % sudo burncd -f /dev/acd1c data release.iso burncd: ioctl(CDRIOCWRITESPEED): Input/output error Dmesg shows: > acd1: SET_SPEED - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x00 Cannot this drive accept ATAPI_SET_SPEED atapi command? -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 18:20:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9353A37B400 for ; Mon, 1 Jul 2002 18:20:15 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id E12D743E09 for ; Mon, 1 Jul 2002 18:20:11 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702012011.YYVM6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 01:20:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA93852; Mon, 1 Jul 2002 18:10:57 -0700 (PDT) Date: Mon, 1 Jul 2002 18:10:57 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 turned out to be minor.. see other mail On Mon, 1 Jul 2002, Julian Elischer wrote: > > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > I'm not sure. I would be interested in seeing any warnings from building > > new libc_r. The only places I can think of are the queues (with the > > QMD debug defined, that would definitely cause problems), but that > > seems to have been ruled out also when queue.h was reverted. Did > > USRSTACK or SIGSTKSZ get changed somehow? > > > > Someone can also try going into lib/libc_r/test and running the > > tests in there, to see if even simple threaded programs are borken > > or not. > > I'd try but... > cc -Wall -pipe -g3 -D_LIBC_R_ -D_REENTRANT -c mutex_d.c -o mutex_d_a.o > mutex_d.c:168: initializer element is not constant > mutex_d.c: In function `waiter': > mutex_d.c:358: warning: too few arguments for format > *** Error code 1 > > Stop in /usr/src/lib/libc_r/test. > > > > 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 Jul 1 18:20:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 213B537B401 for ; Mon, 1 Jul 2002 18:20:23 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8CB43E13 for ; Mon, 1 Jul 2002 18:20:22 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702012021.YYZB6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 01:20:21 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA93850; Mon, 1 Jul 2002 18:10:13 -0700 (PDT) Date: Mon, 1 Jul 2002 18:10:12 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Daniel Eischen wrote: > > Someone can also try going into lib/libc_r/test and running the > tests in there, to see if even simple threaded programs are borken > or not. A cool I didn't know they are there! heres what happens when it is run (After fixing typos) make: don't know how to make test. Stop ref4# make Test static library: -------------------------------------------------------------------------- Test c_user c_system c_total chng passed/FAILED h_user h_system h_total % chng -------------------------------------------------------------------------- hello_d 0.00 0.00 0.00 passed -------------------------------------------------------------------------- hello_s 0.00 0.01 0.01 passed -------------------------------------------------------------------------- join_leak_d 0.19 0.15 0.34 passed -------------------------------------------------------------------------- mutex_d (**hangs here**) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 18:24:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30B1E37B400 for ; Mon, 1 Jul 2002 18:24:51 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3AE343E09 for ; Mon, 1 Jul 2002 18:24:50 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g621ObJn006805; Mon, 1 Jul 2002 21:24:37 -0400 (EDT) Date: Mon, 1 Jul 2002 21:24:37 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > > > Someone can also try going into lib/libc_r/test and running the > > tests in there, to see if even simple threaded programs are borken > > or not. > A > cool > I didn't know they are there! > > > heres what happens when it is run (After fixing typos) > > > make: don't know how to make test. Stop > ref4# make > Test static library: > -------------------------------------------------------------------------- > Test c_user c_system c_total chng > passed/FAILED h_user h_system h_total % chng > -------------------------------------------------------------------------- > hello_d 0.00 0.00 0.00 > passed > -------------------------------------------------------------------------- > hello_s 0.00 0.01 0.01 > passed > -------------------------------------------------------------------------- > join_leak_d 0.19 0.15 0.34 > passed > -------------------------------------------------------------------------- > mutex_d (**hangs here**) This one takes quite a long time to run. Run it by hand and you'll see if it's really hanging or not. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 19: 0:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C91FB37B401 for ; Mon, 1 Jul 2002 19:00:12 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40A1743E09 for ; Mon, 1 Jul 2002 19:00:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702020011.ICMF29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 02:00:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA94003; Mon, 1 Jul 2002 18:45:55 -0700 (PDT) Date: Mon, 1 Jul 2002 18:45:55 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > mutex_d (**hangs here**) > > This one takes quite a long time to run. Run it by hand and you'll > see if it's really hanging or not. you're not wrong! it takes ages.. (still running in another window) false alarm so far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 19:12:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A3337B400 for ; Mon, 1 Jul 2002 19:12:15 -0700 (PDT) Received: from boggy.acest.tutrp.tut.ac.jp (boggy.acest.tutrp.tut.ac.jp [133.15.67.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id BED5F43E09 for ; Mon, 1 Jul 2002 19:12:14 -0700 (PDT) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: from boggy.acest.tutrp.tut.ac.jp (localhost [127.0.0.1]) by boggy.acest.tutrp.tut.ac.jp (8.12.5/8.12.5) with ESMTP id g622CDNL094198; Tue, 2 Jul 2002 11:12:13 +0900 (JST) (envelope-from nakaji@boggy.acest.tutrp.tut.ac.jp) Received: (from nakaji@localhost) by boggy.acest.tutrp.tut.ac.jp (8.12.5/8.12.5/Submit) id g622CCCN094159; Tue, 2 Jul 2002 11:12:12 +0900 (JST) To: freebsd-current@FreeBSD.ORG Cc: Julian Elischer Subject: Re: Post-KSE disaster with libc_r References: <87bs9rzpa8.fsf@boggy.acest.tutrp.tut.ac.jp> MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII From: NAKAJI Hiroyuki Date: Tue, 02 Jul 2002 11:12:12 +0900 In-Reply-To: (Julian Elischer's message of "Mon, 1 Jul 2002 10:26:22 -0700 (PDT)") Message-ID: <87znxayj2b.fsf@boggy.acest.tutrp.tut.ac.jp> Lines: 18 User-Agent: T-gnus/6.15.6 (based on Oort Gnus v0.06) (revision 02) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) 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 >>>>> Julian Elischer wrote: JE> the question is: JE> did you update both kernel and userland? Yes. I always do update the whole world. > I updated my current box about an hour ago, and got into trouble too. And I backed kernel only of date=2002.06.29.17.00.00 and this old kernel has problem. While running /etc/rc it gets panic, but I've lost the message. I'm now rebuilding the latest world, i.e. userland and kernel, with the kernel and userland of yesterday. -- NAKAJI Hiroyuki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 19:20:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 509AB37B400 for ; Mon, 1 Jul 2002 19:20:11 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D69ED43E09 for ; Mon, 1 Jul 2002 19:20:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702022010.OZFJ8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 02:20:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA94114; Mon, 1 Jul 2002 19:15:03 -0700 (PDT) Date: Mon, 1 Jul 2002 19:15:02 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 I think that gets us a LOT closer! Total tests 212, passed 212, failed 0 ref4# Jul 2 01:52:52 ref4 kernel: pid 330 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:52 ref4 kernel: pid 334 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:52 ref4 kernel: pid 338 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:52 ref4 kernel: pid 342 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:52 ref4 kernel: pid 346 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:52 ref4 kernel: pid 350 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 354 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 358 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 362 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 366 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 370 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 374 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 378 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:53 ref4 kernel: pid 382 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:54 ref4 kernel: pid 386 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:54 ref4 kernel: pid 390 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:54 ref4 kernel: pid 394 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:54 ref4 kernel: pid 398 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:54 ref4 kernel: pid 402 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 406 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 410 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 414 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 418 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 422 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 426 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 430 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:55 ref4 kernel: pid 434 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:56 ref4 kernel: pid 438 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:56 ref4 kernel: pid 442 (guard_b), uid 0: exited on signal 11 (core dumped) Jul 2 01:52:56 ref4 kernel: pid 446 (guard_b), uid 0: exited on signal 11 (core dumped) -------------------------------------------------------------------------- sigsuspend_d 0.00 0.01 0.01 passed -------------------------------------------------------------------------- sigwait_d 0.00 0.01 0.01 *** FAILED *** -------------------------------------------------------------------------- guard_s.pl 0.06 0.88 0.95 *** FAILED *** (30/30 failed) -------------------------------------------------------------------------- propagate_s.pl 0.14 0.07 0.21 *** FAILED *** (1/1 failed) -------------------------------------------------------------------------- Totals 3.34 151.65 154.99 0.00 6 / 9 passed (66.67%) 0.00 0.00 0.00 0.00% -------------------------------------------------------------------------- *** Error code 1 Stop in /usr/src/lib/libc_r/test. in gdb: Breakpoint 1, main (argc=3, argv=0xbfbffc10) at guard_b.c:103 103 assert(pthread_attr_init(&attr) == 0); (gdb) s 98 fprintf(stderr, "Test begin\n"); (gdb) Test begin 100 stacksize = strtoul(argv[1], NULL, 10); (gdb) 101 guardsize = strtoul(argv[2], NULL, 10); (gdb) 103 assert(pthread_attr_init(&attr) == 0); (gdb) 108 assert(pthread_attr_getstacksize(&attr, &def_stacksize) == 0); (gdb) 109 assert(pthread_attr_getguardsize(&attr, &def_guardsize) == 0); (gdb) 110 if (def_stacksize != stacksize) { (gdb) 111 assert(pthread_attr_setstacksize(&attr, stacksize) == 0); (gdb) 112 assert(pthread_attr_getstacksize(&attr, &def_stacksize) == 0); (gdb) 113 assert(def_stacksize == stacksize); (gdb) 115 if (def_guardsize != guardsize) { (gdb) 116 assert(pthread_attr_setguardsize(&attr, guardsize) == 0); (gdb) 117 assert(pthread_attr_getguardsize(&attr, &def_guardsize) == 0); (gdb) 118 assert(def_guardsize >= guardsize); (gdb) 127 args.top = NULL; (gdb) 128 args.cur = 0; (gdb) 129 args.max = (stacksize / FRAME_SIZE) - 1; (gdb) 130 fprintf(stderr, "No overflow:\n"); (gdb) No overflow: 131 assert(pthread_create(&thread, &attr, recurse, &args) == 0); (gdb) warning: Cannot insert breakpoint 0: Error accessing memory address 0xd0d0d0d0: Bad address. (gdb) bt #0 0x0804b820 in _thread_kern_scheduler () #1 0x0804f9eb in _write () #2 0x08059cd1 in __swrite () #3 0x08059ddc in _swrite () #4 0x0805964b in __sflush () #5 0x080595e1 in __fflush () #6 0x08053394 in snprintf () #7 0x08053767 in __vfprintf () #8 0x08075080 in ?? () (gdb) hmmm recompile with -g and statically link with -g'd libc_r.... try again.. get to: at /usr/src/lib/libc_r/uthread/uthread_mutex.c:498 498 if (((*mutex)->m_flags & MUTEX_FLAGS_INITED) == 0) { (gdb) 505 switch ((*mutex)->m_protocol) { (gdb) 508 if ((*mutex)->m_owner == NULL) { (gdb) 510 (*mutex)->m_owner = curthread; (gdb) 513 _MUTEX_ASSERT_NOT_OWNED(*mutex); (gdb) 632 (*mutex), m_qe); (gdb) 682 if (curthread->interrupted != 0) (gdb) 686 _SPINUNLOCK(&(*mutex)->lock); (gdb) 692 _thread_kern_sig_undefer(); (gdb) _thread_kern_sig_undefer () at /usr/src/lib/libc_r/uthread/uthread_kern.c:1042 1042 struct pthread *curthread = _get_curthread(); (gdb) _get_curthread () at /usr/src/lib/libc_r/uthread/uthread_kern.c:1129 1129 if (_thread_initial == NULL) (gdb) 1132 return (_thread_run); (gdb) 1133 } (gdb) _thread_kern_sig_undefer () at /usr/src/lib/libc_r/uthread/uthread_kern.c:1048 1048 if (curthread->sig_defer_count > 1) { (gdb) 1052 else if (curthread->sig_defer_count == 1) { (gdb) 1054 curthread->sig_defer_count = 0; (gdb) 1059 if (_sigq_check_reqd != 0) (gdb) 1066 if (((curthread->cancelflags & PTHREAD_AT_CANCEL_POINT) == 0) && (gdb) 1076 if ((curthread->yield_on_sig_undefer != 0) || (gdb) 168 { (gdb) 171 for (i = 0; i < _SIG_WORDS; i++) { (gdb) 172 if (set->__bits[i]) (gdb) 171 for (i = 0; i < _SIG_WORDS; i++) { (gdb) 172 if (set->__bits[i]) (gdb) 171 for (i = 0; i < _SIG_WORDS; i++) { (gdb) 172 if (set->__bits[i]) (gdb) 171 for (i = 0; i < _SIG_WORDS; i++) { (gdb) 172 if (set->__bits[i]) (gdb) 171 for (i = 0; i < _SIG_WORDS; i++) { (gdb) 174 } (gdb) 168 { (gdb) 1082 } (gdb) mutex_lock_common (mutex=0x8060c74) at /usr/src/lib/libc_r/uthread/uthread_mutex.c:693 693 } while (((*mutex)->m_owner != curthread) && (ret == 0) && (gdb) 696 if (curthread->interrupted != 0 && (gdb) 702 } (gdb) __pthread_mutex_lock (mutex=0x8060c74) at /usr/src/lib/libc_r/uthread/uthread_mutex.c:723 723 } (gdb) hangs.. on console: lock order reversal 1st 0xc03585e0 sched lock (sched lock) @ ../../../kern/subr_trap.c:82 2nd 0xc03c2d80 sio (sio) @ ../../../dev/sio/sio.c:3198 failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() probably due to debugging.. will try again with a breakpoint.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 20:14:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED37337B400 for ; Mon, 1 Jul 2002 20:14:51 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81F0F43E09 for ; Mon, 1 Jul 2002 20:14:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g623EkT4038020; Mon, 1 Jul 2002 20:14:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g623Eke5038019; Mon, 1 Jul 2002 20:14:46 -0700 (PDT) (envelope-from dillon) Date: Mon, 1 Jul 2002 20:14:46 -0700 (PDT) From: Matthew Dillon Message-Id: <200207020314.g623Eke5038019@apollo.backplane.com> To: Julian Elischer , "Long, Scott" , FreeBSD current users Subject: -current results (was something funny with soft updates?) References: 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 SMP builds are still producing panics every 2-4 buildworlds after the KSE commit, I'm still trying to track that down. But I was able to complete the softupdates/non-softupdates test with a UP build of -current: with softupdates (UP BUILD, CURRENT): 3122.30 real 2360.70 user 532.54 sys 3083.17 real 2361.14 user 529.53 sys 3085.05 real 2361.59 user 529.32 sys without softupdates (UP BUILD, CURRENT): 3361.70 real 2365.23 user 535.50 sys 3451.55 real 2368.22 user 537.26 sys 3454.85 real 2369.42 user 536.69 sys ^^^^^ ~350 second dif note user times for real. Included below are the original tests that were done under stable... the overall 'real' times are NOT COMPARATIVE since the original tests were done with an SMP build, but the user times should be, and that is where I believe the major difference is occuring. My guess is that the new GCC in -current is eating a massive amount of extra cpu. It is eating over 2300 cpu seconds under -current and only 1400 under -stable while system time remains roughly comparable (remember that the interrupts are not charged to processes under -current). The difference in real time softupdate vs non-softupdates between current and stable is around 350 seconds under current, and 889 seconds under stable. This is fairly comparable when we consider that a good portion of the extra user time eaten in -current is absorbing the stall delays for processes undergoing I/O that softupdates mostly fixes. My conclusion is that softupdates is working fine and (A) the new GCC is a whole lot less efficient then the old GCC and (B) user times are masking gains (due to high parallelism) that would otherwise be realized with softupdates. : (original tests under -stable) :test1# cat x1 (SMP BUILD, STABLE, WITH SOFTUPDATES) : 1497.09 real 1397.98 user 612.06 sys : 1500.12 real 1399.33 user 609.79 sys : 1494.82 real 1398.30 user 612.46 sys :test1# cat x2 (SMP BUILD, STABLE, WITHOUT SOFTUPDATES) : 2449.14 real 1401.34 user 625.54 sys : 2389.75 real 1400.38 user 629.86 sys : 2358.82 real 1403.26 user 624.93 sys : ( ~889 second difference in real time) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 20:18:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD86237B400 for ; Mon, 1 Jul 2002 20:18:20 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4822143E0A for ; Mon, 1 Jul 2002 20:18:20 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g623I9LQ018262; Mon, 1 Jul 2002 23:18:09 -0400 (EDT) Date: Mon, 1 Jul 2002 23:18:09 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > I think that gets us a LOT closer! > > > Total tests 212, passed 212, failed 0 > ref4# Jul 2 01:52:52 ref4 kernel: pid 330 (guard_b), uid 0: exited on > signal 11 (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 338 (guard_b), uid 0: exited on signal 11 > (core dumped) I think this is supposed to SEGV. It's testing guard pages placed above thread stacks. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 23:40:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92E1D37B400 for ; Mon, 1 Jul 2002 23:40:08 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4116843E0A for ; Mon, 1 Jul 2002 23:40:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702064007.VNRO8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 06:40:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA94948; Mon, 1 Jul 2002 23:21:32 -0700 (PDT) Date: Mon, 1 Jul 2002 23:21:31 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Daniel Eischen wrote: > On Mon, 1 Jul 2002, Julian Elischer wrote: > > > I think that gets us a LOT closer! > > > > > > Total tests 212, passed 212, failed 0 > > ref4# Jul 2 01:52:52 ref4 kernel: pid 330 (guard_b), uid 0: exited on > > signal 11 (core dumped) > > Jul 2 01:52:52 ref4 kernel: pid 338 (guard_b), uid 0: exited on signal 11 > > (core dumped) > > I think this is supposed to SEGV. It's testing guard pages placed > above thread stacks. I would imagine that it is supposed to capture the sigsegv instead of actually dying... > > -- > Dan Eischen > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 1 23:46:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 012F637B400 for ; Mon, 1 Jul 2002 23:46:18 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7571A43E09 for ; Mon, 1 Jul 2002 23:46:17 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g626k8bv009067; Tue, 2 Jul 2002 02:46:08 -0400 (EDT) Date: Tue, 2 Jul 2002 02:46:08 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: "Andrey A. Chernov" , NAKAJI Hiroyuki , freebsd-current@FreeBSD.ORG Subject: Re: Post-KSE disaster with libc_r In-Reply-To: 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 On Mon, 1 Jul 2002, Julian Elischer wrote: > > On Mon, 1 Jul 2002, Daniel Eischen wrote: > > > On Mon, 1 Jul 2002, Julian Elischer wrote: > > > > > I think that gets us a LOT closer! > > > > > > > > > Total tests 212, passed 212, failed 0 > > > ref4# Jul 2 01:52:52 ref4 kernel: pid 330 (guard_b), uid 0: exited on > > > signal 11 (core dumped) > > > Jul 2 01:52:52 ref4 kernel: pid 338 (guard_b), uid 0: exited on signal 11 > > > (core dumped) > > > > I think this is supposed to SEGV. It's testing guard pages placed > > above thread stacks. > > I would imagine that it is supposed to capture the sigsegv > instead of actually dying... There's a perl script which is supposed to do that I think. guard_s.pl I think. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 1:29:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F074A37B400; Tue, 2 Jul 2002 01:29:16 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEEF843E0A; Tue, 2 Jul 2002 01:29:15 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 SAA10417; Tue, 2 Jul 2002 18:29:12 +1000 Date: Tue, 2 Jul 2002 18:35:01 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Christian Weisgerber Cc: freebsd-current@FreeBSD.ORG Subject: Re: LP64: (int)signal() In-Reply-To: Message-ID: <20020702182320.X11383-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, 1 Jul 2002, Christian Weisgerber wrote: > I would like to clean up the last instances of (int)signal(...) in > the tree. Any objection to the changes below? No, but ... > Other occurrences not worth touching: > - contrib/opie/opieftpd.c: contrib, not used > - libexec/bootpd/bootpd.c: #ifdef'ed out in favor of sigaction(). ... either the sigaction() or the signal() in bootpd.c is probably wrong, since the sigaction() is missing SA_RESTART. The signal() case has been ifdefed out for a long time, so this apparently doesn't matter much. This has very little to do with LP64 ... Mike Barcroft wrote: > You might want to get rid of the other misuse of `rc' above this and > just remove the variable. The use of an gratuitous int variable rc to capture return values is rampant throughout this code. In fact, not using it is something of a violation of the local style, but in the case of signal() I think it's justifiable because SIG_ERR is so much neater than changing rc to long and messing around with explicit casts. Casting signal() to long just gives undefined behaviour on different machines. It would be less incorrect to cast a magic integer to a function pointer like the implementation must do to create SIG_ERR (at least if the implementation starts with a magic integer), but it is so much neater to just use SIG_ERR. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 1:44: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94C8B37B400 for ; Tue, 2 Jul 2002 01:44:02 -0700 (PDT) Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C914643E0A for ; Tue, 2 Jul 2002 01:43:58 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.56.224.151]) by e1.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g628hvg5172122 for ; Tue, 2 Jul 2002 04:43:57 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by northrelay03.pok.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g628htn78594 for ; Tue, 2 Jul 2002 04:43:56 -0400 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id A26D03130; Tue, 2 Jul 2002 14:13:12 +0530 (IST) Date: Tue, 2 Jul 2002 14:13:12 +0530 From: Sid Carter To: current@freebsd.org Subject: Core Dumps et al on -current Message-ID: <20020702084312.GA89077@calvin.in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: uname -rsp Organisation: Sid Carter Inc. User-Agent: Mutt/1.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, Some of my applications are failing to start on my recently compiled kernel and world. These are the errors I get: ------------------------------------------------ pid 944 (xlock), uid 1001: exited on signal 11 pid 998 (superquadrics), uid 1001: exited on signal 11 (core dumped) pid 1253 (sproingies), uid 1001: exited on signal 11 (core dumped) pid 1429 (bubble3d), uid 1001: exited on signal 11 (core dumped) pid 1470 (pulsar), uid 1001: exited on signal 11 (core dumped) pid 1940 (cage), uid 1001: exited on signal 11 (core dumped) pid 1954 (interference), uid 1001: exited on signal 11 (core dumped) pid 2024 (moebius), uid 1001: exited on signal 11 (core dumped) pid 2180 (rubik), uid 1001: exited on signal 11 (core dumped) pid 2234 (gltext), uid 1001: exited on signal 11 (core dumped) pid 2537 (gltext), uid 1001: exited on signal 11 (core dumped) pid 2600 (boxed), uid 1001: exited on signal 11 (core dumped) pid 2676 (sproingies), uid 1001: exited on signal 11 (core dumped) pid 2684 (stonerview), uid 1001: exited on signal 11 (core dumped) pid 2706 (dangerball), uid 1001: exited on signal 11 (core dumped) pid 2795 (stonerview), uid 1001: exited on signal 11 (core dumped) pid 2825 (gflux), uid 1001: exited on signal 11 (core dumped) pid 2859 (pulsar), uid 1001: exited on signal 11 (core dumped) pid 2971 (sierpinski3d), uid 1001: exited on signal 11 (core dumped) pid 88896 (bubble3d), uid 1001: exited on signal 11 (core dumped) pid 88924 (stonerview), uid 1001: exited on signal 11 (core dumped) /usr/src/sys/vm/uma_core.c:1333: could sleep with "inp" locked from /usr/src/sys/netinet/tcp_usrreq.c:1013 pid 89065 (mozilla-bin), uid 1001: exited on signal 11 (core dumped) ------------------------------------------------ I have compiled my kernel without "INET6" and related drivers. uname -a -------- FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jul 1 21:37:15 IST 2002 root@calvin:/usr/obj/usr/src/sys/GENERIC i386 Anything obvious I missed ? Thanks in advance Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 1:49:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A250537B400 for ; Tue, 2 Jul 2002 01:49:47 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6F2D43E09 for ; Tue, 2 Jul 2002 01:49:45 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17PJMx-000Nuc-00; Tue, 02 Jul 2002 10:50:43 +0200 Date: Tue, 2 Jul 2002 10:50:43 +0200 From: Sheldon Hearn To: Sid Carter Cc: current@freebsd.org Subject: Re: Core Dumps et al on -current Message-ID: <20020702085043.GI90729@starjuice.net> Mail-Followup-To: Sid Carter , current@freebsd.org References: <20020702084312.GA89077@calvin.in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020702084312.GA89077@calvin.in.ibm.com> User-Agent: Mutt/1.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 On (2002/07/02 14:13), Sid Carter wrote: > Anything obvious I missed ? Yes. You haven't been reading your mail. :-) There's known instability at present, that is believed to relate to changes made to libc_r in the last month, or to the recent KSE update and its impact on libc_r. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 1:58:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D6837B400 for ; Tue, 2 Jul 2002 01:58:48 -0700 (PDT) Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8992E43E13 for ; Tue, 2 Jul 2002 01:58:47 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24]) by e31.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id g628wjuJ016392; Tue, 2 Jul 2002 04:58:46 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by westrelay03.boulder.ibm.com (8.11.1m3/NCO/VER6.2) with ESMTP id g628wgJ58338; Tue, 2 Jul 2002 02:58:43 -0600 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id 11CD83130; Tue, 2 Jul 2002 14:27:58 +0530 (IST) Date: Tue, 2 Jul 2002 14:27:57 +0530 From: Sid Carter To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: Core Dumps et al on -current Message-ID: <20020702085757.GA94318@calvin.in.ibm.com> References: <20020702084312.GA89077@calvin.in.ibm.com> <20020702085043.GI90729@starjuice.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020702085043.GI90729@starjuice.net> X-Operating-System: uname -rsp Organisation: Sid Carter Inc. User-Agent: Mutt/1.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 An Tue, Jul 02, 2002 at 10:50:43AM +0200, Sheldon Hearn schreib : > On (2002/07/02 14:13), Sid Carter wrote: > > > Anything obvious I missed ? > > Yes. You haven't been reading your mail. :-) > > There's known instability at present, that is believed to relate to > changes made to libc_r in the last month, or to the recent KSE update > and its impact on libc_r. Hi, Yeah, I have been reading my mail. Oh well..... No Wonder all that mail w.r.t KSE, just did not think that these both were related. Ok....in which case I wait for all that is happening....no wonder....even gnome2 refuses to start ;) Thanks Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 2: 0:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C784B37B400 for ; Tue, 2 Jul 2002 02:00:15 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1743F43E09 for ; Tue, 2 Jul 2002 02:00:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702090014.GAVQ903.sccrmhc03.attbi.com@InterJet.elischer.org> for ; Tue, 2 Jul 2002 09:00:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id BAA95530 for ; Tue, 2 Jul 2002 01:57:40 -0700 (PDT) Date: Tue, 2 Jul 2002 01:57:39 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: KSE status report 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 Ok so Usability for the average command line user is very good. David Xu tracked down a problem that was eluding me with SMP machines. Matt is tracking down something that may be giving some instability but may also be related to what David found. He however gets the award for most confusing debug messages when he managed to get both of his CPUs to enter teh debugger at the same time. I thought that was impossible, but it definitly happenned. (or it certainly looked that way to me :-) The big problem at the moment is that something in the source tree as a whole, and probably something that came in with KSE is stopping us from successfully compiling a working libc_r. (a bit ironic really). A libc_r imported from a system that is not yet upgraded to have KSE sources works fine. A libc_r from a KSE machine will not work correctly on the KSE machine or the pre-KSE machine. The sources are identical, so some thing else in the tree must be influencing its correctness. the result of this problem is that KDE and Gnome apps that are linked with a libc_r created on this system. The test directory in the libc sources is giving me some avenues to work on but I must say, given allthe things that could have gone wrong in the kernel, I'm surprised that the largest problem seems to have come from a userland library that I haven't touched :-/ julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 2: 3:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5731237B400 for ; Tue, 2 Jul 2002 02:03:44 -0700 (PDT) Received: from sdns.kv.ukrtel.net (sdns.kv.ukrtel.net [195.5.27.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CC1843E09 for ; Tue, 2 Jul 2002 02:03:43 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (195.5.51.243 [195.5.51.243]) by sdns.kv.ukrtel.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id NTMMS1WA; Tue, 2 Jul 2002 12:05:54 +0300 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id g6293es06205; Tue, 2 Jul 2002 12:03:40 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3D216CAE.46596D21@FreeBSD.org> Date: Tue, 02 Jul 2002 12:04:46 +0300 From: Maxim Sobolev Reply-To: vegacap@i.com.ua Organization: Vega International Capital X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: "George V. Neville-Neil" Cc: freebsd-current@freebsd.org Subject: Re: picobsd redux References: <200207012155.g61Lt3pb037741@mail.meer.net> Content-Type: text/plain; charset=koi8-r 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 Is there any particular reason for using -current for that? The problem is that -current is in horrible state now (gcc 3.1, KSE-III and so on), so that I'd suggest to use -stable branch or -current sources just before gcc 3.1 import. -Maxim "George V. Neville-Neil" wrote: > > Hey Folks, > > So now I'm working somewhere that we're trying to use Picobsd on the > Soekris boards (www.soekris.com). Right now there is a build problem I'm > trying to > solve. When picobsd goes to build the libraries etc. it chokes on the csu > stuff: > > CC="cc" MKDEP_CPP_OPTS="-M -DCRT_BEGIN" mkdep -f .depend -a -nostdinc > -I/sandb > oxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_FRAME_HDR > -I/sandboxes > /gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/config > -I/sandboxes/gnn/FreeBS > D/src/gnu/lib/csu/../../../contrib/gcc -I. -I/sandboxes/gnn/FreeBSD/src/gnu/lib > / > csu/../../usr.bin/cc/cc_tools /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../ > c > ontrib/gcc/crtstuff.c > cc -nostdinc -I/sandboxes/gnn/FreeBSD/src/../usr/include -DIN_GCC > -DHAVE_LD_EH_ > FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions > -fno-o > mit-frame-pointer -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc > / > config -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc -I. > -I/san > dboxes/gnn/FreeBSD/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN > - > c -o crtbegin.o /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crt > s > tuff.c > In file included from /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/g > c > c/crtstuff.c:63: > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37 > : > field `array' has incomplete type > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:13 > 5 > : field `augmentation' has incomplete type > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:14 > 3 > : field `pc_begin' has incomplete type > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: > warn > ing: `used' attribute directive ignored > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In > funct > ion `__do_global_dtors_aux': > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: > synt > ax error before `completed' > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: > `com > pleted' undeclared (first use in this function) > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: > (Eac > h undeclared identifier is reported only once > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for > each function it appears in.) > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top > l > evel: > /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: > warn > ing: `used' attribute directive ignored > *** Error code 1 > > Any pointers would be great, I need to get this stuff back up to snuff fast. > > Thanks, > George > > -- > George V. Neville-Neil gnn@neville-neil.com > Neville-Neil Consulting www.neville-neil.com > > "I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan > > -- > George V. Neville-Neil gnn@neville-neil.com > Neville-Neil Consulting www.neville-neil.com > > "I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan > > 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 Tue Jul 2 2:20:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B11C37B400 for ; Tue, 2 Jul 2002 02:20:09 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id B915343E0A for ; Tue, 2 Jul 2002 02:20:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702092008.IJNN6023.sccrmhc02.attbi.com@InterJet.elischer.org> for ; Tue, 2 Jul 2002 09:20:08 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA95613 for ; Tue, 2 Jul 2002 02:10:10 -0700 (PDT) Date: Tue, 2 Jul 2002 02:10:09 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: Re: KSE status report In-Reply-To: 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 On Tue, 2 Jul 2002, Julian Elischer wrote: > > Ok so Usability for the average command line user is > very good. David Xu tracked down a problem that was > eluding me with SMP machines. Matt is tracking down > something that may be giving some instability > but may also be related to what David found. > He however gets the award for most confusing > debug messages when he managed to get both of his CPUs > to enter teh debugger at the same time. I thought that was > impossible, but it definitly happenned. (or it certainly > looked that way to me :-) > > The big problem at the moment is that something in the > source tree as a whole, and probably something that came in with KSE > is stopping us from successfully compiling a working libc_r. > (a bit ironic really). > > A libc_r imported from a system that is not yet upgraded to have > KSE sources works fine. A libc_r from a KSE machine > will not work correctly on the KSE machine or the pre-KSE machine. > > The sources are identical, so some thing else in the tree must be > influencing its correctness. > > the result of this problem is that KDE and Gnome apps that > are linked with a libc_r created on this system. don't work.... > > The test directory in the libc sources is giving me some avenues to > work on but I must say, given allthe things that could have gone wrong > in the kernel, I'm surprised that the largest problem seems to > have come from a userland library that I haven't touched :-/ > > julian > > > > 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 Tue Jul 2 2:20:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4827737B405 for ; Tue, 2 Jul 2002 02:20:14 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E09143E0A for ; Tue, 2 Jul 2002 02:20:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702092009.IJNV6023.sccrmhc02.attbi.com@InterJet.elischer.org> for ; Tue, 2 Jul 2002 09:20:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA95597 for ; Tue, 2 Jul 2002 02:07:07 -0700 (PDT) Date: Tue, 2 Jul 2002 02:07:07 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: Re: KSE status report In-Reply-To: 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 BTW feel free to spend some time helping try figire out why libc_r is bombing out. It's not an exclusive club :-) On Tue, 2 Jul 2002, Julian Elischer wrote: > > Ok so Usability for the average command line user is > very good. David Xu tracked down a problem that was > eluding me with SMP machines. Matt is tracking down > something that may be giving some instability > but may also be related to what David found. > He however gets the award for most confusing > debug messages when he managed to get both of his CPUs > to enter teh debugger at the same time. I thought that was > impossible, but it definitly happenned. (or it certainly > looked that way to me :-) > > The big problem at the moment is that something in the > source tree as a whole, and probably something that came in with KSE > is stopping us from successfully compiling a working libc_r. > (a bit ironic really). > > A libc_r imported from a system that is not yet upgraded to have > KSE sources works fine. A libc_r from a KSE machine > will not work correctly on the KSE machine or the pre-KSE machine. > > The sources are identical, so some thing else in the tree must be > influencing its correctness. > > the result of this problem is that KDE and Gnome apps that > are linked with a libc_r created on this system. > > The test directory in the libc sources is giving me some avenues to > work on but I must say, given allthe things that could have gone wrong > in the kernel, I'm surprised that the largest problem seems to > have come from a userland library that I haven't touched :-/ > > julian > > > > 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 Tue Jul 2 2:20:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B98E37B425 for ; Tue, 2 Jul 2002 02:20:16 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9606B43E0A for ; Tue, 2 Jul 2002 02:20:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702092014.IJOK6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 09:20:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA95595; Tue, 2 Jul 2002 02:05:04 -0700 (PDT) Date: Tue, 2 Jul 2002 02:05:03 -0700 (PDT) From: Julian Elischer To: Sid Carter Cc: current@freebsd.org Subject: Re: Core Dumps et al on -current In-Reply-To: <20020702084312.GA89077@calvin.in.ibm.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 On Tue, 2 Jul 2002, Sid Carter wrote: > Hi, > > Some of my applications are failing to start on my recently compiled > kernel and world. [...] > pid 89065 (mozilla-bin), uid 1001: exited on signal 11 (core dumped) > ------------------------------------------------ > -------- > FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jul 1 21:37:15 IST 2002 root@calvin:/usr/obj/usr/src/sys/GENERIC i386 > WHen were these sources checked out (as opposed to compiled?) > Anything obvious I missed ? Uh, the KSE commit that changes most of the kernel? KDE and GNOME programs (and mozilla) are misbehaving badly. > Thanks in advance > Regards > Sid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 2:38:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E398537B400 for ; Tue, 2 Jul 2002 02:38:16 -0700 (PDT) Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B7343E0A for ; Tue, 2 Jul 2002 02:38:14 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.11.6/8.11.6) id g629bnf12679; Tue, 2 Jul 2002 10:37:49 +0100 (BST) (envelope-from rb) Message-Id: <4.3.2.7.2.20020702103543.01f85208@gid.co.uk> X-Sender: rbmail@gid.co.uk X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 02 Jul 2002 10:37:47 +0100 To: "George V. Neville-Neil" From: Bob Bishop Subject: Re: picobsd redux Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200207012155.g61Lt3pb037741@mail.meer.net> Mime-Version: 1.0 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 Hi, At 22:55 1/7/02, George V. Neville-Neil wrote: > When picobsd goes to build the libraries etc. it chokes on the csu >stuff: [etc] First, I'd echo what someone else said about avoiding -current right now. Second, you may have better luck if you buildworld before attempting a picobsd build. -- Bob Bishop +44 (0)118 977 4017 rb@gid.co.uk fax +44 (0)118 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 3: 6:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E2DC37B400 for ; Tue, 2 Jul 2002 03:06:12 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 3EA8143E09 for ; Tue, 2 Jul 2002 03:06:11 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Jul 2002 11:06:10 +0100 (BST) To: Julian Elischer Cc: FreeBSD current users Subject: Re: KSE status report In-Reply-To: Your message of "Tue, 02 Jul 2002 01:57:39 PDT." Date: Tue, 02 Jul 2002 11:06:09 +0100 From: Ian Dowse Message-ID: <200207021106.aa15257@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 , Ju lian Elischer writes: >The big problem at the moment is that something in the >source tree as a whole, and probably something that came in with KSE >is stopping us from successfully compiling a working libc_r. >(a bit ironic really). Is the new (elm)->field.tqe_next = (void *)-1; in TAILQ_REMOVE a likely candidate? That could easily tickle old bugs in other code. The libc_r code does use a lot of TAILQ macros. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 4:35:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D31DB37B400 for ; Tue, 2 Jul 2002 04:35:35 -0700 (PDT) Received: from bsd.ee (bsd.ee [194.126.101.115]) by mx1.FreeBSD.org (Postfix) with SMTP id D43CA43E09 for ; Tue, 2 Jul 2002 04:35:33 -0700 (PDT) (envelope-from hadara@bsd.ee) Received: (qmail 47338 invoked by uid 85); 2 Jul 2002 11:35:37 -0000 Received: from hadara@bsd.ee by daemon.bsd.ee by uid 82 with qmail-scanner-1.12 (spamassassin: 2.20. . Clear:. Processed in 0.049481 secs); 02 Jul 2002 11:35:37 -0000 Received: from unknown (HELO depression.softematic.com) (62.128.96.250) by bsd.ee with SMTP; 2 Jul 2002 11:35:36 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Sven Petai Organization: NPO BSD Estonia To: Julian Elischer Subject: Re: Post-KSE disaster with libc_r Date: Tue, 2 Jul 2002 14:34:53 +0300 X-Mailer: KMail [version 1.4] References: In-Reply-To: Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200207021434.53827.hadara@bsd.ee> 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 tried those libc_r test programs under about a month old CURRENT, and output seems to be identical to yours (didn't try gdb on it but it gives same guard_b segfaults and same programs fail) here's the output: Test static library: -------------------------------------------------------------------------- Test c_user c_system c_total chng passed/FAILED h_user h_system h_total % chng -------------------------------------------------------------------------- hello_d 0.00 0.10 0.10 passed -------------------------------------------------------------------------- hello_s 0.00 0.12 0.12 passed -------------------------------------------------------------------------- join_leak_d 2.50 1.45 3.95 passed -------------------------------------------------------------------------- mutex_d 2.21 116.36 118.57 passed -------------------------------------------------------------------------- sem_d 0.02 0.12 0.14 passed -------------------------------------------------------------------------- sigsuspend_d 0.01 0.12 0.12 passed -------------------------------------------------------------------------- sigwait_d User defined signal 1 0.01 0.12 0.13 *** FAILED *** -------------------------------------------------------------------------- guard_s.pl 1.23 6.91 8.14 *** FAILED *** (30/30 failed) -------------------------------------------------------------------------- propagate_s.pl 3.68 0.77 4.45 *** FAILED *** (1/1 failed) -------------------------------------------------------------------------- Totals 4.74 118.26 123.00 0.00 6 / 9 passed (66.67%) 0.00 0.00 0.00 0.00% -------------------------------------------------------------------------- *** Error code 1 and lots of guard_b segfault messages to console Stop in /usr/src/lib/libc_r/test. On Tuesday 02 July 2002 05:15, Julian Elischer wrote: > I think that gets us a LOT closer! > > > Total tests 212, passed 212, failed 0 > ref4# Jul 2 01:52:52 ref4 kernel: pid 330 (guard_b), uid 0: exited on > signal 11 (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 334 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 338 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 342 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 346 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:52 ref4 kernel: pid 350 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 354 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 358 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 362 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 366 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 370 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 374 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 378 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:53 ref4 kernel: pid 382 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:54 ref4 kernel: pid 386 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:54 ref4 kernel: pid 390 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:54 ref4 kernel: pid 394 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:54 ref4 kernel: pid 398 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:54 ref4 kernel: pid 402 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 406 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 410 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 414 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 418 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 422 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 426 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 430 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:55 ref4 kernel: pid 434 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:56 ref4 kernel: pid 438 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:56 ref4 kernel: pid 442 (guard_b), uid 0: exited on signal 11 > (core dumped) > Jul 2 01:52:56 ref4 kernel: pid 446 (guard_b), uid 0: exited on signal 11 > (core dumped) > > -------------------------------------------------------------------------- > sigsuspend_d 0.00 0.01 0.01 > passed > -------------------------------------------------------------------------- > sigwait_d 0.00 0.01 0.01 > *** FAILED *** > -------------------------------------------------------------------------- > guard_s.pl 0.06 0.88 0.95 > *** FAILED *** (30/30 failed) > -------------------------------------------------------------------------- > propagate_s.pl 0.14 0.07 0.21 > *** FAILED *** (1/1 failed) > -------------------------------------------------------------------------- > Totals 3.34 151.65 154.99 0.00 > 6 / 9 passed (66.67%) 0.00 0.00 0.00 0.00% > -------------------------------------------------------------------------- > *** Error code 1 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 4:36:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10E9E37B400 for ; Tue, 2 Jul 2002 04:36:14 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id F140743E31 for ; Tue, 2 Jul 2002 04:36:12 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g62BZpNq000896; Tue, 2 Jul 2002 15:36:00 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g62BZktJ000895; Tue, 2 Jul 2002 15:35:47 +0400 (MSD) (envelope-from ache) Date: Tue, 2 Jul 2002 15:35:42 +0400 From: "Andrey A. Chernov" To: eischen@pcnet1.pcnet.com Cc: current@freebsd.org Subject: Post-KSE: spiral down to death Message-ID: <20020702113540.GA837@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.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 notice on just updated -current and yesterday's -current too: after few hours of work spiral death slowly happens: system acts like load averege is about 80 while it is really 0.03, it ends with no ping response / reboot required. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 4:46:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EBFD37B400; Tue, 2 Jul 2002 04:46:40 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FF0C43E0A; Tue, 2 Jul 2002 04:46:38 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g62BjlNq001009; Tue, 2 Jul 2002 15:46:23 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g62Bjfd1001008; Tue, 2 Jul 2002 15:45:42 +0400 (MSD) (envelope-from ache) Date: Tue, 2 Jul 2002 15:45:34 +0400 From: "Andrey A. Chernov" To: des@freebsd.org Cc: current@freebsd.org Subject: PasswordAuthentication not works in sshd Message-ID: <20020702114530.GB837@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.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 just upgrade to recent -current sshd and found that PasswordAuthentication not works anymore (always fails, with right password too). I not yet dig deeper at this moment, just FYI. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 5: 6: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94D1237B400 for ; Tue, 2 Jul 2002 05:06:00 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBD2943E31 for ; Tue, 2 Jul 2002 04:59:18 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.4/8.12.3) with ESMTP id g62BrcNq001098; Tue, 2 Jul 2002 15:53:52 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.4/8.12.3/Submit) id g62BrQVn001096; Tue, 2 Jul 2002 15:53:28 +0400 (MSD) (envelope-from ache) Date: Tue, 2 Jul 2002 15:53:18 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Cc: ru@freebsd.org Subject: build stopper: gperf Message-ID: <20020702115312.GA1029@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.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 It seems some lib*++ is missing: ... c++ -O -pipe -march=pentiumpro -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -o gperf bool-array.o gen-perf.o hash-table.o iterator.o key-list.o list-node.o main.o new.o options.o read-line.o trace.o vectors.o version.o hash.o getopt.o getopt1.o gen-perf.o: In function `Gen_Perf::Gen_Perf()': gen-perf.o(.text+0xeb): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x102): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x109): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x11d): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x125): undefined reference to `Vectors::asso_values' gen-perf.o: In function `Gen_Perf::Gen_Perf()': gen-perf.o(.text+0x295): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x2ac): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x2b3): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x2c7): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x2cf): undefined reference to `Vectors::asso_values' gen-perf.o: In function `Gen_Perf::change(List_Node*, List_Node*)': gen-perf.o(.text+0x47b): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x4c4): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x508): undefined reference to `Vectors::asso_values' gen-perf.o: In function `Gen_Perf::operator()()': gen-perf.o(.text+0x651): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x753): more undefined references to `Vectors::asso_values' follow gen-perf.o: In function `Gen_Perf::~Gen_Perf()': gen-perf.o(.text+0x865): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x86c): undefined reference to `Vectors::occurrences' gen-perf.o(.text+0x88d): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x8a8): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o: In function `Gen_Perf::~Gen_Perf()': gen-perf.o(.text+0x917): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o(.text+0x91e): undefined reference to `Vectors::occurrences' gen-perf.o(.text+0x93f): undefined reference to `Vectors::asso_values' gen-perf.o(.text+0x95a): undefined reference to `Vectors::ALPHA_SIZE' gen-perf.o: In function `Gen_Perf::sort_set(char*, int)': gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf8sort_setEPci+0x41): undefined reference to `Vectors::occurrences' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf8sort_setEPci+0x48): undefined reference to `Vectors::occurrences' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf8sort_setEPci+0x4f): undefined reference to `Vectors::occurrences' gen-perf.o: In function `Gen_Perf::affects_prev(char, List_Node*)': gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf12affects_prevEcP9List_Node+0x16): undefined reference to `Vectors::asso_values' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf12affects_prevEcP9List_Node+0x68): undefined reference to `Vectors::asso_values' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf12affects_prevEcP9List_Node+0x8d): undefined reference to `Vectors::asso_values' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf12affects_prevEcP9List_Node+0x153): undefined reference to `Vectors::asso_values' gen-perf.o(.gnu.linkonce.t._ZN8Gen_Perf12affects_prevEcP9List_Node+0x1fe): undefined reference to `Vectors::asso_values' hash-table.o: In function `Hash_Table::insert(List_Node*)': hash-table.o(.text+0x242): undefined reference to `hashpjw(char const*, unsigned)' key-list.o: In function `Key_List::reorder()': key-list.o(.text+0x9b1): undefined reference to `Vectors::occurrences' key-list.o: In function `Key_List::output_hash_function()': key-list.o(.text+0x10f9): undefined reference to `Vectors::ALPHA_SIZE' key-list.o(.text+0x1145): undefined reference to `Vectors::occurrences' key-list.o(.text+0x114f): undefined reference to `Vectors::asso_values' key-list.o(.text+0x1165): undefined reference to `Vectors::ALPHA_SIZE' list-node.o: In function `List_Node::List_Node(char const*, int, char const*)': list-node.o(.text+0x66): undefined reference to `Vectors::occurrences' list-node.o(.text+0x8d): undefined reference to `Vectors::occurrences' list-node.o: In function `List_Node::List_Node(char const*, int, char const*)': list-node.o(.text+0x19a): undefined reference to `Vectors::occurrences' list-node.o(.text+0x1c1): undefined reference to `Vectors::occurrences' options.o: In function `Options::operator()(int, char**)': options.o(.text+0xd74): undefined reference to `Vectors::ALPHA_SIZE' *** Error code 1 Stop in /usr/src/gnu/usr.bin/gperf. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 5:32:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7DA437B400 for ; Tue, 2 Jul 2002 05:32:12 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE9A143E52 for ; Tue, 2 Jul 2002 05:32:11 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 1E105534A; Tue, 2 Jul 2002 14:01:36 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: PasswordAuthentication not works in sshd References: <20020702114530.GB837@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 02 Jul 2002 14:01:35 +0200 In-Reply-To: <20020702114530.GB837@nagual.pp.ru> Message-ID: Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 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 "Andrey A. Chernov" writes: > I just upgrade to recent -current sshd and found that > PasswordAuthentication not works anymore (always fails, with right > password too). I not yet dig deeper at this moment, just FYI. Try this: =================================================================== RCS file: /home/ncvs/src/crypto/openssh/monitor.c,v retrieving revision 1.6 diff -u -r1.6 monitor.c --- monitor.c 29 Jun 2002 11:48:58 -0000 1.6 +++ monitor.c 2 Jul 2002 12:00:31 -0000 @@ -831,7 +831,7 @@ auth_method = "keyboard-interactive/pam"; if (ret == 0) pam_authok = pam_ctxt; - return (ret); + return (0); } int DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 5:32:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FBDE37B400 for ; Tue, 2 Jul 2002 05:32:42 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAE3C43E13 for ; Tue, 2 Jul 2002 05:32:40 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 WAA29051; Tue, 2 Jul 2002 22:08:32 +1000 Date: Tue, 2 Jul 2002 22:14:21 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Matthew Dillon Cc: Julian Elischer , "Long, Scott" , FreeBSD current users Subject: Re: -current results (was something funny with soft updates?) In-Reply-To: <200207020314.g623Eke5038019@apollo.backplane.com> Message-ID: <20020702215851.A11958-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, 1 Jul 2002, Matthew Dillon wrote: > SMP builds are still producing panics every 2-4 buildworlds after the > KSE commit, I'm still trying to track that down. But I was able to > complete the softupdates/non-softupdates test with a UP build of > -current: > > with softupdates (UP BUILD, CURRENT): > 3122.30 real 2360.70 user 532.54 sys > 3083.17 real 2361.14 user 529.53 sys > 3085.05 real 2361.59 user 529.32 sys > > without softupdates (UP BUILD, CURRENT): > 3361.70 real 2365.23 user 535.50 sys > 3451.55 real 2368.22 user 537.26 sys > 3454.85 real 2369.42 user 536.69 sys > ^^^^^ > ~350 second dif note user times > for real. > My conclusion is that softupdates is working fine and (A) the new GCC > is a whole lot less efficient then the old GCC and (B) user times are > masking gains (due to high parallelism) that would otherwise be > realized with softupdates. This seems like the right diagnosis. The new gcc is very well pessimized. A 60% increase in user times is normal :-(. Your increase of almost 70% seems a little high. I guess this is because the user times are not quite directly comparable. SMP can easily increase user time by causing more cache misses... > : (original tests under -stable) > :test1# cat x1 (SMP BUILD, STABLE, WITH SOFTUPDATES) > : 1497.09 real 1397.98 user 612.06 sys > : 1500.12 real 1399.33 user 609.79 sys > : 1494.82 real 1398.30 user 612.46 sys > :test1# cat x2 (SMP BUILD, STABLE, WITHOUT SOFTUPDATES) > : 2449.14 real 1401.34 user 625.54 sys > : 2389.75 real 1400.38 user 629.86 sys > : 2358.82 real 1403.26 user 624.93 sys > : > ( ~889 second difference in real time) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 6: 8:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A951437B401 for ; Tue, 2 Jul 2002 06:08:24 -0700 (PDT) Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC75743E0A for ; Tue, 2 Jul 2002 06:08:23 -0700 (PDT) (envelope-from sidcarter@symonds.net) Received: from westrelay05.boulder.ibm.com (westrelay05.boulder.ibm.com [9.17.192.101]) by e1.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g62D8Lg5178802 for ; Tue, 2 Jul 2002 09:08:21 -0400 Received: from calvin.in.ibm.com (calvin.in.ibm.com [9.182.24.126]) by westrelay05.boulder.ibm.com (8.11.1m3/NCO/VER6.2) with ESMTP id g62D7WF22146 for ; Tue, 2 Jul 2002 07:07:32 -0600 Received: by calvin.in.ibm.com (Postfix, from userid 1001) id D7EF9311B; Tue, 2 Jul 2002 18:37:42 +0530 (IST) Date: Tue, 2 Jul 2002 18:37:42 +0530 From: Sid Carter To: current@freebsd.org Subject: Kernel Panic and Reboot Message-ID: <20020702130742.GA361@calvin.in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: uname -rsp Organisation: Sid Carter Inc. User-Agent: Mutt/1.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 dunno if this is w.r.t. the KSE thingie going on, but my machine got rebooted a while back with this error. I am presently in the old kernel. The syslog shows this -------------------------------------------- Jul 2 18:32:24 calvin syslogd: kernel boot file is /boot/kernel.old/kernel Jul 2 18:32:24 calvin kernel: /var: bad dir ino 18826 at offset 44: mangled entry Jul 2 18:32:24 calvin kernel: panic: ufs_dirbad: bad dir Jul 2 18:32:24 calvin kernel: Jul 2 18:32:24 calvin kernel: syncing disks... panic: bremfree: bp 0xc76b3530 n ot locked Jul 2 18:32:24 calvin kernel: Uptime: 20h16m59s Jul 2 18:32:24 calvin kernel: Terminate ACPI Jul 2 18:32:24 calvin kernel: Automatic reboot in 15 seconds -------------------------------------------- uname -a -------- FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jun 25 02:09:28 IST 2002 root@calvin:/usr/obj/usr/src/sys/GENERIC i386 Is this related to the KSE thingie ? Does the latest cvsup solve it ? TIA Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 6:51:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FCCD37B400 for ; Tue, 2 Jul 2002 06:51:37 -0700 (PDT) Received: from apimail.dns2go.com (pD9E092BE.dip.t-dialin.net [217.224.146.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A9F43E13 for ; Tue, 2 Jul 2002 06:51:36 -0700 (PDT) (envelope-from mariog@tomservo.cc) Received: from tomservo.cc (sgi.api.de [192.168.42.246]) by apimail.dns2go.com (Postfix) with ESMTP id EA4F033A20C for ; Tue, 2 Jul 2002 16:52:30 +0200 (CEST) Message-ID: <3D21AFE6.2050605@tomservo.cc> Date: Tue, 02 Jul 2002 15:51:34 +0200 From: Mario Goebbels User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Subject: About GEOM... 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 Hi! I have some questions about it. The first one is, when I compiled GEOM into the kernel, will physical disks be controlled by it already? Or does it apply to md mounted devices yet? And the second is, when will it be officially activated? Seems to work fine yet (toying around with it). Thanks for any infos. Cheers -mg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 7: 5:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD94737B41A for ; Tue, 2 Jul 2002 07:05:39 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B17A43E09 for ; Tue, 2 Jul 2002 07:05:39 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g62E58A55302; Tue, 2 Jul 2002 09:05:08 -0500 (CDT) (envelope-from jlemon) Date: Tue, 2 Jul 2002 09:05:08 -0500 (CDT) From: Jonathan Lemon Message-Id: <200207021405.g62E58A55302@prism.flugsvamp.com> To: iedowse@maths.tcd.ie, current@freebsd.org, julian@elischer.org Subject: Re: KSE status report X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: 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 article you write: >In message , Ju >lian Elischer writes: >>The big problem at the moment is that something in the >>source tree as a whole, and probably something that came in with KSE >>is stopping us from successfully compiling a working libc_r. >>(a bit ironic really). > >Is the new > > (elm)->field.tqe_next = (void *)-1; > >in TAILQ_REMOVE a likely candidate? That could easily tickle old >bugs in other code. The libc_r code does use a lot of TAILQ macros. From casual inspection of the sources, it appears this may be the case: uthread/pthread_private.h: #define PTHREAD_WORKQ_REMOVE(thrd) do { \ TAILQ_REMOVE(&_workq,thrd,qe); \ (thrd)->flags &= ~PTHREAD_FLAGS_IN_WORKQ; \ } while (0) uthread/uthread_kern.c (in multiple locations): TAILQ_FOREACH(pthread, &_workq, qe) { .... PTHREAD_WORKQ_REMOVE(pthread); } -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 7:15:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AE8637B400 for ; Tue, 2 Jul 2002 07:15:46 -0700 (PDT) Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BD9143E0A for ; Tue, 2 Jul 2002 07:15:46 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g62EFbC64925; Tue, 2 Jul 2002 07:15:37 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by mail.meer.net (8.12.2/8.12.1/meer) with ESMTP id g62EFWpb048023; Tue, 2 Jul 2002 07:15:44 -0700 (PDT) Message-Id: <200207021415.g62EFWpb048023@mail.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: vegacap@i.com.ua Cc: freebsd-current@FreeBSD.ORG Subject: Re: picobsd redux In-Reply-To: Message from Maxim Sobolev of "Tue, 02 Jul 2002 12:04:46 +0300." <3D216CAE.46596D21@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jul 2002 07:15:33 -0700 From: "George V. Neville-Neil" 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 there any particular reason for using -current for that? The > problem is that -current is in horrible state now (gcc 3.1, KSE-III > and so on), so that I'd suggest to use -stable branch or -current > sources just before gcc 3.1 import. > Well there are two things going on. My employer wants to use -CURRENT and is willing to let me hack on it, and the other is that I volunteered to do some of the multi-threading/locking work in the network stack. If I can kill these two birds with one stone I can do work for the project while also getting paid. Alas the paid part gets a higher priority :-) When, exactly, was the 3.1 import? Later, George -- George V. Neville-Neil gnn@neville-neil.com Neville-Neil Consulting www.neville-neil.com "I learn only to be contented." inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 7:31:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64FC637B400 for ; Tue, 2 Jul 2002 07:31:12 -0700 (PDT) Received: from mail2.itxmarket.com (fw.itxmarket.com [213.11.40.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9062C43E13 for ; Tue, 2 Jul 2002 07:31:11 -0700 (PDT) (envelope-from mich@freebsdcluster.net) Received: from freebsdcluster.net (mich2.itxmarket.com [192.168.2.26]) by mail2.itxmarket.com (Postfix) with ESMTP id 6946E37C9D for ; Tue, 2 Jul 2002 16:30:23 +0200 (CEST) Received: by freebsdcluster.net (Postfix, from userid 1000) id D835F3B9644; Tue, 2 Jul 2002 16:28:10 +0200 (CEST) Date: Tue, 2 Jul 2002 16:28:10 +0200 From: Michael Hostbaek To: current@FreeBSD.ORG Subject: kern: device pcm problems Message-ID: <20020702142810.GB29841@mich2.itxmarket.com> Mail-Followup-To: Michael Hostbaek , current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 4.6-STABLE i386 X-PGP-Key: http://www.freebsdcluster.org/~mich/ User-Agent: Mutt/1.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 problems getting my sound card functioning under -CURRENT. (While it was working perfect under -STABLE). I simply added 'device pcm' to the kernel config, when booting on new kernel I get lots of errors like this: port 0x1400-0x14ff irq 5 at device 8.0 on pci0 ../../../vm/uma_core.c:1333: could sleep with "pcm0" locked from ../../../dev/so und/pcm/sound.c:134 PR # 40115 -- Best Regards, Michael Landin Hostbaek FreeBSDCluster.org - an International Community */ PGP-key available upon request /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 7:39: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F1EE37B400 for ; Tue, 2 Jul 2002 07:38:58 -0700 (PDT) Received: from lockdown.spectrum.fearmuffs.net (c164-147.pro.thalamus.se [212.31.164.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14B5143E3D for ; Tue, 2 Jul 2002 07:38:47 -0700 (PDT) (envelope-from gmh003532@brfmasthugget.se) Received: from lockdown.spectrum.fearmuffs.net (localhost.spectrum.fearmuffs.net [127.0.0.1]) by lockdown.spectrum.fearmuffs.net (8.12.3/8.12.3) with ESMTP id g62Ecjg7002283; Tue, 2 Jul 2002 16:38:46 +0200 (CEST) (envelope-from gmh003532@brfmasthugget.se) Received: (from redpixel@localhost) by lockdown.spectrum.fearmuffs.net (8.12.3/8.12.3/Submit) id g62EciYX002282; Tue, 2 Jul 2002 16:38:44 +0200 (CEST) (envelope-from gmh003532@brfmasthugget.se) Date: Tue, 2 Jul 2002 16:38:44 +0200 From: Martin Faxer To: Michael Hostbaek Cc: current@FreeBSD.ORG Subject: Re: kern: device pcm problems Message-ID: <20020702143844.GA517@lockdown.spectrum.fearmuffs.net> References: <20020702142810.GB29841@mich2.itxmarket.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020702142810.GB29841@mich2.itxmarket.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.07.02 16:28:10 +0000, Michael Hostbaek wrote: > I have problems getting my sound card functioning under -CURRENT. (While > it was working perfect under -STABLE). > > I simply added 'device pcm' to the kernel config, when booting on new > kernel I get lots of errors like this: > > port 0x1400-0x14ff irq 5 at device 8.0 on pci0 > ../../../vm/uma_core.c:1333: could sleep with "pcm0" locked from ../../../dev/so > und/pcm/sound.c:134 This is a well known problem; it's basically a diagnostic message telling you that there's a deficiency in the pcm driver. If you want to fix it permanently I suggest that you go and have a look at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without holding the lock. If you just want to work around it, you can probably disable INVARIANTS and WITNESS in your kernel configuration and hope that it won't turn into a real problem (ie. panic.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 7:54:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B87A37B405 for ; Tue, 2 Jul 2002 07:54:25 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id E45BF43E09 for ; Tue, 2 Jul 2002 07:54:24 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g62Es2D56997 for current@freebsd.org; Tue, 2 Jul 2002 09:54:02 -0500 (CDT) (envelope-from jlemon) Date: Tue, 2 Jul 2002 09:54:02 -0500 From: Jonathan Lemon To: current@freebsd.org Subject: additional queue macro Message-ID: <20020702095402.D1020@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i 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 What do people think about adding the following macro to ? (I don't care much about the name, just the functionality) #define TAILQ_FOREACH_TMP(var, tmp, head, field) \ for ((var) = TAILQ_FIRST((head)); \ (var) && (((tmp) = TAILQ_NEXT((var), field)) || 1); \ (var) = (tmp)) Essentially, this provides a traversal of the tailq that is safe from element removal, while being simple to drop in to those sections of the code that need updating, as evidenced in the patch below. -- Jonathan Index: uthread_kern.c =================================================================== RCS file: /ncvs/src/lib/libc_r/uthread/uthread_kern.c,v retrieving revision 1.40 diff -u -r1.40 uthread_kern.c --- uthread_kern.c 2002/02/09 19:58:41 1.40 +++ uthread_kern.c 2002/07/02 14:52:00 @@ -664,7 +664,7 @@ int kern_pipe_added = 0; int nfds = 0; int timeout_ms = 0; - struct pthread *pthread; + struct pthread *pthread, *pthread_next; struct timespec ts; struct timeval tv; @@ -746,7 +746,7 @@ } PTHREAD_WAITQ_SETACTIVE(); - TAILQ_FOREACH(pthread, &_workq, qe) { + TAILQ_FOREACH_TMP(pthread, pthread_next, &_workq, qe) { switch (pthread->state) { case PS_SPINBLOCK: /* @@ -858,7 +858,7 @@ * _poll syscall: */ PTHREAD_WAITQ_SETACTIVE(); - TAILQ_FOREACH(pthread, &_workq, qe) { + TAILQ_FOREACH_TMP(pthread, pthread_next, &_workq, qe) { switch (pthread->state) { case PS_SPINBLOCK: /* @@ -947,7 +947,7 @@ * that is now available. */ PTHREAD_WAITQ_SETACTIVE(); - TAILQ_FOREACH(pthread, &_workq, qe) { + TAILQ_FOREACH_TMP(pthread, pthread_next, &_workq, qe) { if (pthread->state == PS_SPINBLOCK) { /* * If the lock is available, let the thread run. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 8: 9: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0150037B400 for ; Tue, 2 Jul 2002 08:09:05 -0700 (PDT) Received: from gehicks.dyndns.org (adsl-20-181-84.asm.bellsouth.net [66.20.181.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A29843E2F for ; Tue, 2 Jul 2002 08:09:04 -0700 (PDT) (envelope-from gehicks@gehicks.dyndns.org) Received: from mac (mac [10.0.0.13]) by gehicks.dyndns.org (8.12.5/8.12.5) with ESMTP id g62FGQZZ005609; Tue, 2 Jul 2002 15:16:26 GMT (envelope-from gehicks@gehicks.dyndns.org) Date: Tue, 2 Jul 2002 11:09:01 -0400 Subject: Re: additional queue macro Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Cc: current@freebsd.org To: Jonathan Lemon From: W Gerald Hicks In-Reply-To: <20020702095402.D1020@prism.flugsvamp.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.482) 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 Tuesday, July 2, 2002, at 10:54 AM, Jonathan Lemon wrote: > What do people think about adding the following macro to ? > (I don't care much about the name, just the functionality) > Looks great. How about TAILQ_FOREACH_SAFE? Thanks, I'm going to put this in our embedded version of queue.h here :-) Jerry Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 8:13:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0043E37B400 for ; Tue, 2 Jul 2002 08:13:08 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id E316543E3B for ; Tue, 2 Jul 2002 08:13:07 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Jul 2002 16:13:07 +0100 (BST) To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: additional queue macro In-Reply-To: Your message of "Tue, 02 Jul 2002 09:54:02 CDT." <20020702095402.D1020@prism.flugsvamp.com> Date: Tue, 02 Jul 2002 16:13:06 +0100 From: Ian Dowse Message-ID: <200207021613.aa59595@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 <20020702095402.D1020@prism.flugsvamp.com>, Jonathan Lemon writes: >Essentially, this provides a traversal of the tailq that is safe >from element removal, while being simple to drop in to those sections >of the code that need updating, as evidenced in the patch below. Note that this of course is not "safe from element removal" in general; it is just safe when you remove any element other than the next element, whereas TAILQ_FOREACH is safe when you remove any element other than the current one. For example it would not be safe to call a callback that could potentially remove arbitrary elements. It may be clearer in this case just to expand the macro in the code so that it is more obvious what assumptions can be made. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 8:57: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A201637B405 for ; Tue, 2 Jul 2002 08:56:57 -0700 (PDT) Received: from smtp.uc3m.es (smtp03.uc3m.es [163.117.136.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id D70AC43E13 for ; Tue, 2 Jul 2002 08:56:55 -0700 (PDT) (envelope-from jrh@it.uc3m.es) Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by smtp.uc3m.es (Postfix) with ESMTP id 55FEB43164; Tue, 2 Jul 2002 17:56:54 +0200 (CEST) Received: from it.uc3m.es (zangano.it.uc3m.es [163.117.140.41]) by smtp03.uc3m.es (Postfix) with ESMTP id B483A99DE4; Tue, 2 Jul 2002 17:56:33 +0200 (CEST) Message-ID: <3D21CD2C.C1797A68@it.uc3m.es> Date: Tue, 02 Jul 2002 17:56:28 +0200 From: Juan Francisco Rodriguez Hervella X-Mailer: Mozilla 4.74 [es] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: Martin Faxer Cc: Michael Hostbaek , current@FreeBSD.ORG Subject: Re: kern: device pcm problems References: <20020702142810.GB29841@mich2.itxmarket.com> <20020702143844.GA517@lockdown.spectrum.fearmuffs.net> 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 Martin Faxer escribió: > On 2002.07.02 16:28:10 +0000, Michael Hostbaek wrote: > > I have problems getting my sound card functioning under -CURRENT. (While > > it was working perfect under -STABLE). > > > > I simply added 'device pcm' to the kernel config, when booting on new > > kernel I get lots of errors like this: > > > > port 0x1400-0x14ff irq 5 at device 8.0 on pci0 > > ../../../vm/uma_core.c:1333: could sleep with "pcm0" locked from ../../../dev/so > > und/pcm/sound.c:134 > > This is a well known problem; it's basically a diagnostic message > telling you that there's a deficiency in the pcm driver. > > If you want to fix it permanently I suggest that you go and have a look > at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without > holding the lock. > Hello: Im a bit corious about what's the meaning of "UMA". Thanks and sorry fot this simple question :) JFRH. > > If you just want to work around it, you can probably disable INVARIANTS > and WITNESS in your kernel configuration and hope that it won't turn > into a real problem (ie. panic.) > > 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 Tue Jul 2 9:14:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90EF437B400 for ; Tue, 2 Jul 2002 09:14:51 -0700 (PDT) Received: from scotch.ucf.ics.uci.edu (scotch.ucf.ics.uci.edu [128.195.23.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C57943E09 for ; Tue, 2 Jul 2002 09:14:51 -0700 (PDT) (envelope-from sjh@whiskey.ucf.ics.uci.edu) Received: from whiskey.ucf.ics.uci.edu (whiskey.ucf.ics.uci.edu [128.195.23.9]) by scotch.ucf.ics.uci.edu (Postfix) with ESMTP id C1DAB14CF4 for ; Tue, 2 Jul 2002 09:14:48 -0700 (PDT) Received: from whiskey.ucf.ics.uci.edu (localhost [127.0.0.1]) by whiskey.ucf.ics.uci.edu (8.10.2+Sun/8.10.2) with ESMTP id g62GEml21171 for ; Tue, 2 Jul 2002 09:14:48 -0700 (PDT) Message-Id: <200207021614.g62GEml21171@whiskey.ucf.ics.uci.edu> To: current@freebsd.org Reply-To: sjh@ucf.ics.uci.edu X-Message-Flag: Microsoft sucks, switch to UNIX Subject: crashes in -current Date: Tue, 02 Jul 2002 09:14:48 -0700 From: Seth Hettich 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 still getting these crashes: Panicstring: bremfree: bp 0xc772a840 not locked and: Panicstring: Most recently used by kqueue On two very different systems (both PC's). I have more info in PR 38438. Is this happening to other people? -Seth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 9:17:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31ECF37B400 for ; Tue, 2 Jul 2002 09:17:52 -0700 (PDT) Received: from lockdown.spectrum.fearmuffs.net (c164-147.pro.thalamus.se [212.31.164.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 829BF43E09 for ; Tue, 2 Jul 2002 09:17:40 -0700 (PDT) (envelope-from gmh003532@brfmasthugget.se) Received: from lockdown.spectrum.fearmuffs.net (localhost.spectrum.fearmuffs.net [127.0.0.1]) by lockdown.spectrum.fearmuffs.net (8.12.3/8.12.3) with ESMTP id g62GHdg7002715; Tue, 2 Jul 2002 18:17:39 +0200 (CEST) (envelope-from gmh003532@brfmasthugget.se) Received: (from redpixel@localhost) by lockdown.spectrum.fearmuffs.net (8.12.3/8.12.3/Submit) id g62GHcMs002714; Tue, 2 Jul 2002 18:17:39 +0200 (CEST) (envelope-from gmh003532@brfmasthugget.se) Date: Tue, 2 Jul 2002 18:17:38 +0200 From: Martin Faxer To: Juan Francisco Rodriguez Hervella Cc: Michael Hostbaek , current@FreeBSD.ORG Subject: Re: kern: device pcm problems Message-ID: <20020702161738.GC517@lockdown.spectrum.fearmuffs.net> References: <20020702142810.GB29841@mich2.itxmarket.com> <20020702143844.GA517@lockdown.spectrum.fearmuffs.net> <3D21CD2C.C1797A68@it.uc3m.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D21CD2C.C1797A68@it.uc3m.es> 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.07.02 17:56:28 +0000, Juan Francisco Rodriguez Hervella wrote: > Im a bit corious about what's the meaning of "UMA". > > Thanks and sorry fot this simple question :) UMA is the "Universal Memory Allocator", written by Jeff Roberson. It's the memory manager and things like malloc(9) make use of it. It was quite recently committed to -CURRENT so if you search the archives it shouldn't be too hard to find mails describing it in more detail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 9:20:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D8E737B400 for ; Tue, 2 Jul 2002 09:20:14 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id C81D143E09 for ; Tue, 2 Jul 2002 09:20:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702162013.NZIW903.sccrmhc03.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 16:20:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA97200; Tue, 2 Jul 2002 09:14:27 -0700 (PDT) Date: Tue, 2 Jul 2002 09:14:26 -0700 (PDT) From: Julian Elischer To: Ian Dowse Cc: FreeBSD current users Subject: Re: KSE status report In-Reply-To: <200207021106.aa15257@salmon.maths.tcd.ie> 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 Good idea. Unforunatly someone tried to complie a libc_r with the old queue.h and it had the same problem (or so they said). On Tue, 2 Jul 2002, Ian Dowse wrote: > In message , Ju > lian Elischer writes: > >The big problem at the moment is that something in the > >source tree as a whole, and probably something that came in with KSE > >is stopping us from successfully compiling a working libc_r. > >(a bit ironic really). > > Is the new > > (elm)->field.tqe_next = (void *)-1; > > in TAILQ_REMOVE a likely candidate? That could easily tickle old > bugs in other code. The libc_r code does use a lot of TAILQ macros. > > Ian > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 9:20:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0696C37B400 for ; Tue, 2 Jul 2002 09:20:25 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7765043E09 for ; Tue, 2 Jul 2002 09:20:24 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702162023.NZLZ903.sccrmhc03.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 16:20:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA97222; Tue, 2 Jul 2002 09:19:25 -0700 (PDT) Date: Tue, 2 Jul 2002 09:19:25 -0700 (PDT) From: Julian Elischer To: "Andrey A. Chernov" Cc: eischen@pcnet1.pcnet.com, current@freebsd.org Subject: Re: Post-KSE: spiral down to death In-Reply-To: <20020702113540.GA837@nagual.pp.ru> 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 Interesting.. Is this SMP or UP? On Tue, 2 Jul 2002, Andrey A. Chernov wrote: > I notice on just updated -current and yesterday's -current too: after few > hours of work spiral death slowly happens: system acts like load averege > is about 80 while it is really 0.03, it ends with no ping response / > reboot required. > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > 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 Tue Jul 2 9:22:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B857E37B400 for ; Tue, 2 Jul 2002 09:22:33 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2414243E0A for ; Tue, 2 Jul 2002 09:22:33 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g62GMPvZ017340; Tue, 2 Jul 2002 12:22:25 -0400 (EDT) Date: Tue, 2 Jul 2002 12:22:25 -0400 (EDT) From: Daniel Eischen To: Jonathan Lemon Cc: iedowse@maths.tcd.ie, current@FreeBSD.ORG, julian@elischer.org Subject: Re: KSE status report In-Reply-To: <200207021405.g62E58A55302@prism.flugsvamp.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 On Tue, 2 Jul 2002, Jonathan Lemon wrote: > In article you write: > >In message , Ju > >lian Elischer writes: > >>The big problem at the moment is that something in the > >>source tree as a whole, and probably something that came in with KSE > >>is stopping us from successfully compiling a working libc_r. > >>(a bit ironic really). > > > >Is the new > > > > (elm)->field.tqe_next = (void *)-1; > > > >in TAILQ_REMOVE a likely candidate? That could easily tickle old > >bugs in other code. The libc_r code does use a lot of TAILQ macros. > > >From casual inspection of the sources, it appears this may be the case: > > uthread/pthread_private.h: > #define PTHREAD_WORKQ_REMOVE(thrd) do { \ > TAILQ_REMOVE(&_workq,thrd,qe); \ > (thrd)->flags &= ~PTHREAD_FLAGS_IN_WORKQ; \ > } while (0) > > uthread/uthread_kern.c (in multiple locations): > TAILQ_FOREACH(pthread, &_workq, qe) { > .... > PTHREAD_WORKQ_REMOVE(pthread); > } This used to be safe as long as the element removed wasn't re-added to another queue using the same link. There are other places in libc_r where we do re-use the same link (remove from one list and add to another), but roll our own loop in that case: for (p = TAILQ_FIRST(&q); p != NULL; p = p_next) { p_next = TAILQ_NEXT(p, p_qe); ... TAILQ_REMOVE(&q, pthread, p_qe); ... } -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 9:29: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C55F737B400 for ; Tue, 2 Jul 2002 09:29:03 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AF9543E2F for ; Tue, 2 Jul 2002 09:29:03 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.4/8.12.3) with ESMTP id g62GT0T4052160; Tue, 2 Jul 2002 09:29:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.4/8.12.3/Submit) id g62GT0iN052159; Tue, 2 Jul 2002 09:29:00 -0700 (PDT) (envelope-from dillon) Date: Tue, 2 Jul 2002 09:29:00 -0700 (PDT) From: Matthew Dillon Message-Id: <200207021629.g62GT0iN052159@apollo.backplane.com> To: Daniel Eischen Cc: Jonathan Lemon , iedowse@maths.tcd.ie, current@FreeBSD.ORG, julian@elischer.org Subject: Re: KSE status report References: 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 :... :another queue using the same link. There are other places in libc_r :where we do re-use the same link (remove from one list and add to :another), but roll our own loop in that case: : : for (p = TAILQ_FIRST(&q); p != NULL; p = p_next) { : p_next = TAILQ_NEXT(p, p_qe); : ... : TAILQ_REMOVE(&q, pthread, p_qe); : ... : } : :-- :Dan Eischen Why don't we simply conditionalize sys/queue.h for the _KERNEL -Matt Matthew Dillon Index: sys/sys/queue.h =================================================================== RCS file: /home/ncvs/src/sys/sys/queue.h,v retrieving revision 1.50 diff -u -r1.50 queue.h --- sys/sys/queue.h 29 Jun 2002 19:16:10 -0000 1.50 +++ sys/sys/queue.h 2 Jul 2002 16:28:24 -0000 @@ -102,7 +102,11 @@ * _REMOVE + + + + * */ -#define QUEUE_MACRO_DEBUG 0 +#ifdef _KERNEL +#define QUEUE_MACRO_DEBUG 0 /* change this for kernel debugging */ +#else +#define QUEUE_MACRO_DEBUG 0 /* leave alone for userland compatibility */ +#endif #if QUEUE_MACRO_DEBUG /* Store the last 2 places the queue element or head was altered */ struct qm_trace { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 9:36: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1D4437B400 for ; Tue, 2 Jul 2002 09:35:59 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33DAE43E2F for ; Tue, 2 Jul 2002 09:35:59 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g62GZsXO019261; Tue, 2 Jul 2002 12:35:54 -0400 (EDT) Date: Tue, 2 Jul 2002 12:35:54 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Ian Dowse , FreeBSD current users Subject: Re: KSE status report In-Reply-To: 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 On Tue, 2 Jul 2002, Julian Elischer wrote: > Good idea. > > Unforunatly someone tried to complie a libc_r with the old queue.h and it > had the same problem (or so they said). Well, it certainly looks wrong to use TAILQ_REMOVE inside of TAILQ_FOREACH, so either libc_r should be changed or queue.h should be reverted. Also, enabling the queue macro debugging will definitely break libc_r too. > On Tue, 2 Jul 2002, Ian Dowse wrote: > > > In message , Ju > > lian Elischer writes: > > >The big problem at the moment is that something in the > > >source tree as a whole, and probably something that came in with KSE > > >is stopping us from successfully compiling a working libc_r. > > >(a bit ironic really). > > > > Is the new > > > > (elm)->field.tqe_next = (void *)-1; > > > > in TAILQ_REMOVE a likely candidate? That could easily tickle old > > bugs in other code. The libc_r code does use a lot of TAILQ macros. > > > > Ian -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14: 6:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39FDC37B6BB for ; Tue, 2 Jul 2002 14:05:54 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90D5F4416E for ; Tue, 2 Jul 2002 10:00:19 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702170019.IVHS8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 17:00:19 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA97396; Tue, 2 Jul 2002 09:51:43 -0700 (PDT) Date: Tue, 2 Jul 2002 09:51:41 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: Jonathan Lemon , iedowse@maths.tcd.ie, current@FreeBSD.ORG Subject: Re: KSE status report In-Reply-To: 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 I just removed the extra debug line in queue.h that set the "next" pointer to -1 then the element was removed. Since I was told that the problem still occurs with an old queue.h I don;t think that that will fix it but we might as well try it again with this change. On Tue, 2 Jul 2002, Daniel Eischen wrote: > On Tue, 2 Jul 2002, Jonathan Lemon wrote: > > In article you write: > > >In message , Ju > > >lian Elischer writes: > > >>The big problem at the moment is that something in the > > >>source tree as a whole, and probably something that came in with KSE > > >>is stopping us from successfully compiling a working libc_r. > > >>(a bit ironic really). > > > > > >Is the new > > > > > > (elm)->field.tqe_next = (void *)-1; > > > > > >in TAILQ_REMOVE a likely candidate? That could easily tickle old > > >bugs in other code. The libc_r code does use a lot of TAILQ macros. > > > > >From casual inspection of the sources, it appears this may be the case: > > > > uthread/pthread_private.h: > > #define PTHREAD_WORKQ_REMOVE(thrd) do { \ > > TAILQ_REMOVE(&_workq,thrd,qe); \ > > (thrd)->flags &= ~PTHREAD_FLAGS_IN_WORKQ; \ > > } while (0) > > > > uthread/uthread_kern.c (in multiple locations): > > TAILQ_FOREACH(pthread, &_workq, qe) { > > .... > > PTHREAD_WORKQ_REMOVE(pthread); > > } > > This used to be safe as long as the element removed wasn't re-added to > another queue using the same link. There are other places in libc_r > where we do re-use the same link (remove from one list and add to > another), but roll our own loop in that case: > > for (p = TAILQ_FIRST(&q); p != NULL; p = p_next) { > p_next = TAILQ_NEXT(p, p_qe); > ... > TAILQ_REMOVE(&q, pthread, p_qe); > ... > } > > -- > Dan Eischen > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14: 7:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B529E37B6EE for ; Tue, 2 Jul 2002 14:06:00 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0ACC44C89 for ; Tue, 2 Jul 2002 13:20:27 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702202027.OMBY8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 20:20:27 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA97990; Tue, 2 Jul 2002 13:07:56 -0700 (PDT) Date: Tue, 2 Jul 2002 13:07:55 -0700 (PDT) From: Julian Elischer To: Wesley Morgan Cc: iedowse@maths.tcd.ie, current@FreeBSD.ORG Subject: Re: KSE status report In-Reply-To: <13302.148.175.49.1.1025639460.squirrel@www.chemikals.org> 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 ok, so you are saying that GNOME stuff works fine? What do yuo have running and is there still anything that does the wrong thing? On Tue, 2 Jul 2002, Wesley Morgan wrote: > After reading this... I got to thinking, and I copied the old headers into > the wrong place. After rebuilding, it works fine :)... That's what I get > for doing it at 2am! My fault, you guys could have fixed this almost > immediately except for some bad info from me. > > Good idea. > > > > Unforunatly someone tried to complie a libc_r with the old queue.h and > > it had the same problem (or so they said). > > > > On Tue, 2 Jul 2002, Ian Dowse wrote: > > > >> In message > >> , Ju > >> lian Elischer writes: > >> >The big problem at the moment is that something in the > >> >source tree as a whole, and probably something that came in with KSE > >> >is stopping us from successfully compiling a working libc_r. > >> >(a bit ironic really). > >> > >> Is the new > >> > >> (elm)->field.tqe_next = (void *)-1; > >> > >> in TAILQ_REMOVE a likely candidate? That could easily tickle old bugs > >> in other code. The libc_r code does use a lot of TAILQ macros. > >> > >> Ian > >> > > > > > > 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 Tue Jul 2 14: 8:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88BE737B788 for ; Tue, 2 Jul 2002 14:06:12 -0700 (PDT) Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B35F4426B for ; Tue, 2 Jul 2002 10:20:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702172014.BUCH15755.rwcrmhc53.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 17:20:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA97465; Tue, 2 Jul 2002 10:05:59 -0700 (PDT) Date: Tue, 2 Jul 2002 10:05:57 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Daniel Eischen , Jonathan Lemon , iedowse@maths.tcd.ie, current@FreeBSD.ORG Subject: Re: KSE status report In-Reply-To: <200207021629.g62GT0iN052159@apollo.backplane.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 I put the -1 under the conditional so it should be 'gone' now. we'll see it makes a difference. On Tue, 2 Jul 2002, Matthew Dillon wrote: > > :... > :another queue using the same link. There are other places in libc_r > :where we do re-use the same link (remove from one list and add to > :another), but roll our own loop in that case: > : > : for (p = TAILQ_FIRST(&q); p != NULL; p = p_next) { > : p_next = TAILQ_NEXT(p, p_qe); > : ... > : TAILQ_REMOVE(&q, pthread, p_qe); > : ... > : } > : > :-- > :Dan Eischen > > Why don't we simply conditionalize sys/queue.h for the _KERNEL > > -Matt > Matthew Dillon > > > Index: sys/sys/queue.h > =================================================================== > RCS file: /home/ncvs/src/sys/sys/queue.h,v > retrieving revision 1.50 > diff -u -r1.50 queue.h > --- sys/sys/queue.h 29 Jun 2002 19:16:10 -0000 1.50 > +++ sys/sys/queue.h 2 Jul 2002 16:28:24 -0000 > @@ -102,7 +102,11 @@ > * _REMOVE + + + + > * > */ > -#define QUEUE_MACRO_DEBUG 0 > +#ifdef _KERNEL > +#define QUEUE_MACRO_DEBUG 0 /* change this for kernel debugging */ > +#else > +#define QUEUE_MACRO_DEBUG 0 /* leave alone for userland compatibility */ > +#endif > #if QUEUE_MACRO_DEBUG > /* Store the last 2 places the queue element or head was altered */ > struct qm_trace { > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14: 9: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77EA237B8D4 for ; Tue, 2 Jul 2002 14:07:23 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4631D44E23 for ; Tue, 2 Jul 2002 14:00:24 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702210023.FGLO29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 21:00:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA98116; Tue, 2 Jul 2002 13:47:23 -0700 (PDT) Date: Tue, 2 Jul 2002 13:47:22 -0700 (PDT) From: Julian Elischer To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: additional queue macro In-Reply-To: <20020702153446.A66367@prism.flugsvamp.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 On Tue, 2 Jul 2002, Jonathan Lemon wrote: > On Tue, Jul 02, 2002 at 12:58:24PM -0700, Julian Elischer wrote: > > > > On Tue, 2 Jul 2002, Jonathan Lemon wrote: > > > > > What do people think about adding the following macro to ? > > > (I don't care much about the name, just the functionality) > > > > > > #define TAILQ_FOREACH_TMP(var, tmp, head, field) \ > > > for ((var) = TAILQ_FIRST((head)); \ > > > (var) && (((tmp) = TAILQ_NEXT((var), field)) || 1); \ > > > (var) = (tmp)) > > > > Certainly this is moving in the right direction.. > > (acknowleging the problem).. It does the job. > > but if someone knows to use it then they probably also > > know to use a temp variable themselves. > > > > It does work in that there is very little the writer can do to screw this > > up. > > > > The question is simply "is it waranted?" > > It does add complexity.. I guess it needs to be added to all > > the other types as well (LIST, STAILQ etc) > > Well, as Garrett pointed out, the question also is, "is this correct?" > It appears that the old behavior of not modifying the list pointer may > actually be part of the API (although undocumented), and one way to fix > the problem is to just document the behavior. > > Since user programs (like libc_r) may already depend on this, perhaps > the most prudent choice may be to leave the original behavior alone. yes. though the -1s in the kernel showed several bugs where threads were being handled as if they were on a list when they were no longer on that list. I'll leave it as part of teh debug code.. which brings up another question, Do you think I should remove the debug stuff when KSE becomes stable? Or maybe extend it to the other types. It was very useful in debugging KSE, showing the last 2 places that touched the linkages, but it may obscure teh source too much. thoughts anyone? > -- > Jonathan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14:11: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C53B637BF71 for ; Tue, 2 Jul 2002 14:10:22 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E1944D50 for ; Tue, 2 Jul 2002 13:35:18 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g62KYkV66884; Tue, 2 Jul 2002 15:34:46 -0500 (CDT) (envelope-from jlemon) Date: Tue, 2 Jul 2002 15:34:46 -0500 From: Jonathan Lemon To: Julian Elischer Cc: Jonathan Lemon , current@freebsd.org Subject: Re: additional queue macro Message-ID: <20020702153446.A66367@prism.flugsvamp.com> References: <20020702095402.D1020@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: 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 Tue, Jul 02, 2002 at 12:58:24PM -0700, Julian Elischer wrote: > > On Tue, 2 Jul 2002, Jonathan Lemon wrote: > > > What do people think about adding the following macro to ? > > (I don't care much about the name, just the functionality) > > > > #define TAILQ_FOREACH_TMP(var, tmp, head, field) \ > > for ((var) = TAILQ_FIRST((head)); \ > > (var) && (((tmp) = TAILQ_NEXT((var), field)) || 1); \ > > (var) = (tmp)) > > Certainly this is moving in the right direction.. > (acknowleging the problem).. It does the job. > but if someone knows to use it then they probably also > know to use a temp variable themselves. > > It does work in that there is very little the writer can do to screw this > up. > > The question is simply "is it waranted?" > It does add complexity.. I guess it needs to be added to all > the other types as well (LIST, STAILQ etc) Well, as Garrett pointed out, the question also is, "is this correct?" It appears that the old behavior of not modifying the list pointer may actually be part of the API (although undocumented), and one way to fix the problem is to just document the behavior. Since user programs (like libc_r) may already depend on this, perhaps the most prudent choice may be to leave the original behavior alone. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14:11:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2808D37C01F for ; Tue, 2 Jul 2002 14:10:33 -0700 (PDT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF2A144DEF for ; Tue, 2 Jul 2002 13:54:45 -0700 (PDT) (envelope-from null@pozo.com) Received: from quad.pozo.com (quad.pozo.com [216.101.162.53]) by pozo.com (8.12.5/8.12.5) with ESMTP id g62KsiFp000815 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 2 Jul 2002 13:54:45 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <5.1.1.6.2.20020702134604.00a7f428@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Tue, 02 Jul 2002 13:54:44 -0700 To: current@FreeBSD.ORG From: Manfred Antar Subject: dump broken on current since UFS2 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 I haven't been able to use dump since the recent UFS2 changes. the command i use is "dump 0fua /dev/nsa0 /dev/da0s1e" I get lots of this : DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955710]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955709]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955708]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955707]: count=-1 DUMP: DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955706]: count=-1 read error from /dev/da0s1e: Invalid argument: [block -1555955700]: count=-1 DUMP: DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955700]: count=-1 read error from /dev/da0s1e: Invalid argument: [sector -1555955705]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955704]: count=-1 DUMP: DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955703]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955702]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955699]: count=-1 read error from /dev/da0s1e: Invalid argument: [sector -1555955701]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955698]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1555955697]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [block -1553727488]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727488]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727487]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727486]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727485]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727484]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727483]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727482]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727481]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727480]: count=-1 DUMP: read error from /dev/da0s1e: Invalid argument: [sector -1553727479]: count=-1 The tape drive is an HP DDS2 and the disk is a Seagate 9gig SCSI. The controller is onboard Adaptec aic7880 Ultra SCSI adapter. I did a fsck -y before booting. dump worked fine before UFS2 Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14:12:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B30237C1C4 for ; Tue, 2 Jul 2002 14:11:26 -0700 (PDT) Received: from web11402.mail.yahoo.com (web11402.mail.yahoo.com [216.136.131.232]) by mx1.FreeBSD.org (Postfix) with SMTP id 3411644800 for ; Tue, 2 Jul 2002 11:55:18 -0700 (PDT) (envelope-from shizukakudo_99@yahoo.com) Message-ID: <20020702185518.87573.qmail@web11402.mail.yahoo.com> Received: from [218.102.21.1] by web11402.mail.yahoo.com via HTTP; Tue, 02 Jul 2002 11:55:18 PDT Date: Tue, 2 Jul 2002 11:55:18 -0700 (PDT) From: Shizuka Kudo Subject: ASUS CUSL2 panic on acpi To: freebsd-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 Dear all, I wonder if anyone experienced the same issue as mime. I have an ASUS CUSL2 running -current and starting about three days ago, it panic when acpi is autoloaded. If I unset acpi_load at the boot prompt, the machine works fine. Here's the panic message and a trace for those interested acpi0: on motherboard Fatal trap 12: page fault while in kernel mode fault virtual address = 0x16 fault code = supervisor read, page not present instruction pointer = 0x8:0xc04f9aca stack pointer = 0x10:0xc054ea14 frame pointer = 0x10:0xc054ea34 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) kernel: type 12 trap, code=0 Stopped at AcpiExReadDataFromField+0x5a: movzbl 0x16(%eax),%eax db> trace AcpiExReadDataFromField(c0f00400,c25da200,c054ea50,c25e50c0,0) at AcpiExReadDataFromField+0x5a AcpiExResolveNodeToValue(c0f005b0,c0f00400,1,c0ed6d40,c054eab0) at AcpiExResolveNodeToValue+0xd9 AcpiExResolveToValue(c0f005b0,c0f00400,c0f00400,0,c054eab0) at AcpiExResolveToValue+0x53 AcpiExResolveOperands(5b80,c0f005b4,c0f00400,c0efbe00,c0f00400) at AcpiExResolveOperands+0x1cf AcpiDsEvalRegionOperands(c0f00400,c25d6480,c050411e,c25d6480,0) at AcpiDsEvalRegionOperands+0x50 AcpiDsExecEndOp(c0f00400,c054eb14,c0f00414,c0f0040c,cdd4f1b1) at AcpiDsExecEndOp+0x258 AcpiPsParseLoop(c0f00400,c257f900,c054eb74,0,0) at AcpiPsParseLoop+0x579 AcpiPsParseAml(c0f00400,c25dcc40,0,cdd4f1a6,e) at AcpiPsParseAml+0x7c AcpiDsExecuteArguments(c0efbe00,c051de10,e,cdd4f1a6,c257fdc0) at AcpiDsExecuteArguments+0x182 AcpiDsGetRegionArguments(c257fdc0,0,c0efbe00,1,c054ec10) at AcpiDsGetRegionArguments+0x56 AcpiNsInitOneObject(c0efbe00,1,c054ec60,0,0) at AcpiNsInitOneObject+0xd8 AcpiNsWalkNamespace(0,ffffffff,ffffffff,1,c0500620) at AcpiNsWalkNamespace+0xad AcpiWalkNamespace(0,ffffffff,ffffffff,c0500620,c054ec60) at AcpiWalkNamespace+0x77 AcpiNsInitializeObjects(0,c054ecc8,c050b8ab,0,2) at AcpiNsInitializeObjects+0x4d AcpiEnableSubsystem(0,2,c04fd110,0,0) at AcpiEnableSubsystem+0x8a acpi_attach(c25d7580,c25b5090,c03d3590,c0ed4d00,c0f04c80) at acpi_attach+0x13b device_probe_and_attach(c25d7580,c0f04c80,c054ed2c,c0368864,c0f04c80) at device_probe_and_attach+0xaf bus_generic_attach(c0f04c80,0,c0ed4d00,c0efda80,c0f04c80) at bus_generic_attach+0x28 nexus_attach(c0f04c80,c2596090,c03d3590,c03c4480,0) at nexus_attach+0x14 device_probe_and_attach(c0f04c80,c0ef9780,c054ed80,c035b5e5,c0f04f00) at device_probe_and_attach+0xaf root_bus_configure(c0f04f00,c03c4480,0,c054ed98,c020b175) at root_bus_configure+0x28 configure(0,54b000,54bc00,54b000,0) at configure+0x35 mi_startup() at mi_startup+0xb5 begin() at begin+0x43 db> __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14:13:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28BE537B861 for ; Tue, 2 Jul 2002 14:11:52 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA7A44C7D for ; Tue, 2 Jul 2002 13:20:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020702202013.OLVU8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Tue, 2 Jul 2002 20:20:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA97984; Tue, 2 Jul 2002 13:06:02 -0700 (PDT) Date: Tue, 2 Jul 2002 13:06:01 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: FreeBSD current users Subject: Re: KSE status report In-Reply-To: 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 Dan is there a chance that before you upgrade, you see if you can get the test program to pass all the tests? If we can have one that passes on a pre KSE system it will help us considerably.. it seems to fail on the last 3 tests even pre-KSE. (may be compiler dependent). I have reports that KDE stuff seems to be working but I haven't confirmation on that. I will try install some KDE and gnome stuff on my test machines.. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 2 14:14:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DBCE37C23A for ; Tue, 2 Jul 2002 14:11:36 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D1544E29 for ; Tue, 2 Jul 2002 14:01:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 RAA11256 for ; Tue, 2 Jul 2002 17:01:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g62L0jU24089; Tue, 2 Jul 2002 17:00:45 -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: <15650.5244.978755.695282@grasshopper.cs.duke.edu> Date: Tue, 2 Jul 2002 17:00:44 -0400 (EDT) To: freebsd-current@freebsd.org Subject: ACPI breakage? 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 After updating my SuperMicro 370DLE to today's sources, I'm seeing this message scroll repeatedly across my serial console (for different values of N in the range 20-3f ): ACPI-0988: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[N], disabling event I've appended the boot log. Cheers, Drew PS: ACPI used to fail early in the boot with: ACPI-0204: *** Error: AcpiLoadTables: Could not load namespace: AE_NOT_FOUND ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NOT_FOUND ACPI: table load failed: AE_NOT_FOUND That no longer seems to happen. 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 5.0-CURRENT #1: Tue Jul 2 16:26:04 EDT 2002 gallatin@big:/usr/src/sys/i386/compile/SMP Preloaded elf kernel "/boot/kernel/kernel" at 0xc0444000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04440a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (999.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 536805376 (524224K bytes) avail memory = 516304896 (504204K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled Using $PIR table, 9 entries at 0xc00f5260 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 IOAPIC #1 intpin 2 -> irq 2 IOAPIC #1 intpin 6 -> irq 5 IOAPIC #1 intpin 15 -> irq 9 pci0: on acpi_pcib0 atapci0: port 0xdf00-0xdf3f,0xdfe0-0xdfe3,0xdfa8-0xdfaf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfe9a0000-0xfe9bffff irq 2 at device 2.0 on pci0 ata2: at 0xdff0 on atapci0 ata3: at 0xdfa8 on atapci0 pci0: at device 4.0 (no driver attached) fxp0: port 0xd400-0xd43f mem 0xfc900000-0xfc9fffff,0xfcafe000-0xfcafefff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:21:d3:0b inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: port 0x580-0x58f at device 15.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 ohci0: mem 0xfcaff000-0xfcafffff irq 10 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered acpi_pcib1: on acpi0 acpi_pcib1: we have duplicate bus number 0 - not probing bus atkbdc0: port 0x64,0x60 irq 1 on acpi0 fdc0: cmd 3 failed at out byte 1 of 3 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: cmd 3 failed at out byte 1 of 3 pcib1: at pcibus 1 on motherboard IOAPIC #1 intpin 8 -> irq 11 pci1: on pcib1 pci1: at device 1.0 (no driver attached) orm0: Greg 'groggy' Lehey wrote:
On Thursday,  4 July 2002 at 19:20:00 +1000, Bruce Evans wrote:
  
On Wed, 3 Jul 2002, Poul-Henning Kamp wrote:

    
In message <20020703233109.B17974-100000@gamplex.bde.org>, Bruce Evans writes:
      
This is mostly because resources have been diverted away from updating
working code to write a second system.
        
Make that third system, the current slice/label code is our second
system, and I don't think the resources have been diverted as much
as defected.

Either way, I know you don't want either of DEVFS or GEOM, I think
I know where you come from, I just happen to not agree that we
should stay stuck back there.
      
I disagree that DEVFS and GEOM are forwards.
    

I don't know enough about GEOM to embrace it whole-heartedly, but I
think you'd be hard pressed to find anybody who disagrees that devfs
is a forward.  It may need some improvement, but it's so much more
logical than what we had before that I really think you should explain
your objections.
DEVFS would be an improvement for me, when upgrading boxes by adding additional hardware, so I don't have to browse the dmesg, coz I will just look up /dev (since it only shows installed hardware with DEVFS). Same for GEOM, if all that will work what's described on phk's website about GEOM, then it's definitely an improvement too. I'm especially seeing forward for Copy-on-Write and encryption functionality.

-mg

--------------000308090001060506030003-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 2:32:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6920237B401 for ; Thu, 4 Jul 2002 02:32:06 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 774B443E09 for ; Thu, 4 Jul 2002 02:32:05 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 TAA31916; Thu, 4 Jul 2002 19:31:56 +1000 Date: Thu, 4 Jul 2002 19:37:56 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Terry Lambert Cc: Poul-Henning Kamp , Mario Goebbels , Subject: Re: About GEOM... In-Reply-To: <3D23382F.9117C663@mindspring.com> Message-ID: <20020704193543.N21375-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 Wed, 3 Jul 2002, Terry Lambert wrote: > Bruce Evans wrote: > > On Wed, 3 Jul 2002, Poul-Henning Kamp wrote: > > > Some bits are missing yet, for instance the ioctls to change > > > disklabels etc. when they're done and it works also with sysinstall > > > it'll be standard. > > > > It shouldn't be standard, because then using it wouldn't be optional. > > Are you kidding?!? > > That's why it *should* be standard! I don't plan to use it, so making it standard would just get in my way. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 2:47:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DC5937B400 for ; Thu, 4 Jul 2002 02:47:42 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 453E543E64 for ; Thu, 4 Jul 2002 02:47:41 -0700 (PDT) (envelope-from recht@contentmedia.de) Received: (qmail 947 invoked from network); 4 Jul 2002 09:46:14 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.227.204.237) by www.contentmedia.de with SMTP; 4 Jul 2002 09:46:14 -0000 Subject: panic with today's pmap From: Marc Recht To: Julian Elischer Cc: current@FreeBSD.ORG Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 04 Jul 2002 11:47:38 +0200 Message-Id: <1025776059.8085.1.camel@leeloo.intern.geht.de> Mime-Version: 1.0 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 got this with today's pmap panic: pmap_new_thread: kstack allocation failed Yesterday's kernel works fine. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 3:56:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF67A37B400 for ; Thu, 4 Jul 2002 03:56:46 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF0A143E3B for ; Thu, 4 Jul 2002 03:56:45 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 UAA06509; Thu, 4 Jul 2002 20:56:29 +1000 Date: Thu, 4 Jul 2002 21:02:30 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: David Xu Cc: Julian Elischer , Subject: Re: Timeout and SMP race In-Reply-To: <00f401c22337$c6c94d90$ef01a8c0@davidwnt> Message-ID: <20020704202730.X21619-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 Thu, 4 Jul 2002, David Xu wrote: > ----- Original Message ----- > From: "Julian Elischer" > To: "David Xu" > Cc: > Sent: Thursday, July 04, 2002 4:36 PM > Subject: Re: Timeout and SMP race > > > > On Thu, 4 Jul 2002, David Xu wrote: > > > > > while we are getting rid of Giant, current race condition between softclock() > > > and callout_stop() is unacceptable. the race causes two many places in source > > > code would be modified to fit this new behaviour, besides this, everywhere > > > callout_stop() is used need to hold sched_lock and do a mi_switch() and > > > modify td_flags is also unacceptable, this SMP race should be resolved in > > > kern_timeout.c. > > > > > > David Xu > > > > This is probably true.. > > the current hacks for this are rather horrible. I think there msut be > > better ways. Your suggestion sounds plausible. > > > > > > if another thread other than softclock itself is calling callout_stop(), > and callout_stop() detected that softclock is currently running the > callout, it should wait until softclock finishes the work, then return. softclock() intentionally releases callout_lock() to allow other processes to manipulate callouts. What is the race exactly? Concurrent calls to softclock() seem to be possible but seem to be handled correctly (internal locking prevents problems). Well, I can see one race in softclock(): % c_func = c->c_func; % c_arg = c->c_arg; % c_flags = c->c_flags; This caches some values, as is needed since the 'c' pointer may become invalid after we release the lock ... but the things pointed to may become invalid too. % c->c_func = NULL; % if (c->c_flags & CALLOUT_LOCAL_ALLOC) { % c->c_flags = CALLOUT_LOCAL_ALLOC; % SLIST_INSERT_HEAD(&callfree, c, % c_links.sle); % } else % c->c_flags &= ~CALLOUT_PENDING; % mtx_unlock_spin(&callout_lock); callout_stop() may stop 'c' here. It won't do much, since we have already set c->c_func to NULL, but its caller may want the callout actually stopped so that it can do things like unloading the old c->c_func. % if ((c_flags & CALLOUT_MPSAFE) == 0) % mtx_lock(&Giant); % c_func(c_arg); This calls through a possibly-invalid function pointer. % if ((c_flags & CALLOUT_MPSAFE) == 0) % mtx_unlock(&Giant); % mtx_lock_spin(&callout_lock); This seems to be an old bug. In RELENG_4, splsoftclock() gives a more global lock, but there is nothing to prevent callout_stop() being run at splsoftclock(). In fact, it must be able to run when called nested from inside softclock(), since it might be called from the handler. Waiting in callout_stop() for softclock() to finish would deadlock in this case. It's interesting that this case is (always?) avoided in untimeout() by not calling callout_stop() when c->c_func == NULL. softclock() can't do anything about c->c_func going away after it is called. Clients must somehow avoid killing it. I think c->c_func rarely goes away, and the race that you noticed is lost more often. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 4:14:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 009C137B400 for ; Thu, 4 Jul 2002 04:14:25 -0700 (PDT) Received: from draco.macsch.com (ns1.mscsoftware.com [192.207.69.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8096443E31 for ; Thu, 4 Jul 2002 04:14:24 -0700 (PDT) (envelope-from Georg.Koltermann@mscsoftware.com) Received: from mailmuc.muc.eu.mscsoftware.com (mailmuc.muc.macsch.com [161.34.37.20]) by draco.macsch.com (8.9.3/8.9.3) with ESMTP id EAA24041 for ; Thu, 4 Jul 2002 04:14:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailmuc.muc.eu.mscsoftware.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g64BCRp19054 for ; Thu, 4 Jul 2002 13:12:28 +0200 Content-Transfer-Encoding: 7bit Content-Type: text/plain Date: 04 Jul 2002 13:12:47 +0200 From: "Georg-W. Koltermann" Message-Id: <1025781167.736.22.camel@hunter.muc.macsch.com> Mime-Version: 1.0 Received: from hunter.muc.macsch.com by mailmuc.muc.eu.mscsoftware.com (AvMailGate-2.0.0.6) id 19011-3744BB33; Thu, 04 Jul 2002 13:12:12 +0200 Subject: panic: Most recently used by kqueue To: freebsd-current@freebsd.org X-AntiVirus: OK! AntiVir MailGate Version 2.0.0.6 at mailmuc has not found any known virus in this email. X-Mailer: Ximian Evolution 1.0.5 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 got this panic with -current of date=2002.06.27.22.00.00. It reminds me of another panic that I had recently with a -current of 25-June, the message of that earlier incident was "panic: Most recently used by routetbl". hunter[7]$ gdb -k /boot/kernel/kernel vmcore.26 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"... (no debugging symbols found)... IdlePTD at physical address 0x005db000 initial pcb at physical address 0x004aa780 panicstr: bremfree: bp 0xd2a1def0 not locked panic messages: --- panic: Most recently used by kqueue syncing disks... panic: bremfree: bp 0xd2a1def0 not locked Uptime: 1h55m19s pfs_vncache_unload(): 3 entries remaining Dumping 1023 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008 --- #0 0xc02637a8 in doadump () (kgdb) where #0 0xc02637a8 in doadump () #1 0xc0263c32 in boot () #2 0xc0263de5 in panic () #3 0xc0295f35 in bremfree () #4 0xc029774e in vfs_bio_awrite () #5 0xc023e560 in spec_fsync () #6 0xc023e147 in spec_vnoperate () #7 0xc03521c1 in ffs_sync () #8 0xc02a46e3 in sync () #9 0xc0263885 in boot () #10 0xc0263de5 in panic () #11 0xc036f588 in mtrash_ctor () #12 0xc036e4e3 in uma_zalloc_arg () #13 0xc025b018 in malloc () #14 0xc03522a8 in ffs_vget () #15 0xc0357069 in ufs_lookup () #16 0xc035c603 in ufs_vnoperate () #17 0xc029a6b5 in vfs_cache_lookup () #18 0xc035c603 in ufs_vnoperate () #19 0xc029e5a8 in lookup () #20 0xc029e048 in namei () #21 0xc02a6a7a in stat () #22 0xc03a18f5 in syscall () #23 0xc039439d in syscall_with_err_pushed () #24 0x8129269 in ?? () #25 0x8128c15 in ?? () #26 0x81291b5 in ?? () #27 0x8151100 in ?? () #28 0x812987b in ?? () #29 0x81293c0 in ?? () #30 0x8128fab in ?? () #31 0x80f8da3 in ?? () #32 0x8129269 in ?? () #33 0x8151100 in ?? () #34 0x812987b in ?? () #35 0x81293c0 in ?? () #36 0x8151100 in ?? () #37 0x812987b in ?? () #38 0x81293c0 in ?? () #39 0x8151100 in ?? () #40 0x812987b in ?? () #41 0x81293c0 in ?? () #42 0x8151100 in ?? () #43 0x812987b in ?? () #44 0x81293c0 in ?? () #45 0x8151100 in ?? () #46 0x812987b in ?? () #47 0x81293c0 in ?? () #48 0x8151100 in ?? () #49 0x812987b in ?? () #50 0x81293c0 in ?? () #51 0x8151100 in ?? () #52 0x812987b in ?? () #53 0x81293c0 in ?? () #54 0x8151100 in ?? () #55 0x812987b in ?? () #56 0x81293c0 in ?? () #57 0x812874d in ?? () #58 0x812666e in ?? () #59 0x811fa4b in ?? () #60 0x81286b3 in ?? () #61 0x812666e in ?? () #62 0x81286b3 in ?? () #63 0x8126543 in ?? () #64 0x81286b3 in ?? () #65 0x81289a1 in ?? () #66 0x812666e in ?? () #67 0x81286b3 in ?? () #68 0x8126543 in ?? () #69 0x81286b3 in ?? () #70 0x81289a1 in ?? () #71 0x812666e in ?? () #72 0x8129806 in ?? () #73 0x81293c0 in ?? () #74 0x8128ddf in ?? () #75 0x8128c92 in ?? () #76 0x81291b5 in ?? () #77 0x8151100 in ?? () #78 0x812987b in ?? () #79 0x81293c0 in ?? () #80 0x8151100 in ?? () #81 0x812987b in ?? () #82 0x81293c0 in ?? () #83 0x8125efc in ?? () #84 0x80dd92e in ?? () #85 0x80d4585 in ?? () #86 0x8127739 in ?? () #87 0x80d387c in ?? () #88 0x812735c in ?? () #89 0x80d382e in ?? () #90 0x80d33b5 in ?? () #91 0x80d34d8 in ?? () #92 0x80d243b in ?? () #93 0x804ecd1 in ?? () (kgdb) Sorry no symbols this time, I had removed makeoptions COPTFLAGS=-gstabs+ from my config when I tried to troubleshoot a stability problem a few days ago. -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 4:21:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42A2237B400; Thu, 4 Jul 2002 04:21:52 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id F031743E09; Thu, 4 Jul 2002 04:21:50 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 VAA08503; Thu, 4 Jul 2002 21:21:48 +1000 Date: Thu, 4 Jul 2002 21:27:49 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Greg 'groggy' Lehey" Cc: Poul-Henning Kamp , Mario Goebbels , Subject: Re: About GEOM... In-Reply-To: <20020704092253.GW75946@wantadilla.lemis.com> Message-ID: <20020704210304.Y21619-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 Thu, 4 Jul 2002, Greg 'groggy' Lehey wrote: > I don't know enough about GEOM to embrace it whole-heartedly, but I > think you'd be hard pressed to find anybody who disagrees that devfs > is a forward. It may need some improvement, but it's so much more > logical than what we had before that I really think you should explain > your objections. This has been discussed before. Basically, devfs creates work by moving problems around without any significant benefits. I expect control of devfs device visibility and persistence of devfs device attributes would end up mostly in a utility (devd?). But once you have such a utility, you don't need devfs (or MAKEDEV). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 4:24:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B50EE37B400; Thu, 4 Jul 2002 04:24:20 -0700 (PDT) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9053043E42; Thu, 4 Jul 2002 04:24:19 -0700 (PDT) (envelope-from chuckr@chuckr.org) Received: from chuckr.org (localhost.chuckr.org [127.0.0.1]) by april.chuckr.org (8.11.6/8.11.3) with ESMTP id g64BLhJ46478; Thu, 4 Jul 2002 07:22:15 -0400 (EDT) (envelope-from chuckr@chuckr.org) Message-Id: <200207041122.g64BLhJ46478@april.chuckr.org> Date: Thu, 4 Jul 2002 07:21:42 -0400 (EDT) From: Chuck Robey Subject: Re: Recommended MP development machines... To: peter@wemm.org Cc: obrien@FreeBSD.ORG, gnn@neville-neil.com, freebsd-current@FreeBSD.ORG In-Reply-To: <20020704065915.8FDA2390F@overcee.wemm.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 3 Jul, Peter Wemm wrote: > Chuck Robey wrote: >> On Wed, 3 Jul 2002, David O'Brien wrote: >> >> > On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote: >> > > I know everyone says "they all work" but i'd like some recommendations > on >> > > MP machines for -CURRENT work. I'll be ordering one this week. >> > >> > There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness) > . >> > http://www.tyan.com/products/html/thunderk7.html. It comes in multiple >> > flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit >> > PCI, 1 AGP version. You can cheap out and not get the non-SCSI S2462NG >> > model. Match this bad-boy up with a pair of fast Athlon `MP' (not `XP') >> > CPU's and it is a totally solid system. Various FreeBSD committers also >> > have this system. >> > >> > There is a newer [more economic] version called the Thunder K7X. >> > http://www.tyan.com/products/html/thunderk7x.html >> >> "more economic" is a poor way to describe it, seeing as it has all the >> features, plus (1) an updated version of the AMD mp chipset and (2) a >> fixed onboard usb port. The K7 had a broken on-board usb (the AMD >> chipset had a PCI contention bug for the usb port, so the tin back panel >> of the board blocked out the usb, and the K7 came with a PCI usb card, >> which ate up one of your PCI slots. The K7X has a repaired on-board usb, >> so you get that PCI slot back. > > Hmmmmm..... Do you have any details on this? I've had occasional strange > USB-related things happen on this box. Of course, it runs -current which > puts me into the USB danger-zone enough as it is.. but what happens when > this bug is triggered? I just finished buying the K7X myself, so I did quite a bit of research before rejecting the Asus board, and the K7. This included reading about a half dozen reviews I located via google and tomshardware. I'm quite certain of my facts (and my head is abuzz with lots more board trivia about them) but it's going to take a little bit for me to run down the source of the PCI comment. I'll do that, wait a bit for it. > > Cheers, > -Peter > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 > -- ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 4:40:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DCBA37B400 for ; Thu, 4 Jul 2002 04:40:10 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D02E43E3B for ; Thu, 4 Jul 2002 04:40:10 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704114009.IOVV24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 11:40:09 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id EAA07669; Thu, 4 Jul 2002 04:38:39 -0700 (PDT) Date: Thu, 4 Jul 2002 04:38:38 -0700 (PDT) From: Julian Elischer To: Christopher Sharp Cc: current@freebsd.org Subject: Re: panic: vm_page_free: freeing wired page In-Reply-To: <20020704093056.GA614@web.de> 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 I may be fixed. but there's a memory leak still. reboot when your wired coun gets too high. On Thu, 4 Jul 2002, Christopher Sharp wrote: > Hello, > with a world+kernel from yesterday I get this message > and then the machine freezes and/or reboots. > > Any Ideas ? is this already fixed ? > > Christopher Sharp > > -- > Any time things appear to be going better, you have overlooked > something. > > 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 Thu Jul 4 4:44:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDA6237B400 for ; Thu, 4 Jul 2002 04:44:48 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A329843E42 for ; Thu, 4 Jul 2002 04:43:02 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g64BgiI42687; Thu, 4 Jul 2002 14:42:44 +0300 (EEST) (envelope-from ru) Date: Thu, 4 Jul 2002 14:42:44 +0300 From: Ruslan Ermilov To: Munish Chopra Cc: current@FreeBSD.org Subject: Re: error in /usr/src/gnu/usr.bin/binutils/doc/ Message-ID: <20020704114244.GD36762@sunbay.com> References: <20020704061239.GB326@CPE0030ab0ef2bb.cpe.net.cable.rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ylS2wUBXLOxYXZFQ" Content-Disposition: inline In-Reply-To: <20020704061239.GB326@CPE0030ab0ef2bb.cpe.net.cable.rogers.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 --ylS2wUBXLOxYXZFQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Fixed a few minutes ago. On Thu, Jul 04, 2002 at 02:12:39AM -0400, Munish Chopra wrote: > Sources checked out today, 3AM EST. >=20 > makeinfo --no-validate -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc > -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/doc > -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils > -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/mi -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc > --no-split -I /usr/src/gnu/usr.bin/binutils/doc -I > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils/b= inutils.texi > -o binutils.info > ln -sf > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/all-cfg= .texi > gdb-cfg.texi > echo "@set GDBVN `sed q > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/version.in`" > > GDBvn.texi > cp > /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc/hsu= ser.texinfo > inc-hist.texinfo > patch -b .orig < /usr/src/gnu/usr.bin/binutils/doc/inc-hist.diff > makeinfo: Removing output file `gdbint.info' due to errors; use --force > to preserve. > *** Error code 2 > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |$FreeBSD: src/gnu/usr.bin/binutils/doc/inc-hist.diff,v 1.4 2002/07/01 > 07:58:18 sheldonh Exp $ > | > |--- inc-hist.texinfo.orig Wed Apr 11 08:20:01 2001 > |+++ inc-hist.texinfo Wed Apr 11 08:21:57 2001 > -------------------------- > Patching file inc-hist.texinfo using Plan A... > Hunk #1 succeeded at 26. > Hunk #2 succeeded at 39. > done > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error >=20 > Doing a simple 'make' in the directory is fine, so I guess the > buildworld is pulling different stunts. I'd make the effort to track it, > but I'm too tired, maybe someone else will catch it in the morning or > so. >=20 > --=20 > Munish Chopra The FreeBSD NVIDIA Driver Initiative > http://nvidia.netexplorer.org >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --=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 --ylS2wUBXLOxYXZFQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9JDS0Ukv4P6juNwoRApKnAJ4jj32+MmKTfBukbXB9uIJ57uU5RwCcCGtt 199j6z4K+F/GpqYMW6+TssE= =oQX5 -----END PGP SIGNATURE----- --ylS2wUBXLOxYXZFQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 5: 1:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8C4637B400 for ; Thu, 4 Jul 2002 05:01:34 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3389D43E3B for ; Thu, 4 Jul 2002 05:00:29 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704120010.PMMD903.sccrmhc03.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 12:00:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id EAA07703; Thu, 4 Jul 2002 04:42:43 -0700 (PDT) Date: Thu, 4 Jul 2002 04:42:41 -0700 (PDT) From: Julian Elischer To: Marc Recht Cc: current@FreeBSD.ORG Subject: Re: panic with today's pmap In-Reply-To: <1025776059.8085.1.camel@leeloo.intern.geht.de> 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 what do you call "today's" ? (version #?) On 4 Jul 2002, Marc Recht wrote: > Hi! > > I got this with today's pmap > panic: pmap_new_thread: kstack allocation failed > > Yesterday's kernel works fine. > > > Marc > > > > 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 Thu Jul 4 5: 6:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E724037B400 for ; Thu, 4 Jul 2002 05:06:37 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id CA3DB43E09 for ; Thu, 4 Jul 2002 05:06:36 -0700 (PDT) (envelope-from recht@contentmedia.de) Received: (qmail 2549 invoked from network); 4 Jul 2002 12:05:09 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.227.204.237) by www.contentmedia.de with SMTP; 4 Jul 2002 12:05:09 -0000 Subject: Re: panic with today's pmap From: Marc Recht To: Julian Elischer Cc: current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 04 Jul 2002 14:06:33 +0200 Message-Id: <1025784394.23040.21.camel@leeloo.intern.geht.de> Mime-Version: 1.0 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 > what do you call "today's" ? Oops, sorry.. I know I missed something.. :-) > (version #?) src/sys/i386/i386/pmap.c,v 1.331 2002/07/04 00:35:48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 5:17: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A016537B400 for ; Thu, 4 Jul 2002 05:17:06 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4186343E09 for ; Thu, 4 Jul 2002 05:17:06 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.5/8.12.5) with ESMTP id g64CH4ZY030868; Thu, 4 Jul 2002 05:17:04 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.5/8.12.5/Submit) id g64CH4fA030867; Thu, 4 Jul 2002 05:17:04 -0700 (PDT) Date: Thu, 4 Jul 2002 05:17:04 -0700 From: Steve Kargl To: Julian Elischer Cc: FreeBSD current users Subject: Re: KSE status. Message-ID: <20020704051704.A30828@troutmask.apl.washington.edu> 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 julian@elischer.org on Wed, Jul 03, 2002 at 11:17:53PM -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 Wed, Jul 03, 2002 at 11:17:53PM -0700, Julian Elischer wrote: > > bug 1 hides bug 2 hides bug 3 > > the current state of play: > > the system works well for a while however there is a leak in > the system that gradually runs the system out memory. > the wired memory count grows with time. My test system presently has > 241MB of Wired memory out of a 512M system. > Julian, I have the latest pmap.c changes. When I reboot, I'm greeted with: Loading /boot/defaults/loader.conf Unable to load kernel! | can't load 'kernel' This could be a ACPI problem. ACPI has never worked on this motherboard, and the recently imported ACPI code might be the cause of the problem. A 2 day old kernel boots fine, but evenly dies with vm problem as you describe above. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 5:40:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E57037B400 for ; Thu, 4 Jul 2002 05:40:16 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B31043E09 for ; Thu, 4 Jul 2002 05:40:16 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704124011.JERI24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 12:40:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id FAA07948; Thu, 4 Jul 2002 05:38:02 -0700 (PDT) Date: Thu, 4 Jul 2002 05:38:01 -0700 (PDT) From: Julian Elischer To: Marc Recht Cc: current@FreeBSD.ORG Subject: Re: panic with today's pmap In-Reply-To: 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 try a new vm_glue.c as well. ( 1.140) On Thu, 4 Jul 2002, Julian Elischer wrote: > what do you call "today's" ? > (version #?) > > > > On 4 Jul 2002, Marc Recht wrote: > > > Hi! > > > > I got this with today's pmap > > panic: pmap_new_thread: kstack allocation failed > > > > Yesterday's kernel works fine. > > > > > > Marc > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 5:40:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 585E537B401 for ; Thu, 4 Jul 2002 05:40:17 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A02143E09 for ; Thu, 4 Jul 2002 05:40:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704124016.JESH24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 12:40:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id FAA07959; Thu, 4 Jul 2002 05:40:02 -0700 (PDT) Date: Thu, 4 Jul 2002 05:40:01 -0700 (PDT) From: Julian Elischer To: Steve Kargl Cc: FreeBSD current users Subject: Re: KSE status. In-Reply-To: <20020704051704.A30828@troutmask.apl.washington.edu> 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 I've checked in a change for the vm change as for the kernel.. check it is not 0 length :-) In any case you need the newest vm_glue.c (and everything else :-) On Thu, 4 Jul 2002, Steve Kargl wrote: > On Wed, Jul 03, 2002 at 11:17:53PM -0700, Julian Elischer wrote: > > > > bug 1 hides bug 2 hides bug 3 > > > > the current state of play: > > > > the system works well for a while however there is a leak in > > the system that gradually runs the system out memory. > > the wired memory count grows with time. My test system presently has > > 241MB of Wired memory out of a 512M system. > > > > Julian, > > I have the latest pmap.c changes. When I reboot, I'm > greeted with: > > Loading /boot/defaults/loader.conf > Unable to load kernel! > | > can't load 'kernel' > > This could be a ACPI problem. ACPI has never worked > on this motherboard, and the recently imported ACPI > code might be the cause of the problem. > > A 2 day old kernel boots fine, but evenly dies with > vm problem as you describe above. > > -- > Steve > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 5:47:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 034B037B400 for ; Thu, 4 Jul 2002 05:47:30 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40F1043E31 for ; Thu, 4 Jul 2002 05:47:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.5/8.12.5) with ESMTP id g64ClRZY031147; Thu, 4 Jul 2002 05:47:27 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.5/8.12.5/Submit) id g64ClRcH031146; Thu, 4 Jul 2002 05:47:27 -0700 (PDT) Date: Thu, 4 Jul 2002 05:47:27 -0700 From: Steve Kargl To: Julian Elischer Cc: FreeBSD current users Subject: Re: KSE status. Message-ID: <20020704054727.A31138@troutmask.apl.washington.edu> References: <20020704051704.A30828@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 In-Reply-To: ; from julian@elischer.org on Thu, Jul 04, 2002 at 05:40:01AM -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 Thu, Jul 04, 2002 at 05:40:01AM -0700, Julian Elischer wrote: > I've checked in a change for the vm change > > as for the kernel.. check it is not 0 length :-) > Doh! I've built so many kernels the last few days that I just assumed it worked. I've never seen an empty /boot/kernel before this morning. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:10:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C9CF37B400 for ; Thu, 4 Jul 2002 06:10:42 -0700 (PDT) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90E4743E31 for ; Thu, 4 Jul 2002 06:10:38 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5]) by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id g64DAIZ08868; Thu, 4 Jul 2002 22:10:20 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Thu, 04 Jul 2002 22:09:52 +0900 (JST) Message-Id: <20020704.220952.104026566.iwasaki@jp.FreeBSD.org> To: shizukakudo_99@yahoo.com Cc: freebsd-current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: [acpi-jp 1661] Re: ASUS CUSL2 panic on acpi From: Mitsuru IWASAKI In-Reply-To: <20020704.120342.38720157.iwasaki@jp.FreeBSD.org> References: <20020702185518.87573.qmail@web11402.mail.yahoo.com> <20020703.142736.112630398.iwasaki@jp.FreeBSD.org> <20020704.120342.38720157.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 2.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) 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 My analysis was finished. Please try this patch. --- exfield.c- Thu Jul 4 21:54:24 2002 +++ exfield.c Thu Jul 4 21:55:02 2002 @@ -200,7 +200,7 @@ /* Handle both ACPI 1.0 and ACPI 2.0 Integer widths */ IntegerSize = sizeof (ACPI_INTEGER); - if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) + if (WalkState->MethodNode != NULL && WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) { /* * We are running a method that exists in a 32-bit ACPI table. BTW, this bug already fixed in 20020517 version. > > > acpi0: on motherboard > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > fault virtual address = 0x16 > > > fault code = supervisor read, page not present > > > instruction pointer = 0x8:0xc04f9aca > > > stack pointer = 0x10:0xc054ea14 > > > frame pointer = 0x10:0xc054ea34 > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1, def32 1, gran 1 > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > current process = 0 (swapper) > > > kernel: type 12 trap, code=0 > > > Stopped at AcpiExReadDataFromField+0x5a: movzbl 0x16(%eax),%eax > > > db> trace > > > AcpiExReadDataFromField(c0f00400,c25da200,c054ea50,c25e50c0,0) at AcpiExReadDataFromField+0x5a > > # if my understanding on i386 asm is correct, > I think this is at (exfield.c): > 203: if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) > where WalkState->MethodNode is NULL, this caused page fault. > > I'm waiting for further debug info. but I'll try to find where > WalkState->MethodNode suppose to be set... WalkState->MethodNode was initialized to NULL in AcpiDsInitAmlWalk() which called by AcpiDsExecuteArguments(). AcpiExReadDataFromField() assumes that WalkState->MethodNode always has a correct pointer. That's the problem, I think. ACPI_STATUS AcpiDsExecuteArguments ( ACPI_NAMESPACE_NODE *Node, ACPI_NAMESPACE_NODE *ScopeNode, UINT32 AmlLength, UINT8 *AmlStart) ... Status = AcpiDsInitAmlWalk (WalkState, Op, NULL, AmlStart, AmlLength, NULL, NULL, 3); ... AcpiDsInitAmlWalk ( ACPI_WALK_STATE *WalkState, ACPI_PARSE_OBJECT *Op, ACPI_NAMESPACE_NODE *MethodNode, UINT8 *AmlStart, UINT32 AmlLength, ACPI_OPERAND_OBJECT **Params, ACPI_OPERAND_OBJECT **ReturnObjDesc, UINT32 PassNumber) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:20:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F00937B400 for ; Thu, 4 Jul 2002 06:20:45 -0700 (PDT) Received: from web20909.mail.yahoo.com (web20909.mail.yahoo.com [216.136.226.231]) by mx1.FreeBSD.org (Postfix) with SMTP id 8490343E3B for ; Thu, 4 Jul 2002 06:20:44 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020704132044.7338.qmail@web20909.mail.yahoo.com> Received: from [218.108.159.238] by web20909.mail.yahoo.com via HTTP; Thu, 04 Jul 2002 06:20:44 PDT Date: Thu, 4 Jul 2002 06:20:44 -0700 (PDT) From: David Xu Subject: Re: Timeout and SMP race To: Bruce Evans Cc: julian@elischer.org, freebsd-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 in RELENG_4, when one calls callout_stop() (not nested in softclock execute path , I am not talking about this case), after it returns, he can believe that the callout is truely stopped, however in CURRENT, this assumption is false, now we must care if callout_stop() truely stopped the callout when it returned, this is all difference I see, we bring in this race which not exists in RELENG_4, see what hacking code put in kern_condvar.c and kern_synch.c in CURRENT source, this kind of problem is arising and knocking door. sorry, our company's smtp server refuse to relay my mail from home, I must send it from yahoo. :( -David Xu ----- Original Message ----- From: "Bruce Evans" To: "David Xu" Cc: "Julian Elischer" ; Sent: Thursday, July 04, 2002 7:02 PM Subject: Re: Timeout and SMP race > On Thu, 4 Jul 2002, David Xu wrote: > > > ----- Original Message ----- > > From: "Julian Elischer" > > To: "David Xu" > > Cc: > > Sent: Thursday, July 04, 2002 4:36 PM > > Subject: Re: Timeout and SMP race > > > > > > > if another thread other than softclock itself is calling callout_stop(), > > and callout_stop() detected that softclock is currently running the > > callout, it should wait until softclock finishes the work, then return. > > softclock() intentionally releases callout_lock() to allow other processes > to manipulate callouts. What is the race exactly? Concurrent calls to > softclock() seem to be possible but seem to be handled correctly (internal > locking prevents problems). Well, I can see one race in softclock(): > > % c_func = c->c_func; > % c_arg = c->c_arg; > % c_flags = c->c_flags; > > This caches some values, as is needed since the 'c' pointer may become > invalid after we release the lock ... but the things pointed to may become > invalid too. > > % c->c_func = NULL; > % if (c->c_flags & CALLOUT_LOCAL_ALLOC) { > % c->c_flags = CALLOUT_LOCAL_ALLOC; > % SLIST_INSERT_HEAD(&callfree, c, > % c_links.sle); > % } else > % c->c_flags &= ~CALLOUT_PENDING; > % mtx_unlock_spin(&callout_lock); > > callout_stop() may stop 'c' here. It won't do much, since we have already > set c->c_func to NULL, but its caller may want the callout actually stopped > so that it can do things like unloading the old c->c_func. > > % if ((c_flags & CALLOUT_MPSAFE) == 0) > % mtx_lock(&Giant); > % c_func(c_arg); > > This calls through a possibly-invalid function pointer. > > % if ((c_flags & CALLOUT_MPSAFE) == 0) > % mtx_unlock(&Giant); > % mtx_lock_spin(&callout_lock); > > This seems to be an old bug. In RELENG_4, splsoftclock() gives a more > global lock, but there is nothing to prevent callout_stop() being run > at splsoftclock(). In fact, it must be able to run when called nested > from inside softclock(), since it might be called from the handler. > Waiting in callout_stop() for softclock() to finish would deadlock in > this case. It's interesting that this case is (always?) avoided in > untimeout() by not calling callout_stop() when c->c_func == NULL. > > softclock() can't do anything about c->c_func going away after it is > called. Clients must somehow avoid killing it. > > I think c->c_func rarely goes away, and the race that you noticed is > lost more often. > > Bruce > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:24:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5E6F37B400 for ; Thu, 4 Jul 2002 06:24:39 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9FB343E09 for ; Thu, 4 Jul 2002 06:24:38 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 JAA00118; Thu, 4 Jul 2002 09:24:38 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g64DO8227187; Thu, 4 Jul 2002 09:24:08 -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: <15652.19576.327299.996758@grasshopper.cs.duke.edu> Date: Thu, 4 Jul 2002 09:24:08 -0400 (EDT) To: Chuck Robey Cc: Subject: Re: Recommended MP development machines... In-Reply-To: <20020703233926.N66398-100000@april.chuckr.org> References: <20020703202553.A12306@dragon.nuxi.com> <20020703233926.N66398-100000@april.chuckr.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 Chuck Robey writes: > > The main difference in the updated chipset is the fact that the 64 bit PCI > slots now run at double-speed, giving double the throughput. No change Most motherboards which support 64-bit/66MHz PCI slots can't run them anywhere near the theoretical limit. So its more like a 50% improvement than 100% improvement. For objective comparisions of chipsets see http://www.conservativecomputer.com/myrinet/perf.html Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:28:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A9A37B400 for ; Thu, 4 Jul 2002 06:28:18 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB0D643E31 for ; Thu, 4 Jul 2002 06:28:17 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g64DSBTr020463; Thu, 4 Jul 2002 09:28:11 -0400 (EDT) Date: Thu, 4 Jul 2002 09:28:11 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Neal Fachan , Terry Lambert , Garrett Wollman , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: additional queue macro In-Reply-To: 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 On Wed, 3 Jul 2002, Julian Elischer wrote: > On Wed, 3 Jul 2002, Neal Fachan wrote: > > > We've got local changes (which I've attached) where the name is > > *_FOREACH_REMOVE. We didn't add reverse removable iterators. Also, the > > temp variable is the second argument. I can't think of a way of doing it > > without having the externally declare the temporary variable. > > > A I like it and you've even done thge man page.. > > *_FOREACH_REMOVE however suggests that it is going to try remove > something.. Instead of potentially changing the existing *_FOREACH behaviour, why not just add *_FOREACH_CHECKED or *_FOREACH_PEDANTIC that adds the desired behaviour. Or *_FOREACH_DEBUG... -- Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:31:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17FE137B400 for ; Thu, 4 Jul 2002 06:31:11 -0700 (PDT) Received: from netscum.dyndns.dk (dclient217-162-144-72.hispeed.ch [217.162.144.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADD1A43E31 for ; Thu, 4 Jul 2002 06:31:09 -0700 (PDT) (envelope-from bounce@netscum.dyndns.dk) Received: from netscum.dyndns.dk (localhost [127.0.0.1]) by netscum.dyndns.dk (8.12.2/8.12.2) with ESMTP id g64DV7nc072419 for ; Thu, 4 Jul 2002 15:31:07 +0200 (CEST) (envelope-from bounce@netscum.dyndns.dk) Received: (from root@localhost) by netscum.dyndns.dk (8.12.2/8.12.2/Submit) id g64DV6jO072418; Thu, 4 Jul 2002 15:31:06 +0200 (CEST) Date: Thu, 4 Jul 2002 15:31:06 +0200 (CEST) Message-Id: <200207041331.g64DV6jO072418@netscum.dyndns.dk> From: BOUWSMA Beery Organization: Men not wearing any pants that dont shave To: freebsd-current@freebsd.org References: <200206271409.g5RE9sYk065255@netscum.dyndns.dk> Subject: Re: duplicate includes in kdump/ioctl.c ? X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: CABAL MODEM (all hail CABAL) X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No 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 Sorry to answer myself, but after a bit of free time to reflect on this, I may as well talk back at myself. I wrote: > Am I the only one getting duplicated #include lines in the generated > ioctl.c file, created as part of building usr.bin/kdump? YES! > 27 #include > 28 #include > 29 #include > 30 #include > 31 #include > 32 #include > However, there seem to be significant differences between the two > generated ioctl.c files (including another duplicated disklabel.h line). Yow. A clue, that points to: > ... Or might the > fact that I'm using a unionfs mount over /usr/src have something to > do with it (since disklabel.h appears twice with `ls' since I needed > to hack it in the upper unionfs layer)... It is. There's a shadow `scsi' directory that appears under -current (at least, that I'm still using) with a unionfs mount under `ls' twice, and gets traversed twice as well by the `find' that I should have noted had I had the time to pay attention to the mkioctls innards, leading to the duplicate inclusions. So I've added a `sort -u' into the `find' pipeline in hopes of quenching the duplicated includes that appear due to this imperfection of the unionfs. We'll see how it goes... The only way anyone else *might* see this is if they too do a unionfs mount, to keep an unmolested /usr/src around while still allowing one to hack on bits and pieces of it with local customizations, like my hack to mkioctls... Sorry for the noise, but in case anyone else might see such a thing, I thought I'd put this into the archives And, in fact, I've successfully built `kdump' as part of my normal `buildworld', so it seems as if I may even be well on the way to a successful build of -current. Yay. thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:39:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D39D37B400 for ; Thu, 4 Jul 2002 06:39:48 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28A1243E09 for ; Thu, 4 Jul 2002 06:39:47 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.3/8.12.3) with ESMTP id g64DcgQJ045124; Thu, 4 Jul 2002 09:38:42 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.3/8.12.3/Submit) with ESMTP id g64DcfhJ045121; Thu, 4 Jul 2002 09:38:41 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 4 Jul 2002 09:38:41 -0400 (EDT) From: Kenneth Culver To: Julian Elischer Cc: FreeBSD current users Subject: Re: KSE status. In-Reply-To: Message-ID: <20020704093821.P45120-100000@alpha.yumyumyum.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 Does this wired memory problem only happen on SMP systems, or is it happening across the board? Ken On Wed, 3 Jul 2002, Julian Elischer wrote: > > Well it's all fun and games her at KSE central.. > We have a set of cascading hidden bugs.. > > bug 1 hides bug 2 hides bug 3 > > the current state of play: > > the system works well for a while however there is a leak in > the system that gradually runs the system out memory. > the wired memory count grows with time. My test system presently has > 241MB of Wired memory out of a 512M system. > > This didn't affect systems before today because the code was hidden by > another bug.. > that wasn't evident because of another bug.. etc.. > still I think I am making progress. Just remember to reboot your system > whenever your wired memory gets too high :-) > > > > 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 Thu Jul 4 6:52:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08C3837B400 for ; Thu, 4 Jul 2002 06:52:29 -0700 (PDT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76AF343E52 for ; Thu, 4 Jul 2002 06:52:28 -0700 (PDT) (envelope-from mariog@tomservo.cc) Received: from fwd03.sul.t-online.de by mailout07.sul.t-online.com with smtp id 17Q71x-0003Cs-08; Thu, 04 Jul 2002 15:52:21 +0200 Received: from apimail.dns2go.com (520095760089-0001@[80.133.139.178]) by fmrl03.sul.t-online.com with esmtp id 17Q72G-0K0ziaC; Thu, 4 Jul 2002 15:52:40 +0200 Received: from tomservo.cc (sgi.api.de [192.168.42.246]) by apimail.dns2go.com (Postfix) with ESMTP id B67C3339D9E; Thu, 4 Jul 2002 15:52:32 +0200 (CEST) Message-ID: <3D2452F7.9000300@tomservo.cc> Date: Thu, 04 Jul 2002 15:51:51 +0200 From: Mario Goebbels User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kenneth Culver Cc: Julian Elischer , FreeBSD current users Subject: Re: KSE status. References: <20020704093821.P45120-100000@alpha.yumyumyum.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 520095760089-0001@t-dialin.net 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 > > >Does this wired memory problem only happen on SMP systems, or is it >happening across the board? > >Ken > I'm running a uniproc. box at work with -CURRENT and over 4-5hrs, wired grew from 50megs (when I first time checked) to 141megs (now). Dunno if this normal, but it has kept growing. -mg >>Well it's all fun and games her at KSE central.. >>We have a set of cascading hidden bugs.. >> >>bug 1 hides bug 2 hides bug 3 >> >>the current state of play: >> >>the system works well for a while however there is a leak in >>the system that gradually runs the system out memory. >>the wired memory count grows with time. My test system presently has >>241MB of Wired memory out of a 512M system. >> >>This didn't affect systems before today because the code was hidden by >>another bug.. >>that wasn't evident because of another bug.. etc.. >>still I think I am making progress. Just remember to reboot your system >>whenever your wired memory gets too high :-) >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:54:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7371C37B400 for ; Thu, 4 Jul 2002 06:54:34 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2A5243E31 for ; Thu, 4 Jul 2002 06:54:33 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.3/8.12.3) with ESMTP id g64DrTQJ045172; Thu, 4 Jul 2002 09:53:29 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.3/8.12.3/Submit) with ESMTP id g64DrSh7045169; Thu, 4 Jul 2002 09:53:28 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 4 Jul 2002 09:53:28 -0400 (EDT) From: Kenneth Culver To: Mario Goebbels Cc: Julian Elischer , FreeBSD current users Subject: Re: KSE status. In-Reply-To: <3D2452F7.9000300@tomservo.cc> Message-ID: <20020704095243.T45120-100000@alpha.yumyumyum.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 > I'm running a uniproc. box at work with -CURRENT and over 4-5hrs, wired > grew from 50megs (when I first time checked) to 141megs (now). Dunno if > this normal, but it has kept growing. OK, I don't see it happening here on my uniproc box, I havn't tried on my SMP box, I guess my sources aren't new enough. ;-) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 6:55:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C36A637B400 for ; Thu, 4 Jul 2002 06:55:07 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE5EF43E3B for ; Thu, 4 Jul 2002 06:55:06 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 JAA00613 for ; Thu, 4 Jul 2002 09:55:06 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g64Dsa127222; Thu, 4 Jul 2002 09:54:36 -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: <15652.21404.305333.627537@grasshopper.cs.duke.edu> Date: Thu, 4 Jul 2002 09:54:36 -0400 (EDT) To: freebsd-current@freebsd.org Subject: Re: Recommended MP development machines... In-Reply-To: <200207040243.g642hMpb054743@mail.meer.net> References: <200207040243.g642hMpb054743@mail.meer.net> 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 George V. Neville-Neil writes: > Hi, > > I know everyone says "they all work" but i'd like some recommendations on > MP machines for -CURRENT work. I'll be ordering one this week. > I'm in the market for a new SMP x86 workstation to replace my aging alpha desktop. What's the state of ACPI (or apm?) support for SMP machines on current? I'd like to be able to suspend the machine to reduce heat output and power consumption. Is it currently possible to do the moral equivalent of what a laptop's APM bios might call "suspend to memory on an SMP desktop?". Eg, all fans/disks stop spinning, CPUs halt, power consumption goes down to 5-10W, and the memory contents continue to be refreshed until you wake the machine up? Also, what's a commonly available quiet case? The alpha's got so many fans that I think I'm starting to go deaf and I'd like a much less noisy machine. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:12:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8126837B400 for ; Thu, 4 Jul 2002 07:12:17 -0700 (PDT) Received: from www.contentmedia.de (www.contentmedia.de [213.61.138.91]) by mx1.FreeBSD.org (Postfix) with SMTP id B927843E09 for ; Thu, 4 Jul 2002 07:12:16 -0700 (PDT) (envelope-from recht@contentmedia.de) Received: (qmail 3891 invoked from network); 4 Jul 2002 14:10:49 -0000 Received: from unknown (HELO leeloo.intern.geht.de) (217.227.197.213) by www.contentmedia.de with SMTP; 4 Jul 2002 14:10:49 -0000 Subject: Re: panic with today's pmap From: Marc Recht To: Julian Elischer Cc: current@FreeBSD.ORG In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 04 Jul 2002 16:12:14 +0200 Message-Id: <1025791934.730.1.camel@leeloo.intern.geht.de> Mime-Version: 1.0 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 > try a new vm_glue.c as well. > ( 1.140) Yes, this works. Thanks! Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:20:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2BA337B400; Thu, 4 Jul 2002 07:20:45 -0700 (PDT) Received: from ns0.seaman.net (ns0.seaman.net [168.215.64.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B98043E31; Thu, 4 Jul 2002 07:20:44 -0700 (PDT) (envelope-from dick@seaman.org) Received: from tbird.internal.seaman.net (tbird [192.168.10.12]) by ns0.seaman.net (8.12.5/8.12.3) with ESMTP id g64EKdsn020257; Thu, 4 Jul 2002 09:20:39 -0500 (CDT) (envelope-from dick@seaman.org) Received: (from dick@localhost) by tbird.internal.seaman.net (8.11.6/8.11.6) id g64EKcP14497; Thu, 4 Jul 2002 09:20:38 -0500 Date: Thu, 4 Jul 2002 09:20:38 -0500 From: "Richard Seaman, Jr." To: "Joel M. Baldwin" Cc: freebsd-current@FreeBSD.ORG, luigi@FreeBSD.ORG Subject: Re: natd core dumping with bus error Message-ID: <20020704092038.M3283@seaman.org> Mail-Followup-To: "Richard Seaman, Jr." , "Joel M. Baldwin" , freebsd-current@FreeBSD.ORG, luigi@freebsd.org References: <237537741.1025633076@[192.168.1.20]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <237537741.1025633076@[192.168.1.20]>; from qumqats@outel.org on Tue, Jul 02, 2002 at 06:04:36PM -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 Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote: > > > Something has messed up natd. If I don't have the > punch_fw option in the /etc/natd.conf file it eventuially > core dumps with a bus error. I think this started JUST > BEFORE the KSE commit. Yes, I've seen the same thing on a pre-KSE kernel. The error occurs in PunchFWHole in alias_db.c in libalias. Reverting the following commit seems to fix it (I haven't had a chance to investigate further): luigi 2002/06/27 16:02:18 PDT Modified files: sbin/ipfw Makefile sys/netinet ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfw ipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr. email: dick@seaman.org 5182 N. Maple Lane phone: 262-367-5450 Nashotah WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:34: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 414A637B400 for ; Thu, 4 Jul 2002 07:33:59 -0700 (PDT) Received: from csharp.dyndns.org (pD9552B21.dip.t-dialin.net [217.85.43.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E3AB43E31 for ; Thu, 4 Jul 2002 07:33:58 -0700 (PDT) (envelope-from mephisto@csharp.dyndns.org) Received: from mephisto by csharp.dyndns.org with local (Exim 4.05) id 17Q7hc-0003Se-00 for current@FreeBSD.ORG; Thu, 04 Jul 2002 16:35:24 +0200 Date: Thu, 4 Jul 2002 16:35:23 +0200 From: Christopher Sharp To: current@FreeBSD.ORG Subject: Re: panic: vm_page_free: freeing wired page Message-ID: <20020704143523.GA695@web.de> Mail-Followup-To: current@FreeBSD.ORG References: <20020704093056.GA614@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.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 After the change to vm_glue.c the problem seems to be gone ... -- Any time things appear to be going better, you have overlooked something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:36:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4D6B37B400; Thu, 4 Jul 2002 07:36:32 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65AF043E09; Thu, 4 Jul 2002 07:36:22 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g64EZ7P74349; Thu, 4 Jul 2002 17:35:07 +0300 (EEST) (envelope-from ru) Date: Thu, 4 Jul 2002 17:35:06 +0300 From: Ruslan Ermilov To: "Richard Seaman, Jr." Cc: "Joel M. Baldwin" , Luigi Rizzo , current@FreeBSD.org Subject: Re: natd core dumping with bus error Message-ID: <20020704143506.GA72689@sunbay.com> References: <237537741.1025633076@[192.168.1.20]> <20020704092038.M3283@seaman.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <20020704092038.M3283@seaman.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 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote: > On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote: > >=20 > >=20 > > Something has messed up natd. If I don't have the > > punch_fw option in the /etc/natd.conf file it eventuially > > core dumps with a bus error. I think this started JUST > > BEFORE the KSE commit. >=20 > Yes, I've seen the same thing on a pre-KSE kernel. The error > occurs in PunchFWHole in alias_db.c in libalias. Reverting > the following commit seems to fix it (I haven't had a chance > to investigate further): >=20 I will look into it later this week if Luigi does not beat me to it. > luigi 2002/06/27 16:02:18 PDT >=20 > Modified files: > sbin/ipfw Makefile=20 > sys/netinet ip_dummynet.c ip_fw.h=20 > sys/conf files=20 > lib/libalias alias_db.c=20 > Added files: > sbin/ipfw ipfw2.c=20 > sys/netinet ip_fw2.c=20 > Log: > The new ipfw code. > =20 >=20 >=20 > --=20 > Richard Seaman, Jr. email: dick@seaman.org > 5182 N. Maple Lane phone: 262-367-5450 > Nashotah WI 53058 fax: 262-367-5852 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message --=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 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9JF0aUkv4P6juNwoRAiN5AJ48CGGytt+a2XJ99SmHPIxE7bwyPwCeJvnD LScyChJaTWQnOsNaWDib64U= =7z4V -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:53:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE74A37B400 for ; Thu, 4 Jul 2002 07:53:13 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8225543E09 for ; Thu, 4 Jul 2002 07:53:13 -0700 (PDT) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [66.126.108.132] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare via secured & encrypted transport (TLS); Thu, 04 Jul 2002 08:53:14 -0600 Message-ID: <3D24620A.2030303@hotmail.com> Date: Thu, 04 Jul 2002 07:56:10 -0700 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020617 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: memory leak in -current. References: 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 Julian Elischer wrote: > I've tracked it down to my losing 1 page for every thread that is started. > > if I start a process with 6 threads, I lose 6 x 4k. > if I start a single threaded process I lose 4k. The problem seems fixed at this end after the vm_glue update from today, July 4. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 7:57:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADF5837B400 for ; Thu, 4 Jul 2002 07:57:14 -0700 (PDT) Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE89243E09 for ; Thu, 4 Jul 2002 07:57:10 -0700 (PDT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Thu, 04 Jul 2002 07:57:05 -0700 Received: from adsl-64-173-182-155.dsl.mtry01.pacbell.net (adsl-64-173-182-155.dsl.mtry01.pacbell.net [64.173.182.155]) as user eculp@encontacto.net@encontacto.net by Mail.EnContacto.Net with HTTP; Thu, 4 Jul 2002 07:57:05 -0700 Message-ID: <1025794625.3d24624138e07@Mail.EnContacto.Net> Date: Thu, 4 Jul 2002 07:57:05 -0700 From: Edwin Culp To: Kenneth Culver Cc: Mario Goebbels , Julian Elischer , FreeBSD current users Subject: Re: KSE status. References: <20020704095243.T45120-100000@alpha.yumyumyum.org> In-Reply-To: <20020704095243.T45120-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Priority: 3 (Normal) X-Originating-IP: 64.173.182.155 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 Quoting Kenneth Culver : | > I'm running a uniproc. box at work with -CURRENT and over 4-5hrs, wired | > grew from 50megs (when I first time checked) to 141megs (now). Dunno if | > this normal, but it has kept growing. | | OK, I don't see it happening here on my uniproc box, I havn't tried on my | SMP box, I guess my sources aren't new enough. ;-) | For informational purposes: top on one of my machines with 512M memory shows: Mem: 213M Active, 182M Inact, 3038M Wired, 19M Cache, 61M Buf, 2756K Free Swap: 1024M Total, 68K Used, 1024M Free There is something that I just don't understand with the 3038M Wired? my laptop with 256M is now showing an hour after a reboot. Mem: 157M Active, 36M Inact, 512M Wired, 10M Cache, 35M Buf, 11M Free Swap: 1024M Total, 1024M Free both with yesterday's build - kernel and world. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 8:31:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18BB737B400 for ; Thu, 4 Jul 2002 08:31:43 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 781D243E09 for ; Thu, 4 Jul 2002 08:31:42 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g64FUwE48481; Thu, 4 Jul 2002 10:30:58 -0500 (CDT) (envelope-from jlemon) Date: Thu, 4 Jul 2002 10:30:58 -0500 (CDT) From: Jonathan Lemon Message-Id: <200207041530.g64FUwE48481@prism.flugsvamp.com> To: bsddiy@yahoo.com, Bruce Evans , current@freebsd.org Subject: Re: Timeout and SMP race X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: 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 article you write: >in RELENG_4, when one calls callout_stop() (not nested in softclock execute >path >, I am not talking about this case), after it returns, he can believe that the >callout is truely stopped, however in CURRENT, this assumption is false, now we > >must care if callout_stop() truely stopped the callout when it returned, this >is all difference I see, we bring in this race which not exists in RELENG_4, >see what hacking code put in kern_condvar.c and kern_synch.c in CURRENT source, I don't believe this is true. There is a corresponding race in -stable, where the spl() level is dropped before performing the callout, thus allowing either a call to callout_stop() or callout_reset() to come in immediately before the callout is actually made. The callout function is responsible for checking to see if it has lost the race, and perform the appropriate action. This is done with the CALLOUT_PENDING and CALLOUT_ACTIVE flags: s = splnet(); if (callout_pending(tp->tt_delack) || !callout_active(tp->tt_delack)) { splx(s); return; } callout_deactivate(tp->tt_delack); If 'CALLOUT_PENDING' is set, then we lost a race with callout_reset(), and should not perform the callout. If 'CALLOUT_ACTIVE' is clear, then we lost a race with callout_stop(). Either way, on both -current and -stable, you cannot assume that the timer callback is completely gone immediately after calling callout_stop(). -- Jonathan >----- Original Message ----- >From: "Bruce Evans" >To: "David Xu" >Cc: "Julian Elischer" ; >Sent: Thursday, July 04, 2002 7:02 PM >Subject: Re: Timeout and SMP race > > >> On Thu, 4 Jul 2002, David Xu wrote: >> >> > ----- Original Message ----- >> > From: "Julian Elischer" >> > To: "David Xu" >> > Cc: >> > Sent: Thursday, July 04, 2002 4:36 PM >> > Subject: Re: Timeout and SMP race >> > > > >> > >> > if another thread other than softclock itself is calling callout_stop(), >> > and callout_stop() detected that softclock is currently running the >> > callout, it should wait until softclock finishes the work, then return. >> >> softclock() intentionally releases callout_lock() to allow other processes >> to manipulate callouts. What is the race exactly? Concurrent calls to >> softclock() seem to be possible but seem to be handled correctly (internal >> locking prevents problems). Well, I can see one race in softclock(): >> >> % c_func = c->c_func; >> % c_arg = c->c_arg; >> % c_flags = c->c_flags; >> >> This caches some values, as is needed since the 'c' pointer may become >> invalid after we release the lock ... but the things pointed to may become >> invalid too. >> >> % c->c_func = NULL; >> % if (c->c_flags & CALLOUT_LOCAL_ALLOC) { >> % c->c_flags = CALLOUT_LOCAL_ALLOC; >> % SLIST_INSERT_HEAD(&callfree, c, >> % c_links.sle); >> % } else >> % c->c_flags &= ~CALLOUT_PENDING; >> % mtx_unlock_spin(&callout_lock); >> >> callout_stop() may stop 'c' here. It won't do much, since we have already >> set c->c_func to NULL, but its caller may want the callout actually stopped >> so that it can do things like unloading the old c->c_func. >> >> % if ((c_flags & CALLOUT_MPSAFE) == 0) >> % mtx_lock(&Giant); >> % c_func(c_arg); >> >> This calls through a possibly-invalid function pointer. >> >> % if ((c_flags & CALLOUT_MPSAFE) == 0) >> % mtx_unlock(&Giant); >> % mtx_lock_spin(&callout_lock); >> >> This seems to be an old bug. In RELENG_4, splsoftclock() gives a more >> global lock, but there is nothing to prevent callout_stop() being run >> at splsoftclock(). In fact, it must be able to run when called nested >> from inside softclock(), since it might be called from the handler. >> Waiting in callout_stop() for softclock() to finish would deadlock in >> this case. It's interesting that this case is (always?) avoided in >> untimeout() by not calling callout_stop() when c->c_func == NULL. >> >> softclock() can't do anything about c->c_func going away after it is >> called. Clients must somehow avoid killing it. >> >> I think c->c_func rarely goes away, and the race that you noticed is >> lost more often. >> >> Bruce >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > >__________________________________________________ >Do You Yahoo!? >Sign up for SBC Yahoo! Dial - First Month Free >http://sbc.yahoo.com > >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 Thu Jul 4 8:40:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F184A37B407 for ; Thu, 4 Jul 2002 08:40:14 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0137343E09 for ; Thu, 4 Jul 2002 08:40:14 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704154012.SXLM903.sccrmhc03.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 15:40:12 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA08629; Thu, 4 Jul 2002 08:40:03 -0700 (PDT) Date: Thu, 4 Jul 2002 08:40:01 -0700 (PDT) From: Julian Elischer To: Kenneth Culver Cc: FreeBSD current users Subject: Re: KSE status. In-Reply-To: <20020704093821.P45120-100000@alpha.yumyumyum.org> 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 On Thu, 4 Jul 2002, Kenneth Culver wrote: > Does this wired memory problem only happen on SMP systems, or is it > happening across the board? > > Ken > Uniprocessor had the bug too. (had... as in I fixed it..) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 8:40:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DA0A37B408 for ; Thu, 4 Jul 2002 08:40:23 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EC4343E09 for ; Thu, 4 Jul 2002 08:40:22 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704154020.SXNL903.sccrmhc03.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 15:40:20 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA08618; Thu, 4 Jul 2002 08:37:13 -0700 (PDT) Date: Thu, 4 Jul 2002 08:37:11 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: Neal Fachan , Terry Lambert , Garrett Wollman , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: additional queue macro In-Reply-To: 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 that was teh plan... we're just discussing the name.. TAILQ_FOREACH_SAFE ? On Thu, 4 Jul 2002, Daniel Eischen wrote: > On Wed, 3 Jul 2002, Julian Elischer wrote: > > On Wed, 3 Jul 2002, Neal Fachan wrote: > > > > > We've got local changes (which I've attached) where the name is > > > *_FOREACH_REMOVE. We didn't add reverse removable iterators. Also, the > > > temp variable is the second argument. I can't think of a way of doing it > > > without having the externally declare the temporary variable. > > > > > A I like it and you've even done thge man page.. > > > > *_FOREACH_REMOVE however suggests that it is going to try remove > > something.. > > Instead of potentially changing the existing *_FOREACH behaviour, > why not just add *_FOREACH_CHECKED or *_FOREACH_PEDANTIC that > adds the desired behaviour. Or *_FOREACH_DEBUG... > > -- > Dan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 8:42:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65D7237B400 for ; Thu, 4 Jul 2002 08:42:46 -0700 (PDT) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id D20A543E31 for ; Thu, 4 Jul 2002 08:42:40 -0700 (PDT) (envelope-from mariog@tomservo.cc) Received: from fwd03.sul.t-online.de by mailout11.sul.t-online.com with smtp id 17Q8kh-0004iC-00; Thu, 04 Jul 2002 17:42:39 +0200 Received: from apimail.dns2go.com (520095760089-0001@[217.224.156.233]) by fmrl03.sul.t-online.com with esmtp id 17Q8lB-2FN2rgC; Thu, 4 Jul 2002 17:43:09 +0200 Received: from tomservo.cc (sgi.api.de [192.168.42.246]) by apimail.dns2go.com (Postfix) with ESMTP id 9DC3133A0D6 for ; Thu, 4 Jul 2002 17:43:14 +0200 (CEST) Message-ID: <3D246CE9.4090607@tomservo.cc> Date: Thu, 04 Jul 2002 17:42:33 +0200 From: Mario Goebbels User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Subject: Wired mem fun! Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 520095760089-0001@t-dialin.net 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 4th July 5pm CET, with world and kernel from 11am 3rd July, after a couple of hours runtime, doing mainly xchat and Mozilla, I got these stats: Mem: 73M Active, 221M Inact, 210M Wired, 1128K Cache, 61M Buf, 136M Free Swap: 512M Total, 512M Free I started a buildworld, then I aborted somewhere in buildworld when gcc was being compiled. That were the stats then: Mem: 82M Active, 284M Inact, 873M Wired, 29M Cache, 61M Buf, 17M Free Swap: 512M Total, 512M Free ( I aborted coz my holidays start right now. :) ) But the buildworld increased Wired about 663megs, I don't think this is normal, right? I will restart a buildworld over ssh when I'm home with the new vm-glue.c, so see if it raises that high again. Cheers -mg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 8:54: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0537A37B400 for ; Thu, 4 Jul 2002 08:54:00 -0700 (PDT) Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81B0A43E31 for ; Thu, 4 Jul 2002 08:53:59 -0700 (PDT) (envelope-from mariog@tomservo.cc) Received: from fwd03.sul.t-online.de by mailout01.sul.t-online.com with smtp id 17Q8vd-0007Ij-05; Thu, 04 Jul 2002 17:53:57 +0200 Received: from apimail.dns2go.com (520095760089-0001@[217.224.156.233]) by fmrl03.sul.t-online.com with esmtp id 17Q8w1-0DLyG8C; Thu, 4 Jul 2002 17:54:21 +0200 Received: from tomservo.cc (sgi.api.de [192.168.42.246]) by apimail.dns2go.com (Postfix) with ESMTP id 6C97633A0D6; Thu, 4 Jul 2002 17:54:26 +0200 (CEST) Message-ID: <3D246F89.8010003@tomservo.cc> Date: Thu, 04 Jul 2002 17:53:45 +0200 From: Mario Goebbels User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mario Goebbels Cc: current@freebsd.org Subject: Re: Wired mem fun! References: <3D246CE9.4090607@tomservo.cc> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 520095760089-0001@t-dialin.net 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 a second thought, how does it accumulate 870megs of wired memory on a box that has only 512megs and the swap file hasn't even been touched? Maybe there's just a profiling counter boken? Or do I misinterpret the concept of wired memory? Anyway, cheers, -mg > 4th July 5pm CET, with world and kernel from 11am 3rd July, after a > couple of hours runtime, doing mainly xchat and Mozilla, I got these > stats: > > Mem: 73M Active, 221M Inact, 210M Wired, 1128K Cache, 61M Buf, 136M Free > Swap: 512M Total, 512M Free > > I started a buildworld, then I aborted somewhere in buildworld when > gcc was being compiled. That were the stats then: > > Mem: 82M Active, 284M Inact, 873M Wired, 29M Cache, 61M Buf, 17M Free > Swap: 512M Total, 512M Free > > *snip* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 8:59:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD0CB37B400; Thu, 4 Jul 2002 08:59:21 -0700 (PDT) Received: from tpts5.seed.net.tw (tpts5.seed.net.tw [139.175.55.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88B7543E09; Thu, 4 Jul 2002 08:59:17 -0700 (PDT) (envelope-from is88232@cis.nctu.edu.tw) Received: from [61.59.241.52] (helo=cis.nctu.edu.tw) by tpts5.seed.net.tw with esmtp (Seednet MTA build 20010831) id 17Q8zq-0006y9-00; Thu, 04 Jul 2002 23:58:18 +0800 Message-ID: <3D247210.4030407@cis.nctu.edu.tw> Date: Fri, 05 Jul 2002 00:04:32 +0800 From: Chung-Lin Tang User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.7) Gecko/20011222 X-Accept-Language: en-us MIME-Version: 1.0 To: Chuck Robey Cc: David O'Brien , "George V. Neville-Neil" , freebsd-current@FreeBSD.ORG Subject: Re: Recommended MP development machines... References: <20020703233926.N66398-100000@april.chuckr.org> 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 Chuck Robey wrote: >On Wed, 3 Jul 2002, David O'Brien wrote: > >>On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote: >> >>> I know everyone says "they all work" but i'd like some recommendations on >>>MP machines for -CURRENT work. I'll be ordering one this week. >>> >>There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness). >>http://www.tyan.com/products/html/thunderk7.html. It comes in multiple >>flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit >>PCI, 1 AGP version. You can cheap out and not get the non-SCSI S2462NG >>model. Match this bad-boy up with a pair of fast Athlon `MP' (not `XP') >>CPU's and it is a totally solid system. Various FreeBSD committers also >>have this system. >> >>There is a newer [more economic] version called the Thunder K7X. >>http://www.tyan.com/products/html/thunderk7x.html >> > >"more economic" is a poor way to describe it, seeing as it has all the >features, plus (1) an updated version of the AMD mp chipset and (2) a >fixed onboard usb port. The K7 had a broken on-board usb (the AMD >chipset had a PCI contention bug for the usb port, so the tin back panel >of the board blocked out the usb, and the K7 came with a PCI usb card, >which ate up one of your PCI slots. The K7X has a repaired on-board usb, >so you get that PCI slot back. > That was a problem with the 760MPX chipset, the Thunder K7 uses the earlier 760MP which doesn't have that problem. > > >The main difference in the updated chipset is the fact that the 64 bit PCI >slots now run at double-speed, giving double the throughput. No change >for the 32 bit PCI slots. At least for me, the main usage of the 64 bit >slot would be the disk; seeing as both the K7 and the K7X can be had with >a very nice dual channel Adaptec Ultra160 controller, which means you >don't use the 64 bit PCI slot for disk, that kills that. Added cost >for the controller is about $100, not a bad deal. > >I think the K7 had only AGP; the K7X has AGP-Pro; doesn't mean much yet, >but if you're a gaming maven, maybe it'll be important pretty quickly now. > Both has AGP-Pro. > > >---------------------------------------------------------------------------- >Chuck Robey | Interests include C & Java programming, FreeBSD, >chuckr@chuckr.org | electronics, communications, and signal processing. > >New Year's Resolution: I will not sphroxify gullible people into looking up >fictitious words in the dictionary. >---------------------------------------------------------------------------- > > >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 Thu Jul 4 9: 0:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D76FE37B447 for ; Thu, 4 Jul 2002 09:00:17 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8359A43E09 for ; Thu, 4 Jul 2002 09:00:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704160017.MMAW24728.rwcrmhc51.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 16:00:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id IAA08660; Thu, 4 Jul 2002 08:43:43 -0700 (PDT) Date: Thu, 4 Jul 2002 08:43:41 -0700 (PDT) From: Julian Elischer To: Edwin Culp Cc: Kenneth Culver , Mario Goebbels , FreeBSD current users Subject: Re: KSE status. In-Reply-To: <1025794625.3d24624138e07@Mail.EnContacto.Net> 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 don't trust yesterday's build :-/ On Thu, 4 Jul 2002, Edwin Culp wrote: > both with yesterday's build - kernel and world. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 9: 6:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F25F537B400 for ; Thu, 4 Jul 2002 09:06:17 -0700 (PDT) Received: from encontacto.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B45543E4A for ; Thu, 4 Jul 2002 09:06:10 -0700 (PDT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Thu, 04 Jul 2002 09:05:02 -0700 Received: from adsl-64-173-182-155.dsl.mtry01.pacbell.net (adsl-64-173-182-155.dsl.mtry01.pacbell.net [64.173.182.155]) as user eculp@encontacto.net@encontacto.net by Mail.EnContacto.Net with HTTP; Thu, 4 Jul 2002 09:05:02 -0700 Message-ID: <1025798702.3d24722e2d91d@Mail.EnContacto.Net> Date: Thu, 4 Jul 2002 09:05:02 -0700 From: Edwin Culp To: current@freebsd.org Subject: Re: Wired mem fun! References: <3D246CE9.4090607@tomservo.cc> In-Reply-To: <3D246CE9.4090607@tomservo.cc> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Priority: 3 (Normal) X-Originating-IP: 64.173.182.155 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 Quoting Mario Goebbels : | 4th July 5pm CET, with world and kernel from 11am 3rd July, after a | couple of hours runtime, doing mainly xchat and Mozilla, I got these stats: | | Mem: 73M Active, 221M Inact, 210M Wired, 1128K Cache, 61M Buf, 136M Free | Swap: 512M Total, 512M Free | | I started a buildworld, then I aborted somewhere in buildworld when gcc | was being compiled. That were the stats then: | | Mem: 82M Active, 284M Inact, 873M Wired, 29M Cache, 61M Buf, 17M Free | Swap: 512M Total, 512M Free | | ( I aborted coz my holidays start right now. :) ) | But the buildworld increased Wired about 663megs, I don't think this is | normal, right? I will restart a buildworld over ssh when I'm home with | the new vm-glue.c, so see if it raises that high again. I was over 3000M in wired on one machine, cvsup'd to get the new vm_glue.c and friends, recompiled the kernel, rebooted and am now doing a brand new cvsup/make world/kernel. Wired seems to be under control, hasn't gone over 50M, and has moved up and down something I don't think was happening before vm_glue.c. Thanks, Julian and everyone who helped fix this. ed | | Cheers | | -mg | | | 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 Thu Jul 4 9:32:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CA8437B400 for ; Thu, 4 Jul 2002 09:32:20 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02AA443E3B for ; Thu, 4 Jul 2002 09:32:17 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 CAA28640; Fri, 5 Jul 2002 02:32:06 +1000 Date: Fri, 5 Jul 2002 02:38:08 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jonathan Lemon Cc: bsddiy@yahoo.com, Subject: Re: Timeout and SMP race In-Reply-To: <200207041530.g64FUwE48481@prism.flugsvamp.com> Message-ID: <20020705022155.L475-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 Thu, 4 Jul 2002, Jonathan Lemon wrote: > In article you write: > >in RELENG_4, when one calls callout_stop() (not nested in softclock execute > >path > >, I am not talking about this case), after it returns, he can believe that the > >callout is truely stopped, however in CURRENT, this assumption is false, now we > > > >must care if callout_stop() truely stopped the callout when it returned, this > >is all difference I see, we bring in this race which not exists in RELENG_4, > >see what hacking code put in kern_condvar.c and kern_synch.c in CURRENT source, > > I don't believe this is true. There is a corresponding race in -stable, > where the spl() level is dropped before performing the callout, thus > allowing either a call to callout_stop() or callout_reset() to come in > immediately before the callout is actually made. I think Giant locking everything prevents problems in RELENG_4, at least when callout_stop() is called in process context (if it is called in interrupt context then it could easily be interrupting a callout even in the UP case). The race window extends from when the ipl or lock is dropped across the whole callout until the ipl or lock is regained. (The ipl is only dropped to splstatclock(); this prevents interruption by timeouts but not by other interrupts. In -current there is nothing much to prevent softclock() itself being called concurrently, but in theory softclock()'s internal locking should prevent problems.) > The callout function is responsible for checking to see if it has lost > the race, and perform the appropriate action. This is done with the > CALLOUT_PENDING and CALLOUT_ACTIVE flags: > > s = splnet(); > if (callout_pending(tp->tt_delack) || !callout_active(tp->tt_delack)) { > splx(s); > return; > } > callout_deactivate(tp->tt_delack); I think David is objecting to this complicating all callers that do the check and breaking all that don't. The callers in kern_synch.c and kern_condvar.c have an mi_switch() and other complications to handle this sinc they can't just return. > If 'CALLOUT_PENDING' is set, then we lost a race with callout_reset(), > and should not perform the callout. If 'CALLOUT_ACTIVE' is clear, then > we lost a race with callout_stop(). > > Either way, on both -current and -stable, you cannot assume that the > timer callback is completely gone immediately after calling callout_stop(). tsleep() seems to assume this in RELENG_4. [Some context lost to top posting.] Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 9:54:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07B1C37B400 for ; Thu, 4 Jul 2002 09:54:17 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB5F343E09 for ; Thu, 4 Jul 2002 09:54:16 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g64GrQN51105; Thu, 4 Jul 2002 11:53:26 -0500 (CDT) (envelope-from jlemon) Date: Thu, 4 Jul 2002 11:53:26 -0500 From: Jonathan Lemon To: Bruce Evans Cc: Jonathan Lemon , bsddiy@yahoo.com, current@freebsd.org Subject: Re: Timeout and SMP race Message-ID: <20020704115326.R1020@prism.flugsvamp.com> References: <200207041530.g64FUwE48481@prism.flugsvamp.com> <20020705022155.L475-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20020705022155.L475-100000@gamplex.bde.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 Fri, Jul 05, 2002 at 02:38:08AM +1000, Bruce Evans wrote: > On Thu, 4 Jul 2002, Jonathan Lemon wrote: > > > In article you write: > > >in RELENG_4, when one calls callout_stop() (not nested in softclock execute > > >path > > >, I am not talking about this case), after it returns, he can believe that the > > >callout is truely stopped, however in CURRENT, this assumption is false, now we > > > > > >must care if callout_stop() truely stopped the callout when it returned, this > > >is all difference I see, we bring in this race which not exists in RELENG_4, > > >see what hacking code put in kern_condvar.c and kern_synch.c in CURRENT source, > > > > I don't believe this is true. There is a corresponding race in -stable, > > where the spl() level is dropped before performing the callout, thus > > allowing either a call to callout_stop() or callout_reset() to come in > > immediately before the callout is actually made. > > I think Giant locking everything prevents problems in RELENG_4, at least > when callout_stop() is called in process context (if it is called in > interrupt context then it could easily be interrupting a callout even in > the UP case). In the network stack at least, callout_stop() is called in interrupt context, so this case actually happens, and has to be handled. > The race window extends from when the ipl or lock is dropped across the > whole callout until the ipl or lock is regained. (The ipl is only dropped > to splstatclock(); this prevents interruption by timeouts but not by > other interrupts. In -current there is nothing much to prevent softclock() > itself being called concurrently, but in theory softclock()'s internal > locking should prevent problems.) > > > The callout function is responsible for checking to see if it has lost > > the race, and perform the appropriate action. This is done with the > > CALLOUT_PENDING and CALLOUT_ACTIVE flags: > > > > > s = splnet(); > > if (callout_pending(tp->tt_delack) || !callout_active(tp->tt_delack)) { > > splx(s); > > return; > > } > > callout_deactivate(tp->tt_delack); > > I think David is objecting to this complicating all callers that do the > check and breaking all that don't. The callers in kern_synch.c and > kern_condvar.c have an mi_switch() and other complications to handle > this sinc they can't just return. I believe I had this conversation with Justin Gibbs earlier; he told me that the callout consumers (network, cam) had to be aware of the race and handle this if it matters. I don't particularly like complicating the callout handlers as illustrated above, though, so if a better scheme is possible, that would be nice. I originally wanted something equivalent to an atomic spl downgrade (splhigh -> splnet), so the timeout code could obtain the target ipl/lock that the callout handler wanted before dropping splhigh(), but was told this would unnecessarily complicate things. > > If 'CALLOUT_PENDING' is set, then we lost a race with callout_reset(), > > and should not perform the callout. If 'CALLOUT_ACTIVE' is clear, then > > we lost a race with callout_stop(). > > > > Either way, on both -current and -stable, you cannot assume that the > > timer callback is completely gone immediately after calling callout_stop(). > > tsleep() seems to assume this in RELENG_4. tsleep() is only called from process context, and appears to be safe because p->wchan has already been cleared by a previous call to unsleep(). The races only matter if you actually care about them. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10: 8: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F74C37B400 for ; Thu, 4 Jul 2002 10:08:07 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id E50C243E09 for ; Thu, 4 Jul 2002 10:08:06 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g64H81Eu011307; Thu, 4 Jul 2002 13:08:01 -0400 (EDT) Date: Thu, 4 Jul 2002 13:08:00 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Neal Fachan , Terry Lambert , Garrett Wollman , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: additional queue macro In-Reply-To: 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 On Thu, 4 Jul 2002, Julian Elischer wrote: > that was teh plan... we're just discussing the name.. > TAILQ_FOREACH_SAFE ? Oh, I thought the initial proposal was to add a _new_ interface that allowed safe removals while traversing the list (and allow the existing macros to be changed for debugging purposes/extra sanity checks). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10:35: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40F0937B400 for ; Thu, 4 Jul 2002 10:35:07 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3377D43E31 for ; Thu, 4 Jul 2002 10:35:06 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.3/8.12.3) with ESMTP id g64HZ7CU000642 for ; Thu, 4 Jul 2002 13:35:08 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.3/8.12.3/Submit) with ESMTP id g64HZ7PM000639 for ; Thu, 4 Jul 2002 13:35:07 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 4 Jul 2002 13:35:07 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: ipfw rule changes? Message-ID: <20020704133324.A633-100000@alpha.yumyumyum.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 Hi, I just updated this morning to the latest -CURRENT, and just to let everyone know, the new KSE stuff seems to be working fine... however, my ipfw rules for dummynet no longer work: ipfw add queue 1 tcp from any to a.b.c.d 25 in via fxp0 ipfw pipe 1 config bw 28Kbit/s queue 2 ipfw queue 1 config pipe 1 mask dst-ip 0xffffffff Am I doing something wrong here? This worked fine before I rebuilt world (and I'm assuming rebuilt the ipfw program)... Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10:37:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80C9B37B401; Thu, 4 Jul 2002 10:37:11 -0700 (PDT) Received: from april.chuckr.org (april.chuckr.org [66.92.147.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AFB043E09; Thu, 4 Jul 2002 10:37:10 -0700 (PDT) (envelope-from chuckr@chuckr.org) Received: from chuckr.org (localhost.chuckr.org [127.0.0.1]) by april.chuckr.org (8.11.6/8.11.3) with ESMTP id g64HYhJ47500; Thu, 4 Jul 2002 13:35:14 -0400 (EDT) (envelope-from chuckr@chuckr.org) Message-Id: <200207041735.g64HYhJ47500@april.chuckr.org> Date: Thu, 4 Jul 2002 13:34:42 -0400 (EDT) From: Chuck Robey Subject: Re: Recommended MP development machines... To: peter@wemm.org Cc: obrien@FreeBSD.ORG, gnn@neville-neil.com, freebsd-current@FreeBSD.ORG In-Reply-To: <20020704065915.8FDA2390F@overcee.wemm.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 3 Jul, Peter Wemm wrote: > Chuck Robey wrote: >> On Wed, 3 Jul 2002, David O'Brien wrote: >> >> > On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote: >> > > I know everyone says "they all work" but i'd like some recommendations > on >> > > MP machines for -CURRENT work. I'll be ordering one this week. >> > >> > There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness) > . >> > http://www.tyan.com/products/html/thunderk7.html. It comes in multiple >> > flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit >> > PCI, 1 AGP version. You can cheap out and not get the non-SCSI S2462NG >> > model. Match this bad-boy up with a pair of fast Athlon `MP' (not `XP') >> > CPU's and it is a totally solid system. Various FreeBSD committers also >> > have this system. >> > >> > There is a newer [more economic] version called the Thunder K7X. >> > http://www.tyan.com/products/html/thunderk7x.html >> >> "more economic" is a poor way to describe it, seeing as it has all the >> features, plus (1) an updated version of the AMD mp chipset and (2) a >> fixed onboard usb port. The K7 had a broken on-board usb (the AMD >> chipset had a PCI contention bug for the usb port, so the tin back panel >> of the board blocked out the usb, and the K7 came with a PCI usb card, >> which ate up one of your PCI slots. The K7X has a repaired on-board usb, >> so you get that PCI slot back. > > Hmmmmm..... Do you have any details on this? I've had occasional strange > USB-related things happen on this box. Of course, it runs -current which > puts me into the USB danger-zone enough as it is.. but what happens when > this bug is triggered? Sorry it took so long, the web site I originally found it on has apparently disappeared. This link, however, describes the problem neatly: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24472.pdf ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10:38:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B51937B401 for ; Thu, 4 Jul 2002 10:38:11 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id D758C43E31 for ; Thu, 4 Jul 2002 10:38:10 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from alpha.yumyumyum.org (localhost [127.0.0.1]) by alpha.yumyumyum.org (8.12.3/8.12.3) with ESMTP id g64HcCCU000673 for ; Thu, 4 Jul 2002 13:38:13 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Received: from localhost (culverk@localhost) by alpha.yumyumyum.org (8.12.3/8.12.3/Submit) with ESMTP id g64HcCRN000670 for ; Thu, 4 Jul 2002 13:38:12 -0400 (EDT) (envelope-from culverk@yumyumyum.org) X-Authentication-Warning: alpha.yumyumyum.org: culverk owned process doing -bs Date: Thu, 4 Jul 2002 13:38:12 -0400 (EDT) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: Re: ipfw rule changes? In-Reply-To: <20020704133324.A633-100000@alpha.yumyumyum.org> Message-ID: <20020704133517.R633-100000@alpha.yumyumyum.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 > Hi, I just updated this morning to the latest -CURRENT, and just to let > everyone know, the new KSE stuff seems to be working fine... however, my > ipfw rules for dummynet no longer work: > > ipfw add queue 1 tcp from any to a.b.c.d 25 in via fxp0 > ipfw pipe 1 config bw 28Kbit/s queue 2 > ipfw queue 1 config pipe 1 mask dst-ip 0xffffffff > > Am I doing something wrong here? This worked fine before I rebuilt world > (and I'm assuming rebuilt the ipfw program)... > Oh yeah, this is the error message: alpha:~:# ipfw queue 1 config pipe 1 mask dst-ip 0xffffffff ipfw: unrecognised option ``1'' Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10:40:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C98D437B400 for ; Thu, 4 Jul 2002 10:40:15 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 492EF43E09 for ; Thu, 4 Jul 2002 10:40:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704174014.OVV6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 17:40:14 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA09051; Thu, 4 Jul 2002 10:27:08 -0700 (PDT) Date: Thu, 4 Jul 2002 10:27:07 -0700 (PDT) From: Julian Elischer To: Mario Goebbels Cc: current@freebsd.org Subject: Re: Wired mem fun! In-Reply-To: <3D246CE9.4090607@tomservo.cc> 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 how about getting the new version of vm_glue.c that fixes this? :-) On Thu, 4 Jul 2002, Mario Goebbels wrote: > 4th July 5pm CET, with world and kernel from 11am 3rd July, after a > couple of hours runtime, doing mainly xchat and Mozilla, I got these stats: > > Mem: 73M Active, 221M Inact, 210M Wired, 1128K Cache, 61M Buf, 136M Free > Swap: 512M Total, 512M Free > > Mem: 82M Active, 284M Inact, 873M Wired, 29M Cache, 61M Buf, 17M Free > Swap: 512M Total, 512M Free > > the new vm-glue.c, so see if it raises that high again. no it won't To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 10:40:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BCA737B405 for ; Thu, 4 Jul 2002 10:40:18 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id D420443E09 for ; Thu, 4 Jul 2002 10:40:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704174017.OWP6023.sccrmhc02.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 17:40:17 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA09070; Thu, 4 Jul 2002 10:33:25 -0700 (PDT) Date: Thu, 4 Jul 2002 10:33:24 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: Neal Fachan , Terry Lambert , Garrett Wollman , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: additional queue macro In-Reply-To: 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 there are two proposals floatingat the moment.. 1/ I added debugging stuff to TAILQ to help find bad usages in KSE. Qusetion/proposal: Should I extend this to other types and add it to the file (or not delete what is there now) 2/ We could add a new macro/method that is slightly less efficient than the current FOREACH macros, but allows element removal. Exisiting methods would no change. On Thu, 4 Jul 2002, Daniel Eischen wrote: > On Thu, 4 Jul 2002, Julian Elischer wrote: > > that was teh plan... we're just discussing the name.. > > TAILQ_FOREACH_SAFE ? > > Oh, I thought the initial proposal was to add a _new_ interface > that allowed safe removals while traversing the list (and allow > the existing macros to be changed for debugging purposes/extra > sanity checks). > > -- > Dan Eischen > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 11:29:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A2B237B400 for ; Thu, 4 Jul 2002 11:29:43 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98FD443E09 for ; Thu, 4 Jul 2002 11:29:42 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g64ITaw4019130; Thu, 4 Jul 2002 14:29:36 -0400 (EDT) Date: Thu, 4 Jul 2002 14:29:36 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Neal Fachan , Terry Lambert , Garrett Wollman , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: additional queue macro In-Reply-To: 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 On Thu, 4 Jul 2002, Julian Elischer wrote: > there are two proposals floatingat the moment.. > > 1/ I added debugging stuff to TAILQ to help find bad usages in KSE. > Qusetion/proposal: Should I extend this to other types and add it to the > file (or not delete what is there now) I was suggesting that you add macros for debugging purposes instead of potentially changing existing behaviour. The way you've got it now is OK I guess, just as long as it somehow doesn't get enabled or changed in userland. Perhaps it would even break consumers of it in the kernel, though, too. > 2/ > We could add a new macro/method that is slightly less efficient than the > current FOREACH macros, but allows element removal. > Exisiting methods would no change. As wollman pointed out, we already assume that it is safe to remove elements using the existing macros. Adding another interface to do the same thing kinda imples that existing behaviour may change. As proposed though, the new macros would not only allow removals, but also modification of the removed element while still walking the list. These might be useful. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 11:40:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8780237B400 for ; Thu, 4 Jul 2002 11:40:08 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04E0743E09 for ; Thu, 4 Jul 2002 11:40:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704184007.WLYO903.sccrmhc03.attbi.com@InterJet.elischer.org> for ; Thu, 4 Jul 2002 18:40:07 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA09261 for ; Thu, 4 Jul 2002 11:25:31 -0700 (PDT) Date: Thu, 4 Jul 2002 11:25:30 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: status of KSE merge 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 *phew* (wipes sweat from brow) Ok After a hectic couple of days it looks like the stability of -current is back where it should be. Multiple buildworlds are completing with no discernable degradation. At this time I have no information on any apps that fail to work (that did work before KSE). The signal flakiness is still present but at least people can get work done. I will work on this next (though signal experts are welcome to try their hand as well.. (in fact any beginners who want to jump inat the deep end of the pool can guarantee a near-drowning-experience by trying to understand signals). Performance seems pretty much equivalent to pre_KSE. Many thanks to the many people who sent test results and patch suggestions, especialy David Xu who I forgot to acknolegde on the appropriate checkin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 12: 0:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0D8137B400 for ; Thu, 4 Jul 2002 12:00:21 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id D556543E31 for ; Thu, 4 Jul 2002 12:00:20 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704190019.JDIF29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 19:00:19 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA09335; Thu, 4 Jul 2002 11:40:45 -0700 (PDT) Date: Thu, 4 Jul 2002 11:40:44 -0700 (PDT) From: Julian Elischer To: Daniel Eischen Cc: FreeBSD current users Subject: Re: additional queue macro In-Reply-To: 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 On Thu, 4 Jul 2002, Daniel Eischen wrote: > On Thu, 4 Jul 2002, Julian Elischer wrote: > > > there are two proposals floatingat the moment.. > > > > 1/ I added debugging stuff to TAILQ to help find bad usages in KSE. > > Qusetion/proposal: Should I extend this to other types and add it to the > > file (or not delete what is there now) > > I was suggesting that you add macros for debugging purposes instead > of potentially changing existing behaviour. The way you've got it > now is OK I guess, just as long as it somehow doesn't get enabled > or changed in userland. Perhaps it would even break consumers > of it in the kernel, though, too. > > > 2/ > > We could add a new macro/method that is slightly less efficient than the > > current FOREACH macros, but allows element removal. > > Exisiting methods would no change. > > As wollman pointed out, we already assume that it is safe to > remove elements using the existing macros. Adding another > interface to do the same thing kinda imples that existing > behaviour may change. As proposed though, the new macros > would not only allow removals, but also modification of > the removed element while still walking the list. These might > be useful. > In this rare case Garrett was wrong. Only He assumed that. Most people do not assume that, in fact 'folk lore' in general is that it is NOT safe to do that. In fact it is NOT safe to do so if you are going to do anythign WITH that element while still in the loop. The kernel does not do it anywhere I could find, and the man pages specifically avoid doing that. There is no historical precedent because the iterators are already a recent FreeBSD (phk) addition. CSRG did not have them. The ability do do: TAILQ_FOREACH_REMOVABLE(thread, runqueue...) { if (thread should be suspended) { TAILQ_REMOVE(thread); TAILQ_INSERT_TAIL(thread, idlequeue...); } } would be very nice. > -- > Dan Eischen > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 12:24:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7A2B37B400 for ; Thu, 4 Jul 2002 12:24:26 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C83543E09 for ; Thu, 4 Jul 2002 12:24:26 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g64JOLL7024574; Thu, 4 Jul 2002 15:24:21 -0400 (EDT) Date: Thu, 4 Jul 2002 15:24:21 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: FreeBSD current users Subject: Re: additional queue macro In-Reply-To: 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 On Thu, 4 Jul 2002, Julian Elischer wrote: > > On Thu, 4 Jul 2002, Daniel Eischen wrote: > > > On Thu, 4 Jul 2002, Julian Elischer wrote: > > > > > 2/ > > > We could add a new macro/method that is slightly less efficient than the > > > current FOREACH macros, but allows element removal. > > > Exisiting methods would no change. > > > > As wollman pointed out, we already assume that it is safe to > > remove elements using the existing macros. Adding another > > interface to do the same thing kinda imples that existing > > behaviour may change. As proposed though, the new macros > > would not only allow removals, but also modification of > > the removed element while still walking the list. These might > > be useful. > > > > In this rare case Garrett was wrong. Only He assumed that. I assumed that also, and libc_r currently assumes that. Perhaps I am in the minority, but maybe there are more reliances on this than you think? Anyways, I don't have a problem transitioning to another set of macros when they are provided. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 13:39:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0B4237B400 for ; Thu, 4 Jul 2002 13:39:29 -0700 (PDT) Received: from web11403.mail.yahoo.com (web11403.mail.yahoo.com [216.136.131.233]) by mx1.FreeBSD.org (Postfix) with SMTP id 94EDC43E58 for ; Thu, 4 Jul 2002 13:39:28 -0700 (PDT) (envelope-from shizukakudo_99@yahoo.com) Message-ID: <20020704203928.3913.qmail@web11403.mail.yahoo.com> Received: from [203.198.2.8] by web11403.mail.yahoo.com via HTTP; Thu, 04 Jul 2002 13:39:28 PDT Date: Thu, 4 Jul 2002 13:39:28 -0700 (PDT) From: Shizuka Kudo Subject: Re: [acpi-jp 1661] Re: ASUS CUSL2 panic on acpi To: Mitsuru IWASAKI Cc: freebsd-current@freebsd.org, acpi-jp@jp.FreeBSD.org In-Reply-To: <20020704.220952.104026566.iwasaki@jp.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 --- Mitsuru IWASAKI wrote: > My analysis was finished. Please try this patch. > > --- exfield.c- Thu Jul 4 21:54:24 2002 > +++ exfield.c Thu Jul 4 21:55:02 2002 > @@ -200,7 +200,7 @@ > /* Handle both ACPI 1.0 and ACPI 2.0 Integer widths */ > > IntegerSize = sizeof (ACPI_INTEGER); > - if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) > + if (WalkState->MethodNode != NULL && WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) > { > /* > * We are running a method that exists in a 32-bit ACPI table. Mitsuru, Thanks, it works. I was able to boot without panic with your patch. Sorry for not getting back to you on the acpidump and debug info as I didn't have my null modem cable and notebook with me to use as a serial console. Do you still need to acpidump files? BTW, I did notice some hangs that possibly related to ACPI. About two or three months ago, this ASUS CUSL2 hang while running sysinstall. It can react to Alt-F?(i.e. switch virtual console) but not on any other keys nor responding to ping from another computer. I was not able to isolate the cause until this time I unset acpi_load. Without acpi.ko loaded, I could run sysinstall with no problem. In fact, I just found that loading acpi.ko also have the same freeze with CUPS. What should I do to help identifying if this is ACPI related? Regards, __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 13:40:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B1FF37B400 for ; Thu, 4 Jul 2002 13:40:12 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9017A43E09 for ; Thu, 4 Jul 2002 13:40:11 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020704204010.YZCE903.sccrmhc03.attbi.com@InterJet.elischer.org>; Thu, 4 Jul 2002 20:40:10 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA09705; Thu, 4 Jul 2002 13:36:24 -0700 (PDT) Date: Thu, 4 Jul 2002 13:36:23 -0700 (PDT) From: Julian Elischer To: Jeff Roberson Cc: FreeBSD current users Subject: another UMA question. In-Reply-To: <20020702195551.U91055-100000@mail.chesapeake.net> 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 SO I'm using UMA to store threads however UMA seem sto be too eager to create new threads.. for example: (my own version has more instrumentation) ref4# sysctl kern.threads kern.threads.active: 71 <- number currently attached to processes kern.threads.cached: 76 <- number in the UMA pool kern.threads.allocated: 147 <- number presently allocated + cached kern.threads.freed: 0 <- number of times fini() called kern.threads.total: 147 <- number of times init() called kern.threads.max: 79 <- highest ever value of 'active' given that the threads each have an 8k stack attached, this means that there are 68 x 8k stacks that will never be used.. (557056 bytes of wasted ram) how would I go about 'tuning' this? also: After a while UMA starts freeing and then reallocating these: e.g. ref4# sysctl kern.threads kern.threads.active: 63 kern.threads.cached: 147 kern.threads.allocated: 210 kern.threads.freed: 231 kern.threads.total: 441 kern.threads.max: 84 this is wasteful to allocate and deallocate (with all the work involved) 231 threads and sacks for no reason (after it freed them, it pretty quickly reallocated them as you see, there are 147 presently cached, representing 1.2Mb of ram. Can the algorythms be tuned to use a more gentle hysteresis? Can the high and low watermarks be specified per type? Is there a chance you can add a uma_zadjust() or something that allows us to set the cache high and low water marks etc? For example I really don;t want it to start allocating new threads until I have maybe only 12 or so left in the cache. On the other hand I probably want to free them from the cache if I have more than say 40.. This is why I originally used my own cache.. Eventually I would like to be able to adjust the zone parameters according to recent history.. I would like to calculate a running average and variance of thread usage and aim to keep the caches adjusted for AVERAGE + 3xStandard deviations or something. This suggests that I should be able to register another management method with UMA for that zone... thoughts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 13:59:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E094037B400; Thu, 4 Jul 2002 13:59:39 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B1243E09; Thu, 4 Jul 2002 13:59:35 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 QAA07652; Thu, 4 Jul 2002 16:59:32 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g64Kx2g27620; Thu, 4 Jul 2002 16:59:02 -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: <15652.46870.463359.853754@grasshopper.cs.duke.edu> Date: Thu, 4 Jul 2002 16:59:02 -0400 (EDT) To: Bosko Milekic Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) In-Reply-To: <20020620134723.A22954@unixdaemons.com> References: <20020618223635.A98350@panzer.kdm.org> <20020619090046.A2063@panzer.kdm.org> <20020619120641.A18434@unixdaemons.com> <15633.17238.109126.952673@grasshopper.cs.duke.edu> <20020619233721.A30669@unixdaemons.com> <15633.62357.79381.405511@grasshopper.cs.duke.edu> <20020620114511.A22413@unixdaemons.com> <15634.534.696063.241224@grasshopper.cs.duke.edu> <20020620134723.A22954@unixdaemons.com> 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 Bosko Milekic writes: > > One question. I've observed some really anomolous behaviour under > > -stable with my Myricom GM driver (2Gb/s + 2Gb/s link speed, Dual 1GHz > > pIII). When I use 4K mbufs for receives, the best speed I see is > > about 1300Mb/sec. However, if I use private 9K physically contiguous > > buffers I see 1850Mb/sec (iperf TCP). > > > > The obvious conclusion is that there's a lot of overhead in setting up > > the DMA engines, but that's not the case; we have a fairly quick chain > > dma engine. I've provided a "control" by breaking my contiguous > > buffers down into 4K chunks so that I do the same number of DMAs in > > both cases and I still see ~1850 Mb/sec for the 9K buffers. > > > > A coworker suggested that the problem was that when doing copyouts to > > userspace, the PIII was doing speculative reads and loading the cache > > with the next page. However, we then start copying from a totally > > different address using discontigous buffers, so we effectively take > > 2x the number of cache misses we'd need to. Does that sound > > reasonable to you? I need to try malloc'ing virtually contigous and > > physically discontigous buffers & see if I get the same (good) > > performance... > > I believe that the Intel chips do "virtual page caching" and that the > logic that does the virtual -> physical address translation sits between > the L2 cache and RAM. If that is indeed the case, then your idea of > testing with virtually contiguous pages is a good one. > Unfortunately, I don't know if the PIII is doing speculative > cache-loads, but it could very well be the case. If it is and if in > fact the chip does caching based on virtual addresses, then providing it > with virtually contiguous address space may yield better results. If > you try this, please let me know. I'm extremely interested in seeing > the results! contigmalloc'ed private jumbo mbufs (same as bge, if_ti, etc): % iperf -c ugly-my -l 32k -fm ------------------------------------------------------------ Client connecting to ugly-my, TCP port 5001 TCP window size: 0.2 MByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.3 port 1031 connected with 192.168.1.4 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 2137 MBytes 1792 Mbits/sec malloc'ed, physically discontigous private jumbo mbufs: % iperf -c ugly-my -l 32k -fm ------------------------------------------------------------ Client connecting to ugly-my, TCP port 5001 TCP window size: 0.2 MByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.3 port 1029 connected with 192.168.1.4 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 2131 MBytes 1788 Mbits/sec So I'd be willing to believe that the 4Mb/sec loss was due to the extra overhead of setting up 2 additional DMAs. So it looks like this idea would work. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 14:19: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6903F37B400; Thu, 4 Jul 2002 14:18:54 -0700 (PDT) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2DB743E09; Thu, 4 Jul 2002 14:18:53 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0231.cvx21-bradley.dialup.earthlink.net ([209.179.192.231] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QE01-0001aU-00; Thu, 04 Jul 2002 17:18:50 -0400 Message-ID: <3D24BB6E.3829314A@mindspring.com> Date: Thu, 04 Jul 2002 14:17:34 -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: Bruce Evans Cc: Greg 'groggy' Lehey , Poul-Henning Kamp , Mario Goebbels , current@FreeBSD.org Subject: About DEVFS (was: Re: About GEOM...) References: <20020704210304.Y21619-100000@gamplex.bde.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 Bruce Evans wrote: > On Thu, 4 Jul 2002, Greg 'groggy' Lehey wrote: > > I don't know enough about GEOM to embrace it whole-heartedly, but I > > think you'd be hard pressed to find anybody who disagrees that devfs > > is a forward. It may need some improvement, but it's so much more > > logical than what we had before that I really think you should explain > > your objections. > > This has been discussed before. Basically, devfs creates work by moving > problems around without any significant benefits. I expect control of > devfs device visibility and persistence of devfs device attributes would > end up mostly in a utility (devd?). But once you have such a utility, > you don't need devfs (or MAKEDEV). Here are the significant benefits realized by the current devfs, over static device nodes: o Hardware & node synchornization o If the hardware is there, the device is there o If the hardware is not there, the device is not there (as opposed to being there, but being unusable) o Device arrival/departure (necessary for docking ports, USB, IEEE 1394, PCMCIA, PCCARD, and Hot Plug-N-Play) o If a device for which there is a driver arrives, the node is created o If the device for which a node exists is removed, the node is removed o Better support for booting of physically FS-less images o When porting to a new platform, the ability to access device nodes is one less thing to worry about (getting a physical FS running first) o Because device nodes in FreeBSD have more bits, they exceed the major/minor numbers representable on some platform's device nodes in their FS; this means without a devfs, it's impossible to net-boot FreeBSD from some systems o Inability to create non-existant ("convenience") nodes and symbolic links, thus confusing the /dev directory o Inability to accidently "tar" or otherwise archive your entire system to a file in /dev, rather than writing it to a device (;^)) o Increased security, as hacked permissions values away from the system defined acceptable safe values can not persist across a reboot, unless the source code is modified to match Here are the significant disadvantages: o Inability to create non-existant ("convenience") nodes and symbolic links, thus providing device aliases matching those rendesvous expected by existing third party programs, in particular, with regard to ABI compatability o Inability to persistently modify default permissions values away from the system defined acceptable safe values persistantly across a reboot, without modifying instance declaration in source code. o "One size fits all" per major number for template permissions definitions Here are the promised, but as-yet-unrealized additional benefits (you could also call these significant disadvantages, as they were supposed to be part of the pay-off for the switch): o The device instance becomes the vnode reference, rather than the major/minor o Specfs can die, once and for all o struct fileops must die (e.g. inability to set range locks, ownership, other administrative controls on file objects that are not backed by fileops == vfsops) o Real cloning devices -- Personally, I've never been persuaded that the persistance of modifications argument against devfs had any validity; I have yet to see one case that can not be managed via rc.local or modification of driver defaults (e.g. I know of no transient device that results in the creation of multiple device nodes for the same major number). I personally think the correct way to handle this is to write the changes back to the kernel image, if we are talking about modifications to the primary instances of the devices. The ABI argument is resolvable directly: in the conpat hierarchy, you can create a symlink to the device node; problem solved. Yeah, it pisses me off that the devfs was not completed before going on to work on other things which have also not been completed; this goes for both Julian's implementation, which Poul murdered, and Poul's implementation, which I regard as still incomplete. But overall, it seems to be a move forward. I guess if you valued persistance (e.g. the ability to rename your floppy device to be /dev/mickeymouse) over the new features, I guess I could see your point. At this juncture, though, it's starting to look more like luddism than reasoned argument against devfs. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 17:15:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C8E937B400 for ; Thu, 4 Jul 2002 17:15:15 -0700 (PDT) Received: from speaker.rodsbooks.com (ip68-14-7-118.ri.ri.cox.net [68.14.7.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4800343E09 for ; Thu, 4 Jul 2002 17:15:11 -0700 (PDT) (envelope-from rodsmith@rodsbooks.com) Received: by speaker.rodsbooks.com (Postfix, from userid 500) id B40672B80A; Thu, 4 Jul 2002 20:15:06 -0400 (EDT) To: current@FreeBSD.ORG Reply-To: rodsmith@rodsbooks.com Subject: Swap file (not swap partition) with 5.0? Date: Thu, 04 Jul 2002 20:15:06 -0400 (EDT) X-Mailer: XCmail 1.3 - with PGP support, PGP engine version 0.5 (Linux) X-Mailerorigin: http://www.fsai.fh-trier.de/~schmitzj/Xclasses/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20020705001506.B40672B80A@speaker.rodsbooks.com> From: rodsmith@rodsbooks.com (Rod Smith) 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, The http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/adding-swap-space.html web page includes instructions on creating a swap file for use with FreeBSD. Unfortunately, these instructions don't work with the -CURRENT branch -- or at least, not with the 5.0 RC1 release I've got. Specifically, the compile fails very early on with a syntax error over the kernel configuration line: pseudo-device vn 1 I can't seem to find any hint of what's happened to this option in the NOTES file. Any tips? Does 5.0 still support a swap file, and if so, is the procedure for using it documented anywhere? Thanks. -- Rod Smith rodsmith@rodsbooks.com http://www.rodsbooks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 17:25:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BA4937B400 for ; Thu, 4 Jul 2002 17:25:10 -0700 (PDT) Received: from a.smtp-out.sonic.net (a.smtp-out.sonic.net [208.201.224.38]) by mx1.FreeBSD.org (Postfix) with SMTP id E306843E31 for ; Thu, 4 Jul 2002 17:25:09 -0700 (PDT) (envelope-from sonicmail@blarf.homeip.net) Received: (qmail 29770 invoked from network); 5 Jul 2002 00:25:09 -0000 Received: from sub.sonic.net (208.201.224.8) by a.smtp-out.sonic.net with SMTP; 5 Jul 2002 00:25:09 -0000 Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by sub.sonic.net (8.11.6/8.8.5) with ESMTP id g650P9707950; Thu, 4 Jul 2002 17:25:09 -0700 X-envelope-info: Received: by blarf.homeip.net (Postfix, from userid 1006) id BE14819CF; Thu, 4 Jul 2002 17:25:08 -0700 (PDT) Date: Thu, 4 Jul 2002 17:25:08 -0700 From: Alex Zepeda To: Rod Smith , current@freebsd.org Subject: Re: Swap file (not swap partition) with 5.0? Message-ID: <20020705002508.GA3912@blarf.homeip.net> References: <20020705001506.B40672B80A@speaker.rodsbooks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020705001506.B40672B80A@speaker.rodsbooks.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 Thu, Jul 04, 2002 at 08:15:06PM -0400, Rod Smith wrote: > I can't seem to find any hint of what's happened to this option in the > NOTES file. Any tips? Does 5.0 still support a swap file, and if so, is > the procedure for using it documented anywhere? Thanks. vn has been replaced by 'md'. man md. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 18:25:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E81237B400 for ; Thu, 4 Jul 2002 18:25:49 -0700 (PDT) Received: from mail.viasoft.com.cn (ip-167-164-97-218.anlai.com [218.97.164.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5FD443E09 for ; Thu, 4 Jul 2002 18:25:46 -0700 (PDT) (envelope-from davidx@viasoft.com.cn) Received: from davidwnt (davidwnt.viasoft.com.cn [192.168.1.239]) by mail.viasoft.com.cn (8.9.3/8.9.3) with SMTP id JAA28766; Fri, 5 Jul 2002 09:41:43 +0800 Message-ID: <004701c223c1$a0eaadf0$ef01a8c0@davidwnt> From: "David Xu" To: "Julian Elischer" , "FreeBSD current users" References: Subject: Re: status of KSE merge Date: Fri, 5 Jul 2002 09:16:44 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 Julian, could you give us an overview of all signal problems in KSE ? so we maybe work on this more easy. David Xu ----- Original Message -----=20 From: "Julian Elischer" To: "FreeBSD current users" Sent: Friday, July 05, 2002 2:25 AM Subject: status of KSE merge >=20 > *phew* (wipes sweat from brow) >=20 > Ok After a hectic couple of days it looks like the stability of = -current > is back where it should be. Multiple buildworlds are completing=20 > with no discernable degradation. >=20 > At this time I have no information on any apps that fail to work (that = did > work before KSE). >=20 > The signal flakiness is still present but at least people can get work > done. I will work on this next (though signal experts are welcome to > try their hand as well.. (in fact any beginners who want to jump inat = the=20 > deep end of the pool can guarantee a near-drowning-experience by = trying > to understand signals). >=20 > Performance seems pretty much equivalent to pre_KSE. >=20 > Many thanks to the many people who sent test results and patch > suggestions, especialy David Xu who I forgot to acknolegde on the > appropriate checkin. >=20 >=20 >=20 >=20 >=20 > 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 Thu Jul 4 19: 6:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9551837B400 for ; Thu, 4 Jul 2002 19:06:13 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0058443E09 for ; Thu, 4 Jul 2002 19:06:13 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g65266X56053; Thu, 4 Jul 2002 22:06:06 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Thu, 4 Jul 2002 22:06:06 -0400 (EDT) From: Jeff Roberson To: Julian Elischer Cc: FreeBSD current users Subject: Re: another UMA question. In-Reply-To: Message-ID: <20020704182736.Y25604-100000@mail.chesapeake.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 Thu, 4 Jul 2002, Julian Elischer wrote: > > SO I'm using UMA to store threads however UMA seem sto be too eager to > create new threads.. > for example: (my own version has more instrumentation) > > ref4# sysctl kern.threads > kern.threads.active: 71 <- number currently attached to processes > kern.threads.cached: 76 <- number in the UMA pool > kern.threads.allocated: 147 <- number presently allocated + cached > kern.threads.freed: 0 <- number of times fini() called > kern.threads.total: 147 <- number of times init() called > kern.threads.max: 79 <- highest ever value of 'active' > > > given that the threads each have an 8k stack attached, > this means that there are 68 x 8k stacks that will never be used.. > (557056 bytes of wasted ram) > how would I go about 'tuning' this? This is probably due to the per cpu buckets. Even if this is on a uni processor machine there is a single bucket that caches a nonfixed number of items. I have a somewhat lame mechanism for limiting this right now. Basically initially I won't cache more than a slabs worth of items in a bucket, although this can grow. The problem is that UMA doesn't know that there is a lot of other memory associated with this, so it shouldn't cache so many. UMA thinks it's only caching one page per bucket. I definately need a better way to do the bucket allocation and sizing. > > also: > > After a while UMA starts freeing and then reallocating > these: > e.g. > ref4# sysctl kern.threads > kern.threads.active: 63 > kern.threads.cached: 147 > kern.threads.allocated: 210 > kern.threads.freed: 231 > kern.threads.total: 441 > kern.threads.max: 84 > > > this is wasteful to allocate and deallocate (with all the work involved) > 231 threads and sacks for no reason > (after it freed them, it pretty quickly reallocated them as you see, > there are 147 presently cached, representing 1.2Mb of ram. There is an algorithm that tries to calculate demand over the last N seconds (20 right now I believe). This is intended to prevent us from freeing slabs that will be needed immediately. I think this could be revisited now that we have a zone that actually exhibits behavior that is interesting enough to study. Although, please remember that freeing all of that memory now may save diskio. So it is worth whatever startup cost is neccesary to save a page even for a few seconds. > > Can the algorythms be tuned to use a more gentle hysteresis? > Can the high and low watermarks be specified per type? > > Is there a chance you can add a uma_zadjust() or something that > allows us to set the cache high and low water marks etc? > > For example I really don;t want it to start allocating new threads until > I have maybe only 12 or so left in the cache. On the other hand > I probably want to free them from the cache if I have more than say 40.. > This is why I originally used my own cache.. > > Eventually I would like to be able to adjust the zone parameters > according to recent history.. > I would like to calculate a running average and variance of thread > usage and aim to keep the caches adjusted for > AVERAGE + 3xStandard deviations or something. > This suggests that I should be able to register another management > method with UMA for that zone... > > thoughts? > > > > I'd like to avoid any static thresholds and so on. One of the reasons I picked the solaris slab design as a starting point was to avoid any static configuration. I think uma can be aware enough of allocation history and vm page needs to make good decisions. I agree that it probably needs some tuning though, especially the per cpu buckets. Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 19:10:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 910FE37B400; Thu, 4 Jul 2002 19:10:26 -0700 (PDT) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD69043E31; Thu, 4 Jul 2002 19:10:23 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.4/8.12.3) with ESMTP id g652A9ZL012624; Fri, 5 Jul 2002 11:40:10 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: About DEVFS (was: Re: About GEOM...) From: "Daniel O'Connor" To: Terry Lambert Cc: Bruce Evans , "Greg 'groggy' Lehey" , Poul-Henning Kamp , Mario Goebbels , current@FreeBSD.ORG In-Reply-To: <3D24BB6E.3829314A@mindspring.com> References: <20020704210304.Y21619-100000@gamplex.bde.org> <3D24BB6E.3829314A@mindspring.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.7 Date: 05 Jul 2002 11:40:09 +0930 Message-Id: <1025835014.4223.5.camel@chowder.gsoft.com.au> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.6 (www dot roaringpenguin dot com slash mimedefang) 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, 2002-07-05 at 06:47, Terry Lambert wrote: > o Inability to create non-existant ("convenience") nodes and > symbolic links, thus providing device aliases matching those > rendesvous expected by existing third party programs, in > particular, with regard to ABI compatability > o Inability to persistently modify default permissions values > away from the system defined acceptable safe values persistantly > across a reboot, without modifying instance declaration in > source code. > o "One size fits all" per major number for template permissions > definitions I am pretty sure you can put chmod/ln -s commands in /etc/rc.local (I rc.devfs? My -current box is asleep ATM) which largely solves this problem. It isn't perfect but the current DEVFS has good advantages - especially the hardware/node synchronisation which is very useful when you have to shuffle hard drives and have neglected to make the right device nodes first. > Personally, I've never been persuaded that the persistance of modifications > argument against devfs had any validity; I have yet to see one case that > can not be managed via rc.local or modification of driver defaults > (e.g. I know of no transient device that results in the creation of > multiple device nodes for the same major number). I personally think > the correct way to handle this is to write the changes back to the > kernel image, if we are talking about modifications to the primary > instances of the devices. Loader? ie on shutdown write a list of permissions etc into a file which the loader can slurp up next boot and shove into the kernel and be parsed. > But overall, it seems to be a move forward. I guess if you valued > persistance (e.g. the ability to rename your floppy device to be > /dev/mickeymouse) over the new features, I guess I could see your > point. Mmmm.. unnecessary pain. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 19:41:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8FE837B400; Thu, 4 Jul 2002 19:41:34 -0700 (PDT) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83F1A43E09; Thu, 4 Jul 2002 19:41:34 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0169.cvx22-bradley.dialup.earthlink.net ([209.179.198.169] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QJ26-0002Mr-00; Thu, 04 Jul 2002 22:41:19 -0400 Message-ID: <3D2506F9.8B34FD80@mindspring.com> Date: Thu, 04 Jul 2002 19:39: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: Daniel O'Connor Cc: Bruce Evans , Greg 'groggy' Lehey , Poul-Henning Kamp , Mario Goebbels , current@FreeBSD.ORG Subject: Re: About DEVFS (was: Re: About GEOM...) References: <20020704210304.Y21619-100000@gamplex.bde.org> <3D24BB6E.3829314A@mindspring.com> <1025835014.4223.5.camel@chowder.gsoft.com.au> 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 Daniel O'Connor wrote: > I am pretty sure you can put chmod/ln -s commands in /etc/rc.local (I > rc.devfs? My -current box is asleep ATM) which largely solves this > problem. If you have PCMCIA, PCCARD, USB, IEEE 1394, or a docking station, the devices that you are interested in do not necessarily exist at the time that your rc.local is run. If that's the case, this doesn't work. The obvious solution to this is the "devd" that Bruce mentioned; but if you take the obvious solution, you might as well be creating and deleting devices from the devd, rather than in the kernel in a devfs (this is what Bruce meant when he mentioned his "might as well"). The failure with this model is that there is a race on device deletion, which would leave a device present in /dev, when the hardware was no longer available. A devfs (if written correctly) will not have this problem. Note that the PCMCIA code was argues on the point of the two shorter pins, on card eject, about two years ago -- the consensus was that it was possible, but it would take a lot of work, to get to where Windows is, in terms of capability of handling ejected devices. > It isn't perfect but the current DEVFS has good advantages - especially > the hardware/node synchronisation which is very useful when you have to > shuffle hard drives and have neglected to make the right device nodes > first. Yes. It has advantages and disadvantages. It all depends on what you personally value. > > Personally, I've never been persuaded that the persistance of modifications > > argument against devfs had any validity; I have yet to see one case that > > can not be managed via rc.local or modification of driver defaults > > (e.g. I know of no transient device that results in the creation of > > multiple device nodes for the same major number). I personally think > > the correct way to handle this is to write the changes back to the > > kernel image, if we are talking about modifications to the primary > > instances of the devices. > > Loader? > ie on shutdown write a list of permissions etc into a file which the > loader can slurp up next boot and shove into the kernel and be parsed. This really doesn't work very well. You end up with two sets of data. Having done something like this in practice, and had to live with the aftermath, I don't recommend it (at all). > > But overall, it seems to be a move forward. I guess if you valued > > persistance (e.g. the ability to rename your floppy device to be > > /dev/mickeymouse) over the new features, I guess I could see your > > point. > > Mmmm.. unnecessary pain. Eye of the beholder. It's nice to not have to modify binaries with hard coded path strings in them, and instead just hardlink or symlink the local oddly named device to the system local name for the device. For tape devices, for example, the desire for tape rewind before access is really a site local policy preference, and is normally controlled through the device node -- and therefore device name used. THe "mt" command is relatively new, and is not really independent enough (as one example). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 19:49:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 499A537B400 for ; Thu, 4 Jul 2002 19:49:27 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BCEA43E09 for ; Thu, 4 Jul 2002 19:49:26 -0700 (PDT) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) by srv1.cosmo-project.de (8.12.3/8.12.3) with ESMTP id g652nJMa090592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Fri, 5 Jul 2002 04:49:23 +0200 (CEST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (localhost [IPv6:::1]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g652nIFJ043444 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 5 Jul 2002 04:49:18 +0200 (CEST)?g (envelope-from ticso@cicely5.cicely.de) Received: (from ticso@localhost) by cicely5.cicely.de (8.12.1/8.12.1/Submit) id g652nILU043443 for freebsd-current@freebsd.org; Fri, 5 Jul 2002 04:49:18 +0200 (CEST)?g (envelope-from ticso) Date: Fri, 5 Jul 2002 04:49:17 +0200 From: Bernd Walter To: freebsd-current@freebsd.org Subject: sshd login problem Message-ID: <20020705024917.GD40866@cicely5.cicely.de> Reply-To: ticso@cicely.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely5.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.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 sshd refuses my login: [51]cicely30> ssh -v c10 OpenSSH_3.1 FreeBSD localisations 20020318, SSH protocols 1.5/2.0, OpenSSL 0x0090603f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1007 geteuid 1007 anon 1 debug1: Connecting to cicely10.cicely.de [3ffe:400:8d0:301:200:92ff:fe94:f91] port 22. debug1: temporarily_use_uid: 1007/100 (e=1007) debug1: restore_uid debug1: temporarily_use_uid: 1007/100 (e=1007) debug1: restore_uid debug1: Connection established. debug1: identity file /var/home/ticso/.ssh/identity type 0 debug1: identity file /var/home/ticso/.ssh/id_rsa type 0 debug1: identity file /var/home/ticso/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.4p1 FreeBSD-20020702 debug1: match: OpenSSH_3.4p1 FreeBSD-20020702 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.1 FreeBSD localisations 20020318 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 135/256 debug1: bits set: 1633/3191 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'cicely10.cicely.de' is known and matches the DSA host key. debug1: Found key in /var/home/ticso/.ssh/known_hosts2:10 debug1: bits set: 1623/3191 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is publickey debug1: try pubkey: /var/home/ticso/.ssh/id_dsa debug1: input_userauth_pk_ok: pkalg ssh-dss blen 433 lastkey 0x806a350 hint 2 debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type Enter passphrase for key '/var/home/ticso/.ssh/id_dsa': debug1: read PEM private key done: type DSA debug1: ssh-userauth2 successful: method publickey debug1: channel 0: new [client-session] debug1: send channel open 0 debug1: Entering interactive session. debug1: ssh_session2_setup: id 0 debug1: channel request 0: pty-req debug1: channel request 0: shell debug1: fd 3 setting TCP_NODELAY debug1: channel 0: open confirm rwindow 0 rmax 32768 debug1: channel_free: channel 0: client-session, nchannels 1 Connection to cicely10.cicely.de closed by remote host. Connection to cicely10.cicely.de closed. debug1: Transferred: stdin 0, stdout 0, stderr 99 bytes in 0.3 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 299.1 debug1: Exit status -1 1.352u 0.081s 0:13.82 10.3% 78+229k 7+0io 5pf+0w Exit 255 On the console I read: Jul 5 04:37:51 cicely10 sshd[238]: fatal: login_get_lastlog: Cannot find account for uid 1007 Interesting as it already had known the homedir. The account is a NIS account which still works when loggin in via rlogin. Adding the acount localy works. cicely10 is an alpha running -current from 3. Jul. The kernel is a day younger. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 21:21:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E594137B400; Thu, 4 Jul 2002 21:21:14 -0700 (PDT) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4162A43E42; Thu, 4 Jul 2002 21:21:14 -0700 (PDT) (envelope-from bmilekic@angelica.unixdaemons.com) Received: from angelica.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.5/8.12.1) with ESMTP id g654KvdT006762; Fri, 5 Jul 2002 00:20:57 -0400 (EDT) X-Authentication-Warning: angelica.unixdaemons.com: Host bmilekic@localhost.unixdaemons.com [127.0.0.1] claimed to be angelica.unixdaemons.com Received: (from bmilekic@localhost) by angelica.unixdaemons.com (8.12.5/8.12.1/Submit) id g654KubO006761; Fri, 5 Jul 2002 00:20:56 -0400 (EDT) (envelope-from bmilekic) Date: Fri, 5 Jul 2002 00:20:56 -0400 From: Bosko Milekic To: Andrew Gallatin Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) Message-ID: <20020705002056.A5365@unixdaemons.com> References: <20020619090046.A2063@panzer.kdm.org> <20020619120641.A18434@unixdaemons.com> <15633.17238.109126.952673@grasshopper.cs.duke.edu> <20020619233721.A30669@unixdaemons.com> <15633.62357.79381.405511@grasshopper.cs.duke.edu> <20020620114511.A22413@unixdaemons.com> <15634.534.696063.241224@grasshopper.cs.duke.edu> <20020620134723.A22954@unixdaemons.com> <15652.46870.463359.853754@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: <15652.46870.463359.853754@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jul 04, 2002 at 04:59:02PM -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 Thu, Jul 04, 2002 at 04:59:02PM -0400, Andrew Gallatin wrote: > > I believe that the Intel chips do "virtual page caching" and that the > > logic that does the virtual -> physical address translation sits between > > the L2 cache and RAM. If that is indeed the case, then your idea of > > testing with virtually contiguous pages is a good one. > > Unfortunately, I don't know if the PIII is doing speculative > > cache-loads, but it could very well be the case. If it is and if in > > fact the chip does caching based on virtual addresses, then providing it > > with virtually contiguous address space may yield better results. If > > you try this, please let me know. I'm extremely interested in seeing > > the results! > > contigmalloc'ed private jumbo mbufs (same as bge, if_ti, etc): > > % iperf -c ugly-my -l 32k -fm > ------------------------------------------------------------ > Client connecting to ugly-my, TCP port 5001 > TCP window size: 0.2 MByte (default) > ------------------------------------------------------------ > [ 3] local 192.168.1.3 port 1031 connected with 192.168.1.4 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 2137 MBytes 1792 Mbits/sec > > > > malloc'ed, physically discontigous private jumbo mbufs: > > % iperf -c ugly-my -l 32k -fm > ------------------------------------------------------------ > Client connecting to ugly-my, TCP port 5001 > TCP window size: 0.2 MByte (default) > ------------------------------------------------------------ > [ 3] local 192.168.1.3 port 1029 connected with 192.168.1.4 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 2131 MBytes 1788 Mbits/sec > > > So I'd be willing to believe that the 4Mb/sec loss was due to > the extra overhead of setting up 2 additional DMAs. > > > So it looks like this idea would work. Yes, it certainly confirms the virtual-based caching assumptions. I would like to provide virtually contiguous large buffers and believe I can do that via mb_alloc... however, they would be several wired-down pages. Would this be in line with the requirements that these buffers would have, in your mind? (wired-down means that your buffers will come out exactly as they would out of malloc(), so if you were using malloc() already, I'm assuming that wired-down is OK). I think I can allocate the jumbo buffers via mb_alloc from the same map as I allocate clusters from - the clust_map - and keep them in buckets/slabs in per-CPU caches, like I do for mbufs and regular clusters right now. Luigi is in the process of doing some optimisation work around mb_alloc and I'll probably be doing the SMP-specific stuff after he's done so once that's taken care of, we can take a stab at this if you think it's worth it. > Drew Regards, -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 22:13:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A84FD37B400; Thu, 4 Jul 2002 22:13:26 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB9543E3B; Thu, 4 Jul 2002 22:13:25 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g655DMKi042257; Thu, 4 Jul 2002 23:13:22 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g655DMPZ042256; Thu, 4 Jul 2002 23:13:22 -0600 (MDT) (envelope-from ken) Date: Thu, 4 Jul 2002 23:13:21 -0600 From: "Kenneth D. Merry" To: Bosko Milekic Cc: Andrew Gallatin , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) Message-ID: <20020704231321.A42134@panzer.kdm.org> References: <20020619090046.A2063@panzer.kdm.org> <20020619120641.A18434@unixdaemons.com> <15633.17238.109126.952673@grasshopper.cs.duke.edu> <20020619233721.A30669@unixdaemons.com> <15633.62357.79381.405511@grasshopper.cs.duke.edu> <20020620114511.A22413@unixdaemons.com> <15634.534.696063.241224@grasshopper.cs.duke.edu> <20020620134723.A22954@unixdaemons.com> <15652.46870.463359.853754@grasshopper.cs.duke.edu> <20020705002056.A5365@unixdaemons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020705002056.A5365@unixdaemons.com>; from bmilekic@unixdaemons.com on Fri, Jul 05, 2002 at 12:20:56AM -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 Fri, Jul 05, 2002 at 00:20:56 -0400, Bosko Milekic wrote: > On Thu, Jul 04, 2002 at 04:59:02PM -0400, Andrew Gallatin wrote: > > > I believe that the Intel chips do "virtual page caching" and that the > > > logic that does the virtual -> physical address translation sits between > > > the L2 cache and RAM. If that is indeed the case, then your idea of > > > testing with virtually contiguous pages is a good one. > > > Unfortunately, I don't know if the PIII is doing speculative > > > cache-loads, but it could very well be the case. If it is and if in > > > fact the chip does caching based on virtual addresses, then providing it > > > with virtually contiguous address space may yield better results. If > > > you try this, please let me know. I'm extremely interested in seeing > > > the results! > > > > contigmalloc'ed private jumbo mbufs (same as bge, if_ti, etc): > > > > % iperf -c ugly-my -l 32k -fm > > ------------------------------------------------------------ > > Client connecting to ugly-my, TCP port 5001 > > TCP window size: 0.2 MByte (default) > > ------------------------------------------------------------ > > [ 3] local 192.168.1.3 port 1031 connected with 192.168.1.4 port 5001 > > [ ID] Interval Transfer Bandwidth > > [ 3] 0.0-10.0 sec 2137 MBytes 1792 Mbits/sec > > > > > > > > malloc'ed, physically discontigous private jumbo mbufs: > > > > % iperf -c ugly-my -l 32k -fm > > ------------------------------------------------------------ > > Client connecting to ugly-my, TCP port 5001 > > TCP window size: 0.2 MByte (default) > > ------------------------------------------------------------ > > [ 3] local 192.168.1.3 port 1029 connected with 192.168.1.4 port 5001 > > [ ID] Interval Transfer Bandwidth > > [ 3] 0.0-10.0 sec 2131 MBytes 1788 Mbits/sec > > > > > > So I'd be willing to believe that the 4Mb/sec loss was due to > > the extra overhead of setting up 2 additional DMAs. > > > > > > So it looks like this idea would work. > > Yes, it certainly confirms the virtual-based caching assumptions. I > would like to provide virtually contiguous large buffers and believe I > can do that via mb_alloc... however, they would be several wired-down > pages. Would this be in line with the requirements that these buffers > would have, in your mind? (wired-down means that your buffers will > come out exactly as they would out of malloc(), so if you were using > malloc() already, I'm assuming that wired-down is OK). > > I think I can allocate the jumbo buffers via mb_alloc from the same map > as I allocate clusters from - the clust_map - and keep them in > buckets/slabs in per-CPU caches, like I do for mbufs and regular > clusters right now. Luigi is in the process of doing some optimisation > work around mb_alloc and I'll probably be doing the SMP-specific stuff > after he's done so once that's taken care of, we can take a stab at > this if you think it's worth it. If you do implement this, it would also be nice to have some sort of standardized page-walking function to extract the physical addresses. (Otherwise every driver will end up implementing its own loop to do it.) We also may want to examine what sort of guarantees, if any, we can make about the physical page alignment of the allocated mbuf. i.e. if we can guarantee that the mbuf data segment will start on a physical page boundary (if it is at least a page in size), that would allow device drivers to be able to guarantee that they could fit a jumbo frame (9000 bytes) into 3 scatter/gather segments on an i386. The number of scatter/gather segments used is important for some boards, like ti(4), because they have a limited number of scatter/gather segments available. In the case of ti(4), it is 4 S/G segments, which is enough to handle the maximum number of physical data chunks it would take to compose a 9K virtual buffer. (You could start in the middle of a page, have two complete pages, and then end with a partial page.) I suppose it would be good to see what NIC drivers in the tree can receive into or send from multiple chunks of data, and what their requirements are. (how many scatter/gather segments they can handle, what is the maximum MTU, etc.) 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 Thu Jul 4 22:51: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91E8037B400; Thu, 4 Jul 2002 22:50:53 -0700 (PDT) Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F9EE43E31; Thu, 4 Jul 2002 22:50:53 -0700 (PDT) (envelope-from l4rtanker71@hotmail.com) Received: from dialup-207-232-91-141.omaha.radiks.net ([207.232.91.141] helo=jfs3yi62) by smtp6.mindspring.com with smtp (Exim 3.33 #1) id 17QLFG-00032W-00; Fri, 05 Jul 2002 01:03:03 -0400 From: l4rtanker71@hotmail.com To: xtra66@hotmail.com Subject: Trial Offer Date: Tue, 04 Jul 2000 22:22:39 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_44FE_000065B3.00000723" X-Priority: 3 X-MSMail-Priority: Normal Reply-To: l4rtanker71@hotmail.com Message-Id: 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 ------=_NextPart_000_44FE_000065B3.00000723 Content-Type: text/html; Dietary Supplement

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 4 23:50:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2853D37B400 for ; Thu, 4 Jul 2002 23:50:54 -0700 (PDT) Received: from a.smtp-out.sonic.net (a.smtp-out.sonic.net [208.201.224.38]) by mx1.FreeBSD.org (Postfix) with SMTP id AF94D43E31 for ; Thu, 4 Jul 2002 23:50:53 -0700 (PDT) (envelope-from sonicmail@blarf.homeip.net) Received: (qmail 14454 invoked from network); 5 Jul 2002 06:50:53 -0000 Received: from turbo.sonic.net (208.201.224.26) by a.smtp-out.sonic.net with SMTP; 5 Jul 2002 06:50:53 -0000 Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by turbo.sonic.net (8.11.6/8.8.5) with ESMTP id g656orr26718 for ; Thu, 4 Jul 2002 23:50:53 -0700 X-envelope-info: Received: by blarf.homeip.net (Postfix, from userid 1006) id 2357B17D6; Thu, 4 Jul 2002 23:50:52 -0700 (PDT) Date: Thu, 4 Jul 2002 23:50:52 -0700 From: Alex Zepeda To: current@freebsd.org Subject: ACPI woes again.. Message-ID: <20020705065052.GA412@blarf.homeip.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 So thanks to a rather lacking support team at Epox (uh hey, reset your BIOS settings it should be a-okay) and a very helpful Ducrot Bruno.. it was determined that my DSDT was coded haphazardly. A few nips and tucks, and a hardcoded table later, my kernel booted again (where before it hung after probing a thermal zone). This worked all great, as I'd just patch the kernel after every cvsup. 'Cept now that the ACPI code (rather tbget.c) has been restructured enough, I'm not quite sure how to get a new kernel booted. Anyone else out there running an EPoX KP6-BS with -current? Should I just go about disabling ACPI (in favor of APM?)? ... Help? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 0: 0:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD69737B400 for ; Fri, 5 Jul 2002 00:00:50 -0700 (PDT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B616F43E52 for ; Fri, 5 Jul 2002 00:00:49 -0700 (PDT) (envelope-from takawata@axe-inc.co.jp) Received: from axe-inc.co.jp (takawata@[192.47.224.47]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with ESMTP id QAA26015; Fri, 5 Jul 2002 16:00:44 +0900 (JST) Message-Id: <200207050700.QAA26015@axe-inc.co.jp> To: Alex Zepeda Cc: current@freebsd.org Subject: Re: ACPI woes again.. In-reply-to: Your message of "Thu, 04 Jul 2002 23:50:52 MST." <20020705065052.GA412@blarf.homeip.net> Date: Fri, 05 Jul 2002 16:01:08 +0900 From: Takanori Watanabe 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 <20020705065052.GA412@blarf.homeip.net>, Alex Zepeda wrote: >So thanks to a rather lacking support team at Epox (uh hey, reset your >BIOS settings it should be a-okay) and a very helpful Ducrot Bruno.. it >was determined that my DSDT was coded haphazardly. A few nips and tucks, >and a hardcoded table later, my kernel booted again (where before it hung >after probing a thermal zone). > >This worked all great, as I'd just patch the kernel after every cvsup. > >'Cept now that the ACPI code (rather tbget.c) has been restructured >enough, I'm not quite sure how to get a new kernel booted. > >Anyone else out there running an EPoX KP6-BS with -current? > >Should I just go about disabling ACPI (in favor of APM?)? > We already have a way to use your own bytecode without recompiling. Simply put your AML file to /boot/acpi_dsdt.aml and add 'acpi_dsdt_load="YES" to your /boot/loader.conf (Other necessary setting exist in /boot/default/loader.conf) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 0:16:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4A9D37B400 for ; Fri, 5 Jul 2002 00:16:42 -0700 (PDT) Received: from b.smtp-out.sonic.net (b.smtp-out.sonic.net [208.201.224.39]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D19A43E09 for ; Fri, 5 Jul 2002 00:16:42 -0700 (PDT) (envelope-from sonicmail@blarf.homeip.net) Received: (qmail 1958 invoked from network); 5 Jul 2002 07:16:41 -0000 Received: from prop.sonic.net (208.201.224.193) by b.smtp-out.sonic.net with SMTP; 5 Jul 2002 07:16:41 -0000 Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by prop.sonic.net (8.11.6/8.8.5) with ESMTP id g657Gft18179; Fri, 5 Jul 2002 00:16:41 -0700 X-envelope-info: Received: by blarf.homeip.net (Postfix, from userid 1006) id 81E541A5C; Fri, 5 Jul 2002 00:16:40 -0700 (PDT) Date: Fri, 5 Jul 2002 00:16:40 -0700 From: Alex Zepeda To: Takanori Watanabe , current@freebsd.org Subject: Re: ACPI woes again.. Message-ID: <20020705071640.GA739@blarf.homeip.net> References: <20020705065052.GA412@blarf.homeip.net> <200207050700.QAA26015@axe-inc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207050700.QAA26015@axe-inc.co.jp> 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, Jul 05, 2002 at 04:01:08PM +0900, Takanori Watanabe wrote: > We already have a way to use your own bytecode without recompiling. > Simply put your AML file to /boot/acpi_dsdt.aml and add 'acpi_dsdt_load="YES" > to your /boot/loader.conf (Other necessary setting exist in /boot/default/loader.conf) Cool! I can boot now!! When will this make it into the man page? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 0:19:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADFF737B400 for ; Fri, 5 Jul 2002 00:19:34 -0700 (PDT) Received: from a.smtp-out.sonic.net (a.smtp-out.sonic.net [208.201.224.38]) by mx1.FreeBSD.org (Postfix) with SMTP id 3F85A43E09 for ; Fri, 5 Jul 2002 00:19:34 -0700 (PDT) (envelope-from sonicmail@blarf.homeip.net) Received: (qmail 15892 invoked from network); 5 Jul 2002 07:19:34 -0000 Received: from tempest.sonic.net (208.201.224.25) by a.smtp-out.sonic.net with SMTP; 5 Jul 2002 07:19:34 -0000 Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by tempest.sonic.net (8.11.6/8.8.5) with ESMTP id g657JXP29445; Fri, 5 Jul 2002 00:19:33 -0700 X-envelope-info: Received: by blarf.homeip.net (Postfix, from userid 1006) id 43BE91A5C; Fri, 5 Jul 2002 00:19:33 -0700 (PDT) Date: Fri, 5 Jul 2002 00:19:33 -0700 From: Alex Zepeda To: Kenneth Culver , current@freebsd.org Subject: Re: ipfw rule changes? Message-ID: <20020705071933.GB739@blarf.homeip.net> References: <20020704133324.A633-100000@alpha.yumyumyum.org> <20020704133517.R633-100000@alpha.yumyumyum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020704133517.R633-100000@alpha.yumyumyum.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 Thu, Jul 04, 2002 at 01:38:12PM -0400, Kenneth Culver wrote: > alpha:~:# ipfw queue 1 config pipe 1 mask dst-ip 0xffffffff > ipfw: unrecognised option ``1'' Similarly: blarf:~#ipfw /etc/ipv4.firewall ipfw: unrecognised option [-1] icmptype Or if I change it to icmptypes (as it seems to be listed in the man page) I get: ipfw: unrecognised option [41] icmptypes Hmm. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 2:39:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6490A37B400; Fri, 5 Jul 2002 02:39:13 -0700 (PDT) Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AC7643E09; Fri, 5 Jul 2002 02:39:12 -0700 (PDT) (envelope-from vova@express.ru) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 17QPXk-0000FY-00; Fri, 05 Jul 2002 13:38:24 +0400 Subject: Re: About DEVFS (was: Re: About GEOM...) From: "Vladimir B. " Grebenschikov To: Terry Lambert Cc: Daniel O'Connor , Bruce Evans , Greg 'groggy' Lehey , Poul-Henning Kamp , Mario Goebbels , "current@freebsd.org" In-Reply-To: <3D2506F9.8B34FD80@mindspring.com> References: <20020704210304.Y21619-100000@gamplex.bde.org> <3D24BB6E.3829314A@mindspring.com> <1025835014.4223.5.camel@chowder.gsoft.com.au> <3D2506F9.8B34FD80@mindspring.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.7 Date: 05 Jul 2002 13:38:24 +0400 Message-Id: <1025861904.810.3.camel@vbook.express.ru> Mime-Version: 1.0 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 =F7 Fri, 05.07.2002, =D7 06:39, Terry Lambert =CE=C1=D0=C9=D3=C1=CC: > > Loader? > > ie on shutdown write a list of permissions etc into a file which the > > loader can slurp up next boot and shove into the kernel and be parsed. >=20 > This really doesn't work very well. You end up with two sets of > data. Having done something like this in practice, and had to live > with the aftermath, I don't recommend it (at all). May be same mechanism as hints, like: hint.sio.0.mode=3D0622 why not ? Symantic very similar (there are some kernel-hardcoded values and some loader-supplied) > > > But overall, it seems to be a move forward. =20 agree. > -- Terry =20 --=20 Vladimir B. Grebenschikov vova@sw.ru, SWsoft, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 2:45:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F61137B400 for ; Fri, 5 Jul 2002 02:45:39 -0700 (PDT) Received: from imailg2.svr.pol.co.uk (imailg2.svr.pol.co.uk [195.92.195.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34DBF43E09 for ; Fri, 5 Jul 2002 02:45:38 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-355.alakazam.dialup.pol.co.uk ([217.135.12.99] helo=mailgate.originative.co.uk) by imailg2.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17QPei-0008En-00 for current@freebsd.org; Fri, 05 Jul 2002 10:45:37 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id 754091D13D for ; Fri, 5 Jul 2002 10:45:33 +0100 (BST) Subject: Removing perl in make world From: Paul Richards To: current@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Jul 2002 10:45:41 +0100 Message-Id: <1025862341.1573.40.camel@lobster.originative.co.uk> Mime-Version: 1.0 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 think we should add a target to make world that checks for the existence of an old base install of Perl and removes it if it exists. As a general principle, if we do things like remove code during -current development then make world needs to cater for that change. The idea of make world is that what you get at the end of it is a pristine install of a snapshot of FreeBSD from the current branch. The bootstrap target was originally added for this purpose, to deal with issues during releases i.e. to bootstrap from one version of current to another. It's got misunderstood along the way to mean bootstrapping tools needed early in the build process. I'd like to resurrect it's original meaning and add code to clean out old versions of Perl. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 2:45:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F242837B400 for ; Fri, 5 Jul 2002 02:45:46 -0700 (PDT) Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C69FF43E31 for ; Fri, 5 Jul 2002 02:45:45 -0700 (PDT) (envelope-from takawata@axe-inc.co.jp) Received: from axe-inc.co.jp (takawata@[192.47.224.47]) by axe-inc.co.jp (8.9.3+3.2W/3.7W) with ESMTP id SAA28267; Fri, 5 Jul 2002 18:45:42 +0900 (JST) Message-Id: <200207050945.SAA28267@axe-inc.co.jp> To: Alex Zepeda Cc: current@freebsd.org Subject: Re: ACPI woes again.. In-reply-to: Your message of "Fri, 05 Jul 2002 00:16:40 MST." <20020705071640.GA739@blarf.homeip.net> Date: Fri, 05 Jul 2002 18:46:05 +0900 From: Takanori Watanabe 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 <20020705071640.GA739@blarf.homeip.net>, Alex Zepeda wrote: >On Fri, Jul 05, 2002 at 04:01:08PM +0900, Takanori Watanabe wrote: > >> We already have a way to use your own bytecode without recompiling. >> Simply put your AML file to /boot/acpi_dsdt.aml and add 'acpi_dsdt_load="YES >" >> to your /boot/loader.conf (Other necessary setting exist in /boot/default/lo >ader.conf) > >Cool! I can boot now!! > >When will this make it into the man page? Would you review this description? --- acpi.4 Fri Jul 5 17:41:29 2002 +++ acpi.4.new Fri Jul 5 18:37:27 2002 @@ -258,10 +258,33 @@ bus/children scan of the namespace. The ACPI CA code will still know about the avoided region. +.Sh OVERRIDING YOUR BIOS BYTECODE +ACPI interprets bytecode named AML, ACPI Machine Language, provided by BIOS +vendor as memory image at boot time. Sometimes, the AML code contains +problem that is not appeared in Microsoft implement. So we provide a way +to override it with your own AML code. +.Pp +In order to load your AML code, +you must edit +.Pa /boot/loader.conf +and +include the follwing lines. +.Bd -literal -offset indent +acpi_dsdt_load="YES" +acpi_dsdt_name="/boot/acpi_dsdt.aml" #You may change the name. +.Ed +.Pp +In order to prepare your AML code, you will require +.Xr acpidump 8 , +.Xr iasl 1 +in devel/acpicatools port, and some ACPI knowledge. + .Sh COMPATIBILITY ACPI is only found/supported on Intel platforms (i386/IA32 and IA64). .Sh SEE ALSO .Xr config 8 , +.Xr loader.conf 5 , +.Xr acpidump 8 , .Xr acpi 9 .Sh AUTHORS .An -nosplit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 2:52: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF1EF37B400 for ; Fri, 5 Jul 2002 02:52:04 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2900043E09 for ; Fri, 5 Jul 2002 02:52:03 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17QPlq-0000wH-00; Fri, 05 Jul 2002 11:52:58 +0200 Date: Fri, 5 Jul 2002 11:52:58 +0200 From: Sheldon Hearn To: Paul Richards Cc: current@freebsd.org Subject: Re: Removing perl in make world Message-ID: <20020705095258.GC775@starjuice.net> Mail-Followup-To: Paul Richards , current@freebsd.org References: <1025862341.1573.40.camel@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1025862341.1573.40.camel@lobster.originative.co.uk> User-Agent: Mutt/1.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 On (2002/07/05 10:45), Paul Richards wrote: > I think we should add a target to make world that checks for the > existence of an old base install of Perl and removes it if it exists. I don't like this idea. > As a general principle, if we do things like remove code during -current > development then make world needs to cater for that change. The idea of > make world is that what you get at the end of it is a pristine install > of a snapshot of FreeBSD from the current branch. No, the idea of `make world' is to upgrade my system in the way that I tell it to. Having the world target leave perl behind was critical for me when I upgraded my box. > I'd like to resurrect it's original meaning and add code to clean out > old versions of Perl. This would not fit in with the rest of the world target, which doesn't clean out stale headers, stale libraries or stale binaries. Special-casing certain things will surprise people. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 3:16: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 889C337B400 for ; Fri, 5 Jul 2002 03:15:58 -0700 (PDT) Received: from cmailg4.svr.pol.co.uk (cmailg4.svr.pol.co.uk [195.92.195.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE2A43E58 for ; Fri, 5 Jul 2002 03:15:57 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-1241.arcanine.dialup.pol.co.uk ([217.135.25.217] helo=mailgate.originative.co.uk) by cmailg4.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17QQ83-0008Kc-00; Fri, 05 Jul 2002 11:15:55 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id 985341D13D; Fri, 5 Jul 2002 11:15:52 +0100 (BST) Subject: Re: Removing perl in make world From: Paul Richards To: Sheldon Hearn Cc: current@freebsd.org In-Reply-To: <20020705095258.GC775@starjuice.net> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Jul 2002 11:16:00 +0100 Message-Id: <1025864161.1573.45.camel@lobster.originative.co.uk> Mime-Version: 1.0 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, 2002-07-05 at 10:52, Sheldon Hearn wrote: > On (2002/07/05 10:45), Paul Richards wrote: > > > I think we should add a target to make world that checks for the > > existence of an old base install of Perl and removes it if it exists. > > I don't like this idea. > > > As a general principle, if we do things like remove code during -current > > development then make world needs to cater for that change. The idea of > > make world is that what you get at the end of it is a pristine install > > of a snapshot of FreeBSD from the current branch. > > No, the idea of `make world' is to upgrade my system in the way that I > tell it to. I don't think it is. That might be what you've become used to, but that's not what make world was designed to do. It goes to great lengths to make sure that you get a current version of the development branch that's all built with the current bits. As a current developer, you need to see what -current looks like and not what current on top of a lot of other stuff that hides bugs looks like. > Having the world target leave perl behind was critical for me when I > upgraded my box. Why? > > I'd like to resurrect it's original meaning and add code to clean out > > old versions of Perl. > > This would not fit in with the rest of the world target, which doesn't > clean out stale headers, stale libraries or stale binaries. > Special-casing certain things will surprise people. Yeah, well I think it should. I wonder how many people are actually running a real snapshot of current as opposed to a variation of X iterations of current over a period of time. I recently cleaned out a load of stale libraries and I was quite surprised to find that what I thought was a version of current updated daily was not in fact that at all since a lot of my binaries were still linked to much older libraries so I was running a pseudo current, partly up to date and partly not. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 3:30:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A05337B400 for ; Fri, 5 Jul 2002 03:30:54 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.139.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F4AA43E31 for ; Fri, 5 Jul 2002 03:30:52 -0700 (PDT) (envelope-from mark@grimreaper.grondar.org) Received: from storm.FreeBSD.org.uk (uucp@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.5/8.12.5) with ESMTP id g65AUoCE066146; Fri, 5 Jul 2002 11:30:50 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Received: (from uucp@localhost) by storm.FreeBSD.org.uk (8.12.5/8.12.5/Submit) with UUCP id g65AUoPA066145; Fri, 5 Jul 2002 11:30:50 +0100 (BST) Received: from grimreaper.grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.5/8.12.5) with ESMTP id g65ATUii003713; Fri, 5 Jul 2002 11:29:30 +0100 (BST) (envelope-from mark@grimreaper.grondar.org) Message-Id: <200207051029.g65ATUii003713@grimreaper.grondar.org> To: Paul Richards Cc: current@FreeBSD.ORG Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> In-Reply-To: <1025862341.1573.40.camel@lobster.originative.co.uk> ; from Paul Richards "05 Jul 2002 10:45:41 BST." Date: Fri, 05 Jul 2002 11:29:30 +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 > I think we should add a target to make world that checks for the > existence of an old base install of Perl and removes it if it exists. I agree that we may need a tool to do this, but I don't agree that it gets done automatically by "make world". > As a general principle, if we do things like remove code during -current > development then make world needs to cater for that change. The idea of > make world is that what you get at the end of it is a pristine install > of a snapshot of FreeBSD from the current branch. I disagree. This is force-feeding the user base too much. > The bootstrap target was originally added for this purpose, to deal with > issues during releases i.e. to bootstrap from one version of current to > another. It's got misunderstood along the way to mean bootstrapping > tools needed early in the build process. > > I'd like to resurrect it's original meaning and add code to clean out > old versions of Perl. Lots of things get deleted from current as time goes by; headers, libraries, applets, etc. It is the responsibility of the CURRENT builder/user to remove them as she sees fit. Our resposibility as developers goes no further than to help provide removal tools/techniques (I use "find ${DIR} -type f -ctime +1 -delete -print"), and guidance. Of course, there are counterprecedents (libtelnet is one), but these are the exception, and are unlikely to trample all over a user's carefully crafted installation. 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 Fri Jul 5 3:47:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A720F37B400 for ; Fri, 5 Jul 2002 03:47:07 -0700 (PDT) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1169043E4A for ; Fri, 5 Jul 2002 03:47:07 -0700 (PDT) (envelope-from corecode@corecode.ath.cx) Received: from fwd00.sul.t-online.de by mailout03.sul.t-online.com with smtp id 17QQc7-00041C-0B; Fri, 05 Jul 2002 12:46:59 +0200 Received: from spirit.zuhause.stoert.net (320050403952-0001@[80.128.118.41]) by fmrl00.sul.t-online.com with esmtp id 17QQc1-0YcVloC; Fri, 5 Jul 2002 12:46:53 +0200 Received: from elevation.uni.stoert.net (elevation.uni.stoert.net [10.150.180.177]) by spirit.zuhause.stoert.net (8.11.6/8.11.6) with ESMTP id g65Akq898152; Fri, 5 Jul 2002 12:46:52 +0200 (CEST) (envelope-from corecode@elevation.uni.stoert.net) Received: (from corecode@localhost) by elevation.uni.stoert.net (8.12.3/8.12.3/Submit) id g65AkqlQ000485; Fri, 5 Jul 2002 12:46:52 +0200 (CEST) (envelope-from corecode) Date: Fri, 5 Jul 2002 12:46:49 +0200 From: "Simon 'corecode' Schubert" To: Paul Richards Cc: current@FreeBSD.ORG Subject: Re: Removing perl in make world Message-Id: <20020705124649.0e7f2a43.corecode@corecode.ath.cx> In-Reply-To: <1025862341.1573.40.camel@lobster.originative.co.uk> References: <1025862341.1573.40.camel@lobster.originative.co.uk> X-Mailer: Sylpheed version 0.7.8claws (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=.U(Ivj..:kTVx3b" X-Sender: 320050403952-0001@t-dialin.net 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 --=.U(Ivj..:kTVx3b Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On 05 Jul 2002 10:45:41 +0100 Paul Richards wrote: > As a general principle, if we do things like remove code during -current > development then make world needs to cater for that change. The idea of > make world is that what you get at the end of it is a pristine install > of a snapshot of FreeBSD from the current branch. i thought of this several times. in fact we need a file registration thing like the ports have so that old (moved or deleted) stray files can be easily cleaned out. i don't know how far libh is done with handling these things and how that can be incorporated into the installworld process (i.e. file registration). of course this applies for -stable too cheers simon -- /"\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News --=.U(Ivj..:kTVx3b Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9JXkcr5S+dk6z85oRAlAZAJ4udzE88lXo/k7AnAFiSHTFreWcggCePEOQ U2QpNrd92P9bGslUwxZ3deA= =Dq1N -----END PGP SIGNATURE----- --=.U(Ivj..:kTVx3b-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5: 8:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C573B37B49B; Fri, 5 Jul 2002 05:08:39 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E33243EB7; Fri, 5 Jul 2002 05:08:11 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0029.cvx22-bradley.dialup.earthlink.net ([209.179.198.29] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QRrM-0002yk-00; Fri, 05 Jul 2002 08:06:49 -0400 Message-ID: <3D258BAE.3C77B9D9@mindspring.com> Date: Fri, 05 Jul 2002 05:06: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: "Vladimir B. Grebenschikov" Cc: Daniel O'Connor , Bruce Evans , Greg 'groggy' Lehey , Poul-Henning Kamp , Mario Goebbels , "current@freebsd.org" Subject: Re: About DEVFS (was: Re: About GEOM...) References: <20020704210304.Y21619-100000@gamplex.bde.org> <3D24BB6E.3829314A@mindspring.com> <1025835014.4223.5.camel@chowder.gsoft.com.au> <3D2506F9.8B34FD80@mindspring.com> <1025861904.810.3.camel@vbook.express.ru> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable 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 "Vladimir B. Grebenschikov" wrote: > =F7 Fri, 05.07.2002, =D7 06:39, Terry Lambert =CE=C1=D0=C9=D3=C1=CC: > > > Loader? > > > ie on shutdown write a list of permissions etc into a file which th= e > > > loader can slurp up next boot and shove into the kernel and be pars= ed. > > > > This really doesn't work very well. You end up with two sets of > > data. Having done something like this in practice, and had to live > > with the aftermath, I don't recommend it (at all). > = > May be same mechanism as hints, like: > hint.sio.0.mode=3D0622 > = > why not ? Symantic very similar (there are some kernel-hardcoded values= > and some loader-supplied) Because the proper order is: device arrival creation of device node ... deletion of device node device departure And you can't get that, unless you have software control of the device eject mechanism -- and *only* software control (e.g. like the Macintosh floppy drives); the closest you can get to this with a PCMCIA device is to treat the removal notification you get from the shorter pins no longer being connected as a "highest priority" interrupt that invalidates the device, and removed the node. You're never going to get that with Bruce's "devd" approach, which would need to depend on either *real* RT scheduling to get rid of the device (not possible with PC hardware, actually, since you can only guarantee one process at RT, and then only with Djikstra's Banker's Algorithm), or on letting invalid operations proceed to hard failure, with recovery. If you check the archives from two years ago, you will see a long PCMCIA discussion, with the conclusion being a reluctant admission that it's possible to do it right, but is very difficult. By going the "devd" route, you *guarantee* that no one in the future can expend that effort, and make things "work right". See the archived discussion for more details; there no reason to repeat it all again, particularly since most of the very knowledgable PCMCIA people in that discussion are no longer around. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5: 9:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 995AD37B405 for ; Fri, 5 Jul 2002 05:09:11 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED4A643E3B for ; Fri, 5 Jul 2002 05:09:10 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0029.cvx22-bradley.dialup.earthlink.net ([209.179.198.29] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QRtZ-0004MR-00; Fri, 05 Jul 2002 08:09:06 -0400 Message-ID: <3D258C38.9E26407@mindspring.com> Date: Fri, 05 Jul 2002 05:08:24 -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: Takanori Watanabe Cc: Alex Zepeda , current@freebsd.org Subject: Re: ACPI woes again.. References: <200207050945.SAA28267@axe-inc.co.jp> 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 Takanori Watanabe wrote: > +.Sh OVERRIDING YOUR BIOS BYTECODE > +ACPI interprets bytecode named AML, ACPI Machine Language, provided by BIOS > +vendor as memory image at boot time. Sometimes, the AML code contains > +problem that is not appeared in Microsoft implement. So we provide a way > +to override it with your own AML code. > +.Pp How does Windows deal with hardware that has this problem? Do they use a "rogues" list, and replace the AML, too (only automatically)? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5: 9:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6308337B407; Fri, 5 Jul 2002 05:09:22 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 239FA43E5E; Fri, 5 Jul 2002 05:09:20 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 IAA20605; Fri, 5 Jul 2002 08:09:17 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g65C8l928851; Fri, 5 Jul 2002 08:08:47 -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: <15653.35919.24295.698563@grasshopper.cs.duke.edu> Date: Fri, 5 Jul 2002 08:08:47 -0400 (EDT) To: Bosko Milekic Cc: "Kenneth D. Merry" , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) In-Reply-To: <20020705002056.A5365@unixdaemons.com> References: <20020619090046.A2063@panzer.kdm.org> <20020619120641.A18434@unixdaemons.com> <15633.17238.109126.952673@grasshopper.cs.duke.edu> <20020619233721.A30669@unixdaemons.com> <15633.62357.79381.405511@grasshopper.cs.duke.edu> <20020620114511.A22413@unixdaemons.com> <15634.534.696063.241224@grasshopper.cs.duke.edu> <20020620134723.A22954@unixdaemons.com> <15652.46870.463359.853754@grasshopper.cs.duke.edu> <20020705002056.A5365@unixdaemons.com> 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 Bosko Milekic writes: > > Yes, it certainly confirms the virtual-based caching assumptions. I > would like to provide virtually contiguous large buffers and believe I > can do that via mb_alloc... however, they would be several wired-down > pages. Would this be in line with the requirements that these buffers > would have, in your mind? (wired-down means that your buffers will > come out exactly as they would out of malloc(), so if you were using > malloc() already, I'm assuming that wired-down is OK). I'd use these virtually contiguous, physically discontigous mbufs for GigE drivers which support jumbo frames and multiple recv descripters, but are incapable of doing header-splitting, or any other sort of useful framing (almost all of them, I think). From that perspective, it doesn't really matter what the mbufs look like internally. > I think I can allocate the jumbo buffers via mb_alloc from the same map > as I allocate clusters from - the clust_map - and keep them in > buckets/slabs in per-CPU caches, like I do for mbufs and regular > clusters right now. Luigi is in the process of doing some optimisation > work around mb_alloc and I'll probably be doing the SMP-specific stuff > after he's done so once that's taken care of, we can take a stab at > this if you think it's worth it. Would this be easier or harder than simple, physically contiguous buffers? I think that its only worth doing if its easier to manage at the system level, otherwise you might as well use physically contiguous mbufs. My main goal is to see the per-driver cache's of physical memory disappear ;) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5:21:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFB0237B400; Fri, 5 Jul 2002 05:21:29 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 240D643E3B; Fri, 5 Jul 2002 05:21:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 IAA20554; Fri, 5 Jul 2002 08:04:04 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g65C3Y928844; Fri, 5 Jul 2002 08:03:34 -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: <15653.35606.290023.621040@grasshopper.cs.duke.edu> Date: Fri, 5 Jul 2002 08:03:34 -0400 (EDT) To: "Kenneth D. Merry" Cc: Bosko Milekic , current@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: virtually contig jumbo mbufs (was Re: new zero copy sockets snapshot) In-Reply-To: <20020704231321.A42134@panzer.kdm.org> References: <20020619090046.A2063@panzer.kdm.org> <20020619120641.A18434@unixdaemons.com> <15633.17238.109126.952673@grasshopper.cs.duke.edu> <20020619233721.A30669@unixdaemons.com> <15633.62357.79381.405511@grasshopper.cs.duke.edu> <20020620114511.A22413@unixdaemons.com> <15634.534.696063.241224@grasshopper.cs.duke.edu> <20020620134723.A22954@unixdaemons.com> <15652.46870.463359.853754@grasshopper.cs.duke.edu> <20020705002056.A5365@unixdaemons.com> <20020704231321.A42134@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: <...> > > Yes, it certainly confirms the virtual-based caching assumptions. I > > would like to provide virtually contiguous large buffers and believe I > > can do that via mb_alloc... however, they would be several wired-down > > pages. Would this be in line with the requirements that these buffers > > would have, in your mind? (wired-down means that your buffers will > > come out exactly as they would out of malloc(), so if you were using > > malloc() already, I'm assuming that wired-down is OK). > > > > I think I can allocate the jumbo buffers via mb_alloc from the same map > > as I allocate clusters from - the clust_map - and keep them in > > buckets/slabs in per-CPU caches, like I do for mbufs and regular > > clusters right now. Luigi is in the process of doing some optimisation > > work around mb_alloc and I'll probably be doing the SMP-specific stuff > > after he's done so once that's taken care of, we can take a stab at > > this if you think it's worth it. > > If you do implement this, it would also be nice to have some sort of > standardized page-walking function to extract the physical addresses. > (Otherwise every driver will end up implementing its own loop to do it.) Good point. But this sounds like it belongs as a part of the (currently unimplemented) busdma infastructure for mbufs. > We also may want to examine what sort of guarantees, if any, we can make > about the physical page alignment of the allocated mbuf. i.e. if we can > guarantee that the mbuf data segment will start on a physical page boundary > (if it is at least a page in size), that would allow device drivers to be > able to guarantee that they could fit a jumbo frame (9000 bytes) into 3 > scatter/gather segments on an i386. > > The number of scatter/gather segments used is important for some boards, > like ti(4), because they have a limited number of scatter/gather segments > available. In the case of ti(4), it is 4 S/G segments, which is enough to > handle the maximum number of physical data chunks it would take to compose > a 9K virtual buffer. (You could start in the middle of a page, have two > complete pages, and then end with a partial page.) > > I suppose it would be good to see what NIC drivers in the tree can receive > into or send from multiple chunks of data, and what their requirements are. > (how many scatter/gather segments they can handle, what is the maximum MTU, > etc.) If you're just looking at the code, then this would be hard. All the current drivers (with the exception of em) are coded to take one physically contiguous private buffer. I'm pretty sure that most of them are capable of doing scatter DMA, but I don't have the programming docs. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5:23:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BFCE37B400 for ; Fri, 5 Jul 2002 05:23:16 -0700 (PDT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id B28C443E4A for ; Fri, 5 Jul 2002 05:23:15 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0029.cvx22-bradley.dialup.earthlink.net ([209.179.198.29] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QS77-0002v8-00; Fri, 05 Jul 2002 08:23:06 -0400 Message-ID: <3D258F80.BD86F9D0@mindspring.com> Date: Fri, 05 Jul 2002 05:22:24 -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: Sheldon Hearn Cc: Paul Richards , current@freebsd.org Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.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 Sheldon Hearn wrote: > On (2002/07/05 10:45), Paul Richards wrote: > > I think we should add a target to make world that checks for the > > existence of an old base install of Perl and removes it if it exists. > > I don't like this idea. There are a lot of funny things one could say at this point... but removing something as part of an install process really needs to be avoided. > > As a general principle, if we do things like remove code during -current > > development then make world needs to cater for that change. The idea of > > make world is that what you get at the end of it is a pristine install > > of a snapshot of FreeBSD from the current branch. This sort of implies that after a "make installworld", a FreeBSD box is magically in a pristine condition -- except for configuration data and configuration defaults, and the password file, and other things in the /etc directory and ... etc.. This might be an OK goal, but as things stand, configuration data is insufficiently seperate from code in FreeBSD, and this is really not an option at this time. > No, the idea of `make world' is to upgrade my system in the way that I > tell it to. > > Having the world target leave perl behind was critical for me when I > upgraded my box. There are amusing things to say about this as well. One point that should be brought up, though, is that the reason perl was diked out if the base system is that perl itself was growing in a rapid and uncontrolled fashion, much like cancer, and there was no such thing as "core perl" without a lot of things that tended to add security holes (e.g. CGI perl modules, etc.). What this basically means is that, whatever you were left with after the install-based upgrade -- it wasn't officially perl. You are probably better off forcing it to be upgraded at the same time. Unfortunately, this isn't automated, and would require major surgery on the install tools to make it so. Diking it out looks more correct; too bad there's not a "prune" option, as in CVS, that is on by default, but can be turned off. > > I'd like to resurrect it's original meaning and add code to clean out > > old versions of Perl. > > This would not fit in with the rest of the world target, which doesn't > clean out stale headers, stale libraries or stale binaries. > Special-casing certain things will surprise people. Headers and libraries arguably should be removed, so as to avoid errors; not ports headers or libraries -- which aren't in the installation target paths in the first place -- but things like deprecated system headers, etc.. Note that this is really problematic, since there are optional install components, such as binary backward compatability libraries that are installed into system directories, such as /usr/lib, that aren't technically the result of the build process itself. Header files under /usr/include are pretty straight forward, as far as that goes, though, unless they overlap components that get installed for binary compatability (I don't think the tools actually support building for this, though, because of crt, manifest constant, and the a,out->ELF change). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 5:29:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB07137B400 for ; Fri, 5 Jul 2002 05:29:15 -0700 (PDT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E6943E31 for ; Fri, 5 Jul 2002 05:29:15 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0029.cvx22-bradley.dialup.earthlink.net ([209.179.198.29] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QSD2-0006y2-00; Fri, 05 Jul 2002 08:29:12 -0400 Message-ID: <3D2590EF.CDFBDC51@mindspring.com> Date: Fri, 05 Jul 2002 05:28:31 -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: Paul Richards Cc: Sheldon Hearn , current@freebsd.org Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> 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 Paul Richards wrote: > > No, the idea of `make world' is to upgrade my system in the way that I > > tell it to. > > I don't think it is. That might be what you've become used to, but > that's not what make world was designed to do. It goes to great lengths > to make sure that you get a current version of the development branch > that's all built with the current bits. > > As a current developer, you need to see what -current looks like and not > what current on top of a lot of other stuff that hides bugs looks like. This may be a key point (see other posting). However, this is not even true of a clean install, with some sysinstall options, and is certainly not true of a CDROM based upgrade. It's unreasonable to expect that a "make installworld" could reset the system state sufficiently to provide this, other than for sertain "leaf node" things, like system header files that have been obsoleted. I guess the best way for you to argue for this outcome is for you to do the bsd.*.mk modifications to support your idea, and to do all the Makfile modifications to provide the targets, and to have it "off by default". Not a very satisfying approach, but the one with the highest probability that it won't be ripped out 5 minutes after you commit the code ("If thine Makefile mods offend thee, pluck them out"). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 6: 2: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A438A37B400 for ; Fri, 5 Jul 2002 06:01:59 -0700 (PDT) Received: from blackhole.x-echo.com (blackhole.x-echo.com [195.101.94.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A4F43E4A for ; Fri, 5 Jul 2002 06:01:00 -0700 (PDT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 17QRXl-0005nZ-00; Fri, 05 Jul 2002 13:46:33 +0200 Date: Fri, 5 Jul 2002 13:46:33 +0200 To: Terry Lambert Cc: Takanori Watanabe , Alex Zepeda , current@freebsd.org Subject: Re: ACPI woes again.. Message-ID: <20020705114633.GA22257@poup.poupinou.org> References: <200207050945.SAA28267@axe-inc.co.jp> <3D258C38.9E26407@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D258C38.9E26407@mindspring.com> User-Agent: Mutt/1.3.28i From: Ducrot Bruno 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, Jul 05, 2002 at 05:08:24AM -0700, Terry Lambert wrote: > Takanori Watanabe wrote: > > +.Sh OVERRIDING YOUR BIOS BYTECODE > > +ACPI interprets bytecode named AML, ACPI Machine Language, provided by BIOS > > +vendor as memory image at boot time. Sometimes, the AML code contains > > +problem that is not appeared in Microsoft implement. So we provide a way > > +to override it with your own AML code. > > +.Pp > > How does Windows deal with hardware that has this problem? > Do they use a "rogues" list, and replace the AML, too (only > automatically)? Actually, their ACPI implementation suck, so that most of buggy AML work. For example, they don't check correctly if a they have the right to read/write to some Operational Region. If an AML declare incorrecly such regions, under FBSD (or other free OS with an ACPI-CA implementation), it can not work since the bound checking work as expected. But as a consequence, those regions can't be acceded. As an example, the status of the AC can not be reported correctly under a Satellite 3000-601 due to this kind of bug. -- Ducrot Bruno http://www.poupinou.org Page profaissionelle http://toto.tu-me-saoules.com Haume page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 6:29:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BEF337B400 for ; Fri, 5 Jul 2002 06:29:16 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id D770C43E31 for ; Fri, 5 Jul 2002 06:29:15 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id E2BCB534A; Fri, 5 Jul 2002 15:29:13 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: ticso@cicely.de Cc: freebsd-current@freebsd.org Subject: Re: sshd login problem References: <20020705024917.GD40866@cicely5.cicely.de> From: Dag-Erling Smorgrav Date: 05 Jul 2002 15:29:13 +0200 In-Reply-To: <20020705024917.GD40866@cicely5.cicely.de> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 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 Bernd Walter writes: > cicely10 is an alpha running -current from 3. Jul. > The kernel is a day younger. What does 'ident /usr/sbin/sshd | grep monitor' say? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 6:33:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32BDE37B400 for ; Fri, 5 Jul 2002 06:33:17 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2380C43E31 for ; Fri, 5 Jul 2002 06:33:16 -0700 (PDT) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) by srv1.cosmo-project.de (8.12.3/8.12.3) with ESMTP id g65DX9Ma095702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Fri, 5 Jul 2002 15:33:13 +0200 (CEST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (localhost [IPv6:::1]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g65DX8FJ054702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 5 Jul 2002 15:33:09 +0200 (CEST)?g (envelope-from ticso@cicely5.cicely.de) Received: (from ticso@localhost) by cicely5.cicely.de (8.12.1/8.12.1/Submit) id g65DX8HK054701; Fri, 5 Jul 2002 15:33:08 +0200 (CEST)?g (envelope-from ticso) Date: Fri, 5 Jul 2002 15:33:08 +0200 From: Bernd Walter To: Dag-Erling Smorgrav Cc: ticso@cicely.de, freebsd-current@freebsd.org Subject: Re: sshd login problem Message-ID: <20020705133307.GA48977@cicely5.cicely.de> Reply-To: ticso@cicely.de References: <20020705024917.GD40866@cicely5.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely5.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.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 On Fri, Jul 05, 2002 at 03:29:13PM +0200, Dag-Erling Smorgrav wrote: > Bernd Walter writes: > > cicely10 is an alpha running -current from 3. Jul. > > The kernel is a day younger. > > What does 'ident /usr/sbin/sshd | grep monitor' say? [51]cicely10> ident /usr/sbin/sshd | grep monitor $OpenBSD: monitor_mm.c,v 1.6 2002/06/04 23:05:49 markus Exp $ $OpenBSD: monitor.c,v 1.18 2002/06/26 13:20:57 deraadt Exp $ $FreeBSD: src/crypto/openssh/monitor.c,v 1.7 2002/07/02 13:07:17 des Exp $ -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 8:17:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A183F37B411; Fri, 5 Jul 2002 08:17:15 -0700 (PDT) Received: from mail.deltanet.com (mail.deltanet.com [216.237.144.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA5E443E31; Fri, 5 Jul 2002 08:17:11 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from mammoth.eat.frenchfries.net (da001d0389.lax-ca.osd.concentric.net [64.0.145.134]) by mail.deltanet.com (8.11.6/8.11.6) with ESMTP id g65EppO10502; Fri, 5 Jul 2002 07:51:52 -0700 Received: by mammoth.eat.frenchfries.net (Postfix, from userid 1000) id 47A3C51C4; Fri, 5 Jul 2002 08:14:31 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mammoth.eat.frenchfries.net (Postfix) with ESMTP id 44D8C4B35; Fri, 5 Jul 2002 08:14:31 -0700 (PDT) Date: Fri, 5 Jul 2002 08:14:31 -0700 (PDT) From: Paul Herman X-X-Sender: pherman@mammoth.eat.frenchfries.net To: "Vladimir B. Grebenschikov" Cc: Terry Lambert , "Daniel O'Connor" , Bruce Evans , "Greg 'groggy' Lehey" , Poul-Henning Kamp , "current@freebsd.org" Subject: Re: About DEVFS (was: Re: About GEOM...) In-Reply-To: <1025861904.810.3.camel@vbook.express.ru> Message-ID: <20020705075203.I63430-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 5 Jul 2002, Vladimir B. Grebenschikov wrote: > May be same mechanism as hints, like: > hint.sio.0.mode=0622 As long as we are throwing out ideas: Aside from the fact that it's broken and at the moment wouldn't exactly DTRT, I always figured a type of mount_unionfs() with the older filesystem /dev as the upper layer and devfs as the lower layer would be the way to go. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 8:23:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35E6137B400 for ; Fri, 5 Jul 2002 08:23:15 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6347C43E31 for ; Fri, 5 Jul 2002 08:23:13 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17QUwE-0002Mq-00; Fri, 05 Jul 2002 17:24:02 +0200 Date: Fri, 5 Jul 2002 17:24:02 +0200 From: Sheldon Hearn To: Terry Lambert Cc: Paul Richards , current@freebsd.org Subject: Re: Removing perl in make world Message-ID: <20020705152402.GD775@starjuice.net> Mail-Followup-To: Terry Lambert , Paul Richards , current@freebsd.org References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <3D258F80.BD86F9D0@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D258F80.BD86F9D0@mindspring.com> User-Agent: Mutt/1.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 On (2002/07/05 05:22), Terry Lambert wrote: > > This would not fit in with the rest of the world target, which doesn't > > clean out stale headers, stale libraries or stale binaries. > > Special-casing certain things will surprise people. > > Headers and libraries arguably should be removed, so as to avoid > errors; not ports headers or libraries -- which aren't in the > installation target paths in the first place -- but things like > deprecated system headers, etc.. You and Paul are both pretty "out there" if you think -current users will graciously accept a new world order in which ports linked dymanically against system libraries won't work between a system upgrade and the next port reinstall. If you want to clean out crap left behind by `make world', just do this: make world rm -r /usr/include # Make world really should overwrite make installincludes # header files! find /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/share \ -type f -mtime +1 -delete If you're just annoyed by the recent perl wobble, think about how important it is to do what Paul suggests, if it means annoying users who have very good reasons to prefer the way the `make world' upgrade method works. Then, if you still think it's important, figure out a way to do it _without_ annoying those users, as suggested by Terry. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 8:41:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32E0F37B400 for ; Fri, 5 Jul 2002 08:41:13 -0700 (PDT) Received: from mail3.svr.pol.co.uk (mail3.svr.pol.co.uk [195.92.193.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5927743E3B for ; Fri, 5 Jul 2002 08:41:12 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-709.articuno.dialup.pol.co.uk ([217.135.28.197] helo=mailgate.originative.co.uk) by mail3.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17QVCo-00049f-00; Fri, 05 Jul 2002 16:41:11 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id 06D731D13D; Fri, 5 Jul 2002 16:41:09 +0100 (BST) Subject: Re: Removing perl in make world From: Paul Richards To: Sheldon Hearn Cc: Terry Lambert , current@freebsd.org In-Reply-To: <20020705152402.GD775@starjuice.net> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <3D258F80.BD86F9D0@mindspring.com> <20020705152402.GD775@starjuice.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Jul 2002 16:41:16 +0100 Message-Id: <1025883676.30545.15.camel@lobster.originative.co.uk> Mime-Version: 1.0 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, 2002-07-05 at 16:24, Sheldon Hearn wrote: > On (2002/07/05 05:22), Terry Lambert wrote: > > > > This would not fit in with the rest of the world target, which doesn't > > > clean out stale headers, stale libraries or stale binaries. > > > Special-casing certain things will surprise people. > > > > Headers and libraries arguably should be removed, so as to avoid > > errors; not ports headers or libraries -- which aren't in the > > installation target paths in the first place -- but things like > > deprecated system headers, etc.. > > You and Paul are both pretty "out there" if you think -current users > will graciously accept a new world order in which ports linked > dymanically against system libraries won't work between a system upgrade > and the next port reinstall. I'm reluctant to suggest something that scares away -current developers, since I don't think enough people are really working on -current these days. However, if you are developing FreeBSD then you do need to make sure you're running -current and not -cruft. The old mantra of "-current is for developers" still holds and if the development environment becomes ineffective because people are relying on current as a work environment then maybe we should tighten the development environment so it's more suited to those people who are actually working on FreeBSD itself. On my -current box I usually rebuild ports quite regularly anyway because ports get updated pretty frequently. The only real issue with backwards compatibility is the libraries, there's nothing else that should severely impact existing installations. Libraries can easily be dealt with by just moving them to a compat dir. > If you want to clean out crap left behind by `make world', just do this: > > make world > rm -r /usr/include # Make world really should overwrite > make installincludes # header files! > find /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/share \ > -type f -mtime +1 -delete That is precisely what I do periodically (along those lines anyway), and it is often the case that when I do so I find that I've been running -cruft and not -current at all. -- Paul Richards | FreeBSD Services Ltd | Order 4.6 on DVD today! http://www.freebsd-services.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 8:47:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E42937B400 for ; Fri, 5 Jul 2002 08:47:52 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2969843E31 for ; Fri, 5 Jul 2002 08:47:51 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g65Fibdg178300; Fri, 5 Jul 2002 11:44:38 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <1025864161.1573.45.camel@lobster.originative.co.uk> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> Date: Fri, 5 Jul 2002 11:44:36 -0400 To: Paul Richards , Sheldon Hearn From: Garance A Drosihn Subject: Re: Removing perl in make world Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 11:16 AM +0100 7/5/02, Paul Richards wrote: >On Fri, 2002-07-05 at 10:52, Sheldon Hearn wrote: > > On (2002/07/05 10:45), Paul Richards wrote: > > > I'd like to resurrect it's original meaning and add code > > > to clean out old versions of Perl. > > > > This would not fit in with the rest of the world target, > > which doesn't clean out stale headers, stale libraries > > or stale binaries. Special-casing certain things will > > surprise people. >I recently cleaned out a load of stale libraries and I was >quite surprised to find that what I thought was a version of >current updated daily was not in fact that at all since a >lot of my binaries were still linked to much older libraries >so I was running a pseudo current, partly up to date and >partly not. While I agree there should be some automatic way to get rid of old cruft (or at least to list it), I do not think that it should be part of installworld or installkernel. All that any such step can do is find things which "it does not expect" to be there, but it would have no way of knowing *why* the file is there. Maybe it's stale, *or* maybe someone build the port and explicitly pointed it at /usr instead of /usr/local. And if the process automatically removes some old library, and you have a lot of programs linked to that library, won't that be a bit disruptive? A plain installworld can be disruptive enough, without it also removing libraries that important programs might be linked to! -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 9:44: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7683A37B400 for ; Fri, 5 Jul 2002 09:44:03 -0700 (PDT) Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ABC143E09 for ; Fri, 5 Jul 2002 09:44:03 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 86B4A3198E5; Fri, 5 Jul 2002 11:44:05 -0500 (CDT) Date: Fri, 5 Jul 2002 11:44:05 -0500 From: "David W. Chapman Jr." To: Mark Murray Cc: Paul Richards , current@FreeBSD.ORG Subject: Re: Removing perl in make world Message-ID: <20020705164405.GA59288@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Mark Murray , Paul Richards , current@FreeBSD.ORG References: <1025862341.1573.40.camel@lobster.originative.co.uk> <200207051029.g65ATUii003713@grimreaper.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207051029.g65ATUii003713@grimreaper.grondar.org> X-Operating-System: FreeBSD 4.6-STABLE i386 User-Agent: Mutt/1.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 On Fri, Jul 05, 2002 at 11:29:30AM +0100, Mark Murray wrote: > > I think we should add a target to make world that checks for the > > existence of an old base install of Perl and removes it if it exists. > > I agree that we may need a tool to do this, but I don't agree that it > gets done automatically by "make world". Could we also make this tool mv /usr/include /usr/include.old so that it could be run before an installworld? -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 9:50:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09F1637B400; Fri, 5 Jul 2002 09:50:42 -0700 (PDT) Received: from draco.macsch.com (ns1.mscsoftware.com [192.207.69.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E0D443E09; Fri, 5 Jul 2002 09:50:41 -0700 (PDT) (envelope-from Georg.Koltermann@mscsoftware.com) Received: from mailmuc.muc.eu.mscsoftware.com (mailmuc.muc.macsch.com [161.34.37.20]) by draco.macsch.com (8.9.3/8.9.3) with ESMTP id JAA28231; Fri, 5 Jul 2002 09:50:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailmuc.muc.eu.mscsoftware.com (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g65Gmip21734; Fri, 5 Jul 2002 18:48:44 +0200 Cc: current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Content-Type: text/plain Date: 05 Jul 2002 18:48:56 +0200 From: "Georg-W. Koltermann" In-Reply-To: <20020703083114.A7216@dragon.nuxi.com> Message-Id: <1025887736.773.116.camel@hunter.muc.macsch.com> Mime-Version: 1.0 Received: from hunter.muc.macsch.com by mailmuc.muc.eu.mscsoftware.com (AvMailGate-2.0.0.6) id 21684-60FC890D; Fri, 05 Jul 2002 18:48:22 +0200 References: <20020703083114.A7216@dragon.nuxi.com> Subject: Re: dump(8) is hosed To: obrien@FreeBSD.ORG X-AntiVirus: OK! AvMailGate Version 6.12.1.30 at mailmuc has not found any known virus in this email. X-Mailer: Ximian Evolution 1.0.5 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 Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien: > On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in, > pre-KSE3), dump will not complete dumping more than 5GB. At that point > it stops responding properly to ^T, which should give "DUMP: 47.52% done, > finished in 1:19". At the 5GB mark, ^T gives: > > load: 0.00 cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k > > and never changes. The user and system times never advance. Anybody > have any ideas? For me it is broken in a different way. For a small FS like / it works, but dumping my /home, which is 4G, I get DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1 DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1 and on and on. Maybe a 32 bit <--> 64 bit mismatch caused by UFS2? My -current is of date=2002.06.27.22.00.00. Using pax(1) for backup now :-( -- Regards, Georg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 10:10:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED1DE37B400 for ; Fri, 5 Jul 2002 10:10:49 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 356AB43E09 for ; Fri, 5 Jul 2002 10:10:49 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.5/8.12.2) with ESMTP id g65H9poi062709; Fri, 5 Jul 2002 10:09:51 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.5/8.12.5/Submit) id g65H9lFN062707; Fri, 5 Jul 2002 10:09:47 -0700 (PDT) Date: Fri, 5 Jul 2002 10:09:47 -0700 From: "David O'Brien" To: Chuck Robey Cc: peter@wemm.org, gnn@neville-neil.com, freebsd-current@FreeBSD.ORG Subject: Re: Recommended MP development machines... Message-ID: <20020705100947.A90595@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020704065915.8FDA2390F@overcee.wemm.org> <200207041735.g64HYhJ47500@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200207041735.g64HYhJ47500@april.chuckr.org>; from chuckr@chuckr.org on Thu, Jul 04, 2002 at 01:34:42PM -0400 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 Thu, Jul 04, 2002 at 01:34:42PM -0400, Chuck Robey wrote: > >> The K7 had a broken on-board usb (the AMD > >> chipset had a PCI contention bug for the usb port, so the tin back panel > >> of the board blocked out the usb, and the K7 came with a PCI usb card, > >> which ate up one of your PCI slots. > > > > Hmmmmm..... Do you have any details on this? I've had occasional strange > > USB-related things happen on this box. Of course, it runs -current which > > puts me into the USB danger-zone enough as it is.. but what happens when > > this bug is triggered? ... > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/24472.pdf This is good to know. The above doc is for the AMD-768 Peripheral Bus Controller. Luckly the pre-production Thunder K7 mobos had AMD-766's in them. I don't know if Tyan switched to the 768 in later production. http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23615.pdf In HTML format: http://www.google.com/search?q=cache:eipmgE1E_f4C:www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23615.pdf+amd+766+revision+guide&hl=en&ie=UTF-8 Is the revision guide for the AMD-766 south bridge. There are 2 USB nits, but nothing serious like for the AMD-768 rev B1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 10:14: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3D0F37B400 for ; Fri, 5 Jul 2002 10:14:00 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A11943E09 for ; Fri, 5 Jul 2002 10:14:00 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.5/8.12.2) with ESMTP id g65HDxoi074690; Fri, 5 Jul 2002 10:13:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.5/8.12.5/Submit) id g65HDx85074689; Fri, 5 Jul 2002 10:13:59 -0700 (PDT) Date: Fri, 5 Jul 2002 10:13:59 -0700 From: "David O'Brien" To: "Georg-W. Koltermann" Cc: current@FreeBSD.ORG Subject: Re: dump(8) is hosed Message-ID: <20020705101359.A89839@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG Mail-Followup-To: David O'Brien , "Georg-W. Koltermann" , current@FreeBSD.ORG References: <20020703083114.A7216@dragon.nuxi.com> <1025887736.773.116.camel@hunter.muc.macsch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1025887736.773.116.camel@hunter.muc.macsch.com>; from Georg.Koltermann@mscsoftware.com on Fri, Jul 05, 2002 at 06:48:56PM +0200 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 Fri, Jul 05, 2002 at 06:48:56PM +0200, Georg-W. Koltermann wrote: > Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien: > > On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in, > > pre-KSE3), dump will not complete dumping more than 5GB. At that point > > it stops responding properly to ^T, which should give "DUMP: 47.52% done, > > finished in 1:19". At the 5GB mark, ^T gives: > > > > load: 0.00 cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k > > > > and never changes. The user and system times never advance. Anybody > > have any ideas? > > For me it is broken in a different way. For a small FS like / it works, > but dumping my /home, which is 4G, I get > > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1 > > and on and on. Simular to what I get (now that I looked in /var/log/messages): kernel: ccd1: error 22 on component 2 block -431037296 (ccd block 7744633266) kernel: ccd1: error 22 on component 1 block -431037168 (ccd block 7744633266) kernel: ccd1: error 22 on component 2 block -431037168 (ccd block 7744633266) > Maybe a 32 bit <--> 64 bit mismatch caused by UFS2? My -current is of > date=2002.06.27.22.00.00. Maybe. I'll forward this to someone that might know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 11: 2:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E21BA37B400 for ; Fri, 5 Jul 2002 11:02:19 -0700 (PDT) Received: from milan.hitnet.rwth-aachen.de (milan.hitnet.RWTH-Aachen.DE [137.226.181.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78C5243E09 for ; Fri, 5 Jul 2002 11:02:19 -0700 (PDT) (envelope-from chris@milan.hitnet.rwth-aachen.de) Received: by milan.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 34CBBAB9F; Fri, 5 Jul 2002 20:05:43 +0200 (CEST) Date: Fri, 5 Jul 2002 20:05:43 +0200 From: Christian Brueffer To: freebsd-current@freebsd.org Subject: Re: [acpi-jp 1661] Re: ASUS CUSL2 panic on acpi Message-ID: <20020705180543.GB83124@unixpages.org> References: <20020702185518.87573.qmail@web11402.mail.yahoo.com> <20020703.142736.112630398.iwasaki@jp.FreeBSD.org> <20020704.120342.38720157.iwasaki@jp.FreeBSD.org> <20020704.220952.104026566.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020704.220952.104026566.iwasaki@jp.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 On Thu, Jul 04, 2002 at 10:09:52PM +0900, Mitsuru IWASAKI wrote: > My analysis was finished. Please try this patch. > > --- exfield.c- Thu Jul 4 21:54:24 2002 > +++ exfield.c Thu Jul 4 21:55:02 2002 > @@ -200,7 +200,7 @@ > /* Handle both ACPI 1.0 and ACPI 2.0 Integer widths */ > > IntegerSize = sizeof (ACPI_INTEGER); > - if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) > + if (WalkState->MethodNode != NULL && WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) > { > /* > * We are running a method that exists in a 32-bit ACPI table. > The patch works fine, thanks. - Christian -- http://www.unixpages.org chris@unixpages.org GPG Pub-Key : www.unixpages.org/cbrueffer.asc GPG Fingerprint: 0DB5 8563 2473 C72A A8D1 56EA DAD2 B05D 5F3C 3185 GPG Key ID : DAD2B05D5F3C3185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 12: 3:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 454FB37B400 for ; Fri, 5 Jul 2002 12:03:46 -0700 (PDT) Received: from orion.gate5.de (orion.gate5.de [212.84.193.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDB7743E3B for ; Fri, 5 Jul 2002 12:03:44 -0700 (PDT) (envelope-from erdgeist@gate5.de) Received: (qmail 38535 invoked by uid 1075); 5 Jul 2002 19:02:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Jul 2002 19:02:31 -0000 Date: Fri, 5 Jul 2002 21:02:31 +0200 (CEST) From: Dirk Engling Reply-To: erdgeist@gate5.de To: freebsd-current@freebsd.org Subject: process state problems 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 [ erdgeist@bauklotz:~/Coding ] 20:59:14 $> less test.c int main( ) { char a; a = getchar(); return a; } [ erdgeist@bauklotz:~/Coding ] 20:59:19 $> ./test ^Z [1]+ Stopped ./test [ erdgeist@bauklotz:~/Coding ] 20:59:26 $> bg bash: bg: bg background job? [ erdgeist@bauklotz:~/Coding ] 20:59:27 $> uname -a FreeBSD bauklotz.gate5.de 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jul 5 20:33:04 GMT 2002 root@bauklotz.gate5.de:/usr/src/sys/i386/compile/bauklotz i386 [ erdgeist@bauklotz:~/Coding ] 20:59:59 $> bash --version GNU bash, version 2.05a.0(1)-release (i386-portbld-freebsd5.0) Copyright 2001 Free Software Foundation, Inc. [ erdgeist@bauklotz:~/Coding ] 21:00:45 $> fg ./test d d d ^C I just made a fresh world, made a bash2 from current-ports, half an hour old and this is, what happens. On a 4.6 this effect does not appear. Any suggestions? Regards erdgeist ----------------------------------------- fnord! id 0x17B701E5 size 1024 | type rsa 11F8 8FF3 0508 09F9 DC6A 2AB3 AA67 C8CF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 12:52:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D021037B400 for ; Fri, 5 Jul 2002 12:52:20 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F98243E09 for ; Fri, 5 Jul 2002 12:52:20 -0700 (PDT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id F189F2A7F2 for ; Fri, 5 Jul 2002 12:52:19 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id BEFD14C47C for ; Fri, 5 Jul 2002 12:52:19 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id A85D2380A; Fri, 5 Jul 2002 12:52:19 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Julian Elischer Cc: FreeBSD current users Subject: Re: status of KSE merge In-Reply-To: Date: Fri, 05 Jul 2002 12:52:19 -0700 From: Peter Wemm Message-Id: <20020705195219.A85D2380A@overcee.wemm.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 Julian Elischer wrote: > At this time I have no information on any apps that fail to work (that did > work before KSE). > > The signal flakiness is still present but at least people can get work > done. I will work on this next (though signal experts are welcome to > try their hand as well.. (in fact any beginners who want to jump inat the > deep end of the pool can guarantee a near-drowning-experience by trying > to understand signals). Some news: syscall restart after signals is broken. This is responsible for a lot of the ^Z/fg problems as well as some applications failing when their timer signals cause IO problems. Test case: peter@overcee[12:49pm]~-125> cat restart.sh #! /tmp/44sh echo -n "Type something: " read foo echo "You typed: \"$foo\"" peter@overcee[12:49pm]~-126> ./restart.sh Type something: foo You typed: "foo" peter@overcee[12:49pm]~-127> ktrace ./restart.sh Type something: ^Z [1] + Suspended ktrace ./restart.sh peter@overcee[12:49pm]~-128> fg ktrace ./restart.sh You typed: "" peter@overcee[12:49pm]~-129> kdump -R [...] 1091 44sh 0.000061 CALL write(0x1,0x80c4000,0x10) 1091 44sh 0.000029 GIO fd 1 wrote 16 bytes "Type something: " 1091 44sh 0.000198 RET write 16/0x10 1091 44sh 0.000187 CALL read(0,0xbfbff2f3,0x1) 1091 44sh 3.054434 RET read -1 errno 4 Interrupted system call 1091 44sh 0.000695 CALL write(0x1,0x80c4000,0xe) 1091 44sh 0.000025 GIO fd 1 wrote 14 bytes "You typed: "" " 1091 44sh 0.000254 RET write 14/0xe [..] The errno 4 - interrupted system call should not happen. read returns ERESTART internally on the signal catch, and the syscall() function in trap.c is supposed to back up the eip which causes the syscall to be rerun. I have not looked at the code yet. This is responsible for things like vipw failing after ^Z/fg (editor=vi), mergemaster failing on ^Z/fg etc. (it was mergemaster that tipped me off on this.) Applications that use interval timers would be suffering from this pretty badly. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 14:20:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FAD937B400 for ; Fri, 5 Jul 2002 14:20:13 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62A6343E42 for ; Fri, 5 Jul 2002 14:20:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020705212011.UVJD903.sccrmhc03.attbi.com@InterJet.elischer.org>; Fri, 5 Jul 2002 21:20:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA14869; Fri, 5 Jul 2002 14:05:37 -0700 (PDT) Date: Fri, 5 Jul 2002 14:05:36 -0700 (PDT) From: Julian Elischer To: Dirk Engling Cc: freebsd-current@freebsd.org Subject: Re: process state problems In-Reply-To: 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 this is a bug in the KSE signal handling.. peter and I are looking at it at the moemnt. it is a known problem. On Fri, 5 Jul 2002, Dirk Engling wrote: > > [ erdgeist@bauklotz:~/Coding ] > 20:59:14 $> less test.c > int main( ) { > char a; > > a = getchar(); > > return a; > } > [ erdgeist@bauklotz:~/Coding ] > 20:59:19 $> ./test > ^Z > [1]+ Stopped ./test > [ erdgeist@bauklotz:~/Coding ] > 20:59:26 $> bg > bash: bg: bg background job? > > [ erdgeist@bauklotz:~/Coding ] > 20:59:27 $> uname -a > FreeBSD bauklotz.gate5.de 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Fri Jul 5 20:33:04 GMT 2002 > root@bauklotz.gate5.de:/usr/src/sys/i386/compile/bauklotz i386 > > [ erdgeist@bauklotz:~/Coding ] > 20:59:59 $> bash --version > GNU bash, version 2.05a.0(1)-release (i386-portbld-freebsd5.0) > Copyright 2001 Free Software Foundation, Inc. > > [ erdgeist@bauklotz:~/Coding ] > 21:00:45 $> fg > ./test > d > d > d > ^C > > I just made a fresh world, made a bash2 > from current-ports, half an hour old > and this is, what happens. > > On a 4.6 this effect does not appear. > Any suggestions? > > Regards > > erdgeist > > ----------------------------------------- > fnord! > id 0x17B701E5 size 1024 | type rsa > 11F8 8FF3 0508 09F9 DC6A 2AB3 AA67 C8CF > > > 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 Fri Jul 5 15: 9:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A07837B400 for ; Fri, 5 Jul 2002 15:09:18 -0700 (PDT) Received: from goose.mail.pas.earthlink.net (goose.mail.pas.earthlink.net [207.217.120.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A4A443E09 for ; Fri, 5 Jul 2002 15:09:18 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0052.cvx40-bradley.dialup.earthlink.net ([216.244.42.52] helo=mindspring.com) by goose.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QbG5-0006Fb-00; Fri, 05 Jul 2002 15:08:58 -0700 Message-ID: <3D2618D0.30EC39AA@mindspring.com> Date: Fri, 05 Jul 2002 15:08:16 -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: Sheldon Hearn Cc: Paul Richards , current@freebsd.org Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <3D258F80.BD86F9D0@mindspring.com> <20020705152402.GD775@starjuice.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 Sheldon Hearn wrote: > You and Paul are both pretty "out there" if you think -current users > will graciously accept a new world order in which ports linked > dymanically against system libraries won't work between a system upgrade > and the next port reinstall. > > If you want to clean out crap left behind by `make world', just do this: > > make world > rm -r /usr/include # Make world really should overwrite > make installincludes # header files! > find /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/share \ > -type f -mtime +1 -delete > > If you're just annoyed by the recent perl wobble, think about how important > it is to do what Paul suggests, if it means annoying users who have very > good reasons to prefer the way the `make world' upgrade method works. > > Then, if you still think it's important, figure out a way to do it > _without_ annoying those users, as suggested by Terry. 1) It was Paul that suggested it. I merely stated that he had a reasonable argument, depending on his goals. 2) Right after you stopped quoting, implying that I was for the idea, I had said: | Note that this is really problematic, since there are optional | install components, such as binary backward compatability | libraries that are installed into system directories, such as | /usr/lib, that aren't technically the result of the build | process itself. | | Header files under /usr/include are pretty straight forward, as | far as that goes, though, unless they overlap components that | get installed for binary compatability (I don't think the tools | actually support building for this, though, because of crt, | manifest constant, and the a,out->ELF change). ... in other words: i. It's reasonable to want this ii. I don't think you can have this So... before you try to tar something with the "Terry likes it, it must be bad" brush, make sure you know which side of the issue I'm on. This time, I'm on your side. I guess that must mean you're wrong. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 15:34: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9DE237B401 for ; Fri, 5 Jul 2002 15:34:00 -0700 (PDT) Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E7E243E09 for ; Fri, 5 Jul 2002 15:34:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0052.cvx40-bradley.dialup.earthlink.net ([216.244.42.52] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17Qbe9-00037i-00; Fri, 05 Jul 2002 18:33:50 -0400 Message-ID: <3D261EA4.ABC3AEC@mindspring.com> Date: Fri, 05 Jul 2002 15:33:08 -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: Garance A Drosihn Cc: Paul Richards , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> 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 Garance A Drosihn wrote: > While I agree there should be some automatic way to get rid > of old cruft (or at least to list it), I do not think that it > should be part of installworld or installkernel. All that > any such step can do is find things which "it does not expect" > to be there, but it would have no way of knowing *why* the > file is there. Maybe it's stale, *or* maybe someone build the > port and explicitly pointed it at /usr instead of /usr/local. So, to summarize: o People with old cruft may have working -current systems that should not be working, but they can't see the problems because they have files that would not be there if they had done a fresh install. o People with old cruft may be reporting broken -current experiences (e.g. like some of the libc_r breakage recently), when *their personal system* is what is broken, because they have files that would not be there if they had done a fresh install. o Making "make install" remove "everything which is not -current" is a bad idea, because it could surprise people by moving them from the first category -- "should not be working" -- into the "not working" category. Just to play devil's advocate... Aren't the people who would be "surprised" in this case using -current in a way it is not intended to be used? Specifically, isn't -current there *solely* for testing, and not production work, and therefore shouldn't the *primary* purpose of -current -- testing for breakage in -current -- be the first and foremost result of running -current? -- I think that there are two contradictory assumptions in this dicussion... either you want -current to work because it's good code, or you want -current to "just work", and you don't care if that doesn't mean that you can't build an identical, working system from the code in the source repository. Paul: I think the flaw in your idea is that when the source code goes from a working to a non-working condition, there would be no going back to correct the problem, short of a full reinstall or an emergency recovery disk. Others: I think the flaw in your idea is that you aren't really running -current, so why the heck aren't you just running -stable, instead of pretending to run -current? I think it comes down to this: Everyone is interested in having the most people possible running -current. Paul wants to attract new people, and Sheldon wants to not scare away old people. So back to my original suggestion (to Paul) of compromise: | I guess the best way for you to argue for this outcome is for | you to do the bsd.*.mk modifications to support your idea, and | to do all the Makfile modifications to provide the targets, | and to have it "off by default". E.g. with a "make installpristine" or some other target. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 17: 5:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5641C37B400 for ; Fri, 5 Jul 2002 17:05:01 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19CE343E4A for ; Fri, 5 Jul 2002 17:04:47 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id g6604Ori021893; Fri, 5 Jul 2002 17:04:24 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id g6604N3I021892; Fri, 5 Jul 2002 17:04:23 -0700 Date: Fri, 5 Jul 2002 17:04:23 -0700 From: Brooks Davis To: Terry Lambert Cc: Garance A Drosihn , Paul Richards , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world Message-ID: <20020705170423.C24073@Odin.AC.HMC.Edu> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D261EA4.ABC3AEC@mindspring.com>; from tlambert2@mindspring.com on Fri, Jul 05, 2002 at 03:33:08PM -0700 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu 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 --yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jul 05, 2002 at 03:33:08PM -0700, Terry Lambert wrote: > Others: I think the flaw in your idea is that you aren't > really running -current, so why the heck aren't you just > running -stable, instead of pretending to run -current? Of course by this argument, we wouldn't be running -stable either... I agree there is a need to allow developers to clean up their systems to be as much like a clean install as possiable, but I definatly think installworld is the wrong place to do so. I'm also pretty convinced that a make target is the wrong place entierly. The problem is that if you just go nuking everything that's OBE, you will break development machines and that's unacceptable. I can't just rebuild kde on a whim, it takes 10-20 hours on my laptop (and since I last built it with gcc 2.x, it's presumably much worse now.) What would be useful to me, would be a way to list the files that are OBE so I can make a reasionable decision about removing them. Idealy, such a system would have some handy ldd scripts to tell me if libs are used or not. I think Paul's goal is fairly noble, but the suggest solution is unacceptable in my book. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9JjQHXY6L6fI4GtQRAtE6AJ9Udr4jdq1OjKkRAqG+Lq2kp4O9bgCaArSk n/Ti/mJKBja47byQxJujHCY= =pBvz -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 17: 8:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB37937B405 for ; Fri, 5 Jul 2002 17:08:17 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A3AA43E09 for ; Fri, 5 Jul 2002 17:07:51 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g6607kdg174128; Fri, 5 Jul 2002 20:07:46 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3D261EA4.ABC3AEC@mindspring.com> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> Date: Fri, 5 Jul 2002 20:07:44 -0400 To: Terry Lambert From: Garance A Drosihn Subject: Re: Removing perl in make world Cc: Paul Richards , Sheldon Hearn , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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:33 PM -0700 7/5/02, Terry Lambert wrote: > >So, to summarize: > Let me summarize my own position. There are a number of files which installworld does install. After an installworld is done, there may be a number of files on a person's hard disk which were not put there by the most recent installworld. For each of those files, the issue is one of intent. 1) Is it there because the administrator explicitly wanted it to be there, for explicit reasons that may be perfectly valid even while testing the latest snapshot of current? 2) or is it left-over cruft from some previous install, and which is only getting in the way of proper testing? If you keep it that simple, instead of writing 200-line summaries of what is going on (and the possible motivations of everyone), then the solution is also simple. The above is just a slight variation from what happens with /etc config files during a new installworld. We should not have anything which automatically blows away those files. We should have an "unmergemaster" script, which will find those files, and **ASKS THE DEVELOPER** what they want to do for each of those files (or maybe for each set of files). No automatic process is going to be 100% right 100% of the time. Developers do not need to have installworld forcing some person's idea of what a "pristine" testing environment should look like. However, it would be very useful to have something which would just *tell* us what the difference is between our environment and this imaginary perfect testing environment, so we can decide what should (and what should not) be changed. While the solution may be conceptually simple, I will admit that I have no intention of working on it myself. I will therefore drop out of the debate in this thread at this time. Not that I'm upset about any of it, it's just that I don't think I have anything more to contribute. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 17:46:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 929F537B400 for ; Fri, 5 Jul 2002 17:46:39 -0700 (PDT) Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EADA43E09 for ; Fri, 5 Jul 2002 17:46:39 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0052.cvx40-bradley.dialup.earthlink.net ([216.244.42.52] helo=mindspring.com) by scaup.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QdiS-0003LA-00; Fri, 05 Jul 2002 20:46:24 -0400 Message-ID: <3D263DA2.351666CD@mindspring.com> Date: Fri, 05 Jul 2002 17:45: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: Garance A Drosihn Cc: Paul Richards , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.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 Garance A Drosihn wrote: > At 3:33 PM -0700 7/5/02, Terry Lambert wrote: > >So, to summarize: > > > > Let me summarize my own position. I was summarizing both. It's not really necessary to summarize a position you've already taken... that's "reiterating". 8-) 8-). You want a one sentence summary instead of a "200 line" summary? Both sides want as many developers as possible using -current in order to advance things as quickly as possible, but they disagree on how that can be best accomplished and are too busy proving they are right to listen to each other and find a compromise. I think automatically removing perl -- or anything else that could result in a runtime error, if it were removed -- is a bad idea. It's asking "make installworld" to be better at component management than "sysinstall upgrade". This is impossible, with the present tools for configuration management that FreeBSD has. I don't think there is *any* way you can turn a system that is a result of "make installworld" into the same system it would have been if you had installed a snapshot from a CDROM on a clean hard drive, and done minor system configuration. Removing old system header files is a possibility. Doing that will cause compile-time errors, but not runtime errors. If we are looking for a minimum valid set of things to remove automatically, then header files are a good candidate. Doing it, though, is a scary default, if you can't turn it off. How about leaving perl along, and starting with a proof-of-concept? Garance: Could you agree to let Paul add Makefile code *that is on by default* to zap /usr/include so that it contained only header files from the "make installworld", after that command is run? Paul: Could you agree to add a knob that Garance and anyone else who is interested could set in their /etc/make.conf or somewhere else where it only has to be set once, so they could opt-out of participating in your experiment? Does this sound reasonable? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 18: 0:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1578537B400 for ; Fri, 5 Jul 2002 18:00:17 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8261043E09 for ; Fri, 5 Jul 2002 18:00:16 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020706010015.NZPH29588.sccrmhc01.attbi.com@InterJet.elischer.org>; Sat, 6 Jul 2002 01:00:15 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA15609; Fri, 5 Jul 2002 17:43:27 -0700 (PDT) Date: Fri, 5 Jul 2002 17:43:26 -0700 (PDT) From: Julian Elischer To: Peter Wemm Cc: FreeBSD current users Subject: i386 trap code 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 Looking at i386/exception.s one sees: ################################### .globl alltraps .type alltraps,@function alltraps: pushal pushl %ds pushl %es pushl %fs alltraps_with_regs_pushed: mov $KDSEL,%ax mov %ax,%ds mov %ax,%es mov $KPSEL,%ax mov %ax,%fs FAKE_MCOUNT(13*4(%esp)) calltrap: FAKE_MCOUNT(btrap) /* init "from" btrap -> calltrap */ call trap /* * Return via doreti to handle ASTs. */ MEXITCOUNT jmp doreti ####################################### but one has to look in isa/ipl.s to find: ######################################## SUPERALIGN_TEXT .type doreti,@function doreti: FAKE_MCOUNT(bintr) /* init "from" bintr -> doreti */ doreti_next: /* * Check if ASTs can be handled now. PSL_VM must be checked first * since segment registers only have an RPL in non-VM86 mode. */ testl $PSL_VM,TF_EFLAGS(%esp) /* are we in vm86 mode? */ jz doreti_notvm86 cmpl $1,in_vm86call /* are we in a vm86 call? */ jne doreti_ast /* can handle ASTs now if not */ jmp doreti_exit doreti_notvm86: testb $SEL_RPL_MASK,TF_CS(%esp) /* are we in user mode? */ jz doreti_exit /* can't handle ASTs now if not */ doreti_ast: /* * Check for ASTs atomically with returning. Disabling CPU * interrupts provides sufficient locking evein the SMP case, * since we will be informed of any new ASTs by an IPI. */ cli movl PCPU(CURTHREAD),%eax movl TD_KSE(%eax), %eax testl $KEF_ASTPENDING | KEF_NEEDRESCHED,KE_FLAGS(%eax) je doreti_exit sti pushl %esp /* pass a pointer to the trapframe */ call ast add $4,%esp jmp doreti_ast /* * doreti_exit: pop registers, iret. * * The segment register pop is a special case, since it may * fault if (for example) a sigreturn specifies bad segment * registers. The fault is handled in trap.c. */ doreti_exit: MEXITCOUNT .globl doreti_popl_fs doreti_popl_fs: popl %fs .globl doreti_popl_es doreti_popl_es: popl %es .globl doreti_popl_ds doreti_popl_ds: popl %ds popal addl $8,%esp .globl doreti_iret doreti_iret: iret Now: would it not make a lot of sense to put doreti immediatly after calltrap: in the same file so that one could follow the entire picture without having to bounce back and forth between two files? (also gets rid of the jmp in the common case) Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 18:24:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7280137B400 for ; Fri, 5 Jul 2002 18:24:36 -0700 (PDT) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id C26A343E09 for ; Fri, 5 Jul 2002 18:24:35 -0700 (PDT) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (jake@localhost [127.0.0.1]) by k6.locore.ca (8.12.5/8.12.3) with ESMTP id g661PUKk005103; Fri, 5 Jul 2002 21:25:30 -0400 (EDT) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.5/8.12.3/Submit) id g661PUED005102; Fri, 5 Jul 2002 21:25:30 -0400 (EDT) Date: Fri, 5 Jul 2002 21:25:30 -0400 From: Jake Burkholder To: Julian Elischer Cc: Peter Wemm , FreeBSD current users Subject: Re: i386 trap code Message-ID: <20020705212530.C839@locore.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Fri, Jul 05, 2002 at 05:43:26PM -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 Apparently, On Fri, Jul 05, 2002 at 05:43:26PM -0700, Julian Elischer said words to the effect of; > > Looking at i386/exception.s > one sees: [...] > > Now: > > would it not make a lot of sense to put doreti immediatly after > calltrap: in the same file > so that one could follow the entire picture without having to bounce back > and forth between two files? I'd say so, yeah. Its probably there because it used to be alongside splz and unmasked pending isa interrupts. > > (also gets rid of the jmp in the common case) System calls are probably the common case. But I'd suggest just put it after the trap code at the end of the file and leave the jump. Its super aligned so there would probably be a bunch of nops to plow through anyway. Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 19: 5:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5BFA37B400 for ; Fri, 5 Jul 2002 19:05:41 -0700 (PDT) Received: from mail4.svr.pol.co.uk (mail4.svr.pol.co.uk [195.92.193.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id C093543E31 for ; Fri, 5 Jul 2002 19:05:40 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-233.abra.dialup.pol.co.uk ([217.135.1.233] helo=mailgate.originative.co.uk) by mail4.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17Qex9-0007Ev-00; Sat, 06 Jul 2002 03:05:39 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id E3DD11D13D; Sat, 6 Jul 2002 03:05:33 +0100 (BST) Subject: Re: Removing perl in make world From: Paul Richards To: Garance A Drosihn Cc: Terry Lambert , Sheldon Hearn , current@FreeBSD.ORG In-Reply-To: References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 06 Jul 2002 03:05:46 +0100 Message-Id: <1025921146.881.16.camel@lobster.originative.co.uk> Mime-Version: 1.0 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, 2002-07-06 at 01:07, Garance A Drosihn wrote: > At 3:33 PM -0700 7/5/02, Terry Lambert wrote: > > > >So, to summarize: > > > > Let me summarize my own position. > > There are a number of files which installworld does install. After > an installworld is done, there may be a number of files on a person's > hard disk which were not put there by the most recent installworld. > > For each of those files, the issue is one of intent. > > 1) Is it there because the administrator explicitly wanted it > to be there, for explicit reasons that may be perfectly valid > even while testing the latest snapshot of current? > 2) or is it left-over cruft from some previous install, and > which is only getting in the way of proper testing? > > If you keep it that simple, instead of writing 200-line summaries > of what is going on (and the possible motivations of everyone), then > the solution is also simple. The above is just a slight variation > from what happens with /etc config files during a new installworld. > > We should not have anything which automatically blows away those > files. We should have an "unmergemaster" script, which will find > those files, and **ASKS THE DEVELOPER** what they want to do for > each of those files (or maybe for each set of files). No automatic > process is going to be 100% right 100% of the time. I think a -current system is something that should be assumed to be a semi-known environment though. Let's start with a premise: No-one running current is using it for anything other than developing FreeBSD. Given that premise, then there shouldn't be anything in /usr outside of /usr/local, that wasn't put there by make world. Likewise the same should be true of /sbin and /bin. Therefore running, find $listofdirs -newermt $date -delete should be perfectly OK since it's only going to clear out old files that are no longer part of FreeBSD (where $listofdirs is directories that should not be touched other than by make world, and $date is the date of the last install). The only tweak that is necessary is in the case of /usr/lib, where files should be moved to a compat dir and not deleted. I do this periodically on my dev box and it does show up issues. I think it's something we should build into our infrastructure as a step towards a better known environment for testing -current. -- Paul Richards | FreeBSD Services Ltd | Order 4.6 on DVD now. http://www.freebsd-services.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 19:44:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B2AC37B400 for ; Fri, 5 Jul 2002 19:44:37 -0700 (PDT) Received: from web20907.mail.yahoo.com (web20907.mail.yahoo.com [216.136.226.229]) by mx1.FreeBSD.org (Postfix) with SMTP id B32A243E09 for ; Fri, 5 Jul 2002 19:44:36 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020706024436.40687.qmail@web20907.mail.yahoo.com> Received: from [218.108.150.59] by web20907.mail.yahoo.com via HTTP; Fri, 05 Jul 2002 19:44:36 PDT Date: Fri, 5 Jul 2002 19:44:36 -0700 (PDT) From: David Xu Subject: Re: status of KSE merge To: Peter Wemm Cc: Julian Elischer , 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 the following patch can fix the bug, but for KSE programs, it may not be a best solution, KSE programs signal handling is on going... --- kern_synch.c Wed Jul 3 17:15:20 2002 +++ kern_synch.c.new Sat Jul 6 10:36:22 2002 @@ -537,8 +537,7 @@ PROC_LOCK(p); sig = cursig(td); if (thread_suspend_check(1)) { - sig = EINTR; - rval = EINTR; + sig = SIGSTOP; } mtx_lock_spin(&sched_lock); PROC_UNLOCK(p); -David Xu ----- Original Message ----- From: "Peter Wemm" To: "Julian Elischer" Cc: "FreeBSD current users" Sent: Saturday, July 06, 2002 3:52 AM Subject: Re: status of KSE merge > Julian Elischer wrote: > > > At this time I have no information on any apps that fail to work (that did > > work before KSE). > > > > The signal flakiness is still present but at least people can get work > > done. I will work on this next (though signal experts are welcome to > > try their hand as well.. (in fact any beginners who want to jump inat the > > deep end of the pool can guarantee a near-drowning-experience by trying > > to understand signals). > > Some news: syscall restart after signals is broken. This is responsible > for a lot of the ^Z/fg problems as well as some applications failing when > their timer signals cause IO problems. > > Test case: > peter@overcee[12:49pm]~-125> cat restart.sh > #! /tmp/44sh > echo -n "Type something: " > read foo > echo "You typed: \"$foo\"" > peter@overcee[12:49pm]~-126> ./restart.sh > Type something: foo > You typed: "foo" > peter@overcee[12:49pm]~-127> ktrace ./restart.sh > Type something: ^Z > [1] + Suspended ktrace ./restart.sh > peter@overcee[12:49pm]~-128> fg > ktrace ./restart.sh > You typed: "" > peter@overcee[12:49pm]~-129> kdump -R > [...] > 1091 44sh 0.000061 CALL write(0x1,0x80c4000,0x10) > 1091 44sh 0.000029 GIO fd 1 wrote 16 bytes > "Type something: " > 1091 44sh 0.000198 RET write 16/0x10 > 1091 44sh 0.000187 CALL read(0,0xbfbff2f3,0x1) > 1091 44sh 3.054434 RET read -1 errno 4 Interrupted system call > 1091 44sh 0.000695 CALL write(0x1,0x80c4000,0xe) > 1091 44sh 0.000025 GIO fd 1 wrote 14 bytes > "You typed: "" > " > 1091 44sh 0.000254 RET write 14/0xe > [..] > > The errno 4 - interrupted system call should not happen. read returns > ERESTART internally on the signal catch, and the syscall() function in trap.c > is supposed to back up the eip which causes the syscall to be rerun. > > I have not looked at the code yet. This is responsible for things like > vipw failing after ^Z/fg (editor=vi), mergemaster failing on ^Z/fg etc. > (it was mergemaster that tipped me off on this.) > > Applications that use interval timers would be suffering from this pretty > badly. > > Cheers, > -Peter > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com > "All of this is for nothing if we don't go to the stars" - JMS/B5 __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 19:46:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AC9E37B400 for ; Fri, 5 Jul 2002 19:46:09 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7405343E09 for ; Fri, 5 Jul 2002 19:46:08 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g662k4dg180598; Fri, 5 Jul 2002 22:46:05 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <1025921146.881.16.camel@lobster.originative.co.uk> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> <1025921146.881.16.camel@lobster.originative.co.uk> Date: Fri, 5 Jul 2002 22:46:03 -0400 To: Paul Richards From: Garance A Drosihn Subject: Re: Removing perl in make world Cc: Terry Lambert , Sheldon Hearn , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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:05 AM +0100 7/6/02, Paul Richards wrote: >Let's start with a premise: No-one running current is using >it for anything other than developing FreeBSD. This is assumption is too limiting. People running -current are doing it to test the latest builds. What they *do* to test it is their business. Ie, if I want to install some port in /usr instead of /usr/local, that is something I should be able to do. >Given that premise, then there shouldn't be anything in /usr >outside of usr/local, that wasn't put there by make world. >Likewise the same should be true of /sbin and /bin. > >Therefore running, > >find $listofdirs -newermt $date -delete > >should be perfectly OK since it's only going to clear out old >files that are no longer part of FreeBSD Wrong. It will delete files which were not installed by the FreeBSD install process, but that is *not* necessarily the same thing as "old files". The fact that installworld did not install the file does not mean that *I* do not want that file to be right where it is. How you test your -current system is your own business. There should be no command as part of 'installworld' which assumes how I am going to test my system, or what things I am testing on my system. No blind 'find' command should be automatically deleting any files on my system. The perplexing part of this debate is that I do see what problem you are trying to solve, and I *do* think it would be valuable to address that issue. I do not see what is so perplexing about having a separate script, just like mergemaster, which a person could run WHEN THEY WANT TO, and which would *LIST* what files are in their system that would not be in a "pristine install of -current". It could even go thru, just like mergemaster, and ask "What do you want to do about this file? (Remove, LeaveIt)". People reporting a problem could even be told to run this script, so any other person who is debugging that problem can realize exactly what is different about the first person's system. I can see that someone might say "Ah, you have some old perl installed, and therefore I will ignore your bug report for now". What would be the PROBLEM with THAT solution? Please answer that question, instead of just reinterating how you would like to add find command which will blindly delete files from the system of every developer who is on current. If 'installworld' starts erasing files on me, then I am going to have to reserve a larger block of time to cvsup/buildworld. I will react to that by building world less often, and that isn't going to help any wish for "valuable debugging". As it is, I have spent more than 60 hours in the last month just trying to do a buildworld of current, only to be foiled by one problem or another. (nothing dramatic, it's mainly been a matter of picking the wrong times to cvsup...). And here I am on a friday night, doing a new buildworld while running a -current system from April 23rd, because all of those attempts have failed. 60 hours of my free time in the past month with not a damn thing to show for it, and you're going to make installworlds on -current even more of a hassle. Pardon me if I don't signup for it. I will simply drop back to using stable and I won't bother to help out one bit with testing -current. If you think that -current needs FEWER people trying to run it, then feel free to screw up the installworld target. That's just my 2 cents worth. I see the problem you're trying to address, and if most developers of -current see this as a major problem, then maybe it's better to solve the problem and drive away a few other developers. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 20: 1:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CE8837B400 for ; Fri, 5 Jul 2002 20:01:49 -0700 (PDT) Received: from web20907.mail.yahoo.com (web20907.mail.yahoo.com [216.136.226.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 3833C43E31 for ; Fri, 5 Jul 2002 20:01:49 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020706030149.42503.qmail@web20907.mail.yahoo.com> Received: from [218.108.150.59] by web20907.mail.yahoo.com via HTTP; Fri, 05 Jul 2002 20:01:49 PDT Date: Fri, 5 Jul 2002 20:01:49 -0700 (PDT) From: David Xu To: Julian Elischer Cc: Peter Wemm , FreeBSD current users 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 ----- Original Message ----- From: "Julian Elischer" To: "Peter Wemm" Cc: "FreeBSD current users" Sent: Saturday, July 06, 2002 8:43 AM Subject: i386 trap code > > Looking at i386/exception.s > one sees: > ################################### > .globl alltraps > .type alltraps,@function > alltraps: > pushal > pushl %ds > pushl %es > pushl %fs > alltraps_with_regs_pushed: > mov $KDSEL,%ax > mov %ax,%ds > mov %ax,%es > mov $KPSEL,%ax > mov %ax,%fs > FAKE_MCOUNT(13*4(%esp)) > calltrap: > FAKE_MCOUNT(btrap) /* init "from" btrap -> calltrap > */ > call trap > > /* > * Return via doreti to handle ASTs. > */ > MEXITCOUNT > jmp doreti > ####################################### > > but one has to look in isa/ipl.s to find: > ######################################## > SUPERALIGN_TEXT > .type doreti,@function > doreti: > FAKE_MCOUNT(bintr) /* init "from" bintr -> doreti */ > doreti_next: > /* > * Check if ASTs can be handled now. PSL_VM must be checked first > * since segment registers only have an RPL in non-VM86 mode. > */ > testl $PSL_VM,TF_EFLAGS(%esp) /* are we in vm86 mode? */ > jz doreti_notvm86 > cmpl $1,in_vm86call /* are we in a vm86 call? */ sorry for a bit OT, does anyone see this in_vm86call crazy global variable? it prevents two CPUs to trap into VM86 model :( if you have interest in fixing this problem, please have a look at PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/38223 I have also fixed the problem that VM86 call is preempted by interrupt threads and causes system crash. newest patch can always be gotten from : http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz -David Xu __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 20: 3:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F5B337B400 for ; Fri, 5 Jul 2002 20:03:07 -0700 (PDT) Received: from web20905.mail.yahoo.com (web20905.mail.yahoo.com [216.136.226.227]) by mx1.FreeBSD.org (Postfix) with SMTP id D145B43E31 for ; Fri, 5 Jul 2002 20:03:06 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020706030306.96129.qmail@web20905.mail.yahoo.com> Received: from [218.108.150.59] by web20905.mail.yahoo.com via HTTP; Fri, 05 Jul 2002 20:03:06 PDT Date: Fri, 5 Jul 2002 20:03:06 -0700 (PDT) From: David Xu Subject: Re: i386 trap code To: Julian Elischer Cc: Peter Wemm , FreeBSD current users 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 ----- Original Message ----- From: "Julian Elischer" To: "Peter Wemm" Cc: "FreeBSD current users" Sent: Saturday, July 06, 2002 8:43 AM Subject: i386 trap code > > Looking at i386/exception.s > one sees: > ################################### > .globl alltraps > .type alltraps,@function > alltraps: > pushal > pushl %ds > pushl %es > pushl %fs > alltraps_with_regs_pushed: > mov $KDSEL,%ax > mov %ax,%ds > mov %ax,%es > mov $KPSEL,%ax > mov %ax,%fs > FAKE_MCOUNT(13*4(%esp)) > calltrap: > FAKE_MCOUNT(btrap) /* init "from" btrap -> calltrap > */ > call trap > > /* > * Return via doreti to handle ASTs. > */ > MEXITCOUNT > jmp doreti > ####################################### > > but one has to look in isa/ipl.s to find: > ######################################## > SUPERALIGN_TEXT > .type doreti,@function > doreti: > FAKE_MCOUNT(bintr) /* init "from" bintr -> doreti */ > doreti_next: > /* > * Check if ASTs can be handled now. PSL_VM must be checked first > * since segment registers only have an RPL in non-VM86 mode. > */ > testl $PSL_VM,TF_EFLAGS(%esp) /* are we in vm86 mode? */ > jz doreti_notvm86 > cmpl $1,in_vm86call /* are we in a vm86 call? */ sorry for a bit OT, does anyone see this in_vm86call crazy global variable? it prevents two CPUs to trap into VM86 model :( if you have interest in fixing this problem, please have a look at PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/38223 I have also fixed the problem that VM86 call is preempted by interrupt threads and causes system crash. newest patch can always be gotten from : http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz -David Xu __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 20:36:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1553437B400 for ; Fri, 5 Jul 2002 20:36:10 -0700 (PDT) Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 050A443E54 for ; Fri, 5 Jul 2002 20:36:09 -0700 (PDT) (envelope-from imp@village.org) 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 g663a7Y53645 for ; Fri, 5 Jul 2002 21:36:07 -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 g663a6G77895 for ; Fri, 5 Jul 2002 21:36:06 -0600 (MDT) (envelope-from imp@village.org) Date: Fri, 05 Jul 2002 21:35:53 -0600 (MDT) Message-Id: <20020705.213553.111363127.imp@village.org> To: current@FreeBSD.ORG Subject: Re: Removing perl in make world From: "M. Warner Losh" In-Reply-To: <20020705170423.C24073@Odin.AC.HMC.Edu> References: <3D261EA4.ABC3AEC@mindspring.com> <20020705170423.C24073@Odin.AC.HMC.Edu> 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 NetBSD has a mtree.obsolete. Seems like that might not be a bad way to solve this generically. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 20:44:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FB4637B400 for ; Fri, 5 Jul 2002 20:44:35 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D810743E3B for ; Fri, 5 Jul 2002 20:44:34 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 XAA07345; Fri, 5 Jul 2002 23:44:29 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g663hxt29836; Fri, 5 Jul 2002 23:43:59 -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: <15654.26495.25741.948480@grasshopper.cs.duke.edu> Date: Fri, 5 Jul 2002 23:43:59 -0400 (EDT) To: julian@elischer.org Cc: freebsd-current@freebsd.org Subject: panic broken on alpha or scsi or up 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 Hi Julian, When I panic an alpha these days, I end up with the random_kthread spinning on the cpu stuck in msleep, and I never get the disks sync'ed (or, if I disable sync'ing, I never get through a dump): panic: vm_page_wakeup: page not busy!!! panic Stopped at Debugger+0x34: zapnot v0,#0xf,v0 db> c syncing disks... 3 3 Stopped at siointr1+0x198: br zero,siointr1+0x330 db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- msleep() at msleep+0x20 random_kthread() at random_kthread+0xb4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- db> c Stopped at siointr1+0x198: br zero,siointr1+0x330 db> where No such command db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- critical_exit() at critical_exit+0x20 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 msleep() at msleep+0x290 random_kthread() at random_kthread+0xb4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- db> reboot If I disable the randomness thing, I end up getting stuck in another kernel process: db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- critical_exit() at critical_exit+0x20 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 msleep() at msleep+0x290 buf_daemon() at buf_daemon+0x1f4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- I don't have this problem on my x86 testbox, but it has an IDE disk and is SMP. The alpha with the problem is UP, and uses a SCSI disk (isp controller). Any ideas? Are people able to get crashdumps on UP SCSI x86s? Thanks, Drew PS: I was going to make the subject "can't take a dump", but I thought the better of it ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 21:19:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3889D37B400 for ; Fri, 5 Jul 2002 21:19:43 -0700 (PDT) Received: from b.smtp-out.sonic.net (b.smtp-out.sonic.net [208.201.224.39]) by mx1.FreeBSD.org (Postfix) with SMTP id BA9F443E09 for ; Fri, 5 Jul 2002 21:19:42 -0700 (PDT) (envelope-from alex@blarf.homeip.net) Received: (qmail 10494 invoked from network); 6 Jul 2002 04:19:42 -0000 Received: from prop.sonic.net (208.201.224.193) by b.smtp-out.sonic.net with SMTP; 6 Jul 2002 04:19:42 -0000 Received: from blarf.homeip.net (adsl-209-204-188-56.sonic.net [209.204.188.56]) by prop.sonic.net (8.11.6/8.8.5) with ESMTP id g664Jf606312; Fri, 5 Jul 2002 21:19:42 -0700 X-envelope-info: Received: by blarf.homeip.net (Postfix, from userid 1000) id 89AA91BA6; Fri, 5 Jul 2002 21:19:41 -0700 (PDT) Date: Fri, 5 Jul 2002 21:19:41 -0700 From: Alex Zepeda To: Takanori Watanabe , current@freebsd.org Subject: Re: ACPI woes again.. Message-ID: <20020706041941.GA463@blarf.homeip.net> References: <20020705071640.GA739@blarf.homeip.net> <200207050945.SAA28267@axe-inc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207050945.SAA28267@axe-inc.co.jp> 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, Jul 05, 2002 at 06:46:05PM +0900, Takanori Watanabe wrote: > Would you review this description? How about: --- acpi.4.orig Thu Jun 13 02:50:06 2002 +++ acpi.4 Fri Jul 5 21:16:59 2002 @@ -258,10 +258,35 @@ bus/children scan of the namespace. The ACPI CA code will still know about the avoided region. +.Sh OVERRIDING YOUR BIOS BYTECODE +ACPI interprets bytecode named AML, ACPI Machine Language, provided by BIOS +vendor as memory image at boot time. Sometimes, the AML code contains +incorrect bytecode that does not wreak havoc with the Microsoft implementations +of ACPI. Such bugs can often times prevent FreeBSD from booting. In case of +such issues, we provide a way to override buggy AML with your own AML +code. +.Pp +In order to load your AML code, +you must edit +.Pa /boot/loader.conf +and +include the follwing lines. +.Bd -literal -offset indent +acpi_dsdt_load="YES" +acpi_dsdt_name="/boot/acpi_dsdt.aml" #You may change the name. +.Ed +.Pp +In order to prepare your AML code, you will require +.Xr acpidump 8 , +.Xr iasl 1 +in devel/acpicatools port, and some ACPI knowledge. + .Sh COMPATIBILITY ACPI is only found/supported on Intel platforms (i386/IA32 and IA64). .Sh SEE ALSO .Xr config 8 , +.Xr loader.conf 5 , +.Xr acpidump 8 , .Xr acpi 9 .Sh AUTHORS .An -nosplit - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 21:33:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 221C437B400 for ; Fri, 5 Jul 2002 21:33:41 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 564A343E3B for ; Fri, 5 Jul 2002 21:33:40 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 AAA08236; Sat, 6 Jul 2002 00:33:39 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g664X9829916; Sat, 6 Jul 2002 00:33: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: <15654.29445.578666.79579@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 00:33:09 -0400 (EDT) To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: panic broken on alpha or scsi or up In-Reply-To: <20020705212310.A41098@troutmask.apl.washington.edu> References: <15654.26495.25741.948480@grasshopper.cs.duke.edu> <20020705212310.A41098@troutmask.apl.washington.edu> 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 Steve Kargl writes: > On Fri, Jul 05, 2002 at 11:43:59PM -0400, Andrew Gallatin wrote: > > > > Any ideas? Are people able to get crashdumps on UP SCSI x86s? > > > > Yes. I can get dumps on an ahc (adaptec 2940) on a UP x86 box. > > Kernel was built with July 4th current sources. OK, thanks.. It must be alpha specific then. Thanks! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 22: 6: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2067437B400 for ; Fri, 5 Jul 2002 22:06:05 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6200C43E3B for ; Fri, 5 Jul 2002 22:06:04 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 BAA08641 for ; Sat, 6 Jul 2002 01:06:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6655XM29951; Sat, 6 Jul 2002 01:05:33 -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: <15654.31389.772589.952477@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 01:05:33 -0400 (EDT) To: freebsd-current@freebsd.org Subject: more on dumping 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 OK, current is really confusing me. When we are panic'ing and syncing disks, how are we supposed to come back to the current thread which caused the dump after we do an mi_switch() to allow an interrupt thread to run? The alpha seems to get stuck running various sorts of kernel processes, but it never comes back to the one that caused the dump. How is this supposed to work? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 22:33:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2906537B400 for ; Fri, 5 Jul 2002 22:33:17 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9237443E31 for ; Fri, 5 Jul 2002 22:33:16 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.3/8.12.3) with ESMTP id g665YT0M017481; Fri, 5 Jul 2002 22:34:34 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207060534.g665YT0M017481@gw.catspoiler.org> Date: Fri, 5 Jul 2002 22:33:43 -0700 (PDT) From: Don Lewis Subject: Re: Removing perl in make world To: paul@freebsd-services.com Cc: drosih@rpi.edu, tlambert2@mindspring.com, sheldonh@starjuice.net, current@FreeBSD.ORG In-Reply-To: <1025921146.881.16.camel@lobster.originative.co.uk> 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 6 Jul, Paul Richards wrote: > Let's start with a premise: No-one running current is using it for > anything other than developing FreeBSD. > > Given that premise, then there shouldn't be anything in /usr outside of > /usr/local, that wasn't put there by make world. Likewise the same > should be true of /sbin and /bin. The X11 ports install stuff under /usr/X11R6 ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 22:58:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3A7037B401 for ; Fri, 5 Jul 2002 22:58:39 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC17643E31 for ; Fri, 5 Jul 2002 22:58:38 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g665vhm16951; Sat, 6 Jul 2002 00:57:43 -0500 (CDT) (envelope-from jlemon) Date: Sat, 6 Jul 2002 00:57:43 -0500 (CDT) From: Jonathan Lemon Message-Id: <200207060557.g665vhm16951@prism.flugsvamp.com> To: bsddiy@yahoo.com, current@freebsd.org Subject: Re: i386 trap code X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: 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 article you write: >sorry for a bit OT, does anyone see this in_vm86call crazy global variable? >it prevents two CPUs to trap into VM86 model :( Um, unfortunately, this is by design. Most (all?) BIOSen code are single threaded, and the vm86 code shares the entire ISA hole, including the read/write BIOS data area. Allowing more than one CPU to execute BIOS code at once is asking for trouble, since there is no way to know what memory locations are being shared. Now that vm86_lock serves the same function, we could check that lock instead of of the global flag. >I have also fixed the problem that VM86 call is preempted by interrupt >threads and causes system crash. newest patch can always be gotten from : >http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz I haven't looked at vm86 for a long time, but the original code worked by preventing any ASTs from being taken until the BIOS returned. It's likely that this needs to be reworked for -current. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 5 23: 0:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D62D37B401 for ; Fri, 5 Jul 2002 23:00:14 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id F054F43E31 for ; Fri, 5 Jul 2002 23:00:13 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020706060013.GPSG903.sccrmhc03.attbi.com@InterJet.elischer.org>; Sat, 6 Jul 2002 06:00:13 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA16739; Fri, 5 Jul 2002 22:56:43 -0700 (PDT) Date: Fri, 5 Jul 2002 22:56:41 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: more on dumping In-Reply-To: <15654.31389.772589.952477@grasshopper.cs.duke.edu> 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 On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > OK, current is really confusing me. When we are panic'ing and syncing > disks, how are we supposed to come back to the current thread which > caused the dump after we do an mi_switch() to allow an interrupt > thread to run? > It depends. the previous thread should have been put back onto the run queue before the interrupt thread was scheduled. > The alpha seems to get stuck running various sorts of kernel > processes, but it never comes back to the one that caused the dump. > > How is this supposed to work? > > Thanks, > > Drew > > 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 Fri Jul 5 23: 0:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2810337B449 for ; Fri, 5 Jul 2002 23:00:25 -0700 (PDT) Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C96643E09 for ; Fri, 5 Jul 2002 23:00:24 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020706060023.GPTX903.sccrmhc03.attbi.com@InterJet.elischer.org>; Sat, 6 Jul 2002 06:00:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA16746; Fri, 5 Jul 2002 22:59:40 -0700 (PDT) Date: Fri, 5 Jul 2002 22:59:39 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: freebsd-current@freebsd.org Subject: Re: panic broken on alpha or scsi or up In-Reply-To: <15654.26495.25741.948480@grasshopper.cs.duke.edu> 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 put a breakpoint at msleep+0x290 then continue.. sprinkle a few breakpoints at locations you think other processes ahould be hitting if they were to be running.. On Fri, 5 Jul 2002, Andrew Gallatin wrote: > > Hi Julian, > > When I panic an alpha these days, I end up with the random_kthread > spinning on the cpu stuck in msleep, and I never get the disks sync'ed > (or, if I disable sync'ing, I never get through a dump): > > panic: vm_page_wakeup: page not busy!!! > panic > Stopped at Debugger+0x34: zapnot v0,#0xf,v0 > db> c > > syncing disks... 3 3 > > > > Stopped at siointr1+0x198: br > zero,siointr1+0x330 > db> tr > siointr1() at siointr1+0x198 > siointr() at siointr+0x40 > isa_handle_fast_intr() at isa_handle_fast_intr+0x24 > alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 > interrupt() at interrupt+0x110 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > msleep() at msleep+0x20 > random_kthread() at random_kthread+0xb4 > fork_exit() at fork_exit+0xe0 > exception_return() at exception_return > --- root of call graph --- > db> c > > > > Stopped at siointr1+0x198: br zero,siointr1+0x330 > > db> where > No such command > db> tr > siointr1() at siointr1+0x198 > siointr() at siointr+0x40 > isa_handle_fast_intr() at isa_handle_fast_intr+0x24 > alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 > interrupt() at interrupt+0x110 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > critical_exit() at critical_exit+0x20 > _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 > msleep() at msleep+0x290 > random_kthread() at random_kthread+0xb4 > fork_exit() at fork_exit+0xe0 > exception_return() at exception_return > --- root of call graph --- > db> reboot > > > If I disable the randomness thing, I end up getting stuck in another > kernel process: > > db> tr > siointr1() at siointr1+0x198 > siointr() at siointr+0x40 > isa_handle_fast_intr() at isa_handle_fast_intr+0x24 > alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 > interrupt() at interrupt+0x110 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > critical_exit() at critical_exit+0x20 > _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 > msleep() at msleep+0x290 > buf_daemon() at buf_daemon+0x1f4 > fork_exit() at fork_exit+0xe0 > exception_return() at exception_return > --- root of call graph --- > > > I don't have this problem on my x86 testbox, but it has > an IDE disk and is SMP. The alpha with the problem is > UP, and uses a SCSI disk (isp controller). > > Any ideas? Are people able to get crashdumps on UP SCSI x86s? > > Thanks, > > Drew > > PS: I was going to make the subject "can't take a dump", but > I thought the better of it ;) > > 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 Fri Jul 5 23:25:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 468FE37B400 for ; Fri, 5 Jul 2002 23:25:24 -0700 (PDT) Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA32943E09 for ; Fri, 5 Jul 2002 23:25:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0156.cvx40-bradley.dialup.earthlink.net ([216.244.42.156] helo=mindspring.com) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17Qj0L-0005uX-00; Sat, 06 Jul 2002 02:25:14 -0400 Message-ID: <3D268D1F.D96BC3F9@mindspring.com> Date: Fri, 05 Jul 2002 23:24:31 -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: David Xu Cc: Julian Elischer , Peter Wemm , FreeBSD current users Subject: Re: i386 trap code References: <20020706030306.96129.qmail@web20905.mail.yahoo.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 Xu wrote: > > testl $PSL_VM,TF_EFLAGS(%esp) /* are we in vm86 mode? */ > > jz doreti_notvm86 > > cmpl $1,in_vm86call /* are we in a vm86 call? */ > > sorry for a bit OT, does anyone see this in_vm86call crazy global variable? > it prevents two CPUs to trap into VM86 model :( > if you have interest in fixing this problem, please have a look at PR : This is on purpose. Most BIOS implementations are non-reentrant, and if you allocate resources in the bus space to BIOS based I/O, you end up contending for it without locks. This is "crossing the beams" bad... 8-). > http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/38223 > > I have also fixed the problem that VM86 call is preempted by interrupt > threads and causes system crash. newest patch can always be gotten from : > http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz I saw the fix. I like it, though it doesn't fix the handling using an interrupt gate to take interrupts in VM86() mode (the FreeBSD code doesn't do this at present, but it's a problem if you run under VMWare, I think). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 2: 7: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08A9637B400 for ; Sat, 6 Jul 2002 02:07:02 -0700 (PDT) Received: from web20906.mail.yahoo.com (web20906.mail.yahoo.com [216.136.226.228]) by mx1.FreeBSD.org (Postfix) with SMTP id B3C7743E31 for ; Sat, 6 Jul 2002 02:07:01 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020706090701.37865.qmail@web20906.mail.yahoo.com> Received: from [218.108.156.1] by web20906.mail.yahoo.com via HTTP; Sat, 06 Jul 2002 02:07:01 PDT Date: Sat, 6 Jul 2002 02:07:01 -0700 (PDT) From: David Xu Subject: Re: i386 trap code To: Jonathan Lemon , current@freebsd.org In-Reply-To: <200207060557.g665vhm16951@prism.flugsvamp.com> 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 --- Jonathan Lemon wrote: > In article > > you write: > >sorry for a bit OT, does anyone see this in_vm86call crazy global variable? > >it prevents two CPUs to trap into VM86 model :( > > Um, unfortunately, this is by design. Most (all?) BIOSen code are > single threaded, and the vm86 code shares the entire ISA hole, including > the read/write BIOS data area. Allowing more than one CPU to execute > BIOS code at once is asking for trouble, since there is no way to know > what memory locations are being shared. > > Now that vm86_lock serves the same function, we could check that lock > instead of of the global flag. > > > >I have also fixed the problem that VM86 call is preempted by interrupt > >threads and causes system crash. newest patch can always be gotten from : > >http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz > > I haven't looked at vm86 for a long time, but the original code worked > by preventing any ASTs from being taken until the BIOS returned. It's > likely that this needs to be reworked for -current. > -- > Jonathan I don't know if FreeBSD can run DOS program, if it can, then one CPU running DOS program can confuse another CPU which is running BIOS code because of this global flags. my current patch does not remove vm86_lock, it is still there, my orginal purpose is while CPU in VM86 mode, when hardware interrupt occurs, still allow interrupt thread to run. David Xu __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 2:15:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1361637B400 for ; Sat, 6 Jul 2002 02:15:47 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7D7843E3B for ; Sat, 6 Jul 2002 02:15:45 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 TAA16940; Sat, 6 Jul 2002 19:15:31 +1000 Date: Sat, 6 Jul 2002 19:21:39 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Jake Burkholder Cc: Julian Elischer , Peter Wemm , FreeBSD current users Subject: Re: i386 trap code In-Reply-To: <20020705212530.C839@locore.ca> Message-ID: <20020706185530.M4208-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 Fri, 5 Jul 2002, Jake Burkholder wrote: > Apparently, On Fri, Jul 05, 2002 at 05:43:26PM -0700, > Julian Elischer said words to the effect of; > > > > > Looking at i386/exception.s > > one sees: > > [...] > > > > > Now: > > > > would it not make a lot of sense to put doreti immediatly after > > calltrap: in the same file It would make little sense to put it immediatly (sic) after calltrap, since most jumps to it are not from there. > > so that one could follow the entire picture without having to bounce back > > and forth between two files? > > I'd say so, yeah. Its probably there because it used to be alongside > splz and unmasked pending isa interrupts. This is correct. In 386BSD-0.0, it was mainly for handing ICU masking after return from a hardware interrupt and it was in a file named icu.s. In FreeBSD-1, it only handled software masking and was still in icu.s. SMPog renamed it to ipl.s and pushed the hardware interrupt masking issues further away from it. SMPng pushed the software interrupt masking issues away from it (using nested includes, ugh). Its name still suggests that it is more for handling interrupts than traps, but interrupts are a special type of trap and it has nothing to do with isa or ipls, so it belongs more in i386/exception.s than in isa/ipl.s. But the nested includes in it don't logically belong there. > > > > (also gets rid of the jmp in the common case) > > System calls are probably the common case. But I'd suggest just put > it after the trap code at the end of the file and leave the jump. Its > super aligned so there would probably be a bunch of nops to plow through > anyway. Yes, it belongs near the end of the file, perhaps in the same place that it was included. I found that having all the exception and interrupt handling routines close together (on the same page?) made significant differences for microbenchmarks on i486's (presumably because the i486 L1 cache is so small or direct mapped). Better not change the order without running some benchmarks on old machines where this matters, though SMPng may have messed up the order or locality without really trying. (Micro-pessimizations were swamped by macro-pessimizations in SMPng so I didn't notice them, but I noticed micro-pessimizations for splitting the UPAGES from the stack.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 2:28:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C95E37B401 for ; Sat, 6 Jul 2002 02:28:34 -0700 (PDT) Received: from HAL9000.wox.org (12-233-156-170.client.attbi.com [12.233.156.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF70C43E3B for ; Sat, 6 Jul 2002 02:28:33 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.wox.org (localhost [127.0.0.1]) by HAL9000.wox.org (8.12.3/8.12.3) with ESMTP id g669Sfxq000970; Sat, 6 Jul 2002 02:28:42 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.wox.org (8.12.3/8.12.3/Submit) id g669SZ3x000969; Sat, 6 Jul 2002 02:28:35 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Sat, 6 Jul 2002 02:28:35 -0700 From: David Schultz To: David Xu Cc: Jonathan Lemon , current@FreeBSD.ORG Subject: Re: i386 trap code Message-ID: <20020706092835.GB709@HAL9000.wox.org> Mail-Followup-To: David Xu , Jonathan Lemon , current@FreeBSD.ORG References: <200207060557.g665vhm16951@prism.flugsvamp.com> <20020706090701.37865.qmail@web20906.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020706090701.37865.qmail@web20906.mail.yahoo.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 Thus spake David Xu : > I don't know if FreeBSD can run DOS program, if it can, then one CPU running > DOS program can confuse another CPU which is running BIOS code because of this > global flags. > > my current patch does not remove vm86_lock, it is still there, my orginal > purpose is while CPU in VM86 mode, when hardware interrupt occurs, still > allow interrupt thread to run. FreeBSD can run DOS programs, but it does so by emulating all of the common DOS and BIOS calls. You can't safely give untrusted userland programs direct access to the BIOS, and even if you could, the BIOS calls wouldn't work as the DOS programs expected them to. See doscmd(1). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 2:51:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5F5737B400 for ; Sat, 6 Jul 2002 02:51:52 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBDE043E3B for ; Sat, 6 Jul 2002 02:51:51 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 TAA18876; Sat, 6 Jul 2002 19:51:42 +1000 Date: Sat, 6 Jul 2002 19:57:50 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: more on dumping In-Reply-To: <15654.31389.772589.952477@grasshopper.cs.duke.edu> Message-ID: <20020706192954.I4315-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 Sat, 6 Jul 2002, Andrew Gallatin wrote: > OK, current is really confusing me. When we are panic'ing and syncing > disks, how are we supposed to come back to the current thread which > caused the dump after we do an mi_switch() to allow an interrupt > thread to run? > > The alpha seems to get stuck running various sorts of kernel > processes, but it never comes back to the one that caused the dump. > > How is this supposed to work? Accidentally at best. panic() cannot sleep and should not call mi_switch(), but sync() wants to do both. msleep() has a hack that prevents it from doing very much if (cold || panicstr). This works in most cases in FreeBSD-2, but has been rotting as the kernel became more complicated. Before KSEII, it was normal for synch() to hit a deadlock and panic recursively (with no sync() the second time). KSEII may have made things worse by putting a lot of code before the hack in msleep(). The cv_wait() family has the same (cold || panicstr) hack (including cloned (rotted) comments about doing something to give interrupts a chance) but no KSE checks before it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 4:39:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A08537B400 for ; Sat, 6 Jul 2002 04:39:17 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD1A743E09 for ; Sat, 6 Jul 2002 04:39:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0048.cvx40-bradley.dialup.earthlink.net ([216.244.42.48] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17Qnu9-000758-00; Sat, 06 Jul 2002 07:39:10 -0400 Message-ID: <3D26D66F.E107F645@mindspring.com> Date: Sat, 06 Jul 2002 04:37:19 -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: Garance A Drosihn Cc: Paul Richards , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> Content-Type: multipart/mixed; boundary="------------876B036AE35B5777F5EDA84A" 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. --------------876B036AE35B5777F5EDA84A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here are two files that make stateful configuration of world building somewhat easier. I expect that the way this will be used is to allow Paul, et. al. the option of setting a default, and having the system ask users if they want to live with Paul's default, or if they want to select their own default instead. This is a proof of concept; it works on my machine, but obviously it could be hacked until the end of time, and not everyone would be satisfied. Basically, you dump these two files int /usr/src, and then add # # System configuration # .include Before "TGTS=" at the top of /usr/src/Makefile. It will force you to select options (offerring defaults) for two example knobs. It then writes the results to a file called /etc/world.mk, which is then sucked back in by the Makefile.world, after it adds a .BEGIN target that causes the file to be rebuilt if it's missing any options. Basically, this means that you can incrementally add knobs, and anyone who builds, instead of getting surprised by the new knobs, ends up getting asked to select the new knob. If you are afraid of running from a cron script, you can: yes x | make world or make world < /dev/null And it will select the defaults, or: yes n | make world And it will turn all new knobs off automatically. You can edit the file by hand if you need/want to; knobs the script doesn't know about will go away, as will anything other than the default comments, but the ability is there for knobs it knows about. The script as written has two default knobs, "PRISTINE" and "BOB"; these are terrible names, but the are only intended as examples (I expect that the actuall names will be things like "KNOB_DELETE_INCLUDES" and "KNOB_DELETE_PERL", etc.). Basically, it ends up being three data lines in a shell script, per new knob. Note that I haven't tried a "make release" with this yet; I expect you will want to copy in the /etc/world.mk from the local system to do the build, or add the /dev/null redirect to the sub-shell in the jail for the build. -- Terry --------------876B036AE35B5777F5EDA84A Content-Type: text/plain; charset=us-ascii; name="Makefile.world" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Makefile.world" # Support mandatory option recording # # Original: 06 Jul 2002, Terry Lambert # WORLD_CONFIG= /etc/world.mk .BEGIN: @sh ${.CURDIR}/worldconfig.sh ${WORLD_CONFIG} .if exists(${WORLD_CONFIG}) .include "${WORLD_CONFIG}" .endif --------------876B036AE35B5777F5EDA84A Content-Type: application/x-sh; name="worldconfig.sh" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="worldconfig.sh" #!/bin/sh # # worldconfig.sh # # Original: 06 Jul 2002, Terry Lambert # PROGNAME=`basename $0` # mandatory shell variables VARS="" # ------------------------------------------------------------------------ VARS="PRISTINE $VARS" DEF_PRISTINE="NO" MSG_PRISTINE="\ \tYou must select whether or not to delete header files automatically\n \tand recreate them as part of the 'installworld' target.\n" VARS="BOB $VARS" DEF_BOB="YES" MSG_BOB="\ \tThis is a test\n \tThis is only a test\n" # ------------------------------------------------------------------------ # visual spacing ONCE=N # # Read yes/no from user, with default for no input # yesno() { printf "\tThe recommended answer is $2.\n\n" printf "\tEnable this option? " if [ "$2" = "YES" ] then echo -n "(YES)/NO : " read rdyn case $rdyn in N*|n*|F*|f*|0) rdyn="NO" ;; *) rdyn="YES" ;; esac else echo -n "YES/(NO) : " read rdyn case $rdyn in Y*|y*|T*|t*|1) rdyn="YES" ;; *) rdyn="NO" ;; esac fi } # # Handle a single element configuration # configone() { v_val=`eval echo \\$$1` v_def=`eval echo \\$DEF_$1` v_msg=`eval echo \\$MSG_$1` if [ "${v_val}x" = "x" ] then if [ "${ONCE}" = "N" ] then printf "\n\n" ONCE=Y fi printf "$1: No default\n\n" printf "${v_msg}\n" yesno $1 $v_def echo "$1=$rdyn" >> ${CONFIG} echo echo else echo "$1=${v_val}" >> ${CONFIG} fi } # # err: echo to stderr # err() { echo $* >&2 } fatal() { err "${PROGNAME}: $*" exit 1 } usage() { err "Usage: ${PROGNAME} config" exit 1 } # ------------------------------------------------ # Start printf "${PROGNAME}: Begin autoselect\n" # # Verify 1 argument -- the config file # if [ "$1x" = "x" -o "$2x" != "x" ] then usage fi CONFIG="$1" if [ ! -f ${CONFIG} ] then echo "Creating configuration file '${CONFIG}' (first time)" touch ${CONFIG} if [ "$?" != "0" ] then fatal "Could not create file ${CONFIG}" exit 1 fi fi # # Pull in the contents of "foo"; if this is the first time, then # this will do nothing, because the file is empty # . ${CONFIG} # # Create new file # cp ${CONFIG} ${CONFIG}.old if [ "$?" != "0" ] then fatal "Could not copy '${CONFIG}' to '${CONFIG}.old'" fi DATE=`date` cat > ${CONFIG} <; Sat, 6 Jul 2002 04:42:57 -0700 (PDT) Received: from imailg3.svr.pol.co.uk (imailg3.svr.pol.co.uk [195.92.195.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68D5443E09 for ; Sat, 6 Jul 2002 04:42:56 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-510.awesome.dialup.pol.co.uk ([62.25.129.254] helo=mailgate.originative.co.uk) by imailg3.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17Qnxh-0001WW-00; Sat, 06 Jul 2002 12:42:49 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id B48E51D13D; Sat, 6 Jul 2002 12:42:42 +0100 (BST) Subject: Re: Removing perl in make world From: Paul Richards To: Garance A Drosihn Cc: Terry Lambert , Sheldon Hearn , current@FreeBSD.ORG In-Reply-To: References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> <1025921146.881.16.camel@lobster.originative.co.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 06 Jul 2002 12:42:53 +0100 Message-Id: <1025955773.881.29.camel@lobster.originative.co.uk> Mime-Version: 1.0 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, 2002-07-06 at 03:46, Garance A Drosihn wrote: > At 3:05 AM +0100 7/6/02, Paul Richards wrote: > >Let's start with a premise: No-one running current is using > >it for anything other than developing FreeBSD. > > This is assumption is too limiting. It shouldn't be. You're trying to defend a position that the project doesn't support. The -current branch is for FreeBSD developers, or volunteers brave enough to test the -current branch. As such, don't be surprised if it wipes your hard disk clean. > People running -current are doing it to test the latest builds. > What they *do* to test it is their business. Ie, if I want to > install some port in /usr instead of /usr/local, that is something > I should be able to do. You're free to do that, but you're not really testing -current then, since you're doing things outside the scope of what -current is designed to support. If you're doing stuff to stress it in some way that's particular to you're testing regime then fine, but that's something you'd need to be aware of and it's not that different to installing a personal, more up to date version of gcc in the base, if you do that you need to be aware that the standard current build system will overwrite your changes. A 'sysclean' target would be the same in my mind. If you're "within spec" of what -current supports then running that target shouldn't hose you. If you're outside spec then you need to take your own precautions. I'm not suggesting that 'sysclean' be a default part of installworld anymore. I suggested that removing perl should be, but the debate has moved on from that position and I think the sensible thing now would be to create a 'sysclean' target, that could be run as desired that was more comprehensive than just removing perl or other deprecated apps. A more aggressive cleaning target I think solves more problems more effectively and if it's an optional target I can't see any problems. Probably a make.conf knob, like the update target uses, so people can have it on or off as part of the standard build as they desire. I think having it as a make target is a good thing, since it would allow us to easily document that people who truly want to test current should run that target after a build to ensure they're not running old stuff. It keeps the code tied into the build process too. A separate optional script wouldn't be as well integrated into our build setup. -- Paul Richards | FreeBSD Services Ltd | Order 4.6 on DVD now. http://www.freebsd-services.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 4:48: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 745F937B400 for ; Sat, 6 Jul 2002 04:47:58 -0700 (PDT) Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA99B43E42 for ; Sat, 6 Jul 2002 04:47:16 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0048.cvx40-bradley.dialup.earthlink.net ([216.244.42.48] helo=mindspring.com) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17Qo1h-0003AR-00; Sat, 06 Jul 2002 07:46:58 -0400 Message-ID: <3D26D83F.69219DF6@mindspring.com> Date: Sat, 06 Jul 2002 04:45:03 -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: Paul Richards Cc: Garance A Drosihn , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> <1025921146.881.16.camel@lobster.originative.co.uk> <1025955773.881.29.camel@lobster.originative.co.uk> 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 Paul Richards wrote: > On Sat, 2002-07-06 at 03:46, Garance A Drosihn wrote: > > At 3:05 AM +0100 7/6/02, Paul Richards wrote: > > >Let's start with a premise: No-one running current is using > > >it for anything other than developing FreeBSD. > > > > This is assumption is too limiting. > > It shouldn't be. You're trying to defend a position that the project > doesn't support. The -current branch is for FreeBSD developers, or > volunteers brave enough to test the -current branch. > > As such, don't be surprised if it wipes your hard disk clean. It's really "less testing of what will eventually be released and more testers, vs. more testing of what will be eventually released and less testers". It's a saddle curve. Please see the patches I just posted; I think they will permit everyone to "be happy" by letting you add knobs that do what you want to do, set defaults, and then permit people to opt out of those defaults, without having to worry that your default settings will sneak up on them and (e.g.) delete perl out from under them. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 5:15:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 263AE37B400 for ; Sat, 6 Jul 2002 05:15:27 -0700 (PDT) Received: from web20903.mail.yahoo.com (web20903.mail.yahoo.com [216.136.226.225]) by mx1.FreeBSD.org (Postfix) with SMTP id CDE4243E31 for ; Sat, 6 Jul 2002 05:15:26 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020706121526.65635.qmail@web20903.mail.yahoo.com> Received: from [218.108.157.18] by web20903.mail.yahoo.com via HTTP; Sat, 06 Jul 2002 05:15:26 PDT Date: Sat, 6 Jul 2002 05:15:26 -0700 (PDT) From: David Xu Subject: Re: i386 trap code To: David Schultz Cc: Jonathan Lemon , current@FreeBSD.ORG In-Reply-To: <20020706092835.GB709@HAL9000.wox.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 --- David Schultz wrote: > Thus spake David Xu : > > I don't know if FreeBSD can run DOS program, if it can, then one CPU > running > > DOS program can confuse another CPU which is running BIOS code because of > this > > global flags. > > > > my current patch does not remove vm86_lock, it is still there, my orginal > > purpose is while CPU in VM86 mode, when hardware interrupt occurs, still > > allow interrupt thread to run. > > FreeBSD can run DOS programs, but it does so by emulating all of > the common DOS and BIOS calls. You can't safely give untrusted > userland programs direct access to the BIOS, and even if you > could, the BIOS calls wouldn't work as the DOS programs expected > them to. See doscmd(1). I don't know how DOS emulating program works, but if it let DOS program run in VM86 mode, the in_vm86call global flag can prevent one CPU to run VM86 BIOS call and another CPU run DOS VM86 code, because it can not distinct which CPU the kernel is calling BIOS and which CPU is running VM86 DOS code, under SMP this is a problem. for exapmle, vesa module running on first CPU is calling VM86 BIOS, and second CPU is running DOS program, the DOS program maybe simply executes a privilege instruction to trigger trap, and the CPU will see itself calling VM86 BIOS, but it shouldn't. David Xu __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 5:30:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85A6A37B400 for ; Sat, 6 Jul 2002 05:30:20 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 817BC43E4A for ; Sat, 6 Jul 2002 05:30:16 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g66CTqt43793; Sat, 6 Jul 2002 15:29:52 +0300 (EEST) (envelope-from ru) Date: Sat, 6 Jul 2002 15:29:52 +0300 From: Ruslan Ermilov To: Paul Richards Cc: current@FreeBSD.ORG Subject: Re: Removing perl in make world Message-ID: <20020706122952.GE40599@sunbay.com> References: <1025862341.1573.40.camel@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lkTb+7nhmha7W+c3" Content-Disposition: inline In-Reply-To: <1025862341.1573.40.camel@lobster.originative.co.uk> 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 --lkTb+7nhmha7W+c3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 05, 2002 at 10:45:41AM +0100, Paul Richards wrote: > I think we should add a target to make world that checks for the > existence of an old base install of Perl and removes it if it exists. >=20 > As a general principle, if we do things like remove code during -current > development then make world needs to cater for that change. The idea of > make world is that what you get at the end of it is a pristine install > of a snapshot of FreeBSD from the current branch. >=20 > The bootstrap target was originally added for this purpose, to deal with > issues during releases i.e. to bootstrap from one version of current to > another. It's got misunderstood along the way to mean bootstrapping > tools needed early in the build process. >=20 > I'd like to resurrect it's original meaning and add code to clean out > old versions of Perl. >=20 I strongly object to this unless we clearly define the procedure of deleting the old stuff like libraries, headers, programs, etc. I routinely do the cleanup by installing the world into a separate DESTDIR, and comparing it with what is available under /. I don't see a major problem with this except maybe a space. Another approarch is to compare the modification times with the current date; this works almost ok for all things except headers and (now) static libraries plus some miscellaneous stuff that is getting installed with -C. 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 --lkTb+7nhmha7W+c3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9JuLAUkv4P6juNwoRAgvPAJ4/b0eCBR0FMyP3O0VYqH4xga/vWACeO/2k tS10ZogO/hd6DdJytTqIfbQ= =M141 -----END PGP SIGNATURE----- --lkTb+7nhmha7W+c3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 5:39:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 569DF37B400; Sat, 6 Jul 2002 05:39:38 -0700 (PDT) Received: from cmailg5.svr.pol.co.uk (cmailg5.svr.pol.co.uk [195.92.195.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DF2643E4A; Sat, 6 Jul 2002 05:39:37 -0700 (PDT) (envelope-from paul@freebsd-services.com) Received: from modem-182.arcanine.dialup.pol.co.uk ([217.135.21.182] helo=mailgate.originative.co.uk) by cmailg5.svr.pol.co.uk with esmtp (Exim 3.35 #1) id 17Qoqe-0006UW-00; Sat, 06 Jul 2002 13:39:36 +0100 Received: from lobster.originative.co.uk (lobster.originative.co.uk [10.0.0.254]) by mailgate.originative.co.uk (Postfix) with ESMTP id 5D0BC1D13D; Sat, 6 Jul 2002 13:39:35 +0100 (BST) Subject: Re: Removing perl in make world From: Paul Richards To: Ruslan Ermilov Cc: current@FreeBSD.ORG In-Reply-To: <20020706122952.GE40599@sunbay.com> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020706122952.GE40599@sunbay.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 06 Jul 2002 13:39:46 +0100 Message-Id: <1025959186.881.38.camel@lobster.originative.co.uk> Mime-Version: 1.0 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, 2002-07-06 at 13:29, Ruslan Ermilov wrote: > On Fri, Jul 05, 2002 at 10:45:41AM +0100, Paul Richards wrote: > > I think we should add a target to make world that checks for the > > existence of an old base install of Perl and removes it if it exists. > > > > As a general principle, if we do things like remove code during -current > > development then make world needs to cater for that change. The idea of > > make world is that what you get at the end of it is a pristine install > > of a snapshot of FreeBSD from the current branch. > > > > The bootstrap target was originally added for this purpose, to deal with > > issues during releases i.e. to bootstrap from one version of current to > > another. It's got misunderstood along the way to mean bootstrapping > > tools needed early in the build process. > > > > I'd like to resurrect it's original meaning and add code to clean out > > old versions of Perl. > > > I strongly object to this unless we clearly define the procedure of > deleting the old stuff like libraries, headers, programs, etc. > I routinely do the cleanup by installing the world into a separate > DESTDIR, and comparing it with what is available under /. I don't > see a major problem with this except maybe a space. Another approarch > is to compare the modification times with the current date; this > works almost ok for all things except headers and (now) static > libraries plus some miscellaneous stuff that is getting installed > with -C. You need to catch up with the rest of this thread, since I think we're moving towards something more acceptable. However, in the particular case of Perl, I think it does highlight a slightly separate issue in that our build process has no concept of deprecating parts of the OS. The 'sysclean' target will "accidentally" deal with the Perl issue, but I don't think it's wrong to have a target remove a module that has been removed from source since that's what installing the system should really do if the system has opted to deprecate something. -- Paul Richards | FreeBSD Services Ltd | Order 4.6 on DVD now. http://www.freebsd-services.com | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 6:21:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35F9237B408 for ; Sat, 6 Jul 2002 06:21:22 -0700 (PDT) Received: from kwiatek.eu.org (kwiatek.eu.org [193.110.123.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53F8443E09 for ; Sat, 6 Jul 2002 06:21:21 -0700 (PDT) (envelope-from kwiatek@tpi.pl) Received: from localhost (localhost [127.0.0.1]) by kwiatek.eu.org (Postfix) with ESMTP id 06DD232C57 for ; Sat, 6 Jul 2002 15:16:26 +0200 (CEST) Date: Sat, 6 Jul 2002 15:16:26 +0200 (CEST) From: Andrzej Kwiatkowski X-X-Sender: kwiatek@kwiatek.eu.org To: freebsd-current@freebsd.org Subject: subscribe freebsd-current Message-ID: <20020706151613.W80433-100000@kwiatek.eu.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 ---------- Andrzej Kwiatkowski tpinternet unix system administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 7:20:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2B1037B400 for ; Sat, 6 Jul 2002 07:20:24 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB5B843E52 for ; Sat, 6 Jul 2002 07:20:20 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 KAA15257; Sat, 6 Jul 2002 10:20:19 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g66EJnB33383; Sat, 6 Jul 2002 10:19:49 -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: <15654.64645.513754.920800@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 10:19:49 -0400 (EDT) To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: more on dumping In-Reply-To: <20020706192954.I4315-100000@gamplex.bde.org> References: <15654.31389.772589.952477@grasshopper.cs.duke.edu> <20020706192954.I4315-100000@gamplex.bde.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 Bruce Evans writes: > On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > OK, current is really confusing me. When we are panic'ing and syncing > > disks, how are we supposed to come back to the current thread which > > caused the dump after we do an mi_switch() to allow an interrupt > > thread to run? > > > > The alpha seems to get stuck running various sorts of kernel > > processes, but it never comes back to the one that caused the dump. > > > > How is this supposed to work? > > Accidentally at best. panic() cannot sleep and should not call That's the impression I've been getting too ;) > mi_switch(), but sync() wants to do both. msleep() has a hack that > prevents it from doing very much if (cold || panicstr). This works > in most cases in FreeBSD-2, but has been rotting as the kernel became > more complicated. Before KSEII, it was normal for synch() to hit a > deadlock and panic recursively (with no sync() the second time). KSEII > may have made things worse by putting a lot of code before the hack > in msleep(). The cv_wait() family has the same (cold || panicstr) I tried adding the panicstr hack to the new KSE code in msleep(), but it had no noticable affect. I may have done it wrong, as it was a blind stab w/o any understanding (just skip the KSE code if panicstr). > hack (including cloned (rotted) comments about doing something to give > interrupts a chance) but no KSE checks before it. > > Bruce Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 7:34:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC93D37B400 for ; Sat, 6 Jul 2002 07:34:14 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B060B43E4A for ; Sat, 6 Jul 2002 07:34:13 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 KAA15431; Sat, 6 Jul 2002 10:34:13 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g66EXhP33398; Sat, 6 Jul 2002 10:33:43 -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: <15654.65479.31155.182179@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 10:33:43 -0400 (EDT) To: Julian Elischer Cc: freebsd-current@freebsd.org Subject: Re: more on dumping In-Reply-To: References: <15654.31389.772589.952477@grasshopper.cs.duke.edu> 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 Julian Elischer writes: > > > On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > > > > > OK, current is really confusing me. When we are panic'ing and syncing > > disks, how are we supposed to come back to the current thread which > > caused the dump after we do an mi_switch() to allow an interrupt > > thread to run? > > > > It depends. > > the previous thread should have been put back onto the run queue > before the interrupt thread was scheduled. Could it have anything to do with interrupt preemption being disabled on alpha & enabled on i386? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 7:42: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0CAA37B400 for ; Sat, 6 Jul 2002 07:42:02 -0700 (PDT) Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA6143E09 for ; Sat, 6 Jul 2002 07:42:01 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 3.36 #1) id 17Qqln-000Aux-00; Sat, 06 Jul 2002 16:42:43 +0200 Date: Sat, 6 Jul 2002 16:42:43 +0200 From: Sheldon Hearn To: Terry Lambert , Paul Richards , current@freebsd.org Subject: Re: Removing perl in make world Message-ID: <20020706144243.GC41933@starjuice.net> Mail-Followup-To: Terry Lambert , Paul Richards , current@freebsd.org References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <3D258F80.BD86F9D0@mindspring.com> <20020705152402.GD775@starjuice.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020705152402.GD775@starjuice.net> User-Agent: Mutt/1.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 On (2002/07/05 17:24), Sheldon Hearn wrote: > You and Paul are both pretty "out there" if you think -current users > will graciously accept a new world order in which ports linked > dymanically against system libraries won't work between a system upgrade > and the next port reinstall. Sorry about the "heat" of my post. I was stressed out and shouldn't even have been reading my FreeBSD mail to start with. I liked Mark Murray's response to Paul's suggestion much better than my own. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 8: 3:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2514237B400 for ; Sat, 6 Jul 2002 08:03:33 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54E4A43E31 for ; Sat, 6 Jul 2002 08:03:32 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id g66F3Sri006962; Sat, 6 Jul 2002 08:03:28 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id g66F3RIc006960; Sat, 6 Jul 2002 08:03:27 -0700 Date: Sat, 6 Jul 2002 08:03:27 -0700 From: Brooks Davis To: Paul Richards Cc: Garance A Drosihn , Terry Lambert , Sheldon Hearn , current@FreeBSD.ORG Subject: Re: Removing perl in make world Message-ID: <20020706080327.A5654@Odin.AC.HMC.Edu> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> <1025921146.881.16.camel@lobster.originative.co.uk> <1025955773.881.29.camel@lobster.originative.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1025955773.881.29.camel@lobster.originative.co.uk>; from paul@freebsd-services.com on Sat, Jul 06, 2002 at 12:42:53PM +0100 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu 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 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 06, 2002 at 12:42:53PM +0100, Paul Richards wrote: > On Sat, 2002-07-06 at 03:46, Garance A Drosihn wrote: > > At 3:05 AM +0100 7/6/02, Paul Richards wrote: > > >Let's start with a premise: No-one running current is using > > >it for anything other than developing FreeBSD. > >=20 > > This is assumption is too limiting. >=20 > It shouldn't be. You're trying to defend a position that the project > doesn't support. The -current branch is for FreeBSD developers, or > volunteers brave enough to test the -current branch. > > As such, don't be surprised if it wipes your hard disk clean. There's a significant difference between not supporting something and activly breaking it. In any case, I don't agree with that view because I've found that the best way to keep up with -current is to run it as a production desktop. It's worked quite well for several years with only a few minor bumps. Please don't break this. > I think having it as a make target is a good thing, since it would allow > us to easily document that people who truly want to test current should > run that target after a build to ensure they're not running old stuff. > It keeps the code tied into the build process too. A separate optional > script wouldn't be as well integrated into our build setup. A make target is a lousy place because it is too hard to figure out what it does until it's happened. If you're going to just nuke things at random, you might as well reinstall the box every time. It would be cleaner if that's your goal and it wouldn't hurt the rest of us. If you really want a build target, a target that runs something based on an mtree.obsolete file would be reasionable since there would be exactly one place to look. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9Jwa/XY6L6fI4GtQRAnLcAJ9cn9DyL8jr2VcnSneuXc8xByeRKgCgjoHm YFluVIZE2ItOXTnofxArcRA= =OvS0 -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 8:17:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7483137B400 for ; Sat, 6 Jul 2002 08:17:45 -0700 (PDT) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3329043E42 for ; Sat, 6 Jul 2002 08:17:41 -0700 (PDT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.12.4/8.12.4) with ESMTP id g66FHe25066606 for ; Sat, 6 Jul 2002 08:17:40 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.12.4/8.12.4/Submit) id g66FHe0g066605 for current@freebsd.org; Sat, 6 Jul 2002 08:17:40 -0700 (PDT) Date: Sat, 6 Jul 2002 08:17:40 -0700 (PDT) From: David Wolfskill Message-Id: <200207061517.g66FHe0g066605@bunrab.catwhisker.org> To: current@freebsd.org Subject: Incomplete shutdown for -CURRENT built today 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 Thatis, after issuing sudo boot0cfg -s 1 ad0 && sudo halt -p I see (on the serial console): Additional TCP options:. Starting background filesystem checks Sat Jul 6 08:07:46 PDT 2002 FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) login: Juboot() called on cpu#0 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... done And at that point, nothing further. I'm able to ping the machine, but I didn't see the (usual) mention of an attempt to shut power off via ACPI. (Sometimes that would work; sometimes it would time out, but this is the first time I recall not seeing the attempt logged.) I just tried sending a BREAK (to the serial console) [I think I have BREAK_TO_DEBUGGER in the kernel...]; no response. CVSup started at 0347 hs. PDT, using cvsup14 as server. I suppose I'll need to reboot and poke around a bit..... Cheers, david -- David H. Wolfskill david@catwhisker.org Trying to support or use Microsoft products makes about as much sense as painting the outside of a house with watercolors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 9: 8: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E4A537B400 for ; Sat, 6 Jul 2002 09:08:05 -0700 (PDT) Received: from prism.flugsvamp.com (66-191-112-47.mad.wi.charter.com [66.191.112.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79DF343E31 for ; Sat, 6 Jul 2002 09:08:04 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.6/8.11.6) id g66G6wm36913; Sat, 6 Jul 2002 11:06:58 -0500 (CDT) (envelope-from jlemon) Date: Sat, 6 Jul 2002 11:06:58 -0500 From: Jonathan Lemon To: David Xu Cc: David Schultz , Jonathan Lemon , current@FreeBSD.ORG Subject: Re: i386 trap code Message-ID: <20020706110658.A36596@prism.flugsvamp.com> References: <20020706092835.GB709@HAL9000.wox.org> <20020706121526.65635.qmail@web20903.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20020706121526.65635.qmail@web20903.mail.yahoo.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 Sat, Jul 06, 2002 at 05:15:26AM -0700, David Xu wrote: > > I don't know how DOS emulating program works, but if it let DOS > program run in VM86 mode, the in_vm86call global flag can prevent > one CPU to run VM86 BIOS call and another CPU run DOS VM86 code, > because it can not distinct which CPU the kernel is calling BIOS > and which CPU is running VM86 DOS code, under SMP this is a problem. > for exapmle, vesa module running on first CPU is calling VM86 BIOS, > and second CPU is running DOS program, the DOS program maybe simply > executes a privilege instruction to trigger trap, and the CPU > will see itself calling VM86 BIOS, but it shouldn't. The virtual vm86 mode that doscmd(1) uses is different than the vm86 bios calls (or bios16, or bios32) which allows direct execution of BIOS code. They do not have much in common. doscmd() does not directly execute any of the BIOS code; it provides its own BIOS emulator. The scenario you postulate above cannot exist. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 9:44:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F51B37B400 for ; Sat, 6 Jul 2002 09:44:50 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07EE543E09 for ; Sat, 6 Jul 2002 09:44:49 -0700 (PDT) (envelope-from bde@zeta.org.au) 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 CAA06979; Sun, 7 Jul 2002 02:44:40 +1000 Date: Sun, 7 Jul 2002 02:50:48 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Andrew Gallatin Cc: Julian Elischer , Subject: Re: more on dumping In-Reply-To: <15654.65479.31155.182179@grasshopper.cs.duke.edu> Message-ID: <20020707024114.A5419-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 Sat, 6 Jul 2002, Andrew Gallatin wrote: > Julian Elischer writes: > > On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > OK, current is really confusing me. When we are panic'ing and syncing > > > disks, how are we supposed to come back to the current thread which > > > caused the dump after we do an mi_switch() to allow an interrupt > > > thread to run? > > > > It depends. > > > > the previous thread should have been put back onto the run queue > > before the interrupt thread was scheduled. > > Could it have anything to do with interrupt preemption being disabled on > alpha & enabled on i386? Very likely. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 13: 8:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D0C837B400 for ; Sat, 6 Jul 2002 13:08:47 -0700 (PDT) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF79343E31 for ; Sat, 6 Jul 2002 13:08:46 -0700 (PDT) (envelope-from cbh@teabag.demon.co.uk) Received: from teabag.demon.co.uk ([193.237.4.110] helo=teabag.cbhnet) by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2) id 17QvrF-00010L-0U for current@freebsd.org; Sat, 06 Jul 2002 21:08:41 +0100 Received: from localhost (localhost [127.0.0.1]) by teabag.cbhnet (Postfix) with ESMTP id 2408965032 for ; Sat, 6 Jul 2002 21:08:39 +0100 (BST) Date: Sat, 6 Jul 2002 21:08:39 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teabag.cbhnet To: current@freebsd.org Subject: Possible solution to /tmp on md filesystem Message-ID: <20020706210223.H698-100000@teabag.cbhnet> 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 Hi all, If anyone's still looking at the /tmp on md stuff, I've thrown together a workaround/solution based on the "mount_md" idea. Okay, I know that using a shell-script for a mount program may be seen as a Bad Thing and I'm not sure I want to broadcast my duff shell-programming for all to see, but I'll post it if anyone's interested. What I've done is to create a proto file for disklabel to use based on the intended size of the filesystem as specified in /etc/fstab which creates a normal multi-partition disc style "a" partition which skips the first cylinder, newfses it and mounts the result. Seems to work okay, although since it mucks about with disklabel then I'd recommend some caution. If it turns out to be useful I'm happy to convert it into a rather more robust C equivalent. This is, of course, based on the assumption that I haven't entirely missed the point! :) Cheers, Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 13: 9:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34A8737B400 for ; Sat, 6 Jul 2002 13:09:51 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 805F543E42 for ; Sat, 6 Jul 2002 13:09:50 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 QAA19789; Sat, 6 Jul 2002 16:09:46 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g66K9GF33725; Sat, 6 Jul 2002 16:09:16 -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: <15655.20076.568156.307089@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 16:09:16 -0400 (EDT) To: David Wolfskill Cc: current@freebsd.org Subject: Re: Incomplete shutdown for -CURRENT built today In-Reply-To: <200207061517.g66FHe0g066605@bunrab.catwhisker.org> References: <200207061517.g66FHe0g066605@bunrab.catwhisker.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 David Wolfskill writes: > syncing disks... > done > > And at that point, nothing further. I'm able to ping the machine, but I > didn't see the (usual) mention of an attempt to shut power off via ACPI. > (Sometimes that would work; sometimes it would time out, but this is the > first time I recall not seeing the attempt logged.) > > I just tried sending a BREAK (to the serial console) [I think I have > BREAK_TO_DEBUGGER in the kernel...]; no response. Me too! But a break to debugger seemed to work for me: Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 6 6 done [halt sent] Stopped at siointr1+0x198: br zero,siointr1+0x330 db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- kserunnable() at kserunnable+0x10 idle_proc() at idle_proc+0x78 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- db> reboot (this is a UP alpha). I'm glad this happened on x86 too! I was beginning to think boot was only broken on alpha ;) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 13:20:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13E9737B401 for ; Sat, 6 Jul 2002 13:20:03 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0261A43E3B for ; Sat, 6 Jul 2002 13:20:01 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) 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 QAA19882; Sat, 6 Jul 2002 16:19:58 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g66KJSD33734; Sat, 6 Jul 2002 16:19:28 -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: <15655.20688.169088.756630@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 16:19:28 -0400 (EDT) To: Bruce Evans Cc: Julian Elischer , Subject: Re: more on dumping In-Reply-To: <20020707024114.A5419-100000@gamplex.bde.org> References: <15654.65479.31155.182179@grasshopper.cs.duke.edu> <20020707024114.A5419-100000@gamplex.bde.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 Bruce Evans writes: > On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > Julian Elischer writes: > > > On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > > > OK, current is really confusing me. When we are panic'ing and syncing > > > > disks, how are we supposed to come back to the current thread which > > > > caused the dump after we do an mi_switch() to allow an interrupt > > > > thread to run? > > > > > > It depends. > > > > > > the previous thread should have been put back onto the run queue > > > before the interrupt thread was scheduled. > > > > Could it have anything to do with interrupt preemption being disabled on > > alpha & enabled on i386? > > Very likely. > > Bruce Unfortunately, that wasn't it. After reverting all my local hacks, I see that the system ends up here: db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- _mtx_unlock_flags() at _mtx_unlock_flags+0x8c kthread_suspend_check() at kthread_suspend_check+0xbc buf_daemon() at buf_daemon+0x80 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- I think that the buf_daemon just happened to wake up at the wrong time, and the panicstr hacks in msleep prevent it from ever going back to sleep again once it is awake. Now that I realize this, I suspect the same thing happened with the random_kthread that I was talking about earlier. Perhaps there is something about alpha's hz being 1024 which is making it more likely to loose whatever race is won on i386. Humerously enough, if I clear panicstr in panic(), then crashes work (for a loose definition of work, who knows what they mean!), with the added "benefit" of marking the filesystems clean: panic: vm_page_wakeup: page not busy!!! panic Stopped at Debugger+0x34: zapnot v0,#0xf,v0 db> c Waiting (max 60 seconds) for system process `vnlru' to stop...stopped Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... 1 1 done Uptime: 3m17s Dumping 509 MB pid 569 (scp), uid 1387: exited on signal 4 (core dumped) pid 539 (tcsh), uid 1387: exited on signal 4 (core dumped) pid 538 (sshd), uid 1387: exited on signal 4 pid 536 (sshd), uid 0: exited on signal 4 pid 481 (sshd), uid 0: exited on signal 4 pid 442 (ntpd), uid 0: exited on signal 4 16 32 48 64 80 96 112pid 530 (cron), uid 0: exited on signal 4 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Maybe we need to strengthen to the panicstr hacks and only allow the thread which caused the crash and interrupt threads to be scheduled once a panic occurs. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 13:56:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A269537B432 for ; Sat, 6 Jul 2002 13:56:04 -0700 (PDT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DBCA43E42 for ; Sat, 6 Jul 2002 13:56:03 -0700 (PDT) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) by srv1.cosmo-project.de (8.12.3/8.12.3) with ESMTP id g66KtsMa016731 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sat, 6 Jul 2002 22:55:56 +0200 (CEST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (localhost [IPv6:::1]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g66KtsFJ045086 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 6 Jul 2002 22:55:54 +0200 (CEST)?g (envelope-from ticso@cicely5.cicely.de) Received: (from ticso@localhost) by cicely5.cicely.de (8.12.1/8.12.1/Submit) id g66Ktrpo045085; Sat, 6 Jul 2002 22:55:53 +0200 (CEST)?g (envelope-from ticso) Date: Sat, 6 Jul 2002 22:55:52 +0200 From: Bernd Walter To: Chris Hedley Cc: current@FreeBSD.ORG Subject: Re: Possible solution to /tmp on md filesystem Message-ID: <20020706205552.GD23704@cicely5.cicely.de> Reply-To: ticso@cicely.de References: <20020706210223.H698-100000@teabag.cbhnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020706210223.H698-100000@teabag.cbhnet> X-Operating-System: FreeBSD cicely5.cicely.de 5.0-CURRENT i386 User-Agent: Mutt/1.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 On Sat, Jul 06, 2002 at 09:08:39PM +0100, Chris Hedley wrote: > Hi all, > > If anyone's still looking at the /tmp on md stuff, I've thrown together a > workaround/solution based on the "mount_md" idea. Okay, I know that using > a shell-script for a mount program may be seen as a Bad Thing and I'm not > sure I want to broadcast my duff shell-programming for all to see, but > I'll post it if anyone's interested. What I've done is to create a proto > file for disklabel to use based on the intended size of the filesystem as > specified in /etc/fstab which creates a normal multi-partition disc style > "a" partition which skips the first cylinder, newfses it and mounts the > result. Seems to work okay, although since it mucks about with disklabel > then I'd recommend some caution. > > If it turns out to be useful I'm happy to convert it into a rather more > robust C equivalent. This is, of course, based on the assumption that I > haven't entirely missed the point! :) I abused diskless_mount for md filesystems: [351]cicely5> cat /etc/rc.md DEV=`mdconfig -a -t swap -s 1400M` disklabel -r -w ${DEV} auto newfs /dev/${DEV}c tunefs -n enable /dev/${DEV}c mount /dev/${DEV}c /tmp chmod 1777 /tmp DEV=`mdconfig -a -t swap -s 800M` disklabel -r -w ${DEV} auto newfs /dev/${DEV}c tunefs -n enable /dev/${DEV}c mount /dev/${DEV}c /var/run chmod 755 /var/run [352]cicely5> grep rc.md /etc/rc.conf diskless_mount="/etc/rc.md" It's running fine on i386. md currently doesn't work on alpha because of 8k pagesize brokenness. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 14:14:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA95837B400 for ; Sat, 6 Jul 2002 14:14:26 -0700 (PDT) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 367B943E3B for ; Sat, 6 Jul 2002 14:14:26 -0700 (PDT) (envelope-from cbh@teabag.demon.co.uk) Received: from teabag.demon.co.uk ([193.237.4.110] helo=teabag.cbhnet) by anchor-post-31.mail.demon.net with esmtp (Exim 3.35 #1) id 17Qwsr-0004JL-0V; Sat, 06 Jul 2002 22:14:25 +0100 Received: from localhost (localhost [127.0.0.1]) by teabag.cbhnet (Postfix) with ESMTP id E92C665075; Sat, 6 Jul 2002 22:14:22 +0100 (BST) Date: Sat, 6 Jul 2002 22:14:22 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teabag.cbhnet To: ticso@cicely.de Cc: current@FreeBSD.ORG Subject: Re: Possible solution to /tmp on md filesystem In-Reply-To: <20020706205552.GD23704@cicely5.cicely.de> Message-ID: <20020706221005.B684-100000@teabag.cbhnet> 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 Sat, 6 Jul 2002, Bernd Walter wrote: > I abused diskless_mount for md filesystems: Either solution's preferable to my first inelegant attempt at an rc.tmp involving making a complete pigs' ear of rc! :) > [351]cicely5> cat /etc/rc.md > DEV=`mdconfig -a -t swap -s 1400M` > disklabel -r -w ${DEV} auto > newfs /dev/${DEV}c > tunefs -n enable /dev/${DEV}c > mount /dev/${DEV}c /tmp > chmod 1777 /tmp ... snip ... > [352]cicely5> grep rc.md /etc/rc.conf > diskless_mount="/etc/rc.md" > > It's running fine on i386. > md currently doesn't work on alpha because of 8k pagesize brokenness. I used the same procedure, but with the size set to 1G (on i386) I kept getting some sort of overrun problem with newfs; I wasn't able to track down the cause to either newfs or disklabel, but creating a separate "a" partition seems to have done the trick in my case. Unfortunately I can't say for certain if that fixes the problem or merely avoids it. Cheers, Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 14:58:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E94C37B400 for ; Sat, 6 Jul 2002 14:58:37 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6282C43E31 for ; Sat, 6 Jul 2002 14:58:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0570.cvx21-bradley.dialup.earthlink.net ([209.179.194.60] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17QxZZ-0004Nl-00; Sat, 06 Jul 2002 17:58:33 -0400 Message-ID: <3D2767DF.AAA9BDE4@mindspring.com> Date: Sat, 06 Jul 2002 14:57: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: Sheldon Hearn Cc: Paul Richards , current@freebsd.org Subject: Re: Removing perl in make world References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <3D258F80.BD86F9D0@mindspring.com> <20020705152402.GD775@starjuice.net> <20020706144243.GC41933@starjuice.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 Sheldon Hearn wrote: > On (2002/07/05 17:24), Sheldon Hearn wrote: > > You and Paul are both pretty "out there" if you think -current users > > will graciously accept a new world order in which ports linked > > dymanically against system libraries won't work between a system upgrade > > and the next port reinstall. > > Sorry about the "heat" of my post. I was stressed out and shouldn't > even have been reading my FreeBSD mail to start with. > > I liked Mark Murray's response to Paul's suggestion much better than my > own. Heat is a measure of how strongly opinions are held. If no one had any strong opinions on something like *this*, then the project would be in *real* trouble. 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 Jul 6 15: 0:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFAD637B400 for ; Sat, 6 Jul 2002 15:00:17 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4424343E31 for ; Sat, 6 Jul 2002 15:00:17 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020706220016.QFBC8262.rwcrmhc52.attbi.com@InterJet.elischer.org>; Sat, 6 Jul 2002 22:00:16 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA20075; Sat, 6 Jul 2002 14:49:58 -0700 (PDT) Date: Sat, 6 Jul 2002 14:49:55 -0700 (PDT) From: Julian Elischer To: Andrew Gallatin Cc: David Wolfskill , current@freebsd.org Subject: Re: Incomplete shutdown for -CURRENT built today In-Reply-To: <15655.20076.568156.307089@grasshopper.cs.duke.edu> 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 looks to me like the idle thread is running.. what does 'ps' show from ddb and "show locks" On Sat, 6 Jul 2002, Andrew Gallatin wrote: > > David Wolfskill writes: > > syncing disks... > > done > > > > And at that point, nothing further. I'm able to ping the machine, but I > > didn't see the (usual) mention of an attempt to shut power off via ACPI. > > (Sometimes that would work; sometimes it would time out, but this is the > > first time I recall not seeing the attempt logged.) > > > > I just tried sending a BREAK (to the serial console) [I think I have > > BREAK_TO_DEBUGGER in the kernel...]; no response. > > Me too! But a break to debugger seemed to work for me: > > Waiting (max 60 seconds) for system process `syncer' to stop...stopped > > syncing disks... 6 6 > done > > > > > [halt sent] > Stopped at siointr1+0x198: br zero,siointr1+0x330 > > db> tr > siointr1() at siointr1+0x198 > siointr() at siointr+0x40 > isa_handle_fast_intr() at isa_handle_fast_intr+0x24 > alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 > interrupt() at interrupt+0x110 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > kserunnable() at kserunnable+0x10 > idle_proc() at idle_proc+0x78 > fork_exit() at fork_exit+0xe0 > exception_return() at exception_return > --- root of call graph --- > db> reboot > > > (this is a UP alpha). > > > I'm glad this happened on x86 too! I was beginning to think boot was > only broken on alpha ;) > > Drew > > 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 Jul 6 15:50:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C31637B400 for ; Sat, 6 Jul 2002 15:50:20 -0700 (PDT) Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE81F43E3B for ; Sat, 6 Jul 2002 15:50:18 -0700 (PDT) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (h192n2fls35o811.telia.com [217.211.119.192]) by mailc.telia.com (8.11.6/8.11.6) with ESMTP id g66MoHa13300 for ; Sun, 7 Jul 2002 00:50:17 +0200 (CEST) Received: from hatchet ([192.168.0.17]) by phoenix.granlund.nu (8.10.1/8.10.1) with ESMTP id g66MoEG46267 for ; Sun, 7 Jul 2002 00:50:14 +0200 (CEST) Date: Sun, 7 Jul 2002 00:44:39 +0200 (W. Europe Daylight Time) From: Johan Granlund To: Subject: APIC on UP motherboard, Kernel trap Message-ID: X-X-Sender: johan@phoenix.granlund.nu 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 Hi, I have a ASUS A7V333 motherboard. Thats a UP motherboard vith a VIA KT333 chipset and a AMD XP Processor. There is a setting in BIOS where you can select "Interrupt Mode" between APIC an PIC, default APIC. What happends if i set options APIC_IO in the kernel config on a UP system with APIC set in BIOS? The rest is APIC/ACPI/KSE related if anyone is interested. I upgraded today (as of 30 min ago) to a current kernel from pre-KSE. When trying to boot with APIC set in BIOS i get: acpi0: on motherboard Fatal trap 12: page fault while in kernel mode fault virtual address = 0x16 fault code = supervisor read, page not present When setting PIC in Bios and doing a boot -v i get the following from ACPI: Jul 6 23:54:14 waraxe kernel: Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Jul 6 23:54:14 waraxe kernel: Features=0x383fbff Jul 6 23:54:14 waraxe kernel: AMD Features=0xffffffffc0400000 Jul 6 23:54:14 waraxe kernel: real memory = 536854528 (524272K bytes) Jul 6 23:54:14 waraxe kernel: avail memory = 515620864 (503536K bytes) Jul 6 23:54:14 waraxe kernel: pnpbios: Bad PnP BIOS data checksum Jul 6 23:54:14 waraxe kernel: Pentium Pro MTRR support enabled Jul 6 23:54:14 waraxe kernel: Using $PIR table, 11 entries at 0xc00f2050 Jul 6 23:54:14 waraxe kernel: ACPI-0222: *** Warning: Invalid table signature found: [T^_] Jul 6 23:54:14 waraxe kernel: ACPI-0193: *** Error: AcpiLoadTables: Error getting required tables (DSDT/FADT/FACS): AE_BAD_SIGNATURE Jul 6 23:54:14 waraxe kernel: ACPI-0215: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE Jul 6 23:54:14 waraxe kernel: ACPI: table load failed: AE_BAD_SIGNATURE Jul 6 23:54:14 waraxe kernel: npx0: on motherboard Jul 6 23:54:14 waraxe kernel: npx0: INT 16 interface In pre-KSE i could boot with APIC set in BIOS, but got hangs in shutdown after the "stopping vnlru"(?) message, _IF_ i had started X between boot and shutdown. If X was unused i got a clean shutdown. With PIC set ACPI wouldn't start but i had no problems with restarting. If anyone want's more information i will gladly help, but keep in mind that i'm not used to running the debugger and actually should't run Current :) /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 16:25: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1678637B400 for ; Sat, 6 Jul 2002 16:25:06 -0700 (PDT) Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1445943E31 for ; Sat, 6 Jul 2002 16:25:05 -0700 (PDT) (envelope-from imp@village.org) 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 g66NP3Y59544; Sat, 6 Jul 2002 17:25:03 -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 g66NP1G88315; Sat, 6 Jul 2002 17:25:02 -0600 (MDT) (envelope-from imp@village.org) Date: Sat, 06 Jul 2002 17:24:08 -0600 (MDT) Message-Id: <20020706.172408.22142523.imp@village.org> To: paul@freebsd-services.com Cc: drosih@rpi.edu, tlambert2@mindspring.com, sheldonh@starjuice.net, current@FreeBSD.ORG Subject: Re: Removing perl in make world From: "M. Warner Losh" In-Reply-To: <1025955773.881.29.camel@lobster.originative.co.uk> References: <1025921146.881.16.camel@lobster.originative.co.uk> <1025955773.881.29.camel@lobster.originative.co.uk> 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: <1025955773.881.29.camel@lobster.originative.co.uk> Paul Richards writes: : A 'sysclean' target would be the same in my mind. If you're "within : spec" of what -current supports then running that target shouldn't hose : you. If you're outside spec then you need to take your own precautions. NetBSD has in its distribution sets things that look like: obsolete.mi obsolete.${ARCH} and its distribution tools remove the old cruft on installation of the newer distribution set. Something like the following would then put things right: sysclean: @ head -2 ${SRCDIR}/release/obsolete.mi | xargs rm @ head -2 ${SRCDIR}/release/obsolete.${MACHINE_ARCH} | xargs rm would be the FreeBSD way of saying something similar. However, the obsolete.mi file would get large with time :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 16:35:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C7A037B401 for ; Sat, 6 Jul 2002 16:35:20 -0700 (PDT) Received: from gehicks.dyndns.org (adsl-20-178-72.asm.bellsouth.net [66.20.178.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4947443E3B for ; Sat, 6 Jul 2002 16:35:19 -0700 (PDT) (envelope-from gehicks@gehicks.dyndns.org) Received: from mac (mac [10.0.0.13]) by gehicks.dyndns.org (8.12.5/8.12.5) with ESMTP id g66NgNM8001319; Sat, 6 Jul 2002 23:42:23 GMT (envelope-from gehicks@gehicks.dyndns.org) Date: Sat, 6 Jul 2002 19:34:57 -0400 Subject: Re: Incomplete shutdown for -CURRENT built today Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) Cc: Andrew Gallatin , David Wolfskill , current@freebsd.org To: Julian Elischer From: W Gerald Hicks In-Reply-To: Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.482) 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 Try again with new vfs_subr.c, vfs_bio.c Latest updates seem to have fixed it for me. (Thanks Jeff) Cheers, Jerry Hicks gehicks@gehicks.dyndns.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 17: 0:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9614D37B400 for ; Sat, 6 Jul 2002 17:00:12 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4470043E09 for ; Sat, 6 Jul 2002 17:00:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020707000011.SHTH8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Sun, 7 Jul 2002 00:00:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA20531 for ; Sat, 6 Jul 2002 16:57:10 -0700 (PDT) Date: Sat, 6 Jul 2002 16:57:08 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: KSE M-III status & junior hacker project. 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 Well with various hints from here and there I have fixed the ^Z/fg problem (at least it seems fixed to me and others that have tested) This basically leaves only one outstanding problem that I know of which is a problem that Warner has with a particular progam. (This may also be fixed but I don't know) If anyone knows of something that was broken by the KSE commit, (i.e. it worked just before and not after) and is STILL broken please let me know because I think I can pretty much declare that chapter finished, and I'd like to get on with "extending" KSE functionality. This will be the start of Milestone IV, which would be add support for threads to run on multiple processors. Coincident with that some work should also proceed on gradually identifying and cleaning up places in the kernel where multithreading is just not ready.. e.g. which thread status do you get when you type ^T? -------------- On that topic I'd like to suggest a "junior hacker project" for a couple of hackers that would like to sink their teeth into something but are feeling intimidated. The project would be design some options as to what 'ps' and 'top' should show for multithreaded processes, and then work up a set of patches that would allow them to do it.. This would include extending the kernel interface used by ps to handle multiple threads, using hte current interface as a guide, and altering the programs themselves. Anyone interested in this should contect me.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 17:24:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A69CD37B401 for ; Sat, 6 Jul 2002 17:24:50 -0700 (PDT) Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id B415343E54 for ; Sat, 6 Jul 2002 17:24:49 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g670OkN2110126; Sat, 6 Jul 2002 20:24:46 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <1025955773.881.29.camel@lobster.originative.co.uk> References: <1025862341.1573.40.camel@lobster.originative.co.uk> <20020705095258.GC775@starjuice.net> <1025864161.1573.45.camel@lobster.originative.co.uk> <3D261EA4.ABC3AEC@mindspring.com> <1025921146.881.16.camel@lobster.originative.co.uk> <1025955773.881.29.camel@lobster.originative.co.uk> Date: Sat, 6 Jul 2002 20:24:45 -0400 To: Paul Richards From: Garance A Drosihn Subject: Re: Removing perl in make world Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) 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 12:42 PM +0100 7/6/02, Paul Richards wrote: >On Sat, 2002-07-06 at 03:46, Garance A Drosihn wrote: >> At 3:05 AM +0100 7/6/02, Paul Richards wrote: >> >Let's start with a premise: No-one running current is using >> >it for anything other than developing FreeBSD. >> >> This is assumption is too limiting. > >It shouldn't be. You're trying to defend a position that >the project doesn't support. It is too limiting. I might be on current because I have my *own* work I am doing on current. You talk as if the only development on -current is things that "other developers have officially committed" to -current. The fact that I have not committed some work to -current does not give anyone the right to go hog-wild with an 'rm' hanging off a blind 'find' command. It still boils down that you do not know why the files are there. I don't see why you're so determined to cause even more hassle for people trying to "do the right thing" and develop their changes on -current. >The -current branch is for FreeBSD developers, or volunteers >brave enough to test the -current branch. > >As such, don't be surprised if it wipes your hard disk clean. Don't be surprised if you have even fewer -current testers. Don't be surprised if we get to Novemeber of this year, and -current is just as unstable and untested as it was last year. Don't be surprised if we never manage to release -current, because it will never be sufficiently tested. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 17:43:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E67D37B401; Sat, 6 Jul 2002 17:43:39 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69DA343E58; Sat, 6 Jul 2002 17:43:38 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.3/8.12.3) with ESMTP id g670jC0M021663; Sat, 6 Jul 2002 17:45:16 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207070045.g670jC0M021663@gw.catspoiler.org> Date: Sat, 6 Jul 2002 17:44:18 -0700 (PDT) From: Don Lewis Subject: Re: dump(8) is hosed To: Georg.Koltermann@mscsoftware.com Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <1025887736.773.116.camel@hunter.muc.macsch.com> 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 5 Jul, Georg-W. Koltermann wrote: > Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien: >> On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in, >> pre-KSE3), dump will not complete dumping more than 5GB. At that point >> it stops responding properly to ^T, which should give "DUMP: 47.52% done, >> finished in 1:19". At the 5GB mark, ^T gives: >> >> load: 0.00 cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k >> >> and never changes. The user and system times never advance. Anybody >> have any ideas? > > For me it is broken in a different way. For a small FS like / it works, > but dumping my /home, which is 4G, I get > > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1 > > and on and on. > > Maybe a 32 bit <--> 64 bit mismatch caused by UFS2? My -current is of > date=2002.06.27.22.00.00. I'm not able to reproduce this here on a freshly built 11 GB filesystem. It only contains about 2 GB of data, but the data is fairly uniformly spread over all the cylinder groups. I'm running a version of -current built Fri Jul 5 13:07:05 PDT 2002, though I don't recall seeing any likely looking commits since the first report of this problem. I also looked at the source and didn't see anything suspicious, though I did find some print format mismatches. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 18:48:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BDC637B400 for ; Sat, 6 Jul 2002 18:48:34 -0700 (PDT) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FCCC43E42 for ; Sat, 6 Jul 2002 18:48:33 -0700 (PDT) (envelope-from rodrigc@attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.11.0/8.11.0) id g671ms009432 for current@freebsd.org; Sat, 6 Jul 2002 21:48:54 -0400 Date: Sat, 6 Jul 2002 21:48:54 -0400 From: Craig Rodrigues To: current@freebsd.org Subject: Does uplcom(4) support Bencole 08303? Message-ID: <20020706214854.A9138@attbi.com> 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, The uplcom(4) driver which supports USB-to-serial converters lists support for the following devices which use the Prolific PL-2303 chipset. Man page for uplcom driver: http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man4/uplcom.4 Supported cables: ATEN UC-232A http://www.aten.com.tw/USB/USB_1/UC_232A.html BAFO BF-800 http://bafo.com/proddetail.cfm?ID=394 BAFO BF-810 http://bafo.com/proddetail.cfm?ID=395 ELECOM UC-SGT http://www.iogear.com/products/product.php?Item=GUC232A IOGEAR UC-232A http://www.iogear.com/products/product.php?Item=GUC232A I/O DATA USB-RSAQ http://www.iodata.co.jp/products/usb/usbrsaq.htm I/O DATA USB-RSAQ2 http://www.iodata.co.jp/products/network/usbrsaq2.htm PLANEX USB-RS232 URS-03 http://www.planex.net/product/usb/urs-03.htm My local computer shop has the following cable which looks similar: Bencole 08303: http://www.bencole.com/singleproduct.asp?search=usb&partnum=08303 Would the Bencole 08303 cable be supported by the uplcom(4) driver? I can't tell on the manufacturer's web site, nor on the packaging for the cable itself if it is based on the Prolific PL-2303 chipset or not. Thanks. -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 21:56:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7FFB37B400; Sat, 6 Jul 2002 21:56:50 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF3A143E31; Sat, 6 Jul 2002 21:56:49 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.3/8.12.3) with ESMTP id g674wI0M021931; Sat, 6 Jul 2002 21:58:23 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207070458.g674wI0M021931@gw.catspoiler.org> Date: Sat, 6 Jul 2002 21:57:24 -0700 (PDT) From: Don Lewis Subject: Re: dump(8) is hosed To: Georg.Koltermann@mscsoftware.com Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG, mckusick@FreeBSD.ORG In-Reply-To: <1025887736.773.116.camel@hunter.muc.macsch.com> 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 5 Jul, Georg-W. Koltermann wrote: > Am Mi, 2002-07-03 um 17.31 schrieb David O'Brien: >> On a 27-June-2002 23:02:00 UTC system (just before ipfw2 went in, >> pre-KSE3), dump will not complete dumping more than 5GB. At that point >> it stops responding properly to ^T, which should give "DUMP: 47.52% done, >> finished in 1:19". At the 5GB mark, ^T gives: >> >> load: 0.00 cmd: dump 3981 [physstr] 2.11u 43.06s 0% 1536k >> >> and never changes. The user and system times never advance. Anybody >> have any ideas? > > For me it is broken in a different way. For a small FS like / it works, > but dumping my /home, which is 4G, I get > > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739789]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739788]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739787]: count=-1 > DUMP: read error from /dev/ad0s5e: Invalid argument: [sector -1054739786]: count=-1 > > and on and on. > > Maybe a 32 bit <--> 64 bit mismatch caused by UFS2? My -current is of > date=2002.06.27.22.00.00. I was finally finally able to reproduce this by creating a large file before doing the dump. Dump(8) is *very* hosed. The UFS2 import broke it's ability to follow multiple levels of indirect blocks. Here's a patch that fixed the problem along with a bunch of print format mismatches: Index: tape.c =================================================================== RCS file: /home/ncvs/src/sbin/dump/tape.c,v retrieving revision 1.20 diff -u -r1.20 tape.c --- tape.c 21 Jun 2002 06:17:57 -0000 1.20 +++ tape.c 7 Jul 2002 03:56:31 -0000 @@ -204,7 +204,7 @@ quit("Cannot recover\n"); /* NOTREACHED */ } - msg("write error %d blocks into volume %d\n", blocksthisvol, tapeno); + msg("write error %ld blocks into volume %d\n", blocksthisvol, tapeno); broadcast("DUMP WRITE ERROR!\n"); if (!query("Do you want to restart?")) dumpabort(0); Index: traverse.c =================================================================== RCS file: /home/ncvs/src/sbin/dump/traverse.c,v retrieving revision 1.19 diff -u -r1.19 traverse.c --- traverse.c 21 Jun 2002 06:17:57 -0000 1.19 +++ traverse.c 7 Jul 2002 04:24:14 -0000 @@ -275,9 +275,9 @@ { int ret = 0; int i; - static caddr_t idblk; + caddr_t idblk; - if (idblk == NULL && (idblk = malloc(sblock->fs_bsize)) == NULL) + if ((idblk = malloc(sblock->fs_bsize)) == NULL) quit("dirindir: cannot allocate indirect memory.\n"); bread(fsbtodb(sblock, blkno), idblk, (int)sblock->fs_bsize); if (ind_level <= 0) { @@ -294,6 +294,7 @@ else *filesize -= sblock->fs_bsize; } + free(idblk); return (ret); } ind_level--; @@ -306,6 +307,7 @@ ret |= dirindir(ino, blkno, ind_level, filesize, tapesize, nodump); } + free(idblk); return (ret); } @@ -501,9 +503,9 @@ dmpindir(ino_t ino, ufs2_daddr_t blk, int ind_level, off_t *size) { int i, cnt; - static caddr_t idblk; + caddr_t idblk; - if (idblk == NULL && (idblk = malloc(sblock->fs_bsize)) == NULL) + if ((idblk = malloc(sblock->fs_bsize)) == NULL) quit("dmpindir: cannot allocate indirect memory.\n"); if (blk != 0) bread(fsbtodb(sblock, blk), idblk, (int) sblock->fs_bsize); @@ -519,6 +521,7 @@ ufs1_blksout((ufs1_daddr_t *)idblk, cnt, ino); else ufs2_blksout((ufs2_daddr_t *)idblk, cnt, ino); + free(idblk); return; } ind_level--; @@ -529,9 +532,12 @@ else dmpindir(ino, ((ufs2_daddr_t *)idblk)[i], ind_level, size); - if (*size <= 0) + if (*size <= 0) { + free(idblk); return; + } } + free(idblk); } /* @@ -705,13 +711,13 @@ goto loop; } if (cnt == -1) - msg("read error from %s: %s: [block %d]: count=%d\n", + msg("read error from %s: %s: [block %qd]: count=%d\n", disk, strerror(errno), blkno, size); else - msg("short read error from %s: [block %d]: count=%d, got=%d\n", + msg("short read error from %s: [block %qd]: count=%d, got=%d\n", disk, blkno, size, cnt); if (++breaderrors > BREADEMAX) { - msg("More than %d block read errors from %d\n", + msg("More than %d block read errors from %s\n", BREADEMAX, disk); broadcast("DUMP IS AILING!\n"); msg("This is an unrecoverable error.\n"); @@ -730,11 +736,11 @@ ((off_t)blkno << dev_bshift))) == dev_bsize) continue; if (cnt == -1) { - msg("read error from %s: %s: [sector %d]: count=%d\n", + msg("read error from %s: %s: [sector %qd]: count=%d\n", disk, strerror(errno), blkno, dev_bsize); continue; } - msg("short read error from %s: [sector %d]: count=%d, got=%d\n", + msg("short read error from %s: [sector %qd]: count=%d, got=%d\n", disk, blkno, dev_bsize, cnt); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 22:35:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D15ED37B400 for ; Sat, 6 Jul 2002 22:35:31 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E64743E31 for ; Sat, 6 Jul 2002 22:35:31 -0700 (PDT) (envelope-from jeff@freebsd.org) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g675ZUM08141 for ; Sun, 7 Jul 2002 01:35:30 -0400 (EDT) (envelope-from jeff@freebsd.org) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Sun, 7 Jul 2002 01:35:30 -0400 (EDT) From: Jeff Roberson X-X-Sender: jroberson@mail.chesapeake.net Reply-To: Jeff Roberson To: current@freebsd.org Subject: UMA statistics feedback. Message-ID: <20020707013243.U25604-100000@mail.chesapeake.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 To those of you who provided me with UMA statistics; Thank you! The information was enlightening. The current bucket sizes aren't as bad as I had originally anticipated. I think I need to rework the mechanism by which the statistics are collected to get more interesting results, but for now what we have does nicely. Thanks, Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 23:47: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBF8437B400; Sat, 6 Jul 2002 23:46:57 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0594D43E31; Sat, 6 Jul 2002 23:46:57 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g676ku618100; Sun, 7 Jul 2002 02:46:56 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Sun, 7 Jul 2002 02:46:56 -0400 (EDT) From: Jeff Roberson To: current@freebsd.org Cc: cvs-committers@freebsd.org, Subject: Re: cvs commit: src/sys/tools vnode_if.awk In-Reply-To: <200207070639.g676db48049957@freefall.freebsd.org> Message-ID: <20020707024045.J25604-100000@mail.chesapeake.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 Sat, 6 Jul 2002, Jeff Roberson wrote: > jeff 2002/07/06 23:39:37 PDT > > Modified files: > sys/tools vnode_if.awk > Log: > - Use 'options DEBUG_VFS_LOCKS' instead of the DEBUG_ALL_VFS_LOCKS > environment variable to enable the lock verifiction code. > > Revision Changes Path > 1.33 +7 -5 src/sys/tools/vnode_if.awk > This was previously disabled because our locking was so bad that we could not boot with this option enabled. I can now boot, compile a kernel, and reboot without catching any locking asserts. This means that we are safe at our current level of debugging, but we are certainly not out of the woods wrt VFS locking yet. If you have a crash test box I would appreciate it if you would enable this kernel option. If it catches any errors you will be droped into the debugger where you can get a backtrace (type: tr) and mail it to me && current@ to avoid dups. To disable the panic & print once you've hit a bug type the following in ddb: w vfs_badlock_print 0 w vfs_badlock_panic 0 And you will not see any more errors. Thanks! Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 6 23:59:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C634237B401 for ; Sat, 6 Jul 2002 23:59:50 -0700 (PDT) Received: from web20901.mail.yahoo.com (web20901.mail.yahoo.com [216.136.226.223]) by mx1.FreeBSD.org (Postfix) with SMTP id 8E4CE43E3B for ; Sat, 6 Jul 2002 23:59:50 -0700 (PDT) (envelope-from bsddiy@yahoo.com) Message-ID: <20020707065950.88612.qmail@web20901.mail.yahoo.com> Received: from [218.108.144.153] by web20901.mail.yahoo.com via HTTP; Sat, 06 Jul 2002 23:59:50 PDT Date: Sat, 6 Jul 2002 23:59:50 -0700 (PDT) From: David Xu Subject: Re: i386 trap code To: Jonathan Lemon Cc: David Schultz , Jonathan Lemon , current@FreeBSD.ORG In-Reply-To: <20020706110658.A36596@prism.flugsvamp.com> 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 Jonthan, I just use DOS program as an example, for any program, if it wants to go into VM86 mode, it is very easy, just calls i386_vm86() to initailize its VM86 pcb extension, setups some memory area, then call sigreturn() to turn into VM86 mode. I think global in_vm86call flags is a bug under SMP, it creates a race condition. suppose this scenario: CPU A is running a simple VM86 code program. CPU B is running vm86_intcall() by some kernel driver (vesa module ?) CPU B set in_vm86call = 1 CPU A gets a fault trap. CPU A runs trap(), and find that in_vm86call is set and handles the trap as it is running vm86_intcall(), but it is not true and make a mess. David Xu --- Jonathan Lemon wrote: > On Sat, Jul 06, 2002 at 05:15:26AM -0700, David Xu wrote: > > > > I don't know how DOS emulating program works, but if it let DOS > > program run in VM86 mode, the in_vm86call global flag can prevent > > one CPU to run VM86 BIOS call and another CPU run DOS VM86 code, > > because it can not distinct which CPU the kernel is calling BIOS > > and which CPU is running VM86 DOS code, under SMP this is a problem. > > for exapmle, vesa module running on first CPU is calling VM86 BIOS, > > and second CPU is running DOS program, the DOS program maybe simply > > executes a privilege instruction to trigger trap, and the CPU > > will see itself calling VM86 BIOS, but it shouldn't. > > The virtual vm86 mode that doscmd(1) uses is different than the > vm86 bios calls (or bios16, or bios32) which allows direct execution > of BIOS code. They do not have much in common. doscmd() does not > directly execute any of the BIOS code; it provides its own BIOS > emulator. > > The scenario you postulate above cannot exist. > -- > Jonathan __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message