From owner-freebsd-current Sun Jun 27 0:58:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5063414D8D for ; Sun, 27 Jun 1999 00:58:05 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 901EA82; Sun, 27 Jun 1999 15:57:55 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: mckusick@mckusick.com Subject: BUF_LOCK() related panic.. Date: Sun, 27 Jun 1999 15:57:55 +0800 From: Peter Wemm Message-Id: <19990627075755.901EA82@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG panic: lockmgr: locking against myself Debugger("panic") Stopped at Debugger+0x37: movl $0,in_Debugger db> trace Debugger(c024333b) at Debugger+0x37 panic(c0242560,c3337df8,c32f4ed8,c76bd2c0,14d) at panic+0x74 lockmgr(c3337e20,12,c029f320,c6c90a20) at lockmgr+0x20b cluster_wbuild(c76bd2c0,2000,2,5) at cluster_wbuild+0x22b cluster_write(c3337df8,a000,0) at cluster_write+0x121 ffs_write(c76deeb4,1000,1000,c0a64880,c6c90a20) at ffs_write+0x48a vn_write(c0a64880,c76deefc,c0a6a280,0,c76def80) at vn_write+0xe4 dofilewrite(c6c90a20,c0a64880,6,8066000,1000) at dofilewrite+0x88 write(c6c90a20,c76def80,280d5974,8066000,6) at write+0x33 syscall(2f,2f,2f,6,8066000) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x30 db> This is consistant between x86 and Alpha. All I have to do is change a password. SMP won't boot at all. It hangs here: lpt0: Interrupt-driven port ppi0: on ppbus 0 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) I pressed reset, even break-to-debugger didn't work.. To provoke it, do this once or twice: root:[3:21pm]/etc-104# passwd root Changing local password for root. New password: Retype new password: passwd: updating the database... Read from remote host beast: Operation timed out Connection to beast closed. I'll look into this more shortly... Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 1:15:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 86CA014C58 for ; Sun, 27 Jun 1999 01:15:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA10773; Sun, 27 Jun 1999 01:15:43 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 01:15:43 -0700 (PDT) From: Matthew Dillon Message-Id: <199906270815.BAA10773@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627075755.901EA82@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, yes, some of us were just discussing this in a small mailing list. Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to be the brunt of it for a change :-). Kirk doesn't have an SMP box so he didn't see the bug. I have tentitively tracked the problem down to the apparent inability of lockmgr() locks to function from interrupts, even when used in a non-blocking manner, due to the simplelock's it uses internally. The new buffer cache code Kirk committed switched from B_BUSY (manually implemented locks) to lockmgr() locks. I think what is going on is that mainline code is getting a simplelock and then an interrupt is coming along and also trying to get the same lock, but I can't be sure because my DDB backtraces are somewhat munged. I was hoping someone would come up with a quick hack to solve the problem, but baring that I do have a big nasty patch on my site http://www.backplane.com/FreeBSD4/ which replaces the use of lockmgr() locks in the buffer cache code with the new SMP qlock's I began working on yesterday - but I wasn't intending on submitting it for commit for a while -- even the SMP guys haven't seen it yet! This patch is currently only suitable for compiling a new i386 -CURRENT kernel, it will break buildworld and it will also break alpha builds. And it has not been well tested yet... it is running a whole lot of brand new untested code and I'm amazed that it works as well as it does :-) If you do not want to get that involved, you can turn off SMP on the system and it should boot ok. Also be sure to completely recompile your modules (/usr/src/sys/modules), and when cvs updating be sure to update /usr/src/contrib/sys as well as /usr/src/sys/ if you are using softupdates. The size of struct buf has changed radically. -Matt Matthew Dillon :I pressed reset, even break-to-debugger didn't work.. : :To provoke it, do this once or twice: : :root:[3:21pm]/etc-104# passwd root :Changing local password for root. :New password: :Retype new password: :passwd: updating the database... :Read from remote host beast: Operation timed out :Connection to beast closed. : :I'll look into this more shortly... : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 1:31:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 8C89F14C96 for ; Sun, 27 Jun 1999 01:31:32 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.116]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB6BF5; Sun, 27 Jun 1999 10:31:30 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id KAA22443; Sun, 27 Jun 1999 10:12:00 +0200 (CEST) (envelope-from asmodai) Date: Sun, 27 Jun 1999 10:11:59 +0200 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: current@FreeBSD.org, tech-kern@netbsd.org, tech@openbsd.org Subject: Re: General feeling on merging APIs... Message-ID: <19990627101159.C21719@daemon.ninth-circle.org> References: <199906270422.WAA08307@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199906270422.WAA08307@harmony.village.org>; from Warner Losh on Sat, Jun 26, 1999 at 10:22:29PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Warner Losh (imp@harmony.village.org) [990627 09:02]: > In message <199906251653.KAA01796@caspian.plutotech.com> "Justin T. Gibbs" writes: > : The hope is to provide a consistent interface across > : all *BSDs which is why I've addressed this to all of the *BSD projects. > > More generally, I'd like to identify areas where the kernel APIs of > the various projects have diverged and see what, if anything, can be > done about them. I'd also like to get commitment from the various > controlling bodies of the *BSD projects to a statement something along > the lines of: Nice to see interest about this, it means a lot to me that the three BSD's, all with their own fun in use, etc, are willing to work together on this goal. Also, what I am doing with the PDP (here he goes again) is that I am trying to determine which BSD got which function where and in what version. Would make an excellent reference for people wanting to get something running on all three BSD's. (btw, ignore any FreeBSD words in the PDP, I am currently making it *BSD.) > We support the identification of API differences between the > various BSDs. We generally support the idea of merging the > APIs, but reserve the right to veto anything too radical. Sounds like a nice stance, however (not saying you did Warner) it _is_ absolutely fundamental that we, as the three BSD's speaking, put back ego's where it's technical excellence that counts. Private agenda's never served someone. So I myself am counting on the maturity of the participants to discuss technical internals and not moving to ego-talk. Note, this isn't about merging all the three BSD's back together. It's merely about making the API not too diverse/different from each other. (together we stand, divided we fall - cliche, but true) To clue in the OpenBSD people who haven't been reading tech-kern of NetBSD, it started when I pointed out to Bill Sommerfeld that FreeBSD already had an asleep function, which he was about to implement. A good function, but substantially different from FreeBSD's asleep, that I didn't think it was a good idea to just let Bill continue without warning him at least, as well as Matthew Dillon (original writer of FreeBSD's asleep()). Can we say at least, that the core 4.4BSD functions have remained largely/ almost the same across the 3 BSD's? Can we point out at least a few areas in which we differ? Are there differences spotted at hand which can be resolved on short time? > I've been trying to put together some compatibility shims for > newconfig drivers in FreeBSD's new-bus world and have run accross a > number of minor differences that would be trivial to fix. That sounds like a good thing Warner. Any more to tell about this wrt NetBSD and OpenBSD? Looking forward to hear from the lot of you, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist *BSD: We are back and will not accept no... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 1:44:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 86EC614C96 for ; Sun, 27 Jun 1999 01:44:14 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 24D4D81; Sun, 27 Jun 1999 16:44:14 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 01:15:43 MST." <199906270815.BAA10773@apollo.backplane.com> Date: Sun, 27 Jun 1999 16:44:14 +0800 From: Peter Wemm Message-Id: <19990627084414.24D4D81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Ah, yes, some of us were just discussing this in a small mailing list. > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b e > the brunt of it for a change :-). Kirk doesn't have an SMP box so he > didn't see the bug. > > I have tentitively tracked the problem down to the apparent inability of > lockmgr() locks to function from interrupts, even when used in a > non-blocking manner, due to the simplelock's it uses internally. The > new buffer cache code Kirk committed switched from B_BUSY (manually > implemented locks) to lockmgr() locks. I think what is going on is > that mainline code is getting a simplelock and then an interrupt is > coming along and also trying to get the same lock, but I can't be sure > because my DDB backtraces are somewhat munged. It seems to me the main problem (so far) is the buftimelock.. simple_lock(&buftimelock); bp->b_lock.lk_wmesg = buf_wmesg; bp->b_lock.lk_prio = PRIBIO + 4; bp->b_lock.lk_timo = 0; return (lockmgr(&(bp)->b_lock, locktype, &buftimelock, curproc)); Inside lockmgr(): simple_lock(&lkp->lk_interlock); if (flags & LK_INTERLOCK) simple_unlock(interlkp); ^^^^^^^^ <--- &buftimelock; Note that there is no LK_INTERLOCK in any of the calls to lockmgr().. On UP, simplelocks are noops. On SMP, they are real and nothing is ever freeing buftimelock. But that doesn't fix the UP problem where cluster_wbuild() tries to recursively re-lock a buf that the current process already owns. I have a few ideas about that one though, I just don't understand the clustering well enough yet to fix it. Speaking of SMP and simple locks, I'd like to turn on the debugging simplelocks that keep a reference count and check before switching to make sure that a process doesn't sleep holding a lock. This is a pretty fundamental sanity check and would have found the LK_INTERLOCK problem above before it got committed. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 1:46: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 6448815033; Sun, 27 Jun 1999 01:46:02 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA17831; Sun, 27 Jun 1999 10:45:45 +0200 (MET DST) Date: Sun, 27 Jun 1999 10:45:42 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Vince Gonzalez Cc: FreeBSD CURRENT Mailing list , hardware@FreeBSD.ORG Subject: Re: USB project status In-Reply-To: <19990626171921.A336@moe.internal.nycrc.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/src/release/texts/HARDWARE.TXT or http://www.etla.net/~n_hibma/usb Nick On Sat, 26 Jun 1999, Vince Gonzalez wrote: > On Sat, Jun 26, 1999 at 04:11:28PM +0200, Nick Hibma wrote: > > > > Project status of the USB project: > > Is a list of currently supported devices available somewhere? > > -- > vince@nycrc.net > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 1:55: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DA54B14C96 for ; Sun, 27 Jun 1999 01:55:02 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA25097; Sun, 27 Jun 1999 10:54:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Matthew Dillon , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 16:44:14 +0800." <19990627084414.24D4D81@overcee.netplex.com.au> Date: Sun, 27 Jun 1999 10:54:02 +0200 Message-ID: <25095.930473642@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990627084414.24D4D81@overcee.netplex.com.au>, Peter Wemm writes: >Speaking of SMP and simple locks, I'd like to turn on the debugging >simplelocks that keep a reference count and check before switching to make >sure that a process doesn't sleep holding a lock. This is a pretty >fundamental sanity check and would have found the LK_INTERLOCK problem >above before it got committed. Absolutely, I also have seen some indications that checking spl levels (#ifdef DIAGNOSTIC) might be warranted. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 2:22:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 555F215088 for ; Sun, 27 Jun 1999 02:22:51 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BDE6181; Sun, 27 Jun 1999 17:22:50 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 01:15:43 MST." <199906270815.BAA10773@apollo.backplane.com> Date: Sun, 27 Jun 1999 17:22:50 +0800 From: Peter Wemm Message-Id: <19990627092250.BDE6181@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > Ah, yes, some of us were just discussing this in a small mailing list. > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b e > the brunt of it for a change :-). Kirk doesn't have an SMP box so he > didn't see the bug. > > I have tentitively tracked the problem down to the apparent inability of > lockmgr() locks to function from interrupts, even when used in a > non-blocking manner, due to the simplelock's it uses internally. The > new buffer cache code Kirk committed switched from B_BUSY (manually > implemented locks) to lockmgr() locks. I think what is going on is > that mainline code is getting a simplelock and then an interrupt is > coming along and also trying to get the same lock, but I can't be sure > because my DDB backtraces are somewhat munged. In this case, it was just a programming error.. The key to remember is that the simplelocks are used to protect the state of the complex lock, they are not the lock themselves. lockmgr() holds the interlock while gaining or removing references etc and then frees the simplelock so that it can sleep if required etc. The actual implementation of the simplelock routines is interrupt safe (and has to be). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 2:49: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 81B1B151B2 for ; Sun, 27 Jun 1999 02:48:57 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA24502; Sun, 27 Jun 1999 10:51:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 27 Jun 1999 10:51:29 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Matthew Dillon , current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-Reply-To: <19990627092250.BDE6181@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Peter Wemm wrote: > Matthew Dillon wrote: > > Ah, yes, some of us were just discussing this in a small mailing list. > > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b > e > > the brunt of it for a change :-). Kirk doesn't have an SMP box so he > > didn't see the bug. > > > > I have tentitively tracked the problem down to the apparent inability of > > lockmgr() locks to function from interrupts, even when used in a > > non-blocking manner, due to the simplelock's it uses internally. The > > new buffer cache code Kirk committed switched from B_BUSY (manually > > implemented locks) to lockmgr() locks. I think what is going on is > > that mainline code is getting a simplelock and then an interrupt is > > coming along and also trying to get the same lock, but I can't be sure > > because my DDB backtraces are somewhat munged. > > In this case, it was just a programming error.. The key to remember is that > the simplelocks are used to protect the state of the complex lock, they are > not the lock themselves. lockmgr() holds the interlock while gaining or > removing references etc and then frees the simplelock so that it can sleep > if required etc. The actual implementation of the simplelock routines > is interrupt safe (and has to be). The simple_lock* macros don't seem to use the interrupt safe versions (ss_lock etc). What happens if an interrupt is recieved after gaining buftimelock and the interrupt routine also tries to call BUF_LOCK? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 3:18:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E417314C1D for ; Sun, 27 Jun 1999 03:18:44 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3A77B81; Sun, 27 Jun 1999 18:18:42 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Matthew Dillon , current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 10:51:29 +0100." Date: Sun, 27 Jun 1999 18:18:42 +0800 From: Peter Wemm Message-Id: <19990627101842.3A77B81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Sun, 27 Jun 1999, Peter Wemm wrote: > > > Matthew Dillon wrote: > > > Ah, yes, some of us were just discussing this in a small mailing list . > > > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets to b > > e > > > the brunt of it for a change :-). Kirk doesn't have an SMP box so he > > > didn't see the bug. > > > > > > I have tentitively tracked the problem down to the apparent inability of > > > lockmgr() locks to function from interrupts, even when used in a > > > non-blocking manner, due to the simplelock's it uses internally. The > > > new buffer cache code Kirk committed switched from B_BUSY (manually > > > implemented locks) to lockmgr() locks. I think what is going on is > > > that mainline code is getting a simplelock and then an interrupt is > > > coming along and also trying to get the same lock, but I can't be sur e > > > because my DDB backtraces are somewhat munged. > > > > In this case, it was just a programming error.. The key to remember is tha t > > the simplelocks are used to protect the state of the complex lock, they are > > not the lock themselves. lockmgr() holds the interlock while gaining or > > removing references etc and then frees the simplelock so that it can sleep > > if required etc. The actual implementation of the simplelock routines > > is interrupt safe (and has to be). > > The simple_lock* macros don't seem to use the interrupt safe versions > (ss_lock etc). What happens if an interrupt is recieved after gaining > buftimelock and the interrupt routine also tries to call BUF_LOCK? Good question, but I'm not sure ss_lock is what's needed either since that does a cli for the duration of the simplelock being held.. I think the BUF_*() inlines need internal splbio() protection since a biodone() can be called from the tail end of an interrupt, and that *does* try and get a simplelock during a BUF_UNLOCK()... (and BUF_REFCNT()). Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 3:33:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 5EBDB14CA3 for ; Sun, 27 Jun 1999 03:33:23 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA24593; Sun, 27 Jun 1999 11:35:44 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 27 Jun 1999 11:35:44 +0100 (BST) From: Doug Rabson To: Peter Wemm Cc: Matthew Dillon , current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-Reply-To: <19990627101842.3A77B81@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Peter Wemm wrote: > Doug Rabson wrote: > > On Sun, 27 Jun 1999, Peter Wemm wrote: > > > > > Matthew Dillon wrote: > > > > Ah, yes, some of us were just discussing this in a small mailing list > . > > > > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets > to b > > > e > > > > the brunt of it for a change :-). Kirk doesn't have an SMP box so he > > > > didn't see the bug. > > > > > > > > I have tentitively tracked the problem down to the apparent inability > of > > > > lockmgr() locks to function from interrupts, even when used in a > > > > non-blocking manner, due to the simplelock's it uses internally. The > > > > new buffer cache code Kirk committed switched from B_BUSY (manually > > > > implemented locks) to lockmgr() locks. I think what is going on is > > > > that mainline code is getting a simplelock and then an interrupt is > > > > coming along and also trying to get the same lock, but I can't be sur > e > > > > because my DDB backtraces are somewhat munged. > > > > > > In this case, it was just a programming error.. The key to remember is tha > t > > > the simplelocks are used to protect the state of the complex lock, they are > > > not the lock themselves. lockmgr() holds the interlock while gaining or > > > removing references etc and then frees the simplelock so that it can sleep > > > if required etc. The actual implementation of the simplelock routines > > > is interrupt safe (and has to be). > > > > The simple_lock* macros don't seem to use the interrupt safe versions > > (ss_lock etc). What happens if an interrupt is recieved after gaining > > buftimelock and the interrupt routine also tries to call BUF_LOCK? > > Good question, but I'm not sure ss_lock is what's needed either since that > does a cli for the duration of the simplelock being held.. > > I think the BUF_*() inlines need internal splbio() protection since > a biodone() can be called from the tail end of an interrupt, and that *does* > try and get a simplelock during a BUF_UNLOCK()... (and BUF_REFCNT()). In the long term, we probably need an spl-aware simplelock or maybe the cunning no-cost interrupt thread scheme which BSDi are using. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 3:37:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8D70614CA3 for ; Sun, 27 Jun 1999 03:36:52 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CEB4B81; Sun, 27 Jun 1999 18:36:49 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson Cc: Matthew Dillon , current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 11:35:44 +0100." Date: Sun, 27 Jun 1999 18:36:49 +0800 From: Peter Wemm Message-Id: <19990627103649.CEB4B81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Sun, 27 Jun 1999, Peter Wemm wrote: > > > Doug Rabson wrote: > > > On Sun, 27 Jun 1999, Peter Wemm wrote: > > > > > > > Matthew Dillon wrote: > > > > > Ah, yes, some of us were just discussing this in a small mailing list > > . > > > > > Hopefully Kirk will pick up on it soon. Ah well.. someone else g ets > > to b > > > > e > > > > > the brunt of it for a change :-). Kirk doesn't have an SMP box s o he > > > > > didn't see the bug. > > > > > > > > > > I have tentitively tracked the problem down to the apparent inabi lity > > of > > > > > lockmgr() locks to function from interrupts, even when used in a > > > > > non-blocking manner, due to the simplelock's it uses internally. The > > > > > new buffer cache code Kirk committed switched from B_BUSY (manual ly > > > > > implemented locks) to lockmgr() locks. I think what is going on is > > > > > that mainline code is getting a simplelock and then an interrupt is > > > > > coming along and also trying to get the same lock, but I can't be sur > > e > > > > > because my DDB backtraces are somewhat munged. > > > > > > > > In this case, it was just a programming error.. The key to remember is tha > > t > > > > the simplelocks are used to protect the state of the complex lock, they are > > > > not the lock themselves. lockmgr() holds the interlock while gaining o r > > > > removing references etc and then frees the simplelock so that it can sl eep > > > > if required etc. The actual implementation of the simplelock routines > > > > is interrupt safe (and has to be). > > > > > > The simple_lock* macros don't seem to use the interrupt safe versions > > > (ss_lock etc). What happens if an interrupt is recieved after gaining > > > buftimelock and the interrupt routine also tries to call BUF_LOCK? > > > > Good question, but I'm not sure ss_lock is what's needed either since that > > does a cli for the duration of the simplelock being held.. > > > > I think the BUF_*() inlines need internal splbio() protection since > > a biodone() can be called from the tail end of an interrupt, and that *does * > > try and get a simplelock during a BUF_UNLOCK()... (and BUF_REFCNT()). > > In the long term, we probably need an spl-aware simplelock or maybe the > cunning no-cost interrupt thread scheme which BSDi are using. Yes. I will also note that this approach is what John Dyson wanted to do for the G2 kernel. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 4:37:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id B42A614DA8; Sun, 27 Jun 1999 04:37:09 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.255]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB2F3F; Sun, 27 Jun 1999 13:37:08 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id NAA24034; Sun, 27 Jun 1999 13:17:34 +0200 (CEST) (envelope-from asmodai) Date: Sun, 27 Jun 1999 13:17:34 +0200 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: Allen Briggs , tech-kern@netbsd.org, Andy Doran , Eivind Eklund , current@freebsd.org, tech@openbsd.org Subject: Re: Suspend/resume hooks Message-ID: <19990627131734.A23920@daemon.ninth-circle.org> References: <19990626235842.F1063@canolog.ninthwonder.com> <199906270415.WAA08274@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199906270415.WAA08274@harmony.village.org>; from Warner Losh on Sat, Jun 26, 1999 at 10:15:19PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Warner Losh (imp@harmony.village.org) [990627 09:02]: [Excuse my posting this to multiple lists, but I cannot let this go unnoticed] > In message <19990626235842.F1063@canolog.ninthwonder.com> Allen Briggs writes: > : Ideally, there should be no more unnecessary divergence of the APIs--it > : would also be nice to work toward removing any API differences that there > : are now (no matter where they came from, what discussions have taken place, > : or what body parts have been scorched in the past). I know that's a lot > : easier said than done, but I'd be surprised if this isn't what most > : people would like to see. Allen, you are correct. I think that there's a lot to benefit any three of the BSD's from the other. > I know that I'm working on newconfig shims for FreeBSD's new-bus > system and am running into many stupid, trivial errors in doing > that... I'd like to see these areas minimized where it makes sense > and it technical and politically possible to do so. I couldn't agree more on that Warner. > If there is interest in cataloging these differences and trying to > resolve them, I hereby volunteer to setup mailing lists to facilitate > that process. Like I said, I was already busy doing that, albeit slowly, but getting there eventually... Also, a few BSD developers have already been dabbling in userland synchronisation and are still doing that, albeit, as I said before, slowly. > It would be nice if NetBSD's core and FreeBSD's core > would approve, in principle, a statement that says that they generally > support reduction in the differences in API between the two systems, > but resolution of said differences will be handled on a case by case > basis. And OpenBSD's core. > Basically, a "we like the idea in principle, but we'll reserve > the right to veto anything that is too radical." True, that's the best approach, but like I pointed out in another mail, we need to be careful not to bring out old things. Let the past just be the past and concentrate on the future in which this, the API cleanup/ synchronisation, will play an important role. > Since I'm not a member of either core group, I'm not sure what the > best way to proceed here would be. The only comparable `projects' I can name in this aspect Warner, is the Linux Standard Base, POSIX, and the Single Un*x Specification. http://www.linuxbase.org http://www.opengroup.org/austin > Comments? You got my support Warner, actually you took my ideas a little further, I was merely documenting the differences, and you want to get them straightened out as much as possible. I don't think any core-team can deny the importance of a somewhat consistent base API (on multiple areas) in order to keep porting from FreeBSD to NetBSD, or from OpenBSD to FreeBSD to a minimum fuzz. This could also allow us to try to create a driver system that would make exchanging device drivers a breeze. And that would benefit us all... -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist *BSD: We are back and will not accept no... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 4:37:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 8E89315158 for ; Sun, 27 Jun 1999 04:37:11 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.255]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2F3F; Sun, 27 Jun 1999 13:37:07 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id NAA24071; Sun, 27 Jun 1999 13:24:44 +0200 (CEST) (envelope-from asmodai) Date: Sun, 27 Jun 1999 13:24:44 +0200 From: Jeroen Ruigrok/Asmodai To: Peter Wemm Cc: Bruce Evans , mjacob@feral.com, current@FreeBSD.ORG, gibbs@plutotech.com, tech-kern@NetBSD.ORG Subject: Re: Changing the semantics of splsoftclock() Message-ID: <19990627132444.B23920@daemon.ninth-circle.org> References: <199906252228.IAA03303@godzilla.zeta.org.au> <19990627052642.3D12D75@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990627052642.3D12D75@overcee.netplex.com.au>; from Peter Wemm on Sun, Jun 27, 1999 at 01:26:42PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Peter Wemm (peter@netplex.com.au) [990627 09:02]: > Bruce Evans wrote: > > >>Why have splr semantics? That is, it raises to splsoftclock if current > > >>priority is lower, else doesn't fiddle with it. > > > > splsoftclock() has always had spllower() semantics, and its main users > > (kern_clock.c and kern_time.c) depend on this. > > > > FreeBSD has a precedent of not changing poor spl names because the change > > would be confusing: splnet() should be named splsoftnet() and splimp() > > should be named splnet() as in NetBSD. > > I would like to correct this, it is a source of problems when dealing with > NetBSD code. It would be a relatively harmless change for us since it's > failure mode is fairly benign. Old code calling splnet() that gets missed > will still work, just it will block more than is strictly required. > splimp() callers will get found quickly since they'll be an undefined > reference. I would say "go for it", but then again, I am merely a third rank BSD developer, not even a commiter on one BSD ;) However in the perspective of API cleanliness, it would be preffered from my point of view just for the consistency across the BSD's. > However, it would make backporting drivers from -current to 3.x a bit of a > problem.. Guess the STABLE-branch is off limits for these kind of changes without direct consent from core? Just my 0.02 euro's, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The *BSD Programmer's Documentation Project Network/Security Specialist *BSD: We are back and will not accept no... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 5:15:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id A2990150FA; Sun, 27 Jun 1999 05:15:14 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-149.skylink.it [194.185.55.149]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id OAA12709; Sun, 27 Jun 1999 14:14:33 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id OAA02791; Sun, 27 Jun 1999 14:15:06 +0200 (CEST) Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing list Cc: mckusick@FreeBSD.ORG Subject: lockmgr panics Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk, It seems that the recent changes made by Kirk McKusick to the locking mechanism in many files had some side effects. A kernel as of this afternoon kept giving the following panic when compiling a kernel, with the compile and source dir NFS mounted: lockmgr: pid , not exclusive lock holder -2 unlocking lockmgr(c1373b80,6,0,0) + 0x294 relpbuf(c1373b58, c029a384, 2000, c0786e00, c1373b58) + 0x7a swp_pager_async_iodone(c1373b58, 2000, c0786e00, c1373b58, c0786fc4) + 0x1ac biodone(c1373b58, c0786f58, 2000, 3, 1) + 0x4f wdintr(0, 8000000, 10, 10, 10) + 0x63f % mount /dev/wd0s2a on / (NFS exported, local, writes: sync 3 async 106) procfs on /proc (local) /dev/wd0s2e on /var (local, writes: sync 198 async 458) /dev/wd0s2f on /usr (NFS exported, local, writes: sync 455 async 831) 10.1.0.2:/usr/current/src on /usr/src The panic always happened when linking the kernel or objcopy-ing the result. From the DDB prompt 'call boot' failed. After undoing the changes with the commands given at the bottom of the page, it did not fail again. If needed I can try and produce a core file. If I can get the dumping to work that is. BTW and unrelated: In the commit message there was no mentioning of the reviewer for this patch. They probably would mind the credits I guess for the work they've done. Cheers, Nick -- e-Mail: hibma@skylink.it cd /usr/src cvs update -r1.69 sys/sys/buf.h cvs update -r1.13 sys/sys/lock.h cvs update -r1.25 sys/kern/kern_lock.c cvs update -r1.34 sys/kern/kern_physio.c cvs update -r1.52 sys/kern/kern_shutdown.c cvs update -r1.9 sys/kern/subr_dkbad.c cvs update -r1.51 sys/kern/vfs_aio.c cvs update -r1.215 sys/kern/vfs_bio.c cvs update -r1.83 sys/kern/vfs_cluster.c cvs update -r1.202 sys/kern/vfs_subr.c cvs update -r1.74 sys/miscfs/devfs/devfs_vnops.c cvs update -r1.88 sys/miscfs/specfs/spec_vnops.c cvs update -r1.85 sys/msdosfs/msdosfs_vnops.c cvs update -r1.73 sys/nfs/nfs_bio.c cvs update -r1.76 sys/nfs/nfs_subs.c cvs update -r1.131 sys/nfs/nfs_vnops.c cvs update -r1.31 contrib/sys/softupdates/ffs_softdep.c cvs update -r1.57 sys/ufs/ffs/ffs_vnops.c cvs update -r1.44 sys/ufs/mfs/mfs_vnops.c cvs update -r1.39 sys/ufs/ufs/ufs_disksubr.c cvs update -r1.118 sys/vm/swap_pager.c cvs update -r1.47 sys/vm/vm_pager.c cvs update -r1.71 sys/vm/vm_swap.c cvs update -r1.110 sys/vm/vnode_pager.c cvs update -r1.146 sys/isa/fd.c cvs update -r1.29 sys/dev/vinum/vinumio.c cvs update -r1.16 sys/dev/vinum/vinumrequest.c cvs update -r1.12 sys/dev/vinum/vinumrevive.c cvs update -r1.46 sys/gnu/ext2fs/ext2_vnops.c cvs update -r1.4 sys/gnu/ext2fs/fs.h cvs update -r1.17 sys/cam/cam_periph.c cvs update -r1.34 sys/i386/isa/diskslice_machdep.c cvs update -r1.8 sys/alpha/alpha/diskslice_machdep.c cvs update -r1.15 sys/pc98/pc98/atcompat_diskslice.c cvs update -r1.19 sys/pc98/pc98/diskslice_machdep.c cvs update -r1.63 sys/pc98/pc98/fd.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 8:50:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from ftp.dns.ne.jp (ftp.dns.ne.jp [210.155.3.5]) by hub.freebsd.org (Postfix) with ESMTP id C31B114F34; Sun, 27 Jun 1999 08:50:13 -0700 (PDT) (envelope-from tanimura@sakuramail.com) Received: from silver.carrots (yksk0422.ppp.infoweb.ne.jp [210.131.91.230]) by ftp.dns.ne.jp (8.9.2/8.8.5) with ESMTP id AAA21178; Mon, 28 Jun 1999 00:49:42 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by silver.carrots (8.9.3+3.2W/3.7W) with ESMTP id AAA04335; Mon, 28 Jun 1999 00:49:21 +0900 (JST) To: hibma@skylink.it Cc: current@FreeBSD.ORG, mckusick@FreeBSD.ORG, Peter Wemm Cc: Seigo Tanimura Subject: Re: lockmgr panics From: Seigo Tanimura In-Reply-To: Your message of "Sun, 27 Jun 1999 14:15:06 +0200 (CEST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990628004921U.tanimura@sakuramail.com> Date: Mon, 28 Jun 1999 00:49:21 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 32 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Nick Hibma Subject: lockmgr panics Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST) Message-ID: hibma> lockmgr: pid , not exclusive lock holder -2 unlocking Did you really get that message? if the unlocking process is pid -2(LK_KERNPROC), we can unlock, as in: [sys/kern/kern_lock.c:lockmgr()] > case LK_RELEASE: > if (lkp->lk_exclusivecount != 0) { > #if !defined(MAX_PERF) > if (lkp->lk_lockholder != pid && > lkp->lk_lockholder != LK_KERNPROC) /* FALSE */ > panic("lockmgr: pid %d, not %s %d unlocking", > pid, "exclusive lock holder", > lkp->lk_lockholder); Although the fixes by Peter seemed to have solved the problem, I saw lockmgr: pid -2, not exclusive lock holder 48 unlocking on savecore(8) after another panic reboot. I have to go to bed now... I will see what is going on tomorrow. Seigo TANIMURA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 9: 3:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 66D1314D4F; Sun, 27 Jun 1999 08:57:08 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9DBCB81; Sun, 27 Jun 1999 23:56:46 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Seigo Tanimura Cc: hibma@skylink.it, current@FreeBSD.ORG, mckusick@FreeBSD.ORG Subject: Re: lockmgr panics In-reply-to: Your message of "Mon, 28 Jun 1999 00:49:21 +0900." <19990628004921U.tanimura@sakuramail.com> Date: Sun, 27 Jun 1999 23:56:46 +0800 From: Peter Wemm Message-Id: <19990627155646.9DBCB81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > From: Nick Hibma > Subject: lockmgr panics > Date: Sun, 27 Jun 1999 14:15:06 +0200 (CEST) > Message-ID: > > hibma> lockmgr: pid , not exclusive lock holder -2 unlocking > > > Did you really get that message? if the unlocking process is > pid -2(LK_KERNPROC), we can unlock, as in: > > [sys/kern/kern_lock.c:lockmgr()] > > case LK_RELEASE: > > if (lkp->lk_exclusivecount != 0) { > > #if !defined(MAX_PERF) > > if (lkp->lk_lockholder != pid && > > lkp->lk_lockholder != LK_KERNPROC) /* FALSE */ > > panic("lockmgr: pid %d, not %s %d unlocking ", > > pid, "exclusive lock holder", > > lkp->lk_lockholder); > > Although the fixes by Peter seemed to have solved the problem, I saw > > lockmgr: pid -2, not exclusive lock holder 48 unlocking > > on savecore(8) after another panic reboot. I've had that too, also from savecore... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 10:32:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E51EC15051 for ; Sun, 27 Jun 1999 10:32:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA14208; Sun, 27 Jun 1999 10:32:21 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 10:32:21 -0700 (PDT) From: Matthew Dillon Message-Id: <199906271732.KAA14208@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627084414.24D4D81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It seems to me the main problem (so far) is the buftimelock.. : : simple_lock(&buftimelock); : bp->b_lock.lk_wmesg = buf_wmesg; : bp->b_lock.lk_prio = PRIBIO + 4; : bp->b_lock.lk_timo = 0; : return (lockmgr(&(bp)->b_lock, locktype, &buftimelock, curproc)); : :Inside lockmgr(): : : simple_lock(&lkp->lk_interlock); : if (flags & LK_INTERLOCK) : simple_unlock(interlkp); : ^^^^^^^^ <--- &buftimelock; : :Note that there is no LK_INTERLOCK in any of the calls to lockmgr().. On :UP, simplelocks are noops. On SMP, they are real and nothing is ever :freeing buftimelock. Ah ha! That is definitely one problem. It may be the interim fix I've been looking for. :But that doesn't fix the UP problem where cluster_wbuild() tries to :recursively re-lock a buf that the current process already owns. I have a :few ideas about that one though, I just don't understand the clustering :well enough yet to fix it. I haven't had any problems with cluster_wbuild(), are you sure? It looks ok to me. :Speaking of SMP and simple locks, I'd like to turn on the debugging :simplelocks that keep a reference count and check before switching to make :sure that a process doesn't sleep holding a lock. This is a pretty :fundamental sanity check and would have found the LK_INTERLOCK problem :above before it got committed. : :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au I think this would be a good idea. In general, I really dislike the complexity of both simplelocks and lockmgr locks. Simplelocks aren't as simple as they should be and really abuse SMP principles badly if they are indeed attempting to disable interrupts on a global scale! lockmgr() locks are so expensive that using them anywhere represents a serious performance concern. Their use in the buffer cache code is going to be strictly temporary because of that. Hopefully we will be able to remove them from the VFS code as well later this year. They are unbelievably expensive, cutting at least 15 MBytes/sec of cache-case I/O bandwidth. What we really need to do is get rid of all the I/O and interrupt-safety code that is being pushed into core infrastructure routines such as simplelocks and instead operate interrupts as kernel threads. Spinlocks need to be split into two kinds: One that actually spins, and one that does a thread switch in its core loop ( but does not actually try to sleep ). Thread-switching spinlocks would replace much of the current use for spinlocks while the true spinlocks would be used only in non-preemptive threads ( i.e. not used for anything that interacts with an interrupt ). It is then a simple matter to work on further separating resource access by interrupts to reduce the number of involuntary synchronous context switches out of an interrupt thread - a simple performance issue rather then a system-stopping issue. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 10:56: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 5DA2C14BD5; Sun, 27 Jun 1999 10:55:59 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-156.skylink.it [194.185.55.156]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id TAA17506; Sun, 27 Jun 1999 19:55:16 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id TAA03513; Sun, 27 Jun 1999 19:51:23 +0200 (CEST) Date: Sun, 27 Jun 1999 19:51:22 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing list , Seigo Tanimura , Peter Wemm , mckusick@FreeBSD.ORG Subject: Re: lockmgr panics (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Did you really get that message? if the unlocking process is > pid -2(LK_KERNPROC), we can unlock, as in: > lockmgr: pid -2, not exclusive lock holder 48 unlocking This looks like it, yes. Must have made a typo. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 11:10: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1631615068 for ; Sun, 27 Jun 1999 11:09:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA14643; Sun, 27 Jun 1999 11:09:56 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 11:09:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199906271809.LAA14643@apollo.backplane.com> To: Doug Rabson Cc: Peter Wemm , current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In the long term, we probably need an spl-aware simplelock or maybe the :cunning no-cost interrupt thread scheme which BSDi are using. : :-- :Doug Rabson Mail: dfr@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 I really like the idea of a cunning no-cost interrupt thread scheme, I didn't realize that BSDi had moved to it! Doing this would allow us to remove easily half the spl management code and would allow us to fix simplelocks - to implement them the way they ought to be implemented. -- On a related topic, I've done some syscall overhead measurements w/ SMP verses non-SMP systems that people may be interested in. The SMP/patched version includes a patch that Alan is going to commit soon ( a relatively simple removal of unnecessary locks surrounding an already-atomic assembly operation ). The cpu's are P-III/450's. no SMP Null syscall: 3532 nanoseconds SMP Null syscall: 6750 nanoseconds SMP/patched Null syscall: 6533 nanoseconds In comparison, I believe the Linux syscall overhead is on the order of 1 uS. Not that I am concerned about a few measily microseconds, but this does show that we have a ways to go in our SMP work. There is a lot of potential for improvement. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 11:29: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4D00E14D00 for ; Sun, 27 Jun 1999 11:28:54 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10yJfh-0008LF-00 for current@freebsd.org; Sun, 27 Jun 1999 20:28:53 +0200 From: Sheldon Hearn To: current@freebsd.org Subject: HEADS UP! Inetd wrapping OFF by default Date: Sun, 27 Jun 1999 20:28:53 +0200 Message-ID: <32068.930508133@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I've just committed a change to inetd that will effectively turn TCP Wrapping off for anyone who has an installed /etc/rc.conf that specifies an inetd_flags value, as well as anyone who makes world without running mergemaster to update /etc/defaults/rc.conf . This will not be a problem for most people. Inetd now takes command-line options to enable wrapping. This was a decision taken with the approval of our release engineer in an attempt to revert a backward-compatibility problem introduced in 3.2-RELEASE. The relevant changes to the manpage follow: " SYNOPSIS inetd [-d] [-l] [-w] [-c maximum] [-C rate] [-a address] [-p filename] [-R rate] [configuration file] [...] DESCRIPTION [...] -w Turn on TCP Wrapping. If this option is specified twice, internal services will also be wrapped. See the IMPLEMENTATION NOTES section for more information on TCP Wrappers support. [...] IMPLEMENTATION NOTES When given the -w option, inetd will wrap all services specified as ``stream tcp nowait'' except for ``internal'' services. If the -w option is given twice, such ``internal'' services will be wrapped as well. When wrapping is enabled, the tcpd daemon is not required, as that functionality is builtin. For more information on TCP Wrappers; see the relevant documentation ( hosts_access(5) ). " When this change is merged to STABLE, the release notes will be updated and a fat HEADS UP will be posted to the freebsd-stable mailing list. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 11:41:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B36CD1511E for ; Sun, 27 Jun 1999 11:41:07 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10yJr3-0008Uc-00; Sun, 27 Jun 1999 20:40:37 +0200 From: Sheldon Hearn To: mi@aldan.algebra.com Cc: Nick Hibma , current@FreeBSD.ORG Subject: Re: place of logfile for cron (PR 7682) - move it? In-reply-to: Your message of "Sat, 26 Jun 1999 11:57:17 -0400." <199906261557.LAA58145@misha.cisco.com> Date: Sun, 27 Jun 1999 20:40:37 +0200 Message-ID: <32649.930508837@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Jun 1999 11:57:17 -0400, Mikhail Teterin wrote: > I'd, probably, put a symlink from the old location to the new one... That's something you could do on your own machines, but I sincerely hope we _don't_ do that to installworld and future releases. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 11:43:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5F43614E9B for ; Sun, 27 Jun 1999 11:43:06 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10yJtP-0008WX-00; Sun, 27 Jun 1999 20:43:03 +0200 From: Sheldon Hearn To: FreeBSD mailing lists Cc: current@freebsd.org Subject: Re: Ports problems In-reply-to: Your message of "Sat, 26 Jun 1999 22:50:31 +0200." Date: Sun, 27 Jun 1999 20:43:03 +0200 Message-ID: <32768.930508983@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 26 Jun 1999 22:50:31 +0200, FreeBSD mailing lists wrote: > Hi, I just wondered if it was a problem with my installation or in > general, but is anyone else here having problems with ports being > dependant on glib12.2 and ports installing glib12.3 instead? Try mailing ports@freebsd.org . When you do, be sure to give a few examples of "a LARGE number of the ports". Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 11:59:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id 075F714C85 for ; Sun, 27 Jun 1999 11:59:28 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id LAA90801; Sun, 27 Jun 1999 11:59:25 -0700 (PDT) (envelope-from mph) Date: Sun, 27 Jun 1999 11:59:25 -0700 From: Matthew Hunt To: Alex Zepeda Cc: current Subject: Re: gdb no longer works? Message-ID: <19990627115924.A90565@wopr.caltech.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Alex Zepeda on Fri, Jun 25, 1999 at 11:35:04PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jun 25, 1999 at 11:35:04PM -0700, Alex Zepeda wrote: > I've tried numerous times (updating the kernel, buildworld, etc) to get > gdb to work, but so far it seems like ELF coredumps are broken (course > this could be a C++ issue too): It was fixed several weeks ago, at least in 4.0. -- Matthew Hunt * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 12:23:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id C76A214DAA for ; Sun, 27 Jun 1999 12:23:44 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA16417; Sun, 27 Jun 1999 12:23:31 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37767A35.6D9B1751@gorean.org> Date: Sun, 27 Jun 1999 12:23:33 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: Ben Rosengart , freebsd-current@freebsd.org Subject: /etc/defaults (Was: Re: Out of file descriptors ??) References: <199906262321.QAA00428@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > Someone else wrote: > > I am not fond of the new defaults/rc.conf system. Used to be when I > > wanted to modify something in rc.conf, I opened it up and changed the > > value. Now I have to extract a line from defaults/rc.conf, put it in > > rc.conf, and change it -- unless I don't understand the new setup > > correctly. That makes more work for me, not less. What's the idea > > here? > > Separation between the default initialisation values for parameters, > and the actual values of parameters that specifically apply to your > system. > > With only one file, you have no way of adding new (default) parameter > values without forcing the user to manually merge the two. So now instead of requiring user intervention (and implicitly, observation) to implement new knobs we just slide them in unnoticed. Also, there is now no way to know if the syntax for a certain command that you have safely tucked away in /etc/rc.conf.local has changed, unless you manually look at the diff. Yes, I know that's rare, but it DOES happen. > The minor extra amount of work in the short term is greatly offset in > the long term. Try merging your local changes from a 2.2.x rc.conf > with a new 3.x vintage rc.conf to see what I mean. What you're describing is a one time operation, and something that is going to require manual merging no matter what you do. The only difference is that now it requires merging of 3 files instead of 2. The only people benefitted by /etc/defaults are the developers who upgrade very often and are not willing to run mergemaster to upgrade their /etc. It does not benefit the normal user at all, and in fact it penalizes them, as has been expressed here often since the new system was established. But then again, we all know that freebsd is FOR the developers, so us users just have to grin and bear it... or just 'mv /etc/defaults/rc.conf /etc' :) 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 27 13: 3: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id C402714DAA for ; Sun, 27 Jun 1999 13:02:59 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm1-11.vpop1.avtel.net [207.71.237.61]) by beach.silcom.com (Postfix) with ESMTP id B6FF41559 for ; Sun, 27 Jun 1999 13:02:49 -0700 (PDT) Date: Sun, 27 Jun 1999 13:02:50 -0700 (PDT) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: freebsd-current@freebsd.org Subject: Re: /etc/defaults (Was: Re: Out of file descriptors ??) In-Reply-To: <37767A35.6D9B1751@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A nice semi-solution to this problem of having to copy lines from defaults/rc.conf would be a good curses-based rc.conf configuration tool. It could read in a definition file (or this information could be embedded into comments in defaults/rc.conf), present a list of configuration knobs and their current values, give a description of each knob's implications, and have some knowledge about the range of acceptable values (e.g. boolean, int, string, list that expands a template into new config options i.e. network_interfaces and ifconfig_???). Anyone up for the job? :-) I was working on something like this for X11 a while back, that even parsed out and re-wrote the old-style rc.conf with original comments and formatting intact, but that project is currently on hold until I have enough functionality in my new widgets library. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 13: 6:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8D4DA14DAA for ; Sun, 27 Jun 1999 13:06:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA15499; Sun, 27 Jun 1999 13:06:13 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 13:06:13 -0700 (PDT) From: Matthew Dillon Message-Id: <199906272006.NAA15499@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627084414.24D4D81@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :But that doesn't fix the UP problem where cluster_wbuild() tries to :recursively re-lock a buf that the current process already owns. I have a :few ideas about that one though, I just don't understand the clustering :well enough yet to fix it. Ok, I just hit this testing the lockmgr changes. I think the problem is that cluster_wbuild's algorithm was polluted a little by Kirk's commit. Previously it tested for B_BUSY to determine if it could then lock it to include in the cluster. Kirk changed this to actually attempt a lock, and then include it if the lock succeeded and not include it if the lock failed. The problem is that if the buffer was already locked by the same process, this change results in a panic instead of a simple failure to obtain the lock. The solution is to re-tool the code to use the original algorithm ( test the lock before trying to get it, rather then simply trying to get it ), but with the new locks. I do not have time today to do this but I believe I have given sufficient information for Peter, Kirk, or Alan to make the fix. I believe there are two or three areas in Kirk's patchset where he replaced an explicit test with an attempt to actually gain the lock where this sort of panic can occur. I think Kirk was trying to optimize the code :-) Heh heh. Just goes to show that combining functional replacements with optimizations all in one go does not always work. -Matt Matthew Dillon :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 15: 0:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id A84F014DD7 for ; Sun, 27 Jun 1999 15:00:26 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA17603; Sun, 27 Jun 1999 15:00:19 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37769EF5.F5C21AED@gorean.org> Date: Sun, 27 Jun 1999 15:00:21 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brian W. Buchanan" Cc: freebsd-current@freebsd.org Subject: Re: /etc/defaults (Was: Re: Out of file descriptors ??) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian W. Buchanan" wrote: > > A nice semi-solution to this problem of having to copy lines from > defaults/rc.conf would be a good curses-based rc.conf configuration tool. Yes, this would be an excellent idea. However to save you time, I'll expound the 3 different areas of argument that always cause this project to stall: 1. GUI platform curses tcl/tk web/cgi other 2. Data storage pattern flat file multiple flat files database sub arguments, what type of database data storage location 3. How to interface 1. and 2. with the installation/upgrade procedure Many arguments here, all depending on what choices people prefer for 1. and 2. You can find much detail about this in the archives, however each time the discussion comes up it spins and spins, but never lands, so we continue to do nothing. I released mergemaster in part to try and light a candle instead of continuing to curse the darkness, and in part to show that it's not impossible to update the rc's (in particular, although there are other important file update issues) within the current system. Then /etc/defaults came along, and, well... I think I've said enough about that already today. :) What this boils down to is, code talks. The possible designs have been discussed to death, it's time for someone to write something. Of course that'll get ripped apart too, but at least we'll have somewhere new to start from. 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 27 15:47:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id C36EC151D3 for ; Sun, 27 Jun 1999 15:47:14 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A61D781; Mon, 28 Jun 1999 06:47:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 13:06:13 MST." <199906272006.NAA15499@apollo.backplane.com> Date: Mon, 28 Jun 1999 06:47:13 +0800 From: Peter Wemm Message-Id: <19990627224713.A61D781@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > : > :But that doesn't fix the UP problem where cluster_wbuild() tries to > :recursively re-lock a buf that the current process already owns. I have a > :few ideas about that one though, I just don't understand the clustering > :well enough yet to fix it. > > Ok, I just hit this testing the lockmgr changes. > > I think the problem is that cluster_wbuild's algorithm was polluted > a little by Kirk's commit. > > Previously it tested for B_BUSY to determine if it could then lock it > to include in the cluster. Yep, I was aware of this before, but I didn't rip it out since I didn't know what Kirk's intentions were. I'm assuming he's got his experience with making the BSD/OS vfs reentrant in mind, so I don't want to break anything that gets closer to that. A seperate test and then lock would not be reentrant. (Sure, there are far bigger problems than this, but every bit helps when we get there) > Kirk changed this to actually attempt a lock, and then include it > if the lock succeeded and not include it if the lock failed. > > The problem is that if the buffer was already locked by the same process, > this change results in a panic instead of a simple failure to obtain the > lock. > The solution is to re-tool the code to use the original algorithm ( test > the lock before trying to get it, rather then simply trying to get it ), > but with the new locks. I do not have time today to do this but I believ e > I have given sufficient information for Peter, Kirk, or Alan to make the > fix. Actually, I think there is another set if missing BUF_KERNPROC() calls, cluster_callback() frees buffers, so all buffers submitted with it had better be reassigned. This is (I think) part of the problem that cluster_wbuild() is hitting - things were supposed to have been reassigned but are still hanging onto the current process. > I believe there are two or three areas in Kirk's patchset where he > replaced an explicit test with an attempt to actually gain the lock where > this sort of panic can occur. I think Kirk was trying to optimize the > code :-) Heh heh. Just goes to show that combining functional > replacements with optimizations all in one go does not always work. > > -Matt > Matthew Dillon > > > :Cheers, > :-Peter > :-- > :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 16:44:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 15C60151C5 for ; Sun, 27 Jun 1999 16:44:55 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id QAA18194; Sun, 27 Jun 1999 16:44:43 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3776B76A.40FED165@gorean.org> Date: Sun, 27 Jun 1999 16:44:42 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627075755.901EA82@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please forgive me if this is a naive question, but could this problem also relate to why starting netscape now panic's my system? I have a UP celeron 300a system and with the most recent -current I can boot fine, startx fine, but as soon as I try to start netscape the system locks and reboots. I can add DDB and do all that stuff if needed, however if it's possible that this problem is the cause I will simply wait for the fix. Thanks, 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 27 17:10:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CEC0C15212 for ; Sun, 27 Jun 1999 17:10:10 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A1F9481; Mon, 28 Jun 1999 07:49:06 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Cc: current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 16:44:42 MST." <3776B76A.40FED165@gorean.org> Date: Mon, 28 Jun 1999 07:49:06 +0800 From: Peter Wemm Message-Id: <19990627234906.A1F9481@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug wrote: > Please forgive me if this is a naive question, but could this problem a lso > relate to why starting netscape now panic's my system? I have a UP celeron > 300a system and with the most recent -current I can boot fine, startx fine, > but as soon as I try to start netscape the system locks and reboots. > > I can add DDB and do all that stuff if needed, however if it's possible > that this problem is the cause I will simply wait for the fix. I suspect you were running into a problem in swap_pager.c. If anything is going to make your system swap, netscape will be it. I *think* I fixed that particular problem in swap_pager about an hour or so ago. The cluster_wbuild() problem is still lurking though, best advice is to backtrack a bit. > Thanks, > > Doug Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 17:54:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 46BE214D21 for ; Sun, 27 Jun 1999 17:54:22 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA18424; Sun, 27 Jun 1999 17:54:10 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3776C7B1.AF90EF76@gorean.org> Date: Sun, 27 Jun 1999 17:54:09 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@freebsd.org, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627234906.A1F9481@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Doug wrote: > > Please forgive me if this is a naive question, but could this problem a > lso > > relate to why starting netscape now panic's my system? I have a UP celeron > > 300a system and with the most recent -current I can boot fine, startx fine, > > but as soon as I try to start netscape the system locks and reboots. > > > > I can add DDB and do all that stuff if needed, however if it's possible > > that this problem is the cause I will simply wait for the fix. > > I suspect you were running into a problem in swap_pager.c. If anything is > going to make your system swap, netscape will be it. I *think* I fixed > that particular problem in swap_pager about an hour or so ago. Ok, I tried updating and rebuilding the kernel after your commit, still no joy. To add excitment, when it locks up I can't break to the debugger, either automatically or by doing Ctrl-Alt-Escape. > The > cluster_wbuild() problem is still lurking though, best advice is to > backtrack a bit. *nod* I will just hang out in windows for a while and check my commit mail. If it doesn't get fixed by the time I am ready to go back to beating on my serial console project, I'll do just that. Thank you for the response, 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 27 18:11:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-69.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.69]) by hub.freebsd.org (Postfix) with ESMTP id EDE8414BEB for ; Sun, 27 Jun 1999 18:11:49 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from dev.lan.awfulhak.org (dev.lan.awfulhak.org [172.16.0.5]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id DAA11667; Sun, 27 Jun 1999 03:51:13 +0100 (BST) (envelope-from brian@lan.awfulhak.org) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by dev.lan.awfulhak.org (8.9.3/8.9.3) with ESMTP id DAA00419; Sun, 27 Jun 1999 03:45:11 +0100 (BST) (envelope-from brian@dev.lan.awfulhak.org) Message-Id: <199906270245.DAA00419@dev.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "George V. Neville-Neil" Cc: freebsd-current@FreeBSD.org Subject: Re: Who leads networking? In-reply-to: Your message of "Sat, 26 Jun 1999 08:34:01 PDT." <199906261534.IAA13137@punk.meer.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jun 1999 03:45:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hey Folks, > > I'm new to contributing to FreeBSD but not to working with kernels > etc. I'm thinking of adding a new framing type to PPP which is described in > the latest Transactions on Networking. Who do I talk to about this kind > of stuff? Me I guess - if you're thinking of adding it to user-ppp :-) > Thanks, > George -- 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 27 18:19:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from mom.hooked.net (mom.hooked.net [206.80.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CB831527E for ; Sun, 27 Jun 1999 18:19:12 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from fish.hooked.net (garbanzo@fish.hooked.net [206.80.6.48]) by mom.hooked.net (8.8.6/8.8.5) with SMTP id SAA25989; Sun, 27 Jun 1999 18:18:58 -0700 (PDT) Date: Sun, 27 Jun 1999 18:18:58 -0700 (PDT) From: Alex Zepeda To: Doug Cc: Peter Wemm , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-Reply-To: <3776C7B1.AF90EF76@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Doug wrote: > *nod* I will just hang out in windows for a while and check my commit > mail. If it doesn't get fixed by the time I am ready to go back to beating > on my serial console project, I'll do just that. Hah, well some of us aren't quite that lucky :) I managed to reproduce the "netscape crashes the box" thing a few times. And then, triggered a crash (probably the same one) at the command prompt by compiling a few things (got a trace from that one). Savecore didn't want to cooperate however, so I recompiled it, and decided to manually panic the box, which worked fine but the kernel panic'd at savecore (same lockmgr: pid xxx not exclusive... unlocking as I got on the cmd line). Oddly enough, the pid was -2 when savecore tickled it. - alex who wonders who might be crazy enough to port fbsd to mack86k.. You better believe that marijuana can cause castration. Just suppose your girlfriend gets the munchies! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 18:24:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id DE0BA14F84 for ; Sun, 27 Jun 1999 18:23:22 -0700 (PDT) (envelope-from camoody@pacbell.net) Received: from chris1 (ppp-209-232-192-15.chic01.pacbell.net [209.232.192.15]) by mta2.snfc21.pbi.net (8.9.3/8.9.3) with SMTP id SAA13974 for ; Sun, 27 Jun 1999 18:23:21 -0700 (PDT) Message-ID: <001b01bec103$d31b58c0$0fc0e8d1@chris1> From: "Chris Moody" To: "Current FreeBSD" Subject: Fw: libstdc++.so.2 Date: Sun, 27 Jun 1999 18:16:17 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: Chris Moody To: Questions FreeBSD Sent: Sunday, June 27, 1999 6:14 PM Subject: libstdc++.so.2 > Hello everyone, > > I spent several hours last night installing the Current version of FreeBSD > over the internet, for some reason, one of the files was unable to download > successfully. Currently I am unable to get into X Windows, when I try, the X > Windows screen comes up for a second, and then I'm back at a text prompt > telling me at least one time, that it can't find libstdc++so.2, now I was > wondering, can anyone tell me where I could get this file, so that I could > download it from Windows, and then copy it over into the directory FreeBSD > wants it to be in? > > Thank you, > > Chris Moody > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 18:38: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id AF0591524B for ; Sun, 27 Jun 1999 18:38:04 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA19230; Sun, 27 Jun 1999 18:37:52 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3776D1EF.D4D4021E@gorean.org> Date: Sun, 27 Jun 1999 18:37:51 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default References: <32068.930508133@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is going to sound like I'm attacking sheldon, but I'm not since he's already stated that the got approval for this change from Jordan. Sheldon Hearn wrote: > Inetd now takes command-line options to enable wrapping. This was a > decision taken with the approval of our release engineer in an attempt > to revert a backward-compatibility problem introduced in 3.2-RELEASE. > > The relevant changes to the manpage follow: > " > SYNOPSIS > inetd [-d] [-l] [-w] [-c maximum] [-C rate] [-a address] [-p filename] > [-R rate] [configuration file] > [...] > DESCRIPTION > [...] > -w Turn on TCP Wrapping. If this option is specified > twice, internal services will also be wrapped. See the > IMPLEMENTATION NOTES section for more information on TCP > Wrappers support. > > [...] > IMPLEMENTATION NOTES > > When given the -w option, inetd will wrap all services specified as > ``stream tcp nowait'' except for ``internal'' services. If the -w > option is given twice, such ``internal'' services will be wrapped > as well. > > When wrapping is enabled, the tcpd daemon is not required, as that > functionality is builtin. For more information on TCP Wrappers; > see the relevant documentation ( hosts_access(5) ). First, the setting in /etc/defaults/rc.conf should default to off, as defaulting it to on violates POLA for the many many people who haven't updated to 3.x from 2.2 yet. The fact that one release had it on by default IMO does not mean that POLA switches to having it on by default, since the majority of users have not yet upgraded, and the comments and questions on the lists have clearly indicated that having it on is causing more problems than it solves. Also, if the decision is made to leave it on by default, there should be a hosts.allow file installed by default that has nothing but "ALL : ALL" in it. Second, this command line switch is horrible UI design for several reasons. First, any command line option that requires that the same flag be applied twice is bad design, historical precedents aside. Second, what if I want to wrap my internal services, but not wrap my external ones? This design is still presupposing that everyone will want to wrap everything, instead of trying to give the maximum amount of flexibility (and the least amount of surprise) to the average user. I propose that the -w flag be changed to take parameters. To start with, you would have [-w <[e] [i]>] to control wrapping for external and internal services respectively. This would also allow the system to be extensible in the future to include other types or subtypes of services. I really hope that this design will be reconsidered before it gets sent to -stable. 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 27 19:19:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7B38614E30 for ; Sun, 27 Jun 1999 19:19:48 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA89942; Sun, 27 Jun 1999 22:18:53 -0400 (EDT) Date: Sun, 27 Jun 1999 22:18:53 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Peter Wemm Cc: Doug , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-Reply-To: <19990627234906.A1F9481@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Peter Wemm wrote: > Doug wrote: > > Please forgive me if this is a naive question, but could this problem a > lso > > relate to why starting netscape now panic's my system? I have a UP celeron > > 300a system and with the most recent -current I can boot fine, startx fine, > > but as soon as I try to start netscape the system locks and reboots. > > > > I can add DDB and do all that stuff if needed, however if it's possible > > that this problem is the cause I will simply wait for the fix. > > I suspect you were running into a problem in swap_pager.c. If anything is > going to make your system swap, netscape will be it. I *think* I fixed Hmm... you don't think doing grep -500s on a cdev (hdd, actually) will cause REALLY horrible swapping/disk-reading behavior? *grin* > that particular problem in swap_pager about an hour or so ago. The > cluster_wbuild() problem is still lurking though, best advice is to > backtrack a bit. > > > Thanks, > > > > Doug > > Cheers, > -Peter > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 19:27:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 8B0D7152AC for ; Sun, 27 Jun 1999 19:27:17 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA16061; Mon, 28 Jun 1999 11:57:05 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA42623; Mon, 28 Jun 1999 11:57:03 +0930 (CST) Date: Mon, 28 Jun 1999 11:57:02 +0930 From: Greg Lehey To: FreeBSD current users Cc: Kirk McKusick Subject: Lockmgr panic out of nfs_bwrite in latest -CURRENT Message-ID: <19990628115702.M15144@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting the following repeatable panic since the introduction of the changed lockmgr code: (kgdb) bt #0 Debugger (msg=0xc025d4fb "panic") at ../../i386/i386/db_interface.c:324 #1 0xc0153268 in panic (fmt=0xc0265de0 "nfs_strategy: buffer %p not locked") at ../../kern/kern_shutdown.c:450 #2 0xc01e3ade in nfs_strategy (ap=0xc6df6c00) at ../../nfs/nfs_vnops.c:2650 #3 0xc01e44c9 in nfs_writebp (bp=0xc2374e20, force=0x1, procp=0xc68a5100) at vnode_if.h:891 #4 0xc01e4322 in nfs_bwrite (ap=0xc6df6ca0) at ../../nfs/nfs_vnops.c:3034 #5 0xc01e4190 in nfs_flush (vp=0xc6df3440, cred=0xc0f48300, waitfor=0x1, p=0xc68a5100, commit=0x1) at vnode_if.h:1147 #6 0xc01e3b65 in nfs_fsync (ap=0xc6df6d40) at ../../nfs/nfs_vnops.c:2710 #7 0xc0179036 in vinvalbuf (vp=0xc6df3440, flags=0x1, cred=0xc0f48300, p=0xc68a5100, slpflag=0x0, slptimeo=0x0) at vnode_if.h:499 #8 0xc01b1af4 in nfs_vinvalbuf (vp=0xc6df3440, flags=0x1, cred=0xc0f48300, p=0xc68a5100, intrflg=0x1) at ../../nfs/nfs_bio.c:1078 #9 0xc01b10ac in nfs_write (ap=0xc6df6eb4) at ../../nfs/nfs_bio.c:730 #10 0xc018024c in vn_write (fp=0xc0f51940, uio=0xc6df6efc, cred=0xc0f48300, flags=0x0) at vnode_if.h:331 #11 0xc015f2a8 in dofilewrite (p=0xc68a5100, fp=0xc0f51940, fd=0x3, buf=0x804b000, nbyte=0x55, offset=0xffffffffffffffff, flags=0x0) at ../../kern/sys_generic.c:363 #12 0xc015f1b7 in write (p=0xc68a5100, uap=0xc6df6f80) at ../../kern/sys_generic.c:298 #13 0xc022a062 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x804b000, tf_esi = 0x804d040, tf_ebp = 0xbfbfcfb0, tf_isp = 0xc6df6fd4, tf_ebx = 0x55, tf_edx = 0x804b000, tf_ecx = 0x4, tf_eax = 0x4, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x280956dc, tf_cs = 0x1f, tf_eflags = 0x202, tf_esp = 0xbfbfcf88, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056 #14 0xc021baf0 in Xint0x80_syscall () #15 0x80485b9 in ?? () (kgdb) I assume that the origins are easy enough to trace, but I can take a dump or get other information if necessary. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 19:40:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id D9C0E14F8B for ; Sun, 27 Jun 1999 19:40:42 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA79733 for ; Sun, 27 Jun 1999 22:40:17 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Sun, 27 Jun 1999 22:40:17 -0400 (EDT) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: ctm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As most of you know by now, ctm is back, but ftp of ctm is temporarily still broken. If you want something, tell me and I'll stick it in http://www.freebsd.org/~chuckr. It's short of room there too, so don't ask for what you don't need. Thanks, I'll try not to post about ctm on current anymore. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 19:47: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8A5F915102 for ; Sun, 27 Jun 1999 19:47:06 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA16796; Sun, 27 Jun 1999 19:46:41 -0700 (PDT) (envelope-from dillon) Date: Sun, 27 Jun 1999 19:46:41 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280246.TAA16796@apollo.backplane.com> To: Peter Wemm Cc: current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. References: <19990627224713.A61D781@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Yep, I was aware of this before, but I didn't rip it out since I didn't :know what Kirk's intentions were. I'm assuming he's got his experience :with making the BSD/OS vfs reentrant in mind, so I don't want to break :anything that gets closer to that. A seperate test and then lock would :not be reentrant. (Sure, there are far bigger problems than this, but :every bit helps when we get there) I think that code runs at splbio(), so it would still work. But your right -- making the buffer cache code operate in an SMP environment would require a single atomic lock attempt. Still, to get to that point will take a huge amount of continued work so I would not worry about it too much now. :Actually, I think there is another set if missing BUF_KERNPROC() calls, :cluster_callback() frees buffers, so all buffers submitted with it had :better be reassigned. This is (I think) part of the problem that :cluster_wbuild() is hitting - things were supposed to have been reassigned :but are still hanging onto the current process. :... :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au : It could be. I've suggested to Kirk that he remove all the BUF_KERNPROC() stuff and instead reassign the lock in biodone(). My qlock stuff doesn't require lock reassign on release, so that could be why it isn't having problems while the lockmgr() stuff is. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 20:20: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 29884152DE for ; Sun, 27 Jun 1999 20:20:00 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-23.ucdavis.edu [169.237.16.151]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id UAA09555 for ; Sun, 27 Jun 1999 20:19:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id DAA02013 for current@freebsd.org; Mon, 28 Jun 1999 03:19:56 GMT (envelope-from obrien) Date: Sun, 27 Jun 1999 20:19:56 -0700 From: "David O'Brien" To: current@freebsd.org Subject: **HEADS UP** newsyslog.conf syntax change Message-ID: <19990627201956.A1998@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On your next ``make world'', you will need to change any "user.group" specifications in /etc/newsyslog.conf to "user:group". -- -- David (obrien@NUXI.com -or- obrien@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 27 23: 7:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep1.post.tele.dk (fep1.post.tele.dk [195.41.46.133]) by hub.freebsd.org (Postfix) with ESMTP id C42F914E65 for ; Sun, 27 Jun 1999 23:07:32 -0700 (PDT) (envelope-from peter@holm.cc) Received: from holm.cc ([195.249.209.24]) by fep1.post.tele.dk (InterMail v4.0 201-221) with ESMTP id <19990628060728.HVW27563.fep1@holm.cc> for ; Mon, 28 Jun 1999 08:07:28 +0200 Message-ID: <377711B4.F86D0404@holm.cc> Date: Mon, 28 Jun 1999 08:09:56 +0200 From: Peter Holm X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: boot -c causes pagefault in userconfig.c:savelist+18 Content-Type: multipart/mixed; boundary="------------C6C980DA3C83F9AE928C8A34" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C6C980DA3C83F9AE928C8A34 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit This in current as of Saturday. The attached patch to i386/i386/userconfig.c fixes the problem.: Regards -- Peter Holm | mailto:peter@holm.cc | http://login.dknet.dk/~pho/ -[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] - --------------C6C980DA3C83F9AE928C8A34 Content-Type: text/plain; charset=us-ascii; name="userconfig.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="userconfig.diff" *** userconfig.c~ Sun Jun 27 18:39:23 1999 --- userconfig.c Sun Jun 27 18:58:52 1999 *************** *** 843,849 **** { struct isa_device *id_p,*id_pn; struct isa_driver *isa_drv; ! char *name = list->device->id_driver->name; while (list) { --- 843,849 ---- { struct isa_device *id_p,*id_pn; struct isa_driver *isa_drv; ! char *name; while (list) { *************** *** 859,864 **** --- 859,865 ---- { /* look on the list for it */ if (id_p->id_id == list->device->id_id) { + name = list->device->id_driver->name; id_pn = id_p->id_next; isa_drv = id_p->id_driver; if (isa_drv && isa_drv->name) *************** *** 878,883 **** --- 879,885 ---- } if (!id_pn) /* not already on the list */ { + name = list->device->id_driver->name; id_pn = malloc(sizeof(struct isa_device),M_DEVL,M_WAITOK); bcopy(list->device,id_pn,sizeof(struct isa_device)); save_resource(list->device); --------------C6C980DA3C83F9AE928C8A34-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jun 27 23:45:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id AC53715369 for ; Sun, 27 Jun 1999 23:45:07 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-9.iptelecom.net.ua [212.42.68.200]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id JAA03907; Mon, 28 Jun 1999 09:48:11 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id JAA07209; Mon, 28 Jun 1999 09:45:01 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <377719A3.1F2F9D04@altavista.net> Date: Mon, 28 Jun 1999 09:43:47 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Chris Moody Cc: Current FreeBSD Subject: Re: Fw: libstdc++.so.2 References: <001b01bec103$d31b58c0$0fc0e8d1@chris1> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Moody wrote: > ----- Original Message ----- > From: Chris Moody > To: Questions FreeBSD > Sent: Sunday, June 27, 1999 6:14 PM > Subject: libstdc++.so.2 > > > Hello everyone, > > > > I spent several hours last night installing the Current version of FreeBSD > > over the internet, for some reason, one of the files was unable to > download > > successfully. Currently I am unable to get into X Windows, when I try, the > X > > Windows screen comes up for a second, and then I'm back at a text prompt > > telling me at least one time, that it can't find libstdc++so.2, now I was > > wondering, can anyone tell me where I could get this file, so that I could > > download it from Windows, and then copy it over into the directory FreeBSD > > wants it to be in? Try to recompile and reinstall your window manager (which obviously uses libstdc++). Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 0:56:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id A0DDD153B3; Mon, 28 Jun 1999 00:56:20 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id UAA01061; Sun, 27 Jun 1999 20:47:57 -0700 (PDT) Message-Id: <199906280347.UAA01061@flamingo.McKusick.COM> To: Matthew Dillon Subject: Re: Found the startup panic - ccd ( patch included ) Cc: Alan Cox , Julian Elischer , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey In-reply-to: Your message of "Sat, 26 Jun 1999 17:51:05 PDT." <199906270051.RAA05366@apollo.backplane.com> Date: Sun, 27 Jun 1999 20:47:51 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off, sorry for the silence. This is gay freedom weekend in San Francisco, and I've been rather busy socially. It was poor timing on my part to commit such a big change just before I was going to be gone all weekend. I have tried to answer several questions below. Date: Sat, 26 Jun 1999 17:51:05 -0700 (PDT) From: Matthew Dillon To: Alan Cox Cc: Julian Elischer , Kirk McKusick , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net Subject: Found the startup panic - ccd ( patch included ) :I'm seeing the same thing here. : : Alan : :P.S. Julian, perhaps a "mild" warning to -smp would be appropriate. :(I'm off to dinner.) I think I found it. The CCD device is malloc()ing buffers and the new lock is not being initialized. diff included below. Also, in the ccd driver, it was inheriting the B_BUSY by copying b_flags - but Kirk must-a missed it because it was not explicitly specifying B_BUSY. So we also have to call BUF_LOCK() after the BUF_LOCKINIT(). Bleh. I'm not sure I want to know why ccd is malloc()ing its own buffer structures. I'll bet we could improve ccd's performance significantly by having it use getpbuf(). Alan, et all, apply the patch then recompile and reinstall your /usr/src/sys/modules, recompile and reinstall your kernel, and reboot. Kirk, please review and then commit the patch if all looks ok! Thanks! My test machine gets to where I can login, now. I am running more tests. -Matt Matthew Dillon These changes look absolutely correct to me. I see that Peter has committed them. Index: dev/ccd/ccd.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ccd/ccd.c,v retrieving revision 1.48 diff -u -r1.48 ccd.c --- ccd.c 1999/05/30 16:51:18 1.48 +++ ccd.c 1999/06/27 00:33:52 @@ -915,6 +915,8 @@ cbp->cb_buf.b_data = addr; cbp->cb_buf.b_vp = ci->ci_vp; LIST_INIT(&cbp->cb_buf.b_dep); + BUF_LOCKINIT(&cbp->cb_buf); + BUF_LOCK(&cbp->cb_buf, LK_EXCLUSIVE); cbp->cb_buf.b_resid = 0; if (cs->sc_ileave == 0) cbc = dbtob((off_t)(ci->ci_size - cbn)); @@ -947,6 +949,8 @@ cbp->cb_buf.b_dev = ci2->ci_dev; cbp->cb_buf.b_vp = ci2->ci_vp; LIST_INIT(&cbp->cb_buf.b_dep); + BUF_LOCKINIT(&cbp->cb_buf); + BUF_LOCK(&cbp->cb_buf, LK_EXCLUSIVE); cbp->cb_comp = ci2 - cs->sc_cinfo; cb[1] = cbp; /* link together the ccdbuf's and clear "mirror done" flag */ From: Peter Wemm Date: Sun, 27 Jun 1999 16:44:14 +0800 To: Matthew Dillon Subject: Re: BUF_LOCK() related panic.. Cc: current@FreeBSD.ORG, mckusick@mckusick.com In-reply-to: Your message of "Sun, 27 Jun 1999 01:15:43 MST." <199906270815.BAA10773@apollo.backplane.com> It seems to me the main problem (so far) is the buftimelock.. simple_lock(&buftimelock); bp->b_lock.lk_wmesg = buf_wmesg; bp->b_lock.lk_prio = PRIBIO + 4; bp->b_lock.lk_timo = 0; return (lockmgr(&(bp)->b_lock, locktype, &buftimelock, curproc)); Inside lockmgr(): simple_lock(&lkp->lk_interlock); if (flags & LK_INTERLOCK) simple_unlock(interlkp); ^^^^^^^^ <--- &buftimelock; Note that there is no LK_INTERLOCK in any of the calls to lockmgr().. On UP, simplelocks are noops. On SMP, they are real and nothing is ever freeing buftimelock. But that doesn't fix the UP problem where cluster_wbuild() tries to recursively re-lock a buf that the current process already owns. I have a few ideas about that one though, I just don't understand the clustering well enough yet to fix it. Speaking of SMP and simple locks, I'd like to turn on the debugging simplelocks that keep a reference count and check before switching to make sure that a process doesn't sleep holding a lock. This is a pretty fundamental sanity check and would have found the LK_INTERLOCK problem above before it got committed. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au The above along with the splbio locking is the correct fix. I see that Peter has already committed it. On the subject of BUF_KERNPROC, this must be done as I have coded it, not later in biodone. The problem is when the filesystem does a readahead. It starts the I/O on the buffer that it really wants, then starts ASYNC reads on the readahead buffers. When it finishes with the buffer that it wanted and the application enters the kernel to get the next buffer, the filesystem will attempt to lock the buffer on which it earlier initiated the read. If the I/O has not yet finished one of two bad things will happen. If the lock is not recursive, it will panic with `locking against myself' since it will hold the lock from the time when it initiated the readahead. If recursive locking is allowed, then it will get the buffer (since it holds the exclusive lock) and use it before it has been filled. So, it is semantically important that ASYNC read buffers be disowned (i.e., given to the kernel) at the time they are created. That way, only the kernel can access the buffer until the read I/O is done. I agree that this code is ugly, but it is necessary. From: Peter Wemm Date: Mon, 28 Jun 1999 06:47:13 +0800 To: Matthew Dillon Subject: Re: BUF_LOCK() related panic.. Cc: current@FreeBSD.ORG, mckusick@mckusick.com In-reply-to: Your message of "Sun, 27 Jun 1999 13:06:13 MST." <199906272006.NAA15499@apollo.backplane.com> Matthew Dillon wrote: > : > :But that doesn't fix the UP problem where cluster_wbuild() tries to > :recursively re-lock a buf that the current process already owns. I have a > :few ideas about that one though, I just don't understand the clustering > :well enough yet to fix it. > > Ok, I just hit this testing the lockmgr changes. > > I think the problem is that cluster_wbuild's algorithm was polluted > a little by Kirk's commit. > > Previously it tested for B_BUSY to determine if it could then lock it > to include in the cluster. Yep, I was aware of this before, but I didn't rip it out since I didn't know what Kirk's intentions were. I'm assuming he's got his experience with making the BSD/OS vfs reentrant in mind, so I don't want to break anything that gets closer to that. A seperate test and then lock would not be reentrant. (Sure, there are far bigger problems than this, but every bit helps when we get there) > Kirk changed this to actually attempt a lock, and then include it > if the lock succeeded and not include it if the lock failed. > > The problem is that if the buffer was already locked by the same process, > this change results in a panic instead of a simple failure to obtain the > lock. > The solution is to re-tool the code to use the original algorithm ( test > the lock before trying to get it, rather then simply trying to get it ), > but with the new locks. I do not have time today to do this but I believ e > I have given sufficient information for Peter, Kirk, or Alan to make the > fix. Actually, I think there is another set if missing BUF_KERNPROC() calls, cluster_callback() frees buffers, so all buffers submitted with it had better be reassigned. This is (I think) part of the problem that cluster_wbuild() is hitting - things were supposed to have been reassigned but are still hanging onto the current process. > I believe there are two or three areas in Kirk's patchset where he > replaced an explicit test with an attempt to actually gain the lock where > this sort of panic can occur. I think Kirk was trying to optimize the > code :-) Heh heh. Just goes to show that combining functional > replacements with optimizations all in one go does not always work. > > -Matt > Matthew Dillon > > > :Cheers, > :-Peter > :-- > :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au The BUF_LOCK cannot simply be replaced by a check to see if the buffer has a non-zero count. If recursive locks are allowed, they need to be taken into consideration. If shared locks are involved there may be multiple of them allowed (though obviously they are not yet used). I propose the following change to the buffer locking code to basically avoid the locking against myself panic when doing a polling lock (since if recursion is not allowed it will return an error rather than blocking). I am going to leave this running on my test machine overnight to check for problems. I am committing it now as I believe it to be correct and that it will solve some of the locking problems that we have seen. Index: kern_lock.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v retrieving revision 1.26 diff -c -r1.26 kern_lock.c *** kern_lock.c 1999/06/26 02:46:00 1.26 --- kern_lock.c 1999/06/28 07:28:21 *************** *** 337,348 **** * Recursive lock. */ #if !defined(MAX_PERF) ! if ((extflags & LK_CANRECURSE) == 0) panic("lockmgr: locking against myself"); #endif ! lkp->lk_exclusivecount++; ! COUNT(p, 1); ! break; } /* * If we are just polling, check to see if we will sleep. --- 337,350 ---- * Recursive lock. */ #if !defined(MAX_PERF) ! if ((extflags & (LK_NOWAIT | LK_CANRECURSE)) == 0) panic("lockmgr: locking against myself"); #endif ! if ((extflags & LK_CANRECURSE) != 0) { ! lkp->lk_exclusivecount++; ! COUNT(p, 1); ! break; ! } } /* * If we are just polling, check to see if we will sleep. I do not see the problem that you are pointing out with missing BUF_KERNPROC in cluster_callback, but it is well past midnight, so I may not be thinking clearly. Greg Lehey has sent me a panic with the buffer locking in the NFS code. I am too tired to attack it tonight, but will look at it in the morning. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 1:22:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id AD90E14D01; Mon, 28 Jun 1999 01:22:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id BAA06942; Mon, 28 Jun 1999 01:21:22 -0700 (PDT) Date: Mon, 28 Jun 1999 01:21:21 -0700 (PDT) From: Julian Elischer To: Kirk McKusick Cc: Matthew Dillon , Alan Cox , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-Reply-To: <199906280347.UAA01061@flamingo.McKusick.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999, Kirk McKusick wrote: > I see that Peter has already committed it. > > On the subject of BUF_KERNPROC, this must be done as I have coded > it, not later in biodone. The problem is when the filesystem does > a readahead. It starts the I/O on the buffer that it really wants, > then starts ASYNC reads on the readahead buffers. When it finishes > with the buffer that it wanted and the application enters the kernel > to get the next buffer, the filesystem will attempt to lock the > buffer on which it earlier initiated the read. If the I/O has not > yet finished one of two bad things will happen. If the lock is not > recursive, it will panic with `locking against myself' since it will > hold the lock from the time when it initiated the readahead. If > recursive locking is allowed, then it will get the buffer (since > it holds the exclusive lock) and use it before it has been filled. > So, it is semantically important that ASYNC read buffers be disowned > (i.e., given to the kernel) at the time they are created. That way, > only the kernel can access the buffer until the read I/O is done. > I agree that this code is ugly, but it is necessary. > One solution to the "locking against self" probelm with read-ahead buffers would be to give some other entity the ownership of the read-ahead. I would consider even having a separate ID for async operations (the asyncd kermnel thread?) Possibly they could simply be assigned to an existing PID (we have several to chose from .. pagedaemon, syncer or vmdaemon) I mean the requesting process isn't really actually requesting the lookahead, so it should be up to the entity that DID request it (the kernel?) to lock the buffers. I think that whenever you try make something appear as something that it is not you complicate the picture. In this case we are tryin g to make it look as if that process was responsible for the readahead requests, when in actual fact, it is another entity taking it upon itself to make that decision, and see where it gets us? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 1:28:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8910314E1E; Mon, 28 Jun 1999 01:28:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA18365; Mon, 28 Jun 1999 01:28:29 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 01:28:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199906280828.BAA18365@apollo.backplane.com> To: Kirk McKusick Cc: Alan Cox , Julian Elischer , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <199906280347.UAA01061@flamingo.McKusick.COM> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On the subject of BUF_KERNPROC, this must be done as I have coded :it, not later in biodone. The problem is when the filesystem does :a readahead. It starts the I/O on the buffer that it really wants, :... :recursive locking is allowed, then it will get the buffer (since :it holds the exclusive lock) and use it before it has been filled. :So, it is semantically important that ASYNC read buffers be disowned :(i.e., given to the kernel) at the time they are created. That way, :only the kernel can access the buffer until the read I/O is done. :I agree that this code is ugly, but it is necessary. Ok, I see the problem. But I still think we need to implement this a different way. Polluting all the VOP_STRATEGY calls with yet another setup requirement that someone may forget to do is a step backwards, especially if it is only covering a specific situation that could be solved in other ways. Perhaps we can implement a locking system that is immune to the problem. i.e. not attempt to continue to use lockmgr() locks which are turning out to be unsuited to the work but instead use something like my qlocks, but modified to deal with the I/O situation. Perhaps we can use Terry's suggestion for function-specific locks. Instead of using a shared/exclusive lock we instead implement a zone bitmap type of lock, where we can obtain a bitmask of up to 32 non-recursive exclusive locks simultaniously. We would then use the bits to indicate different situations. We would no longer need recursive locks or even shared locks but instead would define bits for immediate access (bits not held through a blocking condition) and for long-term operations-in-progress, such as an I/O-in-progress sitiation ( bits held through a blocking condition). Alternatively, we can use a combination of locks to implement exclusivity as well as shared access. e.g. one bit masking exclusive lock and one normal lock. Normal locks would be obtained and released quickly ( so there is no recursion problem ), but when read I/O is initiated the read-I/O-in-progress lock bit would be left set, and when write I/O is initiated the write-I/O-in-progress lock bit would be left set. Later on when we are trying to relock the buffer, but do not want to allow the situation where we relock a buffer with I/O in progress, we simply attempt to get the I/O bits *AND* the code serialization bit all simultaniously. Since the I/O is in progress this attempt would fail. If the I/O is not in progress both locks succeed; recursion is not a problem because the access lock is strictly temporary and was held and released earlier. :not yet used). I propose the following change to the buffer locking :code to basically avoid the locking against myself panic when doing :a polling lock (since if recursion is not allowed it will return :an error rather than blocking). I am going to leave this running :on my test machine overnight to check for problems. I am committing :it now as I believe it to be correct and that it will solve some :of the locking problems that we have seen. : :Index: kern_lock.c :=================================================================== :RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v :... : : Kirk I'll try running this too. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 1:37: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id A0F4414CC0 for ; Mon, 28 Jun 1999 01:36:36 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B54E582; Mon, 28 Jun 1999 16:36:31 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Kirk McKusick Cc: Matthew Dillon , Alan Cox , Julian Elischer , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Sun, 27 Jun 1999 20:47:51 MST." <199906280347.UAA01061@flamingo.McKusick.COM> Date: Mon, 28 Jun 1999 16:36:31 +0800 From: Peter Wemm Message-Id: <19990628083631.B54E582@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote: [..] Re: kern_lock.c - looks like a reasonable fix. There isn't much point panicing for a poll. > I do not see the problem that you are pointing out with missing > BUF_KERNPROC in cluster_callback, but it is well past midnight, > so I may not be thinking clearly. No, you are correct. I had experimented with moving the cluster_head reassignment to LK_KERNPROC out of BUF_KERNPROC() and into the point where it was added into the tailq, but in the end I realized it wasn't much different and suspected that there could be problems if the cluster build was abandoned at some point, so I left it the way it is. > Greg Lehey has sent me a panic with the buffer locking in the NFS code. > I am too tired to attack it tonight, but will look at it in the morning. I might have a look if I get a chance.. > Kirk Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 1:41:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211]) by hub.freebsd.org (Postfix) with ESMTP id 68BC614CC0 for ; Mon, 28 Jun 1999 01:41:11 -0700 (PDT) (envelope-from ignatios@cs.uni-bonn.de) Received: from cauchy.cs.uni-bonn.de (cauchy [131.220.4.169]) by theory.cs.uni-bonn.de (8.9.1a/8.9.1) with ESMTP id KAA15314; Mon, 28 Jun 1999 10:40:33 +0200 (MET DST) Received: (from ignatios@localhost) by cauchy.cs.uni-bonn.de (8.8.8/8.8.8) id KAA13987; Mon, 28 Jun 1999 10:40:15 +0200 (MET DST) Message-ID: <19990628104015.B13930@cs.uni-bonn.de> Date: Mon, 28 Jun 1999 10:40:15 +0200 From: Ignatios Souvatzis To: Warner Losh , current@FreeBSD.org, tech-kern@netbsd.org, tech@openbsd.org Subject: Re: General feeling on merging APIs... References: <199906270422.WAA08307@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.2i In-Reply-To: <199906270422.WAA08307@harmony.village.org>; from Warner Losh on Sat, Jun 26, 1999 at 10:22:29PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 26, 1999 at 10:22:29PM -0600, Warner Losh wrote: > In message <199906251653.KAA01796@caspian.plutotech.com> "Justin T. Gibbs" writes: > : The hope is to provide a consistent interface across > : all *BSDs which is why I've addressed this to all of the *BSD projects. > > More generally, I'd like to identify areas where the kernel APIs of > the various projects have diverged and see what, if anything, can be > done about them. I'd also like to get commitment from the various > controlling bodies of the *BSD projects to a statement something along > the lines of: For one: http://www.de.daemonnews.org/199809/underhood.html When I, back then, contacted networking wizards from BSDi and FreeBSD, to explicitly offer them the code, or at least to coordinate the definition of the AF_ARP/PF_ARP constant I neede for it, both weren't interested, apparently because they didn't support, and didn't intend to do so, ARCnet (which is not the whole purpose of that change we did in NetBSD, but that's another story). Regards, Ignatios Souvatzis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 2: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6814D14BDA for ; Mon, 28 Jun 1999 02:02:12 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA17555; Mon, 28 Jun 1999 18:32:08 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id SAA46890; Mon, 28 Jun 1999 18:32:06 +0930 (CST) Date: Mon, 28 Jun 1999 18:32:06 +0930 From: Greg Lehey To: Peter Wemm Cc: Kirk McKusick , Matthew Dillon , Alan Cox , Julian Elischer , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org Subject: Re: Found the startup panic - ccd ( patch included ) Message-ID: <19990628183206.T43194@freebie.lemis.com> References: <199906280347.UAA01061@flamingo.McKusick.COM> <19990628083631.B54E582@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990628083631.B54E582@overcee.netplex.com.au>; from Peter Wemm on Mon, Jun 28, 1999 at 04:36:31PM +0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 28 June 1999 at 16:36:31 +0800, Peter Wemm wrote: > Kirk McKusick wrote: > [..] > Re: kern_lock.c - looks like a reasonable fix. There isn't much point > panicing for a poll. > >> I do not see the problem that you are pointing out with missing >> BUF_KERNPROC in cluster_callback, but it is well past midnight, >> so I may not be thinking clearly. > > No, you are correct. I had experimented with moving the cluster_head > reassignment to LK_KERNPROC out of BUF_KERNPROC() and into the point > where it was added into the tailq, but in the end I realized it wasn't > much different and suspected that there could be problems if the cluster > build was abandoned at some point, so I left it the way it is. > >> Greg Lehey has sent me a panic with the buffer locking in the NFS code. >> I am too tired to attack it tonight, but will look at it in the morning. > > I might have a look if I get a chance.. I've been collecting them :-) The first one looks like this: Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 326 } #0 Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 #1 0xc0153474 in panic (fmt=0xc02676a0 "nfs_strategy: buffer %p not locked") at ../../kern/kern_shutdown.c:450 #2 0xc01e41b6 in nfs_strategy (ap=0xc6df2d84) at ../../nfs/nfs_vnops.c:2650 #3 0xc01e4be1 in nfs_writebp (bp=0xc236d7d8, force=0x0, procp=0x0) at vnode_if.h:891 #4 0xc01b1f93 in nfs_write (ap=0xc6df2eb4) at ../../nfs/nfs_bio.c:975 #5 0xc01807d2 in vn_write (fp=0xc0f55000, uio=0xc6df2efc, cred=0xc0f52300, flags=0x0) at vnode_if.h:331 #6 0xc015f4c8 in dofilewrite (p=0xc68aa260, fp=0xc0f55000, fd=0x1, buf=0x80a4000, nbyte=0x400, offset=0xffffffffffffffff, flags=0x0) at ../../kern/sys_generic.c:363 #7 0xc015f3d7 in write (p=0xc68aa260, uap=0xc6df2f80) at ../../kern/sys_generic.c:298 #8 0xc022aee6 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x80a4000, tf_esi = 0x400, tf_ebp = 0xbfbfa6c4, tf_isp = 0xc6df2fd4, tf_ebx = 0x0, tf_edx = 0x1, tf_ecx = 0xa, tf_eax = 0x4, tf_trapno = 0x0, tf_err = 0x2, tf_eip = 0x806a7f8, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xbfbfa6a8, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056 #9 0xc021c960 in Xint0x80_syscall () #10 0x8052c3c in ?? () #11 0x8052bea in ?? () #12 0x804a170 in ?? () #13 0x804b45c in ?? () #14 0x804a675 in ?? () #15 0x8051073 in ?? () #16 0x8050fef in ?? () #17 0x80480e9 in ?? () It happens when I do just about any NFS write; I've been reproducing it with 'make depend' in the NFS-mounted kernel build directory. I'll try to get a dump and send you both a message about where you can find it. The other one is even more simple to reproduce: $ dd if=/dev/da0d of=/dev/null bs=120b Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 326 } #0 Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 #1 0xc0153474 in panic (fmt=0xc025d9a0 "lockmgr: locking against myself") at ../../kern/kern_shutdown.c:450 #2 0xc014eafb in debuglockmgr (lkp=0xc2368c4c, flags=0x10022, interlkp=0xc02c4564, p=0xc68aa3c0, name=0xc0261452 "lockmgr", file=0xc026145a "../../sys/buf.h", line=0x11b) at ../../kern/kern_lock.c:341 #3 0xc0173fc2 in getblk (vp=0xc6dcd780, blkno=0x20, size=0x2000, slpflag=0x0, slptimeo=0x0) at ../../sys/buf.h:283 #4 0xc0172531 in breadn (vp=0xc6dcd780, blkno=0x20, size=0x2000, rablkno=0xc6deee44, rabsize=0xc6deee48, cnt=0x1, cred=0x0, bpp=0xc6deee4c) at ../../kern/vfs_bio.c:433 #5 0xc01864d5 in spec_read (ap=0xc6deeeb4) at ../../miscfs/specfs/spec_vnops.c:308 #6 0xc01f8378 in ufsspec_read (ap=0xc6deeeb4) at ../../ufs/ufs/ufs_vnops.c:1826 #7 0xc01f8931 in ufs_vnoperatespec (ap=0xc6deeeb4) at ../../ufs/ufs/ufs_vnops.c:2327 #8 0xc0180684 in vn_read (fp=0xc0f56d80, uio=0xc6deeefc, cred=0xc0f52200, flags=0x0) at vnode_if.h:303 #9 0xc015f157 in dofileread (p=0xc68aa3c0, fp=0xc0f56d80, fd=0x3, buf=0x805d000, nbyte=0xf000, offset=0xffffffffffffffff, flags=0x0) at ../../kern/sys_generic.c:179 #10 0xc015f067 in read (p=0xc68aa3c0, uap=0xc6deef80) at ../../kern/sys_generic.c:111 #11 0xc022aee6 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0xbfbfcfdc, tf_esi = 0xbfbfcfc8, tf_ebp = 0xbfbfcf90, tf_isp = 0xc6deefd4, tf_ebx = 0xbfbfcfc8, tf_edx = 0x4, tf_ecx = 0x80580a0, tf_eax = 0x3, tf_trapno = 0x16, tf_err = 0x2, tf_eip = 0x8049eec, tf_cs = 0x1f, tf_eflags = 0x246, tf_esp = 0xbfbfcf80, tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056 #12 0xc021c960 in Xint0x80_syscall () #13 0x8048c6d in ?? () #14 0x80480e9 in ?? () For some reason, breadn() doesn't seem to work any more. It works find with bread(), but I haven't localized how the code differs. I've applied Kirk's patch to lockmgr, which seemed to relate to the breadn() problem, but it then found a different set of flags to pass to lockmgr (LK_SLEEPFAIL instead of LK_NOWAIT) and still cause the panic. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 2: 3:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 77AD514BDA for ; Mon, 28 Jun 1999 02:03:29 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10yXJt-000Lma-00; Mon, 28 Jun 1999 11:03:17 +0200 From: Sheldon Hearn To: Doug Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default In-reply-to: Your message of "Sun, 27 Jun 1999 18:37:51 MST." <3776D1EF.D4D4021E@gorean.org> Date: Mon, 28 Jun 1999 11:03:17 +0200 Message-ID: <83735.930560597@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Jun 1999 18:37:51 MST, Doug wrote: > This is going to sound like I'm attacking sheldon, but I'm not > since he's already stated that the got approval for this change from > Jordan. Jordan will be the first to admit that he's been wrong before and I have a thick skin. > First, the setting in /etc/defaults/rc.conf should default to > off, as defaulting it to on violates POLA for the many many people who > haven't updated to 3.x from 2.2 yet. If we were integrating TCP Wrapper support into the base system for the very first time, I'd agree with you. However, we've already had a release go out with an inetd that wrapped by default. This is a situation in which we can't make _everyone_ happy. For the particular case you've provided, anyone who upgrades from 2.2 to 3.3 without reading the release notes will get what's coming to him. > Also, if the decision is made to leave it on by default, there should > be a hosts.allow file installed by default that has nothing but "ALL : > ALL" in it. We already have a hosts.allow that effectively allows everything. > Second, this command line switch is horrible UI design for > several reasons. First, any command line option that requires that > the same flag be applied twice is bad design, historical precedents > aside. That's an unfortunately timed revelation for me. I feel like I've seen it in a number of programs, although the only one I can remember is ftpd(8). I used that program as a reference, not knowing that it was bad design. :-( > Second, what if I want to wrap my internal services, but not wrap my > external ones? Then you want something that the guys working on the code, who use inetd quite a lot, didn't think of. They probably made the assumption that real-world scenarios like that don't exist. > I propose that the -w flag be changed to take parameters. To > start with, you would have [-w <[e] [i]>] to control wrapping for > external and internal services respectively. This makes my skin crawl, but that's probably just because I know what the code looks like. :-) 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 Jun 28 2:38:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by hub.freebsd.org (Postfix) with ESMTP id 116D015408 for ; Mon, 28 Jun 1999 02:38:29 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id EAA22924; Mon, 28 Jun 1999 04:38:27 -0500 (CDT) Received: from sji-ca44-84.ix.netcom.com(209.111.212.212) by dfw-ix14.ix.netcom.com via smap (V1.3) id rma022911; Mon Jun 28 04:37:55 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id CAA51900; Mon, 28 Jun 1999 02:37:50 -0700 (PDT) Date: Mon, 28 Jun 1999 02:37:50 -0700 (PDT) Message-Id: <199906280937.CAA51900@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org In-reply-to: <19990627201956.A1998@dragon.nuxi.com> (obrien@NUXI.com) Subject: Re: **HEADS UP** newsyslog.conf syntax change From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) References: <19990627201956.A1998@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * * On your next ``make world'', you will need to change any "user.group" * specifications in /etc/newsyslog.conf to "user:group". This is not the right way to do it. === - if ((group = strchr(q, '.')) != NULL) { + if ((group = strchr(q, ':')) != NULL) { === Please first change it to accept both syntaxes, with a warning in the manpage that the old one will go away in the future. Then remove the old syntax after a few months. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 3:18:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9C5B515415; Mon, 28 Jun 1999 03:18:17 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-31.ucdavis.edu [169.237.16.159]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id DAA11510; Mon, 28 Jun 1999 03:18:14 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA35783; Mon, 28 Jun 1999 10:18:12 GMT (envelope-from obrien) Date: Mon, 28 Jun 1999 03:18:11 -0700 From: "David O'Brien" To: Satoshi - Ports Wraith - Asami Cc: current@freebsd.org Subject: Re: **HEADS UP** newsyslog.conf syntax change Message-ID: <19990628031811.B14773@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990627201956.A1998@dragon.nuxi.com> <199906280937.CAA51900@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199906280937.CAA51900@silvia.hip.berkeley.edu>; from Satoshi - Ports Wraith - Asami on Mon, Jun 28, 1999 at 02:37:50AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * On your next ``make world'', you will need to change any "user.group" > * specifications in /etc/newsyslog.conf to "user:group". > > This is not the right way to do it. > > Please first change it to accept both syntaxes, with a warning in the > manpage that the old one will go away in the future. Then remove the > old syntax after a few months. How about we leave it this way in -CURRENT, and the MFC will act in the above way. This will give people the remaining lifetime of 3.x (1,2,3? more releases) to convert. For those running -CURRENT... well they are supose to take heed of "HEADS UP" messages. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 3:27: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by hub.freebsd.org (Postfix) with ESMTP id 478FD14C39 for ; Mon, 28 Jun 1999 03:27:05 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4) id FAA26872; Mon, 28 Jun 1999 05:27:01 -0500 (CDT) Received: from sji-ca44-84.ix.netcom.com(209.111.212.212) by dfw-ix2.ix.netcom.com via smap (V1.3) id rma026863; Mon Jun 28 05:26:16 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA52131; Mon, 28 Jun 1999 03:26:11 -0700 (PDT) Date: Mon, 28 Jun 1999 03:26:11 -0700 (PDT) Message-Id: <199906281026.DAA52131@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: obrien@NUXI.com Cc: current@freebsd.org In-reply-to: <19990628031811.B14773@dragon.nuxi.com> (obrien@NUXI.com) Subject: Re: **HEADS UP** newsyslog.conf syntax change From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) References: <19990627201956.A1998@dragon.nuxi.com> <199906280937.CAA51900@silvia.hip.berkeley.edu> <19990628031811.B14773@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "David O'Brien" * > Please first change it to accept both syntaxes, with a warning in the * > manpage that the old one will go away in the future. Then remove the * > old syntax after a few months. * * How about we leave it this way in -CURRENT, and the MFC will act in the * above way. This will give people the remaining lifetime of 3.x (1,2,3? * more releases) to convert. For those running -CURRENT... well they are * supose to take heed of "HEADS UP" messages. Well that will work for me, but I still think it is nicer to do it in a two-step way, so that people don't neccesarily have to convert it right between the make world and reboot. The way I work is, I see the HEADS UP message, edit the setup files so that it will be correct after the next make world or reboot, then forget about it. (Note that if the change is completely backward-incompatible, you can't edit the files right away unless you are sure you aren't going to reboot the machine before the next make world....) Of course, since this is a program that is compilable by itself, I can cvs update usr.sbin/newsyslog and make all install there and change newsyslog.conf now. So I guess it's ok, but you may want to send out another message saying that it's probably safer to rebuild newsyslog and edit newsyslog.conf right now rather than trying to remember doing it right with the next make world. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 3:30:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DAED414C39 for ; Mon, 28 Jun 1999 03:30:49 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-31.ucdavis.edu [169.237.16.159]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id DAA11597 for ; Mon, 28 Jun 1999 03:30:46 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA38033 for current@FreeBSD.ORG; Mon, 28 Jun 1999 10:30:43 GMT (envelope-from obrien) Date: Mon, 28 Jun 1999 03:30:42 -0700 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: HEADS UP! Inetd wrapping OFF by default Message-ID: <19990628033042.A37489@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <32068.930508133@axl.noc.iafrica.com> <3776D1EF.D4D4021E@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <3776D1EF.D4D4021E@gorean.org>; from Doug on Sun, Jun 27, 1999 at 06:37:51PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First, the setting in /etc/defaults/rc.conf should default to off, as > defaulting it to on violates POLA for the many many people who haven't > updated to 3.x from 2.2 yet. Personally, I don't care what is the default in 3.x, but it should be ON by default in 4.0. > I propose that the -w flag be changed to take parameters. To start with, > you would have [-w <[e] [i]>] to control wrapping for external and internal > services respectively. This would also allow the system to be extensible in > the future to include other types or subtypes of services. Interesting idea... I like it. As you said, it removes us from forcing some policy and just provides the mechanism. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 6:49:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6D69214DA6 for ; Mon, 28 Jun 1999 06:49:50 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id ADBA882; Mon, 28 Jun 1999 21:49:48 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: Kirk McKusick , Matthew Dillon , Alan Cox , Julian Elischer , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Mon, 28 Jun 1999 18:32:06 +0930." <19990628183206.T43194@freebie.lemis.com> Date: Mon, 28 Jun 1999 21:49:48 +0800 From: Peter Wemm Message-Id: <19990628134948.ADBA882@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Monday, 28 June 1999 at 16:36:31 +0800, Peter Wemm wrote: > > Kirk McKusick wrote: > > [..] > >> Greg Lehey has sent me a panic with the buffer locking in the NFS code. > >> I am too tired to attack it tonight, but will look at it in the morning. > > > > I might have a look if I get a chance.. > > I've been collecting them :-) The first one looks like this: > > Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 > 326 } > #0 Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 > #1 0xc0153474 in panic (fmt=0xc02676a0 "nfs_strategy: buffer %p not locked") at ../../kern/kern_shutdown.c:450 [..] > It happens when I do just about any NFS write; I've been reproducing > it with 'make depend' in the NFS-mounted kernel build directory. I'll > try to get a dump and send you both a message about where you can find > it. All things being equal, this should be fixed, there was a negated assertion in nfs_strategy. :-) > The other one is even more simple to reproduce: > > $ dd if=/dev/da0d of=/dev/null bs=120b > > Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 > 326 } > #0 Debugger (msg=0xc025e7fb "panic") at ../../i386/i386/db_interface.c:326 > #1 0xc0153474 in panic (fmt=0xc025d9a0 "lockmgr: locking against myself") at ../../kern/kern_shutdown.c:450 > #2 0xc014eafb in debuglockmgr (lkp=0xc2368c4c, flags=0x10022, interlkp=0xc02 c4564, p=0xc68aa3c0, > name=0xc0261452 "lockmgr", file=0xc026145a "../../sys/buf.h", line=0x11b) at ../../kern/kern_lock.c:341 > #3 0xc0173fc2 in getblk (vp=0xc6dcd780, blkno=0x20, size=0x2000, slpflag=0x0 , slptimeo=0x0) at ../../sys/buf.h:283 > #4 0xc0172531 in breadn (vp=0xc6dcd780, blkno=0x20, size=0x2000, rablkno=0xc 6deee44, rabsize=0xc6deee48, cnt=0x1, > cred=0x0, bpp=0xc6deee4c) at ../../kern/vfs_bio.c:433 > #5 0xc01864d5 in spec_read (ap=0xc6deeeb4) at ../../miscfs/specfs/spec_vnops .c:308 > #6 0xc01f8378 in ufsspec_read (ap=0xc6deeeb4) at ../../ufs/ufs/ufs_vnops.c:1 826 > #7 0xc01f8931 in ufs_vnoperatespec (ap=0xc6deeeb4) at ../../ufs/ufs/ufs_vnop s.c:2327 > #8 0xc0180684 in vn_read (fp=0xc0f56d80, uio=0xc6deeefc, cred=0xc0f52200, fl ags=0x0) at vnode_if.h:303 > #9 0xc015f157 in dofileread (p=0xc68aa3c0, fp=0xc0f56d80, fd=0x3, buf=0x805d 000, nbyte=0xf000, > offset=0xffffffffffffffff, flags=0x0) at ../../kern/sys_generic.c:179 > #10 0xc015f067 in read (p=0xc68aa3c0, uap=0xc6deef80) at ../../kern/sys_gener ic.c:111 > #11 0xc022aee6 in syscall (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, t f_edi = 0xbfbfcfdc, tf_esi = 0xbfbfcfc8, > tf_ebp = 0xbfbfcf90, tf_isp = 0xc6deefd4, tf_ebx = 0xbfbfcfc8, tf_edx = 0x4, tf_ecx = 0x80580a0, tf_eax = 0x3, > tf_trapno = 0x16, tf_err = 0x2, tf_eip = 0x8049eec, tf_cs = 0x1f, tf_ef lags = 0x246, tf_esp = 0xbfbfcf80, > tf_ss = 0x2f}) at ../../i386/i386/trap.c:1056 > #12 0xc021c960 in Xint0x80_syscall () > #13 0x8048c6d in ?? () > #14 0x80480e9 in ?? () > > For some reason, breadn() doesn't seem to work any more. It works > find with bread(), but I haven't localized how the code differs. Hmm... > I've applied Kirk's patch to lockmgr, which seemed to relate to the > breadn() problem, but it then found a different set of flags to pass > to lockmgr (LK_SLEEPFAIL instead of LK_NOWAIT) and still cause the > panic. There are also some serious problems with the swap pager.. For starters, BUF_KERNPROC() internally checks that B_ASYNC is set because that's when biodone() frees the lock. However, B_CALL may or may not free the lock too, for example swp_pager_async_iodone() in swap_pager.c. Also, the swap IO clustering/chainging etc is troubled since it turns on and off B_ASYNC and does it's own freeing and waiting. I haven't got my brain around it yet but I don't think it's going to be too hard to fix. Incidently, I do find Matt's code and comments quite nice to work with compared to some obscure areas. > Greg Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 7:50:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7635214FC8 for ; Mon, 28 Jun 1999 07:50:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 1C4DD82; Mon, 28 Jun 1999 22:50:18 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey , Kirk McKusick , Matthew Dillon , Alan Cox , Julian Elischer , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Mon, 28 Jun 1999 21:49:48 +0800." <19990628134948.ADBA882@overcee.netplex.com.au> Date: Mon, 28 Jun 1999 22:50:18 +0800 From: Peter Wemm Message-Id: <19990628145018.1C4DD82@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: [..] > Also, the swap IO clustering/chainging etc is troubled since it turns on > and off B_ASYNC and does it's own freeing and waiting. I haven't got my > brain around it yet but I don't think it's going to be too hard to fix. [..] This is a false alarm, it's not directly swapping related, it affects swap backed vn devices only. (ie: vm_pager_strategy() is only called from the vn device backend) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 8:22:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5B37214D96 for ; Mon, 28 Jun 1999 08:22:21 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA34530; Mon, 28 Jun 1999 11:22:03 -0400 (EDT) Message-Id: <199906281522.LAA34530@cs.rpi.edu> To: Julian Elischer Cc: Tom Bartol , Andrew Gallatin , dillon@backplane.com, freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: NFS Test patch.. Anyone tested it? In-Reply-To: Message from Julian Elischer of "Tue, 22 Jun 1999 14:00:41 PDT." Date: Mon, 28 Jun 1999 11:22:03 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today is a schedulued power outage at RPI. I am going to take this opportunity to install Matt's backported (to -STABLE) NFS patches on our primary NFS server. This is the first real chance we have had to put these under real-world load. As another datapoint, everything will be mounting this server NFSv3 r/w for home directories... Irix6/Solaris2.6/FreeBSD3.0-4.0. This should be an excellent test :) Currently under my home-grown NFS patches the machine has been up 11 days :) -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 8:27:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 7221C14D96 for ; Mon, 28 Jun 1999 08:27:24 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA17764; Mon, 28 Jun 1999 11:26:36 -0400 (EDT) (envelope-from luoqi) Date: Mon, 28 Jun 1999 11:26:36 -0400 (EDT) From: Luoqi Chen Message-Id: <199906281526.LAA17764@lor.watermarkgroup.com> To: bde@zeta.org.au, brdean@mindspring.com, freebsd-current@FreeBSD.ORG Subject: Re: kernel panic w/regard to setting io permissions bitmap Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is > >>0x20, which indexes to what appears to be a busy tss (type=01011b) > >>with a limit of 0x67. That instruction generates a general protection > >>fault with an error code of 0. The current process was Idle. > > The busy tss seems to be the only problem. The busy bit in the tss > descriptor should be clear when the ltr instruction is executed, because > the descriptor has just been copied from an image whose busy bit is clear. > This was broken in rev.1.332 of machdep.c by moving the initialisation > of common_tssd to after the first ltr instruction, so that the busy bit > in common_tssd is set. > > Bruce > > diff -c2 machdep.c~ machdep.c > *** machdep.c~ Sat Jun 26 21:41:33 1999 > --- machdep.c Sun Jun 27 15:52:07 1999 > *************** > *** 1643,1651 **** > common_tss.tss_ss0 = GSEL(GDATA_SEL, SEL_KPL) ; > common_tss.tss_ioopt = (sizeof common_tss) << 16; > - gsel_tss = GSEL(GPROC0_SEL, SEL_KPL); > - ltr(gsel_tss); > - private_tss = 0; > tss_gdt = &gdt[GPROC0_SEL].sd; > common_tssd = *tss_gdt; > > dblfault_tss.tss_esp = dblfault_tss.tss_esp0 = dblfault_tss.tss_esp1 = > --- 1643,1651 ---- > common_tss.tss_ss0 = GSEL(GDATA_SEL, SEL_KPL) ; > common_tss.tss_ioopt = (sizeof common_tss) << 16; > tss_gdt = &gdt[GPROC0_SEL].sd; > common_tssd = *tss_gdt; > + private_tss = 0; > + gsel_tss = GSEL(GPROC0_SEL, SEL_KPL); > + ltr(gsel_tss); > > dblfault_tss.tss_esp = dblfault_tss.tss_esp0 = dblfault_tss.tss_esp1 = > Yes, it was my mistake, I'll fix it. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 8:38:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (Postfix) with ESMTP id B922214DA6; Mon, 28 Jun 1999 08:38:11 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18397.on.bellglobal.com [206.172.130.77]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id LAA08545; Mon, 28 Jun 1999 11:41:09 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id LAA46590; Mon, 28 Jun 1999 11:38:39 -0400 (EDT) (envelope-from tim) Date: Mon, 28 Jun 1999 11:38:38 -0400 From: Tim Vanderhoek To: Satoshi - Ports Wraith - Asami Cc: obrien@NUXI.com, current@freebsd.org Subject: Re: **HEADS UP** newsyslog.conf syntax change Message-ID: <19990628113838.A18220@mad> References: <19990627201956.A1998@dragon.nuxi.com> <199906280937.CAA51900@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199906280937.CAA51900@silvia.hip.berkeley.edu>; from Satoshi - Ports Wraith - Asami on Mon, Jun 28, 1999 at 02:37:50AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jun 28, 1999 at 02:37:50AM -0700, Satoshi - Ports Wraith - Asami wrote: > * > * On your next ``make world'', you will need to change any "user.group" > * specifications in /etc/newsyslog.conf to "user:group". > > Please first change it to accept both syntaxes, with a warning in the > manpage that the old one will go away in the future. Then remove the And modify newsyslog in -stable so that it will accept both syntaxes. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 9: 7: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5A0C415143; Mon, 28 Jun 1999 09:07:03 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id JAA19630; Mon, 28 Jun 1999 09:06:55 -0700 (PDT) Date: Mon, 28 Jun 1999 09:06:54 -0700 (PDT) From: Julian Elischer To: Kirk McKusick Cc: Matthew Dillon , Alan Cox , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate reeplying to myself, especially when it's to tell me that I'm an idiot.. I just realised (i think) that what I suggest below is exactly what you are doing... julian On Mon, 28 Jun 1999, Julian Elischer wrote: > > > On Sun, 27 Jun 1999, Kirk McKusick wrote: > > > I see that Peter has already committed it. > > > > On the subject of BUF_KERNPROC, this must be done as I have coded > > it, not later in biodone. The problem is when the filesystem does > > a readahead. It starts the I/O on the buffer that it really wants, > > then starts ASYNC reads on the readahead buffers. When it finishes > > with the buffer that it wanted and the application enters the kernel > > to get the next buffer, the filesystem will attempt to lock the > > buffer on which it earlier initiated the read. If the I/O has not > > yet finished one of two bad things will happen. If the lock is not > > recursive, it will panic with `locking against myself' since it will > > hold the lock from the time when it initiated the readahead. If > > recursive locking is allowed, then it will get the buffer (since > > it holds the exclusive lock) and use it before it has been filled. > > So, it is semantically important that ASYNC read buffers be disowned > > (i.e., given to the kernel) at the time they are created. That way, > > only the kernel can access the buffer until the read I/O is done. > > I agree that this code is ugly, but it is necessary. > > > > One solution to the "locking against self" probelm with read-ahead > buffers would be to give some other entity the ownership of the read-ahead. > I would consider even having a separate ID for async operations > (the asyncd kermnel thread?) Possibly they could simply be assigned to > an existing PID (we have several to chose from .. pagedaemon, > syncer or vmdaemon) > > I mean the requesting process isn't really actually requesting the > lookahead, so it should be up to the entity that DID request it > (the kernel?) to lock the buffers. I think that whenever you > try make something appear as something that it is not you complicate > the picture. In this case we are tryin g to make it look as if that process > was responsible for the readahead requests, when in actual fact, it is > another entity taking it upon itself to make that decision, and see where > it gets us? > > > 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 Mon Jun 28 9: 9:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 24C951526D for ; Mon, 28 Jun 1999 09:08:26 -0700 (PDT) (envelope-from netchild@Vodix.CS.Uni-SB.de) Received: from work.net.local (maxtnt-031.telip.uni-sb.de [134.96.70.158]) by uni-sb.de (8.9.3/1999031900) with ESMTP id SAA24772 for ; Mon, 28 Jun 1999 18:08:22 +0200 (CEST) X-Authentication-Warning: uni-sb.de: Host maxtnt-031.telip.uni-sb.de [134.96.70.158] claimed to be work.net.local Received: from Vodix.CS.Uni-SB.de (localhost.net.local [127.0.0.1]) by work.net.local (8.9.3/8.9.3) with ESMTP id RAA00494 for ; Mon, 28 Jun 1999 17:39:08 +0200 (CEST) (envelope-from netchild@Vodix.CS.Uni-SB.de) Message-Id: <199906281539.RAA00494@work.net.local> Date: Mon, 28 Jun 1999 17:39:06 +0200 (CEST) From: A.Leidinger@WJPServer.CS.Uni-SB.de Subject: Panic with savecore (and bug with fsck) To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, after 4 crashes in 1 hour without a panic I've got a trace, but it's a trace from a panic produced by "savecore". I didn't think the 4 crashes are related to this trace. I was only able to reboot after commenting savecore in /etc/rc. Btw. after aborting fsck (+) I've got: fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. The world (and kernel) is from a cvsup around Sunday 2am (CEST). ok, here's the trace: ---snip--- checking for core dump... panic: lockmgr: pid -2, not exclusive lock holder 173 unlocking Debugger("panic") stopped at Debugger+0x39: movl $0,in_Debugger db> trace Fatal trap 12: page fault ... fault virtual address = 0x2 fault code = supervisor read, page not present instruction pointer = 0x8:0xc021f080 stack pointer = 0x10:0xc02961d0 frame pointer = 0x10:0x6 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 = Idle interrupt mask = bio kernel: type 12 trap, code 0 ---snip--- dmesg (verbose output available): ---snip--- Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #23: Sun Jun 27 14:04:30 CEST 1999 root@work.net.local:/usr/src/sys/compile/WORK Timecounter "i8254" frequency 1193270 Hz CPU: Pentium II (267.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 67096576 (65524K bytes) config> pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 5 avail memory = 61399040 (59960K bytes) Preloaded elf kernel "kernel" at 0xc037b000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037b09c. Preloaded elf module "vesa.ko" at 0xc037b0ec. Preloaded elf module "cd9660.ko" at 0xc037b188. Preloaded elf module "kernfs.ko" at 0xc037b228. Preloaded elf module "mfs.ko" at 0xc037b2c8. Preloaded elf module "msdos.ko" at 0xc037b364. Preloaded elf module "null.ko" at 0xc037b404. Preloaded elf module "procfs.ko" at 0xc037b4a0. Preloaded elf module "joy.ko" at 0xc037b540. link_elf: symbol lkmexists undefined VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc0346ea2 (1000022) VESA: Matrox Graphics Inc. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS version 1.2 pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 ide_pci0: at device 4.1 on pci0 uhci0: irq 9 at device 4.2 on pci0 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: irq 9 at device 6.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ed0: irq 15 at device 10.0 on pci0 ed0: address 00:80:ad:40:bd:e7, type NE2000 (16 bit) vga-pci0: irq 11 at device 12.0 on pci0 isa0: on motherboard atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x6 on isa0 sc0: VGA <16 virtual consoles, flags=0x206> wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, intr, iordi s wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x20010 on isa0 sio0: type ST16650A sio1 at port 0x2e8-0x2ef irq 10 flags 0x20000 on isa0 sio1: type ST16650A pca0 at port 0x40 on isa0 pca0: PC speaker audio driver isic0 at port 0x300 irq 3 flags 0x4 on isa0 isic0: AVM A1 or AVM Fritz!Card isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x16e0) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x6e0, AddrB=0xee0) ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 i4btrc: 2 ISDN trace device(s) attached i4brbch: 2 raw B channel access device(s) attached i4btel: 1 ISDN telephony interface device(s) attached i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4bctl: ISDN system control port attached i4bisppp: 2 ISDN SyncPPP device(s) attached i4b: ISDN call control device attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry ds0 XXX: driver didn't set ifq_maxlen IP Filter: initialized. Default = pass all, Logging = enabled Waiting 7 seconds for SCSI devices to settle changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C) cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present ---snip--- I try to reproduce one of the mentioned 4 crashes without a panic with a recent -current. In case you need more informations I make a backup of /usr/src and /kernel. Bye, Alexander. -- Columbus had a fourth ship. It sailed over the edge. http://netchild.home.pages.de A.Leidinger+Home @ WJPServer.CS.Uni-SB.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 9:10:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id 4446F15143; Mon, 28 Jun 1999 09:10:43 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id EAA02335; Mon, 28 Jun 1999 04:54:08 -0700 (PDT) Message-Id: <199906281154.EAA02335@flamingo.McKusick.COM> To: Julian Elischer Subject: Re: Found the startup panic - ccd ( patch included ) Cc: Matthew Dillon , Alan Cox , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey In-reply-to: Your message of "Mon, 28 Jun 1999 01:21:21 PDT." Date: Mon, 28 Jun 1999 04:54:07 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Mon, 28 Jun 1999 01:21:21 -0700 (PDT) From: Julian Elischer To: Kirk McKusick cc: Matthew Dillon , Alan Cox , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-Reply-To: <199906280347.UAA01061@flamingo.McKusick.COM> On Sun, 27 Jun 1999, Kirk McKusick wrote: > I see that Peter has already committed it. > > On the subject of BUF_KERNPROC, this must be done as I have coded > it, not later in biodone. The problem is when the filesystem does > a readahead. It starts the I/O on the buffer that it really wants, > then starts ASYNC reads on the readahead buffers. When it finishes > with the buffer that it wanted and the application enters the kernel > to get the next buffer, the filesystem will attempt to lock the > buffer on which it earlier initiated the read. If the I/O has not > yet finished one of two bad things will happen. If the lock is not > recursive, it will panic with `locking against myself' since it will > hold the lock from the time when it initiated the readahead. If > recursive locking is allowed, then it will get the buffer (since > it holds the exclusive lock) and use it before it has been filled. > So, it is semantically important that ASYNC read buffers be disowned > (i.e., given to the kernel) at the time they are created. That way, > only the kernel can access the buffer until the read I/O is done. > I agree that this code is ugly, but it is necessary. > One solution to the "locking against self" probelm with read-ahead buffers would be to give some other entity the ownership of the read-ahead. I would consider even having a separate ID for async operations (the asyncd kermnel thread?) Possibly they could simply be assigned to an existing PID (we have several to chose from .. pagedaemon, syncer or vmdaemon) I mean the requesting process isn't really actually requesting the lookahead, so it should be up to the entity that DID request it (the kernel?) to lock the buffers. I think that whenever you try make something appear as something that it is not you complicate the picture. In this case we are tryin g to make it look as if that process was responsible for the readahead requests, when in actual fact, it is another entity taking it upon itself to make that decision, and see where it gets us? julian The BUF_KERNPROC does exactly what you are talking about. It says take this buffer and give it away to the kernel. It is assigned the "kernel" pid so that it will not be accessible to the process that initiated it until it is released by the kernel. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 9:57:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 44DD514CE2 for ; Mon, 28 Jun 1999 09:57:40 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E590283; Tue, 29 Jun 1999 00:57:38 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Kirk McKusick Cc: Julian Elischer , Matthew Dillon , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Mon, 28 Jun 1999 04:54:07 MST." <199906281154.EAA02335@flamingo.McKusick.COM> Date: Tue, 29 Jun 1999 00:57:38 +0800 From: Peter Wemm Message-Id: <19990628165738.E590283@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote: [..] I've been tinkering around for a while and think I have at least a partial fix for the remaining problems. Certain places use B_CALL and have biodone() from the b_iodone routine, so we can't reliably use B_ASYNC as an indicator of needing to reassign to LK_KERNPROC. We have to do it on a case-by-case basis. It's easier to do cluster_head processing at the point it's gathered rather than in BUF_KERNPROC(). vfs_cluster.c is confusing, but I think I've figured out how to get it right. I'm not 100% sure about checking for B_CALL in both cases prior to VOP_STRATEGY(), and maybe reqbp needs to be considered for the first read in cluster_read(). Also, I think the inline BUF_*() routines/macros would be better as routines in something like vfs_bio.c as the internals cause problems with prototypes etc. I think this patch fixes the remaining panics in pageouts and clustering. Index: kern/vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.218 diff -u -r1.218 vfs_bio.c --- vfs_bio.c 1999/06/28 15:32:10 1.218 +++ vfs_bio.c 1999/06/28 16:48:53 @@ -517,7 +517,8 @@ if (curproc != NULL) curproc->p_stats->p_ru.ru_oublock++; splx(s); - BUF_KERNPROC(bp); + if (oldflags & B_ASYNC) + BUF_KERNPROC(bp); VOP_STRATEGY(bp->b_vp, bp); /* Index: kern/vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.84 diff -u -r1.84 vfs_cluster.c --- vfs_cluster.c 1999/06/26 02:46:08 1.84 +++ vfs_cluster.c 1999/06/28 16:48:53 @@ -252,7 +252,8 @@ if ((bp->b_flags & B_CLUSTER) == 0) vfs_busy_pages(bp, 0); bp->b_flags &= ~(B_ERROR|B_INVAL); - BUF_KERNPROC(bp); + if (bp->b_flags & (B_ASYNC|B_CALL)) + BUF_KERNPROC(bp); error = VOP_STRATEGY(vp, bp); curproc->p_stats->p_ru.ru_inblock++; } @@ -286,7 +287,8 @@ if ((rbp->b_flags & B_CLUSTER) == 0) vfs_busy_pages(rbp, 0); rbp->b_flags &= ~(B_ERROR|B_INVAL); - BUF_KERNPROC(rbp); + if (rbp->b_flags & (B_ASYNC|B_CALL)) + BUF_KERNPROC(rbp); (void) VOP_STRATEGY(vp, rbp); curproc->p_stats->p_ru.ru_inblock++; } @@ -414,6 +416,11 @@ break; } } + /* + * XXX fbp from caller may not be B_ASYNC, but we are going + * to biodone() it in cluster_callback() anyway + */ + BUF_KERNPROC(tbp); TAILQ_INSERT_TAIL(&bp->b_cluster.cluster_head, tbp, b_cluster.cluster_entry); for (j = 0; j < tbp->b_npages; j += 1) { @@ -788,6 +795,7 @@ reassignbuf(tbp, tbp->b_vp); /* put on clean list */ ++tbp->b_vp->v_numoutput; splx(s); + BUF_KERNPROC(tbp); TAILQ_INSERT_TAIL(&bp->b_cluster.cluster_head, tbp, b_cluster.cluster_entry); } Index: sys/buf.h =================================================================== RCS file: /home/ncvs/src/sys/sys/buf.h,v retrieving revision 1.73 diff -u -r1.73 buf.h --- buf.h 1999/06/27 11:40:03 1.73 +++ buf.h 1999/06/28 16:48:53 @@ -315,17 +315,8 @@ static __inline void BUF_KERNPROC(struct buf *bp) { - struct buf *nbp; - int s; - s = splbio(); - if (bp->b_flags & B_ASYNC) - bp->b_lock.lk_lockholder = LK_KERNPROC; - for (nbp = TAILQ_FIRST(&bp->b_cluster.cluster_head); - nbp; nbp = TAILQ_NEXT(&nbp->b_cluster, cluster_entry)) - if (nbp->b_flags & B_ASYNC) - nbp->b_lock.lk_lockholder = LK_KERNPROC; - splx(s); + bp->b_lock.lk_lockholder = LK_KERNPROC; } /* * Find out the number of references to a lock. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 10:35:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8B47C1539D for ; Mon, 28 Jun 1999 10:35:40 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA23042; Mon, 28 Jun 1999 10:35:21 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 10:35:21 -0700 (PDT) From: Matthew Dillon Message-Id: <199906281735.KAA23042@apollo.backplane.com> To: Peter Wemm Cc: Kirk McKusick , Julian Elischer , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <19990628165738.E590283@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Certain places use B_CALL and have biodone() from the b_iodone routine, :so we can't reliably use B_ASYNC as an indicator of needing to reassign :to LK_KERNPROC. We have to do it on a case-by-case basis. : :It's easier to do cluster_head processing at the point it's gathered :rather than in BUF_KERNPROC(). : :vfs_cluster.c is confusing, but I think I've figured out how to get it :right. I'm not 100% sure about checking for B_CALL in both cases prior :to VOP_STRATEGY(), and maybe reqbp needs to be considered for the first :... There has got to be a better way to do this. This is unbelievably messy. Please, guys. I am all for stabilizing what was committed but I just spent a month removing fragility from the buffer cache code, and this is adding it right back in. This stuff is just too fragile. Even if we fix it now, it is only going to cause serious problems in the future. It looks to me that these hacks exist to get around potential problems with exclusive lock recursion. We are not *doing* any exclusive lock recursion right now. I am fairly confident that Kirk can implement the new softupdates-related elements without having to resort to exclusive lock recursion, with only a little thought on the matter. Can we please get rid of the lock reassign junk that only exists to support exclusive lock recusion and instead go with something simpler? That way we can remove all of these BUF_KERNPROC calls which have been strewn all over the code. We have the luxury of time here, can we please do this implementation right instead of rushing through making design mistakes? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 10:56:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id 5776F15483; Mon, 28 Jun 1999 10:56:47 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id GAA02414; Mon, 28 Jun 1999 06:38:33 -0700 (PDT) Message-Id: <199906281338.GAA02414@flamingo.McKusick.COM> To: Matthew Dillon Subject: Re: Found the startup panic - ccd ( patch included ) Cc: Alan Cox , Julian Elischer , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey In-reply-to: Your message of "Mon, 28 Jun 1999 01:28:29 PDT." <199906280828.BAA18365@apollo.backplane.com> Date: Mon, 28 Jun 1999 06:38:25 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are proposing replacing the current buffer locks with two separate locks, one for ownership and the other for I/O. Frankly, I do not find this simpler or easier to understand than what we have now. I also take some issue with the cost of the lockmgr code. It is large, but the critical paths through it are pretty short (it was derived from the MACH lock code which had been pretty well tuned). There is some long and hairy stuff in there like draining locks. But if you intend to have locks in malloced memory, you must have a way to ensure that all references go away before you deallocate it. And while long and nasty, that code is (hopefully) not executed terribly frequently. I will also note that adding the surrounding splbio/splx to all the BUF_ macros nearly doubled the cycle count on those functions. As nearly every instance is already splbio protected (since the B_BUSY and B_WANTED code also required protection to avoid races), it would make a big performance improvement to just go make sure that all the BUF_ calls are already protected rather than needlessly add those splbio and splx calls. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 11:14:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 99C3415455; Mon, 28 Jun 1999 11:14:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA23384; Mon, 28 Jun 1999 11:14:09 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 11:14:09 -0700 (PDT) From: Matthew Dillon Message-Id: <199906281814.LAA23384@apollo.backplane.com> To: Kirk McKusick Cc: Alan Cox , Julian Elischer , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <199906281338.GAA02414@flamingo.McKusick.COM> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :You are proposing replacing the current buffer locks with two separate :locks, one for ownership and the other for I/O. Frankly, I do not find :this simpler or easier to understand than what we have now. I also The simplicity that I am requesting is that we do not add all these BUF_KERNPROC calls all over the code base. I am requesting that we find a solution that does not require that, because the way the BUF_KERNPROC stuff is being now is extremely fragile, unnecessarily changes the VOP API by requiring yet another precondition, and has already caused us significant problems. If the only people who can track down and fix these problems are you, me, and Peter, then what is going to happen when someone else tries to do something with the VFS subsystem later on? The solution can be as simple as encapsulating it as part of something else that is already part of the buffer subsystem. If we can remove those calls from the device drivers I will be much happier. How are we supposed to be able to extend the code when we continue to add pre-conditions to VOP_*() calls? I don't like the idea even if proper documentation were adding. At the moment your commit contains a lot of hacks to handle situations that have not yet occured. I understand why you are doing it... you believe that the situations will occur when you implement the softupdates portion of the changes. But I do not think adding those hacks now is a good idea. I would rather that some additional thought be put into the lock recursion you intended for softupdates in order to make these hacks not-necessary. :take some issue with the cost of the lockmgr code. It is large, but :the critical paths through it are pretty short (it was derived from :the MACH lock code which had been pretty well tuned). There is some It is not short. I've measured it. lockmgr() locks are so expensive that using them in the critical path at all is creating a serious performance problem for us. Even things like namei() calls would more then double in speed if we could reduce the overhead of the lockmgr() calls. The qlock's are about 10 times faster then the lockmgr() locks, possibly even more. It's that bad. :I will also note that adding the surrounding splbio/splx to all the :BUF_ macros nearly doubled the cycle count on those functions. As :nearly every instance is already splbio protected (since the B_BUSY :and B_WANTED code also required protection to avoid races), it would :make a big performance improvement to just go make sure that all the :BUF_ calls are already protected rather than needlessly add those splbio :and splx calls. : : Kirk I agree with you there. I don't think the splbio*() calls are really an issue from a design standpoint because the problem is encapsulated... it exists is only one place, the macro in sys/buf.h. Given the choice betwen a hack that exists in one place ( the splbio*() stuff ), and a hack that is strewn all over the codebase ( the BUF_KERNPROC() stuff ), I'll take the hack that exists in one place every time. I would also like to point out that none of these side effects or prerequisits have been documented at al.. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 11:20:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 80E9914C15; Mon, 28 Jun 1999 11:20:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA23440; Mon, 28 Jun 1999 11:20:02 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 11:20:02 -0700 (PDT) From: Matthew Dillon Message-Id: <199906281820.LAA23440@apollo.backplane.com> To: Kirk McKusick Cc: Alan Cox , Julian Elischer , Mike Smith , Peter Wemm , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <199906281338.GAA02414@flamingo.McKusick.COM> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :and B_WANTED code also required protection to avoid races), it would :make a big performance improvement to just go make sure that all the :BUF_ calls are already protected rather than needlessly add those splbio :and splx calls. : : Kirk Not as big as removing the lockmgr() code and replacing it with something more efficient. Do you realize that the change from B_BUSY to lockmgr() in the getnewbuf() has halved its loop performance? 8 subroutine calls have been indirectly added to the core loop. Eight! And none of them trivial. The serial counter you added halved it again. The loop performance is now 1/4 what it was before, which means that every time getnewbuf() cannot find a new buffer at the beginning of its scan its inefficiencies are compounded 4x per element. I spent a lot of time working on getnewbuf()'s performance and all those gains have now been erased. Look, I agree that we needed to change the B_BUSY stuff to some sort of new locking system, but that doesn't mean we have to throw the kitchen sink in along with it! And it doesn't mean that we have to create a mess in the code just to support certain essentricies that I am almost certain we can do without. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 13:20:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id 2CEEE14BCF for ; Mon, 28 Jun 1999 13:20:24 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id IAA02733; Mon, 28 Jun 1999 08:59:39 -0700 (PDT) Message-Id: <199906281559.IAA02733@flamingo.McKusick.COM> To: Matthew Dillon Subject: Re: Found the startup panic - ccd ( patch included ) Cc: Peter Wemm , Julian Elischer , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey In-reply-to: Your message of "Mon, 28 Jun 1999 10:35:21 PDT." <199906281735.KAA23042@apollo.backplane.com> Date: Mon, 28 Jun 1999 08:59:38 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Mon, 28 Jun 1999 10:35:21 -0700 (PDT) From: Matthew Dillon To: Peter Wemm Cc: Kirk McKusick , Julian Elischer , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <19990628165738.E590283@overcee.netplex.com.au> :Certain places use B_CALL and have biodone() from the b_iodone routine, :so we can't reliably use B_ASYNC as an indicator of needing to reassign :to LK_KERNPROC. We have to do it on a case-by-case basis. : :It's easier to do cluster_head processing at the point it's gathered :rather than in BUF_KERNPROC(). : :vfs_cluster.c is confusing, but I think I've figured out how to get it :right. I'm not 100% sure about checking for B_CALL in both cases prior :to VOP_STRATEGY(), and maybe reqbp needs to be considered for the first :... There has got to be a better way to do this. This is unbelievably messy. Please, guys. I am all for stabilizing what was committed but I just spent a month removing fragility from the buffer cache code, and this is adding it right back in. This stuff is just too fragile. Even if we fix it now, it is only going to cause serious problems in the future. It looks to me that these hacks exist to get around potential problems with exclusive lock recursion. We are not *doing* any exclusive lock recursion right now. I am fairly confident that Kirk can implement the new softupdates-related elements without having to resort to exclusive lock recursion, with only a little thought on the matter. Can we please get rid of the lock reassign junk that only exists to support exclusive lock recusion and instead go with something simpler? That way we can remove all of these BUF_KERNPROC calls which have been strewn all over the code. We have the luxury of time here, can we please do this implementation right instead of rushing through making design mistakes? -Matt You are right that the buffer cache is very tricky. It is hard to change it in ways that preserves functionality and performance. The port of my buffer locking code from BSD/OS has caused problems largely because of a different buffer cache implementation and especially SMP models between the two systems (BSD/OS has no spl's for example). However, this is not a half baked idea that I have come up with and thrown in without thinking. Recursive locking is *required* to get stacking filesystems like union and loopback working reliably. As they currently stand they are full of code to try and track locks at layers all up and down the stack. This code is really nasty and in many cases broken (leading to deadlocks or crashes). The snapshot code also is most easily implemented with recursive locking, the alternative being to put lock monitoring all through bmap and block allocation code. So yes, it would be wonderful if the world could be simple, and I am not a huge fan of the complexity of the buffer locking code. But, I have considered the alternatives and they are worse. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 13:37:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1]) by hub.freebsd.org (Postfix) with ESMTP id 525F515161 for ; Mon, 28 Jun 1999 13:36:59 -0700 (PDT) (envelope-from crawdad@gungnir.fnal.gov) Received: from gungnir.fnal.gov (localhost [127.0.0.1]) by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA08888; Mon, 28 Jun 1999 15:36:46 -0500 (CDT) Message-Id: <199906282036.PAA08888@gungnir.fnal.gov> To: Warner Losh Cc: current@FreeBSD.ORG From: "Matt Crawford" Subject: Re: HEADS UP: PAO3 branch goes into the tree In-reply-to: Your message of Thu, 17 Jun 1999 17:58:36 MDT. <199906172358.RAA08930@harmony.village.org> Date: Mon, 28 Jun 1999 15:36:46 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The PAO3 changes to FreeBSD 3.2 are about to be integrated into the > FreeBSD CVS repository as its own branch off RELENG_3. itojin-san and > the other nomads reached this agreement with -core at Usenix. Warner didn't mention any other list to report problems to, but I just cvsup'd this morning and checked out RELENG_3_2_PAO. "make buildworld" died at usr.sbin/wicontrol/wicontrol.c, for lack of and ensuing errors. The file is present under the RELENG_3 tag, though. Matt Crawford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 13:37:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from web118.yahoomail.com (web118.yahoomail.com [205.180.60.99]) by hub.freebsd.org (Postfix) with SMTP id 25C3015483 for ; Mon, 28 Jun 1999 13:37:20 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990628203830.21074.rocketmail@web118.yahoomail.com> Received: from [147.226.112.101] by web118.yahoomail.com; Mon, 28 Jun 1999 13:38:30 PDT Date: Mon, 28 Jun 1999 13:38:30 -0700 (PDT) From: "Valentin S. Chopov" Subject: MAX_PERF To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is MAX_PERF option? It's in sys/i386/i386/pmap.c, sys/kern/kern_lock.c, sys/vm/swap_pager.c and others. Thanx, Val _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 13:38:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 25F9F15157 for ; Mon, 28 Jun 1999 13:38:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA24584; Mon, 28 Jun 1999 13:38:07 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 13:38:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199906282038.NAA24584@apollo.backplane.com> To: Kirk McKusick Cc: Peter Wemm , Julian Elischer , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: <199906281559.IAA02733@flamingo.McKusick.COM> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :You are right that the buffer cache is very tricky. It is hard to :change it in ways that preserves functionality and performance. :The port of my buffer locking code from BSD/OS has caused problems :largely because of a different buffer cache implementation and :especially SMP models between the two systems (BSD/OS has no spl's :for example). However, this is not a half baked idea that I have :come up with and thrown in without thinking. Recursive locking is :*required* to get stacking filesystems like union and loopback :working reliably. As they currently stand they are full of code to :try and track locks at layers all up and down the stack. This code :is really nasty and in many cases broken (leading to deadlocks or :crashes). The snapshot code also is most easily implemented with :recursive locking, the alternative being to put lock monitoring :all through bmap and block allocation code. So yes, it would be :wonderful if the world could be simple, and I am not a huge fan of :the complexity of the buffer locking code. But, I have considered :the alternatives and they are worse. : : Kirk Wow! Timeout! Miscommunication. I am talking strictly about struct buf locking. I understand and agree completely that recursive locking is absolutely necessary for the VFS layering! I am not throwing your work out - precisely the opposite, I want to keep your work pretty much as is except for two things: (1) I want to replace lockmgr locks ( and I don't mind implementing recursive exclusive locking in the replacement, though I would rather avoid it! ), and (2) I want to find a better way to implement the BUF_KERNPROC() stuff... basically I want to try to find a way to localize the necessary effect in one place in the code rather then have the BUF_KERNPROC() macros strewn all over the code. Same effect, slightly different code organization, that's all. There must be a choke point somewhere where we can put the code. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 13:54:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D202914E90 for ; Mon, 28 Jun 1999 13:54:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA93641; Mon, 28 Jun 1999 14:54:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA16685; Mon, 28 Jun 1999 14:52:45 -0600 (MDT) Message-Id: <199906282052.OAA16685@harmony.village.org> To: "Matt Crawford" Subject: Re: HEADS UP: PAO3 branch goes into the tree Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Jun 1999 15:36:46 CDT." <199906282036.PAA08888@gungnir.fnal.gov> References: <199906282036.PAA08888@gungnir.fnal.gov> Date: Mon, 28 Jun 1999 14:52:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906282036.PAA08888@gungnir.fnal.gov> "Matt Crawford" writes: : Warner didn't mention any other list to report problems to, but : I just cvsup'd this morning and checked out RELENG_3_2_PAO. : "make buildworld" died at usr.sbin/wicontrol/wicontrol.c, for : lack of and ensuing errors. : : The file is present under the RELENG_3 tag, though. I didn't mention it because it didn't break. It works for me. What are your configuration parameters in /etc/make.conf. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:19:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 119A9153FF for ; Mon, 28 Jun 1999 14:19:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA24818; Mon, 28 Jun 1999 14:19:15 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 14:19:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199906282119.OAA24818@apollo.backplane.com> To: "Valentin S. Chopov" Cc: current@FreeBSD.ORG Subject: Re: MAX_PERF References: <19990628203830.21074.rocketmail@web118.yahoomail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :What is MAX_PERF option? :It's in sys/i386/i386/pmap.c, sys/kern/kern_lock.c, :sys/vm/swap_pager.c and others. : :Thanx, : :Val It stands for 'maximum performance'. If you set this option, the kernel will not bother making certain sanity checks within itself. Basically you should not set the option unless you need a really tiny kernel binary. It will not improve performance noticeably. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:22:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 77EAE15418 for ; Mon, 28 Jun 1999 14:22:25 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id RAA16390 for ; Mon, 28 Jun 1999 17:22:23 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA27314 for ; Mon, 28 Jun 1999 17:22:23 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA27310 for ; Mon, 28 Jun 1999 17:22:23 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 28 Jun 1999 17:22:22 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: lockmgr crashes... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to let someone know... I recently (a couple of hours ago) have been having a problem with kernel panics.... I tried to remake the world and the kernel panics saying: panic: lockmgr: then what follows is different every time... all I know is that it doesn't happen until the process number is in the 25000 range, and after this, the disks refuse to sync, and I have to push the reset button on my computer... Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:25:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1]) by hub.freebsd.org (Postfix) with ESMTP id C45881538C for ; Mon, 28 Jun 1999 14:25:26 -0700 (PDT) (envelope-from crawdad@gungnir.fnal.gov) Received: from gungnir.fnal.gov (localhost [127.0.0.1]) by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id QAA09213; Mon, 28 Jun 1999 16:25:17 -0500 (CDT) Message-Id: <199906282125.QAA09213@gungnir.fnal.gov> To: Warner Losh Cc: current@FreeBSD.ORG From: "Matt Crawford" Subject: Re: HEADS UP: PAO3 branch goes into the tree In-reply-to: Your message of Mon, 28 Jun 1999 14:52:45 MDT. <199906282052.OAA16685@harmony.village.org> Date: Mon, 28 Jun 1999 16:25:17 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Warner didn't mention any other list to report problems to, but... > : lack of and ensuing errors. > : The file is present under the RELENG_3 tag, though. > > I didn't mention it because it didn't break. It works for me. What > are your configuration parameters in /etc/make.conf. I never touched that file -- every line is still commented out. But I don't see how make.conf could check out a file from CVS for me that's missing in the source tree when I "make buildworld". "make update" would be different, but with a sticky RELENG_3_2_PAO tag, not much different. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:27:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id BAB6A1548E for ; Mon, 28 Jun 1999 14:26:25 -0700 (PDT) (envelope-from ncbp@freesbee.t.dk) Received: (qmail 11303 invoked by uid 1002); 28 Jun 1999 21:26:24 -0000 Date: Mon, 28 Jun 1999 23:26:24 +0200 From: "Niels Chr. Bank-Pedersen" To: current@FreeBSD.org Subject: panic after loading vinum Message-ID: <19990628232624.A11159@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the latest patches for vinum were commited I am getting a panic immediately after vinum has started. This is on a UP -current (as of today). --- changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present vinum: loaded Can't open history file /var/tmp/vinum_history: Read-only file system (30) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1 fault code = supervisor read, page not present instruction pointer = 0x8:0xc017b954 stack pointer = 0x10:0xc64c7d18 frame pointer = 0x10:0xc64c7d34 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 = 17 (vinum) interrupt mask = kernel: type 12 trap, code=0 Stopped at vn_lock+0x10: testb $0x1,0x1(%esi) db> trace vn_lock(0,20002,0,c09acc00,c09acce4) at vn_lock+0x10 _end(c09acc00,c09acc00,c09d56e0,c5,0) at 0xc09ce85b _end(c09acc00,0,4000e600,c64c7d94,c09d4980) at 0xc09ce82f _end(c64c7dac,c09d3461,c64c7e08,4000e600,c5afa4c0) at 0xc09d4890 _end(c64c7e08,4000e600,c5afa4c0,c64c7ecc,c64c7dd4) at 0xc09d4980 _end(4000e600,465d,c64c7ecc,3,c5afa4c0) at 0xc09d3461 spec_ioctl(c64c7e08,c64c7dec,c01e5d65,c64c7e08,c64c7e98) at spec_ioctl+0x40 spec_vnoperate(c64c7e08,c64c7e98,c017b89d,c64c7e08,c09c2800) at spec_vnoperate+0x15 ufs_vnoperatespec(c64c7e08,c09c2800,c09ad440,0,0) at ufs_vnoperatespec+0x15 vn_ioctl(c09ad440,465d,c64c7ecc,c5afa4c0,c5afa4c0) at vn_ioctl+0xdd ioctl(c5afa4c0,c64c7f80,2,bfbfde00,bfbfde0c) at ioctl+0x1ef syscall(2f,2f,2f,bfbfde0c,bfbfde00) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x30 db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 17 c5afa4c0 c64c6000 0 1 17 000004 2 vinum 15 c5afa780 c64bb000 0 5 5 004006 2 vinum 5 c5afa8e0 c64b8000 0 1 5 004086 3 wait c5afa8e0 sh 4 c5afaa40 c5b05000 0 0 0 000204 2 syncer 3 c5afaba0 c5b03000 0 0 0 000204 3 psleep c028d01c vmdaemon 2 c5afad00 c5b01000 0 0 0 000604 2 pagedaemon 1 c5afae60 c5aff000 0 0 1 004084 3 wait c5afae60 init 0 c02961a0 c02f8000 0 0 0 000204 3 sched c02961a0 swapper 16 c5afa620 c64c2000 0 15 5 002006 5 vinum db> Kernel configuration: machine i386 cpu I686_CPU ident HOME maxusers 16 #config kernel root on da0 options INET options FFS options NFS options CD9660 options FFS_ROOT options PROCFS #options MSDOSFS options COMPAT_43 options SCSI_DELAY=5000 options UCONSOLE options USERCONFIG options MAXCONS=4 #options VISUAL_USERCONFIG options SOFTUPDATES options NO_F00F_HACK options ICMP_BANDLIM options CLK_USE_TSC_CALIBRATION options COMPAT_LINUX options AHC_ALLOW_MEMIO options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE options VESA options SC_HISTORY_SIZE=1024 options XSERVER options DDB #options GDB_REMOTE_CHAT controller isa0 at nexus? controller pnp0 controller pci0 at nexus? controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? controller fdc0 at isa? port IO_FD1 irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device sa0 device cd0 device pass0 device pcm0 device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device ppc0 at isa? port? controller ppbus0 device lpt0 at ppbus? device xl0 pseudo-device loop pseudo-device ether pseudo-device pty 16 pseudo-device gzip pseudo-device bpfilter 4 pseudo-device splash Any clues? /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark NET, IP-section. "Hey, are any of you guys out there actually *using* RFC 1149?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:28: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id 8F8891538C for ; Mon, 28 Jun 1999 14:27:56 -0700 (PDT) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost.concentric.net [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id KAA02893; Mon, 28 Jun 1999 10:06:12 -0700 (PDT) Message-Id: <199906281706.KAA02893@flamingo.McKusick.COM> To: Peter Wemm Subject: Re: Found the startup panic - ccd ( patch included ) Cc: Julian Elischer , Matthew Dillon , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey In-reply-to: Your message of "Tue, 29 Jun 1999 00:57:38 +0800." <19990628165738.E590283@overcee.netplex.com.au> Date: Mon, 28 Jun 1999 10:06:10 -0700 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This looks correct to me. I originally had the BUF_KERNPROC macro just changing the target buffer, but then changed it to follow chains in the hopes of reducing the instances of its use. The way that you have used it below is much clearer and should definitely be put in. Also I hope that your fix to breadn will clear up Greg's problem with NFS. Kirk =-=-=-=-=-=-=-= To: Kirk McKusick Cc: Julian Elischer , Matthew Dillon , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Mon, 28 Jun 1999 04:54:07 MST." <199906281154.EAA02335@flamingo.McKusick.COM> Date: Tue, 29 Jun 1999 00:57:38 +0800 From: Peter Wemm Message-Id: <19990628165738.E590283@overcee.netplex.com.au> Kirk McKusick wrote: [..] I've been tinkering around for a while and think I have at least a partial fix for the remaining problems. Certain places use B_CALL and have biodone() from the b_iodone routine, so we can't reliably use B_ASYNC as an indicator of needing to reassign to LK_KERNPROC. We have to do it on a case-by-case basis. It's easier to do cluster_head processing at the point it's gathered rather than in BUF_KERNPROC(). vfs_cluster.c is confusing, but I think I've figured out how to get it right. I'm not 100% sure about checking for B_CALL in both cases prior to VOP_STRATEGY(), and maybe reqbp needs to be considered for the first read in cluster_read(). Also, I think the inline BUF_*() routines/macros would be better as routines in something like vfs_bio.c as the internals cause problems with prototypes etc. I think this patch fixes the remaining panics in pageouts and clustering. Index: kern/vfs_bio.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.218 diff -u -r1.218 vfs_bio.c --- vfs_bio.c 1999/06/28 15:32:10 1.218 +++ vfs_bio.c 1999/06/28 16:48:53 @@ -517,7 +517,8 @@ if (curproc != NULL) curproc->p_stats->p_ru.ru_oublock++; splx(s); - BUF_KERNPROC(bp); + if (oldflags & B_ASYNC) + BUF_KERNPROC(bp); VOP_STRATEGY(bp->b_vp, bp); /* Index: kern/vfs_cluster.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_cluster.c,v retrieving revision 1.84 diff -u -r1.84 vfs_cluster.c --- vfs_cluster.c 1999/06/26 02:46:08 1.84 +++ vfs_cluster.c 1999/06/28 16:48:53 @@ -252,7 +252,8 @@ if ((bp->b_flags & B_CLUSTER) == 0) vfs_busy_pages(bp, 0); bp->b_flags &= ~(B_ERROR|B_INVAL); - BUF_KERNPROC(bp); + if (bp->b_flags & (B_ASYNC|B_CALL)) + BUF_KERNPROC(bp); error = VOP_STRATEGY(vp, bp); curproc->p_stats->p_ru.ru_inblock++; } @@ -286,7 +287,8 @@ if ((rbp->b_flags & B_CLUSTER) == 0) vfs_busy_pages(rbp, 0); rbp->b_flags &= ~(B_ERROR|B_INVAL); - BUF_KERNPROC(rbp); + if (rbp->b_flags & (B_ASYNC|B_CALL)) + BUF_KERNPROC(rbp); (void) VOP_STRATEGY(vp, rbp); curproc->p_stats->p_ru.ru_inblock++; } @@ -414,6 +416,11 @@ break; } } + /* + * XXX fbp from caller may not be B_ASYNC, but we are going + * to biodone() it in cluster_callback() anyway + */ + BUF_KERNPROC(tbp); TAILQ_INSERT_TAIL(&bp->b_cluster.cluster_head, tbp, b_cluster.cluster_entry); for (j = 0; j < tbp->b_npages; j += 1) { @@ -788,6 +795,7 @@ reassignbuf(tbp, tbp->b_vp); /* put on clean list */ ++tbp->b_vp->v_numoutput; splx(s); + BUF_KERNPROC(tbp); TAILQ_INSERT_TAIL(&bp->b_cluster.cluster_head, tbp, b_cluster.cluster_entry); } Index: sys/buf.h =================================================================== RCS file: /home/ncvs/src/sys/sys/buf.h,v retrieving revision 1.73 diff -u -r1.73 buf.h --- buf.h 1999/06/27 11:40:03 1.73 +++ buf.h 1999/06/28 16:48:53 @@ -315,17 +315,8 @@ static __inline void BUF_KERNPROC(struct buf *bp) { - struct buf *nbp; - int s; - s = splbio(); - if (bp->b_flags & B_ASYNC) - bp->b_lock.lk_lockholder = LK_KERNPROC; - for (nbp = TAILQ_FIRST(&bp->b_cluster.cluster_head); - nbp; nbp = TAILQ_NEXT(&nbp->b_cluster, cluster_entry)) - if (nbp->b_flags & B_ASYNC) - nbp->b_lock.lk_lockholder = LK_KERNPROC; - splx(s); + bp->b_lock.lk_lockholder = LK_KERNPROC; } /* * Find out the number of references to a lock. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 14:30: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D0F1415480 for ; Mon, 28 Jun 1999 14:28:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA93794; Mon, 28 Jun 1999 15:28:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA16977; Mon, 28 Jun 1999 15:27:03 -0600 (MDT) Message-Id: <199906282127.PAA16977@harmony.village.org> To: "Matt Crawford" Subject: Re: HEADS UP: PAO3 branch goes into the tree Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Jun 1999 16:25:17 CDT." <199906282125.QAA09213@gungnir.fnal.gov> References: <199906282125.QAA09213@gungnir.fnal.gov> Date: Mon, 28 Jun 1999 15:27:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906282125.QAA09213@gungnir.fnal.gov> "Matt Crawford" writes: : I never touched that file -- every line is still commented out. But : I don't see how make.conf could check out a file from CVS for me : that's missing in the source tree when I "make buildworld". "make : update" would be different, but with a sticky RELENG_3_2_PAO tag, not : much different. /etc/make.conf is always used, no matter what. If your /etc/make.conf does have no real lines in it, I'm not sure what to tell you I'm doing a make world right now with nothing in my /etc/make.conf just to make sure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 15:30:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 233DD14E87 for ; Mon, 28 Jun 1999 15:30:37 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA94003; Mon, 28 Jun 1999 16:30:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA17482; Mon, 28 Jun 1999 16:29:01 -0600 (MDT) Message-Id: <199906282229.QAA17482@harmony.village.org> To: "Matt Crawford" Cc: current@freebsd.org Subject: Re: HEADS UP: PAO3 branch goes into the tree In-reply-to: Your message of "Mon, 28 Jun 1999 17:17:25 CDT." <199906282217.RAA09523@gungnir.fnal.gov> References: <199906282217.RAA09523@gungnir.fnal.gov> Date: Mon, 28 Jun 1999 16:29:01 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199906282217.RAA09523@gungnir.fnal.gov> "Matt Crawford" writes: : And I'm doing a new buildworld with a copy of the missing file : inserted into src/sys/i386/include by hand. It's suspicious that : if_wavelan_ieee.h has only one CVS tag on it (RELENG_3), and other : files in that directory have a dozen or so. Ahhhhhhhhhhhhhhhrrrrrrrrrrrrggggggggggg!!!!!!! For some reason this didn't get committed on that tag. I've corrected that problem.... It was in my tree, but I didn't check the tags... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 18:18:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 2CDF114EF8 for ; Mon, 28 Jun 1999 18:18:30 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id SAA51513; Mon, 28 Jun 1999 18:17:48 -0700 (PDT) Date: Mon, 28 Jun 1999 18:17:47 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@freebsd.org, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-Reply-To: <199906282038.NAA24584@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok hadn't seen this one when I sent the previous email.. Julian On Mon, 28 Jun 1999, Matthew Dillon wrote: > :You are right that the buffer cache is very tricky. It is hard to > :change it in ways that preserves functionality and performance. > :The port of my buffer locking code from BSD/OS has caused problems > :largely because of a different buffer cache implementation and > :especially SMP models between the two systems (BSD/OS has no spl's > :for example). However, this is not a half baked idea that I have > :come up with and thrown in without thinking. Recursive locking is > :*required* to get stacking filesystems like union and loopback > :working reliably. As they currently stand they are full of code to > :try and track locks at layers all up and down the stack. This code > :is really nasty and in many cases broken (leading to deadlocks or > :crashes). The snapshot code also is most easily implemented with > :recursive locking, the alternative being to put lock monitoring > :all through bmap and block allocation code. So yes, it would be > :wonderful if the world could be simple, and I am not a huge fan of > :the complexity of the buffer locking code. But, I have considered > :the alternatives and they are worse. > : > : Kirk > > Wow! Timeout! Miscommunication. > > I am talking strictly about struct buf locking. I understand and agree > completely that recursive locking is absolutely necessary for the > VFS layering! > > I am not throwing your work out - precisely the opposite, I want to keep > your work pretty much as is except for two things: (1) I want to replace > lockmgr locks ( and I don't mind implementing recursive exclusive locking > in the replacement, though I would rather avoid it! ), and (2) I want to > find a better way to implement the BUF_KERNPROC() stuff... basically I > want to try to find a way to localize the necessary effect in one place > in the code rather then have the BUF_KERNPROC() macros strewn all over the > code. Same effect, slightly different code organization, that's all. > > There must be a choke point somewhere where we can put the code. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 18:23: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from rmx07.globecomm.net (rmx07.iname.net [165.251.8.75]) by hub.freebsd.org (Postfix) with ESMTP id E941C14ED1; Mon, 28 Jun 1999 18:22:55 -0700 (PDT) (envelope-from davec@unforgettable.com) Received: from weba4.iname.net by rmx07.globecomm.net (8.9.1/8.8.0) with ESMTP id VAA10380 From: davec@unforgettable.com Received: (from root@localhost) by weba4.iname.net (8.9.1a/8.9.2.Alpha2) id VAA17925; Mon, 28 Jun 1999 21:22:54 -0400 (EDT) MIME-Version: 1.0 Message-Id: <990628212253RE.23230@weba4.iname.net> Date: Mon, 28 Jun 1999 21:22:53 -0400 (EDT) Content-Type: Text/Plain Content-Transfer-Encoding: 7bit To: majordomo@FreeBSD.ORG, FreeBSD-Current Mailing list Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-ports ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 19: 7:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5FBDB14F48 for ; Mon, 28 Jun 1999 19:06:58 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA21310; Tue, 29 Jun 1999 11:36:56 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA96942; Tue, 29 Jun 1999 09:43:34 +0930 (CST) Date: Tue, 29 Jun 1999 09:43:33 +0930 From: Greg Lehey To: "Niels Chr. Bank-Pedersen" Cc: FreeBSD current users Subject: Re: panic after loading vinum Message-ID: <19990629094333.A86806@freebie.lemis.com> References: <19990628232624.A11159@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990628232624.A11159@bank-pedersen.dk>; from Niels Chr. Bank-Pedersen on Mon, Jun 28, 1999 at 11:26:24PM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Monday, 28 June 1999 at 23:26:24 +0200, Niels Chr. Bank-Pedersen wrote: > Since the latest patches for vinum were commited I am getting a panic > immediately after vinum has started. This is on a UP -current (as of > today). > > --- > changing root device to da0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15) > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > da2 at ahc0 bus 0 target 8 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing > Enabled > da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > cd0 at ahc0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 4.237MB/s transfers (4.237MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > vinum: loaded > Can't open history file /var/tmp/vinum_history: Read-only file system > (30) > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x1 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc017b954 > stack pointer = 0x10:0xc64c7d18 > frame pointer = 0x10:0xc64c7d34 > 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 = 17 (vinum) > interrupt mask = > kernel: type 12 trap, code=0 > Stopped at vn_lock+0x10: testb $0x1,0x1(%esi) > db> trace > vn_lock(0,20002,0,c09acc00,c09acce4) at vn_lock+0x10 > _end(c09acc00,c09acc00,c09d56e0,c5,0) at 0xc09ce85b > _end(c09acc00,0,4000e600,c64c7d94,c09d4980) at 0xc09ce82f > _end(c64c7dac,c09d3461,c64c7e08,4000e600,c5afa4c0) at 0xc09d4890 > _end(c64c7e08,4000e600,c5afa4c0,c64c7ecc,c64c7dd4) at 0xc09d4980 > _end(4000e600,465d,c64c7ecc,3,c5afa4c0) at 0xc09d3461 > spec_ioctl(c64c7e08,c64c7dec,c01e5d65,c64c7e08,c64c7e98) at spec_ioctl+0x40 > spec_vnoperate(c64c7e08,c64c7e98,c017b89d,c64c7e08,c09c2800) at spec_vnoperate+0x15 > ufs_vnoperatespec(c64c7e08,c09c2800,c09ad440,0,0) at ufs_vnoperatespec+0x15 > vn_ioctl(c09ad440,465d,c64c7ecc,c5afa4c0,c5afa4c0) at vn_ioctl+0xdd > ioctl(c5afa4c0,c64c7f80,2,bfbfde00,bfbfde0c) at ioctl+0x1ef > syscall(2f,2f,2f,bfbfde0c,bfbfde00) at syscall+0x182 > Xint0x80_syscall() at Xint0x80_syscall+0x30 > db> ps > [omitted] > db> > > Kernel configuration: > > [omitted] > > Any clues? Yes, they're in vinum(4). They explain what information you should supply if things go wrong. Basically, the information above wouldn't normally be of much use. Having said that, however, in this particular case I *do* recognize the problem. As soon as we get over the lockmgr panics, I should be able to commit a fix for it--hopefully later today. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 21:20:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 8EC95151B7 for ; Mon, 28 Jun 1999 21:20:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA26149; Mon, 28 Jun 1999 21:20:21 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 21:20:21 -0700 (PDT) From: Matthew Dillon Message-Id: <199906290420.VAA26149@apollo.backplane.com> To: Julian Elischer Cc: Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :ok : : hadn't seen this one when I sent the previous email.. : :Julian : : :On Mon, 28 Jun 1999, Matthew Dillon wrote: : :> :You are right that the buffer cache is very tricky. It is hard to :> :change it in ways that preserves functionality and performance. :... I've had a long phone conversation with Kirk. We're basically on the same page. The concentration has got to be to stabilize what we have first, and we will worry about formalizing (and cleaning up) the lock semantics later. Basically what it comes down to is that the exclusive locks on struct buf's are going to have to move to an always-recursive model to handle certain situations that come up both with softupdates and with VFS layering. The original B_BUSY locks were exclusive but non-recursive. The differences between recursive and non-recursive exclusive locks plus unexpected side effects from lockmgr() operation are what led to the bugs in the original commit. For example, recursive exclusive locks require ownership reassignment while non-recursive exclusive locks do not. This led to the KERNPROC hack, and is why it needs to stay in at least until we can formalize the lock semantics and find a choke point (maybe involving fiddling with b_flags) to implement the case more appropriately. I think I also have a good line on how to finally fix the blocking-during-write-I/O problem. Basically it involves taking a page out of UVM and making VMIO pages copy-on-write for the purposes of an I/O, allowing the write operation to take out a shared lock on the buffer instead of an exclusive lock. The I/O operation gets the real page, and if the system needs to write to it while the I/O is in progress the system allocates and copies the page on the fly and the page being used for the I/O is detached (and freed at the end of the I/O). We would essentially get rid of the bogus page junk and replace it with copy-on-write junk. Kirk and I both think that we can get rid of nearly all the blocking conditions that occur during an access to a buffer that is simultanious with an I/O being performed on the same buffer. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 22:59:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep4.post.tele.dk (fep4.post.tele.dk [195.41.46.139]) by hub.freebsd.org (Postfix) with ESMTP id A0A1B1522C for ; Mon, 28 Jun 1999 22:59:12 -0700 (PDT) (envelope-from peter@holm.cc) Received: from holm.cc ([195.249.209.31]) by fep4.post.tele.dk (InterMail v4.0 201-221) with ESMTP id <19990629055912.CCBD3334.fep4@holm.cc> for ; Tue, 29 Jun 1999 07:59:12 +0200 Message-ID: <37786140.ACB199AF@holm.cc> Date: Tue, 29 Jun 1999 08:01:36 +0200 From: Peter Holm X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: lockmgr crashes... References: <199906290548.HAA07683@login.dknet.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Date: Mon, 28 Jun 1999 17:22:22 -0400 (EDT) > From: Kenneth Wayne Culver > To: freebsd-current@FreeBSD.ORG > > > Just to let someone know... I recently (a couple of hours ago) have been > having a problem with kernel panics.... I tried to remake the world and > the kernel panics saying: > > panic: lockmgr: > > then what follows is different every time... all I know is that it doesn't > happen until the process number is in the 25000 range, and after this, the > disks refuse to sync, and I have to push the reset button on my > computer... > > Kenneth Culver > I can reproduce the same error within an hour. Here's a stack trace : #0 0xc016597d in boot () #1 0xc0165bcd in panic () #2 0xc012d561 in db_panic () #3 0xc012d501 in db_command () #4 0xc012d5c6 in db_command_loop () #5 0xc012f727 in db_trap () #6 0xc0251300 in kdb_trap () #7 0xc025f9e0 in trap () #8 0xc0251543 in Debugger () #9 0xc0165bc4 in panic () #10 0xc0161610 in lockmgr () #11 0xc0238c52 in relpbuf () #12 0xc022daa4 in swp_pager_async_iodone () #13 0xc0186393 in biodone () #14 0xc028d227 in wdintr () #15 0xc025e7ec in slow_copyout () #16 0xc017ef13 in soreceive () #17 0xc0174ae4 in soo_read () #18 0xc01717b3 in dofileread () #19 0xc01716c3 in read () #20 0xc026021e in syscall () #21 0xc0251c30 in Xint0x80_syscall () #22 0x8048a2f in ?? () #23 0x804868d in ?? () I compiled with DEBUG_LOG, but the struct lock argument to #10 contains sys/buf.h:261, which is just BUF_LOCK. By the way, can anybody point me to documentation for ddb? Regards, -- Peter Holm | mailto:peter@holm.cc | http://login.dknet.dk/~pho/ -[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 23:12:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7A89B14C87 for ; Mon, 28 Jun 1999 23:12:52 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id XAA58058; Mon, 28 Jun 1999 23:12:07 -0700 (PDT) Date: Mon, 28 Jun 1999 23:12:06 -0700 (PDT) From: Julian Elischer To: Matthew Dillon Cc: Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) In-Reply-To: <199906290420.VAA26149@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Matthew Dillon wrote: > > :ok > : > : hadn't seen this one when I sent the previous email.. > : > :Julian > : > : > :On Mon, 28 Jun 1999, Matthew Dillon wrote: > : > :> :You are right that the buffer cache is very tricky. It is hard to > :> :change it in ways that preserves functionality and performance. > :... > > I've had a long phone conversation with Kirk. We're basically on the > same page. The concentration has got to be to stabilize what we have > first, and we will worry about formalizing (and cleaning up) the lock > semantics later. > > Basically what it comes down to is that the exclusive locks on struct > buf's are going to have to move to an always-recursive model to handle > certain situations that come up both with softupdates and with VFS > layering. The original B_BUSY locks were exclusive but non-recursive. > The differences between recursive and non-recursive exclusive locks > plus unexpected side effects from lockmgr() operation are what led to > the bugs in the original commit. For example, recursive exclusive locks > require ownership reassignment while non-recursive exclusive locks do > not. This led to the KERNPROC hack, and is why it needs to stay in > at least until we can formalize the lock semantics and find a choke point > (maybe involving fiddling with b_flags) to implement the case more > appropriately. > > I think I also have a good line on how to finally fix the > blocking-during-write-I/O problem. Basically it involves taking > a page out of UVM and making VMIO pages copy-on-write for the purposes > of an I/O, allowing the write operation to take out a shared lock on > the buffer instead of an exclusive lock. The I/O operation gets the > real page, and if the system needs to write to it while the I/O is in > progress the system allocates and copies the page on the fly and the > page being used for the I/O is detached (and freed at the end of the I/O). > We would essentially get rid of the bogus page junk and replace it with > copy-on-write junk. > > Kirk and I both think that we can get rid of nearly all the blocking > conditions that occur during an access to a buffer that is simultanious > with an I/O being performed on the same buffer. > The problem I see with this is teh resource load in times of critical resource shortage. If you need to suddenly generate a writable page.. where does the page come from? If resources are not available, I guess you could just stall the write until the original page is reconstituted (after soft updates remerges backed out data), but there is the danger that the write request could be very large, and that duplicated data could be both very expensive and very "surprising" to the system. Still it's an intriguing concept. How much CPU do you "use" to generate the writable copies before you start going backwards in performance. (unless I completely misunderstood what you said.) julian > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 23:13:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 39B8414C87 for ; Mon, 28 Jun 1999 23:13:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 6191383; Tue, 29 Jun 1999 14:13:10 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Holm Cc: freebsd-current@freebsd.org Subject: Re: lockmgr crashes... In-reply-to: Your message of "Tue, 29 Jun 1999 08:01:36 +0200." <37786140.ACB199AF@holm.cc> Date: Tue, 29 Jun 1999 14:13:10 +0800 From: Peter Wemm Message-Id: <19990629061310.6191383@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Holm wrote: > > > > Date: Mon, 28 Jun 1999 17:22:22 -0400 (EDT) > > From: Kenneth Wayne Culver > > To: freebsd-current@FreeBSD.ORG > > > > > > Just to let someone know... I recently (a couple of hours ago) have been > > having a problem with kernel panics.... I tried to remake the world and > > the kernel panics saying: > > > > panic: lockmgr: > > > > then what follows is different every time... all I know is that it doesn't > > happen until the process number is in the 25000 range, and after this, the > > disks refuse to sync, and I have to push the reset button on my > > computer... > > > > Kenneth Culver > > > > I can reproduce the same error within an hour. > > Here's a stack trace : > #9 0xc0165bc4 in panic () > #10 0xc0161610 in lockmgr () > #11 0xc0238c52 in relpbuf () > #12 0xc022daa4 in swp_pager_async_iodone () > #13 0xc0186393 in biodone () > #14 0xc028d227 in wdintr () > #15 0xc025e7ec in slow_copyout () This should be fixed a few minutes ago. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jun 28 23:54: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 67F3714C87 for ; Mon, 28 Jun 1999 23:54:04 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA26968; Mon, 28 Jun 1999 23:53:40 -0700 (PDT) (envelope-from dillon) Date: Mon, 28 Jun 1999 23:53:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199906290653.XAA26968@apollo.backplane.com> To: Julian Elischer Cc: Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The problem I see with this is teh resource load in times of critical :resource shortage. If you need to suddenly generate a writable page.. :where does the page come from? If resources are not available, I guess you :could just stall the write until the original page is reconstituted (after :soft updates remerges backed out data), but there is the danger that the :write request could be very large, and that duplicated data could be both :very expensive and very "surprising" to the system. : :Still it's an intriguing concept. How much CPU do you "use" to generate :the writable copies before you start going backwards in performance. : :julian This was the first thing I considered. It turns out to be a non-problem because you've already initiated the I/O - if you have a critical resource shortage the blockage occurs in a process context and not an interrupt context, and the you are guarenteed a page will become available 'soon'. Duplicating the data is almost certainly not going to be as expensive as waiting for the I/O to complete would be. And it really doesn't happen all that often since the buffer cache normally operates in an LRU fashion. Where it wins the most is that it allows the filesystem to do write-behind without intefering with performance. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 4:28: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id AA13C14BE5 for ; Tue, 29 Jun 1999 04:27:41 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Tue, 29 Jun 1999 12:27:27 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id NHL6LY7Y; Tue, 29 Jun 1999 12:18:28 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10yw30-0001Jw-00 for current@FreeBSD.org; Tue, 29 Jun 1999 12:27:30 +0100 Date: Tue, 29 Jun 1999 12:27:30 +0100 To: current@FreeBSD.org Subject: Which nfs version? Message-Id: <19990629122729.A4981@palmerharvey.co.uk> MIME-Version: 1.0 X-Mailer: Mutt 0.95.5i From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is probably a daft question, but how does one tell what nfs version a mount is? I thought that plain old mount(8) would do the trick, but it doesn't. Any ideas? -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "It's amazing how much you miss -good- Unix command line tools after you get used to Linux and the GNU ones. How Unix vendors can ship ancient shells with no job control and no cursor editing by default and still wonder why people buy NT is beyond me." -- Alan Cox -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 6:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id CCE1D14C56 for ; Tue, 29 Jun 1999 06:13:08 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 0DFA718F7; Tue, 29 Jun 1999 15:13:21 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 0B11E49FC for ; Tue, 29 Jun 1999 15:13:21 +0200 (CEST) Date: Tue, 29 Jun 1999 15:13:17 +0200 (CEST) From: Andrzej Bialecki To: freebsd-current@freebsd.org Subject: Panic in vm_page_zero_idle Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Sources are from yesterday, machine is Toshiba Portege 7020CT. During make -j24 buildworld machine dies with the following panic mesage (notice absence of register dump): kernel: type 12 trap, code=0 Stopped at vm_page_zero_idle+0xc9: movl %eax,0x4(%edx) db> tr vm_page_zero_idle(e,66a,2,183f9ff,756e6547) at vm_page_zero_idle+0xc9 idle_loop() at idle_loop+0x2d I can reproduce it at will, if someone's interested in more detailed report. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 8:59:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (mvo-ca18-41.ix.netcom.com [207.93.156.169]) by hub.freebsd.org (Postfix) with ESMTP id 39C5F14C82 for ; Tue, 29 Jun 1999 08:59:13 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id IAA01937; Tue, 29 Jun 1999 08:59:10 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Tue, 29 Jun 1999 08:59:10 -0700 (PDT) Message-Id: <199906291559.IAA01937@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Is freebsd.org Down? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I attempted to reach the archives to search for a 3.1 boot floppy problem and cannot. Is www.freebsd.org down? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 9:17:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 89C33150D3 for ; Tue, 29 Jun 1999 09:17:30 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10z0WR-000H8g-00; Tue, 29 Jun 1999 18:14:11 +0200 From: Sheldon Hearn To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Is freebsd.org Down? In-reply-to: Your message of "Tue, 29 Jun 1999 08:59:10 MST." <199906291559.IAA01937@ix.netcom.com> Date: Tue, 29 Jun 1999 18:14:11 +0200 Message-ID: <65885.930672851@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999 08:59:10 MST, Thomas Dean wrote: > Is www.freebsd.org down? It was for a while, it isn't at the time of this posting and freebsd-current wasn't a good choice of mailing list. :-) Later, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 9:23:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (mvo-ca18-41.ix.netcom.com [207.93.156.169]) by hub.freebsd.org (Postfix) with ESMTP id B9BE3150D3 for ; Tue, 29 Jun 1999 09:23:20 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id JAA02005; Tue, 29 Jun 1999 09:23:17 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Tue, 29 Jun 1999 09:23:17 -0700 (PDT) Message-Id: <199906291623.JAA02005@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Re: Is freebsd.org Down? References: <199906291559.IAA01937@ix.netcom.com> <19990629180903.A92695@sol.freibergnet.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can get there, now. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 9:41:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E9C6115324 for ; Tue, 29 Jun 1999 09:41:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA96187; Tue, 29 Jun 1999 10:41:00 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA22176; Tue, 29 Jun 1999 10:39:34 -0600 (MDT) Message-Id: <199906291639.KAA22176@harmony.village.org> To: obrien@NUXI.com Subject: Re: **HEADS UP** newsyslog.conf syntax change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Jun 1999 20:19:56 PDT." <19990627201956.A1998@dragon.nuxi.com> References: <19990627201956.A1998@dragon.nuxi.com> Date: Tue, 29 Jun 1999 10:39:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990627201956.A1998@dragon.nuxi.com> "David O'Brien" writes: : On your next ``make world'', you will need to change any "user.group" : specifications in /etc/newsyslog.conf to "user:group". I'll add this to updating, but wouldn't it make more sense to accept (with a warning) the old form when there isn't a user by the name of user.group? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 10:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6C0B514BEF for ; Tue, 29 Jun 1999 10:13:06 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 122DB82; Wed, 30 Jun 1999 01:13:06 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: Re: Panic in vm_page_zero_idle In-reply-to: Your message of "Tue, 29 Jun 1999 15:13:17 +0200." Date: Wed, 30 Jun 1999 01:13:06 +0800 From: Peter Wemm Message-Id: <19990629171306.122DB82@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Hi, > > Sources are from yesterday, machine is Toshiba Portege 7020CT. During make > -j24 buildworld machine dies with the following panic mesage (notice > absence of register dump): > > kernel: type 12 trap, code=0 > Stopped at vm_page_zero_idle+0xc9: movl %eax,0x4(%edx) > > db> tr > vm_page_zero_idle(e,66a,2,183f9ff,756e6547) at vm_page_zero_idle+0xc9 > idle_loop() at idle_loop+0x2d That's because there is no process context at this point, and nowhere the registers are saved for the idle ``context''. Trap 12 is a page fault. Do a 'show registers' to see what's up. I would like to know what %edx is. It's trapping here: m = vm_page_list_find(PQ_FREE, free_rover, FALSE); if (m != NULL && (m->flags & PG_ZERO) == 0) { --(*vm_page_queues[m->queue].lcnt); TAILQ_REMOVE(vm_page_queues[m->queue].pl, m, pageq); ^^^^^^^^^^^^^^^^^^^^^^^^^^^ m->queue = PQ_NONE; splx(s); Specifically, vm_page_queues[m->queue].pl is invalid or the tailq corrupt or something evil along those lines. Or, m->queue is bogus and causing an out of bounds array lookup. Hmm, do a show registers and record %eax at this point too. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 13: 4: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 730A414CAC for ; Tue, 29 Jun 1999 13:03:58 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA20605; Tue, 29 Jun 1999 13:03:52 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 29 Jun 1999 13:03:52 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Warner Losh Cc: obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: **HEADS UP** newsyslog.conf syntax change In-Reply-To: <199906291639.KAA22176@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Warner Losh wrote: > I'll add this to updating, but wouldn't it make more sense to accept > (with a warning) the old form when there isn't a user by the name of > user.group? Yes. Count me as one more vote for "accept with a warning." Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 14: 2:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2.post.tele.dk (fep2.post.tele.dk [195.41.46.135]) by hub.freebsd.org (Postfix) with ESMTP id 6F1B114EB5 for ; Tue, 29 Jun 1999 14:02:34 -0700 (PDT) (envelope-from peter@holm.cc) Received: from holm.cc ([195.249.209.107]) by fep2.post.tele.dk (InterMail v4.0 201-221) with ESMTP id <19990629210253.KVRY13557.fep2@holm.cc> for ; Tue, 29 Jun 1999 23:02:53 +0200 Message-ID: <377934F9.E844B8AC@holm.cc> Date: Tue, 29 Jun 1999 23:04:57 +0200 From: Peter Holm X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Fatal trap 12: page fault while in kernel mode, pmap_copy+0x174 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got this crash with current as of 3 hours ago: current# gdb -k kernel.3 vmcore.3 GNU gdb 4.18 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 3792896 initial pcb at 318fa0 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbfca0250 fault code = supervisor read, page not present instruction pointer = 0x8:0xc025dbd4 stack pointer = 0x10:0xc6b6fe80 frame pointer = 0x10:0xc6b6fea0 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 = 23378 (sh) interrupt mask = panic: from debugger panic: from debugger --- #0 0xc01659ac in boot () (kgdb) bt #0 0xc01659ac in boot () #1 0xc0165bf9 in panic () #2 0xc012d561 in db_panic () #3 0xc012d501 in db_command () #4 0xc012d5c6 in db_command_loop () #5 0xc012f727 in db_trap () #6 0xc0251658 in kdb_trap () #7 0xc0260314 in trap_fatal () #8 0xc025ffed in trap_pfault () #9 0xc025fc2f in trap () #10 0xc025dbd4 in pmap_copy () #11 0xc02320ef in vm_map_copy_entry () #12 0xc02322c8 in vmspace_fork () #13 0xc022f51f in vm_fork () #14 0xc0160655 in fork1 () #15 0xc015ffe5 in fork () #16 0xc026057e in syscall () #17 0xc0251f90 in Xint0x80_syscall () #18 0x804b126 in ?? () #19 0x804a675 in ?? () #20 0x804a5ef in ?? () #21 0x804a70f in ?? () #22 0x804a5fe in ?? () #23 0x8051073 in ?? () #24 0x8050fef in ?? () #25 0x80480e9 in ?? () (kgdb) quit current# uname -a FreeBSD current.risby.dk 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Jun 29 20:00:39 CEST 1999 pho@current.risby.dk:/usr/src/current/src/sys/compile/PHO i386 current# exit I wrote down the result from a "show registers" (I *realy* do need to get a null modem cable). Best regards, -- Peter Holm | mailto:peter@holm.cc | http://login.dknet.dk/~pho/ -[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 14:44: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.30.145]) by hub.freebsd.org (Postfix) with ESMTP id 8D51D14BE5 for ; Tue, 29 Jun 1999 14:43:55 -0700 (PDT) (envelope-from plm@smtp1.xs4all.nl) Received: from localhost. (dc2-isdn1770.dial.xs4all.nl [194.109.154.234]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id XAA27583 for ; Tue, 29 Jun 1999 23:43:54 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.1) id XAA00595; Tue, 29 Jun 1999 23:43:53 +0200 (MET DST) (envelope-from plm) To: freebsd-current@freebsd.org Subject: Suspend mode From: Peter Mutsaers Date: 29 Jun 1999 23:42:34 +0200 Message-ID: <87d7yeu1it.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 27 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while ago (I think when 3.X was still current) when my (ATX) desktop system would go in suspend mode (using zzz, waiting for the timeout or by pushing <4s on the power button) the system would become completely quiet: - disks spin down - CPU fan of Nowadays, some fan keeps running. This is very annoying (forcing me to halt -p all the time instead of going to suspend mode) since the system is in the living room and the noise (even though it is not very loud) is unacceptable. I vaguely remember changes to APM some months ago, I think the problem started back then. Has something changed some months ago that might have caused this? Is there a way to have a complete & quiet suspend again? Thanks in advance, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. ---------------+---------------------+------------------ Powered by FreeBSD (-current). See http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 15: 9:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-3.ppp.wenet.net [206.15.85.3]) by hub.freebsd.org (Postfix) with ESMTP id 68400150AE for ; Tue, 29 Jun 1999 15:09:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id PAA00338; Tue, 29 Jun 1999 15:09:11 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 29 Jun 1999 15:09:10 -0700 (PDT) From: Alex Zepeda To: Peter Mutsaers Cc: freebsd-current@FreeBSD.ORG Subject: Re: Suspend mode In-Reply-To: <87d7yeu1it.fsf@muon.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Jun 1999, Peter Mutsaers wrote: > A while ago (I think when 3.X was still current) when my (ATX) desktop > system would go in suspend mode (using zzz, waiting for the timeout or > by pushing <4s on the power button) the system would become completely > quiet: > > - disks spin down > - CPU fan off Well, pushing <4s on the power button will turn the computer off (in fact it's more of a "hard" power off IIRC). WRT suspend mode, my Award BIOS has an option to keep the fan on all the time while in a power managed state. This might be what's causing your system to continue being so noisy. - alex I thought felt your touch In my car, on my clutch But I guess it's just someone who felt a lot like I remember you. - Translator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 15:24:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 8533D15074 for ; Tue, 29 Jun 1999 15:24:13 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 48807 invoked from network); 29 Jun 1999 22:24:12 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 29 Jun 1999 22:24:12 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id RAA34070; Tue, 29 Jun 1999 17:24:11 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Tue, 29 Jun 1999 17:24:11 -0500 (CDT) From: David Scheidt To: Alex Zepeda Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: Suspend modeX In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Alex Zepeda wrote: > Well, pushing <4s on the power button will turn the computer off (in fact > it's more of a "hard" power off IIRC). Depends on the BIOS. It is often settable. David, who finds most ATX stuff annoying because it hasn't got a 25 pin serial port. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 17:12: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-43.ppp.wenet.net [206.15.85.43]) by hub.freebsd.org (Postfix) with ESMTP id B5014151C7 for ; Tue, 29 Jun 1999 17:12:00 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id RAA00390; Tue, 29 Jun 1999 17:11:50 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 29 Jun 1999 17:11:50 -0700 (PDT) From: Alex Zepeda To: David Scheidt Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG Subject: Re: Suspend modeX In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, David Scheidt wrote: > On Tue, 29 Jun 1999, Alex Zepeda wrote: > > > Well, pushing <4s on the power button will turn the computer off (in fact > > it's more of a "hard" power off IIRC). > > Depends on the BIOS. It is often settable. Weird. I know with ACPI, you can push the button and have Windows suspend or power down gracefully... > David, who finds most ATX stuff annoying because it hasn't got a 25 pin > serial port. So grab a cheap IO card or something (not even my 386 has a 25 pin serial port), or use an adaptor. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 19: 2:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ix.netcom.com (mvo-ca18-41.ix.netcom.com [207.93.156.169]) by hub.freebsd.org (Postfix) with ESMTP id 4096214E07 for ; Tue, 29 Jun 1999 19:02:08 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id TAA02845; Tue, 29 Jun 1999 19:02:06 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Date: Tue, 29 Jun 1999 19:02:06 -0700 (PDT) Message-Id: <199906300202.TAA02845@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: Boot Manager says F1 ?? for WINNT References: <87d7yeu1it.fsf@muon.xs4all.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed -current on a notebook with WINNT on the disk. The notebook has the ide disk limitation. So, I chopped the disk do get around it. Maybe I should buy a new notebook, but, this one works. Everything worked OK, except the boot manager. I get: F1 ?? F2 FreeBSD F3 ?? F4 FreeBSD Pressing F1 boots WINNT, F2 boots FreeBSD. The other partitions are not bootable. The disk slices are: 1. 400MB WINNT NTFS 2. 120 FreeBSD /, swap, and /var 3. 600MB WINNT NTFS 4. 960MB FreeBSD /usr FDISK recognizes the partition as NTFS, etc. How do I get something other than ?? for F1 and lose F3 and F4? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 19:16: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (Postfix) with ESMTP id D30E414E13 for ; Tue, 29 Jun 1999 19:15:57 -0700 (PDT) (envelope-from jobaldwi@vt.edu) Received: from john.baldwin.cx (207-172-143-157.s30.as2.hgt.md.dialup.rcn.com [207.172.143.157]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id WAA16297; Tue, 29 Jun 1999 22:15:51 -0400 (EDT) Message-Id: <199906300215.WAA16297@smtp4.erols.com> X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199906300202.TAA02845@ix.netcom.com> Date: Tue, 29 Jun 1999 22:15:50 -0400 (EDT) From: John Baldwin To: Thomas Dean Subject: RE: Boot Manager says F1 ?? for WINNT Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jun-99 Thomas Dean wrote: > I installed -current on a notebook with WINNT on the disk. The > notebook has the ide disk limitation. So, I chopped the disk do get > around it. Maybe I should buy a new notebook, but, this one works. > > Everything worked OK, except the boot manager. I get: > > F1 ?? > F2 FreeBSD > F3 ?? > F4 FreeBSD > > Pressing F1 boots WINNT, F2 boots FreeBSD. The other partitions are > not bootable. > > The disk slices are: > 1. 400MB WINNT NTFS > 2. 120 FreeBSD /, swap, and /var > 3. 600MB WINNT NTFS > 4. 960MB FreeBSD /usr > > FDISK recognizes the partition as NTFS, etc. > > How do I get something other than ?? for F1 and lose F3 and F4? > > tomdean You could try OS-BS (available on CD 1 in the tools/ dir or via ftp at pub/FreeBSD/tools from any mirror). It's much prettier and configurable, IHMO, than BootEasy. --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 20:51: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 630B614ED6 for ; Tue, 29 Jun 1999 20:51:04 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id WAA17903; Tue, 29 Jun 1999 22:49:37 -0500 (CDT) (envelope-from dan) Date: Tue, 29 Jun 1999 22:49:37 -0500 From: Dan Nelson To: Thomas Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: Boot Manager says F1 ?? for WINNT Message-ID: <19990629224937.A17683@dan.emsphone.com> References: <87d7yeu1it.fsf@muon.xs4all.nl> <199906300202.TAA02845@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199906300202.TAA02845@ix.netcom.com>; from "Thomas Dean" on Tue Jun 29 19:02:06 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jun 29), Thomas Dean said: > I installed -current on a notebook with WINNT on the disk. The > notebook has the ide disk limitation. So, I chopped the disk do get > around it. Maybe I should buy a new notebook, but, this one works. > > Everything worked OK, except the boot manager. I get: > > F1 ?? > F2 FreeBSD > F3 ?? > F4 FreeBSD > > Pressing F1 boots WINNT, F2 boots FreeBSD. The other partitions are > not bootable. > > How do I get something other than ?? for F1 and lose F3 and F4? Part of the problem is the bootblock has to fit in 512 bytes, so there's no room for all possible partition types. At the moment, there are 8 whole bytes free :), so you should be able to fit an "NT" type in there. It would take two bytes to map the NT partition type to the "DOS" string, and two+stringlen to map it to another string. Source is in /sys/boot/i386/boot0/boot0.s As for removing slices from the menu, man boot0cfg. The -m option lets you mask out any or all of the partitions. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jun 29 22: 6:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 1F40A151E8 for ; Tue, 29 Jun 1999 22:06:48 -0700 (PDT) (envelope-from aogrum@vnet.net) Received: from aogrum.vnet.net (aogrum.vnet.net [166.82.198.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with SMTP id BAA04149 for ; Wed, 30 Jun 1999 01:07:05 -0400 (EDT) Message-ID: <3779A0A6.41C67EA6@vnet.net> Date: Wed, 30 Jun 1999 00:44:22 -0400 From: Andy Grum X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Upgrading from ancient to current... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am currently running FreeBSD 2.1.5, and would like to upgrade to 3.1 without losing the tremendous amounts of data on my drive (backups are unfortunately not an option). I have seen several posts containing advice for accomplishing this task by altering sysinstall options, but this seems to only apply when upgrading from less distant version numbers. Is it even possible to upgrade to current from this ancient a version? Any help is appreciated! Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 0:29: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b169.neo.rr.com [24.93.181.169]) by hub.freebsd.org (Postfix) with ESMTP id 92D7114E0D for ; Wed, 30 Jun 1999 00:29:03 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA14201; Wed, 30 Jun 1999 03:32:57 -0400 Date: Wed, 30 Jun 1999 03:32:57 -0400 (EDT) From: Mike Nowlin To: Andy Grum Cc: freebsd-current@FreeBSD.ORG Subject: Re: Upgrading from ancient to current... In-Reply-To: <3779A0A6.41C67EA6@vnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am currently running FreeBSD 2.1.5, and would like to upgrade to 3.1 > without losing the tremendous amounts of data on my drive (backups are > unfortunately not an option). > I have seen several posts containing advice for accomplishing this task > by altering sysinstall options, but this seems to only apply when > upgrading from less distant version numbers. Is it even possible to > upgrade to current from this ancient a version? > I'm not a total expert on this, but from my experience, "stepping" the system up is pretty reliable... Most of my systems started out at 2.1.5, and have been CVSup'd to either 3.x or 2.2.8 without any major hair loss. I would definitely suggest upping to 2.2.8 first -- it's a much easier transition than going directly to 3+. There's a problem I ran into with a change in the root device definition in /etc/fstab, but the mailing lists archives should describe the fix for this -- it's basically changing /dev/wd0a to /dev/wd0s1a (or something like that) if I remember correctly. Once you get it up to a recent 2.x setup, start reading the docs about doing the 2->3 upgrade, while playing with your 2.2.8 system to make sure everything works. > (backups are unfortunately not an option). Hmmmmmmmm....... (frown) Question for the group: Is it possible to run a 2.2.8 kernel (temporarily) with a 2.1.5 binary installation tree? If it is, it'll be much smoother (and safer) upgrade for you.... --Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 0:42: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id D8A7014BCD for ; Wed, 30 Jun 1999 00:42:03 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id AAA26546; Wed, 30 Jun 1999 00:41:54 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <3779CA42.40534D6C@gorean.org> Date: Wed, 30 Jun 1999 00:41:54 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default References: <83735.930560597@axl.noc.iafrica.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > > First, the setting in /etc/defaults/rc.conf should default to > > off, as defaulting it to on violates POLA for the many many people who > > haven't updated to 3.x from 2.2 yet. > > If we were integrating TCP Wrapper support into the base system for the > very first time, I'd agree with you. However, we've already had a > release go out with an inetd that wrapped by default. It's never too late to change a bad decision. :) The majority of users (and clients) I talk to are still using 2.2.8-[Release|Stable] for many reasons, not the least of which is the perceived (and in some cases very real) level of difficulty in the upgrade. > This is a situation in which we can't make _everyone_ happy. For the > particular case you've provided, anyone who upgrades from 2.2 to 3.3 > without reading the release notes will get what's coming to him. That's always true, but traditionally it's been a primary goal of the project to make these kinds of changes as minimal as possible. > > Also, if the decision is made to leave it on by default, there should > > be a hosts.allow file installed by default that has nothing but "ALL : > > ALL" in it. > > We already have a hosts.allow that effectively allows everything. That's good news, thank you for clarifying it. > > Second, this command line switch is horrible UI design for > > several reasons. First, any command line option that requires that > > the same flag be applied twice is bad design, historical precedents > > aside. > > That's an unfortunately timed revelation for me. I mentioned it the last time you brought up this idea, a week or two ago. > I feel like I've seen > it in a number of programs, although the only one I can remember is > ftpd(8). I used that program as a reference, not knowing that it was bad > design. :-( *Nod* Good UI design is a difficult skill to learn, especially when there are so many bad examples out there. > > Second, what if I want to wrap my internal services, but not wrap my > > external ones? > > Then you want something that the guys working on the code, who use inetd > quite a lot, didn't think of. They probably made the assumption that > real-world scenarios like that don't exist. *Nodding again* That's why we have discussion about these kinds of things. :) > > I propose that the -w flag be changed to take parameters. To > > start with, you would have [-w <[e] [i]>] to control wrapping for > > external and internal services respectively. > > This makes my skin crawl, but that's probably just because I know what > the code looks like. :-) Without having looked at the code, I can't see where it would be that much more difficult. If you want to know whether to wrap internal services you are checking for a condition, whether that condition is two -w flags or the 'i' option to a single -w flag. You can solve this easily in any number of ways, the most common of which is toggling a set of hex flags at startup time. I'm sure I don't have to go into details for you, my point is simply that if the code makes this any more difficult than it has to be, fix the code. While you've already got the hood up tuning up one or two more things shouldn't be that much more work. :) Let me know if you need any help with it. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 1:40:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 8F04415355 for ; Wed, 30 Jun 1999 01:40:27 -0700 (PDT) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.2) with SMTP id MAA17056 for ; Wed, 30 Jun 1999 12:40:26 +0400 (MSD) (envelope-from camel@avias.com) From: Ilya Naumov Reply-To: camel@avias.com To: current@FreeBSD.ORG Subject: Re: Boot Manager says F1 ?? for WINNT Date: Wed, 30 Jun 1999 12:28:04 +0400 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <199906300202.TAA02845@ix.netcom.com> MIME-Version: 1.0 Message-Id: <99063012403500.42718@camel.avias.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ÓÒ , 30 ÉÀÎ 1999, Thomas Dean ÎÁÐÉÓÁÌ: > I installed -current on a notebook with WINNT on the disk. The > notebook has the ide disk limitation. So, I chopped the disk do get > around it. Maybe I should buy a new notebook, but, this one works. > > Everything worked OK, except the boot manager. I get: > > F1 ?? > F2 FreeBSD > F3 ?? > F4 FreeBSD > How do I get something other than ?? for F1 and lose F3 and F4? try to install boot.bin (with bootinst.exe) from /tools directory of FreeBSD distribution package. it will call NTFS partition as HPFS :) -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 3: 7:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 6D48F14D47 for ; Wed, 30 Jun 1999 03:07:49 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10zHH9-0000rH-00; Wed, 30 Jun 1999 12:07:31 +0200 From: Sheldon Hearn To: Doug Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default In-reply-to: Your message of "Wed, 30 Jun 1999 00:41:54 MST." <3779CA42.40534D6C@gorean.org> Date: Wed, 30 Jun 1999 12:07:31 +0200 Message-ID: <3302.930737251@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999 00:41:54 MST, Doug wrote: > > This is a situation in which we can't make _everyone_ happy. For the > > particular case you've provided, anyone who upgrades from 2.2 to 3.3 > > without reading the release notes will get what's coming to him. > > That's always true, but traditionally it's been a primary goal of the > project to make these kinds of changes as minimal as possible. Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He doesn't read the release notes, so he doesn't notice that inetd now wraps by default. The impact on him is: 1) Inetd makes unnecessary calls to hosts_access(). 2) Previously unwrapped internal services are suddenly and mysteriously wrapped. The first is a performance issue and isn't a big deal, given that Joe didn't read the release notes. The second _is_ an issue. However, it's got to be an issue for _someone_; either for Joe or for the guy who's upgrading from 3.2-RELEASE to 3.3-RELEASE. To me, it just doesn't make sense to pander to the people who've lagged behind STABLE. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 3: 9:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id B4A96154D5 for ; Wed, 30 Jun 1999 03:09:23 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 10zHIn-0000t9-00; Wed, 30 Jun 1999 12:09:13 +0200 From: Sheldon Hearn To: Doug Cc: current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default In-reply-to: Your message of "Wed, 30 Jun 1999 12:07:31 +0200." <3302.930737251@axl.noc.iafrica.com> Date: Wed, 30 Jun 1999 12:09:13 +0200 Message-ID: <3418.930737353@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999 12:07:31 +0200, Sheldon Hearn wrote: > Okay, so let's say we've got Joe Bloggs upgrading from 2.2.8 to 3.3 . He > doesn't read the release notes, so he doesn't notice that inetd now > wraps by default. The impact on him is: Damnit! I forgot the most important part of my argument -- people upgrading from 2.2.8 and don't read the release notes are going to have an /etc/rc.conf that sets inetd_flags="", hence their systems won't wrap! Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 6:10:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from unix2.it-datacntr.louisville.edu (unix2.it-datacntr.louisville.edu [136.165.4.28]) by hub.freebsd.org (Postfix) with ESMTP id 8832014C98 for ; Wed, 30 Jun 1999 06:10:47 -0700 (PDT) (envelope-from k.stevenson@louisville.edu) Received: from homer.louisville.edu (ktstev01@homer.louisville.edu [136.165.1.20]) by unix2.it-datacntr.louisville.edu (8.8.8/8.8.8) with ESMTP id JAA33050 for ; Wed, 30 Jun 1999 09:10:08 -0400 Received: (from ktstev01@localhost) by homer.louisville.edu (8.8.8/8.8.8) id JAA04413 for freebsd-current@freebsd.org; Wed, 30 Jun 1999 09:10:47 -0400 (EDT) Message-ID: <19990630091046.A3765@homer.louisville.edu> Date: Wed, 30 Jun 1999 09:10:46 -0400 From: Keith Stevenson To: freebsd-current@freebsd.org Subject: Re: HEADS UP! Inetd wrapping OFF by default References: <3302.930737251@axl.noc.iafrica.com> <3418.930737353@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3418.930737353@axl.noc.iafrica.com>; from Sheldon Hearn on Wed, Jun 30, 1999 at 12:09:13PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jun 30, 1999 at 12:09:13PM +0200, Sheldon Hearn wrote: > > > Damnit! I forgot the most important part of my argument -- people > upgrading from 2.2.8 and don't read the release notes are going to have > an /etc/rc.conf that sets inetd_flags="", hence their systems won't > wrap! Wouldn't it stand to reason that these people would fall into one of the following categories? 1) already running tcpd, which will continue to work 2) they will be unwrapped just like they were before the upgrade This is what happened to me when I upgraded from 2.2.8 to 3.1 w/o reading the release notes. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 11: 2: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id D700A155AB for ; Wed, 30 Jun 1999 11:01:58 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id LAA03357; Wed, 30 Jun 1999 11:01:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 30 Jun 1999 11:01:14 -0700 (PDT) From: Doug White To: Mike Nowlin Cc: Andy Grum , freebsd-current@FreeBSD.ORG Subject: Re: Upgrading from ancient to current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999, Mike Nowlin wrote: > > I am currently running FreeBSD 2.1.5, and would like to upgrade to 3.1 > > without losing the tremendous amounts of data on my drive (backups are > > unfortunately not an option). > > I have seen several posts containing advice for accomplishing this task > > by altering sysinstall options, but this seems to only apply when > > upgrading from less distant version numbers. Is it even possible to > > upgrade to current from this ancient a version? > > > > I'm not a total expert on this, but from my experience, "stepping" the > system up is pretty reliable... Most of my systems started out at 2.1.5, > and have been CVSup'd to either 3.x or 2.2.8 without any major hair loss. > I would definitely suggest upping to 2.2.8 first -- it's a much easier > transition than going directly to 3+. There's a problem I ran into with a > change in the root device definition in /etc/fstab, but the mailing lists > archives should describe the fix for this -- it's basically changing > /dev/wd0a to /dev/wd0s1a (or something like that) if I remember correctly. Yes. > Once you get it up to a recent 2.x setup, start reading the docs about > doing the 2->3 upgrade, while playing with your 2.2.8 system to make sure > everything works. > > > (backups are unfortunately not an option). > Hmmmmmmmm....... (frown) > > Question for the group: Is it possible to run a 2.2.8 kernel (temporarily) > with a 2.1.5 binary installation tree? If it is, it'll be much smoother > (and safer) upgrade for you.... No, not particularly. ps/top/friends will not work, and who knows what else. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 11:29:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 249CA1563C for ; Wed, 30 Jun 1999 11:29:26 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA80498; Wed, 30 Jun 1999 14:29:18 -0400 (EDT) Message-Id: <199906301829.OAA80498@cs.rpi.edu> To: Doug White Cc: freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Upgrading from ancient to current... In-Reply-To: Message from Doug White of "Wed, 30 Jun 1999 11:01:14 PDT." Date: Wed, 30 Jun 1999 14:29:18 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bit of a tangent from the original post, but when did the FreeBSD kernel start supporting ELF natively (not talking about Linux emulation). I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5 kernel, and it worked (mostly). I was unaware that anything that "old" supported ELF. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 12:10:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 3439814FE3 for ; Wed, 30 Jun 1999 12:10:09 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 803F182; Thu, 1 Jul 1999 03:10:08 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" Cc: Doug White , freebsd-current@FreeBSD.ORG Subject: Re: Upgrading from ancient to current... In-reply-to: Your message of "Wed, 30 Jun 1999 14:29:18 -0400." <199906301829.OAA80498@cs.rpi.edu> Date: Thu, 01 Jul 1999 03:10:08 +0800 From: Peter Wemm Message-Id: <19990630191008.803F182@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: > This is a bit of a tangent from the original post, but when did the FreeBSD > kernel start supporting ELF natively (not talking about Linux emulation). > I made the mistake of attempting to run a 3.0 ELF world with a 2.2.5 > kernel, and it worked (mostly). I was unaware that anything that "old" > supported ELF. 2.2 supported ELF quite some time before 2.2-stable was branched, for almost as long as ELF binaries were supported under Linux emulation... Native ELF support was added nearly for free. The main thing that'll break is that 3.x kernels and libraries have syscalls that do not exist in 2.x and you'll get SIGSYS's etc. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 17:26: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id ECFE2156ED for ; Wed, 30 Jun 1999 17:25:55 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10zUfm-000CSL-00 for freebsd-current@freebsd.org; Thu, 1 Jul 1999 07:25:50 +0700 Date: Thu, 1 Jul 1999 07:25:50 +0700 (ALMST) From: Boris Popov To: freebsd-current@freebsd.org Subject: Bad reference to zname in vm_zone struct Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Here is a 'little' problem with vm_zone structure and field 'zname' in it. zinit() function takes a pointer to name of zone and assigns it to field zname. Since nfs module defines this name in the static module memory pointer to name becomes invalid when module unloaded via kldunload command. This will lead to trap in kernel or will produce junk in sysctl output: # kldload nfs # kldunload nfs # sysctl vm.zone Last command will produce panic. This has been reported as PR-kern/12464 -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 17:56:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 75D59153CC for ; Wed, 30 Jun 1999 17:56:58 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA42042; Wed, 30 Jun 1999 17:56:33 -0700 (PDT) (envelope-from dillon) Date: Wed, 30 Jun 1999 17:56:33 -0700 (PDT) From: Matthew Dillon Message-Id: <199907010056.RAA42042@apollo.backplane.com> To: Julian Elischer Cc: Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG, Greg Lehey Subject: Re: Found the startup panic - ccd ( patch included ) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So far I've run the latest buffer cache related fixes overnight on my SMP test box without any problems. Is anyone still experiencing buffer-cache related problems with CURRENT? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 18:54:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5ECFA15502; Wed, 30 Jun 1999 18:54:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA07057; Wed, 30 Jun 1999 18:54:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA08285; Wed, 30 Jun 1999 18:54:23 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 30 Jun 1999 18:54:23 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org, stable@freebsd.org Subject: HEADS UP: Soft-updates sources are moving soon Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometime this weekend (July 3-5) I am planning to repository-copy the soft-updates sources from their current location in "src/contrib/sys/softupdates" to "src/sys/contrib/softupdates". All of you using soft-updates will need to adjust your symbolic links in "src/sys/ufs/ffs" after this change has taken effect. The reasons for the move have been discussed before. Briefly, we want to move all of the kernel code to "src/sys" so that the sys tree will be more self-contained. Kirk McKusick has agreed to this change -- in fact he favors it. I'm going to do this in both the -current and RELENG_3 branches. Here is the 1-question FAQ: Q. These symbolic links are a pain. Why don't you just edit "src/sys/conf/files" appropriately? A. The license terms for soft-updates do not permit that. See the FreeBSD mailing list archives (the FreeBSD-current list, probably) for more details. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 19: 5:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E52814EFE; Wed, 30 Jun 1999 19:05:31 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA32098; Thu, 1 Jul 1999 12:05:29 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id MAA02271; Thu, 1 Jul 1999 12:05:29 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 18:54:23 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 12:05:29 +1000 Message-ID: <2269.930794729@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the 1-question FAQ: Q. These symbolic links are a pain. Why don't you just edit "src/sys/conf/files" appropriately? A. The license terms for soft-updates do not permit that. See the FreeBSD mailing list archives (the FreeBSD-current list, probably) for more details. Would it be legal under the licence to include a rule in some Makefile which did the damn things, but was not automatically invoked anywhere? o Seems to me this would preserve the fundamental "intentionality" of the desire to have, and enable the softupdates. Would it be legal to include in standard CVSUP configs rules which prevent loss of the links if installed? o I may be wrong, but I think I loose them when I refresh if some rules are present. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 19: 7:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 6B06615213 for ; Wed, 30 Jun 1999 19:07:46 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA02381; Thu, 1 Jul 1999 11:37:39 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA82435; Thu, 1 Jul 1999 11:37:34 +0930 (CST) Date: Thu, 1 Jul 1999 11:37:34 +0930 From: Greg Lehey To: Matthew Dillon Cc: Julian Elischer , Kirk McKusick , Peter Wemm , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG Subject: Re: Found the startup panic - ccd ( patch included ) Message-ID: <19990701113734.J79211@freebie.lemis.com> References: <199907010056.RAA42042@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907010056.RAA42042@apollo.backplane.com>; from Matthew Dillon on Wed, Jun 30, 1999 at 05:56:33PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 30 June 1999 at 17:56:33 -0700, Matthew Dillon wrote: > So far I've run the latest buffer cache related fixes overnight on my > SMP test box without any problems. > > Is anyone still experiencing buffer-cache related problems with CURRENT? My problems are gone. But I'm not running SMP. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 19:12:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E58F7151F9; Wed, 30 Jun 1999 19:12:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id TAA07135; Wed, 30 Jun 1999 19:12:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA08842; Wed, 30 Jun 1999 19:12:24 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2269.930794729@dstc.edu.au> Date: Wed, 30 Jun 1999 19:12:24 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: George Michaelson Subject: Re: HEADS UP: Soft-updates sources are moving soon Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson wrote: > Q. These symbolic links are a pain. Why don't you just edit > "src/sys/conf/files" appropriately? > > A. The license terms for soft-updates do not permit that. See the > FreeBSD mailing list archives (the FreeBSD-current list, probably) for > more details. > > Would it be legal under the licence to include a rule in some Makefile > which did the damn things, but was not automatically invoked anywhere? Please don't start a discussion about this without first studying the mailing list archives. All of this stuff has been discussed before, and needn't be rehashed again. > Would it be legal to include in standard CVSUP configs rules which prevent > loss of the links if installed? > > o I may be wrong, but I think I loose them when I refresh if some rules > are present. CVSup won't touch your symbolic links. It won't touch any file that it doesn't know anything about. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 19:52:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id A52B814A09; Wed, 30 Jun 1999 19:52:39 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA09795; Thu, 1 Jul 1999 12:52:38 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id MAA02322; Thu, 1 Jul 1999 12:52:37 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 19:12:24 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 12:52:37 +1000 Message-ID: <2320.930797557@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cool. endit. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 20:17: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id D813514CBE; Wed, 30 Jun 1999 20:16:57 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id NAA23601; Thu, 1 Jul 1999 13:16:53 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id NAA02360; Thu, 1 Jul 1999 13:16:52 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 19:12:24 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 13:16:52 +1000 Message-ID: <2358.930799012@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The discussion(s) took place on hackers@FreeBSD.org. The search string in the archives which works is: kirk AND soft-update AND integration note the soft-update, not softupdates. note hackers. not current or stable. If you search anywhere else you will get techno-related issues. cheers -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jun 30 20:58:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EF73C14CBE; Wed, 30 Jun 1999 20:58:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA07398; Wed, 30 Jun 1999 20:58:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA09050; Wed, 30 Jun 1999 20:58:09 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2358.930799012@dstc.edu.au> Date: Wed, 30 Jun 1999 20:58:09 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: George Michaelson Subject: Re: HEADS UP: Soft-updates sources are moving soon Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson wrote: > > The discussion(s) took place on hackers@FreeBSD.org. > > The search string in the archives which works is: > > kirk AND soft-update AND integration > > note the soft-update, not softupdates. Thanks! I couldn't remember for sure where the discussion had been. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 2: 0:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 37201156F9 for ; Thu, 1 Jul 1999 02:00:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9D1CC83; Thu, 1 Jul 1999 17:00:06 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: Matthew Dillon , Julian Elischer , Kirk McKusick , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG Subject: Re: Found the startup panic - ccd ( patch included ) In-reply-to: Your message of "Thu, 01 Jul 1999 11:37:34 +0930." <19990701113734.J79211@freebie.lemis.com> Date: Thu, 01 Jul 1999 17:00:06 +0800 From: Peter Wemm Message-Id: <19990701090006.9D1CC83@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Wednesday, 30 June 1999 at 17:56:33 -0700, Matthew Dillon wrote: > > So far I've run the latest buffer cache related fixes overnight on my > > SMP test box without any problems. > > > > Is anyone still experiencing buffer-cache related problems with CURRENT ? > > My problems are gone. But I'm not running SMP. The main place I expect there to be trouble with is the swap-backed-vn device code. It does it's own clustering, aync/async-aware IO chaining, etc. > Greg Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 4: 8:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 9682014EE3 for ; Thu, 1 Jul 1999 04:08:36 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Thu, 01 Jul 1999 12:08:20 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id N96YDLH4; Thu, 1 Jul 1999 11:59:20 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10zehe-000Aoo-00 for current@freebsd.org; Thu, 1 Jul 1999 12:08:26 +0100 Date: Thu, 1 Jul 1999 12:08:26 +0100 To: current@freebsd.org Subject: fetch(1) and realms with whitespace... Message-Id: <19990701120825.A41541@palmerharvey.co.uk> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to specify a realm with whitespace to fetch? I've just had a fun time trying to do: % export HTTP_AUTH="basic:SunSolve Online:x:y" % fetch -v http://online.sunsolve.sun.co.uk/whatever senddoc: cannot authenticate with server Looking at the code it appears that there isn't a way to escape the whitespace... -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "How Unix vendors can ship ancient shells with no job control and no cursor editing by default and still wonder why people buy NT is beyond me." - Alan Cox -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 9:23:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5609214BF5 for ; Thu, 1 Jul 1999 09:23:38 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id MAA29768; Thu, 1 Jul 1999 12:23:32 -0400 (EDT) (envelope-from wollman) Date: Thu, 1 Jul 1999 12:23:32 -0400 (EDT) From: Garrett Wollman Message-Id: <199907011623.MAA29768@khavrinen.lcs.mit.edu> To: Dominic Mitchell Cc: current@FreeBSD.ORG Subject: fetch(1) and realms with whitespace... In-Reply-To: <19990701120825.A41541@palmerharvey.co.uk> References: <19990701120825.A41541@palmerharvey.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > % export HTTP_AUTH="basic:SunSolve Online:x:y" > % fetch -v http://online.sunsolve.sun.co.uk/whatever > senddoc: cannot authenticate with server > Looking at the code it appears that there isn't a way to escape the > whitespace... That's probably correct. You're certainly welcome to implement it. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 14:48:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 23521156B0 for ; Thu, 1 Jul 1999 14:48:07 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id RAA01864 for ; Thu, 1 Jul 1999 17:48:06 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15294; Thu, 1 Jul 1999 17:47:35 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id RAA01823; Thu, 1 Jul 1999 17:47:35 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199907012147.RAA01823@dean.pc.sas.com> Subject: a fix for a harmless but annoying sysinstall bug ... To: freebsd-current@freebsd.org Date: Thu, 1 Jul 1999 17:47:35 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This following is a patch that eliminates the sysinstall prompt that informs you that a distribution has failed to install, when really everything worked OK. This problem can be a real pain on FTP installs when you have packages following the normal install (like you can set up for a scripted install), but you aren't there to hit "OK", and then your ftp session times out, and the rest of your package installs fail when you finally come back and press "OK" because the ftp session has since timed out. Could someone please consider committing this patch? Index: dist.h =================================================================== RCS file: /mirror/ncvs/src/release/sysinstall/dist.h,v retrieving revision 1.35 diff -u -r1.35 dist.h --- dist.h 1999/05/14 07:15:04 1.35 +++ dist.h 1999/07/01 21:43:20 @@ -21,7 +21,7 @@ #define DIST_DES 0x04000 #define DIST_CATPAGES 0x08000 #define DIST_PORTS 0x10000 -#define DIST_ALL 0xFFFFF +#define DIST_ALL 0x1FFFF /* Canned distribution sets */ #define _DIST_DEVELOPER \ Thanks, -Brian -- Brian Dean The SAS Institute Inc brdean@unx.sas.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 1 15:14:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D65F715736 for ; Thu, 1 Jul 1999 15:14:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA50333; Thu, 1 Jul 1999 15:14:04 -0700 (PDT) (envelope-from dillon) Date: Thu, 1 Jul 1999 15:14:04 -0700 (PDT) From: Matthew Dillon Message-Id: <199907012214.PAA50333@apollo.backplane.com> To: Peter Wemm Cc: Greg Lehey , Julian Elischer , Kirk McKusick , Alan Cox , Mike Smith , "John S. Dyson" , dg@root.com, dyson@iquest.net, current@FreeBSD.ORG Subject: Re: Found the startup panic - ccd ( patch included ) References: <19990701090006.9D1CC83@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :The main place I expect there to be trouble with is the swap-backed-vn device :code. It does it's own clustering, aync/async-aware IO chaining, etc. : :> Greg : :Cheers, :-Peter I'm getting a new one. Sometimes during booting or rebooting the system gets stuck in "biord". I have not been able to get a core dump yet - the sync fails and the system doesn't even try for a core dump for some reason. I'm still trying to track it down. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 15:26:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C65E014A09 for ; Thu, 1 Jul 1999 15:26:52 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA92822 for ; Thu, 1 Jul 1999 15:26:51 -0700 (PDT) Date: Thu, 1 Jul 1999 15:26:49 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: Rfork man page entry & reality. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Rfork man page says: RFMEM If set, the kernel will force sharing of the entire ad- dress space. The child will then inherit all the shared segments the parent process owns. Other segment types will be unaffected. Subsequent forks by the parent will then propagate the shared data and bss between children. The stack segment is always split. May be set only with RFPROC. However the code says: if (flags & RFMEM) { p2->p_vmspace = p1->p_vmspace; p1->p_vmspace->vm_refcnt++; } My guess is that the man page should be changed to say: RFMEM If set, the kernel will force sharing of the entire ad- dress space. The child will then inherit all the memory segments the parent process owns. This is the basis of some thread models. May be set only with RFPROC. Any better suggestions of wording will be apreciated.. I'll check in a change of whatever sounds best after a day or so.. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 15:30:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B4A7414D63 for ; Thu, 1 Jul 1999 15:30:13 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA50452; Thu, 1 Jul 1999 15:30:12 -0700 (PDT) (envelope-from dillon) Date: Thu, 1 Jul 1999 15:30:12 -0700 (PDT) From: Matthew Dillon Message-Id: <199907012230.PAA50452@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Rfork man page entry & reality. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, you are absolutely right. It should also say: rfork() cannot be directly called from C when used with RFMEM, because C cannot deal with the fact that both processes return to the same stack. ( As an aside, we really need a linunx clone()-like system call so we can make use of this very cool rfork() threading feature. I wrote some example code a few months ago which someone can dig up for the core if they want to do it. If we can simply duplicate the linux clone from the compat libs it would be very cool if it were made available in our standard libs ). -Matt Matthew Dillon :The Rfork man page says: : RFMEM If set, the kernel will force sharing of the entire ad- : dress space. The child will then inherit all the shared : segments the parent process owns. Other segment types : will be unaffected. Subsequent forks by the parent will : then propagate the shared data and bss between children. : The stack segment is always split. May be set only with : RFPROC. : :However the code says: : : if (flags & RFMEM) { : p2->p_vmspace = p1->p_vmspace; : p1->p_vmspace->vm_refcnt++; : } : : :My guess is that the man page should be changed to say: : : RFMEM If set, the kernel will force sharing of the entire ad- : dress space. The child will then inherit all the memory : segments the parent process owns. This is the basis of some : thread models. May be set only with RFPROC. : :Any better suggestions of wording will be apreciated.. :I'll check in a change of whatever sounds best :after a day or so.. : :julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 16:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E593C14D90 for ; Thu, 1 Jul 1999 16:29:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA19210 for ; Thu, 1 Jul 1999 16:30:15 -0700 Date: Thu, 1 Jul 1999 16:29:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: this of interest to anyone? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 16:40: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 96BA014D94 for ; Thu, 1 Jul 1999 16:39:55 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 98504 invoked from network); 1 Jul 1999 23:39:54 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 1 Jul 1999 23:39:54 -0000 Received: from localhost (dscheidt@localhost) by shell-2.enteract.com (8.9.3/8.9.2) with SMTP id SAA82784; Thu, 1 Jul 1999 18:39:54 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-2.enteract.com: dscheidt owned process doing -bs Date: Thu, 1 Jul 1999 18:39:54 -0500 (CDT) From: David Scheidt To: Matthew Jacob Cc: freebsd-current@freebsd.org Subject: Re: this of interest to anyone? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Jul 1999, Matthew Jacob wrote: > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > It might be if you supplied some additional information, like what sources your kernel was built from, as a minimum. UP or SMP? What was the box doing when it paniced? If you have a dump, can you provide a stack trace? Anything else useful. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 16:53:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id D652314DD0 for ; Thu, 1 Jul 1999 16:53:38 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id QAA25937; Thu, 1 Jul 1999 16:49:32 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id QAA26321; Thu, 1 Jul 1999 16:53:37 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id QAA09696; Thu, 1 Jul 1999 16:51:05 -0700 To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: Your message of "Thu, 1 Jul 1999 16:29:26 -0700 (PDT)" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990701165105I.thomma@baynetworks.com> Date: Thu, 01 Jul 1999 16:51:05 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking I had the similar panic last night during make world. I have a dump at home but I didn't have time to take a look this morning. My system is dual PPro SMP, 128MB RAM, 3 SCSI UW disks with CCD, about two day old -current. Since the panic happened after update source tree (I should have saved it), I don't have kernel source code for the /kernel. I'll post the details if no one else reports the details when I get home. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 16:54:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 300F8151E9 for ; Thu, 1 Jul 1999 16:54:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA19319; Thu, 1 Jul 1999 16:55:06 -0700 Date: Thu, 1 Jul 1999 16:54:17 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: David Scheidt Cc: freebsd-current@freebsd.org Subject: Re: this of interest to anyone? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > > Sorry- -current as of today, alpha. rebooting. Likely an NFS lock. > > It might be if you supplied some additional information, like what > sources your kernel was built from, as a minimum. UP or SMP? What > was the box doing when it paniced? If you have a dump, can you > provide a stack trace? Anything else useful. > > > David > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 17:54:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from stevenson.cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (Postfix) with ESMTP id 84DFD150FD for ; Thu, 1 Jul 1999 17:54:10 -0700 (PDT) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by stevenson.cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id BAA20201; Fri, 2 Jul 1999 01:54:08 +0100 (BST) Date: Fri, 2 Jul 1999 01:54:06 +0100 Message-Id: <20376.199907020054@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: IBM-DJNA drives on FreeBSD To: phk@critter.freebsd.dk Organization: just say no Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm about to install FreeBSD 3.2 on a machine with an IBM-DJNA-371350 (Deskstar 22GXP 13.5GB) drive. I see that on the -current mailing list a few weeks ago you (phk) said: >Try disabling "ultra DMA" in the BIOS, that seems to have worked for >me on my IBM-DJNA-371800 drive. Is that relevant for 3.2 as well as current? And by "disabling ultra DMA" did you mean "disabling UDMA66" or "disabling UDMA completely"? (You can permanently disable UDMA66 with a DOS utility available from IBM, and it will then act as a plain UDMA33 drive.) Thanks, -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 23:34:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D9FED14DCC for ; Thu, 1 Jul 1999 23:34:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA52990; Thu, 1 Jul 1999 23:34:29 -0700 (PDT) (envelope-from dillon) Date: Thu, 1 Jul 1999 23:34:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199907020634.XAA52990@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Something weird happening w/ SMP -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm getting some really odd stuff with recent -current's configured for SMP. Processes are getting stuck in getblk() and other I/O waits. It does not appear to occur with UP configuration, only SMP. I seem to be able to repeat the problem by dd'ing a raw partition from a SCSI{ disk to /dev/null: dd if=/dev/rda1d bs=32k of=/dev/null If I run a 'systat -vm 1' in another window what I see are a bunch of ahc2 interrupts, around 500-1000 per second, and then it just stops. Then a few seconds later it starts up again. Then it just stops. Then a few seconds later it starts up again. It is as thought interrupts are being disabled for long periods of time but the weird thing is that other interrupts such as clk and rtc continue to work just fine. When the interrupts stop, dd is stuck in a disk-wait state. I'm sure it isn't the SCSI bus: I've got three SCSI busses and it occurs on all three. Plus it does not occur on a UP kernel, only an SMP kernel. If I run an endless loop in another window (e.g. systat shows 50% idle on the 2x SMP box), the interrupts appear to work for longer periods of time before crapping out. It is very weird. I have no idea what is going on. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 1 23:54:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C5E8F150CB for ; Thu, 1 Jul 1999 23:54:28 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA53043; Thu, 1 Jul 1999 23:54:28 -0700 (PDT) (envelope-from dillon) Date: Thu, 1 Jul 1999 23:54:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199907020654.XAA53043@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Re: Something weird happening w/ SMP -current References: <199907020634.XAA52990@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : interrupts such as clk and rtc continue to work just fine. : : When the interrupts stop, dd is stuck in a disk-wait state. I'm sure it : isn't the SCSI bus: I've got three SCSI busses and it occurs on all three. : Plus it does not occur on a UP kernel, only an SMP kernel. : : If I run an endless loop in another window (e.g. systat shows 50% idle : on the 2x SMP box), the interrupts appear to work for longer periods of : time before crapping out. : : It is very weird. I have no idea what is going on. : : -Matt : Here's some more info. If the dd is stuck and systat -vm 1 is showing no interrupts occuring on, for example, ahc2 (irq17), and I then do something that causes an interrupt to occur on mux (irq19), which I guess is ahc1, ahc2 then starts working... until it gets stuck again, that is. I can also get ahc2 going again by issuing another dd on ahc2. For example: dd if=/dev/rda1d bs=32k of=/dev/null ... let this one run ... ... it gets stuck ... dd if=/dev/rda1d bs=32k of=/dev/null count=1 ... this unsticks the first dd ... ... the first dd runs again ... ... the first dd gets stuck again ... repeat... All I can think of is that something is causing the system to lose an occassional interrupt. There's a race condition somewhere. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 0:21:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 172CF14D19 for ; Fri, 2 Jul 1999 00:21:29 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA71793; Fri, 2 Jul 1999 09:21:02 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199907020721.JAA71793@freebsd.dk> Subject: Re: Something weird happening w/ SMP -current In-Reply-To: <199907020654.XAA53043@apollo.backplane.com> from Matthew Dillon at "Jul 1, 1999 11:54:28 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 2 Jul 1999 09:21:02 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > > Here's some more info. If the dd is stuck and systat -vm 1 is showing > no interrupts occuring on, for example, ahc2 (irq17), and I then do > something that causes an interrupt to occur on mux (irq19), which I > guess is ahc1, ahc2 then starts working... until it gets stuck again, > that is. I can also get ahc2 going again by issuing another dd on ahc2. > > For example: > > dd if=/dev/rda1d bs=32k of=/dev/null > ... let this one run ... > ... it gets stuck ... > dd if=/dev/rda1d bs=32k of=/dev/null count=1 > ... this unsticks the first dd ... > ... the first dd runs again ... > ... the first dd gets stuck again ... > repeat... > > All I can think of is that something is causing the system to lose an > occassional interrupt. There's a race condition somewhere. Ahhh, I see this too, on an ATA only box that is, I loose my network from time to time, especially if there is lots of interrups on another source, it endeeed looks like we are loosing interrupts somewhere. Guess we have to study some of the latest changes more carefully and see went wrong, I'll try to experiment a bit with it.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 1: 4:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 516DD15437; Fri, 2 Jul 1999 01:04:25 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA08833; Fri, 2 Jul 1999 17:34:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA94606; Fri, 2 Jul 1999 17:34:22 +0930 (CST) Date: Fri, 2 Jul 1999 17:34:22 +0930 From: Greg Lehey To: FreeBSD Hackers , FreeBSD current users Subject: HEADS UP: Changes in Vinum Message-ID: <19990702173421.T87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been following up on a suggestion Jordan made earlier this week, and I've now introduced some simplified configuration commands for Vinum, in -CURRENT only. I think they cover a fair number of the situations you're likely to need, but they're not intended to be comprehensive. Still, I'd like to make them as good as they can be, and there's a good chance that I'll change them in some detail or another. There's too much to say for this message; RTFM (vinum(8)) and look for the 'concat', 'mirror' and 'stripe' commands and the section SIMPLIFIED CONFIGURATION. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 1:12: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 614AD14D79 for ; Fri, 2 Jul 1999 01:12:03 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id DAA27402; Fri, 2 Jul 1999 03:11:54 -0500 (CDT) Date: Fri, 2 Jul 1999 03:11:54 -0500 From: Alan Cox To: Soren Schmidt Cc: current@freebsd.org Subject: Re: Something weird happening w/ SMP -current Message-ID: <19990702031154.F10611@cs.rice.edu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=QTprm0S8XgL7H0Dt X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --QTprm0S8XgL7H0Dt Content-Type: text/plain; charset=us-ascii Try the attached patch. If this doesn't work, I'll back out the last i386/isa/ipl_funcs.c change. Alan --QTprm0S8XgL7H0Dt Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ipending.patch" Index: i386/i386/swtch.s =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/swtch.s,v retrieving revision 1.82 diff -c -r1.82 swtch.s *** swtch.s 1999/06/01 18:19:45 1.82 --- swtch.s 1999/06/30 07:50:54 *************** *** 311,317 **** * XXX: we had damn well better be sure we had it before doing this! */ CPL_LOCK /* XXX */ ! andl $~SWI_AST_MASK, _ipending /* XXX */ movl $0, _cpl /* XXX Allow ASTs on other CPU */ CPL_UNLOCK /* XXX */ movl $FREE_LOCK, %eax --- 311,317 ---- * XXX: we had damn well better be sure we had it before doing this! */ CPL_LOCK /* XXX */ ! MPLOCKED andl $~SWI_AST_MASK, _ipending /* XXX */ movl $0, _cpl /* XXX Allow ASTs on other CPU */ CPL_UNLOCK /* XXX */ movl $FREE_LOCK, %eax Index: i386/isa/apic_ipl.s =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/apic_ipl.s,v retrieving revision 1.23 diff -c -r1.23 apic_ipl.s *** apic_ipl.s 1999/04/10 19:22:17 1.23 --- apic_ipl.s 1999/06/30 07:43:55 *************** *** 116,121 **** --- 116,122 ---- ALIGN_TEXT splz_unpend: bsfl %ecx,%ecx + lock btrl %ecx,_ipending jnc splz_next cmpl $NHWI,%ecx Index: i386/isa/apic_vector.s =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/apic_vector.s,v retrieving revision 1.40 diff -c -r1.40 apic_vector.s *** apic_vector.s 1999/06/16 03:53:52 1.40 --- apic_vector.s 1999/06/30 07:35:32 *************** *** 398,403 **** --- 398,404 ---- MASK_IRQ(irq_num) ; \ EOI_IRQ(irq_num) ; \ AVCPL_LOCK ; /* MP-safe */ \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ AVCPL_UNLOCK ; \ lock ; \ *************** *** 409,414 **** --- 410,416 ---- ALIGN_TEXT ; \ 2: ; /* masked by cpl|cml */ \ APIC_ITRACE(apic_itrace_masked, irq_num, APIC_ITRACE_MASKED) ; \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ AVCPL_UNLOCK ; \ DELOCK ; /* XXX this is going away... */ \ *************** *** 418,423 **** --- 420,426 ---- 3: ; /* other cpu has isr lock */ \ APIC_ITRACE(apic_itrace_noisrlock, irq_num, APIC_ITRACE_NOISRLOCK) ;\ AVCPL_LOCK ; /* MP-safe */ \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ testl $IRQ_BIT(irq_num), _cpl ; \ jne 4f ; /* this INT masked */ \ *************** *** 485,490 **** --- 488,494 ---- pushl %eax ; \ orl _intr_mask + (irq_num) * 4, %eax ; \ movl %eax, _cpl ; \ + lock ; \ andl $~IRQ_BIT(irq_num), _ipending ; \ AVCPL_UNLOCK ; \ ; \ *************** *** 508,513 **** --- 512,518 ---- MASK_IRQ(irq_num) ; \ EOI_IRQ(irq_num) ; \ AVCPL_LOCK ; /* MP-safe */ \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ AVCPL_UNLOCK ; \ lock ; \ *************** *** 518,523 **** --- 523,529 ---- ALIGN_TEXT ; \ 2: ; /* masked by cpl, leave iactive set */ \ APIC_ITRACE(apic_itrace_masked, irq_num, APIC_ITRACE_MASKED) ; \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ AVCPL_UNLOCK ; \ ISR_RELLOCK ; /* XXX this is going away... */ \ *************** *** 527,532 **** --- 533,539 ---- 3: ; /* other cpu has isr lock */ \ APIC_ITRACE(apic_itrace_noisrlock, irq_num, APIC_ITRACE_NOISRLOCK) ;\ AVCPL_LOCK ; /* MP-safe */ \ + lock ; \ orl $IRQ_BIT(irq_num), _ipending ; \ testl $IRQ_BIT(irq_num), _cpl ; \ jne 4f ; /* this INT masked */ \ *************** *** 698,703 **** --- 705,711 ---- movl _cpl, %eax #endif pushl %eax + lock orl $SWI_AST_PENDING, _ipending AVCPL_UNLOCK lock Index: i386/isa/ipl.s =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.28 diff -c -r1.28 ipl.s *** ipl.s 1999/06/01 18:20:15 1.28 --- ipl.s 1999/06/30 07:46:33 *************** *** 236,241 **** --- 236,242 ---- TEST_CIL /* we enter with cpl locked */ bsfl %ecx, %ecx /* slow, but not worth optimizing */ + lock btrl %ecx, _ipending jnc doreti_next2 /* some intr cleared memory copy */ cmpl $NHWI, %ecx *************** *** 377,383 **** */ cli ICPL_LOCK ! orl $SWI_AST_PENDING, _ipending /* cpl is unlocked in doreti_exit */ subl %eax,%eax #ifdef CPL_AND_CML --- 378,384 ---- */ cli ICPL_LOCK ! MPLOCKED orl $SWI_AST_PENDING, _ipending /* cpl is unlocked in doreti_exit */ subl %eax,%eax #ifdef CPL_AND_CML --QTprm0S8XgL7H0Dt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 1:49:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from neutron.cichlids.com (as8-pri50.rp-plus.de [149.221.239.178]) by hub.freebsd.org (Postfix) with ESMTP id D106014CF9 for ; Fri, 2 Jul 1999 01:49:50 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id KAA02487; Fri, 2 Jul 1999 10:41:48 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id KAA00763; Thu, 12 Aug 1999 10:07:20 +0200 (CEST) (envelope-from alex) From: Alexander Langer Date: Thu, 12 Aug 1999 10:07:20 +0200 To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? Message-ID: <19990812100720.B707@cichlids.cichlids.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Matthew Jacob (mjacob@feral.com): > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking I got this very often the last days, too. Actually I try do downgrade to 3.2, because my machines reboots 3 times a day because of either this error or other things. -CURRENT actually is VERY unstable here. Alex -- ************** I doubt, therefore I might be. ************** *** Send email to to get PGP-Key *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 1:53:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AE89E14CF9 for ; Fri, 2 Jul 1999 01:53:28 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id EAA94262; Fri, 2 Jul 1999 04:51:07 -0400 (EDT) Date: Fri, 2 Jul 1999 04:51:07 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Dominic Mitchell Cc: current@FreeBSD.ORG Subject: Re: fetch(1) and realms with whitespace... In-Reply-To: <19990701120825.A41541@palmerharvey.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 1 Jul 1999, Dominic Mitchell wrote: > Is there any way to specify a realm with whitespace to fetch? I've > just had a fun time trying to do: > > % export HTTP_AUTH="basic:SunSolve Online:x:y" > % fetch -v http://online.sunsolve.sun.co.uk/whatever > senddoc: cannot authenticate with server > > Looking at the code it appears that there isn't a way to escape the > whitespace... Try the patch I've attached. I haven't tested it except to see that it compiles. > -- > Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator > > "How Unix vendors can ship ancient shells with no job control and no cursor > editing by default and still wonder why people buy NT is beyond me." - Alan Cox > -- > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > ********************************************************************** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ --- http.c.orig Fri Jul 2 04:08:04 1999 +++ http.c Fri Jul 2 04:44:10 1999 @@ -1682,6 +1682,17 @@ return EX_NOPERM; } +static inline char * +unescify(register char *s) { + char *o = s; + + for (; *s; s++) + if (*s < 0) + *s = -*s; + + return o; +} + static void parse_http_auth_env(const char *env, struct http_auth_head *ha_tqh) { @@ -1690,7 +1701,15 @@ struct http_auth_method *ham; nenv = alloca(strlen(env) + 1); - strcpy(nenv, env); + for (p = nenv; *p; env++) + if (!*env) + *p = '\0'; + else if (*env != '\\') + *p++ = *env; + else if (*++env) + *p++ = -*env; + else + *p = '\0'; while ((p = strsep(&nenv, " \t")) != 0) { scheme = strsep(&p, ":"); @@ -1707,9 +1726,9 @@ if (ham == 0) continue; ha = safe_malloc(sizeof *ha); - ha->ha_scheme = safe_strdup(scheme); - ha->ha_realm = safe_strdup(realm); - ha->ha_params = params ? safe_strdup(params) : 0; + ha->ha_scheme = unescify(safe_strdup(scheme)); + ha->ha_realm = unescify(safe_strdup(realm)); + ha->ha_params = params ? unescify(safe_strdup(params)) : 0; ha->ha_ham = ham; TAILQ_INSERT_TAIL(ha_tqh, ha, ha_link); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 2: 3: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (Postfix) with ESMTP id 2ACAF14CF3 for ; Fri, 2 Jul 1999 02:02:53 -0700 (PDT) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id LAA23645; Fri, 2 Jul 1999 11:02:43 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990812100720.B707@cichlids.cichlids.com> Date: Fri, 02 Jul 1999 11:02:43 +0200 (MEST) Organization: University of Bayreuth From: Werner Griessl To: Alexander Langer Subject: Re: this of interest to anyone? Cc: freebsd-current@FreeBSD.ORG, Matthew Jacob Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Aug-99 Alexander Langer wrote: > Thus spake Matthew Jacob (mjacob@feral.com): > >> panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > > I got this very often the last days, too. > > Actually I try do downgrade to 3.2, because my machines reboots 3 > times a day because of either this error or other things. -CURRENT > actually is VERY unstable here. > > Alex > -- > ************** I doubt, therefore I might be. ************** > *** Send email to to get PGP-Key *** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- Had it also the last few day's, but no longer since yesterday (Jul 1 1999). BTW: Your date is !!! 12 Aug 1999 !!!! Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 2:28:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 3448814F42 for ; Fri, 2 Jul 1999 02:28:55 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA27946; Fri, 2 Jul 1999 11:28:39 +0200 (MET DST) Date: Fri, 2 Jul 1999 11:28:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Alexander Langer Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: <19990812100720.B707@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are still running current, please cvsup the newest sources. This problem has been solved in the past few days. It showed up on saturday evening after a commit on McKusick and most of the problem area's have been identified and tracked down. There might still be one or two remaining, but these should be very infrequent. Nick On Thu, 12 Aug 1999, Alexander Langer wrote: > Thus spake Matthew Jacob (mjacob@feral.com): > > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > > I got this very often the last days, too. > > Actually I try do downgrade to 3.2, because my machines reboots 3 > times a day because of either this error or other things. -CURRENT > actually is VERY unstable here. > > Alex > -- > ************** I doubt, therefore I might be. ************** > *** Send email to to get PGP-Key *** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 4:20:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-238.birch.net [216.212.1.238]) by hub.freebsd.org (Postfix) with ESMTP id 2610C14C93 for ; Fri, 2 Jul 1999 04:20:03 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id GAA01178; Fri, 2 Jul 1999 06:16:43 -0500 (CDT) From: Jim Bryant Message-Id: <199907021116.GAA01178@argus.tfs.net> Subject: Re: this of interest to anyone? In-Reply-To: from Nick Hibma at "Jul 2, 99 11:28:37 am" To: nick.hibma@jrc.it Date: Fri, 2 Jul 1999 06:15:49 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG interesting. i thought this was a netscape issue. In reply: > If you are still running current, please cvsup the newest sources. This > problem has been solved in the past few days. It showed up on saturday > evening after a commit on McKusick and most of the problem area's have > been identified and tracked down. > > There might still be one or two remaining, but these should be very > infrequent. > > Nick > > > On Thu, 12 Aug 1999, Alexander Langer wrote: > > > Thus spake Matthew Jacob (mjacob@feral.com): > > > > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > > > > I got this very often the last days, too. > > > > Actually I try do downgrade to 3.2, because my machines reboots 3 > > times a day because of either this error or other things. -CURRENT > > actually is VERY unstable here. > > > > Alex > > -- > > ************** I doubt, therefore I might be. ************** > > *** Send email to to get PGP-Key *** > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > -- > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 5: 1: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id BF73314CCE for ; Fri, 2 Jul 1999 05:00:57 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA25856; Fri, 2 Jul 1999 22:00:33 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma025850; Fri, 2 Jul 99 22:00:07 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA19109 for ; Fri, 2 Jul 1999 22:00:07 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA28256 for ; Fri, 2 Jul 1999 22:00:06 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA06282; Fri, 2 Jul 1999 22:00:05 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199907021200.WAA06282@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Stuck in "objtrm" Date: Fri, 02 Jul 1999 22:00:04 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an old 486 here that I thrash to death occasionally. Well, at least I try to get it to page to death. I started a make world last week and forgot about it. Today I noticed that it's been stuck for most of the week. Almost everything is fine, but one cc1 process is stuck in "objtrm". Oh, and I hung a "cat /proc/31624/map", too, trying to get some details (now stuck in "thrd_sleep"). So, am I just tripping over some old long-fixed bug? Or is this a new one worth investigating? The kernel is from 1999/06/16 (just before the vfs_cluster.c commit). Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 6:45:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from neutron.cichlids.com (as3-024.rp-plus.de [149.221.238.216]) by hub.freebsd.org (Postfix) with ESMTP id 983E014D5D for ; Fri, 2 Jul 1999 06:45:27 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id PAA00758; Fri, 2 Jul 1999 15:46:31 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id PAA00495; Fri, 2 Jul 1999 15:43:37 +0200 (CEST) (envelope-from alex) Date: Fri, 2 Jul 1999 15:43:37 +0200 From: Alexander Langer To: Nick Hibma Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? Message-ID: <19990702154337.A468@cichlids.cichlids.com> References: <19990812100720.B707@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i In-Reply-To: X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Nick Hibma (nick.hibma@jrc.it): Hello again! > If you are still running current, please cvsup the newest sources. This > problem has been solved in the past few days. It showed up on saturday > evening after a commit on McKusick and most of the problem area's have > been identified and tracked down. The kernel that made the problem is 2 days old. (From Wednesday). Actually, I even can´t compile a new kernel/world, cause it reboots and hangs all the time. Nice. I´ll try further Alex -- ************** I doubt, therefore I might be. ************** *** Send email to to get PGP-Key *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 7: 3:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (Postfix) with ESMTP id AA30B14D05 for ; Fri, 2 Jul 1999 07:03:46 -0700 (PDT) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id QAA29307; Fri, 2 Jul 1999 16:03:35 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990702154337.A468@cichlids.cichlids.com> Date: Fri, 02 Jul 1999 16:03:35 +0200 (MEST) Organization: University of Bayreuth From: Werner Griessl To: Alexander Langer Subject: Re: this of interest to anyone? Cc: freebsd-current@FreeBSD.ORG, Matthew Jacob , Nick Hibma Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Jul-99 Alexander Langer wrote: > Thus spake Nick Hibma (nick.hibma@jrc.it): > > Hello again! > >> If you are still running current, please cvsup the newest sources. This >> problem has been solved in the past few days. It showed up on saturday >> evening after a commit on McKusick and most of the problem area's have >> been identified and tracked down. > > The kernel that made the problem is 2 days old. (From Wednesday). > Actually, I even can´t compile a new kernel/world, cause it reboots and > hangs all the time. > > Nice. I´ll try further > > Alex > -- > ************** I doubt, therefore I might be. ************** > *** Send email to to get PGP-Key *** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- boot with "kernel.old" and try again. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 9:25:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id 39641156E5 for ; Fri, 2 Jul 1999 09:25:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA03124; Fri, 2 Jul 1999 09:21:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907021621.JAA03124@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alexander Langer Cc: Nick Hibma , Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-reply-to: Your message of "Fri, 02 Jul 1999 15:43:37 +0200." <19990702154337.A468@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 02 Jul 1999 09:21:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > = > The kernel that made the problem is 2 days old. (From Wednesday). > Actually, I even can=B4t compile a new kernel/world, cause it reboots a= nd > hangs all the time. = Welcome to -current. Time to learn about keeping a working kernel = around at all times. -- = \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.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 2 9:40:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7A0E514C42 for ; Fri, 2 Jul 1999 09:40:09 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2619E64; Sat, 3 Jul 1999 00:40:08 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: Alexander Langer , Nick Hibma , Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-reply-to: Your message of "Fri, 02 Jul 1999 09:21:47 MST." <199907021621.JAA03124@dingo.cdrom.com> Content-Transfer-Encoding: 8bit Date: Sat, 03 Jul 1999 00:40:08 +0800 From: Peter Wemm Message-Id: <19990702164008.2619E64@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > The kernel that made the problem is 2 days old. (From Wednesday). > > Actually, I even can´t compile a new kernel/world, cause it reboots and > > hangs all the time. > > Welcome to -current. Time to learn about keeping a working kernel > around at all times. I'll reiterate that. I'm sorry you're having trouble, but this is the very reason why we scream out very loudly and clearly that current is for developers and people who are prepared to live on the bleeding edge and know how to deal with problems or back out when they run into trouble. A few key suggestions for people still along for the ride: 1: When you've got a good running kernel that you're happy with, do yourself a big favour and copy it from /kernel to /kernel.ok or something like that. So, when you manage to get a bad /kernel and /kernel.old, you've still got a fallback that doesn't mean resorting to a fixit disk boot. 2: at least try and keep tabs on the current mailing list. Even if you don't pay a lot of attention, look for 'HEADS_UP' warnings and people having trouble. It's always a good idea to to a skim before a kernel rebuild or make world. 3: Always keep tabs on your cvsup log. If you see a lot of commits to the kernel (src/sys), make *sure* you're up to date on current mail. It often pays to let the dust settle. This doesn't mean it's OK for committers to screw things up for fun, but we're only human. We do try and keep it in fairly good condition (remember, the developers depend on it working for development), but mistakes happen.. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 10:19:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 0A0D8152AA for ; Fri, 2 Jul 1999 10:19:41 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id KAA01510; Fri, 2 Jul 1999 10:15:35 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id KAA29984; Fri, 2 Jul 1999 10:19:39 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id KAA15349; Fri, 2 Jul 1999 10:17:07 -0700 To: nick.hibma@jrc.it Cc: alex@cichlids.com, mjacob@feral.com, freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: Your message of "Fri, 2 Jul 1999 11:28:37 +0200 (MET DST)" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990702101706V.thomma@baynetworks.com> Date: Fri, 02 Jul 1999 10:17:06 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 145 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There might still be one or two remaining, but these should be very > infrequent. The panice happened during make world with two setiathome clients. Is this a new one or one known to be fixed? Thanks PS: June 30 kernel does not have this problem so far. Tammy Stack trace and dmesg follows: poko# gdb -k kernel.3 vmcore.3 GNU gdb 4.18 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)... SMP 2 cpus IdlePTD 3223552 initial pcb at 29bac0 panicstr: from debugger panic messages: --- panic: lockmgr: pid 12933, not exclusive lock holder 12948 unlocking mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 panic: from debugger mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 dumping to dev (4,131073), offset 262144 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc01538fc in boot () (kgdb) where #0 0xc01538fc in boot () #1 0xc0153b7d in panic () #2 0xc012d7c1 in db_panic () #3 0xc012d761 in db_command () #4 0xc012d826 in db_command_loop () #5 0xc012f987 in db_trap () #6 0xc0216d16 in kdb_trap () #7 0xc022c48c in trap () #8 0xc0216f9b in Debugger () #9 0xc0153b74 in panic () #10 0xc014f4d4 in lockmgr () #11 0xc0201cca in relpbuf () #12 0xc01f6a70 in swp_pager_async_iodone () #13 0xc0174633 in biodone () #14 0xc0125c9d in dadone () #15 0xc0121973 in camisr () #16 0xc0121785 in swi_cambio () #17 0xc021c61e in doreti_swi () #18 0x80828fb in ?? () #19 0x805e004 in ?? () #20 0x805bc1e in ?? () #21 0x805c492 in ?? () #22 0x805c373 in ?? () #23 0x80490ff in ?? () ---Type to continue, or q to quit--- #24 0x8084e3e in ?? () #25 0x80878b9 in ?? () #26 0x80480e9 in ?? () (kgdb) quit And dmesg output from a new kernel which survived make world: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #21: Wed Jun 30 21:38:50 PDT 1999 root@poko.pochi.com:/usr/src/sys/compile/POKO Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff real memory = 134217728 (131072K bytes) avail memory = 127401984 (124416K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0301000. Pentium Pro MTRR support enabled, default memory type is uncacheable ccd0-3: Concatenated disk drivers Probing for PnP devices: CSN 1 Vendor ID: CSC0b35 [0x350b630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 fxp0: irq 18 at device 6.0 on pci0 fxp0: Ethernet address 00:a0:c9:55:32:47 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip1: irq 10 at device 7.2 on pci0 ahc0: irq 17 at device 9.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: irq 16 at device 11.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> at fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8705MB (17829870 512 byte sectors: 255H 63S/T 1109C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da2 at ahc0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 10:20:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 597C11577F for ; Fri, 2 Jul 1999 10:20:38 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA57460; Fri, 2 Jul 1999 10:20:20 -0700 (PDT) (envelope-from dillon) Date: Fri, 2 Jul 1999 10:20:20 -0700 (PDT) From: Matthew Dillon Message-Id: <199907021720.KAA57460@apollo.backplane.com> To: Peter Wemm Cc: Mike Smith , Alexander Langer , Nick Hibma , Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? References: <19990702164008.2619E64@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This doesn't mean it's OK for committers to screw things up for fun, but :we're only human. We do try and keep it in fairly good condition :(remember, the developers depend on it working for development), but :mistakes happen.. : :Cheers, :-Peter Hey, I just had a thought... and a question. When we are using cvsup to keep a local CVS reposity in sync, can we tag our local CVS resposity without cvsup deleting the tags? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 10:37:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id AD80F14D34 for ; Fri, 2 Jul 1999 10:37:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0C28F64; Sat, 3 Jul 1999 01:37:15 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Mike Smith , Alexander Langer , Nick Hibma , Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-reply-to: Your message of "Fri, 02 Jul 1999 10:20:20 MST." <199907021720.KAA57460@apollo.backplane.com> Date: Sat, 03 Jul 1999 01:37:15 +0800 From: Peter Wemm Message-Id: <19990702173715.0C28F64@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :This doesn't mean it's OK for committers to screw things up for fun, but > :we're only human. We do try and keep it in fairly good condition > :(remember, the developers depend on it working for development), but > :mistakes happen.. > : > :Cheers, > :-Peter > > Hey, I just had a thought... and a question. When we are using cvsup to > keep a local CVS reposity in sync, can we tag our local CVS resposity > without cvsup deleting the tags? > > -Matt Yes... And you can even branch the local cvs repo and have cvsup work around it.. The trick is to have a non conflicting magic branch number. Try setting CVS_LOCAL_BRANCH_NUM=1000 or so in the environment and do a tag -b. If I remember correctly, you need to disable the 'delete' mode. Hmm: delete The presence of this keyword gives cvsup permission to delete files. If it is missing, no files will be deleted. The presence of the delete keyword puts cvsup into so-called exact mode. In exact mode, CVSup does its best to make the client's files correspond to those on the server. This in- cludes deleting individual deltas and symbolic tags from RCS ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ files, as well as deleting entire files. In exact mode, CVSup verifies every edited file with a checksum, to ensure that the edits have produced a file identical to the master copy on the server. If the checksum test fails for a file, then CVSup falls back upon transferring the entire file. I recall testing this when John was first working on cvsup (that's where the CVS_LOCAL_BRANCH_NUM hack came from :-), and it worked then. I don't know how well (or if) it works now. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 10:54:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EF8F14C89 for ; Fri, 2 Jul 1999 10:54:37 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-140.skylink.it [194.185.55.140]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id TAA11484; Fri, 2 Jul 1999 19:53:47 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id TAA04627; Fri, 2 Jul 1999 19:54:50 +0200 (CEST) Date: Fri, 2 Jul 1999 19:54:50 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: jbryant@tfs.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: <199907021116.GAA01178@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What makes you think that? > interesting. i thought this was a netscape issue. > > In reply: > > If you are still running current, please cvsup the newest sources. This > > problem has been solved in the past few days. It showed up on saturday > > evening after a commit on McKusick and most of the problem area's have > > been identified and tracked down. > > > > There might still be one or two remaining, but these should be very > > infrequent. > > > > Nick > > > > > > On Thu, 12 Aug 1999, Alexander Langer wrote: > > > > > Thus spake Matthew Jacob (mjacob@feral.com): > > > > > > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > > > > > > I got this very often the last days, too. > > > > > > Actually I try do downgrade to 3.2, because my machines reboots 3 > > > times a day because of either this error or other things. -CURRENT > > > actually is VERY unstable here. > > > > > > Alex > > > -- > > > ************** I doubt, therefore I might be. ************** > > > *** Send email to to get PGP-Key *** > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > -- > > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ------------------------------------------------------------------------------ > Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw > voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant > ------------------------------------------------------------------------------ > HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- e-Mail: hibma@skylink.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 2 11: 5: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id 7BBD115715; Fri, 2 Jul 1999 11:04:52 -0700 (PDT) (envelope-from k@numeri.campus.luth.se) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id UAA06785; Fri, 2 Jul 1999 20:04:49 +0200 (CEST) (envelope-from k@numeri.campus.luth.se) Message-Id: <199907021804.UAA06785@numeri.campus.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org Cc: grog@freebsd.org Subject: buildworld fails in sbin/vinum Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 02 Jul 1999 20:04:49 +0200 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi When trying to build a newly updated world I get the following error, whi= ch I = belive was introduced in the latest commit by grog. The case may be that vext.h did not get commited. = (eg. I think "extern int stats" should be "extern int sflag" now) = /K =3D=3D=3D> sbin/vinum cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG = -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/v.c cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG = -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/list.c cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG = -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/../../sys/dev/v= inum/v inumparser.c cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG = -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/../../sys/dev/v= inum/v inumutil.c /usr/src/sbin/vinum/list.c: In function `vinum_list': /usr/src/sbin/vinum/list.c:87: `sflag' undeclared (first use in this func= tion) /usr/src/sbin/vinum/list.c:87: (Each undeclared identifier is reported on= ly = once /usr/src/sbin/vinum/list.c:87: for each function it appears in.) /usr/src/sbin/vinum/list.c: In function `vinum_ldi': /usr/src/sbin/vinum/list.c:181: `sflag' undeclared (first use in this fun= ction) /usr/src/sbin/vinum/list.c: In function `vinum_lvi': /usr/src/sbin/vinum/list.c:273: `sflag' undeclared (first use in this fun= ction) cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG = -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/commands.c /usr/src/sbin/vinum/v.c:263: `vinum_concat' undeclared here (not in a fun= ction) /usr/src/sbin/vinum/v.c:263: initializer element for `funkeys[26].fun' is= not = constant /usr/src/sbin/vinum/v.c:264: `vinum_stripe' undeclared here (not in a fun= ction) /usr/src/sbin/vinum/v.c:264: initializer element for `funkeys[27].fun' is= not = constant /usr/src/sbin/vinum/v.c:265: `vinum_mirror' undeclared here (not in a fun= ction) /usr/src/sbin/vinum/v.c:265: initializer element for `funkeys[28].fun' is= not = constant gzip -cn /usr/src/sbin/vinum/vinum.8 > vinum.8.gz /usr/src/sbin/vinum/list.c: In function `vinum_lpi': /usr/src/sbin/vinum/list.c:392: `sflag' undeclared (first use in this fun= ction) /usr/src/sbin/vinum/list.c: In function `vinum_lsi': /usr/src/sbin/vinum/list.c:545: `sflag' undeclared (first use in this fun= ction) /usr/src/sbin/vinum/list.c: In function `listconfig': /usr/src/sbin/vinum/list.c:627: `sflag' undeclared (first use in this fun= ction) *** Error code 1 *** Error code 1 /usr/src/sbin/vinum/commands.c: In function `genvolname': /usr/src/sbin/vinum/commands.c:1208: `objectname' undeclared (first use i= n = this function) /usr/src/sbin/vinum/commands.c:1208: (Each undeclared identifier is repor= ted = only once /usr/src/sbin/vinum/commands.c:1208: for each function it appears in.) /usr/src/sbin/vinum/commands.c: In function `vinum_concat': /usr/src/sbin/vinum/commands.c:1292: `objectname' undeclared (first use i= n = this function) /usr/src/sbin/vinum/commands.c:1331: warning: implicit declaration of fun= ction = `find_drive_by_devname' /usr/src/sbin/vinum/commands.c:1331: warning: assignment makes pointer fr= om = integer without a cast /usr/src/sbin/vinum/commands.c: In function `vinum_stripe': /usr/src/sbin/vinum/commands.c:1406: `objectname' undeclared (first use i= n = this function) /usr/src/sbin/vinum/commands.c:1409: warning: assignment makes pointer fr= om = integer without a cast /usr/src/sbin/vinum/commands.c:1425: warning: implicit declaration of fun= ction = `min' /usr/src/sbin/vinum/commands.c:1466: warning: assignment makes pointer fr= om = integer without a cast /usr/src/sbin/vinum/commands.c: In function `vinum_mirror': /usr/src/sbin/vinum/commands.c:1541: `sflag' undeclared (first use in thi= s = function) /usr/src/sbin/vinum/commands.c:1563: `objectname' undeclared (first use i= n = this function) /usr/src/sbin/vinum/commands.c:1566: warning: assignment makes pointer fr= om = integer without a cast /usr/src/sbin/vinum/commands.c:1635: warning: assignment makes pointer fr= om = integer without a cast *** Error code 1 3 errors *** 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 11: 5:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 40CA414FF2 for ; Fri, 2 Jul 1999 11:05:10 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-140.skylink.it [194.185.55.140]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA11699; Fri, 2 Jul 1999 20:04:17 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id TAA04643; Fri, 2 Jul 1999 19:57:52 +0200 (CEST) Date: Fri, 2 Jul 1999 19:57:51 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Alexander Langer Cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: this of interest to anyone? In-Reply-To: <19990702154337.A468@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try booting kernel.old . It's supposed to be the previous kernel. If that does not work, I can send you one that does work, so you can at least compile a new kernel. Nick On Fri, 2 Jul 1999, Alexander Langer wrote: > Thus spake Nick Hibma (nick.hibma@jrc.it): >=20 > Hello again! >=20 > > If you are still running current, please cvsup the newest sources. This > > problem has been solved in the past few days. It showed up on saturday > > evening after a commit on McKusick and most of the problem area's have > > been identified and tracked down. >=20 > The kernel that made the problem is 2 days old. (From Wednesday). > Actually, I even can=B4t compile a new kernel/world, cause it reboots and > hangs all the time.=20 >=20 > Nice. I=B4ll try further >=20 > Alex > --=20 > ************** I doubt, therefore I might be. ************** > *** Send email to to get PGP-Key *** >=20 --=20 e-Mail: hibma@skylink.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 2 11: 5:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 818AA15892 for ; Fri, 2 Jul 1999 11:05:32 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA24090; Fri, 2 Jul 1999 11:05:16 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Fri, 2 Jul 1999 11:05:16 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Greg Lehey Cc: freebsd-current@FreeBSD.ORG Subject: vinum stopping world build In-Reply-To: <19990702110233.J87392@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I consistently get the following during a 'make world' on the most recent -current: ===> sbin/vinum cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/v.c /usr/src/sbin/vinum/v.c:263: `vinum_concat' undeclared here (not in a function) /usr/src/sbin/vinum/v.c:263: initializer element for `funkeys[26].fun' is not constant /usr/src/sbin/vinum/v.c:264: `vinum_stripe' undeclared here (not in a function) /usr/src/sbin/vinum/v.c:264: initializer element for `funkeys[27].fun' is not constant /usr/src/sbin/vinum/v.c:265: `vinum_mirror' undeclared here (not in a function) /usr/src/sbin/vinum/v.c:265: initializer element for `funkeys[28].fun' is not constant *** Error code 1 Stop. *** Error code 1 Still happens even after I delete /usr/obj. I also did a 'make clean' in /usr/src just for fun. I'm not doing anything unusual, here is my make.conf: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe USA_RESIDENT= YES TOP_TABLE_SIZE= 101 Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 11:36:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 43E3014CE0 for ; Fri, 2 Jul 1999 11:36:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA17372; Fri, 2 Jul 1999 11:36:11 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA17158; Fri, 2 Jul 1999 11:36:10 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 2 Jul 1999 11:36:10 -0700 (PDT) Message-Id: <199907021836.LAA17158@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: this of interest to anyone? In-Reply-To: <199907021720.KAA57460@apollo.backplane.com> References: <19990702164008.2619E64@overcee.netplex.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199907021720.KAA57460@apollo.backplane.com>, Matthew Dillon wrote: > Hey, I just had a thought... and a question. When we are using > cvsup to keep a local CVS reposity in sync, can we tag our local > CVS resposity without cvsup deleting the tags? Yes, you can do it if you're careful. There's a section "Local Modifications in your CVS Repository" in the CVSup FAQ that talks about it. http://www.polstra.com/projects/freeware/CVSup/ John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 12:22:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 8989114BD5 for ; Fri, 2 Jul 1999 12:22:24 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id PAA04809; Fri, 2 Jul 1999 15:22:27 -0400 (EDT) Date: Fri, 2 Jul 1999 15:22:27 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: current@FreeBSD.org Cc: grog@lemis.com Subject: world broken in vinum (PATCH) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the fix. I'm sure it's not absolutely the same as what Greg will have, but if anyone wants to commit it, it will fix world. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ --- src/sbin/vinum/vext.h.orig Fri Jul 2 15:06:24 1999 +++ src/sbin/vinum/vext.h Fri Jul 2 15:12:12 1999 @@ -80,6 +80,9 @@ void vinum_makedev(int argc, char *argv[], char *arg0[]); void vinum_help(int argc, char *argv[], char *arg0[]); void vinum_quit(int argc, char *argv[], char *arg0[]); +void vinum_concat(int argc, char *argv[], char *arg0[]); +void vinum_stripe(int argc, char *argv[], char *arg0[]); +void vinum_mirror(int argc, char *argv[], char *arg0[]); void vinum_setdaemon(int argc, char *argv[], char *arg0[]); void reset_volume_stats(int volno, int recurse); void reset_plex_stats(int plexno, int recurse); @@ -105,6 +108,7 @@ #endif void make_devices(void); void get_drive_info(struct drive *drive, int index); +struct drive *find_drive_by_devname(char *name); void get_sd_info(struct sd *sd, int index); void get_plex_sd_info(struct sd *sd, int plexno, int sdno); void get_plex_info(struct plex *plex, int index); @@ -145,3 +149,6 @@ extern int file_line; /* and line in input file (yes, this is tacky) */ extern char buffer[]; /* buffer to read in to */ + +extern int sflag; +extern char *objectname; --- src/sbin/vinum/commands.c.orig Fri Jul 2 15:13:19 1999 +++ src/sbin/vinum/commands.c Fri Jul 2 15:17:46 1999 @@ -1422,7 +1422,8 @@ } bigchunk = bigchunk > freelist.sectors ? bigchunk : freelist.sectors; /* max it */ } - maxsize = min(maxsize, bigchunk); /* this is as much as we can do */ + if (bigchunk < maxsize) /* this is as much as we can do */ + maxsize = bigchunk; } /* Now create the volume */ @@ -1580,7 +1581,8 @@ } bigchunk = bigchunk > freelist.sectors ? bigchunk : freelist.sectors; /* max it */ } - maxsize[o & 1] = min(maxsize[o & 1], bigchunk); /* get the maximum size of a subdisk */ + if (bigchunk < maxsize[o & 1]) /* get the maximum size of a subdisk */ + maxsize[o & 1] = bigchunk; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 12:26:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AE6BD14DE9 for ; Fri, 2 Jul 1999 12:26:32 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id PAA04868 for ; Fri, 2 Jul 1999 15:26:35 -0400 (EDT) Date: Fri, 2 Jul 1999 15:26:35 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Re: world broken in vinum (PATCH) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Jul 1999, Brian F. Feldman wrote: > Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > but if anyone wants to commit it, it will fix world. > I know I _could_ commit it, but it's someone else's work that's being actively maintained. It still does break world, but I don't think I have authority to commit over Greg's work. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17: 0:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BD42814D37; Fri, 2 Jul 1999 17:00:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA14399; Sat, 3 Jul 1999 09:30:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA01804; Sat, 3 Jul 1999 09:29:57 +0930 (CST) Date: Sat, 3 Jul 1999 09:29:57 +0930 From: Greg Lehey To: Johan Karlsson , Doug , "Brian F. Feldman" Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: buildworld fails in sbin/vinum Message-ID: <19990703092957.U87392@freebie.lemis.com> References: <19990702110233.J87392@freebie.lemis.com> <199907021804.UAA06785@numeri.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907021804.UAA06785@numeri.campus.luth.se>; from Johan Karlsson on Fri, Jul 02, 1999 at 08:04:49PM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 2 July 1999 at 20:04:49 +0200, Johan Karlsson wrote: > Hi > When trying to build a newly updated world I get the following error, which I > belive was introduced in the latest commit by grog. > The case may be that vext.h did not get commited. Indeed, that was the problem. Ugh. Pass me the pointy hat, please. > (eg. I think "extern int stats" should be "extern int sflag" now) That's one of them. There are others. On Friday, 2 July 1999 at 11:05:16 -0700, Doug wrote: > I consistently get the following during a 'make world' on the most > recent -current: > > > ===> sbin/vinum > cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/v.c That's another. On Friday, 2 July 1999 at 15:22:27 -0400, Brian F. Feldman wrote: > Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > but if anyone wants to commit it, it will fix world. Well, yes, but the result won't work. The sflag variable is what used to be called stats. But thanks for jumping in while I was asleep. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17: 0:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BD42814D37; Fri, 2 Jul 1999 17:00:04 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA14399; Sat, 3 Jul 1999 09:30:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA01804; Sat, 3 Jul 1999 09:29:57 +0930 (CST) Date: Sat, 3 Jul 1999 09:29:57 +0930 From: Greg Lehey To: Johan Karlsson , Doug , "Brian F. Feldman" Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: buildworld fails in sbin/vinum Message-ID: <19990703092957.U87392@freebie.lemis.com> References: <19990702110233.J87392@freebie.lemis.com> <199907021804.UAA06785@numeri.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907021804.UAA06785@numeri.campus.luth.se>; from Johan Karlsson on Fri, Jul 02, 1999 at 08:04:49PM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Format recovered--see http://www.lemis.com/email/email-format.html] On Friday, 2 July 1999 at 20:04:49 +0200, Johan Karlsson wrote: > Hi > When trying to build a newly updated world I get the following error, which I > belive was introduced in the latest commit by grog. > The case may be that vext.h did not get commited. Indeed, that was the problem. Ugh. Pass me the pointy hat, please. > (eg. I think "extern int stats" should be "extern int sflag" now) That's one of them. There are others. On Friday, 2 July 1999 at 11:05:16 -0700, Doug wrote: > I consistently get the following during a 'make world' on the most > recent -current: > > > ===> sbin/vinum > cc -O -pipe -I/usr/src/sbin/vinum/../../sys -g -Wall -DVINUMDEBUG -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/vinum/v.c That's another. On Friday, 2 July 1999 at 15:22:27 -0400, Brian F. Feldman wrote: > Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > but if anyone wants to commit it, it will fix world. Well, yes, but the result won't work. The sflag variable is what used to be called stats. But thanks for jumping in while I was asleep. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17: 2:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2DEBC150B4 for ; Fri, 2 Jul 1999 17:02:24 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA14407; Sat, 3 Jul 1999 09:32:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA01833; Sat, 3 Jul 1999 09:32:23 +0930 (CST) Date: Sat, 3 Jul 1999 09:32:23 +0930 From: Greg Lehey To: "Brian F. Feldman" Cc: current@FreeBSD.ORG Subject: Fixing other people's code (was: world broken in vinum (PATCH)) Message-ID: <19990703093223.V87392@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Fri, Jul 02, 1999 at 03:26:35PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: > On Fri, 2 Jul 1999, Brian F. Feldman wrote: > >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, >> but if anyone wants to commit it, it will fix world. > > I know I _could_ commit it, but it's someone else's work that's being actively > maintained. It still does break world, but I don't think I have authority to > commit over Greg's work. I personally think that, in such a case, you'd be justified to commit it as a temporary measure. Due to the difference in time zones, this has hit people while I've been asleep. That doesn't mean the commit would stay, of course, but at least it would save people unnecessary pain. Note, of course, that I have now committed the correct file, which I had forgotten last night. What do you others think? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17: 9:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 37D731516D for ; Fri, 2 Jul 1999 17:09:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA01898; Fri, 2 Jul 1999 17:04:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907030004.RAA01898@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-reply-to: Your message of "Sat, 03 Jul 1999 09:32:23 +0930." <19990703093223.V87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jul 1999 17:04:45 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? It's your call as the module owner; some others are less likely to be reasonable about it, but I think most aren't really that touchy. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.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 2 17:11:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (unknown [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 1A1B515080 for ; Fri, 2 Jul 1999 17:11:29 -0700 (PDT) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id AAA27899; Sat, 3 Jul 1999 00:09:53 GMT Date: Sat, 3 Jul 1999 00:09:53 +0000 (GMT) From: Ben Rosengart To: Greg Lehey Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <19990703093223.V87392@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Greg Lehey wrote: > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? Was the fix that wasn't yours correct? 'Cause I'd rather have code that doesn't compile than code that compiles but is subtly wrong. -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, 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 2 17:13:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D70D214D37 for ; Fri, 2 Jul 1999 17:13:34 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA01148; Fri, 2 Jul 1999 17:13:21 -0700 Date: Fri, 2 Jul 1999 17:12:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <19990703093223.V87392@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: > > On Fri, 2 Jul 1999, Brian F. Feldman wrote: > > > >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > >> but if anyone wants to commit it, it will fix world. > > > > I know I _could_ commit it, but it's someone else's work that's being actively > > maintained. It still does break world, but I don't think I have authority to > > commit over Greg's work. > > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? opinion: If it's really blocking folks because things don't compile, it is always acceptable to do what you need to do- the tree should always compile even if -current. If the system doesn't boot because of change, then that's an obvious one too. If things work differently or not as well, but things are more or less working, it's not an emergency, so leave it for the author to fix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17:18: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 60DA214D37 for ; Fri, 2 Jul 1999 17:18:02 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id RAA04672; Fri, 2 Jul 1999 17:17:30 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907030017.RAA04672@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-reply-to: Your message of "Sat, 03 Jul 1999 09:32:23 +0930." <19990703093223.V87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jul 1999 17:17:30 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In this case where the module is actively being maintained people can afford to wait and an iterim bandage-type style email posting is sufficient . --------- Amancio's Latest mantra on his DSL line: Live Long and Prosperous !! > On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: > > On Fri, 2 Jul 1999, Brian F. Feldman wrote: > > > >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > >> but if anyone wants to commit it, it will fix world. > > > > I know I _could_ commit it, but it's someone else's work that's being actively > > maintained. It still does break world, but I don't think I have authority to > > commit over Greg's work. > > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Amancio Hasty ahasty@mindspring.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 2 17:30:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 91C7415199 for ; Fri, 2 Jul 1999 17:30:19 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA14557; Sat, 3 Jul 1999 10:00:18 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA02130; Sat, 3 Jul 1999 10:00:17 +0930 (CST) Date: Sat, 3 Jul 1999 10:00:17 +0930 From: Greg Lehey To: Ben Rosengart Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) Message-ID: <19990703100017.A87392@freebie.lemis.com> References: <19990703093223.V87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Ben Rosengart on Sat, Jul 03, 1999 at 12:09:53AM +0000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 0:09:53 +0000, Ben Rosengart wrote: > On Sat, 3 Jul 1999, Greg Lehey wrote: > >> I personally think that, in such a case, you'd be justified to commit >> it as a temporary measure. Due to the difference in time zones, this >> has hit people while I've been asleep. That doesn't mean the commit >> would stay, of course, but at least it would save people unnecessary >> pain. Note, of course, that I have now committed the correct file, >> which I had forgotten last night. >> >> What do you others think? > > Was the fix that wasn't yours correct? No. > 'Cause I'd rather have code that doesn't compile than code that > compiles but is subtly wrong. Well, you can now have code that compiles and is correct :-) Seriously, the only problem with Brian's fix was that it added a new variable. It would have made the stats list functions not work. I think that, for the period of time it would have been there, it would have been the right thing to do: most people don't use Vinum, so the breakage there is just a thorn in their side. For those who do, they'll notice the problem and report it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17:31: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 8FA4314D37 for ; Fri, 2 Jul 1999 17:30:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA14570; Sat, 3 Jul 1999 10:00:55 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA02142; Sat, 3 Jul 1999 10:00:55 +0930 (CST) Date: Sat, 3 Jul 1999 10:00:55 +0930 From: Greg Lehey To: Matthew Jacob Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) Message-ID: <19990703100055.B87392@freebie.lemis.com> References: <19990703093223.V87392@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Matt Jacob on Fri, Jul 02, 1999 at 05:12:56PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 2 July 1999 at 17:12:56 -0700, Matt Jacob wrote: >> On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: >>> On Fri, 2 Jul 1999, Brian F. Feldman wrote: >>> >>>> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, >>>> but if anyone wants to commit it, it will fix world. >>> >>> I know I _could_ commit it, but it's someone else's work that's being actively >>> maintained. It still does break world, but I don't think I have authority to >>> commit over Greg's work. >> >> I personally think that, in such a case, you'd be justified to commit >> it as a temporary measure. Due to the difference in time zones, this >> has hit people while I've been asleep. That doesn't mean the commit >> would stay, of course, but at least it would save people unnecessary >> pain. Note, of course, that I have now committed the correct file, >> which I had forgotten last night. >> >> What do you others think? > > opinion: > > If it's really blocking folks because things don't compile, it is always > acceptable to do what you need to do- the tree should always compile even > if -current. If the system doesn't boot because of change, then that's an > obvious one too. If things work differently or not as well, but things > are more or less working, it's not an emergency, so leave it for the > author to fix. That looks reasonable. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 17:33:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D55A1515C for ; Fri, 2 Jul 1999 17:33:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA01237; Fri, 2 Jul 1999 17:33:37 -0700 Date: Fri, 2 Jul 1999 17:33:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me add to this: > opinion: > > If it's really blocking folks because things don't compile, it is always > acceptable to do what you need to do- the tree should always compile even > if -current. If the system doesn't boot because of change, then that's an > obvious one too. If things work differently or not as well, but things > are more or less working, it's not an emergency, so leave it for the > author to fix.... ...always modulo a short delay (call it a couple of hours) after reporting the problem... after all, you don't *know* that the update isn't finished and that other things are coming down the pipe... but a couple of hours leaves really the most reasonable time for an integration to complete and the author to have had lunch in between. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 18:47:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3EF5B151D5 for ; Fri, 2 Jul 1999 18:47:48 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA13173; Fri, 2 Jul 1999 21:47:48 -0400 (EDT) Date: Fri, 2 Jul 1999 21:47:48 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <19990703093223.V87392@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Greg Lehey wrote: > On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: > > On Fri, 2 Jul 1999, Brian F. Feldman wrote: > > > >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > >> but if anyone wants to commit it, it will fix world. > > > > I know I _could_ commit it, but it's someone else's work that's being actively > > maintained. It still does break world, but I don't think I have authority to > > commit over Greg's work. > > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. This is exactly how I felt. I knew that what I was doing was correct, even if it wasn't the same as what you had, and you would fix it up when you had the chance. However, I had no case to set a precedent of what to do; last time vinum was broken for a long time because phk's changes didn't get reviewed for a while; he didn't want things to go wrong, so he didn't commit it. This was simpler, but I didn't want to do things that are wrong. > > What do you others think? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 19:31:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 86CD914CAF for ; Fri, 2 Jul 1999 19:31:36 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA20132; Fri, 2 Jul 1999 22:31:34 -0400 (EDT) Date: Fri, 2 Jul 1999 22:31:34 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Matthew Jacob Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Jul 1999, Matthew Jacob wrote: > > On Friday, 2 July 1999 at 15:26:35 -0400, Brian F. Feldman wrote: > > > On Fri, 2 Jul 1999, Brian F. Feldman wrote: > > > > > >> Here's the fix. I'm sure it's not absolutely the same as what Greg will have, > > >> but if anyone wants to commit it, it will fix world. > > > > > > I know I _could_ commit it, but it's someone else's work that's being actively > > > maintained. It still does break world, but I don't think I have authority to > > > commit over Greg's work. I have NO idea what I meant by that wording. My change fixed the breakage in make world. > > > > I personally think that, in such a case, you'd be justified to commit > > it as a temporary measure. Due to the difference in time zones, this > > has hit people while I've been asleep. That doesn't mean the commit > > would stay, of course, but at least it would save people unnecessary > > pain. Note, of course, that I have now committed the correct file, > > which I had forgotten last night. > > > > What do you others think? > > opinion: > > If it's really blocking folks because things don't compile, it is always > acceptable to do what you need to do- the tree should always compile even > if -current. If the system doesn't boot because of change, then that's an > obvious one too. If things work differently or not as well, but things > are more or less working, it's not an emergency, so leave it for the > author to fix. > Sorry for the aforementioned REALLY messed-up language. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 19:36:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id B670114CAF for ; Fri, 2 Jul 1999 19:36:41 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id WAA20204; Fri, 2 Jul 1999 22:36:40 -0400 (EDT) Date: Fri, 2 Jul 1999 22:36:40 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Matthew Jacob Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Jul 1999, Matthew Jacob wrote: > > > Let me add to this: > > opinion: > > > > If it's really blocking folks because things don't compile, it is always > > acceptable to do what you need to do- the tree should always compile even > > if -current. If the system doesn't boot because of change, then that's an > > obvious one too. If things work differently or not as well, but things > > are more or less working, it's not an emergency, so leave it for the > > author to fix.... > > ...always modulo a short delay (call it a couple of hours) after reporting > the problem... after all, you don't *know* that the update isn't finished > and that other things are coming down the pipe... but a couple of hours > leaves really the most reasonable time for an integration to complete and > the author to have had lunch in between. > I worded my original post wrong; my change did fix world. Your second point (the "wait and see" approach) wouldn't apply in this case: Greg was asleep, and world was broken. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 19:49:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 9C43A14D74 for ; Fri, 2 Jul 1999 19:49:12 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id MAA01099; Sat, 3 Jul 1999 12:50:27 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199907030250.MAA01099@cimlogic.com.au> Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <19990703093223.V87392@freebie.lemis.com> from Greg Lehey at "Jul 3, 1999 09:32:23 am" To: grog@lemis.com (Greg Lehey) Date: Sat, 3 Jul 1999 12:50:26 +1000 (EST) Cc: green@unixhelp.org (Brian F. Feldman), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > I personally think that, in such a case, you'd be justified to commit > it as a temporary measure. Due to the difference in time zones, this > has hit people while I've been asleep. That doesn't mean the commit > would stay, of course, but at least it would save people unnecessary > pain. Note, of course, that I have now committed the correct file, > which I had forgotten last night. > > What do you others think? I think you shouldn't sleep. Well, you asked! -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 20: 4:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 29B8714D21 for ; Fri, 2 Jul 1999 20:04:33 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA15203; Sat, 3 Jul 1999 12:34:31 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA03055; Sat, 3 Jul 1999 12:34:31 +0930 (CST) Date: Sat, 3 Jul 1999 12:34:31 +0930 From: Greg Lehey To: John Birrell Cc: "Brian F. Feldman" , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) Message-ID: <19990703123431.P87392@freebie.lemis.com> References: <19990703093223.V87392@freebie.lemis.com> <199907030250.MAA01099@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907030250.MAA01099@cimlogic.com.au>; from John Birrell on Sat, Jul 03, 1999 at 12:50:26PM +1000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 12:50:26 +1000, John Birrell wrote: > Greg Lehey wrote: >> I personally think that, in such a case, you'd be justified to commit >> it as a temporary measure. Due to the difference in time zones, this >> has hit people while I've been asleep. That doesn't mean the commit >> would stay, of course, but at least it would save people unnecessary >> pain. Note, of course, that I have now committed the correct file, >> which I had forgotten last night. >> >> What do you others think? > > I think you shouldn't sleep. Yes, that's what I was told on my last assignment in China. > Well, you asked! And you answered :-) So where were you at 3 am this morning? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 20: 6:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 20A7314D21 for ; Fri, 2 Jul 1999 20:06:11 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.3/8.9.1) id NAA01247; Sat, 3 Jul 1999 13:07:34 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199907030307.NAA01247@cimlogic.com.au> Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <19990703123431.P87392@freebie.lemis.com> from Greg Lehey at "Jul 3, 1999 12:34:31 pm" To: grog@lemis.com (Greg Lehey) Date: Sat, 3 Jul 1999 13:07:34 +1000 (EST) Cc: jb@cimlogic.com.au (John Birrell), green@unixhelp.org (Brian F. Feldman), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > Well, you asked! > > And you answered :-) > > So where were you at 3 am this morning? In a land far, far, far away. Then I woke up. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 20:10:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CC00B14D21 for ; Fri, 2 Jul 1999 20:10:47 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA20786 for ; Fri, 2 Jul 1999 23:10:54 -0400 (EDT) Date: Fri, 2 Jul 1999 23:10:54 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: current@FreeBSD.org Subject: Just for the record (was: Re: Fixing other people's code (was: world broken in vinum (PATCH))) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the record, I was correct in the code. Hey, I do have a reputation, albeit not yet much of one! Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ ---------- Forwarded message ---------- Date: Sat, 3 Jul 1999 12:37:15 +0930 From: Greg Lehey To: Brian F. Feldman Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) On Friday, 2 July 1999 at 23:06:17 -0400, Brian F. Feldman wrote: > On Sat, 3 Jul 1999, Greg Lehey wrote: > >> On Friday, 2 July 1999 at 22:35:16 -0400, Brian F. Feldman wrote: >>> On Sat, 3 Jul 1999, Greg Lehey wrote: >>> >>>> On Saturday, 3 July 1999 at 0:09:53 +0000, Ben Rosengart wrote: >>>>> On Sat, 3 Jul 1999, Greg Lehey wrote: >>>>> >>>>> Was the fix that wasn't yours correct? >>>> >>>> No. >>>> >>>>> 'Cause I'd rather have code that doesn't compile than code that >>>>> compiles but is subtly wrong. >>>> >>>> Well, you can now have code that compiles and is correct :-) >>>> >>>> Seriously, the only problem with Brian's fix was that it added a new >>>> variable. It would have made the stats list functions not work. I >>> >>> Out of curiousity, what 'exactly' was wrong? >> >> I had a flag called 'stats', which was set by the -s flag. When I >> introduced the 'mirror' command, I used the -s flag to mean "create a >> striped plex". Obviously, the name 'stats' didn't fit this function, >> so I changed it to 'sflag'. Your fix introduced an additional flag, >> which wouldn't have been used. Hmmm, come to think of it, it might >> have worked anyway... we did have the definition after all. OK, I >> thought it wouldn't work. > > Hey, I did what I could do best: try to understand and fix it quickly! > I _was_ pretty sure it was right tho :) Right. I didn't check it, since I had the tested version waiting (all night) to be checked in. >> The changes for min() weren't needed; vext.h had a definition. > > I guessed that; however, you didn't use max() in the surrounding code, you > used a broken-out form of what max() is usually defined to (or MAX() for > that matter.) Why be consistent when you can be confusing? Yes, maybe I should reconsider that one. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 20:19:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id A51B914C42 for ; Fri, 2 Jul 1999 20:19:19 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA20899 for ; Fri, 2 Jul 1999 23:19:26 -0400 (EDT) Date: Fri, 2 Jul 1999 23:19:26 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: Re: Just for the record (was: Re: Fixing other people's code (was: world broken in vinum (PATCH))) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about that, Greg; I didn't realize it was a personal message I forwarded. Sorry, everyone else, for that faux pas in public :( Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 20:24:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 94E921528F for ; Fri, 2 Jul 1999 20:24:28 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA15294; Sat, 3 Jul 1999 12:54:27 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA03209; Sat, 3 Jul 1999 12:54:26 +0930 (CST) Date: Sat, 3 Jul 1999 12:54:26 +0930 From: Greg Lehey To: "Brian F. Feldman" Cc: current@FreeBSD.ORG Subject: Re: Just for the record (was: Re: Fixing other people's code (was: world broken in vinum (PATCH))) Message-ID: <19990703125426.U87392@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brian F. Feldman on Fri, Jul 02, 1999 at 11:19:26PM -0400 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 2 July 1999 at 23:19:26 -0400, Brian F. Feldman wrote: > Sorry about that, Greg; I didn't realize it was a personal message I forwarded. > Sorry, everyone else, for that faux pas in public :( I'm not upset. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 21:57:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (Postfix) with ESMTP id 0AF0D14BB8; Fri, 2 Jul 1999 21:57:28 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.3/8.9.3) with ESMTP id IAA19340; Sat, 3 Jul 1999 08:57:25 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (minas-tirith.pol.ru [127.0.0.1]) by shuttle.svib.ru (8.9.3/8.8.8) with ESMTP id JAA31071; Sat, 3 Jul 1999 09:01:15 +0400 (MSD) (envelope-from tarkhil@shuttle.svib.ru) Message-Id: <199907030501.JAA31071@shuttle.svib.ru> X-Mailer: exmh version 2.0.3 To: John Polstra Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Soft-updates feedback In-reply-to: Your message "Wed, 30 Jun 1999 18:54:23 PDT." Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Jul 1999 09:01:14 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About a week ago, I've posted a message here and didn't got positive replies. The problem is: when I use soft-updates on IDE disks (disk on primary master, disk on secondary master, CD on primary slave), any active disk-using program (starting Netscape, starting EXMH) causes all other programs literally to stop for several seconds (well, 20-30 seconds is quite often!). Turning soft-updates off causes this nastiness to disappear, but also slows down disk-active processess. 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 2 21:59:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B008614C7F for ; Fri, 2 Jul 1999 21:59:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id VAA01856; Fri, 2 Jul 1999 21:59:31 -0700 Date: Fri, 2 Jul 1999 21:59:02 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Brian F. Feldman" Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > If it's really blocking folks because things don't compile, it is always > > > acceptable to do what you need to do- the tree should always compile even > > > if -current. If the system doesn't boot because of change, then that's an > > > obvious one too. If things work differently or not as well, but things > > > are more or less working, it's not an emergency, so leave it for the > > > author to fix.... > > > > ...always modulo a short delay (call it a couple of hours) after reporting > > the problem... after all, you don't *know* that the update isn't finished > > and that other things are coming down the pipe... but a couple of hours > > leaves really the most reasonable time for an integration to complete and > > the author to have had lunch in between. > > > > I worded my original post wrong; my change did fix world. Your second point > (the "wait and see" approach) wouldn't apply in this case: Greg was asleep, > and world was broken. You have to wait at least a little bit because with CVS there is no atomic update of a set of modules. IF make world is broken, waiting at least a certain period of time and then doing another update is important to ensure that you just simply updated only part of a an active checkin cycle. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 22:25:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9389A14C7F; Fri, 2 Jul 1999 22:25:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01914; Fri, 2 Jul 1999 22:25:11 -0700 Date: Fri, 2 Jul 1999 22:24:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alex Povolotsky Cc: John Polstra , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Soft-updates feedback In-Reply-To: <199907030501.JAA31071@shuttle.svib.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while this is happening, what does 'iostat 1' and 'vmstat 1' tell you? On Sat, 3 Jul 1999, Alex Povolotsky wrote: > About a week ago, I've posted a message here and didn't got positive replies. > > The problem is: > > when I use soft-updates on IDE disks (disk on primary master, disk on > secondary master, CD on primary slave), any active disk-using program > (starting Netscape, starting EXMH) causes all other programs literally to stop > for several seconds (well, 20-30 seconds is quite often!). Turning > soft-updates off causes this nastiness to disappear, but also slows down > disk-active processess. > > Alex. > > > > > 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 2 22:28:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0053414C7F; Fri, 2 Jul 1999 22:28:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA19233; Fri, 2 Jul 1999 22:28:18 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA00889; Fri, 2 Jul 1999 22:28:18 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 02 Jul 1999 22:28:18 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Jacob Subject: Re: Soft-updates feedback Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG, Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know why I'm on the cc for this thread, but please remove me. And it shouldn't be cross-posted to 2 lists. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 2 22:53:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 3586914D52 for ; Fri, 2 Jul 1999 22:53:35 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id WAA05878; Fri, 2 Jul 1999 22:53:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907030553.WAA05878@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: Soft-updates feedback In-reply-to: Your message of "Fri, 02 Jul 1999 22:24:42 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Jul 1999 22:53:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make sure that you have dma enable on your IDE disks . Basically, soft-updates does short bursts of disk activities which can crash a disk or slow down a system during the disk i/o operations using PIO. Yes, I have seen disks spin mindlessly due to the "intensive" short burts of disk io activities and the problem went away by switching to DMA. -- Amancio Hasty ahasty@mindspring.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 2 22:55:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from sturm.canonware.com (canonware.com [204.107.140.54]) by hub.freebsd.org (Postfix) with ESMTP id 7A66D15278 for ; Fri, 2 Jul 1999 22:55:14 -0700 (PDT) (envelope-from jasone@canonware.com) Received: from localhost (jasone@localhost) by sturm.canonware.com (8.8.8/8.8.8) with ESMTP id WAA29645 for ; Fri, 2 Jul 1999 22:55:12 -0700 (PDT) (envelope-from jasone@canonware.com) Date: Fri, 2 Jul 1999 22:55:12 -0700 (PDT) From: Jason Evans To: current@freebsd.org Subject: mmap(), MAP_STACK, and safe addresses Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need a clue about process memory layout, and am hoping someone can provide it. I wrote a program to discover what address ranges mmap() can handle (trying to hack growable stacks into libc_r), and came up with the following output (annotations in `[]'): ---- FreeBSD donner 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Fri Jul 2 19:25:07 PDT 1999 toor@donner:/usr/src/sys/compile/CUSTOM_donner i386 text data bss dec hex filename 2464 220 272 2956 b8c ./brute_stack initialized global: 0x08049a90 uninitialized global: 0x08049c74 main() function: 0x08048604 main() stack: ~0xbfbfd90c (grows down) stack size: 0x1000 bytes bad: 0x00000000 --> 0x00000fff, 0x00001000 bytes good: 0x00001000 --> 0x08047fff, 0x08047000 bytes [???] bad: 0x08048000 --> 0x280e3fff, 0x2009c000 bytes [text->data->bss->heap->] good: 0x280e4000 --> 0xbfbddfff, 0x97afa000 bytes [-><-] bad: 0xbfbde000 --> 0xffffffff, 0x40422000 bytes [<-stack, env] malloc()ed stack: 0x0804b000 ---- Some questions about the above: 1) What is the ??? range for? (The loader?) 2) Where exactly is the stack on the x86? 3) Where is the stack on the Alpha? 4) Where is the code that I should have read instead of bothering you? The rtld-elf code mentions the expectation that the "SVR4 ABI specification, Intel 386 Processor Supplement" is adhered to, but I couldn't find anything more specific. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 3:11:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 4FE65153EB for ; Sat, 3 Jul 1999 03:11:00 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id DAA00913 for ; Sat, 3 Jul 1999 03:10:59 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377DE1B2.BDB78343@gorean.org> Date: Sat, 03 Jul 1999 03:10:58 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: More make world fun Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that things are supposed to be fixed up in the world build I decided to finish what I started this morning. The build completed ok, but when it started the install phase it got part way through, then the machine spontaneously rebooted itself (first time ever on a make world for me, wheeee). When the system came back just about everything failed, including /bin/sh, which means the system is hose-ed. I'm pretty sure that I can restore the system to a usable state by doing an "upgrade" with a recent snap, but I'm a little concerned about the reboot, since this system has been rock solid since I built it in january. Any suggestions on ways to debug the problem are more than welcome. I have some time this weekend that I can devote to it. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 3:25:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 55EC714F2D; Sat, 3 Jul 1999 03:25:41 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-157.skylink.it [194.185.55.157]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id MAA24401; Sat, 3 Jul 1999 12:24:50 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id JAA07814; Sat, 3 Jul 1999 09:24:39 +0200 (CEST) Date: Sat, 3 Jul 1999 09:24:39 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing list Cc: justin@freebsd.org Subject: panic in dadone, PR 12041 Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1356166914-930986679=:7798" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1356166914-930986679=:7798 Content-Type: TEXT/PLAIN; charset=US-ASCII PR 12041 complains about the fact that the system panics with a divide by zero if a zip drive is connected with a medium in it. I've not been able to reproduce the problem, but remember having similar problems when implementing the umass driver for USB. The problem is caused by the following line in scsi_da.c:1326 (3.2-STABLE but applies to CURRENT as well): snprintf(announce_buf, sizeof(announce_buf), "%ldMB (%d %d byte sectors: %dH %dS/T%dC)", dp->sectors / ((1024L * 1024L) / dp->secsize), dp->sectors, dp->secsize, dp->heads, dp->secs_per_track, dp->cylinders); secsize is 0 in some cases (I think it happens when an INQUIRY fails without being detected as having failed). In any case a/(b/c) = a*c/b, but without any divl (with b sometimes 0 and c == 2^20). Patch attached. Nick -- e-Mail: hibma@skylink.it --0-1356166914-930986679=:7798 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="scsi_da.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: SW5kZXg6IHNjc2lfZGEuYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNT IGZpbGU6IC9ob21lL25jdnMvc3JjL3N5cy9jYW0vc2NzaS9zY3NpX2RhLmMs dg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjE5LjIuNQ0KZGlmZiAtdSAtcjEu MTkuMi41IHNjc2lfZGEuYw0KLS0tIHNjc2lfZGEuYwkxOTk5LzA1LzIyIDIy OjU4OjI3CTEuMTkuMi41DQorKysgc2NzaV9kYS5jCTE5OTkvMDcvMDMgMDc6 MjQ6MzUNCkBAIC0xMzI2LDcgKzEzMjYsNyBAQA0KIAkJCWRwID0gJnNvZnRj LT5wYXJhbXM7DQogCQkJc25wcmludGYoYW5ub3VuY2VfYnVmLCBzaXplb2Yo YW5ub3VuY2VfYnVmKSwNCiAJCQkJIiVsZE1CICglZCAlZCBieXRlIHNlY3Rv cnM6ICVkSCAlZFMvVCAlZEMpIiwNCi0JCQkJZHAtPnNlY3RvcnMgLyAoKDEw MjRMICogMTAyNEwpIC8gZHAtPnNlY3NpemUpLA0KKwkJCQlkcC0+c2Vjc2l6 ZSAqIGRwLT5zZWN0b3JzIC8gKDEwMjRMICogMTAyNEwpLA0KIAkJCQlkcC0+ c2VjdG9ycywgZHAtPnNlY3NpemUsIGRwLT5oZWFkcywNCiAJCQkJZHAtPnNl Y3NfcGVyX3RyYWNrLCBkcC0+Y3lsaW5kZXJzKTsNCiAJCX0gZWxzZSB7DQo= --0-1356166914-930986679=:7798-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 5: 4: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B9AE814E27 for ; Sat, 3 Jul 1999 05:03:55 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 82F0B64; Sat, 3 Jul 1999 20:03:53 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-reply-to: Your message of "Fri, 02 Jul 1999 17:33:11 MST." Date: Sat, 03 Jul 1999 20:03:53 +0800 From: Peter Wemm Message-Id: <19990703120353.82F0B64@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > > Let me add to this: > > opinion: > > > > If it's really blocking folks because things don't compile, it is always > > acceptable to do what you need to do- the tree should always compile even > > if -current. If the system doesn't boot because of change, then that's an > > obvious one too. If things work differently or not as well, but things > > are more or less working, it's not an emergency, so leave it for the > > author to fix.... > > ...always modulo a short delay (call it a couple of hours) after reporting > the problem... after all, you don't *know* that the update isn't finished > and that other things are coming down the pipe... but a couple of hours > leaves really the most reasonable time for an integration to complete and > the author to have had lunch in between. I'd like to chime in here.. It really does depend on the situation and requires the people involved to make a judgement call as to whether they think it's worth bypassing an offline maintainer or owner or whatever. If you feel you can justify (if needed) bypassing normal channels and you are confident that you're not going to screw something up then I'd be suggesting it's OK to go ahead - but be prepared to back it out or have it replaced if the maintainer disagrees. If doing this, be sure to label something as a temporary fix, or workaround or whatever so that it's clear what's going on. Personally, for something like vinum where you can strand people if you let a broken /sbin/vinum get installed, I'd be thinking more along the lines of disconnecting it from the Makefiles rather than jumping in. That would get world running again, and leave people with known good /sbin/vinum and /modules/vinum.ko etc. It all comes down to making a judgement call after considering the consequences of *possibly* making things worse, versus the inconvenience of having something broken. Inconvenience to the normal maintainer should be a consideration but isn't a huge deal since it is quite easy to back a commit out... Anyway, That's my 2 cents worth on the subject. :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 7:55:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 49C4214E27 for ; Sat, 3 Jul 1999 07:55:11 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A4BD564; Sat, 3 Jul 1999 22:55:07 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Evans Cc: current@freebsd.org Subject: Re: mmap(), MAP_STACK, and safe addresses In-reply-to: Your message of "Fri, 02 Jul 1999 22:55:12 MST." Date: Sat, 03 Jul 1999 22:55:07 +0800 From: Peter Wemm Message-Id: <19990703145507.A4BD564@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Evans wrote: > I need a clue about process memory layout, and am hoping someone can > provide it. I wrote a program to discover what address ranges mmap() can > handle (trying to hack growable stacks into libc_r), and came up with the > following output (annotations in `[]'): > > ---- > FreeBSD donner 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Fri Jul 2 19:25:07 > PDT 1999 toor@donner:/usr/src/sys/compile/CUSTOM_donner i386 > text data bss dec hex filename > 2464 220 272 2956 b8c ./brute_stack > initialized global: 0x08049a90 > uninitialized global: 0x08049c74 > main() function: 0x08048604 > main() stack: ~0xbfbfd90c (grows down) > stack size: 0x1000 bytes > bad: 0x00000000 --> 0x00000fff, 0x00001000 bytes > good: 0x00001000 --> 0x08047fff, 0x08047000 bytes [???] > bad: 0x08048000 --> 0x280e3fff, 0x2009c000 bytes [text->data->bss->heap->] > good: 0x280e4000 --> 0xbfbddfff, 0x97afa000 bytes [-><-] > bad: 0xbfbde000 --> 0xffffffff, 0x40422000 bytes [<-stack, env] > malloc()ed stack: 0x0804b000 > ---- > > Some questions about the above: > > 1) What is the ??? range for? (The loader?) Under ELF, the program load address is 0x08048000. Why? Good question - "because it is". :-) > 2) Where exactly is the stack on the x86? 0xbfbddfff, growing down. User addressable space (ie: the limit on the %cs and %ds segments) ends there, a user cannot address beyond there. 0xbfbde000 through 0xbfbdffff are where the upages would have been if they still existed. The space is still reserved since there is a virtual redirection there for libkvm and gdb to read the upages from via the procfs 'mem' file. 0xbfbe0000 through 0xbfffffff are the page tables, page directories etc. 0xc0000000 onwards is kernel space. You can also get info from the map file in procfs: Format: start, end, resident, private resident, vm object, access, refcnt, shadowcount, flags, cow, needs-copy, pager type. peter@overcee[10:35pm]~src/sys/nfs-118> cat /proc/curproc/map 0x08048000 0x08054000 12 13 0xc6bb45e8 r-x 2 1 0x0 COW NC vnode 0x08054000 0x08055000 1 0 0xc6d50d80 rw- 1 0 0x2180 COW NNC vnode 0x08055000 0x08059000 3 0 0xc6c67510 rw- 2 0 0x2180 NCOW NNC default 0x08059000 0x0806a000 2 0 0xc6c67510 rwx 2 0 0x2180 NCOW NNC default 0x28054000 0x28055000 1 0 0xc6ba2af8 rwx 1 0 0x2180 NCOW NNC default 0xbfbde000 0xbfbfe000 1 0 0xc6c8b6c0 rwx 1 0 0x2180 NCOW NNC default COW = copy-on-write, NCOW = not copy on write. NC = needs copy, NNC = not needs copy. In this case, the stack is in the last segment and is a whole one page. > 3) Where is the stack on the Alpha? Umm... pwroot@ashburton[10:35pm]/home/ports/net/nttcp-111# cat /proc/curproc/map 0x11fdc000 0x11ffc000 1 0 0xfffffe0005f33550 rwx 1 0 0x2180 NCOW NNC default 0x120000000 0x120012000 9 10 0xfffffe0005b61340 r-x 2 1 0x0 COW NC vnode 0x120020000 0x120022000 1 0 0xfffffe000602bd90 rw- 1 0 0x2180 COW NNC vnode 0x120022000 0x120026000 2 0 0xfffffe0005f24210 rw- 2 0 0x2180 NCOW NNC default 0x120026000 0x120038000 2 0 0xfffffe0005f24210 rwx 2 0 0x2180 NCOW NNC default 0x160020000 0x160022000 1 0 0xfffffe0005c38420 rw- 1 0 0x2180 NCOW NNC default I would guess 0x160021fff and growing down. > 4) Where is the code that I should have read instead of bothering you? The > rtld-elf code mentions the expectation that the "SVR4 ABI specification, > Intel 386 Processor Supplement" is adhered to, but I couldn't find > anything more specific. Another useful tool for investigating this sort of thing is objdump. peter@overcee[10:44pm]~src/sys-119> objdump --all-headers /bin/ls | more [..] start address 0x0804807c Program Header: LOAD off 0x00000000 vaddr 0x08048000 paddr 0x08048000 align 2**12 filesz 0x000282e0 memsz 0x000282e0 flags r-x LOAD off 0x000282e0 vaddr 0x080712e0 paddr 0x080712e0 align 2**12 filesz 0x000012c4 memsz 0x0000a2b0 flags rw- Sections: Idx Name Size VMA LMA File off Algn 0 .init 00000006 08048074 08048074 00000074 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .text 00024e10 0804807c 0804807c 0000007c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 2 .fini 00000006 0806ce8c 0806ce8c 00024e8c 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 3 .rodata 00003440 0806cea0 0806cea0 00024ea0 2**5 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .data 000012b4 080712e0 080712e0 000282e0 2**5 CONTENTS, ALLOC, LOAD, DATA [...] The program header is basically all that the exec handler looks at. It's the equivalent of the old text/data/bss counts in a.out. In this case, it means: File offset 0 gets mmapped to 0x08048000, file length 0x000282e0 == mapping length, read-only (ie: ELF metadata, text and rodata) File offset 0x000282e0 gets mapped to 0x080712e0, the mapping is 0x0000a2b0 bytes long, but only the first 0x000012c4 bytes come from the file. The gap must be zeroed. This is the data (from the file) and bss (zeroed). The section table is not used at run time. It contains detail about what is actually in the load section. People often see the number of sections and compare that to the 3 in a.out and have a heart attack. There's sometimes 30 to 50 sections. However, the key is that only the program header is used at runtime and that lives entirely in the first page of the file and only has two entries. That's also ELF's big problem. That hybrid data+bss section is a real pain in the behind to get right, as there is one page that has got data from the file and the rest is zeroed. You have to explicitly zero it otherwise it gets metadata from the mmap of the file. This is a real pain since it causes an out-of-order read when execing as the demand loading causes execve to pause in kernel mode while the page is pulled in. On the plus side, with ELF you can specifically nominate your segment load addresses and entry points. If you want your .text to start at 0x6000, there is nothing at all stopping you, and the kernel will quite happily exec it and everything will work. You just tell ld and it arranges it. > Thanks, > Jason Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 10:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id DD9E115077 for ; Sat, 3 Jul 1999 10:48:53 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id KAA04518 for ; Sat, 3 Jul 1999 10:48:53 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377E4D04.68C01D58@gorean.org> Date: Sat, 03 Jul 1999 10:48:52 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: panic: ffs_blkfree: freeing free block (Was: Re: More make world fun) References: <377DE1B2.BDB78343@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug wrote: > > Now that things are supposed to be fixed up in the world build I decided > to finish what I started this morning. The build completed ok, but when it > started the install phase it got part way through, then the machine > spontaneously rebooted itself (first time ever on a make world for me, > wheeee). > > When the system came back just about everything failed, including /bin/sh, > which means the system is hose-ed. Ok, I decided to try and find out what happened with this, and using csh at the single user prompt I was able to get things to the point where I could view logs, etc. There was nothing in /var/log/messages at all, and the log of the build stopped at the point where it was installing libc_r. However when I ran 'make installworld' this time it ran past the libc_r no problem, but eventually I got a panic. Here is the info from the debugger: dev=0x2fb0e, block = 9432, fs = /usr panic: ffs_blkfree: freeing free block Debugger("panic") Stopped at Debugger+0x37: movl $0, in Debugger trace: Debugger() panic() ffs_blkfree() ffs_truncate() ufs_inactive() ufs_vnoperate() vput() unlink() syscall() Xint0x80_syscall() IIRC this system was last upgraded (world and kernel) on the first, maybe june 30th. (I can get the exact date if needed.) It's all scsi, adaptec 2940UW adapter, IBM DCAS 4 gig disk, no softupdats. Let me know if there is anything else to do here. I'll be out most of the day today, but I'll be back tonight. HTH, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 11:37: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AEF1F15211; Sat, 3 Jul 1999 11:36:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA03197; Sat, 3 Jul 1999 11:36:32 -0700 Date: Sat, 3 Jul 1999 11:35:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD CURRENT Mailing list , justin@FreeBSD.ORG Subject: Re: panic in dadone, PR 12041 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll fix it, but not this way. It's time to prepare for handling larger than terabyte disks that still have a 512 byte sector size as well. The actual calculation should be: (((u_int64_t) dp->secsize) * ((u_int64_t) dp->sectors)) >> 20LL and the format statement should be %qdMB for the Megabyte size. On Sat, 3 Jul 1999, Nick Hibma wrote: > > PR 12041 complains about the fact that the system panics with a divide > by zero if a zip drive is connected with a medium in it. I've not been > able to reproduce the problem, but remember having similar problems > when implementing the umass driver for USB. The problem is caused by the > following line in scsi_da.c:1326 (3.2-STABLE but applies to CURRENT as > well): > > snprintf(announce_buf, sizeof(announce_buf), > "%ldMB (%d %d byte sectors: %dH %dS/T%dC)", > dp->sectors / ((1024L * 1024L) / dp->secsize), > dp->sectors, dp->secsize, dp->heads, > dp->secs_per_track, dp->cylinders); > > secsize is 0 in some cases (I think it happens when an INQUIRY fails > without being detected as having failed). > > In any case a/(b/c) = a*c/b, but without any divl (with b sometimes 0 > and c == 2^20). > > Patch attached. > > Nick > > -- > e-Mail: hibma@skylink.it > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 11:57:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AA0B714F41; Sat, 3 Jul 1999 11:57:04 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA66065; Sat, 3 Jul 1999 12:57:00 -0600 (MDT) (envelope-from ken) Message-Id: <199907031857.MAA66065@panzer.kdm.org> Subject: Re: panic in dadone, PR 12041 In-Reply-To: from Nick Hibma at "Jul 3, 1999 09:24:39 am" To: hibma@skylink.it (Nick Hibma) Date: Sat, 3 Jul 1999 12:57:00 -0600 (MDT) Cc: current@FreeBSD.ORG (FreeBSD CURRENT Mailing list), gibbs@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote... > > PR 12041 complains about the fact that the system panics with a divide > by zero if a zip drive is connected with a medium in it. I've not been > able to reproduce the problem, but remember having similar problems > when implementing the umass driver for USB. The problem is caused by the > following line in scsi_da.c:1326 (3.2-STABLE but applies to CURRENT as > well): > > snprintf(announce_buf, sizeof(announce_buf), > "%ldMB (%d %d byte sectors: %dH %dS/T%dC)", > dp->sectors / ((1024L * 1024L) / dp->secsize), > dp->sectors, dp->secsize, dp->heads, > dp->secs_per_track, dp->cylinders); > > secsize is 0 in some cases (I think it happens when an INQUIRY fails > without being detected as having failed). > > In any case a/(b/c) = a*c/b, but without any divl (with b sometimes 0 > and c == 2^20). This is a good idea, but will probably just delay the appearance of the problem. It also shows that the Zip drive has buggy firmware, since it shouldn't return a sector size of 0 without an error. > Index: scsi_da.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v > retrieving revision 1.19.2.5 > diff -u -r1.19.2.5 scsi_da.c > --- scsi_da.c 1999/05/22 22:58:27 1.19.2.5 > +++ scsi_da.c 1999/07/03 07:24:35 > @@ -1326,7 +1326,7 @@ > dp = &softc->params; > snprintf(announce_buf, sizeof(announce_buf), > "%ldMB (%d %d byte sectors: %dH %dS/T %dC)", > - dp->sectors / ((1024L * 1024L) / dp->secsize), > + dp->secsize * dp->sectors / (1024L * 1024L), > dp->sectors, dp->secsize, dp->heads, > dp->secs_per_track, dp->cylinders); > } else { > What will happen if the drive is reporting a sector size of zero without returning an error is that you'll get into daopen(), and then panic in the slice code. There has been a similar discussion, with the subject "FreeBSD panics with Mylex DAC960SX" on the -scsi list for the past few days. Bruce posted a patch to the slice code to keep it from panicing. In that case, there are some bugs in the CAM error handling code that keep it from returning an error status in cases where the drive returns a sense key, but no ASC/ASCQ. So we'd end up attaching to the drive, but skipping the standard announcement (above), which would have caused a panic. We would get all the way into daopen(), and then panic in the slice code when it attempted to mod by the sector size. In looking at dopen(), I see there are also some (probably minor) problems that will crop up if dsopen() returns an error. Mainly some flags, etc., that don't get cleaned up. You're welcome to check the patch in, but things won't work correctly in that case at least until Bruce checks in his slice fix, or until we start checking for a sector size of 0 in dasetgeom(). Ken -- Kenneth Merry ken@plutotech.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 3 12: 4:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 35D6115211 for ; Sat, 3 Jul 1999 12:02:21 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA12817; Sat, 3 Jul 1999 13:02:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA28825; Sat, 3 Jul 1999 13:00:09 -0600 (MDT) Message-Id: <199907031900.NAA28825@harmony.village.org> To: mjacob@feral.com Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 02 Jul 1999 21:59:02 PDT." References: Date: Sat, 03 Jul 1999 13:00:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : You have to wait at least a little bit because with CVS there is no atomic : update of a set of modules. IF make world is broken, waiting at least a : certain period of time and then doing another update is important to : ensure that you just simply updated only part of a an active checkin : cycle. Which is why when I hit this, I check the commit messages. I also do a cvsup to freefall (normally I just hit one of the mirrors) and see if the problem is in the sources of the moment. If the problem persisits, I either see if it is trivial to fix and/or send mail to the committer. Sometimes, if I'm thinking, I'll see if they are actively logged into freefall and contact them there.... I do realize this isn't an option for everybody, but has worked for me in the past. 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 3 12:40:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from argus.tfs.net (host1-19.birch.net [216.212.1.19]) by hub.freebsd.org (Postfix) with ESMTP id 26C221517A for ; Sat, 3 Jul 1999 12:40:45 -0700 (PDT) (envelope-from jbryant@argus.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.9.3/8.8.5) id OAA26973; Sat, 3 Jul 1999 14:40:26 -0500 (CDT) From: Jim Bryant Message-Id: <199907031940.OAA26973@argus.tfs.net> Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: from Ben Rosengart at "Jul 3, 99 00:09:53 am" To: ben@skunk.org (Ben Rosengart) Date: Sat, 3 Jul 1999 14:40:25 -0500 (CDT) Cc: freebsd-current@freebsd.org Reply-To: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-CURRENT #31: Thu Apr 8 10:40:17 CDT 1999 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply: > On Sat, 3 Jul 1999, Greg Lehey wrote: > > > I personally think that, in such a case, you'd be justified to commit > > it as a temporary measure. Due to the difference in time zones, this > > has hit people while I've been asleep. That doesn't mean the commit > > would stay, of course, but at least it would save people unnecessary > > pain. Note, of course, that I have now committed the correct file, > > which I had forgotten last night. > > > > What do you others think? > > Was the fix that wasn't yours correct? 'Cause I'd rather have code that > doesn't compile than code that compiles but is subtly wrong. untested code shouldn't be checked in to begin with. such are the basics of version control. mistakes happen in any project, but where i come from CVS/RCS/etc is for tested and working code. if i made such a mistake, i would be grateful for a temporary kludge submitted by someone, assuming they know that it is subject to a proper fix at any moment. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 13:25:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep4.post.tele.dk (fep4.post.tele.dk [195.41.46.139]) by hub.freebsd.org (Postfix) with ESMTP id 3697B15171 for ; Sat, 3 Jul 1999 13:25:12 -0700 (PDT) (envelope-from peter@holm.cc) Received: from holm.cc ([195.249.209.231]) by fep4.post.tele.dk (InterMail v4.0 201-221) with ESMTP id <19990703202511.CXZF18064.fep4@holm.cc> for ; Sat, 3 Jul 1999 22:25:11 +0200 Message-ID: <377E723D.19674A38@holm.cc> Date: Sat, 03 Jul 1999 22:27:41 +0200 From: Peter Holm X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: 12 trap in rfork+0x22 Content-Type: multipart/mixed; boundary="------------C6DB7A8D1433429B6317E010" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C6DB7A8D1433429B6317E010 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I don't know is this is of any interest, but a rfork(0) will cause a fault. I have included a patch. fault code = supervisor read, page not present instruction pointer = 0x8:0xc015ff46 stack pointer = 0x10:0xc6894f38 frame pointer = 0x10:0xc6894f4c 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 = 94200 (syscall) interrupt mask = kernel: type 12 trap, code=0 Stopped at rfork+0x22: movl 0x30(%eax),%eax db> p %eax c015ff46 <--- why this? eax == 0x8 in show reg db> trace rfork(c680a100,c6894f80,2,bfbfdc24,bfbfdc30) at rfork+0x22 syscall(2f,2f,2f,bfbfdc30,bfbfdc24) at syscall+0x182 Xint0x80_syscall() at Xint0x80_syscall+0x30 db> show reg cs 0x8 ds 0x10 es 0x10 fs 0x10 ss 0x10 eax 0x8 ecx 0x7d8aa8c3 edx 0 ebx 0xc680a100 esp 0xc6894f38 ebp 0xc6894f4c esi 0xc02f9a3c sysent+0x7d8 edi 0 eip 0xc015ff46 rfork+0x22 efl 0x10246 rfork+0x22: movl 0x30(%eax),%eax db> -- Peter Holm | mailto:peter@holm.cc | http://login.dknet.dk/~pho/ -[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] - --------------C6DB7A8D1433429B6317E010 Content-Type: text/plain; charset=us-ascii; name="diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diff" *** src/sys/kern/kern_fork.c~ Sat Jul 3 21:15:58 1999 --- src/sys/kern/kern_fork.c Sat Jul 3 21:54:18 1999 *************** *** 130,136 **** error = fork1(p, uap->flags, &p2); if (error == 0) { ! p->p_retval[0] = p2->p_pid; p->p_retval[1] = 0; } return error; --- 130,139 ---- error = fork1(p, uap->flags, &p2); if (error == 0) { ! if (p2 == NULL) ! p->p_retval[0] = 0; ! else ! p->p_retval[0] = p2->p_pid; p->p_retval[1] = 0; } return error; *************** *** 196,201 **** --- 199,205 ---- p1->p_fd = newfd; } } + *procp = NULL; return (0); } --------------C6DB7A8D1433429B6317E010-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 13:34: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3E00215294 for ; Sat, 3 Jul 1999 13:33:29 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id QAA39141; Sat, 3 Jul 1999 16:30:59 -0400 (EDT) Date: Sat, 3 Jul 1999 16:30:59 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Warner Losh Cc: mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) In-Reply-To: <199907031900.NAA28825@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Warner Losh wrote: > In message Matthew Jacob writes: > : You have to wait at least a little bit because with CVS there is no atomic > : update of a set of modules. IF make world is broken, waiting at least a > : certain period of time and then doing another update is important to > : ensure that you just simply updated only part of a an active checkin > : cycle. > > Which is why when I hit this, I check the commit messages. I also do > a cvsup to freefall (normally I just hit one of the mirrors) and see > if the problem is in the sources of the moment. If the problem > persisits, I either see if it is trivial to fix and/or send mail to > the committer. Sometimes, if I'm thinking, I'll see if they are > actively logged into freefall and contact them there.... Checking commit messages was the first thing I did, in this case. > > I do realize this isn't an option for everybody, but has worked for me > in the past. > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 14: 0:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id EFDF915260 for ; Sat, 3 Jul 1999 13:59:43 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AE91578; Sun, 4 Jul 1999 04:59:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Holm Cc: freebsd-current@FreeBSD.org Subject: Re: 12 trap in rfork+0x22 In-reply-to: Your message of "Sat, 03 Jul 1999 22:27:41 +0200." <377E723D.19674A38@holm.cc> Date: Sun, 04 Jul 1999 04:59:41 +0800 From: Peter Wemm Message-Id: <19990703205941.AE91578@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Holm wrote: > I don't know is this is of any interest, but a rfork(0) will cause a > fault. I have included a patch. Argh! Thanks, Committed.. (rev 1.63 kern_fork.c) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 15: 6:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 59F8515185; Sat, 3 Jul 1999 15:06:11 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA24522; Sat, 3 Jul 1999 15:06:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA06152; Sat, 3 Jul 1999 15:06:10 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 03 Jul 1999 15:06:10 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: HEADS UP: Soft-updates sources have been moved Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just finished moving the soft-updates sources to "src/sys/contrib/softupdates", as announced a few days ago. All users of soft-updates will need to update their symbolic links in "src/sys/ufs/ffs" before configuring and building a new kernel. This change affects the main branch (-current), the RELENG_3 branch (-stable), and Warner's RELENG_3_2_PAO branch. I've updated the comments in LINT and README.softupdates accordingly. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 15:12:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 82E33151C5; Sat, 3 Jul 1999 15:12:47 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-158.skylink.it [194.185.55.158]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA00995; Sun, 4 Jul 1999 00:11:55 +0200 Received: from localhost (localhost.plazza.it [127.0.0.1]) by heidi.plazza.it (8.8.8/8.8.5) with SMTP id AAA08953; Sun, 4 Jul 1999 00:11:41 +0200 (CEST) Date: Sun, 4 Jul 1999 00:11:41 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: FreeBSD CURRENT Mailing list , gibbs@FreeBSD.ORG Subject: Re: panic in dadone, PR 12041 In-Reply-To: <199907031857.MAA66065@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > secsize is 0 in some cases (I think it happens when an INQUIRY fails > > without being detected as having failed). > > > > In any case a/(b/c) = a*c/b, but without any divl (with b sometimes 0 > > and c == 2^20). > > This is a good idea, but will probably just delay the appearance of the > problem. It also shows that the Zip drive has buggy firmware, since it > shouldn't return a sector size of 0 without an error. That is perfectly true. It's just that I have not the foggiest why the thing crashes, and this removes the panic. But, rewriting the computation removes one divl from the object code (replacing it by a multiply) :) With respect to the problem with the Zip drive: I haven't got the foggiest what the problem is. Anyone with a non-Plus drive has the same problem (as stated in PR 12041)? Cheers, Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 19: 8:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id B124014F51 for ; Sat, 3 Jul 1999 19:08:30 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA18932; Sun, 4 Jul 1999 11:38:28 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA07064; Sun, 4 Jul 1999 11:38:24 +0930 (CST) Date: Sun, 4 Jul 1999 11:38:22 +0930 From: Greg Lehey To: jbryant@tfs.net Cc: Ben Rosengart , freebsd-current@FreeBSD.ORG Subject: Re: Fixing other people's code (was: world broken in vinum (PATCH)) Message-ID: <19990704113820.K709@freebie.lemis.com> References: <199907031940.OAA26973@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907031940.OAA26973@argus.tfs.net>; from Jim Bryant on Sat, Jul 03, 1999 at 02:40:25PM -0500 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 3 July 1999 at 14:40:25 -0500, Jim Bryant wrote: > In reply: >> On Sat, 3 Jul 1999, Greg Lehey wrote: >> >>> I personally think that, in such a case, you'd be justified to commit >>> it as a temporary measure. Due to the difference in time zones, this >>> has hit people while I've been asleep. That doesn't mean the commit >>> would stay, of course, but at least it would save people unnecessary >>> pain. Note, of course, that I have now committed the correct file, >>> which I had forgotten last night. >>> >>> What do you others think? >> >> Was the fix that wasn't yours correct? 'Cause I'd rather have code that >> doesn't compile than code that compiles but is subtly wrong. > > untested code shouldn't be checked in to begin with. such are the > basics of version control. mistakes happen in any project, but where > i come from CVS/RCS/etc is for tested and working code. Note that the case we're talking about here wasn't an issue of untested code. The code had been tested, and it works. The problem was that I had forgotten to commit one file. Normally, after committing a set of changes, I cvsup and do a "make world". That takes time, of course, and it doesn't stop others from tripping over the same problem. > if i made such a mistake, i would be grateful for a temporary kludge > submitted by someone, assuming they know that it is subject to a > proper fix at any moment. Agreed. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 3 19:13:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 164CE1520D for ; Sat, 3 Jul 1999 19:13:35 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA17547; Sun, 4 Jul 1999 12:13:21 +1000 Date: Sun, 4 Jul 1999 12:13:21 +1000 From: Bruce Evans Message-Id: <199907040213.MAA17547@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, peter@holm.cc Subject: Re: 12 trap in rfork+0x22 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >db> p %eax >c015ff46 <--- why this? eax == 0x8 in show reg %eax seems to be an undetected syntax error. '%' seems to be an alias for '.'. The %eax register is given by $eax. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message